Possible bug after switching WAN from DHCP to Static without a reboot
-
pfSense CE 2.9.0-RELEASE (amd64) running on a mini PC
AT&T fiber modem went bad (lightning strike nearby) and after they replaced it, my static addresses didn't work so I fell back to DHCP until they corrected the problem on their end. I then switched back to my static addresses and everything was working fine (I didn't reboot). Later I checked the system log and found lots of these errors:
"arpresolve: can't allocate llinfo for 192.168.1.254 on igc0"
After hours of troubleshooting with ChatGPT, a reboot was all that was necessary to stop this error message.
Seems like a bug to me but I'm not a coder.
Roy... -
@rpsmith said in Possible bug after switching WAN from DHCP to Static without a reboot:
Seems like a bug to me but I'm not a coder.
I guess whoever wrote it is used to Windows and thought everything else worked the same!
-
It indicates a subnet on igc0 no loner exists and an IP address on the interface is not valid. So I assume that IP was the dhcp lease and that subnet doesn't exist?
I would expect it to stop once the lease expires. It's harmless.
-
@stephenw10 ~ A "feature" that fills up your logs with error messages (several per second for over a day) that you spend hours trying to troubleshoot is not "harmless" in my opinion.
-
So what is that IP? That message implies the firewall is trying to use it in a subnet that doesn't exist for some reason.
-
-
Mmm, so presumably it pulled a lease from the local router when it was running dhcp and now that subnet doesn't exist on the firewall after switching to static addresses?
I agree it would be nice if old leases were killed/removed at that point but it's probably safer to just allow them to timeout.
Unless something else is in play here. A WAN VIP perhaps?
-
@stephenw10 ~ You are correct. That was the gateway address the firewall was using when it was configured for DHCP on the WAN. I switched the WAN back to Static the next day after AT&T reloaded my static IP configuration. I also deleted the leftover DHCP Gateway but never rebooted the firewall. So pfsense continued trying to ping the old DHCP gateway for many hours after that gateway had been deleted and I was up and running on my static IPs.
-
Ah it was the gateway. Hmm, interesting. So you could actually see it pinging the old dhcp gateway even after removing it?
-
@stephenw10 ~ I didn't see that but that is what ChatGPT said it had deduced.
-
I assume your static IP is a public subnet so the old gateway is no longer reachable?
-
@stephenw10 ~ Correct.
Privacy Policy · Cookie Policy