Your message dated Mon, 5 Feb 2018 23:05:05 +0800 with message-id <caaxyomnzj92l5d0owkn8oyqh2rlhvrw-x295jvq406ygfpp...@mail.gmail.com> and subject line has caused the Debian Bug report #725288, regarding miniupnpc does not pick the correct router to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 725288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: miniupnpc Version: 1.6-2 Severity: important Dear Maintainer, My network is setup as follows: my laptop -> (wireless) -> wireless ap -> (ethernet) -> router Both the wireless AP and the router are advertising themselves as uPnP devices correctly. In particular, the router has: Connection type : IP_Routed ExternalIPAddress = <my external ip> GetGenericPortMappingEntry() works while the AP has: Connection type : IP_Bridged GetExternalIPAddress() returns -1 GetGenericPortMappingEntry() returns 501 (Action Failed) This is a correct configuration. However, running "upnpc -l" (or other commands which want to examine port forwarding) tries to talk to the AP instead of the router, presumably because latency to the AP is slightly lower. This is obviously wrong; the AP does not support port forwarding, because it is a bridge without an external IP. miniupnpc should use the uPnP device with connection type IP_Routed for port forwarding. Please don't tell me to turn off uPnP on the wireless AP, because: 1) The current configuration is not actually incorrect in terms of what information is being exported. Note that Windows (for example) is perfectly capable of dealing with this setup. 2) If I turn off uPnP then the AP will no longer be visible in Windows' network map, which is bad, because that's the only way my roommates can configure the AP. There is basically no situation where it is correct for miniupnpc to be attempting to deal with port forwarding on an IP_Bridged device, because that doesn't make any sense. At the very least, if there are multiple routers on the network, and a port forwarding operation fails when talking to the first one, miniupnpc should fall back to talking to the next available device. Output of the relevant upnpc commands: $ upnpc -l upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/ for more information. List of UPNP devices found on the network : desc: http://192.168.1.3:49152/InternetGatewayDevice.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 desc: http://192.168.1.3:49152/InternetGatewayDevice.xml st: uuid:62A48009-FFD7-7CBE-0FA9-1C7EE5DEDFCA desc: http://192.168.1.1:36796/rootDesc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 Found valid IGD : http://192.168.1.3:49152/soap.cgi?service=WANIPConn1 Local LAN ip address : 192.168.1.65 Connection Type : IP_Bridged Status : Connected, uptime=2971s, LastConnectionError : ERROR_NONE Time started : Thu Oct 3 08:45:02 2013 MaxBitRateDown : 100000000 bps (100.0 Mbps) MaxBitRateUp 100000000 bps (100.0 Mbps) GetExternalIPAddress() returned -1 GetExternalIPAddress failed. GetGenericPortMappingEntry() returned 501 (Action Failed) $ upnpc -u http://192.168.1.1:36796/rootDesc.xml -l upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/ for more information. upnpDiscover() error code=0 Found valid IGD : http://192.168.1.1:36796/ Local LAN ip address : 192.168.1.65 Connection Type : IP_Routed Status : Connected, uptime=253021s, LastConnectionError : ERROR_NONE Time started : Mon Sep 30 11:17:56 2013 MaxBitRateDown : 15000000 bps (15.0 Mbps) MaxBitRateUp 5000000 bps (5.0 Mbps) ExternalIPAddress = 50.53.89.53 0 UDP 51413->192.168.1.65:51413 'miniupnpd' '' 0 1 UDP 55649->192.168.1.66:55649 'miniupnpd' '' 0 2 TCP 55649->192.168.1.66:55649 'miniupnpd' '' 0 3 TCP 51413->192.168.1.65:51413 'miniupnpd' '' 0 GetGenericPortMappingEntry() returned 713 (SpecifiedArrayIndexInvalid) -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages miniupnpc depends on: ii libc6 2.17-93 ii libminiupnpc8 1.6-2 Versions of packages miniupnpc recommends: ii minissdpd 1.1.20120121-1 miniupnpc suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Fixed by upstream.
--- End Message ---
