Hi, 

I'm experiencing an issue where miniupnpd is reporting back to the client that it failed to open the port, specifically:

```
[05:29] andrew@neon ~> upnpc -e "upnpc test" -a 10.0.0.10 5001 5001 TCP
upnpc: miniupnpc library test client, version 2.2.7.
 (c) 2005-2024 Thomas Bernard.
More information at https://miniupnp.tuxfamily.org/ or http://miniupnp.free.fr/

List of UPNP devices found on the network :
 desc: http://10.0.0.1:5000/rootDesc.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://10.0.0.1:5000/ctl/IPConn
Local LAN ip address : 10.0.0.10
ExternalIPAddress = 116.255.34.255
GetSpecificPortMappingEntry() failed with code 714 (NoSuchEntryInArray)
```
```

But if i check the pf anchor it did indeed create it:

```
[05:32] andrew@apu ~> sudo pfctl -a miniupnpd -s nat
rdr pass quick on igb0 inet proto tcp from any to any port = 5001 keep state label "upnpc test" rtable 0 -> 10.0.0.10 port 5001
```

This is creating an issue where some appliance devices (eg my xbox one) believes it can't open ports.  I reported this upstream https://github.com/miniupnp/miniupnp/issues/729

I was advised to test again with 2.3.6, which i built from the upstream tarball and `./configure --ipv6 --firewall=pf` and it appears to have resolved the issue.  It would be great if this port could by bumped to 3.3.6.