pfSense Gold Subscription

Author Topic: Log Flooded with "arpresolve: can't allocate llinfo for 192.168.100.1" Messages  (Read 1104 times)

0 Members and 1 Guest are viewing this topic.

Offline EddieA

  • Full Member
  • ***
  • Posts: 151
    • View Profile
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.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 14934
    • View Profile
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.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline EddieA

  • Full Member
  • ***
  • Posts: 151
    • View Profile
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:
Code: [Select]
dhclient: New Routers (re0): 192.168.100.1So it does know that it could have changed.

Cheers.