- frog - lists.frrouting.org

ospf6d doesn't work since upgrading to 8.2.2
by Nicolas Desseauve 21 Mar '22

21 Mar '22

Hello, Since upgrading to 8.2.2 we have a problem with ospf6d (https://github.com/FRRouting/frr/issues/10823) Is there a way to have access to the 8.1 debian package in the repository ? Regards, -- *Nicolas Desseauve* /Responsable de la Sécurité des Systèmes d'Information/ http://www.xsalto.com/ Tél : 04 92 36 60 06 Support : 04 92 36 60 07 Fax : 04 92 36 19 75

2 1

Announcing FRR Release 8.2.2
by Jafar Al-Gharaibeh 14 Mar '22

14 Mar '22

Hi all, We are pleased to announce FRR 8.2.2 release. This release brings a long list of enhancements and fixes with more than 800 commits from 58 developers. Packages: Debian Packages - https://deb.frrouting.org/ <https://deb.frrouting.org/> RPM Packages - https://rpm.frrouting.org/ <https://rpm.frrouting.org/> Snaps - https://snapcraft.io/frr <https://snapcraft.io/frr> Docker - frrouting/frr:v8.2.2 https://hub.docker.com/layers/frrouting/frr/v8.2.2/images/sha256-b236f9d9d6… Some major highlights: - BGP Long-lived graceful restart capability (http://docs.frrouting.org/en/stable-8.2/bgp.html#long-lived-graceful-restart) - BGP Extended Optional Parameters Length for BGP OPEN Message (http://docs.frrouting.org/en/stable-8.2/bgp.html#clicmd-neighbor-PEER-exten…) - BGP Extended BGP Administrative Shutdown Communication - IS-IS Link State Traffic Engineering support (http://docs.frrouting.org/en/stable-8.2/isisd.html#traffic-engineering) - OSPFv3 Support for NSSA Type-7 address ranges (http://docs.frrouting.org/en/stable-8.2/ospf6d.html#ospf6-area) - PBR VLAN actions support (http://docs.frrouting.org/en/stable-8.2/pbr.html#pbr-maps) Please see the release notes for the detailed changelog: * Github release: https://github.com/FRRouting/frr/releases/tag/frr-8.2.2 * FRRouting website: https://frrouting.org/release/8.2.2/ Thanks to all contributors! Cheers, The FRR Development Team!

1 0

OSPF over GRE over IPSec
by Volodymyr Litovka 11 Mar '22

11 Mar '22

Hi colleagues, can anybody help me with an issue in the following configuration. There is GRE over IPSec in transport mode between Linux (Ubuntu 20.04) and two other boxes - Cisco (virtual XE v17.07.01) and Mikrotik (CHR v6). Pings are there, so IPSec policies, addresses, connectivity is ok, but OSPF (I'm using FRR 8.1) do not work. On the linux side, tcpdump shows that it sends hellos in this interface, but both Cisco and CHR see nothing: # tcpdump -i gre1 -v [ ... ] 15:34:49.132222 IP (tos 0xc0, ttl 1, id 15017, offset 0, flags [none], proto OSPF (89), length 68) my_linux > ospf-all.mcast.net: OSPFv2, Hello, length 48 Router-ID x.x.x.x, Backbone Area, Authentication Type: none (0) Options [External] Hello Timer 10s, Dead Timer 40s, Mask 255.255.255.252, Priority 1 Neighbor List: 100.100.8.1 Cisco: Mar 11 15:31:33.522: OSPF-1 HELLO Tu8: Send hello to 224.0.0.5 area 0 from 100.99.0.65 Mar 11 15:31:42.586: OSPF-1 HELLO Tu8: Send hello to 224.0.0.5 area 0 from 100.99.0.65 Mar 11 15:31:51.641: OSPF-1 HELLO Tu8: Send hello to 224.0.0.5 area 0 from 100.99.0.65 Mikrotik (using packet sniffer) also see nothing on input. Definitely, the issue is on Linux side but I can't realize, where exactly. Linux side (mtu is same, multicast switched on): 6: gre1@NONE: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue state UNKNOWN group default qlen 1000 link/gre x.x.x.x peer x.x.x.y inet 100.99.0.66/30 brd 100.99.0.67 scope global gre1 valid_lft forever preferred_lft forever vtysh#sh run [ ... ] interface gre1 ip ospf cost 5 ip ospf mtu-ignore vtysh#sh ip ospf interface gre1 gre1 is up ifindex 6, MTU 1400 bytes, BW 0 Mbit <UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> Internet Address 100.99.0.66/30, Broadcast 100.99.0.67, Area 0.0.0.0 MTU mismatch detection: disabled Router ID x.x.x.x, Network Type POINTOPOINT, Cost: 5 Transmit Delay is 1 sec, State Point-To-Point, Priority 1 No backup designated router on this network Multicast group memberships: OSPFAllRouters Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5 Hello due in 8.701s Neighbor Count is 1, Adjacent neighbor count is 0 vtysh#sh ip ospf neigh Neighbor ID Pri State Dead Time Address Interface RXmtL RqstL DBsmL 100.100.8.1 1 Init/DROther 37.960s 100.99.0.65 gre1:100.99.0.66 0 0 0 host# ip maddress [ ... ] 6: gre1 inet 224.0.0.5 inet 224.0.0.1 What I miss in the Linux configuration? Cisco configuration is for reference: interface Tunnel8 description HZF ip address 100.99.0.65 255.255.255.252 ip mtu 1400 ip ospf network point-to-point ip ospf cost 5 tunnel source GigabitEthernet1 tunnel destination x.x.x.x Tunnel8 is up, line protocol is up Internet Address 100.99.0.65/30, Interface ID 20, Area 0 Attached via Network Statement Process ID 1, Router ID 100.100.8.1, Network Type POINT_TO_POINT, Cost: 5 Topology-MTID Cost Disabled Shutdown Topology Name 0 5 no no Base Transmit Delay is 1 sec, State POINT_TO_POINT Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 oob-resync timeout 40 Hello due in 00:00:04 Supports Link-local Signaling (LLS) Cisco NSF helper support enabled IETF NSF helper support enabled Can not be protected by per-prefix Loop-Free FastReroute Can be used for per-prefix Loop-Free FastReroute repair paths Not Protected by per-prefix TI-LFA Index 1/8/8, flood queue length 0 Next 0x0(0)/0x0(0)/0x0(0) Last flood scan length is 1, maximum is 38 Last flood scan time is 0 msec, maximum is 1 msec Neighbor Count is 0, Adjacent neighbor count is 0 Suppress hello for 0 neighbor(s) Thank you for any recommendations. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 2

Yocto recipe for FRR
by mohammad 27 Feb '22

27 Feb '22

Hi Sorry if this is a duplicate mail. But I couldn't find any reference for FRR recipe in Yocto build system. All I have found are suggestions to modify quagga recipe and an old mail with recipe for FRR 5.0 but unfortunately I couldn't access it Regards

1 0

GRPC support for BGP, OSPF, RIP and OSPFV3 daemons
by jagadeesh N 22 Feb '22

22 Feb '22

Hi All, I wanted to understand the current status and future plans for FRR GRPC Northbound support. I followed the developer guide to get the taste of grpc and looking at the frr test code i was able to do basic static configuration and fetch the configuration using get APIs. But when I tried the same thing on BGP I didn't get any configuration as response(although I configured bgp using VTYSH and also enabled GRPC on bgpd). Due to lack of clarity from the documentation I skimmed through the code, as per my understanding not all the daemons contain the code to support GET and SET APIs as of now. Is my understanding correct? Please point me to any development branch where GRPC support work is going on. Thanks in advance, Jagadeesh N

1 0

Re: [FROG] subscribe
by Abdelmuhaimen Seaudi 17 Feb '22

17 Feb '22

Hello I would like to know if I can setup an EoMPLS PseudoWire using FRR. And, if it is not fully supported, is there a workaround using FRR ? I will be using Debian 11 as my Linux Distro, Kernel version 4.15.x Thanks for any information about the topic Abdelmuhaimen Seaudi, CCIE # 25265 Email: aseaudi(a)gmail.com Skype: aseaudi LinkedIn: www.linkedin.com/in/aseaudi Telephone: +2012 84644 733 >

2 2

Re: [FROG] What can cause State/PfxRcd "(Policy)" in frr 7.5.1?
by Brandon Jackson 31 Jan '22

31 Jan '22

bgp ebgp-requires-policy FRR now REQUIRES that you define a filter for RFC8212. https://docs.frrouting.org/en/latest/bgp.html#clicmd-bgp-ebgp-requires-poli… ---------------------------------- Brandon Jackson bjackson(a)napshome.net On Mon, Jan 31, 2022 at 9:34 AM Peter Olsson via frog < frog(a)lists.frrouting.org> wrote: > > > > ---------- Forwarded message ---------- > From: Peter Olsson <list-frog(a)jyborn.se> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Mon, 31 Jan 2022 15:03:34 +0100 > Subject: What can cause State/PfxRcd "(Policy)" in frr 7.5.1? > Hello! > > I am converting a working quagga configuration into an frr configuration, > since quagga seems abandoned these days. > > I run frr 7.5.1-1.1 in debian 11.2. > > Most peers work fine, but a couple of critical ones get this State which I > haven't seen before: > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down > State/PfxRcd PfxSnt > x.x.x.57 4 yyyy 165 6 0 0 0 00:01:07 > (Policy) 9 > x.x.x.77 4 zzzzz 10 4 0 0 0 00:01:07 > (Policy) 0 > > I'm trying to understand what this means, but haven't found anything so > far. > > The only interesting thing I can see is that the affected peers are using > a private AS number on either itself or the other side. > Could that cause the "(Policy)" State? > > Thanks! > > Peter Olsson > > > > > ---------- Forwarded message ---------- > From: Peter Olsson via frog <frog(a)lists.frrouting.org> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Mon, 31 Jan 2022 15:03:34 +0100 > Subject: [FROG] What can cause State/PfxRcd "(Policy)" in frr 7.5.1? > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog >

1 0

What can cause State/PfxRcd "(Policy)" in frr 7.5.1?
by Peter Olsson 31 Jan '22

31 Jan '22

Hello! I am converting a working quagga configuration into an frr configuration, since quagga seems abandoned these days. I run frr 7.5.1-1.1 in debian 11.2. Most peers work fine, but a couple of critical ones get this State which I haven't seen before: Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt x.x.x.57 4 yyyy 165 6 0 0 0 00:01:07 (Policy) 9 x.x.x.77 4 zzzzz 10 4 0 0 0 00:01:07 (Policy) 0 I'm trying to understand what this means, but haven't found anything so far. The only interesting thing I can see is that the affected peers are using a private AS number on either itself or the other side. Could that cause the "(Policy)" State? Thanks! Peter Olsson

1 0

VPLS not working on Ubuntu 18 VM
by abdelmuhaimen.seaudi＠orange.com 19 Jan '22

19 Jan '22

Hello, I followed the tutorial, and configured 2 Ubuntu 18 VMs with frr OSPF + LDP + L2VPN VPLS. Routing table is OK on the VMs, pseudowires created OK and UP. I cannot see bridge br0 or interface mpw0, if I do “ifconfig” on the linux vm. I tried pinging over the VPLS, but the frames coming from the host are not encapsulated in MPLS. Is there a specific Linux setup necessary to enable the dataplane forwarding to work ? Thanks Abdel-Muhaimen Seaudi Orange Innovation Egypt Email: abdelmuhaimen.seaudi(a)orange.com Mobile: +2012 84644 733 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

3 5

EoMPLS with FRR
by abdelmuhaimen.seaudi＠orange.com 14 Jan '22

14 Jan '22

Hello I would like to know if I can setup an EoMPLS PseudoWire using FRR. And, if it is not fully supported, is there a workaround using FRR ? My linux: Linux sonic 5.10.0-8-2-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux. Thanks for any information about the topic Abdel-Muhaimen Seaudi Orange Innovation Egypt Email: abdelmuhaimen.seaudi(a)orange.com Mobile: +2012 84644 733 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0