From patchwork Tue Dec 17 04:48:15 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: dhanajit.roy@wipro.com X-Patchwork-Id: 301992 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from maxx.maxx.shmoo.com (maxx.shmoo.com [205.134.188.171]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 5018E2C009B for ; Tue, 17 Dec 2013 15:48:36 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by maxx.maxx.shmoo.com (Postfix) with ESMTP id E99119D223; Mon, 16 Dec 2013 23:48:32 -0500 (EST) X-Virus-Scanned: amavisd-new at maxx.shmoo.com Received: from maxx.maxx.shmoo.com ([127.0.0.1]) by localhost (maxx.shmoo.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id im9AQoWdBmde; Mon, 16 Dec 2013 23:48:32 -0500 (EST) Received: from maxx.shmoo.com (localhost [127.0.0.1]) by maxx.maxx.shmoo.com (Postfix) with ESMTP id D30159D215; Mon, 16 Dec 2013 23:48:27 -0500 (EST) X-Original-To: mailman-post+hostap@maxx.shmoo.com Delivered-To: mailman-post+hostap@maxx.shmoo.com Received: from localhost (localhost [127.0.0.1]) by maxx.maxx.shmoo.com (Postfix) with ESMTP id 753729D215 for ; Mon, 16 Dec 2013 23:48:25 -0500 (EST) X-Virus-Scanned: amavisd-new at maxx.shmoo.com Received: from maxx.maxx.shmoo.com ([127.0.0.1]) by localhost (maxx.shmoo.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-9oWuUO7MIq for ; Mon, 16 Dec 2013 23:48:20 -0500 (EST) Received: from wipro-chn-out02.wipro.com (wipro-chn-out02.wipro.com [203.91.208.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "wipro-chn-out01.wipro.com", Issuer "VeriSign Class 3 International Server CA - G3" (not verified)) by maxx.maxx.shmoo.com (Postfix) with ESMTPS id CF2AE9D20F for ; Mon, 16 Dec 2013 23:48:19 -0500 (EST) X-AuditID: cb5bdd89-b7f9c8e000006cba-6d-52afd79096c6 Received: from CHN-OUT-EDG03.wipro.com ( [203.91.201.40]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by wipro-chn-out02.wipro.com (Symantec Mail Security) with SMTP id F3.F0.27834.097DFA25; Tue, 17 Dec 2013 10:18:16 +0530 (IST) Received: from CHN-SNR-MBX-1.wipro.com (10.142.51.141) by CHN-OUT-EDG03.wipro.com (203.91.201.40) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Dec 2013 10:18:15 +0530 Received: from CHN-SNR-MBX-2.wipro.com ([169.254.6.204]) by CHN-SNR-MBX-1.wipro.com ([169.254.5.132]) with mapi id 14.03.0158.001; Tue, 17 Dec 2013 10:18:17 +0530 From: To: Subject: [Hostapd] NEED_AP_MLME for hostapd when MLME is in firmware Thread-Topic: [Hostapd] NEED_AP_MLME for hostapd when MLME is in firmware Thread-Index: Ac764vrEw75bEoyoSqiis3fLgDRpnw== Date: Tue, 17 Dec 2013 04:48:15 +0000 Message-ID: <4B593B70622AB44FA0EFB5A9156A95EB7513522D@CHN-SNR-MBX-2.wipro.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.142.89.26] MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBJsWRmVeSWpSXmKPExsVyOvqkhu6E6+uDDE4uVrZY1PSAyYHRY/ep fSwBjFENjDaJeXn5JYklqQopqcXJtkrhmQVF+QoumcXJOYmZualFSgqZKbZKRkoKBTmJyam5 qXkltkqJBQWpeSlKdlwKGMAGqCwzTyE1Lzk/JTMv3VbJM9hf18LC1FLXUMkuJCNVITMvLb8o N7EkMz9PITk/ryThCk/Gtt9ZBdfcKu49bGFsYJxv3sXIySEhYCKx5fEGdghbTOLCvfVsXYxc HEIC05kkVnTuYIdwtjJKvJ4wlwXCWcYo8Xf6cbAWNgE5if7bB9hAbBEBGYmXm3+xgNjCAi4S 6/t3MHUxcgDFPSWunJGDKNGTuPV3LlgJi4CqxO4t18FaeQX8JLb2tIKNZAS64vupNUwgNrOA uMStJ/OZIK4TkFiy5zwzhC0q8fLxP1YIW0Hi9OxOVoh6HYkFuz+xQdjaEssWvmaGmC8ocXLm ExaQc4QElCUmX1GdwCg6C8mGWUi6ZyHpnoWkewEjyypGyXJQxOkmZ+Tp5peWGBjpgfl6yfm5 mxjBieBu5w7Gi9PsDjEKcDAq8fAWiK4PEmJNLCuuzD3EKMnBpCTK+/UyUIgvKT+lMiOxOCO+ qDQntfgQowQHs5IIL0sBUI43JbGyKrUoHyblCgysicxS3KB4BCaMeGMDA9wcJXFeI+upQUIC 6cDElp2aWpBaBDNHhoNDSYJ3xjWgFYJFqempFWmZOSUIaSYOTpAzeIDO2AVSw1tckJhbnJkO kT/FaMxx5uOHb4wc7x58/sYoxJKXn5cqJc67EKRUAKQ0ozQPbhosQ7xiFAcGgzDvHpAqHmB2 gZv3CmgVE9Cq52vWgawCZg24lFQDozHj2diA7KSNRXoLmznaCurWXY9sOqcS6LXixMI1NXei 5ofZCD/99/SfzWun90pBHd/8D11ceXHyLZefP14ZfvvDu64t7cZJgTK23x3uhnI+oVO9Qx/b 8TMkGeonH2+a8mUr+560Sde2vLsfXGXZpXolfCJHrNHbGBeWa3v9uXcvLbs0m+X9fSWW4oxE Qy3mouJEAKV3Q97rAwAA X-BeenThere: hostap@lists.shmoo.com X-Mailman-Version: 2.1.11 Precedence: list List-Id: HostAP Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hostap-bounces@lists.shmoo.com Errors-To: hostap-bounces@lists.shmoo.com Hi, I am working on a project , where WLAN is a full mac device. I need to enable softap . MLME for access point mode gets handled inside firmware . In that case , do I need to disable NEED_AP_MLME in Hostapd build configuration . But it seems by default NEED_AP_MLME is enabled with driver_nl80211. Will it be correct to disable the NEED_AP_MLME or any other alternative is available . Please suggest. I am looking at wpa_supplicant version '2.0-devel' codebase ( Android Jellybean 4.3 AOSP). Regards Dhanajit -----Original Message----- From: hostap-bounces@lists.shmoo.com [mailto:hostap-bounces@lists.shmoo.com] On Behalf Of hostap-request@lists.shmoo.com Sent: 13 December 2013 22:30 To: hostap@lists.shmoo.com Subject: HostAP Digest, Vol 128, Issue 12 Send HostAP mailing list submissions to hostap@lists.shmoo.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.shmoo.com/mailman/listinfo/hostap or, via email, send a message with subject or body 'help' to hostap-request@lists.shmoo.com You can reach the person managing the list at hostap-owner@lists.shmoo.com When replying, please edit your Subject line so it is more specific than "Re: Contents of HostAP digest..." Today's Topics: 1. [Patch] IEEE80211R: Support FT-OVER-DS when use driver as SME (Zhiyuan Yang) 2. [PATCH] hostapd: Clean interface_added flag (Marek Kwaczynski) 3. Re: Linux wifi monitor interface type for A20/BCM4329/BCM4330 (Arend van Spriel) 4. Re: Linux wifi monitor interface type for A20/BCM4329/BCM4330 (Arend van Spriel) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Dec 2013 23:40:48 -0800 From: Zhiyuan Yang Subject: [Patch] IEEE80211R: Support FT-OVER-DS when use driver as SME To: "hostap@lists.shmoo.com" , "j@w1.fi" Cc: Kevin Gan , Cathy Luo , Tristan Xu Message-ID: <23E65EE4544D484CBE73B588E192C6D620B538C878@sc-vexch3.marvell.com> Content-Type: text/plain; charset="us-ascii" Hi, This patch is to support IEEE80211R FT-OVER-DS when use driver as SME. When use command FT_DS , FT action will be refused when not use wpa supplicant as SME. As follow: if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_SME)) return; /* only SME case supported for now */ Delete this check, and add some other changes to support ft-over-ds when use driver as SME. This changes will not affect ft-over-ds when use WPA supplicant as SME. Thanks BR zhiyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-IEEE80211R-support-ft-over-ds-when-use-driver-as-sme.patch Type: application/octet-stream Size: 2067 bytes Desc: 0001-IEEE80211R-support-ft-over-ds-when-use-driver-as-sme.patch URL: ------------------------------ Message: 2 Date: Fri, 13 Dec 2013 10:32:36 +0100 From: Marek Kwaczynski Subject: [PATCH] hostapd: Clean interface_added flag To: hostap@lists.shmoo.com Cc: j@w1.fi Message-ID: <1386927156-3973-1-git-send-email-marek.kwaczynski@tieto.com> If more BSS networks are added in config file than are supported by the driver, segmantation fault can appear. For this case clean interface_added flag is needed when adding new BSS failed. Signed-hostap: Marek Kwaczynski --- Without this fix I saw segmantation fault or "wlan0: Could not connect to kernel driver" in hostapd when I added more BSS networks in config file than are supported by the driver. For example when I created the following BSSs in config file: 1) wlan0 2) wlan0-1 3) wlan0-2 4) wlan0-3 and the last one couldn't be added because it wasn't supported by the driver, I received the following debug print: nl80211: Adding interface wlan0-3 into bridge br-lan Could not set interface wlan0-3 flags (UP): Device or resource busy After that when I killed hostapd, it tried to remove wlan0-3 and delete global bss pointer - wlan0 src/ap/hostapd.c | 1 + 1 file changed, 1 insertion(+) -- 1.7.9.5 ------------------------------ Message: 3 Date: Fri, 13 Dec 2013 14:08:32 +0100 From: Arend van Spriel Subject: Re: Linux wifi monitor interface type for A20/BCM4329/BCM4330 To: Axel Christiansen , , "hostap@lists.shmoo.com" Message-ID: <52AB06D0.2020906@broadcom.com> Content-Type: text/plain; charset="UTF-8"; format=flowed + hostap list On 12/13/2013 02:04 PM, Axel Christiansen wrote: > Am 13.12.2013 13:22:50, schrieb Arend van Spriel: > > On 12/13/2013 12:51 PM, Axel Christiansen wrote: > > Hello dear Developer. > > > Hopefully this mail is getting through. > > I was wondering if one can tell me about the support f?r > interface type > monitor for: > > driver brcmfmac, os linux, arch arm, hardware BCM4329 or BCM4330 > > Does it work? > When is it expected to work? > > > I got one of those really nice cubieboards/A20 SBC with > integrated wifi > and sadly without monitor interface WPA-encyption as > access-point will > not work. > > > what kernel version are you using? brcmfmac does not need monitor > interface for AP operation. > > Gr. AvS > > > > AP Mode works fine. I belief for encryption especially WPA/WPA2 on Linux > the hostap daemon is widely used. hostapd itself needs that monitor > interface, if i am not too much mistaken. If I am not mistaken you need either monitor interface or support for mgmt_rx. brcmfmac has mgmt_rx support. Regards, Arend > Kernel 3.4 > > > thx, Axel > > > > > > ------------------------------ Message: 4 Date: Fri, 13 Dec 2013 15:44:59 +0100 From: Arend van Spriel Subject: Re: Linux wifi monitor interface type for A20/BCM4329/BCM4330 To: Axel Christiansen , , Message-ID: <52AB1D6B.1030205@broadcom.com> Content-Type: text/plain; charset="UTF-8"; format=flowed On 12/13/2013 02:33 PM, Axel Christiansen wrote: > Am 13.12.2013 14:08:32, schrieb Arend van Spriel: > > + hostap list > > On 12/13/2013 02:04 PM, Axel Christiansen wrote: > > Am 13.12.2013 13:22:50, schrieb Arend van Spriel: > > On 12/13/2013 12:51 PM, Axel Christiansen wrote: > > Hello dear Developer. > > > Hopefully this mail is getting through. > > I was wondering if one can tell me about the support f?r > interface type > monitor for: > > driver brcmfmac, os linux, arch arm, hardware BCM4329 or BCM4330 > > Does it work? > When is it expected to work? > > > I got one of those really nice cubieboards/A20 SBC with > integrated wifi > and sadly without monitor interface WPA-encyption as > access-point will > not work. > > > what kernel version are you using? brcmfmac does not need monitor > interface for AP operation. > > Gr. AvS > > > > AP Mode works fine. I belief for encryption especially WPA/WPA2 > on Linux > the hostap daemon is widely used. hostapd itself needs that monitor > interface, if i am not too much mistaken. > > > If I am not mistaken you need either monitor interface or support for > mgmt_rx. brcmfmac has mgmt_rx support. > > Regards, > Arend > > > > That sound promising. Thx a lot. The bad news is the kernel version. I think 3.4 will give some issues using brcmfmac in AP mode. Regards, Arend > > > Regards. Axel > > > > ------------------------------ diff --git a/src/ap/hostapd.c b/src/ap/hostapd.c index 6fe2956..a436c2a 100644 --- a/src/ap/hostapd.c +++ b/src/ap/hostapd.c @@ -667,6 +667,7 @@ static int hostapd_setup_bss(struct hostapd_data *hapd, int first) NULL, first == -1)) { wpa_printf(MSG_ERROR, "Failed to add BSS (BSSID=" MACSTR ")", MAC2STR(hapd->own_addr)); + hapd->interface_added = 0; return -1; } }