netdev - Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <569EB0C5.7090005@openwrt.org>
Date:	Tue, 19 Jan 2016 22:55:17 +0100
From:	Felix Fietkau <nbd@...nwrt.org>
To:	Stephen Hemminger <stephen@...workplumber.org>,
	YanBo <dreamfly281@...il.com>
Cc:	jouni@....qualcomm.com, kvalo@...eaurora.org,
	Krishna Chaitanya <chaitanya.mgit@...il.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Sebastian Gottschall <s.gottschall@...wrt.com>,
	Johannes Berg <johannes@...solutions.net>,
	netdev <netdev@...r.kernel.org>, hostap@...ts.infradead.org
Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational
 state"

On 2016-01-19 22:48, Stephen Hemminger wrote:
> On Thu, 3 Dec 2015 18:29:00 -0800
> YanBo <dreamfly281@...il.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.
Wireless only the changes the operstate *after* successful
authentication, for which it needs to communicate through the bridge.

- Felix