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

"Address already in use" and lan port locks up

Scheduled Pinned Locked Moved General pfSense Questions
5 Posts 3 Posters 2.0k 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.
  • S
    spetnik
    last edited by Sep 27, 2011, 7:47 PM

    Periodically, our pfSense router will completely stop responding on the LAN side. Unplugging and replugging the LAN cable fixes the issue every time.

    Whenever this happens (as much as several times a day), I see the following (usually several times) in the system log at the time of the issue:

    
    inetd[22782]: 19000/udp: bind: Address already in use
    
    

    Any help would be greatly appreciated.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • M
      Metu69salemi
      last edited by Sep 27, 2011, 8:01 PM

      i don't know what it is, but iana says that tcp/udp 19000 is iGrid server port. Does it ring any bells?

      1 Reply Last reply Reply Quote 0
      • S
        spetnik
        last edited by Sep 27, 2011, 8:20 PM

        Not at all.

        1 Reply Last reply Reply Quote 0
        • S
          spetnik
          last edited by Sep 27, 2011, 8:23 PM

          Actually, it just happened again without that error.

          Any idea why this should happen and just unplugging and replugging the LAN cable would fix it?

          1 Reply Last reply Reply Quote 0
          • J
            jimp Rebel Alliance Developer Netgate
            last edited by Sep 28, 2011, 7:18 PM

            That is from NAT reflection. It's trying to bind the reflection daemon to a high port in order to bounce connections back.

            That message is likely not related to what you are seeing - something else must be happening before that to trigger a reload of the LAN interface. Perhaps it's losing its link (or it believes it is).

            Sounds like it could be a flaky cable/NIC/switch port.

            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
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received