On 2016-01-19 22:48, Stephen Hemminger wrote: > On Thu, 3 Dec 2015 18:29:00 -0800 > YanBo <dreamfly281@xxxxxxxxx> 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 -- 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
