Bug #12920
Updated by Marcos M about 2 years ago
@dpinger@ behaves differently if a when a gateway entry exists in the @config.xml@ file. 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* Gateway entry in config (see notes): * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *missing*; gateway status *pending* No gateway entry in config: * interface down: dpinger process *running*; gateway status *missing* * interface up: dpinger process *running*; gateway status *online* *Tested on 22.05.a.20220308.0600* Gateway entry in config: * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *running*; gateway status *online* No gateway entry in config: * interface down: dpinger process *running*; gateway status *missing* * interface up: dpinger process *running*; gateway status *online* *NOTES*: On switched interfaces (1100), there's a difference between using ifconfig and physically unplugging/plugging a cable: Gateway Using ifconfig and gateway entry in config (using @ifconfig@): config: * interface down: dpinger process *running*; gateway status *offline* * interface up: dpinger process *running*; gateway status *online*