From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pa0-f54.google.com ([209.85.220.54]:35244 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932787AbcASVsZ (ORCPT ); Tue, 19 Jan 2016 16:48:25 -0500 Received: by mail-pa0-f54.google.com with SMTP id ho8so197098891pac.2 for ; Tue, 19 Jan 2016 13:48:25 -0800 (PST) Date: Tue, 19 Jan 2016 13:48:32 -0800 From: Stephen Hemminger To: YanBo Cc: Felix Fietkau , jouni@qca.qualcomm.com, kvalo@codeaurora.org, Krishna Chaitanya , linux-wireless , Sebastian Gottschall , Johannes Berg , netdev , hostap@lists.infradead.org Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state" Message-ID: <20160119134832.3ab2f04b@xeon-e3> (sfid-20160119_224830_874613_FE8C6CC0) In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 3 Dec 2015 18:29:00 -0800 YanBo 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Regression in 3.9 caused by "bridge: respect RFC2863 operational state" Date: Tue, 19 Jan 2016 13:48:32 -0800 Message-ID: <20160119134832.3ab2f04b@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Felix Fietkau , jouni-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org, kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, Krishna Chaitanya , linux-wireless , Sebastian Gottschall , Johannes Berg , netdev , hostap-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: YanBo Return-path: In-Reply-To: Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Thu, 3 Dec 2015 18:29:00 -0800 YanBo 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