2009-03-04 21:33:24

by Alexey Yudichev

[permalink] [raw]
Subject: ath5k master (AP) mode

Hello,

I've just joined the list so don't know how to join the same thread so
to indicate that it's the same matter I use the same subject. I am
trying to make my "04:01.0 Ethernet controller: Atheros Communications
Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)" which is
identified by ath5k as
[=C2=A0=C2=A0 10.356742] ath5k phy0: Atheros AR5213A chip found (MAC: 0=
x59, PHY: 0x43)
[=C2=A0=C2=A0 10.356748] ath5k phy0: RF5112B multiband radio found (0x3=
6)
work in master mode.
I've patched /drivers/net/wireless/ath5k/base.c as was suggested, I
even put a debug printk() to make sure the patched version is used:


=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 printk(KERN_ERR "ath5k_pci: =
AP PATCH APPLIED!!!\n");
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hw->wiphy->interface_modes =3D
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 BIT(NL80211_IFTYPE_STATION) |
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 BIT(NL80211_IFTYPE_AP) |
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 BIT(NL80211_IFTYPE_ADHOC) |
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 BIT(NL80211_IFTYPE_MESH_POINT);


in dmesg I do see this:

[=C2=A0=C2=A0=C2=A0 9.899231] ath5k 0000:04:01.0: PCI INT A -> GSI 17 (=
level, low) -> IRQ 17
[=C2=A0=C2=A0=C2=A0 9.899272] ath5k 0000:04:01.0: registered as 'phy0'
[=C2=A0=C2=A0=C2=A0 9.899275] ath5k_pci: AP PATCH APPLIED!!!
[=C2=A0=C2=A0 10.356742] ath5k phy0: Atheros AR5213A chip found (MAC: 0=
x59, PHY: 0x43)
[=C2=A0=C2=A0 10.356748] ath5k phy0: RF5112B multiband radio found (0x3=
6)

however it still doesn't work:

# iwconfig wlan1 mode master
Error for wireless request "Set Mode" (8B06) :
=C2=A0=C2=A0=C2=A0 SET failed on device wlan1 ; Invalid argument.

Obviously I am missing something, but can't find what. Are there any
other prerequisites? Thanks!


2009-03-11 21:51:27

by Alexey Yudichev

[permalink] [raw]
Subject: Re: ath5k master (AP) mode

> On Tue, Mar 10, 2009 at 5:37 PM, Christoph .J Thompson
> <[email protected]> wrote:
>> On Tue, 10 Mar 2009 21:04:17 +0000
>> Alexey Yudichev <[email protected]> wrote:
>>> Do you know, if I got this far, can unstable connection and not
>>> working WPA be related to older kernel?
>>
>> I can't be sure. I don't have the unstable connection problem but I didn't
>> use WPA yet. So maybe the unstable connection problem only happens with WPA.
>
> It's possible ath5k has bugs in the crypto for AP mode like the ones fixed
> in ath9k recently - you can always try the nohwcrypt=1 modparam.
>
> --
> Bob Copeland %% http://www.bobcopeland.com
>
nohwcrypt=1 did not help (was I correct to put it as "options ath5k
nohwcrypt=1" into /etc/modprobe.d/options in my ubuntu?).

The problem is not that WPA does not work. It works for my WM6 client
(who connects with or without WPA from some 2nd or 3rd attempt but
cannot browse anything anyway even without encryption) but does not
work for WM5 client (who can browse but only when it connects and it
only connects with WPA disabled). Not sure which component to blame
here. Both devices work so nicely with WPA with hardware wireless
router :)

I guess I'll just wait for future versions of driver and kernel and
keep upgrading hoping that it'll start working.

2009-03-04 22:26:55

by Christoph .J Thompson

[permalink] [raw]
Subject: Re: ath5k master (AP) mode

On Wed, 4 Mar 2009 21:33:21 +0000
Alexey Yudichev <[email protected]> wrote:
> Hello,
>=20
> I've just joined the list so don't know how to join the same thread s=
o
> to indicate that it's the same matter I use the same subject. I am
> trying to make my "04:01.0 Ethernet controller: Atheros Communication=
s
> Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)" which is
> identified by ath5k as
> [=A0=A0 10.356742] ath5k phy0: Atheros AR5213A chip found (MAC: 0x59,=
PHY: 0x43)
> [=A0=A0 10.356748] ath5k phy0: RF5112B multiband radio found (0x36)

I have the exact same card (AR5001X+) working in master mode with hosta=
pd. What kernel version and hostapd version do you use?

--=20
Christoph .J Thompson <[email protected]>

2009-05-31 14:56:48

by Alexey Yudichev

[permalink] [raw]
Subject: Re: ath5k master (AP) mode

Just to finish the thread. After all the issues I had I decided to
wait until all patches make it into the official tree. Yesterday I've
downloaded the latest compat-wireless, hostapd 0.6.9, installed it and
everything worked out of the box, including open mode and WPA and on
both WM6 smartphone and WM5 pocket pc. And that's on 2.6.27-14 kernel
(currently latest ubuntu kernel). Thanks everybody for the great work!

>
> On Wed, Mar 11, 2009 at 10:51 PM, Alexey Yudichev <[email protected]> wrote:
>>
>> > On Tue, Mar 10, 2009 at 5:37 PM, Christoph .J Thompson
>> > <[email protected]> wrote:
>> >> On Tue, 10 Mar 2009 21:04:17 +0000
>> >> Alexey Yudichev <[email protected]> wrote:
>> >>> Do you know, if I got this far, can unstable connection and not
>> >>> working WPA be related to older kernel?
>> >>
>> >> I can't be sure. I don't have the unstable connection problem but I didn't
>> >> use WPA yet. So maybe the unstable connection problem only happens with WPA.
>> >
>> > It's possible ath5k has bugs in the crypto for AP mode like the ones fixed
>> > in ath9k recently - you can always try the nohwcrypt=1 modparam.
>> >
>> > --
>> > Bob Copeland %% http://www.bobcopeland.com
>> >
>> nohwcrypt=1 did not help (was I correct to put it as "options ath5k
>> nohwcrypt=1" into /etc/modprobe.d/options in my ubuntu?).
>>
>> The problem is not that WPA does not work. It works for my WM6 client
>> (who connects with or without WPA from some 2nd or 3rd attempt but
>> cannot browse anything anyway even without encryption) but does not
>> work for WM5 client (who can browse but only when it connects and it
>> only connects with WPA disabled). Not sure which component to blame
>> here. Both devices work so nicely with WPA with hardware wireless
>> router :)
>>
>> I guess I'll just wait for future versions of driver and kernel and
>> keep upgrading hoping that it'll start working.
>