Messages

It seems that way now, I didn't need it on 26.1 but the reason of why it was working is unknown to me, but now you do need it with 26.7

IMHO you found a bug, because why would you need both of them when uPnP does more than a Source NAT Rule with Strict-port Enabled does : It completely opens the port like a Port Forward a.k.a. Destination NAT Rule would :)

I mean, even on previous releases, if I didn't have the rule things would complain about strict NAT. With the rule all is fine. I've never gotten the UPNP plugin to give "open NAT" on OPNSense, pretty sure it's not possible in the current releases, but moderate is sufficient to get games to stop complaining so meh.

I finally got it working.

I added this "Source NAT" rule:
https://www.pasteboard.co/lTHlqpZ_SWPY.png

Is this rule required now for getting UPnP IGD & PCP back to work? Why? I am facing the same issue. Active mappings with IP address ?.

It's always been my understanding that it's required, I always used an outbound NAT rule, and since the new firewall stuff came in that moved over to source NAT. So I migrated the rule before upgrading to 26.7 and my upnp stuff is working fine. The only issue is the UI glitch in the active maps section showing question marks instead of IP addresses, but I suspect that will be addressed with an update for the plugin.

and you set Static port right?

What is this last bit exactly? Maybe is something silly I haven't done or did before but need to redo for 26.7

I believe I had to tick on the advanced options in the source nat rule while creating it, but it's a check box called static port.

I migrated that from the old Outbound NAT section on 26.1 before upgrading and things seem to be operating correctly, despite the visual glitch in the UPNP service page.

In the past when I installed OPNSense back in 26.1 I migrated to the new firewall rules.

I had my source NAT configured as Hybrid in 26.1 and it was working for 26.1, in 26.7 it is in Hybrid mode too, besides the visual glitch, was there something I needed to do?

My understanding is that I had already made the modifications required, but maybe I missed something?

My test subject is my son's Destiny 2 and that stopped working for 26.7, I mean you can NAT but you cannot map ports properly, they show as mapped but no IP address and Destiny complains about it so it is not working as it was in 26.1

No, you did everything correctly, source NAT with hybrid rules, and you set Static port right? That last bit is important to get things to stop complaining. Like I said, I am also seeing the ? instead of an IP under maps but I verified multiple times with multiple different games/software that the ports ARE opening and being routed to the correct PCs. If I remember from back when I played Destiny 2 like 10 years ago, I had to go through a whole song and dance to make that game work with PFSense, I have ACL rules set up in the UPNP plugin because I seem to remember that being the trick with PFSense but I'm not sure if that's doing anything here.

As far as I can tell it's working other than the visual bug, at least it's passing the girlfriend test so I don't have to explain why the internet is messed up lol.

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

This is exactly what's happening to me, the IP address column is just ? and while it attempts to add entries to the firewall, uPnP is failing to do so.

I already had migrated my old firewall rules in 26.1 to the new rules set and all of my other rules are working as expected, the firewall seems fine, including my port 53 and 123 interception for the firewall own services.

So for now I just disabled the service until it is confirmed is fixed, but glad it wasn't just a me issue ;-)

I'm seeing the ? under IP as well, but my firewall DOES seem to be creating the maps. My plex server and my girlfriend's PC have both managed to create maps and I've verified the ports are indeed open. Do you have Source NAT configured for static port? I migrated that from the old Outbound NAT section on 26.1 before upgrading and things seem to be operating correctly, despite the visual glitch in the UPNP service page.