system: allow polling when gateway monitor reports a gateway as down

[fichtner]

To fix cases where DHCP on WAN is not recovering due to modem being stubborn.

via: https://forum.opnsense.org/index.php?topic=9050.0
via: https://forum.opnsense.org/index.php?topic=9030.0

[saffrey]

+1 to this issue. Would like to know if there is a workaround that I can implement before the feature is included.

Cheers!

[fichtner]

As far as #5956 is concerned 2de4658 teaches us that dhclient desperately needs a wrapper script to remove the cached IP and/or bring down the interface in order for it to be reconfigured later. Right now when dhclient exits and the link does not go down/up we don't have the chance to run any sort of post-dhcp hook to bring it back up.

[francois-pasquier]

I am experiencing flapping after getting disconnected and reconnected to Wan. ( I have to reboot opnsense to fix it)

Can you confirm it's one of the symptoms that should is included in this issue?

From what I gathered a lot of people are experiencing this and it was a "long time issue"

Thank's for the hard work!

[fichtner]

Flapping is the exact opposite of this problem. Here we never have flapping but dhclient exist at some point and we have no way of knowing. Link down/up actually correctly cycles dhclient.

[fichtner]

This might just work starting with 23.7.2 when default gateway switching is enabled, for details see #6728

[swhite2]

Situation doesn't appear to happen as often anymore, so closing the issue.

[EarlSven]

I appear to still be suffering from this issue Opnsense 24.7.5.

My Virgin Media Hub 3.0 needs my WAN interface to use DHCP, in order to assign it my public IP. I only get an IP if after Opnsense boots I 'reload' the WAN interface on the Interfaces->Overview page. I've tried various things like tinkering with the advanced DHCP client settings, blacklisting DHCP addresses from the Hub's 192.168.x.x address, adding a monitor gateway. None of the above seems to make a difference, whenever I reboot my Opnsense box I have to manually log in and 'reload' the interface. It then immediately works, but it seems no matter how long I leave it it always needs that 'reload' to get a WAN IP.

I've probably been suffering from this issue for a couple of years, but it's quite infrequent that my Opnsense is rebooted, so it's been low priority to investigate and fix.

[jonatino]

I'm on pfsense 24.7.6 and I also have issues with this. My modem will often (at least once a day) go down and when it restarts it will get assigned a new IP from my ISP. This causes all internet access to completely stop until opnsense is restarted regardless if my modem comes back online.

Previously (before yesterday), I used an edgerouter-x which also suffered from the same issue. As a workaround, I wrote the following script for my edgerouter than will force a release/renew of dhcp on the WAN interface whenever the internet was offline.

# Release DHCP
run=/opt/vyatta/bin/vyatta-op-cmd-wrapper

echo "Internet is offline, releasing dhcp"
$run release dhcp interface eth4

# Renew DHCP
echo "Renewing dhcp"
$run renew dhcp interface eth4

Is there any way I can automate something similar in opnsense? Otherwise I'd likely have to go back to my edgerouter due to the frequency of downages I have.