Have I discovered a bug?
-
My cable internet provider changed my IP assignment, and the log started filling up with these error messages: (Went for hours-I noticed it when I saw the daily report).
Mar 22 12:49:50 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:50 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:50 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:49 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:49 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:49 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:48 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0
Mar 22 12:49:48 kernel arpresolve: can't allocate llinfo for 99.x.x.1 on em0The IP address 99.x.x.1 is the new gateway IP.
The messages finally went away when I pulled the plug on the cable modem to force it to reboot.
Is this normal, or have I discovered a bug?
-
It's normal. You usually have to bounce the modem when your ISP reassigns an IP address.
-
@KOM said in Have I discovered a bug?:
It's normal. You usually have to bounce the modem when your ISP reassigns an IP address.
Thanks for the quick answer...
It's not a big deal, but I''m wondering is there a reason that the message doesn't automatically reset?
-
No idea.
-
What is the triggering event that would make WAN reset itself? Did it lose link? Did its DHCP lease expire?
What you experienced was probably some sort of "flag day" event. ISP made a change that required customer action and didn't communicate what was necessary.
-
@Derelict said in Have I discovered a bug?:
What is the triggering event that would make WAN reset itself? Did it lose link? Did its DHCP lease expire?
What you experienced was probably some sort of "flag day" event. ISP made a change that required customer action and didn't communicate what was necessary.
Good point... I don't know... I just descovered that the ISP decided to reassign my IP (likely block of IPs for the neighbourhood). Everything reconnected OK, it was just the old gateway remained in the arp table and it couldn't find a MAC address since it had changed IP. The only side effect was that it confused my VOIP ATA... I could make calls, but my phone didn't ring. I had to reboot the ATA.
I've never heard the term "flag day" event-can you pleas explain?
Anyway, I'm glad that pfSense made me aware of the IP change even if it didn't do it with a precise message-something that a consumer router wouldn't likely do.
-
RFC4192 says: A "flag day" is a procedure in which the network, or a part of it, is changed during a planned outage, or suddenly, causing an outage while the network recovers.
-
it is normal , the message wont reset automatically.
