How to invoke FRR on Mininet containers

[MaxLuo233]

I'm doing a project with FRR running on Mininet containers while I got stuck with how to initialize FRR on those virtual containers. With the FRR offcial documents, I wrote frr.conf file as follows:
frr defaults datacenter

hostname h1-zebra
password this
enable password this
!
interface lo
no shutdown
!
interface h1_1-eth0
ip address 10.1.0.1/24
!
ip route 0.0.0.0/0 10.1.0.254
!

It simply defines the IP address of interfaces of the host h1_1 and adds the default route.

I saved this file path as /etc/frr/frr.conf, and uses h1_1 to run the command '/usr/lib/frr/frrinit.sh start' to invoke the FRR reading this conf file. However, I checked with commands "ip route" and "ifconfig" on h1_1, I found the expected interfaces ip addresses and route were not set.
Could anyone tell me if it is there anything wrong with the syntax of frr.conf file or the invoking process of FRR?

[ton31337]

Could you show show ip route, show int?

[MaxLuo233]

Thanks for your reply. Sure, here are the results:


It seems that the h1_1 Mininet virtual node read the frr conf file successfully after I built up the private directory of h1_1 to save the file. And I did the same thing to h1_2 and R1, two other virtual container nodes with their corresponding frr conf written by myself. The simple topology is h1_1(eth0)---(eth1)R1(eth2)---(eth0)h1_2.
However, I still have the problem that I cannot let h1_1 ping h1_2, which means R1 cannot serve to route traffic. Here is the result of R1 vtysh -c "show running-config":
Current configuration:
!
frr version 9.0.1
frr defaults datacenter
hostname k03
log file /tmp/R1-zebra.log
no ipv6 forwarding
service integrated-vtysh-config
!
password route0
enable password route0
!
interface R1-eth1
ip address 10.1.0.254/24
exit
!
interface R1-eth2
ip address 10.2.0.254/24
exit
!
interface lo
ip address 10.0.0.1/32
exit
!
segment-routing
traffic-eng
exit
exit
!
end

I am a freshman to use FRR. Could you please tell me how to let R1 routing traffic between h1_1 and h1_2 with frr configuration?

[MaxLuo233]

And I'm also confused with the right way to invoke FRR based on FRR official document. What's the difference between the initialization operation using "/usr/lib/frr/frrinit.sh start" and "systemctl frr start", and is "/usr/lib/frr/frrinit.sh start" enough to run all daemons based on file in /etc/frr/daemons or I need to do extra operations to invoke those daemons of each routing protocol?

[MaxLuo233]

I find some other projects running frrouting on mininet virtual nodes. They use commands like "/usr/lib/frr/zebra -f conf/zebra-%s.conf -d -i /tmp/zebra-%s.pid > logs/%s-zebra-stdout 2>&1" and "/usr/lib/frr/bgpd -f conf/bgpd-%s.conf -d -i /tmp/bgp-%s.pid > logs/%s-bgpd-stdout 2>&1" to invoke the corresponding configurations specified in self-defined directory on the mininet nodes. However, these commands not work for me. I wonder does the command "/usr/lib/frr/frrinit.sh start" can replace the "/usr/lib/frr/{zebra bgpd isisd...}"? And also, can "/usr/lib/frr/frrinit.sh" specify the directory to read the conf file?

[ton31337]

I'm totally confused now about what problem we are solving here. You mixed a couple more issues into one, and I'm lost here. Can we start with a single one first?

[MaxLuo233]

I am sorry for my clarification. Now let's focus on only one question: how to start frr?
I saw many ways to start frr based on FRR offcial docs such as "system start frr" "/usr/lib/frr/frrinit.sh start" "/usr/lib/frr/zebra -d -f /etc/frr/zebra.conf"... Could you please tell me which one is true or which one is the best way to invoke frr?