February 2019 - frog - lists.frrouting.org

Re: [FROG] FRR eigrp daemon kill
by Donald Sharp 23 Feb '19

23 Feb '19

So EIGRP still needs some work to bring it up to a more acceptable level of performance. Having said that, I did fix a few EIGRP crashes on master a couple of weeks back that were directly related to interfaces going up/down. Please try latest master and see if this fixes the issues you are seeing. donald On Fri, Feb 22, 2019 at 3:17 AM akÿfffffdn ak via frog <frog(a)lists.frrouting.org> wrote: > > > > > ---------- Forwarded message ---------- > From: "akÿfffffdn ak" <akinengineer(a)yahoo.com> > To: "frog(a)lists.frrouting.org" <frog(a)lists.frrouting.org> > Cc: > Bcc: > Date: Fri, 22 Feb 2019 08:16:07 +0000 (UTC) > Subject: FRR eigrp daemon kill > I installed FRR on debian 9 on 4 VM. > I have 4 node FRR. > All of them have eigrp configuration. > When I start ping test to 2 hop away FRR Router. > Ping test successful. > But when I shutdown the interface of 2 hop away FRR Router. > Ping packets drop down. > With no shut comand in destination interface. > Ping successful again. > But sometimes eigrpd daemon kill itself on FRR and I can not pinging again. > I have to restart frr service on VM. > But normally it should not work like that. > Why this happen it in this scenario. > I have to deliver packets to destination continuously. > Please help! > > > > ---------- Forwarded message ---------- > From: "akÿfffffdn ak via frog" <frog(a)lists.frrouting.org> > To: "frog(a)lists.frrouting.org" <frog(a)lists.frrouting.org> > Cc: > Bcc: > Date: Fri, 22 Feb 2019 00:17:16 -0800 (PST) > Subject: [FROG] FRR eigrp daemon kill > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog

1 0

Using FRR in a product.
by Amod Mishra 22 Feb '19

22 Feb '19

Hello, I am evaluating if i would be able to productize FRR on a clusters of VM. Appreciate if can be provided with some pointers on how to complile FRR libs and make use of these libs. Regards Amod.

3 4

FRR eigrp daemon kill
by akÿfffffdn ak 22 Feb '19

22 Feb '19

I installed FRR on debian 9 on 4 VM. I have 4 node FRR. All of them have eigrp configuration.When I start ping test to 2 hop away FRR Router. Ping test successful.But when I shutdown the interface of 2 hop away FRR Router.Ping packets drop down.With no shut comand in destination interface.Ping successful again. But sometimes eigrpd daemon kill itself on FRR and I can not pinging again. I have to restart frr service on VM. But normally it should not work like that. Why this happen it in this scenario.I have to deliver packets to destination continuously.Please help!

1 0

Re: [FROG] FRR Installation on Debian9
by Tim Bray 21 Feb '19

21 Feb '19

On 21/02/2019 12:33, akÿfffffdn ak via frog wrote: > I have a problem for instaling FRR on Debian 9 that installed on VM. I > need to install FRR installation steps on Debian9 What are you doing at the moment? https://github.com/FRRouting/frr/releases/download/frr-6.0.2/frr_6.0.2-0.de… download and dpkg -i should work **** Your other option is to install or upgrde to debian 10 (buster), because this includes an frr package. Either re-install. Or add buster lines in /etc/apt/sources.list Then: # apt install frr Info here, https://packages.debian.org/buster/frr I'm not sure using debian 10 would be great for production, no security support. But would be an easy way to test. -- Tim Bray Technology Director, ProVu Communications Ltd, Huddersfield, UK. http://www.provu.co.uk/ Phone: +44 1484 840048 IP Telephones, Drop shipping, pre-configuration, XML orders ***** If it is important, just phone *****

1 0

FRR Installation on Debian9
by akÿfffffdn ak 21 Feb '19

21 Feb '19

I have a problem for instaling FRR on Debian 9 that installed on VM. I need to install FRR installation steps on Debian9.

1 0

interface shutdown question
by Oguzhan Kayhan 18 Feb '19

18 Feb '19

Hello I created two virtual servers with FRR 6.0.2 installed on it.. Both has 3 interfaces 1st interafce is wan interafce 2nd and third interfaces are for test of eigrp.. 1st server has this config interface eth1 ip address 192.168.100.1/24 ! router eigrp 100 network 192.168.100.0/24 network 192.168.200.0/24 redistribute kernel redistribute connected 2nd server has; interface eth1 ip address 192.168.100.2/24 ! interface eth3 ip address 192.168.200.2/24 shutdown ! router eigrp 100 network 192.168.100.0/24 network 192.168.200.0/24 redistribute kernel redistribute connected ! I can see the 192.168.200.0/24 routing on server1 via eigrp.. which is nice.. The problem is, if i shutdown the interface 2 on server2.. nothing happens.. centos1# conf t centos1(config)# interface eth3 centos1(config-if)# shutdown centos1(config-if)# end and on sh run i have; interface eth3 ip address 192.168.200.2/24 shutdown but i can still ping this intrface from server1. and on server2 ip addr output as follows; 6: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 62:9c:df:28:36:4a brd ff:ff:ff:ff:ff:ff inet 192.168.200.2/24 brd 192.168.200.255 scope global eth3 valid_lft forever preferred_lft forever It is really strange. It seems shutdown command does not work.

1 0

OSPF Interface Poll Interval
by Amol Lad 12 Feb '19

12 Feb '19

Hi, RFC4750 defines "ospfIfPollInterval" as "The larger time interval, in seconds, between the Hello packets sent to an inactive non-broadcast multi-access neighbor." Does FRR supports this? If yes, then please advise how to configure it? Thanks Amol ________________________________ The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).

1 0

FRRouting (6.0.2) now available in Debian buster/testing
by David Lamparter 11 Feb '19

11 Feb '19

Hi all, I'm pleased to announce FRRouting 6.0.2(-2) is now available in Debian testing (buster)! Please note that if you have an earlier version installed (e.g. from CI auto-packages), you will be auto-updated to 6.0.2 unless you mark the package for hold. It may be necessary to do this as the official Debian packages have been considerably cleaned up and reworked compared to 6.0 and older; there are some visible changes particularly in init scripts and startup behaviour. (These changes were merged in 6.0.1. If you already are at that or newer, the update should be smooth sailing.) Ubuntu has also auto-copied the package to their 19.04 / disco branch. This means that unless something unexpected happens, FRRouting will be available in the following upcoming distribution releases: - Debian 10 / buster (expected to become "stable" in 2~3 months) - Ubuntu 19.04 (expected to release end of April) If you have installed pre-release versions of either of these distributions, installing FRRouting is now a matter of doing a plain "apt install frr". FRRouting will very likely remain at the 6.0.x release train for both of these distributions. If you want to receive updates to newer major versions, manual intervention will still be needed (there might be a PPA/repo at some point.) Cheers, -David

3 3

Need help with bootstrap.sh
by muhammed ibrahim 03 Feb '19

03 Feb '19

Hello I am trying to configure FRR on CentOS 7 and I cloned the source code from github. The next step was to run ./bootstrap.sh but I can't seem to run the script. Whenever I run the script an error listed below shows up. ./bootstrap.sh: line 7: autoreconf: command not found What do I need to do? Here is the instruction below http://docs.frrouting.org/en/latest/installation.html#configuration FRR has an excellent configure script which automatically detects most host configurations. There are several additional configure options to customize the build to include or exclude specific features and dependencies. First, update the build system. Change into your FRR source directory and issue: ./bootstap.sh This will install any missing build scripts and update the Autotools configuration. Once this is done you can move on to choosing your configuration options from the list below. PS: I have also posted this on stackover flow but I haven't gotten a response yet. Sincerely, *Muhammed Ibrahim * *muhe31(a)gmail.com* <muhe31(a)gmail.com>

3 2

Daemons start error
by Amol Lad 01 Feb '19

01 Feb '19

Hi, First thanks to Tobias Jungel. With his help in providing Yocto recipe for FRR, I'm now running FRR on Solidrun's Clearfog platform. I'm running release 5.0.1 and get below error at startup. However, daemons do run even after the error. It seems I need to enable some more kernel config options. Please advise. root@clearfog:~# /usr/lib/frr/frr start Loading capability module if not yet done. Starting Frr daemons (prio:10):.1024 zebra2019/01/19 07:09:55 errors: ZEBRA: NS initialization failure 2(No such file or directory) 2019/01/19 07:09:56 warnings: ZEBRA: Disabling MPLS support (no kernel support) .1024 ospfd2019/01/19 07:09:56 errors: OSPF: NS initialization failure 2(No such file or directory) . Starting Frr monitor daemon:1024 watchfrr. Exiting from the script root@clearfog:~# ps 1410 frr 8308 S /usr/lib/frr/zebra --daemon -A 127.0.0.1 1417 frr 8916 S /usr/lib/frr/ospfd --daemon -A 127.0.0.1 1423 root 5628 S /usr/lib/frr/watchfrr -d -r /usr/sbin/servicebBfrrbBrestartbB%s -s /usr/sbin/servicebBfrrbBstartbB%s -k /usr/sbin/servicebBfrrbBstopbB%s -b bB zebra ospfd root@clearfog:~# ls -l /proc/self/ns/ lrwxrwxrwx 1 root root 0 Jan 19 07:11 cgroup -> cgroup:[4026531835] lrwxrwxrwx 1 root root 0 Jan 19 07:11 mnt -> mnt:[4026531840] root@clearfog:~# Thanks Amol ________________________________ The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).

2 1