This question is actually similar than the post about allowing LAN-traffic a few posts down, and I have been experimenting that way… with varying results (I don’t understand them actually).
I want to run utorrent over a pptp vpn-connection. At each new-connect a random subnet ip is handed out, so I cannot work with ip numbers, i think (not sure). I’ve tried to define a zone for this vpn, both by adding dns-suffix to the connection and by using the address in the dial-up connection and than defining a rule as in the other post excluding all non-vpn trafiic, one rule for outgoing and one for incoming
like block/IP/in/any/zone or hostname (tried both) and the exclude ticked/any
and block/IP/out/zone or hostname (tried both) and the exclude ticked/any/any
I ticked event-writing for these new rules and after starting up utorrent blocking events appear, at the same time certain connections are actually established (and are visible in the connections), because utorrent traffic does not grind to a hold? So I end up with connections blocked that are similar to connections established, that’s the part I don’t get. Maybe this exclude has an effect on the other settings like ports, I don’t know.
Just for clarity, without these rules things work as they should, the setup is along the lines of the recommended setting in the relevant thread elsewhere on this forum.
The objective is to not allow connection over the normal internet connection in case the vpn drops and windows reverts back to default connection.
Maybe somebody has tried this and come up with a solution?
PS: one thing that does work is to define my home network as a zone and stuff it in the blocked zones, but that’s a bit over the top and not always very handy.