331
General Discussion / Re: Is UPNP miss configured or simply broken in it's implementation?
« on: June 29, 2020, 06:48:48 pm »Hey FullyBorked seems like you have the same issues as I did on pfSnese.Hey m0t0k0, I've not been able to get even the first device to work. None of my devices seem to want to activate the upnp service. I wish i knew log location so i could see if it's even getting a request.
I could get UPnP working no problem with just one device but as soon as we have multiple devices trying to access the same game service it all fell over for all but the first device which connected.
I'm certain the is to do with the way MiniUPnP is coded. It apparently has been fixed and there is a patched version which is available with the nightly builds of pfSense.
This is the issue over on MiniUPnP https://github.com/miniupnp/miniupnp/pull/455
The work was done in response to this issue on the pfSense forums https://redmine.pfsense.org/issues/7727
As both OPN and PF use MiniUPnP and the FreeBSD Packet Filter I'm sure they both will share the same fix or something very close to it?
Maybe someone with some more technical understanding can let us know.
I do know the COD Warzone was affected and on my PF box a single PC could connect no issues through UPnP but any subsequent PC would be blocked.
It also affects Xboxes where the first one can connect to the Microsoft network but the subsequent connection on other Xboxes are blocked.
Can we sideload plugins? The patched version of MiniUPnP (miniupnpd-2.2.0-RC1.tar.gz) is available here
https://miniupnp.tuxfamily.org/files/
Sent from my GM1917 using Tapatalk