On Wed, 2007-08-08 at 00:03 +0200, Ulrich Kunitz wrote:
> > Aha, but they're not fully compatible. First of all, you were talking
> > about multiple MACs which isn't something we're going to support
> > (multiple MAC addresses yes).
>
> I would state we should the support the functionality that the
> device supports. Everything else is "form follows function".
But we don't have any devices that have multiple MACs. Yes, we *do* have
devices that support multiple _MAC addresses_ but I don't think any of
them support multiple _MACs_.
> > Secondly, a WDS and AP interface will be
> > running with the same MAC address but have quite different
> > configuration. Thirdly, always doing lookups by MAC address (even if it
> > were possible which it is not due to WDS vs AP) is rather inefficient.
>
> The MAC address lookup issue could be handled.
>
> Assuming that the device would be able to create beacons on a
> specific MAC address, would it need to know about WDS or AP mode?
Say it supports multiple BSSes on a single AP MAC address like many APs
do. Then we have to look up beacons by BSS and other things by MAC
address and it really gets confusing quickly. I think that abstracting
it all down to BSS IDs and MAC addresses gets rather confusing because
the driver authors are also users at the other end and adds interfaces
for testing. If they can see the effect of adding an interface I think
there's a better chance of understanding what's going on.
> Beaconing needs to be supported by the device.
Yes, but how many different beacons does it support? That's something
easily solved by limiting
1) the number of devices to the number of MAC addresses supported
2) the number of AP devices to the number of different beacons
supported
When you start abstracting it down to MAC addresses and BSSIDs these are
IMHO far less clear.
In any case, you're welcome to implement such an API as you're proposing
to demonstrate the feasibility and ease of use. But you probably should
first understand what is possible. And please don't confuse "MAC" and
"MAC address" too much.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
