MiniUPNPD

[franco]

We'll do a 26.1.1 next week for various reasons and include the fix of course.


Cheers,
Franco

[Franco_Ruggeri]

Thanks a lot for fixing, worked perfectly. Relied on these anchors for tailscale direct connections.

[doubletakex]

I'm on 26.1.2_5 and I seem to be having the same issue. I did not manually install the patch.

[Schlammkuh]

I got the same issue with the new 26.1.3. I did not have those issue with the previous 26.1.2_5.

[franco]

To make sure it's not the plugin try

# opnsense-revert -r 26.1.2 os-upnp


Cheers,
Franco

[aphysically]

On a first-install of opnsense on 26.1, now on 26.1.3, I get the same errors as reply #22 who also fresh installed 26.1. I installed os-upnp for the first time after I had upgraded to 26.1.3. I can try the revert if you have instructions on how to undo the change afterward to get it back to default.

2026-03-10T00:28:38    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-10T00:28:38    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases
2026-03-10T00:26:57    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-10T00:26:57    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases
2026-03-10T00:25:42    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-10T00:25:42    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases
2026-03-10T00:25:39    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:39    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     pfctl_get_rules_info: Invalid argument
2026-03-10T00:25:38    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-10T00:25:38    Error    miniupnpd     could not open lease file: /var/run/miniupnpd.leases

[franco]

The errors in the log are one thing and I encourage everyone to research them and report them upstream.

The key question for us is if the service is working or not.


Cheers,
Franco

[BondiBlueBalls]

I saw the same logs during or immediately after the 26.1.3 update, but nothing since. UPnP continues to work fine with my PS5. Not sure if this helps, but figured additional data wouldn't hurt. Thanks!

Code Select Expand

2026-03-05T13:16:00-06:00 Error miniupnpd could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-05T13:16:00-06:00 Error miniupnpd could not open lease file: /var/run/miniupnpd.leases
2026-03-05T13:15:57-06:00 Error miniupnpd could not open lease file: /var/run/miniupnpd.leases-ipv6
2026-03-05T13:15:57-06:00 Error miniupnpd could not open lease file: /var/run/miniupnpd.leases


[Circan]

Greetings,

Joining in as I've also encountered the same scenario with Plex, Xbox, and PS5 on current 26.1.3. Issue is logged back to 26.1, but I didn't notice.

Implemented patch against 26.1.3 and returned successful outcome from earlier in this thread. prior commands. Subsequent a reboot, the issue persists.

Writing to add that it is possible that the service is working; in my implementation replies to UPnP/IGD Controller requests via Home Assistant complete without issue.
Otherwise, I've the same errors as reply #22. Sanitized output:

Code Select Expand

2026-03-10T12:39:30-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument
2026-03-10T12:39:30-XX:XX  Informational miniupnpd SOAPAction: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1#GetTotalBytesSent
2026-03-10T12:39:30-XX:XX  Debug        miniupnpd  Host: <router-ip>:<port>
2026-03-10T12:39:30-XX:XX  Informational miniupnpd HTTP REQUEST from <client-ip>:<port> : POST /ctl/CmnIfCfg (HTTP/1.1)
2026-03-10T12:39:30-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument
2026-03-10T12:39:30-XX:XX  Informational miniupnpd SOAPAction: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1#GetTotalBytesReceived
2026-03-10T12:39:30-XX:XX  Debug        miniupnpd  Host: <router-ip>:<port>
2026-03-10T12:39:30-XX:XX  Informational miniupnpd HTTP REQUEST from <client-ip>:<port> : POST /ctl/CmnIfCfg (HTTP/1.1)
2026-03-10T12:39:30-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument

2026-03-10T12:39:00-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument
2026-03-10T12:39:00-XX:XX  Informational miniupnpd SOAPAction: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1#GetTotalBytesSent
2026-03-10T12:39:00-XX:XX  Debug        miniupnpd  Host: <router-ip>:<port>
2026-03-10T12:39:00-XX:XX  Informational miniupnpd HTTP REQUEST from <client-ip>:<port> : POST /ctl/CmnIfCfg (HTTP/1.1)
2026-03-10T12:39:00-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument
2026-03-10T12:39:00-XX:XX  Informational miniupnpd SOAPAction: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1#GetTotalBytesReceived
2026-03-10T12:39:00-XX:XX  Debug        miniupnpd  Host: <router-ip>:<port>
2026-03-10T12:39:00-XX:XX  Informational miniupnpd HTTP REQUEST from <client-ip>:<port> : POST /ctl/CmnIfCfg (HTTP/1.1)
2026-03-10T12:39:00-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument

2026-03-10T12:38:41-XX:XX  Error        miniupnpd  pfctl_get_rules_info: Invalid argument
2026-03-10T12:38:41-XX:XX  Debug        miniupnpd  sdl_index = <index>  <iface>:<mac-redacted>
2026-03-10T12:38:41-XX:XX  Debug        miniupnpd  level=0 type=20

However, it appears the service is working, at least in part, as UPnP/IGD responses to the HomeAssistant Control integration continues without interruption.