![]() "br0 & br1" I "fixed" it by doing the following steps: This seemed to be an issue since I had previously set up two bridged connections. I do agree it is a port mapping issue with the upgrade. Quote from odjhlofton on May 31, 2019, 5:09 not going to believe it but it works now. Could either one of you two give me a link to some instructions on how to do this? I'm not really running any live projects right now so a system restore and clean wipe wouldn't really hurt me. At this point I'd be happy just reverting to the old version with the backup the system made prior to the upgrade but I'm not sure how to do that. It can't even ping the router but yet I can see DHCP reservations for it in my router. I looked at the article shared and it is similar except at least that person could connect to antman web GUI. Could either one of you two give me a link to some instructions on how to do I've tried every port on the antsle and cannot get a single one of them to work right. Quote from odjhlofton on May 29, 2019, 6:50 I've tried every port on the antsle and cannot get a single one of them to work right. I can't ping the router from the Antsle's root, but when I ssh into an antlet, I can ping the router at 10.10.1.1. I can't ping the router from the Antsle's root, but when I ssh into an antlet, I can ping the router at service net.br0 returns started. I shouldn't be able to access it unless I can access the configuration from br0 first. I can still access my active antlet at 10.10.1.105. I set up br2 and it does get an ip address of 10.10.1.91 but still can't ssh into it or ping from the antsle to the router. Quote from odjhlofton on May 28, 2019, 6:55 service net.br0 returns started. You should have the same issue but I want to check there is no strange mapping going on.Ĭonfig_br0="192.168.1.201 netmask 255.255.0.0" They should all get separate IPs, try to ssh to each one. Maybe try to add the config for br1, br2 & br3 (like below), plug in some cables into them and reboot. I assume ` service net.br0 status` returns started? The only other note I caught is on shutdown I saw an error stating daemon service failed to stop-start. I'm really stumped as to why I can't access it. I checked the config of eth0 by running a ip addr command and it looks correct for br0. So I'm still stumped as to what it could be. However now that it's trying to use 10.10.1.90 instead of 10.10.1.183, I still can't ping the router and I tried running ifconfig eth0 and it states the device cannot be found. The only other note I caught is on shutdown I saw an error stating daemon service failed to changing to DHCP and during startup can tell that it pulled an ip as it showed green when using the DHCP service. ![]() ![]() Quote from odjhlofton on May 28, 2019, 5:04 changing to DHCP and during startup can tell that it pulled an ip as it showed green when using the DHCP service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |