WAN Does not recover if I power cycle my ISP device.

[BurningBarrier]

I noticed this after a recent power failure and might be a new behaviour as I have had power failures before.

If I power cycle my ISP device opnsense will show the WAN as up but no internet services work..

If I then pull the cable and put it back in causing a hard down / up open sense recovers and starts routing again.

I think the interface on the fibre converter comes up before the service is ready and maybe opnsense is failing initially and not re-trying?

This one is tricky as I have to test it outside of the hours the connection is in use.

[almodovaris]

From the LAN, you may perform a renew/reload of DHCP. Under Interfaces, Overview, WAN.

[BurningBarrier]

From the LAN, you may perform a renew/reload of DHCP. Under Interfaces, Overview, WAN.

That is useful, but my preference would be automatic recovery.. I am not exactly sure what stops working when this happens and if I am remote I am not going to be able to recover it with a command.


The thing is I have had the same ISP for a very long time and the fiber converter / ONT that sits in front is the same I have had for years between two different homes.. I am positive opnsense just recovered automatically in the past but maybe it has just been that long since I has been a really long time since I have had an upstream failure or power failure that out lasted my UPS.

[tent]

up (any solution to this? can we file a bugzilla/bug request or RFE to solve this automatically in future versions of OPNsense? I see really many threads about this, or is there a specific reason this should not be implemented?

[BurningBarrier]

Under System --> Configuration --> WAN_DHCP check the settings

Check if "Disable Gateway Monitoring" is turn on IE disabled, try enabling and configuring it if it is.

[tent]

Hello BB,
 thanks for answering!
 I guess you meant System -> Gateways -> Configuration then edit the WAN_DHCP and make sure that the monitoring is not disabled (so no checkbox on Disable Gateway Monitoring): I checked and it is not disabled/checked so that seems not to be a solution to the problem.
 Actually what happens when he loses the interface is that the values of RTT/RTTd/Loss are empty and even when the interface comes back the values stay blank (I guess because he does not automatically redo a dhcp client request)..
 Bummer..

Kr,
 tent:wq