Hi, I have a strange issue where FRR does not pull the kernel default route into its routing table, it does accept any other static route that is not 0.0.0.0/0 into its table: FRR routing table: FRR03# show 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 C>* 1.10.1.3/32 is directly connected, lo, 00:58:38 C>* 192.168.17.0/24 is directly connected, ens37, 00:58:38 C>* 192.168.44.0/24 is directly connected, ens33, 00:58:38 Linux routing table: [root@FRR03 ~]# ip route show default via 192.168.44.2 dev ens33 proto static metric 100 192.168.17.0/24 dev ens37 proto kernel scope link src 192.168.17.137 metric 100 192.168.44.0/24 dev ens33 proto kernel scope link src 192.168.44.145 FRR show running output: FRR03# sh run Building configuration... Current configuration: ! frr version 4.1-dev-MyOwnFRRVersion frr defaults traditional hostname FRR03 log syslog ! interface lo ip address 1.10.1.3/32 ! line vty ! end *** Adding static route in Linux *** [root@FRR03 ~]# ip route add 172.16.25.0/24 via 192.168.44.2 [root@FRR03 ~]# vtysh FRR03# show 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 C>* 1.10.1.3/32 is directly connected, lo, 01:01:15 K>* 172.16.25.0/24 [0/0] via 192.168.44.2, ens33, 00:00:05 C>* 192.168.17.0/24 is directly connected, ens37, 01:01:15 C>* 192.168.44.0/24 is directly connected, ens33, 01:01:15 Due to this issue FRR protocols cannot work correctly eg: BGP cannot peer with a neighbor that is not on a directly connected network or added statically. Does anyone have an idea of what this could be? Thanks,