pali

Full-cone NAT 1:1 setup on upstream router with private IP address on WAN interface on local router is already possible, just enable `ext_perform_stun=yes` option. But it requires that both local...

So, apply this change and look at detailed debug error message what is wrong.

This is not output from the code from this pull request as it prints more information what is wrong... Anyway, this discussion starting to be too off-topic for this pull...

Compile it from sources, there is Makefile for every system. If you do not know how, read instructions for your pfsense system (Sorry I do not know this system).

Ok, this needs to be fixed... Could you try to apply following change? ```diff diff --git a/miniupnpd/upnpforwardcheck.c b/miniupnpd/upnpforwardcheck.c index 48652cc89dd7..a7796d6247ad 100644 --- a/miniupnpd/upnpforwardcheck.c +++ b/miniupnpd/upnpforwardcheck.c @@ -8,6 +8,8 @@ #include...

Ok, here is fix for second part: ```diff diff --git a/miniupnpd/upnpforwardcheck.c b/miniupnpd/upnpforwardcheck.c index 48652cc89dd7..5e98966e79ff 100644 --- a/miniupnpd/upnpforwardcheck.c +++ b/miniupnpd/upnpforwardcheck.c @@ -56,11 +58,13 @@ static int create_sockets(const char *if_name, struct in_addr...

upnp protocol was not designed for cgnat setups. I think that if applications needs to know public ip address they should retrieve public ip address on their own and do...

Is this problem available in the latest unmodified version of miniupnpd from miniupnpd git master branch?

So update to the latest version from miniupnpd git master branch and check if this issue is fixed or not.

Any progress on this?