Originally discovered in OPNSense: https://github.com/opnsense/plugins/issues/3831. See also https://forum.opnsense.org/index.php?topic=38732.0. OPNsense 24.1.2_1-amd64 FreeBSD 13.2-RELEASE-p10 OpenSSL 3.0.13 miniupnpd 2.3.3 Over time, duplicate mappings like this are created: ``` 62852 tcp 10.0.0.87 6690 upnpclient:6690 62852 tcp 10.0.0.87 6690 upnpclient:6690 62852 tcp 10.0.0.87 6690 upnpclient:6690 ``` If you try to get the mapping list using miniupnpc, it returns corrupted results: ``` i protocol exPort->inAddr:inPort description remoteHost leaseTime 0 UDP 0->10.0.0.87:0 '' '34.26.0.0' 0 1 UDP 0->10.0.0.87:0 '' '34.26.0.0' 0 2 UDP 0->10.0.0.87:0 '' '34.26.0.0' 0 ```
+1 here.
There is definitely breakage here since https://github.com/freebsd/freebsd-ports/commit/81e8bb9834
+1 here
This issue has been resolved upstream: https://github.com/miniupnp/miniupnp/issues/719 Please update this FreeBSD port to the latest version in order to resolve this issue. Also just a thought/question... shouldn't this be a part of a CI/CD process so that when the source gets updated the FreeBSD port also gets updated automatically?
Bumping +1 please.
Another bump, +1! Please fix this one as soon as possible since it would improve quality of life for all users of UPNP. Thanks in advance!