From owner-freebsd-isp@FreeBSD.ORG Sun Jan 25 02:10:13 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10E0016A4CE for ; Sun, 25 Jan 2004 02:10:13 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E85A643D31 for ; Sun, 25 Jan 2004 02:10:10 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 0D1341FFC27; Sun, 25 Jan 2004 11:10:09 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 597B41FFC24; Sun, 25 Jan 2004 11:10:07 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 5553B155AB; Sun, 25 Jan 2004 10:06:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 46B7E15384; Sun, 25 Jan 2004 10:06:31 +0000 (UTC) Date: Sun, 25 Jan 2004 10:06:31 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: pi@LF.net In-Reply-To: <20040125092813.GE987@complx.LF.net> Message-ID: References: <4012E087.4080504@mr0vka.eu.org> <4012E2F2.2000108@keystreams.com> <20040124215019.GD987@complx.LF.net> <40132999.3020906@keystreams.com> <20040125092813.GE987@complx.LF.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-isp@freebsd.org Subject: Re: BGP4 using FreeBSD X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 10:10:13 -0000 On Sun, 25 Jan 2004, Kurt Jaeger wrote: Hi, > > >Disks were never the relevant topic. Basically, those systems > > >just worked. Yes, they need a little hand-holding, but not because > > >of the disks. > > > Well that may be, but why risk having a hard drive go out? Flash memory > > most definatley outlasts traditional hard drives. > > See the discussioon nanog about this, a few days ago. > > http://www.merit.edu/mail.archives/nanog/ > > The problem with flash is that has its part of wear and tear as well. > It's not easy to do a real read-only setup. If you don't, some > part of the flash do will wear out. Flash mem do has a finite number > of possible writes. while this is true loading an md_image from a flash disk is quite easy these days with FreeBSD as is booting such from tftp. Then your at about the same problematic cisco p.ex. has writing config back to nvram or flash. But how often would you do this on a cisco and how many writes can you do on a flash card these days ? additionaly you can always save the config to a remote system via tftp/ftp/scp/sftp/cvs/ and if you want you can also fetch them at boot time again (not the thing one really wants but similar to some boot tftp modulo boot loader and kernel loading; unsure what linuxbios et. al. could help here). logging that needs to be saved should go to a remote system anyway. If you want local accounting (p.ex. with a hacked up tcpdump ;-) you may want to have a hd for saving the dumps (perhaps hot swap supported so they can be changed on failure with less/no downtime of your peerings) or have an extra 512MB RAM for this with the possibility of losing some accounting on reboot (which should not happen too often for a router). Just to note there is also a bgpd.pl (BGP daemon implemented in perl) at http://sourceforge.net/projects/bgpd I once had a quick look at it after its initial announcement some (2-3) years agao. Current state is unknown. Never used it. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/