From rcsorensen  Sun May  1 23:05:32 2005
From: rcsorensen (Ryan Sorensen)
Date: Sun, 1 May 2005 23:05:32 -0700
Subject: TinyPEAP and wpa_supplicant
Message-ID: <cb651cdf0505012305211cf4f9@mail.gmail.com>

Just in case anyone is trying to do TinyPEAP and wpa_supplicant, the
configuration on the tinyPEAP website needs to be amended to this:

phase1="include_tls_length=1 peaplabel=0"

instead of

phase1="peaplabel=0"


I still haven't figured out how to get the certificate in the right
format, but that'll come later.

-rcs



From ramalhais  Mon May  2 09:55:17 2005
From: ramalhais (Pedro Ramalhais)
Date: Mon, 02 May 2005 17:55:17 +0100
Subject: wpa_supplicant, ipw2200, association timeouts and other
	allegations
In-Reply-To: <42719A3D.3050207@gmail.com>
References: <42719A3D.3050207@gmail.com>
Message-ID: <1115052915.6421.254.camel@gandalf.uninova.pt>

On Fri, 2005-04-29 at 03:21, Petros Kolyvas wrote:
> Hi! This is my first post to the list. It was suggested I try my luck 
> here by some kind folks at #ipw2200 and #wireless on freenode.
> 
> My problems involve wpa_supplicant and my inability to get it to 
> associate with my access point. The hardware involved is an Intel 
> Pro/Wireless 2200BG (on a dell inspiron 700m) and a D-Link 2100AP 
> (currently running with WPA-PSK using CCMP/AES encryption). The setup 
> works fine under *cough* that other OS. I would like to be completely 
> free of it though.
> 
> The laptop is currently running FC3 and today I compiled and installed 
> 2.6.11.7 with the appropriate modules and options successfully. I'm also 
> using wpa_supplicant 0.4.0 and the latest (1.0.3 at the time of posting) 
> ipw2200 drivers. The wireless card will associate correctly with any 
> open networks, so at least that much is functioning.
> 
> "iwlist eth1 scanning" outputs:
> 
> #start
> Scan completed :
>       Cell 01 - Address: 00:11:95:BF:A6:4F
>                 ESSID:"ShiftFocus"
>                 Protocol:IEEE 802.11bg
>                 Mode:Master
>                 Channel:3
>                 Encryption key:on
>                 Bit Rate:54 Mb/s
>                 Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
>                 Quality=93/100  Signal level=-34 dBm
>             Extra:wpa_ie=dd160050f20101000050f20401000050f20401000050f202
>                 Extra: Last beacon: 22ms ago
> #end
> 
> 
> My wpa_supplicant.conf reads:
> 
> #start
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> 
> network={
> 	ssid="ShiftFocus"
> 	scan_ssid=1
> 	key_mgmt=WPA-PSK
> 	psk="secret-or-so-i-hope"
> }
> #end
...
> 
> Thanks so much!
> Petros K.

The problem is ipw2200 doesn't yet support hidden SSID.
The solution is to search for a patch for ipw2200 or wpa_supplicant on
the ipw2100-devel mailing list or set the essid manually(iwconfig eth1
essid ShiftFocus) while running wpa_supplicant.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From masala  Mon May  2 13:13:24 2005
From: masala (=?ISO-8859-1?Q?Christian_B=FCnnig?=)
Date: Mon, 02 May 2005 22:13:24 +0200
Subject: Using monitor mode
In-Reply-To: <200504291754.j3THsfN7014925@luna.tlmat.unican.es>
References: <200504291754.j3THsfN7014925@luna.tlmat.unican.es>
Message-ID: <427689E4.1010506@web.de>

No idea what's the reason for ethereal's behaviour, but have a try with 
'kismet'! It generally sniffs all packets and is able to store them in a 
libpcap file you can later open with ethereal to inspect it.
It further gives you some infos on seen nodes and networks.

christian

Johnny Choque wrote:
> Hi all,
> 
> I have two laptop which are set to ad-hoc mode and ping from one laptop to
> another. Also, I have a third laptop which is set to monitor mode in order
> to sniff all traffic between laptops in ad-hoc mode. My problem is that
> running ethereal in the third laptop not capture data traffic (ping packets)
> and only capture 802.11 management frames. I had tried to use monitor mode 2
> and 3 but the problem is the same.
> 
> Please, someone tell me how should configure my laptops in order to capture
> simultaneously both data packets and 802.11 management frames?
> 
> Thanks in advance,
> 
> Johnny
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From randall  Mon May  2 13:20:47 2005
From: randall (Randall Ross)
Date: Mon, 02 May 2005 13:20:47 -0700
Subject: No messages when card inserted (FC3, 2.6.10)
Message-ID: <42768B9F.6040001@tech-executive.com>

My system is Fedora Core 3 with (my own) kernel 2.6.10. I'm trying to 
use hostap-driver-0.3.7, (*have also tried 0.4.0 with same results.)

I successfully ran 'make' and 'make install'. No error messages.

Upon insertion of my  Netgear MA401 PC card, I get *no messages at all* 
in /var/log/messages.

This card has been verified to work in this machine with FC3, and kernel 
2.6.10. In fact I had been using it previously and recently. I suspect 
that this recent failure might have something to do with SELinux, as 
I've recently turned on that feature in my kernel, however I cannot say 
for sure if that is the cause. I have another PC wifi card (Buffalo) 
that uses Linuxant drivers, and functions normally. I also have a USB 
wifi dongle (D-link) that uses wlan-ng drivers and also functions normally.)

Can someone shed some light on how I could debug what's happening? What 
should I look for?

Thanks in advance.



From nll  Tue May  3 06:10:45 2005
From: nll (Nicolas Labrosse)
Date: Tue, 03 May 2005 14:10:45 +0100
Subject: Problem with WPA-PSK
Message-ID: <42777855.2050005@aber.ac.uk>

Hi everyone,
I've tried to sort this out on the gentoo forum but without success.
I want to use Wifi on my laptop and I use wpa_supplicant with atheros card AR5212. It works if I choose WEP encryption but I can't get it to work if I choose WPA-PSK.
I use wpa_supplicant v0.3.8, madwifi-driver-0.1_pre20050224, and madwifi-tools-0.1_pre20050106 from portage
System: Linux laptop 2.6.11-gentoo-r6 #5 SMP Tue Apr 26 23:29:55 BST 2005 i686 Mobile Intel(R) Pentium(R) 4     CPU 3.06GHz GenuineIntel GNU/Linux

Here is the output of running 'wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi -dd'
***
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'madwifi'
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
Line: 187 - start of a new network block
ssid - hexdump_ascii(len=10):
     obscured                     my_ssid
PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='my_ssid'
Initializing interface (2) 'ath0'
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:02:8a:b8:15:1e
wpa_driver_madwifi_set_wpa: enabled=1
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_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Wireless event: cmd=0x8b19 len=12
Received 459 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
0: 00:05:b4:07:e9:91 ssid='my_ssid' wpa_ie_len=26 rsn_ie_len=0
   selected
Trying to associate with 00:05:b4:07:e9:91 (SSID='my_ssid' freq=2437 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
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): obscured
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:05:b4:07:e9:91
Association event - clear replay counter
Associated to a new BSS: BSSID=00:05:b4:07:e9:91
No keys have been configured - skip key clearing
Associated with 00:05:b4:07:e9:91
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 'ath0' added
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
RX EAPOL from 00:05:b4:07:e9:8e
RX EAPOL - hexdump(len=99): obscured
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): obscured
WPA: RX message 1 of 4-Way Handshake from 00:05:b4:07:e9:8e (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): obscured
WPA: Renewed SNonce - hexdump(len=32): obscured
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): obscured
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): obscured
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:05:b4:07:e9:8e
RX EAPOL - hexdump(len=99): obscured
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): obscured
WPA: RX message 1 of 4-Way Handshake from 00:05:b4:07:e9:8e (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): obscured
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): obscured
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): obscured
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20 idleWhile=50
Signal 2 received - terminating
wpa_driver_madwifi_deauthenticate
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_madwifi_set_wpa: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
***
it stops when I hit ctrl-C, otherwise it goes on and on...

My config file is:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
        ssid="my_ssid"
        psk="my psk phrase"
}

Nothing too fancy in the network block. Should I change anything? 
When I use WEP, the network block is as follows
network={
        ssid="my_ssid"
        key_mgmt=NONE
        wep_key0=mywepkey
}

Any help appreciated!

Thanks a lot,

Nicolas




From Tilman.Schoop  Tue May  3 06:08:11 2005
From: Tilman.Schoop (Tilman Schoop)
Date: Tue, 03 May 2005 15:08:11 +0200
Subject: WPA with Cisco PCMCIA card?
Message-ID: <427777BB.3030608@dsa-ac.de>

Hi all,

I would like to know if there is a possibility to setup eap/tls and tkip
with wpa_supplicant and a Cisco 350 PCMCIA WLAN card.

I have seen that my card does not fall into one of the categories of
supported drivers for wpa_supplicant, but from Jean Tourilhes howto
website I have learned that the Cisco driver 2.1 can do AES(host) and
MIC. Is there a possibility to use this driver with wpa_supplicant?
Has anybody already configured this setup? Or am I misunderstanding
something?

Thanks

Tilman




From martin.p.bradley  Tue May  3 08:14:14 2005
From: martin.p.bradley (martin.p.bradley at bt.com)
Date: Tue, 3 May 2005 16:14:14 +0100
Subject: How to use eapol_test 
Message-ID: <3046C179E69FC24AB83536978A17614D014E1270@i2km96-ukbr.domain1.systemhost.net>

Folks,

I have got eapol_test compiled thanks to Jouni but I don't know how to
use it.  Could someone tell me where the documentation is or how to use
it.

I have searched www.google.com for eapol_test and my last message came
as the first hit.  This was a first for me :-)

Thanks for any help.
Martin.




On Wed, Apr 06, 2005 at 09:44:10AM +0100, martin.p.bradley at bt.com
wrote:

> Yes it looks like I'm using the wrong openssl library.  How can I
select
> the on that's installed in the directory /usr/local/openssl-0.9.7b/.
> Does the line below do what I need?  Probably not but that was what I
> tried...
> 
> export LDFLAGS=-L/usr/local/openssl-0.9.7b/

I use following lines in .config to select another openssl version:

CFLAGS += -I/home/jm/openssl/include
LIBS += -L/home/jm/openssl/lib

> eapol_test includes a file called radius.h.   I guessed that this was
> the radius.h but it looks like its not the correct one.

Unfortunately, radius.h was not being included in wpa_supplicant
tarballs. You can get it from my CVS repository, though. The easiest way
of compiling eapol_test would thus be to either use CVS pserver (see
http://hostap.epitest.fi/cvs.html) or download a CVS snapshot from
development branch
(http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/hostap/hostap.tar.gz?tarba
ll=1).
In the CVS tree, files are in bit different directories, but you can go
to wpa_supplicant directory, copy your .config file there (with the
openssl paths added as shown above) and just run 'make eapol_test'.

-- 
Jouni Malinen



From proski  Tue May  3 14:50:43 2005
From: proski (Pavel Roskin)
Date: Tue, 03 May 2005 17:50:43 -0400
Subject: [PATCH] Warning fix for 64-bit platforms
Message-ID: <1115157043.11663.14.camel@dv.roinet.com>

Hello!

The patch fixes following warning seen on 64-bit platforms (in my case -
x86_64, gcc-4.0):

In file included from /usr/local/src/hostap/driver/modules/hostap_cs.c:203:
/usr/local/src/hostap/driver/modules/hostap_hw.c: In function ?prism2_transmit_cb?:
/usr/local/src/hostap/driver/modules/hostap_hw.c:1674: warning: cast from pointer to integer of different size
/usr/local/src/hostap/driver/modules/hostap_hw.c: In function ?prism2_transmit?:
/usr/local/src/hostap/driver/modules/hostap_hw.c:1758: warning: cast to pointer from integer of different size

prism2_transmit_cb uses a (void *) argument to get an integer.   A
simple fix would be to use double cast from pointer to long and then to
int (and vice versa when int is passed as a pointer).  But I prefer a
slightly longer patch.

I believe that whenever an argument can hold both a pointer and an
integer, it should be declared long.  long can hold both pointers and
integers (except win64, but we are not coding for Windows), it can be
cast to both of them and it's never assumed to be a valid pointer, which
could be useful for some automatic code checkers.

Signed-off-by: Pavel Roskin <proski at gnu.org>

--- driver/modules/hostap_hw.c
+++ driver/modules/hostap_hw.c
@@ -510,9 +510,9 @@ static int hfa384x_cmd(struct net_device
  */
 static int hfa384x_cmd_callback(struct net_device *dev, u16 cmd, u16 param0,
 				void (*callback)(struct net_device *dev,
-						 void *context, u16 resp0,
+						 long context, u16 resp0,
 						 u16 status),
-				void *context)
+				long context)
 {
 	struct hostap_interface *iface = dev->priv;
 	local_info_t *local = iface->local;
@@ -1666,7 +1666,7 @@ static int prism2_get_txfid_idx(local_in
 
 
 /* Called only from hardware IRQ */
-static void prism2_transmit_cb(struct net_device *dev, void *context,
+static void prism2_transmit_cb(struct net_device *dev, long context,
 			       u16 resp0, u16 res)
 {
 	struct hostap_interface *iface = dev->priv;
@@ -1755,7 +1755,7 @@ static int prism2_transmit(struct net_de
 		dev,
 		HFA384X_CMDCODE_TRANSMIT | HFA384X_CMD_TX_RECLAIM,
 		local->txfid[idx],
-		prism2_transmit_cb, (void *) idx);
+		prism2_transmit_cb, (long) idx);
 
 	if (res) {
 		struct net_device_stats *stats;
@@ -1895,7 +1895,7 @@ static int prism2_tx_80211(struct sk_buf
 		/* Any RX packet seems to break something with TX bus
 		 * mastering; enable command is enough to fix this.. */
 		if (hfa384x_cmd_callback(dev, HFA384X_CMDCODE_ENABLE, 0,
-					 prism2_tx_cb, (void *) buf_len)) {
+					 prism2_tx_cb, (long) buf_len)) {
 			printk(KERN_DEBUG "%s: TX: enable port0 failed\n",
 			       dev->name);
 		}
@@ -2634,7 +2634,7 @@ static void prism2_infdrop(struct net_de
 	 * get out of this state by inquiring CommTallies. */
 	if (!last_inquire || time_after(jiffies, last_inquire + HZ)) {
 		hfa384x_cmd_callback(dev, HFA384X_CMDCODE_INQUIRE,
-				     HFA384X_INFO_COMMTALLIES, NULL, NULL);
+				     HFA384X_INFO_COMMTALLIES, NULL, 0);
 		last_inquire = jiffies;
 	}
 }
@@ -2986,7 +2986,7 @@ static void hostap_passive_scan(unsigned
 
 	if (hfa384x_cmd_callback(dev, HFA384X_CMDCODE_TEST |
 				 (HFA384X_TEST_CHANGE_CHANNEL << 8),
-				 channel, NULL, NULL))
+				 channel, NULL, 0))
 		printk(KERN_ERR "%s: passive scan channel set %d "
 		       "failed\n", dev->name, channel);
 
@@ -3023,7 +3023,7 @@ static void hostap_tick_timer(unsigned l
 	    !local->hw_downloading && local->hw_ready &&
 	    !local->hw_resetting && local->dev_enabled) {
 		hfa384x_cmd_callback(local->dev, HFA384X_CMDCODE_INQUIRE,
-				     HFA384X_INFO_COMMTALLIES, NULL, NULL);
+				     HFA384X_INFO_COMMTALLIES, NULL, 0);
 		last_inquire = jiffies;
 	}
 
--- driver/modules/hostap_wlan.h
+++ driver/modules/hostap_wlan.h
@@ -548,9 +548,9 @@
 	struct list_head list;
 	wait_queue_head_t compl;
 	volatile enum { CMD_SLEEP, CMD_CALLBACK, CMD_COMPLETED } type;
-	void (*callback)(struct net_device *dev, void *context, u16 resp0,
+	void (*callback)(struct net_device *dev, long context, u16 resp0,
 			 u16 res);
-	void *context;
+	long context;
 	u16 cmd, param0, param1;
 	u16 resp0, res;
 	volatile int issued, issuing;


-- 
Regards,
Pavel Roskin




From espy  Tue May  3 16:29:02 2005
From: espy (Tony Espy)
Date: Tue, 03 May 2005 19:29:02 -0400
Subject: HostAP, iwconfig power and SIOCSIWPOWER
Message-ID: <4278093E.5000801@pepper.com>

I have two questions regarding HostAP and SIOCSIWPOWER/iwconfig power.

1. Since the Prism firmware has default settings for MaxSleepDuration 
and HolderoverDuration ( ie. timeout ), is there anyway to enable power 
save without setting a value for one these two parameters?  From looking 
at the source in hostap_ioctl.c, it doesn't appear so...

2. Why does the HostAP prism2_ioctl_siwpower() method divide the given 
sleep and timeout values by 1024?  Shouldn't this be 1,000?
I took a peek at the WirelessTools iwconfig code and it multiplies the 
PS parameters by the constant MEGA ( == 1e6 ) if no specifier suffix is 
supplied.

Tony Espy
Pepper Computer, Inc.




From rocci  Tue May  3 16:29:42 2005
From: rocci (Rocci)
Date: Wed, 04 May 2005 09:29:42 +1000
Subject: Problem with WPA-PSK
In-Reply-To: <42777855.2050005@aber.ac.uk>
References: <42777855.2050005@aber.ac.uk>
Message-ID: <42780966.8060302@rocknetworks.net.au>

Try including the following in your network block for your PSK network:
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP

This works for me using WPA-PSK with a DLink AP
Hope this helps you out.

- Rocci.

Nicolas Labrosse wrote:

>Hi everyone,
>I've tried to sort this out on the gentoo forum but without success.
>I want to use Wifi on my laptop and I use wpa_supplicant with atheros card AR5212. It works if I choose WEP encryption but I can't get it to work if I choose WPA-PSK.
>I use wpa_supplicant v0.3.8, madwifi-driver-0.1_pre20050224, and madwifi-tools-0.1_pre20050106 from portage
>System: Linux laptop 2.6.11-gentoo-r6 #5 SMP Tue Apr 26 23:29:55 BST 2005 i686 Mobile Intel(R) Pentium(R) 4     CPU 3.06GHz GenuineIntel GNU/Linux
>
>Here is the output of running 'wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi -dd'
>***
>Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'madwifi'
>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
>Line: 187 - start of a new network block
>ssid - hexdump_ascii(len=10):
>     obscured                     my_ssid
>PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
>PSK (from passphrase) - hexdump(len=32): [REMOVED]
>Priority group 0
>   id=0 ssid='my_ssid'
>Initializing interface (2) 'ath0'
>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:02:8a:b8:15:1e
>wpa_driver_madwifi_set_wpa: enabled=1
>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_set_countermeasures: enabled=0
>wpa_driver_madwifi_set_drop_unencrypted: enabled=1
>Setting scan request: 0 sec 100000 usec
>Wireless event: cmd=0x8b06 len=8
>RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
>RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
>Starting AP scan (broadcast SSID)
>Wireless event: cmd=0x8b1a len=12
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
>Wireless event: cmd=0x8b19 len=12
>Received 459 bytes of scan results (2 BSSes)
>Scan results: 2
>Selecting BSS from priority group 0
>0: 00:05:b4:07:e9:91 ssid='my_ssid' wpa_ie_len=26 rsn_ie_len=0
>   selected
>Trying to associate with 00:05:b4:07:e9:91 (SSID='my_ssid' freq=2437 MHz)
>Cancelling scan request
>Automatic auth_alg selection: 0x1
>WPA: using IEEE 802.11i/D3.0
>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): obscured
>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=23
>Wireless event: cmd=0x8b15 len=20
>Wireless event: new AP: 00:05:b4:07:e9:91
>Association event - clear replay counter
>Associated to a new BSS: BSSID=00:05:b4:07:e9:91
>No keys have been configured - skip key clearing
>Associated with 00:05:b4:07:e9:91
>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 'ath0' added
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
>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
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
>RX EAPOL from 00:05:b4:07:e9:8e
>RX EAPOL - hexdump(len=99): obscured
>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): obscured
>WPA: RX message 1 of 4-Way Handshake from 00:05:b4:07:e9:8e (ver=1)
>WPA: WPA IE for msg 2/4 - hexdump(len=24): obscured
>WPA: Renewed SNonce - hexdump(len=32): obscured
>WPA: PMK - hexdump(len=32): [REMOVED]
>WPA: PTK - hexdump(len=64): [REMOVED]
>WPA: EAPOL-Key MIC - hexdump(len=16): obscured
>WPA: Sending EAPOL-Key 2/4
>WPA: TX EAPOL-Key 2/4 - hexdump(len=137): obscured
>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:05:b4:07:e9:8e
>RX EAPOL - hexdump(len=99): obscured
>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): obscured
>WPA: RX message 1 of 4-Way Handshake from 00:05:b4:07:e9:8e (ver=1)
>WPA: WPA IE for msg 2/4 - hexdump(len=24): obscured
>WPA: PMK - hexdump(len=32): [REMOVED]
>WPA: PTK - hexdump(len=64): [REMOVED]
>WPA: EAPOL-Key MIC - hexdump(len=16): obscured
>WPA: Sending EAPOL-Key 2/4
>WPA: TX EAPOL-Key 2/4 - hexdump(len=137): obscured
>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20 idleWhile=50
>Signal 2 received - terminating
>wpa_driver_madwifi_deauthenticate
>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_madwifi_set_wpa: enabled=0
>wpa_driver_madwifi_set_drop_unencrypted: enabled=0
>wpa_driver_madwifi_set_countermeasures: enabled=0
>***
>it stops when I hit ctrl-C, otherwise it goes on and on...
>
>My config file is:
>ctrl_interface=/var/run/wpa_supplicant
>ctrl_interface_group=0
>eapol_version=1
>ap_scan=1
>network={
>        ssid="my_ssid"
>        psk="my psk phrase"
>}
>
>Nothing too fancy in the network block. Should I change anything? 
>When I use WEP, the network block is as follows
>network={
>        ssid="my_ssid"
>        key_mgmt=NONE
>        wep_key0=mywepkey
>}
>
>Any help appreciated!
>
>Thanks a lot,
>
>Nicolas
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>



From rocci  Tue May  3 16:44:17 2005
From: rocci (Rocci)
Date: Wed, 04 May 2005 09:44:17 +1000
Subject: wpa not working with server ca
Message-ID: <42780CD1.6000408@rocknetworks.net.au>

Hi there,
I once had this working on my university network but it no longer works.
I have since upgraded my kernel and other aspects of my OS.
Recompiled madwifi & wpa_supplicant on new linux kernel.
WPA-PSK works fine on my PSK network at home but I can no longer get 
this to work on my university network.
My wpa_supplicant config is as follows:
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="ACHERNAR-BG"
        scan_ssid=1
        key_mgmt=WPA-EAP
        eap=PEAP
        pairwise=CCMP TKIP
        group=CCMP TKIP
        identity="username"
        password="mypassword"
        ca_cert="/etc/cert/cert.cer"
        phase1="peapver=1 peaplabel=0"
        phase2="auth=MSCHAPV2"
        priority=1
}



The output from wpa_supplicant -d -i ath0 -c /etc/wpa_supplicant.conf is:

root at roklptop:~# wpa_supplicant -d -i ath0 -c /etc/wpa_supplicant.conf
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 
'default'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
eapol_version=2
ap_scan=1
Priority group 1
   id=0 ssid='ACHERNAR-BG'
Initializing interface (2) 'ath0'
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:0f:3d:87:17:c6
wpa_driver_madwifi_set_wpa: enabled=1
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_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=11):
     41 43 48 45 52 4e 41 52 2d 42 47                  ACHERNAR-BG
Wireless event: cmd=0x8b1a len=24
Wireless event: cmd=0x8b19 len=12
Received 963 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:11:93:24:a3:e0 ssid='ACHERNAR-BG' wpa_ie_len=26 rsn_ie_len=0
   selected
Trying to associate with 00:11:93:24:a3:e0 (SSID='ACHERNAR-BG' 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 8 key_mgmt 1
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT 802.1X
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 01
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 - portControl=Auto
Wireless event: cmd=0x8b1a len=24
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:11:93:24:a3:e0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:11:93:24:a3:e0
No keys have been configured - skip key clearing
Associated with 00:11:93:24:a3:e0
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
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 'ath0' added
RX EAPOL from 00:11:93:24:a3:e0
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
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
     "ASCII values of username"                               username
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:93:24:a3:e0
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=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
     "ASCII values of username"                               username
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:93:24:a3:e0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=17 id=180
EAP: EAP entering state GET_METHOD
EAP: Building EAP-Nak (requested type 17 not allowed)
EAP: allowed methods - hexdump(len=1): 19
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:93:24:a3:e0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=25 id=181
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (25, PEAP)
EAP-PEAP: Forced PEAP version 0
EAP-PEAP: Phase2 EAP types - hexdump(len=1): 1a
TLS: Trusted root certificate(s) loaded
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=6) - Flags 0x21
EAP-PEAP: Start (server ver=1, own ver=0)
EAP-PEAP: Using PEAP version 0
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
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
EAPOL: SUPP_BE entering state TIMEOUT
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:11:93:24:a3:e0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: deinitialize previously used EAP method (25, PEAP) at 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=182
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
     "ASCII values of username"                               username
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:93:24:a3:e0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=17 id=194
EAP: EAP entering state GET_METHOD
EAP: Building EAP-Nak (requested type 17 not allowed)
EAP: allowed methods - hexdump(len=1): 19
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:93:24:a3:e0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=25 id=195
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (25, PEAP)
EAP-PEAP: Forced PEAP version 0
EAP-PEAP: Phase2 EAP types - hexdump(len=1): 1a
TLS: Trusted root certificate(s) loaded
TLS - SSL error: error:0B07C065:x509 certificate 
routines:X509_STORE_add_cert:cert already in hash table
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=6) - Flags 0x21
EAP-PEAP: Start (server ver=1, own ver=0)
EAP-PEAP: Using PEAP version 0
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
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
Signal 2 received - terminating
wpa_driver_madwifi_deauthenticate
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_madwifi_set_wpa: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
EAP: deinitialize previously used EAP method (25, PEAP) at EAP deinit
...


The following lines concern me but I'm not sure what exactly they mean:
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
...
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
EAPOL: SUPP_BE entering state TIMEOUT
...

Any help or pointers would be greatly appreciated.
Thanks
Rocci.



From sime  Wed May  4 00:51:21 2005
From: sime (Simon Males)
Date: Wed, 04 May 2005 17:51:21 +1000
Subject: wpa not working with server ca
In-Reply-To: <42780CD1.6000408@rocknetworks.net.au>
References: <42780CD1.6000408@rocknetworks.net.au>
Message-ID: <42787EF9.9040509@anticd.org>


Rocci wrote:
> Hi there,
> I once had this working on my university network but it no longer works.
> I have since upgraded my kernel and other aspects of my OS.
> Recompiled madwifi & wpa_supplicant on new linux kernel.
> WPA-PSK works fine on my PSK network at home but I can no longer get 
> this to work on my university network.

Rocci,

	Bugger, I never got the chance to connect (been struggling since start 
of semester), its not looking good if even you cannot connect! I posted 
a -d output a little while ago, Jouni asked me to pump out -dd output. 
Jouni did recommend to add includes_tls_length=1 to phase1, although my 
conf is a little different.

Initial thread:
http://lists.shmoo.com/pipermail/hostap/2005-April/010030.html

I let it run for a little while and don't want to paste the whole output 
to the list.

http://anticd.org/~sime/wifi/wpa_error-dd.txt

wpa_supplicant.conf:
network={
        ssid="ACHERNAR-BG"
        key_mgmt=WPA-EAP
        eap=PEAP
        pairwise=TKIP
        group=TKIP
        identity="***"
        password="***"
        ca_cert="/home/sime/Downloads/wifi/thawte/ThawteServerCA.pem"
        phase1="peaplabel=0 includes_tls_length=1"
        phase2="auth=MSCHAPV2"
        priority=10
}


-- 
Simon Males <sime at anticd.org>
No More AOL CDs Australia - www.anticd.org



From jchoque  Wed May  4 00:58:02 2005
From: jchoque (Johnny Choque)
Date: Wed, 4 May 2005 09:58:02 +0200
Subject: Using monitor mode
In-Reply-To: <427689E4.1010506@web.de>
Message-ID: <200505040738.j447cuSV009149@luna.tlmat.unican.es>

Hi,

Thanks for your suggestion about kismet but I prefer to use ethereal because
I need to make several test in which I need to see the packets captured
while the sniffer tool is running.

I am using a Linksys Network PC Card v2.5 and I do not know if that wireless
card have problems with hostap in monitor mode or it is needed to use with
particular firmware version.

Please, any ideas?

Johnny

> No idea what's the reason for ethereal's behaviour, but have 
> a try with 'kismet'! It generally sniffs all packets and is 
> able to store them in a libpcap file you can later open with 
> ethereal to inspect it.
> It further gives you some infos on seen nodes and networks.
> 
> christian
> 
> Johnny Choque wrote:
> > Hi all,
> > 
> > I have two laptop which are set to ad-hoc mode and ping from one 
> > laptop to another. Also, I have a third laptop which is set 
> to monitor 
> > mode in order to sniff all traffic between laptops in 
> ad-hoc mode. My 
> > problem is that running ethereal in the third laptop not 
> capture data 
> > traffic (ping packets) and only capture 802.11 management frames. I 
> > had tried to use monitor mode 2 and 3 but the problem is the same.
> > 
> > Please, someone tell me how should configure my laptops in order to 
> > capture simultaneously both data packets and 802.11 
> management frames?
> > 
> > Thanks in advance,
> > 
> > Johnny
> > 
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap




From roby  Wed May  4 03:07:58 2005
From: roby (roby)
Date: Wed, 04 May 2005 12:07:58 +0200
Subject: Handover performance.
Message-ID: <20050504100758.5564.qmail@webmaildomini.aruba.it>


Hi, 

 I have build a small ESS with 2 access point hostapd based and an access 
server with freeradius. The system works with WPA and EAP-TLS 
authentication. 

A this time I'm testing the handover delay, for VoIP applications. The 
problem is that pre-authentication doesn't seem to work correctly.
I made some test, and the delay time is between 4 and 5 seconds. As you can 
understand it's a very long delay....
I set di Hostapd.conf for support IAPP and also RSN/WPA2 pre-authentication
but... 

Can somebody help me to set the pre-authentication? Did anybody make some 
similar test? All suggestions are wellcome! 

Thanks for your help,
Sincerly
Roby Arlati



From masala  Wed May  4 08:51:19 2005
From: masala (=?ISO-8859-1?Q?Christian_B=FCnnig?=)
Date: Wed, 04 May 2005 17:51:19 +0200
Subject: Using monitor mode
In-Reply-To: <200505040738.j447cuSV009149@luna.tlmat.unican.es>
References: <200505040738.j447cuSV009149@luna.tlmat.unican.es>
Message-ID: <4278EF77.6070205@web.de>

Johnny Choque wrote:
> Hi,
> 
> Thanks for your suggestion about kismet but I prefer to use ethereal because
> I need to make several test in which I need to see the packets captured
> while the sniffer tool is running.
> 
> I am using a Linksys Network PC Card v2.5 and I do not know if that wireless
> card have problems with hostap in monitor mode or it is needed to use with
> particular firmware version.

A too old firmware might be the problem. If you have a try with kismet 
and the problem is still there, then upgrading the firmware could solve 
it. At linux.junsun.net/intersil-prism is a good explanation on how to 
do this and where to get firmware files.

$ hostap_diag -p INTERFACE

tells you which firmware is currently used (sorry if I'm telling you old 
stuff ;) )

If the sniffing works with kismet then I guess it depends on how you set 
the card into monitor mode.

hopefully it helps you, but maybe someone has experienced similar 
problems and knows more about that.

Christian



From smitpe  Wed May  4 12:44:28 2005
From: smitpe (Pieter E Smit)
Date: Wed, 04 May 2005 21:44:28 +0200
Subject: wpa_supplicant + madwifi  <--Peap--- SenaoAP ---Peap--> freeradius
In-Reply-To: <20050504100937.5D79E1345E0@mail.iocaine.com>
References: <20050504100937.5D79E1345E0@mail.iocaine.com>
Message-ID: <4279261C.7030502@gmail.com>

Hi,

I am connecting with a madwifi (wpa_supplicant) to a senao AP with wpa
peap and freeradius server.
I can see the server and supplicant talking but am not sure if i am
authenticated.

Full Dump
http://www.vigor.co.za/linux/wpa_supplicant_20050504.txt
http://www.vigor.co.za/linux/freeradius_20050504.txt

wpa_supplicant
network={
	ssid="wireless_11g"	
	key_mgmt=WPA-EAP
	eap=PEAP
	pairwise=TKIP
	group=TKIP
	identity="user at vigor"
	password="foobar"
	#anonymous_identity="anonymous"
	#ca_cert="/etc/cert/ca.pem"
	#phase1="peaplabel=1 includes_tls_length=1" <<Does not change anything.	
	phase2="auth=MSCHAPV2"
	priority=2
}

#/usr/sbin/wpa_supplicant -w -dd -D madwifi -i ath0
...
...
EAP-PEAP: received Phase 2: code=1 identifier=98 length=11
EAP-PEAP: Phase 2 Request: type=33
EAP-TLV: Received TLVs - hexdump(len=6): 80 03 00 02 00 01
EAP-TLV: Result TLV - hexdump(len=2): 00 01
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): [REMOVED]
EAP: method process -> ignore=FALSE methodState=DONE decision=UNCOND_SUCC
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=98): 00 02 6f 22 a8 76 00 02 6f 20 55 80 88 8e 01
00 00 50 02 62 00 50 19 00 17 03 01 00 20 75 cf fc 43 4d 24 9e 20 b4 54
03 ac 98 ad e1 b7 bd f5 6f 28 d6 98 c3 5b 13 36 1f 1b 70 71 a3 92 17 03
01 00 20 25 7e 09 d8 4b 30 93 c8 ef 7c 1f 26 a9 44 d2 7a 6a 27 aa 6e 60
7c 48 b7 93 2b 5f 86 cc 79 d7 0f
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=8): 01 00 00 04 03 59 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP-Success Id mismatch - reqId=89 lastId=98
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE

And there it pauses for 30 seconds and it all starts over again with.

EAPOL: startWhen --> 0
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=9): 01 00 00 05 01 61 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=97
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE

Wait another 20 sec

EAPOL: authWhile --> 0
EAPOL: SUPP_BE entering state TIMEOUT
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
TX EAPOL - hexdump(len=18): 00 02 6f 22 a8 76 00 02 6f 20 55 80 88 8e 01
01 00 00
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=9): 01 00 00 05 01 61 00 05 01
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE

And it continues with tls peap etc.
Q1. The line "EAP: Received EAP-Success" does this mean i have been
authenticated ?
Q2. "EAP: EAP-Success Id mismatch - reqId=89 lastId=98" i see often, it
seems the ap is sending new requestes during the authentication. Is this
a problem ?
Q3. "How do I know if the AP and supplicant has exchanged keys ?

Regards,
Pieter Smit




From cngriffin  Wed May  4 19:30:59 2005
From: cngriffin (Charles Griffin)
Date: Wed, 4 May 2005 22:30:59 -0400
Subject: WPA-PSK only authenticates if essid is broadcast
Message-ID: <a3c9e8e90505041930c3ea868@mail.gmail.com>

Hello--

I am running Slackware 10.1 on a Dell 700m laptop which has the Dell
1450 dual band internal wireless (802.11a/b/g, 54 Mbps) integrated
card.  I use ndiswrapper v1.1 and the windows driver along with
wpa_supplicant 0.3.8 and it works great in connecting to my Apple
airport extreme base station set with wpa-psk encryption.  The only
problem is that wpa_supplicant will only find the router and
authenticate if I set the essid to broadcast.  If the essid is not
broadcast, wpa_supplicant says it cannot find any access point.

When I built wpa_supplicant, I used these options in my .config file:

CONFIG_DRIVER_NDISWRAPPER=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_EAP_PSK=y

My wpa_supplicant.conf file is:

network={
ssid="myessid"
scan_ssid=1
key_mgmt=WPA-PSK
psk="myencryptionkey"
}

I would really like to be able to turn off my essid broadcast.  Any
suggestions or help would be greatly appreciated.

TIA.



From roby  Thu May  5 01:01:32 2005
From: roby (roby)
Date: Thu, 05 May 2005 10:01:32 +0200
Subject: Handover performance.
In-Reply-To: <200505041334.20069.vda@ilport.com.ua>
References: <20050504100758.5564.qmail@webmaildomini.aruba.it>
	<200505041334.20069.vda@ilport.com.ua>
Message-ID: <20050505080133.22585.qmail@webmaildomini.aruba.it>

As you ask! I give  you  some more detail.... 

I need to know if it possible to use pre-authentication using WPA1. I need 
to reduce the handover delay.
DO the pre-authentication work only with RSN/WPA2? 

You can find here my hostapd.conf. It' s same on both APs. 

##### hostapd configuration file #########################################
# Empty lines and lines starting with # are ignored 

# AP netdevice name (without 'ap' prefix, i.e., wlan0 uses wlan0ap for
# management frames)
interface=wlan0 

# hostapd event logger configuration
#
# Two output method: syslog and stdout (only usable if not forking to
# background).
#
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
# bit 3 (8) = WPA
#
# Levels (minimum value for logged events):
#  0 = verbose debugging
#  1 = debugging
#  2 = informational messages
#  3 = notification
#  4 = warning
#
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2 

# Debugging: 0 = no, 1 = minimal, 2 = verbose, 3 = msg dumps, 4 = excessive
debug=0 

# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump 

# Daemonize hostapd process (i.e., fork to background)
daemonize=1 


##### IEEE 802.11 related configuration 
####################################### 

# SSID to be used in IEEE 802.11 management frames
ssid=accesspoint1 

# Station MAC address -based authentication
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0 

# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd.accept
#deny_mac_file=/etc/hostapd.deny 

# IEEE 802.11 specifies two authentication algorithms. hostapd can be
# configured to allow both of these or only one. Open system authentication
# should be used with IEEE 802.1X.
# Bit fields of allowed authentication algorithms:
# bit 0 = Open System Authentication
# bit 1 = Shared Key Authentication (requires WEP)
auth_algs=3 

# Associate as a station to another AP while still acting as an AP on the 
same
# channel.
#assoc_ap_addr=00:12:34:56:78:9a 


##### IEEE 802.1X (and IEEE 802.1aa/D4) related configuration 
################# 

# Require IEEE 802.1X authorization
ieee8021x=1 

# Use internal minimal EAP Authentication Server for testing IEEE 802.1X.
# This should only be used for testing since it authorizes all users that
# suppot IEEE 802.1X without any keys or certificates.
minimal_eap=0 

# Optional displayable message sent with EAP Request-Identity
eap_message=hello 

# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
#wep_key_len_broadcast=5
#wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300 

# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
eapol_key_index_workaround=1 


##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) 
####################### 

# Interface to be used for IAPP broadcast packets
iapp_interface=access 


##### RADIUS configuration 
####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting 

# The own IP address of the access point (used as NAS-IP-Address) 

own_ip_addr=192.168.1.2 

# Optional NAS-Identifier string for RADIUS messages. When used, this should 
be
# a unique to the NAS within the scope of the RADIUS server. For example, a
# fully qualified domain name can be used here.
#nas_identifier=ap.example.com 

# RADIUS authentication server
auth_server_addr=192.168.1.1
auth_server_port=1812
auth_server_shared_secret=testing123 

# RADIUS accounting server
acct_server_addr=192.168.1.1
acct_server_port=1813
acct_server_shared_secret=testing123 

# Secondary RADIUS servers; to be used if primary one does not reply to
# RADIUS packets. These are optional and there can be more than one 
secondary
# server listed.
#auth_server_addr=127.0.0.2
#auth_server_port=1812
#auth_server_shared_secret=secret2
#
#acct_server_addr=127.0.0.2
#acct_server_port=1813
#acct_server_shared_secret=secret2 

# Retry interval for trying to return to the primary RADIUS server (in
# seconds). RADIUS client code will automatically try to use the next server
# when the current server is not replying to requests. If this interval is 
set,
# primary server will be retried after configured amount of time even if the
# currently used secondary server is still working.
#radius_retry_primary_interval=600 


# Interim accounting update interval
# If this is set (larger than 0) and acct_server is configured, hostapd will
# send interim accounting updates every N seconds. Note: if set, this 
overrides
# possible Acct-Interim-Interval attribute in Access-Accept message. Thus, 
this
# value should not be configured in hostapd.conf, if RADIUS server is used 
to
# control the interim interval.
# This value should not be less 600 (10 minutes) and must not be less than
# 60 (1 minute).
#radius_acct_interim_interval=600 


##### WPA/IEEE 802.11i configuration ###################################### 

# Enable WPA. Setting this variable configures the AP to require WPA (either
# WPA-PSK or WPA-RADIUS/EAP based on other configuration). For WPA-PSK, 
either
# wpa_psk or wpa_passphrase must be set and wpa_key_mgmt must include 
WPA-PSK.
# For WPA-RADIUS/EAP, ieee8021x must be set (but without dynamic WEP keys),
# RADIUS authentication server must be configured, and WPA-EAP must be 
included
# in wpa_key_mgmt.
# This field is a bit field that can be used to enable WPA (IEEE 
802.11i/D3.0)
# and/or WPA2 (full IEEE 802.11i/RSN):
# bit0 = WPA
# bit1 = IEEE 802.11i/RSN (WPA2)
wpa=1 

# WPA pre-shared keys for WPA-PSK. This can be either entered as a 256-bit
# secret in hex format (64 hex digits), wpa_psk, or as an ASCII passphrase
# (8..63 characters) that will be converted to PSK. This conversion uses 
SSID
# so the PSK changed when ASCII passphrase is used and the SSID is changed.
#wpa_psk=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
#wpa_passphrase=secret passphrase 

# Set of accepted key management algorithms (WPA-PSK, WPA-EAP, or both). The
# entries are separated with a space.
wpa_key_mgmt=WPA-EAP 

# Set of accepted cipher suites (encryption algorithms) for pairwise keys
# (unicast packets). This is a space separated list of algorithms:
# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
# Group cipher suite (encryption algorithm for broadcast and multicast 
frames)
# is automatically selected based on this configuration. If only CCMP is
# allowed as the pairwise cipher, group cipher will also be CCMP. Otherwise,
# TKIP will be used as the group cipher.
wpa_pairwise=TKIP 

# Time interval for rekeying GTK (broadcast/multicast encryption keys) in
# seconds.
wpa_group_rekey=600 

# Time interval for rekeying GMK (master key used internally to generate 
GTKs
# (in seconds).
wpa_gmk_rekey=86400 

# Enable IEEE 802.11i/RSN/WPA2 pre-authentication. This is used to speed up
# roaming be pre-authenticating IEEE 802.1X/EAP part of the full RSN
# authentication and key handshake before actually associating with a new 
AP.
rsn_preauth=1
#
# Space separated list of interfaces from which pre-authentication frames 
are
# accepted (e.g., 'eth0' or 'eth0 wlan0wds0'. This list should include all
# interface that are used for connections to other APs. This could include
# wired interfaces and WDS links. The normal wireless data interface towards
# associated stations (e.g., wlan0) should not be added, since
# pre-authentication is only used with APs other than the currently 
associated
# one.
rsn_preauth_interfaces=eth0
######################################################################## 

Thanks for your help.
Roby A. 


Denis Vlasenko Scrive: 

> On Wednesday 04 May 2005 13:07, roby wrote:
>> 
>> Hi,  
>> 
>>  I have build a small ESS with 2 access point hostapd based and an access 
>> server with freeradius. The system works with WPA and EAP-TLS 
>> authentication.  
>> 
>> A this time I'm testing the handover delay, for VoIP applications. The 
>> problem is that pre-authentication doesn't seem to work correctly.
>> I made some test, and the delay time is between 4 and 5 seconds. As you can 
>> understand it's a very long delay....
>> I set di Hostapd.conf for support IAPP and also RSN/WPA2 pre-authentication
>> but...  
>> 
>> Can somebody help me to set the pre-authentication? Did anybody make some 
>> similar test? All suggestions are wellcome! 
> 
> I suggest posting more details.
> --
> vda 
> 
 




From mcgrof  Thu May  5 01:06:25 2005
From: mcgrof (Luis R. Rodriguez)
Date: Thu, 5 May 2005 04:06:25 -0400
Subject: PEAPv2 support
Message-ID: <20050505080625.GD13303@ruslug.rutgers.edu>


Jouni,

how far are we with PEAPv2 support in wpa_supplicant as per
draft-josefsson-pppext-eap-tls-eap-07.txt:

http://www.ee.oulu.fi/research/ouspg/frontier/sota/whitepaper-wots/specs/draft-josefsson-pppext-eap-tls-eap-07.txt

I have been trying to auth against IAS at work in a peap/mschapv2 setup
unsuccessfully. I'm wondering if it has something to do with peapv2.
I'll try again tomorrow and if unsuccessfull I'll send the logs.

Thanks,

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E
-------------- 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/20050505/f97ab883/attachment.pgp 


From st3v3  Thu May  5 04:48:38 2005
From: st3v3 (Steve)
Date: 05 May 2005 12:48:38 +0100
Subject: compiling hostapd without EAP, with 802.1x
Message-ID: <1115293718.3263.8.camel@localhost.localdomain>

Hi all
Ive found a problem with a code change made on Sun Apr 17 17:08:21 2005
to hostap/hostapd/ieee802_1x.c Line 838 of the current CVS
	if (sta->eapol_sm->eap)
			eap_sm_notify_cached(sta->eapol_sm->eap);

I build hostapd without the EAP component. The code change assumes that
the EAP module has been included with CONFIG_EAP in the .config. Which
cannot be guaranteed, espceially for my environment.
When building the code without EAP included in the build
	ieee802_1x.o: In function `ieee802_1x_new_station':
	ieee802_1x.o(.text+0x15b8): undefined reference to
	`eap_sm_notify_cached'
	collect2: ld returned 1 exit status
	make: *** [hostapd] Error 1

Unless including the EAP module, the eap.o will not be compiled.
As this line(ieee802_1x.c:838) is fairly new to this source code, I have
commented it out in my current CVS copy, so I can carry on building in
the same way without EAP.

I would suggest that a #ifdef CONFIG_EAP is required around this line???
Can this change be made to the CVS repository please.

Regards
	Steve


-- 
ENDOFMSG




From josh.howlett  Thu May  5 09:38:44 2005
From: josh.howlett (Josh Howlett)
Date: Thu, 05 May 2005 17:38:44 +0100
Subject: Testing wpa_supplicant on Windows
Message-ID: <E7CB2B504D3C62875D686B7C@cumulus>

I have the opportunity shortly to test wpa_supplicant on a large number of 
machines running a variety of Windows OSes at different patch levels. 
However, I want to make it as easy as possible for the testers to install.

I was wondering whether it were possible to remove the need for the WinPcap 
installation by compiling wpa_supplicant appropriately? I know nothing 
about development in a Windows environment, and would greatly appreciate 
any assistance...

best regards, josh.

-- 
-----------------------------------------------------------
Josh Howlett, Networking & Digital Communications,
Information Systems & Computing, University of Bristol, U.K.
'phone: 0117 928 7850 email: josh.howlett at bris.ac.uk
------------------------------------------------------------



From listmember  Thu May  5 09:45:39 2005
From: listmember (Tolunay Orkun)
Date: Thu, 05 May 2005 11:45:39 -0500
Subject: WPA-PSK only authenticates if essid is broadcast
In-Reply-To: <a3c9e8e90505041930c3ea868@mail.gmail.com>
References: <a3c9e8e90505041930c3ea868@mail.gmail.com>
Message-ID: <427A4DB3.7070608@orkun.us>

Charles,

I am in a similar situation. I have a Dell Latitude D600 with TrueMobile 
1400 card (Broadcom chipset - no native Linux driver).

The current working solution is to use ap_scan=2 and have your network 
entry as the first entry in the config file. This forces you to change 
the config file when you move to a different network. Less than ideal 
and I think it was basically a hack. It may work for stationary hosts 
but for roaming laptops this is great pain.

I think if wpa_supplicant could combine the results of AP scan as well 
as try connecting with the network entries that are market hidden in the 
config file this would not be an issue. When I have some time, I will 
try to patch wpa_supplicant to do this. I've asked in this list about it 
(with cc to Jouni) but got no response. Hopefully, we will get a 
response this time.

There is already a enhancement request in hostap bugzilla:
http://hostap.epitest.fi/bugz/show_bug.cgi?id=16

And here are my messages to HostAP and Ndiswrapper lists:

http://incognito.shmoo.com/pipermail/hostap/2005-April/010120.html
http://sourceforge.net/mailarchive/message.php?msg_id=11527596

Best regards,
Tolunay

Charles Griffin wrote:
> Hello--
> 
> I am running Slackware 10.1 on a Dell 700m laptop which has the Dell
> 1450 dual band internal wireless (802.11a/b/g, 54 Mbps) integrated
> card.  I use ndiswrapper v1.1 and the windows driver along with
> wpa_supplicant 0.3.8 and it works great in connecting to my Apple
> airport extreme base station set with wpa-psk encryption.  The only
> problem is that wpa_supplicant will only find the router and
> authenticate if I set the essid to broadcast.  If the essid is not
> broadcast, wpa_supplicant says it cannot find any access point.
> 
> When I built wpa_supplicant, I used these options in my .config file:
> 
> CONFIG_DRIVER_NDISWRAPPER=y
> CONFIG_WIRELESS_EXTENSION=y
> CONFIG_EAP_PSK=y
> 
> My wpa_supplicant.conf file is:
> 
> network={
> ssid="myessid"
> scan_ssid=1
> key_mgmt=WPA-PSK
> psk="myencryptionkey"
> }
> 
> I would really like to be able to turn off my essid broadcast.  Any
> suggestions or help would be greatly appreciated.
> 
> TIA.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From pkolyvas  Thu May  5 10:00:00 2005
From: pkolyvas (Petros Kolyvas)
Date: Thu, 05 May 2005 13:00:00 -0400
Subject: WPA-PSK only authenticates if essid is broadcast
In-Reply-To: <427A4DB3.7070608@orkun.us>
References: <a3c9e8e90505041930c3ea868@mail.gmail.com>
	<427A4DB3.7070608@orkun.us>
Message-ID: <BAYC1-PASMTP03B662CBC1736CE576DCEDD61A0@cez.ice>

> I think if wpa_supplicant could combine the results of AP scan as well 
> as try connecting with the network entries that are market hidden in the 
> config file this would not be an issue. When I have some time, I will 
> try to patch wpa_supplicant to do this. I've asked in this list about it 
> (with cc to Jouni) but got no response. Hopefully, we will get a 
> response this time.
> 

If wpa supplicant could somehow set the cards essid to the network it's 
trying to connect to before it makes an attempt, would be wonderful.

My ssid is hidden and I have to 'iwconfig eth1 essid ShiftFocus' before 
I attempt to associate with wpa_supplicant if I'm coming from another 
network or a reboot.

Pk
yoink@#ipw2200



From smitpe  Thu May  5 13:13:17 2005
From: smitpe (Pieter E Smit)
Date: Thu, 05 May 2005 22:13:17 +0200
Subject: wpa_supplicant - 4WAY_HANDSHAKE aborted
Message-ID: <427A7E5D.3090406@gmail.com>

Hi,
I am still struggling to get the following working
Laptop(madwifi+wpa_supplicant) <--> HostAP <--> freeradius

The supplicant tries to connect and has some tls problems but every now
and the the SSL works and the i get the following.  Any suggestions will
be welcome.
...
...
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): [REMOVED]
EAP: method process -> ignore=FALSE methodState=DONE decision=UNCOND_SUCC
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=98): 00 02 6f 22 a8 76 00 02 6f 20 55 80 88 8e 01
00 00 50 02 6d 00 50 19 00 17 03 01 00 20 81 ac d2 a9 05 be 8f 60 94 79
e6 68 5e f2 dc 4e 00 f6 cb fb b3 f5 21 a2 de 80 7d e5 0f e4 3d 0e 17 03
01 00 20 40 38 bf 69 f0 d6 24 13 32 6b 5f 81 1d 15 67 ec bf ba bc 7f c0
8a c2 5d 71 dc f1 af 43 73 12 42
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=8): 01 00 00 04 03 64 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP-Success Id mismatch - reqId=100 lastId=109
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 1e 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2 08 44 f7
22 59 73 b1 9d c5 0f db 3a c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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 1e 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2
08 44 f7 22 59 73 b1 9d c5 0f db 3a c1 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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:02:6f:22:a8:76 (ver=1)
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 1f 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2 08 44 f7
22 59 73 b1 9d c5 0f db 3a c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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 1f 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2
08 44 f7 22 59 73 b1 9d c5 0f db 3a c2 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:02:6f:22:a8:76 (ver=1)
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 20 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2 08 44 f7
22 59 73 b1 9d c5 0f db 3a c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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 20 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2
08 44 f7 22 59 73 b1 9d c5 0f db 3a c3 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:02:6f:22:a8:76 (ver=1)
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 21 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2 08 44 f7
22 59 73 b1 9d c5 0f db 3a c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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 21 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2
08 44 f7 22 59 73 b1 9d c5 0f db 3a c4 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:02:6f:22:a8:76 (ver=1)
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted
RX EAPOL from 00:02:6f:22:a8:76
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 22 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2 08 44 f7
22 59 73 b1 9d c5 0f db 3a 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 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 22 9d 1b 1d a3 e3 56 e0 99 75 da 6f c8 55 04 a2 7c 60 96 c2
08 44 f7 22 59 73 b1 9d c5 0f db 3a 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 00 00 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:02:6f:22:a8:76 (ver=1)
WPA: Failed to get master session key from EAPOL state machines
WPA: Key handshake aborted
...
...

Regards,
Pieter



From aschlemm  Thu May  5 14:18:53 2005
From: aschlemm (Tony Schlemmer)
Date: Thu, 5 May 2005 16:18:53 -0500
Subject: Accessing WEP protected networks with ipw2200 + wpa_supplicant
Message-ID: <200505051618.53229.aschlemm@comcast.net>

I've got a Dell Inspiron 6000 laptop with the built in Intel 2915 "Centrino" 
WIFI and I'm seeing problems when I try to access a WEP protected network 
when the "wpa_supplicant" daemon is running. I'm running SuSE 9.2 and it 
includes version 0.12 of the ipw2200. Before upgrading to the latest Intel 
driver I had issues even getting a connection to a WPA protected network. 

I upgraded the driver, firmware and so I now have the following running on my 
laptop:

ipw2200 1.0.3
firmware 2.2
wpa_supplicant 0.4.0

My only remaining problem is that when I connect to a network that's using WEP 
instead of WPA, the association only lasts for a few seconds and then it's 
lost. My workaround for now is to manually kill the "wpa_supplicant" daemon, 
disable it so it doesn't get started and I when I restart the network 
services on my laptop.

In searching through the archives it looks like this is a known problem with 
the Intel driver and not the "wpa_supplicant" daemon. The previous thread 
mentions this problem was with version 1.0.1 of the ipw2200 driver and it 
looks like it's an issue with the 1.0.3 driver as well.

Anthony
 
-- 
Anthony Schlemmer
aschlemm at comcast.net



From devel  Fri May  6 08:16:02 2005
From: devel (Travis J. Weaver)
Date: Fri, 6 May 2005 11:16:02 -0400
Subject: cloak SSID and ignore 'any' SSID
Message-ID: <005b01c5524e$843e4f90$0e03a8c0@Oberon.local>

Hello list,

    What is the command and parameters to cloak the SSID and ignore the 'any' SSID? Is this 'iwpriv wlan0 enh_sec' or something? And what would 'iwpriv wlan0 beacon_int 0' do?Thanks.

BTW
hostap-driver 0.2.6

Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050506/bcf6feb8/attachment.htm 


From deckrider  Fri May  6 09:09:57 2005
From: deckrider (David Everly)
Date: Fri, 6 May 2005 10:09:57 -0600
Subject: wpa_supplicant -Dhostap does not set restricted security mode
Message-ID: <20050506160957.GD27688@elbert.is-a-geek.org>

Hello,

Using the latest Debian/Sarge with their kernel-image-2.6.8-2-686,
related hostap-modules-2.6.8-2-686 (0.3.7-1), and wpasupplicant
(0.3.8-1) packages.

My wireless card is:

card "Linksys Instant Wireless Network PC Card ver.3"
   version "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA"
   manfid 0x0274, 0x1613

I can manually do the following to associate with the AP (the AP is
configured to require WEP shared key and does not broadcast its SSID):

iwconfig wlan0 essid "blah blah blah" \
               mode managed \
	       key restricted 00000000000000000000000000

However, with the following configurations, I cannot associate with the
AP using:

wpa_suppicant -D hostap \
              -i wlan0 \
	      -c /etc/wpa_supplicant.conf \
	      -w

/etc/wpa_supplicant.conf contains:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
        ssid="blah blah blah"
        key_mgmt=NONE
        wep_key0=00000000000000000000000000
        wep_tx_keyidx=0
        priority=5
        auth_alg=SHARED
}

Under this method, when I run 'iwconfig wlan0' I do see that the SSID is
set correctly, but it shows "Security mode:open", which is not correct.

I have also tried the orinoco_cs driver which works manually, but
doesn't even get as far as with the hostap_cs driver.

I am able to associate with this AP using similar configuration on a
different laptop that uses built in wireless requiring the ndiswrapper
driver.

Incidentally, I would like to vote for the following bug, since I have
several networks that do not broadcast their SSIDs:

   http://hostap.epitest.fi/bugz/show_bug.cgi?id=16

Thanks in advance,
Dave.

-- 
Encrypted Mail Preferred:
    Key ID:  8527B9AF
    Key Fingerprint:  E1B6 40B6 B73F 695E 0D3B  644E 6427 DD74 8527 B9AF
    Information:  http://www.gnupg.org/
                                                                                
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html
-------------- 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/20050506/a6acb187/attachment.pgp 


From tim  Thu May  5 11:56:25 2005
From: tim (Tim Boneko)
Date: Thu, 05 May 2005 20:56:25 +0200
Subject: HostAP with ralink card - might it work?
Message-ID: <427A6C59.9070701@kiste>

Hi!
While trying to get rid of wep encryption in my wlan, i found the hostap
project (i know, this is not for ralink cards...).
I decided to just give it a try and installed the package
(Debian 3.1, kernel 2.6.11.7). I configured my wlan card (msi pc54g2
with rt2500 driver) as "wired" and configured all necessary options. 
This is what i found out so far:

When running wpa_supplicant (on the client) in debug mode, it complains
about not finding a suitable AP - most probably because the rt2500
driver doesn?t work in Master mode (yet). Nevertheless, "iwconfig" tells
me that the client uses the hostap machine as AP, and the "Mode" entry
switched itself from "Ad-Hoc" to "Managed".
Under circumstances i can?t really reproduce, hostapd tells me something
like "releasing station [MAC address of the _client_] when i shut down
wpa_supplicant on the client. However, hostapd doesn?t keep the clients
from connecting, even with a bad password - it seems useless.

Is it any worth trying this any further? Has anybody gotten this to work
with a ralink card, or is support for this planned?
thx,

	timbo




From zen_hacker  Fri May  6 13:25:21 2005
From: zen_hacker (Brian Sturgill)
Date: Fri, 06 May 2005 20:25:21 +0000
Subject: cloak SSID and ignore 'any' SSID
In-Reply-To: <005b01c5524e$843e4f90$0e03a8c0@Oberon.local>
Message-ID: <BAY13-F11F6B7D274DFA5CAC3CAEF71B0@phx.gbl>

Here is a clip from the README file in the driver directory of 0.2.4

enh_sec: "enhanced security" bitfield
        0 = options disabled (default)
        1 = hide SSID in beacon frames
        2 = ignore clients configured with "ANY" (broadcast) SSID
        (3 = both options)
        Note! This requires STA f/w ver 1.6.3 or newer

Here is what I use:  /sbin/iwpriv wlan0 enh_sec 3

Hope this helps

Brian

>From: "Travis J. Weaver" <devel at oberonwireless.com>
>Reply-To: "Travis J. Weaver" <devel at oberonwireless.com>
>To: "HostAP" <hostap at shmoo.com>
>Subject: cloak SSID and ignore 'any' SSID
>Date: Fri, 6 May 2005 11:16:02 -0400
>
>Hello list,
>
>     What is the command and parameters to cloak the SSID and ignore the 
>'any' SSID? Is this 'iwpriv wlan0 enh_sec' or something? And what would 
>'iwpriv wlan0 beacon_int 0' do?Thanks.
>
>BTW
>hostap-driver 0.2.6
>
>Travis
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From benjcarson  Fri May  6 14:05:45 2005
From: benjcarson (Benj Carson)
Date: Fri, 06 May 2005 15:05:45 -0600
Subject: madwifi and wpa-psk problem
Message-ID: <200505061505.45184.benjcarson@digitaljunkies.ca>

Hello,

I've scoured this list a bit and it seems I've run across the same problem as 
a few others [1] with madwifi and WPA.  Some people have reported success, so 
I'm hopeful that I can get this to work.

I have a D-Link DWL-G520 which uses the Atheros AR5212 chip and a Linksys 
WAP54G.  The AP is configured to use WPA-PSK, and works fine with the Intel 
PRO/Wireless 2100 in my laptop.  I'm running the latest developer CVS snap of 
wpa_supplicant and I updated madwifi from CVS last week.

I'm having trouble getting the card to associate completely with the AP.  In 
looking at the wpa_supplicant logs, it appears that authentication proceeds 
correctly, but once the group handshake is completed, the connection gets 
disconnected:

...
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:0f:66:75:0c:88 into blacklist
State: COMPLETED -> DISCONNECTED

I'm fairly confident that my wpa_supplicant configuration is correct because 
it is basically identical to the config on my laptop, which works.  Beyond 
fairly obvious issues, I'm not really able to debug this any further and I'm 
hoping someone here can help.  I've collected a debug log from 
wpa_supplicant, turned on debugging in the madwifi driver and I collected 
packets during authentication using my laptop.  These are available here:

http://www.digitaljunkies.ca/~benj/wpa_supplicant/wpa_supplicant.log
http://www.digitaljunkies.ca/~benj/wpa_supplicant/madwifi_debug.log
http://www.digitaljunkies.ca/~benj/wpa_supplicant/Kismet-May-06-2005-1.dump

The system is running Debian, on their 2.6.8-k7 kernel.  If there is any other 
information I should provide, please let me know.  I'm half-handy in C (just 
not familiar with WiFi) so if there's code that you'd like me to noodle with, 
let me know.

Thanks,


Benj Carson
--
[1] http://lists.shmoo.com/pipermail/hostap/2005-April/010110.html



From brian  Fri May  6 14:13:50 2005
From: brian (Brian J. Murrell)
Date: Fri, 06 May 2005 17:13:50 -0400
Subject: smc 7004vwbr is crap!
Message-ID: <1115414030.18871.29.camel@pc>

So after much struggling using wpa_supplicant with an SMC 7004WVBR, I
have gone out and bought a Linksys WRT54GS and my blood pressure has
gone way down.  This thing's WPA "just works".  No having to reboot APs,
restart wpa_supplicant, ifup/down interfaces etc.

Simply put, the SMC 7004WVBR is a big stinkin' smoking bag of crap (as
least where WPA is concerned).  Stay away from it at all costs.  Spend a
bit more and get something that works.

Glad mine was free.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050506/bf231442/attachment.pgp 


From rocci  Sat May  7 00:10:54 2005
From: rocci (Rocci)
Date: Sat, 07 May 2005 17:10:54 +1000
Subject: wpa not working with server ca
In-Reply-To: <42787EF9.9040509@anticd.org>
References: <42780CD1.6000408@rocknetworks.net.au>
	<42787EF9.9040509@anticd.org>
Message-ID: <427C69FE.50801@rocknetworks.net.au>

Thanks Heaps Simon,
That worked for me.
However, that variable should be include_tls_length=1, and not 
includes_tls_length=1.
I think Jouni had accidentally mispelled that variable in his posted 
reply to your original post regarding this problem.
You might want to change the spelling in your config and try again.

I wonder why I didn't need include_tls_length=1 until now. Perhaps IT 
services changed something on their wifi network.
Anyway, it works and I'm back on the UOW WiFi network using WPA.

For those that may find it useful, here is my wpa_supplicant config:

eapol_version=1
ap_scan=1
fast_reauth=1

network={
        ssid="ACHERNAR-BG"
        key_mgmt=WPA-EAP
        eap=PEAP
        pairwise=TKIP
        group=TKIP
        identity="myusername"
        password="mypassword"
        ca_cert="/etc/ssl/certs/Thawte_Server_CA.pem"
        phase1="peaplabel=0 include_tls_length=1"
        phase2="auth=MSCHAPV2"
        priority=1
}

Hope this helps others as it did me.
- Rocci.


Simon Males wrote:

>
> Rocci wrote:
>
>> Hi there,
>> I once had this working on my university network but it no longer works.
>> I have since upgraded my kernel and other aspects of my OS.
>> Recompiled madwifi & wpa_supplicant on new linux kernel.
>> WPA-PSK works fine on my PSK network at home but I can no longer get 
>> this to work on my university network.
>
>
> Rocci,
>
>     Bugger, I never got the chance to connect (been struggling since 
> start of semester), its not looking good if even you cannot connect! I 
> posted a -d output a little while ago, Jouni asked me to pump out -dd 
> output. Jouni did recommend to add includes_tls_length=1 to phase1, 
> although my conf is a little different.
>
> Initial thread:
> http://lists.shmoo.com/pipermail/hostap/2005-April/010030.html
>
> I let it run for a little while and don't want to paste the whole 
> output to the list.
>
> http://anticd.org/~sime/wifi/wpa_error-dd.txt
>
> wpa_supplicant.conf:
> network={
>        ssid="ACHERNAR-BG"
>        key_mgmt=WPA-EAP
>        eap=PEAP
>        pairwise=TKIP
>        group=TKIP
>        identity="***"
>        password="***"
>        ca_cert="/home/sime/Downloads/wifi/thawte/ThawteServerCA.pem"
>        phase1="peaplabel=0 includes_tls_length=1"
>        phase2="auth=MSCHAPV2"
>        priority=10
> }
>
>



From jkmaline  Sat May  7 08:33:00 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 08:33:00 -0700
Subject: Should EAP-MD5 and EAP-MSCHAPv2 support dynamic WEP key?
In-Reply-To: <32653c97050428225517e8ddeb@mail.gmail.com>
References: <32653c97050428225517e8ddeb@mail.gmail.com>
Message-ID: <20050507153300.GK29395@jm.kir.nu>

On Fri, Apr 29, 2005 at 01:55:48PM +0800, YenJung Chang wrote:

> In wpa_supplicant, EAP-MD5 does NOT support dynamic WEP key, does it
> follow the standard? If it does, could somebody please tell me where
> can I get the standard and confirm this information?

EAP-MD5 does not generate keying material and as such, it cannot be used
to generate dynamic WEP keys. This EAP type is defined in RFC 3748.

> Beside, I did not find any information about the relationship between
> EAP-MSCHAPv2 and dynamic WEP key. Could somebody please tell me should
> EAP-MSCHAPv2 support dynamic WEP key or not?

In theory, this could be done, but most implementations do not seem to
use EAP-MSCHAPv2 to generate keys. The keying material defined for
MSCHAPv2 is shorter than normally used with IEEE 802.1X. It is used in
some cases, e.g., binding inner method keys to the full authentication
(EAP-FAST), but it is not usually used without tunneling method
(PEAP/TTLS/FAST).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 15:29:05 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 15:29:05 -0700
Subject: compiling hostapd without EAP, with 802.1x
In-Reply-To: <1115293718.3263.8.camel@localhost.localdomain>
References: <1115293718.3263.8.camel@localhost.localdomain>
Message-ID: <20050507222905.GL29395@jm.kir.nu>

On Thu, May 05, 2005 at 12:48:38PM +0100, Steve wrote:

> Ive found a problem with a code change made on Sun Apr 17 17:08:21 2005
> to hostap/hostapd/ieee802_1x.c Line 838 of the current CVS
> 	if (sta->eapol_sm->eap)
> 			eap_sm_notify_cached(sta->eapol_sm->eap);
> 
> I build hostapd without the EAP component. The code change assumes that
> the EAP module has been included with CONFIG_EAP in the .config.

> I would suggest that a #ifdef CONFIG_EAP is required around this line???

Thanks for reporting this. I fixed this in CVS version by defining an
empty inline function for the case when EAP is not included. This was
forgotten from eap.h when the new function was added.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 15:30:56 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 15:30:56 -0700
Subject: PEAPv2 support
In-Reply-To: <20050505080625.GD13303@ruslug.rutgers.edu>
References: <20050505080625.GD13303@ruslug.rutgers.edu>
Message-ID: <20050507223056.GM29395@jm.kir.nu>

On Thu, May 05, 2005 at 04:06:25AM -0400, Luis R. Rodriguez wrote:

> how far are we with PEAPv2 support in wpa_supplicant as per
> draft-josefsson-pppext-eap-tls-eap-07.txt:

There is not much support for PEAPv2 changes yet. I have been mostly
waiting to see whether the draft is getting stable and whether anyone
has any real interest in implementing PEAPv2.

> I have been trying to auth against IAS at work in a peap/mschapv2 setup
> unsuccessfully. I'm wondering if it has something to do with peapv2.

This has nothing to do with PEAPv2. IAS is using PEAPv0 and
wpa_supplicant works fine with IAS in my tests.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:23:46 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:23:46 -0700
Subject: HostAP with ralink card - might it work?
In-Reply-To: <427A6C59.9070701@kiste>
References: <427A6C59.9070701@kiste>
Message-ID: <20050508062346.GN29395@jm.kir.nu>

On Thu, May 05, 2005 at 08:56:25PM +0200, Tim Boneko wrote:

> While trying to get rid of wep encryption in my wlan, i found the hostap
> project (i know, this is not for ralink cards...).
> I decided to just give it a try and installed the package
> (Debian 3.1, kernel 2.6.11.7). I configured my wlan card (msi pc54g2
> with rt2500 driver) as "wired" and configured all necessary options. 

What exactly are you trying to do and what do you mean with "HostAP" in
this context? Your message was talking about HostAP (which, at least for
me, is a driver from Prism2/2.5/3 cards), wpa_supplicant (IEEE
802.1X/WPA supplicant), and hostapd (IEEE 802.1X/WPA authenticator and
other optional AP functionality).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:27:38 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:27:38 -0700
Subject: Testing wpa_supplicant on Windows
In-Reply-To: <E7CB2B504D3C62875D686B7C@cumulus>
References: <E7CB2B504D3C62875D686B7C@cumulus>
Message-ID: <20050508062738.GO29395@jm.kir.nu>

On Thu, May 05, 2005 at 05:38:44PM +0100, Josh Howlett wrote:

> I have the opportunity shortly to test wpa_supplicant on a large number of 
> machines running a variety of Windows OSes at different patch levels. 

Please note that ndis_events.exe has been reported not to work on older
versions than WinXP, but I haven't seen test results from
wpa_supplicant.exe on other than WinXP so far.

> I was wondering whether it were possible to remove the need for the WinPcap 
> installation by compiling wpa_supplicant appropriately?

No, WinPcap is required for getting access to EAPOL packets used in IEEE
802.1X/WPA and for accessing the NDIS driver. One could of course
implement a new intermediate driver for providing same functionality,
but that would not really change the requirement for installation.

If you want to make installation easier, a combined installer for
WinPcap and wpa_supplicant would be the way to go at least for now.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:32:47 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:32:47 -0700
Subject: Handover performance.
In-Reply-To: <20050505080133.22585.qmail@webmaildomini.aruba.it>
References: <20050504100758.5564.qmail@webmaildomini.aruba.it>
	<200505041334.20069.vda@ilport.com.ua>
	<20050505080133.22585.qmail@webmaildomini.aruba.it>
Message-ID: <20050508063247.GP29395@jm.kir.nu>

On Thu, May 05, 2005 at 10:01:32AM +0200, roby wrote:

> I need to know if it possible to use pre-authentication using WPA1. I need 
> to reduce the handover delay.
> DO the pre-authentication work only with RSN/WPA2? 

There's a reason for hostapd.conf calling it "IEEE 802.11i/RSN/WPA2
pre-authentication"... In other words, it is indeed only for RSN/WPA2
and it will not work in the configuration file you are using (WPA only
network).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:39:31 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:39:31 -0700
Subject: Problem with WPA-PSK
In-Reply-To: <42777855.2050005@aber.ac.uk>
References: <42777855.2050005@aber.ac.uk>
Message-ID: <20050508063931.GQ29395@jm.kir.nu>

On Tue, May 03, 2005 at 02:10:45PM +0100, Nicolas Labrosse wrote:

> I want to use Wifi on my laptop and I use wpa_supplicant with atheros card AR5212. It works if I choose WEP encryption but I can't get it to work if I choose WPA-PSK.

What AP are you using? Can you please send a wpa_supplicant debug log
without removing the packet dumps ("obscured" in the log you sent)? If
you can easily capture a packet log, e.g., with tcpdump or Ethereal,
from the client ('ifconfig ath0 up' and start sniffer before starting
wpa_supplicant), it could also be useful for looking at what is
happening.

> Associated with 00:05:b4:07:e9:91

> EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
> 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
> EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
> EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
> RX EAPOL from 00:05:b4:07:e9:8e

This is somewhat odd behavior from the AP. First, it takes six seconds
to send out the first EAPOL-Key frame and the frame seems to be coming
from another MAC address. Do you happen to know whether this address
would be the MAC address of the wired interface?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:42:07 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:42:07 -0700
Subject: WPA with Cisco PCMCIA card?
In-Reply-To: <427777BB.3030608@dsa-ac.de>
References: <427777BB.3030608@dsa-ac.de>
Message-ID: <20050508064207.GR29395@jm.kir.nu>

On Tue, May 03, 2005 at 03:08:11PM +0200, Tilman Schoop wrote:

> I would like to know if there is a possibility to setup eap/tls and tkip
> with wpa_supplicant and a Cisco 350 PCMCIA WLAN card.
> 
> I have seen that my card does not fall into one of the categories of
> supported drivers for wpa_supplicant,

So, you already know the answer to your question.. ;-)

> but from Jean Tourilhes howto
> website I have learned that the Cisco driver 2.1 can do AES(host) and
> MIC. Is there a possibility to use this driver with wpa_supplicant?

Someone would need to either implement Linux wireless extensions v18
support in the Cisco driver or a wpa_supplicant driver interface for the
current driver. This may also require changes for the driver; I haven't
looked into details of how the Cisco driver is supposed to work with
AES.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:48:11 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:48:11 -0700
Subject: Wireless Extensions v18 and Hostap-Driver v0.3.7
In-Reply-To: <42710DC6.2000708@pepper.com>
References: <42710DC6.2000708@pepper.com>
Message-ID: <20050508064811.GS29395@jm.kir.nu>

On Thu, Apr 28, 2005 at 12:22:30PM -0400, Tony Espy wrote:

> I recently upgraded to the hostap-driver v0.3.7.  Now when I run 
> 'iwconfig' it outputs the message:
> 
> 'Warning: Driver for device wifi0 recommend version 18 of Wireless 
> Extension, but has been compiled with version 15, therefore some driver 
> features may not be available...'

> (1) Is there any way of surpressing this message short of hacking the 
> iwconfig code?

Like hacking some other code? Of course you can change the driver, but I
don't see why that would be any better than changing iwconfig not to
print this warning or build it with WE-18 header files. Of course,
another option would be to direct the output to /dev/null.

> (2) What's the current state of WE version 18?

WE-18 is ready and hopefully included in the next kernel version.

> (3) Are there any major gotchas in trying to bring our kernel up to a 
> later WE version?

I'm not aware of any major problems in doing this.

>  Are there any major advantages in picking up a later 
> verion of WE ( ie. post v15 ).

Depends on whether you need the new features added after v15..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:54:02 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:54:02 -0700
Subject: How to use eapol_test
In-Reply-To: <3046C179E69FC24AB83536978A17614D014E1270@i2km96-ukbr.domain1.systemhost.net>
References: <3046C179E69FC24AB83536978A17614D014E1270@i2km96-ukbr.domain1.systemhost.net>
Message-ID: <20050508065402.GT29395@jm.kir.nu>

On Tue, May 03, 2005 at 04:14:14PM +0100, martin.p.bradley at bt.com wrote:

> I have got eapol_test compiled thanks to Jouni but I don't know how to
> use it.  Could someone tell me where the documentation is or how to use
> it.

Normally, one would create a configuration file with one network block
(this is using the same format as wpa_supplicant configuration file):

network={
    key_mgmt=WPA-EAP
    eap=PEAP
    identity="user"
    password="password"
    ca_cert="ca.pem"
    phase2="auth=MSCHAPV2"
    anonymous_identity="anonymous"
    eap_workaround=0
}


and run eapol_test with something like this:

./eapol_test -cconf.file -a127.0.0.1 -ssecret


If you did not yet notice, eapol_test has a brief usage text:

$ ./eapol_test
usage:
eapol_test [-nW] -c<conf> [-a<AS IP>] [-p<AS port>] [-s<AS secret>] [-r<count>]
eapol_test scard
eapol_test sim <PIN> <num triplets> [debug]

options:
  -c<conf> = configuration file
  -a<AS IP> = IP address of the authentication server, default 127.0.0.1
  -p<AS port> = UDP port of the authentication server, default 1812
  -s<AS secret> = shared secret with the authentication server, default 'radius'
  -r<count> = number of re-authentications
  -W = wait for a control interface monitor before starting
  -n = no MPPE keys expected
Configuration file is required.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May  7 23:58:05 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 7 May 2005 23:58:05 -0700
Subject: Using monitor mode
In-Reply-To: <200504291754.j3THsfN7014925@luna.tlmat.unican.es>
References: <200504291754.j3THsfN7014925@luna.tlmat.unican.es>
Message-ID: <20050508065805.GU29395@jm.kir.nu>

On Fri, Apr 29, 2005 at 08:13:29PM +0200, Johnny Choque wrote:

> Please, someone tell me how should configure my laptops in order to capture
> simultaneously both data packets and 802.11 management frames?

Works for me when configured with 'iwconfig wlan0 mode monitor'.. How
did you configure the driver to monitor mode?

-- 
Jouni Malinen                                            PGP id EFC895FA



From rocci  Sun May  8 07:11:33 2005
From: rocci (Rocci)
Date: Mon, 09 May 2005 00:11:33 +1000
Subject: madwifi and wpa-psk problem
In-Reply-To: <05050718235838@sludge.rocknetworks.net.au>
References: <05050718235838@sludge.rocknetworks.net.au>
Message-ID: <427E1E15.1040800@rocknetworks.net.au>

Can you please post your config for wpa_supplicant ?

- Rocci

Benj Carson wrote:

>Hello,
>
>I've scoured this list a bit and it seems I've run across the same problem as 
>a few others [1] with madwifi and WPA.  Some people have reported success, so 
>I'm hopeful that I can get this to work.
>
>I have a D-Link DWL-G520 which uses the Atheros AR5212 chip and a Linksys 
>WAP54G.  The AP is configured to use WPA-PSK, and works fine with the Intel 
>PRO/Wireless 2100 in my laptop.  I'm running the latest developer CVS snap of 
>wpa_supplicant and I updated madwifi from CVS last week.
>
>I'm having trouble getting the card to associate completely with the AP.  In 
>looking at the wpa_supplicant logs, it appears that authentication proceeds 
>correctly, but once the group handshake is completed, the connection gets 
>disconnected:
>
>...
>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:0f:66:75:0c:88 into blacklist
>State: COMPLETED -> DISCONNECTED
>
>I'm fairly confident that my wpa_supplicant configuration is correct because 
>it is basically identical to the config on my laptop, which works.  Beyond 
>fairly obvious issues, I'm not really able to debug this any further and I'm 
>hoping someone here can help.  I've collected a debug log from 
>wpa_supplicant, turned on debugging in the madwifi driver and I collected 
>packets during authentication using my laptop.  These are available here:
>
>http://www.digitaljunkies.ca/~benj/wpa_supplicant/wpa_supplicant.log
>http://www.digitaljunkies.ca/~benj/wpa_supplicant/madwifi_debug.log
>http://www.digitaljunkies.ca/~benj/wpa_supplicant/Kismet-May-06-2005-1.dump
>
>The system is running Debian, on their 2.6.8-k7 kernel.  If there is any other 
>information I should provide, please let me know.  I'm half-handy in C (just 
>not familiar with WiFi) so if there's code that you'd like me to noodle with, 
>let me know.
>
>Thanks,
>
>
>Benj Carson
>--
>[1] http://lists.shmoo.com/pipermail/hostap/2005-April/010110.html
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>



From jkmaline  Sun May  8 12:03:21 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:03:21 -0700
Subject: wpa_supplicant + madwifi <--Peap--- SenaoAP ---Peap--> freeradius
In-Reply-To: <4279261C.7030502@gmail.com>
References: <20050504100937.5D79E1345E0@mail.iocaine.com>
	<4279261C.7030502@gmail.com>
Message-ID: <20050508190321.GX29395@jm.kir.nu>

On Wed, May 04, 2005 at 09:44:28PM +0200, Pieter E Smit wrote:

> I am connecting with a madwifi (wpa_supplicant) to a senao AP with wpa
> peap and freeradius server.

Which version of wpa_supplicant and FreeRADIUS are you using? Which
Senao AP model is this and what firmware version are you using?

> Full Dump
> http://www.vigor.co.za/linux/wpa_supplicant_20050504.txt
> http://www.vigor.co.za/linux/freeradius_20050504.txt
> 
> wpa_supplicant
> network={
> 	ssid="wireless_11g"	
> 	key_mgmt=WPA-EAP
> 	eap=PEAP
> 	pairwise=TKIP
> 	group=TKIP
> 	identity="user at vigor"
> 	password="foobar"
> 	#anonymous_identity="anonymous"
> 	#ca_cert="/etc/cert/ca.pem"
> 	#phase1="peaplabel=1 includes_tls_length=1" <<Does not change anything.	
> 	phase2="auth=MSCHAPV2"
> 	priority=2

includes_tls_length is a typo (should be include_tls_length), but
anyway, this is not needed with FreeRADIUS.

This wpa_supplicant configuration file does not seem to be complete,
i.e., the debug log shows other fields than the ones included here..

> EAP-PEAP: received Phase 2: code=1 identifier=98 length=11

> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Success
> EAP: EAP-Success Id mismatch - reqId=89 lastId=98
> EAP: EAP entering state DISCARD

There is something odd going on with the EAP identifiers.. I've never
seen this kind of behavior with FreeRADIUS, so I would guess the AP
(IEEE 802.1X Authenticator) could be doing something weird..

Would it be possible for you to make a capture log of EAPOL packets
between the Supplicant and Authenticator (e.g., run tcpdump or ethereal
on the client) and another capture log of RADIUS packets
(tcpdump/ethereal on the host running FreeRADIUS)? Getting these capture
files from the same authentication attempt would be quite helpful for
understanding what is happening here.

> And it continues with tls peap etc.
> Q1. The line "EAP: Received EAP-Success" does this mean i have been
> authenticated ?

This means that the authentication server believed that EAP
authentication was completed successfully.

> Q2. "EAP: EAP-Success Id mismatch - reqId=89 lastId=98" i see often, it
> seems the ap is sending new requestes during the authentication. Is this
> a problem ?

Yes, wpa_supplicant is ignoring the EAP-Success packet since it had
incorrect identifier. This will break the following WPA 4-Way Handshake
since wpa_supplicant does not believe that EAP was completed and as
such, it cannot get the pairwise master key needed for the 4-Way
Handshake,

As a workaround, you could consider changing eap_success_workaround()
function in eap.c to always return 1 (e.g., add "return 1;" as the first
line in that function). This should allow the 4-Way Handshake to be
started properly. Anyway, I would like to understand what is happening
here, so the capture logs I mentioned above would still be helpful even
if this workaround would allow the authentication to be completed.

> Q3. "How do I know if the AP and supplicant has exchanged keys ?

With WPA, wpa_supplicant debug log will show "WPA: Key negotiation
completed with <BSSID> [PTK=<TKIP/CCMP> GTK=<TKIP/CCMP>" when the WPA
key handshake has been completed and data encryption keys have been
exchanged.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:21:28 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:21:28 -0700
Subject: madwifi and wpa-psk problem
In-Reply-To: <200505061505.45184.benjcarson@digitaljunkies.ca>
References: <200505061505.45184.benjcarson@digitaljunkies.ca>
Message-ID: <20050508192128.GY29395@jm.kir.nu>

On Fri, May 06, 2005 at 03:05:45PM -0600, Benj Carson wrote:

> I have a D-Link DWL-G520 which uses the Atheros AR5212 chip and a Linksys 
> WAP54G.  The AP is configured to use WPA-PSK, and works fine with the Intel 
> PRO/Wireless 2100 in my laptop.  I'm running the latest developer CVS snap of 
> wpa_supplicant and I updated madwifi from CVS last week.

Which CVS branch of madwifi are you using (trunk/mainline or BSD
branch)?

> I'm having trouble getting the card to associate completely with the AP.  In 
> looking at the wpa_supplicant logs, it appears that authentication proceeds 
> correctly, but once the group handshake is completed, the connection gets 
> disconnected:

As far as wpa_supplicant is concerned, the WPA-PSK key handshakes are
indeed completed successfully. However, the AP does not seem to be
receiving the final message (group key msg 2/2) and it will retry the
group key handshake by sending msg 1/2 number of times. Eventually, it
will time out and send a deauthentication frame (with reason "Group key
update timeout" in the kismet log you sent).

Unfortunately, the sniffer log does not include EAPOL-Key frames for
some reason. It would be very helpful to get a capture that includes
both the management frames and these data frames in order to verify that
the Group Key packets are indeed sent correctly. One reason for AP not
receiving the frame would be in it not being encrypted correctly. It may
also be possible to use madwifi debugging to find out whether the Group
Key packets are encrypted or not (they should be). I'm not sure how to
enable debugging for this, though.

Following packets should be exchanged in a successful WPA-PSK
authentication:

STA -> AP: mgmt::authentication
STA <- AP: mgmt::authentication
STA -> AP: mgmt::association request
STA <- AP: mgmt::association response
STA <- AP: data::data (unencrypted EAPOL-Key packet, msg 1/4)
STA -> AP: data::data (unencrypted EAPOL-Key packet, msg 2/4)
STA <- AP: data::data (unencrypted EAPOL-Key packet, msg 3/4)
STA -> AP: data::data (unencrypted EAPOL-Key packet, msg 4/4)
STA <- AP: data::data (encrypted EAPOL-Key packet, msg 1/2)
STA -> AP: data::data (encrypted EAPOL-Key packet, msg 2/2)

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:32:56 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:32:56 -0700
Subject: [PATCH] Warning fix for 64-bit platforms
In-Reply-To: <1115157043.11663.14.camel@dv.roinet.com>
References: <1115157043.11663.14.camel@dv.roinet.com>
Message-ID: <20050508193256.GZ29395@jm.kir.nu>

On Tue, May 03, 2005 at 05:50:43PM -0400, Pavel Roskin wrote:

> The patch fixes following warning seen on 64-bit platforms (in my case -
> x86_64, gcc-4.0):

Thanks! Applied with a minor change to also update
hfa384x_cmd_callback() documentation to not call context argument
"data pointer".

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:38:23 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:38:23 -0700
Subject: Hostap and WDS
In-Reply-To: <427282F6.7050505@sahasrasolutions.com>
References: <427282F6.7050505@sahasrasolutions.com>
Message-ID: <20050508193823.GA29395@jm.kir.nu>

On Sat, Apr 30, 2005 at 12:24:46AM +0530, govind wrote:

> We have two Soekris 4521 boards with each having different Senao card
> (One card being Senao SL-2011CD and another one being Senao NL-2011CDPlus
> Ext2 Mercury) both running hostap. If each of these boards are
> accessed as AP's from laptop's, they work fine. But the moment, we
> configure WDS on them to connect the AP's together, they dont seem to
> like each other ;-)

Could you please list the commands you used to configure the WDS links?
Are you using hostapd in this setup?

> DISCLAIMER:
> Information contained and transmitted by this E-MAIL is
> proprietary to Sahasra Solutions

...

Please try to avoid including this kind of disclaimers when sending
messages to this mailing list. I'm known to often ignore messages
completely if they include this kind of invalid disclaimers about
proprietary and confidential information..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:43:00 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:43:00 -0700
Subject: ndiswrapper + wpa_supplicant + SMC 2802W
In-Reply-To: <XFMail.20050428095258.tacorner@chello.at>
References: <XFMail.20050428095258.tacorner@chello.at>
Message-ID: <20050508194300.GB29395@jm.kir.nu>

On Thu, Apr 28, 2005 at 10:03:36AM +0200, tacorner at chello.at wrote:

> I recently purchased a PCI Wifi Card, EZ Connect g SMC 2802W.  I am using a
> recent (last week) version of ndiswrapper from cvs and wpa_supplicant-0.4.0.  I
> can create an Ad-Hoc connection with a laptop using a cardbus card under
> ndiswrapper.  This Ad-Hoc connection has no encryption however.  When I try to
> connect to my netgear WG602 AP it associates, but never completes the WPA
> authentication.

The debug log shows that the driver is reporting association but no
EAPOL packets are received from the access point. I would recommend
first asking on ndiswrapper mailing list whether anyone has been able to
use this card (and the NDIS driver you are using) successfully with WPA.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:48:56 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:48:56 -0700
Subject: Optional WPA and RSN
In-Reply-To: <200504211928.04021.pjf@asn.pl>
References: <200504211928.04021.pjf@asn.pl>
Message-ID: <20050508194856.GC29395@jm.kir.nu>

On Thu, Apr 21, 2005 at 07:28:04PM +0200, Pawel Foremski wrote:

> And here is my question: would it need a lot work (possibly hacking 
> hostapd/drivers) to make hostapd allow both no security at all and RSN (or at 
> least old WPA) at the same time on one access point?

In order for this to work reliably with all client implementations, the
AP would need to be sending out multiple beacon frames (one for each
security mode; usually called "multiple BSSID" or "virtual AP"). This
would need additional functionality from the card firmware/driver and
unfortunately, the current Prism2/2.5/3 firmware does not support it.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 12:51:07 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 12:51:07 -0700
Subject: Authenticate an AP
In-Reply-To: <50834.70.21.108.141.1113999873.squirrel@www.flacp.fujitsulabs.com>
References: <50834.70.21.108.141.1113999873.squirrel@www.flacp.fujitsulabs.com>
Message-ID: <20050508195107.GD29395@jm.kir.nu>

On Wed, Apr 20, 2005 at 08:24:33AM -0400, M Tamer Refaei wrote:

> I have this setup where I have a number of APs running hostap/hostapd
> 0.3.7.  I want APs to establish WDS links with each other only after they
> authenticate to one another.  Is it possible at all to do 802.1X
> authentication between APs (i.e. cards running in master mode)?

This is not currently supported, but in theory, it should be possible to
modify hostapd to do 802.1X authentication for WDS links with minimal
changes and then use wpa_supplicant on the other end of the link to act
as a client.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 15:47:58 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 15:47:58 -0700
Subject: madwifi and wpa-psk problem
In-Reply-To: <20050508192128.GY29395@jm.kir.nu>
References: <200505061505.45184.benjcarson@digitaljunkies.ca>
	<20050508192128.GY29395@jm.kir.nu>
Message-ID: <20050508224758.GE29395@jm.kir.nu>

On Sun, May 08, 2005 at 12:21:28PM -0700, Jouni Malinen wrote:

> As far as wpa_supplicant is concerned, the WPA-PSK key handshakes are
> indeed completed successfully. However, the AP does not seem to be
> receiving the final message (group key msg 2/2) and it will retry the
> group key handshake by sending msg 1/2 number of times. Eventually, it
> will time out and send a deauthentication frame (with reason "Group key
> update timeout" in the kismet log you sent).

I was able to reproduce this problem and the reason for WPA group
handshake not completing was indeed in EAPOL frames not being encrypted
correctly. Some of the ioctl call reordering in wpa_supplicant v0.4.0
must have confused the madwifi driver enough to make it believe it was
not using WPA and consequently, it sent out unencrypted Group Key
messages. This is now fixed in development branch in wpa_supplicant CVS;
the stable branch (0.3.x) versions did not have this problem.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 15:58:20 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 15:58:20 -0700
Subject: wpa_supplicant messaging
In-Reply-To: <20050425135452.GF25887@ch.lugn.nu>
References: <1113391502.18734.23.camel@uberlaptop.ubernet>
	<20050414041656.GB8087@jm.kir.nu>
	<1113989813.18957.2.camel@uberlaptop.ubernet>
	<20050424035301.GB27379@jm.kir.nu>
	<20050425135452.GF25887@ch.lugn.nu>
Message-ID: <20050508225820.GF29395@jm.kir.nu>

On Mon, Apr 25, 2005 at 03:54:53PM +0200, Martin Samuelsson wrote:

> I still think it should be a part of the wpa_supplicant executable for
> two reasons:
> 
> 1. Having one additional process just for starting scripts seems like
>    resource waste.

Separate process is needed in order not to make it more difficult to
implement privacy separation in wpa_supplicant. I don't want to add new
functionality that requires root privileges after startup into
wpa_supplicant if that can be easily avoided.

> 2. Having one configuration file for configuring all wireless stuff
>    would be better for the user than a bunch of places that have to be
>    edited.

If that is really desired, it can be implemented by using this single
file for generating whatever is needed..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 16:36:58 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 16:36:58 -0700
Subject: wpa keyhandshake question / bug
In-Reply-To: <20050419201011.fdviqf9bbnhw8sww@webmail.togg.de>
References: <20050419201011.fdviqf9bbnhw8sww@webmail.togg.de>
Message-ID: <20050508233658.GG29395@jm.kir.nu>

On Tue, Apr 19, 2005 at 08:10:11PM +0200, Sebastian Weitzel wrote:

> I am investigating a wpa bug together with hostapd (tested mit madwifi 
> but should also apply to others) and serveral types of clients 
> (windows, prism, madwifi). On reauthentication (WPA, EAP-TLS) clients 
> lose connection from time to time, especially when there is traffic 
> between client and ap. I narrowed down the problem into one direction, 
> and I now want to get some feedback here to hopefully solve it soon.

How often does this happen (e.g., percentage of attempts) and how much
other traffic was being transmitted during reauthentication?

> I will refer to the 802.11i-2004 standard to describe my problem.
> On page 89 step 4 of the 4-way handshake is described. When the 
> Authenticator received message 4 it checks some things and then goes to 
> PTKINITDONE and sets new key to the driver. After this a group key 
> handshake should occur.

IEEE 802.11i-2004 does not use Group Key handshake directly after 4-Way
Handshake; this mechanism is only used with WPA.. Are you talking about
WPA or WPA2?

> This does not always work for me. In my scenario the message 4 under 
> some circumstance does not reach the authenticator. One possibility is 
> it is lost on air. Another harmfull possibilty is that the message 4 is 
> already encrypted with the new sta key and is dropped by the MAC layer 
> as crypto error (linux queuing issue maybe, that means the message 4 is 
> stuck in linux queue while the .set_key function allready activated the 
> new key in the driver). In first case a retransmit on mac layer 
> will/should happen?

Yes, the first case should rely on lower layer retransmission. It might
be useful to use a lower transmit rate and larger retry count for EAPOL
frames in order to make them less likely to be dropped.

Unfortunately, sending msg 4/4 has some race condition issues in both
WPA and WPA2. set_key() better not change the before msg 4/4 has been
sent out. If this is happening often, some additional synchronization
would be needed to avoid issues.

> That is the point where I am very confused. Does wpa_supplicant 
> recognize that the message 4 did not arrived at the ap and will 
> retransmit the packet? And whats with the driver interface? If the 
> .set_key function is done (directly after sending message 4) all 
> packets from this time on would be encrypted with the new key and 
> dropped from the ap because the 4-way is not done.

There is no mechanism for wpa_supplicant to know whether msg 4/4 was
sent out correctly or not. Even if there were, it does not really have
many options in fixing the case. Retransmitting the EAPOL message is
done at the lower layer and supplicant is only replying to received
EAPOL frames.

The AP will likely retransmit msg 3/4 if it does not receive msg 4/4.
However, this msg 3/4 is using the old key (or plaintext for the first
4-Way Handshake). Drivers could make this more robust by storing the
previously used key for short period of time after key change and trying
to use it to decrypt packets that fail decryption with the new key. This
would allow the retransmitted msg 3/4 to go through.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 16:58:56 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 16:58:56 -0700
Subject: Bug? After switching from monitor mode to master,
	hostap sends *invalid* *IBSS* beacons
In-Reply-To: <200504051012.08157.vda@port.imtp.ilyichevsk.odessa.ua>
References: <200504051012.08157.vda@port.imtp.ilyichevsk.odessa.ua>
Message-ID: <20050508235856.GH29395@jm.kir.nu>

On Tue, Apr 05, 2005 at 10:12:08AM +0300, Denis Vlasenko wrote:

> # iwconfig wlan0 mode monitor
> # iwconfig wlan0 mode master
> 
> I see wlan0 emitting *IBSS* beacons!

> These beacons are invalid. TIM IE must exist only in ESS beacons,
> and IBSSparam only in IBSS. We have both! :)

This turned out to be the same firmware bug for which there was already
a workaround when moving from adhoc mode to master mode. I enabled the
same workaround for monitor->master mode case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 17:07:02 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 17:07:02 -0700
Subject: hostapd + madwifi + external RADIUS mac authenication ONLY
In-Reply-To: <200504221454.05450.chris.kearns@sybernet.ie>
References: <200504221454.05450.chris.kearns@sybernet.ie>
Message-ID: <20050509000702.GI29395@jm.kir.nu>

On Fri, Apr 22, 2005 at 02:54:05PM +0100, Chris Kearns wrote:

> I have spent many hours trying to get hostapd to authenticate client mac 
> addresses off an external RAIDUS server (WITHOUT using WEP or WPA), and have 
> had no success. I don't have access right now to the configuration files I 
> used, but what I would like to know is if anybody has been able to do this 
> with the madwifi driver?

This is not currently supported. madwifi driver takes care of all IEEE
802.11 authentication and association and the MAC address -based
authentication would be part of 802.11 authentication.. It should be
possible to make this work after association, but it may need some
changes in the driver and there would be a race condition with
authentication since hostapd would verify the MAC address only after the
data connection was already up. Better option would be to add new
mechanism for the driver to ask hostapd whether a given MAC address is
allowed to authenticate or not.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May  8 18:33:54 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 8 May 2005 18:33:54 -0700
Subject: [PATCH]: hostapd with madwifi accounting
In-Reply-To: <20041008060822.GA3384@informatik.uni-rostock.de>
References: <20041008060822.GA3384@informatik.uni-rostock.de>
Message-ID: <20050509013354.GJ29395@jm.kir.nu>

On Fri, Oct 08, 2004 at 08:08:22AM +0200, Gunter Burchardt wrote:

> Here are two patches to enable madwifi and hostapd to account station
> traffic. I added /proc/net/madwifi/athX/<station mac> to madwifi driver.
> Hostapd uses these files to get accounting information of a station. To
> use /proc/net/hostap/athX like as suggested in driver_madwifi.c is not
> good in my opinion. If hostap and madwifi driver is used together each
> driver can remove /proc/net/hostap if driver module is unloaded.
> 
> Secondly i added a (custom) netlink message with accounting information
> sent just before madwifi tells hostapd that a station leaves. This is
> nessesary because madwifi deletes procfs entry for the station before
> hostapd reads accounting information.

Thanks! I finally got a working madwifi AP setup running with WPA after
moving to BSD branch and I'm now able to test hostapd with madwifi. I
applied your patch for hostapd to enable RADIUS accounting with madwifi
driver and verified that it works with the netlink message. The procfs
information does not seem to be available from the driver, so interim
accounting messages are not currently supported.

-- 
Jouni Malinen                                            PGP id EFC895FA



From enoll1  Sun May  8 18:41:13 2005
From: enoll1 (Erich Noll)
Date: Sun, 8 May 2005 20:41:13 -0500 (GMT-05:00)
Subject: 16K stack kernel for FC3.91
Message-ID: <16877524.1115602873607.JavaMail.root@gonzo.psp.pas.earthlink.net>

Hello all,

I've got wpa_supplicant working well on my FC3 machine with a Netgear WG111T.  Now, I'm trying to get it working with Fedora Core (almost) 4, i.e. FC3.91 .  Does anyone know where I can get a trustworthy already genned kernel of level 2.6.11-1 or later with 16K stacks analogous to what Linuxant offers for FC3?  I've been trying for the last couple weeks to gen my own but keep running into a compile error on an I2C driver module I can't seem to .config out of the gen.

Thanks in advance and sorry for the slight off-topicity....

Erich Noll
enoll1-at-earthlink.net



From joba123  Sun May  8 23:22:30 2005
From: joba123 (J. =?iso-8859-15?q?Ball=E9?=)
Date: Mon, 9 May 2005 08:22:30 +0200
Subject: ipw2100 + wpa_supplicant setup
Message-ID: <200505090822.30790.joba123@jomp.net>

Hello,

I am trying to set up WPA on my wireless link (WEP works great with the same 
hard/software). It seems the connection is set up right, but then it is 
disconnected for some reason I can't figure out. I have the following 
components:

plain kernel 2.6.11.7 with software suspend 2 patches 2.1.8
wpa_supplicant 0.38
ipw2100 1.1.0 and firmware 1.3
LinkSys BEFW11S4 V4 with firmware 1.50.14
Intel 2100 3B

My wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=1
ap_scan=1
fast_reauth=1

network={
	ssid="LousbergWG"
	key_mgmt=WPA-PSK
	proto=WPA
	psk="... password ..."
	priority=1
}

[some other networks following here]

wpa_supplicant says this:

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
Own MAC address: 00:0c:f1:2c:71:26
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Starting AP scan (broadcast SSID)
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
Scan timeout - try to get results
Received 895 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:0c:41:7e:e8:0c ssid='LousbergWG' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:41:7e:e8:0c (SSID='LousbergWG' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=23
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:41:7e:e8:0c
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:41:7e:e8:0c
No keys have been configured - skip key clearing
Associated with 00:0c:41:7e:e8:0c
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 'eth1' added
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 00:0c:41:7e:e8:0c
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 34 7c 00 52 87 5d 6b 26 
60 0d 9d 35 41 ef e4 45 2d a3 88 85 4d 99 f3 65 ef de 22 37 9f 94 3f 24 46 8a 
80 5b 4c b4ca d5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 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
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 34 7c 00 52 87 
5d 6b 26 60 0d 9d 35 41 ef e4 45 2d a3 88 85 4d 99 f3 65 ef de 22 37 9f 94 3f 
24 46 8a 805b 4c b4 ca d5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 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 00:0c:41:7e:e8:0c (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): 71 96 28 bc 18 83 83 52 b7 2c 23 5e 17 
70 96 7e 4f 81 7f 16 09 82 a8 91 b9 91 5b 00 1b 03 83 ef
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 4a 87 2f c3 a9 d4 4a 05 a0 bb 56 e4 a6 
4d 99 df
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0c 41 7e e8 0c 00 0c f1 2c 71 26 
88 8e 01 03 00 77 fe 01 09 00 20 34 7c 00 52 87 5d 6b 26 71 96 28 bc 18 83 83 
52 b7 2c 23 5e 17 70 96 7e 4f 81 7f 16 09 82 a8 91 b9 91 5b 00 1b 03 83 ef 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 4a 87 2f c3 a9 d4 4a 05 a0 bb 56 e4 a6 4d 99 df 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 00:0c:41:7e:e8:0c
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 a4 93 00 52 87 5d 6b 
27 60 0d 9d 35 41 ef e4 45 2d a3 88 85 4d 99 f3 65 ef de 22 37 9f 94 3f 24 46 
8a 80 5b 4c b4 ca d5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 a6 da 41 81 ef 6f 8d b1 25 aa 05 f8 4f 
74 d7 d9 00 18 dd 16 00 50f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 
50 f2 02
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
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 01 c9 00 20 a4 93 00 52 
87 5d 6b 27 60 0d 9d 35 41 ef e4 45 2d a3 88 85 4d 99 f3 65 ef de 22 37 9f 94 
3f 24 46 8a 80 5b 4c b4 ca d5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a6 da 41 81 ef 6f 8d b1 25 aa 
05 f8 4f 74 d7 d9 00 18 dd16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 
01 00 00 50 f2 02
WPA: RX message 3 of 4-Way Handshake from 00:0c:41:7e:e8:0c (ver=1)
WPA: IE KeyData - 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: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 0c 41 7e e8 0c 00 0c f1 2c 71 26 
88 8e 01 03 00 5f fe 01 09 00 20 a4 93 00 52 87 5d 6b 27 71 96 28 bc 18 83 83 
52 b7 2c 23 5e 17 70 96 7e 4f 81 7f 16 09 82 a8 91 b9 91 5b 00 1b 03 83 ef 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 53 f9 26 03 a3 20 60 a9 6d a4 8d 0d cc 01 ce ec 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_ipw_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
RX EAPOL from 00:0c:41:7e:e8:0c
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 a4 93 00 52 87 5d 6b 
28 25 d3 bb 6f 67 84 06 64 11 4f 1e 21 22 ab 0f dd 3d 16 f2 dc bb 71 03 03 e3 
26 95 32 ee 40 a0 ae 9e 76 fd fc 80 57 f2 29 29 8d 88 17 ae 3a 14 94 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 1c 9d f8 f6 55 94 ba 3a 53 e4 5c f1 f8 
4b 43 8c 00 20 a5 17 cd 214a 73 cb 16 52 38 1e 64 96 9a bb 90 d1 eb 08 c4 d1 
e0 ce 2d df 21 1b 06 98 fb 99 f0
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=127
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 a4 93 00 52 
87 5d 6b 28 25 d3 bb 6f 67 84 06 64 11 4f 1e 21 22 ab 0f dd 3d 16 f2 dc bb 71 
03 03 e3 26 95 32 ee 40 a0 ae 9e 76 fd fc 80 57 f2 29 29 8d 88 17 ae 3a 14 94 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 9d f8 f6 55 94 ba 3a 53 e4 
5c f1 f8 4b 43 8c 00 20 a517 cd 21 4a 73 cb 16 52 38 1e 64 96 9a bb 90 d1 eb 
08 c4 d1 e0 ce 2d df 21 1b 06 98 fb 99 f0
WPA: RX message 1 of Group Key Handshake from 00:0c:41:7e:e8:0c (ver=1)
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_ipw_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 0c 41 7e e8 0c 00 0c f1 2c 71 26 
88 8e 01 03 00 5f fe 03 11 00 20 a4 93 00 52 87 5d 6b 28 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 85 2a 71 cd 6c d9 c3 29 b2 c4 31 07 c3 31 b5 f4 00 00
WPA: Key negotiation completed with 00:0c:41:7e:e8:0c [PTK=TKIP 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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
RX EAPOL from 00:0c:41:7e:e8:0c
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 b0 c3 00 52 87 5d 6b 
29 a5 9c 30 e4 14 a6 04 54 65 8e d3 9b d4 e4 6e 29 e6 9d 14 da 27 67 c7 a9 a4 
fd 10 fb 36 3a e4 8e af 4c 82 61 c1 c4 53 f6 3d e8 b8 17 f5 c4 3c b3 01 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 6a 6f 1d 59 b9 dd e2 4c a1 10 d0 8f 35 
51 4c 6d 00 20 a1 95 77 7b60 36 67 cb 51 bc 35 3e fc 5a ae ba 4b 97 d6 ad 2b 
a5 5f 8f da 40 e8 34 9e 73 ab 54
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=127
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 b0 c3 00 52 
87 5d 6b 29 a5 9c 30 e4 14 a6 04 54 65 8e d3 9b d4 e4 6e 29 e6 9d 14 da 27 67 
c7 a9 a4 fd 10 fb 36 3a e4 8e af 4c 82 61 c1 c4 53 f6 3d e8 b8 17 f5 c4 3c b3 
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6a 6f 1d 59 b9 dd e2 4c a1 10 
d0 8f 35 51 4c 6d 00 20 a195 77 7b 60 36 67 cb 51 bc 35 3e fc 5a ae ba 4b 97 
d6 ad 2b a5 5f 8f da 40 e8 34 9e 73 ab 54
WPA: RX message 1 of Group Key Handshake from 00:0c:41:7e:e8:0c (ver=1)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 01 00 00 00 00 00
wpa_driver_ipw_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 0c 41 7e e8 0c 00 0c f1 2c 71 26 
88 8e 01 03 00 5f fe 03 11 00 20 b0 c3 00 52 87 5d 6b 29 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 cb 01 41 9b 0e 29 62 54 71 e1 40 32 e8 d8 ca f4 00 00
WPA: Group rekeying completed with 00:0c:41:7e:e8:0c [GTK=TKIP]
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
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' 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:0c:41:7e:e8:0c 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_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=21 idleWhile=51
Starting AP scan (broadcast SSID)
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20 idleWhile=50
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=19 idleWhile=49
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=18 idleWhile=48
Scan timeout - try to get results
Received 679 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 1
0: 00:0c:41:7e:e8:0c ssid='LousbergWG' wpa_ie_len=24 rsn_ie_len=0
   skip - blacklisted
1: 00:12:17:b3:0b:d5 ssid='Uni-DSL.de Zugang 988' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:0f:66:a7:20:fc ssid='oecher' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
Selecting BSS from priority group 0
0: 00:0c:41:7e:e8:0c ssid='LousbergWG' wpa_ie_len=24 rsn_ie_len=0
   skip - blacklisted
1: 00:12:17:b3:0b:d5 ssid='Uni-DSL.de Zugang 988' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:0f:66:a7:20:fc ssid='oecher' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
No APs found - clear blacklist and try again
Removed BSSID 00:0c:41:7e:e8:0c from blacklist (clear)
Selecting BSS from priority group 1
0: 00:0c:41:7e:e8:0c ssid='LousbergWG' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:41:7e:e8:0c (SSID='LousbergWG' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:41:7e:e8:0c
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:41:7e:e8:0c
No keys have been configured - skip key clearing
Associated with 00:0c:41:7e:e8:0c
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 'eth1' added
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
Signal 2 received - terminating
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_ipw_set_wpa: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=0
wpa_driver_ipw_set_countermeasures: enabled=0

with ipw2100.ko debug = 7, I also get the following kernel messages:

May  8 20:51:20 joe kernel: ieee80211_crypt: registered algorithm 'TKIP'
May  8 20:51:27 joe kernel: ipw2100: U ipw2100_disable_adapter TODO: implement 
scan state machine
May  8 20:51:27 joe last message repeated 6 times
May  8 20:51:27 joe kernel: ipw2100: U ipw2100_set_scan_options enter
May  8 20:51:30 joe kernel: ipw2100: U ipw2100_disable_adapter TODO: implement 
scan state machine
May  8 20:51:30 joe last message repeated 3 times
May  8 20:51:31 joe kernel: ipw2100: I isr_indicate_associated eth1: 
Associated with 'LousbergWG' at 11Mbps, channel 10 (BSSID=00:0c:41:7e:e8:0c)
May  8 20:51:31 joe kernel: ipw2100: U ipw2100_wx_event_work Waking net queue.
May  8 20:51:31 joe kernel: ipw2100: U ipw2100_disable_adapter TODO: implement 
scan state machine
May  8 20:51:31 joe kernel: ipw2100: U ipw2100_disable_adapter TODO: implement 
scan state machine
May  8 20:51:31 joe kernel: ipw2100: U ipw2100_close enter
May  8 20:51:31 joe kernel: ipw2100: U ipw2100_close exit

I would really appreciate if someone could look into this, because I'm at the 
end of my knowledge.

Thanks

Johannes



From roby  Mon May  9 04:30:55 2005
From: roby (roby)
Date: Mon, 09 May 2005 13:30:55 +0200
Subject: Pre-Authentication with WPA.
Message-ID: <20050509113055.30886.qmail@webmaild.fe1.aruba.it>

Hello everybody, 

  I need your help..... Do anybody know if Pre-Authentication can work with 
WPA? 

  I have a small net with 2 APs based on Hostap. I'm using a 802.1x 
authentication system based on EAP-TLS and the authentication works fine. Do 
someone know how I have to set hostapd for make the pre-authentication 
works? 

Thanks for your kindness,
Regards
Roby.



From tim  Mon May  9 05:11:30 2005
From: tim (Tim Boneko)
Date: Mon, 09 May 2005 14:11:30 +0200
Subject: HostAP with ralink card - might it work?
In-Reply-To: <20050508062346.GN29395@jm.kir.nu>
References: <427A6C59.9070701@kiste> <20050508062346.GN29395@jm.kir.nu>
Message-ID: <427F5372.6080409@kiste>

Jouni Malinen schrieb:
> 
> What exactly are you trying to do and what do you mean with "HostAP" in
> this context?

Sorry for confusing this... I want to use the hostapd for authenticating 
my clients and setting up wpa encryption instead of wep. Hostapd is 
installed on my gateway pc (debian sarge), the clients are linux pcs and 
apples.
There?s no prism chipset available here, only ralink based cards. 
(802.11g based cards with kernel drivers are almost impossible to come 
by in germany)

It seems to me that i made the server and the client communicate about 
wpa keys, but hostapd didn?t keep the client from connecting despite an 
intentionally wrong key. (Does that sentence make sense? I?m not a 
native english speaker, if you didn?t already notice...)

Thanks for replying,

	timbo



From Victor.Wodecki  Mon May  9 17:32:59 2005
From: Victor.Wodecki (Wodecki, Victor Contractor)
Date: Tue, 10 May 2005 10:02:59 +0930
Subject: Possible fix for hostap on dual-slot sleeve iPaq
Message-ID: <37D1FAB2FA7B7E4993785B956F853C731815BC@ednex506.dsto.defence.gov.au>

This is related to the problem described at
http://lists.shmoo.com/pipermail/hostap/2005-April/009994.html

The scenario is when using hostap on an iPaq 5550, using a dual-slot
sleeve holding a D-Link DCF660W.

The symptom is numerous stalls when trying to use scp or any other
high data rate use of that interface.

After some amount of data, the card eventually goes from READY to
NOT READY, and doesn't return to READY without being reset.

The problem doesn't occur with single slot sleeves with part number
173396-001 but does occur in dual slot sleeves with part number
216198-B21.  And we have only today found that the problem also occurs
with new (?) model single slot sleeves with part number 249704-B22.

Experimentation has shown that getting the hostap driver to twiddle
its thumbs between reading hardware registers and writing hardware
registers in some particular circumstances avoids this problem.  A
patch for this is included below, comment welcome.  In effect, this
is a form of rate limiting, but the difference in throughput is quite
small, and the stability is vastly improved.

We have tested this patch on hostap 0.3.7 as well as 0.4.0, it applies
cleanly to both and has the desired effect on both.  Note that this
patch is additional to that shown in the above URL.

Testing has shown that it doesn't appear to be a power issue, and
given that the problem is observed on two models of the available
three different sleeve variants, the problem is most likely either
with the sleeves themselves, or with the sleeve driver.

The patch isn't perfect, it's really just a proof of concept that has
been tidied up.  The amount of time (microseconds) that the driver
twiddles its thumbs for is called 'twiddle'.  It defaults to 25
microseconds, but can be varied either by a procfs entry or via a
module parameter.

There is also an #ifdef to enable the patch; by default (at this stage)
it is enabled.

I welcome feedback from any hostap users using iPaq h5550.  I plan to
also post in the h5400-port mailing list at handhelds.org, but given
that this patch is in the hostap driver, I thought I'd start here.



Index: hostap_hw.c
===================================================================
--- hostap_hw.c	(revision 56)
+++ hostap_hw.c	(revision 64)
@@ -29,6 +29,20 @@
  *   (spin_lock_bh) to prevent concurrent use.
  */
 
+/*
+ * Enabling the following #define causes this driver to wait an
+ * arbitrary amount of time between reading and writing registers
+ * in some instances.  This avoids the problem of timeouts when
+ * using a Prism2-based card in a dual-slot sleeve on an iPaq 5500.
+ *
+ * The amount of time to wait (twiddle thumbs) is called 'twiddle',
+ * and can be specified either by module parameters or via
+ * /proc/net/hostap/twiddle
+ *
+ * The value is a number of microseconds; testing has shown that
+ * values in the range 10-30 work best.
+ */
+#define IPAQ_DUAL_SLEEVE
 
 #include <linux/config.h>
 #include <linux/version.h>
@@ -61,6 +75,13 @@
 MODULE_PARM(mtu, "i");
 MODULE_PARM_DESC(mtu, "Maximum transfer unit");
 
+#ifdef IPAQ_DUAL_SLEEVE
+static int twiddle = 25;
+MODULE_PARM(twiddle, "i");
+MODULE_PARM_DESC(twiddle, "Twiddle thumbs for N microseconds");
+static struct proc_dir_entry *twiddle_file;
+#endif
+
 static int channel[MAX_PARM_DEVICES] = { 3, DEF_INTS };
 MODULE_PARM(channel, PARM_MIN_MAX "i");
 MODULE_PARM_DESC(channel, "Initial channel");
@@ -1294,6 +1315,10 @@
 
 	PDEBUG(DEBUG_FLOW, "prism2_hw_init()\n");
 
+#ifdef IPAQ_DUAL_SLEEVE
+	printk(KERN_DEBUG "%s: twiddle=%d us\n", __FUNCTION__, twiddle);
+#endif
+
 	clear_bit(HOSTAP_BITS_TRANSMIT, &local->bits);
 
  init:
@@ -2060,6 +2085,7 @@
 		/* Internal BAP0 offset points to the byte following rxdesc;
 		 * copy rest of the data using bus master */
 		addr = virt_to_phys(skb_put(skb, len));
+
 		HFA384X_OUTW((addr & 0xffff0000) >> 16,
 			     HFA384X_PCI_M0_ADDRH_OFF);
 		HFA384X_OUTW(addr & 0x0000ffff, HFA384X_PCI_M0_ADDRL_OFF);
@@ -2097,6 +2123,9 @@
  rx_exit:
 	prism2_callback(local, PRISM2_CALLBACK_RX_END);
 	if (!rx_pending) {
+#ifdef IPAQ_DUAL_SLEEVE
+	        udelay (twiddle);
+#endif
 		HFA384X_OUTW(HFA384X_EV_RX, HFA384X_EVACK_OFF);
 	}
 
@@ -2366,6 +2395,9 @@
 	kfree(payload);
 
  fail:
+#ifdef IPAQ_DUAL_SLEEVE
+	udelay (twiddle);
+#endif
 	HFA384X_OUTW(HFA384X_EV_TX, HFA384X_EVACK_OFF);
 }
 
@@ -2552,6 +2584,9 @@
 	tasklet_schedule(&local->info_tasklet);
 
  out:
+#ifdef IPAQ_DUAL_SLEEVE
+	udelay (twiddle);
+#endif
 	HFA384X_OUTW(HFA384X_EV_INFO, HFA384X_EVACK_OFF);
 }
 
@@ -2687,6 +2722,9 @@
 	if (HFA384X_INW(HFA384X_SWSUPPORT0_OFF) != HFA384X_MAGIC) {
 		if (!local->hw_ready)
 			return;
+#ifdef IPAQ_DUAL_SLEEVE
+		udelay (twiddle);
+#endif
 		HFA384X_OUTW(0xffff, HFA384X_EVACK_OFF);
 		if (time_after(jiffies, last_magic_err + 10 * HZ)) {
 			printk("%s: Interrupt, but SWSUPPORT0 does not match: "
@@ -2731,6 +2769,9 @@
 	prism2_check_magic(local);
 
 	for (;;) {
+#ifdef IPAQ_DUAL_SLEEVE
+	        udelay (twiddle);
+#endif
 		ev = HFA384X_INW(HFA384X_EVSTAT_OFF);
 		if (ev == 0xffff) {
 			if (local->shutdown)
@@ -2773,12 +2814,18 @@
 				       !local->dev_enabled ?
 				       " (!dev_enabled)" : "");
 			}
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(ev, HFA384X_EVACK_OFF);
 			return IRQ_HANDLED;
 		}
 
 		if (ev & HFA384X_EV_TICK) {
 			prism2_ev_tick(dev);
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(HFA384X_EV_TICK, HFA384X_EVACK_OFF);
 		}
 
@@ -2799,6 +2846,9 @@
 
 		if (ev & HFA384X_EV_ALLOC) {
 			prism2_alloc_ev(dev);
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(HFA384X_EV_ALLOC, HFA384X_EVACK_OFF);
 		}
 
@@ -2806,18 +2856,27 @@
 		 * in tasklets. TX, TXEXC, RX, and INFO events will be ACKed
 		 * and unmasked after needed data has been read completely. */
 		if (ev & HFA384X_BAP0_EVENTS) {
+#ifdef IPAQ_DUAL_SLEEVE
+		        udelay (twiddle);
+#endif
 			hfa384x_events_no_bap0(dev);
 			tasklet_schedule(&local->bap_tasklet);
 		}
 
 #ifndef final_version
 		if (ev & HFA384X_EV_WTERR) {
+#ifdef IPAQ_DUAL_SLEEVE
+		        udelay (twiddle);
+#endif
 			PDEBUG(DEBUG_EXTRA, "%s: WTERR event\n", dev->name);
 			HFA384X_OUTW(HFA384X_EV_WTERR, HFA384X_EVACK_OFF);
 		}
 #endif /* final_version */
 
 		if (ev & HFA384X_EV_INFDROP) {
+#ifdef IPAQ_DUAL_SLEEVE
+		  	udelay (twiddle);
+#endif
 			prism2_infdrop(dev);
 			HFA384X_OUTW(HFA384X_EV_INFDROP, HFA384X_EVACK_OFF);
 		}
@@ -3203,6 +3262,46 @@
 }
 
 
+#ifndef PRISM2_NO_PROCFS_DEBUG
+#ifdef IPAQ_DUAL_SLEEVE
+static int proc_read_twiddle(char *page, char **start, off_t off, int count, int *eof, void *data)
+{
+        int len;
+
+	MOD_INC_USE_COUNT;
+	len = sprintf (page, "%d\n", twiddle);
+	MOD_DEC_USE_COUNT;
+
+	return len;
+}
+
+
+static int proc_write_twiddle(struct file *file, const char *buffer, unsigned long count, void *data)
+{
+#define TWIDDLELENGTH 20
+        char ourcopy [TWIDDLELENGTH + 1];
+	int len;
+
+	MOD_INC_USE_COUNT;
+	len = (count < TWIDDLELENGTH) ? count : TWIDDLELENGTH;
+	if (copy_from_user (ourcopy, buffer, len)) {
+	        MOD_DEC_USE_COUNT;
+		return -EFAULT;
+	}
+	ourcopy [len] = '\0';
+	twiddle = simple_strtol (ourcopy, NULL, 10);
+#undef TWIDDLELENGTH
+
+	printk(KERN_DEBUG "%s(): twiddle now %d\n", __FUNCTION__, twiddle);
+
+	MOD_DEC_USE_COUNT;
+
+	return len;
+}
+#endif /* IPAQ_DUAL_SLEEVE */
+#endif /* PRISM2_NO_PROCFS_DEBUG */
+
+
 static struct net_device *
 prism2_init_local_data(struct prism2_helper_functions *funcs, int card_idx)
 {
@@ -3386,6 +3485,14 @@
 #ifndef PRISM2_NO_PROCFS_DEBUG
 	create_proc_read_entry("registers", 0, local->proc,
 			       prism2_registers_proc_read, local);
+#ifdef IPAQ_DUAL_SLEEVE
+	twiddle_file = create_proc_entry("net/hostap/twiddle", 0644, local->proc);
+	if (twiddle_file) {
+	        twiddle_file->read_proc = proc_read_twiddle;
+		twiddle_file->write_proc = proc_write_twiddle;
+		twiddle_file->owner = THIS_MODULE;
+	}
+#endif /* IPAQ_DUAL_SLEEVE */
 #endif /* PRISM2_NO_PROCFS_DEBUG */
 
 	hostap_init_data(local);
@@ -3474,6 +3581,10 @@
 #ifndef PRISM2_NO_PROCFS_DEBUG
 	if (local->proc != NULL)
 		remove_proc_entry("registers", local->proc);
+#ifdef IPAQ_DUAL_SLEEVE
+	if (twiddle_file != NULL)
+	        remove_proc_entry("twiddle", twiddle_file);
+#endif /* IPAQ_DUAL_SLEEVE */
 #endif /* PRISM2_NO_PROCFS_DEBUG */
 	hostap_remove_proc(local);


-- 

This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the Crimes Act 1914.  If you have received this email in error, you are requested to contact the sender and delete the email.



From togg  Tue May 10 07:18:08 2005
From: togg (Sebastian Weitzel)
Date: Tue, 10 May 2005 16:18:08 +0200
Subject: wpa keyhandshake question/bug (patch)
Message-ID: <20050510161808.nujkrc1pvij488w8@webmail.togg.de>

> How often does this happen (e.g., percentage of attempts) and how much
> other traffic was being transmitted during reauthentication?

It is very noticable in an outdoor scenario with many accesspoints and 
many customers (about 10-20) connected to each ap. We have eap reauth 
interval set to 600 seconds in the outdoor scenario. I approx. it 
happens every second - to third reauth.

I changed my test scenario to eap-reauth interval of 30 seconds to 
reproduce this behaviour in indoor tests. I was able to reproduce when 
connecting just one client to a madwifi ap and doing some traffic 
(iperf or ping flood, but shaped to 3MBit e.g. is sufficient). I think 
prism is also hit by this issue.
> IEEE 802.11i-2004 does not use Group Key handshake directly after 4-Way
> Handshake; this mechanism is only used with WPA.. Are you talking about
> WPA or WPA2?

I am talking about and using WPA. I dont tested WPA2 yet, because I 
fear incompatibilities with windows clients.

> Yes, the first case should rely on lower layer retransmission. It might
> be useful to use a lower transmit rate and larger retry count for EAPOL
> frames in order to make them less likely to be dropped.

EAPOL packets are now (since some weeks) send with lowest rate in 
madwifi. But this doesnt fixed the issue, but may helped a bit.

> The AP will likely retransmit msg 3/4 if it does not receive msg 4/4.
> However, this msg 3/4 is using the old key (or plaintext for the first
> 4-Way Handshake). Drivers could make this more robust by storing the
> previously used key for short period of time after key change and trying
> to use it to decrypt packets that fail decryption with the new key. This
> would allow the retransmitted msg 3/4 to go through.

I also thought about modifying the driver but I came to the conclusion 
that this is not perfect because not always possible. I did a patch 
which hacks a bit in the EAPOL State machine regarding retries.

I changed it to the following: If the 4/4 packet from the sta is lost 
(I mean the AP has hit dot11RSNAConfigPairwiseUpdateCount) then I just 
force to assume 4/4 is received and continue in the state machine. This 
helped much in my scenario. And I dont see any side effects. If the 3/4 
did not reach the sta then
there develops a inconsistent state because the ap doesnt gets 4/4 from 
sta and assumes answer got lost and procedes (with setting the new 
key), but in my scenario at least this happens once in a hundred tries. 
If it happens the connection will reestablished in a few seconds.


-- 
Regards,
Sebastian Weitzel

-----
Anh?nge (Die Links sind bis zum December 1, 2005 g?ltig)
http://webmail.togg.de/imp/attachment.php?u=togg&t=1115741888&f=11.hostap-set-key.patch



From togg  Tue May 10 07:26:06 2005
From: togg (Sebastian Weitzel)
Date: Tue, 10 May 2005 16:26:06 +0200
Subject: wpa keyhandshake question/bug (patch2)
In-Reply-To: <20050510161808.nujkrc1pvij488w8@webmail.togg.de>
References: <20050510161808.nujkrc1pvij488w8@webmail.togg.de>
Message-ID: <20050510162606.zej14jimsw3ocgoc@webmail.togg.de>

The attachment was maybe a bit hidden in the last mail because I dont 
directly attach files to my mails anymore but instead link them (in the 
last line of the mail).

To be sure nobody misses this, here is the link :)

http://webmail.togg.de/imp/attachment.php?u=togg&t=1115741888&f=11.hostap-set-key.patch

-- 
Regards,
Sebastian Weitzel



From togg  Tue May 10 09:36:25 2005
From: togg (Sebastian Weitzel)
Date: Tue, 10 May 2005 18:36:25 +0200
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
Message-ID: <20050510183625.9p3oj3a1krtw48g4@webmail.togg.de>

Hi all,

severall users (e.g. 
http://thread.gmane.org/gmane.linux.drivers.hostap/10319) on the list 
reported a problem regarding SIOCGIWAP. Using madwifi (talking about 
the old cvs HEAD version).

It happens on authentication that shortly after associating to the ap a 
new wireless event annoucing a new ap occurs. The problem is that the 
mac of the ap is  bogus (00:00:00:00:00:00). In driver_wext.c there is 
a check for this bogus mac and therefore wpa_supplicant_event 
EVENT_DISASSOC is called. The problem here which I am pointing to is 
that the _current_ ap (wpa_s->bssid) is blacklisted, but instead the 
00:00:00:00:00:00 ap should be?

The other question is why the SIOCIWSCAN delivers a bogus ap, but that 
may be a madwifi fault. But wpa_supplicant should not blacklist the 
real ap but the bogus one.


-- 
Regards,
Sebastian Weitzel



From st3v3  Tue May 10 09:51:00 2005
From: st3v3 (Steve)
Date: Tue, 10 May 2005 17:51:00 +0100
Subject: compiling hostapd without EAP, with 802.1x
In-Reply-To: <20050507222905.GL29395@jm.kir.nu>
References: <1115293718.3263.8.camel@localhost.localdomain>
	<20050507222905.GL29395@jm.kir.nu>
Message-ID: <4280E674.1020708@btinternet.com>

Jouni Malinen wrote:

> I fixed this in CVS version by defining an
>empty inline function for the case when EAP is not included. This was
>forgotten from eap.h when the new function was added
>
Thanks for addressing this Jouni.
Can confirm compilation is ok now
Regards
Steve



From jv.suri  Wed May 11 01:56:53 2005
From: jv.suri (Suresh Babu)
Date: Wed, 11 May 2005 14:26:53 +0530
Subject: Hostapd segmentation fault
In-Reply-To: <000801c55605$a3278ab0$ac0aa8c0@sureshj>
References: <000801c55605$a3278ab0$ac0aa8c0@sureshj>
Message-ID: <35a277ac050511015625faa8e3@mail.gmail.com>

Hi all,
         I had got segmentation fault, when attempted to send Ctrl+C
to terminate the Hostapd. I am using madwifi-bsd latest version and
Hostapd 3 weeks old version. I could not debug to find where exactly
hostapd is giving segfault? and the log shows the same PC every time
it`s segfault.
           I`m attaching the log. can any body help to resolve this.
Thanx in advence.
Regards,
Suresh Babu
-------------- next part --------------
bash-2.05a# ./hostapd-1105-1 hostapd-wpa-psk-ccmp.conf
Configuration file: hostapd-wpa-psk-ccmp.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:03:7f:04:a1:52 and ssid 'suba'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=3
madwifi_configure_wpa: pairwise key ciphers=0x8
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x3
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 80 c3 ee 0e 60 21 51 45 ea fb d3 25 a4 1d 5a 53 3c 1a 92
08 cc 18 3a 59 76 14 38 78 d0 ec fd cd
GTK - hexdump(len=16): d1 04 fd 55 7c 9c a0 8a 4a b0 75 5b 77 12 79 5f
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=CCMP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
l2_packet_receive - recv: Network is down
ath0: creating bss 00:03:7f:04:a1:52
Wireless event: cmd=0x8b19 len=12
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:03:7f:05:02:35 IEEE 802.11: associated
  New STA
ath0: STA 00:03:7f:05:02:35 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:03:7f:05:02:35
ath0: STA 00:03:7f:05:02:35 WPA: start authentication
WPA: 00:03:7f:05:02:35 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:03:7f:05:02:35 key_idx=0
ath0: STA 00:03:7f:05:02:35 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:03:7f:05:02:35 authorized=0
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state IDLE
WPA: 00:03:7f:05:02:35 WPA_PTK entering state AUTHENTICATION
WPA: 00:03:7f:05:02:35 WPA_PTK entering state AUTHENTICATION2
WPA: 00:03:7f:05:02:35 WPA_PTK entering state INITPSK
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKSTART
ath0: STA 00:03:7f:05:02:35 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 77 1c 96 99 fa 54 ce 10 05 f8 5a 32 a6
 c2 ff 35 66 fd 31 78 2d 8b 51 ea bd cc 44 8a e6 de ee b5 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 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 123 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=119
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 76 59 fc 35 f7 8a 94 e4 34 db cd 56 43 ed 8f 15 a5 41 88
04 4e e1 10 20 6c 1c 5b 56 b6 b3 b9 b6
PTK - hexdump(len=64): 80 16 4e 86 69 5a 36 24 a4 af c7 ca 03 5d 4a 14 49 2f b0
b4 df 8c 7a fd e9 90 7e 1a 51 d5 0c 99 08 12 21 ce 1a 07 2e 1a fd 10 ec 17 e2 47
 51 6f f5 03 01 7f bf b2 e4 18 22 33 77 3d 6a 60 e6 f2
PMK - hexdump(len=32): 66 37 0f 77 73 8e 31 92 f0 fb 9b 12 8f f2 f8 5e f2 7f 2d
ec 19 1b 41 a4 8d ba 2c 20 46 9a bf e6
PTK - hexdump(len=64): 0b 58 bc eb 56 e5 f1 aa d3 df e4 96 22 d3 2a 0c a1 a0 d3
01 0e 3c 37 25 c8 24 84 54 8c 44 c8 9c ca e3 ed 77 0f 25 91 90 e2 b0 e1 8d c2 d4
 66 88 f5 c1 5a 00 d1 4d 13 54 fc 79 7d 4d 52 1d 31 63
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:03:7f:05:02:35 WPA: sending 3/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=137): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 01 ca 00 10 00 00 00 00 00 00 00 02 77 1c 96 99 fa 54 ce 10 05 f8 5a 32 a6
 c2 ff 35 66 fd 31 78 2d 8b 51 ea bd cc 44 8a e6 de ee b5 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 00 00 00 00 00 00 43 86
9b 6b ab 7d 61 83 7d 81 b2 36 26 39 68 da 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
IEEE 802.1X: 99 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=CCMP addr=00:03:7f:05:02:35 key_idx=0
ath0: STA 00:03:7f:05:02:35 IEEE 802.1X: authorizing port
madwifi_set_sta_authorized: addr=00:03:7f:05:02:35 authorized=1
madwifi_sta_clear_stats: addr=00:03:7f:05:02:35
ath0: STA 00:03:7f:05:02:35 WPA: pairwise key handshake completed (WPA)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:03:7f:05:02:35 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=24): d1 04 fd 55 7c 9c a0 8a 4a b0 75
 5b 77 12 79 5f 00 00 00 00 00 00 00 00
TX EAPOL - hexdump(len=137): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 03 92 00 10 00 00 00 00 00 00 00 03 77 1c 96 99 fa 54 ce 10 05 f8 5a 32 a6
 c2 ff 35 66 fd 31 78 2d 8b 51 ea bd cc 44 8a e6 de ee b4 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 00 00 00 00 00 00 64 a6
9e 48 7f 2b 88 08 86 4c 44 68 91 a1 41 22 00 18 cc da 0b 67 49 48 ff cc 11 4a 78
 36 35 e2 d0 c9 96 e8 35 c5 0f f9 8a a2
IEEE 802.1X: 99 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:03:7f:05:02:35 WPA: group key handshake completed (WPA)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state IDLE
Signal 2 received - terminating
Removing station 00:03:7f:05:02:35
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
Freeing RADIUS radius_client_deinit
madwifi_set_iface_flags: dev_up=0
bash-2.05a# ./hostapd-1105-1 hostapd-wpa-psk-ccmp.conf
Configuration file: hostapd-wpa-psk-ccmp.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:03:7f:04:a1:52 and ssid 'suba'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=3
madwifi_configure_wpa: pairwise key ciphers=0x8
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x3
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 94 44 d3 9c 21 68 74 13 8a b7 c8 ea 57 76 36 93 98 8a 8e
4a 80 55 8d ca 83 64 50 87 15 10 03 7b
GTK - hexdump(len=16): 65 62 c5 e9 14 ea d9 56 a2 77 69 5a 50 9e 37 22
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=CCMP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
l2_packet_receive - recv: Network is down
ath0: creating bss 00:03:7f:04:a1:52
Wireless event: cmd=0x8b19 len=12
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:03:7f:05:02:35 IEEE 802.11: associated
  New STA
ath0: STA 00:03:7f:05:02:35 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:03:7f:05:02:35
ath0: STA 00:03:7f:05:02:35 WPA: start authentication
WPA: 00:03:7f:05:02:35 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:03:7f:05:02:35 key_idx=0
ath0: STA 00:03:7f:05:02:35 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:03:7f:05:02:35 authorized=0
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state IDLE
WPA: 00:03:7f:05:02:35 WPA_PTK entering state AUTHENTICATION
WPA: 00:03:7f:05:02:35 WPA_PTK entering state AUTHENTICATION2
WPA: 00:03:7f:05:02:35 WPA_PTK entering state INITPSK
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKSTART
ath0: STA 00:03:7f:05:02:35 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e db 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 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 123 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=119
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 76 59 fc 35 f7 8a 94 e4 34 db cd 56 43 ed 8f 15 a5 41 88
04 4e e1 10 20 6c 1c 5b 56 b6 b3 b9 b6
PTK - hexdump(len=64): 8a 4e 44 19 09 f4 d2 f1 61 37 6e 3b af 2b 1e d5 20 cc 9c
0e a4 39 b5 75 9d f5 46 60 f8 b5 7d 6d a9 3d 69 12 69 76 2b 1c e5 2e 02 39 62 94
 a7 68 e3 45 17 ff bb 75 b0 bb 6b be 64 c1 12 1f 2a 09
PMK - hexdump(len=32): 66 37 0f 77 73 8e 31 92 f0 fb 9b 12 8f f2 f8 5e f2 7f 2d
ec 19 1b 41 a4 8d ba 2c 20 46 9a bf e6
PTK - hexdump(len=64): 68 f3 bf 77 a1 ff ee 19 d9 e7 a0 3f 65 f8 23 0c 44 53 14
21 5b e3 b4 d5 48 68 e8 ef 12 be 1a d3 25 01 0b 88 16 2e 7d d6 c0 3c 8e b7 d6 99
 5c f9 fe 03 c9 5c ba 5a 22 98 b6 ba 66 66 e9 6e 28 0f
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:03:7f:05:02:35 WPA: sending 3/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=137): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 01 ca 00 10 00 00 00 00 00 00 00 02 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e db 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 00 00 00 00 00 00 66 52
f1 13 c5 3d 4a 26 d2 4b de c4 3e 1f 77 c8 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
IEEE 802.1X: 99 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:03:7f:05:02:35 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=CCMP addr=00:03:7f:05:02:35 key_idx=0
ath0: STA 00:03:7f:05:02:35 IEEE 802.1X: authorizing port
madwifi_set_sta_authorized: addr=00:03:7f:05:02:35 authorized=1
madwifi_sta_clear_stats: addr=00:03:7f:05:02:35
ath0: STA 00:03:7f:05:02:35 WPA: pairwise key handshake completed (WPA)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:03:7f:05:02:35 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=24): 65 62 c5 e9 14 ea d9 56 a2 77 69
 5a 50 9e 37 22 00 00 00 00 00 00 00 00
TX EAPOL - hexdump(len=137): 00 03 7f 05 02 35 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 03 92 00 10 00 00 00 00 00 00 00 03 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e da 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 00 00 00 00 00 00 80 99
20 ac e8 f9 b7 5b a7 1a c7 6b 2d 25 72 ac 00 18 89 24 1e ff 77 2c 55 cc 2e ad 44
 2b 82 c1 6c bd bb 0f 2e 8b 2f be 2a c6
IEEE 802.1X: 99 bytes from 00:03:7f:05:02:35
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:03:7f:05:02:35 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:03:7f:05:02:35 WPA: group key handshake completed (WPA)
WPA: 00:03:7f:05:02:35 WPA_PTK_GROUP entering state IDLE
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:3d:e9:a6:56 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:3d:e9:a6:56 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:3d:e9:a6:56
ath0: STA 00:0f:3d:e9:a6:56 WPA: start authentication
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:3d:e9:a6:56 key_idx=0
ath0: STA 00:0f:3d:e9:a6:56 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:3d:e9:a6:56 authorized=0
WPA: 00:0f:3d:e9:a6:56 WPA_PTK_GROUP entering state IDLE
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state AUTHENTICATION
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state INITPSK
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:e9:a6:56 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 3d e9 a6 56 00 03 7f 04 a1 52 88 8e 01 03 00
5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e dc 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 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 123 bytes from 00:0f:3d:e9:a6:56
   IEEE 802.1X: version=1 type=3 length=119
ath0: STA 00:0f:3d:e9:a6:56 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 66 37 0f 77 73 8e 31 92 f0 fb 9b 12 8f f2 f8 5e f2 7f 2d
ec 19 1b 41 a4 8d ba 2c 20 46 9a bf e6
PTK - hexdump(len=64): 92 b3 71 dd 90 8d ab 65 0e ce 64 cd 76 15 8f ab 3a 64 aa
bd af 8c 64 6e fb 1f c5 a1 1c dd 80 a9 e5 22 dc 29 f5 08 82 23 d1 ea 55 1f f3 4c
 f7 dc c3 31 67 9d d0 74 e1 a2 f7 74 c8 ff 3d 04 d2 26
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:3d:e9:a6:56 WPA: sending 3/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=137): 00 0f 3d e9 a6 56 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 01 ca 00 10 00 00 00 00 00 00 00 02 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e dc 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 00 00 00 00 00 00 8d 63
cb c7 3a 81 a4 4c ae 10 6b 8c 65 9d c7 2a 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
IEEE 802.1X: 99 bytes from 00:0f:3d:e9:a6:56
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:3d:e9:a6:56 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:0f:3d:e9:a6:56 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=CCMP addr=00:0f:3d:e9:a6:56 key_idx=0
ath0: STA 00:0f:3d:e9:a6:56 IEEE 802.1X: authorizing port
madwifi_set_sta_authorized: addr=00:0f:3d:e9:a6:56 authorized=1
madwifi_sta_clear_stats: addr=00:0f:3d:e9:a6:56
ath0: STA 00:0f:3d:e9:a6:56 WPA: pairwise key handshake completed (WPA)
WPA: 00:0f:3d:e9:a6:56 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:3d:e9:a6:56 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=24): 65 62 c5 e9 14 ea d9 56 a2 77 69
 5a 50 9e 37 22 00 00 00 00 00 00 00 00
TX EAPOL - hexdump(len=137): 00 0f 3d e9 a6 56 00 03 7f 04 a1 52 88 8e 01 03 00
77 fe 03 92 00 10 00 00 00 00 00 00 00 03 69 1e 17 57 da 6f 72 16 75 99 8c 53 e3
 ff 11 60 99 73 59 ec 52 cd 0e 2d be 77 bf 0b 05 63 7e da 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 30 e7
d4 12 e0 10 a8 c5 da 29 f5 f5 00 94 15 f2 00 18 28 78 1c 74 2e b2 69 87 15 ae ac
 f1 a0 a9 d3 d5 35 42 ed 6d 3b ef a0 97
IEEE 802.1X: 99 bytes from 00:0f:3d:e9:a6:56
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:3d:e9:a6:56 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:0f:3d:e9:a6:56 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:0f:3d:e9:a6:56 WPA: group key handshake completed (WPA)
WPA: 00:0f:3d:e9:a6:56 WPA_PTK_GROUP entering state IDLE
Signal 2 received - terminating
Removing station 00:0f:3d:e9:a6:56
Removing station 00:03:7f:05!!!abort_handler addr = 0xc177503a, isr = 0x2, statu
s = 0x22a0
:02:35
Flushing old station entries
madwifi_sta_deauth: addr=fUnable to handle kernel NULL pointer dereference at vi
rtual address 0000003d
f:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
madpgd = c1ea4000
wifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
*pgd = 01f9d801, *pmd = 01f9d801, *pte = 00000000, *ppte = 00000000
Internal error: Oops: 0
CPU: 0
pc : [<c0040954>]    lr : [<c00402c4>]    Tainted: P
sp : c1dddd50  ip : 00000001  fp : c1dddd74
r10: 00000000  r9 : 20000013  r8 : 00000001
r7 : c1ddddac  r6 : ff00c020  r5 : c177503a  r4 : 00000002
r3 : ff00c014  r2 : 60000013  r1 : 22a00000  r0 : 00000000
Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 39FF  Table: 01EA4000  DAC: 00000015
Process hostapd-1105-1 (pid: 164, stackpage=c1ddd000)
Stack: (0xc1dddd40 to 0xc1dde000)
dd40: c00402c4 c0040954 00000013 ffffffff c00522a0 00000416 c1dddde0 c014fbc8
dd60: c177503a c1ddddac c1dddd84 c1dddd78 c003e29c c00408f8 c1dddda8 c1dddd88
dd80: c003e2e4 c003e274 ffffffff c1dddde0 c18b4000 00000000 c18b4000 c1ddde18
dda0: c1ddddac c00382a0 c003e2bc c18b4000 00009930 c18b4000 c3a56000 c18b567c
ddc0: c18b4000 c18b4000 00000000 c18b4000 c18b4000 00000000 c1ddde18 c1ddde1c
dde0: c1ddddf4 c3a35500 c3a20294 20000013 ffffffff c1ddde00 00000e52 c18b4000
de00: c18bae50 00000000 c18b4000 c1ddde70 c1ddde1c c3a32dc8 c3a354c8 c1ddde3c
de20: c1ddde2c 00000000 00000000 02000000 00000000 c18b4214 00000000 00000000
de40: 00000006 c1ddde70 00000e52 c18ba000 c18ba358 c18ba000 c18b4000 00000000
de60: c18ba140 c1dddea4 c1ddde74 c3a4a38c c3a32c44 c1ddde78 783a2065 00000003
de80: 00000004 c18ba358 c18c888c c1dddef4 c1ddc000 00000066 c1dddeec c1dddea8
dea0: c3a17118 c3a4a2c0 c3a105b0 c3a105b8 00000000 40017000 a0000013 00000000
dec0: c00c0528 40017021 00000000 00000000 c1dddf24 c3a19f28 c1dddef4 c18ba000
dee0: c1dddf20 c1dddef0 c00ed4e8 c3a16ff0 c3a50b48 8be00000 00000000 bffffdc8
df00: bffffdc8 00008be0 00000000 c1ddc000 c1dddf24 c1dddf68 c1dddf24 c00e716c
df20: c00ed238 61746830 00000000 00000000 00000000 00000003 00000004 00000000
df40: 00000000 00008be0 c0034b20 bffffdc8 00000003 ffffffe7 00000000 c1dddf78
df60: c1dddf6c c00de990 c00e6d6c c1dddfa4 c1dddf7c c00752b4 c00de974 0000004e
df80: 00000021 00000000 0004e508 00000003 00000036 c00387c4 00000000 c1dddfa8
dfa0: c0038620 c0075200 00000000 c003ddb0 00000003 00008be0 bffffdc8 00000000
dfc0: 00000000 0004e508 00000003 00000004 00000000 0004d734 00000000 00000000
dfe0: 0004dab4 bffffdc8 0002a97c 401d7594 60000010 00000003 00000000 00000000
Backtrace:
Function entered at [<c00408ec>] from [<c003e29c>]
 r8 = C1DDDDAC  r7 = C177503A  r6 = C014FBC8  r5 = C1DDDDE0
 r4 = 00000416
Function entered at [<c003e268>] from [<c003e2e4>]
Function entered at [<c003e2b0>] from [<c00382a0>]
 r8 = C18B4000  r7 = 00000000  r6 = C18B4000  r5 = C1DDDDE0
 r4 = FFFFFFFF
Function entered at [<c3a354bc>] from [<c3a32dc8>]
 r8 = C18B4000  r7 = 00000000  r6 = C18BAE50  r5 = C18B4000
 r4 = 00000E52
Function entered at [<c3a32c38>] from [<c3a4a38c>]
Function entered at [<c3a4a2b4>] from [<c3a17118>]
Function entered at [<c3a16fe4>] from [<c00ed4e8>]
Function entered at [<c00ed22c>] from [<c00e716c>]
Function entered at [<c00e6d60>] from [<c00de990>]
Function entered at [<c00de968>] from [<c00752b4>]
Function entered at [<c00751f4>] from [<c0038620>]
 r8 = C00387C4  r7 = 00000036  r6 = 00000003  r5 = 0004E508
 r4 = 00000000
Code: e1a01003 e14b32b2 ebfffe48 e3170b01 (1598303c)
Segmentation fault
bash-2.05a# cd /proc/



From Tilman.Schoop  Wed May 11 05:13:59 2005
From: Tilman.Schoop (Tilman Schoop)
Date: Wed, 11 May 2005 14:13:59 +0200
Subject: wpa_supplicant not connecting when AP powered off at startup
Message-ID: <4281F707.2020902@dsa-ac.de>

Hi all,

I have seen a problem with wpasupplicant that I want to tell you.
Perhaps anyone has an idea or I have a misunderstanding/wrong configuration.

first of all:
wpa_supplicant connects when the AP is visible/powered on

the problem:
when I power on the AP when wpa_supplicant is already running, the
authentication does not succeed. in this case, when I stop
wpa_supplicant and restart it again, authentication is directly done
and network is functional.

what I want to do:
EAP/TLS authentification + TKIP with DLink DWL-122 USB WLAN adapter
(ndiswrapper), AP cisco 1100, freeradius

my wpa_supplicant.conf:
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
        ssid="myessid"
        proto=WPA
        key_mgmt=WPA-EAP
        pairwise=TKIP
        group=TKIP
        eap=TLS
        identity="myid"
        ca_cert="/etc/certs/cacert.pem"
        private_key="/etc/certs/cert-clt.p12"
        private_key_passwd="secret"
        priority=1
}

I start wpa_supplicant with:
wpa_supplicant -dd -i wlan0 -c /etc/wpa_supplicant.conf -D ndiswrapper


Can anybody show me what I am doing wrong?

Greetings
Tilman

PS: I can provide the log files of success/no success



Tilman Schoop
tilman<punto>schoop<arroba>dsa-ac.de





From kevlar981  Wed May 11 19:07:19 2005
From: kevlar981 (Kev)
Date: Wed, 11 May 2005 19:07:19 -0700
Subject: messages
Message-ID: <1115863639.10939.233944378@webmail.messagingengine.com>

Hi Group,

Im using HOSTAP with a DLINK 520 card on a Gentoo server.

I would like if possible to move all debug messages out of the server
message log into a hostap specific log file,
so instead of hostap sending its logs to /var/log/messages could I set
it up to send to /var/log/hostap

Is this possible and if so how?

Thanks in advance.

Regards,
Kev



From lichiyu.cis89  Wed May 11 23:32:43 2005
From: lichiyu.cis89 (lichiyu)
Date: Thu, 12 May 2005 14:32:43 +0800
Subject: where can i find the source code of prism2_param?
Message-ID: <000b01c556bc$6757e0e0$d3a7718c@Howard>

Hi all:
I need the source code of prism2_param, because I have to use mipsel-linux-gcc to recompile prism2_param because of some experiment. 
But the prism2_param is a execution file in hostap utility package. So where can i find the source code of prism2_param?
Can somebody help me? All suggestions are welcome.

Thanks for your help,
Sincerly
Howard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050512/f9dea154/attachment.htm 


From s_manu25  Thu May 12 01:40:46 2005
From: s_manu25 (manisha r sankpal)
Date: 12 May 2005 08:40:46 -0000
Subject: No subject
Message-ID: <20050512084046.5001.qmail@webmail17.rediffmail.com>

Hi All,
 ?
I have made some changes in HostAP driver. If a station or AP is inactive for say 5 minutes it is automatically deleted from list that hostap keeps. this is provision provided by HostAP driver earlier. I just changed a code in order to reduce timing from 5 min to 1 sec. 

Consider a situation where WDS links are made between APs (say AP1 & AP2). AP1 is constantly listening to beacons from AP2 and updating its last received frame (last_rx)variable. I have written a timer which is invoked per second and compares current timing with last received beacon. If AP1 fails to listen beacons from AP2 in a second, it will automatically delete the entry of AP1 from its list by invoking timer handler (it's obivious).. 

while testing this code,I executed modified HostAP driver on AP1 & AP2. when I did "cardctl eject" on AP2, oops are generated and kernel panics.

The output of ksymoops is:
Unable to handle kernel paging request at virtual address c48656c0
c48656c0
*pde = 03da2067
Oops: 0000
CPU:    0
EIP:    0010:[<c48656c0>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: c02975b4  ebx: c11c7eec  ecx: c11c7ed0  edx: c02975b4
esi: c48656c0  edi: fffffffe  ebp: 00000046  esp: c0277f38
ds: 0018  es: 0018  ss: 0018
Process swapper (pid: 0, stackpage=c0277000)
Stack: c011ebd9 c11c7ed0 c0277f40 c0277f40 00000000 c028c730 fffffffe 00000046
      c011b362 c011b274 00000000 00000001 c011b083 c028c730 c028b900 00000000
      c023be38 c0277f98 c010857d c0105330 c0276000 c0276000 ffffe000 c010a9b8
Call Trace:    [<c011ebd9>] [<c011b362>] [<c011b274>] [<c011b083>] [<c010857d>]
  [<c0105330>] [<c010a9b8>] [<c0105330>] [<c0105353>] [<c01053f2>] [<c0105000>]
Code:  Bad EIP value.
                                                                                
                                                                                
>>EIP; c48656c0 <[hostap]prism2_rx_80211+160/500>  <=====
                                                                                
>>eax; c02975b4 <xtime+fb4/1514>
>>ebx; c11c7eec <_end+f10e6c/4548fe0>
>>ecx; c11c7ed0 <_end+f10e50/4548fe0>
>>edx; c02975b4 <xtime+fb4/1514>
>>esi; c48656c0 <[hostap]prism2_rx_80211+160/500>
>>esp; c0277f38 <init_task_union+1f38/f1f0>
                                                                                
Trace; c011ebd9 <del_timer+c39/e40>
Trace; c011b362 <tasklet_kill+92/c0>
Trace; c011b274 <__tasklet_hi_schedule+114/140>
Trace; c011b083 <do_softirq+93/a0>
Trace; c010857d <enable_irq+13d/140>
Trace; c0105330 <default_idle+0/e0>
Trace; c010a9b8 <disable_irq_nosync+1e18/3c70>
Trace; c0105330 <default_idle+0/e0>
Trace; c0105353 <default_idle+23/e0>
Trace; c01053f2 <default_idle+c2/e0>
Trace; c0105000 <empty_zero_page+1000/1310>
                                                                                
<0>Kernel panic: Aiee, killing interrupt handler!
  

What might go wrong with the code? 

Any clue would be appreciated. 

Thanks & regards,
Manisha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050512/c85b6c86/attachment.htm 


From brix  Thu May 12 02:27:01 2005
From: brix (Henrik Brix Andersen)
Date: Thu, 12 May 2005 11:27:01 +0200
Subject: where can i find the source code of prism2_param?
In-Reply-To: <000b01c556bc$6757e0e0$d3a7718c@Howard>
References: <000b01c556bc$6757e0e0$d3a7718c@Howard>
Message-ID: <1115890021.13444.2.camel@sponge.fungus>

On Thu, 2005-05-12 at 14:32 +0800, lichiyu wrote:
> I need the source code of prism2_param, because I have to use
> mipsel-linux-gcc to recompile prism2_param because of some
> experiment. 
> But the prism2_param is a execution file in hostap utility package. So
> where can i find the source code of prism2_param?
> Can somebody help me? All suggestions are welcome.

The prism2_param is a shell script, you already have the source code...

./Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050512/bd8c5bca/attachment.pgp 


From andreaf  Thu May 12 11:24:10 2005
From: andreaf (Andrea G Forte)
Date: Thu, 12 May 2005 14:24:10 -0400
Subject: promiscuous mode only, using hostAP.
Message-ID: <42839F4A.1070200@cs.columbia.edu>

Hi all,

I am writing a small sniffer with hostAP as wireless driver. My problem 
is that it seems that putting the interface wlan0 in promiscuous mode is 
not enough for sniffing packets. Do I have to put it the card in monitor 
mode as well? I know the wireless medium is half duplex, does this mean 
that promiscuous mode only won't work? Or is this a driver issue?
BTW when I set the flag for promiscuous mode I see the message in dmesg 
saying that the card entered promiscuous mode.
My firmware versions are:
NIC: v1.0.0
PRI: v1.1.1
STA: v1.7.4
I have seen other people posting about the same problem but they never 
got a response. Hopefully this time someone will have a solution! :)

Thank you,
Andrea




From mshib  Thu May 12 15:32:05 2005
From: mshib (M.Shibuya)
Date: Fri, 13 May 2005 07:32:05 +0900
Subject: Multiple interface available. (wpa_supplicant)
Message-ID: <200505122240.j4CMebNq065480@cds1.cds.ne.jp>

Hi, all.
I am using two atheros devices. driver is madwifi.
The problem by which authentification sequence is repeated by WPA-PSK by wpa_supplicant was solved.
It functions by any following methods.

	wpa_supplicant -B -c dev0.conf -iath0
	wpa_supplicant -B -c dev1.conf -iath1

	wpa_supplicant -B -c dev0.conf -iath0 -N -c dev1.conf -iath1

Useless code in the middle of DEBUG is also contained in attached patch.
It modified into the version which download(ed) from the project home page on May 12.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant_multiIF.patch
Type: application/octet-stream
Size: 2634 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050513/d32e8dec/attachment.obj 


From s_manu25  Fri May 13 00:08:38 2005
From: s_manu25 (manisha r sankpal)
Date: 13 May 2005 07:08:38 -0000
Subject: Kernel oops when cardctl eject
Message-ID: <20050513070838.22579.qmail@webmail18.rediffmail.com>

 ?Hi All,
  
I have made some changes in HostAP driver. If a station or AP is inactive for say 5 minutes it is automatically deleted from list that hostap keeps. this is provision provided by HostAP driver earlier. I just changed a code in order to reduce timing from 5 min to 1 sec. 

Consider a situation where WDS links are made between APs (say AP1 & AP2). AP1 is constantly listening to beacons from AP2 and updating its last received frame (last_rx)variable. I have written a timer which is invoked per second and compares current timing with last received beacon. If AP1 fails to listen beacons from AP2 in a second, it will automatically delete the entry of AP1 from its list by invoking timer handler (it's obivious).. 

while testing this code,I executed modified HostAP driver on AP1 & AP2. when I did "cardctl eject" on AP2, oops are generated and kernel panics.

The output of ksymoops is:
Unable to handle kernel paging request at virtual address c48656c0
c48656c0
*pde = 03da2067
Oops: 0000
CPU:    0
EIP:    0010:[<c48656c0>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: c02975b4  ebx: c11c7eec  ecx: c11c7ed0  edx: c02975b4
esi: c48656c0  edi: fffffffe  ebp: 00000046  esp: c0277f38
ds: 0018  es: 0018  ss: 0018
Process swapper (pid: 0, stackpage=c0277000)
Stack: c011ebd9 c11c7ed0 c0277f40 c0277f40 00000000 c028c730 fffffffe 00000046
      c011b362 c011b274 00000000 00000001 c011b083 c028c730 c028b900 00000000
      c023be38 c0277f98 c010857d c0105330 c0276000 c0276000 ffffe000 c010a9b8
Call Trace:    [<c011ebd9>] [<c011b362>] [<c011b274>] [<c011b083>] [<c010857d>]
  [<c0105330>] [<c010a9b8>] [<c0105330>] [<c0105353>] [<c01053f2>] [<c0105000>]
Code:  Bad EIP value.
                                                                                
                                                                                
>>EIP; c48656c0 <[hostap]prism2_rx_80211+160/500>  <=====
                                                                                
>>eax; c02975b4 <xtime+fb4/1514>
>>ebx; c11c7eec <_end+f10e6c/4548fe0>
>>ecx; c11c7ed0 <_end+f10e50/4548fe0>
>>edx; c02975b4 <xtime+fb4/1514>
>>esi; c48656c0 <[hostap]prism2_rx_80211+160/500>
>>esp; c0277f38 <init_task_union+1f38/f1f0>
                                                                                
Trace; c011ebd9 <del_timer+c39/e40>
Trace; c011b362 <tasklet_kill+92/c0>
Trace; c011b274 <__tasklet_hi_schedule+114/140>
Trace; c011b083 <do_softirq+93/a0>
Trace; c010857d <enable_irq+13d/140>
Trace; c0105330 <default_idle+0/e0>
Trace; c010a9b8 <disable_irq_nosync+1e18/3c70>
Trace; c0105330 <default_idle+0/e0>
Trace; c0105353 <default_idle+23/e0>
Trace; c01053f2 <default_idle+c2/e0>
Trace; c0105000 <empty_zero_page+1000/1310>
                                                                                
<0>Kernel panic: Aiee, killing interrupt handler!
  

What might go wrong with the code? 

Any clue would be appreciated. 

Thanks & regards,
Manisha






-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050513/1430fabd/attachment.htm 


From hiphin  Fri May 13 13:49:23 2005
From: hiphin (hiphin)
Date: Fri, 13 May 2005 22:49:23 +0200
Subject: hostap clients ?
Message-ID: <001b01c557fd$3e937240$0200a8c0@racunar02>

well I'm geting hostap frendly to me now, it is working for me fine since 0.1.12, now I use 3xhostap v3.7 in WDS as you know, I folow this mailing list for the past 2 years ... but ... (there goes part when I ask something)... I always get stanched width bridging.

this time clients are in bridge, and I did this

prism2_param wlan0 ap_bridge_packets to 0 (zero)

that is on hardware level, what is next step in disabling client bridging

can someone help me ? 

thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050513/7081baf4/attachment.htm 


From pjf  Fri May 13 14:30:45 2005
From: pjf (Pawel Foremski)
Date: Fri, 13 May 2005 23:30:45 +0200
Subject: Optional WPA and RSN
In-Reply-To: <20050508194856.GC29395@jm.kir.nu>
References: <200504211928.04021.pjf@asn.pl> <20050508194856.GC29395@jm.kir.nu>
Message-ID: <200505132330.45618.pjf@asn.pl>

On Sunday 08 May 2005 21:48, Jouni Malinen wrote:
> In order for this to work reliably with all client implementations, the
> AP would need to be sending out multiple beacon frames (one for each
> security mode; usually called "multiple BSSID" or "virtual AP").

For those not reading madwifi mailing lists, Sam Leffler has announced plans 
of support for multiple BSSIDs in net80211layer, what will _probably_ (my 
thought) lead to virtual AP support in mentioned driver:

http://www.freebsd.org/~sam/BSDCan2005.pdf

Yuppie! ;-)

Bye,

-- 
Pawel Foremski
pjf at asn.pl



From merci_danke  Sat May 14 09:01:22 2005
From: merci_danke (musta fatu)
Date: Sat, 14 May 2005 18:01:22 +0200 (CEST)
Subject: [HostAP ] procedure authentication and association mobile node by AP
Message-ID: <20050514160123.853.qmail@web26904.mail.ukl.yahoo.com>

Hi all hostap user,


I trying to simulate  sameless Handover mobile node
(layer 2) between 2 Access Point,

who has already  implemented this procedures (
authentication andassociation by basis station?

Please help me. I have am in urgent need of the idee
and algorithm for authentication and association.

Thank you very much for the consideration.

Thank you


	


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



From gdead  Sat May 14 18:25:55 2005
From: gdead (Bruce Potter)
Date: Sat, 14 May 2005 21:25:55 -0400
Subject: Troubleshooting list problem.. 
Message-ID: <6574C1C1-45CA-407A-81A9-B2AD865F0BCE@shmoo.com>

Howdy,
Please ignore this.. troubleshooting the list.

thanks

bruce



From j.antesberger  Sat May 14 21:58:53 2005
From: j.antesberger (Jochen Antesberger)
Date: Sat, 14 May 2005 23:58:53 -0500
Subject: Connection to DI-624 fails
Message-ID: <1116133133.5588.12.camel@localhost>

Hi,

I have a 3com Office Connect PC card (3CRSHW196, the one with the
retractable antenna). I'm trying to connect to a DLink router (DI-624)
using WPA-PSK but it won't work. I use the atmel driver from
sourceforge, the latest wpa enabled firmware and the supplicant from
debian testing. Kernel is 2.6.8 from debian. I've attached the the
output that I am getting.

If there is any additional information that you need please tell me so. 

Thanks,

Jochen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa.log
Type: text/x-log
Size: 4925 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050514/2c19342f/attachment.bin 


From benjcarson  Sat May 14 22:09:33 2005
From: benjcarson (Benj Carson)
Date: Sat, 14 May 2005 23:09:33 -0600
Subject: madwifi and wpa-psk problem
In-Reply-To: <200505061505.45184.benjcarson@digitaljunkies.ca>
References: <200505061505.45184.benjcarson@digitaljunkies.ca>
Message-ID: <200505142309.33629.benjcarson@digitaljunkies.ca>

Thanks Jouni, the latest CVS works perfectly.  FWIW I think am running the 
trunk version of madwifi (i.e. I co'd madwifi from 
cvs.sf.net:/cvsroot/madwifi).

(Sorry for the late reply, for some reason I haven't been receiving any mail 
from the list.)

Thanks again,


Benj Carson



From andreas  Sun May 15 10:38:47 2005
From: andreas (Andreas Fehr)
Date: Sun, 15 May 2005 19:38:47 +0200 (CEST)
Subject: problem starting wpa with ipw2200 from init script
Message-ID: <Pine.LNX.4.63.0505151927460.3234@ybpnyubfg.ybpnyqbznva>


Hi,

is it possible to search the mailing archive? I don't know whether 
somebody else run into my problem and solved it already.

wpa_supplicant works with my Fujitsu-Siemens P7020 if I start 
wpa_supplicant once the computer has booted. 

I don't get wpa_supplicant running if I run the same wpa_supplicant 
script during bootup of the computer. Sound strange to me.

My boot sequence is as follows:

1) start network script
2) run iwconfig
3) start wpa (with -w)
4) turn on my ipw2200 card (with the switch on the notebook)

I have no connection now

5) start the same wpa script again

Now, I have some connection to my network


Is -w the correct parameter for wpa_supplicant with this boot sequence? 
What might be wrong here?

If somebody has some information, I'll be glad for any pointer in the 
right direction.

Andreas



From frank  Sun May 15 13:47:27 2005
From: frank (Frank Thieme)
Date: Sun, 15 May 2005 22:47:27 +0200
Subject: automatic client configuration
Message-ID: <20050515204727.GA12307@stars.fthieme.net>

Hi,

I used wlan-ng for a long time now. The feature I really loved is that I
know how to configure the things each ap I want be attached to wants and
I can just go to the ap, switch my notebook on and I get all the
different configurations automatically.

I get my WEP key and static address at home, my WEP key and vpn tunnel
in university, dhcp addresses at work and so on.

Now there is a wlan in university demanding wpa authentication - thats
why I want to switch to hostap driver and wpa_supplicant. Would be a
good time to switch to wpa at home, too ;)

I'm looking for some howto or configuration examples to get these
automatic configuration with hostap driver. I have an Airrunner XI-300
(Prism2) pcmcia card firmware updated to 1.7.1.

Bye...Frank




From dimitris  Sun May 15 19:18:41 2005
From: dimitris (Dimitris Kogias)
Date: Sun, 15 May 2005 19:18:41 -0700
Subject: wpa_supplicant WPA-PSK pairwise OK, group fails
Message-ID: <42880301.9040908@gmail.com>

Hi everyone,

My setup:
Debian unstable distro.
Kernel 2.6.11.9 from kernel.org, all crypto modules built.
ipw2200 1.0.3
wpa_supplicant 0.4.0 (debian unstable package).
D-Link DWL-900AP+ access point configured for WPA-PSK.

wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="DLinkSucksAss"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk="my key"
        priority=2
}


Here's the first part of the wpa_supplicant run:



d at 0x19:/etc$ sudo wpa_supplicant -dd -ieth1 -Dipw -cwpa_supplicant.conf
Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'ipw'
Configuration file '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
Line: 23 - start of a new network block
ssid - hexdump_ascii(len=13):
     44 4c 69 6e 6b 53 75 63 6b 73 41 73 73            DLinkSucksAss
proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK (ASCII passphrase) - hexdump_ascii(len=24): [REMOVED]
priority=2 (0x2)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 2
   id=0 ssid='DLinkSucksAss'
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
ioctl[SIOCSIWPMKSA]: Operation not supported
Own MAC address: 00:12:f0:13:51:dc
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 1220 bytes of scan results (6 BSSes)
Scan results: 6
Selecting BSS from priority group 2
0: 00:40:05:5b:3f:34 ssid='DLinkSucksAss' wpa_ie_len=26 rsn_ie_len=0
caps=0x11
   selected
Trying to associate with 00:40:05:5b:3f:34 (SSID='DLinkSucksAss' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Wireless event: cmd=0x8b1a len=26
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:40:05:5b:3f:34
State: ASSOCIATING -> ASSOCIATED
Association event - clear replay counter
Associated to a new BSS: BSSID=00:40:05:5b:3f:34
No keys have been configured - skip key clearing
Associated with 00:40:05:5b:3f:34
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 'eth1' added
RX EAPOL from 00:40:05:5b:3f:34
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 01 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07 42 63 8e
9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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
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 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07
42 63 8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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:40:05:5b:3f:34 (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 79 15 aa 14 d9 21 81 31 f0 e3 2e
83 b4 04 fb 07 ba 1e fb 6f 07 f8 4f fc f8 3b 04 0b 3c d2 96 c1
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=137): 00 40 05 5b 3f 34 00 12 f0 13 51
dc 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 79 15 aa 14
d9 21 81 31 f0 e3 2e 83 b4 04 fb 07 ba 1e fb 6f 07 f8 4f fc f8 3b 04 0b
3c d2 96 c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 f0 dc 16 c4 5a fb cf 02 b1 74 17 0a
7c 21 4d 3a 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 00:40:05:5b:3f:34
RX EAPOL - hexdump(len=125): 01 03 00 79 fe 01 c9 00 20 00 00 00 00 00
00 00 02 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07 42 63
8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 bd ae 3f e5
bd 21 23 f0 2f 7b c8 e2 7f 2e ac 00 1a dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
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 c9 00 20 00 00
00 00 00 00 00 02 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25
07 42 63 8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 bd
ae 3f e5 bd 21 23 f0 2f 7b c8 e2 7f 2e ac 00 1a dd 18 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:40:05:5b:3f:34 (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 02 00 00
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=113): 00 40 05 5b 3f 34 00 12 f0 13 51
dc 88 8e 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 5e 25 b0 29 92 15 42 d2 ca 7c f5 85
88 20 ec d4 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_ipw_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE



At this point, I can ping other hosts on the WLAN (static IP, have
already ifconfig'd the interface and set default route).  However,
wpa_supplicant continues with:



Authentication with 00:40:05:5b:3f:34 timed out.
Added BSSID 00:40:05:5b:3f:34 into blacklist
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
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



And it keeps cycling for ever until Ctrl-C.

For the few seconds that, I presume, wpa_supplicant is trying to set up
the group keying, I have connectivity to the WLAN.  Also, the AP's log
says that my station has connected and authenticated successfully - I
suppose that reflects the end of the pairwise key setup.

While all of the above is going on, I see this in the kernel logs:

May 15 18:50:18 0x19 kernel: TKIP: replay detected:
STA=00:40:05:5b:3f:34 previous TSC 000000000000 received TSC 000000000000


Any ideas?

Thanks,

Dimitris.



From neenams  Mon May 16 00:25:27 2005
From: neenams (Neena M.S)
Date: Mon, 16 May 2005 12:55:27 +0530
Subject: Socket programming-select + raw_sock
Message-ID: <6aa356580505160025a595247@mail.gmail.com>

hi,
 i have a doubt? shall we use select function with raw_socket. Anybody
to help me?
thanks & regards
neena



From alfred.hitch  Mon May 16 02:39:59 2005
From: alfred.hitch (alfred hitch)
Date: Mon, 16 May 2005 05:39:59 -0400
Subject: porting to world radio chips from conexant
Message-ID: <29f91651050516023955da987a@mail.gmail.com>

Hi All,

I intend to port the wpa supplicant to conexant workd radio chips.
I have just started going thru the code and documentation, some
questions as of now if someone could help me with.

1) Has anyone already done this porting (I didnt see it mentioned in
the ported chipset list) ? anyone willing to share experience (if not
code) on same..

2) The current driver we have doesnt supports wireless extensions, so
I also intend to leave the driver that ways and map the stuff in wpa
supplicant driver file. README mentions that wireless extensions
support is optional, and I am inclined to believe so (for my good) 
-;) .
Anyone conform that there are no hidden surprises / pitfalls in not
using wireless extension calls ?

3) I could see api's for setting keys and other ie,.capability etc ..
from supplicant to driver,
but I some how missed where / how does the authentication /
association time handshake messages flow from driver to supplicant,
what all messages from driver I need to provide to supplicant ??

Please bear with me for some time as I am just starting and so some
questions might be a little dumb / beginner -;)

Cheers,
Alfred



From andreas  Mon May 16 07:02:23 2005
From: andreas (Andreas Fehr)
Date: Mon, 16 May 2005 16:02:23 +0200 (CEST)
Subject: problem starting wpa with ipw2200 from init script
In-Reply-To: <Pine.LNX.4.63.0505151927460.3234@ybpnyubfg.ybpnyqbznva>
References: <Pine.LNX.4.63.0505151927460.3234@ybpnyubfg.ybpnyqbznva>
Message-ID: <Pine.LNX.4.63.0505161558100.3404@ybpnyubfg.ybpnyqbznva>

On Sun, 15 May 2005, 19:38, Andreas Fehr (as AF) wrote:

>AF: is it possible to search the mailing archive? I don't know whether 
>AF: somebody else run into my problem and solved it already.
>AF: 
>AF: wpa_supplicant works with my Fujitsu-Siemens P7020 if I start 
>AF: wpa_supplicant once the computer has booted. 
>AF: 
>AF: I don't get wpa_supplicant running if I run the same wpa_supplicant 
>AF: script during bootup of the computer. Sound strange to me.
>AF: 
>AF: My boot sequence is as follows:
>AF: 
>AF: 1) start network script
>AF: 2) run iwconfig
>AF: 3) start wpa (with -w)
>AF: 4) turn on my ipw2200 card (with the switch on the notebook)
>AF: 
>AF: I have no connection now
>AF: 
>AF: 5) start the same wpa script again
>AF: 
>AF: Now, I have some connection to my network
>AF: 
>AF: 
>AF: Is -w the correct parameter for wpa_supplicant with this boot 
>AF: sequence? What might be wrong here?
>AF: 
>AF: If somebody has some information, I'll be glad for any pointer in 
>AF: the right direction.

Well, to make it more fun to debug, read the following.

As I'm able to get a wpa connection to my access point, as soon as I 
start the wpa script manually, I did some further test and guess what... 
as soon as I kill all the wpa entries from 'ps x', my wireless 
connection is even faster than before.

Sound more than strange to me. Any idea on that?



From gdead  Mon May 16 11:44:46 2005
From: gdead (Bruce Potter)
Date: Mon, 16 May 2005 14:44:46 -0400
Subject: Test - please ignore
Message-ID: <16B4FC89-D25F-4166-A652-C367F6238AD7@shmoo.com>

testing



From gdead  Mon May 16 17:32:12 2005
From: gdead (Bruce Potter)
Date: Mon, 16 May 2005 20:32:12 -0400
Subject: Test - pls ignore
Message-ID: <923E6B74-41F6-43D6-B735-84B024F65646@shmoo.com>

Testing.. pls ignore



From gdead  Mon May 16 17:39:38 2005
From: gdead (Bruce Potter)
Date: Mon, 16 May 2005 20:39:38 -0400
Subject: HostAP List problems - Fixed
Message-ID: <45D5C703-6BCF-41B6-B2D9-2EAD70A7D64A@shmoo.com>

Howdy,
Sorry bout the silence on the list.  The mail server hosting the  
HostAP list had some random message problem that caused the HostAP  
mail to wedge itself for the last few days.  Unfortunately, due to  
the volume of mail list traffic on the mail server, it was impossible  
to save the wedge messages while discarding the stuck message (we  
were never able to figure out which of the 1000's of messages was  
really "stuck"... go go gadget mailman debug messages).

Anyhoo, the moral of the story is:

If you sent a message to the list in the last week, you will need to  
resend as it was "lost"

I have a backup of the data, so if you really need something dug up,  
I can do it.  But it's best to assume it's lost if you can just resend.

I apologize for the outage folks.  We monitor our servers for  
availability, but not traffic on one list or another. I'm going to  
try and find a way to do that to make sure this doesn't happen in the  
future

we now return you to your regularly scheduled list.

later

bruce



From jkmaline  Mon May 16 19:39:05 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 16 May 2005 19:39:05 -0700
Subject: Messages to the list for the past ten or so days
Message-ID: <20050517023905.GB8114@jm.kir.nu>

Please note that I did not receive any messages from the Host AP mailing
list during the last ten days (last message I have is from Sat May 7th).
Some of the messages after this are in the web archives, but I'm likely
to be too lazy to start replying to them since I do not have the
original message in my mail folder.. In other words, if you think there
was something that I should really see and answer, please do re-send the
message. If sent twenty or so messages Fri/Sat (6th/7th May), but did
not receive all of them. They seem to be in the web archive, though, so
if you were waiting a reply at around that time, it may be available
there..

PS.

Thanks to Bruce Potter and whoever else was looking into getting the
list running. For some reason, I did not receive the "it's fixed"
message, but let's hope for the best that this message goes through.

-- 
Jouni Malinen                                            PGP id EFC895FA



From togg  Tue May 17 00:51:55 2005
From: togg (Sebastian Weitzel)
Date: Tue, 17 May 2005 09:51:55 +0200
Subject: wpa keyhandshake question/bug (patch)
Message-ID: <20050517095155.f0ivhzsfnrk84s44@webmail.togg.de>

> How often does this happen (e.g., percentage of attempts) and how much
> other traffic was being transmitted during reauthentication?

It is very noticable in an outdoor scenario with many accesspoints and 
many customers (about 10-20) connected to each ap. We have eap reauth 
interval set to 600 seconds in the outdoor scenario. I approx. it 
happens every second - to third reauth.

I changed my test scenario to eap-reauth interval of 30 seconds to 
reproduce this behaviour in indoor tests. I was able to reproduce when 
connecting just one client to a madwifi ap and doing some traffic 
(iperf or ping flood, but shaped to 3MBit e.g. is sufficient). I think 
prism is also hit by this issue.
> IEEE 802.11i-2004 does not use Group Key handshake directly after 4-Way
> Handshake; this mechanism is only used with WPA.. Are you talking about
> WPA or WPA2?

I am talking about and using WPA. I dont tested WPA2 yet, because I 
fear incompatibilities with windows clients.

> Yes, the first case should rely on lower layer retransmission. It might
> be useful to use a lower transmit rate and larger retry count for EAPOL
> frames in order to make them less likely to be dropped.

EAPOL packets are now (since some weeks) send with lowest rate in 
madwifi. But this doesnt fixed the issue, but may helped a bit.

> The AP will likely retransmit msg 3/4 if it does not receive msg 4/4.
> However, this msg 3/4 is using the old key (or plaintext for the first
> 4-Way Handshake). Drivers could make this more robust by storing the
> previously used key for short period of time after key change and trying
> to use it to decrypt packets that fail decryption with the new key. This
> would allow the retransmitted msg 3/4 to go through.

I also thought about modifying the driver but I came to the conclusion 
that this is not perfect because not always possible. I did a patch 
which hacks a bit in the EAPOL State machine regarding retries.

I changed it to the following: If the 4/4 packet from the sta is lost 
(I mean the AP has hit dot11RSNAConfigPairwiseUpdateCount) then I just 
force to assume 4/4 is received and continue in the state machine. This 
helped much in my scenario. And I dont see any side effects. If the 3/4 
did not reach the sta then
there develops a inconsistent state because the ap doesnt gets 4/4 from 
sta and assumes answer got lost and procedes (with setting the new 
key), but in my scenario at least this happens once in a hundred tries. 
If it happens the connection will reestablished in a few seconds.

(see the link in the last line to the attachment).

Regards,
Sebastian Weitzel

-----
Anh?nge (Die Links sind bis zum December 1, 2005 g?ltig)
http://webmail.togg.de/imp/attachment.php?u=togg&t=1115741888&f=11.hostap-set-key.patch



From togg  Tue May 17 00:54:23 2005
From: togg (Sebastian Weitzel)
Date: Tue, 17 May 2005 09:54:23 +0200
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
Message-ID: <20050517095423.hotwiq6lunwcswgw@webmail.togg.de>

Hi all,

This a resend of the message sent some days before. The ml seems to 
eaten the old and some other messages.

Several users (e.g. 
http://thread.gmane.org/gmane.linux.drivers.hostap/10319) on the list 
reported a problem regarding SIOCGIWAP. I am referring to using madwifi 
(old cvs HEAD version) here.

It happens on authentication that shortly after associating to the ap a 
new wireless event annoucing a new ap occurs. The problem is that the 
mac of the ap is  bogus (00:00:00:00:00:00). In driver_wext.c there is 
a check for this bogus mac and therefore wpa_supplicant_event 
EVENT_DISASSOC is called. The problem here which I am pointing to is 
that the _current_ ap (wpa_s->bssid) is blacklisted, but instead the 
00:00:00:00:00:00 ap should be?

The other question is why the SIOCIWSCAN delivers a bogus ap, but that 
may be a madwifi fault. But wpa_supplicant should not blacklist the 
real ap but the bogus one.


-- 
Regards,
Sebastian Weitzel




From Karl.Rothenhoefer  Tue May 17 02:04:50 2005
From: Karl.Rothenhoefer (=?iso-8859-1?Q?Karl_Rothenh=F6fer?=)
Date: Tue, 17 May 2005 11:04:50 +0200
Subject: hostap in SuSE9.2 - bridging and kernel production
Message-ID: <000501c55abf$7c6340e0$70c8a8c0@Gericomk>

Hello everybody,

recently I started migration of my WLAN-Network from SuSE 9.1 to 9.2 and I
experience some issues.

Issue 1: Bridging
============
Though in 9.1 I gained some experience with bridging, I fail to make it work
in 9.2.


The following are my commands:

sempron:~ # brctl addbr mybr
sempron:~ # brctl addif mybr eth0
sempron:~ # brctl addif mybr wlan0
sempron:~ # ifconfig eth0 0.0.0.0
sempron:~ # ifconfig wlan0 0.0.0.0
sempron:~ # ifconfig mybr 192.168.0.1 netmask 255.255.255.0 up

The following is, what I recorded with tail -f /var/log/messages

May 17 10:25:50 sempron ifup: No configuration found for mybr
May 17 10:25:57 sempron kernel: eth0: Promiscuous mode enabled.
May 17 10:25:57 sempron kernel: device eth0 entered promiscuous mode
May 17 10:26:04 sempron kernel: device wlan0 entered promiscuous mode
May 17 10:26:24 sempron kernel: eth0: Promiscuous mode enabled.
May 17 10:27:50 sempron kernel: mybr: no IPv6 routers present

So there is no indication of the learning phase of the bridge and no
indication of its transition to the forwarding state. After this the bridge
doesn't work.
In rare cases I saw the thing even work but without any reproducability and
with no evident explanation.

On another similar configuration, I see that the ethernet port enters
forwarding state but the wlan port still doesn't.

Latter experience made me question the status of the hostap-driver in SuSE
9.2 and they indicate a version 0.2.4-5 which I am currently using together
with Kernel version 2.6.8-24.14.

I therefore decided to go for a new kernel production with hostap version
0.3.7:

Issue 2: Kernel Production with hostap 0.3.7
================================
In following the README files for the kernel patches I wanted to apply the
patches for my kernel but the most recent patch availbale was
hostap-linux-2.6.2.patch. My understanding of its contents was not very
good, but nevertheless I tried to make some adaptations to my more recent
environment. Based on these adaptations I got the impression that I
successfully applied the patch. However the command make xconfig reveals
that no changes for the hostap options have been achieved.

Is there anybody who made simalar experience and could overcome it?
How can I solve the bridging issue?
How can I get/produce a better kernel patch?

Many thanks to everybody, who can help me to make progress after a couple of
unsuccessful days.

Many regards
Karl Rothenh?fer








From dan  Tue May 17 03:55:04 2005
From: dan (Dan Searle)
Date: Tue, 17 May 2005 11:55:04 +0100
Subject: promiscuous mode only, using hostAP.
In-Reply-To: <42839F4A.1070200@cs.columbia.edu>
References: <42839F4A.1070200@cs.columbia.edu>
Message-ID: <709916843.20050517115504@adelix.com>

Hi,

I'm not sure about the behavior of hostap exactly, but with 802.11 it
only makes sense to have an Access Point in promisc. mode.

Dan....

Thursday, May 12, 2005, 7:24:10 PM, you wrote:

> Hi all,

> I am writing a small sniffer with hostAP as wireless driver. My problem
> is that it seems that putting the interface wlan0 in promiscuous mode is
> not enough for sniffing packets. Do I have to put it the card in monitor
> mode as well? I know the wireless medium is half duplex, does this mean
> that promiscuous mode only won't work? Or is this a driver issue?
> BTW when I set the flag for promiscuous mode I see the message in dmesg
> saying that the card entered promiscuous mode.
> My firmware versions are:
> NIC: v1.0.0
> PRI: v1.1.1
> STA: v1.7.4
> I have seen other people posting about the same problem but they never
> got a response. Hopefully this time someone will have a solution! :)

> Thank you,
> Andrea

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


> This message has been scanned for viruses by MailController - www.MailController.altohiway.com


--

Dan Searle
Adelix Ltd
dan.searle at adelix.com web: www.adelix.com
tel: 0845 230 9590 / fax: 0845 230 9591 / support: 0845 230 9592
snail: The Old Post Office, Bristol Rd, Hambrook, Bristol BS16 1RY. UK.

Any views expressed in this email communication are those
of the individual sender, except where the sender specifically states
them to be the views of a member of Adelix Ltd.  Adelix Ltd. does not
represent, warrant or guarantee that the integrity of this communication
has been maintained nor that the communication is free of errors or
interference.




From togg  Tue May 17 04:34:34 2005
From: togg (Sebastian Weitzel)
Date: Tue, 17 May 2005 13:34:34 +0200
Subject: [PATCH]: hostapd with madwifi accounting
In-Reply-To: <20050509013354.GJ29395@jm.kir.nu>
References: <20041008060822.GA3384@informatik.uni-rostock.de>
	<20050509013354.GJ29395@jm.kir.nu>
Message-ID: <20050517133434.raidkoy34ny84wkg@webmail.togg.de>

> Thanks! I finally got a working madwifi AP setup running with WPA after
> moving to BSD branch and I'm now able to test hostapd with madwifi. I
> applied your patch for hostapd to enable RADIUS accounting with madwifi
> driver and verified that it works with the netlink message. The procfs
> information does not seem to be available from the driver, so interim
> accounting messages are not currently supported.

Hi Jouni,

please note that madwifi head cvs needs a patch to enable this procfs 
accounting hack. Its not nice and so in madwifi-bsd it's done via a 
accounting ioctl' (STA-TRAFFIC-STAT)

Do you see any problems with this? (Interim) Accounting works in my tests.


-- 
Regards,
Sebastian Weitzel



From deckrider  Tue May 17 05:31:00 2005
From: deckrider (David Everly)
Date: Tue, 17 May 2005 06:31:00 -0600
Subject: wpa_supplicant -Dhostap does not set restricted security mode
Message-ID: <20050517123100.GA26497@elbert.is-a-geek.org>

Hello,

Using the latest Debian/Sarge with their kernel-image-2.6.8-2-686,
related hostap-modules-2.6.8-2-686 (0.3.7-1), and wpasupplicant
(0.3.8-1) packages.

My wireless card is:

card "Linksys Instant Wireless Network PC Card ver.3"
   version "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA"
   manfid 0x0274, 0x1613

I can manually do the following to associate with the AP (the AP is
configured to require WEP shared key and does not broadcast its SSID):

iwconfig wlan0 essid "blah blah blah" \
               mode managed \
	       key restricted 00000000000000000000000000

However, with the following configurations, I cannot associate with the
AP using:

wpa_suppicant -D hostap \
              -i wlan0 \
	      -c /etc/wpa_supplicant.conf \
	      -w

/etc/wpa_supplicant.conf contains:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
        ssid="blah blah blah"
        key_mgmt=NONE
        wep_key0=00000000000000000000000000
        wep_tx_keyidx=0
        priority=5
        auth_alg=SHARED
}

Under this method, when I run 'iwconfig wlan0' I do see that the SSID is
set correctly, but it shows "Security mode:open", which is not correct.

I have also tried the orinoco_cs driver which works manually, but
doesn't even get as far as with the hostap_cs driver.

I am able to associate with this AP using similar configuration on a
different laptop that uses built in wireless requiring the ndiswrapper
driver.

Incidentally, I would like to vote for the following bug, since I have
several networks that do not broadcast their SSIDs:

   http://hostap.epitest.fi/bugz/show_bug.cgi?id=16

Thanks in advance,
Dave.

-- 
Encrypted Mail Preferred:
    Key ID:  8527B9AF
    Key Fingerprint:  E1B6 40B6 B73F 695E 0D3B  644E 6427 DD74 8527 B9AF
    Information:  http://www.gnupg.org/
                                                                                
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html
-------------- 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/20050517/88597aeb/attachment.pgp 


From jkmaline  Tue May 17 06:28:11 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 06:28:11 -0700
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
In-Reply-To: <20050517095423.hotwiq6lunwcswgw@webmail.togg.de>
References: <20050517095423.hotwiq6lunwcswgw@webmail.togg.de>
Message-ID: <20050517132811.GF8114@jm.kir.nu>

On Tue, May 17, 2005 at 09:54:23AM +0200, Sebastian Weitzel wrote:

> It happens on authentication that shortly after associating to the ap a 
> new wireless event annoucing a new ap occurs. The problem is that the 
> mac of the ap is  bogus (00:00:00:00:00:00). In driver_wext.c there is 
> a check for this bogus mac and therefore wpa_supplicant_event 
> EVENT_DISASSOC is called. The problem here which I am pointing to is 
> that the _current_ ap (wpa_s->bssid) is blacklisted, but instead the 
> 00:00:00:00:00:00 ap should be?

For me, this is not an association with a bogus AP BSSID, but a
disassociation from the current AP. If the driver is generating this
event in a case where it is not actually being disassociated/
deauthenticated, the driver should be fixed..

-- 
Jouni Malinen                                            PGP id EFC895FA



From aschlemm  Tue May 17 06:41:17 2005
From: aschlemm (Tony Schlemmer)
Date: Tue, 17 May 2005 08:41:17 -0500
Subject: problem starting wpa with ipw2200 from init script
In-Reply-To: <Pine.LNX.4.63.0505161558100.3404@ybpnyubfg.ybpnyqbznva>
References: <Pine.LNX.4.63.0505151927460.3234@ybpnyubfg.ybpnyqbznva>
	<Pine.LNX.4.63.0505161558100.3404@ybpnyubfg.ybpnyqbznva>
Message-ID: <200505170841.17723.aschlemm@comcast.net>

On Monday 16 May 2005 09:02, Andreas Fehr wrote:
> Well, to make it more fun to debug, read the following.
>
> As I'm able to get a wpa connection to my access point, as soon as I
> start the wpa script manually, I did some further test and guess what...
> as soon as I kill all the wpa entries from 'ps x', my wireless
> connection is even faster than before.
>
> Sound more than strange to me. Any idea on that?
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

How are you managing to startup the "wpa_supplicant" more than once? I admit 
had this problem under SuSE 9.2 as I startup the daemon through 
SuSE's /etc/sysconfig/network/if-up.d directory via a simple shell script. I  
have my startup script check if  the "wpa_supplicant" daemon is already 
running so the daemon only gets started once.

My Dell Inspiron 6000 laptop is rather odd with SuSE 9.2 as the WIFI interface 
doesn't come up on a set interface. Sometimes it comes up as eth0 and other 
times it comes up as eth1. I had to add some parsing of the output of 
"iwconfig" into my startup script so it can figure out which interface is the 
WIFI one. It's odd but may have something to do about saving power when the 
laptop isn't plugged in its power supply.

Under WinXP I get a message that the internal ethernet adapters was disabled 
when running on battery and I have no CAT-5 cable plugged in. When I plug the 
laptop in to the power supply I get another message telling me that the 
internal LAN adapter was been enabled.

Tony
 
-- 
Anthony  Schlemmer
aschlemm at comcast.net



From togg  Tue May 17 08:55:51 2005
From: togg (Sebastian Weitzel)
Date: Tue, 17 May 2005 17:55:51 +0200
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
Message-ID: <20050517175551.0pbx2co10o8os4os@webmail.togg.de>

> For me, this is not an association with a bogus AP BSSID, but a
> disassociation from the current AP. If the driver is generating this
> event in a case where it is not actually being disassociated/
> deauthenticated, the driver should be fixed..

Maybe http://article.gmane.org/gmane.linux.drivers.hostap/10487 
allready tried to patch this issue. I applied the patch and retested. 
It still dont solves the problem. As you can see the ifindex differs 
which should lead to reject this event, but does not.


ifi->ifi_index=6
drv->ifindex(8) != ifi->ifi_index(6), reject event
fromlen=12 addr=00:00:00:00:00:00
ifi->ifi_index=8
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:0b:6b:33:61:2e into blacklist
State: 4WAY_HANDSHAKE -> DISCONNECTED

I dont know yet why the wireless event still leads to blacklisting. 
Maybe the patch is incomplete.



-- 
Regards,
Sebastian Weitzel




From dimitris  Tue May 17 09:13:03 2005
From: dimitris (Dimitris Kogias)
Date: Tue, 17 May 2005 09:13:03 -0700
Subject: wpa_supplicant WPA-PSK pairwise OK, group fails
Message-ID: <428A180F.6090106@gmail.com>

[resend, caught in list problems]

Hi everyone,

My setup:
Debian unstable distro.
Kernel 2.6.11.9 from kernel.org, all crypto modules built.
ipw2200 1.0.3
wpa_supplicant 0.4.0 (debian unstable package).
D-Link DWL-900AP+ access point configured for WPA-PSK.

wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="DLinkSucksAss"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk="my key"
        priority=2
}


Here's the first part of the wpa_supplicant run:



d at 0x19:/etc$ sudo wpa_supplicant -dd -ieth1 -Dipw -cwpa_supplicant.conf
Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'ipw'
Configuration file '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
Line: 23 - start of a new network block
ssid - hexdump_ascii(len=13):
     44 4c 69 6e 6b 53 75 63 6b 73 41 73 73            DLinkSucksAss
proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK (ASCII passphrase) - hexdump_ascii(len=24): [REMOVED]
priority=2 (0x2)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 2
   id=0 ssid='DLinkSucksAss'
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
ioctl[SIOCSIWPMKSA]: Operation not supported
Own MAC address: 00:12:f0:13:51:dc
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 1220 bytes of scan results (6 BSSes)
Scan results: 6
Selecting BSS from priority group 2
0: 00:40:05:5b:3f:34 ssid='DLinkSucksAss' wpa_ie_len=26 rsn_ie_len=0
caps=0x11
   selected
Trying to associate with 00:40:05:5b:3f:34 (SSID='DLinkSucksAss' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Wireless event: cmd=0x8b1a len=26
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:40:05:5b:3f:34
State: ASSOCIATING -> ASSOCIATED
Association event - clear replay counter
Associated to a new BSS: BSSID=00:40:05:5b:3f:34
No keys have been configured - skip key clearing
Associated with 00:40:05:5b:3f:34
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 'eth1' added
RX EAPOL from 00:40:05:5b:3f:34
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 01 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07 42 63 8e
9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 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
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 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07
42 63 8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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:40:05:5b:3f:34 (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 79 15 aa 14 d9 21 81 31 f0 e3 2e
83 b4 04 fb 07 ba 1e fb 6f 07 f8 4f fc f8 3b 04 0b 3c d2 96 c1
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=137): 00 40 05 5b 3f 34 00 12 f0 13 51
dc 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 79 15 aa 14
d9 21 81 31 f0 e3 2e 83 b4 04 fb 07 ba 1e fb 6f 07 f8 4f fc f8 3b 04 0b
3c d2 96 c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 f0 dc 16 c4 5a fb cf 02 b1 74 17 0a
7c 21 4d 3a 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 00:40:05:5b:3f:34
RX EAPOL - hexdump(len=125): 01 03 00 79 fe 01 c9 00 20 00 00 00 00 00
00 00 02 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25 07 42 63
8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 bd ae 3f e5
bd 21 23 f0 2f 7b c8 e2 7f 2e ac 00 1a dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
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 c9 00 20 00 00
00 00 00 00 00 02 ee 60 69 b3 aa 3d 1b a6 7e 3c 14 3d 31 7f ce 23 61 25
07 42 63 8e 9e c9 8b 4c 55 f1 cd 59 32 b9 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 bd
ae 3f e5 bd 21 23 f0 2f 7b c8 e2 7f 2e ac 00 1a dd 18 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:40:05:5b:3f:34 (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 02 00 00
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=113): 00 40 05 5b 3f 34 00 12 f0 13 51
dc 88 8e 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 5e 25 b0 29 92 15 42 d2 ca 7c f5 85
88 20 ec d4 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_ipw_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE



At this point, I can ping other hosts on the WLAN (static IP, have
already ifconfig'd the interface and set default route).  However,
wpa_supplicant continues with:



Authentication with 00:40:05:5b:3f:34 timed out.
Added BSSID 00:40:05:5b:3f:34 into blacklist
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
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



And it keeps cycling for ever until Ctrl-C.

For the few seconds that, I presume, wpa_supplicant is trying to set up
the group keying, I have connectivity to the WLAN.  Also, the AP's log
says that my station has connected and authenticated successfully - I
suppose that reflects the end of the pairwise key setup.

While all of the above is going on, I see this in the kernel logs:

May 15 18:50:18 0x19 kernel: TKIP: replay detected:
STA=00:40:05:5b:3f:34 previous TSC 000000000000 received TSC 000000000000


Any ideas?

Thanks,

Dimitris.




From sree_raju  Tue May 17 09:28:29 2005
From: sree_raju (Sreedhar .M)
Date: 17 May 2005 16:28:29 -0000
Subject: Socket programming-select + raw_sock
Message-ID: <20050517162829.11521.qmail@webmail9.rediffmail.com>

 ?

Helloo

u cant use the the raw socket for select system call

Raw socket only for live packets .

regards
sreedhar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050517/801acb35/attachment.htm 


From mshib  Tue May 17 11:07:22 2005
From: mshib (M.Shibuya)
Date: Wed, 18 May 2005 03:07:22 +0900
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
In-Reply-To: <20050517175551.0pbx2co10o8os4os@webmail.togg.de>
References: <20050517175551.0pbx2co10o8os4os@webmail.togg.de>
Message-ID: <200505171816.j4HIG276090923@cds1.cds.ne.jp>

Hi, Sebastian.

On Tue, 17 May 2005 17:55:51 +0200
Sebastian Weitzel <togg at togg.de> wrote:
> 
> ifi->ifi_index=6
> drv->ifindex(8) != ifi->ifi_index(6), reject event
> fromlen=12 addr=00:00:00:00:00:00
> ifi->ifi_index=8
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00

Considering this Log, since ifi_index is in agreement, event seems not to throw away.
How about investigating the generating situation of beacon miss by athstats?

Bye, M.shibuya



From ardoaamch  Tue May 17 11:51:48 2005
From: ardoaamch (Adam Roach)
Date: Tue, 17 May 2005 13:51:48 -0500
Subject: Symbol Spectrum24 High Rate
Message-ID: <25e854e7050517115137c4d769@mail.gmail.com>

I have a Symbol Spectrum24 High Rate LA4137 wireless lan card.  I was
wondering if this is what I need to be using to get it working.
-- 
-Adam Michael Roach



From j.antesberger  Tue May 17 14:15:29 2005
From: j.antesberger (Jochen Antesberger)
Date: Tue, 17 May 2005 16:15:29 -0500
Subject: Connection to DI-624 fails
In-Reply-To: <1116133133.5588.12.camel@localhost>
References: <1116133133.5588.12.camel@localhost>
Message-ID: <1116364529.4753.4.camel@localhost>

I forgot to include my config file. Also it would be nice to hear if
anyone was successfully connecting to a DI-624, possibly even with a
3com card.

Here the config:
-----
# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel'
group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
#
# home network; allow all valid ciphers
network={
        ssid="ROUTER-ID"
        scan_ssid=1
        key_mgmt=WPA-PSK
        psk="test0815"
        }
-----

> Hi,
> 
> I have a 3com Office Connect PC card (3CRSHW196, the one with the
> retractable antenna). I'm trying to connect to a DLink router (DI-624)
> using WPA-PSK but it won't work. I use the atmel driver from
> sourceforge, the latest wpa enabled firmware and the supplicant from
> debian testing. Kernel is 2.6.8 from debian. I've attached the the
> output that I am getting.
> 
> If there is any additional information that you need please tell me so. 

-- 
Jochen Antesberger
jochen at antesberger.org    ----    ja3k5 at mizzou.edu




From vlad  Tue May 17 14:25:06 2005
From: vlad (vlad bis)
Date: Wed, 18 May 2005 00:25:06 +0300
Subject: tx_timeout problem
Message-ID: <146553738.20050518002506@bis.net.ua>

I have two routers with Fedora3 and Z-COM XI-626 cards.
There are two points in Ad-Hoc mode with the same servers and 6 miles between them.
If I use full channel speed (450 kb/s) one of the router very often looks like
this: "tx_timeout, hostap is restarting" and no more.. The server is
down. What can I do ? May be use AP mode for link ? Sorry for my
english.  USSR


mail to : vlad at bis.net.ua




From Victor.Wodecki  Tue May 17 18:07:06 2005
From: Victor.Wodecki (Wodecki, Victor Contractor)
Date: Wed, 18 May 2005 10:37:06 +0930
Subject: Possible fix for hostap on dual-slot sleeve iPaq
Message-ID: <37D1FAB2FA7B7E4993785B956F853C731815DA@ednex506.dsto.defence.gov.au>

[This is a repost, due to the recent mailing list problems]


This is related to the problem described at
http://lists.shmoo.com/pipermail/hostap/2005-April/009994.html

The scenario is when using hostap on an iPaq 5550, using a dual-slot
sleeve holding a D-Link DCF660W.

The symptom is numerous stalls when trying to use scp or any other
high data rate use of that interface.

After some amount of data, the card eventually goes from READY to
NOT READY, and doesn't return to READY without being reset.

The problem doesn't occur with single slot sleeves with part number
173396-001 but does occur in dual slot sleeves with part number
216198-B21.  And we have only today found that the problem also occurs
with new (?) model single slot sleeves with part number 249704-B22.

Experimentation has shown that getting the hostap driver to twiddle
its thumbs between reading hardware registers and writing hardware
registers in some particular circumstances avoids this problem.  A
patch for this is included below, comment welcome.  In effect, this
is a form of rate limiting, but the difference in throughput is quite
small, and the stability is vastly improved.

We have tested this patch on hostap 0.3.7 as well as 0.4.0, it applies
cleanly to both and has the desired effect on both.  Note that this
patch is additional to that shown in the above URL.

Testing has shown that it doesn't appear to be a power issue, and
given that the problem is observed on two models of the available
three different sleeve variants, the problem is most likely either
with the sleeves themselves, or with the sleeve driver.

The patch isn't perfect, it's really just a proof of concept that has
been tidied up.  The amount of time (microseconds) that the driver
twiddles its thumbs for is called 'twiddle'.  It defaults to 25
microseconds, but can be varied either by a procfs entry or via a
module parameter.

There is also an #ifdef to enable the patch; by default (at this stage)
it is enabled.

I welcome feedback from any hostap users using iPaq h5550.  I plan to
also post in the h5400-port mailing list at handhelds.org, but given
that this patch is in the hostap driver, I thought I'd start here.



Index: hostap_hw.c
===================================================================
--- hostap_hw.c	(revision 56)
+++ hostap_hw.c	(revision 64)
@@ -29,6 +29,20 @@
  *   (spin_lock_bh) to prevent concurrent use.
  */
 
+/*
+ * Enabling the following #define causes this driver to wait an
+ * arbitrary amount of time between reading and writing registers
+ * in some instances.  This avoids the problem of timeouts when
+ * using a Prism2-based card in a dual-slot sleeve on an iPaq 5500.
+ *
+ * The amount of time to wait (twiddle thumbs) is called 'twiddle',
+ * and can be specified either by module parameters or via
+ * /proc/net/hostap/twiddle
+ *
+ * The value is a number of microseconds; testing has shown that
+ * values in the range 10-30 work best.
+ */
+#define IPAQ_DUAL_SLEEVE
 
 #include <linux/config.h>
 #include <linux/version.h>
@@ -61,6 +75,13 @@
 MODULE_PARM(mtu, "i");
 MODULE_PARM_DESC(mtu, "Maximum transfer unit");
 
+#ifdef IPAQ_DUAL_SLEEVE
+static int twiddle = 25;
+MODULE_PARM(twiddle, "i");
+MODULE_PARM_DESC(twiddle, "Twiddle thumbs for N microseconds");
+static struct proc_dir_entry *twiddle_file;
+#endif
+
 static int channel[MAX_PARM_DEVICES] = { 3, DEF_INTS };
 MODULE_PARM(channel, PARM_MIN_MAX "i");
 MODULE_PARM_DESC(channel, "Initial channel");
@@ -1294,6 +1315,10 @@
 
 	PDEBUG(DEBUG_FLOW, "prism2_hw_init()\n");
 
+#ifdef IPAQ_DUAL_SLEEVE
+	printk(KERN_DEBUG "%s: twiddle=%d us\n", __FUNCTION__, twiddle);
+#endif
+
 	clear_bit(HOSTAP_BITS_TRANSMIT, &local->bits);
 
  init:
@@ -2060,6 +2085,7 @@
 		/* Internal BAP0 offset points to the byte following rxdesc;
 		 * copy rest of the data using bus master */
 		addr = virt_to_phys(skb_put(skb, len));
+
 		HFA384X_OUTW((addr & 0xffff0000) >> 16,
 			     HFA384X_PCI_M0_ADDRH_OFF);
 		HFA384X_OUTW(addr & 0x0000ffff, HFA384X_PCI_M0_ADDRL_OFF);
@@ -2097,6 +2123,9 @@
  rx_exit:
 	prism2_callback(local, PRISM2_CALLBACK_RX_END);
 	if (!rx_pending) {
+#ifdef IPAQ_DUAL_SLEEVE
+	        udelay (twiddle);
+#endif
 		HFA384X_OUTW(HFA384X_EV_RX, HFA384X_EVACK_OFF);
 	}
 
@@ -2366,6 +2395,9 @@
 	kfree(payload);
 
  fail:
+#ifdef IPAQ_DUAL_SLEEVE
+	udelay (twiddle);
+#endif
 	HFA384X_OUTW(HFA384X_EV_TX, HFA384X_EVACK_OFF);
 }
 
@@ -2552,6 +2584,9 @@
 	tasklet_schedule(&local->info_tasklet);
 
  out:
+#ifdef IPAQ_DUAL_SLEEVE
+	udelay (twiddle);
+#endif
 	HFA384X_OUTW(HFA384X_EV_INFO, HFA384X_EVACK_OFF);
 }
 
@@ -2687,6 +2722,9 @@
 	if (HFA384X_INW(HFA384X_SWSUPPORT0_OFF) != HFA384X_MAGIC) {
 		if (!local->hw_ready)
 			return;
+#ifdef IPAQ_DUAL_SLEEVE
+		udelay (twiddle);
+#endif
 		HFA384X_OUTW(0xffff, HFA384X_EVACK_OFF);
 		if (time_after(jiffies, last_magic_err + 10 * HZ)) {
 			printk("%s: Interrupt, but SWSUPPORT0 does not match: "
@@ -2731,6 +2769,9 @@
 	prism2_check_magic(local);
 
 	for (;;) {
+#ifdef IPAQ_DUAL_SLEEVE
+	        udelay (twiddle);
+#endif
 		ev = HFA384X_INW(HFA384X_EVSTAT_OFF);
 		if (ev == 0xffff) {
 			if (local->shutdown)
@@ -2773,12 +2814,18 @@
 				       !local->dev_enabled ?
 				       " (!dev_enabled)" : "");
 			}
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(ev, HFA384X_EVACK_OFF);
 			return IRQ_HANDLED;
 		}
 
 		if (ev & HFA384X_EV_TICK) {
 			prism2_ev_tick(dev);
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(HFA384X_EV_TICK, HFA384X_EVACK_OFF);
 		}
 
@@ -2799,6 +2846,9 @@
 
 		if (ev & HFA384X_EV_ALLOC) {
 			prism2_alloc_ev(dev);
+#ifdef IPAQ_DUAL_SLEEVE
+			udelay (twiddle);
+#endif
 			HFA384X_OUTW(HFA384X_EV_ALLOC, HFA384X_EVACK_OFF);
 		}
 
@@ -2806,18 +2856,27 @@
 		 * in tasklets. TX, TXEXC, RX, and INFO events will be ACKed
 		 * and unmasked after needed data has been read completely. */
 		if (ev & HFA384X_BAP0_EVENTS) {
+#ifdef IPAQ_DUAL_SLEEVE
+		        udelay (twiddle);
+#endif
 			hfa384x_events_no_bap0(dev);
 			tasklet_schedule(&local->bap_tasklet);
 		}
 
 #ifndef final_version
 		if (ev & HFA384X_EV_WTERR) {
+#ifdef IPAQ_DUAL_SLEEVE
+		        udelay (twiddle);
+#endif
 			PDEBUG(DEBUG_EXTRA, "%s: WTERR event\n", dev->name);
 			HFA384X_OUTW(HFA384X_EV_WTERR, HFA384X_EVACK_OFF);
 		}
 #endif /* final_version */
 
 		if (ev & HFA384X_EV_INFDROP) {
+#ifdef IPAQ_DUAL_SLEEVE
+		  	udelay (twiddle);
+#endif
 			prism2_infdrop(dev);
 			HFA384X_OUTW(HFA384X_EV_INFDROP, HFA384X_EVACK_OFF);
 		}
@@ -3203,6 +3262,46 @@
 }
 
 
+#ifndef PRISM2_NO_PROCFS_DEBUG
+#ifdef IPAQ_DUAL_SLEEVE
+static int proc_read_twiddle(char *page, char **start, off_t off, int count, int *eof, void *data)
+{
+        int len;
+
+	MOD_INC_USE_COUNT;
+	len = sprintf (page, "%d\n", twiddle);
+	MOD_DEC_USE_COUNT;
+
+	return len;
+}
+
+
+static int proc_write_twiddle(struct file *file, const char *buffer, unsigned long count, void *data)
+{
+#define TWIDDLELENGTH 20
+        char ourcopy [TWIDDLELENGTH + 1];
+	int len;
+
+	MOD_INC_USE_COUNT;
+	len = (count < TWIDDLELENGTH) ? count : TWIDDLELENGTH;
+	if (copy_from_user (ourcopy, buffer, len)) {
+	        MOD_DEC_USE_COUNT;
+		return -EFAULT;
+	}
+	ourcopy [len] = '\0';
+	twiddle = simple_strtol (ourcopy, NULL, 10);
+#undef TWIDDLELENGTH
+
+	printk(KERN_DEBUG "%s(): twiddle now %d\n", __FUNCTION__, twiddle);
+
+	MOD_DEC_USE_COUNT;
+
+	return len;
+}
+#endif /* IPAQ_DUAL_SLEEVE */
+#endif /* PRISM2_NO_PROCFS_DEBUG */
+
+
 static struct net_device *
 prism2_init_local_data(struct prism2_helper_functions *funcs, int card_idx)
 {
@@ -3386,6 +3485,14 @@
 #ifndef PRISM2_NO_PROCFS_DEBUG
 	create_proc_read_entry("registers", 0, local->proc,
 			       prism2_registers_proc_read, local);
+#ifdef IPAQ_DUAL_SLEEVE
+	twiddle_file = create_proc_entry("net/hostap/twiddle", 0644, local->proc);
+	if (twiddle_file) {
+	        twiddle_file->read_proc = proc_read_twiddle;
+		twiddle_file->write_proc = proc_write_twiddle;
+		twiddle_file->owner = THIS_MODULE;
+	}
+#endif /* IPAQ_DUAL_SLEEVE */
 #endif /* PRISM2_NO_PROCFS_DEBUG */
 
 	hostap_init_data(local);
@@ -3474,6 +3581,10 @@
 #ifndef PRISM2_NO_PROCFS_DEBUG
 	if (local->proc != NULL)
 		remove_proc_entry("registers", local->proc);
+#ifdef IPAQ_DUAL_SLEEVE
+	if (twiddle_file != NULL)
+	        remove_proc_entry("twiddle", twiddle_file);
+#endif /* IPAQ_DUAL_SLEEVE */
 #endif /* PRISM2_NO_PROCFS_DEBUG */
 	hostap_remove_proc(local);

-- 

This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the Crimes Act 1914.  If you have received this email in error, you are requested to contact the sender and delete the email.



From jkmaline  Tue May 17 19:26:59 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:26:59 -0700
Subject: Connection to DI-624 fails
In-Reply-To: <1116133133.5588.12.camel@localhost>
References: <1116133133.5588.12.camel@localhost>
Message-ID: <20050518022659.GH8114@jm.kir.nu>

On Sat, May 14, 2005 at 11:58:53PM -0500, Jochen Antesberger wrote:

> I have a 3com Office Connect PC card (3CRSHW196, the one with the
> retractable antenna). I'm trying to connect to a DLink router (DI-624)
> using WPA-PSK but it won't work. I use the atmel driver from
> sourceforge, the latest wpa enabled firmware and the supplicant from
> debian testing. Kernel is 2.6.8 from debian. I've attached the the
> output that I am getting.

> Wireless event: cmd=0x8c02 len=29
> Custom wireless event: 'ASSOCINFO(ReqIEs='

I don't know whether this this is the only reason for problems, but at
least the ASSOCINFO event is missing the IE information. This is
something that should be reported on the atmel driver mailing list.

I have not used Atmel cards, so I do not know what to expect from them
or the driver. The scan results were getting somewhat mixed up with
other time outs and the first scan failed for some reason. I don't know
whether Atmel driver supports scan_ssid=1. Anyway, the driver was
reporting association, but no EAPOL-Key packets were received from the
AP after this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jim  Tue May 17 19:31:23 2005
From: jim (Jim Thompson)
Date: Tue, 17 May 2005 16:31:23 -1000
Subject: Optional WPA and RSN
In-Reply-To: <20050508194856.GC29395@jm.kir.nu>
References: <200504211928.04021.pjf@asn.pl> <20050508194856.GC29395@jm.kir.nu>
Message-ID: <428AA8FB.9070008@netgate.com>

Jouni Malinen wrote:

>On Thu, Apr 21, 2005 at 07:28:04PM +0200, Pawel Foremski wrote:
>
>  
>
>>And here is my question: would it need a lot work (possibly hacking 
>>hostapd/drivers) to make hostapd allow both no security at all and RSN (or at 
>>least old WPA) at the same time on one access point?
>>    
>>
>
>In order for this to work reliably with all client implementations, the
>AP would need to be sending out multiple beacon frames (one for each
>security mode; usually called "multiple BSSID" or "virtual AP"). This
>would need additional functionality from the card firmware/driver and
>unfortunately, the current Prism2/2.5/3 firmware does not support it.
>  
>
there are prism2/2.5/3 firmware variants that do, but they're not 
commonly available.

jim




From jkmaline  Tue May 17 19:31:51 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:31:51 -0700
Subject: wpa_supplicant WPA-PSK pairwise OK, group fails
In-Reply-To: <428A180F.6090106@gmail.com>
References: <428A180F.6090106@gmail.com>
Message-ID: <20050518023151.GI8114@jm.kir.nu>

On Tue, May 17, 2005 at 09:13:03AM -0700, Dimitris Kogias wrote:

> ipw2200 1.0.3
> wpa_supplicant 0.4.0 (debian unstable package).
> D-Link DWL-900AP+ access point configured for WPA-PSK.

Are you using the latest firmware image on that AP?

> WPA: Installing PTK to the driver.
> WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
> wpa_driver_ipw_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
> State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
> 
> 
> 
> At this point, I can ping other hosts on the WLAN (static IP, have
> already ifconfig'd the interface and set default route).  However,
> wpa_supplicant continues with:

OK, so PTK is configured and unicast packets are working at that point..

> Authentication with 00:40:05:5b:3f:34 timed out.

However, Group Key handshake was not received from the AP.

> For the few seconds that, I presume, wpa_supplicant is trying to set up
> the group keying, I have connectivity to the WLAN.  Also, the AP's log
> says that my station has connected and authenticated successfully - I
> suppose that reflects the end of the pairwise key setup.

Yes.

> While all of the above is going on, I see this in the kernel logs:
> 
> May 15 18:50:18 0x19 kernel: TKIP: replay detected:
> STA=00:40:05:5b:3f:34 previous TSC 000000000000 received TSC 000000000000

If this is indeed what is happening, the AP sent out two packets with
the same packet number and the client driver dropped one of them. If
that one happened to be the Group Key packet, that could explain why it
was not seen in the wpa_supplicant debug. Another possibility would be
in the AP sending out the Group Key packets in plaintext.. Would you
happen to have a way of using a wireless sniffer to capture what packets
are being sent between the AP and client when this happens?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 17 19:38:49 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:38:49 -0700
Subject: porting to world radio chips from conexant
In-Reply-To: <29f91651050516023955da987a@mail.gmail.com>
References: <29f91651050516023955da987a@mail.gmail.com>
Message-ID: <20050518023849.GJ8114@jm.kir.nu>

On Mon, May 16, 2005 at 05:39:59AM -0400, alfred hitch wrote:

> I intend to port the wpa supplicant to conexant workd radio chips.

Are you planning on making this available under an open source license?

> 2) The current driver we have doesnt supports wireless extensions, so
> I also intend to leave the driver that ways and map the stuff in wpa
> supplicant driver file. README mentions that wireless extensions
> support is optional, and I am inclined to believe so (for my good) 
> -;) .
> Anyone conform that there are no hidden surprises / pitfalls in not
> using wireless extension calls ?

As long as you are willing to implement the driver interface code
(driver_*.c) in wpa_supplicant, you do not need to use Linux wireless
extensions. As an example, driver_broadcom.c does not use wireless
extensions.

> 3) I could see api's for setting keys and other ie,.capability etc ..
> from supplicant to driver,
> but I some how missed where / how does the authentication /
> association time handshake messages flow from driver to supplicant,
> what all messages from driver I need to provide to supplicant ??

All data frames (i.e., EAPOL packets) need to be provided to supplicant.
In addition to this, you will need to generate association events
(wpa_supplicant_event() calls with EVENT_ASSOC parameter. Depending on
the driver/firmware implementation, you may have to generate
EVENT_ASSOCINFO events to get WPA IE information from the AssocReq (if
driver/firmware generated it). In addition, wpa_supplicant needs to be
able to get WPA IE from Beacon/ProbeResp frames through the scan
results.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bishop.thomas  Tue May 17 19:42:53 2005
From: bishop.thomas (Thomas Bishop)
Date: Tue, 17 May 2005 22:42:53 -0400
Subject: unable to get madwifi driver built into wpa_supplicant
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAQemNs5JPZEqQUQlyFRzDzAEAAAAA@gmail.com>

Hello All,

I ran through the instructions here:
http://madwifi.sourceforge.net/dokuwiki/doku.php?id=wpa_802.11i.  When I
attempt to run 'wpa_supplicant -Bw -d -Dmadwifi -c/etc/wpa_supplicant.conf
-iath0', I receive the following:

"Initializing interface 'ath0 conf '/etc/wpa_supplicant.conf' driver
'madwifi'
No driver interfaces build into wpa_supplicant"

I have verified both the .config and Makefile entries as described in the
link above.  Am I missing something?  I have a feeling it is something small
that I am overlooking.

Thanks for any assistance.

Regards,

Thomas




From jkmaline  Tue May 17 19:43:33 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:43:33 -0700
Subject: promiscuous mode only, using hostAP.
In-Reply-To: <42839F4A.1070200@cs.columbia.edu>
References: <42839F4A.1070200@cs.columbia.edu>
Message-ID: <20050518024333.GK8114@jm.kir.nu>

On Thu, May 12, 2005 at 02:24:10PM -0400, Andrea G Forte wrote:

> I am writing a small sniffer with hostAP as wireless driver. My problem 
> is that it seems that putting the interface wlan0 in promiscuous mode is 
> not enough for sniffing packets. Do I have to put it the card in monitor 
> mode as well?

Which packets do you want to receive? If you want to get all IEEE 802.11
frames, you do indeed need to put the card in monitor mode.

Host AP driver does not support promiscuous mode because of issues I
have seen with some firmware versions. Anyway, the promiscuous mode
would not likely give you all the packets you were interested in..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 17 19:47:14 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:47:14 -0700
Subject: Hostapd segmentation fault
In-Reply-To: <35a277ac050511015625faa8e3@mail.gmail.com>
References: <000801c55605$a3278ab0$ac0aa8c0@sureshj>
	<35a277ac050511015625faa8e3@mail.gmail.com>
Message-ID: <20050518024714.GL8114@jm.kir.nu>

On Wed, May 11, 2005 at 02:26:53PM +0530, Suresh Babu wrote:

>          I had got segmentation fault, when attempted to send Ctrl+C
> to terminate the Hostapd. I am using madwifi-bsd latest version and
> Hostapd 3 weeks old version. I could not debug to find where exactly
> hostapd is giving segfault? and the log shows the same PC every time
> it`s segfault.

This is not just a segfault, but actually a kernel crash.. In other
words, it is not hostapd, but more likely the madwifi driver triggering
this.. If you can get the backtrace resolved to function names, you
would be more likely to get help..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 17 19:49:00 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:49:00 -0700
Subject: unable to get madwifi driver built into wpa_supplicant
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAQemNs5JPZEqQUQlyFRzDzAEAAAAA@gmail.com>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAQemNs5JPZEqQUQlyFRzDzAEAAAAA@gmail.com>
Message-ID: <20050518024900.GM8114@jm.kir.nu>

On Tue, May 17, 2005 at 10:42:53PM -0400, Thomas Bishop wrote:

> No driver interfaces build into wpa_supplicant"
> 
> I have verified both the .config and Makefile entries as described in the
> link above.  Am I missing something?  I have a feeling it is something small
> that I am overlooking.

If you changed .config file after building wpa_supplicant, please try
doing a full build again (make clean; make). If that does not fix this
problem, please send the .config file you are using.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 17 19:56:33 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:56:33 -0700
Subject: Optional WPA and RSN
In-Reply-To: <428AA8FB.9070008@netgate.com>
References: <200504211928.04021.pjf@asn.pl> <20050508194856.GC29395@jm.kir.nu>
	<428AA8FB.9070008@netgate.com>
Message-ID: <20050518025633.GN8114@jm.kir.nu>

On Tue, May 17, 2005 at 04:31:23PM -1000, Jim Thompson wrote:

> >In order for this to work reliably with all client implementations, the
> >AP would need to be sending out multiple beacon frames (one for each
> >security mode; usually called "multiple BSSID" or "virtual AP"). This
> >would need additional functionality from the card firmware/driver and
> >unfortunately, the current Prism2/2.5/3 firmware does not support it.

> there are prism2/2.5/3 firmware variants that do, but they're not 
> commonly available.

Yes, I know. And should one actually become publicly available with some
documentation, I would expect to see support added into Host AP driver
quite rapidly ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 17 19:59:45 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 17 May 2005 19:59:45 -0700
Subject: Pre-Authentication with WPA.
In-Reply-To: <20050509113055.30886.qmail@webmaild.fe1.aruba.it>
References: <20050509113055.30886.qmail@webmaild.fe1.aruba.it>
Message-ID: <20050518025945.GO8114@jm.kir.nu>

On Mon, May 09, 2005 at 01:30:55PM +0200, roby wrote:

>   I need your help..... Do anybody know if Pre-Authentication can work with 
> WPA? 

Pre-authentication was added in WPA2 and as such, does not work with
WPA.

>   I have a small net with 2 APs based on Hostap. I'm using a 802.1x 
> authentication system based on EAP-TLS and the authentication works fine. Do 
> someone know how I have to set hostapd for make the pre-authentication 
> works? 

If you can use WPA2, that would allow pre-authentication to be used.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dimitris  Tue May 17 20:31:32 2005
From: dimitris (Dimitris Kogias)
Date: Tue, 17 May 2005 20:31:32 -0700
Subject: wpa_supplicant WPA-PSK pairwise OK, group fails
In-Reply-To: <20050518023151.GI8114@jm.kir.nu>
References: <428A180F.6090106@gmail.com> <20050518023151.GI8114@jm.kir.nu>
Message-ID: <428AB714.6010604@gmail.com>

Hi Jouni,

Jouni Malinen wrote:
> On Tue, May 17, 2005 at 09:13:03AM -0700, Dimitris Kogias wrote:
> 
> 
>>ipw2200 1.0.3
>>wpa_supplicant 0.4.0 (debian unstable package).
>>D-Link DWL-900AP+ access point configured for WPA-PSK.
> 
> 
> Are you using the latest firmware image on that AP?

Latest one from D-Link, 3.07, dated 30 December 2003.  Release notes at
http://support.dlink.com/products/view.asp?productid=DWL%2D900AP%2B%5FrevC

This is an end-of-life product so they probably won't be releasing any
firmware updates for it.

>>While all of the above is going on, I see this in the kernel logs:
>>
>>May 15 18:50:18 0x19 kernel: TKIP: replay detected:
>>STA=00:40:05:5b:3f:34 previous TSC 000000000000 received TSC 000000000000
> 
> 
> If this is indeed what is happening, the AP sent out two packets with
> the same packet number and the client driver dropped one of them. If
> that one happened to be the Group Key packet, that could explain why it
> was not seen in the wpa_supplicant debug. Another possibility would be
> in the AP sending out the Group Key packets in plaintext.. Would you
> happen to have a way of using a wireless sniffer to capture what packets
> are being sent between the AP and client when this happens?
> 

No wireless sniffer, and no other wpa_supplicant capable adapter handy
to tcpdump with, but I ran tcpdump on the same interface while running
wpa_supplicant (with the same results).

00:12:f0:13:51:dc is the laptop station, 00:40:05:5b:3f:34 is the AP:

d at 0x19:~$ sudo tcpdump -i eth1 -s 0 -XX -vv
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size
65535 bytes
20:15:39.240397 00:12:f0:13:51:dc > 00:40:05:5b:3f:34, ethertype Unknown
(0x888e), length 18:
        0x0000:  0040 055b 3f34 0012 f013 51dc 888e 0101  . at .[?4....Q.....
        0x0010:  0000                                     ..
20:15:42.395305 00:40:05:5b:3f:34 > 00:12:f0:13:51:dc, ethertype Unknown
(0x888e), length 113:
        0x0000:  0012 f013 51dc 0040 055b 3f34 888e 0103  ....Q.. at .[?4....
        0x0010:  005f fe00 8900 2000 0000 0000 0000 019d  ._..............
        0x0020:  6891 6ae4 9f38 f845 531c 59e6 86a5 7da8  h.j..8.ES.Y...}.
        0x0030:  cf5d 3a0d 0d6b 3d54 7760 fb05 b4de 0200  .]:..k=Tw`......
        0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0060:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0070:  00                                       .
20:15:59.395266 00:40:05:5b:3f:34 > 00:12:f0:13:51:dc, ethertype Unknown
(0x888e), length 113:
        0x0000:  0012 f013 51dc 0040 055b 3f34 888e 0103  ....Q.. at .[?4....
        0x0010:  005f fe00 8900 2000 0000 0000 0000 0151  ._.............Q
        0x0020:  67b5 e544 04f8 dae7 425e e3db 60c9 7348  g..D....B^..`.sH
        0x0030:  9875 84f5 94ad 0a9f 833e 0cc5 3b8c b900  .u.......>..;...
        0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0060:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0070:  00                                       .
20:15:59.399629 00:12:f0:13:51:dc > 00:40:05:5b:3f:34, ethertype Unknown
(0x888e), length 137:
        0x0000:  0040 055b 3f34 0012 f013 51dc 888e 0103  . at .[?4....Q.....
        0x0010:  0077 fe01 0900 2000 0000 0000 0000 01db  .w..............
        0x0020:  d333 ef9d a729 2399 7571 7553 0b60 24bf  .3...)#.uquS.`$.
        0x0030:  fc67 c031 ae5e 1004 3665 7cdb 3b5e ed00  .g.1.^..6e|.;^..
        0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0050:  0000 0000 0000 0000 0000 0000 0000 00ba  ................
        0x0060:  5ffd 4a30 cb90 9008 f63a 8568 e914 8700  _.J0.....:.h....
        0x0070:  18dd 1600 50f2 0101 0000 50f2 0201 0000  ....P.....P.....
        0x0080:  50f2 0201 0000 50f2 02                   P.....P..
20:15:59.404416 00:40:05:5b:3f:34 > 00:12:f0:13:51:dc, ethertype Unknown
(0x888e), length 139:
        0x0000:  0012 f013 51dc 0040 055b 3f34 888e 0103  ....Q.. at .[?4....
        0x0010:  0079 fe01 c900 2000 0000 0000 0000 0251  .y.............Q
        0x0020:  67b5 e544 04f8 dae7 425e e3db 60c9 7348  g..D....B^..`.sH
        0x0030:  9875 84f5 94ad 0a9f 833e 0cc5 3b8c b900  .u.......>..;...
        0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0050:  0000 0000 0000 0000 0000 0000 0000 00e8  ................
        0x0060:  f73e eabd 0dbf 23ab b13c f554 9b98 1900  .>....#..<.T....
        0x0070:  1add 1800 50f2 0101 0000 50f2 0201 0000  ....P.....P.....
        0x0080:  50f2 0201 0000 50f2 0200 00              P.....P....
20:15:59.406376 00:12:f0:13:51:dc > 00:40:05:5b:3f:34, ethertype Unknown
(0x888e), length 113:
        0x0000:  0040 055b 3f34 0012 f013 51dc 888e 0103  . at .[?4....Q.....
        0x0010:  005f fe01 0900 2000 0000 0000 0000 0200  ._..............
        0x0020:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0030:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0040:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0050:  0000 0000 0000 0000 0000 0000 0000 00ef  ................
        0x0060:  9a8c c718 e37a c8e4 ccd2 f2d1 95ee 1d00  .....z..........
        0x0070:  00                                       .
tcpdump: pcap_loop: recvfrom: Network is down
6 packets captured
6 packets received by filter
0 packets dropped by kernel
d at 0x19:~$



As I said the wpa_supplicant results were the same:  Intermittent
point-to-point WLAN connectivity, TKIP replay log entries.  Today I have
also upgraded to the latest version of the ipw2200 driver, 1.0.4, and I
am seeing this message that I didn't see before, and only on the first
time wpa_supplicant tries to set up WPA:

WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00
00 00 00 00 01 9d 68 91 6a e4 9f 38 f8 45 53 1c 59 e6 86 a5 7d a8 cf 5d
3a 0d 0d 6b 3d 54 77 60 fb 05 b4 de 02 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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:40:05:5b:3f:34 (ver=1)
Invalid group cipher (0).
WPA: Failed to generate WPA IE (for msg 2 of 4).
Authentication with 00:40:05:5b:3f:34 timed out.

I don't remember seeing 'Invalid group cipher(0)' before.


Dimitris.



From pcanto  Wed May 18 00:02:11 2005
From: pcanto (Pablo R. Canto)
Date: Wed, 18 May 2005 04:02:11 -0300
Subject: wpa_supplicant IPW2100 D-Link 524 problem
Message-ID: <428AE873.7050105@4m.com.ar>

Mi Config:
IBM T41 IPW2100
OS GNU/Linux FC3 kernel 2.6.11-1.14_FC3
ipw2100 version 1.1.0 patched with the recent 655 [1] as module
Wireless Extension v17
wpa_supplicant-0.4.0 (neither work with 0.3.8)

AP D-Link 524 WPA-PSK enable SSID=pablito PSK="my_passphrase"

[1]http://www.bughost.org/bugzilla/show_bug.cgi?id=655

###my wpa_supplicant.conf: #########
ctrl_interface=/var/run/wpa_supplicant
network={
        ssid="pablito"
        scan_ssid=1
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk="my_passphrase"
}


my wpa_supplicand command string :
wpa_supplicant -c/etc/wpa_supplicant.conf -ieth1 -Dipw -ddd
[root at ix ipw2100-1.1.0]# wpa_supplicant -c/etc/wpa_supplicant.conf 
-ieth1 -Dipw -ddd
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'ipw'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=7):
     70 61 62 6c 69 74 6f                              pablito
scan_ssid=1 (0x1)
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='pablito'
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
ioctl[SIOCSIWPMKSA]: Operation not supported
Own MAC address: 00:0c:f1:42:91:8a
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
     70 61 62 6c 69 74 6f                              pablito
Scan timeout - try to get results
Received 273 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:3d:35:c7:29 ssid='pablito' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:0f:3d:35:c7:29 (SSID='pablito' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Wireless event: cmd=0x8b1a len=20
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
CTRL-EVENT-TERMINATING - signal 2 received
State: DISCONNECTED -> 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
wpa_driver_ipw_set_drop_unencrypted: enabled=0
wpa_driver_ipw_set_countermeasures: enabled=0
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)


I trie 2 weeks to do this work and i can't.

Tanks, Pablo.-

PD: helpppp!! :)




From bishop.thomas  Wed May 18 05:23:48 2005
From: bishop.thomas (Thomas Bishop)
Date: Wed, 18 May 2005 08:23:48 -0400
Subject: unable to get madwifi driver built into wpa_supplicant
In-Reply-To: <20050518024900.GM8114@jm.kir.nu>
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAlERMyigGWk6tKZvgvS+mqwEAAAAA@gmail.com>

Thanks for the response.  I tried rebuilding; no luck.

My madwifi source is at /usr/src/madwifi.  My wpa_supplicant source is at
/usr/src/wpa_supplicant.  Latest versions of both.

Here is the contents of my .config:

CONFIG_DRIVER_MADWIFI=y
CONFIG_WIRELESS_EXTENSION=y

The section I changed in the Makefile:

ifdef CONFIG_DRIVER_MADWIFI
CFLAGS += -I/usr/src/madwifi
OBJS += driver_madwifi.o
CONFIG_WIRELESS_EXTENSION=y
endif

Here is the output of make:

cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o config.o config.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o eloop.o eloop.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o common.o common.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o md5.o md5.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o rc4.o rc4.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o sha1.o sha1.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o aes_wrap.o
aes_wrap.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o driver_madwifi.o
driver_madwifi.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o tls_none.o
tls_none.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o driver_wext.o
driver_wext.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o wpa_supplicant.o
wpa_supplicant.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o wpa.o wpa.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o l2_packet.o
l2_packet.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o drivers.o drivers.c
cc -o wpa_supplicant config.o eloop.o common.o md5.o rc4.o sha1.o aes_wrap.o
driver_madwifi.o tls_none.o driver_wext.o wpa_supplicant.o wpa.o l2_packet.o
drivers.o 
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o wpa_passphrase.o
wpa_passphrase.c
cc -o wpa_passphrase wpa_passphrase.o sha1.o md5.o 
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o wpa_cli.o wpa_cli.c
cc -MMD -O2 -Wall -g -I../driver/modules -I../utils -I../hostapd
-I/usr/src/madwifi  -DCONFIG_WIRELESS_EXTENSION   -c -o wpa_ctrl.o
wpa_ctrl.c
cc -o wpa_cli wpa_cli.o wpa_ctrl.o 

I noticed that madwifi is mentioned a few times, but I am not quite sure
what it is doing (maybe including source files from my madwifi source dir?).
Any help would be appreciated.  Thanks.

-Thomas

-----Original Message-----
From: hostap-bounces+bishop.thomas=gmail.com at shmoo.com
[mailto:hostap-bounces+bishop.thomas=gmail.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: Tuesday, May 17, 2005 10:49 PM
To: hostap at shmoo.com
Subject: Re: unable to get madwifi driver built into wpa_supplicant

On Tue, May 17, 2005 at 10:42:53PM -0400, Thomas Bishop wrote:

> No driver interfaces build into wpa_supplicant"
> 
> I have verified both the .config and Makefile entries as described in the
> link above.  Am I missing something?  I have a feeling it is something
small
> that I am overlooking.

If you changed .config file after building wpa_supplicant, please try
doing a full build again (make clean; make). If that does not fix this
problem, please send the .config file you are using.

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




From frank  Wed May 18 06:23:20 2005
From: frank (Frank Thieme)
Date: Wed, 18 May 2005 15:23:20 +0200
Subject: automatic client configuration
In-Reply-To: <20050515204727.GA12307@stars.fthieme.net>
References: <20050515204727.GA12307@stars.fthieme.net>
Message-ID: <20050518132320.GM5690@stars.fthieme.net>

On Sun, May 15, 2005 at 10:47:27PM +0200, Frank Thieme wrote:
> I used wlan-ng for a long time now. The feature I really loved is that I
> know how to configure the things each ap I want be attached to wants and
> I can just go to the ap, switch my notebook on and I get all the
> different configurations automatically.

ok, I played around a bit. I found out that all the WEP/WPA thing can be
done with wpa_supplicant. 

But how do I set ip addresses, default routes, name server and so on
specific to the network I'm in?

I mean network.opts is not checked if wpa_supplicant is started, is it?

Bye...Frank




From jkmaline  Wed May 18 06:29:55 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 06:29:55 -0700
Subject: unable to get madwifi driver built into wpa_supplicant
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAlERMyigGWk6tKZvgvS+mqwEAAAAA@gmail.com>
References: <20050518024900.GM8114@jm.kir.nu>
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAaFsGGIthMEWF8yccDc62oWKBAAAQAAAAlERMyigGWk6tKZvgvS+mqwEAAAAA@gmail.com>
Message-ID: <20050518132954.GQ8114@jm.kir.nu>

On Wed, May 18, 2005 at 08:23:48AM -0400, Thomas Bishop wrote:

> My madwifi source is at /usr/src/madwifi.  My wpa_supplicant source is at
> /usr/src/wpa_supplicant.  Latest versions of both.
> 
> Here is the contents of my .config:
> 
> CONFIG_DRIVER_MADWIFI=y
> CONFIG_WIRELESS_EXTENSION=y

OK.

> The section I changed in the Makefile:
> 
> ifdef CONFIG_DRIVER_MADWIFI
> CFLAGS += -I/usr/src/madwifi
> OBJS += driver_madwifi.o
> CONFIG_WIRELESS_EXTENSION=y
> endif

Please do not change the Makefile. The include path can be added in
.config by adding that CFLAGS line there. It looks like you removed the
CONFIG_DRIVER_MADWIFI define from the Makefile and while doing that
removed madwifi support from the build. In other wrods, the "CFLAGS +=
-DCONFIG_DRIVER_MADWIFI" has to remain in Makefile in order for the
build to work.

-- 
Jouni Malinen                                            PGP id EFC895FA



From andreaf  Wed May 18 08:40:08 2005
From: andreaf (Andrea G Forte)
Date: Wed, 18 May 2005 11:40:08 -0400
Subject: hostap bug when unloading driver?
Message-ID: <428B61D8.8050605@cs.columbia.edu>

Hi all,

I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove 
the card from the pcmcia slot something weird happens and after a few 
times if I do "lsmod" it shows: hostap_cs  -4.
It seems that the driver does not get unloaded correctly. Also, if I try 
doing "modprobe -r hostap_cs" I get "device busy".
Does anyone know how to fix this? It did not happen to me when I was 
using a very old version of the driver (0.0.4).

Thanks a lot,
Andrea




From jar  Wed May 18 08:44:18 2005
From: jar (Jar)
Date: Wed, 18 May 2005 18:44:18 +0300
Subject: hostap bug when unloading driver?
In-Reply-To: <428B61D8.8050605@cs.columbia.edu>
References: <428B61D8.8050605@cs.columbia.edu>
Message-ID: <428B62D2.7040104@pcuf.fi>

Andrea G Forte wrote:
> Hi all,
> 
> I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove 
> the card from the pcmcia slot something weird happens and after a few 
> times if I do "lsmod" it shows: hostap_cs  -4.
> It seems that the driver does not get unloaded correctly. Also, if I try 
> doing "modprobe -r hostap_cs" I get "device busy".
> Does anyone know how to fix this? It did not happen to me when I was 
> using a very old version of the driver (0.0.4).

Can you do '/sbin/cardctl eject' before unloading hostap_cs module.

-- 
Best Regards, Jar



From pkolyvas  Wed May 18 09:07:43 2005
From: pkolyvas (Petros Kolyvas)
Date: Wed, 18 May 2005 12:07:43 -0400
Subject: wpa_supplicant IPW2100 D-Link 524 problem
In-Reply-To: <428AE873.7050105@4m.com.ar>
References: <428AE873.7050105@4m.com.ar>
Message-ID: <BAYC1-PASMTP0147A3391A98FB28168435D6170@cez.ice>

  > I trie 2 weeks to do this work and i can't.
> 
> Tanks, Pablo.-
> 
> PD: helpppp!! :)

Have you tried setting the iwconfig properties before running 
wpa_supplicant?

With my config, I have to 'iwconfig ifname essid MyNetwork channel x' 
before running wpa_supplicant. I was getting the same errors as you.

You may also try doing a reboot of your router.

Hope that helps.

Pk




From ramalhais  Wed May 18 09:53:10 2005
From: ramalhais (Pedro Ramalhais)
Date: Wed, 18 May 2005 17:53:10 +0100
Subject: wpa_supplicant IPW2100 D-Link 524 problem
In-Reply-To: <428B684F.6010401@gmail.com>
References: <428AE873.7050105@4m.com.ar>  <428B684F.6010401@gmail.com>
Message-ID: <1116435190.4366.11441.camel@gandalf.uninova.pt>

On Wed, 2005-05-18 at 17:07, Petros Kolyvas wrote:
>   > I trie 2 weeks to do this work and i can't.
> > 
> > Tanks, Pablo.-
> > 
> > PD: helpppp!! :)
> 
> Have you tried setting the iwconfig properties before running 
> wpa_supplicant?
> 
> With my config, I have to 'iwconfig ifname essid MyNetwork channel x' 
> before running wpa_supplicant. I was getting the same errors as you.
> 
> You may also try doing a reboot of your router.
> 
> Hope that helps.
> 
> Pk

Are you using hidden ESSID in the AP?
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From andreaf  Wed May 18 12:13:11 2005
From: andreaf (Andrea G Forte)
Date: Wed, 18 May 2005 15:13:11 -0400
Subject: passive scanning question.
Message-ID: <428B93C7.50201@cs.columbia.edu>

Hi all,

when using passive scanning, the function hostap_passive_scan() is 
called. It seems that such a function changes channel, waits for some 
time and then goes to the next channel only. It does not take care of 
collecting beacons and saving the data of each beacon (SSID, signal 
strength, etc.). Who takes care of writing this info somewhere in 
memory? I also see that after we have the data from the beacons, the 
function create_proc_read_entry() gets called to write this data to 
file. I am missing the part in the middle between hostap_passive_scan () 
and create_proc_read_entry().

Thank you for your help,
Andrea




From zen_hacker  Wed May 18 13:10:16 2005
From: zen_hacker (Brian Sturgill)
Date: Wed, 18 May 2005 20:10:16 +0000
Subject: hostap bug when unloading driver?
In-Reply-To: <428B61D8.8050605@cs.columbia.edu>
Message-ID: <BAY13-F1026A63206D316242CB523F7170@phx.gbl>

Are you just ejecting the card or using cardctl to notify the drivers before 
ejecting? Ie... /sbin/cardctl eject 0 for ejecting the card in socket 0.


Brian


>From: Andrea G Forte <andreaf at cs.columbia.edu>
>To: hostap at shmoo.com
>Subject: hostap bug when unloading driver?
>Date: Wed, 18 May 2005 11:40:08 -0400
>
>Hi all,
>
>I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove
>the card from the pcmcia slot something weird happens and after a few
>times if I do "lsmod" it shows: hostap_cs  -4.
>It seems that the driver does not get unloaded correctly. Also, if I try
>doing "modprobe -r hostap_cs" I get "device busy".
>Does anyone know how to fix this? It did not happen to me when I was
>using a very old version of the driver (0.0.4).
>
>Thanks a lot,
>Andrea
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From andreaf  Wed May 18 13:31:47 2005
From: andreaf (Andrea G Forte)
Date: Wed, 18 May 2005 16:31:47 -0400
Subject: hostap bug when unloading driver?
In-Reply-To: <BAY13-F1026A63206D316242CB523F7170@phx.gbl>
References: <BAY13-F1026A63206D316242CB523F7170@phx.gbl>
Message-ID: <428BA633.1070207@cs.columbia.edu>

I was just ejecting the card. If I use the cardctl command everything 
works fine. However, the weird thing is that with hostap 0.0.4 I could 
just eject the card and everything would be unloaded correctly. For some 
reason this is not the case with the newer hostap.
I do not think it is something wrong with my card manager because if so 
I would have had the same problem when using hostap 0.0.4.

Andrea


Brian Sturgill wrote:

>Are you just ejecting the card or using cardctl to notify the drivers before 
>ejecting? Ie... /sbin/cardctl eject 0 for ejecting the card in socket 0.
>
>
>Brian
>
>
>  
>
>>From: Andrea G Forte <andreaf at cs.columbia.edu>
>>To: hostap at shmoo.com
>>Subject: hostap bug when unloading driver?
>>Date: Wed, 18 May 2005 11:40:08 -0400
>>
>>Hi all,
>>
>>I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove
>>the card from the pcmcia slot something weird happens and after a few
>>times if I do "lsmod" it shows: hostap_cs  -4.
>>It seems that the driver does not get unloaded correctly. Also, if I try
>>doing "modprobe -r hostap_cs" I get "device busy".
>>Does anyone know how to fix this? It did not happen to me when I was
>>using a very old version of the driver (0.0.4).
>>
>>Thanks a lot,
>>Andrea
>>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>    
>>
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>  
>




From jphstap  Wed May 18 13:50:35 2005
From: jphstap (Joe Parks)
Date: Wed, 18 May 2005 16:50:35 -0400
Subject: tx_timeout problem
In-Reply-To: <146553738.20050518002506@bis.net.ua>
References: <146553738.20050518002506@bis.net.ua>
Message-ID: <20050518165035.2e4cadb8@scrodconumulus>

On Wed, 18 May 2005 00:25:06 +0300
"vlad (bis)" <vlad at bis.net.ua> wrote:
> If I use full channel speed (450 kb/s) one of the router very often looks like
> this: "tx_timeout, hostap is restarting" and no more.. The server is
> down. 

I've noticed the same problem in Master mode with both WDS connections and regular STA connections.   In addition I've noticed the problem occasionally occurring with various ethernet drivers as well.   In all cases the problem was only occurring under high-speed, heavy throughput conditions.   

But because the problem seems to happen to all sorts of drivers (not just hostap) under those conditions I'm inclined to suspect that the problem lives in more generic queue handling code in the kernel.

I've also noticed that disabling and re-enabling the interface seems to allow recovery from the problem and is the current workaround that I'm using (scripted) when the problem is encountered (I have a daemon watching the error logs for the timeout error).

I'm using an older 2.4 kernel and have tested only briefly with 2.6 and didn't encounter the problem there so I had suspected the problem no longer existed.   But since you mention FC3 having it, I guess it must still exist.

I expect this is a problem best discussed on some other list, but please let me know if you learn anything more about it.



From f.de.kruijf  Wed May 18 14:20:05 2005
From: f.de.kruijf (Freek de Kruijf)
Date: Wed, 18 May 2005 23:20:05 +0200
Subject: WPA-PSK problem with Q-TEC 54G and MSI AP54G
Message-ID: <200505182320.05903.f.de.kruijf@hetnet.nl>

I have a Toshiba laptop with SuSE 9.2, ndiswrapper with PCMCIA Q-TEC 
Wireless 54G (chipset: Marvell W8300), driver mrv8k51.sys and an Access 
Point MSI AP54G. I am using wpa_supplicant v0.3.8

I have this combination working with WEP 128bit, not using wpa_supplicant.

I tried to get this combination working with WPA-PSK which is supported by 
the AP. The AP only has the option WPA-PSK with a passphrase and Encryption 
type TKIP. Logging in the AP is rather limited. See the following 2 lines.
2005/5/18 16:01:18  System   802.1x authenticator started
2005/5/18 17:08:33  Security WPA-PSK four-way handshake failed for 
00:03:2f:24:a7:9b

The wpa configuration file is:
# configuartion file for wpa_supplicant
# this is to use WPA-PSK for connection with a wireless AP (access point)
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=audio
eapol_version=1
ap_scan=1
#Home network
network={
	ssid="FGHIJKL"
	priority=2
	scan_ssid=0
	proto=WPA RSN
	key_mgmt=WPA-PSK
	psk="199966669999666999999669666666"
	pairwise=TKIP
	group=TKIP
}

wpa_supplicant is started with the following command:
wpa_supplicant -iwlan0 -Dndiswrapper -c/etc/wpa_supplicant.conf -dd > 
supplicant.txt

The wpa_supplicant process is closed with <Ctrl>C after only about 10 
seconds. The output is a large file because the process repeats its actions 
rather fast.

The first part of the output file is as follows:
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=17 (from group name 'audio')
eapol_version=1
ap_scan=1
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=7):
     46 47 48 49 4a 4b 4c                              FGHIJKL         
priority=2 (0x2)
scan_ssid=0 (0x0)
proto: 0x3
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=30): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 2
   id=0 ssid='FLM42BJ'
Initializing interface (2) 'wlan0'
Own MAC address: 00:03:2f:24:a7:9b
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 311 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:11:09:08:07:5e ssid='FGHIJKL' wpa_ie_len=26 rsn_ie_len=0
   selected
Trying to associate with 00:11:09:08:07:5e (SSID='FGHIJKL' freq=2442 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
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
Wireless event: cmd=0x8c02 len=215
Custom wireless event: 
'ASSOCINFO(ReqIEs=0007464c4d3432424a010882848b960c18304832041224606cdd050010180100dd180050f20101000050f202 
RespIEs=010482848b9632080c1218243048606c0482848b960301072a01003200000000000000000000000000000000)'
Association info event
req_ies - hexdump(len=44): 00 07 46 4c 4d 34 32 42 4a 01 08 82 84 8b 96 0c 
18 30 48 32 04 12 24 60 6c dd 05 00 10 18 01 00 dd 18 00 50 f2 01 01 00 00 
50 f2 02
resp_ies - hexdump(len=44): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c 
04 82 84 8b 96 03 01 07 2a 01 00 32 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
Truncated IE in assoc_info - hexdump(len=12): dd 18 00 50 f2 01 01 00 00 50 
f2 02
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:11:09:08:07:5e
Association event - clear replay counter
Associated to a new BSS: BSSID=00:11:09:08:07:5e
No keys have been configured - skip key clearing
Associated with 00:11:09:08:07:5e
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:11:09:08:07:5e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 
01 90 03 f5 e5 a6 44 e7 fe 19 e6 ca 7d 7d df 5f 33 9a 8c 22 36 68 1d 84 3a 
27 b9 91 87 29 6d 43 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 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
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 90 03 f5 e5 a6 44 e7 fe 19 e6 ca 7d 7d df 5f 33 9a 8c 22 36 68 
1d 84 3a 27 b9 91 87 29 6d 43 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 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 00:11:09:08:07:5e (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): c0 46 87 52 91 ab 7c d9 ab 35 6f 8f 
3d 6f 38 99 15 7d 62 e5 78 bc 5f 45 9a 69 59 de be 2f b7 d8
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 11 58 a9 21 ab 2f ec 2a 1f a1 04 f7 16 
07 32 18
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 11 09 08 07 5e 00 03 2f 24 a7 
9b 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 c0 46 87 52 91 
ab 7c d9 ab 35 6f 8f 3d 6f 38 99 15 7d 62 e5 78 bc 5f 45 9a 69 59 de be 2f 
b7 d8 00 00 00 00 00 00 00 00 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 58 a9 21 ab 2f ec 2a 1f a1 04 f7 16 07 32 18 
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
Wireless event: cmd=0x8c02 len=215
Custom wireless event: 
'ASSOCINFO(ReqIEs=0007464c4d3432424a010882848b960c18304832041224606cdd050010180100dd180050f20101000050f202 
RespIEs=010482848b9632080c1218243048606c0482848b960301072a01003200000000000000000000000000000000)'
Association info event
req_ies - hexdump(len=44): 00 07 46 4c 4d 34 32 42 4a 01 08 82 84 8b 96 0c 
18 30 48 32 04 12 24 60 6c dd 05 00 10 18 01 00 dd 18 00 50 f2 01 01 00 00 
50 f2 02
resp_ies - hexdump(len=44): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c 
04 82 84 8b 96 03 01 07 2a 01 00 32 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
Truncated IE in assoc_info - hexdump(len=12): dd 18 00 50 f2 01 01 00 00 50 
f2 02
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:11:09:08:07:5e
Association event - clear replay counter
Associated with 00:11:09:08:07:5e
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:11:09:08:07:5e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 
02 90 03 f5 e5 a6 44 e7 fe 19 e6 ca 7d 7d df 5f 33 9a 8c 22 36 68 1d 84 3a 
27 b9 91 87 29 6d 43 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 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
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 02 90 03 f5 e5 a6 44 e7 fe 19 e6 ca 7d 7d df 5f 33 9a 8c 22 36 68 
1d 84 3a 27 b9 91 87 29 6d 43 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 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 00:11:09:08:07:5e (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): 6f dc c2 1b 11 3d 7e 9e ff 44 f4 0b 
78 75 54 72 e2 75 5c 30 64 af 38 e6 08 8c ba 40 af 3f f4 76
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 7e 4f f4 20 62 b5 d0 43 1e 39 6f de 8a 
ad 17 3f
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 11 09 08 07 5e 00 03 2f 24 a7 
9b 88 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 02 6f dc c2 1b 11 
3d 7e 9e ff 44 f4 0b 78 75 54 72 e2 75 5c 30 64 af 38 e6 08 8c ba 40 af 3f 
f4 76 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 7e 4f f4 20 62 b5 d0 43 1e 39 6f de 8a ad 17 3f 
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
Wireless event: cmd=0x8c02 len=215
Custom wireless event: 
'ASSOCINFO(ReqIEs=0007464c4d3432424a010882848b960c18304832041224606cdd050010180100dd180050f20101000050f202 
RespIEs=010482848b9632080c1218243048606c0482848b960301072a01003200000000000000000000000000000000)'
Association info event
req_ies - hexdump(len=44): 00 07 46 4c 4d 34 32 42 4a 01 08 82 84 8b 96 0c 
18 30 48 32 04 12 24 60 6c dd 05 00 10 18 01 00 dd 18 00 50 f2 01 01 00 00 
50 f2 02
resp_ies - hexdump(len=44): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c 
04 82 84 8b 96 03 01 07 2a 01 00 32 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
Truncated IE in assoc_info - hexdump(len=12): dd 18 00 50 f2 01 01 00 00 50 
f2 02
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:11:09:08:07:5e
Association event - clear replay counter
Associated with 00:11:09:08:07:5e
Setting authentication timeout: 10 sec 0 usec

the above seams to repeat itself indefinitely.

Anybody who knows how I should proceed.

-- 
Freek



From proski  Wed May 18 14:36:33 2005
From: proski (Pavel Roskin)
Date: Wed, 18 May 2005 17:36:33 -0400
Subject: [PATCH] wpa_supplicant/wpa_gui/.cvsignore
Message-ID: <1116452193.3648.2.camel@dv.roinet.com>

Hello!

Please add wpa_supplicant/wpa_gui/.cvsignore to CVS so that the build
results are ignored by "cvs update".

Signed-off-by: Pavel Roskin <proski at gnu.org>

--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ wpa_supplicant/wpa_gui/.cvsignore	18 May 2005 21:33:26 -0000
@@ -0,0 +1,5 @@
+.moc
+.obj
+.ui
+Makefile
+wpa_gui



Regards,
Pavel Roskin




From t.schorpp  Wed May 18 19:09:33 2005
From: t.schorpp (thomas schorpp)
Date: Thu, 19 May 2005 04:09:33 +0200
Subject: CVS: WPA/WPA2 WPA-PSK/TLS TKIP/CCMP: EAPOL-Key timeout s in 1/4 msg
	of 4-Way Handshake: win+linux clients, madwifi with WG311T, DWL-G650
Message-ID: <428BF55D.2040008@gmx.de>

hello,

softwares: hostapd 0.3.6...CVS, client: dlink supplicant on win98 or
wpasupplicant 0.3.8-1 debian on linux, madwifi cvs on both.

cant get authenticated.

seems hostap forgets something to broadcast.

clients wait, dont answer, hostap retries 4x... timeout.
handshake wont run through.

1. tried setup with wpa or rsn -eap-tls, certificates only -> failure
2. now as simple as possible WPA-PSK -> failure

no wep. underlying layers should be ok, hw, iwconfig, maybe madwifi
issue with the netgear WG311T?

win clients connect succesful to an embedded device ap, so should be a
issue with hostap suite.

any ideas?

build and test wpasupp cvs meanwhile...

if you rather like bugzilla, pls ask for.

y
tom

Configuration file: /etc/hostapd/hostapd.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:0f:b5:63:e0:f2 and ssid 'madwifi'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): b5 b2 84 ab fd 55 86 f6 a6 2d 8e 25 73 b0 93 48
63 01 42 30 20 0c fa a3 8a 13 74 b6 3a ef 69 06
GTK - hexdump(len=32): 3f e3 30 55 a5 7e 8d 93 71 e2 d0 dc 91 2b 78 f4
86 18 cf 83 ee fb a4 ea f2 c9 bb 9c 0d ba 22 2e
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
Deauthenticate all stations
l2_packet_receive - recv: Network is down
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.11: associated
  New STA
ath0: STA 00:0f:3d:86:fd:ab WPA: event 1 notification
ath0: STA 00:0f:3d:86:fd:ab WPA: start authentication
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:3d:86:fd:ab key_idx=0
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:3d:86:fd:ab authorized=0
WPA: 00:0f:3d:86:fd:ab WPA_PTK_GROUP entering state IDLE
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state AUTHENTICATION
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state AUTHENTICATION2
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITPSK
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 3d 86 fd ab 00 0f b5 63 e0 f2 88 8e
02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 b5 a6 27 35 af f3 71
93 3b 69 cc 30 73 48 21 90 aa 76 63 5d 1a 7d 5a 61 43 e8 4a 94 ce f4 ea
4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
ath0: STA 00:0f:3d:86:fd:ab WPA: EAPOL-Key timeout
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 3d 86 fd ab 00 0f b5 63 e0 f2 88 8e
02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 02 b5 a6 27 35 af f3 71
93 3b 69 cc 30 73 48 21 90 aa 76 63 5d 1a 7d 5a 61 43 e8 4a 94 ce f4 ea
4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
ath0: STA 00:0f:3d:86:fd:ab WPA: EAPOL-Key timeout
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 3d 86 fd ab 00 0f b5 63 e0 f2 88 8e
02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 03 b5 a6 27 35 af f3 71
93 3b 69 cc 30 73 48 21 90 aa 76 63 5d 1a 7d 5a 61 43 e8 4a 94 ce f4 ea
4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
ath0: STA 00:0f:3d:86:fd:ab WPA: EAPOL-Key timeout
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 3d 86 fd ab 00 0f b5 63 e0 f2 88 8e
02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 04 b5 a6 27 35 af f3 71
93 3b 69 cc 30 73 48 21 90 aa 76 63 5d 1a 7d 5a 61 43 e8 4a 94 ce f4 ea
4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 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: 00:0f:3d:86:fd:ab WPA_PTK entering state DISCONNECT
madwifi_sta_deauth: addr=00:0f:3d:86:fd:ab reason_code=2
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state DISCONNECTED
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:3d:86:fd:ab key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:3d:86:fd:ab authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.11: deauthenticated due to local
deauth request
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0

- ca. same with eap-tls -

no logs from win dlink supplicant
reports: "connecting and key wait"

linux wpasupplicant log:

Initializing interface 'ath0' conf '(null)' driver 'madwifi'
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=2
ap_scan=1
fast_reauth=0
Line: 279 - start of a new network block
ssid - hexdump_ascii(len=7):
     6d 61 64 77 69 66 69                              madwifi
proto: 0x1
auth_alg: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x18
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='madwifi'
Initializing interface (2) 'ath0'
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:0f:3d:86:fd:ab
wpa_driver_madwifi_set_wpa: enabled=1
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_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Wireless event: cmd=0x8b19 len=12
Received 850 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 0
0: 00:0f:b5:63:e0:f2 ssid='madwifi' wpa_ie_len=32 rsn_ie_len=0
   selected
Trying to associate with 00:0f:b5:63:e0:f2 (SSID='madwifi' freq=2422 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 3
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=20
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:b5:63:e0:f2
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:b5:63:e0:f2
No keys have been configured - skip key clearing
Associated with 00:0f:b5:63:e0:f2
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 'ath0' added
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28 idleWhile=58
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27 idleWhile=57
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:0f:b5:63:e0:f2 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:0f:b5:63:e0:f2
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:b5:63:e0:f2
No keys have been configured - skip key clearing
Associated with 00:0f:b5:63:e0:f2
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
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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Signal 2 received - terminating
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_madwifi_set_wpa: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
Removed BSSID 00:0f:b5:63:e0:f2 from blacklist (clear)


config files:

wpasupp:

eapol_version=2
ap_scan=1
fast_reauth=0
# Only WPA-PSK is used. Any valid cipher combination is accepted.
network={
	ssid="madwifi"
	proto=WPA
	auth_alg=OPEN
	key_mgmt=WPA-PSK
	pairwise=TKIP CCMP
	group=TKIP CCMP
	psk="01234567"
}

# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used
WEP104
# or WEP40 as the group cipher will not be accepted.
#network={
#	ssid="madwifi"
#	proto=RSN
#	key_mgmt=WPA-EAP
#	auth_alg=OPEN
#	pairwise=CCMP
#	group=CCMP
#	eap=TLS
#	identity="tom2"
#	ca_cert="/etc/wpa/CAcert.pem"
#	client_cert="/etc/wpa/tom2-cert.pem"
#	private_key="/etc/wpa/tom2-key.pem"
#	private_key_passwd=""
#	priority=1
#}

hostap:

interface=ath0

driver=madwifi

logger_syslog=-1
logger_syslog_level=4
logger_stdout=-1
logger_stdout_level=0

debug=4

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

ctrl_interface_group=0

ssid=madwifi

macaddr_acl=0

auth_algs=1


# Require IEEE 802.1X authorization
#ieee8021x=1

eap_authenticator=1

# Path for EAP authenticator user database
#eap_user_file=/etc/hostapd/hostapd.eap_user

# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
ca_cert=/etc/hostapd/wpaca/ca/CAcert.pem

# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
server_cert=/etc/hostapd/wpaca/certs/tom3-cert.pem

private_key=/etc/hostapd/wpaca/certs/tom3-key.pem

# Passphrase for private key
private_key_passwd=

# Optional displayable message sent with EAP Request-Identity
eap_message=Willkommen im madwifi

eapol_key_index_workaround=0

eap_reauth_period=3600

wpa=1

# wpa_passphrase (dot11RSNAConfigPSKPassPhrase)
#wpa_psk=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
wpa_passphrase=01234567

wpa_key_mgmt=WPA-PSK WPA-EAP

wpa_pairwise=TKIP CCMP

wpa_group_rekey=600

wpa_gmk_rekey=86400


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3220 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050519/df625ade/attachment.bin 


From jkmaline  Wed May 18 19:20:43 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 19:20:43 -0700
Subject: WPA-PSK problem with Q-TEC 54G and MSI AP54G
In-Reply-To: <200505182320.05903.f.de.kruijf@hetnet.nl>
References: <200505182320.05903.f.de.kruijf@hetnet.nl>
Message-ID: <20050519022043.GS8114@jm.kir.nu>

On Wed, May 18, 2005 at 11:20:05PM +0200, Freek de Kruijf wrote:

> I have a Toshiba laptop with SuSE 9.2, ndiswrapper with PCMCIA Q-TEC 
> Wireless 54G (chipset: Marvell W8300), driver mrv8k51.sys and an Access 
> Point MSI AP54G. I am using wpa_supplicant v0.3.8

> Wireless event: cmd=0x8c02 len=215
> Custom wireless event: 
> 'ASSOCINFO(ReqIEs=0007464c4d3432424a010882848b960c18304832041224606cdd050010180100dd180050f20101000050f202 
> RespIEs=010482848b9632080c1218243048606c0482848b960301072a01003200000000000000000000000000000000)'

ReqIEs information is truncated. Either ndiswrapper is truncating this or
the Marvell driver is not reporting all IEs from AssocReq. This means
that wpa_supplicant does not get the correct WPA IE and the AP will
reject message 2/4 which is supposed to include the WPA IE that was used
in AssocReq.

This sounds like a driver specific issue, so I would suggest reporting
this on the ndiswrapper mailing list.


> Association info event
> req_ies - hexdump(len=44): 00 07 46 4c 4d 34 32 42 4a 01 08 82 84 8b 96 0c 
> 18 30 48 32 04 12 24 60 6c dd 05 00 10 18 01 00 dd 18 00 50 f2 01 01 00 00 
> 50 f2 02

> Truncated IE in assoc_info - hexdump(len=12): dd 18 00 50 f2 01 01 00 00 50 
> f2 02

This is the part in log giving details of the incorrect ReqIEs. That
0x18 is length of the IE, but there is only 10 bytes on data.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed May 18 19:22:54 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 19:22:54 -0700
Subject: CVS: WPA/WPA2 WPA-PSK/TLS TKIP/CCMP: EAPOL-Key timeout s in 1/4
	msg of 4-Way Handshake: win+linux clients, madwifi with WG311T,
	DWL-G650
In-Reply-To: <428BF55D.2040008@gmx.de>
References: <428BF55D.2040008@gmx.de>
Message-ID: <20050519022254.GT8114@jm.kir.nu>

On Thu, May 19, 2005 at 04:09:33AM +0200, thomas schorpp wrote:

> softwares: hostapd 0.3.6...CVS, client: dlink supplicant on win98 or
> wpasupplicant 0.3.8-1 debian on linux, madwifi cvs on both.

Which version of madwifi cvs are you using? The CVS trunk does not seem
to work with hostapd, but I was able to use the snapshot version from
'BSD' branch with hostapd couple of weeks ago.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed May 18 19:25:16 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 19:25:16 -0700
Subject: [PATCH] wpa_supplicant/wpa_gui/.cvsignore
In-Reply-To: <1116452193.3648.2.camel@dv.roinet.com>
References: <1116452193.3648.2.camel@dv.roinet.com>
Message-ID: <20050519022516.GU8114@jm.kir.nu>

On Wed, May 18, 2005 at 05:36:33PM -0400, Pavel Roskin wrote:

> Please add wpa_supplicant/wpa_gui/.cvsignore to CVS so that the build
> results are ignored by "cvs update".

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed May 18 19:29:10 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 19:29:10 -0700
Subject: hostap bug when unloading driver?
In-Reply-To: <428BA633.1070207@cs.columbia.edu>
References: <BAY13-F1026A63206D316242CB523F7170@phx.gbl>
	<428BA633.1070207@cs.columbia.edu>
Message-ID: <20050519022910.GV8114@jm.kir.nu>

On Wed, May 18, 2005 at 04:31:47PM -0400, Andrea G Forte wrote:

> I was just ejecting the card. If I use the cardctl command everything 
> works fine. However, the weird thing is that with hostap 0.0.4 I could 
> just eject the card and everything would be unloaded correctly. For some 
> reason this is not the case with the newer hostap.
> I do not think it is something wrong with my card manager because if so 
> I would have had the same problem when using hostap 0.0.4.

This could be kernel version specific, since I have no problems ejecting
the card with Linux 2.6.x. I haven't tested 2.4.x kernels for a long
time..

> >>I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove
> >>the card from the pcmcia slot something weird happens and after a few
> >>times if I do "lsmod" it shows: hostap_cs  -4.

Looks like something is decrementing the module usage counter too often,
or more likely, decrementing the counter for incorrect module.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed May 18 19:34:34 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 19:34:34 -0700
Subject: [PATCH]: hostapd with madwifi accounting
In-Reply-To: <20050517133434.raidkoy34ny84wkg@webmail.togg.de>
References: <20041008060822.GA3384@informatik.uni-rostock.de>
	<20050509013354.GJ29395@jm.kir.nu>
	<20050517133434.raidkoy34ny84wkg@webmail.togg.de>
Message-ID: <20050519023434.GW8114@jm.kir.nu>

On Tue, May 17, 2005 at 01:34:34PM +0200, Sebastian Weitzel wrote:

> > Thanks! I finally got a working madwifi AP setup running with WPA after
> > moving to BSD branch and I'm now able to test hostapd with madwifi. I
> > applied your patch for hostapd to enable RADIUS accounting with madwifi
> > driver and verified that it works with the netlink message. The procfs
> > information does not seem to be available from the driver, so interim
> > accounting messages are not currently supported.

> please note that madwifi head cvs needs a patch to enable this procfs 
> accounting hack. Its not nice and so in madwifi-bsd it's done via a 
> accounting ioctl' (STA-TRAFFIC-STAT)

That's ok. I'll remove the procfs stuff once madwifi driver code from
the BSD branch get merged into CVS trunk.. At the moment, CVS head does
not really seem to work at all with hostapd, so I don't really care that
much about it before the merge has happened.

> Do you see any problems with this? (Interim) Accounting works in my tests.

Please note that I wrote the email you are quoting before merging in
support for IEEE80211_IOCTL_GETSTASTATS.. The current CVS snapshot does
indeed work with interim accounting.

-- 
Jouni Malinen                                            PGP id EFC895FA



From t.schorpp  Wed May 18 19:40:02 2005
From: t.schorpp (thomas schorpp)
Date: Thu, 19 May 2005 04:40:02 +0200
Subject: CVS: WPA/WPA2 WPA-PSK/TLS TKIP/CCMP: EAPOL-Key timeout s in 1/4
	msg of 4-Way Handshake: win+linux clients, madwifi with WG311T, DWL-G650
In-Reply-To: <20050519022254.GT8114@jm.kir.nu>
References: <428BF55D.2040008@gmx.de> <20050519022254.GT8114@jm.kir.nu>
Message-ID: <428BFC82.2020309@gmx.de>

Jouni Malinen wrote:
> On Thu, May 19, 2005 at 04:09:33AM +0200, thomas schorpp wrote:
> 
> 
>>softwares: hostapd 0.3.6...CVS, client: dlink supplicant on win98 or
>>wpasupplicant 0.3.8-1 debian on linux, madwifi cvs on both.
> 
> 
> Which version of madwifi cvs are you using? The CVS trunk does not seem
> to work with hostapd, but I was able to use the snapshot version from
> 'BSD' branch with hostapd couple of weeks ago.
> 

thx for fast reply. so madwifi? sounds bad.

hmm.. what you get with proposed standard checkout... i assume head, no
special branch:

May 19 02:33:48 tom3 kernel: ath_pci: driver unloaded
May 19 02:33:48 tom3 kernel: ath_rate_onoe: unloaded
May 19 02:33:48 tom3 kernel: ath_hal: driver unloaded
May 19 02:34:09 tom3 kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212,
RF5111, RF5112, RF2413)
May 19 02:34:09 tom3 kernel: ath_rate_onoe: 1.0
May 19 02:34:09 tom3 kernel: ath_pci: 0.9.4.12 (EXPERIMENTAL)
May 19 02:34:09 tom3 kernel: PCI: Found IRQ 10 for device 0000:00:10.0
May 19 02:34:09 tom3 kernel: PCI: Sharing IRQ 10 with 0000:00:07.2
May 19 02:34:09 tom3 kernel: PCI: Sharing IRQ 10 with 0000:00:0f.1
May 19 02:34:09 tom3 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
May 19 02:34:09 tom3 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May 19 02:34:09 tom3 kernel: ath0: mac 5.9 phy 4.3 radio 4.6
May 19 02:34:09 tom3 kernel: ath0: 802.11 address: 00:0f:b5:63:e0:f2
May 19 02:34:09 tom3 kernel: ath0: Use hw queue 0 for WME_AC_BE traffic
May 19 02:34:09 tom3 kernel: ath0: Use hw queue 1 for WME_AC_BK traffic
May 19 02:34:09 tom3 kernel: ath0: Use hw queue 2 for WME_AC_VI traffic
May 19 02:34:09 tom3 kernel: ath0: Use hw queue 3 for WME_AC_VO traffic
May 19 02:34:09 tom3 kernel: ath0: Atheros 5212: mem=0xfebc0000, irq=10
tom3:~#

driver reports 5212 chip, but its 5213... hope its compatible, card is
rev. 01 according to pcb printing.

remarkable too, i never see the act led blinking or just too fast...

y
tom








From t.schorpp  Wed May 18 19:50:09 2005
From: t.schorpp (thomas schorpp)
Date: Thu, 19 May 2005 04:50:09 +0200
Subject: [PATCH]: hostapd with madwifi accounting
In-Reply-To: <20050519023434.GW8114@jm.kir.nu>
References: <20041008060822.GA3384@informatik.uni-rostock.de>	<20050509013354.GJ29395@jm.kir.nu>	<20050517133434.raidkoy34ny84wkg@webmail.togg.de>
	<20050519023434.GW8114@jm.kir.nu>
Message-ID: <428BFEE1.7060109@gmx.de>

Jouni Malinen wrote:
> On Tue, May 17, 2005 at 01:34:34PM +0200, Sebastian Weitzel wrote:
> 
> 
>>>Thanks! I finally got a working madwifi AP setup running with WPA after
>>>moving to BSD branch and I'm now able to test hostapd with madwifi.

nice, thx. ill verify this too...

but dont need external radius server, etc...




From jkmaline  Wed May 18 20:56:52 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 18 May 2005 20:56:52 -0700
Subject: Release candidate for the next stable release (0.3.9-rc1)
Message-ID: <20050519035652.GX8114@jm.kir.nu>

Finally, I managed to go through the fixes in the development branch
and merge the ones that apply to 0.3.x into the stable branch. I was
hoping to get v0.3.9 released earlier, but didn't have suitable time
for this before. Anyway, a release candidate for the next stable
release is now available at http://hostap.epitest.fi/releases/testing/.

I would hope to release this after about a week or so of testing. In
addition to the testing I can do, it would be useful if you would be
able to test whether this version has introduced any regression and
report any problems to the Host AP mailing list.


Here's a list of changes from the previous stable release:

hostap-driver:
* fixed background scans (iwlist wlan0 scan) not to break data
  connection when in host_roaming 2 mode (e.g., when using
  wpa_supplicant)
* fixed beacon frame when moving from monitor mode to master mode
  (workaround for firmware bug that left IBSS IE in the Beacon frames)


wpa_supplicant:
* modified the EAP workaround that accepts EAP-Success with incorrect
  Identifier to be even less strict about verification in order to
  interoperate with some authentication servers
* fixed RSN IE in 4-Way Handshake message 2/4 for the case where
  Authenticator rejects PMKSA caching attempt and the driver is not
  using assoc_info events
* fixed a possible double free in EAP-TTLS fast-reauthentication when
  identity or password is entered through control interface
* added -P<pid file> argument for wpa_supplicant to write the current
  process id into a file
* driver_madwifi: fixed association in plaintext mode
* driver_madwifi: added preliminary support for compiling against 'BSD'
  branch of madwifi CVS tree


hostapd:
* fixed a bug which caused some RSN pre-authentication cases to use
  freed memory and potentially crash hostapd
* fixed private key loading for cases where passphrase is not set
* fixed WPA2 to add PMKSA cache entry when using integrated EAP
  authenticator
* driver_madwifi: fixed pairwise key removal to allow WPA reauth
  without disassociation
* fixed RADIUS attribute Class processing to only use Access-Accept
  packets to update Class; previously, other RADIUS authentication
  packets could have cleared Class attribute
* fixed PMKSA caching (EAP authentication was not skipped correctly
  with the new state machine changes from IEEE 802.1X draft)


-- 
Jouni Malinen                                            PGP id EFC895FA



From t.schorpp  Thu May 19 00:15:32 2005
From: t.schorpp (thomas schorpp)
Date: Thu, 19 May 2005 09:15:32 +0200
Subject: CVS: WPA/WPA2 WPA-PSK/TLS TKIP/CCMP: EAPOL-Key timeout s in 1/4
	msg of 4-Way Handshake: win+linux clients, madwifi with WG311T, DWL-G650
In-Reply-To: <20050519022254.GT8114@jm.kir.nu>
References: <428BF55D.2040008@gmx.de> <20050519022254.GT8114@jm.kir.nu>
Message-ID: <428C3D14.106@gmx.de>

Jouni Malinen wrote:
> On Thu, May 19, 2005 at 04:09:33AM +0200, thomas schorpp wrote:
> 
> 
>>softwares: hostapd 0.3.6...CVS, client: dlink supplicant on win98 or
>>wpasupplicant 0.3.8-1 debian on linux, madwifi cvs on both.
> 
> 
> Which version of madwifi cvs are you using? The CVS trunk does not seem
> to work with hostapd, but I was able to use the snapshot version from
> 'BSD' branch with hostapd couple of weeks ago.
> 

yes, verified, authentication to hostapd with wpa-psk set in supplicant
on clientis possible with madwifi bsd branch now :)

but one stone left with wpa-eap, see below.

nice thanks.

BTW:

1. compile madwifi with make (install) KERNELRELEASE=2.6.x-m-nnn on
debian with debian distri kernels, or the modules get outside the
lib/modules tree in 2.6.x... enhancement in makefile needed.

2. debugged "Hostapd segmentation fault". dont forget to setup madwifi
in .config correctly before build or hostapd will access driver
"default" at startup instead of madwifi, leading to access violation due
to invalid pointer... sorry, lost the gdb output.


hostapd log on eap-tls auth: (breaks on ath0: STA 00:0f:3d:86:fd:ab WPA:
sending 3/4 msg of 4-Way Handshake) :

tom3:~# /usr/local/bin/hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Using interface ath0 with hwaddr 00:0f:b5:63:e0:f2 and ssid 'madwifi'
madwifi_configure_wpa: group key cipher=3
madwifi_configure_wpa: pairwise key ciphers=0x8
madwifi_configure_wpa: key management algorithms=0x1
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x2
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 71 f2 9b e4 85 4b af 7e a3 ea 9f 0e ab 55 a5 3e
55 9d 6c 32 a1 92 2d 04 57 18 0e 5c db 78 17 11
GTK - hexdump(len=16): f9 d3 70 fb 3c 05 5c cf a9 f5 4c 09 99 55 ab 88
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=CCMP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
Deauthenticate all stations
l2_packet_receive - recv: Network is down
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.11: associated
  New STA
RSN IE: STA PMKID - hexdump(len=16): ac 8c f3 81 b5 9c 11 84 ce 53 e4 bb
cb c8 d8 c4
ath0: STA 00:0f:3d:86:fd:ab WPA: event 1 notification
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: start authentication
EAP: State machine created
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_KEY_TX entering state NO_KEY_TRANSMIT
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
IEEE 802.1X: 00:0f:3d:86:fd:ab CTRL_DIR entering state IN_OR_BOTH
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
IEEE 802.1X: 00:0f:3d:86:fd:ab CTRL_DIR entering state FORCE_BOTH
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
ath0: STA 00:0f:3d:86:fd:ab WPA: start authentication
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:3d:86:fd:ab key_idx=0
WPA: 00:0f:3d:86:fd:ab WPA_PTK_GROUP entering state IDLE
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state AUTHENTICATION
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state AUTHENTICATION2
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state DISCONNECTED
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: unauthorizing port
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state RESTART
IEEE 802.1X: Integrated EAP Authenticator in use - do not generate
EAP-Request/Identity
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: no identity known yet -> CONTINUE
EAP: EAP entering state PROPOSE_METHOD
EAP: getNextMethod: type 1
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 103
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state CONNECTING
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state AUTHENTICATING
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 103)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 13 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=0 length=9
   EAP: code=2 identifier=103 length=9 (response)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: received EAP packet (code=2
id=103 len=9) from STA: EAP Response-Identity (1)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: STA identity 'tom2'
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state RESPONSE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=103 respMethod=1
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-Identity: Peer identity - hexdump_ascii(len=4):
     74 6f 6d 32                                       tom2
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: another method available -> CONTINUE
EAP: EAP entering state PROPOSE_METHOD
EAP: getNextMethod: type 13
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 104
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 104)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 110 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=0 length=106
   EAP: code=2 identifier=104 length=106 (response)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: received EAP packet (code=2
id=104 len=106) from STA: EAP Response-TLS (13)
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state RESPONSE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=104 respMethod=13
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-TLS: Received packet(len=106) - Flags 0x00
SSL: (where=0x10 ret=0x1)
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:before/accept initialization
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 read client hello A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 write server hello A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 write certificate A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 write certificate request A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 flush data
SSL: (where=0x2002 ret=0xffffffff)
SSL: SSL_accept:error in SSLv3 read client certificate A
SSL: 1391 bytes pending from ssl_out
SSL: 1391 bytes left to be sent out (of total 1391 bytes)
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 105
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 105)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 1412 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=0 length=1408
   EAP: code=2 identifier=105 length=1408 (response)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: received EAP packet (code=2
id=105 len=1408) from STA: EAP Response-TLS (13)
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state RESPONSE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=105 respMethod=13
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-TLS: Received packet(len=1408) - Flags 0xc0
EAP-TLS: TLS Message Length: 1651
SSL: Need 253 bytes more input data
SSL: data reassembly failed
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 106
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 106)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 263 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=0 length=259
   EAP: code=2 identifier=106 length=259 (response)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: received EAP packet (code=2
id=106 len=259) from STA: EAP Response-TLS (13)
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state RESPONSE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=106 respMethod=13
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-TLS: Received packet(len=259) - Flags 0x00
TLS: tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
buf='/C=DE/ST=BW/L=KARLSRUHE/O=RUE19/OU=WLAN/CN=madwifi
wlan/emailAddress=root at tom3'
TLS: tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
buf='/C=DE/ST=BW/L=KARLSRUHE/O=RUE19/OU=WLAN/CN=tom2/emailAddress=root at tom3'
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 read client certificate A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 read client key exchange A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 read certificate verify A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 read finished A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 write change cipher spec A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 write finished A
SSL: (where=0x2001 ret=0x1)
SSL: SSL_accept:SSLv3 flush data
SSL: (where=0x20 ret=0x1)
SSL: (where=0x2002 ret=0x1)
SSL: 59 bytes pending from ssl_out
SSL: 59 bytes left to be sent out (of total 59 bytes)
EAP: EAP entering state METHOD_REQUEST
EAP: building EAP-Request: Identifier 107
EAP-TLS: Done
EAP: EAP entering state SEND_REQUEST
EAP: EAP entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 107)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 10 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=0 length=6
   EAP: code=2 identifier=107 length=6 (response)
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.1X: received EAP packet (code=2
id=107 len=6) from STA: EAP Response-TLS (13)
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state RESPONSE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
EAP: EAP entering state RECEIVED
EAP: parseEapResp: rxResp=1 respId=107 respMethod=13
EAP: EAP entering state INTEGRITY_CHECK
EAP: EAP entering state METHOD_RESPONSE
EAP-TLS: Received packet(len=6) - Flags 0x00
SSL: 0 bytes pending from ssl_out
SSL: No data to be sent out
EAP-TLS: Derived key - hexdump(len=64): e2 86 1f 64 83 ce 49 f1 99 e0 a1
d7 83 31 29 a4 90 41 29 db 97 1a f4 37 84 83 30 87 a2 a3 d5 a6 1f cc 6e
28 e7 88 df 82 fd 2d 41 65 af a2 a4 0a c6 9b 6b 7f 92 20 e2 78 af 83 b0
32 53 56 aa a6
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: method succeeded -> SUCCESS
EAP: EAP entering state SUCCESS
EAP: Building EAP-Success (id=107)
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending EAP Packet to 00:0f:3d:86:fd:ab (identifier 107)
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab BE_AUTH entering state IDLE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITPMK
WPA: PMK from EAPOL state machine (len=32)
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKSTART
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 1/4 msg of 4-Way Handshake
IEEE 802.1X: 139 bytes from 00:0f:3d:86:fd:ab
   IEEE 802.1X: version=2 type=3 length=135
ath0: STA 00:0f:3d:86:fd:ab WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): e2 86 1f 64 83 ce 49 f1 99 e0 a1 d7 83 31 29 a4
90 41 29 db 97 1a f4 37 84 83 30 87 a2 a3 d5 a6
PTK - hexdump(len=64): d2 bb a8 70 b7 63 79 c6 24 77 d4 6c 98 57 1c 5a
5a f9 43 38 96 d8 4c 30 6e 34 bc e8 7b 52 56 5e 1c 57 2e 10 44 95 3e 9f
cc a7 22 3f be 83 31 78 f7 d2 bb 83 93 27 8a e8 0f e2 cf 76 25 6e 80 e1
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:3d:86:fd:ab WPA: sending 3/4 msg of 4-Way Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=56): 30 14 01 00 00 0f ac 04
01 00 00 0f ac 04 01 00 00 0f ac 01 00 00 dd 16 000f ac 01 01 00 f9 d3
70 fb 3c 05 5c cf a9 f5 4c 09 99 55 ab 88 dd 00 00 00 00 00 00 00 00 00
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:3d:86:fd:ab
rx_packets=6
tx_packets=8
rx_bytes=2031
tx_bytes=1846
'
ath0: STA 00:0f:3d:86:fd:ab IEEE 802.11: deassociated
ath0: STA 00:0f:3d:86:fd:ab WPA: event 2 notification
madwifi_del_key: addr=00:0f:3d:86:fd:ab key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state DISCONNECTED
WPA: 00:0f:3d:86:fd:ab WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:3d:86:fd:ab key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
IEEE 802.1X: station 00:0f:3d:86:fd:ab port disabled
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
EAP: EAP entering state DISABLED
IEEE 802.1X: 00:0f:3d:86:fd:ab AUTH_PAE entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:3d:86:fd:ab KEY_RX entering state NO_KEY_RECEIVE
EAP: State machine removed
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations
madwifi_set_privacy: enabled=0
tom3:~#









From t.schorpp  Thu May 19 00:50:30 2005
From: t.schorpp (thomas schorpp)
Date: Thu, 19 May 2005 09:50:30 +0200
Subject: is CRL " certificate revocation list" checked by hostapd or openssl
	in eap-tls?
Message-ID: <428C4546.2020204@gmx.de>

# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
ca_cert=/etc/hostapd/wpaca/ca/CAcert.pem

# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
server_cert=/etc/hostapd/wpaca/certs/tom3-cert.pem

no entry for the crl.

i would like to implement this then, to deauthenticate users just simply
by revoking their certs ;)

y
tom

ps. config files for the previous thread posting auth issues:

eap_user database:

#*			TLS

"tom2"                    TLS

client wpasupplicant conf:

-eapol2
-fast reauth0
-ccmp
-ccmp
-identity
-rsn
-open
-certs
-ssid
-wpa-eap
-tls

hostapd.conf:

ieee8021x=1
eapol_key_index_workaround=0
wpa=2
...







From ged  Thu May 19 01:27:29 2005
From: ged (G.W. Haywood)
Date: Thu, 19 May 2005 09:27:29 +0100 (BST)
Subject: hostap bug when unloading driver?
In-Reply-To: <20050518212522.BC3E0134443@mail.iocaine.com>
References: <20050518212522.BC3E0134443@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0505190924220.7781@mail3.jubileegroup.co.uk>

Hi there,

On Wed, 18 May 2005 Andrea G Forte wrote:

> I am using hostap-driver 0.3.7 and Linux kernel 2.4.20 . When I remove
> the card from the pcmcia slot something weird happens and after a few
> times if I do "lsmod" it shows: hostap_cs  -4.

2.4.20 is a very old kernel, I had some trouble with unloading modules
with it too.  Try upgrading to 2.4.30 - it's not a big deal.

73,
Ged.



From alfred.hitch  Thu May 19 02:59:11 2005
From: alfred.hitch (alfred hitch)
Date: Thu, 19 May 2005 05:59:11 -0400
Subject: porting to world radio chips from conexant
In-Reply-To: <20050518023849.GJ8114@jm.kir.nu>
References: <29f91651050516023955da987a@mail.gmail.com>
	<20050518023849.GJ8114@jm.kir.nu>
Message-ID: <29f91651050519025918b68eeb@mail.gmail.com>

Hi Jouni, All,

1) I do intend to make it open source .

2) I went thru broadcom code and mapping it now with my cards structures .. 

3) I now understand (*hope so -;) ) the relavance and what all I have
to   pass apart from API structure population .. i.e what all events
..

I had a small observation, if one could please clarify .. 
in the wpa_supplicant_asocinfo.

The header file which had structure defintion for wpa_even_data, 
mentions that
req_ie, resp_ie
becaon_ie,  are all optional ..

But, in this function code, I see that  we are free'ing any data which
wud have been part of wpa_s , without checking that the driver while
passing this event filled in the correct i.e's or not ..

infact mapping it with drover_broadcom.c
I see that assoc info driver gives to this funciton is copied into
"resp"_ie while wpa_supplicant_asocinfo function is using p =
data->asoc_info.req_ies .
This indicates usage of req_ies, which has like not even been
populated in driver ?
same for beacon frames , driver doesnt passes and we are free'ing and
memcpy'ing ..

Also, if I could ask, of all these 3 (optional ?) ie's which one will
be needed defintely ..
In the sense that from where else can supplicant gather info on ie's
and so I could skip giving here .. ??
scan result population I will with wpa_ie ..
This will be resp_ie right .. 
so that leaves req_ie ,, infact do we need in wpa_s AP's ie, or our
request IE, ?
This is what I could guess, please correct me if I am wrong:

in wpa_s
ap_wpa_ie refers to AP's beacon / resp_ie .. 
ap_rsn_ie .. for RSN case, same meaning as above
assoc_wpa_ie, .. what we just sent in association request ?? req_ie 

Cheers,
Alfred



On 5/17/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Mon, May 16, 2005 at 05:39:59AM -0400, alfred hitch wrote:
> 
> > I intend to port the wpa supplicant to conexant workd radio chips.
> 
> Are you planning on making this available under an open source license?
> 
> > 2) The current driver we have doesnt supports wireless extensions, so
> > I also intend to leave the driver that ways and map the stuff in wpa
> > supplicant driver file. README mentions that wireless extensions
> > support is optional, and I am inclined to believe so (for my good)
> > -;) .
> > Anyone conform that there are no hidden surprises / pitfalls in not
> > using wireless extension calls ?
> 
> As long as you are willing to implement the driver interface code
> (driver_*.c) in wpa_supplicant, you do not need to use Linux wireless
> extensions. As an example, driver_broadcom.c does not use wireless
> extensions.
> 
> > 3) I could see api's for setting keys and other ie,.capability etc ..
> > from supplicant to driver,
> > but I some how missed where / how does the authentication /
> > association time handshake messages flow from driver to supplicant,
> > what all messages from driver I need to provide to supplicant ??
> 
> All data frames (i.e., EAPOL packets) need to be provided to supplicant.
> In addition to this, you will need to generate association events
> (wpa_supplicant_event() calls with EVENT_ASSOC parameter. Depending on
> the driver/firmware implementation, you may have to generate
> EVENT_ASSOCINFO events to get WPA IE information from the AssocReq (if
> driver/firmware generated it). In addition, wpa_supplicant needs to be
> able to get WPA IE from Beacon/ProbeResp frames through the scan
> results.
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From brian  Thu May 19 03:11:31 2005
From: brian (Brian Hill)
Date: Thu, 19 May 2005 06:11:31 -0400
Subject: Patch for wpa_supplicant multiple networks when ap_scan = 2
Message-ID: <200505191011.j4JABV1P008592@leopard.the-hills.org>


Hi,

I'm' not sure if this will be useful to anyone besides myself, but I'm
using the ipw2200 adapter, and have had trouble getting a single
wpa_supplicant configuration file that would get me connected with no
manual intervention to my home WLAN (using simple, static WEP) and my
work WLAN (using IEEE 8021X key management and EAP-PEAP-GTC
authentication).

I made a very crude patch to wpa_supplicant.c that will let the
supplicant scan through multiple networks in priority order, even when
ap_scan = 2.  It's not well done, it's what I could do in just a few
minutes to make it work for me.  I'd certainly appreciate any feedback
if someone finds this useful / badly broken / stupid / funny.

--- wpa_supplicant-0.4.0/wpa_supplicant.c       2005-04-25
22:29:31.000000000 -0400
+++ wpa_supplicant-0.4.0-brian/wpa_supplicant.c 2005-05-18
22:13:07.000000000 -0400
@@ -122,6 +122,8 @@
 extern int wpa_debug_show_keys;
 extern int wpa_debug_timestamp;

+static int last_prio_scan = -1;
+

 void wpa_msg(struct wpa_supplicant *wpa_s, int level, char *fmt, ...)
 {
@@ -1138,6 +1140,7 @@
 {
       struct wpa_supplicant *wpa_s = eloop_ctx;
       struct wpa_ssid *ssid;
+       int prio;

       if (wpa_s->conf->ap_scan == 0) {
               wpa_supplicant_gen_assoc_event(wpa_s);
@@ -1145,7 +1148,13 @@
       }

       if (wpa_s->conf->ap_scan == 2) {
-               ssid = wpa_s->conf->ssid;
+               if(last_prio_scan == wpa_s->conf->num_prio) {
+                       last_prio_scan = -1;
+               }
+               prio = last_prio_scan + 1;
+               last_prio_scan++;
+               ssid = wpa_s->conf->pssid[prio];
+               wpa_printf(MSG_INFO, "Now scanning ssid (%d) %s",
last_prio_scan, ssid->ssid);
               if (ssid == NULL)
                       return;
               wpa_supplicant_associate(wpa_s, NULL, ssid);


--
Brian Hill
brian at the-hills.org



From and0806  Thu May 19 08:58:00 2005
From: and0806 (and hansen)
Date: Thu, 19 May 2005 17:58:00 +0200 (CEST)
Subject: psk AUTHENTICATED but no connection
Message-ID: <20050519155800.15334.qmail@web51101.mail.yahoo.com>

Hello list users

I'm trying to make a simple wpa-psk setup with
hostapd-0.3.7, wpa_supplicant0.3.8, madwifi-20050511
and
2.6.8.1-24mdk linux (mandrake10.1)

The master mode device is controlling its own NAT
network
and its working very nice whitout any security setup
but when I switch to wpa-psk with hostap, on the ap
and wpa_supp. on the client, then I get SUCCESS and
AUTHENTICEATED
but I can't drag any data from a to b ?
I have testet my wpa_supp. configuration against a
linksys wap54g
with wpa-psk enablet, so i guess my wpa client is ok.
I also have to mention that I have to restart the
network after the start of
hostapd and wpa_supp. in both ends, before I get
"AUTHENTICATED"
but still no data.
I hope someone can crawl down in my output and perhaps
spot the problem,
I'm om dead gound here, I have been fiddling around
whitout any success

Best Regards Lasse T. Jensen
here follows my two config files and their output.


##### hostapd configuration file
##############################################
interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=t245
macaddr_acl=0
accept_mac_file=/etc/hostapd.accept
deny_mac_file=/etc/hostapd.deny
auth_algs=1 
eap_authenticator=0
eap_message=hello
eapol_key_index_workaround=0
own_ip_addr=10.10.10.1
wpa=1
wpa_psk=5fdaeed52572ab31258c1ccd48ed73775bc476c239c6e626010e0a0b9269651e
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP
###############################################################################



##### wpa_supplicant configuration file
#######################################
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
        ssid="t245"
       
psk=5fdaeed52572ab31258c1ccd48ed73775bc476c239c6e626010e0a0b9269651e
}
###############################################################################



###############################################################################
[root at accesspoint root]# hostapd /etc/hostapd.conf -d
Configuration file: /etc/hostapd.conf
Using interface ath0 with hwaddr 00:0f:a3:80:bb:23 and
ssid 't245'
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 9c aa cf 84 b6 8f 12 81 79 36
93 e2 0e 76 67 99 f0 74 17 5c 97 26 c7 92 b7 1b 46 94
32 2c 7f 71
GTK - hexdump(len=32): cb 73 bb ee 46 59 47 35 1b dc
22 2d e4 f2 11 5b a9 a9 3a 4e 7b 59 0c bb 3e f8 59 69
18 0c 95 b2
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00
key_idx=1
Flushing old station entries
Deauthenticate all stations
l2_packet_receive - recv: Network is down
l2_packet_receive - recv: Network is down
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.11: associated
  New STA
No WPA/RSN information element for station!?
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.11: deassociated
ath0: STA 00:0f:a3:07:16:b3 WPA: event 2 notification
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:a3:07:16:b3 WPA: event 1 notification
ath0: STA 00:0f:a3:07:16:b3 WPA: start authentication
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:a3:07:16:b3 key_idx=0
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.1X: unauthorizing
port
WPA: 00:0f:a3:07:16:b3 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state INITPSK
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:a3:07:16:b3 WPA: sending 1/4 msg of
4-Way Handshake
IEEE 802.1X: 123 bytes from 00:0f:a3:07:16:b3
   IEEE 802.1X: version=1 type=3 length=119
ath0: STA 00:0f:a3:07:16:b3 WPA: received EAPOL-Key
frame (2/4 Pairwise)
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
PTKCALCNEGOTIATING
PMK - hexdump(len=32): 5f da ee d5 29 72 ab 31 25 8c
1c fd 48 ed 77 77 5b c6 76 c2 39 c6 e6 26 01 0e 0a 0b
92 69 65 1e
PTK - hexdump(len=64): 01 49 f5 af 42 24 d8 3b ab 09
93 a0 9a 1a 93 ea 66 b0 7b 88 2b 88 14 71 8a a1 f3 a0
3d ec 8b 17 76 4d 6a 2e 73 5b e8 67 06 cf 97 95 ee 1b
70 fe 9c 5e 4b 23 0d 43 c2 64 06 6f 72 fd 12 66 9c 77
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
PTKCALCNEGOTIATING2
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:a3:07:16:b3 WPA: sending 3/4 msg of
4-Way Handshake
IEEE 802.1X: 99 bytes from 00:0f:a3:07:16:b3
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:a3:07:16:b3 WPA: received EAPOL-Key
frame (4/4 Pairwise)
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
PTKINITDONE
madwifi_set_key: alg=CCMP addr=00:0f:a3:07:16:b3
key_idx=0
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.1X: authorizing
port
ath0: STA 00:0f:a3:07:16:b3 WPA: pairwise key
handshake completed (WPA)
WPA: 00:0f:a3:07:16:b3 WPA_PTK_GROUP entering state
REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:a3:07:16:b3 WPA: sending 1/2 msg of
Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=40): cb 73
bb ee 46 59 47 35 1b dc 22 2d e4 f2 11 5b a9 a9 3a 4e
7b 59 0c bb 3e f8 59 69 18 0c 95 b2 00 00 00 00 00 00
00 00
IEEE 802.1X: 99 bytes from 00:0f:a3:07:16:b3
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:a3:07:16:b3 WPA: received EAPOL-Key
frame (2/2 Group)
WPA: 00:0f:a3:07:16:b3 WPA_PTK_GROUP entering state
REKEYESTABLISHED
ath0: STA 00:0f:a3:07:16:b3 WPA: group key handshake
completed (WPA)
WPA: 00:0f:a3:07:16:b3 WPA_PTK_GROUP entering state
IDLE
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.11: deassociated
ath0: STA 00:0f:a3:07:16:b3 WPA: event 2 notification
madwifi_del_key: addr=00:0f:a3:07:16:b3 key_idx=0
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:a3:07:16:b3 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:a3:07:16:b3 key_idx=0
ath0: STA 00:0f:a3:07:16:b3 IEEE 802.1X: unauthorizing
port
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations
madwifi_set_privacy: enabled=0
###############################################################################
here i have killed the procces with Ctrl+C





###############################################################################
[root at wlan-client root]# wpa_supplicant -iath0
-c/etc/wpa_supplicant.conf -d
Initializing interface 'ath0' 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'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Priority group 0
   id=0 ssid='t245'
Initializing interface (2) 'ath0'
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:0f:a3:07:16:b3
wpa_driver_madwifi_set_wpa: enabled=1
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_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=20
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
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
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 210 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:a3:80:bb:23 ssid='t245' wpa_ie_len=28
rsn_ie_len=0
   selected
Trying to associate with 00:0f:a3:80:bb:23
(SSID='t245' freq=2457 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=17
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
l2_packet_receive - recv: Network is down
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Authentication with 00:00:00:00:00:00 timed out.
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
Starting AP scan (broadcast SSID)
ioctl[SIOCSIWSCAN]: Invalid argument
Failed to initiate AP scan.
Setting scan request: 10 sec 0 usec
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b1a len=13
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=17
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 210 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:a3:80:bb:23 ssid='t245' wpa_ie_len=28
rsn_ie_len=0
   selected
Trying to associate with 00:0f:a3:80:bb:23
(SSID='t245' freq=2457 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=17
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:a3:80:bb:23
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:a3:80:bb:23
No keys have been configured - skip key clearing
Associated with 00:0f:a3:80:bb:23
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 'ath0' added
RX EAPOL from 00:0f:a3:80:bb:23
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state
machines
IEEE 802.1X RX: version=2 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from
00:0f:a3:80:bb:23 (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): ee 80 ef 67 1c
78 e1 86 df e9 b5 2c 81 88 fa b2 51 70 90 4e f6 c2 fc
e8 19 65 5e 5b f8 ba 9b 98
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): ef 8f 47 56 bd
3e b8 e0 15 02 04 46 db a6 5c b8
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0f:a3:80:bb:23
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state
machines
IEEE 802.1X RX: version=2 type=3 length=123
  EAPOL-Key type=254
WPA: RX message 3 of 4-Way Handshake from
00:0f:a3:80:bb:23 (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 04 00 50 f2 02 01 00
00 50 f2 02
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=CCMP key_idx=0
set_tx=1 seq_len=6 key_len=16
RX EAPOL from 00:0f:a3:80:bb:23
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state
machines
IEEE 802.1X RX: version=2 type=3 length=135
  EAPOL-Key type=254
WPA: RX message 1 of Group Key Handshake from
00:0f:a3:80:bb:23 (ver=2)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 04 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: Key negotiation completed with 00:0f:a3:80:bb:23
[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
###############################################################################



From kshogan  Thu May 19 02:54:55 2005
From: kshogan (Kelly Hogan)
Date: Thu, 19 May 2005 02:54:55 -0700
Subject: Reliability vs speed?
Message-ID: <1116496495.4971.51.camel@m187.linora.com>

Hello all,

Any research on making changes to fragmentation/CTS settings to increase
reliability of links out there?  Mostly looking for implementations that
have sustained better reliability of throughput at the expense of speed
for weak or obstructed signals.

Also, for weak signals, what Sensitivity setting would be best?

Thanks
KH





From dm  Fri May 20 06:31:28 2005
From: dm (dm at chello.nl)
Date: Fri, 20 May 2005 15:31:28 +0200
Subject: ipw2100-1.1.0 and wpa_supplicant-0.3.8
Message-ID: <200505201531.30758.dm@chello.nl>

Hi all,

I'm trying to authenticate on my sweex 54G accesspoint using Gentoo Linux.
It goes fine using Windows and Mac OS X, but wpa_supplicant has some trouble.

My configuration:
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1

# network block
network={
        ssid="Marinus"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
        psk="lotsofstuff"
        priority=3
}

# cat /etc/modules.autoload.d/kernel-2.6
ipw2100
ieee80211
ieee80211_crypt
ieee80211_crypt_wep
ieee80211_crypt_ccmp
ieee80211_crypt_tkip

# wpa_supplicant -Dipw -ieth1 -c/etc/wpa_supplicant.conf -d
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'ipw'
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
Priority group 3
   id=1 ssid='Marinus'
Priority group 2
   id=0 ssid='... secret ...'
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
Own MAC address: 00:04:23:a3:1a:07
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 272 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 3
0: 00:10:a7:27:e1:94 ssid='Marinus' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:10:a7:27:e1:94 (SSID='Marinus' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=20
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
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 272 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 3
0: 00:10:a7:27:e1:94 ssid='Marinus' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:10:a7:27:e1:94 (SSID='Marinus' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=20
Authentication with 00:00:00:00:00:00 timed out.
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
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 272 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 3
0: 00:10:a7:27:e1:94 ssid='Marinus' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:10:a7:27:e1:94 (SSID='Marinus' freq=0 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=20
Authentication with 00:00:00:00:00:00 timed out.
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
Starting AP scan (broadcast SSID)
Signal 2 received - terminating
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
wpa_driver_ipw_set_drop_unencrypted: enabled=0
wpa_driver_ipw_set_countermeasures: enabled=0
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)

My accesspoint logs keep silent... If someone has a clue, please reply :)

Thanks in advance,
Dick
-------------- 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/20050520/fac5460d/attachment.pgp 


From frank  Fri May 20 07:18:45 2005
From: frank (Frank Thieme)
Date: Fri, 20 May 2005 16:18:45 +0200
Subject: automatic client configuration
In-Reply-To: <20050518132320.GM5690@stars.fthieme.net>
References: <20050515204727.GA12307@stars.fthieme.net>
	<20050518132320.GM5690@stars.fthieme.net>
Message-ID: <20050520141844.GH15050@stars.fthieme.net>

On Wed, May 18, 2005 at 03:23:20PM +0200, Frank Thieme wrote:
> On Sun, May 15, 2005 at 10:47:27PM +0200, Frank Thieme wrote:
> > I used wlan-ng for a long time now. The feature I really loved is that I
> > know how to configure the things each ap I want be attached to wants and
> > I can just go to the ap, switch my notebook on and I get all the
> > different configurations automatically.
> 
> ok, I played around a bit. I found out that all the WEP/WPA thing can be
> done with wpa_supplicant. 
> 
> But how do I set ip addresses, default routes, name server and so on
> specific to the network I'm in?
> 
> I mean network.opts is not checked if wpa_supplicant is started, is it?

Can't believe there is nobody here using hostap_cs on a laptop with
different wlans.

I'm still looking for a solution...

Bye...Frank



From uberlord  Fri May 20 09:51:27 2005
From: uberlord (Roy Marples)
Date: Fri, 20 May 2005 17:51:27 +0100
Subject: automatic client configuration
In-Reply-To: <20050520141844.GH15050@stars.fthieme.net>
References: <20050515204727.GA12307@stars.fthieme.net>
	<20050518132320.GM5690@stars.fthieme.net>
	<20050520141844.GH15050@stars.fthieme.net>
Message-ID: <1116607887.7312.5.camel@uberpc.ubernet>

On Fri, 2005-05-20 at 16:18 +0200, Frank Thieme wrote:
> On Wed, May 18, 2005 at 03:23:20PM +0200, Frank Thieme wrote:
> > On Sun, May 15, 2005 at 10:47:27PM +0200, Frank Thieme wrote:
> > > I used wlan-ng for a long time now. The feature I really loved is that I
> > > know how to configure the things each ap I want be attached to wants and
> > > I can just go to the ap, switch my notebook on and I get all the
> > > different configurations automatically.
> > 
> > ok, I played around a bit. I found out that all the WEP/WPA thing can be
> > done with wpa_supplicant. 
> > 
> > But how do I set ip addresses, default routes, name server and so on
> > specific to the network I'm in?
> > 
> > I mean network.opts is not checked if wpa_supplicant is started, is it?
> 
> Can't believe there is nobody here using hostap_cs on a laptop with
> different wlans.
> 
> I'm still looking for a solution...

Gentoo's baselayout-1.11.12-r1 (currently ~ARCH - means unstable but
available) supports this

config_essid=( "192.168.0.2/24" )
routes_essid=( "default via 192.168.0.1" )

dns_domain_essid="whatever.com"
dns_servers_essid=( "192.168.0.1" "192.168.0.20" )
dns_search_domains_essid="domain2.com domain3.net"

config_anotheressid=( "dhcp" )

The only downside is that you need to use Gentoo!

HTH

Roy




From frank  Fri May 20 10:33:38 2005
From: frank (Frank Thieme)
Date: Fri, 20 May 2005 19:33:38 +0200
Subject: automatic client configuration
In-Reply-To: <1116607887.7312.5.camel@uberpc.ubernet>
References: <20050515204727.GA12307@stars.fthieme.net>
	<20050518132320.GM5690@stars.fthieme.net>
	<20050520141844.GH15050@stars.fthieme.net>
	<1116607887.7312.5.camel@uberpc.ubernet>
Message-ID: <20050520173338.GB25163@stars.fthieme.net>

On Fri, May 20, 2005 at 05:51:27PM +0100, Roy Marples wrote:
> Gentoo's baselayout-1.11.12-r1 (currently ~ARCH - means unstable but
> available) supports this
> 
> config_essid=( "192.168.0.2/24" )
> routes_essid=( "default via 192.168.0.1" )
> 
> dns_domain_essid="whatever.com"
> dns_servers_essid=( "192.168.0.1" "192.168.0.20" )
> dns_search_domains_essid="domain2.com domain3.net"
> 
> config_anotheressid=( "dhcp" )
> 
> The only downside is that you need to use Gentoo!

Big downside as I'm a Slackware user, but I'll take a look on their
baselayout. Thanks...

Bye...Frank



From uberlord  Fri May 20 13:18:49 2005
From: uberlord (Roy Marples)
Date: Fri, 20 May 2005 21:18:49 +0100
Subject: automatic client configuration
In-Reply-To: <20050520173338.GB25163@stars.fthieme.net>
References: <20050515204727.GA12307@stars.fthieme.net>
	<20050518132320.GM5690@stars.fthieme.net>
	<20050520141844.GH15050@stars.fthieme.net>
	<1116607887.7312.5.camel@uberpc.ubernet>
	<20050520173338.GB25163@stars.fthieme.net>
Message-ID: <1116620329.7312.9.camel@uberpc.ubernet>

On Fri, 2005-05-20 at 19:33 +0200, Frank Thieme wrote:
> On Fri, May 20, 2005 at 05:51:27PM +0100, Roy Marples wrote:
> > Gentoo's baselayout-1.11.12-r1 (currently ~ARCH - means unstable but
> > available) supports this
> > 
> > config_essid=( "192.168.0.2/24" )
> > routes_essid=( "default via 192.168.0.1" )
> > 
> > dns_domain_essid="whatever.com"
> > dns_servers_essid=( "192.168.0.1" "192.168.0.20" )
> > dns_search_domains_essid="domain2.com domain3.net"
> > 
> > config_anotheressid=( "dhcp" )
> > 
> > The only downside is that you need to use Gentoo!
> 
> Big downside as I'm a Slackware user, but I'll take a look on their
> baselayout. Thanks...
> 

You can also look into the initng project which is a replacement init
and script system. I don't think it supports Slackware as it's Gentoo
based, but I wrote the network scripts for it - and Gentoo. It should be
possible to separate the scripts from initng and just use them in Slack
with a little bit of work. Gentoo's are heavily built into baselayout,
but not so much with initng.

Good luck!

Roy




From t.schorpp  Fri May 20 17:58:21 2005
From: t.schorpp (thomas schorpp)
Date: Sat, 21 May 2005 02:58:21 +0200
Subject: CVS: WPA/WPA2 WPA-PSK/TLS TKIP/CCMP... full success with xp sp2
	supplicant and wpa suppl clients, BIG THX :)
In-Reply-To: <428C3D14.106@gmx.de>
References: <428BF55D.2040008@gmx.de> <20050519022254.GT8114@jm.kir.nu>
	<428C3D14.106@gmx.de>
Message-ID: <428E87AD.9060306@gmx.de>

thomas schorpp wrote:
> Jouni Malinen wrote:
> 
>>On Thu, May 19, 2005 at 04:09:33AM +0200, thomas schorpp wrote:
>>
>>
>>
>>>softwares: hostapd 0.3.6...CVS, client: dlink supplicant on win98 or
>>>wpasupplicant 0.3.8-1 debian on linux, madwifi cvs on both.
>>
>>
>>Which version of madwifi cvs are you using? The CVS trunk does not seem
>>to work with hostapd, but I was able to use the snapshot version from
>>'BSD' branch with hostapd couple of weeks ago.
>>
> 
> 
> yes, verified, authentication to hostapd with wpa-psk set in supplicant
> on clientis possible with madwifi bsd branch now :)
> 
> but one stone left with wpa-eap, see below.
> 
> nice thanks.
> 
> BTW:
> 
> 1. compile madwifi with make (install) KERNELRELEASE=2.6.x-m-nnn on
> debian with debian distri kernels, or the modules get outside the
> lib/modules tree in 2.6.x... enhancement in makefile needed.
> 
> 2. debugged "Hostapd segmentation fault". dont forget to setup madwifi
> in .config correctly before build or hostapd will access driver
> "default" at startup instead of madwifi, leading to access violation due
> to invalid pointer... sorry, lost the gdb output.
> 
> 

OK, got cvs hostapd and supplicants working great RSN/WPA EAP-TLS with
certificates using madwifis cvs bsd branch even at g speeds at 54M.
100M superG speeds not tested yet...

hostapd runs fine on a netgear wg311T (311 has no longer atheros
chipsets in newer rev. so no master mode drivers support yet, needed to
build accesspoints)

windows xp client runs on a belkin F5D7001 using xp sp2 supplicant, note
that the lastest belkin utility did NOT work with wpa-tls! some issue
with the user name, no trackable reports.

neither did windows98se dlink DWL-G650 software in any wifi mode (maybe
due to lack of strong encryption support on this platform).
the windows build of wpasupplicant didnt startup either, reports "device
name mismatch (8!=0)".

so i suggest you using xp2 supplicant and not card deliverer utils on
win. 10 cudo points to ms ;)
the workaround=1 in hostapd.conf needs not to be set so far.

and 100 to the hostap engineers, big thanks for your great product!
its a little hard to set it up, but then... :)

i'll implement certificate crl (cert revokation list) support next days,
if its not done already by libopenssl internally...

y
tom















From ssmayur  Fri May 20 22:33:09 2005
From: ssmayur (Mayur Shah)
Date: Fri, 20 May 2005 22:33:09 -0700
Subject: Can anybody help?
Message-ID: <af77f7d305052022333a6b2a4d@mail.gmail.com>

 I am using the hostap drivers with gumstix product. www.gumstix.com
for compact flash NETGEAR card MA70.

My objective is to connect wirelessly from this embedded device.
When I try to run any any iwconfig command for example,

 iwconfig wifi0 essid xyz

 I get this error
 Error for wirreless requuest "Set ESSID " (8B1A) :
 SET Failed on device wifi0: Invalid Argument

 And this is the same error I get for any type of iwconfig command.
Also in most of the documentation I read, I found the interface to use
is wlan0 but what i get when i do iwconfig is usb0 and wifi0 intefaces
only.

 Can you tell me where the problem is ,

 * Do I need to download new "iwconfig"?
 * Do I need some drivers for hostap

 This gumstix stuff used linux kernel 2.6.10

 Thanks & Appreciate your help

 Regards



From vjoshi  Sat May 21 05:19:49 2005
From: vjoshi (Venkatesh Joshi)
Date: Sat, 21 May 2005 05:19:49 -0700
Subject: hostApd development page ?
Message-ID: <61716BB31DD0AE469370BBE04DD6C07A096AB7@hail.merunetworks.com>

Hi,

I wish to know if there is any webpage related to hostApd development similar to the one for wpa_supplicant at: 

http://hostap.epitest.fi/wpa_supplicant/devel/index.html

thanks,
Venkatesh





From jkmaline  Sat May 21 07:25:47 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 21 May 2005 07:25:47 -0700
Subject: hostApd development page ?
In-Reply-To: <61716BB31DD0AE469370BBE04DD6C07A096AB7@hail.merunetworks.com>
References: <61716BB31DD0AE469370BBE04DD6C07A096AB7@hail.merunetworks.com>
Message-ID: <20050521142547.GI8114@jm.kir.nu>

On Sat, May 21, 2005 at 05:19:49AM -0700, Venkatesh Joshi wrote:

> I wish to know if there is any webpage related to hostApd development similar to the one for wpa_supplicant at: 
> 
> http://hostap.epitest.fi/wpa_supplicant/devel/index.html

Not yet, but there will likely be in the future. These pages for
wpa_supplicant are very new and still somewhat experimental. Once I get
them into more complete condition, doing similar pages for hostapd would
be a good next step.

-- 
Jouni Malinen                                            PGP id EFC895FA



From zen_hacker  Sat May 21 07:43:45 2005
From: zen_hacker (Brian Sturgill)
Date: Sat, 21 May 2005 14:43:45 +0000
Subject: Can anybody help?
In-Reply-To: <af77f7d305052022333a6b2a4d@mail.gmail.com>
Message-ID: <BAY13-F69E2D52AB794012C431E5F70A0@phx.gbl>

Are you sure this is a Prism 2/2.5/3 based card?

Brian

>From: Mayur Shah <ssmayur at gmail.com>
>Reply-To: Mayur Shah <ssmayur at gmail.com>
>To: hostap at shmoo.com
>Subject: Can anybody help?
>Date: Fri, 20 May 2005 22:33:09 -0700
>
>  I am using the hostap drivers with gumstix product. www.gumstix.com
>for compact flash NETGEAR card MA70.
>
>My objective is to connect wirelessly from this embedded device.
>When I try to run any any iwconfig command for example,
>
>  iwconfig wifi0 essid xyz
>
>  I get this error
>  Error for wirreless requuest "Set ESSID " (8B1A) :
>  SET Failed on device wifi0: Invalid Argument
>
>  And this is the same error I get for any type of iwconfig command.
>Also in most of the documentation I read, I found the interface to use
>is wlan0 but what i get when i do iwconfig is usb0 and wifi0 intefaces
>only.
>
>  Can you tell me where the problem is ,
>
>  * Do I need to download new "iwconfig"?
>  * Do I need some drivers for hostap
>
>  This gumstix stuff used linux kernel 2.6.10
>
>  Thanks & Appreciate your help
>
>  Regards
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From frank  Sat May 21 08:19:17 2005
From: frank (Frank Thieme)
Date: Sat, 21 May 2005 17:19:17 +0200
Subject: Can anybody help?
In-Reply-To: <af77f7d305052022333a6b2a4d@mail.gmail.com>
References: <af77f7d305052022333a6b2a4d@mail.gmail.com>
Message-ID: <20050521151916.GB28428@stars.fthieme.net>

On Fri, May 20, 2005 at 10:33:09PM -0700, Mayur Shah wrote:
>  I am using the hostap drivers with gumstix product. www.gumstix.com
> for compact flash NETGEAR card MA70.
> 
> My objective is to connect wirelessly from this embedded device.
> When I try to run any any iwconfig command for example,
> 
>  iwconfig wifi0 essid xyz

shouldn't that be wlan0 instead of wifi0?

Bye...Frank



From wlan.20.briony  Sat May 21 10:13:24 2005
From: wlan.20.briony (wlan.20.briony at spamgourmet.com)
Date: Sat, 21 May 2005 19:13:24 +0200
Subject: which firmware for wl200?
Message-ID: <20050521191324.71864af3.a0305292@unet.univie.ac.at>

Hello all!

I've been looking for firmware for my compaq wl200 in this list but what
i found makes me suspicious - there's a firmware posted by pedro
estrela:
http://lists.shmoo.com/pipermail/hostap/2002-October/000050.html
and he recommends it again later
http://lists.shmoo.com/pipermail/hostap/2002-December/000856.html

but when i try to update my card with it i get:

Incompatible interfaces:
  SREC: role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
  card: role=Supplier variant=0 range=1-1 iface=Modem-Firmware (1)
Incompatible update data.

unfortunately i don't really understand what this error message
means(resp. what variant=0/1 means) and if its harmfull, i'm afraid something could break if i force it.

i get the same results with S1010409.HEX mentioned in the second thread
above. should i try to force the upload with -if? and with which firmware?
i guess the newest firmware that supports my card is around version
1.4.9 - does the firmware have a lot of influence on security issues
like alternating wep-keys and authentification with radius? i've searched a while and was happy
to find an old prism-card and don't want to buy a senao for 60 Euros,
hope it will work with the 10 Euro "Elektronikschrott" i bought on ebay ;-)

any input/recommendations are appreciated!

here are my
card-specs:

Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8002 v1.0.1 (HWB3163-01,02,03,04 Rev A)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v0.6.2 (station firmware)

Production Data Area (PDA)

PDR 0x0001 len=8 Platform name / Manufacturing part number
   41 30 30 30 30 30 30 30
PDR 0x0007 len=8 MAC Controller Supplier Range
   02 00 01 00 01 00 01 00
PDR 0x0008 len=8 NIC ID (component ID)
   02 80 01 00 01 00 00 00
PDR 0x0101 len=6 MAC Address
   00 50 8b 46 bd bb
PDR 0x0103 len=12 Regulatory Domain List
   02 00 30 00 00 00 00 00 00 00 00 00
PDR 0x0104 len=2 Allowed Channel Set/Active Channel List
   ff 1f
PDR 0x0105 len=2 Default Channel
   03 00
PDR 0x0107 len=2 Temperature Type
   01 00
PDR 0x0202 len=100 3861 Baseline Register Settings
   9b 16 00 02 48 04 48 06 80 08 03 0a 00 0c 00 0e 60 10 a2 12 bc 14 1b
16 00 18 00 1a 00 1c 5c 1e 82 20 20 22 c4 24 17 26 0a 28 0e 2a 20 2c 0c
2e 2d 30 20 32 90 34 18 36 76 38 0a$PDR 0x0203 len=128 3861 Shadow
Register Settings
   00 2c 0c 2e 01 2c 10 2e 02 2c 14 2e 03 2c 18 2e 04 2c 1c 2e 05 2c 20
2e 06 2c 24 2e 07 2c 28 2e 08 2c 2e 2e 09 2c 34 2e 0a 2c 38 2e 0b 2c 3c
2e 0c 2c 3f 2e 0d 2c 43 2e 0e 2c 46$PDR 0x0000 len=2 PDA End Record
   9c 31

best regards
tom



From jar  Sat May 21 11:52:39 2005
From: jar (Jar)
Date: Sat, 21 May 2005 21:52:39 +0300 (EEST)
Subject: which firmware for wl200?
In-Reply-To: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
Message-ID: <3301.192.168.0.150.1116701559.squirrel@kone>


> Hello all!
>
> I've been looking for firmware for my compaq wl200 in this list but what
> i found makes me suspicious - there's a firmware posted by pedro
> estrela:

Read the "Mini-howto on Flashing Intersil Prism Chipsets" at:
http://linux.junsun.net/intersil-prism/

Download http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz and use s1010506.hex
STA firmware from it. The 1.7.0 is newest for wl200 but I have found that the 1.5.6
works best. Note that the WPA is only supported in 1.7.0 version. Note also that you
only have to flash the STA=Station firmware not PRI=Primary. The PRI=0.3.0 is newest
and it is OK.

For flashing the STA firmaware, I have always used the windows utility
http://linux.junsun.net/intersil-prism/WinUpdate-0-7-0.exe. First moved the card to
windows machine and flashed it there, then moved back to Linux machine.

That's because the prism2_srec has always complained about some "incompatibility
issues" with this card and with the s1010506.hex frmware. Maybe it is safe to use
"-i" parameter with prism2_srec to ignore these incompatibility errors?

-- 
Best Regards, Jar



From wlan.20.briony  Sat May 21 12:07:12 2005
From: wlan.20.briony (wlan.20.briony at spamgourmet.com)
Date: Sat, 21 May 2005 21:07:12 +0200
Subject: which firmware for wl200?
In-Reply-To: <3301.192.168.0.150.1116701559.squirrel@kone>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
Message-ID: <20050521210712.2d52bf01.benke@thedonkeynetwork.com>

hey, thanks for the fast reply!

> Read the "Mini-howto on Flashing Intersil Prism Chipsets" at:
> http://linux.junsun.net/intersil-prism/

actually i came from this site to the mailing list cause i was unsure about the info they gave there ;-)

> Download http://www.red-bean.com/~proski/firmware/1.5.6.tar.gz and use s1010506.hex
> STA firmware from it. The 1.7.0 is newest for wl200 but I have found that the 1.5.6
> works best. Note that the WPA is only supported in 1.7.0 version. Note also that you
> only have to flash the STA=Station firmware not PRI=Primary. The PRI=0.3.0 is newest
> and it is OK.

nice to hear that there's even newer firmware! unfortunately i get incompatibility-messages with this file as well :-(
unfortunately the only machine running windows has a nforce2-motherboard, which doesn't work with wl200(as stated by compaq, didn't try yet) - guess i'll have to temporary install windows on some spare space on a some other machine - but maybe some else proofs that the '-i'-flag doesn't cause any harm with prism2_srec?
could you add a comment on why/how the 1.5.6 works better than 1.7.0 for you?

many thanks
thomas




From jar  Sat May 21 12:24:59 2005
From: jar (Jar)
Date: Sat, 21 May 2005 22:24:59 +0300 (EEST)
Subject: which firmware for wl200?
In-Reply-To: <20050521210712.2d52bf01.benke@thedonkeynetwork.com>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
Message-ID: <3366.192.168.0.150.1116703499.squirrel@kone>



> unfortunately the only machine running windows has a nforce2-motherboard, which
> doesn't work with wl200(as stated by compaq, didn't try yet) - guess i'll have to
> temporary install windows on some spare space on a some other machine - but maybe
> some else proofs that the '-i'-flag doesn't cause any harm with prism2_srec?

I guess the flashing _should_ work with '-i'-flag because it is the correct
firmware, but I can't be 100% sure, 99.9% maybe.

> could you add a comment on why/how the 1.5.6 works better than 1.7.0 for you?

Actually only thing I noticed under very short testing period, was that the         
 Link Quality, Signal level and Noise level values becomes randomize after upgrading
1.5.6-->1.7.0. Since the 1.5.6 has always been working great for me (about two years
now) and because I don't need WPA (yet!) but need those values I prefer to use
1.5.6.

-- 
Best Regards, Jar



From wlan.20.briony  Sat May 21 13:18:13 2005
From: wlan.20.briony (wlan.20.briony at spamgourmet.com)
Date: Sat, 21 May 2005 22:18:13 +0200
Subject: which firmware for wl200?
In-Reply-To: <3366.192.168.0.150.1116703499.squirrel@kone>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
Message-ID: <20050521221813.026eb724.benke@thedonkeynetwork.com>

> Actually only thing I noticed under very short testing period, was
> that the         
>  Link Quality, Signal level and Noise level values becomes randomize
>  after upgrading
> 1.5.6-->1.7.0. Since the 1.5.6 has always been working great for me
> (about two years now) and because I don't need WPA (yet!) but need
> those values I prefer to use 1.5.6.

ok, one last question - where do i get 1.7.0 cause the link above
only has 1.7.1 - and which firmware-image will i have to use?
i guess 5 minute rekeying with WEP should be enough for security - or am i wrong?

regards
thomas




From frank  Sat May 21 13:32:29 2005
From: frank (Frank Thieme)
Date: Sat, 21 May 2005 22:32:29 +0200
Subject: which firmware for wl200?
In-Reply-To: <20050521221813.026eb724.benke@thedonkeynetwork.com>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
	<20050521221813.026eb724.benke@thedonkeynetwork.com>
Message-ID: <20050521203229.GC28428@stars.fthieme.net>

On Sat, May 21, 2005 at 10:18:13PM +0200, wlan.20.briony at spamgourmet.com wrote:
> ok, one last question - where do i get 1.7.0 cause the link above
> only has 1.7.1 - and which firmware-image will i have to use?
> i guess 5 minute rekeying with WEP should be enough for security - or am i wrong?

He meant 1.7.1 - I use the same firmware (s1) on a different card...

Bye...Frank



From jar  Sat May 21 13:56:57 2005
From: jar (Jar)
Date: Sat, 21 May 2005 23:56:57 +0300 (EEST)
Subject: which firmware for wl200?
In-Reply-To: <20050521221813.026eb724.benke@thedonkeynetwork.com>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
	<20050521221813.026eb724.benke@thedonkeynetwork.com>
Message-ID: <3579.192.168.0.150.1116709017.squirrel@kone>


> ok, one last question - where do i get 1.7.0 cause the link above
> only has 1.7.1 - and which firmware-image will i have to use?
Yes sorry, i mean 1.7.1 (s1010701.hex).

> i guess 5 minute rekeying with WEP should be enough for security - or am i wrong?

Hard to say, but not 100% safe I guess. I use VPN over wlan connection to achieve
(trying) the 100%, if it is even possible. The WPA2 should be safe as it uses AES.

-- 
Best Regards, Jar



From jar  Sat May 21 13:59:06 2005
From: jar (Jar)
Date: Sat, 21 May 2005 23:59:06 +0300 (EEST)
Subject: which firmware for wl200?
In-Reply-To: <20050521203229.GC28428@stars.fthieme.net>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
	<20050521221813.026eb724.benke@thedonkeynetwork.com>
	<20050521203229.GC28428@stars.fthieme.net>
Message-ID: <3585.192.168.0.150.1116709146.squirrel@kone>


> He meant 1.7.1 - I use the same firmware (s1) on a different card...

How are your iwconfig Link Quality, Signal level and Noise level values? Are they
reasonable?

-- 
Best Regards, Jar



From proski  Sat May 21 17:34:53 2005
From: proski (Pavel Roskin)
Date: Sat, 21 May 2005 20:34:53 -0400
Subject: Symbol Spectrum24 High Rate
In-Reply-To: <25e854e7050517115137c4d769@mail.gmail.com>
References: <25e854e7050517115137c4d769@mail.gmail.com>
Message-ID: <1116722093.15984.2.camel@dv.roinet.com>

Hello, Adam!

On Tue, 2005-05-17 at 13:51 -0500, Adam Roach wrote:
> I have a Symbol Spectrum24 High Rate LA4137 wireless lan card.  I was
> wondering if this is what I need to be using to get it working.

No, this card has Symbol chipset, whereas HostAP requires Prism chipset.
You should use Orinoco driver instead.

-- 
Regards,
Pavel Roskin




From jkmaline  Sat May 21 20:59:03 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 21 May 2005 20:59:03 -0700
Subject: is CRL " certificate revocation list" checked by hostapd or
	openssl in eap-tls?
In-Reply-To: <428C4546.2020204@gmx.de>
References: <428C4546.2020204@gmx.de>
Message-ID: <20050522035903.GJ8114@jm.kir.nu>

On Thu, May 19, 2005 at 09:50:30AM +0200, thomas schorpp wrote:

> # CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
> ca_cert=/etc/hostapd/wpaca/ca/CAcert.pem
> 
> # Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
> server_cert=/etc/hostapd/wpaca/certs/tom3-cert.pem
> 
> no entry for the crl.

The current CVS snapshot has a new configuration variable, check_crl.
This can be used to enable CRL verification. However, the implementation
is still quite minimal and the CRL data needs to be added into the
ca_cert file with something external (e.g., 'wget crlurl' and 'cat
ca.pem crl.pem > cafile.pem). In addition, hostapd needs to be restarted
when CRL is changed.

> i would like to implement this then, to deauthenticate users just simply
> by revoking their certs ;)

Deauthenticating users automatically based on certificate revocation
would require storing certificate information for each associated client
and going through this data whenever the CRL is updated. If rejecting
the next authentication is enough, the current hostapd snapshot should
be able to do this. However, it would be nice to add support for
automatically downloading (at least HTTP and LDAP) and updating CRL
based on CDP from the user certificates.. At least, making it easier to
update CRL without having to restart hostapd would be a good start.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat May 21 21:14:12 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 21 May 2005 21:14:12 -0700
Subject: porting to world radio chips from conexant
In-Reply-To: <29f91651050519025918b68eeb@mail.gmail.com>
References: <29f91651050516023955da987a@mail.gmail.com>
	<20050518023849.GJ8114@jm.kir.nu>
	<29f91651050519025918b68eeb@mail.gmail.com>
Message-ID: <20050522041412.GK8114@jm.kir.nu>

On Thu, May 19, 2005 at 05:59:11AM -0400, alfred hitch wrote:

> The header file which had structure defintion for wpa_even_data, 
> mentions that
> req_ie, resp_ie
> becaon_ie,  are all optional ..

req_ies and resp_ies are optional, if driver is not generating its own
IE for AssocReq. beacon_ies is optional if getting these from scan
results is supported. If both cases apply, EVENT_ASSOCINFO itself is
optional.

> But, in this function code, I see that  we are free'ing any data which
> wud have been part of wpa_s , without checking that the driver while
> passing this event filled in the correct i.e's or not ..

I'm not sure what you refering to with "this function" or "part of
wpa_s". Actually, I'm not sure I understood anything from this
paragraph..

> infact mapping it with drover_broadcom.c
> I see that assoc info driver gives to this funciton is copied into
> "resp"_ie while wpa_supplicant_asocinfo function is using p =
> data->asoc_info.req_ies .

Don't look at driver_broadcom.c for this example.. It is not doing what
it is supposed to be.. The driver interface code is supposed to provide
req_ies from the AssocReq. resp_ies are not really used.

> This indicates usage of req_ies, which has like not even been
> populated in driver ?

wpa_supplicant_associnfo() uses req_ies only if it is set.

> same for beacon frames , driver doesnt passes and we are free'ing and
> memcpy'ing ..

Again, I do not understand what you are refering to with "free'ing and
memcpy'ing" in this context. beacon_ies is used only if it is set.

> Also, if I could ask, of all these 3 (optional ?) ie's which one will
> be needed defintely ..

wpa_supplicant needs to get WPA/RSN IE from Beacon/Probe Response frames
(i.e., the one generated by the AP) and WPA/RSN IE from (Re)AssocReq. It
does not matter how these are coming (i.e., either from EVENT_ASSOCINFO
or from wpa_supplicant setting the IE itself and from scan results).

> in wpa_s
> ap_wpa_ie refers to AP's beacon / resp_ie .. 
> ap_rsn_ie .. for RSN case, same meaning as above
> assoc_wpa_ie, .. what we just sent in association request ?? req_ie 

Yes, this is correct except for resp_ie comment; AP does not include
WPA/RSN IE in AssocResp, they come are from either Beacon or Probe
Response frames.

-- 
Jouni Malinen                                            PGP id EFC895FA



From t.schorpp  Sun May 22 08:06:53 2005
From: t.schorpp (thomas schorpp)
Date: Sun, 22 May 2005 17:06:53 +0200
Subject: is CRL " certificate revocation list" checked by hostapd
	or	openssl in eap-tls?
In-Reply-To: <20050522035903.GJ8114@jm.kir.nu>
References: <428C4546.2020204@gmx.de> <20050522035903.GJ8114@jm.kir.nu>
Message-ID: <4290A00D.8040609@gmx.de>

Jouni Malinen wrote:
> On Thu, May 19, 2005 at 09:50:30AM +0200, thomas schorpp wrote:
> 
> 
>># CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
>>ca_cert=/etc/hostapd/wpaca/ca/CAcert.pem
>>
>># Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
>>server_cert=/etc/hostapd/wpaca/certs/tom3-cert.pem
>>
>>no entry for the crl.
> 
> 
> The current CVS snapshot has a new configuration variable, check_crl.
> This can be used to enable CRL verification. However, the implementation
> is still quite minimal and the CRL data needs to be added into the
> ca_cert file with something external (e.g., 'wget crlurl' and 'cat
> ca.pem crl.pem > cafile.pem). In addition, hostapd needs to be restarted
> when CRL is changed.

thx. ok i'll pull the newest HEAD and take a good look.

i'm courios, since the openssl.org docs state crl functionality on cert
verify functions "unused"... if not outdated.

> 
> 
>>i would like to implement this then, to deauthenticate users just simply
>>by revoking their certs ;)
> 
> 
> Deauthenticating users automatically based on certificate revocation
> would require storing certificate information for each associated client
> and going through this data whenever the CRL is updated. If rejecting
> the next authentication is enough, the current hostapd snapshot should
> be able to do this.

yes. maybe an uneconomically effort if i'm the only one who wants it...
last is sufficent for me.

and deauthentication without stating reason to the client user is not
customer friendly. stating a reason in revocation makes crl's
automatically version 2 as the openssl.org docs state. analysis of
handling by current implementations should apply before.

then supplicants must implement a more comprehensive user notification
of cert revocation reason before disconnecting the last valid session,
i've not seen such yet, only manual validation check in d-link software.
at lower level it looks like hostapd and clients supplicant would enter
endless auth trying loops if theres no notification of revoked cert at
least by accessing servers crl over http what is no more possible after
disconnect then since the client cant authenticate and connect again to
the crl server.
many revoked clients could flood the ap then with fast repeated auth reqs.

so a automatic solution should rather be on the clients side.
and all platforms and manufacturers client-sw is not in hostapd projects
control...

there should be a standard draft then. or it is and i've missed it.

and deauth for the next client attempt could be done easier just by
deleting the client in the eap_user database after notyfing the user
manually or automatically with external services without the need for
complex cryptography handling...

> However, it would be nice to add support for
> automatically downloading (at least HTTP and LDAP) and updating CRL
> based on CDP from the user certificates..

unclear target yet, since all os platforms may have no such CDP comms
running by default even if have implemented it.

pls correct, if i understood something wrong here.

> At least, making it easier to
> update CRL without having to restart hostapd would be a good start.
> 

i'll check if i can afford this and consider implementation after
further analysis and hostapd administrators demand on this list.

quick view on the code looks like all is non-trivial encapsulated in
state machine objects. need some time to rev engineer this.

theres very nice dev documentation for wpasupplicant on the site, is
there something for hostapd?

thx
y
tom





From t.schorpp  Sun May 22 10:33:11 2005
From: t.schorpp (thomas schorpp)
Date: Sun, 22 May 2005 19:33:11 +0200
Subject: is CRL " certificate revocation list" checked by hostapd
	or	openssl in eap-tls? script for cert-management
In-Reply-To: <20050522035903.GJ8114@jm.kir.nu>
References: <428C4546.2020204@gmx.de> <20050522035903.GJ8114@jm.kir.nu>
Message-ID: <4290C257.4060308@gmx.de>

Jouni Malinen wrote:
> On Thu, May 19, 2005 at 09:50:30AM +0200, thomas schorpp wrote:
> 
> 
>># CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
>>ca_cert=/etc/hostapd/wpaca/ca/CAcert.pem
>>
>># Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
>>server_cert=/etc/hostapd/wpaca/certs/tom3-cert.pem
>>
>>no entry for the crl.
> 
> 
> The current CVS snapshot has a new configuration variable, check_crl.
> This can be used to enable CRL verification. However, the implementation
> is still quite minimal and the CRL data needs to be added into the
> ca_cert file with something external (e.g., 'wget crlurl' and 'cat
> ca.pem crl.pem > cafile.pem). In addition, hostapd needs to be restarted
> when CRL is changed.
> 

ok, modified cvonks's script for cert management for revoking and
hostapd in debian.
not tested yet. use with care.

-att-

y
tom
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gencert-hostap
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20050522/51a1d085/attachment.txt 


From regio.rocha  Sun May 22 18:30:33 2005
From: regio.rocha (Regio Rocha)
Date: Sun, 22 May 2005 22:30:33 -0300
Subject: wpa_supplicant for windows
Message-ID: <53cbf33c050522183029bd5c47@mail.gmail.com>

Hi!

I need a wpa_example example for windows XP or other windows.
Anybady has example for help me?

-- 
R?gio Rocha Lopes



From jkmaline  Sun May 22 19:38:57 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 22 May 2005 19:38:57 -0700
Subject: wpa_supplicant for windows
In-Reply-To: <53cbf33c050522183029bd5c47@mail.gmail.com>
References: <53cbf33c050522183029bd5c47@mail.gmail.com>
Message-ID: <20050523023857.GN8114@jm.kir.nu>

On Sun, May 22, 2005 at 10:30:33PM -0300, Regio Rocha wrote:

> I need a wpa_example example for windows XP or other windows.
> Anybady has example for help me?

What do you mean with "example" in this context? Configuration file (it
comes with one..)? Something else?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun May 22 21:04:49 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 22 May 2005 21:04:49 -0700
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
Message-ID: <20050523040449.GO8114@jm.kir.nu>

New versions of Prism2/2.5/3 Host AP driver, wpa_supplicant, and
hostapd were just released and are now available from
http://hostap.epitest.fi/

This release is from the new development branch (0.4.x). Please note
that 0.3.x branch continues to be the current source of stable
releases.

This version includes number of bug fixes for the previous development
version. wpa_supplicant comes now with wpa_gui* which is a GUI version
of wpa_cli. In addition, I have started working on developers'
documentation for the programs. Currently, this is only for
wpa_supplicant, but once this part gets more complete, I would expect to
see similar documentation for hostapd. The current documentation is
available at http://hostap.epitest.fi/wpa_supplicant/devel/


*) http://hostap.epitest.fi/wpa_supplicant/wpa_gui.html
   (since there is now a GUI program included with wpa_supplicant,
   it is, of course, time for screenshots ;-)



hostap-driver:
* fixed beacon frame when moving from monitor mode to master mode
  (workaround for firmware bug that left IBSS IE in the Beacon frames)

hostapd:
* fixed RADIUS server initialization when only auth or acct server
  is configured and the other one is left empty
* driver_madwifi: added support for RADIUS accounting
* driver_madwifi: added preliminary support for compiling against 'BSD'
  branch of madwifi CVS tree
* driver_madwifi: fixed pairwise key removal to allow WPA reauth
  without disassociation
* added support for reading additional certificates from PKCS#12 files
  and adding them to the certificate chain
* fixed RADIUS Class attribute processing to only use Access-Accept
  packets to update Class; previously, other RADIUS authentication
  packets could have cleared Class attribute
* added support for more than one Class attribute in RADIUS packets
* added support for verifying certificate revocation list (CRL) when
  using integrated EAP authenticator for EAP-TLS; new hostapd.conf
  options 'check_crl'; CRL must be included in the ca_cert file for now

wpa_supplicant:
* driver_madwifi: fixed WPA/WPA2 mode configuration to allow EAPOL
  packets to be encrypted; this was apparently broken by the changed
  ioctl order in v0.4.0
* driver_madwifi: added preliminary support for compiling against 'BSD'
  branch of madwifi CVS tree
* added support for EAP-MSCHAPv2 password retries within the same EAP
  authentication session
* added support for password changes with EAP-MSCHAPv2 (used when the
  password has expired)
* added support for reading additional certificates from PKCS#12 files
  and adding them to the certificate chain
* fixed association with IEEE 802.1X (no WPA) when dynamic WEP keys
  were used
* fixed a possible double free in EAP-TTLS fast-reauthentication when
  identity or password is entered through control interface
* display EAP Notification messages to user through control interface
  with "CTRL-EVENT-EAP-NOTIFICATION" prefix
* added GUI version of wpa_cli, wpa_gui; this is not build
  automatically with 'make'; use 'make wpa_gui' to build (this requires
  Qt development tools)
* added 'disconnect' command to control interface for setting
  wpa_supplicant in state where it will not associate before
  'reassociate' command has been used
* added support for selecting a network from the list of all configured
  networks ('wpa_cli select_network <network id>'; this disabled all
  other networks; to re-enable, 'wpa_cli select_network any')
* added support for getting scan results through control interface
* added EAP workaround for PEAPv1 session resumption: allow outer,
  i.e., not tunneled, EAP-Success to terminate session since; this can
  be disabled with eap_workaround=0


-- 
Jouni Malinen                                            PGP id EFC895FA



From josh.howlett  Sun May 22 22:58:23 2005
From: josh.howlett (Josh Howlett)
Date: Mon, 23 May 2005 06:58:23 +0100
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <20050523040449.GO8114@jm.kir.nu>
References: <20050523040449.GO8114@jm.kir.nu>
Message-ID: <429170FF.7010802@bristol.ac.uk>

Jouni Malinen wrote:
> This version includes number of bug fixes for the previous development
> version. wpa_supplicant comes now with wpa_gui* which is a GUI version
> of wpa_cli.

I see it's using qt. Does it compile under Windows and, if so, how 
functional is it?

josh.



From brix  Mon May 23 02:31:31 2005
From: brix (Henrik Brix Andersen)
Date: Mon, 23 May 2005 11:31:31 +0200
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <20050523040449.GO8114@jm.kir.nu>
References: <20050523040449.GO8114@jm.kir.nu>
Message-ID: <1116840691.17259.6.camel@sponge.fungus>

On Sun, 2005-05-22 at 21:04 -0700, Jouni Malinen wrote:
> New versions of Prism2/2.5/3 Host AP driver, wpa_supplicant, and
> hostapd were just released and are now available from
> http://hostap.epitest.fi/

I know you haven't releases a hostap-utils-0.4.1, but there's still a
(dead) link to a that from the above URL.

Sincerely,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050523/50002d7a/attachment.pgp 


From ykchoi  Mon May 23 05:35:00 2005
From: ykchoi (Youngkyu Choi)
Date: Mon, 23 May 2005 21:35:00 +0900
Subject: A question about "retry" item in iwconfig
Message-ID: <20050523124059.CC01713401C@mail.iocaine.com>

 
Hi, all.
 
I'm playing with madwifi based on FC3. My PCICIA card's chipset is Atheros
5212 model.
BTW, it is questionable what the 'retry' item means exactly. My console
shows "Retry:off" when I commanded iwconfig.
At first, I misunderstood the current MAC state did not support the
retransmission of the frame. However, I realized that the MAC retransmission
still worked through inserting 'printk' to the place, where the retry field
of the MAC frame header is masked.
 
In my thought, "Retry: off" means that iwconfig utility families including
'iwpriv' does not allow controlling the retransmission functionality, isn't
it? If my guess is not true, please let me know this clearer. Otherwise, the
display from iwconfig would be rather modified to show the appropriate
meanings.
 
Thanks,
Youngkyu.
---
Youngkyu Choi, Ph. D. Candidate 
Multimedia & Wireless Networking Laboratory (MWNL), School of Electrical
Engineering
Seoul National University
 
Tel: +82-(0)2-880-1755
Cell: +82-(0)18-205-9925
E-mail:  <mailto:ykchoi at mwnl.snu.ac.kr> ykchoi at mwnl.snu.ac.kr
MSN:  <mailto:wastebinchoi at hotmail.com> wastebinchoi at hotmail.com
URL:  <http://mwnl.snu.ac.kr/~ykchoi> http://mwnl.snu.ac.kr/~ykchoi   
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050523/5a2beb26/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 5665 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050523/5a2beb26/attachment.gif 


From togg  Mon May 23 05:59:54 2005
From: togg (Sebastian Weitzel)
Date: Mon, 23 May 2005 14:59:54 +0200
Subject: A question about "retry" item in iwconfig
In-Reply-To: <20050523124059.CC01713401C@mail.iocaine.com>
References: <20050523124059.CC01713401C@mail.iocaine.com>
Message-ID: <20050523145954.u2d8dsiqz868gsgg@webmail.togg.de>

> In my thought, "Retry: off" means that iwconfig utility families including
> 'iwpriv' does not allow controlling the retransmission functionality, isn't
> it? If my guess is not true, please let me know this clearer. Otherwise, the
> display from iwconfig would be rather modified to show the appropriate
> meanings.

Though the hostap mailinglist may not be adequate for this issue I try 
to give you a short answer. Madwifi does up to 10 retries on the hal 
layer. The limit is furthermore specified on compile time. For 
management frames the retry is disabled. -- Regards,
Sebastian Weitzel



From jkmaline  Mon May 23 07:18:25 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 07:18:25 -0700
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <1116840691.17259.6.camel@sponge.fungus>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116840691.17259.6.camel@sponge.fungus>
Message-ID: <20050523141825.GP8114@jm.kir.nu>

On Mon, May 23, 2005 at 11:31:31AM +0200, Henrik Brix Andersen wrote:

> I know you haven't releases a hostap-utils-0.4.1, but there's still a
> (dead) link to a that from the above URL.

Thanks, fixed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 07:22:06 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 07:22:06 -0700
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <429170FF.7010802@bristol.ac.uk>
References: <20050523040449.GO8114@jm.kir.nu> <429170FF.7010802@bristol.ac.uk>
Message-ID: <20050523142206.GQ8114@jm.kir.nu>

On Mon, May 23, 2005 at 06:58:23AM +0100, Josh Howlett wrote:
> Jouni Malinen wrote:
> > This version includes number of bug fixes for the previous development
> > version. wpa_supplicant comes now with wpa_gui* which is a GUI version
> > of wpa_cli.
> 
> I see it's using qt. Does it compile under Windows and, if so, how 
> functional is it?

It should be possible to compile it with Qt/Windows. However, there is
no open source version of Qt/Windows available (yet), so I did not try
doing this. If someone has the commercial version and is willing to
build wpa_gui with it, I would be interested in hearing about the the
results.

wpa_gui has more or less the same functionality as wpa_cli. The main
missing part (from both wpa_cli and wpa_gui) is in adding new networks
and modifying the configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From brix  Mon May 23 09:29:01 2005
From: brix (Henrik Brix Andersen)
Date: Mon, 23 May 2005 18:29:01 +0200
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <20050523040449.GO8114@jm.kir.nu>
References: <20050523040449.GO8114@jm.kir.nu>
Message-ID: <1116865741.18733.3.camel@sponge.fungus>

On Sun, 2005-05-22 at 21:04 -0700, Jouni Malinen wrote:
> New versions of Prism2/2.5/3 Host AP driver, wpa_supplicant, and
> hostapd were just released and are now available from
> http://hostap.epitest.fi/

The ipw_param struct of driver_ipw.c is out of sync with the one used in
ipw2200-1.0.4, causing wpa_supplicant-0.4.1 to fail with WPA. The
attached patch fixes it.

Sincerely,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-0.4.1-ipw.patch
Type: text/x-patch
Size: 391 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050523/adb8519a/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050523/adb8519a/attachment.pgp 


From bmeier  Mon May 23 14:06:04 2005
From: bmeier (Beat Meier)
Date: Mon, 23 May 2005 18:06:04 -0300
Subject: hostapd-0.3.7 with 5213 chipset (5212) and WPA-PSK fails
Message-ID: <429245BC.20606@infovia.com.ar>

Hi

I have the following minic pci cards
  5354 MP PLUS ARIES2 4G: 802.11a/b/g miniPCI Card
I have a client which works fine with this card and an WRT54G from Linksys.
No auth ok, WPA-PSK ok

But with hostapd version 0.3.7 and this card the client cannot connect 
to my hostapd.
Without authorization there is no problem.
I use madwifi driver date 20050311  which I compiled myself

The card has an Atheros chip AR5213A.
Ff I do an lspci there is the following output
00:0d.0 Ethernet controller: Unknown device 168c:0013 (rev 01)

dmesg gives me:
ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
wlan: 0.8.4.5 (EXPERIMENTAL)
ath_rate_onoe: 1.0
ath_pci: 0.9.4.12 (EXPERIMENTAL)
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 
24Mbps 36Mbps 48Mbps 54Mbps
ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: mac 5.9 phy 4.3 radio 3.6
ath0: 802.11 address: 00:02:6f:21:e3:9f
ath0: Use hw queue 0 for WME_AC_BE traffic
ath0: Use hw queue 1 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Atheros 5212: mem=0x80000000, irq=12

If I look in hal/ah_devid.h this ids are only the leading 4 digits ? 
i.e. 168c in my case?
How does the driver know which version of chipset to use?

Does anybody use such a card in hostapd which works?
What could be the problem

Below a snipped ot the logs ...
Client logs before this are equals ...

Thanks for any hint

Beat


Output of client to wrt54g:
***********************************
...
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:0c:41:6e:18:d2
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 
00 00 f1 ee 27 69 95 c5 ea 5f 8e 3e 9b eb 59 e7
 2c 4f 05 25 4a df a9 2d 31 cf a6 ba ff 18 90 a6 32 62 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 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
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 00 f1 ee 27 69 95 c5 ea 5f 8e 3e 9b
 eb 59 e7 2c 4f 05 25 4a df a9 2d 31 cf a6 ba ff 18 90 a6 32 62 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 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 00:0c:41:6e:18:d2 (ver=1)
...
***********************************

Output of client to hostapd:
***********************************
...
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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28 idleWhile=58
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27 idleWhile=57
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:02:6f:21:e3:a3 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
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:02:6f:21:e3:a3
Association event - clear replay counter
Associated to a new BSS: BSSID=00:02:6f:21:e3:a3
No keys have been configured - skip key clearing
Associated with 00:02:6f:21:e3:a3
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
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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
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
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
Wireless event: cmd=0x8b19 len=12
Received 564 bytes of scan results (2 BSSes)
Scan results: 2
...
***********************************

Output of hostapd:
***********************************
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:02:6f:21:e3:9f IEEE 802.11: associated
  New STA
ath0: STA 00:02:6f:21:e3:9f WPA: event 1 notification
ath0: STA 00:02:6f:21:e3:9f WPA: start authentication
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:21:e3:9f key_idx=0
ath0: STA 00:02:6f:21:e3:9f IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:02:6f:21:e3:9f authorized=0
WPA: 00:02:6f:21:e3:9f WPA_PTK_GROUP entering state IDLE
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state AUTHENTICATION
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state AUTHENTICATION2
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITPSK
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state PTKSTART
ath0: STA 00:02:6f:21:e3:9f WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 02 6f 21 e3 9f 00 02 6f 21 e3 a3 88 8e 
02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ae a8 24 ad 1f 9c ac 
23 02 4a 7e 0c 94 7c 39 66 19 da fc d0 02 29 6b 5f 30 a4 d5 c7 f2 0f 33 
a8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
ath0: STA 00:02:6f:21:e3:9f WPA: EAPOL-Key timeout
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state PTKSTART
ath0: STA 00:02:6f:21:e3:9f WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 02 6f 21 e3 9f 00 02 6f 21 e3 a3 88 8e 
02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 02 ae a8 24 ad 1f 9c ac 
23 02 4a 7e 0c 94 7c 39 66 19 da fc d0 02 29 6b 5f 30 a4 d5 c7 f2 0f 33 
a8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
ath0: STA 00:02:6f:21:e3:9f WPA: EAPOL-Key timeout
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state PTKSTART
ath0: STA 00:02:6f:21:e3:9f WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 02 6f 21 e3 9f 00 02 6f 21 e3 a3 88 8e 
02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 03 ae a8 24 ad 1f 9c ac 
23 02 4a 7e 0c 94 7c 39 66 19 da fc d0 02 29 6b 5f 30 a4 d5 c7 f2 0f 33 
a8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
ath0: STA 00:02:6f:21:e3:9f WPA: EAPOL-Key timeout
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state PTKSTART
ath0: STA 00:02:6f:21:e3:9f WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 02 6f 21 e3 9f 00 02 6f 21 e3 a3 88 8e 
02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 04 ae a8 24 ad 1f 9c ac 
23 02 4a 7e 0c 94 7c 39 66 19 da fc d0 02 29 6b 5f 30 a4 d5 c7 f2 0f 33 
a8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 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: 00:02:6f:21:e3:9f WPA_PTK entering state DISCONNECT
madwifi_sta_deauth: addr=00:02:6f:21:e3:9f reason_code=2
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state DISCONNECTED
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:21:e3:9f key_idx=0
ath0: STA 00:02:6f:21:e3:9f IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:02:6f:21:e3:9f authorized=0
ath0: STA 00:02:6f:21:e3:9f IEEE 802.11: deauthenticated due to local 
deauth request
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:02:6f:21:e3:9f IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:02:6f:21:e3:9f IEEE 802.11: associated
  New STA
ath0: STA 00:02:6f:21:e3:9f WPA: event 1 notification
ath0: STA 00:02:6f:21:e3:9f WPA: start authentication
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:21:e3:9f key_idx=0
ath0: STA 00:02:6f:21:e3:9f IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:02:6f:21:e3:9f authorized=0
WPA: 00:02:6f:21:e3:9f WPA_PTK_GROUP entering state IDLE
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state AUTHENTICATION
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state AUTHENTICATION2
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITPSK
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state PTKSTART
ath0: STA 00:02:6f:21:e3:9f WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 02 6f 21 e3 9f 00 02 6f 21 e3 a3 88 8e 
02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ae a8 24 ad 1f 9c ac 
23 02 4a 7e 0c 94 7c 39 66 19 da fc d0 02 29 6b 5f 30 a4 d5 c7 f2 0f 33 
a9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:02:6f:21:e3:9f IEEE 802.11: deassociated
ath0: STA 00:02:6f:21:e3:9f WPA: event 2 notification
madwifi_del_key: addr=00:02:6f:21:e3:9f key_idx=0
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state DISCONNECTED
WPA: 00:02:6f:21:e3:9f WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:21:e3:9f key_idx=0
ath0: STA 00:02:6f:21:e3:9f IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:02:6f:21:e3:9f authorized=0
***********************************





From jkmaline  Mon May 23 14:32:58 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:32:58 -0700
Subject: passive scanning question.
In-Reply-To: <428B93C7.50201@cs.columbia.edu>
References: <428B93C7.50201@cs.columbia.edu>
Message-ID: <20050523213257.GA9428@jm.kir.nu>

On Wed, May 18, 2005 at 03:13:11PM -0400, Andrea G Forte wrote:

> when using passive scanning, the function hostap_passive_scan() is 
> called. It seems that such a function changes channel, waits for some 
> time and then goes to the next channel only. It does not take care of 
> collecting beacons and saving the data of each beacon (SSID, signal 
> strength, etc.). Who takes care of writing this info somewhere in 
> memory? I also see that after we have the data from the beacons, the 
> function create_proc_read_entry() gets called to write this data to 
> file. I am missing the part in the middle between hostap_passive_scan () 
> and create_proc_read_entry().

Beacon frames are processed in hostap_80211_rx.c just like other
management frames in hostap_rx_frame_mgmt().

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 14:37:16 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:37:16 -0700
Subject: hostapd-0.3.7 with 5213 chipset (5212) and WPA-PSK fails
In-Reply-To: <429245BC.20606@infovia.com.ar>
References: <429245BC.20606@infovia.com.ar>
Message-ID: <20050523213716.GB9428@jm.kir.nu>

On Mon, May 23, 2005 at 06:06:04PM -0300, Beat Meier wrote:

> But with hostapd version 0.3.7 and this card the client cannot connect 
> to my hostapd.
> Without authorization there is no problem.
> I use madwifi driver date 20050311  which I compiled myself

I would guess you are using madwifi driver from the CVS mainline which
does not seem to work with hostapd. The version from 'BSD' branch of the
madwifi CVS seems to work much better with hostapd. In addition, I would
use a CVS snapshot of hostapd, since there are couple of driver_madwifi
specific bug fixes that were not included in v0.3.7. Alternatively, you
can also use the 0.3.9-rc1 version from
http://hostap.epitest.fi/releases/testing/.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 14:41:26 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:41:26 -0700
Subject: messages
In-Reply-To: <1115863639.10939.233944378@webmail.messagingengine.com>
References: <1115863639.10939.233944378@webmail.messagingengine.com>
Message-ID: <20050523214126.GC9428@jm.kir.nu>

On Wed, May 11, 2005 at 07:07:19PM -0700, Kev wrote:

> Im using HOSTAP with a DLINK 520 card on a Gentoo server.
> 
> I would like if possible to move all debug messages out of the server
> message log into a hostap specific log file,
> so instead of hostap sending its logs to /var/log/messages could I set
> it up to send to /var/log/hostap
> 
> Is this possible and if so how?

Host AP driver uses printk() for some debug messages. These are usually
captured by klogd and depending on your syslogd configuration, they may
be stored somewhere. It may be somewhat difficult to separate kernel
messages from other kernel messages, but at least it should be possible
to configure all kernel messages to be directed into something else than
/var/log/messages. This would be done in your syslogd (or whatever
tool you use for getting syslog) configuration. Similarly, hostapd
syslog messages could be directed to another file using syslog
configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 14:44:46 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:44:46 -0700
Subject: Kernel oops when cardctl eject
In-Reply-To: <20050513070838.22579.qmail@webmail18.rediffmail.com>
References: <20050513070838.22579.qmail@webmail18.rediffmail.com>
Message-ID: <20050523214446.GD9428@jm.kir.nu>

On Fri, May 13, 2005 at 07:08:38AM -0000, manisha r sankpal wrote:

> I have made some changes in HostAP driver. If a station or AP is inactive for say 5 minutes it is automatically deleted from list that hostap keeps. this is provision provided by HostAP driver earlier. I just changed a code in order to reduce timing from 5 min to 1 sec. 

> Consider a situation where WDS links are made between APs (say AP1 & AP2). AP1 is constantly listening to beacons from AP2 and updating its last received frame (last_rx)variable. I have written a timer which is invoked per second and compares current timing with last received beacon. If AP1 fails to listen beacons from AP2 in a second, it will automatically delete the entry of AP1 from its list by invoking timer handler (it's obivious).. 

Are these changes available somewhere?

> while testing this code,I executed modified HostAP driver on AP1 & AP2. when I did "cardctl eject" on AP2, oops are generated and kernel panics.

Does this happen only with the modifications you did or can you
reproduce this with unmodified version of the driver?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 14:48:30 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:48:30 -0700
Subject: HostAP with ralink card - might it work?
In-Reply-To: <427F5372.6080409@kiste>
References: <427A6C59.9070701@kiste> <20050508062346.GN29395@jm.kir.nu>
	<427F5372.6080409@kiste>
Message-ID: <20050523214830.GE9428@jm.kir.nu>

On Mon, May 09, 2005 at 02:11:30PM +0200, Tim Boneko wrote:

> Sorry for confusing this... I want to use the hostapd for authenticating 
> my clients and setting up wpa encryption instead of wep. Hostapd is 
> installed on my gateway pc (debian sarge), the clients are linux pcs and 
> apples.
> There?s no prism chipset available here, only ralink based cards. 
> (802.11g based cards with kernel drivers are almost impossible to come 
> by in germany)

So you are trying to use hostapd with a Ralink-based card in access
point mode? I would assume that this is not supported since no one has
mentioned working on such combination. I don't know what kind of support
Ralink driver has for AP mode, but I would guess that it could be made
to work, but this will likely require changes both to the driver and
hostapd.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 14:52:39 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 14:52:39 -0700
Subject: hostap clients ?
In-Reply-To: <001b01c557fd$3e937240$0200a8c0@racunar02>
References: <001b01c557fd$3e937240$0200a8c0@racunar02>
Message-ID: <20050523215239.GF9428@jm.kir.nu>

On Fri, May 13, 2005 at 10:49:23PM +0200, hiphin wrote:

> well I'm geting hostap frendly to me now, it is working for me fine since 0.1.12, now I use 3xhostap v3.7 in WDS as you know, I folow this mailing list for the past 2 years ... but ... (there goes part when I ask something)... I always get stanched width bridging.
> 
> this time clients are in bridge, and I did this
> 
> prism2_param wlan0 ap_bridge_packets to 0 (zero)
> 
> that is on hardware level, what is next step in disabling client bridging

You would need to give a bit more detailed explanation of what you are
trying to do and what kind of network configuration you are using.. If
you are using layer 2 bridging to connect number of APs and do not want
any of the client stations to talk directly to eachother, you would
probably need to use something like ebtables to configure filtering that
will only allow packets to be bridged if they are directed to the
default gateway MAC address.

-- 
Jouni Malinen                                            PGP id EFC895FA



From f.de.kruijf  Mon May 23 16:04:22 2005
From: f.de.kruijf (Freek de Kruijf)
Date: Tue, 24 May 2005 01:04:22 +0200
Subject: WPA-PSK problem with Q-TEC 54G and MSI AP54G
In-Reply-To: <20050519022043.GS8114@jm.kir.nu>
References: <200505182320.05903.f.de.kruijf@hetnet.nl>
	<20050519022043.GS8114@jm.kir.nu>
Message-ID: <200505240104.22922.f.de.kruijf@hetnet.nl>

On 19 May 2005 04:20, Jouni Malinen wrote:
> On Wed, May 18, 2005 at 11:20:05PM +0200, Freek de Kruijf wrote:
> > I have a Toshiba laptop with SuSE 9.2, ndiswrapper with PCMCIA Q-TEC
> > Wireless 54G (chipset: Marvell W8300), driver mrv8k51.sys and an Access
> > Point MSI AP54G. I am using wpa_supplicant v0.3.8
> This sounds like a driver specific issue, so I would suggest reporting
> this on the ndiswrapper mailing list.

After a lot of experiments now I have this connection running after 
upgrading the ndiswrapper ( now version 1.2rc1) and wpa_supplicant (now 
version 0.3.8).
Configuration is done with the standard Yast from SuSE 9.2 which prepares a 
wpa_supplicant.conf file.

However it is not very robust at the moment. It works when I have the card 
in the system and I boot the system. I can also boot the system without the 
card, insert the card and after that the connection will come up. Removing 
the card while the system is still running should not be done. It might 
hangup the system and only a power down helps. <Ctrl><Alt><something> will 
not work. Also taking the connection down with "ifdown" may hang the 
system.
A normal shutdown of the system with a working connection works OK.

I still wonder if wpa_supplicant should not do a maximum number of attempts 
to establish a connection. From what I have seen it continues indefinitely 
attepting to make the connection when something goes wrong. In my view it 
should do a maximum number of attepts and then give a failure message to 
the log with some information on where and when.

-- 
Freek



From t.schorpp  Mon May 23 16:23:58 2005
From: t.schorpp (thomas schorpp)
Date: Tue, 24 May 2005 01:23:58 +0200
Subject: HostAP with ralink card - might it work?
In-Reply-To: <20050523214830.GE9428@jm.kir.nu>
References: <427A6C59.9070701@kiste>
	<20050508062346.GN29395@jm.kir.nu>	<427F5372.6080409@kiste>
	<20050523214830.GE9428@jm.kir.nu>
Message-ID: <4292660E.8020500@gmx.de>

Jouni Malinen wrote:
> On Mon, May 09, 2005 at 02:11:30PM +0200, Tim Boneko wrote:
> 
> 
>>Sorry for confusing this... I want to use the hostapd for authenticating 
>>my clients and setting up wpa encryption instead of wep. Hostapd is 
>>installed on my gateway pc (debian sarge), the clients are linux pcs and 
>>apples.
>>There?s no prism chipset available here, only ralink based cards. 
>>(802.11g based cards with kernel drivers are almost impossible to come 
>>by in germany)
> 
> 
> So you are trying to use hostapd with a Ralink-based card in access
> point mode? I would assume that this is not supported since no one has
> mentioned working on such combination. I don't know what kind of support
> Ralink driver has for AP mode, but I would guess that it could be made
> to work, but this will likely require changes both to the driver and
> hostapd.
> 

this feature request has been repeated on railink oss driver
mailist/forums since middle 2004.

it seems to me the oss devteam is not interested to implement this :(

ask them on sourceforge why.



From dimitris  Mon May 23 16:31:54 2005
From: dimitris (Dimitris Kogias)
Date: Mon, 23 May 2005 16:31:54 -0700
Subject: D-Link DWL-900AP+ fails WPA-PSK (was Re: wpa_supplicant WPA-PSK
	pairwise OK, group fails)
In-Reply-To: <428AB714.6010604@gmail.com>
References: <428A180F.6090106@gmail.com> <20050518023151.GI8114@jm.kir.nu>
	<428AB714.6010604@gmail.com>
Message-ID: <429267EA.1040200@gmail.com>

Replying here to close this thread out and to make sure this is archived
in google et al:

Dimitris Kogias wrote:
> Hi Jouni,
> 
> Jouni Malinen wrote:
> 
>>On Tue, May 17, 2005 at 09:13:03AM -0700, Dimitris Kogias wrote:
>>
>>
>>
>>>ipw2200 1.0.3
>>>wpa_supplicant 0.4.0 (debian unstable package).
>>>D-Link DWL-900AP+ access point configured for WPA-PSK.
>>
>>
>>Are you using the latest firmware image on that AP?
> 
> 
> Latest one from D-Link, 3.07, dated 30 December 2003.  Release notes at
> http://support.dlink.com/products/view.asp?productid=DWL%2D900AP%2B%5FrevC
> 
> This is an end-of-life product so they probably won't be releasing any
> firmware updates for it.

Furthermore, the second-level support person I ended up talking to
stated that WPA is an "optional feature" and that as such they won't
support it.

I doubt they even did any QA on it, given its apparent failure to
complete the keying protocol as described previously in this thread, not
just with wpa_supplicant but with WinXP SP2 too.

A new netgear WAG302 worked without a hitch.

D.



From bmeier  Mon May 23 16:50:26 2005
From: bmeier (Beat Meier)
Date: Mon, 23 May 2005 20:50:26 -0300
Subject: hostapd-0.3.7 with 5213 chipset (5212) and WPA-PSK fails
In-Reply-To: <20050523213716.GB9428@jm.kir.nu>
References: <429245BC.20606@infovia.com.ar> <20050523213716.GB9428@jm.kir.nu>
Message-ID: <42926C42.30301@infovia.com.ar>

Jouni Malinen schrieb:

>On Mon, May 23, 2005 at 06:06:04PM -0300, Beat Meier wrote:
>
>  
>
>>But with hostapd version 0.3.7 and this card the client cannot connect 
>>to my hostapd.
>>Without authorization there is no problem.
>>I use madwifi driver date 20050311  which I compiled myself
>>    
>>
>
>I would guess you are using madwifi driver from the CVS mainline which
>does not seem to work with hostapd. The version from 'BSD' branch of the
>madwifi CVS seems to work much better with hostapd. In addition, I would
>use a CVS snapshot of hostapd, since there are couple of driver_madwifi
>specific bug fixes that were not included in v0.3.7. Alternatively, you
>can also use the 0.3.9-rc1 version from
>http://hostap.epitest.fi/releases/testing/.
>
>  
>
I have tried now the newest one of hostapd and wpa_supplicant 
(0.3.9-rc1): The same problem.
I have also used now my old linksys WPC54G with ndis driver. The same thing.
So it don't seem to be madwifi driver.

What about the psk?
I have a Passphrase say "foo&one" and ssid "bar"
I have in hostapd.conf
wpa_passphrase=foo

In wpa_supplicant.conf the output of
/usr/local/sbin/wpa_passphrase bar "foo&one"

I have also tried to insert the generated output in hostapd.conf as 
wpa_psk instead of wpa_passphrase.
Nothing works...

BTW: Why doesn't the key[3] not change even if I change wpa_passphrase? 
What is this key?
Only key[2] changes if I restart even hostapd ...

Any hints how to trace?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050523/4e0ed253/attachment.htm 


From jkmaline  Mon May 23 17:52:42 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 17:52:42 -0700
Subject: hostapd-0.3.7 with 5213 chipset (5212) and WPA-PSK fails
In-Reply-To: <42926C42.30301@infovia.com.ar>
References: <429245BC.20606@infovia.com.ar> <20050523213716.GB9428@jm.kir.nu>
	<42926C42.30301@infovia.com.ar>
Message-ID: <20050524005242.GG9428@jm.kir.nu>

On Mon, May 23, 2005 at 08:50:26PM -0300, Beat Meier wrote:
> Jouni Malinen schrieb:
> >I would guess you are using madwifi driver from the CVS mainline which
> >does not seem to work with hostapd. The version from 'BSD' branch of the
> >madwifi CVS seems to work much better with hostapd. In addition, I would
> >use a CVS snapshot of hostapd, since there are couple of driver_madwifi
> >specific bug fixes that were not included in v0.3.7. Alternatively, you
> >can also use the 0.3.9-rc1 version from
> >http://hostap.epitest.fi/releases/testing/.

> I have tried now the newest one of hostapd and wpa_supplicant 
> (0.3.9-rc1): The same problem.

Please note what I wrote about madwifi mainline version not working with
hostapd.. That "Alternatively" was only for hostapd CVS snapshot; you
still need to get 'BSD' branch of madwifi to get this working.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 18:36:02 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 18:36:02 -0700
Subject: Host AP/hostapd/wpa_supplicant - new development release v0.4.1
In-Reply-To: <1116865741.18733.3.camel@sponge.fungus>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116865741.18733.3.camel@sponge.fungus>
Message-ID: <20050524013602.GH9428@jm.kir.nu>

On Mon, May 23, 2005 at 06:29:01PM +0200, Henrik Brix Andersen wrote:
> On Sun, 2005-05-22 at 21:04 -0700, Jouni Malinen wrote:
> > New versions of Prism2/2.5/3 Host AP driver, wpa_supplicant, and
> > hostapd were just released and are now available from
> > http://hostap.epitest.fi/
> 
> The ipw_param struct of driver_ipw.c is out of sync with the one used in
> ipw2200-1.0.4, causing wpa_supplicant-0.4.1 to fail with WPA. The
> attached patch fixes it.

And this would be out of sync with the latest ipw2100 release, wouldn't
it? wpa_supplicant shares a single driver interface for ipw2x00 drivers.
In other words, I cannot apply this unless the drivers are synced or
someone can confirm that this change works with both of the drivers.

I'm not too concerned if the wpa_supplicant development branch is
temporarily out of sync with the latest driver release, but this should
not be allowed for the stable 0.3.x branch. I was planning on releasing
0.3.9 later this week and the driver_ipw changes are already in that
branch. However, this means that either the wpa_supplicant release will
be waiting for ipw2100 driver to sync up (i.e., to get a real release to
replace 1.1.0) or I'll just revert the 64-bit fixes from driver_ipw.c
for now (assuming that gets wpa_supplicant working with both ipw2100 and
ipw2200)..

Unfortunately, I do not have either ipw2100 or ipw2200 in my test setup,
so I'm depending on someone else in testing these and coming up with an
answer on whether I can release wpa_supplicant 0.3.9 with the current
changes and this extra 32-byte padding. No one seem to have done this
with 0.3.9-rc1, since that would fail in the same way with
ipw2200-1.0.4..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon May 23 22:55:58 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 23 May 2005 22:55:58 -0700
Subject: [Ipw2100-devel] Re: Host AP/hostapd/wpa_supplicant - new
	development release v0.4.1
In-Reply-To: <1116910752.3985.59.camel@debian.sh.intel.com>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116865741.18733.3.camel@sponge.fungus>
	<1116910752.3985.59.camel@debian.sh.intel.com>
Message-ID: <20050524055558.GD8082@jm.kir.nu>

On Tue, May 24, 2005 at 12:59:12PM +0800, Zhu Yi wrote:
> On Mon, 2005-05-23 at 18:29 +0200, Henrik Brix Andersen wrote:
> > The ipw_param struct of driver_ipw.c is out of sync with the one used in
> > ipw2200-1.0.4, causing wpa_supplicant-0.4.1 to fail with WPA. The
> > attached patch fixes it.

> Thank you Brix. Seems Jouni forgot to merge this part. I'll resend to
> him.

That would probably be partly forgotten, but more so because it seemed
to break compatibility with older driver versions. Anyway, I added this
patch to wpa_supplicant (both devel and stable branch). If I understood
correctly, this will require an update for the ipw2100 driver.

I made a new release candidate (rc2) of wpa_supplicant 0.3.9. I would
appreciate it if someone could confirm that this works with
ipw2200-1.0.4 and also let me know once a new version of ipw2100 has
been released and tested to work with wpa_supplicant 0.3.9-rc2 so that I
can release the next version of wpa_supplicant from the stable branch.

http://hostap.epitest.fi/releases/testing/wpa_supplicant-0.3.9-rc2.tar.gz

-- 
Jouni Malinen                                            PGP id EFC895FA



From brix  Tue May 24 00:35:59 2005
From: brix (Henrik Brix Andersen)
Date: Tue, 24 May 2005 09:35:59 +0200
Subject: [Ipw2100-devel] Re: Host AP/hostapd/wpa_supplicant - new
	development release v0.4.1
In-Reply-To: <20050524055558.GD8082@jm.kir.nu>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116865741.18733.3.camel@sponge.fungus>
	<1116910752.3985.59.camel@debian.sh.intel.com>
	<20050524055558.GD8082@jm.kir.nu>
Message-ID: <1116920159.14606.2.camel@sponge.fungus>

On Mon, 2005-05-23 at 22:55 -0700, Jouni Malinen wrote: 
> That would probably be partly forgotten, but more so because it seemed
> to break compatibility with older driver versions. Anyway, I added this
> patch to wpa_supplicant (both devel and stable branch). If I understood
> correctly, this will require an update for the ipw2100 driver.

Correct. I will need a new release of the ipw2100 driver as noted in
http://www.bughost.org/bugzilla/show_bug.cgi?id=678

> I made a new release candidate (rc2) of wpa_supplicant 0.3.9. I would
> appreciate it if someone could confirm that this works with
> ipw2200-1.0.4 and also let me know once a new version of ipw2100 has
> been released and tested to work with wpa_supplicant 0.3.9-rc2 so that I
> can release the next version of wpa_supplicant from the stable branch.

I will test wpa_supplicant-0.3.9-rc2 against ipw2200-1.0.4 in a couple
of hours, and against ipw2100-1.1.x once it is released.

Sincerely,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050524/f02ce674/attachment.pgp 


From david.anderson  Tue May 24 00:44:54 2005
From: david.anderson (David Anderson)
Date: Tue, 24 May 2005 09:44:54 +0200
Subject: Multiple stage WEP keying with wpa_supplicant
Message-ID: <4292DB76.7030507@calixo.net>

Hello,

I am trying to authenticate my laptop to my university's wireless 
network (currently in the early beta phase) using wpa_supplicant. The 
engineer setting up the wifi access only gave out a manual for 
authenticating with Windows XP, so I'm trying to transpose that and the 
few (fairly confusing) mails sent by the engineer in question.

 From what I'm able to understand, I need to:
  - Explicitely set an ssid and static WEP key to associate to the AP
  - Perform 802.1x auth using PEAP/MSCHAPv2, bypassing the PEAP 
certificate checks
  - Get hold of a dynamically generated WEP key given out on successful 
authentication and use it instead of the association key.

My first question is more of a general question about 
authentication/keying methods. What is the exact protocol collage that 
would form PEAP/MSCHAPv2 auth with dynamic WEP keying? Does the example 
block entitled "IEEE 802.1X/EAPOL with dynamically generated WEP keys" 
fit what I'm talking about here? Does any of the above procedure I 
deduced make any sense in regard with your past experiences of wireless 
setups?

My second question concerns the capabilities of wpa_supplicant. Is it 
possible to define a network block that'd make wpa_supplicant first 
associate using a given (static) ssid and WEP key, then perform 
authentication and replace the WEP key with what the authenticator 
returns? How would I define this in a network block?
 From my understanding of wpa_supplicant, it would manage the second 
part (auth + keying) with no problem if I explicitely set the essid and 
first WEP key; is there a way to automate this as a part of 
wpa_supplicant's scanning phase?

Thanks in advance for your help
David Anderson.



From brix  Tue May 24 03:54:52 2005
From: brix (Henrik Brix Andersen)
Date: Tue, 24 May 2005 12:54:52 +0200
Subject: [Ipw2100-devel] Re: Host AP/hostapd/wpa_supplicant - new
	development release v0.4.1
In-Reply-To: <1116920159.14606.2.camel@sponge.fungus>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116865741.18733.3.camel@sponge.fungus>
	<1116910752.3985.59.camel@debian.sh.intel.com>
	<20050524055558.GD8082@jm.kir.nu>
	<1116920159.14606.2.camel@sponge.fungus>
Message-ID: <1116932092.14215.6.camel@sponge.fungus>

On Tue, 2005-05-24 at 09:35 +0200, Henrik Brix Andersen wrote:
> I will test wpa_supplicant-0.3.9-rc2 against ipw2200-1.0.4 in a couple
> of hours, and against ipw2100-1.1.x once it is released.

Unfortunately, I am only able to test it with no encryption at my
current location (which works fine) - I will test with WPA-PSK TKIP when
I return home in a couple of hours.

./Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050524/35f2e86b/attachment.pgp 


From brix  Tue May 24 07:39:27 2005
From: brix (Henrik Brix Andersen)
Date: Tue, 24 May 2005 16:39:27 +0200
Subject: [Ipw2100-devel] Re: Host AP/hostapd/wpa_supplicant - new
	development release v0.4.1
In-Reply-To: <1116932092.14215.6.camel@sponge.fungus>
References: <20050523040449.GO8114@jm.kir.nu>
	<1116865741.18733.3.camel@sponge.fungus>
	<1116910752.3985.59.camel@debian.sh.intel.com>
	<20050524055558.GD8082@jm.kir.nu>
	<1116920159.14606.2.camel@sponge.fungus>
	<1116932092.14215.6.camel@sponge.fungus>
Message-ID: <1116945567.14215.8.camel@sponge.fungus>

On Tue, 2005-05-24 at 12:54 +0200, Henrik Brix Andersen wrote:
> Unfortunately, I am only able to test it with no encryption at my
> current location (which works fine) - I will test with WPA-PSK TKIP when
> I return home in a couple of hours.

WPA-PSK TKIP works fine with wpa_supplicant-0.3.9-rc2 and ipw2200-1.0.4.

Regards,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050524/2e964852/attachment.pgp 


From pkolyvas  Tue May 24 08:04:32 2005
From: pkolyvas (Petros Kolyvas)
Date: Tue, 24 May 2005 11:04:32 -0400
Subject: [Ipw2100-devel] Re: Host AP/hostapd/wpa_supplicant -
	new	development release v0.4.1
In-Reply-To: <1116945567.14215.8.camel@sponge.fungus>
References: <20050523040449.GO8114@jm.kir.nu>	<1116865741.18733.3.camel@sponge.fungus>	<1116910752.3985.59.camel@debian.sh.intel.com>	<20050524055558.GD8082@jm.kir.nu>	<1116920159.14606.2.camel@sponge.fungus>	<1116932092.14215.6.camel@sponge.fungus>
	<1116945567.14215.8.camel@sponge.fungus>
Message-ID: <BAYC1-PASMTP03BF9EF993EB354C8125D9D60D0@cez.ice>

Henrik Brix Andersen wrote:
> On Tue, 2005-05-24 at 12:54 +0200, Henrik Brix Andersen wrote:
> 
>>Unfortunately, I am only able to test it with no encryption at my
>>current location (which works fine) - I will test with WPA-PSK TKIP when
>>I return home in a couple of hours.
> 
> 
> WPA-PSK TKIP works fine with wpa_supplicant-0.3.9-rc2 and ipw2200-1.0.4.
> 
> Regards,
> Brix
> 

WPA-PSK CCMP works fine with wpa_supplicant-0.3.9-rc2 and ipw2200-1.0.4 
here.

Pk



From jcromie  Tue May 24 12:53:35 2005
From: jcromie (Jim Cromie)
Date: Tue, 24 May 2005 13:53:35 -0600
Subject: which firmware for wl200?
In-Reply-To: <3366.192.168.0.150.1116703499.squirrel@kone>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>	<3301.192.168.0.150.1116701559.squirrel@kone>	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
Message-ID: <4293863F.5090708@divsol.com>

Jar wrote:

>  
>
>>unfortunately the only machine running windows has a nforce2-motherboard, which
>>doesn't work with wl200(as stated by compaq, didn't try yet) - guess i'll have to
>>temporary install windows on some spare space on a some other machine - but maybe
>>some else proofs that the '-i'-flag doesn't cause any harm with prism2_srec?
>>    
>>
>
>I guess the flashing _should_ work with '-i'-flag because it is the correct
>firmware, but I can't be 100% sure, 99.9% maybe.
>
>  
>
>>could you add a comment on why/how the 1.5.6 works better than 1.7.0 for you?
>>    
>>
>
>Actually only thing I noticed under very short testing period, was that the         
> Link Quality, Signal level and Noise level values becomes randomize after upgrading
>1.5.6-->1.7.0. Since the 1.5.6 has always been working great for me (about two years
>now) and because I don't need WPA (yet!) but need those values I prefer to use
>1.5.6.
>
>  
>
FYI - you can use firmware geared for RAM, and avoid the risks of flashing.
Assuming you can find an R version of the same firmware rev.

I use this in my /etc/modprobe.conf, which triggers an 'upgrade' when 
the card is plugged in.

alias wlan0 hostap
install hostap modprobe --ignore-install hostap ; 
/usr/local/bin/prism2_srec -ir wlan0 /etc/firmware/r1010504.hex





From jar  Tue May 24 13:00:23 2005
From: jar (Jar)
Date: Tue, 24 May 2005 23:00:23 +0300
Subject: which firmware for wl200?
In-Reply-To: <4293863F.5090708@divsol.com>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>	<3301.192.168.0.150.1116701559.squirrel@kone>	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>	<3366.192.168.0.150.1116703499.squirrel@kone>
	<4293863F.5090708@divsol.com>
Message-ID: <429387D7.4050401@pcuf.fi>

Jim Cromie wrote:

> FYI - you can use firmware geared for RAM, and avoid the risks of flashing.
> Assuming you can find an R version of the same firmware rev.
> 
> I use this in my /etc/modprobe.conf, which triggers an 'upgrade' when 
> the card is plugged in.
> 
> alias wlan0 hostap
> install hostap modprobe --ignore-install hostap ; 
> /usr/local/bin/prism2_srec -ir wlan0 /etc/firmware/r1010504.hex

Oh yes, the latest RAM versions for wl200 are r1010506.hex (1.5.6) and 
r1010701.hex (1.7.1). Should be found also from 
http://www.red-bean.com/~proski/firmware/.

-- 
Best Regards, Jar



From Stephane.DELORT  Wed May 25 02:01:50 2005
From: Stephane.DELORT (DELORT Stephane)
Date: Wed, 25 May 2005 11:01:50 +0200
Subject: hostap, wpa_supplicant and wifi pcmcia cards
Message-ID: <200505250849.j4P8nId2001063@harik.murex.com>

Hello @ll,

I am about to buy a pcmcia card to carry out tests in our new wifi network. As this network configured to use PEAP/Mschap v2, I need a card able to deal with these protocols.
My investigations lead me to atheros based chipset cards. Shortlisting the cards given in FreeBSD ath driver man-page with the pcmcia criteria, it appears that none of them is currently able to do WPA2 and 802.11x.

However, since they have the atheros chipset, these cards can be used with hostap for RF monitoring and with wpa_supplicant (read from the wpa_supplicant website).

Is it really possible to use WPA2 ant PEAP/mschap v2 with a card which specifications do not mention it ?
(actually, there is either no record of these cards to run under linux/unix systems on their manufacturer's website)

Here is a list of the cards I selected. It would be really interesting if I can have feedback of people knowing/using these cards.

D-link DWL-AG650
D-link DWL-G650B
Linksys WPC55AG
Netgear WAG511  (seems to be very common in europe and maybe be a piece of choice)
Orinoco 8480
3com 3CRPAG175 (support of WPA2 and PEAP can be read on 3com website; it also have an X-jack antenna for improved transmission skills)

Thanks in advance for any advice,
St?phane



From nll  Wed May 25 02:49:21 2005
From: nll (Nicolas Labrosse)
Date: Wed, 25 May 2005 10:49:21 +0100
Subject: Problem with WPA-PSK
In-Reply-To: <20050508063931.GQ29395@jm.kir.nu>
References: <42777855.2050005@aber.ac.uk> <20050508063931.GQ29395@jm.kir.nu>
Message-ID: <42944A21.6050208@aber.ac.uk>

Jouni Malinen wrote:
> On Tue, May 03, 2005 at 02:10:45PM +0100, Nicolas Labrosse wrote:
> 
> 
>>I want to use Wifi on my laptop and I use wpa_supplicant with atheros card AR5212. It works if I choose WEP encryption but I can't get it to work if I choose WPA-PSK.
> 
> 
> What AP are you using? Can you please send a wpa_supplicant debug log
> without removing the packet dumps ("obscured" in the log you sent)? If
> you can easily capture a packet log, e.g., with tcpdump or Ethereal,
> from the client ('ifconfig ath0 up' and start sniffer before starting
> wpa_supplicant), it could also be useful for looking at what is
> happening.

My AP is a SWEEX wireless modem/router with conexant chipset. The firmware version for WPA is CX_WLANSEC_4.2.0
I have no experience with packet capture... If you really need it I will try to have a look at it but I actually have rare occasions to play with my wireless settings.
I've upgraded madwifi-driver and madwifi-tools to version 0.1_pre20050420 on my gentoo box. I've tried to upgrade wpa_supplicant to versions 0.4.* but I had to come back to stable 0.3.8 as I got other problems (ioctl[SIOCSIWPMKSA]: Operation not supported )

Anyway: a more complete debug log can be found there: http://users.aber.ac.uk/nll/wpa_output.txt
Sorry, it's a bit long, but I don't know what piece of information is the most useful to you... I've left wpa_supplicant running for about 1 minute. It ends when I hit Ctrl-C (l. 1079 in the log, or 8 lines from the end)

> 
> 
>>Associated with 00:05:b4:07:e9:91
> 
> 
>>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 idleWhile=59
>>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
>>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 idleWhile=55
>>EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 idleWhile=54
>>RX EAPOL from 00:05:b4:07:e9:8e
> 
> 
> This is somewhat odd behavior from the AP. First, it takes six seconds
> to send out the first EAPOL-Key frame and the frame seems to be coming
> from another MAC address. Do you happen to know whether this address
> would be the MAC address of the wired interface?
> 

The second one is the MAC address of the modem/router (LAN). The first one is the AP:
WLAN Driver(Marconi) : v3.0.5
Boot Loader Version : v3.1.1
Upper MAC Version : M_UM_3.1.20
Lower MAC Version : M2_LM_D2959SC_3.1.41
AP BSSID: 00:05:B4:07:E9:91 

Thanks a million for your help!

Nicolas




From laenrek  Wed May 25 05:39:40 2005
From: laenrek (Simon Santesteban)
Date: Wed, 25 May 2005 14:39:40 +0200 (CEST)
Subject: EAPOL-Key timeout s in 1/4 msg of 4-Way Handshake
Message-ID: <20050525123940.37575.qmail@web26602.mail.ukl.yahoo.com>

Hello

Im trying to setup hostapd with an atheros card.
I compiled madwifi and hostap, and tried different
versions (madwifi-head, madwifi-bsd, hostap-0.3.7,
hostap-0.4.1), apply some patches, but allways end
with the same behaviour: WPA: EAPOL-Key timeout in 1/4
msg of handshake

Hostap says:

# hostapd /root/wireless-wpa/hostapd2.conf

Configuration file: /root/wireless-wpa/hostapd2.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:02:6f:20:cf:a5 and
ssid 'wifi'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 2f c6 f0 ad 6a 5f f5 51 e1 be
9d a7 cd 9b 9b 0e eb ce 30 27 d2 f8 97 b1 02 69 53 44
d5 40 1b 36
GTK - hexdump(len=32): 52 33 25 5b 95 1b 40 b3 ea d2
01 c6 dc 63 09 f2 0a 33 0c 72 97 a5 2b c1 2e 6b c1 c5
d3 83 b1 48
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00
key_idx=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=3
Deauthenticate all stations
l2_packet_receive - recv: Network is down
Wireless event: cmd=0x8b19 len=12
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:80:5a:22:c2:7e IEEE 802.11: associated
  New STA
ath0: STA 00:80:5a:22:c2:7e WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:80:5a:22:c2:7e
ath0: STA 00:80:5a:22:c2:7e WPA: start authentication
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:80:5a:22:c2:7e key_idx=0
ath0: STA 00:80:5a:22:c2:7e IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:80:5a:22:c2:7e
authorized=0
WPA: 00:80:5a:22:c2:7e WPA_PTK_GROUP entering state
IDLE
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state
AUTHENTICATION
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state
AUTHENTICATION2
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state INITPSK
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state PTKSTART
ath0: STA 00:80:5a:22:c2:7e WPA: sending 1/4 msg of
4-Way Handshake
TX EAPOL - hexdump(len=113): 00 80 5a 22 c2 7e 00 02
6f 20 cf a5 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00
00 00 00 00 01 b9 da f1 56 3d 7d 7f e9 85 7b f3 23 82
a5 47 f8 77 50 00 e5 39 23 51 df c1 c0 d9 38 b2 e4 11
75 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ath0: STA 00:80:5a:22:c2:7e WPA: EAPOL-Key timeout
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state PTKSTART
ath0: STA 00:80:5a:22:c2:7e WPA: sending 1/4 msg of
4-Way Handshake
TX EAPOL - hexdump(len=113): 00 80 5a 22 c2 7e 00 02
6f 20 cf a5 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00
00 00 00 00 02 b9 da f1 56 3d 7d 7f e9 85 7b f3 23 82
a5 47 f8 77 50 00 e5 39 23 51 df c1 c0 d9 38 b2 e4 11
75 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Wireless event: cmd=0x8c02 len=101
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:80:5a:22:c2:7e
rx_packets=0
tx_packets=2
rx_bytes=0
tx_bytes=214
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:80:5a:22:c2:7e IEEE 802.11: deassociated
ath0: STA 00:80:5a:22:c2:7e WPA: event 2 notification
madwifi_del_key: addr=00:80:5a:22:c2:7e key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state
DISCONNECTED
WPA: 00:80:5a:22:c2:7e WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:80:5a:22:c2:7e key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:80:5a:22:c2:7e IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:80:5a:22:c2:7e
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Signal 2 received - terminating
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=3
Deauthenticate all stations
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0



Im using kernel 2.6.11...
some of you succeded doing this, didnt u? please help
I just want to setup wpa-psk

thanks in advance


		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, m?s seguridad 
http://correo.yahoo.es



From Stephane.DELORT  Wed May 25 05:55:16 2005
From: Stephane.DELORT (DELORT Stephane)
Date: Wed, 25 May 2005 14:55:16 +0200
Subject: hostap, wpa_supplicant and wifi pcmcia cards
Message-ID: <200505251243.j4PCghd2016669@harik.murex.com>

Re,

warm thanks to Tilman and thomas for your help.

I selected both the netgear WAG511 and the 3com 3CRPAG175. They should use atheros chipset - to be verified on the card - and are known to work with madwifi and hostap.
Moreover they can be bought easily in Europe.

Does anyone know what is the reason for the twice higher price of the 3 com in regard of the netgear's ?
Even if their is a 2Dbm gap between their transmission power I do not see any big diference.

regards,
St?phane



-----Message d'origine-----
De : Tilman Schoop [mailto:Tilman.Schoop at dsa-ac.de]
Envoy? : mercredi 25 mai 2005 11:37
? : DELORT Stephane
Objet : Re: hostap, wpa_supplicant and wifi pcmcia cards


Hi Stephane,

I have wpa_supplicant with madwifi driver successfully and without
problems running on a 3com 3CRPAG175 card. Configuration for WPA
(EAP/TLS+TKIP); running in a WLAN network with 802.11b/g APs.
host is a i386 platform. I also want to use it on an ARM processor based
system, but at the moment I haven?t tested it.
Greatest problem with the cards is to find a combination of
wpa_supplicant, driver, chipset support.
At the moment I have no experiences with wpa2 but I don`t think
this is a great problem, because if the before mentioned combination
is running, I (teoretically) have support for all protocols that
wpa_supplicant supports.

hope that helps

Greetings
Tilman

DELORT Stephane schrieb:
> Hello @ll,
> 
> I am about to buy a pcmcia card to carry out tests in our new wifi network. As this network configured to use PEAP/Mschap v2, I need a card able to deal with these protocols.
> My investigations lead me to atheros based chipset cards. Shortlisting the cards given in FreeBSD ath driver man-page with the pcmcia criteria, it appears that none of them is currently able to do WPA2 and 802.11x.
> 
> However, since they have the atheros chipset, these cards can be used with hostap for RF monitoring and with wpa_supplicant (read from the wpa_supplicant website).
> 
> Is it really possible to use WPA2 ant PEAP/mschap v2 with a card which specifications do not mention it ?
> (actually, there is either no record of these cards to run under linux/unix systems on their manufacturer's website)
> 
> Here is a list of the cards I selected. It would be really interesting if I can have feedback of people knowing/using these cards.
> 
> D-link DWL-AG650
> D-link DWL-G650B
> Linksys WPC55AG
> Netgear WAG511  (seems to be very common in europe and maybe be a piece of choice)
> Orinoco 8480
> 3com 3CRPAG175 (support of WPA2 and PEAP can be read on 3com website; it also have an X-jack antenna for improved transmission skills)
> 
> Thanks in advance for any advice,
> St?phane
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap


-- 
Tilman Schoop
Fa. DSA - Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany
Email: ts at dsa-ac.de
Tel.: +49-2408-9492-661
Fax.: +49-2408-9492-92



From maccari-thisaintpartofmyaddress-  Wed May 25 07:55:26 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Wed, 25 May 2005 16:55:26 +0200
Subject: receive custom IE in wpa_supplicant
Message-ID: <20050525145526.GB31154@lenst.det.unifi.it>


I was able to make hostapd add a custom IE in beacon frames, I see the IE
pass over the net, but is there a way I can get that data in wpa_supplicant
code?
I'd like the AP to sponsor it's IP address to have the client change its
default route when doing handoff.

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-  Wed May 25 08:30:28 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Wed, 25 May 2005 17:30:28 +0200
Subject: multiple wpa_supplicant on same interface
Message-ID: <20050525153028.GA8249@lenst.det.unifi.it>

what is the technical reason why there can't be multiple wpa_supplicant
running on the same phisical interface?. is there a way to have different
supplicant on different virtual interfaces ?

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 and0806  Wed May 25 09:23:32 2005
From: and0806 (and hansen)
Date: Wed, 25 May 2005 18:23:32 +0200 (CEST)
Subject: EAPOL-Key timeout s in 1/4 msg of 4-Way Handshake
Message-ID: <20050525162333.57484.qmail@web51104.mail.yahoo.com>

Hi.

I have the same problem here, see my previous messages
"psk AUTHENTICATED but no connection"
then i saw that i have to use hostapd bsd branch
so i ended up with the same output as you have
I have tested this, mixed up in any thinkable way
hostapd-0.3.7
hostapd-0.3.9-rc1
hostapd-cvs
madwifi-20050511
madwifi-20050522
madwifi-20050523
madwifi-bsd-branch
wpa_supplicant-0.3.8
wpa_supplicant-cvs
2.6.8.1-24mdk kernel (mandrake10.1)
2.6.11.10 kernel

and my final try
will be to test again but with kernel 2.6.10
if thats not helping either I'll give up
and wait for a future more stable releases of those
components, i can't develop myself so i guess i just
have to wait.
If you find a solution then make a post.

Regards Lasse



From and0806  Wed May 25 10:02:43 2005
From: and0806 (and hansen)
Date: Wed, 25 May 2005 19:02:43 +0200 (CEST)
Subject: hostap, wpa_supplicant and wifi pcmcia cards
Message-ID: <20050525170243.33021.qmail@web51109.mail.yahoo.com>

Hi St?phane

Im sorry that i first saw you messages now, but
i have a fight with madwifi and hostapd
I'm all most about to give up, see threads

psk AUTHENTICATED but no connection
and
EAPOL-Key timeout s in 1/4 msg of 4-Way Handshake
and
Re:  EAPOL-Key timeout s in 1/4 msg of 4-Way Handshake

madwifi and wpa_supplicant is working
but madwifi and hostapd seems broken
at the present moment
my atheros cards is allnet 0281 and 0282
they use the ar5212 chip, so you can hope that
that yours is ar5210 or ar5211
I can't get ar5212 to play with madwifi and hostapd
I have tested more than a week now :(
then one can try the prism54, but I just switched from
from the prism54 because my card died on me
and its almost impossible to find a card that
uses the prism54 chipset, for some reason the
manufactures
don't say what kind of chip they uses, and they switch
chipsets but not the name f.eks. SMC2835W. exists in
3-4 different versions, but that seems different with
the atheros based cards, here manufactures say its a
atheros based card, don`t ask why.
I hope you will have success in your testings, and if
you do, then post a detailed explanation ;)

Regards Lasse


>Re,
>
>warm thanks to Tilman and thomas for your help.
>
>I selected both the netgear WAG511 and the 3com
3CRPAG175. They should 
>use atheros chipset - to be verified on the card -
and are known to 
>work with madwifi and hostap.
>Moreover they can be bought easily in Europe.
>
>Does anyone know what is the reason for the twice
higher price of the 3 
>com in regard of the netgear's ?
>Even if their is a 2Dbm gap between their
transmission power I do not 
>see any big diference.
>
>regards,
>St?phane




From abagri  Wed May 25 11:46:56 2005
From: abagri (Abhijit Bagri)
Date: Wed, 25 May 2005 14:46:56 -0400
Subject: Help for best card
Message-ID: <a22464ef050525114666ae6e95@mail.gmail.com>

Hi,

I am trying to implement an experimental protocol (MAC layer). I might
need to tweak a bit with the hostap cod for that. I wanted to know
what card(commercial brand name for a pcmcia slot pls) will be best
suited to work with hostap. We have laready decided to work with
hostap

My system is(I dont know if any of you will need this):

RHL 9.0
Pentium M 745 1.8 GHz

It will also be great help if you could inform me about availablity of the card

tia
abhijit



From devel  Wed May 25 13:04:29 2005
From: devel (Travis J. Weaver)
Date: Wed, 25 May 2005 16:04:29 -0400
Subject: kick all clients after iwconfig change
Message-ID: <005701c56164$f6438090$0a00a8c0@Oberon.local>

Hello list,

    Is there a way to kick all clients off after an iwconfig change? Instead of:

        iwpriv wlan0 kickmac <hwaddr>

    is there something like:

        iwpriv wlan0 kickmac *    (of course this command does not work, for I have tried it)

    I just want all associated clients to re-associate after a change in iwconfig to the AP. Thanks.

Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050525/d97c0af1/attachment.htm 


From jar  Wed May 25 13:07:46 2005
From: jar (Jar)
Date: Wed, 25 May 2005 23:07:46 +0300
Subject: kick all clients after iwconfig change
In-Reply-To: <005701c56164$f6438090$0a00a8c0@Oberon.local>
References: <005701c56164$f6438090$0a00a8c0@Oberon.local>
Message-ID: <4294DB12.1030002@pcuf.fi>

Travis J. Weaver wrote:
> Hello list,
>  
>     Is there a way to kick all clients off after an iwconfig change? 
> Instead of:
>  
>         iwpriv wlan0 kickmac <hwaddr>
>  
>     is there something like:
>  
>         iwpriv wlan0 kickmac *    (of course this command does not work, 
> for I have tried it)

# Kick out all auth. stations
iwpriv wlan0 maccmd 4

-- 
Best Regards, Jar



From jkmaline  Wed May 25 19:34:58 2005
From: jkmaline (Jouni Malinen)
Date: Wed, 25 May 2005 19:34:58 -0700
Subject: multiple wpa_supplicant on same interface
In-Reply-To: <20050525153028.GA8249@lenst.det.unifi.it>
References: <20050525153028.GA8249@lenst.det.unifi.it>
Message-ID: <20050526023458.GG8082@jm.kir.nu>

On Wed, May 25, 2005 at 05:30:28PM +0200, Leonardo Maccari wrote:

> what is the technical reason why there can't be multiple wpa_supplicant
> running on the same phisical interface?.

Why would you want to do this? Based on configuration, wpa_supplicant
may be controlling the association and in all configurations, it is
taking care of EAPOL processing. Having more than one entity trying to
do this kind of tasks at the same time using the same resource (the
network interface) would lead to interesting end results..

> is there a way to have different
> supplicant on different virtual interfaces ?

Yes, as long as the driver supports this, wpa_supplicant works in this
kind of configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From pkolyvas  Wed May 25 23:42:14 2005
From: pkolyvas (Petros Kolyvas)
Date: Thu, 26 May 2005 02:42:14 -0400
Subject: hostap, wpa_supplicant and wifi pcmcia cards
In-Reply-To: <200505250849.j4P8nId2001063@harik.murex.com>
References: <200505250849.j4P8nId2001063@harik.murex.com>
Message-ID: <BAYC1-PASMTP02FCEB6FBDD7399E029B09D60F0@cez.ice>

DELORT Stephane wrote:
> Hello @ll,
> 
> I am about to buy a pcmcia card to carry out tests in our new wifi network. As this network configured to use PEAP/Mschap v2, I need a card able to deal with these protocols.
> My investigations lead me to atheros based chipset cards. Shortlisting the cards given in FreeBSD ath driver man-page with the pcmcia criteria, it appears that none of them is currently able to do WPA2 and 802.11x.
> 
> However, since they have the atheros chipset, these cards can be used with hostap for RF monitoring and with wpa_supplicant (read from the wpa_supplicant website).
> 
> Is it really possible to use WPA2 ant PEAP/mschap v2 with a card which specifications do not mention it ?
> (actually, there is either no record of these cards to run under linux/unix systems on their manufacturer's website)
> 
> Here is a list of the cards I selected. It would be really interesting if I can have feedback of people knowing/using these cards.
> 
> D-link DWL-AG650
> D-link DWL-G650B
> Linksys WPC55AG
> Netgear WAG511  (seems to be very common in europe and maybe be a piece of choice)
> Orinoco 8480
> 3com 3CRPAG175 (support of WPA2 and PEAP can be read on 3com website; it also have an X-jack antenna for improved transmission skills)
> 
> Thanks in advance for any advice,
> St?phane

I have a D-Link DWL-AG650 running with the latest unstable 
wpa_supplicant fully functional when connected to my access point using 
CCMP (PSK). While not technically WPA2 it functions flawlessly even 
though the card didn't support anything other than WEP/TKIP officially.

Hope that helps.

Pk




From laenrek  Thu May 26 01:22:01 2005
From: laenrek (Simon Santesteban)
Date: Thu, 26 May 2005 10:22:01 +0200 (CEST)
Subject: EAPOL-Key timeout s in 1/4 msg of 4-Way Handshake
In-Reply-To: 6667
Message-ID: <20050526082201.90940.qmail@web26608.mail.ukl.yahoo.com>

--- thomas schorpp <t.schorpp at gmx.de> escribi?:
> Simon Santesteban wrote:
> > Hello
> > 
> > Im trying to setup hostapd with an atheros card.
> > I compiled madwifi and hostap, and tried different
> > versions (madwifi-head, madwifi-bsd, hostap-0.3.7,
> > hostap-0.4.1), apply some patches, but allways end
> > with the same behaviour: WPA: EAPOL-Key timeout in
> 1/4
> > msg of handshake
> > 
> > Hostap says:
> > 
> 
> what client supplicants and hostapd setup? lets see
> config files.
> 
> report all sw + hw, pls.
> 

Client is a w2k machine with a conceptronic 54ri pci
wireless card, using vendor drivers (may I try
wpa_supplicant?)

Server has a senao pci card,

*/proc/pci*
  Bus  0, device  13, function  0:
    Ethernet controller: Atheros Communications, Inc.
AR5212 802.11abg NIC (rev 1).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=10.Max
Lat=28.
      Non-prefetchable 32 bit memory at 0x42000000
[0x4200ffff].
  Bus  0, device  14, function  0:

*hostapd.conf*
interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
debug=4
ssid=wififi
macaddr_acl=0
auth_algs=1
own_ip_addr=127.0.0.1
wpa=1
wpa_passphrase=secret 1234567890
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP

thanks



		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, m?s seguridad 
http://correo.yahoo.es



From maccari-thisaintpartofmyaddress-  Thu May 26 02:21:25 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Thu, 26 May 2005 11:21:25 +0200
Subject: multiple wpa_supplicant on same interface
In-Reply-To: <20050526023458.GG8082@jm.kir.nu>
References: <20050525153028.GA8249@lenst.det.unifi.it>
	<20050526023458.GG8082@jm.kir.nu>
Message-ID: <20050526092125.GA21247@lenst.det.unifi.it>

On Wed, May 25, 2005 at 07:34:58PM -0700, Jouni Malinen wrote:
> On Wed, May 25, 2005 at 05:30:28PM +0200, Leonardo Maccari wrote:
> 
> > what is the technical reason why there can't be multiple wpa_supplicant
> > running on the same phisical interface?.
> 
> Why would you want to do this? Based on configuration, wpa_supplicant
> may be controlling the association and in all configurations, it is
> taking care of EAPOL processing. Having more than one entity trying to

as you might remember I'm trying to modify wpa_supplicant to make it work
in a mesh ad-hoc network. this means that every node should act as an
authenticator and supplicant (towards more then one authenticator, the
sourronding nodes). As this is getting quite difficult, in the meantime
I'd like to have an intermediate solution, giving every machine two nics,
one working as AP and one working as supplicant to sourronding nodes.

Ideally the best solution would be to have on just one nic, a virtual
interface working as AP and multiple vitual interfaces each one running as
a supplicant and connecting to neighbours.

> do this kind of tasks at the same time using the same resource (the
> network interface) would lead to interesting end results..
> 
> > is there a way to have different
> > supplicant on different virtual interfaces ?
> 
> Yes, as long as the driver supports this, wpa_supplicant works in this
> kind of configuration.

so with prismII nics and hostap driver would my ideal solution be possible
to implement? or at least the one with two nics?

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 veerendra.madiwalappa  Thu May 26 03:28:47 2005
From: veerendra.madiwalappa (Veerendra)
Date: 26 May 2005 15:58:47 +0530
Subject: Does supplicant supports 802.1e?
Message-ID: <1117103326.3118.88.camel@ec4semi120256.wipro.com>


Hi,

I have a requirement where in I need to support 802.1e through wpa
supplicant. How this can be achieved?.Please give me some inputs on
this. 

Thanks,
Veerendra




Confidentiality Notice 

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.



From rishikesh.barooah  Thu May 26 05:58:07 2005
From: rishikesh.barooah (rishi)
Date: Thu, 26 May 2005 18:28:07 +0530
Subject: wpa-psk problem still present
Message-ID: <6fb31e6905052605586e76f113@mail.gmail.com>

Hi,

The wpa-psk problem caused by the event  - new ap found 00:00:00:00:00:00 still
occurs for me. I've tried with wpa_supplicant 3.8 to 4.1 with the
current cvs content also,
against the madwifi (main, BSD and WPA branch) - all of them displayed
the same problem of
disconnecting with the current ap and adding it to the blacklist.  

I've tried to use it against the Linksys WRT54GC and a Belkin G
wireless router, and the STA is WG311T from Netgear.  I would also
like to know why the two mac 00:00:00:00:00:00 and 44:44:44:44:44:44
are treated this way ?

my conf file contents : 
network={
    ssid="my-wireless"
    key_mgmt=WPA-PSK
    pairwise=TKIP CCMP
    group=TKIP CCMP WEP104 WEP40
    psk="abcdefghijklmnopqrstuvwxyz"    
}

thanks,
Rishi



From maccari-thisaintpartofmyaddress-  Thu May 26 08:00:49 2005
From: maccari-thisaintpartofmyaddress- (Leonardo Maccari)
Date: Thu, 26 May 2005 17:00:49 +0200
Subject: [patch] receive custom IE in wpa_supplicant
In-Reply-To: <20050525145526.GB31154@lenst.det.unifi.it>
References: <20050525145526.GB31154@lenst.det.unifi.it>
Message-ID: <20050526150049.GA15154@lenst.det.unifi.it>

On Wed, May 25, 2005 at 04:55:26PM +0200, Leonardo Maccari wrote:
> 
> I was able to make hostapd add a custom IE in beacon frames, I see the IE

if it can be useful to someone, here is the hack.

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.3.7-dev/: .config
diff -u ./config.c ../hostapd-0.3.7-dev/config.c
--- ./config.c	2005-01-22 20:43:16.000000000 +0100
+++ ../hostapd-0.3.7-dev/config.c	2005-05-26 16:27:15.000000000 +0200
@@ -66,7 +66,8 @@
 	conf->wpa_group = WPA_CIPHER_TKIP;
 
 	conf->radius_server_auth_port = 1812;
-
+	conf->generic_ie = NULL;
+		
 	return conf;
 }
 
@@ -935,6 +936,8 @@
 		} else if (strcmp(buf, "ctrl_interface") == 0) {
 			free(conf->ctrl_interface);
 			conf->ctrl_interface = strdup(pos);
+		} else if (strcmp(buf, "generic_ie") == 0) {
+			conf->generic_ie = strdup(pos);
 		} else if (strcmp(buf, "ctrl_interface_group") == 0) {
 			struct group *grp;
 			char *endp;
diff -u ./config.h ../hostapd-0.3.7-dev/config.h
--- ./config.h	2005-01-12 02:58:20.000000000 +0100
+++ ../hostapd-0.3.7-dev/config.h	2005-05-26 16:22:11.000000000 +0200
@@ -150,6 +150,7 @@
 	int wpa_gmk_rekey;
 	int rsn_preauth;
 	char *rsn_preauth_interfaces;
+	char * generic_ie;
 
 	char *ctrl_interface; /* directory for UNIX domain sockets */
 	gid_t ctrl_interface_gid;
Only in ./: defconfig
Only in ../hostapd-0.3.7-dev/: hostapd_cli
Only in ./: hostapd.conf
diff -u ./wpa.c ../hostapd-0.3.7-dev/wpa.c
--- ./wpa.c	2005-01-24 04:36:45.000000000 +0100
+++ ../hostapd-0.3.7-dev/wpa.c	2005-05-26 16:40:54.000000000 +0200
@@ -114,6 +114,16 @@
 } __attribute__ ((packed));
 
 
+struct gen_ie_hdr {
+	u8 elem_id; /* WLAN_EID_GENERIC */
+	u8 len;
+} __attribute__ ((packed));
+
+
+
+
+
+
 /* RSN IE version 1
  * 0x01 0x00 (version; little endian)
  * (all following fields are optional:)
@@ -135,6 +145,26 @@
 	u16 version;
 } __attribute__ ((packed));
 
+ 
+int wpa_gen_ip_address_ie(struct hostapd_data *hapd, u8 * buf)
+{
+
+	struct gen_ie_hdr *hdr;
+	u8 *pos;
+	int ie_len;
+
+	ie_len = strlen(hapd->conf->generic_ie);
+
+	hdr = (struct gen_ie_hdr *) buf;
+	hdr->elem_id = WLAN_EID_GENERIC;
+	hdr->len = ie_len;
+	pos = (u8*) (hdr + 1);	
+
+	memcpy(pos, (u8*) hapd->conf->generic_ie, strlen(hapd->conf->generic_ie));
+
+	return ie_len;
+}
+
 
 static int wpa_write_wpa_ie(struct hostapd_data *hapd, u8 *buf, size_t len)
 {
@@ -647,8 +677,24 @@
 		printf("Could not generate WPA IE.\n");
 		return -1;
 	}
+	if(hapd->conf->generic_ie)
+	{
+		u8 * buffer;
+		u8 * ptr;
+		buffer = malloc(hapd->wpa_ie_len + strlen(hapd->conf->generic_ie) + 2);
+		memcpy(buffer, hapd->wpa_ie,hapd->wpa_ie_len);
+		ptr = buffer + hapd->wpa_ie_len;
+		wpa_gen_ip_address_ie(hapd, ptr);
+	
+		if (hostapd_set_generic_elem(hapd, buffer,hapd->wpa_ie_len + strlen(hapd->conf->generic_ie) + 2 )) {
+			printf("Failed to configure WPA IE for the kernel driver.\n");
+		return -1;
+		}
+		printf("\n\nDEBUG adding duplicate IE\n\n");
+		free(buffer);
 
-	if (hostapd_set_generic_elem(hapd, hapd->wpa_ie, hapd->wpa_ie_len)) {
+	}else if (hostapd_set_generic_elem(hapd, hapd->wpa_ie, hapd->wpa_ie_len)) {
+ 
 		printf("Failed to configure WPA IE for the kernel driver.\n");
 		return -1;
 	}


From kshogan  Thu May 26 00:56:30 2005
From: kshogan (Kelly Hogan)
Date: Thu, 26 May 2005 00:56:30 -0700
Subject: hostap wifi0 exists, wlan0 unknown interface
Message-ID: <1117094190.5201.6.camel@m187.linora.com>

We have a unique sitiuation where we see the wifi0 device, but any
reference to wlan0 returns unknown interface.  The
/proc/net/hostap/wlan0 directory exists, and the debug file shows data. 
Reboots do not fix.

Anyone know why this would happen?   Running on a Soekris 4511 with
2.4.20 / hostap 0.2.4

Thanks,
KH




From frank  Thu May 26 12:40:33 2005
From: frank (Frank Thieme)
Date: Thu, 26 May 2005 21:40:33 +0200
Subject: automatic client configuration
In-Reply-To: <1116620329.7312.9.camel@uberpc.ubernet>
References: <20050515204727.GA12307@stars.fthieme.net>
	<20050518132320.GM5690@stars.fthieme.net>
	<20050520141844.GH15050@stars.fthieme.net>
	<1116607887.7312.5.camel@uberpc.ubernet>
	<20050520173338.GB25163@stars.fthieme.net>
	<1116620329.7312.9.camel@uberpc.ubernet>
Message-ID: <20050526194033.GB5677@stars.fthieme.net>

so, after some reading wlan-ng scripts and initng scripts I hacked
something together to get the same auto configuration feature as wlan-ng
has.

For all the others like me:

in /etc/pcmcia/hostap_cs.conf edit

device "hostap_cs"
   class "network" module "hostap", "hostap_cs"

in 

device "hostap_cs"
   class "wpa_supplicant" module "hostap", "hostap_cs"

That will start /etc/pcmcia/wpa_supplicant instead of
/etc/pcmcia/network on card insert.

now if you followed the wpa_supplicant instructions to insert some lines
in /etc/pcmcia/wireless remove them. wpa_supplicant will be started from
the script

now place the script in /etc/pcmcia 

So things like WEP/WPA will be handles via wpa_supplicant. The script
gets the currently attaeched ssid and sets the pcmcia scheme to include
the ssid. Then /etc/pcmcia/network will be called and you can edit
network.opts to you IP configuration, you even can start your vpn or
such in there.

case "$ADDRESS" in
*SSID,*,*,*)
...

selects the right SSID

have fun...

Bye...Frank

-------------- next part --------------
#! /bin/sh
#

if [ -r ./shared ] ; then . ./shared ; else . /etc/pcmcia/shared ; fi

wlan_usage ()
{
    echo "usage: wpa_supplicant [action] [device name] [debug]"
    echo "  actions: start|resume, stop|suspend, check|cksum|restart"
    echo "  debug  : enables shell debug"
    exit 1
}

wlan_set_ssid_schemefile ()
{
        # $1 == SSID

        # Find the scheme file 
        if [ -r /var/lib/misc/pcmcia-scheme ] ; then
                # Debian
                WLAN_SCHEMEFILE="/var/lib/misc/pcmcia-scheme"
        elif [ -d /var/state/pcmcia ] ; then
                WLAN_SCHEMEFILE="/var/state/pcmcia/scheme"
        elif [ -d /var/lib/pcmcia ] ; then
                WLAN_SCHEMEFILE="/var/lib/pcmcia/scheme"
        else
                WLAN_SCHEMEFILE="/var/run/pcmcia-scheme"
        fi

        # Collect the current scheme name and save the file
        if [ -r $WLAN_SCHEMEFILE ] ; then
                WLAN_SCHEME=`cat $WLAN_SCHEMEFILE`
                cp $WLAN_SCHEMEFILE /tmp/wlan_scheme_`date +"%T"`.tmp
        else
                touch /tmp/wlan_scheme_`date +"%T"`.tmp
                
        fi

        # Set up the <scheme:SSID> string
        if [ ! "$WLAN_SCHEME" ] ; then 
                WLAN_SCHEME="default"
        fi
        WLAN_SCHEME="$WLAN_SCHEME:$1"

        # Write to schemefile
        echo $WLAN_SCHEME > $WLAN_SCHEMEFILE
}

wlan_restore_schemefile ()
{
        # Find the scheme file 
        if [ -r /var/lib/misc/pcmcia-scheme ] ; then
                # Debian
                WLAN_SCHEMEFILE="/var/lib/misc/pcmcia-scheme"
        elif [ -d /var/state/pcmcia ] ; then
                WLAN_SCHEMEFILE="/var/state/pcmcia/scheme"
        elif [ -d /var/lib/pcmcia ] ; then
                WLAN_SCHEMEFILE="/var/lib/pcmcia/scheme"
        else
                WLAN_SCHEMEFILE="/var/run/pcmcia-scheme"
        fi

        TMPFILE=`ls /tmp/wlan_scheme*.tmp | tail -n 1`

        if [ -r $TMPFILE ] ; then
                cat $TMPFILE > $WLAN_SCHEMEFILE
                rm -f $TMPFILE
        else
                ${ECHO} "wlan_restore_schemefile: No wlan_scheme\*.tmp file found."
        fi
}

if [ "$3" = "debug" ]; then set -x ; fi

# If number of args is less than 2 display usage
if [ $# -lt 2 ]; then wlan_usage ; fi

# XXXX we can do stuff with $SCHEME still..?
case "$ACTION" in

'start'|'resume')
	# start supplicant
        /usr/bin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf \
                -i$DEVICE

	# find ESSID
        for (( i=0; i<5; i++ )); do
                CurESSID=$( /usr/bin/wpa_cli -i$DEVICE status | /usr/bin/sed -n -e 's/^ssid=//p' )
                if [[ -n ${CurESSID} ]]; then
                        echo ${CurESSID}
                        continue 5
                else 
                        sleep 1
		fi
        done

        # stolen from wlan-ng
        # ==========PCMCIA NETDEVICE=============================
        # Append the SSID to the pcmcia scheme name
        wlan_set_ssid_schemefile "${CurESSID}"

        # Call the normal network initialization
        ./network $1 $2
        if [ $? = 1 ] ; then
#               echo "/etc/pcmcia/network $1 $2 failed."
                wlan_restore_schemefile
                exit 1
        fi
        
        # Restore scheme file to it's prior contents
        wlan_restore_schemefile
	;;

'stop'|'suspend')

    	for (( i=0; i<5; i++ )); do
                CurESSID=$( /usr/bin/wpa_cli -i$DEVICE status | /usr/bin/sed -n -e 's/^ssid=//p' )
                if [[ -n ${CurESSID} ]]; then
                        echo ${CurESSID}
                        continue 5
                else 
                        sleep 1
		fi
        done

	killall wpa_supplicant
       
	# stolen from wlan-ng
        # ==========PCMCIA NETDEVICE=============================
        # Append the SSID to the pcmcia scheme name
        wlan_set_ssid_schemefile "${CurESSID}"

        # Call the normal network initialization
        ./network $1 $2
        if [ $? = 1 ] ; then
#               echo "/etc/pcmcia/network $1 $2 failed."
                wlan_restore_schemefile
                exit 1
        fi
        
        # Restore scheme file to it's prior contents
        wlan_restore_schemefile

	;;

'check'|'cksum'|'restart')
	;;

*)
    wlan_usage
    ;;

esac

exit 0


From bmeier  Thu May 26 13:48:54 2005
From: bmeier (Beat Meier)
Date: Thu, 26 May 2005 17:48:54 -0300
Subject: Bad password in WPA-PSK cannot be deteced in handshake?
Message-ID: <42963636.5080507@infovia.com.ar>

Hi

Is it not possible to detect a bad passwd in the Handshake of WPA-PSK?
At the moment the wpa_supplicant always get through EAPOL stage 1 and 2 
of handshake
i.e. Stage 3 is never reached.
If possible to detect it would be nice to print a warning that the 
passwd is wrong and then
give up or tray a certain times.

Beat



From jwright  Thu May 26 14:00:01 2005
From: jwright (Joshua Wright)
Date: Thu, 26 May 2005 17:00:01 -0400
Subject: Bad password in WPA-PSK cannot be deteced in handshake?
In-Reply-To: <42963636.5080507@infovia.com.ar>
References: <42963636.5080507@infovia.com.ar>
Message-ID: <429638D1.9080403@hasborg.com>

The 802.11i specification indicates that the AP should silently 
discontinue the four-way handshake.  This makes it more difficult for an 
attacker to mount an online dictionary attack.

-Josh

Beat Meier wrote:
> Is it not possible to detect a bad passwd in the Handshake of WPA-PSK?
> At the moment the wpa_supplicant always get through EAPOL stage 1 and 2 
> of handshake

-- 
-Joshua Wright
jwright at hasborg.com
http://home.jwu.edu/jwright/

pgpkey: http://home.jwu.edu/jwright/pgpkey.htm
fingerprint: FDA5 12FC F391 3740 E0AE BDB6 8FE2 FC0A D44B 4A73

Today I stumbled across the world's largest hotspot.  The SSID is "linksys".



From jkmaline  Thu May 26 20:31:34 2005
From: jkmaline (Jouni Malinen)
Date: Thu, 26 May 2005 20:31:34 -0700
Subject: Patch for wpa_supplicant multiple networks when ap_scan = 2
In-Reply-To: <200505191011.j4JABV1P008592@leopard.the-hills.org>
References: <200505191011.j4JABV1P008592@leopard.the-hills.org>
Message-ID: <20050527033134.GJ8082@jm.kir.nu>

On Thu, May 19, 2005 at 06:11:31AM -0400, Brian Hill wrote:

> I made a very crude patch to wpa_supplicant.c that will let the
> supplicant scan through multiple networks in priority order, even when
> ap_scan = 2.  It's not well done, it's what I could do in just a few
> minutes to make it work for me.  I'd certainly appreciate any feedback
> if someone finds this useful / badly broken / stupid / funny.

Thanks! This is similar to what I planned on doing for ap_scan=2 mode
(for bugzilla bug 16). However, your patch has couple of issues that
make it fail in some cases. last_prio_scan would have been shared by
multiple interfaces if wpa_supplicant is controlling more than one
radio. In addition, it did not seem to scan all network blocks if more
than one block was sharing the same priority value.

I ended up using the same code that scan_ssid=1 had for iterating
through the networks. This means that ap_scan=2 will not use the
priority field; instead the order of network blocks in the file is used
to select which network to "scan for". In other words, this would match
with the order that ap_scan=1 mode use if all networks were using
scan_ssid=1 and APs were configured to use hidden SSIDs. These changes
are now in CVS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From duncan.grove  Fri May 27 00:00:00 2005
From: duncan.grove (Duncan Grove)
Date: Fri, 27 May 2005 16:30:00 +0930
Subject: WPA-PSK with prism2_param host_roaming 0 / handover performance 
Message-ID: <4296C570.4050806@dsto.defence.gov.au>

Hi,

I am using wpa_supplicant-0.4.0 with hostap-driver-0.4.0 and JT's 
Wireless Tools 28-pre7 to connect to a number Cisco 1231 APs using 
WPA-PSK; full WPA2 isn't an option for me at this stage. All APs are 
configured with the same SSID and PSK. In its current incarnation, 
wpa_supplicant sets prism2_param host_roaming to 2, i.e. manual scanning 
and roaming. Unfortunately this mode isn't very useful for mobile 
applications. I believe that the eventual plan is to use host_roaming 
mode 1, where the driver would take care of scanning and roaming 
decisions, but this doesn't seem to work yet.

As a stopgap solution, automatic WPA-PSK roaming can be achieved by 
setting prism2_param host_roaming to 0. In this case, 
hostap/wpa_supplicant relies on the firmware to change channels when 
required, and wpa_supplicant simply takes care of the authentication 
process. Unfortunately, however, it takes wpa_supplicant 2-3 seconds to 
decide to rekey. During this period both outgoing and incoming packets 
get dropped with log messages like "dropped unencrypted TX data frame 
(drop unencrypted = 1)" and "TKIP: replay detected: STA=AP_MAC_ADDRESS) 
res=-4" (I can provide dumps of this process if they would help). This 
isn't so great for eg VOIP applications and I would like to reduce the 
duration of this network outage.

Interestingly, a manual channel change by iwconfig wlan0 channel X 
doesn't suffer from this problem. It appears that a manual channel 
change leads to a wpa_supplicant DISCONNECT event, which removes the 
encryption keys, followed by a CONNECT event, which rekeys the channel 
in a timely manner. Conversely, however, an firmware initiated roam just 
causes a CONNECT event without the DISCONNECT first i.e. the keys 
weren't removed and subsequently don't get reestablished quickly.

What is the best way to get wpa_supplicant to rekey in a timely manner 
after a firmware initiated roam? Would it be possible to get 
wpa_supplicant to detect the AP change wireless extension event and 
rekey? Alternatively, would it be possible to add a manual wpa_cli 
reauth command, which simply rekeys the channel without having to go 
through the whole scanning/association process? (I have a modded iwevent 
which will detect the AP change event and run a script, eg containing 
the wpa_cli reauth command). At first glance wpa_cli reassoc may seem to 
be good enough for this purpose, since it appears to do a 0 second scan 
followed by the reauth, but unfortunately the 0 second scan still causes 
more WEXT disconnect / reconnect / AP change events, which are necessary 
to trigger the reassoc/rekey, hence reassocs will be triggered ad infinitum.

Thanks,
Duncan




From ktari.anis  Fri May 27 03:15:02 2005
From: ktari.anis (Anis KTARI)
Date: Fri, 27 May 2005 12:15:02 +0200
Subject: wpa-supplicant apon windows
Message-ID: <e82b86c7050527031566d893b9@mail.gmail.com>

hi, 
 I'm using wpa-supplicant (as a client 802.11i) apon windows, it doesn't work 
 has anybody any idea? (how to do ... )


thanks



From jeffelkins  Fri May 27 07:59:10 2005
From: jeffelkins (Jeff Elkins)
Date: Fri, 27 May 2005 10:59:10 -0400
Subject: Zaurus 5500 PDA
Message-ID: <200505271059.10594.jeffelkins@earthlink.net>

I've got a very basic newbie question...

I'm running a Zaurus 5500 with a custom rom (not Open Zaurus) and I'd like to 
add hostap support. I've got a working arm cross-compiler and have 
successfully compiled kernels and modules, but never external modules, just 
the stuff in the kernel tree.

I'm confused on how to integrate hostap into my source tree. I changed the 
makefile to a KERNEL_PATH pointing to my source and placed the driver 
directory under drivers/pcmcia...obviously, it didn't work.

Could someone help me with this baby-step?

Thanks,

Jeff Elkins








From jim  Fri May 27 10:35:16 2005
From: jim (Jim Howard)
Date: Fri, 27 May 2005 12:35:16 -0500
Subject: What card for hostap to buy today?
Message-ID: <00a601c562e2$728ab0f0$cb0dfea9@austin.swinc.com>

Howdy,

I've looked through all the FAQs and stuff I can find and am still a little confused.  I'm gong to try and set up a Linux box with hostap over the next week or so.  It's a generic Pentium III PC box.

If you were going to go to Fry's or Best Buy today to buy a card that works with hostap, what wireless card would you buy?

thanks

Jim Howard
jim [at] grayraven[dot]com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050527/0c5a75d9/attachment.htm 


From jeffelkins  Fri May 27 19:11:48 2005
From: jeffelkins (Jeff Elkins)
Date: Fri, 27 May 2005 22:11:48 -0400
Subject: Zaurus 5500 PDA
In-Reply-To: <200505271059.10594.jeffelkins@earthlink.net>
References: <200505271059.10594.jeffelkins@earthlink.net>
Message-ID: <200505272211.48277.jeffelkins@earthlink.net>

On Friday 27 May 2005 10:59 am, Jeff Elkins wrote:
> I've got a very basic newbie question...
>
> I'm running a Zaurus 5500 with a custom rom (not Open Zaurus) and I'd like
> to add hostap support. I've got a working arm cross-compiler and have
> successfully compiled kernels and modules, but never external modules, just
> the stuff in the kernel tree.
>
> I'm confused on how to integrate hostap into my source tree. I changed the
> makefile to a KERNEL_PATH pointing to my source and placed the driver
> directory under drivers/pcmcia...obviously, it didn't work.
>
> Could someone help me with this baby-step?

Just as a followup, I've successfully compiled the hostap apps for my arch 
which is an arm kernel:
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 18
EXTRAVERSION = -rmk7-pxa3-embedix
EMBEDIXRELEASE =-021129

Am I correct in that I will have to patch the kernel? I did attempt a make in 
the hostap module source dir with KERNEL_PATH pointed to my source tree and 
CC pointed at my cross-compiler.










From jkmaline  Fri May 27 19:41:53 2005
From: jkmaline (Jouni Malinen)
Date: Fri, 27 May 2005 19:41:53 -0700
Subject: wpa-supplicant apon windows
In-Reply-To: <e82b86c7050527031566d893b9@mail.gmail.com>
References: <e82b86c7050527031566d893b9@mail.gmail.com>
Message-ID: <20050528024153.GQ8082@jm.kir.nu>

On Fri, May 27, 2005 at 12:15:02PM +0200, Anis KTARI wrote:

>  I'm using wpa-supplicant (as a client 802.11i) apon windows, it doesn't work 
>  has anybody any idea? (how to do ... )

A good start would be to give a bit more detailed description of what
does not work. Useful information includes, but is not limited to, used
configuration file, debug log from wpa_supplicant (-dd on command line),
expected results, observed results..

-- 
Jouni Malinen                                            PGP id EFC895FA



From ken  Sat May 28 05:30:23 2005
From: ken (Ken Hilliard)
Date: Sat, 28 May 2005 19:30:23 +0700
Subject: recommended prism wireless adapters
Message-ID: <000601c56381$070646b0$6363a8c0@compaq>

Folks,
 
I'd like to try my hand at building a linux-based wireless AP. Could
anyone recommend a PCI (or USB) wireless adapter compatible with the
hostap driver/utilities? I'm currently based in Thailand so I would need
something widely available. I've heard that Gemtek has cards based on
the Prism chipset.
 
 
Thx, Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050528/bdc9798c/attachment.htm 


From jkmaline  Sat May 28 22:24:19 2005
From: jkmaline (Jouni Malinen)
Date: Sat, 28 May 2005 22:24:19 -0700
Subject: problems with Wireless event: new AP (00:00:00:00:00:00)
In-Reply-To: <20050517175551.0pbx2co10o8os4os@webmail.togg.de>
References: <20050517175551.0pbx2co10o8os4os@webmail.togg.de>
Message-ID: <20050529052418.GT8082@jm.kir.nu>

On Tue, May 17, 2005 at 05:55:51PM +0200, Sebastian Weitzel wrote:

> (jkm:)
> >For me, this is not an association with a bogus AP BSSID, but a
> >disassociation from the current AP. If the driver is generating this
> >event in a case where it is not actually being disassociated/
> >deauthenticated, the driver should be fixed..

> Maybe http://article.gmane.org/gmane.linux.drivers.hostap/10487 
> allready tried to patch this issue. I applied the patch and retested. 

No, that is a completely different issue.

> It still dont solves the problem. As you can see the ifindex differs 
> which should lead to reject this event, but does not.
> 
> 
> ifi->ifi_index=6
> drv->ifindex(8) != ifi->ifi_index(6), reject event

?? this was rejected..

> fromlen=12 addr=00:00:00:00:00:00
> ifi->ifi_index=8
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00

This is another event, isn't it?

> I dont know yet why the wireless event still leads to blacklisting. 

Because the driver is reporting a disassociation!

I took a closer look at madwifi and what is happening (at least in my
test case) is that the association is completed successfully, but
Atheros mac reports a beacon miss and the driver interprets this as the
AP has disappeared, which is not really the case here. This was
relatively easy to reproduce at least with long beacon interval (1000
TU).

This is starting to look like the most commonly reported problem with
madwifi driver* when using wpa_supplicant and I would really appreciate
it if someone would take a closer look at what is happening with beacon
miss events. Either the hardware is configured incorrectly or there are
bogus bmiss events. Either way, the driver should filter these out and
not report disassociation. If the time sync for beacon miss cannot be
fixed, the driver could, e.g., use probe request to verify whether the
AP is still in range before processing the beacon miss event.

*) see, e.g., http://hostap.epitest.fi/bugz/show_bug.cgi?id=44

-- 
Jouni Malinen                                            PGP id EFC895FA



From and0806  Sun May 29 20:11:05 2005
From: and0806 (and hansen)
Date: Mon, 30 May 2005 05:11:05 +0200 (CEST)
Subject: madwifi+hostapd
Message-ID: <20050530031105.10072.qmail@web51104.mail.yahoo.com>

Hi Group

Is there anyone here that can help me a little ?

I'm fighting to get hostapd to authenticate wpa-psk
clients, via wpa_supplicant, is it bugs or is it me
that screws it all up ?
I see people on the lists that have success with this
software
so why isn't it working here, perhaps I'm closer to
the magnetic
pole or something, gravitation differences who knows
;)
I'm using atheros5212 chips in both ends (ap and
client)
I have seen that i have to use the bsd branch of
the madwifi CVS, but still I can't get this to go
I'm using the most current versions of everything
madwifi-bsd-cvs, hostapd-cvs, wpa_suppicant-cvs
wirelesstools28.pre7 and kernel2.6.11.10
My setup is working whitout any encryption at all.
Please help me, this is the 2week of testing and
reading
and i have tried everything, so if i don't get any
response
on this posing either my next step will be to wrap
tinfoil
all over the room, to prevent magnetic interferes ;)
what can i do ?

Regards Lasse



From jkmaline  Sun May 29 20:15:15 2005
From: jkmaline (Jouni Malinen)
Date: Sun, 29 May 2005 20:15:15 -0700
Subject: madwifi+hostapd
In-Reply-To: <20050530031105.10072.qmail@web51104.mail.yahoo.com>
References: <20050530031105.10072.qmail@web51104.mail.yahoo.com>
Message-ID: <20050530031514.GA7950@jm.kir.nu>

On Mon, May 30, 2005 at 05:11:05AM +0200, and hansen wrote:

> I have seen that i have to use the bsd branch of
> the madwifi CVS, but still I can't get this to go
> I'm using the most current versions of everything
> madwifi-bsd-cvs, hostapd-cvs, wpa_suppicant-cvs
> wirelesstools28.pre7 and kernel2.6.11.10

Please send the configuration file you used with hostapd and debug log
from hostapd when trying to associate a station with the AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From goldwater716  Mon May 30 02:43:55 2005
From: goldwater716 (GoldWater)
Date: Mon, 30 May 2005 17:43:55 +0800
Subject: suitable wired client of MS windows
Message-ID: <ac2b1036050530024368951293@mail.gmail.com>

Dear all:

Do any great bother can help me to solve the following problem?

I already install hostapd (enable wired) and FreeRadius in RH9, and I
am using wired connection  only, I want to find a suitable client of
MS windows which can provide EAP/TLS and support smartcard is much
better.

Please Help!

Best Regards,
WaiLun



From 42429  Mon May 30 04:05:55 2005
From: 42429 (Cristian Francesco Panessa)
Date: Mon, 30 May 2005 13:05:55 +0200
Subject: How to hide ssid
Message-ID: <429AF393.20408@unimo.it>

Hi,
There is someone give me some helps about use Hostapd with hide SSID,
because when i try to use it on my ap , my  wpa_supplicant  don't  scan  
ap.

I use:
wpa_supplicant: 0.3.8
hostapd: 0.3.7
hostap driver 0.2.5
firmware  v1.8.4  PRISM III


tnx

Cristian F. Panessa



From and0806  Mon May 30 09:24:30 2005
From: and0806 (and hansen)
Date: Mon, 30 May 2005 18:24:30 +0200 (CEST)
Subject: madwifi+hostapd
Message-ID: <20050530162430.5296.qmail@web51101.mail.yahoo.com>

Hi Jouni Malinen

I did try to post a lot of debugging info
but the mailman application were limiting
me to 25KB so i decided, only to send the main
problem, but anyway, here is the hostapd.conf
and it's dump
I also have to mention that, wpa_supplicant
and hostapd is running about 1 minute before
any association is beginning to appearer in the
hostapd dump.
plus that the dump in both ends is looping.

Regards Lasse Jensen

[root at athlon root]# cat /etc/hostapd.conf
interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=t245
macaddr_acl=0
auth_algs=3
eapol_key_index_workaround=0
eap_authenticator=0
own_ip_addr=127.0.0.1
wpa=1
wpa_passphrase=12345678
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP





[root at athlon root]# /usr/local/bin/hostapd
/etc/hostapd.conf -dd
Configuration file: /etc/hostapd.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:0f:a3:8b:cb:34 and
ssid 't245'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 3a 96 2f 72 64 0a c5 6b 85 19
58 e6 0e 19 a4 b1 a0 99 95 ac 04 ac 77 68 b8 36 c5 e7
7d 2c 24 a3
GTK - hexdump(len=32): c4 1d ca 0b 42 71 53 73 59 83
a7 eb f0 b8 0a b9 ca d7 c3 7b 85 1b 48 ff 1b 21 e7 22
3b 72 9f 23
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00
key_idx=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=3
Deauthenticate all stations
l2_packet_receive - recv: Network is down
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECT
madwifi_sta_deauth: addr=00:0f:b3:05:16:c4
reason_code=2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11:
deauthenticated due to local deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=3
tx_packets=4
rx_bytes=411
tx_bytes=428
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=1
tx_packets=1
rx_bytes=137
tx_bytes=107
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
ath0: STA 00:0f:b3:05:16:c4 WPA: event 2 notification
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECT
madwifi_sta_deauth: addr=00:0f:b3:05:16:c4
reason_code=2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11:
deauthenticated due to local deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=3
tx_packets=4
rx_bytes=411
tx_bytes=428
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=1
tx_packets=1
rx_bytes=137
tx_bytes=107
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
ath0: STA 00:0f:b3:05:16:c4 WPA: event 2 notification
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECT
madwifi_sta_deauth: addr=00:0f:b3:05:16:c4
reason_code=2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11:
deauthenticated due to local deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=3
tx_packets=4
rx_bytes=411
tx_bytes=428
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=1
tx_packets=1
rx_bytes=137
tx_bytes=107
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
ath0: STA 00:0f:b3:05:16:c4 WPA: event 2 notification
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
ath0: STA 00:0f:b3:05:16:c4 WPA: EAPOL-Key timeout
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECT
madwifi_sta_deauth: addr=00:0f:b3:05:16:c4
reason_code=2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11:
deauthenticated due to local deauth request
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=3
tx_packets=4
rx_bytes=411
tx_bytes=428
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:b3:05:16:c4 WPA: event 1 notification
madwifi_sta_clear_stats: addr=00:0f:b3:05:16:c4
ath0: STA 00:0f:b3:05:16:c4 WPA: start authentication
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
WPA: 00:0f:b3:05:16:c4 WPA_PTK_GROUP entering state
IDLE
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
AUTHENTICATION2
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state INITPSK
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:b3:05:16:c4 WPA: sending 1/4 msg of
4-Way Handshake
Wireless event: cmd=0x8c02 len=103
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:0f:b3:05:16:c4
rx_packets=1
tx_packets=1
rx_bytes=137
tx_bytes=107
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.11: deassociated
ath0: STA 00:0f:b3:05:16:c4 WPA: event 2 notification
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
DISCONNECTED
WPA: 00:0f:b3:05:16:c4 WPA_PTK entering state
INITIALIZE
madwifi_del_key: addr=00:0f:b3:05:16:c4 key_idx=0
ioctl[IEEE80211_IOCTL_DELKEY]: Invalid argument
ath0: STA 00:0f:b3:05:16:c4 IEEE 802.1X: unauthorizing
port
madwifi_set_sta_authorized: addr=00:0f:b3:05:16:c4
authorized=0
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Signal 2 received - terminating
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=3
Deauthenticate all stations
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0




From bmeier  Mon May 30 11:32:58 2005
From: bmeier (Beat Meier)
Date: Mon, 30 May 2005 15:32:58 -0300
Subject: Wep doesn't work with atheros 5212
Message-ID: <429B5C5A.1080508@infovia.com.ar>

Hi again

 From day to day I'm more confused.
I've now tried to setup WEP with wpa_supplicant-0.3.9-rc1 and 
wpa_supplicant-0.4.1
Both don't work i.e. I cannot ping my ap.
Ap is a wrt54g. With ndsiwrapper and WPC54g it works with wpa_supplicant 
and atheros card
it down't work BUT if I do it myself i.e.

  iwconfig $NIF key <key>
  ifconfig $NIF down
  iwconfig $NIF enc on
  ifconfig $NIF up
everything works fine.
WPA-PSK seems to work with wpa_supplicant-0.4.1 ...
I'm realy at the end of my know how.
I don't need wep but I think there is a general problem if such a basic 
thing
doesn't work from release to release.
I have not problem to be a tester for my cards in fact I would like it, 
but I need some more
background info so let me know if you use more tester before releasing ...

Where is the problem. Does wep use openssl? Does wpa_supplicant use
own algo for wep and if I do it by hand i.e. madwifi use other algo?
If I do a iwconfig ath0 in both cases it's exactly the same output.
netstat -rn also.

Any help is realy nice.

BTW: I use madwifi-bsd branch from today (20050530) vanilla kernel-2.4.30
wireless tools v26 or v27, wireless extension v16 of kernel and ath0
suse9.0 (with kernel-2.4.30) openssl-0.9.7b-68 of suse.

Beat

Output of dmesg

May 30 14:39:09 bbmpc2 kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, 
AR5212, RF5111, RF5112, RF2413)
May 30 14:39:09 bbmpc2 kernel: wlan: 0.8.5.0-BSD (EXPERIMENTAL)
May 30 14:39:09 bbmpc2 kernel: ath_rate_onoe: 1.0
May 30 14:39:09 bbmpc2 kernel: ath_pci: 0.9.5.0-BSD (EXPERIMENTAL)
May 30 14:39:09 bbmpc2 kernel: Build date: May 30 2005
May 30 14:39:09 bbmpc2 kernel: Debugging version (IEEE80211)
May 30 14:39:09 bbmpc2 kernel: ath0: 11a rates: 6Mbps 9Mbps 12Mbps 
18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May 30 14:39:09 bbmpc2 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
May 30 14:39:09 bbmpc2 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May 30 14:39:09 bbmpc2 kernel: ath0: turboA rates: 6Mbps 9Mbps 12Mbps 
18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May 30 14:39:09 bbmpc2 kernel: ath0: turboG rates: 6Mbps 9Mbps 12Mbps 
18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May 30 14:39:09 bbmpc2 kernel: ath0: H/W encryption support: WEP AES 
AES_CCM TKIP
May 30 14:39:09 bbmpc2 kernel: ath0: mac 5.9 phy 4.3 radio 3.6
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 1 for WME_AC_BE traffic
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 0 for WME_AC_BK traffic
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 2 for WME_AC_VI traffic
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 3 for WME_AC_VO traffic
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 8 for CAB traffic
May 30 14:39:09 bbmpc2 kernel: ath0: Use hw queue 9 for beacons
May 30 14:39:09 bbmpc2 kernel: Debugging version (ATH)
May 30 14:39:09 bbmpc2 kernel: ath0: Atheros 5212: mem=0xe9000000, irq=11


Here is the output of wpa_supplicant which also tells me it should be 
ok, or not?

State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b1a len=21
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:41:6e:18:d2
State: ASSOCIATING -> ASSOCIATED
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:41:6e:18:d2
Associated with 00:0c:41:6e:18:d2
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:0c:41:6e:18:d2 completed (auth)





From wlan.20.briony  Mon May 30 12:32:44 2005
From: wlan.20.briony (wlan.20.briony at spamgourmet.com)
Date: Mon, 30 May 2005 21:32:44 +0200
Subject: which firmware for wl200?
In-Reply-To: <3579.192.168.0.150.1116709017.squirrel@kone>
References: <20050521191324.71864af3.a0305292@unet.univie.ac.at>
	<3301.192.168.0.150.1116701559.squirrel@kone>
	<20050521210712.2d52bf01.benke@thedonkeynetwork.com>
	<3366.192.168.0.150.1116703499.squirrel@kone>
	<20050521221813.026eb724.benke@thedonkeynetwork.com>
	<3579.192.168.0.150.1116709017.squirrel@kone>
Message-ID: <20050530213244.0648bbdb.benke@thedonkeynetwork.com>

> > ok, one last question - where do i get 1.7.0 cause the link above
> > only has 1.7.1 - and which firmware-image will i have to use?
> Yes sorry, i mean 1.7.1 (s1010701.hex).

sorry for the late reply.
it finally worked with winupdate, prism2_srec didn't let me overwrite
the firmware even with the '-s'-option activated.
thanks!!



From dpreed  Mon May 30 14:08:35 2005
From: dpreed (David P. Reed)
Date: Mon, 30 May 2005 17:08:35 -0400
Subject: help! wpa_supplicant with WEP never associates, just timeout-loops
Message-ID: <429B80D3.4050701@reed.com>

I have a fairly vanilla system: FC3, madwifi running pretty standard on 
a Compaq Evo N610c.   ath0 associates just fine without wpa_supplicant 
with an access point using WEP shared keys and ifup, specifying the 
proper key.

I cannot get wpa_supplicant to associate, however.    It finds the 
access point and tries to associate, but times out and loops retrying.   
Here is the output from wpa_supplicant 4.1 (3.8 does the same thing), 
followed by my network block.   (the same thing also happens on my 
x86_64 laptop with both ndiswrapper and  madwifi).

Please help with some suggestions for what to look at, I've looked at 
zillions of things, including coding a really long (60 sec) timeout!  
I'm hardly a newbie to computing or Linux, but I'm a complete newbie to 
wpa_supplicant, and this is just frustrating.  I really want to shift my 
setup to wpa rather than WEP, but this doesn't give me much confidence 
that wpa_supplicant will work for me.



From dpreed  Mon May 30 14:10:10 2005
From: dpreed (David P. Reed)
Date: Mon, 30 May 2005 17:10:10 -0400
Subject: [data included] help! wpa_supplicant with WEP never associates, just
	timeout-loops
Message-ID: <429B8132.3010402@reed.com>

I have a fairly vanilla system: FC3, madwifi running pretty standard on
a Compaq Evo N610c.   ath0 associates just fine without wpa_supplicant
with an access point using WEP shared keys and ifup, specifying the
proper key.

I cannot get wpa_supplicant to associate, however.    It finds the
access point and tries to associate, but times out and loops retrying.
Here is the output from wpa_supplicant 4.1 (3.8 does the same thing),
followed by my network block.   (the same thing also happens on my
x86_64 laptop with both ndiswrapper and  madwifi).

Please help with some suggestions for what to look at, I've looked at
zillions of things, including coding a really long (60 sec) timeout!
I'm hardly a newbie to computing or Linux, but I'm a complete newbie to
wpa_supplicant, and this is just frustrating.  I really want to shift my
setup to wpa rather than WEP, but this doesn't give me much confidence
that wpa_supplicant will work for me.

-------------------------- wpa_supplicant output ------------
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 
'madwifi'
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
opensc_engine_path='/usr/lib/opensc/engine_opensc.so'
pkcs11_engine_path='/usr/lib/opensc/engine_pkcs11.so'
pkcs11_module_path='/usr/lib/pkcs11/opensc-pkcs11.so'
Line: 285 - start of a new network block
ssid - hexdump_ascii(len=8):
      52 65 65 64 2e 63 6f 6d                           Reed.com
key_mgmt: 0x4
wep_key0 - hexdump(len=5): [REMOVED]
wep_key1 - hexdump(len=5): [REMOVED]
wep_key2 - hexdump(len=5): [REMOVED]
wep_tx_keyidx=0 (0x0)
priority=5 (0x5)
auth_alg: 0x2
Priority group 5
    id=0 ssid='Reed.com'
Initializing interface (2) 'ath0'
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
ioctl[SIOCSIWPMKSA]: Operation not supported
Own MAC address: 00:11:50:54:cd:c6
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_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 343 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:09:5b:2f:2f:64 ssid='Reedb.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
1: 00:09:5b:5c:7e:f4 ssid='Reed.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
    selected non-WPA AP 00:09:5b:5c:7e:f4 ssid='Reed.com'
Trying to associate with 00:09:5b:5c:7e:f4 (SSID='Reed.com' freq=2442 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=2 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b1a len=21
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
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
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)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 343 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:09:5b:2f:2f:64 ssid='Reedb.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
1: 00:09:5b:5c:7e:f4 ssid='Reed.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
    selected non-WPA AP 00:09:5b:5c:7e:f4 ssid='Reed.com'
Trying to associate with 00:09:5b:5c:7e:f4 (SSID='Reed.com' freq=2442 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=2 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b1a len=21
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
State: ASSOCIATING -> DISCONNECTED
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
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)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 343 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:09:5b:5c:7e:f4 ssid='Reed.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
1: 00:09:5b:2f:2f:64 ssid='Reedb.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
    selected non-WPA AP 00:09:5b:5c:7e:f4 ssid='Reed.com'
Trying to associate with 00:09:5b:5c:7e:f4 (SSID='Reed.com' freq=2442 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=2 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b1a len=21
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
State: ASSOCIATING -> DISCONNECTED
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
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)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 343 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:09:5b:2f:2f:64 ssid='Reedb.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
1: 00:09:5b:5c:7e:f4 ssid='Reed.com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
    skip - no WPA/RSN IE
    selected non-WPA AP 00:09:5b:5c:7e:f4 ssid='Reed.com'
Trying to associate with 00:09:5b:5c:7e:f4 (SSID='Reed.com' freq=2442 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_key: alg=WEP key_idx=2 set_tx=0 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b1a len=21
CTRL-EVENT-TERMINATING - signal 2 received
State: ASSOCIATING -> DISCONNECTED
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
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)


--------------------- wpa_supplicant.conf
.... contents same as distributed wpa_supplicant.conf minus example network
  blocks - the following is the only network block .......

network={
	ssid="Reed.com"
	key_mgmt=NONE
	wep_key0=F000000000
	wep_key1=F000000000
	wep_key2=F000000000
	wep_tx_keyidx=0
	priority=5
	auth_alg=SHARED
}






From jkmaline  Mon May 30 18:22:01 2005
From: jkmaline (Jouni Malinen)
Date: Mon, 30 May 2005 18:22:01 -0700
Subject: [-mm patch] net/ieee80211/: remove pci.h #include's
In-Reply-To: <20050530205634.GQ10441@stusta.de>
References: <20050530205634.GQ10441@stusta.de>
Message-ID: <20050531012200.GC7950@jm.kir.nu>

On Mon, May 30, 2005 at 10:56:34PM +0200, Adrian Bunk wrote:

> I was wondering why editing pci.h triggered the rebuild of three files 
> under net/, and as far as I can see, there's no reason for these three 
> files to #include pci.h .

>  net/ieee80211/ieee80211_module.c |    1 -
>  net/ieee80211/ieee80211_rx.c     |    1 -
>  net/ieee80211/ieee80211_tx.c     |    1 -

I don't know where these came from since Host AP driver does not include
linux/pci.h into the files doing generic IEEE 802.11 processing. Anyway,
I have nothing against removing these include lines.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ramalhais  Tue May 31 00:27:08 2005
From: ramalhais (Pedro Ramalhais)
Date: Tue, 31 May 2005 08:27:08 +0100
Subject: [PATCH] elektrified wpa_supplicant
Message-ID: <429C11CC.5050709@serrado.net>

If anyone is interested in testing this, i just finished converting 
wpa_supplicant to use libkdb (elektra.sf.net):
http://www.uninova.pt/~pmr/files/WPA/hostap-CVS_2005-05-28_elektra2.diff

Apply to hostap source with -p1 or to wpa_supplicant source with -p2
Run wpa_supplicant once with -c CONFIG_FILE so that it converts the conf 
to kdb, and after that if you run it without -c CONFIG_FILE it will use 
libkdb to get the config.
This will probably help with creating graphical(or other kinds of) 
wireless profile managers and wpa_supplicant config editor.
Now you just have to wait for someone to write a libkdb config editor 
for wireless profiles and wpa_supplicant =:-) (or edit manually).

I added a config_version key to both the wireless and wpa_supplicant 
configuration roots so that we can check which type of data/keys they 
were created. If in the future the config changes to an incompatible 
way, we can check the version.
Also added a bssid->profile_name string which holds a more meaningful 
name than the id number. This would be nice for selecting the profile 
based on the name rather than on the id. Right now i just fill it with 
the profile name read from libkdb.
Profiles converted from the config file are named profileID where ID is 
the network id number.

On a side note, libkdb can be used to listen for key changes. It would 
be very nice if wpa_supplicant could detect these changes and 
reassociate if needed with the new data.

Hope this helps creating a configuration editor for 
wpa_supplicant/wireless profiles.
-- 
Pedro Ramalhais



From roby  Tue May 31 04:51:28 2005
From: roby (roby)
Date: Tue, 31 May 2005 13:51:28 +0200
Subject: Bridge delay.
Message-ID: <20050531115128.24525.qmail@webmaild.fe1.aruba.it>

Hi, 

 I'm doing some performance test on my WLAN. I'm using WPA with EAP/TLS 
authentication sistem. The network is composed of three linux box, 1 
authentication server and 2 access points. All these works fine. 

 At this time I am testing handover delay with VoIP application. The total 
delay time is around 1.07 Sec, but if I analyze the traffic I can see that 
the reauthentication process take just 0.5 sec of the total time. Infact at 
the end of the authentication the access point wait a time between 0.4 and 
0.6 sec to start to forward the traffic. I already check the STP settings, 
and they are fine. I suppose this is a problem of hostap, maybe something 
related with the "Michael" algoritm... 

 I'need to know if I have to modify something in hostap, probably Malinen is 
the best person that can give me suggestion... or if my conjecture is wrong 
please tell me why there are 0.5 seconds of delay before AP starts to 
forward traffic, and how can solve this problem. 

Thank a lot for your help
Roby. 

 


Maybe Malynen can help me, 





From nevynh  Tue May 31 05:00:32 2005
From: nevynh (Nevyn)
Date: Wed, 1 Jun 2005 00:00:32 +1200
Subject: Nokia C110\C111
Message-ID: <bcdb9ee505053105001df231a8@mail.gmail.com>

I'm desperately trying to get the Nokia C110/C111 PCMCIA card going.

I'm the (almost) proud owner of 3 of these cards as they seem to be being 
sold very cheaply at the moment. Has anyone got these drivers working on 
these cards?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050601/0b985981/attachment.htm 


From brix  Tue May 31 05:29:59 2005
From: brix (Henrik Brix Andersen)
Date: Tue, 31 May 2005 14:29:59 +0200
Subject: Nokia C110\C111
In-Reply-To: <bcdb9ee505053105001df231a8@mail.gmail.com>
References: <bcdb9ee505053105001df231a8@mail.gmail.com>
Message-ID: <1117542599.14315.18.camel@sponge.fungus>

On Wed, 2005-06-01 at 00:00 +1200, Nevyn wrote:
> I'm desperately trying to get the Nokia C110/C111 PCMCIA card going.

Those card are prism2/2.5/3 based according to
http://www.linux-wlan.org/docs/wlan_adapters.html.gz - so they ought to
work with the hostap-driver.

You may have to add an entry for those cards
to /etc/pcmcia/hostap_cs.conf.

Sincerely,
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: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050531/1939e375/attachment.pgp 


From jkmaline  Tue May 31 06:07:46 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 06:07:46 -0700
Subject: Nokia C110\C111
In-Reply-To: <1117542599.14315.18.camel@sponge.fungus>
References: <bcdb9ee505053105001df231a8@mail.gmail.com>
	<1117542599.14315.18.camel@sponge.fungus>
Message-ID: <20050531130745.GD7950@jm.kir.nu>

On Tue, May 31, 2005 at 02:29:59PM +0200, Henrik Brix Andersen wrote:
> On Wed, 2005-06-01 at 00:00 +1200, Nevyn wrote:
> > I'm desperately trying to get the Nokia C110/C111 PCMCIA card going.
> 
> Those card are prism2/2.5/3 based according to
> http://www.linux-wlan.org/docs/wlan_adapters.html.gz - so they ought to
> work with the hostap-driver.

No, they are not. They do use Intersil chips, but the MAC is not the
standard HFA3842 used in Prism2 series, but HFA3845 (if I remember
correctly) which seems to have a completely different interface to the
host system and as such, the driver is different and there's not much
hope getting these to work with the Host AP driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 31 06:12:15 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 06:12:15 -0700
Subject: Bridge delay.
In-Reply-To: <20050531115128.24525.qmail@webmaild.fe1.aruba.it>
References: <20050531115128.24525.qmail@webmaild.fe1.aruba.it>
Message-ID: <20050531131215.GE7950@jm.kir.nu>

On Tue, May 31, 2005 at 01:51:28PM +0200, roby wrote:

>  I'm doing some performance test on my WLAN. I'm using WPA with EAP/TLS 
> authentication sistem. The network is composed of three linux box, 1 
> authentication server and 2 access points. All these works fine. 
> 
>  At this time I am testing handover delay with VoIP application. The total 
> delay time is around 1.07 Sec, but if I analyze the traffic I can see that 
> the reauthentication process take just 0.5 sec of the total time. Infact at 
> the end of the authentication the access point wait a time between 0.4 and 
> 0.6 sec to start to forward the traffic. I already check the STP settings, 
> and they are fine. I suppose this is a problem of hostap, maybe something 
> related with the "Michael" algoritm... 

What is this speculation about Michael MIC based on? I see no reason to
believe that would cause 0.5 sec delay. Do you see the same behavior
if you test without using WPA? How did you analyze the traffic? Did you
look at what frames are being sent between the AP and client by using a
wireless sniffer?

-- 
Jouni Malinen                                            PGP id EFC895FA



From roby  Tue May 31 06:32:49 2005
From: roby (roby)
Date: Tue, 31 May 2005 15:32:49 +0200
Subject: Bridge delay.
Message-ID: <20050531133249.4669.qmail@webmaild.fe1.aruba.it>

Hi Jouni, 

   I'll try to answer your questions:

1)What is this speculation about Michael MIC based on?
Please do not care of this conjecture, I know it is wrong. 


2)Do you see the same behavior if you test without using WPA?
No I did not make any test without WPA.. I'll try. 

3)How did you analyze the traffic?
Using Ethereal from the mobile station, end from another computer on the DS. 

4)Did you look at what frames are being sent between the AP and client by 
using a wireless sniffer?
Yes and the access point bridge just the 802.1x messagges... It seems to 
wait a little while before open the controlled port. 

Thk,
Roby. 




From and0806  Tue May 31 07:42:54 2005
From: and0806 (and hansen)
Date: Tue, 31 May 2005 16:42:54 +0200 (CEST)
Subject: madwifi+hostapd
In-Reply-To: <20050530031514.GA7950@jm.kir.nu>
Message-ID: <20050531144254.34052.qmail@web51109.mail.yahoo.com>

> > I have seen that i have to use the bsd branch of
> > the madwifi CVS, but still I can't get this to go
> > I'm using the most current versions of everything
> > madwifi-bsd-cvs, hostapd-cvs, wpa_suppicant-cvs
> > wirelesstools28.pre7 and kernel2.6.11.10
> 
> Please send the configuration file you used with
> hostapd and debug log
> from hostapd when trying to associate a station with
> the AP.
> 
> -- 
> Jouni Malinen                                       
>     PGP id EFC895FA

There is a very big output file at this website
http://www.nethost.dk/debug_dump.txt
an alternative solution can perhaps be
to make a tar ball with your working sourcecode
wpa_supplicant + hostapd + madwifi
and then tell me what kernel version I have to compile
against, plus perhaps the version of wireless tools
you are using, then i'll hopefully end up with a
wireless wpa system for my home brew ap.  and still
whitout the use of tinfoil :)
If more info, testing or anything is needed
then say so.
I dont do c code, but if i can help in other ways
then let me know.

Regards Lasse Jensen




From nevynh  Tue May 31 11:03:09 2005
From: nevynh (Nevyn)
Date: Wed, 1 Jun 2005 06:03:09 +1200
Subject: Nokia C110\C111
In-Reply-To: <20050531130745.GD7950@jm.kir.nu>
References: <bcdb9ee505053105001df231a8@mail.gmail.com>
	<1117542599.14315.18.camel@sponge.fungus>
	<20050531130745.GD7950@jm.kir.nu>
Message-ID: <bcdb9ee505053111037e85c888@mail.gmail.com>

If I were to add an entry in hostap_cs.conf, what would I need to add? The 
output of cardctrl (very roughly and off memory) was something along the 
lines of:

"Nokia" "C110/C111 Wireless Network Card"
"0x0whatever" "0x0whatever"

I had a look at the hostap_cs.conf file and found that it needs name, 
version and those hex addresses. 

On 6/1/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> 
> On Tue, May 31, 2005 at 02:29:59PM +0200, Henrik Brix Andersen wrote:
> > On Wed, 2005-06-01 at 00:00 +1200, Nevyn wrote:
> > > I'm desperately trying to get the Nokia C110/C111 PCMCIA card going.
> >
> > Those card are prism2/2.5/3 based according to
> > http://www.linux-wlan.org/docs/wlan_adapters.html.gz - so they ought to
> > work with the hostap-driver.
> 
> No, they are not. They do use Intersil chips, but the MAC is not the
> standard HFA3842 used in Prism2 series, but HFA3845 (if I remember
> correctly) which seems to have a completely different interface to the
> host system and as such, the driver is different and there's not much
> hope getting these to work with the Host AP driver.
> 
> --
> Jouni Malinen PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20050601/ca6b176e/attachment.htm 


From goldwater716  Tue May 31 11:52:16 2005
From: goldwater716 (GoldWater)
Date: Wed, 1 Jun 2005 02:52:16 +0800
Subject: wired wpa_supplicant-windows-bin-0.4.1
Message-ID: <ac2b10360505311152dc1099@mail.gmail.com>

Dear all:

- I extracted wpa_supplicant-windows-bin-0.4.1 in a winXP (without SP1a),
- ndis_events.exe is running in DOS_prompt
- in another DOS_prompt:
- win_if_list.exe get the following output:
---------------------------------------------------------------------------------------------------------
C:\wpa_supplicant-windows-bin-0.4.1>win_if_list.exe
ifname: \Device\NPF_GenericNdisWanAdapter
description: Generic NdisWan adapter

ifname: \Device\NPF_{3E94358E-F7E1-4DEE-AF8E-34A92F8B084B}
description: Intel(R) PRO Adapter (Microsoft's Packet Scheduler)

ifname: \Device\NPF_{04086B0F-A3D4-4DD7-AAA3-49D44C750165}
description: NET IP/1394 Miniport 
----------------------------------------------------------------------------------------------------------
-After keyin "wpa_supplicant -iIntel -c wpa_supplicant.conf -d", I alway get:

Trying to associate with SSID 'example'
Association request to the driver failed

----------------------------------------------------------------------------------------------------------
do you kindly to tell me, can I use wired Lan card to connect Hostapd?

Thank you!

Best Regards,
Wai Lun



From le.major  Tue May 31 16:06:10 2005
From: le.major (Eric)
Date: Wed, 1 Jun 2005 01:06:10 +0200
Subject: "Unsupported TKIP Group Cipher key length"
Message-ID: <3f9129f505053116066925560c@mail.gmail.com>

Hi,
  I'm trying to get WPA working on my Livebox modem/router and a
madwifi card + wpa_supplicant.

I'm getting these messages from wpa_supplicant:

State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
WPA: RX message 1 of Group Key Handshake from 00:0e:9b:99:1a:38 (ver=1)
WPA: Unsupported TKIP Group Cipher key length 13 (13).
RX EAPOL from 00:0e:9b:99:1a:38
IEEE 802.1X RX: version=1 type=3 length=108
  EAPOL-Key type=254

(looping three times before terminating)

I haven't been able to find any info on this type of error. Is it the
client or the AP's fault?

Ciao.

PS: I'm using wpa_supplicant 0.4.0 and madwifi cvs-2005-05-31.
-- 
Eric



From jkmaline  Tue May 31 19:21:29 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 19:21:29 -0700
Subject: Nokia C110\C111
In-Reply-To: <bcdb9ee505053111037e85c888@mail.gmail.com>
References: <bcdb9ee505053105001df231a8@mail.gmail.com>
	<1117542599.14315.18.camel@sponge.fungus>
	<20050531130745.GD7950@jm.kir.nu>
	<bcdb9ee505053111037e85c888@mail.gmail.com>
Message-ID: <20050601022128.GA15669@jm.kir.nu>

On Wed, Jun 01, 2005 at 06:03:09AM +1200, Nevyn wrote:

> If I were to add an entry in hostap_cs.conf, what would I need to add? The 
> output of cardctrl (very roughly and off memory) was something along the 
> lines of:
> 
> "Nokia" "C110/C111 Wireless Network Card"
> "0x0whatever" "0x0whatever"

If my previous answer was not clear enough, please let me rephrase it:
Nokia C110/C111 does not work with Host AP driver. As such, there is not
much point adding it to hostap_cs.conf.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 31 19:26:33 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 19:26:33 -0700
Subject: wired wpa_supplicant-windows-bin-0.4.1
In-Reply-To: <ac2b10360505311152dc1099@mail.gmail.com>
References: <ac2b10360505311152dc1099@mail.gmail.com>
Message-ID: <20050601022633.GB15669@jm.kir.nu>

On Wed, Jun 01, 2005 at 02:52:16AM +0800, GoldWater wrote:

> - I extracted wpa_supplicant-windows-bin-0.4.1 in a winXP (without SP1a),

> ifname: \Device\NPF_{3E94358E-F7E1-4DEE-AF8E-34A92F8B084B}
> description: Intel(R) PRO Adapter (Microsoft's Packet Scheduler)

> -After keyin "wpa_supplicant -iIntel -c wpa_supplicant.conf -d", I alway get:
> 
> Trying to associate with SSID 'example'
> Association request to the driver failed

> do you kindly to tell me, can I use wired Lan card to connect Hostapd?

The current Windows binary does not support wired network adapters. It
is only built with driver_ndis.c which is trying to configure wireless
OIDs that are not supported by wired Ethernet drivers.

I haven't tested this, but in theory, driver_wired.c might work on
Windows. However, this would require making a new build. If you are
willing to test something experimental and report the results, please
let me know and I should be able to make you a test binary of
wpa_supplicant with driver_wired.c built for Windows. Of course, you can
also build one yourself, if you have a build environment for Windows.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 31 19:34:37 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 19:34:37 -0700
Subject: "Unsupported TKIP Group Cipher key length"
In-Reply-To: <3f9129f505053116066925560c@mail.gmail.com>
References: <3f9129f505053116066925560c@mail.gmail.com>
Message-ID: <20050601023437.GC15669@jm.kir.nu>

On Wed, Jun 01, 2005 at 01:06:10AM +0200, Eric wrote:

>   I'm trying to get WPA working on my Livebox modem/router and a
> madwifi card + wpa_supplicant.
> 
> I'm getting these messages from wpa_supplicant:
> 
> State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
> WPA: RX message 1 of Group Key Handshake from 00:0e:9b:99:1a:38 (ver=1)
> WPA: Unsupported TKIP Group Cipher key length 13 (13).

This sounds like the AP would be advertising that TKIP is used as a
group cipher but the key length sounds more like something for WEP..
Could you please send the full debug log from wpa_supplicant?

> I haven't been able to find any info on this type of error. Is it the
> client or the AP's fault?

How is the AP configured? Are there any options on selecting the group
cipher or something like "allow non-WPA clients"? I haven't seen any AP
doing something that would produce this kind of debug message and it
looks likely that the AP is doing something incorrectly. wpa_supplicant
supports WEP as a group cipher, but that would require that the WPA IE
is advertising WEP, not TKIP..

-- 
Jouni Malinen                                            PGP id EFC895FA



From shawn_yeh  Tue May 31 21:09:36 2005
From: shawn_yeh (shawn_yeh)
Date: 01 Jun 2005 12:09:36 +0800
Subject: A problem : WPA: EAPOL-Key Replay Counter did not increase -
	dropping packet
Message-ID: <1117598976.2845.68.camel@192.168.2.185>

Hi all

I have a problem of connecting to AP by using wpa_supplicant.

I have a CNET AP, and I can always let my device connect to it by
wpa_supplicant.

But after a while it was disconnected, and there were some messages
showed on the console.

WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet

Is there anyone can tell me what the problem is??

Thanks a lot!!



Shawn 




From jkugler  Tue May 31 22:09:48 2005
From: jkugler (Joshua J. Kugler)
Date: Tue, 31 May 2005 21:09:48 -0800
Subject: IPW2100 will not connect to Linksys router
Message-ID: <200505312109.48839.jkugler@bigfoot.com>

I am having trouble with wpa_supplicant (or why else would I be posting, 
right)? :)

NIC: Intel PRO/Wireless LAN 2100 (And latest firmware from 
ipw2100.sf.net)
AP: Linksys BEFW11S4 (802.11b)
Kernel: 2.6.11-6mdk-i586-up-1GB

I have set up WPA on the AP, and it will connect fine from a Windows XP 
box. When I try to connect from this Linux laptop, I get this:

[root at cdesysadminlaptop joshua]# wpa_supplicant -ieth1 
-c/etc/wpa_supplicant.conf -Dipw
Trying to associate with 00:12:17:3c:9c:73 (SSID='hillwireless' freq=0 
MHz)
Associated with 00:12:17:3c:9c:73
WPA: Key negotiation completed with 00:12:17:3c:9c:73 [PTK=TKIP 
GTK=TKIP]
WPA: Group rekeying completed with 00:12:17:3c:9c:73 [GTK=TKIP]
Disconnect event - remove keys
Trying to associate with 00:12:17:3c:9c:73 (SSID='hillwireless' freq=0 
MHz)
Associated with 00:12:17:3c:9c:73
WPA: Key negotiation completed with 00:12:17:3c:9c:73 [PTK=TKIP 
GTK=TKIP]
WPA: Group rekeying completed with 00:12:17:3c:9c:73 [GTK=TKIP]
Disconnect event - remove keys

Over and over and over.
Here's my config, based on the Mandrake initial, and the wap_supplicant 
example:

network={
    ssid="hillwireless"
    psk="blahblahblahblah"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=TKIP NONE
    group=TKIP WEP104 WEP40
    scan_ssid=0
    priority=2
}

Using debug gives (not sure where it starts repeating, so you'll get 
quite a
dump).

Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 
'ipw'
Configuration file '/etc/wpa_supplicant.conf' -> 
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 2 - start of a new network block
ssid - hexdump_ascii(len=12):
     68 69 6c 6c 77 69 72 65 6c 65 73 73               hillwireless    
PSK - hexdump(len=32): [REMOVED]
proto: 0x1
key_mgmt: 0x2
pairwise: 0x9
group: 0xe
scan_ssid=0 (0x0)
priority=2 (0x2)
Priority group 2
   id=0 ssid='hillwireless'
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
Own MAC address: 00:04:23:53:49:e9
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
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
Starting AP scan (broadcast SSID)
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
Scan timeout - try to get results
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 2
No suitable AP found.
Setting scan request: 5 sec 0 usec
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
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 
idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 
idleWhile=0
Starting AP scan (broadcast SSID)
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
Scan timeout - try to get results
Received 255 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:12:17:3c:9c:73 ssid='hillwireless' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:12:17:3c:9c:73 (SSID='hillwireless' freq=0 
MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=25
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 
idleWhile=0
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:12:17:3c:9c:73
Association event - clear replay counter
Associated to a new BSS: BSSID=00:12:17:3c:9c:73
No keys have been configured - skip key clearing
Associated with 00:12:17:3c:9c:73
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 'eth1' added
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=29 
idleWhile=59
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=28 
idleWhile=58
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=27 
idleWhile=57
RX EAPOL from 00:12:17:3c:9c:73
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 7b 3b 0e 52 87 5d 
6c 2c a0 d4 6d c9 62 e3 8f 5b 9c 92 55 be d6 63 ab 0d ed ff 2e 1c 8e 8f 
7d ec f3 fa 47 58 5e 2c 5e 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 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
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 7b 3b 0e 
52 87 5d 6c 2c a0 d4 6d c9 62 e3 8f 5b 9c 92 55 be d6 63 ab 0d ed ff 2e 
1c 8e 8f 7d ec f3 fa 47 58 5e 2c 5e 38 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00:12:17:3c:9c:73 (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): 84 03 d3 0b e7 d9 55 2e 11 8e 54 
a2 2a ce d7 c6 59 0e 71 91 b1 9a 96 fc ed 3d af 0b f9 87 dd 98
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: EAPOL-Key MIC - hexdump(len=16): 4d 17 8a 69 68 d0 55 1a c3 da 62 
5e b0 b6 e0 79
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 12 17 3c 9c 73 00 04 23 53 
49 e9 88 8e 01 03 00 77 fe 01 09 00 20 7b 3b 0e 52 87 5d 6c 2c 84 03 d3 
0b e7 d9 55 2e 11 8e 54 a2 2a ce d7 c6 59 0e 71 91 b1 9a 96 fc ed 3d af 
0b f9 87 dd 98 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 4d 17 8a 69 68 d0 55 1a c3 da 62 
5e b0 b6 e0 79 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 00:12:17:3c:9c:73
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 7b 3b 0e 52 87 
5d 6c 2d a0 d4 6d c9 62 e3 8f 5b 9c 92 55 be d6 63 ab 0d ed ff 2e 1c 8e 
8f 7d ec f3 fa 47 58 5e 2c 5e 38 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f a3 69 66 54 
28 35 8f 7f fb c3 58 2b 12 78 af 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: Ignoring WPA EAPOL-Key frame in EAPOL state machines
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 01 c9 00 20 7b 3b 
0e 52 87 5d 6c 2d a0 d4 6d c9 62 e3 8f 5b 9c 92 55 be d6 63 ab 0d ed ff 
2e 1c 8e 8f 7d ec f3 fa 47 58 5e 2c 5e 38 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f a3 
69 66 54 28 35 8f 7f fb c3 58 2b 12 78 af 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
WPA: RX message 3 of 4-Way Handshake from 00:12:17:3c:9c:73 (ver=1)
WPA: IE KeyData - 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: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 12 17 3c 9c 73 00 04 23 53 
49 e9 88 8e 01 03 00 5f fe 01 09 00 20 7b 3b 0e 52 87 5d 6c 2d 84 03 d3 
0b e7 d9 55 2e 11 8e 54 a2 2a ce d7 c6 59 0e 71 91 b1 9a 96 fc ed 3d af 
0b f9 87 dd 98 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 38 cc d8 e9 ac 23 93 93 0b ba 29 
c7 51 6e ff 38 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_ipw_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
RX EAPOL from 00:12:17:3c:9c:73
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 7b 3b 0e 52 87 
5d 6c 2e f1 3c a1 8a a5 bd ea 01 81 04 15 72 02 bf 6d 46 16 42 c6 08 61 
d2 b9 7c e4 fb 7f 7d 1e 0a 96 56 0d e7 04 89 3b 0b 54 34 7d 88 4b 11 4b 
e6 6b ac 4a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4f 71 64 42 db 
87 49 d4 a4 b8 60 68 63 6e e1 2a 00 20 31 bd 5e 96 2a 4d 77 60 49 4a 45 
c7 23 c8 e1 54 88 95 74 4b cf f2 94 4b 31 05 2b e5 68 ef 71 60
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=127
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 7b 3b 
0e 52 87 5d 6c 2e f1 3c a1 8a a5 bd ea 01 81 04 15 72 02 bf 6d 46 16 42 
c6 08 61 d2 b9 7c e4 fb 7f 7d 1e 0a 96 56 0d e7 04 89 3b 0b 54 34 7d 88 
4b 11 4b e6 6b ac 4a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4f 71 
64 42 db 87 49 d4 a4 b8 60 68 63 6e e1 2a 00 20 31 bd 5e 96 2a 4d 77 60 
49 4a 45 c7 23 c8 e1 54 88 95 74 4b cf f2 94 4b 31 05 2b e5 68 ef 71 60
WPA: RX message 1 of Group Key Handshake from 00:12:17:3c:9c:73 (ver=1)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 4a 00 00 00 00 00
wpa_driver_ipw_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 12 17 3c 9c 73 00 04 23 53 
49 e9 88 8e 01 03 00 5f fe 03 11 00 20 7b 3b 0e 52 87 5d 6c 2e 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 87 54 01 27 e3 5a 19 71 c4 a7 63 
be 98 9f 2c 0e 00 00
WPA: Key negotiation completed with 00:12:17:3c:9c:73 [PTK=TKIP 
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=26 
idleWhile=56
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=25 
idleWhile=55
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=24 
idleWhile=54
RX EAPOL from 00:12:17:3c:9c:73
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 7b 3b 0e 52 87 
5d 6c 2f f1 3c a1 8a a5 bd ea 01 81 04 15 72 02 bf 6d 46 16 42 c6 08 61 
d2 b9 7c e4 fb 7f 7d 1e 0a 96 56 4d 1b 53 bf 8e 30 83 7e 99 bc 70 1e be 
4d db 79 4b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe 92 56 0b 47 
63 fd bd 05 48 67 0d 1a 89 00 a0 00 20 8d 02 dd e7 09 97 47 39 e2 f8 e8 
f5 c6 2e 47 8a f1 98 d4 d5 b6 d1 7f 70 d4 a0 78 94 65 eb 20 ab
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=127
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 91 00 20 7b 3b 
0e 52 87 5d 6c 2f f1 3c a1 8a a5 bd ea 01 81 04 15 72 02 bf 6d 46 16 42 
c6 08 61 d2 b9 7c e4 fb 7f 7d 1e 0a 96 56 4d 1b 53 bf 8e 30 83 7e 99 bc 
70 1e be 4d db 79 4b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe 92 
56 0b 47 63 fd bd 05 48 67 0d 1a 89 00 a0 00 20 8d 02 dd e7 09 97 47 39 
e2 f8 e8 f5 c6 2e 47 8a f1 98 d4 d5 b6 d1 7f 70 d4 a0 78 94 65 eb 20 ab
WPA: RX message 1 of Group Key Handshake from 00:12:17:3c:9c:73 (ver=1)
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 4b 00 00 00 00 00
wpa_driver_ipw_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 12 17 3c 9c 73 00 04 23 53 
49 e9 88 8e 01 03 00 5f fe 03 11 00 20 7b 3b 0e 52 87 5d 6c 2f 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 a7 25 c9 f0 bb 96 9b be 0a 68 81 
e2 d8 60 13 da 00 00
WPA: Group rekeying completed with 00:12:17:3c:9c:73 [GTK=TKIP]
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
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' 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:12:17:3c:9c:73 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_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Starting AP scan (broadcast SSID)
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=20 
idleWhile=50
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=19 
idleWhile=49
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=18 
idleWhile=48
Scan timeout - try to get results
Received 255 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:12:17:3c:9c:73 ssid='hillwireless' wpa_ie_len=24 rsn_ie_len=0
   skip - blacklisted
No APs found - clear blacklist and try again
Removed BSSID 00:12:17:3c:9c:73 from blacklist (clear)
Selecting BSS from priority group 2
0: 00:12:17:3c:9c:73 ssid='hillwireless' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:12:17:3c:9c:73 (SSID='hillwireless' freq=0 
MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
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
wpa_driver_ipw_set_drop_unencrypted: enabled=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
Wireless event: cmd=0x8b1a len=25
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=17 
idleWhile=47
Signal 2 received - terminating
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
wpa_driver_ipw_set_drop_unencrypted: enabled=0
wpa_driver_ipw_set_countermeasures: enabled=0


So, there you go...if you need more logs, let me know.  What I don't 
understand is why my AP get's "blacklisted."  What is it doing wrong?

I'm on vacation, and this is the first time I've tried to hook up to a 
WPA AP, so any help is appreciated!

Thanks so much!!

j----- k-----
-- 
Joshua J. Kugler -- Fairbanks, Alaska -- ICQ#:13706295
Every knee shall bow, and every tongue confess, in heaven, on earth, and 
under the earth, that Jesus Christ is LORD -- Count on it!



From jkmaline  Tue May 31 22:00:33 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 22:00:33 -0700
Subject: [PATCH] elektrified wpa_supplicant
In-Reply-To: <429C11CC.5050709@serrado.net>
References: <429C11CC.5050709@serrado.net>
Message-ID: <20050601050033.GD15669@jm.kir.nu>

On Tue, May 31, 2005 at 08:27:08AM +0100, Pedro Ramalhais wrote:

> If anyone is interested in testing this, i just finished converting 
> wpa_supplicant to use libkdb (elektra.sf.net):
> http://www.uninova.pt/~pmr/files/WPA/hostap-CVS_2005-05-28_elektra2.diff

I know kdb, but it has nothing to do with elektra, but more so with
kernel debugging.. ;-) In other words, I'm not familiar with
libkdb/elektra. Where is it used currently?

The current patch would need some work on getting rid of ifdef's if it
is to be merged into my tree. Actually, it might be worthwhile
implementing this as a separate configuration "provider" as an option to
the current config.c instead of trying to make both of the
implementations fit the same file.

I have some plans on changing the wpa_supplicant configuration interface
to provide easier way of changing the backend in a similar way to the
current driver interface. In addition, one part of the planned changes
would be to add support for storing changes and new data into the
configuration database (note that a text file is one form of database
;-).

> Hope this helps creating a configuration editor for 
> wpa_supplicant/wireless profiles.

My current priority on this area is in getting the wpa_supplicant
control interface to support modifying configuration. This would mean
that the GUI would not need to edit the configuration data file, but to
use wpa_supplicant to do this. This would then use the selected
configuration backend (one of which could be Elektra).

I would hope to get both wpa_gui and wpa_cli using the control interface
to configure wpa_supplicant. Until this is done, I'm unlikely to have
much time available on looking at how the configuration database would
be edited directly without going through wpa_supplicant. Though, of
course this should not prevent others from working on it ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue May 31 22:21:53 2005
From: jkmaline (Jouni Malinen)
Date: Tue, 31 May 2005 22:21:53 -0700
Subject: A problem : WPA: EAPOL-Key Replay Counter did not increase -
	dropping packet
In-Reply-To: <1117598976.2845.68.camel@192.168.2.185>
References: <1117598976.2845.68.camel@192.168.2.185>
Message-ID: <20050601052153.GE15669@jm.kir.nu>

On Wed, Jun 01, 2005 at 12:09:36PM +0800, shawn_yeh wrote:

> I have a problem of connecting to AP by using wpa_supplicant.
> 
> I have a CNET AP, and I can always let my device connect to it by
> wpa_supplicant.
> 
> But after a while it was disconnected, and there were some messages
> showed on the console.
> 
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet
> WPA: EAPOL-Key Replay Counter did not increase - dropping packet
> 
> Is there anyone can tell me what the problem is??

Please send a full debug log from wpa_supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA



From joshua.yang  Tue May 31 23:02:36 2005
From: joshua.yang (=?euc-kr?B?vue9wr/r?=)
Date: Wed, 01 Jun 2005 06:02:36 +0000 (GMT)
Subject: Structure alignment
Message-ID: <5394183.1117605627280.JavaMail.weblogic@ep_ml16>

Hi all

In wpa.h (0.4.1 release)

I have seen the following line

struct ieee802_1x_eapol_key {
    u8 type;
    u16 key_length;
    /* does not repeat within the life of the keying material used to
     * encrypt the Key field; 64-bit NTP timestamp MAY be used here */
    u8 replay_counter[IEEE8021X_REPLAY_COUNTER_LEN];
    ...
}

which in not 16bit aligned. If wpa_supplicant is built with visual c++ 6.0, It will cause problem

I suggest that the above structure may be

struct ieee802_1x_eapol_key {
    u8 type;
    u8 key_length[2];
    /* does not repeat within the life of the keying material used to
     * encrypt the Key field; 64-bit NTP timestamp MAY be used here */
    u8 replay_counter[IEEE8021X_REPLAY_COUNTER_LEN];
    ...
}

in code which is dealing with above structure.

memcpy key_length to temporary u16 variable and convert temporary variable to host order variable.

...

=====================================================
??????(?)
??? ??? ??? 261-8 ???? 5? ?????
?????? XIA ??   ? ? ?
Tel. 02-390-8077     Fax. 02)390-8099
Hp. 016-383-6558     Email. joshua.yang at samsung.com
=====================================================


