Who we are
Our History
OpenSourceRouting (OSR) started in 2011 by an initiative of the Internet Systems Consortium (ISC, www.isc.org) and Google. Recognizing the need to drive innovation in the networking space and the challenges of the volunteer based Quagga community. The idea of OpenSourceRouting is to help develop a robust and tested alternative network stack and re-ignite the open source community behind Quagga.
In early 2014, ISC transferred the OpenSourceRouting project to the Network Device Education Foundation (NetDEF, www.netdef.org), a non-profit corporation based in the Silicon Valley.
What we do
Our Mission
OpenSourceRouting supports Quagga, an Open Source Routing Stack, implementing OSPF, ISIS, BGP, RIP, RIPng, and other protocols. OSR does not own Quagga. OSR drives public awareness and sponsors the main Quagga maintainer and provides engineering resources working mainly on bug fixing, testing and development.
OpenSourceRouting focuses on supporting the community in releasing a mainstream, and stable routing code base enabling networking innovation. Focusing on Quagga, the most widely deployed routing code base, OSR will partner with the existing developer community, including independent code committers, service providers, and academic institutions, in establishing an environment (“platform”) to deliver a high quality code base for Quagga.
Why we do this
Our Motivation
The network equipment space is driven by a few large corporations which care less about innovation and more about market share. The cost and complexity for new challengers to build their own network operating system from scratch continues to rise. OSR fosters innovation by providing a stable base to build on.
Our goal is to support Quagga and it's community. We like to see Quagga as a true alternative and production quality open source routing software. We believe in the benefits if an open source alternative for
- Educational Sector: to learn and test new ideas
- Large Corporation: to add their own "special" sauce (no more vendors who deny features!)
- Equipment Vendors: Lower the bar to enter the routing market and speed up innovations
- End Users: lower cost and increase available choices
Download the Flyers
Dear Sir/ Madam,
there are a set of RFCs we are demanding to get together, and according to the http://www.nongnu.org/quagga/docs/quagga.html#Supported-RFCs site, there is the list of RFCs Quagga suite supports. On the other hand, when I checked the RFC test results, I encountered the RFC 5340 (ospfv3) and this RFC is not included on the list that I just mentioned.
We would appreciate if you could provide us with the full list of RFCs supported by Quagga suite.
Is there a way to include other protocols on top of Quagga?
If we decide to use Quagga on our product, do you provide a workshop/ seminar?
We would be donating to the community, or another type of appropriate payment for the services we deliver and for using Quagga.
Thank you for your cooperation.
Regards,
Ebru KULOGLU
Systems Engineer
Aselsan, Turkiye
Wow.. that’s an old list of RFCs in the Doc section of the official Quagga pages. And obviously outdated.
I’ll see if someone can get this updated sometime. But it’s actually a moving target as new RFCs (and Drafts)
are constantly getting added.
If you (or anyone else) is interested in using Quagga or wants/needs training/code or anything else, then feel
free to contact us at info@opensourcerouting.org – We are always happy to discuss and help (ie we can test or
write code if needed or provide training) or just point you to the right location.
New members are always welcome in the Quagga Community