The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Setting up a VPN killswitch with firewall (Win 7)

    Discussion in 'Networking and Wireless' started by kelowna, Dec 5, 2016.

  1. kelowna

    kelowna Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Hey peeps,

    my VPN sometimes cuts out and I'd like to prevent that by setting up a killswitch with my firewall.

    I'm aware that this can be easily achieved either with Windows Firewall (instructions here) or Comodo Firewall ( here).

    The thing is that I'm currently using Symantec Endpoint Protection v. 12.1. with inbuilt Network Threat Protection which is the equivalent of a firewall. I believe I could fairly easily disable the Network Threat Protection part of that system, turn on the Windows Firewall and configure it to shut down my browser should my VPN disconnect, as per the instructions above.

    So the question #1 is: is it straightforward to just disable Symantec's firewall and turn on the Windows firewall, or do I need to worry about re-establishing a ton of rules and adjustments?

    And question #2: can the Symantec system be configured to attain the same goal? The user interface has a myriad of options for new firewall rules but no straightforward setting for Home/Public networks.

    I'm a novice when it comes to firewalls and I don't want to leave my system full of holes like a Swiss cheese.
     
  2. kelowna

    kelowna Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Okay so I just created a new firewall rule in Symantec Network Threat Protection's settings by
    • selecting "Intel Centrino Advanced N-6235" from the list of network adapters affected by the rule
    • blocking both inbound and outbound traffic
    • putting Firefox in the list of applications affected by that rule
    • applying rule to all hosts and all IP protocols (default option)
    My VPN TAP driver was in the same list of network adapters with said Intel Centrino network adapter, so I made the assumption that with the Intel network adapter blocked by the rule, all Firefox traffic would be routed through the VPN TAP driver. And in case the VPN would turn off... so would all traffic through Firefox.

    Surprisingly, this poor man's killswitch seems to work! All Firefox downloads and websites instantly freeze when I shut down my VPN. Now the only question is whether this is kosher (can it actually be this simple?) or is there some additional thing I should consider?
     
    Last edited: Dec 25, 2016