arpresolve: can't allocate llinfo for 192.168.100.1

Orlie

I've upgraded my cable modem to a Technicolor TC4400. Netgate SG-2220 appliance is my router.

I'm losing access to the Internet frequently. I'm seeing this repeated in the logs:

192.168.100.1 is the device info/Config page for my modem.

Searching the forum I noticed this thread with the same problem but as I am a bit of a newb, I wasn't sure the correct course of action to take as there are a few suggestions.
https://forum.netgate.com/topic/149298/arpresolve-can-t-allocate-llinfo-for-192-168-100-1?loggedin=true

Anyone have any advice? Thanks/

stephenw10

Usually you see that when the modem loses sync with the cable connection and starts handing out it's own IP via DHCP. If you looks back in the logs you will probably see WAN has an IP in that range at some point.
Then when the cable connection comes back it stops responding but doesn't bounce the Ethernet connection so pfSense is still trying to find it as a gateway.

In the Interfaces > WAN in the DHCP settings enter 192.168.100.1 in the 'Reject leases from' field.

Check the gateway logs to confirm it is actually losing the WAN gateway. Then investigate why the modem is apparently losing sync.

Steve

Orlie

Hi Steve,
Thanks for the advice. I've added the IP to the Reject Leases field. No drops today so maybe too early to say fixed but I'm an optimist.

Checking the gateway logs I'm seeing these two entries a bunch of times, any clues?

(IPs obfuscated on purpose)

WAN_DHCP 24.xxx.xxx.161: sendto error: 65

send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 24.xxx.xxx.161 bind_addr 24.xxx.xxx.185 identifier "WAN_DHCP "

SteveITS

@stephenw10 said in arpresolve: can't allocate llinfo for 192.168.100.1:

In the Interfaces > WAN in the DHCP settings enter 192.168.100.1 in the 'Reject leases from' field.

For the record, in AT&T uVerse that will block the passthrough public IP. Otherwise I've seen the same symptom. Restarting pfSense will also "fix" it. It triggers several times per second for me so lots of log writes. It would be helpful if pfSense would "let go" of the old IP faster when it gets a new DHCP IP?

@Orlie said in arpresolve: can't allocate llinfo for 192.168.100.1:

WAN_DHCP 24.xxx.xxx.161: sendto error: 65

Generally that your router can't send the ping to the WAN_DHCP gateway (lost connection).

stephenw10

@Orlie said in arpresolve: can't allocate llinfo for 192.168.100.1:

send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 24.xxx.xxx.161 bind_addr 24.xxx.xxx.185 identifier "WAN_DHCP "

That is dpinger logging the values it's using when it starts. So usually that is when the WAN comes back up or you get a new WAN for some reason.

Steve