Messages

Thanks for the info. I'm going to go ahead and have a go when I get the opportunity.

Warzone is 70+GB so no worries if you cant test it

I'm glad you got your config working.

May I ask if your able to test two systems play g the same game simultaneously?
I definitely had issues with Warzone. Warframe would throw a warning on the main screen but would work.
Also only one machine could get open or moderate NAT with Microsoft Terdo service (Ipv6 tunneneling through Ipv4)  this can be checked through the Win 10 built in Xbox app.

Many thanks

What game is it that you can't get to work?
Is it just one machine connecting or multiple machines from your network?

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.

Sent from my GM1917 using Tapatalk
[/quote]

Oh sorry for hijacking your thread! My experience was with pfSense but I assume OPNsense would be similar. Good luck

Hey FullyBorked seems like you have the same issues as I did on pfSnese.
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/

Thanks for the replys

samsonmcnulty thanks I understand what your saying now OPNsense would randomize the outbound port however it can be set to static so I would use whichever port number the application requested.

I'm 100% certain this is what I did when using pfSense it was locked down with an alias list, ACL and firewall rules.

It worked perfectly but only for one machine at a time.

It appears the fix to MiniUPnP has been merged and so should be available in the next release.
https://github.com/miniupnp/miniupnp/pull/455

I assume the UPnP plugin is MiniUPnP and OPENsense uses the FreeBSD Packet Filter so the issue wo8uld affect it just the same as pfSense?

Does anyone run multiple PC/Game consoles at home who connect to the same online games simultaneously? Can anyone confirm if this just works out the box?

After that you only need to add each device to outbound nat with a static port.

Having a static port somewhat eliminates the function of UPnP tho right?

It seems others have experienced the same type of problems as I have
https://www.reddit.com/r/OPNsenseFirewall/comments/av1t3w/upnp_problems_gaming/

Hi I would like to try OPNsense but there is one thing holding me back!

My home network has 8 gaming PC/Consoles with a constantly evolving games library. This means UPnP is essential as I don't have enough time to be constantly adding and removing ports.

I did try running pfSense a while ago but we had big problems with UPnP. It would work for one user but for some games, subsequent users would not be able to access the game's servers.
I'm pretty confident this was because of MiniUPnPs interaction with the FreeBSD Packet Filter.

From what I understand this has been an ongoing issue for years but has recently seen some work to get it fixed. There is a thread about it over at pfSense.
https://redmine.pfsense.org/issues/7727#change-41170

Before I take the plunge and start learning my way around another firewall is anyone able to confirm if OPNsense would suffer from the same issues?
If it would be possible to use the updated version of MiniUPnP-2.2.0.r1,1?

Many thanks :)