From: Stephen Hemminger <stephen@networkplumber.org>
To: YanBo <dreamfly281@gmail.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
jouni@qca.qualcomm.com, kvalo@codeaurora.org,
Krishna Chaitanya <chaitanya.mgit@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Johannes Berg <johannes@sipsolutions.net>,
netdev <netdev@vger.kernel.org>,
hostap@lists.infradead.org
Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"
Date: Tue, 19 Jan 2016 13:48:32 -0800 [thread overview]
Message-ID: <20160119134832.3ab2f04b@xeon-e3> (raw)
In-Reply-To: <CAFuUQkhHsRZMnNYBbVZU0=BcAKMEktzYgPv6oc=CMFd7MFDi6g@mail.gmail.com>
On Thu, 3 Dec 2015 18:29:00 -0800
YanBo <dreamfly281@gmail.com> wrote:
> Sorry to pick up this thread again, it looks this issue still existed in
> the newer 4.3 kernel. (The EAP frames can not be received by wireless
> interface due to the bridge interface,
> http://marc.info/?l=linux-wireless&m=136743495526905&w=2)
>
> Wonder is anyone know some update for this issue? Currently the only
> workaround is make the 4-address AP and STA associated in security mode
> firstly and then create the bridge, the renew key configuration also need
> be disable at the hostapd side to avoid renew the key at bridge status.
>
> Thanks
> Yanbo
How does wireless device indicate that is up? It may just be that
the code is missing the logic to propagate operstate correctly.
This is normally done by netif_stacked_transfer_operstate and linkwatch
event.
Also STP can be disabled if you don't need it.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: YanBo <dreamfly281-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Felix Fietkau <nbd-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>,
jouni-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org,
kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
Krishna Chaitanya
<chaitanya.mgit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sebastian Gottschall
<s.gottschall-t37Kgv3TaIPQT0dZR+AlfA@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
hostap-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"
Date: Tue, 19 Jan 2016 13:48:32 -0800 [thread overview]
Message-ID: <20160119134832.3ab2f04b@xeon-e3> (raw)
In-Reply-To: <CAFuUQkhHsRZMnNYBbVZU0=BcAKMEktzYgPv6oc=CMFd7MFDi6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 3 Dec 2015 18:29:00 -0800
YanBo <dreamfly281-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Sorry to pick up this thread again, it looks this issue still existed in
> the newer 4.3 kernel. (The EAP frames can not be received by wireless
> interface due to the bridge interface,
> http://marc.info/?l=linux-wireless&m=136743495526905&w=2)
>
> Wonder is anyone know some update for this issue? Currently the only
> workaround is make the 4-address AP and STA associated in security mode
> firstly and then create the bridge, the renew key configuration also need
> be disable at the hostapd side to avoid renew the key at bridge status.
>
> Thanks
> Yanbo
How does wireless device indicate that is up? It may just be that
the code is missing the logic to propagate operstate correctly.
This is normally done by netif_stacked_transfer_operstate and linkwatch
event.
Also STP can be disabled if you don't need it.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-19 21:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFuUQkhHsRZMnNYBbVZU0=BcAKMEktzYgPv6oc=CMFd7MFDi6g@mail.gmail.com>
2015-12-04 2:31 ` Regression in 3.9 caused by "bridge: respect RFC2863 operational state" YanBo
2016-01-19 15:45 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-01-19 15:45 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-01-19 21:10 ` YanBo
2016-01-19 21:10 ` YanBo
2016-01-19 21:48 ` Stephen Hemminger [this message]
2016-01-19 21:48 ` Stephen Hemminger
2016-01-19 21:55 ` Felix Fietkau
2016-01-19 21:55 ` Felix Fietkau
2013-05-01 19:02 Felix Fietkau
2013-05-01 19:49 ` Krishna Chaitanya
2013-05-01 19:49 ` Krishna Chaitanya
[not found] ` <CAOaVG179Rx_JfV99mbjWhwQTALb5gh+2_WVFWDSbngA0qkzoGw@mail.gmail.com>
2013-05-01 21:06 ` Felix Fietkau
2013-05-01 21:06 ` Felix Fietkau
2013-05-01 22:49 ` Stephen Hemminger
2013-05-01 22:49 ` Stephen Hemminger
2013-05-02 0:53 ` Felix Fietkau
2013-05-02 0:53 ` 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=20160119134832.3ab2f04b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=chaitanya.mgit@gmail.com \
--cc=dreamfly281@gmail.com \
--cc=hostap@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=s.gottschall@dd-wrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.