Stuntard

OK so this is going to be a bit of a strange one. I have sabNZBd running in a Docker container on Unraid. No problems there, works great, maxes out my connection etc. My router is a Mikrotik RB5009 and my network is split up with VLANs, again everything works great. My problem is this....when I add a virtual ethernet interface to my bridge in my router, my speed in sabNZBd tanks hard.. and no one on the Mikrotik forums can tell me why. The funny thing is, is I can run the client on my Windows desktop..speed is fine.. I can run a speedtest on the same Unraid server, and the speed is fine. I can download using jDownloader or another client from inside a Docker container, and the speed is fine. But they second I add a VETH interface on my bridge on the router, speeds goes way down. The second I remove it, it goes back up again. The reason I am using the VETH interface on the router is that it is required to run containers on the router itself (I want to run Adguard on the router). There has to be some strange interaction between the docker container and the router somehow. The VETH interface isn't even on the same network subnet as my Unraid server, it just has to exist for the problem to appear.

I have this setup on my second NIC eth1 based of the information here UnRAID Network Settings Enable bonding: No Enable bridging: Yes IPv4 address assignment: None UnRAID Docker Settings (Example) - Use your own IP ranges. Subnet: 192.168.0.0/24 Gateway: 192.168.0.1 DHCP pool: 192.168.0.128/25 (128 hosts) I can get most of my docker containers working when set to the new br1 interface, but there's something messed up with WG-Easy. If I put container on br1, the port mappings on the docker page are blank. I can ping other containers on br1 from inside the WG container, including my Adguard container which is set to be the DNS server over Wireguard. If it put it back on my custom docker network I have all my other containers on, it all works again. My ultimate goal is to Use the second NIC to allow all my docker containers to communicate with eachother, and the internet as well as the Host. I want to be able to use Port 53 of Adguard for DNS, while still having port 53 free for Unraid to use for VMs. Is this even possible using 2 NICs without using VLANs? I have tried following But it is for an old version of Unraid, and the newer mentions But there is no information how to do it.

I'm not sure what is happening now. I can use dig @192.168.0.200 my.domain and it gives me the expected result (I have a DNS rewrite setup to change my domain name into my docker host's LAN IP (it's a different host machine than my Unraid Box). But if I use a browser when connected via Wireguard, the websites time out. I had all this working before I updated Unraid so I don't know what has happened. I have Caddy setup to bypass auth if the connection is coming from a whitelisted LAN ip, which it should do, as the rewrite seems to work, but only from a shell, not my browser. In fact, if i'm connected to my LAN via wireguard at all, I cannot access any of my machines via IP, apart from my Unraid box which is hosting Wireguard. As soon as I drop the wireguard connection, I can access things by IP again (I'm testing with my phone, but on Wi-Fi to LAN, and using Cell Data+Wireguard)

I have just come across this same problem since upgrading Unraid. I can't get Wireguard and Adguard to play along nicely any more, as I have to run Adguard on br0 to not conflict with port 53, which makes it unaccessible to Wireguard

I have just updated Unraid to 16.12.10 and my Adguard is completely screwed up. I get this if I set the container to use Bridge mode rc.docker: AdGuard-Home: Error response from daemon: driver failed programming external connectivity on endpoint AdGuard-Home (b1130b803c6a6733fe5d1ab1d7d7c4dd02456b6617146bd2646ed587fea9092d): Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use And if I use Host mode, for some reason the port mapping is 0.0.0.0:3000/TCP 0.0.0.0:3000 0.0.0.0:3000/UDP 0.0.0.0:3000 0.0.0.0:443/TCP 0.0.0.0:443 0.0.0.0:443/UDP 0.0.0.0:443 0.0.0.0:53/TCP 0.0.0.0:53 0.0.0.0:53/UDP 0.0.0.0:53 0.0.0.0:5443/TCP 0.0.0.0:5443 0.0.0.0:5443/UDP 0.0.0.0:5443 0.0.0.0:6060/TCP 0.0.0.0:6060 0.0.0.0:67/UDP 0.0.0.0:67 0.0.0.0:68/UDP 0.0.0.0:68 0.0.0.0:80/TCP 0.0.0.0:80 0.0.0.0:853/TCP 0.0.0.0:853 0.0.0.0:853/UDP 0.0.0.0:853 which breaks everything. The only port actually mapped in the config is 3000:3000 and 53:53 so I don't know where all the other port mappings are coming from.