On 1/30/2018 10:09 AM, Rafał Miłecki wrote:
From: Rafał Miłecki <rafal@xxxxxxxxxx> When using 4366b1 and 4366c0 chipsets with more recent firmwares 1) 10.10 (TOB) (r663589) 2) 10.10.122.20 (r683106) respectively, it is impossible to use brcmfmac with interface in AP mode. With the AP interface bridged and multicast used, no STA will be able to associate; the STA will be immediately disassociated when attempting to associate. Debugging revealed this to be caused by a "faked" packet (generated by firmware), that is passed to the networking subsystem and then back to the firmware. Fortunately this packet is easily identified and can be detected and ignored as a workaround for misbehaving firmware.
I am actually wondering what this packet is. Have you checked in brcmf_msgbuf_process_rx_complete(). I am curious what buflen is there and what eth_type_trans() will do to the packet, ie. what protocol. As everything should be 802.3 we could/should add a length check of 14 bytes.
Regards, Arend
Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx> --- .../wireless/broadcom/brcm80211/brcmfmac/core.c | 46 ++++++++++++++++++++++ 1 file changed, 46 insertions(+)
