UPNP broken on 21.05?
-
@steveits Yep, that would be my problem. Is there an ETA for when this will get fixed? I have to imagine this is a huge problem for a lot of people. I work in Networking so I can build port-forwards, but I have to imagine there are a lot of people that don't know how, or don't want to.
-
Yup, I'm seeing the same thing. Disappointing after spending 400 bucks on the appliance only to no longer be able use this basic feature...... :(
-
I merged together two threads about this since it's the same issue for both.
We are aware and have been actively working on solving this and other SG-3100 issues.
For those who are affected, was this working on 21.02.2?
-
@jimp Yes. I had UPnP sessions on 21.02.2.
When I upgraded to 21.05 it stopped working.
-
@bcodd Just make manual port forwards. It's pretty simple using the GUI. I manually port forwarded my Xbox and its been working fine.
You'd be pretty surprised how much stuff doesn't need UPnP. I disabled the service and now all my iphones currectly use wifi calling too.
-
I think this is causing my SG1000 router to hang...
https://forum.netgate.com/topic/164877/router-hanging-after-21-05-upgrade
-
It looks like this may be from a change in the FreeBSD kernel between versions that required a new build of miniupnpd, but the version number of miniupnpd didn't increase so it didn't get reinstalled.
You should be able to fix this with:
killall -9 miniupnpd pkg upgrade -fy miniupnpdAnd then click Save on the miniupnpd settings. Or run the
pkgcommand and reboot. -
@jimp Appears to be working :) I have now got rules being created.
It'll be interesting to see if my router hangs in a few days time.
Thanks.
-
there still appears to be a problem.
miniupnpd is still using a LOT of cpu time - doing AFAIK nothing.
I restart it and everything goes back to normal.
-
@sdm900 Are you running 21.05 or 21.09?
-
Version 21.05-RELEASE (arm)
built on Tue Jun 01 16:52:45 EDT 2021
FreeBSD 12.2-STABLEThe system is on the latest version.
Version information updated at Fri Jul 9 10:34:51 AWST 2021 -
I can't reproduce any problem like that here, where I could easily reproduce the error before.
If you haven't yet, after you have updated
miniupnpdmanually as described above, reboot the router to ensure the correct copy is the only one being used.It's also possible there is a lot of local traffic hitting UPnP/NAT-PMP and it's just busy at the time you noticed it.
