Vuze Forums

Vuze Forums > Vuze Desktop Client > Community Open Support > UDP trackers not working
Full Version: UDP trackers not working
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

jriker1

12-02-2016, 11:08 AM
Using Vuze Windows latest version with PIA proxy.  With slow or limited downloads, noticed in the sources, that all trackers that are udp:// based say:  Error: Offline - socks setup failed: Unknown host proxy-nl.privateinternetaccess.com The limited http trackers show online.  Is something setup wrong?  And should I even be looking at http based trackers to be fully secure or is that not relevant?
Thanks. JR

parg

12-02-2016, 11:20 AM
What does the SOCKS status show? Go to the Statistics view (Tools->Statistics) and select the Transfers tab - on the far right there's a SOCKs panel with a 'More...' link.

For reference on my machine I get the following when looking up that domain name:

C:\>nslookup proxy-nl.privateinternetaccess.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    proxy-nl.privateinternetaccess.com
Addresses:  46.166.186.228
          46.166.190.134
          109.201.154.130
          109.201.154.229
          109.201.154.235
          46.166.137.214
          46.166.137.196
          109.201.154.251
          46.166.190.160
          46.166.190.151
          46.166.137.193
          46.166.137.204
          46.166.190.144

jriker1

12-02-2016, 11:26 AM
Thanks for the reply, here is what I have in the SOCKS status.  Right now says OK and failed 9 hours ago.  Expanded info:



Code:
Proxy: proxy-nl.privateinternetaccess.com/46.166.190.133:1080
Last connection attempt: Fri Dec 02 12:23:07 CST 2016
Last failure: Fri Dec 02 03:13:54 CST 2016
Total connections: 1814
Total failures: 84

109.201.135.58
cons=490, last=Fri Dec 02 12:23:07 CST 2016
fails=3, last=Wed Nov 30 22:20:01 CST 2016
46.166.190.151
cons=32, last=Wed Nov 30 23:03:50 CST 2016
fails=3, last=Wed Nov 30 23:04:01 CST 2016
109.201.152.248
cons=122, last=Wed Nov 30 23:13:35 CST 2016
fails=3, last=Wed Nov 30 23:13:45 CST 2016
46.166.186.205
cons=8, last=Wed Nov 30 23:14:15 CST 2016
fails=4, last=Wed Nov 30 23:14:25 CST 2016
109.201.152.231
cons=421, last=Thu Dec 01 16:54:29 CST 2016
fails=3, last=Thu Dec 01 16:54:35 CST 2016
46.166.190.134
cons=10, last=Thu Dec 01 16:55:20 CST 2016
fails=3, last=Thu Dec 01 16:55:26 CST 2016
109.201.154.226
cons=22, last=Thu Dec 01 17:05:52 CST 2016
fails=3, last=Thu Dec 01 17:06:02 CST 2016
46.166.190.158
cons=7, last=Thu Dec 01 17:06:32 CST 2016
fails=3, last=Thu Dec 01 17:06:43 CST 2016
109.201.152.251
cons=93, last=Thu Dec 01 18:14:04 CST 2016
fails=3, last=Thu Dec 01 18:14:14 CST 2016
109.201.154.215
cons=84, last=Thu Dec 01 19:06:58 CST 2016
fails=3, last=Thu Dec 01 19:07:08 CST 2016
46.166.190.161
cons=6, last=Thu Dec 01 19:07:38 CST 2016
fails=3, last=Thu Dec 01 19:07:48 CST 2016
46.166.190.171
cons=6, last=Thu Dec 01 19:08:28 CST 2016
fails=3, last=Thu Dec 01 19:08:38 CST 2016
46.166.190.141
cons=8, last=Thu Dec 01 19:09:33 CST 2016
fails=3, last=Thu Dec 01 19:09:43 CST 2016
109.201.154.236
cons=11, last=Thu Dec 01 19:14:19 CST 2016
fails=3, last=Thu Dec 01 19:14:30 CST 2016
109.201.154.194
cons=54, last=Thu Dec 01 20:16:26 CST 2016
fails=3, last=Thu Dec 01 20:16:32 CST 2016
46.166.190.148
cons=7, last=Thu Dec 01 20:17:04 CST 2016
fails=3, last=Thu Dec 01 20:17:14 CST 2016
109.201.154.207
cons=31, last=Thu Dec 01 20:58:57 CST 2016
fails=3, last=Thu Dec 01 20:59:07 CST 2016
46.166.190.133
cons=17, last=Thu Dec 01 20:59:07 CST 2016
fails=4, last=Thu Dec 01 20:59:07 CST 2016
46.166.188.249
cons=72, last=Thu Dec 01 23:15:02 CST 2016
fails=4, last=Thu Dec 01 23:15:12 CST 2016
109.201.154.244
cons=38, last=Thu Dec 01 23:15:32 CST 2016
fails=4, last=Thu Dec 01 23:15:32 CST 2016
109.201.152.250
cons=106, last=Fri Dec 02 01:06:31 CST 2016
fails=4, last=Fri Dec 02 01:06:32 CST 2016
109.201.154.216
cons=51, last=Fri Dec 02 01:17:45 CST 2016
fails=4, last=Fri Dec 02 01:17:55 CST 2016
46.166.186.212
cons=25, last=Fri Dec 02 01:18:25 CST 2016
fails=4, last=Fri Dec 02 01:18:35 CST 2016
109.201.154.218
cons=46, last=Fri Dec 02 02:13:23 CST 2016
fails=4, last=Fri Dec 02 02:13:34 CST 2016
46.166.137.202
cons=47, last=Fri Dec 02 03:13:43 CST 2016
fails=4, last=Fri Dec 02 03:13:54 CST 2016

My lookup will automatically use my local DNS server but results seem the same:

Code:
Non-authoritative answer:
Name: proxy-nl.privateinternetaccess.com
Addresses: 109.201.154.134
109.201.154.229
46.166.188.248
109.201.138.227
109.201.154.243
109.201.154.219
109.201.154.173
109.201.154.221
109.201.152.234
109.201.154.218
46.166.186.201
46.166.137.216
46.166.190.160

Thanks.

JR

jriker1

12-04-2016, 03:16 PM
Further info from the weekend (not the musical group).  Turning off the proxy completely in Vuze, not all, but most of the UDP connections became "Online".  So either PIA doesn't support UPD thru proxy or Vuze doesn't.  Thoughts?

Thanks.

JR

parg

12-04-2016, 06:32 PM
Vuze should support UDP trackers - no idea about PIA.

Is there any particular reason you are using SOCKS instead of their VPN? SOCKS isn't very secure or reliable.

jriker1

12-04-2016, 07:58 PM
(12-04-2016, 06:32 PM)'parg' Wrote: [ -> ]Vuze should support UDP trackers - no idea about PIA.

Is there particular reason you are using SOCKS instead of their VPN? SOCKS isn't very secure or reliable.

 



Essentially because I run Vuze as a service on my Windows file share server and do not want my server running thru a VPN connection that I can't internally get to the system.  Or have to deal with how I'm going to force route ONLY the Vuze traffic thru the VPN and everything else not thru it.  Plus run VMWare instances on that system so would have to deal with routing those internally as well.  If there is a simple solve for this, glad to listen.

Thanks.

​JR

parg

12-04-2016, 08:33 PM
Running Vuze within a VM and using the VPN in that VM works well

jriker1

12-05-2016, 01:17 PM
(12-04-2016, 08:33 PM)'parg' Wrote: [ -> ]Running Vuze within a VM and using the VPN in that VM works well

 

Thanks.  I was thinking of virtualizing but since I think Vuze doesn't have a linux client, think I will try and get traffic splitting done using OpenVPN.  I say that because with four Windows VM's active already, hate to have another full Windows instance running taking resources.  Linux can run on a really small footprint for something like this but doesn't seem to be an option here.

Thanks.

jR

parg

12-05-2016, 02:01 PM
Vuze does have a linux client:

https://sourceforge.net/projects/azureus...2/download

Some distros have packages but unfortunately they have a tendancy to be out of date, and the way they like to use their own packaging approaches often breaks auto-update.

There can also be issues around the web-page based views (search and subscription results, although the latter is being worked on to use a native view).
Vuze Forums > Vuze Desktop Client > Community Open Support > UDP trackers not working