From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 17:57:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C95816A4CE for ; Thu, 5 Feb 2004 17:57:02 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB8E043D46 for ; Thu, 5 Feb 2004 17:56:56 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i161v1oh025699; Fri, 6 Feb 2004 03:57:01 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i161utPB025694; Fri, 6 Feb 2004 03:56:55 +0200 (EET) (envelope-from ru) Date: Fri, 6 Feb 2004 03:56:55 +0200 From: Ruslan Ermilov To: Brooks Davis Message-ID: <20040206015655.GA25623@FreeBSD.org.ua> References: <20040203213456.GT50677@backmaster.cdsnet.net> <200402051417.00117.sam@errno.com> <20040206003112.GU50677@backmaster.cdsnet.net> <20040206004924.GB20813@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline In-Reply-To: <20040206004924.GB20813@Odin.AC.HMC.Edu> User-Agent: Mutt/1.5.5.1i cc: Sam Leffler cc: current@freebsd.org Subject: Re: VLAn support for atheros/Prism? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 01:57:02 -0000 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 05, 2004 at 04:49:26PM -0800, Brooks Davis wrote: > On Thu, Feb 05, 2004 at 04:31:12PM -0800, mrcpu@cdsnet.net wrote: > > Well, I'm just looking through the specs of the microtik stuff, and they > > say they have vlan support over wireless now. > >=20 > > I can fudge the VLAn support, at the cost of a reduced MTU using the > > "software emulation" vlan tagging, or whatever it is that FreeBSD does, > > and bridge those packets, but that's not the same as true hardware VLAN > > tagging. >=20 > You've got a serious misconception about how vlans work. The only > hardware support that is required is support for a wire MTU of 1504 > bytes so the tag fits on the packet without reducing payload size. Some > interfaces have support for removing the tag from the packet for you and > indicating the tag out of band, but that's only an optimization. >=20 I think the originator is asking why IFCAP_VLAN_MTU is not set by the ath(4) driver (I've only checked with grep(1)), is it due to a hardware limitation, or due to the driver? Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAIvRnUkv4P6juNwoRAhiXAJ0dxsE8P+DjSGyBO1oqYTSe4ey3ggCfWOO+ goVsaWCGkL7xdwk++EpXPQA= =EjP8 -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--