Stop uTorrent when VPN connection lost

I just started using BolehVPN, and am trying to make my uTorrent connect to the internet only through the VPN., and to cut off all torrents if I lose Boleh. I am using Windows 7 Ultimate, SP 1, 32 bit, and Comodo Firewall with Defender +, v. 5.8.213334.2131. My antivirus is avgfree. I am using uTorrent 2.2.1 (build 25110). Please forgive the number of attachments—I hope that they contain relevant information to diagnose and solve this problem.

My uTorrent rules are shown in the attached “3 rules for utorrent”, and my global rules are in the attached “Comodo Global”.

Now, if I try to start uTorrent with Boleh disconnected, no connections are made with Peers/Seeds, which is what I want.

When I connect to Boleh first, and then start uTorrent, I get a lot of connections, as I want (see attached “utorrent opened after boleh opened”).

When I then disconnect Boleh, the number of Seeds/peer connections starts to drop, and gets very low, and the download rate is 0 (see attached “initial Boleh disconnect”).

However, after a while, uTorrent starts reconnecting to Seeds/Peers, and downloading from them (see “reconnect later”), which is decidedly weird.

Also, when I then exit uTorrent, the application closes, but after even a while, Task Manager shows uTorrent.exe still in Processes, and still listening. If I right-click uTorrent and end the process, it does so, and stops listening.

I am totally confused! What can I do to fix this? If you need me to run and post some logs, please let me know.

TIA

[attachment deleted by admin]

Those connections are IPv6 tunnel connections, specifically Teredo tunnel connections, which will bypass the VPN. Unless your VPN provider specifically supports IPv6 traffic, I suggest you do one or two things:

  1. Disable IPv6 in uTorrent (Preferences/General)

and/or - This is better

  1. Disable IPv6 in uTorrent and apply the following at a command prompt: (just copy and paste)

netsh interface ipv6 set privacy state=disable
netsh interface ipv6 6to4 set state state=disabled
netsh interface ipv6 isatap set state state=disabled
netsh interface ipv6 set teredo disabled

This will disable all IPv6 tunnelling interfaces on Windows 7, which unless you specifically need IPv6, for now, is a better option. These changes are reversible and you won’t loose out by disabling these interfaces.

Also, when I then exit uTorrent, the application closes, but after even a while, Task Manager shows uTorrent.exe still in Processes, and still listening. If I right-click uTorrent and end the process, it does so, and stops listening.

The default setting when closing uTorrent is to minimise it to the system tray. Check under Preferences/UI Settings.

When a process is in a ‘Listening’ state it simply means it’s waiting for something to happen, it doesn’t mean it’s doing anything. Unless you completely close the application, thus terminating the connection, it will continue to listen.

Thanks, Radaghast, for your detailed response.

However, IPV6 is greyed out on Preferences (General)–see attachment.

Would this imply that it is not available in the version of uTorrent I’m running?

[attachment deleted by admin]

It’s greyed out because you’re probably running Windows 7, where it’s enabled by default. Open a command prompt and type ipconfig /all. look towards the bottom of the output for something that says:

Tunnel adapter Teredo Tunneling Pseudo-Interface:

See if there’s an address that begins with 2001:0:

Yes, I am running win 7, there is the address beginning with 2001:0.

So, how do I turn it off in uTorrent as you recommended, given that it is greyed out?

In this case, you don’t need to do anything in uTorrent, just run the netsh commands I listed above and make sure, once run, you don’t re-enable Teredo by selecting that button in uTorrent.

I did what you said, and all but the 2nd “disabled” worked–it said “A device attached to the system is not functioning.” Anyway, I started the vpn, started utorrent, it picked up a lot of peers/seeds and started downloading. I cut off the vpn, and in the utorrent screen, the download rate dropped to nothing and disappeared, and the number of peers and seeds also dropped to 0. At that time, about 10% of the file had been downloaded. uTorrent was still running, but not showing anything being downloaded.

The weird thing is that a while later, when I looked at the utorrent screen, it showed that the download was completed, and when I looked at the hard drive, the file was there in full. So somehow, utorrent kept downloading despite the fact that it did not show that it was doing so.

Boy am I confused–feel like Schrödinger’s cat!

The second netsh command disables 6to4 tunnels. It’s possible the tunnel interface wasn’t enabled on your system. Post the results of an ipconfig /all and we can see.

The weird thing is that a while later, when I looked at the utorrent screen, it showed that the download was completed, and when I looked at the hard drive, the file was there in full. So somehow, utorrent kept downloading despite the fact that it did not show that it was doing so.

Boy am I confused–feel like Schrödinger’s cat!

Impossible to say what may have happened without more information. I can only suggest running another test and keeping a close eye on the connections, to and from your PC. It might be worth downloading Wireshark and letting it run for the duration. Another, more simple, option is CurrPorts. With this you can enable logging from the file menu and there’s a list of parameters you can use on the home page.

Hi Radaghast:

Attached is the ipconfig result.

I’ll run CurrPorts later when I don’t need the computer.

Thanks

[attachment deleted by admin]

The ipconfig still shows your system running two tunnelling interfaces, so it appears that when you ran the netsh commands I listed above, something failed. May I suggest running the two commands below, this time run them individually:

netsh interface ipv6 isatap set state state=disabled
netsh interface ipv6 set teredo disabled

After running these, post another ipconfig.

Here it is

[attachment deleted by admin]

Unfortunately, the command didn’t run correctly, please try again.

Error: unrecognized or incomplete command line.

Sorry. I should’ve checked.

[attachment deleted by admin]

That’s better, you’ve ‘shut-down’ the IPv6 tunnelling interfaces and you don’t appear to have native IPv6, so I suggest you run your test again and see what happens.

Thanks, Radaghast, I think that did the trick!