- announce - lists.frrouting.org

Fwd: [NetDev-People] 0x13: An Asynchronous Dataplane for FRR
by Donald Sharp 09 Feb '19

09 Feb '19

Mark - Congratulations on being accepted to talk about your work on FRR's data plane. thanks! donald ---------- Forwarded message --------- From: Jamal Hadi Salim via people <people(a)lists.netdevconf.org> Date: Sat, Feb 9, 2019 at 8:46 AM Subject: [NetDev-People] 0x13: An Asynchronous Dataplane for FRR To: people <people(a)netdevconf.org> Cc: <program-committee(a)netdevconf.org> Nuts and bolts Talk. The FRR (Free-range Routing) software suite is going through a revamp. There is a move to an async threaded model which is planned to utilize new netlink features to improve scalability. This model will also allow programming FIBs and NHs on remote systems. In this talk Mark Stapp will describe the current state of the work and challenges involved in achieving this goal. Some initial results and future plans will be discussed. https://netdevconf.org/0x13/news.html?talk-FRR-async cheers, jamal _______________________________________________ people mailing list people(a)netdevconf.org https://lists.netdevconf.org/cgi-bin/mailman/listinfo/people

1 0

Kernel Bug with address retrieval
by Donald Sharp 18 Jan '19

18 Jan '19

All - The 4.20 linux kernel has a bug with sending link addresses to user-space causing some of them not to be read. The tl;dr; is that after one skb of data sent up, the data is stopped from being sent. If you have a small number of addresses assigned to a box, then you will probably not notice a problem. At this time I would not recommend using linux kernel 4.20 for production network uses. The commit that fixes this is this: commit 7c1e8a3817c55d73b27cc29b84075999c8894179 Author: Arthur Gautier <baloo(a)gandi.net> Date: Mon Dec 31 02:10:58 2018 +0000 netlink: fixup regression in RTM_GETADDR It is my understanding that this was introduced in 4.19-next. This fix should be available in one of the upcoming 4.20.X releases as I understand it. thanks! donald

1 0

New Releases of FRR
by Donald Sharp 11 Jan '19

11 Jan '19

All - On Monday a research group installed into the global BGP routing table a prefix with a attribute type of 0xFF, which is designated as experimental by BGP RFC's. FRR had a developmental escape that read this attribute incorrectly and caused the bgp peering session to flap. If you have compiled FRR with the `--enable-bgp-vnc` option and run BGP as a peer on the global routing table you are vulnerable to this issue. This issue has been fixed in FRR with this commit: https://github.com/FRRouting/frr/commit/943d595a018e69b550db08cccba1d0778a8… We have applied this fix to the stable/3.0(3.0.4), stable/4.0(4.0.1), stable/5.0(5.0.2) and stable/6.0(6.0.2) branches. New releases can be found here: https://github.com/FRRouting/frr/releases/tag/frr-3.0.4 https://github.com/FRRouting/frr/releases/tag/frr-4.0.1 https://github.com/FRRouting/frr/releases/tag/frr-5.0.2 https://github.com/FRRouting/frr/releases/tag/frr-6.0.2 Snap packaging and the FreeBSD ports have been updated as well. We recommend you update your installation of FRR immediately. At this point we are applying for a CVE and will announce that information when we have it. In the near future we plan to implement RFC-7606 to handle this situation better in BGP, if you have any questions please feel free to email me, or to open up discussions on the frog alias. thanks! donald

2 4

Slack Access Request
by Shawn Olson 21 Dec '18

21 Dec '18

Hi there, I'd like to request access to your Slack Channel. We're an ISP in the northwestern region of the US and are beginning to implement FRR into our network. Love it so far - and would like to be more involved. Slack Username is shawn(a)fencepencil.com Thanks! Shawn Olson | Network Engineer Direct: (208) 286-4759 | Cell: (208) 985-6523 24-hour Customer Support: (800) 454-7214 Our Fiber Network Just Got Bigger Syringa Networks has completed the purchase of former Level 3 Metro Network Assets in the Treasure V<http://www.syringanetworks.net/>alley Syringa Networks | SyringaNetworks.net<http://www.syringanetworks.net/> _________________________ Privilege and Confidentiality Notice The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.

1 0

FRRouting @ FOSDEM 2019
by Ray Kinsella 13 Nov '18

13 Nov '18

Hi folks, I am reaching out my friends working on open source across the spectrum of Open Source SDN/NFV related projects. I am chair of the Software Defined Networking room at FOSDEM 2019. FOSDEM is the authentic, free and Open Source conference for Europe, and typically attracts a huge audience of Engineers from throughout Europe. It takes place each year in February in Brussels. If you know engineers working on Networking open source (FRRouting or anything else networking related) in Europe, this is a great opportunity for them to promote their work. The CFP is open until November 25th, would love to see an abstract from you. Thanks, Ray Kinsella FD.io TSC Member -------------------------------------------------------------------- We are pleased to announce the Call for Participation for the FOSDEM 2019 Software Defined Networking devroom! We are now inviting proposals for talks about Open Source Software on the topic of Software Defined Networking. This is an exciting and growing field, and FOSDEM gives an opportunity to reach a unique audience of very knowledgeable and highly technical, free and open source software activists. **Topics:** This year the DevRoom topics will include the following Software Defined Networking fields. - Infrastructure: virtual switches & routers, routing daemons, firewall, security, etc. - Virtual Network Functions: open source network functions, user-space networking stacks, kernel-space networking innovations. - Tooling: Networking SDK's, libraries, frameworks, debuggers, counters & statistics, domain specific languages & extensions, etc. - Validation: Testing tools & frameworks, traffic generators etc - Orchestration: NFV management, ML2 plugins, CNI plugins, SDN Controllers, etc. This year, the DevRoom will focus on low-level networking and high performance packet processing, network automation of containers, virtual machines and private cloud, and the management of networking applications to maintain very high availability and performance independent of whatever the world can throw at their infrastructure (datacenter outages, fires, broken servers, you name it). The deadline for submissions is November 25th, 2018. FOSDEM will be held on the weekend of February 2-3, 2019 and the Software Defined Networking DevRoom will take place on Saturday, February 2, 2019. See http://mdr78.github.io/fosdem/2018/10/15/fosdem-2019-cfp.html for more information, including how to submit a proposal. As you know FOSDEM has zero marketing budget, we would be grateful if you could help spread the word, by forwarding this email to interested people and mailing lists. - The FOSDEM 2019 Software Defined Networking Devroom Team

1 0

6.0 release
by Donald Sharp 18 Oct '18

18 Oct '18

All - We have released 6.0 of FRROUTING: Changes of 6.0 over 5.0: Staticd: New daemon responsible for management of static routes ISISd: Implement dst-src routing as per draft-ietf-isis-ipv6-dst-src-routing BFDd: new daemon for BFD (Bidrectional Forwarding Detection). Responsible for notifying link changes to make routing protocols converge faster. Ubuntu 12.04 is no longer supported (FRR 5.x is last supported version for it) various bug fixes The release images can be found here, with additional documentation: https://github.com/FRRouting/frr/releases I'd like to thank everyone involved in the effort over the last 4 months in getting this released. thanks! donald

1 0

Announcing FRRouting 6.0
by Martin Winter 11 Oct '18

11 Oct '18

FRRouting Version 6.0 is released. This is a major new version with some new daemons: - Staticd: New daemon responsible for management of static routes - ISISd: Implement dst-src routing as per draft-ietf-isis-ipv6-dst-src-routing - BFDd: new daemon for BFD (Bidrectional Forwarding Detection). Responsible for notifying link changes to make routing protocols converge faster. Major changes are the new Static Daemon and the BFD daemon. The Staticd from now on controls the static routes and is (most likely) required in all setups in addition to zebra (Zebra does no longer maintain the static routes). Please be aware that staticd has it’s own configuration file if you are using per-daemon configs (instead of the integrated config). If this file is not there (i.e. transition), then the static routes will be read from the zebra config file instead, but new saves will write a new static file and remove them from zebra. Please be aware of this in case of a downgrade from 6.0 to a pre-6.0 zebra with per-daemon config Pre-Built Packages are available on Github: https://github.com/FRRouting/frr/releases/tag/frr-6.0 Additional packages and package sources are available on the CI system at https://ci1.netdef.org/browse/FRR-FRRREL6-6/artifact Source is in the in the Git https://github.com/FRRouting/frr/tree/stable/6.0 Git branch “stable/6.0”, v6.0 is tagged with label “frr-6.0” Snap packages are in the Ubuntu snap store: https://snapcraft.io/frr Thanks to everyone who has contributed to FRR. - Martin Winter

1 0

Announcing FRRouting 5.0.1
by Martin Winter 06 Jul '18

06 Jul '18

FRRouting v 5.0.1 is released. This is mainly a bug fix release over 5.0, but has a few small enhancements as well Changes since 5.0: - Support Automake 1.16.1 - BGPd: Support for flowspec ICMP, DSCP, packet length, fragment and tcp flags - BGPd: fix rpki validation for ipv6 - VRF: Workaround for kernel bug on Linux 4.14 and newer - Zebra: Fix interface based routes from zebra not marked up - Zebra: Fix large zebra memory usage when redistribute between protocols - Zebra: Allow route-maps to match on source instance - BGPd: Backport peer-attr overrides, peer-level enforce-first-as and filtered-routes fix - BGPd: fix for crash during display of filtered-routes - BGPd: Actually display labeled unicast routes received - Label Manager: Fix to work correctly behind a label manager proxy - Debian Package: Fix build dependency for install-info Pre-Built Packages are available on Github: https://github.com/FRRouting/frr/releases/tag/frr-5.0.1 Additional packages and package sources are available on the CI system at https://ci1.netdef.org/browse/FRR-FR5BUILD-5/artifact Source is in the in the Git https://github.com/FRRouting/frr/tree/stable/5.0 Git branch “stable/5.0”, v5.0.1 is tagged with label “frr-5.0.1” Thanks to everyone who has contributed to FRR. - Martin Winter

1 0

Announcing PBR for FRR
by Donald Sharp 11 Apr '18

11 Apr '18

All - I'd like to announce the availability of a new daemon for FRR on the master branch. PBR( Policy Based Routing ) allows operators to setup policy maps that allow special control forwarding. To configure PBR, see `doc/user/pbr.rst`. Here is a quick example of how to configure: nexthop-group EVA nexthop 4.3.2.1 swp5 nexthop 6.4.3.2 ! pbr-map DONNA seq 10 match src-ip 192.168.210.0/24 match dst-ip 192.168.140.0/24 set nexthop-group EVA ! int swp54 pbr-policy DONNA ! This configuration says, on the incoming interface swp54 if the src matches 192.168.210.0/24 and the dest matches 192.168.140.0/24, use nexthop-group EVA for forwarding the packet. I'd like to thank Vivek, Don, Quentin, Philippe and Russ for their hard work on getting this code into FRR. thanks! donald

1 0

FRR 4.0 Released
by Quentin Young 24 Mar '18

24 Mar '18

Greetings operators and interested parties, The FRRouting contributors are proud to announce that the latest release of FRR is available for download. The team has spent several months integrating code and developing enhancements towards making FRR the best open routing suite available. The project thanks all contributors to this latest release, big and small! You can download it from our release page here: https://github.com/FRRouting/frr/releases/tag/frr-4.0 Documentation is located on the project website: https://frrouting.org/user-guide/ We have also begun to flesh out documentation for contributors and those interested in contributing: https://frrouting.org/dev-guide/ Feedback and documentation improvements are always welcome. Change Summary ============== General ------- * Implemented tab completion for interface names, prefix-lists, route-maps and BGP peer-names New protocols ------------- Added: * RFC 6126 -- Added BABEL protocol daemon * RFC 7868 -- Added EIGRP protocol daemon (experimental) BGP --- Added: * RFC 6810 -- RPKI integration * RFC 3107 -- v4 labeled unicast with partial implementation of draft-ietf-idr-bgp-prefix-sid * RFC 6514 -- Encodings and Procedures for Multicast in MPLS/BGP IP VPN's * RFC 7432 -- MPLS-Based Ethernet VPN (EVPN) * draft-ietf-bess-evpn-overlay * draft-ietf-bess-evpn-inter-subnet-forwarding * draft-ietf-bess-evpn-prefix-advertisement * draft-ietf-idr-tunnel-encaps * draft-ietf-bess-evpn-proxy-arp-nd ISIS ---- Added: * RFC 5120 -- ISIS-MT PIM --- Added: * VRF support OSPFv2 ------ Added: * VRF support * draft-ietf-ospf-segment-routing-extensions-24 (experimental) ZEBRA ----- * Cross-VRF static route leaking Bugfixes ======== * Too many to count.

1 0