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

    Multiple Local Clients Listening on Same Port

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 531 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.
    • B
      birarda
      last edited by

      I'm setting up a new pfSense box on a mac mini so that I can put squid alongside it as well. Our current configuration has a shortcoming I'm wondering if I can easily fix.

      We have a piece of server software that listens on a specific default port and we run multiple of these from different machines around the office. The state tables only seem to allow one mapping for a local listener on that default port. Whoever has the state is able to send and get back packets from our STUN server (which tells it that it is on our public IP at that default port). Any subsequent servers who try and send out to STUN listening on the same port locally are unable to get their packets out.

      It seems like the pfSense only wants to map a local listener on port 50000 to remote port 50000, and once that's taken up it doesn't do anything to work around it. I would expect it to select a random remote port (or 50001) for the second server. Is there a configuration that enables that behaviour?

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        No, no such configuration. It won't select any random port on your behalf.

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