Bug #12920
Updated by Marcos M about 2 years ago
@dpinger@ behaves differently if a static route for the respective gateway is set. A static route is created e.g. due to gateway monitoring IP, IPsec tunnel, or GIF interface). This behavior difference results in failure to fail back after WAN failover. Using DHCP on WAN, and after bouncing the interface with either ifconfig or physically: *Tested on 22.01* Static route exists: * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *stopped*; gateway status *pending* No static route: * interface down: dpinger process *running*; gateway status *missing* * interface up: dpinger process *running*; gateway status *online* *Tested on 22.05.a.20220308.0600* 22.05* Static route exists: * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *running*; gateway status *online* No static route: * interface down: dpinger process *running*; gateway status *missing* * interface up: dpinger process *running*; gateway status *online*