oot@opnsense:~ # pkg show miniupnpdminiupnpd-2.1.20190210,1Name : miniupnpdVersion : 2.1.20190210,1Installed on : Wed Oct 16 10:43:18 2019 MSTOrigin : net/miniupnpdArchitecture : FreeBSD:11:amd64Prefix : /usr/localCategories : netLicenses : BSD3CLAUSEMaintainer : squat@squat.noWWW : http://miniupnp.free.fr/Comment : UPnP IGD implementation which uses pf/ipfOptions : CHECK_PORTINUSE: on IPV6 : on LEASEFILE : off PF_FILTER_RULES: on PIE : on RELRO : on SAFESTACK : on UPNP_IGDV2 : off UPNP_STRICT : offShared Libs required: libssl.so.9 libcrypto.so.9Annotations : FreeBSD_version: 1102000 cpe : cpe:2.3:a:miniupnp_project:miniupnpd:2.1.20190210:::::freebsd11:x64 repo_type : binary repository : OPNsenseFlat size : 267KiBDescription :Mini UPnPd is a lightweight implementation of a UPnP IGD daemon. This issupposed to be run on your gateway machine to allow client systems to redirectports and punch holes in the firewall.WWW: http://miniupnp.free.fr/Locked : no
IPv4 * LAN net * * * * * Allow LAN to Internet
Here's the miniupnpd (upnp) package that OPNsense is using. It doesn't use IGDV2 as it's known to cause issues. Same package as FreeBSD but with extra hardening from HardenedBSD:Code: [Select]oot@opnsense:~ # pkg show miniupnpdminiupnpd-2.1.20190210,1Name : miniupnpdVersion : 2.1.20190210,1Installed on : Wed Oct 16 10:43:18 2019 MSTOrigin : net/miniupnpdArchitecture : FreeBSD:11:amd64Prefix : /usr/localCategories : netLicenses : BSD3CLAUSEMaintainer : squat@squat.noWWW : http://miniupnp.free.fr/Comment : UPnP IGD implementation which uses pf/ipfOptions : CHECK_PORTINUSE: on IPV6 : on LEASEFILE : off PF_FILTER_RULES: on PIE : on RELRO : on SAFESTACK : on UPNP_IGDV2 : off UPNP_STRICT : offShared Libs required: libssl.so.9 libcrypto.so.9Annotations : FreeBSD_version: 1102000 cpe : cpe:2.3:a:miniupnp_project:miniupnpd:2.1.20190210:::::freebsd11:x64 repo_type : binary repository : OPNsenseFlat size : 267KiBDescription :Mini UPnPd is a lightweight implementation of a UPnP IGD daemon. This issupposed to be run on your gateway machine to allow client systems to redirectports and punch holes in the firewall.WWW: http://miniupnp.free.fr/Locked : noYour issue has nothing to do with the link you posted to the miniupnpd github source code issues. I'm just guessing because I'm not clear when you say peer to peer gaming. Is this basically playing the same game locally on a LAN? What the link was referring to is this:For BSD distributions miniupnpd won't work well if you have for example 2 Xbox consoles that are playing the exact same game at the same time. Linux doesn't have this particular issue with miniupnpd so that's why a lot of consumer grade routers don't have any issues with multiple consoles since most of the routers are based on Linux. Linux has masquerade to use with iptables and BSD distributions don't so this is so far where the problem stems from with BSD based distros such as FreeBSD. You won't have any issues with a single console though.I have no issues with miniupnpd and OPNsense. It's working great. I suspect the issue is related to your firewall rules. For testing I would disable a lot of them until you isolate which one is causing the problem. Also the only LAN rule I added to OPNsense is a default pass like below:Code: [Select]IPv4 * LAN net * * * * * Allow LAN to InternetIt appears you have your NAT outbound rule properly setup with static ports.