Return-path: Received: from mail-la0-f51.google.com ([209.85.215.51]:50651 "EHLO mail-la0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751449AbaAWJ1i (ORCPT ); Thu, 23 Jan 2014 04:27:38 -0500 Received: by mail-la0-f51.google.com with SMTP id c6so1222439lan.38 for ; Thu, 23 Jan 2014 01:27:37 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <52DF947E.40800@gmail.com> <52E0BA40.7090203@gmail.com> <52E0D7D5.6060504@gmail.com> Date: Thu, 23 Jan 2014 11:27:37 +0200 Message-ID: (sfid-20140123_102744_250977_863AD498) Subject: Re: 802.11a is supported in AP mode or not? From: Emmanuel Grumbach To: "Liu, Bopeng" Cc: Krishna Chaitanya , zhuyj , linux-wireless Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Jan 23, 2014 at 11:21 AM, Liu, Bopeng wrote: > > > So,it that mean: there is no way to fix this problem by modify the kernel and driver codes? Yes > > Though #iwconfig wlan0 shows there is modes a ? In client mode - not in AP mode > > iwconfig wlan0 > wlan0 IEEE 802.11abgn ESSID:"IDPDK-169c" > Mode:Managed Frequency:2.462 GHz Access Point: A0:88:B4:1E:16:9C > Bit Rate=1 Mb/s Tx-Power=15 dBm > Retry long limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=60/70 Signal level=-50 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:14 Missed beacon:0 > >