Search the Community
Showing results for tags 'Windows Filtering Platform'.
Found 2 results
For a long time, I have been using the Network Lock in Windows Firewall mode. I read this guide from 2014 about the lock modes. Recently I updated the AirVPN client, and when I went to select the Network Lock mode, it notes that Windows Firewall is "(Not Recommended)". The other option is Windows Filtering Platform. Reading other websites, I see that the Windows Filtering Platform is an API by Microsoft that can help adjust filtering. I'm not a very technical person, but I get the gist. In the past when disengaging the Network Lock, in Windows Firewall mode, sometimes it would not properly replace my old firewall policies. I keep regular backups of them, so I usually just re-import them if there is an issue. Normally, I block a program with Windows Firewall rules from communicating over my normal connection... I plan when AirVPN network lock is active, the rule is removed, and it can communicate over the VPN. This has seemed to work for me to prevent the program from communicating if it is accidentally launched when AirVPN is not active -- though I see the problem if AirVPN accidentally shuts down and wipes firewall rules, it would communicate again... I am wondering with the Windows Filtering Platform, if my Windows Firewall rules are left intact, how should I go about managing this situation? Can I limit the program from communicating over my normal connection, but allow it to communicate over the VPN? How would I set this up in Windows Firewall? Again, I am not very technical and I have not used the Windows Filtering Platform option yet, so I am assuming this is the question I should have regarding the setup?... Or perhaps my question should be: What can I do to block a program from communicating over a non AirVPN connection, but allow it to communicate over the VPN, with Windows Filtering Platform as the network lock mode?
I've been having this problem for months now. I'm running Windows 7 and Windows 10 and use Bitdefender Internet Security on both machines. I want to be able to access certain websites outside of the VPN tunnel (so they see my real IP), but still force all other traffic through the VPN tunnel. To achieve this, I added the exceptions inside Eddie under Settings -> Routes. The problem is: they only work as long as I don't have network lock enabled. How do I know this? I'm testing these routes with sites like ipleak.net, doileak.com, ifconfig.co etc. As soon as I activate network lock, I can't access the sites I specified under "routes" anymore. I can ping them just fine, and run a traceroute command, but I can't access them inside any web browser. I also tried adding them under "allowed addresses" inside the "network lock" settings without any luck. I've been trying to solve this issue with staff for almost two months now, but without luck so far. It would be awesome if some of you could try to reproduce the same error, i.e. setting up these routes to see if you can access these sites while network lock is active. "Disclaimer": I'm using the "Windows Filtering Platform" method for network lock. (Which is the default method anyway as far as I'm aware) Everything is working just fine when I'm using the "Windows Firewall" method, even with network lock enabled. However, I don't want to rely on the Windows Firewall, so I'm using the firewall from Bitdefender Internet Security instead Any ideas or suggestions? Can any of you reproduce this same issue? Are any of you using another third party firewall that doesn't cause this issue? If so, which one? PS: Here are the IPs for some of the sites I used for testing so you can just copy and paste them if you want to test it for yourselves: 126.96.36.199 (ipleak.net) 188.8.131.52 (doileak.com) 184.108.40.206 (ifconfig.co)