Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×

Open Source Router on Par With Cisco, Users Say 202

Posted by timothy from the pay-less-per-tube dept.
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.
This discussion has been archived. No new comments can be posted.

Open Source Router on Par With Cisco, Users Say More

Open Source Router on Par With Cisco, Users Say

Comments Filter:

  • Difference between hardware and software.... (Score:4, Insightful)

    by gweihir ( 88907 ) on Monday September 25, 2006 @02:13PM (#16188197)
    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.

    • Re:Difference between hardware and software.... (Score:5, Informative)

      by Shaman ( 1148 ) <shaman@@@kos...net> on Monday September 25, 2006 @02:21PM (#16188337) Homepage
      Bleah. This is tripe. Most Cisco routers have cheap, slow Intel processors in them.

      Until you get up into the gigabit speeds, regular PC hardware is just as good or better. The only thing you have to watch for in the multi-hundred-megabit routing loads is that you don't have a lot of access control lists - which is also an issue you will run into with any router you might choose. Spending some time sizing the buffers and other kernel parameters is also important, because a stock Linux kernel is not set up to be a network core router.

      I've got over 2,000 L2TP connections going into a single 2.4Ghz Intel box running Linux. Performance is significantly better than the Cisco 7204 that it replaced, and it's a lot cheaper and more flexible to support.

      Now, in the multi-gigabit routing tasks, do yourself a favour and get a L7 switch with custom ASICs. Extreme, Foundry and others will be happy to sell you one. Cisco's stuff is crap, right up until you get their million dollar badasses which they bought from another party (go figure).
      • FYI, I had a 7204 VXR and the Linux solution easily outperforms it.

        Still have it, I never throw anything away...

        cisco 7204VXR (NPE400) processor (revision A) with 114688K/16384K bytes of memory.
        Processor board ID 21280102
        R7000 CPU at 350Mhz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 Cache
        4 slot VXR midplane, Version 2.1
        Last reset from power-on
        Bridging software.
        X.25 software, Version 3.0.0.

        PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
        Current configuration on bus mb0_mb1
        • I was under the impression that the VXR equipped with the appropriate line cards would wipe the floor with the PC. Does this linux solution incorporate any kind of ASIC? Any special cards? What kinds of linecards on the VXR?

          Cheers,
          Athanasios

      • Re: (Score:2)

        by Cally ( 10873 )
        You've heard of CEF, right?

        • Re:Difference between hardware and software.... (Score:4, Informative)

          by Shaman ( 1148 ) <shaman@@@kos...net> on Monday September 25, 2006 @02:37PM (#16188573) Homepage
          Certainly have heard of CEF. And have witnessed first-hand how bad it usually works in a big Internet environment.

          Let's see...

          --

          IP CEF with switching (Table Version 271518), flags=0x0
              1030 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 3
              1033 leaves, 27 nodes, 152040 bytes, 269271 inserts, 268238 invalidations
              0 load sharing elements, 0 bytes, 0 references
              universal per-destination load sharing algorithm, id 26B36E8A
              2(0) CEF resets, 1425 revisions of existing leaves
              Resolution Timer: Exponential (currently 1s, peak 1s)
              2250 in-place/0 aborted modifications
              refcounts: 9206 leaf, 7168 node

          Adjacency Table has 888 adjacencies
              2 incomplete adjacencies

          --

          It does speed things greatly. Load on the 2.4Ghz Linux box that replaced it is 0.07 right now, with 1800 L2TP connections.

      • Re: (Score:2)

        by gweihir ( 88907 )
        Sorry, I just meant that for lower speeds, buying Cisco is defeinitely a waste of money.

        For high speeds get a hardware router and not necessarily from Cisco. In fact I don't like Cico for several reasons, which I will not go into here.

      • Re: (Score:2)

        by jgs ( 245596 )
        their million dollar badasses which they bought from another party

        Huh? CRS-1 [cisco.com] was done in-house.

      • Re: (Score:3, Interesting)

        by saridder ( 103936 )
        What part of Cisco's switch is crap? And which switch? Quantify that statement with some solid facts please.

        Cisco routers don't have any Intel processors in them. Some of their network modules that run LINUX do, but their not the router. Open one up and look. In fact they never have and never were x86-based. They were Sun boxes way back when created in Stanford's labs, but that was before Bush Sr. was president. Regular PC's may or may not be able to forward packets as well as a Cisco router, I'm sure
        • I'm currently using an intel box (2.4ghz) running linux (2.6.17). It has 5 gigabit interfaces with hundreds of vlans spread among them. I'm doing indivudual IP address shaping (thousands of clients), traffic control (what vlan can talk to what vlan/interface), MAC address checking - forwarding - NAT. The load on this machine sits between 0.01 and 0.07.

          Everything is home rolled. I learned how to do everything from the LARTC (Linux Advanced Routing and Traffic Control) mailing list archives.

          The thing I lik

    • Re:Difference between hardware and software.... (Score:4, Informative)

      by element-o.p. ( 939033 ) on Monday September 25, 2006 @03:37PM (#16189663) Homepage
      Ummm....no. In anything more complicated than what a switch can do, you are using software to process packets.

      Yes, Cisco (and others) have routers that use ASICs to handle immediate in/out "routing" in hardware, but as soon as you start putting any kind of ACL, any kind of port/IP translation, or anything else that requires any intelligence on the router, you bring in software, and all of the processing overhead that goes with it.

      So....if you are going to do anything *useful* with a router would you rather have a 50-200MHz Cisco box running a bloated IOS (do you *really* use X.25, for example???), or a server-class x86 motherboard running a 1GHz processor with a kernel optimized for routing and software optimized for the protocols you actually use?

      We use http://www.imagestream.com/ [imagestream.com]ImageStream Linux-based routers where I work, and they absolutely run circles around the 2600, 3000, and as5000 -series routers that we have. Their support is absolutely phenomenal. When we have a problem with an ImageStream router, we frequently talk with their programmer, and he works with us until we have a patch installed on the box that fixes the problem. If there's a software bug in your Cisco router, it's "yeah, that will be fixed in the next IOS release"...which unless you paid out the <bodily orifice of your choice> for SmartNet you have to *buy*, even though their product was broken when you bought it.

      You can use overpriced Cisco iron if you want; I'll stick with the Linux-based routers, thanks.
      • If there's a software bug in your Cisco router, it's "yeah, that will be fixed in the next IOS release"...

        They actually admitted to a bug? Hell, they must love you! When I was with UUNET, we used to have to escalate like mad to get them to admit a problem. Of course, once we had Junipers, Cisco started being much more helpful.

      • Re: (Score:3, Informative)

        by netik ( 141046 )
        Wrong.

        Foundry ServerIrons handles ACLs in hardware. So do Cisco Catalysts. If you turn on logging, they switch back to software ACLs, but with logging turned off, ACLs ar ein hardware.

    • Hate to spoil your rosy view of cisco - but their
      "hardware router" is actually just running software.

      I think what you meant was
      "Cisco's proprietary custom software is better than
      the open source equivalent."

      Cisco's hardware isn't more powerful than a typical
      PC - just more specialised.

  • Link to Vyatta (Score:5, Informative)

    by QuantumRiff ( 120817 ) on Monday September 25, 2006 @02:13PM (#16188203)
    Perhaps a link to the actual product would be in order?
    Vyatta Open Flexible Router [vyatta.com]

  • Avoiding "License Transfer" Fees (Score:4, Insightful)

    by evansvillelinux ( 621123 ) on Monday September 25, 2006 @02:13PM (#16188205)
    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.)
    • Yeah, I guess you could say that never buying Cisco equipment in the first place is a way of avoiding their fees. But if you already have (or need) Ciscos, OFR won't help you.

    • Re: (Score:2)

      by Amouth ( 879122 )
      you only have to pay if you want updated firm ware.. or extra options..

      the IOS is more than the hardware... you can buy cisco routers dirt cheep if you don't want the IOS..

      another case where the software is what has the cost behind it

  • if it is only "Standard PC Hardware" (Score:4, Insightful)

    by MerlynEmrys67 ( 583469 ) on Monday September 25, 2006 @02:16PM (#16188237)
    It isn't comparable with Cisco.

    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

    • Re: (Score:2)

      by Cheeze ( 12756 )
      OC3 and greater are probably not in 98% of the companies right now. Most of these companies probably have a weak DSL line with a linksys device. As companies get larger, they move up to T1 and need new hardware, it's probably a shock to have to pay the Cisco tax. What's the price of a 7200VXR class of router these days? If you could provide the same service with an old PC and a few PCI cards at 1/10th the price, you just made a nice cut-rate market for yourself.
      • Strange - why would you expect companies to step down from decent DSL speeds to T1 rates. I assume small companies stay on DSL/Cable for the download rates (host their web server somewhere else - what do you need upload speeds for anyway), then move up to OC12/48 rates (or multiple OC3) when there are enough employees to justify the need for the upload rates these speeds provide - or the reliability of multi homing the network. Again this trade off happens somewhere north of 100 tech workers, or multiple

        • Re: (Score:3, Insightful)

          by aesiamun ( 862627 )
          Because even commercial Cable and DSL sales have very little to no QOS. Read your agreement with your local cable co at some point...

          You aren't guaranteed uptime as a business cable company anymore than you are guaranteed uptime as a residential customer.

          • Absolutely true. (Score:3, Insightful)

            by Shaman ( 1148 )
            If you're not paying at least $100s of dollars a month, you aren't getting any sort of guarantees.
            • Doesn't matter. Commercial Cable services offer no more guarantee for uptime or throughput than their residential offerings.

        • Why change from DSL? Reliability... (Score:5, Informative)

          by WoodstockJeff ( 568111 ) on Monday September 25, 2006 @03:13PM (#16189133) Homepage

          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..."

          • Re: (Score:2)

            by pe1chl ( 90186 )
            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.

            This is of course hogwash. Just like you bonded your T1s to get better reliability, you can do the same with DSL. You can even get DSL and Cable, or DSL from different ISPs.
            In real life your reliability will be better than the "guarantee" you get from your LL supplier (which usually does not give any compensation in case of problems anyway, so you still are responsible for

            • Re: (Score:3, Interesting)

              by WoodstockJeff ( 568111 )

              True, there is no way to guarantee uptime completely, because it all involves wires or radio or something else that can fail in ways that you're not going to be able to fix quickly. Our T1s aren't bonded for reliability, but for speed... a fractional fiber just wasn't available to that site, so multiple T1s is the only way to increase speed. We're hosting, not surfing, so uplink speed is our bottleneck.

              But bonded DSLs have the same problem that a single DSL has - no guarantee of service. Period. And you ca

              • Re: (Score:2)

                by pe1chl ( 90186 )
                You know what? When a 737 flies into your building, it will still fail.
                There is no point in being so paranoid, other than to justify burning money.

                BTW, your cable provider is terrible. We easily get 99.95% uptime on consumer-grade DSL lines, and when counting 07:00 to 23:59 only it is well above 99.99%.
                Over several sites, over several years. Of course they don't guarantee it, but we provide our own backups (multiple lines, dialup backup for emergencies)

    • Re: (Score:2, Interesting)

      by Shaman ( 1148 )
      Cisco has the worst-performing L7 switches on the market until you get into the really large-dollar stuff (which they bought from another company). Use Extreme, Foundry or Big Iron and be much happier.

      Cisco's routers are cheap, mostly Intel-based systems with PC-quality hardware and low performance for the dollar. If you are routing mostly Ethernet (which most do these days), you can build a multi-hundred-megabit Linux router very inexpensively and get more performance out of it than a 7x00 series Cisco r

    • Re:if it is only "Standard PC Hardware" (Score:4, Interesting)

      by Gadzinka ( 256729 ) <rrw@hell.pl> on Monday September 25, 2006 @02:35PM (#16188547) Journal

      If I had one dollar for every time I give this answer, I'd be frelling rich:

      99% of businesses use sub 10Mb connection to the Internet and yet they are told the Cisco is the only way to connect them professionally. Moreover, the sub-$10k Cisco gear is a crap when it comes to performace, on par with good PCIe PC running on multiple Gbit eth interfaces.

      That about sums it up.

      Robert

    • Re:if it is only "Standard PC Hardware" (Score:5, Informative)

      by Cally ( 10873 ) on Monday September 25, 2006 @02:37PM (#16188583) Homepage
      Gosh, someone who knows what they're talking about ;)

      If your internet link is DSL, you do not need a real router :)

      I should point out that this topic comes up every couple of years on NANOG, ummmmmm... here's a reasonable selection from the last decade [google.com]. These people have forgotten more about routing than most of us here will ever know. And until generic PCs come with multi-gig backplanes, it ain't happening anywhere except the low end. And at the low end, you're better off either leaving it to your ISP or using a few whitebox "desktop" switches/routers. They're cheap, cheerful, work, and you don't need to know the difference between "sh ip bgp run" and "sh bgp ip run"...

    • Most businesses simply dont have those demands...Yes, large businesses do, but that isnt of concern for the hundreds of thousands of small to medium sized businesses in the US.

  • I LOVE DD-WRT (Score:3, Interesting)

    by celardore ( 844933 ) on Monday September 25, 2006 @02:16PM (#16188247)
    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.

  • ASICs (Score:4, Insightful)

    by Rekolitus ( 899752 ) * on Monday September 25, 2006 @02:16PM (#16188251)

    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?

    • get ASICs and whatnot that do the job faster than software

      I agree with you in principal(sp?) but I have a question:

      As we upgrade some machines, I've got dual cpu (1.5ghz =/-) and 2+GB RAM being replaced by dual cores. Would server hardware be able to handle as much, if not more than the cisco asics (2800's mostly) I've got?

      I get a damn good router for free. And I've got a spare parts inventory + redundancy. What am I missing?
      • OK first of 2800 series routers realy dont have much in the asic department they realy are software routers with some asics avalible to speed up things like crypto. Realy a PC can deal with just about anything that a sub 7200 can handle. Latency might be a bit higher but that could be solved with some firmware as x86 procs are not happy dealing with gigabit speeds and min MTU sized packets due to the number of interupts generated, now I would not want to do that with a 2800 either.

        The problem with PC's is
  • Can we have that article again, this time in English, please?
  • Two unknown consultants decide that Cisco sucks?

    If we were to judge solutions based solely on the word of two-or-more IT consultants, we would have "enterprise solutions" with MS-ACCESS backends, with a "robust" monthly backup to .TXT files on floppy.

    Seriously, the holes in this article are big enough to park a datacenter full of Cisco hardware in.

  • * As long as we're not switching half the U.S. (Score:3, Insightful)

    by mpapet ( 761907 ) on Monday September 25, 2006 @02:27PM (#16188441) Homepage
    Summary: Works great, supposed problem sounds like it was a driver issue more than an application issue.

    Reads like a well-placed article-vertisement.

    The "as long as we're not switching half the US" comment are the one's I grow tired of. It's a well-wrapped insult.

    I'm not saying Linux is the best tool for routing half the nation, but the comment points out some things that do prevent more linux adoption.

    1. "free" is not as good as something I paid for
    2. Don't fsck with the status quo.

    I admin a company 100% cisco routers/firewalls and I know for a fact Linux can do what gets done.

    I'm not going to tell the boss to "just" switch or evangelize too much because of the social/economic implications of doing so may impact my future. I like my employer, they like me, so when we need another router, it's a cisco. I am personally disappointed by this, but I think it explains why innovation takes -so- long to come to the data center. (at least in the U.S.)

    Let's not forget that cisco can fire most of their software devs and use a linux-based router project if it ever got close to competing with some Cisco products. Does that qualify as innovation? I'd say no. It's not cheaper or better.

  • Advertorial (Score:2, Insightful)

    by HKcastaway ( 985110 )
    It is great that someone is out there tyring to put some preassure on Cisco however this company is not it. I think the average Linux installation with NAT is a bigger threat that this project.

    PC hardware is a joke, slow backplanes, limitation on how many interfaces you can plug in. On the techspecs the number of interfaces types they use is well very very limited. Then reliability of PCs a joke compared to a Cisco box.

    Where is this product used?
    - Is this a bloated replacement for the US$20 taiwan PPPoE rou

  • No huge suprise (Score:3, Insightful)

    by peterdaly ( 123554 ) * <{petedaly} {at} {ix.netcom.com}> on Monday September 25, 2006 @02:30PM (#16188485)
    In or around 1999 I had a 1000 device network routing through a 133Mhz PC running Linux. The 133Mhz system practically thought is was sittle idle as it shuffled packets between three 100 megabit networks.

    I'm not suprised at all that these Open Source solutions are on par with Cisco for many users. My only real concern would be support. At least back then (I have not dealt with them recently), Cisco had great support and would "own" network problem resolution in a way that made it worth paying their price.

    • Re:No huge suprise (Score:4, Insightful)

      by macdaddy ( 38372 ) on Monday September 25, 2006 @02:57PM (#16188873) Homepage Journal
      There is nothing like calling Cisco TAC at 04:00. You get an Aussie TAC engineer that knows 1) you're network is seriously fscked up or you wouldn't be calling him at 04:00, 2) you've already removed what little hair you have from your head and your scalp is bleeding. The nightshift engineer is highly experienced in working under said conditions and is more than capable or resolving the problem. I've been in that position twice in the last month. All I can say is I want to move to Austrailia, mate.

      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.

    • Re: (Score:2)

      by nuintari ( 47926 )
      So, you have a couple of subnets, all through one central router that has one default route, so your routing table has what? All of four entries? And you think this proves that a PC can beat a 'real' router?

      Sorry, that just doesn't need much power to work. Try adding in OSPF, and some redundant links into your internal network. Get a second ISP and become multihomed, run BGP and add all 194,000+ entires from the global routing table into the mix, watch that P133 slow to a crawl.

      Software routers handle every

      • Re: (Score:2)

        by Shaman ( 1148 )
        You only get that kind of performance out of a Cisco when you spend big bucks. Really, really big bucks. You figure a quad-processor Compaq with same-day service is going to be more expensive than a big Cisco router with tepid performance these days?

        • Re: (Score:3, Informative)

          by nuintari ( 47926 )
          AS the AC already mentioned to you, and as I already mentioned, cisco routers route 98%+ of their traffic directly between the line cards, so the CPU can handle important stuff, like handling the routing and express forwarding tables. You can get much better performance out of a cisco because of this architecture because even your quad proc pc based router still has to shove everything through the CPU, and will buckle under the load once you add more than a few line cards. Try plugging your quad proc server

  • in other news (Score:4, Insightful)

    by atarione ( 601740 ) on Monday September 25, 2006 @02:33PM (#16188529)
    a small truck can replace a semi truck.... if you are moving small amounts of items.
    • Hardware-based routers and PC-based routers are really solving much different problems. The hardware routers can handle large volumes of packet-shuffling in ASICs, without having to bother the CPU - on the other hand, if you want CPU and RAM, it's much much more cost-effective to buy a PC (even if you ignore the fact that Cisco gouges on price for standard commercial RAM.) PCI backplanes aren't made to handle all that much router traffic - they're overkill for connecting a DSL or cable modem connection, o

  • Support, Support, Support (Score:5, Interesting)

    by bstory ( 89087 ) on Monday September 25, 2006 @02:35PM (#16188545) Homepage
    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.

    • Re: (Score:2, Informative)

      by HKcastaway ( 985110 )

      You also forgot to mention the fact that the likelyhood of a hardware failure on a PC to a Cisco unit is like 20:1 (for most products).

      Cisco has a far fatter margins on the hardware than PC vendors and can provide a much higher quality product, can afford to underclock the machines for higher reliability etc.

      • So use pfsync and CARP [countersiege.com] on your OpenBSD-based routers running on commodity hardware and have more redundant ones. Have your router automatically email you when fail-over happens (and you're down to only two or three spares) and you can throw the broken one in the bin and replace it with a new one at your leisure, and still be cheaper than Cisco.

    • Re: (Score:3, Insightful)

      by LWATCDR ( 28044 )
      I tend to agree with you but...
      With the cost of commodity PCs these days you could probably have an entire second router on hot standby for the cost of a single year's support contract.
      If it is a T-1 then just move the cable over. If it is an Ethernet connection the fall over could be entirely automatic http://linux-ha.org/ [linux-ha.org]
      You will also have a trade off of in house time to test and configure vs just buying Cisco.
      Of course their are times where generic hardware will not cut it. However this does offer some i

    • Re: (Score:3, Insightful)

      by macdaddy ( 38372 )
      Well said. This easily says 80% of what needs to be said. Without support you have an OSS space heater at 02:00, assuming it will power up at all.
    • Sometimes Cisco support breaks down [slashdot.org], and their record on security provoked Bruce Schneier to say "Now it doesn't matter what they say -- we won't believe them. We know that the public-relations department handles their security vulnerabilities, and not the engineering department." [schneier.com] With an open-source router, you could in theory have competitive support companies, with all the benefits that competition provides.

      Until guaranteed-response support proves itself for open-source routers, most network admins with

    • Re: (Score:2)

      by snero3 ( 610114 )
      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.

      You do have a point there. But as this runs on x86 hardware whats to stop you from having a stack of spare gig network cards lying around? Hell you could have a whole redundant box for the cost of the cisco gear. We have cisco here but honestly it is _MUCH_ fas

    • Just because it's OSS doesn't mean you can't pay for on-site support, on-site hot backups, the works.

      Whether it's OSS or closed source is irrelevant in that regard.

      Except with OSS you are likely to have more flexibility and better value for money.

      "Support" is often a boogeyman pushed by salesdroids when they don't have anything better to offer, trying to scare a customer into getting locked in to their expensive, proprietary solution while ignoring the flexibility, including support, that OSS can offe

    • Re: (Score:2)

      by Alioth ( 221270 )
      It depends, really, on your network.

      For us, being able to use inexpensive commodity parts and being able to have a hot-swap that can be connected in less than 5 minutes strongly trumps a hugely expensive router and 4 hour fix commitment.

      This might not work for everyone. But for the typical office with maybe 100 people working in it, with a couple of internet connections, an OpenBSD system with pfsync+carp (i.e. a spare box and automatic fail-over) will trump a single Cisco router most times and save signifi

    • Re: (Score:2)

      by derF024 ( 36585 ) *
      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.

      I've never encountered a problem with a business critical system that could wait 4 hours that couldn't wait 24.

  • Huh, Samba file sharing? (Score:4, Insightful)

    by IpSo_ ( 21711 ) on Monday September 25, 2006 @02:35PM (#16188557) Homepage Journal
    "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.
  • Hate to break it to ya, but Linksys is owned by Cisco.
  • Since when do we listen to "users?"

  • You're buying the hardware (Score:4, Insightful)

    by thesandbender ( 911391 ) on Monday September 25, 2006 @03:11PM (#16189093)
    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*
    • Building a system that can compete on cost/mtbf

      In my Cisco experience, that is _highly_ platform, IOS and purpose dependent. On one hand, I've had several Cisco boxes at the "high" end ($XXX,XXX.XX), several at the low end ($xxxx.xx) and several in between that have stayed up for years. On the other hand, I've had other Ciscos in each of those same price points enter death spirals as often as daily.

      One 7206VXR I had to reboot every three days to stave off a spewing CEF memory leak. The ESR platform is a
    • Its simpler then that. Appliances, enterprise grade hardware or software. That's job security.

      Sure, you might save a few bucks and maybe, if you're good, come up with something better. But try explaining that to your non-technphile CEO when something (and something always does) goes wrong.

      If my gear fails and I did the best that I could (firmware upgrades, software updates, hardware lifecycle, etc) its no sweat off my back. We rush to repair our systems and someone wags their finger at Sun or Cisco or w
  • When using a PC as a router, what DSL modems do people use?
    I am trying to find some ADSL2+ modems to connect to our Cisco routers.
    (in the past we have used Cisco ADSL WIC, but it has become clear that a consumer-grade Alcatel modem outperforms those, and even worse: there is NO ADSL2+ WIC...)

    The modems have to support PPPoA and provide a transparent "bridge mode" where incoming traffic is delivered on the ethernet port with the Internet IP address as destination. This would be the same mode you would want

  • Hardware support lacking (Score:3, Interesting)

    by drwho ( 4190 ) on Monday September 25, 2006 @08:33PM (#16193789) Homepage Journal
    Too bad they only support Sangoma serial cards.
  • ... of an almost perverse little daydream that I had some time ago. I thought that it would be fun if someone were to made T1, T3, and other interfaces that connected via... USB. A USB connection has enough bandwidth (at least on paper) to run a T3 with ease, and you could pop 32 (or more) USB 2 ports in a machine very easily. And for the lesser-bandwidth interfaces, you could run them off of a USB hub.

    So, imagine a single machine with 30, 50, or 60 network interfaces coming out of it, al
  • I would NEVER take our main CCisco driven backbone down and replace it with Open Source. Again, support is the issue. If there's an issue with the router, Cisco probably definitely knows about it....even the obscure. Sometimes they don't, but they still help you anyway. Can support contracts be had for a Open Source router?? Will the support actualy help me or tell me something like L1nux R0x0rs, RTFM y0u n00b?

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Close