Bug #12920
Updated by Marcos M about 2 years ago
@dpinger@ behaves differently if a when a static route for the respective gateway entry exists in the @config.xml@ file. 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* Gateway entry in config (see notes): Static route exists: * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *missing*; *stopped*; gateway status *pending* No gateway entry in config: 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* Gateway entry in config: Static route exists: * interface down: dpinger process *missing*; gateway status *pending* * interface up: dpinger process *running*; gateway status *online* No gateway entry in config: static route: * 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: Using ifconfig and gateway entry in config: * interface down: dpinger process *running*; gateway status *offline* * interface up: dpinger process *running*; gateway status *online*