summaryrefslogtreecommitdiff
path: root/lib/northbound_cli.c
diff options
context:
space:
mode:
authorRenato Westphal <renato@opensourcerouting.org>2019-01-02 13:05:53 -0200
committerRenato Westphal <renato@opensourcerouting.org>2019-01-02 13:32:31 -0200
commit91d227b7e3cb53ad8fdbcd9d4cff7f0a666918e3 (patch)
treee974a2e924d536b079e95aad2509fd36decf6354 /lib/northbound_cli.c
parentd52fa66f0eab73d73caf5fdb47aeae4132b144db (diff)
zebra, lib: fix the ZEBRA_INTERFACE_VRF_UPDATE zapi message
Unlike the other interface zapi messages, ZEBRA_INTERFACE_VRF_UPDATE identifies interfaces using ifindexes and not interface names. This is a problem because zebra always sends ZEBRA_INTERFACE_DOWN and ZEBRA_INTERFACE_DELETE messages before sending ZEBRA_INTERFACE_VRF_UPDATE, and the ZEBRA_INTERFACE_DELETE callback from all daemons set the interface index to IFINDEX_INTERNAL. Hence, when decoding a ZEBRA_INTERFACE_VRF_UPDATE message, the interface lookup would always fail since the corresponding interface lost its ifindex. Example (ospfd): OSPF: Zebra: Interface[rt1-eth2] state change to down. OSPF: Zebra: interface delete rt1-eth2 vrf default[0] index 8 flags 11143 metric 0 mtu 1500 OSPF: [EC 100663301] INTERFACE_VRF_UPDATE: Cannot find IF 8 in VRF 0 To fix this problem, use interface names instead of ifindexes to indentify interfaces like the other interface zapi messages do. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
Diffstat (limited to 'lib/northbound_cli.c')
0 files changed, 0 insertions, 0 deletions