September 26, 20214 yr Hello. Need help. Yesterday I was redoing some network cabling (disconnecting cable, restarting server etc) and today I can not access any of my dockers that run in bridge mode. I can access Plex and HomeAssistent that run in "Host" mode. I didnt do any changes to Unraid until it all stoped working at that point I upgraded Unraid from 6.8.2 to 6.9.2. Same effect, still can not access Rutorrent and Krusader. RuTorrent : 172.17.0.2:51413/TCP192.168.1.122:51413 172.17.0.2:6881/UDP192.168.1.122:6881 172.17.0.2:9090/TCP192.168.1.122:9090 Krusader: 172.17.0.5:6080/TCP192.168.1.122:6080 Both docker are running but I can not access WebUI. btw. I'm running pfsense as my router in "VM"
September 26, 20214 yr Author Just tried unplugging and plugging back network cable rebooting my two network switches. That didn't do anything. btw pfsense runs on 4 port network switch that is passed through to VM. tower-diagnostics-20210926-1155.zip tower-syslog-20210926-1554.zip
September 27, 20214 yr Author This is from Syslog. Can someone please explain whats all this entering blocking, forwarding, disabled state is : " Sep 26 21:03:32 Tower kernel: device vethbb043b0 entered promiscuous mode Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered disabled state Sep 26 21:03:33 Tower kernel: eth0: renamed from vethf963646 Sep 26 21:03:33 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbb043b0: link becomes ready Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:35 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface vethbb043b0.IPv6 with address fe80::c884:cbff:fe8f:fdb5. Sep 26 21:03:35 Tower avahi-daemon[4528]: New relevant interface vethbb043b0.IPv6 for mDNS. Sep 26 21:03:35 Tower avahi-daemon[4528]: Registering new address record for fe80::c884:cbff:fe8f:fdb5 on vethbb043b0.*. Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:24 Tower kernel: device veth929c61e entered promiscuous mode Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:25 Tower kernel: eth0: renamed from veth192b2ad Sep 26 21:07:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth929c61e: link becomes ready Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:26 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower avahi-daemon[4528]: New relevant interface veth929c61e.IPv6 for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Registering new address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.*. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: veth192b2ad: renamed from eth0 Sep 26 21:07:26 Tower avahi-daemon[4528]: Interface veth929c61e.IPv6 no longer relevant for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Leaving mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: device veth929c61e left promiscuous mode Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower avahi-daemon[4528]: Withdrawing address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.
September 27, 20214 yr Author Well... Looks like I'm slowly answering my questions. I'm able to access the dockers in question by changing the "Network Type" to br0 and assigning an unused ip address. Still don't know why bridge mode is not working when it did before.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.