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

    Can't allocate llinfo

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 3.4k 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.
    • P
      peter_richardson
      last edited by stephenw10

      Hi all,

      In Status -> System Logs -> General, I'm getting tonnes of these errors:

      Jan 22 18:04:08	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:08	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:09	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:09	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:10	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:10	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:11	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:11	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:12	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:12	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:13	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:13	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:14	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:14	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:15	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:15	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:16	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:16	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:17	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:17	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:18	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:18	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:19	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:19	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      Jan 22 18:04:20	kernel		arpresolve: can't allocate llinfo for 10.98.88.1 on igb1
      

      I've looked everywhere but I can't find a cause. Any ideas?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by stephenw10

        You get that if you have something defined on that interface that is not responding to ARP. Usually a gateway.

        Steve

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          usually a <motorolla> cable modem when the coax end goes offline

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Yeah, it could be something that's actually stopped responding or it could be an old gateway that you no longer use that is still defined in the config and can be removed.

            Steve

            1 Reply Last reply Reply Quote 0
            • P
              peter_richardson
              last edited by

              Thanks very much guys. I can't figure out where that IP came from, but it must have been handed down via DHCP on that WAN connection. Either way, it's not happening anymore. The WAN connection in question is a fixed-wireless NBN connection, so not a cable modem. Anyway, solved for now, thanks again.

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

                The most common time I see this is when my cable connection renews DHCP and switches to a different subnet. Some states are still pointing at the old gateway which is no longer valid, thus the error.

                I suspect a similar issue happened there, probably as @heper said, it came from the cable modem. Lots of cable modems will hand you a private address if you lose upstream sync.

                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
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.