Hi everyone, I've been working on OpenEIGRP, a complete rewrite of the existing FRR EIGRP implementation, and wanted to introduce it to the community. One of the main design goals is to deliver an enterprise-grade EIGRP implementation with a strong emphasis on portability and ease of adoption. The OpenEIGRP protocol stack is independent of the underlying routing platform, with separate integration layers for each environment. It's already been ported to Nokia, and I'll be starting work on BIRD/BSD soon. This approach allows us to maintain a single common protocol stack rather than separate implementations for each platform. Major features currently implemented include: * DUAL – Complete Diffusing Update Algorithm FSM, including successor and feasible-successor selection. * RTP – Reliable Transport Protocol with reliable multicast and unicast delivery. * IPv4 and IPv6 – Dual-stack routing support with classic IPv4 and named-mode configuration. * Route Redistribution – Internal/external routes and redistribution with other routing protocols through FRR. * Metrics and Load Balancing – Classic and wide metrics, configurable K-values, ECMP, and unequal-cost load balancing. * Route Summarization and Filtering – Route summarization, distribute lists, prefix lists, and route maps. * Neighbor Management – Dynamic discovery, adjacency maintenance, authentication, and neighbor recovery. * Multiple Instances – Full Named Mode config with multiple autonomous systems, named instances, and address families. * Management and Diagnostics – CLI configuration, operational show/debug commands, protocol statistics, and event logging. * Check out the feature matrix for a full list.. For FRR, OpenEIGRP is designed to be a drop-in source replacement for the existing alpha EIGRP implementation. It also includes a small set of FRR patches needed to support the integration. These patches are backward-compatible with the existing alpha EIGRP implementation currently in FRR. Ideally, I'd like to get them incorporated into the FRR codebase, so I don't have to keep maintaining and tracking them separately as FRR evolves. I'm still working through testing and validation, so I'm not suggesting OpenEIGRP is ready for upstream inclusion just yet. In the meantime, I'd like to invite anyone interested to take a look at the project, particularly the FRR integration, and provide feedback. To try it out, clone the repository and run: ./tools/frr.sh --patch ./tools/frr.sh --install Then configure and build FRR as usual, or deploy one of the pre-build docker images (though they will generally be missing fix's as I add them) GitHub: https://github.com/diivious/eigrp I'd also like to get a feel for whether the FRR community would be interested in accepting OpenEIGRP once testing is further along, and whether getting the supporting patches upstream ahead of time would make sense. Thanks, -d