SenorLoco

Bonding was already off but disabling my VMs did work....although not really an option.

Just pinging from another computer on the same network. I was poking around the wg0.conf and although I don't know enough claim to know what I'm doing it appears the issue is coming from the PostUp=iptables command. Just for giggles I commented out the post up/down and started wireguard and my custom ip dockers continued to work. tower-diagnostics-20191013-1633.zip

default via 192.168.1.1 dev br0 10.253.0.2 dev wg0 scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.10 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

I've tried multiple options for 'Peer type of access' if that is what you're referring to and it happens no matter what is selected. Actually I just deleted everything and setup a very basic server...just generated the keypair, applied changed and activated the server and as soon as I hit activate I was unable to ping a custom ip docker

I understand why wireguard clients could have problems connecting to dockers with a custom ip, but why would that behavior change for devices that are on the same LAN (not using wireguard). If I try to ping one of the dockers with a custom ip from within the LAN (from 192.168.1.160 -> 192.168.1.99) the ping times out, but with wireguard inactive the ping is fine.

I failed to be as specific as I should have...when wireguard is active I can't even access those dockers from my unraid server.

I'm not sure if I've got something configured wrong or if it is working as designed but wireguard is working fine and clients can connect without issue however when wireguard is active I am unable to access any dockers that have a custom ip address (Custom : br0). As soon as I deactivate wireguard those dockers are accessible. Do I have something setup wrong or will they not work together?