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

nhrpd event manager
by Joe Maimon 01 Mar '21

01 Mar '21

I have successfully gotten frr,nhrpd,strongswan,charon all running on another system for a dmvpn application. I am currently trying to do another setup, but without vpn/ipsec, just nhrp/gre. Its not working out well, debug logs show Netlink: Received msg_type 28 which if I recall correctly suggests that the neighbor entry isnt being installed correctly, trying it as root worked even less. So while poking around, I see there is an entire event manager unix sock structure. Perhaps I can parse that and do it myself? However, this is as far as I got. I am interacting with it via shell script. Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: sending event authorize-binding Mar 15 08:11:35 debian67 nhrpd[20977]: Send Registration-Reply(4) 192.168.241.129 -> 192.168.241.130 Mar 15 08:11:35 debian67 nhrpd[20977]: PACKET: Send 45.77.146.76 -> 209.51.164.27 Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: eventid=214 Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: result=accept Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: received: eventid=214 result= Mar 15 08:11:45 debian67 nhrpd[20977]: cache: t67 192.168.241.130: timeout Mar 15 08:11:46 debian67 nhrpd[20977]: Netlink: Received msg_type 28, msg_flags 0 I have looked at the source and I cant seem to convince the function to recognize that result should be "accept". Any advice appreciated. Joe For the interested, the below is the fledgling script #!/bin/bash PROGNAME=`basename $0` VERSION="0.0.1" usage() { echo "Usage: $PROGNAME -s nhrp-sock [-i interface-name] [-u user] [-g group] " echo "" echo "-s nhrp-sock file" echo "-i interface-name to execute on, may be repeated multiple times" echo "-u user to own the sock" echo "-g group to own the sock" exit 1 } SOCK="/var/run/frr/nhrp.sock" USER="frr" GROUP="frr" j=0 while getopts s:i:u:g: opt; do case "$opt" in s) SOCK="$OPTARG" ;; i) INTARR[((j++))]="$OPTARG" ;; u) USER="$OPTARG" ;; g) GROUP="$OPTARG" ;; esac; done coproc socat - UNIX-LISTEN:$SOCK,unlink-early,setuid-early=$USER || exit 1 OLDIFS="$IFS" while read -r S; do if [[ "$S" == "" ]]; then if [[ "$EVID" != "" ]]; then echo -e "eventid=$EVID\nresult=accept\n"; fi unset EVID unset EVINT continue; fi IFS="${IFS}=" SA=($S) IFS="$OLDIFS" case "${SA[0]}" in eventid) EVID="${SA[1]}" ;; interface) EVINT="${SA[1]}" esac done <&"${COPROC[0]}" >&"${COPROC[1]}" kill "$COPROC_PID"

2 3

vtysh line length
by Jens Link 28 Apr '20

28 Apr '20

Hi, as I can't find anything in the documentation and on google, but maybe I just search wrong. Can the line length of vtysh be changes? It looks like its wrapping lines at 80 columns which makes it harder to parse the output in shell script. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink(a)quux.de | --------------- | ----------------------------------------------------------------------------

4 5

Is there some performance report and bugfix list about FRR and QUAGGA ?
by Simon Jones 26 Apr '20

26 Apr '20

Hi all, Now we need to compare QUAGGA and FRR, used for BGP stack, with lots of routes and large QPS. So, 1) Is there some performance report about FRR and QUAGGA? Like RIB size, FIB size, speed of FIB route instoring, speed of route withdraw, etc. 2) Is there some bugfix list which FRR fixed and QUAGGA not fixed. Thank you !!! ---- Simon Jones

2 1

Display in wrong order for prefix-list
by Sébastien 65 24 Apr '20

24 Apr '20

Hi, I note that the display of a prefix-list AND bgp as-path access-list is not in the correct order, the sequences are mixed and this is not easily readable ... ip prefix-list LIST1 seq 10 deny X ip prefix-list LIST1 seq 100 deny X ip prefix-list LIST1 seq 105 deny X ip prefix-list LIST1 seq 15 deny X ip prefix-list LIST1 seq 20 deny X ip prefix-list LIST1 seq 200 permit X ip prefix-list LIST1 seq 25 deny X ip prefix-list LIST1 seq 30 deny X ip prefix-list LIST1 seq 35 deny X ip prefix-list LIST1 seq 40 deny X ip prefix-list LIST1 seq 45 deny X ip prefix-list LIST1 seq 5 deny X How to display the sequences in the right order (10,15,20,25,...,100,105,200,...)? Thank you !

4 6

L3vpn and FRR - Issue
by Rakesh M 23 Apr '20

23 Apr '20

Hi All, I have a peculiar problem with reaching two VPN endpoints between L3VPN enabled FRR Routers I see the routes and everything w.r.t to control plane appears to be fine, but when I try to source the traffic I cant ping each other r1# sh ip route vrf BLUE 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, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route VRF BLUE: B> 100.65.64.152/30 [200/0] via x.x.x.x(vrf default) (recursive), label 16, 00:33:56 * via 100.65.64.137, bond0.3054(vrf default), label 179/16, 00:33:56 C>* 100.65.64.156/30 is directly connected, bond0.3600, 00:47:03 B> 100.65.64.160/30 [200/0] via x.x.x.x(vrf default) (recursive), label 16, 00:13:06 * via 100.65.64.137, bond0.3054(vrf default), label 179/16, 00:13:06 C>* 100.65.64.164/30 is directly connected, eth10, 00:13:24 *root@r1:~# ping -I eth10 100.65.64.161ping: Warning: source address might be selected on device other than eth10.PING 100.65.64.161 (100.65.64.161) from 100.65.64.138 eth10: 56(84) bytes of data.^C* I don't understand this message at all, why it always picking a wrong address when I try to ping it. Can anyone give insights to this? -- -- Rakesh Madupu 2xJNCIE - SP/DC / CCIE-SP#47613 https://r2079.wordpress.com

1 0

Why two duplicate route-map exist in bgpd and zebra ?
by Simon Jones 21 Apr '20

21 Apr '20

Hi all, I'm using quagga-0.99, I set a route-map by vtysh like this: vtysh# prefix-list ARP2HOST_PL3 ... > vtysh# route-map ARP2HOST_RM2 deny sequence 6 > vtysh# match interface lo > vtysh# route-map ARP2HOST_RM2, permit, sequence 10 > vtysh# match ip address prefix-list ARP2HOST_PL3 But I found there are two SAME route-map exist in zebra and bgpd, like this: vtysh# show route-map > ZEBRA: > route-map ARP2HOST_RM2, deny, sequence 6 > Match clauses: > interface eth0 > Set clauses: > Call clause: > Action: > Exit routemap > route-map ARP2HOST_RM2, permit, sequence 10 > Match clauses: > ip address prefix-list ARP2HOST_PL3 > Set clauses: > Call clause: > Action: > Exit routemap > BGP: > route-map ARP2HOST_RM2, deny, sequence 6 > Match clauses: > Set clauses: > Call clause: > Action: > Exit routemap > route-map ARP2HOST_RM2, permit, sequence 10 > Match clauses: > ip address prefix-list ARP2HOST_PL3 > Set clauses: > metric 13 > community 0:100 > Call clause: > Action: > Exit routemap And when I use command > vtysh# redistribute static route-map ARP2HOST_RM2 the redistribute will NOT process any static route SOMETIME, not always !!! Then I compare by add route-map through zebra.conf and bgpd.conf, like this: > zebra.conf: > route-map ARP2HOST_RM2 deny sequence 6 > match interface lo > > bgpd.conf: > prefix-list ARP2HOST_PL3 ... > route-map ARP2HOST_RM2, permit, sequence 10 > match ip address prefix-list ARP2HOST_PL3 And show route-map result beome: > vtysh# show route-map > ZEBRA: > route-map ARP2HOST_RM2, deny, sequence 6 > Match clauses: > interface eth0 > Set clauses: > Call clause: > Action: > Exit routemap > BGP: > route-map ARP2HOST_RM2, permit, sequence 10 > Match clauses: > ip address prefix-list ARP2HOST_PL3 > Set clauses: > metric 13 > community 0:100 > Call clause: > Action: > Exit routemap Then the redistribute will work. focus on code, I guess ALL of zebra(zebra_routemap.c) and bgpd(bgp_routemap.c) will process route-map from vtysh command, which cause this bug? If it is, how to set route-map correctly by vtysh? Thanks !!! ---- Simon Jones

3 3

IS-IS Error
by Mark Tinka 19 Apr '20

19 Apr '20

Hi all. I'm almost there getting IS-IS to work without issue. I'm now faced with the following error log: 2020/04/17 10:02:01 ISIS: IS-IS bpf: could not transmit packet on em0: Input/output error 2020/04/17 10:02:01 ISIS: [EC 67108865] ISIS-Snp (1): Send L2 PSNP on em0 failed This repeats every second. Anyone know what this could be? Systems is FreeBSD-12.1-RELEASE-p3. Despite the error, IS-IS is running and routing is good, talking to a Cisco IOS XE implementation on the other side. So the error is throwing me off. Mark.

2 2

fd80 prefix allocation
by Tran (US), Katherine K 16 Apr '20

16 Apr '20

Hello, Does anyone know how FRR treats "fd80" prefixes? My configuration uses "fd80" prefixes as Unique Local IPv6 Unicast Addresses (IETF RFC 4193), which can be routed. But, somehow, FRR changes these "fd80" addresses to "fe80". Thanks, Katherine

3 7

getting IS-IS routerIPs in BGP-LS
by Colin Zeidler 16 Apr '20

16 Apr '20

Hi, I am trying to monitor an IS-IS network using BGP-LS to receive the network topology. In IS-IS the LSP typically contains a routerIP entry that provides a IP address on the device the LSP is about. This is useful when monitoring the network as it provides an IP that can be queried with SNMP for more information about the given router. In BGP-LS the RFCs show that there is a Node attribute for the IPv4 address/ID of a router, but this is not populated when distributing an IS-IS network (cisco router sending BGP-LS). Is there a known way to configure a router to provide an IP address as part of the BGP-LS node attributes when distributing IS-IS linkstate? My BGP-LS setup involves a cisco ISIS network with 1 router per area, configured with bgp-ls, peered with frr such that frr will receive the BGP-LS messages (but not do anything with them) Currently my solution involves looking at the advertised prefixes. Prefixes with a IS-IS level of 1, and a /32 mask are an IP address that exists on the named router and can be pinged or queried with SNMP. This works until we encounter a L2-only IS-IS router, as the level2 advertised prefixes can exist from any other router in the area, not just interfaces on the device. A potential workaround for this issue with the l2-only routers I think is to check for the prefix with the lowest metric cost and use that one, though this runs the risk of a local /32 prefix being configured with a higher cost than the links + a neighbors /32 (is this something that would realistically happen?) and choosing the wrong IP address. Are there any potential issues with that solution? Thanks, Colin

1 1