torrent trackers fail under TB

[andre...@hotmail.com]

Hi all,

I can't get any torrent trackers to function while TB is on - OSX10.8.4, TB 3.3 (they're perpetually trying to update, but failing, and the torrent status is stuck on "Connecting to peers"). I've heard that no trackers work under VPN's, as a general rule, but I've also heard otherwise. All other internet connections work fine. Any ideas?

TB LOG: http://pastebin.com/qEx3Qqkb 

Config.ovpn: 

client

pull

dev tun

proto tcp

remote 184.154.116.157 443 #US,United States,Chicago,184.154.116.157,tcp,port 443,1,0

resolv-retry infinite

nobind

persist-key

persist-tun

mute-replay-warnings

ca ca.crt

cert client.crt

key client.key

ns-cert-type server

comp-lzo

verb 3

keepalive 5 28

route-delay 3

Related console lines: 

12/23/13 12:50:34.118 AM configd[18]: network changed: v4(en1:172.22.20.7) DNS! Proxy SMB

12/23/13 12:50:35.330 AM mDNSResponder[38]: SIGHUP: Purge cache

12/23/13 12:50:46.237 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: Entered

12/23/13 12:50:46.237 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: No active threads for connection 44096512

12/23/13 12:50:46.238 AM Tunnelblick[2575]: DEBUG: killAllConnectionsIncludingDaemons: has checked for active daemons

12/23/13 12:50:46.239 AM Tunnelblick[2575]: DEBUG: includeDaemons = 0; noUnknownOpenVPNsRunning = 1; noActiveDaemons = 1; noDownRootsActive = 1 

12/23/13 12:50:46.239 AM Tunnelblick[2575]: DEBUG: killAllConnectionsIncludingDaemons: will use killAll

12/23/13 12:50:46.240 AM Tunnelblick[2575]: DEBUG: killAllConnectionsIncludingDaemons: requested killAll

12/23/13 12:50:46.444 AM configd[18]: network changed: v4(en1:172.22.20.7) DNS! Proxy SMB

12/23/13 12:50:46.538 AM mDNSResponder[38]: SIGHUP: Purge cache

12/23/13 12:50:46.556 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: Entered

12/23/13 12:50:46.556 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: No active threads for connection 44096512

12/23/13 12:50:46.557 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: Entered

12/23/13 12:50:46.557 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: No active threads for connection 44096512

12/23/13 12:50:46.558 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: Entered

12/23/13 12:50:46.558 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: No active threads for connection 44096512

12/23/13 12:50:47.366 AM Tunnelblick[2575]: DEBUG: killAllConnectionsIncludingDaemons: killAll finished

12/23/13 12:50:47.368 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: Entered

12/23/13 12:50:47.368 AM Tunnelblick[2575]: DEBUG: cancelAllIPCheckThreadsForConnection: No active threads for connection 44096512

Thanks!

[jkbull...gmail.com]

Blocking torrent traffic is probably something that your VPN service provider, apparently securitykiss.com (or maybe "iPred") is doing, so you need to contact them.

Your "VPN service provider" is the organization which gave you your configuration files, and perhaps a username and password, and to which you are probably paying a fee for VPN service. For more information, please see  Getting VPN Service.

Tunnelblick is just the free software that many VPN service providers recommend or supply to their customers. We do not provide VPN service, just software.

My understanding is that different VPN service providers have different policies regarding torrent traffic -- some allow it and some don't.

Note: The log entries you posted (having to do with "cancelAllIPCheckThreadsForConnection" and "killAllConnectionsIncludingDaemons", are normal Tunnelblick messages having to do with disconnecting from a VPN.