April 2019 - frog - lists.frrouting.org

Yocto Recipe for FRR
by Amol Lad 10 Aug '21

10 Aug '21

Hi, Please advise if there is any Yocto recipe for FRRouting? If not, how to go about creating one for FRR? Yocto Recipe for FRR will hugely simplify integrating FRR in Yocto based embedded linux distributions. So please advise if there are any plans to develop this recipe? 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).

4 10

v6 Route Replace semantics
by Donald Sharp 08 Apr '20

08 Apr '20

All - We recently introduced, into master, a new cli switch for zebra on linux `--v6-rr-semantics`. This was allow zebra to take advantage of the linux kernel getting v6 route replace semantics that is coming soon in the 4.18 linux kernel. So if you are on the bleeding edge of linux kernels and FRR you can start to take advantage of this new feature. What are Route Replace semantics you ask? Suppose we have a v6 route with 2 nexthops: S>* 4:6:7::/64 [1/0] via 1:2:3::4, enp0s3, 00:00:02 via 1:2:8::8, enp0s8, 00:00:02 Now suppose we remove a nexthop: robot# conf t robot(config)# no ipv6 route 5:7:9::/78 1:2:8::9 robot(config)# end robot# show ipv6 route [snip] S>* 5:7:9::/78 [1/0] via 1:2:3::4, enp0s3, 00:01:04 Let's look at the netlink notifications for this event: [ROUTE]5:7:9::/78 proto static metric 20 <----------- From creation of the 2x ecmp for 5:7:9::/78 nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]Deleted 5:7:9::/78 proto static metric 20 <---- We delete the route nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]5:7:9::/78 via 1:2:3::4 dev enp0s3 proto static metric 20 pref medium <----- We add it back in. In order to get the routes right in the kernel we had to delete the route first and then add it back in. Exposing a small window of packets being dropped while the route is fixed in the fib. Route Replace semantics tells the linux kernel to just replace the nexthops for the route. New packets coming in would immediately start using the new ecmp nexthop group path: [ROUTE]5:7:9::/78 proto static metric 20 nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]5:7:9::/78 via 1:2:3::4 dev enp0s3 proto static metric 20 pref medium thanks! donald

2 1

FRR 7.0 BGP does not connect to passive neighbor
by Chris G 29 Apr '19

29 Apr '19

Hello, I have an issue where my BGP neighbor is configured in passive mode, however my BGP (FRR 7.0) instance does not attempt to connect to this neighbor. Is this expected behavior? Is there any way I can force my BGP instance to initiate a connection to the passive BGP neighbor ? Thanks, Chris

4 7

discard interface warnings on FreeBSD
by Mike Tancsa 26 Apr '19

26 Apr '19

I have been using the discard interface - DISC(4) - on FreeBSD for some time to tie down supernets. On frr7, I am getting a warning message at startup I am not sure what to make of The nic is configured as # ifconfig disc0 disc0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 65532 inet 10.128.128.144 netmask 0xfffffff8 inet 10.129.129.1 netmask 0xfffffff0 inet6 2001:db8::1 prefixlen 64 inet6 fe80::1%disc0 prefixlen 64 scopeid 0x7 groups: disc nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> And at startup, I get /usr/local/etc/rc.d/frr start Checking zebra.conf 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.128.128.144/29 != calculated 10.128.128.151, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.129.129.1/28 != calculated 10.129.129.15, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309105] Disabling MPLS support (no kernel support) OK Starting zebra. 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.128.128.144/29 != calculated 10.128.128.151, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.129.129.1/28 != calculated 10.129.129.15, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309105] Disabling MPLS support (no kernel support) If I use the same IP info on another non discard interface it works / doesnt complain. Also, when starting staticd, I get these warnings as well. Checking staticd.conf 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra OK Starting staticd. Looking at the installed routes, it looks ok, except for one which I must be missing something obvious, but its ok on quagga and frr6 I have interface igb1.6: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=600703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,RXCSUM_IPV6,TXCSUM_IPV6> ether 90:e2:ba:01:37:81 inet6 fe80::92e2:baff:fe01:3781%igb1.6 prefixlen 64 scopeid 0xe inet 64.7.149.177 netmask 0xfffffffc broadcast 64.7.149.179 and a static route of ip route 10.87.1.0/30 64.7.149.178 It ends up installing this static route on the discard interface for some reason on frr7. On frr6, it works. next hop is 64.7.149.178. I do get the same warning messages however at startup. On frr5, its the same as frr7. # vtysh -c "show ip route 10.87.1.0/30" Routing entry for 10.87.1.0/30 Known via "static", distance 1, metric 0, best Last update 00:00:14 ago 64.7.149.178 (recursive) * 10.129.129.1, via disc0 kernel confirms # netstat -nr | grep ^10.87.1. 10.87.1.0/30 10.129.129.1 UG1 disc0 # Any ideas what up ? As this is just a test box, there is no MAC addr for the next hop, but would it not mark the route as inactive rather than change the next hop to the discard interface ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike(a)sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada

1 0

Announcing availability of PIM-EVPN BUM Handling
by Donald Sharp 25 Apr '19

25 Apr '19

All - I'd like to thank Anuradha for her work on integrating PIM-EVPN BUM handling in FRRouting. For those of you interested in using this feature you'll need a linux kernel > 5.0 to pick up some new features there. In addition you can read about how to configure here: http://docs.frrouting.org/en/latest/pim.html#pim-evpn-configuration thanks! donald

1 0

FRR on NRL CORE (fyi)
by Phil Wiggins 10 Apr '19

10 Apr '19

If anyone is interested in running FRR in the NRL CORE emulation environment, I have some build scripts for FRR on CORE that I posted at the first link below. Normally CORE runs Quagga, so this script was a hack to shoehorn FRR as a Quagga replacement. These scripts are not part of CORE yet, so are unsupported. People on this list may want to use CORE for FRR experimentation and testing, so you can customize these scripts to suit your own needs. It's best to run this stuff in a VM with no internet connection (after installation) since CORE runs lots of processes as root - a well-known security issue. https://github.com/coreemu/core/issues/170 ( install_frr_for_core.sh) FRR on NRL CORE build script - assumes Ubuntu 16.04.4 clean installation in a VM or physical host: https://gist.github.com/apwiggins/44f3592a61965783372aea5881ed9f7a (core_misc_frr.py ) used by the install script above to install at ./core/misc/frr.py https://gist.github.com/apwiggins/d610c2794c8c0a12a45bfc093fd2e949 (core_services_frr.py) used by the install script above to install at ./core/services/frr.py https://gist.github.com/apwiggins/747a9a14feff2ce3a3b8760406b825a7 https://www.nrl.navy.mil/itd/ncs/products/core The Common Open Research Emulator (CORE) is a tool for emulating networks on one or more machines. You can connect these emulated networks to live networks. CORE consists of a GUI for drawing topologies of lightweight virtual machines, and Python modules for scripting network emulation. Cheers, Phil

2 3

Reg SR Static tunnel config with SID list
by kotesh 08 Apr '19

08 Apr '19

Hi, Does FRR allow to configure SID list for a given prefix (advertised by OSPF SR extensions)? If yes, can somebody point us to some sample config ? Thanks, Kotesh babu.Chundu

1 0

FRR 6.0.2 lost routes after Ubuntu 18.04.2 LTS update/upgrade
by Sim 05 Apr '19

05 Apr '19

After apt-get upgrade / upgrade FRR lost all routes. Reboot or restart the server is the solution to resolve the issue. I'm new with FRR, but this is not happened with Quagga in the last 10/15 years. Is it a "FRR issue" or about Ubuntu 18.04 LTS version? # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnss-systemd libpam-systemd libpci3 libsystemd0 libudev1 pciutils systemd systemd-sysv udev 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 4,765 kB of archives. After this operation, 56.3 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.13 [105 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.13 [205 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.13 [108 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.13 [2,899 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.13 [1,101 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.13 [54.1 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.13 [12.0 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 pciutils amd64 1:3.5.2-1ubuntu1.1 [257 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpci3 amd64 1:3.5.2-1ubuntu1.1 [24.1 kB] Fetched 4,765 kB in 8s (575 kB/s) (Reading database ... 67479 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.13_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.13_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Setting up libsystemd0:amd64 (237-3ubuntu10.13) ... (Reading database ... 67479 files and directories currently installed.) Preparing to unpack .../libpam-systemd_237-3ubuntu10.13_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Preparing to unpack .../systemd_237-3ubuntu10.13_amd64.deb ... Unpacking systemd (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Preparing to unpack .../udev_237-3ubuntu10.13_amd64.deb ... Unpacking udev (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Preparing to unpack .../libudev1_237-3ubuntu10.13_amd64.deb ... Unpacking libudev1:amd64 (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Setting up libudev1:amd64 (237-3ubuntu10.13) ... Setting up systemd (237-3ubuntu10.13) ... (Reading database ... 67479 files and directories currently installed.) Preparing to unpack .../systemd-sysv_237-3ubuntu10.13_amd64.deb ... Unpacking systemd-sysv (237-3ubuntu10.13) over (237-3ubuntu10.12) ... Preparing to unpack .../pciutils_1%3a3.5.2-1ubuntu1.1_amd64.deb ... Unpacking pciutils (1:3.5.2-1ubuntu1.1) over (1:3.5.2-1ubuntu1) ... Preparing to unpack .../libpci3_1%3a3.5.2-1ubuntu1.1_amd64.deb ... Unpacking libpci3:amd64 (1:3.5.2-1ubuntu1.1) over (1:3.5.2-1ubuntu1) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.13) ... Processing triggers for ureadahead (0.100.0-20) ... Setting up systemd-sysv (237-3ubuntu10.13) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up udev (237-3ubuntu10.13) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for dbus (1.12.2-1ubuntu1) ... Setting up libpci3:amd64 (1:3.5.2-1ubuntu1.1) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.13) ... Setting up pciutils (1:3.5.2-1ubuntu1.1) ... Processing triggers for initramfs-tools (0.130ubuntu3.6) ... update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic Processing triggers for libc-bin (2.27-3ubuntu1) ... # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. # ps fax PID TTY STAT TIME COMMAND 955 ? S<s 0:45 /usr/lib/frr/watchfrr -d -r /usr/lib/frr/watchfrr.sh restart %s -s /usr/lib/frr/watchfrr.sh start %s -k /usr/lib/frr/watchfrr.sh stop %s zebra bgpd staticd 1006 ? S<sl 3:59 /usr/lib/frr/zebra -d -A 127.0.0.1 -s 90000000 1009 ? S<sl 7:22 /usr/lib/frr/bgpd -d -A 127.0.0.1 1016 ? S<s 0:05 /usr/lib/frr/staticd -d -A 127.0.0.1 # vtysh Hello, this is FRRouting (version 6.0.2). Copyright 1996-2005 Kunihiro Ishiguro, et al. xxx# sh ip bgp summary IPv4 Unicast Summary: BGP router identifier x.x.32.34, local AS number xxxxxx vrf-id 0 BGP table version 6693928 RIB entries 6, using 960 bytes of memory Peers 2, using 41 KiB of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd x.x.118.244 4 xxxx 915579 27779 0 0 0 00:03:45 Active x.x.32.33 4 xxxxxx 843680 352816 0 0 0 00:05:16 Active # ip add 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet x.x.32.34/32 scope global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:ba:53:46 brd ff:ff:ff:ff:ff:ff inet x.x.32.29/28 brd x.x.32.31 scope global ens160 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:feba:5346/64 scope link valid_lft forever preferred_lft forever 3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:ba:af:9d brd ff:ff:ff:ff:ff:ff inet x.x.32.3/28 brd x.x.32.15 scope global ens192 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:feba:af9d/64 scope link valid_lft forever preferred_lft forever # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface x.x.32.0 0.0.0.0 255.255.255.240 U 0 0 0 ens192 x.x.32.16 0.0.0.0 255.255.255.240 U 0 0 0 ens160 Regards Sim

4 10

FRR
by Azadeh Shahabi 04 Apr '19

04 Apr '19

Hello, I found different approaches regarding the usage of GPL'ed libraries; so I would like to specifically ask regarding the usage of FRR binary. Can I link FRR binary as is with no modification to it nor its source codes to proprietary codes/binary and then sale the commercial product to customer while FRR is embedded in that product as well, or do I need to open source the product or binary that FRR is used on that. Appreciate if you may assist me with this case. Best regards, Azadeh

2 1