On 2012-07-30 3:36 PM, Johannes Berg wrote:

Ok so I'm chipping away at multi-channel operation, but WDS is
troubling. Which channel should it use? It doesn't even have channel
configuration today, but relies on having a channel already, but that
breaks when you have multi-channel since then it either has to have its
own channel or be slaved to another channel...

Anyone have any ideas?

Let's bind WDS interfaces to AP VIFs, then they can be slave to the AP's
channel context. This is necessary for my yet-to-be-resubmitted WDS
fixes anyway.

- Felix