Project

General

Profile

Actions

Bug #9578

closed

Zebra Doesn't detect VIP on lo0 has been removed

Added by Nick Fisk about 5 years ago. Updated about 5 years ago.

Status:
Not a Bug
Priority:
Very Low
Assignee:
Category:
FRR
Target version:
-
Start date:
06/07/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.4.4-p3
Affected Plus Version:
Affected Architecture:

Description

I am using FRR to advertise IP's located on lo0. Previously when using the Quagga package, when changing a VIP to a different IP, it was removed from the Zebra and BGP tables.

After upgrading to FRR I am seeing that both the old and new IP's are still in Zebra and thus being advertised as connected routes to neighbours.

Example: (old IP=185.68.1.250, New IP=185.68.2.50)

root: netstat -rn
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.99.2 UG1 vmx0
10.254.1.0/24 link#2 U vmx1
10.254.1.250 link#2 UHS lo0
127.0.0.1 link#4 UH lo0
185.68.2.50 link#4 UH lo0
192.168.99.0/24 link#1 U vmx0
192.168.99.50 link#1 UHS lo0

Hello, this is FRRouting (version 6.0.2).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR,
> - selected route, * - FIB route

B>* 0.0.0.0/0 [20/0] via 192.168.99.2, vmx0, 00:03:35
C>* 10.254.1.0/24 is directly connected, vmx1, 02:37:46
C>* 185.68.1.250/32 is directly connected, lo0, 02:37:46
C>* 185.68.2.50/32 is directly connected, lo0, 00:03:38
C>* 192.168.99.0/24 is directly connected, vmx0, 02:37:46

Actions

Also available in: Atom PDF