It's now miniupnpd 2.0, and this feature is still tagged as
experimental. The most important line is "Dynamic external ip adresses
are not supported when this option is enabled", and in natpmp.c:259,
syslog(LOG_INFO, "NAT-PMP public address request");
FillPublicAddressResponse(resp,
Andre,
I wont have time to work much on this bug. But could you produce a patch
for fixing it? Then I will happily apply it to the current package.
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I've been thinking a bit about this problem. I think the EXTIP snippet
that causes this problem to begin with is basicly not even needed.
Actually detrimental even.
There are basicly two use cases we need to cover;
1) WAN IP is a single dynamic or static address. This is like 99% of cases.
On 08/23/2012 06:13 AM, Andre Tomt wrote:
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
Initscript magic fails with multiple IP's on WAN interface.
192.168.99.1 and xx.xx.xx.2 (censored) is set on
On 23. aug. 2012 13:49, Thomas Goirand wrote:
On 08/23/2012 06:13 AM, Andre Tomt wrote:
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
Initscript magic fails with multiple IP's on WAN interface.
Package: miniupnpd
Version: 1.7-3
Disclaimer: I installed this in ubuntu, but AFAICT there is nothing
Ubuntu specific with this bug.
Initscript magic fails with multiple IP's on WAN interface.
192.168.99.1 and xx.xx.xx.2 (censored) is set on WAN interface
+ /sbin/iptables -t nat -A
6 matches
Mail list logo
