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

    FreeBSD Packages

    Scheduled Pinned Locked Moved pfSense Packages
    2 Posts 2 Posters 1.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.
    • J
      JoP
      last edited by

      I hope I do not get flamed by posting this into "Packages"…

      I did a "pgk_add -r dhis" from the prompt and it went OK.

      My problem is that I can not get this to run,

      "dhid: failed to open incoming udp socket on port 58800"

      I have used the dhid client successfully on a LAN machine with some UDP rules for port 58800 but when I move this to the pfSense itself and changes the IP for the rule to 127.0.0.1 (also tried the LAN-IP of pfSense) I always get the same error.

      My question:
      Can I create a such a rule?
      (or am I violating the pfSense platform by doing this in the first place?)

      Of course, the best solution would be if the DHID came as a pfSense-package or added under the dynDNS menu

      /JoP

      /JoP

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

        I've never used 'dhis.' However I have experienced some of what you are going through when I built the FreeSWITCH package for pfSense.

        By default FreeSWITCH binds to the WAN IP.  I've also tried connecting to it un-successfully on 127.0.0.1. I did however connect to it on the WAN or the LAN.

        @JoP:

        "dhid: failed to open incoming udp socket on port 58800"

        By default on the LAN interface every port is open. But just for a test you might try a different port like 5880 or something.

        @JoP:

        (or am I violating the pfSense platform by doing this in the first place?)

        No violation.

        @JoP:

        Of course, the best solution would be if the DHID came as a pfSense-package or added under the dynDNS menu

        If you want to make a pfSense package out of it when you have it working you are free to do so.

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