I moved to 26.7, my old firewall rules in 26.1 was already moved to the new rules set format so I imagine that's good on 26.7
But when I look at UPnP mappings I see this:
IP address Port External port Protocol Remote IP Remote port Added via / description
? 22419 22419 UDP any any UPnP IGD / DemonwarePortMapping
No IP address and it seems to not be working (My son is my tester with Destiny 2 complaining about strict NAT), it was working on 26.1
Quote from: Warbreaker on July 16, 2026, 03:12:47 PM(My son is my tester with Destiny 2 complaining about strict NAT)
Configure the following for him :
- Static DHCP IP Address Mapping based on the MAC Address of his PC/Console.
- Enter that IP Address in a new Alias called GAMING_Clients or something like that.
- Switch to Hybrid NAT Mode
- Create a Manual NAT Rule with Strict-port Enabled and as Source the Alias GAMING_Clients.
He will now always at least have Moderated NAT and could even continue gaming without uPnP Enabled :)
I will probably do that at some point, but thought on reporting it as well, either something is broken or the stronger rules on 26.7 is making the old plugin not work at all, for security reasons of course I have only one ACL on my UPnP plugin to just allow non privileged ports to be bound.
It would be interesting to know why it isn't working anymore.
So i've been battling this today, oddly Destiny 2 was my guinea pig too lol
So as far is i can tell miniupnpd seems to struggle to bind the client IP to the port request, now if i roll back to my deployment of 26.1.x this is a non issue. The unfortunate thing also though is i found the stuggestion nero gave to not work either which is odd.
I have yet to go down the port forward route yet mostly because if that works i'll shelf opnsense in favour of another router as i don't have the time or the will to map all the ports of every game that gets played in this house lol.
I have different network segments for different tasks (IoT, Servers, Gaming, Work etc) because i'm lazy uPnP is excellent for the gaming segment (a cheeky /29 subnet) as there are no access rules to other VLANs from there so it can go mental for all I care (before some karen shouts about security and how uPnP is a infiltration waiting to happen).
But judging on how the intel microcode plugin is causing issues i'm just going to assume it's a bug in the network stack somewhere and wait to see what happens maybe the kids will go outside for once.........
Quote from: Baron_Backdoor on July 18, 2026, 08:58:12 PMThe unfortunate thing also though is i found the stuggestion nero gave to not work either which is odd.
Hmm... that sucks... :'(
Did you check https://docs.opnsense.org/ to make sure you have not missed anything ?
My post was more a quick guide line than an actual HowTo :)
QuoteI have yet to go down the port forward route yet mostly because if that works i'll shelf opnsense in favour of another router as i don't have the time or the will to map all the ports of every game that gets played in this house lol.
That sucks indeed and is something I would never do either!
QuoteI have different network segments for different tasks (IoT, Servers, Gaming, Work etc) because i'm lazy uPnP is excellent for the gaming segment (a cheeky /29 subnet) as there are no access rules to other VLANs from there so it can go mental for all I care (before some karen shouts about security and how uPnP is a infiltration waiting to happen).
This "Karen"
APPROVES!!! ;)
QuoteBut judging on how the intel microcode plugin is causing issues i'm just going to assume it's a bug in the network stack somewhere and wait to see what happens maybe the kids will go outside for once.........
LOL! NICE! ^_^
Confirming issues immediately after an upgrade to 26.7 as well
It seems to be partially working though, as some entries/mappings are being made. And now the "IP address" column is just showing "?" for all entries, instead of the local IP as in previous versions. Not sure if that could help point the finger at the actual issue