Actions
Regression #11986
closed
Static routes may not be in routing table when expected
Start date:
06/02/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
21.05.1
Release Notes:
Default
Affected Version:
2.5.x
Affected Architecture:
Description
Static routes that I had established via VTI tunnels are not showing up in the routing table.
related to #11296 -
If the remote side is blocking pings to its VTI, the gateway status is down and no route is added:
https://github.com/pfsense/pfsense/blob/3d259e5e9457bc7e9d5b654366f839eaa2d52369/src/etc/inc/system.inc#L995
see NG #6438
2.5.2/21.05 affected
Related issues
Updated by Jim Pingle over 3 years ago
- Target version set to 2.6.0
- Plus Target Version set to 21.09
Updated by Viktor Gurov over 3 years ago
workaround: Disable Gateway Monitoring or Disable Gateway Monitoring Action
Updated by Jim Pingle over 3 years ago
- Status changed from New to Duplicate
- Target version deleted (
2.6.0) - Plus Target Version deleted (
21.09)
The changes from #11296 were all reverted, and that issue was reopened. So this is now redundant/duplicate.
Updated by Jim Pingle over 3 years ago
- Related to Bug #11296: Static route targets may still reachable via default route when the gateway they should route through is down added
Updated by Jim Pingle over 3 years ago
- Subject changed from Static routes are not installing properly on IPsec VTI links to Static routes may not be in routing table when expected
- Status changed from Duplicate to Resolved
- Plus Target Version set to 21.05.1
- Affected Version changed from 2.6.0 to 2.5.x
As noted above, this was worked around for now by reverting the commits from #11296 but I'm changing this one slightly so we can use it for a release notes entry.
Actions