Search the Community

A question for the AIR staff or forum network experts: Does this solution work as effectively as the firewall rules? I wanted a simple and fast way to kill traffic if the VPN goes down on a WIn 7 machine. I came across set of instructions that implement two to three Windows batch files. In the example, 192.168.1.1 is the actual gateway address. To set protection once AIR VPN is up and running, right click on your prepared protect.bat file and run as admin: netsh int ip set address "Local Area Connection" static 192.168.1.101 255.255.255.0 192.168.222.1 If the tunnel drops out, there is no traffic of any kind since the gateway is a bogus address. To re-enable local network, right click on prepared enable_local.bat file and run as admin: netsh int ip set address "Local Area Connection" static 192.168.1.101 255.255.255.0 192.168.1.1 These commands are for a wired lan connection, the commands for a wireless connect are similar but slightly different. This has been working perfectly as far as I can tell - once the .bat file to protect is run as admin, checking "ipconfig" from the command window results in the bogus gateway as the default. Kill the VPN and traffic is halted right then. There are other details that could be put into a how-to, but I wanted to submit this as an alternative to the more complicated methods first to the staff/forum experts for review. Any reason not to use a method like this, other than it must be executed manually each time?