Slashdot Mirror
Open Source Router on Par With Cisco, Users Say
Jane Walker writes "On a mission to avoid paying top dollar for Cisco routers, two users say Vyatta's Open Flexible Router is a viable alternative to the proprietary norm. Find out about the pluses and minor hassles involved in deploying this alternative." This probably won't surprise the users of (much lower end) networking gear like the famously hackable Linksys WRT54G, which — like a number of internally similar routers — can be reconfigured with one of several open-source firmwares to do things impossible with the hardware as delivered.
It is not surprising that low-end software routers can offer most things a proper Cisco router can. However when you need hgher speeds, a software router can not cut it. It is then when hardware routers show their strenght. A 100Mbps line usually does not require a hardware router. A 10Gbps line does.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Perhaps a link to the actual product would be in order?
Vyatta Open Flexible Router
What are we going to do tonight Brain?
Isn't this a way to avoid paying for the licensed software on Cisco equipment when it's sold second hand? (Not trolling or anything, I think it's ridiculous for Cisco to demand payment for software that's already been paid for once.)
IMHO, IANAL, TINLA, etc...
But then again for SMB - you don't need 100 MBit routing - many of your internal clients are slamming into your sub 10 Mbit internet connection anyway (that is probably further BW limited by the cable/phone company). Now for true enterprise - you really do need switching/routing at the ASIC level - real switching fabrics (not a glorified PCI bus) in the hardware etc. to handle the multiple GBit links, multiple OC12/OC48 connections to the world, etc.
This is where Cisco shines and I don't see "software only solutions" coming anywhere close
I have mod points and I am not afraid to use them
I rent a housemate cable internet, which we had terrible problems with before. The problem is a bad cable causing a load of bad packets to 'clog' the router. It is the only cable long enough I have though, but the DD-WRT firmware worked a treat. It does allow some cool features, such as increasing the number of IP connections from 512 (the default) to 4,096 which is ideal for p2p. You can also boost wireless power from the 28mW default to 250mW+. Anyway, my problem with it clogging up was solved by setting up a cron job within the router so that it reboots at 5am each day. Not ideal, but the solution works until he gets off his ass and finaly buys a wireless card.
This seems to be an entirely software router that just runs on a standard x86 machine.
Isn't half the point of buying a dedicated-hardware router that you get ASICs and whatnot that do the job faster than software?
a small truck can replace a semi truck.... if you are moving small amounts of items.
actually I am happy to see you, however that is in fact a banana in my pocket.
Ok, I haven't looked at the performance numbers, but as a network administrator of a medium sized corporate network I could care less. Whether it be Cisco, Juniper, Nortel or 3Com the difference is in the support. When my wan interface or network interface dies at 2am I don't think anyone from the OSS community is going to have a parts depot within 4 hours to fix the problem. I also don't see 24x7 tech support phone numbers manned by volunteers anytime soon. Vendors don't make the money on the hardware, they make it on services and support. I love OSS, but Linux and OSS are not the magic pill for everything.
"The feature set was comparable to your standard Cisco router," Knox said. "They were offering translating, gateway capability, Samba file sharing, VLAN trunking to 11q ... it really looked like a corporate-level router," he said.
Since when do "corporate-level routers" offer samba file sharing? This seems like the LAST thing I would ever want to put on a router. The only thing I could possibly see Samba being useful for is downloading log/config files. But on a router that is kinda scary, SCP seems much more secure and just as useful.
Open source routing is definitely an option now though. Over 3 years ago the web hosting company I worked for swithced out their Cisco routers that couldn't handle the slighest DDoS attack for a couple AMD based Linux boxes that could easily handle wirespeed DDoS attacks with ease. Not to mention they were a fraction of the cost.
Open Source Time and Attendance, Job Costing a
I wish the SmartNet prices were a little more reasonable. They should cut the prices dramatically for the lower-end 8x5x4-day replacement support so that more people can afford it. This would be a solid recurring business for Cisco whereas only a small percentage of Cisco customers bother buying support nowadays.
I use Debian at home for a general purpose router and firewall and it is very flexible. There have been times when I've been tempted to deploy it as a small/medium business router in lieu of cisco but it's not just about the software, it's about the hardware as well. For a reliable system you need reliable parts... which are more expensive... preferable a cpu with a low thermal dissipation but still fast enough to handle the load, which is going to cost you money and either a RAID system or (ideally) a flash based storage system, which is going to cost money. You can build a system that will beat Cisco's cost/feature set easily. Building a system that can compete on cost/mtbf ... not so easy... and generally just not worth the effort.
The article referenced a "still servicable pc" ... which roughly translate into "a machine that we picked up from behind the receptionists desk and cleaned all the dust bunnies out of.... *shudders*
Strange - why would you expect companies to step down from decent DSL speeds to T1 rates.
When you need reliability, you have to give up on DSL/cable, because no DSL or cable provider is going to give you service guarantees. If a DSL/cable line doesn't provide it's advertised 2Mb/s download throughput, that's too bad; you might be able to negotiate your bill down. And if it goes down, it's going to be you reporting it to your ISP, not the other way around...
But a T1 circuit (generally) has both through throughput and uptime guarantees written into the contract. And automated monitoring of its performance, and fast notification that something's wrong, 24 hours a day. I've had DSL circuits be out for days; the longest a T1 circuit was down was 8 hours, and there were severe financial penalties proscribed for that event.
That's not to say a T1 circuit is perfect; we use a bonded pair of them to feed one site. One went down, due to an incident with a trencher. Verizon promptly fixed it... by moving the circuit to another pair that tested good in the cable. Guess which pair got used... If you guessed the pair that the second circuit lived on, you'd be right, and it went down. This went on for a day, alternating which circuit was up and down, until one of our people met the Verizon tech at the repair site. "You do know that there are TWO T1 circuits here, don't you?" "Oooops..."