XORP 1.0 Released
Mark Handley writes "XORP is the eXtensible Open Router
Platform - an open-source router software stack for FreeBSD and Linux.
It's designed from scratch to be extensible, so you can write your own
router applications that play nicely with the existing routing
protocols. We just released XORP 1.0! There's also a Live CD if you want to try
it out without reinstalling your machine. More details in this CNET article."
But this is good for colleges and other places where the concentration of "guys who can stop by and fix the router" is high. Also not to mention the tinfoil factor of a readonly-livecd router (but does it have remote logging).
Quidquid latine dictum sit, altum videtur
Ironic that there is no mention of Quagga or Zebra (that I can see) in either the XORP website, or the CNET article.
Zebra has been around for a long time now, and is pretty good. Due to the slow release cycle, Quagga forked the codebase, and so there are updated releases. Unfortunately neither project has seen fit to hit the magic 1.0 release.
- Ivan
The code/API does not seem to be designed to close to the ucLinux style of coding. While it's a commendable idea to reuse lowend hardware, it's a little heavy on the resources for a "real" device-based router project. Do the XORP web admins know when the code has been downloaded by half the Taiwanese broadband router companies yet? :P
"We know what happens to people who stay in the middle of the road. They get run over." - Aneurin Bevan
The cost of traditional routers has been a problem for commercial and non commercial organisations with tight budgets. Even in larger organisations with considerable routing investment there can be a real lack of routers for spares and training.
Add to this the fact that some old but worthy routers may not run the latest IOS and hence may have some unpatched vulnerability, which will not be addressed by the manufacturer, who understandably wants you to buy their latest kit.
As the CNET article points out the perceived disadvantage of this open source router software is the performance of the physical platform.
Perhaps it is the hardware implimentation that made people unsure of the Open Router project?
Perhaps a respectable router can be built more easily and for less outlay now than 5 years ago?
My hyperlinks aren't worth the paper they're printed on.
How am I supposed to know if it's any good if there are no screenshots?
will this project do nat forwarding and will it be able to prioritise some things (like ftp). this is one thing which I have found hard to do w/ iptables
Gated got a mention in the CNET article. It was actually a very good alternative to the commercial vendor hardware - argueably many ISPs (that are around today, eg Demon Internet in the UK) would never have been able to start up if it were not for the existance of Gated.
:(
Unfortunately this was an example of a kinda BSD-style licence causing problems. The Gated community (which cost a couple of thousand pounds per year to join, providing access to all code/updates) added a great deal of functionality to the code, and benefited from this.
The whole code was subsequently taken and "owned" by NextHop, meaning most/all of these code benefits were lost. Take a look at the gated.org website to see what happened
- Ivan
depends on what you consider low-end these days.
or what these people consider low-end
low-end might be a 433 mhz intel (like my computer) to them, they might have a p4 or the latest 64 bit AMD. so it might be fine on some machines, but I think yours and my definition of lowend is like a 66 mhz 486 with 16 mb of ram or less. or an ARM cpu or some embedded system.
of course there are the mini-itx systems that would make great mini-routers.
There's also Quagga, a fork of the GNU Zebra (thanks Kunihiro), which is further along, more mature, in much wider use than XORP (I've not heard of anyone actually using XORP in production, while GNU Zebra and Quagga most definitely are) and, most importantly, not written in C++ ;).
NB: I'm biased.
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
This is plenty fast enough for most edge routers, but clearly not going to compete with a Cisco CRS-1 or Juniper core router.
But most of the software in a router is control-plane (routing protocols and the like) and this is what XORP has focussed on to-date. As more people get involved with the project, we'll be able to do more things.
A decade ago no-one thought we'd be running Linux on a supercomputer. But we are. If we can get to the point where XORP is stable enough and fully featured enough for carrier-grade routers, who knows what hardware people will run it on in a few years time.
We are however very committed to keeping XORP as an open-source platform. No matter who uses it commercially, in the long run the only way to open up the router software market is for many boxes from many vendors to run a common open base software platform. With luck and with a lot of help, maybe that can be XORP.
- Mark Handley, XORP Project
Seeing as how they were funded by intel and all, it's probably expected that XORP will be fairly popular. I do think that running older hardware as a router is a good idea - I have a pentium P-54C 150MHz that i use as a router (running Freesco) when my main (Windows...i know....it's humiiliating) computer with ICS goes down. I have never worked with a proper hardware router (just a teenager), but a box running off of a floppy disk/cd/small hard drive is very good as a router, and is very configurable.
Why cant linux do this? Is this not feasible on modern hardware? I find it amusing that I cant simply (for example) use multiple wifi-links in a dynamic way. And no, neither (T)EQL nor ECMP works, ECMP isnt per-packet and EQL isnt dynamic in any way.
Ive heard of no software that can do this, actually. I know it must exist though?
XORP looks like you're trying to hard to be eXXXtreme! or something. EORP would at least sound like a rider of Rohan. Nerdy either way, of course.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Wikipedia begs to differ: XML (Extensible Markup Language)
Jean-Baptiste.. Emanuel... XORP!
www.xorp.org is in California, www2.xorp.org is in London. Both are 6-year old dual 450MHz Xeon machines with 768MBytes of RAM and SCSI disks, running FreeBSD and Apache 1.3.x. Both machines have 100Mb/s access to the Internet.
In 5 hours:
www.xorp.org: transfered ~30 GBytes peaked at around 175 simultaneous httpd processes 15 min load average peaked at 0.7. www2.xorp.org: transfered ~20 GBytes peaked at around 75 simultaneous httpd processes 15 min load average peaked at 0.4. Aggregate bandwidth was ~25Mbit/sec average. I won't know the peak bandwidth without some more analysis, but it's obviously quite a bit more than 25Mb/s. I didn't notice any obvious slowdown on either machine.I've no idea how typical this is, but I'm always curious about how easily sites seem to die due to slashdotting.
- Mark
If it was a BSD license it couldn't have been taken over. A BSD license can get a commercial fork, but the original code remains freely redistributable.
But that can't be right.
Shop as usual. And avoid panic buying.