Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After stopping the FRRouting process, the routes generated by staticd through loading /etc/frr/staticd.conf still remain in the system. #14062

Closed
Anita-ctrl opened this issue Jul 20, 2023 · 5 comments · Fixed by #15424
Labels
triage Needs further investigation

Comments

@Anita-ctrl
Copy link

When using FRRouting version 9.0, I encountered an issue.

  1. View routing table
  2. View the staticd.conf configuration file.
  3. Start FRR.
  4. The static routes have been successfully loaded.
  5. Stop FRR
  6. The static routes still exist in the routing table.

[root@localhost frr]# ip r
default via 192.168.101.2 dev ens32
169.254.0.0/16 dev ens32 scope link metric 1002
192.168.101.0/24 dev ens32 proto kernel scope link src 192.168.101.20

[root@localhost frr]# cat /etc/frr/staticd.conf
ip route 5.5.5.5/32 192.168.101.5
ip route 6.6.6.6/32 192.168.101.5

[root@localhost frr]# /usr/lib/frr/frrinit.sh start
Starting watchfrr with command: ' /usr/lib/frr/watchfrr -d [ OK ]tional zebra mgmtd staticd'
Started watchfrr [ OK ]

[root@localhost frr]# ip r
default via 192.168.101.2 dev ens32
7.5.5.5 via 192.168.101.5 dev ens32 proto 196 metric 20
8.6.6.6 via 192.168.101.5 dev ens32 proto 196 metric 20
169.254.0.0/16 dev ens32 scope link metric 1002
192.168.101.0/24 dev ens32 proto kernel scope link src 192.168.101.20

[root@localhost frr]# /usr/lib/frr/frrinit.sh stop
Stopped watchfrr [ OK ]
Stopped staticd [ OK ]
Stopped mgmtd [ OK ]
Stopped zebra [ OK ]

[root@localhost frr]# ip r

default via 192.168.101.2 dev ens32
5.5.5.5 via 192.168.101.5 dev ens32 proto 196 metric 20
6.6.6.6 via 192.168.101.5 dev ens32 proto 196 metric 20
169.254.0.0/16 dev ens32 scope link metric 1002
192.168.101.0/24 dev ens32 proto kernel scope link src 192.168.101.20

@Anita-ctrl Anita-ctrl added the triage Needs further investigation label Jul 20, 2023
@donaldsharp
Copy link
Member

How did you run zebra?

@Anita-ctrl
Copy link
Author

How did you run zebra?

Start by using the script frrinit.sh provided by FRRouting itself, and execute the commands frrinit.sh start and frrinit.sh stop

@donaldsharp
Copy link
Member

I mean how are you invoking zebra from the daemons file? There are options that say on shutdown don't remove routes

Copy link

github-actions bot commented Mar 5, 2024

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

@frrbot
Copy link

frrbot bot commented Mar 5, 2024

This issue will be automatically closed in the specified period unless there is further activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants