ath6kl hostapd

ath6kl hostapd

[Anthony Ginger]

Hi All,

Can ath6kl support AP mode? If yes, how to config it? I tried a
simplest config, but can't find the AP.

I tried ath6kl driver in git://github.com/kvalo/ath6kl.git and the
standard kernel 3.3-rc3.
I am sure the HW is OK, wpa_supplicant works for me.
hostapd & wpa_supplicant is the latest version build form
git://w1.fi/srv/git/hostap.git,

hostapd -v
hostapd v1.0-rc2
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2012, Jouni Malinen <j@w1.fi> and contributors

Firmware is form linux-firmware, here is the kernel log:
[   14.534308] mmc1: new high speed SDIO card at address 0001
[   15.245538] ath6kl: ar6003 hw 2.1.1 sdio fw 3.1.1.609

I used the simplest config:
cat /etc/hostapd.conf
#change wlan0 to your wireless device
interface=wlan0
driver=nl80211
ssid=test
channel=1

here is the log:
hostapd -d /etc/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd.conf
nl80211: interface wlan0 in phy phy0
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Using driver-based roaming
nl80211: Add own interface ifindex 3
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Create interface iftype 6 (MONITOR)
Failed to create interface mon.wlan0: -95 (Operation not supported)
nl80211: Driver does not support monitor interface type - try to run without it
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz
nl80211: 2457-2482 @ 20 MHz
nl80211: 2474-2494 @ 20 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: Added 802.11b mode based on 802.11g information
Completing interface initialization
Mode: IEEE 802.11b  Channel: 1  Frequency: 2412 MHz
nl80211: Set freq 2412 (ht_enabled=0 sec_channel_offset=0)
Failed to update rate sets in kernel module
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x0
RATE[3] rate=110 flags=0x0
Flushing old station entries
Could not connect to kernel driver.
Deauthenticate all stations
nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=0
set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=1
set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=2
set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=3
set_tx=0 seq_len=0 key_len=0
Using interface wlan0 with hwaddr 00:03:7f:be:f0:a0 and ssid 'test'
nl80211: Set beacon (beacon_set=0)
nl80211: Ignore AP isolation configuration error since isolation is not used
wpa_driver_nl80211_set_operstate: operstate 0->1 (UP)
netlink: Operstate: linkmode=-1, operstate=6
Failed to set TX queue parameters for queue 0.
Failed to set TX queue parameters for queue 1.
Failed to set TX queue parameters for queue 2.
Failed to set TX queue parameters for queue 3.
wlan0: Setup of interface done.
RTM_NEWLINK: operstate=1 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Unknown event 5


Best Regards!
Tony

Re: ath6kl hostapd

[Kalle Valo]

Hi Anthony,

sorry for the late reply, I was sick a long time.

On 02/16/2012 01:30 PM, Anthony Ginger wrote:

> Can ath6kl support AP mode? If yes, how to config it? I tried a
> simplest config, but can't find the AP.

I have used AP mode only with wpasupplicant, I haven't tried with
hostapd yet. I would guess that ath6kl works with hostapd as well but of
course there can be some issues.

> I tried ath6kl driver in git://github.com/kvalo/ath6kl.git and the
> standard kernel 3.3-rc3.
> I am sure the HW is OK, wpa_supplicant works for me.
> hostapd & wpa_supplicant is the latest version build form
> git://w1.fi/srv/git/hostap.git,

This looks good.

> hostapd -v
> hostapd v1.0-rc2
> User space daemon for IEEE 802.11 AP management,
> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
> Copyright (c) 2002-2012, Jouni Malinen <j@w1.fi> and contributors
> 
> Firmware is form linux-firmware, here is the kernel log:
> [   14.534308] mmc1: new high speed SDIO card at address 0001
> [   15.245538] ath6kl: ar6003 hw 2.1.1 sdio fw 3.1.1.609

Ah, firmware is a bit old but IIRC it still should support AP mode. But
I need to submit latest firmware to linux-firmware.git.

> I used the simplest config:
> cat /etc/hostapd.conf
> #change wlan0 to your wireless device
> interface=wlan0
> driver=nl80211
> ssid=test
> channel=1
> 
> here is the log:
> hostapd -d /etc/hostapd.conf
> random: Trying to read entropy from /dev/random
> Configuration file: /etc/hostapd.conf
> nl80211: interface wlan0 in phy phy0
> rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
> nl80211: Using driver-based roaming
> nl80211: Add own interface ifindex 3
> nl80211: Set mode ifindex 3 iftype 3 (AP)
> nl80211: Create interface iftype 6 (MONITOR)
> Failed to create interface mon.wlan0: -95 (Operation not supported)
> nl80211: Driver does not support monitor interface type - try to run without it
> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
> nl80211: Regulatory information - country=00
> nl80211: 2402-2472 @ 40 MHz
> nl80211: 2457-2482 @ 20 MHz
> nl80211: 2474-2494 @ 20 MHz
> nl80211: 5170-5250 @ 40 MHz
> nl80211: 5735-5835 @ 40 MHz
> nl80211: Added 802.11b mode based on 802.11g information
> Completing interface initialization
> Mode: IEEE 802.11b  Channel: 1  Frequency: 2412 MHz
> nl80211: Set freq 2412 (ht_enabled=0 sec_channel_offset=0)
> Failed to update rate sets in kernel module
> RATE[0] rate=10 flags=0x1
> RATE[1] rate=20 flags=0x1
> RATE[2] rate=55 flags=0x0
> RATE[3] rate=110 flags=0x0
> Flushing old station entries
> Could not connect to kernel driver.
> Deauthenticate all stations
> nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=0
> set_tx=0 seq_len=0 key_len=0
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=1
> set_tx=0 seq_len=0 key_len=0
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=2
> set_tx=0 seq_len=0 key_len=0
> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=3
> set_tx=0 seq_len=0 key_len=0
> Using interface wlan0 with hwaddr 00:03:7f:be:f0:a0 and ssid 'test'
> nl80211: Set beacon (beacon_set=0)
> nl80211: Ignore AP isolation configuration error since isolation is not used
> wpa_driver_nl80211_set_operstate: operstate 0->1 (UP)
> netlink: Operstate: linkmode=-1, operstate=6
> Failed to set TX queue parameters for queue 0.
> Failed to set TX queue parameters for queue 1.
> Failed to set TX queue parameters for queue 2.
> Failed to set TX queue parameters for queue 3.
> wlan0: Setup of interface done.
> RTM_NEWLINK: operstate=1 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> Unknown event 5

>From the logs I can't identify what's wrong, but I have to admit that
I'm not very familiar with hostapd. I need to test this myself and I
will get back to you.

Kalle

Re: ath6kl hostapd

[Anthony Ginger]

Hi Kalle,

Thanks! My HW can work with the private Wifi driver(almost the same in
previous linux drivers\staging dir), both hostapd and wpasupplicant.
But I don't like that driver, if the new driver can work with hostapd,
I prefer switch to the new driver.
Take your time and take good care of yourself.

Best Regards!
Tony

2012/2/27 Kalle Valo <kvalo@qca.qualcomm.com>:
> Hi Anthony,
>
> sorry for the late reply, I was sick a long time.
>
> On 02/16/2012 01:30 PM, Anthony Ginger wrote:
>
>> Can ath6kl support AP mode? If yes, how to config it? I tried a
>> simplest config, but can't find the AP.
>
> I have used AP mode only with wpasupplicant, I haven't tried with
> hostapd yet. I would guess that ath6kl works with hostapd as well but of
> course there can be some issues.
>
>> I tried ath6kl driver in git://github.com/kvalo/ath6kl.git and the
>> standard kernel 3.3-rc3.
>> I am sure the HW is OK, wpa_supplicant works for me.
>> hostapd & wpa_supplicant is the latest version build form
>> git://w1.fi/srv/git/hostap.git,
>
> This looks good.
>
>> hostapd -v
>> hostapd v1.0-rc2
>> User space daemon for IEEE 802.11 AP management,
>> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
>> Copyright (c) 2002-2012, Jouni Malinen <j@w1.fi> and contributors
>>
>> Firmware is form linux-firmware, here is the kernel log:
>> [   14.534308] mmc1: new high speed SDIO card at address 0001
>> [   15.245538] ath6kl: ar6003 hw 2.1.1 sdio fw 3.1.1.609
>
> Ah, firmware is a bit old but IIRC it still should support AP mode. But
> I need to submit latest firmware to linux-firmware.git.
>
>> I used the simplest config:
>> cat /etc/hostapd.conf
>> #change wlan0 to your wireless device
>> interface=wlan0
>> driver=nl80211
>> ssid=test
>> channel=1
>>
>> here is the log:
>> hostapd -d /etc/hostapd.conf
>> random: Trying to read entropy from /dev/random
>> Configuration file: /etc/hostapd.conf
>> nl80211: interface wlan0 in phy phy0
>> rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
>> nl80211: Using driver-based roaming
>> nl80211: Add own interface ifindex 3
>> nl80211: Set mode ifindex 3 iftype 3 (AP)
>> nl80211: Create interface iftype 6 (MONITOR)
>> Failed to create interface mon.wlan0: -95 (Operation not supported)
>> nl80211: Driver does not support monitor interface type - try to run without it
>> BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
>> nl80211: Regulatory information - country=00
>> nl80211: 2402-2472 @ 40 MHz
>> nl80211: 2457-2482 @ 20 MHz
>> nl80211: 2474-2494 @ 20 MHz
>> nl80211: 5170-5250 @ 40 MHz
>> nl80211: 5735-5835 @ 40 MHz
>> nl80211: Added 802.11b mode based on 802.11g information
>> Completing interface initialization
>> Mode: IEEE 802.11b  Channel: 1  Frequency: 2412 MHz
>> nl80211: Set freq 2412 (ht_enabled=0 sec_channel_offset=0)
>> Failed to update rate sets in kernel module
>> RATE[0] rate=10 flags=0x1
>> RATE[1] rate=20 flags=0x1
>> RATE[2] rate=55 flags=0x0
>> RATE[3] rate=110 flags=0x0
>> Flushing old station entries
>> Could not connect to kernel driver.
>> Deauthenticate all stations
>> nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=0
>> set_tx=0 seq_len=0 key_len=0
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=1
>> set_tx=0 seq_len=0 key_len=0
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=2
>> set_tx=0 seq_len=0 key_len=0
>> wpa_driver_nl80211_set_key: ifindex=3 alg=0 addr=(nil) key_idx=3
>> set_tx=0 seq_len=0 key_len=0
>> Using interface wlan0 with hwaddr 00:03:7f:be:f0:a0 and ssid 'test'
>> nl80211: Set beacon (beacon_set=0)
>> nl80211: Ignore AP isolation configuration error since isolation is not used
>> wpa_driver_nl80211_set_operstate: operstate 0->1 (UP)
>> netlink: Operstate: linkmode=-1, operstate=6
>> Failed to set TX queue parameters for queue 0.
>> Failed to set TX queue parameters for queue 1.
>> Failed to set TX queue parameters for queue 2.
>> Failed to set TX queue parameters for queue 3.
>> wlan0: Setup of interface done.
>> RTM_NEWLINK: operstate=1 ifi_flags=0x1003 ([UP])
>> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>> Unknown event 5
>
> From the logs I can't identify what's wrong, but I have to admit that
> I'm not very familiar with hostapd. I need to test this myself and I
> will get back to you.
>
> Kalle

Re: ath6kl hostapd

[Kalle Valo]

On 02/27/2012 08:43 AM, Kalle Valo wrote:
> On 02/16/2012 01:30 PM, Anthony Ginger wrote:
> 
>> Can ath6kl support AP mode? If yes, how to config it? I tried a
>> simplest config, but can't find the AP.
> 
> I have used AP mode only with wpasupplicant, I haven't tried with
> hostapd yet. I would guess that ath6kl works with hostapd as well but of
> course there can be some issues.

Sorry for taking so long to answer but I finally tested this myself.

With latest firmware 3.2.0.144 (which I submitted to linux-firmware.git
yesterday) and latest hostapd from git I can create a WPA-PSK network
using hostapd and my Nokia N900 succesfully connected to the network and
I was able to ping N900.

If this is not working for you I recommend updating to the latest firmware.

Kalle

Re: ath6kl hostapd

[Jonathan Bagg]

On 12-04-11 04:54 AM, Kalle Valo wrote:
>
> With latest firmware 3.2.0.144 (which I submitted to linux-firmware.git
> yesterday) and latest hostapd from git I can create a WPA-PSK network
> using hostapd and my Nokia N900 succesfully connected to the network and
> I was able to ping N900.
>
> If this is not working for you I recommend updating to the latest firmware.
>
> Kalle
> --
> 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
Kalle,

When you tried hostapd on the N900, did you use a kernel built from your 
https://github.com/kvalo/ath6kl.git or from compat-wireless?

Jon

Re: ath6kl hostapd

[Kalle Valo]

On 05/01/2012 10:17 PM, Jonathan Bagg wrote:
> On 12-04-11 04:54 AM, Kalle Valo wrote:
>>
>> With latest firmware 3.2.0.144 (which I submitted to linux-firmware.git
>> yesterday) and latest hostapd from git I can create a WPA-PSK network
>> using hostapd and my Nokia N900 succesfully connected to the network and
>> I was able to ping N900.
>>
>> If this is not working for you I recommend updating to the latest firmware.
>
> When you tried hostapd on the N900, did you use a kernel built from your 
> https://github.com/kvalo/ath6kl.git or from compat-wireless?

Just to clarify: I was running hostapd on my x86 box which has ar6003
and I used N900 as the client connecting to the x86 box.

I used ath6kl.git for my tests. I use compat-wireless very little (if
any) in my tests.

Kalle

Re: ath6kl hostapd

[Kalle Valo]

On 05/02/2012 12:19 AM, Jonathan Bagg wrote:
> On 12-05-01 03:27 PM, Kalle Valo wrote:
>> On 05/01/2012 10:17 PM, Jonathan Bagg wrote:
>>>
>>> When you tried hostapd on the N900, did you use a kernel built from your 
>>> https://github.com/kvalo/ath6kl.git or from compat-wireless?
>> Just to clarify: I was running hostapd on my x86 box which has ar6003
>> and I used N900 as the client connecting to the x86 box.
>>
>> I used ath6kl.git for my tests. I use compat-wireless very little (if
>> any) in my tests.
>
> I can not get hostapd with ath6kl working with the following.....
> libnl 3.2.8
> hostapd v2.0-devel (cloned today)
> compat-wireless backport based on linux-next.git next-20120424
> kernel = 2.6.35.3 + freescale's patches
> platform = arm, imx51 babbage dev board
> 
> rfkill: Cannot open RFKILL control device
> nl80211: Failed to set interface wlan0 into AP mode
> nl80211 driver initialization failed.

That's strange. Does dmesg so anything? Are you sure that you are using
the correct version of ath6kl_sdio.ko and not some older version?

Also please enable full debug messages on hostapd and send a full log.

> I'll try and get your kernel from ath6kl.git to boot on my imx51 babbage
> dev board.

That might be challenging. I think it's easier if you add debug messages
and try to pinpoint where it is failing. For example
ath6kl_cfg80211_change_iface() is a good place to start debugging.

Kalle

Re: ath6kl hostapd

[Jonathan Bagg]

On 12-05-03 01:15 AM, Kalle Valo wrote:
>
> That might be challenging. I think it's easier if you add debug messages
> and try to pinpoint where it is failing. For example
> ath6kl_cfg80211_change_iface() is a good place to start debugging.
>
> Kalle
Kalle,

I tried again and it appears that sometimes (< 10 %) I can make 
connections to the ath6kl in AP mode.  Just to rule out any issues with 
my configs & tools, I setup a cw1200 sdio using the same software 
stack.  The cw1200 is working fine for me in AP mode and the output of 
hostapd is richer.  Any clues from the ath6kl hostapd output?


--------hostapd output using ath6kl-------

nl80211: Event message available
nl80211: New station d8:a2:5e:08:89:56
nl80211: Assoc Req IEs - hexdump(len=55): 00 09 4e 31 35 30 2d 66 30 30 
32 01 08 82 84 8b 96 24 30 48 6c 21 02 08 10 24 02 01 0e 32 04 0c 12 18 
60 dd 09 00 10 18 02 00 00 01 00 00 dd 07 00 50 f2 02 00 01 00
wlan0: Event ASSOC (0) received
wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
   New STA
ap_sta_add: register ap_handle_timer timeout for d8:a2:5e:08:89:56 (300 
seconds - ap_max_inactivity)
wlan0: STA d8:a2:5e:08:89:56 RADIUS: starting accounting session 
00000B62-00000000
IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS
hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for 
d8:a2:5e:08:89:56 (300 seconds - ap_max_inactivity)
Sending OFFER of 192.168.5.80
Sending OFFER of 192.168.5.80
Sending ACK to 192.168.5.80
Sending ACK to 192.168.5.80
Sending ACK to 192.168.5.80
random: Got 8/20 bytes from /dev/random
nl80211: Event message available


--------Same software stack, but with cw1200-------

wlan0: Event RX_MGMT (20) received
mgmt::auth
authentication: STA=d8:a2:5e:08:89:56 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
   New STA
ap_sta_add: register ap_handle_timer timeout for d8:a2:5e:08:89:56 (300 
seconds - ap_max_inactivity)
wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: authentication OK (open system)
wlan0: STA d8:a2:5e:08:89:56 MLME: 
MLME-AUTHENTICATE.indication(d8:a2:5e:08:89:56, OPEN_SYSTEM)
wlan0: STA d8:a2:5e:08:89:56 MLME: 
MLME-DELETEKEYS.request(d8:a2:5e:08:89:56)
authentication reply: STA=d8:a2:5e:08:89:56 auth_alg=0 
auth_transaction=2 resp=0 (IE len=0)
wlan0: Event TX_STATUS (18) received
mgmt::auth cb
wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: authenticated
wlan0: Event RX_MGMT (20) received
mgmt::assoc_req
association request: STA=d8:a2:5e:08:89:56 capab_info=0x21 
listen_interval=10
   new AID 1
wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: association OK (aid 1)
wlan0: Event TX_STATUS (18) received
mgmt::assoc_resp cb
wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: associated (aid 1)
wlan0: AP-STA-CONNECTED d8:a2:5e:08:89:56
wlan0: STA d8:a2:5e:08:89:56 MLME: 
MLME-ASSOCIATE.indication(d8:a2:5e:08:89:56)
wlan0: STA d8:a2:5e:08:89:56 MLME: 
MLME-DELETEKEYS.request(d8:a2:5e:08:89:56)
wlan0: STA d8:a2:5e:08:89:56 RADIUS: starting accounting session 
0000167A-00000000
IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS
hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for 
d8:a2:5e:08:89:56 (300 seconds - ap_max_inactivity)
nl80211: Event message available
nl80211: New station d8:a2:5e:08:89:56
Sending OFFER of 192.168.5.80
Sending OFFER of 192.168.5.80
Sending ACK to 192.168.5.80

Jon

Re: ath6kl hostapd

[Kalle Valo]

On 05/04/2012 11:30 PM, Jonathan Bagg wrote:
> On 12-05-03 01:15 AM, Kalle Valo wrote:
>>
>> That might be challenging. I think it's easier if you add debug messages
>> and try to pinpoint where it is failing. For example
>> ath6kl_cfg80211_change_iface() is a good place to start debugging.
> 
> I tried again and it appears that sometimes (< 10 %) I can make 
> connections to the ath6kl in AP mode.

What exactly happens when a connection fails? What client device are you
using?

> Just to rule out any issues with 
> my configs & tools, I setup a cw1200 sdio using the same software 
> stack.  The cw1200 is working fine for me in AP mode and the output of 
> hostapd is richer.

cw1200 is a mac80211 driver and the interface to user space is different
compared to fullmac devices like ath6kl. That's why the log output is
different.

> Any clues from the ath6kl hostapd output?
> 
> 
> --------hostapd output using ath6kl-------
> 
> nl80211: Event message available
> nl80211: New station d8:a2:5e:08:89:56
> nl80211: Assoc Req IEs - hexdump(len=55): 00 09 4e 31 35 30 2d 66 30 30 
> 32 01 08 82 84 8b 96 24 30 48 6c 21 02 08 10 24 02 01 0e 32 04 0c 12 18 
> 60 dd 09 00 10 18 02 00 00 01 00 00 dd 07 00 50 f2 02 00 01 00
> wlan0: Event ASSOC (0) received
> wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: associated
> STA did not include WPS/RSN/WPA IE in (Re)AssocReq
>    New STA
> ap_sta_add: register ap_handle_timer timeout for d8:a2:5e:08:89:56 (300 
> seconds - ap_max_inactivity)
> wlan0: STA d8:a2:5e:08:89:56 RADIUS: starting accounting session 
> 00000B62-00000000
> IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS
> hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for 
> d8:a2:5e:08:89:56 (300 seconds - ap_max_inactivity)
> Sending OFFER of 192.168.5.80
> Sending OFFER of 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80
> random: Got 8/20 bytes from /dev/random
> nl80211: Event message available

Is this from a failing case? From a quick look I don't see anything
wrong in the logs.

What are the symptoms when the connection fails? Did you check that this
isn't a higher level problem (wrong IP address etc)?

Kalle

Re: ath6kl hostapd

[Jonathan Bagg]

On 12-05-10 04:33 AM, Kalle Valo wrote:
> On 05/04/2012 11:30 PM, Jonathan Bagg wrote:
>> On 12-05-03 01:15 AM, Kalle Valo wrote:
>>> That might be challenging. I think it's easier if you add debug messages
>>> and try to pinpoint where it is failing. For example
>>> ath6kl_cfg80211_change_iface() is a good place to start debugging.
>> I tried again and it appears that sometimes (<  10 %) I can make
>> connections to the ath6kl in AP mode.
> What exactly happens when a connection fails? What client device are you
> using?
client = ipad and mac book

Udhcpd keeps sending offers and acks forever.
Sending OFFER of 192.168.5.80
Sending OFFER of 192.168.5.80
Sending ACK to 192.168.5.80
Sending ACK to 192.168.5.80
Sending ACK to 192.168.5.80
>
>> Any clues from the ath6kl hostapd output?
>>
>>
>> --------hostapd output using ath6kl-------
>>
>> nl80211: Event message available
>> nl80211: New station d8:a2:5e:08:89:56
>> nl80211: Assoc Req IEs - hexdump(len=55): 00 09 4e 31 35 30 2d 66 30 30
>> 32 01 08 82 84 8b 96 24 30 48 6c 21 02 08 10 24 02 01 0e 32 04 0c 12 18
>> 60 dd 09 00 10 18 02 00 00 01 00 00 dd 07 00 50 f2 02 00 01 00
>> wlan0: Event ASSOC (0) received
>> wlan0: STA d8:a2:5e:08:89:56 IEEE 802.11: associated
>> STA did not include WPS/RSN/WPA IE in (Re)AssocReq
>>     New STA
>> ap_sta_add: register ap_handle_timer timeout for d8:a2:5e:08:89:56 (300
>> seconds - ap_max_inactivity)
>> wlan0: STA d8:a2:5e:08:89:56 RADIUS: starting accounting session
>> 00000B62-00000000
>> IEEE 802.1X: Ignore STA - 802.1X not enabled or forced for WPS
>> hostapd_new_assoc_sta: reschedule ap_handle_timer timeout for
>> d8:a2:5e:08:89:56 (300 seconds - ap_max_inactivity)
>> Sending OFFER of 192.168.5.80
>> Sending OFFER of 192.168.5.80
>> Sending ACK to 192.168.5.80
>> Sending ACK to 192.168.5.80
>> Sending ACK to 192.168.5.80
>> random: Got 8/20 bytes from /dev/random
>> nl80211: Event message available
> Is this from a failing case? From a quick look I don't see anything
> wrong in the logs.
Good case.
> What are the symptoms when the connection fails? Did you check that this
> isn't a higher level problem (wrong IP address etc)?
I'm using the exact same configs for hostapd and udhcpd with the cw1200 
without an issue.  I'd like to try on x86.

Jon

Re: ath6kl hostapd

[Kalle Valo]

On 05/10/2012 09:31 PM, Jonathan Bagg wrote:
> On 12-05-10 04:33 AM, Kalle Valo wrote:
>> On 05/04/2012 11:30 PM, Jonathan Bagg wrote:
>>> On 12-05-03 01:15 AM, Kalle Valo wrote:
>>>> That might be challenging. I think it's easier if you add debug messages
>>>> and try to pinpoint where it is failing. For example
>>>> ath6kl_cfg80211_change_iface() is a good place to start debugging.
>>> I tried again and it appears that sometimes (<  10 %) I can make
>>> connections to the ath6kl in AP mode.
>> What exactly happens when a connection fails? What client device are you
>> using?
>
> client = ipad and mac book
> 
> Udhcpd keeps sending offers and acks forever.
> Sending OFFER of 192.168.5.80
> Sending OFFER of 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80
> Sending ACK to 192.168.5.80

Maybe it's a broadcast problem or something? Try with manual IPs and
then first run unicast ping separetely both from the client and the AP,
for example:

ping 192.168.5.1

If that works run broadcast ping separetely both from the client and the AP:

ping -b 192.168.1.255

Most likely you need to enable broadcast ping replies to get any answers:

echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts

And if MacOS doesn't support broadcast pings install a real operating
system ;)

Kalle