WAN interface bounce caused pfSense GUI to hang
-
If I'm reading this log correctly, it appears that my ISP rebooted my wan modem, either that or it just lost the link state for some reason. After this happened I lost internet connectivity and could not access the GIU. I was able to ssh into the box and reboot which resolved the issue but I'm wondering what happened. Could someone help interpret this log snippet or direct me to another log that might get to the bottom of this?
Jun 6 10:59:36 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:36 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:36 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:34 check_reload_status rc.newwanip starting igb0 Jun 6 10:59:35 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:35 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:35 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:34 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:34 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:34 kernel arpresolve: can't allocate llinfo for 82.21.255.1 on igb0 Jun 6 10:59:23 check_reload_status Linkup starting igb0 Jun 6 10:59:24 kernel igb0: link state changed to UP Jun 6 10:59:16 check_reload_status Linkup starting igb0 Jun 6 10:59:16 kernel igb0: link state changed to DOWN Jun 6 10:38:15 php-fpm 43444 [pfBlockerNG] Starting cron process. -
@asv345h said in WAN interface bounce caused pfSense GUI to hang:
If I’m reading this log correctly, it appears that my ISP rebooted my wan modem
Interface igb0 went down, and comes back several seconds later.
Probably the box in front of pfSense initiated this - and also probably, it restarted.
It's known that ISP modems & routers can update themselves, and they restart afterwards, that's normal and ok. I do not thing this happens often, though ...The other 99,99 % of these kind of salutations is a faulty modem, bad physical connection - bad network cable or even a bad interface (both sides).
@asv345h said in WAN interface bounce caused pfSense GUI to hang:
After this happened I lost internet connectivity and could not access the GIU
This is not normal at all.
I can rip out the RJ45 cable, the one that represent my WAN interface on my pfSense device anytime. My pfSense GUI will still work.
I advise you to "repair" that (redo the settings, the correct way **). Keep in mind that a pfSense freshly installed with default settings, with a minimal WAN settings, will not react like that.
It's known that pfSense could somewhat miss the fact that a lost connection comes back, and (example) the DHCP-client lease against the ISP isn't renewed. Some (still) recent threads mention this issue, but again : this would not kill the GUI.** Without any proof, I think about a bad DNS situation.
-
I've rebooted the ISP modem and pulled the ethernet cable out many times as well, and, like you said, no problem. I thought dns at first also but tried to access the gui via ip and it also hung. DNS was also affected though as I could not do an nslookup. Weird?!
