From: Johannes Berg <johannes@sipsolutions.net>
To: Josef Miegl <josef@miegl.cz>,
Sebastian Gottschall <s.gottschall@newmedia-net.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Implementing Mikrotik IE
Date: Thu, 22 Aug 2019 08:58:47 +0200 [thread overview]
Message-ID: <a4df85e6c9ff221e89b970ecf3c39960f2b4cd56.camel@sipsolutions.net> (raw)
In-Reply-To: <E28FAC24-4B21-48FB-A010-770BCEF4CCA1@miegl.cz>
On Thu, 2019-08-22 at 01:57 +0200, Josef Miegl wrote:
> On August 20, 2019 2:36:21 PM GMT+02:00, Sebastian Gottschall <s.gottschall@newmedia-net.de> wrote:
> > i know. thats why i never even tried to contribute it upstream. but
> > from
> > hostapd side it was more complicated than just hacking mac80211
> > and from stations a second mod for wpa_supplicant would be needed and
> > since the dd-wrt webgui just uses nl80211 to show the station table
> > its more comportable and takes less code just todo it within the driver
> > i there is special interest in it i could of course try to clean it up
> > and make a upstream patch out of it
>
> I don't think something like Mikrotiks IE belongs to hostapd. The
> cleanest solution is probably parsing the IE and generating the IE for
> hostapd with an external tool, that can the dd-wrt GUI then use. I've
> made a simple C program for this, can share if you want.
Sebastian was talking about yet another case - namely recording it for
the stations, to be able to show it.
I guess hostapd could be made to just generally record *all* the
association request IEs that a station sent and make those available
over the control interface.
Alternatively, you could have another application just listen to nl80211
events, I guess.
Or even the kernel could capture *all*, but I don't see why we'd waste
unpageable kernel memory for it.
johannes
prev parent reply other threads:[~2019-08-22 6:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 15:28 Implementing Mikrotik IE Josef Miegl
2019-08-16 4:07 ` Sebastian Gottschall
2019-08-16 11:10 ` Josef Miegl
2019-08-16 11:15 ` Sebastian Gottschall
2019-08-16 11:38 ` Josef Miegl
2019-08-19 10:12 ` Johannes Berg
2019-08-19 11:37 ` Josef Miegl
2019-08-19 20:21 ` Johannes Berg
2019-08-21 20:04 ` Josef Miegl
2019-08-21 20:09 ` Sebastian Gottschall
2019-08-21 20:12 ` Johannes Berg
2019-08-21 21:17 ` Josef Miegl
2019-08-22 7:00 ` Johannes Berg
2019-08-22 20:08 ` Johannes Berg
2019-08-22 21:06 ` Josef Miegl
2019-08-23 10:54 ` Johannes Berg
2019-08-27 13:08 ` Sebastian Gottschall
2019-08-27 13:10 ` Johannes Berg
2019-08-27 13:14 ` Sebastian Gottschall
2019-08-20 11:53 ` Sebastian Gottschall
2019-08-20 12:22 ` Johannes Berg
2019-08-20 12:46 ` Sebastian Gottschall
2019-08-21 21:19 ` Josef Miegl
[not found] ` <8ec8202e-ca07-3594-5873-5b282d553711@newmedia-net.de>
2019-08-21 23:57 ` Josef Miegl
2019-08-22 6:58 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4df85e6c9ff221e89b970ecf3c39960f2b4cd56.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=josef@miegl.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@newmedia-net.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox