4 ms·
Most come with a killswitch, so if it wonks out you can't access the net.
by thejosh 5y ago
Most come with a killswitch, so if it wonks out you can't access the net.
- Semaphor 5y agoAre killswitches actually fast enough? Serious question, I don’t know much/anything about networking internals. I never trust killswitches and when I want to ensure I don’t leak anything, I bind to the VPN interface instead, but I don’t know if that actually gives better security?
- numpad0 5y agoSpeed should not be a problem and hardware solution should not have to be a better solution, ideally. Shame that has to be brought up still.
- shbooms 5y agoI've never used surfshark myself but they advertise as having a killswitch inlcluded in their VPN [0] so it sounds like in this case, it definitely failed. [0] https://surfshark.com/vpn#vpn-page-essentials https://surfshark.com/vpn#vpn-page-essentials
- deadbunny 5y agoJust setup your routes/firewall so that the only possible way traffic can leave your machine is via the VPN device. VPN dies? no traffic going anywhere. Pretty much networking 101 stuff.
- Semaphor 5y agoThat should be the same when bound to an interface, shouldn’t it?
- roastedpeacock 5y agoKill-switches are a misnomer. What you really want is a firewall external from your "target" system that blackholes all traffic not to the VPN gateways IP address. Than make sure packets traveling the parent interface are ONLY VPN traffic or nothing in case of the tunnel dropping (wireshark is good here.)
- NavinF 5y agoThat sounds like a race condition that gives you a false sense of security. It only takes one leaked packet…