- frog - lists.frrouting.org

Blackhole route unreachable
by matthieu flye sainte marie 14 Dec '20

14 Dec '20

Hi, I am trying to set up a static route to blackhole, but the next hop is unreachable: Here are the route I am trying to push (notice I have tried blackhole and Null0): ip route 192.0.2.1/32 blackhole ip route 192.0.2.2/32 Null0 But the routers keep saying the next hop is unreachable: show ip route static 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, r - rejected, b - backup S>* 192.0.2.1/32 [1/0] unreachable (blackhole), weight 1, 00:07:48 S>* 192.0.2.2/32 [1/0] unreachable (blackhole), weight 1, 00:08:15 show ip route 192.0.2.1/32 Routing entry for 192.0.2.1/32 Known via "static", distance 1, metric 0, best Last update 00:08:23 ago * unreachable (blackhole), weight 1 I need this to work in order to set up RTBH (null route the next hop). On a Cisco router, the same configuration show a directly connected route : show ip route 192.0.2.1 Routing entry for 192.0.2.1/32 Known via "static", distance 1, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via Null0 Route metric is 0, traffic share count is 1 Thank you Regards

1 0

ip nhrp map multicast
by Amol Lad 11 Dec '20

11 Dec '20

Hi, I'm keen on adding this support so DMVPN can work over OSPF/EIGRP. The issue is described in https://github.com/FRRouting/frr/issues/6276 If someone can tell what actually is the issue and a high level overview of what needs to be done then I can add this support. Amol

4 4

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

FRRouting and MPLS
by Olivier CALVANO 23 Nov '20

23 Nov '20

Hello, I have just installed FRR for the first time on a Linux CentOS 8 distribution. I am therefore just starting out. I am gradually reading the forums but there is a lot of information. FRR manages without worries the BGP and the ISIS which I use regularly on my cisco routers. I am now trying to find out if FRR can integrate more deeply into my network, particularly at the MPLS level. as I understood it is in the Kernel that this is done and not in FRR, but is there a way to integrate VRF IP VPN? and the creation of a VLAN type subinterface directly in FRR? Then last question: Is there an implementation of the Cisco EoMPLS equivalent in FRR? (xconnect encapsultation mpls) thank you Olivier

2 1

Re: [FROG] ipv6 nd managed-config-flag ignored?
by Thomas Pircher 23 Nov '20

23 Nov '20

For the archive. Cumulus support was able to help me on this issue. The problem was that I'm using VRRP on top of the VLAN interface, so the IPv6 ND settings had to be configured on the VRRP interface, and not on the underlying VLAN interface: | interface vrrp6-63-3 | ipv6 nd managed-config-flag | ipv6 nd ra-interval 5 | no ipv6 nd suppress-ra So once this was set, everything seems to work fine. I hope the ifindex (63) in the interface name won't change, but that is a separate issue... Thanks, Thomas

1 0

Snmp and agentx
by Matthieu 22 Nov '20

22 Nov '20

Hi, It is the first time that I post on the mailing list, excuse me if it is the wrong place to ask this. I can’t get SNMP to work with SNMP, I have followed this documentation : http://docs.frrouting.org/en/latest/snmp.html <http://docs.frrouting.org/en/latest/snmp.html> 1. Here is my setup: Debian GNU/Linux 9 dpkg -l | grep frr ii frr 7.5-0~deb9 amd64 FRRouting suite of internet protocols (BGP, OSPF, IS-IS, ...) ii frr-pythontools 7.5-0~deb9 all FRRouting suite - Python tools ii frr-snmp 7.5-0~deb9 amd64 FRRouting suite - SNMP support I have used the version from the repo and added frr-snmp (not compiled from source). 2. Here is my /etc/snmp/snmpd.conf: com2sec readonly default **** group MyROGroup v2c readonly view all included .1 80 access MyROGroup "" any noauth exact all none none #Distro Detection extend .1.3.6.1.4.1.2021.7890.1 distro /usr/bin/distro dontLogTCPWrappersConnects true # # This is the default view view all included .1 80 # # # Remove ipRouteTable from view view all excluded .1.3.6.1.2.1.4.21 # # # Remove ipNetToMediaTable from view view all excluded .1.3.6.1.2.1.4.22 # # # Remove ipNetToPhysicalPhysAddress from view view all excluded .1.3.6.1.2.1.4.35 # # Remove ipCidrRouteTable from view view all excluded .1.3.6.1.2.1.4.24 # # # Optionally protect SNMP private/secret values view all excluded .1.3.6.1.6.3.15 view all excluded .1.3.6.1.6.3.16 view all excluded .1.3.6.1.6.3.18 master agentx 3. Here is my /etc/snmp/zebra.conf file: com2sec readonly default **** group MyROGroup v1 readonly view all included .1 80 access MyROGroup "" any noauth exact all none none master agentx 4. I have modified this file /etc/frr/daemons in order to enable SNMP support for each daemon: zebra_options=" -A 127.0.0.1 -s 90000000 -M snmp" bgpd_options=" -A 127.0.0.1 -M snmp" ospfd_options=" -A 127.0.0.1 -M snmp" ospf6d_options=" -A ::1 -M snmp" 5. Each of the routing process have agentx enabled in the config: zebra, bgpd, ospfd, ospf6d. But Frr is complaining in the log: tail -f /var/log/frr/frr.log Nov 22 12:19:12 border3 zebra[11311]: [EC 100663310] snmp[warning]: Warning: Failed to connect to the agentx master agent ([NIL]): Nov 22 12:19:12 border3 ospfd[11323]: [EC 100663310] snmp[warning]: Warning: Failed to connect to the agentx master agent ([NIL]): Nov 22 12:19:12 border3 bgpd[11316]: [EC 100663310] snmp[warning]: Warning: Failed to connect to the agentx master agent ([NIL]): Nov 22 12:19:14 border3 ospf6d[11326]: [EC 100663310] snmp[warning]: Warning: Failed to connect to the agentx master agent ([NIL]): SNMP is working fine for the global system (CPU, disk space, etc…) but not for the specific OID about routing processes. Do you know what I am doing wrong ? Thank you

1 0

question on OSPF over GRE support and possible limitations
by Andrea di donato 19 Nov '20

19 Nov '20

Hello all, I haven't tested FRR yet but was wondering whether FRR is able to form an OSPF adjacency over a GRE tunnel. I was also wondering if there was any limitation should the GRE tunnel dst ip address be resolved by a BGP prefix rather than by an IGP prefix or a static route. I am saying this as, for instance, Cisco IOSXR had and possibly still has that kind of limitation where the ospf process couldn't perform recursive lookups as such in order to then send helloes and flood LSAs ... Cheers Andrea Di Donato -- (?P<whatever>.*IE) No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.

1 0

Re: [FROG] ipv6 nd managed-config-flag ignored?
by Donald Sharp 17 Nov '20

17 Nov '20

Thomas - >From a very quick code inspection it sure looks like we set the flag. I even went and looked at the 4.0+cl3u17 code and it's identical to master. I would suggest you open a case with Cumulus Support to get it looked at. donald On Tue, Nov 17, 2020 at 5:48 AM Thomas Pircher via frog <frog(a)lists.frrouting.org> wrote: > > > > > ---------- Forwarded message ---------- > From: Thomas Pircher <thp.frrouting(a)p5r.uk> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Tue, 17 Nov 2020 10:47:02 +0000 > Subject: ipv6 nd managed-config-flag ignored? > Hi, > > I'm using frr version 4.0+cl3u17 on a Cumulus router. I'm having > troubles setting the managed-config-flag for RA packets. I have this in > my configuration file for the VLAN interface I'd like to configure with > the managed-config-flag on: > > | interface vlan124 > | vrrp 3 > | vrrp 3 ipv6 fd00:4d56:414c:6000::1 > | vrrp 3 priority 150 > | ipv6 nd managed-config-flag > > > But when I sniff the outgoing packets on the interface, I get "Flags [none]" in tcpdump: > > | # tcpdump -lnn -i vlan124 -vvvv -ttt icmp6 and 'ip6[40] = 134' > | tcpdump: listening on vlan124, link-type EN10MB (Ethernet), capture size 262144 bytes > | 00:00:00.000000 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) fe80::c981:f4f7:7f26:a79b > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 24 > | hop limit 64, Flags [none], pref medium, router lifetime 48s, reachable time 0ms, retrans timer 0ms > | source link-address option (1), length 8 (1): 00:00:5e:00:02:03 > | 0x0000: 0000 5e00 0203 > > Is there something I'm doing wrong? Any help is appreciated. > > Thanks, > Thomas > > > > > ---------- Forwarded message ---------- > From: Thomas Pircher via frog <frog(a)lists.frrouting.org> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Tue, 17 Nov 2020 10:47:02 +0000 > Subject: [FROG] ipv6 nd managed-config-flag ignored? > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog

2 1

ipv6 nd managed-config-flag ignored?
by Thomas Pircher 17 Nov '20

17 Nov '20

Hi, I'm using frr version 4.0+cl3u17 on a Cumulus router. I'm having troubles setting the managed-config-flag for RA packets. I have this in my configuration file for the VLAN interface I'd like to configure with the managed-config-flag on: | interface vlan124 | vrrp 3 | vrrp 3 ipv6 fd00:4d56:414c:6000::1 | vrrp 3 priority 150 | ipv6 nd managed-config-flag But when I sniff the outgoing packets on the interface, I get "Flags [none]" in tcpdump: | # tcpdump -lnn -i vlan124 -vvvv -ttt icmp6 and 'ip6[40] = 134' | tcpdump: listening on vlan124, link-type EN10MB (Ethernet), capture size 262144 bytes | 00:00:00.000000 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) fe80::c981:f4f7:7f26:a79b > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 24 | hop limit 64, Flags [none], pref medium, router lifetime 48s, reachable time 0ms, retrans timer 0ms | source link-address option (1), length 8 (1): 00:00:5e:00:02:03 | 0x0000: 0000 5e00 0203 Is there something I'm doing wrong? Any help is appreciated. Thanks, Thomas

1 0

Announcing the 7.5 release of FRR
by Donald Sharp 16 Nov '20

16 Nov '20

All - I'd like to announce the 7.5 release of FRR! Debian Packaging - https://deb.frrouting.org/ Snap Packaging - https://snapcraft.io/frr RPM Packaging - https://rpm.frrouting.org/ Github Release - FreeBSd Packaging - Are built and available in FreeBSD packages/port BFD Profile support Minimum ttl support BGP rpki VRF support GR fixes Add wide option to display of routes Add `maximum-prefix <num> force` Add `bestpath-routes` to neighbor command Add `bgp shutdown message MSG...` command Add v6 Flowspec support Add `neighbor <neigh> shutdown rtt` command Allow update-delay to be applied globaly EVPN Beginning of MultiHoming Support ISIS Segment Routing Support VRF Support Guard against adj timer display overflow Add support for Anycast-SIDs OSPF Segment Routing support for ECMP Various LSA fixes Prevent crash if transferring config amongst instances PBR Adding json support to commands DSCP/ECN based PBR Matching PIM Add more json support to commands Fix missing mesh-group commands MSDP SA forwarding Clear (s,g,rpt) ifchannel on (*, G) prune received Fix igmp querier election and IP address mapping Crash fix when RP is removed STATIC Northbound Support YANG Filter and route-map Support OSPF model definition BGP model definition VTYSH Fix build-time errors for some --enable flags Speed up output of configuration across daemons ZEBRA nexthop group support for FPM northbound support for rib model Backup nexthop support netlink batching support Allow upper level protocols to request ARP Add json output for zebra ES, ES-EVI and access vlan dumps Upgrade to using libyang1.0.184 RPM Moved RPKI to subpackage Added SNMP subpackage Centos 6 and Debian Jessie have been deprecated As always there are too many bugfixes to list individually. This release compromises just over 1k of commits by the community, with contributors from 70 people. thanks! Donald

2 2