WAN gateway not going back up after Internet outage

[kevindd992002]

After several months of using opnsense and a couple of firmware updates to it, I still get this issue:

https://forum.opnsense.org/index.php?topic=41676.msg204737#msg204737

I just experienced it today. Is this not yet fixed?

Here are some logs that triggered today:

https://gist.github.com/kevindd992002/bd55652b9847ca0af03e0d3c24f45957

The WAN gateway never went online until either I restarted the VM or manually renewed the WAN connection in the opnsense GUI.

[pfry]

I haven't looked into the gateway monitoring mechanisms in OPNsense, but have you tried monitoring (pinging) a directly-connected IP (the immediate next-hop) instead of a remote?

[kevindd992002]

I haven't looked into the gateway monitoring mechanisms in OPNsense, but have you tried monitoring (pinging) a directly-connected IP (the immediate next-hop) instead of a remote?

I haven't tried it yet but I can. However, I think it's still best to use a remote IP when monitoring an Internet gateway. In fact, it's what I've been doing with pfsense for several years and it's flawless even with multiWAN. That's why I'm baffled why this isn't working with opnsense with a single WAN.

[Amodin]

After several months of using opnsense and a couple of firmware updates to it, I still get this issue:

https://forum.opnsense.org/index.php?topic=41676.msg204737#msg204737

I just experienced it today. Is this not yet fixed?

Here are some logs that triggered today:

https://gist.github.com/kevindd992002/bd55652b9847ca0af03e0d3c24f45957

The WAN gateway never went online until either I restarted the VM or manually renewed the WAN connection in the opnsense GUI.

I had this problem when I lost internet connectivity before, and it was dpinger not coming back up, so the service had to be started and it worked.  It was later a non-issue for me, as I believe it was corrected after an update, but was back in maybe version 23 into 24?

[kevindd992002]

Based on the dpinger logs I have, dpinger is up and running when this happens. In my case, when the Internet service comes back up it looks like the WAN interface IP address does not renew or something which is why dpinger keeps on failing on the querying the monitor IP. That's just me thinking of possible causes but I'm not sure how to verify this claim in the DHCP logs.