Hi Johannes,
That's a question of how you define "special data packet processing"... You're defining it purely in terms of the mechanics of how you handle them, but that's not really the point.
Why isn't it the point? These are the only data packets userspace management daemon(s) actually care about and has to setup raw sockets + bpf filters for every interface it manages. The current control port makes all of that unnecessary.
So from a holistic point of view, taking kernel + userspace into account, what is wrong with letting control port transport preauth frames if that saves a bunch of resources (and possibly wakeups if the bpf is setup badly) on the system?
Also, the question is what changed your mind? I asked you specifically if preauth should be included in the control port API and you thought it was a good idea at the time?
Preauth frames are _not_ special. They're entirely regular data packets as far as wifi is concerned.
Sure. I already conceded this point if this wasn't clear earlier. Regards, -Denis
