Slashdot Mirror


OS Router Challenges Proprietary Networking

Jane Walker writes "Dave Roberts talks about Vyatta's open source router and how open source technology may soon alter the landscape of enterprise networking." From the article: "Initially, we believe that the x86 PC running Vyatta -- given the range of hardware that's available in the PC world -- can basically replace the midrange of the router market; to use Cisco terminology and model numbers, simply because it's convenient shorthand, basically from the 2800 series to the 7200 series. There's a whole host of equivalent products from Nortel and Alcatel -- but essentially in that range. I wouldn't describe it as Cisco model numbers so much as T1 branch office to gigabit LAN product categories."

238 comments

  1. Sigh.... by 222 · · Score: 4, Insightful

    I love open source and all, but can a project like this really offer the same number of WIC modules?

    I can plug damn near anything into a Cisco router....

    1. Re:Sigh.... by Svartalf · · Score: 5, Interesting

      All depends on what they provide in the way of PCI/PCI-X cards- or whatever the future buses might be...

      I'd say that odds are good you'd get about the same number of media interfaces and what you didn't
      have would very probably have a media adapter or bridge that's standalone to take care of the gaps.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    2. Re:Sigh.... by Nuclear+Elephant · · Score: 4, Funny

      I can plug damn near anything into a Cisco router....

      Open source routers and pr0n sounds like a dangerous combination for you then.

    3. Re:Sigh.... by ChaoticChowder · · Score: 4, Interesting

      This software would have to offer much more that just WIC modules to even have me consider using it. Cisco routers may have low clockspeeds on the core chip, but its the ASICs that give them value. Also, take the 6509 for instance, slap in a SUP720B and you now have a 720 GBps back plane. No PC could ever hope to do that. Also, configuring a Cisco router is pretty much the easiest thing ever. I haven't checked out the software yet, but it better be much easier. Maybe they should network with the Open Source chipset guys and design some ASICs and all the other niceties.

    4. Re:Sigh.... by Thundersnatch · · Score: 5, Interesting
      Also, configuring a Cisco router is pretty much the easiest thing ever.

      Trolling for a +1 funny mod, are we?

      I don't remember who said it, but this is my favorite quote about Cisco software: "Cisco makes easy things difficult, but difficult things possible."

    5. Re:Sigh.... by kindbud · · Score: 4, Funny

      I can plug damn near anything into a Cisco router....

      And if you disable autonegotiate and set speed and duplex at fixed values, you might even get link.

      --
      Edith Keeler Must Die
    6. Re:Sigh.... by Anonymous Coward · · Score: 0

      I know this will sound like a ME TOO! post, but being how true your staement is, I don;t know weather to laugh or shake my head in disgust.

      Because NWay for Cisco = NoWay, just about every network engineer I have ever worked with or talked too (including myself) never use, suggest, or even mention the term "auto negotiation". It is a sad state but it is almost a right of passage that we spread to the junior guys. Have a heart though. These young guys just don't get it! I don't care if it worked on every other piece of equipment you have ever used in your life including your at last NOC position and your previous tier 2/3 positions. Don't question it noob, this is expensive hard core routing and switching here son, only hard coding on my network!

    7. Re:Sigh.... by Anonymous Coward · · Score: 0, Flamebait

      "and you now have a 720 GBps back plane."

      Nice how you kinda make up your own bandwidth measurements... WTF is a "GBps"? Is that "GigaBytespersecond"? I *NEED* that... and, when I saw it, my "bullshit meter" pegged, for obvious reasons.

      Anyway, not being familiar with a Cisco 6509 with a "slapped in" SUP720B... I decided to look for myself to ascertain the truth of your statements (*GASP* - Yes, some of us actually USE this whole "IntarWeb Thingy" to learn things that we don't know, rather than rely on opinion and supposition).

      Here's what I learned:

      http://www.cisco.com/en/US/products/hw/modules/ps2 797/products_data_sheet0900aecd8017376e.html

      And, I discovered one relevant snippet:

      " Scalable and predictable system performance-These modules provide a selection of switch-fabric connections and throughput options:
      32-, 256-, and 720-Gbps bandwidth with a system throughput of: 15, 30, 210, and up to 400 Mpps."

      Which clearly states that there's no such thing as a "720GBps back plane". So, basically, you don't know the fundamental difference between bits and bytes.

      Now, if you're gonna say you made a "simple" mistake - don't. No offense, but, if you're ANYWHERE close to being Cisco certifed, and you're still making such mistakes... I'd be VERY nervous about hiring you for anything that resembles mission critical networking on any large scale: "GBps, Gbps - what's the diff?!?LOLOL!!11One"

      Oh, and the grammar mistakes don't go a long way towards building confidence, either :)

      Posting AC, 'cause I KNOW that all of the 900K+ UID moderators with mod points would blast me into oblivion for this post, despite the fact that it is correct.

      But, my opinion? You're fundamentally clueless, as borne out by your own statements.

    8. Re:Sigh.... by pedalman · · Score: 1
      And if you disable autonegotiate and set speed and duplex at fixed values, you might even get link.
      Providing your CAT5 cabling is terminated properly. When I started my current job, my boss was complaining about dropped packets and data loss. When I hard-set the NICs to 10Mbps, packets stopped dropping.

      My predecessor had run all the cabling from the lab computers to the switch in the closet herself. Unfortunately, each cable end she crimped had its own unique order. Not one of them was terminated to standard.

      --
      Friends don't let friends line-dance.
    9. Re:Sigh.... by SmurfButcher+Bob · · Score: 1

      Actually, I thought Cisco's business model is to sell hardware for the purpose of extorting a monthly $20,000 training fee. You know, like Novell did back in the late '80s.

      --

      help me i've cloned myself and can't remember which one I am

    10. Re:Sigh.... by osbjmg · · Score: 1

      agreed, the number of modules is astounding, seriously. The time it would take to find that kind of market to make all those little modules for a computer would be asinine. Besides, the future isn't in 7200 series routers, it's CRS, GSR, 6500(7600), etc. You would also be hard pressed to do better than cisco overnight. cisco has an army of programmers and a solid foundation around which endless features are added. I like the idea though!

    11. Re:Sigh.... by megaditto · · Score: 1

      GP: 720 GBps back plane. No PC could ever hope to do that.

      That there nailed it.

      P:Trolling for a +1 funny mod, are we?

      He is as much of a funny troll as you are a good Mod.

      --
      Obama likes poor people so much, he wants to make more of them.
    12. Re:Sigh.... by Jzor · · Score: 2, Funny

      ...but can a project like this really offer the same number of WIC modules?

      What do foodstamps have to do with networking?

    13. Re:Sigh.... by bdp · · Score: 1
      I love open source and all, but can a project like this really offer the same number of WIC modules?

      I'm not sure they really need to provide all the modules that Cisco does. The majority of people only use a small subset of all the modules Cisco provides, and as long as that subset can be brought to the PC platform, (if they don't already exist in some form), then there will be a large market for Vyatta's product.
    14. Re:Sigh.... by Mohan+S · · Score: 1

      Can. You can get PC boards with enough slots to do this. If you want to go further, you can get 1U network hardware that are std PC baords with multiple interfaces and 24 ethernet ports etc on which you can run this. Server boards have 2 ethernet interfaces on board and give you 3 PCI slots. This will be able to meet the need of a good lot of customers.

    15. Re:Sigh.... by bdp · · Score: 1
      ...and you now have a 720 GBps back plane. No PC could ever hope to do that.

      That's not quite true. There's no reason I can think of why you couldn't make a backplane for a PC that handles all the network traffic locally, without touching the PCI bus (or whatever bus). In fact, high speed interconnects used on clusters do that sort of thing already, and I suspect any high speed backplane for any platform would need to do the same. I'm not intimately familiar with ASICs, but if they add this type of functionality regardless of the clockspeed on the core chip, they probably handle all the traffic locally too.

      A backplane like that may not exist for a PC currently, but if their PC router is successful enough to get companies using it, somebody will create one. Engineering a high speed backplane for arbitrary hardware is a problem that has already been solved, all that's needed now is a market with enough demand to make it worthwhile to build.

    16. Re:Sigh.... by gujo-odori · · Score: 1

      You sound like a person who read a funny quote (and it's not even all that funny) but never configured a Cisco. I love IOS. You don't often hear some describe a CLI only OS as being intuitive, but IOS is extremely intuitive. It sets a standard that no *nix shell comes close to in that regard.

      I don't really have much interest in putting Linux on my Linksys, but I'd love to be able to install IOS on it :)

    17. Re:Sigh.... by monsted · · Score: 2, Informative

      > That's not quite true. There's no reason I can think of why you couldn't make a backplane for a PC that handles all the network traffic locally, without touching the PCI bus (or whatever bus). In fact, high speed interconnects used on clusters do that sort of thing already, and I suspect any high speed backplane for any platform would need to do the same.

      I think you're missing the point. The backplane of the Cat6500 is pretty much what the PCI bus does for a PC. A 32bit/33mhz PCI bus gives you just about 1 Gbps while the Cat6500 backplane provides three buses of 256, 32 and 4 Gbps (not 720 GBps as the GP suggested - the "Sup720" refers to the 720 Mpps switching capacity). Switching to PCIE gives you 2.5 Gbps per lane, but how many motherboards provide the 100 PCIE lanes needed to compete?

      > I'm not intimately familiar with ASICs, but if they add this type of functionality regardless of the clockspeed on the core chip, they probably handle all the traffic locally too.

      ASICs offload the hard work from the CPU of the Cisco systems. Basically any kind of compute-intensive bulk work, switching (yes, it switches layer 3 too), filtering (access-lists) and so on, is handled by dedicated ASICs and require little or no CPU intervention. This enables the catalyst to handle high amounts of data with a quite small CPU. Things that do end up on the CPU is management work, route computation (BGP changes, for example) and logging. To handle 720 million packets per second, you'd need quite a lot of CPU in your PC.

      > A backplane like that may not exist for a PC currently, but if their PC router is successful enough to get companies using it, somebody will create one. Engineering a high speed backplane for arbitrary hardware is a problem that has already been solved, all that's needed now is a market with enough demand to make it worthwhile to build.

      Well, large Juniper routers are run by a FreeBSD service processor, but i doubt you can run your open source router on it... :)

      One thing the GP doesn't mention is the availability of special service modules, which one again do their work mostly in hardware: firewalls, load balancing, intrusion detection, intrusion protection, voice gateways, etc. Also, it takes 4 port 10GigE and 48 port GigE blades, giving it up to 48 10GigE or 576 GigE ports in a 13 blade chassis (one slot goes to the supervisor), something you'd have a hard time stuffing into a PC :)

      With regard to ease of use, within 15 minutes of powering it on for the first time, most Cisco admins could have it up and running, switching and routing - IOS is a fantastic OS for most things.

      Either way, i doubt the catalyst 6500 is the intended target for an open source routing platform and i'm sure it'll do just fine competing with the 2800-sized routers.

      You may commence flaming the Cisco fanboy now.

    18. Re:Sigh.... by Anonymous Coward · · Score: 0

      I must admit, I was told this just the other day!

    19. Re:Sigh.... by RareButSeriousSideEf · · Score: 3, Funny

      I don't know what all the fuss is about Cisco routers. For my money, Black and Decker wins every time.

    20. Re:Sigh.... by Anonymous Coward · · Score: 0

      You must have never used Juniper's JUNOS if you love the IOS CLI.

    21. Re:Sigh.... by CoonAss56 · · Score: 1

      What was she? Colorblind? Gee, the easist thing in the world is to terminate cable-it's either A or B.

      --
      Won't Bow.....Don't Know How
    22. Re:Sigh.... by Thundersnatch · · Score: 2, Informative

      I have configured many Cisco routers, switches, and VPN concentrators. None had anything close to an intuitive interface, and even standard operations differ from model to model. There's as much backward-compatibility cruft and illogical organization in IOS as in Windows. Cisco documentation is often just plain wrong or so poorly written as to have ambiguous meaning.

      In fact I've never worked on another brand of router besides Cisco, but the CLIs and GUIs of other complex networking devices like Checkpoints & SonicWalls let me know that something more intiutive than IOS is definitely possible.

    23. Re:Sigh.... by hal9000(jr) · · Score: 2, Interesting

      That's interesting. I know alot of people, myself included, that like the IOS command line not becuase it is intuitive (I haven't met a CLI that is "intuitive"), but because it is pretty easy to navigate once you learn a few tricks. Alot of other networking gear have IOS-like interfaces in some cases replicating the IOS structure, but none are exact.

      Maybe the only other CLI that is easier to use is Junipers JunOS, but I haven't spent alot of time with it.

      Oh, and the docs have gotten much, much better from say 6 years ago.

    24. Re:Sigh.... by rekoil · · Score: 1

      First off, in order to get the 720Gbps speeds out of a 6500 series box, you need not only the Sup720B, but every line card in your box needs to have a DFC (Distributed Fabric Card) slapped on...they run aroun $10-15K each IIRC. Without DFCs you'll top out around 40Gbps (still nothing to sneeze at, but not even close to 720Gbps). And even then you've got caevats out the wazoo, such as average packet size - at 64 bytes per packet the switching ASICs will get overloaded before the backplane fills up.

      Secondly, the 6500 series is nowhere near the type of system this project is trying to replicate. This appears intended for the SOHO/branch office application - once you get to the enterprise/service provider level, where every minute of downtime has a real dollar cost, you need things like redundant power and management modules, NUBS compliance, and hot-swappable management/interface modules. You won't see any of that stuff in a PC anytime soon.

    25. Re:Sigh.... by bdp · · Score: 3, Insightful
      I think you're missing the point. The backplane of the Cat6500 is pretty much what the PCI bus does for a PC. A 32bit/33mhz PCI bus gives you just about 1 Gbps while the Cat6500 backplane provides three buses of 256, 32 and 4 Gbps (not 720 GBps as the GP suggested - the "Sup720" refers to the 720 Mpps switching capacity). Switching to PCIE gives you 2.5 Gbps per lane, but how many motherboards provide the 100 PCIE lanes needed to compete?

      I don't think I was entirely missing the point, but maybe I could have gone a little further in explaining myself. My poorly explained suggestion was that you can avoid the PCI bus entirely, thereby avoiding the bottleneck. When you have multiple cards installed in a single box you could just connect them together using some kind of high speed interconnect that goes directly between cards instead of using the system bus. That way you can have your high speed backplane to handle network switching/routing.

      That said, I understand that this is a bit silly and completely misses the point of using a PC as a router instead of something designed to do the job, but it would hardly be the first time such a product came out of the tech industry. If somebody thinks there's a market for it, it will be built.

      ASICs offload the hard work from the CPU of the Cisco systems. Basically any kind of compute-intensive bulk work, switching (yes, it switches layer 3 too), filtering (access-lists) and so on, is handled by dedicated ASICs and require little or no CPU intervention. This enables the catalyst to handle high amounts of data with a quite small CPU. Things that do end up on the CPU is management work, route computation (BGP changes, for example) and logging. To handle 720 million packets per second, you'd need quite a lot of CPU in your PC.

      Is there any reason why you couldn't accomplish this using something besides an ASIC? Offloading the work to the card is what I suggested before, and if you want to switching or routing with any kind of low latency, you have to do that. If you used that strategy, the speed of the processor in the PC wouldn't matter any more than the speed of the processor in a Cisco. Again, it may defeat the point of using a PC for routing, but that doesn't mean nobody would build it if there was a market.

      I think we're in total agreement that the high end of what Cisco does is not the target market. My biggest point that I was trying to make with my post was that there was no reason you couldn't stick a high speed backplane into a PC. It's just a matter of creativty and some engineering. Whether or not it makes sense is a whole different question.

      You may commence flaming the Cisco fanboy now.

      Can't see why I would do that. You managed to express a different point of view without a) going apopletic, b)insisting I'm an idiot for not sharing your view, and c) not insulting me and/or my lineage. If anything, your behavior should be applauded. I can see how you would expect different treatment on /. though.
    26. Re:Sigh.... by skarphace · · Score: 1
      What was she? Colorblind? Gee, the easist thing in the world is to terminate cable-it's either A or B.
      Read again. Here's a little help.
      Unfortunately, each cable end she crimped had its own unique order.
      Big difference between CAT5 punch downs and RJ45 cable terminators.

      Atleast with terminators you need a memory... wO-O-wG-B-wB-G-wBr-Br
      --
      Bullish Machine Tzar
    27. Re:Sigh.... by laughing+rabbit · · Score: 1

      I always preferred Bosch for routers. For most tools, it is the best woodworking tool out there, though nothing beats Milwaukee for it's line of Sawzall models.

      --
      No incumbents, not no where, not no how.
      Vote them out every term.
    28. Re:Sigh.... by monsted · · Score: 1

      Well, if you go through all that to make your PC into a router, you've just created a Juniper M160 :) From your initial post, i was thinking "a motherboard full of PCIe slots and GigE NICs".

      If you start making all these fun crossbar backplanes and line cards with on-board intelligence, you're 90% of the way to a dedicated router appliance and the OS part has been reduced to mostly keeping the hardware alive. This is exactly how a cisco or juniper box works, it just doesn't run Linux (although the juniper one does run FreeBSD ;)). Many older and/or smaller Cisco boxes even use PCI as their backplane.

      I don't see how you'd offload the work to a line card without putting some dedicated hardware on there, which would usually come in the form of an ASIC (or FPGA perhaps).

      > I can see how you would expect different treatment on /. though.

      I was quite certain people would kill me for not joining the "OMG It runs teh linux!!!1" crowd ;)

    29. Re:Sigh.... by pedalman · · Score: 1

      Unfortunately, she had been given a task with no training beforehand. She never heard of things like crosstalk. I kid you not; you could not find a correct A or B termination out of 52 drops. Before I came along, they had been on the phone back and forth with Cisco (it was a Cisco switch) complaining about data loss. Of course, there was nothing wrong with their switch.

      --
      Friends don't let friends line-dance.
    30. Re:Sigh.... by Heywood+J.+Blaume · · Score: 1

      I believe what they're talking about here is network-edge routing applications, not core switching that would require a Catalyst 65xx. Don't need that kind of backplane bandwidth.

    31. Re:Sigh.... by pedalman · · Score: 1
      Big difference between CAT5 punch downs and RJ45 cable terminators.
      Oh, yeah. Forgot to mention that there were no patch panels. Each cable had RJ45 connectors on both ends. Sorry 'bout that, Chief.
      --
      Friends don't let friends line-dance.
    32. Re:Sigh.... by DataSpring · · Score: 1

      I believe you mean "NEBS Compliance" not "NUBS" -- in particular, the most common reference is NEBS Level 3 compliance, which is most often related to "Carrier Class" equipment. This generally means the equipment will operate for years (decades, perhaps) at a time without being turned off and must have certain redundant parts, fire resistance, etc.

      Read more here:
      http://www.nebs-faq.com/what_is_nebs_level_3.htm
      http://en.wikipedia.org/wiki/NEBS

      Cheers!
      --DS

    33. Re:Sigh.... by Thundersnatch · · Score: 1

      So... can you help me figure out how to do simple weighted-queue prioritization for RTP voice traffic on a Cisco 2800? Everything I've tried results in a bandwidth reservation, and also a limit on total RTP throughput equal to the bandiwdth reservation(!). Cisco documentation, support, and a certified consultant we hired via Insight (questionable choice) couldn't figure it out either (although they all say "it's supposed to work, and not limit throughput like that").

      Now granted, I'm no Cisco expert, but I've administered corporate networks for 10 years and can figure out just about anything with a good manual. I shouldn't need in-depth training to do the simplest form of RFC-standard QoS on a router. The simple configuration I want took 3 minutes to implement via GUI on all of our SonicWall devices.

    34. Re:Sigh.... by Cramer · · Score: 2, Interesting

      It would've taken 3 minutes on the Cisco too if Cisco hadn't dropped QDM (QoS Device Manager) several years ago. QoS is never simple. On anything.

      (Obviously, there are alot of people doing that on a SonicWall or there wouldn't be simple "click here" interfaces to set it up.)

      BTW: you're issues with the 2800 could also simply be BUGS in IOS.

    35. Re:Sigh.... by Miniluv · · Score: 1

      Please, please don't suggest people try and implement network fast-paths in fpgas. They're just too damn slow. Prototype in them all you want, but turn it into a real ASIC when you go production.

      Also, you do have to be careful (as you probably know) with Cisco in how you configure their devices to keep the maximum amount of traffic on the fast-path or you will take a beating by pushing too many packets onto their slowass cpus.

      Junipers are awesome, cuz they let us unix geeks onto the router and give us a familiar way to interact with it. Hell, just cuz grep actually works on their devices makes them hands down better than Cisco (imho).

      A shop I worked in a while back tried replacing some juniper routers that were accepting GigE and OC-3 connections with some linux boxes using various PCI cards to take the same connections and do bgp, etc. Wow what a disaster. It wasn't linux's fault per se, but rather that we replaced a well designed, highly specialized box doing a highly specialized job with a general purpose machine. Sure we had a 2.4Ghz CPU instead of a sub 1ghz one, but we ended up being slower due to the lack of high speed silicon that's really good at the simple shit required to route 90+% of the packets it handled.

  2. Good luck with that! by winkydink · · Score: 4, Informative

    Cisco and Juniper offer 24/7 worldwide support. Whether or not it sucks, this is the thing that keeps people cozily asleep at night, knowing that if they have a problem, they have an unchallengeable defense of having bought the best in class support solution (notice I avoid any discussion of h/w, because in the enterprise, h/w without support is worthless).

    Yes, Vyatta talks a good game, but 24/7 worldwide support isn't something you build with a few million bucks in VC funding.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:Good luck with that! by bersl2 · · Score: 1

      Whether or not it sucks, this is the thing that keeps people cozily asleep at night, knowing that if they have a problem, they have an unchallengeable defense of having bought the best in class support solution (notice I avoid any discussion of h/w, because in the enterprise, h/w without support is worthless).

      Because, obviously, it is just that important to cover one's own ass.

    2. Re:Good luck with that! by kfg · · Score: 1

      Yes, Vyatta talks a good game, but 24/7 worldwide support isn't something you build with a few million bucks in VC funding.

      JAWMMBOS (Just Another We Make Money By Offering Support) OSS company. Nothing revolutionary to see here. Move along.

      Does it have a possible niche? Yeah, sure. Might even add something of value to the code pool. We'll see.

      But that doesn't mean that "enterprise" will buy in, which is all this story is about. Putting a corporate face on OSS software to try to make enterprise comfortable buying in to it. It's not a tech story, which is kinda what I was hoping for when I clicked on it.

      KFG

    3. Re:Good luck with that! by winkydink · · Score: 4, Insightful

      It is when you have shareholders. Like it or not.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    4. Re: Good luck with that! by John+Hasler · · Score: 1

      In other words, "No one ever got fired for buying Cisco."

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    5. Re:Good luck with that! by Anonymous Coward · · Score: 0
      Whether or not it sucks, this is the thing that keeps people cozily asleep at night, knowing that if they have a problem, they have an unchallengeable defense of having bought the best in class support solution

      Right... so then why did it take a couple weeks to get a replacement part for a Cisco router on which we pay tens of thousands of dollars a year for a 24x7x4 (four-hour replacement 24x7) support contract? Cisco's support sounds good (and I'll admit that it often is decent enough), but when it fails, it can fail spectacularly. And I don't believe there was any penalty for Cisco or compensation for us, despite the expensive support contract that Cisco was unable to honour.

    6. Re:Good luck with that! by killjoe · · Score: 1

      "Yes, Vyatta talks a good game, but 24/7 worldwide support isn't something you build with a few million bucks in VC funding."

      Why not? I am serious, why not? Most of ciscos support consists of putting you on hold for extended periods anyway. It's phone support and it can be done from anywhere in the world for a pretty cheap price. If somebody needs to come out they call the local chamber of commerce and get the contact of a local consulting company to come out and swap the hardware.

      That's how everybody does it. Do you really think the guy that comes out to swap the motherboard on your HP server is an HP employee? No it's some local guy selling HP hardware or even a local computer shop.

      So tell me once again why it's not possible to support people 24X7 with a few million bucks? The only possible time you can't is when you have too many customers.

      --
      evil is as evil does
    7. Re:Good luck with that! by winkydink · · Score: 2, Interesting

      Look at Red Hat. Why do you think Oracle is considering doing their own distro? Not because there's gobs of money in the distro space, but because RH can't support them well enough now and they have a significant RH installed base. One large enterprise customer would kill a startup with pre & post sales support requirements alone. This is one of the many reasons that startups have problems cracking the enterprise space.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    8. Re: Good luck with that! by Anonymous Coward · · Score: 0

      Unless you work at Nortel

    9. Re:Good luck with that! by Fordiman · · Score: 2, Insightful

      So it's a growth issue. I buy that.

      Now, question: How hard would it be to solicit new VC funding if you've suddenly got a big name customer? Crank that couple million to a couple hundered million.

      I realize there's training timeline issues along with it, but an appropriately motivated company should be able to handle it.

      I think it's just an issue of knowing when to change leadership (e.g., the guy that motivates a couple hundered programmers isn't necessarily the same guy capable of motivating a couple thousand tech support monkeys)

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    10. Re:Good luck with that! by osbjmg · · Score: 1

      So they can do what redhat does... enterprise support on an OSS product.

    11. Re:Good luck with that! by kfg · · Score: 1

      That's where I came in to this movie.

      KFG

    12. Re:Good luck with that! by timeOday · · Score: 2, Funny
      notice I avoid any discussion of h/w, because in the enterprise, h/w without support is worthless.

      Yes, Vyatta talks a good game, but 24/7 worldwide support isn't something you build with a few million bucks in VC funding.

      This sounds eerily like old Sun talk. "We don't care if competing products can do it for less, we're [Sun | SGI | Cray]!! The low end will never catch up with us, because we have special pixie dust!"
    13. Re:Good luck with that! by evilviper · · Score: 1
      Cisco and Juniper offer 24/7 worldwide support. Whether or not it sucks, this is the thing that keeps people cozily asleep at night,

      Really? I think I'd sleep better knowing that (for the same price) I got MULTIPLE PC/software routers, setup in a zero-downtime failover cluster, with replacement parts trivially easy to get anywhere at anytime, and have full access to the source code if ever necessary.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    14. Re:Good luck with that! by winkydink · · Score: 1

      can you say "dilution"? I knew you could.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    15. Re:Good luck with that! by toadlife · · Score: 1

      "Do you really think the guy that comes out to swap the motherboard on your HP server is an HP employee?"

      I'm pretty sure that the guy who comes out to for service calls on our HP servers is an HP employee. It's been the same guy for years, and he does everything from our 1U x86 boxes up to our HP 9000. He always wears an HP shirt and the only 'war stories' he ever tells involve HP equipment.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    16. Re:Good luck with that! by Fulcrum+of+Evil · · Score: 1

      More importantly, you have someone to fix the problem so you don't get woken up.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    17. Re:Good luck with that! by monsted · · Score: 1

      And when your "zero-downtime failover cluster" gets a bug up its ass and the two nodes decide to battle it out for control over the virtual addresses, taking your network down?

      It happens. For Cisco, HP and Sun too. The difference is, you can call them and bug them about it instead of hoping that the open source project people realize there's a problem and have time to fix it - or that you can fix it yourself.

    18. Re:Good luck with that! by Jason+Earl · · Score: 2, Interesting

      Yes, but there is a large market of folks that either A) have dealt with Cisco's so-called support and aren't impressed or B) would rather simply have a preconfigured spare box for less price than a single Cisco.

      If there is one thing that Linux has proved it is that you can't underestimate inexpensive and "good enough." You may not be interested in what Vyatta is selling right now, but I would bet that enough people are interested that the next gen Vyatta is even more competitive. In the long run, the low end of the technology spectrum tends to improve and gobble up marketshare from the guys asking for big margins.

    19. Re:Good luck with that! by vsavkin · · Score: 2, Interesting
      Whether or not it sucks, this is the thing that keeps people cozily asleep at night, knowing that if they have a problem, they have an unchallengeable defense of having bought the best in class support solution


      Here in Moscow, Russia most ISPs buy Cisco gear w/o any kind of support. Not even usual warranty period on hardware is there (Cisco gives 2 or 3 months only). Not having their asses covered by that kind of paper works fine for them.

      Also, when talking about hardware, off-the-shelf PC router can do 100..400 kpps, it is more than enough for small provider's core router, not even considering branches.
    20. Re: Good luck with that! by FST777 · · Score: 1

      I nearly was. The darn thing couldn't be forced to be friends with our ADSL connection, nor would it handle passive FTP properly. I had it replaced with a m0n0wall x86-PC + el-cheapo Alcatel DSL-modem within two days, and then the boss was happy. Not the best solution, but still good enough.

      That was the last time we bought Cisco gear.

      (Yes, we had a Cisco-certified technician called in. He fixed the issue with the ADSL (costed him three hours) but couldn't fix the FTP-issue, forcing us to use 56k dialup for online banking. I'm not kidding.)

      --
      Free beer is never free as in speech. Free speech is always free as in beer.
    21. Re:Good luck with that! by killjoe · · Score: 1

      So the only problem is having too many customers (just like I said). If you have one large customer then you can support them with a few million dollars.

      The idea of a support contract is to make a profit off them. If you are losing money because you sold too many support contracts then you are doing something wrong.

      --
      evil is as evil does
    22. Re:Good luck with that! by pyite · · Score: 1

      Really? I think I'd sleep better knowing that (for the same price) I got MULTIPLE PC/software routers, setup in a zero-downtime failover cluster, with replacement parts trivially easy to get anywhere at anytime, and have full access to the source code if ever necessary.

      There is no such thing as zero-downtime. Even the best engineered systems fail unexpectedly. I recall when our Cisco 12000 GSR core failed, running DPT/SRP. The thing is never supposed to fail, even under multiple hardware failures and fiber cuts. Well guess what? One faulty piece of equipment brought the whole ring down in one fell-swoop. Was that how it's designed? No. Did it happen? Yes. I doubt you'd be able to QA your home-brew setup more than Cisco does their routers that they sell for $1 Million a piece with cards. If they miss stuff, you would too.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

  3. Siad the OS advocate... by Duncan3 · · Score: 5, Funny

    Advocate 1: "I work at Oracle by day, but work on Vyatta by night."

    Advocate 2: "Well, I work at Cisco by day, but work on PostgreSQL by night"

    [awkward pause]

    Advocate 1: "Pistols or swords?"

    --
    - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
    1. Re:Siad the OS advocate... by QuantumG · · Score: 1

      I work on slashdot by day and mySQL by night, can you tell?

      (I don't really, it's a joke).

      --
      How we know is more important than what we know.
    2. Re:Siad the OS advocate... by Profane+MuthaFucka · · Score: 3, Funny

      Well I work on Microsoft Windows during the day, and SQL Server at night.

      Advocate 1: "Pistols or swords?"

      Both please. Right in my head.

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
  4. No. You're not making a 1U into a $40K router by postbigbang · · Score: 4, Interesting

    Here's why:

    1) it takes an RTOS to make things work well. You can grind all the driver code you want, but an RTOS foundation is required with lots of cache
    2) only PCI-X bus gets close, and most 1Us don't have it. That gives you a real ceiling in terms of port-port throughput; don't kid yourself
    3) the algorithms needed to maintain cross-bar speed are gruesome. You don't find this kind of code in anything but sledge-hammered C and assembler, and code that only a mother (and an embedded systems engineer) could love. There is very little forgiveness here.

    Yes, a 1U can make a decent router. But don't kid yourself into believing that you can beat F5, Cisco, Alcatel, etc.

    You can certainly embarrass them, but on the high end, it doesn't work.

    --
    ---- Teach Peace. It's Cheaper Than War.
    1. Re:No. You're not making a 1U into a $40K router by twiddlingbits · · Score: 4, Interesting

      The RTOS doesn't use a lot of cache, It needs a fast CPU and tight code to handle the massive numbers of context switches. The code you mentioned isn't all running on a CPU either. A lot of it is on custom hardware to keep up those data rates. The PCI-X bus would work except very high end, and it IS available in current 1U servers from people like Sun and HP, but certainly not in that old 286 in the closet. You could turn an Opteron with the HyperChannel architecture into a pretty darn good router. But the Opterons cost quite a bit more than a 286 would (does any foundry still MAKE 286 chips?). It's a good project but I agree it's not ready for prime time in the corporate data center.

    2. Re:No. You're not making a 1U into a $40K router by kfg · · Score: 0

      One I clicked on the story about an Open Source router I was kinda hoping to see . . .a router.

      KFG

    3. Re:No. You're not making a 1U into a $40K router by Ant+P. · · Score: 1

      It won't make it into a $40k router, true.

      But it'll make a pretty good $1k router.

    4. Re:No. You're not making a 1U into a $40K router by Tweekster · · Score: 1

      some geeks tend to forget that the vast majority of companies simply dont need a $40K router, they need a 10K router and that is it.

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    5. Re:No. You're not making a 1U into a $40K router by Anonymous Coward · · Score: 1, Interesting

      context switches

      You're doing it wrong. Let's take linux: once the userspace applications configure netfilter (iptables/snort) or the routing table (quagga/zebra) or the rest of the protocol stack (iproute2), everything else is done in kernel. As for speeds, there are linux kernel patches (ok, for one driver so far) that allow the kernel to shovel data to userspace at gigabit speeds already, moving the data from one card to another should be no problem for a limited number of ports.

      Now thats where the system breaks down. Or one could say it breaks down, but has anyone looked at the specs for these routers? Take a look at Cisco's 7200 series page: this model has a throughput on the backplane of 1.8Gbps, for a rating of 2 megapackets per second. If it was connected to four GigE networks, and two of them tried to transmit to the other two networks, you'd hit its maximum. And this thing has up to 4 or 6 bays for network connections.

    6. Re:No. You're not making a 1U into a $40K router by postbigbang · · Score: 1

      It's true that there are a few machines-- in 1U form factors-- with PCI-X. But CPU doesn't get you there. Bus clock and tight driver integration with the kernel space gets you there.... unless you want just a Saturday Night Special sort of router.

      We agree on the 'not ready for prime time' part.

      --
      ---- Teach Peace. It's Cheaper Than War.
    7. Re:No. You're not making a 1U into a $40K router by twiddlingbits · · Score: 1

      The AMD HyperChannel architecture has some possibilities. Non-disclosure prevents me from saying more.

    8. Re:No. You're not making a 1U into a $40K router by postbigbang · · Score: 1

      I love fast buses.

      Now let's write drivers for the cards that we'll plop inside of them, and do all the other good stuff to make 'em work.

      Soon.

      --
      ---- Teach Peace. It's Cheaper Than War.
    9. Re:No. You're not making a 1U into a $40K router by Anonymous Coward · · Score: 0

      pci, PCI-X will lose out to PCI Express as it becomes the x86-xx standard. More specialty neworking cards will use this interface and Cisco and Juniper will lose.

    10. Re:No. You're not making a 1U into a $40K router by Megane · · Score: 2, Informative

      Two words: cut through.

      With a software router (aka your typical Linux-nerd router), the entire packet has to be read before the routing decision can be made. Then it has to be sent out again.

      With Cisco, what you are paying for isn't the routing, it's the low latency of hardware that can see the destination IP address in a packet header, then effortlessly shunt the bits off to another interface in real time. You're also paying for the hardware being designed with 24/7 operation in mind, with little extras like watchdog reset timers that you won't find in that seven-year-old beige box.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    11. Re:No. You're not making a 1U into a $40K router by twiddlingbits · · Score: 1

      AMD has some ideas about direct attached cards for the Hyperchannel but that's not making a lot of progress, the big Opteron server vendors like Sun & HP are not getting behind it. When we get cards we can develop drivers. Right now it all goes thru a PCI Bridge which actually slows things down.

    12. Re:No. You're not making a 1U into a $40K router by Fordiman · · Score: 1

      the article clearly states "middle-end", does it not?

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    13. Re:No. You're not making a 1U into a $40K router by MonsoonDawn · · Score: 1

      Hey, anybody remember the good old days when arguments like this were used to discredit grids & clusters? Let's not forget VoIP.

      Maybe - just maybe - the conjunction of cheap hardware, free OS, and decent routing software will open up new ways of implementing enterprise class routing. Software routers don't necessarily need to emulate Cisco & Juniper to clean their clocks.

    14. Re:No. You're not making a 1U into a $40K router by Florian+Weimer · · Score: 2, Insightful

      Perhaps not a $40K router, but a $15K one--for $3K (including the replacement, should the first unit fail).

      1) it takes an RTOS to make things work well. You can grind all the driver code you want, but an RTOS foundation is required with lots of cache

      IOS is not a real-time operating system, which nicely disproves your claim. 8-)

      2) only PCI-X bus gets close, and most 1Us don't have it. That gives you a real ceiling in terms of port-port throughput; don't kid yourself

      In some of the Cisco low-to-mid-range routers, the line cards are connected to PCI busses (not that what's usually called L3 switches, of course). In fact, these routers are basically PCs with a MIPS CPU.

      3) the algorithms needed to maintain cross-bar speed are gruesome. You don't find this kind of code in anything but sledge-hammered C and assembler, and code that only a mother (and an embedded systems engineer) could love. There is very little forgiveness here.

      Most vendors do not offer wirespeed performance in all cases, either. You usually do not need the last 10% or 20% in performance. Given the savings (both in terms of device price and training), I'm willing to sacrifice 50% of the performance and more.

      The real issue is the feature set of the available software. For GNU/Linux or the BSDs, the basic protocol support is usually there (but perhaps just in a userspace implementation which sacrifices some performance), but even pretty common things are sometimes missing because those who sponsered the development didn't need it (and it's not required by the standards, either). In some case, the implemntation isn't very mature yet. For the price difference of a Cisco box, you could hire someone in Russia to implement the missing stuff, but this gets a bit complicated, especially if you just want a working router.

      On the other hand, there are some things which are impossible to do with IOS (obscure policy-based routing, most kinds of payload analysis, prefix-based accounting, OpenVPN). But most people don't expect routers to do such things anyway.

    15. Re:No. You're not making a 1U into a $40K router by ZWithaPGGB · · Score: 1

      Cisco IOS isn't an RTOS. The XR version is based on an RTOS, but the $40K versions of Cisco's gear don't run it.

      Don't get me started on how underpowered the hardware is. PCI-X 1x is faster than most CISCO backplanes. What Cisco routers are 1U? Let's compare the big pig switches with a 2 or 4U box, and then we'll see apples to apples.

      Sure, you can get your ultra-ancient lame SNA to work on the Crisco, but if you're using one for IP forwarding, you're overpaying for underpowered HW and lame old software that does everything, but nothing well. If you're using one for any added services, note that everything that isn't handled by the VIPs is on the slow path, IE through the main CPU, and that CPU is orders of magnitude slower, due to purchasing and design leadtimes, than the latest Opteron or Core CPU. As for the RAM, have you seen any Cisco routers with gigs of DDR2?

      In short, Vyatta is going to make OSS do for routing what LAMP did for hosting.

    16. Re:No. You're not making a 1U into a $40K router by Bert64 · · Score: 1

      It's not just raw bandwidth to contend with...
      You also need to worry about interrupts, many cards generate 1 interrupt per packet, which will quite quickly saturate the bus when you have lots of small packets coming in.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    17. Re:No. You're not making a 1U into a $40K router by monsted · · Score: 1

      It's also a five year old platform.

    18. Re:No. You're not making a 1U into a $40K router by infosec_spaz · · Score: 1

      Yeah...and as far as I know, Cisco has neither. I can go buy a 3.4ghz P4 processor, and beat their dedicated network processors, as well as their system processors...why not give it a shot? I have used several "other" router OSes and have seen the likes of Mikrotik, Zebra, etc beat Cisco in the mid-range market.

      --
      ----- I have bad karma for a reason! -----
    19. Re:No. You're not making a 1U into a $40K router by twiddlingbits · · Score: 1

      Exactly, and Interrupts cause context switches. The AC was wrong.

    20. Re:No. You're not making a 1U into a $40K router by macdaddy · · Score: 1
      In some of the Cisco low-to-mid-range routers, the line cards are connected to PCI busses (not that what's usually called L3 switches, of course). In fact, these routers are basically PCs with a MIPS CPU.

      Ok, I'll bite. Name one.

  5. The Dawn of Open Source Networking? wtf? by Anonymous Coward · · Score: 2, Interesting

    If you go to Vyatta's website they claim that they are bringing in the "Dawn" of Open Source Networking.
    Unfortunately these folks obviously were living under a ROCK for the past 8-10 years and never noticed
    things like oh.. IPTABLES, and there has been WAN support in Linux for a long time. Great companies like
    Sangoma offer T1 cards etc etc. This is just a bunch of folks trying to cash in on support contracts on
    the backs of great open source projects and developers. We shouldn't even be giving them the press! They
    are a bunch of HACKS!

    1. Re:The Dawn of Open Source Networking? wtf? by ObsessiveMathsFreak · · Score: 1

      Unfortunately these folks obviously were living under a ROCK for the past 8-10 years and never noticed
      things like oh.. IPTABLES, and there has been WAN support in Linux for a long time.


      Actually, they did notice IPTABLES. That was sort of the whole point of starting the project.

      --
      May the Maths Be with you!
    2. Re:The Dawn of Open Source Networking? wtf? by mobby_6kl · · Score: 1
      Actually, they did notice IPTABLES. That was sort of the whole point of starting the project.

      But they still didn't notice what actually mattered: Packet Filter.
    3. Re:The Dawn of Open Source Networking? wtf? by Anonymous Coward · · Score: 0

      So they don't think iptables and iproute2 are networking?
      Did they not notice:

      http://leaf.sourceforge.net/

      That would be like a new linux distribution saying they're
      bringing the Dawn of the Linux Desktop.. complete JOKE!

    4. Re:The Dawn of Open Source Networking? wtf? by Anonymous Coward · · Score: 0

      c'mon now Niall.. we all know you can't configure iptables! :-)

  6. Ah hem, OpenBSD.?.? by Anonymous Coward · · Score: 4, Informative

    You get OpenBGPD and OpenOSPFD all working in concert through the kernel. Oh and did I mention the price? $40.

    Brilliant!

    1. Re:Ah hem, OpenBSD.?.? by Anonymous Coward · · Score: 0

      Networking acronyms give me a headache. Did you say something about the SPF of my BFG? I think it's 30x.

  7. Speed? by quanticle · · Score: 1

    While this router probably will be a valid competitor to Cisco/Juniper in many areas, it probably won't be able to compete in the very high end market where these companies have made a name for themselves. Cisco routers, at least do a lot of processing using ASICs, which are specifically optimized to make the kinds of decisions needed for routing packets. I'm not sure whether traditional x86 can match that level of performance.

    --
    We all know what to do, but we don't know how to get re-elected once we have done it
    1. Re:Speed? by cyber-dragon.net · · Score: 1

      I agree. I am very much an advocate of the "right tool for the right job" theory.
      Making a system designed to be a general purpose tool (ie a 1u computer) into a single purpose device is bound to not be as good as a device designed to do that job.

      If I want a firewall or router I want it to be capable of doing it's job to the best of it's ability, not limited by the processor if another type could have been faster. Also not limited by the OS if a small bit of highly dedicated code could do a better job than something written on top of an OS designed to be all-purpose.

      Just my 2$ (inflation and all)

    2. Re:Speed? by Anonymous Coward · · Score: 0

      You won't match the speed of an ASIC with a generic x86.
      You'd either need some kind of plug-in PCI card with,
      guess what, an ASIC or PFGA processor on it, or some
      very intelligent software that makes use of today's
      multicore processors. Many routers have processors
      directly on the ports, so a processor does the
      processing ON the ingress port, and passes it to the
      egress port. Very rarely do the packets get passed up to
      a master processor. On the PC, that would be like taking
      packets in on a PCI card in slot 1, it do processing on it,
      and bounce it out to a PCI card in slot 2 for egress.

      Basically what Vyatta is doing is this:

        - Giving you a steering wheel
        - Telling you that you need tires,a seat and an engine
        - Telling you that you COULD have a Ferrari

      Reality is, you've got nothing more than a Lada (Geo Metro for
      them Americans) with the word Ferrari painted on the door. When
      you go COMPLAIN to Vyatta.. they'll say, HEY you used the wrong
      hardware! It'll be interesting to see what gear they come up with,
      kinda odd they didn't piece together their own hardware to start
      with.

      Then again, with just a sales number, they can't even setup their
      own e-commerce site, do you really want to trust them with your
      network? :)

    3. Re:Speed? by CastrTroy · · Score: 1

      Can you please tell me why businesses are still running Databases on General purpose boxes with a general purpose OS then? It seems to me that something as resource intensive, time critical, specialized, and expensive as your typical enterprise level database server should be run on specific hardware and a specific OS geared towards running a database. Why do you put your data files on top of a file system that's designed to be general purpose, when you could probably get better performance by dedicating a raw partition or device straight to the database. Wouldn't it be nice if your processor had a Join instruction, or special instructions used for searching large amounts of data. Why are routers the only place where we get specialized hardware and OSes, even though they are rarely the bottleneck.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    4. Re:Speed? by jnf · · Score: 1

      (they're rarely the bottle neck because they have specialized hardware for the task)

    5. Re:Speed? by fozzy1015 · · Score: 1

      As a embedded developer for a big telecom that builds enterprise routers, I can vouch for this. We use ASICs on our interface blades that does the bulk of the layer 2 switching. A packet comes in on a port, it's source MAC and the port it came in on is put into RAM that's on the ASIC itself, and the packet is either fowarded if the DA is known or else it's flooded. Aging is also done by the ASIC. We have lots of custom code on the blades for handling limitations in the SDK, timing issues, and 'corner cases' but the bulk of the layer 2 switching is done by the ASIC. In fact, on our core router we can reboot the main processor card and not only will packets still forward on the same card, they'll even forward across the fabric to other cards. It would be unacceptable for us not to be able to forward traffic on a 24 gig port card to 6 port fiber 10gig at wire rate. The company who builds the ASIC we use is willing to listen to us as to what we want them to dedicate more transistors to in their next revision. It's a pretty good relationship.

      Not to say we don't take network routers becoming more and more of a commodity seriously. Believe it or not raw speed isn't all we aim for in the future. Security features are what our customers seem to be more focused on wanting. A lot of it will be just in the software although looking at the featuers for the next ASIC revision there are some pretty good features for the layer 3 team.

      The parent post mentioned support, which is VERY important to customers. As well as being able to offer a complete solution. I work in enterprise but the company I work for is very big and has hardware for various levels. So here the sales guy can come in and offer an enterprise solution: Two core routers and a few dozen edge routers. But then they offer a microwave WAN link. And wireless nodes as well. A customer wants to know that a single company can offer support for many different levels of their network.

    6. Re:Speed? by CastrTroy · · Score: 1

      I realize what you're saying, but at the end of the day, the router connecting say, the web servers to the database server is usually much faster than it needs to be. Most of the time it can handle the traffic going back and forth with no problem, and the slowest part is actually getting the database to return the results. I'm not saying that specialized hardware for routers isn't a good thing, but rather wondering why we don't see this technique used on other machines in the datacentre. What makes the routers so special. It doesn't make much difference if the network takes 10 ms or .5 ms to return the results when the database takes 100 ms to run the query.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    7. Re:Speed? by cyber-dragon.net · · Score: 1

      Ah but it does make a difference when you get ten database servers behind the router all returning ten requests at 100ms... then you NEED the router to respond at 10ms or better yes?

      Routers are not about the speed of any individual machine... they are about keeping up with ALL machines sitting behind them.

      Not disagreeing with you... I think eventualy for speed increases we WILL have to move to specialized hardware for other things. Why not make a processor that only divvied up tasks? It would send audio to the audio processor, video to the gpu etc. That is the next gen of "general" computing, not faster processors.

  8. Open source and routing by stox · · Score: 4, Insightful

    I guess those BSD guys have just been playing around all these years.

    --
    "To those who are overly cautious, everything is impossible. "
  9. Hardware Components by CelestialWizard · · Score: 3, Insightful

    While a company such as Vyatta may be able to deliver the software to actually do the routing, you still need hardware pieces to actually connect to your equipment.

    There aren't many PCI (full or half height) cards that can do ATM with OC3, etc....

    Then there is the size factor. Data centre space is sparse and expensive, cisco (and such) equipment is built for this space. x86 PCs also run hotter (and louder) than specifically designed hardware from vendors such as cisco, juniper and 3com. oh and they draw more power.

    i just can't see how this will take off in the top end of the market.

    sure, for a small branch office that connects to frame, isdn, dsl or pstn and runs a vpn it may be fine, but not in a data centre or racked environment.

    1. Re:Hardware Components by Knara · · Score: 1
      They did say "midrange", of course.

      I suppose that depends on what one considers "midrange", I suppose.

    2. Re:Hardware Components by alienw · · Score: 1

      You're still not saving anything. Plenty of companies offer tested, integrated router solutions for the low end, at a much lower price point than you can get with an x86 box, and with a 10-year warranty. Show me a PC manufacturer that offers a 10-year warranty.

    3. Re:Hardware Components by burne · · Score: 4, Interesting
      There aren't many PCI (full or half height) cards that can do ATM with OC3, etc....
      I've been able to live in ISP-land for over ten years without ever coming close to ATM. Big exchanges like the AMS-IX (biggest public IX worldwide) have been pure ethernet since their inception. Getting ethernet in some form from a transit-provider is just a checkbox in the right place. Current commodity hardware will do linespeed GigE over PCI-X. Current high-end PC's have sufficient bandwidth available. 66MHz 64bits PCI-X might sound like 266MB/s, but keep in mind that equates to well over 2.5Gbit/s. The right hardware has 3 independant PCI busses and busmasters, so should be able to move 7.5Gbit/s of data via busmastering DMA, and thus with low CPU load. Keeping a full routing table and a bgp-daemon running doesn't require odd hardware. Juniper has been doing that on a Pentium MMX 333 with 768Mbyte since 2001, and a dual Xeon 2.4 will giggle at that 'workload'.

      Combining the above will give you a 3U box (smaller than a 7200) which will route (not switch) 4-5Gbit/s reliable. A 7600 is a lot bigger and a serious sh*tload more expensive. You could buy several identical boxes for redundancy and still keep some change left.

      Support is the only serious objection one could have in a FastEthernet-, GigE- or 10GE-world. Luckily I don't need support. I have been supporting stuff like above for ten years so I can manage. I can even support your Cisco and Juniper-platforms as well. I can handle my monthly exabyte by myself, thank you very much.
    4. Re:Hardware Components by baldusi · · Score: 1

      You could consult here:
      http://www.tldp.org/HOWTO/Hardware-HOWTO/nic.html

      Or here:
      http://linux-atm.sourceforge.net/

      But I guess networking professionals can't really Goggle for "linux ATM".

    5. Re:Hardware Components by figment · · Score: 1

      I totally agree with your assessment here, but I don't see why anyone on the low end would want it either.

      1600s and 2600s are just dirt cheap now, even with WICs. You can't build a comparable x86 (runs on flash, 1u, low power consumption) for the price. And saving 200 bucks by building a crappy x86 really doesn't make any sense when you're paying $500+/mo for your actual T.

      I think everyone agrees that you won't get the performance of an asic-based router, so the only thing they have going for them is price. But with sonoma cards going for $500 each, that's like twice the price of a WIC already.

      So where's the benefit? Slower than a Cisco, more expensive than a Cisco, worse support than a Cisco. "It's open source so you can do anything you want"? I don't know about yours, but my IT staff doesn't have the time or the money or the manpower to devote an army of C/asm programmers to go off writing network code when we could just buy an IOS off the shelf that does the same thing.

    6. Re:Hardware Components by Anonymous Coward · · Score: 0

      here aren't many PCI (full or half height) cards that can do ATM with OC3, etc....

      You only need one that works. Maybe a couple more would be nice for competition and support options. The less there is, the better chance your routing solution that needs one of those cards will support it well. If there was only 5 ethernet chipsets available, I can assue you that every OS ever made would support all five of them and you would never have to hunt down drivers for them.

    7. Re:Hardware Components by wintermute000 · · Score: 1

      Well if you have ethernet over fibre available all well and good, but not everywhere has enough infrastructure to deliver ethernet all the way to the CPE without going through another WAN protocol somewhere.

      I may have been brainwashed by Cisco.... :) but as a regular open source (Fedora) user I'm not convinced consumer grade x86 hardware, no matter how good the software is, will be able to match Cisco/Alcatel etc. for enterprise applications. Not without lots more downtime and the (obvious) support issue which everybody's already thrashed to death. Imagine the nightmare hodgepodge of components, different firmware revisions, etc. etc. (anyone who's had wireless issues with linux on an older card and had to slog through id-ing the firmware, finding what flash images it can take, dunno if its even a hardware issue etc. etc. will see the point right way)

      For home / small business though it sounds like way to go, just like for home / small business, an entirely open source solution is eminently practical and in many ways advantageous

    8. Re:Hardware Components by albanac · · Score: 1
      Big exchanges like the AMS-IX (biggest public IX worldwide)

      Hi. Point of information: last time I looked that was the LINX, and I'm reasonably sure it still is. Also, I'd be interested in your terms here: is 'biggest' meaning 'broadest peering matrix'? Or does it mean 'largest traffic volume on the switch fabric'? Or some other measure?

      ~cHris
    9. Re:Hardware Components by MikeBabcock · · Score: 1

      That's FUD, but to be fair you didn't mean it to be.

      Use hardware that's 100% Linux compatible, its not a big deal. Besides, its not like I can take a DLink card and shove it in a Cisco box either. Using the right hardware is always necessary.

      I use Intel NICs with TX/RX CRC offloading and scatter/gather and they work very well for me.

      --
      - Michael T. Babcock (Yes, I blog)
    10. Re:Hardware Components by wintermute000 · · Score: 1

      True enough, esp. if you have vendors selling 'certified' hardware where every component checks out. Point taken.

      Normally I'm a big linux advocate - I run linux on my 'server' / main desktop, and I own a gp2x, I went through that linux newbie's 'gotta install linux on everything that I can possibly do' syndrome etc. but in this case I'm skeptical of its ability to match the routers whose hardware/software is designed from the ground up to switch / route information, as quickly and reliably as possible. Esp. running on consumer grade hardware.

      HOWEVER

      if the price is right and the margin of difference isn't so great, the open source solution may indeed turn out to be the most cost effective as long as you can cop the lower reliability. Just means we won't be seeing open source x86 core routers for quite some time ;) but for your router that connects your local office to the VPN that only handles 2 connections (LAN back to office, WAN to corporate network), it looks pretty promising.

  10. True... by jd · · Score: 4, Interesting

    ...they buy "world-class support", but having tried to use said support on occasion, I can say that I feel sorry for the world. Sure, it's better than a kick in the head, but not so much that it's worth the cost. I believe the record for longest repair ever was at the University of Manchester, in England, where a Cisco router corrupted the 1518th byte in every packet (thus only corrupting packets with a 1500 byte payload or 1496 bytes over 802.1q). Took them NINE MONTHS to fix. The first three of those, they denied there was even a problem.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:True... by Anonymous Coward · · Score: 0

      a Cisco router corrupted the 1518th byte in every packet (thus only corrupting packets with a 1500 byte payload or 1496 bytes over 802.1q)

      Got a link for that handy? I can't find anything with google.

    2. Re:True... by Tony+Hoyle · · Score: 1

      Really doesn't surprise me with cisco.. I dumped the one cisco router we had after a long list of problems - each time it took over a month to get to someone with a clue to admit there was a problem, and 6-9 months to actually issue a fix. None of those fixes are yet in a shipping IOS.

      My favourite was the DHCP server.. they 'forgot' (their words) to test it on Windows clients, which use an 'obsolete' version of DHCP standard (again their words) so the dynamic DNS updates don't work at all (well they kinda work.. provided you can get it to send the updates to the right server (another, separate, bug) they send the wrong machine name...)

    3. Re:True... by l0ki · · Score: 2, Interesting

      system mtu 1504

      THEY didn't currupt your data- .1q adds extra bits onto a packet so that it can "tunnel" data from source to destination- with- you VLAN info etc intact... thus it has to add data to the packet- which can make it bigger (jumbo) than intermediate devices expect/allow... it's normal bevahior and you just need to tell those intermediate devices to allow bigger MTU size without dropping the frame as being too big... Maybe this was a while back or something.

      You can't blame Cisco for a missing config line...

      --
      "You never truly understand a thing until you can explain it to your grandmother" -Albert Einstein
    4. Re:True... by nolife · · Score: 2, Informative

      If the solution was really that simple, you just proved the parents post. The referenced Cisco world class support team took nine months to diagnose and fix a problem that a random person on /. could have fixed in 30 seconds.

      --
      Bad boys rape our young girls but Violet gives willingly.
    5. Re:True... by NotBorg · · Score: 1

      Ok, that's the extreme case but what about the average or mean times? While I personally do have my doubts about the worth of many "world-class support" options, this example isn't necessarily representative of the business as a whole. If I were to gamble on it, where would my odds lie?

      If I chose an open source solution are my odds better at getting the support I need?

      DGMR, I'm not claiming one side or the other, just find the discussion interesting.

      --
      I want this account deleted.
    6. Re:True... by TCM · · Score: 1

      Why would he have to do that when not using VLANs? The parent said that corruption was occuring at normal full-sized packets in addition to 1496 bytes VLAN packets.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    7. Re:True... by osbjmg · · Score: 2, Informative

      Dude, they surely tried this. Don't assume you fixed the problem when in fact you weren't there! Depending on the platform and functions applied to this particular device, it could have been much more complicated. Usually they are running traffic tunnelled through the FWSM module and it forgets to take into account the .1q tag or they are using an encryption module which had calculated on pre encryption sizes.

    8. Re:True... by monsted · · Score: 1

      They wouldn't leave it for nine months if they didn't have a workaround (set MTU to less than 1500). We've often received engineering builds from TAC to fix various problems and if the excrement hits the fan, you can have TAC work on your case 24/7, moving it between their three main TAC centers.

    9. Re:True... by macdaddy · · Score: 1
      I can not believe you just said that. Repeat after me people:

      Windows DOES NOT adhere to the DHCP protocol standards AT ALL.

      Microsoft's interpretation of the DHCP specs is worse than their interpretation of the W3C's HTML and CSS specs. It is absolutely horendous. Do you want to support Windows DHCP clients? Run the Windows DHCP server or don't bitch and moan when things don't work correctly. This is extremely common knowledge.

    10. Re:True... by macdaddy · · Score: 1
      More likely is that the fiber connections between the buildings were passed through a non-VLAN aware/non-jumbo frame aware optical transport system. IEEE 802.1Q was not ratified until 1998. Most OTSs were not VLAN-aware until the early 2000s. Most OTSs did not support jumbo Ethernet frames until about the same time frame. All OTSs that supported neither VLAN tag passing or jumbo frames would have seen the larger packets as corrupt. The action of the individual OTS would be whatever action the vendor chose to implement. If the OTS did in fact have this limitation and could not be fixed or replaced with a more functional unit then the fix would have been to simply eliminate the L2 connection between the affected buildings and replace it with a L3 connection (ie, route from the affected buildings instead of trunking VLANs back to the core). It's a simple fix but an extremely weird problem to diagnose. I imagine that university, like many universities, has separate telecom and IT departments. In all likelyhood the IT department would have gotten the fiber from the telecom department. In an established institution like that I would be surprised to hear that the telecom department had ATM running across the campus over OTS-supplied rings to support their remote key systems. Telecom would have provided IT with the "fiber connection" which was really a LANE drops off of their OTS system. That would have been the end of the telecom department's involvment. This is a very likely scenario that I've actually seen played out before.

      I ran into this very problem on a much newer OTS no more than 2 weeks ago.

  11. Not just BSD. by jd · · Score: 2, Informative

    GateD used to be under a semi-open license. Then there was MRTD, Zebra and Quagga. XORP is said to be pretty good, too. MIT's Click is probably the most versatile, as you can just about script your own routing elements - very pluggable - with the added capability of routing between physical and simulated (eg: NS-2) networks.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Not just BSD. by Christopher+Cashell · · Score: 1

      Vyatta's work is based on XORP. They've taken it, polished it, enhanced it, and provided even (monetarily) supported it. They also contribute their work back to the XORP project.

      They complement each other well. XORP is more of a research project, while Vyatta's OFR (Open Flexible Router) is a CD installation of XORP and other software that can be installed and run almost as an appliance.

      --
      Topher
  12. If you're in a developing economy by rsilvergun · · Score: 0, Flamebait

    like India or China, 24/7 cya support is much less important, because you're economy is growing fast enough that you can recover from a meltdown, if only by starting a new company.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  13. Yawn. Slow news day? by Anonymous Coward · · Score: 0

    I seem to recall my first home broadband connection used a 386, running Freesco linux from a floppy. The next one was a 486 running smoothwall linux with transparent squid web caching (because I found a CD drive in the trash).

    All on junk hardware picked out of dumpsters (well, OK, I had to buy the cable modem I admit).

    I'm sure you can't route six dozen T1s with complex firewall rules and packet mangling on a 486, but you can do anything a Cisco 2500 series could do, and you can still do QOS, NAT, firewalling, etc. etc. etc. using more recent dumpster hardware. PCs running tuned linux or BSD kernels work great for anything but ISP-grade stuff.

    And this company will sell you open-source routers suitable for small ISPs, too.

    Wake me up when the hype is over.

  14. Ripoff of JunOS by Anonymous Coward · · Score: 0

    Wow can we say blatant ripoff of JunOS

    the command structure is the same..

    1. Re:Ripoff of JunOS by mindtriggerz · · Score: 1

      Hmm, perhaps it's because JunOS is based on BSD?

    2. Re:Ripoff of JunOS by Christopher+Cashell · · Score: 1

      Yeah. It's almost as if they were trying to model the command line interface off of an existing and well known interface to make it easier for people to use. . .

      --
      Topher
  15. This reminds me this... by dark-br · · Score: 2, Interesting

    ... interesting article on TechWorld: A reality check for open source routing.

  16. 7200? How about replacing big iron? by burne · · Score: 5, Informative


    My former employer is using three relatively simple Tyan dual Xeons with a couple of Syskonnekt cards to shove 4-5 gigabits per second of traffic over the internet (yes, full routing, and over 240 peers on AMS-IX and NL-IX). Most of that is usenet (http://www.top1000.org/top1000.current.txt look for 'tweaknews') but well over a gigabit is DSL end user traffic and some hosting. Those boxes cost in the order of 7000 euro's a piece, and are about as stable as a cisco running an current IOS (not as stable as you'd like). 7 grand buys me a single linecard for a 7200 on the secondhand market, and no 7200 will do as much traffic.

    Cisco and Juniper: start getting scared *now*

    1. Re:7200? How about replacing big iron? by saridder · · Score: 1

      Anyone knows that they wouldn't buy a 7200 for that kind of traffic; they'd look at a 7600 or higher. It's like saying my desktop PC can't run an enterprise ERP system. Duh.

      --
      --- RFC 1149 Compliant.
    2. Re:7200? How about replacing big iron? by mlyle · · Score: 3, Insightful

      Right; the parent's point is that commodity hardware is even threatening the high end (e.g. above the Cisco 7200 mentioned in the summary).

      Of course, lack of support and other issues will keep this away from the enterprise for the foreseeable future-- but this could make sense for a lot of startups with specialized needs or wishing to push a lot of traffic on the cheap.

    3. Re:7200? How about replacing big iron? by burne · · Score: 1

      Guess what would be the main consideration for a company pushing 4.5-6Gbit/s of data every day while a customer pays 7.50 or 10 euro's a month for his unlimited usenet account?

    4. Re:7200? How about replacing big iron? by necrogram · · Score: 2, Insightful

      I got a few concerns about diting my cisco and juniper boxen. I've blown a sup on cat 6000. for those of you not up on your cisco slang, a sup is your supervisor engine, analogus to a motherboard/processor pair. two thumb screws, one console cable and 10 minutes later. i was back on line. I cant see swapping out x86 platform that quick. I dont see something like statefull switch over in an x86 style platform. the hardware/software intergration for that is absolutly sick. while on the topic of x86... I peer one of these guys up to a new AS or VRF and suck down a larger BGP table, is it going to pause forwarding and routing while it does a memory swap becuase its underlying os wants to do memory managment buisness as usual style? I'm not knocking open source, but wanting to set your sights on the upper end of the router segment, you need to look at why cisco and juniper are that segment. If you have a need to sustain 4 to 5 gig of routing performance, you're probably going to need more than a routing table

    5. Re:7200? How about replacing big iron? by buddha42 · · Score: 1
      My former employer is using three relatively simple Tyan dual Xeons with a couple of Syskonnekt cards to shove 4-5 gigabits per second of traffic over the internet (yes, full routing, and over 240 peers on AMS-IX and NL-IX). Most of that is usenet (http://www.top1000.org/top1000.current.txt look for 'tweaknews') but well over a gigabit is DSL end user traffic and some hosting. Those boxes cost in the order of 7000 euro's a piece, and are about as stable as a cisco running an current IOS (not as stable as you'd like). 7 grand buys me a single linecard for a 7200 on the secondhand market, and no 7200 will do as much traffic. Cisco and Juniper: start getting scared *now*
      a 7204VXR with a G2 could do that. A G1 could probably just barely make it, since the spec it at 1GB of 64kbyte packets. I don't think your horse porn (sorry usenet) is exactly in the voip category. A G2 would have no problem. Although to be honest, at that level most people would run a 7600 or a 6500 depending on port density.
    6. Re:7200? How about replacing big iron? by MooUK · · Score: 1

      With cheapish commodity hardware as this suggests, you'd have an entire duplicate box or three and still be saving money.

    7. Re:7200? How about replacing big iron? by necrogram · · Score: 1

      saving money isnt the only factor here. if your box is routing that much traffic, you're going to have a few populaed interfaces. Have fun swapping that out. At that size packet switchig speed isnt the only factor. servicability and redundancy are the other. The 7200 series is just two thumb screws. platforms like the 6500/7600 and above, you stick two sups in it. and on a 6500/7600 you can rout 20Gb/s of voice traffic during a sup failover, and not incurr jitter on packet of the call.

    8. Re:7200? How about replacing big iron? by saridder · · Score: 1

      Good point, but most of the networking industry moved from just passing packets fast to doing it intelligently with things like integrated QOS, Security, etc., which keeps most of the routing companies from commoditizing their product. And as networks become more and more intelligent, such as offloading basic or repetitive tasks from servers and applications, networks will continue to not commoditize. Historically, any company that tried to commoditize routing/switching died as customers don't see any value in it. There are some in the 3rd world that are seeing success (Huawei), but for the most part they are niche players that probably wouldn't last more than a few years going off past history.

      --
      --- RFC 1149 Compliant.
  17. Oohh, Vyatta by creepynut · · Score: 2, Funny
    "Initially, we believe that the x86 PC running Vyatta -- given the range"

    Reading from a distance, I thought that said VISTA, not Vyatta :)

    I was starting to think that Vista had lost so many features that the only thing it was good for was for setting up a really, really expensive router.

  18. Other OSS solutions by nurb432 · · Score: 1

    There are several other OSS solutions that can do this.

    But good luck getting support at 1:30 am when the thing goes wierdo on you and you need to reboot the thing, 500 miles away..

    --
    ---- Booth was a patriot ----
  19. heh by Anonymous Coward · · Score: 0

    So i was reading over the documentation for this product, what a headache, looks like it was to be just like cisco in the command line.
    for anything low range to enterprise level, I dont understand why they would choose this product over openbsd.

    Configuring firewall rulesets for this software is just silly, whereas pf is nice and intuitive and actually makes sense.

    Nice idea, but again i agree with the earlier post about port -> port speeds in high end/enterprise applications, you're going to have some difficulty finding something as powerful as a cisco/juniper/whatever that will fit into a 1U space.

  20. Netgear by RickBauls · · Score: 1, Informative

    Just in case anyone was wondering, there are other routers that are open source. I think all of Netgears routers firmware is open.

    1. Re:Netgear by Thundersnatch · · Score: 2, Informative

      FYI, we're talking about "real routers" here... routers that speak BGP and other dynamic routing protocols to link sprawling multi-site networks with leased lines and VPNs. Enterprise-class stuff.

      By comparison, the Netgear, Linksys, D-Link, or whatver else you picked up at CompUSA are not "real routers" at all, as they only use simple NAT and static routes with 2-3 interfaces at most.

    2. Re:Netgear by ruckc · · Score: 2, Informative

      I believe he was referring to netgear's "REAL" routers, they offer some small business routers that are bigger badder than the ones they sell for home use. http://www.netgear.com/products/business/prod_vpnr outer_wired_security_sb.php

    3. Re:Netgear by fdawg · · Score: 1

      Netgear, IIRC, makes L3 switches that are very proprietary (and horribly unstable). I've used their gigabit offering (GSM*some bunch of numbers*) and it would barf at 10Mbit/s of multicast.

    4. Re:Netgear by Thundersnatch · · Score: 1

      Umm... note that even Netgear calls thes "VPN Firewalls", and not routers. Yes, they are technically routers in that they route between a single LAN and the internet. But the functionality and performance differences between one of those Netgears and even a fairly inexpensive enterprise router like the Cisco 2800 is similar to the difference between an ultralight aircraft and a Boeing 737.

    5. Re:Netgear by BrookHarty · · Score: 1

      F5 makes some nice OS based routers. The ones I have are using Linux based, they switched from BSD, but from the GUI you wouldn't ever know.

      Plus with F5 based in Seattle, they get to have nice onsite support for the big players. Cost and performance wise, F5 is doing pretty well with open source.

    6. Re:Netgear by ruckc · · Score: 1

      Umm, according to their website they are `VPN Firewall/Routers`. Heck, even the url i provided in my previous post includes `router` in it.

      I would also just consider the proper comparison as being between cessna, two seaters and a learjet as a better description. Just slightly bigger but quite a bit more capable.

    7. Re:Netgear by RickBauls · · Score: 1

      Wow, I didn't quite expect the to erupt into a flame war...

  21. ISP-grade by nurb432 · · Score: 1

    Or a large businesses data center.

    Don't kid yourself into thinking FreeSCO or IPcop, or monowall, etc can hold up with the big boys.. Sure, home, small and ( perhaps ) medium businesses could get away with it, but not the high end needs a of a large company. Between speed, and size and heat and support of the pc that can get the job done *reliably* its best to stick with the ciscos of the world in that case.

    Be careful who you say is pushing the hype..

    --
    ---- Booth was a patriot ----
  22. Re:Who needs it? by Anonymous Coward · · Score: 1, Insightful

    who the hell modded this up? the routers described in the article and the pissweak nat-in-a-boxes that parent speaks of are so dissimilar it's not funny. -1, clueless idiot talking about things he knows nothing about

  23. re by brennz · · Score: 1

    If Vyatta is the "dawn of open source networking" then who the hell are these guys?

    1. Re:re by ehrichweiss · · Score: 1

      The Tony Orlando of open source networking???

      --
      0x09F911029D74E35BD84156C5635688C0
    2. Re:re by Anonymous Coward · · Score: 0

      A vision from Vyatta's future?

      I looked over their lineup earlier this year ... strong advocate of OSS I am, but at those prices, I'll go ahead and roll my own, thank you very much.

  24. Re:Yawn. Slow news day? by alienw · · Score: 1

    Bullshit. Even a 200 MHz MIPS chip gives pretty shitty routing performance -- just look at a WRT54G router. Mine goes up to 100% cpu usage with a single SIP call. That router of yours would choke if you had more than one or two users or you were running BitTorrent or something. A Cisco 2500 won't. That's the real difference.

  25. Does this have a future? by Anonymous Coward · · Score: 0

    Not many people are going to run out and implement this. That's OK as long as there is some group of users who are over or under served by Cisco. In that case this could be a disruptive technology. Disruptive technologies start in niches of the market that the market leader doesn't care about (maybe in the third world for instance). The technology develops to the point where more and more users are attracted to it. The market leader retreats up-market where the big profits are anyway. Eventually, the disruptive technology becomes good enough to meet the needs of the top end of the market and the old market leader is finished.

    Granted this OS router seems a bit lame right now but I wouldn't write them off forever.

  26. Consider that even a $1K router is silly..... by postbigbang · · Score: 1

    Yes, it's nice to exercise code. A nice $1K router can be had for about $45 in the form of a Linksys home router with some nice kits put on them. Not the fastest, but if you're connecting to a GBE or fiber connection, then you need some speed. All else has as the least common denominator-- the mating link speed. This is usually something ugly like several Ts or at most a DS3. Few orgs get nice fast connection speeds so one is gilding the lilly to think otherwise.

    --
    ---- Teach Peace. It's Cheaper Than War.
  27. It depend on the connection. by Anonymous Coward · · Score: 0

    500-1.2 g machines from VIA are good enough for 100 speed networking with Linux installed on them.
    1000 speed networking 2g machines become a requirement. Still dual processor VIA chips will hold this without much problem. These chips don't get that hot and parts are simple to replace. Ok if your using AMD or INTEL standard chips yes problem.
    10000 Cisco the big boys. Nothing I know of has the heat low enough other than custom hardware. I don't know where sparcs fit here. Never checked there thermal. Even this level might be takable.

    Not alot of companys use 10000. Cost verse access to parts. VIA wins for most of the low end routers. AMD and Intel need to release even if slow cold processors. Ie processors that don't need heat sinks to compete in this market. So adding a heat sink is over kill and makes sure the processor cannot over heat.

  28. PC's just aren't ready by xiana · · Score: 1

    I recently looked into building a PC based router after our NPE-300 board in our Cisco 7206VXR started flaking out.
    While I'm sure it can be done for a T1, you sure as heck aren't going to build an effective DS3 or higher router on a PC.

    The biggest problem right now is lack of PCI ATM adapters. I recently had CDW look into this for us. Apparently IBM used to make an ATM adapter, and HP currently does but is only supported for HPUX.

    As much as the hacker in me would love to put together a DS3 capable, PC based router running Linux, without proper hardware and driver support, it's just not going to happen right now.

    But hey, I hope I'm wrong... If someone can point me in the direction of an ATM adapter with Linux support, great ! I'll start hacking away... Until then, I'll sleep soundly at night knowing that if something blows up and it's an emergency situation, Cisco will ship out parts by start of next business day, in a worse case scenario.

    1. Re:PC's just aren't ready by doublebackslash · · Score: 1

      Here is a page with a few promising items: http://www.sbs.com/products/family/110/ I don't know too much about more than T1s (yet), but that looks about right to me. Let me know if it is of any use to you.

      --
      md5sum /boot/vmlinuz
      d41d8cd98f00b204e9800998ecf8427e /boot/vmlinuz
    2. Re:PC's just aren't ready by Kadin2048 · · Score: 1
      I have not used anything from this company at all, but I just was reading their web site after seeing it further up in the thread, and thought maybe it was what you're looking for.

      Check out:
      http://www.imagestream.com/PCI_1000.html
      The PCI 1000 series consists of WAN adapters that can be used in Industrial Series routers or OEM products running Linux. The 1000 series includes high-performance ATM adapters with one DS3/E3/J2, OC3, or OC12 interface. 1000 series cards comply with ATM Forum specification UNI 3.1 and TM 4.0. The adapters are based on advanced ATM segmentation and reassembly controllers (SARs) that are designed to optimize PCI bus utilization for increased performance with small packets. 1000 series adapters segment and reassemble AAL0, AAL3/4 and AAL5, and the cards manage and transmit raw cells, AAL1 and AAL2.
      This company makes a whole line of Linux-based routers, and as such has a bunch of PCI based cards for them, for a variety of backhaul protocols. I can't tell whether they're getting them from somebody and rebranding them, or if they're actually custom jobs and they've written their own drivers.

      At any rate, since their main product is Linux-based, they have to have Linux drivers for the cards somewhere, either with the cards or distributed with the routers you're supposed to put them in -- how easy it would be to take one of their cards and work it into your DIY solution, I have no idea. (They say it will work as part of an "OEM" product...convince them to send you a 'demo'?)

      Maybe if you called them up and sounded potentially interested in one of their big enterprise routers, but said that right now you couldn't afford it, and just wanted to get one of their ATM PCI cards for your existing Linux solution ... (insert sob story here) they'd help you, make sure you got the right drivers, etc.

      Hey, it's worth a try, right?
      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    3. Re:PC's just aren't ready by Anonymous Coward · · Score: 0

      It looks like they have a relationship with Sangoma for at least T1 and T3 support. Don't know about ATM support. Here's a link on Sangoma's site:
      http://www.sangoma.com/main/products/wanpipe

    4. Re:PC's just aren't ready by xiana · · Score: 1

      Awesome ! Thanks for the link. I'll order one of their cards and see how things go.

    5. Re:PC's just aren't ready by Morty · · Score: 1

      With the increasing popularity of MPLS, WAN interfaces are being replaced by ethernet, anyway.

      But if you really need ATM, Fore/Marconi/Ericsson sells Forerunner OC-3 and OC-12 ATM NICs. The higher end cards support a lot of VPi and VCi numbers. I have been happy with them under Solaris. Linux is not listed as a supported OS under the datasheet, but then, that's not surprising.

  29. Can we slap ourselves? by Triode · · Score: 2, Funny

    We (by that I mean geeks in the networking world) have been doing this for years...

    Why can't we think of ways to profit from this as these companies do??

    Damn, should have gone back and gotten that MBA...

  30. Don't think you'll find one for $45 by Kadin2048 · · Score: 1

    I'm pretty sure the $45 Linksys routers (and they're more like $70 now, for the ones you can flash the firmware on and have a significant amount of RAM: the "54GL") don't have GigE on the LAN side; I think they top out at 100BT. So if you just want an uplink router, they're probably fine once you get them patched up to your liking, but if you want your local net to be fast, they're not going to cut it.

    A router with GigE on the LAN switch and a reasonably fast uplink, and configurable software (not a braindead web interface) is going to put you into the low end of 'real routers' I think, or at least on the very high end of consumer plastic-boxes.

    While I think the guy in the article was engaging in a certain amount of hubris when he compared their "softrouter" to something like the Cisco 7200-series, I do think there's a potential market in between the upper end of the current SOHO routers and switches, and the bottom end of the enterprise market. A powerful, fast router that was easy to use (for someone coming from SOHO boxes) but which offered expandability and the ability to grow with a not-so-small-anymore business, could find a healthy niche.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  31. Open source? Where is it? by Anonymous Coward · · Score: 0

    I checked their web site and can't find the source. They're using GPL code and heavily advertising "Open Source." So where's the source?

    1. Re:Open source? Where is it? by Anonymous Coward · · Score: 0
    2. Re:Open source? Where is it? by MooUK · · Score: 1

      The GPL doesn't demand that the software be available to everyone - just everyone who has the binaries. (Yes, that's simplifying things a bit, but its close enough...) Hence, not having the source available publicly on their website is not breaking the license.

  32. Re:Yawn. Slow news day? by Anonymous Coward · · Score: 0

    Yeah... you can do some heavy duty routing on a 2514... what with the 10 mbit ethernet interfaces and all.... NOT.

  33. You are a moron. by Anonymous Coward · · Score: 0

    A cisco 2500 will lock up hard and require rebooting when faced with even piddly amounts of traffic. They are complete shite. At least low end junipers and high end ciscos reboot instead of locking up when they have to do real work. Off the shelf servers have been EASILY able to replace cisco/juniper gear at 20 times the price for years.

  34. It won't scale by AaronW · · Score: 1

    A PC platform will not scale like a decent router will. The memory latency becomes the bottleneck once you start thrashing your CPU cache when you have a lot of routes or ACLs. For small setups, it might work, but it will not compete with dedicated hardware solutions once the complexity grows.

    I have implemented routers, and the biggest bottleneck is typically memory latency. Once the routing tables grow beyond what will fit in the cache, the latency kills you. Dedicated hardware routers are designed with this in mind, often with multiple banks of low-latency memory or CAMS.

    Try to handle 1M packets per second with 100K routes, MPLS VPNs, ACLs, policy based routing, QoS, policing, marking, reverse path forwarding checks, etc. and it will fall apart. Plus it has to keep statistics on everything. All of that will quickly exceed the memory bandwidth available on any PC platform.

    A decent router can do all of this and run at gigabit speeds or more. Add to that all the various interfaces that are available and the much higher port densities.

    -Aaron

    --
    This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    1. Re:It won't scale by sophanes · · Score: 1

      I concur, a router based on a standard PC architecture simply doesn't scale. For this reason, most high-end routers push as much of the work as possible out to the line cards, which are interconnected with a dedicated high speed backplane (often based upon a crossbar or 3D-torus).

      Also, as the parent noted, doing longest prefix matching in anything other than hardware is a nightmare (and it's going to get worse with IPv6). Still, it seems that Vyatta is aiming more for the low/medium end of the router market so they may be able to avoid these problems.

    2. Re:It won't scale by mi11house · · Score: 1

      Damn right.

      I used to work at a company that made the *test equipment* for big-iron routers. In other words, generated the packets at rates that made them scream for mercy. We used ASICs to serialize/deserialize onto big fat data buses and FPGAs to do stuff like CAMs, massively-parallel matching and byte sweeping. We used the biggest, baddest FPGAs Xilinx et al had to offer and had them bulging at the seams.

      You won't get even close to saturating/dealing with a "serious" link (i.e. OC-12 or more) without being able to distribute the effort around the place - i.e. L2 framing and L3 inspection on a line card and massive backplane capacity. THEN you can use your general-purpose CPU to make routing decisions etc. If your Xeon or whatever has to get interrupted on every packet, or you have packets trying to make their way at line rates across a general-purpose bus like PCI etc, you're gonna hit a problem shortly after adding your second line card to your 4U Dell.

      By the way, a few years ago we used our gear to do some tests on PC-based 155mbps ATM cards. On a "state of the art" Pentium III we got packet loss rates of 5-10%. That's with ONE card.

  35. It's a fluff piece, what did you expect? by SuperBanana · · Score: 1
    We shouldn't even be giving them the press!

    Techtarget's article is the equivalent of Father and Son at the baseball field. Dad throws 'em nice and slow, and Junior hits 'em every time.

    To call this "press" is an insult to news media everywhere, even by their standards. This is nothing more than a fluff piece by Techtarget (and Techtarget isn't "media"; they're basically a "whitepaper rehasher") asking him exactly what he wants to be asked.

  36. Software (config file) compatibility??? by Anonymous Coward · · Score: 0

    Can it understand a text file full of Cisco IOS commands as its config file?

    Or do I have to learn yet another Martian language's arcane vocabulary and obtuse syntax to be able to program it?

    I already went thru hell to learn Cisco's brain-hurting IOS.... I don't want to learn another.

  37. Re:Yawn. Slow news day? by El+Torico · · Score: 4, Informative
    PCs running tuned linux or BSD kernels work great for anything but ISP-grade stuff.

    The first Juniper routers were "Olives", which were PC's running modified BSD. JUNOS is BSD based.
    UUNET, IMHO the greatest ISP ever, first tested them in 1998 or 1999. CISCO had annoyed UUNET with poor service, so UUNET helped bring Juniper into the market. Yes, I am former UUNET and proud of it.
    I found an interesting link to Olives at http://juniper.cluepon.net/index.php/Olive.

    --
    In the land of the blind, the one-eyed man is usually crucified.
  38. More FUD from someone pet project by jbossvi · · Score: 4, Informative

    This keeps coming up every 6 months or so. To rehash it for you:

    1) performance wise a 6x PCI-X motherboard is rare and commodity computers are not built for the buses to independantly talk to each other without invoking cpu.
    2) feature wise you Have to have a RTOS or bad things happen when you try to implement QOS. speaking of features they have libraries full of books that talk about the *thousands* of features technologies that real routers implement (its hard to do that most companies spend tens/hundreds of millions to do this). implementing a few protocols/nat/firewall does not a router make.
    3) If you actually have been involved with these things you would know:
        -ds3/oc3/oc12's are not cheap... phone company bills of $100k a *month* is very common.
        -a couple network engineers $100k/year each
        -dedicated power/colo space/ups/generators $50+k/year
        -SLA's and peering arraingment... $$$
        -uptime to your customers measured in seconds of uptime (revenue $200+k/MONTH). ...... AND you want to save $30k by using a #@$%#$%#$% software router running on a DELL?????

    really, try explaining that to the CEO after the site has lost $10k/HOUR because something wonky is going on with the cpu or the memory oorrr it could be the kernel, I dunno I just rebooted the thing "cuz that usually fixes MY problems"... bye bye SLA.

    --jboss

    1. Re:More FUD from someone pet project by DigiShaman · · Score: 0, Flamebait

      You just bitch-slapped this article. Case closed. It's done, put a fork in it.

      Well done! Good job!

      --
      Life is not for the lazy.
    2. Re:More FUD from someone pet project by MikeBabcock · · Score: 1

      I'd love a list of those protocols, seeing as I use Quagga (previously Zebra), ip (the tool) and QoS/TC tools on Linux regularly. I've had many Cisco certified admins point out that many of these tools are more flexible than their Cisco counterparts.

      PS, last I checked, you can get a 100Mbit feed for $1k/mo here in Ontario Canada if you look hard and routing those packets won't require a PCI-X bus at all. If you're planning on doing very large bandwidth levels, then you're not really in the "midrange" router market at all, are you?

      --
      - Michael T. Babcock (Yes, I blog)
    3. Re:More FUD from someone pet project by 99BottlesOfBeerInMyF · · Score: 1

      performance wise a 6x PCI-X motherboard is rare and commodity computers are not built for the buses to independantly talk to each other without invoking cpu.

      Hmmm, I'm not sure this is a large impediment. Getting some custom hardware to run your open source router on is not all that hard and companies can certainly use this software to sell the hardware, while someone profits from the support and custom dev (yeah tiny market, I know).

      feature wise you Have to have a RTOS or bad things happen when you try to implement QOS.

      In the midrange market, I'm not sure this is really true.

      ...speaking of features they have libraries full of books that talk about the *thousands* of features technologies that real routers implement...

      I'm curious about the feature set as well. Some places really don't use anything but the basics, but a a significant number do. I'm not sure what all this software is supposed to be providing. Also, a lot of the market has moved to management tools that require NetFlow or the like and beating Cisco and Juniper for integration with this is going to be hard. Still, there are a lot of routers out there from other companies that provide a subset of features and they do alright.

      ...implementing a few protocols/nat/firewall does not a router make.

      Having worked in the routing industry, I can tell you some of the big players were very concerned about open source routing, to the point of hiring the developers just to get them to stop working on it. I think it could be a viable business strategy. I guess time will tell.

  39. *sigh* a solution in search of a problem. by l33t-gu3lph1t3 · · Score: 2, Informative

    It'll never, EVER challenge Cisco in the big iron market. Why? Simple. No IT manager has EVER been fired for buying Sun servers, Cisco routers/switches, or IBM PCs. Big iron isn't about open source. Big iron is about triple-redundant reliability, service contracts, and brand trust.

    --
    ------- "From bored to fanboy in 3.8 asian girls" ----------
    1. Re:*sigh* a solution in search of a problem. by MooUK · · Score: 1

      It isn't supposed to; as I understand, the idea is to compete with low-mid to mid range products.

  40. OSS is great, but not for everything... by msimm · · Score: 1

    Sometimes purpose built products simply make more sense. Lets skip the obvious reasons like tested, reliable (hardware) platforms, extensive QA, depending on the user-base even more extensive discovery and bug reporting.

    Na, lets forget about the piddly stuff. I work at a systems admin: do you really want to build a product without the aforementioned benifits (hey, your production systems is now doing beta testing!) and take the heat for to save a few dollars?

    Sure, I'm sure it works pretty good. It might even be the perfect solution for a lot of scenarios. But when you build off a non-supported OSS projects *you* become support. *You* take the blame. If my Cisco router goes south (not that I've ever had that happen) I call technical support and no matter how little my CEO might know about hardware its now *Ciscos* problem.

    That said we do use a lot of OSS software, even in production, but where I feel strongly about 'appliances' is in task-specific applications, ie: router ios's, loadbalancers, firewalls, switches (sure, as in routers).

    Besides, any of you who work as system admins know that Radware hardware has more bling. :) I walk past racks everyday and you can see the people who spend the money to do things right (standardized hardware, good cable management, serious components, nicely organised) and the people who cut corners, because the people who cut corners are the ones who are there, fixing problems while that rack of X4100's with the database using the dual-channel fiber interconnects and the managed gigabit switches and the shiny firewall appliance just kind of clicks along.

    If that sounds like a rant its only because we've cut some of these corners and I've had to work pretty hard to start getting things turned back around (commodity desktop building oem server vendor > specialized oem server vendor (the kind that knows what Linux is and installs and burns in your OS) > Sun/Dell/HP/[Insert favorite vendor here]) all the while convincing the company I work for that saving a few dollars to build a firewall on last gen hardware didn't make as much sense as buying a documented, supports and stable 'boxed' firewall. Not to mention the rest of the network. So ya, I'm a little bitter. :)

    --
    Quack, quack.
    1. Re:OSS is great, but not for everything... by L.Bob.Rife · · Score: 1

      As a counterpoint, I've had great success with software firewalls. The only hardware firewall I've dealt with extensively is Sonicwall, and to me its a nightmare trying to set it up properly and have everything locked down.

      Maybe I'm an idiot, but IPCop is much much easier to deal with. To me, its a lot more secure to have something very simple and obvious, than complex and confusing.

      Last year my small company was faced with a need to upgrade firewalls to accomodate more VPN tunnels to link home offices. We could have paid $3500 for a hardware appliance, or used one of the spare computers we have and set up a software firewall. We "cut corners" as you put it and I couldnt be happier. After a year of easy management, I'm ready to dump the Sonicwalls I have to manage and replace them with low power mini pc's and IPcop.

    2. Re:OSS is great, but not for everything... by msimm · · Score: 2, Informative

      FTR, if you can manage the support and deal with irregularities as they might come up, as it sounds like your company probably can, I totally agree. I'd even go so far as to recommend ClarkConnect, personally.

      But these still don't deal with the issues of hardware/platform stability (yes, its a *lot* easier to design, troubleshoot and design driver modules if you control the platform first), QA (testing commercial *before* sending a product out the door), organized 'knowledge bases' (assuming your appliance has large enough penetration), commercial support because things *will* go wrong and if your running mission critical applications behind your 'appliance' you'd better be able to get fixed fast and have the CMOA part dealt with too (after all, the large the company the less forgiving they can be for mission critical application/server/network downtime).

      So, ya, if you've got the wiggle room and need to allocate re$ources elsewhere and have someone onboard who's stable (hate to inherit someone elses 'customized' framework) I think its very useful.

      But if your company/job/livelyhood/client-base depends on it I feel pretty strongly about using something start to finish purpose built.

      As an aside I did a lot of research on firewall appliances before we purchased our own and of the sys admins I know Sonicwall was the one product that almost unanimously was not recommended. So its probably not just you, just bad luck. We've gone with Astaro, who aside from making a software distrobution also does build an appliance. Its Linux, so I know if things every really went south I could get my hands dirty and make things right, but I don't and shouldn't have to. I can dynamically update rules, add nodes, do hot/cold or hot/hot failover and I don't have to string together a bunch of software applications of varying quality and flexabilty.

      And best of all, although possibly alarming, if I should ever leave the company whoever picks up my work will be able to quickly learn to manage the software. The network doesn't skip a beat.

      Anyway, I'm not trying to argue against what your saying. If it suits your needs use it. You know your company better then I do. I work for a medium sized sompany and some large (fortune 500) sized clients. So we've got a little room in the budget (of course its always a fine line) and certainly a justified need. I don't know if you've ever had to sit in a meeting and explain your network topology and how you handle things like redundancy but when you start naming OSS products outside of say the top 10 you get some pretty disarming looks. :)

      Enjoy IPCop. I'd say take a look a ClarkConnect but until they get the rules/insert method updated I won't touch it, they were using Shorewall and even a minor change (like say opening an FTP port for a new client) requires a Shorewall/IPTables restart (or a CLI insert, but I always though those were more prone to error...as in sleep deprived, up at the colo human error then a clean GUI) and that, at least in my case, is totally unacceptable. Maybe IPCop has dealt with this differently since I last used it, but on the fly changes should be the first priority of any serious firewall solution (well, after overall system security).

      Anyway, I'm just throwing out my $.02. You certainly don't sound like an idiot.

      --
      Quack, quack.
    3. Re:OSS is great, but not for everything... by msimm · · Score: 1

      Speaking of sleep deprived, I'm hoping you can read through all the spelling errors. :)

      --
      Quack, quack.
  41. Consider what a router does, even with IPV6 by postbigbang · · Score: 1

    Did I say IPV6? Shame on me.

    It would be nice to have need for internal routers for many of the tasks that people think they need routers for. Yes, a fatuous ARP table is a beautiful thing if the router can deal with other things. There's a tremendous amount of power in pushing the routing/bridging strength to the edge, and keeping the height low on the hierarchical models; it's more manageable.

    But the little stupid brouters (GBE switches at this rate) are really nice. Add in some nice filtration tables to keep 0wn3d machines off the backbone and life is good. So the eBay cost is dirt for a Linksys, or by a DLink or Netgear or SMC or who cares programmable router. For 1/10th of the effort required to get this other stuff compiled and stable, you can take what's already there and have lunch instead of debugging maniacal routing code that's trying to be stapled into a 1U.

    --
    ---- Teach Peace. It's Cheaper Than War.
  42. So buy support from someone else... by Penguinoflight · · Score: 0, Flamebait

    Might as well pick choose your own professional consultant rather than get stuck with some indians answering phones for a big router company. Is this really hard to see?

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
    1. Re:So buy support from someone else... by winkydink · · Score: 1

      Yes, it is. What's the escalation path for your professional consultant?

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    2. Re:So buy support from someone else... by redcane · · Score: 1

      Escalation path:Fix it or under the contract that has been negotiated you owe a penalty large enough to make you beg to cisco to fix it for you, and to take your first born son as a trade. The risk is now all on the professional consultants end, and if they want to call in some favors/friends/pay the "world class" guys to fix it, they can. Of course, the sort of professional consultants that would enter this agreement, presumably are really quite skilled in the area. But really, this is about risk mitigation, you just need to prove to your boss, it wasn't your fault something stuffed up. While ever someone follows "best practice" the beaurocracy won't fire them, but they won't innovate or try to do better than "procedure" either.... Whats the solution when you have to call the support line 5 times to get off hold and talk to someone who can understand what your saying? Or they want to treat you like you don't know what your doing, and that your problem couldn't possibly need escalation because you haven't run through all the suggestions of likely fixes (which you already tried *before* calling), and which you know do not apply to your problem.

    3. Re:So buy support from someone else... by winkydink · · Score: 1

      good luck finding an sole proprietor who's going to sign a contract with a non-performance penalty. There's enough work out there, that the "good ones" you refer to don't have to. So you're stuck with a mediocre consultant or no teeth for non-performance. No, it's not just about proving it to your boss. If your loss is substantial enough, it may be about proving it to your shareholders. If you drive share price down, they have this nasty habit of litigating.

      In most caes, the CEO of a large company doesn't give a rat if you have to wrestle with customer support to get results. He most likely views that activity as "doing your job".

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  43. Re:Yawn. Slow news day? by Anonymous Coward · · Score: 0

    A Cisco 2500 won't? Are you kidding? The 2500 is the most ancient piece of shit around. I simply can't believe people still use them. What is it about a 20MHz 68030 that makes you think it'll beat a 133MHz MIPS, let alone a 200MHz MIPS processor? Sure, some of the software releases from Linksys might have performance problems, well most of their releases do. I think you'll find that the 2500 keels over far sooner than processor with 10 times the speed, given decent software. I think that happens somewhere between 4 and 8 simultaneous voice calls.

  44. niche by Neuropol · · Score: 2, Interesting

    It's very parallel in it's nature in that a small networking company could present this as a cost effective option. I see how a small networking consultant company could actually push this towards the small business level. But I'm doubtful it could ever be presented at the public/community level for use in schools or public wi-fi rest areas when the state lays out stipulations regarding only accepting bids from Cisco based numbers and Cisco certified installers? More or less, mandating that tax payer investment for this massive scalability be present. Often times, in these areas, that is ten-fold overkill. So there is the need, but I'm afraid that Cisco's name is so far embedded in corporate and state america, it's going to be a tall order to ever penetrate that market. Bringing this comment back to the small business. If a consultant can convince the client that this is a viable router to placing thier 20-something client station network on, then, yes, it has a niche.

  45. This isn't news. by rnxrx · · Score: 3, Insightful
    I think we see some version of this article every few months - yet another revelation of an open source package that can turn PC's into routers. This isn't news. There have been various shapes and forms of routers on *NIX platforms for many, many years. Some of these platforms served (and still serve) as reference implementations of certain routing protocols.

    The common responses on here seem to revolve around the inability of PC hardware to handle high bandwidth. To an extent this is necessarily true. A general purpose PC is going to rely on its CPU to handle each packet traversing the box. Processors are fast and cheap and becoming faster and cheaper as time passes. Most commercial router vendors realized quite a while ago that any architecture whose perforance is based on a single, centrl CPU inherently represents an eventual bottleneck and thus a serious challenge to scalability. As such, most commercial routers have moved to a model where forwarding is pushed as far as possible from a control plane that is as discrete as possible.

    In other words, if we push the actual heavy lifting of forwarding out to distributed components (e.g. the interfaces themselves) then we're no longer left in a situation where our BGP process is vying for cycles and memory access with packets in transit. When properly implemented this means that I can be moving huge amounts of traffic through my router without interrupting network control traffic, management of the box, etc, etc.. It also means that by distributing packet switching they can hit massive performance levels with a comparitively modest CPU.

    At the high end with Cisco and Juniper you're paying for the development of some exotic ASIC's and some even more exotic interface hardware. You're also paying for the capability to support high density - PC platforms aren't going to support tens of 10G or hundreds of 1G interfaces any time soon. The capacity for redundant CPU's, stateful failover, etc is also worth remembering.

    At every level of Cisco and Juniper hardware you're paying for the ongoing development and maintenance of a highly complex codebase full of features that just aren't practical (or, in some situations, possible) for the OSS community to implement well. Implicit in this is a huge system test and regression faculty.

    I've used and deployed open source routers up to OC3 bandwidth. They worked and, for the most part, worked well when faced with relatively simple networking tasks - multihoming enterprises to the Internet, basic WAN routing, etc. My observation has been that these platfoms start to fall apart when faced with requirements for complex routing policies, fancy QoS, MPLS, etc.

    There's a definite place in the world for PC-based open source routing platforms - particularly at the edge of larger networks or in the midst of small and medium sized ones but I don't think Cisco and Juniper need to worry about being rendered completely obsolete any more than Oracle needs to worry about being driven completely out of business by MySQL or PG.

    1. Re:This isn't news. by Anonymous Coward · · Score: 0

      Nice writeup and it seems you put a lot of thought into it.

      There are several posts in this story that claim to be using close to commodity PC hardware and routing 4-6Gbps without any problems. They are not giving assumptions or theories like you are, they are actually using it for a solution right now.

      What percentage of companies are using more bandwidth then that AND using MPLS, elaborate QOS etc? Well maybe the non Cisco or Juniper route is not for them but I'd guess people that need that requirement is a very small fraction of a percentage of companies that have more general routing needs where it would work.

    2. Re:This isn't news. by rnxrx · · Score: 1
      A small percentage? Take a look at medium to large ISP's and larger enterprises. MPLS, QoS, high bandwidth and requirements for high density of 1G, 10G and SONET interfaces pretty much define many (most) of these sorts of networks.

      As for assumptions and theories - I run one of these networks in the financial services sector, including 2000+ network devices spread across several hundred sites and I've been involved with literally dozens of environments of similar and larger scale over the past ten years or so in the enterprise, carrier and public sectors. Within our network we use MPLS extensively and rely on complex QoS mechanisms. We push more bandwidth than many carriers. Downtime represents astronomical costs.

      If your measure of the success or utility of a routing platform is strictly how many packets it can move from one interface to another then you're not talking about real environments where people solve actual problems for actual money. The history of networking is littered with the corpses of companies with devices that were faster but lacked in stability, flexibility, manageability and vendor support.

      4-6 Gbps is plenty of traffic. I'll take folks at their word that these numbers are accurate (..though I've got serious doubts) but honestly the issue of a dozen or so boxes passing that kind of traffic in a vanilla IP environment positively pale in comparison to managing several thousand boxes spread across the planet.

      OSS PC hardware routers are a niche. Smart folks can build very useful routers in relatively small environments on standard commodity hardware. When faced with much larger environment with critical requirements for reliability and the very real issues of support, feature sets, staffing, management and ongoing operations costs lots of smart folks have also tended to realize that the several million dollar delta between an OSS solution and that of a major vendor is cheap in comparison.

    3. Re:This isn't news. by Anonymous Coward · · Score: 0

      I run one of these networks in the financial services sector, including 2000+ network devices spread across several hundred sites

      So everyone of those hundreds of sites (assuming they are a remote office) need 1G, 10G and SONET interfaces. Hundreds of a minimum of 1G connections for a company? Where are those hundreds of connections going? If that is case, You have very heavy requirements. I am not doubting your scenario but let's be realistic, that is so far from the typical requirements to even be considered at the same level.
      You mention mid and large ISP's. I'll give you that but guess what, each of those ISP's is probably providing pieces of that bandwidth to the types of businesses I am refering to who have much lower needs. I worked for one of the largest Airlines in the world and even major hubs (airline hubs, not network hubs) were connected back to the mainframes with max 3Mbit and the entire load could easily be handled by a single T1 but a second T1 and router was for redundancy. The smaller airports like Buffalo, Clevland, Norfolk etc were connected with two 128 or 256. Yes we had offices and buildings in different physical locations that needed much higher needs not the airports and ticket offices.

      We push more bandwidth than many carriers.

      Again, you personal experience and background and size of your bandwidth needs are not what is being questioned. It is the number of people that have a need for anything even close to that. You are comparing apples to oranges here. For every company like yours, there are probably 1000-10000 that are not like yours and need a T1, T3 or equivelent max. Do you think any Wal-Mart, Sears, Home Depot, State Farm, Best-Buy etc.. has any more then that? I don't

    4. Re:This isn't news. by pe1chl · · Score: 1

      That is all true, but was it anywhere claimed otherwise?

      The article talked about midrange routers. Any modern PC can do what a 2xxx or 3xxx cisco can do. I don't know anything about 7xxx so I cannot make that claim.

      Also note that in many environments routers are used between LAN and quite slow WAN links, in the megabit speed range. No challenge for a PC.
      For fast (1G) traffic, switches are used.

    5. Re:This isn't news. by rnxrx · · Score: 1
      Not every site on our network requires 1G+ but most require the other features I mentioned (MPLS, QoS, etc, etc). Once again, though, the nature of my network isn't all that out of the ordinary for my industry. I could say the same about a number of other sectors. You're absolutely right that there are thousands and thousands of small networks for every big one but also bear in mind that when looking at the wider networking industry that big organizations also buy thousands and thousands of network devices.

      The airline and retail industries (as referenced in your post) aren't known for substantial bandwidth requirements to all sites. To take your specific airline case - the reason even your major hubs don't need much bandwidth is that the apps being supported are almost completely terminal based. The same applies to the hospitality sector and really any industry where lots and lots of locations have a relatively small number of users entering data into similar host-based apps. The funny thing is, though, that until recently the only way that these sorts of mainframe apps could be supported was either via thousands and thousands of square feet of aging IBM FEP's landing tons of tiny circuits linking them to terminal controllers or - in the last 10 years or so - via some kind of scheme to transport SNA traffic over an IP backbone. This usually implied DLSw+ and its associated support for SDLC, translational bridging, etc, etc. Things have obviously changed and gotten better as IBM started putting credible IP stacks and Ethernet interfaces into mainframes and PC's with IP and tn3270 clients replaced dumb terminals but these sorts of features (..including airline specific features in IOS) are what sold millions upon millions of almost comically slow and obsolete 2500 and 2600 routers despite being outclassed on most levels by cheap PC's with T1 cards and a BSD or Linux with gated/zebra/quagga/whatever.

      Once again, however, my point was that - despite the 4-6 Gbps cited earlier and numerous OSS performance endorsements on this thread - raw throughput alone offers a generally poor view of the capabilities or utility of a given router or switch platform. To draw the almost inevitable automotive analogy, if I'm presented with a heavy load to move across town I know that I'll need something with plenty of horsepower and torque to do so. Race cars have lots of horsepower and torque. Race cars make lousy moving vans. Similarly, the potential of an OSS routing platform to sustain gigabits of throughput (as referenced in your earlier post) isn't all that interesting as an abstract fact.

      The features that allow me to build a network of thousands of sites while maintaining rock solid stability, sane and predictable ongoing operating expenses and the ability to rapidly and easily adjust to changing requirements are those that make that network useful. These are the things that Cisco and Juniper do well - at the low end and the high end and these are the reasons why a completely free (as in beer) routing platform can be a heck of a lot more expensive than its multi million dollar commercial equivalent. I'd argue that this logic holds true even for many smaller networks. We didn't look to the competent (and fast) BSD routers of 10 years ago to provide channel attached mainframe connectivity and fancy SNA features over a WAN and we don't generally look at the OSS routers of today to provide fancy QoS, MPLS, complex routing policy tools and a host of other items that go well beyond pushing IP from one interface to another.

    6. Re:This isn't news. by Anonymous Coward · · Score: 0

      I see your point I guess.

      in the last 10 years or so - via some kind of scheme to transport SNA traffic over an IP backbone.

      "Scheme" is dead right (at least 5 years ago when I left there). We tested and used devices from multiple vendors trying to find something that was reliable. It was very hard to emulate what needed to happen in real life compared to what was supposed to happen on paper.

  46. Is OSR viable? by bec1948 · · Score: 1


    It's an interesting idea, and all but the troll comments are to the point and even trolls are perceptive.

    Most seem to be missing an important point. What's the company's business model? Free software with tech support for $500 per year? That's not a billion dollar idea. How about the point made that they intend to offer appliances and system blueprints?

    So, it's not really about reusing your old PCs, except for really small companies, start-ups or 3rd worlders. Vyatta readily admits that ultimate performance and absolute reliability does require very careful selection of components and careful engineering. Can it be done with OTS components? I think so.

    The product is essentially a Linux Kernel with a routing stack designed to run on an X86 processor based platform. Almost every network appliance I've studied over the past decade has been based upon the same concept. It's a recognized commodity HW plan, one that most companies are comfortable with, even if they're not aware of it.

    The question is whether they can produce appliances and reference platforms (tested HW configs) that can be replicated and whether these devices can be sold for less than what a "Name Brand" router costs on E-Bay.

    1. Re:Is OSR viable? by Anonymous Coward · · Score: 0

      This is how cisco started off, using off the shelf components. I think though from a performance point of view, it is hard to push these devices and cost of production is relatively high (depending upon how many you sell ofcourse). such an approach enables greater innovation and sharing of new ideas from the public domain ... (new router protocols anyone?)

  47. WideBand beats the crap out of Cisco by Rabid+Cougar · · Score: 5, Interesting

    Wideband makes Layer-3 switches that beat comparable Cisco routers hands down. With their nMU (pronounced "NetMU") it makes easy things easy and difficult things easy too. With their 28-port switches, you can get full-duplex, non-blocking Gigabit transfers on all ports simultaneously. And did I mention that they can even do Gigabit over CAT-3 and barbed wire? Also, if you use the nMU control your switches, none of them even need IP addresses. Good luck trying to hax0r a switch with no IP address. Throw in the fact that all their stuff is made in the USA (no off-shore customer support) and costs much less than comparable Cisco gear that doesn't perform nearly as well, and you have yourself a superior product. If you are expanding or replacing your network infrastructure, consider WideBand over Cisco. You'll be glad you did.

    ***Disclaimer***

    I do not now, nor have I ever worked for WideBand, but we use their gear where I work. BTW, there were some guys who ran a Cisco shop in the training class I was in that WideBand offered. Last I heard, they were replacing all their switches with WideBand gear. IMNSHO, WideBand is the best kept secret in networking

    --
    This isn't the sig you're looking for...
    1. Re:WideBand beats the crap out of Cisco by cyclomedia · · Score: 1

      holy shit, gigabit over barbed wire! Here in Yorkshire we have serious trouble getting decent broadband speeds, the prevailing theory being that it must run over the electric fences alongside the farm fields. Used to blame my FPS packet loss on sheep leaning on them.

      --
      If you don't risk failure you don't risk success.
    2. Re:WideBand beats the crap out of Cisco by cg0def · · Score: 1

      Sure Wideband is great but what does it have to do with the whole OSS router topic?

    3. Re:WideBand beats the crap out of Cisco by Anonymous Coward · · Score: 0

      The topic is about OSS Router AND Proprietary Networking.

    4. Re:WideBand beats the crap out of Cisco by digitalsushi · · Score: 1

      And did I mention that they can even do Gigabit over CAT-3 and barbed wire?

      Source?

      --
      slashdot: where everyone yells sarcastic metaphors to themselves to understand the issue
    5. Re:WideBand beats the crap out of Cisco by archen · · Score: 1

      I don't buy it either, but that's what the website says

      http://www.wband.com/Gigabit_Ethernet.htm

    6. Re:WideBand beats the crap out of Cisco by N3TW4LK3R · · Score: 1
    7. Re:WideBand beats the crap out of Cisco by lptp · · Score: 1

      Even I could trace that - RTFWebsite?

      "The Professional series switches utilize WideBand's robust signaling technology allowing Gigabit connections over Category 5 runs in excess of 200 meters, and even over 100-meter segments of Category 3 cable"

      (too bad about the barbed wire, though...)

      --
      Caveat Emptor: this message won't selfdestruct if you memorize it!
  48. reliability's a doddle. by Anonymous Coward · · Score: 0

    ten cheap PCs running heartbeat & STONITH are more reliable than any single box, period. And cheaper than equivalent hardware.

    Learn the RAID lesson, dude.

  49. WideBand has better support by Rabid+Cougar · · Score: 0, Redundant

    Consider WideBand instead of Cisco. Their Gold Support is so good, that often the first you hear of a problem is an e-mail from them notifying you that they fixed it. And since they're 100% American made and supported, you'll never call and talk to someone who barely speaks English. No, I don't now nor have I ever worked for them. We just use thier products and couldn't be happier.

    --
    This isn't the sig you're looking for...
  50. F5? by Gr8Apes · · Score: 1

    I recall F5's BigIP Pro back in the late 90s. A really nice slick purple and silver box. Big "F5" on the front. Opened the $25+K box up and lo and behold - a P2-233. Oh, and that box was precisely what you think it was now that you know what was in it. A $25K boat anchor. (apoligies to respectable boat anchors everywhere).

    I've heard recently that new deployments of F5's products still suffer some of the same faults we ran across in 99.

    --
    The cesspool just got a check and balance.
    1. Re:F5? by Anonymous Coward · · Score: 0

      franken pix anyone?

    2. Re:F5? by Bert64 · · Score: 1

      A lot of these machines are...
      The Nokia IP650 is just a P2 motherboard, complete with video ports and an onboard nic that you can access if you take the lid off the machine.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    3. Re:F5? by pyite · · Score: 1
      NAMEREMOVED# sh hard
      Cisco Storage Area Networking Operating System (SAN-OS) Software
       
      ...
       
      This supervisor carries Pentium processor with 1028768 kB of memory
      Intel(R) Pentium(R) III CPU at - with 32 KB L2 Cache
      Rev: Family 6, Model 11 stepping 4
      512K bytes of non-volatile memory.
      500736 blocks of internal bootflash (block size 512b)
      Just because it has a PC processor in it doesn't mean it doesn't have ASICs on board. The Cisco MDS 9500 series is an excellent switch, yet it's the ASICs and proprietary hardware that make the difference--not the Pentium III.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

    4. Re:F5? by Gr8Apes · · Score: 1

      I just checked their specs (warning - pdf) and their current bottom of the line box is a pure PC. No ASICs. I don't think they had any ASICs 7 years ago, although I cannot confirm that.

      --
      The cesspool just got a check and balance.
    5. Re:F5? by pyite · · Score: 1

      My comment wasn't direct at that particular box, per se. I'm just saying sometimes it can be both. I'm not surprised that's how the F5 is.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

  51. MS advocate to OS advocate by jkrise · · Score: 1

    MS advocate: I work on .Net, MSMQ, SQL and Windows Vista by the day...
    OS Advocate: Any by the night???
    MS advocate: Oh nothing.. I just Update, patch, reinstall and reboot.
    OS Advocate: What is reboot?

    --
    If you keep throwing chairs, one day you'll break windows....
  52. As a very smart man once said.... by FlyingGuy · · Score: 0

    "Never do it in software, if you can do it hardware".

    Just adding to all the other replies that talked about bandwidth, etc. etc.

    Support. You gotta have support. I dont care HOW good this thing has the potential to be, unless I can call an engineer 24/7 including christmas, I wouldn't even let it in the building.

    Its like choosing MySQL or MS-SQL over Oracle, yeah it may cost you less upfront, but your going to pay in the end.

    I had an oracle server just go completely brain dead. I called Oracle support at 4:30pm, on a Thursday. I was talking to the Denver support Center. Now Denver closed at 8pm, central time. I was still on the phone with an engineer at closing. The very nice lady says, "Ok its closing time and I have to go get my kids, so I have Sam on the line, he is in England, he will be taking it from here, I have briefed him on everything we have done." so on with Sam from England I went. When England closed down, I was shifted to China, then to Australia. When the problem was finally solved, I was talking to California.

    This is why when your IP throughput to your customers is worth 30 or 40 thousand dollars a minute, you dont screw around, you pay the money for the best combination of hardware / support you can afford. I could care less if under the hood they are running a linux, Novell, M$ or Apple kernel, its just has to work, and when it doesn't the support just has to be there 24/7.

    --
    Hey KID! Yeah you, get the fuck off my lawn!
  53. why does the link say not intended as simulators? by artifex2004 · · Score: 1

    When I trained at Juniper Networks' Denver office in December 2001, they had stacks of Olives in the training room, and that's what we used to test commands on.
    Loved them. But the trainer told us at the start not to ask for a tarball :)

  54. Now for the important question... by monsted · · Score: 1

    Does it run FreeBSD?

  55. Ah, a good pun wasted... by skids · · Score: 1

    My guess is 80% of the folks here think a power tool is a cordless screwdriver for taking PC cases off :-)

    1. Re:Ah, a good pun wasted... by RareButSeriousSideEf · · Score: 1

      I only know differently because the PCs I build are mainly for my wife to timeshift Toolbelt Diva.

      (We have very different ideas about what constitutes a "hardware store.")

  56. Re:Yawn. Slow news day? by jmilne · · Score: 2, Informative

    I had some experience with Olives as well. However, their performance wasn't that great. Especially compared to a M10. ASICs made a huge difference.

  57. Speed by Mohan+S · · Score: 1

    I see a good number of posts advocating that ASICs do a better job, are more optimised, memory bandwidth limitations/latencies etc.... I've been there and done that in terms of building a commercial software router running on standard x86 platforms and customised x86 platforms. Products like the CISCO 3845 ISR reach upto 600K packets per second raw forwarding and dip drastically in performance when ACLs, QoS etc are enables. Even for 1500B packets, these routers cannot sustain line rates for ACLs on 2 gig-ethernet interfaces bi-directional. On a standard x86 server board running on Opteron 2GHz, a software router was able to outstrip the CISCO 3845 by 70% and retain performance with ACLs thereby making it more than twice as fast. Mind you, this was on a $1000 server hardware from a well known serverv vendor. I'd expect the OFR to do atleast 70-80% as well. Nothing can stand greater testimony than this to the fact that x86 hardware can deliver performance.

  58. Re:Yawn. Slow news day? by Lumpy · · Score: 2, Informative

    You can easily route 5 T1's on a Thrown away 586MMX at 266Mhz.

    I did it for 6 years with a hand rolled linux install and ipchains. IT was faster than the HP 6 port router it replaced in both speed and network performance and adding in some filtering gave us a product that sould have cost $6000 at the time from the New Cisco company or then popular Colorado networking.

    Every single one of these guys here claiming that no way a PC can route much traffic knows absolutely nothing about networking and routers. Hell a cheap P4-2.8 with the right hardware can route ATM speeds over ethernet easily (Yes kids, you can get ethernet termination on anything from your provider).

    Hell a slow 386 can do a single T1 without getting about 5% processor loads.

    --
    Do not look at laser with remaining good eye.
  59. Re:Yawn. Slow news day? by aleander · · Score: 1

    /me disappears in a puff of absurd.

    I have a WRT54G right here, and there are two persons with bittorrent right now.

    As for pc's, I have a 1300-user network with *lots* of bittorrent-users in it, all behind 8 pc's (P-IV, granted).

    --
    Segmentation fault. Ore dumped.
  60. Re:Yawn. Slow news day? by Anonymous Coward · · Score: 0

    Imagestream - HA! Now, there is a joke!

    A company run from the basement of one of their mother's houses? I've been there and these guys are not worth your time. Check out their corporate headquarters location and tell me this is for real: http://maps.google.com/maps?f=q&hl=en&q=7900+8th+R d,+Plymouth,+IN+46563&ie=UTF8&t=k&om=1&ll=41.36257 3,-86.213365&spn=0.017941,0.042357

    Also, taking open source and then closing it and turning it into a prorietary router != OSS!

    For Vyatta, it looks like they have a real company, a real location, a real management team and the code is available here: http://www.vyatta.com/twiki/bin/view/Community/Sou rceCodeAccess

    For a midrange router with a few FE ports I might give them a shot.

  61. Re: Support by notarus · · Score: 1

    Let's not confuse "sometimes things don't work as expected" with "it never works! it's a disaster!!11!L".

    I'm not the biggest cisco fan in the world, and given sufficient quantities of beer, i can tell dozens of stories of how cisco couldn't or wouldn't fix a particular problem. We even have a free router because it was easier to just give us a different router where the problem didn't happen than fix it on the platform we bought.

    But keep this in mind: We have a free router because it fixed the problem. And for every "this is the stupidest support story ever", the bottom line is ALWAYS it was a p3 or p4 issue. Something annoying but we could live with it if my primary goal at work wasn't to solve or whine away every obstacle to the utopian network.

    Every P1 or P2 issue i've ever reported, and my CCO account is long and has many notes about my character i'm not allowed to read :), every single one has been solved efficiently and with serious concern for the customer. P1s that lasted more than a few days came with every morning conference calls with my tac engineers giving me status.

    Cisco provides good software (with bugs), good support (with bugs), and sells it using people (good grief, they're buggy). And we, the end users, are often buggy too, which needs to be kept in mind as well.

    An open source router sounds nice for the times you're building a small business that has no money to buy something expensive (or a business reason to do so). I'm not going to waste my time bashing it, it's just that it doesn't fit into what I do.

    When I run into a problem where a cam table is corrupted with a particular rediclously contrived but business critical data stream, I need it fixed and I need it fixed fast, and I'm not paid to decode and rewrite layer 2 forwarding to PCI-X interfaces. So for me? It's just not right.

    And dude, don't get me started on running gigabit over cat 3... :)

  62. Intuitive? Prove Thy Case! by Mariner28 · · Score: 1

    Umm, let's see. Intuitive?

    Cisco IOS

    Shutdown a port:
    MyRouter#config
    MyRouter(config)#interface ethernet 1/1
    MyRouter(config-if)#shutdown
    MyRouter(config-if)#Z
    MyRouter#

    Enable a port:
    MyRouter#config
    MyRouter(config)#interface ethernet 0/0
    MyRouter(config-if)#NO shutdown
    MyRouter(config-if)#Z
    MyRouter#

    Boy, that's intuitive!

    Now for that wild, byzantine Linux command shell interface:

    Shutdown a port:
    MyHost# ifdown eth0

    Enable a port:
    MyHost# ifup eth0

    Oops - forgot to show the command to get to "command mode", i.e. - root privelege:
    Myhost$ su
    Password: xxxxx
    MyHost# ifup eth1
    MyHost# exit
    MyHost$

    Thank God Cisco's IOS is soooo much more intuitive than the Linux/bash command shell!!!

    In IOS, you don't "enable" a port, you just don't shut it down! How intuitive!

    --
    "A little misunderstanding? Galileo and the Pope had a little misunderstanding."
    1. Re:Intuitive? Prove Thy Case! by toleraen · · Score: 1

      Lets just start out with a little dictionary action

      The linux commands you're calling out aren't intuitive at all. You're just saying linux is faster to type in. ifup, ifdown? does that mean if = down, then eth1? Linux CLI is notorious for being confusing and unintuitive. Cisco IOS: configure terminal. interface fastethernet0/0. shutdown. it specifically states what you want to do, what interface, and what you want that interface to do. How is ifup eth1 more intuitive than that? All the commands are neatly tucked away where they should be. If it doesn't affect the system in a global manner, it's under the section that it does affect.

      Oh yeah, what do you have to do to check the configuration of your ethernet card in linux?
      more /etc/sysconfig/network-scripts/ifcfg-eth0
      More, an extremely obvious command to show something, and of course the config file is in the first place /I'd/ look.

      Too bad Cisco made it all tough with show running-configuration interface fastethernet0/0 (or if you're concerned about WPM performance, show run int fa0/0).

      Cisco IOS may not be extremely fast to type things out in like Linux. But it is very intuitive. They want to make sure you know exactly where you're working, and what you're doing. I'm not doing networking on my Pentium Pro box in my mom's basement like you are. If I'm running the risk of taking down a corporate network, I need to know that what I'm doing shouldn't affect everything else on the box. Keep access limited to whatever you need. The Cisco CLI makes perfect sense for that purpose.

  63. Source by Rabid+Cougar · · Score: 1

    Google is your friend.

    --
    This isn't the sig you're looking for...
  64. not true by DrGalaxy · · Score: 1

    There are plenty of PCI WAN boards with Linux API/drivers on the market. You can get 1-8 port T1, 1-4 port OC3, and 1-2 port ATM and DS-3 boards. Most of them support channelized links, so you can break your T1 into 12 channels for data and 12 digital voice lines.

    Here is a list of companies you can get them from:
    http://www.sbei.com/ (distributor/products page http://www.ace-electronics.com/Hardware/T1E1J1/t1i ndex.html)

    http://www.imagestream.com/Industrial_Cards.html - they even have a 4 port OC3 PCI card

    http://www.sangoma.com/main/products/wanpipe - solid Linux support and drivers

    http://www.digium.com/ - has 1, 2 and 4 port T1 boards that work GREAT with linux

    Of course installation and configuration of this kind of solution will not be as simple as a Cisco WIC in your 2600.

  65. Actually by Anonymous Coward · · Score: 0

    Even 5 years ago, there was decent kit on the market.

    But you have to distinguise here, there are people that want to use stuff. And there are people that want to build stuff from old PC's. And since they apparently need a way to boots their Alpha Geek status they make up this story about their solution being "better" than what you can buy of the shelf...