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

    Log Flooded with "arpresolve: can't allocate llinfo for 192.168.100.1" Messages

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 2.8k 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.
    • E
      EddieA
      last edited by

      OK, so my cable went down this afternoon, for a couple of hours.  During that time, I started to see this message repeated over and over:

      arpresolve: can't allocate llinfo for 192.168.100.1

      I wasn't bothered while the connection was still down, as I thought it could be related to that.  However, now I'm back on line, I'm still seeing these messages, at the average of one every 2 1/2 seconds, and still continuing.

      Is there any information I can collect, before I reboot the box to see if that clears it.

      Cheers.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        It means something (perhaps the gateway monitoring process) is still trying to reach that IP locally, but since your WAN switched back to the "real" IP, it can no longer reach it directly.

        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
        • E
          EddieA
          last edited by

          Yeah, it certainly looks something like that.

          I don't have the log, from when the connection re-made, but here's a snippet from the point it was lost.  In this case, it was reporting the ISP's Gateway as the problem.

          Is there any way that any process, that's using the gateway address, be re-started when the gateway changes, as the log shows:

          dhclient: New Routers (re0): 192.168.100.1
          

          So it does know that it could have changed.

          Cheers.

          llinfolog.txt

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