On power failure, the DHCP service doesn't start?
-
22.05-RELEASE (arm)
On power failure, the DHCP service doesn't seem to work. Clients can't get a lease. I can work around this by doing a clean reboot after power failure or by saving the DHCP settings to cause a service restart.
Anything I can do to solve this? Sometimes even UPSs have problems.
The issue is it covers my home network and if I am away from home I can't fix it remotely and the family need their Netflix and Alexas.
To make it worse the wireless access point relies upon the DHCP server so I can only fix this by being physically connected. Yes I could change to static instead of reserved. And buy another UPS.
How can I tell why it's not working or started or whatever the problem is?
-
@danielbarron What does the DHCP log say at the time?
Can you just start the service yourself or does that also fail?
Does your router use ZFS? If not that’s probably a good idea if you lose power and don’t have a UPS. It’s more resilient for file system damage.
-
@steveits I replicated the issue. Very easy - just pull the power. And I've solved it. Thanks for your reply.
The issue is caused by the router not being ready by the time the firewall boots. Gateway Monitoring Daemon was stopped/not working - even though it was configured and it was leading to the DHCP server giving leases without a gateway. If I only pull the power from the firewall, not the router, everything is fine. If I restart DHCP, everything is fine. If I restart GMD, it starts but DHCP continues to not set the gateway.
Now I've disabled Gateway Monitoring Daemon with "Disable Gateway Monitoring" I no longer get the problem. My setup can now survive a power outage without a phone call from home.
I have a SG-3100 pfSense
Security Gateway Appliance ( #SG3100-None ). It appears to use UFS. I assume there's no way to convert to ZFS? -
@danielbarron No the 3100 can’t use ZFS.