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

Miniupnpd: Can't find in which sub network the client is

Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
4 Posts 3 Posters 5.6k 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.
  • Z
    zandr
    last edited by Mar 25, 2012, 4:30 PM

    Not sure if this is 2.1 specific, since this is also the first time I've configured pfSense with a network larger than a /24.

    The logs on my machine are full of:
    miniupnpd[4556]: Can't find in which sub network the client is

    A thread in the openwrt forum suggests that the listening_ip lines in miniupnpd.conf need to be in CIDR notation, which they are not on pfSense.

    I'd try fixing up the file manually, but it's not clear how to restart the service without going through the config page in the GUI, which rewrites the config.

    1 Reply Last reply Reply Quote 0
    • M
      majikthise
      last edited by Apr 18, 2012, 11:57 AM

      using Diagnostics -> Edit File, load '/var/etc/miniupnpd.conf'

      ext_ifname=fxp1
      port=2189
      listening_ip=10.0.0.1/20
      packet_log=yes
      presentation_url=http://10.0.0.1/
      uuid=dc2bcb95-fcb0-4fff-101d-4fcd6dc4cfa
      serial=DC2BCB95
      model_number=2.1-DEVELOPMENT

      allow 1024-65535 10.0.1.200/20 1024-65535
      allow 1024-65535 10.0.4.200/20 1024-65535
      allow 1024-65535 10.0.4.210/20 1024-65535
      deny 0-65535 0.0.0.0/0 0-65535
      enable_upnp=yes
      enable_natpmp=yes

      add the CIDR info to the listening_ip line, in the above mine is /20
      you restart the miniupnpd server using Status -> Services

      If you don't see services register, try making sure that you've included the CIDR info in the allow fields. for me, it was only after I did this that the report showed up

      1 Reply Last reply Reply Quote 0
      • J
        jimp Rebel Alliance Developer Netgate
        last edited by Apr 18, 2012, 3:38 PM

        Looking at the source of miniupnpd it seems it would be best to put the CIDR mask there. Shouldn't be too hard to fix up on our end.

        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
        • J
          jimp Rebel Alliance Developer Netgate
          last edited by Apr 18, 2012, 5:21 PM

          databeestje committed a fix for this, seems to work:

          https://github.com/bsdperimeter/pfsense/commit/eaa477d2d658a49e102298d939d17350f3788765

          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
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            [[user:consent.lead]]
            [[user:consent.not_received]]