From: rosenp@gmail.com
To: Russell King - ARM Linux <linux@armlinux.org.uk>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: AP mode with Broadcom 4330
Date: Mon, 14 Aug 2017 23:25:03 -0700 [thread overview]
Message-ID: <1502778303.2319.2.camel@gmail.com> (raw)
In-Reply-To: <20170814233028.GK20805@n2100.armlinux.org.uk>
If using rtlwifi, you could try using rtl8xxxu and see if you get
similar results. ¯\_(ツ)_/¯
On Tue, 2017-08-15 at 00:30 +0100, Russell King - ARM Linux wrote:
> On Fri, Jul 28, 2017 at 09:50:21PM +0200, Arend van Spriel wrote:
> > On 28-07-17 19:49, Russell King - ARM Linux wrote:
> > > Replacing that "(!mbss)" with "mbss" results in AP mode working
> > > on the
> > > 4330. However, I suspect:
> > >
> > > if (brcmf_feat_is_enabled(ifp, BRCMF_FEAT_MBSS))
> > > brcmf_fil_iovar_int_set(ifp, "mbss", mbss);
> > >
> > > actually makes much more sense.
> > >
> > > Given that this is direct firmware interaction, I can't say which
> > > is
> > > correct - all I can say is that mainline kernels are currently
> > > broken.
> >
> > Indeed. I have to come up with a proper fix for both scenarios.
> > Thanks
> > for the report.
>
> I'm now on 4.13-rc4, and running with my patch. I've configured AP
> mode:
>
> Interface wlan0
> ifindex 3
> wdev 0x1
> addr 6c:ad:f8:1d:4c:d9
> ssid Time
> type AP
> wiphy 0
> channel 5 (2432 MHz), width: 20 MHz, center1: 2432 MHz
>
> using NetworkManager with a WPA2 key. However, a Realtek RTL8192EU
> client is trying to connect to it, but is unable:
>
> [ 1750.497436] wlan0: authenticate with 6c:ad:f8:1d:4c:d9
> [ 1750.530929] wlan0: send auth to 6c:ad:f8:1d:4c:d9 (try 1/3)
> [ 1750.738795] wlan0: send auth to 6c:ad:f8:1d:4c:d9 (try 2/3)
> [ 1750.946780] wlan0: send auth to 6c:ad:f8:1d:4c:d9 (try 3/3)
> [ 1751.154764] wlan0: authentication with 6c:ad:f8:1d:4c:d9 timed out
>
> The antennas are definitely within range (finger to thumb distance)
> and the Realtek can definitely see the BCM4330 in AP mode. I don't
> see the interrupts for the SDIO interface increment while the client
> tries to connect.
>
> The WPA2 password is definitely the same on both ends.
>
> Any ideas how to debug this?
>
> Thanks.
>
next prev parent reply other threads:[~2017-08-15 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 14:15 AP mode with Broadcom 4330 Russell King - ARM Linux
2017-07-28 17:49 ` Russell King - ARM Linux
2017-07-28 19:50 ` Arend van Spriel
2017-07-31 12:59 ` Russell King - ARM Linux
2017-07-31 20:28 ` Arend van Spriel
2017-11-14 23:07 ` Russell King - ARM Linux
2017-11-15 8:47 ` Arend van Spriel
2017-08-14 23:30 ` Russell King - ARM Linux
2017-08-15 6:25 ` rosenp [this message]
2017-08-15 8:22 ` Russell King - ARM Linux
2017-08-15 9:42 ` Arend van Spriel
2017-08-15 9:58 ` Russell King - ARM Linux
2017-08-15 10:29 ` Russell King - ARM Linux
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=1502778303.2319.2.camel@gmail.com \
--to=rosenp@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).