Kill Switch if PIA Client Fails?

I know the PIA client has a kill switch built in, but there are two issues with this.

First, the Windows PIA client takes longer to start up than everything else on boot, so my real IP is exposed until the client actually starts up. My workaround is to disable automatically connecting to any wireless network; I wait for the PIA client to load, then manually connect to my wireless network because the kill switch is already active. I can't think of a workaround for a cabled ethernet connection, though, and I need to use that as well on another machine.

Second, if the PIA client application crashes while I'm not present, then there's no more kill switch feature either, and again my real IP is exposed.

My question is: is there a way to setup Windows Firewall, or some other option, in order to block ALL incoming and outgoing traffic when the client is running, or some other such setup so unless I'm actually connected to the VPN, there will be no connection of any kind? I know it's possible to set up the VPN on a router, but this isn't an option for me, especially when I'm on the go.

Comments

  • There are suggestions for windows firewall rules.
    Personally, i disable the 'obtain ip address automatically' (dhcp) in network adapter settings so no default route is added for internet access at anytime. On startup i have a script which starts pia, copies and adds route to a pia server ip (found in pia/data/region_data), and once connected it adds the default route via the tunnel for internet access.
Sign In or Register to comment.