Deluge Forum

I'm using deluge 1.1.5 on kubuntu hardy (x86) and I can't get port forwarding to work. I have a Westel 327W modem/wireless router (Verizon DSL).

I also run the transmission BitTorrent client and it works with port forwarding using port 51413 with the Use UPnP or NAT-PMP checkbox selected.
When I get the port open in transmission, it makes a huge difference, sometimes 20x or more. I usually have to fuss with the router to get it to open the port (reapplying the port forwarding rule, or rebooting the router).

In deluge Preferences->Network, I have Incoming and Outgoing Port Ranges both set to 58846-58846 and I set up a separate port forwarding rule in my router the same as for transmission, but using port 58846. I have left all the Network Extras checkboxes selected.

I have tried checking and unchecking Use Random Ports for both Incoming and Outgoing.
When I click Test Active Port it always shows the yellow triangle - (closed).

The really weird thing is that "Active Port:" never displays 58846. When I check or uncheck Use Random Ports and then click Apply, the Active Port number changes, but never to 58846.

Is this a deluge bug?

TIA

Joe

Hey..i have a similar prob here on Kubuntu 8.10 with deluge 1.1.5..am behind a modem and a router..

i tried port forwarding but it didnt change anything on my speeds..

Playing around with settings i g0t the best speeds by enabling UPNP and NAT-PMP in deluge's preferences and disabling DHT..I also enabled UPNP on my modem and router, without doing any manual port forwarding..
I still get "no incoming connections" but the speeds are g00d, i tried downloading a known linux distro, and i get full speed, so i hope this means am OK..

Maybe the port forwarding with UPNP in 1.1.5 works ok, but there is a bug reporting no incoming connections?

A known Linux distro is not a valid test if it is a popular one. It will have many seeders that your bitTorrent client (deluge) will discover directly through the Peer Exchange ("outgoing"). It will test that the client and your Internet connection are both working fine, but will run very fast without any incoming connections.

The point of incoming connections (as far as I can figure out as a noobie at peer to peer) is that other bitTorrent clients that you didn't find can find you and ask to join up with your efforts to upload and download your torrents.

Getting the incoming port(s) turned on (in another bitTorrent client - transmission) has made a 10 to 20 X download speed difference for some torrents that were going slow.

I turned UPnP on in my router and deluge. So far, it hasn't made a notable difference.

I did a tiny bit of reading about UPnP and from what I gathered, it appears to be a major security risk - especially for machines running Windows, so I wouldn't leave it enabled unless your machine is very well defended and you see a major benefit when it's on

My impression was that it was essentially a shortcut/workaround for people who couldn't figure out how to do port forwarding, but in making things easy, it essentially let anything on your entire local network open up any ports it wants to in a way that would not be very visible to you. So if anything nasty gets on any computer in your local network, it has free reign to phone home for further instructions, to send your data, or help mount an attack on another machine, etc.

same problem,(1.1.5)
i have set my firewall rule to allow only 6881 as my incoming port...but deluge never sets 6881 as the port, it sets 6882 instead.

and i if i set range to 6881 to 6881 then it set so random 56344 or somthing as incoming port!
if i set range to 6880 to 6881 then it sets to 6880. if i set range to 6881 to 6882 then it sets to 6882...its all even number port or somthing...



i ended up frustrated and changing my firewall rule to allow from 6882 instead of 6881!

its working fine now once the incoming port was unblocked by firewall

i m on fedora10 btw

creeping death wrote:same problem,(1.1.5)
i have set my firewall rule to allow only 6881 as my incoming port...but deluge never sets 6881 as the port, it sets 6882 instead.

and i if i set range to 6881 to 6881 then it set so random 56344 or somthing as incoming port!
if i set range to 6880 to 6881 then it sets to 6880. if i set range to 6881 to 6882 then it sets to 6882...its all even number port or somthing...



i ended up frustrated and changing my firewall rule to allow from 6882 instead of 6881!

its working fine now once the incoming port was unblocked by firewall

i m on fedora10 btw

Only thing I could think for your particular problem was something else already using the port 6881. It will use random if you set a single port and that port is already in use.

I solved manually editing iptables

I had the same problem as Creeping Death. When I set my port range to just one port, it was never selected by deluge and I'm sure that port wasn't being used for anything else, so there may be an issue in deluge. I did set the port range to port - 1 to port and it selected port - 1. I then went back into my router and opened port - 1. That works. Now I get incoming connections (until my ISP gets tired of me and blocks the port).

Joe