CVS -C switch

[jbreeden at plumhall.com]

\> Is the host that is running hostapd with -C option in Master mode? Does it
> show anything strange in the hostapd debug?
>

Jouni, thanks for the quick response, and yes hostapd -C is in master mode.

Tried a few more tings today, first updated my CVS to today and tried
connecting hostapd -C to a Dlink 900AP with a number of sta versions, this is
what I got:
sta 0.7.6 - connected
sta 1.3.6 - would not connect
sta 1.4.9 - would not connect
sta 1.5.6 - connected

What I mean by connected is the log message "Associated (as station) with AP
00:05:5d:25:d5:db (aid=0)" after hostapd -C <hwdaddr> wlan0 is fired off.
as soon as the first data pdu (ping) issent, I get a deauthenticate an all
cases (0.7.6 and 1.5.6). This same behavior happens if hostapd -C is talking
to the Dlink or another hostapd runnimg in Master.
The logs on hostapd -C talking to the dlink shows a couple of things, one is:

handle_auth_cb: STA 00:05:5d:25:d5:db not found

and the other is:

unknown mgmt cb frame subtype 0

Both of these messages show up connecting to both the dlink and hostap. Unique
to the dlink is the following:
Association (as station) with AP 00:05:5d:25:d5:db failed (status_code=10)

followed by a successful association.

The full log (hostapd client in Master connecting to dlink):

Using interface wlan0ap with hwaddr 00:90:d1:07:27:1c and ssid 'test'
Flushing old station entries
Deauthenticate all stations
Authenticate with AP 00:05:5d:25:d5:db SSID=fuzzy2 (as station)
handle_auth_cb: STA 00:05:5d:25:d5:db not found
Authenticated (as station) with AP 00:05:5d:25:d5:db
Associate with AP 00:05:5d:25:d5:db SSID=fuzzy2 (as station)
unknown mgmt cb frame subtype 0
Association (as station) with AP 00:05:5d:25:d5:db failed (status_code=10)
Associated (as station) with AP 00:05:5d:25:d5:db (aid=0)

** first pdu (ping) sent from this client to dlink) **

Station 00:05:5d:25:d5:db trying to disassociate, but it is not associated.
Station 00:05:5d:25:d5:db trying to disassociate, but it is not associated.
...

The same with -d flag:

Opening raw packet socket for ifindex 4
Using interface wlan0ap with hwaddr 00:90:d1:07:27:1c and ssid 'test'
Flushing old station entries
Deauthenticate all stations
MGMT
mgmt::beacon
Authenticate with AP 00:05:5d:25:d5:db SSID=fuzzy2 (as station)
Beacon from 00:05:5d:25:d5:db SSID='fuzzy2' CHAN=3
Received 30 bytes management frame
  dump: b2 00 02 01 00 05 5d 25 d5 db 00 90 d1 07 27 1c 00 05 5d 25 d5 db 10
  89 00 00 01 00 00 00MGMT (TX callback) ACK
mgmt::auth cb
handle_auth_cb: STA 00:05:5d:25:d5:db not found
Received 30 bytes management frame
  dump: b0 00 d5 00 00 90 d1 07 27 1c 00 05 5d 25 d5 db 00 05 5d 25 d5 db b0
  c1 00 00 02 00 00 00MGMT
mgmt::auth
authentication: STA=00:05:5d:25:d5:db auth_alg=0 auth_transaction=2 status_code=0
Authenticated (as station) with AP 00:05:5d:25:d5:db
Associate with AP 00:05:5d:25:d5:db SSID=fuzzy2 (as station)
Received 42 bytes management frame
  dump: 02 00 02 01 00 05 5d 25 d5 db 00 90 d1 07 27 1c 00 05 5d 25 d5 db 20
  89 00 00 01 00 00 06 66 75 7a 7a 79 32 01 04 82 84 0b 16MGMT (TX callback) ACK
unknown mgmt cb frame subtype 0
Received 36 bytes management frame
  dump: 10 00 d5 00 00 90 d1 07 27 1c 00 05 5d 25 d5 db 00 05 5d 25 d5 db c0
  c1 01 00 0a 00 00 00 01 04 02 04 0b 96MGMT
mgmt::assoc_resp
Association (as station) with AP 00:05:5d:25:d5:db failed (status_code=10)
Associated (as station) with AP 00:05:5d:25:d5:db (aid=0)
...

You are right, it's a fireware issue. the first time I set it up it worked. I
was using cards with verious older sta versions, Some cards worked, others
didn't. In a flash of brillance I re-flashed them all to 1.4.9. Yep, you're
right - I don't know what those "older versions" where :-) duh...
When it worked, it was great - far better thruput than I was getting with WDS.
BTW, it's the same trick pre Cisco Aironet used on their old 350 APs.
-- 
John R. Breeden
jbreeden at plumhall.com
Kailua-Kona, Hawaii

---

This message (including any attachments) contains
confidential information intended for a specific
individual and purpose, and is protected by law.
If you are not the intended recipient, you should
delete this message and are hereby notified that
any disclosure, copying, or distribution of this
message, or the taking of any action based on it,
is strictly prohibited.

---