Messages

In my import step I get lot's of these:

Code Select Expand

[source_net] opt2 is not a valid source IP address or alias.
but the old rules seem to reference these aliases just fine.  Do I need to recreate them?

Since I use floating rules I had a few of those and just removed the invalid opt entries in the csv file then imported again.


Question:

After migration and removal of the old rules I still have two rules sections.. Is it just going to stay like that for many versions to come or after a reboot or something will it consolidate to just one Rules section again without the [new] tag?

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.

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.

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.