Re: What would it take to get WDS working with channel contexts?
On Fri, 2017-11-17 at 08:46 -0800, Ben Greear wrote: > It looks like my options are to hack the mac80211 stack to be minimally > functional with WDS and channel-contexts, or to hack ath10k driver to > disable chan-tx in order to try to fix the ath10k firmware WDS issues. > > I'd guess the former is of slightly more use to society. Do you have > any quick hacks to allow mac80211 to work with chantx and WDS, even > if you wouldn't want them upstream? No, I don't have anything like that, sorry. johannes
Re: What would it take to get WDS working with channel contexts?
On 11/17/2017 01:45 AM, Johannes Berg wrote: On Thu, 2017-11-16 at 16:28 -0800, Ben Greear wrote: I have a user interested in getting WDS working on ath10k, but evidently this is not supported since ath10k uses channel-contexts: From net/mac80211/main.c: /* * WDS is currently prohibited when channel contexts are used * because there's no clear definition of which channel WDS * type interfaces use */ Anyone have any suggestions as to how this could be made to work? You probably don't want to hear this, but: WDS isn't even properly working without them right now, since for example there's absolutely no feature negotiation between the peers as to which rates and other capabilities, bandwidths, etc. are acceptable (at any given moment in time). I therefore don't see any value in WDS mode at all unless these issues are fixed [*], and as such wouldn't want to take any patches that just do some minimal patching over to allow it with channel contexts. If you ask me, WDS is entirely useless without vendor-specific extensions to allow newer features, and the Linux "vendor-specific" extension to do that is AP/client 4-addr mode. johannes [*] and since the spec doesn't define this, you can't even fix them in any reasonable way, I think, unless you implement some vendor-specific things that maybe one vendor happens to do. It looks like my options are to hack the mac80211 stack to be minimally functional with WDS and channel-contexts, or to hack ath10k driver to disable chan-tx in order to try to fix the ath10k firmware WDS issues. I'd guess the former is of slightly more use to society. Do you have any quick hacks to allow mac80211 to work with chantx and WDS, even if you wouldn't want them upstream? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com
Re: What would it take to get WDS working with channel contexts?
On Thu, 2017-11-16 at 16:28 -0800, Ben Greear wrote: > I have a user interested in getting WDS working on ath10k, but evidently > this is not supported since ath10k uses channel-contexts: > > From net/mac80211/main.c: > > /* >* WDS is currently prohibited when channel contexts are used >* because there's no clear definition of which channel WDS >* type interfaces use >*/ > > > Anyone have any suggestions as to how this could be made to work? You probably don't want to hear this, but: WDS isn't even properly working without them right now, since for example there's absolutely no feature negotiation between the peers as to which rates and other capabilities, bandwidths, etc. are acceptable (at any given moment in time). I therefore don't see any value in WDS mode at all unless these issues are fixed [*], and as such wouldn't want to take any patches that just do some minimal patching over to allow it with channel contexts. If you ask me, WDS is entirely useless without vendor-specific extensions to allow newer features, and the Linux "vendor-specific" extension to do that is AP/client 4-addr mode. johannes [*] and since the spec doesn't define this, you can't even fix them in any reasonable way, I think, unless you implement some vendor-specific things that maybe one vendor happens to do.
What would it take to get WDS working with channel contexts?
I have a user interested in getting WDS working on ath10k, but evidently this is not supported since ath10k uses channel-contexts: From net/mac80211/main.c: /* * WDS is currently prohibited when channel contexts are used * because there's no clear definition of which channel WDS * type interfaces use */ Anyone have any suggestions as to how this could be made to work? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com
