January 8, 20206 yr Today I have several dockers on br0.10 including plex and emby. I have several dockers on bridge, including deluge, nzbget, sonarr, couch potato. I would like to move the dockers from bridge to br0.10. When I do this, they kind of work. I can get to their web interfaces, they can get to the internet, but sonarr cannot get to deluge or nzb. I can open a bash in the sonarr docker and ping the br0.10 ip for deluge, but for whatever reason sonarr cannot find deluge. This obviously breaks everything. Is there something I have to do differently with the br0.10 setup to get this to work? Currently I have plex and emby on br0.10 because that is the vlan my TV/nvidia shild is on and it makes network traffic a bit better. However, sonarr and couch potato cannot notify them of updates as they are on bridge. Is this even possible? Does my question make sense? thanks david
January 9, 20206 yr Author I just tried using br0.0, thinking it would help since it is just the 192.168.1.0 net, which is what the Tower belongs to, but no go. It cannot ping the tower IP either, but can ping everything else. david
January 16, 20206 yr On 1/8/2020 at 11:46 PM, lovingHDTV said: Is this even possible? Docker does not allow different networks to talk to each other. If you want containers to communicate then they all need to be on the same network. In your case br0.10.
January 16, 20206 yr Author I put 5 (sonarr, nzbget, deluge, plex, emby) dockers all on the same network br0.10. But when I do that they cannot talk to each other. That is the gist of the problem. If they are all on bridge they work. david
January 16, 20206 yr When these containers are on the network br0.10 they all get a unique IP address. You need to make sure in the applications that the correct reference to these IP addresses is done.
January 16, 20206 yr Author Yes, I did that. I actually set the IPs in the docker setup so I know them. Edited January 16, 20206 yr by lovingHDTV
January 16, 20206 yr 1 minute ago, lovingHDTV said: Yes, I did that. I actually set the IPs in the docker setup so I know them. That is one part, but you need to change the settings inside the applications too, to match the new set up.
January 16, 20206 yr Author Yes, in sonarr for example, I change Plex's IP to the new one for notifications. I hit test and it cannot find plex. I moved it all back, change all the IPs in docker and applications and it works. Which is why I statically set the IP in the docker setup, so I know how to set them in each application. david
January 16, 20206 yr When you open a console window for sonarr (click on its name and choose 'console'). Can you ping the IP address of Plex? I am not using sonar, but here is an example of Tautilli. I open its console and ping plex Talking about Plex ... Under network settings of Plex you can specify which IP addresses are allowed without authentication. You can specify here the sonarr IP address (or complete network subnet) Edited January 16, 20206 yr by bonienl
January 16, 20206 yr Author Ok, set it back up. I can ping plex and can notify plex, so I was mistaken there. I then tried nzbgetvpn and delugevpn and I can ping them also, but cannot connect. It is making me wonder if the routing within the docker is handling the LAN setting correctly. Here are the routes in delugevpn, they look OK to me, but I'm not an expert: sh-5.0# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.21.90.1 128.0.0.0 UG 0 0 0 tun0 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 128.0.0.0 172.21.90.1 128.0.0.0 UG 0 0 0 tun0 172.21.90.0 0.0.0.0 255.255.254.0 U 0 0 0 tun0 173.245.203.252 192.168.10.1 255.255.255.255 UGH 0 0 0 eth0 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 Here they are in sonarr: sh-5.0# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 routes for nzbget when on bridge: (this works with Sonarr on bridge) sh-5.0# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.21.90.1 128.0.0.0 UG 0 0 0 tun0 0.0.0.0 172.17.0.1 0.0.0.0 UG 0 0 0 eth0 128.0.0.0 172.21.90.1 128.0.0.0 UG 0 0 0 tun0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 172.21.90.0 0.0.0.0 255.255.254.0 U 0 0 0 tun0 192.168.1.0 172.17.0.1 255.255.255.0 UG 0 0 0 eth0 209.197.16.148 172.17.0.1 255.255.255.255 UGH 0 0 0 eth0 Edited January 16, 20206 yr by lovingHDTV
January 16, 20206 yr 1 hour ago, lovingHDTV said: It is making me wonder if the routing within the docker is handling the LAN setting correctly. If ping succeeds, routing is okay. A connection failure is at a higher level (beyond network)
January 17, 20206 yr Author Played a bit more. 1. installed linuxserver nzbget (as it doesn't integrate VPN). This worked fine. 2. with nzbgetvpn - I can ping it, but if I do a curl command it times out I can successfully run the curl command from my PC on the 192.168.1.0/24 subnet so my router is routing to the docker. I cannot ping the br0.10 docker from a tower command prompt. The tower is on the 192.168.1.0/24 subnet also. something is amiss and I can't figure it out. david
January 17, 20206 yr Author In case this helps. some additional routing information for nzbgetvpn. sh-5.0# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.52 netmask 255.255.255.0 broadcast 192.168.10.255 ether 02:42:c0:a8:0a:34 txqueuelen 0 (Ethernet) RX packets 2744 bytes 689060 (672.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1374 bytes 799401 (780.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 35 bytes 148888 (145.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 148888 (145.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.21.90.31 netmask 255.255.254.0 destination 172.21.90.31 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 12 bytes 950 (950.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 852 (852.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sh-5.0# iptables --list Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- 192.168.10.0/24 192.168.10.0/24 ACCEPT udp -- anywhere anywhere udp spt:openvpn ACCEPT tcp -- anywhere anywhere tcp dpt:radg ACCEPT tcp -- anywhere anywhere tcp spt:radg ACCEPT tcp -- 192.168.10.0/24 anywhere tcp dpt:radg ACCEPT icmp -- anywhere anywhere icmp echo-reply ACCEPT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- 192.168.10.0/24 192.168.10.0/24 ACCEPT udp -- anywhere anywhere udp dpt:openvpn ACCEPT tcp -- anywhere anywhere tcp dpt:radg ACCEPT tcp -- anywhere anywhere tcp spt:radg ACCEPT tcp -- anywhere 192.168.10.0/24 tcp spt:radg ACCEPT icmp -- anywhere anywhere icmp echo-request ACCEPT all -- anywhere anywhere
January 18, 20206 yr Author Played a bit more. It doesn't have anything to do with br0.10 as it doesn't work for br0 either. david
Archived
This topic is now archived and is closed to further replies.