"arpresolve: can't allocate llinfo for <gw_ip> on igb0" ??
-
Hello
I see this error in pfsense logs after 2.5.0 upgrade
arpresolve: can't allocate llinfo for <gw_ip> on igb0
Found this solution => add my ISP GW IP address (<gw_ip>) to the "Reject leases from" field of Interfaces > WAN > DHCP Client Configuration
Is it still valid?
NOTE: <gw_ip> is my Gateway from my ISP (as 185.180.64.1)
-
Warning: old thread revival here...
I experienced a similar problem this morning after a planned maintenance outage on my ISP (Xfinity/Comcast). After the outage, I rebooted the Modem and my pfSense pulled a new WAN IP address (DHCP), however, the IPv4 Gateway monitor was showing 100% loss and I could not get out to the internet via IPv4.
The IPv6 interface seemed to be working fine.Looking at the System Logs I noticed this message repeating many times:
Sep 16 05:38:00 kernel arpresolve: can't allocate llinfo for 71.226.124.1 on igb0
I attempted to ping the Comcast GW (71.226.124.1) from my phone via LTE but got 100% packet loss result.
Does this mean the Comcast gateway is down?Investigating further, I looked at Status/Interfaces/WAN and observed that they have me allocated on a /22 subnet. So I changed the Gateway monitor IP to 71.226.126.1 which is on the same /24 block as my WAN IP. I also rebooted my pfSense.
Now the gateway monitor is green and I can access the internet via IPv4.
Looking at the logs now, I am periodically seeing this message:/interfaces.php: Removing static route for monitor 71.226.126.1 and adding a new route through 71.226.124.1
What does all this mean? Should I try to contact Comcast and submit a trouble ticket?
Thanks in advance.
Hardware: Netgate SG-5100 & Motorola MB8600
Cross-posted on Xfinity forums as well: https://forums.xfinity.com/conversations/your-home-network/cannot-ping-comcast-gateway-ip-after-maintenance-outage/6324da992ff2c66589ffe60f
-
@azdeltawye said in "arpresolve: can't allocate llinfo for <gw_ip> on igb0" ??:
I attempted to ping the Comcast GW (71.226.124.1) from my phone via LTE but got 100% packet loss result.
Does this mean the Comcast gateway is down?No. ISP gateways do not have to be accessible externally like that. They only need to respond from the customer side.
You should either use the actual gateway IP or something external like 8.8.8.8 or 1.1.1.1 as the monitoring IP. You have no idea what 71.226.126.1 is.
Steve
-
Thanks Steve. I'll change the monitoring IP.
Is there any value in rejecting this lease IP range as suggested in the original OPs post?
-
No. You need to accept a lease from the ISP, usually from the gateway. Rejecting that would prevent any connection.
Steve
-
@stephenw10
Yeah I realize that. What I meant was if I reject this particular problematic Gateway, it would present another gateway from the DHCP pool for my system to choose. Surely they have many other gateways in my area. I think this particular ASN is a /12...BTW I still cannot ping this gateway when I am on their network. Something is not right. Still waiting for a response from a Comcast/Xfininty representative.
-
That field does not reject gateways it rejects leases from DHCP servers. I expect there to be only one so if you reject leases from it you will get nothing.
The gateway does not have to respond to ping. Some ISP gateways do not. In that situation you have to use an external IP for monitoring.
Steve
-
Got it.
Thanks again!Switched monitoring IP to the Comcast primary DNS server: 75.75.75.75