The Making of a Router
cabenth at gmail.com
Thu Dec 26 16:55:40 UTC 2013
I also wonder about re-inventing the wheel. The router part is easy, you could even do that with a windows box (that's a joke).
Obviously capital cost is part of it, but the man hours involved in doing what you're talking about, especially since you are talking about a telco.... whatever you come up with has to be pretty darn reliable...
Certainly would be interested in a little more information about the use case.
On Dec 26, 2013, at 8:46 AM, Faisal Imtiaz <faisal at snappytelecom.net> wrote:
> I am a believer of not having to re-invent the wheel...
> Having said that.. have you looked at 'purpose built appliances' e.g.
> If you are looking for a full router....
> Consider such as these...
> and there are a few others but the concept is the same
> Personally, I am not a believer in making a single device be the do all / end all of everything..
> While one can do everything on a big server .. however breaking things out e.g. voip trans-coding and routing make maintenance, availability, and ability to create redundancy much more practical.
> Faisal Imtiaz
> Snappy Internet & Telecom
> ----- Original Message -----
>> From: "Nick Cameo" <symack at gmail.com>
>> To: nanog at nanog.org
>> Sent: Thursday, December 26, 2013 11:33:13 AM
>> Subject: The Making of a Router
>> Hello Everyone,
>> We are looking to put together a 2u server with a few PCIe 3 x8
>> (recommendations appreciated). The router will take a voip transcoding
>> line card, and will act as an edge router for a telecom company.
>> For things like BGP (Quagga, Zebra, all that lovely stuff!!!), static
>> routes, and firewall capabilities we are thinking gentoo linux
>> stripped for sure however, what about the BSDs? FreeBSD or OpenBSD.
>> Any comments, feedback, does, and don'ts are much appreciated.
>> Kind Regards,
More information about the NANOG