November 2020 - frog - lists.frrouting.org

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 17 Nov '20

17 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

What causes a prefix received from a downstream to be "invalid"?
by Michael Hohl 09 Nov '20

09 Nov '20

Hello FRRouting community, I've tried to add an IPv6-only downstream to my dual-stack FRRouting-powered BGP setup, but for some reason the prefix of that downstream wasn't distributed to my upstream ISP. So, I consulted `show bgp summary` and spotted that this is the only route which isn't marked as `valid` indicated by a `*`. RPKI isn't enabled, otherwise I would have immediately suspected that to cause some prefix to be invalid. The only thing that makes this downstream different is that it is IPv6-only. What does it mean that a (received) prefix is considered "invalid"? Here is the output for `show bgp 2001:XX:YY::`: ``` BGP routing table entry for 2001:XX:YY::/48 Paths: (1 available, no best path) Not advertised to any peer ZZZZZZ 2a0d:f300:0:VVVV::1 (inaccessible) from 2a0d:f300:0:VVVV::1 (193.219.VV.VV) Origin IGP, invalid, external Last update: Mon Nov 9 09:00:00 2020 ``` ZZZZZZ ... is the downstreams ASN 2001:XX:YY:: ... is the IPv6 prefix the downstream wants to announce 2a0d:f300:0:VVVV::1 ... is the IPv6 address used to run the BGP router of the downstream 193.219.VV.VV ... is the IPv4 address assigned by me to the downstream, but he doesn't really use that one In case the FRRouting version is relevant for this issue, I'm running 7.3.1. Thanks in advance for any help, Michael

3 2