From gentoopower  Wed Mar  1 01:01:31 2006
From: gentoopower (Gentoopower)
Date: Wed, 01 Mar 2006 10:01:31 +0100
Subject: network speed with wpa_supplicant
In-Reply-To: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
References: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
Message-ID: <440562EB.3020208@yahoo.de>

Dan Werner wrote:
> I was wondering, what sort of speed should one expect using
> wpa_supplicant and WPA-PSK?  I have a Toshiba laptop with an
> integrated intel pro/wireless 2200BG adapter.  I installed the ipw2200
> driver but couldn't quite get it working with wpa_supplicant.  I was
> getting a bunch of ioctl errors and started using the 'wext' driver,
> per instructions found via google, and that seems to be working fine.
>
> I usually benchmark my network speeds by starting a download of the
> newest fedora linux iso from one of the mirrors, in this case Duke
> University.  From another wireless pc running Windows 2000, the
> transfer rate levels off at around 77 KB per second (i hate my isp). 
> The wpa_supplicant laptop only gets about 27 KB per second or so (I
> cancelled the other download before starting this test).
27 KB can only mean, you are either far away, so your card only operates
at 1MBit and you have lots of transmission failures, or you just don't
have a bad download speed for this download.
Are all downloads that slow?
>
> So is it possible that I've configured something wrong, or is there
> some current speed limitation with the driver?
I doubt, that it is a problem of the driver or a bad configuration.
>
> Thanks for any help...
> ------------------------------------------------------------------------
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>   



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de



From kelrin  Wed Mar  1 03:40:36 2006
From: kelrin (Kel Modderman)
Date: Wed, 01 Mar 2006 21:40:36 +1000
Subject: wpa_cli quirks?
Message-ID: <44058834.5030904@tpg.com.au>

Hi,

I'd like to query the handling of wpa_cli commands executed as 
arguments, rather than  from within the wpa_cli console. Are they 
handled differently as in the following example?


root at KELSLAP:/home/kel# wpa_cli -i eth1 set_network 1 ssid "kelnet"
FAIL
root at KELSLAP:/home/kel# wpa_cli -i eth1
wpa_cli v0.5.1
Copyright (c) 2004-2006, Jouni Malinen <jkmaline at cc.hut.fi> and contributors

This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.

Alternatively, this software may be distributed under the terms of the
BSD license. See README and COPYING for more details.


Interactive mode

 > set_network 1 ssid "kelnet"
OK
 >

I would have expected the same result from both scenarios.


Also, are the valid values of ap_scan only 0,1 & 2?

 > ap_scan 0
OK
 > ap_scan 1
OK
 > ap_scan 2
OK
 > ap_scan 3
FAIL
 > ap_scan foo
OK

Shouldn't it reject the garbage value of "foo"?

Thanks, Kel.



From danman.danman  Wed Mar  1 05:23:21 2006
From: danman.danman (Dan Werner)
Date: Wed, 1 Mar 2006 08:23:21 -0500
Subject: network speed with wpa_supplicant
In-Reply-To: <440562EB.3020208@yahoo.de>
References: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
	<440562EB.3020208@yahoo.de>
Message-ID: <4270e9ff0603010523k28a43a21jd40bdbdfc46d3106@mail.gmail.com>

Well, I did another test that surprised me a little.  I tried to download
one of the twit.tv podcasts.  Those come from AOL Radio, which always has a
lot of bandwidth.  My Win2k pc got like 120 KB per second, and the laptop
did better but still only topped out at 69 KB per second.  These tests were
again one right after the other.

My laptop is right next to my Win2k pc, so it ought to be similar in terms
of connecting to my router.

I guess if my connection is capable of 69 KB a second, I can live with that,
but it's surprising to me that it would be different at all.


On 3/1/06, Gentoopower <gentoopower at yahoo.de> wrote:
>
> Dan Werner wrote:
> > I was wondering, what sort of speed should one expect using
> > wpa_supplicant and WPA-PSK?  I have a Toshiba laptop with an
> > integrated intel pro/wireless 2200BG adapter.  I installed the ipw2200
> > driver but couldn't quite get it working with wpa_supplicant.  I was
> > getting a bunch of ioctl errors and started using the 'wext' driver,
> > per instructions found via google, and that seems to be working fine.
> >
> > I usually benchmark my network speeds by starting a download of the
> > newest fedora linux iso from one of the mirrors, in this case Duke
> > University.  From another wireless pc running Windows 2000, the
> > transfer rate levels off at around 77 KB per second (i hate my isp).
> > The wpa_supplicant laptop only gets about 27 KB per second or so (I
> > cancelled the other download before starting this test).
> 27 KB can only mean, you are either far away, so your card only operates
> at 1MBit and you have lots of transmission failures, or you just don't
> have a bad download speed for this download.
> Are all downloads that slow?
> >
> > So is it possible that I've configured something wrong, or is there
> > some current speed limitation with the driver?
> I doubt, that it is a problem of the driver or a bad configuration.
> >
> > Thanks for any help...
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
>
>
>
>
>
>
>
> ___________________________________________________________
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060301/177cf321/attachment.htm 


From gentoopower  Wed Mar  1 08:02:30 2006
From: gentoopower (Gentoopower)
Date: Wed, 01 Mar 2006 17:02:30 +0100
Subject: network speed with wpa_supplicant
In-Reply-To: <4270e9ff0603010523k28a43a21jd40bdbdfc46d3106@mail.gmail.com>
References: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>	
	<440562EB.3020208@yahoo.de>
	<4270e9ff0603010523k28a43a21jd40bdbdfc46d3106@mail.gmail.com>
Message-ID: <4405C596.2020701@yahoo.de>

Dan Werner wrote:
> Well, I did another test that surprised me a little.  I tried to
> download one of the twit.tv <http://twit.tv> podcasts.  Those come
> from AOL Radio, which always has a lot of bandwidth.  My Win2k pc got
> like 120 KB per second, and the laptop did better but still only
> topped out at 69 KB per second.  These tests were again one right
> after the other. 
Then there must be something wrong
>
> My laptop is right next to my Win2k pc, so it ought to be similar in
> terms of connecting to my router.
>
> I guess if my connection is capable of 69 KB a second, I can live with
> that, but it's surprising to me that it would be different at all. 
Should not be the case if transfers are just around 100KB/s. A wireless
connection lets say 11MBit link can easily take 300KB/s.
What connection speed does the laptop report? 1 Mbit or higher? Since
you say you are next to the router you should have at least a 11MBit
connection
>
>
> On 3/1/06, *Gentoopower* <gentoopower at yahoo.de
> <mailto:gentoopower at yahoo.de>> wrote:
>
>     Dan Werner wrote:
>     > I was wondering, what sort of speed should one expect using
>     > wpa_supplicant and WPA-PSK?  I have a Toshiba laptop with an
>     > integrated intel pro/wireless 2200BG adapter.  I installed the
>     ipw2200
>     > driver but couldn't quite get it working with wpa_supplicant.  I was
>     > getting a bunch of ioctl errors and started using the 'wext' driver,
>     > per instructions found via google, and that seems to be working
>     fine.
>     >
>     > I usually benchmark my network speeds by starting a download of the
>     > newest fedora linux iso from one of the mirrors, in this case Duke
>     > University.  From another wireless pc running Windows 2000, the
>     > transfer rate levels off at around 77 KB per second (i hate my isp).
>     > The wpa_supplicant laptop only gets about 27 KB per second or so (I
>     > cancelled the other download before starting this test).
>     27 KB can only mean, you are either far away, so your card only
>     operates
>     at 1MBit and you have lots of transmission failures, or you just don't
>     have a bad download speed for this download.
>     Are all downloads that slow?
>     >
>     > So is it possible that I've configured something wrong, or is there
>     > some current speed limitation with the driver?
>     I doubt, that it is a problem of the driver or a bad configuration.
>     >
>     > Thanks for any help...
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > HostAP mailing list
>     > HostAP at shmoo.com <mailto:HostAP at shmoo.com>
>     > http://lists.shmoo.com/mailman/listinfo/hostap
>     >
>
>
>
>
>
>
>
>     ___________________________________________________________
>     Telefonate ohne weitere Kosten vom PC zum PC:
>     http://messenger.yahoo.de
>
>



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de



From jkmaline  Wed Mar  1 08:04:54 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 1 Mar 2006 08:04:54 -0800
Subject: network speed with wpa_supplicant
In-Reply-To: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
References: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
Message-ID: <20060301160453.GA9400@jm.kir.nu>

On Wed, Mar 01, 2006 at 12:10:16AM -0500, Dan Werner wrote:

> I was wondering, what sort of speed should one expect using wpa_supplicant
> and WPA-PSK?

wpa_supplicant has nothing to do with transmitting data packets it is
taking care of authentication and key configuration, but after that, all
depends on the driver. With a proper driver and hardware design that
includes hardware acceleration for TKIP/CCMP (or with fast enough host
CPU), there should not be any noticeable difference in speed when
comparing plaintext connection with WPA enabled connections.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bitbuck3t+hostap  Wed Mar  1 12:05:10 2006
From: bitbuck3t+hostap (bitbuck3t+hostap at gmail.com)
Date: Wed, 1 Mar 2006 15:05:10 -0500
Subject: Intersil Prism2/2.5 card crashing with hostap driver
Message-ID: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>

I'm not quite sure where my problem lies, so I'll try to explain as much as
I can.  I have a Senao 2511CD Plus EXT2 card, which is an Intersil
Prism 2.5card.  I am running Zenwalk
2.2 (slackware based distro) with a 2.6.15.4 kernel.  When I plug the card
into my system, the orinoco and hostap drivers load, but the card binds to
the orinoco driver.  I have commented out the modalias reference in
modules.pcimap for the orinoco.  When I plug the card in now, the hostap
drivers attempt to load, however, things start going very wrong at this
point.  I am attaching the dmesg output when I plug in the card with the
hostap drivers and also when I attempt to eject the card.  Once I eject the
card, I get a traceback and I can no longer plug anything into my pcmcia
slot without rebooting.  I have been searching for about a week and have
tried finding information to fix this, however, I have had no luck.  Any
help would be greatly appreciated.  This problem has entered an area of
linux that I am just not familiar with.  I have been reading up on udev and
how that works in case it is doing something screwy, but I am still no
closer to fixing the problem.  Thanks again for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060301/8b26170c/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: new_output.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060301/8b26170c/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostap_eject.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060301/8b26170c/attachment-0001.txt 


From jfb  Wed Mar  1 12:42:30 2006
From: jfb (Juan Felipe Botero)
Date: Wed, 1 Mar 2006 15:42:30 -0500
Subject: Fw: RE: A important question
In-Reply-To: <BAY105-F344BF744A676562DA39673F7F40@phx.gbl>
References: <20060228201042.M16192@microe.udea.edu.co>
	<BAY105-F344BF744A676562DA39673F7F40@phx.gbl>
Message-ID: <20060301203815.M55057@microe.udea.edu.co>

i was looking and i found that my card is a Intersil card, is true that the majority of
mercury cards have the atheros chipser, but this one is a card with intersil chipset,
the problem that i found is that when i'm going to execute modprobe th result is:
modules.dep could not parse this.

I need to know why the card doesn't work very well

aany body have idea??







---------- Forwarded Message -----------
From: "Brian Sturgill" <zen_hacker at hotmail.com>
To: jfb at microe.udea.edu.co
Sent: Wed, 01 Mar 2006 01:19:27 +0000
Subject: RE: A important question

Did you run depmod? If not you need to let the kernel know there are new 
modules there by running depmod -a . You shlould be able to load the module 
by modprobe manually then. I have never tried using the CF cards. If I do 
remember correctly, the mercury cards are not prism. I think they are 
atheros and use madwifi drivers. Hope this helps.

Brian

>From: "Juan Felipe Botero" <jfb at microe.udea.edu.co>
>To: hostap at shmoo.com
>Subject: A important question
>Date: Tue, 28 Feb 2006 15:13:43 -0500
>
>
>
>HI, i really need some help:
>
>I could compile the hostap driver with the path of the linux kernel of my 
>embedded
>system for a IMXL card based in a arm architecture.
>
>when i compiled the kernel a folder called:
>/lib/modules/2.6.11.4-csb/kernel/drivers/net/wireless was created in my 
>normal Linux
>system file, so i created and copied this folder in the linux file system 
>of the
>embedded architecture, but when i started the Linux again, the driver 
>didn't work. i
>put in the command line - ifconfig wlan0 up - and the answer was - no such 
>device -. I
>think this could be because how the embedded system doesn't have pcmcia 
>support, the
>folder /etc/pcmcia doesn't exist so the file: /etc/pcmcia/hostap_cs.conf 
>doesn't
>exist, i dont know if is necessary that file exists?, i need help if i have 
>done
>something wrong since the driver compilation.
>
>The compact flash card is a sinao NL-2511CF mercury.
>Please help me
>
>lot of thanks
>
>--
>Open WebMail Project (http://openwebmail.org)
>------- End of Forwarded Message -------
>
>
>--
>Open WebMail Project (http://openwebmail.org)
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
------- End of Forwarded Message -------


--
Open WebMail Project (http://openwebmail.org)




From jim  Wed Mar  1 13:02:56 2006
From: jim (Jim Thompson)
Date: Wed, 01 Mar 2006 11:02:56 -1000
Subject: Intersil Prism2/2.5 card crashing with hostap driver
In-Reply-To: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>
References: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>
Message-ID: <44060C00.7060709@netgate.com>

bitbuck3t+hostap at gmail.com wrote:

> I'm not quite sure where my problem lies, so I'll try to explain as
> much as I can.  I have a Senao 2511CD Plus EXT2 card, which is an
> Intersil Prism 2.5 card.  I am running Zenwalk 2.2 (slackware based
> distro) with a 2.6.15.4 <http://2.6.15.4/> kernel.  When I plug the
> card into my system, the orinoco and hostap drivers load, but the card
> binds to the orinoco driver.  I have commented out the modalias
> reference in modules.pcimap for the orinoco.  When I plug the card in
> now, the hostap drivers attempt to load, however, things start going
> very wrong at this point.  I am attaching the dmesg output when I plug
> in the card with the hostap drivers and also when I attempt to eject
> the card.  Once I eject the card, I get a traceback and I can no
> longer plug anything into my pcmcia slot without rebooting.  I have
> been searching for about a week and have tried finding information to
> fix this, however, I have had no luck.  Any help would be greatly
> appreciated.  This problem has entered an area of linux that I am just
> not familiar with.  I have been reading up on udev and how that works
> in case it is doing something screwy, but I am still no closer to
> fixing the problem.  Thanks again for any help.

Your problem started here:

prism2_hw_init: initialized in 199 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.0
wifi0: STA: id=0x1f v1.4.9
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: Command completion event, but no pending commands
hostap_cs: assuming no Primary image in flash - card initialization not completed
wifi0: test Genesis mode with HCR 0x1f

for whatever reason, the firmware on your card is either very slow to
respond, or fails to respond at all.

Is the orinoco driver still loaded?

Did the card work with the orinoco driver (in BSS or IBSS mode)?

Jim



From jar  Wed Mar  1 13:08:51 2006
From: jar (Jar)
Date: Wed, 01 Mar 2006 23:08:51 +0200
Subject: Intersil Prism2/2.5 card crashing with hostap driver
In-Reply-To: <44060C00.7060709@netgate.com>
References: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>
	<44060C00.7060709@netgate.com>
Message-ID: <44060D63.3080702@pcuf.fi>

Jim Thompson wrote:

> Your problem started here:
> 
> prism2_hw_init: initialized in 199 ms
> wifi0: NIC: id=0x800c v1.0.0
> wifi0: PRI: id=0x15 v1.1.0
> wifi0: STA: id=0x1f v1.4.9
> wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
> wifi0: Command completion event, but no pending commands
> hostap_cs: assuming no Primary image in flash - card initialization not completed
> wifi0: test Genesis mode with HCR 0x1f

It can be a pcmcia problem as well. If the problem still exists after 
firmaware update (e.g. 1.0.0-->1.1.1 and 1.4.9-->1.7.4) then most 
probably it is some sort of pcmcia problem. I don't think it would be 
hostap_cs related.

-- 
Best Regards, Jar



From jim  Wed Mar  1 13:21:22 2006
From: jim (Jim Thompson)
Date: Wed, 01 Mar 2006 11:21:22 -1000
Subject: Intersil Prism2/2.5 card crashing with hostap driver
In-Reply-To: <44060D63.3080702@pcuf.fi>
References: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>	<44060C00.7060709@netgate.com>
	<44060D63.3080702@pcuf.fi>
Message-ID: <44061052.9060202@netgate.com>

Jar wrote:

>Jim Thompson wrote:
>
>  
>
>>Your problem started here:
>>
>>prism2_hw_init: initialized in 199 ms
>>wifi0: NIC: id=0x800c v1.0.0
>>wifi0: PRI: id=0x15 v1.1.0
>>wifi0: STA: id=0x1f v1.4.9
>>wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
>>wifi0: Command completion event, but no pending commands
>>hostap_cs: assuming no Primary image in flash - card initialization not completed
>>wifi0: test Genesis mode with HCR 0x1f
>>    
>>
>
>It can be a pcmcia problem as well. If the problem still exists after 
>firmaware update (e.g. 1.0.0-->1.1.1 and 1.4.9-->1.7.4) then most 
>probably it is some sort of pcmcia problem. I don't think it would be 
>hostap_cs related.
>  
>
The 1.4.9 firmware works fine, no reason to update it.   I'd have to
check closely, but I believe that 1.1.0 is the correct PRI for the 1.4.9
STA f/w.

Now, it *could* be pcmcia problems, which is why I asked if the card
functioned correctly with the orinoco driver loaded.

Jim




From bitbuck3t+hostap  Wed Mar  1 13:58:12 2006
From: bitbuck3t+hostap (bitbuck3t+hostap at gmail.com)
Date: Wed, 1 Mar 2006 16:58:12 -0500
Subject: Intersil Prism2/2.5 card crashing with hostap driver
In-Reply-To: <44060C00.7060709@netgate.com>
References: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>
	<44060C00.7060709@netgate.com>
Message-ID: <15ea91da0603011358y619c829dqcf52e1eb03274182@mail.gmail.com>

This output was without the orinoco driver loading.  I can include the
output with the orinoco driver if needed.  When the orinoco driver loads,
everything works fine with the card.  The system also loads the hostap
drivers when Orinoco is loaded, but they don't seem to bind to the card at
all.

On 3/1/06, Jim Thompson <jim at netgate.com> wrote:
>
> bitbuck3t+hostap at gmail.com wrote:
>
> > I'm not quite sure where my problem lies, so I'll try to explain as
> > much as I can.  I have a Senao 2511CD Plus EXT2 card, which is an
> > Intersil Prism 2.5 card.  I am running Zenwalk 2.2 (slackware based
> > distro) with a 2.6.15.4 <http://2.6.15.4/> kernel.  When I plug the
> > card into my system, the orinoco and hostap drivers load, but the card
> > binds to the orinoco driver.  I have commented out the modalias
> > reference in modules.pcimap for the orinoco.  When I plug the card in
> > now, the hostap drivers attempt to load, however, things start going
> > very wrong at this point.  I am attaching the dmesg output when I plug
> > in the card with the hostap drivers and also when I attempt to eject
> > the card.  Once I eject the card, I get a traceback and I can no
> > longer plug anything into my pcmcia slot without rebooting.  I have
> > been searching for about a week and have tried finding information to
> > fix this, however, I have had no luck.  Any help would be greatly
> > appreciated.  This problem has entered an area of linux that I am just
> > not familiar with.  I have been reading up on udev and how that works
> > in case it is doing something screwy, but I am still no closer to
> > fixing the problem.  Thanks again for any help.
>
> Your problem started here:
>
> prism2_hw_init: initialized in 199 ms
> wifi0: NIC: id=0x800c v1.0.0
> wifi0: PRI: id=0x15 v1.1.0
> wifi0: STA: id=0x1f v1.4.9
> wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in
> Host AP mode WDS
> wifi0: Command completion event, but no pending commands
> hostap_cs: assuming no Primary image in flash - card initialization not
> completed
> wifi0: test Genesis mode with HCR 0x1f
>
> for whatever reason, the firmware on your card is either very slow to
> respond, or fails to respond at all.
>
> Is the orinoco driver still loaded?
>
> Did the card work with the orinoco driver (in BSS or IBSS mode)?
>
> Jim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060301/004fc26f/attachment.htm 


From jim  Wed Mar  1 15:16:00 2006
From: jim (Jim Thompson)
Date: Wed, 01 Mar 2006 13:16:00 -1000
Subject: Intersil Prism2/2.5 card crashing with hostap driver
In-Reply-To: <15ea91da0603011358y619c829dqcf52e1eb03274182@mail.gmail.com>
References: <15ea91da0603011205p4b0cb6d6s70dfefffe5a49e23@mail.gmail.com>	
	<44060C00.7060709@netgate.com>
	<15ea91da0603011358y619c829dqcf52e1eb03274182@mail.gmail.com>
Message-ID: <44062B30.9010304@netgate.com>

bitbuck3t+hostap at gmail.com wrote:

> This output was without the orinoco driver loading.  I can include the
> output with the orinoco driver if needed.  When the orinoco driver
> loads, everything works fine with the card.  

The fact that the card works "fine" with the orinoco driver strongly
suggests that your card is fine, and you've got some issue either with
the hostap driver as 'shipped' by your distro, or in your compilation
environment, or have some "conflict" that is tying up a resource needed
by the card, such that it is unable to respond to the hostap driver (or
respond in a timely manner.)

> The system also loads the hostap drivers when Orinoco is loaded, but
> they don't seem to bind to the card at all.

this is the expected behavior.

jim

> On 3/1/06, *Jim Thompson* <jim at netgate.com <mailto:jim at netgate.com>>
> wrote:
>
>     bitbuck3t+hostap at gmail.com <mailto:bitbuck3t+hostap at gmail.com> wrote:
>
>     > I'm not quite sure where my problem lies, so I'll try to explain as
>     > much as I can.  I have a Senao 2511CD Plus EXT2 card, which is an
>     > Intersil Prism 2.5 card.  I am running Zenwalk 2.2 (slackware based
>     > distro) with a 2.6.15.4 <http://2.6.15.4> <http://2.6.15.4/>
>     kernel.  When I plug the
>     > card into my system, the orinoco and hostap drivers load, but
>     the card
>     > binds to the orinoco driver.  I have commented out the modalias
>     > reference in modules.pcimap for the orinoco.  When I plug the
>     card in
>     > now, the hostap drivers attempt to load, however, things start going
>     > very wrong at this point.  I am attaching the dmesg output when
>     I plug
>     > in the card with the hostap drivers and also when I attempt to
>     eject
>     > the card.  Once I eject the card, I get a traceback and I can no
>     > longer plug anything into my pcmcia slot without rebooting.  I have
>     > been searching for about a week and have tried finding
>     information to
>     > fix this, however, I have had no luck.  Any help would be greatly
>     > appreciated.  This problem has entered an area of linux that I
>     am just
>     > not familiar with.  I have been reading up on udev and how that
>     works
>     > in case it is doing something screwy, but I am still no closer to
>     > fixing the problem.  Thanks again for any help.
>
>     Your problem started here:
>
>     prism2_hw_init: initialized in 199 ms
>     wifi0: NIC: id=0x800c v1.0.0
>     wifi0: PRI: id=0x15 v1.1.0
>     wifi0: STA: id=0x1f v1.4.9
>     wifi0: defaulting to bogus WDS frame as a workaround for firmware
>     bug in Host AP mode WDS
>     wifi0: Command completion event, but no pending commands
>     hostap_cs: assuming no Primary image in flash - card
>     initialization not completed
>     wifi0: test Genesis mode with HCR 0x1f
>
>     for whatever reason, the firmware on your card is either very slow to
>     respond, or fails to respond at all.
>
>     Is the orinoco driver still loaded?
>
>     Did the card work with the orinoco driver (in BSS or IBSS mode)?
>
>     Jim
>
>




From ronaldo  Wed Mar  1 15:46:59 2006
From: ronaldo (Ronaldo Vasconcellos)
Date: Wed, 1 Mar 2006 20:46:59 -0300 (BRT)
Subject: network speed with wpa_supplicant
In-Reply-To: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
References: <4270e9ff0602282110j12a98cadl3acca7a9f9663c3b@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0603012040340.19993@exocet.cais.rnp.br>

Depending on your router you could try and install iperf between the 
client and the AP. This way you could better assess the bandwidth. Just a 
suggestion :)

 Iperf Version 2.0.2 
 http://dast.nlanr.net/Projects/Iperf/

Ronaldo

On Wed, 1 Mar 2006, Dan Werner wrote:

> Date: Wed, 1 Mar 2006 00:10:16 -0500
> From: Dan Werner <danman.danman at gmail.com>
> To: hostap at shmoo.com
> Subject: network speed with wpa_supplicant
> 
> I was wondering, what sort of speed should one expect using wpa_supplicant
> and WPA-PSK?  I have a Toshiba laptop with an integrated intel pro/wireless
> 2200BG adapter.  I installed the ipw2200 driver but couldn't quite get it
> working with wpa_supplicant.  I was getting a bunch of ioctl errors and
> started using the 'wext' driver, per instructions found via google, and that
> seems to be working fine.
> 
> I usually benchmark my network speeds by starting a download of the newest
> fedora linux iso from one of the mirrors, in this case Duke University.
> >From another wireless pc running Windows 2000, the transfer rate levels off
> at around 77 KB per second (i hate my isp).  The wpa_supplicant laptop only
> gets about 27 KB per second or so (I cancelled the other download before
> starting this test).
> 
> So is it possible that I've configured something wrong, or is there some
> current speed limitation with the driver?



From pelusitavali  Wed Mar  1 16:03:46 2006
From: pelusitavali (pelusa vali)
Date: Thu, 02 Mar 2006 00:03:46 +0000
Subject: problems authenticating using madwifi, hostapd and freeradius
Message-ID: <BAY23-F7F92998A746B7A93C2D9DDEF50@phx.gbl>

hi everybody, well this is a quite large mail: i'm using debian sarge kernel 
2.6.13, openssl 0.9.8a, hostapd 0.5.1, freeradius 1.0.5, madwifi-ng-r1406, i 
want to use eap-tls in my wlan and over my own ap over linux. so i can 
install and configure all programs (except hostapd, so instead compile 
myself i installed it from .deb format), now i have my certificates and 
programs running but when try to connect a windows client it always stops in 
this state:"Trying to authenticate", and any more happen. i generate 
certificates using winxp extensions.

here is my madwifi configuration:

modprobe ath_pci
wlanconfig ath0 create wlandev wifi0 wlanmode ap
ifconfig ath0 up
/etc/init.d/networking restart
IPTABLES=/sbin/iptables
$IPTABLES -F -t nat
$IPTABLES -A POSTROUTING -t nat -o eth0 -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
/etc/init.d/dhcp restart
iwpriv ath0 mode 3
iwconfig ath0 essid MYWLAN
iwconfig ath0 channel 5
iwconfig ath0 bitrate 54M
iwconfig ath0 frag 512
iwconfig ath0 rts 250

and this is my hostapd.conf file:

interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=3
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=MYWLAN
macaddr_acl=0
auth_algs=3
ieee8021x=1
eap_message=hello_clients
eapol_key_index_workaround=0
eap_reauth_period=3600
eap_server=0
auth_server_addr=192.168.50.1
auth_server_port=1812
auth_server_shared_secret=pupis
acct_server_addr=192.168.50.1
acct_server_port=1813
acct_server_shared_secret=pupis
wpa=1
wpa_key_mgmt=WPA-EAP
wpa_pairwise=TKIP
wpa_group_rekey=600
rsn_preauth=1

this is clients.conf in radius:

client 192.168.50.0/24 {
	secret = pupis
	shortname	= www.mymachine.com
}

users file:

"Administrador"	Auth-Type := EAP

eap.conf file:

tls {
			private_key_file = /root/miscerts/servidor.pem
			certificate_file = /root/miscerts/servidor.pem
			CA_file = /root/miscerts/cacert.pem
			dh_file = /root/miscerts/dh
			random_file = /root/miscerts/random
			fragment_size = 1024
			include_length = yes
			check_crl = yes
                        check_cert_cn = %{User-Name}
		}

and this is radiusd.conf file:

user = nobody
group = nobody
bind_address = *
port = 0



here you have an extract from freeradius messages:

Sending Access-Challenge of id 45 to 192.168.50.1:32770
        EAP-Message = 0x010c032f0d8000000325160301004a020000 
4603014405e74b513e9996de87211edb20c47f40dd002af273747f4f3744 
dc22b2a929204cc9d701379ab60764bf9571959b7cf99bf0a051b8079df5 
5ff610793318fc25000400160301025c0b0002580002550002523082024e 
308201b7a003020102020428022006300d06092a864886f70d0101050500 
305f310b3009060355040613024543311330110603550408130a4368696d 
626f72617a6f3111300f0603550407130852696f62616d6261310f300d06 
0355040a13064553504f4348311730150603550403130e7777772e61706d 
6167612e636f6d301e170d3036303232373135303735335a17
        EAP-Message = 0x0d3037303232373135303735335a305f310b 
3009060355040613024543311330110603550408130a4368696d626f7261 
7a6f3111300f0603550407130852696f62616d6261310f300d060355040a 
13064553504f4348311730150603550403130e7777772e61706d6167612e 
636f6d30819f300d06092a864886f70d010101050003818d003081890281 
8100b94ddf014e77cbcc5b23133a98b77090353f7b9fba6db33b2cd1510e 
8f8c8f533bcec923900dad61e3a0c02e04700c9c95856bdf7d559147a4af 
c8cb5c38d410178d9552d322aedcce46483f7dd761e7583b1e6d075cd107 
27c0941416b9accb097baaec90b46c04aef567ffd08c4acff6
        EAP-Message = 0x88252d81a766ce4e63d9a21c774d97020301 
0001a317301530130603551d25040c300a06082b06010505070301300d06 
092a864886f70d0101050500038181007f41e4ef50c1c77d450dee7b0b43 
72c3cb68163fec851512100ac72fc77d70a83fe87d93d1447842eb919bac 
6a0ad112b687550ad520f50e4651cfde1246343e6f458a1501de2e4018db 
fbb5658b9da522e6283e3d0ab083e8e344befc0628d3ec0245dc672333ac 
e70c8d44d0f1cfce9571c74a4ead43597c4567322e09954e16030100700d 
00006802010200630061305f310b30090603550406130245433113301106 
03550408130a4368696d626f72617a6f3111300f0603550407
        EAP-Message = 0x130852696f62616d6261310f300d06035504 
0a13064553504f4348311730150603550403130e7777772e61706d616761 
2e636f6d0e000000
        Message-Authenticator = 0x00000000000000000000000000 000000
        State = 0x1a0c83eb55ba1000a03c23980883a7aa
Finished request 54
Going to the next request
Waking up in 6 seconds...
rad_recv: Access-Request packet from host 192.168.50.1:32770 , id=46, 
length=176
        User-Name = "Administrador"
        NAS-IP-Address = 192.168.50.1
        NAS-Port = 0
        Called-Station-Id = "00-0F-66-11-C1-97:MYWLAN"
        Calling-Station-Id = "00-0F-66-11-C1-96"
        Framed-MTU = 1400
        NAS-Port-Type = Wireless-802.11
        Connect-Info = "CONNECT 11Mbps 802.11b"
        EAP-Message = 0x020c00060d00
        State = 0x1a0c83eb55ba1000a03c23980883a7aa
        Message-Authenticator = 0x27cc4322bbd111e4235b4675cb 9bbbc5
  Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 55
  modcall[authorize]: module "preprocess" returns ok for req uest 55
  modcall[authorize]: module "chap" returns noop for request  55
  modcall[authorize]: module "mschap" returns noop for reque st 55
    rlm_realm: No '@' in User-Name = "Administrador", lookin g up realm NULL
    rlm_realm: No such realm "NULL"
  modcall[authorize]: module "suffix" returns noop for reque st 55
  rlm_eap: EAP packet type response id 12 length 6
  rlm_eap: No EAP Start, assuming it's an on-going EAP conve rsation
  modcall[authorize]: module "eap" returns updated for reque st 55
    users: Matched entry Administrador at line 97
  modcall[authorize]: module "files" returns ok for request 55
modcall: group authorize returns updated for request 55
  rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
  Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 55
  rlm_eap: Request found, released from the list
  rlm_eap: EAP/tls
  rlm_eap: processing type tls
  rlm_eap_tls: Authenticate
  rlm_eap_tls: processing TLS
rlm_eap_tls: Received EAP-TLS ACK message
  rlm_eap_tls: ack handshake fragment handler
  eaptls_verify returned 1
  eaptls_process returned 13
  modcall[authenticate]: module "eap" returns handled for re quest 55
modcall: group authenticate returns handled for request 55
Sending Access-Challenge of id 46 to 192.168.50.1:32770
        EAP-Message = 0x010d000a0d8000000000
        Message-Authenticator = 0x00000000000000000000000000 000000
        State = 0x683f2718a7a0a8cdcb646c2b11cb50d3
Finished request 55
Going to the next request
Waking up in 6 seconds...
rad_recv: Accounting-Request packet from host 192.168.50.1:3 2771, id=47, 
length=74
        Acct-Status-Type = Accounting-Off
        Acct-Authentic = RADIUS
        NAS-IP-Address = 192.168.50.1
        Called-Station-Id = "00-0F-66-11-C1-97:MYWLAN"
        Acct-Terminate-Cause = NAS-Reboot
  Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 56
  modcall[preacct]: module "preprocess" returns noop for req uest 56
rlm_acct_unique: WARNING: Attribute NAS-Port was not found i n request, 
unique ID MAY be inconsistent
rlm_acct_unique: WARNING: Attribute Acct-Session-Id was not found in 
request, unique ID MAY be inconsistent
rlm_acct_unique: WARNING: Attribute User-Name was not found in request, 
unique ID MAY be inconsistent
rlm_acct_unique: Hashing ',Client-IP-Address = 192.168.50.1, NAS-IP-Address 
= 192.168.50.1,,'
rlm_acct_unique: Acct-Unique-Session-ID = "6ce5fd9afe1e7263" .
  modcall[preacct]: module "acct_unique" returns ok for requ est 56
    rlm_realm: Proxy reply, or no User-Name.  Ignoring.
  modcall[preacct]: module "suffix" returns noop for request  56
  modcall[preacct]: module "files" returns noop for request 56
modcall: group preacct returns ok for request 56
  Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 56
radius_xlat:  '/usr/local/var/log/radius/radacct/192.168.50. 
1/detail-20060301'
rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Ad 
dress}/detail-%Y%m%d expands to /usr/local/var/log/radius/ra 
dacct/192.168.50.1/detail-20060301
rlm_detail: Failed to create directory /usr/local/var/log/ra 
dius/radacct/192.168.50.1: Permission denied
  modcall[accounting]: module "detail" returns fail for requ est 56
modcall: group accounting returns fail for request 56
Finished request 56
Going to the next request
--- Walking the entire request list ---
Cleaning up request 53 ID 44 with timestamp 4405e74b
Cleaning up request 54 ID 45 with timestamp 4405e74b
Cleaning up request 55 ID 46 with timestamp 4405e74b
Cleaning up request 56 ID 47 with timestamp 4405e751
Nothing to do.  Sleeping until we see a request.


and here is hostapd output:

RADIUS packet matching with station 00:0f:66:11:c1:96
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: using EAP timeout of 30 seconds
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: decapsulated EAP packet (code=1 
id=12 l en=815) from RADIUS server: EAP-Request-TLS (13)
IEEE 802.1X: 00:0f:66:11:c1:96 BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:66:11:c1:96 (identifier 12)
TX EAPOL - hexdump(len=833): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 00 
03 2f 01 0c 03 2f 0d 80 00 00 03 25 16 03 01 00 4a 02 00 00 46 03 01 44 05 
e7 4b 51  3e 99 96 de 87 21 1e db 20 c4 7f 40 dd 00 2a f2 73 74 7f 4f 37 44 
dc 22 b2 a9 2 9 20 4c c9 d7 01 37 9a b6 07 64 bf 95 71 95 9b 7c f9 9b f0 a0 
51 b8 07 9d f5 5f f6 10 79 33 18 fc 25 00 04 00 16 03 01 02 5c 0b 00 02 58 
00 02 55 00 02 52 30 82  02 4e 30 82 01 b7 a0 03 02 01 02 02 04 28 02 20 06 
30 0d 06 09 2a 86 48 86 f7 0 d 01 01 05 05 00 30 5f 31 0b 30 09 06 03 55 04 
06 13 02 45 43 31 13 30 11 06 03 55 04 08 13 0a 43 68 69 6d 62 6f 72 61 7a 
6f 31 11 30 0f 06 03 55 04 07 13 08 52  69 6f 62 61 6d 62 61 31 0f 30 0d 06 
03 55 04 0a 13 06 45 53 50 4f 43 48 31 17 3 0 15 06 03 55 04 03 13 0e 77 77 
77 2e 61 70 6d 61 67 61 2e 63 6f 6d 30 1e 17 0d 30 36 30 32 32 37 31 35 30 
37 35 33 5a 17 0d 30 37 30 32 32 37 31 35 30 37 35 33  5a 30 5f 31 0b 30 09 
06 03 55 04 06 13 02 45 43 31 13 30 11 06 03 55 04 08 13 0 a 43 68 69 6d 62 
6f 72 61 7a 6f 31 11 30 0f 06 03 55 04 07 13 08 52 69 6f 62 61 6d 62 61 31 
0f 30 0d 06 03 55 04 0a 13 06 45 53 50 4f 43 48 31 17 30 15 06 03 55  04 03 
13 0e 77 77 77 2e 61 70 6d 61 67 61 2e 63 6f 6d 30 81 9f 30 0d 06 09 2a 8 6 
48 86 f7 0d 01 01 01 05 00 03 81 8d 00 30 81 89 02 81 81 00 b9 4d df 01 4e 
77 cb cc 5b 23 13 3a 98 b7 70 90 35 3f 7b 9f ba 6d b3 3b 2c d1 51 0e 8f 8c 
8f 53 3b  ce c9 23 90 0d ad 61 e3 a0 c0 2e 04 70 0c 9c 95 85 6b df 7d 55 91 
47 a4 af c8 c b 5c 38 d4 10 17 8d 95 52 d3 22 ae dc ce 46 48 3f 7d d7 61 e7 
58 3b 1e 6d 07 5c d1 07 27 c0 94 14 16 b9 ac cb 09 7b aa ec 90 b4 6c 04 ae 
f5 67 ff d0 8c 4a cf f6  88 25 2d 81 a7 66 ce 4e 63 d9 a2 1c 77 4d 97 02 03 
01 00 01 a3 17 30 15 30 13 0 6 03 55 1d 25 04 0c 30 0a 06 08 2b 06 01 05 05 
07 03 01 30 0d 06 09 2a 86 48 86 f7 0d 01 01 05 05 00 03 81 81 00 7f 41 e4 
ef 50 c1 c7 7d 45 0d ee 7b 0b 43 72 c3  cb 68 16 3f ec 85 15 12 10 0a c7 2f 
c7 7d 70 a8 3f e8 7d 93 d1 44 78 42 eb 91 9 b ac 6a 0a d1 12 b6 87 55 0a d5 
20 f5 0e 46 51 cf de 12 46 34 3e 6f 45 8a 15 01 de 2e 40 18 db fb b5 65 8b 
9d a5 22 e6 28 3e 3d 0a b0 83 e8 e3 44 be fc 06 28 d3  ec 02 45 dc 67 23 33 
ac e7 0c 8d 44 d0 f1 cf ce 95 71 c7 4a 4e ad 43 59 7c 45 6 7 32 2e 09 95 4e 
16 03 01 00 70 0d 00 00 68 02 01 02 00 63 00 61 30 5f 31 0b 30 09 06 03 55 
04 06 13 02 45 43 31 13 30 11 06 03 55 04 08 13 0a 43 68 69 6d 62 6f  72 61 
7a 6f 31 11 30 0f 06 03 55 04 07 13 08 52 69 6f 62 61 6d 62 61 31 0f 30 0 d 
06 03 55 04 0a 13 06 45 53 50 4f 43 48 31 17 30 15 06 03 55 04 03 13 0e 77 
77 77 2e 61 70 6d 61 67 61 2e 63 6f 6d 0e 00 00 00
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 10 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=0 length=6
   EAP: code=2 identifier=12 length=6 (response)
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: received EAP packet (code=2 id=12 
len=6 ) from STA: EAP Response-TLS (13)
IEEE 802.1X: 00:0f:66:11:c1:96 BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
  Copied RADIUS State Attribute
ath0: RADIUS Sending RADIUS message to authentication server
RADIUS message: code=1 (Access-Request) identifier=46 length=176
   Attribute 1 (User-Name) length=15
      Value: 'Administrador'
   Attribute 4 (NAS-IP-Address) length=6
      Value: 192.168.50.1
   Attribute 5 (NAS-Port) length=6
      Value: 0
   Attribute 30 (Called-Station-Id) length=30
      Value: '00-0F-66-11-C1-97:MYWLAN'
   Attribute 31 (Calling-Station-Id) length=19
      Value: '00-0F-66-11-C1-96'
   Attribute 12 (Framed-MTU) length=6
      Value: 1400
   Attribute 61 (NAS-Port-Type) length=6
      Value: 19
   Attribute 77 (Connect-Info) length=24
      Value: 'CONNECT 11Mbps 802.11b'
   Attribute 79 (EAP-Message) length=8
      Value: 02 0c 00 06 0d 00
   Attribute 24 (State) length=18
      Value: 1a 0c 83 eb 55 ba 10 00 a0 3c 23 98 08 83 a7 aa
   Attribute 80 (Message-Authenticator) length=18
      Value: 27 cc 43 22 bb d1 11 e4 23 5b 46 75 cb 9b bb c5
ath0: RADIUS Next RADIUS client retransmit in 3 seconds

IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
ath0: RADIUS Received 68 bytes from RADIUS server
ath0: RADIUS Received RADIUS message
RADIUS message: code=11 (Access-Challenge) identifier=46 length=68
   Attribute 79 (EAP-Message) length=12
      Value: 01 0d 00 0a 0d 80 00 00 00 00
   Attribute 80 (Message-Authenticator) length=18
      Value: 8f 71 dd a8 2c 37 db d0 4a d6 ed 2f 99 29 e3 7b
   Attribute 24 (State) length=18
      Value: 68 3f 27 18 a7 a0 a8 cd cb 64 6c 2b 11 cb 50 d3
ath0: STA 00:0f:66:11:c1:96 RADIUS: Received RADIUS packet matched with a 
pendin g request, round trip time 0.00 sec
RADIUS packet matching with station 00:0f:66:11:c1:96
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: using EAP timeout of 30 seconds
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: decapsulated EAP packet (code=1 
id=13 l en=10) from RADIUS server: EAP-Request-TLS (13)
IEEE 802.1X: 00:0f:66:11:c1:96 BE_AUTH entering state REQUEST
IEEE 802.1X: Sending EAP Packet to 00:0f:66:11:c1:96 (identifier 13)
TX EAPOL - hexdump(len=28): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 00 
00 0 a 01 0d 00 0a 0d 80 00 00 00 00
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
Signal 2 received - terminating
Removing station 00:0f:66:11:c1:96
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
ath0: RADIUS Sending RADIUS message to accounting server
RADIUS message: code=4 (Accounting-Request) identifier=47 length=74
   Attribute 40 (Acct-Status-Type) length=6
      Value: 8
   Attribute 45 (Acct-Authentic) length=6
      Value: 1
   Attribute 4 (NAS-IP-Address) length=6
      Value: 192.168.50.1
   Attribute 30 (Called-Station-Id) length=30
      Value: '00-0F-66-11-C1-97:MYWLAN'
   Attribute 49 (Acct-Terminate-Cause) length=6
      Value: 11
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0

i use ethereal so this is what it shows:

Cisco-Li_11:c1:96          TLS		Server Hello, Certificate Request, Server 
Hello
			   EAP          Response, EAP-TLS
			   TLS	        Client Hello
			   TLS		Server Hello, Certificate Request, Server Hello
			   EAP		Response, EAP-TLS

i also run 80211debug from madwifi and this is what i get:

Mar  1 13:01:18 localhost kernel: 08 01 2c 00 00 0f 66 11  c1 97 00 0f 66 11 
c1 96
Mar  1 13:01:18 localhost kernel: 00 0f 66 11 c1 97 10 da  aa aa 03 00 00 00 
08 00
Mar  1 13:01:18 localhost kernel: 45 00 00 28 3a ac 40 00  80 06 09 1c c0 a8 
32 04
Mar  1 13:01:18 localhost kernel: c1 2d 03 2e 04 3c 00 50  b6 55 47 86 ee 5b 
7c 42
Mar  1 13:01:18 localhost kernel: 50 10 44 70 47 56 00 00  1b 87 e5 89
Mar  1 13:01:18 localhost kernel:
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: R (dd40b390 1d40b390) 1d40b3c0 1083b020 
00000000 00000c60 1fc60000 51e51911 !
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: R (dd40b3c0 1d40b3c0) 1d40b3f0 1269a020 
00000000 00000c60 1fd60000 33ef1911 !
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: R (dd40b3f0 1d40b3f0) 1d40b420 1262b020 
00000000 00000c60 10a60000 340b1111 !
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: R (dd40b420 1d40b420) 1d40b450 12666020 
00000000 00000c60 10160000 36801911 !
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: R (dd40b450 1d40b450) 1d40b480 16393020 
00000000 00000c60 1fb60000 5ee41911 !
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x10000
Mar  1 13:01:18 localhost kernel: ath_beacon_setup: m d61493e0 len 124
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x4009
Mar  1 13:01:18 localhost kernel: ath_rx_tasklet
Mar  1 13:01:18 localhost kernel: R (dd40b480 1d40b480) 1d40b4b0 12627020 
00000000 00000c60 1fe60000 281d1911 !
Mar  1 13:01:18 localhost kernel: ath_intr: status 0x10000
Mar  1 13:01:18 localhost kernel: ath_beacon_setup: m d61493e0 len 124
Mar  1 13:01:18 localhost kernel: ath_tx_start: skb0 d6633a40 [data d25ce84e 
len 512] skbaddr 125ce84e
Mar  1 13:01:18 localhost kernel: FRDS 
00:0f:66:11:c1:97->00:0f:66:11:c1:96(00:0f:66:11:c1:97) data 54M
Mar  1 13:01:18 localhost kernel:
Mar  1 13:01:18 localhost kernel: 08 06 cc 00 00 0f 66 11  c1 96 00 0f 66 11 
c1 97
Mar  1 13:01:18 localhost kernel: 00 0f 66 11 c1 97 f0 29  aa aa 03 00 00 00 
08 00
Mar  1 13:01:18 localhost kernel: 45 00 05 dc 24 0f 40 00  2b 06 6f 05 c1 2d 
03 2e
Mar  1 13:01:18 localhost kernel: c0 a8 32 04 00 50 04 3c  ee 5b 7c 42 b6 55 
47 86
Mar  1 13:01:18 localhost kernel: 50 10 21 80 83 2a 00 00  84 e6 91 f7 fb 35 
9d b5
Mar  1 13:01:18 localhost kernel: 65 d1 5a df da 24 a9 19  e9 26 11 d1 e9 7e 
39 01
Mar  1 13:01:18 localhost kernel: 17 9e 38 f4 a4 84 23 ac  42 42 f3 9e 89 a1 
18 f0
Mar  1 13:01:18 localhost kernel: 25 55 19 22 63 d6 64 ee  19 bd 0f 72 a6 21 
6a b0
Mar  1 13:01:18 localhost kernel: cf cf e1 07 ba 7b ba 81  bc 62 98 88 5d 1d 
c5 ba
Mar  1 13:01:18 localhost kernel: 7b fb 65 b4 57 44 e6 e7  6b ad 59 fc 2a 60 
f7 eb
Mar  1 13:01:18 localhost kernel: 30 fe d6 d0 bb fd 39 4a  02 76 d7 de 7a d4 
03 3e
Mar  1 13:01:18 localhost kernel: 35 9c 94 0b b5 76 cb e3  4d 61 d9 d9 0f 19 
64 25
Mar  1 13:01:18 localhost kernel: 8b 61 3c 43 4c c5 84 35  58 da ca 9e 0f 52 
b6 0b
Mar  1 13:01:18 localhost kernel: 36 55 12 9c 38 e1 12 d0  7f ad 95 13 b9 87 
26 1e
Mar  1 13:01:18 localhost kernel: f8 08 55 96 9e e6 18 26  83 56 fd 1c 17 61 
5c f8
Mar  1 13:01:18 localhost kernel: 98 d8 e2 4c ac 67 88 b0  fe e2 75 ed 2a 8d 
98 4e
Mar  1 13:01:18 localhost kernel: 7d ae e4 94 2d 44 fa ba  6b b0 2b 7a 8c d4 
9b b0
Mar  1 13:01:18 localhost kernel: 57 26 64 09 b5 b4 33 fc  c4 4b 09 dc 1d b5 
94 12
Mar  1 13:01:18 localhost kernel: 4a 79 e6 ce 92 c0 f8 b7  55 ef 57 43 48 97 
e8 7d
Mar  1 13:01:18 localhost kernel: f1 8c 9b eb 48 6b 60 05  99 c9 5c e0 c8 bf 
62 cd
Mar  1 13:01:18 localhost kernel: 6b be e3 45 d9 17 98 df  66 b1 69 53 9b b5 
ef f1
Mar  1 13:01:18 localhost kernel: 40 c8 1f 4e e1 04 69 49  b6 76 55 78 98 36 
e2 12
Mar  1 13:01:18 localhost kernel: 3a 59 17 72 1e b3 3a e9  38 05 f3 e4 7f 9d 
54 12
Mar  1 13:01:18 localhost kernel: f3 34 e9 24 75 b4 4b 84  cd 53 8d b2 85 4e 
ea 2b
Mar  1 13:01:18 localhost kernel: 00 1a de 05 0c 33 00 1f  af ad ab 67 ff b3 
e1 25
Mar  1 13:01:18 localhost kernel: cb fd a3 74 3c ec 38 a1  4d 3e 5d 33 ba 80 
67 8b
Mar  1 13:01:18 localhost kernel: bf af b8 44 b9 32 02 58  37 77 b6 08 14 18 
3b eb
Mar  1 13:01:18 localhost kernel: 22 be cd 43 d4 57 61 38  7e 10 24 c6 4a a1 
1e df
Mar  1 13:01:18 localhost kernel: 1f 98 58 05 9f 36 ca 59  ef 6c 3a ea fc 13 
70 2c
Mar  1 13:01:18 localhost kernel: 04 1e ed 87 b3 db 88 07  9b d0 28 bd ea 37 
8e f1
Mar  1 13:01:18 localhost kernel: 1d 45 8c e3 c1 e9 f8 d7  af cf 0c 24 6d 26 
4b 20
Mar  1 13:01:18 localhost kernel: 3f ae 42 0d 1b f6 df 62  67 af 64 34 b3 36 
6c aa
Mar  1 13:01:18 localhost kernel:
Mar  1 13:01:18 localhost kernel: ath_tx_start: Q1: (ds)dcf82040 
(lk)00000000 (d)125ce84e (c0)41620204 (c1)06008200 000b00cc 0090000c
Mar  1 13:01:18 localhost kernel: ath_tx_txqaddbuf: txq depth = 2
Mar  1 13:01:18 localhost kernel: ath_tx_txqaddbuf: link[1] 
(dcf81fe0)=1cf82040 (dcf82040)
Mar  1 13:01:18 localhost kernel: ath_tx_start: skb0 ddfd1c40 [data d07f1410 
len 512] skbaddr 107f1410
Mar  1 13:01:18 localhost kernel: FRDS 
00:0f:66:11:c1:97->00:0f:66:11:c1:96(00:0f:66:11:c1:97) data 54M
Mar  1 13:01:18 localhost kernel:
Mar  1 13:01:18 localhost kernel: 08 06 cc 00 00 0f 66 11  c1 96 00 0f 66 11 
c1 97
Mar  1 13:01:18 localhost kernel: 00 0f 66 11 c1 97 f1 ath_intr: status 0x40
Mar  1 13:01:18 localhost kernel: 29  8a 19 f3 17 c5 9e 9e a8
Mar  1 13:01:18 localhost kernel: 97 38 45 60 ac 38 77 33  72 a0 40 53 c0 a1 
24 70
Mar  1 13:01:18 localhost kernel: 4f 2a ca 1c 6c f8 88 22  47 4c 64 58 cd a8 
f1 a1
Mar  1 13:01:18 localhost kernel: fa c4 03 7e d3 ab 87 91  f1 10 ff 8f 29 72 
3b 45
Mar  1 13:01:18 localhost kernel: 24 41 5e c9 00 0c ed 2e  00 e7 ee de 28 d2 
94 f6
Mar  1 13:01:18 localhost kernel: 81 93 d8 4a a8 2d 84 64  c9 32 b8 03 ca 35 
7c 26
Mar  1 13:01:18 localhost kernel: f6 b6 d0 0b dc d1 cc 9f  fe 47 af ec 70 49 
27 6a
Mar  1 13:01:18 localhost kernel: ec b8 97 59 33 1b 11 44  84 c7 f8 2d 72 ee 
19 9c
Mar  1 13:01:18 localhost kernel: 08 89 49 00 91 7b 59 97  ef ca 7a 83 fa 3b 
c4 e1
Mar  1 13:01:18 localhost kernel: 1f f6 fb 1f e0 37 25 bf  c7 18 11 1f b2 00 
fd 6b
Mar  1 13:01:18 localhost kernel: bc a0 97 1e c7 59 de af  4d b3 79 22 19 05 
e0 fb
Mar  1 13:01:18 localhost kernel: 3f d7 dd 7f 6b a0 0f e7  7b 1a 09 9a 73 08 
c7 5b
Mar  1 13:01:18 localhost kernel: d0 ea f8 38 12 6a db 96  06 9e 4c b6 59 6b 
79 5e
Mar  1 13:01:18 localhost kernel: ca 5a 83 2e 40 8b 32 0e  35 ca e0 ec ec dc 
fa 4b
Mar  1 13:01:18 localhost kernel: f8 ca 26 16 d1 91 89 12  bd c2 ca 59 b3 9d 
9b dc
Mar  1 13:01:18 localhost kernel: 16 cb c9 50 d9 4c 42 c0  34 ba df ba cd 76 
7d 0b
Mar  1 13:01:18 localhost kernel: c4 df 42 79 be b5 37 88  da c2 b7 f6 ae 82 
fc 6d
Mar  1 13:01:18 localhost kernel: e3 fa 67 72 ec d9 89 15  d0 98 4f 77 54 28 
5b 5a
Mar  1 13:01:18 localhost kernel: 75 be b9 0a 54 cc c8 73  0f 95 23 24 1a 38 
c6 84
Mar  1 13:01:18 localhost kernel: 95 49 34 f4 a1 1d 00 9c  ea 9f 18 d4 3a 66 
55 db
Mar  1 13:01:18 localhost kernel: 09 bf 81 9e db ad c1 2c  5d ec f8 cd 50 eb 
08 78
Mar  1 13:01:18 localhost kernel: 2f 50 f4 7d 0a 99 31 53  93 ce 89 ed 4e 9e 
2c 4e
Mar  1 13:01:18 localhost kernel: 87 7d 5c 07 68 0e f5 2c  d2 87 44 0b a8 e7 
e0 3e
Mar  1 13:01:18 localhost kernel: 52 7e 23 aa 01 b1 32 0f  39 f0 59 03 47 e5 
8a a0
Mar  1 13:01:18 localhost kernel: a3 72 27 bf 3d f8 d7 4b  1a b1 f0 47 17 bd 
0a 85
Mar  1 13:01:18 localhost kernel: 26 15 3e a3 c1 e0 dd dc  04 b4 3f f6 c5 50 
89 0f
Mar  1 13:01:18 localhost kernel: 15 a1 2f 85 30 43 70 99  c7 8a b6 8a 93 b3 
f8 70
Mar  1 13:01:18 localhost kernel: 52 fc cb 05 d5 e3 36 37  09 70 46 35 38 b3 
4d d8
Mar  1 13:01:18 localhost kernel: 54 33 37 c4 52 ac 3a 89  3f 7e 13 69 1c da 
a4 77
Mar  1 13:01:18 localhost kernel: ae ca 58 a3 7b 71 01 63  38 52 44 20 16 37 
68 61
Mar  1 13:01:18 localhost kernel: 0b 8f 9f f3 2e 3c b5 60  63 60 e6 3f 38 33 
a4 ed
Mar  1 13:01:18 localhost kernel:
Mar  1 13:01:18 localhost kernel: ath_tx_start: Q1: (ds)dcf820a0 
(lk)00000000 (d)107f1410 (c0)41620204 (c1)06008200 000b00cc 0090000c
Mar  1 13:01:18 localhost kernel: ath_tx_txqaddbuf: txq depth = 3


so my questions are:
1) why client cann't authenticate to freeradius? maybe i'm missing any 
configuration
or freeradius and hostapd aren't working well together?
2) is there any way i can test my certificates from freeradius?? any 
command?
or may be install wpa-supplicant over my debian and test from there 
(authenticator and supplicant in same machine??).
3) why client stops in "Trying to authenticate"? maybe any configuration or 
password am i missing??
4)as you can see en freeradius and hostapd log they say "CONNECT 11Mbps 
802.11b" but i configured my ap to work with 802.11g, so why this behavior?

could any body try to help? i'm really desperate because this is a work for 
university and i must present it next week. please!!!

thanks in advance for your help and time.

_________________________________________________________________
MSN Amor: busca tu ? naranja http://latam.msn.com/amor/




From phamtienluc  Wed Mar  1 17:20:35 2006
From: phamtienluc (phamtienluc phamtienluc)
Date: Wed, 1 Mar 2006 17:20:35 -0800 (PST)
Subject: network speed with wpa_supplicant
Message-ID: <20060302012035.15599.qmail@web31506.mail.mud.yahoo.com>

Dear Jouni Malinen

I have read email "Re: network speed with
wpa_supplicant". In the mail: "wpa_supplicant has
nothing to do with transmitting data packets it is
taking care of authentication and key configuration,
but after that, all depends on the driver". 

I have a question, i want to change DES cipher with
any cipher. where do I change?? in driver or source of
wpa_supplicant

Thank
Regard

Luc pt

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



From chadlich  Wed Mar  1 20:21:34 2006
From: chadlich (Chad Meister)
Date: Wed, 1 Mar 2006 20:21:34 -0800 (PST)
Subject: Association Problems. (WPA_Supplicant 0.5.1 + Madwifi-ng20060210)
In-Reply-To: <20060228032733.GA9338@jm.kir.nu>
Message-ID: <20060302042134.57134.qmail@web35902.mail.mud.yahoo.com>

Hi,

Sorry for the confusion. I'm running madwifi r1437
with the wpa config value set to 1.  Therefore, my
setup is WPA.  It won't accept 2 (WPA2) or 3
(WPA+WPA2).  I'll upgrade soon to r1453. 

So does this mean that this bug
(http://madwifi.org/ticket/241) is closed?

Thanks for the tip,

Chad

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

> On Mon, Feb 27, 2006 at 09:20:30AM -0800, Chad
> Meister wrote:
> 
> > Well, if your looking for a stable version of
> > madwifi-ng, I'm using svn version r1437 on
> GNU/Linux
> > kernel 2.6.13.1.  
> 
> I'm using r1453 and that seems to work, too, without
> major problems.
> 
> > Even though I've enable CCMP, instead of TKIP, I
> don't
> >  think it's a genuine RSN setup, but some sort of
> > hybrid , maybe TSN. (wifi alphabet soup).  This is
> > because I can't set the hostapd.conf variable:
> wpa=1. 
> > It only works as wpa=0.
> 
> Do you mean: cannot set it to wpa=2 or wpa=3? wpa=0
> would mean that
> WPA/WPA2 is disabled completely..
> 
> > I think this is some sort of bug in hostapd, but
> there
> > is a workaround patch for it, I think, at
> madwifi.org.
> 
> I believe the driver had a bug that was fixed and
> that fix happened to
> change the interface to hostapd which required yet
> another change..
> Anyway, the current CVS/SVN versions seem to work
> fine with WPA, WPA2
> and mixed WPA+WPA2 mode. This was fixed around
> r1453, so your version is
> likely too old to have the needed changes.
> 
> -- 
> Jouni Malinen                                       
>     PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



From jkmaline  Wed Mar  1 20:44:27 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 1 Mar 2006 20:44:27 -0800
Subject: Association Problems. (WPA_Supplicant 0.5.1 + Madwifi-ng20060210)
In-Reply-To: <20060302042134.57134.qmail@web35902.mail.mud.yahoo.com>
References: <20060228032733.GA9338@jm.kir.nu>
	<20060302042134.57134.qmail@web35902.mail.mud.yahoo.com>
Message-ID: <20060302044427.GA9350@jm.kir.nu>

On Wed, Mar 01, 2006 at 08:21:34PM -0800, Chad Meister wrote:

> So does this mean that this bug
> (http://madwifi.org/ticket/241) is closed?

As far as the current development versions of madwifi-ng and hostapd are
concerned, yes, that has been resolved. However, I have not yet merged
that change into the stable branch of hostapd.

-- 
Jouni Malinen                                            PGP id EFC895FA



From air_erik2002  Thu Mar  2 05:00:41 2006
From: air_erik2002 (Erik Pozo)
Date: Thu, 2 Mar 2006 14:00:41 +0100 (CET)
Subject: What's KISMET??
Message-ID: <20060302130041.60747.qmail@web25710.mail.ukl.yahoo.com>

Hi, I want to know, What's Kismet??, What's its main job, what are the advantages and How can I use it in Fedora Core 2 (install and configure)
   
  Please help me
   
  Thanks
   
  Erik

		
---------------------------------

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y m?viles desde 1 c?ntimo por minuto.
http://es.voice.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060302/745b0258/attachment.htm 


From ismail  Thu Mar  2 05:35:57 2006
From: ismail (Ismail Donmez)
Date: Thu, 2 Mar 2006 15:35:57 +0200
Subject: What's KISMET??
In-Reply-To: <20060302130041.60747.qmail@web25710.mail.ukl.yahoo.com>
References: <20060302130041.60747.qmail@web25710.mail.ukl.yahoo.com>
Message-ID: <200603021536.02384.ismail@uludag.org.tr>

Per?embe 2 Mart 2006 15:00 tarihinde, Erik Pozo ?unlar? yazm??t?: 
> Hi, I want to know, What's Kismet??, What's its main job, what are the
> advantages and How can I use it in Fedora Core 2 (install and configure)

Google would tell you its at http://www.kismetwireless.net/ .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060302/756ea9ba/attachment.pgp 


From air_erik2002  Thu Mar  2 06:53:49 2006
From: air_erik2002 (Erik Pozo)
Date: Thu, 2 Mar 2006 15:53:49 +0100 (CET)
Subject: What's Wavemon??
Message-ID: <20060302145350.85154.qmail@web25709.mail.ukl.yahoo.com>

Hi, I want to know What's Wavemon??, what's its main job, how can I use it (install and Configure) especially in Fedora Core2
   
  Thanks for all
   
  Erik

		
---------------------------------

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y m?viles desde 1 c?ntimo por minuto.
http://es.voice.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060302/f336f91f/attachment.htm 


From bvthadden  Thu Mar  2 08:51:25 2006
From: bvthadden (Bodo von Thadden)
Date: Thu, 2 Mar 2006 17:51:25 +0100 (MET)
Subject: What's Wavemon??
References: <20060302145350.85154.qmail@web25709.mail.ukl.yahoo.com>
Message-ID: <4038.1141318285@www031.gmx.net>

> --- Urspr?ngliche Nachricht ---
> Von: Erik Pozo <air_erik2002 at yahoo.es>
> An: hostap at shmoo.com
> Betreff: What's Wavemon??
> Datum: Thu, 2 Mar 2006 15:53:49 +0100 (CET)
> 
> Hi, I want to know What's Wavemon??, what's its main job, how can I use it
> (install and Configure) especially in Fedora Core2
>    
>   Thanks for all
>    
>   Erik
>

I think google is your best friend ;-)
http://freshmeat.net/projects/wavemon/

Bodo



From ramalhais  Thu Mar  2 09:52:38 2006
From: ramalhais (Pedro Ramalhais)
Date: Thu, 02 Mar 2006 17:52:38 +0000
Subject: What's Wavemon??
In-Reply-To: <20060302145350.85154.qmail@web25709.mail.ukl.yahoo.com>
References: <20060302145350.85154.qmail@web25709.mail.ukl.yahoo.com>
Message-ID: <440730E6.80202@serrado.net>

Erik Pozo wrote:
> Hi, I want to know What's Wavemon??, what's its main job, how can I use
> it (install and Configure) especially in Fedora Core2
>  
> Thanks for all
>  
> Erik
> 
> ------------------------------------------------------------------------
> 
> LLama Gratis a cualquier PC del Mundo.
> Llamadas a fijos y m?viles desde 1 c?ntimo por minuto.
> http://es.voice.yahoo.com
> <http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

Stop being a lazy ass.
-- 
Pedro Ramalhais



From me  Thu Mar  2 10:23:13 2006
From: me (Jay Strauss)
Date: Thu, 2 Mar 2006 12:23:13 -0600
Subject: What's Google??
Message-ID: <aabc51b60603021023y57edcb91qa9e76117561ccca1@mail.gmail.com>

Hi, I want to know What's Google??, what's its main job, how can I use it
(install and Configure) especially in Fedora Core2

Thanks for all

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060302/8295dfca/attachment.htm 


From ismail  Thu Mar  2 10:25:13 2006
From: ismail (Ismail Donmez)
Date: Thu, 2 Mar 2006 20:25:13 +0200
Subject: What's Google??
In-Reply-To: <aabc51b60603021023y57edcb91qa9e76117561ccca1@mail.gmail.com>
References: <aabc51b60603021023y57edcb91qa9e76117561ccca1@mail.gmail.com>
Message-ID: <200603022025.14074.ismail@uludag.org.tr>

Per?embe 2 Mart 2006 20:23 tarihinde, Jay Strauss ?unlar? yazm??t?: 
> Hi, I want to know What's Google??, what's its main job, how can I use it
> (install and Configure) especially in Fedora Core2
>
> Thanks for all

Good one ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060302/475712fa/attachment.pgp 


From me  Thu Mar  2 10:31:52 2006
From: me (Jay Strauss)
Date: Thu, 2 Mar 2006 12:31:52 -0600
Subject: What's Google??
In-Reply-To: <200603022025.14074.ismail@uludag.org.tr>
References: <aabc51b60603021023y57edcb91qa9e76117561ccca1@mail.gmail.com>
	<200603022025.14074.ismail@uludag.org.tr>
Message-ID: <aabc51b60603021031t458b7aa5vf1d772b430baef5b@mail.gmail.com>

On 3/2/06, Ismail Donmez <ismail at uludag.org.tr> wrote:
>
> Per?embe 2 Mart 2006 20:23 tarihinde, Jay Strauss ?unlar? yazm??t?:
> > Hi, I want to know What's Google??, what's its main job, how can I use
> it
> > (install and Configure) especially in Fedora Core2
> >
> > Thanks for all
>
> Good one ;)


A little immature, but it gave me a smile.  As a lurker I probably should
restrain myself.  But no one ever asks "how do I get hostap working on a
thinkpad A30 with a prism card" for me to answer

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060302/442ba059/attachment.htm 


From kelrin  Thu Mar  2 13:16:24 2006
From: kelrin (Kel Modderman)
Date: Fri, 03 Mar 2006 07:16:24 +1000
Subject: wpa_cli quirks?
In-Reply-To: <44058834.5030904@tpg.com.au>
References: <44058834.5030904@tpg.com.au>
Message-ID: <440760A8.6030904@tpg.com.au>

Kel Modderman wrote:

> Hi,
>
> I'd like to query the handling of wpa_cli commands executed as 
> arguments, rather than  from within the wpa_cli console. Are they 
> handled differently as in the following example?
>
>
> root at KELSLAP:/home/kel# wpa_cli -i eth1 set_network 1 ssid "kelnet"
> FAIL

RX ctrl_iface - hexdump_ascii(len=25):
     53 45 54 5f 4e 45 54 57 4f 52 4b 20 30 20 73 73   SET_NETWORK 0 ss
     69 64 20 6b 65 6c 6e 65 74                        id kelnet
CTRL_IFACE: SET_NETWORK id=0 name='ssid' value='kelnet'
Line 0: failed to parse ssid 'kelnet'.
CTRL_IFACE: Failed to set network variable 'ssid' to 'kelnet'


> root at KELSLAP:/home/kel# wpa_cli -i eth1
> wpa_cli v0.5.1
> Copyright (c) 2004-2006, Jouni Malinen <jkmaline at cc.hut.fi> and 
> contributors
>
> This program is free software. You can distribute it and/or modify it
> under the terms of the GNU General Public License version 2.
>
> Alternatively, this software may be distributed under the terms of the
> BSD license. See README and COPYING for more details.
>
>
> Interactive mode
>
> > set_network 1 ssid "kelnet"
> OK
> >
>

RX ctrl_iface - hexdump_ascii(len=27):
     53 45 54 5f 4e 45 54 57 4f 52 4b 20 30 20 73 73   SET_NETWORK 0 ss
     69 64 20 22 6b 65 6c 6e 65 74 22                  id "kelnet"
CTRL_IFACE: SET_NETWORK id=0 name='ssid' value='"kelnet"'
ssid - hexdump_ascii(len=6):
     6b 65 6c 6e 65 74                                 kelnet


There seems to be an extra bit on the end of the hexdump when the 
command is issued from within the console. I have no idea why.

Thanks, Kel.



From dcbw  Thu Mar  2 13:43:54 2006
From: dcbw (Dan Williams)
Date: Thu, 02 Mar 2006 16:43:54 -0500
Subject: Association Problems. (WPA_Supplicant 0.5.1 + Madwifi-ng20060210)
In-Reply-To: <20060228032733.GA9338@jm.kir.nu>
References: <007001c63baa$d8df4db0$c801a8c0@xchgaix.i2e.fr>
	<20060227172030.13828.qmail@web35910.mail.mud.yahoo.com>
	<20060228032733.GA9338@jm.kir.nu>
Message-ID: <1141335835.9840.3.camel@dhcp83-104.boston.redhat.com>

On Mon, 2006-02-27 at 19:27 -0800, Jouni Malinen wrote:
> On Mon, Feb 27, 2006 at 09:20:30AM -0800, Chad Meister wrote:
> 
> > Well, if your looking for a stable version of
> > madwifi-ng, I'm using svn version r1437 on GNU/Linux
> > kernel 2.6.13.1.  
> 
> I'm using r1453 and that seems to work, too, without major problems.

r1457 appears completely broken WRT unencrypted networks, and for
WEP-104 networks with hidden ESSIDs.  I've tried all sorts of
scan_ssid=1, ap_scan=1, ap_scan=2, but nothing makes the card associate
with wpa_supplicant.  WTF is the problem with madwifi here?  It's
completely inconsistent between driver revisions...

Dan


-------------- next part --------------
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'madwifi' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 42 - start of a new network block
ssid - hexdump_ascii(len=6):
     65 72 65 62 6f 72                                 erebor
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
scan_ssid=1 (0x1)
Priority group 0
   id=0 ssid='erebor'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=13 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:0f:b5:9e:5f:71
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
Added interface ath0
Wireless event: cmd=0x8b06 len=8
Ignore event for foreign ifindex 6
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=6):
     65 72 65 62 6f 72                                 erebor
Wireless event: cmd=0x8b1a len=15
Scan timeout - try to get results
Received 2370 bytes of scan results (14 BSSes)
Scan results: 14
Selecting BSS from priority group 0
<14 AP records snipped for security>
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=8
Scan timeout - try to get results
Received 2133 bytes of scan results (13 BSSes)
Scan results: 13
Selecting BSS from priority group 0
<13 AP records snipped for security>
No suitable AP found.
Setting scan request: 5 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: SCANNING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
Cancelling scan request


[@dhcp83-104 wpa_supplicant-0.4.8]# ./wpa_supplicant -ddd -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'madwifi' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
Line: 42 - start of a new network block
ssid - hexdump_ascii(len=6):
     65 72 65 62 6f 72                                 erebor
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
scan_ssid=1 (0x1)
Priority group 0
   id=0 ssid='erebor'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=13 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:0f:b5:9e:5f:71
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
Added interface ath0
Wireless event: cmd=0x8b06 len=8
Ignore event for foreign ifindex 6
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'erebor'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b19 len=8
Received 1688 bytes of scan results (10 BSSes)
Scan results: 10
Wireless event: cmd=0x8b2a len=8
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'erebor'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
State: ASSOCIATING -> DISCONNECTED
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'erebor'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b1a len=15
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
State: ASSOCIATING -> DISCONNECTED
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'erebor'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b2a len=8
Wireless event: cmd=0x8b1a len=15
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request



From zhangyanfeng  Thu Mar  2 18:20:50 2006
From: zhangyanfeng (zhangyanfeng)
Date: Fri, 3 Mar 2006 10:20:50 +0800
Subject: about handoff latency
References: <20060301090447.BE3DE5642CA@mail.iocaine.com>
Message-ID: <001e01c63e69$16fc27b0$914c1cac@ad.research.nec.com.cn>

Could anyone tell me how much time channel switch of a Prism II will cost, 
and how to decrease it?
Best Regards,

---------------------------------------------------------
Leonard Zhang




From jeremy  Fri Mar  3 14:11:27 2006
From: jeremy (Jeremy Moles)
Date: Fri, 03 Mar 2006 17:11:27 -0500
Subject: WPA Python Bindings
In-Reply-To: <001e01c63e69$16fc27b0$914c1cac@ad.research.nec.com.cn>
References: <20060301090447.BE3DE5642CA@mail.iocaine.com>
	<001e01c63e69$16fc27b0$914c1cac@ad.research.nec.com.cn>
Message-ID: <1141423887.2509.5.camel@localhost.localdomain>

We are developing a PyGTK based GUI for our customers to finally,
once-and-for-all, smash wireless issues.

I've written a sensible set of Python bindings for both libiw and
wpa_supplicant, both of which are freely available to anyone who might
be interested.

pywpa --> http://downloads.emperorlinux.com/contrib/pywpa
pyiw  --> http://downloads.emperorlinux.com/contrib/pyiw

(I chose not to simply devote time to improving NetworkManager--the
other killer app--since it's written in C. Even though I'm a C
programmer, you just don't get work done fast that way.)

Thanks for making a great piece of software. Working with WPA--and it's
ctrl interface--is a pleasure.

P.S. Though I'm sure this has come up before, I'll ask again: is there
work underway (or would there be opposition to me doing so) for creating
DBUS hooks in wpa_supplicant?




From jeremy  Fri Mar  3 14:23:09 2006
From: jeremy (Jeremy Moles)
Date: Fri, 03 Mar 2006 17:23:09 -0500
Subject: WPA Python Bindings
Message-ID: <1141424589.2509.18.camel@localhost.localdomain>

Sorry for the double-post; e-mail is so busted and deprecated,
ugh... .:)

-------------------------------------------------------------------------

We are developing a PyGTK based GUI for our customers to finally,
once-and-for-all, smash wireless issues.

I've written a sensible set of Python bindings for both libiw and
wpa_supplicant, both of which are freely available to anyone who might
be interested.

pywpa --> http://downloads.emperorlinux.com/contrib/pywpa
pyiw  --> http://downloads.emperorlinux.com/contrib/pyiw

(I chose not to simply devote time to improving NetworkManager--the
other killer app--since it's written in C. Even though I'm a C
programmer, you just don't get work done fast that way.)

Thanks for making a great piece of software. Working with WPA--and it's
ctrl interface--is a pleasure.

P.S. Though I'm sure this has come up before, I'll ask again: is there
work underway (or would there be opposition to me doing so) for creating
DBUS hooks in wpa_supplicant?




From stefan  Fri Mar  3 15:04:54 2006
From: stefan (Stefan Rompf)
Date: Sat, 4 Mar 2006 00:04:54 +0100
Subject: PATCH RFC: wpa_supplicant influencing device operstate
Message-ID: <200603040004.55477.stefan@loplof.de>

Hi,

some weeks ago, there has been a quite heated discussion on linux-netdev about 
extending functionality of netif_carrier_on()/off(). In the end, a patch 
written by me has been applied for 2.6.17. For an overview, see the 
documentation at http://www.flamewarmaster.de/software/operstates.txt . The 
patch itself (applies to 2.6.14+) can be found on this site too. Main point 
concerning this list is that it allows an userspace supplicant to signal the 
kernel when the interface is ready for user traffic after authentication, and 
afterwards, kernel notifies other programs via the existing IFF_RUNNING 
interface.

The quagga routing daemon, vrrpd and my new dhcp client 
(http://www.flamewarmaster.de/software/dhcpclient/) can act on these 
messages.

I have attached a patch against wpa_supplicant 0.5.1 to this mail that 
implements signalling functionality in the WEXT driver. Note that I haven't 
tested how this affects drivers that rely on WEXT functionality - this is a 
very first version.

With this extension, I can start wpa_supplicant and my DHCP client in 
parallel. Whenever the supplicant has completed association, and WPA 
authentication if needed, the DHCP client will automatically update the 
interface IP configuration. Together with a graphical wpa_cli (will try 
wpa_gui), this increases usability of wireless LANs a lot. In the long run, 
I'd like this feature to be added to wpa_supplicant.

Thoughts?

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant.diff
Type: text/x-diff
Size: 7523 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060304/331eea09/attachment.diff 


From christian  Sat Mar  4 05:08:14 2006
From: christian (Christian Roessner)
Date: Sat, 04 Mar 2006 14:08:14 +0100
Subject: ndiswrapper/ wireless-tools, wpa_supplicant question
Message-ID: <4409913E.8020901@roessner-net.com>

Hi,

I have spent many hours in trying to get my wifi card configured with
ndiswrapper, wireless-tools and wpa_supplicant.

I installed ndiswrapper 1.8 with CD drivers for the NetGear WG111v2
(Also tested version 1.9, 10.10, 1.11_rc and 1.2).

Also tested all versions available from wireless-tools (starting with
version 27 up to 28_pre14

At least wpa_supplicant versions 4.7, 4.8 and 5.1

I have a standard wpa_supplicant.conf like this:

http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/*checkout*/hostap/wpa_supplicant/examples/wpa-psk-tkip.conf?rev=HEAD&content-type=text/plain

If just doing an ifconfig wlan0 up and starting wpa_supplicant like

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

I NEVER get an successfull association.

If using iwconfig wlan0 essid RNS2 and doing as quickly as possible the
wpa_supplicant comannd, I may be lucky and get the stuff done.

Then I can background the process and do my dhcpcd wlan0 stuff.

It seems that wpa_supplicant has some problems with the association
process. I do not know, if this is wpa_supplicant related or
ndiswrapper/wireless-tools. But because I can have success and even
changed the windows drivers from NetGear to RTL8187 on ndiswrapper, I
believe the root of these problems might be a bug in wpa_supplicant.
Maybe some timing problems??

See the attahced files please.

If you could help me with this, I would be really happy  ;-)

Regards

Christian

N.B.: I am running a stable Gentoo release. Everything was compiled with
CFLAGS="-O0 -march=i686"


-- 
Tel.: 0641-2097252, Mobil: 0171-3611230
PGP: http://www.roessner-net.com/0x6B929997.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: fail.log.gz
Type: application/gzip
Size: 2193 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060304/66431a63/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: success.log.gz
Type: application/gzip
Size: 2494 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060304/66431a63/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060304/66431a63/attachment.pgp 


From bvthadden  Sat Mar  4 07:37:59 2006
From: bvthadden (Bodo von Thadden)
Date: Sat, 4 Mar 2006 16:37:59 +0100 (MET)
Subject: ndiswrapper/ wireless-tools, wpa_supplicant question
References: <4409913E.8020901@roessner-net.com>
Message-ID: <31116.1141486679@www086.gmx.net>

> --- Urspr?ngliche Nachricht ---
> Von: Christian Roessner <christian at roessner-net.com>
> An: hostap at shmoo.com
> Betreff: ndiswrapper/ wireless-tools, wpa_supplicant question
> Datum: Sat, 04 Mar 2006 14:08:14 +0100
> 
> Hi,
> 
> I have spent many hours in trying to get my wifi card configured with
> ndiswrapper, wireless-tools and wpa_supplicant.
> 
> I installed ndiswrapper 1.8 with CD drivers for the NetGear WG111v2
> (Also tested version 1.9, 10.10, 1.11_rc and 1.2).
> 
> Also tested all versions available from wireless-tools (starting with
> version 27 up to 28_pre14
> 
> At least wpa_supplicant versions 4.7, 4.8 and 5.1
> 
> I have a standard wpa_supplicant.conf like this:
> 
>
http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/*checkout*/hostap/wpa_supplicant/examples/wpa-psk-tkip.conf?rev=HEAD&content-type=text/plain
> 
> If just doing an ifconfig wlan0 up and starting wpa_supplicant like
> 
> wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -w -Dndiswrapper -dd
> 
> I NEVER get an successfull association.
> 
> If using iwconfig wlan0 essid RNS2 and doing as quickly as possible the
> wpa_supplicant comannd, I may be lucky and get the stuff done.
> 
> Then I can background the process and do my dhcpcd wlan0 stuff.
> 
> It seems that wpa_supplicant has some problems with the association
> process. I do not know, if this is wpa_supplicant related or
> ndiswrapper/wireless-tools. But because I can have success and even
> changed the windows drivers from NetGear to RTL8187 on ndiswrapper, I
> believe the root of these problems might be a bug in wpa_supplicant.
> Maybe some timing problems??
> 
> See the attahced files please.
> 
> If you could help me with this, I would be really happy  ;-)
> 
> Regards
> 
> Christian
> 
> N.B.: I am running a stable Gentoo release. Everything was compiled with
> CFLAGS="-O0 -march=i686"
> 
> 
> -- 
> Tel.: 0641-2097252, Mobil: 0171-3611230
> PGP: http://www.roessner-net.com/0x6B929997.asc
> 
> 
> 

 Tach Christian,

I also use the Netgear WG111v2 and the router is also from Netgear. I also
use Gentoo Linux ;-) Yes, there is indeed a problem with the timeout &
ndiswrapper.
But it works fine here, on my system. Even at bootup it's connect to the
router (most of the time - but some times I get also a timeout). But I get
it connect, if I do it manuell. I have set the time-out high, to about 5
min.
This is my /etc/conf.d/net :

modules=("wpa_supplicant")
iwconfig_wlan0="essid NETGEAR"
wpa_supplicant_wlan0="-Dndiswrapper"
wpa_timeout_wlan0=360
config_wlan0=("192.168.0.2 netmask 255.255.255.0")
routes_wlan0=("default gw 192.168.0.1")


It should work. I use ndiswrapper version 1.10 and wpa_supplicant version
0.48.

Greetings from Braunschweig
Bodo



From christian  Sun Mar  5 04:09:20 2006
From: christian (Christian Roessner)
Date: Sun, 05 Mar 2006 13:09:20 +0100
Subject: ndiswrapper/ wireless-tools, wpa_supplicant question
In-Reply-To: <31116.1141486679@www086.gmx.net>
References: <4409913E.8020901@roessner-net.com>
	<31116.1141486679@www086.gmx.net>
Message-ID: <440AD4F0.5040301@roessner-net.com>

Moin, Moin,

>  Tach Christian,
> 
> I also use the Netgear WG111v2 and the router is also from Netgear. I also
> use Gentoo Linux ;-) Yes, there is indeed a problem with the timeout &
> ndiswrapper.
> But it works fine here, on my system. Even at bootup it's connect to the
> router (most of the time - but some times I get also a timeout). But I get
> it connect, if I do it manuell. I have set the time-out high, to about 5
> min.
> This is my /etc/conf.d/net :
> 
> modules=("wpa_supplicant")
> iwconfig_wlan0="essid NETGEAR"
> wpa_supplicant_wlan0="-Dndiswrapper"
> wpa_timeout_wlan0=360
> config_wlan0=("192.168.0.2 netmask 255.255.255.0")
> routes_wlan0=("default gw 192.168.0.1")

first of all: Thanks. Unfortunatley, this does not work for me :-( The
only way I get connected is running wpa_supplicant in debug mode. If
using -B, it never gets connected!

Does someone else have any ideas? I would like to know, if this is
wpa_supplicant or ndiswrapper related, so I may ask for help at the
right forum.

Thanks und sch?ne Gr??e aus Gie?en

Christian

-- 
Tel.: 0641-2097252, Mobil: 0171-3611230
PGP: http://www.roessner-net.com/0x6B929997.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060305/0d229110/attachment.pgp 


From chadlich  Sun Mar  5 12:48:56 2006
From: chadlich (Chad Meister)
Date: Sun, 5 Mar 2006 12:48:56 -0800 (PST)
Subject: Association Problems. (WPA_Supplicant 0.5.1 + Madwifi-ng20060210)
In-Reply-To: <20060302044427.GA9350@jm.kir.nu>
Message-ID: <20060305204856.48684.qmail@web35907.mail.mud.yahoo.com>

Hi,

Well, I upgraded to r1453, the stable version of
madwifi-ng and upgraded to the development branch of
hostapd (hostap_0_5_1).  Authentification fails on the
wpa_supplicant side of things.

I get this error message
****begin error message

wpa_supplicant -dd -D madwifi -i ath0 -c
/etc/wpa_supplicant/wpa_supplicant.conf
Initializing interface 'ath0' conf
'/etc/wpa_supplicant/wpa_supplicant.conf' driver
'madwifi' ctrl_interface 'N/A'
Configuration file
'/etc/wpa_supplicant/wpa_supplicant.conf' ->
'/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file
'/etc/wpa_supplicant/wpa_supplicant.conf'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 349 - start of a new network block
ssid - hexdump_ascii(len=5):
     6f 75 73 69 61                                   
ousia
key_mgmt: 0x1
eap methods - hexdump(len=16): 00 00 00 00 0d 00 00 00
00 00 00 00 00 00 00 00
proto: 0x2
auth_alg: 0x1
pairwise: 0x10
identity - hexdump_ascii(len=10):
     68 65 72 61 63 6c 69 74 75 73                    
heraclitus
ca_cert - hexdump_ascii(len=36):
     2f 65 74 63 2f 77 70 61 5f 73 75 70 70 6c 69 63  
/etc/wpa_supplic
     61 6e 74 2f 63 65 72 74 73 2f 63 61 63 65 72 74  
ant/certs/cacert
     2e 70 65 6d                                      
.pem
client_cert - hexdump_ascii(len=41):
     2f 65 74 63 2f 77 70 61 5f 73 75 70 70 6c 69 63  
/etc/wpa_supplic
     61 6e 74 2f 63 65 72 74 73 2f 63 6c 69 65 6e 74  
ant/certs/client
     5f 63 65 72 74 2e 70 65 6d                       
_cert.pem
private_key - hexdump_ascii(len=40):
     2f 65 74 63 2f 77 70 61 5f 73 75 70 70 6c 69 63  
/etc/wpa_supplic
     61 6e 74 2f 63 65 72 74 73 2f 63 6c 69 65 6e 74  
ant/certs/client
     5f 6b 65 79 2e 70 65 6d                          
_key.pem
private_key_passwd - hexdump_ascii(len=8): [REMOVED]
Priority group 0
   id=0 ssid='ousia'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=18 WE(source)=13
enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:02:6f:39:cb:92
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
Failed to initialize control interface '(null)'.
You may have another wpa_supplicant process already
running or the file was left by an unclean termination
of wpa_supplicant in which case you will need to
manually remove this file before starting
wpa_supplicant again.

Failed to add interface ath0
State: DISCONNECTED -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
No keys have been configured - skip key clearing

*******end error message
It looks like wpa_supplicant is looking for the
crtl_interface at /var/run/wpa_supplicant.  However,
as the message suggests ctrl_interface is N/A for the
madwifi driver.

Any ideas here?

Chad

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

> On Wed, Mar 01, 2006 at 08:21:34PM -0800, Chad
> Meister wrote:
> 
> > So does this mean that this bug
> > (http://madwifi.org/ticket/241) is closed?
> 
> As far as the current development versions of
> madwifi-ng and hostapd are
> concerned, yes, that has been resolved. However, I
> have not yet merged
> that change into the stable branch of hostapd.
> 
> -- 
> Jouni Malinen                                       
>     PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



From webmaster  Sun Mar  5 13:05:31 2006
From: webmaster (JAK-Software.org)
Date: Sun, 05 Mar 2006 22:05:31 +0100
Subject: wpa_gui.exe: All needed DLLs (7-zip SFX)
Message-ID: <440B529B.80703@jak-software.org>

I have packed all needed DLLs for wpa_gui.exe into 1 SFX.
The File Size is: 3MB
http://www.jak-software.org/pub/utils/www/wpa_gui-dlls.exe

The Files are: 
mingwm10.dll,Qt3Support4.dll,QtCore4.dll,QtGui4.dll,QtNetwork4.dll,QtSql4.dll,QtXml4.dll



From raffaello_  Mon Mar  6 07:09:24 2006
From: raffaello_ (Raffaello)
Date: Mon, 6 Mar 2006 16:09:24 +0100
Subject: Help with TTLS and PAP
Message-ID: <200603061609.24630.raffaello_@fastwebnet.it>

Hi, I'm trying to use wpa_supplicant with a wireless that needs TTLS and PAP 
method autentication, but I have problems. Anyboby can help me?
Thanks.

Raffaello



****************************
This is my .config file:
****************************

CONFIG_DRIVER_HOSTAP=y
#CONFIG_DRIVER_HERMES=y
#CONFIG_DRIVER_MADWIFI=y
CONFIG_DRIVER_ATMEL=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NDISWRAPPER=y
#CONFIG_DRIVER_BROADCOM=y
#CONFIG_DRIVER_IPW=y
#CONFIG_DRIVER_BSD=y
#CONFIG_DRIVER_NDIS=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_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_PAX=y
CONFIG_EAP_LEAP=y
#CONFIG_PCSC=y

****************************
This is wpa_supplicant.conf
P.S. I know that I don't need a certificate for this wlan
****************************

network={
        ssid="Wireless"
        key_mgmt=WPA-EAP
        eap=TTLS
        identity="<my-identity>"
        anonymous_identity=""
        password="<my-password>"
        #ca_cert="/etc/deacacert.pem"
        phase2="auth=PAP"
}

****************************
This is the result of wpa_supplicant -w -c/etc/wpa_supplicant.conf -iwlan0 -dd
****************************

State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:0f:66:ba:f5:6c prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 16
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 367 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:66:ba:f5:6c ssid='Wireless' wpa_ie_len=30 rsn_ie_len=26 caps=0x11
   selected based on RSN IE
Trying to associate with 00:0f:66:ba:f5:6c (SSID='Wireless' freq=2432 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 1
WPA: set AP WPA IE - hexdump(len=30): dd 1c 00 50 f2 01 01 00 00 50 f2 02 02 
00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 01 01 00
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 
04 00 0f ac 02 01 00 00 0f ac 01 01 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 
00 0f ac 04 01 00 00 0f ac 01 00 00
No keys have been configured - skip key clearing
wpa_driver_hostap_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_hostap_associate
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
RSN: added PMKSA cache candidate 00:0f:66:ba:f5:6c prio 1000
RSN: processing PMKSA candidate list
RSN: not in suitable state for new pre-authentication
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request



From shawn_adams  Mon Mar  6 16:20:25 2006
From: shawn_adams (Shawn Adams)
Date: Tue, 07 Mar 2006 01:20:25 +0100
Subject: wpa_supplicant: WPA: EAPOL-Key Replay Counter did not increase
	-	dropping packet
In-Reply-To: <43EF7C59.3070409@web.de>
References: <43EE4517.5030607@caltech.edu> <43EF7C59.3070409@web.de>
Message-ID: <440CD1C9.6020505@web.de>


Did this thread die completely, or have I missed a posted solution ?



Shawn Adams wrote:
> Hello,
> 
> I've got the same issue, strange enough wpa_supplicant 0.5.0 functions
> fine , same access point - Nortel 2220, as long as I use the Dell 1450
> built-in adapter using ndiswrapper with bcmwl5a. it works with both
> WPA-PSK, and WPA-EAP
> 
> If I use the same wpa_supplicant, same /etc/wpa_supplicant.conf, it
> fails using a PCMCIA wireless card using madwifi drivers, which fails
> with both WPA variants.
> 
> only difference is that my card never connects - the "replay counter"
> errors come immediately, and constantly.
> 
> I can echo Joey, I'd be very interested to provide whatever logs, etc..
> are needed.
> 
> 
> Joey Richards wrote:
>> Hello,
>>
>> I am suffering from the same problem as Vidar.  I'm running on an AMD 
>> Turion laptop with kernel 2.6.15-r1 built for x86_64.  My wireless card 
>> is a Broadcom, using the bcmwl5a 64-bit driver through ndiswrapper.  I 
>> connect to a Netgear WGR614 wireless router using WPA-PSK.
>>
>> I have collected two logs -- one is an annotated log from wpa_supplicant 
>> with the -ddt option (search for <<<<< to find my comments).  The other 
>> is the iwevent log from the same period.  These are available at
>> http://www.its.caltech.edu/~joey/wpa_supplicant
>>
>> What you'll see in the logs is my connecting to the access point 
>> (bork-wireless), accompanied by a couple events in the iwevent log. 
>> About 7 minutes later, wpa_supplicant successfully handshakes with no 
>> event in the iwevent log.  Next, about half an hour later, it attempts 
>> to handshake, fails due to the "Replay Counter" error, and repeats until 
>> I noticed the connection had died.  I closed wpa_supplicant and this 
>> caused the final iwevent activity -- reporting a connection to an access 
>> point with address 00:00:00:00:00:00.  There was no activity at all in 
>> the iwevent log after the initial connection until I shut down 
>> wpa_supplicant.
>>
>> Any assistance would be most appreciated, now by two of us.  Please let 
>> me know if there are any other tests I can run that would help with 
>> diagnosis.
>>
>> joey
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
> 
> 


-- 
Shawn Adams
shawn_adams at web.de




From mcgrathl81  Tue Mar  7 09:21:49 2006
From: mcgrathl81 (Larry McGrath)
Date: Tue, 7 Mar 2006 17:21:49 +0000 (GMT)
Subject: modify beacon frame
Message-ID: <20060307172149.96526.qmail@web26912.mail.ukl.yahoo.com>

Hello,
  
  I need to modify the sending beacon frame structure and parameter  values in the hostap code. unsure where to start. I would appreciate  some pointers.
  
  L
		
---------------------------------
Yahoo! Photos ? NEW, now offering a quality print service from just 8p a photo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060307/1ac2622e/attachment.htm 


From jers  Wed Mar  8 03:08:59 2006
From: jers (jers at inwind.it)
Date: Wed,  8 Mar 2006 12:08:59 +0100
Subject: R: Incompatibility hostapd - windows
Message-ID: <IVT2YZ$B9D31D88AA5F44B6EE5C6C5D2E44C476@libero.it>

Hi,

Thanks for your reply. I used the supplicant for windows provided with the WiFi card. It was the cause of my problem. The problem has never occurred by utilizing the Microsoft supplicant.

Unfortunately I have not solved yet the problem with the VoIP phone.
When I try to connect the phone to the AP, the first repeats the steps: Scanning, Associated and IP configuring while the latter prints the following debug as in the follow.


Hostapd AP / WiFi phone debug

Configuration file: hostapd.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:40:f4:e6:29:37 and ssid 'wpa'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0x2
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 06 31 2e 17 eb f7 34 59 33 fa 28 4b 1f fc a9 f9 91 35 90 fe 99 13 8c 1c d5 cc 7a d8 34 63 e7 72
GTK - hexdump(len=32): 11 09 3c 21 83 f4 b2 55 b6 3e 67 2e 93 da 42 b9 2f 32 ed b5 77 d7 65 3b 00 c3 00 1d 0a f0 15 40
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
l2_packet_receive - recvfrom: Network is down
Wireless event: cmd=0x8c03 len=20
  New STA
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:0a:3a:92 key_idx=0
madwifi_set_sta_authorized: addr=00:02:6f:0a:3a:92 authorized=0
WPA: 00:02:6f:0a:3a:92 WPA_PTK_GROUP entering state IDLE
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state AUTHENTICATION
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state AUTHENTICATION2
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state INITPSK
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKSTART
TX EAPOL - hexdump(len=113): 00 02 6f 0a 3a 92 00 40 f4 e6 29 37 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 5d f9 66 ed cf bc aa 17 76 b1 64 9b 57 4c 36 e6 13 56 8e e3 31 76 19 11 16 4e 0a 3c 65 d5 51 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 123 bytes from 00:02:6f:0a:3a:92
   IEEE 802.1X: version=1 type=3 length=119
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): f5 41 0e ab fd 0c 80 69 56 e4 ac d6 f8 25 aa 06 01 54 b9 62 b1 76 a6 54 34 90 b2 5e e3 03 94 61
PTK - hexdump(len=64): d3 2d f3 f4 96 dc 57 32 62 45 19 ae 95 ac 84 5e b9 76 cb 2a 17 12 aa 19 5d 56 e8 b8 ed b7 f4 4a f2 36 3c 2d 85 0f 96 46 a4 98 23 4e fb 96 56 b8 46 1c ea 4a c6 9c d9 d6 af 38 c5 23 03 f9 6a f9
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
TX EAPOL - hexdump(len=137): 00 02 6f 0a 3a 92 00 40 f4 e6 29 37 88 8e 02 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 5d f9 66 ed cf bc aa 17 76 b1 64 9b 57 4c 36 e6 13 56 8e e3 31 76 19 11 16 4e 0a 3c 65 d5 51 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a9 6b 93 1b 11 8e e5 1b fc a0 a9 e8 40 20 ca 0e 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
TX EAPOL - hexdump(len=137): 00 02 6f 0a 3a 92 00 40 f4 e6 29 37 88 8e 02 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 03 5d f9 66 ed cf bc aa 17 76 b1 64 9b 57 4c 36 e6 13 56 8e e3 31 76 19 11 16 4e 0a 3c 65 d5 51 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 0b 9b 8d 3e 8f b7 a4 2a 69 ad e3 d8 b9 f4 29 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
TX EAPOL - hexdump(len=137): 00 02 6f 0a 3a 92 00 40 f4 e6 29 37 88 8e 02 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 04 5d f9 66 ed cf bc aa 17 76 b1 64 9b 57 4c 36 e6 13 56 8e e3 31 76 19 11 16 4e 0a 3c 65 d5 51 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9c 21 f1 e9 e3 e1 a7 b6 4f 56 47 57 e3 d7 49 33 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
TX EAPOL - hexdump(len=137): 00 02 6f 0a 3a 92 00 40 f4 e6 29 37 88 8e 02 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 05 5d f9 66 ed cf bc aa 17 76 b1 64 9b 57 4c 36 e6 13 56 8e e3 31 76 19 11 16 4e 0a 3c 65 d5 51 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 95 4d 4f 20 8b 1a 05 2b 89 e2 93 21 c7 dd 31 eb 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state DISCONNECT
madwifi_sta_deauth: addr=00:02:6f:0a:3a:92 reason_code=2
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state DISCONNECTED
WPA: 00:02:6f:0a:3a:92 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:02:6f:0a:3a:92 key_idx=0
ioctl[unknown???]: Invalid argument
madwifi_set_sta_authorized: addr=00:02:6f:0a:3a:92 authorized=0
ioctl[unknown???]: Invalid argument
Wireless event: cmd=0x8c04 len=20
Wireless event: cmd=0x8c03 len=20
  New STA
... The same again...


You can see that the AP and the phone cannot negotiate the key. The hostapd.conf file is the same I use to connect Windows stations. Moreover I set the same configuration in a commercial AP and the phone can connect to it. So, the windows stations can connect to the hostapd AP; the wifi phone can connect to commercial AP; the wifi phone cannot connect to the hostapd AP.
I do not understand which is the reason of this behavior of the hostapd AP and the WiFi phone.

In the following the hostapd debug when I connect my notebook and the hostapd.conf file: 
Any suggestion is appreciated. 
Bye
Jers



Hostapd AP / notebook debug

  New STA
WPA: 00:20:a6:52:24:9e WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:20:a6:52:24:9e key_idx=0
madwifi_set_sta_authorized: addr=00:20:a6:52:24:9e authorized=0
WPA: 00:20:a6:52:24:9e WPA_PTK_GROUP entering state IDLE
WPA: 00:20:a6:52:24:9e WPA_PTK entering state AUTHENTICATION
WPA: 00:20:a6:52:24:9e WPA_PTK entering state AUTHENTICATION2
WPA: 00:20:a6:52:24:9e WPA_PTK entering state INITPSK
WPA: 00:20:a6:52:24:9e WPA_PTK entering state PTKSTART
TX EAPOL - hexdump(len=113): 00 20 a6 52 24 9e 00 40 f4 e6 29 37 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 ed 81 47 84 af 89 0e 6e 0d 65 2d c3 91 c1 c3 69 dd 59 03 61 42 4b d3 a6 05 07 81 fc 3e c2 75 79 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 5 bytes from 00:20:a6:52:24:9e
   IEEE 802.1X: version=1 type=1 length=0
   ignoring 1 extra octets after IEEE 802.1X packet
IEEE 802.1X: 123 bytes from 00:20:a6:52:24:9e
   IEEE 802.1X: version=1 type=3 length=119
WPA: 00:20:a6:52:24:9e WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): f5 41 0e ab fd 0c 80 69 56 e4 ac d6 f8 25 aa 06 01 54 b9 62 b1 76 a6 54 34 90 b2 5e e3 03 94 61
PTK - hexdump(len=64): f5 27 a3 f3 1f 48 10 c7 1b 01 1a 3b 52 37 32 1a df 0a af 30 7e 09 43 91 dd c2 81 73 0a d0 5a f7 63 1f 82 6e 18 01 2d a0 6f 04 bf 5a d1 db bc 79 d2 4d af 0e 4e 6b ac 7d 9a d9 00 e9 17 1f 77 39
WPA: 00:20:a6:52:24:9e WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:20:a6:52:24:9e WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
TX EAPOL - hexdump(len=137): 00 20 a6 52 24 9e 00 40 f4 e6 29 37 88 8e 02 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 ed 81 47 84 af 89 0e 6e 0d 65 2d c3 91 c1 c3 69 dd 59 03 61 42 4b d3 a6 05 07 81 fc 3e c2 75 79 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7a ad 67 8f e4 cc da bb a8 d1 74 7d 72 55 d3 02 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X: 99 bytes from 00:20:a6:52:24:9e
   IEEE 802.1X: version=1 type=3 length=95
WPA: 00:20:a6:52:24:9e WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=TKIP addr=00:20:a6:52:24:9e key_idx=0
madwifi_set_sta_authorized: addr=00:20:a6:52:24:9e authorized=1
madwifi_sta_clear_stats: addr=00:20:a6:52:24:9e
madwifi_sta_clear_stats: addr=00:20:a6:52:24:9e
WPA: 00:20:a6:52:24:9e WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
Plaintext EAPOL-Key Key Data - hexdump(len=32): ba 3d 03 2b fd 37 79 be 2e 90 b6 59 51 69 d6 af fa 69 3f ec 13 a8 cc 5b 46 22 0e 27 a9 b8 7c e1
TX EAPOL - hexdump(len=145): 00 20 a6 52 24 9e 00 40 f4 e6 29 37 88 8e 02 03 00 7f fe 03 91 00 20 00 00 00 00 00 00 00 03 ed 81 47 84 af 89 0e 6e 0d 65 2d c3 91 c1 c3 69 dd 59 03 61 42 4b d3 a6 05 07 81 fc 3e c2 75 78 dd 59 03 61 42 4b d3 a6 05 07 81 fc 3e c2 75 7a 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 65 15 bd 70 4f e3 be 26 1f f3 58 d3 29 21 30 52 00 20 78 ea 9d 42 f





My hostapd.conf file is
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored

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

# In case of madwifi driver, an additional configuration parameter, bridge,
# must be used to notify hostapd if the interface is included in a bridge. This
# parameter is not used with Host AP driver.
#bridge=br0

# Driver interface type (hostap/wired/madwifi/prism54; default: hostap)
driver=madwifi

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

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

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

# Interface for separate control program. If this is specified, hostapd
# will create this directory and a UNIX domain socket for listening to requests
# from external programs (CLI/GUI, etc.) for status information and
# configuration. The socket file will be named based on the interface name, so
# multiple hostapd processes/interfaces can be run at the same time if more
# than one interface is used.
# /var/run/hostapd is the recommended directory for sockets and by default,
# hostapd_cli will use it when trying to connect with hostapd.
ctrl_interface=/var/run/hostapd

# Access control for the control interface can be configured by setting the
# directory to allow only members of a group to use sockets. This way, it is
# possible to run hostapd as root (since it needs to change network
# configuration and open raw sockets) and still allow GUI/CLI components to be
# run as non-root users. However, since the control interface can be used to
# change the network configuration, this access needs to be protected in many
# cases. By default, hostapd is configured to use gid 0 (root). If you
# want to allow non-root users to use the contron interface, add a new group
# and change this value to match with that group. Add users that should have
# control interface access to this group.
#
# This variable can be a group name or gid.
#ctrl_interface_group=wheel
ctrl_interface_group=0


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

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

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

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

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

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


##### IEEE 802.1X-2004 related configuration ##################################

# Require IEEE 802.1X authorization
#ieee8021x=1

# Optional displayable message sent with EAP Request-Identity. The first \0
# in this string will be converted to ASCII-0 (nul). This can be used to
# separate network info (comma separated list of attribute=value pairs); see,
# e.g., draft-adrangi-eap-network-discovery-07.txt.
#eap_message=hello
#eap_message=hello\0networkid=netw,nasid=foo,portid=0,NAIRealms=example.com

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

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

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

# Use PAE group address (01:80:c2:00:00:03) instead of individual target
# address when sending EAPOL frames with driver=wired. This is the most common
# mechanism used in wired authentication, but it also requires that the port
# is only used by one station.
#use_pae_group_addr=1

##### Integrated EAP server ###################################################

# Optionally, hostapd can be configured to use an integrated EAP server
# to process EAP authentication locally without need for an external RADIUS
# server. This functionality can be used both as a local authentication server
# for IEEE 802.1X/EAPOL and as a RADIUS server for other devices.

# Use integrated EAP server instead of external RADIUS authentication
# server. This is also needed if hostapd is configured to act as a RADIUS
# authentication server.
eap_server=0

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

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

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

# Private key matching with the server certificate for EAP-TLS/PEAP/TTLS
# This may point to the same file as server_cert if both certificate and key
# are included in a single file. PKCS#12 (PFX) file (.p12/.pfx) can also be
# used by commenting out server_cert and specifying the PFX file as the
# private_key.
#private_key=/etc/hostapd.server.prv

# Passphrase for private key
#private_key_passwd=secret passphrase

# Enable CRL verification.
# Note: hostapd does not yet support CRL downloading based on CDP. Thus, a
# valid CRL signed by the CA is required to be included in the ca_cert file.
# This can be done by using PEM format for CA certificate and CRL and
# concatenating these into one file. Whenever CRL changes, hostapd needs to be
# restarted to take the new CRL into use.
# 0 = do not verify CRLs (default)
# 1 = check the CRL of the user certificate
# 2 = check all CRLs in the certificate path
#check_crl=1

# Configuration data for EAP-SIM database/authentication gateway interface.
# This is a text string in implementation specific format. The example
# implementation in eap_sim_db.c uses this as the file name for the GSM
# authentication triplets.
#eap_sim_db=/etc/hostapd.sim_db


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

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


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

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

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

# RADIUS authentication server
#auth_server_addr=127.0.0.1
#auth_server_port=1812
#auth_server_shared_secret=secret

# RADIUS accounting server
#acct_server_addr=127.0.0.1
#acct_server_port=1813
#acct_server_shared_secret=secret

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

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


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


##### RADIUS authentication server configuration ##############################

# hostapd can be used as a RADIUS authentication server for other hosts. This
# requires that the integrated EAP authenticator is also enabled and both
# authentication services are sharing the same configuration.

# File name of the RADIUS clients configuration for the RADIUS server. If this
# commented out, RADIUS server is disabled.
#radius_server_clients=/etc/hostapd.radius_clients

# The UDP port number for the RADIUS authentication server
#radius_server_auth_port=1812

# Use IPv6 with RADIUS server (IPv4 will also be supported using IPv6 API)
#radius_server_ipv6=1


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

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

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

# Optionally, WPA PSKs can be read from a separate text file (containing list
# of (PSK,MAC address) pairs. This allows more than one PSK to be configured.
# Use absolute path name to make sure that the files can be read on SIGHUP
# configuration reloads.
#wpa_psk_file=/etc/hostapd.wpa_psk

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

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

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

# Rekey GTK when any STA that possesses the current GTK is leaving the BSS.
# (dot11RSNAConfigGroupRekeyStrict)
#wpa_strict_rekey=1

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

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

  

> On Mon, Feb 27, 2006 at 12:51:31PM +0100, jers at inwind.it wrote:
> 
> > I carried out a system with a linux AP and Windows clients. 
> The used 
> > security policy is WPA-PSK. In order to do that I have installed 
> > hostapd (working with madwifi) on the AP and the wpa_supplicant for 
> > windows on clients, in accordance with the documentation 
> provided in 
> > hostap site. No problems... the system works very well.
> 
> > But... WHY I need to install wpa_supplicant for Windows? Why the AP 
> > with hostapd and windows clients without wpa_supplicant 
> cannot get the 
> > connection? I have also used commercial APs and I have 
> configured the 
> > same clients in WPA-PSK mode with the normal procedures provided by 
> > Windows/card drivers (so without wpa_supplicant). I have 
> not found any 
> > problem.
> 
> You should not need to use wpa_supplicant on Windows because of this.
> 
> > I know that WPA is standardized, so I cannot suppose that 
> hostapd or 
> > Windows systems use different rules, or not? What is the reason of 
> > this incompatibility between hostapd and Windows?
> 
> I'm not aware of any interoperability issues, i.e., this 
> works fine in my tests. Could you please provide more details 
> of the configuration (including hostapd.conf and madwifi 
> driver version) and send a debug log from hostapd? If this is 
> not enough, it would also be useful to get debug information 
> from the client side. Which supplicant are you using there? Microsoft?
> 
> -- 
> Jouni Malinen                                            PGP 
> id EFC895FA
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.2.0/276 - Release 
> Date: 07/03/2006
>  
> 




From eleghost  Wed Mar  8 03:08:52 2006
From: eleghost (Scott)
Date: Wed, 08 Mar 2006 19:08:52 +0800
Subject: The drawback of WDS
Message-ID: <1141816133.8505.5.camel@localhost>

As I know, the drawback of WDS are many as Link reconvery / low
throughput and solution also many as 802.1D(STP) for link reconvery and
two NIC for low throughput etc.

Does anyone know that did WDS have other drawback with its solution,
thanks.




From eleghost  Wed Mar  8 03:13:55 2006
From: eleghost (Scott)
Date: Wed, 08 Mar 2006 19:13:55 +0800
Subject: my problem
In-Reply-To: <mailman.2595.1141703470.29539.hostap@shmoo.com>
References: <mailman.2595.1141703470.29539.hostap@shmoo.com>
Message-ID: <1141816436.8505.11.camel@localhost>

Sir,
I'm Scott, I was register to subscriber at 3/7 but no mail in my mailbox
so far I received. what's going on? 


Thanks!


? ??2006-03-06 ? 20:51 -0700?hostap-request at shmoo.com ???
> Welcome to the HostAP at shmoo.com mailing list!
> 
> To post to this list, send your email to:
> 
>   hostap at shmoo.com
> 
> General information about the mailing list is at:
> 
>   http://lists.shmoo.com/mailman/listinfo/hostap
> 
> If you ever want to unsubscribe or change your options (eg, switch to
> or from digest mode, change your password, etc.), visit your
> subscription page at:
> 
>   http://lists.shmoo.com/mailman/options/hostap/eleghost%40gmail.com
> 
> You can also make such adjustments via email by sending a message to:
> 
>   HostAP-request at shmoo.com
> 
> with the word `help' in the subject or body (don't include the
> quotes), and you will get back a message with instructions.
> 
> You must know your password to change your options (including changing
> the password, itself) or to unsubscribe.  It is:
> 
>   0950822962
> 
> Normally, Mailman will remind you of your shmoo.com mailing list
> passwords once every month, although you can disable this if you
> prefer.  This reminder will also include instructions on how to
> unsubscribe or change your account options.  There is also a button on
> your options page that will email your current password to you.




From nix.bh.tan  Wed Mar  8 06:02:51 2006
From: nix.bh.tan (nix.bh.tan at sg.pwc.com)
Date: Wed, 8 Mar 2006 22:02:51 +0800
Subject: Nix BH Tan/SG/GTS/PwC is out of the office.
Message-ID: <OF063C03BC.23DC9D3E-ON4825712B.004D2AA1-4825712B.004D2AA1@pwc.com>

I will be out of the office starting  06/03/2006 and will not return until
15/03/2006.

For assistance on network issues, please contact Tan Tiong Hwee @ 4132 .
For assistance on Lotus Notes issues, please contact Mary Heng or Kevin
Juay @ 4137 & 3671 respectively. For assistance on general issues, please
contact the GTS helpdesk @ 7000.
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.




From george  Thu Mar  9 07:12:26 2006
From: george (George Heeres)
Date: Thu, 09 Mar 2006 09:12:26 -0600
Subject: Prism2 Cards: Maximum Distance / Ack Timeout?
Message-ID: <441045DA.5080201@msworldnet.com>

I've got an Access Point running on a MikroTik RouterBoard 532 with a
200mW Prism2 card (NL-2511MP) on a 12 dBi Omni using MikroTik 2.9.10
(was running 2.9.13 but had to downgrade due to OSPF problems) powered
by 48V POE. From what I've been able to determine by looking at the
internal file system, the MikroTik appears to be using the linux-wlan
drivers (although I don't have confirmation of this, nor do I know what
version...or if customized).

I've got two clients, which are running on WRAP.2C boards, with a custom
built Linux operating system (2.6.11.7 kernel) based on uClibc using the
HostAP drivers (CVS checkout from sometime in early 2005). These clients
are running the exact same card as the Access Point (200mW Prism2 card,
NL-2511MP) with a 14 dBi RooTenna powered by 12V POE.

The distances for these two clients from the access point is: 4.79 mi
and 6.51 mi respectively.

Each of these clients is seeing a signal strength of roughly -80/-84
with a -92/-94 noise floor (roughly same signal strengths from both
tower / client). I'm seeing ping times all over the place with dropped
and duplicate packets:

64 bytes from 10.1.18.251: icmp_seq=1 ttl=62 time=6.40 ms
64 bytes from 10.1.18.251: icmp_seq=2 ttl=62 time=60.6 ms
64 bytes from 10.1.18.251: icmp_seq=3 ttl=62 time=55.8 ms
64 bytes from 10.1.18.251: icmp_seq=5 ttl=62 time=106 ms
64 bytes from 10.1.18.251: icmp_seq=5 ttl=62 time=330 ms (DUP!)
64 bytes from 10.1.18.251: icmp_seq=7 ttl=62 time=5.72 ms
64 bytes from 10.1.18.251: icmp_seq=8 ttl=62 time=52.9 ms
64 bytes from 10.1.18.251: icmp_seq=9 ttl=62 time=67.0 ms
64 bytes from 10.1.18.251: icmp_seq=10 ttl=62 time=73.3 ms
64 bytes from 10.1.18.251: icmp_seq=12 ttl=62 time=6.16 ms
64 bytes from 10.1.18.251: icmp_seq=13 ttl=62 time=154 ms
64 bytes from 10.1.18.251: icmp_seq=13 ttl=62 time=217 ms (DUP!)
64 bytes from 10.1.18.251: icmp_seq=14 ttl=62 time=45.9 ms
64 bytes from 10.1.18.251: icmp_seq=15 ttl=62 time=233 ms
64 bytes from 10.1.18.251: icmp_seq=16 ttl=62 time=43.6 ms
64 bytes from 10.1.18.251: icmp_seq=17 ttl=62 time=73.2 ms
64 bytes from 10.1.18.251: icmp_seq=18 ttl=62 time=5.93 ms
64 bytes from 10.1.18.251: icmp_seq=19 ttl=62 time=60.4 ms
64 bytes from 10.1.18.251: icmp_seq=20 ttl=62 time=7.10 ms
64 bytes from 10.1.18.251: icmp_seq=21 ttl=62 time=14.2 ms
64 bytes from 10.1.18.251: icmp_seq=22 ttl=62 time=5.86 ms
64 bytes from 10.1.18.251: icmp_seq=23 ttl=62 time=207 ms
64 bytes from 10.1.18.251: icmp_seq=24 ttl=62 time=84.8 ms

Browsing around online, I found mention from someone regarding ACK
timeouts using the PRISM2 based cards beyond 8 km (4.9 mi). Additional
reading has confirmed that the ACK timeout on the PRISM2 based cards is
fixed. The nature of the problem (duplicate / dropped packets, etc.)
seems to confirm this as the problem.

I'm trying to determine if the ACK timeout is the cause of the problem
or if it's something else before I start replacing cards. Here is what
I'm thinking as potential reasons for the problem:

1.) ACK timeout. Is there anything that can be done or I just need to
use different cards (ie. Atheros based with dynamic / adjustable ACK)
2.) Signal just not strong enough? What should I be shooting for?
3.) Incompatibility between linux-wlan and hostap drivers? (Don't think
so...)

Please help shed some light on this for me. I'm at the limit of my
knowledge regarding wireless. If you need additional information, please
let me know what you need and I'll do my best to make sure you get it.

Thanks
George



From pelusitavali  Thu Mar  9 08:24:53 2006
From: pelusitavali (Pelusa Vali)
Date: Thu, 09 Mar 2006 16:24:53 +0000
Subject: problems compiling wpa_supplicant
Message-ID: <PM.26873.1141921493@pmweb6.uk1.bibliotech.net>

hi everybody, i'm trying to compile wpa_supplicant 0.4.8 to use it with atheros based card,i want to use tls, this is my .config file:

FLAGS += -I/usr/local/ssl/include
LIBS += -L/usr/local/ssl/lib


CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I../usr/src/madwifi-ng-r1457-20060228/
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_TEST=y
CONFIG_DRIVER_WIRED=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_TLS=y
CONFIG_PKCS12=y
CONFIG_EAPOL_TEST=y
CONFIG_CTRL_IFACE=y
CONFIG_BACKEND=file

but when i do make, i get this:

driver_madwifi.c:31:28: include/compat.h: No such file or directory
driver_madwifi.c:32:32: net80211/ieee80211.h: No such file or directory
driver_madwifi.c:38:39: net80211/ieee80211_crypto.h: No such file or directory
driver_madwifi.c:39:38: net80211/ieee80211_ioctl.h: No such file or directory
driver_madwifi.c: In function `set80211priv':
driver_madwifi.c:102: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in this function)
driver_madwifi.c:102: error: (Each undeclared identifier is reported only once
driver_madwifi.c:102: error: for each function it appears in.)
driver_madwifi.c:103: error: `IEEE80211_IOCTL_CHANLIST' undeclared (first use in this function)
driver_madwifi.c: In function `set80211param':
driver_madwifi.c:143: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_set_wpa_ie':
driver_madwifi.c:163: error: `IEEE80211_IOCTL_SETOPTIE' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_del_key':
driver_madwifi.c:174: error: storage size of `wk' isn't known
driver_madwifi.c:180: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:182: error: `IEEE80211_IOCTL_DELKEY' undeclared (first use in this function)
driver_madwifi.c:174: warning: unused variable `wk'
driver_madwifi.c: In function `wpa_driver_madwifi_set_key':
driver_madwifi.c:192: error: storage size of `wk' isn't known
driver_madwifi.c:214: error: `IEEE80211_CIPHER_WEP' undeclared (first use in this function)
driver_madwifi.c:218: error: `IEEE80211_CIPHER_TKIP' undeclared (first use in this function)
driver_madwifi.c:222: error: `IEEE80211_CIPHER_AES_CCM' undeclared (first use in this function)
driver_madwifi.c:247: error: `IEEE80211_KEY_RECV' undeclared (first use in this function)
driver_madwifi.c:250: error: `IEEE80211_KEY_GROUP' undeclared (first use in this function)
driver_madwifi.c:252: error: `IEEE80211_KEY_XMIT' undeclared (first use in this function)
driver_madwifi.c:252: error: `IEEE80211_KEY_DEFAULT' undeclared (first use in this function)
driver_madwifi.c:253: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:261: error: `IEEE80211_IOCTL_SETKEY' undeclared (first use in this function)
driver_madwifi.c:192: warning: unused variable `wk'
driver_madwifi.c: In function `wpa_driver_madwifi_set_countermeasures':
driver_madwifi.c:269: error: `IEEE80211_PARAM_COUNTERMEASURES' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_set_drop_unencrypted':
driver_madwifi.c:278: error: `IEEE80211_PARAM_DROPUNENCRYPTED' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_deauthenticate':
driver_madwifi.c:285: error: storage size of `mlme' isn't known
driver_madwifi.c:288: error: `IEEE80211_MLME_DEAUTH' undeclared (first use in this function)
driver_madwifi.c:290: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:291: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:285: warning: unused variable `mlme'
driver_madwifi.c: In function `wpa_driver_madwifi_disassociate':
driver_madwifi.c:298: error: storage size of `mlme' isn't known
driver_madwifi.c:301: error: `IEEE80211_MLME_DISASSOC' undeclared (first use in this function)
driver_madwifi.c:303: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:304: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:298: warning: unused variable `mlme'
driver_madwifi.c: In function `wpa_driver_madwifi_associate':
driver_madwifi.c:312: error: storage size of `mlme' isn't known
driver_madwifi.c:335: error: `IEEE80211_PARAM_PRIVACY' undeclared (first use in this function)
driver_madwifi.c:339: error: `IEEE80211_PARAM_WPA' undeclared (first use in this function)
driver_madwifi.c:348: error: `IEEE80211_PARAM_ROAMING' undeclared (first use in this function)
driver_madwifi.c:359: error: `IEEE80211_MLME_ASSOC' undeclared (first use in this function)
driver_madwifi.c:360: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:361: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:312: warning: unused variable `mlme'
driver_madwifi.c: In function `wpa_driver_madwifi_set_auth_alg':
driver_madwifi.c:377: error: `IEEE80211_AUTH_AUTO' undeclared (first use in this function)
driver_madwifi.c:379: error: `IEEE80211_AUTH_SHARED' undeclared (first use in this function)
driver_madwifi.c:381: error: `IEEE80211_AUTH_OPEN' undeclared (first use in this function)
driver_madwifi.c:383: error: `IEEE80211_PARAM_AUTHMODE' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_init':
driver_madwifi.c:461: error: `IEEE80211_PARAM_ROAMING' undeclared (first use in this function)
driver_madwifi.c:467: error: `IEEE80211_PARAM_WPA' undeclared (first use in this function)
driver_madwifi.c: In function `wpa_driver_madwifi_deinit':
driver_madwifi.c:493: error: `IEEE80211_PARAM_ROAMING' undeclared (first use in this function)
driver_madwifi.c:497: error: `IEEE80211_PARAM_PRIVACY' undeclared (first use in this function)
driver_madwifi.c:501: error: `IEEE80211_PARAM_WPA' undeclared (first use in this function)
make: *** [driver_madwifi.o] Error 1

i reviewed my madwifi source directory, and many of these files are there.
so, please could you tell what am i doing wrong?
thanks in advance.



_______________________________________________________________ 
Halloween Humour: Why did Dracula divorce his wife after 800 years? 

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=157




From jphstap  Thu Mar  9 11:02:06 2006
From: jphstap (Joe Parks)
Date: Thu, 9 Mar 2006 14:02:06 -0500
Subject: Prism2 Cards: Maximum Distance / Ack Timeout?
In-Reply-To: <441045DA.5080201@msworldnet.com>
References: <441045DA.5080201@msworldnet.com>
Message-ID: <20060309140206.1261706b@scrodconumulus>

On Thu, 09 Mar 2006 09:12:26 -0600
George Heeres <george at msworldnet.com> wrote:

> The distances for these two clients from the access point is: 4.79 mi
> and 6.51 mi respectively.

I've gone over 9 miles without problems (hostap driver at both ends) using directional antennas.
 
> Each of these clients is seeing a signal strength of roughly -80/-84
> with a -92/-94 noise floor (roughly same signal strengths from both
> tower / client). I'm seeing ping times all over the place with dropped
> and duplicate packets:

That Signal to Noise Ratio isn't great.  A directional antenna at one or both ends should help, if you can do that.

Duplicate packets are indeed a sign that the ACK timeout was exceeded, but in your case that is likely because the sender failed to receive or decode the ACK, not that it wasn't fast enough.  And drops are definitely a sign that a packet wasn't received correctly.
 
> Browsing around online, I found mention from someone regarding ACK
> timeouts using the PRISM2 based cards beyond 8 km (4.9 mi). Additional
> reading has confirmed that the ACK timeout on the PRISM2 based cards is
> fixed. The nature of the problem (duplicate / dropped packets, etc.)
> seems to confirm this as the problem.

My understanding of this problem is that it does exist, but manifests in the 12-15 mile range.  The fact that I've gone 9 miles without difficulty supports that notion.

> 1.) ACK timeout. Is there anything that can be done or I just need to
> use different cards (ie. Atheros based with dynamic / adjustable ACK)

A recent wifi record distance setter claimed in an initial press release to have been using prism2 based cards to go some absurd distance.  That may have been an error in the original press release, but if not then they must have figured out a way around that problem.

If anyone knows anything more about this, I too would be interested in the details.

> 2.) Signal just not strong enough? What should I be shooting for?

That would be my guess.  There is info lurking on the web that details the Signal and Signal to Noise Ratios you should be trying for to achieve various throughput rates.  I don't have any links at hand but Google should be able to help you find it.



From george  Thu Mar  9 12:10:24 2006
From: george (George Heeres)
Date: Thu, 09 Mar 2006 14:10:24 -0600
Subject: Prism2 Cards: Maximum Distance / Ack Timeout?
In-Reply-To: <441045DA.5080201@msworldnet.com>
References: <441045DA.5080201@msworldnet.com>
Message-ID: <44108BB0.3060300@msworldnet.com>

Please let me start off by apologizing if this message end's up in a new
thread. I'm subscribed in Digest Mode...and didn't change modes before
receiving your reply... :(

>Joe Parks wrote:
>I've gone over 9 miles without problems (hostap driver at both ends)
>using directional antennas.
>

>From my limited understanding of the PRISM2 chipset, I thought that most
of the functionality was based on the hardware/firmware. If that's the
case, one would assume there shouldn't be any difference between
performance of the linux-wlan driver vs the hostap drivers.

>That Signal to Noise Ratio isn't great. A directional antenna at one or
>both ends should help, if you can do that.
>
>Duplicate packets are indeed a sign that the ACK timeout was exceeded,
>but in your case that is likely because the sender failed to receive or
>decode the ACK, not that it wasn't fast enough.  And drops are
>definitely a sign that a packet wasn't received correctly.
>

Yes. I agree the SNR is not good. From the site survey, if I raise the
client antenna another 10' we get a 6 dB increase...so I will likely
need to do that.

>>1.) ACK timeout.
>My understanding of this problem is that it does exist, but manifests
>in the 12-15 mile range.  The fact that I've gone 9 miles without
>difficulty supports that notion.
>

What's really strange regarding this is that I have several test clients
which have a VERY, VERY poor signal strength (upper -88/-92). These
clients are about 1-2 miles away. Although the pings times occasionally
jump from 5-8ms to 100-200ms, I don't experience DUP packets and rarely
get a DROPPED packet. Perhaps it's a combination of the poor signal
strength along with the distance?

>>2.) Signal just not strong enough? What should I be shooting for?
>That would be my guess. There is info lurking on the web that
>details the Signal and Signal to Noise Ratios you should be trying for
>to achieve various throughput rates.  I don't have any links at hand
>but Google should be able to help you find it.
>

Well, I think I'm going to replace the Prism2 card at the tower first
with an Atheros based card (SR2, powered down to within FCC limits) and
see what happens then. I've recently read brief mentions / suspicions on
the MikroTik forum that the 2.9 version of their OS has poor Prism2
based performance? I can't find much more, nor a definitive answer on
this, than people's comparison of performance under 2.8 vs 2.9 when they
upgraded.

George



From zhangyanfeng  Thu Mar  9 16:48:08 2006
From: zhangyanfeng (zhangyanfeng)
Date: Fri, 10 Mar 2006 08:48:08 +0800
Subject: HostAP Digest, Vol 35, Issue 6
References: <20060308111423.BA3FD5642C5@mail.iocaine.com>
Message-ID: <002b01c643dc$4d0cd2f0$914c1cac@ad.research.nec.com.cn>

Dear all:

I found the "Channel Switch & Transmission Overhead" of Prism II WLAN card 
is very huge, when I tried to make the card switch the association relation 
from old AP to a new one.  the delay is about 30 ms. Could anyone give me 
whether there is any solution for this problem? Thanks a lot!



Best Regards,

---------------------------------------------------------
Leonard 




From ramalhais  Thu Mar  9 17:57:51 2006
From: ramalhais (Pedro Ramalhais)
Date: Fri, 10 Mar 2006 01:57:51 +0000
Subject: PATCH RFC: wpa_supplicant influencing device operstate
In-Reply-To: <200603040004.55477.stefan@loplof.de>
References: <200603040004.55477.stefan@loplof.de>
Message-ID: <4410DD1F.4020905@serrado.net>

Stefan Rompf wrote:
> Hi,
> 
> some weeks ago, there has been a quite heated discussion on linux-netdev about 
> extending functionality of netif_carrier_on()/off(). In the end, a patch 
> written by me has been applied for 2.6.17. For an overview, see the 
> documentation at http://www.flamewarmaster.de/software/operstates.txt . The 
> patch itself (applies to 2.6.14+) can be found on this site too. Main point 
> concerning this list is that it allows an userspace supplicant to signal the 
> kernel when the interface is ready for user traffic after authentication, and 
> afterwards, kernel notifies other programs via the existing IFF_RUNNING 
> interface.
> 
> The quagga routing daemon, vrrpd and my new dhcp client 
> (http://www.flamewarmaster.de/software/dhcpclient/) can act on these 
> messages.
> 
> I have attached a patch against wpa_supplicant 0.5.1 to this mail that 
> implements signalling functionality in the WEXT driver. Note that I haven't 
> tested how this affects drivers that rely on WEXT functionality - this is a 
> very first version.
> 
> With this extension, I can start wpa_supplicant and my DHCP client in 
> parallel. Whenever the supplicant has completed association, and WPA 
> authentication if needed, the DHCP client will automatically update the 
> interface IP configuration. Together with a graphical wpa_cli (will try 
> wpa_gui), this increases usability of wireless LANs a lot. In the long run, 
> I'd like this feature to be added to wpa_supplicant.
> 
> Thoughts?
> 
> Stefan
> 
> 
> ------------------------------------------------------------------------
> 
> diff -x '*.o' -x '*.d' -x '*~' -x wpa_cli -x wpa_passphrase -x wpa_supplicant -upr wpa_supplicant-0.5.1.orig/driver.h wpa_supplicant-0.5.1/driver.h
> --- wpa_supplicant-0.5.1.orig/driver.h	2005-10-15 17:36:32.000000000 +0200
> +++ wpa_supplicant-0.5.1/driver.h	2006-03-03 20:03:44.000000000 +0100
> @@ -554,6 +554,13 @@ struct wpa_driver_ops {
>  	 */
>  	int (*send_eapol)(void *priv, const u8 *dest, u16 proto,
>  			  const u8 *data, size_t data_len);
> +
> +	/**
> +	 * set_operstate - Sets device operating state to DORMANT or UP
> +	 * @priv: private driver interface data
> +	 * @state: 0 = dormant, 1 = up
> +	 */
> +	void (*set_operstate)(void *priv, int state); 
>  };
>  
>  #endif /* DRIVER_H */
> diff -x '*.o' -x '*.d' -x '*~' -x wpa_cli -x wpa_passphrase -x wpa_supplicant -upr wpa_supplicant-0.5.1.orig/driver_wext.c wpa_supplicant-0.5.1/driver_wext.c
> --- wpa_supplicant-0.5.1.orig/driver_wext.c	2006-01-30 05:11:48.000000000 +0100
> +++ wpa_supplicant-0.5.1/driver_wext.c	2006-03-03 23:48:09.000000000 +0100
> @@ -47,11 +47,14 @@ struct wpa_driver_wext_data {
>  	struct wpa_driver_capa capa;
>  	int has_capability;
>  	int we_version_compiled;
> +	int operstate;
>  };
>  
>  
>  static int wpa_driver_wext_flush_pmkid(void *priv);
>  static int wpa_driver_wext_get_range(void *priv);
> +static void wpa_driver_wext_send_oper_ifla(struct wpa_driver_wext_data *drv,
> +					   char linkmode, char operstate);
>  
>  
>  static int wpa_driver_wext_set_auth_param(struct wpa_driver_wext_data *drv,
> @@ -559,6 +562,15 @@ static void wpa_driver_wext_event_rtm_ne
>  		return;
>  	}
>  
> +	/* some drivers send the association event before the operup event - 
> +	   in this case, lifting operstate in wpa_driver_wext_set_operstate()
> +	   fails. This will hit us when wpa_supplicant doesn't need to do
> +	   802.1X authentication */
> +	if (drv->ifindex == ifi->ifi_index && drv->operstate == 1 &&
> +	    (ifi->ifi_flags & (IFF_LOWER_UP | IFF_DORMANT)) == IFF_LOWER_UP &&
> +	    !(ifi->ifi_flags & IFF_RUNNING))
> +		wpa_driver_wext_send_oper_ifla(drv, -1, IF_OPER_UP);
> +
>  	nlmsg_len = NLMSG_ALIGN(sizeof(struct ifinfomsg));
>  
>  	attrlen = h->nlmsg_len - nlmsg_len;
> @@ -794,6 +806,8 @@ void * wpa_driver_wext_init(void *ctx, c
>  		wpa_driver_wext_alternative_ifindex(drv, ifname2);
>  	}
>  
> +	wpa_driver_wext_send_oper_ifla(drv, 1, IF_OPER_DORMANT);
> +
>  	return drv;
>  }
>  
> @@ -816,6 +830,8 @@ void wpa_driver_wext_deinit(void *priv)
>  	 */
>  	wpa_driver_wext_set_bssid(drv, (u8 *) "\x00\x00\x00\x00\x00\x00");
>  
> +	wpa_driver_wext_send_oper_ifla(priv, 0, IF_OPER_UP);
> +
>  	eloop_unregister_read_sock(drv->event_sock);
>  
>  	if (wpa_driver_wext_get_ifflags(drv, &flags) == 0)
> @@ -1759,6 +1775,57 @@ int wpa_driver_wext_alternative_ifindex(
>  }
>  
>  
> +static void wpa_driver_wext_send_oper_ifla(struct wpa_driver_wext_data *drv,
> +					   char linkmode, char operstate) {
> +	struct {
> +		struct nlmsghdr hdr;
> +		struct ifinfomsg ifinfo;
> +		char opts[16];
> +	} req;
> +	struct rtattr *rta;
> +	static int nl_seq;
> +
> +	req.hdr.nlmsg_len = NLMSG_LENGTH(sizeof(struct ifinfomsg));
> +	req.hdr.nlmsg_type = RTM_SETLINK;
> +	req.hdr.nlmsg_flags = NLM_F_REQUEST;
> +	req.hdr.nlmsg_seq = ++nl_seq;
> +	req.hdr.nlmsg_pid = 0;
> +
> +	req.ifinfo.ifi_family = AF_UNSPEC;
> +        req.ifinfo.ifi_type = 0;
> +        req.ifinfo.ifi_index = drv->ifindex;
> +        req.ifinfo.ifi_flags = 0;
> +        req.ifinfo.ifi_change = 0;
> +
> +	if (linkmode != -1) {
> +		rta = (struct rtattr *)((char *)&req + NLMSG_ALIGN(req.hdr.nlmsg_len));
> +		rta->rta_type = IFLA_LINKMODE;
> +		rta->rta_len = RTA_LENGTH(sizeof(char));
> +		*((char *)RTA_DATA(rta)) = linkmode;
> +		req.hdr.nlmsg_len = NLMSG_ALIGN(req.hdr.nlmsg_len) + RTA_LENGTH(sizeof(char));
> +	}
> +	if (operstate != -1) {
> +		rta = (struct rtattr *)((char *)&req + NLMSG_ALIGN(req.hdr.nlmsg_len));
> +		rta->rta_type = IFLA_OPERSTATE;
> +		rta->rta_len = RTA_LENGTH(sizeof(char));
> +		*((char *)RTA_DATA(rta)) = operstate;
> +		req.hdr.nlmsg_len = NLMSG_ALIGN(req.hdr.nlmsg_len) + RTA_LENGTH(sizeof(char));
> +	}
> +
> +	printf("Operstate: linkmode=%d, operstate=%d\n", linkmode, operstate);
> +
> +	(void)send(drv->event_sock, &req, req.hdr.nlmsg_len, 0);
> +}
> +
> +
> +static void wpa_driver_wext_set_operstate(void *priv, int state) {
> +	struct wpa_driver_wext_data *drv = priv;
> +
> +	drv->operstate = state;
> +	wpa_driver_wext_send_oper_ifla(drv, -1, state?IF_OPER_UP:IF_OPER_DORMANT);
> +}
> +
> +
>  const struct wpa_driver_ops wpa_driver_wext_ops = {
>  	.name = "wext",
>  	.desc = "Linux wireless extensions (generic)",
> @@ -1780,4 +1847,5 @@ const struct wpa_driver_ops wpa_driver_w
>  	.remove_pmkid = wpa_driver_wext_remove_pmkid,
>  	.flush_pmkid = wpa_driver_wext_flush_pmkid,
>  	.get_capa = wpa_driver_wext_get_capa,
> +	.set_operstate = wpa_driver_wext_set_operstate,
>  };
> diff -x '*.o' -x '*.d' -x '*~' -x wpa_cli -x wpa_passphrase -x wpa_supplicant -upr wpa_supplicant-0.5.1.orig/priv_netlink.h wpa_supplicant-0.5.1/priv_netlink.h
> --- wpa_supplicant-0.5.1.orig/priv_netlink.h	2005-06-18 19:39:36.000000000 +0200
> +++ wpa_supplicant-0.5.1/priv_netlink.h	2006-03-03 23:26:45.000000000 +0100
> @@ -20,18 +20,36 @@
>   * library, etc..
>   */
>  
> +#ifndef IFF_LOWER_UP
> +#define IFF_LOWER_UP   0x10000         /* driver signals L1 up         */
> +#endif
> +#ifndef IFF_DORMANT
> +#define IFF_DORMANT    0x20000         /* driver signals dormant       */
> +#endif
> +
>  #ifndef IFLA_IFNAME
>  #define IFLA_IFNAME 3
>  #endif
>  #ifndef IFLA_WIRELESS
>  #define IFLA_WIRELESS 11
>  #endif
> +#ifndef IFLA_OPERSTATE
> +#define IFLA_OPERSTATE 16
> +#endif
> +#ifndef IFLA_LINKMODE
> +#define IFLA_LINKMODE 17
> +#define IF_OPER_DORMANT 5
> +#define IF_OPER_UP 6
> +#endif
> +
> +#define NLM_F_REQUEST 1
>  
>  #define NETLINK_ROUTE 0
>  #define RTMGRP_LINK 1
>  #define RTM_BASE 0x10
>  #define RTM_NEWLINK (RTM_BASE + 0)
>  #define RTM_DELLINK (RTM_BASE + 1)
> +#define RTM_SETLINK (RTM_BASE + 3)
>  
>  #define NLMSG_ALIGNTO 4
>  #define NLMSG_ALIGN(len) (((len) + NLMSG_ALIGNTO - 1) & ~(NLMSG_ALIGNTO - 1))
> @@ -46,6 +64,9 @@
>  #define RTA_NEXT(rta,attrlen) \
>  ((attrlen) -= RTA_ALIGN((rta)->rta_len), \
>  (struct rtattr *) (((char *)(rta)) + RTA_ALIGN((rta)->rta_len)))
> +#define RTA_LENGTH(len) (RTA_ALIGN(sizeof(struct rtattr)) + (len))
> +#define RTA_DATA(rta)   ((void*)(((char*)(rta)) + RTA_LENGTH(0)))
> +
>  
>  
>  struct sockaddr_nl
> diff -x '*.o' -x '*.d' -x '*~' -x wpa_cli -x wpa_passphrase -x wpa_supplicant -upr wpa_supplicant-0.5.1.orig/wpa_supplicant.c wpa_supplicant-0.5.1/wpa_supplicant.c
> --- wpa_supplicant-0.5.1.orig/wpa_supplicant.c	2006-01-30 05:24:58.000000000 +0100
> +++ wpa_supplicant-0.5.1/wpa_supplicant.c	2006-03-03 20:20:15.000000000 +0100
> @@ -706,9 +706,11 @@ void wpa_supplicant_set_state(struct wpa
>  			MAC2STR(wpa_s->bssid), wpa_s->reassociated_connection ?
>  			"(reauth)" : "(auth)");
>  		wpa_s->reassociated_connection = 1;
> +		wpa_drv_set_operstate(wpa_s, 1);
>  	} else if (state == WPA_DISCONNECTED || state == WPA_ASSOCIATING ||
>  		   state == WPA_ASSOCIATED) {
>  		wpa_s->new_connection = 1;
> +		wpa_drv_set_operstate(wpa_s, 0);
>  	}
>  	wpa_s->wpa_state = state;
>  }
> diff -x '*.o' -x '*.d' -x '*~' -x wpa_cli -x wpa_passphrase -x wpa_supplicant -upr wpa_supplicant-0.5.1.orig/wpa_supplicant_i.h wpa_supplicant-0.5.1/wpa_supplicant_i.h
> --- wpa_supplicant-0.5.1.orig/wpa_supplicant_i.h	2005-11-28 05:44:50.000000000 +0100
> +++ wpa_supplicant-0.5.1/wpa_supplicant_i.h	2006-03-03 20:05:17.000000000 +0100
> @@ -484,4 +484,10 @@ static inline int wpa_drv_send_eapol(str
>  	return -1;
>  }
>  
> +static inline void wpa_drv_set_operstate(struct wpa_supplicant *wpa_s,
> +					 int state)
> +{
> +	if (wpa_s->driver->set_operstate)
> +		wpa_s->driver->set_operstate(wpa_s->drv_priv, state);
> +}
>  #endif /* WPA_SUPPLICANT_I_H */
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

I think those are great news.
Maybe someone might want to look into adding it to the wired driver too.
I'm assuming that using wpa_supplicant for 802.1X via wired works.
Thanks for your effort!
-- 
Pedro Ramalhais



From andreas.nolda  Fri Mar 10 00:58:23 2006
From: andreas.nolda (Andreas Nolda)
Date: Fri, 10 Mar 2006 09:58:23 +0100
Subject: No wifi0 after bootup
Message-ID: <200603100958.23899.andreas.nolda@staff.hu-berlin.de>

Hi everybody,

I have the following issue. After bootup I have a wlan0 interface, 
but no wifi0 interface; pinging the AP does not work. Reloading the 
hostap modules manually, however, fixes the problem: I get both 
interfaces and can ping the AP.

I am running Kubuntu Breezy on a Thinkpad T23 with an IBM High Rate 
Wireless LAN mini-PCI card. My /etc/network/interfaces file contains:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

mapping hotplug
	script grep
	map wlan0

iface eth0 inet static
address 141.20.148.224
netmask 255.255.254.0

iface wlan0 inet static
address 192.168.0.2
netmask 255.255.255.0
wireless-mode managed
wireless-essid XXXXXXXX
wireless-key restricted XXXXXXXXXXXXXXXXXXXXXXXXXX
gateway 192.168.0.1

orinoco_pci being blacklisted in /etc/hotplug/blacklist.d/local, the 
following hostap modules have been loaded after bootup:

hostap
hostap_pci
hostap_crypt_wep

The output of ifconfig lists a wlan0 interface, but no wifi0 
interface:

irda0     Link encap:IrLAP  HWaddr 00:00:00:00  
          UP RUNNING NOARP  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:8 
          RX bytes:0 (0.0 b)  TX bytes:3988 (3.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:868 (868.0 b)  TX bytes:868 (868.0 b)

wlan0     Link encap:UNSPEC  HWaddr 
00-20-E0-89-93-DE-00-00-00-00-00-00-00-00-00-00  
          inet addr:192.168.0.2  Bcast:192.168.0.255  
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:24 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Memory:d8ac2000-d8ac3000 

And iwconfig outputs both a wlan0 and a wlan1 interface:

wlan0     IEEE 802.11b  ESSID:"XXXXXXXX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 
00:03:C9:8B:C3:B9   
          Bit Rate:2 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security 
mode:restricted
          Power Management:off
          
wlan1     IEEE 802.11b  ESSID:"XXXXXXXX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 
00:03:C9:8B:C3:B9   
          Bit Rate:2 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security 
mode:restricted
          Power Management:off
          Link Quality=46/70  Signal level=-49 dBm  Noise level=-96 
dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:61   Missed beacon:0

So pinging the AP does not work.

The relevant syslog part is:

Mar 10 08:56:43 localhost kernel: [4294704.105000] hostap_crypt: 
registered algorithm 'NULL'
Mar 10 08:56:43 localhost kernel: [4294704.132000] hostap_pci: 0.4.1 - 
2005-05-22 (Jouni Malinen <jkmaline at cc.hut.fi>)
Mar 10 08:56:43 localhost kernel: [4294704.139000] ACPI: PCI Interrupt 
0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Mar 10 08:56:43 localhost kernel: [4294704.146000] hostap_pci: 
Registered netdevice wifi0
Mar 10 08:56:43 localhost kernel: [4294704.146000] wifi0: Original COR 
value: 0x21
Mar 10 08:56:43 localhost kernel: [4294704.345000] prism2_hw_init: 
initialized in 195 ms
Mar 10 08:56:43 localhost kernel: [4294704.346000] wifi0: NIC: 
id=0x8013 v1.0.0
Mar 10 08:56:43 localhost kernel: [4294704.346000] wifi0: PRI: id=0x15 
v1.1.1
Mar 10 08:56:43 localhost kernel: [4294704.346000] wifi0: STA: id=0x1f 
v1.7.4
Mar 10 08:56:43 localhost kernel: [4294704.350000] wifi0: Intersil 
Prism2.5 PCI: mem=0xec000000, irq=11
Mar 10 08:56:43 localhost kernel: [4294704.356000] wifi0: registered 
netdevice wlan0
[...]
Mar 10 08:56:43 localhost kernel: [4294706.690000] irda_init()
Mar 10 08:56:43 localhost kernel: [4294706.690000] NET: Registered 
protocol family 23
Mar 10 08:56:43 localhost kernel: [4294707.546000] ip_tables: (C) 
2000-2002 Netfilter core team
Mar 10 08:56:43 localhost kernel: [4294707.587000] ip_conntrack 
version 2.1 (3067 buckets, 24536 max) - 248 bytes per conntrack
Mar 10 08:56:43 localhost kernel: [4294709.278000] prism2: wlan0: 
operating mode changed 3 -> 2
Mar 10 08:56:43 localhost kernel: [4294709.309000] hostap_crypt: 
registered algorithm 'WEP'
Mar 10 08:56:43 localhost kernel: [4294709.782000] wlan0: LinkStatus=1 
(Connected)
Mar 10 08:56:43 localhost kernel: [4294709.782000] wlan0: LinkStatus: 
BSSID=00:03:c9:8b:c3:b9
Mar 10 08:56:43 localhost kernel: [4294710.582000] pnp: Device 00:0b 
disabled.
Mar 10 08:56:43 localhost kernel: [4294710.583000] pnp: Device 00:0b 
activated.
[...]
Mar 10 08:56:58 localhost kernel: [4294729.749000] wlan0: invalid 
skb->cb magic (0x00000000, expected 0xf08a36a2)

After reloading the hostap modules, however, everything is fine. Now 
the output of ifconfig is:

irda0     Link encap:IrLAP  HWaddr 00:00:00:00  
          UP RUNNING NOARP  MTU:2048  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:8 
          RX bytes:0 (0.0 b)  TX bytes:15800 (15.4 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1599 (1.5 KiB)  TX bytes:1599 (1.5 KiB)

wifi0     Link encap:UNSPEC  HWaddr 
00-20-E0-89-93-DE-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1083 (1.0 KiB)  TX bytes:1351 (1.3 KiB)
          Interrupt:11 Memory:d8b2c000-d8b2d000 

wlan0     Link encap:Ethernet  HWaddr 00:20:E0:89:93:DE  
          inet addr:192.168.0.2  Bcast:192.168.0.255  
Mask:255.255.255.0
          inet6 addr: fe80::220:e0ff:fe89:93de/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:921 (921.0 b)  TX bytes:1351 (1.3 KiB)
          Interrupt:11 Memory:d8b2c000-d8b2d000 

And iwconfig outputs:

wifi0     IEEE 802.11b  ESSID:"XXXXXXXX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 
00:03:C9:8B:C3:B9   
          Bit Rate:11 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security 
mode:restricted
          Power Management:off
          
wlan0     IEEE 802.11b  ESSID:"XXXXXXXX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 
00:03:C9:8B:C3:B9   
          Bit Rate:11 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security 
mode:restricted
          Power Management:off
          Link Quality=48/70  Signal level=-47 dBm  Noise level=-96 
dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:11   Missed beacon:0

The corresponding syslog part is:

Mar 10 08:58:45 localhost kernel: [4294836.578000] wlan0: LinkStatus=1 
(Connected)
Mar 10 08:58:45 localhost kernel: [4294836.579000] wlan0: LinkStatus: 
BSSID=00:03:c9:8b:c3:b9
[...]
Mar 10 08:58:50 localhost kernel: [4294842.144000] wlan0: invalid 
skb->cb magic (0x00000000, expected 0xf08a36a2)
[...]
Mar 10 08:59:40 localhost kernel: [4294891.346000] wlan0: Original COR 
value: 0x21
Mar 10 08:59:40 localhost kernel: [4294891.369000] ACPI: PCI interrupt 
for device 0000:02:02.0 disabled
Mar 10 08:59:40 localhost kernel: [4294891.372000] hostap_pci: Driver 
unloaded
Mar 10 08:59:48 localhost kernel: [4294899.295000] hostap_crypt: 
unregistered algorithm 'WEP'
Mar 10 08:59:48 localhost kernel: [4294899.305000] hostap_crypt: 
unregistered algorithm 'NULL' (deinit)
Mar 10 08:59:56 localhost kernel: [4294907.597000] hostap_crypt: 
registered algorithm 'NULL'
Mar 10 08:59:56 localhost kernel: [4294907.613000] hostap_pci: 0.4.1 - 
2005-05-22 (Jouni Malinen <jkmaline at cc.hut.fi>)
Mar 10 08:59:56 localhost kernel: [4294907.622000] ACPI: PCI Interrupt 
0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Mar 10 08:59:56 localhost kernel: [4294907.630000] hostap_pci: 
Registered netdevice wifi0
Mar 10 08:59:56 localhost kernel: [4294907.630000] wifi0: Original COR 
value: 0x0
Mar 10 08:59:56 localhost kernel: [4294907.829000] prism2_hw_init: 
initialized in 195 ms
Mar 10 08:59:56 localhost kernel: [4294907.830000] wifi0: NIC: 
id=0x8013 v1.0.0
Mar 10 08:59:56 localhost kernel: [4294907.831000] wifi0: PRI: id=0x15 
v1.1.1
Mar 10 08:59:56 localhost kernel: [4294907.831000] wifi0: STA: id=0x1f 
v1.7.4
Mar 10 08:59:56 localhost kernel: [4294907.835000] wifi0: Intersil 
Prism2.5 PCI: mem=0xec000000, irq=11
Mar 10 08:59:56 localhost kernel: [4294907.843000] wifi0: registered 
netdevice wlan0
Mar 10 08:59:56 localhost kernel: [4294907.989000] prism2: wlan0: 
operating mode changed 3 -> 2
Mar 10 08:59:56 localhost kernel: [4294908.008000] hostap_crypt: 
registered algorithm 'WEP'
Mar 10 08:59:56 localhost kernel: [4294908.052000] wifi0: TXEXC - 
status=0x0004 ([Discon]) tx_control=000c
Mar 10 08:59:56 localhost kernel: [4294908.052000]    retry_count=0 
tx_rate=0 fc=0x4108 (Data::0 ToDS)
Mar 10 08:59:56 localhost kernel: [4294908.052000]    
A1=00:00:00:00:00:00 A2=00:20:e0:89:93:de A3=33:33:00:00:00:16 
A4=00:00:00:00:00:00
Mar 10 08:59:57 localhost kernel: [4294908.624000] wifi0: LinkStatus=1 
(Connected)
Mar 10 08:59:57 localhost kernel: [4294908.624000] wifi0: LinkStatus: 
BSSID=00:03:c9:8b:c3:b9

Any ideas?

Andreas Nolda



From ged  Fri Mar 10 02:09:58 2006
From: ged (G.W. Haywood)
Date: Fri, 10 Mar 2006 10:09:58 +0000 (GMT)
Subject: Prism2 Cards: Maximum Distance / Ack Timeout?
In-Reply-To: <20060310005336.27D9F1342CF@mail.iocaine.com>
References: <20060310005336.27D9F1342CF@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0603100941350.13741@mail3.jubileegroup.co.uk>

Hi there,

On Thu, 9 Mar 2006 George Heeres wrote:

> >>2.) Signal just not strong enough? What should I be shooting for?
> >That would be my guess. There is info lurking on the web...
>
> Well, I think I'm going to replace the Prism2 card at the tower first...
> see what happens then. I've recently read brief mentions / suspicions on
> the MikroTik forum that the 2.9 version of their OS has poor Prism2
> based performance?

As you'll see from

http://www.jubileegroup.co.uk/radio/tree_trimmings.gif

I routinely work with signal strengths less than you're getting, but
only over a 700 metre link.  At less than 90dB the performance is down
to 1Mbit/s but apart from that I've no other complaints.  I do see a
few duplicate packets and the occasional dropped one, nothing serious.

Don't forget that you should aim to get a substantial 'margin' above
what you really need for the application to allow for deterioration in
conditions.  You'll be very disappointed if this all works only until
the leaves come out in the spring (or only when it isn't snowing... :)
http://www.jubileegroup.co.uk/radio/powerbudget.html

I haven't seen any reference to firmware in this thread.  I've seen a
few comments that significant performance improvements can be had by
upgrading from certain versions.  I don't have any links for you but
if you Google around the archives of this List over the last three
years or so I'm sure you'll come with something.  I had problems with
the firmware which was supplied with the MA311 cards that I use, and I
now run 1.7.4 or 1.8.4 on them (either flashed or loaded into the
card's RAM at boot, itdoesn't matter).

--

73,
Ged.



From zephyr  Fri Mar 10 04:25:29 2006
From: zephyr (zephyr at bredband.net)
Date: Fri, 10 Mar 2006 13:25:29 +0100
Subject: Could not connect to kernel driver.
Message-ID: <20060310122529.IJPZ16061.mxfep01.bredband.com@mxfep01>

I have seen a couple more people having this problem, but no solution so far. I have gentoo 2.6.15-r1, latest wireless-tools + madwifi-driver + tools + hostapd from portage(~x86). When hostapd is started, it recons the ath0 IF by telling the mac-address and ssid, but then things go wrong..:

ioctl[unknown???]: Operation not supported
Could not connect to kernel driver.

..and then it quits. I tested to not having ath0 loaded, then hostapd say there's no driver, and also by changing the IF to wired, which works just fine. Can it be madwifi that screw things up for hostapd?

/Mikael




From brix  Fri Mar 10 07:49:48 2006
From: brix (Henrik Brix Andersen)
Date: Fri, 10 Mar 2006 16:49:48 +0100
Subject: WPA-PSK CCMP failure in master mode with linux-2.6.15
In-Reply-To: <20060111182811.GB5194@osgiliath.brixandersen.dk>
References: <20060111182811.GB5194@osgiliath.brixandersen.dk>
Message-ID: <20060310154948.GA8408@osgiliath.brixandersen.dk>

On Wed, Jan 11, 2006 at 07:28:11PM +0100, Henrik Brix Andersen wrote:
> I've tried to get the in-kernel hostap_pci driver in linux-2.6.15 to
> work as a WPA-PSK CCMP enabled AP in master mode along with
> hostapd-0.5.0, so far without luck.
> 
> I am using an IPW2915 (ipw2200) as STA and a prism2.5 based miniPCI
> card as AP. The exact same configuration works fine with the external
> hostap-driver-0.4.7 and hostapd-0.5.0.
> 
> I keep getting "IEEE 802.11: deauthenticated due to local deauth
> request", but I can not seem to find out why...

I've just tried with linux-2.6.16-rc5 and the in-kernel version of the
hostap-driver - works like it should.

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


From siretart  Fri Mar 10 13:45:47 2006
From: siretart (Reinhard Tartler)
Date: Fri, 10 Mar 2006 21:45:47 +0000 (UTC)
Subject: WPA Python Bindings
References: <1141424589.2509.18.camel@localhost.localdomain>
Message-ID: <slrne13ssb.q3l.siretart@hermes.olymp.tauware.de>

Jeremy Moles wrote:
> We are developing a PyGTK based GUI for our customers to finally,
> once-and-for-all, smash wireless issues.

I think this sounds very interesting. Does your project already has a
name? What usecases do you intend to support?

> I've written a sensible set of Python bindings for both libiw and
> wpa_supplicant, both of which are freely available to anyone who might
> be interested.
>
> pywpa --> http://downloads.emperorlinux.com/contrib/pywpa
> pyiw  --> http://downloads.emperorlinux.com/contrib/pyiw

I've taken a short glance at it, both look interesting. Just a side
note: You didn't specify under which licence your work is released.
Could you please fix that?

> (I chose not to simply devote time to improving NetworkManager--the
> other killer app--since it's written in C. Even though I'm a C
> programmer, you just don't get work done fast that way.)

NetworkManager focuses on easy roaming use cases, and gets quickly quite
inflexible when the network configuration gets more complex. Perhaps you
can do better with an implementation in python?

Greetings,
	Reinhard





From brix  Sat Mar 11 10:07:28 2006
From: brix (Henrik Brix Andersen)
Date: Sat, 11 Mar 2006 19:07:28 +0100
Subject: Group key renewal problem
Message-ID: <20060311180728.GA30840@osgiliath.brixandersen.dk>

Hi,

I've just upgraded my HostAP based access point to linux-2.6.16-rc5 to
try out the in-kernel hostap_pci driver.

After the upgrade, my clients are disconnected at each group key
renewal, with the following messages spewed in the system log
(hostap-0.4.7 client):

Mar 11 18:58:48 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 18:58:48 fangorn wifi0: decryption failed (SA=00:02:6f:37:fc:68) res=-2
Mar 11 18:58:49 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 18:58:49 fangorn wifi0: decryption failed (SA=00:02:6f:37:fc:68) res=-2
Mar 11 18:58:50 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 18:58:50 fangorn wifi0: decryption failed (SA=00:02:6f:37:fc:68) res=-2
Mar 11 18:58:51 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 18:58:51 fangorn wifi0: decryption failed (SA=00:02:6f:37:fc:68) res=-2
Mar 11 18:58:51 fangorn wifi0: LinkStatus=2 (Disconnected)
Mar 11 18:58:51 fangorn wifi0: LinkStatus: BSSID=00:02:6f:37:fc:68

(ipw2200-1.1.1 client):

Mar 11 19:00:48 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 19:00:49 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 19:00:50 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68
Mar 11 19:00:51 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68

After a few seconds, wpa_supplicant reauthenticates with the AP, and
everything works until the next group key renewal kicks in. I'm using
hostapd-0.5.1 and wpa_supplicant-0.5.1 with WPA2-PSK CCMP.

Any idea as to how I can debug this further?

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


From msmith  Sat Mar 11 12:07:10 2006
From: msmith (Michael Smith)
Date: Sat, 11 Mar 2006 15:07:10 -0500 (EST)
Subject: madwifi-ng trunk rev for hostapd/wpa_supp 0.4.8
Message-ID: <Pine.LNX.4.61.0603111502430.4145@juice.ott.cti.com>

Hey,

Is anyone having success with hostapd/wpa_supplicant 0.4.8 and madwifi-ng? 
I'm about to switch from madwifi-old (new chipset requires ng) and I'm 
wondering whether I should go with a recent madwifi-ng snapshot, or one 
from closer to Feb 8 when 0.4.8 was released.

Thanks
Mike



From jkmaline  Sat Mar 11 12:23:19 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 11 Mar 2006 12:23:19 -0800
Subject: Group key renewal problem
In-Reply-To: <20060311180728.GA30840@osgiliath.brixandersen.dk>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
Message-ID: <20060311202319.GC9371@jm.kir.nu>

On Sat, Mar 11, 2006 at 07:07:28PM +0100, Henrik Brix Andersen wrote:

> After the upgrade, my clients are disconnected at each group key
> renewal, with the following messages spewed in the system log
> (hostap-0.4.7 client):
> 
> Mar 11 18:58:48 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68

> (ipw2200-1.1.1 client):
> 
> Mar 11 19:00:48 fangorn CCMP: received packet without ExtIV flag from 00:02:6f:37:fc:68

Is that 00:02:6f:37:fc:68 the MAC address of your AP? If yes, it sounds
like the AP starts using incorrect encryption for broadcast/multicast
packets (WEP?) after rekeying. You could verify what kind of encryption
the AP is using by looking at /proc/net/hostap/wlan0/crypt before and
after rekeying.

-- 
Jouni Malinen                                            PGP id EFC895FA



From msmith  Sat Mar 11 12:37:36 2006
From: msmith (Michael Smith)
Date: Sat, 11 Mar 2006 15:37:36 -0500 (EST)
Subject: madwifi-ng trunk rev for hostapd/wpa_supp 0.4.8
In-Reply-To: <Pine.LNX.4.61.0603111502430.4145@juice.ott.cti.com>
References: <Pine.LNX.4.61.0603111502430.4145@juice.ott.cti.com>
Message-ID: <Pine.LNX.4.61.0603111527210.4145@juice.ott.cti.com>


Oops, the internet knows everything... I need madwifi-ng < r1357,
or >= r1453 plus a patch to hostapd 0.4.7 (which seems to apply OK to
0.4.8).

http://madwifi.org/ticket/241

On Sat, 11 Mar 2006, Michael Smith wrote:

> Is anyone having success with hostapd/wpa_supplicant 0.4.8 and madwifi-ng? 
> I'm about to switch from madwifi-old (new chipset requires ng) and I'm 
> wondering whether I should go with a recent madwifi-ng snapshot, or one 
> from closer to Feb 8 when 0.4.8 was released.



From brix  Sat Mar 11 12:49:40 2006
From: brix (Henrik Brix Andersen)
Date: Sat, 11 Mar 2006 21:49:40 +0100
Subject: Group key renewal problem
In-Reply-To: <20060311202319.GC9371@jm.kir.nu>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
	<20060311202319.GC9371@jm.kir.nu>
Message-ID: <20060311204940.GB30840@osgiliath.brixandersen.dk>

On Sat, Mar 11, 2006 at 12:23:19PM -0800, Jouni Malinen wrote:
> Is that 00:02:6f:37:fc:68 the MAC address of your AP?

Yes, it is.

> If yes, it sounds like the AP starts using incorrect encryption for
> broadcast/multicast packets (WEP?) after rekeying. You could verify
> what kind of encryption the AP is using by looking at
> /proc/net/hostap/wlan0/crypt before and after rekeying.

Before group key renewal:

# cat /proc/net/hostap/wlan0/crypt
tx_keyidx=1
key[1] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0
key[2] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0

After group key renewal:

# cat /proc/net/hostap/wlan0/crypt
tx_keyidx=1
key[1] alg=CCMP key_set=1 tx_pn=000000000005 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0
key[2] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0


After the rekeying and disconnection of the client, the below messages
appear in the AP system log:

Mar 11 21:44:15 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: deauthenticated due to local deauth request
Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: authenticated
Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: associated (aid 1, accounting session 441334F8-00000007)
Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: pairwise key handshake completed (RSN)

Where 00:0e:35:fd:81:94 is the MAC address of the client. As you can
see, the client is reauthenticated 5 seconds after the group key
renewal kicked it off the AP.

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


From brix  Sat Mar 11 13:46:39 2006
From: brix (Henrik Brix Andersen)
Date: Sat, 11 Mar 2006 22:46:39 +0100
Subject: Group key renewal problem
In-Reply-To: <20060311204940.GB30840@osgiliath.brixandersen.dk>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
	<20060311202319.GC9371@jm.kir.nu>
	<20060311204940.GB30840@osgiliath.brixandersen.dk>
Message-ID: <20060311214639.GC30840@osgiliath.brixandersen.dk>

On Sat, Mar 11, 2006 at 09:49:40PM +0100, Henrik Brix Andersen wrote:
> Before group key renewal:
> 
> # cat /proc/net/hostap/wlan0/crypt
> tx_keyidx=1
> key[1] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0
> key[2] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0
> 
> After group key renewal:
> 
> # cat /proc/net/hostap/wlan0/crypt
> tx_keyidx=1
> key[1] alg=CCMP key_set=1 tx_pn=000000000005 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0
> key[2] alg=CCMP key_set=1 tx_pn=000000000009 rx_pn=000000000000 format_errors=0 replays=0 decrypt_errors=0

Just rechecked the above using a serial console on the AP. The
tx_keyidx increments on group key renewal. It is incremented at
roughly the same time the client spews the fourth ExtIV message.

Hope this helps.

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


From hostap  Sat Mar 11 23:16:46 2006
From: hostap (Oliver Sorge)
Date: Sun, 12 Mar 2006 08:16:46 +0100
Subject: hostapd problems with bridging
Message-ID: <20060312081646.672abe57@rayden>

Hi,

i'm using debian sid with hostapd 0.4.5 and madwifi-old on my atheros
pci wlan card. wenn i start hostapd, my pda can authenticate and
connect to my hostap with wpa-psk tkip. but when i bridge the wired und
wireless networks, the 4-way-handshake fails with eapol key timeout.
why is this? do you have any solution for me or a hint how i can solve
this problem? i don't want to buy a standalone ap ;) is hostap unable
to work with wlan devices wich are in promiscous mode?

-- 
 .''`.     Oliver Sorge <oliver at dediziert.org>
: :'  :    proud Debian admin and user since 2001
`. `'`
  `-  Debian - when you have better things to do than fix a system



From brix  Sun Mar 12 02:48:33 2006
From: brix (Henrik Brix Andersen)
Date: Sun, 12 Mar 2006 11:48:33 +0100
Subject: hostapd problems with bridging
In-Reply-To: <20060312081646.672abe57@rayden>
References: <20060312081646.672abe57@rayden>
Message-ID: <20060312104833.GA13114@osgiliath.brixandersen.dk>

Hi,

On Sun, Mar 12, 2006 at 08:16:46AM +0100, Oliver Sorge wrote:
> i'm using debian sid with hostapd 0.4.5 and madwifi-old on my atheros
> pci wlan card. wenn i start hostapd, my pda can authenticate and
> connect to my hostap with wpa-psk tkip. but when i bridge the wired und
> wireless networks, the 4-way-handshake fails with eapol key timeout.
> why is this? do you have any solution for me or a hint how i can solve
> this problem? i don't want to buy a standalone ap ;) is hostap unable
> to work with wlan devices wich are in promiscous mode?

Did you remember to add "bridge=br0" to your hostapd.conf file? This
is needed when using madwifi in a bridge.

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


From brix  Sun Mar 12 03:43:48 2006
From: brix (Henrik Brix Andersen)
Date: Sun, 12 Mar 2006 12:43:48 +0100
Subject: Group key renewal problem
In-Reply-To: <20060311204940.GB30840@osgiliath.brixandersen.dk>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
	<20060311202319.GC9371@jm.kir.nu>
	<20060311204940.GB30840@osgiliath.brixandersen.dk>
Message-ID: <20060312114348.GA17973@osgiliath.brixandersen.dk>

On Sat, Mar 11, 2006 at 09:49:40PM +0100, Henrik Brix Andersen wrote:
> After the rekeying and disconnection of the client, the below messages
> appear in the AP system log:
> 
> Mar 11 21:44:15 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: deauthenticated due to local deauth request
> Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: authenticated
> Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: associated (aid 1, accounting session 441334F8-00000007)
> Mar 11 21:44:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: pairwise key handshake completed (RSN)
> 
> Where 00:0e:35:fd:81:94 is the MAC address of the client. As you can
> see, the client is reauthenticated 5 seconds after the group key
> renewal kicked it off the AP.

I had forgotten to enable debug output to the system log, here are the
messages with logger_syslog=-1 and logger_syslog_level=1:

Mar 12 12:33:18 osgiliath hostapd: wlan0: WPA rekeying GTK
Mar 12 12:33:18 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 1/2 msg of Group Key Handshake
Mar 12 12:33:19 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: EAPOL-Key timeout
Mar 12 12:33:19 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 1/2 msg of Group Key Handshake
Mar 12 12:33:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: EAPOL-Key timeout
Mar 12 12:33:20 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 1/2 msg of Group Key Handshake
Mar 12 12:33:21 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: EAPOL-Key timeout
Mar 12 12:33:21 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 1/2 msg of Group Key Handshake
Mar 12 12:33:21 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.1X: unauthorizing port
Mar 12 12:33:21 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: deauthenticated due to local deauth request
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: authentication OK (open system)
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: authenticated
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: association OK (aid 1)
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.11: associated (aid 1, accounting session 441406C2-00000002)
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: event 1 notification
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: start authentication
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.1X: unauthorizing port
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 1/4 msg of 4-Way Handshake
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: received EAPOL-Key frame (2/4 Pairwise)
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: sending 3/4 msg of 4-Way Handshake
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: received EAPOL-Key frame (4/4 Pairwise)
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 IEEE 802.1X: authorizing port
Mar 12 12:34:26 osgiliath hostapd: wlan0: STA 00:0e:35:fd:81:94 WPA: pairwise key handshake completed (RSN)

The first four "WPA: sending 1/2 msg of Group Key Handshake" are the
ones causing the "CCMP: received packet without ExtIV flag from
00:02:6f:37:fc:68" messages on the client.

Would you like me to open a bug report about this?

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


From hostap  Sun Mar 12 06:33:20 2006
From: hostap (Oliver Sorge)
Date: Sun, 12 Mar 2006 15:33:20 +0100
Subject: hostapd problems with bridging
In-Reply-To: <20060312104833.GA13114@osgiliath.brixandersen.dk>
References: <20060312081646.672abe57@rayden>
	<20060312104833.GA13114@osgiliath.brixandersen.dk>
Message-ID: <20060312153320.688b5096@rayden>

On Sun, 12 Mar 2006 11:48:33 +0100
Henrik Brix Andersen <brix at gentoo.org> wrote:

> Did you remember to add "bridge=br0" to your hostapd.conf file? This
> is needed when using madwifi in a bridge.

you got me. i forgot that. hostapd now sais "Configure bridge br0 for
EAPOL traffic" but the eapol key timeouts doesn't dissapear and my pda
can't associate with my hostap :(

-- 
 .''`.     Oliver Sorge <oliver at dediziert.org>
: :'  :    proud Debian admin and user since 2001
`. `'`
  `-  Debian - when you have better things to do than fix a system



From pzawadzki  Sun Mar 12 09:54:46 2006
From: pzawadzki (Piotr Zawadzki)
Date: Sun, 12 Mar 2006 18:54:46 +0100
Subject: Problems with WPA-PSK
Message-ID: <200603121854.47198.pzawadzki@polsl.pl>

I have problems with WPA-PSK setup. I'm using hostapd 0.5.1 and 
wpa_supplicatnt 0.5.1

The hostAP and STA use the following cards, respectively:
AP:
--
2:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 
01)
--
STA:
--
# cardctl ident
product info: "TP-LINK technology ", "Inc. ", "", ""
manfid: 0x0271, 0x0012
function: 6 (network)
--	
The card in the authenticator is the old one, 
--
# hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.0.7
STAID: id=0x001f v1.3.6 (station firmware)
-- 
so I upraded firmware
--
# prism2_srec -gs wlan0 ak010104.hex ; prism2_srec -gp wlan0 ak010104.hex ; 
prism2_srec -rp wlan0 rf010804.hex
...
Components after download:
  NICID: 0x8013 v1.0.0
  PRIID: 0x0015 v1.1.4
  STAID: 0x001f v1.8.4
--
and then started hostapd (hostap driver from the kernel 2.6.14)
with the following config file
--
interface=wlan0
driver=hostap
ssid=misiek
macaddr_acl=0
accept_mac_file=/etc/hostap/hostapd.accept
deny_mac_file=/etc/hostap/hostapd.deny
auth_algs=1
own_ip_addr=192.168.100.1
wpa=1
wpa_passphrase=misiobury
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
--

On the station the wpa_supplicant is started with command

# wpa_supplicant -c wpasupplicant-WPA_PSK.conf -D madwifi -i ath0 -d

File wpasupplicant-WPA_PSK.conf
--
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
network={
    ssid="misiek"
    key_mgmt=WPA-PSK
    proto=WPA
    pairwise=TKIP
    psk="misiobury"
}
--
Unfortunately this setup does not work and supplicant is not able to finish 
4-Way handshake.

Output from hostapd
--
Configuration file: hostapd_WPA-PSK.conf
ctrl_interface_group=0
Opening raw packet socket for ifindex 97
Using interface wlan0 with hwaddr 00:0f:cb:b0:0d:9b and ssid 'misiek'
SSID - hexdump_ascii(len=6):
     6d 69 73 69 65 6b                                 misiek
PSK (ASCII passphrase) - hexdump_ascii(len=9):
     6d 69 73 69 6f 62 75 72 79                        misiobury
PSK (from passphrase) - hexdump(len=32): 58 12 6a d5 89 f0 36 c0 dd 9b db d9 
eb 7e 8c da 9d 4a c0 3e d8 c0 02 ba a5 17 71 5f 06 64 1f ac
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): [REMOVED]
GTK - hexdump(len=32): [REMOVED]
WPA: group state machine entering state SETKEYSDONE
SIOCGIWRANGE: WE(compiled)=19 WE(source)=18 enc_capa=0xf
Flushing old station entries
Deauthenticate all stations
mgmt::auth
authentication: STA=00:0a:eb:a6:6c:98 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.11: authentication OK (open system)
authentication reply: STA=00:0a:eb:a6:6c:98 auth_alg=0 auth_transaction=2 
resp=0
MGMT (TX callback) ACK
mgmt::auth cb
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.11: authenticated
mgmt::assoc_req
association request: STA=00:0a:eb:a6:6c:98 capab_info=0x31 listen_interval=100
  new AID 1
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.11: association OK (aid 1)
MGMT (TX callback) ACK
mgmt::assoc_resp cb
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.11: associated (aid 1, accounting 
session 441459E4-00000000)
wlan0: STA 00:0a:eb:a6:6c:98 WPA: event 1 notification
wlan0: STA 00:0a:eb:a6:6c:98 WPA: start authentication
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state INITIALIZE
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.1X: unauthorizing port
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state IDLE
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state AUTHENTICATION
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state INITPSK
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state PTKSTART
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 1/4 msg of 4-Way Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:0a:eb:a6:6c:98 TX status - version=2 type=3 length=95 - ack=1
DATA
IEEE 802.1X: 123 bytes from 00:0a:eb:a6:6c:98
   IEEE 802.1X: version=1 type=3 length=119
wlan0: STA 00:0a:eb:a6:6c:98 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state PTKINITNEGOTIATING
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 3/4 msg of 4-Way Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=24): [REMOVED]
DATA (TX callback) ACK
IEEE 802.1X: 00:0a:eb:a6:6c:98 TX status - version=2 type=3 length=119 - ack=1
DATA
IEEE 802.1X: 99 bytes from 00:0a:eb:a6:6c:98
   IEEE 802.1X: version=1 type=3 length=95
wlan0: STA 00:0a:eb:a6:6c:98 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state PTKINITDONE
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.1X: authorizing port
wlan0: STA 00:0a:eb:a6:6c:98 WPA: pairwise key handshake completed (WPA)
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
DATA (TX callback) ACK
IEEE 802.1X: 00:0a:eb:a6:6c:98 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:0a:eb:a6:6c:98 WPA: EAPOL-Key timeout
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
DATA (TX callback) ACK
IEEE 802.1X: 00:0a:eb:a6:6c:98 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:0a:eb:a6:6c:98 WPA: EAPOL-Key timeout
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
DATA (TX callback) ACK
IEEE 802.1X: 00:0a:eb:a6:6c:98 TX status - version=2 type=3 length=127 - ack=1
wlan0: STA 00:0a:eb:a6:6c:98 WPA: EAPOL-Key timeout
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state REKEYNEGOTIATING
wlan0: STA 00:0a:eb:a6:6c:98 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state KEYERROR
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 
00:0a:eb:a6:6c:98 reason 2
WPA: 00:0a:eb:a6:6c:98 WPA_PTK_GROUP entering state IDLE
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state DISCONNECTED
WPA: 00:0a:eb:a6:6c:98 WPA_PTK entering state INITIALIZE
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.1X: unauthorizing port
wlan0: STA 00:0a:eb:a6:6c:98 IEEE 802.11: deauthenticated due to local deauth 
request
DATA (TX callback) ACK
--
 			
Output from the wpa_supplicant
--
Initializing interface 'ath0' conf 'wpasupplicant-WPA_PSK.conf' driver 
'madwifi' ctrl_interface 'N/A'
Configuration file 'wpasupplicant-WPA_PSK.conf' -> 
'/root/wpasupplicant-WPA_PSK.conf'
Reading configuration file '/root/wpasupplicant-WPA_PSK.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
Line 11: removed CCMP from group cipher list since it was not allowed for 
pairwise cipher
Priority group 0
id=0 ssid='misiek'
Initializing interface (2) 'ath0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=13 enc_capa=0x0
capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:0a:eb:a6:6c:98
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
Added interface ath0
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=8
Wireless event: cmd=0x8b19 len=8
Received 311 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
0: 00:0f:cb:b0:0d:9b ssid='misiek' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
       selected based on WPA IE
Trying to associate with 00:0f:cb:b0:0d:9b (SSID='misiek' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 
00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 10 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=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:cb:b0:0d:9b
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:0f:cb:b0:0d:9b
No keys have been configured - skip key clearing
Associated with 00:0f:cb:b0:0d:9b
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0f:cb:b0:0d:9b
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=2 type=3 length=95
EAPOL-Key type=254
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:0f:cb:b0:0d:9b (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 
01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): e6 8b 25 28 9a 26 21 56 74 49 12 a0 a2 
bd ef 74 08 c5 e2 fc 97 da ec a1 7c f5 52 7f 8f 67 40 11
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0f:cb:b0:0d:9b
IEEE 802.1X RX: version=2 type=3 length=119
EAPOL-Key type=254
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:0f:cb:b0:0d:9b (ver=1)
WPA: IE KeyData - hexdump(len=24): da 7d cc be da 73 7b 67 f3 ca 66 0f 99 e8 
55 7e 67 03 39 36 39 09 38 e0
WPA: EAPOL-Key Key Data underflow (ie=218 len=125)
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:0f:cb:b0:0d:9b into blacklist
State: GROUP_HANDSHAKE -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - 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
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=8
Wireless event: cmd=0x8b19 len=8
Received 311 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
0: 00:0f:cb:b0:0d:9b ssid='misiek' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
Trying to associate with 00:0f:cb:b0:0d:9b (SSID='misiek' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 
00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_madwifi_associate
Setting authentication timeout: 10 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=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0f:cb:b0:0d:9b
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:0f:cb:b0:0d:9b
No keys have been configured - skip key clearing
Associated with 00:0f:cb:b0:0d:9b
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RX EAPOL from 00:0f:cb:b0:0d:9b
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=2 type=3 length=95
       EAPOL-Key type=254
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:0f:cb:b0:0d:9b (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 
01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 67 8d 2b f3 d5 86 64 63 cf a9 e4 5a f4 
50 08 48 2e c5 fc 4d 63 f0 aa 82 f8 6c 74 71 56 8c d2 4c
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:0f:cb:b0:0d:9b
IEEE 802.1X RX: version=2 type=3 length=119
EAPOL-Key type=254
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:0f:cb:b0:0d:9b (ver=1)
WPA: IE KeyData - hexdump(len=24): 4e d4 a6 e2 ff e7 7a 1b f2 33 4a 04 c3 80 
98 0a f8 59 64 fd 36 53 2f d0
WPA: EAPOL-Key Key Data underflow (ie=78 len=212)
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_madwifi_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:0f:cb:b0:0d:9b blacklist count incremented to 2
State: GROUP_HANDSHAKE -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
--		   
-- 
Piotr Zawadzki, Silesian Technical University
PGP: http://www.keyserver.net/



From pelusitavali  Sun Mar 12 10:30:46 2006
From: pelusitavali (Pelusa Vali)
Date: Sun, 12 Mar 2006 18:30:46 +0000
Subject: will this work?
Message-ID: <PM.2508.1142188246@pmweb18.uk1.bibliotech.net>

hi everybody, i use debian sarge, madwifi-ng-r1457, hostapd 0.4.8 and freeradius 1.1, i want to use eap-tls, is there any special configuration or patch should be applied to any of this programs to get them work? i tried configurations from madwifi users docs and many tutorials, but nothing works.  simply clients cann't authenticate, always get: Access-Reject.  
these are my conf files:

MADWIFI:

modprobe ath_pci autocreate=ap
wlanconfig ath0 create wlandev wifi0 wlanmode ap
ifconfig ath0 up
iwpriv ath0 mode 3
iwconfig ath0 essid MYWLAN
iwconfig ath0 channel 2
iwconfig ath0 bitrate 54M
iwconfig ath0 frag 512
iwconfig ath0 rts 250
iwpriv ath0 ar 1
echo 1 > /proc/sys/net/ipv4/ip_forward
/etc/init.d/networking restart
IPTABLES=/sbin/iptables
$IPTABLES -F -t nat
$IPTABLES -A POSTROUTING -t nat -o eth0 -j MASQUERADE
/etc/init.d/dhcp stop
/etc/init.d/dhcp start

DHCP:
subnet 192.168.10.0 netmask 255.255.255.0 {  
range 192.168.10.2 192.168.10.30;
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.10.255;
  default-lease-time 600;
  max-lease-time 7200;
}

HOSTAPD:
interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=4
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=MYWLAN
macaddr_acl=0
auth_algs=3
ieee8021x=1
eap_message=hello
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1
nas_identifier=www.server.com
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=whatever
acct_server_addr=127.0.0.1
acct_server_port=1813
acct_server_shared_secret=whatever
wpa=1
wpa_key_mgmt=WPA-EAP
wpa_pairwise=TKIP
wpa_strict_rekey=1
wpa_gmk_rekey=86400

DEFAULT HOSTAPD:
#RUN_DAEMON=yes

RADIUS USERS:
"pupis" 
DEFAULT	Auth-Type = System
         Fall-Through = 1

here i tried too: DEFAULT	Auth-Type = EAP
         Fall-Through = 1

each one alone, and together.

RADIUS CLIENTS.CONF:
client 127.0.0.1 {
        secret         = whatever
        shortname      = www.server.com
}

RADIUS EAP.CONF:
default_eap_type = tls
tls {
certificate_file = ${raddbdir}/certs/cert-srv.pem
CA_file = ${raddbdir}/certs/demoCA/cacert.pem
dh_file = ${raddbdir}/certs/dh
random_file = ${raddbdir}/certs/random
}

when i run, get this:

hostapd logs:
Sending RADIUS message to accounting server
RADIUS message: code=4 (Accounting-Request) identifier=0 length=88
   Attribute 40 (Acct-Status-Type) length=6
      Value: 7
   Attribute 45 (Acct-Authentic) length=6
      Value: 1
   Attribute 4 (NAS-IP-Address) length=6
      Value: 127.0.0.1
   Attribute 32 (NAS-Identifier) length=14
      Value: 'www.server.com'
   Attribute 30 (Called-Station-Id) length=30
      Value: '00-0F-66-11-C1-97:MYWLAN'
   Attribute 49 (Acct-Terminate-Cause) length=6
      Value: 11
Next RADIUS client retransmit in 3 seconds
Flushing old station entries

running locally radtest:

radtest pupis whatever localhost 0 whatever
Sending Access-Request of id 178 to 127.0.0.1 port 1812
        User-Name = "pupis"
        User-Password = "whatever"
        NAS-IP-Address = 255.255.255.255
        NAS-Port = 0
rad_recv: Access-Accept packet from host 127.0.0.1:1812, id=178, length=20

by the way, i cann't run radclient or radeapclient, when use it, don't get any response.

but now, winxp clients don't detect this wlan as activated with wpa, only wlan without security, and don't get any ip direction, even i'm using dhcp.  if i don't run radius and hostapd then client do get ip direction and can use wlan.

so, my question again is, what should i do to get eap-tls working?? i heard that may be this won't work with debian, could it be a possible explanation?? i'm really tired , i tried everything i think,  and don't know what more should do.
thanks in advance for your patience.


_______________________________________________________________ 
Halloween Humour: What kind of girl does a mummy go out with?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=154




From paul  Sun Mar 12 16:13:54 2006
From: paul (Paul H. Yoshimune)
Date: Sun, 12 Mar 2006 16:13:54 -0800
Subject: wpa_supplicant, Airport Extreme Base Station, and WPA-PSK...
Message-ID: <4414B942.7020704@vindicia.com>

All:

I'm trying to set up a very basic 802.11g network using wpa_supplicant (Linux 
client), an Apple Airport Extreme Base Station, and WPA-PSK.  The latter two 
are set up, and work fine with a couple of PowerBooks with Airport cards.  I'm 
having a hard time getting the Linux machine (a ThinkPad T43, Intel 2200 
wireless) working, however.

The general configuration works fine - it can talk on open networks without 
trouble.  The error output looks like:

[root at paul ~]# wpa_supplicant -D wext -d -c /etc/wpa_supplicant.conf -ieth1
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'wext' 
ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
opensc_engine_path='/usr/lib/opensc/engine_opensc.so'
pkcs11_engine_path='/usr/lib/opensc/engine_pkcs11.so'
pkcs11_module_path='/usr/lib/pkcs11/opensc-pkcs11.so'
Priority group 9
    id=0 ssid='Extreme'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=18 WE(source)=16 enc_capa=0x0
   capabilities: key_mgmt 0x0 enc 0x3
Own MAC address: 00:13:ce:81:0a:b6
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface eth1
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 2525 bytes of scan results (12 BSSes)
Scan results: 12
Selecting BSS from priority group 9
0: 00:13:10:88:36:b5 ssid='<hidden>' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
    skip - SSID mismatch
1: 00:11:24:a4:34:ed ssid='Extreme' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
    selected based on WPA IE
Trying to associate with 00:11:24:a4:34:ed (SSID='Extreme' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 
00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=20
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_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
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
State: DISCONNECTED -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 2707 bytes of scan results (13 BSSes)
Scan results: 13
Selecting BSS from priority group 9
0: 00:13:10:88:36:b5 ssid='<hidden>' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
    skip - SSID mismatch
1: 00:11:24:a4:34:ed ssid='Extreme' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
    selected based on WPA IE
Trying to associate with 00:11:24:a4:34:ed (SSID='Extreme' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 
00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=20
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
State: ASSOCIATING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_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
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
State: DISCONNECTED -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request
[root at paul ~]#

The relevant bits of wpa_supplicant.conf look like:

network={
         ssid="Extreme"
         scan_ssid=0
         proto=WPA
         key_mgmt=WPA-PSK
         pairwise=TKIP
         group=TKIP
         psk="8d9rE6wq"
         priority=9
}

It seems that I'm looking for the most basic/straightforward case of using 
WPA, so I'm sure I'm missing something stupid.  Ideas?  Thanks...

-Paul



From jkmaline  Sun Mar 12 17:15:38 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 12 Mar 2006 17:15:38 -0800
Subject: [RFC: 2.6 patch] hostap_hw.c:hfa384x_set_rid(): fix error handling
In-Reply-To: <20060309230646.GI21864@stusta.de>
References: <20060309230646.GI21864@stusta.de>
Message-ID: <20060313011538.GU9383@jm.kir.nu>

On Fri, Mar 10, 2006 at 12:06:46AM +0100, Adrian Bunk wrote:

> The Coverity checker noted that the call to prism2_hw_reset() was dead 
> code.
> 
> Does this patch change the code to what was intended?

Thanks! Based on my CVS history, it looks like this was broken in 2002
when the access command was moved from another function and verification
of -ETIMEDOUT value was not moved correctly. The original behavior would
be achieved by changing your patch to call printk first before the moved
prism2_hw_reset(dev) call. I added this (with the re-ordered printk) to
my queue for wireless-2.6.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Mar 12 17:23:41 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 12 Mar 2006 17:23:41 -0800
Subject: [2.6 patch] hostap_ap.c:hostap_add_sta(): inconsequent NULL
	checking
In-Reply-To: <20060310191026.GS21864@stusta.de>
References: <20060310191026.GS21864@stusta.de>
Message-ID: <20060313012341.GV9383@jm.kir.nu>

On Fri, Mar 10, 2006 at 08:10:26PM +0100, Adrian Bunk wrote:
> The Coverity checker spotted this inconsequent NULL checking 
> (unconditionally dereferencing directly after checking for NULL
> isn't a good idea).

Thanks! Added to my queue for wireless-2.6.

-- 
Jouni Malinen                                            PGP id EFC895FA



From monnier  Mon Mar 13 14:37:02 2006
From: monnier (Stefan Monnier)
Date: Mon, 13 Mar 2006 17:37:02 -0500
Subject: wpa_cli action tscript for web-based authentication
Message-ID: <jwvfylmrn2z.fsf-monnier+diro@gnu.org>

Has anyone written a wpa_cli action script that can be used for those public
access points that require you to go through an https-based authentication
before allowing you access to the internet?

BTW, let me also agree with Paul Fox (pgf at brightstareng.com) that there
should be some way to pass information from /etc/wpa_supplicant.conf to the
wpa_cli action script.  I'd want to be able to write in my
wpa_supplicant.conf something like:

   network={
     ssid="Foobar"
     key_mgmt=NONE
     cli_arg1="https"
     cli_arg2="username"
     cli_arg3="password"
   }

   network={
     ssid="FooToto"
     key_mgmt=NONE
     cli_arg1="pptp"
     cli_arg2="pptp.server.name"
     cli_arg3="username"
     cli_arg4="password"
   }


-- Stefan



From fatimapeter  Mon Mar 13 18:36:44 2006
From: fatimapeter (Fatima Peter)
Date: Mon, 13 Mar 2006 18:36:44 -0800
Subject: Help in forwarding frames to application
Message-ID: <BAY103-F7CF2C6D2E8BE3861C408DAFE10@phx.gbl>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060313/1f2f35bc/attachment.htm 


From jhz  Mon Mar 13 23:12:58 2006
From: jhz (Jared Holzman)
Date: Tue, 14 Mar 2006 15:12:58 +0800
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
Message-ID: <44166CFA.3000404@mrxtech.com.au>

To All,

I'm having trouble trying to configure HostAP with static WEP on my 
server. Configuration seems to work using iwconfig tool (iwconfig mode 
Master, iwconfig essid, iwconfig key etc, etc) and I can then use the 
AP. However once I start the hostapd daemon, the encryption key seems to 
disappear from iwconfig and the AP becomes unusuable (in both unsecured 
mode and WEP mode) and if I try and set the key subsequently, using the 
iwconfig tool, it fails with an error and then comes up with invalid 
output until I reset the device.

Any Ideas?

Thanks,

Jared

PS Following is some relevant log information

[root at bob root]# iwconfig wlan0
wlan0     IEEE 802.11b  ESSID:"homezone"  Nickname:"bob.homezone"
          Mode:Master  Frequency:2.437 GHz  Access Point: 00:09:5B:67:92:F2   
          Bit Rate:5.5 Mb/s   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:2  Rx invalid frag:0
          Tx excessive retries:460  Invalid misc:171   Missed beacon:0

[root at bob root]# cat /etc/hostapd/hostapd.conf | grep -v ^\#
interface=wlan0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=homezone
macaddr_acl=0
accept_mac_file=/etc/hostapd/hostapd.accept
deny_mac_file=/etc/hostapd/hostapd.deny
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
own_ip_address=127.0.0.1

[root at bob root]# hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Opening raw packet socket for ifindex 11
Using interface wlan0 with hwaddr 00:09:5b:67:92:f2 and ssid 'homezone'
Flushing old station entries
Deauthenticate all stations
Wireless event: cmd=0x8c04 len=20
Wireless event: cmd=0x8b2a len=8
Received 268 bytes management frame
DATA
Data frame from not associated STA 00:0f:b5:8e:da:43
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 24 bytes management frame
DATA
Data frame from not associated STA 00:09:5b:67:8e:fd
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations
Could not disable PrivacyInvoked for interface wlan0
Could not remove generic information element from interface wlan0

[root at bob root]# hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Opening raw packet socket for ifindex 17
Using interface wlan0 with hwaddr 00:09:5b:67:92:f2 and ssid 'homezone'
Flushing old station entries
Deauthenticate all stations
Wireless event: cmd=0x8c04 len=20
Wireless event: cmd=0x8b2a len=8
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 24 bytes management frame
DATA
Data frame from not associated STA 00:09:5b:67:8e:fd
Received 24 bytes management frame
DATA
Data frame from not associated STA 00:09:5b:67:8e:fd
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 60 bytes management frame
DATA
Data frame from not associated STA 00:0f:b5:8e:da:43
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 342 bytes management frame
extra data in frame (elen=0)
unknown frame type 3
Received 360 bytes management frame
DATA
Data frame from not associated STA 00:0f:b5:8e:da:43

Received 360 bytes management frame
DATA
Data frame from not associated STA 00:0f:b5:8e:da:43

[root at bob root]# iwconfig wlan0
wlan0     IEEE 802.11b  ESSID:"homezone"  Nickname:"bob.homezone"
          Mode:Master  Frequency:2.437 GHz  Access Point: 00:09:5B:67:92:F2
          Bit Rate:11 Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:14   Missed beacon:0

[root at bob root]# iwconfig wlan0 key XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; Invalid argument.
[root at bob root]# iwconfig wlan0
wlan0     IEEE 802.11-DS  ESSID:"homezone"
          Mode:Master
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:14   Missed beacon:0


[root at bob root]# iwconfig -v
iwconfig  Wireless-Tools version 28
          Compatible with Wireless Extension v11 to v19.

Kernel    Currently compiled with Wireless Extension v19.

wifi0     Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension v19.

wlan0     Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension v19.

wlan0ap   Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension v19.





From hostap  Tue Mar 14 00:32:00 2006
From: hostap (Oliver Sorge)
Date: Tue, 14 Mar 2006 09:32:00 +0100
Subject: upgrading from 0.4.5 to 0.5.0
Message-ID: <20060314093200.41969975@rayden>

Hi,

i just upgraded from hostapd 0.4.5 to hostap 0.5.0 and now i get this
annoying eapol key timeouts. if i downgrade to 0.4.5 everything works
fine. the config file is the same. is there another directive i've
missed inthe newer version of hostap?

-- 
 .''`.     Oliver Sorge <oliver at dediziert.org>
: :'  :    proud Debian admin and user since 2001
`. `'`
  `-  Debian - when you have better things to do than fix a system



From sebastian.eiser  Tue Mar 14 04:56:29 2006
From: sebastian.eiser (Sebastian Eiser)
Date: Tue, 14 Mar 2006 13:56:29 +0100
Subject: WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper,
	ubuntu, WG511 (v1)
Message-ID: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>

Hi all,

I gratefully read on the wpa_supplicant homepage that I may use this
mailing list to ask topics not only related to hostap, but also e.g.
ndiswrapper in conjunction with wpa_supplicant, so I hope this is not
annoying for you...actually I couldnt get help in any kind of forum
for more that a week intensive posting - so I take this to the
experts.
 I've just searched the non-gzip'd archive, but my problem is slightly
different.
---

I'm trying to set up a wpa connection (Ubuntu 5.10) using the latest
releases of ndiswrapper and wpa_supplicant. The driver works fine with
wpa in windoze, and ndiswrapper confirms it correctly loaded (chipset
Intersil ISL3890 (netgear WG511 V1)).
if I do "wpa_supplicant -i wlan0 -D ndiswrapper -c
/etc/wpa_supplicant.conf -ddd" the 4WAY_HANDSHAKE state never
completes. when I read the output, several lines may indicate a faulty
setup (full output appended):

ioctl[SIOCSIWPMKSA]: No such device
>> this is not serious, afaik
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
>> ? - is this due to a faulty key? windoze successfully uses a 63char
ASCII code. I used wpa_passphrase to convert it to HEX.. anyway - it
continues:

ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>> 4 times....

and in the end:
WPA: Sending EAPOL-Key 2/4
>> all the time. It seems like the AP doesnt accept the key and
wouldnt let me connect. is there a way to check that in detail.

I saw that Arjan van Bentem hostap at avbentem.dds.nl (post to the
maillist on Tue Apr 19 12:19:07 MDT 2005) had a quite similar problem
http://lists.shmoo.com/pipermail/hostap/2005-April/010113.html

I hope (and still believe) I just made a dump mistake during the
configuration, but I've tried so hard and it seems that I'm not yet
skilled enough to solve it. that's why I'd greatly appreciate any
input to this topic.
actually my neighbor (I share my connection with him) is just laughing
at me: "why the hell dont you wanna use windows"... well, he dosent
know a thing.

guys, I'm looking forward for you replies! feel free to request
further information... dont let me down, for my neighbors sake ;-)

seb

pasting complete terminal output:
---
sudo wpa_supplicant -i wlan0 -D ndiswrapper -c /etc/wpa_supplicant.conf -ddd

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
fast_reauth=1
Line: 17 - start of a new network block
ssid - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
scan_ssid=1 (0x1)
proto: 0x1
key_mgmt: 0x2
PSK - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='WG-Netz'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: No such device
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:09:5b:45:df:68
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
Scan timeout - try to get results
Received 2307 bytes of scan results (9 BSSes)
Scan results: 9
Selecting BSS from priority group 0
0: 00:04:0e:7e:49:32 ssid='WG-Netz' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:04:0e:7e:49:32 (SSID='WG-Netz' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8c02 len=169
Custom wireless event:
'ASSOCINFO(ReqIEs=000757472d4e65747a010402040b1632080c1218243048606cdd160050f20101000050f20201000050f20201000050f202
RespIEs=010482848b9632088c129824b048606c)'
Association info event
req_ies - hexdump(len=49): 00 07 57 47 2d 4e 65 74 7a 01 04 02 04 0b
16 32 08 0c 12 18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 8c 12 98 24 b0 48 60 6c
WPA: set own WPA/RSN 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
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:04:0e:7e:49:32
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:04:0e:7e:49:32
No keys have been configured - skip key clearing
Associated with 00:04:0e:7e:49:32
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:04:0e:7e:49:32
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17 e3 13 ae
c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
00 00 00 00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17
e3 13 ae c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:04:0e:7e:49:32 (ver=1)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 1d 3d 6d 10 76 eb c3 b0 c9 4a
39 8c 03 23 77 53 9b ed 8d 45 cf 8d 17 fa 78 4d 8c 4b 60 67 65 30
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 ...
<<<<< to be repeated all the time .... (the hexdump values change, though)



From gianni.costanzi  Tue Mar 14 06:27:55 2006
From: gianni.costanzi (Gianni Costanzi)
Date: Tue, 14 Mar 2006 15:27:55 +0100
Subject: wlan0 disappears after few seconds [Hostap problem]
Message-ID: <671355fe0603140627v16be166amdfaf3d3539f9e96c@mail.gmail.com>

Hi,
I've installed hostap on a Gentoo Linux box with kernel 2.4.31 (I need
to use a 2.4 kernel) and a Netgear MA401 PCMCIA card and everything
seems to work: I can change wlan0 to Master mode (even if I get an
error, as if the request was illegal, but then iwconfig shows me wlan0
and wifi0 in Master mode.. is it normal?) and other laptops are able
to connect to my laptop as if it was an access point (two laptops
associated themselves to my laptop and then they were able to ping one
each other).. The problem is that after few seconds something wrong
happens and the access point stops working (iwconfig tells me that
wlan0 has "no wireless extensions").. I'll put here the relevant
content of dmesg, perhaps some of you can help me (i need to make this
stuff work for my thesis):


pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
Yenta ISA IRQ mask 0x0050, PCI irq 7
Socket status: 30000010
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: excluding 0x810-0x87f
cs: IO port probe 0x0100-0x04ff: excluding 0x370-0x377 0x3b0-0x3df
0x3f0-0x3f7 0x480-0x4bf 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=50 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 5.0, irq 7, io 0x0100-0x013f
prism2_hw_init: initialized in 190 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
wifi0: defaulting to host-based encryption as a workaround for
firmware bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug
in Host AP mode WDS
wifi0: registered netdevice wlan0
wlan0: Host AP mode does not support 'Any' essid
prism2: wlan0: operating mode changed 3 -> 2
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=00:09:5b:54:7a:c1
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:14:a8:24:b6:b0
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc04, len=34)
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc04, len=34)
prism2: wlan0: operating mode changed 2 -> 3
wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
wifi0: scheduled card reset
hostap_cs: wifi0: resetting card
prism2_pccard_cor_sreset: original COR 41
wifi0: removed pending cmd_queue entry (type=0, cmd=0x0002, param0=0x0000)
prism2_hw_init: initialized in 200 ms
wlan0: hfa384x_cmd: command was not completed (res=0, entry=f73b8260,
type=0, cmd=0x0002, param0=0x0000, EVSTAT=0000 INTEN=e09f)
wlan0: reset port failed to disable port
wifi0: 00:0e:35:7c:a3:0e auth_cb - alg=0 trans#=2 status=0 - STA authenticated
wifi0: 00:0e:35:7c:a3:0e assoc_cb - STA associated
wifi0: 00:e0:98:b4:2f:4d auth_cb - alg=0 trans#=2 status=0 - STA authenticated
wifi0: assoc from 00:e0:98:b4:2f:4d with extra data (10 bytes)
[<32><08><0c><12><18><24><30><48><60><6c>]
wifi0: 00:e0:98:b4:2f:4d assoc_cb - STA associated
wifi0: Deauthenticate all stations
wlan0: hfa384x_cmd: entry still in list? (entry=f77a4d60, type=0, res=200)
wlan0: hfa384x_cmd: interrupted; err=-4
wlan0: MAC port 0 enabling failed
wlan0: could not enable MAC port
wifi0: Command completion event, but no pending commands


Perhaps it's something related to the "MAC port 0 enabling failed" error...
Any idea?

Thank you in advance for any suggestion,
Gianni

--
--------------------------------------------------------------------------------------------------------------
|  Gianni Costanzi (gianni.costanzi at gmail.com)
|
|  Gentoo Documentation Project (GDP) Member - Italian Translator
|       (http://www.gentoo.org/proj/en/gdp/)
|       (http://ares.science.unitn.it/~gianni.costanzi/)
|
|  Free Software Foundation Member #3844 (www.fsf.org)
|
|  Why GNU/Linux? (http://www.gnu.org/gnu/why-gnu-linux.html)
--------------------------------------------------------------------------------------------------------------


From bryan  Tue Mar 14 09:39:28 2006
From: bryan (Bryan Kadzban)
Date: Tue, 14 Mar 2006 12:39:28 -0500
Subject: WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper,
	ubuntu, WG511 (v1)
In-Reply-To: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>
References: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>
Message-ID: <20060314173928.GA25078@kadzban.is-a-geek.net>

On Tue, Mar 14, 2006 at 01:56:29PM +0100, Sebastian Eiser wrote:
> SIOCGIWRANGE: too old (short) data - assuming WPA is not supported

What kernel version is this?  It might work better (especially if you're
using the latest ndiswrapper) to use the wext driver in wpa_supplicant
instead of the ndiswrapper driver.  (-Dwext instead of -Dndiswrapper)

> and in the end:
> WPA: Sending EAPOL-Key 2/4
> >> all the time. It seems like the AP doesnt accept the key and
> wouldnt let me connect. is there a way to check that in detail.

Only if you can get at logs from the AP that would tell you why it's
dropping the EAPOL-Key frame.  The most common reason is a mismatch in
PSK values, but there are other reasons too.  I think looking into wext
(assuming you have a new enough kernel) would be a bit more promising,
though.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060314/6ec8d688/attachment.pgp 


From sebastian.eiser  Tue Mar 14 11:37:16 2006
From: sebastian.eiser (Sebastian Eiser)
Date: Tue, 14 Mar 2006 20:37:16 +0100
Subject: WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper,
	ubuntu, WG511 (v1)
In-Reply-To: <20060314173928.GA25078@kadzban.is-a-geek.net>
References: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>
	<20060314173928.GA25078@kadzban.is-a-geek.net>
Message-ID: <1fe8db230603141137h485a52fau27ae75c003c696d2@mail.gmail.com>

Guys, you're wonderful!

I just tried your suggestions (but I couldnt get the AP log - my
neighbor is gone).

right, Bryan first
> What kernel version is this?
2.6.12-9-686

> -Dwext instead of -Dndiswrapper

same problem with
> SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
but additional:
> Driver does not support WPA.
and it seems to me that it wouldnt work: it fails already in state ASSOCIATING.

thanks so far! do I need addional setup before using the wext driver?

seb

terminal output:
-----
seb at ubuntu-seb:~$ sudo wpa_supplicant -i wlan0 -D wext -c
/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 17 - start of a new network block
ssid - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
scan_ssid=1 (0x1)
proto: 0x1
key_mgmt: 0x2
PSK - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='WG-Netz'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: No such device
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:09:5b:45:df:68
wpa_driver_wext_set_wpa
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_countermeasures
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
wpa_driver_wext_set_drop_unencrypted
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
Scan timeout - try to get results
Received 2484 bytes of scan results (10 BSSes)
Scan results: 10
Selecting BSS from priority group 0
0: 00:04:0e:7e:49:32 ssid='WG-Netz' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:04:0e:7e:49:32 (SSID='WG-Netz' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WEXT auth param 6 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
State: SCANNING -> ASSOCIATING
wpa_driver_wext_associate
ioctl[SIOCSIWGENIE]: No such device
WEXT auth param 0 value 0x2 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 1 value 0x4 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 2 value 0x4 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 3 value 0x2 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 10 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 8 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=19
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING




On 3/14/06, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:
> On Tue, Mar 14, 2006 at 01:56:29PM +0100, Sebastian Eiser wrote:
> > SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
>
> What kernel version is this?  It might work better (especially if you're
> using the latest ndiswrapper) to use the wext driver in wpa_supplicant
> instead of the ndiswrapper driver.  (-Dwext instead of -Dndiswrapper)
>
> > and in the end:
> > WPA: Sending EAPOL-Key 2/4
> > >> all the time. It seems like the AP doesnt accept the key and
> > wouldnt let me connect. is there a way to check that in detail.
>
> Only if you can get at logs from the AP that would tell you why it's
> dropping the EAPOL-Key frame.  The most common reason is a mismatch in
> PSK values, but there are other reasons too.  I think looking into wext
> (assuming you have a new enough kernel) would be a bit more promising,
> though.
>
>
>
>



From sebastian.eiser  Tue Mar 14 11:46:02 2006
From: sebastian.eiser (Sebastian Eiser)
Date: Tue, 14 Mar 2006 20:46:02 +0100
Subject: WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper,
	ubuntu, WG511 (v1)
In-Reply-To: <4416DD2A.9070305@yahoo.de>
References: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>
	<4416DD2A.9070305@yahoo.de>
Message-ID: <1fe8db230603141146wdea218aj651f95dbf5118150@mail.gmail.com>

Hi again, thanks for the reply,

here are the requested outputs:
>  wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0

eapol_version=1
ap_scan=1
fast_reauth=1

network={
	ssid="WG-Netz"
	scan_ssid=1
#	pairwise=TKIP
	proto=WPA
	key_mgmt=WPA-PSK
	psk=7b3b4b.. [63 char removed]
}

> dmesg | grep ndiswrapper
seb at ubuntu-seb:~$ dmesg | grep ndiswrapper
[4294699.902000] ndiswrapper version 1.1 loaded (preempt=no,smp=no)
[4294710.088000] ndiswrapper: driver netwg511 (NETGEAR,02/16/2005,
3.03.20.0) loaded
[4294710.089000] ndiswrapper: using irq 11
[4294713.906000] wlan0: ndiswrapper ethernet device 00:09:5b:45:df:68
using driver netwg511, configuration file 1260:3890:1385:4800.5.conf

> lsmod
seb at ubuntu-seb:~$ lsmod
Module                  Size  Used by
ipv6                  251200  6
rfcomm                 38460  0
l2cap                  24740  5 rfcomm
bluetooth              48356  4 rfcomm,l2cap
speedstep_ich           5164  0
speedstep_lib           4228  1 speedstep_ich
cpufreq_userspace       4316  1
cpufreq_stats           5252  0
freq_table              4388  2 speedstep_ich,cpufreq_stats
cpufreq_powersave       1696  0
cpufreq_ondemand        6044  0
cpufreq_conservative     6948  0
pcmcia                 26568  2
radeon                 78080  1
drm                    64884  2 radeon
video                  15748  0
tc1100_wmi              6692  0
sony_acpi               5324  0
pcc_acpi               11104  0
hotkey                  9284  0
dev_acpi               11108  0
i2c_acpi_ec             5472  0
i2c_core               21200  1 i2c_acpi_ec
button                  6480  0
battery                 9348  0
container               4384  0
ac                      4708  0
af_packet              21768  2
prism54                55912  0
firmware_class          9952  1 prism54
rtc                    12344  0
pcspkr                  3396  0
irtty_sir               8512  0
sir_dev                18444  1 irtty_sir
irda                  187612  2 irtty_sir,sir_dev
crc_ccitt               1984  1 irda
floppy                 59124  0
yenta_socket           25292  2
rsrc_nonstatic         13376  1 yenta_socket
pcmcia_core            49348  3 pcmcia,yenta_socket,rsrc_nonstatic
snd_intel8x0           33248  1
snd_ac97_codec         83932  1 snd_intel8x0
snd_pcm_oss            52704  0
snd_mixer_oss          19296  1 snd_pcm_oss
snd_pcm                88840  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer              24164  1 snd_pcm
snd                    54884  8
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore               9600  1 snd
snd_page_alloc         10600  2 snd_intel8x0,snd_pcm
tpm_atmel               5536  0
tpm_nsc                 6656  0
tpm                     9888  2 tpm_atmel,tpm_nsc
pci_hotplug            27508  0
intel_agp              23164  1
agpgart                34792  2 drm,intel_agp
nls_utf8                2016  2
nls_cp437               5664  2
vfat                   13440  2
fat                    52668  1 vfat
dm_mod                 57692  1
joydev                  9984  0
tsdev                   7776  0
evdev                   9664  1
ndiswrapper           130824  0
psmouse                30116  0
mousedev               11616  1
parport_pc             35236  1
lp                     12292  0
parport                35912  2 parport_pc,lp
sd_mod                 19120  2
md                     45584  0
ext3                  136264  1
jbd                    54776  1 ext3
mbcache                 9252  1 ext3
thermal                13000  0
processor              22812  1 thermal
fan                     4484  0
usb_storage            74112  2
scsi_mod              135688  2 sd_mod,usb_storage
usbhid                 35264  0
ehci_hcd               34248  0
ohci_hcd               20644  0
usbcore               117884  6
ndiswrapper,usb_storage,usbhid,ehci_hcd,ohci_hcde100                  
34976  0
mii                     5696  1 e100
ide_disk               18464  4
ide_generic             1376  0
piix                   10372  1
ide_core              138772  4 usb_storage,ide_disk,ide_generic,piix
unix                   26896  656
capability              4712  0
commoncap               6816  1 capability
vesafb                  7992  1
vgastate                9664  0
softcursor              2272  1 vesafb
cfbimgblt               2944  1 vesafb
cfbfillrect             3872  1 vesafb
cfbcopyarea             4608  1 vesafb
fbcon                  38496  72
tileblit                2368  1 fbcon
font                    8224  1 fbcon
bitblit                 5632  1 fbcon

 ... lsmod says that the prism54 driver is still loaded.... does this
any good / bad? I believe it gets loaded automatically while booting.

> ifconfig (wpa_supplicant ist trying to connect in other terminal)
seb at ubuntu-seb:~$ ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:09:5B:45:DF:68
          inet6 addr: fe80::209:5bff:fe45:df68/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15707 (15.3 KiB)  TX bytes:2193 (2.1 KiB)
          Memory:20800000-20801fff

seb at ubuntu-seb:~$ iwconfig
wlan0     IEEE 802.11g  ESSID:"WG-Netz"
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:04:0E:7E:49:32
          Bit Rate:24 Mb/s   Tx-Power:32 dBm
          RTS thr:2347 B   Fragment thr:2346 B
          Power Management:off
          Link Quality:91/100  Signal level:-66 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:46  Invalid misc:6107   Missed beacon:0

thanks to both of you for your help so far. thanks!

seb

On 3/14/06, Gentoopower <gentoopower at yahoo.de> wrote:
> What is the output of:
>
> dmesg | grep ndiswrapper
>
> and please supply your:
>
>  wpa_supplicant.conf
>
> output of lsmod
>
> and the output of /sbin/ifconfig after you started wpa_supplicant
>
>
>
> Sebastian Eiser wrote:
> > Hi all,
> >
> > I gratefully read on the wpa_supplicant homepage that I may use this
> > mailing list to ask topics not only related to hostap, but also e.g.
> > ndiswrapper in conjunction with wpa_supplicant, so I hope this is not
> > annoying for you...actually I couldnt get help in any kind of forum
> > for more that a week intensive posting - so I take this to the
> > experts.
> >  I've just searched the non-gzip'd archive, but my problem is slightly
> > different.
> > ---
> >
> > I'm trying to set up a wpa connection (Ubuntu 5.10) using the latest
> > releases of ndiswrapper and wpa_supplicant. The driver works fine with
> > wpa in windoze, and ndiswrapper confirms it correctly loaded (chipset
> > Intersil ISL3890 (netgear WG511 V1)).
> > if I do "wpa_supplicant -i wlan0 -D ndiswrapper -c
> > /etc/wpa_supplicant.conf -ddd" the 4WAY_HANDSHAKE state never
> > completes. when I read the output, several lines may indicate a faulty
> > setup (full output appended):
> >
> > ioctl[SIOCSIWPMKSA]: No such device
> >
> >>> this is not serious, afaik
> >>>
> > SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
> >
> >>> ? - is this due to a faulty key? windoze successfully uses a 63char
> >>>
> > ASCII code. I used wpa_passphrase to convert it to HEX.. anyway - it
> > continues:
> >
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
> >
> >>> 4 times....
> >>>
> >
> > and in the end:
> > WPA: Sending EAPOL-Key 2/4
> >
> >>> all the time. It seems like the AP doesnt accept the key and
> >>>
> > wouldnt let me connect. is there a way to check that in detail.
> >
> > I saw that Arjan van Bentem hostap at avbentem.dds.nl (post to the
> > maillist on Tue Apr 19 12:19:07 MDT 2005) had a quite similar problem
> > http://lists.shmoo.com/pipermail/hostap/2005-April/010113.html
> >
> > I hope (and still believe) I just made a dump mistake during the
> > configuration, but I've tried so hard and it seems that I'm not yet
> > skilled enough to solve it. that's why I'd greatly appreciate any
> > input to this topic.
> > actually my neighbor (I share my connection with him) is just laughing
> > at me: "why the hell dont you wanna use windows"... well, he dosent
> > know a thing.
> >
> > guys, I'm looking forward for you replies! feel free to request
> > further information... dont let me down, for my neighbors sake ;-)
> >
> > seb
> >
> > pasting complete terminal output:
> > ---
> > sudo wpa_supplicant -i wlan0 -D ndiswrapper -c /etc/wpa_supplicant.conf -ddd
> >
> > 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
> > fast_reauth=1
> > Line: 17 - start of a new network block
> > ssid - hexdump_ascii(len=7):
> >      57 47 2d 4e 65 74 7a                              WG-Netz
> > scan_ssid=1 (0x1)
> > proto: 0x1
> > key_mgmt: 0x2
> > PSK - hexdump(len=32): [REMOVED]
> > Priority group 0
> >    id=0 ssid='WG-Netz'
> > Initializing interface (2) 'wlan0'
> > EAPOL: SUPP_PAE entering state DISCONNECTED
> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > EAPOL: SUPP_BE entering state INITIALIZE
> > EAP: EAP entering state DISABLED
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > ioctl[SIOCSIWPMKSA]: No such device
> > SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
> > Own MAC address: 00:09:5b:45:df:68
> > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
> > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
> > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
> > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
> > Setting scan request: 0 sec 100000 usec
> > Wireless event: cmd=0x8b06 len=8
> > RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> > RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> > Wireless event: cmd=0x8b2a len=12
> > Wireless event: cmd=0x8b2a len=12
> > Wireless event: cmd=0x8b2a len=12
> > Wireless event: cmd=0x8b2a len=12
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (specific SSID)
> > Scan SSID - hexdump_ascii(len=7):
> >      57 47 2d 4e 65 74 7a                              WG-Netz
> > Scan timeout - try to get results
> > Received 2307 bytes of scan results (9 BSSes)
> > Scan results: 9
> > Selecting BSS from priority group 0
> > 0: 00:04:0e:7e:49:32 ssid='WG-Netz' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
> >    selected
> > Trying to associate with 00:04:0e:7e:49:32 (SSID='WG-Netz' freq=2447 MHz)
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > WPA: using IEEE 802.11i/D3.0
> > WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
> > WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
> > 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
> > WPA: clearing AP RSN IE
> > WPA: using GTK TKIP
> > WPA: using PTK TKIP
> > WPA: using KEY_MGMT WPA-PSK
> > WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
> > 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> > No keys have been configured - skip key clearing
> > State: SCANNING -> ASSOCIATING
> > Setting authentication timeout: 5 sec 0 usec
> > EAPOL: External notification - EAP success=0
> > EAPOL: External notification - EAP fail=0
> > EAPOL: External notification - portControl=Auto
> > Wireless event: cmd=0x8c02 len=169
> > Custom wireless event:
> > 'ASSOCINFO(ReqIEs=000757472d4e65747a010402040b1632080c1218243048606cdd160050f20101000050f20201000050f20201000050f202
> > RespIEs=010482848b9632088c129824b048606c)'
> > Association info event
> > req_ies - hexdump(len=49): 00 07 57 47 2d 4e 65 74 7a 01 04 02 04 0b
> > 16 32 08 0c 12 18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02
> > 01 00 00 50 f2 02 01 00 00 50 f2 02
> > resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 8c 12 98 24 b0 48 60 6c
> > WPA: set own WPA/RSN 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
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:04:0e:7e:49:32
> > State: ASSOCIATING -> ASSOCIATED
> > Associated to a new BSS: BSSID=00:04:0e:7e:49:32
> > No keys have been configured - skip key clearing
> > Associated with 00:04:0e:7e:49:32
> > WPA: Association event - clear replay counter
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > EAPOL: External notification - EAP success=0
> > EAPOL: External notification - portEnabled=1
> > EAPOL: SUPP_PAE entering state CONNECTING
> > EAPOL: txStart
> > WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
> > EAPOL: SUPP_BE entering state IDLE
> > EAP: EAP entering state INITIALIZE
> > EAP: EAP entering state IDLE
> > Setting authentication timeout: 10 sec 0 usec
> > RX EAPOL from 00:04:0e:7e:49:32
> > RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
> > 00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17 e3 13 ae
> > c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Setting authentication timeout: 10 sec 0 usec
> > IEEE 802.1X RX: version=1 type=3 length=95
> >   EAPOL-Key type=254
> > WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
> > 00 00 00 00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17
> > e3 13 ae c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > State: ASSOCIATED -> 4WAY_HANDSHAKE
> > WPA: RX message 1 of 4-Way Handshake from 00:04:0e:7e:49:32 (ver=1)
> > WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
> > 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> > WPA: Renewed SNonce - hexdump(len=32): 1d 3d 6d 10 76 eb c3 b0 c9 4a
> > 39 8c 03 23 77 53 9b ed 8d 45 cf 8d 17 fa 78 4d 8c 4b 60 67 65 30
> > WPA: PMK - hexdump(len=32): [REMOVED]
> > WPA: PTK - hexdump(len=64): [REMOVED]
> > WPA: Sending EAPOL-Key 2/4
> > WPA: TX EAPOL-Key - hexdump(len=123): 01 03 ...
> > <<<<< to be repeated all the time .... (the hexdump values change, though)
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
> >
> >
>
>
>
>
>
> ___________________________________________________________
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>



From gentoopower  Tue Mar 14 12:20:05 2006
From: gentoopower (Gentoopower)
Date: Tue, 14 Mar 2006 21:20:05 +0100
Subject: WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper, 
	ubuntu, WG511 (v1)
In-Reply-To: <1fe8db230603141146wdea218aj651f95dbf5118150@mail.gmail.com>
References: <1fe8db230603140456h1448bacbr4663b5392c8efe11@mail.gmail.com>	
	<4416DD2A.9070305@yahoo.de>
	<1fe8db230603141146wdea218aj651f95dbf5118150@mail.gmail.com>
Message-ID: <44172575.3000500@yahoo.de>

Okay, get a newer ndiswrapper version yours is 1.1, latest is 1.10 and I
think around 1.1 there were problems with some netgear cards.

http://sourceforge.net/projects/ndiswrapper/

The installation is very easy, just extract run make and make install as
root, reboot and you should see that ndiswrapper reports the new version:

dmesg | grep ndiswrapper


Then try again.

Sebastian Eiser wrote:
> Hi again, thanks for the reply,
>
> here are the requested outputs:
>   
>>  wpa_supplicant.conf
>>     
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
>
> eapol_version=1
> ap_scan=1
> fast_reauth=1
>
> network={
> 	ssid="WG-Netz"
> 	scan_ssid=1
> #	pairwise=TKIP
> 	proto=WPA
> 	key_mgmt=WPA-PSK
> 	psk=7b3b4b.. [63 char removed]
> }
>
>   
>> dmesg | grep ndiswrapper
>>     
> seb at ubuntu-seb:~$ dmesg | grep ndiswrapper
> [4294699.902000] ndiswrapper version 1.1 loaded (preempt=no,smp=no)
> [4294710.088000] ndiswrapper: driver netwg511 (NETGEAR,02/16/2005,
> 3.03.20.0) loaded
> [4294710.089000] ndiswrapper: using irq 11
> [4294713.906000] wlan0: ndiswrapper ethernet device 00:09:5b:45:df:68
> using driver netwg511, configuration file 1260:3890:1385:4800.5.conf
>
>   
>> lsmod
>>     
> seb at ubuntu-seb:~$ lsmod
> Module                  Size  Used by
> ipv6                  251200  6
> rfcomm                 38460  0
> l2cap                  24740  5 rfcomm
> bluetooth              48356  4 rfcomm,l2cap
> speedstep_ich           5164  0
> speedstep_lib           4228  1 speedstep_ich
> cpufreq_userspace       4316  1
> cpufreq_stats           5252  0
> freq_table              4388  2 speedstep_ich,cpufreq_stats
> cpufreq_powersave       1696  0
> cpufreq_ondemand        6044  0
> cpufreq_conservative     6948  0
> pcmcia                 26568  2
> radeon                 78080  1
> drm                    64884  2 radeon
> video                  15748  0
> tc1100_wmi              6692  0
> sony_acpi               5324  0
> pcc_acpi               11104  0
> hotkey                  9284  0
> dev_acpi               11108  0
> i2c_acpi_ec             5472  0
> i2c_core               21200  1 i2c_acpi_ec
> button                  6480  0
> battery                 9348  0
> container               4384  0
> ac                      4708  0
> af_packet              21768  2
> prism54                55912  0
> firmware_class          9952  1 prism54
> rtc                    12344  0
> pcspkr                  3396  0
> irtty_sir               8512  0
> sir_dev                18444  1 irtty_sir
> irda                  187612  2 irtty_sir,sir_dev
> crc_ccitt               1984  1 irda
> floppy                 59124  0
> yenta_socket           25292  2
> rsrc_nonstatic         13376  1 yenta_socket
> pcmcia_core            49348  3 pcmcia,yenta_socket,rsrc_nonstatic
> snd_intel8x0           33248  1
> snd_ac97_codec         83932  1 snd_intel8x0
> snd_pcm_oss            52704  0
> snd_mixer_oss          19296  1 snd_pcm_oss
> snd_pcm                88840  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
> snd_timer              24164  1 snd_pcm
> snd                    54884  8
> snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
> soundcore               9600  1 snd
> snd_page_alloc         10600  2 snd_intel8x0,snd_pcm
> tpm_atmel               5536  0
> tpm_nsc                 6656  0
> tpm                     9888  2 tpm_atmel,tpm_nsc
> pci_hotplug            27508  0
> intel_agp              23164  1
> agpgart                34792  2 drm,intel_agp
> nls_utf8                2016  2
> nls_cp437               5664  2
> vfat                   13440  2
> fat                    52668  1 vfat
> dm_mod                 57692  1
> joydev                  9984  0
> tsdev                   7776  0
> evdev                   9664  1
> ndiswrapper           130824  0
> psmouse                30116  0
> mousedev               11616  1
> parport_pc             35236  1
> lp                     12292  0
> parport                35912  2 parport_pc,lp
> sd_mod                 19120  2
> md                     45584  0
> ext3                  136264  1
> jbd                    54776  1 ext3
> mbcache                 9252  1 ext3
> thermal                13000  0
> processor              22812  1 thermal
> fan                     4484  0
> usb_storage            74112  2
> scsi_mod              135688  2 sd_mod,usb_storage
> usbhid                 35264  0
> ehci_hcd               34248  0
> ohci_hcd               20644  0
> usbcore               117884  6
> ndiswrapper,usb_storage,usbhid,ehci_hcd,ohci_hcde100                  
> 34976  0
> mii                     5696  1 e100
> ide_disk               18464  4
> ide_generic             1376  0
> piix                   10372  1
> ide_core              138772  4 usb_storage,ide_disk,ide_generic,piix
> unix                   26896  656
> capability              4712  0
> commoncap               6816  1 capability
> vesafb                  7992  1
> vgastate                9664  0
> softcursor              2272  1 vesafb
> cfbimgblt               2944  1 vesafb
> cfbfillrect             3872  1 vesafb
> cfbcopyarea             4608  1 vesafb
> fbcon                  38496  72
> tileblit                2368  1 fbcon
> font                    8224  1 fbcon
> bitblit                 5632  1 fbcon
>
>  ... lsmod says that the prism54 driver is still loaded.... does this
> any good / bad? I believe it gets loaded automatically while booting.
>
>   
>> ifconfig (wpa_supplicant ist trying to connect in other terminal)
>>     
> seb at ubuntu-seb:~$ ifconfig
>
> wlan0     Link encap:Ethernet  HWaddr 00:09:5B:45:DF:68
>           inet6 addr: fe80::209:5bff:fe45:df68/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:139 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:15707 (15.3 KiB)  TX bytes:2193 (2.1 KiB)
>           Memory:20800000-20801fff
>
> seb at ubuntu-seb:~$ iwconfig
> wlan0     IEEE 802.11g  ESSID:"WG-Netz"
>           Mode:Managed  Frequency:2.447 GHz  Access Point: 00:04:0E:7E:49:32
>           Bit Rate:24 Mb/s   Tx-Power:32 dBm
>           RTS thr:2347 B   Fragment thr:2346 B
>           Power Management:off
>           Link Quality:91/100  Signal level:-66 dBm  Noise level:-256 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:46  Invalid misc:6107   Missed beacon:0
>
> thanks to both of you for your help so far. thanks!
>
> seb
>
> On 3/14/06, Gentoopower <gentoopower at yahoo.de> wrote:
>   
>> What is the output of:
>>
>> dmesg | grep ndiswrapper
>>
>> and please supply your:
>>
>>  wpa_supplicant.conf
>>
>> output of lsmod
>>
>> and the output of /sbin/ifconfig after you started wpa_supplicant
>>
>>
>>
>> Sebastian Eiser wrote:
>>     
>>> Hi all,
>>>
>>> I gratefully read on the wpa_supplicant homepage that I may use this
>>> mailing list to ask topics not only related to hostap, but also e.g.
>>> ndiswrapper in conjunction with wpa_supplicant, so I hope this is not
>>> annoying for you...actually I couldnt get help in any kind of forum
>>> for more that a week intensive posting - so I take this to the
>>> experts.
>>>  I've just searched the non-gzip'd archive, but my problem is slightly
>>> different.
>>> ---
>>>
>>> I'm trying to set up a wpa connection (Ubuntu 5.10) using the latest
>>> releases of ndiswrapper and wpa_supplicant. The driver works fine with
>>> wpa in windoze, and ndiswrapper confirms it correctly loaded (chipset
>>> Intersil ISL3890 (netgear WG511 V1)).
>>> if I do "wpa_supplicant -i wlan0 -D ndiswrapper -c
>>> /etc/wpa_supplicant.conf -ddd" the 4WAY_HANDSHAKE state never
>>> completes. when I read the output, several lines may indicate a faulty
>>> setup (full output appended):
>>>
>>> ioctl[SIOCSIWPMKSA]: No such device
>>>
>>>       
>>>>> this is not serious, afaik
>>>>>
>>>>>           
>>> SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
>>>
>>>       
>>>>> ? - is this due to a faulty key? windoze successfully uses a 63char
>>>>>
>>>>>           
>>> ASCII code. I used wpa_passphrase to convert it to HEX.. anyway - it
>>> continues:
>>>
>>> ioctl[SIOCSIWENCODEEXT]: No such device
>>> Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>>>
>>>       
>>>>> 4 times....
>>>>>
>>>>>           
>>> and in the end:
>>> WPA: Sending EAPOL-Key 2/4
>>>
>>>       
>>>>> all the time. It seems like the AP doesnt accept the key and
>>>>>
>>>>>           
>>> wouldnt let me connect. is there a way to check that in detail.
>>>
>>> I saw that Arjan van Bentem hostap at avbentem.dds.nl (post to the
>>> maillist on Tue Apr 19 12:19:07 MDT 2005) had a quite similar problem
>>> http://lists.shmoo.com/pipermail/hostap/2005-April/010113.html
>>>
>>> I hope (and still believe) I just made a dump mistake during the
>>> configuration, but I've tried so hard and it seems that I'm not yet
>>> skilled enough to solve it. that's why I'd greatly appreciate any
>>> input to this topic.
>>> actually my neighbor (I share my connection with him) is just laughing
>>> at me: "why the hell dont you wanna use windows"... well, he dosent
>>> know a thing.
>>>
>>> guys, I'm looking forward for you replies! feel free to request
>>> further information... dont let me down, for my neighbors sake ;-)
>>>
>>> seb
>>>
>>> pasting complete terminal output:
>>> ---
>>> sudo wpa_supplicant -i wlan0 -D ndiswrapper -c /etc/wpa_supplicant.conf -ddd
>>>
>>> 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
>>> fast_reauth=1
>>> Line: 17 - start of a new network block
>>> ssid - hexdump_ascii(len=7):
>>>      57 47 2d 4e 65 74 7a                              WG-Netz
>>> scan_ssid=1 (0x1)
>>> proto: 0x1
>>> key_mgmt: 0x2
>>> PSK - hexdump(len=32): [REMOVED]
>>> Priority group 0
>>>    id=0 ssid='WG-Netz'
>>> Initializing interface (2) 'wlan0'
>>> EAPOL: SUPP_PAE entering state DISCONNECTED
>>> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
>>> EAPOL: SUPP_BE entering state INITIALIZE
>>> EAP: EAP entering state DISABLED
>>> EAPOL: External notification - portEnabled=0
>>> EAPOL: External notification - portValid=0
>>> ioctl[SIOCSIWPMKSA]: No such device
>>> SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
>>> Own MAC address: 00:09:5b:45:df:68
>>> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
>>> ioctl[SIOCSIWENCODEEXT]: No such device
>>> Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>>> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
>>> ioctl[SIOCSIWENCODEEXT]: No such device
>>> Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>>> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
>>> ioctl[SIOCSIWENCODEEXT]: No such device
>>> Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>>> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
>>> ioctl[SIOCSIWENCODEEXT]: No such device
>>> Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
>>> Setting scan request: 0 sec 100000 usec
>>> Wireless event: cmd=0x8b06 len=8
>>> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>>> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
>>> Wireless event: cmd=0x8b2a len=12
>>> Wireless event: cmd=0x8b2a len=12
>>> Wireless event: cmd=0x8b2a len=12
>>> Wireless event: cmd=0x8b2a len=12
>>> State: DISCONNECTED -> SCANNING
>>> Starting AP scan (specific SSID)
>>> Scan SSID - hexdump_ascii(len=7):
>>>      57 47 2d 4e 65 74 7a                              WG-Netz
>>> Scan timeout - try to get results
>>> Received 2307 bytes of scan results (9 BSSes)
>>> Scan results: 9
>>> Selecting BSS from priority group 0
>>> 0: 00:04:0e:7e:49:32 ssid='WG-Netz' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
>>>    selected
>>> Trying to associate with 00:04:0e:7e:49:32 (SSID='WG-Netz' freq=2447 MHz)
>>> Cancelling scan request
>>> WPA: clearing own WPA/RSN IE
>>> Automatic auth_alg selection: 0x1
>>> WPA: using IEEE 802.11i/D3.0
>>> WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
>>> WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
>>> 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
>>> WPA: clearing AP RSN IE
>>> WPA: using GTK TKIP
>>> WPA: using PTK TKIP
>>> WPA: using KEY_MGMT WPA-PSK
>>> WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
>>> 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
>>> No keys have been configured - skip key clearing
>>> State: SCANNING -> ASSOCIATING
>>> Setting authentication timeout: 5 sec 0 usec
>>> EAPOL: External notification - EAP success=0
>>> EAPOL: External notification - EAP fail=0
>>> EAPOL: External notification - portControl=Auto
>>> Wireless event: cmd=0x8c02 len=169
>>> Custom wireless event:
>>> 'ASSOCINFO(ReqIEs=000757472d4e65747a010402040b1632080c1218243048606cdd160050f20101000050f20201000050f20201000050f202
>>> RespIEs=010482848b9632088c129824b048606c)'
>>> Association info event
>>> req_ies - hexdump(len=49): 00 07 57 47 2d 4e 65 74 7a 01 04 02 04 0b
>>> 16 32 08 0c 12 18 24 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02
>>> 01 00 00 50 f2 02 01 00 00 50 f2 02
>>> resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 8c 12 98 24 b0 48 60 6c
>>> WPA: set own WPA/RSN 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
>>> Wireless event: cmd=0x8b15 len=20
>>> Wireless event: new AP: 00:04:0e:7e:49:32
>>> State: ASSOCIATING -> ASSOCIATED
>>> Associated to a new BSS: BSSID=00:04:0e:7e:49:32
>>> No keys have been configured - skip key clearing
>>> Associated with 00:04:0e:7e:49:32
>>> WPA: Association event - clear replay counter
>>> EAPOL: External notification - portEnabled=0
>>> EAPOL: External notification - portValid=0
>>> EAPOL: External notification - EAP success=0
>>> EAPOL: External notification - portEnabled=1
>>> EAPOL: SUPP_PAE entering state CONNECTING
>>> EAPOL: txStart
>>> WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
>>> EAPOL: SUPP_BE entering state IDLE
>>> EAP: EAP entering state INITIALIZE
>>> EAP: EAP entering state IDLE
>>> Setting authentication timeout: 10 sec 0 usec
>>> RX EAPOL from 00:04:0e:7e:49:32
>>> RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00
>>> 00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17 e3 13 ae
>>> c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00 00 00 00
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> Setting authentication timeout: 10 sec 0 usec
>>> IEEE 802.1X RX: version=1 type=3 length=95
>>>   EAPOL-Key type=254
>>> WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00
>>> 00 00 00 00 00 01 ba 20 39 67 e7 f2 ee 4c 67 b8 96 16 bc 0d ea 04 17
>>> e3 13 ae c6 67 28 3d f7 a2 ab 3e 98 14 20 86 00 00 00 00 00 00 00 00
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> State: ASSOCIATED -> 4WAY_HANDSHAKE
>>> WPA: RX message 1 of 4-Way Handshake from 00:04:0e:7e:49:32 (ver=1)
>>> WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
>>> 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
>>> WPA: Renewed SNonce - hexdump(len=32): 1d 3d 6d 10 76 eb c3 b0 c9 4a
>>> 39 8c 03 23 77 53 9b ed 8d 45 cf 8d 17 fa 78 4d 8c 4b 60 67 65 30
>>> WPA: PMK - hexdump(len=32): [REMOVED]
>>> WPA: PTK - hexdump(len=64): [REMOVED]
>>> WPA: Sending EAPOL-Key 2/4
>>> WPA: TX EAPOL-Key - hexdump(len=123): 01 03 ...
>>> <<<<< to be repeated all the time .... (the hexdump values change, though)
>>> _______________________________________________
>>> HostAP mailing list
>>> HostAP at shmoo.com
>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>>
>>>
>>>       
>>
>>
>>
>> ___________________________________________________________
>> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>>
>>
>>     
>
>
>   



	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de



From fatimapeter  Tue Mar 14 12:49:03 2006
From: fatimapeter (Fatima Peter)
Date: Tue, 14 Mar 2006 12:49:03 -0800
Subject: hostapd-0.4.8 problem
Message-ID: <BAY103-F149A487DCBD20A60B034DCAFE10@phx.gbl>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060314/dd6e9721/attachment.htm 


From jfb  Tue Mar 14 12:48:12 2006
From: jfb (Juan Felipe Botero)
Date: Tue, 14 Mar 2006 15:48:12 -0500
Subject: help with IMXL
Message-ID: <20060314204250.M64005@microe.udea.edu.co>


I, i really need some help:

I could compile the hostap driver with the path of the linux kernel of my embedded
system for a IMXL card based in a arm architecture.

when i compiled the kernel a folder called:
/lib/modules/2.6.11.4-csb/kernel/drivers/net/wireless was created in my normal Linux
system file, so i created and copied this folder in the linux file system of the
embedded architecture, but when i started the Linux again, the driver didn't work. i can
use the modprobe and it&#347; seems like there are no problems, but when i put in the command
line - ifconfig wlan0 up - the answer was - no such device -. I

I really don't know about that problem, if someone has worked in a IMXL card please help me
The compact flash card is a sinao NL-2511CF mercury, i know this card has a prism2 chipset
Please help me

lot of thanks 
--
Open WebMail Project (http://openwebmail.org)




From pelusitavali  Tue Mar 14 14:41:41 2006
From: pelusitavali (Pelusa Vali)
Date: Tue, 14 Mar 2006 22:41:41 +0000
Subject: cann't compile hostapd 0.5.1
Message-ID: <PM.22801.1142376101@pmweb18.uk1.bibliotech.net>

hi everybody, well after many tries and cann't compile hostapd 0.4.7 i decided compile 0.5.1, i get many errors and warnings, diferent from which i got with 0.4.7, when type make, get messages like this:

In file included from hostapd.c:16:
includes.h:25:20: warning: stdlib.h: No such file or directory
includes.h:26:19: warning: stdio.h: No such file or directory
includes.h:28:20: warning: string.h: No such file or directory
includes.h:30:20: warning: signal.h: No such file or directory
includes.h:31:23: warning: sys/types.h: No such file or directory
includes.h:32:19: warning: errno.h: No such file or directory
includes.h:34:19: warning: ctype.h: No such file or directory
includes.h:35:18: warning: time.h: No such file or directory
includes.h:38:20: warning: unistd.h: No such file or directory
includes.h:42:24: warning: sys/socket.h: No such file or directory
includes.h:43:24: warning: netinet/in.h: No such file or directory
includes.h:44:23: warning: arpa/inet.h: No such file or directory
includes.h:46:21: warning: sys/uio.h: No such file or directory
includes.h:47:22: warning: sys/time.h: No such file or directory
hostapd.c:17:20: warning: syslog.h: No such file or directory
In file included from hostapd.c:19:
eloop.h:78: error: syntax error before "size_t"
eloop.h:79: error: `eloop_register_event' declared as function returning a function
eloop.h:80: error: syntax error before "void"
eloop.h:90: error: syntax error before "size_t"
In file included from common.h:18,
                 from hostapd.h:4,
                 from hostapd.c:20:
os.h:75: error: syntax error before "size_t"
In file included from hostapd.h:4,
                 from hostapd.c:20:
common.h:21:20: warning: endian.h: No such file or directory

hostapd.c:1079: error: dereferencing pointer to incomplete type
hostapd.c:1080: error: dereferencing pointer to incomplete type
hostapd.c:1082: error: dereferencing pointer to incomplete type
hostapd.c:1093: error: `LOG_DAEMON' undeclared (first use in this function)

so, please, could any body tell me what is happening and if this have solution??  please i really need to use this software.
thanks for your help.



_______________________________________________________________ 
Halloween Trivia: Where does the custom of trick or treating come from?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=121




From cristian.ionescu-idbohrn  Tue Mar 14 14:50:25 2006
From: cristian.ionescu-idbohrn (Cristian Ionescu-Idbohrn)
Date: Tue, 14 Mar 2006 23:50:25 +0100 (CET)
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <PM.22801.1142376101@pmweb18.uk1.bibliotech.net>
References: <PM.22801.1142376101@pmweb18.uk1.bibliotech.net>
Message-ID: <0603142347180.7943@somehost>

On Tue, 14 Mar 2006, Pelusa Vali wrote:

> hi everybody, well after many tries and cann't compile hostapd 0.4.7 i
> decided compile 0.5.1, i get many errors and warnings, diferent from
> which i got with 0.4.7, when type make, get messages like this:
>
> In file included from hostapd.c:16:
> includes.h:25:20: warning: stdlib.h: No such file or directory

[snip]

You seem to be missing the libc6-dev package.
What's your distribution?
What's your kernel version?


Cheers,
Cristian

-- 
supercomputer $400 million in gold bullion analyzer encryption
BLU-114/B LABLINK Soviet codes PLO IRA North Korea morse Yukon radar
NORAD



From espy  Tue Mar 14 18:03:23 2006
From: espy (Tony Espy)
Date: Tue, 14 Mar 2006 21:03:23 -0500
Subject: wpa_supplicant, hostap & virtual access points?
Message-ID: <441775EB.2050607@pepper.com>

I recently caught wind of something called 'Virtual Access Points' which 
allows a single access point to broadcast multiple ESSID utilizing a 
single BSSID.

I stumbled upon this because I was doing some testing where I was 
toggling the broadcastESSID setting of an access point and noticed that 
at one point I received two networks in the scan results from 
wpa_supplicant with the same BSSID.  One had a null ESSID, the other had 
it set.

I took a look at the hostap driver code (prism2_translate_scan() ) and 
it looks like if driver is configured for WPA, it will allow multiple 
scan results to be returned with the same BSSID.

My questions are:

1. How prevalent is this kind of configuration and does it really follow 
the 802.11 specification?

2. Does wpa_supplicant support this kind of configuration?

Thanks,
Tony Espy
Pepper Computer




From jim  Tue Mar 14 18:12:05 2006
From: jim (Jim Thompson)
Date: Tue, 14 Mar 2006 16:12:05 -1000
Subject: wpa_supplicant, hostap & virtual access points?
In-Reply-To: <441775EB.2050607@pepper.com>
References: <441775EB.2050607@pepper.com>
Message-ID: <441777F5.4080804@netgate.com>

Tony Espy wrote:

>I recently caught wind of something called 'Virtual Access Points' which 
>allows a single access point to broadcast multiple ESSID utilizing a 
>single BSSID.
>
>I stumbled upon this because I was doing some testing where I was 
>toggling the broadcastESSID setting of an access point and noticed that 
>at one point I received two networks in the scan results from 
>wpa_supplicant with the same BSSID.  One had a null ESSID, the other had 
>it set.
>
>I took a look at the hostap driver code (prism2_translate_scan() ) and 
>it looks like if driver is configured for WPA, it will allow multiple 
>scan results to be returned with the same BSSID.
>
>My questions are:
>
>1. How prevalent is this kind of configuration and does it really follow 
>the 802.11 specification?
>  
>
its within 802.11 spec.  (I had the idea in 1999 or possibly 1998.)  Its
(correctly) implemented
in the madwifi drive and the devicescape code.

You can do multiple BSSIDs on some chipsets too.

>2. Does wpa_supplicant support this kind of configuration?
>
no, but nothing prevents you running two copies.




From jkmaline  Tue Mar 14 18:46:30 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Mar 2006 18:46:30 -0800
Subject: wpa_supplicant, hostap & virtual access points?
In-Reply-To: <441775EB.2050607@pepper.com>
References: <441775EB.2050607@pepper.com>
Message-ID: <20060315024629.GA9384@jm.kir.nu>

On Tue, Mar 14, 2006 at 09:03:23PM -0500, Tony Espy wrote:

> I recently caught wind of something called 'Virtual Access Points' which 
> allows a single access point to broadcast multiple ESSID utilizing a 
> single BSSID.

> 1. How prevalent is this kind of configuration and does it really follow 
> the 802.11 specification?

There are number of implementations of multiple SSID per BSSID type of
virtual AP and couple of multiple BSSIDs per a radio. I would assume
someone can find a clause in 802.11 that would be against something that
is done, especially so for multi-SSID case, but at least some
combinations of security modes in multi-SSID work find with most
clients. Multi-BSSID looks like multiple devices to a client, so it
allows even more transparent virtual AP implementation.

> 2. Does wpa_supplicant support this kind of configuration?

Yes it does, as long as the driver allows this to be done. Multi-SSID
looks somewhat like hidden SSID, so wpa_supplicant needs to be
configured to either use ap_scan=2 mode or scan_ssid=1 if the driver
supports that. Multi-BSSID case does not require any special
configuration since that looks exactly like multiple devices on
everything that wpa_supplicant would care about.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 14 18:49:36 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Mar 2006 18:49:36 -0800
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <PM.22801.1142376101@pmweb18.uk1.bibliotech.net>
References: <PM.22801.1142376101@pmweb18.uk1.bibliotech.net>
Message-ID: <20060315024936.GB9384@jm.kir.nu>

On Tue, Mar 14, 2006 at 10:41:41PM +0000, Pelusa Vali wrote:
> hi everybody, well after many tries and cann't compile hostapd 0.4.7 i decided compile 0.5.1, i get many errors and warnings, diferent from which i got with 0.4.7, when type make, get messages like this:
> 
> In file included from hostapd.c:16:
> includes.h:25:20: warning: stdlib.h: No such file or directory

Can you please include the full 'make' output, including the compiler
command line. Please also send the .config file that you used here. This
stdlib.h is very basic include file and either there is something
horribly wrong with the build tools on that host or something is
misconfigured to make C pre-processor not find the header files.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 14 18:53:09 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Mar 2006 18:53:09 -0800
Subject: hostapd-0.4.8 problem
In-Reply-To: <BAY103-F149A487DCBD20A60B034DCAFE10@phx.gbl>
References: <BAY103-F149A487DCBD20A60B034DCAFE10@phx.gbl>
Message-ID: <20060315025309.GC9384@jm.kir.nu>

On Tue, Mar 14, 2006 at 12:49:03PM -0800, Fatima Peter wrote:

> <P>When I use interface=ath1 in hostapd.conf, I get the following error message:

> <P>===================================================<BR>#TODO: wlan0 fails in icotl() calls. change it <BR>#interface=wlan0<BR>interface=ath1<BR>bridge=br0</P>
> <P>driver=hostap</P>


Please don't send HTML-only messages. They look quite horrible when
viewed with a real email client that does not try to behave like a web
browser..

That driver=hostap line is incorrect since you seem to be using madwifi
driver. It should be replaced with driver=madwifi in this case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 14 19:16:25 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Mar 2006 19:16:25 -0800
Subject: [2.6 patch] hostap_{pci,plx}.c: fix memory leaks
In-Reply-To: <20060313222841.GQ13973@stusta.de>
References: <20060313222841.GQ13973@stusta.de>
Message-ID: <20060315031625.GE9384@jm.kir.nu>

On Mon, Mar 13, 2006 at 11:28:41PM +0100, Adrian Bunk wrote:
> This patch fixes two memotry leaks spotted by the Coverity checker.

Thanks. I'll make a bit different patch to resolve this and related PCI
"leaks" in one change. I'm going through the Coverity reports for Host
AP driver, so I'll include other fixes in a patch set, too.

-- 
Jouni Malinen                                            PGP id EFC895FA



From pelusitavali  Tue Mar 14 21:41:36 2006
From: pelusitavali (Pelusa Vali)
Date: Wed, 15 Mar 2006 05:41:36 +0000
Subject: cann't compile hostapd 0.5.1
Message-ID: <PM.14076.1142401296@pmweb6.uk1.bibliotech.net>

>hi everybody, well after many tries and cann't compile hostapd 0.4.7 i decided compile 0.5.1, i get many errors and warnings, diferent from which i got with 0.4.7, when type make, get messages like this:
>
>In file included from hostapd.c:16:
>includes.h:25:20: warning: stdlib.h: No such file or directory
>includes.h:26:19: warning: stdio.h: No such file or directory
>includes.h:28:20: warning: string.h: No such file or directory
>includes.h:30:20: warning: signal.h: No such file or directory
>includes.h:31:23: warning: sys/types.h: No such file or directory
>includes.h:32:19: warning: errno.h: No such file or directory
>includes.h:34:19: warning: ctype.h: No such file or directory
>includes.h:35:18: warning: time.h: No such file or directory
>includes.h:38:20: warning: unistd.h: No such file or directory
>includes.h:42:24: warning: sys/socket.h: No such file or directory
>includes.h:43:24: warning: netinet/in.h: No such file or directory
>includes.h:44:23: warning: arpa/inet.h: No such file or directory
>includes.h:46:21: warning: sys/uio.h: No such file or directory
>includes.h:47:22: warning: sys/time.h: No such file or directory
>hostapd.c:17:20: warning: syslog.h: No such file or directory
>In file included from hostapd.c:19:
>eloop.h:78: error: syntax error before "size_t"
>eloop.h:79: error: `eloop_register_event' declared as function returning a function
>eloop.h:80: error: syntax error before "void"
>eloop.h:90: error: syntax error before "size_t"
>In file included from common.h:18,
>                 from hostapd.h:4,
>                 from hostapd.c:20:
>os.h:75: error: syntax error before "size_t"
>In file included from hostapd.h:4,
>                 from hostapd.c:20:
>common.h:21:20: warning: endian.h: No such file or directory
>
>hostapd.c:1079: error: dereferencing pointer to incomplete type
>hostapd.c:1080: error: dereferencing pointer to incomplete type
>hostapd.c:1082: error: dereferencing pointer to incomplete type
>hostapd.c:1093: error: `LOG_DAEMON' undeclared (first use in this function)
>
>so, please, could any body tell me what is happening and if this have solution??  please i really need to use this software.
>thanks for your help.

>You seem to be missing the libc6-dev package.
>What's your distribution?
>What's your kernel version?
>

well, i use debian sarge, kernel 2.6.15 and do have installed libc6-dev package

thanks christian


_______________________________________________________________ 
How long is a 10-pin bowling lane? 60 feet, 80 feet or 100 feet? 

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=242




From fraxinus.excelsior  Wed Mar 15 00:23:32 2006
From: fraxinus.excelsior (Yasen Balev)
Date: Wed, 15 Mar 2006 10:23:32 +0200
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <PM.14076.1142401296@pmweb6.uk1.bibliotech.net>
References: <PM.14076.1142401296@pmweb6.uk1.bibliotech.net>
Message-ID: <2d1888f90603150023ud14a32ck@mail.gmail.com>

well, all those "no such file"s are in libc6-dev package. Something is
messed up with it.
Can you compile anything else (kernel does not count)


2006/3/15, Pelusa Vali <pelusitavali at postmaster.co.uk>:
> >hi everybody, well after many tries and cann't compile hostapd 0.4.7 i decided compile 0.5.1, i get many errors and warnings, diferent from which i got with 0.4.7, when type make, get messages like this:
> >
> >In file included from hostapd.c:16:
> >includes.h:25:20: warning: stdlib.h: No such file or directory
> >includes.h:26:19: warning: stdio.h: No such file or directory
> >includes.h:28:20: warning: string.h: No such file or directory
> >includes.h:30:20: warning: signal.h: No such file or directory
> >includes.h:31:23: warning: sys/types.h: No such file or directory
> >includes.h:32:19: warning: errno.h: No such file or directory
> >includes.h:34:19: warning: ctype.h: No such file or directory
> >includes.h:35:18: warning: time.h: No such file or directory
> >includes.h:38:20: warning: unistd.h: No such file or directory
> >includes.h:42:24: warning: sys/socket.h: No such file or directory
> >includes.h:43:24: warning: netinet/in.h: No such file or directory
> >includes.h:44:23: warning: arpa/inet.h: No such file or directory
> >includes.h:46:21: warning: sys/uio.h: No such file or directory
> >includes.h:47:22: warning: sys/time.h: No such file or directory
> >hostapd.c:17:20: warning: syslog.h: No such file or directory
> >In file included from hostapd.c:19:
> >eloop.h:78: error: syntax error before "size_t"
> >eloop.h:79: error: `eloop_register_event' declared as function returning a function
> >eloop.h:80: error: syntax error before "void"
> >eloop.h:90: error: syntax error before "size_t"
> >In file included from common.h:18,
> >                 from hostapd.h:4,
> >                 from hostapd.c:20:
> >os.h:75: error: syntax error before "size_t"
> >In file included from hostapd.h:4,
> >                 from hostapd.c:20:
> >common.h:21:20: warning: endian.h: No such file or directory
> >
> >hostapd.c:1079: error: dereferencing pointer to incomplete type
> >hostapd.c:1080: error: dereferencing pointer to incomplete type
> >hostapd.c:1082: error: dereferencing pointer to incomplete type
> >hostapd.c:1093: error: `LOG_DAEMON' undeclared (first use in this function)
> >
> >so, please, could any body tell me what is happening and if this have solution??  please i really need to use this software.
> >thanks for your help.
>
> >You seem to be missing the libc6-dev package.
> >What's your distribution?
> >What's your kernel version?
> >
>
> well, i use debian sarge, kernel 2.6.15 and do have installed libc6-dev package
>
> thanks christian
>
>
> _______________________________________________________________
> How long is a 10-pin bowling lane? 60 feet, 80 feet or 100 feet?
>
> postmaster.co.uk
> http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=242
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From garat  Wed Mar 15 00:44:49 2006
From: garat (Svata Dedic)
Date: Wed, 15 Mar 2006 09:44:49 +0100
Subject: Hostap & ifrename
Message-ID: <4417D401.8070507@volny.cz>

Hello,

I have troubles with hostap when using ifrename to rename interfaces at
boot. All the wifi and wlan devices are renamed OK and work nicely, but
the hostap information exported through /proc still use the old names
for devices (as detected when the driver first loads).

I am using hostap-0.4.4 - is there some fix for this issue in later
versions, so I should consider an upgrade ? There was a patch sent to
this list back in September 2005 I think, but the patch didn't work for
me: contents of /proc/net/hostap were screwed (duplicate directory names
etc).

Thanks!
-Svata

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



From cristian.ionescu-idbohrn  Wed Mar 15 00:50:55 2006
From: cristian.ionescu-idbohrn (Cristian Ionescu-Idbohrn)
Date: Wed, 15 Mar 2006 09:50:55 +0100 (CET)
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <2d1888f90603150023ud14a32ck@mail.gmail.com>
References: <PM.14076.1142401296@pmweb6.uk1.bibliotech.net>
	<2d1888f90603150023ud14a32ck@mail.gmail.com>
Message-ID: <0603150949050.13475@somehost>

On Wed, 15 Mar 2006, Yasen Balev wrote:

> well, all those "no such file"s are in libc6-dev package. Something
> is messed up with it.

Right. Those header files should be found under /usr/include op a
debian box.


Cheers,
Cristian



From pelusitavali  Wed Mar 15 03:05:07 2006
From: pelusitavali (Pelusa Vali)
Date: Wed, 15 Mar 2006 11:05:07 +0000
Subject: cann't compile hostapd 0.5.1
Message-ID: <PM.3256.1142420707@pmweb11.uk1.bibliotech.net>

On Wed, 15 Mar 2006 10:23:32 +0200 , "Yasen Balev" <fraxinus.excelsior at gmail.com>  wrote:
>well, all those "no such file"s are in libc6-dev package. Something is
>messed up with it.
>Can you compile anything else (kernel does not count)

thanks yassen, well in fact i could compile freeradius, madwifi-ng, but you are right, i don't have libc6-dev, i get this:

The following packages have unmet dependencies:
  libc6-dev: Depends: libc6 (= 2.3.2.ds1-22) but 2.3.6-3 is to be installed

well i think it's a very newbie error, could you please excuse??, but i'm really very newbie.!!
so, i installed it and again type make, now get this:

driver_madwifi.c:21:28: warning: include/compat.h: No such file or directory
driver_madwifi.c:22:32: warning: net80211/ieee80211.h: No such file or directorydriver_madwifi.c:28:39: warning: net80211/ieee80211_crypto.h: No such file or directory
driver_madwifi.c:29:38: warning: net80211/ieee80211_ioctl.h: No such file or directory
driver_madwifi.c: In function `set80211priv':
driver_madwifi.c:124: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in this function)
driver_madwifi.c:124: error: (Each undeclared identifier is reported only once
driver_madwifi.c:124: error: for each function it appears in.)
driver_madwifi.c:125: error: `IEEE80211_IOCTL_CHANLIST' undeclared (first use in this function)
driver_madwifi.c: In function `set80211param':
driver_madwifi.c:167: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in this function)
driver_madwifi.c: In function `madwifi_configure_wpa':
driver_madwifi.c:198: error: `IEEE80211_CIPHER_AES_CCM' undeclared (first use in this function)
driver_madwifi.c:201: error: `IEEE80211_CIPHER_TKIP' undeclared (first use in this function)
driver_madwifi.c:204: error: `IEEE80211_CIPHER_WEP' undeclared (first use in this function)
driver_madwifi.c:210: error: `IEEE80211_CIPHER_NONE' undeclared (first use in this function)
driver_madwifi.c:219: error: `IEEE80211_PARAM_MCASTCIPHER' undeclared (first use in this function)
driver_madwifi.c:226: error: `IEEE80211_PARAM_MCASTKEYLEN' undeclared (first use in this function)
driver_madwifi.c:241: error: `IEEE80211_PARAM_UCASTCIPHERS' undeclared (first use in this function)
driver_madwifi.c:249: error: `IEEE80211_PARAM_KEYMGTALGS' undeclared (first use in this function)
driver_madwifi.c:260: error: `IEEE80211_PARAM_RSNCAPS' undeclared (first use in this function)
driver_madwifi.c:267: error: `IEEE80211_PARAM_WPA' undeclared (first use in this function)
driver_madwifi.c: In function `madwifi_set_ieee8021x':
driver_madwifi.c:332: error: `IEEE80211_PARAM_AUTHMODE' undeclared (first use in this function)
driver_madwifi.c:333: error: `IEEE80211_AUTH_AUTO' undeclared (first use in this function)
driver_madwifi.c:346: error: `IEEE80211_AUTH_WPA' undeclared (first use in this function)
driver_madwifi.c:346: error: `IEEE80211_AUTH_8021X' undeclared (first use in this function)
driver_madwifi.c: In function `madwifi_set_privacy':
driver_madwifi.c:363: error: `IEEE80211_PARAM_PRIVACY' undeclared (first use in this function)
driver_madwifi.c: In function `madwifi_set_sta_authorized':
driver_madwifi.c:371: error: storage size of `mlme' isn't known
driver_madwifi.c:378: error: `IEEE80211_MLME_AUTHORIZE' undeclared (first use in this function)
driver_madwifi.c:380: error: `IEEE80211_MLME_UNAUTHORIZE' undeclared (first use in this function)
driver_madwifi.c:382: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:383: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:371: warning: unused variable `mlme'
driver_madwifi.c: In function `madwifi_del_key':
driver_madwifi.c:392: error: storage size of `wk' isn't known
driver_madwifi.c:400: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:401: error: `IEEE80211_KEYIX_NONE' undeclared (first use in this function)
driver_madwifi.c:406: error: `IEEE80211_IOCTL_DELKEY' undeclared (first use in this function)
driver_madwifi.c:392: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_set_key':
driver_madwifi.c:416: error: storage size of `wk' isn't known
driver_madwifi.c:427: error: `IEEE80211_CIPHER_WEP' undeclared (first use in this function)
driver_madwifi.c:429: error: `IEEE80211_CIPHER_TKIP' undeclared (first use in this function)
driver_madwifi.c:431: error: `IEEE80211_CIPHER_AES_CCM' undeclared (first use in this function)
driver_madwifi.c:446: error: `IEEE80211_KEY_RECV' undeclared (first use in this function)
driver_madwifi.c:446: error: `IEEE80211_KEY_XMIT' undeclared (first use in this function)
driver_madwifi.c:448: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:450: error: `IEEE80211_KEY_DEFAULT' undeclared (first use in this function)
driver_madwifi.c:453: error: `IEEE80211_KEYIX_NONE' undeclared (first use in this function)
driver_madwifi.c:458: error: `IEEE80211_IOCTL_SETKEY' undeclared (first use in this function)
driver_madwifi.c:416: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_get_seqnum':
driver_madwifi.c:467: error: storage size of `wk' isn't known
driver_madwifi.c:474: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:479: error: `IEEE80211_IOCTL_GETKEY' undeclared (first use in this function)
driver_madwifi.c:467: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_sta_deauth':
driver_madwifi.c:635: error: storage size of `mlme' isn't known
driver_madwifi.c:641: error: `IEEE80211_MLME_DEAUTH' undeclared (first use in this function)
driver_madwifi.c:643: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:644: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:635: warning: unused variable `mlme'
driver_madwifi.c: In function `madwifi_sta_disassoc':
driver_madwifi.c:652: error: storage size of `mlme' isn't known
driver_madwifi.c:659: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:660: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:652: warning: unused variable `mlme'
driver_madwifi.c: At top level:
driver_madwifi.c:664: error: `IEEE80211_ADDR_LEN' undeclared here (not in a function)
driver_madwifi.c: In function `madwifi_process_wpa_ie':
driver_madwifi.c:687: error: storage size of `ie' isn't known
driver_madwifi.c:694: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:695: error: `IEEE80211_IOCTL_GETWPAIE' undeclared (first use in this function)
driver_madwifi.c:687: warning: unused variable `ie'
driver_madwifi.c: At top level:
driver_madwifi.c:721: error: `IEEE80211_ADDR_LEN' undeclared here (not in a function)
driver_madwifi.c: In function `madwifi_wireless_event_wireless':
driver_madwifi.c:852: error: incompatible type for argument 2 of `madwifi_del_sta'
driver_madwifi.c:855: error: incompatible type for argument 2 of `madwifi_new_sta'
driver_madwifi.c: In function `madwifi_set_countermeasures':
driver_madwifi.c:1251: error: `IEEE80211_PARAM_COUNTERMEASURES' undeclared (first use in this function)
make: *** [driver_madwifi.o] Error 1

those errors are same i get with hostapd 0.4.7, now again, so do you know where is the error, i think it's a problem with madwifi, but don't know what to do, any ideas??
i would appreciate so much any suggestion or help
thanks in advance.



_______________________________________________________________ 
How "hot" is the hottest creature on Earth?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=6




From cristian.ionescu-idbohrn  Wed Mar 15 03:26:20 2006
From: cristian.ionescu-idbohrn (Cristian Ionescu-Idbohrn)
Date: Wed, 15 Mar 2006 12:26:20 +0100 (CET)
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <PM.3256.1142420707@pmweb11.uk1.bibliotech.net>
References: <PM.3256.1142420707@pmweb11.uk1.bibliotech.net>
Message-ID: <0603151218400.13475@somehost>

On Wed, 15 Mar 2006, Pelusa Vali wrote:

> well i think it's a very newbie error, could you please excuse??,
> but i'm really very newbie.!! so, i installed it and again type
> make, now get this:
>
> driver_madwifi.c:21:28: warning: include/compat.h: No such file or directory

This could be the reason:

madwifi-dev - includes for the Multiband Atheros Driver for WiFi

> driver_madwifi.c:22:32: warning: net80211/ieee80211.h: No such file or directorydriver_madwifi.c:28:39: warning: net80211/ieee80211_crypto.h: No such file or directory

[snip]

> driver_madwifi.c: At top level:
> driver_madwifi.c:721: error: `IEEE80211_ADDR_LEN' undeclared here (not in a function)
> driver_madwifi.c: In function `madwifi_wireless_event_wireless':
> driver_madwifi.c:852: error: incompatible type for argument 2 of `madwifi_del_sta'
> driver_madwifi.c:855: error: incompatible type for argument 2 of `madwifi_new_sta'
> driver_madwifi.c: In function `madwifi_set_countermeasures':
> driver_madwifi.c:1251: error: `IEEE80211_PARAM_COUNTERMEASURES' undeclared (first use in this function)
> make: *** [driver_madwifi.o] Error 1
>
> those errors are same i get with hostapd 0.4.7, now again, so do you
> know where is the error, i think it's a problem with madwifi, but
> don't know what to do, any ideas?? i would appreciate so much any
> suggestion or help

You may also need to install one or several of these packages:

# apt-cache search ieee80211
ieee80211-source - Source for the 802.11 (wireless) network stack for Linux
ieee80211softmac-headers-2.6.15-1 - IEEE 802.11 SoftMAC headers for Linux 2.6.15-1
ieee80211softmac-modules-2.6.15-1-486 - IEEE 802.11 SoftMAC kernel module for Linux 2.6.15-1-486
ieee80211softmac-modules-2.6.15-1-686 - IEEE 802.11 SoftMAC kernel module for Linux 2.6.15-1-686
ieee80211softmac-modules-2.6.15-1-686-smp - IEEE 802.11 SoftMAC kernel module for Linux 2.6.15-1-686-smp
ieee80211softmac-modules-2.6.15-1-k7 - IEEE 802.11 SoftMAC kernel module for Linux 2.6.15-1-k7
ieee80211softmac-modules-2.6.15-1-k7-smp - IEEE 802.11 SoftMAC kernel module for Linux 2.6.15-1-k7-smp
ieee80211softmac-source - Source for the ieee80211softmac driver


Cheers,
Cristian



From fraxinus.excelsior  Wed Mar 15 04:03:50 2006
From: fraxinus.excelsior (Yasen Balev)
Date: Wed, 15 Mar 2006 14:03:50 +0200
Subject: cann't compile hostapd 0.5.1
In-Reply-To: <PM.3256.1142420707@pmweb11.uk1.bibliotech.net>
References: <PM.3256.1142420707@pmweb11.uk1.bibliotech.net>
Message-ID: <2d1888f90603150403vb44a331x@mail.gmail.com>

2006/3/15, Pelusa Vali <pelusitavali at postmaster.co.uk>:

> well i think it's a very newbie error, could you please excuse??, but i'm really very newbie.!!

that's not bad by itself. Excused.

> so, i installed it and again type make, now get this:
>
> driver_madwifi.c:21:28: warning: include/compat.h: No such file or directory
> .......yabayabayaba another MADWIFI files missing......

your .config file for hostapd does not include a proper (absolute)
path to madwifi driver sources.

go and check it.



From rafa  Wed Mar 15 12:21:17 2006
From: rafa (Rafa Marin Lopez)
Date: Wed, 15 Mar 2006 15:21:17 -0500
Subject: wpa_supplicant 0.5.1 & association
Message-ID: <4418773D.6070503@dif.um.es>

Hi all

Is there any way wpa_supplicant can start directly association for a 
particular AP (if the parameters are provided externally) without doing 
scanning?.

Regards.

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




From matt  Wed Mar 15 12:26:20 2006
From: matt (Matt Brown)
Date: Thu, 16 Mar 2006 09:26:20 +1300
Subject: Hostap & ifrename
In-Reply-To: <4417D401.8070507@volny.cz>
References: <4417D401.8070507@volny.cz>
Message-ID: <1142454380.11239.1.camel@localhost.localdomain>

On Wed, 2006-03-15 at 09:44 +0100, Svata Dedic wrote:

> I am using hostap-0.4.4 - is there some fix for this issue in later
> versions, so I should consider an upgrade ? There was a patch sent to
> this list back in September 2005 I think, but the patch didn't work for
> me: contents of /proc/net/hostap were screwed (duplicate directory names
> etc).

Ian sent in a revised patch based on my earlier work at the end of
January. You can find it at
http://lists.shmoo.com/pipermail/hostap/2006-January/012457.html

As far as I'm aware it hasn't been committed to the driver yet, however
it addresses (or at least it should) the issues that Jouni raised about
my earlier patch. 

Cheers

-- 
Matt Brown
matt at mattb.net.nz
Mob +64 21 611 544 www.mattb.net.nz
-------------- 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/20060316/0096c724/attachment.pgp 


From gianni.costanzi  Wed Mar 15 12:33:56 2006
From: gianni.costanzi (Gianni Costanzi)
Date: Wed, 15 Mar 2006 21:33:56 +0100
Subject: wlan0 disappears after few seconds [Hostap problem]
In-Reply-To: <671355fe0603140627v16be166amdfaf3d3539f9e96c@mail.gmail.com>
References: <671355fe0603140627v16be166amdfaf3d3539f9e96c@mail.gmail.com>
Message-ID: <671355fe0603151233n727c51b6o4280454b2fc6fb67@mail.gmail.com>

Hi,
I've installed hostap on a Gentoo Linux box with kernel 2.4.31 (I need
to use a 2.4 kernel) and a Netgear MA401 PCMCIA card and everything
seems to work: I can change wlan0 to Master mode (even if I get an
error, as if the request was illegal, but then iwconfig shows me wlan0
and wifi0 in Master mode.. is it normal?) and other laptops are able
to connect to my laptop as if it was an access point (two laptops
associated themselves to my laptop and then they were able to ping one
each other).. The problem is that after few seconds something wrong
happens and the access point stops working (iwconfig tells me that
wlan0 has "no wireless extensions").. I'll put here the relevant
content of dmesg, perhaps some of you can help me (i need to make this
stuff work for my thesis):


pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Linux Kernel Card Services 3.1.22
 options:  [pci] [cardbus] [pm]
Yenta ISA IRQ mask 0x0050, PCI irq 7
Socket status: 30000010
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: excluding 0x810-0x87f
cs: IO port probe 0x0100-0x04ff: excluding 0x370-0x377 0x3b0-0x3df
0x3f0-0x3f7 0x480-0x4bf 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=50 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 5.0, irq 7, io 0x0100-0x013f
prism2_hw_init: initialized in 190 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
wifi0: defaulting to host-based encryption as a workaround for
firmware bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug
in Host AP mode WDS
wifi0: registered netdevice wlan0
wlan0: Host AP mode does not support 'Any' essid
prism2: wlan0: operating mode changed 3 -> 2
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=00:09:5b:54:7a:c1
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:14:a8:24:b6:b0
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc04, len=34)
wlan0: CMD=0x0121 => res=0x7f, resp0=0x0004
wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc04, len=34)
prism2: wlan0: operating mode changed 2 -> 3
wifi0: Interrupt, but SWSUPPORT0 does not match: 0000 != 8A32 - card removed?
wifi0: scheduled card reset
hostap_cs: wifi0: resetting card
prism2_pccard_cor_sreset: original COR 41
wifi0: removed pending cmd_queue entry (type=0, cmd=0x0002, param0=0x0000)
prism2_hw_init: initialized in 200 ms
wlan0: hfa384x_cmd: command was not completed (res=0, entry=f73b8260,
type=0, cmd=0x0002, param0=0x0000, EVSTAT=0000 INTEN=e09f)
wlan0: reset port failed to disable port
wifi0: 00:0e:35:7c:a3:0e auth_cb - alg=0 trans#=2 status=0 - STA authenticated
wifi0: 00:0e:35:7c:a3:0e assoc_cb - STA associated
wifi0: 00:e0:98:b4:2f:4d auth_cb - alg=0 trans#=2 status=0 - STA authenticated
wifi0: assoc from 00:e0:98:b4:2f:4d with extra data (10 bytes)
[<32><08><0c><12><18><24><30><48><60><6c>]
wifi0: 00:e0:98:b4:2f:4d assoc_cb - STA associated
wifi0: Deauthenticate all stations
wlan0: hfa384x_cmd: entry still in list? (entry=f77a4d60, type=0, res=200)
wlan0: hfa384x_cmd: interrupted; err=-4
wlan0: MAC port 0 enabling failed
wlan0: could not enable MAC port
wifi0: Command completion event, but no pending commands


Perhaps it's something related to the "MAC port 0 enabling failed" error...
Any idea?

Thank you in advance for any suggestion,
Gianni

--
--------------------------------------------------------------------------------------------------------------
|  Gianni Costanzi (gianni.costanzi at gmail.com)
|
|  Gentoo Documentation Project (GDP) Member - Italian Translator
|       (http://www.gentoo.org/proj/en/gdp/)
|       (http://ares.science.unitn.it/~gianni.costanzi/)
|
|  Free Software Foundation Member #3844 (www.fsf.org)
|
|  Why GNU/Linux? (http://www.gnu.org/gnu/why-gnu-linux.html)
--------------------------------------------------------------------------------------------------------------


From jar  Wed Mar 15 12:47:51 2006
From: jar (Jar)
Date: Wed, 15 Mar 2006 22:47:51 +0200
Subject: wlan0 disappears after few seconds [Hostap problem]
In-Reply-To: <671355fe0603151233n727c51b6o4280454b2fc6fb67@mail.gmail.com>
References: <671355fe0603140627v16be166amdfaf3d3539f9e96c@mail.gmail.com>
	<671355fe0603151233n727c51b6o4280454b2fc6fb67@mail.gmail.com>
Message-ID: <44187D77.7000805@pcuf.fi>

Gianni Costanzi wrote:

> prism2_hw_init: initialized in 190 ms
> wifi0: NIC: id=0x800c v1.0.0
> wifi0: PRI: id=0x15 v1.0.7
> wifi0: STA: id=0x1f v1.3.6

Can you try to update the card firmwares if it helps?

v1.0.7 --> v1.1.1
v1.3.6 --> v1.7.4

See: http://linux.junsun.net/intersil-prism/


-- 
Best Regards, Jar



From pelusitavali  Wed Mar 15 14:27:49 2006
From: pelusitavali (Pelusa Vali)
Date: Wed, 15 Mar 2006 22:27:49 +0000
Subject: madwifi and hostapd persistent error
Message-ID: <PM.7818.1142461669@pmweb5.uk1.bibliotech.net>

hi people, well after many tries finally i must say i cann't compile hostapd, always get this:
 
driver_madwifi.c:21:28: warning: include/compat.h: No such file or directory
driver_madwifi.c:22:32: warning: net80211/ieee80211.h: No such file or directory
driver_madwifi.c:28:39: warning: net80211/ieee80211_crypto.h: No such file or di rectory
driver_madwifi.c:29:38: warning: net80211/ieee80211_ioctl.h: No such file or dir ectory
driver_madwifi.c: In function `set80211priv':
driver_madwifi.c:124: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in  this function)
driver_madwifi.c:124: error: (Each undeclared identifier is reported only once
driver_madwifi.c:124: error: for each function it appears in.)
driver_madwifi.c:125: error: `IEEE80211_IOCTL_CHANLIST' undeclared (first use in  this function)
driver_madwifi.c: In function `set80211param':
driver_madwifi.c:167: error: `IEEE80211_IOCTL_SETPARAM' undeclared (first use in  this function)
driver_madwifi.c: In function `madwifi_configure_wpa':
driver_madwifi.c:198: error: `IEEE80211_CIPHER_AES_CCM' undeclared (first use in  this function)
driver_madwifi.c:201: error: `IEEE80211_CIPHER_TKIP' undeclared (first use in th is function)
driver_madwifi.c:204: error: `IEEE80211_CIPHER_WEP' undeclared (first use in thi s function)
driver_madwifi.c:210: error: `IEEE80211_CIPHER_NONE' undeclared (first use in th is function)
driver_madwifi.c:219: error: `IEEE80211_PARAM_MCASTCIPHER' undeclared (first use  in this function)
driver_madwifi.c:226: error: `IEEE80211_PARAM_MCASTKEYLEN' undeclared (first use  in this function)
driver_madwifi.c:241: error: `IEEE80211_PARAM_UCASTCIPHERS' undeclared (first us e in this function)
driver_madwifi.c:249: error: `IEEE80211_PARAM_KEYMGTALGS' undeclared (first use in this function)
driver_madwifi.c:260: error: `IEEE80211_PARAM_RSNCAPS' undeclared (first use in this function)
driver_madwifi.c:267: error: `IEEE80211_PARAM_WPA' undeclared (first use in this  function)
driver_madwifi.c: In function `madwifi_set_ieee8021x':
driver_madwifi.c:332: error: `IEEE80211_PARAM_AUTHMODE' undeclared (first use in  this function)
driver_madwifi.c:333: error: `IEEE80211_AUTH_AUTO' undeclared (first use in this  function)
driver_madwifi.c:346: error: `IEEE80211_AUTH_WPA' undeclared (first use in this function)
driver_madwifi.c:346: error: `IEEE80211_AUTH_8021X' undeclared (first use in thi s function)
driver_madwifi.c: In function `madwifi_set_privacy':
driver_madwifi.c:363: error: `IEEE80211_PARAM_PRIVACY' undeclared (first use in this function)
driver_madwifi.c: In function `madwifi_set_sta_authorized':
driver_madwifi.c:371: error: storage size of `mlme' isn't known
driver_madwifi.c:378: error: `IEEE80211_MLME_AUTHORIZE' undeclared (first use in  this function)
driver_madwifi.c:380: error: `IEEE80211_MLME_UNAUTHORIZE' undeclared (first use in this function)
driver_madwifi.c:382: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:383: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:371: warning: unused variable `mlme'
driver_madwifi.c: In function `madwifi_del_key':
driver_madwifi.c:392: error: storage size of `wk' isn't known
driver_madwifi.c:400: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:401: error: `IEEE80211_KEYIX_NONE' undeclared (first use in thi s function)
driver_madwifi.c:406: error: `IEEE80211_IOCTL_DELKEY' undeclared (first use in t his function)
driver_madwifi.c:392: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_set_key':
driver_madwifi.c:416: error: storage size of `wk' isn't known
driver_madwifi.c:427: error: `IEEE80211_CIPHER_WEP' undeclared (first use in thi s function)
driver_madwifi.c:429: error: `IEEE80211_CIPHER_TKIP' undeclared (first use in th is function)
driver_madwifi.c:431: error: `IEEE80211_CIPHER_AES_CCM' undeclared (first use in  this function)
driver_madwifi.c:446: error: `IEEE80211_KEY_RECV' undeclared (first use in this function)
driver_madwifi.c:446: error: `IEEE80211_KEY_XMIT' undeclared (first use in this function)
driver_madwifi.c:448: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:450: error: `IEEE80211_KEY_DEFAULT' undeclared (first use in th is function)
driver_madwifi.c:453: error: `IEEE80211_KEYIX_NONE' undeclared (first use in thi s function)
driver_madwifi.c:458: error: `IEEE80211_IOCTL_SETKEY' undeclared (first use in t his function)
driver_madwifi.c:416: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_get_seqnum':
driver_madwifi.c:467: error: storage size of `wk' isn't known
driver_madwifi.c:474: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:479: error: `IEEE80211_IOCTL_GETKEY' undeclared (first use in t his function)
driver_madwifi.c:467: warning: unused variable `wk'
driver_madwifi.c: In function `madwifi_sta_deauth':
driver_madwifi.c:635: error: storage size of `mlme' isn't known
driver_madwifi.c:641: error: `IEEE80211_MLME_DEAUTH' undeclared (first use in th is function)
driver_madwifi.c:643: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:644: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:635: warning: unused variable `mlme'
driver_madwifi.c: In function `madwifi_sta_disassoc':
driver_madwifi.c:652: error: storage size of `mlme' isn't known
driver_madwifi.c:659: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:660: error: `IEEE80211_IOCTL_SETMLME' undeclared (first use in this function)
driver_madwifi.c:652: warning: unused variable `mlme'
driver_madwifi.c: At top level:
driver_madwifi.c:664: error: `IEEE80211_ADDR_LEN' undeclared here (not in a func tion)
driver_madwifi.c: In function `madwifi_process_wpa_ie':
driver_madwifi.c:687: error: storage size of `ie' isn't known
driver_madwifi.c:694: error: `IEEE80211_ADDR_LEN' undeclared (first use in this function)
driver_madwifi.c:695: error: `IEEE80211_IOCTL_GETWPAIE' undeclared (first use in  this function)
driver_madwifi.c:687: warning: unused variable `ie'
driver_madwifi.c: At top level:
driver_madwifi.c:721: error: `IEEE80211_ADDR_LEN' undeclared here (not in a func tion)
driver_madwifi.c: In function `madwifi_wireless_event_wireless':
driver_madwifi.c:852: error: incompatible type for argument 2 of `madwifi_del_st a'
driver_madwifi.c:855: error: incompatible type for argument 2 of `madwifi_new_st a'
driver_madwifi.c: In function `madwifi_set_countermeasures':
driver_madwifi.c:1251: error: `IEEE80211_PARAM_COUNTERMEASURES' undeclared (firs t use in this function)
make: *** [driver_madwifi.o] Error 1

so, it seems hostapd is unable to locate this soft, but i reviewed and all are under madwifi directory, and this is my .config file:

CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I../usr/src/madwifi-ng-r1457-20060228

so tried to download and install this packets:

madwifi-dev_0.svn20060207-1_all.deb
madwifi-source_0.svn20060207-1_all.deb
madwifi-tools_0.svn20060207-1_i386.deb

and made this in .config file:

CFLAGS += -I../usr/include/madwifi/include/ 

i used this too:

CFLAGS += -I/usr/local/include
LIBS += -L/usr/local/lib

but, always same error.  so i installed hostapd_0.5.1-1.deb and configured it so work with madwifi, but this program simply don't talk with madwifi, first trying to use radius internal server, and get this:

ioctl[unknown???]: Argument list too long
Could not connect to kernel driver.
Deauthenticate all stations
rmdir[ctrl_interface]: No such file or directory
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0

if try using freeradius, worst, clients never see radius server.
by the way i use debian sarge kernel 2.6.15, freeradius-1.1.0, madwifi-ng-r1457.

now, why this behavior?? why hostapd simply cann't detect madwifi?? i followed instructions from madwifi.org documents and many different tutorials, but nothing seems to work for me.
so, please, could any body try to help?

thanks in advance.


_______________________________________________________________ 
What is the tallest volcano in the world?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=267




From tbeville  Wed Mar 15 15:29:20 2006
From: tbeville (Tony Beville)
Date: Wed, 15 Mar 2006 15:29:20 -0800
Subject: Regarding LEAP with TKIP
Message-ID: <4418A350.7070708@intellidot.net>

We have a customer requirement for our wireless device to support Cisco 
LEAP with TKIP encryption.  Does this even make sense?

We currently have  wpa_supplicant (with our Hermes-II radio) working 
with what I guess I would called "regular LEAP," using rotating WEP keys.

Can anyone confirm if LEAP with TKIP is a meaningful thing to do, and if 
so, what would our wpa_supplicant configuration file look like to 
support it?

Thanks in advance,

Tony

tbeville (at) intellidot (dot) net



From Edwin.Whitelaw  Wed Mar 15 17:31:21 2006
From: Edwin.Whitelaw (Edwin Whitelaw)
Date: Wed, 15 Mar 2006 20:31:21 -0500
Subject: Yet another question about bridgiing...
Message-ID: <4418BFE9.5090805@nrvunwired.net>

Has the hostap code yet (or will it ever) evolved to allow layer 2 
bridging between two radios on the smae host - one in AP and one in 
client mode?

It would really be a wonderful capability for certain applications in a 
WISP network where routing to just a very few customer off the AP side 
is not really worth the hassle or necessary.

I have googled in general and searched the HostAP archives prior to 
posting.  Just wanted to make sure I hadn't missed anything.

Thanks,

Edwin



From jkmaline  Wed Mar 15 18:42:11 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Mar 2006 18:42:11 -0800
Subject: Regarding LEAP with TKIP
In-Reply-To: <4418A350.7070708@intellidot.net>
References: <4418A350.7070708@intellidot.net>
Message-ID: <20060316024211.GA9368@jm.kir.nu>

On Wed, Mar 15, 2006 at 03:29:20PM -0800, Tony Beville wrote:

> We have a customer requirement for our wireless device to support Cisco 
> LEAP with TKIP encryption.  Does this even make sense?

In the sense of LEAP not being were secure, it does not make much sense
;-). Anyway, this would be WPA-Enterprise using LEAP as the EAP method..

> We currently have  wpa_supplicant (with our Hermes-II radio) working 
> with what I guess I would called "regular LEAP," using rotating WEP keys.

.. whereas this is IEEE 802.1X (non-WPA) with LEAP as the EAP method.

> Can anyone confirm if LEAP with TKIP is a meaningful thing to do, and if 
> so, what would our wpa_supplicant configuration file look like to 
> support it?

I would not recommend this mode, but yes, it should work. Configuration
for this would be something like this:

network={
    ssid="foo"
    key_mgmt=WPA-EAP
    proto=WPA
    pairwise=TKIP
    group=TKIP
}

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 15 18:45:14 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Mar 2006 18:45:14 -0800
Subject: Yet another question about bridgiing...
In-Reply-To: <4418BFE9.5090805@nrvunwired.net>
References: <4418BFE9.5090805@nrvunwired.net>
Message-ID: <20060316024514.GB9368@jm.kir.nu>

On Wed, Mar 15, 2006 at 08:31:21PM -0500, Edwin Whitelaw wrote:
> Has the hostap code yet (or will it ever) evolved to allow layer 2 
> bridging between two radios on the smae host - one in AP and one in 
> client mode?

This is not question about implementation, but protocol.. IEEE 802.11
simply does not allow client mode device to send frames with other that
its own address as the source MAC address and this is enough to break
layer 2 bridging. You can do such bridging with WDS links, though. In
addition, layer 2 NAT or other address translation mechanisms could be
used to make something similar work (but with limitations on what
protocols can be bridged).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jar  Wed Mar 15 23:46:32 2006
From: jar (Jar)
Date: Thu, 16 Mar 2006 09:46:32 +0200 (EET)
Subject: Yet another question about bridgiing...
In-Reply-To: <20060316024514.GB9368@jm.kir.nu>
References: <4418BFE9.5090805@nrvunwired.net> <20060316024514.GB9368@jm.kir.nu>
Message-ID: <48821.192.168.0.2.1142495192.squirrel@kone.netland.fin>


> This is not question about implementation, but protocol.. IEEE 802.11
> simply does not allow client mode device to send frames with other that
> its own address as the source MAC address and this is enough to break
> layer 2 bridging.

http://www.ieee802.org/11/DocFiles/05/11-05-0710-00-000m-wds-clarifications.doc

I understand this so that 4-addr frame is not part of the ieee802.11 standard for
STAs but nothing is relly preventing to use the 4-addr format with infrastructure
mode STA to build bridges etc. devices??


-- 
Best Regards, Jar



From proski  Thu Mar 16 00:06:28 2006
From: proski (Pavel Roskin)
Date: Thu, 16 Mar 2006 03:06:28 -0500
Subject: Yet another question about bridgiing...
In-Reply-To: <48821.192.168.0.2.1142495192.squirrel@kone.netland.fin>
References: <4418BFE9.5090805@nrvunwired.net> <20060316024514.GB9368@jm.kir.nu>
	<48821.192.168.0.2.1142495192.squirrel@kone.netland.fin>
Message-ID: <1142496388.3678.2.camel@dv>

On Thu, 2006-03-16 at 09:46 +0200, Jar wrote:
> I understand this so that 4-addr frame is not part of the ieee802.11 standard for
> STAs but nothing is relly preventing to use the 4-addr format with infrastructure
> mode STA to build bridges etc. devices??

Yes, that's what the old MadWifi does as a substitute for WDS.  Of
course, this is highly non-standard on both ends.

-- 
Regards,
Pavel Roskin




From jim  Thu Mar 16 01:50:20 2006
From: jim (Jim Thompson)
Date: Wed, 15 Mar 2006 23:50:20 -1000
Subject: Yet another question about bridgiing...
In-Reply-To: <1142496388.3678.2.camel@dv>
References: <4418BFE9.5090805@nrvunwired.net>
	<20060316024514.GB9368@jm.kir.nu>	<48821.192.168.0.2.1142495192.squirrel@kone.netland.fin>
	<1142496388.3678.2.camel@dv>
Message-ID: <441934DC.2080208@netgate.com>

Pavel Roskin wrote:

>On Thu, 2006-03-16 at 09:46 +0200, Jar wrote:
>  
>
>>I understand this so that 4-addr frame is not part of the ieee802.11 standard for
>>STAs but nothing is relly preventing to use the 4-addr format with infrastructure
>>mode STA to build bridges etc. devices??
>>    
>>
>
>Yes, that's what the old MadWifi does as a substitute for WDS.  Of
>course, this is highly non-standard on both ends.
>
>  
>
First, that document is not part of the IEEE standard.

Second, all devices in an 802.11 network are STAs.  (APs are STAs with 
"access point" functions.)

In the IEEE standard, only APs have "distribution" functionality.

WDS is a "wireless distribution" function.

Therefore only APS "have" WDS.  

Pendantic?  Yes.

And yes, nothing really "prevents" a STA from sending and receiving 
4-address frames.

(Speaking to the previous therad, a carefull look at the docuement, and 
a bit of knowledge that only addr2 is ever ACKed (if any ACK is sent) 
should reveal why the 4-address frame format is necessary.)

Jim





From brix  Thu Mar 16 11:36:06 2006
From: brix (Henrik Brix Andersen)
Date: Thu, 16 Mar 2006 20:36:06 +0100
Subject: Group key renewal problem
In-Reply-To: <20060312114348.GA17973@osgiliath.brixandersen.dk>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
	<20060311202319.GC9371@jm.kir.nu>
	<20060311204940.GB30840@osgiliath.brixandersen.dk>
	<20060312114348.GA17973@osgiliath.brixandersen.dk>
Message-ID: <20060316193606.GA32562@osgiliath.brixandersen.dk>

On Sun, Mar 12, 2006 at 12:43:48PM +0100, Henrik Brix Andersen wrote:
> Would you like me to open a bug report about this?

Just did, http://hostap.epitest.fi/bugz/show_bug.cgi?id=126

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


From fjenkins873  Thu Mar 16 14:41:09 2006
From: fjenkins873 (frank jenkins)
Date: Thu, 16 Mar 2006 22:41:09 +0000
Subject: associating fails without error
Message-ID: <BAY113-F35F80F88AEE4EBA31B7DFDEBE70@phx.gbl>

I'm trying to connect a laptop with a DWL-650 (with primary firmware 1.0.7 
and station firmware 1.8.4) to a wrt54g using rsn,wpa-psk, and ccmp. I'm 
using the 2.6.15 kernel with hostap driver 0.4.4 and wireless tools v28.

wpa_supplicant can see the access point and tries to associate with it, but 
for some reason that isn't obvious to me in the logs, it disassociates and 
starts looking for another ap. Here's (what I think is) the relevant part of 
the output from wpa_supplicant:

  0: 00:14:bf:ed:39:45 ssid='TestSsid' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
  selected based on RSN IE
  Trying to associate with 00:14:bf:ed:39:45 (SSID='TestSsid' freq=2452 MHz)
  Cancelling scan request
  WPA: clearing own WPA/RSN IE
  Automatic auth_alg selection: 0x1
  RSN: using IEEE 802.11i/D9.0
  WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
  WPA: clearing AP WPA IE
  WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f 
ac 04 01 00 00 0f ac 02 00 00
  WPA: using GTK CCMP
  WPA: using PTK CCMP
  WPA: using KEY_MGMT WPA-PSK
  WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 
00 00 0f ac 04 01 00 00 0f ac 02 00 00
  No keys have been configured - skip key clearing
  wpa_driver_hostap_set_drop_unencrypted: enabled=1
  State: SCANNING -> ASSOCIATING
  wpa_driver_hostap_associate
  Setting authentication timeout: 10 sec 0 usec
  EAPOL: External notification - EAP success=0
  EAPOL: External notification - EAP fail=0
  EAPOL: External notification - portControl=Auto
  RSN: Ignored PMKID candidate without preauth flag
  Wireless event: cmd=0x8b06 len=8
  Wireless event: cmd=0x8b04 len=12
  Wireless event: cmd=0x8b1a len=17
  Wireless event: cmd=0x8b15 len=20
  Wireless event: new AP: 00:14:bf:ed:39:45
  State: ASSOCIATING -> ASSOCIATED
  Associated to a new BSS: BSSID=00:14:bf:ed:39:45
  No keys have been configured - skip key clearing
  Associated with 00:14:bf:ed:39:45
  WPA: Association event - clear replay counter
  EAPOL: External notification - portEnabled=0
  EAPOL: External notification - portValid=0
  EAPOL: External notification - EAP success=0
  EAPOL: External notification - portEnabled=1
  EAPOL: SUPP_PAE entering state CONNECTING
  EAPOL: SUPP_BE entering state IDLE
  Setting authentication timeout: 10 sec 0 usec
  RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi1' added
  EAPOL: startWhen --> 0
  EAPOL: SUPP_PAE entering state CONNECTING
  EAPOL: txStart
  WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
  Wireless event: cmd=0x8b15 len=20
  Wireless event: new AP: 00:00:00:00:00:00
  Setting scan request: 0 sec 100000 usec
  Added BSSID 00:14:bf:ed:39:45 into blacklist
  Added BSSID 00:14:bf:ed:39:45 into blacklist
  State: ASSOCIATED -> DISCONNECTED
  EAPOL: External notification - portEnabled=0
  EAPOL: SUPP_PAE entering state DISCONNECTED
  EAPOL: SUPP_BE entering state INITIALIZE
  EAPOL: External notification - portValid=0
  EAPOL: External notification - EAP success=0
  CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
  wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0

And here's the network block of my wpa_supplicant.conf
network={
  ssid="TestSsid"
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=CCMP
  group=CCMP
  psk="12345678"
  priority=1
}

I don't see any reason in the log for it to stop connecting in the log, but 
then
I've never used wpa_supplicant before. Can anyone tell me what I'm missing?

_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/




From ryan.castellucci  Thu Mar 16 17:31:32 2006
From: ryan.castellucci (Ryan Castellucci)
Date: Thu, 16 Mar 2006 17:31:32 -0800
Subject: [PATCH} Make AP_MAX_INACTIVITY configurable
Message-ID: <118619310603161731q1c14a833xa80bf4435807fc36@mail.gmail.com>

This patch applies fine on 0.4.8. It adds the config file option
'max_inactivity'.

----- CUT HERE ----
diff -u hostapd-0.3.7/config.c hostap/config.c
--- hostapd-0.3.7/config.c      2005-01-22 11:43:16.000000000 -0800
+++ hostap/config.c     2006-03-07 16:29:46.000000000 -0800
@@ -65,6 +65,8 @@
        conf->wpa_pairwise = WPA_CIPHER_TKIP;
        conf->wpa_group = WPA_CIPHER_TKIP;

+       conf->max_inactivity = AP_MAX_INACTIVITY;
+
        conf->radius_server_auth_port = 1812;

        return conf;
@@ -681,6 +683,8 @@
                        conf->logger_stdout = atoi(pos);
                } else if (strcmp(buf, "dump_file") == 0) {
                        conf->dump_log_name = strdup(pos);
+               } else if (strcmp(buf, "max_inactivity") == 0) {
+                       conf->max_inactivity = atoi(pos);
                } else if (strcmp(buf, "ssid") == 0) {
                        conf->ssid_len = strlen(pos);
                        if (conf->ssid_len >= HOSTAPD_SSID_LEN ||
diff -u hostapd-0.3.7/config.h hostap/config.h
--- hostapd-0.3.7/config.h      2005-01-11 17:58:20.000000000 -0800
+++ hostap/config.h     2006-03-07 16:29:46.000000000 -0800
@@ -102,6 +102,8 @@
                                * EAP Request-Identity */
        int eapol_key_index_workaround;

+       u32 max_inactivity;
+
        size_t default_wep_key_len;
        int individual_wep_key_len;
        int wep_rekeying_period;
diff -u hostapd-0.3.7/sta_info.c hostap/sta_info.c
--- hostapd-0.3.7/sta_info.c    2004-11-26 19:33:13.000000000 -0800
+++ hostap/sta_info.c   2006-03-07 16:29:46.000000000 -0800
@@ -178,13 +178,13 @@
                        printf("  Could not get station info from kernel "
                               "driver for " MACSTR ".\n",
                               MAC2STR(sta->addr));
-               } else if (inactive_sec < AP_MAX_INACTIVITY &&
+               } else if (inactive_sec < hapd->conf->max_inactivity &&
                           sta->flags & WLAN_STA_ASSOC) {
                        /* station activity detected; reset timeout state */
                        HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL,
                                      "  Station has been active\n");
                        sta->timeout_next = STA_NULLFUNC;
-                       next_time = AP_MAX_INACTIVITY - inactive_sec;
+                       next_time = hapd->conf->max_inactivity - inactive_sec;
                }
        }

@@ -196,7 +196,7 @@
                /* data nullfunc frame poll did not produce TX errors; assume
                 * station ACKed it */
                sta->timeout_next = STA_NULLFUNC;
-               next_time = AP_MAX_INACTIVITY;
+               next_time = hapd->conf->max_inactivity;
        }

        if (next_time) {
@@ -342,7 +342,7 @@
        sta->acct_interim_interval = hapd->conf->radius_acct_interim_interval;

        /* initialize STA info data */
-       eloop_register_timeout(AP_MAX_INACTIVITY, 0, ap_handle_timer,
+       eloop_register_timeout(hapd->conf->max_inactivity, 0, ap_handle_timer,
                               hapd, sta);
        memcpy(sta->addr, addr, ETH_ALEN);
        sta->next = hapd->sta_list;
---- END CUT ----



From eleghost  Thu Mar 16 23:20:29 2006
From: eleghost (Scott)
Date: Fri, 17 Mar 2006 15:20:29 +0800
Subject: What is difference between WDS and IAPP
Message-ID: <1142580030.9273.8.camel@localhost>

Hi all:

I'm confusing on my subject, I directly think WDS is a protocol between
AP and IAPP also too. Except WDS have limitation that must same
channel / encryption and recode the MAC address each other but IAPP no
need to do it. I am curious that what is main differnet between WDS and
IAPP?

Any command whould be appreciation.
-- 
Scott <eleghost at gmail.com>




From pieter  Fri Mar 17 03:44:37 2006
From: pieter (Pieter Hollants)
Date: Fri, 17 Mar 2006 12:44:37 +0100
Subject: [PATCH] Re-synchronize driver_madwifi.c ioctl order with madwifi-ng
	rev 1331 and later
Message-ID: <441AA125.6050900@hollants.com>

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

In wpa_supplicant/driver_madwifi.c, rev. 1.19 added support for
madwifi-ng's at that time new private ioctls. That was based against SVN
rev 1298-1330 of madwifi-ng's net80211/net80211_wireless.c, in which the
ioctl order still was SETPARAM, GETPARAM, SETKEY etc.

However, as http://madwifi.org/changeset/1331 shows, the ioctls were
reordered on 22 November last year, and wpa_supplicant wasn't updated so
far to reflect these changes. So in my theory, wpa_supplicant's
madwifi-ng support must have been broken since then, since the ioctls it
uses are the old ones.

I noticed this in my debugging attempts, since I got messages such as

WPA: Installing PTK to the driver
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
ioctl[unknown???]: No such device of address
WPA: Failed to set PTK to the driver.

The actual problem here is what I'm still trying to debug, within the
context of this message only the "unknown???" part is of relevance since
this should obviously be SETKEY.

Attached is a patch to re-synchronize the ioctl order in
driver_madwifi.c to madwifi-ng rev 1331 and later. Please check.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGqEla8/cc5b1WpwRAmQKAKCaiSWUIT8sYQy3ZwlpBnykBxGHJgCgimIk
O20LTTSr9fulzeedUR5eRwA=
=HIQ1
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant-0.4.8-madwifing-ioctls.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060317/a465fbc2/attachment.txt 


From imamushroom  Fri Mar 17 03:54:29 2006
From: imamushroom (Andrew Leach)
Date: Fri, 17 Mar 2006 11:54:29 +0000
Subject: hostapd causes kernel panic in openwrt on a netgear wgt634u
Message-ID: <91ceaec60603170354r777b51aj@mail.gmail.com>

Hi,

Kernel panics when hostapd is executed on wgt634u using hostapd -
0.5.1-1and kmod-madwifi -
2.6.15.6+r1456.
Any ideas?

Thanks,
Andrew

The output trace follows:

root at OpenWrt <https://openwrt.org/wiki/OpenWrt>:/# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf madwifi_set_iface_flags: dev_up=0 br0:
port 2(ath0) entering disabled state

Using interface ath0 with hwaddr 00:00:ba:dc:0d:Data bus error, epc ==
c00eba18, ra == c00e7f08

Oops[#1 <https://openwrt.org/ticket/1>]:

Cpu 0

$ 0 : 00000000 10009c00 c0128000 00008000

$ 4 : 81c20000 00000006 81c202f0 81c202b0

$ 8 : 000000c0 81dcc000 81224000 813fc000

$12 : 81db7000 00000200 00000100 81c9a000

$16 : 81c22888 81c20000 81c20000 813e8000

$20 : 00000000 813e8f18 813e916c 00008914

$24 : 00000000 c00c0188

$28 : 81562000 81563cb0 81c202f0 c00e7f08

Hi : 000003d9

Lo : 99952600

epc : c00eba18 Tainted: P

ra : c00e7f08 Status: 10009c03 KERNEL EXL IE

Cause : 0000001c

PrId? <https://openwrt.org/wiki/PrId> : 00029007

Modules linked in: snd_pcm_oss snd_mixer_oss snd_usb_audio snd_hwdep
snd_usb_lib snd_rawmidi snd_pcm snd_timer snd snd_page_alloc ehci_hcd
uhci_hcd usb_storage sd_mod scsi_mod usbcore soundcore vfat fat nfs lockd
sunrpc ext3 jbd ext2 nls_utf8 nls_iso8859_15 nls_iso8859_1 nls_cp850
nls_cp437 nls_base wlan_scan_sta wlan_scan_ap wlan_xauth wlan_wep wlan_tkip
wlan_ccmp wlan_acl ath_pci ath_rate_sample ath_hal wlan switch_robo
switch_core

Process hostapd (pid: 1402, threadinfo=81562000, task=8036abe8)

Stack : 00000000 813e8f18 80260000 00008914 00000000 81c20000 81c20000
c00e7f08

  00000000 8005a804 7f9dbc20 8014f818 10009c03 00000001 00000000 00000000

    00000000 00000002 00000000 00000000 812b9320 812b9320 00000000 813e8260

    81c20000 813e8000 00000000 813e8f18 80260000 00008914 7f9dbc20 c0093c20

    80001fd4 00000006 81052000 00000000 81563d48 00000000 00000000 7f9dbc00

    ...

  Call Trace: [<c00e7f08>] [<8005a804>] [<8014f818>] [<c0093c20>]
[<80001fd4>] [<80156780>] [<c00c0230>] [<c00c602c>] [<c00c60cc>]
[<80156780>] [<801586d4>] [<801aece0>] [<801aeb50>] [<801b075c>]
[<80111b4c>] [<80149c4c>] [<801123d0>] [<80112324>] [<80093130>]
[<80093490>] [<800770d8>] [<80031d60>] [<80093508>] [<80030fb0>]
[<80001e4c>] [<80012720>] [<80012720>]

Code: 8e420014 34038000 00431021 <8c431930> 30628000 5440003b 8e222bbc
00032642 000315c2

ed and ssid 'prive' madwifi_set_ieee8021x: enabled=1 madwifi_configure_wpa:
group key cipher=1 madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2 madwifi_configure_wpa:
rsn capabilities=0x0 madwifi_configure_wpa: enable WPA= 0x3
madwifi_set_iface_flags: dev_up=1 Segmentation fault
root at OpenWrt<https://openwrt.org/wiki/OpenWrt>:/#
Data bus error, epc == c01c41a0, ra == c02241a8

Oops[#2 <https://openwrt.org/ticket/2>]:

Cpu 0

$ 0 : 00000000 10009c00 c0172020 00000000

$ 4 : 813fd100 8021de10 c0172020 00000000

$ 8 : 00000002 10009c01 813fd0c8 00000001

$12 : 00000000 00000001 80220000 ffffffd5

$16 : 00000100 813fd000 802626e4 8021de48

$20 : 80220000 80300000 00000010 00001000

$24 : 00000000 c0224160

$28 : 8021c000 8021ddf8 00000010 c02241a8

Hi : 000003d0

Lo : db47d9c0

epc : c01c41a0 Tainted: P

ra : c02241a8 Status: 10009c02 KERNEL EXL

Cause : 0000001c

PrId? <https://openwrt.org/wiki/PrId> : 00029007

Modules linked in: snd_pcm_oss snd_mixer_oss snd_usb_audio snd_hwdep
snd_usb_lib snd_rawmidi snd_pcm snd_timer snd snd_page_alloc ehci_hcd
uhci_hcd usb_storage sd_mod scsi_mod usbcore soundcore vfat fat nfs lockd
sunrpc ext3 jbd ext2 nls_utf8 nls_iso8859_15 nls_iso8859_1 nls_cp850
nls_cp437 nls_base wlan_scan_sta wlan_scan_ap wlan_xauth wlan_wep wlan_tkip
wlan_ccmp wlan_acl ath_pci ath_rate_sample ath_hal wlan switch_robo
switch_core

Process swapper (pid: 0, threadinfo=8021c000, task=8021e000)

Stack : b0bfb305 00000000 80260000 80260000 80260000 80260000 8021de00
00000007

  00000100 c02242d4 802626e4 8021de48 80036614 80036614 8022062c 00000000

    00000000 00000007 8021dee0 80300000 8021de48 8021de48 00000000 80262470

    0000000a 80260000 00000002 80031c7c 00000002 80300000 00000010 00001000

    10009c00 8021dee0 00000002 00000001 80031d60 00000590 00008000 8021dee0

    ...

  Call Trace: [<c02242d4>] [<80036614>] [<80036614>] [<80031c7c>]
[<80031d60>] [<8000a914>] [<8000b060>] [<80001e4c>] [<80001fd4>]
[<8015343c>] [<8000ab10>] [<8000aae4>] [<80232774>] [<80232758>]
[<8023212c>]

Code: 8d420004 00071880 00433021 <8cc30044> 30622000 10400007 30620002
10400020 006f1024

Kernel panic - not syncing: Aiee, killing interrupt handler!

 <0>Rebooting in 3 seconds..Please stand by while rebooting the system...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060317/1d20337f/attachment.htm 


From pieter  Fri Mar 17 04:16:47 2006
From: pieter (Pieter Hollants)
Date: Fri, 17 Mar 2006 13:16:47 +0100
Subject: [PATCH] Re-synchronize driver_madwifi.c ioctl order with
	madwifi-ng rev 1331 and later
In-Reply-To: <441AA125.6050900@hollants.com>
References: <441AA125.6050900@hollants.com>
Message-ID: <441AA8AF.4080209@hollants.com>

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

Sorry, attached the wrong file. Here is the correct, tested version.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGqiva8/cc5b1WpwRAg6NAKCagd38RqiYkrV+84eS7bhjIQzGFwCeJarg
YOdVnhPaDpfDPvVrhDo4YXE=
=W2cr
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant-0.4.8-madwifing-ioctls.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060317/91541a4d/attachment.txt 


From svens  Fri Mar 17 04:38:17 2006
From: svens (Sven Schnelle)
Date: Fri, 17 Mar 2006 13:38:17 +0100
Subject: hostapd causes kernel panic in openwrt on a netgear wgt634u
In-Reply-To: <91ceaec60603170354r777b51aj@mail.gmail.com> (Andrew Leach's
	message of "Fri, 17 Mar 2006 11:54:29 +0000")
References: <91ceaec60603170354r777b51aj@mail.gmail.com>
Message-ID: <86ek115jra.fsf@deprecated.bitebene.org>

A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060317/fc008aea/attachment.pgp 


From pieter  Fri Mar 17 08:09:51 2006
From: pieter (Pieter Hollants)
Date: Fri, 17 Mar 2006 17:09:51 +0100
Subject: [PATCH] Re-synchronize driver_madwifi.c ioctl order
	with	madwifi-ng rev 1331 and later
In-Reply-To: <441AA8AF.4080209@hollants.com>
References: <441AA125.6050900@hollants.com> <441AA8AF.4080209@hollants.com>
Message-ID: <441ADF4F.4030201@hollants.com>

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

Small correction: of course, my assumption, that wpa_supplicant wouldn't
work correctly at all, was wrong, as the patch only affects the error
messages when ioctl() fails. Which, as I was too blind to see this
morning, naturally does not happen under normal circumstances.

Yet, the patch looks correct and necessary to me, albeit not critical.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGt9Pa8/cc5b1WpwRAhp3AJ42o9U/bQisY9sgFR11B5lTzkEwrwCfRVTF
tufxvchKX/il3lFjg1o4e2U=
=v2G+
-----END PGP SIGNATURE-----



From pieter  Fri Mar 17 08:18:14 2006
From: pieter (Pieter Hollants)
Date: Fri, 17 Mar 2006 17:18:14 +0100
Subject: Possible solution for "Failed to set PTK to the driver" errors with
	madwifi-ng
Message-ID: <441AE146.7090309@hollants.com>

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

Just as a hint for other users, possibly those who like I work on
embedded systems: if wpa_supplicant on madwifi-ng based hardware fails
to complete its 4-way handshake with error messages such as these

WPA: Installing PTK to the driver.
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
ioctl[IEEE80211_IOCTL_SETKEY]: No such device or address.
WPA: Failed to set PTK to the driver.

then, as advanced users will immediately notice, this is not a
wpa_supplicant bug. And actually, it is no madwifi-ng bug either, as you
will find out if you use madwifi's 80211debug utility: error messages
like these appear when your system's module loading facilities do not
work properly. Unfortunately this error message is surpressed by default.

I thought this hint might be useful here, since users might probably not
be completely clear about the different components entailed, and the
same symptom might also occur with other drivers that employ the
net80211 stack.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGuCta8/cc5b1WpwRAkrvAJ9JPln7tqViDXPI4akWVtTfeRn2oACgpN52
7g+Tsc43GcKPWbzN3wW9It4=
=NNQm
-----END PGP SIGNATURE-----



From Edwin.Whitelaw  Fri Mar 17 11:30:17 2006
From: Edwin.Whitelaw (Edwin Whitelaw)
Date: Fri, 17 Mar 2006 14:30:17 -0500
Subject: Routing throughput problem - Voyage 0.2pre4 on WRAP w/NL2511 hostap
Message-ID: <441B0E49.7070509@nrvunwired.net>

I've got a WRAP running 0.2pre4 with two NL2511 cards installed (wlan0,
wlan1).  wlan1 is in client mode and wlan0 set as an AP.

Everything associates fine and I can get consistent 4+mbs indicated by
iperf when talking to/from the WRAP out either interface.  However,
throughput *through* the system, in one radio and out the other, is
terrible varying from around 1 mbs down to the 100kbs range.

I'm using simple routing, no tricks.  No log entries or errors to give a
clue.

I've had an almost identical setup (one radio is a CM9 in 11a managed
mode) in the field for months and it works great.  The diagram below
shows my test environment.

DebianPC--copper--OrinocoAP1000/\/11b/\/\wlan1(STA)-WRAP-wlan0(AP)/\/W2K-laptop
172.17.1.2                       Ch 6  172.17.1.25    172.17.10.1 Ch 11

iperf from the PC to/from the WRAP is over 4mbs tested in either direction
iperf from the laptop is also over 4mbs to/from the WRAP
iperf from the DebianPC to the laptop is terrible :-(

Anyone have an idea about what's causing the throughput problem?

Thanks,

Edwin

-- 
<=+=+=+==+=+=+==+=+=+=+=+=+=+=+=>
Edwin Whitelaw, P.E.
New River Valley Unwired, LLC
2200 Lonesome Dove Dr
Christiansburg, VA 24073
540-239-0318





From re2823  Fri Mar 17 18:41:38 2006
From: re2823 (Jaime)
Date: Sat, 18 Mar 2006 02:41:38 +0000
Subject: "wpa_supplicant -B -w" ups the interface but the Debian docs say
	it shouldn't
Message-ID: <1142649699.6297.3.camel@t21jt>

Hi all.

I am writing to try to find out whether the following behaviour is a bug
or not:
When I run "wpa_supplicant -B -w" against my ndiswrapper interface, the
wpa_supplicant process appears to bring up the interface:

Result of running "ifconfig -s":
Iface   MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR
eth0   1500 0     563      0      0      0   629      0      0 0     
lo    16436 0       0      0      0      0     0      0      0 0     

Then run "/usr/sbin/wpa_supplicant -B -w -i wlan0 -D wext -c 
/etc/wpa_supplicant.conf"

Then run "ifconfig -s" again:
Iface   MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR
eth0   1500 0     569      0      0      0   629      0      0      0
lo    16436 0       0      0      0      0     0      0      0      0
wlan0  1500 0       2      0      0      0     0      0      2      0

The wlan0 remains up until I kill the wpa_supplicant process, at which
point the interface then goes down again. I get this behaviour using
wpa_supplicant 0.4.5 (under Ubuntu 5.10) and wpa_supplicant 0.4.7 (under
Debian Etch).

The reason why I am writing this email is that Debian's wpa_supplicant
package contains a file which states that when wpa_supplicant is run
with the -Bw flags, "the wpa_supplicant daemon will start, and sit
waiting for the name interface to come up" (rather than bringing up that
interface).

So as far as I can tell, either:
a) running "wpa_supplicant -B -w" SHOULD up the interface (in which case
there is a bug in Debian's wpa_supplicant documentation, or
b) running "wpa_supplicant -B -w" SHOULDN'T up the interface (in which
case I've observed a bug in wpa_supplicant's behaviour).

Any comments on what SHOULD happen would be gratefully appreciated...

Thank you, Dave

PS I logged my original Debian bug regarding this behaviour here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356144
(Please ignore the ifupdown comments...)





From jkmaline  Fri Mar 17 18:58:32 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 17 Mar 2006 18:58:32 -0800
Subject: "wpa_supplicant -B -w" ups the interface but the Debian docs say
	it shouldn't
In-Reply-To: <1142649699.6297.3.camel@t21jt>
References: <1142649699.6297.3.camel@t21jt>
Message-ID: <20060318025832.GB9381@jm.kir.nu>

On Sat, Mar 18, 2006 at 02:41:38AM +0000, Jaime wrote:

> I am writing to try to find out whether the following behaviour is a bug
> or not:
> When I run "wpa_supplicant -B -w" against my ndiswrapper interface, the
> wpa_supplicant process appears to bring up the interface:

That is the expected behavior.

> The reason why I am writing this email is that Debian's wpa_supplicant
> package contains a file which states that when wpa_supplicant is run
> with the -Bw flags, "the wpa_supplicant daemon will start, and sit
> waiting for the name interface to come up" (rather than bringing up that
> interface).

That "to come up" needs to be interpreted as "to appear".. In other
words, "-w" is used to wait for an interface to be added (no need to set
it UP). This was added for removable devices (pccard/cardbus/usb).

-- 
Jouni Malinen                                            PGP id EFC895FA



From pieter  Sat Mar 18 05:12:30 2006
From: pieter (Pieter Hollants)
Date: Sat, 18 Mar 2006 14:12:30 +0100
Subject: [PATCH] Bring hostapd driver_madwifi.c ioctl error handling in-line
	with madwifi-ng r1331 and later
Message-ID: <441C073E.4020903@hollants.com>

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

Same patch as yesterday, this time for hostapd.

As before, this patch fixes the error handling in driver_madwifi.c's
set80211priv() to be in sync with the order used by madwifi-ng since rev
1331.

The patch is against 0.5.1, but should apply to current CVS rev 1.42 as
well.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEHAc+a8/cc5b1WpwRAsxkAJ9SFqnD5KYoUCZX5Pb/VLDKXzeQhACg7Z1s
mF+6KQBmwOErbpRJGThQOvA=
=tok+
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd-0.5.1-madwifing-ioctls.diff
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060318/4ef53d2f/attachment.txt 


From engage  Sat Mar 18 17:36:21 2006
From: engage (engage)
Date: Sat, 18 Mar 2006 18:36:21 -0700
Subject: wpa_supplicant, ndiswrapper, kernel 2.6.15.6
Message-ID: <200603181836.21948.engage@n0sq.us>

I just built kernel 2.6.15.6 on an Athlon 64 system but I have a problem with 
wpa_supplicant running on this kernel. This is a Mandriva 2006 system. 
Anyway, ndiswrapper (1.9) loads ok and the driver and hardware show present. 
But, when I start wpa_supplicant (0.4.8), there's no association with the AP 
and there are no errors. But, I did notice the following from dmesg:

ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
gcc-4.0'
ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
gcc-4.0'
ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
gcc-4.0'
ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
gcc-4.0'
ndiswrapper version 1.9 loaded (preempt=no,smp=no)
ndiswrapper: driver bcmwl5 (Linksys,07/17/2003, 3.30.15.0) loaded
ndiswrapper: using irq 21
wlan0: ndiswrapper ethernet device 00:0f:66:6d:8d:c9 using driver bcmwl5, 
14E4:4320:1737:0014.5.conf

Everything works fine with kernel 2.6.12-17mdk except that wpa_supplicant 
doesn't seem to work from /etc/rc.local.




From dcbw  Sun Mar 19 08:57:24 2006
From: dcbw (Dan Williams)
Date: Sun, 19 Mar 2006 11:57:24 -0500
Subject: wpa_supplicant, ndiswrapper, kernel 2.6.15.6
In-Reply-To: <200603181836.21948.engage@n0sq.us>
References: <200603181836.21948.engage@n0sq.us>
Message-ID: <1142787445.2294.24.camel@localhost.localdomain>

On Sat, 2006-03-18 at 18:36 -0700, engage wrote:
> I just built kernel 2.6.15.6 on an Athlon 64 system but I have a problem with 
> wpa_supplicant running on this kernel. This is a Mandriva 2006 system. 
> Anyway, ndiswrapper (1.9) loads ok and the driver and hardware show present. 
> But, when I start wpa_supplicant (0.4.8), there's no association with the AP 
> and there are no errors. But, I did notice the following from dmesg:
> 
> ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
> gcc-4.0'
> ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
> gcc-4.0'
> ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
> gcc-4.0'
> ndiswrapper: version magic '2.6.15.6 K8 gcc-4.0' should be '2.6.15.6 K7 
> gcc-4.0'
> ndiswrapper version 1.9 loaded (preempt=no,smp=no)
> ndiswrapper: driver bcmwl5 (Linksys,07/17/2003, 3.30.15.0) loaded
> ndiswrapper: using irq 21
> wlan0: ndiswrapper ethernet device 00:0f:66:6d:8d:c9 using driver bcmwl5, 
> 14E4:4320:1737:0014.5.conf

This means that your newly recompiled kernel was not built with the same
options as your original kernel.  Recompile your kernel with the
original kernel's options and you should be fine.  Linux kernel modules
have a "version magic" that _MUST_ match the kernel's, otherwise they
won't load.

Note the K8 vs. K7 different between the kernel and your module.

Dan





From pelusitavali  Sun Mar 19 16:55:01 2006
From: pelusitavali (Pelusa Vali)
Date: Mon, 20 Mar 2006 00:55:01 +0000
Subject: hostapd and madwifi don't work well
Message-ID: <PM.22187.1142816101@pmweb5.uk1.bibliotech.net>

hi list, well i'd like report problems i'm having with madwifi and hostapd.
first of all i had to upgrade to etch from sarge to get last libraries needed to compile hostapd, in other way it was impossible, trying to install them alone get my system totally unstable.
well after upgrading and installed whole libraries needed, i compiled madwifi-ng-r1475, everything was ok, my clients could connect and work very well by hours, no problem.
so wanted to add security, decided to use hostapd, i really want tls but for testing purposes decided start only with psk, so compiled hostapd-0.5.1, i could do this: 

make clean
make
make install

but any file was copied to system, so copied hostapd.conf from madwifi docs and try to work, i could start program and clients try to connect, even get connection by 2 seconds at intervals, but never get total connection, always stay in "Aquiring network address" and i get this from hostapd:

ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 3/4 msg of 4-Way Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED]
TX EAPOL - hexdump(len=153): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 87 fe 01 ca 00 10 00 00 00 00 00 00 00 05 b2 28 81 f6 12 c2 cf 57 b1 cf 17 06 7d  da 74 42 d7 be 81 63 48 51 73 cf c5 59 67 31 3f 6d 22 87 00 00 00 00 00 00 00 0 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97 2d b4 0f 31 bb 01 07 9a 04 dc b2 6f 6c a7 2e 00 28 73 04 45 27 49 f6 96 ab 0e 19 c7  0f 76 8c 81 c4 f3 44 f0 72 f3 aa e4 22 fe 7d 31 70 fa ff fa c0 96 4c 97 8f a2 3 c c5 4e
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:0f:66 :11:c1:96 reason 2
madwifi_sta_deauth: addr=00:0f:66:11:c1:96 reason_code=2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state DISCONNECTED
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ioctl[unknown???]: Invalid argument
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=0
ioctl[unknown???]: Invalid argument
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: deauthenticated due to local deauth req uest
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:66:11:c1:96 WPA: event 1 notification
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 WPA: start authentication
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=0
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state IDLE
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state AUTHENTICATION
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITPSK
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=121): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 67 fe 00 8a 00 10 00 00 00 00 00 00 00 01 b2 28 81 f6 12 c2 cf 57 b1 cf 17 06 7d  da 74 42 d7 be 81 63 48 51 73 cf c5 59 67 31 3f 6d 22 88 00 00 00 00 00 00 00 0 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 5 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=1 length=0
   ignoring 1 extra octets after IEEE 802.1X packet
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 3/4 msg of 4-Way Handshake

Ethereal always shows MDS HEADER MALFORMED PACKET.
 
so decided try with hostapd-0.4.8, and now get this:

ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=TKIP addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: authorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=1
madwifi_sta_clear_stats: addr=00:0f:66:11:c1:96
ath0: STA 00:0f:66:11:c1:96 WPA: pairwise key handshake completed (WPA)
madwifi_sta_clear_stats: addr=00:0f:66:11:c1:96
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): 6c d7 50 cf 76 e1 ed 65 ce 95 4a  3a c4 bf fd 10 45 a0 c2 11 0b e0 59 ff c7 c9 41 12 9f 72 3c 19
ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): 6c d7 50 cf 76 e1 ed 65 ce 95 4a  3a c4 bf fd 10 45 a0 c2 11 0b e0 59 ff c7 c9 41 12 9f 72 3c 19
IEEE 802.1X: 99 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:0f:66:11:c1:96 WPA: group key handshake completed (WPA)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state IDLE
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: associated
ath0: STA 00:0f:66:11:c1:96 WPA: event 1 notification
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 WPA: event 4 notification
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITPSK
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
IEEE 802.1X: 5 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=1 length=0
   ignoring 1 extra octets after IEEE 802.1X packet
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): be 6c 65 0a f0 3b ab 57 0a 8e 33 d4 35 ef a3 e6 1b 72 d5 6c 86 0d 34 61 da 4a db 68 50 e2 4c 35
PTK - hexdump(len=64): fe 57 c4 28 a6 f0 8a 15 9c 52 97 96 ab cc ce 77 fe 8d e7 3e 45 90 65 4c aa 61 09 2c a2 5e 12 95 c8 69 a6 c2 21 9a bd 4d 00 58 d6 46 63 d6  90 68 ed d8 9d 34 54 77 2b 98 95 89 99 cf 94 cb 56 cf
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 3/4 msg of 4-Way Handshake
IEEE 802.1X: 99 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=TKIP addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: authorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=1
madwifi_sta_clear_stats: addr=00:0f:66:11:c1:96
ath0: STA 00:0f:66:11:c1:96 WPA: pairwise key handshake completed (WPA)
madwifi_sta_clear_stats: addr=00:0f:66:11:c1:96
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/2 msg of Group Key Handshake
Plaintext EAPOL-Key Key Data - hexdump(len=32): 6c d7 50 cf 76 e1 ed 65 ce 95 4a  3a c4 bf fd 10 45 a0 c2 11 0b e0 59 ff c7 c9 41 12 9f 72 3c 19
IEEE 802.1X: 99 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:0f:66:11:c1:96 WPA: group key handshake completed (WPA)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state IDLE
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: deassociated
ath0: STA 00:0f:66:11:c1:96 WPA: event 2 notification
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ioctl[unknown???]: Invalid argument

clients of course cann't connect and always stay in "Aquiring network address"

finally decided to try with hostapd-0.5.1.deb, now get this:

www:/home/server# /etc/init.d/hostapd start
Starting advanced IEEE 802.11 management: hostapdioctl[unknown???]: Argument list too long
...failed.

www:/home/server# hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:0f:66:11:c1:97 and ssid 'MYWLAN'
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0x2
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
madwifi_set_privacy: enabled=1
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
ioctl[unknown???]: Argument list too long
Could not connect to kernel driver.
Deauthenticate all stations
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0

nothing happens, nothing works.

so decided back to initial configuration, without hostapd, but now clients disconnect each 10 minutes, so something is wrong with my system, but what?? with first implementation clients showed successfull wlan connection icon (winxp), now, they are connected but icon shows they are not, and ethereal shows MDS MALFORMED PACKET.

so two questions:

1) what should i do to get my system again working well, as first implementation?? i deleted everything related with hostapd.  should i reinstall whole system? Please tell me it's not necessary!!
2) why hostapd and madwifi aren't talking each other??

this is my hostapd.conf file:

interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=1
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=MYWLAN
macaddr_acl=0
auth_algs=1
wpa_passphrase=mywlan
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP 

ok, i know it's a huge e-mail, excuse me, i hope some charitable soul could help me.

thanks in advance for your patience.




_______________________________________________________________ 
The island of Gotland belongs to which country? 

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=183




From jkmaline  Sun Mar 19 17:13:32 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 19 Mar 2006 17:13:32 -0800
Subject: [PATCH} Make AP_MAX_INACTIVITY configurable
In-Reply-To: <118619310603161731q1c14a833xa80bf4435807fc36@mail.gmail.com>
References: <118619310603161731q1c14a833xa80bf4435807fc36@mail.gmail.com>
Message-ID: <20060320011332.GB9370@jm.kir.nu>

On Thu, Mar 16, 2006 at 05:31:32PM -0800, Ryan Castellucci wrote:

> This patch applies fine on 0.4.8. It adds the config file option
> 'max_inactivity'.

Thanks! This did not apply to development branch anymore due to
changes in configuration data structures. I merged in similar changes
and the same functionality is now available. Though, the parameter name
is ap_max_inactivity, not max_inactivity.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Mar 19 17:34:13 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 19 Mar 2006 17:34:13 -0800
Subject: [PATCH] Re-synchronize driver_madwifi.c ioctl order with
	madwifi-ng rev 1331 and later
In-Reply-To: <441AA125.6050900@hollants.com>
References: <441AA125.6050900@hollants.com>
Message-ID: <20060320013413.GC9370@jm.kir.nu>

On Fri, Mar 17, 2006 at 12:44:37PM +0100, Pieter Hollants wrote:

> In wpa_supplicant/driver_madwifi.c, rev. 1.19 added support for
> madwifi-ng's at that time new private ioctls. That was based against SVN
> rev 1298-1330 of madwifi-ng's net80211/net80211_wireless.c, in which the
> ioctl order still was SETPARAM, GETPARAM, SETKEY etc.
> 
> However, as http://madwifi.org/changeset/1331 shows, the ioctls were
> reordered on 22 November last year, and wpa_supplicant wasn't updated so
> far to reflect these changes.

Great.. That's not exactly what I would like to see happening with
ioctl() numbers.. I applied your patches to both wpa_supplicant and
hostapd with some extra code to avoid similar changes to first/last item
in the list from causing possible buffer overflows.

-- 
Jouni Malinen                                            PGP id EFC895FA



From lilycocola  Sun Mar 19 19:24:21 2006
From: lilycocola (lily coco)
Date: Mon, 20 Mar 2006 12:24:21 +0900 (JST)
Subject: About LEAP
Message-ID: <20060320032421.91990.qmail@web3502.mail.bbt.yahoo.co.jp>

It is said that LEAP requires special support from the
driver. Can anyone explain the reason for me? TIA.


--------------------------------------
TSUKAME EIKOU! KAGAYAKE EGAO!
Yahoo! JAPAN JPC OFFICIAL PARTNER INTERNET PORTAL SITE
http://pr.mail.yahoo.co.jp/wintergames/



From jkmaline  Sun Mar 19 19:29:38 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 19 Mar 2006 19:29:38 -0800
Subject: hostapd/wpa_supplicant - new development release v0.5.2
Message-ID: <20060320032938.GA9355@jm.kir.nu>

New versions of wpa_supplicant and hostapd were just
released and are now available from http://hostap.epitest.fi/

This release is from the development branch (0.5.x). Please note that
0.4.x branch continues to be the current source of stable releases.


hostapd:
* fixed stdarg use in hostapd_logger(): if both stdout and syslog
  logging was enabled, hostapd could trigger a segmentation fault in
  vsyslog on some CPU -- C library combinations
* moved HLR/AuC gateway implementation for EAP-SIM/AKA into an external
  program to make it easier to use for implementing real SS7 gateway;
  eap_sim_db is not anymore used as a file name for GSM authentication
  triplets; instead, it is path to UNIX domain socket that will be used
  to communicate with the external gateway program (e.g., hlr_auc_gw)
* added example HLR/AuC gateway implementation, hlr_auc_gw, that uses
  local information (GSM authentication triplets from a text file and
  hardcoded AKA authentication data); this can be used to test EAP-SIM
  and EAP-AKA
* added Milenage algorithm (example 3GPP AKA algorithm) to hlr_auc_gw
  to make it possible to test EAP-AKA with real USIM cards (this is
  disabled by default; define AKA_USE_MILENAGE when building hlr_auc_gw
  to enable this)
* driver_madwifi: added support for getting station RSN IE from
  madwifi-ng svn r1453 and newer; this fixes RSN that was apparently
  broken with earlier change (r1357) in the driver
* changed EAP method registration to use a dynamic list of methods
  instead of a static list generated at build time
* fixed WPA message 3/4 not to encrypt Key Data field (WPA IE)
  [Bug 125]
* added ap_max_inactivity configuration parameter

wpa_supplicant:
* do not try to use USIM APDUs when initializing PC/SC for SIM card
  access for a network that has not enabled EAP-AKA
* fixed EAP phase 2 Nak for EAP-{PEAP,TTLS,FAST} (this was broken in
  v0.5.1 due to the new support for expanded EAP types)
* added support for generating EAP Expanded Nak
* try to fetch scan results once before requesting new scan when
  starting up in ap_scan=1 mode (this can speed up initial association
  a lot with, e.g., madwifi-ng driver)
* added support for receiving EAPOL frames from a Linux bridge
  interface (-bbr0 on command line)
* fixed EAPOL re-authentication for sessions that used PMKSA caching
* changed EAP method registration to use a dynamic list of methods
  instead of a static list generated at build time
* fixed PMKSA cache deinitialization not to use freed memory when
  removing PMKSA entries
* fixed a memory leak in EAP-TTLS re-authentication
* reject WPA/WPA2 message 3/4 if it does not include any valid
  WPA/RSN IE
* driver_wext: added fallback to use SIOCSIWENCODE for setting auth_alg
  if the driver does not support SIOCSIWAUTH


-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Mar 19 19:32:22 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 19 Mar 2006 19:32:22 -0800
Subject: About LEAP
In-Reply-To: <20060320032421.91990.qmail@web3502.mail.bbt.yahoo.co.jp>
References: <20060320032421.91990.qmail@web3502.mail.bbt.yahoo.co.jp>
Message-ID: <20060320033222.GB9355@jm.kir.nu>

On Mon, Mar 20, 2006 at 12:24:21PM +0900, lily coco wrote:
> It is said that LEAP requires special support from the
> driver. Can anyone explain the reason for me? TIA.

Strictly speaking, LEAP (as in EAP method) does not require driver
support. However, LEAP is often used with Cisco APs that are configured
to require "Network EAP" authentication algorithm and that is the part
that requires driver support on the driver. If the AP is configured to
allow open system authentication with LEAP, no additional driver support
is needed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From svens  Sun Mar 19 23:04:31 2006
From: svens (Sven Schnelle)
Date: Mon, 20 Mar 2006 08:04:31 +0100
Subject: hostapd and madwifi don't work well
In-Reply-To: <PM.22187.1142816101@pmweb5.uk1.bibliotech.net> (Pelusa Vali's
	message of "Mon, 20 Mar 2006 00:55:01 +0000")
References: <PM.22187.1142816101@pmweb5.uk1.bibliotech.net>
Message-ID: <86hd5ty4u8.fsf@deprecated.bitebene.org>

A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060320/c4f5a192/attachment.pgp 


From mistamaila  Sun Mar 19 23:31:05 2006
From: mistamaila (John H.)
Date: Mon, 20 Mar 2006 01:31:05 -0600
Subject: -Dwext problems with zydas driver and wpa-psk - ioctl[SIOCSIWPMKSA]:
	Invalid argument, Could not configure driver to use managed mode,
	Association request to the driver failed
Message-ID: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>

I don't know what's wrong, it's just not working anymore, but same
router works in XP.  Currently using .67 of zd1211 driver and
wpa_supplicant .4.8, but get same results from .5.2.

I ran wpa_passphrase again and used the generated config, but same problem.

 /usr/src/wpasupplicant/wpa_supplicant -w -i wlan0 -c
/etc/wpa_supplicant.conf -Dwext
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Associated with 00:90:4b:36:b8:66
WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (auth)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Associated with 00:90:4b:36:b8:66
WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (reauth)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Associated with 00:90:4b:36:b8:66
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Associated with 00:90:4b:36:b8:66
WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (reauth)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Associated with 00:90:4b:36:b8:66
WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (reauth)
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Associated with 00:90:4b:36:b8:66
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Associated with 00:90:4b:36:b8:66
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Associated with 00:90:4b:36:b8:66
WPA: 4-Way Handshake failed - pre-shared key may be incorrect
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-TERMINATING - signal 2 received
Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed



From jhz  Mon Mar 20 00:58:48 2006
From: jhz (Jared Holzman)
Date: Mon, 20 Mar 2006 16:58:48 +0800
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
In-Reply-To: <44166CFA.3000404@mrxtech.com.au>
References: <44166CFA.3000404@mrxtech.com.au>
Message-ID: <441E6EC8.6060500@mrxtech.com.au>

Hey Guys,

Haven't heard a single response so far. Does this mean my problem has 
baffled everybody? Or has nobody bothered to look? If somebody wouldn't 
mind at least having a quick look at my hostapd.conf below to see it 
that's where the problem lies, that'd be great.

Thanks,
Jared

Jared Holzman wrote:

>To All,
>
>I'm having trouble trying to configure HostAP with static WEP on my 
>server. Configuration seems to work using iwconfig tool (iwconfig mode 
>Master, iwconfig essid, iwconfig key etc, etc) and I can then use the 
>AP. However once I start the hostapd daemon, the encryption key seems to 
>disappear from iwconfig and the AP becomes unusuable (in both unsecured 
>mode and WEP mode) and if I try and set the key subsequently, using the 
>iwconfig tool, it fails with an error and then comes up with invalid 
>output until I reset the device.
>
>Any Ideas?
>
>Thanks,
>
>Jared
>
>PS Following is some relevant log information
>
>[root at bob root]# iwconfig wlan0
>wlan0     IEEE 802.11b  ESSID:"homezone"  Nickname:"bob.homezone"
>          Mode:Master  Frequency:2.437 GHz  Access Point: 00:09:5B:67:92:F2   
>          Bit Rate:5.5 Mb/s   Sensitivity=1/3  
>          Retry min limit:8   RTS thr:off   Fragment thr:off
>          Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security mode:restricted
>          Power Management:off
>          Link Quality:0  Signal level:0  Noise level:0
>          Rx invalid nwid:0  Rx invalid crypt:2  Rx invalid frag:0
>          Tx excessive retries:460  Invalid misc:171   Missed beacon:0
>
>[root at bob root]# cat /etc/hostapd/hostapd.conf | grep -v ^\#
>interface=wlan0
>logger_syslog=-1
>logger_syslog_level=2
>logger_stdout=-1
>logger_stdout_level=2
>debug=0
>dump_file=/tmp/hostapd.dump
>ctrl_interface=/var/run/hostapd
>ctrl_interface_group=0
>ssid=homezone
>macaddr_acl=0
>accept_mac_file=/etc/hostapd/hostapd.accept
>deny_mac_file=/etc/hostapd/hostapd.deny
>auth_algs=3
>eapol_key_index_workaround=0
>eap_server=0
>own_ip_address=127.0.0.1
>
>[root at bob root]# hostapd -dd /etc/hostapd/hostapd.conf
>Configuration file: /etc/hostapd/hostapd.conf
>Opening raw packet socket for ifindex 11
>Using interface wlan0 with hwaddr 00:09:5b:67:92:f2 and ssid 'homezone'
>Flushing old station entries
>Deauthenticate all stations
>Wireless event: cmd=0x8c04 len=20
>Wireless event: cmd=0x8b2a len=8
>Received 268 bytes management frame
>DATA
>Data frame from not associated STA 00:0f:b5:8e:da:43
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 24 bytes management frame
>DATA
>Data frame from not associated STA 00:09:5b:67:8e:fd
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Signal 2 received - terminating
>Flushing old station entries
>Deauthenticate all stations
>Could not disable PrivacyInvoked for interface wlan0
>Could not remove generic information element from interface wlan0
>
>[root at bob root]# hostapd -dd /etc/hostapd/hostapd.conf
>Configuration file: /etc/hostapd/hostapd.conf
>Opening raw packet socket for ifindex 17
>Using interface wlan0 with hwaddr 00:09:5b:67:92:f2 and ssid 'homezone'
>Flushing old station entries
>Deauthenticate all stations
>Wireless event: cmd=0x8c04 len=20
>Wireless event: cmd=0x8b2a len=8
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 24 bytes management frame
>DATA
>Data frame from not associated STA 00:09:5b:67:8e:fd
>Received 24 bytes management frame
>DATA
>Data frame from not associated STA 00:09:5b:67:8e:fd
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 60 bytes management frame
>DATA
>Data frame from not associated STA 00:0f:b5:8e:da:43
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 342 bytes management frame
>extra data in frame (elen=0)
>unknown frame type 3
>Received 360 bytes management frame
>DATA
>Data frame from not associated STA 00:0f:b5:8e:da:43
>
>Received 360 bytes management frame
>DATA
>Data frame from not associated STA 00:0f:b5:8e:da:43
>
>[root at bob root]# iwconfig wlan0
>wlan0     IEEE 802.11b  ESSID:"homezone"  Nickname:"bob.homezone"
>          Mode:Master  Frequency:2.437 GHz  Access Point: 00:09:5B:67:92:F2
>          Bit Rate:11 Mb/s   Sensitivity=1/3
>          Retry min limit:8   RTS thr:off   Fragment thr:off
>          Encryption key:off
>          Power Management:off
>          Link Quality:0  Signal level:0  Noise level:0
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:1  Invalid misc:14   Missed beacon:0
>
>[root at bob root]# iwconfig wlan0 key XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
>Error for wireless request "Set Encode" (8B2A) :
>    SET failed on device wlan0 ; Invalid argument.
>[root at bob root]# iwconfig wlan0
>wlan0     IEEE 802.11-DS  ESSID:"homezone"
>          Mode:Master
>          Link Quality:0  Signal level:0  Noise level:0
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:1  Invalid misc:14   Missed beacon:0
>
>
>[root at bob root]# iwconfig -v
>iwconfig  Wireless-Tools version 28
>          Compatible with Wireless Extension v11 to v19.
>
>Kernel    Currently compiled with Wireless Extension v19.
>
>wifi0     Recommend Wireless Extension v18 or later,
>          Currently compiled with Wireless Extension v19.
>
>wlan0     Recommend Wireless Extension v18 or later,
>          Currently compiled with Wireless Extension v19.
>
>wlan0ap   Recommend Wireless Extension v18 or later,
>          Currently compiled with Wireless Extension v19.
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>



From brix  Mon Mar 20 01:03:06 2006
From: brix (Henrik Brix Andersen)
Date: Mon, 20 Mar 2006 10:03:06 +0100
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
In-Reply-To: <441E6EC8.6060500@mrxtech.com.au>
References: <44166CFA.3000404@mrxtech.com.au> <441E6EC8.6060500@mrxtech.com.au>
Message-ID: <20060320090306.GA4042@osgiliath.brixandersen.dk>

On Mon, Mar 20, 2006 at 04:58:48PM +0800, Jared Holzman wrote:
> Haven't heard a single response so far. Does this mean my problem has 
> baffled everybody? Or has nobody bothered to look? If somebody wouldn't 
> mind at least having a quick look at my hostapd.conf below to see it 
> that's where the problem lies, that'd be great.

Why run hostapd when using static WEP?

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


From jhz  Mon Mar 20 01:58:11 2006
From: jhz (Jared Holzman)
Date: Mon, 20 Mar 2006 17:58:11 +0800
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
In-Reply-To: <20060320090306.GA4042@osgiliath.brixandersen.dk>
References: <44166CFA.3000404@mrxtech.com.au> <441E6EC8.6060500@mrxtech.com.au>
	<20060320090306.GA4042@osgiliath.brixandersen.dk>
Message-ID: <441E7CB3.8020903@mrxtech.com.au>

I've got no idea. I assumed running the hostapd daemon was neccessary 
for correct AP operation. There's nothing in the documentation about not 
running hostapd if you're using static WEP. What if you wanted to do MAC 
filtering?


Henrik Brix Andersen wrote:

>On Mon, Mar 20, 2006 at 04:58:48PM +0800, Jared Holzman wrote:
>  
>
>>Haven't heard a single response so far. Does this mean my problem has 
>>baffled everybody? Or has nobody bothered to look? If somebody wouldn't 
>>mind at least having a quick look at my hostapd.conf below to see it 
>>that's where the problem lies, that'd be great.
>>    
>>
>
>Why run hostapd when using static WEP?
>
>Regards,
>Brix
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060320/612738b0/attachment.htm 


From pieter  Mon Mar 20 02:08:12 2006
From: pieter (Pieter Hollants)
Date: Mon, 20 Mar 2006 11:08:12 +0100
Subject: -Dwext problems with zydas driver and wpa-psk -
	ioctl[SIOCSIWPMKSA]:
	Invalid argument, Could not configure driver to use managed mode,
	Association request to the driver failed
In-Reply-To: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
References: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
Message-ID: <441E7F0C.6020404@hollants.com>

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

John H. schrieb:
>  /usr/src/wpasupplicant/wpa_supplicant -w -i wlan0 -c
> /etc/wpa_supplicant.conf -Dwext
> ioctl[SIOCSIWPMKSA]: Invalid argument
> ioctl[SIOCSIWMODE]: Invalid argument
> Could not configure driver to use managed mode
> Trying to associate with 00:90:4b:36:b8:66 (SSID='dapt' freq=2437 MHz)
> ioctl[SIOCSIWFREQ]: Invalid argument
> Association request to the driver failed

I don't know about the zydas driver, but in my case (madwifi-ng) it
helped to enabled the driver-specific debug options with athdebug and
80211debug. If there aren't any, you might want to temporarily insert
some debug printk()'s in the drivers' ioctl-handling code, to see what's
going on exactly.

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEHn8Ma8/cc5b1WpwRAkQwAJ9ziwcDC3q0wg/3OUO3TlcoVVSjGACeJRbn
xhRTBAovro9GadOc5bkenUo=
=bn6z
-----END PGP SIGNATURE-----



From pelusitavali  Mon Mar 20 02:10:14 2006
From: pelusitavali (Pelusa Vali)
Date: Mon, 20 Mar 2006 10:10:14 +0000
Subject: hostapd and madwifi don't work well
Message-ID: <PM.13861.1142849414@pmweb19.uk1.bibliotech.net>

On Mon, 20 Mar 2006 08:04:31 +0100 , "Sven Schnelle" <svens at gmx.de>  wrote:
>Hi,
>
>Pelusa Vali <pelusitavali at postmaster.co.uk> writes:
>
>> so wanted to add security, decided to use hostapd, i really want tls
>> but for testing purposes decided start only with psk, so compiled
>> hostapd-0.5.1, i could do this:
>>
>> make clean
>> make
>> make install
>
>Did you compile hostapd against your madwifi-ng sources? you should
>have a line like 'CFLAGS += -I/usr/src/madwifi-ng' in your .config.
>
>Sven.

yes, this is my .config file:

CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I/usr/src/madwifi-ng/
CONFIG_IAPP=y
CONFIG_RSN_PREAUTH=y
CONFIG_EAP=y
CONFIG_EAP_MD5=y
CONFIG_EAP_TLS=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_TTLS=y
CONFIG_PKCS12=y
CONFIG_RADIUS_SERVER=y
CONFIG_IPV6=y






_______________________________________________________________ 
Halloween Humour: What do you call a monster with gravy, meat and potatos on his head?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=139




From jar  Mon Mar 20 05:42:23 2006
From: jar (Jar)
Date: Mon, 20 Mar 2006 15:42:23 +0200
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
In-Reply-To: <441E7CB3.8020903@mrxtech.com.au>
References: <44166CFA.3000404@mrxtech.com.au>
	<441E6EC8.6060500@mrxtech.com.au>	<20060320090306.GA4042@osgiliath.brixandersen.dk>
	<441E7CB3.8020903@mrxtech.com.au>
Message-ID: <441EB13F.5040806@pcuf.fi>

Jared Holzman wrote:
> I've got no idea. I assumed running the hostapd daemon was neccessary 
> for correct AP operation. There's nothing in the documentation about not 

Not for the basic AP operation.

> running hostapd if you're using static WEP. What if you wanted to do MAC 
> filtering?

Something like this maybe:

$IWPRIV $WLAN_DEV maccmd 1              # Allow policy for ACL list
$IWPRIV $WLAN_DEV maccmd 3              # Flush the ACL list
$IWPRIV $WLAN_DEV addmac $mac		# Add MAC $mac
$IWPRIV $WLAN_DEV maccmd 4              # Kick out all auth. stations

-- 
Best Regards, Jar



From jkmaline  Mon Mar 20 06:12:30 2006
From: jkmaline (Jouni Malinen)
Date: Mon, 20 Mar 2006 06:12:30 -0800
Subject: -Dwext problems with zydas driver and wpa-psk -
	ioctl[SIOCSIWPMKSA]: Invalid argument,
	Could not configure driver to use managed mode,
	Association request to the driver failed
In-Reply-To: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
References: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
Message-ID: <20060320141230.GA9370@jm.kir.nu>

On Mon, Mar 20, 2006 at 01:31:05AM -0600, John H. wrote:

> I don't know what's wrong, it's just not working anymore, but same
> router works in XP.  Currently using .67 of zd1211 driver and
> wpa_supplicant .4.8, but get same results from .5.2.

>  /usr/src/wpasupplicant/wpa_supplicant -w -i wlan0 -c
> /etc/wpa_supplicant.conf -Dwext

Please send more verbose debug log (i.e., add -dd to the command line).

> WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
> CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (auth)

At least the initial connection worked fine, so the basic functionality
seems to be available.

> WPA: EAPOL-Key Replay Counter did not increase - dropping packet

This is most commonly triggered if the driver does not report
disconnection to the supplicant. More verbose debug could help in
figuring out whether that is the case, but one may need to take a look
at wireless capture log of the frames sent at this point to figure out
what exactly happened unless the driver provides useful debug
information about associations.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ryan.castellucci  Mon Mar 20 11:39:20 2006
From: ryan.castellucci (Ryan Castellucci)
Date: Mon, 20 Mar 2006 11:39:20 -0800
Subject: hostapd will not start
Message-ID: <118619310603201139s4a0d4ec8i8d76f9d74fbbede5@mail.gmail.com>

I applied to patch to get hostapd to work with post-1331 madwifi-ng,
but it's refusing to start up....

This is hostapd 0.5.1 compliled agains madwifi-nr r1475

# hostapd -dddd /usr/local/etc/hostapd-ath0.conf
Configuration file: /usr/local/etc/hostapd-ath0.conf
Configure bridge br0 for EAPOL traffic.
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:02:6f:20:fa:82 and ssid 'test-ath0'
SIOCGIWRANGE: WE(compiled)=19 WE(source)=13 enc_capa=0x0
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Could not connect to kernel driver.
Deauthenticate all stations
madwifi_set_iface_flags: dev_up=0

Anyone got any sugguestions?

--
Ryan Castellucci http://ryanc.org/



From jkmaline  Mon Mar 20 20:30:28 2006
From: jkmaline (Jouni Malinen)
Date: Mon, 20 Mar 2006 20:30:28 -0800
Subject: Problem With HostAP and static WEP, kernel 2.6.14, hostap 0.47
In-Reply-To: <44166CFA.3000404@mrxtech.com.au>
References: <44166CFA.3000404@mrxtech.com.au>
Message-ID: <20060321043028.GM9370@jm.kir.nu>

On Tue, Mar 14, 2006 at 03:12:58PM +0800, Jared Holzman wrote:

> I'm having trouble trying to configure HostAP with static WEP on my 
> server. Configuration seems to work using iwconfig tool (iwconfig mode 
> Master, iwconfig essid, iwconfig key etc, etc) and I can then use the 
> AP. However once I start the hostapd daemon, the encryption key seems to 
> disappear from iwconfig and the AP becomes unusuable (in both unsecured 
> mode and WEP mode) and if I try and set the key subsequently, using the 
> iwconfig tool, it fails with an error and then comes up with invalid 
> output until I reset the device.

The current version of hostapd does not support this kind of mode (i.e.,
static WEP keys), so this would need to be done without hostapd like was
mentioned in an earlier reply.

-- 
Jouni Malinen                                            PGP id EFC895FA



From benzyg  Tue Mar 21 05:41:51 2006
From: benzyg (Gabay, Benzy)
Date: Tue, 21 Mar 2006 15:41:51 +0200
Subject: 5.1 release
Message-ID: <07CE9E6DC822DA459A1540EA834D007F9CDAC1@dile01.ent.ti.com>

Hi all,

 

Does anyone know when does the 5.1 version is due to be officially out
and fully tested?

 

Thanks

===========

Benz

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


From jkmaline  Tue Mar 21 06:25:25 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Mar 2006 06:25:25 -0800
Subject: 5.1 release
In-Reply-To: <07CE9E6DC822DA459A1540EA834D007F9CDAC1@dile01.ent.ti.com>
References: <07CE9E6DC822DA459A1540EA834D007F9CDAC1@dile01.ent.ti.com>
Message-ID: <20060321142525.GA9318@jm.kir.nu>

On Tue, Mar 21, 2006 at 03:41:51PM +0200, Gabay, Benzy wrote:

> Does anyone know when does the 5.1 version is due to be officially out
> and fully tested?

5.1 of what? If you are referring to 0.5.1 of either hostapd or
wpa_supplicant, it was "officially released", but being a development
release, I would not call it "fully tested".

-- 
Jouni Malinen                                            PGP id EFC895FA



From jfb  Tue Mar 21 12:06:52 2006
From: jfb (Juan Felipe Botero)
Date: Tue, 21 Mar 2006 15:06:52 -0500
Subject: please help with IMXL
In-Reply-To: <20060314204250.M64005@microe.udea.edu.co>
References: <20060314204250.M64005@microe.udea.edu.co>
Message-ID: <20060321200616.M54589@microe.udea.edu.co>



--
Open WebMail Project (http://openwebmail.org)


---------- Original Message -----------
From: "Juan Felipe Botero" <jfb at microe.udea.edu.co>
To: hostap at shmoo.com
Sent: Tue, 14 Mar 2006 15:48:12 -0500
Subject: help with IMXL

> I, i really need some help:
> 
> I could compile the hostap driver with the path of the linux kernel of my embedded
> system for a IMXL card based in a arm architecture.
> 
> when i compiled the kernel a folder called:
> /lib/modules/2.6.11.4-csb/kernel/drivers/net/wireless was created in my normal 
> Linux system file, so i created and copied this folder in the linux file 
> system of the embedded architecture, but when i started the Linux again, the 
> driver didn't work. i can use the modprobe and it&#347; seems like there are 
> no problems, but when i put in the command line - ifconfig wlan0 up - the 
> answer was - no such device -. I
> 
> I really don't know about that problem, if someone has worked in a IMXL card 
> please help me The compact flash card is a sinao NL-2511CF mercury, i know 
> this card has a prism2 chipset Please help me
> 
> lot of thanks 
> --
> Open WebMail Project (http://openwebmail.org)
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
------- End of Original Message -------




From gandalf_the_gray  Tue Mar 21 12:17:04 2006
From: gandalf_the_gray (FireStorm -)
Date: Tue, 21 Mar 2006 20:17:04 +0000
Subject: problem with hostap+ndiswrapper
Message-ID: <BAY107-F357A81A8AAC6E73A6A327FDCD80@phx.gbl>

Hello list,

this is not a hostap related question, but it seems that the list is 
appropriate anyway (I apologize in advance if it isn't).

Here it goes:
I am trying to make my PCMCIA card work with WPA. Wpa_supplicant seems to 
work fine, but after a few minutes the connection hangs and I am not able to 
transfer anything, unless restarting the card and restarting wpa_supplicant 
again.

Some info:
- The card uses a Linksys INPROCOMM IPN 2220 chipset.
- I use ndiswrapper version 2.7 to make it work with the neti2220.inf 
driver.
- The OS is a custom Devil-Linux with 2.4.32 kernel (with grsec).
- Wpa_supplicant is version 0.4.8
- The AP is a NetGear DG834GT

Here is the wpa_supplicant.conf file:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root
network={
        ssid="xxxx"
        key_mgmt=WPA-PSK
        proto=WPA
        psk="yyyy"
}

Looking through the wpa_supplicant log (pasted below), it seems that at 
17:28 the AP  starts  triggering GROUP_HANDSHAKE's. The first ones get 
COMPLETE'd, but after a while the PC starts to complain that "Key Replay 
Counter did not increase", dropping all subsequent packets. At that point, 
no packet makes its way to/from the PC.

Another clue: when starting wpa_supplicant I get:
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device

...but as I said, for a few minuted the link is up and running

So... anybody has some clue about how to solve this ?

Thanks in advance

Al

----- wpa_supplicant log-----
Mar 21 17:19:17.693290: Initializing interface 'wlan0' conf 
'/etc/wpa_supplicant.conf' driver 'ndiswrapper' ctrl_interface 'N/A'
Mar 21 17:19:17.693660: Configuration file '/etc/wpa_supplicant.conf' -> 
'/etc/wpa_supplicant.conf'
Mar 21 17:19:17.693685: Reading configuration file 
'/etc/wpa_supplicant.conf'
Mar 21 17:19:17.693808: ctrl_interface='/var/run/wpa_supplicant'
Mar 21 17:19:17.694653: ctrl_interface_group=0 (from group name 'root')
Mar 21 17:19:17.694710: fast_reauth=1
Mar 21 17:19:17.774947: Priority group 0
Mar 21 17:19:17.774974:    id=0 ssid='xxxxx'
Mar 21 17:19:17.775011: Initializing interface (2) 'wlan0'
Mar 21 17:19:17.785767: EAPOL: SUPP_PAE entering state DISCONNECTED
Mar 21 17:19:17.785799: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
Mar 21 17:19:17.785814: EAPOL: SUPP_BE entering state INITIALIZE
Mar 21 17:19:17.785836: EAP: EAP entering state DISABLED
Mar 21 17:19:17.786016: EAPOL: External notification - portEnabled=0
Mar 21 17:19:17.786113: EAPOL: External notification - portValid=0
Mar 21 17:19:17.788090: SIOCGIWRANGE: too old (short) data - assuming WPA is 
not supported
Mar 21 17:19:17.811576: Own MAC address: 00:01:36:0a:6d:af
Mar 21 17:19:17.811673: wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 
seq_len=0 key_len=0
Mar 21 17:19:17.813384: Driver did not support SIOCSIWENCODEEXT, trying 
SIOCSIWENCODE
Mar 21 17:19:17.813446: wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 
seq_len=0 key_len=0
Mar 21 17:19:17.815025: Driver did not support SIOCSIWENCODEEXT, trying 
SIOCSIWENCODE
Mar 21 17:19:17.815062: wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 
seq_len=0 key_len=0
Mar 21 17:19:17.816622: Driver did not support SIOCSIWENCODEEXT, trying 
SIOCSIWENCODE
Mar 21 17:19:17.816657: wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 
seq_len=0 key_len=0
Mar 21 17:19:17.818224: Driver did not support SIOCSIWENCODEEXT, trying 
SIOCSIWENCODE
Mar 21 17:19:17.818322: Setting scan request: 0 sec 100000 usec
Mar 21 17:19:17.818531: Added interface wlan0
Mar 21 17:19:17.818639: Wireless event: cmd=0x8b06 len=8
Mar 21 17:19:17.818679: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Mar 21 17:19:17.818719: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Mar 21 17:19:17.818752: Wireless event: cmd=0x8b2a len=12
Mar 21 17:19:17.818785: Wireless event: cmd=0x8b2a len=12
Mar 21 17:19:17.818817: Wireless event: cmd=0x8b2a len=12
Mar 21 17:19:17.818849: Wireless event: cmd=0x8b2a len=12
Mar 21 17:19:17.919620: State: DISCONNECTED -> SCANNING
Mar 21 17:19:17.919639: Starting AP scan (broadcast SSID)
Mar 21 17:19:20.929631: Scan timeout - try to get results
Mar 21 17:19:20.929855: Received 316 bytes of scan results (1 BSSes)
Mar 21 17:19:20.929877: Scan results: 1
Mar 21 17:19:20.929895: Selecting BSS from priority group 0
Mar 21 17:19:20.929911: 0: 00:0f:b5:57:2e:30 ssid='xxxx' wpa_ie_len=24 
rsn_ie_len=0 caps=0x11
Mar 21 17:19:20.929945:    selected based on WPA IE
Mar 21 17:19:20.929975: Trying to associate with 00:0f:b5:57:2e:30 
(SSID='NorthernFortress' freq=2452 MHz)
Mar 21 17:19:20.929994: Cancelling scan request
Mar 21 17:19:20.930009: WPA: clearing own WPA/RSN IE
Mar 21 17:19:20.930022: Automatic auth_alg selection: 0x1
Mar 21 17:19:20.930060: WPA: using IEEE 802.11i/D3.0
Mar 21 17:19:20.930077: WPA: Selected cipher suites: group 8 pairwise 8 
key_mgmt 2
Mar 21 17:19:20.930095: WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 
01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Mar 21 17:19:20.930143: WPA: clearing AP RSN IE
Mar 21 17:19:20.930160: WPA: using GTK TKIP
Mar 21 17:19:20.930176: WPA: using PTK TKIP
Mar 21 17:19:20.930193: WPA: using KEY_MGMT WPA-PSK
Mar 21 17:19:20.930210: WPA: Set own WPA IE default - hexdump(len=24): dd 16 
00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Mar 21 17:19:20.930260: No keys have been configured - skip key clearing
Mar 21 17:19:20.930282: State: SCANNING -> ASSOCIATING
Mar 21 17:19:20.931350: Setting authentication timeout: 10 sec 0 usec
Mar 21 17:19:20.931373: EAPOL: External notification - EAP success=0
Mar 21 17:19:20.931470: EAPOL: External notification - EAP fail=0
Mar 21 17:19:20.931608: EAPOL: External notification - portControl=Auto
Mar 21 17:19:20.949714: Wireless event: cmd=0x8c02 len=209
Mar 21 17:19:20.949744: Custom wireless event: 
'ASSOCINFO(ReqIEs=00104e6f72746865726e466f727472657373010802040b160c12182432043048606cdd160050f20101000050f20201000050f20201000050f202 
RespIEs=010882848b0c1296182432043048606cdd0900037f01010000ff7f)'
Mar 21 17:19:20.949787: Association info event
Mar 21 17:19:20.949802: req_ies - hexdump(len=58): 00 10 4e 6f 72 74 68 65 
72 6e 46 6f 72 74 72 65 73 73 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 
6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Mar 21 17:19:20.949892: resp_ies - hexdump(len=27): 01 08 82 84 8b 0c 12 96 
18 24 32 04 30 48 60 6c dd 09 00 03 7f 01 01 00 00 ff 7f
Mar 21 17:19:20.949943: WPA: set own WPA/RSN 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
Mar 21 17:19:20.950014: Wireless event: cmd=0x8b15 len=20
Mar 21 17:19:20.950032: Wireless event: new AP: 00:0f:b5:57:2e:30
Mar 21 17:19:20.950053: State: ASSOCIATING -> ASSOCIATED
Mar 21 17:19:20.950091: Associated to a new BSS: BSSID=00:0f:b5:57:2e:30
Mar 21 17:19:20.950108: No keys have been configured - skip key clearing
Mar 21 17:19:20.950130: Associated with 00:0f:b5:57:2e:30
Mar 21 17:19:20.950146: WPA: Association event - clear replay counter
Mar 21 17:19:20.950168: EAPOL: External notification - portEnabled=0
Mar 21 17:19:20.950266: EAPOL: External notification - portValid=0
Mar 21 17:19:20.950362: EAPOL: External notification - EAP success=0
Mar 21 17:19:20.950457: EAPOL: External notification - portEnabled=1
Mar 21 17:19:20.950472: EAPOL: SUPP_PAE entering state CONNECTING
Mar 21 17:19:20.950486: EAPOL: SUPP_BE entering state IDLE
Mar 21 17:19:20.950552: Setting authentication timeout: 10 sec 0 usec
Mar 21 17:19:20.950706: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:19:20.950737: Setting authentication timeout: 10 sec 0 usec
Mar 21 17:19:20.950760: IEEE 802.1X RX: version=1 type=3 length=95
Mar 21 17:19:20.950777:   EAPOL-Key type=254
Mar 21 17:19:20.950814: State: ASSOCIATED -> 4WAY_HANDSHAKE
Mar 21 17:19:20.950831: WPA: RX message 1 of 4-Way Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:19:20.950856: WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 
50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Mar 21 17:19:20.952630: WPA: Renewed SNonce - hexdump(len=32): bf c7 f6 67 
10 b1 9a 47 b0 76 df ad 78 d9 b4 ce 95 dc 49 8f a1 82 f0 8d a2 7f 14 6c 14 
68 38 05
Mar 21 17:19:20.952759: WPA: PMK - hexdump(len=32): [REMOVED]
Mar 21 17:19:20.952777: WPA: PTK - hexdump(len=64): [REMOVED]
Mar 21 17:19:20.952792: WPA: Sending EAPOL-Key 2/4
Mar 21 17:19:20.953182: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:19:20.953210: IEEE 802.1X RX: version=1 type=3 length=119
Mar 21 17:19:20.953227:   EAPOL-Key type=254
Mar 21 17:19:20.953259: State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
Mar 21 17:19:20.953275: WPA: RX message 3 of 4-Way Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:19:20.953295: WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 
01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Mar 21 17:19:20.953349: WPA: Sending EAPOL-Key 4/4
Mar 21 17:19:20.953402: WPA: Installing PTK to the driver.
Mar 21 17:19:20.953420: WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Mar 21 17:19:20.953470: State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
Mar 21 17:19:20.953703: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:19:20.953729: IEEE 802.1X RX: version=1 type=3 length=127
Mar 21 17:19:20.953745:   EAPOL-Key type=254
Mar 21 17:19:20.953771: State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
Mar 21 17:19:20.953787: WPA: RX message 1 of Group Key Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:19:20.953829: WPA: Group Key - hexdump(len=32): [REMOVED]
Mar 21 17:19:20.953844: WPA: Installing GTK to the driver (keyidx=2 tx=0).
Mar 21 17:19:20.953859: WPA: RSC - hexdump(len=6): 26 00 00 00 00 00
Mar 21 17:19:20.953900: WPA: Sending EAPOL-Key 2/2
Mar 21 17:19:20.953979: WPA: Key negotiation completed with 
00:0f:b5:57:2e:30 [PTK=TKIP GTK=TKIP]
Mar 21 17:19:20.954027: Cancelling authentication timeout
Mar 21 17:19:20.954066: State: GROUP_HANDSHAKE -> COMPLETED
Mar 21 17:19:20.954092: CTRL-EVENT-CONNECTED - Connection to 
00:0f:b5:57:2e:30 completed (auth)
Mar 21 17:19:20.954108: EAPOL: External notification - portValid=1
Mar 21 17:19:20.954200: EAPOL: External notification - EAP success=1
Mar 21 17:19:20.954218: EAPOL: SUPP_PAE entering state AUTHENTICATING
Mar 21 17:19:20.954233: EAPOL: SUPP_BE entering state SUCCESS
Mar 21 17:19:20.954246: EAP: EAP entering state DISABLED
Mar 21 17:19:20.954261: EAPOL: SUPP_PAE entering state AUTHENTICATED
Mar 21 17:19:20.954275: EAPOL: SUPP_BE entering state IDLE
Mar 21 17:19:23.809634: EAPOL: startWhen --> 0
Mar 21 17:28:29.579797: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:29.579852: IEEE 802.1X RX: version=1 type=3 length=127
Mar 21 17:28:29.579870:   EAPOL-Key type=254
Mar 21 17:28:29.579911: State: COMPLETED -> GROUP_HANDSHAKE
Mar 21 17:28:29.579927: WPA: RX message 1 of Group Key Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:28:29.579969: WPA: Group Key - hexdump(len=32): [REMOVED]
Mar 21 17:28:29.579985: WPA: Installing GTK to the driver (keyidx=1 tx=0).
Mar 21 17:28:29.580000: WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Mar 21 17:28:29.580063: WPA: Sending EAPOL-Key 2/2
Mar 21 17:28:29.580121: WPA: Group rekeying completed with 00:0f:b5:57:2e:30 
[GTK=TKIP]
Mar 21 17:28:29.580139: State: GROUP_HANDSHAKE -> COMPLETED
Mar 21 17:28:30.579765: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:30.579814: IEEE 802.1X RX: version=1 type=3 length=127
Mar 21 17:28:30.579830:   EAPOL-Key type=254
Mar 21 17:28:30.579867: State: COMPLETED -> GROUP_HANDSHAKE
Mar 21 17:28:30.579883: WPA: RX message 1 of Group Key Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:28:30.579924: WPA: Group Key - hexdump(len=32): [REMOVED]
Mar 21 17:28:30.579940: WPA: Installing GTK to the driver (keyidx=1 tx=0).
Mar 21 17:28:30.579955: WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Mar 21 17:28:30.580015: WPA: Sending EAPOL-Key 2/2
Mar 21 17:28:30.580078: WPA: Group rekeying completed with 00:0f:b5:57:2e:30 
[GTK=TKIP]
Mar 21 17:28:30.580095: State: GROUP_HANDSHAKE -> COMPLETED
Mar 21 17:28:31.579757: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:31.579819: IEEE 802.1X RX: version=1 type=3 length=127
Mar 21 17:28:31.579836:   EAPOL-Key type=254
Mar 21 17:28:31.579878: State: COMPLETED -> GROUP_HANDSHAKE
Mar 21 17:28:31.579894: WPA: RX message 1 of Group Key Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:28:31.579936: WPA: Group Key - hexdump(len=32): [REMOVED]
Mar 21 17:28:31.579952: WPA: Installing GTK to the driver (keyidx=1 tx=0).
Mar 21 17:28:31.579966: WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Mar 21 17:28:31.580029: WPA: Sending EAPOL-Key 2/2
Mar 21 17:28:31.580089: WPA: Group rekeying completed with 00:0f:b5:57:2e:30 
[GTK=TKIP]
Mar 21 17:28:31.580107: State: GROUP_HANDSHAKE -> COMPLETED
Mar 21 17:28:32.579732: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:32.579770: IEEE 802.1X RX: version=1 type=3 length=127
Mar 21 17:28:32.579788:   EAPOL-Key type=254
Mar 21 17:28:32.579818: State: COMPLETED -> GROUP_HANDSHAKE
Mar 21 17:28:32.579833: WPA: RX message 1 of Group Key Handshake from 
00:0f:b5:57:2e:30 (ver=1)
Mar 21 17:28:32.579872: WPA: Group Key - hexdump(len=32): [REMOVED]
Mar 21 17:28:32.579888: WPA: Installing GTK to the driver (keyidx=1 tx=0).
Mar 21 17:28:32.579902: WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Mar 21 17:28:32.579951: WPA: Sending EAPOL-Key 2/2
Mar 21 17:28:32.580006: WPA: Group rekeying completed with 00:0f:b5:57:2e:30 
[GTK=TKIP]
Mar 21 17:28:32.580024: State: GROUP_HANDSHAKE -> COMPLETED
Mar 21 17:28:34.909991: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:34.910034: IEEE 802.1X RX: version=1 type=3 length=95
Mar 21 17:28:34.910052:   EAPOL-Key type=254
Mar 21 17:28:34.910068: WPA: EAPOL-Key Replay Counter did not increase - 
dropping packet
Mar 21 17:28:35.909730: RX EAPOL from 00:0f:b5:57:2e:30
Mar 21 17:28:35.909780: IEEE 802.1X RX: version=1 type=3 length=95
Mar 21 17:28:35.909797:   EAPOL-Key type=254
Mar 21 17:28:35.909853: WPA: EAPOL-Key Replay Counter did not increase - 
dropping packet
<snip>

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/




From gandalf_the_gray  Tue Mar 21 12:24:20 2006
From: gandalf_the_gray (FireStorm -)
Date: Tue, 21 Mar 2006 20:24:20 +0000
Subject: problem with hostap+ndiswrapper
Message-ID: <BAY107-F16EB641D227AB2CD7D761DDCD80@phx.gbl>

Clearly, the subject was supposed to be: "wpa_supplicant+ndiswrapper"

Sorry

Al

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




From ruzsinszky.attila  Tue Mar 21 12:25:58 2006
From: ruzsinszky.attila (Attila Ruzsinszky)
Date: Tue, 21 Mar 2006 21:25:58 +0100
Subject: supplicant under WinXP
Message-ID: <f637dd860603211225l53de1242l@mail.gmail.com>

Hi,

I'm a beginner in wpa_supplicant under M$ XP.

I configured a WPA Enterprise and I want to connect it.
(WPA+TKIP - Linksys WRT54GL OpenWRT RC4 +
FreeRADIUS under SuSE 9.0)
This config is working under Linux SuSE 9.3 with
wpa_supplicant but not under WinXP!

My cards are:
- Senao NL-2511CD Plus(E100)
- SMC WCB-G-EU
- Asus notebook with built-in Broadcom chip.

Seano (SuSE9.3) and SMC (SuSE10.0) is working.

My first question:
- Can I use those cards with WPA Enterprise because
Windows drivers aren't supported, max. WPA-PSK
(SMC) and WEP (Senao)?
- If the first answer is positive, then I've got a problem,
because I made a test under XP with Senao and I
wasn't able to connect:

Initializing interface
'\Device\NPF_{888D223C-4295-41F1-8B48-00EF7B147C74}' conf
'wpa_supplicant.conf' driver 'ndis' ctrl_interface 'N/A'
Configuration file 'wpa_supplicant.conf' ->
'D:\wpa_supplicant-windows-bin-0.4.8/wpa_supplicant.conf'
Reading configuration file
'D:\wpa_supplicant-windows-bin-0.4.8/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
opensc_engine_path='/usr/lib/opensc/engine_opensc.so'
pkcs11_engine_path='/usr/lib/opensc/engine_pkcs11.so'
pkcs11_module_path='/usr/lib/pkcs11/opensc-pkcs11.so'
Priority group 1
   id=0 ssid='mySSID'
Initializing interface (2) '\Device\NPF_{888D223C-4295-41F1-8B48-00EF7B147C74}'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3, 1, 0, 27
NDIS: 3 adapter names found
NDIS: 3 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericDialupAdapter - Generic dialup adapter
NDIS: 1 - \Device\NPF_{888D223C-4295-41F1-8B48-00EF7B147C74} - IEEE
802.11b WLAN network adaptor PC Card (Microsoft's Packet Scheduler)
NDIS: 2 - \Device\NPF_{D0BA227F-7E51-48D3-810E-497E928DD123} - SiS NIC
SISNIC (Microsoft's Packet Scheduler)
NDIS: Adapter description prefix 'IEEE 802.11b WLAN network adaptor PC Card'
ndis_get_oid: oid=0xd010122 len (512) failed
NDIS: verifying driver WPA capability
NDIS: WPA key management supported
NDIS: WPA-PSK key management supported
ndis_set_oid: oid=0xd01011b len (4) failed
NDIS: Failed to set OID_802_11_ENCRYPTION_STATUS (6)
NDIS: TKIP encryption supported
NDIS: driver supports WPA
NDIS: driver capabilities: key_mgmt 0x5 enc 0x4 auth 0x3
Own MAC address: 00:02:6f:33:xx:yy
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd010114 len (4) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_set_oid: oid=0xd010114 len (4) failed
Setting scan request: 0 sec 100000 usec
Added interface \Device\NPF_{888D223C-4295-41F1-8B48-00EF7B147C74}
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=11):
     xx xx xx xx xx xx xx xx xx xx                    mySSID
NDIS: turning radio on before the first scan
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 1
Selecting BSS from priority group 1
0: 00:02:6f:xx:xx:xx ssid='otherSSID' wpa_ie_len=0 rsn_ie_len=0 caps=0x0
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Starting AP scan (broadcast SSID)
...

Is this a config problem or driver or anything else?
mySSID is hidden...

TIA,
Ruzsi



From bryan  Tue Mar 21 14:41:27 2006
From: bryan (Bryan Kadzban)
Date: Tue, 21 Mar 2006 17:41:27 -0500
Subject: supplicant under WinXP
In-Reply-To: <f637dd860603211225l53de1242l@mail.gmail.com>
References: <f637dd860603211225l53de1242l@mail.gmail.com>
Message-ID: <44208117.3030308@kadzban.is-a-geek.net>

Attila Ruzsinszky wrote:
> My first question:
> - Can I use those cards with WPA Enterprise because
> Windows drivers aren't supported, max. WPA-PSK
> (SMC) and WEP (Senao)?

The SMC card should work (since the driver reports WPA-PSK capability,
it should be able to to TKIP encryption, and AFAIK wpa_supplicant
handles everything else).  But the Senao card might have issues if its
XP drivers only support WEP.

Your output says:

> Initializing interface
> '\Device\NPF_{888D223C-4295-41F1-8B48-00EF7B147C74}' conf
> 'wpa_supplicant.conf' driver 'ndis' ctrl_interface 'N/A'
> Configuration file 'wpa_supplicant.conf' ->
> 'D:\wpa_supplicant-windows-bin-0.4.8/wpa_supplicant.conf'
> Reading configuration file
> 'D:\wpa_supplicant-windows-bin-0.4.8/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> eapol_version=1
> ap_scan=1

But later, you say:

> mySSID is hidden...

If the SSID is hidden, then it might be worth looking through [1] for
the documentation for the ap_scan parameter.  The value 2 might be
helpful, depending on your driver, but read the linked docs, as there
are several other things you have to set.  (Search the page for the
string ap_scan.)

Also note that hiding your SSID provides only *very* minimal security;
as soon as the first person associates, the SSID is sent in cleartext
over the air by both the station and the AP anyway.  (It has to be,
otherwise the AP wouldn't be able to see which SSID the client wants to
associate with.)

[1]
http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/*checkout*/hostap/wpa_supplicant/wpa_supplicant.conf?rev=HEAD&content-type=text/plain
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060321/2d188ffd/attachment.pgp 


From joey  Tue Mar 21 14:40:06 2006
From: joey (Joey Richards)
Date: Tue, 21 Mar 2006 14:40:06 -0800
Subject: problem with hostap+ndiswrapper
In-Reply-To: <20060321202525.85431134294@mail.iocaine.com>
References: <20060321202525.85431134294@mail.iocaine.com>
Message-ID: <442080C6.6010806@caltech.edu>

Al,

I have the same problem (connection dropping due to "Key Replay Counter 
did not increase") with my broadcomm chipset and a Netgear WG614 access 
point.  No solution was found -- it was suggested to try to use a 3rd 
party (i.e., another PC with a wireless card) to try to observe the 
traffic and see what's going on.  I was not able to do this as I don't 
have access to another wireless card.

In my case, I have no trouble connecting using the same hardware under 
Windows, even with the Windows version of wpa_supplicant.  I've tried 
both the -Dndiswrapper and -Dwext options to wpa_supplicant under Linux. 
  Mine is a 2.6.something kernel.

joey


> Date: Tue, 21 Mar 2006 20:17:04 +0000
> From: "FireStorm -" <gandalf_the_gray at hotmail.com>
> Subject: problem with hostap+ndiswrapper
> To: hostap at shmoo.com
> Message-ID: <BAY107-F357A81A8AAC6E73A6A327FDCD80 at phx.gbl>
> Content-Type: text/plain; format=flowed
> 
> Hello list,
> 
> this is not a hostap related question, but it seems that the list is 
> appropriate anyway (I apologize in advance if it isn't).
> 
> Here it goes:
> I am trying to make my PCMCIA card work with WPA. Wpa_supplicant seems to 
> work fine, but after a few minutes the connection hangs and I am not able to 
> transfer anything, unless restarting the card and restarting wpa_supplicant 
> again.
> 
> Some info:
> - The card uses a Linksys INPROCOMM IPN 2220 chipset.
> - I use ndiswrapper version 2.7 to make it work with the neti2220.inf 
> driver.
> - The OS is a custom Devil-Linux with 2.4.32 kernel (with grsec).
> - Wpa_supplicant is version 0.4.8
> - The AP is a NetGear DG834GT
> 
> Here is the wpa_supplicant.conf file:
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=root
> network={
>         ssid="xxxx"
>         key_mgmt=WPA-PSK
>         proto=WPA
>         psk="yyyy"
> }
> 
> Looking through the wpa_supplicant log (pasted below), it seems that at 
> 17:28 the AP  starts  triggering GROUP_HANDSHAKE's. The first ones get 
> COMPLETE'd, but after a while the PC starts to complain that "Key Replay 
> Counter did not increase", dropping all subsequent packets. At that point, 
> no packet makes its way to/from the PC.
> 
> Another clue: when starting wpa_supplicant I get:
> ioctl[SIOCSIWPMKSA]: No such device
> ioctl[SIOCSIWENCODEEXT]: No such device
> ioctl[SIOCSIWENCODEEXT]: No such device
> ioctl[SIOCSIWENCODEEXT]: No such device
> ioctl[SIOCSIWENCODEEXT]: No such device
> 
> ...but as I said, for a few minuted the link is up and running
> 
> So... anybody has some clue about how to solve this ?
> 
> Thanks in advance
> 
> Al




From dcbw  Tue Mar 21 15:21:25 2006
From: dcbw (Dan Williams)
Date: Tue, 21 Mar 2006 18:21:25 -0500
Subject: [patch] Add eloop support for write & error socket callbacks
Message-ID: <1142983286.6106.2.camel@localhost.localdomain>

Patch attached, against current 0.4 HEAD.  Write and error callbacks are
needed for DBUS support, which I plan to add in the next month or so for
a DBUS-enabled control interface.

I'd rather have done one function for registering read, write, and error
callbacks and use an enum or something to figure out which type, but
that breaks source compatibility for the rest of the code and that
sucks.  This patch should work without changes to any part other than
eloop.

Dan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: eloop-write-error.patch
Type: text/x-patch
Size: 9518 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060321/44783127/attachment.bin 


From gandalf_the_gray  Tue Mar 21 15:32:41 2006
From: gandalf_the_gray (FireStorm -)
Date: Tue, 21 Mar 2006 23:32:41 +0000
Subject: problem with hostap+ndiswrapper
In-Reply-To: <442080C6.6010806@caltech.edu>
Message-ID: <BAY107-F183D344A65F794A9AD0268DCD80@phx.gbl>

Hello Joey,

>it was suggested to try to use a 3rd
>party (i.e., another PC with a wireless card)

I followed your advice and booted the laptop with Knoppix instead of 
Devil-Linux. The good news is that now wpa_supplicant works perfectly. The 
bad news is that now I have to figure out what's wrong with my Devil Linux 
build.

Two things I noticed so far:

1) there is no more "ioctl[SIOCSIWENCODEEXT]: No such device" repeated 4 
times when I launch wpa_supplicant, but only "ioctl[SIOCSIWPMKSA]: No such 
device" repeated once.

2) When issuing "wpa_cli status" now I get:

Selected interface 'wlan0'
bssid=xx:xx:xx:xx:xx:xx
ssid=<xxx>
pairwise_cipher=TKIP
group_cipher=TKIP
key_mgmt=WPA-PSK
wpa_state=COMPLETED
ip_address=10.0.69.73
Supplicant PAE state=AUTHENTICATED
suppPortStatus=Authorized
EAP state=SUCCESS

The weird things is that previously (in the non-working scenario) the last 3 
lines were missing. Something I messed configuring wpa_supplicant ? Some 
kernel support for EAP that was missing ? Any other possibility ?

Thanks

Al


> > Hello list,
> >
> > this is not a hostap related question, but it seems that the list is
> > appropriate anyway (I apologize in advance if it isn't).
> >
> > Here it goes:
> > I am trying to make my PCMCIA card work with WPA. Wpa_supplicant seems 
>to
> > work fine, but after a few minutes the connection hangs and I am not 
>able to
> > transfer anything, unless restarting the card and restarting 
>wpa_supplicant
> > again.
> >
> > Some info:
> > - The card uses a Linksys INPROCOMM IPN 2220 chipset.
> > - I use ndiswrapper version 2.7 to make it work with the neti2220.inf
> > driver.
> > - The OS is a custom Devil-Linux with 2.4.32 kernel (with grsec).
> > - Wpa_supplicant is version 0.4.8
> > - The AP is a NetGear DG834GT
> >
> > Here is the wpa_supplicant.conf file:
> >
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=root
> > network={
> >         ssid="xxxx"
> >         key_mgmt=WPA-PSK
> >         proto=WPA
> >         psk="yyyy"
> > }
> >
> > Looking through the wpa_supplicant log (pasted below), it seems that at
> > 17:28 the AP  starts  triggering GROUP_HANDSHAKE's. The first ones get
> > COMPLETE'd, but after a while the PC starts to complain that "Key Replay
> > Counter did not increase", dropping all subsequent packets. At that 
>point,
> > no packet makes its way to/from the PC.
> >
> > Another clue: when starting wpa_supplicant I get:
> > ioctl[SIOCSIWPMKSA]: No such device
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > ioctl[SIOCSIWENCODEEXT]: No such device
> > ioctl[SIOCSIWENCODEEXT]: No such device
> >
> > ...but as I said, for a few minuted the link is up and running
> >
> > So... anybody has some clue about how to solve this ?
> >
> > Thanks in advance
> >
> > Al
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/




From jpjiang  Tue Mar 21 17:45:30 2006
From: jpjiang (jianping jiang)
Date: Tue, 21 Mar 2006 17:45:30 -0800
Subject: EAP-FAST under Windows XP
Message-ID: <3e2dce660603211745r36df40b7peb14cfe8d33d2005@mail.gmail.com>

I am trying to use EAP-FAST under Windows XP SP2. I am using WPA-Supplicant
5.2. So far no luck. I am wondering if anyone has made it work under
Windows. And here is my configuration and output messages. I have changed
several parameters back and forth, but still not working. I'll appreciate if
you can point out any mistake. Thanks!

config file as follow:
+++++++++++++++++++++++++
eapol_version=1

ap_scan=1


# EAP-FAST with WPA (WPA or WPA2)
network={
    ssid="Voice"
    key_mgmt=WPA-EAP
    eap=FAST
    pairwise=TKIP
    anonymous_identity="anonymous"
    identity="user"
    password="password"
    phase1="fast_provisioning=1"
#    phase2="auth=MSCHAPV2"
    pac_file="C:/wpa_supplicanteap-fast.pac"
    #pac_file="blob://eap-fast-pac"
}

+++++++++++++++++++
Output :

C:\WPA-Supplicant\wpa_supplicant-windows-bin-0.5.2>.\wpa_supplicant.exe -i
ORiNO
CO -c EAP-FAST.conf -d
Initializing interface 'ORiNOCO' conf 'EAP-FAST.conf' driver 'default'
ctrl_inte
rface 'N/A' bridge 'N/A'
Reading configuration file 'EAP-FAST.conf'
eapol_version=2
ap_scan=1
Line 19: removed CCMP from group cipher list since it was not allowed for
pairwi
se cipher
Priority group 0
   id=0 ssid='Voice'
Initializing interface (2) 'ORiNOCO'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
NDIS: Packet.dll version: 3, 1, 0, 27
NDIS: 4 adapter names found
NDIS: 4 adapter descriptions found
NDIS: 0 - \Device\NPF_GenericDialupAdapter - Generic dialup adapter
NDIS: 1 - \Device\NPF_{3916E046-39B1-4861-8C57-BD59B4EAEA25} - ORiNOCO
802.11abg
 ComboCard Gold (Microsoft's Packet Scheduler)
NDIS: 2 - \Device\NPF_{E81584C8-9FF2-4088-9561-C06D101E14B9} - Dell Wireless
145
0 Dual Band WLAN Mini-PCI Card (Microsoft's Packet Scheduler)
NDIS: 3 - \Device\NPF_{47450170-B5B3-4E94-96C0-84459019AB71} - Broadcom
NetXtrem
e Gigabit Ethernet Driver (Microsoft's Packet Scheduler)
NDIS: Matched interface '\Device\NPF_{3916E046-39B1-4861-8C57-BD59B4EAEA25}'
bas
ed on description 'ORiNOCO 802.11abg ComboCard Gold (Microsoft's Packet
Schedule
r) '
NDIS: Adapter description prefix 'ORiNOCO 802.11abg ComboCard Gold'
ndis_get_oid: oid=0xd010122 len (512) failed
NDIS: verifying driver WPA capability
NDIS: WPA key management supported
NDIS: WPA-PSK key management supported
NDIS: CCMP encryption supported
NDIS: TKIP encryption supported
NDIS: driver supports WPA
NDIS: driver capabilities: key_mgmt 0x5 enc 0xc auth 0x3
Connected to ROOT\WMI.
Driver interface replaced interface name with
'\Device\NPF_{3916E046-39B1-4861-8
C57-BD59B4EAEA25}'
Own MAC address: 00:20:a6:51:59:43
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Setting scan request: 0 sec 100000 usec
Added interface \Device\NPF_{3916E046-39B1-4861-8C57-BD59B4EAEA25}
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to
speed
up initial association
Scan results: 0
Selecting BSS from priority group 0
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
NDIS: turning radio on before the first scan
ndis_get_oid: oid=0xd010101 len (6) failed
Scan timeout - try to get results
Scan results: 3
Selecting BSS from priority group 0
0: 00:13:10:bc:b6:d0 ssid='deco_designs' wpa_ie_len=24 rsn_ie_len=0
caps=0x10
   skip - SSID mismatch
1: 00:11:20:ee:70:5d ssid='WLAB-A' wpa_ie_len=24 rsn_ie_len=0 caps=0x10
   skip - SSID mismatch
2: 00:12:d9:c8:be:50 ssid='Voice' wpa_ie_len=26 rsn_ie_len=0 caps=0x10
   selected based on WPA IE
Trying to associate with 00:12:d9:c8:be:50 (SSID='Voice' freq=5220 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 1
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01
00
00 50 f2 02 01 00 00 50 f2 01 28 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50
f2
02 01 00 00 50 f2 02 01 00 00 50 f2 01
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
MSNdis_StatusMediaConnect
  InstanceName: 'ORiNOCO 802.11abg ComboCard Gold'
NDIS: event - type 0
NDIS: Media Connect Event
NDIS: ReqFixed=0x3 RespFixed=0x7 off_req=40 off_resp=140 len_req=100
len_resp=68

NDIS: 3 BSSID items to process for AssocInfo
Association info event
req_ies - hexdump(len=100): 00 05 56 6f 69 63 65 01 08 0c 12 18 24 30 48 60
6c d
d 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01 85 1e
00
00 66 00 00 00 00 00 18 00 00 00 00 00 08 60 a4 85 00 00 00 00 00 00 00 00
00 00
 00 00 95 0a 00 40 96 00 00 00 00 00 00 00 dd 06 00 40 96 01 01 00 dd 05 00
40 9
6 03 02
resp_ies - hexdump(len=68): 01 08 8c 12 98 24 b0 48 60 6c 85 1e 00 00 84 00
0f 0
0 ff 03 01 00 43 69 73 63 6f 31 00 c8 00 6f e3 4c 00 af dd 30 00 00 00 26 95
0a
00 40 96 00 0a 0a 0a 0a 01 00 dd 05 00 40 96 03 04 dd 05 00 40 96 0b 01
beacon_ies - hexdump(len=43): 00 05 56 6f 69 63 65 01 08 8c 12 98 24 b0 48
60 6c
 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01 28
00
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2
02 0
1 00 00 50 f2 02 01 00 00 50 f2 01
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01
00
00 50 f2 02 01 00 00 50 f2 01 28 00
WPA: clearing AP RSN IE
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:12:d9:c8:be:50
No keys have been configured - skip key clearing
Associated with 00:12:d9:c8:be:50
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:12:d9:c8:be:50
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 id=1 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=38):
     00 6e 65 74 77 6f 72 6b 69 64 3d 56 6f 69 63 65   _networkid=Voice
     2c 6e 61 73 69 64 3d 43 69 73 63 6f 31 2c 70 6f   ,nasid=Cisco1,po
     72 74 69 64 3d 30                                 rtid=0
EAP: using anonymous identity - hexdump_ascii(len=9):
     61 6e 6f 6e 79 6d 6f 75 73                        anonymous
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
RX EAPOL from 00:12:d9:c8:be:50
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=2 method=43 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method: vendor 0 method 43 (FAST)
EAP-FAST: Automatic PAC provisioning is allowed
EAP-FAST: Phase2 EAP types - hexdump(len=8): 00 00 00 00 1a 00 00 00
EAP-FAST: read 1 PAC entries from 'C:/wpa_supplicanteap-fast.pac'
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 43 (FAST) selected
EAP: EAP entering state METHOD
SSL: Received packet(len=26) - Flags 0x21
EAP-FAST: Start (server ver=1, own ver=1)
EAP-FAST: Using FAST version 1
EAP-FAST: A-ID - hexdump_ascii(len=16):
     4c 4f 43 41 4c 20 52 41 44 49 55 53 20 53 45 52   LOCAL RADIUS SER
EAP-FAST: PAC found for this A-ID
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: 240 bytes pending from ssl_out
SSL: 240 bytes left to be sent out (of total 240 bytes)
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:12:d9:c8:be:50
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=3 method=43 vendor=0 vendorMethod=0
EAP: EAP entering state METHOD
SSL: Received packet(len=594) - Flags 0x81
SSL: TLS Message Length: 584
EAP-FAST: client_random - hexdump(len=32): 44 20 ab 13 3c 51 4c b4 fd b5 86
7b d
e 88 31 9a f6 79 6d 03 22 c9 0c 5b e5 f1 1e 80 92 dc 10 9c
EAP-FAST: server_random - hexdump(len=32): d3 f8 78 7b 75 d3 f8 36 19 47 31
19 c
f 19 47 b6 0d 61 7f 64 bc 0d 61 70 59 5a 14 74 9f 59 5a bb
EAP-FAST: TLS pre-master-secret - hexdump(len=48): [REMOVED]
SSL: (where=0x4008 ret=0x22f)
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:illegal
parameter
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read server hello B
OpenSSL: tls_connection_handshake - SSL_connect error:14092105:SSL
routines:SSL3
_GET_SERVER_HELLO:wrong cipher returned
SSL: 7 bytes pending from ssl_out
SSL: Failed - tls_out available to report error
SSL: 7 bytes left to be sent out (of total 7 bytes)
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:12:d9:c8:be:50
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Failure
EAP: EAP entering state FAILURE
CTRL-EVENT-EAP-FAILURE EAP authentication failed
EAPOL: SUPP_PAE entering state HELD
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state FAIL
EAPOL: SUPP_BE entering state IDLE
CTRL-EVENT-TERMINATING - signal 0 received
Removing interface \Device\NPF_{3916E046-39B1-4861-8C57-BD59B4EAEA25}
State: ASSOCIATED -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_ndis_set_wpa: enabled=0
No keys have been configured - skip key clearing
ndis_set_oid: oid=0xd010115 len (4) failed
NDIS: failed to disassociate and turn radio off
EAP: deinitialize previously used EAP method (43, FAST) at EAP deinit
Cancelling scan request

C:\WPA-Supplicant\wpa_supplicant-windows-bin-0.5.2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060321/080d5182/attachment.htm 


From fjenkins873  Tue Mar 21 18:29:49 2006
From: fjenkins873 (frank jenkins)
Date: Wed, 22 Mar 2006 02:29:49 +0000
Subject: Can't connect to ap
Message-ID: <BAY113-F41C64AD1AF28372676FAEEBD90@phx.gbl>

I'm trying to connect a laptop with a DWL-650 (with primary firmware 1.0.7
and station firmware 1.8.4) to a wrt54g using rsn,wpa-psk, and ccmp. I'm
using the 2.6.15 kernel with hostap driver 0.4.4 and wireless tools v28.

wpa_supplicant can see the access point and tries to associate with it, but
for some reason that isn't obvious to me in the logs, it disassociates and
starts looking for another ap.

Here's the network block of my wpa_supplicant.conf
network={
  ssid="TestSsid"
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=CCMP
  group=CCMP
  psk="12345678"
  priority=1
}

I don't see any reason in the log for it to stop connecting, but then I've 
never used wpa_supplicant before. Can anyone tell me what I'm missing?

Here's (what I think is) the relevant part of the output from 
wpa_supplicant:

  0: 00:14:bf:ed:39:45 ssid='TestSsid' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
  selected based on RSN IE
  Trying to associate with 00:14:bf:ed:39:45 (SSID='TestSsid' freq=2452 MHz)
  Cancelling scan request
  WPA: clearing own WPA/RSN IE
  Automatic auth_alg selection: 0x1
  RSN: using IEEE 802.11i/D9.0
  WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
  WPA: clearing AP WPA IE
  WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f 
ac 04 01 00 00 0f ac 02 00 00
  WPA: using GTK CCMP
  WPA: using PTK CCMP
  WPA: using KEY_MGMT WPA-PSK
  WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 
00 00 0f ac 04 01 00 00 0f ac 02 00 00
  No keys have been configured - skip key clearing
  wpa_driver_hostap_set_drop_unencrypted: enabled=1
  State: SCANNING -> ASSOCIATING
  wpa_driver_hostap_associate
  Setting authentication timeout: 10 sec 0 usec
  EAPOL: External notification - EAP success=0
  EAPOL: External notification - EAP fail=0
  EAPOL: External notification - portControl=Auto
  RSN: Ignored PMKID candidate without preauth flag
  Wireless event: cmd=0x8b06 len=8
  Wireless event: cmd=0x8b04 len=12
  Wireless event: cmd=0x8b1a len=17
  Wireless event: cmd=0x8b15 len=20
  Wireless event: new AP: 00:14:bf:ed:39:45
  State: ASSOCIATING -> ASSOCIATED
  Associated to a new BSS: BSSID=00:14:bf:ed:39:45
  No keys have been configured - skip key clearing
  Associated with 00:14:bf:ed:39:45
  WPA: Association event - clear replay counter
  EAPOL: External notification - portEnabled=0
  EAPOL: External notification - portValid=0
  EAPOL: External notification - EAP success=0
  EAPOL: External notification - portEnabled=1
  EAPOL: SUPP_PAE entering state CONNECTING
  EAPOL: SUPP_BE entering state IDLE
  Setting authentication timeout: 10 sec 0 usec
  RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi1' added
  EAPOL: startWhen --> 0
  EAPOL: SUPP_PAE entering state CONNECTING
  EAPOL: txStart
  WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
  Wireless event: cmd=0x8b15 len=20
  Wireless event: new AP: 00:00:00:00:00:00
  Setting scan request: 0 sec 100000 usec
  Added BSSID 00:14:bf:ed:39:45 into blacklist
  Added BSSID 00:14:bf:ed:39:45 into blacklist
  State: ASSOCIATED -> DISCONNECTED
  EAPOL: External notification - portEnabled=0
  EAPOL: SUPP_PAE entering state DISCONNECTED
  EAPOL: SUPP_BE entering state INITIALIZE
  EAPOL: External notification - portValid=0
  EAPOL: External notification - EAP success=0
  CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
  wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
  wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0

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




From jkmaline  Tue Mar 21 19:16:06 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Mar 2006 19:16:06 -0800
Subject: [patch] Add eloop support for write & error socket callbacks
In-Reply-To: <1142983286.6106.2.camel@localhost.localdomain>
References: <1142983286.6106.2.camel@localhost.localdomain>
Message-ID: <20060322031606.GB9367@jm.kir.nu>

On Tue, Mar 21, 2006 at 06:21:25PM -0500, Dan Williams wrote:

> Patch attached, against current 0.4 HEAD.  Write and error callbacks are
> needed for DBUS support, which I plan to add in the next month or so for
> a DBUS-enabled control interface.

Thanks! The implementation itself looks fine, but I need to think about
the interface bit more closely from the view point of non-UNIX systems
that may not have select() or even BSD sockets.. The proposed changes
would make this interface very similar to select() features and that may
not be the best choice for this.

> I'd rather have done one function for registering read, write, and error
> callbacks and use an enum or something to figure out which type, but
> that breaks source compatibility for the rest of the code and that
> sucks.  This patch should work without changes to any part other than
> eloop.

Indeed.. I would not accept this if all places using eloop would need to
be changed. However, it should be possible to add a new function for
doing the registration as long as the existing API is implemented as a
wrapper on top of this new interface. This would allow new code to use
the new function while the old code would still work as-is.

Using a single function for this and maybe even changing the callback
functions to include an extra parameter, event type, could be a cleaner
solution for this. There would be only one eloop_sock_table and it would
have bitmask of which events (read/write/error) are registered to be
received.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 21 19:23:42 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Mar 2006 19:23:42 -0800
Subject: EAP-FAST under Windows XP
In-Reply-To: <3e2dce660603211745r36df40b7peb14cfe8d33d2005@mail.gmail.com>
References: <3e2dce660603211745r36df40b7peb14cfe8d33d2005@mail.gmail.com>
Message-ID: <20060322032342.GC9367@jm.kir.nu>

On Tue, Mar 21, 2006 at 05:45:30PM -0800, jianping jiang wrote:

> I am trying to use EAP-FAST under Windows XP SP2. I am using WPA-Supplicant
> 5.2. So far no luck. I am wondering if anyone has made it work under
> Windows. And here is my configuration and output messages. I have changed
> several parameters back and forth, but still not working. I'll appreciate if
> you can point out any mistake. Thanks!

I've tested EAP-FAST under WinXP, but not with this 0.5.2 version. It
looks like you have actually been able to complete provisioning step
since wpa_supplicant was able to read a PAC. Something is then going
wrong during the TLS handshake for normal authentication:

> EAP-FAST: A-ID - hexdump_ascii(len=16):
>      4c 4f 43 41 4c 20 52 41 44 49 55 53 20 53 45 52   LOCAL RADIUS SER
> EAP-FAST: PAC found for this A-ID

It looks like you are using the internal EAP-FAST authentication server
in an Cisco AP. Is that the case? Which Cisco model is this and which
firmware version are you using? I tested the local authentication server
long time ago, but have been mostly testing against Cisco ACS lately.

> EAP: Received EAP-Request id=3 method=43 vendor=0 vendorMethod=0
> EAP: EAP entering state METHOD
> SSL: Received packet(len=594) - Flags 0x81
> SSL: TLS Message Length: 584
> EAP-FAST: client_random - hexdump(len=32): 44 20 ab 13 3c 51 4c b4 fd b5 86
> 7b d
> e 88 31 9a f6 79 6d 03 22 c9 0c 5b e5 f1 1e 80 92 dc 10 9c
> EAP-FAST: server_random - hexdump(len=32): d3 f8 78 7b 75 d3 f8 36 19 47 31
> 19 c
> f 19 47 b6 0d 61 7f 64 bc 0d 61 70 59 5a 14 74 9f 59 5a bb
> EAP-FAST: TLS pre-master-secret - hexdump(len=48): [REMOVED]
> SSL: (where=0x4008 ret=0x22f)
> SSL: SSL3 alert: write (local SSL3 detected an error):fatal:illegal
> parameter
> SSL: (where=0x1002 ret=0xffffffff)
> SSL: SSL_connect:error in SSLv3 read server hello B
> OpenSSL: tls_connection_handshake - SSL_connect error:14092105:SSL
> routines:SSL3
> _GET_SERVER_HELLO:wrong cipher returned

Hmm.. OpenSSL did not like the TLS ServerHello. I don't remember seeing
this particular error before. Would it be possible for you to capture
these initial messages (ClientHello and this ServerHello) and send a
capture file for further analysis? This can be done either locally on
the client (e.g., with Ethereal) or with a wireless sniffer.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Tue Mar 21 19:26:52 2006
From: dcbw (Dan Williams)
Date: Tue, 21 Mar 2006 22:26:52 -0500
Subject: [patch] Add eloop support for write & error socket callbacks
In-Reply-To: <20060322031606.GB9367@jm.kir.nu>
References: <1142983286.6106.2.camel@localhost.localdomain>
	<20060322031606.GB9367@jm.kir.nu>
Message-ID: <1142998013.9060.3.camel@localhost.localdomain>

On Tue, 2006-03-21 at 19:16 -0800, Jouni Malinen wrote:
> On Tue, Mar 21, 2006 at 06:21:25PM -0500, Dan Williams wrote:
> 
> > Patch attached, against current 0.4 HEAD.  Write and error callbacks are
> > needed for DBUS support, which I plan to add in the next month or so for
> > a DBUS-enabled control interface.
> 
> Thanks! The implementation itself looks fine, but I need to think about
> the interface bit more closely from the view point of non-UNIX systems
> that may not have select() or even BSD sockets.. The proposed changes
> would make this interface very similar to select() features and that may
> not be the best choice for this.

DBus, at least, uses the socket and select model anyway, which fits in
nicely here.  What OSs don't have select, other than some random
real-time ones?  What does moving off select() actually gain?  In any
case, if we don't have read/write/error, we'll need to figure out some
way to kludge that in.

Underneath, dbus opens a UNIX domain socket to the dbus daemon, and the
user (in this case wpa_supplicant) needs to monitor that socket for
read/write/error states.  So if there's some other mechanism used rather
than select(), the dbus code would still have to use select in some
fashion to even think of working.  We'd end up essentially polling that
socket anyway.

> > I'd rather have done one function for registering read, write, and error
> > callbacks and use an enum or something to figure out which type, but
> > that breaks source compatibility for the rest of the code and that
> > sucks.  This patch should work without changes to any part other than
> > eloop.
> 
> Indeed.. I would not accept this if all places using eloop would need to
> be changed. However, it should be possible to add a new function for
> doing the registration as long as the existing API is implemented as a
> wrapper on top of this new interface. This would allow new code to use
> the new function while the old code would still work as-is.
> 
> Using a single function for this and maybe even changing the callback
> functions to include an extra parameter, event type, could be a cleaner
> solution for this. There would be only one eloop_sock_table and it would
> have bitmask of which events (read/write/error) are registered to be
> received.

Is this a prerequisite for accepting the patch?  Seems fairly easy, so
I'll try that.

Dan





From jkmaline  Tue Mar 21 19:31:44 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Mar 2006 19:31:44 -0800
Subject: help with IMXL
In-Reply-To: <20060314204250.M64005@microe.udea.edu.co>
References: <20060314204250.M64005@microe.udea.edu.co>
Message-ID: <20060322033144.GE9367@jm.kir.nu>

On Tue, Mar 14, 2006 at 03:48:12PM -0500, Juan Felipe Botero wrote:

> I could compile the hostap driver with the path of the linux kernel of my embedded
> system for a IMXL card based in a arm architecture.
> 
> when i compiled the kernel a folder called:
> /lib/modules/2.6.11.4-csb/kernel/drivers/net/wireless was created in my normal Linux
> system file, so i created and copied this folder in the linux file system of the
> embedded architecture, but when i started the Linux again, the driver didn't work. i can
> use the modprobe and it&#347; seems like there are no problems, but when i put in the command
> line - ifconfig wlan0 up - the answer was - no such device -. I

Which modules did you load? Can you please send 'dmesg' output from the
board after having loaded these modules?

> I really don't know about that problem, if someone has worked in a IMXL card please help me
> The compact flash card is a sinao NL-2511CF mercury, i know this card has a prism2 chipset

Have you used any CF cards successfully on this board? In other words,
is the Linux pcmcia subsystem working properly?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 21 19:54:51 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Mar 2006 19:54:51 -0800
Subject: [patch] Add eloop support for write & error socket callbacks
In-Reply-To: <1142998013.9060.3.camel@localhost.localdomain>
References: <1142983286.6106.2.camel@localhost.localdomain>
	<20060322031606.GB9367@jm.kir.nu>
	<1142998013.9060.3.camel@localhost.localdomain>
Message-ID: <20060322035451.GF9367@jm.kir.nu>

On Tue, Mar 21, 2006 at 10:26:52PM -0500, Dan Williams wrote:

> DBus, at least, uses the socket and select model anyway, which fits in
> nicely here.  What OSs don't have select, other than some random
> real-time ones?  What does moving off select() actually gain?  In any
> case, if we don't have read/write/error, we'll need to figure out some
> way to kludge that in.

Windows does not allow select() to be used for everything and
wpa_supplicant 0.5.x is using WaitForMultipleObjects() in eloop_win.c
because of this. WSAEventSelect() allows number of different event
types, including read and write, so I'm not too worried about this.
PalmOS is another examply I've seen and that was require quite a bit of
hacking on this front. In addition, we need to keep in mind that
wpa_supplicant is indeed being used on number of those "random real-time
ones"..

By the way, that "error" should probably be renamed to "exception". I
don't know what it is used for with dbus, but I would assume that this
could be used for other things than just errors.

> Underneath, dbus opens a UNIX domain socket to the dbus daemon, and the
> user (in this case wpa_supplicant) needs to monitor that socket for
> read/write/error states.  So if there's some other mechanism used rather
> than select(), the dbus code would still have to use select in some
> fashion to even think of working.  We'd end up essentially polling that
> socket anyway.

Yes, as far as dbus is concerned, this should be fine. I just try to
keep the eloop interface generic enough to handle most cases and this
means trying to avoid OS or single functionality based exceptions
whenever that is reasonable.

> > Indeed.. I would not accept this if all places using eloop would need to
> > be changed. However, it should be possible to add a new function for
> > doing the registration as long as the existing API is implemented as a
> > wrapper on top of this new interface. This would allow new code to use
> > the new function while the old code would still work as-is.
> > 
> > Using a single function for this and maybe even changing the callback
> > functions to include an extra parameter, event type, could be a cleaner
> > solution for this. There would be only one eloop_sock_table and it would
> > have bitmask of which events (read/write/error) are registered to be
> > received.
> 
> Is this a prerequisite for accepting the patch?  Seems fairly easy, so
> I'll try that.

I wouldn't say prerequisite, but this would be highly preferred. eloop
is used in number of programs and just like the driver wrapper API, this
is something that should not really be modified frequently. In other
words, if this patch went in, it would be more difficult to get rid of
the new functions any time soon.. Having a more generic way of
registering more than just three events may also end up being useful if
there is need to support something additional in the future. If this can
be added without having to introduce new functions, it would likely fit
in more nicely.

-- 
Jouni Malinen                                            PGP id EFC895FA



From pmanna  Tue Mar 21 23:19:08 2006
From: pmanna (Prasenjit Manna)
Date: Wed, 22 Mar 2006 12:49:08 +0530
Subject: Need Multi-Auth Information
Message-ID: <4420FA6C.1060206@netd.com>

Hi,

I want to know some informations regarding How multi-auth works in wired 
setup.
1. What is the destination address of EAPOL packet? Is this unicast or 
group address?
    In single-host mode, Authenticator sends EAPOL-Request/Identity 
packets to wire.
    The same this is applicable here for multi-auth mode? If it is like 
this, then what will be the destination
    address of the first packets from authenticator?


Thanks in advance,
Prasenjit



From bryan  Wed Mar 22 04:06:43 2006
From: bryan (Bryan Kadzban)
Date: Wed, 22 Mar 2006 07:06:43 -0500
Subject: supplicant under WinXP
In-Reply-To: <f637dd860603220145j6ec6c62bu@mail.gmail.com>
References: <f637dd860603211225l53de1242l@mail.gmail.com>	
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
Message-ID: <44213DD3.2090404@kadzban.is-a-geek.net>

(I'm assuming you meant to copy the list on your last message...)

Attila Ruzsinszky wrote:
>> The SMC card should work (since the driver reports WPA-PSK
>> capability, it should be able to to TKIP encryption, and AFAIK
>> wpa_supplicant handles everything else).  But the Senao card might
>> have issues if its XP drivers only support WEP.
> 
> It is very interesting, because SMC network program knows only WEP 
> and WPA-PSK. But it is a good news in your opinion it will work!

Well, wait...  If you're talking about the supplicant programs that came
with the drivers, then that's not an "upper" bound on the encryption and
authentication protocols that the card can support.  The Senao card, for
instance:  if the program that came with it only has an option for WEP,
that doesn't mean that the card's firmware can't do TKIP, just that the
program that they provided can't do the 4-way handshake.  (Or that the
driver isn't advertising that capability.)

To find out for sure what capabilities the driver is giving Windows (and
therefore what encryptions it's capable of under wpa_supplicant), try
firing up the XP supplicant and adding a preferred network "manually".
Look at the options under authentication; if WPA and WPA-PSK are there,
then the card's driver is advertising support for them.  If only "open"
and "shared" are there, then the driver is only advertising WEP.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060322/57bc024e/attachment.pgp 


From ruzsinszky.attila  Wed Mar 22 09:53:49 2006
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Wed, 22 Mar 2006 18:53:49 +0100
Subject: supplicant under WinXP
In-Reply-To: <44213DD3.2090404@kadzban.is-a-geek.net>
References: <f637dd860603211225l53de1242l@mail.gmail.com>	
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net>
Message-ID: <44218F2D.2050703@gmail.hu>

Hi,

Bryan Kadzban ?rta:
> (I'm assuming you meant to copy the list on your last message...)
I think my messages remained private. :-(
I pushed the reply button and now I can see no more e-mail address
except yours.
Do I have to explicite address the list?

>>> The SMC card should work (since the driver reports WPA-PSK
>>> capability, it should be able to to TKIP encryption, and AFAIK
>>> wpa_supplicant handles everything else).  But the Senao card might
>>> have issues if its XP drivers only support WEP.
>> It is very interesting, because SMC network program knows only WEP 
>> and WPA-PSK. But it is a good news in your opinion it will work!
> 
> Well, wait...  If you're talking about the supplicant programs that came
No!
I talked about M$ drivers not about wpa_supplicant.

> with the drivers, then that's not an "upper" bound on the encryption and
> authentication protocols that the card can support.  The Senao card, for
> instance:  if the program that came with it only has an option for WEP,
> that doesn't mean that the card's firmware can't do TKIP, just that the
> program that they provided can't do the 4-way handshake.  (Or that the
> driver isn't advertising that capability.)
It is very interesting!
I'm confused now. :-(
The card is same:
- under Linux, with wpa_supplicant, I can connect my AP with WPA TKIP
TLS. So the card is support it. (I upgraded its firmware as I read on
the Net.)
- under M$ XP SP1 it doesn't work neither its driver or wpa_supplicant.

> To find out for sure what capabilities the driver is giving Windows (and
> therefore what encryptions it's capable of under wpa_supplicant), try
> firing up the XP supplicant and adding a preferred network "manually".
> Look at the options under authentication; if WPA and WPA-PSK are there,
> then the card's driver is advertising support for them.  If only "open"
> and "shared" are there, then the driver is only advertising WEP.
This is the situation. :-( No WPA!

I understand where is the problem then. Linux is working, XP not. Card
is the same. So the problematic part is the driver which was supplied
by card?

Back to your advice for SMC card...
It is working! ;-) Both under Linux and XP SP1! Nice.

Only problem, with my hidden SSID doesn't work.
I tried out ap_scan=0,1,2 parameters. Only ap_scan=1 is good for me,
and unhidden SSID! Is this correct?

And here is some other error notices:
D:\wpa_supplicant-windows-bin-0.4.8>wpa_supplicant -i 
\Device\NPF_{C8940014-8714
-4DD0-A851-560BCCAD89C6} -c wpa_supplicant.conf
Trying to associate with 00:14:bf:xx:xx:x (SSID='mySSID' freq=2xxx MHz)
Associated with 00:14:bf:xx:xx:x
CTRL-EVENT-EAP-STARTED EAP authentication started
OpenSSL: pending error: error:0D07803A:asn1 encoding 
routines:ASN1_ITEM_EX_D2I:n
ested asn1 error
OpenSSL: pending error: error:140C800D:SSL 
routines:SSL_use_certificate_file:ASN
1 lib
OpenSSL: pending error: error:0D0680A8:asn1 encoding 
routines:ASN1_CHECK_TLEN:wr
ong tag
OpenSSL: pending error: error:0D07803A:asn1 encoding 
routines:ASN1_ITEM_EX_D2I:n
ested asn1 error
OpenSSL: pending error: error:0D09A00D:asn1 encoding 
routines:d2i_PrivateKey:ASN
1 lib
OpenSSL: pending error: error:140CB00D:SSL 
routines:SSL_use_PrivateKey_file:ASN1
  lib
CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:14:bf:xx:xx:xx [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:14:bf:xx:xx:xx completed (auth)

TIA,
Ruzsi

Ps: Do you know PCMCIA card which is working perfectly under
SuSE >=9.0 and at least M$ XP?




From pgf  Wed Mar 22 14:29:19 2006
From: pgf (Paul Fox)
Date: Wed, 22 Mar 2006 17:29:19 -0500
Subject: wap54g "basic rates" setting, and prism hostap driver
Message-ID: <4449.1143066559@brightstareng.com>

hi -- 

i don't know that anything is actually wrong, but i'm seeing something
odd.

i have a Linksys WAP54G (firmware 3.01), an NL-2511CD prism
pcmcia card (firmware 1.8.4), and hostap drivers (either 0.3.9 or
0.4.7, same results).  i'm using WPA, but don't know that that
matters.

the WAP54G has a setting for "Basic Rates", which can
have the values "ALL", "1-2 Mbps", and "Default".  if
i select either "1-2 Mbps" or "Default", all is well.  if
i select "ALL", i can no longer associate.  the Linksys
docs are as follows:

    Basic Rates.  This setting is not actually one rate of
    transmission but a series of rates that are advertised to the
    other wireless devices in your network, so they know at which
    rates the Access Point can transmit.  At the Default setting,
    the Access Point will advertise that it will automatically
    select the best rate for transmission.  Other options are
    1-2Mbps, for use with older wireless technology, and All,
    when you wish to have all rates advertised.  The Basic Data
    Rates are not the rates transmitted; the rates transmitted
    can be configured through the Transmission Rates setting on
    this screen.

why would the explicit advertisement of rates affect association?
is there a requirement that a client support all advertised rates?

the more i think about this, the more i think that my observed
behavior may be expected -- the AP is probably advertising
rates up through 54, and the card doesn't like them all, so it
doesn't associate.  or something like that.  but if that's the
case, i'm wondering what the possible use of this particular
negotiation is -- why wouldn't the AP and card just agree to the
mutually supported subset of rates, rather than an all-or-nothing
behavior.

can anyone shed light?

paul
=---------------------
 paul fox, pgf at brightstareng.com



From pelusitavali  Wed Mar 22 18:26:36 2006
From: pelusitavali (Pelusa Vali)
Date: Thu, 23 Mar 2006 02:26:36 +0000
Subject: clients cann't connect when using hostapd
Message-ID: <PM.7065.1143080796@pmweb6.uk1.bibliotech.net>

hi list, could any body try to help please?? i have this problem since many time ago, and this is my problem:
i can compile hostapd, but when type make install nothing happens, so copied hostapd.conf file in /etc/hostapd (i created this directory ), this is my .config file to compile:
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I/usr/src/madwifi/
CONFIG_IAPP=y
CONFIG_RSN_PREAUTH=y
CONFIG_EAP=y
CONFIG_EAP_MD5=y
CONFIG_EAP_TLS=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_TTLS=y
CONFIG_PKCS12=y
CONFIG_IPV6=y
 
this is my hostapd.conf file:

interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=1
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=MYWLAN
macaddr_acl=0
auth_algs=1
wpa=1
wpa_passphrase=serveraccess
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP

so i can use hostapd with this: hostapd -dd /etc/hostadp/hostapd.conf
 
buy my clients never can connect with my ap (by the way i use debian etch, kernel 2.6.15.6, madwifi-ng-r1475, hostapd-0.5.1), i mean they try, but never can connect successfully, never can get ip direction from dhcp nor nothing else, this is what hostapd shows when trying to connect a client:

WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake
ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 02 c4 38 a2 52 0a 22 e3 d1 3d f4 34 de 05 83 87 b4 0a bf 1e e9 1e fb b5 b8 0a 90 80 5d 27 54 fe 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake
ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 03 c4 38 a2 52 0a 22 e3 d1 3d f4 34 de 05 83 87 b4 0a bf 1e e9 1e fb b5 b8 0a 90 80 5d 27 54 fe 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake
ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 04 c4 38 a2 52 0a 22 e3 d1 3d f4 34 de 05 83 87 b4 0a bf 1e e9 1e fb b5 b8 0a 90 80 5d 27 54 fe 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:0f:66:11:c1:96 reason 2
madwifi_sta_deauth: addr=00:0f:66:11:c1:96 reason_code=2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state DISCONNECTED
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ioctl[unknown???]: Invalid argument
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=0
ioctl[unknown???]: Invalid argument
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: deauthenticated due to local deauth request
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:66:11:c1:96 IEEE 802.11: associated
  New STA
ath0: STA 00:0f:66:11:c1:96 WPA: event 1 notification
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 WPA: start authentication
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0f:66:11:c1:96 key_idx=0
ath0: STA 00:0f:66:11:c1:96 IEEE 802.1X: unauthorizing port
madwifi_set_sta_authorized: addr=00:0f:66:11:c1:96 authorized=0
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state IDLE
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state AUTHENTICATION
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITPSK
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 c4 38 a2 52 0a 22 e3 d1 3d f4 34 de 05 83 87 b4 0a bf 1e e9 1e fb b5 b8 0a 90 80 5d 27 54 fe 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter
expected replay counter - hexdump(len=8): 00 00 00 00 00 00 00 01
received replay counter - hexdump(len=8): 00 00 00 00 00 00 00 04
IEEE 802.1X: 5 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=1 length=0
   ignoring 1 extra octets after IEEE 802.1X packet
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake
ath0: STA 00:0f:66:11:c1:96 WPA: EAPOL-Key timeout
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 02 c4 38 a2 52 0a 22 e3 d1 3d f4 34 de 05 83 87 b4 0a bf 1e e9 1e fb b5 b8 0a 90 80 5d 27 54 fe 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 125 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake

i want first wpa-psk just for testing purposes, to see if madwifi and hostapd can really talk each other. and as you can see, it's impossible, i guess is some error with my system or maybe with debian??

so, could you try to guess what is wrong and if is possible to solve it in some way??

thanks.


_______________________________________________________________ 
Which planet radiates more energy than it receives from the sun?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=190




From mistamaila  Wed Mar 22 18:47:04 2006
From: mistamaila (John H.)
Date: Wed, 22 Mar 2006 20:47:04 -0600
Subject: -Dwext problems with zydas driver and wpa-psk -
	ioctl[SIOCSIWPMKSA]: Invalid argument,
	Could not configure driver to use managed mode,
	Association request to the driver failed
In-Reply-To: <20060320141230.GA9370@jm.kir.nu>
References: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
	<20060320141230.GA9370@jm.kir.nu>
Message-ID: <5b9417770603221847q12ba9265r9259d25b15dc204e@mail.gmail.com>

did you get my reply?  it would not let me send it to the mailing list
because it said it was too large.  i sent the debug info.
thx

On 3/20/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Mon, Mar 20, 2006 at 01:31:05AM -0600, John H. wrote:
>
> > I don't know what's wrong, it's just not working anymore, but same
> > router works in XP.  Currently using .67 of zd1211 driver and
> > wpa_supplicant .4.8, but get same results from .5.2.
>
> >  /usr/src/wpasupplicant/wpa_supplicant -w -i wlan0 -c
> > /etc/wpa_supplicant.conf -Dwext
>
> Please send more verbose debug log (i.e., add -dd to the command line).
>
> > WPA: Key negotiation completed with 00:90:4b:36:b8:66 [PTK=TKIP GTK=TKIP]
> > CTRL-EVENT-CONNECTED - Connection to 00:90:4b:36:b8:66 completed (auth)
>
> At least the initial connection worked fine, so the basic functionality
> seems to be available.
>
> > WPA: EAPOL-Key Replay Counter did not increase - dropping packet
>
> This is most commonly triggered if the driver does not report
> disconnection to the supplicant. More verbose debug could help in
> figuring out whether that is the case, but one may need to take a look
> at wireless capture log of the frames sent at this point to figure out
> what exactly happened unless the driver provides useful debug
> information about associations.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>



From jkmaline  Wed Mar 22 19:05:53 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Mar 2006 19:05:53 -0800
Subject: wap54g "basic rates" setting, and prism hostap driver
In-Reply-To: <4449.1143066559@brightstareng.com>
References: <4449.1143066559@brightstareng.com>
Message-ID: <20060323030553.GA9370@jm.kir.nu>

On Wed, Mar 22, 2006 at 05:29:19PM -0500, Paul Fox wrote:

> i have a Linksys WAP54G (firmware 3.01), an NL-2511CD prism
> pcmcia card (firmware 1.8.4), and hostap drivers (either 0.3.9 or
> 0.4.7, same results).  i'm using WPA, but don't know that that
> matters.

> the WAP54G has a setting for "Basic Rates", which can
> have the values "ALL", "1-2 Mbps", and "Default".  if
> i select either "1-2 Mbps" or "Default", all is well.  if
> i select "ALL", i can no longer associate.

If that "ALL" includes 802.11g rates, setting basic rates to that will
prevent all 802.11b stations from associating with the AP.

>     Basic Rates.  This setting is not actually one rate of
>     transmission but a series of rates that are advertised to the
>     other wireless devices in your network, so they know at which
>     rates the Access Point can transmit.  At the Default setting,
>     the Access Point will advertise that it will automatically
>     select the best rate for transmission.  Other options are
>     1-2Mbps, for use with older wireless technology, and All,
>     when you wish to have all rates advertised.  The Basic Data
>     Rates are not the rates transmitted; the rates transmitted
>     can be configured through the Transmission Rates setting on
>     this screen.

This is confusing at best..  Basic rate sets are the rates that will be
used for special uses like broadcast (to be visible for all STAs) and
ACKs. There is another rate set, "Supported Rates", that would be much
closer to this description.

> why would the explicit advertisement of rates affect association?
> is there a requirement that a client support all advertised rates?

Yes, that is indeed exactly what is required for Basic Rates. Supported
Rates does not have such requirement.

> the more i think about this, the more i think that my observed
> behavior may be expected -- the AP is probably advertising
> rates up through 54, and the card doesn't like them all, so it
> doesn't associate.  or something like that.  but if that's the
> case, i'm wondering what the possible use of this particular
> negotiation is -- why wouldn't the AP and card just agree to the
> mutually supported subset of rates, rather than an all-or-nothing
> behavior.

Your 802.11b station is likely trying to associate, but the AP is
rejecting this since the station does not support all required options.
Usually 802.11g APs are configured to only include 802.11b rates as
basic rates to allow backwards compatibility. All 802.11g rates can be
in the supported rate set so that 802.11g stations can use them for
unicast frames. Including 802.11g rates in basic rate set may improve
multicast performance, so there may be valid use cases for that, too,
but at the cost of dropping backwards compatibility.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 22 20:12:09 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Mar 2006 20:12:09 -0800
Subject: clients cann't connect when using hostapd
In-Reply-To: <PM.7065.1143080796@pmweb6.uk1.bibliotech.net>
References: <PM.7065.1143080796@pmweb6.uk1.bibliotech.net>
Message-ID: <20060323041209.GC10303@jm.kir.nu>

On Thu, Mar 23, 2006 at 02:26:36AM +0000, Pelusa Vali wrote:

> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP CCMP

I would suggest starting with only one pairwise cipher configured. There
have been some problems with enabling both of them in some
configurations. It'll be easier to test this once the simplest case has
been known to work.

> buy my clients never can connect with my ap (by the way i use debian etch, kernel 2.6.15.6, madwifi-ng-r1475, hostapd-0.5.1), i mean they try, but never can connect successfully, never can get ip direction from dhcp nor nothing else, this is what hostapd shows when trying to connect a client:

What clients are you using (operating system, wlan hardware, driver,
supplicant, version numbers)?

> ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake

This is normally a sign of either incorrectly configured WPA
PSK/passphrase or an implementation error. Are you sure that the same
passphrase is configured in both the AP and client?


PS.

hostapd v0.5.1 has a bug that would break the next msg 3/4, so even if
you get through this msg 2/4, you should really upgrade to 0.5.2 in
order to be able to complete authentication successfully.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 22 20:15:28 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Mar 2006 20:15:28 -0800
Subject: Need Multi-Auth Information
In-Reply-To: <4420FA6C.1060206@netd.com>
References: <4420FA6C.1060206@netd.com>
Message-ID: <20060323041528.GD10303@jm.kir.nu>

On Wed, Mar 22, 2006 at 12:49:08PM +0530, Prasenjit Manna wrote:

> I want to know some informations regarding How multi-auth works in wired 
> setup.
> 1. What is the destination address of EAPOL packet? Is this unicast or 
> group address?

IEEE 802.1X requires that the PAE group address (01:80:c2:00:00:03) is
used as the destination address in wired Ethernet networks.

>     In single-host mode, Authenticator sends EAPOL-Request/Identity 
> packets to wire.
>     The same this is applicable here for multi-auth mode? If it is like 
> this, then what will be the destination
>     address of the first packets from authenticator?

All EAPOL frames will be sent to the same group address, so this
requires that there are separate ports (e.g., switch ports) that the
authenticator can use for each supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 22 20:20:57 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Mar 2006 20:20:57 -0800
Subject: supplicant under WinXP
In-Reply-To: <44218F2D.2050703@gmail.hu>
References: <f637dd860603211225l53de1242l@mail.gmail.com>
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net>
	<44218F2D.2050703@gmail.hu>
Message-ID: <20060323042057.GE10303@jm.kir.nu>

On Wed, Mar 22, 2006 at 06:53:49PM +0100, Ruzsinszky Attila wrote:

> The card is same:
> - under Linux, with wpa_supplicant, I can connect my AP with WPA TKIP
> TLS. So the card is support it. (I upgraded its firmware as I read on
> the Net.)
> - under M$ XP SP1 it doesn't work neither its driver or wpa_supplicant.

wpa_supplicant would support WPA on both Linux and Windows XP, but it
sounds like the Windows driver you are using does not support WPA.

> Only problem, with my hidden SSID doesn't work.
> I tried out ap_scan=0,1,2 parameters. Only ap_scan=1 is good for me,
> and unhidden SSID! Is this correct?

ap_scan=2 should work fine with Windows NDIS drivers. I haven't seen any
NDIS driver that would not work with it.. Did you configure all
parameters that ap_scan comments in wpa_supplicant.conf mention? Please
send your configuration file if you cannot get this working.

> Ps: Do you know PCMCIA card which is working perfectly under
> SuSE >=9.0 and at least M$ XP?

I'm not aware of any card that works _perfectly_ ;-). I've used
Prism2/2.5/3-based PC Cards successfully with both Windows and Linux.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 22 20:26:03 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Mar 2006 20:26:03 -0800
Subject: -Dwext problems with zydas driver and wpa-psk -
	ioctl[SIOCSIWPMKSA]: Invalid argument,
	Could not configure driver to use managed mode,
	Association request to the driver failed
In-Reply-To: <5b9417770603221847q12ba9265r9259d25b15dc204e@mail.gmail.com>
References: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
	<20060320141230.GA9370@jm.kir.nu>
	<5b9417770603221847q12ba9265r9259d25b15dc204e@mail.gmail.com>
Message-ID: <20060323042603.GF10303@jm.kir.nu>

On Wed, Mar 22, 2006 at 08:47:04PM -0600, John H. wrote:

> did you get my reply?  it would not let me send it to the mailing list
> because it said it was too large.  i sent the debug info.

Yes, I did receive it. However..

> > On Mon, Mar 20, 2006 at 01:31:05AM -0600, John H. wrote:
> > > WPA: EAPOL-Key Replay Counter did not increase - dropping packet

That message did not show up at all in the debug log.. There were number
of successful associations and WPA handshakes, but each one seemed to be
followed by disconnection event. Either the AP was disconnecting the
client or the driver was reporting disconnection for some reason.

wpa_supplicant debug log does not provide enough information to
determine what is happening here, so one would either need to get debug
information from the driver or the AP. In addition, it would be useful
to see a wireless capture log of frames sent between the client and the
AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mistamaila  Wed Mar 22 21:26:21 2006
From: mistamaila (John H.)
Date: Wed, 22 Mar 2006 23:26:21 -0600
Subject: -Dwext problems with zydas driver and wpa-psk -
	ioctl[SIOCSIWPMKSA]: Invalid argument,
	Could not configure driver to use managed mode,
	Association request to the driver failed
In-Reply-To: <20060323042603.GF10303@jm.kir.nu>
References: <5b9417770603192331w156ad61qca7a3698c5508fab@mail.gmail.com>
	<20060320141230.GA9370@jm.kir.nu>
	<5b9417770603221847q12ba9265r9259d25b15dc204e@mail.gmail.com>
	<20060323042603.GF10303@jm.kir.nu>
Message-ID: <5b9417770603222126q8698c47kb392ffe1d278a954@mail.gmail.com>

so is it likely the zd1211 driver that is at fault?  if so, zd1211
list, how would i provide such info that he would need?

On 3/22/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Wed, Mar 22, 2006 at 08:47:04PM -0600, John H. wrote:
>
> > did you get my reply?  it would not let me send it to the mailing list
> > because it said it was too large.  i sent the debug info.
>
> Yes, I did receive it. However..
>
> > > On Mon, Mar 20, 2006 at 01:31:05AM -0600, John H. wrote:
> > > > WPA: EAPOL-Key Replay Counter did not increase - dropping packet
>
> That message did not show up at all in the debug log.. There were number
> of successful associations and WPA handshakes, but each one seemed to be
> followed by disconnection event. Either the AP was disconnecting the
> client or the driver was reporting disconnection for some reason.
>
> wpa_supplicant debug log does not provide enough information to
> determine what is happening here, so one would either need to get debug
> information from the driver or the AP. In addition, it would be useful
> to see a wireless capture log of frames sent between the client and the
> AP.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>



From pmanna  Wed Mar 22 22:04:01 2006
From: pmanna (Prasenjit Manna)
Date: Thu, 23 Mar 2006 11:34:01 +0530
Subject: Need Multi-Auth Information
In-Reply-To: <20060323041528.GD10303@jm.kir.nu>
References: <4420FA6C.1060206@netd.com> <20060323041528.GD10303@jm.kir.nu>
Message-ID: <44223A51.3080902@netd.com>

Jouni Malinen wrote:

>On Wed, Mar 22, 2006 at 12:49:08PM +0530, Prasenjit Manna wrote:
>
>  
>
>>I want to know some informations regarding How multi-auth works in wired 
>>setup.
>>1. What is the destination address of EAPOL packet? Is this unicast or 
>>group address?
>>    
>>
>
>IEEE 802.1X requires that the PAE group address (01:80:c2:00:00:03) is
>used as the destination address in wired Ethernet networks.
>  
>
I think this is for single-host or multi-host mode. But multi-auth mode, 
except the first packet from
either of the side(supplicant or authenticator),  all the other 
communication should be unicast.

>  
>
>>    In single-host mode, Authenticator sends EAPOL-Request/Identity 
>>packets to wire.
>>    The same this is applicable here for multi-auth mode? If it is like 
>>this, then what will be the destination
>>    address of the first packets from authenticator?
>>    
>>
>
>All EAPOL frames will be sent to the same group address, so this
>requires that there are separate ports (e.g., switch ports) that the
>authenticator can use for each supplicant.
>  
>
I am assuming a scenario, where one switchport and multiple clients are 
connected through a hub.
Whoever(client) has authenticator, they will get the access to the 
switchport. This is I am talking about
multi-auth mode.




From joey  Wed Mar 22 22:59:30 2006
From: joey (Joey Richards)
Date: Wed, 22 Mar 2006 22:59:30 -0800
Subject: problem with hostap+ndiswrapper
In-Reply-To: <20060321234121.188CE5642F5@mail.iocaine.com>
References: <20060321234121.188CE5642F5@mail.iocaine.com>
Message-ID: <44224752.1060305@caltech.edu>

Al,

That's interesting.  Please let us know if you figure out what the 
difference is.  I'm using Gentoo with a 2.6.15-r1 kernel and having no luck.

Also, if you do have access to another machine that can sniff all the 
wireless traffic, please let us know.  This is actually what I meant by 
my suggestion.  Jouni thought that getting a complete record of the 
packets exchanged between the AP and the client could help determine 
what's going wrong.  The hypothesis was that some sort of event was not 
making its way between the driver and wpa_supplicant.

What are the versions of various things (ndiswrapper, wpa_supplicant, 
kernel) under the working Knoppix configuration?  Are they the same as 
for your Devil-Linux configuration?

Thanks, and glad to hear you made some progress,
joey


> Date: Tue, 21 Mar 2006 23:32:41 +0000
> From: "FireStorm -" <gandalf_the_gray at hotmail.com>
> Subject: Re: problem with hostap+ndiswrapper
> To: hostap at shmoo.com
> Message-ID: <BAY107-F183D344A65F794A9AD0268DCD80 at phx.gbl>
> Content-Type: text/plain; format=flowed
> 
> Hello Joey,
> 
>> >it was suggested to try to use a 3rd
>> >party (i.e., another PC with a wireless card)
> 
> I followed your advice and booted the laptop with Knoppix instead of 
> Devil-Linux. The good news is that now wpa_supplicant works perfectly. The 
> bad news is that now I have to figure out what's wrong with my Devil Linux 
> build.
> 
> Two things I noticed so far:
> 
> 1) there is no more "ioctl[SIOCSIWENCODEEXT]: No such device" repeated 4 
> times when I launch wpa_supplicant, but only "ioctl[SIOCSIWPMKSA]: No such 
> device" repeated once.
> 
> 2) When issuing "wpa_cli status" now I get:
> 
> Selected interface 'wlan0'
> bssid=xx:xx:xx:xx:xx:xx
> ssid=<xxx>
> pairwise_cipher=TKIP
> group_cipher=TKIP
> key_mgmt=WPA-PSK
> wpa_state=COMPLETED
> ip_address=10.0.69.73
> Supplicant PAE state=AUTHENTICATED
> suppPortStatus=Authorized
> EAP state=SUCCESS
> 
> The weird things is that previously (in the non-working scenario) the last 3 
> lines were missing. Something I messed configuring wpa_supplicant ? Some 
> kernel support for EAP that was missing ? Any other possibility ?
> 
> Thanks
> 
> Al
> 
> 
>>> > > 





From pelusitavali  Thu Mar 23 07:33:21 2006
From: pelusitavali (Pelusa Vali)
Date: Thu, 23 Mar 2006 15:33:21 +0000
Subject: clients cann't connect when using hostapd
Message-ID: <PM.28008.1143128001@pmweb6.uk1.bibliotech.net>

>> wpa_key_mgmt=WPA-PSK
>> wpa_pairwise=TKIP CCMP
>
>I would suggest starting with only one pairwise cipher configured. There
>have been some problems with enabling both of them in some
>configurations. It'll be easier to test this once the simplest case has
>been known to work.
>
>> buy my clients never can connect with my ap (by the way i use debian etch, kernel 2.6.15.6, madwifi-ng-r1475, hostapd-0.5.1), i mean they try, but never can connect successfully, never can get ip direction from dhcp nor nothing else, this is what hostapd shows when trying to connect a client:
>
>What clients are you using (operating system, wlan hardware, driver,
>supplicant, version numbers)?
>
>> ath0: STA 00:0f:66:11:c1:96 WPA: invalid MIC in msg 2/4 of 4-Way Handshake
>
>This is normally a sign of either incorrectly configured WPA
>PSK/passphrase or an implementation error. Are you sure that the same
>passphrase is configured in both the AP and client?
>
>
>PS.
>
>hostapd v0.5.1 has a bug that would break the next msg 3/4, so even if
>you get through this msg 2/4, you should really upgrade to 0.5.2 in
>order to be able to complete authentication successfully.
>
>-- 
>Jouni Malinen                                            PGP id EFC895FA


Thanks so much Jouni, you are my idol now, i was testing my configuration by 1 year and never worked, now with last revision of hostapd, simply works!!!.
thanks for your help and effort.
you are right, with new version and using only TKIP clients can connect, i use winxp clients with many different wlan adapters: Broadcom, Linksys, Atheros, and configured access with windows tools.
i just tested WPA-PSK, i guess it will work with TLS too. now i will configure and test it.

i get these messages now:

IEEE 802.1X: 5 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=1 length=0
   ignoring 1 extra octets after IEEE 802.1X packet
ath0: WPA rekeying GTK
WPA: group state machine entering state SETKEYS
GMK - hexdump(len=32): [REMOVED]
GTK - hexdump(len=32): [REMOVED]
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYNEGOTIATING
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 ie_len=0 gtk_len=32 keyidx=2 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=32): [REMOVED]
TX EAPOL - hexdump(len=145): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 7f fe 03 a1 00 20 00 00 00 00 00 00 00 05 3a 64 7f 32 5b 19 d3 50 65 df e8 d4 c2 70 52 03 c2 61 86 7e 6d 43 53 8e ce 80 f5 e4 75 c1 a0 31 c2 61 86 7e 6d 43 53 8e ce 80 f5 e4 75 c1 a0 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c9 c2 cb 2f 41 b8 4d 34 0f d5 e1 d5 7d cc 0e f8 00 20 82 96 6a 73 45 de 56 68 b7 56 ea 1d 31 a4 1b fa fa 81 fc d3 fe 8c e9 d0 ce a4 d0 b1 42 97 5f ba
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2
IEEE 802.1X: 99 bytes from 00:0f:66:11:c1:96
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:0f:66:11:c1:96 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:0f:66:11:c1:96 WPA: group key handshake completed (WPA)
WPA: 00:0f:66:11:c1:96 WPA_PTK_GROUP entering state IDLE

again, thanks.


_______________________________________________________________ 
Which Dutchman won the men's singles title at Wimbledon in 1996? 

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=229




From ruzsinszky.attila  Thu Mar 23 10:19:16 2006
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Thu, 23 Mar 2006 19:19:16 +0100
Subject: supplicant under WinXP
In-Reply-To: <20060323042057.GE10303@jm.kir.nu>
References: <f637dd860603211225l53de1242l@mail.gmail.com>	<44208117.3030308@kadzban.is-a-geek.net>	<f637dd860603220145j6ec6c62bu@mail.gmail.com>	<44213DD3.2090404@kadzban.is-a-geek.net>	<44218F2D.2050703@gmail.hu>
	<20060323042057.GE10303@jm.kir.nu>
Message-ID: <4422E6A4.9070608@gmail.hu>

Hi,

> wpa_supplicant would support WPA on both Linux and Windows XP, but it
> sounds like the Windows driver you are using does not support WPA.
The driver which was supplied with card doesn't support anything
except WEP (under M$ Windows).

>> Only problem, with my hidden SSID doesn't work.
>> I tried out ap_scan=0,1,2 parameters. Only ap_scan=1 is good for me,
>> and unhidden SSID! Is this correct?
> 
> ap_scan=2 should work fine with Windows NDIS drivers. I haven't seen any
> NDIS driver that would not work with it.. Did you configure all
> parameters that ap_scan comments in wpa_supplicant.conf mention? Please
> send your configuration file if you cannot get this working.
Here is my config:


ctrl_interface=/var/run/wpa_supplicant

eapol_version=1

ap_scan=1

fast_reauth=1

opensc_engine_path=/usr/lib/opensc/engine_opensc.so
pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so

network={
	ssid="mySSID"
	scan_ssid=1
	proto=WPA
	key_mgmt=WPA-EAP
	pairwise=CCMP TKIP
	group=CCMP TKIP
	eap=TLS
	identity="user at example.com"
	ca_cert="myCA-cacert.pem"
	client_cert="ruzsinszkya at email.hu-cert.pem"
	private_key="ruzsinszkya at email.hu-key.pem"
	private_key_passwd="myprivkey-pswd"
	priority=1
}

blob-base64-exampleblob={
SGVsbG8gV29ybGQhCg==
}

That's all! Others are commented out.

> I'm not aware of any card that works _perfectly_ ;-). I've used
> Prism2/2.5/3-based PC Cards successfully with both Windows and Linux.
I think my Senao NL-2511CD Plus(E100) card is Prism2.5. Is that right?

TIA,
RUzsi




From ruzsinszky.attila  Thu Mar 23 10:19:34 2006
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Thu, 23 Mar 2006 19:19:34 +0100
Subject: supplicant under WinXP
In-Reply-To: <44213DD3.2090404@kadzban.is-a-geek.net>
References: <f637dd860603211225l53de1242l@mail.gmail.com>	
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net>
Message-ID: <4422E6B6.9070000@gmail.hu>

Hi,

I sent thist message yesterday evening and I can't see on the list.
So let's see again...


Bryan Kadzban ?rta:
 > (I'm assuming you meant to copy the list on your last message...)
I think my messages remained private. :-(
I pushed the reply button and now I can see no more e-mail address
except yours.
Do I have to explicite address the list?

 >>> The SMC card should work (since the driver reports WPA-PSK
 >>> capability, it should be able to to TKIP encryption, and AFAIK
 >>> wpa_supplicant handles everything else).  But the Senao card might
 >>> have issues if its XP drivers only support WEP.
 >> It is very interesting, because SMC network program knows only WEP 
and WPA-PSK. But it is a good news in your opinion it will work!
 >
 > Well, wait...  If you're talking about the supplicant programs that came
No!
I talked about M$ drivers not about wpa_supplicant.

 > with the drivers, then that's not an "upper" bound on the encryption and
 > authentication protocols that the card can support.  The Senao card, for
 > instance:  if the program that came with it only has an option for WEP,
 > that doesn't mean that the card's firmware can't do TKIP, just that the
 > program that they provided can't do the 4-way handshake.  (Or that the
 > driver isn't advertising that capability.)
It is very interesting!
I'm confused now. :-(
The card is same:
- under Linux, with wpa_supplicant, I can connect my AP with WPA TKIP
TLS. So the card is support it. (I upgraded its firmware as I read on
the Net.)
- under M$ XP SP1 it doesn't work neither its driver or wpa_supplicant.

 > To find out for sure what capabilities the driver is giving Windows (and
 > therefore what encryptions it's capable of under wpa_supplicant), try
 > firing up the XP supplicant and adding a preferred network "manually".
 > Look at the options under authentication; if WPA and WPA-PSK are there,
 > then the card's driver is advertising support for them.  If only "open"
 > and "shared" are there, then the driver is only advertising WEP.
This is the situation. :-( No WPA!

I understand where is the problem then. Linux is working, XP not. Card
is the same. So the problematic part is the driver which was supplied
by card?

Back to your advice for SMC card...
It is working! ;-) Both under Linux and XP SP1! Nice.

Only problem, with my hidden SSID doesn't work.
I tried out ap_scan=0,1,2 parameters. Only ap_scan=1 is good for me,
and unhidden SSID! Is this correct?

And here is some other error notices:
D:\wpa_supplicant-windows-bin-0.4.8>wpa_supplicant -i 
\Device\NPF_{C8940014-8714
-4DD0-A851-560BCCAD89C6} -c wpa_supplicant.conf
Trying to associate with 00:14:bf:xx:xx:x (SSID='mySSID' freq=2xxx MHz)
Associated with 00:14:bf:xx:xx:x
CTRL-EVENT-EAP-STARTED EAP authentication started
OpenSSL: pending error: error:0D07803A:asn1 encoding 
routines:ASN1_ITEM_EX_D2I:n
ested asn1 error
OpenSSL: pending error: error:140C800D:SSL 
routines:SSL_use_certificate_file:ASN
1 lib
OpenSSL: pending error: error:0D0680A8:asn1 encoding 
routines:ASN1_CHECK_TLEN:wr
ong tag
OpenSSL: pending error: error:0D07803A:asn1 encoding 
routines:ASN1_ITEM_EX_D2I:n
ested asn1 error
OpenSSL: pending error: error:0D09A00D:asn1 encoding 
routines:d2i_PrivateKey:ASN
1 lib
OpenSSL: pending error: error:140CB00D:SSL 
routines:SSL_use_PrivateKey_file:ASN1
  lib
CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:14:bf:xx:xx:xx [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:14:bf:xx:xx:xx completed (auth)

TIA,
Ruzsi

Ps: Do you know PCMCIA card which is working perfectly under
SuSE >=9.0 and at least M$ XP?




From jar  Thu Mar 23 12:36:48 2006
From: jar (Jar)
Date: Thu, 23 Mar 2006 22:36:48 +0200
Subject: Hostapd & Xp client problem
Message-ID: <442306E0.1030400@pcuf.fi>

Hello

I try to setup hostapd for Windows clients. I use WPA-PSK and TKIP or 
CCMP but the connection doesn't work properly either of them. Group key 
handshake seems to be the problem? Any ideas or comments?

Hostap-drvier: 0.4.4-kernel
Kernel: 2.6.15-1.1833_FC4
Hostapd: 0.5.2
Card:
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.7.4 (station firmware)

Client OS: Xp+SP1+WPA fixes
Client supplicant: Xp's wzc
Client Card: Intel Pro Wireless 2100 3B with latest drivers

[root at AP hostapd-0.5.2]# ./hostapd hostapd.conf
Configuration file: hostapd.conf
Opening raw packet socket for ifindex 17
Using interface wlan0 with hwaddr 00:0e:XX:XX:XX:XX and ssid 'XXXX-YYYY'
Flushing old station entries
Deauthenticate all stations
MGMT
mgmt::auth
authentication: STA=00:04:23:4f:67:d6 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
   New STA
authentication reply: STA=00:04:23:4f:67:d6 auth_alg=0 
auth_transaction=2 resp=0
MGMT (TX callback) ACK
mgmt::auth cb
MGMT
mgmt::assoc_req
association request: STA=00:04:23:4f:67:d6 capab_info=0x11 
listen_interval=10
IEEE 802.11 element parse ignored unknown element (id=133 elen=28)
   new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
wlan0: STA 00:04:23:4f:67:d6 WPA: event 1 notification
wlan0: STA 00:04:23:4f:67:d6 WPA: start authentication
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/4 msg of 4-Way Handshake
Wireless event: cmd=0x8c03 len=20
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=103 - 
ack=1
DATA
IEEE 802.1X: 125 bytes from 00:04:23:4f:67:d6
    IEEE 802.1X: version=1 type=3 length=121
wlan0: STA 00:04:23:4f:67:d6 WPA: received EAPOL-Key frame (2/4 Pairwise)
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 3/4 msg of 4-Way Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=127 - 
ack=1
DATA
IEEE 802.1X: 99 bytes from 00:04:23:4f:67:d6
    IEEE 802.1X: version=1 type=3 length=95
wlan0: STA 00:04:23:4f:67:d6 WPA: received EAPOL-Key frame (4/4 Pairwise)
wlan0: STA 00:04:23:4f:67:d6 WPA: pairwise key handshake completed (WPA)
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
Wireless event: cmd=0x8c04 len=20
DATA
Data frame from not associated STA 00:04:23:4f:67:d6
MGMT
mgmt::auth
authentication: STA=00:04:23:4f:67:d6 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
   New STA
authentication reply: STA=00:04:23:4f:67:d6 auth_alg=0 
auth_transaction=2 resp=0
MGMT (TX callback) ACK
mgmt::auth cb
MGMT
mgmt::assoc_req
association request: STA=00:04:23:4f:67:d6 capab_info=0x11 
listen_interval=10
IEEE 802.11 element parse ignored unknown element (id=133 elen=28)
   new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
wlan0: STA 00:04:23:4f:67:d6 WPA: event 1 notification
wlan0: STA 00:04:23:4f:67:d6 WPA: start authentication
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/4 msg of 4-Way Handshake
DATA
Too short data frame
Wireless event: cmd=0x8c03 len=20
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=103 - 
ack=1
DATA
IEEE 802.1X: 125 bytes from 00:04:23:4f:67:d6
    IEEE 802.1X: version=1 type=3 length=121
wlan0: STA 00:04:23:4f:67:d6 WPA: received EAPOL-Key frame (2/4 Pairwise)
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 3/4 msg of 4-Way Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=127 - 
ack=1
DATA
IEEE 802.1X: 99 bytes from 00:04:23:4f:67:d6
    IEEE 802.1X: version=1 type=3 length=95
wlan0: STA 00:04:23:4f:67:d6 WPA: received EAPOL-Key frame (4/4 Pairwise)
wlan0: STA 00:04:23:4f:67:d6 WPA: pairwise key handshake completed (WPA)
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
IEEE 802.1X: 00:04:23:4f:67:d6 TX status - version=2 type=3 length=119 - 
ack=1
wlan0: STA 00:04:23:4f:67:d6 WPA: EAPOL-Key timeout
wlan0: STA 00:04:23:4f:67:d6 WPA: sending 1/2 msg of Group Key Handshake
DATA (TX callback) ACK
Wireless event: cmd=0x8c04 len=20
Signal 2 received - terminating
Flushing old station entries
Deauthenticate all stations

-- 
Best Regards, Jar



From bryan  Thu Mar 23 15:36:31 2006
From: bryan (Bryan Kadzban)
Date: Thu, 23 Mar 2006 18:36:31 -0500
Subject: supplicant under WinXP
In-Reply-To: <4422E6B6.9070000@gmail.hu>
References: <f637dd860603211225l53de1242l@mail.gmail.com>		<44208117.3030308@kadzban.is-a-geek.net>	<f637dd860603220145j6ec6c62bu@mail.gmail.com>	<44213DD3.2090404@kadzban.is-a-geek.net>
	<4422E6B6.9070000@gmail.hu>
Message-ID: <442330FF.5040806@kadzban.is-a-geek.net>

Ruzsinszky Attila wrote:
> I pushed the reply button and now I can see no more e-mail address
> except yours.
> Do I have to explicite address the list?

With most mail clients, you can hit "reply all" instead of "reply", and
it'll copy the list for you.  That's what I do in Thunderbird at least.
I've never used gmail (I know, I must be one of only about 5 people), so
I don't know exactly how you'd do it there.

> No!
> I talked about M$ drivers not about wpa_supplicant.

Must have misunderstood then, or something.

> I'm confused now. :-(
> The card is same:
> - under Linux, with wpa_supplicant, I can connect my AP with WPA TKIP
> TLS. So the card is support it. (I upgraded its firmware as I read on
> the Net.)

Sounds like both the card and its firmware support TKIP then.  And
wpa_supplicant supports WPA in EAP-TLS mode.  So it should work fine.

> - under M$ XP SP1 it doesn't work neither its driver or wpa_supplicant.

That's probably a problem with driver you're using then.

> I understand where is the problem then. Linux is working, XP not. Card
> is the same. So the problematic part is the driver which was supplied
> by card?

Yes; you could perhaps look for an updated driver from whoever made your
card.  WPA is pretty ancient by now -- if your card doesn't have drivers
that support it, I'll be surprised.

> Only problem, with my hidden SSID doesn't work.
> I tried out ap_scan=0,1,2 parameters. Only ap_scan=1 is good for me,
> and unhidden SSID! Is this correct?

As Jouni said, Windows/NDIS should work with ap_scan=2, so I'm not sure
what's going on with that.

> OpenSSL: pending error: error:0D07803A:asn1 encoding 
> routines:ASN1_ITEM_EX_D2I:nested asn1 error
> OpenSSL: pending error: error:140C800D:SSL 
> routines:SSL_use_certificate_file:ASN1 lib
> OpenSSL: pending error: error:0D0680A8:asn1 encoding 
> routines:ASN1_CHECK_TLEN:wrong tag
> OpenSSL: pending error: error:0D07803A:asn1 encoding 
> routines:ASN1_ITEM_EX_D2I:nested asn1 error
> OpenSSL: pending error: error:0D09A00D:asn1 encoding 
> routines:d2i_PrivateKey:ASN1 lib
> OpenSSL: pending error: error:140CB00D:SSL 
> routines:SSL_use_PrivateKey_file:ASN1 lib

Not sure where this comes from, but it doesn't look like the full
output.  Perhaps it's related to another message you got somewhere
before?

> CTRL-EVENT-CONNECTED - Connection to 00:14:bf:xx:xx:xx completed (auth)

This should mean that your card is connected and working just fine.  At
this point you should be able to get a DHCP lease (or statically assign
an address), and you should be able to pass traffic.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060323/377f45e7/attachment.pgp 


From adrian  Thu Mar 23 16:55:38 2006
From: adrian (Adrian Caceres)
Date: Thu, 23 Mar 2006 16:55:38 -0800
Subject: wpa_supplicant_scan sometimes will not initiate association when
	it should
Message-ID: <1143161739.8950.60.camel@localhost.localdomain>

I wrote a small app that controls the supplicant using the same
interface as wpa_cli.

I am running rev 0.4.8 but I believe the same bug is in 0.5.1.

Here is the sequence of events:

- app adds network.  Only one network in list
- app selects network.  Supplicant attempts to connect but driver fails.
wpa_s->prev_scan_ssid ends points to selected network.
- app attempts to reconnect.  In wpa_supplicant_scan, prev_scan_ssid
still points to the only network in the list and the one we want.

	ssid = wpa_s->conf->ssid;
	if (wpa_s->prev_scan_ssid != BROADCAST_SSID_SCAN) {
		while (ssid) {
			if (ssid == wpa_s->prev_scan_ssid) {
				ssid = ssid->next;
>>> this will lead to ssid being set to NULL
				break;
			}
			ssid = ssid->next;
		}
	}
	if (scan_req != 2 && wpa_s->conf->ap_scan == 2) {
		/*
		 * ap_scan=2 mode - try to associate with each SSID instead of
		 * scanning for each scan_ssid=1 network.
		 */
		if (ssid == NULL) {
>>> and we will return here - never requesting the driver to associate
		    return;
        }

The fix I implemented is as follows but I am not sure if this will
work on the other ap_scan modes.

@@ -852,6 +857,9 @@
                        ssid = ssid->next;
                }
        }
+    if (ssid == NULL) {
+           ssid = wpa_s->conf->ssid;
+    }
        while (ssid) {
                if (!ssid->disabled &&
                    (ssid->scan_ssid || wpa_s->conf->ap_scan == 2))



regards

- adrian







From jkmaline  Thu Mar 23 19:35:54 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 23 Mar 2006 19:35:54 -0800
Subject: supplicant under WinXP
In-Reply-To: <4422E6A4.9070608@gmail.hu>
References: <f637dd860603211225l53de1242l@mail.gmail.com>
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net>
	<44218F2D.2050703@gmail.hu> <20060323042057.GE10303@jm.kir.nu>
	<4422E6A4.9070608@gmail.hu>
Message-ID: <20060324033554.GA9370@jm.kir.nu>

On Thu, Mar 23, 2006 at 07:19:16PM +0100, Ruzsinszky Attila wrote:

> >> Only problem, with my hidden SSID doesn't work.

> ap_scan=1

That should be ap_scan=2

> network={
> 	ssid="mySSID"
> 	scan_ssid=1

scan_ssid is not supported by NDIS drivers, so that should be removed.

> 	pairwise=CCMP TKIP
> 	group=CCMP TKIP

These have to be explicitly set to just one value when using ap_scan=2,
i.e., remove either TKIP or CCMP based on what your AP is configured to
do.

-- 
Jouni Malinen                                            PGP id EFC895FA



From tbeville  Thu Mar 23 21:53:45 2006
From: tbeville (Tony Beville)
Date: Thu, 23 Mar 2006 21:53:45 -0800
Subject: WPA-Enterprise and hermes driver?
Message-ID: <44238969.8050700@intellidot.net>

Are many folks out there using the driver_hermes.c module?  I know it's 
not part of the current wpa_supplicant package, but there is an older 
version that is part of the agere driver for 2.4 kernel.   We had to 
forward-port that module to work with current wpa_supplicant, and have 
it working for several scenarios, including LEAP (non-WPA), and WPA-PSK.

I have been trying to get it work for  WPA with EAP, specifically LEAP, 
with some Cisco Aironet 1200s, but no luck.    I know I have the 
wpa_supplicant.conf correct, because testing on a laptop (2.6 kernel) 
with madwifi and ipw it works like a charm (Thanks to Jouni for helping 
on that!).  But our hermes device won't fly;  it fails on association.  
Sniffing the packets, it looks like the WPA info in the assoc request is 
missing.

We are using agere driver 7.20, on a 2.4 kernel. 

Anyone else out there using this hardware that can confirm the 
capabilities of this module, or of the driver?

Thanks!


Tony

tbeville (at) intellidot (dot) net








From ruzsinszky.attila  Fri Mar 24 08:44:32 2006
From: ruzsinszky.attila (Attila Ruzsinszky)
Date: Fri, 24 Mar 2006 11:44:32 -0500
Subject: supplicant under WinXP
In-Reply-To: <442330FF.5040806@kadzban.is-a-geek.net>
References: <f637dd860603211225l53de1242l@mail.gmail.com>
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net> <4422E6B6.9070000@gmail.hu>
	<442330FF.5040806@kadzban.is-a-geek.net>
Message-ID: <f637dd860603240844l3027f55o@mail.gmail.com>

Hi,

> > I pushed the reply button and now I can see no more e-mail address
> > except yours.
> > Do I have to explicite address the list?
>
> With most mail clients, you can hit "reply all" instead of "reply", and
Yes, "Reply all" was the trick! Thanks.
Now you're the addressee and the list gets a reply.

> Sounds like both the card and its firmware support TKIP then.  And
> wpa_supplicant supports WPA in EAP-TLS mode.  So it should work fine.
Yes, it works perfectly under Linux in the same notebook.

> > - under M$ XP SP1 it doesn't work neither its driver or wpa_supplicant.
>
> That's probably a problem with driver you're using then.
Yes.

> Yes; you could perhaps look for an updated driver from whoever made your
> card.  WPA is pretty ancient by now -- if your card doesn't have drivers
> that support it, I'll be surprised.
I haven't find it, yet.
Anyone can help me? Card is: NL-2511CD Plus (E100)

> As Jouni said, Windows/NDIS should work with ap_scan=2, so I'm not sure
> what's going on with that.
OK. My config should have to modify using ap_scan=2.
Under Linux, it wasn't problem. I'm not an XP expert. I try using M$
product as few as I can. But my colleagues are XP fans ...

> > OpenSSL: pending error: error:140CB00D:SSL
> > routines:SSL_use_PrivateKey_file:ASN1 lib
>
> Not sure where this comes from, but it doesn't look like the full
> output.  Perhaps it's related to another message you got somewhere
> before?
It was the full output what I enclosed.

> > CTRL-EVENT-CONNECTED - Connection to 00:14:bf:xx:xx:xx completed (auth)
>
> This should mean that your card is connected and working just fine.  At
> this point you should be able to get a DHCP lease (or statically assign
> an address), and you should be able to pass traffic.
Yes, it works like a charm! ;-) I got the IP over DHCP, but I'd like to mention
It was the SMC card, not my NL-2511!

Thank you for your help!
TIA:
Ruzsi



From ruzsinszky.attila  Fri Mar 24 08:46:42 2006
From: ruzsinszky.attila (Attila Ruzsinszky)
Date: Fri, 24 Mar 2006 11:46:42 -0500
Subject: supplicant under WinXP
In-Reply-To: <20060324033554.GA9370@jm.kir.nu>
References: <f637dd860603211225l53de1242l@mail.gmail.com>
	<44208117.3030308@kadzban.is-a-geek.net>
	<f637dd860603220145j6ec6c62bu@mail.gmail.com>
	<44213DD3.2090404@kadzban.is-a-geek.net> <44218F2D.2050703@gmail.hu>
	<20060323042057.GE10303@jm.kir.nu> <4422E6A4.9070608@gmail.hu>
	<20060324033554.GA9370@jm.kir.nu>
Message-ID: <f637dd860603240846i580d660et@mail.gmail.com>

Hi,

> > >> Only problem, with my hidden SSID doesn't work.
>
> > ap_scan=1
>
> That should be ap_scan=2
Yes, I know.

> > network={
> >       ssid="mySSID"
> >       scan_ssid=1
>
> scan_ssid is not supported by NDIS drivers, so that should be removed.
OK. And was it the problem?

> >       pairwise=CCMP TKIP
> >       group=CCMP TKIP
>
> These have to be explicitly set to just one value when using ap_scan=2,
> i.e., remove either TKIP or CCMP based on what your AP is configured to
> do.
I think this was the problem. Do you agree with me?

TIA,
Ruzsi



From jan.ceuleers  Fri Mar 24 09:12:09 2006
From: jan.ceuleers (Jan Ceuleers)
Date: Fri, 24 Mar 2006 18:12:09 +0100
Subject: Help needed
Message-ID: <44242869.5080409@computer.org>

All,

I am trying for the first time to get a Linux client to associate with 
an access point that is already successfully serving a number of Windows 
clients.

Client: soekris net4801 running kernel 2.4.31. Atheros-based wlan board. 
Madwifi driver; wpa_supplicant 0.4.8. The Access point is identical 
except that it runs hostapd 0.3.9.

I'm attaching debug output from wpa_supplicant on the client and hostapd 
on the ap.

I don't know why the ap requests deauth (what does reason=2 mean?). The 
client has a specific WPA key configured for its MAC address and it is 
mentioned in the hostapd.allow file. The AP's hostapd.conf file follows:

interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=0
logger_stdout=0
logger_stdout_level=4
debug=2
wpa=1
wpa_psk_file=/etc/hostapd.wpa-psk.keys
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
wpa_group_rekey=600
wpa_strict_rekey=1
macaddr_acl=1
deny_mac_file=/etc/hostapd.deny
accept_mac_file=/etc/hostapd.accept

Any hints will be gratefully received.

Jan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd.out
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060324/0697d31e/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant.out
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20060324/0697d31e/attachment-0001.txt 


From pu.jeff  Fri Mar 24 12:16:35 2006
From: pu.jeff (Jeff Pu)
Date: Fri, 24 Mar 2006 15:16:35 -0500
Subject: madwifi support multiple station VAPs?
Message-ID: <440d76750603241216i352bc44bw21946036a33d33c1@mail.gmail.com>

Hi, I wonder why only one station VAP can exist on a device? is it possible
to
extend multiple station VAP support on a Atheros device?

Thanks a lot,

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


From jim  Fri Mar 24 18:53:29 2006
From: jim (Jim Thompson)
Date: Fri, 24 Mar 2006 16:53:29 -1000
Subject: [Madwifi-users] Throughput tests with madwifi and
	hostap/wpasupplicant
In-Reply-To: <14441.1143060303@www069.gmx.net>
References: <14441.1143060303@www069.gmx.net>
Message-ID: <CA0EC7E4-E22F-4737-BBD5-046B34CDDD6D@netgate.com>


On Mar 22, 2006, at 10:45 AM, Beat Meier wrote:

> Hi all
>
> I've done some throughput tests with iperf.
>
> Configuration
> **************
>   AP: wrap2c, SR5
>   Client: wrap2c, CM9
> Software: madwifi-ng-1457, hostapd/wpa_supplicant-0.5.2 using WPA-PSK
> Rate was set fixed to the value indicate on ap and client.
> This is done with 802.11a (5.825 GHz)
> This was done without long distance i.e. only 4m but values
> of cts etc. are set to 6000m!!
> iperf was done at least 15 times per rate and the values were very  
> equal
> (iperf has default tcp window size (client: 16 Kbyte, server: 85.3  
> KByte)
> This has not been in the past!! It seems that either madwifi (which is
> more probable) or hostap/wpa_supplicant has changed to the good  
> site!!!
> In the past I had "fluctuations" about 3-4Mbps now around 0.1Mbps
>
> Iperf server on cliente wrap
> Iperf client from gatway before AP ie.e
> gw -> ap -> client
>
>
> Testresults
> ***********
>
>  6M:  4.3 Mbps (28%)
>  9M:  6.6 Mbps (27%)
> 12M:  8.2 Mbps (32%)
> 18M: 12.6 Mbps (30%)
> 24M: 16.0 Mbps (34%)
> 36M: 21.6 Mbps (40%)
> 48M: 25.7 Mbps (46%)
> 54M: 29.2 Mbps (46%)
>
> The percentage is the overhead (loss of bandwidth) at this rate.
>
> I've seen a lot of mails about asking max. throughput on wrap and
> that's cpu limited to max. 20Mbps but this seems not to be true as  
> seen by
> 48M,54M.

I can get around 30Mbps on freebsd, too.

> Has anybody more better results??
>
> Now my question.
> Does anybody know because until 18M (24M) the protocol overhead or  
> whatever
> is about 30%
> and later there is going to 45%?
> Is it because other modulation? (BPSK,QPSK,16-QAM,64-QAM). Has anybody
> information
> which modulation is used at which rate?
> Retries were in the normal range (I think).

If I had to guess, you're dropping more packets at the higher  
modulation rates.  At 48Mbps and 54Mbps, you're typically limited by  
EVM, not SNR.

Jim




From jan.ceuleers  Sat Mar 25 04:21:06 2006
From: jan.ceuleers (Jan Ceuleers)
Date: Sat, 25 Mar 2006 13:21:06 +0100
Subject: Help needed
In-Reply-To: <44242869.5080409@computer.org>
References: <44242869.5080409@computer.org>
Message-ID: <442535B2.20704@computer.org>

Answering part of my own question:

Jan Ceuleers wrote:
...
> I don't know why the ap requests deauth (what does reason=2 mean?).

I have since found that reason code 2 is called 
WLAN_REASON_PREV_AUTH_NOT_VALID . I however still don't understand why 
it is being invoked (e.g. assuming that this means that the previous 
authentication is not valid, what's invalid about it?).

Again, thanks for any help anyone is willing/able to provide.

Jan



From brix  Sat Mar 25 10:36:39 2006
From: brix (Henrik Brix Andersen)
Date: Sat, 25 Mar 2006 19:36:39 +0100
Subject: Group key renewal problem
In-Reply-To: <20060316193606.GA32562@osgiliath.brixandersen.dk>
References: <20060311180728.GA30840@osgiliath.brixandersen.dk>
	<20060311202319.GC9371@jm.kir.nu>
	<20060311204940.GB30840@osgiliath.brixandersen.dk>
	<20060312114348.GA17973@osgiliath.brixandersen.dk>
	<20060316193606.GA32562@osgiliath.brixandersen.dk>
Message-ID: <20060325183639.GA5917@osgiliath.brixandersen.dk>

On Thu, Mar 16, 2006 at 08:36:06PM +0100, Henrik Brix Andersen wrote:
> Just did, http://hostap.epitest.fi/bugz/show_bug.cgi?id=126

To others who may have encountered this issue, Jouni has produced a
patch for linux-2.6.x which fixes this issue:

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

Thanks Jouni! :)

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


From hostap  Sat Mar 25 19:37:13 2006
From: hostap (Alexey Marinichev)
Date: Sat, 25 Mar 2006 19:37:13 -0800
Subject: IEEE8021X problem
Message-ID: <44260C69.6050005@lyosha.org>

Hello,

I've been trying to get wpa_supplicant to work with our wireless network 
at work for quite a while and I'm always seeing the same problem: 
"SSL_connect - want more data".  Here's the log:

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=133
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (25, PEAP)
EAP-PEAP: Forced PEAP version 0
EAP-PEAP: Phase2 EAP types - hexdump(len=1): 1a
CTRL-EVENT-EAP-METHOD EAP method 25 (PEAP) selected
EAP: EAP entering state METHOD
SSL: Received packet(len=6) - Flags 0x21
EAP-PEAP: Start (server ver=1, own ver=0)
EAP-PEAP: Using PEAP version 0
SSL: (where=0x10 ret=0x1)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:before/connect initialization
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3 write client hello A
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3 read server hello A
SSL: SSL_connect - want more data
SSL: 101 bytes pending from ssl_out
SSL: 101 bytes left to be sent out (of total 101 bytes)
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE

The network part from my config file looks like this:
network={
        ssid="ssid"
        key_mgmt=IEEE8021X
        eap=PEAP
        identity="name at company.com"
        password="password"
        phase1="peapver=0"
        phase2="auth=MSCHAPV2"

        priority=0
}

Any ideas what it is and what I should try?  Instructions for using 
wireless network from Windows explicitly state that "Validate server 
certificate" should be unchecked.

Thanks!

Lyosha



From jkmaline  Sat Mar 25 19:50:49 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 19:50:49 -0800
Subject: IEEE8021X problem
In-Reply-To: <44260C69.6050005@lyosha.org>
References: <44260C69.6050005@lyosha.org>
Message-ID: <20060326035049.GA9382@jm.kir.nu>

On Sat, Mar 25, 2006 at 07:37:13PM -0800, Alexey Marinichev wrote:

> I've been trying to get wpa_supplicant to work with our wireless network 
> at work for quite a while and I'm always seeing the same problem: 
> "SSL_connect - want more data".  Here's the log:

Do you know which authentication server is used in this network? Could
you please capture the EAPOL frames between the authenticator (AP) and
supplicant, e.g., with Ethereal from the client? Is anything else
printed after this log excerpt or is it just followed by a timeout?

> Any ideas what it is and what I should try?  Instructions for using 
> wireless network from Windows explicitly state that "Validate server 
> certificate" should be unchecked.

That is quite "useful" comment.. This breaks the network security by
opening it for man-in-the-middle attacks.. Anyway, this should not be
related to the problem you are seeing since server certificate
validation would happen only after the ServerHello message is received
successfully.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Mar 25 19:57:28 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 19:57:28 -0800
Subject: Help with TTLS and PAP
In-Reply-To: <200603061609.24630.raffaello_@fastwebnet.it>
References: <200603061609.24630.raffaello_@fastwebnet.it>
Message-ID: <20060326035728.GB9382@jm.kir.nu>

On Mon, Mar 06, 2006 at 04:09:24PM +0100, Raffaello wrote:
> Hi, I'm trying to use wpa_supplicant with a wireless that needs TTLS and PAP 
> method autentication, but I have problems. Anyboby can help me?

Which driver and which kernel version are you using?

> State: SCANNING -> ASSOCIATING
> wpa_driver_hostap_associate
> ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
> ioctl[SIOCSIWFREQ]: Invalid argument
> Association request to the driver failed

This does not look very promising.. This looks like some kind of
mismatch in driver configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Mar 25 19:58:49 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 19:58:49 -0800
Subject: modify beacon frame
In-Reply-To: <20060307172149.96526.qmail@web26912.mail.ukl.yahoo.com>
References: <20060307172149.96526.qmail@web26912.mail.ukl.yahoo.com>
Message-ID: <20060326035849.GC9382@jm.kir.nu>

On Tue, Mar 07, 2006 at 05:21:49PM +0000, Larry McGrath wrote:

>   I need to modify the sending beacon frame structure and parameter  values in the hostap code. unsure where to start. I would appreciate  some pointers.

The current Prism2/2.5/3 firmware allows only addition of a generic IE
(e.g., WPA/RSN IE) to Beacon and Probe Response frames. Other kind of
modification is not supported.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Mar 25 20:04:21 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 20:04:21 -0800
Subject: R: Incompatibility hostapd - windows
In-Reply-To: <IVT2YZ$B9D31D88AA5F44B6EE5C6C5D2E44C476@libero.it>
References: <IVT2YZ$B9D31D88AA5F44B6EE5C6C5D2E44C476@libero.it>
Message-ID: <20060326040421.GD9382@jm.kir.nu>

On Wed, Mar 08, 2006 at 12:08:59PM +0100, jers at inwind.it wrote:

> Unfortunately I have not solved yet the problem with the VoIP phone.
> When I try to connect the phone to the AP, the first repeats the steps: Scanning, Associated and IP configuring while the latter prints the following debug as in the follow.

It looks like the phone does not reply to EAPOL frames from the AP. If
it has incorrect IEEE 802.1X/EAPOL frame processing for version
negotiation, that could be enough to explain this kind of behavior. I
would suggest updating the AP to use hostapd v0.5.2 and testing with
EAPOL hardcoded to use old version number. This can be done by modifying
wpa_common.h:

replace this line:

#define EAPOL_VERSION 2

with this:

#define EAPOL_VERSION 1

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Mar 25 20:06:45 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 20:06:45 -0800
Subject: Hostapd & Xp client problem
In-Reply-To: <442306E0.1030400@pcuf.fi>
References: <442306E0.1030400@pcuf.fi>
Message-ID: <20060326040645.GE9382@jm.kir.nu>

On Thu, Mar 23, 2006 at 10:36:48PM +0200, Jar wrote:

> I try to setup hostapd for Windows clients. I use WPA-PSK and TKIP or 
> CCMP but the connection doesn't work properly either of them. Group key 
> handshake seems to be the problem? Any ideas or comments?

> Hostap-drvier: 0.4.4-kernel
> Kernel: 2.6.15-1.1833_FC4

This sounds likely to be the same issue as was reported (and fixed)
here:

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

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Mar 25 20:11:44 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Mar 2006 20:11:44 -0800
Subject: problem with hostap+ndiswrapper
In-Reply-To: <BAY107-F183D344A65F794A9AD0268DCD80@phx.gbl>
References: <442080C6.6010806@caltech.edu>
	<BAY107-F183D344A65F794A9AD0268DCD80@phx.gbl>
Message-ID: <20060326041144.GF9382@jm.kir.nu>

On Tue, Mar 21, 2006 at 11:32:41PM +0000, FireStorm - wrote:

> I followed your advice and booted the laptop with Knoppix instead of 
> Devil-Linux. The good news is that now wpa_supplicant works perfectly. The 
> bad news is that now I have to figure out what's wrong with my Devil Linux 
> build.

> 1) there is no more "ioctl[SIOCSIWENCODEEXT]: No such device" repeated 4 
> times when I launch wpa_supplicant, but only "ioctl[SIOCSIWPMKSA]: No such 
> device" repeated once.

Sounds like you could be using a newer version of ndiswrapper and/or
kernel with Knoppix and that may have fixed something.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Mar 26 07:51:35 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 26 Mar 2006 07:51:35 -0800
Subject: Help needed
In-Reply-To: <44242869.5080409@computer.org>
References: <44242869.5080409@computer.org>
Message-ID: <20060326155134.GA9415@jm.kir.nu>

On Fri, Mar 24, 2006 at 06:12:09PM +0100, Jan Ceuleers wrote:

> I am trying for the first time to get a Linux client to associate with 
> an access point that is already successfully serving a number of Windows 
> clients.

> I'm attaching debug output from wpa_supplicant on the client and hostapd 
> on the ap.

It looks like the client is receiving the first message of 4-way
handshake and wpa_supplicant log indicates that it is sending out
message 2/4. However, this message does not show up in hostapd debug
log.

Based on this information, it's difficult to say why the message 2/4 is
not received correctly. It could be either because of the client not
actually sending it or because of the AP failing to receive it. If you
have possibility of using a wireless sniffer, it would be interesting to
see a capture log showing the frames sent between the AP and client in
this case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dtheoharis  Sun Mar 26 09:41:04 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 20:41:04 +0300
Subject: WPA2 problems using wpa_supplicant
Message-ID: <3948f2f20603260941l7b12043en69925f4ef93f7261@mail.gmail.com>

Hi ,


Trying to get prism2.5 using hostap to do wpa-psk/wpa2-psk tkip & aes
but i get this error and then it just stops



 wpa_supplicant -i wlan0 -D hostap -c /etc/wpa_supplicant.conf
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported


any fix for that?



From dtheoharis  Sun Mar 26 09:42:33 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 20:42:33 +0300
Subject: tx power
Message-ID: <3948f2f20603260942g2fcdc98fy273945791e46adba@mail.gmail.com>

Hi

Is there a reaso why i do  not see the tx power level in iwconfig?
its a prism2.5 card. A Senao to be more specific. Thanks ;)

 iwconfig wlan0
wlan0     IEEE 802.11b  ESSID:"test"
          Mode:Managed  Frequency:2.412 GHz  Access Point: None
          Bit Rate:2 Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-73 dBm  Noise level=-73 dBm
          Rx invalid nwid:0  Rx invalid crypt:432  Rx invalid frag:0
          Tx excessive retries:4  Invalid misc:41   Missed beacon:0



From dtheoharis  Sun Mar 26 10:11:06 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 21:11:06 +0300
Subject: upgrading firmware
Message-ID: <3948f2f20603261011o84188a4t12f75b30af3acb45@mail.gmail.com>

ok the test prism2_srec -v went fine so I thought I would procceed to
a permanent flash but now it gives me this error
whats going on?



Downloading to non-volatile memory (flash).
Note! This can take about 30 seconds. Do _not_ remove card during download.
Odd.. Download request for the kernel driver failed.
Are you sure you have compiled (and loaded the correct version of)
hostap.o module with PRISM2_DOWNLOAD_SUPPORT definition in
driver/module/hostap_config.h?
In addition, non-volatile download requires PRISM2_NON_VOLATILE_DOWNLOAD
to be defined.
ioctl[PRISM2_IOCTL_DOWNLOAD]: Operation not supported

Download failed!



From jkmaline  Sun Mar 26 10:26:25 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 26 Mar 2006 10:26:25 -0800
Subject: WPA2 problems using wpa_supplicant
In-Reply-To: <3948f2f20603260941l7b12043en69925f4ef93f7261@mail.gmail.com>
References: <3948f2f20603260941l7b12043en69925f4ef93f7261@mail.gmail.com>
Message-ID: <20060326182625.GC9415@jm.kir.nu>

On Sun, Mar 26, 2006 at 08:41:04PM +0300, Dimitris Theoharis wrote:

> Trying to get prism2.5 using hostap to do wpa-psk/wpa2-psk tkip & aes
> but i get this error and then it just stops

>  wpa_supplicant -i wlan0 -D hostap -c /etc/wpa_supplicant.conf
> ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported

Which version of the kernel, driver, and wpa_supplicant are you using?
Can you please send full debug output (i.e., add -dd to wpa_supplicant
command line) and 'dmesg' output after having tried starting up
wpa_supplicant? Can you using iwconfig to configure the driver?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Mar 26 10:27:39 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 26 Mar 2006 10:27:39 -0800
Subject: tx power
In-Reply-To: <3948f2f20603260942g2fcdc98fy273945791e46adba@mail.gmail.com>
References: <3948f2f20603260942g2fcdc98fy273945791e46adba@mail.gmail.com>
Message-ID: <20060326182739.GD9415@jm.kir.nu>

On Sun, Mar 26, 2006 at 08:42:33PM +0300, Dimitris Theoharis wrote:

> Is there a reaso why i do  not see the tx power level in iwconfig?
> its a prism2.5 card. A Senao to be more specific. Thanks ;)

I'm not aware of a way of reading the TX power level reliably from
Prism2/2.5/3 cards.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dtheoharis  Sun Mar 26 10:33:42 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 21:33:42 +0300
Subject: WPA2 problems using wpa_supplicant
In-Reply-To: <20060326182625.GC9415@jm.kir.nu>
References: <3948f2f20603260941l7b12043en69925f4ef93f7261@mail.gmail.com>
	<20060326182625.GC9415@jm.kir.nu>
Message-ID: <3948f2f20603261033u78f4f2bew5a1a09f86fe49ed3@mail.gmail.com>

wpa_supplicant -i wlan0 -D hostap -c /etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
'hostap' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=6):
     44 69 6d 4e 65 74                                 DimNet
proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='DimNet'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=19 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
Added alternative ifindex 4 (wifi0) for wireless events
Added alternative ifindex 4 (wifi0) for wireless events
Own MAC address: 00:02:6f:30:df:45
wpa_driver_hostap_set_wpa: enabled=1
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Driver does not support WPA.
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
Added interface wlan0
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=8
Received 177 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0f:b5:93:f9:67 ssid='DimNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=0
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to disable WPA in the driver.
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
Control interface directory not empty - leaving it behind
Cancelling scan request



kernel 2.6.15.6 , Debian and Kelmo's modified wpasup package. I am in
the process of upgrading my firwmare to a much newer one

On 3/26/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Sun, Mar 26, 2006 at 08:41:04PM +0300, Dimitris Theoharis wrote:
>
> > Trying to get prism2.5 using hostap to do wpa-psk/wpa2-psk tkip & aes
> > but i get this error and then it just stops
>
> >  wpa_supplicant -i wlan0 -D hostap -c /etc/wpa_supplicant.conf
> > ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
>
> Which version of the kernel, driver, and wpa_supplicant are you using?
> Can you please send full debug output (i.e., add -dd to wpa_supplicant
> command line) and 'dmesg' output after having tried starting up
> wpa_supplicant? Can you using iwconfig to configure the driver?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From dtheoharis  Sun Mar 26 10:59:03 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 21:59:03 +0300
Subject: tx power
In-Reply-To: <20060326182739.GD9415@jm.kir.nu>
References: <3948f2f20603260942g2fcdc98fy273945791e46adba@mail.gmail.com>
	<20060326182739.GD9415@jm.kir.nu>
Message-ID: <3948f2f20603261059l676fa2f5ybe9b2d51fc731c23@mail.gmail.com>

is there another way?

On 3/26/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Sun, Mar 26, 2006 at 08:42:33PM +0300, Dimitris Theoharis wrote:
>
> > Is there a reaso why i do  not see the tx power level in iwconfig?
> > its a prism2.5 card. A Senao to be more specific. Thanks ;)
>
> I'm not aware of a way of reading the TX power level reliably from
> Prism2/2.5/3 cards.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From dtheoharis  Sun Mar 26 12:17:18 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sun, 26 Mar 2006 23:17:18 +0300
Subject: flashing firmware
Message-ID: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>

I keep getting errors

I first found this how to :  http://hostap.epitest.fi/

If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
hostap does not compile. Simply comment them back and it
compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
Debian.

My card is  a Senao PCMCIA nl-2511cd plus ext2 pcmcia
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.4.9 (station firmware) .


How to fix the  " make " problem ?



From acinonyxs  Sun Mar 26 13:00:32 2006
From: acinonyxs (Acinonyx)
Date: Mon, 27 Mar 2006 00:00:32 +0300
Subject: tx power
References: <3948f2f20603260942g2fcdc98fy273945791e46adba@mail.gmail.com><20060326182739.GD9415@jm.kir.nu>
	<3948f2f20603261059l676fa2f5ybe9b2d51fc731c23@mail.gmail.com>
Message-ID: <005801c65118$55c70890$3c10020a@acinonyxpc>

Try this patch:

http://acinonyx.dimme.net/electronics/index.html


----- Original Message ----- 
From: "Dimitris Theoharis" <dtheoharis at gmail.com>
To: <hostap at shmoo.com>
Sent: Sunday, March 26, 2006 9:59 PM
Subject: Re: tx power


> is there another way?
> 
> On 3/26/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>> On Sun, Mar 26, 2006 at 08:42:33PM +0300, Dimitris Theoharis wrote:
>>
>> > Is there a reaso why i do  not see the tx power level in iwconfig?
>> > its a prism2.5 card. A Senao to be more specific. Thanks ;)
>>
>> I'm not aware of a way of reading the TX power level reliably from
>> Prism2/2.5/3 cards.
>>
>> --
>> 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
>

__________________________________________________
?????????????? Yahoo!;
?????????? ?? ?????????? ???????? (spam);   ?? Yahoo! Mail ???????? ??? ???????? ?????? ????????? ???? ??? ??????????? ?????????  
http://mail.yahoo.gr 



From dtheoharis  Sun Mar 26 13:51:28 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 27 Mar 2006 00:51:28 +0300
Subject: flashing firmware ******* update******
Message-ID: <3948f2f20603261351x30428374n26bbbaa4dbc5942@mail.gmail.com>

I managed to do a RAM only based downloading of new firmware. I still
can not get it to stay permanent because of the previous errors I am
getting.



this is working now

 prism2_srec -g wlan0 ak010104.hex
srec summary for ak010104.hex
Included file name: AK010104.HEX
Component: 0x0015 1.1.4 (primary firmware)


Verifying update compatibility and combining data:
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
OK.

Downloading to volatile memory (RAM).
OK.
root at D810:/home/dimgr/1.7.4# prism2_srec -r wlan0  rf010704.hex
srec summary for rf010704.hex
Included file name: RF010704.HEX
Component: 0x001f 1.7.4 (station firmware)

ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
STAID not available (maybe running PRI-only)
ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
ioctl[PRISM2_IOCTL_HOSTAPD]: No data available

Verifying update compatibility and combining data:
OK.

Downloading to volatile memory (RAM).
OK.
Components after download:
  NICID: 0x800c v1.0.0
  PRIID: 0x0015 v1.1.4
  STAID: 0x001f v1.7.4



but


prism2_srec -v -f wlan0 <primary firmware> <station firmware>     will
still wont work



From stijn  Sun Mar 26 18:33:34 2006
From: stijn (Stijn Tintel)
Date: Mon, 27 Mar 2006 04:33:34 +0200
Subject: Perl wrapper for wpa_supplicant/hostapd
Message-ID: <44274EFE.1070203@linux-ipv6.be>

Hi

In case anyone might be interested, rafl wrote a small wrapper around 
wpa_ctrl.[ch] in the wpasupplicant sources so one can communicate with 
wpa_supplicant/hostapd using perl now.

It is available for download at 
http://search.cpan.org/~flora/Wifi-WpaCtrl-0.01/pm/WpaCtrl.pm
Feedback (to rafl) is appreciated. Thanks!


Kindest regards
Stijn Tintel




From jkmaline  Sun Mar 26 19:15:57 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 26 Mar 2006 19:15:57 -0800
Subject: flashing firmware
In-Reply-To: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
Message-ID: <20060327031557.GH9415@jm.kir.nu>

On Sun, Mar 26, 2006 at 11:17:18PM +0300, Dimitris Theoharis wrote:

> If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
> PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
> hostap does not compile. Simply comment them back and it
> compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
> Debian.

Please describe what exactly you changed in hostap_config.h.

> How to fix the  " make " problem ?

How about starting by sending the error messages from the compilers
(full make output)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From dtheoharis  Sun Mar 26 22:43:28 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 27 Mar 2006 09:43:28 +0300
Subject: flashing firmware
In-Reply-To: <20060327031557.GH9415@jm.kir.nu>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
	<20060327031557.GH9415@jm.kir.nu>
Message-ID: <3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>

I uncomented the  2 defines.

for example



/* Include code for downloading firmware images into volatile RAM. */
#define PRISM2_DOWNLOAD_SUPPORT

i removed that #

and

#define PRISM2_NON_VOLATILE_DOWNLOAD

removed that # too




On 3/27/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Sun, Mar 26, 2006 at 11:17:18PM +0300, Dimitris Theoharis wrote:
>
> > If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
> > PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
> > hostap does not compile. Simply comment them back and it
> > compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
> > Debian.
>
> Please describe what exactly you changed in hostap_config.h.
>
> > How to fix the  " make " problem ?
>
> How about starting by sending the error messages from the compilers
> (full make output)?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From dtheoharis  Sun Mar 26 23:20:20 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 27 Mar 2006 10:20:20 +0300
Subject: flashing firmware
In-Reply-To: <3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
	<20060327031557.GH9415@jm.kir.nu>
	<3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
Message-ID: <3948f2f20603262320k48dba5aahc35bb2a981fa1ba1@mail.gmail.com>

I managed to ONLY  download primary firmware alone in Genesis mode.
Everything else fails

On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> I uncomented the  2 defines.
>
> for example
>
>
>
> /* Include code for downloading firmware images into volatile RAM. */
> #define PRISM2_DOWNLOAD_SUPPORT
>
> i removed that #
>
> and
>
> #define PRISM2_NON_VOLATILE_DOWNLOAD
>
> removed that # too
>
>
>
>
> On 3/27/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> > On Sun, Mar 26, 2006 at 11:17:18PM +0300, Dimitris Theoharis wrote:
> >
> > > If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
> > > PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
> > > hostap does not compile. Simply comment them back and it
> > > compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
> > > Debian.
> >
> > Please describe what exactly you changed in hostap_config.h.
> >
> > > How to fix the  " make " problem ?
> >
> > How about starting by sending the error messages from the compilers
> > (full make output)?
> >
> > --
> > Jouni Malinen                                            PGP id EFC895FA
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
>



From dtheoharis  Sun Mar 26 23:21:24 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 27 Mar 2006 10:21:24 +0300
Subject: flashing firmware
In-Reply-To: <3948f2f20603262320k48dba5aahc35bb2a981fa1ba1@mail.gmail.com>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
	<20060327031557.GH9415@jm.kir.nu>
	<3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
	<3948f2f20603262320k48dba5aahc35bb2a981fa1ba1@mail.gmail.com>
Message-ID: <3948f2f20603262321v71f372b8nb6eb6988f56ab616@mail.gmail.com>

station firmware too

so

prism2_srec -g
                    -r

work fine


On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> I managed to ONLY  download primary firmware alone in Genesis mode.
> Everything else fails
>
> On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> > I uncomented the  2 defines.
> >
> > for example
> >
> >
> >
> > /* Include code for downloading firmware images into volatile RAM. */
> > #define PRISM2_DOWNLOAD_SUPPORT
> >
> > i removed that #
> >
> > and
> >
> > #define PRISM2_NON_VOLATILE_DOWNLOAD
> >
> > removed that # too
> >
> >
> >
> >
> > On 3/27/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> > > On Sun, Mar 26, 2006 at 11:17:18PM +0300, Dimitris Theoharis wrote:
> > >
> > > > If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
> > > > PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
> > > > hostap does not compile. Simply comment them back and it
> > > > compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
> > > > Debian.
> > >
> > > Please describe what exactly you changed in hostap_config.h.
> > >
> > > > How to fix the  " make " problem ?
> > >
> > > How about starting by sending the error messages from the compilers
> > > (full make output)?
> > >
> > > --
> > > Jouni Malinen                                            PGP id EFC895FA
> > > _______________________________________________
> > > HostAP mailing list
> > > HostAP at shmoo.com
> > > http://lists.shmoo.com/mailman/listinfo/hostap
> > >
> >
>



From dtheoharis  Mon Mar 27 00:05:00 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 27 Mar 2006 11:05:00 +0300
Subject: flashing firmware
In-Reply-To: <3948f2f20603262321v71f372b8nb6eb6988f56ab616@mail.gmail.com>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
	<20060327031557.GH9415@jm.kir.nu>
	<3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
	<3948f2f20603262320k48dba5aahc35bb2a981fa1ba1@mail.gmail.com>
	<3948f2f20603262321v71f372b8nb6eb6988f56ab616@mail.gmail.com>
Message-ID: <3948f2f20603270005k3f37fdfflc2a40ef8a00c26c2@mail.gmail.com>

the config.h that doesnt work



#ifndef HOSTAP_CONFIG_H
#define HOSTAP_CONFIG_H

#define PRISM2_VERSION "0.4.7 - 2005-11-20"

/* In the previous versions of Host AP driver, support for user space version
 * of IEEE 802.11 management (hostapd) used to be disabled in the default
 * configuration. From now on, support for hostapd is always included and it is
 * possible to disable kernel driver version of IEEE 802.11 management with a
 * separate define, PRISM2_NO_KERNEL_IEEE80211_MGMT. */
/* #define PRISM2_NO_KERNEL_IEEE80211_MGMT */

/* Maximum number of events handler per one interrupt */
#define PRISM2_MAX_INTERRUPT_EVENTS 20

/* Use PCI bus master to copy data to/from BAP (only available for
 * hostap_pci.o).
 *
 * Note! This is extremely experimental. PCI bus master is not supported by
 * Intersil and it seems to have some problems at least on TX path (see below).
 * The driver code for implementing bus master support is based on guessing
 * and experimenting suitable control bits and these might not be correct.
 * This code is included because using bus master makes a huge difference in
 * host CPU load (something like 40% host CPU usage to 5-10% when sending or
 * receiving at maximum throughput).
 *
 * Note2! Station firmware version 1.3.5 and primary firmware
versionEnable PRISM2_DOWNLOAD_SUPPORT and PRISM2_NON_VOLATILE_DOWNLOAD
in driver/modules/hostap_config.h. You simply just uncomment those two
define's. 1.0.7
 * have some fixes for PCI corruption and these (or newer) versions are
 * recommended especially when using bus mastering.
 *
 * NOTE: PCI bus mastering code has not been updated for long time and it is
 * not likely to compile and it will _not_ work as is. Only enable this if you
 * are prepared to first fix the implementation..
 */
/* #define PRISM2_BUS_MASTER */

#ifdef PRISM2_BUS_MASTER

/* PCI bus master implementation seems to be broken in current
 * hardware/firmware versions. Enable this to use enable command to fix
 * something before starting bus master operation on TX path. This will add
 * some latency and an extra interrupt to each TX packet. */
#define PRISM2_ENABLE_BEFORE_TX_BUS_MASTER

#endif /* PRISM2_BUS_MASTER */

/* Include code for downloading firmware images into volatile RAM. */
#define PRISM2_DOWNLOAD_SUPPORT

/* Allow kernel configuration to enable download support. */
#if !defined(PRISM2_DOWNLOAD_SUPPORT) && defined(CONFIG_HOSTAP_FIRMWARE)
#define PRISM2_DOWNLOAD_SUPPORT
#endif

#ifdef PRISM2_DOWNLOAD_SUPPORT
/* Allow writing firmware images into flash, i.e., to non-volatile storage.
 * Before you enable this option, you should make absolutely sure that you are
 * using prism2_srec utility that comes with THIS version of the driver!
 * In addition, please note that it is possible to kill your card with
 * non-volatile download if you are using incorrect image. This feature has not
 * been fully tested, so please be careful with it. */
#define PRISM2_NON_VOLATILE_DOWNLOAD
#endif /* PRISM2_DOWNLOAD_SUPPORT */

/* Include wireless extensions sub-ioctl support even if wireless extensions
 * version is less than 15 (actually, only if it is 12 .. 14). If ver >= 15,
 * these will be included. Please note, that this requires iwpriv version 25
 * or higher (older versions will segfault due to long ioctl list). */
/* #define PRISM2_USE_WE_SUB_IOCTLS */

/* Use IW_PRIV_TYPE_ADDR with private WE ioctls taking MAC address argument
 * (instead of old 18*char). This requires iwpriv ver >= 25. This will be
 * automatically included for WIRELESS_EXT >= 15. */
/* #define PRISM2_USE_WE_TYPE_ADDR */

/* Save low-level I/O for debugging. This should not be enabled in normal use.
 */
/* #define PRISM2_IO_DEBUG */

/* Following defines can be used to remove unneeded parts of the driver, e.g.,
 * to limit the size of the kernel module. Definitions can be added here in
 * hostap_config.h or they can be added to make command with EXTRA_CFLAGS,
 * e.g.,
 * 'make pccard EXTRA_CFLAGS="-DPRISM2_NO_DEBUG -DPRISM2_NO_PROCFS_DEBUG"'
 */

/* Do not include debug messages into the driver */
/* #define PRISM2_NO_DEBUG */

/* Do not include /proc/net/prism2/wlan#/{registers,debug} */
/* #define PRISM2_NO_PROCFS_DEBUG */

/* Do not include station functionality (i.e., allow only Master (Host AP) mode
 */
/* #define PRISM2_NO_STATION_MODES */

/* Enable TX power Setting functions
 * (min att = -128 , max att =  127)
 */

#define RAW_TXPOWER_SETTING

/* Use Linux crypto API instead of own encryption implementation whenever
 * possible. */
/* #define HOSTAP_USE_CRYPTO_API */

#endif /* HOSTAP_CONFIG_H */








On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> station firmware too
>
> so
>
> prism2_srec -g
>                     -r
>
> work fine
>
>
> On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> > I managed to ONLY  download primary firmware alone in Genesis mode.
> > Everything else fails
> >
> > On 3/27/06, Dimitris Theoharis <dtheoharis at gmail.com> wrote:
> > > I uncomented the  2 defines.
> > >
> > > for example
> > >
> > >
> > >
> > > /* Include code for downloading firmware images into volatile RAM. */
> > > #define PRISM2_DOWNLOAD_SUPPORT
> > >
> > > i removed that #
> > >
> > > and
> > >
> > > #define PRISM2_NON_VOLATILE_DOWNLOAD
> > >
> > > removed that # too
> > >
> > >
> > >
> > >
> > > On 3/27/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> > > > On Sun, Mar 26, 2006 at 11:17:18PM +0300, Dimitris Theoharis wrote:
> > > >
> > > > > If i uncomment  PRISM2_DOWNLOAD_SUPPORT and
> > > > > PRISM2_NON_VOLATILE_DOWNLOAD in driver/modules/hostap_config.h   then
> > > > > hostap does not compile. Simply comment them back and it
> > > > > compiles fine.  I am using hostap-driver-0.4.7, 2.6.15.6 kernel on
> > > > > Debian.
> > > >
> > > > Please describe what exactly you changed in hostap_config.h.
> > > >
> > > > > How to fix the  " make " problem ?
> > > >
> > > > How about starting by sending the error messages from the compilers
> > > > (full make output)?
> > > >
> > > > --
> > > > Jouni Malinen                                            PGP id EFC895FA
> > > > _______________________________________________
> > > > HostAP mailing list
> > > > HostAP at shmoo.com
> > > > http://lists.shmoo.com/mailman/listinfo/hostap
> > > >
> > >
> >
>



From brix  Mon Mar 27 00:12:17 2006
From: brix (Henrik Brix Andersen)
Date: Mon, 27 Mar 2006 10:12:17 +0200
Subject: flashing firmware
In-Reply-To: <3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
References: <3948f2f20603261217v55475e72n4110535118621c3a@mail.gmail.com>
	<20060327031557.GH9415@jm.kir.nu>
	<3948f2f20603262243u31c27939h510c213bfc0022b0@mail.gmail.com>
Message-ID: <20060327081217.GA20324@osgiliath.brixandersen.dk>

On Mon, Mar 27, 2006 at 09:43:28AM +0300, Dimitris Theoharis wrote:
> /* Include code for downloading firmware images into volatile RAM. */
> #define PRISM2_DOWNLOAD_SUPPORT
> 
> i removed that #
> 
> and
> 
> #define PRISM2_NON_VOLATILE_DOWNLOAD
> 
> removed that # too

Removing the # in front of define is not the correct way of enabling
non-volatile firmware downloads, please see the below patch:

diff -urp hostap-driver-0.4.7/driver/modules/hostap_config.h hostap-driver-0.4.7-firmware/driver/modules/hostap_config.h
--- hostap-driver-0.4.7/driver/modules/hostap_config.h	2005-11-21 02:42:12.000000000 +0100
+++ hostap-driver-0.4.7-firmware/driver/modules/hostap_config.h	2005-11-21 10:27:54.000000000 +0100
@@ -59,7 +59,7 @@
  * In addition, please note that it is possible to kill your card with
  * non-volatile download if you are using incorrect image. This feature has not
  * been fully tested, so please be careful with it. */
-/* #define PRISM2_NON_VOLATILE_DOWNLOAD */
+#define PRISM2_NON_VOLATILE_DOWNLOAD
 #endif /* PRISM2_DOWNLOAD_SUPPORT */
 
 /* Include wireless extensions sub-ioctl support even if wireless extensions

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


From jan.ceuleers  Mon Mar 27 02:22:59 2006
From: jan.ceuleers (Jan Ceuleers)
Date: Mon, 27 Mar 2006 12:22:59 +0200
Subject: Help needed
In-Reply-To: <20060326155134.GA9415@jm.kir.nu>
References: <44242869.5080409@computer.org> <20060326155134.GA9415@jm.kir.nu>
Message-ID: <4427BD03.5050306@computer.org>

Jouni Malinen wrote:
> It looks like the client is receiving the first message of 4-way
> handshake and wpa_supplicant log indicates that it is sending out
> message 2/4. However, this message does not show up in hostapd debug
> log.
> 
> Based on this information, it's difficult to say why the message 2/4 is
> not received correctly. It could be either because of the client not
> actually sending it or because of the AP failing to receive it. If you
> have possibility of using a wireless sniffer, it would be interesting to
> see a capture log showing the frames sent between the AP and client in
> this case.

Jouni,

Thanks very much for your response.

I have since resolved the problem. For the record: it seems that I was 
over-configuring the wireless interface on the client prior to calling 
wpa_supplicant. What works is the following:

modprobe ath_pci
ifconfig ath0 up
wpa_supplicant -Bw -c /etc/wpa_supplicant.conf -iath0 -Dmadwifi
dhcpcd -d ath0

What does not work is setting a bunch of parameters (such as ssid, 
network mode, etc.) using iwconfig and iwpriv prior to calling 
wpa_supplicant.

My problem may have been due to one parameter being set in particular, 
but I haven't bothered trying to find out.

Best regards, Jan



From BLA023  Mon Mar 27 06:00:45 2006
From: BLA023 (Avdeev Leonid-BLA023)
Date: Mon, 27 Mar 2006 16:00:45 +0200
Subject: Question about hostapd (authenticator) support for wired (Ethernet)
	clients
Message-ID: <156788466B1F4C46B37ACABC385FA555EA363C@zil01exm62.ds.mot.com>

Hello,
 
    Once you posted a link to an extension that permits HostAP to work
in wired env.
    It was pae-0.0.2.tar.gz, the link does not work now. 
    Could you please update it or give me some other location where the
extentsion could be acquired.
 
Regards,
Avdeev Leonid
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060327/97835c5d/attachment.htm 


From jakamkon  Mon Mar 27 06:48:44 2006
From: jakamkon (Kuba Konczyk)
Date: Mon, 27 Mar 2006 16:48:44 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
Message-ID: <2e947fbb0603270648x78420617kf81192474f89c27a@mail.gmail.com>

Hello,

Support for wired clients is now integrated in hostapd.Look at the
file wired.conf in hostapd sources.According to README it's
experimental,but I'm currently working with it without a problems.

Regards
Kuba



From BLA023  Mon Mar 27 07:20:51 2006
From: BLA023 (Avdeev Leonid-BLA023)
Date: Mon, 27 Mar 2006 17:20:51 +0200
Subject: Question about hostapd (authenticator) support for wired (Ethernet)
	clients
Message-ID: <156788466B1F4C46B37ACABC385FA555EA368C@zil01exm62.ds.mot.com>

Hello,
 
    If it is integrated in hostapd then the PAE support is done in user
space now?
    No kernel pathces are needed?
    
 
Regards,
Avdeev Leonid
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20060327/2e79563d/attachment.htm 


From jakamkon  Mon Mar 27 07:37:49 2006
From: jakamkon (Kuba Konczyk)
Date: Mon, 27 Mar 2006 17:37:49 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
Message-ID: <2e947fbb0603270737ub1118e4w228a5c6fc2c3ca33@mail.gmail.com>

Hello,

>> If it is integrated in hostapd then the PAE support is done in user
>> space now?
Yes.
>> No kernel pathces are needed?
No kernel patches are needed.

Regards
Kuba



From pelusitavali  Mon Mar 27 08:25:31 2006
From: pelusitavali (Pelusa Vali)
Date: Mon, 27 Mar 2006 17:25:31 +0100
Subject: slow and delayed connection
Message-ID: <PM.11738.1143476731@pmweb7.uk1.bibliotech.net>

>hi list, well, finally my ap works with wpa-eap, i use debian etch, madwifi-ng-r1475, freeradius 1.1.0 and hostapd 0.5.2. my ap can authenticate users and they can connect to wlan, everything ok.  but now result they cann't surf internet because connection is very slow, they cann't inclusive access google or yahoo, connection is too slow and requests are never completed or delays among 35-120 seconds.  i'm just performing tests, so ap and clients are in same room.
and when clients authenticating get lots of messages like this:

IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 BE_AUTH entering state IDLE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0f:66:11:c1:96 REAUTH_TIMER entering state INITIALIZE
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state INITPMK
WPA: PMK from EAPOL state machine (len=32)
WPA: 00:0f:66:11:c1:96 WPA_PTK entering state PTKSTART
ath0: STA 00:0f:66:11:c1:96 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=1 ie_len=0 gtk_len=0 key idx=0 encr=0)
TX EAPOL - hexdump(len=113): 00 0f 66 11 c1 96 00 0f 66 11 c1 97 88 8e 02 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 bb a5 40 06 72 ff 43 57 37 d3 d3 67 f1  5c 13 3f 6c 48 d1 fb 14 5a 31 ce b2 ce 47 a9 96 20 a5 20 00 00 00 00 00 00 00 0 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

and authentication delays 2 minutes, is it normal??

>using ethereal to monitor wlan get a lot (but really many) of messages like this:
>
>SOURCE             DESTINATION           PROTOCOL                  INFO
>Cisco-Li_11:c1:96  192.168.50.1          MDS HEADER                [Malformed Packet]
>
>where 192.168.50.1 is ap's ip direction.
>these are my configuration files:
>
>MADWIFI:
>
>rmmod ath_pci
>modprobe ath_pci autocreate=ap
>ifconfig ath0 up
>iwpriv ath0 mode 3
>iwconfig ath0 essid MYWLAN
>iwconfig ath0 channel auto
>iwconfig ath0 bitrate 54M
>echo 1 > /proc/sys/net/ipv4/ip_forward
>/etc/init.d/networking restart
>IPTABLES=/sbin/iptables
>$IPTABLES -F -t nat
>$IPTABLES -A POSTROUTING -t nat -o eth0 -j MASQUERADE
>/etc/init.d/dhcp restart
>
>HOSTAPD:
>
>interface=ath0
>driver=madwifi
>logger_syslog=-1
>logger_syslog_level=2
>logger_stdout=-1
>logger_stdout_level=1
>debug=4
>dump_file=/tmp/hostapd.dump
>ctrl_interface=/var/run/hostapd
>ctrl_interface_group=0
>ssid=MYWLAN
>macaddr_acl=0
>auth_algs=1
>ieee8021x=1
>eap_server=0
>own_ip_addr=127.0.0.1
>nas_identifier=www.srvw1.com
>auth_server_addr=127.0.0.1
>auth_server_port=1812
>auth_server_shared_secret=mywlan
>acct_server_addr=127.0.0.1
>acct_server_port=1813
>acct_server_shared_secret=mywlan
>wpa=1
>wpa_key_mgmt=WPA-EAP
>wpa_pairwise=TKIP
>wpa_group_rekey=300
>wpa_gmk_rekey=640
>
>typing 8011debug 0xffffffff get this:
>
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] power save mode on, 1 sta's in ps mode
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] save frame, 1 now queued
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] power save mode off, 0 sta's in ps mode
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] flush ps queue, 1 packets queued
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:97] ieee80211_beacon_update: TIM updated, pending 0, off 0, len 1
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] power save mode on, 1 sta's in ps mode
>Mar 26 05:49:48 www kernel: ath0: [00:0f:66:11:c1:96] power save mode off, 0 sta's in ps mode
>Mar 26 05:49:50 www kernel: ath0: received probe_req from 00:0f:66:11:c1:96 rssi 20
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] recv probe req
>Mar 26 05:49:50 www kernel: ath0: ieee80211_ref_node (ieee80211_send_mgmt:1765) cd739000<00:0f:66:11:c1:96> refcnt 5
>Mar 26 05:49:50 www kernel: [00:0f:66:11:c1:96] send probe_resp on channel 1
>Mar 26 05:49:50 www kernel: ath0: received probe_req from 00:0f:66:11:c1:96 rssi 21
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] recv probe req
>Mar 26 05:49:50 www kernel: ath0: ieee80211_ref_node (ieee80211_send_mgmt:1765) cd739000<00:0f:66:11:c1:96> refcnt 5
>Mar 26 05:49:50 www kernel: [00:0f:66:11:c1:96] send probe_resp on channel 1
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] power save mode off, 0 sta's in ps mode
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] power save mode on, 1 sta's in ps mode
>Mar 26 05:49:50 www kernel: ath0: received probe_req from 00:0f:66:11:c1:96 rssi 12
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] recv probe req
>Mar 26 05:49:50 www kernel: ath0: ieee80211_ref_node (ieee80211_send_mgmt:1765) cd739000<00:0f:66:11:c1:96> refcnt 5
>Mar 26 05:49:50 www kernel: [00:0f:66:11:c1:96] send probe_resp on channel 1
>Mar 26 05:49:50 www kernel: ath0: [00:0f:66:11:c1:96] power save mode off, 0 sta's in ps mode
>
>and athdebug 0xffffffff this:
>
>Mar 26 05:55:08 www kernel: ath_intr: status 0x10000
>Mar 26 05:55:08 www kernel: ath_beacon_setup: m c363a5c0 len 148
>Mar 26 05:55:08 www kernel: ath_intr: status 0x9
>Mar 26 05:55:08 www kernel: ath_rx_tasklet
>Mar 26 05:55:08 www kernel: R (c1a53060 1a53060) 01a53090 03342020 00000000 00000c60 1164001c 598e0b03 *
>Mar 26 05:55:08 www kernel: TODS 00:0f:66:11:c1:96->00:0f:66:11:c1:97(00:0f:66:11:c1:97) data 48M +22
>Mar 26 05:55:08 www kernel:  
>Mar 26 05:55:08 www kernel: 48 09 2c 00 00 0f 66 11  c1 97 00 0f 66 11 c1 96  
>Mar 26 05:55:08 www kernel: 00 0f 66 11 c1 97 a0 41  d6 49 f6 9b 
>Mar 26 05:55:08 www kernel: 
>Mar 26 05:55:08 www kernel: ath_intr: status 0x4009
>Mar 26 05:55:08 www kernel: ath_rx_tasklet
>Mar 26 05:55:08 www kernel: R (c1a53090 1a53090) 01a530c0 0d0c8020 00000000 00000c60 10d40000 69f41111 !
>Mar 26 05:55:08 www kernel: ath_intr: status 0x4009
>Mar 26 05:55:08 www kernel: ath_rx_tasklet
>Mar 26 05:55:08 www kernel: R (c1a530c0 1a530c0) 01a530f0 0d0e0020 00000000 00000c60 10240000 1dcc1911 !
>Mar 26 05:55:08 www kernel: ath_intr: status 0x4009
>Mar 26 05:55:08 www kernel: ath_rx_tasklet
>Mar 26 05:55:08 www kernel: R (c1a530f0 1a530f0) 01a53120 0037a020 00000000 00000c60 10940000 1f4c1911 !
>
>so please could you help??? why clients connection is so slow?? by the way, my speed connection to internet in ap is very good. is there any parameter i should set to get clients could use internet without problems?? and why authentication delays to much too??.
i almost forget, if i turn off my ap and after turn it on, client cann't connect any more, it must be restarted to get connection again.
do you have any idea why this behavior??
>
>thanks for your help
>
>
>
>
>
>_______________________________________________________________ 
>Who was the first boxer to beat Muhammad Ali in the professional ring?
>
>postmaster.co.uk
>http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=219



_______________________________________________________________ 
Which animal has a heart the size of a small car?

postmaster.co.uk
http://www.postmaster.co.uk/cgi-bin/meme/quiz.pl?id=4




From togg  Mon Mar 27 10:18:24 2006
From: togg (Sebastian Weitzel)
Date: Mon, 27 Mar 2006 20:18:24 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
Message-ID: <20060327201824.c1izr56m941co080@webmail.togg.de>

Are you sure about that hostap does PAE functionality for wired interfaces?
That means does hostap only allow traffic from and to authenticated  
wired stations?

AFAIK hostapd does not. It only does authentication and accounting.
Its been some month I've looked on hostap code, but in the current cvs
I couldnt find PAE support for wired.


Sebastian



Zitat von Kuba Konczyk <jakamkon at gmail.com>:

> Hello,
>
>>> If it is integrated in hostapd then the PAE support is done in user
>>> space now?
> Yes.
>>> No kernel pathces are needed?
> No kernel patches are needed.
>
> Regards
> Kuba
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
> !DSPAM:44280765161591156479586!
>
>



-- 
Sebastian Weitzel




From jt  Mon Mar 27 11:15:44 2006
From: jt (Jean Tourrilhes)
Date: Mon, 27 Mar 2006 11:15:44 -0800
Subject: tx power
Message-ID: <20060327191544.GD31590@bougret.hpl.hp.com>

Jouni Malinen wrote :
> 
> On Sun, Mar 26, 2006 at 08:42:33PM +0300, Dimitris Theoharis wrote:
> 
> > Is there a reaso why i do  not see the tx power level in iwconfig?
> > its a prism2.5 card. A Senao to be more specific. Thanks ;)
> 
> I'm not aware of a way of reading the TX power level reliably from
> Prism2/2.5/3 cards.

	WE-17 has added 'relative' Tx-Power, i.e. txpower which are
not in dBm or mW but in arbitrary/funny units. You could export the
raw value from the register and let the user deal with the rest.
	This was added precisely because you kept complaining about
that ;-)

	Have fun...

	Jean



From jakamkon  Mon Mar 27 14:38:09 2006
From: jakamkon (Kuba Konczyk)
Date: Tue, 28 Mar 2006 00:38:09 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
In-Reply-To: <2e947fbb0603271436m6ee11fdagb44af84974f2e5c9@mail.gmail.com>
References: <2e947fbb0603270737ub1118e4w228a5c6fc2c3ca33@mail.gmail.com>
	<20060327180533.4iprtsc8p63o0o80@webmail.togg.de>
	<2e947fbb0603271436m6ee11fdagb44af84974f2e5c9@mail.gmail.com>
Message-ID: <2e947fbb0603271438k67dac329s7fceeb6ab4bbab8@mail.gmail.com>

Hello Sebastian,
I was not precise.
2006/3/27, Sebastian Weitzel <togg at togg.de>:
> Are you sure about that hostap does PAE functionality for wired interfaces?
We are talking about Authenticator PAE functionality.
> That means does hostap only allow traffic from and to authenticated stations?
> AFAIK hostapd does not.
This is only a part of the Authenticator PAE functionality (IEEE Std
802.1X-2004,6.6.3).
Hostap doesn't block any traffic so every traffic is allowed.In
practice you will need bridge
software to control traffic between supplicant's ports and services
port(s) according to the outcome of the authentication exchange.I'm
currently working on integrating ebtables filtering rules with hostap
state machine.The idea is simple: for example when port is in
unauthorized state we apply filtering rules saying: 'allow only eapol
traffic between supplicant and the authenticator' and when port
changes state to authorized we extend it to: 'and forward X traffic
from supplicant to service port'.I hope this will clear the case:)

Regards
Kuba



From pocmatos  Mon Mar 27 16:02:03 2006
From: pocmatos (Paulo J. Matos)
Date: Tue, 28 Mar 2006 01:02:03 +0100
Subject: Is this the correct driver for my pci card?
Message-ID: <11b141710603271602o48591ac9h9b3577ecf3c2efd7@mail.gmail.com>

Hi all,

I have a Fujitsu Siemens Lifebook E7110, running gentoo linux, and
although I have the laptop for some years now I was never really able
to see wireless work on linux. I've been trying orinoco drivers from
2.6 kernel but without much success, although iwconfig reports a card,
it never reports signal strenght or link quality.
Here's the output of lspci:
02:0d.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)

Here's the output of iwconfig with orinoco/hermes drivers loaded:
eth2      IEEE 802.11b  ESSID:""  Nickname:"Prism  I"
          Mode:Managed  Access Point: Not-Associated   Bit Rate:11 Mb/s
          Sensitivity:1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/92  Signal level=-68 dBm  Noise level=-122 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Now I found hostap and I would like to know if someone can help me
recognize which driver I should use for this card. Thanks,

--
Paulo Jorge Matos - pocm at sat inesc-id pt
Web: http://sat.inesc-id.pt/~pocm
Computer and Software Engineering
INESC-ID - SAT Group



From togg  Mon Mar 27 23:33:46 2006
From: togg (Sebastian Weitzel)
Date: Tue, 28 Mar 2006 09:33:46 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
Message-ID: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>

Zitat von Kuba Konczyk <jakamkon at gmail.com>:

> Hello Sebastian,
> I was not precise.
> 2006/3/27, Sebastian Weitzel <togg at togg.de>:
>> Are you sure about that hostap does PAE functionality for wired interfaces?
> We are talking about Authenticator PAE functionality.

Yep correctly.

>> That means does hostap only allow traffic from and to authenticated  
>>  stations?
>> AFAIK hostapd does not.
> This is only a part of the Authenticator PAE functionality (IEEE Std
> 802.1X-2004,6.6.3).
> Hostap doesn't block any traffic so every traffic is allowed.In
> practice you will need bridge
> software to control traffic between supplicant's ports and services
> port(s) according to the outcome of the authentication exchange.I'm
> currently working on integrating ebtables filtering rules with hostap
> state machine.The idea is simple: for example when port is in
> unauthorized state we apply filtering rules saying: 'allow only eapol
> traffic between supplicant and the authenticator' and when port
> changes state to authorized we extend it to: 'and forward X traffic
> from supplicant to service port'.I hope this will clear the case:)

It's been a while I've looked in the Standard. However my former  
coworker Gunter Burchardt thought about the ebtables solution for  
implementing the access control, but he dropped this thought because  
of not beeing flexible enough. He implemented it in C instead. See the  
ML for more info.

Have a look at his code, it worked quite stable and effective for us.  
There were some problems with dropping gone clients if I remember  
correctly, but this could be fixed.
I just wanted to append the sources to this email when I noticed that  
my archive got corrupt. I will need to find an proper one later.


-- 
Sebastian Weitzel



From jakamkon  Tue Mar 28 00:28:36 2006
From: jakamkon (Kuba Konczyk)
Date: Tue, 28 Mar 2006 10:28:36 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
In-Reply-To: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
References: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
Message-ID: <2e947fbb0603280028k45e13dd8pd9dca36894e58601@mail.gmail.com>

Hello,

Do you mean this patch?
http://lists.shmoo.com/pipermail/hostap/2004-December/008719.html

Thanks.
Kuba

2006/3/28, Sebastian Weitzel <togg at togg.de>:
> Zitat von Kuba Konczyk <jakamkon at gmail.com>:
>
> > Hello Sebastian,
> > I was not precise.
> > 2006/3/27, Sebastian Weitzel <togg at togg.de>:
> >> Are you sure about that hostap does PAE functionality for wired interfaces?
> > We are talking about Authenticator PAE functionality.
>
> Yep correctly.
>
> >> That means does hostap only allow traffic from and to authenticated
> >>  stations?
> >> AFAIK hostapd does not.
> > This is only a part of the Authenticator PAE functionality (IEEE Std
> > 802.1X-2004,6.6.3).
> > Hostap doesn't block any traffic so every traffic is allowed.In
> > practice you will need bridge
> > software to control traffic between supplicant's ports and services
> > port(s) according to the outcome of the authentication exchange.I'm
> > currently working on integrating ebtables filtering rules with hostap
> > state machine.The idea is simple: for example when port is in
> > unauthorized state we apply filtering rules saying: 'allow only eapol
> > traffic between supplicant and the authenticator' and when port
> > changes state to authorized we extend it to: 'and forward X traffic
> > from supplicant to service port'.I hope this will clear the case:)
>
> It's been a while I've looked in the Standard. However my former
> coworker Gunter Burchardt thought about the ebtables solution for
> implementing the access control, but he dropped this thought because
> of not beeing flexible enough. He implemented it in C instead. See the
> ML for more info.
>
> Have a look at his code, it worked quite stable and effective for us.
> There were some problems with dropping gone clients if I remember
> correctly, but this could be fixed.
> I just wanted to append the sources to this email when I noticed that
> my archive got corrupt. I will need to find an proper one later.
>
>
> --
> Sebastian Weitzel
>



From togg  Tue Mar 28 00:36:14 2006
From: togg (Sebastian Weitzel)
Date: Tue, 28 Mar 2006 10:36:14 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
In-Reply-To: <2e947fbb0603280028k45e13dd8pd9dca36894e58601@mail.gmail.com>
References: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
	<2e947fbb0603280028k45e13dd8pd9dca36894e58601@mail.gmail.com>
Message-ID: <20060328103614.upuu2zk93hui0o80@webmail.togg.de>

Zitat von Kuba Konczyk <jakamkon at gmail.com>:

> Hello,
>
> Do you mean this patch?
> http://lists.shmoo.com/pipermail/hostap/2004-December/008719.html

Exactly, but the patch in the mail is only the hostap part. The other  
required part is a kernel module, which is not available from gunthers  
homepage anymore.


-- 
Sebastian Weitzel



From calimerot_6  Tue Mar 28 00:49:38 2006
From: calimerot_6 (Jeremy Fix)
Date: Tue, 28 Mar 2006 10:49:38 +0200
Subject: Trying to configure wpa_supplicant with ipw2200
Message-ID: <BAY112-F24CD7DCB671F1CC2DAEBCDC0D30@phx.gbl>

Hi all !

I'm trying unsuccessfully to configure on linux wpa_supplicant to access to 
my AP.

The connection works if i configure my AP with WEP .
The connection works on a Windows computer with WPA .. but not on linux.

My distribution is Mandriva 2006, i installed wpa_supplicant v0.4-4 .

I give you outpuf of some commands, hope it could help :

[root] iwlist eth2 scan
   Adress : 00:07:CB:56:4E:C7
   ESSID : "Misou"
   Protocol : IEEE 802.11bg
   Mode : Master
   Channel : 11
   Encryption Key : on
   Bit rate : 54 Mb/s
   Extra : Rates (Mb/s) : 1 2 5.5 6 9 11 12 18 24 36 48 54
   Quality : 88/100 Signal level = -41dBm
   (Unknown Wireless Token 0x8C05)
   (Unknown Wireless Token 0x8C05)
   Extra : Last Beacon : 999ms ago

My wpa_supplicant.conf :

ctrl_interface= /var/run/wpa_supplicant
ctrl_interface_group = 0
eapol_version = 1
ap_scan = 1
fast_reauth = 1
pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
network {
   ssid="Misou"
   psk="xxxxxxx"   <--- the psk defined in my AP config
   scan_ssid = 1
   proto=WPA
   key_mgmt=WPA-PSK
}

And i'm starting wpa_supplicant with :
wpa_supplicant -i eth2 -D ipw -c /etc/wpa_supplicant.conf -dd

>From the several lines of the output , i can see these following states (if 
you need the whole output, i could give it to you):

  State: DISCONNECTED->SCANNING
  [...]
  Selecting BSS from priority group 0
  0 : 00:07:cb:56:4e:c7 ssid="Misou" wpa_ie_len=28 rsn_ie_len=26 caps=0x11 
selected
  Trying to associate with 00:07:cb:56:4e:c7 (SSID="Misou" freq=0 MHz)
  Cancelling scan request
  [...]
  ioctl[IPW_IOCTL_WPA_SUPPLICANT] : Operation not supported
  State : SCANNING->ASSOCIATING
  ioctl[IPW_IOCTL_WPA_SUPPLICANT] : Operation not supported
  ioctl[IPW_IOCTL_WPA_SUPPLICANT] : Operation not supported
  Setting authentification timeout: 5 sec 0 usec
  EAPOL : External notification - EAP success = 0
  EAPOL : External notification - EAP fail = 0
  EAPOL : External notification - portControl = Auto
  RSN : Ignored PMKID candidate without preauth flag
  Wireless event : cmd=0x8b1a len=18
  Authentification with 00:00:00:00:00:00 timed out
  Added BSSID 00:00:00:00:00:00 into blacklist
  State: ASSOCIATING -> DISCONNECTED

And all along the output, i can see several "ioctl[IPW_IOCTL_WPA_SUPPLICANT] 
: Operation not supported"

Thanks a lot for your help.





From brix  Tue Mar 28 01:11:06 2006
From: brix (Henrik Brix Andersen)
Date: Tue, 28 Mar 2006 11:11:06 +0200
Subject: Trying to configure wpa_supplicant with ipw2200
In-Reply-To: <BAY112-F24CD7DCB671F1CC2DAEBCDC0D30@phx.gbl>
References: <BAY112-F24CD7DCB671F1CC2DAEBCDC0D30@phx.gbl>
Message-ID: <20060328091106.GA15985@osgiliath.brixandersen.dk>

On Tue, Mar 28, 2006 at 10:49:38AM +0200, Jeremy Fix wrote:
> ap_scan = 1
> fast_reauth = 1
> pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
> pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so

There should be no need for the above four lines given your network
configuration.

>    scan_ssid = 1

No need for this line either.

> And i'm starting wpa_supplicant with :
> wpa_supplicant -i eth2 -D ipw -c /etc/wpa_supplicant.conf -dd

If you're using linux-2.6.13 or newer you need to use '-D wext'
instead of '-D ipw'.

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


From pocmatos  Tue Mar 28 07:13:46 2006
From: pocmatos (Paulo J. Matos)
Date: Tue, 28 Mar 2006 16:13:46 +0100
Subject: Can't load PCI driver
Message-ID: <11b141710603280713l2a3bd5f5h6a089a27a6deeb07@mail.gmail.com>

Hi all,

I have kernel 2.6.15 and I when I try to load the driver:
# modprobe hostap-pci
FATAL: Error inserting hostap_pci
(/lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/wireless/hostap/hostap_pci.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

Here's dmesg output:
ieee80211_crypt: registered algorithm 'NULL'
hostap_pci: disagrees about version of symbol prism2_update_comms_qual
hostap_pci: Unknown symbol prism2_update_comms_qual
hostap_pci: disagrees about version of symbol hostap_set_hostapd
hostap_pci: Unknown symbol hostap_set_hostapd
hostap_pci: disagrees about version of symbol hostap_set_encryption
hostap_pci: Unknown symbol hostap_set_encryption
hostap_pci: disagrees about version of symbol hostap_remove_proc
hostap_pci: Unknown symbol hostap_remove_proc
hostap_pci: disagrees about version of symbol hostap_set_auth_algs
hostap_pci: Unknown symbol hostap_set_auth_algs
hostap_pci: disagrees about version of symbol hostap_get_stats
hostap_pci: Unknown symbol hostap_get_stats
hostap_pci: disagrees about version of symbol hostap_add_interface
hostap_pci: Unknown symbol hostap_add_interface
hostap_pci: disagrees about version of symbol hostap_free_data
hostap_pci: Unknown symbol hostap_free_data
hostap_pci: disagrees about version of symbol hostap_set_word
hostap_pci: Unknown symbol hostap_set_word
hostap_pci: disagrees about version of symbol hostap_info_process
hostap_pci: Unknown symbol hostap_info_process
hostap_pci: disagrees about version of symbol hostap_set_string
hostap_pci: Unknown symbol hostap_set_string
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_remove_interface
hostap_pci: Unknown symbol hostap_remove_interface
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_80211_header_parse
hostap_pci: Unknown symbol hostap_80211_header_parse
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
hostap_pci: disagrees about version of symbol hostap_check_sta_fw_version
hostap_pci: Unknown symbol hostap_check_sta_fw_version
hostap_pci: disagrees about version of symbol hostap_get_porttype
hostap_pci: Unknown symbol hostap_get_porttype
hostap_pci: disagrees about version of symbol hostap_80211_rx
hostap_pci: Unknown symbol hostap_80211_rx
hostap_pci: disagrees about version of symbol hostap_set_roaming
hostap_pci: Unknown symbol hostap_set_roaming
hostap_pci: disagrees about version of symbol hostap_handle_sta_tx_exc
hostap_pci: Unknown symbol hostap_handle_sta_tx_exc
hostap_pci: disagrees about version of symbol hostap_info_init
hostap_pci: Unknown symbol hostap_info_init
hostap_pci: disagrees about version of symbol hostap_master_start_xmit
hostap_pci: Unknown symbol hostap_master_start_xmit


Another issue... how can I upgrade my Prism2.5 firmware. I heard some
firmware was buggy.

Thanks in advance,
--
Paulo Jorge Matos - pocm at sat inesc-id pt
Web: http://sat.inesc-id.pt/~pocm
Computer and Software Engineering
INESC-ID - SAT Group



From jakamkon  Tue Mar 28 09:48:03 2006
From: jakamkon (Kuba Konczyk)
Date: Tue, 28 Mar 2006 19:48:03 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
In-Reply-To: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
References: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
Message-ID: <2e947fbb0603280948l1c9dc99blb9d06ded28fb2e5d@mail.gmail.com>

Hello Sebastian,

2006/3/28, Sebastian Weitzel <togg at togg.de>:
> It's been a while I've looked in the Standard. However my former
> coworker Gunter Burchardt thought about the ebtables solution for
> implementing the access control, but he dropped this thought because
> of not beeing flexible enough. He implemented it in C instead.
What sort of ebtables solution do you mean?On the kernel level or in
the user space?
Why ebtables solution wasn't flexible?


Regards,
Kuba



From mellon85  Tue Mar 28 10:14:15 2006
From: mellon85 (Dario Meloni)
Date: Tue, 28 Mar 2006 20:14:15 +0200
Subject: Wired network and CISCO ACS
Message-ID: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>

Hi,
Does everyone managed to authenticate on a wired ethernet network? I
am having prolbem using PEAP/MSCHAPv2 with an ACS server and I can't
manage to make it work...


From togg  Tue Mar 28 12:33:52 2006
From: togg (Sebastian Weitzel)
Date: Tue, 28 Mar 2006 22:33:52 +0200
Subject: Question about hostapd (authenticator) support for wired
	(Ethernet) clients
In-Reply-To: <2e947fbb0603280948l1c9dc99blb9d06ded28fb2e5d@mail.gmail.com>
References: <20060328093346.wpzxdylpzz8k48cs@webmail.togg.de>
	<2e947fbb0603280948l1c9dc99blb9d06ded28fb2e5d@mail.gmail.com>
Message-ID: <20060328223352.z6lsq50yvubwoog8@webmail.togg.de>

Zitat von Kuba Konczyk <jakamkon at gmail.com>:

> Hello Sebastian,
>
> 2006/3/28, Sebastian Weitzel <togg at togg.de>:
>> It's been a while I've looked in the Standard. However my former
>> coworker Gunter Burchardt thought about the ebtables solution for
>> implementing the access control, but he dropped this thought because
>> of not beeing flexible enough. He implemented it in C instead.
> What sort of ebtables solution do you mean?On the kernel level or in
> the user space?
> Why ebtables solution wasn't flexible?

No question - ebtables could be used for this task. But using ebtables  
you are required to setup a bridge. The PAE functionaliy itself is not  
dependent on bridging, so why we should introduce such dependency.
Gunters PAE kernel module uses Layer2 patch in kernel. I think this is  
a more generous approach.

-- 
Sebastian Weitzel



From wyqjnm  Tue Mar 28 12:49:41 2006
From: wyqjnm (Jacky)
Date: Wed, 29 Mar 2006 08:49:41 +1200
Subject: Wired network and CISCO ACS
In-Reply-To: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
Message-ID: <4429A165.8090807@gmail.com>

I have the same problem. I am getting "Bad request from NAS" message 
from the Cisco ACS 3.1 server.

My wpa_supplicant configuration is:
============ start
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root

eapol_version=2
ap_scan=0
network={
   ssid=""
   key_mgmt=IEEE8021X
   eap=PEAP
   identity="jnz\jacky"
   password="jacky"
   phase1="peaplabel=0 peapver=1"
   phase2="auth=MSCHAPV2"
}
======== end

And my hostapd config is:
======== start
interface=eth0
driver=wired
logger_stdout=-1
logger_stdout_level=4
debug=4
dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd
ctrl_interface_group=jacky

auth_algs=3

ieee8021x=1
eap_message=hello
use_pae_group_addr=1
eap_server=0
nas_identifier=test

auth_server_addr=192.168.2.142
auth_server_port=1812
auth_server_shared_secret=cisco
=========== end

hostapd log is
============ start
Received EAPOL packet
IEEE 802.1X: 46 bytes from 00:11:56:00:00:4a
  IEEE 802.1X: version=2 type=0 length=14
  ignoring 28 extra octets after IEEE 802.1X packet
  EAP: code=2 identifier=0 length=14 (response)
IEEE 802.1X: 00:11:56:00:00:4a BE_AUTH entering state RESPONSE
Encapsulating EAP message into a RADIUS packet
RADIUS message: code=1 (Access-Request) identifier=0 length=168
  Attribute 1 (User-Name) length=11
     Value: 'jnz\jacky'
  Attribute 4 (NAS-IP-Address) length=6
     Value: 192.168.2.41
  Attribute 32 (NAS-Identifier) length=16
     Value: 'frog.pnz.co.nz'
  Attribute 5 (NAS-Port) length=6
     Value: 0
  Attribute 30 (Called-Station-Id) length=20
     Value: '00-0D-61-11-7F-8A:'
  Attribute 31 (Calling-Station-Id) length=19
     Value: '00-11-56-00-00-4A'
  Attribute 12 (Framed-MTU) length=6
     Value: 1400
  Attribute 61 (NAS-Port-Type) length=6
     Value: 19
  Attribute 77 (Connect-Info) length=24
     Value: 'CONNECT 11Mbps 802.11b'
  Attribute 79 (EAP-Message) length=16
     Value: 02 00 00 0e 01 6a 6e 7a 5c 6a 61 63 6b 79
  Attribute 80 (Message-Authenticator) length=18
     Value: eb 0f ae db 4b 6a 1d 5d 66 c3 99 da f0 b5 a8 27
IEEE 802.1X: 00:11:56:00:00:4a REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:11:56:00:00:4a REAUTH_TIMER entering state INITIALIZE
RADIUS message: code=3 (Access-Reject) identifier=0 length=50
  Attribute 18 (?Unknown?) length=12
  Attribute 80 (Message-Authenticator) length=18
     Value: f2 6f 9f 3a a3 c8 85 7c 66 6f 62 ad 01 37 80 23
RADIUS packet matching with station 00:11:56:00:00:4a
eth0: STA 00:11:56:00:00:4a IEEE 802.1X: could not extract EAP-Message 
from RADIUS message
IEEE 802.1X: 00:11:56:00:00:4a BE_AUTH entering state IGNORE
IEEE 802.1X: 00:11:56:00:00:4a BE_AUTH entering state FAIL
IEEE 802.1X: Sending canned EAP packet FAILURE to 00:11:56:00:00:4a 
(identifier 1)
IEEE 802.1X: 00:11:56:00:00:4a REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:11:56:00:00:4a AUTH_PAE entering state HELD
eth0: STA 00:11:56:00:00:4a IEEE 802.1X: authentication failed
============ end

wpa_supplicant log is
============ start
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=5):
    68 65 6c 6c 6f                                    hello
EAP: using real identity - hexdump_ascii(len=9):
    6a 6e 7a 5c 6a 61 63 6b 79                        jnz\jacky
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=18): 02 00 00 0e 02 00 00 0e 01 6a 6e 7a 5c 6a 61 
63 6b 79
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:0d:61:11:7f:8a
RX EAPOL - hexdump(len=46): 02 00 00 04 04 01 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-Failure
EAP: Workaround for unexpected identifier field in EAP Success: reqId=1 
lastId=0 (these are supposed to be same)
EAP: EAP entering state FAILURE
CTRL-EVENT-EAP-FAILURE EAP authentication failed
============ end





From ruzsinszky.attila  Tue Mar 28 13:19:48 2006
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Tue, 28 Mar 2006 23:19:48 +0200
Subject: wpa_gui for SuSE 9.3?
Message-ID: <f637dd860603281319l2e6e6f74m@mail.gmail.com>

Hi,

I'm looking for wpa_gui binary under SuSE 9.3.
Anyone has it?

TIA,
Ruzsi



From kosta1000  Tue Mar 28 14:22:24 2006
From: kosta1000 (Kosta Rojdestvensky)
Date: Tue, 28 Mar 2006 15:22:24 -0700
Subject: Newbie wpa_supplicant question
Message-ID: <b96e70cc0603281422u415eb0a1w3aaff8d6eda5690f@mail.gmail.com>

Hello,

I'm trying to connect to the corporate wireless network in Ubuntu
Breezy without full knowledge of the server parameters. (My local
network support guys are useless...)
In windows it works under the Funk Odyssey client software.
I was trying several parameters in wpa_supplicant.conf and looks like
I got connected (kind of).
At least I got successful messages in the debug output of supplicant (v0.4.5) :
...
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
wpa_driver_ipw_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
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:40:96:52:0a:84 completed (reauth)
EAPOL: SUPP_PAE entering state AUTHENTICATED
...
and output from the wpa_cli looks like
# wpa_cli status
Selected interface 'eth1'
bssid=00:40:96:49:2a:6a
ssid=NULL
pairwise_cipher=NONE
group_cipher=NONE
key_mgmt=IEEE 802.1X (no WPA)
wpa_state=COMPLETED
Supplicant PAE state=AUTHENTICATED
suppPortStatus=Authorized
EAP state=SUCCESS
selectedMethod=25 (EAP-PEAP)
EAP TLS cipher=AES256-SHA
EAP-PEAPv1 Phase2 method=GTC
...

my wpa_supplicant.conf looks like:

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
network={
       scan_ssid=1
        ssid="NULL"
        key_mgmt=IEEE8021X
        proto=WPA2
        eap=PEAP
        identity="aaaaaaa"
        password="xxxxxxx"
        phase1="peaplabel=0"
        phase2="auth=MSCHAPv2"
        priority=1
}


The problem is that there is no response from the DHCP server at this point.
Am I missing something and the interface is not really connected?
and
    "State: ASSOCIATED -> COMPLETED "
    "CTRL-EVENT-CONNECTED-Connection to 00:40:96:52:0a:84 completed"
messages do not mean 'Really connected' ?

I also tried two different cards (ipw2200, and ath) with the same result...
The same time my collegue just mentioned successful connection on Mac OS
using standard mac software...

Any help or directions are very
appreciated.


Thanks,

Kosta Rozdestvensky



From proski  Tue Mar 28 14:30:46 2006
From: proski (Pavel Roskin)
Date: Tue, 28 Mar 2006 17:30:46 -0500
Subject: wpa_gui for SuSE 9.3?
In-Reply-To: <f637dd860603281319l2e6e6f74m@mail.gmail.com>
References: <f637dd860603281319l2e6e6f74m@mail.gmail.com>
Message-ID: <1143585046.22613.1.camel@dv>

On Tue, 2006-03-28 at 23:19 +0200, Ruzsinszky Attila wrote:
> Hi,
> 
> I'm looking for wpa_gui binary under SuSE 9.3.
> Anyone has it?

Soliciting binaries on a public mailing list is somewhat risky.

Maybe you could describe why you cannot compile wpa_gui?  Do you have
gcc, g++ and qt-devel installed?  Then it's just a matter of running
qmake and make.

-- 
Regards,
Pavel Roskin




From wyqjnm  Tue Mar 28 14:56:00 2006
From: wyqjnm (Jacky)
Date: Wed, 29 Mar 2006 10:56:00 +1200
Subject: Wired network and CISCO ACS
In-Reply-To: <4429A165.8090807@gmail.com>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<4429A165.8090807@gmail.com>
Message-ID: <4429BF00.4070109@gmail.com>

It seems to work now. I actually wrongly configured the ACS to use a 
Radius (Ascend). Now I changed it Radius (IETF).

Jacky wrote:

>I have the same problem. I am getting "Bad request from NAS" message 
>from the Cisco ACS 3.1 server.
>  
>




From foreveruni  Tue Mar 28 15:28:36 2006
From: foreveruni (=?ISO-8859-1?Q?Jo=E3o_Mamede?=)
Date: Wed, 29 Mar 2006 00:28:36 +0100
Subject: wpa_gui compilation
Message-ID: <4429C6A4.7060008@clix.pt>

guys I'm trying to compile wpa_gui in my desktop everything compiles 
fine glibc version:2.3.6 gcc/g++ 4.0.3  qt 3.3.5
in my laptop I have glibc 2.3.6 gcc/g++ 4.0.3 qt(tried 3.3.5 and 3.3.6)
and I have this compilation error:
I've tried with make wpa_gui too in wpa_supplicant-0.4.7(tried 0.5.2 and 
0.5.1 versions too :( nothing)

root at SIV:/usr/src/wpa_supplicant-0.4.7/wpa_gui# make
g++ -c -pipe -Wall -W -O -march=pentium4 -mmmx -mfpmath=sse -msse -msse2 
-pipe  
-DQT_NO_DEBUG -DQT_SHARED -DQT_THREAD_SUPPORT 
-I/usr/share/qt/mkspecs/default -I
. -I.. -I/usr/include/qt -I.ui/ -I. -I.moc/ -o .obj/wpagui.o .ui/wpagui.cpp
.ui/../wpagui.ui.h: In member function 'void WpaGui::destroy()':
.ui/../wpagui.ui.h:80: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h: In member function 'virtual void WpaGui::parse_argv()':
.ui/../wpagui.ui.h:92: error: 'getopt' was not declared in this scope
.ui/../wpagui.ui.h:97: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h:98: error: 'optarg' was not declared in this scope
.ui/../wpagui.ui.h: In member function 'int 
WpaGui::openCtrlConnection(const cha
r*)':
.ui/../wpagui.ui.h:116: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h:126: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h:146: error: 'malloc' was not declared in this scope
.ui/../wpagui.ui.h:167: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h:171: error: 'free' was not declared in this scope
.ui/../wpagui.ui.h: In member function 'virtual void 
WpaGui::processMsg(char*)':
.ui/../wpagui.ui.h:518: error: 'atoi' was not declared in this scope
make: *** [.obj/wpagui.o] Error 1

Hope you guys help me.
Tnx
Joao Mamede



From jkmaline  Tue Mar 28 19:16:17 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Mar 2006 19:16:17 -0800
Subject: Wired network and CISCO ACS
In-Reply-To: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
Message-ID: <20060329031617.GA9394@jm.kir.nu>

On Tue, Mar 28, 2006 at 08:14:15PM +0200, Dario Meloni wrote:

> Does everyone managed to authenticate on a wired ethernet network? I

Yes.

> am having prolbem using PEAP/MSCHAPv2 with an ACS server and I can't
> manage to make it work...

You need to provide more details of your setup and debug logs etc. for
someone to be able to help with this..

-- 
Jouni Malinen                                            PGP id EFC895FA



From wyqjnm  Tue Mar 28 19:18:44 2006
From: wyqjnm (Jacky)
Date: Wed, 29 Mar 2006 15:18:44 +1200
Subject: Machine authentication
Message-ID: <4429FC94.2020500@gmail.com>

Hi,

Does wpa_supplicant supports machine authentication? If so, how to 
configure it?

More specifically, in Cisco's ACS, there is a setting called "Enable 
machine access restrictions". Does wpa_supplicant support that?

Thanks,

Jacky



From jkmaline  Tue Mar 28 19:22:15 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Mar 2006 19:22:15 -0800
Subject: Newbie wpa_supplicant question
In-Reply-To: <b96e70cc0603281422u415eb0a1w3aaff8d6eda5690f@mail.gmail.com>
References: <b96e70cc0603281422u415eb0a1w3aaff8d6eda5690f@mail.gmail.com>
Message-ID: <20060329032215.GB9394@jm.kir.nu>

On Tue, Mar 28, 2006 at 03:22:24PM -0700, Kosta Rojdestvensky wrote:

> EAPOL: using part of EAP keying material data encryption key -
> hexdump(len=13): [REMOVED]EAPOL: Setting dynamic WEP key: unicast
> keyidx 3 len 13
> wpa_driver_ipw_set_key: alg=WEP key_idx=3 set_tx=128 seq_len=0 key_len=13

Using non-zero key index for unicast keys is against number of standards
and there are drivers that do not support this. I do not remember
whether ipw2x00 handles this or not, but this could explain why the data
connection does not work.

> Am I missing something and the interface is not really connected?
> and
>     "State: ASSOCIATED -> COMPLETED "
>     "CTRL-EVENT-CONNECTED-Connection to 00:40:96:52:0a:84 completed"
> messages do not mean 'Really connected' ?

As far as wpa_supplicant is concerned, everything is done at this point
and the authentication and key distribution was completed successfully.

> I also tried two different cards (ipw2200, and ath) with the same result...

Based on my notes, this kind of configuration has worked with NDIS
drivers (wpa_supplicant on WinXP), Host AP driver, and madwifi (though,
quite an old version). I do not remember having tested this with
ipw2200.

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Tue Mar 28 19:25:19 2006
From: proski (Pavel Roskin)
Date: Tue, 28 Mar 2006 22:25:19 -0500
Subject: [PATCH] Allow compiling wpa_gui-qt4 for Qt 3.x
Message-ID: <1143602719.25546.13.camel@dv>

Hello!

This patch allows to compile wpa_gui-qt4 for Qt 3.x.  Thus, the same
source can be used for both Qt 3.x and Qt 4.x.  I think this patch could
be applied, then files from wpa_gui-qt4 could be copied over wpa_gui,
and then wpa_gui-qt4 could be removed.  I don't think wpa_gui will use
any Qt4 features any time soon, so it's better to have a single source.

Since QT_VERSION is only defined in qmake for Qt 4.x, it's sufficient to
check that it's not empty.  Better suggestions are welcome.

The patched source has been successfully compiled for Qt 3.3.5 and
4.1.1.

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

--- wpa_supplicant/wpa_gui-qt4/wpa_gui.pro
+++ wpa_supplicant/wpa_gui-qt4/wpa_gui.pro
@@ -34,10 +34,14 @@
   OBJECTS_DIR = .obj
 }
 
+qtver = $$[QT_VERSION]
+isEmpty( qtver ) {
+	message(Compiling for Qt 3.x)
+	DEFINES += Q3ListViewItem=QListViewItem
+} else {
+	message(Compiling for Qt $$qtver)
+	QT += qt3support 
+	CONFIG += uic3
+}
 
 
-#The following line was inserted by qt3to4
-QT += qt3support 
-#The following line was inserted by qt3to4
-CONFIG += uic3
-
--- wpa_supplicant/wpa_gui-qt4/wpamsg.h
+++ wpa_supplicant/wpa_gui-qt4/wpamsg.h
@@ -1,8 +1,16 @@
 #ifndef WPAMSG_H
 #define WPAMSG_H
 
+class WpaMsg;
+
+#if QT_VERSION >= 0x040000
 #include <QDateTime>
 #include <QLinkedList>
+typedef QLinkedList<WpaMsg> WpaMsgList;
+#else
+#include <qdatetime.h>
+typedef QValueList<WpaMsg> WpaMsgList;
+#endif
 
 class WpaMsg {
 public:
@@ -23,6 +31,4 @@
     QDateTime timestamp;
 };
 
-typedef QLinkedList<WpaMsg> WpaMsgList;
-
 #endif /* WPAMSG_H */


-- 
Regards,
Pavel Roskin




From jkmaline  Tue Mar 28 19:26:36 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Mar 2006 19:26:36 -0800
Subject: Machine authentication
In-Reply-To: <4429FC94.2020500@gmail.com>
References: <4429FC94.2020500@gmail.com>
Message-ID: <20060329032636.GC9394@jm.kir.nu>

On Wed, Mar 29, 2006 at 03:18:44PM +1200, Jacky wrote:

> Does wpa_supplicant supports machine authentication? If so, how to 
> configure it?

Which EAP method are you using? Machine authentication is usually just
meaning that a different set of credentials (e.g., private key and
certificate) is used, but otherwise the authentication works as the
normal user authentication. Machine authentication would then be used
when no one is logged on to the system (e.g., to set up network
connection for the user authentication to happen over network). Most of
this is outside the scope of wpa_supplicant, i.e., one would need to
configure the system to update wpa_supplicant configuration based on
user logon.

> More specifically, in Cisco's ACS, there is a setting called "Enable 
> machine access restrictions". Does wpa_supplicant support that?

Could you please give more details on what this setting is supposed to
do? Or at least provide ACS version number and location of that setting
in its configuration UI.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Mar 28 19:33:48 2006
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Mar 2006 19:33:48 -0800
Subject: [PATCH] Allow compiling wpa_gui-qt4 for Qt 3.x
In-Reply-To: <1143602719.25546.13.camel@dv>
References: <1143602719.25546.13.camel@dv>
Message-ID: <20060329033348.GD9394@jm.kir.nu>

On Tue, Mar 28, 2006 at 10:25:19PM -0500, Pavel Roskin wrote:

> This patch allows to compile wpa_gui-qt4 for Qt 3.x.  Thus, the same
> source can be used for both Qt 3.x and Qt 4.x.  I think this patch could
> be applied, then files from wpa_gui-qt4 could be copied over wpa_gui,
> and then wpa_gui-qt4 could be removed.  I don't think wpa_gui will use
> any Qt4 features any time soon, so it's better to have a single source.

Interesting.. I had not consider this for two reasons: I was actually
planning on getting rid of Qt3 compat stuff completely and was expecting
this to require more changes.

Qt3 compat library increases size requirements for Qt4 GUIs quite a lot
and because of that it would really be nice to get rid of that..
However, this would also mean that your patch would not be of much use
since Qt3 would be unable to handle the end result easily.

In most cases, I would certainly prefer to have just one source code
tree, but this may require some more work to allow proper Qt4-only build
to work with the same tree. For now, I'll add this patch to a list of
things to consider and don't apply it before getting bit better
understanding on what really needs to happen with the Qt4 version of
wpa_gui. If nothing else, it might be worthwhile to move the current
wpa_gui-qt4 version and this patch into wpa_gui and continue working on
Qt4-only version on wpa_gui-qt4..

-- 
Jouni Malinen                                            PGP id EFC895FA



From proski  Tue Mar 28 21:06:51 2006
From: proski (Pavel Roskin)
Date: Wed, 29 Mar 2006 00:06:51 -0500
Subject: wpa_gui compilation
In-Reply-To: <4429C6A4.7060008@clix.pt>
References: <4429C6A4.7060008@clix.pt>
Message-ID: <1143608811.25546.15.camel@dv>

Hello!

On Wed, 2006-03-29 at 00:28 +0100, Jo?o Mamede wrote:
> guys I'm trying to compile wpa_gui in my desktop everything compiles 
> fine glibc version:2.3.6 gcc/g++ 4.0.3  qt 3.3.5
> in my laptop I have glibc 2.3.6 gcc/g++ 4.0.3 qt(tried 3.3.5 and 3.3.6)
> and I have this compilation error:
[skip]
> .ui/../wpagui.ui.h: In member function 'void WpaGui::destroy()':
> .ui/../wpagui.ui.h:80: error: 'free' was not declared in this scope

I guess we should add more include files to *.ui.h, and not just for
Windows.  Please try this patch:

--- wpa_supplicant/wpa_gui/networkconfig.ui.h
+++ wpa_supplicant/wpa_gui/networkconfig.ui.h
@@ -10,6 +10,7 @@
 ** destructor.
 *****************************************************************************/
 
+#include <stdlib.h>
 
 enum {
     AUTH_NONE = 0,
--- wpa_supplicant/wpa_gui/userdatarequest.ui.h
+++ wpa_supplicant/wpa_gui/userdatarequest.ui.h
@@ -10,6 +10,8 @@
 ** destructor.
 *****************************************************************************/
 
+#include <stdlib.h>
+
 int UserDataRequest::setParams(WpaGui *_wpagui, const char *reqMsg)
 {
     char *tmp, *pos, *pos2;
--- wpa_supplicant/wpa_gui/wpagui.ui.h
+++ wpa_supplicant/wpa_gui/wpagui.ui.h
@@ -11,10 +11,9 @@
 *****************************************************************************/
 
 
-#ifdef __MINGW32__
 /* Need to get getopt() */
 #include <unistd.h>
-#endif
+#include <stdlib.h>
 
 
 void WpaGui::init()


-- 
Regards,
Pavel Roskin




From mellon85  Tue Mar 28 22:42:25 2006
From: mellon85 (Dario Meloni)
Date: Wed, 29 Mar 2006 08:42:25 +0200
Subject: Wired network and CISCO ACS
In-Reply-To: <20060329031617.GA9394@jm.kir.nu>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<20060329031617.GA9394@jm.kir.nu>
Message-ID: <3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>

== Configuration
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
fast_reauth=1
network={
	eapol_flags=1
	key_mgmt=IEEE8021X
	eap=PEAP
	phase1="peaplabel=0 peapver=1"
	phase2="auth=MSCHAPV2"
	identity="72836"
	password="..."
	client_cert="/usr/local/etc/cert/CertWiFi.pem"
}


wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.con -Dwired -ieth0 -d

=== output
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=2
ap_scan=0
fast_reauth=1
Priority group 0
   id=0 ssid=''
Initializing interface (2) 'eth0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wired_init: Added multicast membership with packet socket
Own MAC address: 00:0b:5d:4d:fd:d7
Setting scan request: 0 sec 100000 usec
Added interface eth0
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
Associated to a new BSS: BSSID=01:80:c2:00:00:03
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=Auto
Associated with 01:80:c2:00:00:03
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
RX EAPOL from 00:0d:28:a6:bd:0a
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
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=6):
     63 37 32 38 33 36                                 72836
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
RX EAPOL from 00:0d:28:a6:bd:0a
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=73
EAP: EAP entering state GET_METHOD
EAP: initialize selected EAP method (25, PEAP)
EAP-PEAP: Forced PEAP version 1
EAP-PEAP: Phase2 EAP types - hexdump(len=1): 1a
OpenSSL: tls_connection_client_cert - SSL_use_certificate_file (DER)
failed error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
OpenSSL: pending error: error:0D07803A:asn1 encoding
routines:ASN1_ITEM_EX_D2I:nested asn1 error
OpenSSL: pending error: error:140C800D:SSL
routines:SSL_use_certificate_file:ASN1 lib
OpenSSL: SSL_use_certificate_file (PEM) --> OK
CTRL-EVENT-EAP-METHOD EAP method 25 (PEAP) selected
EAP: EAP entering state METHOD
SSL: Received packet(len=6) - Flags 0x21
EAP-PEAP: Start (server ver=1, own ver=1)
EAP-PEAP: Using PEAP version 1
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: 101 bytes pending from ssl_out
SSL: 101 bytes left to be sent out (of total 101 bytes)
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE


From rob.davis  Wed Mar 29 00:09:13 2006
From: rob.davis (Rob Davis)
Date: Wed, 29 Mar 2006 10:09:13 +0200
Subject: problem with marginal connections in mesh network.
Message-ID: <442A40A9.9070404@virgin.net>

Hello.

We're running a mesh network across several miles in Northern Italy
using AODV and hostap.  We have recently seen a new surge in new signals
which have nothing to do with the mesh appearing on the same channels as
we're using.  The problem with these signals is they are pulling the
rate down of our gateways.  Is there a way to block specific mac
addresses from trying to connect using hostap?

dmesg brings up thousands of these..


handle_ap_item - addr3(BSSID)=00:a0:f8:ca:16:27 not own MAC
handle_ap_item - addr3(BSSID)=00:02:6f:33:ba:cd not own MAC
handle_ap_item - addr3(BSSID)=00:a0:f8:ca:16:27 not own MAC


We have asked if the would be able to change channel, but they are
unable to at the moment as they would have to call in a technician.. (Or
so they say..)
-- 
Latest news on http://www.streetcredo.org.uk/rob

Rob Davis



From hammadnaveed  Tue Mar 28 23:24:56 2006
From: hammadnaveed (Hammad)
Date: Wed, 29 Mar 2006 07:24:56 +0000 (UTC)
Subject: cannot authenticate using LEAP 
Message-ID: <loom.20060329T091653-299@post.gmane.org>

Hi,

I am using madwifi-ng-r1475 and hostapd 0.4.8. It is working with PSK but with
leap it doesnot complete authentication. below is what i get

Configuration file: myconf.conf
Configure bridge br0 for EAPOL traffic.
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:40:96:a3:8b:8f and ssid 'test'
ath0: RADIUS Authentication server 192.168.0.42:1812
ath0: RADIUS Accounting server 192.168.0.42:1813
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0x2
madwifi_configure_wpa: key management algorithms=0x1
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x1
madwifi_set_iface_flags: dev_up=1
madwifi_set_privacy: enabled=1
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 38 08 f3 e0 bd 70 16 43 51 ed b2 6f 39 47 49 f8 26 d9 a9
bc cc e4 a2 33 8b 54 ed b7 56 38 2f 55
GTK - hexdump(len=32): 2f 59 5a 4d ad 8b a2 2d 88 cf 0c 17 3d 30 1d 2e a4 21 64
54 09 ee 10 b8 2b 9f cb 68 a3 13 f0 e1
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
ath0: RADIUS Sending RADIUS message to accounting server
RADIUS message: code=4 (Accounting-Request) identifier=0 length=84
   Attribute 40 (Acct-Status-Type) length=6
      Value: 7
   Attribute 45 (Acct-Authentic) length=6
      Value: 1
   Attribute 4 (NAS-IP-Address) length=6
      Value: 192.168.0.224
   Attribute 32 (NAS-Identifier) length=16
      Value: 'ap.example.com'
   Attribute 30 (Called-Station-Id) length=24
      Value: '00-40-96-A3-8B-8F:test'
   Attribute 49 (Acct-Terminate-Cause) length=6
      Value: 11
ath0: RADIUS Next RADIUS client retransmit in 3 seconds

Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
l2_packet_receive - recvfrom: Network is down
l2_packet_receive - recvfrom: Network is down
ath0: RADIUS Received 20 bytes from RADIUS server
ath0: RADIUS Received RADIUS message
RADIUS message: code=5 (Accounting-Response) identifier=0 length=20
ath0: STA 00:00:00:00:00:00 RADIUS: Received RADIUS packet matched with a pendin
g request, round trip time 0.02 sec
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:11:95:b9:18:03 IEEE 802.11: associated
  New STA
No WPA/RSN information element for station!?
ath0: WPA rekeying GTK
WPA: group state machine entering state SETKEYS
GMK - hexdump(len=32): 38 08 f3 e0 bd 70 16 43 51 ed b2 6f 39 47 49 f8 26 d9 a9
bc cc e4 a2 33 8b 54 ed b7 56 38 2f 55
GTK - hexdump(len=32): 43 2e 3b 89 b9 cf 09 ba db ed 5c 7b 27 62 5f 7b 29 12 97
37 a1 f8 c1 c7 89 60 d7 31 7e 8a 1e 80
WPA: group state machine entering state SETKEYSDONE
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2
  Sending disassociation info to STA 00:11:95:b9:18:03
madwifi_sta_disassoc: addr=00:11:95:b9:18:03 reason_code=4
ioctl[unknown???]: Invalid argument
  Sending disassociation info to STA 00:11:95:b9:18:03
madwifi_sta_disassoc: addr=00:11:95:b9:18:03 reason_code=4
ioctl[unknown???]: Invalid argument
ath0: STA 00:11:95:b9:18:03 IEEE 802.11: disassociated due to inactivity
  Sending deauthentication info to STA 00:11:95:b9:18:03
madwifi_sta_deauth: addr=00:11:95:b9:18:03 reason_code=2
ath0: STA 00:11:95:b9:18:03 IEEE 802.11: deauthenticated due to inactivity
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:11:95:b9:18:03 IEEE 802.11: deassociated
Wireless event: cmd=0x8c03 len=20


my hostapd.conf file is given below :

interface=ath0

bridge=br0

driver=madwifi

logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2

debug=3

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

ctrl_interface_group=0

ssid=test

auth_algs=1

ieee8021x=1

eapol_key_index_workaround=1

eap_server=0

own_ip_addr=192.168.0.224

nas_identifier=ap.example.com

auth_server_addr=192.168.0.42
auth_server_port=1812
auth_server_shared_secret=testing123

acct_server_addr=192.168.0.42
acct_server_port=1813
acct_server_shared_secret=testing123

wpa=1

wpa_key_mgmt=WPA-EAP

wpa_pairwise=TKIP

wpa_group_rekey=300

wpa_gmk_rekey=640


I cant figure out the problem........
Thanx in advance for your time........

Hammad 




From jar  Wed Mar 29 06:21:27 2006
From: jar (Jar)
Date: Wed, 29 Mar 2006 17:21:27 +0300
Subject: Hostapd.accept file format question
Message-ID: <442A97E7.7090902@pcuf.fi>

Hello

hostapd.accept example file is like this:

# List of MAC addresses that are allowed to authenticate (IEEE 802.11)
# with the AP.
00:11:22:33:44:55
00:66:77:88:99:aa
00:00:22:33:44:55

Does it (hostapd.accept file parsing) work right if I add some extra 
fields, like:

# List of MAC addresses that are allowed to authenticate (IEEE 802.11)
# with the AP.
00:11:22:33:44:55 10.1.1.1 5000 5000 # Comment 1
00:66:77:88:99:aa 10.1.1.2 5001 5001 # Comment 2
00:00:22:33:44:55 10.1.1.3 5002 5002 # Comment 3

-- 
Best Regards, Jar



From jkmaline  Wed Mar 29 06:28:01 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Mar 2006 06:28:01 -0800
Subject: cannot authenticate using LEAP
In-Reply-To: <loom.20060329T091653-299@post.gmane.org>
References: <loom.20060329T091653-299@post.gmane.org>
Message-ID: <20060329142801.GB9377@jm.kir.nu>

On Wed, Mar 29, 2006 at 07:24:56AM +0000, Hammad wrote:

> I am using madwifi-ng-r1475 and hostapd 0.4.8. It is working with PSK but with
> leap it doesnot complete authentication. below is what i get

Unlike other EAP methods, LEAP is an odd beast.. It does not follow the
EAP RFC and would require quite a bit of changes to get it working. In
other words, it is not supported in hostapd. Taken into account the
security issues identified in LEAP, I have no plans of adding support
for it either.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 29 06:34:12 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Mar 2006 06:34:12 -0800
Subject: Wired network and CISCO ACS
In-Reply-To: <3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<20060329031617.GA9394@jm.kir.nu>
	<3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>
Message-ID: <20060329143412.GC9377@jm.kir.nu>

On Wed, Mar 29, 2006 at 08:42:25AM +0200, Dario Meloni wrote:

> == Configuration

...

> 	eapol_flags=1

Wired connection is unlikely to distribute encryption keys so
eapol_flags should be set to 0 or removed complete.

> EAP-PEAP: Start (server ver=1, own ver=1)
> EAP-PEAP: Using PEAP version 1

The first PEAP message from the authentication server is received
successfully.. 

> 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: 101 bytes pending from ssl_out
> SSL: 101 bytes left to be sent out (of total 101 bytes)

And this is the ClientHello messsage from the supplicant..

> EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
> EAP: EAP entering state SEND_RESPONSE
> EAP: EAP entering state IDLE
> EAPOL: SUPP_BE entering state RESPONSE
> EAPOL: txSuppRsp
> EAPOL: SUPP_BE entering state RECEIVE

However, the server does not seem to answer to it. Since you are using
Cisco ACS, I would recommend testing with include_tls_length=1 added to
the phase1 parameter. Some versions of ACS seem to require that TLS
Message Length is in the messages even if they are not fragmented.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mellon85  Wed Mar 29 07:03:14 2006
From: mellon85 (Dario Meloni)
Date: Wed, 29 Mar 2006 17:03:14 +0200
Subject: Wired network and CISCO ACS
In-Reply-To: <20060329143412.GC9377@jm.kir.nu>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<20060329031617.GA9394@jm.kir.nu>
	<3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>
	<20060329143412.GC9377@jm.kir.nu>
Message-ID: <3e1f5f250603290703i4472b7bdub11fec59bc96a666@mail.gmail.com>

2006/3/29, Jouni Malinen <jkmaline at cc.hut.fi>:
> On Wed, Mar 29, 2006 at 08:42:25AM +0200, Dario Meloni wrote:
>
> > == Configuration
>
> ...
>
> >       eapol_flags=1
>
> Wired connection is unlikely to distribute encryption keys so
> eapol_flags should be set to 0 or removed complete.

I read on the wpa_supplicant website to use the 1.

>
> > EAP-PEAP: Start (server ver=1, own ver=1)
> > EAP-PEAP: Using PEAP version 1
>
> The first PEAP message from the authentication server is received
> successfully..
>
> > 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: 101 bytes pending from ssl_out
> > SSL: 101 bytes left to be sent out (of total 101 bytes)
>
> And this is the ClientHello messsage from the supplicant..
>
> > EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
> > EAP: EAP entering state SEND_RESPONSE
> > EAP: EAP entering state IDLE
> > EAPOL: SUPP_BE entering state RESPONSE
> > EAPOL: txSuppRsp
> > EAPOL: SUPP_BE entering state RECEIVE
>
> However, the server does not seem to answer to it. Since you are using
> Cisco ACS, I would recommend testing with include_tls_length=1 added to
> the phase1 parameter. Some versions of ACS seem to require that TLS
> Message Length is in the messages even if they are not fragmented.
>

Making the 2 changes you said it works. thanks a lot for the help


From kosta1000  Wed Mar 29 09:08:24 2006
From: kosta1000 (Kosta Rojdestvensky)
Date: Wed, 29 Mar 2006 10:08:24 -0700
Subject: Newbie wpa_supplicant question
In-Reply-To: <20060329032215.GB9394@jm.kir.nu>
References: <b96e70cc0603281422u415eb0a1w3aaff8d6eda5690f@mail.gmail.com>
	<20060329032215.GB9394@jm.kir.nu>
Message-ID: <b96e70cc0603290908u1e2fad9fkcb78fd90d772d4ac@mail.gmail.com>

I'm very appreciate your prompt response,  Jouni,

I got one persistent error message from the wpa_supplicant.

When submitting wpa_cli status command, wpa_supplicant
reports in  debug output:

EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: startWhen --> 0
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS
ioctl[SIOCGIFADDR]: Cannot assign requested address
EAPOL: authWhile --> 0

Does it confirms your previous notes about ipw2200?

Do you think trying NDIS wrapper driver could make sense?
(Currently I have intel ipw2200 embeded and Atheros madwifi pcmci
cards available).

Do I have any other options besides dual booting with windows?


Thanks,

Kosta

On 3/28/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Tue, Mar 28, 2006 at 03:22:24PM -0700, Kosta Rojdestvensky wrote:
>
> > EAPOL: using part of EAP keying material data encryption key -
> > hexdump(len=13): [REMOVED]EAPOL: Setting dynamic WEP key: unicast
> > keyidx 3 len 13
> > wpa_driver_ipw_set_key: alg=WEP key_idx=3 set_tx=128 seq_len=0 key_len=13
>
> Using non-zero key index for unicast keys is against number of standards
> and there are drivers that do not support this. I do not remember
> whether ipw2x00 handles this or not, but this could explain why the data
> connection does not work.
>
> > Am I missing something and the interface is not really connected?
> > and
> >     "State: ASSOCIATED -> COMPLETED "
> >     "CTRL-EVENT-CONNECTED-Connection to 00:40:96:52:0a:84 completed"
> > messages do not mean 'Really connected' ?
>
> As far as wpa_supplicant is concerned, everything is done at this point
> and the authentication and key distribution was completed successfully.
>
> > I also tried two different cards (ipw2200, and ath) with the same result...
>
> Based on my notes, this kind of configuration has worked with NDIS
> drivers (wpa_supplicant on WinXP), Host AP driver, and madwifi (though,
> quite an old version). I do not remember having tested this with
> ipw2200.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From stefan  Wed Mar 29 10:44:51 2006
From: stefan (Stefan Rompf)
Date: Wed, 29 Mar 2006 20:44:51 +0200
Subject: PATCH RFC: wpa_supplicant influencing device operstate
In-Reply-To: <200603040004.55477.stefan@loplof.de>
References: <200603040004.55477.stefan@loplof.de>
Message-ID: <200603292044.51399.stefan@loplof.de>

Hi Jouni,

did you have time to look at this stuff? I've just added support for the other 
drivers that depend on wext (tested with madwifi) and then upgraded the patch 
for 0.5.2

Stefan

> Hi,
>
> some weeks ago, there has been a quite heated discussion on linux-netdev
> about extending functionality of netif_carrier_on()/off(). In the end, a
> patch written by me has been applied for 2.6.17. For an overview, see the
> documentation at http://www.flamewarmaster.de/software/operstates.txt . The
> patch itself (applies to 2.6.14+) can be found on this site too. Main point
> concerning this list is that it allows an userspace supplicant to signal
> the kernel when the interface is ready for user traffic after
> authentication, and afterwards, kernel notifies other programs via the
> existing IFF_RUNNING interface.
>
> The quagga routing daemon, vrrpd and my new dhcp client
> (http://www.flamewarmaster.de/software/dhcpclient/) can act on these
> messages.
>
> I have attached a patch against wpa_supplicant 0.5.1 to this mail that
> implements signalling functionality in the WEXT driver. Note that I haven't
> tested how this affects drivers that rely on WEXT functionality - this is a
> very first version.
>
> With this extension, I can start wpa_supplicant and my DHCP client in
> parallel. Whenever the supplicant has completed association, and WPA
> authentication if needed, the DHCP client will automatically update the
> interface IP configuration. Together with a graphical wpa_cli (will try
> wpa_gui), this increases usability of wireless LANs a lot. In the long run,
> I'd like this feature to be added to wpa_supplicant.
>
> Thoughts?
>
> Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-0.5.2.diff
Type: text/x-diff
Size: 13704 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060329/72daec46/attachment.diff 


From wyqjnm  Wed Mar 29 13:42:11 2006
From: wyqjnm (Jacky)
Date: Thu, 30 Mar 2006 09:42:11 +1200
Subject: Machine authentication
In-Reply-To: <20060329032636.GC9394@jm.kir.nu>
References: <4429FC94.2020500@gmail.com> <20060329032636.GC9394@jm.kir.nu>
Message-ID: <442AFF33.1000307@gmail.com>

Thanks for your response.

>Which EAP method are you using?
>
What EAP method should I use for machine authentication?
Actually the real question should be:
What Windows XP is using during the machine authentication?
I have:
1. enabled XP's 802.11x authentication in the network settings.
2. Used "Smart Card or other Certificate"
3. enabled "Authenticate as computer when computer information is available"
4. enabled "Use a certificate on this computer"
5. enabled "Use simple certificate selection (Recommended)"

>>More specifically, in Cisco's ACS, there is a setting called "Enable 
>>machine access restrictions". Does wpa_supplicant support that?
>>    
>>
>
>Could you please give more details on what this setting is supposed to
>do? Or at least provide ACS version number and location of that setting
>in its configuration UI.
>
>  
>

I am usgin ACS v3.1.  The setting is in External User Database -> 
Windows Database -> Configure -> Windows EAP Settings -> Machine 
Authentication
checked three options:
1. Enable PEAP machine authentication
2. Enable TLS machine authentication
EAP-TLS and PEAP machine authentication prefix: host/
3. Enable machine access restriction
    Aging time: 12
    Group map for successful user authentication without machine 
authentication: No Access

I have got an error for ACS when I enabled the machine access restriction :
"External DB user access denied (Machine Access Restriction).

The documentation for the above options show below
==========
Windows EAP Settings

The Windows EAP Settings table controls various options for EAP 
authentication.
Enable password change inside PEAP or EAP-FAST --
If you want to enable password changes with PEAP(EAP-MSCHAPv2), 
PEAP(EAP-GTC), and EAP-FAST(EAP-GTC), select this checkbox.

EAP-TLS Strip Domain Name --
If you want Cisco Secure ACS to remove the domain name from a username 
derived from the Subject Alternative Name (SAN) field in an end-user 
certificate, select this checkbox.

Enable PEAP machine authentication --
If you want to enable machine authentication using machine name and 
password with PEAP(EAP-MSCHAPv2), select this checkbox.

Enable EAP-TLS machine authentication --
If you want to enable machine authentication using machine certificates 
with EAP-TLS, select this checkbox.

EAP-TLS and PEAP machine authentication name prefix --
you want Cisco Secure ACS to substitute a different string of characters 
for the string "host/" at the beginning of any machine name being 
authenticated by PEAP(EAP-MSCHAPv2) or EAP-TLS, type the string in this box.

Enable machine access restrictions --
To use machine authentication as a condition for user authorization, 
select this check box. Microsoft PEAP and EAP-TLS users accessing the 
network with a computer that failed machine authentication are 
authenticated normally but receive only the authorizations defined by 
the group mapping list, below.

Aging time (hours) --
The number of hours that Cisco Secure ACS caches a successful machine 
authentication. For as long as successful machine authentication is 
retained in the cache, the machine access restrictions feature can use 
it to determine whether to limit a user to the group specified in the 
group mapping list, below.

Group map for successful user authentication without machine 
authentication --
When the machine access restrictions feature is enabled, this list 
specifies the user group whose authorizations are applied to an EAP-TLS 
or Microsoft PEAP user who passes authentication but uses a computer 
that failed machine authentication.
=========



From rafa  Wed Mar 29 14:03:15 2006
From: rafa (Rafa Marin Lopez)
Date: Wed, 29 Mar 2006 17:03:15 -0500
Subject: wpa_supplicant scanning + association time
Message-ID: <442B0423.8090400@dif.um.es>

Hi all

I noticed, that starting wpa_supplicant, there is a big delay (around 3 
seconds) before starting EAP-TLS authentication.

Do anybody know why it is happening?.

Thanks in advance.

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




From ifreebiz  Wed Mar 29 14:39:04 2006
From: ifreebiz (ifreebiz at fastmail.fm)
Date: Wed, 29 Mar 2006 14:39:04 -0800
Subject: wpa_supplicant executable size/memory size
Message-ID: <1143671944.20562.257861259@webmail.messagingengine.com>

Hi, 

I need to adapt wpa_supplicant for an embedded system. I need to
estimate the resouces it needs. I am wondering how much is the size of
the wpa_supplicant executable on your system? How much memory it uses on
your system?  I just want to get some rough idea. Any suggestions?

Thanks very much, Andrew.
-- 
  
  ifreebiz at fastmail.fm

-- 
http://www.fastmail.fm - mmm... Fastmail...




From bryan  Wed Mar 29 15:42:23 2006
From: bryan (Bryan Kadzban)
Date: Wed, 29 Mar 2006 18:42:23 -0500
Subject: Machine authentication
In-Reply-To: <442AFF33.1000307@gmail.com>
References: <4429FC94.2020500@gmail.com> <20060329032636.GC9394@jm.kir.nu>
	<442AFF33.1000307@gmail.com>
Message-ID: <442B1B5F.4000403@kadzban.is-a-geek.net>

Jacky wrote:
> 
>> Which EAP method are you using?
> 
> What EAP method should I use for machine authentication?

Doesn't matter, anything will work (assuming you can get at the
credentials).

> Actually the real question should be: What Windows XP is using during
> the machine authentication?

That depends.  It doesn't choose any one authentication type, and in
fact without a registry hack, it won't authenticate as a computer at
all, until you reboot it.

> I have:
> 1. enabled XP's 802.11x authentication in the network settings.
> 2. Used "Smart Card or other Certificate"

It's therefore using EAP-TLS, with a certificate stored in the machine's
MY store.  (Probably anyway.)  wpa_supplicant can also use this cert.

> 3. enabled "Authenticate as computer when computer information is
> available"

That doesn't make it do machine auth all the time, only at boot.  To get
it to do that all the time, you have to refer to this article:

http://technet2.microsoft.com/WindowsServer/en/Library/8e74974f-c951-48ce-8235-02f4ed8e74921033.mspx

and go to the "802.11 Wireless Registry Entries" section.  There you'll
find an AuthMode registry value that needs to be set under
HKLM\Software\Microsoft\EAPOL\Parameters\General\Global, to control what
kind of authentication the OS's supplicant will do.

(Note that this is not required for wpa_supplicant, only for the XP
supplicant.  My point is that without this change, XP will not use
machine credentials by default, unless it's currently booting.
Subsequent roams, reassociations, and reauthentications will use user
credentials without this change.  And just hitting OK in the "add a new
preferred network" dialog will also use user credentials, until you
reboot.)

At this point, you probably need to figure out whether your machine even
has a certificate issued to it.  There is no built-in certificates MMC
snap-in, but you can add the certificates console to an MMC session.
Start->Run->type in "mmc" (no quotes)->OK.  Then go to "add/remove a
snap-in", choose "add" (or something like that; I'm going from memory at
this point), select "certificates", hit OK, make sure you select "this
machine", then hit OK or close until you're back at the cert snap-in.

Then expand Personal.  You should have a Certificates entry under that,
containing your machine's cert.  If not, then go through the Add/Remove
thingy again, and select "my user account" instead of "this machine",
and you should see a cert in the newly-added Personal bucket.

In either case, you'll have to configure wpa_supplicant's network block
like this:

network={
	ssid="whatever"
	key_mgmt=WPA-EAP
	proto=WPA2   # or WPA, I'm not sure what version you need
	eap=TLS
	private_key=cert://xxxxxxx
}

You have to replace the xxxxxxx with some string that's part of the CN
of the cert that you want to use (either the machine one or the user
one).  wpa_supplicant will look for a cert with a CN having this string
as a substring, first in your personal store, then in the machine store
-- so make sure you have a valid substring in there, otherwise it might
use the wrong cert.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060329/04b2b647/attachment.pgp 


From jkmaline  Wed Mar 29 19:12:28 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Mar 2006 19:12:28 -0800
Subject: wpa_supplicant executable size/memory size
In-Reply-To: <1143671944.20562.257861259@webmail.messagingengine.com>
References: <1143671944.20562.257861259@webmail.messagingengine.com>
Message-ID: <20060330031227.GA9368@jm.kir.nu>

On Wed, Mar 29, 2006 at 02:39:04PM -0800, ifreebiz at fastmail.fm wrote:

> I need to adapt wpa_supplicant for an embedded system. I need to
> estimate the resouces it needs. I am wondering how much is the size of
> the wpa_supplicant executable on your system? How much memory it uses on
> your system?  I just want to get some rough idea. Any suggestions?

I would suggest building it for your target system with the
configuration that includes only the features you need and then taking a
look at the end result..

This depends a lot on the build-time configuration (mainly on what EAP
methods are included). Minimal build with WPA/WPA2-Personal is
somewhere around 50 kB and largest build is likely around 250 kB or so.
If TLS is used, TLS library is needed on top of this and if the system
does not include it anyway, this could add around 700-1000 kB if OpenSSL
is used (again, depending on configuration).

As far as dynamic memory use is concerned, that is also depending
greatly on the used configuration. Very rough estimate would be around
10-20 kB for WPA/WPA2-Personal and maybe around 50-150 kB for
WPA/WPA2-Enterprise with TLS. No guarantees on correctness for these
values, though ;-).
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 29 19:16:58 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Mar 2006 19:16:58 -0800
Subject: wpa_supplicant scanning + association time
In-Reply-To: <442B0423.8090400@dif.um.es>
References: <442B0423.8090400@dif.um.es>
Message-ID: <20060330031658.GB9368@jm.kir.nu>

On Wed, Mar 29, 2006 at 05:03:15PM -0500, Rafa Marin Lopez wrote:

> I noticed, that starting wpa_supplicant, there is a big delay (around 3 
> seconds) before starting EAP-TLS authentication.

Which version of wpa_supplicant are you using and with what driver? Do
you use ap_scan=1 or ap_scan=2 mode? wpa_supplicant 0.5.2 completes
WPA-PSK authentication within half a second or so from startup with
madwifi-ng in my test setup. With ap_scan=1, most of the time is likely
spent waiting for the driver to scan for APs unless the results are
already available when wpa_supplicant is started. ap_scan=2 may be quite
a bit faster if the driver supports it.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Mar 29 19:24:42 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Mar 2006 19:24:42 -0800
Subject: Wired network and CISCO ACS
In-Reply-To: <3e1f5f250603290703i4472b7bdub11fec59bc96a666@mail.gmail.com>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<20060329031617.GA9394@jm.kir.nu>
	<3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>
	<20060329143412.GC9377@jm.kir.nu>
	<3e1f5f250603290703i4472b7bdub11fec59bc96a666@mail.gmail.com>
Message-ID: <20060330032442.GC9368@jm.kir.nu>

On Wed, Mar 29, 2006 at 05:03:14PM +0200, Dario Meloni wrote:
> 2006/3/29, Jouni Malinen <jkmaline at cc.hut.fi>:
> > On Wed, Mar 29, 2006 at 08:42:25AM +0200, Dario Meloni wrote:

> > >       eapol_flags=1
> >
> > Wired connection is unlikely to distribute encryption keys so
> > eapol_flags should be set to 0 or removed complete.
> 
> I read on the wpa_supplicant website to use the 1.

Can you please be more specific on where this information is so that it
can be fixed? At least the example wpa_supplicant.conf file mentions
that ap_scan must be set to be 0 for wired authentication.

-- 
Jouni Malinen                                            PGP id EFC895FA



From hammadnaveed  Wed Mar 29 20:11:57 2006
From: hammadnaveed (hammad naveed)
Date: Wed, 29 Mar 2006 20:11:57 -0800 (PST)
Subject: No subject
Message-ID: <20060330041157.92076.qmail@web53209.mail.yahoo.com>

set authenticate DAMN11
set delivery off

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



From wyqjnm  Wed Mar 29 20:37:45 2006
From: wyqjnm (Jacky)
Date: Thu, 30 Mar 2006 16:37:45 +1200
Subject: Machine authentication
In-Reply-To: <442B1B5F.4000403@kadzban.is-a-geek.net>
References: <4429FC94.2020500@gmail.com> <20060329032636.GC9394@jm.kir.nu>
	<442AFF33.1000307@gmail.com>
	<442B1B5F.4000403@kadzban.is-a-geek.net>
Message-ID: <442B6099.5030406@gmail.com>

In either case, you'll have to configure wpa_supplicant's network block

>like this:
>
>network={
>	ssid="whatever"
>	key_mgmt=WPA-EAP
>	proto=WPA2   # or WPA, I'm not sure what version you need
>	eap=TLS
>	private_key=cert://xxxxxxx
>}
>
>  
>
Thanks, in fact I am using wpa_supplicant on Linux.  I manage to find 
the current user's certifcate in the cert MMC.
However, when I try to export the certificate, I can not export the 
private key. Also what format should I export it to (DER/Base-64/.P7B)?

Another question is: can I actually find out what's the machine account 
password and can I use the machine account password instead?

Jacky



From siretart  Thu Mar 30 00:21:15 2006
From: siretart (Reinhard Tartler)
Date: Thu, 30 Mar 2006 08:21:15 +0000 (UTC)
Subject: [patch] leaking passwords in the debug log
Message-ID: <slrne2n57r.im4.siretart@hermes.olymp.tauware.de>

In ubuntu, there was a patch submitted to a bug which causes
wpasupplicant to leak passwords. You can see the bug here:

https://launchpad.net/bugs/37070

The patch in question can be seen here:

http://librarian.launchpad.net/1896628/40_ctrl_iface_hide_keys.dpatch

What do you think about this patch? Should it be included in the next
release?

Greetings,
	Reinhard





From mellon85  Thu Mar 30 01:30:19 2006
From: mellon85 (Dario Meloni)
Date: Thu, 30 Mar 2006 11:30:19 +0200
Subject: Wired network and CISCO ACS
In-Reply-To: <20060330032442.GC9368@jm.kir.nu>
References: <3e1f5f250603281014j63193d97v8f9ca02d3860f85b@mail.gmail.com>
	<20060329031617.GA9394@jm.kir.nu>
	<3e1f5f250603282242s2eecf2bfl8de58073b7c2961a@mail.gmail.com>
	<20060329143412.GC9377@jm.kir.nu>
	<3e1f5f250603290703i4472b7bdub11fec59bc96a666@mail.gmail.com>
	<20060330032442.GC9368@jm.kir.nu>
Message-ID: <3e1f5f250603300130j65f29621j55f95fa6df1f88a4@mail.gmail.com>

I'm sorry but I can't find where i read it... maybe i misread.

2006/3/30, Jouni Malinen <jkmaline at cc.hut.fi>:
> On Wed, Mar 29, 2006 at 05:03:14PM +0200, Dario Meloni wrote:
> > 2006/3/29, Jouni Malinen <jkmaline at cc.hut.fi>:
> > > On Wed, Mar 29, 2006 at 08:42:25AM +0200, Dario Meloni wrote:
>
> > > >       eapol_flags=1
> > >
> > > Wired connection is unlikely to distribute encryption keys so
> > > eapol_flags should be set to 0 or removed complete.
> >
> > I read on the wpa_supplicant website to use the 1.
>
> Can you please be more specific on where this information is so that it
> can be fixed? At least the example wpa_supplicant.conf file mentions
> that ap_scan must be set to be 0 for wired authentication.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>


From bryan  Thu Mar 30 04:06:51 2006
From: bryan (Bryan Kadzban)
Date: Thu, 30 Mar 2006 07:06:51 -0500
Subject: Machine authentication
In-Reply-To: <442B6099.5030406@gmail.com>
References: <4429FC94.2020500@gmail.com>
	<20060329032636.GC9394@jm.kir.nu>	<442AFF33.1000307@gmail.com>	<442B1B5F.4000403@kadzban.is-a-geek.net>
	<442B6099.5030406@gmail.com>
Message-ID: <442BC9DB.7040705@kadzban.is-a-geek.net>

Jacky wrote:
> Thanks, in fact I am using wpa_supplicant on Linux.

That might be a bit of a problem...

> I manage to find the current user's certifcate in the cert MMC. 
> However, when I try to export the certificate, I can not export the 
> private key.

There's a flag that you can set when generating or importing a cert that
tells Windows that it can't export the private key.  AFAICT there's no
way around that either (although I'm not a cryptanalyst; the encryption
on the file is likely pretty weak, given Microsoft's history in this area).

In theory, you could replace advapi32.dll with a version that unsets the
"don't allow exporting" flag when either CryptGenKey or CryptImportKey
are called, but I could never get this to work (it always resulted in an
access violation).  But I tried a "wrapper" DLL, so it may be that you
could do something similar to what the unofficial IE jscript.dll patch
does (patch the file in place somehow).  You'd definitely want to undo
the patch later though.

Or maybe someone else has an idea?

> Also what format should I export it to (DER/Base-64/.P7B)?

If you want to export the private key, then your only option is PKCS12
format, whatever extension that is.  The other two will only allow you
to export the cert itself (at least, on 2000 that's the case, I'm not
sure about XP).

> Another question is: can I actually find out what's the machine
> account password and can I use the machine account password instead?

If you're a member of the domain, then this password changes from time
to time.  You could install a password-change-sniffer DLL on the DC and
get the password from it (in fact we have something similar set up on
our domain for our user passwords, so that we can unlock users' desktops
when they aren't there, without killing all their programs), but if you
don't handle it securely, it's a pretty gaping hole in the network's
security.

If your user has a cert (you seemed to imply it above, though I don't
know if I read that right), then could you perhaps use your user's
password?  That might be simpler.  (With the Windows supplicant, you
wouldn't be able to get at that until you logged on.  But if you know
the password, you can set Linux up to use it regardless of who's logged
on, as long as it lets you on the network.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060330/1ab24439/attachment.pgp 


From leonidavdeev  Thu Mar 30 04:30:54 2006
From: leonidavdeev (Leonid Avdeev)
Date: Thu, 30 Mar 2006 14:30:54 +0200
Subject: PAE module for WIRED auth NEEDED
Message-ID: <44c9b20b0603300430l52727c48ld3736df289dfc49c@mail.gmail.com>

Hello,

PAE module for wired authentication created by Gunter Burchardt was
once available vie this link
http://www.informatik.uni-rostock.de/~gbur/pae/pae-0.0.2.tar.gz.

Now the link is broken. Does someone have the archive and can mail it to me?

Thanks.



From ramalhais  Thu Mar 30 04:58:07 2006
From: ramalhais (Pedro Ramalhais)
Date: Thu, 30 Mar 2006 13:58:07 +0100
Subject: PAE module for WIRED auth NEEDED
In-Reply-To: <44c9b20b0603300430l52727c48ld3736df289dfc49c@mail.gmail.com>
References: <44c9b20b0603300430l52727c48ld3736df289dfc49c@mail.gmail.com>
Message-ID: <442BD5DF.70401@serrado.net>

Leonid Avdeev wrote:
> Hello,
> 
> PAE module for wired authentication created by Gunter Burchardt was
> once available vie this link
> http://www.informatik.uni-rostock.de/~gbur/pae/pae-0.0.2.tar.gz.
> 
> Now the link is broken. Does someone have the archive and can mail it to me?
> 
> Thanks.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

I'm not sure this is the same thing:

http://sourceforge.net/projects/pae
http://prdownloads.sourceforge.net/pae/pae-0.0.3.tar.bz2?download

-- 
Pedro Ramalhais



From jkmaline  Thu Mar 30 06:21:01 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 30 Mar 2006 06:21:01 -0800
Subject: [patch] leaking passwords in the debug log
In-Reply-To: <slrne2n57r.im4.siretart@hermes.olymp.tauware.de>
References: <slrne2n57r.im4.siretart@hermes.olymp.tauware.de>
Message-ID: <20060330142100.GA9385@jm.kir.nu>

On Thu, Mar 30, 2006 at 08:21:15AM +0000, Reinhard Tartler wrote:

> In ubuntu, there was a patch submitted to a bug which causes
> wpasupplicant to leak passwords. You can see the bug here:

> https://launchpad.net/bugs/37070

> http://librarian.launchpad.net/1896628/40_ctrl_iface_hide_keys.dpatch
> 
> What do you think about this patch? Should it be included in the next
> release?

I think I already fixed this in wpa_supplicant 0.5.2 a week or so ago.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Thu Mar 30 07:40:09 2006
From: dcbw (Dan Williams)
Date: Thu, 30 Mar 2006 10:40:09 -0500
Subject: [patch] leaking passwords in the debug log
In-Reply-To: <20060330142100.GA9385@jm.kir.nu>
References: <slrne2n57r.im4.siretart@hermes.olymp.tauware.de>
	<20060330142100.GA9385@jm.kir.nu>
Message-ID: <1143733209.2091.0.camel@localhost.localdomain>

On Thu, 2006-03-30 at 06:21 -0800, Jouni Malinen wrote:
> On Thu, Mar 30, 2006 at 08:21:15AM +0000, Reinhard Tartler wrote:
> 
> > In ubuntu, there was a patch submitted to a bug which causes
> > wpasupplicant to leak passwords. You can see the bug here:
> 
> > https://launchpad.net/bugs/37070
> 
> > http://librarian.launchpad.net/1896628/40_ctrl_iface_hide_keys.dpatch
> > 
> > What do you think about this patch? Should it be included in the next
> > release?
> 
> I think I already fixed this in wpa_supplicant 0.5.2 a week or so ago.

Can we get it applied to STABLE too?  Everyone is currently shipping
0.4.8 (at least SUSE, Fedora, and a few others are).

Dan





From chip  Thu Mar 30 08:53:58 2006
From: chip (Chip Salzenberg)
Date: Thu, 30 Mar 2006 08:53:58 -0800
Subject: [patch] hostap driver in 2.6.16 kernel doesn't want to handle D-Link
	DWL-650 any more
Message-ID: <20060330165358.GA20806@tytlal.topaz.cx>

The hostap driver in the 2.6.15 kernel worked fine with my D-Link DWL-650
card.  However, when I upgraded to 2.6.16, the hostap_cs module did not load
any more when the card was inserted.  Apparently the hostap_cs module now
has a more restrictive device list -- too restrictive.  The list now
excludes my DWL-650, which is:

  Socket 0 Device 0:      [hostap_cs]             (bus ID: 0.0)
          Configuration:  state: on
          Product Name:   Link DWL-650 11Mbps WLAN Card Version 01.02 
          Identification: manf_id: 0x0156 card_id: 0x0002
                          function: 6 (network)
                          prod_id(1): --- (---)
                          prod_id(2): "Link DWL-650 11Mbps WLAN Card" (0xb6f1b0ab)
                          prod_id(3): "Version 01.02" (0x4b74baa0)
                          prod_id(4): --- (---)

This (obvious but perhaps overzelous) patch works for me:

--- hostap_cs.c.dpkg-dist	2006-03-19 21:53:29.000000000 -0800
+++ hostap_cs.c	2006-03-29 23:29:19.000000000 -0800
@@ -891,8 +891,12 @@
 	PCMCIA_DEVICE_MANF_CARD(0xd601, 0x0005),
 	PCMCIA_DEVICE_MANF_CARD(0xd601, 0x0010),
+#if 0
 	PCMCIA_DEVICE_MANF_CARD_PROD_ID1(0x0156, 0x0002, "INTERSIL",
 					 0x74c5e40d),
 	PCMCIA_DEVICE_MANF_CARD_PROD_ID1(0x0156, 0x0002, "Intersil",
 					 0x4b801a17),
+#else
+	PCMCIA_DEVICE_MANF_CARD(0x0156, 0x0002),
+#endif
 	PCMCIA_MFC_DEVICE_PROD_ID12(0, "SanDisk", "ConnectPlus",
 				    0x7a954bd9, 0x74be00c6),

-- 
Chip Salzenberg <chip at pobox.com>



From proski  Thu Mar 30 09:03:45 2006
From: proski (Pavel Roskin)
Date: Thu, 30 Mar 2006 12:03:45 -0500
Subject: [patch] hostap driver in 2.6.16 kernel doesn't want to handle
	D-Link DWL-650 any more
In-Reply-To: <20060330165358.GA20806@tytlal.topaz.cx>
References: <20060330165358.GA20806@tytlal.topaz.cx>
Message-ID: <1143738225.29308.5.camel@dv>

Hello!

On Thu, 2006-03-30 at 08:53 -0800, Chip Salzenberg wrote:
> The hostap driver in the 2.6.15 kernel worked fine with my D-Link DWL-650
> card.  However, when I upgraded to 2.6.16, the hostap_cs module did not load
> any more when the card was inserted.  Apparently the hostap_cs module now
> has a more restrictive device list -- too restrictive.  The list now
> excludes my DWL-650, which is:
> 
>   Socket 0 Device 0:      [hostap_cs]             (bus ID: 0.0)
>           Configuration:  state: on
>           Product Name:   Link DWL-650 11Mbps WLAN Card Version 01.02 
>           Identification: manf_id: 0x0156 card_id: 0x0002
>                           function: 6 (network)
>                           prod_id(1): --- (---)
>                           prod_id(2): "Link DWL-650 11Mbps WLAN Card" (0xb6f1b0ab)

This is a bug in the PCMCIA subsystem!  The first line should be "D",
not "".  I have already talked to another person who has this problem
and I have the CIS dump.  "D" is there, but the kernel cannot find it.
The userspace parser in dump_cis prints "D".

I have already posted this problem ti the PCMCIA list, and I'm planning
to work on it myself.  I'm even planning to flash one of my cards with
that CIS to reproduce the problem.

> +#else
> +	PCMCIA_DEVICE_MANF_CARD(0x0156, 0x0002),

Please don't apply this patch.  It doesn't address the real problem.
Matching numeric ID because the vendor strings cannot be parsed properly
is not a solution, it's a bad hack.

-- 
Regards,
Pavel Roskin




From wyqjnm  Thu Mar 30 12:04:16 2006
From: wyqjnm (Jacky)
Date: Fri, 31 Mar 2006 08:04:16 +1200
Subject: Machine authentication
In-Reply-To: <442BC9DB.7040705@kadzban.is-a-geek.net>
References: <4429FC94.2020500@gmail.com>
	<20060329032636.GC9394@jm.kir.nu>	<442AFF33.1000307@gmail.com>	<442B1B5F.4000403@kadzban.is-a-geek.net>
	<442B6099.5030406@gmail.com>
	<442BC9DB.7040705@kadzban.is-a-geek.net>
Message-ID: <442C39C0.7040902@gmail.com>


>If your user has a cert (you seemed to imply it above, though I don't
>know if I read that right), then could you perhaps use your user's
>password?  That might be simpler.  (With the Windows supplicant, you
>wouldn't be able to get at that until you logged on.  But if you know
>the password, you can set Linux up to use it regardless of who's logged
>on, as long as it lets you on the network.)
>  
>
My ultimal goal is to get machine authenticate working. I have included 
Cisco ACS's "machine access restriction" option explaination in my 
second email on this thread. I don't know how exactly it works, but I 
guess ACS is detecting ( or Active Directory is telling ACS) that an 
authentication is a machine authentication. ACS will allow certain 
operation only if machine authentication is successful (for example 
allow user authentication only if machine authenticated). Therefore 
using the user's cert or password is not help in this case.
I am also making assumption that if I set the identity to 
"host/mychinename" then ACS(or AD) will think this is a machine 
authentication (since I can see XP sending this as username in Ethereal 
log). Then I hope if I use the machine cert or machine password with the 
hostname as identity it will make ACS believe it is machine authentication.

Jacky



From bryan  Thu Mar 30 15:16:32 2006
From: bryan (Bryan Kadzban)
Date: Thu, 30 Mar 2006 18:16:32 -0500
Subject: Machine authentication
In-Reply-To: <442C39C0.7040902@gmail.com>
References: <4429FC94.2020500@gmail.com>
	<20060329032636.GC9394@jm.kir.nu>	<442AFF33.1000307@gmail.com>	<442B1B5F.4000403@kadzban.is-a-geek.net>
	<442B6099.5030406@gmail.com>
	<442BC9DB.7040705@kadzban.is-a-geek.net>
	<442C39C0.7040902@gmail.com>
Message-ID: <442C66D0.8070908@kadzban.is-a-geek.net>

Jacky wrote:
> ACS will allow certain operation only if machine authentication is
> successful (for example allow user authentication only if machine
> authenticated).

Oh.  Well, that's going to be hard to duplicate, then, considering the
nature of the machine password (AD and the machine know it, but AFAIK
you can't get it out of either of them once it's been changed) and the
machine cert (not being flagged as exportable).

Unless someone can figure out a patch to advapi32.dll so that the "don't
allow exporting this key" flag doesn't get set in the actual cert key,
that is.  (If someone can, I'd like to see it too.)  Maybe I'll look
into it, but I don't know a ton about Windows assembly, so it may not
work out.

> I am also making assumption that if I set the identity to 
> "host/mychinename" then ACS(or AD) will think this is a machine 
> authentication (since I can see XP sending this as username in
> Ethereal log).

That's probably true; that's likely the only way it knows, actually.
(Depending on your domain, it may be possible to authenticate as
machinename$ instead of host/machine.dns.name, but I'd use the host/
version instead if possible.)

> Then I hope if I use the machine cert or machine password with the 
> hostname as identity it will make ACS believe it is machine
> authentication.

I would guess that this is what happens on the ACS side.  (However, I
don't know how ACS maps that machine authentication to a user when the
user tries to log on.  Maybe it's just the MAC address that the AP adds
(the RADIUS calling station ID attribute).  That might be fragile though.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20060330/912f2bbd/attachment.pgp 


From jkmaline  Thu Mar 30 18:58:57 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 30 Mar 2006 18:58:57 -0800
Subject: [patch] leaking passwords in the debug log
In-Reply-To: <1143733209.2091.0.camel@localhost.localdomain>
References: <slrne2n57r.im4.siretart@hermes.olymp.tauware.de>
	<20060330142100.GA9385@jm.kir.nu>
	<1143733209.2091.0.camel@localhost.localdomain>
Message-ID: <20060331025856.GA9395@jm.kir.nu>

On Thu, Mar 30, 2006 at 10:40:09AM -0500, Dan Williams wrote:

> Can we get it applied to STABLE too?  Everyone is currently shipping
> 0.4.8 (at least SUSE, Fedora, and a few others are).

Yes, I merged it into 0.4.x branch earlier today, so it will be in
0.4.9.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ryan.castellucci  Fri Mar 31 15:55:53 2006
From: ryan.castellucci (Ryan Castellucci)
Date: Fri, 31 Mar 2006 15:55:53 -0800
Subject: hostapd "Could not connect to kernel driver" with madwifi-ng
In-Reply-To: <118619310603271457v34401645k8c4d116c8628b530@mail.gmail.com>
References: <118619310603271457v34401645k8c4d116c8628b530@mail.gmail.com>
Message-ID: <118619310603311555h746dee4ft59e85fe0d583f73c@mail.gmail.com>

I'm using hostapd 0.5.2 compiled with madwifi-ng r1475, and I get the
following when I attempt ot that hostapd:

# hostapd -dddd /rw/etc/hostapd-ath0.conf
Configuration file: /rw/etc/hostapd-ath0.conf
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:02:6f:20:fa:82 and ssid 'test-ath0'
SIOCGIWRANGE: WE(compiled)=19 WE(source)=13 enc_capa=0x0
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
ioctl[IEEE80211_IOCTL_SETMLME]: Invalid argument
Could not connect to kernel driver.
Deauthenticate all stations
madwifi_set_iface_flags: dev_up=0

I know I've got hostapd compiled against the madwifi drivers i'm
using, and it is installed corectly as far as i can tell.

my config file

interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ssid=test-ath0
eapol_key_index_workaround=0
eap_server=0
own_ip_addr=127.0.0.1

strace output

# strace hostapd -dddd /rw/etc/hostapd-ath0.conf
execve("/usr/local/bin/hostapd", ["hostapd", "-dddd", "/rw/etc/hostapd-ath0.conf
"], [/* 13 vars */]) = 0
uname({sys="Linux", node="hotspot", ...}) = 0
brk(0)                                  = 0x808b000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
xb7fa3000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=6275, ...}) = 0
old_mmap(NULL, 6275, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fa1000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/i586/libssl.so.0.9.7", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\205\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=182192, ...}) = 0
old_mmap(NULL, 182960, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7f74000
old_mmap(0xb7f9e000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x2a
000) = 0xb7f9e000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/i586/libcrypto.so.0.9.7", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\300\2"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=952744, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
xb7f73000
old_mmap(NULL, 970744, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7e86000
old_mmap(0xb7f5e000, 73728, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xd7
000) = 0xb7f5e000
old_mmap(0xb7f70000, 12280, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANON
YMOUS, -1, 0) = 0xb7f70000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360^\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1244688, ...}) = 0
old_mmap(NULL, 1254852, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7d53000
old_mmap(0xb7e7b000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x12
7000) = 0xb7e7b000
old_mmap(0xb7e83000, 9668, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONY
MOUS, -1, 0) = 0xb7e83000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libdl.so.2", O_RDONLY)       = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\34\0\000"..., 512) = 5
12
fstat64(3, {st_mode=S_IFREG|0644, st_size=9872, ...}) = 0
old_mmap(NULL, 8632, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7d50000
old_mmap(0xb7d52000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x200
0) = 0xb7d52000
close(3)                                = 0
munmap(0xb7fa1000, 6275)                = 0
brk(0)                                  = 0x808b000
brk(0x80ac000)                          = 0x80ac000
brk(0)                                  = 0x80ac000
rt_sigaction(SIGHUP, {0x804d440, [HUP], SA_RESTART}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {0x804d440, [INT], SA_RESTART}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTERM, {0x804d440, [TERM], SA_RESTART}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGUSR1, {0x804d440, [USR1], SA_RESTART}, {SIG_DFL}, 8) = 0
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 64), ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B19200 opost isig icanon echo ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
xb7fa2000
write(1, "Configuration file: /rw/etc/host"..., 46Configuration file: /rw/etc/ho
stapd-ath0.conf
) = 46
open("/rw/etc/hostapd-ath0.conf", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=10893, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
xb7fa1000
read(3, "##### hostapd configuration file"..., 4096) = 4096
read(3, "and\n# concatenating these into o"..., 4096) = 4096
read(3, "is can be either entered as a 25"..., 4096) = 2701
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0xb7fa1000, 4096)                = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
ioctl(3, SIOCGIFINDEX, {8, "ath0"})     = 0
socket(PF_PACKET, SOCK_RAW, 36488)      = 4
ioctl(4, SIOCGIFINDEX, {8, "ath0"})     = 0
bind(4, {sa_family=AF_PACKET, proto=0x888e, if8, pkttype=PACKET_HOST, addr(0)={0
, }, 20) = 0
ioctl(4, SIOCGIFHWADDR, 0xbfab9420)     = 0
ioctl(3, SIOCSIWMODE, 0xbfab9490)       = 0
write(1, "madwifi_set_iface_flags: dev_up="..., 34madwifi_set_iface_flags: dev_u
p=0
) = 34
ioctl(3, SIOCGIFFLAGS, 0xbfab9420)      = 0
ioctl(3, SIOCSIFFLAGS, 0xbfab9420)      = 0
ioctl(3, SIOCGIWESSID, 0xbfab94b0)      = 0
write(1, "Using interface ath0 with hwaddr"..., 72Using interface ath0 with hwad
dr 00:02:6f:20:fa:82 and ssid 'test-ath0'
) = 72
gettimeofday({1143500214, 434222}, NULL) = 0
time(NULL)                              = 1143500214
ioctl(3, SIOCGIWRANGE, 0xbfab9480)      = 0
write(1, "SIOCGIWRANGE: WE(compiled)=19 WE"..., 57SIOCGIWRANGE: WE(compiled)=19
WE(source)=13 enc_capa=0x0
) = 57
socket(PF_NETLINK, SOCK_RAW, 0)         = 5
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000001}, 12) = 0
write(1, "Flushing old station entries\n", 29Flushing old station entries
) = 29
write(1, "madwifi_sta_deauth: addr=ff:ff:f"..., 57madwifi_sta_deauth: addr=ff:ff
:ff:ff:ff:ff reason_code=3
) = 57
ioctl(3, 0x8bf0, 0xbfab9400)            = -1 EINVAL (Invalid argument)
dup(2)                                  = 6
fcntl64(6, F_GETFL)                     = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat64(6, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 64), ...}) = 0
ioctl(6, SNDCTL_TMR_TIMEBASE or TCGETS, {B19200 opost isig icanon echo ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0
xb7fa1000
_llseek(6, 0, 0xbfab9280, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(6, "ioctl[IEEE80211_IOCTL_SETMLME]: "..., 49ioctl[IEEE80211_IOCTL_SETMLME]
: Invalid argument
) = 49
close(6)                                = 0
munmap(0xb7fa1000, 4096)                = 0
write(1, "Could not connect to kernel driv"..., 36Could not connect to kernel dr
iver.
) = 36
write(1, "Deauthenticate all stations\n", 28Deauthenticate all stations
) = 28
close(0)                                = 0
close(5)                                = 0
write(1, "madwifi_set_iface_flags: dev_up="..., 34madwifi_set_iface_flags: dev_u
p=0
) = 34
ioctl(3, SIOCGIFFLAGS, 0xbfab95c0)      = 0
ioctl(3, SIOCSIFFLAGS, 0xbfab95c0)      = 0
close(3)                                = 0
close(4)                                = 0
munmap(0xb7fa2000, 4096)                = 0
exit_group(1)                           = ?

--
Ryan Castellucci http://ryanc.org/


--
Ryan Castellucci http://ryanc.org/



