From: Jouni Malinen <j@w1.fi>
To: J Mo <jmomo@jmomo.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wpa_supplicant bridging problems
Date: Fri, 19 Feb 2016 21:39:36 +0200 [thread overview]
Message-ID: <20160219193936.GA24116@w1.fi> (raw)
In-Reply-To: <56C69232.6080200@jmomo.net>
On Thu, Feb 18, 2016 at 07:55:30PM -0800, J Mo wrote:
> This was a bug already fixed in git. The Debian wpa_supplicant is
> old (2.3). Source right now is pre-2.6. I compiled my own and it
> works fine.
> I suspect this was fixed in git commit
> e6dd8196e5daf39e4204ef8ecd26dd50fdca6040, but there are two other
> commits which also look like they are related to bridging and EAPOL.
That is not really a fix for the real problem.. It is only a workaround
to avoid the quite unfortunate and already years old kernel regression..
While that workaround covers some cases, it has a cost (more CPU use)
and it is possible to come up with sequences that break even that
workaround. Unfortunately, I'm not aware of any robust way of working
around this from user space without significant CPU load increase.
This thread from 2013 discusses that root issue:
http://marc.info/?l=linux-wireless&m=136743495526905&w=2
Unfortunately, there is still no fix for this in the kernel.. There is a
proposed fix that is included in OpenWrt, but it is unclear how this
issue could be fixed properly.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2016-02-19 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 3:30 wpa_supplicant bridging problems J Mo
2016-02-17 8:49 ` Simon Malthieu
2016-02-17 10:05 ` J Mo
2016-02-18 4:16 ` J Mo
2016-02-18 6:43 ` J Mo
2016-02-19 3:55 ` J Mo
2016-02-19 19:39 ` Jouni Malinen [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=20160219193936.GA24116@w1.fi \
--to=j@w1.fi \
--cc=jmomo@jmomo.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).