Deluge Forum

Hi all

I am running Deluge 1.3.0 on linux. I have configured my network setup to use one dedicated incoming port (2323) and my router forwards this port. I have the scheduler enabled to only download at night. My problem is during the day when Deluge is idle my box is sending and receiving a LOT of UDP traffic on port 2323. Do you have any idea why this is happening? Here is a tcpdump snippet:

-----
09:52:48.355523 IP 192.168.0.2.2323 > 196.215.93.108.54124: UDP, length 101
09:52:48.565287 IP 196.215.93.108.54124 > 192.168.0.2.2323: UDP, length 275
09:52:48.565393 IP 192.168.0.2.2323 > 207.210.53.221.49837: UDP, length 101
09:52:52.359522 IP 192.168.0.2.2323 > 222.188.160.197.16001: UDP, length 101
09:52:53.067203 IP 222.188.160.197.16001 > 192.168.0.2.2323: UDP, length 266
09:52:53.067464 IP 192.168.0.2.2323 > 173.32.181.8.29627: UDP, length 101
09:52:53.072786 IP 222.188.160.197.16001 > 192.168.0.2.2323: UDP, length 62
09:52:53.072863 IP 192.168.0.2.2323 > 222.188.160.197.16001: UDP, length 62
09:52:53.363505 IP 192.168.0.2.2323 > 82.193.140.164.64614: UDP, length 101
09:52:53.363549 IP 192.168.0.2.2323 > 178.59.96.238.29717: UDP, length 101
-----

Thanks!
mono

Are you sure that the port in question isn't being used by anything else. This is the main reason why it is usually suggested to pick a port above the 6881 range, hopefully well above ones that are specified for a specific service. Another thought would be it isn't doing any transferring per-se but keeping the torrent alive or tracker updated.

You could try running wireshark or something to see what the data actually is, or what program it's coming from... (I have no experience to offer here on this though)

I would say that's DHT looking for other peers.

Hi johnny. Thanks for the reply.
You were right, it is DHT. I disabled it in the network preferences and the traffic stops. Do you know why the scheduler does not handle this better? It seems unnecessary to be looking for DHT nodes if Deluge is scheduled not to download.

Cheers,
mono