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

    miniUPnPd not working since 23.09 (worked in 23.05.1)

    Scheduled Pinned Locked Moved General pfSense Questions
    27 Posts 5 Posters 3.9k Views
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, so you don't see any errors until the NAS tries to open port forwards?

      P 2 Replies Last reply Reply Quote 0
      • P
        PiAxel @stephenw10
        last edited by

        @stephenw10
        maybe, but it was working with 23.05.1
        I have an ip intercom which needs upnp and it doesn't work.
        in the logs I see

        Nov 16 21:48:59	miniupnpd	69075	Port forwarding is now disabled
        

        how can I enable it ?

        1 Reply Last reply Reply Quote 0
        • P
          PiAxel @stephenw10
          last edited by PiAxel

          @stephenw10
          I find a solution
          I changed in /var/etc/miniupnpd.conf
          port=2189 to port=1900
          and now It works
          there are some rules in upnp status

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, interesting. That's not any different to 23.05.1. That's the port miniupnpd itself uses.
            https://docs.netgate.com/pfsense/en/latest/services/upnp.html#upnp-nat-pmp

            johnpozJ 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @stephenw10
              last edited by johnpoz

              @stephenw10 so I not a fan or a user of upnp.. But I just enabled it to have it create the .conf file and yup it put in 2189 which doesn't make any sense

              [23.09-RELEASE][admin@sg4860.local.lan]/var/etc: cat miniupnpd.conf 
              ext_ifname=igb1
              port=2189
              listening_ip=igb4
              secure_mode=yes
              presentation_url=https://192.168.200.1:8443/
              uuid=da5797c4-0daa-f185-0994-a6afe6c2ecb
              serial=DA5797C4
              model_number=23.09-RELEASE
              enable_upnp=yes
              enable_natpmp=yes
              [23.09-RELEASE][admin@sg4860.local.lan]/var/etc: 
              

              But it is listening on 1900 as well

              [23.09-RELEASE][admin@sg4860.local.lan]/var/etc: sockstat | grep 1900
              root     miniupnpd  77102 7   udp4   *:1900                *:*
              [23.09-RELEASE][admin@sg4860.local.lan]/var/etc: sockstat | grep 2189
              root     miniupnpd  77102 4   tcp6   *:2189                *:*
              root     miniupnpd  77102 6   tcp4   *:2189                *:*
              [23.09-RELEASE][admin@sg4860.local.lan]/var/etc: 
              

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Because that's the port minipnpd listens on the http:
                curl http://192.168.200.1:2189/rootDesc.xml

                As far as I know that can be omitted entirely and miniupnpd will use a random port.

                Setting it to 1900 is probably a bad idea since it should already be listening there. Though for udp.

                johnpozJ 1 Reply Last reply Reply Quote 0
                • johnpozJ
                  johnpoz LAYER 8 Global Moderator @stephenw10
                  last edited by johnpoz

                  @stephenw10 were they come up with that port, I don't show it registered as that.. Pretty sure radware has that registered for something they do radware-rpm-s

                  And I concur - setting that port in the config to 1900 prob not a good idea, and I would think really had nothing to do with his issue.. UPnP is UDP.

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.8, 24.11

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Yeah, unclear. Looks like they removed that over on the other side after deciding it was pointless setting it.

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      PiAxel @stephenw10
                      last edited by PiAxel

                      @stephenw10
                      I disable port in the conf file and now miniupnpd use a random port.
                      It's still working
                      How can I know if the port 2189 is already use by another service ?

                      johnpozJ 1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator @PiAxel
                        last edited by

                        @PiAxel said in miniUPnPd not working since 23.09 (worked in 23.05.1):

                        How can I know if the port 2189 is already use by another service ?

                        do the command I did with sockstat

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        P 1 Reply Last reply Reply Quote 1
                        • P
                          PiAxel @johnpoz
                          last edited by

                          @johnpoz
                          ok thank you
                          but it is not used...

                          johnpozJ 1 Reply Last reply Reply Quote 0
                          • johnpozJ
                            johnpoz LAYER 8 Global Moderator @PiAxel
                            last edited by

                            @PiAxel well if its running and you want to know what port it is using do

                            sockstat | grep miniupnpd

                            An intelligent man is sometimes forced to be drunk to spend time with his fools
                            If you get confused: Listen to the Music Play
                            Please don't Chat/PM me for help, unless mod related
                            SG-4860 24.11 | Lab VMs 2.8, 24.11

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              PiAxel @johnpoz
                              last edited by

                              @johnpoz

                              /root: sockstat | grep miniupnpd
                              root     miniupnpd  36049 4   tcp6   *:51760               *:*
                              root     miniupnpd  36049 5   dgram  -> /var/run/log
                              root     miniupnpd  36049 6   tcp4   *:51760               *:*
                              root     miniupnpd  36049 7   udp4   *:1900                *:*
                              root     miniupnpd  36049 8   stream /var/run/php-fpm.socket
                              root     miniupnpd  36049 9   udp6   *:1900                *:*
                              root     miniupnpd  36049 10  udp4   192.168.1.1:55617     *:*
                              root     miniupnpd  36049 11  udp6   *:64174               *:*
                              root     miniupnpd  36049 12  stream /var/run/php-fpm.socket
                              root     miniupnpd  36049 14  udp4   192.168.1.1:5351      *:*
                              root     miniupnpd  36049 15  udp6   *:5351                *:*
                              
                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                That seems fine. I have no explanation as to why changing the port value to 1900 seemed to allow it work though. That really shouldn't have changed anything significant.

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  PiAxel @stephenw10
                                  last edited by

                                  thank you very much for your help !

                                  P 1 Reply Last reply Reply Quote 0
                                  • P
                                    PiAxel @PiAxel
                                    last edited by

                                    @PiAxel
                                    The problem is back since update 23.09.1
                                    everything seems to be working fine but neither my NAS nor any other network device can open a port via upnp. the games on my pc say that I am in strict NAT.
                                    In pfsense stat upnp is empty.
                                    f6d07078-2e0b-47d8-a9c1-71c6161f3078-image.png
                                    541c839e-57d0-426d-9a96-61cfbb8ade8e-image.png
                                    I try with port=0 instead of 2189 but it didn't change anything
                                    2d0856ea-155c-4fc6-a6db-6da1770a278c-image.png
                                    b716ca21-8f88-4b96-9147-d7b885ee4fd2-image.png
                                    Tell me what you want to know about my pfsense.

                                    Please help me!

                                    P 1 Reply Last reply Reply Quote 0
                                    • P
                                      PiAxel @PiAxel
                                      last edited by

                                      I have disabled STUN and there is no more message with "port forwarding is now disabled" but that still doesn't work.

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        @PiAxel said in miniUPnPd not working since 23.09 (worked in 23.05.1):

                                        STUN: ext interface ix0 has now public IP address external ipv4 but firewall filters incoming connections set by miniunnpd

                                        That implies you have something set that is preventing miniupnpd opening inbound ports somehow.

                                        Do you have a custom block all rule on WAN or as Floating?

                                        P 1 Reply Last reply Reply Quote 1
                                        • P
                                          PiAxel @stephenw10
                                          last edited by

                                          @stephenw10
                                          No, I don't have any rule on WAN or as floating to block all

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            Could be something upstream blocking it then. Try to send some traffic to your WAN from some external address and see if it arrives in a packet capture.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.