- frog - lists.frrouting.org

slack channel invite
by David Teach 28 Mar '19

28 Mar '19

Hi There, Could I get an invite to the slack channel? Thanks, - David

2 1

Re: [FROG] FRR Installation on Debian9
by Quentin Young 25 Mar '19

25 Mar '19

From source: http://docs.frrouting.org/projects/dev-guide/en/latest/building-frr-for-deb… <http://docs.frrouting.org/projects/dev-guide/en/latest/building-frr-for-deb…> From packages: https://deb.frrouting.org/ <https://deb.frrouting.org/> If you encounter any bugs please report them on the issue tracker (https://github.com/frrouting/frr/issues <https://github.com/frrouting/frr/issues>). Quentin > On Mar 25, 2019, at 3:00 AM, akÿfffffdn ak via frog <frog(a)lists.frrouting.org> wrote: > > > From: akÿfffffdn ak <akinengineer(a)yahoo.com> > Subject: Re: [FROG] FRR Installation on Debian9 > Date: March 25, 2019 at 2:59:55 AM EDT > To: Tim Bray <tim(a)provu.co.uk>, <frog(a)lists.frrouting.org> > > > I installed frr 7.1 on centos7 and watch installing process which is mentioned by Donald Sharp. It is useful. I could run eigrp between 2 frr node. There were 2 hops between ends. > > Sent from Yahoo Mail for iPhone <https://overview.mail.yahoo.com/?.src=iOS> > > On Perşembe, Şubat 21, 2019, 3:56 ÖS, Tim Bray via frog <frog(a)lists.frrouting.org> wrote: > > 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… <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 <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/ <http://www.provu.co.uk/> Phone: +44 1484 840048 <tel:+44%201484%20840048> > IP Telephones, Drop shipping, pre-configuration, XML orders > ***** If it is important, just phone ***** > > > > > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org <mailto:frog@lists.frrouting.org> > https://lists.frrouting.org/listinfo/frog <https://lists.frrouting.org/listinfo/frog> > > > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog

1 0

Re: [FROG] FRR Installation on Debian9
by akÿfffffdn ak 25 Mar '19

25 Mar '19

I installed frr 7.1 on centos7 and watch installing process which is mentioned by Donald Sharp. It is useful. I could run eigrp between 2 frr node. There were 2 hops between ends. Sent from Yahoo Mail for iPhone On Perşembe, Şubat 21, 2019, 3:56 ÖS, Tim Bray via frog <frog(a)lists.frrouting.org> wrote: 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 ***** _______________________________________________ frog mailing list frog(a)lists.frrouting.org https://lists.frrouting.org/listinfo/frog

1 0

FIB routing compaction / compression
by Stefan Priebe - Profihost AG 18 Mar '19

18 Mar '19

Hello List, is there a fib routing compaction or compression plugin available? While having only a bunch of upstreams / peers 64k fib size of a standard switch would be enough for a full bgp table in rib. If not what‘s needed for frr? Greets, Stefan

4 5

OSPFv2 in a VRF, FRR 6.0.2 on Ubuntu 18.10
by Chuck Cox 14 Mar '19

14 Mar '19

Hi folks, I'm trying to set up a lab environment to test some OSPF stuff. I installed the FRR 6.0.2-0~ubuntu18.04.1 package on top of Ubuntu 18.10. I elected to leave my management interface (ens3) in the default VRF and put the others in a VRF called "WAN", shown as item #10 below: $ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:68:bb:72 brd ff:ff:ff:ff:ff:ff 3: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:ed:f8:ad brd ff:ff:ff:ff:ff:ff 4: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:07:11:c7 brd ff:ff:ff:ff:ff:ff 5: ens11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:6e:51:76 brd ff:ff:ff:ff:ff:ff 6: ens12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:bf:5d:f3 brd ff:ff:ff:ff:ff:ff 7: ens13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:f5:24:55 brd ff:ff:ff:ff:ff:ff 8: ens14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d3:1d:30 brd ff:ff:ff:ff:ff:ff 9: ens15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:e3:cf:dd brd ff:ff:ff:ff:ff:ff 10: WAN: <NOARP,MASTER,UP,LOWER_UP> mtu 65536 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 06:6a:07:90:27:3a brd ff:ff:ff:ff:ff:ff "ip route" correctly shows only the connected subnet route for the management net and a default: $ ip route default via 192.168.42.1 dev ens3 proto static 192.168.42.0/24 dev ens3 proto kernel scope link src 192.168.42.153 And the other connected routes in the VRF: $ ip route show vrf WAN unreachable default metric 4278198272 172.16.1.0/24 dev ens9 proto kernel scope link src 172.16.1.1 172.17.1.0/24 dev ens14 proto kernel scope link src 172.17.1.1 192.0.2.0/24 dev ens10 proto kernel scope link src 192.0.2.1 198.51.100.0/24 dev ens11 proto kernel scope link src 198.51.100.1 203.0.113.0/24 dev ens12 proto kernel scope link src 203.0.113.1 What I see inside vtysh matches: $ ip route show vrf WAN unreachable default metric 4278198272 172.16.1.0/24 dev ens9 proto kernel scope link src 172.16.1.1 172.17.1.0/24 dev ens14 proto kernel scope link src 172.17.1.1 192.0.2.0/24 dev ens10 proto kernel scope link src 192.0.2.1 198.51.100.0/24 dev ens11 proto kernel scope link src 198.51.100.1 203.0.113.0/24 dev ens12 proto kernel scope link src 203.0.113.1 router# sho ip ro vrf WAN Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, > - selected route, * - FIB route VRF WAN: K * 0.0.0.0/0 [255/8192] unreachable (ICMP unreachable), 04:04:10 C>* 172.16.1.0/24 is directly connected, ens9, 04:04:10 C>* 172.17.1.0/24 is directly connected, ens14, 04:04:10 C>* 192.0.2.0/24 is directly connected, ens10, 04:04:10 C>* 198.51.100.0/24 is directly connected, ens11, 04:04:10 C>* 203.0.113.0/24 is directly connected, ens12, 04:04:10 So far so good. Now I enabled ospfd in /etc/frr/daemons and restarted FRR. The ospfd process is running: $ ps -ef|grep frr root 2045 1 0 13:31 ? 00:00:02 /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 ospfd staticd frr 2059 1 0 13:31 ? 00:00:00 /usr/lib/frr/zebra -d -A 127.0.0.1 -s 90000000 frr 2064 1 0 13:31 ? 00:00:01 /usr/lib/frr/ospfd -d -A 127.0.0.1 frr 2069 1 0 13:31 ? 00:00:00 /usr/lib/frr/staticd -d -A 127.0.0.1 Then I put in some seemingly basic OSPF config shown below. Yes, I really only want to speak OSPF on one of the interfaces (ens14) for now. router# sho run Building configuration... Current configuration: ! frr version 6.0.2 frr defaults traditional hostname router log syslog informational no ipv6 forwarding service integrated-vtysh-config ! interface ens3 description MGMT ! interface ens9 vrf WAN description ServerLAN ip address 172.16.1.1/24 ! interface ens10 vrf WAN description MPLS ip address 192.0.2.1/24 ! interface ens11 vrf WAN description PtP ip address 198.51.100.1/24 ! interface ens12 vrf WAN description Satellite ip address 203.0.113.1/24 ! interface ens13 vrf WAN description Inet ! interface ens14 vrf WAN description SD-WAN ip address 172.17.1.1/24 ! interface ens15 vrf WAN description XAXD-LAN ! router ospf 42 vrf WAN ospf router-id 172.17.1.1 redistribute connected passive-interface ens9 passive-interface ens10 passive-interface ens11 passive-interface ens12 passive-interface ens13 passive-interface ens15 area 0.0.0.0 range 10.0.0.0/8 area 0.0.0.0 range 172.16.0.0/20 area 0.0.0.0 range 192.0.2.0/24 area 0.0.0.0 range 192.168.0.0/16 area 0.0.0.0 range 198.51.100.0/24 area 0.0.0.0 range 203.0.113.0/24 default-information originate ! line vty ! end Now here's the problem: OSPF appears to be running but it's not doing anything and none of the show commands give any output, except "sho ip ospf vrf/vrfs": router# sho ip ospf vrf Name Id RouterId Default-IP-Routing-Table 0 0.0.0.0 WAN 10 172.17.1.1 Total number of OSPF VRFs: 2 router# sho ip ospf vrfs Name Id RouterId Default-IP-Routing-Table 0 0.0.0.0 WAN 10 172.17.1.1 Total number of OSPF VRFs: 2 router# sho ip ospf vrf WAN dat router# sho ip ospf vrf WAN int router# sho ip ospf vrf WAN nei router# sho ip ospf vrf WAN route router# sho ip ospf dat router# sho ip ospf int router# sho ip ospf nei router# sho ip ospf route Any suggestions? I've restarted FRR a couple of times and rebooted the box too, same results... Thanks, Chuck

2 2

7.0 release
by David Lamparter 13 Mar '19

13 Mar '19

Hi all, I'm very happy to announce we have released version 7.0 of FRRouting! [https://github.com/FRRouting/frr/releases] There are some major changes in this release, specifically libyang [https://github.com/CESNET/libyang] is now a hard requirement to build and run FRRouting. Here's the full list of major changes from 6.0.x to 7.0: - YANG data modeling & NETCONF support has arrived for the following daemons: - ripd - ripngd - isisd Note that this uses FRR-specific models and may still be subject to some changes. Feedback is strongly appreciated! - Error Codes / Categories are now added to log messages. They are printed as [EC 99999999999] on log messages and identify classes of errors. The library, bgpd, ospfd and zebra have been properly extended to categorize errors while the other daemons have somewhat more rudimentary cateogries. - "configure terminal" in the CLI is no longer an exclusive state on any daemon, i.e. multiple users can edit the configuration at the same time in all daemons. This was previously already the case for zebra and isisd. - BGP enhancements: - EVPN Duplicate Address Detection - EVPN route servers - EVPN extended mobility - Global IPv6 addresses can be used for RFC5549 (v4-over-v6) nexthops - Flowspec protocol support has been significantly extended. (Note that OS integration is still very incomplete.) - Add-Path IDs are now reused on transmission when possible - Aggregates now properly aggregate extended and large community attributes - IS-IS: - BFD support has been added - triggered hellos have been implemented - new daemon: OpenFabric (a datacenter variant of IS-IS - cf. https://datatracker.ietf.org/doc/draft-white-openfabric/) - Zebra's kernel/dataplane interface is undergoing a rewrite and parts have been moved into a separate thread with a more extensible architecture. Work on this project is ongoing. - staticd now supports onlink nexthops for static routes - sharpd now supports nexthop groups for route installs - many bugs were fixed, also including quite a few overdue documentation improvements. This also includes CVE-2017-3224 which is a low-severity low-impact OSPF vulnerability (as evident by the 2017 date.) Important packaging and build related changes: - libyang is now required to build and run FRRouting. Version 0.16.74 or newer (e.g. 0.16-r3 which is 0.16.105) is strongly recommended. Older versions will create additional hazards at both build and runtime because an extension module needs to be installed. Support for libyang versions before 0.16.74 will be removed in the next non-stable FRRouting version. - when using libyang before 0.16.74, make sure to specify the "--with-libyang-pluginsdir=/usr/lib/frr/libyang_plugins" option (change path to fit system) - Debian packaging has been completely overhauled (matches the changes in 6.0.2.) If you are creating derivative Debian packages, updates will be necessary. - RPKI and SNMP are now separate packages that can be installed additionally. There are no longer distinct "RPKI" and "no RPKI" versions of FRRouting on Debian. - Debian packages are now provided in a repository at: https://deb.frrouting.org/ - Snapcraft packaging has been updated to match. - There is a new "--enable-static-bin" option to link libfrr statically into FRR binaries. This is the only supported way of doing any static linking of FRR. ("--disable-shared" is NOT supported.) - all daemons now properly complete their startup before allowing their parent to exit when the -d daemonization option is used. This should remove the need for any "sleep" calls or start retrying in init scripts. - some minor non-reproducibility issues were fixed. FRRouting should now always build reproducibly. - the topotests system that was previously maintained separately is now shipped as part of the FRR source under tests/topotests. As you can see this is quite a changelog and I'd like to thank everyone who contributed to this release. It has been a very productive 6 months! Cheers, -David

1 0

Slack channel invite
by Ivanov Petar 03 Mar '19

03 Mar '19

Hi, I am a student at ETH Zurich doing some work in Network verification and recently found FRRouting, which I think is a great project. Could I please get an invite to the Slack channel? Email: ivanovpe(a)student.ethz.ch Best Regards, Petar Ivanov

1 0

Getting an error while installing FRR
by muhammed ibrahim 01 Mar '19

01 Mar '19

Hello, I need help with this error helpers/python/frrtest.py:200: TestRefMismatch ----------------------------------------------------------- Captured stderr call ----------------------------------------------------------- 2019/03/01 18:22:41 warnings: NONE: libyang: Failed to open libyang user types plugins directory "/usr/lib/frr/frr/libyang_plugins" (Not a directory). 2019/03/01 18:22:41 errors: NONE: [EC 100663342] yang_init: failed to load frr_user_types.so ----------------------------------------------- generated xml file: /etc/frr/tests/tests.xml ----------------------------------------------- ============================================ 191 failed, 212 passed, 2 skipped in 17.67 seconds ============================================ make: *** [tests/tests.xml] Error 1 I am installing FRR on CENTOS 7 and I installed libyang in /etc/ folder following the instructions http://docs.frrouting.org/projects/dev-guide/en/latest/building-frr -for-centos7.html Not sure what I am doing wrong. incerely, *Muhammed Ibrahim * *muhe31(a)gmail.com* <muhe31(a)gmail.com>

1 0

frr 5.0.2, remove-private-AS and ebgp multihop
by Chris Malton 28 Feb '19

28 Feb '19

Hi all, Weird one here: In my config I have an eBGP Multihop peer, and for some reason, despite the config looking like this: router bgp 65001 neighbor w.x.y.z remote-as nnnnn neighbor w.x.y.z local-as 205804 neighbor w.x.y.z description Upstream - Peering Router - b neighbor w.x.y.z ebgp-multihop 2 neighbor w.x.y.z disable-connected-check neighbor w.x.y.z update-source 81.187.56.158 address-family ipv4 unicast neighbor w.x.y.z remove-private-AS all replace-AS nnnnn is the correct peer ASN. The resulting PCAP in wireshark shows: Path Attribute - AS_PATH: 205804 65001 Flags: 0x50, Transitive, Extended-Length, Well-known, Complete Type Code: AS_PATH (2) Length: 10 AS Path segment: 205804 65001 Segment type: AS_SEQUENCE (2) Segment length (number of ASN): 2 AS4: 205804 AS4: 65001 I am convinced I have done something wrong, as I expected FRR to strip 65001 from the sequence. I'm running frr 5.0.2 on a pfSense (so alas, upgrading to 6 isn't an option at the moment). Any hints what I've done wrong - or is this a known bug? Regards, Chris Malton -- Delta V Technologies Limited 03333 402 402 www.deltav-tech.co.uk Office: 17 Elm Close, Southampton, SO16 7DT Company No. 11006104 Registered in England and Wales

2 2

RFC 4364 configuration example
by Mark Tees 26 Feb '19

26 Feb '19

Hi there, Does anyone have a full MPLS layer 3 VPN example I can test out? Also, which version I should try with. I have tried with FRR 6.0 and can see routes under the VRF like below: ord-b457489f5df65f1f# show bgp vrf vrf2 ipv4 </snip> Network Next Hop Metric LocPrf Weight Path *> 5.5.5.1/32 0.0.0.0 0 32768 ? *> 10.13.12.0/30 0.0.0.0 0 32768 ? However I can't see them in the main vpn table or sent to vpn peers. ord-b457489f5df65f1f# show bgp ipv4 vpn No BGP prefixes displayed, 0 exist Have tried with rt/rd/label config under vrf-policy in 'router bgp xxxx' and also under 'router xxxx vrf vrf2'. redistribute connected redistribute static label vpn export 34712 rd vpn export 10.12.12.1:100 nexthop vpn export 10.12.12.1 rt vpn both 45437:100 I followed the Linux VRF instructions for setting up VRF and that appears ok. Any ideas are welcome. Cheers, Mark

2 2