This forum has been archived. All content is frozen. Please use KDE Discuss instead.

DHT Causes Bad Traffic?

Tags: None
(comma "," separated)
esaym
Registered Member
Posts
2
Karma
0

DHT Causes Bad Traffic?

Wed Jan 17, 2007 8:03 pm
As seen by the logs on smoothwall: http://www.lindsay.ath.cx/stuff/firewalllog.dat.html

Normally the only traffic that is logged are connections from the WAN that get dropped by iptables. Traffic on forwarded ports does not get logged. As you can see by the log, ktorrent is producing quite a bit of traffic that for some reason is getting logged. And the amount of traffic that it is logging will turn a small log file into a 20mb one over night which causes memory problems on smoothwall.

The computer with ktorrent on it is 10.36.36.199 and the external IP address is 72.183.201.32. Ports forwarded to 10.36.36.199 on smoothwall are 6881 tcp&udp and 4444udp.

Why ktorrent is trying to connect to the ip it is running on I don't know. It only happens with dht on. Everything is fine with it off. Also according to the logs from ktorrent, it is trying to get sources from my external ip address (72.183.201.32). Why it does that I don't know:

Code: Select all
Initiating connection to 121.92.132.137
Initiating connection to 193.179.148.53
Initiating connection to 195.20.3.6
Initiating connection to 24.116.162.243
Initiating connection to 62.103.145.160
Initiating connection to 62.38.5.176
Initiating connection to 71.104.4.234
[b]Initiating connection to 72.183.201.32[/b]
Initiating connection to 80.60.131.245
Initiating connection to 80.60.81.84
Initiating connection to 82.160.118.24
Initiating connection to 86.149.216.18
Initiating connection to 86.20.212.200
Initiating connection to 86.87.21.66
Initiating connection to 24.254.199.11
Initiating connection to 70.77.41.8
[b]Initiating connection to 72.183.201.32[/b]
Initiating connection to 83.109.245.229
Authentication to 70.77.41.8 : failure
Timeout occurred
Authentication to 83.109.245.229 : failure
Timeout occurred
[b]Authentication to 72.183.201.32 : failure
Timeout occurred[/b]
Authentication to 83.109.245.229 : failure
Timeout occurred
Authentication to 24.18.216.184 : failure
Timeout occurred
Authentication to 68.199.20.147 : failure
Timeout occurred
Authentication to 72.183.201.32 : failure
Timeout occurred


Perhaps ktorrent doesn't like NAT? Is this information enough for someone to trouble shoot? I can provide more if needed or run network traffic sniffers....

I really don't think this is a smoothwall problem since I have ran lots of other p2p apps before and I have never ran into a problem like this.


Thanks!
George
Moderator
Posts
5421
Karma
1

Thu Jan 18, 2007 5:27 pm
Because of the NAT, KT doesn't know the WAN IP address. With DHT you can easily get your own IP address back, which is not really a problem, if you connect to yourself, the connection will be refused.
esaym
Registered Member
Posts
2
Karma
0

Thu Jan 18, 2007 7:38 pm
George wrote:Because of the NAT, KT doesn't know the WAN IP address. With DHT you can easily get your own IP address back, which is not really a problem, if you connect to yourself, the connection will be refused.


Hmm so because of that it is getting logged I guess?
jdong
Registered Member
Posts
358
Karma
0

Thu Jan 18, 2007 10:05 pm
That, along with repeated attempts to contact peers that may be refusing connections.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]