Spam/duplicate route entries

General questions
, ,
1

Hi,

Running VyOS Stream 2025.11, I’m just checking my IPv4 and IPv6 route entries and had noticed lots of duplicate entries saying the local interface IP address is directly connected, such as in this IPv4 routing table example:

Otherwise, the network itself functions properly without any issues, although I’ll prefer to know why it happens and to reduce the clutter.

xxxx@xxxx0# run show ip route
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

S 0.0.0.0/0 [10/0] via 172.31.255.1, wg0, weight 1, 22:23:04
S>* 0.0.0.0/0 [1/0] via 192.168.1.1, eth0, weight 1, 22:23:04
S>* 10.0.0.0/16 [1/0] via 172.16.0.2, bond0, weight 1, 21:28:25
C>* 172.16.0.0/30 is directly connected, bond0, weight 1, 21:28:25
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 21:28:25
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 21:30:14
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 21:32:56
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 21:33:40
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 22:23:04
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 22:23:05
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h29m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h29m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h36m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h36m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h38m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d06h38m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d07h58m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d07h58m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d08h52m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d08h53m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d08h53m
L * 172.16.0.1/32 is directly connected, bond0, weight 1, 1d08h53m
L>* 172.16.0.1/32 is directly connected, bond0, weight 1, 1d09h25m
L 172.16.0.1/32 is directly connected, bond0 inactive, weight 1, 1d09h30m
L 172.16.0.1/32 is directly connected, bond0 inactive, weight 1, 1d09h39m
C>* 172.16.1.0/24 is directly connected, eth6, weight 1, 21:28:38
L>* 172.16.1.1/32 is directly connected, eth6, weight 1, 21:28:38
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d06h29m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d06h36m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d06h36m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d06h38m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d06h38m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d07h58m
L 172.16.2.1/32 is directly connected, eth1 inactive, weight 1, 1d08h01m
C>* 172.31.255.0/30 is directly connected, wg0, weight 1, 22:23:04
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 22:23:04
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 22:23:04
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h29m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h29m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h36m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h36m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h38m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d06h38m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d07h58m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d07h58m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d09h30m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d09h30m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d16h25m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d16h25m
L * 172.31.255.2/32 is directly connected, wg0, weight 1, 1d18h41m
L>* 172.31.255.2/32 is directly connected, wg0, weight 1, 1d18h42m
C>* 192.168.1.0/24 is directly connected, eth0, weight 1, 22:23:04
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 22:23:04
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 22:23:05
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h29m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h29m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h36m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h36m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h38m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d06h38m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d07h58m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d07h58m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d09h30m
L * 192.168.1.2/32 is directly connected, eth0, weight 1, 1d09h30m
L>* 192.168.1.2/32 is directly connected, eth0, weight 1, 1d16h25m
L 192.168.1.2/32 is directly connected, eth0 inactive, weight 1, 1d18h42m

What would’ve be the cause of such duplicate entries? Thanks.

2

Looks like FRR bug Duplicate routes from local route protocol · Issue #20337 · FRRouting/frr · GitHub

3

Thanks so much for the response, I appreciate it.