From: Felix Fietkau <nbd@openwrt.org>
To: netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Johannes Berg <johannes@sipsolutions.net>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"
Date: Wed, 01 May 2013 21:02:29 +0200 [thread overview]
Message-ID: <518166C5.4080904@openwrt.org> (raw)
Hi,
commit 576eb62598f10c8c7fd75703fe89010cdcfff596
Author: stephen hemminger <shemminger@vyatta.com>
Date: Fri Dec 28 18:15:22 2012 +0000
bridge: respect RFC2863 operational state
This commit breaks putting a mac80211 4-address client mode interface in
a bridge and using it with WPA encryption.
wpa_supplicant has to receive EAP frames for authentication from the
bridge interface, since the rx handler hook steals them from the
wireless interface. However, it also keeps the interface operstate to
IF_OPER_DORMANT for as long as the WPA handshake is incomplete, which
causes the bridge code to drop EAP packets.
In the long run, I'd like to sort out this mess by passing EAP frames to
userspace via nl80211 - but since that will require userspace changes,
what do we do about this issue in the mean time?
- Felix
next reply other threads:[~2013-05-01 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:02 Felix Fietkau [this message]
2013-05-01 19:49 ` Regression in 3.9 caused by "bridge: respect RFC2863 operational state" Krishna Chaitanya
[not found] ` <CAOaVG179Rx_JfV99mbjWhwQTALb5gh+2_WVFWDSbngA0qkzoGw@mail.gmail.com>
2013-05-01 21:06 ` Felix Fietkau
2013-05-01 22:49 ` Stephen Hemminger
2013-05-02 0:53 ` Felix Fietkau
[not found] <CAFuUQkhHsRZMnNYBbVZU0=BcAKMEktzYgPv6oc=CMFd7MFDi6g@mail.gmail.com>
2015-12-04 2:31 ` YanBo
2016-01-19 15:45 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-01-19 21:10 ` YanBo
2016-01-19 21:48 ` Stephen Hemminger
2016-01-19 21:55 ` Felix Fietkau
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=518166C5.4080904@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=shemminger@vyatta.com \
/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).