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!
Hello, I am curious as to why the pfSense FreeBSD port of this package has been updated first before the main FreeBSD port of this package? https://github.com/pfsense/FreeBSD-ports/commit/6e7d96166c051915155356546474a1c6e68cf2aa Is this due to netgate sponsoring the change? If so is there some sort of delay/exclusivity that pfSense gets due to the sponsership before being merged into the main FreeBSD port? Just seems odd to me that the main FreeBSD package would not be updated first and then all other downstream projects would then be subsequently updated.
(In reply to xpendable from comment #8) That's concerning, especially considering that the previous sponsored commit from the same person has broken what was working fine before. And now this issue has affected all FreeBSD users for many months.
Created attachment 251015 [details] patch from May 8
Attached the GitHub patch and will ask for this to be assigned/handled.
^Triage: with bugmeister hat, reset maintainer-feedback flag due to timeout. To maintainer: it is not clear to me whether you ever saw this PR. But in either case, please let bugmeister@ and/or portmgr@ know if you are still interested in maintaining this port.
(In reply to xpendable from comment #8) It's OPNsense (Deciso) and not PFsense (Netgate).
(In reply to roylaprattep from comment #13) You don't understand. net/miniupnpd was made barely maintainable due to libpfctl additions that are not going upstream. This report was from OPNsense, but affects all FreeBSD users. Now pfSense has a fix written by the person who introduced libpfctl here in the first place, but did not fix it in FreeBSD. I have HIS patch attached. Now we are still waiting from SOMEONE to step in and commit it here? I don't think this is a fair/reasonable approach to bugs and maintaining software in the FreeBSD ports tree. Cheers, Franco
(In reply to Franco Fichtner from comment #14) Ok ok. Sorry, I'm not used to FreeBSD architecture and how it actually works. I'm only using OPNsense, otherwise I'm a Debian guy.
fixed: 81eb1a733dac