Unraid using WG0 instead eth0

[Thrathius]

Having an issue where unraid has just decided that WG0 is its primary nic and now is only accessible if that vpn connection is on and active, anyone run into this or know the fix?

[ljm42]

Not a lot to go on here, but perhaps WG0 is setup as "VPN tunneled access for system"? Assuming you are on a recent version of Unraid, there is a “VPN tunneled access for docker” that you probably want instead. see https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/ 

 

[Thrathius]

It will also do the same for wg1, if i turn the tunnel off my public IP goes back to normal for the server via terminal curl ifconfig.me

[Thrathius]

On 2/24/2023 at 5:30 PM, ljm42 said:

Not a lot to go on here, but perhaps WG0 is setup as "VPN tunneled access for system"? Assuming you are on a recent version of Unraid, there is a “VPN tunneled access for docker” that you probably want instead. see https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/ 

 

It is configured as tunneled access for docker

[Thrathius]

So it would appear that my unraid server is tunneling itself along side any dockers for the tunnel. Not sure why or how.

[Naidu]

Hello,

 

I just ran into this issue how did you resolve it?

[Thrathius]

Unfortunately no, my work around was I installed another nic that routes through an openwrt with a VPN tunnel and only select dockers operate on it. 

I tried different routing rules, vlans, etc. This was the only thing that worked and I sometimes still have to reset the other nic connection because unraid tries to use it randomly as it's primary.