pfSense not responding to network after ISP outage

Gertjan

@jamie said in pfSense not responding to network after ISP outage:

beep and logged a couple of messages to the console but then nothing more happened and it didn't reboot.

That part, on the console access, from initial power up, going trough initial drive detection, and booting from a selected boot drive, and eventually booting pfSense, holds the info about what is happening.
Can you show it ?

stephenw10

Did it come up with an IP or gateway that conflicted with any other locally defined subnet? You have obscured the IPs so we can't check.

jamie

@Gertjan please correct me if I'm wrong but are you saying that the log of the next boot contains information on why the shutdown prior failed? I would think that is unlikely.

@stephenw10 I've only obscured the WAN and upstream gateway IPs, both of which I've just done a find and replace on so anywhere you see XWANX, this is referencing a single IP address, same for XGWX. My WAN IP is static and was not one of my local subnets (which are all 10.x.x.x). Equally my gateway IP was correctly my ISP's gateway (another public address).

stephenw10

@jamie said in pfSense not responding to network after ISP outage:

Equally my gateway IP was correctly my ISP's gateway (another public address).

Ok. I asked because ISPs using PPPoE commonly use a private IP address for the upstream gateway and that cannot conflict

jamie

Ah ok. Mine is a public address, I looked it up and confirmed it's in a range owned by my ISP.

stephenw10

Hmm, what NICs are you using? On LAN especially? Hard to see anything that would prevent it pinging out from the LAN as long as LAN clients still had a valid IP address.

jamie

Here I'm using a PC Engines APU2 system with 3x onboard Intel I210 gigabit NICs. Some LAN clients still had their DHCP addresses, others were failing to DHCP as it wasn't getting served. Equally I tried pinging something with a known static IP and nothing.

stephenw10

Hmm, shouldn't be an issue with the NICs on that. Unless it's actually a hardware problem.

I'd try something low level. Start a continuous ping from the command line to something static on the LAN. Run a packet capture on the LAN interface to make sure it's actually sending packets.

Gertjan

@jamie said in pfSense not responding to network after ISP outage:

please correct me if I'm wrong but are you saying that the log of the next boot contains information on why the shutdown prior failed? I would think that is unlikely.

Correct.
But I was asking for this :

@jamie said in pfSense not responding to network after ISP outage:

nothing more happened and it didn't reboot.

For this

@jamie said in pfSense not responding to network after ISP outage:

... contains information on why the shutdown prior failed?

For this the logs before the failed shutdown can show usefull info.

jamie

@stephenw10 I had to force reboot at the time to get back online so unfortunately can't try now but if it happens again I'll run a capture and check that. Thanks!

@Gertjan I have provided the system.log covering the duration from when I initiated a reboot to the first two lines of the next boot after I had to pull power as the system appeared to have gotten stuck. Is there a different log file which you're interested to see?