Peter Stuge wrote: > On Wed, Jul 27, 2005 at 09:03:59AM -0700, Ben Greear wrote: > >>I guess we could just let application writers know to pass a >>pre-constructed *ethernet* frame instead of a VLAN frame. It is >>likely that this is how folks use it anyway... > > > How about the priority bits then? You can do mapping against sk->priority and set the priority with setsockopt in user space. For detailed control, it may be good to have a 'do not re-encapsulate' flag settable on a socket with setsockopt. That way user-space could specify 'raw' behaviour if desired, on a per socket basis. Ben > > > //Peter > _______________________________________________ > Vlan mailing list > Vlan@xxxxxxxxxxxxxxx > http://www.lanforge.com/mailman/listinfo/vlan > -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com