Open-Source Router to Take on Cisco?
ickypick writes to tell us that CNN is running an article about the emergence of an OpenSource Router product, currently in Beta, that targets mid-size enterprise customers for about one-fifth the cost of current enterprise networking giants' hardware. From the article: "The machine runs on two Intel chips, but far more noteworthy is its software, known as XORP, or extensible open router platform. The versatile open-source application can direct data traffic for a giant corporation as easily as it can manage a home Wi-Fi network." The current release is available for download from Vyatta's web site."
Eddie Kohler, whose PhD thesis at MIT was the Click modular router (which from what I understand turned into the "engine" behind XORP), is one of the principal designers and developers of XORP. They published a paper at NSDI last year, which you can read here (Warning: PDF). It states very clearly what the goal of XORP is, and how well it performs. Quite interesting.
Not true. CARP + PFSYNC with OpenBSD and now even FreeBSD work quite nicely. You can do not only hot failover, but also load balancing.
Sometimes I feel like a nut... Ok so it's most of the time
OpenBSD ships with its own RIP, BGP and OSPF daemons. Its BGP daemon is BY FAR better than xorp and quagga, and its BSD licensed of course. OpenBSD is already a fantastic software router, maybe you should try using it instead of ignorantly telling us what it "could be"?
Switches and routing are different things, you can't really compare the two. And again, in their router module, if you implement any sort of ACL, are you still avoiding process-switching?
This used to be the case waaaayyyy long time ago (ok we're talking years not decades) but starting in Cisco's Cat5500 series they've started pushing the FIB (Forwarding Information Base) into hardware as much as possible... Update an ACL and the assocated FIB gets updated. It started off with the first packet of a flow gets processed switch (i.e. routed) and then the rest of the flow after that gets switched after that, now with Cat6500s with a current supervisor card and fabric enabled host cards it's not even that. ACLs (now VACLs) modify the FIBs directly and everything is directly switched, TTLs decremented as they pass through, counters incremented etc (aren't ASICs nice)... allowing the processor lazely handle the hum-drum work of responding to SNMP requests that dump information tables that would chock a small horse.
-- Ed Bugg --You have freedom of choice, but not of consequences.--