Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    UPnP Fix for multiple clients/consoles playing the same game

    Gaming
    22
    109
    34.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Saber
      last edited by

      Confirmed, add the Static port mapping back in and both consoles now show NAT Type 2. Weird, wonder what the difference is. I'll have to do another log capture later and see what the differences in behavior are.

      1 Reply Last reply Reply Quote 1
      • S
        Saber
        last edited by Saber

        So I'm definitely at a loss... lol According to the UPnP RFC Sony isn't following the recommendations of how to handle error code 718. But I have no idea why that I see zero change in behavior miniupnp wise, but Playstation is reporting NAT Type 2 with static port mapping enabled, but no change in miniupnp response.

        See below (public IP X'd out.):

        First Playstation to bootup and get online.

        Feb 19 11:20:05 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.19:50995 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.19:50995 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49778 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49779 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49780 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:20:05 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.19:9308 protocol UDP for: 10.0.0.19:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:20:05 Firewall miniupnpd[61453]: UPnP permission rule 1 matched : port mapping accepted
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Check protocol udp for port 9308 on ext_if em0 xxx.xxx.xxx.xxx, 859168D0
        Feb 19 11:20:05 Firewall miniupnpd[61453]: fe00000a:22827 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 00000000:1900 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 00000000:67 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 0100007f:53 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: fe00000a:53 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 0a01080a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:26424 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 1200080a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:1487 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 0502080a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:35710 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 0800080a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:2987 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 00000000:514 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 01e6fa0a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: fe14000a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: fe0a000a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 0100007f:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: fe00000a:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 00000000:123 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 859168d0:1194 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: 00000000:0 00000000:0 <=> 9308 859168d0:9308
        Feb 19 11:20:05 Firewall miniupnpd[61453]: redirecting port 9308 to 10.0.0.19:9308 protocol UDP for: 10.0.0.19:9308 to 9308 (UDP)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: use external ip xxx.xxx.xxx.xxx
        Feb 19 11:20:05 Firewall miniupnpd[61453]: level=0 type=20
        Feb 19 11:20:05 Firewall miniupnpd[61453]: sdl_index = 2 em1:0.c1.a2.20.12.31
        Feb 19 11:20:05 Firewall miniupnpd[61453]: ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1 (ver=1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.19:62353 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.19:62353 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49781 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49782 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:20:05 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.19:49783 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:05 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:05 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:20:05 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.19:9308 protocol UDP for: 10.0.0.19:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:20:05 Firewall miniupnpd[61453]: UPnP permission rule 1 matched : port mapping accepted
        Feb 19 11:20:05 Firewall miniupnpd[61453]: updating existing port mapping 9308 UDP (rhost '') => 10.0.0.19:9308

        Second Playstation to bootup and get online:

        Feb 19 11:20:59 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.18:56783 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.18:56783 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:57528 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:53101 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:63652 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:20:59 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.18:9308 protocol UDP for: 10.0.0.18:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:20:59 Firewall miniupnpd[61453]: UPnP permission rule 0 matched : port mapping accepted
        Feb 19 11:20:59 Firewall miniupnpd[61453]: port 9308 UDP (rhost '') already redirected to 10.0.0.19:9308
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Returning UPnPError 718: ConflictInMappingEntry
        Feb 19 11:20:59 Firewall miniupnpd[61453]: level=0 type=20
        Feb 19 11:20:59 Firewall miniupnpd[61453]: sdl_index = 2 em1:0.c1.a2.20.12.31
        Feb 19 11:20:59 Firewall miniupnpd[61453]: ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1 (ver=1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.18:56271 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.18:56271 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51145 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51146 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:20:59 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51147 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:20:59 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:20:59 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.18:9308 protocol UDP for: 10.0.0.18:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:20:59 Firewall miniupnpd[61453]: UPnP permission rule 0 matched : port mapping accepted
        Feb 19 11:20:59 Firewall miniupnpd[61453]: port 9308 UDP (rhost '') already redirected to 10.0.0.19:9308
        Feb 19 11:20:59 Firewall miniupnpd[61453]: Returning UPnPError 718: ConflictInMappingEntry
        Feb 19 11:21:17 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.18:60736 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:21:17 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:21:17 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.18:60736 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:21:17 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51202 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:21:17 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:17 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51203 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:21:17 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:17 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:21:17 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51204 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:21:17 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:17 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:21:17 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.18:9308 protocol UDP for: 10.0.0.18:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:21:17 Firewall miniupnpd[61453]: UPnP permission rule 0 matched : port mapping accepted
        Feb 19 11:21:17 Firewall miniupnpd[61453]: port 9308 UDP (rhost '') already redirected to 10.0.0.19:9308
        Feb 19 11:21:17 Firewall miniupnpd[61453]: Returning UPnPError 718: ConflictInMappingEntry
        Feb 19 11:21:18 Firewall miniupnpd[61453]: level=0 type=20
        Feb 19 11:21:18 Firewall miniupnpd[61453]: sdl_index = 2 em1:0.c1.a2.20.12.31
        Feb 19 11:21:18 Firewall miniupnpd[61453]: ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1 (ver=1)
        Feb 19 11:21:18 Firewall miniupnpd[61453]: SSDP M-SEARCH from 10.0.0.18:64158 ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
        Feb 19 11:21:18 Firewall miniupnpd[61453]: Single search found
        Feb 19 11:21:18 Firewall miniupnpd[61453]: SendSSDPResponse(): 0 bytes to 10.0.0.18:64158 ST: HTTP/1.1 200 OK^M CACHE-CONTROL: max-age=120^M ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1^M USN: uuid:2fdeeab1-42c9-19cc-8e38-93771b9fc28::urn:schemas-upnp-org:device:InternetGatewayDevice:1^M EXT:^M SERVER: FreeBSD/12.3-STABLE UPnP/1.1 MiniUPnPd/2.2.1^M LOCATION: http://10.0.0.254:2189/rootDesc.xml^M OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01^M 01-NLS: 1645287585^M BOOTID.UPNP.ORG: 1645287585^M CONFIGID.UPNP.ORG: 1337^M ^M
        Feb 19 11:21:18 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51208 : GET /rootDesc.xml (HTTP/1.1)
        Feb 19 11:21:18 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:18 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51209 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:21:18 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:18 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#GetExternalIPAddress
        Feb 19 11:21:18 Firewall miniupnpd[61453]: HTTP REQUEST from 10.0.0.18:51210 : POST /ctl/IPConn (HTTP/1.1)
        Feb 19 11:21:18 Firewall miniupnpd[61453]: Host: 10.0.0.254:2189
        Feb 19 11:21:18 Firewall miniupnpd[61453]: SOAPAction: urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping
        Feb 19 11:21:18 Firewall miniupnpd[61453]: AddPortMapping: ext port 9308 to 10.0.0.18:9308 protocol UDP for: 10.0.0.18:9308 to 9308 (UDP) leaseduration=0 rhost=
        Feb 19 11:21:18 Firewall miniupnpd[61453]: UPnP permission rule 0 matched : port mapping accepted
        Feb 19 11:21:18 Firewall miniupnpd[61453]: port 9308 UDP (rhost '') already redirected to 10.0.0.19:9308
        Feb 19 11:21:18 Firewall miniupnpd[61453]: Returning UPnPError 718: ConflictInMappingEntry

        E 1 Reply Last reply Reply Quote 1
        • E
          encrypt1d @Saber
          last edited by

          @saber
          I think you mentioned in an earlier post that you have a linux firewall that works.

          Is that a similar config? I.e. miniupnpd with pf?

          If it is, you could run it with the same debug level, and perhaps diff the responses from miniupnpd (via packet compare) that say the port is already taken.

          It wouldn't fix anything, but could point to a deeper reason why the playstation isn't trying new ports each time.

          Prior to the patch, my windows/Call of Duty client would randomly pick new ports forever, filling up the UPnP mapping table without bounds. After the patch, it gets the 718 error the first time, picks a new port and the second one sticks.

          S 1 Reply Last reply Reply Quote 0
          • S
            Saber @encrypt1d
            last edited by Saber

            @encrypt1d said in UPnP Fix for multiple clients/consoles playing the same game:

            @saber
            I think you mentioned in an earlier post that you have a linux firewall that works.

            Is that a similar config? I.e. miniupnpd with pf?

            If it is, you could run it with the same debug level, and perhaps diff the responses from miniupnpd (via packet compare) that say the port is already taken.

            It wouldn't fix anything, but could point to a deeper reason why the playstation isn't trying new ports each time.

            Prior to the patch, my windows/Call of Duty client would randomly pick new ports forever, filling up the UPnP mapping table without bounds. After the patch, it gets the 718 error the first time, picks a new port and the second one sticks.

            I've removed the Linux firewall, mostly because I prefer PFSense but I'm really curious now what Linux does differently with how it handles multiple devices asking for the same port. I'll see if I can standup a Linux firewall in a VM and put the Playstation's in the same VLAN and log the miniupnp / packet capture to try and narrow down what the differences are if any.

            To answer your question, Linux isn't the same as Packet Filter. Linux uses IPTables / Netfilter. While BSD / Unix based OS's use Packet Filter.

            I thought for sure I'd see a difference in the miniupnp responses considering both Playstations now show a NAT Type 2 with Static Port mapping enabled, but nothing. Miniupnp responded the exact same way, yet Playstation is reporting a different NAT Type...

            What is kind of funny, if not a little ironic is that Playstation 4 based Operating System is FreeBSD.... lol

            E 1 Reply Last reply Reply Quote 0
            • E
              encrypt1d @Saber
              last edited by

              @saber

              I'll hopefully save you some time on setting up that test firewall. If it will running miniupnpd & pf, it will not work at all if the firewall's wan ip is a private RFC1918 address. I'd say there's low value in choosing that config for your test anyway, since the outcome would likely be the same. I'd go with a different implementation.

              I have a separate thread tracking that bug, and I have proposed a code change to the miniupnp developers. You can catch up on these threads if you are interested.

              https://forum.netgate.com/topic/169773/miniupnp-full-cone-double-natincorrectly-adding-rules
              https://github.com/miniupnp/miniupnp/issues/598

              S 1 Reply Last reply Reply Quote 1
              • S
                Saber @encrypt1d
                last edited by

                @encrypt1d said in UPnP Fix for multiple clients/consoles playing the same game:

                @saber

                I'll hopefully save you some time on setting up that test firewall. If it will running miniupnpd & pf, it will not work at all if the firewall's wan ip is a private RFC1918 address. I'd say there's low value in choosing that config for your test anyway, since the outcome would likely be the same. I'd go with a different implementation.

                I have a separate thread tracking that bug, and I have proposed a code change to the miniupnp developers. You can catch up on these threads if you are interested.

                https://forum.netgate.com/topic/169773/miniupnp-full-cone-double-natincorrectly-adding-rules
                https://github.com/miniupnp/miniupnp/issues/598

                That saved me a TON of time. CGNAT what a pain. I'm spending extra with my ISP to get a Public IP so I'm not behind a CGNAT.

                I'll have to see if I can find some old hardware to throw a Linux Firewall distro on it and see what is different. The problem is always time.

                1 Reply Last reply Reply Quote 0
                • R
                  rivageeza
                  last edited by

                  Had some time to perform further testing just now.

                  I disabled NAT Reflection mode for port forwards and unchecked both Enable NAT Reflection for 1:1 NAT and Enable automatic outbound NAT for Reflection and the patch still works.

                  Tested, PC + PS5, Warzone, both in the same lobby/match at the same time. Both devices reported open NAT.
                  Pre-patch this wasn't possible.

                  chrome_6ZNb7rSQxG.png

                  m0njiM 1 Reply Last reply Reply Quote 0
                  • m0njiM
                    m0nji @rivageeza
                    last edited by

                    @rivageeza and no static port mappings in NAT Outbound Rules?

                    Intel i3-N305 / 4 x 2.5Gbe LAN @2.7.2-Release
                    WAN: Vodafone 1000/50, Telekom 250/40; Switch: USW Enterprise 8 PoE, USW Flex XG, US-8-60W; Wifi: Unifi 6 Lite AP, U6 Mesh

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      rivageeza @m0nji
                      last edited by rivageeza

                      @m0nji nothing to do with the PC or consoles. I used to but I removed them and retested last week.

                      I did create one rule over the weekend but that's for Wireguard, my LAN is 10.10.10.1/24, PS5 is 10.10.10.30 and PC 10.10.10.38.

                      Wireguard rule below

                      chrome_HBHdHD001g.png

                      1 Reply Last reply Reply Quote 1
                      • Y
                        yorke @jimp
                        last edited by

                        @jimp
                        I applied the patch fix for upnp reboot Pfsense deleted all rules
                        under portforward and hybrid outbound NAT Reboot Pfsense,
                        Network address translation all unchecked and disabled,
                        enabled UPnP & NAT-PMP and added ACL rules,
                        Tested upnp with warframe, Call of Duty Vanguard, Overwatch, Borderlands
                        StatusUPnP & NAT-PMP UPnP & NAT-PMP Rules the Playstation connections
                        were listed, but i could not connect to the servers or play.

                        I had to recreate all portforward and hybrid outbound NAT in order
                        for the playstation to connect,NAT-2
                        but now the StatusUPnP & NAT-PMP UPnP & NAT-PMP Rules and
                        Shell Output - pfSsh.php playback pfanchordrill are empty
                        when PlayStation is connected and playing games.

                        BEFORE CREATING portforward and hybrid outbound NAT RULES

                        Shell Output - grep miniupnpd /tmp/rules.debug
                        binat-anchor "miniupnpd"
                        nat-anchor "miniupnpd"
                        rdr-anchor "miniupnpd"
                        anchor "miniupnpd"

                        Shell Output - pfSsh.php playback pfanchordrill
                        listed all connections

                        StatusSystem LogsSystemRouting
                        Mar 2 14:16:17 miniupnpd 18758 HTTP listening on port xxxx
                        Mar 2 14:16:17 miniupnpd 18758 no HTTP IPv6 address, disabling IPv6
                        Mar 2 14:16:17 miniupnpd 18758 Listening for NAT-PMP/PCP traffic on port xxxx

                        I remove and apply the patch following the advice in this post but with no luck
                        I see the connection under Shell Output - pfSsh.php playback pfanchordrill
                        and StatusUPnP & NAT-PMP UPnP & NAT-PMP but cannot connect to server can't play
                        put rules back in place every thing works.

                        jimpJ 1 Reply Last reply Reply Quote 0
                        • jimpJ
                          jimp Rebel Alliance Developer Netgate @yorke
                          last edited by

                          @yorke Please start a new thread for your issue, it doesn't sound related to this. You have some other type of problem with UPnP.

                          Remember: Upvote with the šŸ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                          Need help fast? Netgate Global Support!

                          Do not Chat/PM for help!

                          1 Reply Last reply Reply Quote 0
                          • F
                            fusioncha0s @rivageeza
                            last edited by fusioncha0s

                            @rivageeza I can confirm that this setup after applying the patch works with 2 PCs trying to play Call Of Duty Vanguard, It took rebooting the pfsense box and both my pc's, I can run Call of Duty Vanguard without any problems with both PCs having an open NAT. My setup runs a VLAN with both PCs on that VLAN.

                            Before Applying the Patch - Had same setup as you mention. I could launch Vanguard on PC1 and get to the multiplayer screen and it would show Open but sometimes moderate. While PC1 was sitting in the multiplayer screen waiting to start a match, i tried to launch Vanguard on PC2. I was able to get to the "Connecting to services" screen during bootup until I was met with the "Disconnected from Server" which forces me to exit to desktop.

                            After Applying the Patch - Keeping the same setup you mention. Only difference is I rebooted the pfsense box and also shutdown both computers while the pfsense box was rebooting. Gave it a good 5 minutes and turned both computers on. Started PC1 with vanguard, boots up as usual to multiplayer screen and an Open NAT this time. Booted up PC2 vanguard and it passes the initial "connecting to services" screen and I can get into multiplayer. PC2 also showed and Open NAT.

                            m0njiM 1 Reply Last reply Reply Quote 0
                            • m0njiM
                              m0nji @fusioncha0s
                              last edited by

                              @fusioncha0s he is not using this specific config anymore. you have to scroll down a bit ;)

                              Intel i3-N305 / 4 x 2.5Gbe LAN @2.7.2-Release
                              WAN: Vodafone 1000/50, Telekom 250/40; Switch: USW Enterprise 8 PoE, USW Flex XG, US-8-60W; Wifi: Unifi 6 Lite AP, U6 Mesh

                              F 1 Reply Last reply Reply Quote 0
                              • F
                                fusioncha0s @m0nji
                                last edited by

                                @m0nji thank you for letting me know. I have also disabled NAT Reflection mode for port forwards and unchecked both Enable NAT Reflection for 1:1 NAT and Enable automatic outbound NAT for Reflection with the patch and both my pc's run Vanguard without and issue and contains Open NAT for both. I still have my outbound setup though along with my ACL's.

                                1 Reply Last reply Reply Quote 0
                                • C
                                  chief
                                  last edited by

                                  Can anyone that has this patch applied tell me what result running this test is returning?

                                  https://github.com/automation-stack/nat-discovery

                                  Used to use PF a while back before I noticed it didnā€™t support 2 PCs playing Halo (1 person would get kicked out)

                                  Really want to make the switch to pfsense but the only reason I stay with WRT is because I get full cone NAT, which is the best for gaming.

                                  Thanks!

                                  E 2 Replies Last reply Reply Quote 0
                                  • E
                                    encrypt1d @chief
                                    last edited by

                                    @chief said in UPnP Fix for multiple clients/consoles playing the same game:

                                    I get full cone NAT

                                    @chief You'll want to read up on this thread. Those of us behind a full cone double NAT aren't fully operational with this patch (yet). Once they issue a miniupnpd release, and pfSense includes it, it will work, assuming nothing else gets broken of course. I am running a version I built myself, and both STUN and the "Override WAN address" options work flawlessly on 2.6.0 CE. Without the additional miniupnpd fix, only those with public IPs on their WAN interface can successfully use UPNP.

                                    https://forum.netgate.com/topic/169773/miniupnp-full-cone-double-natincorrectly-adding-rules

                                    1 Reply Last reply Reply Quote 0
                                    • E
                                      encrypt1d @chief
                                      last edited by encrypt1d

                                      @chief said in UPnP Fix for multiple clients/consoles playing the same game:

                                      https://github.com/automation-stack/nat-discovery

                                      Also a note on using a tool like the automation-stack/nat-discovery link posted above:

                                      Without manual changes, this will never result in anything other than a restricted NAT result if run on a host behind the firewall. The tool does not actually make any UPNP port mapping requests, so its tests will not be NATed as desired or allowed back through the firewall. You can probably add the NAT/FW rules yourself to make that work, however ...

                                      The STUN implementation included in miniupnpd includes a very similar check, which runs directly from the firewall itself when STUN is enabled. Assuming you have the firewall rule to allow the inbound connection attempts directly to the firewall WAN IP, it does in fact report a fully open NAT.

                                      Mar 18 10:05:43 firewall miniupnpd[782]: STUN: Performing with host=stun.sipgate.net and port=3478 ...
Mar 18 10:05:43 firewall miniupnpd[782]: resolve_stun_host: stun.sipgate.net:3478 => 217.10.68.152:3478
Mar 18 10:05:43 firewall miniupnpd[782]: perform_stun: local ports 38769 13999 4669 15715
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: waiting 3 secs and 0 usecs
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: received responses: 1
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: waiting 3 secs and 0 usecs
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: received responses: 3
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: waiting 3 secs and 0 usecs
Mar 18 10:05:43 firewall miniupnpd[782]: wait_for_stun_responses: received responses: 4
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: Type 0x0101, Length 68, Magic Cookie 2112a442
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: MAPPED-ADDRESS X.X.X.X:38769
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOURCE-ADDRESS 217.10.68.152:3478
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: CHANGED-ADDRESS 217.116.122.136:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: XOR-MAPPED-ADDRESS X.X.X.X:38769
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOFTWARE Vovida.org 0.96
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: Type 0x0101, Length 68, Magic Cookie 2112a442
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: MAPPED-ADDRESS X.X.X.X:13999
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOURCE-ADDRESS 217.10.68.152:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: CHANGED-ADDRESS 217.116.122.136:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: XOR-MAPPED-ADDRESS X.X.X.X:13999
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOFTWARE Vovida.org 0.96
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: Type 0x0101, Length 68, Magic Cookie 2112a442
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: MAPPED-ADDRESS X.X.X.X:4669
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOURCE-ADDRESS 217.116.122.136:3478
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: CHANGED-ADDRESS 217.116.122.136:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: XOR-MAPPED-ADDRESS X.X.X.X:4669
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOFTWARE Vovida.org 0.96
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: Type 0x0101, Length 68, Magic Cookie 2112a442
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: MAPPED-ADDRESS X.X.X.X:15715
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOURCE-ADDRESS 217.116.122.136:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: CHANGED-ADDRESS 217.116.122.136:3479
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: XOR-MAPPED-ADDRESS X.X.X.X:15715
Mar 18 10:05:43 firewall miniupnpd[782]: parse_stun_response: SOFTWARE Vovida.org 0.96
Mar 18 10:05:43 firewall miniupnpd[782]: STUN: ext interface igb0 with IP address Y.Y.Y.Y is now behind unrestricted NAT 1:1 with public IP address X.X.X.X: Port forwarding is now enabled
                                      C 1 Reply Last reply Reply Quote 0
                                      • C
                                        chief @encrypt1d
                                        last edited by

                                        @encrypt1d Thanks for your reply. The "Override WAN address" is that for just users that are behind a double NAT? Are you saying that if I run the latest pfsense with only the patch would I be on a full cone NAT? My public IP is on my WAN. I wouldn't need the additional miniupnpd fix then right?

                                        I used to use this site to test my full cone nat http://nattest.net.in.tum.de/
                                        It looks like they brought it down and are building a new test that uses javascript instead of the old one that used Java-Applets https://www.net.in.tum.de/research/software/

                                        I found the github test which I now know is not quite the same thing, since it doesn't do upnp port mapping requests. Do you know of any test that does do something like that website that I posted above?

                                        E 1 Reply Last reply Reply Quote 0
                                        • E
                                          encrypt1d @chief
                                          last edited by

                                          @chief said in UPnP Fix for multiple clients/consoles playing the same game:

                                          The "Override WAN address" is that for just users that are behind a double NAT?

                                          Yes, that is correct. Same goes for the STUN option. You wouldn't need either option or the miniupnpd fix if your setup isn't double NAT. When you asked about full cone NAT, I assumed you meant your ISP was NATing.

                                          Full cone NAT is a term which typically applies to your ISP's upstream router. If they are not NATing anything, then it is fully under your control.
                                          This page has a good write-up on the definition:
                                          https://dh2i.com/kbs/kbs-2961448-understanding-different-nat-types-and-hole-punching/
                                          And they have a tool as well, which should show as "permissive" when you run it (assuming you are defaulting your outbound traffic with static port NATing.)
                                          https://clients.dh2i.com/NatTest/

                                          The truth is any NAT test tool you use only tests your existing NAT rules, not what a game will see, because the game will program new NAT/Firewall rules via UPNP that override anything you have configured.

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            Jon8RFC
                                            last edited by

                                            I don't know where to find UPnP-related logs, but I had an odd issue with it not working just now (2022-03-20 ~02:15-02:30, for my own reference). COD:Warzone was showing as "strict NAT"

                                            Filter reload and reset states did not resolve it. The firewall had been rebooted earlier in the day when there were internet issues outside my local network (both with my provider as well as with google overall and their DNS servers), on the WAN side, and the intermittent internet connectivity continued for many hours after the reboot. The internet has been fine for many hours now, but for whatever reason, UPnP wasn't functioning as expected with the patch. It was as if the patch wasn't working.

                                            I don't know if a reboot resolved it alone, because I also reverted the patch and re-applied it before rebooting. But, the issue was resolved and UPnP would port forward normally and COD:Warzone showed as "open NAT" again.

                                            It makes me wonder if there was some weird issue where the firewall got confused and stuck in a bad state in one or more of these scenarios:

                                            • whenever there was a valid WAN IP, but no functional connectivity
                                            • when one of the DNS servers was dysfunctional
                                            • when it flip-flopped between 192.168.100.10 WAN IP (local, assigned by the modem when no IP can be retrieved due to internet connectivity issues) and and the real IP once it was retrieved and assigned, as internet connectivity went up and down over a period of many hours

                                            Just wanted to share that if it's something else worth looking at.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post