Date: Sun, 03 Jul 2005 01:25:39 -0000 From: Ruslan Ermilov <ru@FreeBSD.org> To: Christian Brueffer <brueffer@FreeBSD.org>, Robert Watson <rwatson@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man4 em.4 Message-ID: <20050220091312.GA46244@ip.net.ua> In-Reply-To: <200502200009.j1K09cI4071290@repoman.freebsd.org> References: <200502200009.j1K09cI4071290@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 20, 2005 at 12:09:38AM +0000, Christian Brueffer wrote: > brueffer 2005-02-20 00:09:38 UTC >=20 > FreeBSD src repository (doc committer) >=20 > Modified files: > share/man/man4 em.4=20 > Log: > Remove the note about em(4) not working with bridge(4) when hardware > assisted VLAN processing is enabled from the BUGS section. This is > expected to work now. > =20 > Revision Changes Path > 1.19 +1 -5 src/share/man/man4/em.4 >=20 Currently, it should be safe to operate em(4) with hardware VLAN tagging even if it's set to promiscuous mode and bridge(4) is running on VLANs. I'm working on a fix that allows bpf(4) to see normal ETHERTYPE_VLAN frames even if the underlying driver supplies frames with VLAN mbuf tags. Once this is implemented, the hacks from em(4) can go away completely. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCGFSoqRfpzJluFF4RAoMYAKCXwVZHd2KLvmbrCyrcnPD38BFvVQCcCpwb o0iqnOxpbk2tBD8NTCvPwmg= =ZVKI -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050220091312.GA46244>