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

    Kernel: arpresolve: can't allocate llinfo for

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 2.2k 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.
    • H
      heper
      last edited by

      Hi,

      I have kind of a situation where i have 2 WAN connections

      TIER1: WAN_TELENET
      TIER2: WAN_SCARLET

      We've been losing internet connection multiple occasions when the Tier2 is down, then afterwards then Tier1 wan has a hickup.
      For some reason i get this ?

      The arpresolve messages keep flooding logs until someone hits release/Renew in the interfaces status pages.

      Can someone provide me with a solution to this problem?

      Kind regards

      Jeroen
      edit: also note that during that time another computer directly connected to the cable modem is able to keep pinging to 8.8.8.8 without interuption

      
Nov 24 08:55:36 pfsense dhclient: Creating resolv.conf
Nov 24 08:59:01 pfsense apinger: ALARM: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
Nov 24 08:59:11 pfsense check_reload_status: Reloading filter
Nov 24 08:59:16 pfsense php: : MONITOR: WAN_TELENET is down, removing from routing group
Nov 24 08:59:16 pfsense php: : Gateways status could not be determined, considering all as up/active.
Nov 24 09:01:03 pfsense apinger: alarm canceled: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
Nov 24 09:01:13 pfsense check_reload_status: Reloading filter
Nov 24 09:03:18 pfsense php: /index.php: Successful webConfigurator login for user 'admin' from 172.16.10.97
Nov 24 09:03:18 pfsense php: /index.php: Successful webConfigurator login for user 'admin' from 172.16.10.97
Nov 24 09:07:27 pfsense dhclient[11900]: connection closed
Nov 24 09:07:27 pfsense dhclient[11900]: connection closed
Nov 24 09:07:27 pfsense dhclient[11900]: exiting.
Nov 24 09:07:27 pfsense dhclient[11900]: exiting.
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:29 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
......
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense dhclient: PREINIT
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense dhclient[53791]: DHCPREQUEST on em0 to 255.255.255.255 port 67
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:31 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:32 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:32 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
.......
Nov 24 09:07:35 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:35 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:35 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:36 pfsense dhclient[53791]: DHCPREQUEST on em0 to 255.255.255.255 port 67
Nov 24 09:07:36 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:36 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
......
Nov 24 09:07:38 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:38 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:38 pfsense apinger: ALARM: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
Nov 24 09:07:39 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:39 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
......
Nov 24 09:07:42 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:42 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:43 pfsense dhclient[53791]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 2
Nov 24 09:07:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:43 pfsense dhclient[53791]: DHCPOFFER from XXX.XXX.192.1
Nov 24 09:07:43 pfsense dhclient: ARPSEND
Nov 24 09:07:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
......
Nov 24 09:07:44 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:44 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:44 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:44 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient: ARPCHECK
Nov 24 09:07:45 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient[53791]: DHCPREQUEST on em0 to 255.255.255.255 port 67
Nov 24 09:07:45 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient[53791]: DHCPACK from XXX.XXX.192.1
Nov 24 09:07:45 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient: BOUND
Nov 24 09:07:45 pfsense dhclient: Starting add_new_address()
Nov 24 09:07:45 pfsense dhclient: ifconfig em0 inet XXX.XXX.213.131 netmask 255.255.192.0 broadcast 255.255.255.255
Nov 24 09:07:45 pfsense dhclient: New IP Address (em0): XXX.XXX.213.131
Nov 24 09:07:45 pfsense dhclient: New Subnet Mask (em0): 255.255.192.0
Nov 24 09:07:45 pfsense dhclient: New Broadcast Address (em0): 255.255.255.255
Nov 24 09:07:45 pfsense dhclient: New Routers (em0): XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient: Adding new routes to interface: em0
Nov 24 09:07:45 pfsense dhclient: /sbin/route add default XXX.XXX.192.1
Nov 24 09:07:45 pfsense dhclient: Creating resolv.conf
Nov 24 09:07:45 pfsense check_reload_status: rc.newwanip starting em0
Nov 24 09:07:45 pfsense dhclient[53791]: bound to XXX.XXX.213.131 -- renewal in 3235 seconds.
Nov 24 09:07:45 pfsense apinger: alarm canceled: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
Nov 24 09:07:48 pfsense check_reload_status: Reloading filter
Nov 24 09:07:50 pfsense php: : rc.newwanip: Informational is starting em0.
Nov 24 09:07:50 pfsense php: : rc.newwanip: on (IP address: XXX.XXX.213.131) (interface: wan) (real interface: em0).
Nov 24 09:07:50 pfsense php: : ROUTING: setting default route to XXX.XXX.192.1
Nov 24 09:07:50 pfsense php: : Removing static route for monitor 8.8.8.8 and adding a new route through XXX.XXX.192.1
Nov 24 09:07:50 pfsense check_reload_status: Reloading filter
Nov 24 09:07:50 pfsense apinger: Exiting on signal 15.
Nov 24 09:07:51 pfsense dnsmasq[41278]: reading /etc/resolv.conf
Nov 24 09:07:51 pfsense dnsmasq[41278]: using nameserver 193.74.208.135#53
Nov 24 09:07:51 pfsense dnsmasq[41278]: using nameserver 8.8.4.4#53
Nov 24 09:07:51 pfsense dnsmasq[41278]: using nameserver 195.130.130.132#53
Nov 24 09:07:51 pfsense dnsmasq[41278]: using nameserver 8.8.8.8#53
Nov 24 09:07:51 pfsense dnsmasq[41278]: ignoring nameserver 127.0.0.1 - local interface
Nov 24 09:07:51 pfsense dnsmasq[41278]: ignoring nameserver 127.0.0.1 - local interface
      1 Reply Last reply Reply Quote 0
      • H
        heper
        last edited by

        Last week i've disabled tier2 wan interface + removed the failover gw group.

        the arpresolve errors still occur frequently (once a week). release/renew of the wan interface solves it.

        Anyone have a clue ?

        Dec  5 14:45:48 pfsense check_reload_status: Syncing firewall
Dec  5 15:25:43 pfsense dhclient: EXPIRE
Dec  5 15:25:43 pfsense dhclient: Deleting old routes
Dec  5 15:25:43 pfsense dhclient: PREINIT
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.G
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
.....
Dec  5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:52 pfsense apinger: ALARM: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
Dec  5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
.....
Dec  5 15:26:02 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:02 pfsense check_reload_status: Reloading filter
Dec  5 15:26:02 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
.....
Dec  5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:07 pfsense php: : The command '/sbin/route change -inet default dynamic' returned exit code '68', the output was 'route: bad address: dynamic'
Dec  5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:07 pfsense php: : ERROR!  PPTP enabled but could not resolve the $pptpdtarget
Dec  5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:08 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
....
Dec  5 15:26:15 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:15 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:16 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW
Dec  5 15:26:44 pfsense dhclient: FAIL
Dec  5 15:26:47 pfsense dhclient: ARPSEND
Dec  5 15:26:49 pfsense dhclient: ARPCHECK
Dec  5 15:26:49 pfsense dhclient: BOUND
Dec  5 15:26:49 pfsense dhclient: Starting add_new_address()
Dec  5 15:26:49 pfsense dhclient: ifconfig em0 inet XXX.XXX.WAN.IP netmask 255.255.192.0 broadcast 255.255.255.255
Dec  5 15:26:49 pfsense dhclient: New IP Address (em0): XXX.XXX.WAN.IP
Dec  5 15:26:49 pfsense dhclient: New Subnet Mask (em0): 255.255.192.0
Dec  5 15:26:49 pfsense dhclient: New Broadcast Address (em0): 255.255.255.255
Dec  5 15:26:49 pfsense dhclient: New Routers (em0): XXX.XXX.WAN.GW
Dec  5 15:26:49 pfsense dhclient: Adding new routes to interface: em0
Dec  5 15:26:49 pfsense dhclient: /sbin/route add default XXX.XXX.WAN.GW
Dec  5 15:26:49 pfsense dhclient: Creating resolv.conf
Dec  5 15:26:49 pfsense check_reload_status: rc.newwanip starting em0
Dec  5 15:26:49 pfsense apinger: alarm canceled: WAN_TELENET(8.8.8.8)  *** WAN_TELENETdown ***
        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.