Saying that IS-IS in FRR is broken is incorrect, that it is in many ways weird - no offense to folks who coded it :) (especially if you have worked with commercial code bases), that it doesn’t scale/naive, missing features - for sure. FRR runs today some of the biggest DCs in the world and is reasonably stable within the feature set used (RFC7938), there’s interest in further IS-IS development - you could see some minor bug fixes/features coming from a particular company, if you are interested - join them and work together. FRR is an Open Source project, whining about missing features is not helpful, coding (or at least testing) and contributing is. Cheers, Jeff
On May 8, 2023, at 9:51 AM, Mark Tinka <mark@tinka.africa> wrote:
On 5/8/23 18:45, Mark Tinka wrote:
Broken when talking to Cisco IOS XE. Catalogued here:
https://lists.frrouting.org/pipermail/frog/2023-March/001265.html
I have no doubt FRR can talk IS-IS to other instances of FRR, but that is not a realistic scenario in a large scale network with multiple vendors.
And do add, IS-IS in Quagga has been broken from the get. There is no work happening there to develop it. All hopes for a working IS-IS in non-commercial vendor code is happening in FRR.
I have not considered IS-IS in VyOS, as the my use-case is for Anycast running on FreeBSD.
Mark.