From kshogan  Mon Nov  1 01:33:17 2004
From: kshogan (Kshogan)
Date: Mon, 01 Nov 2004 10:33:17 +0100
Subject: No subject
Message-ID: <bbiluabqewhcclgvnjn@shmoo.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041101/dd630d37/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Joke.scr
Type: application/octet-stream
Size: 18897 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041101/dd630d37/attachment.obj 


From thevedado  Mon Nov  1 04:20:23 2004
From: thevedado (michael schatz)
Date: Mon, 1 Nov 2004 04:20:23 -0800 (PST)
Subject: WDS link problem: ping only
In-Reply-To: <200411010919.50394.vda@port.imtp.ilyichevsk.odessa.ua>
Message-ID: <20041101122023.11054.qmail@web21521.mail.yahoo.com>

denis-
thanks for your responses---i think you understand my difficulty well, but i'm not
sure i understand what to do based on your suggestions...see below

Denis Vlasenko <vda at port.imtp.ilyichevsk.odessa.ua> wrote: 

On Monday 01 November 2004 06:05, michael schatz wrote:
> 
> Hi-
> I've established a WDS static link between two APs running hostAP (call
> them AP:A and AP:B) under RedHat 9.0. AP:A and all wireless devices that
> associate with it have full access to the internet (ping, DNS, web
> browsing, ssh, etc). AP:B also has full access to the internet, but
> all wireless devices associated with AP:B can only ping (only by using IP

ping what? ping anything? ping AP only?


everything behind AP:B can ping anything (AP:B, AP:A, wireless devices on AP:A, anything on the internet) but only if i use the explicit IP address-i.e. host names are not resolved.


> addresses)....nothing else works( no DNS, no ssh, no web
> browsing, etc). below
> i give the architecture and the scripts on both APs (/etc/rc.local)
> that i use to set up the WDS link with ipforwarding and routing. could
> someone suggest what i'm missing in configuring the forwarding/routing
> of AP:B's devices?
> 
> 
> Thanks!
> 
> Mike
> 


You most probably meant this:

INTERNET via router (192.168.0.1)
|
|
eth0 (192.168.0.7)
AP-A wlan0 (10.1.2.1) -- 
10.1.2.254/30
|
WDS
|
10.1.2.253/30
AP-B wlan0 (10.1.3.1) --


yes, denis---your sketch is better and correct.

 

 


> ********AP:A initialization script********
> #!/bin/sh
> #
> 
> touch /var/lock/subsys/local
> echo "Local wlan0 config. stuff"
> /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 15
> 
> echo "setup WDS static link"
> #MAC address below from AP on other end of the link
> iwpriv wlan0 wds_add BB:BB:BB:BB:BB:BB
> ip addr add 10.1.2.254/30 broadcast 10.1.2.255 dev wlan0wds0
> ip link set wlan0wds0 up
> 
> echo "Enabling IP Masquerading"
> /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> echo "1" >/proc/sys/net/ipv4/ip_forward

You dont have any routing setup here.
Does AP-A know how to reach 10.1.3.x?
If not, nothing will work from behind AP-B.



you are exactly right!.....AP-A  _cannot_ reach 10.1.3.x   i think this is the main problem...how specifically do i correct this?

 


> ********AP:B initialization script********
> 
> #!/bin/sh
> #
> touch /var/lock/subsys/local
> echo "Local wlan0 config. stuff"
> /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 23
> 
> echo "set up WDS static link"
> #MAC address below from other end of link
> iwpriv wlan0 wds_add AA:AA:AA:AA:AA:AA
> 
> ip addr add 10.1.2.253/30 broadcast 10.1.2.255 dev wlan0wds0
> ip link set wlan0wds0 up
> 
> echo "Enabling IP Masquerading"
> /sbin/iptables -t nat -A POSTROUTING -o wlan0wds0 -j MASQUERADE
> /sbin/route add -net default gw 10.1.2.254 metric 1
> 
> echo "1" >/proc/sys/net/ipv4/ip_forward

This looks ok.

BTW, use tcpdump to see what's going on the 'wire'.
--


How specifically do i use tcpdump in this case?

 



 


		
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041101/8be2298e/attachment.htm 


From vda  Mon Nov  1 05:15:19 2004
From: vda (Denis Vlasenko)
Date: Mon, 1 Nov 2004 15:15:19 +0200
Subject: WDS link problem: ping only
In-Reply-To: <20041101122023.11054.qmail@web21521.mail.yahoo.com>
References: <20041101122023.11054.qmail@web21521.mail.yahoo.com>
Message-ID: <200411011515.19934.vda@port.imtp.ilyichevsk.odessa.ua>

On Monday 01 November 2004 14:20, michael schatz wrote:
> denis-
> thanks for your responses---i think you understand my difficulty well, but i'm not
> sure i understand what to do based on your suggestions...see below
> 
> Denis Vlasenko <vda at port.imtp.ilyichevsk.odessa.ua> wrote: 
> 
> On Monday 01 November 2004 06:05, michael schatz wrote:
> > 
> > Hi-
> > I've established a WDS static link between two APs running hostAP (call
> > them AP:A and AP:B) under RedHat 9.0. AP:A and all wireless devices that
> > associate with it have full access to the internet (ping, DNS, web
> > browsing, ssh, etc). AP:B also has full access to the internet, but
> > all wireless devices associated with AP:B can only ping (only by using IP
> 
> ping what? ping anything? ping AP only?
> 
> 
> everything behind AP:B can ping anything (AP:B, AP:A, wireless devices on AP:A, anything on the internet) but only if i use the explicit IP address-i.e. host names are not resolved.

Your routing/firewall is correct, then. Only DNS is messed up.

Do "ping www.yahoo.com" and watch tcpdumps, you
will see where do DNS requests are going,
and wheter there is any reply.

Check /etc/resolv.conf

> You most probably meant this:
> 
> INTERNET via router (192.168.0.1)
> |
> |
> eth0 (192.168.0.7)
> AP-A wlan0 (10.1.2.1) -- 
> 10.1.2.254/30
> |
> WDS
> |
> 10.1.2.253/30

> AP-B wlan0 (10.1.3.1) --
> > ********AP:A initialization script********
> > #!/bin/sh
> > #
> > 
> > touch /var/lock/subsys/local
> > echo "Local wlan0 config. stuff"
> > /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 15
> > 
> > echo "setup WDS static link"
> > #MAC address below from AP on other end of the link
> > iwpriv wlan0 wds_add BB:BB:BB:BB:BB:BB
> > ip addr add 10.1.2.254/30 broadcast 10.1.2.255 dev wlan0wds0
> > ip link set wlan0wds0 up
> > 
> > echo "Enabling IP Masquerading"
> > /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> > echo "1" >/proc/sys/net/ipv4/ip_forward
> 
> You dont have any routing setup here.
> Does AP-A know how to reach 10.1.3.x?
> If not, nothing will work from behind AP-B.
> 
> you are exactly right!.....AP-A  _cannot_ reach 10.1.3.x   i think this is the main problem...how specifically do i correct this?

At closer examination, you have MASQed out 10.1.3.x

You can leave it as is if you do want 10.1.3.x
firewalled from outside.

Or remove MASQ and add routing rule on AP-A so that it
knows thtat there is a subnet behind AP-B's ip:

> > ********AP:B initialization script********
> > 
> > #!/bin/sh
> > #
> > touch /var/lock/subsys/local
> > echo "Local wlan0 config. stuff"
> > /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 23
> > 
> > echo "set up WDS static link"
> > #MAC address below from other end of link
> > iwpriv wlan0 wds_add AA:AA:AA:AA:AA:AA
> > 
> > ip addr add 10.1.2.253/30 broadcast 10.1.2.255 dev wlan0wds0
> > ip link set wlan0wds0 up
> > 
> > echo "Enabling IP Masquerading"
> > /sbin/iptables -t nat -A POSTROUTING -o wlan0wds0 -j MASQUERADE
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

remove this, then add on AP-A:

ip route add 10.1.3.0/24 via 10.1.2.253

> BTW, use tcpdump to see what's going on the 'wire'.
> 
> How specifically do i use tcpdump in this case?

tcpdump -nli<interface>
--
vda




From yenjung  Mon Nov  1 18:29:56 2004
From: yenjung (YenJung Chang)
Date: Tue, 2 Nov 2004 10:29:56 +0800
Subject: How to get certificate
Message-ID: <32653c97041101182978601c90@mail.gmail.com>

Hi, 

I am a newbie on wpa_supplicant and I am testing its features,
however, I don't know how to get or setup a certificate in station
side.
Is there any document teaching this?
or would someone like to tell me how to do?
Any advice is appreciated.
Thanks.

Regards,
yj.



From ceyong  Mon Nov  1 21:32:53 2004
From: ceyong (Yong Chu Eu رَطسسس)
Date: Mon, 1 Nov 2004 21:32:53 -0800 (PST)
Subject: Driver for device wlan0 has been compiled with version 16 of
	Wireless Extension, while this program is using version 15
Message-ID: <20041102053253.51998.qmail@web54606.mail.yahoo.com>

[root at localhost root]# iwconfig wlan0 txpower 150
Warning: Driver for device wlan0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Operation not supported.
[root at localhost root]# iwconfig wlan0 txpower 150
Warning: Driver for device wlan0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Operation not supported.
[root at localhost root]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

Warning: Driver for device wifi0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

wifi0     IEEE 802.11b  ESSID:"homenetwork" 
Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:04:75:88:7F:9C
          Bit Rate=11Mb/s   Sensitivity=1/0
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:230   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"homenetwork" 
Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:04:75:88:7F:9C
          Bit Rate=11Mb/s   Sensitivity=1/0
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:230   Missed beacon:0


=====
???????????????????????? Happy & Healthy Always ! ^_^ !
?????????????? Homepage:ceyong.alturl.com
ICQ:16994867/ Yahoo Messenger ID:ceyong 
MSN Messenger:ceyong at hotmail.com


		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From ceyong  Tue Nov  2 01:26:49 2004
From: ceyong (Yong Chu Eu رَطسسس)
Date: Tue, 2 Nov 2004 01:26:49 -0800 (PST)
Subject: problem in Wireless Extension
Message-ID: <20041102092649.31964.qmail@web54607.mail.yahoo.com>

i am install hostap driver on my redhat linux 2.4.26, any one can help? i
try on few version kernel of linux

[root at localhost root]# iwconfig wlan0 txpower 150
Warning: Driver for device wlan0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Operation not supported.
[root at localhost root]# iwconfig wlan0 txpower 150
Warning: Driver for device wlan0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

Error for wireless request "Set Tx Power" (8B26) :
    SET failed on device wlan0 ; Operation not supported.
[root at localhost root]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

Warning: Driver for device wifi0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

wifi0     IEEE 802.11b  ESSID:"homenetwork" 
Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:04:75:88:7F:9C
          Bit Rate=11Mb/s   Sensitivity=1/0
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:230   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"homenetwork" 
Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:04:75:88:7F:9C
          Bit Rate=11Mb/s   Sensitivity=1/0
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:230   Missed beacon:0




=====
???????????????????????? Happy & Healthy Always ! ^_^ !
?????????????? Homepage:ceyong.alturl.com
ICQ:16994867/ Yahoo Messenger ID:ceyong 
MSN Messenger:ceyong at hotmail.com


		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From trepo  Tue Nov  2 01:37:12 2004
From: trepo (Viliam Trepak)
Date: Tue, 02 Nov 2004 10:37:12 +0100
Subject: problem in Wireless Extension
In-Reply-To: <20041102092649.31964.qmail@web54607.mail.yahoo.com>
References: <20041102092649.31964.qmail@web54607.mail.yahoo.com>
Message-ID: <1099388232.30407.57.camel@hq.netcomga.sk>

On Tue, 2004-11-02 at 10:26, Yong Chu Eu (??????) wrote:
> i am install hostap driver on my redhat linux 2.4.26, any one can help? i
> try on few version kernel of linux
> 
> [root at localhost root]# iwconfig wlan0 txpower 150
> Warning: Driver for device wlan0 has been compiled with version 16
> of Wireless Extension, while this program is using version 15.
> Some things may be broken...
You will have to recompile the wireless tools to get rid of the warning.

> Error for wireless request "Set Tx Power" (8B26) :
>     SET failed on device wlan0 ; Operation not supported.
What card? What firmware? Which version of HostAP driver?
(I assume it's the latest, but don't let us make assumptions - provide some data)

Viliam Trepak
----------------
If at first you do succeed, try to hide your astonishment.




From jperez  Tue Nov  2 01:40:14 2004
From: jperez (=?iso-8859-1?Q?Juana_P=E9rez?=)
Date: Tue, 2 Nov 2004 10:40:14 +0100
Subject: signal strength value with prism 3
Message-ID: <01af01c4c0bf$f97b7240$9a28a8c0@jperez>

Hi,
I was developing a kind of sniffer to meassure the signal strength value from client frames, the problem is that I was using a prism 2/2.5 chipset and it is going to be sold out. It is not going to be produced anymore. The shop I was buying the wireless cards from is producing the cards with the prism 3 chipset. Is it possible to monitore the signal strength value with this chipset? 
Thanks in advance


Juana P?rez Soto

-------------------------------------------------------
Fagor Electr?nica, S. Coop.
Centro de Desarrollo Tecnol?gico
C/ Avd. de los Castros S/N
39005 Santander, Espa?a
 
Tel?fono:   +34 942 291400
Fax:        +34 942 200921
 
Email:  jperez at fagorelectronica.es
Web:    www.fagorelectronica.com

______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041102/f6ab4ec6/attachment.htm 


From ceyong  Tue Nov  2 04:19:51 2004
From: ceyong (Yong Chu Eu رَطسسس)
Date: Tue, 2 Nov 2004 04:19:51 -0800 (PST)
Subject: problem in Wireless Extension
Message-ID: <20041102121951.64434.qmail@web54601.mail.yahoo.com>

Thanks for kindly reply

i am using 3com Airconnect 3CRWE777A-E1 network card with firmware 1.5.6(i
flashing it from 0.8.3 with hostap-utilities), i try hostap driver from
version 0.1.3,0.2.0 to 0.2.5. same problem happend. i suspect maybe
Wireless Extension on kernel 2.4.26 cannot support HOSTAP, i did not have
any problem on my redhat 9.0 with kernel 2.4.20 and kernel 2.4.22. 

I recompile my redhat linux 9.0 to kernel 2.4.26.


sorry to ask , i need to recompile wireless tool? what wireless tool u
mean here? recompile kernel? i tried even reinstall redhat 9.0 and
recompile to kernel 2.4.26. recompile hostap-driver? i tried 


On Tue, 2004-11-02 at 10:26, Yong Chu Eu (??????) wrote:
> i am install hostap driver on my redhat linux 2.4.26, any one can help?
i
> try on few version kernel of linux
> 
> [root at localhost root]# iwconfig wlan0 txpower 150
> Warning: Driver for device wlan0 has been compiled with version 16
> of Wireless Extension, while this program is using version 15.
> Some things may be broken...
You will have to recompile the wireless tools to get rid of the warning.

> Error for wireless request "Set Tx Power" (8B26) :
>     SET failed on device wlan0 ; Operation not supported.
What card? What firmware? Which version of HostAP driver?
(I assume it's the latest, but don't let us make assumptions - provide
some data)

Viliam Trepak
----------------
If at first you do succeed, try to hide your astonishment.

=====
???????????????????????? Happy & Healthy Always ! ^_^ !
?????????????? Homepage:ceyong.alturl.com
ICQ:16994867/ Yahoo Messenger ID:ceyong 
MSN Messenger:ceyong at hotmail.com


		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From Frank.Cole  Tue Nov  2 09:23:33 2004
From: Frank.Cole (Cole Frank Contr AFRL/IFGC)
Date: Tue, 2 Nov 2004 17:23:33 -0000 
Subject: signal strength value with prism 3
Message-ID: <8FF908802100A9419F2792537D08AF1809C6ADCF@fsjrez02.adm.rl.af.mil>


Absolutely. The receive signal strength (RSSI) measurement is calculated a
little differently depending on
how you want to use it but is still available. Pretty much everything else
is the same.

Which driver set are you using?

Frank Cole
// Wireless Information Assurance Laboratory //
// Air Force Research Lab/Rome Research Site //
// COM: (315) 330-3686 DSN: 587-3686 // 

-----Original Message-----
From: hostap-bounces+frank.cole=rl.af.mil at shmoo.com
[mailto:hostap-bounces+frank.cole=rl.af.mil at shmoo.com] On Behalf Of Juana
P?rez
Sent: Tuesday, November 02, 2004 4:40 AM
To: ListaHOSTAP
Subject: signal strength value with prism 3


Hi,
I was developing a kind of sniffer to meassure the signal strength value
from client frames, the problem is that I was using a prism 2/2.5 chipset
and it is going to be sold out. It is not going to be produced anymore. The
shop I was buying the wireless cards from is producing the cards with the
prism 3 chipset. Is it possible to monitore the signal strength value with
this chipset? 
Thanks in advance


Juana P?rez Soto

-------------------------------------------------------
Fagor Electr?nica, S. Coop.
Centro de Desarrollo Tecnol?gico
C/ Avd. de los Castros S/N
39005 Santander, Espa?a
 
Tel?fono:   +34 942 291400
Fax:        +34 942 200921
 
Email:  jperez at fagorelectronica.es
Web:    www.fagorelectronica.com

______________________________________________________________________



From simon.kagstrom  Tue Nov  2 10:58:01 2004
From: simon.kagstrom (Simon Kagstrom)
Date: Tue, 2 Nov 2004 19:58:01 +0100
Subject: SWSUPPORT write/read failed
Message-ID: <20041102185801.GA17523@ipdska.ipd.bth.se>

Hello!

I'm trying to understand why the Sandisk Connectplus card doesn't work. One
thing which I don't understand is why the write to SWSUPPORT0 isn't working. I
get results as

SWSUPPORT0 write/read failed: 8AFF != 8A32

when inserting the card. Before this, there are some other errors

prism2_config()
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0047, io.base=0x0000, len=128
hostap_cs: Registered netdevice wifi0
wifi0: Interrupt, but dev not OK
hostap_cs: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x017f
prism2_hw_init()
wifi0: init command completed too quickly - retrying
prism2_hw_init: initialized in 0 ms
prism2_enable_aux_port(1) timed out
wifi0: trying to read PDA from 0x007f0000: failed
wifi0: trying to read PDA from 0x003f0000: failed
wifi0: trying to read PDA from 0x00390000: failed
wifi0: trying to read PDA from 0x007f0002: failed
prism2_enable_aux_port: was not enabled!?


should the SWSUPPORT0 write work if the card isn't configured properly before
(especially the "Interrupt, but dev not OK" looks suspicious).

When delaying a bit after the write to SWSUPPORT, I get 00ff instead when
reading it.

Are there any parts of the prism3 support still missing by the way?

// Simon



From arttysta  Wed Nov  3 02:29:45 2004
From: arttysta (arttysta)
Date: Wed, 3 Nov 2004 11:29:45 +0100
Subject: Firmware upload
Message-ID: <000801c4c190$0bfc44f0$8201a8c0@artline5stqgle>

    How to upload firmware into card ?

type o firmware
   ak010104.hex -primary
   rf010803.hex - secondary

this firmwares are compatybile with my card
but i can't upload them even with command 
prism2_srec -g wlan0 ak010104.hex 
or
prism2_srec -r wlan0 rf010803.hex 

Can any one help me with this thing ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041103/08ff8e0e/attachment.htm 


From gentoopower  Wed Nov  3 03:16:38 2004
From: gentoopower (Kuckuck Kuckuck)
Date: Wed, 3 Nov 2004 12:16:38 +0100 (CET)
Subject: No AP with WPA found , got lots of debug info to troubleshoot this
Message-ID: <20041103111638.50651.qmail@web51101.mail.yahoo.com>

Hi guys,

I have tried to use ndiswrapper yerterday and
encountered the following problem.
When starting wpa_supplicant it doesn't find my AP,
but the AP is up and working, as I'm using also a
windows laptop which is connected to the AP and is
connected using WPA-PSK TKIP.

I tried the both stable and latest sources of
ndiswrapper & wpa_supplicant , my box is running
gentoo
with kernel 2.6.7.

I'm not sure if this is a problem of wireless-tools(I
got the latest installed), ndiswrapper or
wpa_supplicant.
That's why I added as much information, in my
debugfile I sent ,I could find.

Any help would be greatly appreciated


	

	
		
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debugwlan0.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20041103/a2b524ac/attachment.txt 


From fstakkel  Wed Nov  3 03:55:59 2004
From: fstakkel (petra lastand)
Date: Wed, 3 Nov 2004 03:55:59 -0800 (PST)
Subject: Authentication timed out, ndiswrapper
Message-ID: <20041103115559.22543.qmail@web41901.mail.yahoo.com>

Trying to use wpa-psk with ndiswrapper. Network-card
is DWL-510 and router DI-514. This is the
wpa_supplicant.conf:

network={
        ssid="default"
        psk="secret key"
        priority=5
}

Output from wpa_supplicant -dd

Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
SSID - hexdump_ascii(len=7):
     64 65 66 61 75 6c 74                             
default         
PSK (ASCII passphrase) - hexdump_ascii(len=61):
     "secret key -> removed"  
priority=5
PSK (from passphrase) - hexdump(len=32): bd 52 ab af
c1 fd a1 b4 59 35 23 59 60 97 50 9e 60 59 48 0e d1 66
a4 ac f8 e3 1f b5 85 24 6a 24
Priority group 5
   id=0 ssid='default'
Setting scan request: 0 sec 100000 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Wireless event: cmd=0x8c02 len=133
Custom wireless event:
'ASSOCINFO(ReqIEs=000764656661756c74010482848b96dd180050f20101000050f20201000050f20201000050f2020000
RespIEs=010482848b96)'
Association info event
req_ies - hexdump(len=41): 00 07 64 65 66 61 75 6c 74
01 04 82 84 8b 96 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
assoc_wpa_ie - hexdump(len=26): dd 18 00 50 f2 01 01
00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00
00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:88:2b:9e:21
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:88:2b:9e:21
Setting authentication timeout: 10 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 267 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 267 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 243 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 339 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0d:88:2b:9e:21 ssid='default' wpa_ie_len=24
rsn_ie_len=0
   selected
Trying to associate with 00:0d:88:2b:9e:21
(SSID='default' freq=2422 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
Authentication with 00:0d:88:2b:9e:21 timed out.



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From cwevans  Wed Nov  3 06:22:35 2004
From: cwevans (Chris Evans)
Date: Wed, 3 Nov 2004 06:22:35 -0800
Subject: Firmware upload
In-Reply-To: <000801c4c190$0bfc44f0$8201a8c0@artline5stqgle>
References: <000801c4c190$0bfc44f0$8201a8c0@artline5stqgle>
Message-ID: <CEEC5860-2DA3-11D9-8030-000A95B1BFFA@acm.org>

Sure we can help, mind giving us the error messages?  What versions of 
the kernel and hostap you are using.  Did you compile them yourself, or 
are the packaged.  If packaged, where did you get the packages?
On Nov 3, 2004, at 2:29 AM, arttysta wrote:

> ??? How to upload firmware into card ?
> ?
> type o firmware
> ?? ak010104.hex -primary
> ?? rf010803.hex - secondary
> ?
> this firmwares are compatybile with my card
> but i can't upload them even with command
>  prism2_srec -g wlan0 ak010104.hex
>  or
> prism2_srec -r wlan0 rf010803.hex
>  ?
> Can any one help me with this thing ?
>
> ----------------------------------------------------------------------
>  Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
--
       -+--++---+++----++++-----+++++-----++++----+++---++--+-
      ___
  _.-|   |          |\__/,|   (`\      | Chris Evans
{   |   |          |o o  |__ _) )     |
  "-.|___|        _.( T   )  `  /      | cwevans at acm.org
   .--'-`-.     _((_ `^--' /_<  \      |
.+|______|__.-||__)`-'(((/  (((/      |  "Any technology distinguishable
                                       |  from magic, is not advanced
   Nika plays with a computer mouse    |  enough" -- Gregory Benford
       BY: Mike Rosulek                |
          http://www.mikero.com/misc/ascii/




From vsinha  Wed Nov  3 17:43:42 2004
From: vsinha (Vishal Sinha)
Date: Wed, 3 Nov 2004 17:43:42 -0800
Subject: Urgent: Looking for wireless tech support engineer
In-Reply-To: <20041103142444.51DFB2C777@mail.iocaine.com>
Message-ID: <APEHKHIBOIHDDPDNHKENKEFEKNAB.vsinha@foundrynet.com>

Technical Support Wireless

Day to day Responsibilities:

Provides support to customers, resellers and field personnel in resolving
company product related issues. Document sequence of events related to
resolving customer technical issues

Must Have Skills

The Customer Support Engineer will provide daily phone consultation with
clients as they call to report problems with their software and/or hardware;
document client calls in the client management database; ensure client
expectations are properly managed, and that issues and needs are resolved to
the client's satisfaction in a timely manner. The successful candidate will
work as a direct resource for external clients, as well as internal clients
to resolve technical problems, provide troubleshooting skills and research
for more difficult problems, escalate client problems that require a more
complicated solution, maintain call ownership, and see the problem through
to resolution. Additionally, they will test new releases for software
products before distribution to clients to ensure the product is sound, work
with third party vendors regarding client data that is transmitted to them,
research and resolve problems that may occur with sending and/or receiving
client data, troubleshoot client-reporting issues, contact vendors to clear
up the issues, and provide follow-up to clients when issues are resolved.
The Successful candidate understands all service offers and the benefits to
our clients, works as a direct resource to answer client inquiries, and must
have the ability to effectively communicate to both clients and internal
personnel while working under pressure and with time constraints. Finally,
the successful candidate will be involved in the creation and completion of
department and individual goals and fulfilling all services the team
promises to clients.

The ideal candidate will have experience with 802.11 wireless and encryption
protocols such as WEP, WPA, TKIP, and AES experience with authentication
protocols such as 802.1X, and Radius, and network management (NMS)
experience. The candidate should have experience in the L3 VPN's and
tunneling. A firm understanding of 802.11a/b/g radio technology and the
security aspects is strongly desired.

Education and Work Experience:

FNCNE and/or FNCNP is highly preferred. Candidates hired without this
certification will be required to complete the FNCNE certification program
within six (6) months of hire date.

Prefer BS or related discipline. Experience with STP, BGP, OSPF, RIP, MPLS,
IPX, AppleTalk.


Interested, send me an email @ vsinha at foundrynet.com




From jkmaline  Wed Nov  3 19:02:31 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:02:31 -0800
Subject: No AP with WPA found ,
	got lots of debug info to troubleshoot this
In-Reply-To: <20041103111638.50651.qmail@web51101.mail.yahoo.com>
References: <20041103111638.50651.qmail@web51101.mail.yahoo.com>
Message-ID: <20041104030230.GA7380@jm.kir.nu>

On Wed, Nov 03, 2004 at 12:16:38PM +0100, Kuckuck Kuckuck wrote:

> I have tried to use ndiswrapper yerterday and
> encountered the following problem.
> When starting wpa_supplicant it doesn't find my AP,
> but the AP is up and working, as I'm using also a
> windows laptop which is connected to the AP and is
> connected using WPA-PSK TKIP.

This looks more like a problem with the NDIS driver or ndiswrapper than
wpa_supplicant. ndiswrapper is reporting that the AP did not have WPA IE
in the Beacon frame. wpa_supplicant cannot really do much in such a
case. In other words, posting this to ndiswrapper mailing list with some
more details about the used wireless LAN card and NDIS driver could be
better way to get this resolved.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:12:33 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:12:33 -0800
Subject: SWSUPPORT write/read failed
In-Reply-To: <20041102185801.GA17523@ipdska.ipd.bth.se>
References: <20041102185801.GA17523@ipdska.ipd.bth.se>
Message-ID: <20041104031233.GB7380@jm.kir.nu>

On Tue, Nov 02, 2004 at 07:58:01PM +0100, Simon Kagstrom wrote:

> I'm trying to understand why the Sandisk Connectplus card doesn't work. One
> thing which I don't understand is why the write to SWSUPPORT0 isn't working. I
> get results as
> 
> SWSUPPORT0 write/read failed: 8AFF != 8A32

It is unclear whether the registers are mapped correctly since init
command fails and SWSUPPORT0 reigster does not work properly. Has the
patch for the multi-func card fixed to make sure that COR is set
correctly to get the card in I/O mode?

> should the SWSUPPORT0 write work if the card isn't configured properly before
> (especially the "Interrupt, but dev not OK" looks suspicious).

Depends on what part is not configured properly.. It is available quite
soon, but at least the registers have to match and the card may need
some setup (e.g., that COR mentioned above).

> Are there any parts of the prism3 support still missing by the way?

Should not be missing.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:20:06 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:20:06 -0800
Subject: problem in Wireless Extension
In-Reply-To: <20041102121951.64434.qmail@web54601.mail.yahoo.com>
References: <20041102121951.64434.qmail@web54601.mail.yahoo.com>
Message-ID: <20041104032006.GC7380@jm.kir.nu>

On Tue, Nov 02, 2004 at 04:19:51AM -0800, Yong Chu Eu (??????) wrote:

> i am using 3com Airconnect 3CRWE777A-E1 network card with firmware 1.5.6(i
> flashing it from 0.8.3 with hostap-utilities), i try hostap driver from
> version 0.1.3,0.2.0 to 0.2.5. same problem happend. i suspect maybe
> Wireless Extension on kernel 2.4.26 cannot support HOSTAP, i did not have
> any problem on my redhat 9.0 with kernel 2.4.20 and kernel 2.4.22. 

> On Tue, 2004-11-02 at 10:26, Yong Chu Eu (??????) wrote:
> > [root at localhost root]# iwconfig wlan0 txpower 150

Host AP driver does not support iwconfig txpower option.

> > Warning: Driver for device wlan0 has been compiled with version 16
> > of Wireless Extension, while this program is using version 15.
> > Some things may be broken...

This can be ignored in most cases.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:22:36 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:22:36 -0800
Subject: How to get certificate
In-Reply-To: <32653c97041101182978601c90@mail.gmail.com>
References: <32653c97041101182978601c90@mail.gmail.com>
Message-ID: <20041104032235.GD7380@jm.kir.nu>

On Tue, Nov 02, 2004 at 10:29:56AM +0800, YenJung Chang wrote:

> I am a newbie on wpa_supplicant and I am testing its features,
> however, I don't know how to get or setup a certificate in station
> side.
> Is there any document teaching this?
> or would someone like to tell me how to do?

There is nothing wpa_supplicant specific in certificate enrollment. This
process depends on what kind of CA configuration you are using, so it is
somewhat outside the scope of wpa_supplicant documentation. Anyway,
there are couple of howtos/tutorials on how to enroll certificates for
either wpa_supplicant or Xsupplicant. I don't have any URLs for these
handy, but google should be helpful here..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:30:42 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:30:42 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
	Atheros 802.11a/b/g card
In-Reply-To: <4185D9EF.7010602@cisco.com>
References: <4185D9EF.7010602@cisco.com>
Message-ID: <20041104033042.GE7380@jm.kir.nu>

On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote:

> I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip 
> (5212 I think it is called).  The card has a PCI id of vendor 0x168c, 
> device 0x0013.
> 
> wpa_supplicant fails when I try to use WPA-PSK.  I downloaded a trial copy 
> of driverloader and it works fine.

Which NDIS driver are you using?

> The debug from wpa_supplicant indicates that the AP scan returns 0 bytes. 
> No suitable AP is found.  I am not sure where the problem lies except that 
> it fails with both ndiswrapper and the madwifi drivers pulled from the 
> madwifi project's cvs last wednesday.

Can you get scan any results with 'iwlist wlan0 scan'? Can you use
ndiswrapper in plaintext mode with the same AP?

> What debugs should I obtain in order to solve this problem?  I ran 
> wpa_supplicant with the -dd command line option and saw that the sacn 
> failed.  (Sorry I lost the log I captured.  I will recreate it later and 
> post it as a followup to this message.)

That would be suitable log file for hostap (i.e., wpa_supplicant)
mailing list.

> I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried ndiswrapper 
> 0.11 but the perl script prints out a number of error messages so went back 
> to version 0.10).  The access point is a Cisco 1100.

Which firmware version is used in the AP? I haven't tested ndiswrapper
with Cisco APs, but wpa_supplicant and Atheros-based cards have worked
nicely with Cisco APs.


On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote:

> Does anyone else have this up and running with an Atheros-chip ?

Yes, worked fine with ndiswrapper the last time I tested (a long time
ago, though).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:36:49 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:36:49 -0800
Subject: Sandisk connectplus
In-Reply-To: <20041029144556.GA9035@ipdska.ipd.bth.se>
References: <20041029144556.GA9035@ipdska.ipd.bth.se>
Message-ID: <20041104033649.GF7380@jm.kir.nu>

On Fri, Oct 29, 2004 at 04:45:56PM +0200, Simon Kagstrom wrote:

>    Also, to activate the wireless function, you should write two values (0xc5
>    and 0x4b) to the io space base + 0x40, which is HFA384X_RXFID_OFF. Does
>    that make sense?

Partly.. Those values look like COR values that would be used to enable
the card by setting it to I/O mode. In other words, this is to PC Card
COR register, none of the Prism3 specific registers like RXFID.

> 1. There have been some concerns [1] that the linux PCMCIA support does not
>    cater multifunctional cards. Is this so? Or maybe the hostap driver?

I have never used multi-func PC Card, but there certainly seems to be
some support for it since even your configuration was binding one of the
functions ("to 1" or "to 0").. It's unclear to me how much of the
multi-func initialization should be done in core pcmcia code and how
much in the driver, though.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:44:08 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:44:08 -0800
Subject: Turning off some or all kernel log messages
In-Reply-To: <200410311320.45067.barr.156@osu.edu>
References: <200410311320.45067.barr.156@osu.edu>
Message-ID: <20041104034408.GG7380@jm.kir.nu>

On Sun, Oct 31, 2004 at 01:20:44PM -0500, Andrew Barr wrote:

> wifi0: STA 00:0d:88:51:61:3a TX rate lowered to 20
> 
> Sometimes those messages are all that's output by dmesg. Is there any way to 
> quiet down the verbosity of HostAP logging?i

Sure.. You have the source code.. ;-)

It should be ok to just comment out the PDEBUG() and printk() calls that
you do not consider useful. This particular one could, however, be
removed from the default build anyway..

> I looked for both a module 
> parameter and a Makefile option, but I couldn't find any way to change the 
> verbosity of logging.

This is build time only.. You can remove PDEBUG() messages by defining
PRISM2_NO_DEBUG, e.g, in hostap_config.h. This may also still work from
the command line:

make EXTRA_CFLAGS="-DPRISM2_NO_DEBUG"

-- 
Jouni Malinen                                            PGP id EFC895FA



From yenjung  Wed Nov  3 19:47:21 2004
From: yenjung (YenJung Chang)
Date: Thu, 4 Nov 2004 11:47:21 +0800
Subject: How to get certificate
In-Reply-To: <20041104032235.GD7380@jm.kir.nu>
References: <32653c97041101182978601c90@mail.gmail.com>
	<20041104032235.GD7380@jm.kir.nu>
Message-ID: <32653c970411031947367a83d7@mail.gmail.com>

Thanks for your reply.
Now I can get the certificate from CA server, and convert it to PEM format.
Thanks all.

Regards,
yj.

On Wed, 3 Nov 2004 19:22:36 -0800, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Tue, Nov 02, 2004 at 10:29:56AM +0800, YenJung Chang wrote:
> 
> > I am a newbie on wpa_supplicant and I am testing its features,
> > however, I don't know how to get or setup a certificate in station
> > side.
> > Is there any document teaching this?
> > or would someone like to tell me how to do?
> 
> There is nothing wpa_supplicant specific in certificate enrollment. This
> process depends on what kind of CA configuration you are using, so it is
> somewhat outside the scope of wpa_supplicant documentation. Anyway,
> there are couple of howtos/tutorials on how to enroll certificates for
> either wpa_supplicant or Xsupplicant. I don't have any URLs for these
> handy, but google should be helpful here..
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jkmaline  Wed Nov  3 19:46:18 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:46:18 -0800
Subject: Unknown symbol
In-Reply-To: <20041030161027.48048.qmail@web14103.mail.yahoo.com>
References: <20041030161027.48048.qmail@web14103.mail.yahoo.com>
Message-ID: <20041104034618.GH7380@jm.kir.nu>

On Sat, Oct 30, 2004 at 09:10:27AM -0700, Michael Cox wrote:

> When trying to load hostap I see the following from
> dmesg:
> 
> hostap_cs: Unknown symbol hostap_netif_stop_queues
> hostap_cs: Unknown symbol hostap_netif_wake_queues

Which version of the driver are you using? Could you please try with the
current stable release (0.2.5)? Those functions have been removed long
time ago.. If you have modules (mainly, hostap.ko in this case) from
older versions, please make sure that they are removed when testing new
version of the driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov  3 19:57:03 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 19:57:03 -0800
Subject: strange problems after upgrading to kernel 2.6.10rc1
In-Reply-To: <20041029170112.GA14869@bougret.hpl.hp.com>
References: <20041029170112.GA14869@bougret.hpl.hp.com>
Message-ID: <20041104035703.GI7380@jm.kir.nu>

On Fri, Oct 29, 2004 at 10:01:12AM -0700, Jean Tourrilhes wrote:
> Jouni wrote :
> > With the new development model for Linux 2.6, this is likely to become
> > more frequent.. Linux 2.6.10-rc1 seems to have changed PCI calls for
> > driver registration and power saving state in a way which is not
> > backwards compatible.

> 	I remember some driver authors grumbling about all the changes
> to the Wireless Extension API and all the pain it was causing in his
> driver. I'm glad that this time, I'm not the culprit.

Most, if not all, changes in wireless extensions were backwards
compatible at least in the source level. From my viewpoint, it's quite
a bit different to start removing function arguments..

> 	Some kernel developpers seem to have a position that backward
> compatibility should be avoided at all cost and breaking it is good
> fun. One of the "benefit" is that it punishes driver living outside
> the kernel, and therefore encourage people to maintain their driver in
> the kernel. So, I guess we can expect more of it.

Well.. I can understand the goal of having a clean interface to internal
kernel functionality. Yes, it will mean things get broken every now and
then, but then again, one can go the route of taking a distro kernel and
hope for the best that the distro in question includes all the needed
drivers.

> 	Wich brin nicely to the topic of inclusion of HostAP in the
> kernel...

I didn't get much (well, none) comments on this when I submitted the
driver for wireless-2.6 tree. I could try to update wireless-2.6 version
to match with my current work version and then ask whether it could be
merged into linux-2.6 tree..

-- 
Jouni Malinen                                            PGP id EFC895FA



From shortestpathfirst  Wed Nov  3 20:38:51 2004
From: shortestpathfirst (Michael Cox)
Date: Wed, 3 Nov 2004 20:38:51 -0800 (PST)
Subject: Unknown symbol
In-Reply-To: <20041104034618.GH7380@jm.kir.nu>
Message-ID: <20041104043851.5268.qmail@web14106.mail.yahoo.com>

I'm using driver 0.2.5 (tried the CVS snapshot, too,
with no difference). This is a brand new laptop/brand
new install, so nothing old was on there.

Thanks,
Michael

--- Jouni Malinen <jkmaline at cc.hut.fi> wrote:

> On Sat, Oct 30, 2004 at 09:10:27AM -0700, Michael
> Cox wrote:
> 
> > When trying to load hostap I see the following
> from
> > dmesg:
> > 
> > hostap_cs: Unknown symbol hostap_netif_stop_queues
> > hostap_cs: Unknown symbol hostap_netif_wake_queues
> 
> Which version of the driver are you using? Could you
> please try with the
> current stable release (0.2.5)? Those functions have
> been removed long
> time ago.. If you have modules (mainly, hostap.ko in
> this case) from
> older versions, please make sure that they are
> removed when testing new
> version of the driver.
> 
> -- 
> Jouni Malinen                                       
>     PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From jkmaline  Wed Nov  3 21:42:19 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 21:42:19 -0800
Subject: Unknown symbol
In-Reply-To: <20041104043851.5268.qmail@web14106.mail.yahoo.com>
References: <20041104034618.GH7380@jm.kir.nu>
	<20041104043851.5268.qmail@web14106.mail.yahoo.com>
Message-ID: <20041104054219.GJ7380@jm.kir.nu>

On Wed, Nov 03, 2004 at 08:38:51PM -0800, Michael Cox wrote:

> I'm using driver 0.2.5 (tried the CVS snapshot, too,
> with no difference). This is a brand new laptop/brand
> new install, so nothing old was on there.

Please send output from following commands:

uname -a
find /lib/modules -name 'hostap*'

The two symbols you mentioned are not included in the current driver
versions. In other words, it looks like there is an old version of the
kernel module somewhere.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yenjung  Wed Nov  3 21:48:05 2004
From: yenjung (YenJung Chang)
Date: Thu, 4 Nov 2004 13:48:05 +0800
Subject: terminated at sending EAPOL-key 2/4 on PEAP.
Message-ID: <32653c970411032148424c175c@mail.gmail.com>

Hi, list

I can't connect to my RADIUS server with EAP-PEAP, my setting,
environment and debug message are showed below..
However, the WPA-PSK is workable...

<environment>
=============================
RADIUS server: windows 2000 server
AP: Cisco 1200 a+b

STATION: 
- Kernel: 2.4.25
- Wireless card: Atheros ar5212
- Driver: Madwifi
- wpa_supplicant version: 0.2.5
=============================

<setting>
==============================
# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
# (e.g., Radiator)
network={
	ssid="1200b"
	key_mgmt=WPA-EAP
	eap=PEAP
	identity="spencer"
	password="Ss=1234"
	ca_cert="/etc/ssl/certs/netgearca.pem"
	phase1="peaplabel=1"
	phase2="auth=MSCHAPV2"
	priority=2
}

command:
wpa_supplicant -d -c/etc/wpa_supplicant.conf -iath0

==========================================

<debug message>
===========================================
l2_packet_receive - recv: Network is down
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 2
   id=0 ssid='1200b'
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_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
Starting AP scan (broadcast SSID)
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 2716 bytes of scan results (13 BSSes)
Scan results: 13
Selecting BSS from priority group 2
0: 00:09:5b:f7:14:8c ssid='*spencer*' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:0f:b5:10:a5:38 ssid='davidv3' wpa_ie_len=26 rsn_ie_len=0
   skip - SSID mismatch
2: 00:0c:85:71:6e:a8 ssid='1200b' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='1200b' freq=2437 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=18
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
RX EAPOL from 00:0c:85:71:6e:a8
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=7):
     73 70 65 6e 63 65 72                              spencer         
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:0c:85:71:6e:a8
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=7):
     73 70 65 6e 63 65 72                              spencer         
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:0c:85:71:6e:a8
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=3
EAP: EAP entering state GET_METHOD
EAP-PEAP: Force new label for key derivation
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=6) - Flags 0x20
EAP-PEAP: Start (server ver=0, own ver=1)
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 left to be sent out (of total 100 bytes)
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:0c:85:71:6e:a8
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=4
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=1396) - Flags 0xc0
EAP-PEAP: TLS Message Length: 4723
SSL: Need 3337 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
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=5
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=1396) - Flags 0x40
SSL: Need 1947 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
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=6
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=1396) - Flags 0x40
SSL: Need 557 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
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=7
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=563) - Flags 0x00
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server hello A
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
buf='/DC=com/DC=GUI/CN=Netgear CA'
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
buf='/CN=dni-9j5p6pp7hnj.GUI.com'
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server certificate A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server certificate request A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server done A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client certificate A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client key exchange A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write change cipher spec A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write finished A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 flush data
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read finished A
SSL: SSL_connect - want more data
SSL: 194 bytes left to be sent out (of total 194 bytes)
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
IEEE 802.1X RX: version=1 type=0 length=563
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
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=8
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=53) - Flags 0x80
EAP-PEAP: TLS Message Length: 43
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read finished A
SSL: (where=0x20 ret=0x1)
SSL: (where=0x1002 ret=0x1)
SSL: No data to be sent out
EAP-PEAP: TLS done, proceed to Phase 2
EAP-PEAP: using label 'client PEAP encryption' in key derivation
EAP-PEAP: Derived key - hexdump(len=64): f8 50 44 cc e4 a5 95 7e 34 15
09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af ae
9f fc e0 35 29 c5 e5 ee b2 46 45 38 f1 e8 94 45 90 5b aa 6f 8f fb 1d
b3 5f 6a a8 1d 3e 63 4a
SSL: Building ACK
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 57, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
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=9
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=28) - Flags 0x00
EAP-PEAP: received 22 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=1): 01
EAP-PEAP: received Phase 2: code=1 identifier=9 length=5
EAP-PEAP: Phase 2 Request: type=1
EAP: using real identity - hexdump_ascii(len=7):
     73 70 65 6e 63 65 72                              spencer         
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=12): 02 09 00 0c 01 73
70 65 6e 63 65 72
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:0c:85:71:6e:a8
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=10
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=64) - Flags 0x00
EAP-PEAP: received 58 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=37): 1a 01 0a 00 24 10
32 1d da 61 e2 2b a7 4e 2c f4 8a 98 03 d8 d2 9e 44 4e 49 2d 39 4a 35
50 36 50 50 37 48 4e 4a
EAP-PEAP: received Phase 2: code=1 identifier=10 length=41
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received challenge
EAP-MSCHAPV2: Authentication Servername - hexdump_ascii(len=15):
     44 4e 49 2d 39 4a 35 50 36 50 50 37 48 4e 4a      DNI-9J5P6PP7HNJ 
EAP-MSCHAPV2: Generating Challenge Response
EAP-MSCHAPV2: auth_challenge - hexdump(len=16): 32 1d da 61 e2 2b a7
4e 2c f4 8a 98 03 d8 d2 9e
EAP-MSCHAPV2: peer_challenge - hexdump(len=16): f1 c8 54 a8 1a f7 9b
7a c1 8c 31 7a e0 c4 62 5d
EAP-MSCHAPV2: username - hexdump_ascii(len=7):
     73 70 65 6e 63 65 72                              spencer         
EAP-MSCHAPV2: password - hexdump_ascii(len=7):
     53 73 3d 31 32 33 34                              Ss=1234         
EAP-MSCHAPV2: response - hexdump(len=24): a0 7d d4 88 1e 96 a6 b1 4c
70 35 bf 66 94 c9 1e 5c 58 f6 45 e8 38 af d1
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=66): 02 0a 00 42 1a 02
0a 00 3d 31 f1 c8 54 a8 1a f7 9b 7a c1 8c 31 7a e0 c4 62 5d 00 00 00
00 00 00 00 00 a0 7d d4 88 1e 96 a6 b1 4c 70 35 bf 66 94 c9 1e 5c 58
f6 45 e8 38 af d1 00 73 70 65 6e 63 65 72
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 68, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
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=11
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=74) - Flags 0x00
EAP-PEAP: received 68 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=47): 1a 03 0a 00 2e 53
3d 43 37 45 38 35 42 38 46 38 30 36 34 31 46 36 36 45 32 46 36 34 37
37 45 41 36 32 33 41 46 38 30 37 30 46 46 44 38 41 39
EAP-PEAP: received Phase 2: code=1 identifier=11 length=51
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received success
EAP-MSCHAPV2: Success message - hexdump(len=0):
EAP-MSCHAPV2: Authentication succeeded
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 0b 00 06 1a 03
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 78, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
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=12
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=38) - Flags 0x00
EAP-PEAP: received 32 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=11): 01 0c 00 0b 21 80
03 00 02 00 01
EAP-PEAP: received Phase 2: code=1 identifier=12 length=11
EAP-PEAP: Phase 2 Request: type=33
EAP-PEAP: Received TLVs - hexdump(len=6): 80 03 00 02 00 01
EAP-PEAP: Result TLV - hexdump(len=2): 00 01
EAP-PEAP: TLV Result - Success - EAP-PEAP/Phase2 Completed
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): 02 0c 00 0b 21 80
03 00 02 00 01
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:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: Workaround for unexpected identifier field in EAP Success:
reqId=13 lastId=12 (these are supposed to be same)
EAP: EAP entering state SUCCESS
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
WPA: Renewed SNonce - hexdump(len=32): b7 a5 c6 89 79 94 04 e0 88 f7
48 48 ae a6 84 f7 48 e7 6b e2 0c e8 19 87 01 5f 20 dc 0b e7 d8 10
WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
ce 48 4a af
WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
WPA: PTK - hexdump(len=64): ca cd 66 64 b3 fc 22 c2 d1 1e 38 5d 11 0b
90 47 a9 a7 75 b2 98 b4 c8 7b e4 b3 09 fd f8 b3 10 b8 c0 ec 68 34 6b
c0 a2 d9 4e 3e f2 f5 39 ef ee 82 62 27 51 be 9a 09 6a 68 b1 63 a1 c3
5d 96 ea f6
WPA: EAPOL-Key MIC - hexdump(len=16): 05 d0 a1 6c 24 5a 40 a2 15 b2 b4
24 97 ea 41 31
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0c:85:71:6e:a8
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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
ce 48 4a af
WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
WPA: PTK - hexdump(len=64): 04 b6 7f 59 b9 33 17 78 b9 10 86 35 18 8c
ab 32 37 e7 48 17 20 80 22 f8 32 a0 7a cc 7a 87 2f ca b8 0b 2a 24 a1
e6 6e 73 9b 49 45 1b d0 68 31 93 9f 63 d6 73 db fb 04 12 eb c8 ff 77
03 40 7d 62
WPA: EAPOL-Key MIC - hexdump(len=16): 91 1c 3f e5 fb 00 ed ce fe b4 8e
f5 f6 ec e3 fb
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0c:85:71:6e:a8
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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
ce 48 4a af
WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
WPA: PTK - hexdump(len=64): de 9b 98 fd 5b 32 ff 12 4d 8d 4a 94 89 7f
d8 a0 6f b4 f6 45 55 0a 94 95 83 39 52 44 62 16 b4 b6 ce 4d c7 40 ad
c2 a3 40 5f a5 11 45 4e a0 8c 99 d5 ed e1 b3 b5 45 e2 27 61 73 14 12
7d 89 3e 83
WPA: EAPOL-Key MIC - hexdump(len=16): b6 3a 56 f5 cb 31 9b 66 c6 43 d4
ae 25 64 1b 12
WPA: Sending EAPOL-Key 2/4
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
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
==================================================

Please tell me what mistake I made.

If there is more information I should provide, please tell me.
Any advice is appreciated.

Thanks,
yj.



From yenjung  Wed Nov  3 21:54:53 2004
From: yenjung (YenJung Chang)
Date: Thu, 4 Nov 2004 13:54:53 +0800
Subject: terminated at sending EAPOL-key 2/4 on PEAP.
In-Reply-To: <32653c970411032148424c175c@mail.gmail.com>
References: <32653c970411032148424c175c@mail.gmail.com>
Message-ID: <32653c97041103215416b9e6ac@mail.gmail.com>

I missed some settings in wpa_supplicant.conf.

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

Thanks,
yj.

On Thu, 4 Nov 2004 13:48:05 +0800, YenJung Chang <yenjung at gmail.com> wrote:
> Hi, list
> 
> I can't connect to my RADIUS server with EAP-PEAP, my setting,
> environment and debug message are showed below..
> However, the WPA-PSK is workable...
> 
> <environment>
> =============================
> RADIUS server: windows 2000 server
> AP: Cisco 1200 a+b
> 
> STATION:
> - Kernel: 2.4.25
> - Wireless card: Atheros ar5212
> - Driver: Madwifi
> - wpa_supplicant version: 0.2.5
> =============================
> 
> <setting>
> ==============================
> # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
> # (e.g., Radiator)
> network={
>         ssid="1200b"
>         key_mgmt=WPA-EAP
>         eap=PEAP
>         identity="spencer"
>         password="Ss=1234"
>         ca_cert="/etc/ssl/certs/netgearca.pem"
>         phase1="peaplabel=1"
>         phase2="auth=MSCHAPV2"
>         priority=2
> }
> 
> command:
> wpa_supplicant -d -c/etc/wpa_supplicant.conf -iath0
> 
> ==========================================
> 
> <debug message>
> ===========================================
> l2_packet_receive - recv: Network is down
> 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 2
>    id=0 ssid='1200b'
> 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_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
> Starting AP scan (broadcast SSID)
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 2716 bytes of scan results (13 BSSes)
> Scan results: 13
> Selecting BSS from priority group 2
> 0: 00:09:5b:f7:14:8c ssid='*spencer*' wpa_ie_len=24 rsn_ie_len=0
>    skip - SSID mismatch
> 1: 00:0f:b5:10:a5:38 ssid='davidv3' wpa_ie_len=26 rsn_ie_len=0
>    skip - SSID mismatch
> 2: 00:0c:85:71:6e:a8 ssid='1200b' wpa_ie_len=24 rsn_ie_len=0
>    selected
> Trying to associate with 00:0c:85:71:6e:a8 (SSID='1200b' freq=2437 MHz)
> Cancelling scan request
> WPA: using IEEE 802.11i/D3.0
> 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
> 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
> 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=18
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:0c:85:71:6e:a8
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
> 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
> 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
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=7):
>      73 70 65 6e 63 65 72                              spencer
> 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:0c:85:71:6e:a8
> 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=7):
>      73 70 65 6e 63 65 72                              spencer
> 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:0c:85:71:6e:a8
> 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=3
> EAP: EAP entering state GET_METHOD
> EAP-PEAP: Force new label for key derivation
> EAP-PEAP: Phase2 type: MSCHAPV2
> SSL: Trusted root certificate(s) loaded
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=6) - Flags 0x20
> EAP-PEAP: Start (server ver=0, own ver=1)
> 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 left to be sent out (of total 100 bytes)
> 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:0c:85:71:6e:a8
> 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=4
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=1396) - Flags 0xc0
> EAP-PEAP: TLS Message Length: 4723
> SSL: Need 3337 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=5
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=1396) - Flags 0x40
> SSL: Need 1947 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=6
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=1396) - Flags 0x40
> SSL: Need 557 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=7
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=563) - Flags 0x00
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server hello A
> SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
> buf='/DC=com/DC=GUI/CN=Netgear CA'
> SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
> buf='/CN=dni-9j5p6pp7hnj.GUI.com'
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server certificate A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server certificate request A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server done A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write client certificate A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write client key exchange A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write change cipher spec A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write finished A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 flush data
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read finished A
> SSL: SSL_connect - want more data
> SSL: 194 bytes left to be sent out (of total 194 bytes)
> 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
> IEEE 802.1X RX: version=1 type=0 length=563
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=8
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=53) - Flags 0x80
> EAP-PEAP: TLS Message Length: 43
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read finished A
> SSL: (where=0x20 ret=0x1)
> SSL: (where=0x1002 ret=0x1)
> SSL: No data to be sent out
> EAP-PEAP: TLS done, proceed to Phase 2
> EAP-PEAP: using label 'client PEAP encryption' in key derivation
> EAP-PEAP: Derived key - hexdump(len=64): f8 50 44 cc e4 a5 95 7e 34 15
> 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af ae
> 9f fc e0 35 29 c5 e5 ee b2 46 45 38 f1 e8 94 45 90 5b aa 6f 8f fb 1d
> b3 5f 6a a8 1d 3e 63 4a
> SSL: Building ACK
> 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 57, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=9
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=28) - Flags 0x00
> EAP-PEAP: received 22 bytes encrypted data for Phase 2
> EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=1): 01
> EAP-PEAP: received Phase 2: code=1 identifier=9 length=5
> EAP-PEAP: Phase 2 Request: type=1
> EAP: using real identity - hexdump_ascii(len=7):
>      73 70 65 6e 63 65 72                              spencer
> EAP-PEAP: Encrypting Phase 2 data - hexdump(len=12): 02 09 00 0c 01 73
> 70 65 6e 63 65 72
> 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:0c:85:71:6e:a8
> 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=10
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=64) - Flags 0x00
> EAP-PEAP: received 58 bytes encrypted data for Phase 2
> EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=37): 1a 01 0a 00 24 10
> 32 1d da 61 e2 2b a7 4e 2c f4 8a 98 03 d8 d2 9e 44 4e 49 2d 39 4a 35
> 50 36 50 50 37 48 4e 4a
> EAP-PEAP: received Phase 2: code=1 identifier=10 length=41
> EAP-PEAP: Phase 2 Request: type=26
> EAP-PEAP: Phase 2 EAP packet
> EAP-MSCHAPV2: Received challenge
> EAP-MSCHAPV2: Authentication Servername - hexdump_ascii(len=15):
>      44 4e 49 2d 39 4a 35 50 36 50 50 37 48 4e 4a      DNI-9J5P6PP7HNJ
> EAP-MSCHAPV2: Generating Challenge Response
> EAP-MSCHAPV2: auth_challenge - hexdump(len=16): 32 1d da 61 e2 2b a7
> 4e 2c f4 8a 98 03 d8 d2 9e
> EAP-MSCHAPV2: peer_challenge - hexdump(len=16): f1 c8 54 a8 1a f7 9b
> 7a c1 8c 31 7a e0 c4 62 5d
> EAP-MSCHAPV2: username - hexdump_ascii(len=7):
>      73 70 65 6e 63 65 72                              spencer
> EAP-MSCHAPV2: password - hexdump_ascii(len=7):
>      53 73 3d 31 32 33 34                              Ss=1234
> EAP-MSCHAPV2: response - hexdump(len=24): a0 7d d4 88 1e 96 a6 b1 4c
> 70 35 bf 66 94 c9 1e 5c 58 f6 45 e8 38 af d1
> EAP-PEAP: Encrypting Phase 2 data - hexdump(len=66): 02 0a 00 42 1a 02
> 0a 00 3d 31 f1 c8 54 a8 1a f7 9b 7a c1 8c 31 7a e0 c4 62 5d 00 00 00
> 00 00 00 00 00 a0 7d d4 88 1e 96 a6 b1 4c 70 35 bf 66 94 c9 1e 5c 58
> f6 45 e8 38 af d1 00 73 70 65 6e 63 65 72
> 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 68, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=11
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=74) - Flags 0x00
> EAP-PEAP: received 68 bytes encrypted data for Phase 2
> EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=47): 1a 03 0a 00 2e 53
> 3d 43 37 45 38 35 42 38 46 38 30 36 34 31 46 36 36 45 32 46 36 34 37
> 37 45 41 36 32 33 41 46 38 30 37 30 46 46 44 38 41 39
> EAP-PEAP: received Phase 2: code=1 identifier=11 length=51
> EAP-PEAP: Phase 2 Request: type=26
> EAP-PEAP: Phase 2 EAP packet
> EAP-MSCHAPV2: Received success
> EAP-MSCHAPV2: Success message - hexdump(len=0):
> EAP-MSCHAPV2: Authentication succeeded
> EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 0b 00 06 1a 03
> 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 78, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=12
> EAP: EAP entering state METHOD
> EAP-PEAP: Received packet(len=38) - Flags 0x00
> EAP-PEAP: received 32 bytes encrypted data for Phase 2
> EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=11): 01 0c 00 0b 21 80
> 03 00 02 00 01
> EAP-PEAP: received Phase 2: code=1 identifier=12 length=11
> EAP-PEAP: Phase 2 Request: type=33
> EAP-PEAP: Received TLVs - hexdump(len=6): 80 03 00 02 00 01
> EAP-PEAP: Result TLV - hexdump(len=2): 00 01
> EAP-PEAP: TLV Result - Success - EAP-PEAP/Phase2 Completed
> EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): 02 0c 00 0b 21 80
> 03 00 02 00 01
> 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:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Success
> EAP: Workaround for unexpected identifier field in EAP Success:
> reqId=13 lastId=12 (these are supposed to be same)
> EAP: EAP entering state SUCCESS
> EAPOL: SUPP_BE entering state RECEIVE
> EAPOL: SUPP_BE entering state SUCCESS
> EAPOL: SUPP_BE entering state IDLE
> WPA: EAPOL frame too short, len 46, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> 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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
> WPA: Renewed SNonce - hexdump(len=32): b7 a5 c6 89 79 94 04 e0 88 f7
> 48 48 ae a6 84 f7 48 e7 6b e2 0c e8 19 87 01 5f 20 dc 0b e7 d8 10
> WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
> a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
> ce 48 4a af
> WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
> ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
> WPA: PTK - hexdump(len=64): ca cd 66 64 b3 fc 22 c2 d1 1e 38 5d 11 0b
> 90 47 a9 a7 75 b2 98 b4 c8 7b e4 b3 09 fd f8 b3 10 b8 c0 ec 68 34 6b
> c0 a2 d9 4e 3e f2 f5 39 ef ee 82 62 27 51 be 9a 09 6a 68 b1 63 a1 c3
> 5d 96 ea f6
> WPA: EAPOL-Key MIC - hexdump(len=16): 05 d0 a1 6c 24 5a 40 a2 15 b2 b4
> 24 97 ea 41 31
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:0c:85:71:6e:a8
> 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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
> WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
> a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
> ce 48 4a af
> WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
> ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
> WPA: PTK - hexdump(len=64): 04 b6 7f 59 b9 33 17 78 b9 10 86 35 18 8c
> ab 32 37 e7 48 17 20 80 22 f8 32 a0 7a cc 7a 87 2f ca b8 0b 2a 24 a1
> e6 6e 73 9b 49 45 1b d0 68 31 93 9f 63 d6 73 db fb 04 12 eb c8 ff 77
> 03 40 7d 62
> WPA: EAPOL-Key MIC - hexdump(len=16): 91 1c 3f e5 fb 00 ed ce fe b4 8e
> f5 f6 ec e3 fb
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:0c:85:71:6e:a8
> 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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
> WPA: PMK from EAPOL state machines - hexdump(len=32): f8 50 44 cc e4
> a5 95 7e 34 15 09 03 06 97 ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1
> ce 48 4a af
> WPA: PMK - hexdump(len=32): f8 50 44 cc e4 a5 95 7e 34 15 09 03 06 97
> ea 99 23 8c e0 b9 bb 34 01 37 93 94 bb d1 ce 48 4a af
> WPA: PTK - hexdump(len=64): de 9b 98 fd 5b 32 ff 12 4d 8d 4a 94 89 7f
> d8 a0 6f b4 f6 45 55 0a 94 95 83 39 52 44 62 16 b4 b6 ce 4d c7 40 ad
> c2 a3 40 5f a5 11 45 4e a0 8c 99 d5 ed e1 b3 b5 45 e2 27 61 73 14 12
> 7d 89 3e 83
> WPA: EAPOL-Key MIC - hexdump(len=16): b6 3a 56 f5 cb 31 9b 66 c6 43 d4
> ae 25 64 1b 12
> WPA: Sending EAPOL-Key 2/4
> 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
> 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
> ==================================================
> 
> Please tell me what mistake I made.
> 
> If there is more information I should provide, please tell me.
> Any advice is appreciated.
> 
> Thanks,
> yj.
>



From jkmaline  Wed Nov  3 21:54:14 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 3 Nov 2004 21:54:14 -0800
Subject: terminated at sending EAPOL-key 2/4 on PEAP.
In-Reply-To: <32653c970411032148424c175c@mail.gmail.com>
References: <32653c970411032148424c175c@mail.gmail.com>
Message-ID: <20041104055414.GK7380@jm.kir.nu>

On Thu, Nov 04, 2004 at 01:48:05PM +0800, YenJung Chang wrote:

> I can't connect to my RADIUS server with EAP-PEAP, my setting,
> environment and debug message are showed below..
> However, the WPA-PSK is workable...

> # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
> # (e.g., Radiator)
> network={

> 	phase1="peaplabel=1"

Why did you select this example? The RADIUS server is using PEAPv0 and
the wpa_supplicant configuration here is set to use v1 PEAP label in
session key generation. This will not interoperate. Please re-test after
removing that phase1 configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yenjung  Wed Nov  3 22:05:00 2004
From: yenjung (YenJung Chang)
Date: Thu, 4 Nov 2004 14:05:00 +0800
Subject: terminated at sending EAPOL-key 2/4 on PEAP.
In-Reply-To: <20041104055414.GK7380@jm.kir.nu>
References: <32653c970411032148424c175c@mail.gmail.com>
	<20041104055414.GK7380@jm.kir.nu>
Message-ID: <32653c97041103220523f0925c@mail.gmail.com>

Hi, Jouni,

Thanks for your reply.
I tried it with PEAPv0, and it is workable now, Thanks again. :)

Regards,
yj.


On Wed, 3 Nov 2004 21:54:14 -0800, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Thu, Nov 04, 2004 at 01:48:05PM +0800, YenJung Chang wrote:
> 
> > I can't connect to my RADIUS server with EAP-PEAP, my setting,
> > environment and debug message are showed below..
> > However, the WPA-PSK is workable...
> 
> > # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
> > # (e.g., Radiator)
> > network={
> 
> >       phase1="peaplabel=1"
> 
> Why did you select this example? The RADIUS server is using PEAPv0 and
> the wpa_supplicant configuration here is set to use v1 PEAP label in
> session key generation. This will not interoperate. Please re-test after
> removing that phase1 configuration.
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From david.mattes  Thu Nov  4 08:30:51 2004
From: david.mattes (David Mattes)
Date: Thu, 04 Nov 2004 08:30:51 -0800
Subject: Smartcards and wpa_supplicant
In-Reply-To: <4173D26D.5080300@et.bocholt.fh-ge.de>
References: <416BD7E9.7040403@et.bocholt.fh-ge.de>	<20041013040555.GA21644@jm.kir.nu>
	<4173D26D.5080300@et.bocholt.fh-ge.de>
Message-ID: <418A593B.9020806@boeing.com>

Gordon,

This looks like great work!  What version of wpa_supplicant did you 
patch against?

Thanks,
David




From david.mattes  Thu Nov  4 08:50:46 2004
From: david.mattes (David Mattes)
Date: Thu, 04 Nov 2004 08:50:46 -0800
Subject: Smartcards and wpa_supplicant
In-Reply-To: <418A593B.9020806@boeing.com>
References: <416BD7E9.7040403@et.bocholt.fh-ge.de>	<20041013040555.GA21644@j	m.kir.nu><4173D26D.5080300@et.bocholt.fh-ge.de>
	<418A593B.9020806@boeing.com>
Message-ID: <418A5DE6.70708@boeing.com>

Never mind, it's patched against the latest development release.  Sorry 
for the noise!

David Mattes wrote:

> Gordon,
>
> This looks like great work!  What version of wpa_supplicant did you 
> patch against?
>
> Thanks,
> David





From jt  Thu Nov  4 09:20:55 2004
From: jt (Jean Tourrilhes)
Date: Thu, 4 Nov 2004 09:20:55 -0800
Subject: strange problems after upgrading to kernel 2.6.10rc1
In-Reply-To: <20041104035703.GI7380@jm.kir.nu>
References: <20041029170112.GA14869@bougret.hpl.hp.com>
	<20041104035703.GI7380@jm.kir.nu>
Message-ID: <20041104172055.GA27853@bougret.hpl.hp.com>

On Wed, Nov 03, 2004 at 07:57:03PM -0800, Jouni Malinen wrote:
> 
> Most, if not all, changes in wireless extensions were backwards
> compatible at least in the source level. From my viewpoint, it's quite
> a bit different to start removing function arguments..

	Precisely.

> > 	Some kernel developpers seem to have a position that backward
> > compatibility should be avoided at all cost and breaking it is good
> > fun. One of the "benefit" is that it punishes driver living outside
> > the kernel, and therefore encourage people to maintain their driver in
> > the kernel. So, I guess we can expect more of it.
> 
> Well.. I can understand the goal of having a clean interface to internal
> kernel functionality. Yes, it will mean things get broken every now and
> then, but then again, one can go the route of taking a distro kernel and
> hope for the best that the distro in question includes all the needed
> drivers.

	I'm currently playing with a embedded device that has a
heavily patched 2.4.19 kernel. No way I'm going to forward port thir
patch to 2.6.X. I did appreciate that HostAP compiled and worked with
minimal fuss (once I upgraded the WE).
	So, there are people who appreciate your effort of keeping
your driver compatible with multiple kernel version, even if some
kernel developper thing this is bad.

> > 	Wich brin nicely to the topic of inclusion of HostAP in the
> > kernel...
> 
> I didn't get much (well, none) comments on this when I submitted the
> driver for wireless-2.6 tree. I could try to update wireless-2.6 version
> to match with my current work version and then ask whether it could be
> merged into linux-2.6 tree..

	The fact is that nobody is using the wireless-2.6 tree. I
don't, and I don't know anybody who does. It seems to me that Jeff's
effort to coerce wireless effort toward his goals did only get minimal
traction. Maybe it's time to get HostAP in -mm.
	Only my personal opinion, of course.

> Jouni Malinen

	Jean



From barr.156  Thu Nov  4 15:45:53 2004
From: barr.156 (Andrew Barr)
Date: Thu, 4 Nov 2004 18:45:53 -0500
Subject: Power Save Protocol
Message-ID: <200411041845.53204.barr.156@osu.edu>

The Intel PRO/Wireless 2100 supports something called the Power Save Protcol:

http://ipw2100.sourceforge.net/README.ipw2100 -- look for the section "Power 
Management"

The document notes that the AP must support this protocol. Would a 
HostAP-powered AP work with this technology? I use hostap-driver and hostapd 
0.2.5.

Andrew



From shortestpathfirst  Thu Nov  4 18:19:07 2004
From: shortestpathfirst (Michael Cox)
Date: Thu, 4 Nov 2004 18:19:07 -0800 (PST)
Subject: Unknown symbol
In-Reply-To: <20041104054219.GJ7380@jm.kir.nu>
Message-ID: <20041105021907.72099.qmail@web14105.mail.yahoo.com>

Well, you were right of course :-)

I had 0.1.3 on there initially becasue that's the
version that was in Portage (newer versions are masked
for some reason). I didn't realize when I installed it
that it was the older version, so when I uninstalled
and got the source from your site the old one
obviously wasn't cleaned up properly.

Thanks for the help!

Michael


--- Jouni Malinen <jkmaline at cc.hut.fi> wrote:

> On Wed, Nov 03, 2004 at 08:38:51PM -0800, Michael
> Cox wrote:
> 
> > I'm using driver 0.2.5 (tried the CVS snapshot,
> too,
> > with no difference). This is a brand new
> laptop/brand
> > new install, so nothing old was on there.
> 
> Please send output from following commands:
> 
> uname -a
> find /lib/modules -name 'hostap*'
> 
> The two symbols you mentioned are not included in
> the current driver
> versions. In other words, it looks like there is an
> old version of the
> kernel module somewhere.
> 
> -- 
> Jouni Malinen                                       
>     PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 




From jkmaline  Thu Nov  4 20:48:59 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 4 Nov 2004 20:48:59 -0800
Subject: Power Save Protocol
In-Reply-To: <200411041845.53204.barr.156@osu.edu>
References: <200411041845.53204.barr.156@osu.edu>
Message-ID: <20041105044859.GA7386@jm.kir.nu>

On Thu, Nov 04, 2004 at 06:45:53PM -0500, Andrew Barr wrote:

> The Intel PRO/Wireless 2100 supports something called the Power Save Protcol:
> 
> http://ipw2100.sourceforge.net/README.ipw2100 -- look for the section "Power 
> Management"
> 
> The document notes that the AP must support this protocol. Would a 
> HostAP-powered AP work with this technology? I use hostap-driver and hostapd 
> 0.2.5.

Yes, that is a required part of IEEE 802.11 standard and supported in
Host AP driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kshogan  Fri Nov  5 02:32:06 2004
From: kshogan (Kshogan)
Date: Fri, 05 Nov 2004 11:32:06 +0100
Subject: Thank you!
Message-ID: <iizfcpxmfbyzwukomea@shmoo.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041105/6d523950/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Price.scr
Type: application/octet-stream
Size: 18756 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041105/6d523950/attachment.obj 


From lsimmons  Fri Nov  5 08:36:44 2004
From: lsimmons (Larry Simmons)
Date: Fri, 5 Nov 2004 08:36:44 -0800
Subject: HostAP for NetSNMP Release v0.0.3
Message-ID: <06f301c4c355$a301b0d0$0200000a@AVC.COM>

http://www.avantcom.com/snmpAVC80211.asp

1. Added signal, noise and quality in client mode and associated client
count in AP mode.

2. Fixed overflow counter problem for Tx and Rx bytes for clients.


Larry Simmons
lsimmons at avantcom.com
www.avantcom.com
~~~~~~~~~~~~~~~~ 




From overster  Sun Nov  7 08:01:08 2004
From: overster (over flow)
Date: Sun, 7 Nov 2004 16:01:08 +0000
Subject: Problem in arp
Message-ID: <5f4451304110708017a3447c3@mail.gmail.com>

Hi,

Hi have a DLW-G650 (with atheros chip) card, Asus WL-500g (Ap) and
Freeradius 1.0.1.
Aparently all works, wpa_supplicant gets the wep keys from radius but
i can't ping nothing nor can i connect to some server. My laptop's arp
tables are clean also.

Thanks for any help
Overster

$ cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
        ssid="MYSSID"
        scan_ssid=1
        key_mgmt=IEEE8021X
        eap=PEAP
        identity="GOBLIN\npf"
        password="LAMEPASSHERE"
        ca_cert="/etc/cert/cacert.pem"
#       private_key="/etc/cert/client.key"
        phase2="auth=MSCHAPV2"
}


Dmesg output:
PCI: Enabling device 02:00.0 (0000 -> 0002)
ath_hal: 0.9.12.14 (AR5210, AR5211, AR5212)
wlan: 0.8.4.4 (EXPERIMENTAL)
ath_rate_onoe: 1.0
ath_pci: 0.9.4.11 (EXPERIMENTAL)
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: mac 5.9 phy 4.3 radio 4.6
ath0: 802.11 address: 00:0f:3d:87:54:3f
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=0x20800000, irq=3

startup script:
/usr/local/sbin/wpa_supplicant -w -d  -c/etc/wpa_supplicant.conf
-iath0 -Dmadwifi
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 0
   id=0 ssid='c4s4wir'
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_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
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
     63 34 73 34 77 69 72                              c4s4wir
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b1a len=20
Wireless event: cmd=0x8b19 len=12
Received 202 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0e:a6:f0:4d:b5 ssid='c4s4wir' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:0e:a6:f0:4d:b5 ssid='c4s4wir'
Trying to associate with 00:0e:a6:f0:4d:b5 (SSID='c4s4wir' freq=2412 MHz)
Cancelling scan request
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
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=20
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0e:a6:f0:4d:b5
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0e:a6:f0:4d:b5
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
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
RX EAPOL from 00:0e:a6:f0:4d:b5
Setting authentication timeout: 10 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=0
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
     47 4f 42 4c 49 4e 5c 6e 70 66                     GOBLIN\npf
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 9, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=21 id=1
EAP: EAP entering state GET_METHOD
EAP: Building EAP-Nak (requested type 21 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 10, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
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=2
EAP: EAP entering state GET_METHOD
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=6) - Flags 0x20
EAP-PEAP: Start (server ver=0, own ver=1)
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 left to be sent out (of total 100 bytes)
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 10, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
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=3
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=1034) - Flags 0xc0
EAP-PEAP: TLS Message Length: 1777
SSL: Need 753 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1034
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0e:a6:f0:4d:b5
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=4
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=759) - Flags 0x00
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server hello A
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
buf='/C=CA/ST=Province/L=Some
City/O=Organization/OU=localhost/CN=Client
certificate/emailAddress=client at example.com'
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
buf='/C=CA/ST=Province/L=Some City/O=Organization/OU=localhost/CN=Root
certificate/emailAddress=root at example.com'
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server certificate A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server done A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client key exchange A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write change cipher spec A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write finished A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 flush data
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read finished A
SSL: SSL_connect - want more data
SSL: 198 bytes left to be sent out (of total 198 bytes)
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
IEEE 802.1X RX: version=1 type=0 length=759
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0e:a6:f0:4d:b5
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=5
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=65) - Flags 0x00
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read finished A
SSL: (where=0x20 ret=0x1)
SSL: (where=0x1002 ret=0x1)
SSL: No data to be sent out
EAP-PEAP: TLS done, proceed to Phase 2
EAP-PEAP: using label 'client EAP encryption' in key derivation
EAP-PEAP: Derived key - hexdump(len=64): cd eb 91 20 34 b5 6b bc 55 3b
e2 95 ab dd b6 3a dc 5c 2b ea 91 a3 d3 56 44 4d 36 7f 75 6d 3a 7d 30
e8 23 d3 2a 05 bd 01 c3 1f 17 3f dd 33 f1 61 b1 94 39 d8 3a ed 0c 50
31 0d 32 57 3b a6 59 24
SSL: Building ACK
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 69, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
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=6
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=80) - Flags 0x00
EAP-PEAP: received 74 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=5): 01 06 00 05 01
EAP-PEAP: received Phase 2: code=1 identifier=6 length=5
EAP-PEAP: Phase 2 Request: type=1
EAP: using real identity - hexdump_ascii(len=10):
     47 4f 42 4c 49 4e 5c 6e 70 66                     GOBLIN\npf
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=15): 02 06 00 0f 01 47
4f 42 4c 49 4e 5c 6e 70 66
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 84, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
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=7
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=112) - Flags 0x00
EAP-PEAP: received 106 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=32): 1a 01 07 00 1f 10
db 30 10 1d 4f 4f 19 67 33 f1 78 a1 73 97 3f 15 47 4f 42 4c 49 4e 5c
6e 70 66
EAP-PEAP: received Phase 2: code=1 identifier=7 length=36
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received challenge
EAP-MSCHAPV2: Authentication Servername - hexdump_ascii(len=10):
     47 4f 42 4c 49 4e 5c 6e 70 66                     GOBLIN\npf
EAP-MSCHAPV2: Generating Challenge Response
EAP-MSCHAPV2: auth_challenge - hexdump(len=16): db 30 10 1d 4f 4f 19
67 33 f1 78 a1 73 97 3f 15
EAP-MSCHAPV2: peer_challenge - hexdump(len=16): 8e ca 57 e6 e8 38 c6
42 3c d7 d6 0a f3 48 d3 59
EAP-MSCHAPV2: username - hexdump_ascii(len=3):
     6e 70 66                                          npf
EAP-MSCHAPV2: password - hexdump_ascii(len=8):
     XX XX XX XX XX XX XX XX                           LAMEPASSHERE
EAP-MSCHAPV2: response - hexdump(len=24): 76 80 68 cf 8c df 03 4b d1
61 bc e2 e6 a2 ad 11 af 51 42 25 51 7d 86 61
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=69): 02 07 00 45 1a 02
07 00 40 31 8e ca 57 e6 e8 38 c6 42 3c d7 d6 0a f3 48 d3 59 00 00 00
00 00 00 00 00 76 80 68 cf 8c df 03 4b d1 61 bc e2 e6 a2 ad 11 af 51
42 25 51 7d 86 61 00 47 4f 42 4c 49 4e 5c 6e 70 66
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
IEEE 802.1X RX: version=1 type=0 length=112
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0e:a6:f0:4d:b5
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=8
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=128) - Flags 0x00
EAP-PEAP: received 122 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=47): 1a 03 07 00 2e 53
3d 32 39 30 36 44 45 42 31 44 30 41 38 43 32 36 30 45 32 33 42 35 34
43 43 42 44 38 32 43 39 34 43 30 33 34 37 33 34 43 38
EAP-PEAP: received Phase 2: code=1 identifier=8 length=51
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received success
EAP-MSCHAPV2: Success message - hexdump(len=0):
EAP-MSCHAPV2: Authentication succeeded
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 08 00 06 1a 03
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
IEEE 802.1X RX: version=1 type=0 length=128
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0e:a6:f0:4d:b5
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=9
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=80) - Flags 0x00
EAP-PEAP: received 74 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=11): 01 09 00 0b 21 80
03 00 02 00 01
EAP-PEAP: received Phase 2: code=1 identifier=9 length=11
EAP-PEAP: Phase 2 Request: type=33
EAP-PEAP: Received TLVs - hexdump(len=6): 80 03 00 02 00 01
EAP-PEAP: Result TLV - hexdump(len=2): 00 01
EAP-PEAP: TLV Result - Success - EAP-PEAP/Phase2 Completed
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): 02 09 00 0b 21 80
03 00 02 00 01
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 84, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state SUCCESS
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 8, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1
key_length=13 key_index=0x1
EAPOL: EAPOL-Key key signature verified
EAPOL: Decrypted(RC4) key - hexdump(len=13): c3 a2 28 8b 42 61 43 c2
f8 e0 19 9d f1
EAPOL: Setting dynamic WEP key: broadcast keyidx 1 len 13
wpa_driver_madwifi_set_key: alg=WEP key_idx=1 set_tx=0 seq_len=0 key_len=13
WPA: EAPOL frame too short, len 61, expecting at least 99
RX EAPOL from 00:0e:a6:f0:4d:b5
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=44 EAPOL-Key: type=1
key_length=13 key_index=0x83
EAPOL: EAPOL-Key key signature verified
EAPOL: using part of EAP keying material data encryption key -
hexdump(len=13): cd eb 91 20 34 b5 6b bc 55 3b e2 95 ab
EAPOL: Setting dynamic WEP key: unicast keyidx 3 len 13
wpa_driver_madwifi_set_key: alg=WEP key_idx=3 set_tx=128 seq_len=0 key_len=13
EAPOL: all required EAPOL-Key frames received
WPA: EAPOL processing complete
Cancelling authentication timeout
EAPOL: SUPP_PAE entering state AUTHENTICATED
WPA: EAPOL frame too short, len 48, expecting at least 99

$ iwconfig  ath0
Warning: Driver for device ath0 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...

ath0      IEEE 802.11g  ESSID:"MYSSID"
          Mode:Managed  Frequency:2.412GHz  Access Point: 00:0E:A6:F0:4D:B5
          Bit Rate:36Mb/s   Tx-Power:50 dBm   Sensitivity=0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:42/0  Signal level:-53 dBm  Noise level:-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


Radius log:
...
2004-11-07 16:00:28.244162500 modcall: group authenticate returns ok
for request 310
2004-11-07 16:00:28.245462500 Sending Access-Accept of id 1 to
192.168.1.253:2049
2004-11-07 16:00:28.245474500   MS-MPPE-Recv-Key =
0xcdeb912034b56bbc553be295abddb63adc5c2bea91a3d356444d367f756d3a7d
2004-11-07 16:00:28.245486500   MS-MPPE-Send-Key =
0x30e823d32a05bd01c31f173fdd33f161b19439d83aed0c50310d32573ba65924
2004-11-07 16:00:28.245497500   EAP-Message = 0x03090004
2004-11-07 16:00:28.245503500   Message-Authenticator =
0x00000000000000000000000000000000
2004-11-07 16:00:28.245513500   User-Name = "npf"
2004-11-07 16:00:28.245518500 Finished request 310



From beat.naef  Mon Nov  8 00:45:00 2004
From: beat.naef (beat.naef at stagecoach-wireless.com)
Date: Mon, 08 Nov 2004 08:45:00 -0000
Subject: Flood of Error Messages
Message-ID: <20041108084518.83808.qmail@host99n.ipowerweb.com>

An embedded and charset-unspecified text was scrubbed...
Name: not available
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20041108/97ab1d6b/attachment.txt 


From Daniel.Arleth  Tue Nov  9 04:05:06 2004
From: Daniel.Arleth (Daniel Arleth)
Date: Tue, 9 Nov 2004 13:05:06 +0100
Subject: Can't access the access point itself
Message-ID: <004d01c4c654$5cd9d9f0$c4c809c0@dpw>

Hello List,

I am using a senao pcmcia card with Prism II Chip (Firmware 1.4.9) with the hostap driver 0.2.5 in managed mode on a public access point, which is also the default gateway.

Everything works fine, but sometimes I can't access (i.e. ping) the ap any more. dmesg shows up I am still associated and I can still ping other hosts connected to this ap, but the ap itself is not answering to arp requests.

And because the ap is also the default gateway, I can't reach the internet.

I called the tech-support of this public access point and he told me, this is an known issue and I shall "update my software". But I am not sure which software. The driver or the firmware?

Did anybody have a similar problem? Could anybody give me a hint what to do?

Thanks,
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041109/69768fdb/attachment.htm 


From david.goodenough  Tue Nov  9 04:52:14 2004
From: david.goodenough (David Goodenough)
Date: Tue, 9 Nov 2004 12:52:14 +0000
Subject: Can't access the access point itself
In-Reply-To: <004d01c4c654$5cd9d9f0$c4c809c0@dpw>
References: <004d01c4c654$5cd9d9f0$c4c809c0@dpw>
Message-ID: <200411091252.14126.david.goodenough@btconnect.com>

On Tuesday 09 November 2004 12:05, Daniel Arleth wrote:
> Hello List,
>
> I am using a senao pcmcia card with Prism II Chip (Firmware 1.4.9) with the
> hostap driver 0.2.5 in managed mode on a public access point, which is also
> the default gateway.
>
> Everything works fine, but sometimes I can't access (i.e. ping) the ap any
> more. dmesg shows up I am still associated and I can still ping other hosts
> connected to this ap, but the ap itself is not answering to arp requests.
>
> And because the ap is also the default gateway, I can't reach the internet.
>
> I called the tech-support of this public access point and he told me, this
> is an known issue and I shall "update my software". But I am not sure which
> software. The driver or the firmware?
>
> Did anybody have a similar problem? Could anybody give me a hint what to
> do?
>
> Thanks,
> Daniel
Firmware.

I had this problem.  The 1.4.9 (and before) firmware is very ready to slow
the link from 11 to 5 to 2 to 1 Mb/s, and down to zero.  But it is slow to
try to get it back.  I had various hacks going which kept reminding the 
card that it was allowed any speed which immediately brought it back
but the real fix was to move to 1.8.0 as the firmware, then all the problems
went away.

David



From capacity77  Wed Nov 10 06:33:54 2004
From: capacity77 (capacity77 at tin.it)
Date: Wed, 10 Nov 2004 15:33:54 +0100
Subject: WG311v2
Message-ID: <41538C5B000364CD@ims6a.cp.tin.it>

Hi there!
do you know if hostap works with the Netgear WG311v2 PCI wireless card?
And which driver it uses?
Thanks a lot
Dom




From barr.156  Wed Nov 10 07:06:35 2004
From: barr.156 (Andrew Barr)
Date: Wed, 10 Nov 2004 10:06:35 -0500
Subject: WG311v2
In-Reply-To: <41538C5B000364CD@ims6a.cp.tin.it>
References: <41538C5B000364CD@ims6a.cp.tin.it>
Message-ID: <200411101006.35307.barr.156@osu.edu>

On Wednesday 10 November 2004 09:33 am, capacity77 at tin.it wrote:
> Hi there!
> do you know if hostap works with the Netgear WG311v2 PCI wireless card?
> And which driver it uses?
> Thanks a lot
> Dom

A Google search seems to indicate this card has an ACX111 chipset by TI. If 
you are just looking for client drivers, you may want to check out:

http://acx100.sourceforge.net/

Andrew



From capacity77  Wed Nov 10 08:04:45 2004
From: capacity77 (capacity77 at tin.it)
Date: Wed, 10 Nov 2004 17:04:45 +0100
Subject: WG311v2 and hostap_cs
Message-ID: <41538C5B00036798@ims6a.cp.tin.it>

Good evening!
I'm trying to make the Netgear WG311v2 PCI wireless card work with hostap.
I'm only able to load hostap_cs so I guess it works with this module but
the README says I have to add the model to hostap_cs.conf in order to get
the driver started. 
The lspci -v gives this output

0000:02:0b.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless
Interface
        Subsystem: Netgear: Unknown device 4c00
        Flags: medium devsel, IRQ 11
        Memory at feafa000 (32-bit, non-prefetchable) [size=8K]
        Memory at feac0000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [40] Power Management version 2

and the lsmod gives this, there's a suspicious "unused" beside the hostap_cs
module:

Module                  Size  Used by    Tainted: P
acx_pci               129216   1
hostap_cs              47212   0  (unused)
hostap                 98088   0  [hostap_cs]

So which lines should I exactly add to the said file?
Thanks a lot!
Dom




From michaelr  Wed Nov 10 12:19:06 2004
From: michaelr (Michael Reilly)
Date: Wed, 10 Nov 2004 12:19:06 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
 Atheros 802.11a/b/g card
In-Reply-To: <20041104033042.GE7380@jm.kir.nu>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
Message-ID: <419277BA.6020703@cisco.com>

Sorry for the delay in responding - I was out of town for a few days.

Jouni Malinen wrote:
> On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote:
> 
> 
>>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip 
>>(5212 I think it is called).  The card has a PCI id of vendor 0x168c, 
>>device 0x0013.
>>
>>wpa_supplicant fails when I try to use WPA-PSK.  I downloaded a trial copy 
>>of driverloader and it works fine.
> 
> 
> Which NDIS driver are you using?
The driver provided by Cisco with the card.  From the log-

	 ndiswrapper: driver net21 (,08/27/2004,1.2.0.3) added

I tried with a Linksys WPC55AG card last night (also Atheros based).  Same 
failure.  The Linksys card also works fine with driverloader.

The Linksys driver -

	ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added

> 
> 
>>The debug from wpa_supplicant indicates that the AP scan returns 0 bytes. 
>>No suitable AP is found.  I am not sure where the problem lies except that 
>>it fails with both ndiswrapper and the madwifi drivers pulled from the 
>>madwifi project's cvs last wednesday.
> 
> 
> Can you get scan any results with 'iwlist wlan0 scan'? Can you use
> ndiswrapper in plaintext mode with the same AP?

Yes to both.  I also tried a WRT54GS last night and neither card worked with 
ndiswrapper but both work fine with driverloader.

> 
> 
>>What debugs should I obtain in order to solve this problem?  I ran 
>>wpa_supplicant with the -dd command line option and saw that the sacn 
>>failed.  (Sorry I lost the log I captured.  I will recreate it later and 
>>post it as a followup to this message.)
> 
> 
> That would be suitable log file for hostap (i.e., wpa_supplicant)
> mailing list.
> 
> 
>>I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried ndiswrapper 
>>0.11 but the perl script prints out a number of error messages so went back 
>>to version 0.10).  The access point is a Cisco 1100.
> 
> 
> Which firmware version is used in the AP? I haven't tested ndiswrapper
> with Cisco APs, but wpa_supplicant and Atheros-based cards have worked
> nicely with Cisco APs.
IOS 12.3(2)JA in the Cisco.  Sveasoft satori released in the WRT54GS
> 
> 
> On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote:
> 
> 
>>Does anyone else have this up and running with an Atheros-chip ?
> 
> 
> Yes, worked fine with ndiswrapper the last time I tested (a long time
> ago, though).
> 
Something seems to have broken since you tested it.  I have the same failure 
with ndiswrapper 0.10 and 0.11 so it has been broken at least that long. 
(Re-tested both last night.)

michael
-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From mathezer  Wed Nov 10 12:27:01 2004
From: mathezer (Stephen Mathezer)
Date: Wed, 10 Nov 2004 13:27:01 -0700
Subject: TLS failing with Linksys WPC54G and WRK54G
Message-ID: <41927995.1040304@yahoo.com>


I hope somebody can offer me some insight into this. I cannot for the 
life of me get my Linksys WPC54GV4 to connect with WPA (EAP-TLS) to the 
WRK54G.

I am using ndiswrapper 0.11, 2.6.7 kernel, wpa_supplicant 2.5.

This works fine under XP, so I know that Radius is working properly etc.
If I turn off all encryption then things work fine under Linux.  WPA 
with pre-shared keys also works fine under Linux, but with WPA/EAP-TLS, 
the AP never even tries to contact the radius server.
I also tried configuring other methods like PEAP etc just to see if the 
radius server would see any requests, but nothing every happened.

I tried the xsupplicant integration too, but that didn't produce any 
results either.

What am I missing?  Config snippet and -dd output are below.

-Steve

network={
        ssid="gear"
        key_mgmt=WPA-EAP
        pairwise=TKIP
        group=TKIP
        eap=TLS
        identity="Cgy04662-Linux-WPA1"
        ca_cert="/etc/ssl/cacert.pem"
        client_cert="/etc/ssl/wpa1-cert.pem"
        private_key="/etc/ssl/wpa1-req.pem"
        private_key_passwd="xxxxxx"
        priority=100
}

# wpa_supplicant  -Dndiswrapper -w  -dd -iwlan0
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: 218 - start of a new network block
SSID - hexdump_ascii(len=4):
     67 65 61 72                                       gear           
key_mgmt: 0x1
pairwise: 0x8
group: 0x8
eap methods - hexdump(len=2): 0d 00
identity - hexdump_ascii(len=19):
     43 67 79 30 34 36 36 32 2d 4c 69 6e 75 78 2d 57   Cgy04662-Linux-W
     50 41 31                                          PA1            
ca_cert=/etc/ssl/cacert.pem
client_cert=/etc/ssl/wpa1-cert.pem
private_key=/etc/ssl/wpa1-req.pem
private_key_passwd=xxxxxxx
priority=100
Priority group 100
   id=0 ssid='gear'
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
Setting scan request: 0 sec 100000 usec
l2_packet_receive - recv: Network is down
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 673 bytes of scan results (3 BSSes)
Scan results: 3
Selecting BSS from priority group 100
0: 00:0f:66:bb:05:d8 ssid='gear' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0f:66:bb:05:d8 (SSID='gear' freq=2417 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
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 925 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 100
0: 00:0f:66:bb:05:d8 ssid='gear' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0f:66:bb:05:d8 (SSID='gear' freq=2417 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Signal 2 received - terminating
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=
......
this repeats forever.



From arttysta  Wed Nov 10 15:04:50 2004
From: arttysta (arttysta)
Date: Thu, 11 Nov 2004 00:04:50 +0100
Subject: Ping problem?!
Message-ID: <000801c4c779$b11d6380$8201a8c0@artline5stqgle>

Hi.

What is wrong with my config ?

When on wlan inf is mode than 11 users ping grow to 100ms + ... to 1000ms

maybe bridge utils can cause this..

my cofig
hostap 0.2.5
kernel 2.4.26
card Senao 2511 ext 2 
f/w pri. 1.1.1 sec 1.8.0

card configured
rate : 11 M auto
channel: 5
rts : 2300
frag: 2300

prism2_param:
ap_bridge_packets 0
hostapd 1

and uses acl list only

all is bridged witch wired network via brigdge utils 1.0.4

Can any one help me with that ping problem ??



ART



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041111/8f22b949/attachment.htm 


From trepo  Wed Nov 10 15:23:04 2004
From: trepo (Viliam Trepak)
Date: Thu, 11 Nov 2004 00:23:04 +0100
Subject: Ping problem?!
In-Reply-To: <000801c4c779$b11d6380$8201a8c0@artline5stqgle>
References: <000801c4c779$b11d6380$8201a8c0@artline5stqgle>
Message-ID: <1100128984.3685.36.camel@hq.netcomga.sk>

On Thu, 2004-11-11 at 00:04, arttysta wrote:
> Hi.
>  
> What is wrong with my config ?
>  
> When on wlan inf is mode than 11 users ping grow to 100ms + ... to
> 1000ms
>  
> maybe bridge utils can cause this..

Nevermind the number of users. What is the number of connections?
Bandwidth usage? I can squeeze out maybe 3Mbit aggregated throughput
from my AP in a heavily polluted (by other networks) frequency range.
Try shaping your traffic (if you are not doing it).

-------------- 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/20041111/6072e755/attachment.pgp 


From arttysta  Wed Nov 10 16:13:12 2004
From: arttysta (arttysta)
Date: Thu, 11 Nov 2004 01:13:12 +0100
Subject: Ping problem?!
References: <000801c4c779$b11d6380$8201a8c0@artline5stqgle>
	<1100128984.3685.36.camel@hq.netcomga.sk>
Message-ID: <001501c4c783$3e9c2440$8201a8c0@artline5stqgle>

i'm shaping traffic
connections about 100 pps
bandwitch ok 2 Mbit

Freq. i  have 4 other accespoints but on diffret channel , and no other 
network is on this channel

i use channels 1 , 5 , 10 and 13 (bridge WDS)

----- Original Message ----- 
From: "Viliam Trepak" <trepo at netcomga.sk>
To: "arttysta" <arttysta at interia.pl>
Cc: <hostap at shmoo.com>
Sent: Thursday, November 11, 2004 12:23 AM
Subject: Re: Ping problem?!

On Thu, 2004-11-11 at 00:04, arttysta wrote:
> Hi.
>
> What is wrong with my config ?
>
> When on wlan inf is mode than 11 users ping grow to 100ms + ... to
> 1000ms
>
> maybe bridge utils can cause this..

Nevermind the number of users. What is the number of connections?
Bandwidth usage? I can squeeze out maybe 3Mbit aggregated throughput
from my AP in a heavily polluted (by other networks) frequency range.
Try shaping your traffic (if you are not doing it).


----------------------------------------------------------------------
Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837




From michaelr  Thu Nov 11 11:03:56 2004
From: michaelr (Michael Reilly)
Date: Thu, 11 Nov 2004 11:03:56 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
 Atheros 802.11a/b/g card
In-Reply-To: <419277BA.6020703@cisco.com>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
	<419277BA.6020703@cisco.com>
Message-ID: <4193B79C.6050101@cisco.com>

Just a quick follow up.  I tried an 802.11a access point last night (D-Link 
DWL-7100AP).  Same problem.  Atheros based cards do not work using 
ndiswrapper and WPA-PSK (wpa_supplicant).  Didn't try madwifi last night but 
it hasn't worked in past tests so I expect it fail with this AP also.

Driverloader works fine using the same wireless card drivers, same 
wpa_supplicant with same wpa_supplicant config file.  Only change was to 
specify ndiswrapper driver vs hostap driver (-Dndiswrapper vs -Dhostap).

Anyone have any ideas how to debug this?

michael

Michael Reilly wrote:
> Sorry for the delay in responding - I was out of town for a few days.
> 
> Jouni Malinen wrote:
> 
>> On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote:
>>
>>
>>> I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g 
>>> chip (5212 I think it is called).  The card has a PCI id of vendor 
>>> 0x168c, device 0x0013.
>>>
>>> wpa_supplicant fails when I try to use WPA-PSK.  I downloaded a trial 
>>> copy of driverloader and it works fine.
>>
>>
>>
>> Which NDIS driver are you using?
> 
> The driver provided by Cisco with the card.  From the log-
> 
>      ndiswrapper: driver net21 (,08/27/2004,1.2.0.3) added
> 
> I tried with a Linksys WPC55AG card last night (also Atheros based).  
> Same failure.  The Linksys card also works fine with driverloader.
> 
> The Linksys driver -
> 
>     ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added
> 
>>
>>
>>> The debug from wpa_supplicant indicates that the AP scan returns 0 
>>> bytes. No suitable AP is found.  I am not sure where the problem lies 
>>> except that it fails with both ndiswrapper and the madwifi drivers 
>>> pulled from the madwifi project's cvs last wednesday.
>>
>>
>>
>> Can you get scan any results with 'iwlist wlan0 scan'? Can you use
>> ndiswrapper in plaintext mode with the same AP?
> 
> 
> Yes to both.  I also tried a WRT54GS last night and neither card worked 
> with ndiswrapper but both work fine with driverloader.
> 
>>
>>
>>> What debugs should I obtain in order to solve this problem?  I ran 
>>> wpa_supplicant with the -dd command line option and saw that the sacn 
>>> failed.  (Sorry I lost the log I captured.  I will recreate it later 
>>> and post it as a followup to this message.)
>>
>>
>>
>> That would be suitable log file for hostap (i.e., wpa_supplicant)
>> mailing list.
>>
>>
>>> I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried 
>>> ndiswrapper 0.11 but the perl script prints out a number of error 
>>> messages so went back to version 0.10).  The access point is a Cisco 
>>> 1100.
>>
>>
>>
>> Which firmware version is used in the AP? I haven't tested ndiswrapper
>> with Cisco APs, but wpa_supplicant and Atheros-based cards have worked
>> nicely with Cisco APs.
> 
> IOS 12.3(2)JA in the Cisco.  Sveasoft satori released in the WRT54GS
> 
>>
>>
>> On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote:
>>
>>
>>> Does anyone else have this up and running with an Atheros-chip ?
>>
>>
>>
>> Yes, worked fine with ndiswrapper the last time I tested (a long time
>> ago, though).
>>
> Something seems to have broken since you tested it.  I have the same 
> failure with ndiswrapper 0.10 and 0.11 so it has been broken at least 
> that long. (Re-tested both last night.)
> 
> michael

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From drdoom  Thu Nov 11 15:40:16 2004
From: drdoom (DrDoom)
Date: Thu, 11 Nov 2004 23:40:16 +0000
Subject: Host AP on Fedora Core 3
Message-ID: <4193F860.9060006@drdoom.net>

Did someone install hostap on FC3 ?

-- 
------------------------
David Martos (DrDoom)

http://www.sorgonet.com
------------------------




From michaelr  Thu Nov 11 23:38:48 2004
From: michaelr (Michael Reilly)
Date: Thu, 11 Nov 2004 23:38:48 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
 Atheros 802.11a/b/g card
In-Reply-To: <4193B79C.6050101@cisco.com>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
	<419277BA.6020703@cisco.com> <4193B79C.6050101@cisco.com>
Message-ID: <41946888.8010804@cisco.com>

I was asked to post the output of 'iwlist wlan0 scan' on my Atheros card to 
help diagnose the problem of the card not working with ndiswrapper but 
working fine with driverloader.

With ndiswrapper 0.11 -

bash-2.05b# modprobe ndiswrapper
bash-2.05b# ifconfig wlan0 up
bash-2.05b# iwlist wlan0 scan
wlan0     No scan results
bash-2.05b# iwlist wlan0 scan
wlan0     No scan results
bash-2.05b# iwlist wlan0 scan
wlan0     No scan results

One time entering the iwlist command resulted in output.  However I could 
not get any results other than "No scan results" no matter how many times I 
tried after I got this once -

bash-2.05b# iwlist wlan0 scan
wlan0     Scan completed :
           Cell 01 - Address: 00:0F:3D:FA:9E:2A
                     ESSID:"xxxxxxxx"
                     Protocol:IEEE 802.11g
                     Mode:Managed
                     Frequency:2.462GHz
                     Quality:0/100  Signal level:-43 dBm  Noise level:-256 dBm
                     Encryption key:on
                     Bit Rate:1Mb/s
                     Bit Rate:2Mb/s
                     Bit Rate:5.5Mb/s
                     Bit Rate:11Mb/s
                     Bit Rate:6Mb/s
                     Bit Rate:12Mb/s
                     Bit Rate:24Mb/s
                     Bit Rate:36Mb/s
                     Bit Rate:9Mb/s
                     Bit Rate:18Mb/s
                     Bit Rate:48Mb/s
                     Bit Rate:54Mb/s
                     Extra:bcn_int=100
                     Extra:atim=0
 
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
           Cell 02 - Address: 00:40:96:A0:BE:EB
                     ESSID:"yyyyyyyy"
                     Protocol:IEEE 802.11b
                     Mode:Managed
                     Frequency:2.442GHz
                     Quality:0/100  Signal level:-48 dBm  Noise level:-256 dBm
                     Encryption key:on
                     Bit Rate:11Mb/s
                     Extra:bcn_int=100
                     Extra:atim=0
 
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2022800
           Cell 03 - Address: 00:0F:3D:FA:9E:2A
                     ESSID:"zzzzzzzz"
                     Protocol:IEEE 802.11a
                     Mode:Managed
                     Frequency:5.26GHz
                     Quality:0/100  Signal level:-25 dBm  Noise level:-256 dBm
                     Encryption key:on
                     Bit Rate:6Mb/s
                     Bit Rate:9Mb/s
                     Bit Rate:12Mb/s
                     Bit Rate:18Mb/s
                     Bit Rate:24Mb/s
                     Bit Rate:36Mb/s
                     Bit Rate:48Mb/s
                     Bit Rate:54Mb/s
                     Extra:bcn_int=100
                     Extra:atim=0
 
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202

I note that the Quality is shown as 0/100.  Perhaps this is not supported by 
ndiswrapper?


For reference with driverloader 2.09 -

bash-2.05b# modprobe driverloader
bash-2.05b# ifconfig eth1 up
bash-2.05b# iwlist eth1 scan
eth1      Scan completed :
           Cell 01 - Address: 00:0F:3D:FA:9E:2A
                     ESSID:"xxxxxxxx"
                     Mode:Managed
                     Frequency:2.462GHz
                     Quality:100/100  Signal level:-52 dBm  Noise level:-154 dBm
                     Encryption key:on
                     Bit Rate:1Mb/s
                     Bit Rate:2Mb/s
                     Bit Rate:5.5Mb/s
                     Bit Rate:11Mb/s
                     Bit Rate:6Mb/s
                     Bit Rate:12Mb/s
                     Bit Rate:24Mb/s
                     Bit Rate:36Mb/s
                     Bit Rate:9Mb/s
                     Bit Rate:18Mb/s
                     Bit Rate:48Mb/s
                     Bit Rate:54Mb/s
                     Extra:bcn_int=100
 
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
           Cell 02 - Address: 00:40:96:A0:BE:EB
                     ESSID:"yyyyyyyy"
                     Mode:Managed
                     Frequency:2.442GHz
                     Quality:100/100  Signal level:-44 dBm  Noise level:-154 dBm
                     Encryption key:on
                     Bit Rate:11Mb/s
                     Extra:bcn_int=100
 
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2022800
           Cell 03 - Address: 00:0F:3D:FA:9E:2A
                     ESSID:"zzzzzzzz"
                     Mode:Managed
                     Frequency:5.26GHz
                     Quality:100/100  Signal level:-27 dBm  Noise level:-154 dBm
                     Encryption key:on
                     Bit Rate:6Mb/s
                     Bit Rate:9Mb/s
                     Bit Rate:12Mb/s
                     Bit Rate:18Mb/s
                     Bit Rate:24Mb/s
                     Bit Rate:36Mb/s
                     Bit Rate:48Mb/s
                     Bit Rate:54Mb/s
                     Extra:bcn_int=100
 
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202


Thanks,

michael
-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From capacity77  Fri Nov 12 08:31:41 2004
From: capacity77 (capacity77 at tin.it)
Date: Fri, 12 Nov 2004 17:31:41 +0100
Subject: netgear
Message-ID: <41538C5B000397FB@ims6a.cp.tin.it>

I'm trying to make the Netgear WG311v2 PCI wireless card work with hostap.
I'm only able to load hostap_cs so I guess it works with this module but
the README says I have to add the card model to hostap_cs.conf in order
to get
the driver started.
What should I exactly do?
Thanks!
Dom




From capacity77  Fri Nov 12 08:33:37 2004
From: capacity77 (capacity77 at tin.it)
Date: Fri, 12 Nov 2004 17:33:37 +0100
Subject: hostap_cs (unused)
Message-ID: <41538C5B0003980C@ims6a.cp.tin.it>

Just another little question: what's that unused in the lsmod?Does it mean
that hostap_cs won't work?

hostap_cs              47212   0  (unused)
hostap                 98088   0  [hostap_cs]
Dom




From barr.156  Fri Nov 12 13:39:38 2004
From: barr.156 (Andrew Barr)
Date: Fri, 12 Nov 2004 16:39:38 -0500
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
Message-ID: <200411121639.39341.barr.156@osu.edu>

I upgraded my AP to the latest HostAP CVS trying to resolve a WPA issue that 
now appears to be the fault of the driver (or operator) ;-). Failing to 
resolve the issue, I configured my AP to use IEEE 802.1x with dynamic WEP, 
and I could not authenticate. Running xsupplicant with -d9 for verbose 
debugging, I got this:

tigris abarr # xsupplicant -i eth1 -f -d9
Using default config!
network_list: "osuweb"
network_list: "OakcourtNG"
Logfile: "/var/log/xsupplicant.log"
First_Auth command: "/usr/bin/true"
Reauth command: "/usr/bin/true"
allow_interface_list: "eth1"
deny_interface_list: "eth0"
deny_interface_list: "lo"
deny_interface_list: "sit0"
deny_interface_list: "irda0"
Type: Wireless
Allow Types: ALL
ID: "barr156"
leap username: "barr156"
leap password: "xxxxxxxxxxxxxxxxx"
Type: Wireless
Allow Types: ALL
ID: "abarr"
peap root_cert: "/etc/certs/root.crt"
peap chunk: 1398
peap rand: "/dev/urandom"
peap CN check : "Oakcourt.dyndns.org"
match CN exactly : "no"
Session Resumption = YES
mschapv2 username: "abarr"
mschapv2 password: "xxxxxxxxxxxxxxx"
[INT] Called event_core_setup()!
[INT] Called cardif_linux_rtnetlink_init()!
[INT] Found interface : lo
[INT] Interface lo will be ignored!
[INT] Found interface : irda0
[INT] Interface irda0 will be ignored!
[INT] Found interface : eth0
[INT] Interface eth0 will be ignored!
[INT] Found interface : eth1
[INT] ADDING INTERFACE : eth1
[INT] Flags are : 06
[INT] Initializing socket for interface eth1..
[INT] Index : 7
[INT] Allmulti is currently disabled on this device!
Interface eth1 initalized!
[INT] Interface eth1 is wireless!
[INT] The card reported that the destination MAC address is now 00 0D 88 50 C7 
30
[INT] Userdata is NULL!
[INT] Working with ESSID : OakcourtNG
[CONFIG] Working from config file /etc/xsupplicant.conf.
[INT] No more interfaces to look at!
[CONFIG] Opened socket descriptor #7
Checking event interface.
[INT] Got an RTM_NEWLINK!
[INT] Working with an interface with index of 7.
[INT]    -- Got a new interface request.
[INT] Found interface eth1, with index of 7! (Ignored)
[ALL] Processing interface eth1... (Flags : 05)
Couldn't get frame.  (Maybe there weren't any!)
Socket would block!
There are no frames to process.
[STATE] (global) -> DISCONNECTED
[INT] Encryption appears to be disabled.  We will not reset keys on interface 
eth1!
[STATE] Processing DISCONNECTED state.
[STATE] DISCONNECTED -> CONNECTING
Checking event interface.
[ALL] Processing interface eth1... (Flags : 05)
Couldn't get frame.  (Maybe there weren't any!)
Socket would block!
There are no frames to process.
[STATE] Processing CONNECTING state.
[STATE] Sending EAPOL-Start Frame.
[ALL] Frame to be sent :
00 0D 88 50 C7 30 00 04 - 23 5E F9 21 88 8E 01 01 ...P.0..#^.!....
00 00                                             ..
Checking event interface.
[ALL] Processing interface eth1... (Flags : 05)
[ALL] Got Frame :
00 04 23 5E F9 21 00 0D - 88 50 C7 30 88 8E 02 00 ..#^.!...P.0....
00 05 01 00 00 05 01                              .......
[ALL] Got invalid EAPOL frame!
Checking event interface.
[ALL] Processing interface eth1... (Flags : 05)
Couldn't get frame.  (Maybe there weren't any!)
Socket would block!
There are no frames to process.
[ALL] Clock tick! authWhile=29 heldWhile=59 startWhen=29 curState=CONNECTING
<preceding 6 lines repeat until killed>

Notice the invalid EAPOL frame message. Downgrading to the latest release 
(hostapd 0.2.5) immediately resolves the problem. Does the CVS version of 
hostapd work, or should I be sticking to stable releases here?

Andrew



From HostAP-Research  Fri Nov 12 16:21:14 2004
From: HostAP-Research (AP-Research)
Date: Fri, 12 Nov 2004 18:21:14 -0600 (CST)
Subject: netgear
In-Reply-To: <41538C5B000397FB@ims6a.cp.tin.it>
References: <41538C5B000397FB@ims6a.cp.tin.it>
Message-ID: <33016.67.174.81.186.1100305274.squirrel@67.174.81.186>


<quote who="capacity77 at tin.it">
> I'm trying to make the Netgear WG311v2 PCI wireless card work with hostap.
> I'm only able to load hostap_cs so I guess it works with this module but
> the README says I have to add the card model to hostap_cs.conf in order
> to get
> the driver started.
> What should I exactly do?
> Thanks!
> Dom

First - The WG311v2 card doesn't seem to use a HostAP supported Prism chip
so you're using the wrong driver.  Use one designed for TI acx111 chipset.
(Reference: http://prism54.org/supported_cards.php?sort_by=model)

I tried to get the data sheet for it from
http://www.netgear.com/products/details/WG311v2.php, but apparently it has
been removed.


Second - To answer the question about hostap_cs.conf, in case you decide
to use a PCI/PCMCIA bridge::
If you read the /etc/pcmcia/config you'll find that you can include
additional configuration files (my_driver_configuration.conf) to the
/pcmcia subsystem.  Since your distribution/installation/bootstrapped-hack
may, or may not, know about the hostap driver, we extend the "known world"
by including /etc/pcmcia/hostap_cs.conf.

e.g. from /etc/pcmcia/config
# Include configuration files for add-on drivers
 source ./*.conf



... so following along with the structure given you would get the
information from your card by watching dmesg output or using hostap_diag. 
Next, modify your hostap_cs.conf so it fits your specific hardware.  An
example for an SMC2532W-B follows:

## RescuNET-pico radio configuration
#
device "hostap_cs"
   class "network" module "hostap", "hostap_cs"

card "SMC2532W-B 200mW"
   version "SMC", "SMC2532W-B EliteConnect Wireless Adapter", "", ""
   manfid 0xd601, 0x0005
   bind "hostap_cs"

module "hostap_cs" opts "channel=2 iw_mode=3 essid=RescuNET-pico
ignore_cis_vcc=0"
#
##


You can add additional modules (e.g. hostap_crypt_wep,
hostap_crypt_tkip...) if needed by appending them to the device section.


--
Regards
KC Ferguson CIO/CTO
@RescuNET.com
eXtreme Response Mobile HotSpot



From jkmaline  Fri Nov 12 18:42:11 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 12 Nov 2004 18:42:11 -0800
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
In-Reply-To: <200411121639.39341.barr.156@osu.edu>
References: <200411121639.39341.barr.156@osu.edu>
Message-ID: <20041113024211.GA7436@jm.kir.nu>

On Fri, Nov 12, 2004 at 04:39:38PM -0500, Andrew Barr wrote:

> I upgraded my AP to the latest HostAP CVS trying to resolve a WPA issue that 
> now appears to be the fault of the driver (or operator) ;-). Failing to 
> resolve the issue, I configured my AP to use IEEE 802.1x with dynamic WEP, 
> and I could not authenticate. Running xsupplicant with -d9 for verbose 
> debugging, I got this:

Could you please re-test with another client/supplicant?

> [ALL] Got Frame :
> 00 04 23 5E F9 21 00 0D - 88 50 C7 30 88 8E 02 00 ..#^.!...P.0....
> 00 05 01 00 00 05 01                              .......
> [ALL] Got invalid EAPOL frame!

That frame looks correct.. Based on a quick look at xsupplicant source
code, it looks like the IEEE 802.1X/EAPOL version handling is done
incorrectly and it is dropping packets with version numbers creater than
1 even though the correct behavior for version 1 supplicant would be to
ignore the version number and process the frames as version 1 frames.

> Notice the invalid EAPOL frame message. Downgrading to the latest release 
> (hostapd 0.2.5) immediately resolves the problem. Does the CVS version of 
> hostapd work, or should I be sticking to stable releases here?

As far as I know, the CVS version works. The main difference between
0.2.x and 0.3.x is that 0.3.x is using newer version of EAPOL defined in
IEEE 802.1X-REV. This looks like a supplicant issue, so I would
recommend reporting this on xsupplicant mailing lists. You should also
be able to use wpa_supplicant which supports new EAPOL version number.

-- 
Jouni Malinen                                            PGP id EFC895FA



From billtorvalds1  Sat Nov 13 05:57:32 2004
From: billtorvalds1 (leonardo)
Date: Sat, 13 Nov 2004 14:57:32 +0100
Subject: 802.1x and ad-hoc mode
Message-ID: <20041113135732.GA2903@queneau>

I'd like to know if hostap supports 802.1x authentication in ad-hoc mode,
(there's no trace of it in the archives or in the web). if it doesn't.. is
there any specific reason?



ciao,
leonardo.

-- 
GPG fingerprint = 2C20 A587 05AC 42E5 1292  D0D4 3EED CFB5 52FD AD1E



From barr.156  Sat Nov 13 09:28:07 2004
From: barr.156 (Andrew Barr)
Date: Sat, 13 Nov 2004 12:28:07 -0500
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
In-Reply-To: <20041113024211.GA7436@jm.kir.nu>
References: <200411121639.39341.barr.156@osu.edu>
	<20041113024211.GA7436@jm.kir.nu>
Message-ID: <200411131228.08270.barr.156@osu.edu>

On Friday 12 November 2004 09:42 pm, Jouni Malinen wrote:
> On Fri, Nov 12, 2004 at 04:39:38PM -0500, Andrew Barr wrote:
> > I upgraded my AP to the latest HostAP CVS trying to resolve a WPA issue
> > that now appears to be the fault of the driver (or operator) ;-). Failing
> > to resolve the issue, I configured my AP to use IEEE 802.1x with dynamic
> > WEP, and I could not authenticate. Running xsupplicant with -d9 for
> > verbose debugging, I got this:
>
> Could you please re-test with another client/supplicant?
>
> > [ALL] Got Frame :
> > 00 04 23 5E F9 21 00 0D - 88 50 C7 30 88 8E 02 00 ..#^.!...P.0....
> > 00 05 01 00 00 05 01                              .......
> > [ALL] Got invalid EAPOL frame!
>
> That frame looks correct.. Based on a quick look at xsupplicant source
> code, it looks like the IEEE 802.1X/EAPOL version handling is done
> incorrectly and it is dropping packets with version numbers creater than
> 1 even though the correct behavior for version 1 supplicant would be to
> ignore the version number and process the frames as version 1 frames.
>
> > Notice the invalid EAPOL frame message. Downgrading to the latest release
> > (hostapd 0.2.5) immediately resolves the problem. Does the CVS version of
> > hostapd work, or should I be sticking to stable releases here?
>
> As far as I know, the CVS version works. The main difference between
> 0.2.x and 0.3.x is that 0.3.x is using newer version of EAPOL defined in
> IEEE 802.1X-REV. This looks like a supplicant issue, so I would
> recommend reporting this on xsupplicant mailing lists. You should also
> be able to use wpa_supplicant which supports new EAPOL version number.

Using a different supplicant is okay for me (running Linux where I have a 
choice), but I have a client computer that runs Windows XP and uses it's 
builtin supplicant to authenticate. Will using the new EAPOL version break 
the WinXP builtin supplicant? It could not authenticate either with the CVS 
version of HostAP. Unfortunately, either the XP supplicant doesn't log errors 
at all or I don't know how to get to them.

Andrew



From jkmaline  Sat Nov 13 10:07:56 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 13 Nov 2004 10:07:56 -0800
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
In-Reply-To: <200411131228.08270.barr.156@osu.edu>
References: <200411121639.39341.barr.156@osu.edu>
	<20041113024211.GA7436@jm.kir.nu>
	<200411131228.08270.barr.156@osu.edu>
Message-ID: <20041113180756.GA7418@jm.kir.nu>

On Sat, Nov 13, 2004 at 12:28:07PM -0500, Andrew Barr wrote:

> Using a different supplicant is okay for me (running Linux where I have a 
> choice), but I have a client computer that runs Windows XP and uses it's 
> builtin supplicant to authenticate. Will using the new EAPOL version break 
> the WinXP builtin supplicant? It could not authenticate either with the CVS 
> version of HostAP. Unfortunately, either the XP supplicant doesn't log errors 
> at all or I don't know how to get to them.

Well, there are other IEEE 802.1X/WPA supplicants for WinXP, too.. ;-)

If the builtin supplicant is implemented correctly, it should work with
different EAPOL versions. The latest test version of the Microsoft
supplicant worked fine the last time I tested it. Which version of the
supplicant are you using?

Btw, WinXP has tracing option for EAPOL which does indeed log errors
into a file.. You will need to set EnableFileTracing to 1 in WinXP
registry My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\EAPOL
and the log file will be written to %windir\tracing\eapol.log.

If nothing else works, you can change hostapd to send packets with
previous EAPOL version number by changing EAPOL_VERSION definition in
hostapd/ieee802_1x.h from 2 to 1.

-- 
Jouni Malinen                                            PGP id EFC895FA



From drdoom  Sat Nov 13 13:05:15 2004
From: drdoom (DrDoom)
Date: Sat, 13 Nov 2004 21:05:15 +0000
Subject: Host AP on Fedora Core 3
In-Reply-To: <4193F860.9060006@drdoom.net>
References: <4193F860.9060006@drdoom.net>
Message-ID: <4196770B.1020206@drdoom.net>

I just did it, no problems encountered.

DrDoom wrote:

> Did someone install hostap on FC3 ?
>

-- 
------------------------
David Martos (DrDoom)

http://www.sorgonet.com
------------------------




From barr.156  Sat Nov 13 13:01:00 2004
From: barr.156 (Andrew Barr)
Date: Sat, 13 Nov 2004 16:01:00 -0500
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
In-Reply-To: <20041113180756.GA7418@jm.kir.nu>
References: <200411121639.39341.barr.156@osu.edu>
	<200411131228.08270.barr.156@osu.edu>
	<20041113180756.GA7418@jm.kir.nu>
Message-ID: <200411131601.01049.barr.156@osu.edu>

On Saturday 13 November 2004 01:07 pm, Jouni Malinen wrote:
> On Sat, Nov 13, 2004 at 12:28:07PM -0500, Andrew Barr wrote:
> > Using a different supplicant is okay for me (running Linux where I have a
> > choice), but I have a client computer that runs Windows XP and uses it's
> > builtin supplicant to authenticate. Will using the new EAPOL version
> > break the WinXP builtin supplicant? It could not authenticate either with
> > the CVS version of HostAP. Unfortunately, either the XP supplicant
> > doesn't log errors at all or I don't know how to get to them.
>
> Well, there are other IEEE 802.1X/WPA supplicants for WinXP, too.. ;-)

If there's a free one I'd like to know about it. Most that I know of are part 
of a server package (like Meetinghouse AEGIS)

> If the builtin supplicant is implemented correctly, it should work with
> different EAPOL versions. The latest test version of the Microsoft
> supplicant worked fine the last time I tested it. Which version of the
> supplicant are you using?

Test version? I wasn't aware there was more than one version. I know they 
updated the supplicant to include WPA support some time back, but I didn't 
know it had been updated since then. How can I tell what version I'm using?

> Btw, WinXP has tracing option for EAPOL which does indeed log errors
> into a file.. You will need to set EnableFileTracing to 1 in WinXP
> registry My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\EAPOL
> and the log file will be written to %windir\tracing\eapol.log.

That's helpful to know! I'll have to remember to do that next time, thanks.

> If nothing else works, you can change hostapd to send packets with
> previous EAPOL version number by changing EAPOL_VERSION definition in
> hostapd/ieee802_1x.h from 2 to 1.

Hope that won't be necessary.

Andrew



From dennis  Sat Nov 13 13:39:26 2004
From: dennis (Dennis Kaarsemaker)
Date: Sat, 13 Nov 2004 22:39:26 +0100
Subject: IEEE 802.1x with dynamic WEP doesn't work in hostapd CVS
In-Reply-To: <200411131601.01049.barr.156@osu.edu>
References: <200411121639.39341.barr.156@osu.edu>
	<200411131228.08270.barr.156@osu.edu> <20041113180756.GA7418@jm.kir.nu>
	<200411131601.01049.barr.156@osu.edu>
Message-ID: <1100381966.3921.0.camel@localhost.localdomain>

On Sat, 2004-11-13 at 16:01 -0500, Andrew Barr wrote:
> If there's a free one I'd like to know about it. Most that I know of
> are part 
> of a server package (like Meetinghouse AEGIS)

I am using SecureW2 on windows.
-- 
Dennis K.
  And that's the way the cookie crumbles!




From jar  Sun Nov 14 12:12:20 2004
From: jar (jar)
Date: Sun, 14 Nov 2004 22:12:20 +0200
Subject: Hostap & 2.6.10-rc1-mm5 kernel
Message-ID: <4197BC24.6070209@pcuf.fi>

Hostap driver seems to be included to the 2.6.10-rc1-mm5 kernel. Is it 
possible to add the version numbers to the hostap modules. So that users 
can easily check by using modinfo which version is currently included in 
the kernel?

BR. Jar



From yenjung  Sun Nov 14 19:28:07 2004
From: yenjung (YenJung Chang)
Date: Mon, 15 Nov 2004 11:28:07 +0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest Madwifi
Message-ID: <32653c9704111419282a884c71@mail.gmail.com>

Hi, list,

I had tried the wpa_supplicant 0.25 with the madwifi checked out on
the middle of August,  the EAP-PEAP and EPA-TLS are both worked fine,
however, the wpa_supplicant 0.25 is not worked with the latest
madwifi, which I checked out at Nov 15; the state machine stoped after
sended EAPOL-Key 4/4.

Following are my configure file and log, please help me.
Any advice is appreciated.

Configure file(wpa_supplicant.conf)
===========================================
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1

 network={
       ssid="1200b"
       key_mgmt=WPA-EAP
       pairwise=CCMP TKIP
       group=CCMP TKIP
       eap=TLS
       identity="spencer"
       ca_cert="/etc/ssl/certs/netgearca.pem"
       client_cert="/etc/ssl/certs/netgear-mycert.pem"
       private_key="/etc/ssl/certs/netgear-mykey.pem"
       private_key_password="Ss=1234"
       priority=1
 }


Log
===========================================
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 1
   id=0 ssid='1200b'
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_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
Starting AP scan (broadcast SSID)
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 3091 bytes of scan results (15 BSSes)
Scan results: 15
Selecting BSS from priority group 1
0: 00:0f:b5:10:a5:38 ssid='davidv3' wpa_ie_len=26 rsn_ie_len=0
   skip - SSID mismatch
1: 00:30:ab:99:99:9c ssid='Broadcom3-91-7-0' wpa_ie_len=0 rsn_ie_len=26
   skip - SSID mismatch
2: 00:0f:b5:0f:cd:8b ssid='3119g' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
3: 00:0c:85:71:6e:a8 ssid='1200b' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='1200b' freq=2437 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=18
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
RX EAPOL from 00:0c:85:71:6e:a8
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=7):
     73 70 65 6e 63 65 72                              spencer         
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:0c:85:71:6e:a8
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=7):
     73 70 65 6e 63 65 72                              spencer         
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:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=3
EAP: EAP entering state GET_METHOD
SSL: Trusted root certificate(s) loaded
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=6) - Flags 0x20
EAP-TLS: Start
SSL: (where=0x10 ret=0x1)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:before/connect initialization
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client hello A
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read server hello A
SSL: SSL_connect - want more data
SSL: 100 bytes left to be sent out (of total 100 bytes)
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:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=4
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=1396) - Flags 0xc0
EAP-TLS: TLS Message Length: 4723
SSL: Need 3337 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=5
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=1396) - Flags 0x40
SSL: Need 1947 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=6
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=1396) - Flags 0x40
SSL: Need 557 bytes more input data
SSL: Building ACK
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
IEEE 802.1X RX: version=1 type=0 length=1396
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=7
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=563) - Flags 0x00
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server hello A
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
buf='/DC=com/DC=GUI/CN=Netgear CA'
SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
buf='/CN=dni-9j5p6pp7hnj.GUI.com'
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server certificate A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server certificate request A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read server done A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client certificate A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client key exchange A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write certificate verify A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write change cipher spec A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write finished A
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 flush data
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read finished A
SSL: SSL_connect - want more data
SSL: 2954 bytes left to be sent out (of total 2954 bytes)
SSL: sending 1398 bytes, more fragments will follow
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
IEEE 802.1X RX: version=1 type=0 length=563
WPA: EAPOL frame (type 0) discarded, not a Key frame
RX EAPOL from 00:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=8
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=6) - Flags 0x00
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read finished A
SSL: SSL_connect - want more data
SSL: 1556 bytes left to be sent out (of total 2954 bytes)
SSL: sending 1398 bytes, more fragments will follow
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:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=9
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=6) - Flags 0x00
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read finished A
SSL: SSL_connect - want more data
SSL: 158 bytes left to be sent out (of total 2954 bytes)
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:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=13 id=10
EAP: EAP entering state METHOD
EAP-TLS: Received packet(len=53) - Flags 0x80
EAP-TLS: TLS Message Length: 43
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 read finished A
SSL: (where=0x20 ret=0x1)
SSL: (where=0x1002 ret=0x1)
SSL: No data to be sent out
EAP-TLS: Done
EAP-TLS: Derived key - hexdump(len=64): 64 6c 4a ab 01 26 b1 2d 6f ca
af ed 16 43 a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8 d4 aa 29 41 70
99 17 be 03 5a 57 53 f3 45 7e f8 1e 31 1f 17 2b 8d b7 f0 f7 62 d2 f8
76 1a a7 f5 c4 92 d6 fd
SSL: Building ACK
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 57, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state SUCCESS
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:0c:85:71:6e:a8
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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
WPA: Renewed SNonce - hexdump(len=32): c1 69 a1 b0 c4 66 f8 ec e0 b6
bd 00 0c 29 af 93 42 65 0c 92 95 5c 51 b7 b3 35 9c bf 7f da 28 80
WPA: PMK from EAPOL state machines - hexdump(len=32): 64 6c 4a ab 01
26 b1 2d 6f ca af ed 16 43 a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8
d4 aa 29 41
WPA: PMK - hexdump(len=32): 64 6c 4a ab 01 26 b1 2d 6f ca af ed 16 43
a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8 d4 aa 29 41
WPA: PTK - hexdump(len=64): 2f a1 50 f6 97 5b 99 fb fb c2 41 55 c7 74
b5 fe 9c da 2c 9f af e7 c7 41 fd b0 89 d9 10 7a 58 04 ff 1f 38 8a 6c
9b 69 45 6a a1 4c d7 f2 2e a5 f0 8c 13 24 d4 1e 9d 47 03 ce db 51 bf
d2 63 68 43
WPA: EAPOL-Key MIC - hexdump(len=16): 1e 36 e6 7b 29 90 e2 4c 4c 06 33
96 d0 ad e6 90
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0c:85:71:6e:a8
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 message 3 of 4-Way Handshake from 00:0c:85:71:6e:a8 (ver=1)
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
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
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

Regards,
yj.



From michaelr  Sun Nov 14 21:59:28 2004
From: michaelr (Michael Reilly)
Date: Sun, 14 Nov 2004 21:59:28 -0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <32653c9704111419282a884c71@mail.gmail.com>
References: <32653c9704111419282a884c71@mail.gmail.com>
Message-ID: <419845C0.1040903@cisco.com>

This is a well documented problem.  Atheros cards fail with madwifi and 
ndiswrapper.  They work fine with driverloader.  I have not seen an 
explanation for the problem nor any determination as to whether the problem 
is in madwifi and ndiswrapper or it is in wpa_supplicant.

Based on your message it sounds like a change made to madwifi since the 
middle of August caused the problem.  Perhaps a similar change was made to 
ndiswrapper.

michael

YenJung Chang wrote:
> Hi, list,
> 
> I had tried the wpa_supplicant 0.25 with the madwifi checked out on
> the middle of August,  the EAP-PEAP and EPA-TLS are both worked fine,
> however, the wpa_supplicant 0.25 is not worked with the latest
> madwifi, which I checked out at Nov 15; the state machine stoped after
> sended EAPOL-Key 4/4.
> 
> Following are my configure file and log, please help me.
> Any advice is appreciated.
> 
> Configure file(wpa_supplicant.conf)
> ===========================================
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> 
>  network={
>        ssid="1200b"
>        key_mgmt=WPA-EAP
>        pairwise=CCMP TKIP
>        group=CCMP TKIP
>        eap=TLS
>        identity="spencer"
>        ca_cert="/etc/ssl/certs/netgearca.pem"
>        client_cert="/etc/ssl/certs/netgear-mycert.pem"
>        private_key="/etc/ssl/certs/netgear-mykey.pem"
>        private_key_password="Ss=1234"
>        priority=1
>  }
> 
> 
> Log
> ===========================================
> 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 1
>    id=0 ssid='1200b'
> 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_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
> Starting AP scan (broadcast SSID)
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 3091 bytes of scan results (15 BSSes)
> Scan results: 15
> Selecting BSS from priority group 1
> 0: 00:0f:b5:10:a5:38 ssid='davidv3' wpa_ie_len=26 rsn_ie_len=0
>    skip - SSID mismatch
> 1: 00:30:ab:99:99:9c ssid='Broadcom3-91-7-0' wpa_ie_len=0 rsn_ie_len=26
>    skip - SSID mismatch
> 2: 00:0f:b5:0f:cd:8b ssid='3119g' wpa_ie_len=24 rsn_ie_len=0
>    skip - SSID mismatch
> 3: 00:0c:85:71:6e:a8 ssid='1200b' wpa_ie_len=24 rsn_ie_len=0
>    selected
> Trying to associate with 00:0c:85:71:6e:a8 (SSID='1200b' freq=2437 MHz)
> Cancelling scan request
> WPA: using IEEE 802.11i/D3.0
> 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
> 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
> 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=18
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:0c:85:71:6e:a8
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
> 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
> 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
> RX EAPOL from 00:0c:85:71:6e:a8
> 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=7):
>      73 70 65 6e 63 65 72                              spencer         
> 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:0c:85:71:6e:a8
> 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=7):
>      73 70 65 6e 63 65 72                              spencer         
> 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:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=3
> EAP: EAP entering state GET_METHOD
> SSL: Trusted root certificate(s) loaded
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=6) - Flags 0x20
> EAP-TLS: Start
> SSL: (where=0x10 ret=0x1)
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:before/connect initialization
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write client hello A
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read server hello A
> SSL: SSL_connect - want more data
> SSL: 100 bytes left to be sent out (of total 100 bytes)
> 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:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=4
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=1396) - Flags 0xc0
> EAP-TLS: TLS Message Length: 4723
> SSL: Need 3337 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=5
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=1396) - Flags 0x40
> SSL: Need 1947 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=6
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=1396) - Flags 0x40
> SSL: Need 557 bytes more input data
> SSL: Building ACK
> 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
> IEEE 802.1X RX: version=1 type=0 length=1396
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=7
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=563) - Flags 0x00
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server hello A
> SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=1
> buf='/DC=com/DC=GUI/CN=Netgear CA'
> SSL: eap_tls_verify_cb - preverify_ok=1 err=0 (ok) depth=0
> buf='/CN=dni-9j5p6pp7hnj.GUI.com'
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server certificate A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server certificate request A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read server done A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write client certificate A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write client key exchange A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write certificate verify A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write change cipher spec A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 write finished A
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 flush data
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read finished A
> SSL: SSL_connect - want more data
> SSL: 2954 bytes left to be sent out (of total 2954 bytes)
> SSL: sending 1398 bytes, more fragments will follow
> 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
> IEEE 802.1X RX: version=1 type=0 length=563
> WPA: EAPOL frame (type 0) discarded, not a Key frame
> RX EAPOL from 00:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=8
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=6) - Flags 0x00
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read finished A
> SSL: SSL_connect - want more data
> SSL: 1556 bytes left to be sent out (of total 2954 bytes)
> SSL: sending 1398 bytes, more fragments will follow
> 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:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=9
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=6) - Flags 0x00
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read finished A
> SSL: SSL_connect - want more data
> SSL: 158 bytes left to be sent out (of total 2954 bytes)
> 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:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Request method=13 id=10
> EAP: EAP entering state METHOD
> EAP-TLS: Received packet(len=53) - Flags 0x80
> EAP-TLS: TLS Message Length: 43
> SSL: (where=0x1001 ret=0x1)
> SSL: SSL_connect:SSLv3 read finished A
> SSL: (where=0x20 ret=0x1)
> SSL: (where=0x1002 ret=0x1)
> SSL: No data to be sent out
> EAP-TLS: Done
> EAP-TLS: Derived key - hexdump(len=64): 64 6c 4a ab 01 26 b1 2d 6f ca
> af ed 16 43 a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8 d4 aa 29 41 70
> 99 17 be 03 5a 57 53 f3 45 7e f8 1e 31 1f 17 2b 8d b7 f0 f7 62 d2 f8
> 76 1a a7 f5 c4 92 d6 fd
> SSL: Building ACK
> 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 57, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> EAPOL: Received EAP-Packet frame
> EAPOL: SUPP_BE entering state REQUEST
> EAPOL: getSuppRsp
> EAP: EAP entering state RECEIVED
> EAP: Received EAP-Success
> EAP: EAP entering state SUCCESS
> EAPOL: SUPP_BE entering state RECEIVE
> EAPOL: SUPP_BE entering state SUCCESS
> EAPOL: SUPP_BE entering state IDLE
> WPA: EAPOL frame too short, len 46, expecting at least 99
> RX EAPOL from 00:0c:85:71:6e:a8
> 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 message 1 of 4-Way Handshake from 00:0c:85:71:6e:a8 (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 01
> WPA: Renewed SNonce - hexdump(len=32): c1 69 a1 b0 c4 66 f8 ec e0 b6
> bd 00 0c 29 af 93 42 65 0c 92 95 5c 51 b7 b3 35 9c bf 7f da 28 80
> WPA: PMK from EAPOL state machines - hexdump(len=32): 64 6c 4a ab 01
> 26 b1 2d 6f ca af ed 16 43 a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8
> d4 aa 29 41
> WPA: PMK - hexdump(len=32): 64 6c 4a ab 01 26 b1 2d 6f ca af ed 16 43
> a6 b7 cf 80 61 d8 9a 80 87 93 6b 5e 89 e8 d4 aa 29 41
> WPA: PTK - hexdump(len=64): 2f a1 50 f6 97 5b 99 fb fb c2 41 55 c7 74
> b5 fe 9c da 2c 9f af e7 c7 41 fd b0 89 d9 10 7a 58 04 ff 1f 38 8a 6c
> 9b 69 45 6a a1 4c d7 f2 2e a5 f0 8c 13 24 d4 1e 9d 47 03 ce db 51 bf
> d2 63 68 43
> WPA: EAPOL-Key MIC - hexdump(len=16): 1e 36 e6 7b 29 90 e2 4c 4c 06 33
> 96 d0 ad e6 90
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:0c:85:71:6e:a8
> 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 message 3 of 4-Way Handshake from 00:0c:85:71:6e:a8 (ver=1)
> WPA: Sending EAPOL-Key 4/4
> WPA: Installing PTK to the driver.
> WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
> wpa_driver_madwifi_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
> 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
> 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
> 
> Regards,
> yj.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From capacity77  Mon Nov 15 06:41:37 2004
From: capacity77 (capacity77 at tin.it)
Date: Mon, 15 Nov 2004 15:41:37 +0100
Subject: cards
In-Reply-To: <4194F952.3000301@nerim.net>
Message-ID: <41538C5B0003BE52@ims6a.cp.tin.it>

Hi!
I'm trying to make hostap work for a special study in my university, there
are a few different wireless cards I can use but till now I've been unlucky
because I've tried the dwl650+ and the Netgear WG311v2 that seem not to
be based on the Prism chipset. Today I found a Lucent Orinoco Gold but before
starting installing it, I'd like to be sure if it will support the hostap
mode or not. 
Is there a list of the supported cards? I found a list on 
http://wiki.personaltelco.net/index.cgi/Prism2Card
but unfortunately either this Orinoco is not present, can I be sure it isn't
good for me?
Thanks for your info
Dom


>-- Messaggio originale --
>Date: Fri, 12 Nov 2004 18:56:34 +0100
>From: Colas GRONIER <cgronier at nerim.net>
>To: capacity77 at tin.it
>Subject: Re: netgear
>
>
>Your Netgear WG311v2  is not based  on an Intersil Prism chipset so you

>can not use it with hostap..
>
>Andre Barr give you the link to find a linux driver for the TI ACX100 
>Based Wireless card :
>
>On Wednesday 10 November 2004 09:33 am, capacity77 at tin.it wrote:
>
> >> Hi there!
> >> do you know if hostap works with the Netgear WG311v2 PCI wireless card?
> >> And which driver it uses?
> >> Thanks a lot
> >> Dom
>
>
>A Google search seems to indicate this card has an ACX111 chipset by TI.
>If
>you are just looking for client drivers, you may want to check out:
>
>http://acx100.sourceforge.net/
>
>Andrew
>
>
>capacity77 at tin.it wrote:
>> I'm to make the Netgear WG311v2 PCI wireless card work with hostap.
>> I'm only able to load hostap_cs so I guess it works with this module
but
>> the README says I have to add the card model to hostap_cs.conf in order
>> to get
>> the driver started.
>> What should I exactly do?
>> Thanks!
>> Dom
>> 
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>> 





From zen_hacker  Mon Nov 15 06:57:42 2004
From: zen_hacker (Brian Sturgill)
Date: Mon, 15 Nov 2004 14:57:42 +0000
Subject: cards
Message-ID: <BAY13-F6m6kwViaaskj00014f72@hotmail.com>

Orinoco cards are not supported by the Hostap driver.

>From: capacity77 at tin.it
>To: "Colas GRONIER" <cgronier at nerim.net>, hostap at shmoo.com
>Subject: cards
>Date: Mon, 15 Nov 2004 15:41:37 +0100
>
>Hi!
>I'm trying to make hostap work for a special study in my university, there
>are a few different wireless cards I can use but till now I've been unlucky
>because I've tried the dwl650+ and the Netgear WG311v2 that seem not to
>be based on the Prism chipset. Today I found a Lucent Orinoco Gold but 
>before
>starting installing it, I'd like to be sure if it will support the hostap
>mode or not.
>Is there a list of the supported cards? I found a list on
>http://wiki.personaltelco.net/index.cgi/Prism2Card
>but unfortunately either this Orinoco is not present, can I be sure it 
>isn't
>good for me?
>Thanks for your info
>Dom
>
>
> >-- Messaggio originale --
> >Date: Fri, 12 Nov 2004 18:56:34 +0100
> >From: Colas GRONIER <cgronier at nerim.net>
> >To: capacity77 at tin.it
> >Subject: Re: netgear
> >
> >
> >Your Netgear WG311v2  is not based  on an Intersil Prism chipset so you
>
> >can not use it with hostap..
> >
> >Andre Barr give you the link to find a linux driver for the TI ACX100
> >Based Wireless card :
> >
> >On Wednesday 10 November 2004 09:33 am, capacity77 at tin.it wrote:
> >
> > >> Hi there!
> > >> do you know if hostap works with the Netgear WG311v2 PCI wireless 
>card?
> > >> And which driver it uses?
> > >> Thanks a lot
> > >> Dom
> >
> >
> >A Google search seems to indicate this card has an ACX111 chipset by TI.
> >If
> >you are just looking for client drivers, you may want to check out:
> >
> >http://acx100.sourceforge.net/
> >
> >Andrew
> >
> >
> >capacity77 at tin.it wrote:
> >> I'm to make the Netgear WG311v2 PCI wireless card work with hostap.
> >> I'm only able to load hostap_cs so I guess it works with this module
>but
> >> the README says I have to add the card model to hostap_cs.conf in order
> >> to get
> >> the driver started.
> >> What should I exactly do?
> >> Thanks!
> >> Dom
> >>
> >> _______________________________________________
> >> 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 openapproject  Mon Nov 15 09:22:19 2004
From: openapproject (gaurav dawra)
Date: Mon, 15 Nov 2004 17:22:19 +0000
Subject: cards
Message-ID: <BAY24-F26d4gmSknvh700096f44@hotmail.com>

hi!

Cards which are based on Prism 2/2.5 chipset are supported by hostap. I use 
hostap driver for cards like Senao NL2511 CD EXT2 PLUS, linksys WPC11, 
netgear MA401. You can get all these from amazon.com

Hope this help!!
--Gaurav

>From: capacity77 at tin.it
>To: "Colas GRONIER" <cgronier at nerim.net>, hostap at shmoo.com
>Subject: cards
>Date: Mon, 15 Nov 2004 15:41:37 +0100
>
>Hi!
>I'm trying to make hostap work for a special study in my university, there
>are a few different wireless cards I can use but till now I've been unlucky
>because I've tried the dwl650+ and the Netgear WG311v2 that seem not to
>be based on the Prism chipset. Today I found a Lucent Orinoco Gold but 
>before
>starting installing it, I'd like to be sure if it will support the hostap
>mode or not.
>Is there a list of the supported cards? I found a list on
>http://wiki.personaltelco.net/index.cgi/Prism2Card
>but unfortunately either this Orinoco is not present, can I be sure it 
>isn't
>good for me?
>Thanks for your info
>Dom
>
>
> >-- Messaggio originale --
> >Date: Fri, 12 Nov 2004 18:56:34 +0100
> >From: Colas GRONIER <cgronier at nerim.net>
> >To: capacity77 at tin.it
> >Subject: Re: netgear
> >
> >
> >Your Netgear WG311v2  is not based  on an Intersil Prism chipset so you
>
> >can not use it with hostap..
> >
> >Andre Barr give you the link to find a linux driver for the TI ACX100
> >Based Wireless card :
> >
> >On Wednesday 10 November 2004 09:33 am, capacity77 at tin.it wrote:
> >
> > >> Hi there!
> > >> do you know if hostap works with the Netgear WG311v2 PCI wireless 
>card?
> > >> And which driver it uses?
> > >> Thanks a lot
> > >> Dom
> >
> >
> >A Google search seems to indicate this card has an ACX111 chipset by TI.
> >If
> >you are just looking for client drivers, you may want to check out:
> >
> >http://acx100.sourceforge.net/
> >
> >Andrew
> >
> >
> >capacity77 at tin.it wrote:
> >> I'm to make the Netgear WG311v2 PCI wireless card work with hostap.
> >> I'm only able to load hostap_cs so I guess it works with this module
>but
> >> the README says I have to add the card model to hostap_cs.conf in order
> >> to get
> >> the driver started.
> >> What should I exactly do?
> >> Thanks!
> >> Dom
> >>
> >> _______________________________________________
> >> 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

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From x-hostap  Mon Nov 15 15:52:46 2004
From: x-hostap (Steven Ihde)
Date: Mon, 15 Nov 2004 15:52:46 -0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <419845C0.1040903@cisco.com>
References: <32653c9704111419282a884c71@mail.gmail.com>
	<419845C0.1040903@cisco.com>
Message-ID: <20041115235246.GA23863@hamachi.dyndns.org>

On Sun, 14 Nov 2004 21:59:28 -0800, Michael Reilly wrote:
> This is a well documented problem.  Atheros cards fail with madwifi and 
> ndiswrapper.  They work fine with driverloader.  I have not seen an 
> explanation for the problem nor any determination as to whether the problem 
> is in madwifi and ndiswrapper or it is in wpa_supplicant.
> 
> Based on your message it sounds like a change made to madwifi since the 
> middle of August caused the problem.  Perhaps a similar change was made to 
> ndiswrapper.
[snip]

I'm successfully using an Atheros-based DLink DWL-G650 with madwifi
(checked out mid-October) and wpa_supplicant 0.2.5 (Debian 0.2.5-2)
with Debian unstable with kernel 2.6.8.  The AP is a Netgear FWG114P,
and I'm using WPA-PSK.  So it would seem your statement that "Atheros
cards fail with madwifi" needs further qualification.

I must admit that there are good days and bad days -- sometimes
wpa_supplicant spends upwards of a minute "Trying to associate" every
time it rekeys, and other days it works great.  But fundamentally, it
works.

I've been meaning to figure out why it's so inconsistent.  The obvious
answer is poor signal strength or interference, but this only seems to
happen when rekeying and I often sit in a spot with a clear line of
sight to the AP less than 50ft away and the signal strength seems
good.  I had much better results with a Linksys AP, but my wife's
PowerBook's AirPort card didn't get along with the Linksys, so we use
the Netgear :-)

-Steve




From shawn_adams  Mon Nov 15 16:11:50 2004
From: shawn_adams (Shawn Adams)
Date: Tue, 16 Nov 2004 01:11:50 +0100
Subject: wpa_supplicant 0.2.5 compilation fail
In-Reply-To: <20041115235246.GA23863@hamachi.dyndns.org>
References: <32653c9704111419282a884c71@mail.gmail.com>	<419845C0.1040903@cisco.com>
	<20041115235246.GA23863@hamachi.dyndns.org>
Message-ID: <419945C6.2010902@web.de>

Hello,

Perhaps I'm missing some vital docs, or something is not clear for me.

Objective is to get wpa_supplicant to act as a SUPPLICANT for a CLIENT 
wireless card, to allow this CLIENT to attach to an existing access 
point. I do not want this Linux PC to act as an access point.

Platform happens to be Suse 8.2.
Madwifi drivers work wonderfully with an Athlon based PCMCIA card.

 From the README, and associated docs, it is clear that wpa_supplicant 
supports a Hermes driver, from other pieces, appears this Hermes code is 
REQUIRED. The .config docs suggest this Hermes is just one of many 
possible interfaces that might be disabled by editing the .config.

When I compile wpa_supplicant, it appears the Hermes code is somehow 
needed by other code.(seems regardless of settings in .config)

make: *** No rule to make target `driver_hermes.o', needed by 
`wpa_supplicant'.  Stop.


Can anyone clarify :
1. is this Hermes code required ?
2. if yes, exactly which piece of code must one download ?


Thanks very much in advance



-- 
Shawn Adams





From michaelr  Mon Nov 15 17:50:21 2004
From: michaelr (Michael Reilly)
Date: Mon, 15 Nov 2004 17:50:21 -0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <20041115235246.GA23863@hamachi.dyndns.org>
References: <32653c9704111419282a884c71@mail.gmail.com>
	<419845C0.1040903@cisco.com>
	<20041115235246.GA23863@hamachi.dyndns.org>
Message-ID: <41995CDD.3040308@cisco.com>

I am using a 2.4.26 kernel.  That may be the difference.  I have not heard 
of anyone able to get madwifi from October or later and wpa_supplicant 2.5 
working on an Atheros card with a 2.4.2?.  Same with ndiswrapper 0.11.  I 
took a look at ndiswrapper 0.12rc1 but it appears to not compile with a 
2.4.26 kernel.

So the people I know and myself who use Atheros cards are forced to use 
driverloader at this time or try upgrading to a 2.6.x kernel and see if that 
works.

michael
Steven Ihde wrote:
> On Sun, 14 Nov 2004 21:59:28 -0800, Michael Reilly wrote:
> 
>>This is a well documented problem.  Atheros cards fail with madwifi and 
>>ndiswrapper.  They work fine with driverloader.  I have not seen an 
>>explanation for the problem nor any determination as to whether the problem 
>>is in madwifi and ndiswrapper or it is in wpa_supplicant.
>>
>>Based on your message it sounds like a change made to madwifi since the 
>>middle of August caused the problem.  Perhaps a similar change was made to 
>>ndiswrapper.
> 
> [snip]
> 
> I'm successfully using an Atheros-based DLink DWL-G650 with madwifi
> (checked out mid-October) and wpa_supplicant 0.2.5 (Debian 0.2.5-2)
> with Debian unstable with kernel 2.6.8.  The AP is a Netgear FWG114P,
> and I'm using WPA-PSK.  So it would seem your statement that "Atheros
> cards fail with madwifi" needs further qualification.
> 
> I must admit that there are good days and bad days -- sometimes
> wpa_supplicant spends upwards of a minute "Trying to associate" every
> time it rekeys, and other days it works great.  But fundamentally, it
> works.
> 
> I've been meaning to figure out why it's so inconsistent.  The obvious
> answer is poor signal strength or interference, but this only seems to
> happen when rekeying and I often sit in a spot with a clear line of
> sight to the AP less than 50ft away and the signal strength seems
> good.  I had much better results with a Linksys AP, but my wife's
> PowerBook's AirPort card didn't get along with the Linksys, so we use
> the Netgear :-)
> 
> -Steve

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From jkmaline  Mon Nov 15 17:59:43 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 15 Nov 2004 17:59:43 -0800
Subject: wpa_supplicant 0.2.5 compilation fail
In-Reply-To: <419945C6.2010902@web.de>
References: <32653c9704111419282a884c71@mail.gmail.com>
	<419845C0.1040903@cisco.com>
	<20041115235246.GA23863@hamachi.dyndns.org>
	<419945C6.2010902@web.de>
Message-ID: <20041116015943.GA7450@jm.kir.nu>

On Tue, Nov 16, 2004 at 01:11:50AM +0100, Shawn Adams wrote:

> Platform happens to be Suse 8.2.
> Madwifi drivers work wonderfully with an Athlon based PCMCIA card.

So, you are using madwifi driver..

> From the README, and associated docs, it is clear that wpa_supplicant 
> supports a Hermes driver, from other pieces, appears this Hermes code is 
> REQUIRED. The .config docs suggest this Hermes is just one of many 
> possible interfaces that might be disabled by editing the .config.

But why are you trying to use Hermer driver interface?? Please let me
know what led to this conclusion so that I can improve documentation to
make this more clear. Hermer driver interface is used only if you are
using Hermer driver, which you are not.. If you are using madwifi
driver, you should use madwifi driver interface.

> Can anyone clarify :
> 1. is this Hermes code required ?

No.

> 2. if yes, exactly which piece of code must one download ?

Did you read the README file in wpa_supplicant package?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 15 18:02:37 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 15 Nov 2004 18:02:37 -0800
Subject: Hostap & 2.6.10-rc1-mm5 kernel
In-Reply-To: <4197BC24.6070209@pcuf.fi>
References: <4197BC24.6070209@pcuf.fi>
Message-ID: <20041116020237.GB7450@jm.kir.nu>

On Sun, Nov 14, 2004 at 10:12:20PM +0200, jar wrote:

> Hostap driver seems to be included to the 2.6.10-rc1-mm5 kernel. Is it 
> possible to add the version numbers to the hostap modules. So that users 
> can easily check by using modinfo which version is currently included in 
> the kernel?

At the moment, it is not that clear what the version number would
indicate or what it should be. The current code in wireless-2.6 (and
-mm) is osmething that is close to current CVS development branch (which
does not really have any version number), but it is not identical to
this.. What would you like to learn from the version number?

-- 
Jouni Malinen                                            PGP id EFC895FA



From yenjung  Mon Nov 15 19:55:09 2004
From: yenjung (YenJung Chang)
Date: Tue, 16 Nov 2004 11:55:09 +0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <41995CDD.3040308@cisco.com>
References: <32653c9704111419282a884c71@mail.gmail.com>
	<419845C0.1040903@cisco.com>
	<20041115235246.GA23863@hamachi.dyndns.org>
	<41995CDD.3040308@cisco.com>
Message-ID: <32653c970411151955f45a170@mail.gmail.com>

I never try to compile the madwifi on 2.4.26. The kernel I used for
wpa_supplicant 2.5 and madwifi from Nov 9 is 2.4.25.
It is working fine after I re-compile the wpa_supplicant with the
madwifi from Nov 9.
I guess it also could be working fine with 2.4.26.

yj.


On Mon, 15 Nov 2004 17:50:21 -0800, Michael Reilly <michaelr at cisco.com> wrote:
> I am using a 2.4.26 kernel.  That may be the difference.  I have not heard
> of anyone able to get madwifi from October or later and wpa_supplicant 2.5
> working on an Atheros card with a 2.4.2?.  Same with ndiswrapper 0.11.  I
> took a look at ndiswrapper 0.12rc1 but it appears to not compile with a
> 2.4.26 kernel.
> 
> So the people I know and myself who use Atheros cards are forced to use
> driverloader at this time or try upgrading to a 2.6.x kernel and see if that
> works.
> 
> michael
> 
> 
> Steven Ihde wrote:
> > On Sun, 14 Nov 2004 21:59:28 -0800, Michael Reilly wrote:
> >
> >>This is a well documented problem.  Atheros cards fail with madwifi and
> >>ndiswrapper.  They work fine with driverloader.  I have not seen an
> >>explanation for the problem nor any determination as to whether the problem
> >>is in madwifi and ndiswrapper or it is in wpa_supplicant.
> >>
> >>Based on your message it sounds like a change made to madwifi since the
> >>middle of August caused the problem.  Perhaps a similar change was made to
> >>ndiswrapper.
> >
> > [snip]
> >
> > I'm successfully using an Atheros-based DLink DWL-G650 with madwifi
> > (checked out mid-October) and wpa_supplicant 0.2.5 (Debian 0.2.5-2)
> > with Debian unstable with kernel 2.6.8.  The AP is a Netgear FWG114P,
> > and I'm using WPA-PSK.  So it would seem your statement that "Atheros
> > cards fail with madwifi" needs further qualification.
> >
> > I must admit that there are good days and bad days -- sometimes
> > wpa_supplicant spends upwards of a minute "Trying to associate" every
> > time it rekeys, and other days it works great.  But fundamentally, it
> > works.
> >
> > I've been meaning to figure out why it's so inconsistent.  The obvious
> > answer is poor signal strength or interference, but this only seems to
> > happen when rekeying and I often sit in a spot with a clear line of
> > sight to the AP less than 50ft away and the signal strength seems
> > good.  I had much better results with a Linksys AP, but my wife's
> > PowerBook's AirPort card didn't get along with the Linksys, so we use
> > the Netgear :-)
> >
> > -Steve
> 
> --
> ---- ---- ----
> Michael Reilly    michaelr at cisco.com
>      Cisco Systems,  California
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jar  Tue Nov 16 00:40:03 2004
From: jar (Jar)
Date: Tue, 16 Nov 2004 10:40:03 +0200 (EET)
Subject: Hostap & 2.6.10-rc1-mm5 kernel
In-Reply-To: <20041116020237.GB7450@jm.kir.nu>
References: <4197BC24.6070209@pcuf.fi> <20041116020237.GB7450@jm.kir.nu>
Message-ID: <43281.194.157.0.2.1100594403.squirrel@194.157.0.2>


> On Sun, Nov 14, 2004 at 10:12:20PM +0200, jar wrote:
>
>> Hostap driver seems to be included to the 2.6.10-rc1-mm5 kernel. Is it
>> possible to add the version numbers to the hostap modules. So that users
>> can easily check by using modinfo which version is currently included in
>> the kernel?
>
> At the moment, it is not that clear what the version number would
> indicate or what it should be. The current code in wireless-2.6 (and
> -mm) is osmething that is close to current CVS development branch (which
> does not really have any version number), but it is not identical to
> this.. What would you like to learn from the version number?

In the future, I don't know what is the updating speed in the kernel driver and your
separate stable version (*.tar.gz). If the kernel version is updating slower than
the separate package you could check the version number of the kernel module. Maybe
the version number will tell something what to expect the driver; bugs corrected in
newer version, new features added, etc. But if the kernel version is always more or
less the same that the current stable package, then the version number is not needed
I guess.

BR.
-- 
Best Regards, Jar



From michaelr  Tue Nov 16 01:34:51 2004
From: michaelr (Michael Reilly)
Date: Tue, 16 Nov 2004 01:34:51 -0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <32653c970411151955f45a170@mail.gmail.com>
References: <32653c9704111419282a884c71@mail.gmail.com>	
	<419845C0.1040903@cisco.com>	
	<20041115235246.GA23863@hamachi.dyndns.org>	
	<41995CDD.3040308@cisco.com>
	<32653c970411151955f45a170@mail.gmail.com>
Message-ID: <4199C9BB.4060803@cisco.com>

I will upgrade from cvs tonight and see if I can get it to work.  I upgraded 
  around the 5th of November.

michael

YenJung Chang wrote:
> I never try to compile the madwifi on 2.4.26. The kernel I used for
> wpa_supplicant 2.5 and madwifi from Nov 9 is 2.4.25.
> It is working fine after I re-compile the wpa_supplicant with the
> madwifi from Nov 9.
> I guess it also could be working fine with 2.4.26.
> 
> yj.
> 
> 
> On Mon, 15 Nov 2004 17:50:21 -0800, Michael Reilly <michaelr at cisco.com> wrote:
> 
>>I am using a 2.4.26 kernel.  That may be the difference.  I have not heard
>>of anyone able to get madwifi from October or later and wpa_supplicant 2.5
>>working on an Atheros card with a 2.4.2?.  Same with ndiswrapper 0.11.  I
>>took a look at ndiswrapper 0.12rc1 but it appears to not compile with a
>>2.4.26 kernel.
>>
>>So the people I know and myself who use Atheros cards are forced to use
>>driverloader at this time or try upgrading to a 2.6.x kernel and see if that
>>works.
>>
>>michael
>>
>>
>>Steven Ihde wrote:
>>
>>>On Sun, 14 Nov 2004 21:59:28 -0800, Michael Reilly wrote:
>>>
>>>
>>>>This is a well documented problem.  Atheros cards fail with madwifi and
>>>>ndiswrapper.  They work fine with driverloader.  I have not seen an
>>>>explanation for the problem nor any determination as to whether the problem
>>>>is in madwifi and ndiswrapper or it is in wpa_supplicant.
>>>>
>>>>Based on your message it sounds like a change made to madwifi since the
>>>>middle of August caused the problem.  Perhaps a similar change was made to
>>>>ndiswrapper.
>>>
>>>[snip]
>>>
>>>I'm successfully using an Atheros-based DLink DWL-G650 with madwifi
>>>(checked out mid-October) and wpa_supplicant 0.2.5 (Debian 0.2.5-2)
>>>with Debian unstable with kernel 2.6.8.  The AP is a Netgear FWG114P,
>>>and I'm using WPA-PSK.  So it would seem your statement that "Atheros
>>>cards fail with madwifi" needs further qualification.
>>>
>>>I must admit that there are good days and bad days -- sometimes
>>>wpa_supplicant spends upwards of a minute "Trying to associate" every
>>>time it rekeys, and other days it works great.  But fundamentally, it
>>>works.
>>>
>>>I've been meaning to figure out why it's so inconsistent.  The obvious
>>>answer is poor signal strength or interference, but this only seems to
>>>happen when rekeying and I often sit in a spot with a clear line of
>>>sight to the AP less than 50ft away and the signal strength seems
>>>good.  I had much better results with a Linksys AP, but my wife's
>>>PowerBook's AirPort card didn't get along with the Linksys, so we use
>>>the Netgear :-)
>>>
>>>-Steve
>>
>>--
>>---- ---- ----
>>Michael Reilly    michaelr at cisco.com
>>     Cisco Systems,  California
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From Al_Smolkin  Tue Nov 16 13:51:20 2004
From: Al_Smolkin (Al Smolkin)
Date: Tue, 16 Nov 2004 16:51:20 -0500
Subject: Hostap on FC2
Message-ID: <20041116215051.03DF11A020B@smtp-1.hotpop.com>

Need help getting hostap to work with NEAT (RedHat GUI network config tool).

Right now window manager freezes upon trying to select Mode.

Here's the output of iwconfig immed after service pcmcia restart

eth0      IEEE 802.11b  ESSID:"test"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:04:E2:80:90:79  
          Bit Rate:11Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:0   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"test"  
          Mode:Master  Frequency:2.422GHz  Access Point: 00:04:E2:80:90:79  
          Bit Rate:11Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:0   Missed beacon:0


It's a kernel 2.6.8-1.521
The card is SMC 2532W-B EliteConnect, and yes, I've listed it in hostap_cs.conf with manfid and bind.


Thanks to all

Al






From shawn_adams  Tue Nov 16 13:53:41 2004
From: shawn_adams (Shawn Adams)
Date: Tue, 16 Nov 2004 22:53:41 +0100
Subject: wpa_supplicant 0.2.5 compilation fail
In-Reply-To: <20041116015943.GA7450@jm.kir.nu>
References: <32653c9704111419282a884c71@mail.gmail.com>	<419845C0.1040903@cisco.com>	<20041115235246.GA23863@hamachi.dyndns.org>	<419945C6.2010902@web.de>
	<20041116015943.GA7450@jm.kir.nu>
Message-ID: <419A76E5.6070609@web.de>



Jouni,

thanks for your response.

The only tip on the docs I can offer is in discussing the ".config" 
file, it would be logical that if:

CONFIG_DRIVER_HERMES=y

enables the option, that:

CONFIG_DRIVER_HERMES=n

disables the option.  I would state clearly that one must remove the 
option line.

now onto the next hop.


thanks again


Jouni Malinen wrote:
> On Tue, Nov 16, 2004 at 01:11:50AM +0100, Shawn Adams wrote:
> 
> 
>>Platform happens to be Suse 8.2.
>>Madwifi drivers work wonderfully with an Athlon based PCMCIA card.
> 
> 
> So, you are using madwifi driver..
> 
> 
>>From the README, and associated docs, it is clear that wpa_supplicant 
>>supports a Hermes driver, from other pieces, appears this Hermes code is 
>>REQUIRED. The .config docs suggest this Hermes is just one of many 
>>possible interfaces that might be disabled by editing the .config.
> 
> 
> But why are you trying to use Hermer driver interface?? Please let me
> know what led to this conclusion so that I can improve documentation to
> make this more clear. Hermer driver interface is used only if you are
> using Hermer driver, which you are not.. If you are using madwifi
> driver, you should use madwifi driver interface.
> 
> 
>>Can anyone clarify :
>>1. is this Hermes code required ?
> 
> 
> No.
> 
> 
>>2. if yes, exactly which piece of code must one download ?
> 
> 
> Did you read the README file in wpa_supplicant package?
> 


-- 
Shawn Adams
shawn_adams at web.de




From capacity77  Wed Nov 17 04:25:07 2004
From: capacity77 (capacity77 at tin.it)
Date: Wed, 17 Nov 2004 13:25:07 +0100
Subject: suggest a card
Message-ID: <41538C5B0003EBB7@ims6a.cp.tin.it>

Hi there!
I have to buy a wireless card based on an Intersil Prism chipset to make
hostap work with it.
Which one do you advice me, which one are you using?
Dom.




From padam.singh  Wed Nov 17 04:56:42 2004
From: padam.singh (Padam J Singh)
Date: Wed, 17 Nov 2004 18:26:42 +0530
Subject: intel ipw2100 in AP mode
Message-ID: <419B4A8A.5010704@inventum.cc>

Hi!
Has anyone tested if the intel ipw2100 can be used in AP mode, as in 
host ap?

I have the miniPCI version of this card, and am using it on an Intel IXP 
425 board (big endian).


Any pointers regarding this will help me!

Thanks in advance!

Padam J Singh.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: padam.singh.vcf
Type: text/x-vcard
Size: 327 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041117/f6578ea8/attachment.vcf 


From capacity77  Wed Nov 17 09:42:18 2004
From: capacity77 (capacity77 at tin.it)
Date: Wed, 17 Nov 2004 18:42:18 +0100
Subject: Lucent cards
Message-ID: <41538C5B0003F51B@ims6a.cp.tin.it>

after a long research I found that HostAP may work with Lucent based cards
too.
I have a Lucent based card, is it true that I can make hostap run with this
card?




From st3v3  Wed Nov 17 10:03:11 2004
From: st3v3 (Steve)
Date: Wed, 17 Nov 2004 18:03:11 +0000
Subject: hostap & madwifi with 902.1x & dynamic WEP
Message-ID: <1100714591.25601.17.camel@localhost>

Hey all
I have a SC1100 development board with two radios fitted.
One is prism based the other atheros (5212) based. Both of which Im
confguring to be access points (Master mode).
I have a couple of questions which I hope you can answer.
I am using the 2.4.26 kernel and a CVS snapshot of hostap-driver hostapd
and madwifi all taken on 16/11/04.
Im not sure if this is a madwifi or a hostap related this is my first
port of call. So apologies if you think it should be on the madwifi
list.

Q1/ I have configured hostapd with the .config file for compilation of
the MADWIFI_DRIVER. Which are the correct modules that hostapd requires.
I have not changed anything in the madwifi driver (is this correct),
this is used as is. I have the wlan_xauth module loaded, Is this the
correct module)s_ that hostapd should be using?? 

Q2/ When starting hostapd a WEP key is generated successfully. However
the current transmit key when using iwlist ath0 key does not change. 
Configuration file: /rw/etc/hostapd.ath0.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:02:6f:53:11:74 and ssid
'awap_ap_madwifi'
ath0: RADIUS Authentication server 10.0.0.242:1812
madwifi_set_ieee8021x: enabled=1
madwifi_set_iface_flags: dev_up=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=0
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=2
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=3
IEEE 802.1X: New default WEP key index 2
IEEE 802.1X: New default WEP key - hexdump(len=13): 6b 32 24 1a ed 13 be
2b cf 87 06 91 9b
madwifi_set_key: alg=WEP addr=00:00:00:00:00:00 key_idx=2
Flushing old station entries
Deauthenticate all stations
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=2
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
wrap1C-000DB9000A7C:~# iwlist ath0 key
ath0      3 key sizes : 40, 104, 128bits
          4 keys available :
                [1]: off
                [2]: off
                [3]: 6B32-241A-ED13-BE2B-CF87-0691-9B (104 bits)
                [4]: off
          Current Transmit Key: [1]
          Security mode:open
Tx Key [1] is used which is set to off ?????

The bahaviour for the prism chipset is as follows which I believe to be
correct.
Configuration file: /rw/etc/hostapd.wlan0.conf
Opening raw packet socket for ifindex 8
Using interface wlan0ap with hwaddr 00:20:e0:d0:2a:e5 and ssid
'awap_ap_hostap'
wlan0: RADIUS Authentication server 10.0.0.242:1812
IEEE 802.1X: New default WEP key index 2
IEEE 802.1X: New default WEP key - hexdump(len=13): b2 28 d9 85 92 34 ff
77 df 75 c1 2f 7a
Flushing old station entries
Deauthenticate all stations
wrap1C-000DB9000A7C:~# iwlist wlan0 key
Warning: Driver for device wlan0 recommend version 18 of Wireless
Extension,
but has been compiled with version 16, therefore some driver features
may not be available...
                                                                                                                        
wlan0     2 key sizes : 40, 104bits
          4 keys available :
                [1]: off
                [2]: off
                [3]: B228-D985-9234-FF77-DF75-C12F-7A (104 bits)
                [4]: off
          Current Transmit Key: [3]
          Security mode:open

Ive noted the warning for wlan0 and wireless extension, but this
interface is working 100% in 802.1x & dynamic keys. 
Can someone explain to me what is happening and why??

Regards
	Steve


-- 
Steve <st3v3 at btinternet.com>




From michaelr  Wed Nov 17 10:10:21 2004
From: michaelr (Michael Reilly)
Date: Wed, 17 Nov 2004 10:10:21 -0800
Subject: Stoped at EPAOL-Key 4/4 in wpa_supplicant 0.25 and latest
	Madwifi
In-Reply-To: <32653c970411151955f45a170@mail.gmail.com>
References: <32653c9704111419282a884c71@mail.gmail.com>	
	<419845C0.1040903@cisco.com>	
	<20041115235246.GA23863@hamachi.dyndns.org>	
	<41995CDD.3040308@cisco.com>
	<32653c970411151955f45a170@mail.gmail.com>
Message-ID: <419B940D.50002@cisco.com>

Updated from the cvs repository yesterday night.  madwifi now works again. 
Only ndiswrapper fails with atheros cards.

michael

YenJung Chang wrote:
> I never try to compile the madwifi on 2.4.26. The kernel I used for
> wpa_supplicant 2.5 and madwifi from Nov 9 is 2.4.25.
> It is working fine after I re-compile the wpa_supplicant with the
> madwifi from Nov 9.
> I guess it also could be working fine with 2.4.26.
> 
> yj.
> 
> 
> On Mon, 15 Nov 2004 17:50:21 -0800, Michael Reilly <michaelr at cisco.com> wrote:
> 
>>I am using a 2.4.26 kernel.  That may be the difference.  I have not heard
>>of anyone able to get madwifi from October or later and wpa_supplicant 2.5
>>working on an Atheros card with a 2.4.2?.  Same with ndiswrapper 0.11.  I
>>took a look at ndiswrapper 0.12rc1 but it appears to not compile with a
>>2.4.26 kernel.
>>
>>So the people I know and myself who use Atheros cards are forced to use
>>driverloader at this time or try upgrading to a 2.6.x kernel and see if that
>>works.
>>
>>michael
>>
>>
>>Steven Ihde wrote:
>>
>>>On Sun, 14 Nov 2004 21:59:28 -0800, Michael Reilly wrote:
>>>
>>>
>>>>This is a well documented problem.  Atheros cards fail with madwifi and
>>>>ndiswrapper.  They work fine with driverloader.  I have not seen an
>>>>explanation for the problem nor any determination as to whether the problem
>>>>is in madwifi and ndiswrapper or it is in wpa_supplicant.
>>>>
>>>>Based on your message it sounds like a change made to madwifi since the
>>>>middle of August caused the problem.  Perhaps a similar change was made to
>>>>ndiswrapper.
>>>
>>>[snip]
>>>
>>>I'm successfully using an Atheros-based DLink DWL-G650 with madwifi
>>>(checked out mid-October) and wpa_supplicant 0.2.5 (Debian 0.2.5-2)
>>>with Debian unstable with kernel 2.6.8.  The AP is a Netgear FWG114P,
>>>and I'm using WPA-PSK.  So it would seem your statement that "Atheros
>>>cards fail with madwifi" needs further qualification.
>>>
>>>I must admit that there are good days and bad days -- sometimes
>>>wpa_supplicant spends upwards of a minute "Trying to associate" every
>>>time it rekeys, and other days it works great.  But fundamentally, it
>>>works.
>>>
>>>I've been meaning to figure out why it's so inconsistent.  The obvious
>>>answer is poor signal strength or interference, but this only seems to
>>>happen when rekeying and I often sit in a spot with a clear line of
>>>sight to the AP less than 50ft away and the signal strength seems
>>>good.  I had much better results with a Linksys AP, but my wife's
>>>PowerBook's AirPort card didn't get along with the Linksys, so we use
>>>the Netgear :-)
>>>
>>>-Steve
>>
>>--
>>---- ---- ----
>>Michael Reilly    michaelr at cisco.com
>>     Cisco Systems,  California
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From david.losada  Wed Nov 17 11:20:19 2004
From: david.losada (DAVID LOSADA CARBALLO)
Date: Wed, 17 Nov 2004 21:20:19 +0200
Subject: wpa_supplicant 0.2.5: succesful key negotiation,
 kicked off by "new AP" event
Message-ID: <d2b214299.14299d2b2@urv.net>

Hello,

I'm using wpa_supplicant 0.2.5 along with Intel ipw2100 drivers (version 1.0) on a linux 2.6.9 kernel on a Gentoo distribution. This against a Buffalo AirStation G54 access point, using a WPA-PSK configuration with AES encryption.

As what i understand from wpa_supplicant debugging output (which i can send directly to anybody willing to help me), wpa_supplicant succesfully finds the wireless LAN and performs the key negotiation:

WPA: Key negotiation completed with 00:07:40:a2:d4:98
Cancelling authentication timeout
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1

immediately after, though, a wireless event is received:

Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:07:40:a2:d4:98

("new AP", maybe still scanning?). In consequence, negotiated keys are cleared and process is kicked off again:

Association event - clear replay counter
Associated to a new BSS: BSSID=00:07:40:a2:d4:98
wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw2100_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw2100_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw2100_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING

result is that i never get a stable connection. Any clues about what to do with this problem, please?

kind regards

David Losada




From amr  Wed Nov 17 11:54:13 2004
From: amr (amrnasr)
Date: Wed, 17 Nov 2004 12:54:13 -0700
Subject: Compact flash memory slot specifications
References: <20041117192154.4B7812BF8B@mail.iocaine.com>
Message-ID: <000701c4ccdf$371bab30$ef05050a@siliconlabs>

Hi all,
Does anyone know from where i can get the specifications of the 
compact flash memory slot ?
Amr



From barr.156  Wed Nov 17 12:27:20 2004
From: barr.156 (Andrew Barr)
Date: Wed, 17 Nov 2004 15:27:20 -0500
Subject: wpa_supplicant 0.2.5: succesful key negotiation,
	kicked off by "new AP" event
In-Reply-To: <d2b214299.14299d2b2@urv.net>
References: <d2b214299.14299d2b2@urv.net>
Message-ID: <200411171527.21446.barr.156@osu.edu>

On Wednesday 17 November 2004 02:20 pm, DAVID LOSADA CARBALLO wrote:
> Hello,
>
> I'm using wpa_supplicant 0.2.5 along with Intel ipw2100 drivers (version
> 1.0) on a linux 2.6.9 kernel on a Gentoo distribution. This against a
> Buffalo AirStation G54 access point, using a WPA-PSK configuration with AES
> encryption.
>
> As what i understand from wpa_supplicant debugging output (which i can send
> directly to anybody willing to help me), wpa_supplicant succesfully finds
> the wireless LAN and performs the key negotiation:
>
> WPA: Key negotiation completed with 00:07:40:a2:d4:98
> Cancelling authentication timeout
> EAPOL: External notification - portValid=1
> EAPOL: External notification - EAP success=1
>
> immediately after, though, a wireless event is received:
>
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:07:40:a2:d4:98
>
> ("new AP", maybe still scanning?). In consequence, negotiated keys are
> cleared and process is kicked off again:
>
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:07:40:a2:d4:98
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state CONNECTING
>
> result is that i never get a stable connection. Any clues about what to do
> with this problem, please?

You need to patch your driver to include this patch:

http://ipw2100.sourceforge.net/patches/ipw2100-0.62-all_patches.patch

It says 0.62 but applies cleanly to 1.0.0. I still can't get it to work 
reliably--I lose the connection shortly before the connection rekeys (I use 
WPA-EAP) and then it comes back after the key negotiation completes.

Andrew

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



From ramalhais  Wed Nov 17 11:28:51 2004
From: ramalhais (Pedro Ramalhais)
Date: Wed, 17 Nov 2004 19:28:51 +0000
Subject: wpa_supplicant 0.2.5: succesful key negotiation, kicked off by
	"new AP" event
In-Reply-To: <d2b214299.14299d2b2@urv.net>
References: <d2b214299.14299d2b2@urv.net>
Message-ID: <1100719731.13803.544.camel@gandalf.uninova.pt>

On Wed, 2004-11-17 at 19:20, DAVID LOSADA CARBALLO wrote:
> Hello,
> 
> I'm using wpa_supplicant 0.2.5 along with Intel ipw2100 drivers (version 1.0) on a linux 2.6.9 kernel on a Gentoo distribution. This against a Buffalo AirStation G54 access point, using a WPA-PSK configuration with AES encryption.
> 
> As what i understand from wpa_supplicant debugging output (which i can send directly to anybody willing to help me), wpa_supplicant succesfully finds the wireless LAN and performs the key negotiation:
> 
> WPA: Key negotiation completed with 00:07:40:a2:d4:98
> Cancelling authentication timeout
> EAPOL: External notification - portValid=1
> EAPOL: External notification - EAP success=1
> 
> immediately after, though, a wireless event is received:
> 
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:07:40:a2:d4:98
> 
> ("new AP", maybe still scanning?). In consequence, negotiated keys are cleared and process is kicked off again:
> 
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:07:40:a2:d4:98
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state CONNECTING
> 
> result is that i never get a stable connection. Any clues about what to do with this problem, please?
> 
> kind regards
> 
> David Losada
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

Hi!
That's a problem with the ipw2100 driver where association events are
delayed (it's a firmware problem), so wpa_supplicant receives packets
before the association event, and when it receives the association event
it resets the keys, making authentication fail.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From ramalhais  Wed Nov 17 15:18:19 2004
From: ramalhais (Pedro Ramalhais)
Date: Wed, 17 Nov 2004 23:18:19 +0000
Subject: wpa_supplicant 0.2.5: succesful key negotiation, kicked off by
	"new AP" event
In-Reply-To: <1100719731.13803.544.camel@gandalf.uninova.pt>
References: <d2b214299.14299d2b2@urv.net>
	<1100719731.13803.544.camel@gandalf.uninova.pt>
Message-ID: <1100733499.20421.2.camel@rootix>

On Wed, 2004-11-17 at 19:28, Pedro Ramalhais wrote:
> On Wed, 2004-11-17 at 19:20, DAVID LOSADA CARBALLO wrote:
> > Hello,
> > 
> > I'm using wpa_supplicant 0.2.5 along with Intel ipw2100 drivers (version 1.0) on a linux 2.6.9 kernel on a Gentoo distribution. This against a Buffalo AirStation G54 access point, using a WPA-PSK configuration with AES encryption.
> > 
> > As what i understand from wpa_supplicant debugging output (which i can send directly to anybody willing to help me), wpa_supplicant succesfully finds the wireless LAN and performs the key negotiation:
> > 
> > WPA: Key negotiation completed with 00:07:40:a2:d4:98
> > Cancelling authentication timeout
> > EAPOL: External notification - portValid=1
> > EAPOL: External notification - EAP success=1
> > 
> > immediately after, though, a wireless event is received:
> > 
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:07:40:a2:d4:98
> > 
> > ("new AP", maybe still scanning?). In consequence, negotiated keys are cleared and process is kicked off again:
> > 
> > Association event - clear replay counter
> > Associated to a new BSS: BSSID=00:07:40:a2:d4:98
> > wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_ipw2100_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_ipw2100_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_ipw2100_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_ipw2100_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
> > EAPOL: External notification - portValid=0
> > EAPOL: External notification - EAP success=0
> > EAPOL: External notification - portEnabled=1
> > EAPOL: SUPP_PAE entering state CONNECTING
> > 
> > result is that i never get a stable connection. Any clues about what to do with this problem, please?
> > 
> > kind regards
> > 
> > David Losada
> > 
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> 
> Hi!
> That's a problem with the ipw2100 driver where association events are
> delayed (it's a firmware problem), so wpa_supplicant receives packets
> before the association event, and when it receives the association event
> it resets the keys, making authentication fail.

Try ipw2100-0.56+wpa eapol patch
Check this script:
http://www.uninova.pt/~pmr/files/WPA/WPA-HOWTO-script.sh

-- 
Pedro Ramalhais <ramalhais at serrado.net>




From gbur  Wed Nov 17 21:21:55 2004
From: gbur (Gunter Burchardt)
Date: Thu, 18 Nov 2004 06:21:55 +0100
Subject: intel ipw2100 in AP mode
In-Reply-To: <419B4A8A.5010704@inventum.cc>
References: <419B4A8A.5010704@inventum.cc>
Message-ID: <20041118052155.GD28407@informatik.uni-rostock.de>

> Has anyone tested if the intel ipw2100 can be used in AP mode, as in 
> host ap?
> 
> I have the miniPCI version of this card, and am using it on an Intel IXP 
> 425 board (big endian).

HostAP only supports prism2/2.5/3 and atheros chipsets for ap mode.
iwp21?? is NOT supported. But there is an interface to add it. Feel
free to implement it :)

regards
gunter



From togg  Thu Nov 18 01:56:22 2004
From: togg (Sebastian Weitzel)
Date: Thu, 18 Nov 2004 10:56:22 +0100 (CET)
Subject: hostap_pci compile problem on 2.6.9 kernel
Message-ID: <4685.213.146.118.69.1100771782.squirrel@213.146.118.69>

Hello,

I get following compile problem on kernel 2.6.9 (gentoo-dev-sources):

make[1]: Entering directory `/usr/src/linux-2.6.9-gentoo-r3'
  CC [M]  /usr/src/hostap/hostap/driver/modules/hostap_pci.o
/usr/src/hostap/hostap/driver/modules/hostap_pci.c: In function
`prism2_pci_suspend':
/usr/src/hostap/hostap/driver/modules/hostap_pci.c:351: error: parse error
before '<<' token
/usr/src/hostap/hostap/driver/modules/hostap_pci.c: In function
`prism2_pci_resume':
/usr/src/hostap/hostap/driver/modules/hostap_pci.c:372: error: parse error
before '<<' token
make[2]: *** [/usr/src/hostap/hostap/driver/modules/hostap_pci.o] Error 1


hostap_plx compiles and runs fine.

Regards,
Sebastian Weitzel




From yenjung  Thu Nov 18 05:35:06 2004
From: yenjung (YenJung Chang)
Date: Thu, 18 Nov 2004 21:35:06 +0800
Subject: play wpa_supplicant and madwifi in bridge mode.
Message-ID: <32653c970411180535453f168@mail.gmail.com>

Hi!

Is there anyone tried to wpa_supplicant(version 0.25) and
madwifi(checked out at Nov.9) in bridge mode?
I had tried two cases:
1: fired up wpa_supplicant, started bridge mode after wpa_supplicant
connected to RADIUS server.
2: started bridge mode then fired up wpa_supplicant.

ps. the bridge mode over here is meant eth0(8130) and ath0(atheros
5212) was putted into br0.

Case 1 was working, at least it could connect to RADIUS server, but
case 2 failed to connect to RADIUS server.

Following is the log of case 2.
Is there anybody know why?

===========================================================
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 1
   id=0 ssid='Cisco1200g'
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_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
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 3426 bytes of scan results (17 BSSes)
Scan results: 17
Selecting BSS from priority group 1
0: 00:30:ab:25:2e:d6 ssid='3105_11g' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
Authentication with 00:0c:85:71:6e:a8 timed out.
Setting scan request: 0 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
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 2819 bytes of scan results (14 BSSes)
Scan results: 14
Selecting BSS from priority group 1
0: 00:30:ab:25:2e:d6 ssid='3105_11g' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 3512 bytes of scan results (17 BSSes)
Scan results: 17
Selecting BSS from priority group 1
0: 00:30:ab:25:2e:d6 ssid='3105_11g' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
Authentication with 00:0c:85:71:6e:a8 timed out.
Setting scan request: 0 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
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 3035 bytes of scan results (15 BSSes)
Scan results: 15
Selecting BSS from priority group 1
0: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
Authentication with 00:0c:85:71:6e:a8 timed out.
Setting scan request: 0 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
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 3171 bytes of scan results (16 BSSes)
Scan results: 16
Selecting BSS from priority group 1
0: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
Authentication with 00:0c:85:71:6e:a8 timed out.
Setting scan request: 0 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
Disconnect event - remove keys
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 2885 bytes of scan results (14 BSSes)
Scan results: 14
Selecting BSS from priority group 1
0: 00:30:ab:25:2e:d6 ssid='3105_11g' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:0c:85:71:6e:a8 ssid='Cisco1200g' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0c:85:71:6e:a8 (SSID='Cisco1200g' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
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
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
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=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0c:85:71:6e:a8
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0c:85:71:6e:a8
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
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
Signal 2 received - terminating
wpa_driver_madwifi_deauthenticate
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
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
=========================================================

Any reply is appreciated.
Thanks.

yj.



From jkmaline  Thu Nov 18 07:07:42 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 18 Nov 2004 07:07:42 -0800
Subject: hostap_pci compile problem on 2.6.9 kernel
In-Reply-To: <4685.213.146.118.69.1100771782.squirrel@213.146.118.69>
References: <4685.213.146.118.69.1100771782.squirrel@213.146.118.69>
Message-ID: <20041118150742.GA7446@jm.kir.nu>

On Thu, Nov 18, 2004 at 10:56:22AM +0100, Sebastian Weitzel wrote:

> I get following compile problem on kernel 2.6.9 (gentoo-dev-sources):
> 
> make[1]: Entering directory `/usr/src/linux-2.6.9-gentoo-r3'
>   CC [M]  /usr/src/hostap/hostap/driver/modules/hostap_pci.o
> /usr/src/hostap/hostap/driver/modules/hostap_pci.c: In function
> `prism2_pci_suspend':
> /usr/src/hostap/hostap/driver/modules/hostap_pci.c:351: error: parse error
> before '<<' token

Which version of the Host AP driver are you using? If it is from CVS
pserver, could you please verify that there are no conflicts in the
file?

-- 
Jouni Malinen                                            PGP id EFC895FA



From somsaks  Thu Nov 18 08:24:08 2004
From: somsaks (Somsak Sriprayoonsakul)
Date: Thu, 18 Nov 2004 23:24:08 +0700
Subject: wpa_supplicant 0.2.5 + ipw2100 0.62: problem authenticating with
	WPA-PSK
Message-ID: <f6744e7804111808245099f9ca@mail.gmail.com>

Hi,
  Here's my environment

Dell Latitude 500 (Intel Centrino + Intel Pro 2100 miniPCI card)
OS: Fedora Core 3
AP: 3com OfficeConnect ADSL Wireless Router (3CRWE754G72-A)
AP configuration: WPA-PSK with TKIP
wpa_supplicant version: 0.2.5 + ipw2100 patch from
http://www.uninova.pt/~pmr/files/WPA/ (I recompile ATRpms SRPMS of
wpa_supplicant with ipw2100 patched)
ipw2100 version: 0.62

   I base my configuration on WPA-HOWTO.sh script (on ipw2100 patched
site). My problem is that, WPA-PSK does not works on my card. I've try
driverloader + windows xp driver (with -Dhostap) and everything works
(except that it needs special kernel with stack size = 16kb which is
not working properly on Centrino). I compare the verbose log message
of the two drivers, it seems as if something wrong happened between
handshake 3 of 4 and "authenticated". Could someone kindly help me out
of this problems?
   Attached with this mail is the -ddd log from wpa_supplicant for
both configuration (driverloader and ipw2100) also dmesg log from my
machine.
   Sorry if the problem does not belongs to wpa_supplicant. I don't
sure whether this is ipw2100 driver issue or wpa_supplicant. But the
card works well without WPA enable.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Temp.tar.bz2
Type: application/octet-stream
Size: 9583 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041118/df9a0df6/attachment.obj 


From ramalhais  Thu Nov 18 11:20:10 2004
From: ramalhais (Pedro Ramalhais)
Date: Thu, 18 Nov 2004 19:20:10 +0000
Subject: wpa_supplicant 0.2.5 + ipw2100 0.62: problem authenticating
	with WPA-PSK
In-Reply-To: <f6744e7804111808245099f9ca@mail.gmail.com>
References: <f6744e7804111808245099f9ca@mail.gmail.com>
Message-ID: <1100805608.12589.279.camel@gandalf.uninova.pt>

On Thu, 2004-11-18 at 16:24, Somsak Sriprayoonsakul wrote:
> Hi,
>   Here's my environment
> 
> Dell Latitude 500 (Intel Centrino + Intel Pro 2100 miniPCI card)
> OS: Fedora Core 3
> AP: 3com OfficeConnect ADSL Wireless Router (3CRWE754G72-A)
> AP configuration: WPA-PSK with TKIP
> wpa_supplicant version: 0.2.5 + ipw2100 patch from
> http://www.uninova.pt/~pmr/files/WPA/ (I recompile ATRpms SRPMS of
> wpa_supplicant with ipw2100 patched)
> ipw2100 version: 0.62
> 
>    I base my configuration on WPA-HOWTO.sh script (on ipw2100 patched
> site). My problem is that, WPA-PSK does not works on my card. I've try
> driverloader + windows xp driver (with -Dhostap) and everything works
> (except that it needs special kernel with stack size = 16kb which is
> not working properly on Centrino). I compare the verbose log message
> of the two drivers, it seems as if something wrong happened between
> handshake 3 of 4 and "authenticated". Could someone kindly help me out
> of this problems?
>    Attached with this mail is the -ddd log from wpa_supplicant for
> both configuration (driverloader and ipw2100) also dmesg log from my
> machine.
>    Sorry if the problem does not belongs to wpa_supplicant. I don't
> sure whether this is ipw2100 driver issue or wpa_supplicant. But the
> card works well without WPA enable.
> 
> ______________________________________________________________________
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

Try 0.56 + wpa-eapol patch
Check http://www.uninova.pt/~pmr/files/WPA/WPA-HOWTO-script.sh for URLs.
0.56 + wpa-eapol patch is the only version that works for me 100% with
WPA, other versions have problems with four-way handshake or with GTK
rekeying. Those problems are being worked on.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From espy  Thu Nov 18 12:16:37 2004
From: espy (Tony Espy)
Date: Thu, 18 Nov 2004 15:16:37 -0500
Subject: Problem with HostAP/WEP running in Managed mode
Message-ID: <419D0325.4030504@pepper.com>

Hi --

I'm having problems getting the HostAP driver to connect in Managed mode 
to an Orinoco AP-200 AccessPoint configured for WEP.

Before I get into the details, here's a bit more configuration info:

Platform: Pepper Pad2 Tablet; XScale PXA270 CPU running MontaVista CEE 
Linux 3.1 ( a 2.4.20 kernel w/some 2.5/6 features back-ported by MV ).

Wireless Extensions: v14
Wireless Tools: v27
HostAP: 0.2.5

Wi-Fi Card: Gemtek Prism II based CF card ( hostap_cs reports firmware 
as -- NIC: id=0x801b v1.0.0, PRI: id=0x15 v1.1.0, STA: id=0x1f v1.4.9 )

I currently have things set up so that the PCMCIA sub-system loads the 
drivers.  I've confirmed that hostap_cs, hostap, and hostap_crypt_wep 
are all loaded.

I'm following the instructions for Manual Roaming from the HostAP README:

prism2_param wlan0 host_roaming 2
iwconfig wlan0 mode managed
iwconfig wlan0 essid any
iwlist wlan0 scan ( the results from this look OK )
iwlist wlan0 key <WEP key>
iwlist wlan0 essid Pepper
iwlist wlan0 ap <AP MAC>

My problem is that although it looks like I've associated with our AP, 
the Bitrate always shows up as 2Mbps.  I also see a constantly 
incrementing Rx invalid crypt, Tx excessive retries, and Invalid misc 
counters when I run 'iwconfig wlan0'.

I also notice that the signal level reported for the AP is very low 
(-230 dBm ) when I run 'iwconfig wlan0'.  This differs drastically from 
the report from 'iwlist wlan0 scan', which reports a signal strength of 
-56 dBm from the AP I'm trying to connect to.

When I run 'dmesg', the last two messages are:

wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID: 00:02:2d:40:44:85 ( which is correct for our AP ).

We had been running a Symbol Spectrum24 card w/the Orinoco driver that 
worked great, however we have a new requirement to support WPA, thus 
I've been working for the past week of so to try and get HostAP working 
on the Pepper Pad.

Any help/advice would be much appreciated.

thanks,
Tony Espy
Pepper Computer, Inc.





From techie  Thu Nov 18 12:55:32 2004
From: techie (Chris)
Date: Thu, 18 Nov 2004 12:55:32 -0800
Subject: Problem with HostAP/WEP running in Managed mode
In-Reply-To: <419D0325.4030504@pepper.com>
References: <419D0325.4030504@pepper.com>
Message-ID: <419D0C44.3060300@whiterocker.com>

Tony Espy wrote:

<snip>

> Wi-Fi Card: Gemtek Prism II based CF card ( hostap_cs reports firmware 
> as -- NIC: id=0x801b v1.0.0, PRI: id=0x15 v1.1.0, STA: id=0x1f v1.4.9 )

<snip>

> We had been running a Symbol Spectrum24 card w/the Orinoco driver that 
> worked great, however we have a new requirement to support WPA, thus 
> I've been working for the past week of so to try and get HostAP 
> working on the Pepper Pad.

I believe you will need a newer firmware to do WPA.  v1.4.9 is good for 
WEP, but we found that for WPA v1.7.4 was required.  A useful link is 
http://linux.junsun.net/intersil-prism/ which contains instructions on 
how to upgrade your firmware and links to the firmware itself.  In the 
past I have found many problems are alleviated by upgrading the 
firmware, whether WPA was required or not.

Chris.



From cbzimmermann  Thu Nov 18 18:31:41 2004
From: cbzimmermann (Zimmermann, Christopher Brian Chris)
Date: Thu, 18 Nov 2004 21:31:41 -0500
Subject: wpa_supplicant v0.2.4 and vxworks ARM issue
Message-ID: <ED957039F85CAD47BF7937C3B3323ADB16A0F4@pauex2ku07.agere.com>

All,
 
I am having a problem with porting wpa_supplicant to VxWorks 5.5 and
Hermes 2, for use with WPA-PSK.  
 
Everything looks good...associating, passing 4-way handshake for
pairwise key, decrypting group key message 1 of 2...however I am getting
MIC errors in both directions.  Two of these causes my Cisco AP1200 to
boot me with an 802.11 Disassociate.
 
I ran the tests in sha1.c, all passed.  I also added the Pairwise Key
Derivation from H7 of the 802.11i/D10.0 document from April 2004.  This
test passed too.  
 
How can I be decrypting properly, yet have MIC errors.  I tried flipping
the TX and RX  MIC keys, just in case.  No luck.
 
I took our latest Windows driver, same firmware as my ARM platform.
This authenticates with my Cisco AP1200, using the exact same
configuration.  I took the TKIP Key and MIC Keys on Windows and told my
ARM platform that was it's pairwise key information.  I then sent out
the same packet for groupwise key message 2 of 2 that Windows did, and
this generates the same TX MIC as Windows does.       
 
Any ideas/suggestions would be greatly appreciated.
 
Thanks,
Chris
 
cbzimmermann at agere.com
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041118/bfc63e29/attachment.htm 


From gargid  Fri Nov 19 06:28:55 2004
From: gargid (Gargi D)
Date: Fri, 19 Nov 2004 19:58:55 +0530
Subject: HostAP mode in HostAP driver 0.1.3 v/s 0.2.4
Message-ID: <00c101c4ce44$1a16db20$1006a8c0@rahul>

Hi,

I have a 802.11b PCMCIA card from US Robotics with STA f/w : 0.7.6.

The card works in HostAP mode with HostAP driver version 0.1.3.  However with upgraded driver 0.2.4 there are some problems.  The led on card blinks, hostap gets loaded and wireless tools indicate that the card is in master mode however a client is not able to associate with it.  

When I checked in ethereal, when the card works with HostAP driver 0.2.4 the capability information in the beacon indicates that the card is in IBSS mode.  Strangely enough when the same card is made to work with HostAP driver 0.1.3 the capability information changes to indicate that the card is now in AP mode and now clients can associate with it.

Since beacons are any way generated by firmware, how is the behavior changing with different driver versions of HostAP?

Any explanations?

Regards,


Gargi Dadhich
Member Technical Staff
Networking and Internet Software Group (NISG)
C-DAC, Pune

Tel:    020-25694000/1/2/3      Extn: 484 
Fax:   020-25694059 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041119/7bb08f93/attachment.htm 


From gianni.uglietti  Fri Nov 19 08:53:43 2004
From: gianni.uglietti (Gianni Uglietti)
Date: Fri, 19 Nov 2004 16:53:43 +0000
Subject: HostAP and WPA-PSK - HELP
Message-ID: <9cfb17880411190853c29b58b@mail.gmail.com>

Hello everybody,
I am using HostAP in order to test a WPA-PSK environnement. I have a
laptop acting as AP (running hostapd) and another laptop acting as
supplicant (running wpa_supplicant).

Here is my configuration for HostAP with WPA-PSK:

#cat hostapd.conf  
ssid=testnet
macaddr_acl=1
auth_algs=1
own_ip_addr=192.168.1.22
wpa=1
wpa_passphrase=testsecret
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP 

and here my configuration for wpa_supplicant:

#cat wpa_supplicant.conf
ap_scan=1
network={
       ssid="testnet"
       psk="testsecret"
       proto=WPA
       key_mgmt=WPA-PSK
       pairwise=CCMP TKIP
       group=CCMP TKIP WEP104 WEP40
       priority=5
}

After starting both hostapd and wpa_suppling, I cannot authenticate my
supplicant because for each AP found it says:

skip - no WPA/RSN IE
No suitable AP found

A similar message is prompted also by the AP.

Any suggestions? 

Thanks,
Gianni



From mrtheplague  Fri Nov 19 08:58:25 2004
From: mrtheplague (Mr. The Plague)
Date: Fri, 19 Nov 2004 09:58:25 -0700
Subject: Lucent cards
In-Reply-To: <41538C5B0003F51B@ims6a.cp.tin.it>
References: <41538C5B0003F51B@ims6a.cp.tin.it>
Message-ID: <82736d4f041119085854622008@mail.gmail.com>

It's not *supposed* to work, but it *might* work in client mode,
because the designs were originally very similar (or so i heard). I'd
recommend running HermesAP if you need the AP functionality, or the
regular Orinoco driver if you don't. Running hostap on hermes cards
and the orinoco driver on prism2 cards is a last measure to get basic
functionality for a while, and isn't supported or recommended.


On Wed, 17 Nov 2004 18:42:18 +0100, capacity77 at tin.it <capacity77 at tin.it> wrote:
> after a long research I found that HostAP may work with Lucent based cards
> too.
> I have a Lucent based card, is it true that I can make hostap run with this
> card?
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From billtorvalds1  Fri Nov 19 11:54:37 2004
From: billtorvalds1 (leonardo)
Date: Fri, 19 Nov 2004 20:54:37 +0100
Subject: understanding the code.
Message-ID: <20041119195437.GA3525@queneau>


hi all..
I'm reviewing hostapd code for a university project, we have to study a
new form of authentication in ad-hoc wlan and I have to integrate it with
hostap.
I need to understand if I interpreted the code in a correct way: when a
frame is received it is handled by handle_frame(), if it's a data packet
it passes through handle_data() and then, if it's a EAP packet it goes to
ieee802_1x_receive(). If it's a EAPOL packet it will interfere with EAPOL
state machine, otherwise if it's a EAP packet we have to forward it to
RADIUS right? 

something I don't understand it's why it handle just "eap response"
packet and not every EAP packet, then in handle_eap_response() I can't see
how that packet is treated, there's no direct call to any radius function.
is it handled by the state machine in the main loop?

I'm writing some informal documentation about the code, when it become
something readable I will publish it

thanks,
leonardo.

-- 
GPG fingerprint = 2C20 A587 05AC 42E5 1292  D0D4 3EED CFB5 52FD AD1E



From HostAP-Research  Fri Nov 19 12:42:26 2004
From: HostAP-Research (AP-Research)
Date: Fri, 19 Nov 2004 14:42:26 -0600 (CST)
Subject: HostAP mode in HostAP driver 0.1.3 v/s 0.2.4
In-Reply-To: <00c101c4ce44$1a16db20$1006a8c0@rahul>
References: <00c101c4ce44$1a16db20$1006a8c0@rahul>
Message-ID: <32918.67.174.81.186.1100896946.squirrel@67.174.81.186>


<quote who="Gargi D">
> I have a 802.11b PCMCIA card from US Robotics with STA f/w : 0.7.6.

Have you tried newer STA f/w?
IDTable is available @ http://linux.junsun.net/intersil-prism/IDtable.html
Firmware is available @ http://www.red-bean.com/~proski/firmware/

-- 
Regards
KC Ferguson CIO/CTO
@RescuNET.com
eXtreme Response Mobile HotSpot



From jim.cromie  Fri Nov 19 16:38:57 2004
From: jim.cromie (Jim Cromie)
Date: Fri, 19 Nov 2004 17:38:57 -0700
Subject: wpa-supplicant makefile patch
Message-ID: <cfe85dfa04111916383c6b5c85@mail.gmail.com>

attached patch is trivial, but mildly helpful, ie:

[jimc at harpo wpa_supplicant-0.2.5]$ more patch-make1
--- Makefile.orig       2004-11-19 16:59:55.569710456 -0700
+++ Makefile    2004-11-19 17:22:01.798093096 -0700
@@ -34,6 +34,11 @@
                echo '.config exists - did not replace it'; \
                exit 1; \
        fi
+       @if [ -x /sbin/modprobe ]; then \
+               if /sbin/modprobe ndiswrapper 2>/dev/null ; then \
+                       echo CONFIG_DRIVER_NDISWRAPPER=y >> .config; \
+               fi \
+       fi
        echo CONFIG_DRIVER_HOSTAP=y >> .config
        echo CONFIG_DRIVER_WEXT=y >> .config
        echo CONFIG_WIRELESS_EXTENSION=y >> .config


I thought about adding a foreach loop to test for a number of modules,
but punted cuz I dont know how to upcase 'ndiswrapper'.
In any case, it better to use a proper hash to map 
   modulename => CONFIG_flag
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-make1
Type: application/octet-stream
Size: 469 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041119/4f9d4858/attachment.obj 


From HostAP-Research  Fri Nov 19 20:10:59 2004
From: HostAP-Research (AP-Research)
Date: Fri, 19 Nov 2004 22:10:59 -0600 (CST)
Subject: Patch submission format
Message-ID: <32878.67.174.81.186.1100923859.squirrel@67.174.81.186>

What is your preferred diff command for providing patches?

I found some small typos and such in hostapd-0.2.5/README
[hostapd-0.2.5]# diff -Naur README README.new >> README.patch

-- 
Regards
KC Ferguson CIO/CTO
@RescuNET.com
eXtreme Response Mobile HotSpot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: README.patch
Type: text/x-patch
Size: 6096 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041119/d2140a0f/attachment.bin 


From gargid  Sat Nov 20 00:02:42 2004
From: gargid (Gargi D)
Date: Sat, 20 Nov 2004 13:32:42 +0530
Subject: HostAP mode in HostAP driver 0.1.3 v/s 0.2.4
References: <00c101c4ce44$1a16db20$1006a8c0@rahul>
	<32918.67.174.81.186.1100896946.squirrel@67.174.81.186>
Message-ID: <000801c4ced7$4fdc88c0$1006a8c0@rahul>

> Have you tried newer STA f/w?
> IDTable is available @ http://linux.junsun.net/intersil-prism/IDtable.html
> Firmware is available @ http://www.red-bean.com/~proski/firmware/
>
The available firmwares are not compatible with the USR card.  I checked
that.  My card has component ID 8002.


I have one more card from Senao, which seems to work fine with both the
driver versions.
What makes me wonder is how the USR card with same firmware changes its
behavior with different driver versions?




From dg  Sat Nov 20 00:00:41 2004
From: dg (Dimitri Georganas)
Date: Sat, 20 Nov 2004 09:00:41 +0100
Subject: open1x xsupplicant
Message-ID: <419EF9A9.1020806@mitc.net>

Hello,

Are there any experiences with setting up the hostap in client emode 
together with open1x's xsupplicant? I've been trying to get it work with 
various other drivers, but no luck so far.

Basically it comes down to the question if hostap will allow wep key 
insertion after 802.1x
authentication...

TIA

dg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041120/29e2106c/attachment.pgp 


From gbur  Sat Nov 20 00:10:41 2004
From: gbur (Gunter Burchardt)
Date: Sat, 20 Nov 2004 09:10:41 +0100
Subject: understanding the code.
In-Reply-To: <20041119195437.GA3525@queneau>
References: <20041119195437.GA3525@queneau>
Message-ID: <20041120081041.GE28407@informatik.uni-rostock.de>

On 2004-11-19 - 20:54:37, leonardo wrote:

> I need to understand if I interpreted the code in a correct way: when a
> frame is received it is handled by handle_frame(), if it's a data packet
> it passes through handle_data() and then, if it's a EAP packet it goes to
> ieee802_1x_receive(). If it's a EAPOL packet it will interfere with EAPOL
> state machine, otherwise if it's a EAP packet we have to forward it to
> RADIUS right? 
>
> something I don't understand it's why it handle just "eap response"
> packet and not every EAP packet, then in handle_eap_response() I can't see
> how that packet is treated, there's no direct call to any radius function.
> is it handled by the state machine in the main loop?
 
EAPOL is EAP over LAN. Each packet for authentication is sent over this
protocol - so each EAPOL packet received from a station influence eapol
state machine! The state machine decides what to do (eg. sending
something to radius server).

Communication with radius server is task of Backend Authentication state
machine (BE_AUTH). An answer of the radius server is sent with txReq()
alias ieee802_1x_tx_req() to the station.

Jouni correct me if im wrong.

> I'm writing some informal documentation about the code, when it become
> something readable I will publish it

Look at developer.txt .

regards
gunter



From andrew  Sat Nov 20 05:39:50 2004
From: andrew (Andrew Duane)
Date: Sat, 20 Nov 2004 13:39:50 -0000
Subject: Ndiswrapper +wpa_supplicant
Message-ID: <ECOWS02MpBRbijiWZeV0000c7bf@smtp-out2.blueyonder.co.uk>

Hi

 

I wonder if someone would be so kind as to help me?

 

I seem to have some trouble with running wpa_supplicant. Here is a dump of
the error:

 

[root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
-c/etc/wpa_supplicant.conf -dd

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=100 (from group name 'users')

Line: 6 - start of a new network block

SSID - hexdump_ascii(len=10):

     46 6f 75 6e 64 61 74 69 6f 6e                     Linksys

key_mgmt: 0x2

PSK (ASCII passphrase) - hexdump_ascii(len=14):

     7a 71 39 67 68 74 73 63 31 6d 31 74 61 72         passcode

PSK (from passphrase) - hexdump(len=32): b2 24 58 dd 40 0a db 2e 22 18 af d1
29

ee 90 d0 5b a9 90 f8 ec 01 65 e0 d5 c4 46 fa ed 45 b7 b4

Priority group 0

   id=0 ssid='Linksys'

Setting scan request: 0 sec 100000 usec

Starting AP scan (specific SSID)

Scan SSID - hexdump_ascii(len=10):

     46 6f 75 6e 64 61 74 69 6f 6e                     Linksys

Failed to initiate AP scan.

 

I've substituted the SSID and passcode.

 

My /etc/wpa_supplicant.conf looks like this:

 

# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group

ctrl_interface=/var/run/wpa_supplicant

ctrl_interface_group=users

#

# home network; allow all valid ciphers

network={

        ssid="Linksys"

        scan_ssid=1

        key_mgmt=WPA-PSK

        psk="passcode"

}

 

And my .config before I did a make was:

 

CONFIG_EAP_PSK=y

CONFIG_WIRELESS_EXTENSION=y

CONFIG_DRIVER_NDISWRAPPER=y

 

I use ndiswrapper to wrap my windows drivers and it works okay without
encryption.

 

Any ideas? You help would be appreciated.

 

Regards

 

Andrew

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


From jkmaline  Sat Nov 20 06:11:48 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 06:11:48 -0800
Subject: open1x xsupplicant
In-Reply-To: <419EF9A9.1020806@mitc.net>
References: <419EF9A9.1020806@mitc.net>
Message-ID: <20041120141148.GA6979@jm.kir.nu>

On Sat, Nov 20, 2004 at 09:00:41AM +0100, Dimitri Georganas wrote:

> Are there any experiences with setting up the hostap in client emode 
> together with open1x's xsupplicant? I've been trying to get it work with 
> various other drivers, but no luck so far.

So did you try it with Host AP driver or not? As far as I know, Host AP
driver should work fine with both xsupplicant and wpa_supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 20 08:29:21 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 08:29:21 -0800
Subject: Patch submission format
In-Reply-To: <32878.67.174.81.186.1100923859.squirrel@67.174.81.186>
References: <32878.67.174.81.186.1100923859.squirrel@67.174.81.186>
Message-ID: <20041120162921.GA7074@jm.kir.nu>

On Fri, Nov 19, 2004 at 10:10:59PM -0600, AP-Research wrote:

> What is your preferred diff command for providing patches?
> 
> I found some small typos and such in hostapd-0.2.5/README
> [hostapd-0.2.5]# diff -Naur README README.new >> README.patch

Unified diff is the preferred format; ideally to the current CVS
version, but against the latest release is also fine in most cases. I
merged the changes here to both development and stable branches and
couple of other files that included same text.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 20 08:31:55 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 08:31:55 -0800
Subject: wpa-supplicant makefile patch
In-Reply-To: <cfe85dfa04111916383c6b5c85@mail.gmail.com>
References: <cfe85dfa04111916383c6b5c85@mail.gmail.com>
Message-ID: <20041120163155.GB7074@jm.kir.nu>

On Fri, Nov 19, 2004 at 05:38:57PM -0700, Jim Cromie wrote:

> attached patch is trivial, but mildly helpful, ie:
> 
> [jimc at harpo wpa_supplicant-0.2.5]$ more patch-make1
> --- Makefile.orig       2004-11-19 16:59:55.569710456 -0700
> +++ Makefile    2004-11-19 17:22:01.798093096 -0700
> @@ -34,6 +34,11 @@
>                 echo '.config exists - did not replace it'; \
>                 exit 1; \
>         fi
> +       @if [ -x /sbin/modprobe ]; then \
> +               if /sbin/modprobe ndiswrapper 2>/dev/null ; then \
> +                       echo CONFIG_DRIVER_NDISWRAPPER=y >> .config; \
> +               fi \
> +       fi

This has an unexpected side-effect of trying to load a kernel module and
I would rather not change 'make mkconfig' to do this. In addition, this
would require root privileges whereas the compilation should not add
such a requirement.

I'm more likely to just remove the 'make mkconfig' completely and add a
seaprate config.example (etc.) file that could be used as a template.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 20 08:34:04 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 08:34:04 -0800
Subject: HostAP and WPA-PSK - HELP
In-Reply-To: <9cfb17880411190853c29b58b@mail.gmail.com>
References: <9cfb17880411190853c29b58b@mail.gmail.com>
Message-ID: <20041120163404.GC7074@jm.kir.nu>

On Fri, Nov 19, 2004 at 04:53:43PM +0000, Gianni Uglietti wrote:

> After starting both hostapd and wpa_suppling, I cannot authenticate my
> supplicant because for each AP found it says:
> 
> skip - no WPA/RSN IE
> No suitable AP found

> A similar message is prompted also by the AP.

There is no such message in hostapd. Could you please send the exact
message from hostapd.

Which version of the station firmware do you use in the AP and client?
WPA requires version 1.7.x or newer.

-- 
Jouni Malinen                                            PGP id EFC895FA



From gudmk  Sat Nov 20 09:59:06 2004
From: gudmk (Gudmundur Karlsson)
Date: Sat, 20 Nov 2004 12:59:06 -0500
Subject: Extending reach with another hostap_cs AP
Message-ID: <BAY101-F24A762B480AEA4A7986298BFC40@phx.gbl>

newbie question:
I have an access point set up on a linux (slackware) box using hostap_cs in 
host mode.
Now I want to extend the reach of the network by installing an identical 
system running in ap host mode also (a few hundred meters apart (both APs 
using senao 2511 CD PLUS EXT2)).
My plan is just to set it up the same way with the same SSID, hoping to keep 
all clients on the same subnet.   The second AP would request a dhcp address 
from the first.
Each client would connect to whichever AP is the nearest one.

Do I need to do anything special to achieve this?
Can I really use only one subnet for all wireless connections?
Thanks in advance,
Gudmundur





From jkmaline  Sat Nov 20 21:04:04 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 21:04:04 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
	Atheros 802.11a/b/g card
In-Reply-To: <419277BA.6020703@cisco.com>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
	<419277BA.6020703@cisco.com>
Message-ID: <20041121050404.GB6980@jm.kir.nu>

On Wed, Nov 10, 2004 at 12:19:06PM -0800, Michael Reilly wrote:

> >>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip 
> >>(5212 I think it is called).  The card has a PCI id of vendor 0x168c, 
> >>device 0x0013.
> >>
> >>wpa_supplicant fails when I try to use WPA-PSK.  I downloaded a trial 
> >>copy of driverloader and it works fine.

> 	ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added

I tested with another AR5212-based a/b/g card and the same driver
version (2.4.2.33) using the current CVS snapshot of ndiswrapper and
Linux 2.4.28. This worked in my tests with WPA-PSK. In couple of test
cases with Linksys WRT54G as the AP, it took few attempts to get group
key handshake completed, though. This may be some kind of timing related
issue with the client not receiving encrypted frames immediately after
the keys have been configured. The tests with another AP (Gateway
7001ag) were succeeded on the first try. This AP has a longer timeout
for group key handshake, which could explain the behavior.

WPA-RADIUS (key_mgmt=WPA+IEEE 802.1X) was not apparently implemented at
all in ndiswrapper (I would assume it was just forgotten). I added
support for it and this seemed to allow association and completion of
IEEE 802.1X + WPA authentication. The attached patch against the
ndiswrapper CVS was enough to get this working and it would be nice to
see it being added to the next ndiswrapper release.

I tested this with both Atheros and Broadcom based cards. There seems to
be some issues with both cards as far as reliability in getting packets
through during the authentication is concerned.. Some of the IEEE 802.1X
packets seem to disappear and I needed to use shorter EAPOL state
machine timeouts to get authentication more reliable. Another issue was
the failure in getting group key handshake done in some test runs that I
mentioned above.

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Index: driver/iw_ndis.c
===================================================================
RCS file: /cvsroot/ndiswrapper/ndiswrapper/driver/iw_ndis.c,v
retrieving revision 1.79
diff -u -p -r1.79 iw_ndis.c
--- driver/iw_ndis.c	13 Nov 2004 04:56:27 -0000	1.79
+++ driver/iw_ndis.c	21 Nov 2004 04:49:35 -0000
@@ -1523,6 +1523,7 @@ static int wpa_associate(struct net_devi
 		 wpa_assoc_info.key_mgmt_suite,
 		 wpa_assoc_info.pairwise_suite, wpa_assoc_info.group_suite);
 	if (wpa_assoc_info.key_mgmt_suite != KEY_MGMT_PSK &&
+	    wpa_assoc_info.key_mgmt_suite != KEY_MGMT_802_1X &&
 	    wpa_assoc_info.key_mgmt_suite != KEY_MGMT_NONE)
 		TRACEEXIT(return -EINVAL);
 
@@ -1555,6 +1556,11 @@ static int wpa_associate(struct net_devi
 			TRACEEXIT(return -EINVAL);
 		auth_mode = AUTHMODE_WPAPSK;
 		break;
+	case KEY_MGMT_802_1X:
+		if (!test_bit(CAPA_WPA, &handle->capa))
+			TRACEEXIT(return -EINVAL);
+		auth_mode = AUTHMODE_WPA;
+		break;
 	case KEY_MGMT_NONE:
 		if (wpa_assoc_info.group_suite != CIPHER_WEP104 &&
 		    wpa_assoc_info.group_suite != CIPHER_WEP40)


From jkmaline  Sat Nov 20 21:08:30 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 21:08:30 -0800
Subject: TLS failing with Linksys WPC54G and WRK54G
In-Reply-To: <41927995.1040304@yahoo.com>
References: <41927995.1040304@yahoo.com>
Message-ID: <20041121050830.GC6980@jm.kir.nu>

On Wed, Nov 10, 2004 at 01:27:01PM -0700, Stephen Mathezer wrote:

> I hope somebody can offer me some insight into this. I cannot for the 
> life of me get my Linksys WPC54GV4 to connect with WPA (EAP-TLS) to the 
> WRK54G.
> 
> I am using ndiswrapper 0.11, 2.6.7 kernel, wpa_supplicant 2.5.

The current version of ndiswrapper does not seem to support WPA-EAP.
Could you please re-test with the attached patch?

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Index: driver/iw_ndis.c
===================================================================
RCS file: /cvsroot/ndiswrapper/ndiswrapper/driver/iw_ndis.c,v
retrieving revision 1.79
diff -u -p -r1.79 iw_ndis.c
--- driver/iw_ndis.c	13 Nov 2004 04:56:27 -0000	1.79
+++ driver/iw_ndis.c	21 Nov 2004 04:49:35 -0000
@@ -1523,6 +1523,7 @@ static int wpa_associate(struct net_devi
 		 wpa_assoc_info.key_mgmt_suite,
 		 wpa_assoc_info.pairwise_suite, wpa_assoc_info.group_suite);
 	if (wpa_assoc_info.key_mgmt_suite != KEY_MGMT_PSK &&
+	    wpa_assoc_info.key_mgmt_suite != KEY_MGMT_802_1X &&
 	    wpa_assoc_info.key_mgmt_suite != KEY_MGMT_NONE)
 		TRACEEXIT(return -EINVAL);
 
@@ -1555,6 +1556,11 @@ static int wpa_associate(struct net_devi
 			TRACEEXIT(return -EINVAL);
 		auth_mode = AUTHMODE_WPAPSK;
 		break;
+	case KEY_MGMT_802_1X:
+		if (!test_bit(CAPA_WPA, &handle->capa))
+			TRACEEXIT(return -EINVAL);
+		auth_mode = AUTHMODE_WPA;
+		break;
 	case KEY_MGMT_NONE:
 		if (wpa_assoc_info.group_suite != CIPHER_WEP104 &&
 		    wpa_assoc_info.group_suite != CIPHER_WEP40)


From jkmaline  Sat Nov 20 21:16:04 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 20 Nov 2004 21:16:04 -0800
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS02MpBRbijiWZeV0000c7bf@smtp-out2.blueyonder.co.uk>
References: <ECOWS02MpBRbijiWZeV0000c7bf@smtp-out2.blueyonder.co.uk>
Message-ID: <20041121051604.GD6980@jm.kir.nu>

On Sat, Nov 20, 2004 at 01:39:50PM -0000, Andrew Duane wrote:

> I wonder if someone would be so kind as to help me?

If you will provide some more information..

Which version of ndiswrapper are you using? With which NDIS driver and
which wlan card?

> I seem to have some trouble with running wpa_supplicant. Here is a dump of
> the error:

> [root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
> -c/etc/wpa_supplicant.conf -dd

> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=10):
>      46 6f 75 6e 64 61 74 69 6f 6e                     Linksys
> Failed to initiate AP scan.

And what happened after this? I saw similar issues with a scan for
specific SSID (scan_ssid=1), but broadcast SSID scan worked fine. Please
also verify whether you can see the correct AP in 'iwlist wlan0 scan'
output and whether this includes wpa_ie information.

> And my .config before I did a make was:
> 
> CONFIG_EAP_PSK=y

You do not need EAP-PSK for WPA-PSK; it is an experimental EAP method
that is not likely to be deployed anywhere yet.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dennis  Sun Nov 21 02:41:40 2004
From: dennis (Dennis Kaarsemaker)
Date: Sun, 21 Nov 2004 11:41:40 +0100
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS02MpBRbijiWZeV0000c7bf@smtp-out2.blueyonder.co.uk>
References: <ECOWS02MpBRbijiWZeV0000c7bf@smtp-out2.blueyonder.co.uk>
Message-ID: <1101033700.3935.1.camel@localhost.localdomain>

On Sat, 2004-11-20 at 13:39 +0000, Andrew Duane wrote:
> Failed to initiate AP scan.

I have seen this exact same error when using older versions of
ndiswrapper & wpa_supplicant. I am now using CVS versions of both and
the message has disappeared.

Unfortunately, i do not know which of the two actually caused this error
but I believe it was the ndiswrapper.
-- 
Dennis K.
  And that's the way the cookie crumbles!




From andrew  Sun Nov 21 05:06:18 2004
From: andrew (Andrew Duane)
Date: Sun, 21 Nov 2004 13:06:18 -0000
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <20041121051604.GD6980@jm.kir.nu>
Message-ID: <ECOWS06MsWPxKcyr7hL0000fd8b@smtp-out6.blueyonder.co.uk>

Thanks for your reply.

I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.

I tried the ndis 0.12rc3 cvs but it errors when I compile.

Once I get:

Failed to initiate AP scan.

It just hangs there. There are no subsequent messages

"I saw similar issues with a scan for
specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."

What value needs to be in my conf file to broadcast? I just followed the
instructions.

I've removed CONFIG_EAP_PSK=y from .config and recompiled okay. Config now
looks like this:

CONFIG_WIRELESS_EXTENSION=y
CONFIG_DRIVER_NDISWRAPPER=y

Thanks for your help

-----Original Message-----
From: hostap-bounces+andrew=duaneville.com at shmoo.com
[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: 21 November 2004 05:16
To: hostap at shmoo.com
Subject: Re: Ndiswrapper +wpa_supplicant

On Sat, Nov 20, 2004 at 01:39:50PM -0000, Andrew Duane wrote:

> I wonder if someone would be so kind as to help me?

If you will provide some more information..

Which version of ndiswrapper are you using? With which NDIS driver and
which wlan card?

> I seem to have some trouble with running wpa_supplicant. Here is a dump of
> the error:

> [root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
> -c/etc/wpa_supplicant.conf -dd

> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=10):
>      46 6f 75 6e 64 61 74 69 6f 6e                     Linksys
> Failed to initiate AP scan.

And what happened after this? I saw similar issues with a scan for
specific SSID (scan_ssid=1), but broadcast SSID scan worked fine. Please
also verify whether you can see the correct AP in 'iwlist wlan0 scan'
output and whether this includes wpa_ie information.

> And my .config before I did a make was:
> 
> CONFIG_EAP_PSK=y

You do not need EAP-PSK for WPA-PSK; it is an experimental EAP method
that is not likely to be deployed anywhere yet.

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







From andrew  Sun Nov 21 05:13:17 2004
From: andrew (Andrew Duane)
Date: Sun, 21 Nov 2004 13:13:17 -0000
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS06MsWPxKcyr7hL0000fd8b@smtp-out6.blueyonder.co.uk>
Message-ID: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>

Oh just reread and missed some information.

My ndis driver is bcmwl5 and the wireless card is the linksys wmp54g,
although ndis works okay when I turn off wpa encryption.

Also here is what is returned from iwlist wlan0 scan:

wlan0     Scan completed :
          Cell 01 - Address: 00:0C:41:9D:F4:4A
                    ESSID:"Foundation"
                    Protocol:IEEE 802.11b
                    Mode:Managed
                    Frequency:2.452GHz
                    Quality:0/100  Signal level:-54 dBm  Noise level:-256
dBm
                    Encryption key:on
                    Bit Rate:1Mb/s
                    Bit Rate:2Mb/s
                    Bit Rate:5.5Mb/s
                    Bit Rate:11Mb/s
                    Bit Rate:18Mb/s
                    Bit Rate:24Mb/s
                    Bit Rate:36Mb/s
                    Bit Rate:54Mb/s
                    Bit Rate:6Mb/s
                    Bit Rate:9Mb/s
                    Bit Rate:12Mb/s
                    Bit Rate:48Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
 
Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202

A bit odd it says that the protocol is 802.11b as I have it set to only
accept 802.11g???

-----Original Message-----
From: hostap-bounces+andrew=duaneville.com at shmoo.com
[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Andrew
Duane
Sent: 21 November 2004 13:06
To: 'Jouni Malinen'
Cc: hostap at shmoo.com
Subject: RE: Ndiswrapper +wpa_supplicant

Thanks for your reply.

I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.

I tried the ndis 0.12rc3 cvs but it errors when I compile.

Once I get:

Failed to initiate AP scan.

It just hangs there. There are no subsequent messages

"I saw similar issues with a scan for
specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."

What value needs to be in my conf file to broadcast? I just followed the
instructions.

I've removed CONFIG_EAP_PSK=y from .config and recompiled okay. Config now
looks like this:

CONFIG_WIRELESS_EXTENSION=y
CONFIG_DRIVER_NDISWRAPPER=y

Thanks for your help

-----Original Message-----
From: hostap-bounces+andrew=duaneville.com at shmoo.com
[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: 21 November 2004 05:16
To: hostap at shmoo.com
Subject: Re: Ndiswrapper +wpa_supplicant

On Sat, Nov 20, 2004 at 01:39:50PM -0000, Andrew Duane wrote:

> I wonder if someone would be so kind as to help me?

If you will provide some more information..

Which version of ndiswrapper are you using? With which NDIS driver and
which wlan card?

> I seem to have some trouble with running wpa_supplicant. Here is a dump of
> the error:

> [root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
> -c/etc/wpa_supplicant.conf -dd

> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=10):
>      46 6f 75 6e 64 61 74 69 6f 6e                     Linksys
> Failed to initiate AP scan.

And what happened after this? I saw similar issues with a scan for
specific SSID (scan_ssid=1), but broadcast SSID scan worked fine. Please
also verify whether you can see the correct AP in 'iwlist wlan0 scan'
output and whether this includes wpa_ie information.

> And my .config before I did a make was:
> 
> CONFIG_EAP_PSK=y

You do not need EAP-PSK for WPA-PSK; it is an experimental EAP method
that is not likely to be deployed anywhere yet.

-- 
Jouni Malinen                                            PGP id EFC895FA
_______________________________________________
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 gentoopower  Sun Nov 21 06:38:45 2004
From: gentoopower (Stefan)
Date: Sun, 21 Nov 2004 15:38:45 +0100
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
References: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
Message-ID: <41A0A875.7010307@yahoo.de>

Andrew Duane wrote:

>Oh just reread and missed some information.
>
>My ndis driver is bcmwl5 and the wireless card is the linksys wmp54g,
>although ndis works okay when I turn off wpa encryption.
>
>Also here is what is returned from iwlist wlan0 scan:
>
>wlan0     Scan completed :
>          Cell 01 - Address: 00:0C:41:9D:F4:4A
>                    ESSID:"Foundation"
>                    Protocol:IEEE 802.11b
>                    Mode:Managed
>                    Frequency:2.452GHz
>                    Quality:0/100  Signal level:-54 dBm  Noise level:-256
>dBm
>                    Encryption key:on
>                    Bit Rate:1Mb/s
>                    Bit Rate:2Mb/s
>                    Bit Rate:5.5Mb/s
>                    Bit Rate:11Mb/s
>                    Bit Rate:18Mb/s
>                    Bit Rate:24Mb/s
>                    Bit Rate:36Mb/s
>                    Bit Rate:54Mb/s
>                    Bit Rate:6Mb/s
>                    Bit Rate:9Mb/s
>                    Bit Rate:12Mb/s
>                    Bit Rate:48Mb/s
>                    Extra:bcn_int=100
>                    Extra:atim=0
> 
>Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
>
>A bit odd it says that the protocol is 802.11b as I have it set to only
>accept 802.11g???
>  
>

Yes somehow either ndiswrapper or wpa_supplicant have trouble with 
802.11g APs tested a few of them usually they work if one sets them to 
802.11b, if possible.

>-----Original Message-----
>From: hostap-bounces+andrew=duaneville.com at shmoo.com
>[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Andrew
>Duane
>Sent: 21 November 2004 13:06
>To: 'Jouni Malinen'
>Cc: hostap at shmoo.com
>Subject: RE: Ndiswrapper +wpa_supplicant
>
>Thanks for your reply.
>
>I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.
>
>I tried the ndis 0.12rc3 cvs but it errors when I compile.
>
>Once I get:
>
>Failed to initiate AP scan.
>
>It just hangs there. There are no subsequent messages
>
>"I saw similar issues with a scan for
>specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."
>
>What value needs to be in my conf file to broadcast? I just followed the
>instructions.
>
>I've removed CONFIG_EAP_PSK=y from .config and recompiled okay. Config now
>looks like this:
>
>CONFIG_WIRELESS_EXTENSION=y
>CONFIG_DRIVER_NDISWRAPPER=y
>
>Thanks for your help
>
>-----Original Message-----
>From: hostap-bounces+andrew=duaneville.com at shmoo.com
>[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Jouni
>Malinen
>Sent: 21 November 2004 05:16
>To: hostap at shmoo.com
>Subject: Re: Ndiswrapper +wpa_supplicant
>
>On Sat, Nov 20, 2004 at 01:39:50PM -0000, Andrew Duane wrote:
>
>  
>
>>I wonder if someone would be so kind as to help me?
>>    
>>
>
>If you will provide some more information..
>
>Which version of ndiswrapper are you using? With which NDIS driver and
>which wlan card?
>
>  
>
>>I seem to have some trouble with running wpa_supplicant. Here is a dump of
>>the error:
>>    
>>
>
>  
>
>>[root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
>>-c/etc/wpa_supplicant.conf -dd
>>    
>>
>
>  
>
>>Starting AP scan (specific SSID)
>>Scan SSID - hexdump_ascii(len=10):
>>     46 6f 75 6e 64 61 74 69 6f 6e                     Linksys
>>Failed to initiate AP scan.
>>    
>>
>
>And what happened after this? I saw similar issues with a scan for
>specific SSID (scan_ssid=1), but broadcast SSID scan worked fine. Please
>also verify whether you can see the correct AP in 'iwlist wlan0 scan'
>output and whether this includes wpa_ie information.
>
>  
>
>>And my .config before I did a make was:
>>
>>CONFIG_EAP_PSK=y
>>    
>>
>
>You do not need EAP-PSK for WPA-PSK; it is an experimental EAP method
>that is not likely to be deployed anywhere yet.
>
>  
>




From dg  Sun Nov 21 06:44:54 2004
From: dg (Dimitri Georganas)
Date: Sun, 21 Nov 2004 15:44:54 +0100
Subject: open1x xsupplicant
In-Reply-To: <20041120141148.GA6979@jm.kir.nu>
References: <419EF9A9.1020806@mitc.net> <20041120141148.GA6979@jm.kir.nu>
Message-ID: <41A0A9E6.4090105@mitc.net>

Jouni Malinen wrote:

>On Sat, Nov 20, 2004 at 09:00:41AM +0100, Dimitri Georganas wrote:
>
>  
>
>>Are there any experiences with setting up the hostap in client emode 
>>together with open1x's xsupplicant? I've been trying to get it work with 
>>various other drivers, but no luck so far.
>>    
>>
>
>So did you try it with Host AP driver or not? As far as I know, Host AP
>driver should work fine with both xsupplicant and wpa_supplicant.
>
>  
>
Hi Jouni,

No but I will try now. Just wanted to check with the list before trying. 
I've been trying quite a few
drivers last week with only disappointing results.

Thanks
Dimitri

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041121/42bea8ce/attachment.pgp 


From andrew  Sun Nov 21 07:07:29 2004
From: andrew (Andrew Duane)
Date: Sun, 21 Nov 2004 15:07:29 -0000
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <41A0A875.7010307@yahoo.de>
Message-ID: <ECOWS06MnhzXjbCiyxT000101fc@smtp-out6.blueyonder.co.uk>

I changed my Linksys router/ap (WRT54G) to B only then ran wpa_supplicant
again but no luck. Same as before. I've put it back to mixed now. Still get
protocol b from a scan though?

-----Original Message-----
From: Stefan [mailto:gentoopower at yahoo.de] 
Sent: 21 November 2004 14:39
To: andrew at duaneville.com
Cc: hostap at shmoo.com
Subject: Re: Ndiswrapper +wpa_supplicant

Andrew Duane wrote:

>Oh just reread and missed some information.
>
>My ndis driver is bcmwl5 and the wireless card is the linksys wmp54g,
>although ndis works okay when I turn off wpa encryption.
>
>Also here is what is returned from iwlist wlan0 scan:
>
>wlan0     Scan completed :
>          Cell 01 - Address: 00:0C:41:9D:F4:4A
>                    ESSID:"Foundation"
>                    Protocol:IEEE 802.11b
>                    Mode:Managed
>                    Frequency:2.452GHz
>                    Quality:0/100  Signal level:-54 dBm  Noise level:-256
>dBm
>                    Encryption key:on
>                    Bit Rate:1Mb/s
>                    Bit Rate:2Mb/s
>                    Bit Rate:5.5Mb/s
>                    Bit Rate:11Mb/s
>                    Bit Rate:18Mb/s
>                    Bit Rate:24Mb/s
>                    Bit Rate:36Mb/s
>                    Bit Rate:54Mb/s
>                    Bit Rate:6Mb/s
>                    Bit Rate:9Mb/s
>                    Bit Rate:12Mb/s
>                    Bit Rate:48Mb/s
>                    Extra:bcn_int=100
>                    Extra:atim=0
> 
>Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
>
>A bit odd it says that the protocol is 802.11b as I have it set to only
>accept 802.11g???
>  
>

Yes somehow either ndiswrapper or wpa_supplicant have trouble with 
802.11g APs tested a few of them usually they work if one sets them to 
802.11b, if possible.

>-----Original Message-----
>From: hostap-bounces+andrew=duaneville.com at shmoo.com
>[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Andrew
>Duane
>Sent: 21 November 2004 13:06
>To: 'Jouni Malinen'
>Cc: hostap at shmoo.com
>Subject: RE: Ndiswrapper +wpa_supplicant
>
>Thanks for your reply.
>
>I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.
>
>I tried the ndis 0.12rc3 cvs but it errors when I compile.
>
>Once I get:
>
>Failed to initiate AP scan.
>
>It just hangs there. There are no subsequent messages
>
>"I saw similar issues with a scan for
>specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."
>
>What value needs to be in my conf file to broadcast? I just followed the
>instructions.
>
>I've removed CONFIG_EAP_PSK=y from .config and recompiled okay. Config now
>looks like this:
>
>CONFIG_WIRELESS_EXTENSION=y
>CONFIG_DRIVER_NDISWRAPPER=y
>
>Thanks for your help
>
>-----Original Message-----
>From: hostap-bounces+andrew=duaneville.com at shmoo.com
>[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Jouni
>Malinen
>Sent: 21 November 2004 05:16
>To: hostap at shmoo.com
>Subject: Re: Ndiswrapper +wpa_supplicant
>
>On Sat, Nov 20, 2004 at 01:39:50PM -0000, Andrew Duane wrote:
>
>  
>
>>I wonder if someone would be so kind as to help me?
>>    
>>
>
>If you will provide some more information..
>
>Which version of ndiswrapper are you using? With which NDIS driver and
>which wlan card?
>
>  
>
>>I seem to have some trouble with running wpa_supplicant. Here is a dump of
>>the error:
>>    
>>
>
>  
>
>>[root at server1 wpa_supplicant-0.2.5]# wpa_supplicant -iwlan0
>>-c/etc/wpa_supplicant.conf -dd
>>    
>>
>
>  
>
>>Starting AP scan (specific SSID)
>>Scan SSID - hexdump_ascii(len=10):
>>     46 6f 75 6e 64 61 74 69 6f 6e                     Linksys
>>Failed to initiate AP scan.
>>    
>>
>
>And what happened after this? I saw similar issues with a scan for
>specific SSID (scan_ssid=1), but broadcast SSID scan worked fine. Please
>also verify whether you can see the correct AP in 'iwlist wlan0 scan'
>output and whether this includes wpa_ie information.
>
>  
>
>>And my .config before I did a make was:
>>
>>CONFIG_EAP_PSK=y
>>    
>>
>
>You do not need EAP-PSK for WPA-PSK; it is an experimental EAP method
>that is not likely to be deployed anywhere yet.
>
>  
>







From jkmaline  Sun Nov 21 08:31:04 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 21 Nov 2004 08:31:04 -0800
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
References: <ECOWS06MsWPxKcyr7hL0000fd8b@smtp-out6.blueyonder.co.uk>
	<ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
Message-ID: <20041121163104.GA7016@jm.kir.nu>

On Sun, Nov 21, 2004 at 01:13:17PM -0000, Andrew Duane wrote:

> Also here is what is returned from iwlist wlan0 scan:
> 
> wlan0     Scan completed :
>           Cell 01 - Address: 00:0C:41:9D:F4:4A
>                     ESSID:"Foundation"
>                     Protocol:IEEE 802.11b

> Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
> 
> A bit odd it says that the protocol is 802.11b as I have it set to only
> accept 802.11g???

That's fine, nothing is using that information. I would assume
ndiswrapper does not try to map the supported rates information into
IEEE 802.11b vs .11g. The main information is here: scan seems to work
and it returns wpa_ie.


Previous message:

> I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.
> 
> I tried the ndis 0.12rc3 cvs but it errors when I compile.

Please use the CVS snapshot, not the 0.12rc3 prerelease. At least the
version from yesterday worked in my tests whereas 0.12rc3 required some
fixing for Linux 2.4.28 (but worked with the minor changes I did).

> Once I get:
> 
> Failed to initiate AP scan.
> 
> It just hangs there. There are no subsequent messages

That's odd.. wpa_supplicant should scan again after five seconds. Could
you please re-test with -ddd on wpa_supplicant command line to enable
all debug messages.

> "I saw similar issues with a scan for
> specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."
> 
> What value needs to be in my conf file to broadcast? I just followed the
> instructions.

Just leave that scan_ssid line out from the configuration and test
again.

-- 
Jouni Malinen                                            PGP id EFC895FA



From andrew  Sun Nov 21 09:14:33 2004
From: andrew (Andrew Duane)
Date: Sun, 21 Nov 2004 17:14:33 -0000
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <20041121163104.GA7016@jm.kir.nu>
Message-ID: <ECOWS03MWAdPj8VTTma00010996@smtp-out3.blueyonder.co.uk>

Bingo!

All I changed was to remove scan_ssid from the configuration file and it
worked.

If you need me to post anything else about my config let me know so it can
help others.

To summarise I use ndiswrapper 0.11 wpa_supplicant 0.2.5 with Linux 2.6.9
kernel on Fedora distro. With a linsys wrt54g ap/router and a linksys wmp54g
pci card.

With the following .config:

CONFIG_WIRELESS_EXTENSION=y
CONFIG_DRIVER_NDISWRAPPER=y

And my wpa_supplicant.conf:

# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=users
#
# home network; allow all valid ciphers
network={
        ssid="My_Ssid"
        key_mgmt=WPA-PSK
        psk="secret"
}

Thank you very much for your help.

-----Original Message-----
From: hostap-bounces+andrew=duaneville.com at shmoo.com
[mailto:hostap-bounces+andrew=duaneville.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: 21 November 2004 16:31
To: hostap at shmoo.com
Subject: Re: Ndiswrapper +wpa_supplicant

On Sun, Nov 21, 2004 at 01:13:17PM -0000, Andrew Duane wrote:

> Also here is what is returned from iwlist wlan0 scan:
> 
> wlan0     Scan completed :
>           Cell 01 - Address: 00:0C:41:9D:F4:4A
>                     ESSID:"Foundation"
>                     Protocol:IEEE 802.11b

> Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202
> 
> A bit odd it says that the protocol is 802.11b as I have it set to only
> accept 802.11g???

That's fine, nothing is using that information. I would assume
ndiswrapper does not try to map the supported rates information into
IEEE 802.11b vs .11g. The main information is here: scan seems to work
and it returns wpa_ie.


Previous message:

> I'm running version 0.11 of ndiswrapper and 0.2.5 of wpa_supplicant.
> 
> I tried the ndis 0.12rc3 cvs but it errors when I compile.

Please use the CVS snapshot, not the 0.12rc3 prerelease. At least the
version from yesterday worked in my tests whereas 0.12rc3 required some
fixing for Linux 2.4.28 (but worked with the minor changes I did).

> Once I get:
> 
> Failed to initiate AP scan.
> 
> It just hangs there. There are no subsequent messages

That's odd.. wpa_supplicant should scan again after five seconds. Could
you please re-test with -ddd on wpa_supplicant command line to enable
all debug messages.

> "I saw similar issues with a scan for
> specific SSID (scan_ssid=1), but broadcast SSID scan worked fine."
> 
> What value needs to be in my conf file to broadcast? I just followed the
> instructions.

Just leave that scan_ssid line out from the configuration and test
again.

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







From seb  Sun Nov 21 09:45:56 2004
From: seb (Sebastian Kaps)
Date: Sun, 21 Nov 2004 18:45:56 +0100
Subject: Question regarding WPA(-PSK)
Message-ID: <m3pt275c4r.fsf@toyland.sauerland.de>

Hi!

I have a SMC2802W V2 card which I'm running with ndiswrapper.
I want to use WPA-PSK encryption, so I installed wpasupplicant.

This basically works, but I always have to run "wpa_cli reassociate"
after bringing up the interface. Otherwise I can't connect to my access
point.

Can this be automated somehow?

Here's my /etc/wpa_supplicant.conf:
,----
| ctrl_interface=/var/run/wpa_supplicant # for wpa_cli support
| 
| network={
|   ssid="WLAN"
|   psk="secret"
|   key_mgmt=WPA-PSK
|   proto=WPA
| }
`----

wpa_supplicant itself is started by ifup(8) like this:
,----
| /usr/sbin/wpa_supplicant -Bw -i wlan0 -D ndiswrapper -c /etc/wpa_supplicant.conf
`----
-- 
Ciao, Sebastian



From jkmaline  Sun Nov 21 09:59:17 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 21 Nov 2004 09:59:17 -0800
Subject: Question regarding WPA(-PSK)
In-Reply-To: <m3pt275c4r.fsf@toyland.sauerland.de>
References: <m3pt275c4r.fsf@toyland.sauerland.de>
Message-ID: <20041121175917.GB7016@jm.kir.nu>

On Sun, Nov 21, 2004 at 06:45:56PM +0100, Sebastian Kaps wrote:

> I have a SMC2802W V2 card which I'm running with ndiswrapper.
> I want to use WPA-PSK encryption, so I installed wpasupplicant.
> 
> This basically works, but I always have to run "wpa_cli reassociate"
> after bringing up the interface. Otherwise I can't connect to my access
> point.

This is not the expected behavior and I do not need to force
reassociation in my tests with ndiswrapper. Could yu please send
wpa_suplicant debug log (i.e., do not fork to background with -B and
add -ddd to command line) for a case where you let it run first for a
minute or two before running "wpa_cli reassociate"? I would like to see
what is happening and why reassociation request trigger the completion
of the negotiation.

-- 
Jouni Malinen                                            PGP id EFC895FA



From beat.naef  Sun Nov 21 12:36:50 2004
From: beat.naef (Beat Naef)
Date: Sun, 21 Nov 2004 12:36:50 -0800
Subject: rx frame header question
Message-ID: <000401c4d009$d4bd37f0$1f01a8c0@swissalps>

My one of my access points is showing numerous error messages of the
following form:

Nov 21 18:09:35 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@199388)


After running prism2_param wlan0 dump 1 = dump RX frame headers I was able
to capture a fair number of rx frame headers. Below is a sample record:

Nov 21 18:10:47 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=3 signal=29 rate=20 rxflow=0; jiffies=206638
Nov 21 18:10:47 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x41c0 data_len=47
Nov 21 18:10:47 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=51:c1:45:20:d8:dd
Nov 21 18:10:47 localhost kernel:    dst=b0:fc:ab:ec:31:cf
src=85:d8:9b:0d:ef:8f len=47

The fields A4, dst and src contain mac addresses that I do not recognize.
Currently the invalid misc counter is at 37354 and rapidly growing. The rx
invalid crypt counter is at 43 and the tx excessive retries counter is at
145. The last time I rebooted was about one hour ago.

Any idea what may cause these corrupted frames and error messages?

Below is a more extensive collection of records as well as bootup
information.


With kind regards

Beat Naef




More rx dump records:

Nov 21 17:36:44 localhost kernel: hostap_crypt: registered algorithm 'NULL'
Nov 21 17:36:44 localhost kernel: hostap_pci: 0.2.4 - metrix 2004-08-19
(Jouni Malinen <jkmaline at cc.hut.fi>)
Nov 21 17:36:44 localhost kernel: hostap_pci: Registered netdevice wifi0
Nov 21 17:36:44 localhost kernel: wifi0: Original COR value: 0x0
Nov 21 17:36:44 localhost kernel: prism2_hw_init: initialized in 200 ms
Nov 21 17:36:44 localhost kernel: wifi0: NIC: id=0x8013 v1.0.0
Nov 21 17:36:44 localhost kernel: wifi0: PRI: id=0x15 v1.1.1
Nov 21 17:36:44 localhost kernel: wifi0: STA: id=0x1f v1.7.4
Nov 21 17:36:44 localhost kernel: wifi0: Intersil Prism2.5 PCI:
mem=0xa0000000, irq=10
Nov 21 17:36:44 localhost kernel: wifi0: registered netdevice wlan0

Nov 21 17:36:44 localhost kernel: hostap_crypt: registered algorithm 'WEP'
Nov 21 17:36:44 localhost kernel: wifi0: registered netdevice wlan0wds0

Nov 21 17:36:44 localhost kernel: wifi0: enabling hostapd mode
Nov 21 17:36:44 localhost kernel: wifi0: registered netdevice wlan0ap
Nov 21 17:36:44 localhost kernel: NET4: Ethernet Bridge 008 for NET4.0
Nov 21 17:36:44 localhost kernel: device wlan0 entered promiscuous mode
Nov 21 17:36:45 localhost kernel: device wlan0wds0 entered promiscuous mode
Nov 21 17:36:45 localhost kernel: wlan0wds0: attempt to add interface with
same source address.
Nov 21 17:36:45 localhost kernel: br0: port 2(wlan0wds0) entering learning
state
Nov 21 17:36:45 localhost kernel: br0: port 1(wlan0) entering learning state
Nov 21 17:36:45 localhost /etc/hotplug/net.agent: invoke ifup br0
Nov 21 17:37:00 localhost kernel: br0: port 2(wlan0wds0) entering forwarding
state
Nov 21 17:37:00 localhost kernel: br0: topology change detected, propagating
Nov 21 17:37:00 localhost kernel: br0: port 1(wlan0) entering forwarding
state
Nov 21 17:37:00 localhost kernel: br0: topology change detected, propagating

Nov 21 18:09:35 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@199388)
Nov 21 18:09:43 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@200192)
Nov 21 18:10:47 localhost kernel: wifi0: TXEXC - status=0x0001 ([RetryErr])
tx_control=000c
Nov 21 18:10:47 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4b08
(Data::0 ToDS FromDS)
Nov 21 18:10:47 localhost kernel:    A1=00:02:6f:05:53:67
A2=00:02:6f:34:e5:eb A3=00:02:6f:05:53:67 A4=00:02:6f:34:e5:eb
Nov 21 18:10:47 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@206580)
Nov 21 18:10:47 localhost kernel: wifi0: RX status=0x2000 (port=0, type=1,
fcserr=0) silence=3 signal=29 rate=20 rxflow=0; jiffies=206600
Nov 21 18:10:47 localhost kernel:    FC=0x4308 (type=2:0) dur=0x0102
seq=0x4110 data_len=60 [ToDS] [FromDS]
Nov 21 18:10:47 localhost kernel:    A1=00:02:6f:34:e5:eb
A2=00:02:6f:05:53:67 A3=00:02:6f:34:e5:eb A4=00:02:6f:05:53:67
Nov 21 18:10:47 localhost kernel:    dst=00:02:6f:34:e5:eb
src=00:02:6f:05:53:67 len=60

Nov 21 18:10:47 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=3 signal=29 rate=20 rxflow=0; jiffies=206638
Nov 21 18:10:47 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x41c0 data_len=47
Nov 21 18:10:47 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=51:c1:45:20:d8:dd
Nov 21 18:10:47 localhost kernel:    dst=b0:fc:ab:ec:31:cf
src=85:d8:9b:0d:ef:8f len=47

Nov 21 18:10:48 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=4 signal=29 rate=20 rxflow=0; jiffies=206740
Nov 21 18:10:48 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4270 data_len=47
Nov 21 18:10:48 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=9d:bd:6b:c9:51:3c
Nov 21 18:10:48 localhost kernel:    dst=45:60:12:91:3a:76
src=e3:6d:e9:d0:1e:79 len=47

Nov 21 18:10:49 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=4 signal=29 rate=20 rxflow=0; jiffies=206842
Nov 21 18:10:49 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4450 data_len=47
Nov 21 18:10:49 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=12:6f:6b:72:11:5c
Nov 21 18:10:49 localhost kernel:    dst=02:ae:bb:32:e2:6c
src=ee:33:2e:ba:8a:99 len=47

Nov 21 18:10:49 localhost kernel: wifi0: RX status=0x2000 (port=0, type=1,
fcserr=0) silence=4 signal=29 rate=20 rxflow=0; jiffies=206842
Nov 21 18:10:49 localhost kernel:    FC=0x4208 (type=2:0) dur=0x0000
seq=0x4460 data_len=86 [FromDS]
Nov 21 18:10:49 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:04:e2:80:48:6e A4=00:4d:7f:b6:25:d6
Nov 21 18:10:49 localhost kernel:    dst=ff:ff:ff:ff:ff:ff
src=00:04:e2:80:48:6e len=86

Nov 21 18:10:50 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=3 signal=30 rate=20 rxflow=0; jiffies=206944
Nov 21 18:10:50 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4750 data_len=47
Nov 21 18:10:50 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=4b:4e:bd:70:f7:8b
Nov 21 18:10:50 localhost kernel:    dst=8f:2b:40:b7:3b:e2
src=fc:74:c8:a3:60:31 len=47

Nov 21 18:10:51 localhost kernel: wifi0: RX status=0x2000 (port=0, type=1,
fcserr=0) silence=4 signal=30 rate=20 rxflow=0; jiffies=207046
Nov 21 18:10:51 localhost kernel:    FC=0x4208 (type=2:0) dur=0x0000
seq=0x4930 data_len=36 [FromDS]
Nov 21 18:10:51 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:66 A4=3a:30:33:3a:32:35
Nov 21 18:10:51 localhost kernel:    dst=ff:ff:ff:ff:ff:ff
src=00:02:6f:05:53:66 len=36

Nov 21 18:10:53 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=4 signal=30 rate=20 rxflow=0; jiffies=207250
Nov 21 18:10:53 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4a10 data_len=47
Nov 21 18:10:53 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=45:e0:be:12:a5:0b
Nov 21 18:10:53 localhost kernel:    dst=ff:d2:48:36:75:35
src=98:66:58:e7:8b:5b len=47


Nov 21 18:10:54 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=4 signal=30 rate=20 rxflow=0; jiffies=207352
Nov 21 18:10:54 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4a60 data_len=47
Nov 21 18:10:54 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=f7:01:b5:a7:58:14
Nov 21 18:10:54 localhost kernel:    dst=ca:39:70:2c:26:41
src=6e:74:5e:09:0c:80 len=47

Nov 21 18:10:56 localhost kernel: wifi0: RX status=0x0000 (port=0, type=0,
fcserr=0) silence=4 signal=29 rate=20 rxflow=0; jiffies=207454
Nov 21 18:10:56 localhost kernel:    FC=0x0080 (type=0:8) dur=0x0000
seq=0x4af0 data_len=47
Nov 21 18:10:56 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:05:53:67 A3=00:02:6f:05:53:67 A4=6e:63:6f:64:69:6e
Nov 21 18:10:56 localhost kernel:    dst=20:67:7a:69:70:2c
src=20:64:65:66:6c:61 len=47

Nov 21 18:12:57 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@219628)
Nov 21 18:14:58 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@231696)

Nov 21 18:15:11 localhost kernel: wifi0: TX status=0x0000 retry_count=0
tx_rate=0 tx_control=0x000c; jiffies=233001
Nov 21 18:15:11 localhost kernel:    FC=0x4208 (type=2:0) dur=0x0000
seq=0x0000 data_len=336 [FromDS]
Nov 21 18:15:11 localhost kernel:    A1=ff:ff:ff:ff:ff:ff
A2=00:02:6f:34:e5:eb A3=00:04:e2:80:65:4f A4=00:00:00:00:00:00
Nov 21 18:15:11 localhost kernel:    dst=00:00:00:00:00:00
src=00:00:00:00:00:00 len=336

Nov 21 18:19:01 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256046)
Nov 21 18:19:02 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256078)
Nov 21 18:19:02 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256089)
Nov 21 18:19:02 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256092)
Nov 21 18:19:02 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256110)
Nov 21 18:19:02 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256141)
Nov 21 18:19:05 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256356)
Nov 21 18:19:08 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256669)
Nov 21 18:19:09 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256756)
Nov 21 18:19:09 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256787)
Nov 21 18:19:09 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256790)
Nov 21 18:19:11 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@256959)
Nov 21 18:19:12 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@257058)
Nov 21 18:19:12 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@257139)
Nov 21 18:19:23 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@258180)
Nov 21 18:19:23 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@258207)
Nov 21 18:19:23 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@258235)
Nov 21 18:19:23 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@258249)
Nov 21 18:20:26 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@264465)
Nov 21 18:21:00 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@267915)
Nov 21 18:21:37 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@271571)
Nov 21 18:21:37 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@271587)
Nov 21 18:21:39 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@271818)
Nov 21 18:21:40 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@271858)
Nov 21 18:21:53 localhost kernel: wifi0: Could not find STA
00:02:6f:05:53:67 for this TX error (@273199)




From andreas  Sun Nov 21 16:30:48 2004
From: andreas (Andreas Schuldei)
Date: Mon, 22 Nov 2004 01:30:48 +0100
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
Message-ID: <20041122003048.GA11581@timotheus.schuldei.org>

Again i experience problems with wpa from my notebook with the
newest madwifi driver from cvs (atheos hardware), my wrt54g
linksys router (new broadcom binary drivers) with sveasoft
alchemy-6.0-rc1.w42 firmware

please look at the attached debug output from wpa_supplicant and
tell me where the problem might be.


root at timotheus:~# wpa_supplicant -i ath0 -D madwifi -d
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 5
   id=0 ssid='Access_Point'
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_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
l2_packet_receive - recv: Network is down
Starting AP scan (broadcast SSID)
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 274 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:0f:66:45:e2:ad ssid='Access_Point' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:0f:66:45:e2:ad (SSID='Access_Point' freq=2462 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
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
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=25
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:66:45:e2:ad
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:66:45:e2:ad
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
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0f:66:45:e2:ad
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 message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 6b 6f af 8f fe 17 4c 0c 24 ae 47 cc 4c 1e ba 47 05 45 d8 0a 86 27 59 f6 ee c3 a1 38 14 84 83 66
WPA: PMK - hexdump(len=32): 80 19 e1 b6 71 25 1c 44 8a 46 d1 84 e7 cf 68 7b 91 b9 c1 c6 a2 09 05 68 e0 3b d6 1f c1 f7 ce f5
WPA: PTK - hexdump(len=64): 3f 43 6c 79 3c 6e 95 f4 6c b8 86 f7 95 e4 31 15 5a 9f 37 6a 2c f2 8b 87 c3 92 fc 43 a0 93 d6 44 96 8b fd 0e fe d8 69 6f d9 44 f4 e6 9a ca d5 d6 95 a1 dc 68 34 58 b3 9d 32 a1 9d 68 a6 fc d8 d6
WPA: EAPOL-Key MIC - hexdump(len=16): 36 3f b5 35 54 86 12 4a ec dd 47 64 f0 6a d7 f9
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0f:66:45:e2:ad
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 message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
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:66:45:e2:ad
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 message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16
WPA: Sending EAPOL-Key 2/2
WPA: Key negotiation completed with 00:0f:66:45:e2:ad
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
EAP: EAP entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
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
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:66:45:e2:ad
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:66:45:e2:ad
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
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0f:66:45:e2:ad
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 message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): ef fa 4e 71 23 9e 85 ca e6 79 91 b2 a0 24 f9 9b 2c 76 23 ed dd f5 9c 5f 12 fb f5 ee 05 f6 08 b1
WPA: PMK - hexdump(len=32): 80 19 e1 b6 71 25 1c 44 8a 46 d1 84 e7 cf 68 7b 91 b9 c1 c6 a2 09 05 68 e0 3b d6 1f c1 f7 ce f5
WPA: PTK - hexdump(len=64): 20 f5 d9 32 a8 e8 b6 3e 5e 55 aa 17 12 c3 5e 4e 2c 54 10 63 9f e3 25 80 e2 83 81 0e 59 14 ca a2 5d a5 88 da 36 1b cd a3 10 5b 95 f6 9d f1 d8 a5 43 31 e9 2d 09 67 6d ef ed 92 1f 91 b3 51 c9 3e
WPA: EAPOL-Key MIC - hexdump(len=16): 77 d7 10 b4 ab 2b dc 1c 37 4a da 39 22 50 d3 56
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0f:66:45:e2:ad
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 message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
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:66:45:e2:ad
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 message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 03 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16
WPA: Sending EAPOL-Key 2/2
WPA: Key negotiation completed with 00:0f:66:45:e2:ad
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
EAP: EAP entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
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
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 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 5
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12





configuration:

root at timotheus:~# cat /etc/wpa_supplicant.conf | egrep -v '^[[:space:]]*#.*|^[[:space:]]*$'
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
        ssid="Access_Point"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk="XXXXXXXXXXXXXX"
        priority=5
}




From jkmaline  Sun Nov 21 18:08:11 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 21 Nov 2004 18:08:11 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041122003048.GA11581@timotheus.schuldei.org>
References: <20041122003048.GA11581@timotheus.schuldei.org>
Message-ID: <20041122020811.GE7013@jm.kir.nu>

On Mon, Nov 22, 2004 at 01:30:48AM +0100, Andreas Schuldei wrote:

> Again i experience problems with wpa from my notebook with the
> newest madwifi driver from cvs (atheos hardware), my wrt54g
> linksys router (new broadcom binary drivers) with sveasoft
> alchemy-6.0-rc1.w42 firmware

I tried to reproduce this with same configuration using CVS version of
madwifi and Satori-4.0 v2.07.1.7sv firmware on WRT54G. However,
everything seemed to work fine with WPA-PSK/CCMP..

Which version of the Broadcom driver is used in the firmware you are
using? You can get this information with 'wl ver'. The one I used has
following version information:

(none):[~]# wl ver
wl:     3.50 RC21.10
        wl0: Jan 21 2004 20:53:00 version 3.50.21.10

Is alchemy-6.0-rc1.w42 firmware available somewhere for testing? I would
need at least wl.o and nas binaries to be able to reproduce the same
test setup.

> root at timotheus:~# wpa_supplicant -i ath0 -D madwifi -d

> WPA: RX message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
> WPA: Installing GTK to the driver (keyidx=1 tx=0).
> WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
> wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16
> WPA: Sending EAPOL-Key 2/2
> WPA: Key negotiation completed with 00:0f:66:45:e2:ad
> Cancelling authentication timeout

Everything looks fine here, i.e., 4-Way and Group Key handshakes were
completed. However..

> 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

Something triggered the driver to generate disconnect event. I would
assume this was Disassociate or Deauthenticate frame from the AP.
Wireless sniffer trace of the authentication attempt could be used to
verify this..

-- 
Jouni Malinen                                            PGP id EFC895FA



From michaelr  Sun Nov 21 19:59:01 2004
From: michaelr (Michael Reilly)
Date: Sun, 21 Nov 2004 19:59:01 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
 Atheros 802.11a/b/g card
In-Reply-To: <20041121050404.GB6980@jm.kir.nu>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
	<419277BA.6020703@cisco.com> <20041121050404.GB6980@jm.kir.nu>
Message-ID: <41A16405.40703@cisco.com>

I just tried 0.12rc3 with my two Atheros cards against a Cisco 1100 AP using 
WPA-PSK.  It failed with both cards.  It may be related to the timing 
related problems you are seeing.  I have been busy at work so haven't had a 
chance to play with this a lot

michael
Jouni Malinen wrote:
> On Wed, Nov 10, 2004 at 12:19:06PM -0800, Michael Reilly wrote:
> 
> 
>>>>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip 
>>>>(5212 I think it is called).  The card has a PCI id of vendor 0x168c, 
>>>>device 0x0013.
>>>>
>>>>wpa_supplicant fails when I try to use WPA-PSK.  I downloaded a trial 
>>>>copy of driverloader and it works fine.
> 
> 
>>	ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added
> 
> 
> I tested with another AR5212-based a/b/g card and the same driver
> version (2.4.2.33) using the current CVS snapshot of ndiswrapper and
> Linux 2.4.28. This worked in my tests with WPA-PSK. In couple of test
> cases with Linksys WRT54G as the AP, it took few attempts to get group
> key handshake completed, though. This may be some kind of timing related
> issue with the client not receiving encrypted frames immediately after
> the keys have been configured. The tests with another AP (Gateway
> 7001ag) were succeeded on the first try. This AP has a longer timeout
> for group key handshake, which could explain the behavior.
> 
> WPA-RADIUS (key_mgmt=WPA+IEEE 802.1X) was not apparently implemented at
> all in ndiswrapper (I would assume it was just forgotten). I added
> support for it and this seemed to allow association and completion of
> IEEE 802.1X + WPA authentication. The attached patch against the
> ndiswrapper CVS was enough to get this working and it would be nice to
> see it being added to the next ndiswrapper release.
> 
> I tested this with both Atheros and Broadcom based cards. There seems to
> be some issues with both cards as far as reliability in getting packets
> through during the authentication is concerned.. Some of the IEEE 802.1X
> packets seem to disappear and I needed to use shorter EAPOL state
> machine timeouts to get authentication more reliable. Another issue was
> the failure in getting group key handshake done in some test runs that I
> mentioned above.
> 

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From sean  Sun Nov 21 19:38:46 2004
From: sean (Sean Faircloth)
Date: Sun, 21 Nov 2004 22:38:46 -0500
Subject: (no subject)
Message-ID: <1101094726.4171.8.camel@localhost.localdomain>

Hi All, I'm new to this list so I apologize if this post is stupid...

I have a D-link 520 air Rev E1 (yes I'm sure) running a freshly compiled
2.6.9 kernel with CONFIG_NET_RADIO=y

[root at localhost hostap-driver-0.2.5]# uname -a
Linux localhost.localdomain 2.6.9 #1 Sun Nov 21 20:42:10 EST 2004 i686
athlon i386 GNU/Linux

[root at localhost hostap-driver-0.2.5]# grep
"NET_RADIO" /usr/src/linux/.config
CONFIG_NET_RADIO=y


I recently downloaded hostap-driver-0.2.5 and compiled and installed it
without error:

make[1]: Leaving directory `/usr/src/linux-2.6.9'
make install_all_info
make[1]: Entering directory `/wireless/hostap-driver-0.2.5'
*** Become superuser and 'make install' to install the modules. ***
make[1]: Leaving directory `/wireless/hostap-driver-0.2.5'
[root at localhost hostap-driver-0.2.5]# make install
make install_check
make[1]: Entering directory `/wireless/hostap-driver-0.2.5'
make[1]: Leaving directory `/wireless/hostap-driver-0.2.5'
*** Copying modules to: /lib/modules/2.6.9/kernel/drivers/net/wireless
mkdir -p /lib/modules/2.6.9/kernel/drivers/net/wireless
cp driver/modules/*.ko /lib/modules/2.6.9/kernel/drivers/net/wireless
*** Running depmod...
[root at localhost hostap-driver-0.2.5]# 

So far so good. but...

[root at localhost hostap-driver-0.2.5]# modprobe hostap_pci
FATAL: Error inserting hostap_pci
(/lib/modules/2.6.9/kernel/drivers/net/wireless/hostap_pci.ko): Unknown
symbol in module, or unknown parameter (see dmesg)



[root at localhost hostap-driver-0.2.5]# dmesg
ersion of symbol hostap_info_process
hostap_pci: Unknown symbol hostap_info_process
hostap_pci: disagrees about version of symbol hostap_set_antsel
hostap_pci: Unknown symbol hostap_set_antsel
hostap_pci: disagrees about version of symbol hostap_setup_dev
hostap_pci: Unknown symbol hostap_setup_dev
hostap_pci: disagrees about version of symbol hostap_init_data
hostap_pci: Unknown symbol hostap_init_data
hostap_pci: disagrees about version of symbol hostap_init_ap_proc
hostap_pci: Unknown symbol hostap_init_ap_proc
hostap_pci: disagrees about version of symbol hostap_set_hostapd_sta
hostap_pci: Unknown symbol hostap_set_hostapd_sta
hostap_pci: disagrees about version of symbol hostap_init_proc
hostap_pci: Unknown symbol hostap_init_proc

and on and on and on.... for symbol hostap_*

Any ideas?


Thanks
--Sean







From michaelr  Sun Nov 21 20:05:32 2004
From: michaelr (Michael Reilly)
Date: Sun, 21 Nov 2004 20:05:32 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041122003048.GA11581@timotheus.schuldei.org>
References: <20041122003048.GA11581@timotheus.schuldei.org>
Message-ID: <41A1658C.7080705@cisco.com>


For me it fails with my Cisco 1100 AP (802.11b) and the latest madwifi from 
CVS.  I am using wpa_supplicant 0.2.5.  It also fails with ndiswrapper 
0.12rc3 for me.  I have two Atheros cards and both fail the same way.

It works with my wrt54gs using satori from sveasoft.  I've not tried alchemy 
yet.

michael
Andreas Schuldei wrote:
> Again i experience problems with wpa from my notebook with the
> newest madwifi driver from cvs (atheos hardware), my wrt54g
> linksys router (new broadcom binary drivers) with sveasoft
> alchemy-6.0-rc1.w42 firmware
> 
> please look at the attached debug output from wpa_supplicant and
> tell me where the problem might be.
> 
> 
> root at timotheus:~# wpa_supplicant -i ath0 -D madwifi -d
> 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 5
>    id=0 ssid='Access_Point'
> 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_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
> l2_packet_receive - recv: Network is down
> Starting AP scan (broadcast SSID)
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 274 bytes of scan results (1 BSSes)
> Scan results: 1
> Selecting BSS from priority group 5
> 0: 00:0f:66:45:e2:ad ssid='Access_Point' wpa_ie_len=24 rsn_ie_len=0
>    selected
> Trying to associate with 00:0f:66:45:e2:ad (SSID='Access_Point' freq=2462 MHz)
> Cancelling scan request
> WPA: using IEEE 802.11i/D3.0
> WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
> 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
> 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=25
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:0f:66:45:e2:ad
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:0f:66:45:e2:ad
> 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
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state CONNECTING
> EAPOL: txStart
> WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
> EAPOL: SUPP_BE entering state IDLE
> EAP: EAP entering state INITIALIZE
> EAP: EAP entering state IDLE
> Setting authentication timeout: 10 sec 0 usec
> RX EAPOL from 00:0f:66:45:e2:ad
> 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 message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
> WPA: Renewed SNonce - hexdump(len=32): 6b 6f af 8f fe 17 4c 0c 24 ae 47 cc 4c 1e ba 47 05 45 d8 0a 86 27 59 f6 ee c3 a1 38 14 84 83 66
> WPA: PMK - hexdump(len=32): 80 19 e1 b6 71 25 1c 44 8a 46 d1 84 e7 cf 68 7b 91 b9 c1 c6 a2 09 05 68 e0 3b d6 1f c1 f7 ce f5
> WPA: PTK - hexdump(len=64): 3f 43 6c 79 3c 6e 95 f4 6c b8 86 f7 95 e4 31 15 5a 9f 37 6a 2c f2 8b 87 c3 92 fc 43 a0 93 d6 44 96 8b fd 0e fe d8 69 6f d9 44 f4 e6 9a ca d5 d6 95 a1 dc 68 34 58 b3 9d 32 a1 9d 68 a6 fc d8 d6
> WPA: EAPOL-Key MIC - hexdump(len=16): 36 3f b5 35 54 86 12 4a ec dd 47 64 f0 6a d7 f9
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:0f:66:45:e2:ad
> 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 message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
> 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:66:45:e2:ad
> 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 message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
> WPA: Installing GTK to the driver (keyidx=1 tx=0).
> WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
> wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16
> WPA: Sending EAPOL-Key 2/2
> WPA: Key negotiation completed with 00:0f:66:45:e2:ad
> 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
> EAP: EAP entering state SUCCESS
> EAPOL: SUPP_PAE entering state AUTHENTICATED
> EAPOL: SUPP_BE entering state IDLE
> 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
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:0f:66:45:e2:ad
> Association event - clear replay counter
> Associated to a new BSS: BSSID=00:0f:66:45:e2:ad
> 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
> EAPOL: External notification - portValid=0
> EAPOL: External notification - EAP success=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state CONNECTING
> EAPOL: txStart
> WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
> EAPOL: SUPP_BE entering state IDLE
> EAP: EAP entering state INITIALIZE
> EAP: EAP entering state IDLE
> Setting authentication timeout: 10 sec 0 usec
> RX EAPOL from 00:0f:66:45:e2:ad
> 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 message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
> WPA: Renewed SNonce - hexdump(len=32): ef fa 4e 71 23 9e 85 ca e6 79 91 b2 a0 24 f9 9b 2c 76 23 ed dd f5 9c 5f 12 fb f5 ee 05 f6 08 b1
> WPA: PMK - hexdump(len=32): 80 19 e1 b6 71 25 1c 44 8a 46 d1 84 e7 cf 68 7b 91 b9 c1 c6 a2 09 05 68 e0 3b d6 1f c1 f7 ce f5
> WPA: PTK - hexdump(len=64): 20 f5 d9 32 a8 e8 b6 3e 5e 55 aa 17 12 c3 5e 4e 2c 54 10 63 9f e3 25 80 e2 83 81 0e 59 14 ca a2 5d a5 88 da 36 1b cd a3 10 5b 95 f6 9d f1 d8 a5 43 31 e9 2d 09 67 6d ef ed 92 1f 91 b3 51 c9 3e
> WPA: EAPOL-Key MIC - hexdump(len=16): 77 d7 10 b4 ab 2b dc 1c 37 4a da 39 22 50 d3 56
> WPA: Sending EAPOL-Key 2/4
> RX EAPOL from 00:0f:66:45:e2:ad
> 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 message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)
> 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:66:45:e2:ad
> 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 message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2)
> WPA: Group Key - hexdump(len=16): 6b 22 bd f8 7c ec ff 29 bd 7b 7c 71 53 1f 78 14
> WPA: Installing GTK to the driver (keyidx=1 tx=0).
> WPA: RSC - hexdump(len=6): 03 00 00 00 00 00
> wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16
> WPA: Sending EAPOL-Key 2/2
> WPA: Key negotiation completed with 00:0f:66:45:e2:ad
> 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
> EAP: EAP entering state SUCCESS
> EAPOL: SUPP_PAE entering state AUTHENTICATED
> EAPOL: SUPP_BE entering state IDLE
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> 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
> 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 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> Wireless event: cmd=0x8b19 len=12
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 5
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (broadcast SSID)
> Wireless event: cmd=0x8b1a len=12
> 
> 
> 
> 
> 
> configuration:
> 
> root at timotheus:~# cat /etc/wpa_supplicant.conf | egrep -v '^[[:space:]]*#.*|^[[:space:]]*$'
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> network={
>         ssid="Access_Point"
>         proto=WPA
>         key_mgmt=WPA-PSK
>         pairwise=CCMP TKIP
>         group=CCMP TKIP WEP104 WEP40
>         psk="XXXXXXXXXXXXXX"
>         priority=5
> }
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From HostAP-Research  Sun Nov 21 21:53:44 2004
From: HostAP-Research (AP-Research)
Date: Sun, 21 Nov 2004 23:53:44 -0600 (CST)
Subject: cardmgr-3.2.7 and hostap-cvs-04.11.20
Message-ID: <33208.67.174.81.186.1101102824.squirrel@67.174.81.186>

After hostap-cvs-04.11.20 `make install` and `service pcmcia restart`
cardmgr begins reporting an error:

cardmgr[2144]: open_sock(socket 2) failed: Bad file descriptor
cardmgr[2144]: watching 2 sockets

I wasn't able to get anything relevant from Google :(  I can't rmmod any
more either ?!?  `service pcmcia stop` returns:

ERROR: Module ds is in use by orinoco_cs,hostap_cs
ERROR: Module pcmcia_core is in use by yenta_socket,orinoco_cs,hostap_cs,ds


My steps were:
1) make linux src
2) make hostap-cvs-04.11.20
3) make install hostap-cvs-04.11.20
4) service pcmcia restart

The only software INSTALLED was HostAP... What diagnostic steps do I take
from here?

Toshiba 5205-S703
SMC2532W-B wlan0 - hostap_cs - private cell
miniPCI Agere wlan1 - orinoco_cs - upstream cell

linux-2.6.9-1.3_FC2
cardmgr version 3.2.7
wireless-tools-26-4
Wireless Extension v16

--
Regards
KC Ferguson CIO/CTO
@RescuNET.com
eXtreme Response Mobile HotSpot



From dennis  Sun Nov 21 22:41:05 2004
From: dennis (Dennis Kaarsemaker)
Date: Mon, 22 Nov 2004 07:41:05 +0100
Subject: Ndiswrapper +wpa_supplicant
In-Reply-To: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
References: <ECOWS02MAk94eMuOKBj0000e764@smtp-out2.blueyonder.co.uk>
Message-ID: <1101105665.4099.5.camel@localhost.localdomain>

On Sun, 2004-11-21 at 13:13 +0000, Andrew Duane wrote:
> My ndis driver is bcmwl5

With that exact same driver, the folowing setup works:
wpa_supplicant 0.2.5
 dennis at raptor ~ $ wpa_supplicant -v
 wpa_supplicant v0.2.5 - Copyright (c) 2003-2004, Jouni Malinen 
 
ndiswrapper from my OS distribution (probably recent version)
 dennis at raptor ~ $ dmesg | grep ndis
 ndiswrapper version 0.10 loaded (preempt=yes,smp=no)
 ndiswrapper: driver bcmwl5.sys (ASUS,07/17/2003, 3.30.15.0) added
 ndiswrapper: using irq 11
 wlan0: ndiswrapper ethernet device 00:0e:a6:9d:ac:09 using driver
 bcmwl5.sys
 ndiswrapper device wlan0 supports WPA with AES/CCMP and TKIP ciphers

The card is Asus Wl100g (PCMCIA) and the driver is the windows 2000
driver since I was warned that the XP driver would not work :)
-- 
Dennis K.
  And that's the way the cookie crumbles!




From andreas  Mon Nov 22 01:44:27 2004
From: andreas (Andreas Schuldei)
Date: Mon, 22 Nov 2004 10:44:27 +0100
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041122020811.GE7013@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
Message-ID: <20041122094427.GB4253@lukas.schuldei.com>

* Jouni Malinen (jkmaline at cc.hut.fi) [041122 03:08]:
> On Mon, Nov 22, 2004 at 01:30:48AM +0100, Andreas Schuldei wrote:
> 
> > Again i experience problems with wpa from my notebook with the
> > newest madwifi driver from cvs (atheos hardware), my wrt54g
> > linksys router (new broadcom binary drivers) with sveasoft
> > alchemy-6.0-rc1.w42 firmware
> 
> I tried to reproduce this with same configuration using CVS version of
> madwifi and Satori-4.0 v2.07.1.7sv firmware on WRT54G. However,
> everything seemed to work fine with WPA-PSK/CCMP..
> 
> Which version of the Broadcom driver is used in the firmware you are
> using? You can get this information with 'wl ver'. The one I used has
> following version information:
> 
> (none):[~]# wl ver
> wl:     3.50 RC21.10
>         wl0: Jan 21 2004 20:53:00 version 3.50.21.10

wl: 3.60 RC13.0
 wl0: Aug 2 2004 14:32:51 version 3.60.13.0

the troubles started when sveasofts firmware moved away from the
satori firmware. they say the new firmware did not allow some
bogus connection modes anymore.

> 
> Is alchemy-6.0-rc1.w42 firmware available somewhere for testing? I would
> need at least wl.o and nas binaries to be able to reproduce the same
> test setup.

i asked exactly that question beforehand. i understand *you* can
get it from them for testing (c:
mail them to info at sveasoft.com to obtain one. 

i will follow up on my old thread in the forum to raise my
concernes. 



From gianni.uglietti  Mon Nov 22 01:49:46 2004
From: gianni.uglietti (Gianni Uglietti)
Date: Mon, 22 Nov 2004 09:49:46 +0000
Subject: HostAP and WPA-PSK - HELP
In-Reply-To: <20041120163404.GC7074@jm.kir.nu>
References: <9cfb17880411190853c29b58b@mail.gmail.com>
	<20041120163404.GC7074@jm.kir.nu>
Message-ID: <9cfb178804112201491d77152a@mail.gmail.com>

You are right Jouni.

The message prompted by AP is: 

STA [MAC address]: No WPA/RSN IE in association request.

As NIC (network interface cards) I'm using a prism54 on the supplicant
and a prism2 on the AP.

What do you really mean by "station firmware"? How can I check it?

Thanks for your support.

Gianni


On Sat, 20 Nov 2004 08:34:04 -0800, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Fri, Nov 19, 2004 at 04:53:43PM +0000, Gianni Uglietti wrote:
> 
> > After starting both hostapd and wpa_suppling, I cannot authenticate my
> > supplicant because for each AP found it says:
> >
> > skip - no WPA/RSN IE
> > No suitable AP found
> 
> > A similar message is prompted also by the AP.
> 
> There is no such message in hostapd. Could you please send the exact
> message from hostapd.
> 
> Which version of the station firmware do you use in the AP and client?
> WPA requires version 1.7.x or newer.
> 
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From andreas  Mon Nov 22 02:55:57 2004
From: andreas (Andreas Schuldei)
Date: Mon, 22 Nov 2004 11:55:57 +0100
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041122020811.GE7013@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
Message-ID: <20041122105557.GA6773@lukas.schuldei.com>

* Jouni Malinen (jkmaline at cc.hut.fi) [041122 03:08]:
> > Again i experience problems with wpa from my notebook with the
> > newest madwifi driver from cvs (atheos hardware), my wrt54g
> > linksys router (new broadcom binary drivers) with sveasoft
> > alchemy-6.0-rc1.w42 firmware
> 
> I tried to reproduce this with same configuration using CVS version of
> madwifi and Satori-4.0 v2.07.1.7sv firmware on WRT54G. However,
> everything seemed to work fine with WPA-PSK/CCMP..

i now tried the Alchemy-6.0-rc3 firmware and it works. it also
has the new broadcom drivers (version in other reply). so we can
rule out thoes and wpa_supplicant as the culpit, i guess and just
blame the alchemy-6.0-rc1.w42 firmware.



From hostap  Mon Nov 22 05:37:24 2004
From: hostap (Joachim Wickman)
Date: Mon, 22 Nov 2004 15:37:24 +0200 (EET)
Subject: Rogue dhcpd
Message-ID: <3323.62.148.199.210.1101130644.squirrel@webmail.tawi.fi>

Hello,

I think hostap allows dhcp/bootp between clients, is this true?
If so, how can I block this?

I'm using Gentoo and HostAP 0.1.2

// Joachim



From jkmaline  Mon Nov 22 06:16:46 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 22 Nov 2004 06:16:46 -0800
Subject: HostAP and WPA-PSK - HELP
In-Reply-To: <9cfb178804112201491d77152a@mail.gmail.com>
References: <9cfb17880411190853c29b58b@mail.gmail.com>
	<20041120163404.GC7074@jm.kir.nu>
	<9cfb178804112201491d77152a@mail.gmail.com>
Message-ID: <20041122141646.GA7013@jm.kir.nu>

On Mon, Nov 22, 2004 at 09:49:46AM +0000, Gianni Uglietti wrote:

> The message prompted by AP is: 
> 
> STA [MAC address]: No WPA/RSN IE in association request.
> 
> As NIC (network interface cards) I'm using a prism54 on the supplicant
> and a prism2 on the AP.

prism54?? That would have been useful information in the first message..
If you mean Prism54.org driver, it does not yet support WPA as the
client..

> What do you really mean by "station firmware"? How can I check it?

Yes, you can see it, e.g., in 'dmesg' output after initializing the
drivers (wifi0: STA: id=0x1f v1.8.3) or with hostap_diag in the utils
package.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 22 06:19:52 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 22 Nov 2004 06:19:52 -0800
Subject: Rogue dhcpd
In-Reply-To: <3323.62.148.199.210.1101130644.squirrel@webmail.tawi.fi>
References: <3323.62.148.199.210.1101130644.squirrel@webmail.tawi.fi>
Message-ID: <20041122141952.GB7013@jm.kir.nu>

On Mon, Nov 22, 2004 at 03:37:24PM +0200, Joachim Wickman wrote:

> I think hostap allows dhcp/bootp between clients, is this true?
> If so, how can I block this?

By default, all traffic, including DHCP, is allowed. If it is ok to
block all direct traffic between the associated clients, you can
disable internal bridge in the driver by setting ap_bridge_packets to 0
(e.g., 'iwpriv wlan0 ap_bridge_packets 0' or 'prism2_param wlan0
ap_bridge_packets 0').

-- 
Jouni Malinen                                            PGP id EFC895FA



From gianni.uglietti  Mon Nov 22 07:51:27 2004
From: gianni.uglietti (Gianni Uglietti)
Date: Mon, 22 Nov 2004 15:51:27 +0000
Subject: HostAP and WPA-PSK - HELP
In-Reply-To: <20041122141646.GA7013@jm.kir.nu>
References: <9cfb17880411190853c29b58b@mail.gmail.com>
	<20041120163404.GC7074@jm.kir.nu>
	<9cfb178804112201491d77152a@mail.gmail.com>
	<20041122141646.GA7013@jm.kir.nu>
Message-ID: <9cfb17880411220751d24d6ce@mail.gmail.com>

Dear Jouni,

sorry for not giving you all the right information. Now I only use
prism2 cards with updated firmware (1.7.4 or 1.8.0).

It seems to work now but I still have a problem. I have 2 laptops
runnins as APs and ons supplicant. I want to roam between the 2 AP but
I have some problems when, after connecting to the second AP, I want
to return to the first. It seems that the AP keeps in memory some keys
but I don't know how to verify it.

Thanks,
Gianni


On Mon, 22 Nov 2004 06:16:46 -0800, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Mon, Nov 22, 2004 at 09:49:46AM +0000, Gianni Uglietti wrote:
> 
> > The message prompted by AP is:
> >
> > STA [MAC address]: No WPA/RSN IE in association request.
> >
> > As NIC (network interface cards) I'm using a prism54 on the supplicant
> > and a prism2 on the AP.
> 
> prism54?? That would have been useful information in the first message..
> If you mean Prism54.org driver, it does not yet support WPA as the
> client..
> 
> > What do you really mean by "station firmware"? How can I check it?
> 
> Yes, you can see it, e.g., in 'dmesg' output after initializing the
> drivers (wifi0: STA: id=0x1f v1.8.3) or with hostap_diag in the utils
> package.
> 
> --
> 
> 
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From ashwinsrao  Mon Nov 22 21:10:05 2004
From: ashwinsrao (Ashwin Rao)
Date: Tue, 23 Nov 2004 05:10:05 -0000
Subject: Beacon Intervals
Message-ID: <20041123050857.26235.qmail@webmail32.rediffmail.com>


Hi,
I am using the hostap driver 0.2.5 on a prism card.
I can increase the beacon interval upto only 4.xxx seconds i.e giving 4096 as a parameter for beacon_int. For values above this it is ineffective, i.e the beacon interval field in the beacon has the value set by the iwpriv command, but the beacons are transmitted in an interval of 0.1 seconds.
Can I set the beacon interval to large values like say 10 seconds, If yes then how? 

Regards,
Ashwin






-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041123/13adfe5a/attachment.htm 


From jkmaline  Mon Nov 22 21:59:11 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 22 Nov 2004 21:59:11 -0800
Subject: Beacon Intervals
In-Reply-To: <20041123050857.26235.qmail@webmail32.rediffmail.com>
References: <20041123050857.26235.qmail@webmail32.rediffmail.com>
Message-ID: <20041123055911.GB7025@jm.kir.nu>

On Tue, Nov 23, 2004 at 05:08:57AM -0000, Ashwin Rao wrote:

> I am using the hostap driver 0.2.5 on a prism card.
> I can increase the beacon interval upto only 4.xxx seconds i.e giving 4096 as a parameter for beacon_int. For values above this it is ineffective, i.e the beacon interval field in the beacon has the value set by the iwpriv command, but the beacons are transmitted in an interval of 0.1 seconds.
> Can I set the beacon interval to large values like say 10 seconds, If yes then how? 

No, this 4096 is the firmware limit for the beacon interval.

-- 
Jouni Malinen                                            PGP id EFC895FA



From seb  Mon Nov 22 22:42:34 2004
From: seb (Sebastian Kaps)
Date: Tue, 23 Nov 2004 07:42:34 +0100
Subject: Question regarding WPA(-PSK)
In-Reply-To: <20041121175917.GB7016@jm.kir.nu> (Jouni Malinen's message of
	"Sun, 21 Nov 2004 09:59:17 -0800")
References: <m3pt275c4r.fsf@toyland.sauerland.de>
	<20041121175917.GB7016@jm.kir.nu>
Message-ID: <m3zn19m5gl.fsf@toyland.sauerland.de>

Hi Jouni!

On Sun, 21 Nov 2004 09:59:17 -0800 you wrote:

> reassociation in my tests with ndiswrapper. Could yu please send
> wpa_suplicant debug log (i.e., do not fork to background with -B and
> add -ddd to command line) for a case where you let it run first for a
> minute or two before running "wpa_cli reassociate"?

I've posted the logfile to this list, but the message exceeded 25 kB and
is now waiting for the mod's approval. So until then, I've also put the
log here: <http://www.sebastian-kaps.de/misc/wpa.log>

-- 
Ciao, Sebastian



From juin.cm89  Tue Nov 23 00:04:16 2004
From: juin.cm89 (Yujuin Liu)
Date: Tue, 23 Nov 2004 16:04:16 +0800
Subject: Path diversity with hostap driver
In-Reply-To: <20041123055911.GB7025@jm.kir.nu>
Message-ID: <20041123080410.9778D3EB7C@mail.ee.ntu.edu.tw>


Hi all,
I am using the hostap driver 0.2.5 on Linksys WPC11v3 (1.7.4), everything is
fine.
Recently I am doing some research about video multicasting in wireless
network.
My question is:
Is it possible for a mobilenode who uses hostap driver to receive multicast
packets from several APs simultaneously, i.e. besides the original
associated AP? If yes, what mode should the mobilenode be set in, and how to
configure the relative parameters? If not, is it possible to revise the
driver in order to achieve the goal? 
Any help is appreciated.  ;-)

Yujuin Liu




From andreas  Tue Nov 23 12:40:28 2004
From: andreas (Andreas Schuldei)
Date: Tue, 23 Nov 2004 21:40:28 +0100
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041122020811.GE7013@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
Message-ID: <20041123204028.GD1457@lukas.schuldei.com>

* Jouni Malinen (jkmaline at cc.hut.fi) [041122 03:08]:
> Is alchemy-6.0-rc1.w42 firmware available somewhere for testing? I would
> need at least wl.o and nas binaries to be able to reproduce the same
> test setup.

i now see very similar problems with Alchemy-6.0-rc3. please do
contact support at sveasoft.com and ask for version for debugging
this thing. like this it is not really usable.



From jkmaline  Tue Nov 23 21:08:21 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 23 Nov 2004 21:08:21 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041123204028.GD1457@lukas.schuldei.com>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
	<20041123204028.GD1457@lukas.schuldei.com>
Message-ID: <20041124050821.GB7030@jm.kir.nu>

On Tue, Nov 23, 2004 at 09:40:28PM +0100, Andreas Schuldei wrote:

> i now see very similar problems with Alchemy-6.0-rc3. please do
> contact support at sveasoft.com and ask for version for debugging
> this thing. like this it is not really usable.

Does the debug log from wpa_supplicant differ from the previous one?
How much time does it take to get the disconnected event after the group
key handshake has been finished? Can you reproduce this same problem
with the latest Linksys firmware (which seems to be using the same newer
version of Broadcom driver)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From oleg  Tue Nov 23 23:22:56 2004
From: oleg (Oleg Borovkov)
Date: Wed, 24 Nov 2004 10:22:56 +0300
Subject: Maximize transfer speed
In-Reply-To: <20041123204329.37D9F2BF54@mail.iocaine.com>
References: <20041123204329.37D9F2BF54@mail.iocaine.com>
Message-ID: <741593519.20041124102256@bal.ru>

Hello,

Please explain me how i can maximize transfer between two WDS mode
prism based bridge?
In this bridged link go various traffic - http, voip, ftp, and other...
now i have next config (it's equal at both side, different only mac):

iwconfig wlan0 channel 14 rate 11M fixed
iwpriv wlan0 wds_add 00:60:B3:01:01:01
iwpriv wlan0 other_ap_policy 0
iwpriv wlan0 host_roaming 2
iwpriv wlan0 enh_sec 3
iwpriv wlan0 maccmd 1
iwpriv wlan0 sens 3
iwpriv wlan0 alc 0
iwpriv wlan0 addmac 00:60:B3:01:01:01
ifconfig eth0 0.0.0.0 up
ifconfig wlan0wds0 0.0.0.0 up
brctl addbr br0
brctl stp   br0 off      
brctl setfd br0 0        
brctl addif br0 eth0     
brctl addif br0 wlan0wds0
ifconfig br0 up
iwpriv wlan0 writemif 62 128
iwconfig wlan0 retry 20     


-- 
Best regards,
 Oleg                            mailto:oleg at bal.ru




From project.9323603  Wed Nov 24 01:42:36 2004
From: project.9323603 (COFM)
Date: Wed, 24 Nov 2004 17:42:36 +0800
Subject: Hold scan results for a period of time
Message-ID: <000501c4d209$f118a7c0$0201a8c0@cofmd120>

Hi!

If i command "# iwlist wlan0 scanning", i can get the scanning results from 
the monitor.
Now i do scan at time1, i can get ap information at that time1.
Later, i do scan again at time2, then i can get new ap information at that 
time2.
It seems that the ap information i got just the results at time2, not 
include the results at time1.
If AP1 is alive at time1, but inactive at time2. Thus i can't get the 
information about AP1 finally.

When i need to do roaming, i want to refer the previous information.
How can i hold the scan results for a period of time?

Any help would be greatly appreciated

Thanks,
Sevesdion 




From peter.decleyn  Wed Nov 24 02:20:57 2004
From: peter.decleyn (Peter De Cleyn)
Date: Wed, 24 Nov 2004 11:20:57 +0100
Subject: Adding generic Information Elements
In-Reply-To: <832b47df041123053810c12247@mail.gmail.com>
References: <832b47df041123053810c12247@mail.gmail.com>
Message-ID: <832b47df041124022059f8f9cd@mail.gmail.com>

Hi list,

I would like to add some own Information Elements (IE) to the
association request and response messages.

A search here and some browsing through the code showed me that
something similar is done when using WPA, (using
prism2_ioctl_set_generic_elment etc) but I still have some questions.

* How do you define where you want to add the new IE (e.g. beacon
frame, asso req, asso res)
* When should this be set: if the IE does not change once or every
time a certain frame is sent
* Is there a performance penalty setting the IE e.g. does one need to
reset the card or something to commit the changes to the firmware.

I understand that in the end a call to hfa384x_set_rid with
HFA384X_RID_GENERICELEMENT is issued. Is there any documentation about
the use of RIDs. If its in the  prism2 driver programmers manual, cold
you please give me some references inside this document as I don't
seem to find what I'm looking for.

These questions might be trivial to you, but I'm quite new to the
field so I could really appreciate some answers.

thanks a lot for reading and hopefully answering these questions!

Peter



From eduardgv  Wed Nov 24 02:25:59 2004
From: eduardgv (eduardgv)
Date: Wed, 24 Nov 2004 11:25:59 +0100
Subject: Hold scan results for a period of time
In-Reply-To: <000501c4d209$f118a7c0$0201a8c0@cofmd120>
References: <000501c4d209$f118a7c0$0201a8c0@cofmd120>
Message-ID: <66c3877d04112402252d0b1caf@mail.gmail.com>

iwlist wlan0 scan >> scan_tmpfile

...sometimes the simplest solution is the best solution, but is often ruled out.




On Wed, 24 Nov 2004 17:42:36 +0800, COFM <project.9323603 at nctu.edu.tw> wrote:
> Hi!
> 
> If i command "# iwlist wlan0 scanning", i can get the scanning results from
> the monitor.
> Now i do scan at time1, i can get ap information at that time1.
> Later, i do scan again at time2, then i can get new ap information at that
> time2.
> It seems that the ap information i got just the results at time2, not
> include the results at time1.
> If AP1 is alive at time1, but inactive at time2. Thus i can't get the
> information about AP1 finally.
> 
> When i need to do roaming, i want to refer the previous information.
> How can i hold the scan results for a period of time?
> 
> Any help would be greatly appreciated
> 
> Thanks,
> Sevesdion
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From manojv  Wed Nov 24 03:08:07 2004
From: manojv (Manoj Verma, Noida)
Date: Wed, 24 Nov 2004 16:38:07 +0530
Subject: Adding generic Information Elements
Message-ID: <267988DEACEC5A4D86D5FCD780313FBB02013510@exch-03.noida.hcltech.com>

See the reply below..

> -----Original Message-----
> From: hostap-bounces+manojv=noida.hcltech.com at shmoo.com [mailto:hostap-
> bounces+manojv=noida.hcltech.com at shmoo.com] On Behalf Of Peter De Cleyn
> Sent: Wednesday, November 24, 2004 3:51 PM
> To: hostAP at shmoo.com
> Subject: Adding generic Information Elements
> 
> Hi list,
> 
> I would like to add some own Information Elements (IE) to the
> association request and response messages.
> 
> A search here and some browsing through the code showed me that
> something similar is done when using WPA, (using
> prism2_ioctl_set_generic_elment etc) but I still have some questions.
> 
> * How do you define where you want to add the new IE (e.g. beacon
> frame, asso req, asso res)

If we are acting as supplicant then this should be added to the association
request frame.

> * When should this be set: if the IE does not change once or every
> time a certain frame is sent

It should be set before sending the join request to the Access point.

> * Is there a performance penalty setting the IE e.g. does one need to
> reset the card or something to commit the changes to the firmware.

I don't think so...

> 
> I understand that in the end a call to hfa384x_set_rid with
> HFA384X_RID_GENERICELEMENT is issued. Is there any documentation about
> the use of RIDs. If its in the  prism2 driver programmers manual, cold
> you please give me some references inside this document as I don't
> seem to find what I'm looking for.
> 

The WPA info element is set using the "cnfWPAData" RID. 


> These questions might be trivial to you, but I'm quite new to the
> field so I could really appreciate some answers.
> 
> thanks a lot for reading and hopefully answering these questions!
> 
> Peter
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap



From project.9323603  Wed Nov 24 03:45:35 2004
From: project.9323603 (COFM)
Date: Wed, 24 Nov 2004 19:45:35 +0800
Subject: Hold scan results for a period of time
Message-ID: <000201c4d21b$1ce47260$0201a8c0@cofmd120>

Thx, i know this command "iwlist wlan0 scan >> scan_tmpfile"
will do redirection from the standard output to file.
But when i do roaming, how can i use these privious data (i.e. 
scan_tmpfile)?
In other words, how can let the driver refer privious scan result for 
roaming ? 




From peter.decleyn  Wed Nov 24 05:26:52 2004
From: peter.decleyn (Peter De Cleyn)
Date: Wed, 24 Nov 2004 14:26:52 +0100
Subject: Adding generic Information Elements
In-Reply-To: <267988DEACEC5A4D86D5FCD780313FBB020133E8@exch-03.noida.hcltech.com>
References: <267988DEACEC5A4D86D5FCD780313FBB020133E8@exch-03.noida.hcltech.com>
Message-ID: <832b47df04112405263614e72f@mail.gmail.com>

> > Hi list,
> >
> > I would like to add some own Information Elements (IE) to the
> > association request and response messages.
> >
> > A search here and some browsing through the code showed me that
> > something similar is done when using WPA, (using
> > prism2_ioctl_set_generic_elment etc) but I still have some questions.
> >
> > * How do you define where you want to add the new IE (e.g. beacon
> > frame, asso req, asso res)
> 
> If we are acting as supplicant then this should be added to the association
> request frame.

Sorry if I was'nt clear enough, but I want to enhance the basic
association process by adding extra IEs and I found some references on
how to add IEs in the WPA supplicant code. driver_hostap.c uses a
ioctl which eventually calls prism2_ioctl_set_generic_element in
hostap_ioctl.c which adds the generic Information Element.


So my first question was how to make sure a certain IE was added to
e.g. the association request (response) sent to a AP (STA).

> 
> > * When should this be set: if the IE does not change once or every
> > time a certain frame is sent
> 
> It should be set before sending the join request to the Access point.
> 

Does this means that the supplied IE will be added to the next
management frame?

> > These questions might be trivial to you, but I'm quite new to the
> > field so I could really appreciate some answers.
> >
> > thanks a lot for reading and hopefully answering these questions!
> >
> > Peter
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
>



From vanja  Wed Nov 24 06:16:27 2004
From: vanja (Vanja Hrustic)
Date: Wed, 24 Nov 2004 15:16:27 +0100
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
Message-ID: <20041124151627.024f18c8.vanja@pobox.com>

Hello!

I've got some Senao SL-2011CD card, and HostAP driver loads fine.

However, I am confused with firwmare versions/revisions.

I have managed to flash STA firmware to version 1.4.9. But primary
firmware is 0.3.0, which seems old, since other cards I've had used 1.0.0
or newer. I wanted to try to update primary firmware file, but I am not
sure which one I need.

hostap driver loads ok:

...
Nov 24 15:01:35 amber cardmgr[8791]: socket 0: Senao
SL-2011CD/SL-2011CDPLUS
Nov 24 15:01:35 amber kernel: hostap_cs: 0.2.5 - 2004-10-03 (Jouni Malinen
<jkmaline at cc.hut.fi>)
Nov 24 15:01:35 amber kernel: hostap_cs: Registered netdevice wifi0
Nov 24 15:01:35 amber kernel: hostap_cs: index 0x01: Vcc 3.3, irq 10, io
0x9100-0x913f
...

This is what hostap_diag shows:

NICID: id=0x8003 v1.0.0 (HWB3163 Rev B, Samsung PC Card Rev. B)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v1.4.9 (station firmware)

I've taken various primary fw files (from
www.red-bean.com/proski/~firmware/), and tried prism2_srec with most of
them.

The only one which didn't report error ("Incompatible update data") was
p10003c0.hex.

However, it seems to be 0.3.0, which I already have.

Is it possible to somehow update primary firwmare to newer version, since
none of the other files would be accepted by prism2_srec?

How much does primary firmware version matter for the functionality of the
Prism 2.5 card?

Thanks.

Vanja



From jkmaline  Wed Nov 24 07:24:52 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 24 Nov 2004 07:24:52 -0800
Subject: Hold scan results for a period of time
In-Reply-To: <000501c4d209$f118a7c0$0201a8c0@cofmd120>
References: <000501c4d209$f118a7c0$0201a8c0@cofmd120>
Message-ID: <20041124152452.GA7013@jm.kir.nu>

On Wed, Nov 24, 2004 at 05:42:36PM +0800, COFM wrote:

> If i command "# iwlist wlan0 scanning", i can get the scanning results from 
> the monitor.

> If AP1 is alive at time1, but inactive at time2. Thus i can't get the 
> information about AP1 finally.
> 
> When i need to do roaming, i want to refer the previous information.
> How can i hold the scan results for a period of time?

Why would you like to use information about AP that is not "active" when
selecting roaming target?

However, if you mean that the firmware scan missed an AP that is still
active and in range at time2, you might want to test the current
development snapshot. I modified scanning code couple of days ago to use
the in-driver BSS list to fill in missing APs when reporting scan
results. This requires new STA f/w (1.7.x or newer) and WPA enabled
(e.g., when running wpa_supplicant). This BSS list has somewhat longer
lifetime, so couple of missed packets should not make an AP disappear
from the scan results.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Nov 24 07:31:58 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 24 Nov 2004 07:31:58 -0800
Subject: Question regarding WPA(-PSK)
In-Reply-To: <m3zn19m5gl.fsf@toyland.sauerland.de>
References: <m3pt275c4r.fsf@toyland.sauerland.de>
	<20041121175917.GB7016@jm.kir.nu>
	<m3zn19m5gl.fsf@toyland.sauerland.de>
Message-ID: <20041124153158.GB7013@jm.kir.nu>

On Tue, Nov 23, 2004 at 07:42:34AM +0100, Sebastian Kaps wrote:

> I've posted the logfile to this list, but the message exceeded 25 kB and
> is now waiting for the mod's approval. So until then, I've also put the
> log here: <http://www.sebastian-kaps.de/misc/wpa.log>

As far as wpa_supplicant is concerned, this log shows two successful
authentications. As such, this is likely to be more on topic for
ndiswrapper mailing list. I don't think there's much wpa_supplicant
could do about this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jar  Wed Nov 24 07:56:54 2004
From: jar (Jar)
Date: Wed, 24 Nov 2004 17:56:54 +0200 (EET)
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
In-Reply-To: <20041124151627.024f18c8.vanja@pobox.com>
References: <20041124151627.024f18c8.vanja@pobox.com>
Message-ID: <51844.194.157.0.2.1101311814.squirrel@194.157.0.2>


> I have managed to flash STA firmware to version 1.4.9. But primary
> firmware is 0.3.0, which seems old, since other cards I've had used 1.0.0
> or newer. I wanted to try to update primary firmware file, but I am not
> sure which one I need.

Seems to be a Prism2 card. I think that the primary fw 0.3.0 is just ok, there is no
newer version. I am using 1.5.6 STA fw from www.red-bean.com/proski/~firmware/ for
my prism2 card:

NICID: id=0x8002 v1.0.1 (HWB3163-01,02,03,04 Rev A)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v1.5.6 (station firmware)

There is also v1.7.1 version (s1010701.hex) in www.red-bean.com/proski/~firmware/
but it doesn't work as goog as the v1.5.6 for me.

However I flashed my card by using Windows utility because prism2_srec complains
some incompatibility issues when I tried to update to v1.5.6 or v1.7.1.

-- 
Best Regards, Jar



From seb  Wed Nov 24 08:57:19 2004
From: seb (Sebastian Kaps)
Date: Wed, 24 Nov 2004 17:57:19 +0100
Subject: Question regarding WPA(-PSK)
In-Reply-To: <20041124153158.GB7013@jm.kir.nu> (Jouni Malinen's message of
	"Wed, 24 Nov 2004 07:31:58 -0800")
References: <m3pt275c4r.fsf@toyland.sauerland.de>
	<20041121175917.GB7016@jm.kir.nu>
	<m3zn19m5gl.fsf@toyland.sauerland.de>
	<20041124153158.GB7013@jm.kir.nu>
Message-ID: <m3act7mbgw.fsf@toyland.sauerland.de>

Hi Jouni!

> As far as wpa_supplicant is concerned, this log shows two successful
> authentications. As such, this is likely to be more on topic for
> ndiswrapper mailing list. I don't think there's much wpa_supplicant
> could do about this.

Thanks for your answer. I'll ask the ndiswrapper guys then...

-- 
Ciao, Sebastian



From michaelr  Wed Nov 24 14:44:07 2004
From: michaelr (Michael Reilly)
Date: Wed, 24 Nov 2004 14:44:07 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041124050821.GB7030@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>	<20041122020811.GE7013@jm.kir.nu>	<20041123204028.GD1457@lukas.schuldei.com>
	<20041124050821.GB7030@jm.kir.nu>
Message-ID: <41A50EB7.5020005@cisco.com>

Considering that the same config but using a Cisco 1100 or 1200 Access Point 
exhibits the same behavior I would guess that there may be a generic timing 
or similar problem instead of something specific to the newer Broadcom 
wireless driver.

I am using the same identical config but with a D-Link 802.11A/B/G access 
point and it works perfectly.

michael
Jouni Malinen wrote:
> On Tue, Nov 23, 2004 at 09:40:28PM +0100, Andreas Schuldei wrote:
> 
> 
>>i now see very similar problems with Alchemy-6.0-rc3. please do
>>contact support at sveasoft.com and ask for version for debugging
>>this thing. like this it is not really usable.
> 
> 
> Does the debug log from wpa_supplicant differ from the previous one?
> How much time does it take to get the disconnected event after the group
> key handshake has been finished? Can you reproduce this same problem
> with the latest Linksys firmware (which seems to be using the same newer
> version of Broadcom driver)?
> 

-- 
---- ---- ----
Michael Reilly    michaelr at cisco.com
     Cisco Systems,  California



From andreas  Wed Nov 24 14:52:49 2004
From: andreas (Andreas Schuldei)
Date: Wed, 24 Nov 2004 23:52:49 +0100
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041124050821.GB7030@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
	<20041123204028.GD1457@lukas.schuldei.com>
	<20041124050821.GB7030@jm.kir.nu>
Message-ID: <20041124225249.GA13048@lukas.schuldei.com>

* Jouni Malinen (jkmaline at cc.hut.fi) [041124 06:09]:
> On Tue, Nov 23, 2004 at 09:40:28PM +0100, Andreas Schuldei wrote:
> 
> > i now see very similar problems with Alchemy-6.0-rc3. please do
> > contact support at sveasoft.com and ask for version for debugging
> > this thing. like this it is not really usable.
> 
> Does the debug log from wpa_supplicant differ from the previous one?
> How much time does it take to get the disconnected event after the group
> key handshake has been finished? Can you reproduce this same problem
> with the latest Linksys firmware (which seems to be using the same newer
> version of Broadcom driver)?

if it is a timing problem (as suggested in the mail in this
thread) how can i procude debug output with timing information?




From billtorvalds1  Wed Nov 24 23:25:24 2004
From: billtorvalds1 (leonardo)
Date: Thu, 25 Nov 2004 08:25:24 +0100
Subject: understanding the code.
In-Reply-To: <20041120081041.GE28407@informatik.uni-rostock.de>
References: <20041119195437.GA3525@queneau>
	<20041120081041.GE28407@informatik.uni-rostock.de>
Message-ID: <20041125072524.GA3087@queneau>

* Saturday 20 November 2004, alle 09:10, Gunter Burchardt scrive:
> On 2004-11-19 - 20:54:37, leonardo wrote:
> 
> > I need to understand if I interpreted the code in a correct way: when a
> > frame is received it is handled by handle_frame(), if it's a data packet
> > it passes through handle_data() and then, if it's a EAP packet it goes to
> > ieee802_1x_receive(). If it's a EAPOL packet it will interfere with EAPOL
> > state machine, otherwise if it's a EAP packet we have to forward it to
> > RADIUS right? 
> >
> > something I don't understand it's why it handle just "eap response"
> > packet and not every EAP packet, then in handle_eap_response() I can't see
> > how that packet is treated, there's no direct call to any radius function.
> > is it handled by the state machine in the main loop?


there's a copuple of things I miss.. 

main initializes one interface.hapd[i] for phisical interface (just one
for me). this calls init_driver_hostap() which calls driver_init() which calls
init_sockets() which increments eloop.readers_count. So we have one
eloop.reader[] for interface, and one eloop.reader[].sock to listen to.
in eloop_run() we whatch this socket and pass the data it receives to the
correct handler. right?

upon receival of a frame handlers call each other untill we get 
to 802_1x_receive() that does this:

sta = ap_get_sta(hapd, sa);
[...]
eapol_sm_step(sta->eapol_sm);

so we have an authenticator state machine for every station, and a new
station is initialized with hostapd_new_assoc_sta(), which I guess it is
exectued at the moment of a new association. 

back to EAPOL sm: the authenticator state machine (which I
suppose is the one specified in the standard) changes from the
connecting to the authenticating state when it receives EAPOL-Start frame.

case IEEE802_1X_TYPE_EAPOL_START:
[...]
		sta->eapol_sm->auth_pae.eapolStart = TRUE;
		sta->eapol_sm->dot1xAuthEapolStartFramesRx++;
		eapol_sm_step(sta->eapol_sm);

this happens just for EAPOL_START frames. for generic EAP frames we have:

case IEEE802_1X_TYPE_EAP_PACKET:
[...]
        handle_eap(hapd, sta, (u8 *) (hdr + 1), datalen);

in handle_eap(), as I said before we have:

switch (eap->code) {
00712         case EAP_CODE_REQUEST:
00713                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (request)\n");
00714                 return;
00715         case EAP_CODE_RESPONSE:
00716                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (response)\n");
00717                 handle_eap_response(hapd, sta, eap, (u8 *) (eap + 1), eap_len);
00718                 break;
00719         case EAP_CODE_SUCCESS:
00720                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (success)\n");
00721                 return;
00722         case EAP_CODE_FAILURE:
00723                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (failure)\n");
00724                 return;
00725         default:
00726                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (unknown code)\n");
00727                 return;

which means that we handle EAP_RESPONSES and we don't do anything on
everything else. in handle_eap_response() we set a few parameters on the
sm but we don't make it run, neither we send any RADIUS packet. I guess
the RADIUS packet is sent (shouldn't we forward EAP packets to
authentication server?) afterwards when something which I still don't know
makes the sm run.

so the question remains: why do we handle just EAP_RESPONSE packets? what
do we do with the rest? 

some more: when we initialize a new sm we pass from the states
initialize->disconnected->restart->connecting almost withouth
intervention. to pass to the authenticating state we need eapReq=1 and
I can't see where this is set, since in the code we just set eapolStart.

thanks everybody for attention, I hope I'll soon pay back with some
contribution.
leonardo.

-- 
GPG fingerprint = 2C20 A587 05AC 42E5 1292  D0D4 3EED CFB5 52FD AD1E



From reeopp  Thu Nov 25 03:56:29 2004
From: reeopp (pepe perez)
Date: Thu, 25 Nov 2004 12:56:29 +0100
Subject: problem with madwifi drivers
Message-ID: <BAY13-F5E5FF97DE26E2B8CEBE9BD2B90@phx.gbl>

Hi there!!!

First of all I must say I have only been running SuSE on my laptop for 2 
months so I'm a total newbie (just as a warning)

I'm trying t set up WPA_supplicant 0.2.5 with madwifi drivers (cvs 
20041021). I have compiled the madwifi drives properly (I think!!) according 
to web page:

http://madwifiwiki.thewebhost.de/wiki/MadwifiConceptronicC54COnRedHat9

and they seem to work:

Nov 25 12:23:50 dhcppc0 kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 
0002)
Nov 25 12:23:50 dhcppc0 kernel: ath_pci: cache line size not set; forcing 32
Nov 25 12:23:50 dhcppc0 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 4.6
Nov 25 12:23:50 dhcppc0 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Nov 25 12:23:50 dhcppc0 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 
6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Nov 25 12:23:50 dhcppc0 kernel: ath0: 802.11 address: 00:80:5a:22:11:78
Nov 25 12:23:50 dhcppc0 kernel: ath0: Atheros 5212: mem=0x10800000, irq=11
Nov 25 12:23:50 dhcppc0 kernel: Vendor = 0x168c   id=0x13 subsys: -1

I have also configure the .config for the wpa_supplicant:


CONFIG_DRIVER_MADWIFI=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_LEAP=y
CONFIG_PCSC=y

I've updated the make file to look for the madwifi drivers

ifdef CONFIG_DRIVER_MADWIFI
CFLAGS += -DCONFIG_DRIVER_MADWIFI
CFLAGS += -I/usr/src/madwifi		# change to reflect local setup
OBJS += driver_madwifi.o
CONFIG_WIRELESS_EXTENSION=y
endif

everything seemed to compile properly (I don't have any log sorry). I did 
update the wpa_supplicant.conf file in /etc:

network={
ssid="mylan"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
priority=1
psk="mypassword"
}

but when I try to start supplicant:

dhcppc0:/home/oscar/wpa_supplicant-0.2.5 # wpa_supplicant -iwlan0 
-c/etc/wpa_supplicant.conf -d
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 1
   id=0 ssid='xxxxxxxx'
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[SIOCGIFINDEX]: No such device
wpa_driver_madwifi_set_wpa: enabled=0
ioctl[IEEE80211_IOCTL_SETOPTIE]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
Failed to disable WPA in the driver.
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
wpa_driver_madwifi_set_countermeasures: enabled=0
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
SIOCGIFFLAGS: No such device
dhcppc0:/home/oscar/wpa_supplicant-0.2.5 #

I suspected from the line "wpa_driver_madwifi_set_wpa: enabled=0" and Ive 
been searching for any information in the form, in fact there is a similar 
problem in september "Atheros 5212 and WPA issues" but I didn't fin any 
solution on there...

Does anybody have any idea???? A I told you I'm quite new and I'm pretty 
lost!!!
thanks anyway!
Oscar

Other info which may help: I'm running SuSE9.1 with kernel 2.6.4-52.. If you 
need any other information, please let me know!

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/




From manojv  Thu Nov 25 03:55:34 2004
From: manojv (Manoj Verma, Noida)
Date: Thu, 25 Nov 2004 17:25:34 +0530
Subject: Adding generic Information Elements
Message-ID: <267988DEACEC5A4D86D5FCD780313FBB020AB2E9@exch-03.noida.hcltech.com>



>-----Original Message-----
>From: Peter De Cleyn [mailto:peter.decleyn at gmail.com]
>Sent: Wednesday, November 24, 2004 6:57 PM
>To: Manoj Verma, Noida
>Cc: hostap at shmoo.com
>Subject: Re: Adding generic Information Elements
>
>> > Hi list,
>> >
>> > I would like to add some own Information Elements (IE) to the
>> > association request and response messages.
>> >
>> > A search here and some browsing through the code showed me that
>> > something similar is done when using WPA, (using
>> > prism2_ioctl_set_generic_elment etc) but I still have some questions.
>> >
>> > * How do you define where you want to add the new IE (e.g. beacon
>> > frame, asso req, asso res)
>>
>> If we are acting as supplicant then this should be added to the
>association
>> request frame.
>
>Sorry if I was'nt clear enough, but I want to enhance the basic
>association process by adding extra IEs and I found some references on
>how to add IEs in the WPA supplicant code. driver_hostap.c uses a
>ioctl which eventually calls prism2_ioctl_set_generic_element in
>hostap_ioctl.c which adds the generic Information Element.
>
>
>So my first question was how to make sure a certain IE was added to
>e.g. the association request (response) sent to a AP (STA).
>
I think one way is to sniff the packets you are sending.
Second way I can think of is enabling debug at the access point side and see
the association frame it has received.
I will be interested in knowing other ways.

>>
>> > * When should this be set: if the IE does not change once or every
>> > time a certain frame is sent
>>
>> It should be set before sending the join request to the Access point.
>>
>
>Does this means that the supplied IE will be added to the next
>management frame?

YES ...
>
>> > These questions might be trivial to you, but I'm quite new to the
>> > field so I could really appreciate some answers.
>> >
>> > thanks a lot for reading and hopefully answering these questions!
>> >
>> > Peter
>> > _______________________________________________
>> > HostAP mailing list
>> > HostAP at shmoo.com
>> > http://lists.shmoo.com/mailman/listinfo/hostap
>>



From jar  Thu Nov 25 04:48:15 2004
From: jar (Jar)
Date: Thu, 25 Nov 2004 14:48:15 +0200 (EET)
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
In-Reply-To: <20041125131152.1ec00a59.vanja@pobox.com>
References: <20041124151627.024f18c8.vanja@pobox.com>
	<51844.194.157.0.2.1101311814.squirrel@194.157.0.2>
	<20041125131152.1ec00a59.vanja@pobox.com>
Message-ID: <54116.194.157.0.2.1101386895.squirrel@194.157.0.2>


> What are your experiences, then, with Prism2 card? Is it running stable?

Very good with 1.5.6 fw, stays stable/up/running several months 24h/a day. With
1.7.1 fw it works generally ok, but Link Quality and dBm values (reported by
iwconfig) seemed to be totally useless (radomize). For me it is important to know
how good/bad the link currently is.

With 1.7.1 it should be possible to use "Hide SSID" and "WPA" features.


-- 
Best Regards, Jar



From rok.papez  Thu Nov 25 04:59:53 2004
From: rok.papez (Rok Papez)
Date: Thu, 25 Nov 2004 13:59:53 +0100
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F5E5FF97DE26E2B8CEBE9BD2B90@phx.gbl>
References: <BAY13-F5E5FF97DE26E2B8CEBE9BD2B90@phx.gbl>
Message-ID: <200411251359.53348.rok.papez@arnes.si>

Dne ?etrtek 25 november 2004 12:56 je pepe perez napisal(a):

> dhcppc0:/home/oscar/wpa_supplicant-0.2.5 # wpa_supplicant -iwlan0 
> -c/etc/wpa_supplicant.conf -d

Does it work with a "-D madwifi" switch ?

-- 
lep pozdrav,
Rok Pape?.



From yenjung  Thu Nov 25 05:20:22 2004
From: yenjung (YenJung Chang)
Date: Thu, 25 Nov 2004 21:20:22 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F5E5FF97DE26E2B8CEBE9BD2B90@phx.gbl>
References: <BAY13-F5E5FF97DE26E2B8CEBE9BD2B90@phx.gbl>
Message-ID: <32653c970411250520c57f178@mail.gmail.com>

AFAIK, the interface name of madwifi is "ath0", hence, the interface
in your command should be -iath0, not -iwlan0.

yj.



On Thu, 25 Nov 2004 12:56:29 +0100, pepe perez <reeopp at hotmail.com> wrote:
> Hi there!!!
> 
> First of all I must say I have only been running SuSE on my laptop for 2
> months so I'm a total newbie (just as a warning)
> 
> I'm trying t set up WPA_supplicant 0.2.5 with madwifi drivers (cvs
> 20041021). I have compiled the madwifi drives properly (I think!!) according
> to web page:
> 
> http://madwifiwiki.thewebhost.de/wiki/MadwifiConceptronicC54COnRedHat9
> 
> and they seem to work:
> 
> Nov 25 12:23:50 dhcppc0 kernel: PCI: Enabling device 0000:03:00.0 (0000 ->
> 0002)
> Nov 25 12:23:50 dhcppc0 kernel: ath_pci: cache line size not set; forcing 32
> Nov 25 12:23:50 dhcppc0 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 4.6
> Nov 25 12:23:50 dhcppc0 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> Nov 25 12:23:50 dhcppc0 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> Nov 25 12:23:50 dhcppc0 kernel: ath0: 802.11 address: 00:80:5a:22:11:78
> Nov 25 12:23:50 dhcppc0 kernel: ath0: Atheros 5212: mem=0x10800000, irq=11
> Nov 25 12:23:50 dhcppc0 kernel: Vendor = 0x168c   id=0x13 subsys: -1
> 
> I have also configure the .config for the wpa_supplicant:
> 
> CONFIG_DRIVER_MADWIFI=y
> CONFIG_WIRELESS_EXTENSION=y
> CONFIG_IEEE8021X_EAPOL=y
> CONFIG_EAP_MD5=y
> CONFIG_MSCHAPV2=y
> CONFIG_EAP_TLS=y
> CONFIG_EAP_PEAP=y
> CONFIG_EAP_TTLS=y
> CONFIG_EAP_GTC=y
> CONFIG_EAP_OTP=y
> CONFIG_EAP_SIM=y
> CONFIG_EAP_AKA=y
> CONFIG_EAP_PSK=y
> CONFIG_EAP_LEAP=y
> CONFIG_PCSC=y
> 
> I've updated the make file to look for the madwifi drivers
> 
> ifdef CONFIG_DRIVER_MADWIFI
> CFLAGS += -DCONFIG_DRIVER_MADWIFI
> CFLAGS += -I/usr/src/madwifi            # change to reflect local setup
> OBJS += driver_madwifi.o
> CONFIG_WIRELESS_EXTENSION=y
> endif
> 
> everything seemed to compile properly (I don't have any log sorry). I did
> update the wpa_supplicant.conf file in /etc:
> 
> network={
> ssid="mylan"
> scan_ssid=1
> proto=WPA
> key_mgmt=WPA-PSK
> pairwise=TKIP
> group=TKIP
> priority=1
> psk="mypassword"
> }
> 
> but when I try to start supplicant:
> 
> dhcppc0:/home/oscar/wpa_supplicant-0.2.5 # wpa_supplicant -iwlan0
> -c/etc/wpa_supplicant.conf -d
> 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 1
>    id=0 ssid='xxxxxxxx'
> 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[SIOCGIFINDEX]: No such device
> wpa_driver_madwifi_set_wpa: enabled=0
> ioctl[IEEE80211_IOCTL_SETOPTIE]: No such device
> ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
> ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
> ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
> Failed to disable WPA in the driver.
> wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
> wpa_driver_madwifi_set_countermeasures: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
> SIOCGIFFLAGS: No such device
> dhcppc0:/home/oscar/wpa_supplicant-0.2.5 #
> 
> I suspected from the line "wpa_driver_madwifi_set_wpa: enabled=0" and Ive
> been searching for any information in the form, in fact there is a similar
> problem in september "Atheros 5212 and WPA issues" but I didn't fin any
> solution on there...
> 
> Does anybody have any idea???? A I told you I'm quite new and I'm pretty
> lost!!!
> thanks anyway!
> Oscar
> 
> Other info which may help: I'm running SuSE9.1 with kernel 2.6.4-52.. If you
> need any other information, please let me know!
> 
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From david.goodenough  Thu Nov 25 05:24:56 2004
From: david.goodenough (David Goodenough)
Date: Thu, 25 Nov 2004 13:24:56 +0000
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
In-Reply-To: <54116.194.157.0.2.1101386895.squirrel@194.157.0.2>
References: <20041124151627.024f18c8.vanja@pobox.com>
	<20041125131152.1ec00a59.vanja@pobox.com>
	<54116.194.157.0.2.1101386895.squirrel@194.157.0.2>
Message-ID: <200411251324.57015.david.goodenough@btconnect.com>

On Thursday 25 November 2004 12:48, Jar wrote:
> > What are your experiences, then, with Prism2 card? Is it running stable?
>
> Very good with 1.5.6 fw, stays stable/up/running several months 24h/a day.
> With 1.7.1 fw it works generally ok, but Link Quality and dBm values
> (reported by iwconfig) seemed to be totally useless (radomize). For me it
> is important to know how good/bad the link currently is.
>
> With 1.7.1 it should be possible to use "Hide SSID" and "WPA" features.
There is also a 1.8.0 which seems to run very well as far as I can see.

David



From wilson_kyip2  Thu Nov 25 05:34:46 2004
From: wilson_kyip2 (Ip wilson)
Date: Thu, 25 Nov 2004 21:34:46 +0800 (CST)
Subject: How to get the beacon frame in managed mode
Message-ID: <20041125133446.88107.qmail@web41725.mail.yahoo.com>

Dear all,
   I am doing a project for a indoor positioning system by using hostap to get the information 
of the received beacon frames from multiple AP. I have modified the wlansniff program in hostap-0.0.4 a 
little to captured the beacon frames from the raw socket.
        It work well when I switched the card into monitor mode and master mode ! But I cannot get 
anythings for the beacon frames in managed mode. I am interested to know whether it is possible to get 
the beacon frame for my positioning system when the card is in managed mode. It 's because I am 
building some location-aware application project and the user should probably use the managed mode to 
join some AP.
  Thank for attention ;-)
 
Wilson Ip


---------------------------------
????????Games ?????
?? Yahoo! Messenger
http://messenger.yahoo.com.hk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041125/25befc9f/attachment.htm 


From st3v3  Thu Nov 25 05:53:07 2004
From: st3v3 (st3v3 at btinternet.com)
Date: Thu, 25 Nov 2004 13:53:07 +0000 (GMT)
Subject: hostapd(cvs) & madwifi(cvs)
Message-ID: <20041125135307.18885.qmail@web86106.mail.ukl.yahoo.com>

Hi all
Im trying to get hostapd(cvs) to run with madwifi(cvs)
on one radio and also hostap-driver on another radio.
Im trying to get 802.1x EAP/TLS to work with madwifi.
I belive I am missing some fundamental IOCTL calls to
get this to work correctly. Im using 2.4.28 with
Wireless Extensions 16.
In order to get the missing IOCTL calls I belive I
need to get WE18 working.
I have tried to copy wireless.h(v18) and iw_handler.h
(v6) replacing those in the kernel. But have run into
some problems doing it this way.
The hostap driver file hostap.c(line 930) in
driver/modules refers to dev->wiresless_data from the
linux/netdevices.h file. If WE greater than 16. The
definiton of wireless_data I cant find anywhere in any
flavour of the linux kernel. :( not even in the 2.6.x
kernel tree or in a WE patch.
Please correct me if I have mis-understood the
interaction between hostap-driver/hostapd/madwifi and
WE18.
Does anyone have a patch for WE18 on 2.4.28??
I do understand that WE17 & WE18 have not been
released yet.
Am i missing something?
Regards
Steve




From jar  Thu Nov 25 06:16:08 2004
From: jar (Jar)
Date: Thu, 25 Nov 2004 16:16:08 +0200 (EET)
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
In-Reply-To: <200411251324.57015.david.goodenough@btconnect.com>
References: <20041124151627.024f18c8.vanja@pobox.com>
	<20041125131152.1ec00a59.vanja@pobox.com>
	<54116.194.157.0.2.1101386895.squirrel@194.157.0.2>
	<200411251324.57015.david.goodenough@btconnect.com>
Message-ID: <60943.194.157.0.2.1101392168.squirrel@194.157.0.2>


> There is also a 1.8.0 which seems to run very well as far as I can see.

Where? Flash or ram version? At least the firmware in
http://www.red-bean.com/proski/firmware/1.8.0.tar.gz seems to be only for prism2.5.

-- 
Best Regards, Jar



From reeopp  Thu Nov 25 06:21:46 2004
From: reeopp (pepe perez)
Date: Thu, 25 Nov 2004 15:21:46 +0100
Subject: problem with madwifi drivers
Message-ID: <BAY13-F32C9E61C449FBE6326B666D2B90@phx.gbl>

Hi YenJung!
I think I already tried it, anyway I have just tried again and not so much 
difference:

dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
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 1
   id=0 ssid='OSCARLAN'
Using existing control interface directory.
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_madwifi_set_wpa: enabled=1
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
Failed to enable WPA in the driver.
wpa_driver_madwifi_set_wpa: enabled=0
ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
Failed to disable WPA in the driver.
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
wpa_driver_madwifi_set_countermeasures: enabled=0
ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
Control interface directory not empty - leaving it behind

It looks like something else is going on, meybe in configuration or 
compilation....

Thanks a lot for your help!!!
Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: pepe perez <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Thu, 25 Nov 2004 21:20:22 +0800
>
>AFAIK, the interface name of madwifi is "ath0", hence, the interface
>in your command should be -iath0, not -iwlan0.
>
>yj.
>
>
>

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




From david.goodenough  Thu Nov 25 06:29:57 2004
From: david.goodenough (David Goodenough)
Date: Thu, 25 Nov 2004 14:29:57 +0000
Subject: prism2_srec and HWB3163 Rev B, Samsung PC Card Rev. B
In-Reply-To: <60943.194.157.0.2.1101392168.squirrel@194.157.0.2>
References: <20041124151627.024f18c8.vanja@pobox.com>
	<200411251324.57015.david.goodenough@btconnect.com>
	<60943.194.157.0.2.1101392168.squirrel@194.157.0.2>
Message-ID: <200411251429.57434.david.goodenough@btconnect.com>

On Thursday 25 November 2004 14:16, Jar wrote:
> > There is also a 1.8.0 which seems to run very well as far as I can see.
>
> Where? Flash or ram version? At least the firmware in
> http://www.red-bean.com/proski/firmware/1.8.0.tar.gz seems to be only for
> prism2.5.
My apologies, you are right, I use Senao cards which are 2.5, and I assumed
that this version was also available for other Prism types.

David



From jkmaline  Thu Nov 25 06:55:37 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 25 Nov 2004 06:55:37 -0800
Subject: How to get the beacon frame in managed mode
In-Reply-To: <20041125133446.88107.qmail@web41725.mail.yahoo.com>
References: <20041125133446.88107.qmail@web41725.mail.yahoo.com>
Message-ID: <20041125145537.GA7013@jm.kir.nu>

On Thu, Nov 25, 2004 at 09:34:46PM +0800, Ip wilson wrote:

>         It work well when I switched the card into monitor mode and master mode ! But I cannot get 
> anythings for the beacon frames in managed mode. I am interested to know whether it is possible to get 
> the beacon frame for my positioning system when the card is in managed mode. It 's because I am 
> building some location-aware application project and the user should probably use the managed mode to 
> join some AP.

Yes, this information is needed for WPA, too, and the latest station
firmware versions (1.7.x and newer) have option for allowing the driver
to receive Beacon frames. The current version of the driver (both
0.3.x and 0.2.x branches) use this whenever WPA mode is enabled (by
running wpa_supplicant and manually with "iwpriv wlan0 wpa 1").

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Nov 25 07:00:56 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 25 Nov 2004 07:00:56 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <41A50EB7.5020005@cisco.com>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
	<20041123204028.GD1457@lukas.schuldei.com>
	<20041124050821.GB7030@jm.kir.nu> <41A50EB7.5020005@cisco.com>
Message-ID: <20041125150056.GB7013@jm.kir.nu>

On Wed, Nov 24, 2004 at 02:44:07PM -0800, Michael Reilly wrote:

> Considering that the same config but using a Cisco 1100 or 1200 Access 
> Point exhibits the same behavior I would guess that there may be a generic 
> timing or similar problem instead of something specific to the newer 
> Broadcom wireless driver.

How much time it takes to get disconnected event after the group key
handshake was finished? Ideally, I would like to see wireless sniffer
trace showing whether the disconnection was caused by the AP sending
deauth or disassoc frame to the station. Other option would be that
madwifi driver decided for some reason (e.g., missed beacons) that the
AP was not there anymore. Adding/Enabling some debug code in madwifi
should show if this is the cause.

-- 
Jouni Malinen                                            PGP id EFC895FA



From capacity77  Thu Nov 25 08:04:02 2004
From: capacity77 (capacity77 at tin.it)
Date: Thu, 25 Nov 2004 17:04:02 +0100
Subject: mode MASTER
Message-ID: <41538C5B000493F3@ims6a.cp.tin.it>

Hi list!
I wanted to ask one thing: if I don't have hostap and with iwconfig I set
the mode to MASTER, what does it happen, thath my wireless card works as
an Access Point?
If so, which is the difference between this situation and the hostap?
Thanks a lot
Dom




From shawn_adams  Thu Nov 25 08:58:17 2004
From: shawn_adams (Shawn Adams)
Date: Thu, 25 Nov 2004 17:58:17 +0100
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F32C9E61C449FBE6326B666D2B90@phx.gbl>
References: <BAY13-F32C9E61C449FBE6326B666D2B90@phx.gbl>
Message-ID: <41A60F29.1090906@web.de>




Same issue on my machine.

Kernel is 2.4.20, SuSE distr. otherwise, madwifi works fine.

wpa_supplicant is 0.2.5


pepe perez wrote:
> Hi YenJung!
> I think I already tried it, anyway I have just tried again and not so 
> much difference:
> 
> dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> 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 1
>   id=0 ssid='OSCARLAN'
> Using existing control interface directory.
> 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_madwifi_set_wpa: enabled=1
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Failed to enable WPA in the driver.
> wpa_driver_madwifi_set_wpa: enabled=0
> ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Failed to disable WPA in the driver.
> wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> wpa_driver_madwifi_set_countermeasures: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Control interface directory not empty - leaving it behind
> 
> It looks like something else is going on, meybe in configuration or 
> compilation....
> 
> Thanks a lot for your help!!!
> Oscar
> 
>> From: YenJung Chang <yenjung at gmail.com>
>> Reply-To: YenJung Chang <yenjung at gmail.com>
>> To: pepe perez <reeopp at hotmail.com>
>> CC: hostap at shmoo.com
>> Subject: Re: problem with madwifi drivers
>> Date: Thu, 25 Nov 2004 21:20:22 +0800
>>
>> AFAIK, the interface name of madwifi is "ath0", hence, the interface
>> in your command should be -iath0, not -iwlan0.
>>
>> yj.
>>
>>
>>
> 
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search! 
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 


-- 
Shawn Adams
shawn_adams at web.de




From gbur  Thu Nov 25 09:00:49 2004
From: gbur (Gunter Burchardt)
Date: Thu, 25 Nov 2004 18:00:49 +0100
Subject: hostapd(cvs) & madwifi(cvs)
In-Reply-To: <20041125135307.18885.qmail@web86106.mail.ukl.yahoo.com>
References: <20041125135307.18885.qmail@web86106.mail.ukl.yahoo.com>
Message-ID: <20041125170049.GF28407@informatik.uni-rostock.de>

> Hi all
> Im trying to get hostapd(cvs) to run with madwifi(cvs)
> on one radio and also hostap-driver on another radio.
> Im trying to get 802.1x EAP/TLS to work with madwifi.
> I belive I am missing some fundamental IOCTL calls to
> get this to work correctly. Im using 2.4.28 with
> Wireless Extensions 16.
> In order to get the missing IOCTL calls I belive I
> need to get WE18 working.
> I have tried to copy wireless.h(v18) and iw_handler.h
> (v6) replacing those in the kernel. But have run into
> some problems doing it this way.
> The hostap driver file hostap.c(line 930) in
> driver/modules refers to dev->wiresless_data from the
> linux/netdevices.h file. If WE greater than 16. The
> definiton of wireless_data I cant find anywhere in any
> flavour of the linux kernel. :( not even in the 2.6.x
> kernel tree or in a WE patch.
> Please correct me if I have mis-understood the
> interaction between hostap-driver/hostapd/madwifi and
> WE18.
> Does anyone have a patch for WE18 on 2.4.28??
> I do understand that WE17 & WE18 have not been
> released yet.
> Am i missing something?

You don't need hostap-driver for atheros based cards. You need madwifi
driver and hostapd! You have to enable madwifi support in hostapd. Its
documented in the readme file. Be sure that all madwifi modules are
loaded (ath_hal, ath_pci, wlan, wlan_crypt_tkip, ...). On some
plattforms autoload of crypt modules doesn't work.

regards
gunter



From gbur  Thu Nov 25 09:38:18 2004
From: gbur (Gunter Burchardt)
Date: Thu, 25 Nov 2004 18:38:18 +0100
Subject: understanding the code.
In-Reply-To: <20041125072524.GA3087@queneau>
References: <20041119195437.GA3525@queneau>
	<20041120081041.GE28407@informatik.uni-rostock.de>
	<20041125072524.GA3087@queneau>
Message-ID: <20041125173818.GG28407@informatik.uni-rostock.de>

> there's a copuple of things I miss.. 
> 
> main initializes one interface.hapd[i] for phisical interface (just one
> for me). this calls init_driver_hostap() which calls driver_init() which calls
> init_sockets() which increments eloop.readers_count. So we have one
> eloop.reader[] for interface, and one eloop.reader[].sock to listen to.
> in eloop_run() we whatch this socket and pass the data it receives to the
> correct handler. right?

Yes. Hostapd is single threaded. Each action is caused by eloop.
Received data on sockets in only one thing a handler function is
called. Secondly you can register functions that will be called after a
specific time!

> upon receival of a frame handlers call each other untill we get 
> to 802_1x_receive() that does this:
> 
> sta = ap_get_sta(hapd, sa);
> [...]
> eapol_sm_step(sta->eapol_sm);
> 
> so we have an authenticator state machine for every station, and a new
> station is initialized with hostapd_new_assoc_sta(), which I guess it is
> exectued at the moment of a new association. 

Yes, yes, yes! :)

> back to EAPOL sm: the authenticator state machine (which I
> suppose is the one specified in the standard) changes from the
> connecting to the authenticating state when it receives EAPOL-Start frame.

Yes. Read IEEE802.1x standard. Its free (and very long). You will find
state machine there!
 
> case IEEE802_1X_TYPE_EAPOL_START:
> [...]
> 		sta->eapol_sm->auth_pae.eapolStart = TRUE;
> 		sta->eapol_sm->dot1xAuthEapolStartFramesRx++;
> 		eapol_sm_step(sta->eapol_sm);
> 
> this happens just for EAPOL_START frames. for generic EAP frames we have:
> 
> case IEEE802_1X_TYPE_EAP_PACKET:
> [...]
>         handle_eap(hapd, sta, (u8 *) (hdr + 1), datalen);
> 
> in handle_eap(), as I said before we have:
> 
> switch (eap->code) {
> 00712         case EAP_CODE_REQUEST:
> 00713                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (request)\n");
> 00714                 return;
> 00715         case EAP_CODE_RESPONSE:
> 00716                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (response)\n");
> 00717                 handle_eap_response(hapd, sta, eap, (u8 *) (eap + 1), eap_len);
> 00718                 break;
> 00719         case EAP_CODE_SUCCESS:
> 00720                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (success)\n");
> 00721                 return;
> 00722         case EAP_CODE_FAILURE:
> 00723                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (failure)\n");
> 00724                 return;
> 00725         default:
> 00726                 HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, " (unknown code)\n");
> 00727                 return;
> 
> which means that we handle EAP_RESPONSES and we don't do anything on
> everything else. in handle_eap_response() we set a few parameters on the
> sm but we don't make it run, neither we send any RADIUS packet. I guess
> the RADIUS packet is sent (shouldn't we forward EAP packets to
> authentication server?) afterwards when something which I still don't know
> makes the sm run.

Well, you set some sm parameters for:
ieee802_1x.c:   sm->eapolEap = TRUE;

In ieee802_1x_receive() at the end eapol_sm_step(sta->eapol_sm) is
called for each packet. The sm parameters causes BE_AUTH state machine
to change state (or not).


sm->eapolEAP is TRUE for Response packets.

look at following code in eapol_sm.c:

        case BE_AUTH_REQUEST:
                if (sm->eapolEap)
                        SM_ENTER(BE_AUTH, RESPONSE);
                else if (sm->be_auth.eapReq)
                        SM_ENTER(BE_AUTH, REQUEST);
                else if (sm->eapTimeout)
                        SM_ENTER(BE_AUTH, TIMEOUT);
                break;

BE_AUTH is in state BE_AUTH_REQUEST (awaiting an answer). If eapolEAP
is set the state is changed to RESPONSE.

> so the question remains: why do we handle just EAP_RESPONSE packets? what
> do we do with the rest?

Which rest do you mean eapol_sm_step() is called for each eap packet. So
the changed sm parameters can cause state change of sm state machine!

> some more: when we initialize a new sm we pass from the states
> initialize->disconnected->restart->connecting almost withouth
> intervention. to pass to the authenticating state we need eapReq=1 and
> I can't see where this is set, since in the code we just set eapolStart.

eapReq is set to TRUE in ieee802_1x.c.

regards
gunter



From st3v3  Thu Nov 25 10:07:57 2004
From: st3v3 (Steve)
Date: Thu, 25 Nov 2004 18:07:57 +0000
Subject: hostapd(cvs) & madwifi(cvs)
In-Reply-To: <20041125170049.GF28407@informatik.uni-rostock.de>
References: <20041125135307.18885.qmail@web86106.mail.ukl.yahoo.com>
	<20041125170049.GF28407@informatik.uni-rostock.de>
Message-ID: <1101406077.8050.21.camel@localhost>

Hi Gunther
Thanks for replying.
I do understand that for atheros based cards you need the madwifi
driver. I would like to use the 802.1x authenticator from hostapd on my
atheros card AND on the prism card with the hostap-driver. Two radios as
two APs. 
Currently I have the prism card successfully working with hostapd and
802.1x. Im looking now to get the same functionality on the other radio
(i,e the atheros card with 5212 silicon).

I can confirm that the drive_madwifi.c does compile.
I have the ath_hal and ath_pci loaded.
I also have wlan and wlan_xauth loaded. I dont have wlan_crypt_tkip
loaded however I thought wlan_xauth from madwifi allowed the use of an
external authenticator. i.e hostapd??

I currently have the .config file in hostapd with
CONFIG_DRIVER_MADWIFI=y
and an additional include path for my kernel source.

I also have the hostapd.conf file for the madwifi. 
802.1x EAP/TLS does work from the the prism card so other than
driver=madwifi.,bridge=br0 and the interface name (ath0) they are the
same.

Am I right in thinking that the combination of hostapd & madwifi with
802.1x EAP/TLS authentication does require WE18?

Regards
	Steve

> 
> You don't need hostap-driver for atheros based cards. You need madwifi
> driver and hostapd! You have to enable madwifi support in hostapd. Its
> documented in the readme file. Be sure that all madwifi modules are
> loaded (ath_hal, ath_pci, wlan, wlan_crypt_tkip, ...). On some
> plattforms autoload of crypt modules doesn't work.
> 
> regards
> gunter
-- 
Steve <st3v3 at btinternet.com>




From gbur  Thu Nov 25 10:31:25 2004
From: gbur (Gunter Burchardt)
Date: Thu, 25 Nov 2004 19:31:25 +0100
Subject: hostapd(cvs) & madwifi(cvs)
In-Reply-To: <1101406077.8050.21.camel@localhost>
References: <20041125135307.18885.qmail@web86106.mail.ukl.yahoo.com>
	<20041125170049.GF28407@informatik.uni-rostock.de>
	<1101406077.8050.21.camel@localhost>
Message-ID: <20041125183125.GH28407@informatik.uni-rostock.de>

On 2004-11-25 - 18:07:57, Steve wrote:
> Subject: Re: hostapd(cvs) & madwifi(cvs)
> From: Steve <st3v3 at btinternet.com>
> To: Gunter Burchardt <gbur at informatik.uni-rostock.de>
> Cc: Hostap Mailing list <hostap at shmoo.com>
> Date: Thu, 25 Nov 2004 18:07:57 +0000
> X-Mailer: Evolution 2.0.2 
> 
> Hi Gunther
> Thanks for replying.
> I do understand that for atheros based cards you need the madwifi
> driver. I would like to use the 802.1x authenticator from hostapd on my
> atheros card AND on the prism card with the hostap-driver. Two radios as
> two APs. 
> Currently I have the prism card successfully working with hostapd and
> 802.1x. Im looking now to get the same functionality on the other radio
> (i,e the atheros card with 5212 silicon).

You can start hostapd with more than one config:
hostapd config1.conf config2.conf ... configN.conf
 
> I can confirm that the drive_madwifi.c does compile.
> I have the ath_hal and ath_pci loaded.
> I also have wlan and wlan_xauth loaded. I dont have wlan_crypt_tkip
> loaded however I thought wlan_xauth from madwifi allowed the use of an
> external authenticator. i.e hostapd??

Yes! You need wlan_tkip and/or wlan_ccmp loaded depending on your
hostapd config (wlan_crypt_tkip was the wrong name). Normaly these
modules should be loaded automaticaly if needed. But on some plattforms
it fails. 

> I currently have the .config file in hostapd with
> CONFIG_DRIVER_MADWIFI=y
> and an additional include path for my kernel source.

Yes! This is nessesary!

> I also have the hostapd.conf file for the madwifi. 
> 802.1x EAP/TLS does work from the the prism card so other than
> driver=madwifi.,bridge=br0 and the interface name (ath0) they are the
> same.

Everythink seems ok - what is the problem? What says hostapd log (start
with hostapd -ddd /your/path/to/config). One issue is that you have to
set essid with iwconfig. Set mode to master by iwconfig is a good idea
too.
 
> Am I right in thinking that the combination of hostapd & madwifi with
> 802.1x EAP/TLS authentication does require WE18?

I think you doesn't need WE18. It works with 2.4.26 and WE16 for my
own.

regards
gunter




From naik  Thu Nov 25 19:34:09 2004
From: naik (Vinayak Naik)
Date: Thu, 25 Nov 2004 22:34:09 -0500 (EST)
Subject: Installing hostap on Apple Powerbook
Message-ID: <Pine.GSO.4.40.0411252233100.22428-100000@nu.cis.ohio-state.edu>

Hi,

Has anybody installed hostap drive on Apple's Powerbook?

Thanks,

- Vinayak




From yenjung  Fri Nov 26 01:12:44 2004
From: yenjung (YenJung Chang)
Date: Fri, 26 Nov 2004 17:12:44 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F32C9E61C449FBE6326B666D2B90@phx.gbl>
References: <BAY13-F32C9E61C449FBE6326B666D2B90@phx.gbl>
Message-ID: <32653c97041126011245c5cbf6@mail.gmail.com>

OK....
I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules, right?

Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
all in net80211 directory.

yj.


On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com> wrote:
> Hi YenJung!
> I think I already tried it, anyway I have just tried again and not so much
> difference:
> 
> dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> 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 1
>    id=0 ssid='OSCARLAN'
> Using existing control interface directory.
> 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_madwifi_set_wpa: enabled=1
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Failed to enable WPA in the driver.
> wpa_driver_madwifi_set_wpa: enabled=0
> ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Failed to disable WPA in the driver.
> wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> wpa_driver_madwifi_set_countermeasures: enabled=0
> ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> Control interface directory not empty - leaving it behind
> 
> It looks like something else is going on, meybe in configuration or
> compilation....
> 
> Thanks a lot for your help!!!
> Oscar
> 
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: pepe perez <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Thu, 25 Nov 2004 21:20:22 +0800
> >
> >AFAIK, the interface name of madwifi is "ath0", hence, the interface
> >in your command should be -iath0, not -iwlan0.
> >
> >yj.
> >
> >
> >
> 
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> 
>



From romanol  Fri Nov 26 01:16:21 2004
From: romanol (Romano Giannetti)
Date: Fri, 26 Nov 2004 10:16:21 +0100
Subject: Problem setting keys with ndiswrapper after authentication?
Message-ID: <20041126091621.GA14791@pern.dea.icai.upco.es>


Hi. I have a problem with wpa_supplicant that is driving me crazy; I think
that I am very near to the success but I am blocked by this last problem. If
I manage to solve this up, I *promise* I'll wrote a little HOWTO... (bribing
mode...)

Well. I have ndiswrapper installed (last version, 0.12rc3), with a realtek
ndis5 driver version 173. 

First of all, I set essid manually (no way to obtain this in scan mode, so I
disabled it) and "up" the interface 

Script started on Wed 24 Nov 2004 12:33:37 PM CET
[root at rukbat wifi]# iwconfig wlan0 mode managed essid upco_wlan key 0 open
[root at rukbat wifi]# iwconfig wlan0 && ifconfig wlan0
wlan0     IEEE 802.11b  ESSID:"upco_wlan"  
          Mode:Managed  Frequency:2.427GHz  Access Point: 00:11:5C:77:82:40  
          Bit Rate:11Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:2432 B   Fragment thr:2432 B   
          Encryption key:00   Security mode:open
          Power Management:off
          Link Quality:100/100  Signal level:-59 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr 00:0B:9D:00:B2:6E  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:120 (120.0 b)  TX bytes:0 (0.0 b)
          Interrupt:9 Memory:10800000-108000ff 

The configuration file is here (password deleted)

          
[root at rukbat wifi]# cat /etc/wpa_supplicant.conf | egrep -v "^#"

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
network={
        ssid="upco_wlan"
	key_mgmt=IEEE8021X
 	eap=PEAP
	identity="romano at upcont.es"
	password="-------"
	phase2="auth=MSCHAPV2"
	priority=1
}

Then I start wpa_supplicant --- a version with a little modification; I added 

        fprintf(stderr, "key data: key_idx=%d set_tx=%d\n", key_idx, set_tx);

        fprintf(stderr, "trying to set key...\n");
	if ((a=iw_set_ext(ifname, WPA_SET_KEY, &priv_req)) < 0)
		ret = -1;
        fprintf(stderr, "result of iw_set_ext, RESULT %d\n", a);
        
in wpa_ndiswrapper_set_key(), obtaining (I will comment with a leading *****
the logs, so that you can skip this rapidly...) 

[root at rukbat wifi]# ./wpa_supplicant-0.2.5/wpa_supplicant -Dndiswrapper \
   -iwlan0  -c/etc/wpa_supplicant.conf -dd
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=0
Line: 191 - start of a new network block
SSID - hexdump_ascii(len=9):
     75 70 63 6f 5f 77 6c 61 6e                        upco_wlan       
key_mgmt: 0x8
eap methods - hexdump(len=2): 19 00
identity - hexdump_ascii(len=16):
     72 6f 6d 61 6e 6f 40 75 70 63 6f 6e 74 2e 65 73   romano at upcont.es
password - hexdump_ascii(len=9):

*****     [removed]

phase2=auth=MSCHAPV2
priority=1
Priority group 1
   id=0 ssid='upco_wlan'
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
key data: key_idx=0 set_tx=0
trying to set key...
result of iw_set_ext, RESULT 0
key data: key_idx=1 set_tx=0
trying to set key...
result of iw_set_ext, RESULT 0
key data: key_idx=2 set_tx=0
trying to set key...
result of iw_set_ext, RESULT 0
key data: key_idx=3 set_tx=0
trying to set key...
result of iw_set_ext, RESULT 0

***** setting keys seems to work...

Setting scan request: 0 sec 100000 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=00:11:5c:6b:8f:20

***** [more successfull setting keys removed] 

Network configuration found for the current AP
EAPOL: External notification - portControl=Auto
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING

***** [lot of handshaking removed, available on request]

EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=75) - Flags 0x01
EAP-PEAP: received 69 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=32): 01 e9 00 20 1a 01 e9 00 1b 10 5b 0c 40 a0 d7 0b 7c 83 94 fa 20 81 8a 4a 18 f6 45 4f 4c 49 4f 4e
EAP-PEAP: received Phase 2: code=1 identifier=233 length=32
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received challenge
EAP-MSCHAPV2: Authentication Servername - hexdump_ascii(len=6):
     45 4f 4c 49 4f 4e                                 EOLION          
EAP-MSCHAPV2: Generating Challenge Response
EAP-MSCHAPV2: auth_challenge - hexdump(len=16): 5b 0c 40 a0 d7 0b 7c 83 94 fa 20 81 8a 4a 18 f6
EAP-MSCHAPV2: peer_challenge - hexdump(len=16): 96 8f 28 d6 ef 19 6d eb 33 57 1b 75 3c 78 00 80
EAP-MSCHAPV2: username - hexdump_ascii(len=16):
     72 6f 6d 61 6e 6f 40 75 70 63 6f 6e 74 2e 65 73   romano at upcont.es
EAP-MSCHAPV2: password - hexdump_ascii(len=9):

***** removed password 

EAP-MSCHAPV2: response - hexdump(len=24): 75 78 05 02 b9 b5 aa b7 b7 d1 18 47 47 db 50 6e 75 e8 06 a7 ad 01 6a 5e
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=75): 02 e9 00 4b 1a 02 e9 00 46 31 96 8f 28 d6 ef 19 6d eb 33 57 1b 75 3c 78 00 80 00 00 00 00 00 00 00 00 75 78 05 02 b9 b5 aa b7 b7 d1 18 47 47 db 50 6e 75 e8 06 a7 ad 01 6a 5e 00 72 6f 6d 61 6e 6f 40 75 70 63 6f 6e 74 2e 65 73
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=162): 00 11 5c 6b 8f 20 00 0b 9d 00 b2 6e 88 8e 01 00 00 90 02 e9 00 90 19 01 17 03 01 00 20 66 ca c7 76 8d 99 00 9f 94 2e 61 0e 3b 50 50 db 98 40 e3 f8 e3 41 7a ed 90 35 8a f3 2c 05 f6 cf 17 03 01 00 60 8e 9c 7d e3 3f 50 8c a5 79 51 c8 d3 a3 3f 9e 6b 5b 13 b8 d8 49 d4 e8 37 cd f1 58 aa 61 31 5d 97 12 65 c0 d0 e5 27 84 1e fb 58 ab fb ac 9e da 42 53 a4 eb 54 f4 4f 03 fd 73 0a 16 24 b8 1d c3 c4 98 79 ce 3a 24 7d 8b cf dc ca 71 79 26 a0 fc a9 cd 66 27 bd f1 f3 a9 3f 14 30 de d8 3e ce a2 b4
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 79, expecting at least 99
RX EAPOL from 00:11:5c:6b:8f:20
RX EAPOL - hexdump(len=95): 01 00 00 5b 01 ea 00 5b 19 01 17 03 01 00 50 e5 18 7f b5 b3 45 69 12 f5 f4 32 bc f3 ea 9f 8a 39 6f 85 77 58 eb 65 21 e9 5a b4 f2 87 7c 21 86 a4 6d e3 db b3 16 a8 c7 ab ac 00 55 17 5c cf 0b 04 16 2d 7a 81 81 83 a6 48 59 41 ab 09 89 ec 62 36 9d 0e 6d c0 f0 60 44 83 a3 af d2 03 82 4c 7a
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=234
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=91) - Flags 0x01
EAP-PEAP: received 85 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=51): 01 ea 00 33 1a 03 e9 00 2e 53 3d 33 31 42 44 42 32 38 37 38 42 37 44 42 34 35 42 39 35 30 42 30 32 34 43 30 38 35 41 34 45 38 45 46 35 35 33 38 46 42 35
EAP-PEAP: received Phase 2: code=1 identifier=234 length=51
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received success
EAP-MSCHAPV2: Success message - hexdump(len=0):
EAP-MSCHAPV2: Authentication succeeded

***** So it's all ok, or not? It seems to authenticate correctly!

EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 ea 00 06 1a 03
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 11 5c 6b 8f 20 00 0b 9d 00 b2 6e 88 8e 01 00 00 50 02 ea 00 50 19 01 17 03 01 00 20 c3 bb f6 20 a1 fd c5 0f 3c 9e 6c 68 d5 40 d7 c1 f0 88 7e 58 09 b1 86 c1 f7 b2 35 50 c5 48 aa 10 17 03 01 00 20 e2 cc ff 70 6e d8 0a c1 0d 7f bb cc 85 8b 59 0e 10 15 11 1f 90 c3 00 82 1f 7f 19 e7 21 2b cb 05
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 95, expecting at least 99
RX EAPOL from 00:11:5c:6b:8f:20
RX EAPOL - hexdump(len=47): 01 00 00 2b 01 eb 00 2b 19 01 17 03 01 00 20 5a 58 1d 70 85 74 29 f1 01 dd 7e ff 85 57 0b a3 b7 8e 3f 2f d2 8d ae 01 70 83 0c 41 c0 a0 bc c6
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=235
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=43) - Flags 0x01
EAP-PEAP: received 37 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=11): 01 eb 00 0b 21 80 03 00 02 00 01
EAP-PEAP: received Phase 2: code=1 identifier=235 length=11
EAP-PEAP: Phase 2 Request: type=33
EAP-PEAP: Received TLVs - hexdump(len=6): 80 03 00 02 00 01
EAP-PEAP: Result TLV - hexdump(len=2): 00 01
EAP-PEAP: TLV Result - Success - EAP-PEAP/Phase2 Completed
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): 02 eb 00 0b 21 80 03 00 02 00 01
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 11 5c 6b 8f 20 00 0b 9d 00 b2 6e 88 8e 01 00 00 50 02 eb 00 50 19 01 17 03 01 00 20 fa 25 f6 15 40 74 62 d2 6b 8f e8 8c e2 0d 39 ed 74 09 01 52 14 34 73 5f 9d 2b 8c 9e af 61 37 03 17 03 01 00 20 70 9d 4a f4 a1 8d e9 be ac 8c 9b 19 a1 a6 83 37 0f 4c 19 6d 65 cb 1b 89 1b f5 ee 59 31 24 54 b2
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 47, expecting at least 99
RX EAPOL from 00:11:5c:6b:8f:20
RX EAPOL - hexdump(len=46): 01 00 00 04 03 eb 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state SUCCESS
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:5c:6b:8f:20
RX EAPOL - hexdump(len=61): 01 03 00 39 01 00 0d 00 00 41 a4 71 e1 00 09 98 e7 2e ff e2 83 9c a2 06 11 7e 1d 41 0d 8b c3 00 bf 80 38 ee c6 55 e9 c1 cb 9c c4 81 7b 97 14 ec 30 9e f6 36 4a aa c0 88 a6 95 36 38 7b
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1 key_length=13 key_index=0x0
EAPOL: EAPOL-Key key signature verified
EAPOL: Decrypted(RC4) key - hexdump(len=13): 13 ab d7 39 ef 08 e0 bc 63 a7 d1 a8 b9
EAPOL: Setting dynamic WEP key: broadcast keyidx 0 len 13
key data: key_idx=0 set_tx=0
trying to set key...
result of iw_set_ext, RESULT -1

***** HERE is the fault!!!

EAPOL: Failed to set WEP key to the  driver.
WPA: EAPOL frame too short, len 61, expecting at least 99
EAPOL: Port Timers tick - authWhile=29 heldWhile=0 startWhen=29 idleWhile=59
EAPOL: Port Timers tick - authWhile=28 heldWhile=0 startWhen=28 idleWhile=58
EAPOL: Port Timers tick - authWhile=27 heldWhile=0 startWhen=27 idleWhile=57
Signal 2 received - terminating
***** [more successfull setting keys removed] 
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0


Well, if anyone can help me on this, me and the whole (little but growing)
linux community at my University will forever ever be grateful. 

Thank you very much, 	
                        Romano 


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



From st3v3  Fri Nov 26 01:16:47 2004
From: st3v3 (st3v3 at btinternet.com)
Date: Fri, 26 Nov 2004 09:16:47 +0000 (GMT)
Subject: hostapd(cvs) & madwifi(cvs)
Message-ID: <20041126091647.18459.qmail@web86108.mail.ukl.yahoo.com>

Hey Gunter
Just to continue with this problem.
I have now tried loading the modules wlan_tkip,
wlan_ccmp. Im still having the same behaviour.
I have some provided some additonal info in this
email.

hostap_pci hostap_pci: cvs251104 - 2004-11-25 (Jouni
Malinen <jkmaline at cc.hut.fi>)
hostap_pci: Registered netdevice wifi0
wifi0: NIC: id=0x8022 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.5.6
wifi0: Intersil Prism2.5 PCI: mem=0xa0000000, irq=9
 
ath_pci Warning: loading
/lib/modules/2.4.28-sc1100/net/ath_hal.o will taint
the kernel:ath_hal: 0.9.12.14 ( non-GPL licenseAR5210
- Proprietary
, AR5211, AR5212)
wlan: 0.8.4.4 (EXPERIMENTAL)
ath_rate_onoe: 1.0
ath_pci: 0.9.4.11 (EXPERIMENTAL)
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: mac 5.6 phy 4.1 radio 1.7
ath0: 802.11 address: 00:02:6f:53:11:74
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
wrap1C-000DB9000A7C:~# lsmod
Module                  Size  Used by    Tainted: P
wlan_xauth               560   0  (unused)
wlan_ccmp               3904   0  (unused)
wlan_tkip               8144   0  (unused)
wlan_wep                3584   3  (autoclean)
hostap_crypt_wep        3552   3  (autoclean)
bridge                 21992   1  (autoclean)
ath_pci                35884   0
ath_rate_onoe           3872   0  [ath_pci]
wlan                   77348   1  [wlan_xauth
wlan_ccmp wlan_tkip wlan_wep ath_pci ath_rate_onoe]
ath_hal               118896   1  [ath_pci]
hostap_pci             39972   3
hostap                 88712   0  [hostap_crypt_wep
hostap_pci]
 
wrap1C-000DB9000A7C:~# hostapd -dddd
/rw/etc/hostapd.ath0.conf
Configuration file: /rw/etc/hostapd.ath0.conf
mbr0: port 3(ath0) entering learning state
adwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:02:6f:53:1setmlme
#01:mlme->im_op=3
1:74 and ssid 'awap_ap_madwifi'
ath0: RADIUS Authentication server 10.0.0.242:1812
madwifi_set_ieee8021x: enabled=1
madwifi_set_iface_flags: dev_up=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=0
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=2
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=3
IEEE 802.1X: New default WEP key index 2
IEEE 802.1X: New default WEP key - hexdump(len=13): 89
52 67 45 d5 c0 6f d0 9d 74 1e 6f ca
madwifi_set_key: alg=WEP addr=00:00:00:00:00:00
key_idx=2
Flushing old station entries
Deauthenticate all stations
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=2
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
l2_packet_receive - recv: Network is down
br0: port 3(ath0) entering forwarding state
br0: topology change detected, propagating
Wireless event: cmd=0x8c00 len=20
Wireless event: wpaie=0xc37f1dc2
cmd=0x8c03 len=20
ath0: STA 00:02:81:0c:03:98 IEEE 802.11: associated
  New STA
No WPA/RSN information element for station!?
Wireless event: cmd=0x8c00 len=20
Wireless event: cmd=0x8c00 len=20
Wireless event: cmd=0x8c00 len=20
Wireless event: cmd=0x8c00 len=20
Wireless evenath0: STA 00:0f:20:e1:36:22 IEEE 802.11:
deassociated
Wireless event: cmd=0x8c00 len=20
 
Signal 2 received - terminating
Removing station 00:02:81:0c:03:98
Flushing old station entries
Deauthenticate all stations
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff
reason_code=2
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0
t: cmd=0x8c04 len=20
wrap1C-000DB9000A7C:~# iwconfig --version
iwconfig  Wireless-Tools version 27
          Compatible with Wireless Extension v11 to
v17.
 
Kernel    Currently compiled with Wireless Extension
v16.
 
wifi0     Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension
v16.
 
wlan0     Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension
v16.
 
ath0      Recommend Wireless Extension v13 or later,
          Currently compiled with Wireless Extension
v16.
 
wlan0ap   Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension
v16.
 
wrap1C-000DB9000A7C:~# uname -a
Linux wrap1C-000DB9000A7C 2.4.28-sc1100 #3 Fri Nov 26
08:21:01 GMT 2004 i586 unknown


hostapd.ath0.conf
 
# AP info
interface=ath0
driver=madwifi
daemonize=1
ssid=awap_ap_madwifi
                                                      
                              
#Authentication and WEP key methods
macaddr_acl=0
auth_algs=1
ieee8021x=1
eap_message=hello
wep_key_len_broadcast=13
wep_key_len_unicast=13
wep_rekey_period=300
eapol_key_index_workaround=1
own_ip_addr=10.0.0.58
nas_identifier=wrap1C-000DB9000A7C
#Radius Server Config
auth_server_addr=10.0.0.242
auth_server_port=1812
auth_server_shared_secret=********
                                                      
                              
#Debug level
debug=3

The client succeeds in assoicating, and gets to
sending the EAPOL - start. Apart from a few more
EAPOL-start  after retrying. The 802.1x authentication
does not proceed.
Do you have a comment on the failing IOCTL SETMLME
call?
In my original email I mentioned WE18. With iwconfig
--version, all apps recomend WE18, Hence my intial
query on WE18. 

Another problem that I have seen is the setting of the
keys from hostapd. I mentioned it another post I made
but had no response. Hostapd sets a key with idx 2.
The key does get set in madwifi. But the current tx
key in madwifi always remains at 1 (iwlist ath0 key).

Im working on this full time, to get this up and
running.

Kind regards
Steve





From reeopp  Fri Nov 26 03:32:27 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 12:32:27 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c97041126011245c5cbf6@mail.gmail.com>
Message-ID: <BAY13-F170DE687ED8E7CBBAB1361D2BA0@phx.gbl>


Hi YenJung

Sorry but where shall I insert them?

BR/ Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: pepe perez <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 17:12:44 +0800
>
>OK....
>I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules, right?
>
>Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
>all in net80211 directory.
>
>yj.
>
>
>On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com> wrote:
> > Hi YenJung!
> > I think I already tried it, anyway I have just tried again and not so 
>much
> > difference:
> >
> > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > 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 1
> >    id=0 ssid='OSCARLAN'
> > Using existing control interface directory.
> > 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_madwifi_set_wpa: enabled=1
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > Failed to enable WPA in the driver.
> > wpa_driver_madwifi_set_wpa: enabled=0
> > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > Failed to disable WPA in the driver.
> > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > wpa_driver_madwifi_set_countermeasures: enabled=0
> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > Control interface directory not empty - leaving it behind
> >
> > It looks like something else is going on, meybe in configuration or
> > compilation....
> >
> > Thanks a lot for your help!!!
> > Oscar
> >
> > >From: YenJung Chang <yenjung at gmail.com>
> > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > >To: pepe perez <reeopp at hotmail.com>
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > >
> > >AFAIK, the interface name of madwifi is "ath0", hence, the interface
> > >in your command should be -iath0, not -iwlan0.
> > >
> > >yj.
> > >
> > >
> > >
> >
> > _________________________________________________________________
> > Don't just search. Find. Check out the new MSN Search!
> > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >
> >

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From yenjung  Fri Nov 26 04:29:02 2004
From: yenjung (YenJung Chang)
Date: Fri, 26 Nov 2004 20:29:02 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F170DE687ED8E7CBBAB1361D2BA0@phx.gbl>
References: <32653c97041126011245c5cbf6@mail.gmail.com>
	<BAY13-F170DE687ED8E7CBBAB1361D2BA0@phx.gbl>
Message-ID: <32653c97041126042958858531@mail.gmail.com>

If you compiled madwifi as kernel module, the modules with prefixed
"wlan_" were in
directory "madwifi/net80211".  You can command as:

insmod ${madwifi}/net80211/wlan_tkip.o

please replace the ${madwifi} with the actual path of madwifi in your machine.


If you compiled madwifi within kernel image, there is no madwifi
modules needed to insert.

yj.

On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> 
> Hi YenJung
> 
> Sorry but where shall I insert them?
> 
> BR/ Oscar
> 
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: pepe perez <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 17:12:44 +0800
> 
> 
> >
> >OK....
> >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules, right?
> >
> >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
> >all in net80211 directory.
> >
> >yj.
> >
> >
> >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com> wrote:
> > > Hi YenJung!
> > > I think I already tried it, anyway I have just tried again and not so
> >much
> > > difference:
> > >
> > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > 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 1
> > >    id=0 ssid='OSCARLAN'
> > > Using existing control interface directory.
> > > 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_madwifi_set_wpa: enabled=1
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > Failed to enable WPA in the driver.
> > > wpa_driver_madwifi_set_wpa: enabled=0
> > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > Failed to disable WPA in the driver.
> > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > Control interface directory not empty - leaving it behind
> > >
> > > It looks like something else is going on, meybe in configuration or
> > > compilation....
> > >
> > > Thanks a lot for your help!!!
> > > Oscar
> > >
> > > >From: YenJung Chang <yenjung at gmail.com>
> > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > >To: pepe perez <reeopp at hotmail.com>
> > > >CC: hostap at shmoo.com
> > > >Subject: Re: problem with madwifi drivers
> > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > >
> > > >AFAIK, the interface name of madwifi is "ath0", hence, the interface
> > > >in your command should be -iath0, not -iwlan0.
> > > >
> > > >yj.
> > > >
> > > >
> > > >
> > >
> > > _________________________________________________________________
> > > Don't just search. Find. Check out the new MSN Search!
> > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > >
> > >
> 
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
>



From reeopp  Fri Nov 26 04:30:47 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 13:30:47 +0100
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F17F0ED94437973419089B1D2BA0@phx.gbl>
Message-ID: <BAY13-F34E743927A44D82F35B744D2BA0@phx.gbl>

Sorry YenJung

I mean, they already are under

usr/src/madwifi/net80211

is that enough?

Thanks!
Oscar

>From: "Oscar p" <reeopp at hotmail.com>
>To: yenjung at gmail.com
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 12:32:27 +0100
>
>
>Hi YenJung
>
>Sorry but where shall I insert them?
>
>BR/ Oscar
>
>>From: YenJung Chang <yenjung at gmail.com>
>>Reply-To: YenJung Chang <yenjung at gmail.com>
>>To: pepe perez <reeopp at hotmail.com>
>>CC: hostap at shmoo.com
>>Subject: Re: problem with madwifi drivers
>>Date: Fri, 26 Nov 2004 17:12:44 +0800
>>
>>OK....
>>I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules, right?
>>
>>Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
>>all in net80211 directory.
>>
>>yj.
>>
>>
>>On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com> wrote:
>> > Hi YenJung!
>> > I think I already tried it, anyway I have just tried again and not so 
>>much
>> > difference:
>> >
>> > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
>> > 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 1
>> >    id=0 ssid='OSCARLAN'
>> > Using existing control interface directory.
>> > 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_madwifi_set_wpa: enabled=1
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > Failed to enable WPA in the driver.
>> > wpa_driver_madwifi_set_wpa: enabled=0
>> > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > Failed to disable WPA in the driver.
>> > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > wpa_driver_madwifi_set_countermeasures: enabled=0
>> > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
>> > Control interface directory not empty - leaving it behind
>> >
>> > It looks like something else is going on, meybe in configuration or
>> > compilation....
>> >
>> > Thanks a lot for your help!!!
>> > Oscar
>> >
>> > >From: YenJung Chang <yenjung at gmail.com>
>> > >Reply-To: YenJung Chang <yenjung at gmail.com>
>> > >To: pepe perez <reeopp at hotmail.com>
>> > >CC: hostap at shmoo.com
>> > >Subject: Re: problem with madwifi drivers
>> > >Date: Thu, 25 Nov 2004 21:20:22 +0800
>> > >
>> > >AFAIK, the interface name of madwifi is "ath0", hence, the interface
>> > >in your command should be -iath0, not -iwlan0.
>> > >
>> > >yj.
>> > >
>> > >
>> > >
>> >
>> > _________________________________________________________________
>> > Don't just search. Find. Check out the new MSN Search!
>> > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>> >
>> >
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From reeopp  Fri Nov 26 04:33:17 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 13:33:17 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c97041126042958858531@mail.gmail.com>
Message-ID: <BAY13-F40FBD28850365736C8BB24D2BA0@phx.gbl>

Hi YenJung
This is what I get:
dhcppc0:/ # insmod /home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
insmod: error inserting 
'/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 Unknown 
symbol in module

Thanks once more!!!!
Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 20:29:02 +0800
>
>If you compiled madwifi as kernel module, the modules with prefixed
>"wlan_" were in
>directory "madwifi/net80211".  You can command as:
>
>insmod ${madwifi}/net80211/wlan_tkip.o
>
>please replace the ${madwifi} with the actual path of madwifi in your 
>machine.
>
>
>If you compiled madwifi within kernel image, there is no madwifi
>modules needed to insert.
>
>yj.
>
>On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> >
> > Hi YenJung
> >
> > Sorry but where shall I insert them?
> >
> > BR/ Oscar
> >
> > >From: YenJung Chang <yenjung at gmail.com>
> > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > >To: pepe perez <reeopp at hotmail.com>
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> >
> >
> > >
> > >OK....
> > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules, 
>right?
> > >
> > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
> > >all in net80211 directory.
> > >
> > >yj.
> > >
> > >
> > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com> 
>wrote:
> > > > Hi YenJung!
> > > > I think I already tried it, anyway I have just tried again and not 
>so
> > >much
> > > > difference:
> > > >
> > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > > 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 1
> > > >    id=0 ssid='OSCARLAN'
> > > > Using existing control interface directory.
> > > > 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_madwifi_set_wpa: enabled=1
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > Failed to enable WPA in the driver.
> > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > Failed to disable WPA in the driver.
> > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > Control interface directory not empty - leaving it behind
> > > >
> > > > It looks like something else is going on, meybe in configuration or
> > > > compilation....
> > > >
> > > > Thanks a lot for your help!!!
> > > > Oscar
> > > >
> > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > >To: pepe perez <reeopp at hotmail.com>
> > > > >CC: hostap at shmoo.com
> > > > >Subject: Re: problem with madwifi drivers
> > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > >
> > > > >AFAIK, the interface name of madwifi is "ath0", hence, the 
>interface
> > > > >in your command should be -iath0, not -iwlan0.
> > > > >
> > > > >yj.
> > > > >
> > > > >
> > > > >
> > > >
> > > > _________________________________________________________________
> > > > Don't just search. Find. Check out the new MSN Search!
> > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > >
> > > >
> >
> > _________________________________________________________________
> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/




From gbur  Fri Nov 26 04:38:29 2004
From: gbur (Gunter Burchardt)
Date: Fri, 26 Nov 2004 13:38:29 +0100
Subject: hostapd(cvs) & madwifi(cvs)
In-Reply-To: <20041126091647.18459.qmail@web86108.mail.ukl.yahoo.com>
References: <20041126091647.18459.qmail@web86108.mail.ukl.yahoo.com>
Message-ID: <20041126123829.GI28407@informatik.uni-rostock.de>

On 2004-11-26 - 09:16:47, st3v3 at btinternet.com wrote:
> Date: Fri, 26 Nov 2004 09:16:47 +0000 (GMT)
> From: <st3v3 at btinternet.com>
> Subject: Re: hostapd(cvs) & madwifi(cvs)
> To: gbur at informatik.uni-rostock.de
> Cc: hostap at shmoo.com
> 
> Hey Gunter
> Just to continue with this problem.
> I have now tried loading the modules wlan_tkip,
> wlan_ccmp. Im still having the same behaviour.
> I have some provided some additonal info in this
> email.

Is all "wep_..." configuration disabled in hostapd.conf? If not please
disable it. WEP is not WPA! Configuring it at same time will destroy
WPA groupkey.
Your station seams not to be configured to WPA. It sends no WPA IE in
its association request - so hostapd didn't handle this station.


> The client succeeds in assoicating, and gets to
> sending the EAPOL - start. Apart from a few more
> EAPOL-start  after retrying. The 802.1x authentication
> does not proceed.
> Do you have a comment on the failing IOCTL SETMLME
> call?

Not at the moment. I have no reference system here (one day holiday :)
). But i guess i saw failing ioctrl on my system too - without
problems.

> In my original email I mentioned WE18. With iwconfig
> --version, all apps recomend WE18, Hence my intial
> query on WE18. 

Well, WE16 seams to be ok. All functions work!

> Another problem that I have seen is the setting of the
> keys from hostapd. I mentioned it another post I made
> but had no response. Hostapd sets a key with idx 2.
> The key does get set in madwifi. But the current tx
> key in madwifi always remains at 1 (iwlist ath0 key).

Disable WEP!

regards
gunter



From yenjung  Fri Nov 26 04:51:57 2004
From: yenjung (YenJung Chang)
Date: Fri, 26 Nov 2004 20:51:57 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F40FBD28850365736C8BB24D2BA0@phx.gbl>
References: <32653c97041126042958858531@mail.gmail.com>
	<BAY13-F40FBD28850365736C8BB24D2BA0@phx.gbl>
Message-ID: <32653c970411260451ca27a1c@mail.gmail.com>

OK...
This my steps to insert madwifi modules, maybe you can give it a try
and then tell us what you get.

cd ${madwifi}
insmod net80211/wlan.o
insmod net80211/wlan_acl.o
insmod net80211/wlan_wep.o
insmod net80211/wlan_tkip.o
insmod net80211/wlan_ccmp.o
insmod ath_hal/ath_hal.o
insmod ath/ath_pci.o

yj.

On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> Hi YenJung
> This is what I get:
> dhcppc0:/ # insmod /home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> insmod: error inserting
> '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 Unknown
> symbol in module
> 
> Thanks once more!!!!
> Oscar
> 
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: Oscar p <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 20:29:02 +0800
> 
> 
> >
> >If you compiled madwifi as kernel module, the modules with prefixed
> >"wlan_" were in
> >directory "madwifi/net80211".  You can command as:
> >
> >insmod ${madwifi}/net80211/wlan_tkip.o
> >
> >please replace the ${madwifi} with the actual path of madwifi in your
> >machine.
> >
> >
> >If you compiled madwifi within kernel image, there is no madwifi
> >modules needed to insert.
> >
> >yj.
> >
> >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > >
> > > Hi YenJung
> > >
> > > Sorry but where shall I insert them?
> > >
> > > BR/ Oscar
> > >
> > > >From: YenJung Chang <yenjung at gmail.com>
> > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > >To: pepe perez <reeopp at hotmail.com>
> > > >CC: hostap at shmoo.com
> > > >Subject: Re: problem with madwifi drivers
> > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > >
> > >
> > > >
> > > >OK....
> > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules,
> >right?
> > > >
> > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those are
> > > >all in net80211 directory.
> > > >
> > > >yj.
> > > >
> > > >
> > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com>
> >wrote:
> > > > > Hi YenJung!
> > > > > I think I already tried it, anyway I have just tried again and not
> >so
> > > >much
> > > > > difference:
> > > > >
> > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > > > 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 1
> > > > >    id=0 ssid='OSCARLAN'
> > > > > Using existing control interface directory.
> > > > > 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_madwifi_set_wpa: enabled=1
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > Failed to enable WPA in the driver.
> > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > Failed to disable WPA in the driver.
> > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > Control interface directory not empty - leaving it behind
> > > > >
> > > > > It looks like something else is going on, meybe in configuration or
> > > > > compilation....
> > > > >
> > > > > Thanks a lot for your help!!!
> > > > > Oscar
> > > > >
> > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > >CC: hostap at shmoo.com
> > > > > >Subject: Re: problem with madwifi drivers
> > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > >
> > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> >interface
> > > > > >in your command should be -iath0, not -iwlan0.
> > > > > >
> > > > > >yj.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > >
> > > > >
> > >
> > > _________________________________________________________________
> > > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > >
> > >
> 
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search! 
> http://search.msn.com/
> 
>



From st3v3  Fri Nov 26 04:58:44 2004
From: st3v3 (st3v3 at btinternet.com)
Date: Fri, 26 Nov 2004 12:58:44 +0000 (GMT)
Subject: hostapd(cvs) & madwifi(cvs)
Message-ID: <20041126125844.31547.qmail@web86108.mail.ukl.yahoo.com>

Hey Gunter
Ive made some more progress on this issue......

>Your station seams not to be configured to WPA. It sends no WPA IE in its association >request - so hostapd didn't handle this station.

Correct. Im wanting to do 802.1x with dynamic WEP. (i,e without WPA)

In driver_madwifi.c This configuration is not allowed. As the code logic goes 802.1x is invalid without WPA. So Ive temporaily removed most of the WPA version code checks. (via #if 0)

May also need to remove some of the other WPA checks later on in this function. 

This allowed me to then authenticate with WPA disabled.

Do you anticpate any problems with this configuration? If not I will create a patch that allows 802.1x to happen without WPA. (ie. WPA=0, ieee8021x=1 in hostapd.conf)

Regards

Steve

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041126/3a6baa18/attachment.htm 


From reeopp  Fri Nov 26 04:58:11 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 13:58:11 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c970411260451ca27a1c@mail.gmail.com>
Message-ID: <BAY13-F33B6F946B67E426742A617D2BA0@phx.gbl>

Hi YenJung!!

These are tehe results

dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
insmod: error inserting 'net80211/wlan.o': -1 File exists
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_acl.o
insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in module
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_wep.o
insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in module
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_tkip.o
insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in module
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_ccmp.o
insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in module
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
insmod: error inserting 'ath/ath_pci.o': -1 File exists
dhcppc0:/home/oscar/madwifi/madwifi-20041021 #

some of them seem to be already included while some others not (don't know 
why). I can send you the log from madwifi installation if you think it can 
help...

Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 20:51:57 +0800
>
>OK...
>This my steps to insert madwifi modules, maybe you can give it a try
>and then tell us what you get.
>
>cd ${madwifi}
>insmod net80211/wlan.o
>insmod net80211/wlan_acl.o
>insmod net80211/wlan_wep.o
>insmod net80211/wlan_tkip.o
>insmod net80211/wlan_ccmp.o
>insmod ath_hal/ath_hal.o
>insmod ath/ath_pci.o
>
>yj.
>
>On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > Hi YenJung
> > This is what I get:
> > dhcppc0:/ # insmod 
>/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > insmod: error inserting
> > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 Unknown
> > symbol in module
> >
> > Thanks once more!!!!
> > Oscar
> >
> > >From: YenJung Chang <yenjung at gmail.com>
> > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > >To: Oscar p <reeopp at hotmail.com>
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> >
> >
> > >
> > >If you compiled madwifi as kernel module, the modules with prefixed
> > >"wlan_" were in
> > >directory "madwifi/net80211".  You can command as:
> > >
> > >insmod ${madwifi}/net80211/wlan_tkip.o
> > >
> > >please replace the ${madwifi} with the actual path of madwifi in your
> > >machine.
> > >
> > >
> > >If you compiled madwifi within kernel image, there is no madwifi
> > >modules needed to insert.
> > >
> > >yj.
> > >
> > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > >
> > > > Hi YenJung
> > > >
> > > > Sorry but where shall I insert them?
> > > >
> > > > BR/ Oscar
> > > >
> > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > >To: pepe perez <reeopp at hotmail.com>
> > > > >CC: hostap at shmoo.com
> > > > >Subject: Re: problem with madwifi drivers
> > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > >
> > > >
> > > > >
> > > > >OK....
> > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules,
> > >right?
> > > > >
> > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those 
>are
> > > > >all in net80211 directory.
> > > > >
> > > > >yj.
> > > > >
> > > > >
> > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com>
> > >wrote:
> > > > > > Hi YenJung!
> > > > > > I think I already tried it, anyway I have just tried again and 
>not
> > >so
> > > > >much
> > > > > > difference:
> > > > > >
> > > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > > > > 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 1
> > > > > >    id=0 ssid='OSCARLAN'
> > > > > > Using existing control interface directory.
> > > > > > 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_madwifi_set_wpa: enabled=1
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > Failed to enable WPA in the driver.
> > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > Failed to disable WPA in the driver.
> > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > Control interface directory not empty - leaving it behind
> > > > > >
> > > > > > It looks like something else is going on, meybe in configuration 
>or
> > > > > > compilation....
> > > > > >
> > > > > > Thanks a lot for your help!!!
> > > > > > Oscar
> > > > > >
> > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > >CC: hostap at shmoo.com
> > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > >
> > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> > >interface
> > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > >
> > > > > > >yj.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > 
>_________________________________________________________________
> > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > >
> > > > > >
> > > >
> > > > _________________________________________________________________
> > > > Express yourself instantly with MSN Messenger! Download today it's 
>FREE!
> > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > >
> > > >
> >
> > _________________________________________________________________
> > Don't just search. Find. Check out the new MSN Search!
> > http://search.msn.com/
> >
> >

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From yenjung  Fri Nov 26 05:05:20 2004
From: yenjung (YenJung Chang)
Date: Fri, 26 Nov 2004 21:05:20 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F33B6F946B67E426742A617D2BA0@phx.gbl>
References: <32653c970411260451ca27a1c@mail.gmail.com>
	<BAY13-F33B6F946B67E426742A617D2BA0@phx.gbl>
Message-ID: <32653c97041126050516902680@mail.gmail.com>

Oscar,

Please remove wlan.o, ath_hal.o and ath_pci.o first, then re-insert again.
Command as following:

rmmod ath_pci
rmmod ath_hal
rmmod wlan

Please do it as the order.

yj.


On Fri, 26 Nov 2004 13:58:11 +0100, Oscar p <reeopp at hotmail.com> wrote:
> Hi YenJung!!
> 
> These are tehe results
> 
> dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
> dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> insmod: error inserting 'net80211/wlan.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_acl.o
> insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_wep.o
> insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_tkip.o
> insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_ccmp.o
> insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> insmod: error inserting 'ath/ath_pci.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> 
> some of them seem to be already included while some others not (don't know
> why). I can send you the log from madwifi installation if you think it can
> help...
> 
> Oscar
> 
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: Oscar p <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 20:51:57 +0800
> 
> 
> >
> >OK...
> >This my steps to insert madwifi modules, maybe you can give it a try
> >and then tell us what you get.
> >
> >cd ${madwifi}
> >insmod net80211/wlan.o
> >insmod net80211/wlan_acl.o
> >insmod net80211/wlan_wep.o
> >insmod net80211/wlan_tkip.o
> >insmod net80211/wlan_ccmp.o
> >insmod ath_hal/ath_hal.o
> >insmod ath/ath_pci.o
> >
> >yj.
> >
> >On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > Hi YenJung
> > > This is what I get:
> > > dhcppc0:/ # insmod
> >/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > > insmod: error inserting
> > > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 Unknown
> > > symbol in module
> > >
> > > Thanks once more!!!!
> > > Oscar
> > >
> > > >From: YenJung Chang <yenjung at gmail.com>
> > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > >To: Oscar p <reeopp at hotmail.com>
> > > >CC: hostap at shmoo.com
> > > >Subject: Re: problem with madwifi drivers
> > > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> > >
> > >
> > > >
> > > >If you compiled madwifi as kernel module, the modules with prefixed
> > > >"wlan_" were in
> > > >directory "madwifi/net80211".  You can command as:
> > > >
> > > >insmod ${madwifi}/net80211/wlan_tkip.o
> > > >
> > > >please replace the ${madwifi} with the actual path of madwifi in your
> > > >machine.
> > > >
> > > >
> > > >If you compiled madwifi within kernel image, there is no madwifi
> > > >modules needed to insert.
> > > >
> > > >yj.
> > > >
> > > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > > >
> > > > > Hi YenJung
> > > > >
> > > > > Sorry but where shall I insert them?
> > > > >
> > > > > BR/ Oscar
> > > > >
> > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > >CC: hostap at shmoo.com
> > > > > >Subject: Re: problem with madwifi drivers
> > > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > > >
> > > > >
> > > > > >
> > > > > >OK....
> > > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules,
> > > >right?
> > > > > >
> > > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those
> >are
> > > > > >all in net80211 directory.
> > > > > >
> > > > > >yj.
> > > > > >
> > > > > >
> > > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com>
> > > >wrote:
> > > > > > > Hi YenJung!
> > > > > > > I think I already tried it, anyway I have just tried again and
> >not
> > > >so
> > > > > >much
> > > > > > > difference:
> > > > > > >
> > > > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > > > > > 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 1
> > > > > > >    id=0 ssid='OSCARLAN'
> > > > > > > Using existing control interface directory.
> > > > > > > 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_madwifi_set_wpa: enabled=1
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Failed to enable WPA in the driver.
> > > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Failed to disable WPA in the driver.
> > > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Control interface directory not empty - leaving it behind
> > > > > > >
> > > > > > > It looks like something else is going on, meybe in configuration
> >or
> > > > > > > compilation....
> > > > > > >
> > > > > > > Thanks a lot for your help!!!
> > > > > > > Oscar
> > > > > > >
> > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > >CC: hostap at shmoo.com
> > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > > >
> > > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> > > >interface
> > > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > > >
> > > > > > > >yj.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> >_________________________________________________________________
> > > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > > >
> > > > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > Express yourself instantly with MSN Messenger! Download today it's
> >FREE!
> > > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > > >
> > > > >
> > >
> > > _________________________________________________________________
> > > Don't just search. Find. Check out the new MSN Search!
> > > http://search.msn.com/
> > >
> > >
> 
> _________________________________________________________________
> 
> 
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
>



From reeopp  Fri Nov 26 05:15:14 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 14:15:14 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c97041126050516902680@mail.gmail.com>
Message-ID: <BAY13-F1669944D34755FCBB3C07DD2BA0@phx.gbl>

Hi YenJung

I've removed ath_pci, ath_hal, wlan:

dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_pci
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_hal
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod wlan
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_acl.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_wep.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_tkip.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_ccmp.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
insmod: error inserting 'net80211/ath_pci.o': -1 Unknown symbol in module
dhcppc0:/home/oscar/madwifi/madwifi-20041021 #

but it keeps on not working (I cannot paste anythng else since I lost 
connection) trying to recover...

Oscar



>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 21:05:20 +0800
>
>Oscar,
>
>Please remove wlan.o, ath_hal.o and ath_pci.o first, then re-insert again.
>Command as following:
>
>rmmod ath_pci
>rmmod ath_hal
>rmmod wlan
>
>Please do it as the order.
>
>yj.
>
>
>On Fri, 26 Nov 2004 13:58:11 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > Hi YenJung!!
> >
> > These are tehe results
> >
> > dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> > insmod: error inserting 'net80211/wlan.o': -1 File exists
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_acl.o
> > insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in 
>module
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_wep.o
> > insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in 
>module
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_tkip.o
> > insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in 
>module
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_ccmp.o
> > insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in 
>module
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> > insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> > insmod: error inserting 'ath/ath_pci.o': -1 File exists
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> >
> > some of them seem to be already included while some others not (don't 
>know
> > why). I can send you the log from madwifi installation if you think it 
>can
> > help...
> >
> > Oscar
> >
> > >From: YenJung Chang <yenjung at gmail.com>
> > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > >To: Oscar p <reeopp at hotmail.com>
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Fri, 26 Nov 2004 20:51:57 +0800
> >
> >
> > >
> > >OK...
> > >This my steps to insert madwifi modules, maybe you can give it a try
> > >and then tell us what you get.
> > >
> > >cd ${madwifi}
> > >insmod net80211/wlan.o
> > >insmod net80211/wlan_acl.o
> > >insmod net80211/wlan_wep.o
> > >insmod net80211/wlan_tkip.o
> > >insmod net80211/wlan_ccmp.o
> > >insmod ath_hal/ath_hal.o
> > >insmod ath/ath_pci.o
> > >
> > >yj.
> > >
> > >On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > > Hi YenJung
> > > > This is what I get:
> > > > dhcppc0:/ # insmod
> > >/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > > > insmod: error inserting
> > > > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 
>Unknown
> > > > symbol in module
> > > >
> > > > Thanks once more!!!!
> > > > Oscar
> > > >
> > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > >To: Oscar p <reeopp at hotmail.com>
> > > > >CC: hostap at shmoo.com
> > > > >Subject: Re: problem with madwifi drivers
> > > > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> > > >
> > > >
> > > > >
> > > > >If you compiled madwifi as kernel module, the modules with prefixed
> > > > >"wlan_" were in
> > > > >directory "madwifi/net80211".  You can command as:
> > > > >
> > > > >insmod ${madwifi}/net80211/wlan_tkip.o
> > > > >
> > > > >please replace the ${madwifi} with the actual path of madwifi in 
>your
> > > > >machine.
> > > > >
> > > > >
> > > > >If you compiled madwifi within kernel image, there is no madwifi
> > > > >modules needed to insert.
> > > > >
> > > > >yj.
> > > > >
> > > > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> 
>wrote:
> > > > > >
> > > > > > Hi YenJung
> > > > > >
> > > > > > Sorry but where shall I insert them?
> > > > > >
> > > > > > BR/ Oscar
> > > > > >
> > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > >CC: hostap at shmoo.com
> > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >OK....
> > > > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o 
>modules,
> > > > >right?
> > > > > > >
> > > > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, 
>those
> > >are
> > > > > > >all in net80211 directory.
> > > > > > >
> > > > > > >yj.
> > > > > > >
> > > > > > >
> > > > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez 
><reeopp at hotmail.com>
> > > > >wrote:
> > > > > > > > Hi YenJung!
> > > > > > > > I think I already tried it, anyway I have just tried again 
>and
> > >not
> > > > >so
> > > > > > >much
> > > > > > > > difference:
> > > > > > > >
> > > > > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf 
>-d
> > > > > > > > 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 1
> > > > > > > >    id=0 ssid='OSCARLAN'
> > > > > > > > Using existing control interface directory.
> > > > > > > > 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_madwifi_set_wpa: enabled=1
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > Failed to enable WPA in the driver.
> > > > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > Failed to disable WPA in the driver.
> > > > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > Control interface directory not empty - leaving it behind
> > > > > > > >
> > > > > > > > It looks like something else is going on, meybe in 
>configuration
> > >or
> > > > > > > > compilation....
> > > > > > > >
> > > > > > > > Thanks a lot for your help!!!
> > > > > > > > Oscar
> > > > > > > >
> > > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > > >CC: hostap at shmoo.com
> > > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > > > >
> > > > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> > > > >interface
> > > > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > > > >
> > > > > > > > >yj.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > >_________________________________________________________________
> > > > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > > 
>_________________________________________________________________
> > > > > > Express yourself instantly with MSN Messenger! Download today 
>it's
> > >FREE!
> > > > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > > > >
> > > > > >
> > > >
> > > > _________________________________________________________________
> > > > Don't just search. Find. Check out the new MSN Search!
> > > > http://search.msn.com/
> > > >
> > > >
> >
> > _________________________________________________________________
> >
> >
> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From yenjung  Fri Nov 26 05:30:13 2004
From: yenjung (YenJung Chang)
Date: Fri, 26 Nov 2004 21:30:13 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F1669944D34755FCBB3C07DD2BA0@phx.gbl>
References: <32653c97041126050516902680@mail.gmail.com>
	<BAY13-F1669944D34755FCBB3C07DD2BA0@phx.gbl>
Message-ID: <32653c970411260530514773bf@mail.gmail.com>

Oscar,

Maybe you should recompile madwifi and try it again.
I can not make sense of why ath_pci.o failed to insert.

In addition, please remove inserted modules before you insert again.

yj.


On Fri, 26 Nov 2004 14:15:14 +0100, Oscar p <reeopp at hotmail.com> wrote:
> Hi YenJung
> 
> I've removed ath_pci, ath_hal, wlan:
> 
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_pci
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_hal
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod wlan
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_acl.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_wep.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_tkip.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_ccmp.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> insmod: error inserting 'net80211/ath_pci.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> 
> but it keeps on not working (I cannot paste anythng else since I lost
> connection) trying to recover...
> 
> Oscar
> 
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: Oscar p <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 21:05:20 +0800
> 
> 
> >
> >Oscar,
> >
> >Please remove wlan.o, ath_hal.o and ath_pci.o first, then re-insert again.
> >Command as following:
> >
> >rmmod ath_pci
> >rmmod ath_hal
> >rmmod wlan
> >
> >Please do it as the order.
> >
> >yj.
> >
> >
> >On Fri, 26 Nov 2004 13:58:11 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > Hi YenJung!!
> > >
> > > These are tehe results
> > >
> > > dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> > > insmod: error inserting 'net80211/wlan.o': -1 File exists
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> >net80211/wlan_acl.o
> > > insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in
> >module
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> >net80211/wlan_wep.o
> > > insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in
> >module
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> >net80211/wlan_tkip.o
> > > insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in
> >module
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> >net80211/wlan_ccmp.o
> > > insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in
> >module
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> > > insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> > > insmod: error inserting 'ath/ath_pci.o': -1 File exists
> > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> > >
> > > some of them seem to be already included while some others not (don't
> >know
> > > why). I can send you the log from madwifi installation if you think it
> >can
> > > help...
> > >
> > > Oscar
> > >
> > > >From: YenJung Chang <yenjung at gmail.com>
> > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > >To: Oscar p <reeopp at hotmail.com>
> > > >CC: hostap at shmoo.com
> > > >Subject: Re: problem with madwifi drivers
> > > >Date: Fri, 26 Nov 2004 20:51:57 +0800
> > >
> > >
> > > >
> > > >OK...
> > > >This my steps to insert madwifi modules, maybe you can give it a try
> > > >and then tell us what you get.
> > > >
> > > >cd ${madwifi}
> > > >insmod net80211/wlan.o
> > > >insmod net80211/wlan_acl.o
> > > >insmod net80211/wlan_wep.o
> > > >insmod net80211/wlan_tkip.o
> > > >insmod net80211/wlan_ccmp.o
> > > >insmod ath_hal/ath_hal.o
> > > >insmod ath/ath_pci.o
> > > >
> > > >yj.
> > > >
> > > >On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > > > Hi YenJung
> > > > > This is what I get:
> > > > > dhcppc0:/ # insmod
> > > >/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > > > > insmod: error inserting
> > > > > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1
> >Unknown
> > > > > symbol in module
> > > > >
> > > > > Thanks once more!!!!
> > > > > Oscar
> > > > >
> > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > >To: Oscar p <reeopp at hotmail.com>
> > > > > >CC: hostap at shmoo.com
> > > > > >Subject: Re: problem with madwifi drivers
> > > > > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> > > > >
> > > > >
> > > > > >
> > > > > >If you compiled madwifi as kernel module, the modules with prefixed
> > > > > >"wlan_" were in
> > > > > >directory "madwifi/net80211".  You can command as:
> > > > > >
> > > > > >insmod ${madwifi}/net80211/wlan_tkip.o
> > > > > >
> > > > > >please replace the ${madwifi} with the actual path of madwifi in
> >your
> > > > > >machine.
> > > > > >
> > > > > >
> > > > > >If you compiled madwifi within kernel image, there is no madwifi
> > > > > >modules needed to insert.
> > > > > >
> > > > > >yj.
> > > > > >
> > > > > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com>
> >wrote:
> > > > > > >
> > > > > > > Hi YenJung
> > > > > > >
> > > > > > > Sorry but where shall I insert them?
> > > > > > >
> > > > > > > BR/ Oscar
> > > > > > >
> > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > >CC: hostap at shmoo.com
> > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >OK....
> > > > > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o
> >modules,
> > > > > >right?
> > > > > > > >
> > > > > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o,
> >those
> > > >are
> > > > > > > >all in net80211 directory.
> > > > > > > >
> > > > > > > >yj.
> > > > > > > >
> > > > > > > >
> > > > > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez
> ><reeopp at hotmail.com>
> > > > > >wrote:
> > > > > > > > > Hi YenJung!
> > > > > > > > > I think I already tried it, anyway I have just tried again
> >and
> > > >not
> > > > > >so
> > > > > > > >much
> > > > > > > > > difference:
> > > > > > > > >
> > > > > > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf
> >-d
> > > > > > > > > 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 1
> > > > > > > > >    id=0 ssid='OSCARLAN'
> > > > > > > > > Using existing control interface directory.
> > > > > > > > > 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_madwifi_set_wpa: enabled=1
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > Failed to enable WPA in the driver.
> > > > > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > Failed to disable WPA in the driver.
> > > > > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > Control interface directory not empty - leaving it behind
> > > > > > > > >
> > > > > > > > > It looks like something else is going on, meybe in
> >configuration
> > > >or
> > > > > > > > > compilation....
> > > > > > > > >
> > > > > > > > > Thanks a lot for your help!!!
> > > > > > > > > Oscar
> > > > > > > > >
> > > > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > > > >CC: hostap at shmoo.com
> > > > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > > > > >
> > > > > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> > > > > >interface
> > > > > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > > > > >
> > > > > > > > > >yj.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > >_________________________________________________________________
> > > > > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> >_________________________________________________________________
> > > > > > > Express yourself instantly with MSN Messenger! Download today
> >it's
> > > >FREE!
> > > > > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > > > > >
> > > > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > http://search.msn.com/
> > > > >
> > > > >
> > >
> > > _________________________________________________________________
> > >
> > >
> > > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > >
> > >
> 
> _________________________________________________________________
> 
> 
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
>



From reeopp  Fri Nov 26 05:36:03 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 14:36:03 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c970411260530514773bf@mail.gmail.com>
Message-ID: <BAY13-F26DAD941084601088DD037D2BA0@phx.gbl>

Hi YenJung!!

May you explain how a litle bit since I already tried and I had no 
success??? Just some hints and important steps not to forget...

Thanks a lot once more!!!
Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 21:30:13 +0800
>
>Oscar,
>
>Maybe you should recompile madwifi and try it again.
>I can not make sense of why ath_pci.o failed to insert.
>
>In addition, please remove inserted modules before you insert again.
>
>yj.
>
>
>On Fri, 26 Nov 2004 14:15:14 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > Hi YenJung
> >
> > I've removed ath_pci, ath_hal, wlan:
> >
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_pci
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod ath_hal
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # rmmod wlan
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_acl.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_wep.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_tkip.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan_ccmp.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> > insmod: error inserting 'net80211/ath_pci.o': -1 Unknown symbol in 
>module
> > dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> >
> > but it keeps on not working (I cannot paste anythng else since I lost
> > connection) trying to recover...
> >
> > Oscar
> >
> > >From: YenJung Chang <yenjung at gmail.com>
> > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > >To: Oscar p <reeopp at hotmail.com>
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Fri, 26 Nov 2004 21:05:20 +0800
> >
> >
> > >
> > >Oscar,
> > >
> > >Please remove wlan.o, ath_hal.o and ath_pci.o first, then re-insert 
>again.
> > >Command as following:
> > >
> > >rmmod ath_pci
> > >rmmod ath_hal
> > >rmmod wlan
> > >
> > >Please do it as the order.
> > >
> > >yj.
> > >
> > >
> > >On Fri, 26 Nov 2004 13:58:11 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > > Hi YenJung!!
> > > >
> > > > These are tehe results
> > > >
> > > > dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>net80211/wlan.o
> > > > insmod: error inserting 'net80211/wlan.o': -1 File exists
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> > >net80211/wlan_acl.o
> > > > insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in
> > >module
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> > >net80211/wlan_wep.o
> > > > insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in
> > >module
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> > >net80211/wlan_tkip.o
> > > > insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in
> > >module
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod
> > >net80211/wlan_ccmp.o
> > > > insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in
> > >module
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod 
>ath_hal/ath_hal.o
> > > > insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> > > > insmod: error inserting 'ath/ath_pci.o': -1 File exists
> > > > dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
> > > >
> > > > some of them seem to be already included while some others not 
>(don't
> > >know
> > > > why). I can send you the log from madwifi installation if you think 
>it
> > >can
> > > > help...
> > > >
> > > > Oscar
> > > >
> > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > >To: Oscar p <reeopp at hotmail.com>
> > > > >CC: hostap at shmoo.com
> > > > >Subject: Re: problem with madwifi drivers
> > > > >Date: Fri, 26 Nov 2004 20:51:57 +0800
> > > >
> > > >
> > > > >
> > > > >OK...
> > > > >This my steps to insert madwifi modules, maybe you can give it a 
>try
> > > > >and then tell us what you get.
> > > > >
> > > > >cd ${madwifi}
> > > > >insmod net80211/wlan.o
> > > > >insmod net80211/wlan_acl.o
> > > > >insmod net80211/wlan_wep.o
> > > > >insmod net80211/wlan_tkip.o
> > > > >insmod net80211/wlan_ccmp.o
> > > > >insmod ath_hal/ath_hal.o
> > > > >insmod ath/ath_pci.o
> > > > >
> > > > >yj.
> > > > >
> > > > >On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> 
>wrote:
> > > > > > Hi YenJung
> > > > > > This is what I get:
> > > > > > dhcppc0:/ # insmod
> > > > >/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > > > > > insmod: error inserting
> > > > > > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1
> > >Unknown
> > > > > > symbol in module
> > > > > >
> > > > > > Thanks once more!!!!
> > > > > > Oscar
> > > > > >
> > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > >To: Oscar p <reeopp at hotmail.com>
> > > > > > >CC: hostap at shmoo.com
> > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >If you compiled madwifi as kernel module, the modules with 
>prefixed
> > > > > > >"wlan_" were in
> > > > > > >directory "madwifi/net80211".  You can command as:
> > > > > > >
> > > > > > >insmod ${madwifi}/net80211/wlan_tkip.o
> > > > > > >
> > > > > > >please replace the ${madwifi} with the actual path of madwifi 
>in
> > >your
> > > > > > >machine.
> > > > > > >
> > > > > > >
> > > > > > >If you compiled madwifi within kernel image, there is no 
>madwifi
> > > > > > >modules needed to insert.
> > > > > > >
> > > > > > >yj.
> > > > > > >
> > > > > > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p 
><reeopp at hotmail.com>
> > >wrote:
> > > > > > > >
> > > > > > > > Hi YenJung
> > > > > > > >
> > > > > > > > Sorry but where shall I insert them?
> > > > > > > >
> > > > > > > > BR/ Oscar
> > > > > > > >
> > > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > > >CC: hostap at shmoo.com
> > > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >OK....
> > > > > > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o
> > >modules,
> > > > > > >right?
> > > > > > > > >
> > > > > > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o,
> > >those
> > > > >are
> > > > > > > > >all in net80211 directory.
> > > > > > > > >
> > > > > > > > >yj.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez
> > ><reeopp at hotmail.com>
> > > > > > >wrote:
> > > > > > > > > > Hi YenJung!
> > > > > > > > > > I think I already tried it, anyway I have just tried 
>again
> > >and
> > > > >not
> > > > > > >so
> > > > > > > > >much
> > > > > > > > > > difference:
> > > > > > > > > >
> > > > > > > > > > dhcppc0:~ # wpa_supplicant -iath0 
>-c/etc/wpa_supplicant.conf
> > >-d
> > > > > > > > > > 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 1
> > > > > > > > > >    id=0 ssid='OSCARLAN'
> > > > > > > > > > Using existing control interface directory.
> > > > > > > > > > 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_madwifi_set_wpa: enabled=1
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > Failed to enable WPA in the driver.
> > > > > > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > Failed to disable WPA in the driver.
> > > > > > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > > > > Control interface directory not empty - leaving it 
>behind
> > > > > > > > > >
> > > > > > > > > > It looks like something else is going on, meybe in
> > >configuration
> > > > >or
> > > > > > > > > > compilation....
> > > > > > > > > >
> > > > > > > > > > Thanks a lot for your help!!!
> > > > > > > > > > Oscar
> > > > > > > > > >
> > > > > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > > > > >CC: hostap at shmoo.com
> > > > > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > > > > > >
> > > > > > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, 
>the
> > > > > > >interface
> > > > > > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > > > > > >
> > > > > > > > > > >yj.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > >_________________________________________________________________
> > > > > > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > > > > > 
>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > >_________________________________________________________________
> > > > > > > > Express yourself instantly with MSN Messenger! Download 
>today
> > >it's
> > > > >FREE!
> > > > > > > > 
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > > 
>_________________________________________________________________
> > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > http://search.msn.com/
> > > > > >
> > > > > >
> > > >
> > > > _________________________________________________________________
> > > >
> > > >
> > > > Express yourself instantly with MSN Messenger! Download today it's 
>FREE!
> > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > >
> > > >
> >
> > _________________________________________________________________
> >
> >
> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From reeopp  Fri Nov 26 07:04:36 2004
From: reeopp (Oscar p)
Date: Fri, 26 Nov 2004 16:04:36 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c970411260530514773bf@mail.gmail.com>
Message-ID: <BAY13-F744FA90782C8B7A502A9BD2BA0@phx.gbl>

Hi

This is what I did:

1.- remove all driver files from /lib/modules/2.6.4-52-default/net
2.- reboot the machine without wireless card
3.- compile the madwifi again
4.- copy wlan.o, ath_hal.o, ath_pci.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, 
wlan_ccmp.o, into  /lib/modules/2.6.4-52-default/net
5.- try insmod on wlan.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, wlan_ccmp.o, 
ath_hal.o, ath_pci.o, all of them were properly loaded but ath_pci:

Compaq:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
insmod: error inserting 'ath/ath_pci.o': -1 Unknown symbol in module

dmesg messages:


Nov 26 15:50:33 Compaq kernel: wlan: no version for "struct_module" found: 
kernel tainted.
Nov 26 15:50:33 Compaq kernel: wlan: no version magic, tainting kernel.
Nov 26 15:50:33 Compaq kernel: wlan: 0.8.4.4 (EXPERIMENTAL)
Nov 26 15:50:51 Compaq kernel: wlan_acl: no version magic, tainting kernel.
Nov 26 15:50:51 Compaq kernel: wlan: mac acl policy registered
Nov 26 15:51:05 Compaq kernel: wlan_wep: no version magic, tainting kernel.
Nov 26 15:51:17 Compaq kernel: wlan_tkip: no version magic, tainting kernel.
Nov 26 15:51:30 Compaq kernel: wlan_ccmp: no version magic, tainting kernel.
Nov 26 15:51:38 Compaq kernel: ath_hal: no version magic, tainting kernel.
Nov 26 15:51:38 Compaq kernel: ath_hal: module license 'Proprietary' taints 
kernel.
Nov 26 15:51:38 Compaq kernel: ath_hal: 0.9.12.14 (AR5210, AR5211, AR5212)
Nov 26 15:51:52 Compaq kernel: ath_pci: no version magic, tainting kernel.
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_tx_complete
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_attach
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newassoc
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_copy
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_cleanup
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_detach
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_init
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_findrate
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newstate
Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_setupxtxdesc

6.- I inserted the pmcia with the following messages:


Nov 26 15:52:11 Compaq /etc/hotplug/pci.agent[5742]: FATAL: Error inserting 
ath_pci (/lib/modules/2.6.4-52-default/extra/ath_pci.ko): Unknown symbol in 
module, or unknown parameter (see dmesg)
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_encap
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_encap
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_input
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_input
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_ifattach
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifattach
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
_ath_hal_attach
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol _ath_hal_attach
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_ifdetach
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifdetach
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ath_hal_computetxtime
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_computetxtime
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_dump_pkt
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_dump_pkt
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ath_hal_detach
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_detach
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_media_change
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
ieee80211_media_change
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_xrates
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_iterate_nodes
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
ieee80211_iterate_nodes
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_find_node
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_find_node
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_next_scan
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_next_scan
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_media_init
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_media_init
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_new_state
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_get_rssi
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_media_status
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
ieee80211_media_status
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_rates
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_chan2ieee
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2ieee
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ath_hal_init_channels
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_init_channels
Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
ieee80211_chan2mode
Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2mod

it seems there is something wrong with ath_pci but I do not know what it 
is....

Thanks a lot for your help!
Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 21:30:13 +0800
>
>Oscar,
>
>Maybe you should recompile madwifi and try it again.
>I can not make sense of why ath_pci.o failed to insert.
>
>In addition, please remove inserted modules before you insert again.
>
>yj.
>
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From jkmaline  Fri Nov 26 07:58:01 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 26 Nov 2004 07:58:01 -0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F744FA90782C8B7A502A9BD2BA0@phx.gbl>
References: <32653c970411260530514773bf@mail.gmail.com>
	<BAY13-F744FA90782C8B7A502A9BD2BA0@phx.gbl>
Message-ID: <20041126155801.GA7013@jm.kir.nu>

On Fri, Nov 26, 2004 at 04:04:36PM +0100, Oscar p wrote:

> 1.- remove all driver files from /lib/modules/2.6.4-52-default/net

Please also remove madwifi modules from other subdirectories under
/lib/modules/2.6.4-52-default if you have installed another version
before. The syslog excerpt showed something being loaded from
/lib/modules/2.6.4-52-default/extra with mismatch in version..

> 5.- try insmod on wlan.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, wlan_ccmp.o, 
> ath_hal.o, ath_pci.o, all of them were properly loaded but ath_pci:

Nowadays, you will also need to load rate control algorithm as a kernel
module (ath_rate/onoe/ath_rate_onoe.ko).


PS.

madwifi driver has its own mailing lists.. This does not really have
anything to do with Host AP drivers or hostapd/wpa_supplicant..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 27 08:35:12 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 27 Nov 2004 08:35:12 -0800
Subject: Module version mismatch
In-Reply-To: <1101094726.4171.8.camel@localhost.localdomain>
References: <1101094726.4171.8.camel@localhost.localdomain>
Message-ID: <20041127163512.GA7441@jm.kir.nu>

On Sun, Nov 21, 2004 at 10:38:46PM -0500, Sean Faircloth wrote:

> [root at localhost hostap-driver-0.2.5]# modprobe hostap_pci
> FATAL: Error inserting hostap_pci
> (/lib/modules/2.6.9/kernel/drivers/net/wireless/hostap_pci.ko): Unknown
> symbol in module, or unknown parameter (see dmesg)

> hostap_pci: Unknown symbol hostap_info_process
> hostap_pci: disagrees about version of symbol hostap_set_antsel

This symbols are from hostap.ko module. It looks like you have a
mismatch in kernel modules, i.e., hostap.ko is from a different
version/build than hostap_pci.ko. Make sure you don't have more than one
hostap.ko in /lib/modules/<kernel ver> subdirectory. In addition, make
sure that you have not loaded hostap.ko module from different version
before loading hostap_pci.ko.

-- 
Jouni Malinen                                            PGP id EFC895FA



From reeopp  Sat Nov 27 12:25:16 2004
From: reeopp (Oscar p)
Date: Sat, 27 Nov 2004 21:25:16 +0100
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F7678E7783A39E41983C97D2BA0@phx.gbl>
Message-ID: <BAY13-F126A51F0A826022FB1C37ED2BB0@phx.gbl>

Hi all
It looks like finally solved, I have installed Mandrake instead of SuSE and 
compiled madwifi again. Fortunately there is a wpa_supplicant rpm for 
mandrake which I instlled. Now everything seems to work, do not aske me 
exactly why....

I'm facing a different problem now, everything seems to work but I'm not 
getting any IP, look:
[root at Compaq network-scripts]# wpa_supplicant -Bd -iath0 
-c/etc/wpa_supplicant.conf -Dmadwifi
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 5
   id=0 ssid='OSCARLAN'
Using existing control interface directory.
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_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
Daemonize..
[root at Compaq network-scripts]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

ath0      IEEE 802.11g  ESSID:"OSCARLAN"  Nickname:"Compaq"
          Mode:Managed  Frequency:2.437GHz  Access Point: 00:80:5A:22:AA:54
          Bit Rate=54Mb/s   Tx-Power:50 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:20EE-672E-ABA4-1854-6EB3-C34F-5480-ACDA   Security 
mode:restricted
          Power Management:off
          Link Quality:23/94  Signal level:-72 dBm  Noise level:-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

but :

[root at Compaq network-scripts]# ifconfig
ath0      Link encap:Ethernet  HWaddr 00:80:5A:22:11:78
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32 errors:6 dropped:0 overruns:0 frame:6
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:4025 (3.9 Kb)  TX bytes:2216 (2.1 Kb)
          Interrupt:11 Memory:d1ad5000-d1ae5000

I've updated ifcfg-ath0 and wireless:

    if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
        /usr/local/bin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf \
                -Dmadwifi -i$DEVICE
    fi
and wireless.opt:

    MODE="Managed"
    WPA="y"
    ;;

For some reason when the system is started wireless doesn't work and I have 
to restart wpa_supplicant and the network itself....

I don't know if I should ask or help in a new thread or is it ok here, so in 
case I should let me know!!!

Thanks a lot
Oscar

>From: "Oscar p" <reeopp at hotmail.com>
>To: yenjung at gmail.com
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Fri, 26 Nov 2004 16:04:36 +0100
>
>Hi
>
>This is what I did:
>
>1.- remove all driver files from /lib/modules/2.6.4-52-default/net
>2.- reboot the machine without wireless card
>3.- compile the madwifi again
>4.- copy wlan.o, ath_hal.o, ath_pci.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, 
>wlan_ccmp.o, into  /lib/modules/2.6.4-52-default/net
>5.- try insmod on wlan.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, wlan_ccmp.o, 
>ath_hal.o, ath_pci.o, all of them were properly loaded but ath_pci:
>
>Compaq:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
>insmod: error inserting 'ath/ath_pci.o': -1 Unknown symbol in module
>
>dmesg messages:
>
>
>Nov 26 15:50:33 Compaq kernel: wlan: no version for "struct_module" found: 
>kernel tainted.
>Nov 26 15:50:33 Compaq kernel: wlan: no version magic, tainting kernel.
>Nov 26 15:50:33 Compaq kernel: wlan: 0.8.4.4 (EXPERIMENTAL)
>Nov 26 15:50:51 Compaq kernel: wlan_acl: no version magic, tainting kernel.
>Nov 26 15:50:51 Compaq kernel: wlan: mac acl policy registered
>Nov 26 15:51:05 Compaq kernel: wlan_wep: no version magic, tainting kernel.
>Nov 26 15:51:17 Compaq kernel: wlan_tkip: no version magic, tainting 
>kernel.
>Nov 26 15:51:30 Compaq kernel: wlan_ccmp: no version magic, tainting 
>kernel.
>Nov 26 15:51:38 Compaq kernel: ath_hal: no version magic, tainting kernel.
>Nov 26 15:51:38 Compaq kernel: ath_hal: module license 'Proprietary' taints 
>kernel.
>Nov 26 15:51:38 Compaq kernel: ath_hal: 0.9.12.14 (AR5210, AR5211, AR5212)
>Nov 26 15:51:52 Compaq kernel: ath_pci: no version magic, tainting kernel.
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_tx_complete
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_attach
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newassoc
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_copy
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_node_cleanup
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_detach
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_init
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_findrate
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newstate
>Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_setupxtxdesc
>
>6.- I inserted the pmcia with the following messages:
>
>
>Nov 26 15:52:11 Compaq /etc/hotplug/pci.agent[5742]: FATAL: Error inserting 
>ath_pci (/lib/modules/2.6.4-52-default/extra/ath_pci.ko): Unknown symbol in 
>module, or unknown parameter (see dmesg)
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_encap
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_encap
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_input
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_input
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_ifattach
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifattach
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>_ath_hal_attach
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol _ath_hal_attach
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_ifdetach
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifdetach
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ath_hal_computetxtime
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ath_hal_computetxtime
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_dump_pkt
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_dump_pkt
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ath_hal_detach
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_detach
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_media_change
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_media_change
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_xrates
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_iterate_nodes
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_iterate_nodes
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_find_node
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_find_node
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_next_scan
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_next_scan
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_media_init
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_media_init
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_new_state
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_get_rssi
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_media_status
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_media_status
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_rates
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_chan2ieee
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2ieee
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ath_hal_init_channels
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ath_hal_init_channels
>Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol 
>ieee80211_chan2mode
>Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2mod
>
>it seems there is something wrong with ath_pci but I do not know what it 
>is....
>
>Thanks a lot for your help!
>Oscar
>
>>From: YenJung Chang <yenjung at gmail.com>
>>Reply-To: YenJung Chang <yenjung at gmail.com>
>>To: Oscar p <reeopp at hotmail.com>
>>CC: hostap at shmoo.com
>>Subject: Re: problem with madwifi drivers
>>Date: Fri, 26 Nov 2004 21:30:13 +0800
>>
>>Oscar,
>>
>>Maybe you should recompile madwifi and try it again.
>>I can not make sense of why ath_pci.o failed to insert.
>>
>>In addition, please remove inserted modules before you insert again.
>>
>>yj.
>>
>>
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From jkmaline  Sat Nov 27 17:24:58 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 27 Nov 2004 17:24:58 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041126131928.GB15224@lukas.schuldei.com>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
	<20041123204028.GD1457@lukas.schuldei.com>
	<20041124050821.GB7030@jm.kir.nu> <41A50EB7.5020005@cisco.com>
	<20041125150056.GB7013@jm.kir.nu>
	<20041126131928.GB15224@lukas.schuldei.com>
Message-ID: <20041128012458.GB6904@jm.kir.nu>

On Fri, Nov 26, 2004 at 02:19:28PM +0100, Andreas Schuldei wrote:

> ok, here are some logs with debugging in the madwifi driver
> activated (by echo 1 > /proc/sys/dev/ath0/debug)

Thanks. This is starting to point towards being something to do with the
driver and not wpa_supplicant, so I cc'ed madwifi-devel mailing list
which is probably a more suitable forum for this question.


Summary:

WPA key handshake completes successfully, ar521x generates beacon miss
interrupt after about 90 seconds, scans fail for some reason during
following couple of minutes.

In other words, it is the client driver that decides that the connection
is down. It is unclear to me why this is happening, though. One
explanation would be that the AP and client get out of sync with
beacons, but that should not really happen since the client is supposed
to do time sync based on the beacon frames in the first place..
Alternatively, the AP could have indeed stopped sending beacons which
should be obvious if you can run a wireless sniffer to capture what
packets are being sent.

If the AP is still up, but the client just misses couple of beacons, I
would prefer the driver to try a bit harder before reporting this as a
lost connection. I haven't looked into madwifi code to see how many
beacons need to be missed. Anyway, I would at least try to probe the AP
first (e.g., send ProbeReq for its BSSID) and only report disconnection
if no reply is received.


Details:

Here's the driver debug for association:

Nov 26 13:47:07 localhost kernel: NODS
00:05:4e:4a:47:44->00:0f:66:45:e2:ad(00:0f:66:45:e2:ad) auth 1M
Nov 26 13:47:07 localhost kernel:  b000 3a01 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 0000 0000 0100 0000
Nov 26 13:47:07 localhost kernel: NODS
00:05:4e:4a:47:44->00:0f:66:45:e2:ad(00:0f:66:45:e2:ad) assoc_req 1M
Nov 26 13:47:07 localhost kernel:  0000 3a01 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 1000 3104 6400 000c 4163 6365 7373 5f50 6f69 6e74
0108 8284 8b0c 1296 1824 3204 3048 606c dd16 0050 f201 0100 0050 f202
0100 0050 f204 0100 0050 f202
Nov 26 13:47:07 localhost kernel: ath_tx_start:
link[3](edf9c86c)=2df9c898 (edf9c898)

This triggered association event to wpa_supplicant:

Wireless event: cmd=0x8b1a len=25
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:66:45:e2:ad
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0f:66:45:e2:ad

Followed by RX of msg 1/4

WPA: RX message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)

and reply msg 2/4:

WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 0f 66 45 e2 ad 00 05 4e 4a
47 44 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 00 00 00 00 00 12 7c 68
7c d0 e6 d0 c2 be e0 15 eb 30 f2 72 d6 7d f4 f9 42 aa 05 6d 23 82 66 cd
fa a0 9b 16 4b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 17 9a 49 c1 f5 59 be 16 6f c9 a3
d5 b8 53 2e 9c 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2
04 01 00 00 50 f2 02

in the driver:

Nov 26 13:47:07 localhost kernel: TODS
00:05:4e:4a:47:44->00:0f:66:45:e2:ad(00:0f:66:45:e2:ad) data 36M
Nov 26 13:47:07 localhost kernel:  0801 2c00 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 2000 aaaa 0300 0000 888e 0103 0077 fe01 0a00 1000
0000 0000 0000 0012 7c68 7cd0 e6d0 c2be e015 eb30 f272 d67d f4f9 42aa
056d 2382 66cd faa0 9b16 4b00 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0017 9a49 c1f5 59be 166f c9a3 d5b8
532e 9c00 18dd 1600 50f2 0101 0000 50f2 0201 0000 50f2 0401 0000 50f2 02

followed by msg 3/4

WPA: RX message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2)

and reply, msg 4/4

WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 0f 66 45 e2 ad 00 05 4e 4a
47 44 88 8e 01 03 00 5f fe 01 0a 00 10 00 00 00 00 00 00 00 01 12 7c 68
7c d0 e6 d0 c2 be e0 15 eb 30 f2 72 d6 7d f4 f9 42 aa 05 6d 23 82 66 cd
fa a0 9b 16 4b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 e6 35 f0 27 f8 b2 9a c5 0b 17 a6
cb df af d0 e8 00 00

Nov 26 13:47:07 localhost kernel: ath_tx_start: Q1: 00000000 37f8d830
013c009f 0000009b 22240000 000db92d
Nov 26 13:47:07 localhost kernel: TODS
00:05:4e:4a:47:44->00:0f:66:45:e2:ad(00:0f:66:45:e2:ad) data 36M
Nov 26 13:47:07 localhost kernel:  0801 2c00 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 3000 aaaa 0300 0000 888e 0103 005f fe01 0a00 1000
0000 0000 0000 0112 7c68 7cd0 e6d0 c2be e015 eb30 f272 d67d f4f9 42aa
056d 2382 66cd faa0 9b16 4b00 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 00e6 35f0 27f8 b29a c50b 17a6 cbdf
afd0 e800 00

keys configured

RX msg 1/2 (encrypted)

Reply:

WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key 2/2 - hexdump(len=113): 00 0f 66 45 e2 ad 00 05 4e 4a
47 44 88 8e 01 03 00 5f fe 03 12 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 b5 87 22 4c 6b 01 a7 bf 71 5b 9e
e8 51 48 1e 43 00 00

Nov 26 13:47:07 localhost kernel:  0841 2c00 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 4000 0100 0020 0000 0000 aaaa 0300 0000 888e 0103
005f fe03 1200 2000 0000 0000 0000 0200 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00b5 8722 4c6b
01a7 bf71 5b9e e851 481e 4300 00
Nov 26 13:47:07 localhost kernel: ath_tx_start: Q1: 00000000 019e6e28
413c0097 0000008b 22240000 000db92d
Nov 26 13:47:07 localhost kernel: ath_tx_start:
link[1](edf9c8f0)=2df9c91c (edf9c91c)


At this point, connection is up and everything is done as far as
wpa_supplicant is concerned:

WPA: Key negotiation completed with 00:0f:66:45:e2:ad
Cancelling authentication timeout

Next things happening is driver reporting that the hardware reported
beacon miss:

Nov 26 13:48:41 localhost kernel: ath_bmiss_tasklet
Nov 26 13:48:41 localhost kernel: NODS
00:05:4e:4a:47:44->00:0f:66:45:e2:ad(00:0f:66:45:e2:ad) assoc_req 1M
Nov 26 13:48:41 localhost kernel:  0000 3a01 000f 6645 e2ad 0005 4e4a
4744 000f 6645 e2ad 5000 1104 6400 000c 4163 6365 7373 5f50 6f69 6e74
0108 0204 0b0c 1216 1824 3204 3048 606c dd16 0050 f201 0100 0050 f202
0100 0050 f204 0100 0050 f202

I don't know what that assoc_req is; maybe the driver tries to associate
back with the AP in case of beacon miss

This beacon miss is reported to wpa_supplicant as disconnect event:

Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Disconnect event - remove keys

This triggers wpa_supplicant to start scanning. madwifi debug shows lots
of probe_req being sent, but all the scan results are empty (0 BSSes).
It seems to take minutes before getting real scan results. After this,
the same process seems to be repeated; this time with 128 seconds of
connection uptime before getting ath_bmiss_tasklet.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 27 20:55:36 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 27 Nov 2004 20:55:36 -0800
Subject: Problem setting keys with ndiswrapper after authentication?
In-Reply-To: <20041126091621.GA14791@pern.dea.icai.upco.es>
References: <20041126091621.GA14791@pern.dea.icai.upco.es>
Message-ID: <20041128045536.GC6904@jm.kir.nu>

ndiswrapper-general cc'ed; please, apply the attached patch to
ndiswrapper CVS.


On Fri, Nov 26, 2004 at 10:16:21AM +0100, Romano Giannetti wrote:

> Well. I have ndiswrapper installed (last version, 0.12rc3), with a realtek
> ndis5 driver version 173. 

> First of all, I set essid manually (no way to obtain this in scan mode, so I
> disabled it) and "up" the interface 

OK, although support for scanning for specific SSID with ndiswrapper
when using wpa_supplicant should be added at some point.. Unfortunately,
this seems to be somewhat complex task with NDIS and multiple possible
authentication modes.

> [root at rukbat wifi]# iwconfig wlan0 mode managed essid upco_wlan key 0 open
> [root at rukbat wifi]# iwconfig wlan0 && ifconfig wlan0
> wlan0     IEEE 802.11b  ESSID:"upco_wlan"  
>           Mode:Managed  Frequency:2.427GHz  Access Point: 00:11:5C:77:82:40  

OK, so association works when done manually. I tested this with
wpa_supplicant doing scanning and it actually failed. ndiswrapper ended
up configuring the driver to reject APs that were using encryption.. I
fixed wpa_supplicant to set cipher suite to WEP-104 when using IEEE
802.1X (available in the current Host AP CVS snapshot) and this seemed
to have fixed the association part.

> EAPOL: Decrypted(RC4) key - hexdump(len=13): 13 ab d7 39 ef 08 e0 bc 63 a7 d1 a8 b9
> EAPOL: Setting dynamic WEP key: broadcast keyidx 0 len 13
> key data: key_idx=0 set_tx=0
> trying to set key...
> result of iw_set_ext, RESULT -1
> 
> ***** HERE is the fault!!!

Indeed. There's a bug in the way the current ndiswrapper handles WEP
keys from wpa_supplicant. wpa_set_key() tries to convert the WPA key set
structure into normal wireless extensions WEP configuration, but does it
incorrectly. The key is already in binary form, so no hex2bin conversion
is needed. In addition, key index needs +1 to match the wireless
extensions.

The attached patch to the current ndiswrapper CVS version fixes these
problems. With this patch and the current CVS version of wpa_supplicant,
I was able to complete IEEE 802.1X (non-WPA) authentication and use the
encrypted data connection (both unicast and multicast worked).

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Index: driver/iw_ndis.c
===================================================================
RCS file: /cvsroot/ndiswrapper/ndiswrapper/driver/iw_ndis.c,v
retrieving revision 1.83
diff -u -p -r1.83 iw_ndis.c
--- driver/iw_ndis.c	22 Nov 2004 06:02:50 -0000	1.83
+++ driver/iw_ndis.c	28 Nov 2004 04:34:03 -0000
@@ -1276,48 +1276,6 @@ static int wpa_set_wpa(struct net_device
 	}
 }
 
-static int char_to_hex(int c)
-{
-	if (c >= '0' && c <= '9')
-		return c - '0';
-	if (c >= 'a' && c <= 'f')
-		return c - 'a' + 10;
-	return -1;
-}
-
-/* convert key in string to hex digits - 2 chars make up one digit */
-static int key_str_to_hex(const char *str, unsigned char *key, int str_len)
-{
-	int i, key_len;
-
-	if (!memcmp(str, "s:", 2))
-	{
-		key_len = str_len-2;
-		if (key_len >= IW_ENCODING_TOKEN_MAX)
-			TRACEEXIT(return -1);
-		memcpy(key, str+2, key_len);
-	}
-	else
-		for (i = key_len = 0; i < str_len-1; i += 2, key_len++)
-		{
-			int c1, c2;
-
-			if (key_len >= IW_ENCODING_TOKEN_MAX)
-				TRACEEXIT(return -1);
-			/* sscanf(str, "%1X", &ch) doesn't seem to work */
-			c1 = char_to_hex(tolower(str[i]));
-			c2 = char_to_hex(tolower(str[i+1]));
-			if (c1 < 0 || c2 < 0)
-				TRACEEXIT(return -1);
-			key[key_len] = c1 << 4 | c2;
-		}
-	DBGTRACE("key length = %d", key_len);
-	if (key_len == 5 || key_len == 13)
-		TRACEEXIT(return key_len);
-	else
-		TRACEEXIT(return -1);
-}
-
 static int remove_key(struct ndis_handle *handle, int key_index,
 		      mac_address bssid)
 {
@@ -1392,25 +1350,20 @@ static int wpa_set_key(struct net_device
 	if (wpa_key.alg == WPA_ALG_WEP)
 	{
 		union iwreq_data encr_req;
-		unsigned char key[IW_ENCODING_TOKEN_MAX];
-		int i;
 
 		if (test_bit(CAPA_ENCR_NONE, &handle->capa))
 			TRACEEXIT(return -EINVAL);
 
 		memset(&encr_req, 0, sizeof(encr_req));
-		encr_req.data.flags = wpa_key.key_index;
+		encr_req.encoding.flags = wpa_key.key_index + 1;
 		/* auth mode is set with set_auth_alg */
 		if (handle->auth_mode == AUTHMODE_OPEN)
-			encr_req.data.flags |= IW_ENCODE_OPEN;
+			encr_req.encoding.flags |= IW_ENCODE_OPEN;
 		else
-			encr_req.data.flags |= IW_ENCODE_RESTRICTED;
-		i = key_str_to_hex(usrkey, key, wpa_key.key_len);
-		if (i < 0)
-			TRACEEXIT(return -EINVAL);
-		encr_req.data.length = i;
-		encr_req.data.pointer = key;
-		if (iw_set_encr(dev, info, &encr_req, key))
+			encr_req.encoding.flags |= IW_ENCODE_RESTRICTED;
+		encr_req.encoding.length = wpa_key.key_len;
+		encr_req.encoding.pointer = wpa_key.key;
+		if (iw_set_encr(dev, info, &encr_req, usrkey))
 			TRACEEXIT(return -EINVAL);
 		else
 			TRACEEXIT(return 0);


From jkmaline  Sat Nov 27 23:27:26 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 27 Nov 2004 23:27:26 -0800
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041124225249.GA13048@lukas.schuldei.com>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041122020811.GE7013@jm.kir.nu>
	<20041123204028.GD1457@lukas.schuldei.com>
	<20041124050821.GB7030@jm.kir.nu>
	<20041124225249.GA13048@lukas.schuldei.com>
Message-ID: <20041128072726.GD6904@jm.kir.nu>

On Wed, Nov 24, 2004 at 11:52:49PM +0100, Andreas Schuldei wrote:

> if it is a timing problem (as suggested in the mail in this
> thread) how can i procude debug output with timing information?

The current development snapshot of wpa_supplicant has a new command
line argument, -t, for enabling timestamping of debug messages.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Nov 27 23:40:30 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 27 Nov 2004 23:40:30 -0800
Subject: wpa_supplicant fails with ndiswrapper andmadwifi driver for
	Atheros 802.11a/b/g card
In-Reply-To: <41A16405.40703@cisco.com>
References: <4185D9EF.7010602@cisco.com> <20041104033042.GE7380@jm.kir.nu>
	<419277BA.6020703@cisco.com> <20041121050404.GB6980@jm.kir.nu>
	<41A16405.40703@cisco.com>
Message-ID: <20041128074030.GE6904@jm.kir.nu>

On Sun, Nov 21, 2004 at 07:59:01PM -0800, Michael Reilly wrote:

> I just tried 0.12rc3 with my two Atheros cards against a Cisco 1100 AP 
> using WPA-PSK.  It failed with both cards.  It may be related to the timing 
> related problems you are seeing.  I have been busy at work so haven't had a 
> chance to play with this a lot

Could you please re-test ndiswrapper with the current development branch
snapshot of wpa_supplicant?

I did some more testing with number of different client cards, drivers,
and APs. There are indeed quite many cases where the group key handshake
fails because of the client not receiving the encrypted EAPOL-Key frame.

I was able to improve reliablity of the key handshakes greatly by
removing some of the key clearing operations. In practice, this removed
the five key delete operations that were done immediately after link up
(association) event.

I don't know why removing keys would cause issues in receiving encrypted
unicast frames _after_ new PTK is configured just some time after this.
Anyway, most of the key clearing operations are not really needed, so
getting rid of them should at least speed up association a bit, if
nothing else. I would like to remove the unicast key for the new AP to
make sure that no old key is configured during the initial 4-Way
Handshake. However, even that one operation seemed to make group key
handshake unreliable.

-- 
Jouni Malinen                                            PGP id EFC895FA



From saschasommer  Sun Nov 28 03:22:17 2004
From: saschasommer (Sascha Sommer)
Date: Sun, 28 Nov 2004 12:22:17 +0100
Subject: [PATCH] WPA Supplicant hidden ssid support
Message-ID: <200411281222.17467.saschasommer@freenet.de>

Hi,
just tryed out ndiswrapper + wpa supplicant with an linksys wrt54g and an 
acx111 wlan card. Unfortunatelly wpa supplicant had problems with the 
authentication due to the hidden ssid.
I attached a trivial patch against 0.2.5 to fix this. I'm not sure if it will 
work with all configuration, but I think you will get the idea.

Sascha Sommer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hidden_ssid.patch
Type: text/x-diff
Size: 1029 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041128/00ecb592/attachment.patch 


From mbuchhol  Sun Nov 28 04:26:00 2004
From: mbuchhol (mbuchhol at eu.uu.net)
Date: Sun, 28 Nov 2004 13:26:00 +0100 (CET)
Subject: IPW2100 and "Failed to set PTK to the driver"
Message-ID: <XFMail.20041128132600.mbuchhol@eu.uu.net>

Hi,

I have the Debian (Sarge) Kernel 2.6.6 with the IPW-Driver 1.0.1 and
wpa_supplicant-0.2.5

I use this configfile:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
        ssid="UUnet"
        key_mgmt=WPA-EAP
        proto=WPA
        pairwise=TKIP
        group=TKIP
        eap=PEAP
        identity="logname"
        password="password"
        phase1="peapver=0"
        phase2="auth=MSCHAPV2"
        priority=2
}

This is the last message, before it starts over again:

WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 07 eb 30 ed 3c 00 04 23 91
15 7c 88 8e 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 28 68 31
36 b8 c6 5e d0 7 4 1e 7f 32 7d 8e 3b ac b8 ec 54 f1 fe 0f 38 b4 5b 26 85
9d 81 9f 19 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 e8 20 17 89 21 1e 70 f5 4e 46 31
ec 26 db 2c 67 00 00 WPA: Installing PTK to the driver.
WPAioctl[IPW2100_IOCTL_WPA_SUPPLICANT]: Invalid argument
: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_ipw2100_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6
key_len=32 Failed to set encryption.
WPA: Failed to set PTK to the driver.

I also found and activated encryption in the IPW-Driver's Makefile:

# If you do not want any encryption/decryptoin code in the driver,
# comment out this line:
CONFIG_IEEE80211_CRYPT=$(CONFIG_IEEE80211)



What have i forgotten to enable, define or install?
I have absolutely no clue and my manager wants to use my Notebook for a
presentation (that it works with Linux too) for a customer next
Thursday.
I already scanned the Mailing-List Archive, but could not find anything,
that matches.
Any help is welcome.

Thank you

-- 
mit freundlichen Gruessen / with friendly regards
Michael Buchholz              MCI Group       Office: +49 231 9721192
                          Sebrathweg 20  Home-Office: +49 231 9479858
MSAS Support       44149 Dortmund, Germany    Fax...: +49 231 9722508 





From jsun  Sun Nov 28 11:32:07 2004
From: jsun (Jun Sun)
Date: Sun, 28 Nov 2004 11:32:07 -0800
Subject: Host AP on Fedora Core 3
In-Reply-To: <4196770B.1020206@drdoom.net>
References: <4193F860.9060006@drdoom.net> <4196770B.1020206@drdoom.net>
Message-ID: <20041128193207.GA28996@gateway.junsun.net>

On Sat, Nov 13, 2004 at 09:05:15PM +0000, DrDoom wrote:
> I just did it, no problems encountered.
> 
> DrDoom wrote:
> 
> >Did someone install hostap on FC3 ?
> >
>

I am trying to do the same but having problems.

Did you install hostap as add-on modules or as kernel patch?

I am compiling hostap as add-on modules.  The problem appears to be that
the modules are compiled as .o files instead of .ko files.  depmod -ae
won't discover the .o hostap files. 

I did encounter a couple of other issues.  I summarize them as follows
and hopefully other people can benefit:

1. fc3 does not have kernel source rpm.

. up2date --get-source kernel
. (as root) rpm -ivh /var/spool/up2date/kernel-2.6.9-1.667.src.rpm
. rpmbuild -v -v --target=i686 -bp /usr/src/redhat/SPEC/kernel-2.6.spec
. cd /usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9/
. [if you are using SMP kernel]
	cp configs/<smp>.config .config
. make oldconfig
. make vmlinux

The last step is stupid.  But without it, some files such as include/linux/
version.h are not created.

2. hostap picks up kernel version from the source tree instead of
   current running kernel.  I had to patch the Makefile for hostap:

diff -Nru Makefile.orig Makefile
--- Makefile.orig       2004-11-28 10:44:41.438069327 -0800
+++ Makefile    2004-11-28 11:04:44.250296615 -0800
@@ -1,6 +1,8 @@
 # Edit this path to match with your system (it should point to the root
 # directory of the Linux kernel source)
-KERNEL_PATH=/usr/src/linux
+#KERNEL_PATH=/usr/src/linux
+#KERNEL_PATH=/home/jsun/build/kernel/linux-2.4.20-8
+KERNEL_PATH=/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9/
 
 # Systems using external pcmcia-cs package (instead of kernel-tree pcmcia
 # modules):
@@ -53,6 +55,7 @@
 KERNELRELEASE := $(shell if [ -r $(VERFILE) ]; \
        then (cat $(VERFILE); echo UTS_RELEASE) | $(CC) $(INCLUDES) $(CFLAGS) -E - | tail -1 | xargs echo; \
        else uname -r; fi)
+KERNELRELEASE := $(shell uname -r)
 KERNELVER := $(shell echo "$(KERNELRELEASE)" | \
        sed "s/\([0-9]*\.[0-9]*\.[0-9]*\).*/\1/")
 MODPATH := $(DESTDIR)/lib/modules/$(KERNELRELEASE)

Jun



From jar  Sun Nov 28 11:51:17 2004
From: jar (jar)
Date: Sun, 28 Nov 2004 21:51:17 +0200
Subject: Host AP on Fedora Core 3
In-Reply-To: <20041128193207.GA28996@gateway.junsun.net>
References: <4193F860.9060006@drdoom.net> <4196770B.1020206@drdoom.net>
	<20041128193207.GA28996@gateway.junsun.net>
Message-ID: <41AA2C35.1030400@pcuf.fi>

Jun Sun wrote:
> I am compiling hostap as add-on modules.  The problem appears to be that
> the modules are compiled as .o files instead of .ko files.  depmod -ae
> won't discover the .o hostap files. 
> 
> I did encounter a couple of other issues.  I summarize them as follows
> and hopefully other people can benefit:

You don't need kernel source any more to compile modules. Just compile 
modules against /lib/modules/kernel-2.6.9/build directory.

1. cd hostap_source_dir
2. make KERNEL_PATH=/lib/modules/kernel-2.6.9/build

RB. Jar



From jsun  Sun Nov 28 14:17:00 2004
From: jsun (Jun Sun)
Date: Sun, 28 Nov 2004 14:17:00 -0800
Subject: Host AP on Fedora Core 3
In-Reply-To: <41AA2C35.1030400@pcuf.fi>
References: <4193F860.9060006@drdoom.net> <4196770B.1020206@drdoom.net>
	<20041128193207.GA28996@gateway.junsun.net>
	<41AA2C35.1030400@pcuf.fi>
Message-ID: <20041128221700.GA29092@gateway.junsun.net>

On Sun, Nov 28, 2004 at 09:51:17PM +0200, jar wrote:
> Jun Sun wrote:
> >I am compiling hostap as add-on modules.  The problem appears to be that
> >the modules are compiled as .o files instead of .ko files.  depmod -ae
> >won't discover the .o hostap files. 
> >
> >I did encounter a couple of other issues.  I summarize them as follows
> >and hopefully other people can benefit:
> 
> You don't need kernel source any more to compile modules. Just compile 
> modules against /lib/modules/kernel-2.6.9/build directory.
> 
> 1. cd hostap_source_dir
> 2. make KERNEL_PATH=/lib/modules/kernel-2.6.9/build
>

Ahh, I see.  Thanks.

It turns out my .o problem was caused by "make pci_install".  After
I did "make install", everything now is fine.

Jun



From brix  Sun Nov 28 15:12:44 2004
From: brix (Henrik Brix Andersen)
Date: Mon, 29 Nov 2004 00:12:44 +0100
Subject: IPW2100 and "Failed to set PTK to the driver"
In-Reply-To: <XFMail.20041128132600.mbuchhol@eu.uu.net>
References: <XFMail.20041128132600.mbuchhol@eu.uu.net>
Message-ID: <1101683564.5019.1.camel@sponge.fungus>

Hi,

On Sun, 2004-11-28 at 13:26 +0100, mbuchhol at eu.uu.net wrote:
> WPA: Failed to set PTK to the driver.

Does your kernel have michael_mic support?

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/20041129/ec9e8d35/attachment.pgp 


From ramalhais  Sun Nov 28 18:25:29 2004
From: ramalhais (Pedro Ramalhais)
Date: Mon, 29 Nov 2004 02:25:29 +0000
Subject: IPW2100 and "Failed to set PTK to the driver"
In-Reply-To: <XFMail.20041128132600.mbuchhol@eu.uu.net>
References: <XFMail.20041128132600.mbuchhol@eu.uu.net>
Message-ID: <1101682978.21428.1.camel@rootix>

On Sun, 2004-11-28 at 12:26, mbuchhol at eu.uu.net wrote:
> Hi,
> 
> I have the Debian (Sarge) Kernel 2.6.6 with the IPW-Driver 1.0.1 and
> wpa_supplicant-0.2.5
> 
> I use this configfile:
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> network={
>         ssid="UUnet"
>         key_mgmt=WPA-EAP
>         proto=WPA
>         pairwise=TKIP
>         group=TKIP
>         eap=PEAP
>         identity="logname"
>         password="password"
>         phase1="peapver=0"
>         phase2="auth=MSCHAPV2"
>         priority=2
> }
> 
> This is the last message, before it starts over again:
> 
> WPA: Sending EAPOL-Key 4/4
> WPA: TX EAPOL-Key 4/4 - hexdump(len=113): 00 07 eb 30 ed 3c 00 04 23 91
> 15 7c 88 8e 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 28 68 31
> 36 b8 c6 5e d0 7 4 1e 7f 32 7d 8e 3b ac b8 ec 54 f1 fe 0f 38 b4 5b 26 85
> 9d 81 9f 19 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 e8 20 17 89 21 1e 70 f5 4e 46 31
> ec 26 db 2c 67 00 00 WPA: Installing PTK to the driver.
> WPAioctl[IPW2100_IOCTL_WPA_SUPPLICANT]: Invalid argument
> : RSC - hexdump(len=6): 00 00 00 00 00 00
> wpa_driver_ipw2100_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6
> key_len=32 Failed to set encryption.
> WPA: Failed to set PTK to the driver.
> 
> I also found and activated encryption in the IPW-Driver's Makefile:
> 
> # If you do not want any encryption/decryptoin code in the driver,
> # comment out this line:
> CONFIG_IEEE80211_CRYPT=$(CONFIG_IEEE80211)
> 
> 
> 
> What have i forgotten to enable, define or install?
> I have absolutely no clue and my manager wants to use my Notebook for a
> presentation (that it works with Linux too) for a customer next
> Thursday.
> I already scanned the Mailing-List Archive, but could not find anything,
> that matches.
> Any help is welcome.
> 
> Thank you

You probably forgot to enable WPA in the Makefile.
If not, check that the module that is being loaded is the 1.0.1 with WPA
compiled in, and not a module loaded in your initrd.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From yenjung  Sun Nov 28 18:41:14 2004
From: yenjung (YenJung Chang)
Date: Mon, 29 Nov 2004 10:41:14 +0800
Subject: problem with madwifi drivers
In-Reply-To: <BAY13-F126A51F0A826022FB1C37ED2BB0@phx.gbl>
References: <BAY13-F7678E7783A39E41983C97D2BA0@phx.gbl>
	<BAY13-F126A51F0A826022FB1C37ED2BB0@phx.gbl>
Message-ID: <32653c9704112818418d3b563@mail.gmail.com>

Sorry for reply so late. I took two days vacation. :)

If you did not setup ath0 as dhcp client, it would not get IP automatically.
You can setup its ip manually after it connected to a AP.
Moreover, I don't how Mandrake configures and set network interface at
system starting, I have no suggestion for this.

yj.

On Sat, 27 Nov 2004 21:25:16 +0100, Oscar p <reeopp at hotmail.com> wrote:
> Hi all
> It looks like finally solved, I have installed Mandrake instead of SuSE and
> compiled madwifi again. Fortunately there is a wpa_supplicant rpm for
> mandrake which I instlled. Now everything seems to work, do not aske me
> exactly why....
> 
> I'm facing a different problem now, everything seems to work but I'm not
> getting any IP, look:
> [root at Compaq network-scripts]# wpa_supplicant -Bd -iath0
> -c/etc/wpa_supplicant.conf -Dmadwifi
> 
> 
> 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 5
>    id=0 ssid='OSCARLAN'
> Using existing control interface directory.
> 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_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
> Daemonize..
> [root at Compaq network-scripts]# iwconfig
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> ath0      IEEE 802.11g  ESSID:"OSCARLAN"  Nickname:"Compaq"
>           Mode:Managed  Frequency:2.437GHz  Access Point: 00:80:5A:22:AA:54
>           Bit Rate=54Mb/s   Tx-Power:50 dBm   Sensitivity=0/3
>           Retry:off   RTS thr:off   Fragment thr:off
>           Encryption key:20EE-672E-ABA4-1854-6EB3-C34F-5480-ACDA   Security
> mode:restricted
>           Power Management:off
>           Link Quality:23/94  Signal level:-72 dBm  Noise level:-95 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> but :
> 
> [root at Compaq network-scripts]# ifconfig
> ath0      Link encap:Ethernet  HWaddr 00:80:5A:22:11:78
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:32 errors:6 dropped:0 overruns:0 frame:6
>           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:199
>           RX bytes:4025 (3.9 Kb)  TX bytes:2216 (2.1 Kb)
>           Interrupt:11 Memory:d1ad5000-d1ae5000
> 
> I've updated ifcfg-ath0 and wireless:
> 
>     if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
>         /usr/local/bin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf \
>                 -Dmadwifi -i$DEVICE
>     fi
> and wireless.opt:
> 
>     MODE="Managed"
>     WPA="y"
>     ;;
> 
> For some reason when the system is started wireless doesn't work and I have
> to restart wpa_supplicant and the network itself....
> 
> I don't know if I should ask or help in a new thread or is it ok here, so in
> case I should let me know!!!
> 
> Thanks a lot
> Oscar
> 
> >From: "Oscar p" <reeopp at hotmail.com>
> >To: yenjung at gmail.com
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 16:04:36 +0100
> >
> >Hi
> >
> >This is what I did:
> >
> >1.- remove all driver files from /lib/modules/2.6.4-52-default/net
> >2.- reboot the machine without wireless card
> >3.- compile the madwifi again
> >4.- copy wlan.o, ath_hal.o, ath_pci.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o,
> >wlan_ccmp.o, into  /lib/modules/2.6.4-52-default/net
> 
> 
> >5.- try insmod on wlan.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, wlan_ccmp.o,
> >ath_hal.o, ath_pci.o, all of them were properly loaded but ath_pci:
> >
> >Compaq:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> >insmod: error inserting 'ath/ath_pci.o': -1 Unknown symbol in module
> >
> >dmesg messages:
> >
> >
> >Nov 26 15:50:33 Compaq kernel: wlan: no version for "struct_module" found:
> >kernel tainted.
> >Nov 26 15:50:33 Compaq kernel: wlan: no version magic, tainting kernel.
> >Nov 26 15:50:33 Compaq kernel: wlan: 0.8.4.4 (EXPERIMENTAL)
> >Nov 26 15:50:51 Compaq kernel: wlan_acl: no version magic, tainting kernel.
> >Nov 26 15:50:51 Compaq kernel: wlan: mac acl policy registered
> >Nov 26 15:51:05 Compaq kernel: wlan_wep: no version magic, tainting kernel.
> >Nov 26 15:51:17 Compaq kernel: wlan_tkip: no version magic, tainting
> >kernel.
> >Nov 26 15:51:30 Compaq kernel: wlan_ccmp: no version magic, tainting
> >kernel.
> >Nov 26 15:51:38 Compaq kernel: ath_hal: no version magic, tainting kernel.
> >Nov 26 15:51:38 Compaq kernel: ath_hal: module license 'Proprietary' taints
> >kernel.
> >Nov 26 15:51:38 Compaq kernel: ath_hal: 0.9.12.14 (AR5210, AR5211, AR5212)
> >Nov 26 15:51:52 Compaq kernel: ath_pci: no version magic, tainting kernel.
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_tx_complete
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_attach
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newassoc
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_copy
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol
> >ath_rate_node_cleanup
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_detach
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_node_init
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_findrate
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_newstate
> >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol
> >ath_rate_setupxtxdesc
> >
> >6.- I inserted the pmcia with the following messages:
> >
> >
> >Nov 26 15:52:11 Compaq /etc/hotplug/pci.agent[5742]: FATAL: Error inserting
> >ath_pci (/lib/modules/2.6.4-52-default/extra/ath_pci.ko): Unknown symbol in
> >module, or unknown parameter (see dmesg)
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_encap
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_encap
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_input
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_input
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_ifattach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifattach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >_ath_hal_attach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol _ath_hal_attach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_ifdetach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_ifdetach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ath_hal_computetxtime
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> >ath_hal_computetxtime
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_dump_pkt
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_dump_pkt
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ath_hal_detach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_detach
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_media_change
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> >ieee80211_media_change
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_xrates
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_iterate_nodes
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> >ieee80211_iterate_nodes
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_find_node
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_find_node
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_next_scan
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_next_scan
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_media_init
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_media_init
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_new_state
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_get_rssi
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_media_status
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> >ieee80211_media_status
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_add_rates
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_chan2ieee
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2ieee
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ath_hal_init_channels
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> >ath_hal_init_channels
> >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of symbol
> >ieee80211_chan2mode
> >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_chan2mod
> >
> >it seems there is something wrong with ath_pci but I do not know what it
> >is....
> >
> >Thanks a lot for your help!
> >Oscar
> >
> >>From: YenJung Chang <yenjung at gmail.com>
> >>Reply-To: YenJung Chang <yenjung at gmail.com>
> >>To: Oscar p <reeopp at hotmail.com>
> >>CC: hostap at shmoo.com
> >>Subject: Re: problem with madwifi drivers
> >>Date: Fri, 26 Nov 2004 21:30:13 +0800
> >>
> >>Oscar,
> >>
> >>Maybe you should recompile madwifi and try it again.
> >>I can not make sense of why ath_pci.o failed to insert.
> >>
> >>In addition, please remove inserted modules before you insert again.
> >>
> >>yj.
> >>
> >>
> >
> 
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
>



From jkmaline  Sun Nov 28 19:51:15 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 28 Nov 2004 19:51:15 -0800
Subject: wpa_supplicant: new driver interface API
Message-ID: <20041129035115.GB7025@jm.kir.nu>

The current development branch in CVS has a new version of the
wpa_supplicant driver API. This is the major cleanup I had planned for
the new development branch to fix some design flaws in the original API.
As a consequence of the changes, the new API is not anymore backwards
compatible and all driver interface implementations (driver_*.c) will
need to be modified for the wpa_supplicant v0.3.x branch. The current
stable branch, v0.2.x, has not (and most likely, will not) change this
API, so the old driver interface code can be used with that branch.

I would appreciate any comments on the driver interface design. Now
would be the best time to do any further changes before v0.3.x branch
starts to get closer to being the next stable branch. Source code
compatibile (i.e., driver_*.c from an older version compiles with the
changed API) changes are ok in the future, but at some point relatively
soon I will stop accepting changes that break the compatibility within
0.3.x branch.

I converted all driver_*.c files that are in the wpa_supplicant CVS
repository to use the new interface. I know that there are number of
external implementations which has not been included in the
wpa_supplicant releases for a reason or another. I can convert them too,
if they are first released under suitable open source license to be
included in the wpa_supplicant releases.. ;-) There may be some more
changes lined up for 0.3.x development branch, so getting the external
code to my CVS will save some maintenance time in the future.

So far, I have only verified that all driver_*.c files compile and
tested that driver_hostapd.c works. I will verify that driver_madwifi.c
and driver_ndiswrapper.c works, too, but for all the other driver_*.c
implementations, I would appreciate it if someone with the hardware
would test the current development snapshot and would report whether
there are any issues that should be fixed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mail  Mon Nov 29 04:21:50 2004
From: mail (Michael Riviera)
Date: Mon, 29 Nov 2004 12:21:50 +0000
Subject: madwifi(cvs), wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <20041128012458.GB6904@jm.kir.nu>
References: <20041122003048.GA11581@timotheus.schuldei.org>	<20041122020811.GE7013@jm.kir.nu>	<20041123204028.GD1457@lukas.schuldei.com>	<20041124050821.GB7030@jm.kir.nu>
	<41A50EB7.5020005@cisco.com>	<20041125150056.GB7013@jm.kir.nu>	<20041126131928.GB15224@lukas.schuldei.com>
	<20041128012458.GB6904@jm.kir.nu>
Message-ID: <41AB145E.6020604@michaelriviera.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041129/96fc3413/attachment.htm 


From romanol  Mon Nov 29 03:23:43 2004
From: romanol (Romano Giannetti)
Date: Mon, 29 Nov 2004 12:23:43 +0100
Subject: Problem setting keys with ndiswrapper after authentication?
In-Reply-To: <20041128045536.GC6904@jm.kir.nu>
References: <20041126091621.GA14791@pern.dea.icai.upco.es>
	<20041128045536.GC6904@jm.kir.nu>
Message-ID: <20041129112343.GB18542@pern.dea.icai.upco.es>

Warning: crossposted to hostap and ndiswrapper mailing list. 

On Sat, Nov 27, 2004 at 08:55:36PM -0800, Jouni Malinen wrote:
> ndiswrapper-general cc'ed; please, apply the attached patch to
> ndiswrapper CVS.

Thank you for the answer. I had no time to try it (my laptop is at home
now), but I will report back as soon as possible. 

Just one question: I downloaded ndiswrapper 0.12 and --- although via a
completely different patch --- the iwndis.c file is quite changed. Should I
use this version? Is the bug fixed in a different way? 

> 
> > [root at rukbat wifi]# iwconfig wlan0 mode managed essid upco_wlan key 0 open
> > [root at rukbat wifi]# iwconfig wlan0 && ifconfig wlan0
> > wlan0     IEEE 802.11b  ESSID:"upco_wlan"  
> >           Mode:Managed  Frequency:2.427GHz  Access Point: 00:11:5C:77:82:40  
> 
> OK, so association works when done manually. I tested this with
> wpa_supplicant doing scanning and it actually failed. ndiswrapper ended
> up configuring the driver to reject APs that were using encryption.. I
> fixed wpa_supplicant to set cipher suite to WEP-104 when using IEEE
> 802.1X (available in the current Host AP CVS snapshot) and this seemed
> to have fixed the association part.

Do you mean the CVS snapshot "stable" or "development"? 

> The attached patch to the current ndiswrapper CVS version fixes these
> problems. With this patch and the current CVS version of wpa_supplicant,
> I was able to complete IEEE 802.1X (non-WPA) authentication and use the
> encrypted data connection (both unicast and multicast worked).

I will try it later tonight or tomorrow and report. Thanks. 

Romano 

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



From togg  Mon Nov 29 06:35:11 2004
From: togg (Sebastian Weitzel)
Date: Mon, 29 Nov 2004 15:35:11 +0100 (CET)
Subject: wpa_supplicant: new driver interface API
In-Reply-To: <20041129035115.GB7025@jm.kir.nu>
References: <20041129035115.GB7025@jm.kir.nu>
Message-ID: <4655.213.146.118.69.1101738911.squirrel@213.146.118.69>

> The current development branch in CVS has a new version of the
> wpa_supplicant driver API. This is the major cleanup I had planned for
> the new development branch to fix some design flaws in the original API.

Hi Jouni,

I did not yet found time to look at the source, but do you think it would
be possible to integrate a multi-interface (or multi-config) support to
wpa_supplicant as it is already in hostapd?

It would be nice to support multiple interfaces with one wpa_supplicant to
save memory and configuration overhead.


Regards,
Sebastian Weitzel





From brix  Mon Nov 29 07:25:20 2004
From: brix (Henrik Brix Andersen)
Date: Mon, 29 Nov 2004 16:25:20 +0100
Subject: wpa_supplicant pkg-config patch
Message-ID: <1101741921.7822.15.camel@sponge.fungus>

Hi Jouni,

I've written a patch for the Makefile of wpa_supplicant-0.2.5 to use
pkg-config to determine the LIBS and CFLAGS to use for pcsc-lite and
OpenSSL.

The dnet library still doesn't come with a libdnet.pc file for
pkg-config, but it has a legacy dnet-config utility which works the
same. The pcap library doesn't provide either and is therefore still
hard-coded in the Makefile.

I have removed the commented lines for setting CFLAGS and LIBS for
unusual installation paths of OpenSSL since this can now be handled
globally by setting the environment variable PKG_CONFIG_PATH to the path
of the .pc file(s).

The need for the patch rose when attempting to build against
>=pcsc-lite-1.2.9-beta3, since the default location of the header files
changed from /usr/include to /usr/include/PSCS.

Sincerely,
Brix
-- 
Henrik Brix Andersen <brix at gentoo.org>
Gentoo Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-0.2.5-pkg-config.patch
Type: text/x-patch
Size: 1719 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041129/e0e96a2d/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/20041129/e0e96a2d/attachment.pgp 


From romanol  Mon Nov 29 09:47:40 2004
From: romanol (Romano Giannetti)
Date: Mon, 29 Nov 2004 18:47:40 +0100
Subject: Problem setting keys with ndiswrapper after authentication?
In-Reply-To: <20041129134536.3B1DB13790D@pgiri.homelinux.org>
References: <20041126091621.GA14791@pern.dea.icai.upco.es>
	<20041128045536.GC6904@jm.kir.nu>
	<20041129112343.GB18542@pern.dea.icai.upco.es>
Message-ID: <20041129174740.GA28861@pern.dea.icai.upco.es>

On Mon, Nov 29, 2004 at 08:45:35AM -0500, Giridhar Pemmasani wrote:
> 
> Please try current cvs of ndiswrapper. It already has fixes that Jouni
> sent earlier - you don't need to change iw_ndis.c.

Hi. I tried the last ndiswrapper CVS 0.12 at 041129 with wpa_supplicant 0.2.5
as suggested here; I have to say that I had a partial success: one step
more, but nevertheless the connection does not come up. 

A bit of debug output: 

as before, I do the manual association of the interface: 

[root at rukbat ndiswrapper]# iwconfig wlan0 mode managed essid upco_wlan key 0 open

(By the way: sometime I have to repeat the above two or three time before
having the essid association shown). 

[root at rukbat ndiswrapper]# iwconfig wlan0 && ifconfig wlan0
wlan0     IEEE 802.11b  ESSID:"upco_wlan"  
          Mode:Managed  Frequency:2.442GHz  Access Point: 00:11:5C:6B:90:E0  
          Bit Rate:11Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:2432 B   Fragment thr:2432 B   
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:-54 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr 00:0B:9D:00:B2:6E  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:60 (60.0 b)  TX bytes:0 (0.0 b)
          Interrupt:9 Memory:10800000-108000ff 

[root at rukbat ndiswrapper]# wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf -dd
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=0
Line: 191 - start of a new network block
SSID - hexdump_ascii(len=9):
     75 70 63 6f 5f 77 6c 61 6e                        upco_wlan       
key_mgmt: 0x8
eap methods - hexdump(len=2): 19 00
identity - hexdump_ascii(len=16):
     72 6f 6d 61 6e 6f 40 75 70 63 6f 6e 74 2e 65 73   romano at upcont.es
password - hexdump_ascii(len=9):
****password removed****

...etc, like before. I remove all the output until the new problem...

[...]
EAP-PEAP: Phase 2 Request: type=26
EAP-PEAP: Phase 2 EAP packet
EAP-MSCHAPV2: Received success
EAP-MSCHAPV2: Success message - hexdump(len=0):
EAP-MSCHAPV2: Authentication succeeded
EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 f0 00 06 1a 03

...ok? It seems that the identification succeeded.

[...]
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1 key_length=13 key_index=0x0
EAPOL: EAPOL-Key key signature verified
EAPOL: Decrypted(RC4) key - hexdump(len=13): 13 ab d7 39 ef 08 e0 bc 63 a7 d1 a8 b9
EAPOL: Setting dynamic WEP key: broadcast keyidx 0 len 13

Bingo, now it works (and iwconfig shows the new key set). But now, when I
try to start dhclient there is no answer, and wpa_supplicant says: 

WPA: EAPOL frame too short, len 61, expecting at least 99
EAPOL: Port Timers tick - authWhile=29 heldWhile=0 startWhen=29 idleWhile=59
EAPOL: Port Timers tick - authWhile=28 heldWhile=0 startWhen=28 idleWhile=58
EAPOL: Port Timers tick - authWhile=27 heldWhile=0 startWhen=27 idleWhile=57
EAPOL: Port Timers tick - authWhile=26 heldWhile=0 startWhen=26 idleWhile=56
EAPOL: Port Timers tick - authWhile=25 heldWhile=0 startWhen=25 idleWhile=55
EAPOL: Port Timers tick - authWhile=24 heldWhile=0 startWhen=24 idleWhile=54
EAPOL: Port Timers tick - authWhile=23 heldWhile=0 startWhen=23 idleWhile=53
EAPOL: Port Timers tick - authWhile=22 heldWhile=0 startWhen=22 idleWhile=52
EAPOL: Port Timers tick - authWhile=21 heldWhile=0 startWhen=21 idleWhile=51
Authentication with 00:11:5c:6b:90:e0 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
EAPOL: Port Timers tick - authWhile=20 heldWhile=0 startWhen=20 idleWhile=50
EAPOL: Port Timers tick - authWhile=19 heldWhile=0 startWhen=19 idleWhile=49
EAPOL: Port Timers tick - authWhile=18 heldWhile=0 startWhen=18 idleWhile=48
EAPOL: Port Timers tick - authWhile=17 heldWhile=0 startWhen=17 idleWhile=47
EAPOL: Port Timers tick - authWhile=16 heldWhile=0 startWhen=16 idleWhile=46
EAPOL: Port Timers tick - authWhile=15 heldWhile=0 startWhen=15 idleWhile=45
EAPOL: Port Timers tick - authWhile=14 heldWhile=0 startWhen=14 idleWhile=44
EAPOL: Port Timers tick - authWhile=13 heldWhile=0 startWhen=13 idleWhile=43
EAPOL: Port Timers tick - authWhile=12 heldWhile=0 startWhen=12 idleWhile=42
EAPOL: Port Timers tick - authWhile=11 heldWhile=0 startWhen=11 idleWhile=41
Authentication with 00:11:5c:6b:90:e0 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
EAPOL: Port Timers tick - authWhile=10 heldWhile=0 startWhen=10 idleWhile=40
EAPOL: Port Timers tick - authWhile=9 heldWhile=0 startWhen=9 idleWhile=39
EAPOL: Port Timers tick - authWhile=8 heldWhile=0 startWhen=8 idleWhile=38
EAPOL: Port Timers tick - authWhile=7 heldWhile=0 startWhen=7 idleWhile=37
EAPOL: Port Timers tick - authWhile=6 heldWhile=0 startWhen=6 idleWhile=36
EAPOL: Port Timers tick - authWhile=5 heldWhile=0 startWhen=5 idleWhile=35
EAPOL: Port Timers tick - authWhile=4 heldWhile=0 startWhen=4 idleWhile=34
EAPOL: Port Timers tick - authWhile=3 heldWhile=0 startWhen=3 idleWhile=33
RX EAPOL from 00:11:5c:6b:90:e0
RX EAPOL - hexdump(len=46): 01 00 00 05 01 01 00 05 01 00 00 00 00 00 00 00 00 00 00 00 00 00 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: Received EAP-Packet frame
WPA: EAPOL frame too short, len 46, expecting at least 99
EAPOL: Port Timers tick - authWhile=2 heldWhile=0 startWhen=2 idleWhile=32
EAPOL: Port Timers tick - authWhile=1 heldWhile=0 startWhen=1 idleWhile=31
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=30
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=29
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=28
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=27
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=26
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=25
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=24
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=23
Authentication with 00:11:5c:6b:90:e0 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=22
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=21
Signal 2 received - terminating
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0

...and no data pass thru the wlan0 interface. I do not know if it's my
ignorance or what. I run dhclient -n -d wlan0 to avoid reconfiguration of
the interface, but I tried various variations without success. 

Any hints? Thanks! 

Romano



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



From reeopp  Mon Nov 29 10:57:35 2004
From: reeopp (Oscar p)
Date: Mon, 29 Nov 2004 19:57:35 +0100
Subject: problem with madwifi drivers
In-Reply-To: <32653c9704112818418d3b563@mail.gmail.com>
Message-ID: <BAY13-F1810BB118F526539FF4E7DD2BD0@phx.gbl>

Hi YenJung,

I already did so however there must be something else I'm trying to find 
out....
I'll let you know whenever I find it....

Thanks
Oscar

>From: YenJung Chang <yenjung at gmail.com>
>Reply-To: YenJung Chang <yenjung at gmail.com>
>To: Oscar p <reeopp at hotmail.com>
>CC: hostap at shmoo.com
>Subject: Re: problem with madwifi drivers
>Date: Mon, 29 Nov 2004 10:41:14 +0800
>
>Sorry for reply so late. I took two days vacation. :)
>
>If you did not setup ath0 as dhcp client, it would not get IP 
>automatically.
>You can setup its ip manually after it connected to a AP.
>Moreover, I don't how Mandrake configures and set network interface at
>system starting, I have no suggestion for this.
>
>yj.
>
>On Sat, 27 Nov 2004 21:25:16 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > Hi all
> > It looks like finally solved, I have installed Mandrake instead of SuSE 
>and
> > compiled madwifi again. Fortunately there is a wpa_supplicant rpm for
> > mandrake which I instlled. Now everything seems to work, do not aske me
> > exactly why....
> >
> > I'm facing a different problem now, everything seems to work but I'm not
> > getting any IP, look:
> > [root at Compaq network-scripts]# wpa_supplicant -Bd -iath0
> > -c/etc/wpa_supplicant.conf -Dmadwifi
> >
> >
> > 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 5
> >    id=0 ssid='OSCARLAN'
> > Using existing control interface directory.
> > 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_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
> > Daemonize..
> > [root at Compaq network-scripts]# iwconfig
> > lo        no wireless extensions.
> >
> > eth0      no wireless extensions.
> >
> > ath0      IEEE 802.11g  ESSID:"OSCARLAN"  Nickname:"Compaq"
> >           Mode:Managed  Frequency:2.437GHz  Access Point: 
>00:80:5A:22:AA:54
> >           Bit Rate=54Mb/s   Tx-Power:50 dBm   Sensitivity=0/3
> >           Retry:off   RTS thr:off   Fragment thr:off
> >           Encryption key:20EE-672E-ABA4-1854-6EB3-C34F-5480-ACDA   
>Security
> > mode:restricted
> >           Power Management:off
> >           Link Quality:23/94  Signal level:-72 dBm  Noise level:-95 dBm
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> >
> > but :
> >
> > [root at Compaq network-scripts]# ifconfig
> > ath0      Link encap:Ethernet  HWaddr 00:80:5A:22:11:78
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:32 errors:6 dropped:0 overruns:0 frame:6
> >           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:199
> >           RX bytes:4025 (3.9 Kb)  TX bytes:2216 (2.1 Kb)
> >           Interrupt:11 Memory:d1ad5000-d1ae5000
> >
> > I've updated ifcfg-ath0 and wireless:
> >
> >     if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
> >         /usr/local/bin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf \
> >                 -Dmadwifi -i$DEVICE
> >     fi
> > and wireless.opt:
> >
> >     MODE="Managed"
> >     WPA="y"
> >     ;;
> >
> > For some reason when the system is started wireless doesn't work and I 
>have
> > to restart wpa_supplicant and the network itself....
> >
> > I don't know if I should ask or help in a new thread or is it ok here, 
>so in
> > case I should let me know!!!
> >
> > Thanks a lot
> > Oscar
> >
> > >From: "Oscar p" <reeopp at hotmail.com>
> > >To: yenjung at gmail.com
> > >CC: hostap at shmoo.com
> > >Subject: Re: problem with madwifi drivers
> > >Date: Fri, 26 Nov 2004 16:04:36 +0100
> > >
> > >Hi
> > >
> > >This is what I did:
> > >
> > >1.- remove all driver files from /lib/modules/2.6.4-52-default/net
> > >2.- reboot the machine without wireless card
> > >3.- compile the madwifi again
> > >4.- copy wlan.o, ath_hal.o, ath_pci.o, wlan_acl.o, wlan_wep.o, 
>wlan_tkip.o,
> > >wlan_ccmp.o, into  /lib/modules/2.6.4-52-default/net
> >
> >
> > >5.- try insmod on wlan.o, wlan_acl.o, wlan_wep.o, wlan_tkip.o, 
>wlan_ccmp.o,
> > >ath_hal.o, ath_pci.o, all of them were properly loaded but ath_pci:
> > >
> > >Compaq:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> > >insmod: error inserting 'ath/ath_pci.o': -1 Unknown symbol in module
> > >
> > >dmesg messages:
> > >
> > >
> > >Nov 26 15:50:33 Compaq kernel: wlan: no version for "struct_module" 
>found:
> > >kernel tainted.
> > >Nov 26 15:50:33 Compaq kernel: wlan: no version magic, tainting kernel.
> > >Nov 26 15:50:33 Compaq kernel: wlan: 0.8.4.4 (EXPERIMENTAL)
> > >Nov 26 15:50:51 Compaq kernel: wlan_acl: no version magic, tainting 
>kernel.
> > >Nov 26 15:50:51 Compaq kernel: wlan: mac acl policy registered
> > >Nov 26 15:51:05 Compaq kernel: wlan_wep: no version magic, tainting 
>kernel.
> > >Nov 26 15:51:17 Compaq kernel: wlan_tkip: no version magic, tainting
> > >kernel.
> > >Nov 26 15:51:30 Compaq kernel: wlan_ccmp: no version magic, tainting
> > >kernel.
> > >Nov 26 15:51:38 Compaq kernel: ath_hal: no version magic, tainting 
>kernel.
> > >Nov 26 15:51:38 Compaq kernel: ath_hal: module license 'Proprietary' 
>taints
> > >kernel.
> > >Nov 26 15:51:38 Compaq kernel: ath_hal: 0.9.12.14 (AR5210, AR5211, 
>AR5212)
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: no version magic, tainting 
>kernel.
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_tx_complete
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_attach
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_newassoc
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_node_copy
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol
> > >ath_rate_node_cleanup
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol ath_rate_detach
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_node_init
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_findrate
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol 
>ath_rate_newstate
> > >Nov 26 15:51:52 Compaq kernel: ath_pci: Unknown symbol
> > >ath_rate_setupxtxdesc
> > >
> > >6.- I inserted the pmcia with the following messages:
> > >
> > >
> > >Nov 26 15:52:11 Compaq /etc/hotplug/pci.agent[5742]: FATAL: Error 
>inserting
> > >ath_pci (/lib/modules/2.6.4-52-default/extra/ath_pci.ko): Unknown 
>symbol in
> > >module, or unknown parameter (see dmesg)
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_encap
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_encap
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_input
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ieee80211_input
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_ifattach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_ifattach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >_ath_hal_attach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol _ath_hal_attach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_ifdetach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_ifdetach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ath_hal_computetxtime
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> > >ath_hal_computetxtime
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_dump_pkt
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_dump_pkt
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ath_hal_detach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol ath_hal_detach
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_media_change
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> > >ieee80211_media_change
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_add_xrates
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_iterate_nodes
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> > >ieee80211_iterate_nodes
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_find_node
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_find_node
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_next_scan
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_next_scan
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_media_init
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_media_init
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_new_state
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_get_rssi
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_media_status
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> > >ieee80211_media_status
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_add_rates
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_chan2ieee
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_chan2ieee
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ath_hal_init_channels
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol
> > >ath_hal_init_channels
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: disagrees about version of 
>symbol
> > >ieee80211_chan2mode
> > >Nov 26 15:52:11 Compaq kernel: ath_pci: Unknown symbol 
>ieee80211_chan2mod
> > >
> > >it seems there is something wrong with ath_pci but I do not know what 
>it
> > >is....
> > >
> > >Thanks a lot for your help!
> > >Oscar
> > >
> > >>From: YenJung Chang <yenjung at gmail.com>
> > >>Reply-To: YenJung Chang <yenjung at gmail.com>
> > >>To: Oscar p <reeopp at hotmail.com>
> > >>CC: hostap at shmoo.com
> > >>Subject: Re: problem with madwifi drivers
> > >>Date: Fri, 26 Nov 2004 21:30:13 +0800
> > >>
> > >>Oscar,
> > >>
> > >>Maybe you should recompile madwifi and try it again.
> > >>I can not make sense of why ath_pci.o failed to insert.
> > >>
> > >>In addition, please remove inserted modules before you insert again.
> > >>
> > >>yj.
> > >>
> > >>
> > >
> >
> > _________________________________________________________________
> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




From goldygill  Mon Nov 29 17:24:40 2004
From: goldygill (RUPINDER gill)
Date: Mon, 29 Nov 2004 17:24:40 -0800 (PST)
Subject: 802.11 ACK packet examination
Message-ID: <20041130012440.41768.qmail@web52910.mail.yahoo.com>

Hi,

Is it possible to check/modify bits in 802.11 ACK
packets in hostap before sending them and just after
receiving them.  I am trying to set/check the order
bit in Frame control for an experiment. I have been
looking in the driver code and haven't been able to
find code which can help examine the ACK packets. Or
is it handled completely by the firmware ?

Any help would be much appreciated. 

Thanks
Rupinder


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail



From xinwenfu  Mon Nov 29 18:02:56 2004
From: xinwenfu (Xinwen Fu)
Date: Mon, 29 Nov 2004 20:02:56 -0600 (CST)
Subject: 802.11 ACK packet examination
In-Reply-To: <20041130012440.41768.qmail@web52910.mail.yahoo.com>
References: <20041130012440.41768.qmail@web52910.mail.yahoo.com>
Message-ID: <Pine.GSO.4.58.0411292001010.28016@unix.cs.tamu.edu>

> Is it possible to check/modify bits in 802.11 ACK
> packets in hostap before sending them and just after
> receiving them.  I am trying to set/check the order
> bit in Frame control for an experiment. I have been
> looking in the driver code and haven't been able to
> find code which can help examine the ACK packets. Or
> is it handled completely by the firmware ?

	ACK is done in firmware not in driver code. Basically, you cannot
do any MAC protocol stuff in driver code, and it is all done in firmware
(card ROM).

Fu



>
> Any help would be much appreciated.
>
> Thanks
> Rupinder
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Helps protect you from nasty viruses.
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From jt  Mon Nov 29 18:07:34 2004
From: jt (Jean Tourrilhes)
Date: Mon, 29 Nov 2004 18:07:34 -0800
Subject: [PATCH] Cross compile 0.2.5 on arm 2.6.X
Message-ID: <20041130020733.GA15982@bougret.hpl.hp.com>

	Hi Jouni,

	I found the following problem cross compiling HostAP 0.2.5 for
the ARM platform. The in/out I/O functions are not resolved at
link/depmod time. On the ARM, they are #define, not actual functions.
	The attached patch fix that problem by including <asm/io.h>,
and the driver works fine. Obviously, you may want to do that
differently. The funny thing is that hostap_cs.c include that file,
while none of the other do...
	Note that this is for compilation in-kernel. I did not manage
to cross-compile out of kernel, it mixes ARM and i386 at ELF time, and
I'm stumped. As in-kernel works...
	Have fun...

	Jean

---------------------------------------------------------------

diff -u -p --new-file linux-2.6.9-rc1/drivers/net/wireless-j2/hostap_compat.h linux-2.6.9-rc1/drivers/net/wireless/hostap_compat.h
--- linux-2.6.9-rc1/drivers/net/wireless-j2/hostap_compat.h	2004-11-29 14:47:11.000000000 -0800
+++ linux-2.6.9-rc1/drivers/net/wireless/hostap_compat.h	2004-11-29 14:53:05.000000000 -0800
@@ -1,6 +1,11 @@
 #ifndef HOSTAP_COMPAT_H
 #define HOSTAP_COMPAT_H
 
+#if (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,0))
+/* Cross compiling on ARM with 2.6.X require that - Jean II */
+#include <asm/io.h>
+#endif
+
 #if (LINUX_VERSION_CODE > KERNEL_VERSION(2,5,47))
 #define NEW_MODULE_CODE
 #endif




From mrcool  Mon Nov 29 18:17:54 2004
From: mrcool (Jerry)
Date: Mon, 29 Nov 2004 20:17:54 -0600
Subject: Question about 'iwconfig wlanX ap'  command
Message-ID: <002901c4d682$cd459b00$b900a8c0@Home>

Hello!

I have a "feed" link that is a client to an access point.  Its a 12 mile
link that isnt really "strong" but i get good throughput, so i presume that
there isnt packet loss.  Problem was, even though i would set the essid on
the client, it would sometimes roam to another AP (but still show the
correct essid).  It wasnt too secure anyway, so my solution was this:

on the AP I use:   iwpriv wlan0 maccmd 1   <- turns on mac filter
                           iwpriv wlan0 addmac 11:22:33:44:55:66  (where mac
is zcomax clone in client below.)

on the client i use: iwpriv wlan0 host_roaming 2   <- turns OFF roaming
                            iwconfig wlan0 ap 00:02:6f:aa:bb:cc  (where mac
is AP above)

The idea is to make these units a point to point link (my luck with Ad-Hoc
has been less than stellar), nothing else can associate to the AP, and the
client should ONLY associate to this particular AP.  And this works like it
should. but if the AP is rebooted, or gone for whatever reason for a short
period of time, the client will not re-associate. I have to log into the
client and : "iwconfig wlan0 ap 00:02:6f:aa:bb:cc" again for it to
reassociate.   Is this the fault of the host_roaming command?

To be honest I havent tried it without the host_roaming command (just the
iwconfig wlan0 ap command alone) to see if the iwconfig ap command was
enough.  My solution was to cron the iwconfig wlan0 ap command every 5
minutes, which is probably using a sledgehammer on a finishing nail.

suggestions, clarifications?

Thanks!
Jerryf




From jkmaline  Mon Nov 29 21:28:48 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 21:28:48 -0800
Subject: wpa_supplicant: new driver interface API
In-Reply-To: <4655.213.146.118.69.1101738911.squirrel@213.146.118.69>
References: <20041129035115.GB7025@jm.kir.nu>
	<4655.213.146.118.69.1101738911.squirrel@213.146.118.69>
Message-ID: <20041130052848.GB7025@jm.kir.nu>

On Mon, Nov 29, 2004 at 03:35:11PM +0100, Sebastian Weitzel wrote:

> I did not yet found time to look at the source, but do you think it would
> be possible to integrate a multi-interface (or multi-config) support to
> wpa_supplicant as it is already in hostapd?

This was not in my original plans, but the use of the same event loop
implementation that is used in hostapd should make this quite
straightforwarded. In fact, I ended up doing this now.

> It would be nice to support multiple interfaces with one wpa_supplicant to
> save memory and configuration overhead.

The current devel snapshot should have this implemented. I tested only
with a dummy driver interface as an extra interface and one real radio
and it seemed to work. Anyway, if you end up testing this, please let me
know whether it works with two (or more) real radios..

You will need to specify all interfaces on the command line, separated
with -N. For example:

wpa_supplicant -cwpa1.conf -iwlan0 -Dhostap -N -cwpa2.conf -iath0 -Dmadwifi

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 29 21:38:04 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 21:38:04 -0800
Subject: [PATCH] Cross compile 0.2.5 on arm 2.6.X
In-Reply-To: <20041130020733.GA15982@bougret.hpl.hp.com>
References: <20041130020733.GA15982@bougret.hpl.hp.com>
Message-ID: <20041130053804.GC7025@jm.kir.nu>

On Mon, Nov 29, 2004 at 06:07:34PM -0800, Jean Tourrilhes wrote:

> 	I found the following problem cross compiling HostAP 0.2.5 for
> the ARM platform. The in/out I/O functions are not resolved at
> link/depmod time. On the ARM, they are #define, not actual functions.
> 	The attached patch fix that problem by including <asm/io.h>,
> and the driver works fine. Obviously, you may want to do that
> differently. The funny thing is that hostap_cs.c include that file,
> while none of the other do...

Thanks!

Hmm.. I think it'll be simpler to just include asm/io.h to all
hostap_{cs,plx,pci} modules whether it is really needed or not. There
should not be any need to limit this to 2.6.x either.

I would assume hostap_cs.c ended up including this file either because I
needed it at some point for one of my target platforms that do not have
PCI bus.. Alternatively, it may have something to do with external
pcmcia-cs compilation.

> 	Note that this is for compilation in-kernel. I did not manage
> to cross-compile out of kernel, it mixes ARM and i386 at ELF time, and
> I'm stumped. As in-kernel works...

I'm assuming you mean using kernel Makefile or not with
in/out-of-kernel.. I believe I have cross-compiled it
out-of-tree many times. However, nowadays I use kernel Makefiles for all
builds, so I wouldn't be too surprised if the Host AP makefile would not
handle something properly. If you meant linked-in-kernel without using
modules, then you can of course ignore this part ;-).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 29 21:55:05 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 21:55:05 -0800
Subject: Problem setting keys with ndiswrapper after authentication?
In-Reply-To: <20041129174740.GA28861@pern.dea.icai.upco.es>
References: <20041126091621.GA14791@pern.dea.icai.upco.es>
	<20041128045536.GC6904@jm.kir.nu>
	<20041129112343.GB18542@pern.dea.icai.upco.es>
	<20041129174740.GA28861@pern.dea.icai.upco.es>
Message-ID: <20041130055505.GD7025@jm.kir.nu>

On Mon, Nov 29, 2004 at 06:47:40PM +0100, Romano Giannetti wrote:

> Hi. I tried the last ndiswrapper CVS 0.12 at 041129 with wpa_supplicant 0.2.5

> [root at rukbat ndiswrapper]# wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf -dd

> ...etc, like before. I remove all the output until the new problem...

Please do not.. or at least make the full output available somewhere.

> EAP-PEAP: Phase 2 Request: type=26
> EAP-PEAP: Phase 2 EAP packet
> EAP-MSCHAPV2: Received success
> EAP-MSCHAPV2: Success message - hexdump(len=0):
> EAP-MSCHAPV2: Authentication succeeded
> EAP-PEAP: Encrypting Phase 2 data - hexdump(len=6): 02 f0 00 06 1a 03
> 
> ...ok? It seems that the identification succeeded.

No, this is not yet completed. PEAP requires additional success
notification.. This was not included in this message, but I would assume
it actually succeeded based on the following output.

> [...]
> EAPOL: Received EAPOL-Key frame
> EAPOL: KEY_RX entering state KEY_RECEIVE
> EAPOL: processKey
> EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1 key_length=13 key_index=0x0
> EAPOL: EAPOL-Key key signature verified
> EAPOL: Decrypted(RC4) key - hexdump(len=13): 13 ab d7 39 ef 08 e0 bc 63 a7 d1 a8 b9
> EAPOL: Setting dynamic WEP key: broadcast keyidx 0 len 13

Again, getting more context would be useful, but I'm guessing here for
now.. You received only one key (broadcast), but wpa_supplicant was
configured to expect two keys (separate unicast key). Both cases are
valid for IEEE 802.1X, but if you use only one key (this broadcast one),
you will need to tell wpa_supplicant about this by setting eapol_flags=2
in the configuration file.

> Bingo, now it works (and iwconfig shows the new key set). But now, when I
> try to start dhclient there is no answer, and wpa_supplicant says: 
> 
> WPA: EAPOL frame too short, len 61, expecting at least 99
> EAPOL: Port Timers tick - authWhile=29 heldWhile=0 startWhen=29 idleWhile=59
> EAPOL: Port Timers tick - authWhile=28 heldWhile=0 startWhen=28 idleWhile=58
> EAPOL: Port Timers tick - authWhile=27 heldWhile=0 startWhen=27 idleWhile=57
> EAPOL: Port Timers tick - authWhile=26 heldWhile=0 startWhen=26 idleWhile=56
> EAPOL: Port Timers tick - authWhile=25 heldWhile=0 startWhen=25 idleWhile=55
> EAPOL: Port Timers tick - authWhile=24 heldWhile=0 startWhen=24 idleWhile=54
> EAPOL: Port Timers tick - authWhile=23 heldWhile=0 startWhen=23 idleWhile=53
> EAPOL: Port Timers tick - authWhile=22 heldWhile=0 startWhen=22 idleWhile=52
> EAPOL: Port Timers tick - authWhile=21 heldWhile=0 startWhen=21 idleWhile=51
> Authentication with 00:11:5c:6b:90:e0 timed out.

wpa_supplicant did not receive the other expected key (unicast) and
consequently timed out authentication.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 29 22:07:51 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 22:07:51 -0800
Subject: wpa_supplicant pkg-config patch
In-Reply-To: <1101741921.7822.15.camel@sponge.fungus>
References: <1101741921.7822.15.camel@sponge.fungus>
Message-ID: <20041130060751.GE7025@jm.kir.nu>

On Mon, Nov 29, 2004 at 04:25:20PM +0100, Henrik Brix Andersen wrote:

> I've written a patch for the Makefile of wpa_supplicant-0.2.5 to use
> pkg-config to determine the LIBS and CFLAGS to use for pcsc-lite and
> OpenSSL.

Thanks! I have not been using pkg-config much, but based on what I can
see, it does not seem to handle cross compilation cases, nor cases where
there are more than one version of the library installed, easily. Both
of these cases are quite common for wpa_supplicant.

> I have removed the commented lines for setting CFLAGS and LIBS for
> unusual installation paths of OpenSSL since this can now be handled
> globally by setting the environment variable PKG_CONFIG_PATH to the path
> of the .pc file(s).

Or would this be the way to handle cross compilation or multiple
versions with pkg-config? Sounds somewhat complex if I need to end up
writing one set of .pc files for each target system (of which there are
dozen or so)..

I would still prefer to be able to easily set these paths and library
selection in the Makefile, .config, and make command line. Having
pkg-config as the default should be ok, but I would like to first verify
that some of the not-so-simple cross compilation setups do not suffer
too much with this kind of change.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 29 22:15:41 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 22:15:41 -0800
Subject: [PATCH] WPA Supplicant hidden ssid support
In-Reply-To: <200411281222.17467.saschasommer@freenet.de>
References: <200411281222.17467.saschasommer@freenet.de>
Message-ID: <20041130061541.GF7025@jm.kir.nu>

On Sun, Nov 28, 2004 at 12:22:17PM +0100, Sascha Sommer wrote:

> just tryed out ndiswrapper + wpa supplicant with an linksys wrt54g and an 
> acx111 wlan card. Unfortunatelly wpa supplicant had problems with the 
> authentication due to the hidden ssid.

In general, wpa_supplicant supports hidden SSIDs, but ndiswrapper
interface does not yet..

> I attached a trivial patch against 0.2.5 to fix this. I'm not sure if it will 
> work with all configuration, but I think you will get the idea.

This is not suitable for cases where there are multiple APs configured
with hidden SSIDs and/or multiple security policies in wpa_supplicant
networks. driver_ndiswrapper will need to do something more complex to
handle this case. It looks like NDIS driver will need to at least be
configured with the correct SSID (i.e., make them try to associate with
the AP using hidden SSID) before scan results include these APs.
However, this might not be enough, since there are number of different
security policies..

One simple test case would be to add set_ssid call to scan request in
driver_ndiswrapper.c and then go through all the possible security
policies and verify whether the AP is found or not. If not, one would
need to uset set_ssid and in addition, go through all security policies
to match the scanning capability expected by wpa_supplicant.. Alas, this
cannot be done cleanly in driver_ndiswrapper.c and would thus require
changes that make the core implementation more complex.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Nov 29 22:18:22 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 29 Nov 2004 22:18:22 -0800
Subject: Question about 'iwconfig wlanX ap'  command
In-Reply-To: <002901c4d682$cd459b00$b900a8c0@Home>
References: <002901c4d682$cd459b00$b900a8c0@Home>
Message-ID: <20041130061822.GG7025@jm.kir.nu>

On Mon, Nov 29, 2004 at 08:17:54PM -0600, Jerry wrote:

> on the client i use: iwpriv wlan0 host_roaming 2   <- turns OFF roaming

Not only roaming..

> The idea is to make these units a point to point link (my luck with Ad-Hoc
> has been less than stellar), nothing else can associate to the AP, and the
> client should ONLY associate to this particular AP.  And this works like it
> should. but if the AP is rebooted, or gone for whatever reason for a short
> period of time, the client will not re-associate. I have to log into the
> client and : "iwconfig wlan0 ap 00:02:6f:aa:bb:cc" again for it to
> reassociate.   Is this the fault of the host_roaming command?

No, it is doing exactly what it is expected to do, i.e., not join the AP
automatically if the link gets down for any reason.. You might want to
test with host_roaming=1, which actually allows the firmware to start
scanning if the client gets disassociated.

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Mon Nov 29 23:32:35 2004
From: gbur (Gunter Burchardt)
Date: Tue, 30 Nov 2004 08:32:35 +0100
Subject: New SessionID and statistics
Message-ID: <20041130073234.GB23962@informatik.uni-rostock.de>

Hi Jouni,

I looked throug your last changes in hostapd and found following change
in ieee802_11.c:

  /* Stop previous accounting session, if one is started, and allocate
   * new session id for the new session. */
  accounting_sta_stop(hapd, sta);
  accounting_sta_get_id(hapd, sta);

Generating a new sessionid is a great idea (i had a not submitted patch
for my own doing this) but you missid one thing. You have to reset the
accounting data in driver! At the moment it is only possible to do this
by deleting the station from driver and readd the station. A new IOCTRL
only reseting the stats would be fine. I have such an IOCTRL in
PAE-module.

regards
gunter 



From andreas  Tue Nov 30 00:27:51 2004
From: andreas (Andreas Schuldei)
Date: Tue, 30 Nov 2004 09:27:51 +0100
Subject: [Madwifi-devel] Re: madwifi(cvs),
	wpa_supp v0.2.5 and linksys router problem
In-Reply-To: <200411281422.11005.sam@errno.com>
References: <20041122003048.GA11581@timotheus.schuldei.org>
	<20041126131928.GB15224@lukas.schuldei.com>
	<20041128012458.GB6904@jm.kir.nu>
	<200411281422.11005.sam@errno.com>
Message-ID: <20041130082751.GC9983@lukas.schuldei.com>

* Sam Leffler (sam at errno.com) [041128 23:14]:
> [hostap@ trimmed since it appears unrelated to hostap stuff]
> 
> On Saturday 27 November 2004 05:24 pm, Jouni Malinen wrote:
> > On Fri, Nov 26, 2004 at 02:19:28PM +0100, Andreas Schuldei wrote:
> > > ok, here are some logs with debugging in the madwifi driver
> > > activated (by echo 1 > /proc/sys/dev/ath0/debug)
> >
> > Thanks. This is starting to point towards being something to do with the
> > driver and not wpa_supplicant, so I cc'ed madwifi-devel mailing list
> > which is probably a more suitable forum for this question.

ok, i attache the trivial perl program i wrote to pull together
all the debug output and put it in the correct cronological order
in which it appeared. note that i seems to have dropped a char
here and there, but i think that is not critical. I hope this
perlscript can help others collecting meaningfull debug data,
too.

i also had to unbuffer wpa_supplicant`s output to make that
possible. i added a fflush(stdout); in wpa_printf. I would
recommend doing that upstream, too, for better usability in
debugging environments.

i let the logging run over night and there were several
connection losses during that time. this resulted in 39Mbyte of
log data. i bzip2'ed them and put the resulting 1.5Mbyte file up
on http://www.schuldei.org/debug.txt.bz2

i hope you find all the evidence/data you need to squish this
bugger. if you do need a sniffer log on top of that i could do
that, too. if you can do without that, i am happy. (c:

looking at the athstats output of the file i see periodic raise
and fall of the pysical error rate. i know that EMI
(electromagnetic interferance?) can play funny games... but what
device has such a interferance pattern?  it seems to be allmost
error free for ca 30 seconds to go up to 20-40 errors a second
for minutes. is this my antenna/network device breaking or my
neighbours fridge going on and off?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syncronous-logging.pl
Type: text/x-perl
Size: 1541 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20041130/2c945fc3/attachment.pl 


From st3v3  Tue Nov 30 01:33:31 2004
From: st3v3 (st3v3 at btinternet.com)
Date: Tue, 30 Nov 2004 09:33:31 +0000 (GMT)
Subject: hostapd(cvs) & madwifi(cvs) - PATCH attached
Message-ID: <20041130093331.939.qmail@web86111.mail.ukl.yahoo.com>

Hey all
Further to my posting the problem of 802.1x authentication without WPA.
See thread "hostapd(cvs) & madwifi(cvs)"
Find attached a patch that allows for this particular configuration.
The driver_madwifi.c assumes that with 802.1x WPA must be used IMHO this is incorrect, as 802.1x may be used without WPA. i.e 802.1x with WEP
The error "No WPA/RSN information available for station" is seen if 
wpa=0 or not set in the hostapd.conf file.
Could a developer please review this patch and add it to the CVS repository.
I have tested this code with hostapd CVS dated 25.11.04 and the CVS of madwifi at the same date.
Kind Regards
Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20041130/ccfd2be4/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa-and-8021x.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20041130/ccfd2be4/attachment.txt 


From saschasommer  Tue Nov 30 02:03:42 2004
From: saschasommer (Sascha Sommer)
Date: Tue, 30 Nov 2004 11:03:42 +0100
Subject: [PATCH] WPA Supplicant hidden ssid support
In-Reply-To: <20041130061541.GF7025@jm.kir.nu>
References: <200411281222.17467.saschasommer@freenet.de>
	<20041130061541.GF7025@jm.kir.nu>
Message-ID: <200411301103.42260.saschasommer@freenet.de>

On Tuesday 30 November 2004 07:15, Jouni Malinen wrote:
> On Sun, Nov 28, 2004 at 12:22:17PM +0100, Sascha Sommer wrote:
> > just tryed out ndiswrapper + wpa supplicant with an linksys wrt54g and an
> > acx111 wlan card. Unfortunatelly wpa supplicant had problems with the
> > authentication due to the hidden ssid.
>
> In general, wpa_supplicant supports hidden SSIDs, but ndiswrapper
> interface does not yet..
>

I don't understand how this is possible, because I think it is always using 
the broadcasted ssid for authentication, but then I didn't check the whole 
code, therefore I might have overseen something.

> > I attached a trivial patch against 0.2.5 to fix this. I'm not sure if it
> > will work with all configuration, but I think you will get the idea.
>
> This is not suitable for cases where there are multiple APs configured
> with hidden SSIDs and/or multiple security policies in wpa_supplicant
> networks. driver_ndiswrapper will need to do something more complex to
> handle this case. It looks like NDIS driver will need to at least be
> configured with the correct SSID (i.e., make them try to associate with
> the AP using hidden SSID) before scan results include these APs.
> However, this might not be enough, since there are number of different
> security policies..

I already suspected something like this.

> One simple test case would be to add set_ssid call to scan request in
> driver_ndiswrapper.c and then go through all the possible security
> policies and verify whether the AP is found or not. If not, one would
> need to uset set_ssid and in addition, go through all security policies
> to match the scanning capability expected by wpa_supplicant.. Alas, this
> cannot be done cleanly in driver_ndiswrapper.c and would thus require
> changes that make the core implementation more complex.

No idea, I prefer the opensource acx100 driver, only tryed things out.
My patch will do it for me in my testcase.

Thanks for your answer.


Sascha



From brix  Tue Nov 30 02:25:58 2004
From: brix (Henrik Brix Andersen)
Date: Tue, 30 Nov 2004 11:25:58 +0100
Subject: wpa_supplicant pkg-config patch
In-Reply-To: <20041130060751.GE7025@jm.kir.nu>
References: <1101741921.7822.15.camel@sponge.fungus>
	<20041130060751.GE7025@jm.kir.nu>
Message-ID: <1101810358.11116.11.camel@sponge.fungus>

On Mon, 2004-11-29 at 22:07 -0800, Jouni Malinen wrote:
> Thanks! I have not been using pkg-config much, but based on what I can
> see, it does not seem to handle cross compilation cases, nor cases where
> there are more than one version of the library installed, easily. Both
> of these cases are quite common for wpa_supplicant.

Actually, it does. If you have installed one version of the library in,
say, /usr/local/ and another in /usr, all you have to do to compile
against the one in /usr/local is call:

        PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/ make

That will pull in the CFLAGS and LDFLAGS (LIBS) from the *.pc files
found in /usr/local/lib/pkgconfig/

How does the current Makefile handle cross-compilation?

> Or would this be the way to handle cross compilation or multiple
> versions with pkg-config? Sounds somewhat complex if I need to end up
> writing one set of .pc files for each target system (of which there are
> dozen or so)..

The *.pc files are automatically generated at compilation time - so if
installing a library to two different locations, there will
automatically be two different *.pc files with different CFLAGS, etc.

> I would still prefer to be able to easily set these paths and library
> selection in the Makefile, .config, and make command line. Having
> pkg-config as the default should be ok, but I would like to first verify
> that some of the not-so-simple cross compilation setups do not suffer
> too much with this kind of change.

Of course. An option for the long run could be to port wpa_supplicant to
use the auto* tools (./configure; make; make install). That would ease
cross-compilation, multiple library versions etc a great deal.

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/20041130/66d54cde/attachment.pgp 


From bpalos  Tue Nov 30 04:55:32 2004
From: bpalos (Bogdan Palos)
Date: Tue, 30 Nov 2004 12:55:32 +0000
Subject: Netgear WG311/WPA = random connection timeouts?
Message-ID: <BAY23-F35664083B11A152E82AC80CCBE0@phx.gbl>

Hi all,
i installed Ndiswrapper 0.11 + wpa_supplicant 0.25 on Fedora Core 3 with a 
Netgear WG311 (54/108mbps) PCI card. All works ok except it only does for a 
couple of minutes :)

According to the -dd option, it hangs eventually after "Cancelling timeout 
request" or something...i'll post the exact line when i get home. It shows 1 
or 2 successful WPA key negotiations between card and AP, i can connect to 
the Net but as i said after a while (1 min, 2 min - never lasted more than 
10min) it dies on me.

"iwlist wlan0 scan" shows me 2 APs (mine and a neighbor's -> w/o any 
encryption, how typical) as well as the wpa_ie for my AP ( a WGT624 with the 
4.1.1 firmware - will update to 4.2.4 tonight).

Please help, i'm going crazy here!





From Cristian.Hesselman  Tue Nov 30 05:39:57 2004
From: Cristian.Hesselman (Cristian Hesselman)
Date: Tue, 30 Nov 2004 14:39:57 +0100
Subject: (no subject)
Message-ID: <7422EC15A76E9F4FB237EF78F933D253AAC09D@exchangebe.corporate.telin.nl>

Hi,

Can anyone tell me what happens when I set the retry limit using
iwconfig? Does it set the short retry limit or the long one? Already
tried to find an answer through the web, but no luck so far.

Thanks,
Cristian




From Cristian.Hesselman  Tue Nov 30 05:41:48 2004
From: Cristian.Hesselman (Cristian Hesselman)
Date: Tue, 30 Nov 2004 14:41:48 +0100
Subject: definition of retry limit?
Message-ID: <7422EC15A76E9F4FB237EF78F933D253AAC09E@exchangebe.corporate.telin.nl>

Hi,

Can anyone tell me what happens when I set the retry limit using
iwconfig? Does it set the short retry limit or the long one? Already
tried to find an answer through the web, but no luck so far.

Thanks,
Cristian




From romanol  Tue Nov 30 07:00:59 2004
From: romanol (Romano Giannetti)
Date: Tue, 30 Nov 2004 16:00:59 +0100
Subject: Problem setting keys with ndiswrapper after authentication?
In-Reply-To: <20041130055505.GD7025@jm.kir.nu>
References: <20041126091621.GA14791@pern.dea.icai.upco.es>
	<20041128045536.GC6904@jm.kir.nu>
	<20041129112343.GB18542@pern.dea.icai.upco.es>
	<20041129174740.GA28861@pern.dea.icai.upco.es>
	<20041130055505.GD7025@jm.kir.nu>
Message-ID: <20041130150059.GA3524@pern.dea.icai.upco.es>

First of all: 1000 of thanks for your time. 

On Mon, Nov 29, 2004 at 09:55:05PM -0800, Jouni Malinen wrote:

> > [root at rukbat ndiswrapper]# wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf -dd
> 
> > ...etc, like before. I remove all the output until the new problem...
> 
> Please do not.. or at least make the full output available somewhere.

Ok. I tried to send all of it but it was too long; I have put the complete
log available on the web...

Whep. More data for my wireless quest... this time I will not cut it, so
it's quite large. 

Commands starts with '#'. I am using cvs-ndiswrapper and cvs-wpa_supplicant,
downloaded this morning. I enabled ap_scan and it seems to work well. 

Script started on Tue 30 Nov 2004 03:26:09 PM CET

# iwconfig  wlan0 && ifconfig wlan0

wlan0     IEEE 802.11b  ESSID:off/any  
          Mode:Auto  Frequency:2.442GHz  Access Point: 00:00:00:00:00:00  
          Bit Rate:11Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:2432 B   Fragment thr:2432 B   
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:-56 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr 00:0B:9D:00:B2:6E  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1245 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:137535 (134.3 Kb)  TX bytes:2247 (2.1 Kb)
          Interrupt:9 Memory:10800000-108000ff 

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

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'ndiswrapper'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
Line: 191 - start of a new network block
ssid - hexdump_ascii(len=9):
     75 70 63 6f 5f 77 6c 61 6e                        upco_wlan       
key_mgmt: 0x8
eap methods - hexdump(len=2): 19 00
identity - hexdump_ascii(len=16):
     72 6f 6d 61 6e 6f 40 75 70 63 6f 6e 74 2e 65 73   romano at upcont.es
password - hexdump_ascii(len=9): [REMOVED]
phase2 - hexdump_ascii(len=13):
     61 75 74 68 3d 4d 53 43 48 41 50 56 32            auth=MSCHAPV2   
Priority group 0
   id=0 ssid='upco_wlan'

[...]
removed data; message was too long for the maillist managed. A complete 
log is at http://www.dea.icai.upco.es/romano/report3_complete.txt 
[...]

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=129
EAP: EAP entering state METHOD
EAP-PEAP: Received packet(len=43) - Flags 0x01
EAP-PEAP: received 37 bytes encrypted data for Phase 2
EAP-PEAP: Decrypted Phase 2 EAP - hexdump(len=11): 01 81 00 0b 21 80 03 00 02 00 01
EAP-PEAP: received Phase 2: code=1 identifier=129 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

**** 
ok: that seems to authenticate me. System managers told me that they could
see my successfull authentication. 

EAP-PEAP: Encrypting Phase 2 data - hexdump(len=11): [REMOVED]
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 11 5c 77 82 40 00 0b 9d 00 b2 6e 88 8e 01 00 00 50 02 81 00 50 19 01 17 03 01 00 20 28 df 37 23 a2 6f 23 dc 94 86 93 ac 69 a2 09 80 0e dc 7f 78 35 80 cb dd 30 52 e5 34 79 1e 31 81 17 03 01 00 20 e5 1f 13 de e1 e0 49 df c9 f9 eb ba 87 ae b3 60 c8 65 9d 5f f2 a2 4a 61 01 3d 22 60 cb d0 81 c7
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 47, expecting at least 99
RX EAPOL from 00:11:5c:77:82:40
RX EAPOL - hexdump(len=46): 01 00 00 04 03 81 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state SUCCESS
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state SUCCESS
EAPOL: SUPP_BE entering state IDLE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:11:5c:77:82:40
RX EAPOL - hexdump(len=61): 01 03 00 39 01 00 0d 00 00 41 ac 83 0b 00 b1 3d 1f dc 96 7b ca c7 a6 18 71 7e c8 5a 02 85 99 01 85 c2 4b 23 0a 04 7a 03 06 fb 65 5e ae a0 cc 00 b2 8a 34 48 fd 38 99 0a a6 84 7a e9 32
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1 key_length=13 key_index=0x1
EAPOL: EAPOL-Key key signature verified
EAPOL: Decrypted(RC4) key - hexdump(len=13): [REMOVED]
EAPOL: Setting dynamic WEP key: broadcast keyidx 1 len 13

**** That seems to set the WEP key.... 

WPA: EAPOL frame too short, len 61, expecting at least 99
RX EAPOL from 00:11:5c:77:82:40
RX EAPOL - hexdump(len=48): 01 03 00 2c 01 00 0d 00 00 41 ac 83 0b 00 b2 be e0 c6 9f 3d 67 f2 e0 c3 2a ca 68 fa 23 eb 20 83 3f 28 3a 58 a0 65 50 b4 74 5b f5 e6 39 13 12 97
EAPOL: Received EAPOL-Key frame
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=44 EAPOL-Key: type=1 key_length=13 key_index=0x83
EAPOL: EAPOL-Key key signature verified
EAPOL: using part of EAP keying material data encryption key - hexdump(len=13): [REMOVED]
EAPOL: Setting dynamic WEP key: unicast keyidx 3 len 13

*** and that the other... 

EAPOL: all required EAPOL-Key frames received
WPA: EAPOL processing complete
Cancelling authentication timeout
EAPOL: SUPP_PAE entering state AUTHENTICATED

**** Now I start (on another terminal) dhclient, which says: 

[root at rukbat romano]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.1rc14
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
 
Listening on LPF/wlan0/00:0b:9d:00:b2:6e
Sending on   LPF/wlan0/00:0b:9d:00:b2:6e
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
[...]

*** without answer. Meanwhile, wpa_supplicant continues saying: 

WPA: EAPOL frame too short, len 48, expecting at least 99
EAPOL: Port Timers tick - authWhile=29 heldWhile=0 startWhen=29 idleWhile=59
[...]
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=15
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=14
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=13

*** It seems no traffic go trough. If at this stage (in a third terminal) I
ask for wlan0 state: 

# iwconfig wlan0 && ifconfig wlan0

wlan0     IEEE 802.11b  ESSID:"upco_wlan"  
          Mode:Managed  Frequency:2.427GHz  Access Point: 00:11:5C:77:82:40  
          Bit Rate:11Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:2432 B   Fragment thr:2432 B   
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:-53 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr 00:0B:9D:00:B2:6E  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1263 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:142553 (139.2 Kb)  TX bytes:3342 (3.2 Kb)
          Interrupt:9 Memory:10800000-108000ff 

*** It seems to me that I received the keys, but no keys are used by the
driver. I feel I am really near to the connection... 

Finally, I hit ctl-c on wpa_supplicant...

Signal 2 received - terminating
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
EAP: deinitialize previously used EAP method (25, PEAP) at EAP deinit

Again, any hint? 

       Romano
       

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



From jt  Tue Nov 30 10:03:17 2004
From: jt (Jean Tourrilhes)
Date: Tue, 30 Nov 2004 10:03:17 -0800
Subject: [PATCH] Cross compile 0.2.5 on arm 2.6.X
In-Reply-To: <20041130053804.GC7025@jm.kir.nu>
References: <20041130020733.GA15982@bougret.hpl.hp.com>
	<20041130053804.GC7025@jm.kir.nu>
Message-ID: <20041130180317.GB17691@bougret.hpl.hp.com>

On Mon, Nov 29, 2004 at 09:38:04PM -0800, Jouni Malinen wrote:
> On Mon, Nov 29, 2004 at 06:07:34PM -0800, Jean Tourrilhes wrote:
> 
> > 	I found the following problem cross compiling HostAP 0.2.5 for
> > the ARM platform. The in/out I/O functions are not resolved at
> > link/depmod time. On the ARM, they are #define, not actual functions.
> > 	The attached patch fix that problem by including <asm/io.h>,
> > and the driver works fine. Obviously, you may want to do that
> > differently. The funny thing is that hostap_cs.c include that file,
> > while none of the other do...
> 
> Thanks!
> 
> Hmm.. I think it'll be simpler to just include asm/io.h to all
> hostap_{cs,plx,pci} modules whether it is really needed or not. There
> should not be any need to limit this to 2.6.x either.

	That's what I though ;-) Thanks !

> I would assume hostap_cs.c ended up including this file either because I
> needed it at some point for one of my target platforms that do not have
> PCI bus.. Alternatively, it may have something to do with external
> pcmcia-cs compilation.
> 
> > 	Note that this is for compilation in-kernel. I did not manage
> > to cross-compile out of kernel, it mixes ARM and i386 at ELF time, and
> > I'm stumped. As in-kernel works...
> 
> I'm assuming you mean using kernel Makefile or not with
> in/out-of-kernel.. I believe I have cross-compiled it
> out-of-tree many times.

	For 2.4.X, it works fine. Bah.

> However, nowadays I use kernel Makefiles for all
> builds, so I wouldn't be too surprised if the Host AP makefile would not
> handle something properly. If you meant linked-in-kernel without using
> modules, then you can of course ignore this part ;-).

	Ok ;-)

> Jouni Malinen                                            PGP id EFC895FA

	Jean



From oivindg  Tue Nov 30 11:55:57 2004
From: oivindg (=?ISO-8859-1?Q?=D8ivind_Gylver?=)
Date: Tue, 30 Nov 2004 20:55:57 +0100
Subject: Authentication with 00:00:00:00:00:00 timed out.
Message-ID: <ac81ed35041130115537885f62@mail.gmail.com>

Hello,
I have a problem connecting to a wlan (uio) with ipw2200-0.15 driver
(ipw firmware 2.0) and and wpa_supplicant 0.2.5 using PEAP without
WPA. I can choose from several APs, but none will respond to my
association request - they all time out, and loop. In short, the
following snippet is what happens and loops for eternity:

   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Authentication with 00:00:00:00:00:00 timed out.

My Linux kernel is 2.6.9-1.3_FC2.

Below is a listing of my configuration file, interfaces and log.

For the record, running my Windows partition on the same hardware will
connect to these access points just fine. Also, using wpa_supplicant
to connect to my home network (using WEP+PSK) is working excellent.

I hope someone can help me, I'm really stuck.

Thanks,
Oivind



Configuration file
------------------

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
eapol_version=1
 
network={
        ssid="uio"
        scan_ssid=0

#       bssid=00:02:8a:21:19:08
#       bssid=00:02:8a:0e:34:73
#       bssid=00:0e:83:19:2c:f0
#       bssid=00:11:21:6c:6b:20
#       bssid=00:0e:38:c3:1b:70
#       bssid=00:0e:83:19:2a:60
        bssid=00:11:21:66:92:70
 
        key_mgmt=IEEE8021X NONE
        eap=PEAP
        identity="oivindg"
        ca_cert="/etc/Thawte.pem"
        password="ssshhhhh"
        priority=1
}
 
-----------------------------------------------------------------------------

[root at localhost root]# iwconfig
lo        no wireless extensions.
 
eth0      unassociated  ESSID:"uio"  Nickname:"localhost.localdomain"
          Mode:Managed  Channel:0  Access Point: 00:11:21:66:92:70
          Bit Rate=0kb/s   Tx-Power=20 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:140   Missed beacon:0
 
eth1      no wireless extensions.
 
sit0      no wireless extensions.
 
cipsec0   no wireless extensions.

-----------------------------------------------------------------------------

[root at localhost root]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0E:35:5F:47:23
          inet6 addr: fe80::20e:35ff:fe5f:4723/64 Scope:Link
          UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:140 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0xc000 Memory:d0202000-d0202fff

-----------------------------------------------------------------------------

[root at localhost root]# wpa_supplicant -d -Dwext -c/etc/wpa.conf -i eth0
Configuration file '/etc/wpa.conf' -> '/etc/wpa.conf'
Reading configuration file '/etc/wpa.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=1
eapol_version=1
Priority group 1
   id=0 ssid='uio'
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_wext_set_wpa: enabled=1 - not yet implemented
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures: enabled=0 - not yet implemented
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 799 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:02:8a:21:19:08 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:0e:83:19:2c:f0 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:11:21:66:92:70 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
3: 00:02:8a:0e:34:73 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Cancelling scan request
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
wpa_driver_wext_associate - not yet implemented
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 999 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 1
0: 00:02:8a:21:19:08 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:11:21:6c:6b:20 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:0e:83:19:2c:f0 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
3: 00:11:21:66:92:70 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
4: 00:02:8a:0e:34:73 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Cancelling scan request
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
wpa_driver_wext_associate - not yet implemented
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 800 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:02:8a:21:19:08 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:0e:83:19:2c:f0 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:11:21:66:92:70 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
3: 00:02:8a:0e:34:73 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Cancelling scan request
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
wpa_driver_wext_associate - not yet implemented
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 799 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:02:8a:21:19:08 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:0e:83:19:2c:f0 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:11:21:66:92:70 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
3: 00:02:8a:0e:34:73 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Cancelling scan request
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
wpa_driver_wext_associate - not yet implemented
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Authentication with 00:00:00:00:00:00 timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 800 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 1
0: 00:02:8a:21:19:08 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
1: 00:0e:83:19:2c:f0 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
2: 00:11:21:66:92:70 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
3: 00:02:8a:0e:34:73 ssid='uio' wpa_ie_len=0 rsn_ie_len=0
   skip - no WPA/RSN IE
   selected non-WPA AP 00:11:21:66:92:70 ssid='uio'
Trying to associate with 00:11:21:66:92:70 (SSID='uio' freq=0 MHz)
Cancelling scan request
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
wpa_driver_wext_associate - not yet implemented
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Signal 2 received - terminating
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa: enabled=0 - not yet implemented
wpa_driver_wext_set_drop_unencrypted: enabled=0 - not yet implemented
wpa_driver_wext_set_countermeasures: enabled=0 - not yet implemented



From espy  Tue Nov 30 16:52:27 2004
From: espy (Tony Espy)
Date: Tue, 30 Nov 2004 19:52:27 -0500
Subject: Linksys WRT54G not sending WPA/RSN IEs?
Message-ID: <41AD15CB.9080601@pepper.com>


I'm having problems getting WPA-PSK to work between a Linksys WRT54G AP 
(fw ver=v2.04.4 ) and a Linux tablet running hostap (v0.25) & 
wpa_supplicant (v0.25).  I'm running a 2.4.20 kernel with the Wireless 
Extensions v15 patch + wireless_tools v27.

When I run wpa_supplicant in the foreground w/the debug switch, the scan 
results for the WRT54G always come back with a wpa_ie_len of 0, so the 
AP is skipped.

Has anyone else had problems with a WRT54G not sending WPA/RSN IEs?

Note -- I've made sure that "wireless SSID broadcast" is set to "enabled".

thanks,
Tony Espy
Pepper Computer, Inc.




