Network Lock and Disconnect

[MersennePrime 1]

[newb alert]

​

​I thought that the Network Lock's function was the inhibition of any internet connection by software capable to do so 1) after the AirVPN was started but 2) had either lost or had not yet established any connection to one of the servers listed. 

​

​What happens is this (on my Win10-PC): After Eddie was started, I still connect to the internet with my IP address showing even with the Network Lock activated. Once I click "Connect to a recommended server", no connection can be established as long as a server hasn't been properly put into use. As soon as this has happened, my IP is indeed masked, as expected.

 

When I disconnect from a server, but still have Eddie running, my IP is, once again, showing up on the internet.

 

Is this how it's supposed to be? And if so, what is the Network Lock good for? If I disconnect without realising it, my privacy would be impaired. So, either something isn't working correctly, or I don't quite understand the function of the lock.

 

[/newb alert]

[go558a83nk 360]

are you using a firewall other than the one that's built into windows 10?

[MersennePrime 1]

are you using a firewall other than the one that's built into windows 10?

 

 

That was indeed the problem.

 

I had tried out AirVPN before and had tested the functionality with Windows Firewall and the older but quite formidable Private Firewall, and the Network Lock had worked fine. And I hadn't immediately realised that I had since then started to test the Total Security package of Bitdefender. And it was their firewall that ignored the Network Lock.

 

After deactivation, the lock did its work in collaboration with the Windows Firewall. No surprise there.

 

Now, I know far too well that 3rd party software firewalls are a mixed blessing at best, and more than a few are worse than no firewall at all.

 

But since it's such a hassle to finetune the Windows Firewall, I'll either go back to the well-tested Private Firewall or try out one of the software packages that add funtionality to the built in one.

 

I wonder if it's practical to add a user-updated list to the forum which includes the 3rd party firewalls that do and do not work with the Network Lock while using a specific OS? IMO, it's a key feature of the AirVPN client, and the impact of 3rd party tools is easily missed.

 

Anyway, thanks for the quick reply. The problem is solved.

[Staff 9922]

I wonder if it's practical to add a user-updated list to the forum which includes the 3rd party firewalls that do and do not work with the Network Lock while using a specific OS? IMO, it's a key feature of the AirVPN client, and the impact of 3rd party tools is easily missed.

 

 

Any system can't in general run two firewalls simultaneously. You would have two programs with high privileges competing to modify concurrently the OS network filtering table. This is obviously absurd and will lead to unpredictable behavior.

 

Running a firewall different than Windows Firewall is in several cases a bad idea on Windows 7 and later versions. You might enlarge the system surface attack not to mention potential and unwanted interference with various networking usages. Windows Firewall from Windows 7 and later versions has improved a lot and currently does packet filtering just like any other 3rd party tool.

 

Kind regards

[MersennePrime 1]

Any system can't in general run two firewalls simultaneously. (..) Running a firewall different than Windows Firewall is in several cases a bad idea on Windows 7 and later versions.

 

You are perfectly right. And my experience with the impact of one 3rd party tool on another is just one more example of the myriad of unintended consequences that happen in such an interdependent environment and that might impair privacy and security.

 

In any case, it's time to get out of Dodge and get rid of W10; it's just not possible to shut this OS up completely. But that's another story entirely.