Re: outgoing interface field

On Thu, 2008-06-19 at 22:14 +0200, Johannes Berg wrote:

> > Besides, radiotap headers are designed to be transferable between
> > systems.  It should be possible to send frames with radiotap headers
> > from another system, possibly with a different endianness and
> > different
> > wireless hardware.  Encoding local data (VAP number) makes radiotap
> > headers system-specific.
> 
> This isn't designed to be ever saved to disk, it's for communication
> between userspace and the kernel when running an AP. We just happen to
> use radiotap for that to save inventing yet another interface.

Then there is very little point in discussing it.  I thought you were
going to suggest some elegant addition to the standard.  Piggybacking
the frames with some OS and system specific data is not.

> > It's funny, we are creating the rules that exclude us, and then we are
> > shopping around for sponsors.  We need exceptions for experimental use.
> 
> Actually, I just figured out that the OUIs have a 'locally assigned' bit
> like MAC addresses (well I guess MAC addresses inherit it from OUIs), so
> we can use that and assign "experimental" OUIs to ourselves as long as
> they don't clash within radiotap.

OK, fine.

-- 
Regards,
Pavel Roskin