Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vuze open udp port
#1
I had a total config crash and reinstalled 5300 > 5400 > 5401_b01 > 5401_b02
But now I see that Vuze open some dynamic udp ports (both tcpv4 & tcpv6) every time I start/restart!
The ports changes for every start/restart!
(seen this in both b01 & b02)

I have not installed any new plugins since the crash. (see pict for used plugins)
(I have failed to rule out wich one of the plugins that could be responsible for these ports!)

Running Vuze  behind a firewall/NAT net and need to redirect properly.

This is how netstat looks like:
C:\Users\Lina>netstat -noa | find "3060"
  TCP    0.0.0.0:8229           0.0.0.0:0              LISTENING       3060
  TCP    127.0.0.1:6880         0.0.0.0:0              LISTENING       3060
  TCP    127.0.0.1:36196        127.0.0.1:36197        ESTABLISHED     3060
  TCP    127.0.0.1:36197        127.0.0.1:36196        ESTABLISHED     3060
  TCP    127.0.0.1:36198        127.0.0.1:36199        ESTABLISHED     3060
  TCP    127.0.0.1:36199        127.0.0.1:36198        ESTABLISHED     3060
  TCP    127.0.0.1:36200        127.0.0.1:36201        ESTABLISHED     3060
  TCP    127.0.0.1:36201        127.0.0.1:36200        ESTABLISHED     3060
  TCP    127.0.0.1:45100        0.0.0.0:0              LISTENING       3060
  TCP    172.16.0.104:8229      xxx.xxx.xxx.xxx:5130   ESTABLISHED     3060
  TCP    172.16.0.104:8229      xxx.xxx.xxx.xxx:26551   ESTABLISHED     3060
  TCP    172.16.0.104:40953     xxx.xxx.xxx.xxx:80     LAST_ACK        3060
  TCP    [::]:8229              [::]:0                 LISTENING       3060
  UDP    0.0.0.0:8229           *:*                                    3060
  UDP    0.0.0.0:16680          *:*                                    3060
  UDP    0.0.0.0:49132          *:*                                    3060
  UDP    0.0.0.0:51044          *:*                                    3060
  UDP    0.0.0.0:52828          *:*                                    3060
  UDP    0.0.0.0:52830          *:*                                    3060
  UDP    0.0.0.0:52831          *:*                                    3060
  UDP    0.0.0.0:59007          *:*                                    3060
  UDP    0.0.0.0:60557          *:*                                    3060
  UDP    0.0.0.0:60561          *:*                                    3060
  UDP    0.0.0.0:63906          *:*                                    3060
  UDP    172.16.0.104:53295     *:*                                    3060
  UDP    [::]:8229              *:*                                    3060
  UDP    [::]:16680             *:*                                    3060
  UDP    [::]:49132             *:*                                    3060
  UDP    [::]:51044             *:*                                    3060
  UDP    [::]:52828             *:*                                    3060
  UDP    [::]:52830             *:*                                    3060
  UDP    [::]:52831             *:*                                    3060
  UDP    [::]:59007             *:*                                    3060
  UDP    [::]:60557             *:*                                    3060
  UDP    [::]:60561             *:*                                    3060
  UDP    [::]:63906             *:*                                    3060
**********************************************
8829 selected main port, 6880, 16880, 49132 & 53295 belongs to id-ed plugins.....the rest?

Java 1.7.0_65
 Oracle Corporation
SWT v4233, win32
Windows 7 v6.1, x86
V5.4.0.1_B02/4 az2

 

 

 


Attached Files Thumbnail(s)
   
Reply
#2
Hmm, that could be some new coded added in 5400 (I assume you saw this behaviour prior to 5401_B01 as nothing really changed there - if I am right this code was added a few months ago) that tries to grab peers from the DHT - it is a backup mechanism and the assumption was that any NAT devices general support for UDP temporary firewall 'holes' would be sufficient (unsolicited incoming UDP packets do not need to route).

You should only see one of these active though, not sure why you are seeing multiple ports - does the list continue to grow over time? 
Reply
#3
yes....

"I assume you saw this behaviour prior to 5401_B01"..........no, but it could have been soo!

I reverted back to 5301_b50 and no mIDHT.....voila! no "extra" ports unsed. (still using vuze v5000.exe as loader)

And I saw that the setting for mIDHT plugin refused to use the port selected, tons of tons firewall entries on default port 49001.
when i switched back to default I guess that i will have to live with all "channel" packets in the flow until they forget me?
 
Man! Didnt the creators of imDHT invent any way of removing users from the pool? After 12h I still recieve around five calls every minute!!
 

 

 

 
Reply
#4
testing 5401_b03 + miDHT

better but.....

Vuze open a listen port bound to localhost for something (think port opens right away early in the startup process)
and do not reuse that port eg reopen a new port all the time (not that good)

  TCP    127.0.0.1:54335        127.0.0.1:54336        ESTABLISHED     3628
  TCP    127.0.0.1:54336        127.0.0.1:54335        ESTABLISHED     3628
  TCP    127.0.0.1:54337        127.0.0.1:54338        ESTABLISHED     3628
  TCP    127.0.0.1:54338        127.0.0.1:54337        ESTABLISHED     3628
  TCP    127.0.0.1:54339        127.0.0.1:54340        ESTABLISHED     3628
  TCP    127.0.0.1:54340        127.0.0.1:54339        ESTABLISHED     3628
  TCP    127.0.0.1:54341        0.0.0.0:0              LISTENING       3628
  TCP    127.0.0.1:54341        127.0.0.1:36412        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36414        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36417        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36419        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36421        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36424        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36426        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36428        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36430        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36432        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36434        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36436        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36438        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36440        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36442        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36444        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36446        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36448        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36450        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36452        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36454        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36456        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36462        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36464        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36466        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36468        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36470        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36472        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36474        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36475        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36478        TIME_WAIT       0
  TCP    127.0.0.1:54341        127.0.0.1:36480        TIME_WAIT       0

pattern some minutes later...

 TCP    127.0.0.1:34392        127.0.0.1:34393        ESTABLISHED     3248
 TCP    127.0.0.1:34393        127.0.0.1:34392        ESTABLISHED     3248
 TCP    127.0.0.1:37107        127.0.0.1:54341        TIME_WAIT       0
 TCP    127.0.0.1:37109        127.0.0.1:54341        TIME_WAIT       0
 TCP    127.0.0.1:37116        127.0.0.1:54341        TIME_WAIT       0
 TCP    127.0.0.1:37120        127.0.0.1:54341        TIME_WAIT       0
 TCP    127.0.0.1:37122        127.0.0.1:54341        TIME_WAIT       0
 TCP    127.0.0.1:37126        127.0.0.1:54341        TIME_WAIT       0

the six first ports are ok (vuze componet traffic?) but the last use up ports quite fast...
guess this is miDHT?

 

 
Reply
#5
If they're TCP ports in a 'TIME_WAIT' then that means the connection has been closed by your computer and the network is waiting for a period of time to receive any stray packets that might arrive and cause confusion if the port is immediately reused.

Best bet would be that they are peer connections?
Reply
#6
no, they are not...

look at this line:
  TCP    127.0.0.1:54341        0.0.0.0:0              LISTENING       3628

see the port number? all the time_wait connections was from above connection.
TCP    127.0.0.1:54341        127.0.0.1:36419        TIME_WAIT       0

also the other way:  TCP    127.0.0.1:37107        127.0.0.1:54341        TIME_WAIT       0

can this be a pair like:
  TCP    127.0.0.1:54339        127.0.0.1:54340        ESTABLISHED     3628
  TCP    127.0.0.1:54340        127.0.0.1:54339        ESTABLISHED     3628
gone broken?
Reply
#7
5401_b03 w/o mlDHT is fine, no localhost interconnect trashing...

C:\Users\Lina>netstat -noa | find "2128"
  TCP    0.0.0.0:8229           0.0.0.0:0              LISTENING       2128
  TCP    127.0.0.1:6880         0.0.0.0:0              LISTENING       2128
  TCP    127.0.0.1:45100        0.0.0.0:0              LISTENING       2128
  TCP    127.0.0.1:49035        127.0.0.1:49036        ESTABLISHED     2128
  TCP    127.0.0.1:49036        127.0.0.1:49035        ESTABLISHED     2128
  TCP    127.0.0.1:49037        127.0.0.1:49038        ESTABLISHED     2128
  TCP    127.0.0.1:49038        127.0.0.1:49037        ESTABLISHED     2128
  TCP    127.0.0.1:49039        127.0.0.1:49040        ESTABLISHED     2128
  TCP    127.0.0.1:49040        127.0.0.1:49039        ESTABLISHED     2128
  TCP    172.16.0.104:8229      xxx.xxx.xxx.xxx:12001   SYN_RECEIVED    2128
  TCP    [::]:8229              [::]:0                 LISTENING       2128
  UDP    0.0.0.0:8229           *:*                                    2128
  UDP    0.0.0.0:16680          *:*                                    2128
  UDP    172.16.0.104:53295     *:*                                    2128
  UDP    [::]:8229              *:*                                    2128
  UDP    [::]:16680             *:*                                    2128
 
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Open Url not showing from clipboard -No Hash Processing NaPurHab 3 540 09-21-2016, 08:03 AM
Last Post: parg
  New version 5.7.2.0 Opens new instance on file open hjkaye@gmail.com 1 550 08-02-2016, 12:30 PM
Last Post: hjkaye@gmail.com



Users browsing this thread: 1 Guest(s)