- Joined
- Aug 20, 2006
- Messages
- 13,000
Came home to find that my VPN connection killed itself and my torrents were downloading through my real IP. Fuck that.
I figure the best way to prevent this in the future is kill all traffic in uTorrent if the VPN drops. I'm reading something about using Comodo to do this:
Does this sound like a good idea, or is there an even simpler way to handle this? Also, is it totally okay to run Comodo and the built-in Windows firewall simultaneously?
I figure the best way to prevent this in the future is kill all traffic in uTorrent if the VPN drops. I'm reading something about using Comodo to do this:
With Comodo, the procedure is simple and fast. When you connect to AirVPN, regardless of the server you're connected to, your TUN/TAP adapter is DHCP-assigned an IP address in the range specified by our Technical Specs page. https://airvpn.org/specs/
Therefore, in order to block a program to send out packets when you're not connected to Air, just block (for any program you wish) any outgoing packet NOT coming from range 10.4.0.0->10.9.255.255, from any port to any port. Comodo supports both IP ranges (without need of CIDR notation) and the NOT operator.
Open you Comodo control center, click on the tab "Firewall", select "Network Security Policy", click on the tab "Application Rules".
Detect the application you want to block when not connected to Air, or add it in the list through the "Browse" command, right-click on the application entry, select "Edit rule" (or "Add rule" if the application has no rules), and define the rule as you can see in the attached image. Leave "Source Port" and "Destination Port" to "Any".
Does this sound like a good idea, or is there an even simpler way to handle this? Also, is it totally okay to run Comodo and the built-in Windows firewall simultaneously?