Local routes are duplicated multiple times by FRR. I've tested this on 1.5 (2026.02), and there is a forum thread regarding it happening on 1.5 (2025.11). This does not impact performance or routing decisions, it only seems to cause excess routes to appear:
trae@cr01a-vyos:~$ show ip ro 192.168.100.3/32 longer
Codes: K - kernel route, C - connected, L - local, S - static,
R - RIP, O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric, t - Table-Direct,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
IPv4 unicast VRF default:
L * 192.168.100.3/32 is directly connected, bond0.2522, weight 1, 00:17:44
L * 192.168.100.3/32 is directly connected, bond0.2522, weight 1, 00:17:44
L * 192.168.100.3/32 is directly connected, bond0.2522, weight 1, 00:17:44
L>* 192.168.100.3/32 is directly connected, bond0.2522, weight 1, 00:19:35
L 192.168.100.3/32 is directly connected, bond0.2522 inactive, weight 1, 00:20:13
trae@cr01a-vyos:~$ show ip ro 192.168.100.3
Routing entry for 192.168.100.3/32
Known via "local", distance 0, metric 0
Last update 00:17:56 ago
Flags: None
Status: Installed
* directly connected, bond0.2522, weight 1
Routing entry for 192.168.100.3/32
Known via "local", distance 0, metric 0
Last update 00:17:56 ago
Flags: None
Status: Installed
* directly connected, bond0.2522, weight 1
Routing entry for 192.168.100.3/32
Known via "local", distance 0, metric 0
Last update 00:17:56 ago
Flags: None
Status: Installed
* directly connected, bond0.2522, weight 1
Routing entry for 192.168.100.3/32
Known via "local", distance 0, metric 0, best
Last update 00:19:47 ago
Flags: Selected
Status: Installed
* directly connected, bond0.2522, weight 1
Routing entry for 192.168.100.3/32
Known via "local", distance 0, metric 0
Last update 00:20:25 ago
Flags: None
Status: Installed
directly connected, bond0.2522 inactive, weight 1
trae@cr01a-vyos:~$ show interface bonding bond0.2522
bond0.2522@bond0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000
link/ether ac:1f:6b:12:f6:f6 brd ff:ff:ff:ff:ff:ff
inet 70.133.162.225/32 scope global bond0.2522
valid_lft forever preferred_lft forever
inet 192.168.100.3/29 brd 192.168.100.7 scope global bond0.2522
valid_lft forever preferred_lft forever
inet6 2600:1702:55f3:c800::225/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::ae1f:6bff:fe12:f6f6/64 scope link
valid_lft forever preferred_lft forever
Description: ATT
RX: bytes packets errors dropped overrun mcast
5881797 30639 0 40 0 2581
TX: bytes packets errors dropped carrier collisions
12437104 60679 0 2 0 0Here's where it's reported upstream for FRR:
https://github.com/FRRouting/frr/issues/20337
Here's where it's fixed:
https://github.com/FRRouting/frr/commit/bf1312b8e9f65b7e4046760105dce9bace038fad