Linux wireless drivers development
 help / color / mirror / Atom feed
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, 27 Aug 2019 15:10:12 +0200	[thread overview]
Message-ID: <ac3fa1160afc5f4ccb1b41bd0b2e6dd165448180.camel@sipsolutions.net> (raw)
In-Reply-To: <21433c24-4860-be12-8d79-11e954e0bf9d@newmedia-net.de>

On Tue, 2019-08-27 at 15:08 +0200, Sebastian Gottschall wrote:
> Am 22.08.2019 um 23:06 schrieb Josef Miegl:
> > On August 22, 2019 10:08:13 PM GMT+02:00, Johannes Berg <johannes@sipsolutions.net> wrote:
> > > On Thu, 2019-08-22 at 09:00 +0200, Johannes Berg wrote:
> > > > Perhaps it expects the 4-way-HS to already be in 4-addr frame format,
> > > or
> > > > something else special in the 4-way-HS if you have WDS?
> > > I think this is actually the right guess.
> > Yes, it indeed it! Thank you so much Johannes!

> good finding. my idea here is if we parse the wds flags field from mtik 
> ie within mac80211 we could also support this special handing without 
> any workaround

The same holds true if we parse it in hostapd, and add a flag to the
EAPOL to control the encapsulation, which is way more general, so much
preferable IMHO.

johannes


  reply	other threads:[~2019-08-27 13:10 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 [this message]
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

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=ac3fa1160afc5f4ccb1b41bd0b2e6dd165448180.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