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

DHT port fowarding help needed

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

DHT port fowarding help needed

Tue Jul 24, 2007 3:26 am
I'm using a stupid Linksys router (WRT54G) that doesn't do port forwarding right.
I've attempted to fix it but I can't. In the below image you can see what I had to do for azureus, I don't think it worked for deluge though. I know it worked for azureus and DHT and NAT was fine. I can't get it right for ktorrent though. Theses are my stats:
UPnP plugin enabled
Port: 6883
UDP Tracker Port: 6884
UDP port for DHT com: 6885
I don't think this would effect it but several of my torrents I download come from a private tracker (GT), but I don't think that would effect it.
Image

Any ideas on how to fix the problem?
artusek
Registered Member
Posts
10
Karma
0
OS

Tue Jul 24, 2007 10:17 pm
I have set my ports in a bit different way.
Port: 53102 (protocol TCP)
UDP Tracker Port: 53103 (protocol UDP)
UDP port for DHT com: 53104 (protocol UDP)
You have set all ports for both protocols - TCP and UDP. I do not know whether it makes difference.
All these ports are assigned for my IP - 192.168.1.3
I have disabled dhcp in network settings and IP for my computer is set statically.
UPnP disabled.
With such settings I can almost always reach down/uploads close to my maximum bandwith - ca. 240 KB/s downloads and 35 KB/s uploads.
Some more useful info You can get here:
http://www.azureuswiki.com/index.php/PortIsBlacklisted

Regards,
Jerzy

KTorrent 2.2dev, Mandriva 2007.1, KDE 3.5.7, kernel 2.6.21
malfist
Registered Member
Posts
2
Karma
0

Wed Jul 25, 2007 12:55 pm
Same problem, no DHT. I changed ports on ktorrent and on the routers properties.

Edit: DHT status lists 65 nodes but most peers are still non-DHTed
stevenofnine
Registered Member
Posts
62
Karma
0

Re: DHT port fowarding help needed

Wed Jul 25, 2007 3:30 pm
malfist wrote:I'm using a stupid Linksys router (WRT54G) that doesn't do port forwarding right.
Theses are my stats:
UPnP plugin enabled
Port: 6883
UDP Tracker Port: 6884
UDP port for DHT com: 6885

Any ideas on how to fix the problem?


First of all, don't manually open ports for KTorrent if you have uPnP enabled.

The Linksys WRT54G (I have one) works perfectly well with Port Forwarding, and I have used it with Azureus, uTorrent and KTorrent with no requirement to manually open anything.

First off. Stop using 688x ports. Use 5-digit ports, preferably in the 40,000-60,000 range.

Enable uPnP in the KTorrent client.
Enable uPnP on your Linksys if it requires you to.
Make sure your Linksys has the "Block Anonymous Internet Requests"
OFF in Security.

Reboot the router and computer.

Off you go.
randomjohn
Registered Member
Posts
9
Karma
0

Tue Jul 31, 2007 11:45 pm
depending on the version of your router, the better long-term solution is to install dd-wrt as your firmware. the vanilla linksys firmware is awful and dd-wrt adds great functionality. [url]http://www.dd-wrt.com
[/url]
jdong
Registered Member
Posts
358
Karma
0

Wed Aug 01, 2007 2:36 am
Umm... the DHT field in peers has *nothing* to do with if DHT is working properly. It just means whether or not the peer has publically announced that it supports DHT. In fact, uTorrent and BitComet clients will show an X, but actually respond to DHT.

As long as you have a good number of nodes (>50), DHT is working properly.


Bookmarks



Who is online

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