os-upnp plugin not working?

[bamf]

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 ?.

[Chris123NT]

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.

[Warbreaker]

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 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

[mayne88]

Anyone else with this issue on 26.7?
2026-07-22T12:25:02
Error
miniupnpd
could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-07-22T12:25:02
Error
miniupnpd
could not open lease file: /var/run/miniupnpd.leases

[nero355]

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 :)

[Warbreaker]

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'm sort of new to OPNSense, I started using OPNSense somewhere around 26.1.x, in my new installation back then I migrated to the new rules set because of a message I read that legacy would go away, so maybe the bug I found was with the new rules set? either way I can't recall having to do anything other than the Source NAT change from Automatic to Hybrid.