From: Johannes Berg <johannes@sipsolutions.net>
To: Sebastian Gottschall <s.gottschall@newmedia-net.de>,
Josef Miegl <josef@miegl.cz>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Implementing Mikrotik IE
Date: Tue, 20 Aug 2019 14:22:08 +0200 [thread overview]
Message-ID: <bb0d7dd87a7821df245919c86458bd50a3d1a81e.camel@sipsolutions.net> (raw)
In-Reply-To: <b8009787-a182-d5f2-6dde-ee540c65a03b@newmedia-net.de>
On Tue, 2019-08-20 at 13:53 +0200, Sebastian Gottschall wrote:
> i was talking about a different scenario. its not about adding a
> element, but to read it back for gui for instance. this is why i made a
> patch which parses this special ie
> and adds the radioname as extra element to the station table. this works
> for ap as well of course. so iw ath0 station dump will print out the
> radio name if available
Oh. That's something I'd argue should just be implemented in hostapd
then? No need to do anything in the kernel for that.
johannes
next prev parent reply other threads:[~2019-08-20 12:22 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 [this message]
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
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=bb0d7dd87a7821df245919c86458bd50a3d1a81e.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