September 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

ospfd crashes when deleting a route-map
by Amol Lad 27 Nov '20

27 Nov '20

Hi, I'm using FRR 7.4 (OpenWrt). I'm not using the integrated-config (i.e. each daemon has it's own config file). Below sequence of commands crashes ospfd. Please advise if any more useful debug information I can provide regarding this issue. === CRASH-1 [this happens after "no route-map SET_MED permit 10" command is executed] OSPF[9944]: Received signal 4 at 1772832797 (si_addr 0xffffffffb6f206d0); aborting... OSPF[9944]: in thread vtysh_read scheduled from lib/vty.c:2675 FRR(config)# log syslog FRR(config)# debug ospf zebra FRR(config)# debug ospf event FRR(config)# debug ospf ism FRR(config)# do show running-config Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional log syslog hostname FRR ! line vty ! End FRR(config)# route-map SET_MED permit 10 FRR(config-route-map)# set metric 3333 FRR(config-route-map)# exit FRR(config)# no route-map SET_MED permit 10 (** console hangs here for very long time and finally shows below error **) vtysh: error reading from ospfd: No such file or directory (2)Warning: closing connection to ospfd because of an I/O error! FRR(config)# === CRASH-2 [this happens after "set metric 1234" command is executed] ripd[9945]: route_set_metric_compile: Metric specified: 1234 is greater than RIP_METRIC_INFINITY, using INFINITY instead ripngd[9948]: route_set_metric_compile: Metric specified: 1234 is being converted into METRIC_INFINITY OSPF[9952]: Received signal 11 at 1772834027 (si_addr 0x8); aborting... OSPF[9952]: in thread vtysh_read scheduled from lib/vty.c:2675 FRR(config)# log syslog FRR(config)# debug ospf ism FRR(config)# debug ospf event FRR(config)# debug ospf zebra FRR(config)# do show running-config Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional log syslog hostname FRR ! line vty ! End FRR(config)# route-map SET_MED permit 10 FRR(config-route-map)# set metric 1234 (** console hangs here for very long time and finally shows below error **) vtysh: error reading from ospfd: No such file or directory (2)Warning: closing connection to ospfd because of an I/O error! AprisaLTE(config-route-map)# == root@AprisaLTE:/# cat /etc/frr/daemons # The watchfrr and zebra daemons are always started. # bgpd=yes ospfd=yes #ospfd_instances=1,20 ospf6d=yes ripd=yes ripngd=yes isisd=no pimd=no ldpd=no nhrpd=yes eigrpd=yes babeld=no sharpd=no pbrd=no bfdd=no fabricd=no vrrpd=no # # If this option is set the /etc/init.d/frr script automatically loads # the config via "vtysh -b" when the servers are started. # Check /etc/pam.d/frr if you intend to use "vtysh"! # vtysh_enable=yes zebra_options=" -A 127.0.0.1 -s 90000000 -f /opt/conf/openwrt/etc/frr/zebra.conf" bgpd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/bgpd.conf" ospfd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/ospfd.conf" ospf6d_options=" -A ::1 -f /opt/conf/openwrt/etc/frr/ospf6d.conf" ripd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/ripd.conf" ripngd_options=" -A ::1 -f /opt/conf/openwrt/etc/frr/ripngd.conf" isisd_options=" -A 127.0.0.1" pimd_options=" -A 127.0.0.1" ldpd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/ldpd.conf" nhrpd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/nhrpd.conf" eigrpd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/eigrpd.conf" babeld_options=" -A 127.0.0.1" sharpd_options=" -A 127.0.0.1" pbrd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/pbrd.conf" staticd_options="-A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/staticd.conf" bfdd_options=" -A 127.0.0.1 -f /opt/conf/openwrt/etc/frr/bfdd.conf" fabricd_options="-A 127.0.0.1" vrrpd_options=" -A 127.0.0.1" # The list of daemons to watch is automatically generated by the init script. #watchfrr_options="" # for debugging purposes, you can specify a "wrap" command to start instead # of starting the daemon directly, e.g. to use valgrind on ospfd: # ospfd_wrap="/usr/bin/valgrind" # or you can use "all_wrap" for all daemons, e.g. to use perf record: # all_wrap="/usr/bin/perf record --call-graph -" # the normal daemon command is added to this at the end.

2 7

disc0 interface in FreeBSD 12.x
by mike tancsa 01 Oct '20

01 Oct '20

Up to version 6.x of frr, I have been able to tie down larger prefixes with a static routing pointing to the discard interface on FreeBSD. eg. the static route entry ip route 10.0.0.0/8 10.128.128.144 # sh ip route 10.0.0.0/8 Routing entry for 10.0.0.0/8 Known via "static", distance 1, metric 0, best Last update 09w0d01h ago * 10.128.128.144, via disc0 where disc0 is # ifconfig disc0 disc0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 65532 inet 10.128.128.144 netmask 0xfffffffc inet6 fe80::1%disc0 prefixlen 64 scopeid 0x8 inet6 2001:db8::1 prefixlen 64 groups: disc nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> however, on frr7.4 this no longer works, On my test box % ifconfig disc0 disc0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 65532 inet 10.128.128.1 netmask 0xfffffffc inet6 fe80::1%disc0 prefixlen 64 scopeid 0x6 groups: disc nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> i3# conf t i3(config)# ip route 10.0.0.0/8 10.128.128.1 % Warning!! Local connected address is configured as Gateway IP(10.128.128.1) i3(config)# i3# sh ip route 10.0.0.0/8 % Network not in table i3# If I user disc0, it seems to work, but I get warnings on start up i3(config)# ip route 10.0.0.0/8 disc0 i3# wr Note: this version of vtysh never writes vtysh.conf Building Configuration... Configuration saved to /usr/local/etc/frr/zebra.conf Configuration saved to /usr/local/etc/frr/bgpd.conf Configuration saved to /usr/local/etc/frr/staticd.conf i3# sh ip route 10.0.0.0/8 Routing entry for 10.0.0.0/8 Known via "static", distance 1, metric 0, best Last update 00:00:07 ago * directly connected, disc0, weight 1 i3# 2020/09/30 14:57:53 STATIC: Static Route using disc0 interface not installed because the interface does not exist in specified vrf 2020/09/30 14:57:53 STATIC: Static Route using disc0 interface not installed because the interface does not exist in specified vrf the kernel routing table does seem to have it installed # netstat -nra | grep 10.0.0 10.0.0.0/8 disc0 U1 0 65532 disc0 # What is the "proper" way to do this on frr7x ? Thanks ---Mike

3 7

frr 7.x check_config generating errors / warnings FreeBSD 12
by mike tancsa 01 Oct '20

01 Oct '20

Hi All, With frr7.4, starting up the daemons seems to generate a whole mess of warnings / errors which doing their check. Are they actually errors or false positives ? The daemon seems to start up fine e.g. # zebra -C 2020/09/30 17:17:37 ZEBRA: [EC 4043309110] Disabling MPLS support (no kernel support) but staticd # staticd -C 2020/09/30 17:18:10 STATIC: Static Route using disc0 interface not installed because the interface does not exist in specified vrf 2020/09/30 17:18:10 STATIC: Static Route using disc0 interface not installed because the interface does not exist in specified vrf 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra 2020/09/30 17:18:10 STATIC: static_zebra_nht_register: Failure to send nexthop to zebra with the last message being generating for every static route I have in my config eg ip route 10.11.13.0/28 192.168.135.68 ip route 10.20.30.16/30 192.168.135.68 However, starting up the daemons seem to be ok. zebra -v zebra version 7.4 Copyright 1996-2005 Kunihiro Ishiguro, et al. configured with: '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--disable-doc-html' '--sysconfdir=/usr/local/etc/frr' '--localstatedir=/var/run/frr' '--disable-backtrace' '--disable-nhrpd' '--disable-pimd' '--disable-vrrpd' '--with-vtysh-pager=cat' '--disable-config-rollbacks' '--disable-datacenter' '--enable-fpm' '--disable-ldpd' '--without-libpam' '--enable-rpki' '--disable-shell-access' '--disable-snmp' '--disable-tcmalloc' '--enable-vtysh' '--prefix=/usr/local' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/share/info/' '--build=amd64-portbld-freebsd12.1' 'build_alias=amd64-portbld-freebsd12.1' 'PKG_CONFIG=pkgconf' 'CC=cc' 'CFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'LDFLAGS= -L/usr/local/lib -L/usr/local/lib -fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=-I/usr/local/include -I/usr/local/include' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'PYTHON=/usr/local/bin/python3.7' staticd -v staticd version 7.4 Copyright 1996-2005 Kunihiro Ishiguro, et al. configured with: '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--disable-doc-html' '--sysconfdir=/usr/local/etc/frr' '--localstatedir=/var/run/frr' '--disable-backtrace' '--disable-nhrpd' '--disable-pimd' '--disable-vrrpd' '--with-vtysh-pager=cat' '--disable-config-rollbacks' '--disable-datacenter' '--enable-fpm' '--disable-ldpd' '--without-libpam' '--enable-rpki' '--disable-shell-access' '--disable-snmp' '--disable-tcmalloc' '--enable-vtysh' '--prefix=/usr/local' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/share/info/' '--build=amd64-portbld-freebsd12.1' 'build_alias=amd64-portbld-freebsd12.1' 'PKG_CONFIG=pkgconf' 'CC=cc' 'CFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'LDFLAGS= -L/usr/local/lib -L/usr/local/lib -fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=-I/usr/local/include -I/usr/local/include' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'PYTHON=/usr/local/bin/python3.7' ---Mike

2 2

FreeBSD 12.1 / FRR 7.4, error inserting v6 routes into zebra/kernel
by Muenz, Michael 30 Sep '20

30 Sep '20

Hi, I'm maintaining the FRR plugin for OPNsense Firewall, currently based on FreeBSD/HardenedBSD 12.1 with FRR 7.4. I received a report from a user that a peering via v6 the bgpd successfully receives the v6 routes which are also displayed in sh bgp ipv6, but they wont get into the routing table and in frr.log there's: kernel_rtm: X:X:X:X rtm_write() unexpectedly returned -2 for command RTM_ADD Bit more details and screenshots are also here available: https://twitter.com/TallWireless/status/1309489192502734850

2 2

ask for MPLS implementation
by Eric Barrieres 30 Sep '20

30 Sep '20

Hello, I have to found one technical solution to create an MPLS routing protocol within satellites. The objectives is to permit network between satellites using the MPLS protocol in free space. Do you know if frr routing software can do it? I am not interested in the API permitting encapsulation the MPLS in a GRE Tunnel. Regards,

1 0

BGP: /32 network cannot be advertised unless "no bgp network import-check" is present
by Amol Lad 28 Sep '20

28 Sep '20

Hi, I've configured a dummy interface (in Linux) with IP Address 1.1.1.1/32 and advertising it in BGP. However, this network is not getting advertised unless I also give "no bgp network import-check" command. Please see below for more details and advise what could be going wrong or I'm missing some other configuration. (Same is true with IPv6 address with /128 prefix - this also cannot be advertised unless no import-check is given even though the address present in IPv6 routing table) Thanks Amol Current configuration: ! frr version 7.4 frr defaults traditional hostname FRR log syslog ! router bgp 1 no bgp ebgp-requires-policy neighbor 10.10.10.2 remote-as 2 ! address-family ipv4 unicast network 1.1.1.1/32 exit-address-family ! line vty ! end ==== FRR(config-router)# do show ip route 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 K * 1.1.1.1/32 [0/10] is directly connected, loop0, 00:54:33 C>* 1.1.1.1/32 is directly connected, loop0, 00:54:33 === [ As you can see "*>" is missing before 1.1.1.1/32. However, If I give "no bgp network import-check" then *> comes here and network is advertised to neighbor] FRR(config-router)# do show bgp ipv4 unicast BGP table version is 2, local router ID is 172.17.1.106, vrf id 0 Default local pref 100, local AS 64512 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 1.1.1.1/32 0.0.0.0 0 32768 i Displayed 1 routes and 1 total paths === root@FRR:/# ip addr show loop0 6: loop0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 52:db:5f:99:52:d4 brd ff:ff:ff:ff:ff:ff inet 1.1.1.1/32 brd 255.255.255.255 scope global loop0 valid_lft forever preferred_lft forever inet6 fe80::50db:5fff:fe99:52d4/64 scope link valid_lft forever preferred_lft forever ===

2 2

OSPF with FRR and Nexus
by Travis Garrison 23 Sep '20

23 Sep '20

I have a Nexus 9300 that I am trying to get connected to FRR using OSPF. I have several Mikrotiks and other routers connected but this is my first Nexus. I think the issue is with my config on the nexus side. Any one have any ideas on what I missed? FRR - 7.4 release Debian 10.4 Interface configured with 100.76.0.1/30 address interface eno1d1 ip ospf network point-to-point ! router-id 100.78.0.3 ! router ospf ospf router-id 100.78.0.3 network 100.76.0.0/30 area 0.0.0.0 network 100.78.0.3/32 area 0.0.0.0 Nexus interface Ethernet1/49 ip address 100.76.0.2/30 ip ospf network point-to-point ip router ospf 0 area 0.0.0.0 no shutdown interface loopback0 ip address 100.78.0.1/32 ip router ospf 0 area 0.0.0.0 router ospf 0 router-id 100.78.0.1

1 1

Is there an IPv6 forwarding bug in FRR running in namespace?
by Peter Olsson 23 Sep '20

23 Sep '20

Or am I doing it wrong? (But it works in quagga.) Debian 10.5. FRR tried both 6.0.2 and 7.3.1. Installed package is frr-snmp. This is what i do: /etc/sysctl.d/local.conf: net.ipv4.ip_forward=1 net.ipv6.conf.all.forwarding=1 mkdir -p /run/frr/$NS chown frr:frr /run/frr/$NS /sbin/ip netns add $NS /sbin/ip netns exec $NS /sbin/ip link set dev lo up Create two interfaces, one of which is a veth peer to a veth interface in the default namespace. Both interfaces have IPv4 and IPv6 addresses. /sbin/ip netns exec $NS /usr/lib/frr/zebra -d -A 127.0.0.1 -s 90000000 -N $NS /sbin/ip netns exec $NS /usr/lib/frr/bgpd -d -A 127.0.0.1 -N $NS /sbin/ip netns exec $NS /usr/lib/frr/ospfd -d -A 127.0.0.1 -N $NS /sbin/ip netns exec $NS /usr/lib/frr/ospf6d -d -A 127.0.0.1 -N $NS /sbin/ip netns exec $NS /usr/lib/frr/staticd -d -A 127.0.0.1 -N $NS cat /proc/sys/net/ipv6/conf/*/forwarding show all ones. (However, the namespace interfaces aren't displayed in /proc/sys/net/ipv6/conf, just the default namespace interfaces. But the same goes for IPv4, and I have no problems with IPv4.) In /etc/frr/$NS/zebra.conf I have this configuration: " frr version 7.3.1 frr defaults traditional hostname xxx password xxx enable password xxx log syslog informational log facility local6 ! interface xxx ip address xxx ipv6 address xxx ! interface veth-xxx-C ip address xxx ipv6 address xxx ! line vty exec-timeout 60 0 " Every time I reboot this server, ipv6 forwarding is turned off in the namespace zebra. ipv6 forwarding works fine in the default namespace, and ipv4 forwarding works fine both in $NS and the default namespace. # ip netns exec ipvpn-gotanet telnet localhost 2601 Hello, this is FRRouting (version 7.3.1). # sh run ... no ipv6 forwarding ... # sh ip for IP forwarding is on # sh ipv for ipv6 forwarding is off sh start doesn't display the "no ipv6 forwarding" line. I also noticed that two other FRR servers, running Debian 10.3, have the same problem, showing "no ipv6 forwarding" in the running zebra configuration. Those two servers don't use IPv6 in namespaces, so I haven't noticed this problem in them before now. This has never been a problem in quagga. Thanks! Peter Olsson

1 1