August 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

Question about PIM
by kevin-chiang 03 Sep '19

03 Sep '19

Dear developers, We have some questions about pimd: According to my test, seems FRR can't handle IGMPv3 report with exclude mode (system still forwards the specified multicast data packet which is received from exclude source IP) ==> Does FRR support IGMPv3 report with exclude mode?? ==> Or any bug fix plan in the future? If we enable IGMP only, then multicast data packet can't forward succeeded, seems we must enable PIM also. ==> Dose FRR have any plan to support only IGMP enable case?? Please guide us Thanks a lot BRs Kevin Loop Telecommunication International, Inc. www.looptelecom.com 8GESW is designed to transport Ethernet services over SDH/SONET networks (EoS). It provides eight GbE ports and a range of standard L2 switch functions, including VLAN, Q-in-Q, MAC learning, MSTP/RSTP, CoS and QoS, and etc. Ethernet bridging services include EPL, EVPL, and EPLAN. Max. bandwidth for SDH/SONET transportation is either STM-4/OC-12 or STM-16/OC-48. Dual 8GESW cards can be mounted simultaneously to achieve card-level protection. Protection switch happens within 50 ms without any traffic interruption. Traffic at the SDH/SONET side is further protected by SNCP/UPSR ring and MSP (1+1). For further arrangement and more information, please do not hesitate to contact Loop Telecom. "Migrating Legacy Networks to the Future"

2 1

[FRR] [syslog] How to dump log of bgpd
by Simon Jones 23 Aug '19

23 Aug '19

Hi all, I'm using FRR, I found zebra, staticd could dump log, but bgpd could not I start bgpd like this: > root@NX-ZWYC-M1F202-A16-HW6865-A-INT-212:/# /usr/lib/frr/bgpd -A > 127.0.0.1 -M snmp --log stdout --log-level debug > There is only this log: > 2019/08/22 07:21:43 BGP: bgpd 7.0.1-sonic starting: vty@2605, bgp@ > <all>:179 Then I up/down peer, there is no log ---- Simon Jones

2 2

Solaris and FRR
by Donald Sharp 21 Aug '19

21 Aug '19

All - During yesterday's weekly technical meeting we discussed solaris and FRR. The FRR CI system uses Omnios, and over the last year or so with the increased usage of external libraries it has started to become extremely hard to keep Omnios in a working state. With the additional major rework of the zebra data plane it is becoming apparent that not having a built up test system for that platform we are running the risk of letting Solaris compatibility become woefully out of date. One of the options discussed was dropping Solaris but before we do so we wanted to gauge community interest/usage of FRR on solaris platforms and would like to hear opinions from people on this matter. thanks! donald

1 0

DEB repo and Apt-Cacher NG
by Chriztoffer Hansen 19 Aug '19

19 Aug '19

Hello, Anyone have had success before with configuring http://deb.frrouting.org/frr/ together with Apt-Cacher NG with ForceManaged enabled? Currently trying. But ends up with the following results each time I execute 'apt-get update' on any machine connected to the proxy. ``` Err:3 http://deb.frrouting.org/frr buster InRelease 403 Forbidden file type or location [IP: 192.0.2.0 3142] ``` ``` #/etc/apt-cacher-ng/acng.conf (snip) Remap-frrouting: file:frrouting_mirrors /frr ; file:backends_frrouting ForceManaged: 1 (snip) ``` ``` #/etc/apt-cacher-ng/backends_frrouting http://deb.frrouting.org/frr/ ``` -- Chriztoffer

1 0

Why my snmptrap handle script not work?
by Simon Jones 16 Aug '19

16 Aug '19

Hi all, I'm following this to handle snmp trap: http://docs.frrouting.org/en/latest/snmp.html this is /etc/snmp/snmptrapd.conf: > traphandle .3.6.1.2.1.15 /etc/snmp/snmptrap_handle.sh this is snmptrap_handle.sh: > echo "test" > temp.txt and snmptrapd got SNMP trap like this: > root@NX-ZWYC-M1F202-A16-HW6865-A-INT-212:/# snmptrapd -f -Lo > NET-SNMP version 5.7.3 > 2019-08-14 11:53:50 172.18.8.212(via UDP: > [127.0.0.1]:34916->[127.0.0.1]:162) TRAP, SNMP v1, community public > iso.3.6.1.2.1.15 Enterprise Specific Trap (2) Uptime: 2:11:33.09 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 = Hex-STRING: 06 02 > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 = INTEGER: 6 > 2019-08-14 11:54:04 172.18.8.212(via UDP: > [127.0.0.1]:34916->[127.0.0.1]:162) TRAP, SNMP v1, community public > iso.3.6.1.2.1.15 Enterprise Specific Trap (1) Uptime: 2:11:47.10 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 = Hex-STRING: 06 02 > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 = INTEGER: 6 > 2019-08-14 11:57:39 172.18.8.212(via UDP: > [127.0.0.1]:34916->[127.0.0.1]:162) TRAP, SNMP v1, community public > iso.3.6.1.2.1.15 Enterprise Specific Trap (2) Uptime: 2:15:22.90 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 = Hex-STRING: 06 02 > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 = INTEGER: 6 But snmptrap_handle.sh does not work, as there is no temp.txt. So why ? BTW, this is also not work /etc/snmp/snmptrapd.conf: > traphandle .1.3.6.1.4.1.3317.1.2.2 /etc/snmp/snmptrap_handle.sh > ---- Simon Jones

2 1

[BUG] [FRR-SNMP] SNMP trap message with wrong peer status
by Simon Jones 16 Aug '19

16 Aug '19

Hi all, I'm working on sonic-frr, which is just frr. I enable frr-snmp, and follow this (http://docs.frrouting.org/en/latest/snmp.html) to get trap, this is my configuration: > root@NX-ZWYC-M1F202-A16-HW6865-A-INT-212:/# cat /etc/snmp/snmptrapd.conf > # > # EXAMPLE-trap.conf: > # An example configuration file for configuring the Net-SNMP snmptrapd > agent. > # > > ############################################################################### > # > # This file is intended to only be an example. > # When the snmptrapd agent starts up, this is where it will look for it. > # > # All lines beginning with a '#' are comments and are intended for you > # to read. All other lines are configuration commands for the agent. > disableAuthorization yes > # > # PLEASE: read the snmptrapd.conf(5) manual page as well! > # > #authCommunity log,execute,net private > #authCommunity log,execute,net public > #authCommunity log,execute,net snmp@sankuai > # > traphandle .1.3.6.1.2.1.15.0.1 ./bgp-peer-status > traphandle .1.3.6.1.2.1.15.0.2 ./bgp-peer-status > root@NX-ZWYC-M1F202-A16-HW6865-A-INT-212:/# cat ./bgp-peer-status > #!/bin/bash > echo `cat -` Then I up/down bgp peer use these command: > NX-ZWYC-M1F202-A16-HW6865-A-INT-212(config-router)# router bgp 65003 > NX-ZWYC-M1F202-A16-HW6865-A-INT-212(config-router)# neighbor 192.168.10.9 > shutdown > NX-ZWYC-M1F202-A16-HW6865-A-INT-212(config-router)# no neighbor > 192.168.10.9 shutdown This is trap message I got, I got 2 messages, you could see, the 2 message is the same, especially in bgp peer status, I guess this is a BUG ? > root@NX-ZWYC-M1F202-A16-HW6865-A-INT-212:/etc/snmp# /usr/sbin/snmptrapd > -f -Lo4d > NET-SNMP version 5.7.3 > 2019-08-15 09:42:15 172.18.8.212(via UDP: > [127.0.0.1]:34916->[127.0.0.1]:162) TRAP, SNMP v1, community public > iso.3.6.1.2.1.15 Enterprise Specific Trap (1) Uptime: 23:59:58.54 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 = Hex-STRING: 06 02 > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 = INTEGER: 6 # This is first BGP peer > status, which is Establish > localhost > UDP: [127.0.0.1]:34916->[127.0.0.1]:162 > iso.3.6.1.2.1.1.3.0 0:23:59:58.54 > iso.3.6.1.6.3.1.1.4.1.0 iso.3.6.1.2.1.15.0.1 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 "06 02 " > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 6 > iso.3.6.1.6.3.18.1.3.0 172.18.8.212 > iso.3.6.1.6.3.18.1.4.0 "public" > iso.3.6.1.6.3.1.1.4.3.0 iso.3.6.1.2.1.15 > > 2019-08-15 09:42:22 172.18.8.212(via UDP: > [127.0.0.1]:34916->[127.0.0.1]:162) TRAP, SNMP v1, community public > iso.3.6.1.2.1.15 Enterprise Specific Trap (2) Uptime: 1 day, 0:00:05.65 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 = Hex-STRING: 06 02 > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 = INTEGER: 6 # This is second BGP peer > status, which is also Establish > localhost > UDP: [127.0.0.1]:34916->[127.0.0.1]:162 > iso.3.6.1.2.1.1.3.0 1:0:00:05.65 > iso.3.6.1.6.3.1.1.4.1.0 iso.3.6.1.2.1.15.0.2 > iso.3.6.1.2.1.15.3.1.14.192.168.10.9 "06 02 " > iso.3.6.1.2.1.15.3.1.2.192.168.10.9 6 > iso.3.6.1.6.3.18.1.3.0 172.18.8.212 > iso.3.6.1.6.3.18.1.4.0 "public" > iso.3.6.1.6.3.1.1.4.3.0 iso.3.6.1.2.1.15 ---- Simon Jones

1 0

What's this 'interface' mean in 'neighbor' configure node ?
by Simon Jones 09 Aug '19

09 Aug '19

Hi all, I found this is new in FRR compared to QUAGGA, what's this used for ? Why I should config interface first ? Is there some DOC about this ? # neighbor 1.1.1.1/24 > ... > interface Enable BGP on interface # neighbor 1.1.1.1/24 remote-as 5001 > % Create the peer-group or interface first or specify "interface" keyword > % if using an unnumbered interface neighbor ---- Simon Jones

3 2

terminal paginate
by mike tancsa 07 Aug '19

07 Aug '19

After years of not using vtysh (habit), we are switching to use it for frr6. However, one thing I cant seem to figure out is how to make terminal paginate the default ? On FreeBSD, I have the environment var set setenv VTYSH_PAGER '/usr/bin/less -EFX' but when I connect, I always have to issue terminal paginate and then it works from there. Is there a way to make this the default ? ---Mike

2 6