Search the Community
Showing results for tags 'routing outside tunnel'.
Found 1 result
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: 220.127.116.11 (ipleak.net) 18.104.22.168 (doileak.com) 22.214.171.124 (ifconfig.co)