November 2018 - frog - lists.frrouting.org

v6 Route Replace semantics
by Donald Sharp 09 Apr '20

09 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 on NRL CORE (fyi)
by Phil Wiggins 11 Apr '19

11 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

Increasing the foot print
by Satyavalli Rama 27 Nov '18

27 Nov '18

Hi We are planning to write some applications using the existing FRR Daemons. Is there a way to increase the Foot-Print of the FRR Daemons like pbrd, bgpd etc., Thanks & Regards Satya Valli Tata Consultancy Services Mailto: satyavalli.rama(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1

Warning: connecting to ospfd...failed!
by Sean Barmettler 22 Nov '18

22 Nov '18

I'm at my wits end and have no idea how to proceed. All info I can think of, below. root@debian-r1:/etc/frr# service frr status ● frr.service - FRRouting Loaded: loaded (/etc/systemd/system/frr.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2018-11-20 07:56:19 MST; 1s ago Process: 1824 ExecStop=/usr/lib/frr/frr stop (code=exited, status=0/SUCCESS) Process: 1956 ExecStart=/usr/lib/frr/frr start (code=exited, status=0/SUCCESS) Tasks: 11 (limit: 19660) CGroup: /system.slice/frr.service ├─1975 /usr/lib/frr/zebra -s 90000000 --daemon -A 127.0.0.1 ├─1979 /usr/lib/frr/staticd --daemon -A 127.0.0.1 ├─1987 /usr/lib/frr/bgpd --daemon -A 127.0.0.1 ├─1999 /usr/lib/frr/ospfd --daemon -A 127.0.0.1 -n 100 └─2006 /usr/lib/frr/watchfrr -d -r /usr/lib/frr/frrbBrestartbB%s -s /usr/lib/frr/frrbBstartbB%s -k /usr/lib/frr/frrbBstopbB%s -b bB zebra bgpd ospfd-100 Nov 20 07:56:17 debian-r1 frr[1956]: Loading capability module if not yet done. Nov 20 07:56:18 debian-r1 frr[1956]: 2018/11/20 07:56:18 warnings: ZEBRA: [EC 4043309104] Disabling MPLS support (no kernel support) Nov 20 07:56:18 debian-r1 watchfrr[2006]: watchfrr 6.1-devLabv1-Nov2018-g82ae591 starting: vty@0 Nov 20 07:56:18 debian-r1 watchfrr[2006]: zebra state -> up : connect succeeded Nov 20 07:56:18 debian-r1 watchfrr[2006]: ospfd-100 state -> up : connect succeeded Nov 20 07:56:18 debian-r1 watchfrr[2006]: bgpd state -> up : connect succeeded Nov 20 07:56:18 debian-r1 watchfrr[2006]: all daemons up, doing startup-complete notify Nov 20 07:56:18 debian-r1 frr[1956]: starting staticd since zebra is running ospfd-100 watchfrr. Nov 20 07:56:19 debian-r1 frr[1956]: Exiting from the script Nov 20 07:56:19 debian-r1 systemd[1]: Started FRRouting. root@debian-r1:/etc/frr# vtysh Hello, this is FRRouting (version 6.1-devLabv1-Nov2018-g82ae591). Copyright 1996-2005 Kunihiro Ishiguro, et al. This is a git build of frr-6.1-dev-230-gd482ae591 Associated branch(es): local:master github/frrouting/frr.git/master debian-r1# config t debian-r1(config)# router ospf 100 Warning: connecting to ospfd...failed! debian-r1(config-router)# root@debian-r1:/etc/frr# ps aux | grep ospf frr 1999 0.0 0.5 60132 4452 ? S<s 07:56 0:00 /usr/lib/frr/ospfd --daemon -A 127.0.0.1 -n 100 root 2006 0.0 0.3 58364 2716 ? S<s 07:56 0:00 /usr/lib/frr/watchfrr -d -r /usr/lib/frr/frrbBrestartbB%s -s /usr/lib/frr/frrbBstartbB%s -k /usr/lib/frr/frrbBstopbB%s -b bB zebra bgpd ospfd-100 root 2031 0.0 0.1 12784 1016 pts/1 S+ 08:06 0:00 grep ospf root@debian-r1:/etc/frr# cat frr.conf frr version 6.1-devLabv1-Nov2018 frr defaults traditional hostname debian-r1 no ipv6 forwarding service integrated-vtysh-config username cumulus nopassword ! password test enable password test ! line vty ! root@debian-r1:/etc/frr#

3 3

Slack
by Derrick Lim 15 Nov '18

15 Nov '18

Hello, Could I please get a Slack invite? Regards, Derrick

2 1

Slack invite
by b f31415 08 Nov '18

08 Nov '18

Hi Could I get an invite to the slack channel? Thanks

2 1

Slack
by Hendrik Meyburgh 06 Nov '18

06 Nov '18

Hi. Please can I get an invite to Slack?

2 1

Northbound API and the new libyang dependency
by Renato Westphal 06 Nov '18

06 Nov '18

Hi all, I'd like to announce that the Northbound API PR [1] was merged a couple of days ago. This is only the beginning of a long journey to modernize FRR with a model-driven architecture based on the YANG modeling language. The goal of this initiative is to provide better interfaces to configure and monitor FRR programatically, since the good old CLI is unfit for that purpose. Examples of new management interfaces include the NETCONF and RESTCONF protocols (supported though the ConfD and Sysrepo plugins). There's also a new gRPC-based northbound plugin under development and the CLI will of course continue to be available, now with new features like support for configuration transactions and rollbacks (please check the demos [2]). It's important to say, however, that only daemons converted to the new northbound model will be able to take advantage of the new northbound capabilities. As of now, only the ripd daemon was converted (ripd was chosen for being one of the simplest daemons we have). This means we can configure/monitor ripd using NETCONF for example, but the same doesn't apply to the other daemons yet. The remaining daemons should be converted within the next few months, and everyone from the community is welcome to collaborate :) For more information about the new Northbound API, please check the documentation [3]. As a consequence of this work, FRR will have a new mandatory dependency: libyang [4]. Everyone please check the updated FRR build instructions to see how to obtain and install this library for your platform. Thanks everyone who collaborated to make this possible! Best Regards, Renato. [1] https://github.com/FRRouting/frr/pull/2705 [2] https://github.com/opensourcerouting/frr/wiki/Demos [3] https://github.com/opensourcerouting/frr/wiki/Architecture [4] https://github.com/CESNET/libyang

1 0

Open source routing @ ietf meetup -- Tuesday Lunch
by Lou Berger 05 Nov '18

05 Nov '18

Hi, We're continuing with the informal Open source routing @ ietf meetup. Anyone interested in joining a "bring your own lunch" gathering of folks using/building open source routing code, please drop in to "Borophimarn 3 on the 3rd floor" on *Tuesday* during lunch (noon). There is no agenda or slides. Please feel free to bring a topic that you'd like to discuss or just come and listen. Cheers, Lou https://datatracker.ietf.org/meeting/103/floor-plan#3rd-floor

1 0