adamfritzsche

This was my issue. The tailscale plugin. Did not associate it with this as I had TS running for weeks now without issue. Just so happens I have not restarted the docker service or unraid since then.

I setup a new instance of unraid and the br0 and assigning an ip to the SWAG docker works as expected. So something somewhere is dorked up with my unraid instance. Is there a safe way to wipe my network settings replacing them with "clean" settings?

I had attempted to try a community docker app out, "matter-server" container by digiblur and it specifies having to have ipv6 enabled whether or not you actually use it. So I enabled it, but quickly noticed that my SWAG container stopped working. This container I have on br0 so that I can assign an IP address within my local network range. I have found that the container will can no longer reach the internet to grab all the docker mods it is using and has some other errors as well due to not not being able to get to the internet. I have put the network back to IPv4 only and the issue persists. I can switch the container to any other network type be it bridge, host, or a custom docker network and it will work just fine. Any ideas?

Any further ideas on why this is happening?

Right. That is how I had it for years, no issue. All of a sudden dockers will not communicate with each other using the Host IP and I fail to understand why. I can and do access these dockers via the host ip and corresponding port from anywhere else, except another docker. This was my previous setup, which no longer works. Now to get them to work I have to use this, which is problematic.

Yes, most of them are using bridge.

Any other advice on this? It is rather frustrating. Using the 172.* subnet works, but the ip's for the dockers on this subnet are not static, so I am constantly having breaks in the communication between dockers and have to go into them and change the ip's around when they end up changing at random.

A few months ago out of the blue my docker containers were unable to communicate between each other using the local subnet I am using (192.168.1.0/24). I can reach them via any other device on the subnet no problem. After a large struggle, I found that they will communicate via the docker subnet? (172.17.0.XXX). This provided an immediate solution but not an answer to what happened as I have had this setup for several years without issue. The issue using the docker subnet (or whatever it is actually referred to) is that the IP changes randomly and then I have to go through a bunch of dockers to reflect these changes. Any ideas to a solution, one way or another?

Ah, yes. That makes sense. Thank you.

Okay, so I have a dumb question. I have pfSense as a VM in unRaid. I have a quad Intel nic passed through to the VM. Port Designated WAN goes to cable modem, LAN goes to switch, which then goes to all my wired devices and wireless AP's. One of these ports on the switch goes back to the unRaid server onboard nic, which is used to give unRaid network access. This all works great until I restart the unRaid Machine. Obviously, unRaid starts before the pfSense VM can, resulting in the unRaid machine getting assigned a 169.xxx.xxx.xxx address which then results in not being able to access unRaid, have to put the old router back in place to get access again. Am I missing something? / Is there a way to resolve this?