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] [thread-next>] [day] [month] [year] [list]

Message-ID: <439966a35f064c7690f2ccbe7296c552@aphydexm01b.ap.qualcomm.com>
Date:	Tue, 19 Jan 2016 15:45:03 +0000
From:	"Shajakhan, Mohammed Shafi (Mohammed Shafi)" 
	<mohammed@....qualcomm.com>
To:	YanBo <dreamfly281@...il.com>, "nbd@...nwrt.org" <nbd@...nwrt.org>,
	"Malinen, Jouni" <jouni@....qualcomm.com>,
	"kvalo@...eaurora.org" <kvalo@...eaurora.org>
CC:	Stephen Hemminger <stephen@...workplumber.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" <hostap@...ts.infradead.org>
Subject: RE: Regression in 3.9 caused by "bridge: respect RFC2863 operational
 state"

Hi all,

Any updates on this please. 

Thanks,
shafi

-----Original Message-----
From: linux-wireless-owner@...r.kernel.org [mailto:linux-wireless-owner@...r.kernel.org] On Behalf Of YanBo
Sent: Friday, December 04, 2015 8:01 AM
To: nbd@...nwrt.org; Malinen, Jouni; kvalo@...eaurora.org
Cc: Stephen Hemminger; Krishna Chaitanya; linux-wireless; Sebastian Gottschall; Johannes Berg; netdev; hostap@...ts.infradead.org
Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state"

 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
> On Wed, May 1, 2013 at 5:53 PM, Felix Fietkau <nbd@...nwrt.org> wrote:
> >
> > On 2013-05-02 12:49 AM, Stephen Hemminger wrote:
> > > On Wed, 01 May 2013 23:06:16 +0200 Felix Fietkau <nbd@...nwrt.org> 
> > > wrote:
> > >
> > >> On 2013-05-01 10:21 PM, Stephen Hemminger wrote:
> > >> > What about using AF_PACKET bound to underlying wireless device 
> > >> > and the packet type. You can even use BPF to filter.
> > >> As far as I know, AF_PACKET only works when not binding it to the 
> > >> packet type (otherwise it get stolen by the rx handler).
> > >
> > > You can do AF_PACKET and it gets handle before rx_handler.
> > If I don't bind it to a protocol, it ends up in ptype_all, if I do, 
> > it ends up in &ptype_base. ptype_all is processed before the 
> > rx_handler, ptype_base is processed after the rx handler.
> > Hooking into ptype_all wastes tons of CPU cycles, hooking into 
> > ptype_base does not solve the problem.
> >
> > - Felix
> > --
> > To unsubscribe from this list: send the line "unsubscribe 
> > linux-wireless" in the body of a message to 
> > majordomo@...r.kernel.org More majordomo info at  
> > http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@...r.kernel.org More majordomo info at  http://vger.kernel.org/majordomo-info.html