Web down after power failure
-
Does it have a default route in that state? Check Diag > Routes.
-
@stephenw10 When it's up normally it shows:
default normal ip UGS 7 1500 mvneta0.4090
But in the down state the default line is missing. -
Hmm, do you see anything in the logs where it fails to add a default route?
Try setting WAN_DHCP as the default IPv4 gateway in Sys > Routing rather than automatic.
-
@stephenw10 said in Web down after power failure:
WAN_DHCP as the default did not help. Don't know how to read the various logs. -
Well when the DHCP WAN comes up I expect the gateway to be reset as the default route. If that fails there would usually be an error in the System and/or gateways logs showing that failed and why.
Check the dhcp log for the dhclient entries. You should see something like:
Sep 17 22:11:51 dhclient 8480 Starting add_new_address() Sep 17 22:11:51 dhclient 8722 ifconfig ix3 inet 172.21.16.232 netmask 255.255.255.0 broadcast 172.21.16.255 Sep 17 22:11:51 dhclient 9400 New IP Address (ix3): 172.21.16.232 Sep 17 22:11:51 dhclient 10067 New Subnet Mask (ix3): 255.255.255.0 Sep 17 22:11:51 dhclient 10981 New Broadcast Address (ix3): 172.21.16.255 Sep 17 22:11:51 dhclient 11527 New Routers (ix3): 172.21.16.1 Sep 17 22:11:51 dhclient 12199 Adding new routes to interface: ix3 Sep 17 22:11:51 dhclient 13332 /sbin/route add -host 172.21.16.1 -iface ix3 Sep 17 22:11:51 dhclient 14251 /sbin/route add default 172.21.16.1If that route add default command fails it should show an error there and/or in the system log at that time.
-
@swisscheese said in Web down after power failure:
solution given is to get a UPS.
If you experience frequent power failure, investing in one is a must...
-
This post is deleted! -
@swisscheese said in Web down after power failure:
Sep 18 07:32:28 dhclient 80717 Adding new routes to interface: mvneta0.4090
Hmm, not trying to add a default route it looks like. I wonder if the dhcp server is sending it a default route. You might try capturing that dhcp sequence in a pcap and looking at what's actually being sent.
However I think I would try a simpler test. What happens if you manually boot the modem and then boot pfSense after, say, 30s?
If that works it's an easy workaround to add a longer boot delay to pfSense so that the modem has finished booting before pfSense requests a dhcp lease.
Steve
-
This post is deleted! -
@stephenw10 Good idea on the boot delay. I used 60 sec (did not try 30) and it seemed to work. Thank you!
