linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Daniel Drake <drake@endlessm.com>,
	franky.lin@broadcom.com, hante.meuleman@broadcom.com,
	chi-hsien.lin@cypress.com, wright.feng@cypress.com
Cc: linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	brcm80211-dev-list@cypress.com,
	Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: Make brcmfmac repeat authentication requests
Date: Tue, 13 Feb 2018 10:50:48 +0100	[thread overview]
Message-ID: <5A82B4F8.2090209@broadcom.com> (raw)
In-Reply-To: <CAD8Lp47D5sGCpxSiFYQviu0a62W4aj-5Sgs6sjE7E2cZWwsUwg@mail.gmail.com>

On 2/12/2018 3:04 PM, Daniel Drake wrote:
> Hi,
>
> We are working with the Weibu F3C MiniPC which includes BCM43455 SDIO
> wifi chip 0x004345(17221) rev 0x000006
>
> Testing Linux 4.15, this wifi adapter is unable to authenticate with
> the MF928 MiFi Access Point which is common in Africa. The STA sends
> the authentication request, which is ACKed by the AP, but then the
> conversation ends there (a timeout later bubbles up to userspace).
> Windows 10 with broadcom driver version 1.605.1.0 is also unable to
> connect.

I tried to find info about that access point equipment, but not getting 
any hits apart from a olivetti laser printer, but I doubt it is that. 
Can you provide more details.

> My laptop with ath10k can authenticate and connect fine. There the
> conversation is:
>
> 1. STA sends authentication request
> 2. AP sends ACK
> 3. After 0.1s timeout, STA sends another auth request
> 4. AP sends ACK
> 5. AP sends authentication response
> 6. etc.
>
> Also confirmed the same pattern on a couple of smartphones, where the
> delay seems to be 0.3s before repeating the authentication request.
>
> Clearly this AP is not behaving correctly; the authentication request
> should not have to be repeated. However of all the devices to hand,
> unfortunately only this broadcom device is unable to connect.

User-space (wpa_supplicant) would retry the connect attempt so I guess 
you are saying that the timing between the two auth requests is important?

> Is there a way to adjust the driver/firmware to repeat the
> authentication requests when they are not responded to? This would
> match the behaviour of other devices and work around this issue.

Is firmware not repeating at all or is the time between the two auth 
requests too long?

Checking firmware there is a 300ms timeout and it does a retry if the 
limit is not reached. However, that limit is initialized to zero :-p

Could you try the patch below?

Regards,
Arend

diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c 
b/drivers
index 19686ef..af1ab00 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
@@ -384,6 +384,9 @@ int brcmf_c_preinit_dcmds(struct brcmf_if *ifp)
                 goto done;
         }

+       /* allow join retry by firmware */
+       (void)brcmf_fil_iovar_int_set(ifp, "assoc_retry_max", 1);
+
         /* Enable tx beamforming, errors can be ignored (not supported) */
         (void)brcmf_fil_iovar_int_set(ifp, "txbf", 1);



> Thanks
> Daniel
>

  reply	other threads:[~2018-02-13  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 14:04 Make brcmfmac repeat authentication requests Daniel Drake
2018-02-13  9:50 ` Arend van Spriel [this message]
2018-02-14 13:03   ` Daniel Drake
2018-02-15 12:46     ` Arend van Spriel
2018-02-16  7:36       ` Daniel Drake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A82B4F8.2090209@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211-dev-list@cypress.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=drake@endlessm.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=wright.feng@cypress.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).