Public bug reported:

Binary package hint: azureus

Hours after Azureus (Vuze) is closed, I'm still getting incoming
connection attempts. Netstat doesn't show it, but both my router's logs
and wireshark do. The following is a wireshark capture about 5 hours
after I shut down azureus. "oms" is the port that I'm running it on
(4662) and it's forwarded to my computer. You can see it's using
TCP/UDP, however, the TCP is the only one that seems to be able to be
acknowledged.

No.     Time        Source                Destination           Protocol Info
      1 0.000000    76.101.124.129        192.168.1.102         TCP      
writesrv > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
      2 0.000124    192.168.1.102         76.101.124.129        TCP      oms > 
writesrv [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
      3 3.192542    76.101.124.129        192.168.1.102         TCP      
writesrv > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
      4 3.192591    192.168.1.102         76.101.124.129        TCP      oms > 
writesrv [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
      5 6.055616    76.101.124.129        192.168.1.102         TCP      
writesrv > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
      6 6.055667    192.168.1.102         76.101.124.129        TCP      oms > 
writesrv [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
      7 10.152410   76.101.124.129        192.168.1.102         TCP      
eicon-x25 > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
      8 10.152464   192.168.1.102         76.101.124.129        TCP      oms > 
eicon-x25 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
      9 11.691533   76.101.124.129        192.168.1.102         TCP      
eicon-x25 > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
     10 11.691586   192.168.1.102         76.101.124.129        TCP      oms > 
eicon-x25 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
     11 14.147625   76.101.124.129        192.168.1.102         TCP      
eicon-x25 > oms [SYN] Seq=0 Win=48180 Len=0 MSS=1452 WS=0
     12 14.147679   192.168.1.102         76.101.124.129        TCP      oms > 
eicon-x25 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
     15 18.139609   82.170.65.100         192.168.1.102         UDP      Source 
port: 27372  Destination port: oms
     16 18.139669   192.168.1.102         82.170.65.100         ICMP     
Destination unreachable (Port unreachable)
     19 27.151826   91.156.6.76           192.168.1.102         UDP      Source 
port: 34626  Destination port: oms
     20 27.151909   192.168.1.102         91.156.6.76           ICMP     
Destination unreachable (Port unreachable)
     21 27.151949   193.204.177.134       192.168.1.102         UDP      Source 
port: 61321  Destination port: oms
     22 27.151979   192.168.1.102         193.204.177.134       ICMP     
Destination unreachable (Port unreachable)
     23 27.152049   85.92.36.245          192.168.1.102         UDP      Source 
port: 59383  Destination port: oms
     24 27.152081   192.168.1.102         85.92.36.245          ICMP     
Destination unreachable (Port unreachable)
     25 27.152205   71.131.182.241        192.168.1.102         UDP      Source 
port: 28627  Destination port: oms
     26 27.152234   192.168.1.102         71.131.182.241        ICMP     
Destination unreachable (Port unreachable)
     27 30.121340   88.254.85.221         192.168.1.102         UDP      Source 
port: 45682  Destination port: oms
     28 30.121402   192.168.1.102         88.254.85.221         ICMP     
Destination unreachable (Port unreachable)
     29 35.532473   94.212.48.158         192.168.1.102         UDP      Source 
port: 54978  Destination port: oms
     30 35.532542   192.168.1.102         94.212.48.158         ICMP     
Destination unreachable (Port unreachable)
     31 36.965891   93.106.70.246         192.168.1.102         UDP      Source 
port: 50000  Destination port: oms
     32 36.965959   192.168.1.102         93.106.70.246         ICMP     
Destination unreachable (Port unreachable)


This is slowing my 3mb internet connection down to the equivalent of 56k. And 
it's not just my computer that's acting slow, everyone on my router is. The 
only way I've found to fix it is some combination of restarting my computer, 
router, & modem; most likely because I'm getting a new IP address.

My thoughts are that azureus isn't properly closing the torrent
connections. Can anyone testify to the same problem? When I start
azureus, though, all of my torrents have 0 seeds, 0 peers.

I'm using Azureus v3.1.1.0-3ubuntu3 from the repositories along with
sun-java v6-10-0ubuntu2 also from the repositories.

I'm on Intrepid and uname shows: 2.6.27-11-generic #1 SMP Thu Jan 15
11:03:58 UTC 2009 i686 GNU/Linux

Let me know if I need to include anything else.  Running azureus via the
terminal shows no useful information, and there isn't a debug option I
can find.

** Affects: azureus (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Getting incoming network connection attempts hours after Azureus is closed
https://bugs.launchpad.net/bugs/320330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to