North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Routers vs. PC's for routing - was list problems?

  • From: James Cornman
  • Date: Thu May 23 15:42:01 2002

We've had some rather good success with PC based routers. Typical
setup was FreeBSD 4.x, 512mb, 20gb RAID-1, 3com Gigabit Ethernet card,
Fore Systems OC3 ATM card. All this, with zebra on top. It worked well for
a long time, although it turned out getting deprecated because of some
zebra issues (with ospfd. They (the problems) weren't confirmed by the
zebra community but thats the only thing we could narrow it down to.
ospfd would die periodically.) The line cards were bought off of eBay.
We did VLAN trunking through the 3com GBE card to a Catalyst 3548. Did any
rate limiting with DUMMYNET and ipfw pipes. Overall, the whole system
worked great for a few months without human interaction,
until the ospfd problems.

Feel free to contact me off list if you have any questions. I dont know
all of the exact hardware/software tweaking that were done; alot of them
were left default, but i'll try to help.


-- 
James Cornman <[email protected]>
Net Access Corporation - http://www.nac.net/

On Thu, 23 May 2002, E.B. Dreger wrote:

>
> ADC> Date: Thu, 23 May 2002 14:30:16 -0400
> ADC> From: Anthony D Cennami
>
>
> ADC> "Not to say you can't route well with a linux or bsd system
> ADC> you can but at the high-end probably not as well."
> ADC>
> ADC> Tell that to Juniper.
>
> Where can I buy their line cards for my PC?
>
>
> --
> Eddy
>
> Brotsman & Dreger, Inc. - EverQuick Internet Division
> Phone: +1 (316) 794-8922 Wichita/(Inter)national
> Phone: +1 (785) 865-5885 Lawrence
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
> From: A Trap <[email protected]>
> To: [email protected]
> Subject: Please ignore this portion of my mail signature.
>
> These last few lines are a trap for address-harvesting spambots.
> Do NOT send mail to <[email protected]>, or you are likely to
> be blocked.
>
>