Frr: staticd dont install routes

Created on 28 Nov 2019  路  2Comments  路  Source: FRRouting/frr

* staticd dont install routes *
frr from debian buster (6.0.2)

To Reproduce
Steps to reproduce the behavior:
2 routers (r1, r2), between them - ospfd with redistribute static
on common interfaces - external configuration which brings on 1 router an ip in every interface (something like vrrp). Interfaces like br10, br11, br12, brX etc.
Bringed ip is 172.30.X.253/24

In vtysh configured routes like:

ip route 172.31.15.0/24 172.30.15.253
ip route 172.31.19.0/24 172.30.19.253

etc.

Expected behavior
when external process change ip from r1 to r2(ip a d 172.30.19.253/24 on r1, and ip a a 172.30.19.253/24 on r2) - staticd should install in kernel route to 172.31.19.253/24 on r2). That works fine in quagga. Unfortunetly - in frr it randomly don't work:

root@r2:~# ip r get 172.31.19.0
172.31.19.0 via XXX dev defaultinterface src XXX uid 0 
    cache 
root@r2:~# vtysh -c 'show runn' |grep  172.31.19.0
ip route 172.31.19.0/24 172.30.19.253
root@r2:~# ip r get 172.30.19.253
172.30.19.253 dev br19 src 172.30.19.254 uid 0 
    cache 

in vtysh:

r2# show ip route  172.31.19.0
Routing entry for 172.31.19.0/24
  Known via "ospf", distance 110, metric 20
  Last update 00:34:08 ago
    interconnection_ip, via interconnection_interface

Routing entry for 172.31.19.0/24
  Known via "static", distance 1, metric 0, best
  Last update 01w6d12h ago
  * 172.30.19.253, via br19

but - it don't work randomly - sometimes work fine

If i reinstall route - works ok:

oot@r2:~# ip r get 172.31.19.0
172.31.19.0 via XXX dev defaultinterfac src XXX uid 0 
    cache 
root@r2:~# vtysh -c 'configure terminal' -c 'no ip route 172.31.19.0/24 172.30.19.253'
root@r2:~# vtysh -c 'configure terminal' -c 'ip route 172.31.19.0/24 172.30.19.253'
root@r2:~# ip r get 172.31.19.0
172.31.19.0 via 172.30.19.253 dev br19 src 172.30.19.254 uid 0 
    cache 

Versions

  • OS Kernel: Linux, 4.19
  • FRR Version 6.0.2-2
triage

Most helpful comment

we have fixed a large number of issues in staticd since 6.0 came out. I would highly recommend upgrading to a more modern version

All 2 comments

we have fixed a large number of issues in staticd since 6.0 came out. I would highly recommend upgrading to a more modern version

@polychaeta autoclose in 1week.

Was this page helpful?
0 / 5 - 0 ratings