lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG1a4rvQTA7UgxLOxu_cC88grjHttyjPD_4kyDhb7Y9FcBBkLQ@mail.gmail.com>
Date:	Thu, 18 Aug 2011 00:01:34 -0400
From:	Pavel Ivanov <paivanof@...il.com>
To:	Gábor Stefanik <netrolller.3d@...il.com>
Cc:	"Luis R. Rodriguez" <lrodriguez@...eros.com>,
	Jouni Malinen <jmalinen@...eros.com>,
	Vasanthakumar Thiagarajan <vasanth@...eros.com>,
	Senthil Balasubramanian <senthilkumar@...eros.com>,
	linux-wireless@...r.kernel.org, ath9k-devel@...ts.ath9k.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ath9k: make driver usable standalone

> Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
> configuration tool.

I've just tried to use iw and it didn't quite work for me. Maybe it's
interfering with something installed in Ubuntu by default but
connect/disconnect commands didn't seem to do anything. And why these
commands can be executed only as root?
Well, maybe in Ubuntu 11.10 it will work better.


Pavel


2011/8/17 Gábor Stefanik <netrolller.3d@...il.com>:
> 2011/8/17 Pavel Ivanov <paivanof@...il.com>:
>>> WIRELESS_EXT is not required for configuring wireless on recent
>>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
>>
>> Since what version it's deprecated? Do user-space tools know about this new API?
>>
>> Neither iwconfig nor iwlist worked for me without WIRELESS_EXT.
>>
>>
>> Pavel
>>
>
> Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
> configuration tool.
>
>>
>> 2011/8/17 Gábor Stefanik <netrolller.3d@...il.com>:
>>> On Wed, Aug 17, 2011 at 5:28 AM, Pavel Ivanov <paivanof@...il.com> wrote:
>>>> When ath9k is the only wireless driver included in the build
>>>> WIRELESS_EXT configuration option becomes undefined. Because of that
>>>> driver becomes essentially unusable as you can't actually connect to
>>>> any WiFi network. By including WIRELESS_EXT into Kconfig we ensure
>>>> that build with ath9k and without other drivers (having WIRELESS_EXT
>>>> selected in their Kconfig) is actually usable.
>>>
>>> WIRELESS_EXT is not required for configuring wireless on recent
>>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
>>>
>>>>
>>>> Signed-off-by: Pavel Ivanov <paivanof@...il.com>
>>>> ---
>>>>
>>>> diff --git a/drivers/net/wireless/ath/ath9k/Kconfig
>>>> b/drivers/net/wireless/ath/ath9k/Kconfig
>>>> index d9c08c6..2573f77 100644
>>>> --- a/drivers/net/wireless/ath/ath9k/Kconfig
>>>> +++ b/drivers/net/wireless/ath/ath9k/Kconfig
>>>> @@ -11,6 +11,7 @@ config ATH9K
>>>>        select LEDS_CLASS
>>>>        select NEW_LEDS
>>>>        select ATH9K_COMMON
>>>> +       select WIRELESS_EXT
>>>>        ---help---
>>>>          This module adds support for wireless adapters based on
>>>>          Atheros IEEE 802.11n AR5008, AR9001 and AR9002 family
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ