MiniUPNPD

[franco]

And the base system?

# opnsense-update -zbr 25.7.11

(also needs a reboot)


Cheers,
Franco

[epyon9283]

Same behavior unfortunately

[franco]

I'm a bit at a loss where the bug would come from if components are back on 25.7.11 and it's still happening.  It was working on 25.7.11, totally and normally?


Cheers,
Franco

[epyon9283]

Honestly, I'm not sure. I don't think I ever checked on 25.7.11.

[Marius_]

Hi,

It worked perfectly fine on 25.7.11 before upgrade... :)

I got the same errors... After upgrade.

2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-01-29T22:10:40ErrorminiupnpdFailed to add NAT-PMP 28159 TCP->192.168.1.19:32400 'NAT-PMP 28159 TCP'
2026-01-29T22:10:40Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument

[franco]

I'm liking to https://forum.opnsense.org/index.php?topic=50566.msg258338#msg258338 which could be related since we don't get anywhere with older OS versions.

[burre90]

Hi,

It worked perfectly fine on 25.7.11 before upgrade... :)

I got the same errors... After upgrade.

2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument
2026-01-29T22:10:40ErrorminiupnpdFailed to add NAT-PMP 28159 TCP->192.168.1.19:32400 'NAT-PMP 28159 TCP'
2026-01-29T22:10:40Errorminiupnpdioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-01-29T22:10:40Errorminiupnpdpfctl_get_rules_info: Invalid argument

I am also getting
2026-01-30T00:51:58-08:00   Error   miniupnpd    ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument

And Franco I also tried both the opnsense-update commands you shared (with a reboot each time) and no change.

[burre90]

I had some spare time, so I set up a fresh USB install of OPNsense 26.1 with the default config/settings to test UPnP behavior.

here is the log:

2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:39    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:33    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:22    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:18    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T10:00:17    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:38    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:37    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:37    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:36    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:35    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:28    Error    miniupnpd    pfctl_get_rules_info: Invalid argument
2026-01-30T09:59:28    Error    miniupnpd    could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-01-30T09:59:28    Error    miniupnpd    could not open lease file: /var/run/miniupnpd.leases

[epyon9283]

I'm liking to https://forum.opnsense.org/index.php?topic=50566.msg258338#msg258338 which could be related since we don't get anywhere with older OS versions.

No luck. Same behavior after patching.

[fuzelet]

I know this is for the 26.1 section but thought I would at least mention I am still on 25.7.11_9 and "UPnP IGD & PCP" seems to be working fine for me. I was able to use my PS5 and connect to various games and see active maps being created in the GUI under Services: UPnP IGD & PCP: Active Maps.  If there is anything I can potentially provide to help with this while still on this version please let me know.

[franco]

I think I found it.  Looks like a feature removal gone wrong:

# opnsense-patch https://github.com/opnsense/core/commit/311184daa8
# /usr/local/etc/rc.filter_configure

It should bring back the required anchors.


Cheers,
Franco