There is a fixing in http://git.openwrt.org/?p=openwrt.git;a=blob_plain;f=target/linux/generic/patches-4.3/120-bridge_allow_receiption_on_disabled_port.patch for your reference. Yanbo On Tue, Jan 19, 2016 at 7:45 AM, Shajakhan, Mohammed Shafi (Mohammed Shafi) <mohammed@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > Any updates on this please. > > Thanks, > shafi > > -----Original Message----- > From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless-owner@xxxxxxxxxxxxxxx] On Behalf Of YanBo > Sent: Friday, December 04, 2015 8:01 AM > To: nbd@xxxxxxxxxxx; Malinen, Jouni; kvalo@xxxxxxxxxxxxxx > Cc: Stephen Hemminger; Krishna Chaitanya; linux-wireless; Sebastian Gottschall; Johannes Berg; netdev; hostap@xxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxx> wrote: >> > >> > On 2013-05-02 12:49 AM, Stephen Hemminger wrote: >> > > On Wed, 01 May 2013 23:06:16 +0200 Felix Fietkau <nbd@xxxxxxxxxxx> >> > > 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@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
