Network lock, qBittorrent and Windows Security Alert

[nestegg101 3]

I have installed a few torrent clients to test but Network lock seems to be related to an anomaly in my qBittorrent setup. With Network Lock Deactivated, all clients work normally (all are allowed in the original Windows Firewall ruleset). With Network Lock Activated, the first time qBittorrent is run, I get a Windows Security Alert asking whether to allow qBittorrent to run. Regardless of whether I click Allow or Cancel, rules blocking qBittorrent would be added like this:

 

 

I would like to find out why:

 

1. Only qBittorrent will trigger a Windows Security Alert on first run. Other torrent clients do not trigger any Windows Security Alerts at all even though they are not listed in the AirVPN ruleset.

 

2. Regardless whether I click allow or cancel the Windows Security Alert popup, rules blocking qBittorrent still get added.

 

Thanks.

 

 

[rainmakerraw 94]

Yeah I get this too. I don't know if it's an Eddie/network lock thing or a qBittorrent thing. I'd imagine it's actually the latter, so might be worth checking their forum. It does the same on OS X with or without Eddie installed, to the point where I disabled OS X's firewall (pf) and installed HandsOff instead. 

[nestegg101 3]

Yeah I get this too. I don't know if it's an Eddie/network lock thing or a qBittorrent thing. I'd imagine it's actually the latter, so might be worth checking their forum. It does the same on OS X with or without Eddie installed, to the point where I disabled OS X's firewall (pf) and installed HandsOff instead. 

 

How do you manage it in Windows? Do you have to unblock the blocking rules created each time on qBittorrent's first run before you can continue use it for that session (till the next network unlock/lock cycle)?

[eyes878 43]

I get this on all programs when they start and I have Network Lock enabled. Clicking cancel doesn't stop the program from working and seems like it would prevent the program from possibly circumventing the firewall, but don't quote me on that last sentence, neither of the options seem to make a difference.

[nestegg101 3]

I get this on all programs when they start and I have Network Lock enabled. Clicking cancel doesn't stop the program from working and seems like it would prevent the program from possibly circumventing the firewall, but don't quote me on that last sentence, neither of the options seem to make a difference.

For my case, both allow and cancel do the same thing: create block rules. Oddly, not all programs trigger a firewall alert.