summaryrefslogtreecommitdiff
path: root/zebra/zebra_errors.c
diff options
context:
space:
mode:
authoranlan_cs <vic.lan@pica8.com>2022-03-04 21:52:27 +0800
committeranlan_cs <anlan_cs@tom.com>2023-10-07 10:06:39 +0800
commitb580c52698287c24e41b6c5b190c2ddddc336f4c (patch)
tree34f270ed0e4bc62a5ae7724f3dd07d3b91bec608 /zebra/zebra_errors.c
parentd6a9c7ec8776c6d937bc51c3cd4df1c1f59b5c58 (diff)
*: remove ZEBRA_INTERFACE_VRF_UPDATE
Currently when one interface changes its VRF, zebra will send these messages to all daemons in *order*: 1) `ZEBRA_INTERFACE_DELETE` ( notify them delete from old VRF ) 2) `ZEBRA_INTERFACE_VRF_UPDATE` ( notify them move from old to new VRF ) 3) `ZEBRA_INTERFACE_ADD` ( notify them added into new VRF ) When daemons deal with `VRF_UPDATE`, they use `zebra_interface_vrf_update_read()->if_lookup_by_name()` to check the interface exist or not in old VRF. This check will always return *NULL* because `DELETE` ( deleted from old VRF ) is already done, so can't find this interface in old VRF. Send `VRF_UPDATE` is redundant and unuseful. `DELETE` and `ADD` are enough, they will deal with RB tree, so don't send this `VRF_UPDATE` message when vrf changes. Since all daemons have good mechanism to deal with changing vrf, and don't use this `VRF_UPDATE` mechanism. So, it is safe to completely remove all the code with `VRF_UPDATE`. Signed-off-by: anlan_cs <anlan_cs@tom.com>
Diffstat (limited to 'zebra/zebra_errors.c')
0 files changed, 0 insertions, 0 deletions