December 2019 - frog - lists.frrouting.org

insert RIP routes into specified table (Linux)
by frr user 10 Dec '19

10 Dec '19

Hello to all. I am trying to use frr 6.0.2 on Debian 10.2; Show, plz, the simplest example of how to insert a route accepted by the RIP protocol into the specified table? For example, the route 192.0.2.0/24 received via RIP needs to be inserted into table #250. Or tell me, do I need to use VRF for this? Thanks.

1 0

Re: [FROG] Failed to start frr.service: Unit frr.service not found
by Alexis Bauvin 09 Dec '19

09 Dec '19

Hi, Yup, that’s why. The systemd service file is not dynamic and does not take into account the actual install path. You may be able to use systemd to run frr as your user, in your home, by modifying the paths in the service file. However, that is not really what this service file is meant for. Depending on how you configured your frr build, just changing the various paths of the service might be enough. frrinit.sh might give you some trouble though, as this script is rather huge and convoluted. Good luck! Alexis PS: don’t forget the ML in your CCs ;) > Le 9 déc. 2019 à 14:05, <ian.2.oakley(a)bt.com> <ian.2.oakley(a)bt.com> a écrit : > > Hi Alexis, > > I copied the frr.service file into /etc/system/system and then ran sudo service frr start. > That gave me the following: > Job for frr.service failed because the control process exited with error code. > See "systemctl status frr.service" and "journalctl -xe" for details. > > Running systemctl status frr.service gave me: > frr.service - FRRouting > Loaded: loaded (/etc/systemd/system/frr.service; disabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Mon 2019-12-09 13:00:29 GMT; 11s ago > Docs: https://frrouting.readthedocs.io/en/latest/setup.html > Process: 16172 ExecStart=/usr/lib/frr/frrinit.sh start (code=exited, status=203/EXEC) > > Dec 09 13:00:29 IanRed systemd[1]: Starting FRRouting... > Dec 09 13:00:29 IanRed systemd[16172]: frr.service: Failed to execute command: No such file or directory > Dec 09 13:00:29 IanRed systemd[16172]: frr.service: Failed at step EXEC spawning /usr/lib/frr/frrinit.sh: No such file or directory > Dec 09 13:00:29 IanRed systemd[1]: frr.service: Control process exited, code=exited status=203 > Dec 09 13:00:29 IanRed systemd[1]: frr.service: Failed with result 'exit-code'. > Dec 09 13:00:29 IanRed systemd[1]: Failed to start FRRouting. > Dec 09 13:00:29 IanRed systemd[1]: frr.service: Triggering OnFailure= dependencies. > Dec 09 13:00:29 IanRed systemd[1]: frr.service: Failed to enqueue OnFailure= job: No such file or directory > > The install directory for my FRR install is in /home/user/ - does that explain anything? > > Regards, > Ian > > -----Original Message----- > From: Alexis Bauvin <abauvin(a)scaleway.com> > Sent: 09 December 2019 12:55 > To: Oakley,I,Ian,TUS2 R <ian.2.oakley(a)bt.com> > Cc: frog(a)lists.frrouting.org > Subject: Re: [FROG] Failed to start frr.service: Unit frr.service not found > > Hi, > > This is a SystemD unit file. It needs to be placed in /etc/systemd/system for systemd to find it and start frr. > > Alexis > >> Le 9 déc. 2019 à 13:07, <ian.2.oakley(a)bt.com> <ian.2.oakley(a)bt.com> a écrit : >> >> Hi, >> >> I installed FRR on my Ubuntu virtual machine from source, hoping to use it with CORE for multicast routing with PIM. >> However, I haven’t been able to manage even that; when I attempt to >> start the FRR service (sudo service frr start) I am given the error >> message in the subject (Failed to start frr.service: Unit frr.service not found.) This is despite me running the command in my /frr/tools directory where frr.service is located. >> Am I missing something here? >> >> Best regards, >> Ian Oakley >> >> _______________________________________________ >> frog mailing list >> frog(a)lists.frrouting.org >> https://lists.frrouting.org/listinfo/frog >

1 0

Failed to start frr.service: Unit frr.service not found
by ian.2.oakley＠bt.com 09 Dec '19

09 Dec '19

Hi, I installed FRR on my Ubuntu virtual machine from source, hoping to use it with CORE for multicast routing with PIM. However, I haven't been able to manage even that; when I attempt to start the FRR service (sudo service frr start) I am given the error message in the subject (Failed to start frr.service: Unit frr.service not found.) This is despite me running the command in my /frr/tools directory where frr.service is located. Am I missing something here? Best regards, Ian Oakley

3 2

Installing learned routes in the kernel routing table
by Daniel Corbe 08 Dec '19

08 Dec '19

I apologize for asking a question which in all probability has a really obvious answer. I have a freshly installed FRR 7.2 from sources on Alpine Linux. The 'zebra' process is running as id=frr and I have a working BGP session. The issue is, it's not installing routes into the kernel routing table. Being that zebra and bgpd are running as the 'frr' user, I made sure zebra had cap_net_admin: # getcap zebra zebra = cap_net_admin+p My Running config: # show run Building configuration... Current configuration: ! frr version 7.2 frr defaults datacenter hostname aagico-alpine-mia no ipv6 forwarding ! router bgp 64225 neighbor vultr peer-group neighbor vultr remote-as 64515 neighbor vultr password xxx neighbor vultr ebgp-multihop 2 neighbor 169.254.169.254 peer-group vultr neighbor 2001:19f0:ffff::1 peer-group vultr ! line vty ! end /etc/frr/daemons: # cat /etc/frr/daemons zebra=yes bgpd=yes ospfd=no ospf6d=no ripd=no ripngd=no isisd=no pimd=no ldpd=no nhrpd=no eigrpd=no babeld=no sharpd=no staticd=yes pbrd=no bfdd=yes fabricd=no # # If this option is set the /etc/init.d/frr script automatically loads # the config via "vtysh -b" when the servers are started. # Check /etc/pam.d/frr if you intend to use "vtysh"! # vtysh_enable=yes zebra_options=" -s 90000000 --daemon -A 127.0.0.1" bgpd_options=" --daemon -A 127.0.0.1" ospfd_options=" --daemon -A 127.0.0.1" ospf6d_options=" --daemon -A ::1" ripd_options=" --daemon -A 127.0.0.1" ripngd_options=" --daemon -A ::1" isisd_options=" --daemon -A 127.0.0.1" pimd_options=" --daemon -A 127.0.0.1" ldpd_options=" --daemon -A 127.0.0.1" nhrpd_options=" --daemon -A 127.0.0.1" eigrpd_options=" --daemon -A 127.0.0.1" babeld_options=" --daemon -A 127.0.0.1" sharpd_options=" --daemon -A 127.0.0.1" staticd_options=" --daemon -A 127.0.0.1" pbrd_options=" --daemon -A 127.0.0.1" bfdd_options=" --daemon -A 127.0.0.1" fabricd_options=" --daemon -A 127.0.0.1" #MAX_FDS=1024 # The list of daemons to watch is automatically generated by the init script. #watchfrr_options="" # for debugging purposes, you can specify a "wrap" command to start instead # of starting the daemon directly, e.g. to use valgrind on ospfd: # ospfd_wrap="/usr/bin/valgrind" # or you can use "all_wrap" for all daemons, e.g. to use perf record: # all_wrap="/usr/bin/perf record --call-graph -" # the normal daemon command is added to this at the end.

2 1

vtysh -f "Unknown command"
by Volodymyr Litovka 03 Dec '19

03 Dec '19

Dear friends, probably, I'm missing something, but I'm not able to use "vtysh -f <filename>", while "vtysh -c" works perfectly: # vtysh -c "show daemons" zebra bgpd watchfrr staticd # cat inp.txt show daemons # vtysh -f inp.txt line 1: % Unknown command[4]: show daemons # echo "show daemons" | vtysh -f /dev/stdin line 1: % Unknown command[4]: show daemons FRR v7.2 under Ubuntu 18.04 I will appreciate any ideas on how to configure FRR using pre-generated configuration. Thank you! -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 4