1
24.1 Legacy Series / WAN not pulling IP on power restore
« on: April 12, 2024, 12:00:09 am »
I have opnSense running on a mini PC and there is a ONT that serves as my modem. They are both protected by the same UPS.
Today I've found that if the UPS loses power and both need to boot up at the same time, opnSense finishes booting before the ONT. It detects the Ethernet link before the ONT boots; but of course can't pull an IP so it just lists the WAN interface as down.
Once the ONT finishes booting, it doesn't seem like opnSense retries pulling an IP, so the WAN stays down until I manually log in and tell opnSense to renew the lease on the WAN interface.
If I only reboot the router without rebooting the ONT, everything works as expected and an IP is pulled at boot.
Is there a way to get opnSense to retry to account for the ONT booting up? Or any other suggested solution so that it doesn't just give up on WAN and require manual intervention?
Today I've found that if the UPS loses power and both need to boot up at the same time, opnSense finishes booting before the ONT. It detects the Ethernet link before the ONT boots; but of course can't pull an IP so it just lists the WAN interface as down.
Once the ONT finishes booting, it doesn't seem like opnSense retries pulling an IP, so the WAN stays down until I manually log in and tell opnSense to renew the lease on the WAN interface.
If I only reboot the router without rebooting the ONT, everything works as expected and an IP is pulled at boot.
Is there a way to get opnSense to retry to account for the ONT booting up? Or any other suggested solution so that it doesn't just give up on WAN and require manual intervention?