From owner-freebsd-isp@FreeBSD.ORG Wed Apr 29 15:02:33 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64D5A1065672 for ; Wed, 29 Apr 2009 15:02:33 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) Received: from mail.mgwigglesworth.com (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 93D8A8FC1C for ; Wed, 29 Apr 2009 15:02:32 +0000 (UTC) (envelope-from martes@mgwigglesworth.net) To: freebsd-isp@freebsd.org Date: Wed, 29 Apr 2009 11:01:37 -0400 Envelope-To: freebsd-isp@freebsd.org References: <200904281702.19301.martes@mgwigglesworth.net> <49F7797B.1060306@thingy.com> Message-ID: <200904291101.38436.martes@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from localhost.localnet (192.168.5.12 [192.168.5.12]) by mail.mgwigglesworth.com; Wed, 29 Apr 2009 11:01:55 -0400 Organization: M.G. Wigglesworth Holdings, LLC User-Agent: KMail/1.10.3 (Linux/2.6.27.19-desktop586-1mnb; KDE/4.1.3; i686; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [freebsd-isp] Temporary Routing/Switching backup with Backplane and multiple switch cards... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: martes@mgwigglesworth.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 15:02:33 -0000 On Tuesday 28 April 2009 17:47:39 Howard Jones wrote: > Martes G Wigglesworth wrote: > > I was wondering if anyone else has attempted to compliment their routing > > devices or switching devices with a back-plane and multiple switch cards > > or E1/T1 cards with any success? Meaning that it was worth the trouble to > > build. > > > > This seems a bit useless initially, however, I am doing some research > > into this for quick-fix disaster recovery systems in case the 3800s are > > down, etc... A bit home-grown, but would like to know if the design > > idea would be viable and not just a costly home-grown project... Maybe > > for a small point of present in a wireless environment which has multiple > > E1/T1 drops to terminate for back-haul transfer central management > > stations, etc... > > _______________________________________________ > > You mean like these? > http://www.vyatta.com/ > http://www.xorp.org/ > http://www.freesco.org/ > All are "software routers" various levels of hardware support for (e.g.) > Sangoma E1/T1 cards. > > Plenty of people use Quagga+Linux or Quagga+FreeBSD (Quagga is the > BGP/OSPF component most of these uses) for peering/transit. PC hardware > will route over 100Mbit quite happily. > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" Thank you for the new links that I had not come across yet. However, I was not as clear as I should have been. I was more interested in finding out when it became, or would become less cost effective to do this type of setup, due to economies of scale like Cisco and Juniper devices possibly being cheaper than havnig to spend on individual pieces to... More specifically, when is it not cost effective to do such a thing? Assuming a larger, and not smaller network architecture. When does the embedded, specifically designed network processor do a better job than a stripped down server appliance, as described above?