VLAN/Lan access
It should be possible to define routes which are not routed over the VPN. So currently my wifi devices are in a dedicated vlan, if I try to connect to a different vlan then with VPN on, its not possible.
Benjamin Hoffmann
shared this idea
-
Barbara Morrigan commented
i need it too
-
Pavel commented
I confirm.
1) Turning off KillSwitch because of Split Tunnel is simply wrong.
2) I also have two WireGuard VPNs on my office router, and whenever I switch to a different Wi-Fi AP on my laptop or connect a LAN cable, I lose the custom routes entered via "ip route add..."
The solution could be either to exclude the network in the split tunnel or to run a custom script after connecting to the protonPN network. I'm ancient because I remember the pre-Python era when protonVPN could handle this :-) -
Kike
commented
My home LAN is a type B IP network with 10 subnets. All devices connected to a specific subnet depending on its role and my security definitions. My router determines the allowed connections across subnets.
Today, Proton VPN's "Allow LAN Access" only allows access nodes inside my IP subnet.
I could solve the problem using split tunneling, but I use Kill Switch and Split Tunneling is not compatible with Kill Switch.Therefore I am forced to disable the VPN when I need to access another subnet.
Defining what static Nodes inside my B LAN construct can be accessed directly would allow me to work as I need to.
-
prototype
commented
Adding static routes should be done outside the VPN app. It is risky if you have a permanent static route when roaming and inadvertendly connect to devices in insecure networks.