- frog - lists.frrouting.org

EIGRP: neighbor configuration validation error
by Amol Lad 14 Oct '20

14 Oct '20

Hi, I'm getting below error when trying to setup EIGRP neighbor. I initially suspected it could be because of /32 prefix but same problem comes with /24 network also. FRR(config)# router eigrp 123 FRR(config-router)# network 10.0.0.254/32 FRR(config-router)# neighbor 10.0.0.1 % Configuration failed: validation error. Please check the logs for more details. FRR(config-router)# Syslog output: warning 2035-03-29T19:10:55+00:00 eigrpd: [EC 100663331] nb_callback_configuration: error processing configuration change: error [internal inconsistency] event [validate] operation [create] xpath [/frr-eigrpd:eigrpd/instance[asn='65000'][vrf='default']/neighbor[.='10.0.0.1']] warning 2035-03-29T19:10:55+00:00 eigrpd: [EC 100663337] nb_candidate_commit_prepare: failed to validate candidate configuration I'm using FRR 7.4 and libyang 1.0.167 Please advise. Thanks Amol == FRR(config-router)# do show ip route ... N>* 10.0.0.1/32 [10/0] is directly connected, gre1, weight 1, 00:15:37 N>* 10.0.0.2/32 [10/0] is directly connected, gre1, weight 1, 00:28:34 E 10.0.0.254/32 [90/28160] is directly connected, gre1, weight 1, 00:00:12 C>* 10.0.0.254/32 is directly connected, gre1, 21:34:35 ... FRR(config-router)# do show ip eigrp interfaces EIGRP interfaces for AS(123) Interface Bandwidth Delay Peers Xmit Queue Mean Pacing Time Multicast Pending Hello Holdtime Un/Reliable SRTT Un/Reliable Flow Timer Routes gre1 100000 10 0 0 / 0 0 0 0 0 5 15 === 24: gre1@eth2: <MULTICAST,UP,LOWER_UP> mtu 1472 qdisc noqueue state UNKNOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 inet 10.0.0.254/32 brd 255.255.255.255 scope global gre1 valid_lft forever preferred_lft forever

2 1

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

Redistributing routes in EIGRP and route-map
by Amol Lad 22 Sep '20

22 Sep '20

Hi, We can redistribute routes in EIGRP using "redistribute" command. For example, from FRR documentation: redistribute bgp metric (1-4294967295) (0-4294967295) (0-255) (1-255) (1-65535) redistribute bgp redistributes routing information from bgp route entries into the EIGRP tables. Is there a way to filter these routes using a route-map as done in other protocols such as BGP? I'm using release 7.4 and don't see route-map option. Please advise. Thanks Amol

2 1

Regarding FRR Pim Protocol Function
by Pankaj Garbyal 18 Sep '20

18 Sep '20

Hello Sir/Madam, I am using FRRRouting Release 5.1 for PIM Protocol support in my Switch. But I find that PIM Protocol is not acknowledging the multicast packets coming towards it. When i compared the same with FRR installed in Linux PC, i found that a new interface named "pimreg" is enabled by FRR but the same is not happening in FRR of my switch. Kindly provide me help to get the pimreg interface option in my switch through FRR. also provide some information on the role of "pimreg" to run the PIM Protocol at FRR. Attached here my quagga build file for your reference. Thank you in advance for your support. Regards, Pankaj Garbyal Mobile: +91-9873987203

2 1