[4.1.2] UPnP doesn't work with Orange FunBox2.0

[woj-tek]

qBittorrent version and Operating System

4.1.2

If on linux, libtorrent and Qt version

macOS QT: 5.8.0 libtorrent: 1.1.9.0 boost: 1.67.0

What is the problem

UPnP doesn't work with Orange FunBox2.0 In the qBittorrent logs I can see:

16/8/18 9:54 - UPnP / NAT-PMP support [ON]

but port is inaccessible from outside and in the router panel I don't see it's entry (there are entries from other applications like Skype

What is the expected behavior

UPnP should work

Steps to reproduce

enable UPnP in settings

Extra info(if any)

not that I can think of.

[kompowiec]

I don't associate the offer but qBittorrent doesn't work with Port-restricted cone NAT, i have LTE internet and can't open ports, only solution it's use UDP/TCP/ICMP hole punching but... this client not supported this method NAT traversal. But i think so is nice to have, original utorrent 2.2.1 he boasts that he supports this solution.

For symmetric NAT is possible use supernode thanks to trackers.

i tested UPnP but doesn't work for me, it was work only once in a lifetime (probably by accident) and usually not at all

[Seeker2]

qBitTorrent attempts to do both UPnP and NAT-PMP, which might cause conflicts with each other or manually forwarded ports in rare cases.

Even if you see incoming uTP connections, that doesn't mean UPnP worked. libtorrent, which qBitTorrent uses as its core, also does do STUN-based UDP NAT hole-punching using uTP...but its method is less successful than uTorrent. So you can see incoming uTP peers+seeds on torrents even firewalled by NAT and some software firewalls. The requirement is there must be already-connected peers or seeds (which must also use uTorrent or recent-enough version of Deluge/qBT for libtorrent to offer that feature) to "introduce" firewalled peers/seeds to each other. Both the methods that uTorrent and qBT use have nothing to do with trackers.

[kompowiec]

I understand. Currently, I only see that others are trying to connect with me but can't any seed. While downloading, I noticed two things: 1) send with speed 1-2 kb/s but i think so is fake because never I have not seen one of those connected to "use it", it never increased from me ratio. 2) when the download slows down, suddenly seed to about 100 kb/s max, until the full speed returns, it must be physical ailment, the artificial limit gives nothing.

So, if you say that qbittorrent have NAT traversal, there is a solution to seed on port-restrct cone NAT? I bought one day a public IP address once from ISP but not worked, because simply i just stayed behind restrict NAT.

[Seeker2]

1.That minimal 1-2 KB/sec speed is probably overheads, not file transfers of the torrent.

2.If the qBT max limit didn't even partially work, did you have it set to allow uTP peers and seeds to exceed the limit?

qBT's NAT traversal may not work on "tighter" forms of NAT, beyond the simple unforwarded router behind a modem in bridge mode. uTorrent's may be slightly better in that regard.

[kompowiec]

I tested other option: torrent doesn't have any seed so i add webseed download and... can upload! i seeding probably with maximum bandwidth, 1 MIB/s but if i download file it can't continue seeding (disconnect). I will tested option altruist mode on utorrent, work but my seed is 0.5 kb/s or not possible :(

[FranciscoPombal]

UPnP support has been working correctly for some time now. The most common cause of failure is due to routers not supporting lease duration. However, in the advanced settings, there is now the option to customize this value - even setting it to 0, which means no lease duration is negotiated (resulting in a permanent lease), to workaround these kinds of router bugs.

If you have any issues with the latest version, please open a new issue report (if it's a straight UPnP implementation bug, open a bug report in the libtorrent bug tracker instead).

Thank you for your contributions.