Static route targets may still reachable via default route when the gateway they should route through is down
When WAN gateway is down, I can still access/ping stuff that is set "static route" thru the primary WAN.
`/etc/rc.gateway_alarm` must delete static routes entries for that gateway
Updated by Viktor Gurov about 1 year ago
Updated by Jim Pingle 9 months ago
- Subject changed from When WAN gateway is down, I can still access/ping stuff that is set "static route" thru the primary WAN to Static route targets may still reachable via default route when the gateway they should route through is down
Updating subject for release notes.
Updated by Jim Pingle 8 months ago
- Status changed from Resolved to New
- Target version changed from 2.5.2 to 2.6.0
- Plus Target Version changed from 21.05 to 21.09
Per Jim T, reverted this from 2.6.0 and 2.5.2. It appears to be causing some unintended side effects.
Can revisit a different approach, or perhaps making it optional and off by default, for the next release.
Updated by Jocelyn Viau about 2 months ago
Thank you for reporting this issue, I have a very similar problem. In my case, I added a static route that goes through a routed IPSec tunnel (VTI). When the tunnel goes down, the traffic for that static route still tries to go through the tunnel and get lost. When the tunnel is down or the IPSec VTI gateway is unreacheable, I would like the static route that uses the VTI Gateway to be removed from the routing table and have the traffic be routed using the remaining routing table.