Hello Johannes, > > In our case, we are experimenting with applications running along with > > hostapd and enabling band steering and client roaming functionality. > > As I mentioned, various approaches are being examined, including > > both pure nl80211-based approach as well as adding direct hooks > > to hostapd. > > To be honest, I'm torn on this. > > On the one hand, I think it's fairly reasonable functionality, but on > the other hand I'm not sure we should encourage such separate > approaches - it seems to me that will lead to a lot of fragmentation > and much harder debuggability for upstream where these things get used. > > It's also a bunch of code we have to maintain, for nothing that seems > of use to the community - since it's the sort of flexibility explicitly > designed for non-public code (otherwise it could just be part of > hostapd; actually it could even if it were non-public, at least in > theory, unless you're planning it as a value-add thing to go with an > open source hostapd ...). > > So while I don't want to stop you entirely in your tracks with this, > I'd really prefer you explore other options regarding where to put your > client steering functionality, perhaps even working on hostapd. Well, our preferred approach for these experiments is going to be communication with hostapd instead of kernel. One of the reasons is that GET_CMD_BEACON is not enough. We have to enable multiple listeners of mgmt frames as well. However that feature was rejected earlier this year: https://patchwork.kernel.org/patch/9615697 By the way, speaking about GET_CMD_BEACON and its possible users in the community. There is already a stub for it in nl80211 uapi headers. What was the original idea for that ? Or was it just a placeholder added together with SET_BEACON ? Regards, Sergey
