I have my Xibo server set up in my local office (“Office A”), and it is running without any problems at all. I have a player set up in a remote office (“Office B”). The player in Office B refuses to connect to the server. Troubleshooting led to the fact that no computer within Office B will connect to the server in Office A, even though they will connect to any other authorized destination within the network in Office A. My head has almost exploded with trying to find out why this might be; there are NO blocks in place in either Office A or Office B that would stop communication with a specific IP and not any others.
As a side note of some significance, I need to point out that I am using 172.20.0.0/24 in Office B, with 172.20.0.1 being the gateway. Office A uses 172.17.1.0/24.
After much tail chasing to no avail, I finally, out of desperation, logged in to my Linux server to see if I could ping from Office A to Office B. Before I actually tried the ping, however, I did ifconfig on a whim, where I found this:
br-610d8954f4eb Link encap:Ethernet HWaddr 02:42:fe:54:5b:1f
inet addr:172.20.0.1 Bcast:172.20.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:feff:fe54:5b1f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1229263 errors:0 dropped:0 overruns:0 frame:0
TX packets:1245832 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6958679062 (6.9 GB) TX bytes:454071718 (454.0 MB)
docker0 Link encap:Ethernet HWaddr 02:42:23:ba:69:59
inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:15:5d:01:de:04
inet addr:172.17.1.250 Bcast:172.17.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:5dff:fe01:de04/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43956617 errors:0 dropped:876392 overruns:0 frame:0
TX packets:2609225 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4034068179 (4.0 GB) TX bytes:6060750487 (6.0 GB)
As you can see, the bridge is configured to use the same exact IP as the gateway in Office B. I am positive that this is what is causing my lack of communication, but I am completely clueless how I might fix it, and I’m hoping that someone can guide me.
I would like to point out that I have done some investigation into this issue. Docker Docs has this:
https://docs.docker.com/v17.09/engine/userguide/networking/default_network/custom-docker0/
I can create the daemon.json file mentioned in the above doc, and I can populate it, but I’m not sure exactly what to enter there, which is the majority of the reason I’m asking for assistance. I know my network information required in the bottom part of the sample given, but does it matter what I put in place for the bip and fixed-cidr in the first part?
{
"bip": "192.168.1.5/24",
"fixed-cidr": "192.168.1.5/25",
"fixed-cidr-v6": "2001:db8::/64",
"mtu": 1500,
"default-gateway": "10.20.1.1",
"default-gateway-v6": "2001:db8:abcd::89",
"dns": ["10.20.1.2","10.20.1.3"]
}
The default-gateway and dns lines will be my Office A information, which I know well, but I don’t want to break the internal communication by assigning a subnet that differs wildly from that of docker0, but I don’t see anything that specifies whether this is a concern or not.
Thank you in advance!