From: Arend van Spriel <arend@broadcom.com>
To: "Jörg Krause" <jkrause@posteo.de>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 7/7] brcmfmac: add multiple BSS support.
Date: Sat, 27 Dec 2014 19:18:37 +0100 [thread overview]
Message-ID: <549EF7FD.5070702@broadcom.com> (raw)
In-Reply-To: <1417885078.22723.24.camel@posteo.de>
On 12/06/14 17:57, Jörg Krause wrote:
> First, I just subscribed to this mailing list and copied the subject
> from the archive. I didn't know better.
>
> Second, many thanks for this new feature to the Broadcom developers!
>
> I've tested this series of patches with the linux-next-20141205 kernel
> on a custom ARM board with a BCM43362 chip running a Linux system build
> with Buildroot. I'm using the wireless tools hostapd/wpa_supplicant 2.3.
>
> I was able to create a virtual interface:
> # iw dev wlan0 interface add wlan0_ap type __ap
>
> Add IP and set MAC:
> # ip addr add 192.168.2.1/24 broadcast 255.255.255.0 dev
> wlan0_ap
> # ip link set dev wlan0_ap address 12:34:56:78:ab:ce
>
> Start hostapd with the following minimal configuration:
> # cat /etc/hostapd-minimal.conf
> interface=wlan0_ap
> driver=nl80211
> ssid=myAP
> channel=1
> # hostapd -B /etc/hostapd-minimal.conf
>
> Start dnsmasq daemon with minimal configuration:
> # cat /etc/dnsmasq
> interface=wlan0_ap
> dhcp-range=192.168.2.2,192.168.2.254,24h
> # dnsmasq
>
>
> ifconfig shows:
> wlan0_ap Link encap:Ethernet HWaddr 12:34:56:78:AB:CE
> inet addr:192.168.2.1 Bcast:255.255.255.0
> Mask:255.255.255.0
> inet6 addr: fe80::1034:56ff:fe78:abce/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1 errors:0 dropped:1 overruns:0 frame:0
> TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:60 (60.0 B) TX bytes:20728 (20.2 KiB)
>
> Looks good so far.
>
> Unfortunatly, I do not see any SSID 'myAP', but an SSID
> 'BRCM_TEST_SSID'. Trying to associate with the SSID using wpa_supplicant
> 2.3 fails.
>
> Do I missed something within the setup?
Hi Jörg,
I looked at the 43362 firmware, ie. using hexdump -C, and it contains
the string BRCM_TEST_SSID. I already mentioned that being suspicious. So
it may be a firmware issue. I recently bought a Cubietruck device, which
has a 43362 module integrated, so I will try to replicate this.
Regards,
Arend
> Best regards
> Jörg Krause
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-27 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 16:57 [PATCH 7/7] brcmfmac: add multiple BSS support Jörg Krause
2014-12-06 18:17 ` Arend van Spriel
2014-12-06 19:19 ` Arend van Spriel
2014-12-06 20:07 ` Jörg Krause
2014-12-27 18:18 ` Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-03 20:05 [PATCH 0/7] brcmfmac: Multiple-BSS and PCIe fixes Arend van Spriel
2014-12-03 20:05 ` [PATCH 7/7] brcmfmac: add multiple BSS support Arend van Spriel
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=549EF7FD.5070702@broadcom.com \
--to=arend@broadcom.com \
--cc=jkrause@posteo.de \
--cc=linux-wireless@vger.kernel.org \
/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).