mF2C/vpn

vpn client container can't update host's routing table

Closed this issue · 1 comments

As the vpn client now runs its network in host mode, it takes over the host's network. However, @flordan reports loss of connectivity seemingly due to a permissions problem where the vpn client is not allowed to alter the host's routing table.

Turns out routing was OK but the resolv.conf on the host was not updated. However, server now implements a fix by having the client not route all traffic over the VPN.