From owner-freebsd-net@FreeBSD.ORG Wed Jan 28 13:03:59 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53E4F16A4CE for ; Wed, 28 Jan 2004 13:03:59 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8789443D1F for ; Wed, 28 Jan 2004 13:03:57 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <200401282103530140052680e>; Wed, 28 Jan 2004 21:03:57 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA07373; Wed, 28 Jan 2004 13:03:52 -0800 (PST) Date: Wed, 28 Jan 2004 13:03:51 -0800 (PST) From: Julian Elischer To: veedee@c7.campus.utcluj.ro In-Reply-To: <20040128204603.GA19311@c7.campus.utcluj.ro> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Large scale NAT - problem resolved X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 21:03:59 -0000 On Wed, 28 Jan 2004 veedee@c7.campus.utcluj.ro wrote: > On Wed, Jan 28, 2004 at 10:41:20PM +0200, Ruslan Ermilov wrote: > > On Wed, Jan 28, 2004 at 12:15:56AM -0800, Julian Elischer wrote: > > > > > > On Wed, 28 Jan 2004, Andriy Korud wrote: > > > > > > > > > > > Hi, > > > > At last I've managed to build stable NAT on FreeBSD box for 34Mbit link and > > > > ~2000 clients (cable modem network). > > > > At full speed (34Mbit) CPU usage is 0% and system load is 0.0 :-) > > > > > > > > > > It'd be really interesting to see how natd would handle such a load.... > > > > > You must be kidding. ;) > > Agreed. NATd "crashes" with 400 clients on AMD Athlon 900Mhz. :( ipnat > works fine. > > This raises a question... is there any point in still having natd? (don't > throw rocks at me please, I'm just asking). Or maybe it's still being used > for servers with less clients to nat? Well for people using ipfw.. if_nat requires ipfilter If it 'crashes' that sugests that a bug exists.. anyone know what 'crashes' means? gets slow? if so then probably using a hash table somehwere would fix it..