From bmeier  Tue Nov  1 05:25:57 2005
From: bmeier (Beat Meier)
Date: Tue, 01 Nov 2005 10:25:57 -0300
Subject: wpa_supplicant-0.4.6 with madwifi-ng now compiles but does still not
	associate to hostapd
Message-ID: <43676CE5.6080109@infovia.com.ar>

Hi

At least I were able to compile hostapd-0.4.6. and wpa_supplicant-0.4.6 
with kernel 2.6.14 and WE19 and
madwifi-ng (), but wpa_supplicant it still doesn't work.
With kernel 2.6.12 and madnwifi-ng it was the same.
wpa_supplicant cannot connect to hostapd. It "hangs" by scanning. Last 
messages below.

Nov 01 09:40:05.902507: Added interface ath0
Nov 01 09:40:05.904041: Wireless event: cmd=0x8b06 len=8
Nov 01 09:40:05.905437: Ignore event for foreign ifindex 3
Nov 01 09:40:05.906722: RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Nov 01 09:40:05.908131: RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Nov 01 09:40:06.003678: State: DISCONNECTED -> SCANNING
Nov 01 09:40:06.004720: Starting AP scan (broadcast SSID)
Nov 01 09:40:06.005970: Wireless event: cmd=0x8b1a len=8

Have also tried to use with scan_ssid=1 but it's the same. It hangs ...
Any idea what's wrong?

Has anybody running wpa_supplicant with madwifi-ng?

wpa_supplicant-0.4.3 with old madwifi-bsd-driver works well to
hostapd-0.4.6 with madwifi-ns so the problem is really in wpa_supplicant.
I think there is something wrong with the ioctls in driver_madwifi.c.

Jouni  have you used already madwifi-ng???

Beat




From bmeier  Tue Nov  1 06:52:45 2005
From: bmeier (Beat Meier)
Date: Tue, 01 Nov 2005 11:52:45 -0300
Subject: wpa_supplicant-0.4.6 with madwifi-ng now compiles but does still
	not	associate to hostapd
In-Reply-To: <43676CE5.6080109@infovia.com.ar>
References: <43676CE5.6080109@infovia.com.ar>
Message-ID: <4367813D.2090408@infovia.com.ar>

BTW:

If you want compile wpa_supplicant-0.4.6 you have to copy original 
wirless.h to wireless_copy.h and
You must include
 #include <sys/socket.h>
in the following files
driver_hostap.c
driver_atmel.c




From chip  Tue Nov  1 18:58:44 2005
From: chip (Chip Salzenberg)
Date: Tue, 1 Nov 2005 18:58:44 -0800
Subject: "wifi0: interrupt delivery does not seem to work"
In-Reply-To: <20051031235200.GH6993@tytlal.topaz.cx>
References: <20051031013349.GA24013@tytlal.topaz.cx>
	<20051031235200.GH6993@tytlal.topaz.cx>
Message-ID: <20051102025844.GA6610@tytlal.topaz.cx>

Version 0.3.9 under kernel 2.6.12 works fine.

Version 0.4.4-kernel included with kernel 2.6.14 does not work, nor
does version 0.4.1 compiled separately; there seems to be a problem
with interrupt delivery.  As long as the module is installed,
keystrokes and all other interrupt-driven activity pause for a LONG
time.  In fact, often keystrokes will auto-repeat as the interrupt for
the key-raise event gets delayed.

C'mon guys, anybody have a clue here?  Anybody?  I'd like to use the
2.6.14 kernel, but hostap is holding back the upgrade.

Oct 29 16:34:11 tytlal kernel: usb 2-1: new full speed USB device using uhci_hcd and address 3
Oct 29 16:34:11 tytlal kernel: usb 2-1: configuration #1 chosen from 2 choices
Oct 29 16:34:11 tytlal kernel: cdc_acm 2-1:1.0: ttyACM0: USB ACM device
Oct 29 16:34:23 tytlal kernel: hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
Oct 29 16:34:23 tytlal kernel: hostap_cs: Registered netdevice wifi0
Oct 29 16:34:23 tytlal kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x4100-0x413f
Oct 29 16:34:23 tytlal kernel: wifi0: NIC: id=0x800c v1.0.0
Oct 29 16:34:23 tytlal kernel: wifi0: PRI: id=0x15 v1.1.1
Oct 29 16:34:23 tytlal kernel: wifi0: STA: id=0x1f v1.8.4
Oct 29 16:34:26 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:34:26 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:34:42 tytlal pppd[6511]: tcsetattr: No such device or address (line 1010)
Oct 29 16:34:42 tytlal pppd[6511]: Exit.
Oct 29 16:35:57 tytlal kernel: wifi0: interrupt delivery does not seem to work
Oct 29 16:35:57 tytlal kernel: wifi0: cnfAuthentication setting to 0x1 failed
Oct 29 16:37:03 tytlal kernel: hostap_cs: Registered netdevice wifi0
Oct 29 16:37:03 tytlal kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x4100-0x413f
Oct 29 16:37:03 tytlal kernel: wifi0: NIC: id=0x800c v1.0.0
Oct 29 16:37:03 tytlal kernel: wifi0: PRI: id=0x15 v1.1.1
Oct 29 16:37:03 tytlal kernel: wifi0: STA: id=0x1f v1.8.4
Oct 29 16:37:05 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:37:05 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:37:10 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:37:16 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:37:16 tytlal kernel: hostap_cs: wifi0: resetting card
-- 
Chip Salzenberg <chip at pobox.com>



From wirelessdude12345  Tue Nov  1 19:44:04 2005
From: wirelessdude12345 (Wireless Dude)
Date: Tue, 01 Nov 2005 21:44:04 -0600
Subject: TX Packets in Monitor Mode
In-Reply-To: <BAY16-F10AD83A2FD1FBE54FB20A6EE6C0@phx.gbl>
Message-ID: <BAY16-F236E46AD3DCE8353014EEEEE6E0@phx.gbl>

Hi again,

I've managed to send packets in Monitor Mode.
As a first pass, I have just editted the driver source.
I have editted

hostap_data_start_xmit()

in hostap_80211_tx.c

and more specifically I have hard-coded the setting of,
hdr.addr1
hdr.addr2
hdr.addr3

Using this method I can set the address fields to what ever I want.
I have noticed that it is possible to change the source address (addr2).
The prism programmers manual seems to indicate that the firmware will 
automatically set addr2 but this doesn't seemd to be the case.

I am now trying to set the frame control field.
Setting fc =0x0080 (data packet type, subtype 0 , version 0), allows me to 
send a packet using the 802.11 header that is passed as part of

struct hfa384x_tx_frame txdesc;

in function
prism_tx_80211()
located in hostap_hw.c

When I try to set TODS in the frame control field the card seems to 
construct the packet using the 802.3 header info, even through the 
struct_type in the TxControl field that gets passed to the card as part of 
the hfa384x_tx_frame is set to 1 (ie 802.11 format).

Has anyone seen behaviour like this? The programmers manual doesn't mention 
much about Monitor Mode, am I trying to do the impossible here?
If anyone can point me to any extra documentation apart from the prism 
programmers manual that would be great.


James P.


>From: "Wireless Dude" <wirelessdude12345 at hotmail.com>
>To: hostap at shmoo.com
>Subject: TX Packets in Monitor Mode
>Date: Mon, 31 Oct 2005 01:15:40 -0600
>
>Hi all,
>
>I'm trying to send an arbitry packet while in monitor mode.
>(We are creating our own lightweight wireless protocol for a university 
>project).
>I adapted hostapd.c to send a packet with the payload I want.
>I put the card in monitor mode and try to send the packet.
>I have a sniffer accepting all packets, and it sees 4 packets, that look 
>like they have my created payload spread through them (data seems to be 
>there, just spread out across the 4 packets).
>My question is, can I send a packet in monitor mode?
>If not, how can I send a packet that I have constructed? ie no source addr, 
>destination addr, BSSID, type, etc..
>Is this possible using the hostap driver?
>I'm using a prism2 card and the latest hostap driver.
>
>thanks.
>James P.
>
>_________________________________________________________________
>Don?t just search. Find. Check out the new MSN Search! 
>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>


>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee? 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963




From proski  Tue Nov  1 20:36:50 2005
From: proski (Pavel Roskin)
Date: Tue, 01 Nov 2005 23:36:50 -0500
Subject: TX Packets in Monitor Mode
In-Reply-To: <BAY16-F236E46AD3DCE8353014EEEEE6E0@phx.gbl>
References: <BAY16-F236E46AD3DCE8353014EEEEE6E0@phx.gbl>
Message-ID: <1130906210.9704.17.camel@dv>

Hello!

On Tue, 2005-11-01 at 21:44 -0600, Wireless Dude wrote:

> Using this method I can set the address fields to what ever I want.
> I have noticed that it is possible to change the source address (addr2).
> The prism programmers manual seems to indicate that the firmware will 
> automatically set addr2 but this doesn't seemd to be the case.

Perhaps the monitor mode is an exception.

> When I try to set TODS in the frame control field the card seems to 
> construct the packet using the 802.3 header info, even through the 
> struct_type in the TxControl field that gets passed to the card as part of 
> the hfa384x_tx_frame is set to 1 (ie 802.11 format).
> 
> Has anyone seen behaviour like this?

Try filling the 802.3 header with zeroes.  Something like this was found
in Lucent cards.

-- 
Regards,
Pavel Roskin




From proski  Tue Nov  1 20:40:17 2005
From: proski (Pavel Roskin)
Date: Tue, 01 Nov 2005 23:40:17 -0500
Subject: Host AP driver and Linux 2.6.14
In-Reply-To: <43663782.8000606@infovia.com.ar>
References: <20051028035559.GB8991@jm.kir.nu> <43663782.8000606@infovia.com.ar>
Message-ID: <1130906417.9704.20.camel@dv>

On Mon, 2005-10-31 at 12:25 -0300, Beat Meier wrote:
> Jouni Malinen wrote:
> 
> I've downloaded vanilla kernel source 2.6.14 and wanted to build hostapd ...

Only the driver was included.  hostapd is still a separate download.

> Until now I have used only external release, so if I miss something, 
> sorry ....
> but  there is only support for Prism chipset.
> How do I add madwifi support for hostapd in this version??

Again, there is no hostapd in the kernel.

-- 
Regards,
Pavel Roskin




From divy  Tue Nov  1 21:05:42 2005
From: divy (divy at speakeasy.net)
Date: Wed, 02 Nov 2005 05:05:42 +0000
Subject: hostapd and tkip countermeasures
Message-ID: <W777010846212501130907942@webmail2>

Hi, 

> -----Original Message-----
> From: Jouni Malinen [mailto:jkmaline at cc.hut.fi]
> Sent: Thursday, October 13, 2005 02:33 AM
> To: hostap at shmoo.com
> Subject: Re: hostapd and tkip countermeasures
> 
> On Sat, Oct 08, 2005 at 09:32:51PM +0000, divy at speakeasy.net wrote:
> 
> > There does not seem to be an hostapd equivalent to the wpa_supplicant function wpa_drv_set_countermeasures(). 
> > Hostapd enforces tkip countermeasures only if it handles the management frames. 
> > If a driver only reports association events, hostapd proceeds to the authentication phase even if coutermeasures are still active.
> > 
> > Here is a proposed patch to hostapd.c that fixes the issue:
> 
> Thanks, applied. This does not fix the exact behavior since the client
> is allowed to complete association, but this is clearly improving the
> previous implementation. wpa_drv_set_countermeasures() like
> functionality and changes in the drivers would be needed to make the
> IEEE 802.11 authentication and association fail when countermeasures are
> in effect.

Please find a proposed patch in attachement which adds the hostapd_set_countermeasures() functionality and uses it for the madwifi driver.
The patch was created against hostapd-0.4.6.

Thanks,
Divy


-------------- next part --------------
A non-text attachment was scrubbed...
Name: countermeasures.diff
Type: application/octet-stream
Size: 2466 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051102/f5eca4a7/attachment.obj 


From gabcicala  Wed Nov  2 08:35:51 2005
From: gabcicala (gabriele cicala)
Date: Wed, 2 Nov 2005 17:35:51 +0100
Subject: Hostap and promiscuous mode
Message-ID: <4d7cfd320511020835v242cd812n7bb84f041ff0d3fd@mail.gmail.com>

Hi all.
I've searched in the mailing list and also on the net if it is possible to
use the hostap driver in promiscuous mode while I'm connected to a wireless
LAN. I mean while an active link is enabled between me and another host in a
WLAN I would sniff other traffic that is not sent to me (using Ethereal, of
course).

Do you have any experience with this problem?

Thank you in advance.
gabcicala
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051102/2209c388/attachment.htm 


From castet.matthieu  Wed Nov  2 10:46:53 2005
From: castet.matthieu (matthieu castet)
Date: Wed, 02 Nov 2005 19:46:53 +0100
Subject: [test] airo : first WPA-PSK support
Message-ID: <4369099D.3010502@free.fr>

Hi,

I have a working linux airo driver that support  WPA-PSK, but it is very 
ugly.
It only support one card, and don't support MPI350. Also it only works 
with WPA.

Currently the RX and TX key are set only for set_tx=1 key. The card 
should report valid mic key with EV_MIC, but the driver hangs for an 
unknow reason.

There still lot's of work to complete WPA support and merge it with an 
universal driver.

Attached a diff against 2.6.14 kernel.

If you test it, please send me your comment.


Matthieu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: airo_wpa.diff
Type: text/x-patch
Size: 19639 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051102/9015db65/attachment.bin 


From rafa  Wed Nov  2 15:08:27 2005
From: rafa (Rafa Marin Lopez)
Date: Wed, 02 Nov 2005 18:08:27 -0500
Subject: wpa2 fails
In-Reply-To: <20051016024250.GA9065@jm.kir.nu>
References: <43ba03f30510150244o3ccf37j@mail.gmail.com>
	<20051016024250.GA9065@jm.kir.nu>
Message-ID: <436946EB.7090805@dif.um.es>

Hi all

After executing WPA2  WPA-PSK mode.. i obtained this error after sending 
2/4 message

WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 01 0a 00 00 00 00 
00 00 00 00 00 04 00 c0 4c 12 3a 89 ab 21 16 19 7f 31 aa 70 18 76 89 dc 
2e 68 bb e1 ad bb d1 12 02 93 8d cf 43 c5 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de 5c 
87 b4 95 28 ce af d9 6d e3 3c 93 5f d5 f6 00 16 30 14 01 00 00 0f ac 04 
01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
WPA: 4-Way Handshake failed - pre-shared key may be incorrect

however keys are equal after several verifications.

can you help me ?

Thanks.

>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa at dif.um.es
------------------------------------------------------




From saint_lucy  Wed Nov  2 18:20:24 2005
From: saint_lucy (Lucia Di Occhi)
Date: Thu, 03 Nov 2005 02:20:24 +0000
Subject: wrt54g ssid broadcast disabled
In-Reply-To: <43654EAE.3060301@kadzban.is-a-geek.net>
Message-ID: <BAY102-F1F42D6D9866C770817925F2610@phx.gbl>

Thank you for your reply.  I did get it to work using only TKIP in the 
config and removing CCMP, but I am curious about the statement you made 
about EAS-CCMP.  My router, the WRT54G, supports Security Mode WPA2-Personal 
and two encryption algorithms:

TKIP+AES
AES

The router is configured for WPA2 and TKIP+AES but you are saying that 
AES-CCMP is more secure.  So my question is: what is the difference between 
the two encryption options offered by the linksys WPA2 security mode, which 
one is deemed more secure and why?

since my wpa_supplicant.conf now reads:
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
what am I really using, is it WPA instead of WPA2 even if the AP is set for 
WPA2?

Thanks.

>From: Bryan Kadzban <bryan at kadzban.is-a-geek.net>
>To: hostap at shmoo.com
>Subject: Re: wrt54g ssid broadcast disabled
>Date: Sun, 30 Oct 2005 17:52:30 -0500
>
>Lucia Di Occhi wrote:
> > Is there any configuration/workaround to connect to a wrt54g v3.1
> > latest firmware with disabled ssid broadcast?  I am using the
> > ndiswrapper driver.
>
>Sure; check the sample config file, specifically the section on ap_scan.
>The ndiswrapper driver does support the required mode.  ;-)
>
> > Spare me the talk about disabling SSID Broadcast when using WPA which
> > is secure, etc., etc.:-)
>
>Yes, WPA is "secure", so removing the SSID doesn't add much.  (Actually
>WPA and TKIP are only an interim measure; the long-term fix is to move
>to WPA2 and AES-CCMP.  TKIP wouldn't include countermeasures that get
>invoked when a MIC check fails, if it was a long-term fix.  AES-CCMP
>doesn't include these countermeasures, because it doesn't need them.)
>
>But you should know that removing the SSID IE from the beacons wouldn't
>give you anything anyway, even with 40-bit WEP.  The beacons still go
>out (they have to, otherwise the supplicant would not know whether the
>AP matched its security configuration, or whether a downgrade attack was
>happening), and the association-request/association-response frames
>include the SSID anyway.  So anyone listening while an association
>happened would still know the SSID.
>
>But, if you still want to turn the SSID off, look at the sample config
>file, in the ap_scan section, as above.


><< signature.asc >>




>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement




From bryan  Wed Nov  2 19:04:37 2005
From: bryan (Bryan Kadzban)
Date: Wed, 02 Nov 2005 22:04:37 -0500
Subject: wrt54g ssid broadcast disabled
In-Reply-To: <BAY102-F1F42D6D9866C770817925F2610@phx.gbl>
References: <BAY102-F1F42D6D9866C770817925F2610@phx.gbl>
Message-ID: <43697E45.2020103@kadzban.is-a-geek.net>

Lucia Di Occhi wrote:
> My router, the WRT54G, supports Security Mode WPA2-Personal and two
> encryption algorithms:
> 
> TKIP+AES
> AES
> 
> The router is configured for WPA2 and TKIP+AES but you are saying
> that AES-CCMP is more secure.  So my question is: what is the
> difference between the two encryption options offered by the linksys
> WPA2 security mode, which one is deemed more secure and why?

With TKIP+AES, I believe your AP is advertising two different possible
pairwise encryption algorithms (TKIP and AES-CCMP), and using TKIP for
the group key (because it has to stay compatible with all associated
clients).

With AES(-CCMP) only, the AP will advertise only AES-CCMP for pairwise
keys, and use AES-CCMP for the group key as well.

The difference is that AES-CCMP is not a band-aid on WEP, it's an
entirely different encryption algorithm.  TKIP is "just" a band-aid.

Don't get me wrong; TKIP has proven (so far) to be a pretty decent
band-aid, and it's probably good enough for almost anyone at this time.
(The underlying RC4 algorithm is still supported by a lot of HTTPS
sites, for instance.)  But stuff like this can change pretty quickly,
too, and IMO RC4 is starting to age (but note: I'm not a cryptanalyst!).

That's why I use AES on my wireless networks, at least.

> since my wpa_supplicant.conf now reads: 
>     proto=WPA
>     key_mgmt=WPA-PSK 
>     pairwise=TKIP
>     group=TKIP
> what am I really using, is it WPA instead of WPA2 even if the AP is set
> for WPA2?

WPA and WPA2 are compatibility standards from the Wi-Fi Alliance.  WPA
included TKIP encryption, using either pre-shared keys or full EAP
authentication (with a RADIUS server).  WPA2 includes either TKIP or
AES-CCMP encryption, using either pre-shared keys or full EAP
authentication (again, with a RADIUS server).  Users may enable or
disable any of the available encryption algorithms on their APs in any
mode.  I believe AES-CCMP is an extension for WPA also, because my
(fairly old) WRT54G offers AES-CCMP, but not WPA2.  Maybe there was no
standard for that combination, though.

There are also some minor differences between WPA and WPA2 regarding key
caching and fast roaming, but I don't believe those are required with
WPA2 (they are an option, but I think a WPA2 AP can interoperate with a
client that doesn't support the caching).

According to that network block, you are using WPA (no key-caching) on
the client side.  I believe you're still using WPA2 (support for
key-caching) on the AP side, but this specific client isn't taking
advantage of the caching capability.  If this client never roams, it
doesn't matter.

If you want to use AES, then you can try setting pairwise and group to
CCMP in wpa_supplicant's config, and use AES only in the AP's config.
(Because if you use TKIP+AES, then you'll have to use group=TKIP on the
client side.)  proto=WPA2 shouldn't hurt, but depending on the client
NIC and drivers, it might.  But as above, if you don't roam, I don't
believe it matters anyway.

key_mgmt should stay WPA-PSK unless you plan on setting up a RADIUS
server for client authentication.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051102/36938c91/attachment.pgp 


From jkmaline  Wed Nov  2 20:23:15 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 2 Nov 2005 20:23:15 -0800
Subject: wrt54g ssid broadcast disabled
In-Reply-To: <43697E45.2020103@kadzban.is-a-geek.net>
References: <BAY102-F1F42D6D9866C770817925F2610@phx.gbl>
	<43697E45.2020103@kadzban.is-a-geek.net>
Message-ID: <20051103042315.GJ8766@jm.kir.nu>

On Wed, Nov 02, 2005 at 10:04:37PM -0500, Bryan Kadzban wrote:

> WPA and WPA2 are compatibility standards from the Wi-Fi Alliance.

Depends on what you mean with compatible.. And as far as WPA2 is
concerned, Wi-Fi Alliance came up with the name whereas the standard is
actually coming from IEEE..

TKIP is identical in WPA and WPA2. CCMP is almost the same, but not
exactly; if fragmentation is used and someone actually implemented CCMP
as specified in WPA spec (i.e., in old IEEE 802.11i/D3.0), there would
be interoperability issues.

Key handshake uses different message contents and as such, I would not
call that compatible. However, both WPA and WPA2 can be enabled in the
AP at the same time.

> According to that network block, you are using WPA (no key-caching) on
> the client side.  I believe you're still using WPA2 (support for
> key-caching) on the AP side, but this specific client isn't taking
> advantage of the caching capability.  If this client never roams, it
> doesn't matter.

If the client is configured to use WPA (as was indeed the case here),
the AP must also have WPA enabled. In other words, both client and AP
used WPA in this case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Thu Nov  3 03:58:56 2005
From: bryan (Bryan Kadzban)
Date: Thu, 03 Nov 2005 06:58:56 -0500
Subject: wrt54g ssid broadcast disabled
In-Reply-To: <20051103042315.GJ8766@jm.kir.nu>
References: <BAY102-F1F42D6D9866C770817925F2610@phx.gbl>	<43697E45.2020103@kadzban.is-a-geek.net>
	<20051103042315.GJ8766@jm.kir.nu>
Message-ID: <4369FB80.3020505@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> TKIP is identical in WPA and WPA2. CCMP is almost the same, but not 
> exactly; if fragmentation is used and someone actually implemented CCMP
> as specified in WPA spec (i.e., in old IEEE 802.11i/D3.0), there would
> be interoperability issues.

Oh really...  Well, that's probably a good thing to file away in case I
ever need it, then.  Thanks!

> Key handshake uses different message contents

Well, just different OUIs in the IE(s) in the key-data field, right?  Or
are there other differences?  (I've read some of 802.11i, but not the
WPA spec.)

It is true that this would not be compatible though, you're right.

Thanks for the corrections, in any case!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051103/f9bb0a8f/attachment.pgp 


From bryan  Thu Nov  3 04:06:18 2005
From: bryan (Bryan Kadzban)
Date: Thu, 03 Nov 2005 07:06:18 -0500
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <20051031214009.GA2602@kadzban.is-a-geek.net>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>
	<20051031214009.GA2602@kadzban.is-a-geek.net>
Message-ID: <4369FD3A.2090803@kadzban.is-a-geek.net>

Bryan Kadzban wrote:
> So the problem is still there, but the problem isn't that
> set_ap_rsn_ie doesn't get called.  The problem is that the scan
> results table is out of date, and it returns the wrong IE.
> 
> I have tried doing a "wpa_cli scan" while the supplicant is in this 
> state (to update the scan results table), but that refuses to ever 
> reconnect to the current AP, for some reason.  I believe it's an
> issue with the NDIS driver in use (Linksys's driver for their WMP54GS
> cards), but I don't know that for sure.

I've since tried a couple things.  Using ap_scan=1 instead of 2 makes
scanning not kill the connection at least -- although after some
consideration, I think scanning every few minutes is probably not a
great way to fix this issue.

Since the changing value is always the RSN capabilities field, and
always the number of PTKSA/GTKSA replay counters, I changed the code to
zero out those replay counter bits in both IEs just before it does its
memcmp.  (I actually made a copy first, because I'm not sure what else
those pointers are used for.)  This does work -- the client does come
back after an AP restart changes that value.

Does this have any security implication?  I don't think so (especially
since I left the rest of the capabilities field as-is), but I don't know
for sure; maybe someone else here does?

It's also only a temporary workaround, I think, until we can fix our APs
to not change that IE.  But still, I'm not sure what the implications
are security wise.  (I don't really completely understand what those
replay counters do -- just watch for reused IVs?  then why would you
need more than one per PTKSA?)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051103/f004854a/attachment.pgp 


From miernik  Thu Nov  3 05:40:49 2005
From: miernik (Miernik)
Date: Thu, 3 Nov 2005 14:40:49 +0100
Subject: interrupt delivery does not seem to work
Message-ID: <20051103134049.62B.0.NOFFLE@localhost.localdomain.local>

I can't get my Senao miniPCI SL-2511MP PLUS 2.10 card to work.

The card has a sticker:
S/N: 044377522
NL-2511MP PLUS(ETSI)
MAC: 00026F33B9F3

Here I show what commands I run, and what appears after that in "dmesg"
output:

# insmod hostap
,----------------------------------------------------------------------------------------------------------------------------------
| hostap_crypt: registered algorithm 'NULL'
`----------------------------------------------------------------------------------------------------------------------------------
# insmod hostap_pci
,----------------------------------------------------------------------------------------------------------------------------------
| hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen <jkmaline at cc.hut.fi>)
| PCI: Enabling device 01:02.0 (0000 -> 0002)
| hostap_pci: Registered netdevice wifi0
| wifi0: Original COR value: 0x0
| prism2_hw_init: initialized in 200 ms
| wifi0: NIC: id=0x8013 v1.0.0
| wifi0: PRI: id=0x15 v1.1.1
| wifi0: STA: id=0x1f v1.8.4
| wifi0: Intersil Prism2.5 PCI: mem=0x40002000, irq=6
| wifi0: registered netdevice wlan0
`----------------------------------------------------------------------------------------------------------------------------------
# iwconfig wlan0 mode Managed
,----------------------------------------------------------------------------------------------------------------------------------
| prism2: wlan0: operating mode changed 3 -> 2
`----------------------------------------------------------------------------------------------------------------------------------
# ifconfig wlan0 up
# iwlist wlan0 scan
,----------------------------------------------------------------------------------------------------------------------------------
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89c60, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89c60, type=0, cmd=0x0021, param0=0xfdc6, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fdc6, len=12)
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89c60, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89c60, type=0, cmd=0x0021, param0=0xfdc1, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fdc1, len=2)
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89c60, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89c60, type=0, cmd=0x0021, param0=0xfdc6, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fdc6, len=12)
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89c60, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89c60, type=0, cmd=0x0021, param0=0xfc06, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fc06, len=2)
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89c60, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89c60, type=0, cmd=0x0021, param0=0xfd42, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fd42, len=6)
| wlan0: hfa384x_cmd: entry still in list? (entry=80e89ce0, type=0, res=0)
| wlan0: hfa384x_cmd: command was not completed (res=0, entry=80e89ce0, type=0, cmd=0x0021, param0=0xfc0e, EVSTAT=8010 INTEN=0000)
| wlan0: interrupt delivery does not seem to work
| wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-145, rid=fc0e, len=34)
`----------------------------------------------------------------------------------------------------------------------------------

The output of the last command usually is:
,---------------------------
| wlan0     No scan results
`---------------------------
but sometimes (so far 3 times, for probably a hundred attepts to get a
scan), I get a correct scan with 6 or mode APs in range, many of them
with very good signal, like -68 dBm at noise level -90 dBm. The card is
in fact in good radio rage, so that should be the correct output all the
time.

I also tried downgrading the card's STA firmware to v1.7.4, with the
same results.

-- 




From jphstap  Thu Nov  3 07:59:46 2005
From: jphstap (Joe Parks)
Date: Thu, 3 Nov 2005 10:59:46 -0500
Subject: Hostap and promiscuous mode
In-Reply-To: <4d7cfd320511020835v242cd812n7bb84f041ff0d3fd@mail.gmail.com>
References: <4d7cfd320511020835v242cd812n7bb84f041ff0d3fd@mail.gmail.com>
Message-ID: <20051103105946.393c1ec9@scrodconumulus>

On Wed, 2 Nov 2005 17:35:51 +0100
gabriele cicala <gabcicala at gmail.com> wrote:

> Hi all.
> I've searched in the mailing list and also on the net if it is possible to
> use the hostap driver in promiscuous mode while I'm connected to a wireless
> LAN. I mean while an active link is enabled between me and another host in a
> WLAN I would sniff other traffic that is not sent to me (using Ethereal, of
> course).

Promiscuous mode doesn't produce quite the same results with wireless cards as it does with Ethernet cards.   You *can* put hostap driver into promiscuous mode, but it still won't show you any traffic not sent with your card as the intended receiver (so not much use for the purpose you mention)

But there is a way to sniff other traffic.   You can put the card into MONITOR mode.   This allows you to sniff other wireless traffic.  However it prevents you from using the card in a *normal* way.   You can no longer transmit (well at least not reliably) or associate to or act as an Access Point.



From rafa  Thu Nov  3 09:09:34 2005
From: rafa (Rafa Marin Lopez)
Date: Thu, 03 Nov 2005 12:09:34 -0500
Subject: wpa2 fails
In-Reply-To: <436946EB.7090805@dif.um.es>
References: <43ba03f30510150244o3ccf37j@mail.gmail.com>
	<20051016024250.GA9065@jm.kir.nu> <436946EB.7090805@dif.um.es>
Message-ID: <436A444E.2080205@dif.um.es>

Hi again...

I am using madwifi and hostapd 0.4.6

Now I have seen  supplicant receives message 1/4 in the 4-way handshake 
sends the 2/4  , it arrives to AP (i checked this with ethereal) but 
hostapd sends again 1/4 becuase timeout ocurred. It looks as if HostaAPd 
does not proccess 2/4 sent by supplicant...

some idea?

Thanks.

Rafa Marin Lopez wrote:

> Hi all
>
> After executing WPA2  WPA-PSK mode.. i obtained this error after 
> sending 2/4 message
>
> WPA: Sending EAPOL-Key 2/4
> WPA: TX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 01 0a 00 00 00 00 
> 00 00 00 00 00 04 00 c0 4c 12 3a 89 ab 21 16 19 7f 31 aa 70 18 76 89 
> dc 2e 68 bb e1 ad bb d1 12 02 93 8d cf 43 c5 00 00 00 00 00 00 00 00 
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 00 de 5c 87 b4 95 28 ce af d9 6d e3 3c 93 5f d5 f6 00 16 30 14 01 00 
> 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>
> however keys are equal after several verifications.
>
> can you help me ?
>
> Thanks.
>
>>  
>>
>
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa at dif.um.es
------------------------------------------------------




From shawn_adams  Thu Nov  3 10:59:28 2005
From: shawn_adams (Shawn Adams)
Date: Thu, 03 Nov 2005 19:59:28 +0100
Subject: Michael MIC failure detected
Message-ID: <436A5E10.80201@web.de>


I'm wondering about the error message:

Michael MIC failure detected

does this correspond to the AP syslog message:

Information: WPA group key update fails at 00-20-d8-03-86-94

???

Thanks



State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:20:d8:03:8a:bc (ver=1)
WPA: IE KeyData - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 01 00 00
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
Wireless event: cmd=0x8c02 len=85
Custom wireless event: 'MLME-MICHAELMICFAILURE.indication(keyid=0
unicast addr=00:20:d8:03:86:94)'
Michael MIC failure detected
WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99)
Wireless event: cmd=0x8c02 len=85
Custom wireless event: 'MLME-MICHAELMICFAILURE.indication(keyid=0
unicast addr=00:20:d8:03:86:94)'
Michael MIC failure detected
WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99)
TKIP countermeasures started
wpa_driver_madwifi_set_countermeasures: enabled=1

-- 
Shawn Adams
shawn_adams at web.de




From chip  Thu Nov  3 11:15:08 2005
From: chip (Chip Salzenberg)
Date: Thu, 3 Nov 2005 11:15:08 -0800
Subject: interrupt delivery does not seem to work
In-Reply-To: <20051103134049.62B.0.NOFFLE@localhost.localdomain.local>
References: <20051103134049.62B.0.NOFFLE@localhost.localdomain.local>
Message-ID: <20051103191508.GD6816@tytlal.topaz.cx>

On Thu, Nov 03, 2005 at 02:40:49PM +0100, Miernik wrote:
> | wlan0: interrupt delivery does not seem to work

I'm getting that too.  I have yet to get any reply from this list, or
from linux-kernel.  I wonder how a driver can get developed and put in
the kernel tree while no attention is paid to bug reports...
-- 
Chip Salzenberg <chip at pobox.com>



From rjy  Thu Nov  3 16:24:26 2005
From: rjy (Russell J. Yount)
Date: Thu, 03 Nov 2005 19:24:26 -0500
Subject: Linux-2.6.14 hostapd driver problem?
Message-ID: <103373913.1131045866@[192.168.1.207]>

I have been using a 2511 CD PLUS EXT2 card with linux 2.6.11.12 and
the 0.3.9 versions of the hostap driver/hostapd reliably for
some time now. The card firmware is 1.7.4 and I am using WPA-PSK.
The machine is soekris net4521.

I built linux 2.6.14 and tried using both hostapd 0.3.9 and 0.4.6
with no success. The following log is contains both hostapd 0.4.6
log messages and linux 2.6.14. It seems I get rather intermittent
connectivity with 2.6.14, the group key handshake keeps failing
and the card is resetting. This is happening on two different
identical systems I tried upgrading.

Is this a problem with the driver in the 2.6.14 kernel?


Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:02:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:07 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:07 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:08 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:08 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:08 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:08 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-00000006)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:02:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:14 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:14 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:15 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:15 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:16 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:16 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:16 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:16 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-00000007)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:02:20 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:21 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:21 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:22 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:22 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:23 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:02:23 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:02:23 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:02:23 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-00000008)
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:03:01 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:02 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:02 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:03 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key 4/4 Pairwise with unexpected replay counter
Nov  1 20:03:03 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:03 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:04 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:04 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:05 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:08 server0 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Nov  1 20:03:08 server0 kernel: wifi0 Tx timed out! Resetting card
Nov  1 20:03:08 server0 kernel: wifi0: CMD=010b EVSTAT=0000 OFFSET0=0000 
OFFSET1=0000 SWSUPPORT0=8a32
Nov  1 20:03:08 server0 kernel: wifi0: scheduled card reset
Nov  1 20:03:08 server0 kernel: hostap_cs: wifi0: resetting card
Nov  1 20:03:08 server0 kernel: prism2_pccard_cor_sreset: original COR 41
Nov  1 20:03:09 server0 kernel: wifi0: removed pending cmd_queue entry 
(type=1, cmd=0x010b, param0=0x015e)
Nov  1 20:03:09 server0 kernel: prism2_hw_init: initialized in 192 ms
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-00000009)
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:03:09 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:03:10 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:10 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:11 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:11 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:12 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:12 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:13 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-0000000A)
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:03:26 server0 kernel: wlan0: dropped frame from unauthorized port 
(IEEE 802.1X): ethertype=0x0800
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:03:26 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:27 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:27 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:28 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:28 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:29 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:29 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:29 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:29 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-0000000B)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:03:33 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:34 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:34 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:35 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:35 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:36 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:36 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:36 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:36 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-0000000C)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: start 
authentication
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/4 msg of 4-Way Handshake
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (2/4 Pairwise)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
3/4 msg of 4-Way Handshake
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: received 
EAPOL-Key frame (4/4 Pairwise)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
authorizing port
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: pairwise 
key handshake completed (WPA)
Nov  1 20:03:41 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:42 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:42 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:43 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:43 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:44 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: 
EAPOL-Key timeout
Nov  1 20:03:44 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: sending 
1/2 msg of Group Key Handshake
Nov  1 20:03:44 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.1X: 
unauthorizing port
Nov  1 20:03:44 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
deauthenticated due to local deauth request
Nov  1 20:03:48 server0 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Nov  1 20:03:48 server0 kernel: wifi0 Tx timed out! Resetting card
Nov  1 20:03:48 server0 kernel: wifi0: CMD=010b EVSTAT=0000 OFFSET0=0000 
OFFSET1=0000 SWSUPPORT0=8a32
Nov  1 20:03:48 server0 kernel: wifi0: scheduled card reset
Nov  1 20:03:48 server0 kernel: hostap_cs: wifi0: resetting card
Nov  1 20:03:48 server0 kernel: prism2_pccard_cor_sreset: original COR 41
Nov  1 20:03:48 server0 kernel: wifi0: removed pending cmd_queue entry 
(type=1, cmd=0x010b, param0=0x0188)
Nov  1 20:03:48 server0 kernel: prism2_hw_init: initialized in 192 ms
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authentication OK (open system)
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 0 
notification
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
authenticated
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
association OK (aid 1)
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 IEEE 802.11: 
associated (aid 1, accounting session 43680FB1-0000000D)
Nov  1 20:04:06 server0 hostapd: wlan0: STA 00:90:4b:14:39:26 WPA: event 1 
notification

end of log....





From t.schorpp  Thu Nov  3 18:07:17 2005
From: t.schorpp (thomas schorpp)
Date: Fri, 04 Nov 2005 03:07:17 +0100
Subject: no more gtk rekeying after local deauth request
	(hostapd-wpa_supplicant)
In-Reply-To: <20050903155058.GY7781@jm.kir.nu>
References: <4312B91A.3090302@gmx.de>
	<4312EB30.8000601@kadzban.is-a-geek.net>	<4312FCEE.7080909@gmx.de>	<20050829170157.GB3449@kadzban.is-a-geek.net>	<4315D454.7070601@gmx.de>
	<43162709.7040800@gmx.de> <20050903155058.GY7781@jm.kir.nu>
Message-ID: <436AC255.3050904@gmx.de>

Jouni Malinen wrote:
> On Wed, Aug 31, 2005 at 11:54:17PM +0200, thomas schorpp wrote:
> 
> 
>>strange: if a linux wpasuppl. rsn client joins the net no more group key
>>handshakes with this xp client with latest hostapd...?
>>-> maybe security issue / policy violation
> 

hi,

got a brand new d-link dwl-g650 c2 and

see it again, this time in latest(? ive seen no checkins for a week so
far) hostapd+wpasupplicant cvs on 2.6.14 with madwifi cvs (which still
has the acpi suspend/resume issue in ath-*.ko and wlan-ccmp.ko,
requiring module removal in acpi script before sleep and ifupdown
explicitly) :

Nov  4 00:34:19 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
handshake completed (RSN)
Nov  4 00:34:55 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
authenticated
Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
deauthenticated due to local deauth request

? its not gmk-rekey, occours 1 per h.

Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
deassociated
Nov  4 00:34:59 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
associated
Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
key handshake completed (RSN)
Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
authenticated

-no more gtk rekeying until wpasupplicant restart.

Nov  4 01:13:46 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
deassociated
Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
associated
Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
key handshake completed (RSN)
Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
authenticated
Nov  4 01:18:47 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
handshake completed (RSN)
...

> 
> Can you provide a debug log from hostapd showing this kind of behavior
> (with some additional comments on where you would have expected to see
> group key handshake)?
> 

ok. i do it next, this is a security issue. windows+mac rsn clients not
 involved and rekeying normal with hostapd.

tom schorpp



From stefanmartinek  Fri Nov  4 01:30:56 2005
From: stefanmartinek (Stefan Martinek)
Date: Fri, 4 Nov 2005 01:30:56 -0800
Subject: Hey Hostap ;)
Message-ID: <493316675.1131096655785.JavaMail.root@tonybennet>

Stefan Martinek has invited you to join hi5. By joining hi5, you will be connected to Stefan and all of Stefan's friends.
 
hi5 is the place where friends meet. You can use hi5 for the following purposes:
* Find old friends
* Meet new people
* Browse photos

Join Stefan, meet Stefan's friends, and meet people that share your interests now!

Click here:
http://www.hi5.com/register/8LKAD?inviteId=NLJLR5HZD845546612h0







This invitation was sent to hostap at shmoo.com on behalf of Stefan Martinek (stefanmartinek at hotmail.com).

If you do not wish to receive invitations from hi5 members, click on the link below:
http://www.hi5.com/friend/displayBlockInvite.do?inviteId=NLJLR5HZD845546612h0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051104/13f353f5/attachment.htm 


From rafa  Fri Nov  4 06:27:27 2005
From: rafa (Rafa Marin Lopez)
Date: Fri, 04 Nov 2005 09:27:27 -0500
Subject: Bridging with madwifi
In-Reply-To: <20051016024250.GA9065@jm.kir.nu>
References: <43ba03f30510150244o3ccf37j@mail.gmail.com>
	<20051016024250.GA9065@jm.kir.nu>
Message-ID: <436B6FCF.6070906@dif.um.es>

Hi Jouni

I have tried hostapd 0.4.6 with madwifi-old and kernel 2.6.10 and the 
same problem happen. That is, if bridge is enabled AP does not listen 
frame 2/4 in 4-way handshake . However without bridging thing work 
perfectly.

Any idea about that?.

Regards.

Jouni Malinen wrote:

>On Sat, Oct 15, 2005 at 11:44:53AM +0200, Thomas Heiz wrote:
>
>  
>
>>I want to set up hostapd with bridge between a madwifi card and wired
>>ethernet. I've inserted a line "bridge=br0" in my hostapd.conf.
>>    
>>
>
>  
>
>>When I start hostapd, everything seems to be OK, but when a station
>>wants to connect, the following error occures.
>>
>>frame too short for this IEEE 802.1X packet
>>    
>>
>
>l2_packet cleanup in 0.4.4 missed one case, i.e., receiving EAPOL frames
>from madwifi driver when it is a part of a bridge. A fix for this is now
>available in the development branch of my CVS repository.
>
>  
>

-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa at dif.um.es
------------------------------------------------------




From t.schorpp  Fri Nov  4 07:08:09 2005
From: t.schorpp (thomas schorpp)
Date: Fri, 04 Nov 2005 16:08:09 +0100
Subject: no more gtk rekeying after local deauth
	request	(hostapd-wpa_supplicant)
In-Reply-To: <436AC255.3050904@gmx.de>
References: <4312B91A.3090302@gmx.de>	<4312EB30.8000601@kadzban.is-a-geek.net>	<4312FCEE.7080909@gmx.de>	<20050829170157.GB3449@kadzban.is-a-geek.net>	<4315D454.7070601@gmx.de>	<43162709.7040800@gmx.de>
	<20050903155058.GY7781@jm.kir.nu> <436AC255.3050904@gmx.de>
Message-ID: <436B7959.2070808@gmx.de>

thomas schorpp wrote:
> Jouni Malinen wrote:
> 
>>On Wed, Aug 31, 2005 at 11:54:17PM +0200, thomas schorpp wrote:
>>
>>
>>
>>>strange: if a linux wpasuppl. rsn client joins the net no more group key
>>>handshakes with this xp client with latest hostapd...?
>>>-> maybe security issue / policy violation
>>
> 
> hi,
> 
> got a brand new d-link dwl-g650 c2 and
> 
> see it again, this time in latest(? ive seen no checkins for a week so
> far) hostapd+wpasupplicant cvs on 2.6.14 with madwifi cvs (which still
> has the acpi suspend/resume issue in ath-*.ko and wlan-ccmp.ko,
> requiring module removal in acpi script before sleep and ifupdown
> explicitly) :
> 
> Nov  4 00:34:19 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
> handshake completed (RSN)
> Nov  4 00:34:55 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
> authenticated
> Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
> deauthenticated due to local deauth request
> 
> ? its not gmk-rekey, occours 1 per h.
> 
> Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
> deassociated
> Nov  4 00:34:59 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
> associated
> Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
> key handshake completed (RSN)
> Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
> authenticated
> 
> -no more gtk rekeying until wpasupplicant restart.
> 
> Nov  4 01:13:46 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
> deassociated
> Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
> associated
> Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
> key handshake completed (RSN)
> Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
> authenticated
> Nov  4 01:18:47 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
> handshake completed (RSN)
> ...
> 
> 
>>Can you provide a debug log from hostapd showing this kind of behavior
>>(with some additional comments on where you would have expected to see
>>group key handshake)?
>>
> 
> 
> ok. i do it next, this is a security issue. windows+mac rsn clients not
>  involved and rekeying normal with hostapd.
> 

hm. with both started in debug mode, this issue does NOT occur.

debug log says local deauth request with wireless-event 5.

maybe a debug "if{}else" is buggy in the code or the last old code cvs madwifi driver. 

a pity i cant test with the new madwifi-ng code, 
it crashes with reproducible kernel-panic on wpasupplicant startup scanning for the ap in irq handler 
on debian 2.6.14-1-686 (2) kernel image at ath_send_start or ath_send_end. hardware independent.

...

testing madwifi-ng right now, after cold boot the kernel panic does not occur 
but wpasupplicant fails on scan init with somemissing ioctl.

trying compile it against madwifi-ng fails in function set80211priv, if.h redefinitions, 
ieee80211_ioctl_chanlist undeclared, latest debian linux-kernel-headers package too old, 2.6.13-rc..  




From romanol  Fri Nov  4 07:57:14 2005
From: romanol (Romano Giannetti)
Date: Fri, 4 Nov 2005 16:57:14 +0100
Subject: hostapd/wpa_supplicant - new development release v0.4.6
In-Reply-To: <20051028034827.GA8991@jm.kir.nu>
References: <20051028034827.GA8991@jm.kir.nu>
Message-ID: <20051104155714.GA12853@pern.dea.icai.upcomillas.es>

On Thu, Oct 27, 2005 at 08:48:27PM -0700, Jouni Malinen wrote:
> 
> This release is from the new development branch (0.4.x). Please note
> that the 0.3.x branch continues to be the current source of stable
> releases.
> 

Hi. I tested wpa_supplicant (802.1x authentication with PEAP/MSCHAPv2) and I
can confirm _no_ regressions from 0.3.x series. 

wpa_gui is really nice. the only slightly disturbing thing is that the
password is shown in clear text (I knoe, I have it in clear text in mi
wpa.conf file, but still... it's quite surprising). 

Nice and good work, thank you! 

     Romano

-- 
Romano Giannetti             -  Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2416  fax +34 915 596 569



From swong  Fri Nov  4 10:00:13 2005
From: swong (Simon Wong)
Date: Fri, 04 Nov 2005 10:00:13 -0800
Subject: madwifi + hostapd fail
Message-ID: <436BA1AD.70007@changind.com>

Hi,

I'm trying to get WPA-PSK with TKIP to work on my system. I'm using the 
latest stable version of hostapd, and a relatively recent version of 
madwifi. I'm trying to use a winxp machine to attach to this system. I'm 
not getting data through. Any ideas on what might be wrong?

Here is the conf file:
interface=ath1
ssid=RTK_AP36
wpa=1
driver=madwifi
wpa_passphrase=********
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
wpa_group_rekey=600
wpa_gmk_rekey=86400
debug=1

Here is part of the dump:
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state AUTHENTICATION
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state INITPSK
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state DISCONNECT
madwifi_sta_deauth: addr=00:0d:88:9c:e3:f6 reason_code=2
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state DISCONNECTED
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0d:88:9c:e3:f6 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: No such file or directory
ath1: STA 00:0d:88:9c:e3:f6 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0d:88:9c:e3:f6 authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
ath1: STA 00:0d:88:9c:e3:f6 IEEE 802.11: deauthenticated due to local 
deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0d:88:9c:e3:f6
rx_packets=6
tx_packets=4
rx_bytes=586
tx_bytes=428

-- 
Simon Wong
System Engineer
CHANG Industry, Inc.
1925 McKinley Ave., Suite F
La Verne, CA 91725
www.changind.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swong.vcf
Type: text/x-vcard
Size: 219 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051104/e67f6058/attachment.vcf 


From chip  Fri Nov  4 12:01:35 2005
From: chip (Chip Salzenberg)
Date: Fri, 4 Nov 2005 12:01:35 -0800
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
Message-ID: <20051104200135.GA8649@tytlal.topaz.cx>

ARE THERE ANY MAINTAINERS HERE?  AT ALL?

I'm having serious but probably easily fixed (for the maintainers)
problems with hostap.  I can't upgrade from 2.6.12 to the 2.6.14
without breaking the hostap driver.  I'm not using exotic hardware,
it's just an old DWL-650 and a ThinkPad A30.

I'm not asking for much, just a little clue on how to solve this.  If
you didn't want your driver used, why would you ignore bug reports,
and why would you seek inclusion in the mainstream Linux kernel?  If
you're not going to maintain this driver, why is this list address in
the kernel MAINTAINERS file?
-- 
Chip Salzenberg <chip at pobox.com>



From proski  Fri Nov  4 13:57:41 2005
From: proski (Pavel Roskin)
Date: Fri, 04 Nov 2005 16:57:41 -0500
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <20051104200135.GA8649@tytlal.topaz.cx>
References: <20051104200135.GA8649@tytlal.topaz.cx>
Message-ID: <1131141461.2317.7.camel@dv>

Hello!

On Fri, 2005-11-04 at 12:01 -0800, Chip Salzenberg wrote:
> ARE THERE ANY MAINTAINERS HERE?  AT ALL?
> 
> I'm having serious but probably easily fixed (for the maintainers)
> problems with hostap.  I can't upgrade from 2.6.12 to the 2.6.14
> without breaking the hostap driver.  I'm not using exotic hardware,
> it's just an old DWL-650 and a ThinkPad A30.

If you use so many capital letters in the subject, it would be
reasonable to provide links your previous messages, so that the
attention you have received is diverted from your feelings to your
problem.  Also, it's often helpful to rephrase your question, add more
details and show that you did some research.

> I'm not asking for much, just a little clue on how to solve this.  If
> you didn't want your driver used, why would you ignore bug reports,
> and why would you seek inclusion in the mainstream Linux kernel?  If
> you're not going to maintain this driver, why is this list address in
> the kernel MAINTAINERS file?

Maintainers cannot always reply to every bug report.  They are
responsible for development, not for support.  You may get better
answers from people not listed in the MAINTAINERS file.

I may be able to look at the hostap_pci issue, just not right now.

-- 
Regards,
Pavel Roskin




From gentoopower  Fri Nov  4 14:11:37 2005
From: gentoopower (Stefan)
Date: Fri, 04 Nov 2005 23:11:37 +0100
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <1131141461.2317.7.camel@dv>
References: <20051104200135.GA8649@tytlal.topaz.cx>
	<1131141461.2317.7.camel@dv>
Message-ID: <436BDC99.3040005@yahoo.de>

Pavel Roskin wrote:

>Hello!
>
>On Fri, 2005-11-04 at 12:01 -0800, Chip Salzenberg wrote:
>  
>
>>ARE THERE ANY MAINTAINERS HERE?  AT ALL?
>>
>>I'm having serious but probably easily fixed (for the maintainers)
>>problems with hostap.  I can't upgrade from 2.6.12 to the 2.6.14
>>without breaking the hostap driver.  I'm not using exotic hardware,
>>it's just an old DWL-650 and a ThinkPad A30.
>>    
>>
>
>If you use so many capital letters in the subject, it would be
>reasonable to provide links your previous messages, so that the
>attention you have received is diverted from your feelings to your
>problem.  Also, it's often helpful to rephrase your question, add more
>details and show that you did some research.
>  
>
Yeah, it would be really helpful if you provided more info, instead of
saying that 2.6.14 breaks hostap driver.

What means breaking, doens't compile, no traffic from the card, no auth etc.

>  
>
>>I'm not asking for much, just a little clue on how to solve this.  If
>>you didn't want your driver used, why would you ignore bug reports,
>>and why would you seek inclusion in the mainstream Linux kernel?  If
>>you're not going to maintain this driver, why is this list address in
>>the kernel MAINTAINERS file?
>>    
>>
>
>Maintainers cannot always reply to every bug report.  They are
>responsible for development, not for support.  You may get better
>answers from people not listed in the MAINTAINERS file.
>
>I may be able to look at the hostap_pci issue, just not right now.
>
>  
>


	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de



From chip  Fri Nov  4 15:23:41 2005
From: chip (Chip Salzenberg)
Date: Fri, 4 Nov 2005 15:23:41 -0800
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <436BDC99.3040005@yahoo.de>
References: <20051104200135.GA8649@tytlal.topaz.cx>
	<1131141461.2317.7.camel@dv> <436BDC99.3040005@yahoo.de>
Message-ID: <20051104232340.GD8649@tytlal.topaz.cx>

On Fri, Nov 04, 2005 at 11:11:37PM +0100, Stefan wrote:
> Yeah, it would be really helpful if you provided more info, instead of
> saying that 2.6.14 breaks hostap driver.

This is the third message I've posted with the same log info.
Below I've quoted the previous one.

PS: If there was ever any doubt that my previous messages fell into a
    black hole, you've proved it.

--------------------------------------------------------------------------
Date: Tue, 1 Nov 2005 18:58:44 -0800
From: Chip Salzenberg <chip at pobox.com>
To: hostap at shmoo.com
Subject: "wifi0: interrupt delivery does not seem to work"
Message-ID: <20051102025844.GA6610 at tytlal.topaz.cx>
References: <20051031013349.GA24013 at tytlal.topaz.cx> <20051031235200.GH6993 at tytlal.topaz.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051031235200.GH6993 at tytlal.topaz.cx>
User-Agent: Mutt/1.5.11
Status: RO
Content-Length: 2448
Lines: 39

Version 0.3.9 under kernel 2.6.12 works fine.

Version 0.4.4-kernel included with kernel 2.6.14 does not work, nor
does version 0.4.1 compiled separately; there seems to be a problem
with interrupt delivery.  As long as the module is installed,
keystrokes and all other interrupt-driven activity pause for a LONG
time.  In fact, often keystrokes will auto-repeat as the interrupt for
the key-raise event gets delayed.

C'mon guys, anybody have a clue here?  Anybody?  I'd like to use the
2.6.14 kernel, but hostap is holding back the upgrade.

Oct 29 16:34:11 tytlal kernel: usb 2-1: new full speed USB device using uhci_hcd and address 3
Oct 29 16:34:11 tytlal kernel: usb 2-1: configuration #1 chosen from 2 choices
Oct 29 16:34:11 tytlal kernel: cdc_acm 2-1:1.0: ttyACM0: USB ACM device
Oct 29 16:34:23 tytlal kernel: hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
Oct 29 16:34:23 tytlal kernel: hostap_cs: Registered netdevice wifi0
Oct 29 16:34:23 tytlal kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x4100-0x413f
Oct 29 16:34:23 tytlal kernel: wifi0: NIC: id=0x800c v1.0.0
Oct 29 16:34:23 tytlal kernel: wifi0: PRI: id=0x15 v1.1.1
Oct 29 16:34:23 tytlal kernel: wifi0: STA: id=0x1f v1.8.4
Oct 29 16:34:26 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:34:26 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:34:42 tytlal pppd[6511]: tcsetattr: No such device or address (line 1010)
Oct 29 16:34:42 tytlal pppd[6511]: Exit.
Oct 29 16:35:57 tytlal kernel: wifi0: interrupt delivery does not seem to work
Oct 29 16:35:57 tytlal kernel: wifi0: cnfAuthentication setting to 0x1 failed
Oct 29 16:37:03 tytlal kernel: hostap_cs: Registered netdevice wifi0
Oct 29 16:37:03 tytlal kernel: hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x4100-0x413f
Oct 29 16:37:03 tytlal kernel: wifi0: NIC: id=0x800c v1.0.0
Oct 29 16:37:03 tytlal kernel: wifi0: PRI: id=0x15 v1.1.1
Oct 29 16:37:03 tytlal kernel: wifi0: STA: id=0x1f v1.8.4
Oct 29 16:37:05 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:37:05 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:37:10 tytlal kernel: hostap_cs: wifi0: resetting card
Oct 29 16:37:16 tytlal kernel: wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
Oct 29 16:37:16 tytlal kernel: hostap_cs: wifi0: resetting card
-- 
Chip Salzenberg <chip at pobox.com>
--------------------------------------------------------------------------

-- 
Chip Salzenberg <chip at pobox.com>



From rafa  Fri Nov  4 15:46:00 2005
From: rafa (Rafa Marin Lopez)
Date: Fri, 04 Nov 2005 18:46:00 -0500
Subject: Implementation question: 802.1X port
Message-ID: <436BF2B8.5040506@dif.um.es>

Hi all


I am trying to see where implementation of uncontrolled/controlled port 
is implemented. Going deep in the source code i just noticed it could be 
placed on madwifi driver (i am using this driver for my atheros wireless 
card) and not in the hostapd source code. is my guess  correct?

Please let me know...

Thanks.

-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa at dif.um.es
------------------------------------------------------




From jkmaline  Fri Nov  4 17:53:58 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 4 Nov 2005 17:53:58 -0800
Subject: Implementation question: 802.1X port
In-Reply-To: <436BF2B8.5040506@dif.um.es>
References: <436BF2B8.5040506@dif.um.es>
Message-ID: <20051105015358.GA9392@jm.kir.nu>

On Fri, Nov 04, 2005 at 06:46:00PM -0500, Rafa Marin Lopez wrote:

> I am trying to see where implementation of uncontrolled/controlled port 
> is implemented. Going deep in the source code i just noticed it could be 
> placed on madwifi driver (i am using this driver for my atheros wireless 
> card) and not in the hostapd source code. is my guess  correct?

If you mean the packet filtering part, then yes, that is indeed in
kernel space. Normal data packets are not sent to user space (hostapd)
for processing.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Nov  4 18:17:57 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 4 Nov 2005 18:17:57 -0800
Subject: hostap 0.4.4-kernel interrupt troubles: "SWSUPPORT0 does not
	match"
In-Reply-To: <20051031013349.GA24013@tytlal.topaz.cx>
References: <20051031013349.GA24013@tytlal.topaz.cx>
Message-ID: <20051105021757.GA8898@jm.kir.nu>

On Sun, Oct 30, 2005 at 05:33:49PM -0800, Chip Salzenberg wrote:

> I've got a pcmcmia laptop setup using the hostap drivers.
> (For which, btw, thanks!)
> 
> Version 0.3.9 under kernel 2.6.12 works fine.

Can you test whether the current development version (0.4.6) works with
2.6.12? What about 2.6.13?

> Version 0.4.4-kernel included with kernel 2.6.14 does not; there seems
> to be a problem with interrupt delivery.  As long as the module is
> installed, keystrokes and all other interrupt-driven activity pause
> for a LONG time.  In fact, often keystrokes will auto-repeat as the
> interrupt for the key-raise event gets delayed.

I cannot reproduce this in my test setup. Linux 2.6.14 with the Host AP
driver works on my IBM ThinkPad T43 with hostap_cs and the same station
firmware version that you seem to be using (1.8.4). Did you need to do
something with the card before seeing this issue apart from plugging it
in? I was able to associate with WPA without seeing any problems.

Are you using the new hotplug mechanism to initialize PC Card modules?
Can you please send full dmesg output including everything from the
kernel startup to the point when hostap_cs starts reporting problems?

-- 
Jouni Malinen                                            PGP id EFC895FA



From rafa  Fri Nov  4 20:53:37 2005
From: rafa (Rafa Marin Lopez)
Date: Fri, 04 Nov 2005 23:53:37 -0500
Subject: Implementation question: 802.1X port
In-Reply-To: <20051105015358.GA9392@jm.kir.nu>
References: <436BF2B8.5040506@dif.um.es> <20051105015358.GA9392@jm.kir.nu>
Message-ID: <436C3AD1.9010302@dif.um.es>

Hi Jouni...

Jouni Malinen wrote:

>On Fri, Nov 04, 2005 at 06:46:00PM -0500, Rafa Marin Lopez wrote:
>
>  
>
>>I am trying to see where implementation of uncontrolled/controlled port 
>>is implemented. Going deep in the source code i just noticed it could be 
>>placed on madwifi driver (i am using this driver for my atheros wireless 
>>card) and not in the hostapd source code. is my guess  correct?
>>    
>>
>
>If you mean the packet filtering part, 
>
Yes i meant that...

>then yes, that is indeed in
>kernel space. 
>
I would be interested in checking all frames sent through uncontrolled 
port even if they are data frames (they would be filtered by 
uncontrolled port) . But following your comments, it would mean to touch 
the madwifi driver right?

>Normal data packets are not sent to user space (hostapd)
>for processing.
>  
>
You mean here when STA is authenticated right?.

Regards.

-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa at dif.um.es
------------------------------------------------------




From t.schorpp  Fri Nov  4 22:48:41 2005
From: t.schorpp (thomas schorpp)
Date: Sat, 05 Nov 2005 07:48:41 +0100
Subject: no more gtk rekeying after reauth (hostapd-wpa_supplicant)
In-Reply-To: <436B7959.2070808@gmx.de>
References: <4312B91A.3090302@gmx.de>	<4312EB30.8000601@kadzban.is-a-geek.net>	<4312FCEE.7080909@gmx.de>	<20050829170157.GB3449@kadzban.is-a-geek.net>	<4315D454.7070601@gmx.de>	<43162709.7040800@gmx.de>	<20050903155058.GY7781@jm.kir.nu>
	<436AC255.3050904@gmx.de> <436B7959.2070808@gmx.de>
Message-ID: <436C55C9.6090807@gmx.de>

thomas schorpp wrote:
> thomas schorpp wrote:
> 
>>Jouni Malinen wrote:
>>
>>
>>>On Wed, Aug 31, 2005 at 11:54:17PM +0200, thomas schorpp wrote:
>>>
>>>
>>>
>>>
>>>>strange: if a linux wpasuppl. rsn client joins the net no more group key
>>>>handshakes with this xp client with latest hostapd...?
>>>>-> maybe security issue / policy violation
>>>
>>hi,
>>
>>got a brand new d-link dwl-g650 c2 and
>>
>>see it again, this time in latest(? ive seen no checkins for a week so
>>far) hostapd+wpasupplicant cvs on 2.6.14 with madwifi cvs (which still
>>has the acpi suspend/resume issue in ath-*.ko and wlan-ccmp.ko,
>>requiring module removal in acpi script before sleep and ifupdown
>>explicitly) :
>>
>>Nov  4 00:34:19 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
>>handshake completed (RSN)
>>Nov  4 00:34:55 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
>>authenticated
>>Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
>>deauthenticated due to local deauth request
>>
>>? its not gmk-rekey, occours 1 per h.
>>
>>Nov  4 00:34:58 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
>>deassociated
>>Nov  4 00:34:59 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
>>associated
>>Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
>>key handshake completed (RSN)
>>Nov  4 00:35:00 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
>>authenticated
>>
>>-no more gtk rekeying until wpasupplicant restart.
>>
>>Nov  4 01:13:46 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
>>deassociated
>>Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.11:
>>associated
>>Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: pairwise
>>key handshake completed (RSN)
>>Nov  4 01:13:54 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 IEEE 802.1X:
>>authenticated
>>Nov  4 01:18:47 tom3 hostapd: ath0: STA 00:0f:3d:af:91:99 WPA: group key
>>handshake completed (RSN)
>>...
>>
>>
>>
>>>Can you provide a debug log from hostapd showing this kind of behavior
>>>(with some additional comments on where you would have expected to see
>>>group key handshake)?
>>>
>>
>>
>>ok. i do it next, this is a security issue. windows+mac rsn clients not
>> involved and rekeying normal with hostapd.
>>
> 
> 
> hm. with both started in debug mode, this issue does NOT occur.
> 
> debug log says local deauth request with wireless-event 5.
> 
> maybe a debug "if{}else" is buggy in the code or the last old code cvs madwifi driver. 
> 

ah. its a eap reauth failure: (debug logs later)


tom2:~# ifup ath0
Trying to associate with 00:0f:b5:63:e0:f2 (SSID='madwifi' freq=2422 MHz)
Associated with 00:0f:b5:63:e0:f2
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:0f:b5:63:e0:f2 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:63:e0:f2 completed (auth)
dhcpcd.exe: wrong interface name "ath0"

WPA: Group rekeying completed with 00:0f:b5:63:e0:f2 [GTK=CCMP]
...
WPA: Group rekeying completed with 00:0f:b5:63:e0:f2 [GTK=CCMP]
WPA: Group rekeying completed with 00:0f:b5:63:e0:f2 [GTK=CCMP]
...
~1h
...
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:0f:b5:63:e0:f2 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:0f:b5:63:e0:f2 (SSID='madwifi' freq=2422 MHz)
Associated with 00:0f:b5:63:e0:f2
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success)
WPA: Key negotiation completed with 00:0f:b5:63:e0:f2 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:63:e0:f2 completed (reauth) <------------------
CTRL-EVENT-EAP-FAILURE EAP authentication failed
...
no more group rekeying. manual restart needed

but inet further online in spite of reauth failure(!)

i try disabling fast_reauth...






From proski  Sat Nov  5 01:56:16 2005
From: proski (Pavel Roskin)
Date: Sat, 05 Nov 2005 04:56:16 -0500
Subject: hostap_pci and recent kernels
Message-ID: <1131184576.3967.3.camel@dv>

Hello!

Since the problems with hostap_pci on the latest kernels have been
reported, I decided to test them too.

I'm using current netdev kernel from git on a x86_64 system (single
EM64T with hyperthreading enabled).  hostap_pci is not working properly.
It keeps reporting WTERR and INFDROP events once in a few seconds.

I tried the included hostap, the CVS version and 0.3.9 - all of them
exhibit this problem.  I guess the problem is related to the kernel
somehow, but hostap should be doing something wrong too.

The CVS version of orinoco_pci doesn't have this problem.  It would
report INFDROP events if there were some, but it doesn't report any
errors.

The card is a MiniPCI card in a MiniPCI-to-PCI adapter.

Actually, the card is working (I tested scanning and monitor mode), it
just keeps spewing those messages.

hostap_crypt: registered algorithm 'NULL'
hostap_pci: CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 233
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
prism2_hw_init: initialized in 196 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: Intersil Prism2.5 PCI: mem=0xd0000000, irq=233
wifi0: registered netdevice wlan0
wlan0: Host AP mode does not support 'Any' essid
wifi0: Command completion event, but no pending commands
Already released txfid found at idx 3
wifi0: WTERR event
wifi0: INFDROP event
wifi0: Command completion event, but no pending commands
Already released txfid found at idx 4
wifi0: WTERR event
wifi0: INFDROP event
wifi0: hfa384x_cmd_issue: cmd reg was busy for 1 usec
wifi0: hfa384x_cmd_issue: cmd reg was busy for 1 usec

# cat /proc/interrupts 
           CPU0       CPU1       
  0:     212732          0    IO-APIC-edge  timer
  1:       2605          0    IO-APIC-edge  i8042
  8:          3          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
14:       7369          0    IO-APIC-edge  ide0
50:      30277          0   IO-APIC-level  uhci_hcd:usb5, Intel ICH6
58:      10682          0   IO-APIC-level  libata
169:        847          0   IO-APIC-level  tg0
177:          0          0   IO-APIC-level  yenta
217:          2          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
225:          0          0   IO-APIC-level  uhci_hcd:usb3
233:        846          0   IO-APIC-level  uhci_hcd:usb4, wifi0
NMI:         92         72 
LOC:     212683     212674 
ERR:          1
MIS:          0

]# lspci -vx -s 04:02.0
04:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)
        Subsystem: Intersil Corporation Prism 2.5 Wavelan chipset
        Flags: bus master, medium devsel, latency 64, IRQ 233
        Memory at d0000000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
00: 60 12 73 38 17 01 90 02 01 00 80 02 10 40 00 00
10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 60 12 73 38
30: 00 00 00 00 dc 00 00 00 00 00 00 00 03 01 00 00

-- 
Regards,
Pavel Roskin




From ged  Sat Nov  5 04:54:55 2005
From: ged (G.W. Haywood)
Date: Sat, 5 Nov 2005 12:54:55 +0000 (GMT)
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <20051105000120.0ADE65642BE@mail.iocaine.com>
References: <20051105000120.0ADE65642BE@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0511051205080.29328@mail3.jubileegroup.co.uk>

Hi there,

On Fri, 4 Nov 2005 hostap-request at shmoo.com wrote:

> In search of HOSTAP MAINTAINERS - are you hiding?
> [...]
> This is the third message I've posted with the same log info.

You are well out of order, Mr. Salzenberg - perhaps you posted to the
wrong list?  Your fortuitously uncommon hostname 'tytlal' does not
appear in my list archive before 3 November and the first message that
I can see on this list from your address arrived yesterday.  There was
no log information in it:

> Message: 9
> Date: Thu, 3 Nov 2005 11:15:08 -0800
> From: Chip Salzenberg <chip at pobox.com>
> Subject: Re: interrupt delivery does not seem to work
> To: Miernik <miernik at ffii.org>
> Cc: hostap at shmoo.com
> Message-ID: <20051103191508.GD6816 at tytlal.topaz.cx>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Nov 03, 2005 at 02:40:49PM +0100, Miernik wrote:
> > | wlan0: interrupt delivery does not seem to work
>
> I'm getting that too.  I have yet to get any reply from this list, or
> from linux-kernel.  I wonder how a driver can get developed and put in
> the kernel tree while no attention is paid to bug reports...

Hostap is one of the most stable and well-supported community projects
that I know of, and people get a lot more and better support here a lot
quicker than were they to be using some product that they'd paid for.

I don't think anyone here will hold a grudge, but all the same an
apology would be in order.  There'll be no more from me on this subject.

73,
Ged.

In

http://www.kerneltraffic.org/kernel-traffic/kt20000710_75.html#1

Chip Salzenberg put in,

My experience in the Perl community has taught me that tolerating or
even celebrating buttheads who happen to be technically prolific is,
in the end, very costly. It creates a skin-thickness requirement. Some
who might have contributed leave rather than putting up with verbal
abuse. A once-friendly community is be sacrificed on the altar of
technical advancement... ironically, to the eventual detriment of
both.

In a later post, Chip added:

Hans happened to trigger the discussion, and I happen to dislike his
conspiracy theories, so I could see how it would look like I'm picking
on him specifically. But I'm not. I'm just taking this opportunity to
discuss the theory and practice of open source cooperation.

See also

http://en.wikipedia.org/wiki/Chip_Salzenberg



From castet.matthieu  Sat Nov  5 05:56:11 2005
From: castet.matthieu (matthieu castet)
Date: Sat, 05 Nov 2005 14:56:11 +0100
Subject: wpa rekey
Message-ID: <436CB9FB.3000503@free.fr>

Hi,

I have a question about WPA rekey.

My driver always use the WPA key at index 0 and never used the rekey key ?

Why ?
It is a configuration problem on the AP, on the client driver ?

When does a peer choose to change the key index ?

Thanks

Matthieu



From jkmaline  Sat Nov  5 07:40:37 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 5 Nov 2005 07:40:37 -0800
Subject: wpa rekey
In-Reply-To: <436CB9FB.3000503@free.fr>
References: <436CB9FB.3000503@free.fr>
Message-ID: <20051105154037.GA9260@jm.kir.nu>

On Sat, Nov 05, 2005 at 02:56:11PM +0100, matthieu castet wrote:

> I have a question about WPA rekey.
> 
> My driver always use the WPA key at index 0 and never used the rekey key ?
> 
> Why ?

If you are talking about pairwise (i.e., per-station unicast key), it is
always using key index 0. In other words, rekeying changes the key
itself, but key index remains the same. As far as group
(broadcast/multicast) keys are concerned, AP may decide to change the
key index (1 .. 3), but there is no requirement to do so. I would assume
most implementations to rotate between key index 1 and 2, though.

> It is a configuration problem on the AP, on the client driver ?

No.

> When does a peer choose to change the key index ?

AP decides which key index to use.

-- 
Jouni Malinen                                            PGP id EFC895FA



From gentoopower  Sat Nov  5 08:42:06 2005
From: gentoopower (Stefan)
Date: Sat, 05 Nov 2005 17:42:06 +0100
Subject: hostap_pci and recent kernels
In-Reply-To: <1131184576.3967.3.camel@dv>
References: <1131184576.3967.3.camel@dv>
Message-ID: <436CE0DE.9090408@yahoo.de>

Pavel Roskin wrote:

>Hello!
>
>Since the problems with hostap_pci on the latest kernels have been
>reported, I decided to test them too.
>
>I'm using current netdev kernel from git on a x86_64 system (single
>EM64T with hyperthreading enabled).  hostap_pci is not working properly.
>It keeps reporting WTERR and INFDROP events once in a few seconds.
>
>I tried the included hostap, the CVS version and 0.3.9 - all of them
>exhibit this problem.  I guess the problem is related to the kernel
>somehow, but hostap should be doing something wrong too.
>  
>
Can you test with acpi=off boot param.

I have helped some folks on the ide mailinglist, who have problems since
2.6.13, a lot of acpi code
changed after 2.6.12 and it seems like CPUs with Hyperthreading have
various problems now.

>The CVS version of orinoco_pci doesn't have this problem.  It would
>report INFDROP events if there were some, but it doesn't report any
>errors.
>
>The card is a MiniPCI card in a MiniPCI-to-PCI adapter.
>
>Actually, the card is working (I tested scanning and monitor mode), it
>just keeps spewing those messages.
>
>hostap_crypt: registered algorithm 'NULL'
>hostap_pci: CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
>ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 233
>hostap_pci: Registered netdevice wifi0
>wifi0: Original COR value: 0x0
>prism2_hw_init: initialized in 196 ms
>wifi0: NIC: id=0x8013 v1.0.0
>wifi0: PRI: id=0x15 v1.1.1
>wifi0: STA: id=0x1f v1.7.4
>wifi0: Intersil Prism2.5 PCI: mem=0xd0000000, irq=233
>wifi0: registered netdevice wlan0
>wlan0: Host AP mode does not support 'Any' essid
>wifi0: Command completion event, but no pending commands
>Already released txfid found at idx 3
>wifi0: WTERR event
>wifi0: INFDROP event
>wifi0: Command completion event, but no pending commands
>Already released txfid found at idx 4
>wifi0: WTERR event
>wifi0: INFDROP event
>wifi0: hfa384x_cmd_issue: cmd reg was busy for 1 usec
>wifi0: hfa384x_cmd_issue: cmd reg was busy for 1 usec
>
># cat /proc/interrupts 
>           CPU0       CPU1       
>  0:     212732          0    IO-APIC-edge  timer
>  1:       2605          0    IO-APIC-edge  i8042
>  8:          3          0    IO-APIC-edge  rtc
>  9:          0          0   IO-APIC-level  acpi
>14:       7369          0    IO-APIC-edge  ide0
>50:      30277          0   IO-APIC-level  uhci_hcd:usb5, Intel ICH6
>58:      10682          0   IO-APIC-level  libata
>169:        847          0   IO-APIC-level  tg0
>177:          0          0   IO-APIC-level  yenta
>217:          2          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
>225:          0          0   IO-APIC-level  uhci_hcd:usb3
>233:        846          0   IO-APIC-level  uhci_hcd:usb4, wifi0
>NMI:         92         72 
>LOC:     212683     212674 
>ERR:          1
>MIS:          0
>
>]# lspci -vx -s 04:02.0
>04:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
>chipset (rev 01)
>        Subsystem: Intersil Corporation Prism 2.5 Wavelan chipset
>        Flags: bus master, medium devsel, latency 64, IRQ 233
>        Memory at d0000000 (32-bit, prefetchable) [size=4K]
>        Capabilities: [dc] Power Management version 2
>00: 60 12 73 38 17 01 90 02 01 00 80 02 10 40 00 00
>10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
>20: 00 00 00 00 00 00 00 00 00 00 00 00 60 12 73 38
>30: 00 00 00 00 dc 00 00 00 00 00 00 00 03 01 00 00
>
>  
>


	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de



From chip  Sat Nov  5 10:09:19 2005
From: chip (Chip Salzenberg)
Date: Sat, 5 Nov 2005 10:09:19 -0800
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <Pine.LNX.4.58.0511051205080.29328@mail3.jubileegroup.co.uk>
References: <20051105000120.0ADE65642BE@mail.iocaine.com>
	<Pine.LNX.4.58.0511051205080.29328@mail3.jubileegroup.co.uk>
Message-ID: <20051105180919.GI8649@tytlal.topaz.cx>

On Sat, Nov 05, 2005 at 12:54:55PM +0000, G.W. Haywood wrote:
> You are well out of order, Mr. Salzenberg - perhaps you posted to the
> wrong list?  Your fortuitously uncommon hostname 'tytlal' does not
> appear in my list archive before 3 November and the first message that
> I can see on this list from your address arrived yesterday.  There was
> no log information in it:

Perhaps your search methods are inadequate.
  Oct 30:  http://lists.shmoo.com/pipermail/hostap/2005-October/011706.html
  Nov 1:   http://lists.shmoo.com/pipermail/hostap/2005-November/011716.html

> I don't think anyone here will hold a grudge, but all the same an
> apology would be in order.

It would appear so.
-- 
Chip Salzenberg <chip at pobox.com>



From bferrell  Sat Nov  5 10:12:38 2005
From: bferrell (Bruce Ferrell)
Date: Sat, 05 Nov 2005 10:12:38 -0800
Subject: In search of HOSTAP MAINTAINERS - are you hiding?
In-Reply-To: <20051105180919.GI8649@tytlal.topaz.cx>
References: <20051105000120.0ADE65642BE@mail.iocaine.com>	<Pine.LNX.4.58.0511051205080.29328@mail3.jubileegroup.co.uk>
	<20051105180919.GI8649@tytlal.topaz.cx>
Message-ID: <436CF616.7070106@baywinds.org>

Chip Salzenberg wrote:
> On Sat, Nov 05, 2005 at 12:54:55PM +0000, G.W. Haywood wrote:
> 
>>You are well out of order, Mr. Salzenberg - perhaps you posted to the
>>wrong list?  Your fortuitously uncommon hostname 'tytlal' does not
>>appear in my list archive before 3 November and the first message that
>>I can see on this list from your address arrived yesterday.  There was
>>no log information in it:
> 
> 
> Perhaps your search methods are inadequate.
>   Oct 30:  http://lists.shmoo.com/pipermail/hostap/2005-October/011706.html
>   Nov 1:   http://lists.shmoo.com/pipermail/hostap/2005-November/011716.html
> 
> 
>>I don't think anyone here will hold a grudge, but all the same an
>>apology would be in order.
> 
> 
> It would appear so.

Chip,

My mail archive for the list shows your first message on 10/30/2005 with 
log info.

Maybe he didn't search on your e-mail address?

BTW, I liked your quoted comments from the kernel list.




From brix  Sat Nov  5 11:13:52 2005
From: brix (Henrik Brix Andersen)
Date: Sat, 5 Nov 2005 20:13:52 +0100
Subject: hostap_pci and recent kernels
In-Reply-To: <1131184576.3967.3.camel@dv>
References: <1131184576.3967.3.camel@dv>
Message-ID: <20051105191352.GB7627@dmz.brixandersen.dk>

On Sat, Nov 05, 2005 at 04:56:16AM -0500, Pavel Roskin wrote:
> I'm using current netdev kernel from git on a x86_64 system (single
> EM64T with hyperthreading enabled).  hostap_pci is not working properly.
> It keeps reporting WTERR and INFDROP events once in a few seconds.

I'm using the stand-along hostap-driver-0.4.5 in master mode on a
vanilla linux-2.6.14 without problems.

I'm using an Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
on a Soekris net4801.

Could this be a 64bit issue?

Regards,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Metadistribution | Mobile computing herd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 211 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051105/6267e4e7/attachment.pgp 


From shawn_adams  Sat Nov  5 15:39:50 2005
From: shawn_adams (Shawn Adams)
Date: Sun, 06 Nov 2005 00:39:50 +0100
Subject: wpa error message
In-Reply-To: <436BF2B8.5040506@dif.um.es>
References: <436BF2B8.5040506@dif.um.es>
Message-ID: <436D42C6.9070904@web.de>

Hello

Using wpa_supplicant 0.4.6 with a madwifi card.

the card works with a recent madwifi in WEP 128 mode, no issue.

Can anyone tell me what the following error message means:
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:20:d8:03:8a:bc completed (auth)
EAPOL: External notification - portValid=1
EAPOL: SUPP_PAE entering state AUTHENTICATED
Wireless event: cmd=0x8b2a len=12
RX EAPOL from 00:20:d8:03:8a:bc
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=108
  EAPOL-Key type=254
WPA: EAPOL-Key Replay Counter did not increase - dropping packet

This "dropping packet" message seems to coincide with 3 EAP key frames
sent by the AP.

right after the 3rd message, wpa drops, and blacklists the AP.

Any hints would be welcome.



-- 
Shawn Adams
shawn_adams at web.de




From ramalhais  Sat Nov  5 16:32:01 2005
From: ramalhais (Pedro Ramalhais)
Date: Sun, 6 Nov 2005 00:32:01 -0000 (WET)
Subject: hostap_pci and recent kernels
In-Reply-To: <20051105191352.GB7627@dmz.brixandersen.dk>
References: <1131184576.3967.3.camel@dv>
	<20051105191352.GB7627@dmz.brixandersen.dk>
Message-ID: <53455.192.168.1.4.1131237121.squirrel@fly.resnet.serrado.net>


Henrik Brix Andersen wrote:
> On Sat, Nov 05, 2005 at 04:56:16AM -0500, Pavel Roskin wrote:
>> I'm using current netdev kernel from git on a x86_64 system (single
>> EM64T with hyperthreading enabled).  hostap_pci is not working properly.
>> It keeps reporting WTERR and INFDROP events once in a few seconds.
>
> I'm using the stand-along hostap-driver-0.4.5 in master mode on a
> vanilla linux-2.6.14 without problems.
>
> I'm using an Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
> on a Soekris net4801.
>
> Could this be a 64bit issue?
>
> Regards,
> Brix
> --
> Henrik Brix Andersen <brix at gentoo.org>
> Gentoo Metadistribution | Mobile computing herd
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>

I recently upgrade to 2.6.14 and i'm using the in-kernel hostap drivers.
Everythings works fine, using WDS too, and no weird messages.
The processor is an Intel Celeron 600Mhz.
If you need my .config i'd be glad to provide it.
Hope this helps.

-- 
Pedro Ramalhais
ramalhais_ at _serrado.net
--
God is real, unless declared integer.




From bryan  Sat Nov  5 18:39:15 2005
From: bryan (Bryan Kadzban)
Date: Sat, 05 Nov 2005 21:39:15 -0500
Subject: wpa error message
In-Reply-To: <436D42C6.9070904@web.de>
References: <436BF2B8.5040506@dif.um.es> <436D42C6.9070904@web.de>
Message-ID: <436D6CD3.5070401@kadzban.is-a-geek.net>

Shawn Adams wrote:
> Can anyone tell me what the following error message means:
>
> RX EAPOL from 00:20:d8:03:8a:bc
> EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
> IEEE 802.1X RX: version=1 type=3 length=108
>   EAPOL-Key type=254
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet

Probably the supplicant not being notified that the connection dropped
and came back, but possibly a bug in your AP -- depending on when this
happens.

The replay counter that it's talking about is a 64-bit value in the
EAPOL-Key frame, which is used to make sure the supplicant only sees one
copy of each EAPOL-Key frame.  If it sees 2 frames with a replay counter
value that doesn't increment, it knows that the last one is a duplicate,
and drops it.

The replay counter is supposed to reset to 0 in the AP and on the client
on every association or reassociation.

I got output similar to that when using Cisco APs and the windows port
of wpa_supplicant -- I wasn't running ndis_events, so association events
weren't being reported to wpa_supplicant, so it was seeing what it
thought was a repeated replay counter value.  (Because the AP reset the
counter on the STA's reassociation, but the supplicant didn't know it
had reassociated, so it didn't reset its counter.)

So if you're running this on Windows, make sure that ndis_events is
running.  If you're running it on Linux, then make sure that however
your backend driver (wext?) reports associations/reassociations is
actually getting through to the supplicant.

Also, when does it happen?  When the AP's radio resets perhaps, or at
some other point where a reassociation should be happening?  And what's
the value of the replay counter in the dropped frame?  (-dd will show
you packet dumps of everything except keys, so that would be one way to
find out.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051105/579bd478/attachment.pgp 


From jkmaline  Sat Nov  5 19:40:23 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 5 Nov 2005 19:40:23 -0800
Subject: wpa_supplicant win98 wired patch
In-Reply-To: <Pine.LNX.4.44.0511031320240.26586-100000@eloth.gjh.sk>
References: <Pine.LNX.4.44.0511031320240.26586-100000@eloth.gjh.sk>
Message-ID: <20051106034022.GA8972@jm.kir.nu>

On Thu, Nov 03, 2005 at 01:23:58PM +0100, Jozef Vesely wrote:

> 1. If I "cross" compile (mingw) wpa_supplicant on linux
> for windows with WpdPack_3_1.zip from
> http://www.winpcap.org/install/bin/WpdPack_3_1.zip
> I get folowing error.
> 
> l2_packet_pcap.c:87: error: conflicting types for `pcap_sendpacket'
> ../WpdPack/Include/pcap.h:247: error: previous declaration of `pcap_sendpacket'

It looks like WinPcap 3.1 changed the pcap_sendpacket() prototype. I
updated my build system to use the latest WinPcap release and removed
the not (anymore) needed prototype definition from l2_packet_pcap.c.

> 2. On Windows 98 Packet.dll 3.0 alpha3 does not provide descriptions in
> PacketGetAdapterNames:

> NDIS: mismatch in adapter name and description counts (1 != 0)
> 
> Packet.dll 3.1 works OK. I suggest simple fix in driver_ndis.c

Thanks, applied.

> 3. If I want wpa_supplicant to authentificate with our campus
> wired 802.1x network, it is needed to allow reception of packets
> destined to 01:80:c2:00:00:03 (PAE group address).

Thanks, applied.


PS.

This was the first time I remember having heard of someone testing
wpa_supplicant with Win98. I take it that it worked with these changes
on wired network. Did you happen to test wireless authentication on
Win98? I would like to update the list of known-to-work versions in
README-Windows.txt if someone has successfully tested wpa_supplicant on
a Windows 98 system with a wireless card.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov  5 20:03:46 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 5 Nov 2005 20:03:46 -0800
Subject: wpa error message
In-Reply-To: <436D42C6.9070904@web.de>
References: <436BF2B8.5040506@dif.um.es> <436D42C6.9070904@web.de>
Message-ID: <20051106040346.GB8972@jm.kir.nu>

On Sun, Nov 06, 2005 at 12:39:50AM +0100, Shawn Adams wrote:

> Using wpa_supplicant 0.4.6 with a madwifi card.

> Can anyone tell me what the following error message means:
> State: GROUP_HANDSHAKE -> COMPLETED
> CTRL-EVENT-CONNECTED - Connection to 00:20:d8:03:8a:bc completed (auth)
> EAPOL: External notification - portValid=1
> EAPOL: SUPP_PAE entering state AUTHENTICATED
> Wireless event: cmd=0x8b2a len=12
> RX EAPOL from 00:20:d8:03:8a:bc
> EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
> IEEE 802.1X RX: version=1 type=3 length=108
>   EAPOL-Key type=254
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet

Could you please send full debug log from the beginning to this point
with -ddt on the command line? It would also be useful to get a packet
capture log (e.g., with Ethereal or tcpdump from the ath0 interface on
the client).

> This "dropping packet" message seems to coincide with 3 EAP key frames
> sent by the AP.
> 
> right after the 3rd message, wpa drops, and blacklists the AP.

Those packets were likely reauthentication and either the
(re)association was missed somehow or the AP has a bug in its WPA
implementation. AP is disconnecting at this point since it did not
receive a reply from the station. What kind of AP are you using
(vendor/model/firmware version)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov  5 20:15:43 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 5 Nov 2005 20:15:43 -0800
Subject: [2.6 patch] rename hostap.c to hostap_main.c
In-Reply-To: <20051106005343.GF3668@stusta.de>
References: <20051106005343.GF3668@stusta.de>
Message-ID: <20051106041543.GC8972@jm.kir.nu>

On Sun, Nov 06, 2005 at 01:53:43AM +0100, Adrian Bunk wrote:
> I wanted to remove the #include "hostap_ioctl.c" from hostap.c and build 
> hostap_ioctl.c separately, but this doesn't work since hostap.c has the 
> same name as the module.

Is this patch changing anything in hostap.c or is it just a rename of
the file? Patch file is not exactly ideal for this kind of changes and I
hope git has a better way of storing this kind of rename.

I would rather not rename the file, but if this is the only way of
getting the module built in pieces, I'm okay with the change (assuming
nothing else changed in hostap.c in this changeset).


> +++ linux-2.6.14-rc5-mm1-full/drivers/net/wireless/hostap/Makefile	2005-11-06 00:14:57.000000000 +0100
> @@ -1,5 +1,7 @@
> -obj-$(CONFIG_HOSTAP_CS) += hostap_cs.o
> -obj-$(CONFIG_HOSTAP_PLX) += hostap_plx.o
> -obj-$(CONFIG_HOSTAP_PCI) += hostap_pci.o
> +obj-$(CONFIG_HOSTAP)		+= hostap.o
> +
> +obj-$(CONFIG_HOSTAP_CS)		+= hostap_cs.o
> +obj-$(CONFIG_HOSTAP_PLX)	+= hostap_plx.o
> +obj-$(CONFIG_HOSTAP_PCI)	+= hostap_pci.o

Why were the hostap_{cs,plx,pci} lines changed? I prefer the original
version of those lines (i.e., no extra padding).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jar  Sun Nov  6 03:48:50 2005
From: jar (Jar)
Date: Sun, 6 Nov 2005 13:48:50 +0200 (EET)
Subject: [Off topic] Difference between wpa: tkip & aes
Message-ID: <1793.192.168.0.150.1131277730.squirrel@kone>


Hello

With Liksys wrt54g AP I can select WPA-PSK and then I have two alternatives: TKIP
and AES. When I capture some packets with wireless sniffer and then comparing these
two methods (tkip/aes), I can't see no dirrerence. In both cases the APs beacon
probes looks like the same and also the data packets seems to be only TKIP/WEP
protected in both cases. I can't see AES or CCMP anywhere even if the WPA-PSK/AES is
selected, should I? What is the dirrefence between TKIP/AES?

It is also possible to select WPA2-PSK and then again two alternatives: TKIP and
AES. Can someone explain the magic behind these modes?

I want to use WPA-PSK with AES. What should I look for in the sniffed packets to
ensure that the encryption uses AES and not TKIP/WEP?

-- 
Best Regards, Jar



From castet.matthieu  Sun Nov  6 04:08:27 2005
From: castet.matthieu (matthieu castet)
Date: Sun, 06 Nov 2005 13:08:27 +0100
Subject: wpa rekey
In-Reply-To: <20051105154037.GA9260@jm.kir.nu>
References: <436CB9FB.3000503@free.fr> <20051105154037.GA9260@jm.kir.nu>
Message-ID: <436DF23B.5040608@free.fr>

Hi Jouni,

Jouni Malinen wrote:
> 
> If you are talking about pairwise (i.e., per-station unicast key), it is
> always using key index 0. In other words, rekeying changes the key
> itself, but key index remains the same. As far as group
> (broadcast/multicast) keys are concerned, AP may decide to change the
> key index (1 .. 3), but there is no requirement to do so. I would assume
> most implementations to rotate between key index 1 and 2, though.
> 
Thanks, now I understand.
Only the GTK is rekey and it is only used for broadcast/multicast frames
from AP.


Matthieu




From bryan  Sun Nov  6 05:21:48 2005
From: bryan (Bryan Kadzban)
Date: Sun, 06 Nov 2005 08:21:48 -0500
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <1793.192.168.0.150.1131277730.squirrel@kone>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
Message-ID: <436E036C.6040402@kadzban.is-a-geek.net>

Jar wrote:
> When I capture some packets with wireless sniffer and then comparing
> these two methods (tkip/aes), I can't see no dirrerence. In both
> cases the APs beacon probes looks like the same

Well, with WPA-PSK, the beacons would only differ by a small number of
bytes, I think.  The only thing that would change is the pairwise (and
possibly group, but I don't know for sure what Linksys's APs use for
broadcast when in WPA-PSK/AES mode) encryption method, and that's stored
in just one byte in the WPA IE.

With WPA2, that one byte would change from a 01 to a 02, but I'm not
sure which values it would take on with WPA.

> and also the data packets seems to be only TKIP/WEP protected in both
> cases.

How did you come to that conclusion?  Were you looking at directed
packets, or broadcast/multicast packets?

> It is also possible to select WPA2-PSK and then again two
> alternatives: TKIP and AES. Can someone explain the magic behind
> these modes?

See:

http://mail.iocaine.com/pipermail/hostap/2005-November/011725.html

from 4 days ago, and also Jouni's followup (I had a few things wrong in
that post).

> I want to use WPA-PSK with AES. What should I look for in the sniffed
> packets to ensure that the encryption uses AES and not TKIP/WEP?

What makes you think they're using TKIP now?  I guess I always assumed
that the encryption method matched what I had configured on both the
client and AP sides, so I never figured out how to tell the difference
just by looking at data packets.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051106/8de7647e/attachment.pgp 


From jar  Sun Nov  6 05:54:31 2005
From: jar (Jar)
Date: Sun, 06 Nov 2005 15:54:31 +0200
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <436E036C.6040402@kadzban.is-a-geek.net>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
	<436E036C.6040402@kadzban.is-a-geek.net>
Message-ID: <436E0B17.5050402@pcuf.fi>

Bryan Kadzban wrote:
> How did you come to that conclusion?  Were you looking at directed
> packets, or broadcast/multicast packets?

Unicast data packets.

> What makes you think they're using TKIP now?  I guess I always assumed
> that the encryption method matched what I had configured on both the
> client and AP sides, so I never figured out how to tell the difference
> just by looking at data packets.

Because the sniffer shows that the data packets are WEP protected. 
Looking inside the data packet there is mention about TKIP.

When using Kismet, it complains about some weak keys after 24h traffic. 
  I assume that the weak key problem is because TKIP/WEP method is 
actually used and not CCMP-AES.

Or is it so that you can't see via sniffer is the encryption TKIP or 
AES? How to 100% verify the security of the connection then?

-- 
Best Regards, Jar



From lims  Sun Nov  6 06:34:38 2005
From: lims (limor)
Date: Sun, 6 Nov 2005 16:34:38 +0200
Subject: Can't get beyond group key handshake 
Message-ID: <JAEIKABDHEIDLCHFDJPGEEHFCGAA.lims@connectone.com>

Hi,
I am trying to use a code that's based on hostAP to test WPA on an embedded
device connected to a Prism3 CF card.
I am able to finish the 4-Way parwise key handshake, and then receive,
decrypt and reply to the first group key message, but even though my reply
is decrypted with no problem by the sniffer I am using and all the fields
seem correct, after 5 seconds the AP (a D-Link DWL-2100AP) seems to re-start
the 4-Way handshake.
The second 4-Way handshake will also look the same - after 4 (pairwise) + 2
(group) key packets + 5 seconds it will re-start again, and so on and on
forever.
With a HostAP driver running on a Suse machine with the same CF card and the
same AP, another 4-Way handshake only starts after a few minutes (though I
was never able to actually send or recieve packets over that link either).
What can be the problem???
At this point my implementation does not generate good random numbers -
can that have anything to do with it?

thanks,
Limor.






From lims  Sun Nov  6 08:07:45 2005
From: lims (limor)
Date: Sun, 6 Nov 2005 18:07:45 +0200
Subject: how to cleanup a previous hostap installation
Message-ID: <JAEIKABDHEIDLCHFDJPGEEHGCGAA.lims@connectone.com>

Hi,
I had a HostAP driver compiled, installed and working on my Suse machine
with a DCF-66W card, and I used it with wpa_supplicant to connect to a WPA
enabled AP for a while.
In the last few days something went wrong and now as long as hostap_cs.conf
exists in etc/pcmcia HostAp tries to load but fails and iwconfig shows -
"wifi0 	no wireless extensions".
I renamed the conf file re-started - the orinoco driver loads and the card
works well as "eth1".
recompiling HostAP does not seem to help.

This is from my current dmesg log -
>hostap_cs: Registered netdevice wifi0
>hostap_cs: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x013f
>prism2_hw_init: initialized in 232 ms
>wifi0: hfa384x_cmd: entry still in list? (entry=c6285b80, type=0, res=0)
>wifi0: hfa384x_cmd: command wasnot completed (res=0, entry=c6295b80,
type=0, cmd=0x0001, param0=0x0000, EVSTAT=8000, INTEN=0010)
>wifi0: MAC port 0 enabling failed
>wifi0: could not enable MAC port

and so on (a list of initialization errors) until eventually -

>hostap_cs: Shutdown failed

I am new to linux - are there files that I can manually delete in order to
make sure I really start-over with the hostAP installation (before I go to
the extreme measure of re-installing Suse)?..

Thanks,
Limor.





From jkmaline  Sun Nov  6 10:04:18 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 10:04:18 -0800
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <436E0B17.5050402@pcuf.fi>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
	<436E036C.6040402@kadzban.is-a-geek.net> <436E0B17.5050402@pcuf.fi>
Message-ID: <20051106180418.GC9194@jm.kir.nu>

On Sun, Nov 06, 2005 at 03:54:31PM +0200, Jar wrote:

> Because the sniffer shows that the data packets are WEP protected. 
> Looking inside the data packet there is mention about TKIP.

The sniffer has no way of knowing that they are WEP protected unless is
takes a look at what happened during association.

> When using Kismet, it complains about some weak keys after 24h traffic. 
>   I assume that the weak key problem is because TKIP/WEP method is 
> actually used and not CCMP-AES.

That weak key claim is probably valid only if WEP was used (i.e., not
for TKIP and certainly not for CCMP). Anyway, even for WEP, there are
more efficient ways of cracking the key than weak keys, so reporting
weak is kind of pointless for WEP nowadays.. It is weak, no matter what
key is used.

> Or is it so that you can't see via sniffer is the encryption TKIP or 
> AES? How to 100% verify the security of the connection then?

There are no clear differences in TKIP and CCMP frame format that would
be clearly pointing out which one is being used. You could probably
figure out which one it is by looking at number of frames and how the
IV/packet number/TSC fields are being incremented since that part is
somewhat different between TKIP and CCMP. Anyway, the proper
verification would be to take a look at what kind of WPA/RSN IE was used
in (Re)Association Request (and later authenticated during 4-Way
Handshake).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov  6 10:09:12 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 10:09:12 -0800
Subject: how to cleanup a previous hostap installation
In-Reply-To: <JAEIKABDHEIDLCHFDJPGEEHGCGAA.lims@connectone.com>
References: <JAEIKABDHEIDLCHFDJPGEEHGCGAA.lims@connectone.com>
Message-ID: <20051106180912.GD9194@jm.kir.nu>

On Sun, Nov 06, 2005 at 06:07:45PM +0200, limor wrote:

> I am new to linux - are there files that I can manually delete in order to
> make sure I really start-over with the hostAP installation (before I go to
> the extreme measure of re-installing Suse)?..

Removing the installed kernel modules is probably the best way of doing
this. In addition, you can remove hostap_cs.conf. This can be done,
e.g., with following commands.

find /lib/modules/`uname -r` -name 'hostap*o' -exec rm {} \;
rm /etc/pcmcia/hostap_cs.conf

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov  6 10:54:29 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 10:54:29 -0800
Subject: hostapd and tkip countermeasures
In-Reply-To: <W777010846212501130907942@webmail2>
References: <W777010846212501130907942@webmail2>
Message-ID: <20051106185429.GJ9194@jm.kir.nu>

On Wed, Nov 02, 2005 at 05:05:42AM +0000, divy at speakeasy.net wrote:

> Please find a proposed patch in attachement which adds the hostapd_set_countermeasures() functionality and uses it for the madwifi driver.
> The patch was created against hostapd-0.4.6.

Thanks! Applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Sun Nov  6 11:35:40 2005
From: bryan (Bryan Kadzban)
Date: Sun, 06 Nov 2005 14:35:40 -0500
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <20051106180418.GC9194@jm.kir.nu>
References: <1793.192.168.0.150.1131277730.squirrel@kone>	<436E036C.6040402@kadzban.is-a-geek.net>
	<436E0B17.5050402@pcuf.fi> <20051106180418.GC9194@jm.kir.nu>
Message-ID: <436E5B0C.2030902@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> There are no clear differences in TKIP and CCMP frame format that
> would be clearly pointing out which one is being used.

Right -- after encryption, the data is supposed to look pretty much
random to someone that doesn't do any decryption on it.  This makes it
hard to tell what encryption method was used -- I believe that even WEP
looks just about as random as anything else.  (Though maybe that's
changed now.)

> Anyway, the proper verification would be to take a look at what kind
> of WPA/RSN IE was used in (Re)Association Request (and later
> authenticated during 4-Way Handshake).

That's what I've done -- specifically, I look at the part of the WPA/RSN
IE that says which encryption methods are supported and requested (in
all of the (re)association requests, beacons, probe responses, and the
frames in the 4-way handshake), and assume that the client and AP honor
those.

The fields in question contain an OUI and a 1-byte number, where the OUI
is for vendor-specific encryptions, but a standard OUI and byte are
specified for either TKIP or CCMP.  (The IE format, OUI values, and byte
values are part of 802.11i, which is downloadable from IEEE as part of
their "Get 802" thingy.  I'm pretty sure they're in section 7 of the
spec -- but definitely whichever section is named "Frame Formats".)

Ethereal is also helpful decoding these IEs and bytes, if you have a
capture file in a format that it can read.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051106/dea86ffe/attachment.pgp 


From jkmaline  Sun Nov  6 11:40:53 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 11:40:53 -0800
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <20051031185250.GA18468@kadzban.is-a-geek.net>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>
Message-ID: <20051106194053.GM9194@jm.kir.nu>

On Mon, Oct 31, 2005 at 01:52:50PM -0500, Bryan Kadzban wrote:

> At times, when we reset the radios on these APs (for instance, when the
> AP restarts, or when we change a setting on the relevant SSID / virtual
> BSSID), the "RSN capabilities" field in the RSN IE in the beacons and
> probe responses will change.  I've seen these APs go from advertising 1
> PTKSA counter/1 GTKSA counter to 4 of each, and sometimes they go from 4
> to 1.  It's (so far) always either 4 or 1, though, and the PTKSA counter
> count is always the same as the GTKSA counter count.

This sounds like enabling/disabling WMM which uses four separate TX
queues.

> I believe it is legal (according to 802.11i) for an AP to change its RSN
> IE like this, as long as it can inform clients of the new IE.  But I'm
> not sure; maybe it is invalid.

This is indeed allowed behavior and the main problem is in getting the
client to update its WPA/RSN IE from Beacon/ProbeRsp frames.

> How can I either clear the stored AP RSN IE, or update it with the
> current probe response / beacon frames' contents?  Is it possible at all
> using the control interface?  Or is it possible with NDIS somehow?

wpa_supplicant should ask the driver for the IE after each association.
I haven't tested this, but if this is not the case, wpa_supplicant
should be fixed to do this. However, this is not enough, since also the
NDIS driver has to update its BSSID list to include the latest WPA/RSN
IE.


On Mon, Oct 31, 2005 at 04:40:09PM -0500, Bryan Kadzban wrote:

> So the problem is still there, but the problem isn't that set_ap_rsn_ie
> doesn't get called.  The problem is that the scan results table is out
> of date, and it returns the wrong IE.

OK, this is nice to hear (well, from wpa_supplicant view point at least
;-).

> I have tried doing a "wpa_cli scan" while the supplicant is in this
> state (to update the scan results table), but that refuses to ever
> reconnect to the current AP, for some reason.  I believe it's an issue
> with the NDIS driver in use (Linksys's driver for their WMP54GS> cards),
> but I don't know that for sure.

Hmm.. "wpa_cli scan" should not break association; NDIS spec requires
that scan request can be issued at any time.. Do you mean that the
driver refuses to reconnect to the AP or that wpa_supplicant does not
allow the authentication after this?

The problem here seems to be in getting the driver to update its BSSID
table. Some drivers are known to cache results for a while and I've seen
some drivers not updating this data for a long while. It may be possible
to change some parameters in the registry to start timing out BSSID data
more quickly with some drivers. Likewise, I've seen at least some
vendors improving on this area over time, so updating to the latest
driver may also help with this.

> (So the log I attached isn't worth much.  I could attach another log if
> needed, but it'll take some doing to get it below the message-size
> threshold that this list has.)

You can send longer logs directly to my email address, if needed. NDIS
driver not updating BSSID data is not really a supplicant issue, so that
is somewhat less interesting for me, but if the "wpa_cli scan" is
triggering wpa_supplicant to do something incorrectly, that should be
fixed.


On Thu, Nov 03, 2005 at 07:06:18AM -0500, Bryan Kadzban wrote:

> I've since tried a couple things.  Using ap_scan=1 instead of 2 makes
> scanning not kill the connection at least -- although after some
> consideration, I think scanning every few minutes is probably not a
> great way to fix this issue.

WPA2 (and even roaming in general) actually assumes that drivers are
doing periodic background scanning.. However, this should not require
manual trigger. 

> Since the changing value is always the RSN capabilities field, and
> always the number of PTKSA/GTKSA replay counters, I changed the code to
> zero out those replay counter bits in both IEs just before it does its
> memcmp.  (I actually made a copy first, because I'm not sure what else
> those pointers are used for.)  This does work -- the client does come
> back after an AP restart changes that value.

Those replay counters are not really used for anything in the
supplicant.

> Does this have any security implication?  I don't think so (especially
> since I left the rest of the capabilities field as-is), but I don't know
> for sure; maybe someone else here does?

Doing this kind of masking of the IEs is against the standard, but I
don't see it causing any security problems, so it should be fine as a
workaround for the driver not updating BSSID data.

> It's also only a temporary workaround, I think, until we can fix our APs
> to not change that IE.  But still, I'm not sure what the implications
> are security wise.  (I don't really completely understand what those
> replay counters do -- just watch for reused IVs?  then why would you
> need more than one per PTKSA?)

The APs are allowed to change WPA/RSN IE. Though, I have to admit it is
somewhat surprising thing to do if you did not change configuration
(disabled/enabled WMM) at that point.

WPA/RSN IE is just used to advertise how many replay counters are
supported. WMM needs four (i.e., one for each TX queue). I would assume
that most drivers ignore these values completely and use separate replay
counters regardless of what is being advertised.

The proper fix for the issue would be to fix the NDIS driver to update
its BSSID data to match with the latest Beacon/ProbeRsp frames received
from the AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From asattari  Sun Nov  6 11:44:27 2005
From: asattari (asattari at site.uottawa.ca)
Date: Sun, 6 Nov 2005 14:44:27 -0500 (EST)
Subject: VoIp software
In-Reply-To: <20051106180912.GD9194@jm.kir.nu>
References: <JAEIKABDHEIDLCHFDJPGEEHGCGAA.lims@connectone.com>
	<20051106180912.GD9194@jm.kir.nu>
Message-ID: <4533.127.0.0.1.1131306267.squirrel@127.0.0.1>

hello all,

I am looking for some VoIp software specialy one which is Linux based,
free or not. can any one help me and give me his/experience in this
matter.

Thanks in advance




From jkmaline  Sun Nov  6 11:51:55 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 11:51:55 -0800
Subject: no more gtk rekeying after local deauth request
	(hostapd-wpa_supplicant)
In-Reply-To: <436AC255.3050904@gmx.de>
References: <4312B91A.3090302@gmx.de> <4312EB30.8000601@kadzban.is-a-geek.net>
	<4312FCEE.7080909@gmx.de>
	<20050829170157.GB3449@kadzban.is-a-geek.net>
	<4315D454.7070601@gmx.de> <43162709.7040800@gmx.de>
	<20050903155058.GY7781@jm.kir.nu> <436AC255.3050904@gmx.de>
Message-ID: <20051106195155.GN9194@jm.kir.nu>

On Fri, Nov 04, 2005 at 03:07:17AM +0100, thomas schorpp wrote:
> > On Wed, Aug 31, 2005 at 11:54:17PM +0200, thomas schorpp wrote:
> >>strange: if a linux wpasuppl. rsn client joins the net no more group key
> >>handshakes with this xp client with latest hostapd...?
> >>-> maybe security issue / policy violation

> -no more gtk rekeying until wpasupplicant restart.

> ok. i do it next, this is a security issue. windows+mac rsn clients not
>  involved and rekeying normal with hostapd.

I'm trying to remember what was the exact issue. Could you please give a
short summary of what the problems you have seen are?

If I understood correctly, you are using madwifi+hostapd as the AP and
have both Linux (madwifi+wpa_supplicant) and Windows/MAC clients using
WPA2.

Are you saying that hostapd stops rekeying group keys when both Linux
and Windows/MAC clients are associated, but this does not happen if
either only the Linux client associates or only Windows/MAC clients
associate? Or is rekeying only stopped for one of the clients and the
other clients continue getting new group keys?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov  6 12:23:57 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 12:23:57 -0800
Subject: Implementation question: 802.1X port
In-Reply-To: <436C3AD1.9010302@dif.um.es>
References: <436BF2B8.5040506@dif.um.es> <20051105015358.GA9392@jm.kir.nu>
	<436C3AD1.9010302@dif.um.es>
Message-ID: <20051106202357.GR9194@jm.kir.nu>

On Fri, Nov 04, 2005 at 11:53:37PM -0500, Rafa Marin Lopez wrote:

> I would be interested in checking all frames sent through uncontrolled 
> port even if they are data frames (they would be filtered by 
> uncontrolled port) . But following your comments, it would mean to touch 
> the madwifi driver right?

Yes, that's correct.

-- 
Jouni Malinen                                            PGP id EFC895FA



From HostAP-Research  Sun Nov  6 11:48:42 2005
From: HostAP-Research (AP-Research)
Date: Sun, 6 Nov 2005 13:48:42 -0600 (CST)
Subject: VoIp software
In-Reply-To: <4533.127.0.0.1.1131306267.squirrel@127.0.0.1>
References: <JAEIKABDHEIDLCHFDJPGEEHGCGAA.lims@connectone.com>
	<20051106180912.GD9194@jm.kir.nu>
	<4533.127.0.0.1.1131306267.squirrel@127.0.0.1>
Message-ID: <1177.67.174.172.10.1131306522.squirrel@www.maxrack.net>


<quote who="asattari at site.uottawa.ca">
> hello all,
>
> I am looking for some VoIp software specialy one which is Linux based,
> free or not. can any one help me and give me his/experience in this matter.

Definitely the wrong list for this question, but you might try:
http://www.asterisk.org/

-- 
Regards
KC Ferguson CIO/CTO
@RescuNET.com




From jar  Sun Nov  6 12:40:19 2005
From: jar (Jar)
Date: Sun, 6 Nov 2005 22:40:19 +0200 (EET)
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <20051106180418.GC9194@jm.kir.nu>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
	<436E036C.6040402@kadzban.is-a-geek.net> <436E0B17.5050402@pcuf.fi>
	<20051106180418.GC9194@jm.kir.nu>
Message-ID: <3047.192.168.0.154.1131309619.squirrel@kone>


> The sniffer has no way of knowing that they are WEP protected unless is
> takes a look at what happened during association.

OK, I am not a specialist, but the sniffer shows the data-packet as below when the
WPA-TKIP is selected. How the sniffer know that this data is WEP data?

Packet Info
  Flags:                0x00
  Status:               0x04  Encrypted
  Packet Length:        1562
  Timestamp:            00:18:39.435062200 11/03/2005
  Data Rate:            22  11.0 Mbps
  Channel:              11  2462 MHz
  Signal Level:         59%
  Noise Level:          0%
802.11 MAC Header
  Version:              0
  Type:                 %10  Data
  Subtype:              %0000  Data Only
Frame Control Flags:    %01000011
                        0... .... Non-strict order
                        .1.. .... WEP Enabled
                        ..0. .... No More Data
                        ...0 .... Power Management - active mode
                        .... 0... This is not a Re-Transmission
                        .... .0.. Last or Unfragmented Frame
                        .... ..1. Exit from the Distribution System
                        .... ...1 To the Distribution System

  Duration:             213  Microseconds
  Receiver:             00:14:BF:48:A1:A2
  Transmitter:          00:14:BF:2E:2E:2E
  Destination:          00:50:FC:5A:5A:5A  Edimax Tech:5A:5A:5A
  Seq. Number:          195
  Frag. Number:         0
  Source:               00:14:BF:22:22:22
802.11 TKIP Data
  WEP IV:               0x00201A
  RC4Key[0]:            0x00
  RC4Key[1]:            0x20
  RC4Key[2]:            0x1A

  TKIP Key Index:       0x20
  Reserved:             %00100
  Ext IV:               %0
  Key ID:               %00  Key ID=1

  TKIP SC:              0x00000000
  TKIP Data:
  ...||+.......V..  D5 04 B8 7C 7C 2B 84 1D 15 B5 0E D8 E2 56 A3 AF
  ....
  ....

And like this when WPA-AES is selected:

Packet Info
  Flags:                0x00
  Status:               0x04  Encrypted
  Packet Length:        1558
  Timestamp:            00:20:39.381721800 11/03/2005
  Data Rate:            22  11.0 Mbps
  Channel:              11  2462 MHz
  Signal Level:         60%
  Noise Level:          0%
802.11 MAC Header
  Version:              0
  Type:                 %10  Data
  Subtype:              %0000  Data Only
Frame Control Flags:    %01000011
                        0... .... Non-strict order
                        .1.. .... WEP Enabled
                        ..0. .... No More Data
                        ...0 .... Power Management - active mode
                        .... 0... This is not a Re-Transmission
                        .... .0.. Last or Unfragmented Frame
                        .... ..1. Exit from the Distribution System
                        .... ...1 To the Distribution System

  Duration:             213  Microseconds
  Receiver:             00:14:BF:48:A1:A2
  Transmitter:          00:14:BF:2E:2E:2E
  Destination:          00:50:FC:5A:5A:5A  Edimax Tech:5A:5A:5A
  Seq. Number:          91
  Frag. Number:         0
  Source:               00:14:BF:22:22:22
802.11 TKIP Data
  WEP IV:               0x0C0000
  RC4Key[0]:            0x0C
  RC4Key[1]:            0x00
  RC4Key[2]:            0x00

  TKIP Key Index:       0x20
  Reserved:             %00100
  Ext IV:               %0
  Key ID:               %00  Key ID=1

  TKIP SC:              0x00000000
  TKIP Data:
  .J.\..'>c\.0A..-  7F 4A CA 5C E2 F5 27 3E 63 5C FD 30 41 F7 AC 2D
  ...
  ...

So this data could be AES encrypted even if this sniffer claims it is TKIP/WEP?


> That weak key claim is probably valid only if WEP was used (i.e., not
> for TKIP and certainly not for CCMP). Anyway, even for WEP, there are
> more efficient ways of cracking the key than weak keys, so reporting
> weak is kind of pointless for WEP nowadays.. It is weak, no matter what
> key is used.

Strange, Kismet complais about weak keys even when the WPA-AES is selected from the AP.

-- 
Best Regards, Jar



From t.schorpp  Sun Nov  6 12:42:53 2005
From: t.schorpp (thomas schorpp)
Date: Sun, 06 Nov 2005 21:42:53 +0100
Subject: no more gtk rekeying after local deauth request
	(hostapd-wpa_supplicant)
In-Reply-To: <20051106195155.GN9194@jm.kir.nu>
References: <4312B91A.3090302@gmx.de>
	<4312EB30.8000601@kadzban.is-a-geek.net>	<4312FCEE.7080909@gmx.de>	<20050829170157.GB3449@kadzban.is-a-geek.net>	<4315D454.7070601@gmx.de>
	<43162709.7040800@gmx.de>	<20050903155058.GY7781@jm.kir.nu>
	<436AC255.3050904@gmx.de> <20051106195155.GN9194@jm.kir.nu>
Message-ID: <436E6ACD.90900@gmx.de>

Jouni Malinen wrote:
> On Fri, Nov 04, 2005 at 03:07:17AM +0100, thomas schorpp wrote:
> 
>>>On Wed, Aug 31, 2005 at 11:54:17PM +0200, thomas schorpp wrote:
>>>
>>>>strange: if a linux wpasuppl. rsn client joins the net no more group key
>>>>handshakes with this xp client with latest hostapd...?
>>>>-> maybe security issue / policy violation
> 
> 
>>-no more gtk rekeying until wpasupplicant restart.
> 
> 
>>ok. i do it next, this is a security issue. windows+mac rsn clients not
>> involved and rekeying normal with hostapd.
> 
> 
> I'm trying to remember what was the exact issue. Could you please give a
> short summary of what the problems you have seen are?
> 
> If I understood correctly, you are using madwifi+hostapd as the AP and
> have both Linux (madwifi+wpa_supplicant) and Windows/MAC clients using
> WPA2.

yes. except of one of two winxp clients using WPA1 cause belkin driver doesnt
support RSN but WPA with CCMP/AES. all in all up to 4 clients.

hostapd is configured to accept WPA1+2 but requires CCMP.

> 
> Are you saying that hostapd stops rekeying group keys when both Linux
> and Windows/MAC clients are associated, but this does not happen if
> either only the Linux client associates or only Windows/MAC clients
> associate? Or is rekeying only stopped for one of the clients and the
> other clients continue getting new group keys?
> 

mac/winxp clients rekeying goes on.

hostapd stops rekeying with wpa_supplicant after 

# EAP reauthentication period in seconds (default: 3600 seconds; 0 = disable
# reauthentication).
eap_reauth_period=3600

is fired.

last seen with only one RSN wpa_supplicant linux client on the network.

client machine then prints eap auth failure.

hostapd maintains connection and port further authorized.

it does *not* occur with both in full debugging mode.

ive set it to 0 for now.

y
tom





From asattari  Sun Nov  6 14:06:19 2005
From: asattari (asattari at site.uottawa.ca)
Date: Sun, 6 Nov 2005 17:06:19 -0500 (EST)
Subject: No subject
Message-ID: <3827.127.0.0.1.1131314779.squirrel@127.0.0.1>

hello all,
>
>I am looking for some VoIp software specialy one which is Linux based,
>free or not. can any one help me and give me his/experience in this
>matter.
>
>Thanks in advance
Afsaneh




From bryan  Sun Nov  6 14:12:52 2005
From: bryan (Bryan Kadzban)
Date: Sun, 06 Nov 2005 17:12:52 -0500
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <3047.192.168.0.154.1131309619.squirrel@kone>
References: <1793.192.168.0.150.1131277730.squirrel@kone>	<436E036C.6040402@kadzban.is-a-geek.net>
	<436E0B17.5050402@pcuf.fi>	<20051106180418.GC9194@jm.kir.nu>
	<3047.192.168.0.154.1131309619.squirrel@kone>
Message-ID: <436E7FE4.1080302@kadzban.is-a-geek.net>

Jar wrote:
> OK, I am not a specialist, but the sniffer shows the data-packet as
> below when the WPA-TKIP is selected. How the sniffer know that this
> data is WEP data?
> 
> 802.11 MAC Header
>   Version:              0
>   Type:                 %10  Data
>   Subtype:              %0000  Data Only
> Frame Control Flags:    %01000011
>                         0... .... Non-strict order
>                         .1.. .... WEP Enabled

If this bit is what's making you think it's WEP, that's not entirely
right.  This bit is set whenever the data is encrypted using any
algorithm at all (...well, at least WEP, TKIP, and AES all set it).

> 802.11 TKIP Data
>   WEP IV:               0x00201A
>   RC4Key[0]:            0x00
>   RC4Key[1]:            0x20
>   RC4Key[2]:            0x1A
> 
>   TKIP Key Index:       0x20
>   Reserved:             %00100
>   Ext IV:               %0
>   Key ID:               %00  Key ID=1
> 
>   TKIP SC:              0x00000000
>   TKIP Data:
>   ...||+.......V..  D5 04 B8 7C 7C 2B 84 1D 15 B5 0E D8 E2 56 A3 AF
>   ....
>   ....

I'm not quite sure what most of this means...

> And like this when WPA-AES is selected:
> 
> 802.11 MAC Header
>   Version:              0
>   Type:                 %10  Data
>   Subtype:              %0000  Data Only
> Frame Control Flags:    %01000011
>                         0... .... Non-strict order
>                         .1.. .... WEP Enabled

Again, this is the same bit -- it should really be called the "privacy"
bit IMO (and some packet dissectors do call it that), not the "WEP
Enabled" bit.

> 802.11 TKIP Data
>   WEP IV:               0x0C0000

That's a common CCMP IV value -- I see it fairly often when running the
Windows port of AirSnort against our CCMP network.

But again, I don't know what most of the rest of that info means.

> So this data could be AES encrypted even if this sniffer claims it is
> TKIP/WEP?

Yes -- if the sniffer was written before CCMP was standardized, it might
claim that CCMP packets were TKIP.  (Or, if it was written before TKIP,
it would claim that everything was WEP due to the privacy bit being set.
This is what AirSnort seems to do, for instance -- but I have it log to
a pcap-format file, and then pull that file up in Ethereal, which gives
better results.)

>>That weak key claim is probably valid only if WEP was used (i.e., not
>>for TKIP and certainly not for CCMP). Anyway, even for WEP, there are
>>more efficient ways of cracking the key than weak keys, so reporting
>>weak is kind of pointless for WEP nowadays.. It is weak, no matter what
>>key is used.
> 
> Strange, Kismet complais about weak keys even when the WPA-AES is
> selected from the AP.
> 

Weak keys for WEP (actually, I believe it's talking about weak IVs, not
keys, but I could be wrong there) are not weak if you use a different
encryption system.

The weakness of some IVs was due to the fact that the first bunch of
bytes out of RC4's pseudo-random number generator were not actually
pseudo-random.  RC4 is basically an XOR encryption against a
pseudo-random bitstream, so if you know the original data (e.g. an IP
header), and you have the encrypted data, it's easy to recover the
pseudo-random stream.  And if certain IVs cause a correlation between
the stream and the key bits, you can recover some of the key bits with a
decent probability (much better than brute force).

I don't know the details of the newer attacks on WEP, but this is likely
the attack that Kismet is warning you about.  But TKIP throws away the
first bunch of supposedly pseudo-random bytes before using them to XOR
anything, so even if one of these "weak" IVs is used, the non-randomness
is lost by the time all those bytes are thrown away.

And AES doesn't even involve a bitstream or XORs (its encryption changes
the output bytes depending only on the input bytes, the current counter
value (the IV), and the pairwise temporal key), so it's not vulnerable
to anything like the WEP issues.  (It may be vulnerable to other kinds
of attacks, but so far nothing of import has been found.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051106/ff899cd5/attachment.pgp 


From bryan  Sun Nov  6 14:42:43 2005
From: bryan (Bryan Kadzban)
Date: Sun, 06 Nov 2005 17:42:43 -0500
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <20051106194053.GM9194@jm.kir.nu>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>
	<20051106194053.GM9194@jm.kir.nu>
Message-ID: <436E86E3.3050606@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> This sounds like enabling/disabling WMM which uses four separate TX 
> queues.

Well, we've disabled WMM entirely, and we aren't changing that setting.
After doing some more testing, it seems that the number of replay
counters is 4 (both PTKSA and GTKSA) on an AP booted with our config.
After changing the DTIM interval from 2 to 5 on the CCMP SSID, the
number of replay counters drops to 1 (for both PTKSA and GTKSA).
Setting the DTIM interval back to 2 does not change the number of replay
counters, either.  After the next AP boot, the number of replay counters
does reset to 4.

Cisco's still working on the issue.  I suspect a bug in their firmware,
but they may say "the standard says that as long as our beacons and
probe responses are the same as our 4-way handshake IEs, we're OK".  And
they'd be perfectly OK to do so.

> wpa_supplicant should ask the driver for the IE after each
> association.

I don't know whether it does for sure or not, but I don't believe so.
I'll see if I can find out from the log (or maybe I'll just edit
driver_ndis to wpa_printf something when the IE OID is requested), and
if I find anything helpful, I'll send the info tomorrow.

> I haven't tested this, but if this is not the case, wpa_supplicant 
> should be fixed to do this. However, this is not enough, since also
> the NDIS driver has to update its BSSID list to include the latest
> WPA/RSN IE.

OK, we also run a different program that I've written, which does a list
scan on startup, then gets the scan results every second and puts them
in a grid on the screen.  (This is because these machines will be used
by people that will change anything we let them change, and most
wireless vendors' utilities allow any user to change everything -- SSID,
PSK, EAP credentials, anything.  So we wrote our own, which was pretty
much read-only.)

With all drivers that we use, the associated BSSID updates at least some
pieces of information (signal strength is what we're mostly looking at)
every second.  With some drivers, the other BSSIDs that are in range
update also.  The driver for the WMP54GS rev 1.1 card that we use for
testing *does* update the non-associated BSSIDs' signal strength.

I don't look at the IEs in this program, though.  Maybe they don't
change even though the signal strength does.  I should probably start
looking at them.

Anyway, what I'm saying is, all the drivers that we use show some kind
of update on at least one BSSID without a scan.

>> I have tried doing a "wpa_cli scan" while the supplicant is in this
>> state (to update the scan results table), but that refuses to ever
>> reconnect to the current AP, for some reason.  I believe it's an
>> issue with the NDIS driver in use (Linksys's driver for their
>> WMP54GS cards), but I don't know that for sure.
> 
> Hmm.. "wpa_cli scan" should not break association; NDIS spec requires
> that scan request can be issued at any time.. Do you mean that the 
> driver refuses to reconnect to the AP or that wpa_supplicant does not
> allow the authentication after this?

I'm not exactly sure anymore -- I know authentication was broken after
the scan, and I'm fairly sure the association was too.  Bug in Linksys's
driver?  (Though I think it happened with D-Link's latest DWL-G520 rev B
driver also.)

However, my wireless monitor program also sends an NDIS scan request
whenever one of its buttons is clicked, and that does not break the
association or prevent subsequent (re)authentications.

(I think the problem was actually ap_scan=2 interfering with some of the
code in wpa_supplicant, but I'm not sure.)

> The problem here seems to be in getting the driver to update its
> BSSID table.

Yes, I'd probably agree with that (though I do still want to look at the
logs).

> Likewise, I've seen at least some vendors improving on this area over
> time, so updating to the latest driver may also help with this.

There is only one driver for the WMP54GS rev 1.1 cards, so we've done
that already.  ;-)

> You can send longer logs directly to my email address, if needed.
> NDIS driver not updating BSSID data is not really a supplicant issue,
> so that is somewhat less interesting for me, but if the "wpa_cli
> scan" is triggering wpa_supplicant to do something incorrectly, that
> should be fixed.

OK, I'll try to reproduce that tomorrow as well, and depending on the
log, I'll send it somewhere (either here, or to your address).

>> I changed the code to zero out those replay counter bits in both
>> IEs just before it does its memcmp.  (I actually made a copy first,
>> because I'm not sure what else those pointers are used for.)
> 
> Those replay counters are not really used for anything in the 
> supplicant.

I figured they probably weren't, but I didn't know for sure.  I assume
they're something that the supplicant could use if it wanted to?

I wasn't sure what else the IEs might have been used for, though, so I
didn't want to modify them in-place.

>> Does this have any security implication?  I don't think so
>> (especially since I left the rest of the capabilities field as-is),
>> but I don't know for sure; maybe someone else here does?
> 
> Doing this kind of masking of the IEs is against the standard, but I 
> don't see it causing any security problems, so it should be fine as a
> workaround for the driver not updating BSSID data.

Hmm, OK.  I'd rather fix the issue than keep this workaround, I think.

> The APs are allowed to change WPA/RSN IE. Though, I have to admit it
> is somewhat surprising thing to do if you did not change
> configuration (disabled/enabled WMM) at that point.

Nope, we only changed the DTIM interval.  (This did reset the radio,
though, so that may possibly be related.)

> WPA/RSN IE is just used to advertise how many replay counters are 
> supported. WMM needs four (i.e., one for each TX queue).

Ah, OK, that makes sense.

> The proper fix for the issue would be to fix the NDIS driver to
> update its BSSID data to match with the latest Beacon/ProbeRsp frames
> received from the AP.

Yes, that sounds about right.  I have a few different things to look at;
I'll post back tomorrow.

Thanks a ton!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051106/a20c145b/attachment.pgp 


From jkmaline  Sun Nov  6 16:41:34 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 6 Nov 2005 16:41:34 -0800
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
Message-ID: <20051107004134.GW9194@jm.kir.nu>

I'm considering of moving from using CVS to git for Host AP / hostapd /
wpa_supplicant repository and would like to know whether someone is
depending on the current anonymous pserver access to the CVS repository.
For those who do not know git, it is the new content tracking tool used
in Linux kernel development.

My git repository would be available in the same way as the CVS
repository and there would be a web interface to the new repository, so
the main change would not be in what is being available, but just in the
protocol used to access it. I would probably leave the CVS repository
available for some time and/or make it available as a downloadable
tarball of the cvsroot directory, but all the new changes would be going
only into the git repository. Please let me know if this would cause
inconvenience.

If you are interested in seeing what the git repository looks like, the
web interface to my test repostitory is available at
http://hostap.epitest.fi/cgi-bin/gitweb.cgi and the git repository can
be cloned from http://hostap.epitest.fi/hostap.git.

-- 
Jouni Malinen                                            PGP id EFC895FA



From t.schorpp  Sun Nov  6 17:56:52 2005
From: t.schorpp (thomas schorpp)
Date: Mon, 07 Nov 2005 02:56:52 +0100
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <20051107004134.GW9194@jm.kir.nu>
References: <20051107004134.GW9194@jm.kir.nu>
Message-ID: <436EB464.9050107@gmx.de>

Jouni Malinen wrote:

> If you are interested in seeing what the git repository looks like, the
> web interface to my test repostitory is available at
> http://hostap.epitest.fi/cgi-bin/gitweb.cgi and the git repository can
> be cloned from http://hostap.epitest.fi/hostap.git.
> 

"git - the stupid content tracker" :D

why not. looks good.




From lims  Sun Nov  6 23:46:06 2005
From: lims (limor)
Date: Mon, 7 Nov 2005 09:46:06 +0200
Subject: how to cleanup a previous hostap installation
In-Reply-To: <20051106180912.GD9194@jm.kir.nu>
Message-ID: <JAEIKABDHEIDLCHFDJPGMEHJCGAA.lims@connectone.com>

Assuming my hostap_cs.conf is just a copy of the example one that is
provided with the package,
then isn't it true that applying "make clean", "make" and "make install" in
the package directory will replace those files anyway even if I don't remove
them first? I think that is what happened when I tried it (and as I
mentioned - whatever the problem in my current installation is, it did not
go away when I re-installed the package).
Are there no other files that the driver might have left somewhere when it
was still functioning well (that might cause the errors I described)? files
that are created/changed dynamically when the driver is active? something
must have changed somewhere to cause the problem and I don't suspect it's
the driver object files that were changed.. The linux is only used for 2
purposes - 1. to test WPA PSK (via wpa_supplicant) on the Prism Cf card. 2.
to sniff the wireless communication on the network with Ethereal using
monitor mode on the Prism. Any ideas?

Thanks,
Limor.


-----Original Message-----
From: hostap-bounces+lims=connectone.com at shmoo.com
[mailto:hostap-bounces+lims=connectone.com at shmoo.com]On Behalf Of Jouni
Malinen
Sent: Sunday, November 06, 2005 8:09 PM
To: hostap at shmoo.com
Subject: Re: how to cleanup a previous hostap installation


On Sun, Nov 06, 2005 at 06:07:45PM +0200, limor wrote:

> I am new to linux - are there files that I can manually delete in order to
> make sure I really start-over with the hostAP installation (before I go to
> the extreme measure of re-installing Suse)?..

Removing the installed kernel modules is probably the best way of doing
this. In addition, you can remove hostap_cs.conf. This can be done,
e.g., with following commands.

find /lib/modules/`uname -r` -name 'hostap*o' -exec rm {} \;
rm /etc/pcmcia/hostap_cs.conf

--
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap





From radu  Mon Nov  7 09:35:13 2005
From: radu (Radu Brumariu)
Date: Mon, 07 Nov 2005 12:35:13 -0500
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 , kernel
	2.6.16 (RHEL4U2)
Message-ID: <436F9051.50106@cs.kent.edu>

Hi list,

I am trying to use wpa_supplicant 0.4.6 but when I try to run it, it 
gives the following errors :

Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 
'ipw' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
update_config=1
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=10 (from group name 'wheel')
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 394 - start of a new network block
ssid - hexdump_ascii(len=2):
     43 53                                             CS
key_mgmt: 0x1
eap methods - hexdump(len=2): 19 00
proto: 0x1
group: 0x18
identity - hexdump_ascii(len=16):
     72 61 64 75 40 63 73 2e 6b 65 6e 74 2e 65 64 75   <my username>
password - hexdump_ascii(len=7): [REMOVED]
phase2 - hexdump_ascii(len=13):
     61 75 74 68 3d 4d 53 43 48 41 50 56 32            auth=MSCHAPV2
priority=10 (0xa)
Priority group 10
   id=0 ssid='CS'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_ipw_init is called
SIOCGIWRANGE: WE(compiled)=19 WE(source)=16 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:0e:35:4c:ad:b0
wpa_driver_ipw_set_wpa: enabled=1
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Failed to set encryption.
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Failed to set encryption.
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Failed to set encryption.
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Failed to set encryption.
wpa_driver_ipw_set_countermeasures: enabled=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
wpa_driver_ipw_set_drop_unencrypted: enabled=1
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
bind(PF_UNIX): Address already in use
ctrl_iface exists, but does not allow connections - assuming it was 
leftover from forced program termination
Successfully replaced leftover ctrl_iface socket 
'/var/run/wpa_supplicant/eth1'
Added interface eth1
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 4095 bytes of scan results (17 BSSes)
Scan results: 17
Selecting BSS from priority group 10
0: 00:13:1a:2a:bd:21 ssid='CS Administration' wpa_ie_len=26 
rsn_ie_len=22 caps=0x11
   skip - SSID mismatch
1: 00:13:60:0c:7c:92 ssid='CS Faculty' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
   skip - SSID mismatch
2: 00:13:60:0c:7c:91 ssid='CS Administration' wpa_ie_len=26 
rsn_ie_len=22 caps=0x11
   skip - SSID mismatch
3: 00:13:60:0c:7c:95 ssid='Math' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
   skip - SSID mismatch
4: 00:13:60:0c:7c:94 ssid='MSB Wireless' wpa_ie_len=26 rsn_ie_len=22 
caps=0x11
   skip - SSID mismatch
5: 00:13:60:0c:7b:60 ssid='CS' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
   selected based on WPA IE
Trying to associate with 00:13:60:0c:7b:60 (SSID='CS' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 1
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 
02 01 00 00 50 f2 02 01 00 00 50 f2 01 28 00
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 
0f ac 04 01 00 00 0f ac 01 28 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01
No keys have been configured - skip key clearing
wpa_driver_ipw_set_drop_unencrypted: enabled=1
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
State: SCANNING -> ASSOCIATING
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RSN: Ignored PMKID candidate without preauth flag
Wireless event: cmd=0x8b1a len=11
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_ipw_set_wpa: enabled=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
wpa_driver_ipw_set_drop_unencrypted: enabled=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
wpa_driver_ipw_set_countermeasures: enabled=0
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
No keys have been configured - skip key clearing
Cancelling scan request


I have the latest ipw2200 - 1.0.8, ieeee stack - 1.1.5, kernel 2.6.14.


Here is my /etc/wpa_supplicant.conf
update_config=1
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="CS"
        key_mgmt=WPA-EAP
        eap=PEAP
        proto=WPA
        group=CCMP TKIP
        identity="<myusername>"
        password="<mypassword>"
        #phase1="peaplabel=1"
        phase2="auth=MSCHAPV2"
        priority=10
}

I have looked in the sources for the ipw2200 and it seems that the ioctl 
command that it complains about it's declared , but I don't understand 
why it doesn't work ...

Please advice.

Regards,
Radu



From ramalhais  Mon Nov  7 09:42:05 2005
From: ramalhais (Pedro Ramalhais)
Date: Mon, 07 Nov 2005 17:42:05 +0000
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 , kernel
	2.6.16 (RHEL4U2)
In-Reply-To: <436F9051.50106@cs.kent.edu>
References: <436F9051.50106@cs.kent.edu>
Message-ID: <436F91ED.6060209@serrado.net>

Radu Brumariu wrote:
> Hi list,
> 
> I am trying to use wpa_supplicant 0.4.6 but when I try to run it, it 
> gives the following errors :
> 
> Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 
> 'ipw' ctrl_interface 'N/A'
> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant.conf'
> update_config=1
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group=10 (from group name 'wheel')
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> Line: 394 - start of a new network block
> ssid - hexdump_ascii(len=2):
>      43 53                                             CS
> key_mgmt: 0x1
> eap methods - hexdump(len=2): 19 00
> proto: 0x1
> group: 0x18
> identity - hexdump_ascii(len=16):
>      72 61 64 75 40 63 73 2e 6b 65 6e 74 2e 65 64 75   <my username>
> password - hexdump_ascii(len=7): [REMOVED]
> phase2 - hexdump_ascii(len=13):
>      61 75 74 68 3d 4d 53 43 48 41 50 56 32            auth=MSCHAPV2
> priority=10 (0xa)
> Priority group 10
>    id=0 ssid='CS'
> Initializing interface (2) 'eth1'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> wpa_driver_ipw_init is called
> SIOCGIWRANGE: WE(compiled)=19 WE(source)=16 enc_capa=0x0
>   capabilities: key_mgmt 0x0 enc 0x3
> Own MAC address: 00:0e:35:4c:ad:b0
> wpa_driver_ipw_set_wpa: enabled=1
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Failed to set encryption.
> wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Failed to set encryption.
> wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Failed to set encryption.
> wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Failed to set encryption.
> wpa_driver_ipw_set_countermeasures: enabled=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> wpa_driver_ipw_set_drop_unencrypted: enabled=1
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Setting scan request: 0 sec 100000 usec
> Using existing control interface directory.
> bind(PF_UNIX): Address already in use
> ctrl_iface exists, but does not allow connections - assuming it was 
> leftover from forced program termination
> Successfully replaced leftover ctrl_iface socket 
> '/var/run/wpa_supplicant/eth1'
> Added interface eth1
> Wireless event: cmd=0x8b06 len=8
> State: DISCONNECTED -> SCANNING
> Starting AP scan (broadcast SSID)
> Scan timeout - try to get results
> Received 4095 bytes of scan results (17 BSSes)
> Scan results: 17
> Selecting BSS from priority group 10
> 0: 00:13:1a:2a:bd:21 ssid='CS Administration' wpa_ie_len=26 
> rsn_ie_len=22 caps=0x11
>    skip - SSID mismatch
> 1: 00:13:60:0c:7c:92 ssid='CS Faculty' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
>    skip - SSID mismatch
> 2: 00:13:60:0c:7c:91 ssid='CS Administration' wpa_ie_len=26 
> rsn_ie_len=22 caps=0x11
>    skip - SSID mismatch
> 3: 00:13:60:0c:7c:95 ssid='Math' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
>    skip - SSID mismatch
> 4: 00:13:60:0c:7c:94 ssid='MSB Wireless' wpa_ie_len=26 rsn_ie_len=22 
> caps=0x11
>    skip - SSID mismatch
> 5: 00:13:60:0c:7b:60 ssid='CS' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
>    selected based on WPA IE
> Trying to associate with 00:13:60:0c:7b:60 (SSID='CS' freq=0 MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE
> Automatic auth_alg selection: 0x1
> wpa_driver_ipw_set_auth_alg: auth_alg=0x1
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> WPA: using IEEE 802.11i/D3.0
> WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 1
> WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 
> 02 01 00 00 50 f2 02 01 00 00 50 f2 01 28 00
> WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 
> 0f ac 04 01 00 00 0f ac 01 28 00
> WPA: using GTK TKIP
> WPA: using PTK TKIP
> WPA: using KEY_MGMT 802.1X
> WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 
> 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01
> No keys have been configured - skip key clearing
> wpa_driver_ipw_set_drop_unencrypted: enabled=1
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> State: SCANNING -> ASSOCIATING
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> Setting authentication timeout: 5 sec 0 usec
> EAPOL: External notification - portControl=Auto
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> Wireless event: cmd=0x8b1a len=11
> CTRL-EVENT-TERMINATING - signal 2 received
> Removing interface eth1
> State: ASSOCIATING -> DISCONNECTED
> No keys have been configured - skip key clearing
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> wpa_driver_ipw_set_wpa: enabled=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> wpa_driver_ipw_set_drop_unencrypted: enabled=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> wpa_driver_ipw_set_countermeasures: enabled=0
> ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
> No keys have been configured - skip key clearing
> Cancelling scan request
> 
> 
> I have the latest ipw2200 - 1.0.8, ieeee stack - 1.1.5, kernel 2.6.14.
> 
> 
> Here is my /etc/wpa_supplicant.conf
> update_config=1
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> network={
>         ssid="CS"
>         key_mgmt=WPA-EAP
>         eap=PEAP
>         proto=WPA
>         group=CCMP TKIP
>         identity="<myusername>"
>         password="<mypassword>"
>         #phase1="peaplabel=1"
>         phase2="auth=MSCHAPV2"
>         priority=10
> }
> 
> I have looked in the sources for the ipw2200 and it seems that the ioctl 
> command that it complains about it's declared , but I don't understand 
> why it doesn't work ...
> 
> Please advice.
> 
> Regards,
> Radu
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap


Use -Dwext instead of -Dipw

-- 
Pedro Ramalhais



From jar  Mon Nov  7 10:09:45 2005
From: jar (Jar)
Date: Mon, 07 Nov 2005 20:09:45 +0200
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <436E7FE4.1080302@kadzban.is-a-geek.net>
References: <1793.192.168.0.150.1131277730.squirrel@kone>	<436E036C.6040402@kadzban.is-a-geek.net>	<436E0B17.5050402@pcuf.fi>	<20051106180418.GC9194@jm.kir.nu>	<3047.192.168.0.154.1131309619.squirrel@kone>
	<436E7FE4.1080302@kadzban.is-a-geek.net>
Message-ID: <436F9869.1020909@pcuf.fi>

Bryan Kadzban wrote:

>>802.11 TKIP Data
>>  WEP IV:               0x00201A
>>  RC4Key[0]:            0x00
>>  RC4Key[1]:            0x20
>>  RC4Key[2]:            0x1A
>>
>>  TKIP Key Index:       0x20
>>  Reserved:             %00100
>>  Ext IV:               %0
>>  Key ID:               %00  Key ID=1
>>
>>  TKIP SC:              0x00000000
>>  TKIP Data:
>>  ...||+.......V..  D5 04 B8 7C 7C 2B 84 1D 15 B5 0E D8 E2 56 A3 AF
>>  ....
> I'm not quite sure what most of this means...

OK now I sniff iit with Kismet, the security mode is WPA_PSK_AES. The 
data packet looks like this:

No.     Time        Source                Destination           Protocol 
Info
    5655 342.729498  00:14:bf:2e:2e:2e     EdimaxTe_5a:5a:5a     IEEE 
802.11 Data

Frame 5655 (1554 bytes on wire, 1554 bytes captured)
IEEE 802.11
     Type/Subtype: Data (32)
     Frame Control: 0x4308 (Normal)
         Version: 0
         Type: Data frame (2)
         Subtype: 0
         Flags: 0x43
             DS status: Frame part of WDS (To DS: 1  From DS: 1) (0x03)
             .... .0.. = More Fragments: This is the last fragment
             .... 0... = Retry: Frame is not being retransmitted
             ...0 .... = PWR MGT: STA will stay up
             ..0. .... = More Data: No data buffered
             .1.. .... = WEP flag: WEP is enabled
             0... .... = Order flag: Not strictly ordered
     Duration: 213
     Receiver address: 00:14:bf:48:48:48 (00:14:bf:48:48:48)
     Transmitter address: 00:14:bf:bf:bf:bf (00:14:bf:bf:bf:bf)
     Destination address: 00:50:fc:5a:5a:5a (EdimaxTe_5a:5a:5a)
     Fragment number: 0
     Sequence number: 769
     Source address: 00:14:bf:2e:2e:2e (00:14:bf:2e:2e:2e)
     TKIP/CCMP parameters
         CCMP Ext. Initialization Vector: 0x0000000000DA
         Key: 0
Data (1516 bytes)

0000  af e0 27 6b be 48 34 ba 61 10 7e 20 71 dd 56 f6   ..'k.H4.a.~ q.V.
0010  33 ef 6d 67 64 fe 40 7a 88 88 0e da 94 c5 d2 0f   3.mgd. at z........
....
....

There is now mention about "CCMP Ext. Initialization Vector", so assume 
this is indeed AES encrypted.

But still Kismet complains about weak keys:

Network 3: "TEST" BSSID: "00:14:bf:2e:2e:2e"
     Type       : infrastructure
     Carrier    : unknown
     Info       : "None"
     Channel    : 13
     Encryption : "WEP TKIP WPA AES-CCM "
     Maxrate    : 11.0
     LLC        : 1888
     Data       : 67173
     Crypt      : 67151
     Weak       : 19
     Dupe IV    : 26294
     Total      : 69061
     First      : "Mon Nov  7 19:08:43 2005"
     Last       : "Mon Nov  7 20:03:09 2005"
     Min Loc: Lat 90.000000 Lon 180.000000 Alt 0.000000 Spd 0.000000
     Max Loc: Lat -90.000000 Lon -180.000000 Alt 0.000000 Spd 0.000000

Data       : 67173
Crypt      : 67151
Weak       : 19
Dupe IV    : 26294

Data packets 67173 and crypted packet 67151 => 67173-67151=22. Does this 
mean that there has been 22 unencrypted packets? Encryption is CCMP and 
still 19 weak keys?

What are Dupe IVs ? Is this serious?

-- 
Best Regards, Jar



From radu  Mon Nov  7 11:19:26 2005
From: radu (Radu Brumariu)
Date: Mon, 07 Nov 2005 14:19:26 -0500
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 , kernel
	2.6.16 (RHEL4U2)
In-Reply-To: <436F91ED.6060209@serrado.net>
References: <436F9051.50106@cs.kent.edu> <436F91ED.6060209@serrado.net>
Message-ID: <436FA8BE.4020808@cs.kent.edu>

Thank you very much, that worked.
But why ? Isn't it supposed to work with the ipw driver ?

Thanks again,
Radu

>
>Use -Dwext instead of -Dipw
>
>  
>




From jar  Mon Nov  7 11:29:34 2005
From: jar (Jar)
Date: Mon, 07 Nov 2005 21:29:34 +0200
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <436F9869.1020909@pcuf.fi>
References: <1793.192.168.0.150.1131277730.squirrel@kone>	<436E036C.6040402@kadzban.is-a-geek.net>	<436E0B17.5050402@pcuf.fi>	<20051106180418.GC9194@jm.kir.nu>	<3047.192.168.0.154.1131309619.squirrel@kone>	<436E7FE4.1080302@kadzban.is-a-geek.net>
	<436F9869.1020909@pcuf.fi>
Message-ID: <436FAB1E.5070008@pcuf.fi>

Jar wrote:
> OK now I sniff iit with Kismet, the security mode is WPA_PSK_AES. The 
> data packet looks like this:
> 
> No.     Time        Source                Destination           Protocol 
> Info
>     5655 342.729498  00:14:bf:2e:2e:2e     EdimaxTe_5a:5a:5a     IEEE 
> 802.11 Data
> 
> Frame 5655 (1554 bytes on wire, 1554 bytes captured)
> IEEE 802.11
>      Type/Subtype: Data (32)
>      Frame Control: 0x4308 (Normal)
>          Version: 0
>          Type: Data frame (2)
>          Subtype: 0
>          Flags: 0x43
>              DS status: Frame part of WDS (To DS: 1  From DS: 1) (0x03)
>              .... .0.. = More Fragments: This is the last fragment
>              .... 0... = Retry: Frame is not being retransmitted
>              ...0 .... = PWR MGT: STA will stay up
>              ..0. .... = More Data: No data buffered
>              .1.. .... = WEP flag: WEP is enabled
>              0... .... = Order flag: Not strictly ordered
>      Duration: 213
>      Receiver address: 00:14:bf:48:48:48 (00:14:bf:48:48:48)
>      Transmitter address: 00:14:bf:bf:bf:bf (00:14:bf:bf:bf:bf)
>      Destination address: 00:50:fc:5a:5a:5a (EdimaxTe_5a:5a:5a)
>      Fragment number: 0
>      Sequence number: 769
>      Source address: 00:14:bf:2e:2e:2e (00:14:bf:2e:2e:2e)
>      TKIP/CCMP parameters
>          CCMP Ext. Initialization Vector: 0x0000000000DA
>          Key: 0
> Data (1516 bytes)
> 
> 0000  af e0 27 6b be 48 34 ba 61 10 7e 20 71 dd 56 f6   ..'k.H4.a.~ q.V.
> 0010  33 ef 6d 67 64 fe 40 7a 88 88 0e da 94 c5 d2 0f   3.mgd. at z........
> ....

But sometimes data packets show both CCMP and TKIP and sometimes just 
CCMP. I don't know what it means?

     TKIP/CCMP parameters
         TKIP Ext. Initialization Vector: 0x00000000D100
         CCMP Ext. Initialization Vector: 0x00000000ACD1
         Key: 0
Data (1516 bytes)
0000  54 36 bd ae e1 d3 b6 68 9b 3c 11 41 3b f6 6b a9   T6.....h.<.A;.k.
...
...

-- 
Best Regards, Jar



From ramalhais  Mon Nov  7 16:03:25 2005
From: ramalhais (Pedro Ramalhais)
Date: Tue, 08 Nov 2005 00:03:25 +0000
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 , kernel
	2.6.16 (RHEL4U2)
In-Reply-To: <436FA8BE.4020808@cs.kent.edu>
References: <436F9051.50106@cs.kent.edu> <436F91ED.6060209@serrado.net>
	<436FA8BE.4020808@cs.kent.edu>
Message-ID: <436FEB4D.1000100@serrado.net>

Radu Brumariu wrote:
> Thank you very much, that worked.
> But why ? Isn't it supposed to work with the ipw driver ?
> 
> Thanks again,
> Radu
> 
>>
>> Use -Dwext instead of -Dipw
>>
>>  
>>
> 

The ipw drivers support the kernel wireless interface for WPA if the
kernel has wireless extensions version 18. Kernels since 2.6.13 have
version 18, so when you compile against these kernels, it will enable
the kernel interface and disable the "old" ipw specific interface.

-- 
Pedro Ramalhais



From jkmaline  Mon Nov  7 18:59:44 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 7 Nov 2005 18:59:44 -0800
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <436FAB1E.5070008@pcuf.fi>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
	<436E036C.6040402@kadzban.is-a-geek.net>
	<436E0B17.5050402@pcuf.fi> <20051106180418.GC9194@jm.kir.nu>
	<3047.192.168.0.154.1131309619.squirrel@kone>
	<436E7FE4.1080302@kadzban.is-a-geek.net>
	<436F9869.1020909@pcuf.fi> <436FAB1E.5070008@pcuf.fi>
Message-ID: <20051108025944.GA9072@jm.kir.nu>

On Mon, Nov 07, 2005 at 09:29:34PM +0200, Jar wrote:

> But sometimes data packets show both CCMP and TKIP and sometimes just 
> CCMP. I don't know what it means?

It means that the sniffer did not have enough information to determine
whether the frame was using TKIP or CCMP. I don't know what you are
trying to do, but it is just not feasible to determine whether any
single frame is encrypted with TKIP or CCMP. If you need this
information, you will need to do stateful inspection of the WPA
handshake to figure out what kind of encryption was configured.

As far as weak IVs are concerned, the tool you are using is probably
just not clever enough to realize that they do not apply to TKIP or
CCMP. Duplicate IVs could be layer two retransmissions of the same
packet.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Mon Nov  7 19:29:17 2005
From: bryan (Bryan Kadzban)
Date: Mon, 07 Nov 2005 22:29:17 -0500
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <436E86E3.3050606@kadzban.is-a-geek.net>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>	<20051106194053.GM9194@jm.kir.nu>
	<436E86E3.3050606@kadzban.is-a-geek.net>
Message-ID: <43701B8D.4040609@kadzban.is-a-geek.net>

Bryan Kadzban wrote:
> Jouni Malinen wrote:
>> wpa_supplicant should ask the driver for the IE after each 
>> association.
> 
> I don't know whether it does for sure or not, but I don't believe so.
> I'll see if I can find out from the log (or maybe I'll just edit 
> driver_ndis to wpa_printf something when the IE OID is requested),
> and if I find anything helpful, I'll send the info tomorrow.

OK -- after looking at driver_ndis.c a bit more, it looks like it
doesn't actually report the beacon IEs on an association-info event.
When the driver associates, it generates an NDIS media-connect event,
which ends up calling into wpa_driver_ndis_event_connect (assuming
ndis_events is running).

That function calls wpa_driver_ndis_get_associnfo, which is supposed to
report the various IEs back to the rest of the code.  But that function
only does a get_oid on OID_802_11_ASSOCIATION_INFORMATION, which does
not include the beacon or probe response IEs.  (That information is
available from OID_802_11_BSSID_LIST, though it may not be the most
recent scan.)  It zeroes out the wpa_event_data union, then sets its
assoc_info.req_ies and assoc_info.resp_ies (and the corresponding
lengths), but it never does anything with the assoc_info.beacon_ies.

I added code to request OID_802_11_BSSID_LIST, then iterate through the
results looking for a result that has a BSSID matching drv->bssid.  When
I find the first one, I check its ->IELength and make sure that's bigger
than the size of the NDIS_802_11_FIXED_IEs structure.  Then I set
assoc_info.beacon_ies to ->IEs + sizeof(NDIS_802_11_FIXED_IEs), and I
set assoc_info.beacon_ies_len to ->IELength - sizeof(that-structure).

Then I call wpa_supplicant_event(..., EVENT_ASSOCINFO, ...);.

This works fine -- the WMP54GS driver does update its BSSID list soon
enough after an association that we've never gotten the old IEs.

I would send a patch, but since I made the changes while at work, I'm
not entirely sure who owns them.  If you can't reimplement the changes
based on this description, let me know and I'll see if I can get them to
release it under a dual-BSD-GPL license, to match wpa_supplicant.

>> Hmm.. "wpa_cli scan" should not break association; NDIS spec
>> requires that scan request can be issued at any time.. Do you mean
>> that the driver refuses to reconnect to the AP or that
>> wpa_supplicant does not allow the authentication after this?
> 
> I'm not exactly sure anymore -- I know authentication was broken
> after the scan, and I'm fairly sure the association was too.  Bug in
> Linksys's driver?  (Though I think it happened with D-Link's latest
> DWL-G520 rev B driver also.)

Yes, it looks like the problem was ap_scan=2.  I've looked at the log
again, and the problem is almost assuredly due to driver_ndis.c (yes,
this issue too).  I've attached a gzipped log.

When wpa_supplicant.c calls wpa_drv_scan, that ends up calling into
wpa_driver_ndis_scan.  That function checks drv->radio_enabled, and if
that flag isn't set, it calls wpa_driver_ndis_disconnect (which sets the
current SSID to a 32-byte random value).

When wpa_supplicant is configured in ap_scan=2 mode and using the NDIS
driver, wpa_driver_ndis_scan never gets called on startup.  Instead, the
code just associates with the first SSID in the config file.  (In
ap_scan=1 mode, wpa_supplicant does indeed call wpa_drv_scan during its
startup.)  So when the control interface requests a scan, radio_enabled
is 0, because the driver was never told to scan the first time around.

So the first control interface scan ends up setting the SSID to a random
string.  (In the log, this is the point where it says "NDIS: turning
radio on before the first scan", line 549.)  This is what breaks the
association, and I'm pretty sure it's also what causes all the failures
later.

One possible fix might be to find somewhere else in driver_ndis.c to set
drv->radio_enabled, so that it gets set no matter what the ap_scan mode
is.  I haven't tried this, but I'm guessing it'd work.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log-scan.txt.gz
Type: application/gzip
Size: 7956 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051107/201e78e3/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051107/201e78e3/attachment.pgp 


From jar  Mon Nov  7 23:29:03 2005
From: jar (Jar)
Date: Tue, 8 Nov 2005 09:29:03 +0200 (EET)
Subject: [Off topic] Difference between wpa: tkip & aes
In-Reply-To: <20051108025944.GA9072@jm.kir.nu>
References: <1793.192.168.0.150.1131277730.squirrel@kone>
	<436E036C.6040402@kadzban.is-a-geek.net> <436E0B17.5050402@pcuf.fi>
	<20051106180418.GC9194@jm.kir.nu>
	<3047.192.168.0.154.1131309619.squirrel@kone>
	<436E7FE4.1080302@kadzban.is-a-geek.net> <436F9869.1020909@pcuf.fi>
	<436FAB1E.5070008@pcuf.fi> <20051108025944.GA9072@jm.kir.nu>
Message-ID: <37990.194.157.0.2.1131434943.squirrel@netlandzone.dyndns.org>


> Jouni Malinen wrote:
>
> I don't know what you are trying to do, but it is just not feasible to determine
> whether any single frame is encrypted with TKIP or CCMP.

Actually I have been wondering how to verify the encryption, not just trust the
selected encryption method. Unfotunally this seems not to be trivial job to do for
ordinary person. I understand this now. And the sniffing tools have weaknesses too,
you can't 100% trust them.

Thanks to Bryan and Jouni for the answers.

-- 
Best Regards, Jar



From miernik  Tue Nov  8 00:47:14 2005
From: miernik (Miernik)
Date: Tue, 8 Nov 2005 09:47:14 +0100 (CET)
Subject: WPA doesn't work - Authentication with 00:00:00:00:00:00 timed out.
Message-ID: <21152.80.50.88.10.1131439634.squirrel@www.ffii.org>

I have a problem trying to connect to an access point with WPA-PSK/CCMP
using with a Prism2.5 card, hostap 0.4.5 driver, 2.4.30 kernel with
Wireless Extensions v18 patch (default is v16 in 2.4.30, but that doesn't
support WPA). Version of wpa_supplicant is 0.4.5 (I am not exactly sure
now, it might have been 0.4.6, anyway something recent).

Here is the output of wpa_supplicant:

root at OpenWrt:/# wpa_supplicant -c /etc/wpa_supplicant.conf -D hostap -i
wlan0 -dd -t -K
Jan 01 00:04:44.809490: Initializing interface 'wlan0' conf
'/etc/wpa_supplicant.conf' driver 'hostap'
Jan 01 00:04:44.812942: Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Jan 01 00:04:44.814693: Reading configuration file '/etc/wpa_supplicant.conf'
Jan 01 00:04:44.817075: ctrl_interface='/var/run/wpa_supplicant'
Jan 01 00:04:44.818686: Line: 5 - start of a new network block
Jan 01 00:04:44.820488: ssid - hexdump_ascii(len=8):
     65 68 65 6c 70 2e 70 6c                           ehelp.pl
Jan 01 00:04:44.823935: key_mgmt: 0x2
Jan 01 00:04:44.825637: pairwise: 0x10
Jan 01 00:04:44.827234: group: 0x10
Jan 01 00:04:44.828830: PSK (ASCII passphrase) - hexdump_ascii(len=10):
     11 11 11 11 11 11 11 11 11 11                     ..........
Jan 01 00:04:47.723146: PSK (from passphrase) - hexdump(len=32): 11 11 11
11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
11 11 11 11
Jan 01 00:04:47.725849: Priority group 0
Jan 01 00:04:47.727518:    id=0 ssid='ehelp.pl'
Jan 01 00:04:47.729159: Initializing interface (2) 'wlan0'
Jan 01 00:04:48.665523: EAPOL: SUPP_PAE entering state DISCONNECTED
Jan 01 00:04:48.667215: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
Jan 01 00:04:48.668886: EAPOL: SUPP_BE entering state INITIALIZE
Jan 01 00:04:48.670640: EAP: EAP entering state DISABLED
Jan 01 00:04:48.672924: EAPOL: External notification - portEnabled=0
Jan 01 00:04:48.674800: EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: Operation not supported
Jan 01 00:04:48.683502: SIOCGIWRANGE: WE(compiled)=18 WE(source)=18
enc_capa=0xf
Jan 01 00:04:48.685114:   capabilities: key_mgmt 0xf enc 0xf
Jan 01 00:04:48.687493: Own MAC address: 00:02:6f:33:b9:f3
Jan 01 00:04:48.689144: wpa_driver_hostap_set_wpa: enabled=1
Jan 01 00:04:48.717601: wpa_driver_hostap_set_key: alg=none key_idx=0
set_tx=0 seq_len=0 key_len=0
Jan 01 00:04:48.719577: wpa_driver_hostap_set_key: alg=none key_idx=1
set_tx=0 seq_len=0 key_len=0
Jan 01 00:04:48.721646: wpa_driver_hostap_set_key: alg=none key_idx=2
set_tx=0 seq_len=0 key_len=0
Jan 01 00:04:48.723617: wpa_driver_hostap_set_key: alg=none key_idx=3
set_tx=0 seq_len=0 key_len=0
Jan 01 00:04:48.725569: wpa_driver_hostap_set_countermeasures: enabled=0
Jan 01 00:04:48.727232: wpa_driver_hostap_set_drop_unencrypted: enabled=1
Jan 01 00:04:48.729154: Setting scan request: 0 sec 100000 usec
Jan 01 00:04:48.733220: Wireless event: cmd=0x8b06 len=8
Jan 01 00:04:48.840248: State: DISCONNECTED -> SCANNING
Jan 01 00:04:48.841828: Starting AP scan (broadcast SSID)
Jan 01 00:04:49.585271: Wireless event: cmd=0x8b19 len=12
Jan 01 00:04:49.589382: Received 484 bytes of scan results (5 BSSes)
Jan 01 00:04:49.591063: Scan results: 5
Jan 01 00:04:49.591550: Selecting BSS from priority group 0
Jan 01 00:04:49.591996: 0: 00:0f:66:c8:8b:17 ssid='ehelp.pl' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
Jan 01 00:04:49.592730:    selected
Jan 01 00:04:49.593348: Trying to associate with 00:0f:66:c8:8b:17
(SSID='ehelp.pl' freq=2442 MHz)
Jan 01 00:04:49.593868: Cancelling scan request
Jan 01 00:04:49.594303: WPA: clearing own WPA/RSN IE
Jan 01 00:04:49.594827: Automatic auth_alg selection: 0x1
Jan 01 00:04:49.596800: WPA: using IEEE 802.11i/D3.0
Jan 01 00:04:49.597304: WPA: Selected cipher suites: group 16 pairwise 16
key_mgmt 2
Jan 01 00:04:49.597793: WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50
f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
Jan 01 00:04:49.598913: WPA: clearing AP RSN IE
Jan 01 00:04:49.599362: WPA: using GTK CCMP
Jan 01 00:04:49.599822: WPA: using PTK CCMP
Jan 01 00:04:49.600386: WPA: using KEY_MGMT WPA-PSK
Jan 01 00:04:49.600834: WPA: Set own WPA IE default - hexdump(len=24): dd
16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
Jan 01 00:04:49.601964: No keys have been configured - skip key clearing
Jan 01 00:04:49.602386: wpa_driver_hostap_set_drop_unencrypted: enabled=1
Jan 01 00:04:49.602884: State: SCANNING -> ASSOCIATING
Jan 01 00:04:49.603342: wpa_driver_hostap_associate
Jan 01 00:04:49.682081: Setting authentication timeout: 5 sec 0 usec
Jan 01 00:04:49.683711: EAPOL: External notification - EAP success=0
Jan 01 00:04:49.685605: EAPOL: External notification - EAP fail=0
Jan 01 00:04:49.687518: EAPOL: External notification - portControl=Auto
Jan 01 00:04:49.689943: Wireless event: cmd=0x8b06 len=8
Jan 01 00:04:49.691839: Wireless event: cmd=0x8b04 len=12
Jan 01 00:04:49.693635: Wireless event: cmd=0x8b1a len=21
Jan 01 00:04:54.690322: Authentication with 00:00:00:00:00:00 timed out.
Jan 01 00:04:54.691934: Added BSSID 00:00:00:00:00:00 into blacklist
Jan 01 00:04:54.693598: State: ASSOCIATING -> DISCONNECTED
Jan 01 00:04:54.695183: No keys have been configured - skip key clearing
Jan 01 00:04:54.696748: EAPOL: External notification - portEnabled=0
Jan 01 00:04:54.698641: EAPOL: External notification - portValid=0
Jan 01 00:04:54.700756: Setting scan request: 0 sec 0 usec
Jan 01 00:04:54.702447: State: DISCONNECTED -> SCANNING
Jan 01 00:04:54.704027: Starting AP scan (broadcast SSID)
Jan 01 00:04:55.353133: Wireless event: cmd=0x8b19 len=12
Jan 01 00:04:55.356399: Received 869 bytes of scan results (10 BSSes)
Jan 01 00:04:55.358006: Scan results: 10
Jan 01 00:04:55.359589: Selecting BSS from priority group 0
Jan 01 00:04:55.361261: 0: 00:12:17:e7:7a:cc ssid='ehelp.pl' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
Jan 01 00:04:55.363036:    selected
Jan 01 00:04:55.364817: Trying to associate with 00:12:17:e7:7a:cc
(SSID='ehelp.pl' freq=2412 MHz)
Jan 01 00:04:55.366488: Cancelling scan request
Jan 01 00:04:55.368052: WPA: clearing own WPA/RSN IE
Jan 01 00:04:55.369610: Automatic auth_alg selection: 0x1
Jan 01 00:04:55.371609: WPA: using IEEE 802.11i/D3.0
Jan 01 00:04:55.373202: WPA: Selected cipher suites: group 16 pairwise 16
key_mgmt 2
Jan 01 00:04:55.374858: WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50
f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
Jan 01 00:04:55.377138: WPA: clearing AP RSN IE
Jan 01 00:04:55.378754: WPA: using GTK CCMP
Jan 01 00:04:55.380451: WPA: using PTK CCMP
Jan 01 00:04:55.382066: WPA: using KEY_MGMT WPA-PSK
Jan 01 00:04:55.383649: WPA: Set own WPA IE default - hexdump(len=24): dd
16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
Jan 01 00:04:55.385952: No keys have been configured - skip key clearing
Jan 01 00:04:55.387168: wpa_driver_hostap_set_drop_unencrypted: enabled=1
Jan 01 00:04:55.389193: State: SCANNING -> ASSOCIATING
Jan 01 00:04:55.390884: wpa_driver_hostap_associate
Jan 01 00:04:55.469040: Setting authentication timeout: 5 sec 0 usec
Jan 01 00:04:55.470739: EAPOL: External notification - EAP success=0
Jan 01 00:04:55.472646: EAPOL: External notification - EAP fail=0
Jan 01 00:04:55.474538: EAPOL: External notification - portControl=Auto
Jan 01 00:04:55.476662: Wireless event: cmd=0x8b06 len=8
Jan 01 00:04:55.478438: Wireless event: cmd=0x8b04 len=12
Jan 01 00:04:55.480349: Wireless event: cmd=0x8b1a len=21
Jan 01 00:05:00.480314: Authentication with 00:00:00:00:00:00 timed out.
Jan 01 00:05:00.481920: BSSID 00:00:00:00:00:00 blacklist count
incremented to 2
Jan 01 00:05:00.483602: State: ASSOCIATING -> DISCONNECTED
Jan 01 00:05:00.485187: No keys have been configured - skip key clearing



Here is my /etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant

network={
        ssid="ehelp.pl"
        key_mgmt=WPA-PSK
#        proto=WPA
        pairwise=CCMP
        group=CCMP
        psk="........."
}

dmesg output:

hostap_crypt: registered algorithm 'NULL'
hostap_pci: 0.4.5 - 2005-09-25 (Jouni Malinen <jkmaline at cc.hut.fi>)
PCI: Enabling device 01:02.0 (0000 -> 0002)
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
prism2_hw_init: initialized in 190 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: Intersil Prism2.5 PCI: mem=0x40002000, irq=6
wifi0: registered netdevice wlan0
hostap_crypt: registered algorithm 'CCMP'
prism2: wlan0: operating mode changed 3 -> 2
wlan0: Preferred AP (SIOCSIWAP) is used only in Managed mode when
host_roaming is enabled
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: no scan results for host roaming
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wlan0: Trying to join BSSID 00:0f:66:c8:8b:17
wifi0: LinkStatus=6 (Association failed)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: no scan results for host roaming
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wlan0: Trying to join BSSID 00:12:17:e7:7a:cc
wifi0: LinkStatus=6 (Association failed)


root at OpenWrt:/# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:0F:66:C8:8B:17
                    ESSID:"ehelp.pl"
                    Mode:Master
                    Frequency:2.442 GHz (Channel 7)
                    Encryption key:on
                    (Unknown Wireless Token 0x8C05)
          Cell 02 - Address: 00:12:17:E7:7A:CC
                    ESSID:"ehelp.pl"
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    (Unknown Wireless Token 0x8C05)


The card is Senao miniPCI SL-2511MP PLUS 2.10

It has a sticker:
S/N: 044377522
NL-2511MP PLUS(ETSI)
MAC: 00026F33B9F3

What might be the problem? Please help.

-- 
FFII





From maccari-thisaintpartofmyaddress-  Tue Nov  8 02:39:39 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Tue, 8 Nov 2005 11:39:39 +0100
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <436EB464.9050107@gmx.de>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
Message-ID: <20051108103939.GC4458@lenst.det.unifi.it>

On Mon, Nov 07, 2005 at 02:56:52AM +0100, thomas schorpp wrote:
> Jouni Malinen wrote:
> 
> > If you are interested in seeing what the git repository looks like, the
> > web interface to my test repostitory is available at
> > http://hostap.epitest.fi/cgi-bin/gitweb.cgi and the git repository can
> > be cloned from http://hostap.epitest.fi/hostap.git.
> > 
> 
> "git - the stupid content tracker" :D

link to an overview of git:
http://linux.yyz.us/git-howto.html

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 




From radu  Tue Nov  8 06:41:16 2005
From: radu (Radu Brumariu)
Date: Tue, 08 Nov 2005 09:41:16 -0500
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 , kernel
	2.6.16 (RHEL4U2)
In-Reply-To: <436FEB4D.1000100@serrado.net>
References: <436F9051.50106@cs.kent.edu> <436F91ED.6060209@serrado.net>
	<436FA8BE.4020808@cs.kent.edu> <436FEB4D.1000100@serrado.net>
Message-ID: <4370B90C.5010900@cs.kent.edu>

Pedro Ramalhais wrote:

>Radu Brumariu wrote:
>  
>
>>Thank you very much, that worked.
>>But why ? Isn't it supposed to work with the ipw driver ?
>>
>>Thanks again,
>>Radu
>>
>>    
>>
>>>Use -Dwext instead of -Dipw
>>>
>>> 
>>>
>>>      
>>>
>
>The ipw drivers support the kernel wireless interface for WPA if the
>kernel has wireless extensions version 18. Kernels since 2.6.13 have
>version 18, so when you compile against these kernels, it will enable
>the kernel interface and disable the "old" ipw specific interface.
>
>  
>
Ok, so if I understand this right, after the 2.6.13, no matter what 
wireless board I have, as long as I compile the drivers for the board 
and the wext module I should use the wext.
What is the lowest version of ipw for which the wpa_supplicant will 
work, given that I have a kernel lower than 2.6.13 ?

Regards,
Radu



From ramalhais  Tue Nov  8 07:34:15 2005
From: ramalhais (Pedro Ramalhais)
Date: Tue, 08 Nov 2005 15:34:15 +0000
Subject: wpa_supplicant 0.4.6 + ipw2200 1.0.8 , ieee80211 - 1.1.15 ,
	kernel 2.6.16 (RHEL4U2)
In-Reply-To: <4370B90C.5010900@cs.kent.edu>
References: <436F9051.50106@cs.kent.edu> <436F91ED.6060209@serrado.net>
	<436FA8BE.4020808@cs.kent.edu> <436FEB4D.1000100@serrado.net>
	<4370B90C.5010900@cs.kent.edu>
Message-ID: <1131464055.30117.53.camel@gandalf.uninova.pt>

On Tue, 2005-11-08 at 09:41 -0500, Radu Brumariu wrote:
> Pedro Ramalhais wrote:
> 
> >Radu Brumariu wrote:
> >  
> >
> >>Thank you very much, that worked.
> >>But why ? Isn't it supposed to work with the ipw driver ?
> >>
> >>Thanks again,
> >>Radu
> >>
> >>    
> >>
> >>>Use -Dwext instead of -Dipw
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >
> >The ipw drivers support the kernel wireless interface for WPA if the
> >kernel has wireless extensions version 18. Kernels since 2.6.13 have
> >version 18, so when you compile against these kernels, it will enable
> >the kernel interface and disable the "old" ipw specific interface.
> >
> >  
> >
> Ok, so if I understand this right, after the 2.6.13, no matter what 
> wireless board I have, as long as I compile the drivers for the board 
> and the wext module I should use the wext.
> What is the lowest version of ipw for which the wpa_supplicant will 
> work, given that I have a kernel lower than 2.6.13 ?
> 
> Regards,
> Radu

I think you didn't understand what i said. Maybe i didn't explain myself
very well.
The ipw drivers choose to disable the "old" driver specific interface in
the presence of a kernel which supports WPA features (WE18 are present
on kernels >= 2.4.13). If you use older kernels to compile the driver,
it will include the ipw interface, else it will include the kernel
interface.
Hope this clarifies it.

Regards,
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From theetjuh  Tue Nov  8 12:23:42 2005
From: theetjuh (Theetjuh)
Date: Tue, 8 Nov 2005 21:23:42 +0100
Subject: DHCP failing with -Dwext and kernel 2.6.14
In-Reply-To: <1e4a094e0511030101x434d4060sf3eb40f9c71ca106@mail.gmail.com>
References: <1e4a094e0511030101x434d4060sf3eb40f9c71ca106@mail.gmail.com>
Message-ID: <1e4a094e0511081223n3e4100c2ta278720f23160b0c@mail.gmail.com>

Hi,


I've got a new laptop, ipw2200 instead of an atheros card, but using the
same ap's.

slackware 10.2 - kernel 2.6.14
ieee80211 1.1.6
ipw2200 1.0.8
ipw2200-fw 2.4
wpa_supplicant 0.4.6

I'm using wpa-psk with the same router as before, so i copied the
wpa_supplicant.conf , authentication succees, but dhcp doesn't work, setting
a static ip works.

Disabled the encryption on the router, no wpa_supplicant .... good to go !!

I've tried a few different drivers and kernels, but no go :(

wpa_cli :
<2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Authentication with 00:00:00:00:00:00 timed out.
<2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
<2>Associated with rr:oo:uu:tt:ee:rr
<2>WPA: Key negotiation completed with rr:oo:uu:tt:ee:rr [PTK=CCMP GTK=TKIP]
<2>CTRL-EVENT-CONNECTED - Connection to rr:oo:uu:tt:ee:rr completed (auth)

wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -ieth0 -dd :
ioctl[SIOCSIWPMKSA]: Operation not supported
l2_packet_receive - recvfrom: Network is down

Do you guys have any suggestions ?


--


Greetz
Theetjuh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/90b76998/attachment.htm 


From swong  Tue Nov  8 14:19:13 2005
From: swong (Simon Wong)
Date: Tue, 08 Nov 2005 14:19:13 -0800
Subject: WPA-PSK with madwifi with hostapd not working
Message-ID: <43712461.9040802@changind.com>

Hi,

I'm trying to get WPA-PSK with TKIP to work on my system, set up as an 
access point. I'm using the latest stable version of hostapd, and a 
relatively recent version of madwifi. I'm trying to use a winxp machine 
to attach to this system. It seems like the client authenticated but the 
key couldn't be added to the system. Any ideas on what might be wrong?

Here is the conf file:
interface=ath1
ssid=RTK_AP36
wpa=1
driver=madwifi
wpa_passphrase=********
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
wpa_group_rekey=600
wpa_gmk_rekey=86400
debug=1

Here is part of the dump:
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state AUTHENTICATION
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state INITPSK
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
ath1: STA 00:0d:88:9c:e3:f6 WPA: EAPOL-Key timeout
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state PTKSTART
ath1: STA 00:0d:88:9c:e3:f6 WPA: sending 1/4 msg of 4-Way Handshake
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state DISCONNECT
madwifi_sta_deauth: addr=00:0d:88:9c:e3:f6 reason_code=2
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state DISCONNECTED
WPA: 00:0d:88:9c:e3:f6 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0d:88:9c:e3:f6 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: No such file or directory
ath1: STA 00:0d:88:9c:e3:f6 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0d:88:9c:e3:f6 authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: No such file or directory
ath1: STA 00:0d:88:9c:e3:f6 IEEE 802.11: deauthenticated due to local 
deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0d:88:9c:e3:f6
rx_packets=6
tx_packets=4
rx_bytes=586
tx_bytes=428

-- 
Simon Wong




From ramalhais  Tue Nov  8 14:28:42 2005
From: ramalhais (Pedro Ramalhais)
Date: Tue, 08 Nov 2005 22:28:42 +0000
Subject: DHCP failing with -Dwext and kernel 2.6.14
In-Reply-To: <1e4a094e0511081223n3e4100c2ta278720f23160b0c@mail.gmail.com>
References: <1e4a094e0511030101x434d4060sf3eb40f9c71ca106@mail.gmail.com>
	<1e4a094e0511081223n3e4100c2ta278720f23160b0c@mail.gmail.com>
Message-ID: <4371269A.4010604@serrado.net>

Theetjuh wrote:
> Hi,
> 
> 
> I've got a new laptop, ipw2200 instead of an atheros card, but using the
> same ap's.
> 
> slackware 10.2 - kernel 2.6.14
> ieee80211 1.1.6
> ipw2200 1.0.8
> ipw2200-fw 2.4
> wpa_supplicant 0.4.6
> 
> I'm using wpa-psk with the same router as before, so i copied the
> wpa_supplicant.conf , authentication succees, but dhcp doesn't work,
> setting a static ip works.
> 
> Disabled the encryption on the router, no wpa_supplicant .... good to go !!
> 
> I've tried a few different drivers and kernels, but no go :(
> 
> wpa_cli :
> <2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
> <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
> <2>Associated with rr:oo:uu:tt:ee:rr
> <2>WPA: Key negotiation completed with rr:oo:uu:tt:ee:rr [PTK=CCMP GTK=TKIP]
> <2>CTRL-EVENT-CONNECTED - Connection to rr:oo:uu:tt:ee:rr completed (auth)
> 
> wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -ieth0 -dd :
> ioctl[SIOCSIWPMKSA]: Operation not supported
> l2_packet_receive - recvfrom: Network is down
> 
> Do you guys have any suggestions ?
> 
> 
> -- 
> 
> 
> Greetz
> Theetjuh

Try the attached patch, or try loading the ipw2200 module with parameter
hwcrypto=0.
-- 
Pedro Ramalhais
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ipw2200-1.0.8-broadcast_fix.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/1b8d7d36/attachment.txt 


From bmeier  Tue Nov  8 15:42:24 2005
From: bmeier (Beat Meier)
Date: Tue, 08 Nov 2005 20:42:24 -0300
Subject: Patches to use madwifi-ng with hostapd-0.4.6 and wpa_supplicant-0.4.6
Message-ID: <437137E0.1070002@infovia.com.ar>

Jouni

New version of wireless.h don't define anymore some includes.
Changes of drivers like madwifi will affect always hostapd, wpa_supplicant
because of changes of wireless packages.
Why was wireless_copy.h added?

Madwifi has added now iwlib.h instead of linnux/wireless.h as you stated 
before
should not be included in userspace progs because of kernel space headers.
But iwlib.h would be the right inlcude also for hostapd, wpa_supplicant?

Please let me know if anything is against this approch.
If we do so we have to change madwifi include file.

We are trying to find the way so everything works together again with 
madwifi-ng.

Here are my patch proposel.
This are all against wpa_supplicant-0.4.6 and hostapd-0.4.6

I have defined an other DEFINE for new driver so we can have old and new 
driver in parallel.
ioctl section of driver_madwifi could be changed only error case i.e. 
last entry of list but
I think do it so we have more flexibilty if old driver should change 
(but in fact should not ...)

Notes about applying:
First *_madwifi_ng.patch must be applied and if you agree to change 
wireless_copy.h for iwlib.h
apply *_iwlib_header.patch.

I have compiled with new madwifi-1314 and old bsd brach version 
madwifi-bsd-20050702.
I have not tested old version...

Please let me know as soon as possible if we can go this way so we can 
work on at madwifi
and do the changes.

The other patch is against madwifi-1314 if you want compile against 
madwifi-ng.

Greetings

Beat
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd_iwlib_header.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/f204b11b/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/f204b11b/attachment-0001.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant_iwlib_header.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/f204b11b/attachment-0002.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051108/f204b11b/attachment-0003.txt 


From theetjuh  Tue Nov  8 15:45:11 2005
From: theetjuh (Theetjuh)
Date: Wed, 9 Nov 2005 00:45:11 +0100
Subject: DHCP failing with -Dwext and kernel 2.6.14
In-Reply-To: <4371269A.4010604@serrado.net>
References: <1e4a094e0511030101x434d4060sf3eb40f9c71ca106@mail.gmail.com>
	<1e4a094e0511081223n3e4100c2ta278720f23160b0c@mail.gmail.com>
	<4371269A.4010604@serrado.net>
Message-ID: <1e4a094e0511081545n1afa6ddfx8c8a035f8f2a95bc@mail.gmail.com>

Thnx Pedro,

The hwcrypto=0 worked perfectly, the patch didn't btw

On 11/8/05, Pedro Ramalhais <ramalhais at serrado.net> wrote:
>
> Theetjuh wrote:
> > Hi,
> >
> >
> > I've got a new laptop, ipw2200 instead of an atheros card, but using the
> > same ap's.
> >
> > slackware 10.2 - kernel 2.6.14
> > ieee80211 1.1.6
> > ipw2200 1.0.8
> > ipw2200-fw 2.4
> > wpa_supplicant 0.4.6
> >
> > I'm using wpa-psk with the same router as before, so i copied the
> > wpa_supplicant.conf , authentication succees, but dhcp doesn't work,
> > setting a static ip works.
> >
> > Disabled the encryption on the router, no wpa_supplicant .... good to go
> !!
> >
> > I've tried a few different drivers and kernels, but no go :(
> >
> > wpa_cli :
> > <2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
> > <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > <2>Authentication with 00:00:00:00:00:00 timed out.
> > <2>Trying to associate with rr:oo:uu:tt:ee:rr (SSID='blabla' freq=0 MHz)
> > <2>Associated with rr:oo:uu:tt:ee:rr
> > <2>WPA: Key negotiation completed with rr:oo:uu:tt:ee:rr [PTK=CCMP
> GTK=TKIP]
> > <2>CTRL-EVENT-CONNECTED - Connection to rr:oo:uu:tt:ee:rr completed
> (auth)
> >
> > wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -ieth0 -dd :
> > ioctl[SIOCSIWPMKSA]: Operation not supported
> > l2_packet_receive - recvfrom: Network is down
> >
> > Do you guys have any suggestions ?
> >
> >
> > --
> >
> >
> > Greetz
> > Theetjuh
>
> Try the attached patch, or try loading the ipw2200 module with parameter
> hwcrypto=0.
> --
> Pedro Ramalhais
>
>
> --- ipw2200.c 2005-11-06 03:59:14.000000000 +0000
> +++ ipw2200.c.broadcast_fix 2005-11-08 22:25:16.000000000 +0000
> @@ -7982,8 +7982,8 @@ static void ipw_rebuild_decrypted_skb(st
>
> static inline int ipw_is_broadcast_ether_addr(const u8 * addr)
> {
> - return (addr[0] & 0xff && addr[1] & 0xff && addr[2] & 0xff &&
> - addr[3] & 0xff && addr[4] & 0xff && addr[5] & 0xff);
> + return ((addr[0] & addr[1] & addr[2] &
> + addr[3] & addr[4] & addr[5]) == 0xff);
> }
>
> static void ipw_handle_data_packet(struct ipw_priv *priv,
>
>
>


--


Greetz
Theetjuh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/1a7372b2/attachment.htm 


From jkmaline  Tue Nov  8 18:31:05 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 8 Nov 2005 18:31:05 -0800
Subject: Patches to use madwifi-ng with hostapd-0.4.6 and
	wpa_supplicant-0.4.6
In-Reply-To: <437137E0.1070002@infovia.com.ar>
References: <437137E0.1070002@infovia.com.ar>
Message-ID: <20051109023105.GA8986@jm.kir.nu>

On Tue, Nov 08, 2005 at 08:42:24PM -0300, Beat Meier wrote:

> New version of wireless.h don't define anymore some includes.

I don't know what you are refering to with "new version", but the latest
release, i.e., WE-19, does include linux/types.h, linux/socket.h, and
linux/if.h.

> Changes of drivers like madwifi will affect always hostapd, wpa_supplicant
> because of changes of wireless packages.

Changes of the drivers should not affect (well, assuming they would use
just Linux Wireless Extensions), but changes of WE do indeed affect user
space programs.

> Why was wireless_copy.h added?

Because linux/wireless.h cannot be included in user space programs
without major compatibility problems with libc header files. Another
reason is in being able to build one binary that supports multiple WE
versions.

> Madwifi has added now iwlib.h instead of linnux/wireless.h as you stated 
> before
> should not be included in userspace progs because of kernel space headers.
> But iwlib.h would be the right inlcude also for hostapd, wpa_supplicant?

No, the license of iwlib is not compatible with hostapd/wpa_supplicant.

> Please let me know if anything is against this approch.

I cannot accept changes to hostapd/wpa_supplicant that would make them
GPL only. I'm fine with the change that went already in into subversion,
i.e., just #ifdef __KERNEL__ around all include statements in header
files that are also linked into user space programs. I can include
whatever libc headers I want to make this work for
hostapd/wpa_supplicant and the header files are still functional for the
kernel code without any other changes.

> We are trying to find the way so everything works together again with 
> madwifi-ng.
> 
> Here are my patch proposel.
> This are all against wpa_supplicant-0.4.6 and hostapd-0.4.6

Thanks. I'll take a closer look at this, but that may have to wait till
Saturday.

> Please let me know as soon as possible if we can go this way so we can 
> work on at madwifi
> and do the changes.

What changes are needed on the driver side?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Nov  8 18:37:24 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 8 Nov 2005 18:37:24 -0800
Subject: WPA-PSK with madwifi with hostapd not working
In-Reply-To: <43712461.9040802@changind.com>
References: <43712461.9040802@changind.com>
Message-ID: <20051109023724.GB8986@jm.kir.nu>

On Tue, Nov 08, 2005 at 02:19:13PM -0800, Simon Wong wrote:

> I'm trying to get WPA-PSK with TKIP to work on my system, set up as an 
> access point. I'm using the latest stable version of hostapd, and a 
> relatively recent version of madwifi. I'm trying to use a winxp machine 
> to attach to this system. It seems like the client authenticated but the 
> key couldn't be added to the system. Any ideas on what might be wrong?

Is your ath1 interface part of a bridge device? If yes, you will need to
add bridge=<that bridge dev> to the configuration file. If this is not
enough to fix the issue, I would suggest testing hostapd v0.4.6.

-- 
Jouni Malinen                                            PGP id EFC895FA



From miernik  Tue Nov  8 21:58:59 2005
From: miernik (Miernik)
Date: Wed, 9 Nov 2005 06:58:59 +0100 (CET)
Subject: WPA doesn't work - Authentication with 00:00:00:00:00:00 timed 
	out.
In-Reply-To: <19645.80.50.88.10.1131514616.squirrel@www.ffii.org>
References: <19645.80.50.88.10.1131514616.squirrel@www.ffii.org>
Message-ID: <23815.80.50.88.10.1131515939.squirrel@www.ffii.org>

> Hello,
>
> I have a problem trying to connect to an access point with WPA-PSK/CCMP
> using with a Prism2.5 card, hostap 0.4.5 driver, 2.4.30 kernel with
> Wireless Extensions v18 patch (default is v16 in 2.4.30, but that doesn't
> support WPA). Version of wpa_supplicant is 0.4.5.

Sorry for a bit mangled log output, a better log of the problem is here:

http://forum.openwrt.org/viewtopic.php?id=3214

--
FFII
+32486233396





From bmeier  Wed Nov  9 07:13:21 2005
From: bmeier (Beat Meier)
Date: Wed, 09 Nov 2005 12:13:21 -0300
Subject: How to compile hostapd-0.4.6 and wpa_supplicant-0.4.6 for madwifi-ng
	(1314)
In-Reply-To: <20051109023105.GA8986@jm.kir.nu>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
Message-ID: <43721211.1060407@infovia.com.ar>

Jouni

If you don't want philosohic stuff read the end of the mail :-) for my 
conclusions to go for now ...

Jouni Malinen wrote:

>On Tue, Nov 08, 2005 at 08:42:24PM -0300, Beat Meier wrote:
>
>  
>
>>New version of wireless.h don't define anymore some includes.
>>    
>>
>
>I don't know what you are refering to with "new version", but the latest
>release, i.e., WE-19, does include linux/types.h, linux/socket.h, and
>linux/if.h.
>
>  
>
Release 28-pre10 does not include this anymore. Here the codefragment:

/***************************** INCLUDES *****************************/

/* Do not put any header in this file, this creates a mess when
 * exported to user space. Most users have included all the
 * relevant headers anyway... Jean II */
/*#include <linux/types.h>*/        /* for "caddr_t" et al      */
/*#include <linux/socket.h>*/       /* for "struct sockaddr" et al  */
/*#include <linux/if.h>*/       /* for IFNAMSIZ and co... */



>>Changes of drivers like madwifi will affect always hostapd, wpa_supplicant
>>because of changes of wireless packages.
>>    
>>
>
>Changes of the drivers should not affect (well, assuming they would use
>just Linux Wireless Extensions), but changes of WE do indeed affect user
>space programs.
>
>  
>
>>Why was wireless_copy.h added?
>>    
>>
>
>Because linux/wireless.h cannot be included in user space programs
>without major compatibility problems with libc header files. Another
>reason is in being able to build one binary that supports multiple WE
>versions.
>
>  
>
>>Madwifi has added now iwlib.h instead of linnux/wireless.h as you stated 
>>before
>>should not be included in userspace progs because of kernel space headers.
>>But iwlib.h would be the right inlcude also for hostapd, wpa_supplicant?
>>    
>>
>
>No, the license of iwlib is not compatible with hostapd/wpa_supplicant.
>
>  
>
Sorry. What do you mean with that?
hostapd/wpa_supplicant is dual license GPL version 2 and BSD,
iwlib.h is realeased unter GPL license.

Is this a problem because not BSD license or what do you mean?
sample_pm.c in wireless_tools is realease under LGPL, MPL or BSD license.

If this is a problem we could see with Jean or did you do that already 
some time ago?

>>Please let me know if anything is against this approch.
>>    
>>
>
>I cannot accept changes to hostapd/wpa_supplicant that would make them
>GPL only. I'm fine with the change that went already in into subversion,
>i.e., just #ifdef __KERNEL__ around all include statements in header
>files that are also linked into user space programs. I can include
>whatever libc headers I want to make this work for
>hostapd/wpa_supplicant and the header files are still functional for the
>kernel code without any other changes.
>
>  
>
Ok this seems to be the problem. I do not know the bsd license but would 
it help if Jean would change the
license to dual license of gpl and bsd of only the header file?

>>We are trying to find the way so everything works together again with 
>>madwifi-ng.
>>
>>Here are my patch proposel.
>>This are all against wpa_supplicant-0.4.6 and hostapd-0.4.6
>>    
>>
>
>Thanks. I'll take a closer look at this, but that may have to wait till
>Saturday.
>
>  
>
Ok  forgott everything above ...
Only philosophic questions.

I have no compile both with you wireless_copy.h and my madwifi patches 
NOT iwlib patches and
my madwifi patches.
With this I was able to compile wpa_supplicant and hostapd.
With new version of wireless.h of Release 28-pre10 copyied to 
wireless_copy.h I was not able to compile.

>>Please let me know as soon as possible if we can go this way so we can 
>>work on at madwifi
>>and do the changes.
>>    
>>
>
>What changes are needed on the driver side?
>
>  
>
Not much. An include file more or so as sent already but the fact is to 
have a version which people can use
to compile the whole stuff without applying here a patch there a patch ...


Ok here my conclusions:

I send here all patches for madwifi-ng and wpa_supplicant-0.4.6 and 
hostapd-0.4.6 together.
With this patches it is possible to compile a working 
wpa_supplicant/hostapd for madwifi-ng release 1314.

But as noted before with this patches it works fine at least for me :-)



Beat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/2b34a982/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/2b34a982/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/2b34a982/attachment-0001.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: madwifi_1314.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/2b34a982/attachment-0002.txt 


From bmeier  Wed Nov  9 07:14:22 2005
From: bmeier (Beat Meier)
Date: Wed, 09 Nov 2005 12:14:22 -0300
Subject: How to compile hostapd-0.4.6 and wpa_supplicant-0.4.6 for madwifi-ng
	(1314)
In-Reply-To: <20051109023105.GA8986@jm.kir.nu>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
Message-ID: <4372124E.3040404@infovia.com.ar>

Jouni

If you don't want philosohic stuff read the end of the mail :-) for my 
conclusions to go for now ...

Jouni Malinen wrote:

>On Tue, Nov 08, 2005 at 08:42:24PM -0300, Beat Meier wrote:
>
>  
>
>>New version of wireless.h don't define anymore some includes.
>>    
>>
>
>I don't know what you are refering to with "new version", but the latest
>release, i.e., WE-19, does include linux/types.h, linux/socket.h, and
>linux/if.h.
>
>  
>
Release 28-pre10 does not include this anymore. Here the codefragment:

/***************************** INCLUDES *****************************/

/* Do not put any header in this file, this creates a mess when
 * exported to user space. Most users have included all the
 * relevant headers anyway... Jean II */
/*#include <linux/types.h>*/        /* for "caddr_t" et al      */
/*#include <linux/socket.h>*/       /* for "struct sockaddr" et al  */
/*#include <linux/if.h>*/       /* for IFNAMSIZ and co... */



>>Changes of drivers like madwifi will affect always hostapd, wpa_supplicant
>>because of changes of wireless packages.
>>    
>>
>
>Changes of the drivers should not affect (well, assuming they would use
>just Linux Wireless Extensions), but changes of WE do indeed affect user
>space programs.
>
>  
>
>>Why was wireless_copy.h added?
>>    
>>
>
>Because linux/wireless.h cannot be included in user space programs
>without major compatibility problems with libc header files. Another
>reason is in being able to build one binary that supports multiple WE
>versions.
>
>  
>
>>Madwifi has added now iwlib.h instead of linnux/wireless.h as you stated 
>>before
>>should not be included in userspace progs because of kernel space headers.
>>But iwlib.h would be the right inlcude also for hostapd, wpa_supplicant?
>>    
>>
>
>No, the license of iwlib is not compatible with hostapd/wpa_supplicant.
>
>  
>
Sorry. What do you mean with that?
hostapd/wpa_supplicant is dual license GPL version 2 and BSD,
iwlib.h is realeased unter GPL license.

Is this a problem because not BSD license or what do you mean?
sample_pm.c in wireless_tools is realease under LGPL, MPL or BSD license.

If this is a problem we could see with Jean or did you do that already 
some time ago?

>>Please let me know if anything is against this approch.
>>    
>>
>
>I cannot accept changes to hostapd/wpa_supplicant that would make them
>GPL only. I'm fine with the change that went already in into subversion,
>i.e., just #ifdef __KERNEL__ around all include statements in header
>files that are also linked into user space programs. I can include
>whatever libc headers I want to make this work for
>hostapd/wpa_supplicant and the header files are still functional for the
>kernel code without any other changes.
>
>  
>
Ok this seems to be the problem. I do not know the bsd license but would 
it help if Jean would change the
license to dual license of gpl and bsd of only the header file?

>>We are trying to find the way so everything works together again with 
>>madwifi-ng.
>>
>>Here are my patch proposel.
>>This are all against wpa_supplicant-0.4.6 and hostapd-0.4.6
>>    
>>
>
>Thanks. I'll take a closer look at this, but that may have to wait till
>Saturday.
>
>  
>
Ok  forgott everything above ...
Only philosophic questions.

I have no compile both with you wireless_copy.h and my madwifi patches 
NOT iwlib patches and
my madwifi patches.
With this I was able to compile wpa_supplicant and hostapd.
With new version of wireless.h of Release 28-pre10 copyied to 
wireless_copy.h I was not able to compile.

>>Please let me know as soon as possible if we can go this way so we can 
>>work on at madwifi
>>and do the changes.
>>    
>>
>
>What changes are needed on the driver side?
>
>  
>
Not much. An include file more or so as sent already but the fact is to 
have a version which people can use
to compile the whole stuff without applying here a patch there a patch ...


Ok here my conclusions:

I send here all patches for madwifi-ng and wpa_supplicant-0.4.6 and 
hostapd-0.4.6 together.
With this patches it is possible to compile a working 
wpa_supplicant/hostapd for madwifi-ng release 1314.

But as noted before with this patches it works fine at least for me :-)

BTW: I have testet WPA-PSK, EAP-TLS and PLAIN (no authentication) and 
everything seems to work correct
until now ...



Beat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/13932a43/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/13932a43/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant_madwifi_ng.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/13932a43/attachment-0001.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: madwifi_1314.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/13932a43/attachment-0002.txt 


From gentoopower  Wed Nov  9 07:30:35 2005
From: gentoopower (Stefan)
Date: Wed, 09 Nov 2005 16:30:35 +0100
Subject: WPA doesn't work - Authentication with 00:00:00:00:00:00 timed
	out.
In-Reply-To: <23815.80.50.88.10.1131515939.squirrel@www.ffii.org>
References: <19645.80.50.88.10.1131514616.squirrel@www.ffii.org>
	<23815.80.50.88.10.1131515939.squirrel@www.ffii.org>
Message-ID: <4372161B.2020705@yahoo.de>

Miernik wrote:

>>Hello,
>>
>>I have a problem trying to connect to an access point with WPA-PSK/CCMP
>>using with a Prism2.5 card, hostap 0.4.5 driver, 2.4.30 kernel with
>>Wireless Extensions v18 patch (default is v16 in 2.4.30, but that doesn't
>>support WPA). Version of wpa_supplicant is 0.4.5.
>>    
>>
>
>Sorry for a bit mangled log output, a better log of the problem is here:
>
>http://forum.openwrt.org/viewtopic.php?id=3214
>  
>

Have you tried with config looking like?

network={
        ssid="ehelp.pl"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk="........."
}

>--
>FFII
>+32486233396
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>


	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de



From tony  Wed Nov  9 10:09:35 2005
From: tony (Tony Jarnigan)
Date: Wed, 9 Nov 2005 12:09:35 -0600
Subject: unknown timeout using wpa_supplicant
Message-ID: <9d42e8280511091009l166cce6fs78ab664eef638025@mail.gmail.com>

My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim AP.
It connects fine but when another machine(B) on the network tries to ping
it, there's no response; no ssh or vnc either although the daemons are
running. It's not iptables or any other firewall software, nothing is
running.

Oddly enough, if A pings B, B can connect no problem. If I discontinue the
ping, the problem seems to come up again within 2 minutes. If I turn off
WPA-PSK and not run wpa_supplicant, everything works as expected.

Any ideas on what is going on? I appreciate any suggestions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051109/e6fb8ab4/attachment.htm 


From lists  Wed Nov  9 16:06:44 2005
From: lists (Lasse Riis)
Date: Thu, 10 Nov 2005 01:06:44 +0100
Subject: ioctl error
Message-ID: <43728F14.2000204@lasseriis.dk>

Hi

I'm having various problems with WPA_supplicant.

I've left out the in-kernel 80211 subsystem and I have the following 
versions of things (a combo reported to work on the ipw2100-list): 
(forgive the portage-style)
[ebuild   R   ] net-wireless/ieee80211-1.1.6
[ebuild   R   ] net-wireless/ipw2100-1.1.3
[ebuild   R   ] net-wireless/wpa_supplicant-0.4.6
[ebuild   R   ] net-wireless/wireless-tools-28_pre10

And my wpa_sup.conf (currently) reads:
nashe ~ # cat /etc/wpa_supplicant.conf
#ctrl_interface=/var/run/wpa_supplicant

eapol_version=1

ap_scan=2

network={
         ssid="Pozzi"
         proto=WPA
         key_mgmt=WPA-PSK
         pairwise=TKIP
         group=TKIP WEP104 WEP40
         psk="mykey"
         priority=2
}

One in a hundred times or so my wpa-setup will actually function. That 
means come up, obtain an IP-address and actually work. But usually only 
for an hour or less. (I've recognised no pattern of causes in the 
outages). This part of the problem i'm not sure i can blame on wpa_sup 
or my Linksys WAP54G, but so far I'm blaming the latter. I've not been 
able to have a Windows box running at the same time (as i don't have 
one) to see if it also drops the connection (as this would isolate the 
problem). These outages caused me to update to the above mentioned 
versions of everything. Hoping to increase stability.

However once I get kicked off, or just at most other times, starting wpa 
will fail. Running it manually reveals this ioctl error:
ioctl[SIOCSIWFREQ]: Operation not supported

I've not been able to tell what causes the whole thing to work. But it 
seems to only happen on "fresh boots", meaning times where the machine 
has just been booted, the ipw2100 mod has just been loaded and wpa_sup 
is started. But again, this is only 1/100 times or so, and hence not 
really a trusty pattern.

I have no clue what happens, or if this is even a wpa_sup or an ipw2100 
problem. (but ipw2100 works fine with unencrypted networks).

I was hoping someone might have some ideas?

Here's some sample output from a non-working run:

nashe ~ # wpa_supplicant -ieth1 -Dwext -c /etc/wpa_supplicant.conf -ddd
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'wext'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
eapol_version=1
ap_scan=2
Line: 7 - start of a new network block
ssid - hexdump_ascii(len=5):
      50 6f 7a 7a 69                                    Pozzi
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0xe
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
priority=2 (0x2)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 2
    id=0 ssid='Pozzi'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:04:23:92:09:4a
wpa_driver_wext_set_wpa
SIOCGIWRANGE: WE(compiled)=19 WE(source)=16 enc_capa=0x0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Trying to associate with SSID 'Pozzi'
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 14 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 
01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_associate
ioctl[SIOCSIWFREQ]: Operation not supported
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=14
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
Trying to associate with SSID 'Pozzi'
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 14 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 
01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_associate
ioctl[SIOCSIWFREQ]: Operation not supported
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=14
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Signal 2 received - terminating
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)



From proski  Wed Nov  9 18:25:40 2005
From: proski (Pavel Roskin)
Date: Wed, 09 Nov 2005 21:25:40 -0500
Subject: Patches to use madwifi-ng with hostapd-0.4.6 and
	wpa_supplicant-0.4.6
In-Reply-To: <20051109023105.GA8986@jm.kir.nu>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
Message-ID: <1131589540.6107.17.camel@dv>

Hi, Beat and Jouni!

On Tue, 2005-11-08 at 18:31 -0800, Jouni Malinen wrote:
> On Tue, Nov 08, 2005 at 08:42:24PM -0300, Beat Meier wrote:
> 
> > Why was wireless_copy.h added?
> 
> Because linux/wireless.h cannot be included in user space programs
> without major compatibility problems with libc header files. Another
> reason is in being able to build one binary that supports multiple WE
> versions.

That's a pretty good reason to have a copy.  I'm yet to see detailed
arguments against it (e.g. something doesn't work, and there is a way to
check it).

I suggest that the patches affecting the include files are dropped for
now.  I changed MadWifi tools to use iwlib.h yesterday, but there have
been some complaints (one was from somebody with glibc 2.1.x), and I'm
considering whether to revert that change.

> > We are trying to find the way so everything works together again with 
> > madwifi-ng.
> > 
> > Here are my patch proposel.
> > This are all against wpa_supplicant-0.4.6 and hostapd-0.4.6
> 
> Thanks. I'll take a closer look at this, but that may have to wait till
> Saturday.

Please check what happens with the compatibility with old MadWifi.  What
I would want to avoid is having broken leftovers of code to support old
MadWifi.  Either remove it or keep it working.

-- 
Regards,
Pavel Roskin




From ph  Wed Nov  9 20:02:52 2005
From: ph (Peter Harkins)
Date: Wed, 9 Nov 2005 22:02:52 -0600
Subject: DWL 520 E1 no longer works
Message-ID: <20051110040252.GA7917@malaprop.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm having serious trouble getting my DWL-520 E1 card working again
since I switched to Ubuntu, and I can't figure out why. It used to work
fine -- well, if I did a cold boot and then immediately a warm boot
before I tried to load the driver and, yes, this took a great many hours
to puzzle out. But this is the best I can get now:

$ sudo ./hostap_fw_load wlan0
Password:
Downloading primary firmware /etc/firmware/pm010102.hex
srec summary for pm010102.hex
Included file name: PM010102.HEX
Component: 0x0015 1.1.2 (primary firmware)


Verifying update compatibility and combining data:
Plugging PDR 0400 (NIC configuration): ram16=1 pci=1 (07 00)
OK.

Downloading to volatile memory (RAM).
OK.
srec summary for pm010102.hex
Included file name: PM010102.HEX
Component: 0x0015 1.1.2 (primary firmware)

ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
STAID not available (maybe running PRI-only)
ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
Could not read wlan PDA. This requires PRISM2_DOWNLOAD_SUPPORT definition in driver/module/hostap_config.h.

But that configuration variable was indeed compiled in when I followed
the instructions here: https://wiki.ubuntu.com//DLinkDWL520E1 I'm on
Ubuntu 5.10 with kernel 2.6.12-9-686, hostapd and hostap-source
1:0.4.2-1, and hostap-utils 1:0.4.0-1.

I'd appreciate any advice or pointers how to get this working.

Thanks in advance.


- --
Peter Harkins    -    ph at malaprop.org    -    http://malaprop.org


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: If you don't know what this is, it's OK to ignore it.

iD8DBQFDcsZra6PWv6+ALKoRAhUoAJ9SCIFQasrY6Gcf3hD9szXggy+v3wCcDLWF
MHjUgbpdS1e8ywWABlOGUmo=
=QXy9
-----END PGP SIGNATURE-----



From jkmaline  Wed Nov  9 20:17:07 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 9 Nov 2005 20:17:07 -0800
Subject: Patches to use madwifi-ng with hostapd-0.4.6 and
	wpa_supplicant-0.4.6
In-Reply-To: <1131589540.6107.17.camel@dv>
References: <437137E0.1070002@infovia.com.ar>
	<20051109023105.GA8986@jm.kir.nu> <1131589540.6107.17.camel@dv>
Message-ID: <20051110041707.GB8960@jm.kir.nu>

On Wed, Nov 09, 2005 at 09:25:40PM -0500, Pavel Roskin wrote:

> Please check what happens with the compatibility with old MadWifi.  What
> I would want to avoid is having broken leftovers of code to support old
> MadWifi.  Either remove it or keep it working.

Like I mentioned before, I'm not going to apply a patch that breaks
compatibility with the old madwifi version, so yes, I will indeed
testing this. However, I'm likely to remove the old-old (pre-BSD branch
merge) support at some point and now might be a good point do do it
since the mix of three different versions is starting to get somewhat
complex and difficult to maintain.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  9 20:31:22 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 9 Nov 2005 20:31:22 -0800
Subject: How to compile hostapd-0.4.6 and wpa_supplicant-0.4.6 for
	madwifi-ng (1314)
In-Reply-To: <4372124E.3040404@infovia.com.ar>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<4372124E.3040404@infovia.com.ar>
Message-ID: <20051110043122.GC8960@jm.kir.nu>

On Wed, Nov 09, 2005 at 12:14:22PM -0300, Beat Meier wrote:

> >I don't know what you are refering to with "new version", but the latest
> >release, i.e., WE-19, does include linux/types.h, linux/socket.h, and
> >linux/if.h.

> Release 28-pre10 does not include this anymore. Here the codefragment:

> /* Do not put any header in this file, this creates a mess when
> * exported to user space. Most users have included all the
> * relevant headers anyway... Jean II */
> /*#include <linux/types.h>*/        /* for "caddr_t" et al      */
> /*#include <linux/socket.h>*/       /* for "struct sockaddr" et al  */
> /*#include <linux/if.h>*/       /* for IFNAMSIZ and co... */

I believe this change was rejected already once (maybe when WE-19 was
submitted on netdev list) since it broke lots of drivers. I haven't
looked whether those drivers have been modified to allow this kind of
change in linux/wireless.h. Anyway, I'm not going to replace
wireless_copy.h anytime soon in hostapd/wpa_supplicant.

> >No, the license of iwlib is not compatible with hostapd/wpa_supplicant.

> Sorry. What do you mean with that?
> hostapd/wpa_supplicant is dual license GPL version 2 and BSD,
> iwlib.h is realeased unter GPL license.
> 
> Is this a problem because not BSD license or what do you mean?

Yes. I cannot use any GPL-only libraries in hostapd/wpa_supplicant as a
required core component (and if someone wants to be pedantic, I know
that GNU Readline is GPL-only, but that is an optional library for
wpa_cli). In other words, hostapd/wpa_supplicant must be available in a
form that can be used with BSD license.

> sample_pm.c in wireless_tools is realease under LGPL, MPL or BSD license.
> 
> If this is a problem we could see with Jean or did you do that already 
> some time ago?

Personally, I don't see any problem here since I do not have any plans
on starting to use iwlib now. I have not discussed this topic in more
details apart from mentioning that I cannot use that library due to
license incompatibility.

> Ok this seems to be the problem. I do not know the bsd license but would 
> it help if Jean would change the
> license to dual license of gpl and bsd of only the header file?

If the library part (libiw.so) is not needed for this particular use,
that would resolve the license compatibility issue, but like I
mentioned above, I'm not planning on change hostapd/wpa_supplicant on
this area at least at the moment. This kind of change could be helpful
for other programs, but I do not want to be trying to force people to
use any specific license.

> I have no compile both with you wireless_copy.h and my madwifi patches 
> NOT iwlib patches and
> my madwifi patches.
> With this I was able to compile wpa_supplicant and hostapd.
> With new version of wireless.h of Release 28-pre10 copyied to 
> wireless_copy.h I was not able to compile.

Thanks for reporting this. I'll try to update both hostapd and
wpa_supplicant later this week so that they can be used both with
madwifi-old and madwifi-ng.

> Not much. An include file more or so as sent already but the fact is to 
> have a version which people can use
> to compile the whole stuff without applying here a patch there a patch ...

OK.

> I send here all patches for madwifi-ng and wpa_supplicant-0.4.6 and 
> hostapd-0.4.6 together.
> With this patches it is possible to compile a working 
> wpa_supplicant/hostapd for madwifi-ng release 1314.

Thanks!

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  9 20:39:35 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 9 Nov 2005 20:39:35 -0800
Subject: ioctl error
In-Reply-To: <43728F14.2000204@lasseriis.dk>
References: <43728F14.2000204@lasseriis.dk>
Message-ID: <20051110043934.GD8960@jm.kir.nu>

On Thu, Nov 10, 2005 at 01:06:44AM +0100, Lasse Riis wrote:

> I've left out the in-kernel 80211 subsystem and I have the following 
> versions of things (a combo reported to work on the ipw2100-list): 

> ap_scan=2

Have you tried this with ap_scan=1?

>          group=TKIP WEP104 WEP40

That is actually invalid configuration for ap_scan=2 (only one option
allowed). However, I don't think that has anything to do with the issue
you are seeing.

> One in a hundred times or so my wpa-setup will actually function. That 
> means come up, obtain an IP-address and actually work. But usually only 
> for an hour or less. (I've recognised no pattern of causes in the 
> outages). This part of the problem i'm not sure i can blame on wpa_sup 
> or my Linksys WAP54G, but so far I'm blaming the latter.

Those are not the only components that need to work together, i.e., the
driver would need to be added to the list of potential reasons.

> However once I get kicked off, or just at most other times, starting wpa 
> will fail. Running it manually reveals this ioctl error:
> ioctl[SIOCSIWFREQ]: Operation not supported

I don't remember whether ipw2100 works with ap_scan=2. I have only used
ipw2200 driver and always with ap_scan=1 (i.e., wpa_supplicant using
scan requests).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  9 20:42:17 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 9 Nov 2005 20:42:17 -0800
Subject: unknown timeout using wpa_supplicant
In-Reply-To: <9d42e8280511091009l166cce6fs78ab664eef638025@mail.gmail.com>
References: <9d42e8280511091009l166cce6fs78ab664eef638025@mail.gmail.com>
Message-ID: <20051110044217.GE8960@jm.kir.nu>

On Wed, Nov 09, 2005 at 12:09:35PM -0600, Tony Jarnigan wrote:

> My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim AP.
> It connects fine but when another machine(B) on the network tries to ping
> it, there's no response; no ssh or vnc either although the daemons are
> running. It's not iptables or any other firewall software, nothing is
> running.
> 
> Oddly enough, if A pings B, B can connect no problem. If I discontinue the
> ping, the problem seems to come up again within 2 minutes. If I turn off
> WPA-PSK and not run wpa_supplicant, everything works as expected.

That sounds like issues with multicast/broadcast receive on the host
(A). Pinging A->B allows (B) to update its ARP table without (A) having
to receive broadcast arp who-has request and that 2 minutes would be a
timeout for the ARP cache.

What card and driver (including version) are you using on (A)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From tony  Thu Nov 10 06:56:28 2005
From: tony (Tony Jarnigan)
Date: Thu, 10 Nov 2005 08:56:28 -0600
Subject: unknown timeout using wpa_supplicant
In-Reply-To: <20051110044217.GE8960@jm.kir.nu>
References: <9d42e8280511091009l166cce6fs78ab664eef638025@mail.gmail.com>
	<20051110044217.GE8960@jm.kir.nu>
Message-ID: <9d42e8280511100656t31410637ge43c6b8acf5a6d67@mail.gmail.com>

On 11/9/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Wed, Nov 09, 2005 at 12:09:35PM -0600, Tony Jarnigan wrote:
>
> > My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim
> AP.
> > It connects fine but when another machine(B) on the network tries to
> ping
> > it, there's no response; no ssh or vnc either although the daemons are
> > running. It's not iptables or any other firewall software, nothing is
> > running.
> >
> > Oddly enough, if A pings B, B can connect no problem. If I discontinue
> the
> > ping, the problem seems to come up again within 2 minutes. If I turn off
> > WPA-PSK and not run wpa_supplicant, everything works as expected.
>
> That sounds like issues with multicast/broadcast receive on the host
> (A). Pinging A->B allows (B) to update its ARP table without (A) having
> to receive broadcast arp who-has request and that 2 minutes would be a
> timeout for the ARP cache.
>
> What card and driver (including version) are you using on (A)?


Proxim 8470 using madwifi checked out 8/14/05: ath_pci=0.9.6, ath_hal=
0.9.14.9 <http://0.9.14.9>

I've just recently learned the new madwifi is out but haven't had a chance
to compile it. I'll investigate broadcast issues but it also seems to be
some interaction with wpa_supplicant since without wpa_supplicant, B can get
to A without A pinging B.

Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051110/e08e8b9d/attachment.htm 


From jar  Thu Nov 10 08:31:34 2005
From: jar (Jar)
Date: Thu, 10 Nov 2005 18:31:34 +0200 (EET)
Subject: [Off topic] One (final) question about Wpa-psk/AES vs. Wpa2-psk/AES
Message-ID: <43113.194.157.0.2.1131640294.squirrel@netlandzone.dyndns.org>


Hello

Is the Wpa-psk/AES as secure as the Wpa2-psk/AES?

-- 
Best Regards, Jar



From bmeier  Thu Nov 10 08:40:29 2005
From: bmeier (Beat Meier)
Date: Thu, 10 Nov 2005 13:40:29 -0300
Subject: Patches to use madwifi-ng with hostapd-0.4.6
	andwpa_supplicant-0.4.6
In-Reply-To: <1131589540.6107.17.camel@dv>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<1131589540.6107.17.camel@dv>
Message-ID: <437377FD.20209@infovia.com.ar>

Pavel Roskin wrote:

>
>Please check what happens with the compatibility with old MadWifi.  What
>I would want to avoid is having broken leftovers of code to support old
>MadWifi.  Either remove it or keep it working.
>
>  
>
A already noted the patches SHOULD be compatible with old ones.
It compiles fine and there are only some ifdefs so there has no logic 
changed ...
Only thing could be bad ifdefs ...

Beat



From bryan  Thu Nov 10 09:35:09 2005
From: bryan (Bryan Kadzban)
Date: Thu, 10 Nov 2005 12:35:09 -0500
Subject: unknown timeout using wpa_supplicant
In-Reply-To: <9d42e8280511100656t31410637ge43c6b8acf5a6d67@mail.gmail.com>
References: <9d42e8280511091009l166cce6fs78ab664eef638025@mail.gmail.com>
	<20051110044217.GE8960@jm.kir.nu>
	<9d42e8280511100656t31410637ge43c6b8acf5a6d67@mail.gmail.com>
Message-ID: <20051110173509.GA8676@kadzban.is-a-geek.net>

On Thu, Nov 10, 2005 at 08:56:28AM -0600, Tony Jarnigan wrote:
> I'll investigate broadcast issues but it also seems to be some
> interaction with wpa_supplicant since without wpa_supplicant, B can
> get to A without A pinging B.

Well, without wpa_supplicant there is no group encryption (...at least,
barring WEP).  So if the problem is with the TKIP or AES group keys
getting out of sync or getting set up wrong, that could be what you're
seeing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051110/2b8241c8/attachment.pgp 


From engage  Thu Nov 10 15:57:00 2005
From: engage (engage)
Date: Thu, 10 Nov 2005 16:57:00 -0700
Subject: wpa_supplicant dies?
Message-ID: <200511101657.00814.engage@n0sq.us>

I'm running version 0.4.5 with a Linksys WMP54G & Linksys WRT54G router. 
Kernel 2.6.14, Mandriva 2005LE. WPA-PSK.

The problem is that the key gets turned off on the PC. When I run killall 
wpa_supplicant I get a no process killed message. So, I execute 
wpa_supplicant, iwconfig shows everything OK (AP association, key, etc). But, 
I get no route to host when I try to ping the AP. The AP is running since my 
wired connections work OK. The WMP54G has a static address & ifconfig shows 
proper configuration. I tried a network restart and still can't ping the 
router but I can ping the wireless card address. Grr, I forgot to check the 
routing tables. Anyway, a reboot gets everything working again.  I don't see 
any problems in the logs. I'm going to turn on debugging but I'm not sure if 
I'll understand the output since I'm not a security guru. Any idea as to what 
is causing this? 

So far, google hasn't provided me with an answer or a clue. Currently, I'm 
using a workaround by having cron run a script to monitor the encryption key 
- if the key is off the PC will be rebooted - not an elegant solution but it 
keeps the system running (especially when I'm away from home).



From throw_away_2002  Thu Nov 10 16:54:10 2005
From: throw_away_2002 (none none)
Date: Thu, 10 Nov 2005 16:54:10 -0800 (PST)
Subject: Worked for a while, but no longer
Message-ID: <20051111005410.95567.qmail@web52113.mail.yahoo.com>

I had this working (briefly), but now
it seems I can't connect again. :(

# dog /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
        group=TKIP
        key_mgmt=WPA-PSK
        pairwise=TKIP
        proto=WPA
        psk="mypassword"
        ssid="myssid"
        }


# wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf
-iwlan0 -dd

Initializing interface 'wlan0' conf
'/etc/wpa_supplicant.conf' driver 'ndiswrapper'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=2
Line: 5 - start of a new network block
group: 0x8
key_mgmt: 0x2
pairwise: 0x8
proto: 0x1
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
ssid - hexdump_ascii(len=11):  [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='myssid'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: [REMOVED]
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Trying to associate with SSID 'myssid'
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8c07 len=87
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated to a new BSS: BSSID= [REMOVED]
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: Using WPA IE from AssocReq to set cipher suites
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Associated with [REMOVED]
EAPOL: External notification - portEnabled=0

EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00
00 00 00 00 00 00 01 4f 08 2e ef 65 b9 cf 7d 57 01 17 73 fc
b3 b8 66 20 53 d8 81
72 85 db 8f f5 4a 9a 4e a9 13 fa 1d 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89
00 20 00 00 00 00 00 00 00 01 4f 08 2e ef 65 b9 cf 7d 57 01
17 73 fc b3 b8 66 20
53 d8 81 72 85 db 8f f5 4a 9a 4e a9 13 fa 1d 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVED]
WPA: Renewed SNonce - hexdump(len=32): 67 85 36 e4 71 8a 31
de f6 97 2b b0 ca 4a 10 f8 b5 37 f6 a8 ce c9 3b 73 29 ca 2c
24 0f 7e 64 fe
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 2d d1 5b e7 07 40 4c
2c d9 9f c8 f6 08 05 7b c4
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82
00 14 a5 15 f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00
00 00 00 00 01 67 8
5 36 e4 71 8a 31 de f6 97 2b b0 ca 4a 10 f8 b5 37 f6 a8 ce
c9 3b 73 29 ca 2c 24 0f 7e 64 fe 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d d1 5b
e7 07 40 4c 2c d9 9f c8 f6 08 05 7b c4 00 18 dd 16 00 50 f2
01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0
startWhen=29 idleWhile=59
EAPOL: Port Timers tick - authWhile=0 heldWhile=0
startWhen=28 idleWhile=58
Wireless event: cmd=0x8c07 len=87
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated with [REMOVED]
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED

The last 36 (or so) lines just keep repeating
(with minor changes in the hex dumps). The
client seems to see the access point (and the
access point sees the client as an "attached
device"), but somehow authentication never
seems to take place. Can someone explain why
not?

Thank you very much in advancne for your help.


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com



From miernik  Thu Nov 10 20:32:04 2005
From: miernik (Miernik)
Date: Fri, 11 Nov 2005 05:32:04 +0100 (CET)
Subject: WPA doesn't work - Authentication with 00:00:00:00:00:00 timed 
	out.
In-Reply-To: <4372161B.2020705@yahoo.de>
References: <19645.80.50.88.10.1131514616.squirrel@www.ffii.org>
	<23815.80.50.88.10.1131515939.squirrel@www.ffii.org>
	<4372161B.2020705@yahoo.de>
Message-ID: <10869.80.50.88.10.1131683524.squirrel@www.ffii.org>

>>Sorry for a bit mangled log output, a better log of the problem is here:
>>
>>http://forum.openwrt.org/viewtopic.php?id=3214
>>
>>
>
> Have you tried with config looking like?
>
> network={
>         ssid="ehelp.pl"
>         proto=WPA
>         key_mgmt=WPA-PSK
>         pairwise=CCMP TKIP
>         group=CCMP TKIP
>         psk="........."
> }

Yes, no difference.

-- 
Miernik




From tobias.gebhard  Fri Nov 11 04:47:31 2005
From: tobias.gebhard (Tobias Gebhard)
Date: Fri, 11 Nov 2005 13:47:31 +0100 (CET)
Subject: status of prism54-wpa for hostapd
Message-ID: <30810736.1131713252123.OPEN-XCHANGE.WebMail.ox@lee.leedom.home>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051111/701d6212/attachment.htm 


From tobias.gebhard  Fri Nov 11 04:55:33 2005
From: tobias.gebhard (Tobias Gebhard)
Date: Fri, 11 Nov 2005 13:55:33 +0100 (CET)
Subject: status of prism54-wpa for hostapd
Message-ID: <24056908.1131713734159.OPEN-XCHANGE.WebMail.ox@lee.leedom.home>

Sorry, first mail was html only format. Now in plain text:
?

Hello,
I am using the current snapshot from the prism54 drivers (not the kernel
one).
Running hostapd without WPA works without problems.

The Problem:
hostapd with WPA (wpa=1) exits with an errormessage.

The command:
$ hostapd hostapd.conf
Configuration file: hostapd.conf
Using interface eth2 with hwaddr 00:01:36:0d:c2:ea and ssid 'test'
Could not set PrivacyInvoked for interface eth2
WPA initialization failed.
rmdir[ctrl_interface]: No such file or directory
Could not disable PrivacyInvoked for interface eth2
$ dmesg|tail -n 3
ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.
ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.
ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.


Are there any activities for hostapd with wpa for prism54 cards?
Is there any chance to get this running or should kick away the prism54
card and buy an atheros card?





From m  Fri Nov 11 06:29:39 2005
From: m (Matthias Lemke)
Date: Fri, 11 Nov 2005 15:29:39 +0100
Subject: wpa-psk with hostap problem to associate
In-Reply-To: <20051106225823.1520713406C@mail.iocaine.com>
References: <20051106225823.1520713406C@mail.iocaine.com>
Message-ID: <4374AAD3.10106@box.li>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

i am using hostap + wpa_supplicant (0.3.8)
STA firmware is 1.7.4

The AP is configured to: WPA-PSK with TKIP.
ssid "seclan" is broadcasted.

I set "iwconfig wlan0 essid "seclan"

/usr/sbin/wpa_supplicant -w  -i wifi0 -d -c /etc/wpa_supplicant.conf

Kernel is 2.6.14

the config includes:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
#eapol_version=1
#ap_scan=0



network={
        ssid="seclan"
        scan_ssid=1
        key_mgmt=WPA-PSK
        proto=WPA
        pairwise=TKIP
        group=TKIP
        psk=aaf189c326f0a3f9813fc089955027868fb6f33ae647985d591d6b6b637283a5
}


and a debug output looks like:


Scan SSID - hexdump_ascii(len=6):
     73 65 63 6c 61 6e                                 seclan
Wireless event: cmd=0x8b19 len=8
IWEVGENIE overflow
Received 209 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:13:10:15:45:4a ssid='' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
No APs found - clear blacklist and try again
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Selecting BSS from priority group 0
0: 00:13:10:15:45:4a ssid='' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Signal 2 received - terminating
No keys have been configured - skip key clearing


what happens?

regards and thanks

math
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDdKrTpmSFPkdbqigRAhW/AKCVpCSMyrj9/+ZhEzP6QNPaO5ffiQCfcTCt
W9Oks3n8JDbXHGP6QfyGYpo=
=259W
-----END PGP SIGNATURE-----



From oshogg  Fri Nov 11 15:52:33 2005
From: oshogg (Osho GG)
Date: Fri, 11 Nov 2005 15:52:33 -0800
Subject: newbie questions about wpa_supplicant
Message-ID: <126dcc3c0511111552q1ad8b904j9e2664c3fc3b12bb@mail.gmail.com>

Hi,

I just started using wpa_supplicant and have a basic question about it. I
have a home network using WPA-PSK, a work network using WEP with hidden
ssid, a school network using no securing (yes!) and a couple of public hot
spots that I visit. I am very happy with wpa_supplicant in that it can
automatically connect and configure my wireless interface in each of these
locations!!!

My question concerns regarding starting of dhcpcd. Everytime I have to
manually start the dhcpcd once wpa_supplicant establishes the connection
with the Access point. Is there a way wpa_supplicant can do it
automatically? My other question is can wpa_supplicant handle wired
interfaces?

Currently, I have ifplugd running for wired interface and wpa_supplicant
running for wireless interface. In the ifplugd action script, I handle
starting and killing of dhcpcd for both wired and wireless interfaces.
However, this is prone to many different race conditions (particularly when
I consider suspending/resuming and roaming from one location to another). It
would be great if wpa_supplicant could also handle my wired interface and
can automagically manage dhcpcd start/killing for the interfaces (of course
with preference for wired over wireless) and I did not have to run ifplugd
at all. Has anyone able to do that?

I am using IBM Thinkpad T42p laptop running SuSE 9.1 with the following
configuration.

Kernel - 2.6.14
Wireless driver - ipw2200 1.0.8
Wireless card's firmware version - 2.4
IEEE 80211 version - ieee80211 1.1.6 (I removed the one that was supplied
with the kernel)
wpa_supplicant - 0.4.6
ifplugd - 0.25

Any help would be greatly appreciated.

Thanks,
--
Osho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051111/6115eef3/attachment.htm 


From jkmaline  Fri Nov 11 20:24:41 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 11 Nov 2005 20:24:41 -0800
Subject: How to compile hostapd-0.4.6 and wpa_supplicant-0.4.6 for
	madwifi-ng (1314)
In-Reply-To: <4372124E.3040404@infovia.com.ar>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<4372124E.3040404@infovia.com.ar>
Message-ID: <20051112042441.GA8991@jm.kir.nu>

On Wed, Nov 09, 2005 at 12:14:22PM -0300, Beat Meier wrote:

> I send here all patches for madwifi-ng and wpa_supplicant-0.4.6 and 
> hostapd-0.4.6 together.
> With this patches it is possible to compile a working 
> wpa_supplicant/hostapd for madwifi-ng release 1314.

Thanks again. I ended up doing this a bit differently so that users do
not need to configure madwifi-ng vs. madwifi-old in .config. In other
words, this is selected automatically based on the defined ioctls. One
will still need to build hostapd/wpa_supplicant separately for
madwifi-ng and madwifi-old, i.e., the automatic detection is build time
operation.

I cleaned up the ioctl error printing and added a backup timeout for
scan request so that the temporary driver_wext::scan() does not need to
be used. Anyway, it would be nice to get madwifi-ng supporting the new
WE-18 mechanism for per-SSID scans instead of the current broken
mechanism of using set_ssid to select which SSID to scan for.

IEEE80211_MLME_CLEAR_STATS is now used only if the header files define
it, i.e., it is not currently used with madwifi-ng, but will be
automatically taken into use (with rebuild of hostapd) once support for
that has been merged into madwifi-ng.

All changes are in my CVS (devel branch only) and will be included in
the next release (0.4.7). I verified that both wpa_supplicant and
hostapd build and based on a quick test, seem to also work, with both
madwifi-old and madwifi-ng.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Nov 11 20:28:02 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 11 Nov 2005 20:28:02 -0800
Subject: wpa_supplicant win98 wired patch
In-Reply-To: <Pine.LNX.4.44.0511072037300.28127-100000@eloth.gjh.sk>
References: <20051106034022.GA8972@jm.kir.nu>
	<Pine.LNX.4.44.0511072037300.28127-100000@eloth.gjh.sk>
Message-ID: <20051112042802.GB8991@jm.kir.nu>

On Mon, Nov 07, 2005 at 09:19:24PM +0100, Jozef Vesely wrote:

> I would like to qualify the "testing" wpa_supplicant
> received on win98. As I have limited access to the Win98
> machine, you'd rather not consider it thoroughly tested.
> I have no access to neither wireless card nor network so
> everything I write concerns wired network.

Thanks for the details.

> So I looked into the wpa_supplicant and came up with "obvious"
> patch to filtering rule I sent you. Patched wpa_supplicant
> "works" OK (receives "Request,Identity" packet and responds
> with "Response,Identity") in my simulated environment,
> however today's brief tests on real win98 in 802.1x network
> were _negative_.

That's unfortunate. Anyway, I verified that the patch fixed this issue
on WinXP, so the change itself was indeed correct. I have no idea what
could be causing issues on Win98, though.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kelrin  Sat Nov 12 01:23:45 2005
From: kelrin (Kel Modderman)
Date: Sat, 12 Nov 2005 19:23:45 +1000
Subject: [Madwifi-devel] Re: How to compile hostapd-0.4.6 and
	wpa_supplicant-0.4.6 for madwifi-ng (1314)
In-Reply-To: <20051112042441.GA8991@jm.kir.nu>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<4372124E.3040404@infovia.com.ar> <20051112042441.GA8991@jm.kir.nu>
Message-ID: <4375B4A1.50901@tpg.com.au>

Jouni Malinen wrote:

>On Wed, Nov 09, 2005 at 12:14:22PM -0300, Beat Meier wrote:
>
>  
>
>>I send here all patches for madwifi-ng and wpa_supplicant-0.4.6 and 
>>hostapd-0.4.6 together.
>>With this patches it is possible to compile a working 
>>wpa_supplicant/hostapd for madwifi-ng release 1314.
>>    
>>
>
>Thanks again. I ended up doing this a bit differently so that users do
>not need to configure madwifi-ng vs. madwifi-old in .config. In other
>words, this is selected automatically based on the defined ioctls. One
>will still need to build hostapd/wpa_supplicant separately for
>madwifi-ng and madwifi-old, i.e., the automatic detection is build time
>operation.
>  
>
Hi Jouni,

This is great news!

However, this method has a distinct disadvantage for binary 
distributions; a new wpasupplicant that works with madwifi-ng will not 
be backwards compatible with users still happy with the old madwifi, as 
it seems that you will support one or the other but not both at once.

Is it too much of a burden on you to support multiple madwifi versions 
at once?

Suggestions on howto handle this situation for maintainers of 
wpa_supplicant for various binary distributions?

Thanks, Kel.



From jkmaline  Sat Nov 12 06:59:30 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 06:59:30 -0800
Subject: [Madwifi-devel] Re: How to compile hostapd-0.4.6 and
	wpa_supplicant-0.4.6 for madwifi-ng (1314)
In-Reply-To: <4375B4A1.50901@tpg.com.au>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<4372124E.3040404@infovia.com.ar>
	<20051112042441.GA8991@jm.kir.nu> <4375B4A1.50901@tpg.com.au>
Message-ID: <20051112145930.GA8979@jm.kir.nu>

On Sat, Nov 12, 2005 at 07:23:45PM +1000, Kel Modderman wrote:

> However, this method has a distinct disadvantage for binary 
> distributions; a new wpasupplicant that works with madwifi-ng will not 
> be backwards compatible with users still happy with the old madwifi, as 
> it seems that you will support one or the other but not both at once.

Just to make sure it was understood that this is in no way limited to
"this method" since all the patches I've seen has the same property.

> Is it too much of a burden on you to support multiple madwifi versions 
> at once?

It would be somewhat complex. One could either create two separate
driver interfaces in wpa_supplicant (e.g., driver_madwifi.c and
driver_madwifi_ng.c) which is something that I was considering to do
first. However, since the madwifi drivers use the exact same include
file names, the build system would need to be modified to point at
different directories for these two set of files.

Alternatively, one could create copy of all the needed structures from
both versions and create private set of header files with both
structures included and then decide on run time which one to use.
Obviously, this would be quite a bit of extra work. If the driver
interfaces were expected to be relatively static, I could consider doing
this, but I don't that this would be the case for madwifi-ng, so I'm
unlikely to be interested in following up with changes in the header
files and synchorizing the private, merged copy of the structures with
that all the time.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 12 07:08:04 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 07:08:04 -0800
Subject: [Madwifi-devel] Re: How to compile hostapd-0.4.6 and
	wpa_supplicant-0.4.6 for madwifi-ng (1314)
In-Reply-To: <20051112145930.GA8979@jm.kir.nu>
References: <437137E0.1070002@infovia.com.ar> <20051109023105.GA8986@jm.kir.nu>
	<4372124E.3040404@infovia.com.ar>
	<20051112042441.GA8991@jm.kir.nu> <4375B4A1.50901@tpg.com.au>
	<20051112145930.GA8979@jm.kir.nu>
Message-ID: <20051112150804.GB8979@jm.kir.nu>

On Sat, Nov 12, 2005 at 06:59:30AM -0800, Jouni Malinen wrote:
> On Sat, Nov 12, 2005 at 07:23:45PM +1000, Kel Modderman wrote:
> > Is it too much of a burden on you to support multiple madwifi versions 
> > at once?
> 
> It would be somewhat complex. One could either create two separate
> driver interfaces in wpa_supplicant (e.g., driver_madwifi.c and
> driver_madwifi_ng.c)

Actually, for wpa_supplicant, the easiest solution would be to start
using driver_wext.c by someone adding WE-18 support to madwifi-ng.. This
would get rid of need to maintain separate driver interface code in the
future and driver_madwifi.c could be built against madwifi-old headers.
Sure, this would not solve all issues (e.g., using madwifi-ng with WE-17
or older), but it would certainly be nicer as far as the goal of getting
Linux driver using common interface is concerned.
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From superd1230  Sat Nov 12 08:11:01 2005
From: superd1230 (superd)
Date: Sun, 13 Nov 2005 00:11:01 +0800
Subject: RSN pre-authentication environment
Message-ID: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>

I used hostapd 0.3.9, wpa_supplicant 0.3.9 under freebsd 6.0 to build
my pre-authentication environment, but wpa_supplicant always tell me
pre-authentication timed out.
do any people success building pre-authentication environment?
What OS, hostapd,and wpa_supplicant version do you use?
thx.



From jkmaline  Sat Nov 12 08:19:41 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 08:19:41 -0800
Subject: RSN pre-authentication environment
In-Reply-To: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
References: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
Message-ID: <20051112161940.GA9439@jm.kir.nu>

On Sun, Nov 13, 2005 at 12:11:01AM +0800, superd wrote:
> I used hostapd 0.3.9, wpa_supplicant 0.3.9 under freebsd 6.0 to build
> my pre-authentication environment, but wpa_supplicant always tell me
> pre-authentication timed out.
> do any people success building pre-authentication environment?
> What OS, hostapd,and wpa_supplicant version do you use?

I've tested pre-authentication successfully with 0.3.x and 0.4.x version
and Linux and WinXP. Please give more details of your configuration and
debug log from both wpa_supplicant and hostapd.

-- 
Jouni Malinen                                            PGP id EFC895FA



From superd1230  Sat Nov 12 08:39:08 2005
From: superd1230 (superd)
Date: Sun, 13 Nov 2005 00:39:08 +0800
Subject: RSN pre-authentication environment
In-Reply-To: <20051112161940.GA9439@jm.kir.nu>
References: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
	<20051112161940.GA9439@jm.kir.nu>
Message-ID: <699acd380511120839m567a9734n5e7a60d323749f62@mail.gmail.com>

I use preauth_test to check
thanks.
========== hostapd.conf ====================
interface=ath0
driver=bsd

logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
debug=3
dump_file=/home/hostapd/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel

ssid=wmnet
macaddr_acl=0
auth_algs=1

ieee8021x=1

own_ip_addr=192.168.71.54 <-- 2 APs' IP are different
auth_server_addr=140.114.71.149
auth_server_port=1812
auth_server_shared_secret=SharedSecret99

wpa=2
wpa_key_mgmt=WPA-EAP
wpa_pairwise=CCMP TKIP
rsn_preauth=1
rsn_preauth_interfaces=rl0

========== hostapd start ===================
Configuration file: ./hostapd.conf
bsd_set_iface_flags: dev_up=0
bsd_get_ssid: ssid="wmnet"
Using interface ath0 with hwaddr 00:11:95:f4:cf:63 and ssid 'wmnet'
Nov 12 16:18:42.149529: ath0: RADIUS Authentication server 140.114.71.149:1812
bsd_set_ieee8021x: enabled=1
bsd_configure_wpa: group key cipher=TKIP (1)
bsd_configure_wpa: pairwise key ciphers=0xa
bsd_configure_wpa: key management algorithms=0x1
bsd_configure_wpa: rsn capabilities=0x1
bsd_configure_wpa: enable WPA= 0x2
bsd_set_iface_flags: dev_up=1
RSN pre-auth interface 'rl0'
bsd_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): f9 e6 99 00 4a 59 5e 2f 54 76 ec 62 f9 bd ce 9c
b9 a5 49 df ca 74 33 4f 00 4a 81 d2 b1 78 48 92
GTK - hexdump(len=32): 9e 0e 0e f2 40 2f 52 e3 80 04 85 bb 8b 5c ff 1c
bc 6b 14 65 fa 0d 0e 4a 6f 7f 68 45 ba 27 c0 a2
WPA: group state machine entering state SETKEYSDONE
bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
bsd_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations

==== wpa_supplicant =========
> ./preauth_test wpa_supplicant.conf 00:11:95:f4:cf:63 fxp0
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=5):
     77 6d 6e 65 74                                    wmnet
scan_ssid=1 (0x1)
mode=0 (0x0)
proto: 0x2
key_mgmt: 0x1
auth_alg: 0x1
eap methods - hexdump(len=2): 0d 00
identity - hexdump_ascii(len=5):
     74 65 65 6d 75                                    teemu
ca_cert - hexdump_ascii(len=25):
     2f 68 6f 6d 65 2f 77 70 61 2f 63 65 72 74 2f 63   /home/wpa/cert/c
     61 63 65 72 74 2e 70 65 6d                        acert.pem
client_cert - hexdump_ascii(len=29):
     2f 68 6f 6d 65 2f 77 70 61 2f 63 65 72 74 2f 63   /home/wpa/cert/c
     6c 69 65 6e 74 63 65 72 74 2e 70 65 6d            lientcert.pem
private_key - hexdump_ascii(len=29):
     2f 68 6f 6d 65 2f 77 70 61 2f 63 65 72 74 2f 63   /home/wpa/cert/c
     6c 69 65 6e 74 63 65 72 74 2e 70 65 6d            lientcert.pem
private_key_passwd - hexdump_ascii(len=9):
     70 77 34 63 6c 69 65 6e 74                        pw4client
Priority group 0
   id=0 ssid='wmnet'
RSN: starting pre-authentication with 00:11:95:f4:cf:63
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=1
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL (preauth) - hexdump(len=4): 01 01 00 00
EAPOL test timed out


===== server side I use tcpdump to check packet ========
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on rl0, link-type EN10MB (Ethernet), capture size 96 bytes
16:19:24.080983 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:28.216489 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:33.225924 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:38.235353 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:43.244796 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:48.254229 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
16:19:53.263677 00:0d:60:cb:f4:7f (oui Unknown) > 00:11:95:f4:cf:63
(oui Unknown), ethertype Unknown (0x88c7), length 60:
^[^[^[^C26057 packets captured
26407 packets received by filter
0 packets dropped by kernel


On 11/13/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Sun, Nov 13, 2005 at 12:11:01AM +0800, superd wrote:
> > I used hostapd 0.3.9, wpa_supplicant 0.3.9 under freebsd 6.0 to build
> > my pre-authentication environment, but wpa_supplicant always tell me
> > pre-authentication timed out.
> > do any people success building pre-authentication environment?
> > What OS, hostapd,and wpa_supplicant version do you use?
>
> I've tested pre-authentication successfully with 0.3.x and 0.4.x version
> and Linux and WinXP. Please give more details of your configuration and
> debug log from both wpa_supplicant and hostapd.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jkmaline  Sat Nov 12 08:46:22 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 08:46:22 -0800
Subject: newbie questions about wpa_supplicant
In-Reply-To: <126dcc3c0511111552q1ad8b904j9e2664c3fc3b12bb@mail.gmail.com>
References: <126dcc3c0511111552q1ad8b904j9e2664c3fc3b12bb@mail.gmail.com>
Message-ID: <20051112164622.GB9439@jm.kir.nu>

On Fri, Nov 11, 2005 at 03:52:33PM -0800, Osho GG wrote:

> My question concerns regarding starting of dhcpcd. Everytime I have to
> manually start the dhcpcd once wpa_supplicant establishes the connection
> with the Access point. Is there a way wpa_supplicant can do it
> automatically?

Yes, or well, to be more exact, wpa_supplicant can be used to generate
an event when network connection is established and an external program
would be used to do whatever network configuration is needed. I believe
some Linux distributions have already done this kind of integration.

I added following description into the README file on how to do this
with wpa_cli:

wpa_cli can used to run external programs whenever wpa_supplicant
connects or disconnects from a network. This can be used, e.g., to
update network configuration and/or trigget DHCP client to update IP
addresses, etc.

One wpa_cli process in "action" mode needs to be started for each
interface. For example, the following command starts wpa_cli for the
default ingterface (-i can be used to select the interface in case of
more than one interface being used at the same time):

wpa_cli -a/sbin/wpa_action.sh -B

The action file (-a option, /sbin/wpa_action.sh in this example) will
be executed whenever wpa_supplicant completes authentication (connect
event) or detects disconnection). The action script will be called
with two command line arguments: interface name and event (CONNECTED
or DISCONNECTED). If the action script needs to get more information
about the current network, it can use 'wpa_cli status' to query
wpa_supplicant for more information.

Following example can be used as a simple template for an action
script:

#!/bin/sh

IFNAME=$1
CMD=$2

if [ "$CMD" == "CONNECTED" ]; then
    SSID=`wpa_cli -i$IFNAME status | grep ^ssid= | cut -f2- -d=`
    # configure network, signal DHCP client, etc.
fi

if [ "$CMD" == "DISCONNECTED" ]; then
    # remove network configuration, if needed
fi


> My other question is can wpa_supplicant handle wired interfaces?

Yes, driver_wired.c (-Dwired on command line) can be used to
authenticate wired interfaces with IEEE 802.1X. Example from README:

6) Authentication for wired Ethernet. This can be used with 'wired'
interface
   (-Dwired on command line).

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=0
network={
    key_mgmt=IEEE8021X
    eap=MD5
    identity="user"
    password="password"
    eapol_flags=0
}

-- 
Jouni Malinen                                            PGP id EFC895FA



From rob.vandermeulen  Sat Nov 12 08:52:42 2005
From: rob.vandermeulen (Rob Vandermeulen)
Date: Sat, 12 Nov 2005 17:52:42 +0100
Subject: Very slow roaming or reassociation in WPA2 mode
Message-ID: <200511121752.42606.rob.vandermeulen@tiscali.be>

Hello
I am still having problems roaming/reconnecting to our wireless network, which 
is very unpleasant since we are planning to run a few hundred citrix users 
(using an ipw2200 equiped laptop) over it (and citrix doesn't really love 
minute-long disconnects). Anyway, i did some more extensive testing and 
gathered the following. (logs 
are at the bottom)

The test setup -
1 Trapeze MX and 2 ("dump") AP's connected to it (this setup is fully WPA2 
compliant) - APs have mac ending in B9:80 and 17:80 (this one is located 
further from my test setup then the first one). 

I can connect fine with wpa_supplicant (0.4.6 version, ipw-1.0.8, ieee-1.1.6, 
fw 2.4, kernel 2.6.13 ) using wext, and the card connects fine to the 17:80 
AP (although the other one is much closer, a few meters from the test setup). 
Everything is fine, an then i disable the 17:80 radio. wpa_supplicants 
detects this very fast, and start to reassociate. This works, but takes 
somewhere between 30s-1minute. It first has to try a few times to 
reassociate, and when that works it just "hangs" while trying to reassociate 
somewhere in the process... and the citrix session is long lost by the time 
it comes through.

This behavior also seems to happen after a few hours connect time (without me 
disabling an AP's radio), mostly after +- 4 or 8 hours according to the 
reports i got from the testusers.

Logs are here (on a deflate enabled webserver)
http://www.redsoft.be/stuff/wpalog
http://www.redsoft.be/stuff/dmesglog

Kind regards
Rob Vandermeulen



From jkmaline  Sat Nov 12 09:04:13 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 09:04:13 -0800
Subject: RSN pre-authentication environment
In-Reply-To: <699acd380511120839m567a9734n5e7a60d323749f62@mail.gmail.com>
References: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
	<20051112161940.GA9439@jm.kir.nu>
	<699acd380511120839m567a9734n5e7a60d323749f62@mail.gmail.com>
Message-ID: <20051112170413.GC9439@jm.kir.nu>

On Sun, Nov 13, 2005 at 12:39:08AM +0800, superd wrote:

> I use preauth_test to check

> ========== hostapd.conf ====================
> interface=ath0
> rsn_preauth_interfaces=rl0

The configuration files looked fine and a similar test on my Linux test
setup works.

> Using interface ath0 with hwaddr 00:11:95:f4:cf:63 and ssid 'wmnet'

> > ./preauth_test wpa_supplicant.conf 00:11:95:f4:cf:63 fxp0

Please note that the MAC address used here is likely to differ from the
MAC address of the rl0 interface. If rl0 is filtering frames based on
the MAC address, it will likely drop the RSN pre-authentication frames
since they are going to a foreign address.

On Linux, I see similar behavior when the rsn_preauth_interfaces are not
in promiscuous mode. Once I configure them for promiscuous mode, hostapd
starts seeing the pre-authentication frames and debug log shows "RSN:
receive pre-auth packet from interface...".

I don't know how FreeBSD netif is normally configured for this kind of
case, but you will probably either have to configure it for promiscuous
mode or if possible, add the MAC address of the wireless interface to
list of RX addresses for the wired interface.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 12 09:22:05 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 09:22:05 -0800
Subject: wpa-psk with hostap problem to associate
In-Reply-To: <4374AAD3.10106@box.li>
References: <20051106225823.1520713406C@mail.iocaine.com>
	<4374AAD3.10106@box.li>
Message-ID: <20051112172205.GD9439@jm.kir.nu>

On Fri, Nov 11, 2005 at 03:29:39PM +0100, Matthias Lemke wrote:

> i am using hostap + wpa_supplicant (0.3.8)

> I set "iwconfig wlan0 essid "seclan"

That is not needed.

> /usr/sbin/wpa_supplicant -w  -i wifi0 -d -c /etc/wpa_supplicant.conf

You should use wlan0, not wifi0 as the interface.

> Kernel is 2.6.14

Linux 2.6.14 changes some of the wireless extensions events in
uncompatible way and wpa_supplicant 0.3.8 does not have matching
changes. You will either need to update to the current 0.3.x snapshot or
to the latest 0.4.x version to work with Linux 2.6.14.

> IWEVGENIE overflow

This is caused by the difference in Linux 2.6.14 (WE-19) events.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 12 09:23:48 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 12 Nov 2005 09:23:48 -0800
Subject: [Off topic] One (final) question about Wpa-psk/AES vs.
	Wpa2-psk/AES
In-Reply-To: <43113.194.157.0.2.1131640294.squirrel@netlandzone.dyndns.org>
References: <43113.194.157.0.2.1131640294.squirrel@netlandzone.dyndns.org>
Message-ID: <20051112172348.GE9439@jm.kir.nu>

On Thu, Nov 10, 2005 at 06:31:34PM +0200, Jar wrote:

> Is the Wpa-psk/AES as secure as the Wpa2-psk/AES?

I believe so. At least I do not remember any security related change in
the key handshake between WPA and IEEE 802.11i as far as configuring
CCMP is concerned.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jeff_sadowski  Sat Nov 12 09:50:55 2005
From: jeff_sadowski (Jeff Sadowski)
Date: Sat, 12 Nov 2005 09:50:55 -0800 (PST)
Subject: How to compile hostapd-0.4.6 and
	wpa_supplicant-0.4.6 for madwifi-ng (1314) (Kel Modderman)
Message-ID: <20051112175055.88817.qmail@web33514.mail.mud.yahoo.com>

>Message: 1
>Date: Sat, 12 Nov 2005 19:23:45 +1000
>From: Kel Modderman <kelrin at tpg.com.au>
>Subject: Re: [Madwifi-devel] Re: How to compile
>hostapd-0.4.6 and
>        wpa_supplicant-0.4.6 for madwifi-ng (1314)
>To: Jouni Malinen <jkmaline at cc.hut.fi>
>Cc: hostap at shmoo.com,
>madwifi-devel at lists.sourceforge.net
>Message-ID: <4375B4A1.50901 at tpg.com.au>
>Content-Type: text/plain; charset=ISO-8859-1;
>format=flowed
>
>Jouni Malinen wrote:
>
>>On Wed, Nov 09, 2005 at 12:14:22PM -0300, Beat
>Meier wrote:
>>
>>  
>>
>>>I send here all patches for madwifi-ng and
>wpa_supplicant-0.4.6 and 
>>>hostapd-0.4.6 together.
>>>With this patches it is possible to compile a
>working 
>>>wpa_supplicant/hostapd for madwifi-ng release
>1314.
>>>    
>>>
>>
>>Thanks again. I ended up doing this a bit
>differently so that users do
>>not need to configure madwifi-ng vs. madwifi-old
>>in .config. In other
>>words, this is selected automatically based on the
>defined ioctls. One
>>will still need to build hostapd/wpa_supplicant
>separately for
>>madwifi-ng and madwifi-old, i.e., the automatic
>detection is build 
>time
>>operation.
>>  
>>
>Hi Jouni,
>
>This is great news!
>
>However, this method has a distinct disadvantage for
>binary 
>distributions; a new wpasupplicant that works with
>madwifi-ng will not 
>be backwards compatible with users still happy with
>the old madwifi, as 
>it seems that you will support one or the other but
>not both at once.
>
>Is it too much of a burden on you to support
>multiple madwifi versions 
>at once?
>
>Suggestions on howto handle this situation for
>maintainers of 
>wpa_supplicant for various binary distributions?
>
>Thanks, Kel.
>
>
>------------------------------
Considering that the madwifi team has never realeased
"stable" (I know they work good) madwifi drivers. I
think it would be in everyones best interest to
develop for the ng version of madwifi which I still
have yet to get working even with the patches that
where provided. My card just seems to constantly
switch card modes from a to g to Ta(what is this
anyone know) in a continuous cycle. I constantly go
back to a really old version of the madwifi driver a
cvs snapshot I took in august or so and use
wpa_supplicant 0.4.5 I haven't tried 0.4.6 because
0.4.5 works good enough for me. And as I go to upgrade
my wpa_supplicant I will also want to upgrade my
madwifi driver. I REALLY WANT TO UPGRADE MY MADWIFI
DRIVER. Sorry Im getting anxious for a new one that I
can get working.


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com



From sam  Sat Nov 12 11:01:20 2005
From: sam (Sam Leffler)
Date: Sat, 12 Nov 2005 11:01:20 -0800
Subject: RSN pre-authentication environment
In-Reply-To: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
References: <699acd380511120811n5d58847as5fb9d9207666d9bc@mail.gmail.com>
Message-ID: <43763C00.7010503@errno.com>

superd wrote:
> I used hostapd 0.3.9, wpa_supplicant 0.3.9 under freebsd 6.0 to build
> my pre-authentication environment, but wpa_supplicant always tell me
> pre-authentication timed out.
> do any people success building pre-authentication environment?
> What OS, hostapd,and wpa_supplicant version do you use?

There is no support for pre-auth on freebsd; I've solicited someone to 
work on this since hostapd got committed but received no responses.

	Sam



From engage  Sat Nov 12 20:30:45 2005
From: engage (engage)
Date: Sat, 12 Nov 2005 21:30:45 -0700
Subject: RSN questions
Message-ID: <200511122130.45886.engage@n0sq.us>

I'm trying to get wpa_supplicant-0.4.5 set up for WPA2. I don't want to use a 
radius server for this. Anyway, I set up my Linksys WRT54G for WPA2-Personal 
with TKIP+AES (the other option for WPA2-Personal is AES).

Here's what I used for wpa_supplicant.conf:

#WPA2-Personal

ctrl_interface=/var/run/wpa_supplicant

network={
        ssid="??????????"
        key_mgmt=WPA-PSK
        proto=WPA2 #i tried using RSN also
        pairwise=TKIP
        group=TKIP
        psk="?????????????????????????????"
        scan_ssid=1
}

It doesn't work. iwconfig shows an AP association and an encryption key. I can 
ping the router but I can't access my DNS server or web surf. I can't ping 
anything outside my LAN. The above config file does work with proto=WPA.

I've been reading a few howto's but they have me confused and most of them are 
directed at Enterprise setups (port authentication with a radius server). And 
the only thing I've seen in the supplicant's README concerning AES is CCMP. 
If I understand correctly , CCMP is an improvement over AES and is used with 
a radius server?  I don't see any other options in the README that are 
appropriate.  Does WPA2 require something more sophisticated than TKIP or 
AES? The sample config files that I've seen have EAP in them. Like I said, 
I'm confused as to how to do this.

What am I missing?



From jkmaline  Sun Nov 13 07:17:29 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Nov 2005 07:17:29 -0800
Subject: RSN questions
In-Reply-To: <200511122130.45886.engage@n0sq.us>
References: <200511122130.45886.engage@n0sq.us>
Message-ID: <20051113151729.GA8968@jm.kir.nu>

On Sat, Nov 12, 2005 at 09:30:45PM -0700, engage wrote:

> I'm trying to get wpa_supplicant-0.4.5 set up for WPA2. I don't want to use a 
> radius server for this. Anyway, I set up my Linksys WRT54G for WPA2-Personal 
> with TKIP+AES (the other option for WPA2-Personal is AES).

What wireless LAN card and driver (including version) are you using? Do
you need TKIP with some clients? If not, setting the AP to use just CCMP
(AES) would be more secure.

> network={
>         key_mgmt=WPA-PSK
>         proto=WPA2 #i tried using RSN also
>         pairwise=TKIP
>         group=TKIP

Do you have any particular reason to limit to using TKIP for pairwise
even though the AP was configured to allow CCMP?

> It doesn't work. iwconfig shows an AP association and an encryption key. I can 
> ping the router but I can't access my DNS server or web surf. I can't ping 
> anything outside my LAN. The above config file does work with proto=WPA.

Are you saying that you can ping your AP over the wireless connection?
there shouldn't really be much difference in LAN vs. internet access.
Did you look at wpa_supplicant debug log? Did it claim that the
connection was established successfully?

> I've been reading a few howto's but they have me confused and most of them are 
> directed at Enterprise setups (port authentication with a radius server). And 
> the only thing I've seen in the supplicant's README concerning AES is CCMP. 
> If I understand correctly , CCMP is an improvement over AES and is used with 
> a radius server?

CCMP is a mode for using AES. In other words, when some devices talk
about TKIP or AES, they actually mean TKIP or CCMP..

>  I don't see any other options in the README that are 
> appropriate.  Does WPA2 require something more sophisticated than TKIP or 
> AES? The sample config files that I've seen have EAP in them. Like I said, 
> I'm confused as to how to do this.

Your configuration file looked valid, though, I would have used
pairwise=CCMP in that case. If you change the AP to be CCMP (AES) only,
both pairwise and group would be CCMP in wpa_supplicant configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov 13 08:46:36 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Nov 2005 08:46:36 -0800
Subject: [2.6 patch] rename hostap.c to hostap_main.c
In-Reply-To: <20051113162745.GM21448@stusta.de>
References: <20051106005343.GF3668@stusta.de> <20051106041543.GC8972@jm.kir.nu>
	<20051113162745.GM21448@stusta.de>
Message-ID: <20051113164636.GB8968@jm.kir.nu>

On Sun, Nov 13, 2005 at 05:27:45PM +0100, Adrian Bunk wrote:

> There's no other change.
> 
> If you agree, Jeff might be able to do the
> 
>   mv drivers/net/wireless/hostap/hostap.c \
>     drivers/net/wireless/hostap/hostap_main.c
> 
> plus applying the patch below.

OK, I'm okay with that change.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov 13 10:03:21 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Nov 2005 10:03:21 -0800
Subject: Very slow roaming or reassociation in WPA2 mode
In-Reply-To: <200511121752.42606.rob.vandermeulen@tiscali.be>
References: <200511121752.42606.rob.vandermeulen@tiscali.be>
Message-ID: <20051113180321.GC8968@jm.kir.nu>

On Sat, Nov 12, 2005 at 05:52:42PM +0100, Rob Vandermeulen wrote:

> I can connect fine with wpa_supplicant (0.4.6 version, ipw-1.0.8, ieee-1.1.6, 
> fw 2.4, kernel 2.6.13 ) using wext, and the card connects fine to the 17:80 
> AP (although the other one is much closer, a few meters from the test setup). 
> Everything is fine, an then i disable the 17:80 radio. wpa_supplicants 
> detects this very fast, and start to reassociate. This works, but takes 
> somewhere between 30s-1minute. It first has to try a few times to 
> reassociate, and when that works it just "hangs" while trying to reassociate 
> somewhere in the process...

Have you tried ap_scan=1 setting? ap_scan=2 should, at least in theory,
be a bit faster, assuming the driver has a good roaming implementation.
However, it would be interesting to see what happens with ap_scan=1.

I would also like to see a wpa_supplicant debug log with time stamps (-t
added on the command line), so that it would be easier to figure out
where the delay was. I have not yet had a chance to test this kind of
roaming case with ipw2x00 myself, but I'll try to do this is at some
point with ipw2915.

-- 
Jouni Malinen                                            PGP id EFC895FA



From throw_away_2002  Sun Nov 13 12:46:22 2005
From: throw_away_2002 (Tom)
Date: Sun, 13 Nov 2005 12:46:22 -0800 (PST)
Subject: Can't connect - looks like authentication times out
Message-ID: <20051113204622.15293.qmail@web52106.mail.yahoo.com>

Posted this a few days ago, but did not
receive any replies, so trying again.

# dog /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
        group=TKIP
        key_mgmt=WPA-PSK
        pairwise=TKIP
        proto=WPA
        psk="mypassword"
        ssid="myssid"
        }


# wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf
-iwlan0 -dd

Initializing interface 'wlan0' conf
'/etc/wpa_supplicant.conf' driver 'ndiswrapper'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=2
Line: 5 - start of a new network block
group: 0x8
key_mgmt: 0x2
pairwise: 0x8
proto: 0x1
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
ssid - hexdump_ascii(len=11):  [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='myssid'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: [REMOVED]
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Trying to associate with SSID 'myssid'
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8c07 len=87
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated to a new BSS: BSSID= [REMOVED]
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: Using WPA IE from AssocReq to set cipher suites
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Associated with [REMOVED]
EAPOL: External notification - portEnabled=0

EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00
00 00 00 00 00 00 01 4f 08 2e ef 65 b9 cf 7d 57 01 17 73 fc
b3 b8 66 20 53 d8 81
72 85 db 8f f5 4a 9a 4e a9 13 fa 1d 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89
00 20 00 00 00 00 00 00 00 01 4f 08 2e ef 65 b9 cf 7d 57 01
17 73 fc b3 b8 66 20
53 d8 81 72 85 db 8f f5 4a 9a 4e a9 13 fa 1d 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVED]
WPA: Renewed SNonce - hexdump(len=32): 67 85 36 e4 71 8a 31
de f6 97 2b b0 ca 4a 10 f8 b5 37 f6 a8 ce c9 3b 73 29 ca 2c
24 0f 7e 64 fe
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 2d d1 5b e7 07 40 4c
2c d9 9f c8 f6 08 05 7b c4
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82
00 14 a5 15 f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00
00 00 00 00 01 67 8
5 36 e4 71 8a 31 de f6 97 2b b0 ca 4a 10 f8 b5 37 f6 a8 ce
c9 3b 73 29 ca 2c 24 0f 7e 64 fe 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d d1 5b
e7 07 40 4c 2c d9 9f c8 f6 08 05 7b c4 00 18 dd 16 00 50 f2
01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0
startWhen=29 idleWhile=59
EAPOL: Port Timers tick - authWhile=0 heldWhile=0
startWhen=28 idleWhile=58
Wireless event: cmd=0x8c07 len=87
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated with [REMOVED]
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED

The last 36 (or so) lines just keep repeating
(with minor changes in the hex dumps). The
client seems to see the access point (and the
access point sees the client as an "attached
device"), but somehow authentication never
seems to take place. Can someone explain why
not?

Thank you very much in advance for your help.


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com



From engage  Sun Nov 13 13:00:45 2005
From: engage (engage)
Date: Sun, 13 Nov 2005 14:00:45 -0700
Subject: RSN questions
In-Reply-To: <1e4a094e0511130343x2cbccbe1ud44f0e282005aa4a@mail.gmail.com>
References: <200511122130.45886.engage@n0sq.us>
	<1e4a094e0511130343x2cbccbe1ud44f0e282005aa4a@mail.gmail.com>
Message-ID: <200511131400.46157.engage@n0sq.us>

CCMP wouldn't work when using proto=WPA2 but it did work with proto=WPA. I do 
get an error message when starting wpa_supplicant: ioctl[SIOCSIWPMKSA]: 
Operation not supported. I'm trying to figure out why but I'm including the 
following debug (wpa_supplicant ...... -d) output when using proto=WPA2. 
Maybe you can figure this out faster than I can:

#cat /etc/wpa_supplicant.conf
#ctrl_interface=/var/run/wpa_supplicant
#
#network={
#       ssid="??????????????????"
#       key_mgmt=WPA-PSK
#       proto=WPA2
#       pairwise=CCMP
#       group=CCMP
#       psk="???????????????????????"
#       scan_ssid=1
#}
#
#dmesg | grep ndiswrapper
#ndiswrapper version 1.5 loaded (preempt=no,smp=no)
#wlan0: ndiswrapper ethernet device 00:0f:66:6d:8d:c9 using driver bcmwl5,

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 
'default'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
   id=0 ssid='???????????'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=18 enc_capa=0xe
  capabilities: key_mgmt 0xa enc 0xf
Own MAC address: 00:0f:66:6d:8d:c9
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
     4b 49 37 52 57                                    ???????????           
Scan timeout - try to get results
Received 281 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='???????????' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
   selected
Trying to associate with 00:12:17:e2:8d:05 (SSID='???????????' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 
04 01 00 00 0f ac 02 00 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 
00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 281 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='???????????' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
   selected
Trying to associate with 00:12:17:e2:8d:05 (SSID='???????????' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 
04 01 00 00 0f ac 02 00 00
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 
00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)

On Sunday 13 November 2005 04:43 am, you wrote:
>Change the lines 2 to:
>
>pairwise=CCMP TKIP
>group=CCMP TKIP
>
>and it works :)
>
>On 11/13/05, engage <engage at n0sq.us> wrote:
>> I'm trying to get wpa_supplicant-0.4.5 set up for WPA2. I don't want to
>> use a
>> radius server for this. Anyway, I set up my Linksys WRT54G for
>> WPA2-Personal
>> with TKIP+AES (the other option for WPA2-Personal is AES).
>>
>> Here's what I used for wpa_supplicant.conf:
>>
>> #WPA2-Personal
>>
>> ctrl_interface=/var/run/wpa_supplicant
>>
>> network={
>> ssid="??????????"
>> key_mgmt=WPA-PSK
>> proto=WPA2 #i tried using RSN also
>> pairwise=TKIP
>> group=TKIP
>> psk="?????????????????????????????"
>> scan_ssid=1
>> }
>>
>> It doesn't work. iwconfig shows an AP association and an encryption key. I
>> can
>> ping the router but I can't access my DNS server or web surf. I can't ping
>> anything outside my LAN. The above config file does work with proto=WPA.
>>
>> I've been reading a few howto's but they have me confused and most of them
>> are
>> directed at Enterprise setups (port authentication with a radius server).
>> And
>> the only thing I've seen in the supplicant's README concerning AES is
>> CCMP.
>> If I understand correctly , CCMP is an improvement over AES and is used
>> with
>> a radius server? I don't see any other options in the README that are
>> appropriate. Does WPA2 require something more sophisticated than TKIP or
>> AES? The sample config files that I've seen have EAP in them. Like I said,
>> I'm confused as to how to do this.
>>
>> What am I missing?
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>
>--
>
>
>Greetz
>Theetjuh



From jjstrauss  Sun Nov 13 13:00:31 2005
From: jjstrauss (Jay Strauss)
Date: Sun, 13 Nov 2005 15:00:31 -0600
Subject: Stumpped, trying to get WPA to work on Ubuntu (Breezy)
Message-ID: <aabc51b60511131300g196e2681u2d166896f1f4a738@mail.gmail.com>

Hi,

I've had WPA working in the past, I've searched through all my old
posts to this list (as well as others).  But I'm stumpped.  Below is
how I have things configured and outputs of, what I think is relevent.
 Like in the subject, this is a fresh install of ubuntu (Breezy) on a
thinkpad A30 that I've been using to attach to a WPA access point.

I hope someone can shed some light.

Thanks
Jay

( I hope the output of my wpa_supplicant command isn't too obnoxious)

I've loaded:

apt-get wpasupplicant hostap-utils hostapd


root at ubuntu:/home/jstrauss# hostap_diag eth0
Host AP driver diagnostics information for 'eth0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.7.4 (station firmware)

root at ubuntu:/home/jstrauss# cat /etc/default/wpasupplicant | grep -v \#

ENABLED=1

OPTIONS="-w"

OPTIONS="-i eth0 -D hostap -c /etc/wpa_supplicant.conf"

root at ubuntu:/home/jstrauss# cat /etc/wpa_supplicant.conf | grep -v \#

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0

eapol_version=1
ap_scan=1
fast_reauth=1

network={
        ssid="StayOffChannelOne"
        psk=b2ccd634e188f57bc861d07733c5a510b868d5f8df4cd319bb671ae5e6fe69f9
}


root at ubuntu:/home/jstrauss# cat /etc/network/interfaces | grep -v \#

auto lo
iface lo inet loopback

mapping hotplug
        script grep
        map eth1

iface eth1 inet dhcp

auto eth0
iface eth0 inet dhcp

root at ubuntu:/home/jstrauss# wpa_supplicant -ieth0 -Dhostap
-c/etc/wpa_supplicant.conf -d 2>&1

ioctl[SIOCSIWPMKSA]: Operation not supported
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'hostap'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Priority group 0
   id=0 ssid='StayOffChannelOne'
Initializing interface (2) 'eth0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:20:e0:89:8f:e2
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 1055 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:13:10:88:68:d4 into blacklist
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 820 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:13:10:88:68:d4 blacklist count incremented to 2
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 943 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   skip - blacklisted
1: 00:12:17:f0:52:e9 ssid='comcast' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:13:10:eb:30:47 ssid='Faus2817' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:0d:72:6e:6c:41 ssid='2WIRE890' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:0f:66:3a:60:04 ssid='snowday' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
5: 00:13:10:b1:bf:f9 ssid='steve' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
6: 8a:00:33:22:9f:b9 ssid='hpsetup' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
   skip - no WPA/RSN IE
No APs found - clear blacklist and try again
Removed BSSID 00:13:10:88:68:d4 from blacklist (clear)
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:13:10:88:68:d4 into blacklist
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 943 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:13:10:88:68:d4 blacklist count incremented to 2
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 943 bytes of scan results (7 BSSes)
Scan results: 7
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   skip - blacklisted
1: 00:12:17:f0:52:e9 ssid='comcast' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:13:10:eb:30:47 ssid='Faus2817' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:0f:66:3a:60:04 ssid='snowday' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:0d:72:6e:6c:41 ssid='2WIRE890' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
5: 00:13:10:b1:bf:f9 ssid='steve' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
6: 8a:00:33:22:9f:b9 ssid='hpsetup' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
   skip - no WPA/RSN IE
No APs found - clear blacklist and try again
Removed BSSID 00:13:10:88:68:d4 from blacklist (clear)
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:13:10:88:68:d4 into blacklist
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 1125 bytes of scan results (8 BSSes)
Scan results: 8
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24
rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:13:10:88:68:d4 blacklist count incremented to 2
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added



From jjstrauss  Sun Nov 13 13:18:09 2005
From: jjstrauss (Jay Strauss)
Date: Sun, 13 Nov 2005 15:18:09 -0600
Subject: Stumpped, trying to get WPA to work on Ubuntu (Breezy)
In-Reply-To: <aabc51b60511131300g196e2681u2d166896f1f4a738@mail.gmail.com>
References: <aabc51b60511131300g196e2681u2d166896f1f4a738@mail.gmail.com>
Message-ID: <aabc51b60511131318k366f65adudf32b117274b41ff@mail.gmail.com>

A couple of more outputs I forgot:

I have no idea where the entry for eth2 is coming from in the iwconfig

Thanks
Jay

root at ubuntu:/home/jstrauss# ifconfig eth0
eth0      Link encap:UNSPEC  HWaddr 00-20-E0-89-8F-E2-00-00-00-00-00-00-00-00-00
-00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2014 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:47 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:228014 (222.6 KiB)  TX bytes:104 (104.0 b)
          Interrupt:11 Memory:d8ae0000-d8ae1000

root at ubuntu:/home/jstrauss# iwconfig
lo        no wireless extensions.

eth1      no wireless extensions.

Warning: Driver for device eth0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

eth0      IEEE 802.11b  ESSID:"StayOffChannelOne"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 44:44:44:44:44:44
          Bit Rate:11 Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

eth2      IEEE 802.11b  ESSID:"StayOffChannelOne"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 44:44:44:44:44:44
          Bit Rate:11 Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=28/70  Signal level=-67 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:494  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:577   Missed beacon:0

sit0      no wireless extensions.



From jkmaline  Sun Nov 13 14:24:21 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Nov 2005 14:24:21 -0800
Subject: Stumpped, trying to get WPA to work on Ubuntu (Breezy)
In-Reply-To: <aabc51b60511131318k366f65adudf32b117274b41ff@mail.gmail.com>
References: <aabc51b60511131300g196e2681u2d166896f1f4a738@mail.gmail.com>
	<aabc51b60511131318k366f65adudf32b117274b41ff@mail.gmail.com>
Message-ID: <20051113222421.GA8944@jm.kir.nu>

On Sun, Nov 13, 2005 at 03:18:09PM -0600, Jay Strauss wrote:

> I have no idea where the entry for eth2 is coming from in the iwconfig

If you are really using Host AP driver, someone has changed the default
interface names and if whoever did this decided to use eth0 and eth2
instead of the normally used wifi0 and wlan0, the new prefixes are
confusing at best..

If eth0 is wifi0, you should be using the other interface (maybe eth2?
something with the same MAC address). If that part is not clear, please
send 'ifconfig -a' output to show all interfaces.

In addition, renaming wifi0 and wlan0 to something else is not going to
work very well with the latest wpa_supplicant code due to filtering of
wireless events is automatically fixed for the standard interface names,
but not if something else is used.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov 13 14:28:03 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 13 Nov 2005 14:28:03 -0800
Subject: Can't connect - looks like authentication times out
In-Reply-To: <20051113204622.15293.qmail@web52106.mail.yahoo.com>
References: <20051113204622.15293.qmail@web52106.mail.yahoo.com>
Message-ID: <20051113222803.GB8944@jm.kir.nu>

On Sun, Nov 13, 2005 at 12:46:22PM -0800, Tom wrote:

> Posted this a few days ago, but did not
> receive any replies, so trying again.

I don't remember having seen your earlier message in my Host AP folder..

> # wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf
> -iwlan0 -dd

Which version of ndiswrapper and wpa_supplicant are you using?

> The last 36 (or so) lines just keep repeating
> (with minor changes in the hex dumps). The
> client seems to see the access point (and the
> access point sees the client as an "attached
> device"), but somehow authentication never
> seems to take place. Can someone explain why
> not?

Most common reason for message 1/4 being sent out repeatedly is a
mismatch in PSK (e.g., in ASCII passphrase). Either the AP is not seeing
the reply (msg 2/4) or that frame is being rejected for some reason.
What AP are you using? Can you get any event/debug log information from
it?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jjstrauss  Sun Nov 13 15:13:28 2005
From: jjstrauss (Jay Strauss)
Date: Sun, 13 Nov 2005 17:13:28 -0600
Subject: Stumpped, trying to get WPA to work on Ubuntu (Breezy)
In-Reply-To: <20051113222421.GA8944@jm.kir.nu>
References: <aabc51b60511131300g196e2681u2d166896f1f4a738@mail.gmail.com>
	<aabc51b60511131318k366f65adudf32b117274b41ff@mail.gmail.com>
	<20051113222421.GA8944@jm.kir.nu>
Message-ID: <aabc51b60511131513l68fcd6e6s4ff0d6447da9a9b7@mail.gmail.com>

Its a unadulterated install of ubuntu (kubuntu to be exact).  Last ubuntu
install had the the 'eth' names too.  I don't know why this occurres, maybe
it's a hardware thing.

In the past I've tried to change the name to wlan0 but could never figure it
out.

<the worse part> I did a fresh install yesterday, got WPA to work (somehow),
thought I better document it for the next person, reinstalled today and can't
get it to work (I must have done something, but sure can remember or figure
out what)

I did ifconfig -a and wpa_supplicant on eth2 like you asked below

Thanks
Jay

root at ubuntu:/home/jstrauss# ifconfig -a
eth0      Link encap:UNSPEC  HWaddr
00-20-E0-89-8F-E2-00-79-00-00-00-00-00-00-00-00
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2221 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:85 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:248668 (242.8 KiB)  TX bytes:2637 (2.5 KiB)
          Interrupt:11 Memory:d8ae0000-d8ae1000

eth1      Link encap:Ethernet  HWaddr 00:D0:59:83:5F:D2
          inet addr:192.168.1.119  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:59ff:fe83:5fd2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2301 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2029 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1588055 (1.5 MiB)  TX bytes:360738 (352.2 KiB)

eth2      Link encap:Ethernet  HWaddr 00:20:E0:89:8F:E2
          inet6 addr: fe80::220:e0ff:fe89:8fe2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1012 errors:0 dropped:823 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:106849 (104.3 KiB)  TX bytes:2247 (2.1 KiB)
          Interrupt:11 Memory:d8ae0000-d8ae1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3465 (3.3 KiB)  TX bytes:3465 (3.3 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


wpa_supplicant -ieth2 -Dhostap -c/etc/wpa_supplicant.conf -d

ioctl[SIOCSIWPMKSA]: Operation not supported
Initializing interface 'eth2' conf '/etc/wpa_supplicant.conf' driver 'hostap'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Priority group 0
   id=0 ssid='StayOffChannelOne'
Initializing interface (2) 'eth2'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:20:e0:89:8f:e2
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth2' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth2' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 731 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 0
0: 00:13:10:88:68:d4 ssid='StayOffChannelOne' wpa_ie_len=24 rsn_ie_len=0
caps=0x11
   selected
Trying to associate with 00:13:10:88:68:d4 (SSID='StayOffChannelOne' freq=2412
MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01
00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=30
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:88:68:d4
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:13:10:88:68:d4
No keys have been configured - skip key clearing
Associated with 00:13:10:88:68:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
RX EAPOL from 00:13:10:88:68:d4
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:13:10:88:68:d4 (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 6b 47 da 4f b0 6e 09 bd 86 86 04 fd ab
67 29 48 de d4 2d a9 8e 13 b4 64 97 94 5a 59 bc 58 d8 6f
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
RTM_NEWL



From nix.bh.tan  Sun Nov 13 16:22:56 2005
From: nix.bh.tan (nix.bh.tan at sg.pwc.com)
Date: Mon, 14 Nov 2005 08:22:56 +0800
Subject: Nix BH Tan/SG/GTS/PwC is out of the office.
Message-ID: <OFF5DB26D9.7ADEF69C-ON482570B9.00021970-482570B9.00021970@pwc.com>

I will be out of the office starting  14/11/2005 and will not return until
21/11/2005.

For assistance on network issues, please contact Tan Tiong Hwee @ 4132 .
For assistance on Lotus Notes issues, please contact Mary Heng or Kevin
Juay @ 4137 & 3671 respectively. For assistance on general issues, please
contact the GTS helpdesk @ 7000.
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.




From throw_away_2002  Sun Nov 13 18:15:38 2005
From: throw_away_2002 (Tom)
Date: Sun, 13 Nov 2005 18:15:38 -0800 (PST)
Subject: Can't connect - looks like authentication times out
In-Reply-To: <20051113222803.GB8944@jm.kir.nu>
Message-ID: <20051114021538.40065.qmail@web52107.mail.yahoo.com>

--- Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> > # wpa_supplicant -Dndiswrapper
> -c/etc/wpa_supplicant.conf
> > -iwlan0 -dd
> 
> Which version of ndiswrapper and wpa_supplicant are you
> using?

ndiswrapper 1.2
wpa_supplicant 0.3.9 (latest stable version, I believe)

> > The last 36 (or so) lines just keep repeating
> > (with minor changes in the hex dumps). The
> > client seems to see the access point (and the
> > access point sees the client as an "attached
> > device"), but somehow authentication never
> > seems to take place. Can someone explain why
> > not?
> 
> Most common reason for message 1/4 being sent out
> repeatedly is a mismatch in PSK (e.g., in ASCII
> passphrase).

Checked the value in /etc/wpa_supplicant.conf with
a dump of the netgear.cfg. They match (and I have
another device using the same passphrase that also
connects).

> What AP are you using?

Netgear WGT624.

> Can you get any event/debug log information from it?

I don't believe that it has any event logging. :(

Tom


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com



From tony  Sun Nov 13 18:51:31 2005
From: tony (Tony Jarnigan)
Date: Sun, 13 Nov 2005 20:51:31 -0600
Subject: unknown timeout using wpa_supplicant
Message-ID: <9d42e8280511131851r226cd009wb5ec3ce54ea57be8@mail.gmail.com>

On 11/9/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Wed, Nov 09, 2005 at 12:09:35PM -0600, Tony Jarnigan wrote:
>
> > My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim
> AP.
> > It connects fine but when another machine(B) on the network tries to
> ping
> > it, there's no response; no ssh or vnc either although the daemons are
> > running. It's not iptables or any other firewall software, nothing is
> > running.
> >
> > Oddly enough, if A pings B, B can connect no problem. If I discontinue
> the
> > ping, the problem seems to come up again within 2 minutes. If I turn off
> > WPA-PSK and not run wpa_supplicant, everything works as expected.
>
> That sounds like issues with multicast/broadcast receive on the host
> (A). Pinging A->B allows (B) to update its ARP table without (A) having
> to receive broadcast arp who-has request and that 2 minutes would be a
> timeout for the ARP cache.


I tried compiling the new madwifi-ng drivers and also wpa_supplicant
0.4.6but they didn't seem to work together (I didn't spend much time
debugging).
I went back to my previous madwifi drivers but used the newer wpa_supplicant
and things seem to work now. I'll certainly want madwifi-ng working in the
future but this gets me what I want.

Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051113/b0609405/attachment.htm 


From throw_away_2002  Sun Nov 13 22:58:20 2005
From: throw_away_2002 (Tom)
Date: Sun, 13 Nov 2005 22:58:20 -0800 (PST)
Subject: Can't connect - looks like authentication times out
In-Reply-To: <20051113222803.GB8944@jm.kir.nu>
Message-ID: <20051114065820.58160.qmail@web52105.mail.yahoo.com>

--- Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> Most common reason for message 1/4 being sent out repeatedly is a
> mismatch in PSK (e.g., in ASCII passphrase). Either the AP is not
> seeing the reply (msg 2/4) or that frame is being rejected for some
> reason.

Occasionally (and I don't know why), when I try to run
wpa_supplicant, I get this instead:

# wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf -iwlan0 -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
'ndiswrapper'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=2
Line: 5 - start of a new network block
group: 0x8
key_mgmt: 0x2
pairwise: 0x8
proto: 0x1
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
ssid - hexdump_ascii(len=11): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid= [REMOVED]
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: [REMOVED]
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Disconnect event - remove keys
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Trying to associate with SSID [REMOVED]
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0
idleWhile=0
Signal 15 received - terminating
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
#

Maybe this will give you more information.


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com



From stefan  Mon Nov 14 00:28:13 2005
From: stefan (Stefan Schmidt)
Date: Mon, 14 Nov 2005 09:28:13 +0100
Subject: [Patch] Do not display password in plain text wpa_gui network edit
	menu. Close #81
Message-ID: <20051114082813.GL11848@susi>

Hello.

At university we use 802.1x with EAP-TTLS to connect our wlan. The
login and password are the same as for mail, printing and everything
else. If i use wpa_supplicant and wpa_gui to connect, i have to enter
my password. But after connection is completed i can the the plaintext
password in wpa_gui edit network menu.
To correct this problem i have attached a small patch. It compiles
fine with 0.4.6 and cvs for me. This patch closes bug #81
http://hostap.epitest.fi/bugz/show_bug.cgi?id=81
The patch is only for qt3 gui, but should work with qt4 too.

regards
Stefan Schmidt
-------------- next part --------------
--- wpa_supplicant-0.4.6/wpa_gui/networkconfig.ui	2005-10-27 04:17:50.000000000 +0200
+++ wpa_supplicant-0.4.6-password-patched/wpa_gui/networkconfig.ui	2005-11-11 21:22:21.000000000 +0100
@@ -200,6 +200,9 @@
                     <property name="enabled">
                         <bool>false</bool>
                     </property>
+                    <property name="echoMode">
+                        <enum>Password</enum>
+                    </property>
                     <property name="toolTip" stdset="0">
                         <string>Password for EAP methods</string>
                     </property>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051114/e7118605/attachment.pgp 


From rob.vandermeulen  Sun Nov 13 23:52:53 2005
From: rob.vandermeulen (Rob Vandermeulen)
Date: Mon, 14 Nov 2005 08:52:53 +0100
Subject: Very slow roaming or reassociation in WPA2 mode
In-Reply-To: <20051113180321.GC8968@jm.kir.nu>
References: <200511121752.42606.rob.vandermeulen@tiscali.be>
	<20051113180321.GC8968@jm.kir.nu>
Message-ID: <200511140852.53862.rob.vandermeulen@tiscali.be>

I will try to send a timestamped log today or tomorrow. And i did try 
ap_scan=1 multiple times ( i probably tested almost every configuration 
variance there is) but it is much slower then ap_scan=2, and doesn't even 
work most of the time. The initial association always goes fine, but 
roaming/re-connecting is a problem, ap_scan=1 seems to get confused after a 
few roams/reconnects and doesn't find my network anymore, even though it's 
there (i'll try to find a log with that behaviour to make it more clear).

Kind regards
Rob Vandermeulen

PS. I already posted this to the ipw2200 dev list a weeks ago, and their 
conclusion was that it didn't seem to be a driver issue at first sight.

PS2 : My APs+ MX are supposed to support "fast reauthentication & seamless 
roaming" (vendorspeak), but information on that is very sparse (it could be 
preauthentication or keycaching or hopefully not some proprietary solution). 
wpa_supplicant seems to support preauth but very little documentation is 
available about these subjects - if anyone has more information i would 
gladly appreciate it

On Sunday 13 November 2005 19:03, Jouni Malinen wrote:
> On Sat, Nov 12, 2005 at 05:52:42PM +0100, Rob Vandermeulen wrote:
> > I can connect fine with wpa_supplicant (0.4.6 version, ipw-1.0.8,
> > ieee-1.1.6, fw 2.4, kernel 2.6.13 ) using wext, and the card connects
> > fine to the 17:80 AP (although the other one is much closer, a few meters
> > from the test setup). Everything is fine, an then i disable the 17:80
> > radio. wpa_supplicants detects this very fast, and start to reassociate.
> > This works, but takes somewhere between 30s-1minute. It first has to try
> > a few times to reassociate, and when that works it just "hangs" while
> > trying to reassociate somewhere in the process...
>
> Have you tried ap_scan=1 setting? ap_scan=2 should, at least in theory,
> be a bit faster, assuming the driver has a good roaming implementation.
> However, it would be interesting to see what happens with ap_scan=1.
>
> I would also like to see a wpa_supplicant debug log with time stamps (-t
> added on the command line), so that it would be easier to figure out
> where the delay was. I have not yet had a chance to test this kind of
> roaming case with ipw2x00 myself, but I'll try to do this is at some
> point with ipw2915.



From Karl.Rothenhoefer  Mon Nov 14 03:24:23 2005
From: Karl.Rothenhoefer (=?us-ascii?Q?Karl_Rothenhofer?=)
Date: Mon, 14 Nov 2005 12:24:23 +0100
Subject: AW: Virtual WiFi on Linux?
In-Reply-To: <loom.20051022T031151-75@post.gmane.org>
Message-ID: <000401c5e90d$f7d05740$9088fea9@Medion>

Hi,

I have been testing this with a miniPCI card from Wistron that is based on
Atheros Chipset. I have used the life CD for testing it and can confirm,
that it works. I used two different clients, which associated with different
security mechanismes.

I have not yet done any performance tests, but there was nothing exiting in
terms of remarkable degradations.





-----Ursprungliche Nachricht-----
Von: hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com
[mailto:hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com]Im
Auftrag von Wang Chen
Gesendet: Samstag, 22. Oktober 2005 03:25
An: hostap at shmoo.com
Betreff: Re: Virtual WiFi on Linux?





Dan Searle <dan <at> adelix.com> writes:
>
> Hi,
>
> Talking somewhat specifically about Madwifi here, but what I'm saying
> could be taken in a more generic sense....
<..skip..>

According to linuxdevices.com there's at least one commercial Linux
implementation of virtualwifi on atheros chipset at www.wilibox.com .  They
claim to support multiple virtual APs (multiple BSSIDs) and multiple client
mode
STA (station) connections concurrently.




_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap





From rob.vandermeulen  Mon Nov 14 03:05:51 2005
From: rob.vandermeulen (Rob Vandermeulen)
Date: Mon, 14 Nov 2005 12:05:51 +0100
Subject: Very slow roaming or reassociation in WPA2 mode
In-Reply-To: <200511140852.53862.rob.vandermeulen@tiscali.be>
References: <200511121752.42606.rob.vandermeulen@tiscali.be>
	<20051113180321.GC8968@jm.kir.nu>
	<200511140852.53862.rob.vandermeulen@tiscali.be>
Message-ID: <200511141205.51358.rob.vandermeulen@tiscali.be>

Here is a log with timestamps : 
http://www.redsoft.be/stuff/wpatimestamp (it's on a deflate enabled webserver)

To recapitulate - these are 2 dumb AP's connected to a MX (mobility exchange, 
sort of an access concentrator). I initialize roaming by switching of an AP, 
and both AP's are well within range so the client should have no RF issues 
reaching the other AP. The AP's should support some kind af fast reauth 
(keycaching or preauth, don't know), but right now a roam takes 30+ secs - in 
the logs it's here :
Nov 14 10:11:44.506653: EAPOL: startWhen --> 0
Nov 14 10:12:11.529545: EAPOL: authWhile --> 0


Btw - i replaced the company name in the logs with CORP

Hopefully this helps - if sniffer logs are needed, just ask.

Kind regards
Rob



From superd1230  Mon Nov 14 05:50:55 2005
From: superd1230 (superd)
Date: Mon, 14 Nov 2005 21:50:55 +0800
Subject: association fail in hostapd with EAP-TLS under linux
Message-ID: <699acd380511140550sf579cc5t2b16cc3d4435292d@mail.gmail.com>

I setup hostapd under linux kernel 2.6.14 and freebsd 6.0, both
hostapd.conf are the same.
when I use wpa_supplicant to associate with hostapd under freebsd
6.0,there is no problem to associate.
but an error occurs when associate with linux.
the following is the wpa_supplicant message.
is there anything I lost in linux configuration?
=======================================================
Reading configuration file 'D:\wpa/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=5):
    77 6d 6e 65 74                                    wmnet
scan_ssid=1 (0x1)
mode=0 (0x0)
proto: 0x2
key_mgmt: 0x1
auth_alg: 0x1
eap methods - hexdump(len=2): 0d 00
identity - hexdump_ascii(len=5):
    74 65 65 6d 75                                    teemu
ca_cert - hexdump_ascii(len=17):
    2e 2f 63 65 72 74 2f 63 61 63 65 72 74 2e 70 65   ./cert/cacert.pe
    6d                                                m
client_cert - hexdump_ascii(len=21):
    2e 2f 63 65 72 74 2f 63 6c 69 65 6e 74 63 65 72   ./cert/clientcer
    74 2e 70 65 6d                                    t.pem
private_key - hexdump_ascii(len=20):
    2e 2f 63 65 72 74 2f 63 6c 69 65 6e 74 6b 65 79   ./cert/clientkey
    2e 70 65 6d                                       .pem
private_key_passwd - hexdump_ascii(len=9): [REMOVED]
Priority group 0
  id=0 ssid='wmnet'
Initializing interface (2) '11b/g'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3, 1, 0, 27
NDIS: 3 adapter names found
NDIS: 3 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericDialupAdapter - Generic dialup adapter
NDIS: 1 - \Device\NPF_{A939E304-6A5C-4188-A3B7-BD041947FEA4} - 11b/g
Wireless LAN Mini PCI Adapter (Microsoft's Packet Scheduler)
NDIS: 2 - \Device\NPF_{821FDF57-AF31-4D3B-85A5-84349628F059} -
Intel(R) PRO/100 VE Network Connection (Microsoft's Packet Scheduler)
NDIS: Matched interface
'\Device\NPF_{A939E304-6A5C-4188-A3B7-BD041947FEA4}' based on
description '11b/g Wireless LAN Mini PCI Adapter (Microsoft's Packet
Scheduler) '
NDIS: Adapter description prefix '11b/g Wireless LAN Mini PCI Adapter'
OID_802_11_CAPABILITY - hexdump(len=128): 80 00 00 00 02 00 00 00 08
00 00 00 0e 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 03 00 00 00 04 00 00
00 03 00 00 00 06 00 00 00 04 00 00 00 04 00 00 00 04 00 00 00 06 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 04
00 00 00 06 00 00 00 06 00 00 00 07 00 00 00 04 00 00 00 07 00 00 00
06 00 00 00
NDIS: Driver supports OID_802_11_CAPABILITY - NoOfPMKIDs 8 NoOfAuthEncrPairs 14
NDIS: 0 - auth 0 encr 1
NDIS: 1 - auth 0 encr 0
NDIS: 2 - auth 1 encr 1
NDIS: 3 - auth 1 encr 0
NDIS: 4 - auth 3 encr 4
NDIS: 5 - auth 3 encr 6
NDIS: 6 - auth 4 encr 4
NDIS: 7 - auth 4 encr 6
NDIS: 8 - auth 0 encr 0
NDIS: 9 - auth 0 encr 0
NDIS: 10 - auth 6 encr 4
NDIS: 11 - auth 6 encr 6
NDIS: 12 - auth 7 encr 4
NDIS: 13 - auth 7 encr 6
NDIS: driver capabilities: key_mgmt 0xf enc 0xf auth 0x3
NDIS: OID_802_11_PMKID (flush) - hexdump(len=8): 08 00 00 00 00 00 00 00
Driver interface replaced interface name with
'\Device\NPF_{A939E304-6A5C-4188-A3B7-BD041947FEA4}'
Own MAC address: 00:0e:9b:4a:c5:95
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Setting scan request: 0 sec 100000 usec
Added interface \Device\NPF_{A939E304-6A5C-4188-A3B7-BD041947FEA4}
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
    77 6d 6e 65 74                                    wmnet
NDIS: turning radio on before the first scan
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 10
Selecting BSS from priority group 0
6: 00:02:2d:66:6f:f6 ssid='NTHU_CS_WLAN' wpa_ie_len=0 rsn_ie_len=0 caps=0x0
  skip - no WPA/RSN IE
7: 00:11:95:f4:cf:75 ssid='wmnet' wpa_ie_len=0 rsn_ie_len=26 caps=0x10
  selected based on RSN IE
Trying to associate with 00:11:95:f4:cf:75 (SSID='wmnet' freq=2417 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 1
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00
0f ac 04 00 0f ac 02 01 00 00 0f ac 01 01 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02
01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:11:95:f4:cf:75 prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=9): 02 00 00 05 01 00 00 05 01
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=9): 02 00 00 05 01 00 00 05 01
EAPOL: Received EAP-Packet frame
NDIS: association information - hexdump(len=139): 28 00 00 00 03 00 31
00 0a 00 00 00 00 00 00 00 23 00 00 00 28 00 00 00 07 00 31 00 00 00
01 c0 06 00 00 00 4b 00 00 00 00 05 77 6d 6e 65 74 01 04 02 04 0b 16
30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 01 01 00 01
04 82 84 0b 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDIS: ReqFixed=0x3 RespFixed=0x7 off_req=40 off_resp=75 len_req=35 len_resp=6
NDIS: Request IEs - hexdump(len=35): 00 05 77 6d 6e 65 74 01 04 02 04
0b 16 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 01 01
00
NDIS: Response IEs - hexdump(len=6): 01 04 82 84 0b 16
Association info event
req_ies - hexdump(len=35): 00 05 77 6d 6e 65 74 01 04 02 04 0b 16 30
14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 01 01 00
resp_ies - hexdump(len=6): 01 04 82 84 0b 16
WPA: set own WPA/RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01
00 00 0f ac 04 01 00 00 0f ac 01 01 00
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:11:95:f4:cf:75
No keys have been configured - skip key clearing
Associated with 00:11:95:f4:cf:75
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL - hexdump(len=4): 01 01 00 00
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=9): 02 00 00 05 01 01 00 05 01
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=1
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=5):
    74 65 65 6d 75                                    teemu
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=14): 01 00 00 0a 02 01 00 0a 01 74 65 65 6d 75
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=9): 02 00 00 05 01 01 00 05 01
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=1
EAP: EAP entering state RETRANSMIT
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=14): 01 00 00 0a 02 01 00 0a 01 74 65 65 6d 75
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=10): 02 00 00 06 01 02 00 06 0d 20
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=2
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (13, TLS)
TLS: Trusted root certificate(s) loaded
OpenSSL: SSL_use_certificate_ASN1 failed:
error:00000000:lib(0):func(0):reason(0)
OpenSSL: SSL_use_certificate_file (DER) failed: error:0D0680A8:asn1
encoding routines:ASN1_CHECK_TLEN:wrong tag
OpenSSL: SSL_use_certificate_file (PEM) --> OK
OpenSSL: SSL_use_PrivateKey_File (DER) failed: error:0D094068:asn1
encoding routines:d2i_ASN1_SET:bad tag
OpenSSL: SSL_use_PrivateKey_File (PEM) --> OK
SSL: Private key loaded successfully
CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
EAP: EAP entering state METHOD
SSL: Received packet(len=6) - Flags 0x20
EAP-TLS: Start
SSL: (where=0x10 ret=0x1)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:before/connect initialization
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client hello A
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read server hello A
SSL: SSL_connect - want more data
SSL: 100 bytes pending from ssl_out
SSL: 100 bytes left to be sent out (of total 100 bytes)
EAP: method process -> ignore=FALSE methodState=CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=110): 01 00 00 6a 02 02 00 6a 0d 00 16 03 01 00
5f 01 00 00 5b 03 01 43 78 8c ae f9 03 77 93 32 91 f1 fa 41 4a dc 43
a4 78 fe 2f c3 99 3d 0b 34 4e dd ba 11 d0 ee 34 00 00 34 00 39 00 38
00 35 00 16 00 13 00 0a 00 33 00 32 00 2f 00 66 00 05 00 04 00 63 00
62 00 61 00 15 00 12 00 09 00 65 00 64 00 60 00 14 00 11 00 08 00 06
00 03 01 00
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=10): 02 00 00 06 01 02 00 06 0d 20
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=2
EAP: EAP entering state RETRANSMIT
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=110): 01 00 00 6a 02 02 00 6a 0d 00 16 03 01 00
5f 01 00 00 5b 03 01 43 78 8c ae f9 03 77 93 32 91 f1 fa 41 4a dc 43
a4 78 fe 2f c3 99 3d 0b 34 4e dd ba 11 d0 ee 34 00 00 34 00 39 00 38
00 35 00 16 00 13 00 0a 00 33 00 32 00 2f 00 66 00 05 00 04 00 63 00
62 00 61 00 15 00 12 00 09 00 65 00 64 00 60 00 14 00 11 00 08 00 06
00 03 01 00
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=1038): 02 00 04 0a 01 03 04 0a 0d c0 00 00 07
af 16 03 01 00 4a 02 00 00 46 03 01 43 78 8d 6b 64 a3 b7 88 96 3d 13
0e f7 cd 79 b8 fc 44 79 68 7c 39 60 ad 46 7b ae db 5a c2 30 1f 20 78
c4 9e 28 28 97 02 26 2e 7b e3 5e d3 2a 31 d1 3f e7 55 d5 4b 17 5f 19
b5 5e 46 99 8c 14 5c 88 00 35 00 16 03 01 06 cf 0b 00 06 cb 00 06 c8
00 03 78 30 82 03 74 30 82 02 dd a0 03 02 01 02 02 09 00 cb 5a 66 42
9e 8e 78 88 30 0d 06 09 2a 86 48 86 f7 0d 01 01 04 05 00 30 76 31 0b
30 09 06 03 55 04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54
57 31 0b 30 09 06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a
13 04 6e 74 68 75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d
06 03 55 04 03 13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86
f7 0d 01 09 01 16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72
67 30 1e 17 0d 30 35 31 30 32 31 31 37 34 37 32 31 5a 17 0d 30 36 31
30 32 31 31 37 34 37 32 31 5a 30 77 31 0b 30 09 06 03 55 04 06 13 02
54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30 09 06 03 55 04
07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74 68 75 31 0d 30
0b 06 03 55 04 0b 13 04 6e 74 68 75 31 0b 30 09 06 03 55 04 03 13 02
63 73 31 23 30 21 06 09 2a 86 48 86 f7 0d 01 09 01 16 14 73 75 70 65
72 64 31 32 33 30 40 67 6d 61 69 6c 2e 63 6f 6d 30 81 9f 30 0d 06 09
2a 86 48 86 f7 0d 01 01 01 05 00 03 81 8d 00 30 81 89 02 81 81 00 e5
65 cd c8 0f 39 e4 f3 48 cd 12 78 bb 74 81 e7 a5 04 5d e9 8a 0b 8e 57
b2 08 ad 29 72 42 b6 54 8b 27 4e d0 65 09 dd 10 c1 12 2a f0 98 a9 ac
c5 2a 8c a4 19 bb f7 b3 e1 56 ee 07 95 c0 3e 32 00 45 81 1a a0 41 85
4e d4 80 93 99 35 fb 25 49 32 36 5b 22 63 04 09 86 c5 4e bb cb ac d4
ef 37 44 5e 51 c6 68 cc 3a f4 a9 c9 d9 4a 97 fc 82 b5 4a c0 d8 81 22
5f f1 54 27 63 be 8b 60 bb 04 c0 bf 02 03 01 00 01 a3 82 01 07 30 82
01 03 30 09 06 03 55 1d 13 04 02 30 00 30 2c 06 09 60 86 48 01 86 f8
42 01 0d 04 1f 16 1d 4f 70 65 6e 53 53 4c 20 47 65 6e 65 72 61 74 65
64 20 43 65 72 74 69 66 69 63 61 74 65 30 1d 06 03 55 1d 0e 04 16 04
14 b0 af 4c 2e 91 9e 2b f1 73 f2 ee f1 f6 3f 0a 4f 84 bf 1a 2e 30 81
a8 06 03 55 1d 23 04 81 a0 30 81 9d 80 14 9a d5 5c f5 31 1b ce 41 62
d2 dd 0e ec 4d 58 d0 7d 16 36 e4 a1 7a a4 78 30 76 31 0b 30 09 06 03
55 04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30
09 06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74
68 75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d 06 03 55 04
03 13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86 f7 0d 01 09
01 16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72 67 82 09 00
cb 5a 66 42 9e 8e 78 86 30 0d 06 09 2a 86 48 86 f7 0d 01 01 04 05 00
03 81 81 00 4c 06 fa 0e 37 1d 89 31 96 29 fd e0 18 4b d2 ba ef e2 4c
b5 62 cb a1 5f 6b bc 30 79 c3 de e6 73 9e 67 6a 27 53 41 3b 76 c3 07
f8 33 46 20 55 87 ea 64 d7 f5 44 4d 83 4e 45 14 f6 ea 92 95 67 c8 66
ab 8b 97 cd af fa 65 83 62 3a cd 55 4a 1a 09 7b 75 78 d0 7d 52 be e3
a3 c3 5d 4c 04 b7 c8 24 a9 5c 29 b4 56 4c 7d 32 e1 a6 3d 16 7d b9 ce
64 94 d1 ea 89 b1 0c 3f 59 e4 70 91 44 f3 6e ec 66 00 03 4a 30 82 03
46 30 82 02 af a0 03 02 01 02 02 09 00 cb 5a 66 42 9e 8e 78 86 30 0d
06 09 2a 86 48 86 f7 0d 01 01 04 05 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=3
EAP: EAP entering state METHOD
SSL: Received packet(len=1034) - Flags 0xc0
SSL: TLS Message Length: 1967
SSL: Need 943 bytes more input data
SSL: Building ACK
EAP: method process -> ignore=FALSE methodState=CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=10): 01 00 00 06 02 03 00 06 0d 00
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=1038): 02 00 04 0a 01 03 04 0a 0d c0 00 00 07
af 16 03 01 00 4a 02 00 00 46 03 01 43 78 8d 6b 9d 93 4f f1 17 9c d8
cc 0c b7 8a a3 47 28 cf 07 82 09 96 a1 7b a7 44 9c 02 08 7c a8 20 9f
45 ad b3 fa 8d 48 d3 c4 44 20 50 c8 f1 3b a3 77 f6 d9 18 85 6b 0a 75
12 0f d2 23 60 bf 1c c5 00 35 00 16 03 01 06 cf 0b 00 06 cb 00 06 c8
00 03 78 30 82 03 74 30 82 02 dd a0 03 02 01 02 02 09 00 cb 5a 66 42
9e 8e 78 88 30 0d 06 09 2a 86 48 86 f7 0d 01 01 04 05 00 30 76 31 0b
30 09 06 03 55 04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54
57 31 0b 30 09 06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a
13 04 6e 74 68 75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d
06 03 55 04 03 13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86
f7 0d 01 09 01 16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72
67 30 1e 17 0d 30 35 31 30 32 31 31 37 34 37 32 31 5a 17 0d 30 36 31
30 32 31 31 37 34 37 32 31 5a 30 77 31 0b 30 09 06 03 55 04 06 13 02
54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30 09 06 03 55 04
07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74 68 75 31 0d 30
0b 06 03 55 04 0b 13 04 6e 74 68 75 31 0b 30 09 06 03 55 04 03 13 02
63 73 31 23 30 21 06 09 2a 86 48 86 f7 0d 01 09 01 16 14 73 75 70 65
72 64 31 32 33 30 40 67 6d 61 69 6c 2e 63 6f 6d 30 81 9f 30 0d 06 09
2a 86 48 86 f7 0d 01 01 01 05 00 03 81 8d 00 30 81 89 02 81 81 00 e5
65 cd c8 0f 39 e4 f3 48 cd 12 78 bb 74 81 e7 a5 04 5d e9 8a 0b 8e 57
b2 08 ad 29 72 42 b6 54 8b 27 4e d0 65 09 dd 10 c1 12 2a f0 98 a9 ac
c5 2a 8c a4 19 bb f7 b3 e1 56 ee 07 95 c0 3e 32 00 45 81 1a a0 41 85
4e d4 80 93 99 35 fb 25 49 32 36 5b 22 63 04 09 86 c5 4e bb cb ac d4
ef 37 44 5e 51 c6 68 cc 3a f4 a9 c9 d9 4a 97 fc 82 b5 4a c0 d8 81 22
5f f1 54 27 63 be 8b 60 bb 04 c0 bf 02 03 01 00 01 a3 82 01 07 30 82
01 03 30 09 06 03 55 1d 13 04 02 30 00 30 2c 06 09 60 86 48 01 86 f8
42 01 0d 04 1f 16 1d 4f 70 65 6e 53 53 4c 20 47 65 6e 65 72 61 74 65
64 20 43 65 72 74 69 66 69 63 61 74 65 30 1d 06 03 55 1d 0e 04 16 04
14 b0 af 4c 2e 91 9e 2b f1 73 f2 ee f1 f6 3f 0a 4f 84 bf 1a 2e 30 81
a8 06 03 55 1d 23 04 81 a0 30 81 9d 80 14 9a d5 5c f5 31 1b ce 41 62
d2 dd 0e ec 4d 58 d0 7d 16 36 e4 a1 7a a4 78 30 76 31 0b 30 09 06 03
55 04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30
09 06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74
68 75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d 06 03 55 04
03 13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86 f7 0d 01 09
01 16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72 67 82 09 00
cb 5a 66 42 9e 8e 78 86 30 0d 06 09 2a 86 48 86 f7 0d 01 01 04 05 00
03 81 81 00 4c 06 fa 0e 37 1d 89 31 96 29 fd e0 18 4b d2 ba ef e2 4c
b5 62 cb a1 5f 6b bc 30 79 c3 de e6 73 9e 67 6a 27 53 41 3b 76 c3 07
f8 33 46 20 55 87 ea 64 d7 f5 44 4d 83 4e 45 14 f6 ea 92 95 67 c8 66
ab 8b 97 cd af fa 65 83 62 3a cd 55 4a 1a 09 7b 75 78 d0 7d 52 be e3
a3 c3 5d 4c 04 b7 c8 24 a9 5c 29 b4 56 4c 7d 32 e1 a6 3d 16 7d b9 ce
64 94 d1 ea 89 b1 0c 3f 59 e4 70 91 44 f3 6e ec 66 00 03 4a 30 82 03
46 30 82 02 af a0 03 02 01 02 02 09 00 cb 5a 66 42 9e 8e 78 86 30 0d
06 09 2a 86 48 86 f7 0d 01 01 04 05 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=3
EAP: AS used the same Id again, but EAP packets were not identical
EAP: workaround - assume this is not a duplicate packet
EAP: EAP entering state METHOD
SSL: Received packet(len=1034) - Flags 0xc0
SSL: TLS Message Length: 1967
SSL: more data than TLS message length indicated
EAP-TLS: TLS processing failed
SSL: Building ACK
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=10): 01 00 00 06 02 03 00 06 0d 00
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:11:95:f4:cf:75
RX EAPOL - hexdump(len=957): 02 00 03 b9 01 04 03 b9 0d 80 00 00 07 af
30 76 31 0b 30 09 06 03 55 04 06 13 02 54 57 31 0b 30 09 06 03 55 04
08 13 02 54 57 31 0b 30 09 06 03 55 04 07 13 02 48 43 31 0d 30 0b 06
03 55 04 0a 13 04 6e 74 68 75 31 0b 30 09 06 03 55 04 0b 13 02 63 73
31 0f 30 0d 06 03 55 04 03 13 06 73 75 70 65 72 64 31 20 30 1e 06 09
2a 86 48 86 f7 0d 01 09 01 16 11 73 75 70 65 72 64 40 73 75 70 65 72
64 2e 6f 72 67 30 1e 17 0d 30 35 31 30 32 31 31 37 34 36 31 34 5a 17
0d 30 37 31 30 32 31 31 37 34 36 31 34 5a 30 76 31 0b 30 09 06 03 55
04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30 09
06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74 68
75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d 06 03 55 04 03
13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86 f7 0d 01 09 01
16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72 67 30 81 9f 30
0d 06 09 2a 86 48 86 f7 0d 01 01 01 05 00 03 81 8d 00 30 81 89 02 81
81 00 af 24 f9 a4 15 5f 5c a4 db 43 ba 29 3d 28 8f 40 98 3a bd e5 44
34 02 57 43 24 5e 80 f7 f5 5e b5 23 dc 63 35 16 b1 57 d2 50 01 91 0c
e2 e3 92 8d 5b 09 78 12 a8 43 d4 1d ca a5 34 73 03 8f ee 54 d5 a7 08
8a 69 1b 62 a5 b4 49 22 cb 94 d3 a6 d0 99 f5 67 4d 5a 99 47 c2 e9 cf
ee fb 22 9f bf 1b 5f cd 14 ec 23 27 4e 4e 9d 50 2d 10 a4 82 42 9f c7
c7 01 eb 24 e5 75 b5 62 8a 28 62 3f 9e 4d 93 02 03 01 00 01 a3 81 db
30 81 d8 30 1d 06 03 55 1d 0e 04 16 04 14 9a d5 5c f5 31 1b ce 41 62
d2 dd 0e ec 4d 58 d0 7d 16 36 e4 30 81 a8 06 03 55 1d 23 04 81 a0 30
81 9d 80 14 9a d5 5c f5 31 1b ce 41 62 d2 dd 0e ec 4d 58 d0 7d 16 36
e4 a1 7a a4 78 30 76 31 0b 30 09 06 03 55 04 06 13 02 54 57 31 0b 30
09 06 03 55 04 08 13 02 54 57 31 0b 30 09 06 03 55 04 07 13 02 48 43
31 0d 30 0b 06 03 55 04 0a 13 04 6e 74 68 75 31 0b 30 09 06 03 55 04
0b 13 02 63 73 31 0f 30 0d 06 03 55 04 03 13 06 73 75 70 65 72 64 31
20 30 1e 06 09 2a 86 48 86 f7 0d 01 09 01 16 11 73 75 70 65 72 64 40
73 75 70 65 72 64 2e 6f 72 67 82 09 00 cb 5a 66 42 9e 8e 78 86 30 0c
06 03 55 1d 13 04 05 30 03 01 01 ff 30 0d 06 09 2a 86 48 86 f7 0d 01
01 04 05 00 03 81 81 00 0c 83 5f 17 7c bb a4 9a 8a f7 51 68 93 c3 8e
76 76 41 4e 7c c9 b6 1f e6 9f 41 fc ea fd 80 11 9d 2d 0f 12 22 94 0e
a8 7c 15 87 77 e5 04 42 7f a8 63 07 0f 34 9d 04 1f 1f 6e 91 f9 2c dd
e8 ea 05 20 aa 60 27 da e4 ed c6 7d 95 b1 96 08 84 76 54 db cf 24 05
56 92 10 20 00 c0 c9 66 18 d4 a3 4f a8 24 71 e5 7d 21 d7 15 df e3 29
11 bf 28 03 52 4b 08 85 c6 f9 de 65 50 a8 5b d0 f9 0e 5a e9 7d 16 03
01 00 87 0d 00 00 7f 02 01 02 00 7a 00 78 30 76 31 0b 30 09 06 03 55
04 06 13 02 54 57 31 0b 30 09 06 03 55 04 08 13 02 54 57 31 0b 30 09
06 03 55 04 07 13 02 48 43 31 0d 30 0b 06 03 55 04 0a 13 04 6e 74 68
75 31 0b 30 09 06 03 55 04 0b 13 02 63 73 31 0f 30 0d 06 03 55 04 03
13 06 73 75 70 65 72 64 31 20 30 1e 06 09 2a 86 48 86 f7 0d 01 09 01
16 11 73 75 70 65 72 64 40 73 75 70 65 72 64 2e 6f 72 67 0e 00 00 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=4
EAP: EAP entering state METHOD
SSL: Received packet(len=953) - Flags 0x80
SSL: TLS Message Length: 1967
SSL: Need 1024 bytes more input data
SSL: Building ACK
EAP: method process -> ignore=FALSE methodState=CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=10): 01 00 00 06 02 04 00 06 0d 00
EAPOL: SUPP_BE entering state RECEIVE
....loop and loop



From m  Mon Nov 14 05:52:49 2005
From: m (Matthias Lemke)
Date: Mon, 14 Nov 2005 14:52:49 +0100
Subject: wpa-psk with hostap problem to associate
In-Reply-To: <20051113211659.66067564196@mail.iocaine.com>
References: <20051113211659.66067564196@mail.iocaine.com>
Message-ID: <437896B1.8090407@box.li>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Message: 1
> Date: Sat, 12 Nov 2005 09:22:05 -0800
> From: Jouni Malinen <jkmaline at cc.hut.fi>
> Subject: Re: wpa-psk with hostap problem to associate
> To: hostap at shmoo.com
> Message-ID: <20051112172205.GD9439 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
> 
> On Fri, Nov 11, 2005 at 03:29:39PM +0100, Matthias Lemke wrote:
> 
>>Kernel is 2.6.14
> 
> 
> Linux 2.6.14 changes some of the wireless extensions events in
> uncompatible way and wpa_supplicant 0.3.8 does not have matching
> changes. You will either need to update to the current 0.3.x snapshot or
> to the latest 0.4.x version to work with Linux 2.6.14.
> 
> 
>>IWEVGENIE overflow
> 
> 
> This is caused by the difference in Linux 2.6.14 (WE-19) events.
> 

latest devel. works very well on my zaurus now.
thanks!

math
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDeJaxpmSFPkdbqigRAiAxAKCE1T52V1fxV5bStRns/zvUaW3/TACfVcFw
PMg52+MXT7A3/gzLaJDE5/g=
=U6M5
-----END PGP SIGNATURE-----



From asattari  Mon Nov 14 17:48:19 2005
From: asattari (Afsaneh Sattari)
Date: Mon, 14 Nov 2005 20:48:19 -0500
Subject: Can not read signal quality and level with Syslink PCMCIA using Host
	Ap , and mode Master
References: <000401c5e90d$f7d05740$9088fea9@Medion>
Message-ID: <43793E63.807@site.uottawa.ca>


Hello,

Is there anyway without upgrading the driver from version 14 to 15, and 
I will be able to read the quality of link and level for my Syslink card 
, using Host Ap. I need that this pc works as an Accesspoint, so I have 
to set the mode Master, but can not get some iwconfig info like sugnal 
quality and ...

Thanks for any help or suggestions

Afsaneh





From asattari  Mon Nov 14 17:50:54 2005
From: asattari (Afsaneh Sattari)
Date: Mon, 14 Nov 2005 20:50:54 -0500
Subject: Can not read signal quality and level with Syslink PCMCIA using
	Host Ap , and mode Master
References: <000401c5e90d$f7d05740$9088fea9@Medion>
	<43793E63.807@site.uottawa.ca>
Message-ID: <43793EFE.702@site.uottawa.ca>

Some more info, I am using linux redhat 9, kernel version 2.4.20

Afsaneh Sattari wrote:

>
> Hello,
>
> Is there anyway without upgrading the driver from version 14 to 15, 
> and I will be able to read the quality of link and level for my 
> Syslink card , using Host Ap. I need that this pc works as an 
> Accesspoint, so I have to set the mode Master, but can not get some 
> iwconfig info like sugnal quality and ...
>
> Thanks for any help or suggestions
>
> Afsaneh
>
>





From sunny.tired  Mon Nov 14 18:50:03 2005
From: sunny.tired (sunny sunny)
Date: Mon, 14 Nov 2005 20:50:03 -0600
Subject: Making AP quite for some time
Message-ID: <8171b6160511141850o44e82811tef423ee566d01c93@mail.gmail.com>

Hi,

I tried to search this but could not come to a definite conclusion.

This is my problem,

I have a hostAP interface in Master mode on which some clients are
associated. I want to transmit about 27 packets (takes about 300 msecs) from
a hostAP interface (in master mode) at a reduced power level. After this the
hostAP should be able to resume its normal AP operation. I want to avoid any
unnecessary handoff during this time.


>From the web here are some conclusions I have drawn,
1. I would have to somehow disable beacons transmissions during this time,
so that the clients do not get disassociated.
2. The clients would have to be informed that the AP is temporarily
unavailable (probably some kind of a power down mode)?


Kindly help. Thanks in advance.
Santosh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051114/dde07990/attachment.htm 


From hancockr  Mon Nov 14 20:01:49 2005
From: hancockr (Robert Hancock)
Date: Mon, 14 Nov 2005 22:01:49 -0600
Subject: wpa_supplicant 0.4.6 not working on ipw2200 with 2.6.14
Message-ID: <43795DAD.5050700@shaw.ca>

I am having trouble with wpa_supplicant 0.4.6 with the 2.6.14 kernel 
under Fedora Core 4 with ipw2200 1.0.8 and ieee80211 1.1.6. Under 2.6.13 
it worked fine with the same driver versions.

wpa_supplicant is set to use the "wext" driver. When wpa_supplicant 
starts up, I get some of these:

ioctl[SIOCSIWENCODEEXT]: Invalid argument

and then

WPA: Installing PTK to the driver.
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
Driver did not support SIOCSIWENCODEEXT
WPA: Failed to set PTK to the driver.
EAPOL: External notification - portValid=1
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RSN: received GTK in pairwise handshake - hexdump(len=34): [REMOVED]
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 3e 4b 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=1 set_tx=0 seq_len=6 key_len=32
Driver did not support SIOCSIWENCODEEXT
WPA: Failed to set GTK to the driver.
RSN: Failed to install GTK
RSN: Failed to configure GTK

Any ideas?



From hancockr  Mon Nov 14 21:09:36 2005
From: hancockr (Robert Hancock)
Date: Mon, 14 Nov 2005 23:09:36 -0600
Subject: wpa_supplicant 0.4.6 not working on ipw2200 with 2.6.14
In-Reply-To: <126dcc3c0511142026p14836b80i5cbdbfa219ef3c18@mail.gmail.com>
References: <43795DAD.5050700@shaw.ca>
	<126dcc3c0511142026p14836b80i5cbdbfa219ef3c18@mail.gmail.com>
Message-ID: <43796D90.8010801@shaw.ca>

Osho GG wrote:
> When you installed ieee80211, did you make sure that all previous 
> modules in /lib/modules/ were deleted. I found that they were not and 
> then it was not working. I had to manually do something like
> 
> find /lib/modules/<kernel-version>/ -iname "*ieee80211*" -print
> 
> For each of the files found in this manner. I deleted them and then do 
> make install in ieee80211-1.1.6.

Indeed that was it, thanks.. I suppose I should have noticed that error 
about ieee80211_crypt_tkip failing to load :-)

I think I will report that as a bug to the ipw2200/ieee80211 people 
though.. the "make install" for those should handle the case where there 
are already modules in /lib/modules. It seems that if you do "make 
install" it does nothing in that case. I had to copy the modules in 
manually but I must have messed something up the first time..



From proski  Mon Nov 14 23:12:02 2005
From: proski (Pavel Roskin)
Date: Tue, 15 Nov 2005 02:12:02 -0500
Subject: [PATCH] hostap: allow flash download in kernel configuration
Message-ID: <1132038722.3512.4.camel@dv>

Flash firmware download in Host AP is actually stable enough for general
use.  Allow enabling it in the kernel configuration.

Signed-off-by: Pavel Roskin <proski at gnu.org>

diff --git a/drivers/net/wireless/hostap/Kconfig b/drivers/net/wireless/hostap/Kconfig
index 56f41c7..1bba21c 100644
--- a/drivers/net/wireless/hostap/Kconfig
+++ b/drivers/net/wireless/hostap/Kconfig
@@ -26,8 +26,21 @@ config HOSTAP_FIRMWARE
 	depends on HOSTAP
 	---help---
 	Configure Host AP driver to include support for firmware image
-	download. Current version supports only downloading to volatile, i.e.,
-	RAM memory. Flash upgrade is not yet supported.
+	download. This option by itself only enables downloading to
+	volatile memory, i.e. RAM. This option is required to support
+	cards that don't have firmware in flash, such as D-Link DWL-520
+	rev E and D-Link DWL-650 rev P.
+
+	Firmware image downloading needs user space tool, prism2_srec. It is
+	available from http://hostap.epitest.fi/.
+
+config HOSTAP_FIRMWARE_NVRAM
+	bool "Support for non-volatile firmware download"
+	depends on HOSTAP_FIRMWARE
+	---help---
+	Allow Host AP to write firmware images to non-volatile flash memory,
+	i.e. card memory that survives power cycling. Enable this option if
+	you want to be able to change card firmware permanently.
 
 	Firmware image downloading needs user space tool, prism2_srec. It is
 	available from http://hostap.epitest.fi/.
diff --git a/drivers/net/wireless/hostap/hostap_config.h b/drivers/net/wireless/hostap/hostap_config.h
index 7ed3425..cead232 100644
--- a/drivers/net/wireless/hostap/hostap_config.h
+++ b/drivers/net/wireless/hostap/hostap_config.h
@@ -31,6 +31,12 @@
 /* #define PRISM2_NON_VOLATILE_DOWNLOAD */
 #endif /* PRISM2_DOWNLOAD_SUPPORT */
 
+/* Allow kernel configuration to enable non-volatile download support. */
+#if !defined(PRISM2_NON_VOLATILE_DOWNLOAD) && \
+    defined(CONFIG_HOSTAP_FIRMWARE_NVRAM)
+#define PRISM2_NON_VOLATILE_DOWNLOAD
+#endif
+
 /* Save low-level I/O for debugging. This should not be enabled in normal use.
  */
 /* #define PRISM2_IO_DEBUG */


-- 
Regards,
Pavel Roskin




From garat  Mon Nov 14 23:29:39 2005
From: garat (Svata Dedic)
Date: Tue, 15 Nov 2005 08:29:39 +0100
Subject: Change AP BSSID / MAC
Message-ID: <43798E63.1000302@volny.cz>

Hi,

a quick question, how can I alter the BSSID / MAC of the wireless card
that my AP is running on ? I am using ZCOM XI-626 hardware, hostap_pci
driver.

Thanks for advice,
-Svata



From oshogg  Mon Nov 14 23:50:08 2005
From: oshogg (Osho GG)
Date: Mon, 14 Nov 2005 23:50:08 -0800
Subject: wpa_supplicant 0.4.6 not working on ipw2200 with 2.6.14
In-Reply-To: <43796D90.8010801@shaw.ca>
References: <43795DAD.5050700@shaw.ca>
	<126dcc3c0511142026p14836b80i5cbdbfa219ef3c18@mail.gmail.com>
	<43796D90.8010801@shaw.ca>
Message-ID: <126dcc3c0511142350s7c26149aj24740efa921ebf81@mail.gmail.com>

I think if you do make check_old in ieee80211-1.1.6 it is supposed to find
all the old ieee80211 files in /lib/modules/... and delete them but it does
not actually do that...

Osho

On 11/14/05, Robert Hancock <hancockr at shaw.ca> wrote:
>
> Osho GG wrote:
> > When you installed ieee80211, did you make sure that all previous
> > modules in /lib/modules/ were deleted. I found that they were not and
> > then it was not working. I had to manually do something like
> >
> > find /lib/modules/<kernel-version>/ -iname "*ieee80211*" -print
> >
> > For each of the files found in this manner. I deleted them and then do
> > make install in ieee80211-1.1.6.
>
> Indeed that was it, thanks.. I suppose I should have noticed that error
> about ieee80211_crypt_tkip failing to load :-)
>
> I think I will report that as a bug to the ipw2200/ieee80211 people
> though.. the "make install" for those should handle the case where there
> are already modules in /lib/modules. It seems that if you do "make
> install" it does nothing in that case. I had to copy the modules in
> manually but I must have messed something up the first time..
>



--
Osho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051114/b05d392a/attachment.htm 


From oshogg  Tue Nov 15 00:23:39 2005
From: oshogg (Osho GG)
Date: Tue, 15 Nov 2005 00:23:39 -0800
Subject: newbie questions about wpa_supplicant
In-Reply-To: <20051112164622.GB9439@jm.kir.nu>
References: <126dcc3c0511111552q1ad8b904j9e2664c3fc3b12bb@mail.gmail.com>
	<20051112164622.GB9439@jm.kir.nu>
Message-ID: <126dcc3c0511150023l3cd4b4d9h39d7646a92aa325c@mail.gmail.com>

Many many thanks Jouni for your detailed response. It has helped me a great
deal in getting closer to "network interfaces just work no matter where I
am" ... I am still not quite there yet but I feel that it is possible with
some scripting.

By the way, my wired interface does not use any authentication. Normally, I
just plug the cable in and do dhcpcd eth1 and it starts working. Can I still
use wpa_supplicant for it?

My other question is regarding dhcpcd. Currently my scripts do dhcpcd -k
<interface> whenever wpa_supplicant indicates that the interface has been
disconnected and then I do dhcpcd <interface> whenever it is connected. Is
there a better way than "kill, restart" dhcpcd like that? I am using
2.0version of dhcpcd and its manpage mentions about using the -o
option with
wpa_supplicant, ifplugd etc. but I am not sure how exactly it should be
used. Any advise?

thanks,
Osho

On 11/12/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Fri, Nov 11, 2005 at 03:52:33PM -0800, Osho GG wrote:
>
> > My question concerns regarding starting of dhcpcd. Everytime I have to
> > manually start the dhcpcd once wpa_supplicant establishes the connection
> > with the Access point. Is there a way wpa_supplicant can do it
> > automatically?
>
> Yes, or well, to be more exact, wpa_supplicant can be used to generate
> an event when network connection is established and an external program
> would be used to do whatever network configuration is needed. I believe
> some Linux distributions have already done this kind of integration.
>
> I added following description into the README file on how to do this
> with wpa_cli:
>
> wpa_cli can used to run external programs whenever wpa_supplicant
> connects or disconnects from a network. This can be used, e.g., to
> update network configuration and/or trigget DHCP client to update IP
> addresses, etc.
>
> One wpa_cli process in "action" mode needs to be started for each
> interface. For example, the following command starts wpa_cli for the
> default ingterface (-i can be used to select the interface in case of
> more than one interface being used at the same time):
>
> wpa_cli -a/sbin/wpa_action.sh -B
>
> The action file (-a option, /sbin/wpa_action.sh in this example) will
> be executed whenever wpa_supplicant completes authentication (connect
> event) or detects disconnection). The action script will be called
> with two command line arguments: interface name and event (CONNECTED
> or DISCONNECTED). If the action script needs to get more information
> about the current network, it can use 'wpa_cli status' to query
> wpa_supplicant for more information.
>
> Following example can be used as a simple template for an action
> script:
>
> #!/bin/sh
>
> IFNAME=$1
> CMD=$2
>
> if [ "$CMD" == "CONNECTED" ]; then
> SSID=`wpa_cli -i$IFNAME status | grep ^ssid= | cut -f2- -d=`
> # configure network, signal DHCP client, etc.
> fi
>
> if [ "$CMD" == "DISCONNECTED" ]; then
> # remove network configuration, if needed
> fi
>
>
> > My other question is can wpa_supplicant handle wired interfaces?
>
> Yes, driver_wired.c (-Dwired on command line) can be used to
> authenticate wired interfaces with IEEE 802.1X. Example from README:
>
> 6) Authentication for wired Ethernet. This can be used with 'wired'
> interface
> (-Dwired on command line).
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
> ap_scan=0
> network={
> key_mgmt=IEEE8021X
> eap=MD5
> identity="user"
> password="password"
> eapol_flags=0
> }
>
> --
> Jouni Malinen PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



--
Osho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051115/24dc8ffc/attachment.htm 


From jers  Tue Nov 15 02:04:29 2005
From: jers (Jers)
Date: Tue, 15 Nov 2005 11:04:29 +0100
Subject: hoptapd and prism54 problem
Message-ID: <436A23A400B8A80A@ms004msg.mail.fw> (added by
	postmaster@fastwebnet.it)

Hi all,

 

I'm a new hostapd user and I hope you can help me!

I'd like to carry out a WPA-PSK access point with TKIP encryption method.
I'm working with Debian, kernel 2.6.9, and I'm using a pci Artem WLAN Card
whose data sheet asserts to support this security solution.

Moreover, this card include the PrismGT/Duette chipset and, therefore, it
works fine with prism54 driver. I tested it. Unfortunately, the prism54
official site is down at the moment and, consequently, I cannot have any
support to know if and how I can use iwpriv private ioctls to get my task.
However, I downloaded the driver which should be support WPA-2

 

http://svnweb.tuxfamily.org/listing.php?repname=prism54+%28prism54%29
<http://svnweb.tuxfamily.org/listing.php?repname=prism54+%28prism54%29&path=
%2Ftags%2FWPA-2%2F&rev=0&sc=0> &path=%2Ftags%2FWPA-2%2F&rev=0&sc=0

 

(the driver supporting only WPA-1 does not compile because the isl_ioctl.c
has a lot of simple mistake and so it does not seem reliable). 

 

Besides, I downloaded and installed hostapd-0.3.9 which supports Prism54
driver. I run 

 

ifup eth1

hostapd hostapd.conf

 

It seems to work but it also prints 

 

protocol 0300 is buggy, dev eth1

 

Actually, it does not work. In fact all clients get the connection with the
AP, without any key.

Can someone provide any suggestion?

 

Thanks in advance.

Jers

 

PS: In the following, my configuration files:

 

My .config file is:

 

# Driver interface for Prism54 driver

CONFIG_DRIVER_PRISM54=y

 

# WPA2/IEEE 802.11i RSN pre-authentication

CONFIG_RSN_PREAUTH=y

# Integrated EAP authenticator

CONFIG_EAP=y

# EAP-PEAP for the integrated EAP authenticator

CONFIG_EAP_PEAP=y

 

My hostapd configuration file is:

 

interface=eth1

driver=prism54

logger_syslog=-1

logger_syslog_level=-1

logger_stdout=-1

logger_stdout_level=2

 

debug=4

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

 

ctrl_interface_group=0

ssid=MY_SSID

macaddr_acl=0

eap_authenticator=0

 

own_ip_addr=127.0.0.1

 

wpa=1

wpa_psk=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef

wpa_key_mgmt=WPA-PSK

wpa_pairwise=TKIP

wpa_gmk_rekey=86400

 

All the other parameters are commented. 

 

Finally, my /etc/network/interfaces file is

 

iface eth1 inet static

      post-up /etc/init.d/dhcp start

      pre-down /etc/init.d/dacp stop

      address 192.165.1.1

      netmask 255.255.255.240

      network 192.165.1.0

      broadcast 192.165.1.15

 

 

 


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.0/168 - Release Date: 14/11/2005


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051115/876d6b5b/attachment.htm 


From cduffy  Mon Nov 14 08:11:03 2005
From: cduffy (Charles Duffy)
Date: Mon, 14 Nov 2005 10:11:03 -0600
Subject: Oops on loading drivers for hostap-driver 0.3.9 (on x86_64 host)
Message-ID: <dlacup$m5a$1@sea.gmane.org>

Card is a PCI prism2 (per lspci, "Intersil Corporation Prism 2.5 Wavelan 
chipset (rev 01)"). I've built a copy of hostap-driver 0.3.9; my kernel 
is SuSE's 2.6.5-7.127-default on an x86_64 system.

hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
prism2_hw_init: initialized in 198 ms
wifi0: hfa384x_cmd: entry still in list? (entry=000001003f03bc80, 
type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, 
entry=000001003f03bc80, type=0, cmd=0x0001, param0=0x0000, EVSTAT=8000 
INTEN=0010)
wifi0: MAC port 0 enabling failed
wifi0: could not enable MAC port
wifi0: hfa384x_cmd: entry still in list? (entry=000001003f03bc00, 
type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, 
entry=000001003f03bc00, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8000 
INTEN=0010)
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8)
Could not get RID for component NIC
hostap_pci: Initialization failed
hostap_pci: hardware initialization failed
wifi0: removed pending cmd_queue entry (type=0, cmd=0x0002, param0=0x0000)
Unable to handle kernel paging request at ffffff00001b9060 RIP:
<ffffffffa025d483>{:hostap_pci:hfa384x_cmd+1059}
PML4 51e063 PGD 7fee0067 PMD 7fee1067 PTE 0
Oops: 0000 [1]
CPU 0
Pid: 7856, comm: ip Tainted: P  U (2.6.5-7.127-default 
SLES9_SP1_BRANCH-20041201144208)
RIP: 0010:[<ffffffffa025d483>] 
<ffffffffa025d483>{:hostap_pci:hfa384x_cmd+1059}
RSP: 0018:000001003b0f9c68  EFLAGS: 00010293
RAX: ffffff00001b9000 RBX: 0000000000000002 RCX: 000001003f03bc80
RDX: 0000000000000000 RSI: 000001003b75a000 RDI: ffffffffa0263b48
RBP: 000001003f03bc80 R08: 000001003b0f8000 R09: 0000000000000002
R10: 0000000000000004 R11: 0000000000002710 R12: 0000000000000000
R13: 000001003b75a000 R14: 000001003f03bc90 R15: 000001003b75a4c8
FS:  0000002a959a50a0(0000) GS:ffffffff80516800(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffff00001b9060 CR3: 0000000000101000 CR4: 00000000000006e0
Process ip (pid: 7856, threadinfo 000001003b0f8000, task 000001003f464510)
Stack: ffffffff80456a04 0000000000000202 0000000000000024 ffffffff801369b5
        0000000000000000 0000000000000000 0002000000000001 000001003b75a000
        0000003000000010 0000000000000216
Call Trace:<ffffffff801369b5>{printk+421} 
<ffffffff801322d0>{default_wake_function+0}
        <ffffffff801322d0>{default_wake_function+0} 
<ffffffffa025d60e>{:hostap_pci:prism2_hw_shutdown+142}
        <ffffffffa006f438>{:hostap:prism2_close+184} 
<ffffffffa006f5ab>{:hostap:prism2_open+219}
        <ffffffff802c4a47>{dev_open+119} 
<ffffffff802c39d8>{dev_change_flags+104}
        <ffffffff80303655>{devinet_ioctl+709} 
<ffffffff80168635>{handle_mm_fault+373}
        <ffffffff80120398>{do_page_fault+536} 
<ffffffff80303f1c>{inet_ioctl+92}
        <ffffffff802bcdb1>{sock_ioctl+609} <ffffffff8018dacf>{sys_ioctl+991}
        <ffffffff802bbf6c>{sock_create+348} 
<ffffffff80110384>{system_call+124}


Code: 0f b7 58 60 44 8b 45 20 0f b7 40 64 0f b7 db 0f b7 c0 89 5c
RIP <ffffffffa025d483>{:hostap_pci:hfa384x_cmd+1059} RSP <000001003b0f9c68>
CR2: ffffff00001b9060



For reference, orinoco_pci loads succesfully with this card, as follows:

orinoco.c 0.13e (David Gibson <hermes at gibson.dropbear.id.au> and others)
orinoco_pci.c 0.13e (David Gibson <hermes at gibson.dropbear.id.au> & Jean 
Tourrilhes <jt at hpl.hp.com>)
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 5 (level, low) -> IRQ 5
Detected Orinoco/Prism2 PCI device at 0000:02:06.0, mem:0xFDDFF000 to 
0xFDDFFFFF -> 0xffffff00001b9000, irq:5
Reset 
done.............................................................................................................................................................................................................................................................;
Clear 
Reset.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................;
pci_cor : reg = 0x0 - CBAC5 - CB8D1
eth1: Station identity 001f:0004:0001:0007
eth1: Looks like an Intersil firmware version 1.7.4
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:09:5B:68:51:25
eth1: Station name "Prism  I"
eth1: ready




From tobias.gebhard  Tue Nov 15 04:22:41 2005
From: tobias.gebhard (Tobias Gebhard)
Date: Tue, 15 Nov 2005 13:22:41 +0100 (CET)
Subject: hoptapd and prism54 problem
In-Reply-To: <436A23A400B8A80A@ms004msg.mail.fw> (added by
	postmaster@fastwebnet.it)
References: <436A23A400B8A80A@ms004msg.mail.fw> (added by
	postmaster@fastwebnet.it)>
Message-ID: <29689095.1132057361724.OPEN-XCHANGE.WebMail.ox@lee.leedom.home>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051115/ce6e2b81/attachment.htm 


From jers  Tue Nov 15 04:57:44 2005
From: jers (jers at inwind.it)
Date: Tue, 15 Nov 2005 13:57:44 +0100
Subject: hoptapd and prism54 problem
Message-ID: <IPZYO8$D0E6D0E73C5246E91DFE60E64AAF2AA4@libero.it>

Hi Tobias,

I really hope you are wrong because, according to my task, I cannot change my card.
Obviously I'll post any solution found, but I hope that others can help us.

Bye
Jers

> Hi
> 
> i have the same problem. And it seems to me that there is at moment no
> possibility to run hostapd with wpa and prism54. Hostapd is prepared to run wpa
> on prism54, but the prism54 driver development is stuck.
> 
> The easiest way is to buy a atheros card (madwifi drivers).
> 
> Just my 2 cents.
> 
> If you have a solution can you please report it back to the mailing list?
> 
> 




From posuna  Tue Nov 15 08:15:00 2005
From: posuna (Pablo Osuna)
Date: Tue, 15 Nov 2005 11:15:00 -0500
Subject: Diversity
Message-ID: <1132071300.7898.13.camel@localhost.localdomain>

Hi all:

I have these three cards running with hostap:

2511CD Plus EXT 2 PCMCIA 200mW
NL-2511MP PLUS mini-PCI 200mW
Reliawave? 802.11b 300mW High Power Wireless PC Card - Prism 2.5

I am using them with default diversity parameters (antsel_tx=0 and
antsel_rx=0) but do not know if I should set these parameters up to
another one. In that case, how I should setup the wlan interface? I do
not know the difference between AntSel pin low/high.

Please any advice on this would be appreciated.

Thanks!

Pablo

        antsel_tx:
                0 = do not touch TX AntSel, i.e., use card default
(default)
                1 = use antenna diversity
                2 = force TX AntSel pin low
                3 = force TX AntSel pin high
        antsel_rx:
                0 = do not touch RX AntSel, i.e., use card default
(default)
                1 = use antenna diversity
                2 = force RX AntSel pin low
                3 = force RX AntSel pin high




From asattari  Tue Nov 15 08:16:15 2005
From: asattari (asattari at site.uottawa.ca)
Date: Tue, 15 Nov 2005 11:16:15 -0500 (EST)
Subject: Host Ap and Syslink 
In-Reply-To: <43793E63.807@site.uottawa.ca>
References: <000401c5e90d$f7d05740$9088fea9@Medion>
	<43793E63.807@site.uottawa.ca>
Message-ID: <4903.127.0.0.1.1132071375.squirrel@127.0.0.1>


>
> Hello,
>
> Is there anyway that I will be able to read the quality of link and
level for my Syslink card , using Host Ap. I need that this pc works as
an Accesspoint, so I have to set the mode Master, but can not get some
iwconfig info like sugnalquality and ...Apparently the driver does not
report all the wireless info, i need to get updated signal and link
quality
>
> Thanks for any help or suggestions
>
> Afsaneh





From asattari  Tue Nov 15 08:27:43 2005
From: asattari (asattari at site.uottawa.ca)
Date: Tue, 15 Nov 2005 11:27:43 -0500 (EST)
Subject: [Fwd: Host Ap and Syslink]
Message-ID: <1306.127.0.0.1.1132072063.squirrel@127.0.0.1>


I am wondering to know Why my message was not posted ...

thanks
afsaneh
---------------------------- Original Message ----------------------------
Subject: Host Ap and Syslink
From:    asattari at site.uottawa.ca
Date:    Tue, November 15, 2005 11:16 am
To:      "Afsaneh Sattari" <asattari at site.uottawa.ca>
Cc:      "Afsaneh Sattari" <asattari at site.uottawa.ca>
         "'Wang Chen'" <apfw at excite.com>
         hostap at shmoo.com
--------------------------------------------------------------------------


>
> Hello,
>
> Is there anyway that I will be able to read the quality of link and
level for my Syslink card , using Host Ap. I need that this pc works as an
Accesspoint, so I have to set the mode Master, but can not get some
iwconfig info like sugnalquality and ...Apparently the driver does not
report all the wireless info, i need to get updated signal and link
quality
>
> Thanks for any help or suggestions
>
> Afsaneh





Regards,
Afsaneh




From jeff_sadowski  Tue Nov 15 12:33:26 2005
From: jeff_sadowski (Jeff Sadowski)
Date: Tue, 15 Nov 2005 12:33:26 -0800 (PST)
Subject: madwifi-ng works now yeah
Message-ID: <20051115203326.82572.qmail@web33511.mail.mud.yahoo.com>

Ok I tested the cvs of the development today with
madwifi-ng I obtained on 11-11 and it works :-) at
least at my school I'll try in on my wpa latter today
and at work tomorrow

Thanks

Jeff


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com



From guy  Tue Nov 15 13:12:26 2005
From: guy (Yaoyao Gu)
Date: Tue, 15 Nov 2005 16:12:26 -0500
Subject: Problem with changing the transmission power (txpower)
Message-ID: <003e01c5ea29$47672d30$b3a46ba4@ece.ohiostate.edu>

Hi,

I am really new to this community. So please let me know if this topic has been well discussed before.  I am using Linksys wcf12 wireless cf card. The version of the hostap driver is 0.2.5. I met some problem when I tried to reduce the transmission power of the cf wireless card.

When I execute the following commands, it gives me the error message such as "no private ioctl supported".
$ iwpriv wlan0 prism2-param 5 1  //change the alc to auto control 
                                                    // I have also tried 0 value here 
                                                    // but it generates the same error later
$ iwpriv wlan0 prism2-param 6 103  // set the tx power to 103  

I have also tried $iwconfig wlan0 txpower 103, and it gives me the following message. I guess it's the same problem.
Error for wireless request "Set Tx Power" (8B26) :
SET failed on device wlan0 ; Operation not supported.Several possible reason I can guess: 1) The cf card doesn't support transmission power control. 2) The version of hostap I have doesn't support txpower.

I checked $ iwpriv and it gives a list of parameters that iwpriv can control.  I didn't find txpower in it. But alc is there. I think that's why I can change alc setting. So does that mean that the hostap doesn't support txpower in the current version. If that's the case, how can I solve this problem? Do I need to modify the driver by myself? 

Thanks in advance. Any thoughts or suggestions are highly appreciated.

Cheers,

Yaoyao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051115/0cd25d69/attachment.htm 


From posuna  Tue Nov 15 13:17:29 2005
From: posuna (Pablo Osuna)
Date: Tue, 15 Nov 2005 16:17:29 -0500
Subject: Problem with changing the transmission power (txpower)
In-Reply-To: <003e01c5ea29$47672d30$b3a46ba4@ece.ohiostate.edu>
References: <003e01c5ea29$47672d30$b3a46ba4@ece.ohiostate.edu>
Message-ID: <1132089449.7898.25.camel@localhost.localdomain>

Please see:

http://list.voyage.hk/pipermail/voyage-linux/2005-November/000448.html

You should upgrade your driver to a newer version (0.3.9 or 0.4.5)

Regards:

Pablo

El mar, 15-11-2005 a las 16:12 -0500, Yaoyao Gu escribi?:
> Hi,
>  
> I am really new to this community. So please let me know if this
> topic has been well discussed before.  I am using Linksys wcf12
> wireless cf card. The version of the hostap driver is 0.2.5. I
> met some problem when I tried to reduce the transmission power of
> the cf wireless card.
>  
> When I execute the following commands, it gives me the error message
> such as "no private ioctl supported".
> 
> $ iwpriv wlan0 prism2-param 5 1  //change the alc to auto control 
>                                                     // I have also
> tried 0 value here 
>                                                     // but it
> generates the same error later
> $ iwpriv wlan0 prism2-param 6 103  // set the tx power to 103  
> 
> I have also tried $iwconfig wlan0 txpower 103, and it gives me the
> following message. I guess it's the same problem.
> Error for wireless request "Set Tx Power" (8B26) :
> SET failed on device wlan0 ; Operation not supported.
> Several possible reason I can guess: 1) The cf card doesn't support
> transmission power control. 2) The version of hostap I have doesn't
> support txpower.
>  
> I checked $ iwpriv and it gives a list of parameters that iwpriv can
> control.  I didn't find txpower in it. But alc is there. I think
> that's why I can change alc setting. So does that mean that the hostap
> doesn't support txpower in the current version. If that's the case,
> how can I solve this problem? Do I need to modify the driver by
> myself? 
>  
> Thanks in advance. Any thoughts or suggestions are highly appreciated.
>  
> Cheers,
>  
> Yaoyao
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From gros  Tue Nov 15 13:18:42 2005
From: gros (GROS =?iso-8859-1?B?Suly9G1l?=)
Date: Tue, 15 Nov 2005 22:18:42 +0100
Subject: SanDisk ConnectPlus SDWCFB-128 -> /proc/net/hostap/ is empty
Message-ID: <20051115211842.GA426@pc212>

hostap-driver-0.4.5

SanDisk CompactFlash 128MB + Low Power Wi-Fi Card 802.11b "Connect Plus" with PC Card Adapter
SDWCFB-128
H/W:1.0 F/W:1.7.4
20-91-00073-128E

/proc/net/hostap/ is empty

lsmod:
hostap_cs              48180   0  (unused)
hostap                 97032   0  [hostap_cs]

/etc/pcmcia/hostap_cs.conf:
card "SanDisk ConnectPlus"
   version "SanDisk", "ConnectPlus"
   manfid 0xd601, 0x0101
   bind "hostap_cs" to 0
   bind "ide-cs" to 1

If we swap the last 2 lines, the computer stop until we unplug the card.

debug:
kernel: hostap_crypt: registered algorithm 'NULL'
kernel: hostap_cs: setting Vcc=33 (constant)
kernel: hostap_cs: CS_EVENT_CARD_INSERTION
kernel: hostap_cs: setting Vcc=33 (from config)
kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
kernel: io->flags = 0x0047, io.base=0x0000, len=128
kernel: wifi0: Interrupt, but dev not OK
last message repeated 6 times
kernel: wifi0: Multi-function SanDisk ConnectPlus detected - using vendor-specific initialization
kernel: wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
kernel: wifi0: init command completed too quickly - retrying
kernel: wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
kernel: prism2_hw_init: initialized in 0 ms
kernel: wifi0: valid PDA not found
kernel: prism2_config() failed
kernel: hostap_cs: CS_EVENT_CARD_REMOVAL
kernel: wifi0: card already removed or not configured during shutdown
kernel: hostap_crypt: unregistered algorithm 'NULL' (deinit)

messages:
cardmgr[423]: socket 0: SanDisk ConnectPlus
kernel: hostap_cs: 0.4.5 - 2005-09-25 (Jouni Malinen <jkmaline at cc.hut.fi>)
cardmgr[423]: executing: 'modprobe ide-cs 2>&1'
cardmgr[423]: + modprobe: Can't locate module ide-cs
cardmgr[423]: modprobe exited with status 255
cardmgr[423]: module /lib/modules/2.4.31/pcmcia/ide-cs.o not available
kernel: hostap_cs: Registered netdevice wifi0
kernel: hostap_cs: index 0x01: Vcc 3.3, irq 11, io 0x0200-0x027f
kernel: hostap_cs: first command failed - assuming card does not have primary firmware
kernel: hostap_cs: first command failed - assuming card does not have primary firmware
kernel: hostap_cs: Driver unloaded

syslog:
kernel: NET: 76264 messages suppressed.
kernel: wifi0: prism2_enable_aux_port - timeout - reg=0xffff
kernel: wifi0: prism2_enable_aux_port - timeout - reg=0xffff
kernel: SWSUPPORT0 write/read failed: FFFF != 8A32
kernel: hostap_cs: Initialization failed
cardmgr[423]: get dev info on socket 0 failed: Resource temporarily unavailable


Thank you very much for your advices

-- 
@++.
jg.
//Il est toujours facile d'ob?ir, si l'on r?ve de commander.



From holger  Tue Nov 15 13:59:05 2005
From: holger (Holger Eitzenberger)
Date: Tue, 15 Nov 2005 22:59:05 +0100
Subject: hostapd/madwifi: interface does not come up on boot
Message-ID: <20051115215905.GA5360@kruemel.my-eitzenberger.de>

Hi,

I am switching from hostap.ko based solution to madwifi/hostapd and
I am seeing a strange behaviour with both of them.

After boot the ath0 device doesn't come up.  The behaviour is as
follows:

  boot
  ifconfig ath0 up
  hostapd started			# does not work

  # ifconfig again...
  ifconfig ath0 up			# syslog: ath0: creating bss 00:0f:b5:63:c5:64
							# it works

Other tests showed that hostapd is needed at the the time ath0
first comes up.  Another ifconfig ath0 up after hostapd was started 
works, even if hostapd is stopped again.

Is this a known issue?

Thx in advance.  /holger
  



From rjc  Tue Nov 15 16:12:28 2005
From: rjc (Bob Carlson)
Date: Tue, 15 Nov 2005 18:12:28 -0600
Subject: wpa_supplicant PSK question
Message-ID: <20051115161600.59D2899D@dm16.mta.everyone.net>

I am porting wpa_supplicant into an embedded application so I am trying to
minimize the code included. We do not require radius, only WEP and WPA-PSK.
So far as my understanding has progressed, we should not require EAPOL,
although there does appear to be a 4-way key exchange that is used.
However, as I build things up, I am finding that there are a lot of
references to EAPOL code that do not seem to be conditional.

What modules and code for EAPOL must still be included, even though we are
using only PSK?

Thanks, Bob




From eitanb  Wed Nov 16 00:39:16 2005
From: eitanb (Bar, Eitan)
Date: Wed, 16 Nov 2005 10:39:16 +0200
Subject: EAPOLs in Linux Wireless Extensions
Message-ID: <C08C15DE99919148ACF278138C3CEC413BE688@dile01.ent.ti.com>

Hi,

 

Can somebody please describe the chain of events in the kernel/user-mode (as far as WEXT IOCTLs and events) that occur when a station associates and starts the EAPOL handshake?

What I?m specifically interested in is how the kernel driver makes sure that only EAPOL packets are sent/received by the driver and how can the network stack (or whoever) makes sure EAPOLs are prioritized over other types of traffic. (What happens if at the moment the interface notifies ?UP?, the network stack starts sending heavy traffic).

Will this traffic be just dropped at some higher level of the kernel driver and handle only EAPOLs? (I am aware of a driver wrapper to handle only EAPOLs, but what I?m concerned is other traffic from network stack and what happens to it).

 

Is there maybe a special support to notify the linux networking stack that it should not forward any packets other than EAPOLs?

 

Thanks,

 Eitan

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051116/7a25ed11/attachment.htm 


From trevor.pering  Wed Nov 16 17:11:32 2005
From: trevor.pering (Pering, Trevor)
Date: Wed, 16 Nov 2005 17:11:32 -0800
Subject: CF Card Power Save Mode
Message-ID: <EFCD68F7BFDB06468769D4D9EAAA93870977B46B@scsmsx401.amr.corp.intel.com>

Hello -- I'm trying to get power save mode working with a CF wi-fi card
-- specifically the Linksys WCF12. (We have also tried the NetGear701).
We can set the mode ok with iwconfig, but the power consumption does not
change. Does anybody know if this is the sort of thing that is likely to
work?  I searched the archives, and there have been several posts to
this list asking about similar things, but very few responses. Are there
any CF-based WiFi cards that people know about that definitely support
PSM with HostAP?  The card itself (WCF12) should support it, according
to the specs, but the trick is to actually get it working...
 
The command we are using is: iwconfig wlan0 power period 500ms

Any help, advice, or experience would be greatly appreciated.

Cheers,
	Trevor



From throw_away_2002  Wed Nov 16 17:56:13 2005
From: throw_away_2002 (Tom)
Date: Wed, 16 Nov 2005 17:56:13 -0800 (PST)
Subject: Still can't connect
Message-ID: <20051117015614.4220.qmail@web52104.mail.yahoo.com>

Upgraded to ndiswrapper 1.5, but now I see the AP
on a "blacklist." :(

# dog /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
        group=TKIP
        key_mgmt=WPA-PSK
        pairwise=TKIP
        proto=WPA
        psk="mypassword"
        ssid="myssid"
        }

# wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf -iwlan0 -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
'ndiswrapper'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=2
Line: 5 - start of a new network block
group: 0x8
key_mgmt: 0x2
pairwise: 0x8
proto: 0x1
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
ssid - hexdump_ascii(len=11): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid=[REMOVED]
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: [REMOVED]
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Trying to associate with SSID [REMOVED]
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8c07 len=95
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated to a new BSS: BSSID=[REMOVED]
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: Using WPA IE from AssocReq to set cipher suites
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Associated with [REMOVED]
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 1b 1d 76 85 0e c2 90 80 58 9b 9f e7 1f d7 88 c7 44 75 88 8e 05
1f 20 ca 99 f4 5d 65 f2 a5 c2 65 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 1b 1d 76 85 0e c2 90 80 58 9b 9f e7 1f d7 88 c7 44 75
88 8e 05 1f 20 ca 99 f4 5d 65 f2 a5 c2 65 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVED]
WPA: Renewed SNonce - hexdump(len=32): f9 31 fd a3 2d 45 59 cf 09 bc 80
9d 55 b7 1a ba 05 3c 8b 75 e2 aa 79 21 c5 3d 75 20 ec e9 21 72
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 08 25 e3 5a 38 38 e6 93 16 3c ed
be 61 3f af 66
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82 00 14 a5 15
f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 f9 31 fd
a3 2d 45 59 cf 09 bc 80 9d 55 b7 1a ba 05 3c 8b 75 e2 aa 79 21 c5 3d 75
20 ec e9 21 72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 08 25 e3 5a 38 38 e6 93 16 3c ed
be 61 3f af 66 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2
02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29
idleWhile=59
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28
idleWhile=58
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 78 6b 75 e8 a5 9f 1e b7 56 3d fd d6 2b e6 0e 10 28 0b 79 db 33
10 8b d8 49 37 fa 89 d8 38 be 5b 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 78 6b 75 e8 a5 9f 1e b7 56 3d fd d6 2b e6 0e 10 28 0b
79 db 33 10 8b d8 49 37 fa 89 d8 38 be 5b 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVED]
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 11 bd 72 cb 75 24 f6 26 1e 9d 84
ab ba b1 f2 14
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82 00 14 a5 15
f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 f9 31 fd
a3 2d 45 59 cf 09 bc 80 9d 55 b7 1a ba 05 3c 8b 75 e2 aa 79 21 c5 3d 75
20 ec e9 21 72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 11 bd 72 cb 75 24 f6 26 1e 9d 84
ab ba b1 f2 14 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2
02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27
idleWhile=57
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=26
idleWhile=56
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25
idleWhile=55
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 dc 5a d4 b2 3e 53 75 87 97 a8 b3 e9 a6 2a e8 b1 2f bc 8a e5 8e
90 50 47 1f a8 94 f8 fc e8 ed ea 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 dc 5a d4 b2 3e 53 75 87 97 a8 b3 e9 a6 2a e8 b1 2f bc
8a e5 8e 90 50 47 1f a8 94 f8 fc e8 ed ea 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVEI]
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): cc 38 88 fe 95 e8 82 6a af 45 6e
8f 27 32 18 6c
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82 00 14 a5 15
f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 f9 31 fd
a3 2d 45 59 cf 09 bc 80 9d 55 b7 1a ba 05 3c 8b 75 e2 aa 79 21 c5 3d 75
20 ec e9 21 72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 cc 38 88 fe 95 e8 82 6a af 45 6e
8f 27 32 18 6c 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2
02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24
idleWhile=54
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=23
idleWhile=53
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=22
idleWhile=52
RX EAPOL from [REMOVED]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 b0 ed ab 07 28 c5 d6 b8 63 eb 01 04 af 61 0a 54 7d cb 00 04 b5
d7 99 71 e5 5e 24 50 31 04 63 db 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 b0 ed ab 07 28 c5 d6 b8 63 eb 01 04 af 61 0a 54 7d cb
00 04 b5 d7 99 71 e5 5e 24 50 31 04 63 db 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from [REMOVED]
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 34 fb 42 52 f4 84 06 8d 47 91 0b
b9 5d e1 f7 b4
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b ea 31 82 00 14 a5 15
f4 8c 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 f9 31 fd
a3 2d 45 59 cf 09 bc 80 9d 55 b7 1a ba 05 3c 8b 75 e2 aa 79 21 c5 3d 75
20 ec e9 21 72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 34 fb 42 52 f4 84 06 8d 47 91 0b
b9 5d e1 f7 b4 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2
02 01 00 00 50 f2 02
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=21
idleWhile=51
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20
idleWhile=50
Authentication with [REMOVED] timed out.
Added BSSID [REMOVED] into blacklist
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
Trying to associate with SSID [REMOVED]
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
BSSID [REMOVED] blacklist count incremented to 2
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Disconnect event - remove keys
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=19
idleWhile=49
Wireless event: cmd=0x8c07 len=95
Wireless event: cmd=0x8c08 len=40
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: [REMOVED]
Association event - clear replay counter
Associated to a new BSS: BSSID=[REMOVED]

And so on until I kill it, then I finally get:

Removed BSSID [REMOVED] from blacklist (clear)

I don't know where the "AP 00:00:00:00:00:00" comes
from. Any ideas? Thanks.


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com



From maccari-thisaintpartofmyaddress-  Thu Nov 17 02:50:10 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Thu, 17 Nov 2005 11:50:10 +0100
Subject: [PATCH] adding wpa_common.h
Message-ID: <20051117105010.GA28712@lenst.det.unifi.it>

I'm back trying to link wpa_supplicant with hostapd code, with the aim of
having a supplicant SM working into hostapd code (final aim is have WPA
over WDS). This is a little patch I spoke about a few weeks ago that makes
things easier, it moves some definitions common to wpa_supplicant and
hostapd code into a common file wpa_common.h. There are a few definitions
in the new file but they might become more with time.

with this and a few more diffs I was able to do something like:

 struct wpa_sm_ctx * ctx;
 ctx = malloc(sizeof(*ctx));
 if (ctx == NULL) {
	 printf("Failed to allocate WPA context.\n");
	 return -1;
 }

 initialize_supplicant_interface(ctx);

into hostapd.c, now I'm thinkng how to port all the functions needed by
wpa_sm_ctx. as said before it would be easier if files in different
packages could have different names (wpa.c has the same name in
wpa_supplicant and hostapd, it would be easier if it was named wpa_s.c and
wpa_a.c or whatever), that would save some rename or hardlink for
compilation.

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 

-------------- next part --------------
Only in hostapd-0.4.6-dev/: .config
diff --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u hostapd-0.4.6/ieee802_1x.h hostapd-0.4.6-dev/ieee802_1x.h
--- hostapd-0.4.6/ieee802_1x.h	2005-08-29 06:05:12.000000000 +0200
+++ hostapd-0.4.6-dev/ieee802_1x.h	2005-11-17 11:18:14.568460880 +0100
@@ -1,23 +1,6 @@
 #ifndef IEEE802_1X_H
 #define IEEE802_1X_H
 
-/* IEEE Std 802.1X-REV-d11, 7.2 */
-
-struct ieee802_1x_hdr {
-	u8 version;
-	u8 type;
-	u16 length;
-	/* followed by length octets of data */
-} __attribute__ ((packed));
-
-#define EAPOL_VERSION 2
-
-enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
-       IEEE802_1X_TYPE_EAPOL_START = 1,
-       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
-       IEEE802_1X_TYPE_EAPOL_KEY = 3,
-       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
-};
 
 /* draft-congdon-radius-8021x-20.txt */
 
@@ -43,9 +26,6 @@
 	 * RC4 key used in encryption = Key-IV + MS-MPPE-Recv-Key */
 } __attribute__ ((packed));
 
-enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
-       EAPOL_KEY_TYPE_WPA = 254 };
-
 
 void ieee802_1x_receive(struct hostapd_data *hapd, const u8 *sa, const u8 *buf,
 			size_t len);
Common subdirectories: hostapd-0.4.6/logwatch and hostapd-0.4.6-dev/logwatch
Only in hostapd-0.4.6-dev/: wpa_common.h
diff --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u hostapd-0.4.6/wpa.h hostapd-0.4.6-dev/wpa.h
--- hostapd-0.4.6/wpa.h	2005-06-26 20:27:44.000000000 +0200
+++ hostapd-0.4.6-dev/wpa.h	2005-11-17 11:32:37.745238064 +0100
@@ -1,14 +1,14 @@
 #ifndef WPA_H
 #define WPA_H
 
-#define WPA_NONCE_LEN 32
+#include "wpa_common.h"
+
 #define WPA_PMK_LEN PMK_LEN
-#define WPA_REPLAY_COUNTER_LEN 8
 #define WPA_GMK_LEN 32
 #define WPA_GTK_MAX_LEN 32
-#define WPA_KEY_RSC_LEN 8
 #define PMKID_LEN 16
 
+
 struct rsn_pmksa_cache {
 	struct rsn_pmksa_cache *next, *hnext;
 	u8 pmkid[PMKID_LEN];
-------------- next part --------------
Only in wpa_supplicant-0.4.6-dev/: .config
Common subdirectories: wpa_supplicant-0.4.6/doc and wpa_supplicant-0.4.6-dev/doc
Common subdirectories: wpa_supplicant-0.4.6/examples and wpa_supplicant-0.4.6-dev/examples
Only in wpa_supplicant-0.4.6-dev/: wpa_common.h
Common subdirectories: wpa_supplicant-0.4.6/wpa_gui and wpa_supplicant-0.4.6-dev/wpa_gui
Common subdirectories: wpa_supplicant-0.4.6/wpa_gui-qt4 and wpa_supplicant-0.4.6-dev/wpa_gui-qt4
diff --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u wpa_supplicant-0.4.6/wpa.h wpa_supplicant-0.4.6-dev/wpa.h
--- wpa_supplicant-0.4.6/wpa.h	2005-10-02 01:34:36.000000000 +0200
+++ wpa_supplicant-0.4.6-dev/wpa.h	2005-11-17 11:28:05.963555160 +0100
@@ -16,29 +16,10 @@
 #define WPA_H
 
 #include "defs.h"
+#include "wpa_common.h"
 
 #define BIT(n) (1 << (n))
 
-struct ieee802_1x_hdr {
-	u8 version;
-	u8 type;
-	u16 length;
-	/* followed by length octets of data */
-} __attribute__ ((packed));
-
-#define EAPOL_VERSION 2
-
-enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
-       IEEE802_1X_TYPE_EAPOL_START = 1,
-       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
-       IEEE802_1X_TYPE_EAPOL_KEY = 3,
-       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
-};
-
-enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
-       EAPOL_KEY_TYPE_WPA = 254 };
-
-
 #define WPA_CAPABILITY_PREAUTH BIT(0)
 
 #define GENERIC_INFO_ELEM 0xdd
diff --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u wpa_supplicant-0.4.6/wpa_i.h wpa_supplicant-0.4.6-dev/wpa_i.h
--- wpa_supplicant-0.4.6/wpa_i.h	2005-09-12 22:16:15.000000000 +0200
+++ wpa_supplicant-0.4.6-dev/wpa_i.h	2005-11-17 11:27:09.184186936 +0100
@@ -15,10 +15,6 @@
 #ifndef WPA_I_H
 #define WPA_I_H
 
-#define WPA_NONCE_LEN 32
-#define WPA_REPLAY_COUNTER_LEN 8
-
-
 struct rsn_pmksa_candidate;
 
 /**


From jeff_sadowski  Thu Nov 17 07:30:55 2005
From: jeff_sadowski (Jeff Sadowski)
Date: Thu, 17 Nov 2005 07:30:55 -0800 (PST)
Subject: madwifi-ng and wpa_supplicant
Message-ID: <20051117153055.56553.qmail@web33515.mail.mud.yahoo.com>

Previously I said I got madwifi-ng working with
wpa_supplicant at school.

Well as soon as I got home wpa_supplicant stopped
working. I'm not sure if its that my school has no wep
key or wpa stuff or it could also be the kind of
Access Points they have. And it still doesn't work at
work either. I know they have some sort of cisco APs
at school and that we have a different cisco ap at
work. So I think maybe the madwifi driver doesn't
report things right. I have two APs at home both in my
wpa_supplicant list
one is wpa and thats a linksys WRT54G and the other is
just wep and thats a dlink. I had to revert back to a
cvs snapshot taken in september for the madwifi driver
in order for it to work.


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com



From hualaw  Thu Nov 17 08:36:17 2005
From: hualaw (hua law)
Date: Fri, 18 Nov 2005 00:36:17 +0800
Subject: How the management frames are sent to user space?
Message-ID: <c2af449f0511170836y4a50180br969559a2883ebd97@mail.gmail.com>

I traced the frame receive function calling link and finally in the
prism2_rx_80211() funciton I found the following lines:
  if (type == PRISM2_RX_MGMT && (fc & WLAN_FC_PVER)) {
printk(KERN_DEBUG "%s: dropped management frame with header "
"version %d\n", dev->name, fc & WLAN_FC_PVER);
dev_kfree_skb_any(skb);
return 0;
}
 the hostap version is 0.3.9
 I was informed that the management frames are been process by user space
deamon processes, but I can not guess out the implementation from the above
code.
 What the mechnism the hostap tranfering his management frames to the user
space?
 Help me please, Thanks.
 Best Regard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051118/3ce82b53/attachment.htm 


From jar  Thu Nov 17 10:54:41 2005
From: jar (Jar)
Date: Thu, 17 Nov 2005 20:54:41 +0200
Subject: Hostap_pci vs. orinoco_pci
Message-ID: <437CD1F1.9080300@pcuf.fi>


Hello

When using FC4 2.6.12, I have to put the following lines to the end of 
the /etc/hotplug/blacklist to get rid of loading orinoco_pci.

# a) Do NOT load orinoco_pci when we are using hostap driver
# b) Do NOT load hostap_pci or it's alias wlan1 defined in
#    /etc/modprobe.conf, let network service run it instead.
orinoco_pci
hostap_pci
wlan1

Now when I updated to FC4 2.6.14 this doesn't work any more. I have to 
delete orinoco_pci. Otherwise both hostap_pci and orinoco_pci are loaded 
at boot.

Intresiting thing is (according to dmesg) that the orinoco_pci is loaded 
first and then hostap_pci. Anyhow, finally lsmod shows that no orinoco* 
modules has been loaded. Who unloads them, does loading another module 
(hostap_pci) for same device cause that?

orinoco 0.15rc2 (David Gibson <hermes at gibson.dropbear.id.au>, Pavel 
Roskin <proski at gnu.org>, et al)
orinoco_pci 0.15rc2 (Pavel Roskin <proski at gnu.org>, David Gibson 
<hermes at gibson.dropbear.id.au> & Jean Tour
eth2: WEP supported, 104-bit key
eth2: MAC address 00:0E:6A:6A:6A:6A
eth2: Station name "Prism  I"
eth2: ready
ACPI: PCI interrupt for device 0000:02:0a.0 disabled
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
ip_tables: (C) 2000-2002 Netfilter core team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.3 (4095 buckets, 32760 max) - 236 bytes per conntrack
u32 classifier
     Perfomance counters on
     OLD policer on
     input device check on
Ingress scheduler: Classifier actions prefered over netfilter
ieee80211_crypt: registered algorithm 'NULL'
hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 11 (level, 
low) -> IRQ 11
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x50
prism2_hw_init: initialized in 192 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: Intersil Prism2.5 PCI: mem=0xdfbff000, irq=11
wifi0: registered netdevice wlan0

Finally I have to delete orinoco_pci. That is not elegant way to handle 
this. What is the _great_ idea to put prism2 device IDs to the orinoco 
driver?

Is there some other method than the delete method to handle this? What 
if I had one orinoco_pci and one hostap_pci device in same PC and I want 
to use orinco driver for orinoco and hostap driver for prism2 device?

-- 
Best Regards, Jar



From ars  Fri Nov 18 02:07:17 2005
From: ars (Arseniy Chernov)
Date: Fri, 18 Nov 2005 13:07:17 +0300
Subject: Michael Countermeasures tracing
Message-ID: <437DA7D5.3000008@itconnection.ru>

Hello.

I'm spending second week already trying to understand how should the 
trace of source of MIC error in a buggy RF environment be performed, 
hope to receive some advices here...

The DS is built on two D-Link DWL-2100AP, latest firmwares.
MS are either Intel PRO Wireless 2200BG or Ambit Microsystems 11b/g WNIC.

WPA-PSK with TKIP

Monitoring APs reports MIC errors in RX frames periodically. The report 
on D-Link looks like "MIC error in RX frame at %integer", where %integer 
is something that my Russian D-Link office could not explain ("too deep" 
they said). I suppose it is a value from total frames passed DS->RF, 
DS<-RF counter.

But what is certain: RX means that there's a buggy adapter - I doubt if 
I'm wrong.

What I did first is started a syslog stats on roaming/associations from 
a week period (I thought MICs can be caused by a panicly roamed MS that 
calculated checksum for one DEST MAC, but sends frame to other DEST 
MAC). Its examples are:

2005-11-02 13:37:40	User.Notice	192.168.0.125	Wireless STA connected 
00-0E-35-FC-E5-53
2005-11-02 13:37:43	User.Notice	192.168.0.124	Wireless STA connected 
00-0E-35-FC-E5-53

countermeasures followed on AP .124


OR

2005-11-17 17:37:03	User.Notice	192.168.0.125	Wireless STA connected 
00-12-F0-18-E2-DF
2005-11-17 17:37:03	User.Notice	192.168.0.125	Last message repeated 10 times

countermeasures followed on .125

OR very funny one

2005-11-17 20:03:49	User.Notice	192.168.0.124	Wireless STA connected 
00-12-F0-18-B1-F3
2005-11-17 20:04:04	User.Notice	192.168.0.124	Last message repeated 509 
times

countermeasures followed on .124

so you see, no system at all among those 15 MB of logs. So it's not the 
poing of panic roaming - so I was wrong.

I started ethereal monitoring to catch any suspicious 
authentication/association denicals or something just in few frames 
before actual countermeasure starts on a given AP.
Found nothing suspicious - just Data and Acks...

I wonder how can I solve this problem with MIC errors leading to 
countermeasures constantly.

Thank you.



-- 
Regards,
Arseniy Chernov
e-mail: ars at itconnection.ru
phone: +7 812 320-9850




From vda  Fri Nov 18 03:53:43 2005
From: vda (Denis Vlasenko)
Date: Fri, 18 Nov 2005 13:53:43 +0200
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <437CD1F1.9080300@pcuf.fi>
References: <437CD1F1.9080300@pcuf.fi>
Message-ID: <200511181353.43811.vda@ilport.com.ua>

On Thursday 17 November 2005 20:54, Jar wrote:
> 
> Hello
> 
> When using FC4 2.6.12, I have to put the following lines to the end of 
> the /etc/hotplug/blacklist to get rid of loading orinoco_pci.
> 
> # a) Do NOT load orinoco_pci when we are using hostap driver
> # b) Do NOT load hostap_pci or it's alias wlan1 defined in
> #    /etc/modprobe.conf, let network service run it instead.
> orinoco_pci
> hostap_pci
> wlan1
> 
> Now when I updated to FC4 2.6.14 this doesn't work any more. I have to 
> delete orinoco_pci. Otherwise both hostap_pci and orinoco_pci are loaded 
> at boot.
> 
> Intresiting thing is (according to dmesg) that the orinoco_pci is loaded 
> first and then hostap_pci. Anyhow, finally lsmod shows that no orinoco* 
> modules has been loaded. Who unloads them, does loading another module 
> (hostap_pci) for same device cause that?
> 
> orinoco 0.15rc2 (David Gibson <hermes at gibson.dropbear.id.au>, Pavel 
> Roskin <proski at gnu.org>, et al)
> orinoco_pci 0.15rc2 (Pavel Roskin <proski at gnu.org>, David Gibson 
> <hermes at gibson.dropbear.id.au> & Jean Tour
> eth2: WEP supported, 104-bit key
> eth2: MAC address 00:0E:6A:6A:6A:6A
> eth2: Station name "Prism  I"
> eth2: ready
> ACPI: PCI interrupt for device 0000:02:0a.0 disabled
> e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
> eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> ip_tables: (C) 2000-2002 Netfilter core team
> Netfilter messages via NETLINK v0.30.
> ip_conntrack version 2.3 (4095 buckets, 32760 max) - 236 bytes per conntrack
> u32 classifier
>      Perfomance counters on
>      OLD policer on
>      input device check on
> Ingress scheduler: Classifier actions prefered over netfilter
> ieee80211_crypt: registered algorithm 'NULL'
> hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
> ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 11 (level, 
> low) -> IRQ 11
> hostap_pci: Registered netdevice wifi0
> wifi0: Original COR value: 0x50
> prism2_hw_init: initialized in 192 ms
> wifi0: NIC: id=0x8013 v1.0.0
> wifi0: PRI: id=0x15 v1.1.1
> wifi0: STA: id=0x1f v1.7.4
> wifi0: Intersil Prism2.5 PCI: mem=0xdfbff000, irq=11
> wifi0: registered netdevice wlan0
> 
> Finally I have to delete orinoco_pci. That is not elegant way to handle 
> this. What is the _great_ idea to put prism2 device IDs to the orinoco 
> driver?
> 
> Is there some other method than the delete method to handle this? What 
> if I had one orinoco_pci and one hostap_pci device in same PC and I want 
> to use orinco driver for orinoco and hostap driver for prism2 device?

Do not build both modules. Or even send patch to remove prism2 dev IDs
from orinoco.
--
vda



From jwright  Fri Nov 18 04:26:14 2005
From: jwright (Joshua Wright)
Date: Fri, 18 Nov 2005 07:26:14 -0500
Subject: Michael Countermeasures tracing
In-Reply-To: <437DA7D5.3000008@itconnection.ru>
References: <437DA7D5.3000008@itconnection.ru>
Message-ID: <437DC866.4000007@hasborg.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arseniy Chernov wrote:
> I'm spending second week already trying to understand how should the 
> trace of source of MIC error in a buggy RF environment be performed, 
> hope to receive some advices here...

It's interesting that you would ever see a Michael error.  The design of
TKIP has a few different security features that would make it difficult
for someone to craft a frame that would report an invalid Michael hash.
 Specifically, I believe the TKIP RX handling process works as follows:

1. Receive frame, examine sequence number.  If sequence number is too
small, drop frame (mitigating replay attacks).
2. Implement key mixing function to decrypt the MPDU and check the ICV.
 If the ICV is invalid, drop the frame.
3. Reassemble all MPDU's into the MSDU and calculate Michael hash over
the contents.  If Michael hash is invalid, record and take
countermeasures if necessary.

I see a few different possibilities where you would be experiencing
Michael errors:

1. An adversary is maliciously injecting malformed frames to DoS your
network by triggering Michael countermeasures.  This isn't likely, as
the attacker has to overcome the rules of sequence enforcement and
maintaining the integrity of the ICV in order to make this happen.
2. Faulty AP implementation - if your AP isn't following the correct
order of steps to decrypt and verify the contents of an MSDU (e.g. they
are checking the Michael hash before they check the ICV), then a corrupt
frame could cause this condition.
3. Faulty client implementation - If your client has a software flaw, it
is possible that they aren't recording the Michael hash properly, or are
not calculating the Michael hash over the correct fields.  I'd imagine
this is the most likely case here - what client software and card are
you using for your station?

Thanks for sharing these details.

- -Josh
- --
- -Joshua Wright
jwright at hasborg.com

2005-2006 pgpkey: http://802.11ninja.net/pgpkey.htm
fingerprint: F00E 7A42 8375 0C55 964F E5A4 4D2F 22F6 3658 A4BF

Today I stumbled across the world's largest hotspot.  The SSID is "linksys".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDfchlTS8i9jZYpL8RAr1yAJ49LzjNVNjciLFaYuzK8rTBLU5+twCeNPTc
hbPUkaydwB2weoCEIOvafiw=
=8ECs
-----END PGP SIGNATURE-----



From jar  Fri Nov 18 05:37:25 2005
From: jar (Jar)
Date: Fri, 18 Nov 2005 15:37:25 +0200 (EET)
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <200511181353.43811.vda@ilport.com.ua>
References: <437CD1F1.9080300@pcuf.fi> <200511181353.43811.vda@ilport.com.ua>
Message-ID: <59174.194.157.0.2.1132321045.squirrel@netlandzone.dyndns.org>


> Do not build both modules. Or even send patch to remove prism2 dev IDs
> from orinoco.

The problem is that distros naturally provides both modules as default in their
kernels. This same applies also to the orinoco_cs and hostap_cs. I can't see the why
the orinoco driver has to try support prism2 devices now when the hostap driver is
in the kernel. This has been causes unnecessary mess with these drivers for many
people already.

If I remember correctly the prism2 IDs e.g. for the orinico_cs was added quite
resently.

-- 
Best Regards, Jar



From ars  Fri Nov 18 05:56:46 2005
From: ars (Arseniy Chernov)
Date: Fri, 18 Nov 2005 16:56:46 +0300
Subject: Michael Countermeasures tracing
In-Reply-To: <437DC866.4000007@hasborg.com>
References: <437DA7D5.3000008@itconnection.ru> <437DC866.4000007@hasborg.com>
Message-ID: <437DDD9E.6020002@itconnection.ru>

Hello Joshua,

> I see a few different possibilities where you would be experiencing
> Michael errors:
> 
> 1. An adversary is maliciously injecting malformed frames to DoS your
> network by triggering Michael countermeasures.  This isn't likely, as
> the attacker has to overcome the rules of sequence enforcement and
> maintaining the integrity of the ICV in order to make this happen.

Furthermore, there is noone in RF but domestic MSes, checked this many 
times already, logged kismet... Noone!

> 2. Faulty AP implementation - if your AP isn't following the correct
> order of steps to decrypt and verify the contents of an MSDU (e.g. they
> are checking the Michael hash before they check the ICV), then a corrupt
> frame could cause this condition.

The same revision/firmware APs are working great at another site - so I 
don't think this is up to D-Link. Seems more like it's a client.

> 3. Faulty client implementation - If your client has a software flaw, it
> is possible that they aren't recording the Michael hash properly, or are
> not calculating the Michael hash over the correct fields.  I'd imagine
> this is the most likely case here - what client software and card are
> you using for your station?

5 x Intel PRO Wireless 2200BG
1 x Ambit Microsystems 11b/g Wireless Network Adapter

As to the Intel, what I just found out is that they released a shiny new 
software in beginning of Novemer - so I'd rather re-install ALL drivers, 
ALL WLAN tools to the very-very-very latest ones and check the site again.

They claim:

ftp://aiedownload.intel.com/df-support/9563/ENG/Install%20and%20Support%20Notes.htm

issue 1658027 Intel? PROSet/Wireless software fails to correctly 
authenticate in a 802.1x environment after many roams

issue 1619573 WPA2-TKIP, WEP and WPA-AES,WEP encryption failure 
w/WPA2-AES+TKIP+WEP access point

This is something not very specific to my case, but they seem to have 
problems with WPA, anyway.

 > Thanks for sharing these details.

Thank you for taking time to clear my TKIP understanding.

I'll send a report about this issue, because this countermeasures thing 
were somewhat outstanding for me. I hope that was simply buggy Intel.

Cheers!



-- 
Regards,
Arseniy Chernov
e-mail: ars at itconnection.ru
phone: +7 812 320-9850




From jar  Fri Nov 18 07:28:28 2005
From: jar (Jar)
Date: Fri, 18 Nov 2005 17:28:28 +0200 (EET)
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <200511181353.43811.vda@ilport.com.ua>
References: <437CD1F1.9080300@pcuf.fi> <200511181353.43811.vda@ilport.com.ua>
Message-ID: <38797.194.157.0.2.1132327708.squirrel@netlandzone.dyndns.org>


> Do not build both modules. Or even send patch to remove prism2 dev IDs
> from orinoco.

Hostap_cpi and orinoco_pci has exactly the same IDs:

static struct pci_device_id prism2_pci_id_table[] __devinitdata = {
        /* Intersil Prism3 ISL3872 11Mb/s WLAN Controller */
        { 0x1260, 0x3872, PCI_ANY_ID, PCI_ANY_ID },
        /* Intersil Prism2.5 ISL3874 11Mb/s WLAN Controller */
        { 0x1260, 0x3873, PCI_ANY_ID, PCI_ANY_ID },
        /* Samsung MagicLAN SWL-2210P */
        { 0x167d, 0xa000, PCI_ANY_ID, PCI_ANY_ID },
        { 0 }
};

static struct pci_device_id orinoco_pci_pci_id_table[] = {
        /* Intersil Prism 3 */
        {0x1260, 0x3872, PCI_ANY_ID, PCI_ANY_ID,},
        /* Intersil Prism 2.5 */
        {0x1260, 0x3873, PCI_ANY_ID, PCI_ANY_ID,},
        /* Samsung MagicLAN SWL-2210P */
        {0x167d, 0xa000, PCI_ANY_ID, PCI_ANY_ID,},
        {0,},
};

If the Prism2 IDs are taken off, nothing left. Should the orinoco_pci die and the
hostap_pci continue?

Still not understand why to support prism2 devices (e.g. pcmcia or pci) via orinoco
driver when better driver (hostap) for them is in (starting from 2.6.14). It would
be OK if the users could easily (wihout compiling the kernel) and temporarily
(without deleting the competing modules) block the other, but this is not currently
possible?

Should the authors of the orinoco driver concentrate to adding the
wpa/wpa_supplicant support for the pure orinoco(hermes1) products rather than adding
support for other devices which already has a proper Linux driver?

-- 
Best Regards, Jar



From proski  Fri Nov 18 07:30:50 2005
From: proski (Pavel Roskin)
Date: Fri, 18 Nov 2005 10:30:50 -0500
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <200511181353.43811.vda@ilport.com.ua>
References: <437CD1F1.9080300@pcuf.fi> <200511181353.43811.vda@ilport.com.ua>
Message-ID: <1132327850.15814.19.camel@dv>

Hello!

On Fri, 2005-11-18 at 13:53 +0200, Denis Vlasenko wrote:
> On Thursday 17 November 2005 20:54, Jar wrote:
> > 
> > Hello
> > 
> > When using FC4 2.6.12, I have to put the following lines to the end of 
> > the /etc/hotplug/blacklist to get rid of loading orinoco_pci.
> > 
> > # a) Do NOT load orinoco_pci when we are using hostap driver
> > # b) Do NOT load hostap_pci or it's alias wlan1 defined in
> > #    /etc/modprobe.conf, let network service run it instead.
> > orinoco_pci
> > hostap_pci
> > wlan1
[snip]
> > Finally I have to delete orinoco_pci. That is not elegant way to handle 
> > this. What is the _great_ idea to put prism2 device IDs to the orinoco 
> > driver?

The drivers only list devices they support.  The drivers is where this
information is stored for the kernel and userspace utilities.  Drivers
don't scan buses and don't choose whether to support a particular device
or to leave it to another driver.

Not having some supported devices listed in the driver would be a bigger
problem, because if the driver doesn't know whether it supports a
device, how can more generic utilities know that?

> > Is there some other method than the delete method to handle this? What 
> > if I had one orinoco_pci and one hostap_pci device in same PC and I want 
> > to use orinco driver for orinoco and hostap driver for prism2 device?

You should talk to hotplug/udev developers about it.  The mailing list
is at linux-hotplug-devel at lists.sourceforge.net

Blacklisting the driver doesn't look like a flexible solution.  You need
a way to "blacklist" a driver for a device, or better yet, "endorse" a
driver for a device to make sure that no other driver is allowed to use
it.

> Do not build both modules. Or even send patch to remove prism2 dev IDs
> from orinoco.

There is no way such patches will be applied.  The fix doesn't belong to
the driver.

By the way, orinoco_pci only support Prism based cards.  I'm not aware
of any non-prism PCI cards compatible or potentially compatible with
orinoco_pci.  Any "Orinoco PCI cards" are actually supported by
orinoco_plx.

-- 
Regards,
Pavel Roskin




From ahmet  Fri Nov 18 08:19:50 2005
From: ahmet (Ahmet Basagalar)
Date: Fri, 18 Nov 2005 09:19:50 -0700
Subject: Wired authentication on hostapd
Message-ID: <007501c5ec5b$e6e93770$3c05050a@AHMET>

We may need to use hostapd for wired 802.1x authentication, but at the 
moment as you may know it only discovers clients based on DHCP requests. If 
somebody has static IP he does not need to authenticate. I have seen some 
postings about PAE module to make client discovery without DHCP request. Can 
somebody explain the steps to use PAE and also will I need to patch hostapd 
for PAE support?

Thanks,
Ahmet 




From jar  Fri Nov 18 08:45:46 2005
From: jar (Jar)
Date: Fri, 18 Nov 2005 18:45:46 +0200 (EET)
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <1132327850.15814.19.camel@dv>
References: <437CD1F1.9080300@pcuf.fi> <200511181353.43811.vda@ilport.com.ua>
	<1132327850.15814.19.camel@dv>
Message-ID: <1211.192.168.0.150.1132332346.squirrel@kone>


> The drivers only list devices they support.  The drivers is where this
> information is stored for the kernel and userspace utilities.  Drivers
> don't scan buses and don't choose whether to support a particular device
> or to leave it to another driver.
>
> Not having some supported devices listed in the driver would be a bigger
> problem, because if the driver doesn't know whether it supports a
> device, how can more generic utilities know that?

Thanks for this clarification! I have always (wrongly) believed that the driver is
guilty for this. According to you there is nothing wrong even if there is 99
different driver candidates for one single device, right?

> You should talk to hotplug/udev developers about it.  The mailing list
> is at linux-hotplug-devel at lists.sourceforge.net

Seems bug to me or at least something important has been forgotten when implementing
hotplug/udev. I am not familiar with hotplug/udev, but sure the developers know the
problem?

> Blacklisting the driver doesn't look like a flexible solution.  You need
> a way to "blacklist" a driver for a device, or better yet, "endorse" a
> driver for a device to make sure that no other driver is allowed to use
> it.

Blacklisting is better than nothing, now we have nothing. And it really sounds bad
when someone says "delete a module".

> By the way, orinoco_pci only support Prism based cards.

Is there some particular reason to keep the orinoco_pci now when we have hostap_pci?

-- 
Best Regards, Jar



From proski  Fri Nov 18 15:20:20 2005
From: proski (Pavel Roskin)
Date: Fri, 18 Nov 2005 18:20:20 -0500
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <1211.192.168.0.150.1132332346.squirrel@kone>
References: <437CD1F1.9080300@pcuf.fi>
	<200511181353.43811.vda@ilport.com.ua> <1132327850.15814.19.camel@dv>
	<1211.192.168.0.150.1132332346.squirrel@kone>
Message-ID: <1132356020.15814.57.camel@dv>

On Fri, 2005-11-18 at 18:45 +0200, Jar wrote:
> > The drivers only list devices they support.  The drivers is where this
> > information is stored for the kernel and userspace utilities.  Drivers
> > don't scan buses and don't choose whether to support a particular device
> > or to leave it to another driver.
> >
> > Not having some supported devices listed in the driver would be a bigger
> > problem, because if the driver doesn't know whether it supports a
> > device, how can more generic utilities know that?
> 
> Thanks for this clarification! I have always (wrongly) believed that the driver is
> guilty for this. According to you there is nothing wrong even if there is 99
> different driver candidates for one single device, right?

Right.

> > You should talk to hotplug/udev developers about it.  The mailing list
> > is at linux-hotplug-devel at lists.sourceforge.net
> 
> Seems bug to me or at least something important has been forgotten when implementing
> hotplug/udev. I am not familiar with hotplug/udev, but sure the developers know the
> problem?

I'm not sure.  It looks like hotplug is being obsoleted
modules-init-tools:
http://sourceforge.net/mailarchive/message.php?msg_id=11680386

Unfortunately, modprobe only decides which module to load.  As far as I
know, it doesn't tell the driver which devices to use.

OK, I'll write to the list myself.

> > Blacklisting the driver doesn't look like a flexible solution.  You need
> > a way to "blacklist" a driver for a device, or better yet, "endorse" a
> > driver for a device to make sure that no other driver is allowed to use
> > it.
> 
> Blacklisting is better than nothing, now we have nothing.

It's still not quite good in case of 99 modules :-)

>  And it really sounds bad
> when someone says "delete a module".

Yes.

> > By the way, orinoco_pci only support Prism based cards.
> 
> Is there some particular reason to keep the orinoco_pci now when we have hostap_pci?

Because it's more universal.  I can have an Orinoco pcmcia card and a
Prism PCI card and have them both supported by one driver.

Not having orinoco_pci would be like an artificial limitation for users
with Prism PCI cards.

orinoco_pci is good for testing Orinoco backend on embedded systems that
only support MiniPCI.

Development of the orinoco driver is still going on.  Not having
orinoco_pci would limit developers and testers to systems with PCMCIA
bridges (including PLX).

-- 
Regards,
Pavel Roskin




From hualaw  Fri Nov 18 18:29:25 2005
From: hualaw (hua law)
Date: Sat, 19 Nov 2005 10:29:25 +0800
Subject: wonder about management frames communication between kernel space and
	user space
Message-ID: <c2af449f0511181829u77f45d25v86a20c4e09ad0a5a@mail.gmail.com>

I know that the hostap use user space process to handle the athentication
and association request frame.The process includes sending request frames to
the user space and sending back the response frames to the kernel.
 In the driver code, I found the following code in prism2_rx_p80211
function.It seems the kernel drops the frames, why?
  if (type == PRISM2_RX_MGMT && (fc & WLAN_FC_PVER)) {
printk(KERN_DEBUG "%s: dropped management frame with header "
"version %d\n", dev->name, fc & WLAN_FC_PVER);
dev_kfree_skb_any(skb);
return 0;
}
 In hostapd, I found the function hostap_send_mgmt_frame() and they use
send() to send their managemen response, but where the kernel accept the
messages and complete station's management process?
 Help me please!
 Best regard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051119/4b83fac7/attachment.htm 


From mrtheplague  Fri Nov 18 23:21:02 2005
From: mrtheplague (Mr. The Plague)
Date: Sat, 19 Nov 2005 00:21:02 -0700
Subject: Another question about genesis mode
Message-ID: <82736d4f0511182321k47ff41acs98aeec1f9d0b2f2b@mail.gmail.com>

A while back, I thought I hosed my card and required genesis mode repair. My
problem was just an interrupt conflict. I don't think that's the case this
time...

My card gives *no* signs of life. Inserting it gives an error in syslog from
the PCMCIA driver:

cs: pcmcia_socket0: time out after reset.

And that's all I get on either of my machines.

Is there help for me?

Thanks,
mtp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051119/8c4b4819/attachment.htm 


From vda  Sat Nov 19 03:31:35 2005
From: vda (Denis Vlasenko)
Date: Sat, 19 Nov 2005 13:31:35 +0200
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <1132356020.15814.57.camel@dv>
References: <437CD1F1.9080300@pcuf.fi>
	<1211.192.168.0.150.1132332346.squirrel@kone>
	<1132356020.15814.57.camel@dv>
Message-ID: <200511191331.35969.vda@ilport.com.ua>

On Saturday 19 November 2005 01:20, Pavel Roskin wrote:

> > > By the way, orinoco_pci only support Prism based cards.
> > 
> > Is there some particular reason to keep the orinoco_pci now when we have hostap_pci?
> 
> Because it's more universal.  I can have an Orinoco pcmcia card and a
> Prism PCI card and have them both supported by one driver.
> 
> Not having orinoco_pci would be like an artificial limitation for users
> with Prism PCI cards.
> 
> orinoco_pci is good for testing Orinoco backend on embedded systems that
> only support MiniPCI.
> 
> Development of the orinoco driver is still going on.  Not having
> orinoco_pci would limit developers and testers to systems with PCMCIA
> bridges (including PLX).

I don't quite understand you. Let me ask it another way: is it possible
to make hostap and orinoco drivers to support disjoint sets of devices?
--
vda 



From jar  Sat Nov 19 06:24:43 2005
From: jar (Jar)
Date: Sat, 19 Nov 2005 16:24:43 +0200
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <1132356020.15814.57.camel@dv>
References: <437CD1F1.9080300@pcuf.fi>	 <200511181353.43811.vda@ilport.com.ua>
	<1132327850.15814.19.camel@dv>	
	<1211.192.168.0.150.1132332346.squirrel@kone>
	<1132356020.15814.57.camel@dv>
Message-ID: <437F35AB.6000703@pcuf.fi>

Pavel Roskin wrote:
>>>By the way, orinoco_pci only support Prism based cards.
>>
>>Is there some particular reason to keep the orinoco_pci now when we have hostap_pci?
> 
> Because it's more universal.  I can have an Orinoco pcmcia card and a
> Prism PCI card and have them both supported by one driver.

But how good the Prism2 support actually is? Orinoco drivers can't 
support WPA. So Prism2 users ends up to use orinoco driver without 
important WPA security. With hostap driver they can get all the flavours.

> Not having orinoco_pci would be like an artificial limitation for users
> with Prism PCI cards.

It is now limitation for the Prism users and users who want to use it as 
access point when the system wants to load orinoco drivers (pcmcia, pci) 
instead of hostap_xxx.

> orinoco_pci is good for testing Orinoco backend on embedded systems that
> only support MiniPCI.
> 
> Development of the orinoco driver is still going on.  Not having
> orinoco_pci would limit developers and testers to systems with PCMCIA
> bridges (including PLX).

Maybe you should concentrate to support Hermes I and WPA. In my opinion 
  when the two drivers supports the same hardware it is waste of time.
Particularly when the hostap driver is somewhat 100% complete for 
present day's wireless use.

The situation would be different if the hostap has some weaknesses when 
the another driver hasn't. But the hostap driver does it's job well, for 
me over two years now 365d/24h and it's security features are also up to 
date.

I have also orinoco cards and naturally want to use orinoco driver for 
them. But at least with Lucent fw:8.72 sometimes the system gives me 
"interrupt delivery" warnings and the orinoco_cs resets the card when I 
use it in monitor mode together with Kismet.

-- 
Best Regards, Jar



From proski  Sat Nov 19 09:49:32 2005
From: proski (Pavel Roskin)
Date: Sat, 19 Nov 2005 12:49:32 -0500
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <437F35AB.6000703@pcuf.fi>
References: <437CD1F1.9080300@pcuf.fi>
	<200511181353.43811.vda@ilport.com.ua> <1132327850.15814.19.camel@dv>
	<1211.192.168.0.150.1132332346.squirrel@kone>
	<1132356020.15814.57.camel@dv> <437F35AB.6000703@pcuf.fi>
Message-ID: <20051119124932.cpzxcgso44g8c8g4@webmail.spamcop.net>

Quoting Jar <jar at pcuf.fi>:

> Maybe you should concentrate to support Hermes I and WPA. In my opinion
>   when the two drivers supports the same hardware it is waste of time.
> Particularly when the hostap driver is somewhat 100% complete for
> present day's wireless use.

I think you overestimate how many efforts went into orinoco_pci.  PCMCIA and USB
frontends have been actually much more time consuming.

Anyway, I'll follow your advice.

--
Regards,
Pavel Roskin



From jar  Sat Nov 19 10:54:00 2005
From: jar (Jar)
Date: Sat, 19 Nov 2005 20:54:00 +0200
Subject: Hostap_pci vs. orinoco_pci
In-Reply-To: <20051119124932.cpzxcgso44g8c8g4@webmail.spamcop.net>
References: <437CD1F1.9080300@pcuf.fi>	<200511181353.43811.vda@ilport.com.ua>
	<1132327850.15814.19.camel@dv>	<1211.192.168.0.150.1132332346.squirrel@kone>	<1132356020.15814.57.camel@dv>
	<437F35AB.6000703@pcuf.fi>
	<20051119124932.cpzxcgso44g8c8g4@webmail.spamcop.net>
Message-ID: <437F74C8.4010203@pcuf.fi>

Pavel Roskin wrote:

> I think you overestimate how many efforts went into orinoco_pci.  PCMCIA and USB
> frontends have been actually much more time consuming.

Yes you are right. I am not a kernel programmer (just a Linux user). But 
I mean the driver maintenance, why to maintenance things twice. But as 
you say I may be wrong. You are a programmer and the driver author, so 
you know the best.

> Anyway, I'll follow your advice.

I don't want to advise, I don't even have enough skills to advise 
anybody. These are my personal thoughts only. Actually I want to thank 
you for all the effort you've put into Linux and Linux Wireless.

Basically I need both drivers (orinoco and hostap) but the live with 
them in same system has become difficult, but that is not a driver fault 
as you say. Maybe I am frustrated and that's why I am crying for these 
things.

Orinoco driver has been the only driver for Hermes/Prism cards for a 
long time now, but the things has been changed, the hostap has become 
part of the kernel. I hope the WPA functionality would also be part of 
the orinoco driver in near future.

-- 
Best Regards, Jar



From stephan.schlumbohm  Sat Nov 19 13:14:45 2005
From: stephan.schlumbohm (Stephan Schlumbohm)
Date: Sat, 19 Nov 2005 13:14:45 -0800
Subject: Handoff with wpa_supplicant and madwifi driver
Message-ID: <000001c5ed4e$478e3060$4c01a8c0@stephansmobile>

Hi all,

I'm having serious trouble with the handoff from one access point to another using wpa_supplicant (stable 0.3.8 and development 0.4.6) with the madwifi driver (madwifi-ng latest svn snapshot from madwifi.org).

Both access points have the same ESSID and operate on the same channel and have the same security settings. In fact, those access points are mesh access points - both are connected to a FreeRADIUS server.

Authentication (Open, WPA-PSK, WPA-802.1X-TLS/PEAP/TTLS) works fine in this setup to each access point.

But, when I try to roam from one access point to another, wpa_supplicant does not initiate a reassociation request to the new access point. Instead, it disassociates the old access point, then it performs the scanning and then finally goes through a full new authentication with the new access point.

This causes the handoff to take about 1.5 to 3 seconds. This is not acceptable and is not intended by the developers. A single channel handoff should take about 10 to 300 ms (depending on authentication).

Is this a problem in wpa_supplicant or in the madwifi-driver?

Has anyone the handoff with wpa_supplicant and madwifi working successfully?

Here's the debug output from wpa_supplicant 0.3.8 performing a couple of WPA-PSK handoffs:


EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
**************** HANDOFF 1 **********************************************
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:0d:97:04:04:12 into blacklist
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:97:04:04:12
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:97:04:04:12
No keys have been configured - skip key clearing
Associated with 00:0d:97:04:04:12
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0d:97:04:04:12
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 02 8a 00 10 00 00 00 00 00 00 00 06 a1 5d 6c ec 7d ce c2 2f 16 1a 17 32 b8 17 10
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 02 8a 00 10 00 00 00 00 00 00 00 06 a1 5d 6c ec 7d ce c2 2f 16 1a 17 30
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:12 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 74 da c9 ad 96 3a f5 e3 dc be 7a 57 78 50 f8 ca 29 1b 2d 74 26 f1 bf ff 0d 41 4c bd9
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 35 14 56 c2 f3 c5 8b f9 72 ad fc 03 73 29 36 60
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 12 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 870 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 1
0: 00:0d:97:04:04:10 ssid='Test' wpa_ie_len=28 rsn_ie_len=0
   selected
Trying to associate with 00:0d:97:04:04:10 (SSID='Test' freq=2462 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b1a len=33
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:97:04:04:10
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:97:04:04:10
No keys have been configured - skip key clearing
Associated with 00:0d:97:04:04:10
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50 d3 cd 80
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): be 6a 04 68 c0 12 f1 c8 3b 43 59 40 62 d3 cc 3d 3b 56 39 73 b6 fc aa c2 a5 f0 44 a9b
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): f6 48 a4 69 d9 3f 94 e0 2f 75 64 d9 f1 bf 26 3d
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28 idleWhile=58
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27 idleWhile=57
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=26 idleWhile=56
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 02 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50 d3 cd 80
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 02 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): be 86 c1 1e 06 d4 1f d7 b2 8c 28 f8 c5 40 53 24
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=23 idleWhile=53
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=22 idleWhile=52
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=21 idleWhile=51
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 03 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50 d3 cd 80
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 03 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): f0 d2 39 81 38 db 08 bb 9b 57 92 82 1f a5 ed 14
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=127): 01 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 04 13 e6 b2 92 7e 3f 4c ff 16 57 e9 50 d3 cd 2
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=123
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=127): 01 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 04 13 e6 b2 92 7e 3f 4c ff 16 57 e9 2
WPA: RX message 3 of 4-Way Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: IE KeyData - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 5f fe 01 0a 00 10 00 00 00 000
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=139): 01 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 05 53 2c 64 c6 0b 4b e7 cb e6 ff 0a 60 13 f9 1
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=135
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=139): 01 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 05 53 2c 64 c6 0b 4b e7 cb e6 ff 0a 1
WPA: RX message 1 of Group Key Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=1 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key 2/2 - hexdump(len=113): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 5f fe 03 12 00 20 00 00 00 000
WPA: Key negotiation completed with 00:0d:97:04:04:10 [PTK=CCMP GTK=TKIP]
Cancelling authentication timeout
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20 idleWhile=50
...
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
************************* HANDOFF 2 *************************************
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:0d:97:04:04:10 into blacklist
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:97:04:04:10
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:97:04:04:10
No keys have been configured - skip key clearing
Associated with 00:0d:97:04:04:10
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0d:97:04:04:10
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 02 8a 00 10 00 00 00 00 00 00 00 06 6d 2f 3d 95 85 7c 69 fa be fd e9 56 d6 53 40
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 02 8a 00 10 00 00 00 00 00 00 00 06 6d 2f 3d 95 85 7c 69 fa be fd e9 50
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:10 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): fc af c6 ff 8f bf 6d 4b 6c 24 d7 d7 83 64 12 d9 d6 ff c6 18 3f 6b d7 83 94 e8 ef 908
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): b4 83 d1 10 2d 6d 0e 0c b7 74 42 9e 20 33 49 3c
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 10 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 870 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 1
0: 00:0d:97:04:04:07 ssid='Test' wpa_ie_len=28 rsn_ie_len=0
   selected
Trying to associate with 00:0d:97:04:04:07 (SSID='Test' freq=2462 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b1a len=33
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:97:04:04:07
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:97:04:04:07
No keys have been configured - skip key clearing
Associated with 00:0d:97:04:04:07
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RX EAPOL from 00:0d:97:04:04:07
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 49 6e 86 05 a5 f5 ad 0c 8d 1e c9 84 21 c9 10
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 49 6e 86 05 a5 f5 ad 0c 8d 1e c9 80
WPA: RX message 1 of 4-Way Handshake from 00:0d:97:04:04:07 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 34 d1 fd 73 bc 97 36 30 5a 1d 2b 03 6c 87 74 f0 63 9d 35 c2 dc 5e e8 60 6e 5c 2d 30a
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): fa 42 5d de 71 68 dc 60 83 38 ff e3 94 03 b8 c0
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0d 97 04 04 07 00 02 6f 21 1d 6b 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 002
RX EAPOL from 00:0d:97:04:04:07
RX EAPOL - hexdump(len=127): 01 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 49 6e 86 05 a5 f5 ad 0c 8d 1e c9 84 21 c9 2
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=123
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=127): 01 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 49 6e 86 05 a5 f5 ad 0c 8d 1e c9 2
WPA: RX message 3 of 4-Way Handshake from 00:0d:97:04:04:07 (ver=2)
WPA: IE KeyData - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 f2 04 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 0d 97 04 04 07 00 02 6f 21 1d 6b 88 8e 01 03 00 5f fe 01 0a 00 10 00 00 00 000
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28 idleWhile=58
RX EAPOL from 00:0d:97:04:04:07
RX EAPOL - hexdump(len=139): 01 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 61 a6 a7 d1 b8 e1 35 c6 fb 6e f4 63 e3 f1 3
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=135
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=139): 01 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 61 a6 a7 d1 b8 e1 35 c6 fb 6e f4 3
WPA: RX message 1 of Group Key Handshake from 00:0d:97:04:04:07 (ver=2)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=1 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key 2/2 - hexdump(len=113): 00 0d 97 04 04 07 00 02 6f 21 1d 6b 88 8e 01 03 00 5f fe 03 12 00 20 00 00 00 000
WPA: Key negotiation completed with 00:0d:97:04:04:07 [PTK=CCMP GTK=TKIP]
Cancelling authentication timeout
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27 idleWhile=57
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=26 idleWhile=56
...



Cheers,

Stephan




From bryan  Sat Nov 19 17:10:33 2005
From: bryan (Bryan Kadzban)
Date: Sat, 19 Nov 2005 20:10:33 -0500
Subject: Handoff with wpa_supplicant and madwifi driver
In-Reply-To: <000001c5ed4e$478e3060$4c01a8c0@stephansmobile>
References: <000001c5ed4e$478e3060$4c01a8c0@stephansmobile>
Message-ID: <437FCD09.5010507@kadzban.is-a-geek.net>

Stephan Schlumbohm wrote:
> But, when I try to roam from one access point to another, 
> wpa_supplicant does not initiate a reassociation request to the new 
> access point.

It's not supposed to -- userspace does not generally (AFAIK anyway)
handle management frames of any kind.

> Instead, it disassociates the old access point, then it performs the 
> scanning and then finally goes through a full new authentication with
> the new access point.

Try looking at the various different ap_scan modes; it sounds like you
want one where the driver does the scanning and roaming.  But note that
not all drivers support all modes (or at least, I've heard that not all
of them support ap_scan=2, anyway -- I only use the Windows port at
work, so I only have to deal with the NDIS driver, which does support
that mode).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051119/09190ecf/attachment.pgp 


From engage  Sat Nov 19 19:29:54 2005
From: engage (engage)
Date: Sat, 19 Nov 2005 20:29:54 -0700
Subject: wpa_supplicant & winpcap & windows 2000
Message-ID: <200511192029.54712.engage@n0sq.us>

I'm trying to get wpa_supplicant running on Win2K. I keep getting a box that 
the dll files aren't in the path even though the winpcap dll's are in 
WINNT/system32. Is there something else I need to check?



From jkmaline  Sat Nov 19 19:32:28 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 19 Nov 2005 19:32:28 -0800
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <200511192029.54712.engage@n0sq.us>
References: <200511192029.54712.engage@n0sq.us>
Message-ID: <20051120033228.GA9047@jm.kir.nu>

On Sat, Nov 19, 2005 at 08:29:54PM -0700, engage wrote:

> I'm trying to get wpa_supplicant running on Win2K. I keep getting a box that 
> the dll files aren't in the path even though the winpcap dll's are in 
> WINNT/system32. Is there something else I need to check?

Which version of wpa_supplicant are you trying to use? If you haven't
tried the latest one (0.4.6), please re-test with that.

Does the error message give any other information, e.g., the name of
missing DLLs?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 19 19:37:55 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 19 Nov 2005 19:37:55 -0800
Subject: [PATCH] adding wpa_common.h
In-Reply-To: <20051117105010.GA28712@lenst.det.unifi.it>
References: <20051117105010.GA28712@lenst.det.unifi.it>
Message-ID: <20051120033755.GB9047@jm.kir.nu>

On Thu, Nov 17, 2005 at 11:50:10AM +0100, Leonardo Maccari wrote:

> into hostapd.c, now I'm thinkng how to port all the functions needed by
> wpa_sm_ctx. as said before it would be easier if files in different
> packages could have different names (wpa.c has the same name in
> wpa_supplicant and hostapd, it would be easier if it was named wpa_s.c and
> wpa_a.c or whatever), that would save some rename or hardlink for
> compilation.

That is unlikely to happen, so using subdirectories would probably be
easier way to resolve that.

Please re-diff your changes with -N option for diff so that the new file
(wpa_common.h) is included.

-- 
Jouni Malinen                                            PGP id EFC895FA



From engage  Sat Nov 19 20:13:15 2005
From: engage (engage)
Date: Sat, 19 Nov 2005 21:13:15 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <20051120033228.GA9047@jm.kir.nu>
References: <200511192029.54712.engage@n0sq.us>
	<20051120033228.GA9047@jm.kir.nu>
Message-ID: <200511192113.15876.engage@n0sq.us>

On Saturday 19 November 2005 08:32 pm, Jouni Malinen wrote:
>On Sat, Nov 19, 2005 at 08:29:54PM -0700, engage wrote:
>> I'm trying to get wpa_supplicant running on Win2K. I keep getting a box
>> that the dll files aren't in the path even though the winpcap dll's are in
>> WINNT/system32. Is there something else I need to check?
>
>Which version of wpa_supplicant are you trying to use? If you haven't
>tried the latest one (0.4.6), please re-test with that.

I'm using the latest stable release 0.3.9.

>
>Does the error message give any other information, e.g., the name of
>missing DLLs?

No, it doesn't.



From jkmaline  Sat Nov 19 20:39:06 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 19 Nov 2005 20:39:06 -0800
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <200511192113.15876.engage@n0sq.us>
References: <200511192029.54712.engage@n0sq.us>
	<20051120033228.GA9047@jm.kir.nu>
	<200511192113.15876.engage@n0sq.us>
Message-ID: <20051120043906.GD9047@jm.kir.nu>

On Sat, Nov 19, 2005 at 09:13:15PM -0700, engage wrote:

> I'm using the latest stable release 0.3.9.

Please try 0.4.6. If I remember correctly, one of the fixes included in
it for Win2k was indeed resolving an issue with libpcap DLL (either
winpcap.dll or packet.dll was being loaded without .dll and Win2k did
not like that).

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Sun Nov 20 05:42:51 2005
From: bryan (Bryan Kadzban)
Date: Sun, 20 Nov 2005 08:42:51 -0500
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <43701B8D.4040609@kadzban.is-a-geek.net>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>	<20051106194053.GM9194@jm.kir.nu>	<436E86E3.3050606@kadzban.is-a-geek.net>
	<43701B8D.4040609@kadzban.is-a-geek.net>
Message-ID: <43807D5B.5050001@kadzban.is-a-geek.net>

Bryan Kadzban wrote:
> This works fine -- the WMP54GS driver does update its BSSID list soon
> enough after an association that we've never gotten the old IEs.
> 
> I would send a patch, but since I made the changes while at work, I'm
> not entirely sure who owns them.  If you can't reimplement the
> changes based on this description, let me know and I'll see if I can
> get them to release it under a dual-BSD-GPL license, to match
> wpa_supplicant.

So should I try to do this, or was my description enough?

> When wpa_supplicant.c calls wpa_drv_scan, that ends up calling into 
> wpa_driver_ndis_scan.  That function checks drv->radio_enabled, and
> if that flag isn't set, it calls wpa_driver_ndis_disconnect (which
> sets the current SSID to a 32-byte random value).
> 
> When wpa_supplicant is configured in ap_scan=2 mode and using the
> NDIS driver, wpa_driver_ndis_scan never gets called on startup.
> Instead, the code just associates with the first SSID in the config
> file.  (In ap_scan=1 mode, wpa_supplicant does indeed call
> wpa_drv_scan during its startup.)  So when the control interface
> requests a scan, radio_enabled is 0, because the driver was never
> told to scan the first time around.
> 
> So the first control interface scan ends up setting the SSID to a
> random string.  (In the log, this is the point where it says "NDIS:
> turning radio on before the first scan", line 549.)  This is what
> breaks the association, and I'm pretty sure it's also what causes all
> the failures later.

Any ideas on this one?

Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051120/7b489435/attachment.pgp 


From eitanb  Sun Nov 20 07:07:26 2005
From: eitanb (Bar, Eitan)
Date: Sun, 20 Nov 2005 17:07:26 +0200
Subject: switch to (really) CONNECTED state in wpa_supplicant 0.3.9
Message-ID: <C08C15DE99919148ACF278138C3CEC413BE6B9@dile01.ent.ti.com>

Hi,

 

I would like to insert my own hook into wpa_supplicant 0.3.9 to be called after STA is (really) associated and all key negotiation is complete.

Is there such a spot in the code?

When not working with security, I would just patch into the EVENT_ASSOC handler, but whenever using security, this will not work.

 

Can anyone please point out the perfect spot to do that?

 

Thanks!

 Eitan

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051120/85bf1426/attachment.htm 


From jkmaline  Sun Nov 20 10:55:16 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 10:55:16 -0800
Subject: switch to (really) CONNECTED state in wpa_supplicant 0.3.9
In-Reply-To: <C08C15DE99919148ACF278138C3CEC413BE6B9@dile01.ent.ti.com>
References: <C08C15DE99919148ACF278138C3CEC413BE6B9@dile01.ent.ti.com>
Message-ID: <20051120185516.GB9169@jm.kir.nu>

On Sun, Nov 20, 2005 at 05:07:26PM +0200, Bar, Eitan wrote:

> I would like to insert my own hook into wpa_supplicant 0.3.9 to be called after STA is (really) associated and all key negotiation is complete.
> 
> Is there such a spot in the code?

There is probably not a single place in 0.3.9 for this, but I did change
0.4.x to allow this to be done easily. In other words, you could either
move to 0.4.x or try to port the change to 0.3.x. The place to look for
this is in wpa_supplicant_set_state() in wpa_supplicant.c and the place
where wpa_msg() is called with WPA_EVENT_CONNECTED prefix.

-- 
Jouni Malinen                                            PGP id EFC895FA



From engage  Sun Nov 20 11:53:27 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 12:53:27 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <20051120043906.GD9047@jm.kir.nu>
References: <200511192029.54712.engage@n0sq.us>
	<200511192113.15876.engage@n0sq.us>
	<20051120043906.GD9047@jm.kir.nu>
Message-ID: <200511201253.28056.engage@n0sq.us>

On Saturday 19 November 2005 09:39 pm, Jouni Malinen wrote:
>On Sat, Nov 19, 2005 at 09:13:15PM -0700, engage wrote:
>> I'm using the latest stable release 0.3.9.
>
>Please try 0.4.6. If I remember correctly, one of the fixes included in
>it for Win2k was indeed resolving an issue with libpcap DLL (either
>winpcap.dll or packet.dll was being loaded without .dll and Win2k did
>not like that).

wpa_supplicant-windows-bin-0.4.6 eliminated that problem. But, I'm wondering 
if the 11g cards that I have can do WPA2. I've tried all combinations for 
CCMP and I can get an association. My Netgear WG511 PC card & Linksys 
WPC54Gv2 are WPA-PSK capable but there are no driver updates for these cards 
that enables WPA2. Time to spend more money?



From jkmaline  Sun Nov 20 12:08:58 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 12:08:58 -0800
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <43701B8D.4040609@kadzban.is-a-geek.net>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>
	<20051106194053.GM9194@jm.kir.nu>
	<436E86E3.3050606@kadzban.is-a-geek.net>
	<43701B8D.4040609@kadzban.is-a-geek.net>
Message-ID: <20051120200858.GC9169@jm.kir.nu>

On Mon, Nov 07, 2005 at 10:29:17PM -0500, Bryan Kadzban wrote:

> I added code to request OID_802_11_BSSID_LIST, then iterate through the
> results looking for a result that has a BSSID matching drv->bssid.  When
> I find the first one, I check its ->IELength and make sure that's bigger
> than the size of the NDIS_802_11_FIXED_IEs structure.  Then I set
> assoc_info.beacon_ies to ->IEs + sizeof(NDIS_802_11_FIXED_IEs), and I
> set assoc_info.beacon_ies_len to ->IELength - sizeof(that-structure).
> 
> Then I call wpa_supplicant_event(..., EVENT_ASSOCINFO, ...);.
> 
> This works fine -- the WMP54GS driver does update its BSSID list soon
> enough after an association that we've never gotten the old IEs.

Thanks! This sounds like a reasonable thing to do. I modified
driver_ndis.c to do this.

> One possible fix might be to find somewhere else in driver_ndis.c to set
> drv->radio_enabled, so that it gets set no matter what the ap_scan mode
> is.  I haven't tried this, but I'm guessing it'd work.

This is indeed the proper way to fix this. set_ssid() is now doing this
and this change seemed to fix the problem in ap_scan=2 mode.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Sun Nov 20 13:18:10 2005
From: bryan (Bryan Kadzban)
Date: Sun, 20 Nov 2005 16:18:10 -0500
Subject: NDIS driver / changing RSN IEs
In-Reply-To: <20051120200858.GC9169@jm.kir.nu>
References: <20051031185250.GA18468@kadzban.is-a-geek.net>	<20051106194053.GM9194@jm.kir.nu>	<436E86E3.3050606@kadzban.is-a-geek.net>	<43701B8D.4040609@kadzban.is-a-geek.net>
	<20051120200858.GC9169@jm.kir.nu>
Message-ID: <4380E812.1090307@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> Thanks! This sounds like a reasonable thing to do. I modified 
> driver_ndis.c to do this.

Our version now matches (well, it's close enough at least) the official
one, woohoo!  Easy upgrades again!  ;-)

> This is indeed the proper way to fix this. set_ssid() is now doing
> this and this change seemed to fix the problem in ap_scan=2 mode.

Great!  I'll probably try the next release to double-check, but from the
webcvs diffs, it does look like that should fix it.

Thank you!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051120/17f19275/attachment.pgp 


From engage  Sun Nov 20 13:20:02 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 14:20:02 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <200511201253.28056.engage@n0sq.us>
References: <200511192029.54712.engage@n0sq.us>
	<20051120043906.GD9047@jm.kir.nu>
	<200511201253.28056.engage@n0sq.us>
Message-ID: <200511201420.02875.engage@n0sq.us>

On Sunday 20 November 2005 12:53 pm, engage wrote:
>On Saturday 19 November 2005 09:39 pm, Jouni Malinen wrote:
>>On Sat, Nov 19, 2005 at 09:13:15PM -0700, engage wrote:
>>> I'm using the latest stable release 0.3.9.
>>
>>Please try 0.4.6. If I remember correctly, one of the fixes included in
>>it for Win2k was indeed resolving an issue with libpcap DLL (either
>>winpcap.dll or packet.dll was being loaded without .dll and Win2k did
>>not like that).
>
>wpa_supplicant-windows-bin-0.4.6 eliminated that problem. But, I'm wondering
>if the 11g cards that I have can do WPA2. I've tried all combinations for
>CCMP and I can get an association. My Netgear WG511 PC card & Linksys
>WPC54Gv2 are WPA-PSK capable but there are no driver updates for these cards
>that enables WPA2. Time to spend more money?

I messed up when trying to use the Netgear card. I got it somewhat working but 
the connection is rapidly going up and down. Here is the log:

Initializing interface '\Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}' 
conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A'
Configuration file 'wpa_supplicant.conf' -> 'C:
\MyDownloadFiles\WPA/wpa_supplicant.conf'
Reading configuration file 'C:\MyDownloadFiles\WPA/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
   id=0 ssid='$$$$$$$$$$$$$'
Initializing interface (2) 
'\Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3, 1, 0, 27
NDIS: 2 adapter names found
NDIS: 2 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericDialupAdapter - Generic dialup adapter
NDIS: 1 - \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9} - NETGEAR WG511 
54 Mbps Wireless PC Card
NDIS: Adapter description prefix 'NETGEAR WG511 54 Mbps Wireless PC Card'
ndis_get_oid: oid=0xd010122 len (512) failed
NDIS: verifying driver WPA capability
NDIS: WPA key management supported
NDIS: WPA-PSK key management supported
NDIS: CCMP encryption supported
NDIS: TKIP encryption supported
NDIS: driver supports WPA
NDIS: driver capabilities: key_mgmt 0x5 enc 0xc auth 0x3
Own MAC address: 00:09:5b:e9:19:ac
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
Setting scan request: 0 sec 100000 usec
Added interface \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
     4b 49 37 52 57                                    $$$$$$$$$$$$$           
NDIS: turning radio on before the first scan
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 1
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='$$$$$$$$$$$$$' wpa_ie_len=26 rsn_ie_len=0 caps=0x10
   selected based on WPA IE
Trying to associate with 00:12:17:e2:8d:05 (SSID='$$$$$$$$$$$$$' freq=2462 
MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 04 01 
00 00 50 f2 04 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
ndis_set_oid: oid=0xd010119 len (4) failed
NDIS: Failed to set OID_802_11_PRIVACY_FILTER (1)
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
ndis_get_oid: oid=0xd010101 len (6) failed
RX EAPOL from 00:12:17:e2:8d:05
Setting authentication timeout: 10 sec 0 usec
NDIS: ReqFixed=0x0 RespFixed=0x7 off_req=40 off_resp=87 len_req=47 len_resp=24
Association info event
req_ies - hexdump(len=47): 00 05 4b 49 37 52 57 01 04 02 04 0b 16 32 08 0c 12 
18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 
00 50 f2 02
resp_ies - hexdump(len=24): 01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 12 98 60 dd 
06 00 10 18 02 02 04
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:12:17:e2:8d:05
No keys have been configured - skip key clearing
Associated with 00:12:17:e2:8d:05
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:12:17:e2:8d:05 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): b3 12 4d c8 43 bb 8b a6 1f 03 5a 7d 09 
38 25 1f 5d d4 cb fc 96 f5 45 3b 13 0d 89 0a 1c db ae 32
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:12:17:e2:8d:05
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=121
  EAPOL-Key type=254
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
RX EAPOL from 00:12:17:e2:8d:05
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Authentication with 00:12:17:e2:8d:05 timed out.
Added BSSID 00:12:17:e2:8d:05 into blacklist
State: 4WAY_HANDSHAKE -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
ndis_get_oid: oid=0xd010101 len (6) failed
BSSID 00:12:17:e2:8d:05 blacklist count incremented to 2
State: SCANNING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 1
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='$$$$$$$$$$$$$' wpa_ie_len=26 rsn_ie_len=0 caps=0x10
   skip - blacklisted
No APs found - clear blacklist and try again
Removed BSSID 00:12:17:e2:8d:05 from blacklist (clear)
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='$$$$$$$$$$$$$' wpa_ie_len=26 rsn_ie_len=0 caps=0x10
   selected based on WPA IE
Trying to associate with 00:12:17:e2:8d:05 (SSID='$$$$$$$$$$$$$' freq=2462 
MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 04 01 
00 00 50 f2 04 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: DISCONNECTED -> ASSOCIATING
ndis_set_oid: oid=0xd010119 len (4) failed
NDIS: Failed to set OID_802_11_PRIVACY_FILTER (1)
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
RX EAPOL from 00:12:17:e2:8d:05
NDIS: ReqFixed=0x0 RespFixed=0x7 off_req=40 off_resp=87 len_req=47 len_resp=24
Association info event
req_ies - hexdump(len=47): 00 05 4b 49 37 52 57 01 04 02 04 0b 16 32 08 0c 12 
18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 
00 50 f2 02
resp_ies - hexdump(len=24): 01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 12 98 60 dd 
06 00 10 18 02 02 04
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:12:17:e2:8d:05
No keys have been configured - skip key clearing
Associated with 00:12:17:e2:8d:05
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:12:17:e2:8d:05 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): f6 22 91 9d e1 8b 1f da b0 ca 99 02 b9 
72 9d 49 2c 80 7e c5 99 d5 e9 80 b2 ea c9 cc 53 bf 67 d6
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:12:17:e2:8d:05
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=121
  EAPOL-Key type=254
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
RX EAPOL from 00:12:17:e2:8d:05
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}
State: 4WAY_HANDSHAKE -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_ndis_set_wpa: enabled=0
No keys have been configured - skip key clearing
Cancelling scan request



From jkmaline  Sun Nov 20 16:09:41 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 16:09:41 -0800
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <200511201420.02875.engage@n0sq.us>
References: <200511192029.54712.engage@n0sq.us>
	<20051120043906.GD9047@jm.kir.nu>
	<200511201253.28056.engage@n0sq.us>
	<200511201420.02875.engage@n0sq.us>
Message-ID: <20051121000941.GA9524@jm.kir.nu>

On Sun, Nov 20, 2005 at 02:20:02PM -0700, engage wrote:

> IEEE 802.1X RX: version=1 type=3 length=95
>   EAPOL-Key type=254
> State: ASSOCIATED -> 4WAY_HANDSHAKE
> WPA: RX message 1 of 4-Way Handshake from 00:12:17:e2:8d:05 (ver=2)
> WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
> 01 00 00 50 f2 04 01 00 00 50 f2 02
> WPA: Renewed SNonce - hexdump(len=32): b3 12 4d c8 43 bb 8b a6 1f 03 5a 7d 09 
> 38 25 1f 5d d4 cb fc 96 f5 45 3b 13 0d 89 0a 1c db ae 32
> WPA: PMK - hexdump(len=32): [REMOVED]
> WPA: PTK - hexdump(len=64): [REMOVED]
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:12:17:e2:8d:05
> Setting authentication timeout: 10 sec 0 usec
> IEEE 802.1X RX: version=1 type=3 length=121
>   EAPOL-Key type=254

It looks like the first two messages of WPA 4-Way Handshake are
correctly received. However, something odd happens with the third
message:

> WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
> WPA: Could not verify EAPOL-Key MIC - dropping packet

It looks like the AP accepted message 2/4, but then send out message 3/4
with incorrect MIC. This is quite odd behavior.. What AP (vendor/model)
are you using?

> RX EAPOL from 00:12:17:e2:8d:05
> IEEE 802.1X RX: version=1 type=3 length=119
>   EAPOL-Key type=254
> WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
> WPA: Could not verify EAPOL-Key MIC - dropping packet

Interestingly, this frame is two bytes shorter than the previous frame
even though I would have assumed this to be a retransmitted message
3/4..

Could you please send me debug log with -dd on the command line so that
these two frames are included in full in the log? In addition, if you
happen to have Ethereal installed or can install it easily, it would be
nice to receive a capture log from the network interface with these
EAPOL-Key frames.

-- 
Jouni Malinen                                            PGP id EFC895FA



From engage  Sun Nov 20 17:34:34 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 18:34:34 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <20051121000941.GA9524@jm.kir.nu>
References: <200511192029.54712.engage@n0sq.us>
	<200511201420.02875.engage@n0sq.us>
	<20051121000941.GA9524@jm.kir.nu>
Message-ID: <200511201834.35459.engage@n0sq.us>

On Sunday 20 November 2005 05:09 pm, Jouni Malinen wrote:
>On Sun, Nov 20, 2005 at 02:20:02PM -0700, engage wrote:
>> IEEE 802.1X RX: version=1 type=3 length=95
>>   EAPOL-Key type=254
>> State: ASSOCIATED -> 4WAY_HANDSHAKE
>> WPA: RX message 1 of 4-Way Handshake from 00:12:17:e2:8d:05 (ver=2)
>> WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50
>> f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
>> WPA: Renewed SNonce - hexdump(len=32): b3 12 4d c8 43 bb 8b a6 1f 03 5a 7d
>> 09 38 25 1f 5d d4 cb fc 96 f5 45 3b 13 0d 89 0a 1c db ae 32
>> WPA: PMK - hexdump(len=32): [REMOVED]
>> WPA: PTK - hexdump(len=64): [REMOVED]
>> WPA: Sending EAPOL-Key 2/4
>> RX EAPOL from 00:12:17:e2:8d:05
>> Setting authentication timeout: 10 sec 0 usec
>> IEEE 802.1X RX: version=1 type=3 length=121
>>   EAPOL-Key type=254
>
>It looks like the first two messages of WPA 4-Way Handshake are
>correctly received. However, something odd happens with the third
>
>message:
>> WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
>> WPA: Could not verify EAPOL-Key MIC - dropping packet
>
>It looks like the AP accepted message 2/4, but then send out message 3/4
>with incorrect MIC. This is quite odd behavior.. What AP (vendor/model)
>are you using?

Linksys WRT54Gv2.2 with firmware v4.20.7, Aug. 18, 2005

>
>> RX EAPOL from 00:12:17:e2:8d:05
>> IEEE 802.1X RX: version=1 type=3 length=119
>>   EAPOL-Key type=254
>> WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
>> WPA: Could not verify EAPOL-Key MIC - dropping packet
>
>Interestingly, this frame is two bytes shorter than the previous frame
>even though I would have assumed this to be a retransmitted message
>3/4..
>
>Could you please send me debug log with -dd on the command line so that
>these two frames are included in full in the log? In addition, if you
>happen to have Ethereal installed or can install it easily, it would be
>nice to receive a capture log from the network interface with these
>EAPOL-Key frames.

No, I haven't used ethereal in a long time but I guess now is a good time to 
get re-acquainted with it.

Here's the out with -dd:


Initializing interface '\Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}' 
conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A'
Configuration file 'wpa_supplicant.conf' -> 'C:
\MyDownloadFiles\WPA/wpa_supplicant.conf'
Reading configuration file 'C:\MyDownloadFiles\WPA/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=5):
     4b 49 37 52 57                                    $$$$$$$$$$$$$$$           
scan_ssid=1 (0x1)
key_mgmt: 0x2
proto: 0x1
pairwise: 0x10
group: 0x10
PSK (ASCII passphrase) - hexdump_ascii(len=30): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='$$$$$$$$$$$$$$$'
Initializing interface (2) 
'\Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3, 1, 0, 27
NDIS: 2 adapter names found
NDIS: 2 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericDialupAdapter - Generic dialup adapter
NDIS: 1 - \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9} - NETGEAR WG511 
54 Mbps Wireless PC Card
NDIS: Adapter description prefix 'NETGEAR WG511 54 Mbps Wireless PC Card'
ndis_get_oid: oid=0xd010122 len (512) failed
NDIS: verifying driver WPA capability
NDIS: WPA key management supported
NDIS: WPA-PSK key management supported
NDIS: CCMP encryption supported
NDIS: TKIP encryption supported
NDIS: driver supports WPA
NDIS: driver capabilities: key_mgmt 0x5 enc 0xc auth 0x3
Own MAC address: 00:09:5b:e9:19:ac
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
Setting scan request: 0 sec 100000 usec
Added interface \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
     4b 49 37 52 57                                    $$$$$$$$$$$$$$$           
NDIS: turning radio on before the first scan
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 2
Selecting BSS from priority group 0
0: 00:12:17:e2:8d:05 ssid='$$$$$$$$$$$$$$$' wpa_ie_len=26 rsn_ie_len=0 
caps=0x10
   selected based on WPA IE
Trying to associate with 00:12:17:e2:8d:05 (SSID='$$$$$$$$$$$$$$$' freq=2462 
MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 04 01 
00 00 50 f2 04 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
ndis_set_oid: oid=0xd010119 len (4) failed
NDIS: Failed to set OID_802_11_PRIVACY_FILTER (1)
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
ndis_get_oid: oid=0xd010101 len (6) failed
RX EAPOL from 00:12:17:e2:8d:05
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 00 
58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 90 7f 43 a6 
7f eb 0b 2e 32 7d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00
Setting authentication timeout: 10 sec 0 usec
NDIS: association information - hexdump(len=158): 57 00 00 00 00 00 00 00 00 
00 00 12 17 e2 8d 05 2f 00 00 00 28 00 00 00 07 00 31 04 00 00 03 c0 18 00 00 
00 57 00 00 00 00 05 4b 49 37 52 57 01 04 02 04 0b 16 32 08 0c 12 18 24 30 48 
60 6c dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02 
01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 12 98 60 dd 06 00 10 18 02 02 04 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
NDIS: ReqFixed=0x0 RespFixed=0x7 off_req=40 off_resp=87 len_req=47 len_resp=24
NDIS: Request IEs - hexdump(len=47): 00 05 4b 49 37 52 57 01 04 02 04 0b 16 32 
08 0c 12 18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 
04 01 00 00 50 f2 02
NDIS: Response IEs - hexdump(len=24): 01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 
12 98 60 dd 06 00 10 18 02 02 04
Association info event
req_ies - hexdump(len=47): 00 05 4b 49 37 52 57 01 04 02 04 0b 16 32 08 0c 12 
18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 
00 50 f2 02
resp_ies - hexdump(len=24): 01 08 82 84 8b 96 24 b0 48 6c 32 04 8c 12 98 60 dd 
06 00 10 18 02 02 04
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:12:17:e2:8d:05
No keys have been configured - skip key clearing
Associated with 00:12:17:e2:8d:05
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 
00 00 00 58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 90 
7f 43 a6 7f eb 0b 2e 32 7d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:12:17:e2:8d:05 (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): b3 12 4d c8 43 bb 8b a6 1f 03 5a 7d 09 
38 25 1f 5d d4 cb fc 96 f5 45 3b 13 0d 89 0a 1c db ae 32
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 0a 00 10 00 00 00 00 
00 00 00 00 b3 12 4d c8 43 bb 8b a6 1f 03 5a 7d 09 38 25 1f 5d d4 cb fc 96 f5 
45 3b 13 0d 89 0a 1c db ae 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 68 6f 0c e4 a8 29 c6 c2 22 a4 
29 5c e4 9d d9 7c 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 
01 00 00 50 f2 02
RX EAPOL from 00:12:17:e2:8d:05
RX EAPOL - hexdump(len=125): 01 03 00 79 fe 01 ca 00 10 00 00 00 00 00 00 00 
01 58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 90 7f 43 
a6 7f eb 0b 2e 32 7d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 c8 64 94 0e 18 3c c8 45 bc 2d 10 f6 73 
13 8a 96 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 
50 f2 02 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=121
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=125): 01 03 00 79 fe 01 ca 00 10 00 00 00 00 
00 00 00 01 58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 
90 7f 43 a6 7f eb 0b 2e 32 7d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c8 64 94 0e 18 3c c8 45 bc 2d 
10 f6 73 13 8a 96 00 1a dd 18 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 
01 00 00 50 f2 02 00 00
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
RX EAPOL from 00:12:17:e2:8d:05
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 03 a2 00 10 00 00 00 00 00 00 00 
02 58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 90 7f 43 
a6 7f eb 0b 2e 32 7c 90 17 a2 32 fe 2f 90 7f 43 a6 7f eb 0b 2e 32 7e 72 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 8b 49 d0 64 98 9f 5e 1a 82 59 d9 25 03 
34 c4 9c 00 18 01 3c 1f a6 cf f8 bb ad 7c d7 9e 15 1d 3b 99 72 c9 f2 2f 51 84 
4d c6 80
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 03 a2 00 10 00 00 00 00 
00 00 00 02 58 f3 3f de 75 dc b9 e8 b0 04 3f 8b 78 fe e0 14 90 17 a2 32 fe 2f 
90 7f 43 a6 7f eb 0b 2e 32 7c 90 17 a2 32 fe 2f 90 7f 43 a6 7f eb 0b 2e 32 7e 
72 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8b 49 d0 64 98 9f 5e 1a 82 59 
d9 25 03 34 c4 9c 00 18 01 3c 1f a6 cf f8 bb ad 7c d7 9e 15 1d 3b 99 72 c9 f2 
2f 51 84 4d c6 80
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Authentication with 00:12:17:e2:8d:05 timed out.
Added BSSID 00:12:17:e2:8d:05 into blacklist
State: 4WAY_HANDSHAKE -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
ndis_get_oid: oid=0xd010101 len (6) failed
BSSID 00:12:17:e2:8d:05 blacklist count incremented to 2
State: SCANNING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_set_oid: oid=0xd01011e len (16) failed
ndis_get_oid: oid=0xd010101 len (6) failed
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface \Device\NPF_{A7D8D996-EB21-4B84-8FF6-F416697D6DF9}
State: DISCONNECTED -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_ndis_set_wpa: enabled=0
No keys have been configured - skip key clearing
Removed BSSID 00:12:17:e2:8d:05 from blacklist (clear)
Cancelling scan request



From engage  Sun Nov 20 17:56:13 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 18:56:13 -0700
Subject: wpa_supplicant & winpcap & windows 2000
Message-ID: <200511201856.14134.engage@n0sq.us>

Attached is a 30 second capture using ethereal:



-------------- next part --------------
A non-text attachment was scrubbed...
Name: etheralNetgearWG511
Type: application/octet-stream
Size: 12905 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051120/0cd6ceda/attachment.obj 


From jkmaline  Sun Nov 20 18:30:01 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 18:30:01 -0800
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
Message-ID: <20051121023001.GB9524@jm.kir.nu>

New versions of Host AP driver, wpa_supplicant, and hostapd were just
released and are now available from http://hostap.epitest.fi/

This release moves 0.4.x branch from development to stable status. In
other words, from now on, 0.4.x versions are the latest available
stable releases. 0.3.x branch continues to be supported, but it is
moving more towards only including critical fixes. 0.2.x branch is
about to reach its end of life. I'm planning on releasing one more
0.2.x version with whatever changes have accumulated in the branch and
after that, no more changes are made to 0.2.x branch. In other words,
I would recommend starting to move to either 0.4.x or 0.3.x versions
if you are still using 0.2.x.

I will move 0.4.x development into its own branch (hostap_0_4_branch)
and CVS trunk will become new development branch with eventual 0.5.x
releases. This means that CVS trunk is again open for larger changes.
Please also note that hostap-driver is now developed in Linux 2.6 tree
and I do not plan on making external 0.5.x releases of the driver from
my CVS repository. In other words, 0.5.x releases are mainly expected
for hostapd and wpa_supplicant.


hostapd:
* driver_wired: fixed EAPOL sending to optionally use PAE group address
  as the destination instead of supplicant MAC address; this is
  disabled by default, but should be enabled with use_pae_group_addr=1
  in configuration file if the wired interface is used by only one
  device at the time (common switch configuration)
* driver_madwifi: configure driver to use TKIP countermeasures in order
  to get correct behavior (IEEE 802.11 association failing; previously,
  association succeeded, but hostpad forced disassociation immediately)
* driver_madwifi: added support for madwifi-ng

wpa_supplicant:
* l2_packet_pcap: fixed wired IEEE 802.1X authentication with libpcap
  and WinPcap to receive frames sent to PAE group address
* disable EAP state machine when IEEE 802.1X authentication is not used
  in order to get rid of bogus "EAP failed" messages
* fixed OpenSSL error reporting to go through all pending errors to
  avoid confusing reports of old errors being reported at later point
  during handshake
* fixed configuration file updating to not write empty variables
  (e.g., proto or key_mgmt) that the file parser would not accept
* fixed ADD_NETWORK ctrl_iface command to use the same default values
  for variables as empty network definitions read from config file
  would get
* fixed EAP state machine to not discard EAP-Failure messages in many
  cases (e.g., during TLS handshake)
* fixed a infinite loop in private key reading if the configured file
  cannot be parsed successfully
* driver_madwifi: added support for madwifi-ng
* wpa_gui: do not display password/PSK field contents
* wpa_gui: added CA certificate configuration
* driver_ndis: fixed scan request in ap_scan=2 mode not to change SSID
* driver_ndis: include Beacon IEs in AssocInfo in order to notice if
  the new AP is using different WPA/RSN IE
* use longer timeout for IEEE 802.11 association to avoid problems with
  drivers that may take more than five second to associate


No changes in hostap-driver or hostap-utils, so previous versions were
released as-is to start the stable branch with shared version number
for all components.


-- 
Jouni Malinen                                            PGP id EFC895FA



From engage  Sun Nov 20 19:17:57 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 20:17:57 -0700
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <20051121023001.GB9524@jm.kir.nu>
References: <20051121023001.GB9524@jm.kir.nu>
Message-ID: <200511202017.58004.engage@n0sq.us>

OI just tried using the new windows version (o.4.7) but I'm getting the dialog 
box that states that the dll's can't be found in the path, again. 
wpa_supplicant-windows-bin-0.4.6 didn't do this.



From jkmaline  Sun Nov 20 19:49:04 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 19:49:04 -0800
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <200511202017.58004.engage@n0sq.us>
References: <20051121023001.GB9524@jm.kir.nu>
	<200511202017.58004.engage@n0sq.us>
Message-ID: <20051121034904.GD9524@jm.kir.nu>

On Sun, Nov 20, 2005 at 08:17:57PM -0700, engage wrote:

> OI just tried using the new windows version (o.4.7) but I'm getting the dialog 
> box that states that the dll's can't be found in the path, again. 
> wpa_supplicant-windows-bin-0.4.6 didn't do this.

That's unfortunate.. I changed my build host and it looks like I may
have forgotten to change WinPcap to request full DLL name. Workaround
for this is to copy packet.dll to packet (if I remember correctly). I'll
try to fix my build setup to use the same configuration as 0.4.6 did.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Sun Nov 20 20:01:13 2005
From: bryan (Bryan Kadzban)
Date: Sun, 20 Nov 2005 23:01:13 -0500
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <20051121034904.GD9524@jm.kir.nu>
References: <20051121023001.GB9524@jm.kir.nu>	<200511202017.58004.engage@n0sq.us>
	<20051121034904.GD9524@jm.kir.nu>
Message-ID: <43814689.2060701@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> That's unfortunate.. I changed my build host and it looks like I may 
> have forgotten to change WinPcap to request full DLL name. Workaround
> for this is to copy packet.dll to packet (if I remember correctly).
> I'll try to fix my build setup to use the same configuration as 0.4.6
> did.

Might it be possible to get a v0.4.7.1 with that change in place?

(What I did when compiling 0.4.6 using Debian's mingw, was use the full
path to Packet.lib instead of just saying -lpacket.  When it used the .a
file, it tried to link against packet, but when it used Packet.lib, it
tried to link against packet.dll.  Not sure if that helps, though.)

If you don't want to do a new release, no big deal I suppose.  It'd just
be nice.

Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051120/c2b7c060/attachment.pgp 


From jkmaline  Sun Nov 20 20:08:24 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 20:08:24 -0800
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <43814689.2060701@kadzban.is-a-geek.net>
References: <20051121023001.GB9524@jm.kir.nu>
	<200511202017.58004.engage@n0sq.us>
	<20051121034904.GD9524@jm.kir.nu>
	<43814689.2060701@kadzban.is-a-geek.net>
Message-ID: <20051121040824.GE9524@jm.kir.nu>

On Sun, Nov 20, 2005 at 11:01:13PM -0500, Bryan Kadzban wrote:

> Might it be possible to get a v0.4.7.1 with that change in place?

Sure, once I figure out what happened to my build system, I'll create
0.4.7.1 or the windows-bin package.

> (What I did when compiling 0.4.6 using Debian's mingw, was use the full
> path to Packet.lib instead of just saying -lpacket.  When it used the .a
> file, it tried to link against packet, but when it used Packet.lib, it
> tried to link against packet.dll.  Not sure if that helps, though.)

Interesting.. I worked around the problem by modifying .def file for
libpacket and just use -lpacket to get libpacket.a. However, I seemed to
have changed libpacket.a three weeks ago and the new version was one
that did not include this change. I just don't remember why I changed
it.. ;-)

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov 20 20:24:51 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 20 Nov 2005 20:24:51 -0800
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <20051121040824.GE9524@jm.kir.nu>
References: <20051121023001.GB9524@jm.kir.nu>
	<200511202017.58004.engage@n0sq.us>
	<20051121034904.GD9524@jm.kir.nu>
	<43814689.2060701@kadzban.is-a-geek.net>
	<20051121040824.GE9524@jm.kir.nu>
Message-ID: <20051121042451.GF9524@jm.kir.nu>

On Sun, Nov 20, 2005 at 08:08:24PM -0800, Jouni Malinen wrote:

> Interesting.. I worked around the problem by modifying .def file for
> libpacket and just use -lpacket to get libpacket.a. However, I seemed to
> have changed libpacket.a three weeks ago and the new version was one
> that did not include this change. I just don't remember why I changed
> it.. ;-)

OK. It looks like I moved to WinPcap 3.1 at that point and ended up just
taking the pre-built binaries which do not have my workaround for
packet.dll loading. I built the library with the modification now and
created wpa_supplicant 0.4.7.1. Please let me know whether this resolves
the DLL loading issue on Win2k.

http://hostap.epitest.fi/releases/wpa_supplicant-windows-bin-0.4.7.1.zip

-- 
Jouni Malinen                                            PGP id EFC895FA



From engage  Sun Nov 20 21:21:38 2005
From: engage (engage)
Date: Sun, 20 Nov 2005 22:21:38 -0700
Subject: hostap/hostapd/wpa_supplicant - new stable release v0.4.7
In-Reply-To: <20051121042451.GF9524@jm.kir.nu>
References: <20051121023001.GB9524@jm.kir.nu> <20051121040824.GE9524@jm.kir.nu>
	<20051121042451.GF9524@jm.kir.nu>
Message-ID: <200511202221.38665.engage@n0sq.us>

On Sunday 20 November 2005 09:24 pm, Jouni Malinen wrote:
>On Sun, Nov 20, 2005 at 08:08:24PM -0800, Jouni Malinen wrote:
>> Interesting.. I worked around the problem by modifying .def file for
>> libpacket and just use -lpacket to get libpacket.a. However, I seemed to
>> have changed libpacket.a three weeks ago and the new version was one
>> that did not include this change. I just don't remember why I changed
>> it.. ;-)
>
>OK. It looks like I moved to WinPcap 3.1 at that point and ended up just
>taking the pre-built binaries which do not have my workaround for
>packet.dll loading. I built the library with the modification now and
>created wpa_supplicant 0.4.7.1. Please let me know whether this resolves
>the DLL loading issue on Win2k.
>
>http://hostap.epitest.fi/releases/wpa_supplicant-windows-bin-0.4.7.1.zip

It fixed the dll problem but I'm still having a problem with associating with 
the AP - same problem as I reported earlier.



From jkmaline  Mon Nov 21 19:42:59 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 21 Nov 2005 19:42:59 -0800
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <200511201856.14134.engage@n0sq.us>
References: <200511201856.14134.engage@n0sq.us>
Message-ID: <20051122034259.GB9482@jm.kir.nu>

On Sun, Nov 20, 2005 at 06:56:13PM -0700, engage wrote:

> Attached is a 30 second capture using ethereal:

Thanks! This is getting somewhat confusing.. This capture file shows a
successfully completed WPA authentication and even successful DHCP
handshake after that. There is couple of extra EAPOL-Key frames after
the normal WPA pairwise and group handshakes, but it looks like AP is
just ignoring them and connection works after this..

However, the debug log from wpa_supplicant showed a quite a bit
different behavior. The different sizes for EAPOL-Key frames are likely
caused by them actually being different frames (msg 3/4 and group key
msg 1/2); not retransmission of msg 3/4 like I originally thought. In
other words, supplicant is not sending out msg 4/4 since 3/4 failed
validation. However, AP is assuming that the msg 4/4 was just dropped
and continues to group key handshake.

I don't know what would explain this different behavior, though. Have
you ever noticed network working in this configuration? Would it be
possible to get a debug log from wpa_supplicant and a matching Ethereal
capture log from the same attempt (and maybe just leave it running for
couple of minutes so that there are more than one failure)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 21 19:50:45 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 21 Nov 2005 19:50:45 -0800
Subject: Still can't connect
In-Reply-To: <20051117015614.4220.qmail@web52104.mail.yahoo.com>
References: <20051117015614.4220.qmail@web52104.mail.yahoo.com>
Message-ID: <20051122035045.GC9482@jm.kir.nu>

On Wed, Nov 16, 2005 at 05:56:13PM -0800, Tom wrote:

> Upgraded to ndiswrapper 1.5, but now I see the AP
> on a "blacklist." :(

It looks like ndiswrapper is not reporting association information to
wpa_supplicant. This could end up in a mismatch in WPA IE for message
2/4 which would lead to AP rejecting this packet from the supplicant.

Could you please re-try this with 'iwevent' running at the same time to
make sure that ndiswrapper is indeed not reporting association
information when the association happens? In addition, I would be
interested in seeing whether the behavior changes if this test is run
with wpa_supplicant v0.4.7.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 21 20:10:10 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 21 Nov 2005 20:10:10 -0800
Subject: EAPOLs in Linux Wireless Extensions
In-Reply-To: <C08C15DE99919148ACF278138C3CEC413BE688@dile01.ent.ti.com>
References: <C08C15DE99919148ACF278138C3CEC413BE688@dile01.ent.ti.com>
Message-ID: <20051122041010.GD9482@jm.kir.nu>

On Wed, Nov 16, 2005 at 10:39:16AM +0200, Bar, Eitan wrote:

> Can somebody please describe the chain of events in the kernel/user-mode (as far as WEXT IOCTLs and events) that occur when a station associates and starts the EAPOL handshake?

Start is different based on ap_scan configuration:

ap_scan=1:

- wpa_supplicant requests scan with SIOCSIWSCAN
- driver reports scan complete with wireless event SIOCGIWSCAN
- wpa_supplicant reads scan results with SIOCGIWSCAN (multiple call if
  a larget buffer is needed)
- wpa_supplicant decides which AP to use based on scan results
- wpa_supplicant configures driver to associate with the selected BSS
  (SIOCSIWMODE, SIOCSIWGENIE, SIOCSIWAUTH, SIOCSIWFREQ,
   SIOCSIWESSID, SIOCSIWAP)

ap_scan=2:

- wpa_supplicant configures driver to associate with an SSID
  (SIOCSIWMODE, SIOCSIWGENIE, SIOCSIWAUTH, SIOCSIWESSID)


After this, both modes use similar steps:

- optionally (or required for drivers that generate WPA/RSN IE for
  (Re)AssocReq), driver reports association parameters (AssocReq IEs)
  with wireless event IWEVASSOCREQIE (and optionally IWEVASSOCRESPIE)
- driver reports association with wireless event SIOCGIWAP
- wpa_supplicant takes care of EAPOL frame handling (validating
  information from associnfo and if needed, from scan results if WPA/RSN
  IE from the Beacon frame is not reported through associnfo)

> What I?m specifically interested in is how the kernel driver makes sure that only EAPOL packets are sent/received by the driver and how can the network stack (or whoever) makes sure EAPOLs are prioritized over other types of traffic. (What happens if at the moment the interface notifies ?UP?, the network stack starts sending heavy traffic).

Currently, the wlan driver is expected to take care of this, i.e., it
should filter out non-EAPOL frames if IEEE 802.1X/WPA/WPA2
authentication has been configured, but encryption keys are not yet
configured. set_drop_unencrypted() driver_ops handler can be used to
configure this behavior for the driver.

As far as packet scheduling is concerned, the wlan driver would be
responsible for using higher priority (e.g., VO category with WMM) for
EAPOL frames.

> Will this traffic be just dropped at some higher level of the kernel driver and handle only EAPOLs? (I am aware of a driver wrapper to handle only EAPOLs, but what I?m concerned is other traffic from network stack and what happens to it).

In the current implementation, that traffic would likely be sent to the
driver and the driver would be responsible for dropping non-EAPOL
frames.

> Is there maybe a special support to notify the linux networking stack that it should not forward any packets other than EAPOLs?

I haven't looked at the current IEEE 802.11 stack code in Linux 2.6.14,
but in theory, this kind of functionality could happen in the generic
802.11 code. However, if you need to support something older than Linux
2.6.14 or if you are not using the 802.11 code from kernel tree
(net/ieee80211), the driver better be prepared for handling this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 21 20:49:05 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 21 Nov 2005 20:49:05 -0800
Subject: wpa_supplicant PSK question
In-Reply-To: <20051115161600.59D2899D@dm16.mta.everyone.net>
References: <20051115161600.59D2899D@dm16.mta.everyone.net>
Message-ID: <20051122044905.GE9482@jm.kir.nu>

On Tue, Nov 15, 2005 at 06:12:28PM -0600, Bob Carlson wrote:

> I am porting wpa_supplicant into an embedded application so I am trying to
> minimize the code included. We do not require radius, only WEP and WPA-PSK.

May I ask which OS you are using?

> So far as my understanding has progressed, we should not require EAPOL,
> although there does appear to be a 4-way key exchange that is used.
> However, as I build things up, I am finding that there are a lot of
> references to EAPOL code that do not seem to be conditional.

> What modules and code for EAPOL must still be included, even though we are
> using only PSK?

WPA-PSK is indeed using EAPOL frames, but it does not require IEEE
802.1X/EAPOL or EAP state machines. In other words, you do not need
eapol_sm.c or eap.c/eap_*.c. One of the easiest ways of finding out what
is needed is to build wpa_supplicant for Linux and use a minimal
configuration in .config, e.g.:

CONFIG_DRIVER_TEST=y
CONFIG_NO_STDOUT_DEBUG=y


This links in following files into wpa_supplicant binary:

config.o eloop.o common.o md5.o rc4.o sha1.o config_file.o base64.o
l2_packet_linux.o tls_none.o wpa.o preauth.o aes_wrap.o
wpa_supplicant.o events.o main.o drivers.o driver_test.o

This is enough to run WPA-PSK, but not WPA-EAP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From maccari-thisaintpartofmyaddress-  Tue Nov 22 03:47:41 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Tue, 22 Nov 2005 12:47:41 +0100
Subject: Handoff with wpa_supplicant and madwifi driver
In-Reply-To: <000001c5ed4e$478e3060$4c01a8c0@stephansmobile>
References: <000001c5ed4e$478e3060$4c01a8c0@stephansmobile>
Message-ID: <20051122114741.GB19458@lenst.det.unifi.it>

On Sat, Nov 19, 2005 at 01:14:45PM -0800, Stephan Schlumbohm wrote:
> Hi all,
> 
> I'm having serious trouble with the handoff from one access point to another using wpa_supplicant (stable 0.3.8 and development 0.4.6) with the madwifi driver (madwifi-ng latest svn snapshot from madwifi.org).
> 
> Both access points have the same ESSID and operate on the same channel and have the same security settings. In fact, those access points are mesh access points - both are connected to a FreeRADIUS server.
> 
> Authentication (Open, WPA-PSK, WPA-802.1X-TLS/PEAP/TTLS) works fine in this setup to each access point.
> 
> But, when I try to roam from one access point to another, wpa_supplicant does not initiate a reassociation request to the new access point. Instead, it disassociates the old access point, then it performs the scanning and then finally goes through a full new authentication with the new access point.

My experience says that scan time is not the real bottlenck, delay is
introduced by loss of conectivity _before_ triggering a new scan, then from
RADIUS authentication (multi-hop packets, worse in a mesh environment),
and finally some delays that I couldn't really explain after
authentication and before first EAPOL packet. Jouni said a few time ago
that a bug was cleaned that caused hostapd waste some time after
authentication.
Anyway if you use WPA/WPA2 you must renegotiate the PMK key (whatever
authentication method you use) and renegotiate the PTK/GTK.

> 
> This causes the handoff to take about 1.5 to 3 seconds. This is not acceptable and is not intended by the developers. A single channel handoff should take about 10 to 300 ms (depending on authentication).
> 

there is an old thread about handoff times that you might read in the
archives. 

a couple questions: how do you trigger handoff procedure from one AP to
another? and what does mesh access points means? how do they authenticate
each other ?

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 




From bryan  Tue Nov 22 04:00:34 2005
From: bryan (Bryan Kadzban)
Date: Tue, 22 Nov 2005 07:00:34 -0500
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <20051122034259.GB9482@jm.kir.nu>
References: <200511201856.14134.engage@n0sq.us>
	<20051122034259.GB9482@jm.kir.nu>
Message-ID: <43830862.3070500@kadzban.is-a-geek.net>

Jouni Malinen wrote:
> Thanks! This is getting somewhat confusing.. This capture file shows
> a successfully completed WPA authentication and even successful DHCP 
> handshake after that. There is couple of extra EAPOL-Key frames after
> the normal WPA pairwise and group handshakes, but it looks like AP is
> just ignoring them and connection works after this..

engage:  Is the Windows 2000 "Wireless Configuration" service disabled,
or is it running?  (Even when we set it to manual, it still starts on
boot.  When using the wpa_supplicant windows port on 2000, we have to
disable it.)

We've seen some *very* odd behavior when this service is running -- it's
like it tries to restart EAP after the supplicant finishes, but it has
no configuration, so it always fails.  Which makes authentication
usually fail, too, although sometimes wpa_supplicant does another round
of EAP traffic and gets the connection to come up.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051122/1e072c5e/attachment.pgp 


From rjc  Tue Nov 22 07:23:07 2005
From: rjc (Bob Carlson)
Date: Tue, 22 Nov 2005 09:23:07 -0600
Subject: wpa_supplicant PSK question
In-Reply-To: <20051122044905.GE9482@jm.kir.nu>
Message-ID: <20051122072656.9A8AE0A3@dm18.mta.everyone.net>

I am working with VxWorks and Tornado. Since I have to build the supplicant
in Tornado in concert with the rest of the application, it's hard to use
the existing build defines. When I tried to build without eapol_sm.c and
eap.c, I couldn't get rid of unresolved externals. I considered the idea of
including the .config file as an include in all the .c files so I could use
the same build defines without having to do contortions in Tornado.

That list of .o files should be invaluable. Thanks for that.

Cheers, Bob

> -----Original Message-----
> From: hostap-bounces+bob.carlson=sigpro.com at shmoo.com [mailto:hostap-
> bounces+bob.carlson=sigpro.com at shmoo.com] On Behalf Of Jouni Malinen
> Sent: Monday, November 21, 2005 10:49 PM
> To: hostap at shmoo.com
> Subject: Re: wpa_supplicant PSK question
> 
> On Tue, Nov 15, 2005 at 06:12:28PM -0600, Bob Carlson wrote:
> 
> > I am porting wpa_supplicant into an embedded application so I am trying
> to
> > minimize the code included. We do not require radius, only WEP and WPA-
> PSK.
> 
> May I ask which OS you are using?
> 
> > So far as my understanding has progressed, we should not require EAPOL,
> > although there does appear to be a 4-way key exchange that is used.
> > However, as I build things up, I am finding that there are a lot of
> > references to EAPOL code that do not seem to be conditional.
> 
> > What modules and code for EAPOL must still be included, even though we
> are
> > using only PSK?
> 
> WPA-PSK is indeed using EAPOL frames, but it does not require IEEE
> 802.1X/EAPOL or EAP state machines. In other words, you do not need
> eapol_sm.c or eap.c/eap_*.c. One of the easiest ways of finding out what
> is needed is to build wpa_supplicant for Linux and use a minimal
> configuration in .config, e.g.:
> 
> CONFIG_DRIVER_TEST=y
> CONFIG_NO_STDOUT_DEBUG=y
> 
> 
> This links in following files into wpa_supplicant binary:
> 
> config.o eloop.o common.o md5.o rc4.o sha1.o config_file.o base64.o
> l2_packet_linux.o tls_none.o wpa.o preauth.o aes_wrap.o
> wpa_supplicant.o events.o main.o drivers.o driver_test.o
> 
> This is enough to run WPA-PSK, but not WPA-EAP.
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From oltmanns  Tue Nov 22 08:24:31 2005
From: oltmanns (Elias Oltmanns)
Date: Tue, 22 Nov 2005 17:24:31 +0100
Subject: wpasupplicant/madwifi and bridging
Message-ID: <87ek58wszk.fsf@denkblock.local>

Hi there,

using wpasupplicant and madwifi (still old generation, recent cvs
version though), I couldn't bring bridging to work in this setup. Is
there a way to have wpasupplicant authenticate to an ap through an
interface which is part of a bridge?

Thanks in advance,

Elias



From rjc  Tue Nov 22 09:07:17 2005
From: rjc (Bob Carlson)
Date: Tue, 22 Nov 2005 11:07:17 -0600
Subject: wpa_supplicant PSK question
In-Reply-To: <20051122044905.GE9482@jm.kir.nu>
Message-ID: <20051122091107.9A8AF2B3@dm18.mta.everyone.net>

I'm still confused. Using WPA(2)-PSK, the system still needs to carry out
the 4-way handshake. It looks to me like eap_psk.c does that. And that
seems to depend on eap.c and eapol_sm.c. I've probably just missed
something, but I could use a little more help.

Thanks, Bob

> -----Original Message-----
> From: hostap-bounces+bob.carlson=sigpro.com at shmoo.com [mailto:hostap-
> bounces+bob.carlson=sigpro.com at shmoo.com] On Behalf Of Jouni Malinen
> Sent: Monday, November 21, 2005 10:49 PM
> To: hostap at shmoo.com
> Subject: Re: wpa_supplicant PSK question
> 
> WPA-PSK is indeed using EAPOL frames, but it does not require IEEE
> 802.1X/EAPOL or EAP state machines. In other words, you do not need
> eapol_sm.c or eap.c/eap_*.c. One of the easiest ways of finding out what
> is needed is to build wpa_supplicant for Linux and use a minimal
> configuration in .config, e.g.:
> 
> CONFIG_DRIVER_TEST=y
> CONFIG_NO_STDOUT_DEBUG=y
> 
> 
> This links in following files into wpa_supplicant binary:
> 
> config.o eloop.o common.o md5.o rc4.o sha1.o config_file.o base64.o
> l2_packet_linux.o tls_none.o wpa.o preauth.o aes_wrap.o
> wpa_supplicant.o events.o main.o drivers.o driver_test.o
> 
> This is enough to run WPA-PSK, but not WPA-EAP.
> 
> --




From bryan  Tue Nov 22 09:35:01 2005
From: bryan (Bryan Kadzban)
Date: Tue, 22 Nov 2005 12:35:01 -0500
Subject: wpa_supplicant PSK question
In-Reply-To: <20051122091107.9A8AF2B3@dm18.mta.everyone.net>
References: <20051122044905.GE9482@jm.kir.nu>
	<20051122091107.9A8AF2B3@dm18.mta.everyone.net>
Message-ID: <20051122173501.GA7124@kadzban.is-a-geek.net>

On Tue, Nov 22, 2005 at 11:07:17AM -0600, Bob Carlson wrote:
> I'm still confused. Using WPA(2)-PSK, the system still needs to carry out
> the 4-way handshake. It looks to me like eap_psk.c does that. And that
> seems to depend on eap.c and eapol_sm.c. I've probably just missed
> something, but I could use a little more help.

Nope, that's for EAP-PSK, not WPA(2)-PSK.  ;-)

I'd never heard of that security method before wpa_supplicant, but it
looks like basically EAP without the username.  (The only piece of
information used to authenticate users is the PSK.)  It's not the same
as WPA(2)-PSK, though, because I believe you can havee different PMKs
(with WPA(2)-PSK, the PMK is the PSK; when EAP is involved, the PMK can
be sent from the RADIUS server, depending on the EAP method).

The 4-way handshake used in all WPA and WPA2 methods is done in wpa.c.
(See, for instance, the wpa_supplicant_process_{1,3}_of_4 functions.)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051122/08d8581a/attachment.pgp 


From rjc  Tue Nov 22 14:16:15 2005
From: rjc (Bob Carlson)
Date: Tue, 22 Nov 2005 16:16:15 -0600
Subject: wpa_supplicant PSK question - update
In-Reply-To: <20051122091107.9A8AF2B3@dm18.mta.everyone.net>
Message-ID: <20051122142008.9A8AF440@dm16.mta.everyone.net>

I now see where wpa.c seems to have code for the 4-way handshake. I can
also see from your list of files that you are referring to the new 0.4.7. I
am working with 0.3.9, which was the stable one when I started.

Is there any reason why I should be moving to 0.4.7? I have a lot of work
invested in the current code, though it's still conceivable to switch.

Cheers, Bob

> -----Original Message-----
> From: hostap-bounces+bob.carlson=sigpro.com at shmoo.com [mailto:hostap-
> bounces+bob.carlson=sigpro.com at shmoo.com] On Behalf Of Bob Carlson
> Sent: Tuesday, November 22, 2005 11:07 AM
> To: 'Jouni Malinen'; hostap at shmoo.com
> Subject: RE: wpa_supplicant PSK question
> 
> I'm still confused. Using WPA(2)-PSK, the system still needs to carry out
> the 4-way handshake. It looks to me like eap_psk.c does that. And that
> seems to depend on eap.c and eapol_sm.c. I've probably just missed
> something, but I could use a little more help.
> 
> Thanks, Bob
> 
> > -----Original Message-----
> > From: hostap-bounces+bob.carlson=sigpro.com at shmoo.com [mailto:hostap-
> > bounces+bob.carlson=sigpro.com at shmoo.com] On Behalf Of Jouni Malinen
> > Sent: Monday, November 21, 2005 10:49 PM
> > To: hostap at shmoo.com
> > Subject: Re: wpa_supplicant PSK question
> >
> > WPA-PSK is indeed using EAPOL frames, but it does not require IEEE
> > 802.1X/EAPOL or EAP state machines. In other words, you do not need
> > eapol_sm.c or eap.c/eap_*.c. One of the easiest ways of finding out
> what
> > is needed is to build wpa_supplicant for Linux and use a minimal
> > configuration in .config, e.g.:
> >
> > CONFIG_DRIVER_TEST=y
> > CONFIG_NO_STDOUT_DEBUG=y
> >
> >
> > This links in following files into wpa_supplicant binary:
> >
> > config.o eloop.o common.o md5.o rc4.o sha1.o config_file.o base64.o
> > l2_packet_linux.o tls_none.o wpa.o preauth.o aes_wrap.o
> > wpa_supplicant.o events.o main.o drivers.o driver_test.o
> >
> > This is enough to run WPA-PSK, but not WPA-EAP.
> >
> > --
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From engage  Tue Nov 22 15:41:53 2005
From: engage (engage)
Date: Tue, 22 Nov 2005 16:41:53 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <43830862.3070500@kadzban.is-a-geek.net>
References: <200511201856.14134.engage@n0sq.us>
	<20051122034259.GB9482@jm.kir.nu>
	<43830862.3070500@kadzban.is-a-geek.net>
Message-ID: <200511221641.54540.engage@n0sq.us>

On Tuesday 22 November 2005 05:00 am, Bryan Kadzban wrote:
>Jouni Malinen wrote:
>> Thanks! This is getting somewhat confusing.. This capture file shows
>> a successfully completed WPA authentication and even successful DHCP
>> handshake after that. There is couple of extra EAPOL-Key frames after
>> the normal WPA pairwise and group handshakes, but it looks like AP is
>> just ignoring them and connection works after this..
>
>engage:  Is the Windows 2000 "Wireless Configuration" service disabled,
>or is it running?  (Even when we set it to manual, it still starts on
>boot.  When using the wpa_supplicant windows port on 2000, we have to
>disable it.)

It was set for manual start. I disabled the service but I'm getting the same 
results (even after a reboot).

>
>We've seen some *very* odd behavior when this service is running -- it's
>like it tries to restart EAP after the supplicant finishes, but it has
>no configuration, so it always fails.  Which makes authentication
>usually fail, too, although sometimes wpa_supplicant does another round
>of EAP traffic and gets the connection to come up.



From jkmaline  Tue Nov 22 19:08:14 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 22 Nov 2005 19:08:14 -0800
Subject: wpa_supplicant PSK question
In-Reply-To: <20051122091107.9A8AF2B3@dm18.mta.everyone.net>
References: <20051122044905.GE9482@jm.kir.nu>
	<20051122091107.9A8AF2B3@dm18.mta.everyone.net>
Message-ID: <20051123030814.GA9497@jm.kir.nu>

On Tue, Nov 22, 2005 at 11:07:17AM -0600, Bob Carlson wrote:
> I'm still confused. Using WPA(2)-PSK, the system still needs to carry out
> the 4-way handshake. It looks to me like eap_psk.c does that. And that
> seems to depend on eap.c and eapol_sm.c. I've probably just missed
> something, but I could use a little more help.

eap_psk.c is an implementation of EAP-PSK which has nothing to do with
WPA-PSK. In other words, it is not needed here and neither are the files
it would have added to the dependency list.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Nov 22 19:17:17 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 22 Nov 2005 19:17:17 -0800
Subject: wpa_supplicant PSK question - update
In-Reply-To: <20051122142008.9A8AF440@dm16.mta.everyone.net>
References: <20051122091107.9A8AF2B3@dm18.mta.everyone.net>
	<20051122142008.9A8AF440@dm16.mta.everyone.net>
Message-ID: <20051123031717.GB9497@jm.kir.nu>

On Tue, Nov 22, 2005 at 04:16:15PM -0600, Bob Carlson wrote:
> I now see where wpa.c seems to have code for the 4-way handshake. I can
> also see from your list of files that you are referring to the new 0.4.7. I
> am working with 0.3.9, which was the stable one when I started.
> 
> Is there any reason why I should be moving to 0.4.7? I have a lot of work
> invested in the current code, though it's still conceivable to switch.

In general, I would recommend using the latest stable version when
starting a new project. 0.4.x has number of new features and cleanup in
the design that I consider very useful, but of course, you need to take
a look at whether they would be more useful for you than the potential
extra work added in moving from 0.3.x to 0.4.x.

If you want to have access to up-to-date documentation for the
implementation, you should also take into account that 0.3.x is not
documented as thoroughly as 0.4.x is. As far as future support is
concerned, I would guess that 0.4.x will be supported for quite a bit
longer than 0.3.x which may also be a useful thing to keep in mind.

If you will be able to contribute some changes to the open source
version, I would highly recommend doing this based on 0.4.x or even
better from my view point, on current development branch (0.5.x), but
that may not be that good of a choice at this point for a stable
product since it is likely going to get much more changes than 0.4.x.

-- 
Jouni Malinen                                            PGP id EFC895FA



From rjc  Tue Nov 22 19:38:12 2005
From: rjc (Bob Carlson)
Date: Tue, 22 Nov 2005 21:38:12 -0600
Subject: wpa_supplicant PSK question - update
In-Reply-To: <20051123031717.GB9497@jm.kir.nu>
Message-ID: <20051122194206.BAD89389@dm18.mta.everyone.net>

I've got a lot of time pressure, so I will stick with the current code
base. I am also figuring out as I go the best way to adapt to VXWorks. I
thought it might be fun to come back to wpa_supplicant after I'm done with
the port and contribute some well-considered changes to a more current
version.

Cheers, Bob

> -----Original Message-----
> From: hostap-bounces+bob.carlson=sigpro.com at shmoo.com [mailto:hostap-
> bounces+bob.carlson=sigpro.com at shmoo.com] On Behalf Of Jouni Malinen
> Sent: Tuesday, November 22, 2005 9:17 PM
> To: hostap at shmoo.com
> Subject: Re: wpa_supplicant PSK question - update
> 
> On Tue, Nov 22, 2005 at 04:16:15PM -0600, Bob Carlson wrote:
> > I now see where wpa.c seems to have code for the 4-way handshake. I can
> > also see from your list of files that you are referring to the new
> 0.4.7. I
> > am working with 0.3.9, which was the stable one when I started.
> >
> > Is there any reason why I should be moving to 0.4.7? I have a lot of
> work
> > invested in the current code, though it's still conceivable to switch.
> 
> In general, I would recommend using the latest stable version when
> starting a new project. 0.4.x has number of new features and cleanup in
> the design that I consider very useful, but of course, you need to take
> a look at whether they would be more useful for you than the potential
> extra work added in moving from 0.3.x to 0.4.x.
> 
> If you want to have access to up-to-date documentation for the
> implementation, you should also take into account that 0.3.x is not
> documented as thoroughly as 0.4.x is. As far as future support is
> concerned, I would guess that 0.4.x will be supported for quite a bit
> longer than 0.3.x which may also be a useful thing to keep in mind.
> 
> If you will be able to contribute some changes to the open source
> version, I would highly recommend doing this based on 0.4.x or even
> better from my view point, on current development branch (0.5.x), but
> that may not be that good of a choice at this point for a stable
> product since it is likely going to get much more changes than 0.4.x.
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From duncan.grove  Tue Nov 22 19:49:55 2005
From: duncan.grove (Duncan Grove)
Date: Wed, 23 Nov 2005 14:19:55 +1030
Subject: HostAP Digest, Vol 31, Issue 32 
In-Reply-To: <20051123033711.AEBDE56421D@mail.iocaine.com>
References: <20051123033711.AEBDE56421D@mail.iocaine.com>
Message-ID: <4383E6E3.3030907@dsto.defence.gov.au>

I'll be there.

We forfeited last week :-( . Greg, Geoff and myself were there but 
Kriegy got the wrong time and Chop, what happened to you? I gather we'll 
need to stump up $ for the forfeit but I'm not sure how much it is. 
Geoff? I guess we'll just share it around...?

Cheers,
Duncan

hostap-request at shmoo.com wrote:

>Send HostAP mailing list submissions to
>	hostap at shmoo.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.shmoo.com/mailman/listinfo/hostap
>or, via email, send a message with subject or body 'help' to
>	hostap-request at shmoo.com
>
>You can reach the person managing the list at
>	hostap-owner at shmoo.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of HostAP digest..."
>
>
>Today's Topics:
>
>   1. Re: Handoff with wpa_supplicant and madwifi driver
>      (Leonardo Maccari)
>   2. Re: wpa_supplicant & winpcap & windows 2000 (Bryan Kadzban)
>   3. RE: wpa_supplicant PSK question (Bob Carlson)
>   4. wpasupplicant/madwifi and bridging (Elias Oltmanns)
>   5. RE: wpa_supplicant PSK question (Bob Carlson)
>   6. Re: wpa_supplicant PSK question (Bryan Kadzban)
>   7. RE: wpa_supplicant PSK question - update (Bob Carlson)
>   8. Re: wpa_supplicant & winpcap & windows 2000 (engage)
>   9. Re: wpa_supplicant PSK question (Jouni Malinen)
>  10. Re: wpa_supplicant PSK question - update (Jouni Malinen)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 22 Nov 2005 12:47:41 +0100
>From: Leonardo Maccari
>	<maccari-thisaintpartofmyaddress- at lenst.det.unifi.it>
>Subject: Re: Handoff with wpa_supplicant and madwifi driver
>To: hostap at shmoo.com
>Message-ID: <20051122114741.GB19458 at lenst.det.unifi.it>
>Content-Type: text/plain; charset=us-ascii
>
>On Sat, Nov 19, 2005 at 01:14:45PM -0800, Stephan Schlumbohm wrote:
>  
>
>>Hi all,
>>
>>I'm having serious trouble with the handoff from one access point to
>>    
>>
>another using wpa_supplicant (stable 0.3.8 and development 0.4.6) with
>the madwifi driver (madwifi-ng latest svn snapshot from madwifi.org).
>  
>
>>Both access points have the same ESSID and operate on the same channel
>>    
>>
>and have the same security settings. In fact, those access points are
>mesh access points - both are connected to a FreeRADIUS server.
>  
>
>>Authentication (Open, WPA-PSK, WPA-802.1X-TLS/PEAP/TTLS) works fine in
>>    
>>
>this setup to each access point.
>  
>
>>But, when I try to roam from one access point to another,
>>    
>>
>wpa_supplicant does not initiate a reassociation request to the new
>access point. Instead, it disassociates the old access point, then it
>performs the scanning and then finally goes through a full new
>authentication with the new access point.
>
>My experience says that scan time is not the real bottlenck, delay is
>introduced by loss of conectivity _before_ triggering a new scan, then
>from
>RADIUS authentication (multi-hop packets, worse in a mesh environment),
>and finally some delays that I couldn't really explain after
>authentication and before first EAPOL packet. Jouni said a few time ago
>that a bug was cleaned that caused hostapd waste some time after
>authentication.
>Anyway if you use WPA/WPA2 you must renegotiate the PMK key (whatever
>authentication method you use) and renegotiate the PTK/GTK.
>
>  
>
>>This causes the handoff to take about 1.5 to 3 seconds. This is not
>>    
>>
>acceptable and is not intended by the developers. A single channel
>handoff should take about 10 to 300 ms (depending on authentication).
>  
>
>
>there is an old thread about handoff times that you might read in the
>archives. 
>
>a couple questions: how do you trigger handoff procedure from one AP to
>another? and what does mesh access points means? how do they
>authenticate
>each other ?
>
>ciao,
>leonardo.
>
>  
>



From wfragg  Tue Nov 22 21:20:35 2005
From: wfragg (Ivan Dubrov)
Date: Wed, 23 Nov 2005 11:20:35 +0600
Subject: EAPOL-Key timeout again
Message-ID: <5657db0f0511222120g3af8fe5bmd0e60611b7558215@mail.gmail.com>

I have set up latest madwifi-ng drivers (1330 revision from the
Subversion) and hostapd 0.4.7 with WPA-PSK security.

I've got the following results:

WinXP+SP2 works well with this configuration, several Pocket PC's work
well too (namely, HP iPAQ'



From wfragg  Tue Nov 22 21:26:30 2005
From: wfragg (Ivan Dubrov)
Date: Wed, 23 Nov 2005 11:26:30 +0600
Subject: EAPOL-Key timeout again
Message-ID: <5657db0f0511222126p3f5e2895occ30f6d9aabc26f5@mail.gmail.com>

Hello,

Sorry for previous message, I've unintentionally pressed "send" button.

I have set up latest madwifi-ng drivers (1330 revision from the
Subversion) and hostapd 0.4.7 with WPA-PSK security.

I've got the following results:

WinXP+SP2 works well with this configuration, several Pocket PC's work
well (namely, HP iPAQ rx3715, some of Dell Axim), the Palm (some of
Palm One) works well too.

But two devices do not work. They are Nokia 9500 and Sony PSP.
However, if I disable hostapd, they can connect.

I've attached the log file and a configuration. Is there any way to
debug this from the access point (I'm afraid there is no way to have
nice logs on these devices)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log
Type: application/octet-stream
Size: 8084 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051123/51d85be5/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hostapd.conf
Type: application/octet-stream
Size: 13505 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051123/51d85be5/attachment-0001.obj 


From maccari-thisaintpartofmyaddress-  Thu Nov 24 03:28:58 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Thu, 24 Nov 2005 12:28:58 +0100
Subject: [PATCH] adding wpa_common.h
In-Reply-To: <20051120033755.GB9047@jm.kir.nu>
References: <20051117105010.GA28712@lenst.det.unifi.it>
	<20051120033755.GB9047@jm.kir.nu>
Message-ID: <20051124112858.GA31542@lenst.det.unifi.it>

On Sat, Nov 19, 2005 at 07:37:55PM -0800, Jouni Malinen wrote:
> On Thu, Nov 17, 2005 at 11:50:10AM +0100, Leonardo Maccari wrote:
> 
> Please re-diff your changes with -N option for diff so that the new file
> (wpa_common.h) is included.

here it is.

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 

-------------- next part --------------
Common subdirectories: wpa_supplicant-0.4.6/doc and wpa_supplicant-0.4.6-dev/doc
Common subdirectories: wpa_supplicant-0.4.6/examples and wpa_supplicant-0.4.6-dev/examples
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N wpa_supplicant-0.4.6/wpa_common.h wpa_supplicant-0.4.6-dev/wpa_common.h
--- wpa_supplicant-0.4.6/wpa_common.h	1970-01-01 01:00:00.000000000 +0100
+++ wpa_supplicant-0.4.6-dev/wpa_common.h	2005-11-17 11:16:04.000000000 +0100
@@ -0,0 +1,28 @@
+
+/* Common structs/defines between supplicant and authenticator*/
+#define WPA_REPLAY_COUNTER_LEN 8
+#define WPA_NONCE_LEN 32
+#define WPA_KEY_RSC_LEN 8
+
+#define EAPOL_VERSION 2
+
+
+struct ieee802_1x_hdr {
+	u8 version;
+	u8 type;
+	u16 length;
+	/* followed by length octets of data */
+} __attribute__ ((packed));
+
+
+enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
+       IEEE802_1X_TYPE_EAPOL_START = 1,
+       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
+       IEEE802_1X_TYPE_EAPOL_KEY = 3,
+       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
+};
+
+enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
+       EAPOL_KEY_TYPE_WPA = 254 };
+
+
Common subdirectories: wpa_supplicant-0.4.6/wpa_gui and wpa_supplicant-0.4.6-dev/wpa_gui
Common subdirectories: wpa_supplicant-0.4.6/wpa_gui-qt4 and wpa_supplicant-0.4.6-dev/wpa_gui-qt4
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N wpa_supplicant-0.4.6/wpa.h wpa_supplicant-0.4.6-dev/wpa.h
--- wpa_supplicant-0.4.6/wpa.h	2005-10-02 01:34:36.000000000 +0200
+++ wpa_supplicant-0.4.6-dev/wpa.h	2005-11-17 11:28:05.000000000 +0100
@@ -16,29 +16,10 @@
 #define WPA_H
 
 #include "defs.h"
+#include "wpa_common.h"
 
 #define BIT(n) (1 << (n))
 
-struct ieee802_1x_hdr {
-	u8 version;
-	u8 type;
-	u16 length;
-	/* followed by length octets of data */
-} __attribute__ ((packed));
-
-#define EAPOL_VERSION 2
-
-enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
-       IEEE802_1X_TYPE_EAPOL_START = 1,
-       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
-       IEEE802_1X_TYPE_EAPOL_KEY = 3,
-       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
-};
-
-enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
-       EAPOL_KEY_TYPE_WPA = 254 };
-
-
 #define WPA_CAPABILITY_PREAUTH BIT(0)
 
 #define GENERIC_INFO_ELEM 0xdd
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N wpa_supplicant-0.4.6/wpa_i.h wpa_supplicant-0.4.6-dev/wpa_i.h
--- wpa_supplicant-0.4.6/wpa_i.h	2005-09-12 22:16:15.000000000 +0200
+++ wpa_supplicant-0.4.6-dev/wpa_i.h	2005-11-17 11:27:09.000000000 +0100
@@ -15,10 +15,6 @@
 #ifndef WPA_I_H
 #define WPA_I_H
 
-#define WPA_NONCE_LEN 32
-#define WPA_REPLAY_COUNTER_LEN 8
-
-
 struct rsn_pmksa_candidate;
 
 /**
-------------- next part --------------
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N hostapd-0.4.6/ieee802_1x.h hostapd-0.4.6-dev/ieee802_1x.h
--- hostapd-0.4.6/ieee802_1x.h	2005-08-29 06:05:12.000000000 +0200
+++ hostapd-0.4.6-dev/ieee802_1x.h	2005-11-17 11:18:14.000000000 +0100
@@ -1,23 +1,6 @@
 #ifndef IEEE802_1X_H
 #define IEEE802_1X_H
 
-/* IEEE Std 802.1X-REV-d11, 7.2 */
-
-struct ieee802_1x_hdr {
-	u8 version;
-	u8 type;
-	u16 length;
-	/* followed by length octets of data */
-} __attribute__ ((packed));
-
-#define EAPOL_VERSION 2
-
-enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
-       IEEE802_1X_TYPE_EAPOL_START = 1,
-       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
-       IEEE802_1X_TYPE_EAPOL_KEY = 3,
-       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
-};
 
 /* draft-congdon-radius-8021x-20.txt */
 
@@ -43,9 +26,6 @@
 	 * RC4 key used in encryption = Key-IV + MS-MPPE-Recv-Key */
 } __attribute__ ((packed));
 
-enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
-       EAPOL_KEY_TYPE_WPA = 254 };
-
 
 void ieee802_1x_receive(struct hostapd_data *hapd, const u8 *sa, const u8 *buf,
 			size_t len);
Common subdirectories: hostapd-0.4.6/logwatch and hostapd-0.4.6-dev/logwatch
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N hostapd-0.4.6/wpa_common.h hostapd-0.4.6-dev/wpa_common.h
--- hostapd-0.4.6/wpa_common.h	1970-01-01 01:00:00.000000000 +0100
+++ hostapd-0.4.6-dev/wpa_common.h	2005-11-17 11:15:57.000000000 +0100
@@ -0,0 +1,28 @@
+
+/* Common structs/defines between supplicant and authenticator*/
+#define WPA_REPLAY_COUNTER_LEN 8
+#define WPA_NONCE_LEN 32
+#define WPA_KEY_RSC_LEN 8
+
+#define EAPOL_VERSION 2
+
+
+struct ieee802_1x_hdr {
+	u8 version;
+	u8 type;
+	u16 length;
+	/* followed by length octets of data */
+} __attribute__ ((packed));
+
+
+enum { IEEE802_1X_TYPE_EAP_PACKET = 0,
+       IEEE802_1X_TYPE_EAPOL_START = 1,
+       IEEE802_1X_TYPE_EAPOL_LOGOFF = 2,
+       IEEE802_1X_TYPE_EAPOL_KEY = 3,
+       IEEE802_1X_TYPE_EAPOL_ENCAPSULATED_ASF_ALERT = 4
+};
+
+enum { EAPOL_KEY_TYPE_RC4 = 1, EAPOL_KEY_TYPE_RSN = 2,
+       EAPOL_KEY_TYPE_WPA = 254 };
+
+
diff --exclude .config --exclude defconfig --exclude '*.swp' --exclude cscope.out --exclude tags -u -N hostapd-0.4.6/wpa.h hostapd-0.4.6-dev/wpa.h
--- hostapd-0.4.6/wpa.h	2005-06-26 20:27:44.000000000 +0200
+++ hostapd-0.4.6-dev/wpa.h	2005-11-17 11:32:37.000000000 +0100
@@ -1,14 +1,14 @@
 #ifndef WPA_H
 #define WPA_H
 
-#define WPA_NONCE_LEN 32
+#include "wpa_common.h"
+
 #define WPA_PMK_LEN PMK_LEN
-#define WPA_REPLAY_COUNTER_LEN 8
 #define WPA_GMK_LEN 32
 #define WPA_GTK_MAX_LEN 32
-#define WPA_KEY_RSC_LEN 8
 #define PMKID_LEN 16
 
+
 struct rsn_pmksa_cache {
 	struct rsn_pmksa_cache *next, *hnext;
 	u8 pmkid[PMKID_LEN];


From msmith  Thu Nov 24 13:36:56 2005
From: msmith (Michael Smith)
Date: Thu, 24 Nov 2005 16:36:56 -0500 (EST)
Subject: wpa_supplicant deassociated, doesn't reassociate
Message-ID: <Pine.LNX.4.61.0511241629070.5541@juice.ott.cti.com>

Hi,

I'm on Linux 2.6.11.11, trying to switch to wpa_supplicant/hostapd 0.4.7 + 
madwifi-ng (was wpa/hostapd 0.4.3 and a madwifi-bsd checkout from June).

I have a ~3km noisy test link and I'm having a problem that I can't 
reliably reproduce yet. If the madwifi-ng master deassociates the station 
(e.g. due to AP config change), sometimes the client isn't able to 
reassociate on the first try, probably because of a lost packet:

Nov 24 21:24:27 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: associated
Nov 24 21:24:30 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: deauthenticated due to local deauth request
Nov 24 21:24:30 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: deassociated

Normally the client immediately tries to reassociate, but a few times I've 
seen it never come back. Logging into the client over another link, I can 
check wpa_supplicant and it thinks it is in state COMPLETED, with bssid 
00:00:00:00:00:00. I told it "reassoc", but it didn't seem to do anything 
(no association reported on the master). A reboot of the client fixes it, 
a reboot of the master does not.

I know it's pretty vague at this point, but any suggestions on where to 
look in wpa_supplicant would be helpful.

Thanks,
Mike



From stephan.schlumbohm  Thu Nov 24 19:38:04 2005
From: stephan.schlumbohm (Stephan Schlumbohm)
Date: Thu, 24 Nov 2005 19:38:04 -0800
Subject: Handoff with wpa_supplicant and madwifi driver
In-Reply-To: <20051122114741.GB19458@lenst.det.unifi.it>
Message-ID: <000701c5f171$a7ab0a50$1502a8c0@stephansmobile>

I did some testing with the same wireless card under Windows with a Cisco
driver (and supplicant) and got a handoff time of less than 300 ms on
average. In this setup the station is sending re-association request frames
to the new access point.

I tested then the same card together with the Cisco driver under Linux using
Linuxand DriverLoader and wpa_supplicant-0.4.7. I achieved for the same
setup a handoff time of 1 to 1.5 seconds on average. This time
wpa_supplicant is using re-association request frames as well (as compared
to the madwifi-ng driver). It seems wpa_supplicant is not performing a very
quick handoff. As I understand, the handoff is triggered by the driver,
wpa_supplicant gets a wireless event and some re-association information and
then walks through the re-association. It seems to me that the handoff is
not very well implemented in the madwifi driver and / or the madwifi driver
is not communicating the information in the right way to wpa_supplicant.

Another thing I noticed with both supplicants is that if you keep sending
ICMP Echo Request every 20 ms during the handoff you can screw up the EAPOL
message exchange very badly. Handoff in that setup to up to 10!! seconds,
because the station went through a few authentications until it finally
authenticated successfully.

The handoff is created naturally, just by walking the laptop out of the
range of the first access point to the next access point. Mesh access points
just connect the access points wirelessly together instead of over a wired
distribution system.



-----Ursprungliche Nachricht-----
Von: hostap-bounces+stephan.schlumbohm=tu-harburg.de at shmoo.com
[mailto:hostap-bounces+stephan.schlumbohm=tu-harburg.de at shmoo.com] Im
Auftrag von Leonardo Maccari
Gesendet: Dienstag, 22. November 2005 03:48
An: hostap at shmoo.com
Betreff: Re: Handoff with wpa_supplicant and madwifi driver

On Sat, Nov 19, 2005 at 01:14:45PM -0800, Stephan Schlumbohm wrote:
> Hi all,
> 
> I'm having serious trouble with the handoff from one access point to
another using wpa_supplicant (stable 0.3.8 and development 0.4.6) with the
madwifi driver (madwifi-ng latest svn snapshot from madwifi.org).
> 
> Both access points have the same ESSID and operate on the same channel and
have the same security settings. In fact, those access points are mesh
access points - both are connected to a FreeRADIUS server.
> 
> Authentication (Open, WPA-PSK, WPA-802.1X-TLS/PEAP/TTLS) works fine in
this setup to each access point.
> 
> But, when I try to roam from one access point to another, wpa_supplicant
does not initiate a reassociation request to the new access point. Instead,
it disassociates the old access point, then it performs the scanning and
then finally goes through a full new authentication with the new access
point.

My experience says that scan time is not the real bottlenck, delay is
introduced by loss of conectivity _before_ triggering a new scan, then from
RADIUS authentication (multi-hop packets, worse in a mesh environment), and
finally some delays that I couldn't really explain after authentication and
before first EAPOL packet. Jouni said a few time ago that a bug was cleaned
that caused hostapd waste some time after authentication.
Anyway if you use WPA/WPA2 you must renegotiate the PMK key (whatever
authentication method you use) and renegotiate the PTK/GTK.

> 
> This causes the handoff to take about 1.5 to 3 seconds. This is not
acceptable and is not intended by the developers. A single channel handoff
should take about 10 to 300 ms (depending on authentication).
> 

there is an old thread about handoff times that you might read in the
archives. 

a couple questions: how do you trigger handoff procedure from one AP to
another? and what does mesh access points means? how do they authenticate
each other ?

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
Obviously -thisaintpartofmyaddress- is not part of my real email address 

_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap




From Florian.Prester  Fri Nov 25 04:23:36 2005
From: Florian.Prester (Florian Prester)
Date: Fri, 25 Nov 2005 13:23:36 +0100
Subject: wpa_supplicant FreeBSD 6.0: no PMKID found??
Message-ID: <43870248.6030206@rrze.uni-erlangen.de>

Hi all,

what means the following error message:

RSN: no matching PMKID found
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted

The authentication works fine, but the keymanagement fails.
Where do I have to look? I have no clue.

Thank you
Florian Prester

-- 
Dipl. Inf. Florian Prester
Network Administration
Regionales RechenZentrum Erlangen
Universitaet Erlangen-Nuernberg
Martensstr. 1
91052 Erlangen
Germany

Tel.: +499131 8527813





From engage  Fri Nov 25 10:57:57 2005
From: engage (engage)
Date: Fri, 25 Nov 2005 11:57:57 -0700
Subject: wpa_supplicant & winpcap & windows 2000
In-Reply-To: <20051122034259.GB9482@jm.kir.nu>
References: <200511201856.14134.engage@n0sq.us>
	<20051122034259.GB9482@jm.kir.nu>
Message-ID: <200511251157.57666.engage@n0sq.us>

On Monday 21 November 2005 08:42 pm, Jouni Malinen wrote:
>On Sun, Nov 20, 2005 at 06:56:13PM -0700, engage wrote:
>> Attached is a 30 second capture using ethereal:
>
>Thanks! This is getting somewhat confusing.. This capture file shows a
>successfully completed WPA authentication and even successful DHCP
>handshake after that. There is couple of extra EAPOL-Key frames after
>the normal WPA pairwise and group handshakes, but it looks like AP is
>just ignoring them and connection works after this..
>
>However, the debug log from wpa_supplicant showed a quite a bit
>different behavior. The different sizes for EAPOL-Key frames are likely
>caused by them actually being different frames (msg 3/4 and group key
>msg 1/2); not retransmission of msg 3/4 like I originally thought. In
>other words, supplicant is not sending out msg 4/4 since 3/4 failed
>validation. However, AP is assuming that the msg 4/4 was just dropped
>and continues to group key handshake.
>
>I don't know what would explain this different behavior, though. Have
>you ever noticed network working in this configuration? Would it be
>possible to get a debug log from wpa_supplicant and a matching Ethereal
>capture log from the same attempt (and maybe just leave it running for
>couple of minutes so that there are more than one failure)?

The same wpa_supplicant.conf is successfully being used on 2 other computers 
running the linux wpa_supplicant-0.4.5, 1 is a laptop with the ipw2200 driver 
and the other is a desktop with a Broadcom Corporation BCM4306 (using 
ndiswrapper). 

Anyway, I just booted the other laptop with the Netgear PC Card and now it is 
solidly working. Maybe I needed to wait longer? I did run ethereal for 5 
minutes if you still want to look at the log. Now, it's time to figure out 
how to set this up as a service. Thanks for the help. 



From jkmaline  Fri Nov 25 13:35:25 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 25 Nov 2005 13:35:25 -0800
Subject: Developers' documentation for wpa_supplicant and hostapd
Message-ID: <20051125213525.GF8969@jm.kir.nu>

I have been working on developers' documentation for wpa_supplicant
(http://hostap.epitest.fi/wpa_supplicant/devel/) for a while and it has
quite a bit of material already. I've now started doing the same for
hostapd and hopefully, at some point there will be similar documentation
available at the web site.

Finding functions to document is relatively easy, but it can get
difficult for me to figure out which areas of code need more comments.
Having worked on this for number of years and knowing the implementation
inside out is making lots of things look trivial.. It would be helpful
to get feedback from people who have tried to understand the
implementation and have found areas that are either very difficult to
understand or at least take a lot of time to figure out.

You have now a good chance to get explanation for your favorite
difficult to understand area! Just let me know where that is and I'll
try to make sure the implementation gets commented out properly to make
it easier and faster to understand what is going on and why.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Nov 27 11:41:33 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 27 Nov 2005 11:41:33 -0800
Subject: [PATCH] adding wpa_common.h
Message-ID: <20051127194133.GB8989@jm.kir.nu>

I haven't received messages from the mailing list for a while, so this
is based on web archives; sorry about breaking the thread.

> On Sat, Nov 19, 2005 at 07:37:55PM -0800, Jouni Malinen wrote:
> > Please re-diff your changes with -N option for diff so that the new file
> > (wpa_common.h) is included.
>
> here it is.

Thanks, applied with couple of minor changes. Please note that this
change is in development branch, not 0.4.x branch, even though your diff
was against v0.4.6.

-- 
Jouni Malinen                                            PGP id EFC895FA



From sebastian.roeder  Sun Nov 27 14:39:15 2005
From: sebastian.roeder (Sebastian =?utf-8?q?R=C3=B6der?=)
Date: Sun, 27 Nov 2005 23:39:15 +0100
Subject: wpa_supplicant on Linksys Router Wrt54G for wired eap-md5
Message-ID: <200511272339.15650.sebastian.roeder@uni-bielefeld.de>

I have successfuly installed openwrt on my Linksys WLAN-Router Wrt54G Version 
2.2. The router has a WAN Port (Internet), a 4-port switch (LAN) and wifi:

~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:13:10:27:DE:F3
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1041 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:618354 (603.8 KiB)
          Interrupt:5 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 00:13:10:27:DE:F5
          inet addr:192.168.178.11  Bcast:192.168.178.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2338 errors:0 dropped:0 overruns:0 frame:207969
          TX packets:2224 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:202761 (198.0 KiB)  TX bytes:337505 (329.5 KiB)
          Interrupt:4 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan0     Link encap:Ethernet  HWaddr 00:13:10:27:DE:F3
          inet addr:192.168.177.21  Bcast:192.168.177.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1782 (1.7 KiB)

vlan1     Link encap:Ethernet  HWaddr 00:13:10:27:DE:F3
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1038 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:616572 (602.1 KiB)

The interface layout is a little bit complicated - the is a good graphic on 
http://voidmain.is-a-geek.net/i/WRT54_sw1_internal_architecture.png

In short, eth0 is the switch itself - a Broadcom BCM5325. eth1 is the WLAN 
interface, vlan0 provides the 4 LAN ports (virtual interfaces, via tagging) 
and vlan1 provides the WAN port.

I have installed wpa_supplicant-0.4.7 on the router and use the following 
config to do eap-md5 authentification over the (wired) WAN port:

~# less /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=wheel
ap_scan=0
network={
        key_mgmt=IEEE8021X
        eap=MD5
        identity="my_user"
        password="my_passwd"
        eapol_flags=0
}

This config works perfect on my desktop maschine.

However wpa_supplicant -i vlan1 -D wired -c /etc/wpa-supplicant.conf -dd gives 
me the following:

Initializing interface 'vlan1' conf '/etc/wpa_supplicant.conf' driver 'wired' 
ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=0
Line: 4 - start of a new network block
key_mgmt: 0x8
eap methods - hexdump(len=2): 04 00
identity - hexdump_ascii(len=7):
     73 72 6f 65 64 65 72                              sroeder
password - hexdump_ascii(len=8): [REMOVED]
eapol_flags=0 (0x0)
Priority group 0
   id=0 ssid=''
Initializing interface (2) 'vlan1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wired_init: Added multicast membership with packet socket
Own MAC address: 00:13:10:27:de:f3
Setting scan request: 0 sec 100000 usec
Added interface vlan1
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
Associated to a new BSS: BSSID=01:80:c2:00:00:03
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=Auto
Associated with 01:80:c2:00:00:03
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL - hexdump(len=4): 01 01 00 00
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL - hexdump(len=4): 01 01 00 00
EAPOL: idleWhile --> 0
EAP: EAP entering state FAILURE
CTRL-EVENT-EAP-FAILURE EAP authentication failed
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state FAIL
EAPOL: SUPP_PAE entering state HELD
EAPOL: SUPP_BE entering state IDLE
EAPOL: startWhen --> 0

tcpdump shows that there is NOTHING going on on vlan1 - one would think the 
cable is not plugged or something. But it is of cause and the cable is OK (I 
use it on my desktop box without problems).

Does this config need some extra care, doesn't wpa_supplicant handle the vlan 
interfaces right or what else might be the problem here? I guess my problem 
is related to this very "special" hardware. Now I hope some networking gurus 
can give me some pointers in which direction I should hunt the problem down.

Thanks in advance.

One difference that sticks in my mind is that the desktop uses kernel 2.6 
while the router is on 2.4.30.



From nix.bh.tan  Sun Nov 27 18:00:46 2005
From: nix.bh.tan (nix.bh.tan at sg.pwc.com)
Date: Mon, 28 Nov 2005 10:00:46 +0800
Subject: Nix BH Tan/SG/GTS/PwC is out of the office.
Message-ID: <OFFACA73A6.0041CC38-ON482570C7.000B0EC7-482570C7.000B0EC8@pwc.com>

I will be out of the office starting  27/11/2005 and will not return until
02/12/2005.

For assistance on network issues, please contact Tan Tiong Hwee @ 4132 .
For assistance on Lotus Notes issues, please contact Mary Heng or Kevin
Juay @ 4137 & 3671 respectively. For assistance on general issues, please
contact the GTS helpdesk @ 7000.
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.




From jakob.alvermark  Mon Nov 28 02:22:47 2005
From: jakob.alvermark (Jakob Alvermark)
Date: Mon, 28 Nov 2005 11:22:47 +0100
Subject: Wired authentication on FreeBSD?
Message-ID: <1133173367.12084.5.camel@dyn-office-8.teligent.se>

Hi,

I am new to this and playing around.
I would like to test wired authentication to start with.
I got FreeBSD 6.0-RELEASE and I downloaded the latest stable hostapd.
However it doesn't seem to compile, is it supposed to?

Regards,
Jakob Alvermark




From jkmaline  Mon Nov 28 07:58:00 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 28 Nov 2005 07:58:00 -0800
Subject: Wired authentication on FreeBSD?
In-Reply-To: <1133173367.12084.5.camel@dyn-office-8.teligent.se>
References: <1133173367.12084.5.camel@dyn-office-8.teligent.se>
Message-ID: <20051128155800.GB8977@jm.kir.nu>

On Mon, Nov 28, 2005 at 11:22:47AM +0100, Jakob Alvermark wrote:

> I would like to test wired authentication to start with.
> I got FreeBSD 6.0-RELEASE and I downloaded the latest stable hostapd.
> However it doesn't seem to compile, is it supposed to?

It is supposed to compile, but I don't know whether this version has
been tested on FreeBSD 6.0. I'm using a cross compiler on Linux to
verify the builds before releases (well, if I remember to ;-) and at
least I'm able to build it using this setup. I have header files from
one of the 6.0 test releases, so they may be a bit different from the
official release, though.

Actually, now that I look more closely, I'm not including driver_wired.c
in the FreeBSD test build. Once I added it, I was able to reproduce this
problem. driver_wired.c has not been ported to FreeBSD yet. There isn't
much code in it and l2_packet_freebsd.c is likely to already have most
of the needed functionality, so it should be relatively easy to get this
built for FreeBSD. The best option would likely be to first convert it
to use l2_packet and then go through the remaining parts (e.g.,
multicast membership management) which may need changing.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 28 08:02:19 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 28 Nov 2005 08:02:19 -0800
Subject: wpa_supplicant FreeBSD 6.0: no PMKID found??
In-Reply-To: <43870248.6030206@rrze.uni-erlangen.de>
References: <43870248.6030206@rrze.uni-erlangen.de>
Message-ID: <20051128160219.GC8977@jm.kir.nu>

On Fri, Nov 25, 2005 at 01:23:36PM +0100, Florian Prester wrote:

> what means the following error message:
> 
> RSN: no matching PMKID found

This would normally indicate that the driver tried to use PMKSA caching
by including PMKID in the association request, but a matching entry was
not found in the wpa_supplicant PMKSA cache.

> WPA: Failed to get master session key from EAPOL state machines
> WPA: Key handshake aborted

EAP did not provide key material, e.g., because it did not actually
complete successfully (key may be generated, but the final success
message is not accepted, etc.).

> The authentication works fine, but the keymanagement fails.
> Where do I have to look? I have no clue.

I would like to see full debug log showing this behavior, i.e., output
of wpa_supplicant when run on foreground with -dd on the command line.

-- 
Jouni Malinen                                            PGP id EFC895FA



From cristian.ionescu-idbohrn  Mon Nov 28 07:59:53 2005
From: cristian.ionescu-idbohrn (Cristian Ionescu-Idbohrn)
Date: Mon, 28 Nov 2005 16:59:53 +0100 (CET)
Subject: syslog messages (was: wpa_supplicant FreeBSD 6.0: no PMKID found??)
In-Reply-To: <20051128160219.GC8977@jm.kir.nu>
References: <43870248.6030206@rrze.uni-erlangen.de>
	<20051128160219.GC8977@jm.kir.nu>
Message-ID: <0511281653240.18170@somehost>

Jouni,

On Mon, 28 Nov 2005, Jouni Malinen wrote:

[snip]

> I would like to see full debug log showing this behavior, i.e.,
> output of wpa_supplicant when run on foreground with -dd on the
> command line.

Do you have any plans making possible to get debug log (and other)
messages to the syslog too? That would be very useful, specially when
wpa_supplicant runs on embeded systems.


Cheers,
Cristian



From jakob.alvermark  Mon Nov 28 08:01:00 2005
From: jakob.alvermark (Jakob Alvermark)
Date: Mon, 28 Nov 2005 17:01:00 +0100
Subject: Wired authentication on FreeBSD?
In-Reply-To: <20051128155800.GB8977@jm.kir.nu>
Message-ID: <20051128162110.A3616134062@mail.iocaine.com>

Alright.
I am not a developer (I once was but that was years ago), so I'm probably
not the best man to fix it. Is there someone willing to have a look at it?

Regards,
Jakob

-----Original Message-----
Subject: Re: Wired authentication on FreeBSD?

On Mon, Nov 28, 2005 at 11:22:47AM +0100, Jakob Alvermark wrote:

> I would like to test wired authentication to start with.
> I got FreeBSD 6.0-RELEASE and I downloaded the latest stable hostapd.
> However it doesn't seem to compile, is it supposed to?

It is supposed to compile, but I don't know whether this version has
been tested on FreeBSD 6.0. I'm using a cross compiler on Linux to
verify the builds before releases (well, if I remember to ;-) and at
least I'm able to build it using this setup. I have header files from
one of the 6.0 test releases, so they may be a bit different from the
official release, though.

Actually, now that I look more closely, I'm not including driver_wired.c
in the FreeBSD test build. Once I added it, I was able to reproduce this
problem. driver_wired.c has not been ported to FreeBSD yet. There isn't
much code in it and l2_packet_freebsd.c is likely to already have most
of the needed functionality, so it should be relatively easy to get this
built for FreeBSD. The best option would likely be to first convert it
to use l2_packet and then go through the remaining parts (e.g.,
multicast membership management) which may need changing.

-- 
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap





From maccari-thisaintpartofmyaddress-  Mon Nov 28 08:16:04 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Mon, 28 Nov 2005 17:16:04 +0100
Subject: Handoff with wpa_supplicant and madwifi driver
In-Reply-To: <000701c5f171$a7ab0a50$1502a8c0@stephansmobile>
References: <20051122114741.GB19458@lenst.det.unifi.it>
	<000701c5f171$a7ab0a50$1502a8c0@stephansmobile>
Message-ID: <20051128161604.GB15228@lenst.det.unifi.it>

On Thu, Nov 24, 2005 at 07:38:04PM -0800, Stephan Schlumbohm wrote:
> I did some testing with the same wireless card under Windows with a Cisco
> driver (and supplicant) and got a handoff time of less than 300 ms on
> average. In this setup the station is sending re-association request frames
> to the new access point.

As far as I understood it, in 802.11i reassociation is thought to be done within the
same AP with which you had previuos association, if you try to reassociate
with an AP that you never authenticated with, it should deauthenticate you
and force you to have standard 802.11 authentication. so if cisco cards behave
like this, it might be a particular cisco behaviuor. what kind of AP are
you using? 


> 
> The handoff is created naturally, just by walking the laptop out of the
> range of the first access point to the next access point. Mesh access points
> just connect the access points wirelessly together instead of over a wired
> distribution system.

if this is your situation you might want to check out what
pre-authentication does, it might help performance.
see also different roaming modes in hostap driver and selective scan in
driver scan, that might help the scan phase. 

ciao,
leonardo.
-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 




From maccari-thisaintpartofmyaddress-  Mon Nov 28 08:27:55 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Mon, 28 Nov 2005 17:27:55 +0100
Subject: Developers' documentation for wpa_supplicant and hostapd
In-Reply-To: <20051125213525.GF8969@jm.kir.nu>
References: <20051125213525.GF8969@jm.kir.nu>
Message-ID: <20051128162755.GC15228@lenst.det.unifi.it>

On Fri, Nov 25, 2005 at 01:35:25PM -0800, Jouni Malinen wrote:
> You have now a good chance to get explanation for your favorite
> difficult to understand area! Just let me know where that is and I'll
> try to make sure the implementation gets commented out properly to make
> it easier and faster to understand what is going on and why.

I think the double macro definition in eapol_sm.c is confusing to get at
first glance.

ciao,
leonardo.
-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 




From maccari-thisaintpartofmyaddress-  Mon Nov 28 08:29:33 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Mon, 28 Nov 2005 17:29:33 +0100
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <20051108103939.GC4458@lenst.det.unifi.it>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
	<20051108103939.GC4458@lenst.det.unifi.it>
Message-ID: <20051128162933.GD15228@lenst.det.unifi.it>

On Tue, Nov 08, 2005 at 11:39:39AM +0100, Leonardo Maccari wrote:
> On Mon, Nov 07, 2005 at 02:56:52AM +0100, thomas schorpp wrote:
> link to an overview of git:
> http://linux.yyz.us/git-howto.html

It happened to me to try to work with git. I realized that the link I
posted it's the only documentation around, and while asking help to kernel
hackers I received this kind of answer more then once "I know how to use
git just for what I need it, and I really don't want to know more than
that".
So, before changing to git it might be a good idea to let it stabilize and
have some more docs.

ciao,
leonardo.

-- 
   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 




From frank  Mon Nov 28 09:17:25 2005
From: frank (frank at meerkoetter.org)
Date: Mon, 28 Nov 2005 18:17:25 +0100
Subject: wpa_supplicant network selection
Message-ID: <20051128181725.negeuotahao8w4sc@admin.betaversion.net>

Hi,

i'm interested in how exactly the wpa_supplicant selects networks.
The documentation states:

> Configuration file can include one or more network blocks, e.g., one
> for each used SSID. wpa_supplicant will automatically select the best
> betwork based on the order of network blocks in the configuration
> file, network security level (WPA/WPA2 is prefered), and signal
> strength.

The comments in the example configuration also state that this selection
is influenced by the priority of a network block.

I did a quick survey of the source code but couldn't find the code which
does the selection based on signal strength in events.c.

Is selection based on signal strength already implemented?

Regards,
  Frank




From bboissin+hostap  Mon Nov 28 10:57:18 2005
From: bboissin+hostap (Benoit Boissinot)
Date: Mon, 28 Nov 2005 19:57:18 +0100
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <20051128162933.GD15228@lenst.det.unifi.it>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
	<20051108103939.GC4458@lenst.det.unifi.it>
	<20051128162933.GD15228@lenst.det.unifi.it>
Message-ID: <20051128185718.GA17125@ens-lyon.fr>

On 11/28/05, Leonardo Maccari
<maccari-thisaintpartofmyaddress- at lenst.det.unifi.it> wrote:
> On Tue, Nov 08, 2005 at 11:39:39AM +0100, Leonardo Maccari wrote:
> > On Mon, Nov 07, 2005 at 02:56:52AM +0100, thomas schorpp wrote:
> > link to an overview of git:
> > http://linux.yyz.us/git-howto.html
>
> It happened to me to try to work with git. I realized that the link I
> posted it's the only documentation around, and while asking help to kernel
> hackers I received this kind of answer more then once "I know how to use
> git just for what I need it, and I really don't want to know more than
> that".
> So, before changing to git it might be a good idea to let it stabilize and
> have some more docs.
>

If you want to look at the alternatives, maybe you can try mercurial [1].
It has a good performance [2] (the initial goal was to be able to track
the kernel) and the UI is easier to understand than git.

regards,

Benoit

[1] http://www.selenic.com/mercurial
[2] http://www.keltia.net/EuroBSDCon/paper.pdf / http://www.keltia.net/EuroBSDCon/slides.pdf



From chip  Mon Nov 28 11:44:14 2005
From: chip (Chip Salzenberg)
Date: Mon, 28 Nov 2005 11:44:14 -0800
Subject: wpa_supplicant requires restart on PCMCIA re-insertion
Message-ID: <20051128194414.GI6446@tytlal.topaz.cx>

I've been forced to stop and start wpa_supplicant whenever I re-insert the
PCMCIA wireless card.  (D-Link DWL-650, one of the old ones.)

One of the things I like best about wpa_supplicant is its flexible
configuration, which should allow it to run all day in the background and
automatically associate to one wireless network after another.  Sadly, this
has not been the case with wpa_supplicant 0.4.6 and 0.4.7 (I've tried both),
at least with the Linux kernel 2.6.14 hostap driver (0.4.4-kernel).[*]

It's running as:

   /usr/sbin/wpa_supplicant -B -w -i wlan0 -D hostap -c /etc/wpa_supplicant.conf

What additional debug info should I provide to help diagnose this issue?

[*] For those of you who remember my earlier hostap driver problem: I was
    going to post debugging info, but the problem disappeared with a Debian
    kernel upgrade (still 2.6.14), then reappeared with the next upgrade
    (still 2.6.14).  Current evidence suggests that it's all about IRQ
    allocation: by forcing assignment to a limited set of IRQs (specifically
    avoiding 3,5, and 7), I've gotten apparently reliable success.
-- 
Chip Salzenberg <chip at pobox.com>



From rjc  Mon Nov 28 13:51:52 2005
From: rjc (Bob Carlson)
Date: Mon, 28 Nov 2005 15:51:52 -0600
Subject: L2 test code?
Message-ID: <20051128135527.BAD988D8@dm17.mta.everyone.net>

I am just testing my port of the wpa supplicant core. The driver test
package and the test vectors for AES have proven very handy. Is there test
code available for the L2 driver? I haven't found any yet.

Cheers, Bob




From proski  Mon Nov 28 19:20:07 2005
From: proski (Pavel Roskin)
Date: Mon, 28 Nov 2005 22:20:07 -0500
Subject: [PATCH] Changing peer address for WDS interfaces
Message-ID: <1133234407.27750.52.camel@dv>

It may be useful to change the peer address for WDS interfaces.  I found
this functionality in the current MadWifi driver and I thought maybe
hostap could have this feature as well.

The "Access Point" value reported by iwconfig for WDS interfaces is the
MAC address of the peer.  iwconfig can set that value as well.  This
patch makes it possible to set the peer address of WDS interfaces using
iwconfig.

Since WDS is implemented in software, there should be no need to reset
the card.

The code could have some protection against duplicate addresses, but I
think it would bloat the code and inconvenience users e.g. when peer
addresses are swapped between two WDS interfaces.

Signed-off-by: Pavel Roskin <proski at gnu.org>

diff --git a/drivers/net/wireless/hostap/hostap_ioctl.c b/drivers/net/wireless/hostap/hostap_ioctl.c
index 2617d70..8a73444 100644
--- a/drivers/net/wireless/hostap/hostap_ioctl.c
+++ b/drivers/net/wireless/hostap/hostap_ioctl.c
@@ -713,6 +713,11 @@ static int prism2_ioctl_siwap(struct net
 	iface = netdev_priv(dev);
 	local = iface->local;
 
+	if (iface->type == HOSTAP_INTERFACE_WDS) {
+		memcpy(iface->u.wds.remote_addr, &ap_addr->sa_data, ETH_ALEN);
+		return 0;
+	}
+
 	memcpy(local->preferred_ap, &ap_addr->sa_data, ETH_ALEN);
 
 	if (local->host_roaming == 1 && local->iw_mode == IW_MODE_INFRA) {


-- 
Regards,
Pavel Roskin




From proski  Mon Nov 28 21:27:11 2005
From: proski (Pavel Roskin)
Date: Tue, 29 Nov 2005 00:27:11 -0500
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <20051128185718.GA17125@ens-lyon.fr>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
	<20051108103939.GC4458@lenst.det.unifi.it>
	<20051128162933.GD15228@lenst.det.unifi.it>
	<20051128185718.GA17125@ens-lyon.fr>
Message-ID: <1133242031.27750.72.camel@dv>

Hello!

First of all, I'm very positive about switching to git.  After trying
git, CVS doesn't feel like a version control system at all ("cvs log"
doesn't do the right thing) and even subversion seems limited (where's
gitk for subversion?)

On Mon, 2005-11-28 at 19:57 +0100, Benoit Boissinot wrote:
> On 11/28/05, Leonardo Maccari
> <maccari-thisaintpartofmyaddress- at lenst.det.unifi.it> wrote:
> > It happened to me to try to work with git. I realized that the link I
> > posted it's the only documentation around, and while asking help to kernel
> > hackers I received this kind of answer more then once "I know how to use
> > git just for what I need it, and I really don't want to know more than
> > that".

That's OK.  git is a low level interface.  Nobody is supposed to know
all its commands.  I use cogito for almost everything.

> > So, before changing to git it might be a good idea to let it stabilize and
> > have some more docs.

Version 1.0 is around the corner.  The documentation is quite extensive.
Run "make doc" to generate manuals.  Run "make rpm" to generate rpm
packages including manuals.

Most importantly, git has been used for months on very serious projects
and I'm not aware of any data loss.

> If you want to look at the alternatives, maybe you can try mercurial [1].
> It has a good performance [2] (the initial goal was to be able to track
> the kernel) and the UI is easier to understand than git.

Mercurial is good, but I would prefer git for anything kernel related
just for compatibility reasons.

Also, mercurial is less popular, so hgk lags behind gitk, I'm not aware
of a qgit equivalent for mercurial (it looks like gitk, but works much
faster), and I haven't heard of anything like StGIT for mercurial (StGIT
allows to refine patches).

As for comparing the command line interface, mercurial should be
compared to cogito, and they are on the par (in my opinion).

-- 
Regards,
Pavel Roskin




From andreaf  Tue Nov 29 14:28:35 2005
From: andreaf (Andrea G Forte)
Date: Tue, 29 Nov 2005 17:28:35 -0500
Subject: wpa-psk and hostap problem.
Message-ID: <438CD613.90606@cs.columbia.edu>

Hi all.

I was conducting some experiments with a Netgear AP, and two linux 
laptops (kernel 2.4). On one of the laptops I used hostap 0.3.9 and 
wpa_supplicant 0.4.7 and on the other laptop I used hostap-driver0.3.9 
without any supplicant. On the AP I enabled WPA-PSK. Now, according to 
the standard, a client should first associate to the AP and then perform 
authentication. A long time ago I used hostAP as AP in a similar 
scenario and if I remember correctly it was following this behavior. 
However, the problem is that now the laptop on which I do *not* run the 
supplicant it even fails associating to the AP. I always get association 
failed (Linkstatus = 6). Is this a problem related to the Netgear AP 
that does not follow the standard or is it a problem with the hostap 
driver? The laptop with the wpa_supplicant associates correctly even if 
with a few problems (association fails many times before everything goes 
through).

Thank you for your help,
Andrea




From support8  Tue Nov 29 16:04:59 2005
From: support8 (Eliot, Wireless and Server Administrator,
	Great Lakes Internet)
Date: Tue, 29 Nov 2005 19:04:59 -0500
Subject: RADIUS + EAP AVP Structure
Message-ID: <0633E0EDB4F25F43A2D7179CA11FAFAB1D660C@xavier.staff.greatlakes.net>


I am trying to write an IAS extension DLL, but I'm having trouble
figuring out the EAP stuff that I need to do. I thought someone on this
list might be able to help me.

When an EAP attribute (79) is specified in a RADIUS Access-Challenge,
what is the structure of the value?

What I know is that it is basically a pointer to some data structure
(I'm assuming some EAP data structure). I have seen about 5 different
structures in the Microsoft documentation and I'm not sure which one is
used in the RADIUS attribute or how to tell what is being used. Is it
this one:

1 bit mandatory flag
1 bit reserved flag
14 bit type
16 bit length
Followed by data

Or, is it an array of these where the next one starts after <length>
bytes of data have been read, or is it something else entirely?

And, does the type field I listed in this packet layout correspond to
the same type field that you would set to a value of 8 to specify an
EAP-TLV URI attribute? 

Is this information encrypted in some way and needs to be decrypted
first, or should I be able to read it if I can read the username,
password, and other RADIUS attributes?

Also, if I test the RADIUS attributes, there are two types that interest
me. One type is what FreeRADIUS terms "EAP-Message" and that is type ID
79. The other type is what Microsoft calls ratEAPTLV, which I'm not
certain what the number is for that one. Are these two different RADIUS
attributes, or does a TLV go in an "EAP-Message" attribute as the value?


Anyway, I thought maybe the authors of WPA Supplicant or people who
contribute might be able to answer my questions for me. 

Thanks in advance for any help. 

Eliot Gable
Certified Wireless Network Administrator (CWNA)
Certified Wireless Security Professional (CWSP)
Cisco Certified Network Associate (CCNA)
CompTIA Security+ Certified
CompTIA Network+ Certified
Network and Systems Administrator
Great Lakes Internet, Inc.
112 North Howard
Croswell, MI 48422
(810) 679-3395
(877) 558-8324
 
Now offering Broadband Wireless Internet access in Croswell, Lexington,
Brown City, Yale, and Sandusky. Call for details.




From bryan  Tue Nov 29 18:25:37 2005
From: bryan (Bryan Kadzban)
Date: Tue, 29 Nov 2005 21:25:37 -0500
Subject: RADIUS + EAP AVP Structure
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB1D660C@xavier.staff.greatlakes.net>
References: <0633E0EDB4F25F43A2D7179CA11FAFAB1D660C@xavier.staff.greatlakes.net>
Message-ID: <438D0DA1.2050909@kadzban.is-a-geek.net>

Eliot wrote:
> When an EAP attribute (79) is specified in a RADIUS Access-Challenge,
> what is the structure of the value?

Take a look at a network capture (either Ethereal or MS Network Monitor)
-- that might give some useful information.

In particular, you should note that EAP data sent by the supplicant gets
repackaged into RADIUS attributes by the AP.  And since the length of a
RADIUS attribute is given (in the packet at least) by a single byte, the
maximum length is 255 -- so if the EAP data is longer than 255 bytes,
it'll take up more than one RADIUS attribute.

I'm not sure how each attribute's data is represented, although I would
guess that Ethereal's RADIUS dissector knows.  Perhaps it even knows
well enough to give you the original EAPOL frame.

> Also, if I test the RADIUS attributes, there are two types that 
> interest me. One type is what FreeRADIUS terms "EAP-Message" and that
> is type ID 79.

IIRC, that's the one that contains each piece of the EAP data.  Many of
these can exist in a single RADIUS request (up to the maximum size of a
RADIUS packet, minus any other attributes that have been included).
Microsoft's IAS extension API doesn't have a name for that one, but it's
the one you should be looking for if you're doing EAP from wireless clients.

> The other type is what Microsoft calls ratEAPTLV, which I'm not 
> certain what the number is for that one.

According to:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ias/ias/radius_attribute_type.asp

the number is 272.  It also says "see the IETF draft for EAP-TLV"
(and gives a 404 link), which I would presume contains part of the EAP
packet's format.  Although I don't know why it doesn't use 79...  maybe
because it's nonstandard?  Many of the other 2xx attributes on that page
seem to be extension attributes; maybe this one is similar.

Maybe you should see if there's anything else helpful in that IAS
extension DLL reference section of MSDN.  Failing that, see if perhaps
your company has a contact with Microsoft who might know who to ask
about stuff like this (like my company did with cert services, when we
had questions about autoenrollment) -- or possibly use a development
support call.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20051129/5fe62930/attachment.pgp 


From jkmaline  Tue Nov 29 20:25:02 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 29 Nov 2005 20:25:02 -0800
Subject: wpa-psk and hostap problem.
In-Reply-To: <438CD613.90606@cs.columbia.edu>
References: <438CD613.90606@cs.columbia.edu>
Message-ID: <20051130042502.GF8948@jm.kir.nu>

On Tue, Nov 29, 2005 at 05:28:35PM -0500, Andrea G Forte wrote:

> I was conducting some experiments with a Netgear AP, and two linux 
> laptops (kernel 2.4). On one of the laptops I used hostap 0.3.9 and 
> wpa_supplicant 0.4.7 and on the other laptop I used hostap-driver0.3.9 
> without any supplicant. On the AP I enabled WPA-PSK. Now, according to 
> the standard, a client should first associate to the AP and then perform 
> authentication.

Also according to the standard, the AP that is configured to use WPA
must reject association if the client does not use WPA..

> However, the problem is that now the laptop on which I do *not* run the 
> supplicant it even fails associating to the AP. I always get association 
> failed (Linkstatus = 6). Is this a problem related to the Netgear AP 
> that does not follow the standard or is it a problem with the hostap 
> driver?

I have hard time trying to understand this explanation.. Could you
please explain what you were expecting to see and what you think is
incorrect behavior? If I understood this setup correctly, you have AP
configured to use WPA and the client (the one not running
wpa_supplicant) configured not to use WPA. Did I understand that
correctly? If yes, the expected behavior is that the client does not
complete association with this AP and that seems to be exactly what is
happening here..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Nov 29 20:35:07 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 29 Nov 2005 20:35:07 -0800
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <1133242031.27750.72.camel@dv>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
	<20051108103939.GC4458@lenst.det.unifi.it>
	<20051128162933.GD15228@lenst.det.unifi.it>
	<20051128185718.GA17125@ens-lyon.fr> <1133242031.27750.72.camel@dv>
Message-ID: <20051130043507.GG8948@jm.kir.nu>

On Tue, Nov 29, 2005 at 12:27:11AM -0500, Pavel Roskin wrote:

> First of all, I'm very positive about switching to git.  After trying
> git, CVS doesn't feel like a version control system at all ("cvs log"
> doesn't do the right thing) and even subversion seems limited (where's
> gitk for subversion?)

Compared to CVS, many things look quite a bit nicer.. ;-) However, I
don't see subversion going far enough to justify the effort to
converting from CVS (when it is used in the way I use it; i.e., commits
considered as changesets and additional tools used to process these
changesets).

> Mercurial is good, but I would prefer git for anything kernel related
> just for compatibility reasons.

That is one of my main reasons for git, too. I have to use it for kernel
development anyway, so why not use the same tool for other parts of the
project. Kernel development with git is also likely to make sure that
someone will continue maintaining git for the foreseeable future.

One concern with git has been mentioned and that is availability of it
for all the target systems that are currently used for wpa_supplicant or
hostapd development. I want to make sure that at least *BSD have easy
access to the needed tools before replacing CVS. Windows (or at least
cygwin) support would also be nice to have.
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Nov 29 20:38:40 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 29 Nov 2005 20:38:40 -0800
Subject: syslog messages (was: wpa_supplicant FreeBSD 6.0: no PMKID
	found??)
In-Reply-To: <0511281653240.18170@somehost>
References: <43870248.6030206@rrze.uni-erlangen.de>
	<20051128160219.GC8977@jm.kir.nu> <0511281653240.18170@somehost>
Message-ID: <20051130043840.GH8948@jm.kir.nu>

On Mon, Nov 28, 2005 at 04:59:53PM +0100, Cristian Ionescu-Idbohrn wrote:

> Do you have any plans making possible to get debug log (and other)
> messages to the syslog too? That would be very useful, specially when
> wpa_supplicant runs on embeded systems.

Yes, that is on my to-do list and also recorded in bugzilla as an open
case (http://hostap.epitest.fi/bugz/show_bug.cgi?id=78). It was mainly
waiting for the new development tree (0.5.x) materialize and since that
has happened, it would be good time to merge in syslog support.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Nov 29 20:43:04 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 29 Nov 2005 20:43:04 -0800
Subject: L2 test code?
In-Reply-To: <20051128135527.BAD988D8@dm17.mta.everyone.net>
References: <20051128135527.BAD988D8@dm17.mta.everyone.net>
Message-ID: <20051130044304.GI8948@jm.kir.nu>

On Mon, Nov 28, 2005 at 03:51:52PM -0600, Bob Carlson wrote:

> I am just testing my port of the wpa supplicant core. The driver test
> package and the test vectors for AES have proven very handy. Is there test
> code available for the L2 driver? I haven't found any yet.

No, I don't think there is such a thing. RX side should be relatively
simple (i.e., less than 20 lines or so of code) to test by just
initializing eloop and registering l2_packet handler for, say, IP
packets. Sending would not require much more if the goal is to just see
that something goes out can be seen with a sniffer from an external
device.

This kind of test tool would fit in quite well with testing another area,
i.e., the driver interface code. Adding simple test programs for both
interfaces would sound like a useful addition..

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Tue Nov 29 22:40:41 2005
From: proski (Pavel Roskin)
Date: Wed, 30 Nov 2005 01:40:41 -0500
Subject: Host AP/hostapd/wpa_supplicant repository and cvs vs. git
In-Reply-To: <20051130043507.GG8948@jm.kir.nu>
References: <20051107004134.GW9194@jm.kir.nu> <436EB464.9050107@gmx.de>
	<20051108103939.GC4458@lenst.det.unifi.it>
	<20051128162933.GD15228@lenst.det.unifi.it>
	<20051128185718.GA17125@ens-lyon.fr> <1133242031.27750.72.camel@dv>
	<20051130043507.GG8948@jm.kir.nu>
Message-ID: <1133332841.16360.6.camel@dv>

On Tue, 2005-11-29 at 20:35 -0800, Jouni Malinen wrote:

> One concern with git has been mentioned and that is availability of it
> for all the target systems that are currently used for wpa_supplicant or
> hostapd development. I want to make sure that at least *BSD have easy
> access to the needed tools before replacing CVS. Windows (or at least
> cygwin) support would also be nice to have.

I haven't seen anyone voicing such concerns.  *BSD is supported.  Cygwin
is supported.  Only native Windows git is problematic because of git's
reliance on shell scripts.

-- 
Regards,
Pavel Roskin




From cristian.ionescu-idbohrn  Wed Nov 30 01:15:48 2005
From: cristian.ionescu-idbohrn (Cristian Ionescu-Idbohrn)
Date: Wed, 30 Nov 2005 10:15:48 +0100 (CET)
Subject: syslog messages
In-Reply-To: <20051130043840.GH8948@jm.kir.nu>
References: <43870248.6030206@rrze.uni-erlangen.de>
	<20051128160219.GC8977@jm.kir.nu>
	<0511281653240.18170@somehost> <20051130043840.GH8948@jm.kir.nu>
Message-ID: <0511301013490.18170@somehost>

On Tue, 29 Nov 2005, Jouni Malinen wrote:

> Yes, that is on my to-do list and also recorded in bugzilla as an open
> case (http://hostap.epitest.fi/bugz/show_bug.cgi?id=78). It was mainly
> waiting for the new development tree (0.5.x) materialize and since that
> has happened, it would be good time to merge in syslog support.

Now I'm happy :)


Cheers,
Cristian



From throw_away_2002  Wed Nov 30 02:33:08 2005
From: throw_away_2002 (Tom)
Date: Wed, 30 Nov 2005 02:33:08 -0800 (PST)
Subject: Still can't connect
In-Reply-To: <20051122035045.GC9482@jm.kir.nu>
Message-ID: <20051130103308.82432.qmail@web52102.mail.yahoo.com>

--- Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> It looks like ndiswrapper is not reporting
> association information to wpa_supplicant. This
> could end up in a mismatch in WPA IE for message
> 2/4 which would lead to AP rejecting this packet
> from the supplicant.
> 
> Could you please re-try this with 'iwevent'
> running at the same time to make sure that
> ndiswrapper is indeed not reporting association
> information when the association happens? In
> addition, I would be interested in seeing whether
> the behavior changes if this test is run
> with wpa_supplicant v0.4.7.

Upgraded to 0.4.7 before trying anything.

# iwevent
Waiting for Wireless Events from interfaces...
Warning: Driver for device wlan0 has been compiled with version 18
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...

10:18:27.774310    wlan0    Set Mode:Managed

# dog /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
        group=TKIP
        key_mgmt=WPA-PSK
        pairwise=TKIP
        proto=WPA
        psk="ur57I11ag00FBA11"
        ssid="localdomain"
        }

# wpa_supplicant -Dndiswrapper -c/etc/wpa_supplicant.conf -iwlan0 -dd

[including only the part that loops]
RX EAPOL from [ REMOVED ]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 e9 d8 88 a2 56 1d 09 e7 25 ed 63 32 0b e1 40 8f 9f 40 df 91 bb
19 ce e2 37 c7 d4 9c f0 23 13 42 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 e9 d8 88 a2 56 1d 09 e7 25 ed 63 32 0b e1 40 8f 9f 40
df 91 bb 19 ce e2 37 c7 d4 9c f0 23 13 42 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATING -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:ea:31:82 (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): a4 5d 83 05 68 9f 24 2b 5d f8 71
c6 34 c0 af ea b9 3a 5d a1 63 4f c6 b1 1e 17 4c 89 70 44 5d 0c
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00
00 00 00 00 00 01 a4 5d 83 05 68 9f 24 2b 5d f8 71 c6 34 c0 af ea b9 3a
 5d a1 63 4f c6 b1 1e 17 4c 89 70 44 5d 0c 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d
d4 25 e8 24 fa c8 db fa d4 a9 09 f2 23 95 d9 00 18 dd 16 00 50 f2 01 01
00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RX EAPOL from [ REMOVED ]
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 c6 1d 42 d0 d5 15 de 86 f1 37 67 16 51 f6 4f 76 c6 51 7f 52 30
67 09 2e 6c d1 f3 19 f0 8d 65 a4 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 c6 1d 42 d0 d5 15 de 86 f1 37 67 16 51 f6 4f 76 c6 51
7f 52 30 67 09 2e 6c d1 f3 19 f0 8d 65 a4 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:ea:31:82 (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00
00 00 00 00 00 01 a4 5d 83 05 68 9f 24 2b 5d f8 71 c6 34 c0 af ea b9 3a
 5d a1 63 4f c6 b1 1e 17 4c 89 70 44 5d 0c 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 52
8f cd 7a 81 f5 e7 cb d1 ae ec bc a5 db 81 f8 00 18 dd 16 00 50 f2 01 01
00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02

Let me know if you need anything else. Thanks again.

Tom


		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/



From klaasdc  Wed Nov 30 03:30:11 2005
From: klaasdc (Klaas De Craemer)
Date: Wed, 30 Nov 2005 12:30:11 +0100
Subject: Problems connecting to "ANY" ap...
Message-ID: <f59e60020511300330k54d87d22i@mail.gmail.com>

Hello

Recently I bought a Senao 2511CD pccard with Prism2.5 chipset. In
windows, the card works perfect, it auto-connects to any accesspoint
it sees. However, in Linux, configuring it is a real mess. I compiled
the hostap 0.4.7 driver, and my dmesg output shows:

hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.4.7 - 2005-11-20 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0100-0x013f
prism2_hw_init: initialized in 196 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.0
wifi0: STA: id=0x1f v1.8.2
wifi0: registered netdevice wlan0

Now, the point is that 'iwconfig' won't do much. For example:
iwconfig wlan0 mode managed
iwconfig wlan0 essid "any"
And nothing happens, the card's status led stays dark, while under
windows, it keeps lit all the time. Even if I first set 'prism2_param
wlan0 host_roaming 1' as stated in the readme.
But if I start kwirelessmonitor and use the experimental feature to
set the network name to "any", the status led on the card immediately
lights up and I'm connected. If I reinsert the card, the problem is
back and the only way to connect to an accesspoint is via
kwirelessmonitor.
Also things like 'iwlist wlan0 scanning' gives:
wlan0     Interface doesn't support scanning : Network is down
What is going on? I don't seem to have this with the wlan_ng drivers.

Klaas De Craemer



From ars  Wed Nov 30 06:28:18 2005
From: ars (Arseniy Chernov)
Date: Wed, 30 Nov 2005 17:28:18 +0300
Subject: Michael Countermeasures tracing
In-Reply-To: <437DC866.4000007@hasborg.com>
References: <437DA7D5.3000008@itconnection.ru> <437DC866.4000007@hasborg.com>
Message-ID: <438DB702.3030001@itconnection.ru>

Hello Joshua,

Returning back to our short thread, I'd like to report that we've 
updated all stations' drivers (see below) and started monitoring that 
buggy RF environment 7 workdays ago.

The average amount of Michael errors in WPA-PSK has decreased 
dramatically, but still, there are some of them occuring daily (3...5 as 
we could notice, not followed by countermeasures). We still cannot 
understand why this takes place, but, however, we were able to solve our 
main problem.

For your interest:

(Sony VAIO series)
Intel PRO Wireless 2200bg Network Adapter driver v.9.0.3.0 (10/26/2005)

(IBM T series)
AMBIT Microsystems 802.11bg NIC Driver v. 4.1.102.1095

APs:

D-Link DWL-2100AP
Firmware v2.10eu release 0338


Thanks again for your bright and simple suggestion. We never knew Intel 
or IBM could produce buggy NICs, but it seems like they aren't angels, too.

Cheers!

Joshua Wright wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Arseniy Chernov wrote:
> 
>>I'm spending second week already trying to understand how should the 
>>trace of source of MIC error in a buggy RF environment be performed, 
>>hope to receive some advices here...
> 
> 
> It's interesting that you would ever see a Michael error.  The design of
> TKIP has a few different security features that would make it difficult
> for someone to craft a frame that would report an invalid Michael hash.
>  Specifically, I believe the TKIP RX handling process works as follows:
> 
> 1. Receive frame, examine sequence number.  If sequence number is too
> small, drop frame (mitigating replay attacks).
> 2. Implement key mixing function to decrypt the MPDU and check the ICV.
>  If the ICV is invalid, drop the frame.
> 3. Reassemble all MPDU's into the MSDU and calculate Michael hash over
> the contents.  If Michael hash is invalid, record and take
> countermeasures if necessary.
> 
> I see a few different possibilities where you would be experiencing
> Michael errors:
> 
> 1. An adversary is maliciously injecting malformed frames to DoS your
> network by triggering Michael countermeasures.  This isn't likely, as
> the attacker has to overcome the rules of sequence enforcement and
> maintaining the integrity of the ICV in order to make this happen.
> 2. Faulty AP implementation - if your AP isn't following the correct
> order of steps to decrypt and verify the contents of an MSDU (e.g. they
> are checking the Michael hash before they check the ICV), then a corrupt
> frame could cause this condition.
> 3. Faulty client implementation - If your client has a software flaw, it
> is possible that they aren't recording the Michael hash properly, or are
> not calculating the Michael hash over the correct fields.  I'd imagine
> this is the most likely case here - what client software and card are
> you using for your station?
> 
> Thanks for sharing these details.
> 
> - -Josh
> - --
> - -Joshua Wright
> jwright at hasborg.com
> 
> 2005-2006 pgpkey: http://802.11ninja.net/pgpkey.htm
> fingerprint: F00E 7A42 8375 0C55 964F E5A4 4D2F 22F6 3658 A4BF
> 
> Today I stumbled across the world's largest hotspot.  The SSID is "linksys".
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> 
> iD8DBQFDfchlTS8i9jZYpL8RAr1yAJ49LzjNVNjciLFaYuzK8rTBLU5+twCeNPTc
> hbPUkaydwB2weoCEIOvafiw=
> =8ECs
> -----END PGP SIGNATURE-----

-- 
Regards,
Arseniy Chernov
e-mail: ars at itconnection.ru
phone: +7 812 320-9850




From jers  Wed Nov 30 06:43:10 2005
From: jers (Jers)
Date: Wed, 30 Nov 2005 15:43:10 +0100
Subject: status of prism54-wpa for hostapd
Message-ID: <438C6E4E00085FCD@ms001msg.mail.fw> (added by
	postmaster@fastwebnet.it)

Hi Tobias,
 
I?m trying the WPA-PSK Access point throughout prism54 and hostapd and I had
same problems. When you run ifconfig
you should have both eth2 and eth2ap interfaces. In this case you have to
do:
 
Ifconfig eth2ap up
 
in order to run hostapd. 
 
Doing that, hostapd seems to work fine. Moreover, stations detect the AP
protected with WPA.
Unfortunately I can?t get the connection between clients and AP. Seems that
the AP does not listen to the connection requests.
 
If you try to test WPA with prism54, please let me know if it works!
 
Thanks.
Jers
 
 
 
 
>Hello,
>I am using the current snapshot from the prism54 drivers (not the kernel
one).
>Running hostapd without WPA works without problems.
> 
>The Problem:
>hostapd with WPA (wpa=1) exits with an errormessage.
> 
>The command:
>$ hostapd hostapd.conf
>Configuration file: hostapd.conf
>Using interface eth2 with hwaddr 00:01:36:0d:c2:ea and ssid 'test'
>Could not set PrivacyInvoked for interface eth2
>WPA initialization failed.
>rmdir[ctrl_interface]: No such file or directory
>Could not disable PrivacyInvoked for interface eth2
>$ dmesg|tail -n 3
>ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.
>ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.
>ap_net_ioctl: Ioctls for AP devices are NOT supported in this driver.
> 
> 
>Are there any activities for hostapd with wpa for prism54 cards?
>Is there any chance to get this running or should kick away the prism54
>card and buy an atheros card?
 
 

 


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.10/188 - Release Date: 29/11/2005
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051130/c237c425/attachment.htm 


From proski  Wed Nov 30 07:08:36 2005
From: proski (Pavel Roskin)
Date: Wed, 30 Nov 2005 10:08:36 -0500
Subject: Problems connecting to "ANY" ap...
In-Reply-To: <f59e60020511300330k54d87d22i@mail.gmail.com>
References: <f59e60020511300330k54d87d22i@mail.gmail.com>
Message-ID: <1133363316.16360.9.camel@dv>

On Wed, 2005-11-30 at 12:30 +0100, Klaas De Craemer wrote:
> Also things like 'iwlist wlan0 scanning' gives:
> wlan0     Interface doesn't support scanning : Network is down

Run this:
ifconfig wlan0 up

> What is going on? I don't seem to have this with the wlan_ng drivers.

linux-wlan-ng comes with scripts that may bring the interface up
automatically.

-- 
Regards,
Pavel Roskin




From klaasdc  Wed Nov 30 07:54:40 2005
From: klaasdc (Klaas De Craemer)
Date: Wed, 30 Nov 2005 16:54:40 +0100
Subject: Problems connecting to "ANY" ap...
In-Reply-To: <1133363316.16360.9.camel@dv>
References: <f59e60020511300330k54d87d22i@mail.gmail.com>
	<1133363316.16360.9.camel@dv>
Message-ID: <f59e60020511300754k3109709fn@mail.gmail.com>

I just found it in the Readme :) I must have read over it...
Anyway, thank you very much for helping!

Regards,
Klaas

2005/11/30, Pavel Roskin <proski at gnu.org>:
> On Wed, 2005-11-30 at 12:30 +0100, Klaas De Craemer wrote:
> > Also things like 'iwlist wlan0 scanning' gives:
> > wlan0     Interface doesn't support scanning : Network is down
>
> Run this:
> ifconfig wlan0 up
>
> > What is going on? I don't seem to have this with the wlan_ng drivers.
>
> linux-wlan-ng comes with scripts that may bring the interface up
> automatically.
>
> --
> Regards,
> Pavel Roskin
>
>



From andreaf  Wed Nov 30 13:17:08 2005
From: andreaf (Andrea G Forte)
Date: Wed, 30 Nov 2005 16:17:08 -0500
Subject: wpa-psk and hostap problem.
In-Reply-To: <20051130042502.GF8948@jm.kir.nu>
References: <438CD613.90606@cs.columbia.edu> <20051130042502.GF8948@jm.kir.nu>
Message-ID: <438E16D4.4080305@cs.columbia.edu>

Yes, the problem and the solution are both what you suggested. Thank you.
One more thing. Is there a reason why unencrypted data frames are 
dropped? Also, can you suggest any official documentation about WPA?

Thanks a lot,
Andrea


Jouni Malinen wrote:

>On Tue, Nov 29, 2005 at 05:28:35PM -0500, Andrea G Forte wrote:
>
>  
>
>>I was conducting some experiments with a Netgear AP, and two linux 
>>laptops (kernel 2.4). On one of the laptops I used hostap 0.3.9 and 
>>wpa_supplicant 0.4.7 and on the other laptop I used hostap-driver0.3.9 
>>without any supplicant. On the AP I enabled WPA-PSK. Now, according to 
>>the standard, a client should first associate to the AP and then perform 
>>authentication.
>>    
>>
>
>Also according to the standard, the AP that is configured to use WPA
>must reject association if the client does not use WPA..
>
>  
>
>>However, the problem is that now the laptop on which I do *not* run the 
>>supplicant it even fails associating to the AP. I always get association 
>>failed (Linkstatus = 6). Is this a problem related to the Netgear AP 
>>that does not follow the standard or is it a problem with the hostap 
>>driver?
>>    
>>
>
>I have hard time trying to understand this explanation.. Could you
>please explain what you were expecting to see and what you think is
>incorrect behavior? If I understood this setup correctly, you have AP
>configured to use WPA and the client (the one not running
>wpa_supplicant) configured not to use WPA. Did I understand that
>correctly? If yes, the expected behavior is that the client does not
>complete association with this AP and that seems to be exactly what is
>happening here..
>
>  
>




From jkmaline  Wed Nov 30 18:50:54 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 30 Nov 2005 18:50:54 -0800
Subject: wpa-psk and hostap problem.
In-Reply-To: <438E16D4.4080305@cs.columbia.edu>
References: <438CD613.90606@cs.columbia.edu> <20051130042502.GF8948@jm.kir.nu>
	<438E16D4.4080305@cs.columbia.edu>
Message-ID: <20051201025054.GB9038@jm.kir.nu>

On Wed, Nov 30, 2005 at 04:17:08PM -0500, Andrea G Forte wrote:
> Yes, the problem and the solution are both what you suggested. Thank you.
> One more thing. Is there a reason why unencrypted data frames are 
> dropped?

Please be more specific. I was just about to answer "security", but I'm
not sure what you are asking.

> Also, can you suggest any official documentation about WPA?

Wi-Fi Alliance has the "WPA Specification Documentation" for sale at
http://www.wi-fi.org/OpenSection/protected_access_archive.asp. That's
probably the closest thing to "official documentation" for WPA.

-- 
Jouni Malinen                                            PGP id EFC895FA



From support8  Wed Nov 30 09:03:33 2005
From: support8 (Eliot, Wireless and Server Administrator,
	Great Lakes Internet)
Date: Wed, 30 Nov 2005 12:03:33 -0500
Subject: RADIUS + EAP AVP Structure
Message-ID: <0633E0EDB4F25F43A2D7179CA11FAFAB04B574@xavier.staff.greatlakes.net>


Thanks for the reply.

I'll try the packet capture suggestions.

The MSDN site information I have gone over probably 15 times now. There just isn't anything useful in there. I did go to the RFC specified in the documentation and looked up the format of the packets. That is what I posted in my first post. But it still does not seem to work. So, I must be doing something wrong. 

Unfortunately, my company only employs about 11 people. I am the most knowledgeable about all this stuff and usually I'm the one everyone comes to for answers. But you say that Microsoft has a development support option available? Would that be standard (as in free) through our MSDN subscription? 

Eliot Gable
Certified Wireless Network Administrator
Cisco Certified Network Associate
CompTIA Security+ Certified
CompTIA Network+ Certified
Network and Systems Administrator
Great Lakes Internet, Inc.
112 North Howard
Croswell, MI 48422
810-679-3395



-----Original Message-----
From: Bryan Kadzban [mailto:bryan at kadzban.is-a-geek.net]
Sent: Tue 11/29/2005 9:25 PM
To: Eliot, Wireless and Server Administrator, Great Lakes Internet
Cc: hostap at shmoo.com
Subject: Re: RADIUS + EAP AVP Structure
 
Eliot wrote:
> When an EAP attribute (79) is specified in a RADIUS Access-Challenge,
> what is the structure of the value?

Take a look at a network capture (either Ethereal or MS Network Monitor)
-- that might give some useful information.

In particular, you should note that EAP data sent by the supplicant gets
repackaged into RADIUS attributes by the AP.  And since the length of a
RADIUS attribute is given (in the packet at least) by a single byte, the
maximum length is 255 -- so if the EAP data is longer than 255 bytes,
it'll take up more than one RADIUS attribute.

I'm not sure how each attribute's data is represented, although I would
guess that Ethereal's RADIUS dissector knows.  Perhaps it even knows
well enough to give you the original EAPOL frame.

> Also, if I test the RADIUS attributes, there are two types that 
> interest me. One type is what FreeRADIUS terms "EAP-Message" and that
> is type ID 79.

IIRC, that's the one that contains each piece of the EAP data.  Many of
these can exist in a single RADIUS request (up to the maximum size of a
RADIUS packet, minus any other attributes that have been included).
Microsoft's IAS extension API doesn't have a name for that one, but it's
the one you should be looking for if you're doing EAP from wireless clients.

> The other type is what Microsoft calls ratEAPTLV, which I'm not 
> certain what the number is for that one.

According to:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ias/ias/radius_attribute_type.asp

the number is 272.  It also says "see the IETF draft for EAP-TLV"
(and gives a 404 link), which I would presume contains part of the EAP
packet's format.  Although I don't know why it doesn't use 79...  maybe
because it's nonstandard?  Many of the other 2xx attributes on that page
seem to be extension attributes; maybe this one is similar.

Maybe you should see if there's anything else helpful in that IAS
extension DLL reference section of MSDN.  Failing that, see if perhaps
your company has a contact with Microsoft who might know who to ask
about stuff like this (like my company did with cert services, when we
had questions about autoenrollment) -- or possibly use a development
support call.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051130/4b2804d3/attachment.htm 


