From owner-freebsd-net Wed Feb 2 12:31:52 2000 Delivered-To: freebsd-net@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by builder.freebsd.org (Postfix) with ESMTP id CB22A4186 for ; Wed, 2 Feb 2000 12:31:35 -0800 (PST) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 12G6Qe-0004Gt-00; Wed, 2 Feb 2000 20:31:08 +0000 Date: Wed, 2 Feb 2000 20:31:08 +0000 (BST) From: Jasper Wallace To: "Matthew N. Dodd" Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: 802.1Q VLANs In-Reply-To: Message-ID: X-NCC-RegID: uk.instant-web MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Feb 2000, Matthew N. Dodd wrote: > On Wed, 2 Feb 2000, Jasper Wallace wrote: > > We are using the vlan patches from: > > > > http://www.euitt.upm.es/~pjlobo/fbsdvlan.html > > > > quite happily - they only work with fxp's tho, and don't do proper interface > > statistics reporting... > > ifconfig in both -STABLE and -CURRENT has support for setting up vlan > devices. > > ifconfig vlanX vlan N vlandev foo0 ... yeah, i don't bother with vlanconfig - it's the kernal patches that matter. > I've got a switch that supports vlans and have tested the code by > configuring vlan devices on 2 machine and pinging. It works enough for > that but there are unrelated bugs in the network driver I'm using that > have prevented further testing. oh well, with the vlan code in -stable i could ping, but tcp or udp packets would eventually panic the machine, it's fine with the patches from the above url. -- Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message