October 2018 - frog - lists.frrouting.org

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 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

how to make FRR know about configured netns on a centos system?
by Roman Dodin 28 Oct '18

28 Oct '18

Hi all, I have a centos7 system with netns pre-created and populated with an interface: $ sudo ip netns exec ns-data ip -4 -br a lo UNKNOWN 127.0.0.1/8 eth1 UP 192.168.1.101/24 Whereas my base routing instance has a management interface: $ ip -4 -br a lo UNKNOWN 127.0.0.1/8 eth0 UP 10.0.0.101/24 I want to run vtysh and be able to navigate/configure these VRFs, but I cant see the ns-data VRF even if I launch vtysh in that namespace. [centos@pc1 ~]$ sudo vtysh pc1.nuage.lab# show interface Interface eth0 is up, line protocol is up Link ups: 0 last: (never) Link downs: 0 last: (never) vrf: Default-IP-Routing-Table index 2 metric 0 mtu 1500 speed 4294967295 flags: <UP,BROADCAST,RUNNING,MULTICAST> Type: Ethernet HWaddr: fa:16:3e:28:67:f8 inet 10.0.0.101/24 broadcast 10.0.0.255 inet6 fe80::f816:3eff:fe28:67f8/64 Interface Type Other Interface lo is up, line protocol is up Link ups: 0 last: (never) Link downs: 0 last: (never) vrf: Default-IP-Routing-Table index 1 metric 0 mtu 65536 speed 0 flags: <UP,LOOPBACK,RUNNING> Type: Loopback Interface Type Other pc1.nuage.lab# show vrf vrf ns-data inactive If I try to create a VRF with a namespace name mathing my existing netns, I got this error: pc1.nuage.lab(config)# vrf ns-data pc1.nuage.lab(config-vrf)# netns ns-data % [ZEBRA] Unknown command: netns ns-data What am I doing wrong here? -- BR, Roman Dodin

2 3

join slack
by Roman Dodin 27 Oct '18

27 Oct '18

Hello community, would be so kind to invite me to the FRRs slack channel? -- BR, Roman Dodin

3 3

BGP unnumbered
by Madhu 27 Oct '18

27 Oct '18

Hi, Is the bgp unnumbered feature broken from version 5.0? I checked in version 6 , I see the bgp neighborship established with unnumbered and if I advertise the routes its showing ipv4 address as next hop instead of interface ID/IPv6 Link local. Below are the show outputs and the running configurations of one of the system. Can somebody please help me out? Am i missing something? ``` show ip bgp summary IPv4 Unicast Summary: BGP router identifier 3.3.3.3, local AS number 65535 vrf-id 0 BGP table version 0 RIB entries 1, using 160 bytes of memory Peers 2, using 41 KiB of memory Peer groups 2, using 128 bytes of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/P fxRcd br200 4 65001 79 87 0 0 0 00:09:08 0 br10 4 65002 119 106 0 0 0 00:08:09 1 ``` ``` show ip bgp BGP table version is 0, local router ID is 3.3.3.3, vrf id 0 Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, i internal, r RIB-failure, S Stale, R Removed Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path 40.1.1.0/24 4.4.4.4 0 0 65002 i ``` ``` interface lo100 ip address 3.3.3.3/32 ! router bgp 65535 bgp router-id 3.3.3.3 bgp bestpath as-path multipath-relax bgp bestpath compare-routerid neighbor fabric peer-group neighbor fabric remote-as 65001 neighbor fabric capability extended-nexthop neighbor fabric1 peer-group neighbor fabric1 remote-as 65002 neighbor fabric1 capability extended-nexthop neighbor br200 interface peer-group fabric neighbor br10 interface peer-group fabric1 ! address-family ipv6 unicast neighbor fabric activate neighbor fabric1 activate exit-address-family ``` Thanks, Madhu

1 0

Re: [FROG] Multicast Protocol
by Donald Sharp 25 Oct '18

25 Oct '18

Tim - All who ask get an invite. donald On Thu, Oct 25, 2018 at 4:38 AM Tim Bray via frog <frog(a)lists.frrouting.org> wrote: > > > > > ---------- Forwarded message ---------- > From: Tim Bray <tim(a)provu.co.uk> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Thu, 25 Oct 2018 09:37:17 +0100 > Subject: Re: [FROG] Multicast Protocol > On 24/10/2018 14:07, Donald Sharp wrote: > > I would also recommend joining the FRRouting slack for a real-time > > debugging ability. > > I thought this was invite only? > > -- > 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 ***** > > > > > > ---------- Forwarded message ---------- > From: Tim Bray via frog <frog(a)lists.frrouting.org> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Thu, 25 Oct 2018 01:38:07 -0700 (PDT) > Subject: Re: [FROG] Multicast Protocol > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog

1 0

Multicast Protocol
by Tamar Cohen 25 Oct '18

25 Oct '18

Hi all, My name is Tamar and I have the release 5.0.1 of the FRRouting, it is an excellent IP routing protocol suite! I try to use frr in multicast traffic. 1) Is frr support multicast traffic? (I ask because I tried without success) I write this commands: ip multicast ip pim rp IP ADDR inteface INTERFACE ip pim sm\\ in all interfaces Also I add an ospf: router ospf 1 network 0.0.0.0 0.0.0.0 area 0 my setup include tow PC and one additional router (VM of cisco) [cid:image004.jpg@01D46B90.20365000] This setup does not foreword a multicast traffic unfortunately ... 2) I try to debug the traffic in the frr with the "debug" commands but it does not print to the screen anything. In the manual [cid:image006.jpg@01D46B90.20365000] When I wrote the command I got [cid:image007.png@01D46B8F.489CADB0] Why? 3) Is the frr support pim protocol? It is written in the manual but not work in my setup I would be very grateful if you could help me with this. Thank you! Tamar [cid:image002.jpg@01D26F1D.BF96EE00] Tamar Cohen NFV SW Engineer T: +972-73-270-7625 F: +972-08-6436791 | tamar_c(a)rad.com<mailto:tamar_c@rad.com> www.rad.com<http://www.rad.com/> | Follow RAD on LinkedIn<http://www.linkedin.com/company/7369/> | Facebook<http://www.facebook.com/pages/RAD-Data-Communications/72479223117> | Twitter<http://twitter.com/raddatacomms> | YouTube<http://www.youtube.com/user/radwebmaster#g/u>

3 6

Audio Transcription Service Provider
by Laura Davis 25 Oct '18

25 Oct '18

1 0

Babeld Question
by Oguzhan Kayhan 18 Oct '18

18 Oct '18

Hello all, Newbie on FRR and also Babel I made a test setup as 2 frr routers They have 2 interfaces in common subnet.. and a 3rd interface which only belongs to each router seperately.. First i tried the config with ospfd The 3rd interface routing appeared correctly and 1st router was able to ping 3rd interface of the other router (and vice versa) Then i wanted to test babel.. Disabled ospfd Made an example config for babel ! ! interface eth0 babel hello-interval 100 ! interface eth2 babel wired babel hello-interval 100 ! interface eth1 babel hello-interval 100 ! ! router babel network eth0 network eth1 network eth2 redistribute ipv4 connected When starting FRR i am getting the following errors Starting Frr daemons (prio:10):. zebra2018/10/18 17:59:30 warnings: ZEBRA: [EC 4043309104] Disabling MPLS support (no kernel support) . babeldThere is same network configuration eth0 There is same network configuration eth1 There is same network configuration eth2 eth0 : common interface 10.1.1.231-10.1.1.232 eth1: seperate interface 192.168.20.1 / 192.168.21.1 eth2: common interface 192.168.30.1 / 192.168.30.2 Here is the routing : 0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 after a second 0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0 10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.21.0 10.1.1.232 255.255.255.0 UG 0 0 0 eth0 192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 As you see routing seem ok after a second.. but on next second it dissapears. So do ping.. PING 192.168.21.1 (192.168.21.1) 56(84) bytes of data. ping: sendmsg: Network is unreachable 64 bytes from 192.168.21.1: icmp_seq=4 ttl=64 time=1.58 ms 64 bytes from 192.168.21.1: icmp_seq=6 ttl=64 time=0.751 ms ping: sendmsg: Network is unreachable 64 bytes from 192.168.21.1: icmp_seq=8 ttl=64 time=0.868 ms Here is the output of babel interface ospfd-3# sh babel route 10.1.1.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52317 age 2 via eth1 neigh fe80::986c:adff:fef9:5113 nexthop 192.168.21.1 (feasible) 10.1.1.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52318 age 1 via eth2 neigh fe80::9885:8cff:fe66:8028 nexthop 192.168.30.2 (feasible) 192.168.21.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52318 age 1 via eth1 neigh fe80::986c:adff:fef9:5113 nexthop 192.168.21.1 (installed) 192.168.21.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52318 age 1 via eth2 neigh fe80::9885:8cff:fe66:8028 nexthop 192.168.30.2 (feasible) 192.168.30.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52317 age 2 via eth1 neigh fe80::986c:adff:fef9:5113 nexthop 192.168.21.1 (feasible) 192.168.30.0/24 metric 65535 refmetric 0 id f2:e7:01:ff:fe:4e:47:eb seqno 52318 age 1 via eth2 neigh fe80::9885:8cff:fe66:8028 nexthop 192.168.30.2 (feasible) 10.1.1.0/24 metric 0 (exported) 192.168.20.0/24 metric 0 (exported) 192.168.30.0/24 metric 0 (exported)

1 1

6.0 release
by Donald Sharp 18 Oct '18

18 Oct '18

All - We have released 6.0 of FRROUTING: Changes of 6.0 over 5.0: Staticd: New daemon responsible for management of static routes ISISd: Implement dst-src routing as per draft-ietf-isis-ipv6-dst-src-routing BFDd: new daemon for BFD (Bidrectional Forwarding Detection). Responsible for notifying link changes to make routing protocols converge faster. Ubuntu 12.04 is no longer supported (FRR 5.x is last supported version for it) various bug fixes The release images can be found here, with additional documentation: https://github.com/FRRouting/frr/releases I'd like to thank everyone involved in the effort over the last 4 months in getting this released. thanks! donald

2 1