transmission is using the wrong upnp device for portforwarding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
transmission (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: transmission
Transmission gladly reports that it enabled port forwarding via UPnP on 172.16.3.10, but (as it should know!) 172.16.3.10 is *not* my gateway and not responsible for any port-forwarding regarding my internet connection.
A simple "route -n" would suffice, to check against this :)
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: b2f2c3385a2bd6c
CheckboxSystem: d00f84de8a55581
Date: Thu Dec 24 16:07:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: transmission-gtk 1.75-0ubuntu2
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: transmission
Uname: Linux 2.6.31-16-generic x86_64
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Transmission uses an unmodified version of miniupnpc for port forwarding, so I'm reassigning this ticket to the miniupnpc package. If there's more attention needed by the Transmission team, feel free to ping me.