Project

General

Profile

Bug #9572

uPNP not working - miniupnpd needs an update, reporting "interface index not matching", which has been fixed upstream

Added by Robert Johnston about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
uPNP
Target version:
-
Start date:
05/31/2019
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.4-p3
Affected Architecture:
amd64

Description

miniupnpd is reporting "interface index not matching 10 != 2", which was fixed in commit https://github.com/miniupnp/miniupnp/commit/1fe8d21cf2fda3bb6a2435d267b41f3b68641c23

Any version released after then (2.0 or 2.1) will have the fix in. Without it, miniupnpd is not responding on the interface(s) requested, so upnp and nat-pmp port mapping isn't working.

History

#1 Updated by Tim Harman about 2 months ago

[2.4.4-RELEASE][admin@x.com]/var/log: cat /etc/version.patch
3
[2.4.4-RELEASE][admin@x.com]/var/log: pkg info | grep upnp
miniupnpd-2.0.20180503,1 UPnP IGD implementation which uses pf/ipf

Doesn't this mean we already have v2.0 installed with the fix (this is a version from May 2018, after the commit date)

#2 Updated by Robert Johnston about 1 month ago

Tim Harman wrote:

[2.4.4-RELEASE][admin@x.com]/var/log: cat /etc/version.patch
3
[2.4.4-RELEASE][admin@x.com]/var/log: pkg info | grep upnp
miniupnpd-2.0.20180503,1 UPnP IGD implementation which uses pf/ipf

Doesn't this mean we already have v2.0 installed with the fix (this is a version from May 2018, after the commit date)

Huh, so we do. I've raised an issue at the miniupnpd tracker (https://github.com/miniupnp/miniupnp/issues/379) and I'll let you know what, if anything, comes up from it.

Also available in: Atom PDF