On Wed, Dec 12, 2001 at 03:15:58PM -0500, Sam Tannous wrote: > On Thu, Nov 15, 2001 at 01:42:07PM -0800, Brooks Davis wrote: > > On Thu, Nov 15, 2001 at 03:41:21PM -0600, Shaun Marko wrote: > > > Could you also get the desired result by using a kernel without > > > VLAN support? > > > The original poster said he didn't want to configure VLAN interfaces > > > anyway. > > For the moment, on stable hosts, that will work. Driver vlan support is > > no longer optional in current and that change will be MFC'd just as soon > > as I get it tested. The right answer is probably to modify the > > VLAN_INPUT_TAG macro to do the bpf stuff. > > > > is there a way to turn off driver VLAN support? > > (I don't object to having it on by default. > I just want to be able to turn it off > so I can see *all* the vlan traffic with tcpdump/libpcap > (even if I have VLAN turned on in my kernel)).
In current there's an interface capability configuration system that is used to enable and disable things like hardware checksum support. I intend to look at adding a bit to control hardware VLAN decoding. Unfortunatly it won't be possiable to MFC this without a rule change because it would break all binary network drivers. We do plan to modify vlan_input_tag to fake up a vlan header and pass the packet to bfp so you will be able to tap hardware decoded vlan frames. I'm not sure it this will be enabled by default or not. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
msg04445/pgp00000.pgp
Description: PGP signature
