From owner-freebsd-net@FreeBSD.ORG Wed Apr 12 20:30:15 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 C7C0816A407 for ; Wed, 12 Apr 2006 20:30:15 +0000 (UTC) (envelope-from ericx_lists@vineyard.net) Received: from smtp1.vineyard.net (a1.vineyard.net [204.17.195.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2135243D4C for ; Wed, 12 Apr 2006 20:30:11 +0000 (GMT) (envelope-from ericx_lists@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by smtp1.vineyard.net (Postfix) with ESMTP id 1E54D1581881 for ; Wed, 12 Apr 2006 16:30:11 -0400 (EDT) Received: from smtp1.vineyard.net ([127.0.0.1]) by localhost (ace1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24165-01-32 for ; Wed, 12 Apr 2006 16:30:10 -0400 (EDT) Received: from [204.17.195.104] (fortiva.vineyard.net [204.17.195.104]) by smtp1.vineyard.net (Postfix) with ESMTP id D00951581814 for ; Wed, 12 Apr 2006 16:30:10 -0400 (EDT) Message-ID: <443D6325.2050109@vineyard.net> Date: Wed, 12 Apr 2006 16:29:25 -0400 From: "Eric W. Bates" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <443CF4D7.1030204@ide.resurscentrum.se> <20060412201725.GA42102@heff.fud.org.nz> In-Reply-To: <20060412201725.GA42102@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-ace1 at Vineyard.NET Subject: Re: Sub-interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Apr 2006 20:30:15 -0000 Andrew Thompson wrote: > On Wed, Apr 12, 2006 at 02:38:47PM +0200, Jon Otterholm wrote: >> Hi. >> >> I am designing a new network and one way to go is to configure a router >> based on FreeBSD with one IF/customer. This would mean around 1000 >> VLAN-IF's/router - would this work? Do you see any problems with this? > > 1000 vlan interfaces will work fine. In all the stable branches (and > releases) the vlans will be in a linked list, this can be slower as the > list increases in size. In CURRENT this is now a hash list and you can > optimise it even more by defining VLAN_ARRAY which will directly > dereference the tag->ifnet. We did run into a problem when we had too many (more than 15) addresses/interfaces on a system. isc-dhcpd has some table sizes hard-coded for some data structures. This was solved by patching common/discover.c (thanks to help from this list). Obviously not a problem if you aren't planning on dhcp. > > Andrew > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >