after power loss wan requires reboot to connect
-
Doing some electrical work and when I powered the pfsense box and cable modem everything looked to be working. The wan ip address is same as when it is working so it appears it should work but it requires unplugging and replugging the wan cable or pfsense reboot. Thought this generally worked after prior utility outages so don't know why it's failing now. Any settings to change to avoid this issue?
-
It sounds like the modem it not ready by the time pfSense requests the WAN address.
After power cycling both check for a default route in Diag > Routes.
Try resaving the WAN interface config. Does it then come back up correctly?
You may just need to add a boot delay to pfSense to allow the modem to come up first.
-
FWIW, This could also happen due to auto negotiation delays. I have to fix my main WAN port at 2500Base-T or DHCP fails around a third of the time at boot.
-
@JimS FYI, Possibly related, I am mentioning this in case someone has the issue. After a modem replacement I had to power cycle pfsense 2.6.2 after a power failure.
I am now on 2.7.2 but have not had a power outage since so don't know if it's fixed. Could be modem timing mentioned above. In my case I could not access anything on pfsense.I posted this March 2025:
The recent S33 modem failure and change to S34 caused pfsense 2.6 not to come back up after a power failure (3 this month so far!)I hope pfsense 2.7.2 can recover from a power failure like 2.6 did with the old modem.2.6 always recovered until the modem change, strange but true. Trying to login to pfsense 2.6 returned the dreaded "502 Bad Gateway Nginx error". Had to power off/on. Waiting to see what happens to 2.7.2. I'm thinking possible ethernet driver issue with a different chip in the S34 than the S33, which may be fixed in 2.7.2
