nanog mailing list archives
Re: Routers vs. PC's for routing - was list problems?
From: Vinny Abello <vinny () tellurian com>
Date: Thu, 23 May 2002 17:09:27 -0400
At 04:17 PM 5/23/2002 -0400, you wrote:
> I agree with you on that. Hot swapability for various interfaces is > something routers obviously have over PC's. Hot swap PCI is old news.
True, but not widely implemented in the standard PC market. If you want a server that has hot swap capability, you're likely paying a premium price for a lot of extra other features. It's not something you can typically just build yourself, and if you can you'll need a case that allows you easy access to swap the PCI cards. By the time you pay for an enterprise level server with this capability, I would rather have put the money towards a good router.
> True... unless going for 64 bit PCI at 66MHz... still it's obvious that > routers are designed for one simple purpose and generally have larger > backplanes to handle that. However, $ for $, even when buying used cisco gear at 80% off from dot-booms, a PC router will outperform any traditional router.
At what speeds though? As you get into the higher gbic speeds, a PC doesn't have the backplane to cut it. Now if we're talking raw processing power, a PC can blow away a router in calculations per second any day. :)
> I agree a router is probably more efficient in just routing packets, but in > complex filtering or traffic manipulation/packet sniffing, a PC might have > the edge. :) Yes, ipfw/dummy is very very cool. Like, inducing a few 100 msecs of latency to folks who don't pay on time :)
Hehehehe... Interesting approach. I find it more fun to just shut them off. It makes them take you more seriously. Unfortunately I would say only a small percentage of users, may 20% or so would even notice the latency issues if they were having them. They're more likely to complain about slow transfer speeds. That is even more fun and can be done on any traditional Cisco... Traffic shaping is cool but hindered by being limited to controlling outbound traffic on an interface. Rate limiting even more fun. Hmm... [exceed action drop] Why is there so much damn packet loss on my connection when I put traffic across it??? ;)
Vinny Abello Network Engineer Server Management vinny () tellurian com (973)300-9211 x 125 (973)940-6125 (Direct) Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN
Current thread:
- Re: Routers vs. PC's for routing - was list problems? James Cornman (May 23)
- <Possible follow-ups>
- Re: Routers vs. PC's for routing - was list problems? E.B. Dreger (May 23)
- Re: Routers vs. PC's for routing - was list problems? Dominic J. Eidson (May 23)
- Re: Routers vs. PC's for routing - was list problems? Vinny Abello (May 23)
- Re: Routers vs. PC's for routing - was list problems? E.B. Dreger (May 23)
- Re: Routers vs. PC's for routing - was list problems? Henry Yen (May 23)
- Re: Routers vs. PC's for routing - was list problems? Andrew Brown (May 24)
- Re: Routers vs. PC's for routing - was list problems? Dan Hollis (May 23)
- Re: Routers vs. PC's for routing - was list problems? Joseph T. Klein (May 23)
- Write Only was Re: Routers vs. PC's for routing - was list problems? Joseph T. Klein (May 23)
- Re: Routers vs. PC's for routing - was list problems? Greg A. Woods (May 23)
- Re: Routers vs. PC's for routing - was list problems? David Lesher (May 24)
- Re: Routers vs. PC's for routing - was list problems? Scott Granados (May 24)
- Re: Routers vs. PC's for routing - was list problems? Joseph T. Klein (May 23)
- RE: Routers vs. PC's for routing - was list problems? Rowland, Alan D (May 24)
(Thread continues...)