Tracker using HTTP 301 wrong source IP used.

[Napsterbater]

Looks like Vuze (5.6.0.0/4 az2 per about) fails to use the bound IP when its connecting to a tracker it was refered to via a HTTP 301 from torrents defined tracker.

Torrent has  tracker.site.com as its tracker.

Vuze connect to tracker.site.com from its v6 bound IP correctly (tracker and vuze are dual stack, vuze has 1 IPv4 and 1 IPv6 bound).

tracker.site.com gives Vuze a HTTP 301 (Moved Permanently) to tracker01.site.com

Vuze connect to tracker01.site.com from the OS selected default source IP not from the bound IP as in the first request.

This cuases the tracker to get/use the wrong IP then as intended and setup with Firewall rules.


OS Windows Server 2012 r2 (I.E. Windows 8.1 Server)
Java Ver: 1.8.0_25 (64bit)
Vuze Ver:  5.6.0.0/4 az2

 

[parg]

Is this new behaviour? I don't think anything has changed in this area recently

[Napsterbater]

Is this new behaviour? I don't think anything has changed in this area recently

 

I dont know, I am just coming back to Vuze after a long time away.

This happens in both IPv4 and IPv6, just confirmed the same issue in IPv4.

Should be easy to test reproduce.

Set 2 IPs for IPv4 or v6 depending on the test at the time.

Bind Vuze to the IP that is not the default Java/OS selected source IP. Set a webserver (and DNS or host) up say tracker1.local.lan and set it up to host only HTTP 301 anwsers pointed at tracker2.local.lan and watch with wireshark.

One thing I noticed, Java (atleast on Windows) seem to pick a diffrenrt source IP then windows as its default.

For example all normal IPv4 traffic on this box is sourced from 10.0.1.1 yet Java uses 10.0.1.2 (10.0.1.1/2/5 are all configured on this system on that same interface)

But that dosnt change the fact of Vuze sourcing the 2nd connection from the "default" ip instead of the bound IP

 

[parg]

Please try 5601_B02 (join the beta program) - should be fixed although I didn't have a 301/302'ing tracker to test against

[Napsterbater]

Please try 5601_B02 (join the beta program) - should be fixed although I didn't have a 301/302'ing tracker to test against

 

Yep working as it should now, cant belive it was fixed that fast.

Thanks.