summaryrefslogtreecommitdiffstats
path: root/src/vnet/classify
diff options
context:
space:
mode:
authorAlexander Chernavin <achernavin@netgate.com>2022-03-02 16:12:49 +0000
committerMatthew Smith <mgsmith@netgate.com>2022-03-25 13:15:21 +0000
commitd373ebef012b1fe94c3df0b92e8c27f90cf782f9 (patch)
treeb288f3948ce2a65cf7794854f00429561556cfb7 /src/vnet/classify
parentd545f04d3c29d53983b442be7cbfc14eed9280c3 (diff)
linux-cp: handle ipv4 routes when link goes down
Type: improvement Currently, when the link goes down on an interface, routes that resolve through that interface and created with Nexthop API are removed by the kernel. However, IPv4 routes remain in the FIB because the kernel doesn't send any notifications about that. And for the plugin working with user-space applications that create routes in the kernel using Nexthop API there should be a mechanism to synchronize the FIB and the kernel in this case. With this change, add two new startup configuration options to the plugin to be able to control what should happen with static and dynamic routes managed by the plugin on link down: - del-static-on-link-down (disabled by default, delete routes created with the linux-cp static FIB source on link down), - del-dynamic-on-link-down (disabled by default, delete routes created with the linux-cp dynamic FIB source on link down). Then, monitor link state changes on interfaces for which a linux-cp pair exists. If the link goes down on one of the interfaces, process routes that resolve through that interface according to the new configurations. Signed-off-by: Alexander Chernavin <achernavin@netgate.com> Change-Id: I0fbaeeca3f3d1fcd22e8eebb08a0a4a3d0dfe5b8
Diffstat (limited to 'src/vnet/classify')
0 files changed, 0 insertions, 0 deletions