tnerb

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated. They are. You sure you not got something going on at the router level? Or any other openvpn plugin? Spent some time this morning confirming I don't have anything else connecting to OpenVPN in the network. If I stop the transmission-openvpn docker then duckdns updates the correct external IP. Setting the duckdns docker to Host and Privileged does nothing. This is very confusing to me. Host mode won't do anything. That's only for incoming connections. You can exec into the container and do traceroute to confirm but it's most definitely an issue with openvpn. Nothing we can do in the duckdns side Thanks a lot for looking into it and responding. I'll have to do some more digging. I'll look into what you suggested with the traceroute.

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated. They are. You sure you not got something going on at the router level? Or any other openvpn plugin? Spent some time this morning confirming I don't have anything else connecting to OpenVPN in the network. If I stop the transmission-openvpn docker then duckdns updates the correct external IP. Setting the duckdns docker to Host and Privileged does nothing. This is very confusing to me.

I agree it does appear that way. Not sure how that is happening... I thought dockers were separated.

Where does the docker get the IP from? I'm having an issue where it is grabbing the IP used by my VPN service (PIA) that i connect with my transmission-openvpn docker to. If I stop the transmission-openvpn docker the duckdns docker updates the duckdns.org service with my outward facing IP. Any thoughts how I can run the duckdns docker to update with my IP (not the PIA ip)? I've tried running it as a host and bridge network type.