I would look at routes and ruleset both before and after starting the gizmo: ip ro I don’t know Nordvpn, but if it does tamper with firewall too … I have seen setups where that (or equivalent) was not sufficient the initial local config had quirks that the VPN client failed to anticipate. That extra static route keeps the whole up.

Therefore, the machine must continue to send the packets of the VPN connection via “local internet”.Īt least one OpenVPN setup did actually create following routes: default via (GW2 in VPN) If it puts anything out from vp0, it will get those packets, encrypt them, and should send a packet to VPN server.

Now the question is: How does the VPN client continue to send packets to the VPN server?Īccording to routing table it should send to GW2 by tossing packets out from vp0. Link-local subnet (VPN): use interface (vp0) However, without the “split tunnel” the default route is changed to be someone in the VPN subnet (once known as “roadwarrior” config): default via (GW2 in VPN) Fine, you have two sets of neighbours: link-local subnet (VPN): use interface (vp0) The VPN offers a new interface and subnet behind it. toss out from em1 (unless the VPN server is in the link-local subnet …) It must use the routes above:įorward to GW, i.e. Now your VPN client establishes connection to VPN server. Link-local subnet (LAN): use interface (em1) We do know that in default (one interface) setup the routing table looks like: default via (GW in LAN)

Nordvpn linux install