From bryan  Fri Dec  1 05:31:11 2006
From: bryan (Bryan Kadzban)
Date: Fri, 01 Dec 2006 08:31:11 -0500
Subject: WinXP+PEAP+Cert Behavior
In-Reply-To: <20061201065955.GA77053@hal.rasterburn.org>
References: <20061129073313.GA19778@hal.rasterburn.org>
	<456E5B3C.8040207@kadzban.is-a-geek.net>
	<20061130051152.GA12416@hal.rasterburn.org>
	<456ECA8D.2090600@kadzban.is-a-geek.net>
	<20061130162903.GA31808@hal.rasterburn.org>
	<20061130174603.GA12419@kadzban.is-a-geek.net>
	<20061201065955.GA77053@hal.rasterburn.org>
Message-ID: <45702E9F.800@kadzban.is-a-geek.net>

Benn wrote:
> Well, the key rotation should keep it from being interceptable simply
>  from any point,

Not really.  The key rotation doesn't matter here -- the attacker would
be sending broadcast ARP responses using the known group key at the
moment, claiming that his machine had somebody else's IP.  So when a
server tries to send to that IP, it sends to the attacker's MAC instead
of the real MAC.  The AP will happily use the attacker's key to encrypt
this traffic, because it only looks at the target MAC.

Because the attacker already has a valid association, the new group key
will be given to him just like any other valid client.  And so at the
appropriate time, the attacker's ARP responses will start being
encrypted with the new group key.

This isn't related to getting onto the network; this is an attack that
can be carried out after associating and going through the EAP
transaction, if everyone is always allowed.  It's a half-DoS, half-MitM
attack (you can do either).

> Interesting you mention that -- I actually tweaked freeradius to do 
> exactly that, but lacking the proper response Message-Authenticator
> it was dropped.  Is that the kind of thing that I can easily
> generate?

You should only require the RADIUS shared secret.  It may be easier if
you write your own "RADIUS" server (in quotes because it isn't; it'll
just blindly generate accept messages); then you can take the shared
secret and generate the proper authenticator.

> Or, is it a pretty straightforward calculation?

IIRC, it has something to do with repeated MD5 hashing, and putting the
shared secret into the source for the hash.

> I should probably just rtfm the radius rfc, ne? :)

That's what I was going to suggest.  ;-)  It's what I do every time I
need to refresh myself on the Message-Authenticator stuff (and also any
other fields).

RFC 2865.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061201/2517ff93/attachment.pgp 


From tino.keitel  Sat Dec  2 05:03:06 2006
From: tino.keitel (Tino Keitel)
Date: Sat, 2 Dec 2006 14:03:06 +0100
Subject: wpa_supplicant broken when card is ejected/inserted
Message-ID: <20061202130306.GA1418@thinkpad.home.local>

Hi folks,

I used to use this setup:

- wpa_supplicant always running

- Cardbus card that I insert when I need it

I noticed at some point that this doesn't work anymore. Now I tried to
repair my setup, and observed the following:

1.

- card inserted, supplicant started: can associate, dhclient gets an IP

- card ejected, supplicant goes to sleep

- card inserted again, supplicant seems to associate, but dhclient
  doesn't get an IP [1]

- supplicant restarted, dhclient gets an IP

2.

- card not inserted, supplicant started and waiting for the interface

- card inserted, supplicant can not associate [2]

- supplicant restarted, can associate, dhclient gets an IP

What can I do to repair this setup?

I use wpa_supplicant 0.5.5 (Debian Etch).

The card is Atheros based. Here are the madwifi driver versions:

ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath_rate_sample: 1.2 (svn r1724)
ath_pci: 0.9.4.5 (svn r1724)

My wpa_supplicant command line:

wpa_supplicant -d -iath0 -w -Dwext -c /etc/wpa_supplicant.conf

Regards,
Tino

[1] http://tikei.de/1.log

[2] http://tikei.de/2.log



From j.witteveen  Sat Dec  2 10:41:16 2006
From: j.witteveen (Jouke Witteveen)
Date: Sat, 2 Dec 2006 19:41:16 +0100
Subject: new wired driver code
Message-ID: <3993a4980612021041o7e9f5fb5m3f279d633fa18108@mail.gmail.com>

Hello,

For some stupid reason my ISP uses WPA on its connection. So in order
to get my FreeBSD box on the net I need to make driver_wired.c from
the wpa_supplicant work in BSD. I downloaded the source (v0.4.8) and
tried to compile. A few days of reading a lot of c code in order to
lean c later I came up with the following changes:

BSD doesn't provide the following include, and the code that uses it
is __linux__ only anyway, so I added the following if block:
---driver_wired.c------
#ifdef __linux__
#include <netpacket/packet.h>
#endif /* __linux__ */
------

Next I searched for all non-BSD compliant code and found that ifreq
has no ifr_hwaddr in BSD (this is used in wpa_driver_wired_multi). The
following adjustment however does not work though I'm pretty positive
something alike should do the trick) because the ioctl complains about
invalid arguments during runtime:
---driver_wired.c (wpa_driver_wired_multi)------
#ifdef __linux__
        ifr.ifr_hwaddr.sa_family = AF_UNSPEC;
        memcpy(ifr.ifr_hwaddr.sa_data, addr, ETH_ALEN);
#else /* __linux__ */
        ifr.ifr_addr.sa_family = AF_UNSPEC;
        memcpy(ifr.ifr_addr.sa_data, addr, ETH_ALEN);
#endif /* __linux__ */

        if (ioctl(s, add ? SIOCADDMULTI : SIOCDELMULTI, (caddr_t) &ifr) < 0) {
                perror("ioctl[SIOC{ADD/DEL}MULTI]");
                close(s);
                return -1;
        }
------

Can anyone help me getting the wired driver to work in FreeBSD? I
would be most grateful, not only with solutions, but also with
suggestions.

Regards,
- Jouke



From jkmaline  Sat Dec  2 15:59:15 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 2 Dec 2006 15:59:15 -0800
Subject: [PATCH] Avoid a segmentation fault
In-Reply-To: <456EDC37.8030908@6wind.com>
References: <456EDC37.8030908@6wind.com>
Message-ID: <20061202235915.GA6104@jm.kir.nu>

On Thu, Nov 30, 2006 at 02:27:19PM +0100, Nicolas DICHTEL wrote:

> please find enclosed a patch to avoid segmentation fault when some
> errors occur when loading certificats.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yuaimin  Sun Dec  3 18:33:15 2006
From: yuaimin (=?gb2312?B?09qwrsPx?=)
Date: Mon, 4 Dec 2006 10:33:15 +0800
Subject: use case of FilterID in hostap
Message-ID: <200612041033890.SM01984@yuaimin>

Hello every one !
   
    I am doing some experience about trusted network connection.I use hostAPd as my Access Point.As the TNC Specification required,the AP should support FilterID to isolate the current connection to specific location.So can someone add the function handling FilterID .
    Thank you very much!!

	Previous Mail:
>  On Fri, Oct 20, 2006 at 03:24:36PM +0800, ?????? wrote:

> 	I am using HostAPd(on a wired Ethernet Card) and a Radius server to do some experience. I want to know if the HostAPd support the Filter-Id Attribute that is wrapped in a Accept-Accept packet.

> No, hostapd does not control any filtering that would benefit of this
> attribute and as such, it is not parsed from Access-Accept. Do you have
> some specific use cases in mind for this attribute? What would you like
> hostapd to do if the RADIUS server includes this attribute? I could
> think of adding a callback function to be called when Access-Accept is
> received. This function would likely be empty at least for the time
> being, but there would be a clear place to add some custom code if
> someone wants to add extra actions based on Access-Accept. It would also
> be possible to just send this frame to another process to allow changing
> this behavior without having to modify hostapd.

	


			 





From jkmaline  Sun Dec  3 18:54:34 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 3 Dec 2006 18:54:34 -0800
Subject: use case of FilterID in hostap
In-Reply-To: <200612041033890.SM01984@yuaimin>
References: <200612041033890.SM01984@yuaimin>
Message-ID: <20061204025433.GA9688@jm.kir.nu>

On Mon, Dec 04, 2006 at 10:33:15AM +0800, ?????? wrote:

>     I am doing some experience about trusted network connection.I use hostAPd as my Access Point.As the TNC Specification required,the AP should support FilterID to isolate the current connection to specific location.So can someone add the function handling FilterID .

Can you please tell us where to get TNC specification that specifies how
FilterID needs to be supported?

-- 
Jouni Malinen                                            PGP id EFC895FA



From ramprasad.rajendran  Sun Dec  3 22:01:29 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Mon, 4 Dec 2006 11:31:29 +0530
Subject: Username on EAP-MSCHAPv2
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F692B@blr-m3-msg.wipro.com>


Hi,
I am using wpa_supplicant version 0.5.5 and hostapd 0.4.9 as the
authenticator cum RADIUS.
I am testing with EAP-MSCHAPv2

The username in the hostapd's user and password file has the format
DOMAIN\user.

I tried setting the username at the configuration file at the supplicant
to user at DOMAIN, DOMAIN\user, but gets rejected.
Is there any particular format in which the user name must be used for
MSCHAPV2.

Thanks in advance
----
ram


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From beat.naef  Mon Dec  4 10:17:48 2006
From: beat.naef (Beat Naef)
Date: Mon, 4 Dec 2006 10:17:48 -0800
Subject: Client dyn WEP problem
Message-ID: <LPBBIACKFCPEOAJEDEFIEEHENKAA.beat.naef@stagecoach-wireless.com>

We run a wireless network with following setup:

3 clients, running wpa-supplicant, EAP-TLS, dyn WEP, authenticating against
a hostapd master using the built in EAP authenticator.

At ifup the clients initiate the connection with the master and get the
periodically changing WEP key from the master.

The master initiates and is supposed to maintain a constant port 80
connection to download images from the clients (it used to work fine without
dyn WEP).

Every once in a while some or all clients get "lost". It appears that the
re-keying process is not always working properly. Most of the time the
clients do come back at the next re-keying round.

We are currently running a script on the clients that does an ifdown-ifup
every 5 min. This essentially forces the re-authentication, re-association
and re-keying of the clients. This is already much better than waiting for
the next re-keying round but still causes frequent connection disruptions.

How can we get the clients to re-authenticate if the re-keying did not
happen properly?

We are thinking about setting up a script that monitors the
/proc/net/hostap/wlan0 and the /proc/net/wireless. However we are not sure
what piece of information to monitor.

Another solution would be to monitor the kernel messages, because they do
show that the encryption failed, which we assume is the reason for the
clients to get "lost".

With kind regards

Beat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Beat Naef.vcf
Type: text/x-vcard
Size: 533 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061204/2db9452a/attachment.vcf 


From dcbw  Mon Dec  4 11:58:07 2006
From: dcbw (Dan Williams)
Date: Mon, 04 Dec 2006 14:58:07 -0500
Subject: [PATCH] dbus ctrl interface: fix reply message success argument
Message-ID: <1165262287.25362.4.camel@localhost.localdomain>

A mistype caused the success argument not to be added to the reply
message.

Dan

--- wpa_supplicant/ctrl_iface_dbus_handlers.c.bak	2006-12-04 14:23:57.000000000 -0500
+++ wpa_supplicant/ctrl_iface_dbus_handlers.c	2006-12-04 14:23:59.000000000 -0500
@@ -64,7 +64,7 @@
 	unsigned int success = 1;
 
 	reply = dbus_message_new_method_return(message);
-	dbus_message_append_args(message, DBUS_TYPE_UINT32, &success,
+	dbus_message_append_args(reply, DBUS_TYPE_UINT32, &success,
 				 DBUS_TYPE_INVALID);
 	return reply;
 }

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctrl-iface-dbus-handlers-reply-return.patch
Type: text/x-patch
Size: 438 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061204/6713a0ca/attachment.bin 


From dcbw  Mon Dec  4 12:02:57 2006
From: dcbw (Dan Williams)
Date: Mon, 04 Dec 2006 15:02:57 -0500
Subject: [PATCH] dbus ctrl interface: add interface 'state' method
Message-ID: <1165262577.25362.9.camel@localhost.localdomain>

There is currently a state change signal, but no way to get the initial
interface state.  This patch adds that method.

Dan

--- wpa_supplicant/ctrl_iface_dbus_handlers.c.foo	2006-12-04 14:26:36.000000000 -0500
+++ wpa_supplicant/ctrl_iface_dbus_handlers.c	2006-12-04 14:33:56.000000000 -0500
@@ -1173,3 +1173,27 @@
 out:
 	return reply;
 }
+
+/**
+ * wpas_dbus_iface_get_state - Get interface state
+ * @message: Pointer to incoming dbus message
+ * @wpa_s: wpa_supplicant structure for a network interface
+ * Returns: A dbus message containing a STRING representing the current
+ *          interface state
+ *
+ * Handler function for "state" method call.
+ */
+DBusMessage * wpas_dbus_iface_get_state(DBusMessage *message,
+					  struct wpa_supplicant *wpa_s)
+{
+	DBusMessage *reply = NULL;
+	const char * str_state;
+
+	reply = dbus_message_new_method_return(message);
+	if (reply != NULL) {
+		str_state = wpa_supplicant_state_txt(wpa_s->wpa_state);
+		dbus_message_append_args(message, DBUS_TYPE_STRING, &str_state, DBUS_TYPE_INVALID);
+	}
+
+	return reply;
+}
--- wpa_supplicant/ctrl_iface_dbus_handlers.h.foo	2006-12-04 14:31:22.000000000 -0500
+++ wpa_supplicant/ctrl_iface_dbus_handlers.h	2006-12-04 14:32:01.000000000 -0500
@@ -68,6 +68,9 @@
 DBusMessage * wpas_dbus_iface_set_ap_scan(DBusMessage *message,
                                           struct wpa_supplicant *wpa_s);
 
+DBusMessage * wpas_dbus_iface_get_state(DBusMessage *message,
+                                        struct wpa_supplicant *wpa_s);
+
 #endif /* CONFIG_CTRL_IFACE_DBUS */
 
 #endif /* CTRL_IFACE_DBUS_HANDLERS_H */
--- wpa_supplicant/ctrl_iface_dbus.c.foo	2006-12-04 14:26:51.000000000 -0500
+++ wpa_supplicant/ctrl_iface_dbus.c	2006-12-04 14:27:52.000000000 -0500
@@ -530,6 +530,8 @@
 			reply = wpas_dbus_iface_disconnect(message, wpa_s);
 		else if (!strcmp(method, "setAPScan"))
 			reply = wpas_dbus_iface_set_ap_scan(message, wpa_s);
+		else if (!strcmp(method, "state"))
+			reply = wpas_dbus_iface_get_state(message, wpa_s);
 	}
 
 	/* If the message was handled, send back the reply */

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctrl-iface-dbus-iface-state.patch
Type: text/x-patch
Size: 1970 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061204/66e09dff/attachment.bin 


From j.witteveen  Mon Dec  4 13:09:22 2006
From: j.witteveen (Jouke Witteveen)
Date: Mon, 4 Dec 2006 22:09:22 +0100
Subject: Fwd: new wired driver code
In-Reply-To: <3993a4980612021041o7e9f5fb5m3f279d633fa18108@mail.gmail.com>
References: <3993a4980612021041o7e9f5fb5m3f279d633fa18108@mail.gmail.com>
Message-ID: <3993a4980612041309p487cf64dl8e6f6e251aaf2a25@mail.gmail.com>

After some inspection of some sourcecode of the OS I found the following:
---net/if.c------
/* Don't let users screw up protocols' entries. */
if (ifr->ifr_addr.sa_family != AF_LINK)
	return (EINVAL);
------
and:
---net/if_fddisubr.c------
if ((e_addr[0] & 1) != 1)
	return (EADDRNOTAVAIL);
------
So I changed some more in driver_wired.c (see previous mail too):
---driver_wired.c------
#ifdef __linux__
        ifr.ifr_hwaddr.sa_family = AF_UNSPEC;
        memcpy(ifr.ifr_hwaddr.sa_data, addr, ETH_ALEN);
#else /* __linux__ */
        ifr.ifr_addr.sa_family = AF_LINK;
        memcpy(ifr.ifr_addr.sa_data, addr, ETH_ALEN);
        printf("Expected result: %x\n", // for debugging
                ((caddr_t) &(ifr.ifr_addr.sa_data))[0] & 1);
#endif /* __linux__ */
------
Though the expected result is 1 (I believe that is good) I still get
the EADDRNOTAVAIL:
---wpa_supplicant output (excerpt)------
(...)
Initializing interface (2) 'xl0'
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
Expected result: 1
ioctl[SIOC{ADD/DEL}MULTI]: Can't assign requested address
(...)
------
I think I con really use some help on how to get my 802.1X authentication going.
Has anyone succeeded in doing so on FreeBSD using a wired card?

Regards,
- Jouke


---------- Forwarded message ----------
From: Jouke Witteveen <j.witteveen at gmail.com>
Date: Dec 2, 2006 7:41 PM
Subject: new wired driver code
To: hostap at shmoo.com


Hello,

For some stupid reason my ISP uses WPA on its connection. So in order
to get my FreeBSD box on the net I need to make driver_wired.c from
the wpa_supplicant work in BSD. I downloaded the source (v0.4.8) and
tried to compile. A few days of reading a lot of c code in order to
lean c later I came up with the following changes:

BSD doesn't provide the following include, and the code that uses it
is __linux__ only anyway, so I added the following if block:
---driver_wired.c------
#ifdef __linux__
#include <netpacket/packet.h>
#endif /* __linux__ */
------

Next I searched for all non-BSD compliant code and found that ifreq
has no ifr_hwaddr in BSD (this is used in wpa_driver_wired_multi). The
following adjustment however does not work though I'm pretty positive
something alike should do the trick) because the ioctl complains about
invalid arguments during runtime:
---driver_wired.c (wpa_driver_wired_multi)------
#ifdef __linux__
        ifr.ifr_hwaddr.sa_family = AF_UNSPEC;
        memcpy(ifr.ifr_hwaddr.sa_data, addr, ETH_ALEN);
#else /* __linux__ */
        ifr.ifr_addr.sa_family = AF_UNSPEC;
        memcpy(ifr.ifr_addr.sa_data, addr, ETH_ALEN);
#endif /* __linux__ */

        if (ioctl(s, add ? SIOCADDMULTI : SIOCDELMULTI, (caddr_t) &ifr) < 0) {
                perror("ioctl[SIOC{ADD/DEL}MULTI]");
                close(s);
                return -1;
        }
------

Can anyone help me getting the wired driver to work in FreeBSD? I
would be most grateful, not only with solutions, but also with
suggestions.

Regards,
- Jouke



From naik  Mon Dec  4 13:42:29 2006
From: naik (Vinayak Naik)
Date: Mon, 4 Dec 2006 13:42:29 -0800
Subject: Pseudo_ibss mode does not work in for kernel-2.6
In-Reply-To: <11cc02d70612041338h5c997abeya5f37cc6d3e19a5c@mail.gmail.com>
References: <11cc02d70612041338h5c997abeya5f37cc6d3e19a5c@mail.gmail.com>
Message-ID: <11cc02d70612041342o1ae27a7ct488d0837e46d1ae2@mail.gmail.com>

Hi,

I have been using hostap-driver-3.7 in pseudo_ibss mode under
kernel-2.4.19 for a while. Recently, I have upgraded to kernel-2.6.14.

As a result, hostap-driver-3.7 to hostap-driver-4.1 do not work on the
new kernel. Here is the error message "pcmcia: hostap_cs lacks a
requisite callback function". So I have upgraded to hostap-driver-4.4.
Although the error goes away, the card is not able to communicate with
its peers in pseudo_ibss mode. I am using the same old cards. Any
idea, what's wrong?

Thanks,

- Vinayak



From a.h.pohl  Mon Dec  4 14:20:22 2006
From: a.h.pohl (Alexander Pohl)
Date: Mon, 4 Dec 2006 22:20:22 +0000
Subject: WPA2/AES disconnect problem
Message-ID: <a83119a70612041420r42f263fdp994886fa96153f76@mail.gmail.com>

Hello,

I have a problem with WPA2/AES. The client gets disconnected due to "local
deauth request" soon after successful authentication against
freeradius (EAP-PEAP). In the moment I am using WPA/TKIP, which does
not have the above problem.

My setup:

Client: IBM Thinkpad R50 (WinXP SP2) with Access Connections v4.21 and
11a/b/g Wireless LAN Mini PCI Adapter II (Atheros)

AP: IBM Thinkpad X23 (Debian Etch 4.0) with hostapd 0.5.5, freeradius
1.1.3 and Cisco Aironet 11a/b/g CardBus Wireless LAN Client Adapter
(Atheros)

hostapd.log:

Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
eapol_version=2
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:40:96:a1:c8:a0 and ssid 'debian-ssid'
ath0: RADIUS Authentication server 127.0.0.1:1812
ath0: RADIUS Accounting server 127.0.0.1:1813
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=0x1
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA= 0x3
madwifi_set_iface_flags: dev_up=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=0
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=2
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=3
IEEE 802.1X: New default WEP key index 2
IEEE 802.1X: New default WEP key - hexdump(len=13): [REMOVED]
madwifi_set_key: alg=WEP addr=00:00:00:00:00:00 key_idx=2
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
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
madwifi_set_privacy: enabled=1
ath0: RADIUS Sending RADIUS message to accounting server
ath0: RADIUS Next RADIUS client retransmit in 3 seconds

SIOCGIWRANGE: WE(compiled)=20 WE(source)=13 enc_capa=0xf
ath0: IEEE 802.11 Fetching hardware channel/rate support not supported.
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
Deauthenticate all stations
ath0: RADIUS Received 20 bytes from RADIUS server
ath0: RADIUS Received RADIUS message
ath0: STA 00:00:00:00:00:00 RADIUS: Received RADIUS packet matched
with a pending request, round trip time 0.00 sec
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0e:9b:ba:1e:ea IEEE 802.11: associated
 New STA
ath0: STA 00:0e:9b:ba:1e:ea WPA: event 1 notification
......
......
......
ath0: STA 00:0e:9b:ba:1e:ea WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0e:9b:ba:1e:ea WPA: sending 3/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=1 pairwise=8 ie_len=54
gtk_len=32 keyidx=1 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=104): [REMOVED]
TX EAPOL - hexdump(len=217): 00 0e 9b ba 1e ea 00 40 96 a1 c8 a0 88 8e
02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 02 fb fa e6 59 6b 61
54 3e bd 5c 48 36 72 03 f0 dd c7 9a b7 04 0c f0 25 f4 a7 76 ed 65 8f
2e e7 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 72 04 41 c1 0a 29 cc a3 67 2d be
cf 26 df 98 a2 00 68 22 89 93 38 c0 ad 26 9b 74 4c aa bb e0 5f f7 e1
33 b9 f5 b6 31 bb 59 ac bc 89 86 e8 5a 69 0c db d0 a6 89 d2 c7 d5 d0
9a c6 1b 04 9b c9 22 bc 0f fe e6 d4 38 29 7e 91 39 5e 65 8d a2 4c 6b
85 30 68 c9 b6 70 d8 7c 8e 0b a4 e8 bd e6 ac f1 d8 c8 80 53 37 f0 6b
00 f8 f8 d9 e1 59 c4 b2 9a 0c 3f 37 47 72 fc 77 49 d3 16
IEEE 802.1X: 00:0e:9b:ba:1e:ea REAUTH_TIMER entering state INITIALIZE
ath0: STA 00:0e:9b:ba:1e:ea WPA: EAPOL-Key timeout
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0e:9b:ba:1e:ea WPA: sending 3/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=1 pairwise=8 ie_len=54
gtk_len=32 keyidx=1 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=104): [REMOVED]
TX EAPOL - hexdump(len=217): 00 0e 9b ba 1e ea 00 40 96 a1 c8 a0 88 8e
02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 03 fb fa e6 59 6b 61
54 3e bd 5c 48 36 72 03 f0 dd c7 9a b7 04 0c f0 25 f4 a7 76 ed 65 8f
2e e7 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 7e 2e 6c 0c 58 34 fc 67 ba 10 24
e2 72 3a 8e 78 00 68 22 89 93 38 c0 ad 26 9b 74 4c aa bb e0 5f f7 e1
33 b9 f5 b6 31 bb 59 ac bc 89 86 e8 5a 69 0c db d0 a6 89 d2 c7 d5 d0
9a c6 1b 04 9b c9 22 bc 0f fe e6 d4 38 29 7e 91 39 5e 65 8d a2 4c 6b
85 30 68 c9 b6 70 d8 7c 8e 0b a4 e8 bd e6 ac f1 d8 c8 80 53 37 f0 6b
00 f8 f8 d9 e1 59 c4 b2 9a 0c 3f 37 47 72 fc 77 49 d3 16
IEEE 802.1X: 00:0e:9b:ba:1e:ea REAUTH_TIMER entering state INITIALIZE
ath0: STA 00:0e:9b:ba:1e:ea WPA: EAPOL-Key timeout
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0e:9b:ba:1e:ea WPA: sending 3/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=1 pairwise=8 ie_len=54
gtk_len=32 keyidx=1 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=104): [REMOVED]
TX EAPOL - hexdump(len=217): 00 0e 9b ba 1e ea 00 40 96 a1 c8 a0 88 8e
02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 04 fb fa e6 59 6b 61
54 3e bd 5c 48 36 72 03 f0 dd c7 9a b7 04 0c f0 25 f4 a7 76 ed 65 8f
2e e7 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 05 72 ad 6f b9 9b 4e d4 76 e4 0b
76 fa 40 f7 35 00 68 22 89 93 38 c0 ad 26 9b 74 4c aa bb e0 5f f7 e1
33 b9 f5 b6 31 bb 59 ac bc 89 86 e8 5a 69 0c db d0 a6 89 d2 c7 d5 d0
9a c6 1b 04 9b c9 22 bc 0f fe e6 d4 38 29 7e 91 39 5e 65 8d a2 4c 6b
85 30 68 c9 b6 70 d8 7c 8e 0b a4 e8 bd e6 ac f1 d8 c8 80 53 37 f0 6b
00 f8 f8 d9 e1 59 c4 b2 9a 0c 3f 37 47 72 fc 77 49 d3 16
IEEE 802.1X: 00:0e:9b:ba:1e:ea REAUTH_TIMER entering state INITIALIZE
ath0: STA 00:0e:9b:ba:1e:ea WPA: EAPOL-Key timeout
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:0e:9b:ba:1e:ea WPA: sending 3/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=1 pairwise=8 ie_len=54
gtk_len=32 keyidx=1 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=104): [REMOVED]
TX EAPOL - hexdump(len=217): 00 0e 9b ba 1e ea 00 40 96 a1 c8 a0 88 8e
02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 05 fb fa e6 59 6b 61
54 3e bd 5c 48 36 72 03 f0 dd c7 9a b7 04 0c f0 25 f4 a7 76 ed 65 8f
2e e7 0d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0b 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 f1 08 2a 6b 05 e4 4e c2 67 9b 01
cd 76 b1 73 ad 00 68 22 89 93 38 c0 ad 26 9b 74 4c aa bb e0 5f f7 e1
33 b9 f5 b6 31 bb 59 ac bc 89 86 e8 5a 69 0c db d0 a6 89 d2 c7 d5 d0
9a c6 1b 04 9b c9 22 bc 0f fe e6 d4 38 29 7e 91 39 5e 65 8d a2 4c 6b
85 30 68 c9 b6 70 d8 7c 8e 0b a4 e8 bd e6 ac f1 d8 c8 80 53 37 f0 6b
00 f8 f8 d9 e1 59 c4 b2 9a 0c 3f 37 47 72 fc 77 49 d3 16
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect:
STA 00:0e:9b:ba:1e:ea reason 2
madwifi_sta_deauth: addr=00:0e:9b:ba:1e:ea reason_code=2
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state DISCONNECTED
WPA: 00:0e:9b:ba:1e:ea WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:0e:9b:ba:1e:ea key_idx=0
ath0: STA 00:0e:9b:ba:1e:ea IEEE 802.11: deauthenticated due to local
deauth request
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:0e:9b:ba:1e:ea IEEE 802.11: disassociated

Any help is very appreciated,
Alexander



From naik  Mon Dec  4 15:34:39 2006
From: naik (Vinayak Naik)
Date: Mon, 4 Dec 2006 15:34:39 -0800
Subject: Pseudo_ibss mode does not work in for kernel-2.6
In-Reply-To: <11cc02d70612041338h5c997abeya5f37cc6d3e19a5c@mail.gmail.com>
References: <11cc02d70612041338h5c997abeya5f37cc6d3e19a5c@mail.gmail.com>
Message-ID: <11cc02d70612041534t189e3ec2k2e0b31d54fdba3b1@mail.gmail.com>

Please disregard the posting. Pseudo_ibss mode worked using
hostap-driver-4.4 under kernel-2.6.14. The trick is the order in which
iwconfig, prism2_param, and ifconfig commands are called.

- Vinayak

On 12/4/06, Vinayak Naik <naik at cens.ucla.edu> wrote:
> Hi,
>
> I have been using hostap-driver-3.7 in pseudo_ibss mode under
> kernel-2.4.19 for a while. Recently, I have upgraded to kernel-2.6.14.
>
> As a result, hostap-driver-3.7 to hostap-driver-4.1 do not work on the
> new kernel. Here is the error message "pcmcia: hostap_cs lacks a
> requisite callback function". So I have upgraded to hostap-driver-4.4.
> Although the error goes away, the card is not able to communicate with
> its peers in pseudo_ibss mode. I am using the same old cards. Any
> idea, what's wrong?
>
> Thanks,
>
> - Vinayak
>



From dcbw  Mon Dec  4 20:42:41 2006
From: dcbw (Dan Williams)
Date: Mon, 04 Dec 2006 23:42:41 -0500
Subject: [PATCH] dbus control interface: use dbus_connection_unref
Message-ID: <1165293761.12340.1.camel@localhost.localdomain>

dbus_connection_close() is deprecated and not what we want here;
instead, unref the connection and be a good citizen.

Dan

--- ctrl_iface_dbus.c.unref-not-close	2006-12-04 22:53:28.000000000 -0500
+++ ctrl_iface_dbus.c	2006-12-04 23:17:38.000000000 -0500
@@ -852,7 +852,7 @@
 						    NULL, NULL, NULL);
 		dbus_connection_set_timeout_functions(iface->con, NULL, NULL,
 						      NULL, NULL, NULL);
-		dbus_connection_close(iface->con);
+		dbus_connection_unref(iface->con);
 	}
 
 	memset(iface, 0, sizeof(struct ctrl_iface_dbus_priv));

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctrl-iface-dbus-unref-not-close.patch
Type: text/x-patch
Size: 418 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061204/df78ceac/attachment.bin 


From dcbw  Mon Dec  4 20:45:27 2006
From: dcbw (Dan Williams)
Date: Mon, 04 Dec 2006 23:45:27 -0500
Subject: [PATCH] dbus control interface: dispatch initial messages
Message-ID: <1165293927.12340.5.camel@localhost.localdomain>

For whatever reason, messages that come in right after we've claimed the
bus name but not iterated through the eloop once don't get dispatched.
To fix this, schedule a dispatch timeout immediately after
initialization of our DBus service.

Dan

--- ctrl_iface_dbus.c.dispatch-earlier	2006-12-04 23:18:23.000000000 -0500
+++ ctrl_iface_dbus.c	2006-12-04 23:40:00.000000000 -0500
@@ -751,6 +751,25 @@
 
 
 /**
+ * dispatch_initial_dbus_messages - Dispatch initial dbus messages after
+ *     claiming bus name
+ * @eloop_ctx: the DBusConnection to dispatch on
+ * @timeout_ctx: unused
+ *
+ * If clients are quick to notice that wpa_supplicant claimed its bus name,
+ * there may have been messages that came in before initialization was
+ * all finished.  Dispatch those here.
+ */
+static void dispatch_initial_dbus_messages(void *eloop_ctx, void *timeout_ctx)
+{
+	DBusConnection * con = eloop_ctx;
+
+	while (dbus_connection_get_dispatch_status(con) ==
+	       DBUS_DISPATCH_DATA_REMAINS)
+		dbus_connection_dispatch(con);
+}
+
+/**
  * wpa_supplicant_dbus_ctrl_iface_init - Initialize dbus control interface
  * @global: Pointer to global data from wpa_supplicant_init()
  * Returns: Pointer to dbus_ctrl_iface date or %NULL on failure
@@ -788,6 +807,16 @@
 	if (integrate_with_eloop(iface->con, iface))
 		goto fail;
 
+	/* Register the message handler for the global dbus interface */
+	if (!dbus_connection_register_object_path(iface->con,
+						  WPAS_DBUS_PATH, &wpas_vtable,
+						  iface)) {
+		perror("dbus_connection_register_object_path[dbus]");
+		wpa_printf(MSG_ERROR, "Could not set up DBus message "
+			   "handler.");
+		goto fail;
+	}
+
 	/* Register our service with the message bus */
 	dbus_error_init(&error);
 	switch (dbus_bus_request_name(iface->con, WPAS_DBUS_SERVICE,
@@ -813,19 +842,18 @@
 	if (ret != 0)
 		goto fail;
 
-	/* Register the message handler for the global dbus interface */
-	if (!dbus_connection_register_object_path(iface->con,
-						  WPAS_DBUS_PATH, &wpas_vtable,
-						  iface)) {
-		perror("dbus_connection_register_object_path[dbus]");
-		wpa_printf(MSG_ERROR, "Could not set up DBus message "
-			   "handler.");
-		goto fail;
-	}
-
 	wpa_printf(MSG_DEBUG, "Providing DBus service '" WPAS_DBUS_SERVICE
 		   "'.");
 
+	/* Dispatch initial DBus messages that may have come in since the bus name
+	 * was claimed above.  Happens when clients are quick to notice the
+	 * wpa_supplicant service.
+	 *
+	 * FIXME: is there a better solution to this problem?
+	 */
+	eloop_register_timeout(0, 50, dispatch_initial_dbus_messages,
+	                       iface->con, NULL);
+
 	return iface;
 
 fail:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctrl-iface-dbus-dispatch-initial.patch
Type: text/x-patch
Size: 2407 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061204/ad84ffef/attachment.bin 


From kubaosuch  Tue Dec  5 01:38:46 2006
From: kubaosuch (Kuba Osuch)
Date: Tue, 5 Dec 2006 10:38:46 +0100
Subject: hostapd problem
Message-ID: <010501c71851$29b58cd0$03b2fea9@kuba>

My setup:
Slackware 11.0
Kernel 2.6.17
New hostapd
New madwifi drivers

I start my hostapd:
/usr/local/sbin/snmpd -c /usr/local/sbin/snmpd.conf
/etc/rc.d/wlanconfig ath0 destroy
/etc/rc.d/wlanconfig ath0 create wlandev wifi0 wlanmode ap
ifconfig ath0 192.168.4.1 netmask 255.255.255.0 up
/usr/src/hostapd-0.4.9/hostapd -B /etc/hostapd.conf
/usr/sbin/dhcpd eth1 ath0

my hostapd.conf:
interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=--1
logger_stdout_level=2
debug=0
ctrl_interface_group=0
macaddr_acl=0
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
dump_file=/tmp/hostapd.dump
ssid="KUBAOSUCH"
wpa=1
wpa_passphrase=danaosuch
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP


After start reboot i can connect to my ap:)
Client nokia e61.

But when i kill hostapd

and start:
hostapd -ddd /etc/hostapd.conf
And i have got this error.
ioctl[unknown???]: Invalid argument
 
 
 
 
 

madwifi_del_key: addr=00:13:fd:40:63:eb key_idx=0
ioctl[unknown???]: Invalid argument
madwifi_set_sta_authorized: addr=00:13:fd:40:63:eb authorized=0
ioctl[unknown???]: Invalid argument
Wireless event: cmd=0x8c04 len=20
Wireless event: cmd=0x8c03 len=20
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061205/a8945f70/attachment.htm 


From Mark.Powell  Tue Dec  5 04:34:32 2006
From: Mark.Powell (Mark Powell)
Date: Tue, 05 Dec 2006 12:34:32 +0000
Subject: Sequences for PTK rekeying
Message-ID: <45756758.7080001@csr.com>

Hi,

We are trying to understand the possible message sequences for PTK/GTK
establishment and rekeying that wpa_supplicant uses via the
Wireless Extensions API, and the interaction with the driver.

Looking at PTKs first, it seems to me that there are six possible
scenarios:

1) Us as initiator, success.
2) Us as responder, success.
3) Us as initiator, fails at second stage.
4) Us as responder, fails at second stage.
5) Us as initiator, fails at first stage.
6) Us as responder, fails at first stage.

These get progressively harder!

1) Us initiator, success.
The sequence is:

    Tx EAPOL Auth 1
    Rx EAPOL Auth 2
    Tx EAPOL Auth 3
    Rx EAPOL Auth 4
    Set keys

Is this correct?

2) Us responder, success.

    Rx EAPOL Auth 1
    Tx EAPOL Auth 2
    Rx EAPOL Auth 3
    Tx EAPOL Auth 4
    Set keys

Is this correct?
Particularly, does the SetKeys happen after the Tx EAPOL Auth 4 or could
it happen after the Rx EAPOL Auth 3?
Does the system wait for acknowledgement of the second tx before setting
the keys?

3) Us initiator, fails at second stage.

    Tx EAPOL Auth 1
    Rx EAPOL Auth 2
    Tx EAPOL Auth 3
    Timeout or rx bad EAPOL Auth 4

Is there any indication to the driver that the key
establishment/rekeying has failed?

4) Us responder, fails at second stage.

    Rx EAPOL Auth 1
    Tx EAPOL Auth 2
    Timeout or rx bad EAPOL Auth 3

Is there any indication to the driver that the key
establishment/rekeying has failed?

5) Us initiator, fails at first stage.

    Tx EAPOL Auth 1
    Timeout or rx bad EAPOL Auth 2

Is there any indication to the driver that the key
establishment/rekeying has failed?

6) Us responder, fails at first stage.

    Rx bad EAPOL Auth 1


Well, at least this one is easy!



Is there any difference between initial PTK establishment and
rekeying?



Similarly, for GTKs there seem to be four possible scenarios:

1) Us initiator, success.
2) Us responder, success.
3) Us initiator, fails.
4) Us responder, fails.

1) Us initiator, success.

    Tx EAPOL Auth 1
    Rx EAPOL Auth 2
    Set keys

Correct?

2) Us responder, success.

    Rx EAPOL Auth 1
    Tx EAPOL Auth 2
    Set keys

Is this correct?
Particularly, does the SetKeys happen after the Tx or could it happen
after the Rx?
Does the system wait for acknowledgement of the tx before setting the keys?

3) Us initiator, fails.

    Tx EAPOL Auth 1
    Timeout or rx bad EAPOL Auth 2

Is there any indication to the driver that the key
establishment/rekeying has failed?

4) Us responder, fails.

    Rx bad EAPOL Auth 1

As easy as before.


Again, is there any difference between the initial GTK establishment and
GTK rekeying?


Thanks for your help,

Mark


-- 
Mark Powell mailto:Mark.Powell at csr.com
Group Leader, Host Drivers Tel: +44 (0)1223 692000
CSR, Churchill House, Cambridge Business Park, Cowley Road, Cambridge,
CB24 0WZ, UK


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php



From mh+hostap  Tue Dec  5 04:53:13 2006
From: mh+hostap (Marc Haber)
Date: Tue, 5 Dec 2006 13:53:13 +0100
Subject: [wpa-supplicant] How to control association timeout?
In-Reply-To: <20061101051143.GJ6105@jm.kir.nu>
References: <20061030154045.GB14140@torres.l21.ma.zugschlus.de>
	<20061101051143.GJ6105@jm.kir.nu>
Message-ID: <20061205125313.GA27371@torres.l21.ma.zugschlus.de>

On Tue, Oct 31, 2006 at 09:11:43PM -0800, Jouni Malinen wrote:
> On Mon, Oct 30, 2006 at 04:40:45PM +0100, Marc Haber wrote:
> > I am using wpa_supplicant on Debian sid (version 0.5.5-2) with current
> > kernel and an ipw2200 interface. I am frequenly moving between my own
> > wireless LAN (WPA-PSK) and the wireless LAN at my girlfriend's place
> > (WEP-128 with hidden ssid). Here my wpa_supplicant.conf:
> 
> > ap_scan=2
> 
> > network={
> >         ssid="<mine>"
> > }
> 
> > network={
> >         ssid="<hers>"
> >         scan_ssid=1
> > }
> 
> > At her place, my notebook first tries to associate to my home wireless
> > LAN for 60 seconds before moving on to her wireless LAN, where the
> > association succeeds immediately.
> > 
> > How can I shorten that time to, say, 5 seconds?
> 
> One way of doing this would be to use ap_scan=1 with a driver that
> supports scan_ssid=1, but since ipw2200 is not such a driver, that
> answer is probably not very helpful..

Yes, and I am not in a position to exchange the ipw2200 card for
something else.

> There is no configuration option for this in wpa_supplicant at the
> moment. If you are willing to change source code and rebuild
> wpa_supplicant, you can change this by modifying
> wpa_supplicant_associate() function in wpa_supplicant.c.

Can I ask for this to be changeable at run time in a future version?

> That 60 there is the timeout for ap_scan=2 case.

I am currently solving this issue by manually issueing select commands
for the network in question.

> I don't know whether I would really like to make this configuration,
> though. I would rather consider ap_scan=2 mode with multiple enabled
> network blocks as a special case that request scanning of multiple SSIDs
> before trying to associate with the first network.

In my limited understanding of wpa_supplicant, ap_scan=2 mode is
needed for an ipw2200 card once even one of the networks in question
has its SSID hidden.

One is not always in a position to influence the configuration of the
wireless LAN in question, and, frankly, I am getting tired about
trying to educate people who think that they know everything better in
the first place.

>  One problem with this is, though, that most drivers do not have such
>  functionality and wpa_supplicant would need to try to associate with
>  each network first with minimal timeout (just couple of seconds) in
>  order to get them included in the scan results.

Yes, that's what wpa_supplicant currently does, with 60 seconds
timeout, which is way too long for the majority of _my_ cases.

>  After each association attempt, scan results would be collected and
>  merged together. Only after this, the best AP (based on security
>  policy and/or priority configuration) would be selected and
>  wpa_supplicant would try to associate with it using a longer timeout.

I'd be happy if wpa_supplicant would take the first network it finds,
they are sufficiently far apart to make absolutely sure that there is
always only one of them in range.

> It should also be possible to optimize this by assuming that each
> network without scan_ssid=1 is sending out its SSID (i.e., does not need
> a specific per-SSID scan). In that case, the scan process would start
> with one scan for all SSIDs and the try-quick-association loop would
> only go through the network blocks with scan_ssid=1. This would likely
> be the fastest solution that is likely to work with most drivers.

That sounds like a good idea to me.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835



From prabhu  Tue Dec  5 05:10:03 2006
From: prabhu (Prabhakar kushwaha)
Date: Tue, 5 Dec 2006 05:10:03 -0800
Subject: eap - tls certificate
Message-ID: <20061205051003.408350DF@resin06.mta.everyone.net>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061205/5c777890/attachment.htm 


From ifreebiz  Tue Dec  5 17:26:30 2006
From: ifreebiz (Andrew)
Date: Tue, 05 Dec 2006 17:26:30 -0800
Subject: supplicant's response to a corrupted server hello  message
In-Reply-To: <20060811030359.GA8975@jm.kir.nu>
References: <200608091429.02949.florian.fainelli@int-evry.fr>
	<20060810022724.GB9017@jm.kir.nu>
	<1155242278.32587.268111144@webmail.messagingengine.com>
	<20060811030359.GA8975@jm.kir.nu>
Message-ID: <1165368390.15537.279066875@webmail.messagingengine.com>

I think I got a wrong response from wpa_supplicant(version 0.4.8) to a
corrupted server hello message. The below is the log. And the response
message is 023c000d150015000000020246. The FreeRadius server says the
the tls version is wrong. Has any one seen this problem before? And how
to fix it?

Thanks, Andrew

SSL: SSL3 alert: write (local SSL3 detected an error):fatal:protocol
version
SSL: SSL_connect:error in SSLv3 read server hello A
OpenSSL: tls_connection_handshake - SSL_connect error:1408F10B:SSL
 routines:SSL3_GET_RECORD:wrong version number 
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


-- 
http://www.fastmail.fm - The way an email service should be




From a.h.pohl  Wed Dec  6 13:57:56 2006
From: a.h.pohl (Alexander Pohl)
Date: Wed, 6 Dec 2006 21:57:56 +0000
Subject: WPA2/AES disconnect problem
In-Reply-To: <c4a81f5e0612050001s6e39e0f7g5e44857abfb92d48@mail.gmail.com>
References: <a83119a70612041420r42f263fdp994886fa96153f76@mail.gmail.com>
	<c4a81f5e0612050001s6e39e0f7g5e44857abfb92d48@mail.gmail.com>
Message-ID: <a83119a70612061357k407d62a1ra6bba87d3f0135cd@mail.gmail.com>

Dear Kuba,

Here are my config files for freeradius. You basically need only to
adjust eap.conf to allow PEAP and TLS  authentication methods and
create a users file (or use a MySQL, PostgreSQL or LDAP database). You
also need a public key infrastructure to generate your own
certificates.

eap.conf:

default_eap_type = tls
  tls {
                        private_key_file = ${raddbdir}/certs/freeradius-key.pem
                        certificate_file = ${raddbdir}/certs/freeradius-cert.pem
                        CA_file = ${raddbdir}/certs/cacert.pem
                        CA_path = ${raddbdir}/certs
                        dh_file = ${raddbdir}/certs/dh1024.pem
                        random_file = /dev/urandom

                        check_crl = yes
                        check_cert_issuer = "/O=The University of
Reading/OU=CA/emailAddress=a.h.pohl at reading.ac.uk/L=Reading/ST=Berkshire/C=GB/CN=Debian
RootCA"
}
peap {
                      default_eap_type = mschapv2
}

users:

"user"    User-Password == "pass"



I have summarised the openssl commands to set up your own PKI below.
You need a simple openssl.cnf file:

#
# OpenSSL configuration file.
#

# Establish working directory.
dir = .

[ req ]
default_bits = 1024 # Size of keys
default_keyfile = key.pem # name of generated keys
default_md = md5 # message digest algorithm
string_mask = nombstr # permitted characters
distinguished_name = req_distinguished_name
req_extensions = v3_req

[ req_distinguished_name ]
# Variable name   Prompt string
#----------------------   ----------------------------------
0.organizationName = Organization Name (company)
organizationalUnitName = Organizational Unit Name (department, division)
emailAddress = Email Address
emailAddress_max = 40
localityName = Locality Name (city, district)
stateOrProvinceName = State or Province Name (full name)
countryName = Country Name (2 letter code)
countryName_min = 2
countryName_max = 2
commonName = Common Name (hostname, IP, or your name)
commonName_max = 64

# Default values for the above, for consistency and less typing.
# Variable name   Value
#------------------------------   ------------------------------
0.organizationName_default = The University of Reading
localityName_default = Reading
stateOrProvinceName_default = Berkshire
countryName_default = GB

[ v3_ca ]
basicConstraints = CA:TRUE
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always,issuer:always

[ v3_req ]
basicConstraints = CA:FALSE
subjectKeyIdentifier = hash

[ ca ]
default_ca = CA_default

[ CA_default ]
serial = $dir/serial
database = $dir/index.txt
new_certs_dir = $dir/newcerts
certificate = $dir/cacert.pem
private_key = $dir/private/cakey.pem
default_days = 365
default_md = md5
preserve = no
email_in_dn = no
nameopt = default_ca
certopt = default_ca
policy = policy_match

[ policy_match ]
countryName = match
stateOrProvinceName = match
organizationName = match
organizationalUnitName = optional
commonName = supplied
emailAddress = optional

[ xpclient_ext]
extendedKeyUsage = 1.3.6.1.5.5.7.3.2

[ xpserver_ext ]
extendedKeyUsage = 1.3.6.1.5.5.7.3.1

[ openvpn_server ]
nsCertType = server
nsComment  = "OpenSSL Generated Server Certificate"

[ openvpn_client ]
nsCertType = client
nsComment  = "OpenSSL Generated Client Certificate"



Then use the following commands to generate your certificates:

# make root CA
mkdir newcerts private
echo '01' > serial
touch index.txt

openssl req -new -x509 -extensions v3_ca -keyout private/cakey.pem
-out cacert.pem -days 3650 -config ./openssl.cnf

chmod 0400 private/cakey.pem
echo 'private key' > private/ca.key
chmod 0400 private/ca.key

# check
openssl x509 -in cacert.pem -noout -text
openssl x509 -in cacert.pem -noout -dates
openssl x509 -in cacert.pem -noout -purpose

#signing request
openssl req -new -nodes -out req.pem -config ./openssl.cnf

---
Organizational Unit: a reminder of what the certificate is for
Email Address: the postmaster, wemaster, etc...
Common Name: the server hostname, server name, etc...
---

#sign client
openssl ca -out cert.pem -passin file:private/ca.key -config
./openssl.cnf -extensions xpclient_ext -infiles req.pem
#sign server
openssl ca -out cert.pem -passin file:private/ca.key -config
./openssl.cnf -extensions xpserver_ext -infiles req.pem

#remove text
mv cert.pem tmp.pem
openssl x509 -in tmp.pem -out cert.pem

cat cert.pem key.pem > cert-key.pem

#create revocation list
openssl ca -gencrl -passin file:private/ca.key -crldays 31 -config
./openssl.cnf -out rootca.crl

#diffie-hellmann
openssl dhparam -out dh1024.pem 1024


You have to save your private key for cacert.pem in a file or type the
passphrase interactively. Coming back to hostapd configuration, WPA2
uses always AES (CCMP), whereas with WPA you have the choice between
TKIP or AES. The client decides which cipher will be used in case of
WPA, if you allow both (wpa_pairwise=TKIP CCMP).

I hope that keeps you going,
Alexander



From a.h.pohl  Wed Dec  6 14:03:36 2006
From: a.h.pohl (Alexander Pohl)
Date: Wed, 6 Dec 2006 22:03:36 +0000
Subject: WPA2/AES disconnect problem
In-Reply-To: <a83119a70612061357k407d62a1ra6bba87d3f0135cd@mail.gmail.com>
References: <a83119a70612041420r42f263fdp994886fa96153f76@mail.gmail.com>
	<c4a81f5e0612050001s6e39e0f7g5e44857abfb92d48@mail.gmail.com>
	<a83119a70612061357k407d62a1ra6bba87d3f0135cd@mail.gmail.com>
Message-ID: <a83119a70612061403s39086a5ak5df064aba50d6e3c@mail.gmail.com>

I have just spotted that according to your config you are using WPA,
not WPA2. To activate WPA2 (as well as WPA) you need to specify wpa=3.
Also your clients need to support this.

Alexander



From jkmaline  Wed Dec  6 20:11:54 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 6 Dec 2006 20:11:54 -0800
Subject: supplicant's response to a corrupted server hello  message
In-Reply-To: <1165368390.15537.279066875@webmail.messagingengine.com>
References: <200608091429.02949.florian.fainelli@int-evry.fr>
	<20060810022724.GB9017@jm.kir.nu>
	<1155242278.32587.268111144@webmail.messagingengine.com>
	<20060811030359.GA8975@jm.kir.nu>
	<1165368390.15537.279066875@webmail.messagingengine.com>
Message-ID: <20061207041154.GD6112@jm.kir.nu>

On Tue, Dec 05, 2006 at 05:26:30PM -0800, Andrew wrote:

> I think I got a wrong response from wpa_supplicant(version 0.4.8) to a
> corrupted server hello message. The below is the log. And the response
> message is 023c000d150015000000020246. The FreeRadius server says the
> the tls version is wrong. Has any one seen this problem before? And how
> to fix it?

Can you reproduce this issue? Would it be possible to get more complete
debug log showing hexdump of the TLS messages?

> SSL: SSL3 alert: write (local SSL3 detected an error):fatal:protocol

This is OpenSSL saying that the received TLS packet was invalid.

> SSL: 7 bytes left to be sent out (of total 7 bytes)

And this is the TLS alert message from OpenSSL. these 7 bytes are the
last seven bytes in the message above.. For some reason the TLS version
field is 0000 which sounds a bit odd. Other than that, it looks like a
valid TLS alert. Anyway, this is from OpenSSL and wpa_supplicant is
forwarding it unmodified.
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Dec  6 20:15:03 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 6 Dec 2006 20:15:03 -0800
Subject: eap - tls certificate
In-Reply-To: <20061205051003.408350DF@resin06.mta.everyone.net>
References: <20061205051003.408350DF@resin06.mta.everyone.net>
Message-ID: <20061207041503.GE6112@jm.kir.nu>

On Tue, Dec 05, 2006 at 05:10:03AM -0800, Prabhakar kushwaha wrote:
> i am doing test for EAP - TLS. which requires client side ceritficate. i have got from the windows.<BR>but it is in .pfx format.<BR>can u tell me how i can get following<BR>1.ca certificate in .pem format<BR>2. client certificate in .pem<BR>3.client certifacate password&nbsp; in .pem <BR>which is required in EAP -TLS<BR>

wpa_supplicant can use .pfx (PKCS#12) files, so you should not need to
convert the file. Anyway, you can use OpenSSL to export certificates and
keys from a PKCS#12 file (see "man pkcs12").

-- 
Jouni Malinen                                            PGP id EFC895FA



From ramprasad.rajendran  Thu Dec  7 01:58:04 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Thu, 7 Dec 2006 15:28:04 +0530
Subject: EAP-FAST inner Auth Fails
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F6962@blr-m3-msg.wipro.com>


Hi,

I am using wpa_supplicant-0.5.5 and hostapd as the authenticator and I
am testing over a wired interface. 
The radius server that I'm using is Steel Belted Radius
I had commented out code related to certificate processing to reduce on
the size.

As soon as Phase1 suceeds, in phase 2, the Radius server requests for
identity, without using any inner authentication.
Is this correct? I guess an inner authentication method should start as
part of phase 2

Attached alongwith is the output and my configuration file

----
ram



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Output.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20061207/dfe11b14/attachment.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fast.conf
Type: application/octet-stream
Size: 560 bytes
Desc: fast.conf
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061207/dfe11b14/attachment.obj 


From b_zarboni  Thu Dec  7 12:23:07 2006
From: b_zarboni (Ben Z)
Date: Thu, 7 Dec 2006 15:23:07 -0500 (EST)
Subject: Fedora Core 5
Message-ID: <646338.88600.qm@web88005.mail.re2.yahoo.com>

Hi all;
   
  I'm having trouble searching the mailing list, so I can tell if this has been posted before.
   
  I can't seem to use my Prism 2 card in my Fedora Core 5 laptop. 
   
  Here's my setup: Panasonic Toughbook CF-29 - Intel Pentium M 1.6GHz
                            Fedora Core 5 - 2.6.17 kernel ( Fedora Kernel 2.6.17-1.2157_FC5 )
   
  I had to blacklist my orinoco driver (because this is a Prism-2 card, but the orinoco driver kept loading for it)
   
  When I try to install the hostap driver I get:

  ieee80211: 802.11 data/management/control stack, 1.2.15
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno at linux.intel.com>
hostap: disagrees about version of symbol ieee80211_get_crypto_ops
hostap: Unknown symbol ieee80211_get_crypto_ops
hostap_cs: Unknown symbol prism2_update_comms_qual
hostap_cs: Unknown symbol hostap_set_hostapd
hostap_cs: Unknown symbol hostap_set_encryption
hostap_cs: Unknown symbol hostap_remove_proc
hostap_cs: Unknown symbol hostap_set_auth_algs
hostap_cs: Unknown symbol hostap_80211_get_hdrlen
hostap_cs: Unknown symbol hostap_set_multicast_list_queue
hostap_cs: Unknown symbol hostap_get_stats
hostap_cs: Unknown symbol hostap_add_interface
hostap_cs: Unknown symbol hostap_free_data
hostap_cs: Unknown symbol hostap_set_word
hostap_cs: Unknown symbol hostap_info_process
hostap_cs: Unknown symbol hostap_set_string
hostap_cs: Unknown symbol hostap_set_antsel
hostap_cs: Unknown symbol hostap_remove_interface
hostap_cs: Unknown symbol hostap_setup_dev
hostap_cs: Unknown symbol hostap_dump_rx_header
hostap_cs: Unknown symbol hostap_init_data
hostap_cs: Unknown symbol hostap_80211_header_parse
hostap_cs: Unknown symbol hostap_init_ap_proc
hostap_cs: Unknown symbol hostap_set_hostapd_sta
hostap_cs: Unknown symbol hostap_init_proc
hostap_cs: Unknown symbol hostap_dump_tx_header
hostap_cs: Unknown symbol hostap_check_sta_fw_version
hostap_cs: Unknown symbol hostap_get_porttype
hostap_cs: Unknown symbol hostap_80211_rx
hostap_cs: Unknown symbol hostap_set_roaming
hostap_cs: Unknown symbol hostap_handle_sta_tx_exc
hostap_cs: Unknown symbol hostap_info_init
hostap_cs: Unknown symbol hostap_master_start_xmit
hostap: disagrees about version of symbol ieee80211_get_crypto_ops
hostap: Unknown symbol ieee80211_get_crypto_ops
hostap: disagrees about version of symbol ieee80211_get_crypto_ops
hostap: Unknown symbol ieee80211_get_crypto_ops

   
  Any help would be greatly appreciated!
   
  Thank you, 
   
  Ben Z
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061207/873f7b28/attachment.htm 


From jar  Thu Dec  7 12:25:56 2006
From: jar (Jar)
Date: Thu, 07 Dec 2006 22:25:56 +0200
Subject: Fedora Core 5
In-Reply-To: <646338.88600.qm@web88005.mail.re2.yahoo.com>
References: <646338.88600.qm@web88005.mail.re2.yahoo.com>
Message-ID: <457878D4.3070101@pcuf.fi>

Ben Z wrote:
> When I try to install the hostap driver I get:

Why to install, it is already included to 2.6.17 kernel and FC5?

-- 
Best Regards, Jar



From b_zarboni  Thu Dec  7 12:32:07 2006
From: b_zarboni (Ben Z)
Date: Thu, 7 Dec 2006 15:32:07 -0500 (EST)
Subject: Fedora Core 5
In-Reply-To: <457878D4.3070101@pcuf.fi>
Message-ID: <535101.96521.qm@web88013.mail.re2.yahoo.com>

I'm sorry, I meant "load" the driver.

Jar <jar at pcuf.fi> wrote:  

Why to install, it is already included to 2.6.17 kernel and FC5?

-- 
Best Regards, Jar

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


From jar  Thu Dec  7 13:03:48 2006
From: jar (Jar)
Date: Thu, 07 Dec 2006 23:03:48 +0200
Subject: Fedora Core 5
In-Reply-To: <535101.96521.qm@web88013.mail.re2.yahoo.com>
References: <535101.96521.qm@web88013.mail.re2.yahoo.com>
Message-ID: <457881B4.6040102@pcuf.fi>

Ben Z wrote:
> I'm sorry, I meant "load" the driver.

Ah, OK. How do you load the driver? Doesn't pcmcia system load it 
automagically when you plug the card in?

-- 
Best Regards, Jar



From b_zarboni  Thu Dec  7 13:31:58 2006
From: b_zarboni (Ben Z)
Date: Thu, 07 Dec 2006 16:31:58 -0500
Subject: Fedora Core 5
In-Reply-To: <457881B4.6040102@pcuf.fi>
References: <535101.96521.qm@web88013.mail.re2.yahoo.com>
	<457881B4.6040102@pcuf.fi>
Message-ID: <1165527118.2364.4.camel@localhost.localdomain>

No,  it doesn't seem to. :(

I've been trying to 'modprobe hostap_cs'



On Thu, 2006-12-07 at 23:03 +0200, Jar wrote:
> Ben Z wrote:
> > I'm sorry, I meant "load" the driver.
> 
> Ah, OK. How do you load the driver? Doesn't pcmcia system load it 
> automagically when you plug the card in?
> 




From jkmaline  Thu Dec  7 19:18:39 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 7 Dec 2006 19:18:39 -0800
Subject: EAP-FAST inner Auth Fails
In-Reply-To: <52E5BF168B8CA143A198D856F73D5A9D0F6962@blr-m3-msg.wipro.com>
References: <52E5BF168B8CA143A198D856F73D5A9D0F6962@blr-m3-msg.wipro.com>
Message-ID: <20061208031838.GA6110@jm.kir.nu>

On Thu, Dec 07, 2006 at 03:28:04PM +0530, ramprasad.rajendran at wipro.com wrote:

> I am using wpa_supplicant-0.5.5 and hostapd as the authenticator and I
> am testing over a wired interface. 
> The radius server that I'm using is Steel Belted Radius
> I had commented out code related to certificate processing to reduce on
> the size.

I've never tested EAP-FAST with SBR, so I don't know what to expect from
it.

Which TLS library are you using? Patched OpenSSL?

> As soon as Phase1 suceeds, in phase 2, the Radius server requests for
> identity, without using any inner authentication.
> Is this correct? I guess an inner authentication method should start as
> part of phase 2
> 
> Attached alongwith is the output and my configuration file

Could you please send a debug log that shows the full EAP-FAST
authentication? The one attached to the message did not include any EAP
processing, not even the identity request.

Have you configured the RADIUS server to use EAP-FAST for the user that
you configured as the 'identity' in wpa_supplicant configuration? Are
you trying to use in-band provisioning first or has that already been
taken care of? I would suggest removing phase2 option for the initial
test because there are some limits on which EAP method can be used in
the tunneled phase 2.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Dec  7 19:20:50 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 7 Dec 2006 19:20:50 -0800
Subject: Fedora Core 5
In-Reply-To: <646338.88600.qm@web88005.mail.re2.yahoo.com>
References: <646338.88600.qm@web88005.mail.re2.yahoo.com>
Message-ID: <20061208032050.GB6110@jm.kir.nu>

On Thu, Dec 07, 2006 at 03:23:07PM -0500, Ben Z wrote:

>   Here's my setup: Panasonic Toughbook CF-29 - Intel Pentium M 1.6GHz
>                             Fedora Core 5 - 2.6.17 kernel ( Fedora Kernel 2.6.17-1.2157_FC5 )

>   I had to blacklist my orinoco driver (because this is a Prism-2 card, but the orinoco driver kept loading for it)
>    
>   When I try to install the hostap driver I get:
> 
>   ieee80211: 802.11 data/management/control stack, 1.2.15
> ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno at linux.intel.com>
> hostap: disagrees about version of symbol ieee80211_get_crypto_ops

This sounds like ieee80211 module with its version of crypto code gets
loaded first. This will likely cause problems since that version has
been modified from the original code in Host AP driver. I would suggest
trying to prevent ieee80211 from being loaded and make sure that the
Host AP version of crypto gets used here.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Dec  7 21:45:28 2006
From: jkmaline (Jouni Malinen)
Date: Thu, 7 Dec 2006 21:45:28 -0800
Subject: EAP-FAST inner Auth Fails
In-Reply-To: <52E5BF168B8CA143A198D856F73D5A9D0F6969@blr-m3-msg.wipro.com>
References: <52E5BF168B8CA143A198D856F73D5A9D0F6969@blr-m3-msg.wipro.com>
Message-ID: <20061208054528.GC6110@jm.kir.nu>

On Fri, Dec 08, 2006 at 10:37:44AM +0530, ramprasad.rajendran at wipro.com wrote:

> TLSv1: Received Finished
> TLSv1: Handshake completed successfully
> SSL: No data to be sent out
> EAP-FAST: TLS done, proceed to Phase 2

OK, so the TLS handshake does indeed seem to be completed successfully.

> EAP-FAST: Decrypted Phase 2 TLV(s) - hexdump(len=9): 80 09 00 05 01 01 00 05 01
> EAP-FAST: received Phase 2: TLV type 9 length 5 (mandatory)
> EAP-FAST: EAP Payload TLV - hexdump(len=5): 01 01 00 05 01
> EAP-FAST: Phase 2 Request: type=1

And the server is sending out EAP-Request/Identity frame in the tunnel
and that is received successfully.

> EAP: using real identity - hexdump_ascii(len=4):
>      74 65 73 74                                       test
> EAP-FAST: Encrypting Phase 2 data - hexdump(len=13): 80 09 00 09 02 04 00 09 01 74 65 73 74

The EAP-Response/Identity from the client looks fine, too.

> EAP-FAST: Decrypted Phase 2 TLV(s) - hexdump(len=6): 80 03 00 02 00 02
> EAP-FAST: Result TLV - hexdump(len=2): 00 02
> EAP-FAST: Result: Failure

But the server is rejecting this identity.

Have you been able to use this server with another client
implementation? Are you sure that the server is configured to allow this
identity to be used? Do you have access to the logs from the server?

-- 
Jouni Malinen                                            PGP id EFC895FA



From ramprasad.rajendran  Thu Dec  7 22:06:03 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Fri, 8 Dec 2006 11:36:03 +0530
Subject: EAP-FAST inner Auth Fails
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F696D@blr-m3-msg.wipro.com>



>-----Original Message-----
>From: hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com 
>[mailto:hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com]
> On Behalf Of Jouni Malinen
>Sent: Friday, December 08, 2006 11:15 AM
>To: hostap at shmoo.com
>Subject: Re: EAP-FAST inner Auth Fails
>
>> EAP-FAST: Decrypted Phase 2 TLV(s) - hexdump(len=9): 80 09 
>00 05 01 01 
>> 00 05 01
>> EAP-FAST: received Phase 2: TLV type 9 length 5 (mandatory)
>> EAP-FAST: EAP Payload TLV - hexdump(len=5): 01 01 00 05 01
>> EAP-FAST: Phase 2 Request: type=1
>
>And the server is sending out EAP-Request/Identity frame in 
>the tunnel and that is received successfully.

Is this fine. Can the server just ask for a request identity inside the
tunnel instead of using any authentication method like GTC or MSCHAPV2.
The documentation at the server says, the following
"
1. In Phase 0, a client without a valid PAC opens a connection through a
RAS to the
Steel-Belted Radius server. Steel-Belted Radius uses EAP-MS-CHAPv2 to
authenticate the user. If authentication is successful, Steel-Belted
Radius generates a
PAC for the user. and returns an Access-Reject message that contains the
PAC.
If a client already has a valid PAC, Phase 0 is omitted.

2. In Phase 1, the client and the Steel-Belted Radius server establish a
TLS tunnel
based on the PAC presented by the user. During Phase 1, the server
verifies that the
PAC presented by the client was generated by its current or retired
server secret.

3. In Phase 2, the server authenticates the user or machine credentials
using EAP-GTC
inside the protected TLS tunnel. If the PAC is valid and the user's
credentials are
correct, the authentication succeeds and Steel-Belted Radius returns an
Access-Accept message. If the user's PAC is due to expire soon,
Steel-Belted Radius
provisions the client with a new PAC over the secure network connection
at the end
of Phase 2..

I don't think the server shows this behaviour.

>
>> EAP: using real identity - hexdump_ascii(len=4):
>>      74 65 73 74                                       test
>> EAP-FAST: Encrypting Phase 2 data - hexdump(len=13): 80 09 
>00 09 02 04 
>> 00 09 01 74 65 73 74
>
>The EAP-Response/Identity from the client looks fine, too.
>
>> EAP-FAST: Decrypted Phase 2 TLV(s) - hexdump(len=6): 80 03 
>00 02 00 02
>> EAP-FAST: Result TLV - hexdump(len=2): 00 02
>> EAP-FAST: Result: Failure
>
>But the server is rejecting this identity.
>
>Have you been able to use this server with another client 
>implementation? Are you sure that the server is configured to 
>allow this identity to be used? Do you have access to the logs 
>from the server?

The server's log says the following

==> authReports/rejects_20061208.csv <==
"2006-12-08","11:29:51","<ANY>","test","EAP-FAST","User name or
credential incorrect","Inner EAP-FAST authentication
failed","10.114.2.53"

==> 20061208.log <==
12/08/2006 11:29:51 User test ultimately failed challenge sequence
12/08/2006 11:29:51 Sent reject response

I haven't tried the server with any other client. 
Though I've tested this SBR server and the supplicant with EAP-MSCHAPV2
and EAP-MD5 and they are working perfectly fine.

--
ram

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


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From david.goodenough  Fri Dec  8 06:34:03 2006
From: david.goodenough (David Goodenough)
Date: Fri, 8 Dec 2006 14:34:03 +0000
Subject: Relationship between Link quality and signal level
Message-ID: <200612081434.04535.david.goodenough@btconnect.com>

Why would I get:- 

         Link Quality:0/92  Signal level:-69 dBm  Noise level:-90 dBm
 
from iwconfig?  Normally the link quality first number is roughly the
difference between the signal level and the noise level, but here is
reports 0.

The other end of this link reports a more healthy link quality:-

          Link Quality:30/92  Signal level:-79 dBm  Noise level:-100 dBm
 
but (I presume because the first one says 0) the current rate is 1Mb/s

This link is running ad-hoc, these are the only two stations on this 
network, and neither end can detect (using iwlist scan) any other users
on this channel.  There is a clear line of site, and there are virtually
no buildings in between to generate any non-802.11 interference.

Both ends are using Senao PCMCIA 802.11b cards, prism chipset, both
at 1.8.0 firmware.

Any ideas welcome.

David



From jkmaline  Fri Dec  8 07:06:43 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 8 Dec 2006 07:06:43 -0800
Subject: EAP-FAST inner Auth Fails
In-Reply-To: <52E5BF168B8CA143A198D856F73D5A9D0F696D@blr-m3-msg.wipro.com>
References: <52E5BF168B8CA143A198D856F73D5A9D0F696D@blr-m3-msg.wipro.com>
Message-ID: <20061208150643.GA6105@jm.kir.nu>

On Fri, Dec 08, 2006 at 11:36:03AM +0530, ramprasad.rajendran at wipro.com wrote:

> >And the server is sending out EAP-Request/Identity frame in 
> >the tunnel and that is received successfully.
> 
> Is this fine. Can the server just ask for a request identity inside the
> tunnel instead of using any authentication method like GTC or MSCHAPV2.

It is normal to first ask for the real identity inside the encrypted
tunnel to protect the privacy of the user identity. This means that the
anonymous_identity in wpa_supplicant configuration is sent in plain, but
the identity value is only send in the encrypted tunnel.

EAP-GTC or EAP-MSCHAPv2 is supposed to follow this identity query in the
tunnel.

> The server's log says the following
> 
> ==> authReports/rejects_20061208.csv <==
> "2006-12-08","11:29:51","<ANY>","test","EAP-FAST","User name or
> credential incorrect","Inner EAP-FAST authentication
> failed","10.114.2.53"

This sounds like the "test" user would not be properly configured in the
server. This identity was rejected even before starting EAP-MSCHAPv2.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Fri Dec  8 07:19:28 2006
From: dcbw (Dan Williams)
Date: Fri, 08 Dec 2006 10:19:28 -0500
Subject: Relationship between Link quality and signal level
In-Reply-To: <200612081434.04535.david.goodenough@btconnect.com>
References: <200612081434.04535.david.goodenough@btconnect.com>
Message-ID: <1165591168.2779.41.camel@localhost.localdomain>

On Fri, 2006-12-08 at 14:34 +0000, David Goodenough wrote:
> Why would I get:- 
> 
>          Link Quality:0/92  Signal level:-69 dBm  Noise level:-90 dBm
>  
> from iwconfig?  Normally the link quality first number is roughly the
> difference between the signal level and the noise level, but here is
> reports 0.

This varies between drivers.  But the "correct" way to report link
quality is:

- Signal level: raw signal level either in dBm or RSSI from the card
- Link Quality: a subjective measure of how good the link is, including
signal strength, speed the link is operating at vs. capable speed,
packet loss, retries, etc.

Link Quality in correctly-written drivers should be a value in the range
[0, 100] inclusive representing a percentage between "worst" link and
"best" link.

Signal level is just the raw measure of RF energy received by the radio
on the card and is one component of link quality.

Link quality in Linux wireless drivers has never been extremely
reliable, though this is getting much better as time goes on.  The ipw
drivers are good examples of how to do link quality correctly.

> The other end of this link reports a more healthy link quality:-
> 
>           Link Quality:30/92  Signal level:-79 dBm  Noise level:-100 dBm
>  
> but (I presume because the first one says 0) the current rate is 1Mb/s
> 
> This link is running ad-hoc, these are the only two stations on this 
> network, and neither end can detect (using iwlist scan) any other users
> on this channel.  There is a clear line of site, and there are virtually
> no buildings in between to generate any non-802.11 interference.
> 
> Both ends are using Senao PCMCIA 802.11b cards, prism chipset, both
> at 1.8.0 firmware.

What kernel version and hostap driver version are you using?  The link
quality is calculated by the _driver_, not by the card or firmware, and
the different may be due to different driver versions.

Dan

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




From asattari  Fri Dec  8 10:06:34 2006
From: asattari (asattari at site.uottawa.ca)
Date: Fri, 8 Dec 2006 13:06:34 -0500 (EST)
Subject: Relationship between Link quality and signal level
In-Reply-To: <1165591168.2779.41.camel@localhost.localdomain>
References: <200612081434.04535.david.goodenough@btconnect.com>
	<1165591168.2779.41.camel@localhost.localdomain>
Message-ID: <2237.127.0.0.1.1165601194.squirrel@127.0.0.1>

hello,

In my thesis there was a subsection about this issue, hope it helps you

Yours
Afsaneh



There is an inconsistency in the way terms such as, ?signal strength?,
?signal quality?, and ?signal to noise ratio? are used by researchers,
developers and users, when it comes to the 802.11 standard. At the
beginning of our test, it was not clear what the signal strength values
reported by each of our computers represented or if they were correct.
>From our personal observations, and after researching this subject, we
came to the conclusion that, this confusion arises when common terms are
used with inconsistent definition, or misunderstanding of the common terms
leads to false conclusions. In [CHIV-4] we find the precise definitions of
the above terms (those definitions coming from reliable sources such as
802.11 standards), as follows:

?? Signal strength is defined in 802.11 as the Received Signal Strength
Indicator
(RSSI). RSSI, is intended to be used as a ?relative value? within the
chipset. This is a 1-byte value so that it could have values ranging from
0 to 255, but vendors prefer to use arbitrary scales from 0 to RSSI_Max
where the latter is vendor-specific (for instance, Cisco uses 101, Symbol
31, Atheros 60).  It is not associated with any particular power scale 
(e.g. mW) and is not required to be of any particular accuracy or
precision. The RSSI value is used internally by the microcode in the
adapter and this is why vendors are not forced to use a compatible
standard. As an example of its use, if the RSSI value is below some
threshold, the NIC knows that the channel is idle. Therefore, the signal
strength numbers reported by an 802.11 card will probably not be
consistent between two
vendors, and should not be assumed to be particularly accurate or precise
(Details are provided below).

? Signal quality is defined very briefly in the 802.11 standard. Common
definitions have
arisen, but they are usually incorrect. The correct definition hinges on the
term, ?PN code correlation strength,? which is a measure of the match
(correlation) between the incoming DSSS signal and an ideal DSSS signal.

? Signal to noise ratio is a general term that is used in a novel way by
802.11
administrators. Most usages of the term refer to the strength of the signal
relative to thermal noise within a circuit  , but many professionals, use the
term to refer to the strength of the signal at the receive antenna
relative to the
ambient, non-802.11 RF power that is  present at the bandwidth occupy by
the signal. According to the standard communications systems terminology,
SNR is defined as the ratio of received signal power to the power of the
additive Gaussian noise that appears at the output of the receiver. While
thesedefinitions are not  wrong, they may lead to confusion when 802.11
professionals communicate among themselves.

? Receive sensitivity refers to the weakest power level the card?s internal
thermal noise will allow it to receive. It is unrelated to the ambient, non-
802.11 RF energy in the environment. [CHIV-4].
4.2.2	Measurement Units for RF Signal Strength

There are four Units of measurements that are used to represent RF Signal
Strength: mW( milliwatts), dBm (?dB?-milliwatts), RSSI (Received Signal
Strength Indicator), and a percentage measurement.
Equation (4.1) shows that ?dBm? is a logarithmic measurement of signal
strength and dBm values can be directly converted to and from mW values.

dBm = log10 (mW) * 10                                                     
                      		(4.1)

RSSI, which has been explained earlier, is an arbitrary integer, with an
allowable range of 0-255 (a 1-byte value) defined in the 802.11 standard.
This value is used internally by the micro-code of the adaptor and by the
device driver. For example, when an adaptor wants to transmit a packet, it
is checking whether the channel is clear (i.e.: no one else is
transmitting) or not. If the RSSI value is below a certain low value, the
chipset knows that the channel is clear [CHIV-6].
No vendors have chosen to measure 256 different signal level values.  Each
of the 802.11 NIC?s vendors adopts and uses a specific maximum RSSI value
(RSSI_Max). For example, Cisco chooses to measure 101 separate values for
RF energy and their RSSI_Max is 100. Symbol uses an RSSI_Max value of 31.
The Atheros chipset uses the RSSI_Max value of 60. In Appendix B, more
details information is provided.
When using RSSI as basis for reporting dBm signal strength, it is common
to see the signal strength been represented as a percentage. The
percentage represents the RSSI for a specific packet, which constitutes
practically the division between the measured to the maximum (RSSI_Max)
value, multiplied by 100 (in order to derive the percentage). For example,
when the signal level is 50%, this is reported with different values of
RSSI, depending on the vendor;  a Symbol card would convert to an RSSI of
16, because its RSSI_Max =31, Atheros, with RSSI_Max = 60, would convert
it to an RSSI of 30, and for Cisco, which is the easiest one because its
RSSI_Max = 100,  RSSI is 50.
Unfortunately, we still do not know how all vendors map RSSI to signal
strength percentage. This lack of consistency between vendors, does not
allow for direct comparison of performance evaluation results, performed
with equipment of different vendors.

?Signal quality? is also reported by vendors? client utilities. Those, who
are working with IEEE 802.11 products, are aware that these two
parameters, ?signal strength? and ?signal quality?, are the two metrics
for assessing the ?goodness? of the 802.11 signal. Unfortunately, other
that the definition of ?signal quality? we provided earlier in section
4.2.1, the 802.11 standard does not offer further information.  Based on
the definition, the authors of  [CHIV-6] conclude that ?signal quality?
?reflects the amount of signal within the channel formed between the two
communicating stations (e.g. an AP and a client). The above description is
consistent among the manufacturers.  For example a manufacturer might say
that an IEEE 802.11b chipset needs a minimum of 20 dBm signal quality in
order to achieve 11 Mbps data rate. But the 802.11 standard, does not
define a specific method of calculating and reporting the ?signal
quality?, and, as in the case of ?signal strength?, the vendors measure it
using inconsistent methods. The IEEE 802.11 standard defines ?Signal to
Noise Ratio? (SNR), as can be seen in section 4.2.1.  However, since
802.11 cards do not typically report SNR, practically the concept of SNR
is not used.














> On Fri, 2006-12-08 at 14:34 +0000, David Goodenough wrote:
>> Why would I get:-
>>
>>          Link Quality:0/92  Signal level:-69 dBm  Noise level:-90 dBm
>>
>> from iwconfig?  Normally the link quality first number is roughly the
>> difference between the signal level and the noise level, but here is
>> reports 0.
>
> This varies between drivers.  But the "correct" way to report link
> quality is:
>
> - Signal level: raw signal level either in dBm or RSSI from the card
> - Link Quality: a subjective measure of how good the link is, including
> signal strength, speed the link is operating at vs. capable speed,
> packet loss, retries, etc.
>
> Link Quality in correctly-written drivers should be a value in the range
> [0, 100] inclusive representing a percentage between "worst" link and
> "best" link.
>
> Signal level is just the raw measure of RF energy received by the radio
> on the card and is one component of link quality.
>
> Link quality in Linux wireless drivers has never been extremely
> reliable, though this is getting much better as time goes on.  The ipw
> drivers are good examples of how to do link quality correctly.
>
>> The other end of this link reports a more healthy link quality:-
>>
>>           Link Quality:30/92  Signal level:-79 dBm  Noise level:-100 dBm
>>
>> but (I presume because the first one says 0) the current rate is 1Mb/s
>>
>> This link is running ad-hoc, these are the only two stations on this
>> network, and neither end can detect (using iwlist scan) any other users
>> on this channel.  There is a clear line of site, and there are virtually
>> no buildings in between to generate any non-802.11 interference.
>>
>> Both ends are using Senao PCMCIA 802.11b cards, prism chipset, both
>> at 1.8.0 firmware.
>
> What kernel version and hostap driver version are you using?  The link
> quality is calculated by the _driver_, not by the card or firmware, and
> the different may be due to different driver versions.
>
> Dan
>
>> Any ideas welcome.
>>
>> David
>> _______________________________________________
>> 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
>


-- 

"Whatever is deserved to be admired not ought to being plunder"---- 
Margot Bigel





From jkmaline  Fri Dec  8 20:12:55 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 8 Dec 2006 20:12:55 -0800
Subject: EAP-FAST inner Auth Fails
In-Reply-To: <52E5BF168B8CA143A198D856F73D5A9D0F696D@blr-m3-msg.wipro.com>
References: <52E5BF168B8CA143A198D856F73D5A9D0F696D@blr-m3-msg.wipro.com>
Message-ID: <20061209041255.GD6105@jm.kir.nu>

On Fri, Dec 08, 2006 at 11:36:03AM +0530, ramprasad.rajendran at wipro.com wrote:
> 
> The server's log says the following
> 
> ==> authReports/rejects_20061208.csv <==
> "2006-12-08","11:29:51","<ANY>","test","EAP-FAST","User name or
> credential incorrect","Inner EAP-FAST authentication
> failed","10.114.2.53"
> 
> ==> 20061208.log <==
> 12/08/2006 11:29:51 User test ultimately failed challenge sequence
> 12/08/2006 11:29:51 Sent reject response

SBR is not very helpful with the debug log.. I tried to enable full
debugging and even with that, the server was only saying that inner auth
failed.

After looking at what exactly was being sent in the inner
EAP-Response/Identity, I found a bug in wpa_supplicant. It was using
incorrect EAP identifier in this message (the one from the outer
EAP-Request and SBR happened to be using different identifier in the
inner request and refused to accept the response because of the
mismatch).

This is now fixed in the CVS version of wpa_supplicant (in both 0.5.x
and 0.6.x branches) and the fix is included in the latest snapshots. I
was able to complete EAP-FAST provisioning and authentication against
SBR with this version.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec  9 15:53:29 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 9 Dec 2006 15:53:29 -0800
Subject: [PATCH] dbus ctrl interface: fix reply message success argument
In-Reply-To: <1165262287.25362.4.camel@localhost.localdomain>
References: <1165262287.25362.4.camel@localhost.localdomain>
Message-ID: <20061209235328.GA6126@jm.kir.nu>

On Mon, Dec 04, 2006 at 02:58:07PM -0500, Dan Williams wrote:

> A mistype caused the success argument not to be added to the reply
> message.

Thanks for this and the other patches. I applied all four patches into
the development branch (0.6.x). Should these be merged into 0.5.x for
the stable release 0.5.7? Some of the patches were clear bug fixes, but
I'm not fully sure about all of them. The current policy on 0.5.x is
that only bug fixes are accepted at this point.

-- 
Jouni Malinen                                            PGP id EFC895FA



From andrzej.boron  Sat Dec  9 17:05:07 2006
From: andrzej.boron (Andrzej Boron)
Date: Sun, 10 Dec 2006 02:05:07 +0100
Subject: kernel 2.6.17.14 & WL 200 & udev
Message-ID: <001801c71bf7$3c275070$640a010a@x9a316f6e3eec4>

Hi

Anyone know why hostap driver not starting ???


lspci -vvv

0000:00:0e.0 PCMCIA bridge: Cirrus Logic CL 6729 (rev 07)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 2030 [size=4]




lspcmcia -vv



Socket 0 Bridge:        [pd6729]        (bus ID: 0000:00:0e.0)
        Configuration:  state: on       ready: yes
                        Voltage: 3.3V Vcc: 3.3V Vpp: 3.3V
                        Available IRQs: none
                        Available ioports:      0x00000100 - 0x0000016f
                                                0x00000178 - 0x0000021f
                                                0x00000230 - 0x00000267
                                                0x00000270 - 0x000002e7
                                                0x000002f0 - 0x0000032f
                                                0x00000338 - 0x0000036f
                                                0x00000380 - 0x00000387
                                                0x00000390 - 0x000003f7
                                                0x00000400 - 0x000004ff
                                                0x00000800 - 0x000008ff
                                                0x00000a00 - 0x00000aff
                                                0x00000c08 - 0x00000c4f
                                                0x00000c58 - 0x00000c7f
                                                0x00000c88 - 0x00000cf7
                        Available iomem:        0x000c0000 - 0x000fffff
                                                0xa0000000 - 0xa0ffffff
Socket 0 Device 0:      [-- no driver --]       (bus ID: 0.0)
        Configuration:  state: on
        Product Name:   Compaq WL200_11Mbps_Wireless_PCI_Card
        Identification: manf_id: 0x0138 card_id: 0x0002
                        function: 6 (network)
                        prod_id(1): "Compaq" (0x54f7c49c)
                        prod_id(2): "WL200_11Mbps_Wireless_PCI_Card" 
(0x15a75e5b)
                        prod_id(3): --- (---)
                        prod_id(4): --- (---)
Socket 1 Bridge:        [pd6729]        (bus ID: 0000:00:0e.0)
        Configuration:  state: on       ready: yes
                        Available IRQs: none
                        Available ioports:      0x00000100 - 0x0000016f
                                                0x00000178 - 0x0000021f
                                                0x00000230 - 0x00000267
                                                0x00000270 - 0x000002e7
                                                0x000002f0 - 0x0000032f
                                                0x00000338 - 0x0000036f
                                                0x00000380 - 0x00000387
                                                0x00000390 - 0x000003f7
                                                0x00000400 - 0x000004ff
                                                0x00000800 - 0x000008ff
                                                0x00000a00 - 0x00000aff
                                                0x00000c08 - 0x00000c4f
                                                0x00000c58 - 0x00000c7f
                                                0x00000c88 - 0x00000cf7
                        Available iomem:        0x000c0000 - 0x000fffff
                                                0x60000000 - 0x60ffffff
                                                0xa0000000 - 0xa0ffffff



DMESG



Linux version 2.6.17.14 (root) (gcc version 4.1.2 20060901 (prerelease) 
(Debian 4.1.1-13)) #2 Sun Dec 10 01:01:48 CET 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
 BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
512MB LOWMEM available.
On node 0 totalpages: 131072
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 126976 pages, LIFO batch:31
DMI 2.1 present.
ACPI: RSDP (v000 COMPAQ                                ) @ 0x000e0010
ACPI: RSDT (v001 COMPAQ CPQB053  0x19990821  0x00000000) @ 0x000e0080
ACPI: FADT (v001 COMPAQ SCARAB   0x00000001  0x00000000) @ 0x000e00cc
ACPI: SSDT (v001 COMPAQ VILLTBL1 0x00000001 MSFT 0x0100000b) @ 0x000e09c3
ACPI: SSDT (v001 COMPAQ PNP_PRSS 0x00000001 MSFT 0x0100000b) @ 0x000e19c0
ACPI: SSDT (v001 COMPAQ      PME 0x00000001 MSFT 0x0100000b) @ 0x000e2134
ACPI: DSDT (v001 COMPAQ     DSDT 0x00000001 MSFT 0x0100000b) @ 0x00000000
ACPI: PM-Timer IO Port: 0xf808
Allocating PCI resources starting at 30000000 (gap: 20000000:dffc0000)
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 597.020 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 516076k/524288k available (2199k kernel code, 7732k reserved, 676k 
data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1194.97 BogoMIPS 
(lpj=2389949)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 
00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000 
00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Coppermine) stepping 01
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 0k freed
ACPI: setting ELCR to 0200 (from 0800)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xed8e3, last bus=1
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region f800-f83f claimed by PIIX4 ACPI
PCI quirk: region fc00-fc0f claimed by PIIX4 SMB
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 15 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a 
report
pnp: 00:0c: ioport range 0x15c-0x15d has been reserved
pnp: 00:0c: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:0d: ioport range 0xf800-0xf81f could not be reserved
pnp: 00:0d: ioport range 0xf820-0xf83f has been reserved
pnp: 00:0d: ioport range 0xfc00-0xfc0f has been reserved
PCI: Bridge: 0000:00:01.0
  IO window: 1000-1fff
  MEM window: 40000000-400fffff
  PREFETCH window: 41000000-41ffffff
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 65536 bind 32768)
TCP reno registered
Machine check exception polling timer started.
* Found PM-Timer Bug on this chipset. Due to workarounds for a bug,
* this time source is slow.  Consider trying other time sources (clock=)
audit: initializing netlink socket (disabled)
audit(1165713256.200:1): initialized
SGI XFS with security attributes, no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Limiting direct PCI/PCI transfers.
ACPI: Power Button (CM) [PBTN]
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 8 throttling states)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
lp: driver loaded but no devices found
Real Time Clock Driver v1.12ac
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> 
IRQ 11
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0d.0: 3Com PCI 3c905 Boomerang 100baseTx at 00012080.
orinoco 0.15rc3 (David Gibson <hermes at gibson.dropbear.id.au>, Pavel Roskin 
<proski at gnu.org>, et al)
orinoco_pci 0.15rc3 (Pavel Roskin <proski at gnu.org>, David Gibson 
<hermes at gibson.dropbear.id.au> & Jean Tourrilhes <jt at hpl.hp.com>)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:14.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x2020-0x2027, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x2028-0x202f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: WDC WD800JB-00FSA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63, 
UDMA(33)
hda: cache flushes supported
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> 
IRQ 11
pd6729: Cirrus PD6729 PCI to PCMCIA Bridge at 0x2030 on irq 11
pd6729: PCI card interrupts, PCI status changes
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
PNP: PS/2 Controller [PNP0303:KBD,PNP0f0e:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
Advanced Linux Sound Architecture Driver Version 1.0.11rc4 (Wed Mar 22 
10:27:24 2006 UTC).
ALSA device list:
  No soundcards found.
oprofile: using timer interrupt.
netem: version 1.2
u32 classifier
    Perfomance counters on
ip_conntrack version 2.4 (4096 buckets, 32768 max) - 224 bytes per conntrack
input: AT Translated Set 2 keyboard as /class/input/input0
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
Ebtables v2.0 registered
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation 
<jketreno at linux.intel.com>
ieee80211_crypt: registered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'WEP'
ieee80211_crypt: registered algorithm 'CCMP'
ieee80211_crypt: registered algorithm 'TKIP'
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 148k freed
pccard: PCMCIA card inserted into slot 0
cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x220-0x22f 0x268-0x26f 
0x2e8-0x2ef 0x330-0x337 0x370-0x37f 0x388-0x38f 0x3f8-0x3ff
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xc00-0xcff: excluding 0xc00-0xc07 0xc50-0xc57 0xc80-0xc87 
0xcf8-0xcff
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x220-0x22f 0x268-0x26f 
0x2e8-0x2ef 0x330-0x337 0x370-0x37f 0x388-0x38f 0x3f8-0x3ff
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xc00-0xcff: excluding 0xc00-0xc07 0xc50-0xc57 0xc80-0xc87 
0xcf8-0xcff
cs: IO port probe 0xa00-0xaff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3) is a NS16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS3 at I/O 0x2e8 (irq = 3) is a NS16550A
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> 
IRQ 11
e100: eth1: e100_probe: addr 0x42200000, irq 11, MAC addr 00:08:C7:FF:57:13
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:14.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> 
IRQ 11
uhci_hcd 0000:00:14.2: UHCI Host Controller
uhci_hcd 0000:00:14.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:14.2: irq 11, io base 0x00002000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Adding 506008k swap on /dev/hda9.  Priority:-1 extents:1 across:506008k
EXT3 FS on hda1, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover.
pcmcia: This interface will soon be removed from the kernel; please expect 
breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html 
for details.
NET: Registered protocol family 15
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> 
IRQ 11
eth0:  setting full-duplex.
ttyS2: LSR safety check engaged!
ttyS2: LSR safety check engaged!
CAPI Subsystem Rev 1.1.2.8
capifs: Rev 1.1.2.3
capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
ip_tables: (C) 2000-2006 Netfilter Core Team
IPP2P v0.8.2 loading





From dcbw  Sat Dec  9 20:16:46 2006
From: dcbw (Dan Williams)
Date: Sat, 09 Dec 2006 23:16:46 -0500
Subject: [PATCH] dbus ctrl interface: fix reply message success argument
In-Reply-To: <20061209235328.GA6126@jm.kir.nu>
References: <1165262287.25362.4.camel@localhost.localdomain>
	<20061209235328.GA6126@jm.kir.nu>
Message-ID: <1165724206.23318.8.camel@localhost.localdomain>

On Sat, 2006-12-09 at 15:53 -0800, Jouni Malinen wrote:
> On Mon, Dec 04, 2006 at 02:58:07PM -0500, Dan Williams wrote:
> 
> > A mistype caused the success argument not to be added to the reply
> > message.
> 
> Thanks for this and the other patches. I applied all four patches into
> the development branch (0.6.x). Should these be merged into 0.5.x for
> the stable release 0.5.7? Some of the patches were clear bug fixes, but

Yes, they should all go into 0.5.x too.  They are pretty much bug fixes,
or omissions in the DBus API that I noticed while hooking up the
NetworkManager bits to wpa_supplicant.  They don't break backwards
compatibility for the DBus API with any previous versions.

If you want to be _really_ strict, you can drop the "add interface
'state'" patch from 0.5.x, but without it you can't get the interface's
initial state (though a signal is sent when the state changes).  Again,
this does not break anything, but adds the additional method call.

Thanks!
Dan

> I'm not fully sure about all of them. The current policy on 0.5.x is
> that only bug fixes are accepted at this point.
> 




From sud_NOSPAM  Sat Dec  9 20:42:08 2006
From: sud_NOSPAM (SuD)
Date: Sun, 10 Dec 2006 05:42:08 +0100
Subject: Hostap_cs shared irq oops
Message-ID: <457B9020.1040101@latinsud.com>

Hi, I recently upgraded to kernel 2.6.18.2 and noticed these problems:
 - I realized that having CONFIG_ISA=y makes it always crash when i 
insert the card (complains about unexpected LVT TMR interrupt). So i 
disabled Isa.
 - Hostap_cs gets a shared Irq (this didn't happen with kernel 
2.6.15.6). It crashes if the interrupt is triggered while the device is 
not fully initialized (Error is: "Divide error 0000 [#1]"). I can 
workaround that by using a flag and inserting a "if (!my_init_flag) { 
return IRQ_HANDLED }" at the begining of the irq handler.

- I don't know much about irq allocation. Can i try something to get my 
separate irq back?
- Should i try different configuration or 2.6.19?
- Should hostap_cs be enhanced to support shared irq?

I use debian etch. Laptop is a G200N 1.7GHz Centrino.

My /proc/interrupts in 2.6.18.2:
           CPU0
  0:     756865          XT-PIC  timer
  1:      11062          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:      30453          XT-PIC  uhci_hcd:usb3, eth0
  9:     306542          XT-PIC  acpi
 10:      40192          XT-PIC  ohci1394, yenta, ipw2200, 
ehci_hcd:usb1, uhci_hcd:usb4, Intel 82801DB-ICH4, pcmcia0.0
 11:     167128          XT-PIC  uhci_hcd:usb2, i915 at pci:0000:00:02.0
 12:     226854          XT-PIC  i8042
 14:      48281          XT-PIC  ide0
 15:      24932          XT-PIC  ide1

Some acpi boot messages:
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs *10)
ACPI: PCI Interrupt Link [LNKC] (IRQs *10)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5) *11
ACPI: PCI Interrupt Link [LNKE] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKF] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Embedded Controller [EC0] (gpe 29) interrupt mode.
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PFN1] (off)

Thanks, please CC me if you can (works both with or without the "_nospam").




From jkmaline  Sat Dec  9 20:35:33 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 9 Dec 2006 20:35:33 -0800
Subject: [PATCH] dbus ctrl interface: fix reply message success argument
In-Reply-To: <1165724206.23318.8.camel@localhost.localdomain>
References: <1165262287.25362.4.camel@localhost.localdomain>
	<20061209235328.GA6126@jm.kir.nu>
	<1165724206.23318.8.camel@localhost.localdomain>
Message-ID: <20061210043533.GB6126@jm.kir.nu>

On Sat, Dec 09, 2006 at 11:16:46PM -0500, Dan Williams wrote:

> Yes, they should all go into 0.5.x too.  They are pretty much bug fixes,
> or omissions in the DBus API that I noticed while hooking up the
> NetworkManager bits to wpa_supplicant.  They don't break backwards
> compatibility for the DBus API with any previous versions.

OK. I merged all the patches for 0.5.7.

> If you want to be _really_ strict, you can drop the "add interface
> 'state'" patch from 0.5.x, but without it you can't get the interface's
> initial state (though a signal is sent when the state changes).  Again,
> this does not break anything, but adds the additional method call.

Well, I'm quite strict for non-fixes at this point, but I can make a
small exception for dbus ctrl_iface and similar separate components.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jar  Sun Dec 10 03:23:17 2006
From: jar (Jar)
Date: Sun, 10 Dec 2006 13:23:17 +0200
Subject: kernel 2.6.17.14 & WL 200 & udev
In-Reply-To: <001801c71bf7$3c275070$640a010a@x9a316f6e3eec4>
References: <001801c71bf7$3c275070$640a010a@x9a316f6e3eec4>
Message-ID: <457BEE25.4060403@pcuf.fi>

Andrzej Boron wrote:
> Hi
> 
> Anyone know why hostap driver not starting ???

Compaq WL200 + Fedora6 2.6.18-1.2798.fc6 is working fine here. First try 
to blacklist: ieee80211, orinoco, orinoco_pci, orinoco_plx, orinoco_cs 
and hermes modules.

-- 
Best Regards, Jar



From bayar  Sun Dec 10 20:18:40 2006
From: bayar (Erdenebayar Buriad)
Date: Mon, 11 Dec 2006 13:18:40 +0900
Subject: Hostap & Bonding with ARP link monitoring
Message-ID: <005a01c71cdb$7027f1b0$64faa8c0@CGNTVC2>

Hi folks

I have problem, bonding with ARP link monitoring.

My testbed is simple, only two mobile nodes with 2 wireless interfaces, each 
node.
I planned to demonstrate bonding technology with ARP link monitoring, 
bonding mode 0 (balance-rr).
When I use MII monitoring for bonding, It was OK (bonding mode: 0,1,2,3).

But when I tried bonding with ARP link monitoring, It seams to be some 
problem. There was not any connection between nodes (between bonded 
interfaces). Each nodes sending ARP packets.
Also, I have not any boning error message when I configure bonding driver 
and interface.
Status bonding is DOWN in the "/proc/net/bonding/bond0".
I used this command on both nodes : "modprobe bonding mode=2 
arp_interval=1000 arp_ip_target=10.0.0.1"

---------
I am using Wireless interface: PRISM 3 chipset based wireless cards
driver : Hostap 0.4.7 (also I tried 0.4.9) and hostap-util 0.4.7
linux kernel -2.6.13.5 (RHEL 4)
---------

Have you any idea, please ?

Regards,
Bayaraa 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061211/fb7273d4/attachment.htm 


From ramprasad.rajendran  Mon Dec 11 05:35:15 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Mon, 11 Dec 2006 19:05:15 +0530
Subject: EAP-FAST inner Auth Fails
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F6978@blr-m3-msg.wipro.com>



Hi,

>
>>This is now fixed in the CVS version of wpa_supplicant (in
>>both 0.5.x and 0.6.x branches) and the fix is included in the 
>>latest snapshots. I was able to complete EAP-FAST provisioning 
>>and authentication against SBR with this version.
>
I downloaded the latest version from the CVS. I am still not through
with SBR and EAP-FAST. The initial request identity in 
phase 2 goes through, but the EAP-FAST Phase2(MSCHAPv2) fails with a
reject :-(.

Attached is the log for supplicant

Is the radius server sending the PAC along with the EAP-MSCHAP reject
message?

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



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: supplicant.log
Type: application/octet-stream
Size: 11256 bytes
Desc: supplicant.log
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061211/2ff373ac/attachment.obj 


From ramprasad.rajendran  Mon Dec 11 21:57:43 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Tue, 12 Dec 2006 11:27:43 +0530
Subject: EAP-FAST inner Auth Fails
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F6983@blr-m3-msg.wipro.com>


Hi,

>-----Original Message-----
>From: hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com 
>[mailto:hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com]
> On Behalf Of ramprasad.rajendran at wipro.com
>Sent: Monday, December 11, 2006 7:05 PM
>To: hostap at shmoo.com
>Subject: Re: EAP-FAST inner Auth Fails
>
>I downloaded the latest version from the CVS. I am still not 
>through with SBR and EAP-FAST. The initial request identity in 
>phase 2 goes through, but the EAP-FAST Phase2(MSCHAPv2) fails 
>with a reject :-(.
>
>Attached is the log for supplicant
>
>Is the radius server sending the PAC along with the EAP-MSCHAP 
>reject message?

I was able to do PAC provisioning and authentication using EAP-FAST with
Steel Belted Radius as the server. The size I was able to get was 149 K
on x86.
There was a minor configuration problem at the server.
Thanks!

>----
>Ram
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>
>
>The information contained in this electronic message and any 
>attachments to this message are intended for the exclusive use 
>of the addressee(s) and may contain proprietary, confidential 
>or privileged information. If you are not the intended 
>recipient, you should not disseminate, distribute or copy this 
>e-mail. Please notify the sender immediately and destroy all 
>copies of this message and any attachments. 
>
>WARNING: Computer viruses can be transmitted via email. The 
>recipient should check this email and any attachments for the 
>presence of viruses. The company accepts no liability for any 
>damage caused by any virus transmitted by this email.
> 
>www.wipro.com
>


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From yohonet  Tue Dec 12 00:53:14 2006
From: yohonet (Vincent Panel)
Date: Tue, 12 Dec 2006 09:53:14 +0100
Subject: TKIP: replay detected:
Message-ID: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>

Hi,

I get a lot of these messages in my kernel log :

kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
0000000004a9 received TSC 0000000004a8

I see a lot of people have the same problem, but I found no real
solution to this problem.

I'm using wpa_supplicant-0.5.5 and found nothing in the changelog of
wpa_supplicant 0.5.6 which lets me think there's a improvement.

I don't have access to the access point (it belongs to my company),
but I'm ready to test and provide you with any piece of necessary
information.

Thanks

Vincent.



From scallegari  Tue Dec 12 03:15:44 2006
From: scallegari (Sergio Callegari)
Date: Tue, 12 Dec 2006 12:15:44 +0100
Subject: wpa_supplicant fails and reports weird AP address in association
Message-ID: <457E8F60.1000706@arces.unibo.it>

Hi,

I am trying to set up a wireless network including an Hamlet access
point and a Linux laptop with an intel 3945 wireless interface.

Everything is fine as long as I limit myself to WEP security.

If I try to use WPA security with wpa_supplicant, things stop working.

Precisely I am getting the following problem

running

    wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -D wext

with the following wpa_supplicant.conf
network={
        ssid="XXXXXXXXX"
        scan_ssid=1
        proto=WPA
        key_mgmt=WPA-PSK
        psk="secure"
        pairwise=TKIP
        group=TKIP
}

associates but immediately dies reporting that the 4-Way handshake
is failing and suggesting a wrong pre-shared key (which is not the case).

Curiously, I have noticed the following inconsistency:

1) my AP MAC address should be AA:BB:CC:DD:EE:30 as reported on the AP 
web interface (only last byte is properly quoted here).

2) iwlist eth1 scan reports AA:BB:CC:DD:EE:33... i.e. the last byte is 
different in 3 bits.

3) By cross checking with another host (a windows one, to make the 
crosscheck more significant) I see that also the other host reports
AA:BB:CC:DD:EE:33 as the AP mac.

4) when wpa_supplicant reports association, it says it is associating 
with AA:BB:CC:DD:EE:33...

5) however, the subsequent debug of the 4 way
handshake shows AA:BB:CC:DD:EE:30 as the AP address...

May this has anything to do with the failed handshake?

Some information that might be useful:

Linux kernel is the ubuntu version of 2.6.17 (generic, i.e. SMP) on a
CORE 2 duo (DELL D820 laptop).
wireless driver is ipw3945, kernel module version 1.1.0mp
wpa_supplicant is version 0.5.4

any idea?

Sergio





From alex  Tue Dec 12 04:20:32 2006
From: alex (Alex Pounds)
Date: Tue, 12 Dec 2006 12:20:32 -0000 (GMT)
Subject: HostAP and WPA2 with Intersil Prism card
Message-ID: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>

Hello,

First up, let me explain that I am pretty ignorant of the world of wireless
networking. I've tried to find the answer to my question from the
documentation, but a lot of it seems tied to using HostAP to build an access
point, and a lot of it goes over my head.

I have a small home wireless network - just my desktop PC, in fact, which
uses a LinkSys router attached to the ADSL for its internet connection. The
router uses WPA2 for security. I have recently purchased a laptop that has
an Intersil Prism 2.5 card (see lspci output at
http://www.ethicsgirls.com/stuff/lspci.txt -
http://www.ethicsgirls.com/stuff/dmesg.txt may also be of some use) that
does not support WPA in-hardware.

My question is simple: Can I use hostAP to do the WPA2 part in software, and
thus use my laptop with my home network? If so, how? I've been told
conflicting things about wpa_supplicant (story 1: It needs hardware support.
Story 2: Hardware support is not neccessary, it needs driver support) and on
the whole I am hugely confused. If someone can let me know if this is
possible and point me to some simple documentation on how to set it up, I'd
be most grateful.

Thank you,

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^




From dcbw  Tue Dec 12 04:49:50 2006
From: dcbw (Dan Williams)
Date: Tue, 12 Dec 2006 07:49:50 -0500
Subject: TKIP: replay detected:
In-Reply-To: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
Message-ID: <1165927790.2747.3.camel@localhost.localdomain>

On Tue, 2006-12-12 at 09:53 +0100, Vincent Panel wrote:
> Hi,
> 
> I get a lot of these messages in my kernel log :
> 
> kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> 0000000004a9 received TSC 0000000004a8

What kernel and what driver are you using?

> I see a lot of people have the same problem, but I found no real
> solution to this problem.

Can you do some packet sniffing and figure out whether the TSC is really
going backwards between messages from the AP to your STA?  If so, it's
clearly an access point problem.  But before that, lets figure out what
driver you're using and make sure it's not one of the ones that's under
heavier development...

Dan

> I'm using wpa_supplicant-0.5.5 and found nothing in the changelog of
> wpa_supplicant 0.5.6 which lets me think there's a improvement.
> 
> I don't have access to the access point (it belongs to my company),
> but I'm ready to test and provide you with any piece of necessary
> information.
> Thanks
> 
> Vincent.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From dcbw  Tue Dec 12 04:53:40 2006
From: dcbw (Dan Williams)
Date: Tue, 12 Dec 2006 07:53:40 -0500
Subject: wpa_supplicant fails and reports weird AP address in association
In-Reply-To: <457E8F60.1000706@arces.unibo.it>
References: <457E8F60.1000706@arces.unibo.it>
Message-ID: <1165928020.2747.7.camel@localhost.localdomain>

On Tue, 2006-12-12 at 12:15 +0100, Sergio Callegari wrote:
> Hi,
> 
> I am trying to set up a wireless network including an Hamlet access
> point and a Linux laptop with an intel 3945 wireless interface.
> 
> Everything is fine as long as I limit myself to WEP security.
> 
> If I try to use WPA security with wpa_supplicant, things stop working.
> 
> Precisely I am getting the following problem
> 
> running
> 
>     wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -D wext
> 
> with the following wpa_supplicant.conf
> network={
>         ssid="XXXXXXXXX"
>         scan_ssid=1
>         proto=WPA
>         key_mgmt=WPA-PSK
>         psk="secure"

Is it really something with quotes?  First, try using the
'wpa-passhprase' tool or copy the actual _hex_ key from your AP's
configuration screen, and paste it into your wpa_supplicant
configuration like so:

	psk=11bbccddeeff223399...

i.e., _don't_ use quotes, and use the hexadecimal key rather than using
quotes here.  If you use quotes, wpa_supplicant interprets the config
option as a string, which clearly isn't what you want here.  And I don't
believe that wpa_supplicant supports passphrase hashing for WPA
internally, that's what wpa-passphrase is for.

Dan

>         pairwise=TKIP
>         group=TKIP
> }
> 
> associates but immediately dies reporting that the 4-Way handshake
> is failing and suggesting a wrong pre-shared key (which is not the case).
> 
> Curiously, I have noticed the following inconsistency:
> 
> 1) my AP MAC address should be AA:BB:CC:DD:EE:30 as reported on the AP 
> web interface (only last byte is properly quoted here).
> 
> 2) iwlist eth1 scan reports AA:BB:CC:DD:EE:33... i.e. the last byte is 
> different in 3 bits.
> 
> 3) By cross checking with another host (a windows one, to make the 
> crosscheck more significant) I see that also the other host reports
> AA:BB:CC:DD:EE:33 as the AP mac.
> 
> 4) when wpa_supplicant reports association, it says it is associating 
> with AA:BB:CC:DD:EE:33...
> 
> 5) however, the subsequent debug of the 4 way
> handshake shows AA:BB:CC:DD:EE:30 as the AP address...
> 
> May this has anything to do with the failed handshake?
> 
> Some information that might be useful:
> 
> Linux kernel is the ubuntu version of 2.6.17 (generic, i.e. SMP) on a
> CORE 2 duo (DELL D820 laptop).
> wireless driver is ipw3945, kernel module version 1.1.0mp
> wpa_supplicant is version 0.5.4
> 
> any idea?
> 
> Sergio
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From scallegari  Tue Dec 12 05:38:13 2006
From: scallegari (Sergio Callegari)
Date: Tue, 12 Dec 2006 14:38:13 +0100
Subject: wpa_supplicant fails and reports weird AP address in	association
In-Reply-To: <1165928020.2747.7.camel@localhost.localdomain>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
Message-ID: <457EB0C5.1000908@arces.unibo.it>

Dan Williams wrote:
> On Tue, 2006-12-12 at 12:15 +0100, Sergio Callegari wrote:
>   
>> Hi,
>>
>> I am trying to set up a wireless network including an Hamlet access
>> point and a Linux laptop with an intel 3945 wireless interface.
>>
>> Everything is fine as long as I limit myself to WEP security.
>>
>> If I try to use WPA security with wpa_supplicant, things stop working.
>>
>> Precisely I am getting the following problem
>>
>> running
>>
>>     wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -D wext
>>
>> with the following wpa_supplicant.conf
>> network={
>>         ssid="XXXXXXXXX"
>>         scan_ssid=1
>>         proto=WPA
>>         key_mgmt=WPA-PSK
>>         psk="secure"
>>     
>
> Is it really something with quotes?  First, try using the
> 'wpa-passhprase' tool or copy the actual _hex_ key from your AP's
> configuration screen, and paste it into your wpa_supplicant
> configuration like so:
>
> 	psk=11bbccddeeff223399...
>
> i.e., _don't_ use quotes, and use the hexadecimal key rather than using
> quotes here.  If you use quotes, wpa_supplicant interprets the config
> option as a string, which clearly isn't what you want here.  And I don't
> believe that wpa_supplicant supports passphrase hashing for WPA
> internally, that's what wpa-passphrase is for.
>
> Dan
I believe you can either supply as the psk an exadecimal key or a 
string.  In the latter case, wpa supplicant should convert it 
automatically into a hex key using the same algorithm as 
wpa-passphrase... at least, this is what I get from the docs:

"wpa-psk will accept a plaintext string enclosed in quotation marks this 
is equivalent to the 'wpa-passphrase' option"

For instance, this is the example that man wpa_supplicant.conf gives me:

network={
               ssid="home"
               scan_ssid=1
               key_mgmt=WPA-PSK
               psk="very secret passphrase"
          }

Sergio




From prabhu  Tue Dec 12 05:44:07 2006
From: prabhu (Prabhakar kushwaha)
Date: Tue, 12 Dec 2006 05:44:07 -0800
Subject: capabilty
Message-ID: <20061212054407.746E6610@resin01.mta.everyone.net>

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


From kelmo  Tue Dec 12 06:18:55 2006
From: kelmo (Kel Modderman)
Date: Wed, 13 Dec 2006 00:18:55 +1000
Subject: wpa_supplicant fails and reports weird AP address
	=?iso-8859-1?q?in=09association?=
In-Reply-To: <457EB0C5.1000908@arces.unibo.it>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
	<457EB0C5.1000908@arces.unibo.it>
Message-ID: <200612130018.55939.kelmo@kanotixguide.org>

On Tuesday 12 December 2006 23:38, Sergio Callegari wrote:
> Dan Williams wrote:
> > On Tue, 2006-12-12 at 12:15 +0100, Sergio Callegari wrote:
> >> Hi,
> >>
> >> I am trying to set up a wireless network including an Hamlet access
> >> point and a Linux laptop with an intel 3945 wireless interface.
> >>
> >> Everything is fine as long as I limit myself to WEP security.
> >>
> >> If I try to use WPA security with wpa_supplicant, things stop working.
> >>
> >> Precisely I am getting the following problem
> >>
> >> running
> >>
> >>     wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -D wext
> >>
> >> with the following wpa_supplicant.conf
> >> network={
> >>         ssid="XXXXXXXXX"
> >>         scan_ssid=1
> >>         proto=WPA
> >>         key_mgmt=WPA-PSK
> >>         psk="secure"
> >
> > Is it really something with quotes?  First, try using the
> > 'wpa-passhprase' tool or copy the actual _hex_ key from your AP's
> > configuration screen, and paste it into your wpa_supplicant
> > configuration like so:
> >
> > 	psk=11bbccddeeff223399...
> >
> > i.e., _don't_ use quotes, and use the hexadecimal key rather than using
> > quotes here.  If you use quotes, wpa_supplicant interprets the config
> > option as a string, which clearly isn't what you want here.  And I don't
> > believe that wpa_supplicant supports passphrase hashing for WPA
> > internally, that's what wpa-passphrase is for.
> >
> > Dan
>
> I believe you can either supply as the psk an exadecimal key or a
> string.  In the latter case, wpa supplicant should convert it
> automatically into a hex key using the same algorithm as
> wpa-passphrase... at least, this is what I get from the docs:
>
> "wpa-psk will accept a plaintext string enclosed in quotation marks this
> is equivalent to the 'wpa-passphrase' option"

That looks like a snippet from the debian wpasupplicant package. If it is, the 
documentation is referring to special wpa-* options specific to ifupdown 
integration in debian. ie, options to be used in /etc/network/interfaces, not 
wpa_supplicant.conf.

Thanks, Kel.



From mr.fred.smoothie  Tue Dec 12 07:40:29 2006
From: mr.fred.smoothie (Dave Neuer)
Date: Tue, 12 Dec 2006 10:40:29 -0500
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
Message-ID: <161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>

On 12/12/06, Alex Pounds <alex at alexpounds.com> wrote:
>
> My question is simple: Can I use hostAP to do the WPA2 part in software, and
> thus use my laptop with my home network? If so, how? I've been told
> conflicting things about wpa_supplicant (story 1: It needs hardware support.
> Story 2: Hardware support is not neccessary, it needs driver support) and on
> the whole I am hugely confused. If someone can let me know if this is
> possible and point me to some simple documentation on how to set it up, I'd
> be most grateful.

I'm new here too, and probably reall don't know what I'm talking
about. That caveat aside:

I just spent the last couple of days slaving over my Belkin Prism 2.5
card and Debian desktop, trying to get it to work with my WPA-enabled
router also. I managed to finally get it to "sort of" work by updating
the firmware on the card using prism2_srec (which comes with
hostap-utils) and then running the normal debian "interfaces" way w/
wpa_supplicant and the hostap kernel driver. So it seems like it is
possible to get it working without running hostapd.

However, notice the "sort of" working part. In my case, I can
associate w/ my AP, but then wpa_supplicant continuously get
disconnected and reconnected, to the point where I can't run DHCP on
the interface. I was going to try to troubleshoot it today. So, I
don't know if my problem is caused by poor signal, interference w/
other wireless devices I'm running, inadequate firmware (I upgraded
from the 1.4.2 station firmware which came on the card to 1.7.4 -- the
minimum version required to get WPA working, in my understanding) or
some kind of configuration issue.

Hopefully someone w/ more experience can correct me where I've erred
here. At any rate, I thought it might be useful -- it took me a
looooong time to get to there w/ the information I could find online.

Good luck,
Dave



From bryan  Tue Dec 12 09:40:24 2006
From: bryan (Bryan Kadzban)
Date: Tue, 12 Dec 2006 12:40:24 -0500
Subject: wpa_supplicant fails and reports weird AP address in	association
In-Reply-To: <200612130018.55939.kelmo@kanotixguide.org>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
	<457EB0C5.1000908@arces.unibo.it>
	<200612130018.55939.kelmo@kanotixguide.org>
Message-ID: <20061212174024.GA4704@kadzban.is-a-geek.net>

On Wed, Dec 13, 2006 at 12:18:55AM +1000, Kel Modderman wrote:
> On Tuesday 12 December 2006 23:38, Sergio Callegari wrote:
> >
> > I believe you can either supply as the psk an exadecimal key or a
> > string.  In the latter case, wpa supplicant should convert it
> > automatically into a hex key using the same algorithm as
> > wpa-passphrase... at least, this is what I get from the docs:
> >
> > "wpa-psk will accept a plaintext string enclosed in quotation marks this
> > is equivalent to the 'wpa-passphrase' option"
> 
> That looks like a snippet from the debian wpasupplicant package. If it is, the
> documentation is referring to special wpa-* options specific to ifupdown 
> integration in debian. ie, options to be used in /etc/network/interfaces, not 
> wpa_supplicant.conf.

Nope, it's valid in wpa_supplicant.conf:

http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/hostap/wpa_supplicant/wpa_supplicant.conf?rev=1.88&content-type=text/vnd.viewcvs-markup

See the first sample config entry (near the end of the file, after the
comments explaining the syntax).

It is true that using the ASCII passphrase will slow down the startup of
wpa_supplicant a bit, because it has to run through the set of hashes to
create the hex passphrase, but with modern CPUs it's probably not going
to be noticeable.

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


From jar  Tue Dec 12 11:17:52 2006
From: jar (Jar)
Date: Tue, 12 Dec 2006 21:17:52 +0200
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
Message-ID: <457F0060.1040302@pcuf.fi>

Alex Pounds wrote:
> My question is simple: Can I use hostAP to do the WPA2 part in software, and
> thus use my laptop with my home network? If so, how? I've been told
> conflicting things about wpa_supplicant (story 1: It needs hardware support.

Yes. Prism2/2.5/3 station firmware needs to be 1.7.0 or newer. 1.7.4 is 
a good candidate. It is quite trivial to update the firmware if needed. 
See http://linux.junsun.net/intersil-prism/

> Story 2: Hardware support is not neccessary, it needs driver support) and on
> the whole I am hugely confused. If someone can let me know if this is
> possible and point me to some simple documentation on how to set it up, I'd
> be most grateful.

Support is needed from all levels: Hardware-->Sta fw:1.7.0-->, 
driver-->hostap-driver and supplicant-->wpa_supplicant.

-- 
Best Regards, Jar



From david.mattes  Tue Dec 12 15:26:32 2006
From: david.mattes (David Mattes)
Date: Tue, 12 Dec 2006 15:26:32 -0800
Subject: wpa_supplicant with opensc smartcard
Message-ID: <457F3AA8.90701@boeing.com>

Hi,

I'm trying to get smartcard support working for wpa.  I know the 
credential is fine, because when it's on my hard drive, I can auth just 
fine.  I installed it on a smartcard (and can successfully use 
openssl->engine and openssl->req and openssl->s_client with the 
credential) and am having problems getting the supplicant to auth.  I'm 
using wpa_supplicant-0.4.9.  Notice it does take the engine ~7 seconds 
to initialize - is that too long?  It seems like something is timing out 
and causing a re-scan???  Any insights or suggestions for further debugging?

Here are the pertinent supplicant output snippets:
-------------------------------------------------------------
Dec 12 15:14:09.599719: EAP: EAP entering state RECEIVED
Dec 12 15:14:09.599726: EAP: Received EAP-Request method=13 id=5
Dec 12 15:14:09.599732: EAP: EAP entering state GET_METHOD
Dec 12 15:14:09.599738: EAP: Initialize selected EAP method (13, TLS)
Dec 12 15:14:09.600505: TLS: Trusted root certificate(s) loaded
Dec 12 15:14:09.600785: OpenSSL: tls_connection_client_cert - 
SSL_use_certificate_file (DER) failed error:0D0680A8:asn1 encoding 
routines:ASN1_CHECK_TLEN:wrong tag
Dec 12 15:14:09.600808: OpenSSL: pending error: error:0D07803A:asn1 
encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error
Dec 12 15:14:09.600887: OpenSSL: pending error: error:140C800D:SSL 
routines:SSL_use_certificate_file:ASN1 lib
Dec 12 15:14:09.601198: OpenSSL: SSL_use_certificate_file (PEM) --> OK
Dec 12 15:14:09.601208: SSL: Initializing TLS engine
ctx.c:596:sc_establish_context: ===================================
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_KEY_TYPE = CKK_RSA
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_LABEL = Certificate
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_ID = 45
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_ID = 45
pkcs11-session.c:235:C_Login: Login for session 1
framework-pkcs15.c:741:pkcs15_login: PIN verification returned 0
pkcs11-object.c:207:C_FindObjectsInit: C_FindObjectsInit(slot = 0)
pkcs11-object.c:208:C_FindObjectsInit: C_FindObjectsInit(): CKA_CLASS = 
CKO_PRIVATE_KEY
pkcs11-object.c:266:C_FindObjectsInit: Object 0/1 matches
pkcs11-object.c:277:C_FindObjectsInit: 1 matching objects
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_KEY_TYPE = CKK_RSA
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_LABEL = Private Key
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_ID = 45
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_ID = 45
pkcs11-object.c:207:C_FindObjectsInit: C_FindObjectsInit(slot = 0)
pkcs11-object.c:208:C_FindObjectsInit: C_FindObjectsInit(): CKA_CLASS = 
CKO_PUBLIC_KEY
pkcs11-object.c:266:C_FindObjectsInit: Object 0/3 matches
pkcs11-object.c:277:C_FindObjectsInit: 1 matching objects
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_KEY_TYPE = CKK_RSA
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_LABEL = Certificate
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_ID = 45
pkcs11-object.c:123:C_GetAttributeValue: Object 3: CKA_ID = 45
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_SENSITIVE = TRUE
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_EXTRACTABLE = (null)
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_MODULUS = 
D124CEFEEA02A9523A03F72B05A37AB88D67062DE1FE8596E6E91AFDB2D3E1DB
pkcs11-object.c:123:C_GetAttributeValue: Object 1: CKA_PUBLIC_EXPONENT = 
010001
Dec 12 15:14:16.652950: CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
Dec 12 15:14:16.652967: CTRL_IFACE monitor send - hexdump(len=25): 2f 74 
6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 39 37 39 38 2d 35 30 31 30 00
Dec 12 15:14:16.653061: EAP: EAP entering state METHOD
Dec 12 15:14:16.653073: SSL: Received packet(len=6) - Flags 0x20
Dec 12 15:14:16.653080: EAP-TLS: Start
Dec 12 15:14:16.653144: SSL: (where=0x10 ret=0x1)
Dec 12 15:14:16.653224: SSL: (where=0x1001 ret=0x1)
Dec 12 15:14:16.653236: SSL: SSL_connect:before/connect initialization
Dec 12 15:14:16.653673: SSL: (where=0x1001 ret=0x1)
Dec 12 15:14:16.653683: SSL: SSL_connect:SSLv3 write client hello A
Dec 12 15:14:16.653698: SSL: (where=0x1002 ret=0xffffffff)
Dec 12 15:14:16.653706: SSL: SSL_connect:error in SSLv3 read server hello A
Dec 12 15:14:16.653719: SSL: SSL_connect - want more data
Dec 12 15:14:16.653727: SSL: 100 bytes pending from ssl_out
Dec 12 15:14:16.653736: SSL: 100 bytes left to be sent out (of total 100 
bytes)
Dec 12 15:14:16.653746: EAP: method process -> ignore=FALSE 
methodState=MAY_CONT decision=FAIL
Dec 12 15:14:16.653755: EAP: EAP entering state SEND_RESPONSE
Dec 12 15:14:16.653762: EAP: EAP entering state IDLE
Dec 12 15:14:16.653770: EAPOL: SUPP_BE entering state RESPONSE
Dec 12 15:14:16.653775: EAPOL: txSuppRsp
Dec 12 15:14:16.653782: TX EAPOL - hexdump(len=110): 01 00 00 6a 02 05 
00 6a 0d 00 16 03 01 00 5f 01 00 00 5b 03 01 45 7f 37 c8 20 c0 30 0f d2 
c9 22 59 c6 e5 ec 7b fe c7 2b ea d6 18 a4 74 a8 0a bd 87 2d c8 62 3a 00 
00 34 00 39 00 38 00 35 00 16 00 13 00 0a 00 33 00 32 00 2f 00 66 00 05 
00 04 00 63 00 62 00 61 00 15 00 12 00 09 00 65 00 64 00 60 00 14 00 11 
00 08 00 06 00 03 01 00
Dec 12 15:14:16.653879: EAPOL: SUPP_BE entering state RECEIVE
Dec 12 15:14:16.653951: Wireless event: cmd=0x8b15 len=20
Dec 12 15:14:16.653958: Wireless event: new AP: 00:00:00:00:00:00
Dec 12 15:14:16.653977: Setting scan request: 0 sec 100000 usec
Dec 12 15:14:16.653987: Added BSSID 00:14:1c:c8:9f:b0 into blacklist
Dec 12 15:14:16.653997: State: ASSOCIATED -> DISCONNECTED

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



From Nazeer.Khan  Tue Dec 12 22:32:04 2006
From: Nazeer.Khan (Nazeer Khan)
Date: Wed, 13 Dec 2006 17:32:04 +1100 (EST)
Subject: Problem Configuring "hostapd"
Message-ID: <59573.203.143.170.163.1165991524.squirrel@mailbag.nicta.com.au>


Hi,

I download the latest stable version of hostapd-0.4.5, but i am having
problem with the configuration.

All the problems are with "tls_openssl.c"

It starts with this.....

tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory
tls_openssl.c:26:25: error: openssl/err.h: No such file or directory
tls_openssl.c:27:28: error: openssl/pkcs12.h: No such file or directory
tls_openssl.c:28:28: error: openssl/x509v3.h: No such file or directory
tls_openssl.c:45: error: syntax error before ?SSL?
tls_openssl.c:45: warning: no semicolon at end of struct or union
tls_openssl.c:46: warning: type defaults to ?int? in declaration of ?ssl_in?
tls_openssl.c:46: warning: type defaults to ?int? in declaration of ?ssl_out?
tls_openssl.c:46: warning: data definition has no type or storage class


and there are hundreds of problems with the same file.

Can someone help me with that. I am using madwifi-ng with linux 2.6.12
(Ubuntu)

Thank u.

Nazeer Khan



--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.



From ramprasad.rajendran  Tue Dec 12 23:47:33 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Wed, 13 Dec 2006 13:17:33 +0530
Subject: Problem Configuring "hostapd"
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F6993@blr-m3-msg.wipro.com>


Hi,

>-----Original Message-----
>From: hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com 
>[mailto:hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com]
> On Behalf Of Nazeer Khan
>Sent: Wednesday, December 13, 2006 12:02 PM
>To: Host AP
>Subject: Problem Configuring "hostapd"
>
>
>
>Hi,
>
>I download the latest stable version of hostapd-0.4.5, but i 
>am having problem with the configuration.
>
>All the problems are with "tls_openssl.c"
>
>It starts with this.....
>
>tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory
>tls_openssl.c:26:25: error: openssl/err.h: No such file or directory
>tls_openssl.c:27:28: error: openssl/pkcs12.h: No such file or directory
>tls_openssl.c:28:28: error: openssl/x509v3.h: No such file or directory
>tls_openssl.c:45: error: syntax error before 'SSL'
>tls_openssl.c:45: warning: no semicolon at end of struct or union
>tls_openssl.c:46: warning: type defaults to 'int' in 
>declaration of 'ssl_in'
>tls_openssl.c:46: warning: type defaults to 'int' in 
>declaration of 'ssl_out'
>tls_openssl.c:46: warning: data definition has no type or storage class

Please set the PATH to where your openssl include files are present.
--
Ram

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


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From bayar  Wed Dec 13 00:18:38 2006
From: bayar (Erdenebayar Buriad)
Date: Wed, 13 Dec 2006 17:18:38 +0900
Subject: Problem Configuring "hostapd"
Message-ID: <002301c71e8f$4ae581a0$64faa8c0@CGNTVC2>

>
> Hi,
>
> I download the latest stable version of hostapd-0.4.5, but i am having
> problem with the configuration.

Hi,
I think, you have latest stable version of hostap 0.4.7 and 0.4.9.

>
> All the problems are with "tls_openssl.c"
>
> It starts with this.....
>
> tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory
> tls_openssl.c:26:25: error: openssl/err.h: No such file or directory
> tls_openssl.c:27:28: error: openssl/pkcs12.h: No such file or directory
> tls_openssl.c:28:28: error: openssl/x509v3.h: No such file or directory
> tls_openssl.c:45: error: syntax error before 'SSL'
> tls_openssl.c:45: warning: no semicolon at end of struct or union
> tls_openssl.c:46: warning: type defaults to 'int' in declaration of 
> 'ssl_in'
> tls_openssl.c:46: warning: type defaults to 'int' in declaration of 
> 'ssl_out'
> tls_openssl.c:46: warning: data definition has no type or storage class
>
>
> and there are hundreds of problems with the same file.
>
> Can someone help me with that. I am using madwifi-ng with linux 2.6.12
> (Ubuntu)
>

You need to add path of openssl include files to environment variable.

Bayar





From Nazeer.Khan  Wed Dec 13 00:34:20 2006
From: Nazeer.Khan (Nazeer Khan)
Date: Wed, 13 Dec 2006 19:34:20 +1100 (EST)
Subject: FW: Problem Configuring "hostapd"
In-Reply-To: <52E5BF168B8CA143A198D856F73D5A9D0F6993@blr-m3-msg.wipro.com>
References: <52E5BF168B8CA143A198D856F73D5A9D0F6993@blr-m3-msg.wipro.com>
Message-ID: <45740.203.143.168.131.1165998860.squirrel@mailbag.nicta.com.au>


Hi,

I cannot locate openssl. Do i need to install any package?

Can you explain a little more please ?

THank you.

Nazeer

>
> Hi,
>
>>-----Original Message-----
>>From: hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com
>>[mailto:hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com]
>> On Behalf Of Nazeer Khan
>>Sent: Wednesday, December 13, 2006 12:02 PM
>>To: Host AP
>>Subject: Problem Configuring "hostapd"
>>
>>
>>
>>Hi,
>>
>>I download the latest stable version of hostapd-0.4.5, but i
>>am having problem with the configuration.
>>
>>All the problems are with "tls_openssl.c"
>>
>>It starts with this.....
>>
>>tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory
>>tls_openssl.c:26:25: error: openssl/err.h: No such file or directory
>>tls_openssl.c:27:28: error: openssl/pkcs12.h: No such file or directory
>>tls_openssl.c:28:28: error: openssl/x509v3.h: No such file or directory
>>tls_openssl.c:45: error: syntax error before 'SSL'
>>tls_openssl.c:45: warning: no semicolon at end of struct or union
>>tls_openssl.c:46: warning: type defaults to 'int' in
>>declaration of 'ssl_in'
>>tls_openssl.c:46: warning: type defaults to 'int' in
>>declaration of 'ssl_out'
>>tls_openssl.c:46: warning: data definition has no type or storage class
>
> Please set the PATH to where your openssl include files are present.
> --
> Ram



--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.



From Nazeer.Khan  Wed Dec 13 01:11:52 2006
From: Nazeer.Khan (Nazeer Khan)
Date: Wed, 13 Dec 2006 20:11:52 +1100 (EST)
Subject: [Fwd: RE: Problem Configuring "hostapd"]
Message-ID: <34381.203.143.168.131.1166001112.squirrel@mailbag.nicta.com.au>


Hi,

I got openssl now. I download it from "http://www.openssl.org/" and
configured it successfully. I am trying to set the path variable, but i
don't know where i am doing the mistake. I am having the same problem
again. My path to openssl is as under.

/usr/src/CASC-LWAP/openssl-0.9.7l/include/openssl/ssl.h
/usr/local/ssl/include/openssl/ssl.h


How can i add the path.

Please help.

Nazeer Khan



>
>Hi,
>
>I download the latest stable version of hostapd-0.4.5, but i
>am having problem with the configuration.
>
>All the problems are with "tls_openssl.c"
>
>It starts with this.....
>
>tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory
tls_openssl.c:26:25: error: openssl/err.h: No such file or directory
tls_openssl.c:27:28: error: openssl/pkcs12.h: No such file or directory
tls_openssl.c:28:28: error: openssl/x509v3.h: No such file or directory
tls_openssl.c:45: error: syntax error before 'SSL'
>tls_openssl.c:45: warning: no semicolon at end of struct or union
tls_openssl.c:46: warning: type defaults to 'int' in
>declaration of 'ssl_in'
>tls_openssl.c:46: warning: type defaults to 'int' in
>declaration of 'ssl_out'
>tls_openssl.c:46: warning: data definition has no type or storage class

Please set the PATH to where your openssl include files are present. --
Ram

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


The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s) and
may contain proprietary, confidential or privileged information. If you
are not the intended recipient, you should not disseminate, distribute or
copy this e-mail. Please notify the sender immediately and destroy all
copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

www.wipro.com




--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.



From alex  Wed Dec 13 03:09:48 2006
From: alex (Alex Pounds)
Date: Wed, 13 Dec 2006 11:09:48 -0000 (GMT)
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
Message-ID: <39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>

On Tue, December 12, 2006 3:40 pm, Dave Neuer wrote:
> I'm new here too, and probably reall don't know what I'm talking
> about. That caveat aside:
>
> I just spent the last couple of days slaving over my Belkin Prism 2.5
> card and Debian desktop, trying to get it to work with my WPA-enabled
> router also. I managed to finally get it to "sort of" work by updating
> the firmware on the card using prism2_srec (which comes with
> hostap-utils) and then running the normal debian "interfaces" way w/
> wpa_supplicant and the hostap kernel driver. So it seems like it is
> possible to get it working without running hostapd.

Hello,

Could I get some more details from you regarding your Debian setup? I too am
running Debian, and spent last night trying to update my firmware. I'm using
a 2.6.17 kernel (the kernel-image-2.6.17-2-686 package, I think - this is
all off the top of my head) and the hostap-utils to provide prism2_srec,
etc. I've downloaded the latest firmware, but when I try to do a "dry run" I
get a message that prism2_srec couldn't read the wlan card's PDA, and
telling me I need to have a certain config option (PRISM2_DOWNLOAD_*,
perhaps?) enabled in my hostap_config.h. I get the same message if I use the
-r option to try and pop the firmware in RAM.

I did presume that the hostap modules didn't have this option enabled, but
now I'm starting to think it may be something else. Did you have to futz
around and build your own kernel to get it working, or are you using a
Debian stock kernel?

Apologies for being vague about the error messages, by the way - the laptop
in question is at home, and I am not.

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^




From tomsimnett  Wed Dec 13 03:34:00 2006
From: tomsimnett (Tom Simnett)
Date: Wed, 13 Dec 2006 11:34:00 +0000
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
Message-ID: <200612131134.05280.tomsimnett@yahoo.co.uk>

On Wednesday 13 December 2006 11:09, Alex Pounds wrote:
> On Tue, December 12, 2006 3:40 pm, Dave Neuer wrote:
> > I'm new here too, and probably reall don't know what I'm talking
> > about. That caveat aside:
> >
> > I just spent the last couple of days slaving over my Belkin Prism 2.5
> > card and Debian desktop, trying to get it to work with my WPA-enabled
> > router also. I managed to finally get it to "sort of" work by updating
> > the firmware on the card using prism2_srec (which comes with
> > hostap-utils) and then running the normal debian "interfaces" way w/
> > wpa_supplicant and the hostap kernel driver. So it seems like it is
> > possible to get it working without running hostapd.
>
> Hello,
>
> Could I get some more details from you regarding your Debian setup? I too
> am running Debian, and spent last night trying to update my firmware. I'm
> using a 2.6.17 kernel (the kernel-image-2.6.17-2-686 package, I think -
> this is all off the top of my head) and the hostap-utils to provide
> prism2_srec, etc. I've downloaded the latest firmware, but when I try to do
> a "dry run" I get a message that prism2_srec couldn't read the wlan card's
> PDA, and telling me I need to have a certain config option
> (PRISM2_DOWNLOAD_*, perhaps?) enabled in my hostap_config.h. I get the same
> message if I use the -r option to try and pop the firmware in RAM.
>
> I did presume that the hostap modules didn't have this option enabled, but
> now I'm starting to think it may be something else. Did you have to futz
> around and build your own kernel to get it working, or are you using a
> Debian stock kernel?
>
> Apologies for being vague about the error messages, by the way - the laptop
> in question is at home, and I am not.

I am having a similar problem on a laptop of mine - I kind of gave up because 
I'm getting a new laptop in a month or so anyway, but I wanted to outline the 
problem I am having.

What I understand is that versions of the prism firmware lower than 0.5.6 iirc 
don't support wpa, where higher versions do, but versions above 0.7.4 are 
unstable.

I have been unable to update the firmware using the hostap tools that were 
designed to do so, as they just don't recognise the card and its parameters, 
even though the card is actually found, and the relevant drivers loaded.

Was support for firmware updates removed in an earlier version of hostap?

Thanks,

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061213/f27de8b3/attachment.pgp 


From bryan  Wed Dec 13 04:04:43 2006
From: bryan (Bryan Kadzban)
Date: Wed, 13 Dec 2006 07:04:43 -0500
Subject: Problem Configuring "hostapd"
In-Reply-To: <34381.203.143.168.131.1166001112.squirrel@mailbag.nicta.com.au>
References: <34381.203.143.168.131.1166001112.squirrel@mailbag.nicta.com.au>
Message-ID: <457FEC5B.5050203@kadzban.is-a-geek.net>

Nazeer Khan wrote:
> I got openssl now. I download it from "http://www.openssl.org/" and 
> configured it successfully. I am trying to set the path variable, but
> i don't know where i am doing the mistake. I am having the same
> problem again. My path to openssl is as under.
> 
> /usr/src/CASC-LWAP/openssl-0.9.7l/include/openssl/ssl.h 
> /usr/local/ssl/include/openssl/ssl.h
> 
> 
> How can i add the path.

Did you install OpenSSL from source, or only configure it?  It looks
like it may have been installed.

You *should* have just installed your distro's openssl-devel or
openssl-dev package.  That would put all the right files into the right
places so that you don't have to mess with *anything* to get it to work;
gcc would find it by default.

If you've installed OpenSSL from sources, you're probably running a
strange mix of versions, and it may not even work right.  I'd suggest
removing OpenSSL (if "make uninstall" doesn't work, then you'll have to
do it by hand) and installing your distro's -devel package.

And don't mess with $PATH at all -- that's *only* used to find programs
to run, not headers or libraries.  Those are found using gcc's -I and -L
flags; but you won't need any flags if you just use your distro's
package.

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


From mr.fred.smoothie  Wed Dec 13 04:59:45 2006
From: mr.fred.smoothie (Dave Neuer)
Date: Wed, 13 Dec 2006 07:59:45 -0500
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
Message-ID: <161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>

On 12/13/06, Alex Pounds <alex at alexpounds.com> wrote:
>
> Could I get some more details from you regarding your Debian setup? I too am
> running Debian, and spent last night trying to update my firmware. I'm using
> a 2.6.17 kernel (the kernel-image-2.6.17-2-686 package, I think - this is
> all off the top of my head) and the hostap-utils to provide prism2_srec,
> etc. I've downloaded the latest firmware, but when I try to do a "dry run" I
> get a message that prism2_srec couldn't read the wlan card's PDA, and
> telling me I need to have a certain config option (PRISM2_DOWNLOAD_*,
> perhaps?) enabled in my hostap_config.h. I get the same message if I use the
> -r option to try and pop the firmware in RAM.
>
> I did presume that the hostap modules didn't have this option enabled, but
> now I'm starting to think it may be something else. Did you have to futz
> around and build your own kernel to get it working, or are you using a
> Debian stock kernel?

I did install the latest kernel from unstable (2.6.18), and modified
the config (you need to select CONFIG_HOSTAP_FIRMWARE and
CONFIG_HOSTAP_FIRMWARE_NVRAM). The former may be selected already in
the previous config (in /boot/config-<your-previous-kernel-version>)
but you need the latter as well.

Once you rebuild, install and reboot the new kernel, you can then run
the prism2_srec utility to flash the card. Note, apparently because of
some inconsistency between the driver, utilities and debian's udev
setup, you will need to explicitly tell prism2_srec where the PDAs are
(e.g., prism2_srec -v eth<n> -O /proc/net/hostap/wlan0/pda <primary
firmware>.hex <station firmware>.hex).

Finally, I was not able to get a stable connection to the AP using the
debian interfaces-based startup -- tried several different ways.
Instead, I used NetworkManager and just started up wpa_supplicant with
"wpa_supplicant -d -g /var/run/wpa-supplicant-global" so
NetworkManager can find wpa_supplicant's control interface, and I can
initiate a connection to the AP that way, and when it (inevitably)
fails, I can toggle the connection with a couple of clicks.

All of this was enough to almost make be go buy a dynex Atheros-based
card for $35. But this is OK for now (I won't be able to download
large files on that machine most likely). Perhaps if I get time, I can
debug the issues w/ wpa_supplicant disconnecting.

Hope that helps,
Dave



From yohonet  Wed Dec 13 06:15:48 2006
From: yohonet (Vincent Panel)
Date: Wed, 13 Dec 2006 15:15:48 +0100
Subject: Fwd: TKIP: replay detected:
In-Reply-To: <15116fd10612130614q45eb8cads67d44892c25975d4@mail.gmail.com>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<1165927790.2747.3.camel@localhost.localdomain>
	<15116fd10612130614q45eb8cads67d44892c25975d4@mail.gmail.com>
Message-ID: <15116fd10612130615v49b040d7h769c9c7454426e3e@mail.gmail.com>

On 12/12/06, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2006-12-12 at 09:53 +0100, Vincent Panel wrote:
> > Hi,
> >
> > I get a lot of these messages in my kernel log :
> >
> > kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> > 0000000004a9 received TSC 0000000004a8
>
> What kernel and what driver are you using?

$ uname -a
Linux xxx.yyy.com 2.6.17-6mdv #1 SMP Wed Oct 25 12:24:51 MDT 2006 i686
Intel(R) Pentium(R) 4 CPU 3.20GHz GNU/Linux

> > I see a lot of people have the same problem, but I found no real
> > solution to this problem.
>
> Can you do some packet sniffing and figure out whether the TSC is really
> going backwards between messages from the AP to your STA?

I'll try to and post the results.

> If so, it's
> clearly an access point problem.  But before that, lets figure out what
> driver you're using and make sure it's not one of the ones that's under
> heavier development...
>
> Dan
>
> > I'm using wpa_supplicant-0.5.5 and found nothing in the changelog of
> > wpa_supplicant 0.5.6 which lets me think there's a improvement.
> >
> > I don't have access to the access point (it belongs to my company),
> > but I'm ready to test and provide you with any piece of necessary
> > information.
> > Thanks
> >
> > Vincent.
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
>
>
(Sorry dan, forgot to reply to all)



From yohonet  Wed Dec 13 06:24:37 2006
From: yohonet (Vincent Panel)
Date: Wed, 13 Dec 2006 15:24:37 +0100
Subject: wpa_supplicant fails and reports weird AP address in association
In-Reply-To: <457E8F60.1000706@arces.unibo.it>
References: <457E8F60.1000706@arces.unibo.it>
Message-ID: <15116fd10612130624m2a2624e1yd8ed25a6d6c1d364@mail.gmail.com>

On 12/12/06, Sergio Callegari <scallegari at arces.unibo.it> wrote:
> Hi,
>
> I am trying to set up a wireless network including an Hamlet access
> point and a Linux laptop with an intel 3945 wireless interface.

It may be unrelated, but I noticed strange behavior with this Wifi
card : the "radio kill switch" is sometimes reported to be off whereas
it isn't.

If you look at a variable named
/sys/bus/pci/drivers/ipw3945/00*/rf_kill (approximate name, on top of
my head), you may see it's different from 0 although the "wifi +
bluetooth" button is turned on on some laptops. This variable should
be 0 if everything is ok, 1 if you turn off the switch, 2 if you turn
it on but a problem occurs and 3 if you turn it off but a problem
occurs.

If I plug a cable in my ethernet port, this variable is systematically
2 or 3, but is never 0 or 1... This is very odd and probably linked to
the driver. I'll try to recompile a newer version.



From abaillargeon  Wed Dec 13 06:53:14 2006
From: abaillargeon (Aaron Baillargeon)
Date: Wed, 13 Dec 2006 09:53:14 -0500
Subject: aironet1100 EAP-FAST  + supplicant
Message-ID: <458013DA.1050701@mobilerobots.com>

Hi,

I found an email from June posted to the mailing list that asked about 
EAP-FAST and an SSL error that came up with CiscoAPs, couldn't find any 
resolution. Below is an excerpt from the email(seemingly from a cisco 
employee) showing the error:


/ 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=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


I was curious if anyone else working with EAP-FAST encountered this.
I tried openssl 0.9.8a and 0.9.8d(patched) with wpa_supplicant 0.5.6 and 
dont have any other EAP-FAST capable servers around to test (freeradius 
doesn't support it correct?)


Thanks,
-Ahren




From j.witteveen  Wed Dec 13 13:22:40 2006
From: j.witteveen (Jouke Witteveen)
Date: Wed, 13 Dec 2006 22:22:40 +0100
Subject: Can't assign requested address
Message-ID: <3993a4980612131322h570e0216le5f1f5825807cfef@mail.gmail.com>

Hello all,

(See also my recent messages: "new wired driver code")
When I start wpa_supplicant with my new code I keep getting:
"Can't assign requested address" (code 49: EADDRNOTAVAIL).
When I run an old program I found on the net:
http://www.kohala.com/start/mtest.c (NOTE: I changed AF_UNSPEC to
AF_LINK again - else it wouldn't work) with:
'a xl0 1.80.c2.0.0.3'
things DO work.
Though when I include the mtest code in driver_wired.c it too gives
the EADDRNOTAVAIL.
I discovered that when I first add the multicast address through mtest
and then run wpa_supplicant it tends not to complain. I suspect
something checks to see whether the requested address is already
alligned.
Anyhow: I do not have a clue why I get this error. Help is really welcome.

Regards,
Jouke Witteveen



From ramprasad.rajendran  Wed Dec 13 19:36:23 2006
From: ramprasad.rajendran (ramprasad.rajendran at wipro.com)
Date: Thu, 14 Dec 2006 09:06:23 +0530
Subject: aironet1100 EAP-FAST  + supplicant
Message-ID: <52E5BF168B8CA143A198D856F73D5A9D0F69A4@blr-m3-msg.wipro.com>




Hi,


>-----Original Message-----
>From: hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com 
>[mailto:hostap-bounces+ramprasad.rajendran=wipro.com at shmoo.com]
> On Behalf Of Aaron Baillargeon
>Sent: Wednesday, December 13, 2006 8:23 PM
>To: hostap at shmoo.com
>Subject: aironet1100 EAP-FAST + supplicant
>
>
>Hi,
>
>
>I was curious if anyone else working with EAP-FAST encountered 
>this. I tried openssl 0.9.8a and 0.9.8d(patched) with 
>wpa_supplicant 0.5.6 and 
>dont have any other EAP-FAST capable servers around to test 
>(freeradius 
>doesn't support it correct?)

You could get an evaluation version(30 days evaluation) from Funk Steel
Belted Radius.
You'll be able to only use EAP-MSCHAPv2 for provisioning and EAP-GTC for
inner authentication with the evaluation version.
I tested wpa_supplicant version from CVS and used the internal crypto
and TLS libraries.

--
ram

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


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From jkmaline  Wed Dec 13 21:29:38 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 13 Dec 2006 21:29:38 -0800
Subject: aironet1100 EAP-FAST  + supplicant
In-Reply-To: <458013DA.1050701@mobilerobots.com>
References: <458013DA.1050701@mobilerobots.com>
Message-ID: <20061214052938.GB6152@jm.kir.nu>

On Wed, Dec 13, 2006 at 09:53:14AM -0500, Aaron Baillargeon wrote:

> I found an email from June posted to the mailing list that asked about 
> EAP-FAST and an SSL error that came up with CiscoAPs, couldn't find any 
> resolution. Below is an excerpt from the email(seemingly from a cisco 
> employee) showing the error:

> / 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

If I remember correctly, this is caused by a bug in the EAP-FAST server
implementation that is included in some of the APs as the local
authentication server.

> I was curious if anyone else working with EAP-FAST encountered this.
> I tried openssl 0.9.8a and 0.9.8d(patched) with wpa_supplicant 0.5.6 and 
> dont have any other EAP-FAST capable servers around to test (freeradius 
> doesn't support it correct?)

The internal TLS implementation (CONFIG_TLS=internal and
CONFIG_INTERNAL_LIBTOMMATH=y in .config) seems to work with the local
authentication server in the Cisco APs.. In order to get OpenSSL
working, some of the cipher suites would need to be disabled as a
workaround (again, if I remember correctly).

-- 
Jouni Malinen                                            PGP id EFC895FA



From amitd23.singh  Wed Dec 13 22:52:27 2006
From: amitd23.singh (amit Singh)
Date: Thu, 14 Dec 2006 12:22:27 +0530
Subject: EAP-TLS logs
Message-ID: <a554dc6a0612132252p437d6ed3qbf4b8a40020bf6ca@mail.gmail.com>

Hi,
 If any one have sniffer(ethereal log) of EAP-TLS method for window XP
please share me for my refernce.I have properly configure Radius
server,WindowXP and AP for EAP-TLS method.I am able to see in ethreal
packets
 Client hello and Server Hello message but Window XP is not able to
authenticate to server.Through event viewer I had seen Error Crypto32.dll. I
think it is not supporting server_keycert.pem.I have client cert in pkcs12
format and root cert der format.and on server cert and root in pem
format.Please help me what could be issue...
here is more about versions:
FreeRADIUS Version 1.0.5
, D-Link(DI 524) AP with "WPA-EAP"

If any one have complete Ethereal log please share me so that I can get my
problem.It's not issue If you have linux system then it will be also
helpfull. Thanks in advance.

Thanks,
Amit Singh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061214/ffa88e7f/attachment.htm 


From dominik.geisel  Thu Dec 14 01:12:13 2006
From: dominik.geisel (Dominik Geisel)
Date: Thu, 14 Dec 2006 10:12:13 +0100
Subject: Z-Com ZI-325HP+ - Ubuntu 6.10 - very slow connection
Message-ID: <28932a650612140112m4c76cabbxb35e63b978e3b1b1@mail.gmail.com>

Hi there,

I have a new Z-Com ZI-325HP+ running with Ubuntu 6.10 (2.6.17-10generic) on
a IBM X-series laptop. The card is running fine and connecting to my AP,
which is about 10 m away with one medium wall inbetween, with 11Mbit all the
time. I usw WPA-TKIP encryption and the NetworkManager tool with
gnome-applet to connect.
My problem is, that I get very low transfer speeds. I tried downloading via
FTP from another machine in the local LAN and got about 200 Kbyte/sec. With
placing the laptop 1 m in direct sight to the AP I get no more than 300
Kbyte/sec.
I have an Atheros 802.11bg card working with madwifi-drivers and get around
2000 Kbyte/sec with this card (sure, it is g and not b).
Where could be the problem?

iwconfig:
--------------------
wifi0     IEEE 802.11b  ESSID:"Corpus"
          Mode:Managed  Frequency:2.472 GHz  Access Point:
00:04:0E:2B:4C:ED
          Bit Rate:11 Mb/s   Sensitivity=1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

wlan0     IEEE 802.11b  ESSID:"Corpus"
          Mode:Managed  Frequency:2.472 GHz  Access Point:
00:04:0E:2B:4C:ED
          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=41/70  Signal level=-33 dBm  Noise level=-74 dBm
          Rx invalid nwid:0  Rx invalid crypt:1  Rx invalid frag:0
          Tx excessive retries:19  Invalid misc:1018   Missed beacon:0


dmesg:
--------------------
[17180778.356000] pccard: PCMCIA card inserted into slot 0
[17180816.068000] pcmcia: registering new device pcmcia0.0
[17180816.332000] hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi
>)
[17180816.336000] hostap_cs: setting Vcc=33 (constant)
[17180816.336000] Checking CFTABLE_ENTRY 0x01 (default 0x01)
[17180816.336000] IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
[17180816.336000] io->flags = 0x0046, io.base=0x0000, len=64
[17180816.336000] hostap_cs: Registered netdevice wifi0
[17180816.376000] hostap_cs: index 0x01: , irq 3, io 0x3100-0x313f
[17180816.572000] prism2_hw_init: initialized in 196 ms
[17180816.572000] wifi0: NIC: id=0x800c v1.0.0
[17180816.572000] wifi0: PRI: id=0x15 v1.1.1
[17180816.572000] wifi0: STA: id=0x1f v1.8.4
[17180816.576000] wifi0: registered netdevice wlan0
[17180816.696000] ADDRCONF(NETDEV_UP): wifi0: link is not ready
[17180816.696000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17180816.764000] wifi0: LinkStatus=2 (Disconnected)
[17180816.764000] wifi0: LinkStatus: BSSID=44:44:44:44:44:44
[17180817.624000] wifi0: LinkStatus=1 (Connected)
[17180817.624000] wifi0: LinkStatus: BSSID=00:14:c1:2b:aa:6e
[17180817.624000] ADDRCONF(NETDEV_CHANGE): wifi0: link becomes ready
[17180817.624000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[17180820.260000] wifi0: LinkStatus=4 (Access point out of range)
[17180820.260000] wifi0: LinkStatus: BSSID=00:14:c1:2b:aa:6e
[17180827.964000] wlan0: no IPv6 routers present
[17180841.824000] wifi0: LinkStatus=2 (Disconnected)
[17180841.824000] wifi0: LinkStatus: BSSID=00:14:c1:2b:aa:6e
[17180842.272000] wifi0: LinkStatus=2 (Disconnected)
[17180842.272000] wifi0: LinkStatus: BSSID=44:44:44:44:44:44
[17180842.284000] wifi0: LinkStatus=2 (Disconnected)
[17180842.284000] wifi0: LinkStatus: BSSID=44:44:44:44:44:44
[17180842.300000] wifi0: LinkStatus=2 (Disconnected)
[17180842.300000] wifi0: LinkStatus: BSSID=44:44:44:44:44:44
[17180842.312000] wlan0: Trying to join BSSID 00:04:0e:2b:4c:ed
[17180842.336000] wifi0: LinkStatus=1 (Connected)
[17180842.340000] wifi0: LinkStatus: BSSID=00:04:0e:2b:4c:ed
[17180842.340000] ADDRCONF(NETDEV_CHANGE): wifi0: link becomes ready


Thank you very much!
Dominik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061214/2f5e9704/attachment.htm 


From Nazeer.Khan  Thu Dec 14 02:56:04 2006
From: Nazeer.Khan (Nazeer Khan)
Date: Thu, 14 Dec 2006 21:56:04 +1100 (EST)
Subject: hostapd first Launch unsuccessful
Message-ID: <61460.124.176.73.240.1166093764.squirrel@mailbag.nicta.com.au>


Hi,

Whenever i run hostapd i have to do it twise. The first time it just stop
due to "bind(PF_UNIX)" i guess. Why does this happens the first time. The
second time i run hostapd, i am successful.

By second time i mean the following.....
-----------------------------

root at nazeer:/etc/hostapd# hostapd -dd WPA_EAP.conf
=>Error given below........

In the same terminal after the error.
root at nazeer:/etc/hostapd# hostapd -dd WPA_EAP.conf
=>Works fine......


<<<<<<<<<<<<<<<<Error Output>>>>>>>>>>>>>>>>

Configuration file: WPA_EAP.conf
Configure bridge br0 for EAPOL traffic.
madwifi_set_iface_flags: dev_up=0
Using interface ath0 with hwaddr 00:11:95:f2:86:2d and ssid 'NK_EAP_Enabled'
ath0: RADIUS Authentication server 127.0.0.1:1812
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): c1 1a 2d ae 2a 43 17 77 95 6a c0 d0 d8 9d c0 83 47
d9 63 26 6e c5 ef 51 3f cc ef 9a cb 7b b8 c1
GTK - hexdump(len=32): ed 27 08 7e 9a 0d 78 b5 1d 6c a9 72 cd d1 05 6d 04
38 a4 86 70 d6 95 82 4e 99 fa ed ed 42 cd ba
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
bind(PF_UNIX): Address already in use >>>>>>>>>>>>>>>>>>>>>>>>>>>> why ???
Failed to setup control interface
madwifi_set_privacy: enabled=0
madwifi_set_ieee8021x: enabled=0
madwifi_set_iface_flags: dev_up=0


Why do i have to run hostapd two times everytime???

Thank you.

Nazeer Khan


--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.



From jar  Thu Dec 14 03:40:43 2006
From: jar (Jar)
Date: Thu, 14 Dec 2006 13:40:43 +0200 (EET)
Subject: Z-Com ZI-325HP+ - Ubuntu 6.10 - very slow connection
In-Reply-To: <28932a650612140112m4c76cabbxb35e63b978e3b1b1@mail.gmail.com>
References: <28932a650612140112m4c76cabbxb35e63b978e3b1b1@mail.gmail.com>
Message-ID: <44194.81.209.37.10.1166096443.squirrel@netlandzone.dyndns.org>


> [17180816.572000] wifi0: STA: id=0x1f v1.8.4

Do you have tried with v1.7.4 firmware?

-- 
Best Regards, Jar



From alex  Thu Dec 14 16:13:02 2006
From: alex (Alex Pounds)
Date: Fri, 15 Dec 2006 00:13:02 +0000
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
Message-ID: <20061215001302.GA17496@localhost.localdomain>

On Wed, Dec 13, 2006 at 07:59:45AM -0500, Dave Neuer wrote:
> Once you rebuild, install and reboot the new kernel, you can then run
> the prism2_srec utility to flash the card. Note, apparently because of
> some inconsistency between the driver, utilities and debian's udev
> setup, you will need to explicitly tell prism2_srec where the PDAs are
> (e.g., prism2_srec -v eth<n> -O /proc/net/hostap/wlan0/pda <primary
> firmware>.hex <station firmware>.hex).

Well, I have since updated my firmware (which went OK), but I am now
having problems. Different problems. I used the following command to
update my firmware: 

prism2_srec -f -v eth0 -O /proc/net/hostap/wlan0/pda pk010101.hex sf010804.hex

This reported everything went fine; running hostap_diag eth0 also reported
everything as going fine. I then tried to get wpa_supplicant on the go. On
my desktop, I don't do things "properly" to get my wifi back after a
reboot - I've got the following shell script that's called from an init
script: 

#!/bin/bash
iwconfig ath0 ap AA:BB:CC:DD:EE:C8
iwconfig ath0 essid "wireless"
iwconfig ath0 channel 1
iwpriv ath0 bgscan 0
iwpriv ath0 wpa 3
wpa_supplicant -Bw -Dwext -iath0 -c/etc/wpa_supplicant.conf
dhclient ath0

I tried this, but using wlan0_rename as my parameter and using the
following wpa_supplicant line: 

wpa_supplicant -Bw -Dhostap -iwlan0_rename -c/etc/wpa_supplicant.conf

To be honest, there was some futzing involved with some commands using
eth0 and some as wlan0_rename as the interface name. I've managed to tie
myself in knots this way before, and decided to reboot. And that is where
the fun begins. The interface doesn't come back up on reboot, though both
the hostap and hostap_pci modules are shown as loaded. If I rmmod them
both and then modprobe hostap_pci, I get the following: 

hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline at cc.hut.fi>)
PCI: Enabling device 0000:01:02.0 (0110 -> 0112)
ACPI: PCI Interrupt 0000:01:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) - > IRQ 11
hostap_pci: Registered netdevice wifi0
wifi0: Interrupt delivery does not seem to work
hostap_pci: Initialization failed
ACPI: PCI interrupt for device 0000:01:02.0 disabled 

The kernel.log reveals a similar story, but after the "Registered
netdevice wifi0" line the following are given: 

wifi0: Original COR value: 0x21
prism2_hw_init: initialized in 192 ms
wifi0: hfa384x_cmd: entry still in list? (entry=df211b20, type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, entry=df211b20, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8010 INTEN=0010)
wifi0: interrupt delivery does not seem to work
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8)
Could not get RID for component NIC

And then the rest is as above. So, what's the story? How do I get my
module loading again, and when I've done that how am I supposed to get
wpa/wifi going? 

Thank you, 
  
-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^



From yann.garcia  Fri Dec 15 06:22:41 2006
From: yann.garcia (Yann Garcia)
Date: Fri, 15 Dec 2006 15:22:41 +0100
Subject: wpa_supllicant on Windows XP : stange DHCP behavior when using WEP
Message-ID: <03a301c72054$7b6b4dc0$0c01000a@smartcomnet.local>

Hi all,

 

I've got a problem and I don't really understand what happening. I want to
connect my Windows client (Netgear WG111v2) to my hotspot (WEP secured).

A Linux box with Hostapd/Chillispot/Radius works as an access point.

The Windows XP client uses wpa_supplicant to establish the connection.

 

Here is my problem:

*	Without WEP, all works fine;
*	With WEP, the access point never receive the DHCP Discover request
(tcpdump doesn't see any packet on the wlan0 interface) but (it's strange!)
I can see (ethereal on windows) the DHCP Discover packets sent on the client
interface. In the /var/log/messages, I can see that the association is
established by hostapd.

 

So I don't really understand what happening.

 

The configuration seems to be ok because I can connect my client to the
hotspot (with WEP enable) using WZC.

 

Please anyone can help me?

 

Thanks a lot for your help,

 

Yann

 

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


From jkmaline  Fri Dec 15 07:49:47 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 15 Dec 2006 07:49:47 -0800
Subject: wpa_supllicant on Windows XP : stange DHCP behavior when using WEP
In-Reply-To: <03a301c72054$7b6b4dc0$0c01000a@smartcomnet.local>
References: <03a301c72054$7b6b4dc0$0c01000a@smartcomnet.local>
Message-ID: <20061215154947.GB6154@jm.kir.nu>

On Fri, Dec 15, 2006 at 03:22:41PM +0100, Yann Garcia wrote:

> The Windows XP client uses wpa_supplicant to establish the connection.

Which version of wpa_supplicant are you using?

> *	Without WEP, all works fine;
> *	With WEP, the access point never receive the DHCP Discover request
> (tcpdump doesn't see any packet on the wlan0 interface) but (it's strange!)
> I can see (ethereal on windows) the DHCP Discover packets sent on the client
> interface. In the /var/log/messages, I can see that the association is
> established by hostapd.

Sounds like the driver did not understand how the WEP key was configured
or it dropped it for some reason.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mr.fred.smoothie  Fri Dec 15 07:54:22 2006
From: mr.fred.smoothie (Dave Neuer)
Date: Fri, 15 Dec 2006 10:54:22 -0500
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <20061215001302.GA17496@localhost.localdomain>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
	<20061215001302.GA17496@localhost.localdomain>
Message-ID: <161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>

On 12/14/06, Alex Pounds <alex at alexpounds.com> wrote:
>
> Well, I have since updated my firmware (which went OK), but I am now
> having problems. Different problems. I used the following command to
> update my firmware:
>
> prism2_srec -f -v eth0 -O /proc/net/hostap/wlan0/pda pk010101.hex sf010804.hex

<snip>

> prism2_hw_init: initialized in 192 ms
> wifi0: hfa384x_cmd: entry still in list? (entry=df211b20, type=0, res=0)
> wifi0: hfa384x_cmd: command was not completed (res=0, entry=df211b20, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8010 INTEN=0010)
> wifi0: interrupt delivery does not seem to work
> wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8)
> Could not get RID for component NIC

First off, I'd be lying if I said I knew what was going on here.
However, it's clear enough from  this snippet of log file that the
device is not responding to some commands the way the driver expects
it to.

If it were me, I might try flashing a different firmware version (my
impression from reading all of the info I could find in my attempts to
get things working was that 1.7.4, the version I flashed, is
considered fairly stable).

Of course, that's the drag about having to run binary blobs; it's
really impossible to know what's going on inside the firmware, so
solving something like this is inevitably going to be a process of
trial and error.

Dave



From dtheoharis  Sat Dec 16 03:52:39 2006
From: dtheoharis (Dimitris Theoharis)
Date: Sat, 16 Dec 2006 06:52:39 -0500
Subject: hostap and FreeBSD
Message-ID: <3948f2f20612160352h73845751uda525481b48bf208@mail.gmail.com>

Hi ,

Is it possible to setup hostap on a freebsd box and then to connect it
to a WPA2 network?:)



From alex  Sat Dec 16 05:33:52 2006
From: alex (Alex Pounds)
Date: Sat, 16 Dec 2006 13:33:52 +0000
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
	<20061215001302.GA17496@localhost.localdomain>
	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>
Message-ID: <20061216133352.GA25998@localhost.localdomain>

On Fri, Dec 15, 2006 at 10:54:22AM -0500, Dave Neuer wrote:
> On 12/14/06, Alex Pounds <alex at alexpounds.com> wrote:
> > prism2_hw_init: initialized in 192 ms
> > wifi0: hfa384x_cmd: entry still in list? (entry=df211b20, type=0, res=0)
> > wifi0: hfa384x_cmd: command was not completed (res=0, entry=df211b20, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8010 INTEN=0010)
> > wifi0: interrupt delivery does not seem to work
> > wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8)
> > Could not get RID for component NIC
> 
> First off, I'd be lying if I said I knew what was going on here.
> However, it's clear enough from  this snippet of log file that the
> device is not responding to some commands the way the driver expects
> it to.

Funnily enough, when I started the laptop up today this problem
disappeared. My best guess is the motherboard or wifi card got confused a
bit through a combination of reflashing the chipset and a warm reboot.
Starting it up from scratch made everything come up OK. 

After some messing around all night (with some help from the lovely
#debian folks on Freenode) I'm pretty sure I've reached the same place as
you have - I can associate to the access point, but it then flip-flops
between associated and unassociated. You haven't found a solution to this
yet, have you? 

Some debugging output is included below.

$ wpa_supplicant -D hostap -i eth0 -c /etc/wpa_supplicant.conf
Trying to associate with AA:BB:CC:DD:EE:c8  (SSID='ourwifi' freq=2412 MHz)
Associated with AA:BB:CC:DD:EE:c8
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with AA:BB:CC:DD:EE:c8  (SSID='ourwifi' freq=2412 MHz)
Associated with AA:BB:CC:DD:EE:c8
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with AA:BB:CC:DD:EE:c8  (SSID='ourwifi' freq=2412 MHz)
Associated with AA:BB:CC:DD:EE:c8
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys


$ wpa_supplicant -dd -D hostap -i eth0 -c /etc/wpa_supplicant.conf
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'hostap' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7):
     6f 75 72 77 69 66 69                              ourwifi         
PSK - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='ourwifi'
Initializing interface (2) 'eth0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=20 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:20:e0:4d:17:38
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Added interface eth0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
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
Received 93 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: AA:BB:CC:DD:EE:c8 ssid='ourwifi' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
   selected based on RSN IE
Trying to associate with AA:BB:CC:DD:EE:c8 (SSID='ourwifi' freq=2412 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 proto 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_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
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
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: AA:BB:CC:DD:EE:c8
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=AA:BB:CC:DD:EE:c8
No keys have been configured - skip key clearing
Associated with AA:BB:CC:DD:EE:c8
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
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' 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)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
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 AA:BB:CC:DD:EE:c8 into blacklist
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
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
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
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
State: DISCONNECTED -> SCANNING


There is more, but it's all much of a muchness from that point on. So,
what's up with all this? 

Thank you, 

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^



From jkmaline  Sat Dec 16 20:18:39 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Dec 2006 20:18:39 -0800
Subject: hostap and FreeBSD
In-Reply-To: <3948f2f20612160352h73845751uda525481b48bf208@mail.gmail.com>
References: <3948f2f20612160352h73845751uda525481b48bf208@mail.gmail.com>
Message-ID: <20061217041839.GD6119@jm.kir.nu>

On Sat, Dec 16, 2006 at 06:52:39AM -0500, Dimitris Theoharis wrote:

> Is it possible to setup hostap on a freebsd box and then to connect it
> to a WPA2 network?:)

I don't know what exactly you are referring to with "hostap" in this
context, but for me, it is the Host AP Linux driver and there is not
much point in trying to run that on FreeBSD.. Anyway, the current
FreeBSD includes support for similar function in number of wlan drivers
and it also includes wpa_supplicant and hostapd, so yes, it should be
possible to connect to WPA2 networks (assuming the driver you use
supports this).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec 16 20:26:57 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Dec 2006 20:26:57 -0800
Subject: wpa_supplicant fails and reports weird AP address in association
In-Reply-To: <457E8F60.1000706@arces.unibo.it>
References: <457E8F60.1000706@arces.unibo.it>
Message-ID: <20061217042657.GE6119@jm.kir.nu>

On Tue, Dec 12, 2006 at 12:15:44PM +0100, Sergio Callegari wrote:

> I am trying to set up a wireless network including an Hamlet access
> point and a Linux laptop with an intel 3945 wireless interface.

I'm not familiar with "Hamlet access point". What is it? Is there a more
specific model number and software version etc. available?

> 1) my AP MAC address should be AA:BB:CC:DD:EE:30 as reported on the AP 
> web interface (only last byte is properly quoted here).
> 
> 2) iwlist eth1 scan reports AA:BB:CC:DD:EE:33... i.e. the last byte is 
> different in 3 bits.

It sounds like the AP is using more than one address. The oen shown in
the web UI is likely the one from the wired interface, not wireless, in
this case..

> 4) when wpa_supplicant reports association, it says it is associating 
> with AA:BB:CC:DD:EE:33...
> 
> 5) however, the subsequent debug of the 4 way
> handshake shows AA:BB:CC:DD:EE:30 as the AP address...
> 
> May this has anything to do with the failed handshake?

Yes, very possible.

> wpa_supplicant is version 0.5.4

Could you please run with the latest wpa_supplicant version (0.5.6) and
if that is also failing, please post a detailed debug log from
wpa_supplicant (-dd on command line).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec 16 20:31:47 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Dec 2006 20:31:47 -0800
Subject: wpa_supplicant fails and reports weird AP address in association
In-Reply-To: <1165928020.2747.7.camel@localhost.localdomain>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
Message-ID: <20061217043147.GF6119@jm.kir.nu>

On Tue, Dec 12, 2006 at 07:53:40AM -0500, Dan Williams wrote:

> Is it really something with quotes?  First, try using the
> 'wpa-passhprase' tool or copy the actual _hex_ key from your AP's
> configuration screen, and paste it into your wpa_supplicant
> configuration like so:
> 
> 	psk=11bbccddeeff223399...

This may be quite confusing instruction to give.. I would expect most
users of WPA-Personal to configure the key as an ASCII passphrase, not
as 64 character hex string..

> i.e., _don't_ use quotes, and use the hexadecimal key rather than using
> quotes here.  If you use quotes, wpa_supplicant interprets the config
> option as a string, which clearly isn't what you want here.  And I don't
> believe that wpa_supplicant supports passphrase hashing for WPA
> internally, that's what wpa-passphrase is for.

Clearly, the configuration was indeed trying to use a string and I would
expect that was the desired configuration in this case. Like Bryan
already mentioned, wpa_supplicant does indeed support passphrase hashing
for WPA PSK (and always has supported).

There is only one use for wpa_passphrase and that is to minimize the
startup time by removing the need to derive the key again every time.
However, taken into account the speed of most modern CPUs, there is
almost no cases where I would recommend wpa_passphrase to be used. It
is just much easier to use the ASCII passphrase in the configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec 16 20:35:19 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Dec 2006 20:35:19 -0800
Subject: TKIP: replay detected:
In-Reply-To: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
Message-ID: <20061217043519.GG6119@jm.kir.nu>

On Tue, Dec 12, 2006 at 09:53:14AM +0100, Vincent Panel wrote:

> I get a lot of these messages in my kernel log :
> 
> kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> 0000000004a9 received TSC 0000000004a8

Which wlan driver are you using?

> I'm using wpa_supplicant-0.5.5 and found nothing in the changelog of
> wpa_supplicant 0.5.6 which lets me think there's a improvement.

This message is from kernel and wpa_supplicant is very unlikely to have
anything to do with it.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec 16 20:39:00 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 16 Dec 2006 20:39:00 -0800
Subject: Problem Configuring "hostapd"
In-Reply-To: <59573.203.143.170.163.1165991524.squirrel@mailbag.nicta.com.au>
References: <59573.203.143.170.163.1165991524.squirrel@mailbag.nicta.com.au>
Message-ID: <20061217043900.GH6119@jm.kir.nu>

On Wed, Dec 13, 2006 at 05:32:04PM +1100, Nazeer Khan wrote:

> I download the latest stable version of hostapd-0.4.5, but i am having
> problem with the configuration.
> 
> All the problems are with "tls_openssl.c"

> tls_openssl.c:25:25: error: openssl/ssl.h: No such file or directory

This indicates that OpenSSL development package was not found (likely
not installed). Are you planning on using hostapd as an authentication
server (EAP server) or only as an access point controller? If latter,
you do not actually need OpenSSL at all (but you will need to remove
CONFIG_EAP* entries from .config). If you do not OpenSSL, I would
suggest installing the development package for it from the distribution
you use.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yohonet  Sun Dec 17 06:35:11 2006
From: yohonet (Vincent Panel)
Date: Sun, 17 Dec 2006 15:35:11 +0100
Subject: TKIP: replay detected:
In-Reply-To: <20061217043519.GG6119@jm.kir.nu>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
Message-ID: <15116fd10612170635p592d29dw13494a746a1bd2f7@mail.gmail.com>

On 12/17/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> This message is from kernel and wpa_supplicant is very unlikely to have
> anything to do with it.
>
Thanks.

I think the real bug comes from the AP, but I can't reproduce it now.
If it happens again, I'll sniff the connection with the AP and re-open
this thread. I know this message comes from the kernel.



From jar  Sun Dec 17 06:43:01 2006
From: jar (Jar)
Date: Sun, 17 Dec 2006 16:43:01 +0200
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <20061216133352.GA25998@localhost.localdomain>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>	<20061215001302.GA17496@localhost.localdomain>	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>
	<20061216133352.GA25998@localhost.localdomain>
Message-ID: <45855775.7010807@pcuf.fi>

Alex Pounds wrote:
> I can associate to the access point, but it then flip-flops
> between associated and unassociated. You haven't found a solution to this

Consider to downgrade to 1.7.4 firmware.

-- 
Best Regards, Jar



From elcorreu  Sun Dec 17 07:19:59 2006
From: elcorreu (Ignasi Blanco Sastre)
Date: Sun, 17 Dec 2006 16:19:59 +0100
Subject: Multicast traffic
Message-ID: <60b30af40612170719g8faaacjc9b6561e2a68ec4b@mail.gmail.com>

Hi,

I receive multicast traffic from a AP with a PrismII card running in hostAP
mode (hostap 0.4.9 + Conceptronic Airbridge 11C), without any STA's in Power
Save Mode in the network, and this traffic is limited by DTIM period.
Multicast traffic are delayed until the beacon frame with bitmap control at
1.

Why multicast traffic aren't delivered like unicast traffic?

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061217/118f7852/attachment.htm 


From dcbw  Sun Dec 17 07:41:44 2006
From: dcbw (Dan Williams)
Date: Sun, 17 Dec 2006 10:41:44 -0500
Subject: wpa_supplicant fails and reports weird AP address in association
In-Reply-To: <20061217043147.GF6119@jm.kir.nu>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
	<20061217043147.GF6119@jm.kir.nu>
Message-ID: <1166370104.2757.15.camel@localhost.localdomain>

On Sat, 2006-12-16 at 20:31 -0800, Jouni Malinen wrote:
> On Tue, Dec 12, 2006 at 07:53:40AM -0500, Dan Williams wrote:
> 
> > Is it really something with quotes?  First, try using the
> > 'wpa-passhprase' tool or copy the actual _hex_ key from your AP's
> > configuration screen, and paste it into your wpa_supplicant
> > configuration like so:
> > 
> > 	psk=11bbccddeeff223399...
> 
> This may be quite confusing instruction to give.. I would expect most
> users of WPA-Personal to configure the key as an ASCII passphrase, not
> as 64 character hex string..
> 
> > i.e., _don't_ use quotes, and use the hexadecimal key rather than using
> > quotes here.  If you use quotes, wpa_supplicant interprets the config
> > option as a string, which clearly isn't what you want here.  And I don't
> > believe that wpa_supplicant supports passphrase hashing for WPA
> > internally, that's what wpa-passphrase is for.
> 
> Clearly, the configuration was indeed trying to use a string and I would
> expect that was the desired configuration in this case. Like Bryan
> already mentioned, wpa_supplicant does indeed support passphrase hashing
> for WPA PSK (and always has supported).
> 
> There is only one use for wpa_passphrase and that is to minimize the
> startup time by removing the need to derive the key again every time.
> However, taken into account the speed of most modern CPUs, there is
> almost no cases where I would recommend wpa_passphrase to be used. It
> is just much easier to use the ASCII passphrase in the configuration.

I stand corrected...

Thanks,
Dan




From dcbw  Sun Dec 17 07:42:12 2006
From: dcbw (Dan Williams)
Date: Sun, 17 Dec 2006 10:42:12 -0500
Subject: TKIP: replay detected:
In-Reply-To: <20061217043519.GG6119@jm.kir.nu>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
Message-ID: <1166370132.2757.17.camel@localhost.localdomain>

On Sat, 2006-12-16 at 20:35 -0800, Jouni Malinen wrote:
> On Tue, Dec 12, 2006 at 09:53:14AM +0100, Vincent Panel wrote:
> 
> > I get a lot of these messages in my kernel log :
> > 
> > kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> > 0000000004a9 received TSC 0000000004a8
> 
> Which wlan driver are you using?

I believe he said ipw3945...

Dan

> 
> > I'm using wpa_supplicant-0.5.5 and found nothing in the changelog of
> > wpa_supplicant 0.5.6 which lets me think there's a improvement.
> 
> This message is from kernel and wpa_supplicant is very unlikely to have
> anything to do with it.
> 




From kelmo  Sun Dec 17 13:15:41 2006
From: kelmo (Kel Modderman)
Date: Mon, 18 Dec 2006 07:15:41 +1000
Subject: seg fault when interface does not exist
Message-ID: <200612180715.42193.kelmo@kanotixguide.org>

Hi,

wpa_supplicant currently crashes hard if the interface to be used is 
non-existant (or a typo is made).

$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext -ifoo0
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'foo0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
Segmentation fault

Wouldn't it be nicer if it exited gracefully (with a hint) before trying to 
configure the non-existant interface?

Thanks, Kel.



From alex  Sun Dec 17 16:38:34 2006
From: alex (Alex Pounds)
Date: Mon, 18 Dec 2006 00:38:34 +0000
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <45855775.7010807@pcuf.fi>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
	<20061215001302.GA17496@localhost.localdomain>
	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>
	<20061216133352.GA25998@localhost.localdomain>
	<45855775.7010807@pcuf.fi>
Message-ID: <20061218003834.GA4636@localhost.localdomain>

On Sun, Dec 17, 2006 at 04:43:01PM +0200, Jar wrote:
> Alex Pounds wrote:
> >I can associate to the access point, but it then flip-flops
> >between associated and unassociated. You haven't found a solution to this
> 
> Consider to downgrade to 1.7.4 firmware.

I've downgraded to 1.7.4, but I have exactly the same problem as before.
Debugging output with -dd from wpa_supplicant is pretty much identical
(sometimes it receives 3 BSSIDs instead of 1 from the previous session). 

Any other ideas? 

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^



From jkmaline  Sun Dec 17 20:53:48 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 17 Dec 2006 20:53:48 -0800
Subject: seg fault when interface does not exist
In-Reply-To: <200612180715.42193.kelmo@kanotixguide.org>
References: <200612180715.42193.kelmo@kanotixguide.org>
Message-ID: <20061218045348.GD9711@jm.kir.nu>

On Mon, Dec 18, 2006 at 07:15:41AM +1000, Kel Modderman wrote:

> wpa_supplicant currently crashes hard if the interface to be used is 
> non-existant (or a typo is made).

What do you mean with "currently"? Which version are you using? I cannot
reproduce this with either the 0.5.x or 0.6.x branch..

> Wouldn't it be nicer if it exited gracefully (with a hint) before trying to 
> configure the non-existant interface?

Crashing is of course not the expected behavior. The driver wrappers
could be modified to verify that the interface exists before trying to
use it, but at least driver_wext output is quite clear on the interface
really not being there no matter how hard one tries to use it.. ;-)

$ sudo ./wpa_supplicant -Dwext -isofof -c psk-test.conf
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'sofof' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 17 20:55:49 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 17 Dec 2006 20:55:49 -0800
Subject: TKIP: replay detected:
In-Reply-To: <1166370132.2757.17.camel@localhost.localdomain>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
	<1166370132.2757.17.camel@localhost.localdomain>
Message-ID: <20061218045549.GE9711@jm.kir.nu>

On Sun, Dec 17, 2006 at 10:42:12AM -0500, Dan Williams wrote:
> > On Tue, Dec 12, 2006 at 09:53:14AM +0100, Vincent Panel wrote:
> > > I get a lot of these messages in my kernel log :
> > > 
> > > kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> > > 0000000004a9 received TSC 0000000004a8

> I believe he said ipw3945...

In that case I would recommend asking this on the ipw3945 mailing list,
not here.. It is driver specific and I my guess would be that ipw3945
driver is not filtering out duplicate frames based on seq# before
processing TKIP replays.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kelmo  Sun Dec 17 22:13:33 2006
From: kelmo (Kel Modderman)
Date: Mon, 18 Dec 2006 16:13:33 +1000
Subject: seg fault when interface does not exist
In-Reply-To: <20061218045348.GD9711@jm.kir.nu>
References: <200612180715.42193.kelmo@kanotixguide.org>
	<20061218045348.GD9711@jm.kir.nu>
Message-ID: <200612181613.33888.kelmo@kanotixguide.org>

On Monday 18 December 2006 14:53, Jouni Malinen wrote:
> On Mon, Dec 18, 2006 at 07:15:41AM +1000, Kel Modderman wrote:
> > wpa_supplicant currently crashes hard if the interface to be used is
> > non-existant (or a typo is made).
>
> What do you mean with "currently"? Which version are you using? I cannot
> reproduce this with either the 0.5.x or 0.6.x branch..

Debian 0.5.6-1 binary. No modification to your tarball apart from a patch that 
points to specific doc's. The following config is used (madwifi headers are 
activated via another patch):

diff -Nru wpa_supplicant.orig/.config wpa_supplicant/.config
--- wpa_supplicant.orig/.config	1970-01-01 10:00:00.000000000 +1000
+++ wpa_supplicant/.config	2006-03-14 21:53:16.364723608 +1000
@@ -0,0 +1,41 @@
+CONFIG_DRIVER_ATMEL=y
+CONFIG_DRIVER_HOSTAP=y
+CONFIG_DRIVER_IPW=y
+#CONFIG_DRIVER_MADWIFI=y
+#CFLAGS+=-I./driver_madwifi
+CONFIG_DRIVER_NDISWRAPPER=y
+CONFIG_DRIVER_WEXT=y
+CONFIG_DRIVER_WIRED=y
+CONFIG_WIRELESS_EXTENSION=y
+CONFIG_DRIVER_TEST=y
+
+#CONFIG_DRIVER_PRISM54=y	# Prism54 support broken upstream
+#CONFIG_DRIVER_NDIS=y		# Windows only
+#CONFIG_DRIVER_HERMES=y		# Non-GPL header required
+#CONFIG_DRIVER_BROADCOM=y	# Non-GPL header required
+
+CONFIG_IEEE8021X_EAPOL=y
+
+CONFIG_EAP_MD5=y
+CONFIG_EAP_MSCHAPV2=y
+#CONFIG_EAP_FAST=y		# Requires OpenSSL rebuild
+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_PSK=y
+CONFIG_EAP_PAX=y
+CONFIG_EAP_LEAP=y
+#CONFIG_EAP_AKA=y
+#CONFIG_EAP_SAKE=y
+
+CONFIG_PKCS12=y
+CONFIG_SMARTCARD=y
+#CONFIG_PCSC=y
+
+CONFIG_CTRL_IFACE=y
+CONFIG_CTRL_IFACE_DBUS=y
+CONFIG_READLINE=y
+

>
> > Wouldn't it be nicer if it exited gracefully (with a hint) before trying
> > to configure the non-existant interface?
>
> Crashing is of course not the expected behavior. The driver wrappers
> could be modified to verify that the interface exists before trying to
> use it, but at least driver_wext output is quite clear on the interface
> really not being there no matter how hard one tries to use it.. ;-)

Yeah its clear enough for me. Just don't know what the segfault issue is 
caused by. Might try a more minimal build config to see if it exists there.

Thanks, Kel.



From abaillargeon  Mon Dec 18 06:17:47 2006
From: abaillargeon (Aaron Baillargeon)
Date: Mon, 18 Dec 2006 09:17:47 -0500
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <20061218003834.GA4636@localhost.localdomain>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>	<20061215001302.GA17496@localhost.localdomain>	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>	<20061216133352.GA25998@localhost.localdomain>	<45855775.7010807@pcuf.fi>
	<20061218003834.GA4636@localhost.localdomain>
Message-ID: <4586A30B.9080008@mobilerobots.com>

Alex Pounds wrote:
> On Sun, Dec 17, 2006 at 04:43:01PM +0200, Jar wrote:
>   
>> Alex Pounds wrote:
>>     
>>> I can associate to the access point, but it then flip-flops
>>> between associated and unassociated. You haven't found a solution to this
>>>       
>> Consider to downgrade to 1.7.4 firmware.
>>     
>
> I've downgraded to 1.7.4, but I have exactly the same problem as before.
> Debugging output with -dd from wpa_supplicant is pretty much identical
> (sometimes it receives 3 BSSIDs instead of 1 from the previous session). 
>
> Any other ideas? 
>
>   
Just from staring at these for a couple days, the debug output seems 
like it might be a config error on either the authentication server or 
the client. From the log it seems you're using wpa2-psk/ccmp?, have you 
tried wpa-psk/tkip or other configs and gotten them to work?

There are a bunch of sample config files on the supplicant main page.  
My config for wpa2ccmp is:

network={
        ssid="psk"
        scan_ssid=1
        key_mgmt=WPA-PSK
        proto=WPA2
        pairwise=CCMP
        group=CCMP
        psk="passphrase"
}


-- 
Aaron Baillargeon
Integration Engineer
MobileRobots Inc.
19 Columbia Dr.
Amherst, NH 03031
603-881-7960 x165 (voice)
603-881-3818 (fax)
abaillargeon at mobilerobots.com




From alex  Mon Dec 18 06:44:53 2006
From: alex (Alex Pounds)
Date: Mon, 18 Dec 2006 14:44:53 -0000 (GMT)
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <4586A30B.9080008@mobilerobots.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>	<20061215001302.GA17496@localhost.localdomain>	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>	<20061216133352.GA25998@localhost.localdomain>	<45855775.7010807@pcuf.fi>
	<20061218003834.GA4636@localhost.localdomain>
	<4586A30B.9080008@mobilerobots.com>
Message-ID: <52908.193.203.83.22.1166453093.squirrel@webmail.alexpounds.com>

On Mon, December 18, 2006 2:17 pm, Aaron Baillargeon wrote:
> Just from staring at these for a couple days, the debug output seems
> like it might be a config error on either the authentication server or
> the client. From the log it seems you're using wpa2-psk/ccmp?, have you
> tried wpa-psk/tkip or other configs and gotten them to work?

I'll have a fiddle with this when I get home - it's entirely possible, as I
don't really understand exactly what you're saying. I don't think this is an
issue with my wpa_supplicant.conf, though, as I'm using exactly the same
wpa_supplicant.conf on both my laptop (which does not work and produces the
error messages shown) and on my PC (which works fine with my AP). They are
identical - they MD5Sum again.

I'll certainly poke around and try with other authentication schemes, but if
it is a config problem I'd expect it to be a non-wpa_supplicant config
problem.

Thanks for the suggestion,

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^




From mr.fred.smoothie  Mon Dec 18 07:17:21 2006
From: mr.fred.smoothie (Dave Neuer)
Date: Mon, 18 Dec 2006 10:17:21 -0500
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <4586A30B.9080008@mobilerobots.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com>
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com>
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com>
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com>
	<20061215001302.GA17496@localhost.localdomain>
	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com>
	<20061216133352.GA25998@localhost.localdomain>
	<45855775.7010807@pcuf.fi>
	<20061218003834.GA4636@localhost.localdomain>
	<4586A30B.9080008@mobilerobots.com>
Message-ID: <161717d50612180717r6d80dbeen67a6cf4806ebcf31@mail.gmail.com>

On 12/18/06, Aaron Baillargeon <abaillargeon at mobilerobots.com> wrote:
> Alex Pounds wrote:
> >
> > I've downgraded to 1.7.4, but I have exactly the same problem as before.
> > Debugging output with -dd from wpa_supplicant is pretty much identical
> > (sometimes it receives 3 BSSIDs instead of 1 from the previous session).
> >
> > Any other ideas?
> >
> >
> Just from staring at these for a couple days, the debug output seems
> like it might be a config error on either the authentication server or
> the client. From the log it seems you're using wpa2-psk/ccmp?, have you
> tried wpa-psk/tkip or other configs and gotten them to work?

FWIW, I'm using TKIP only, and I have the same problem. I did find
that when I connect w/ a static-style startup script, I can't connect
long enough to use the connection at all.

I've started doing wpa_supplicant -B -C
/path-to-global-control-interface, and then using NetworkManager to
connect to the AP. It's still fairly unstable, but not unusably so. I
end up just having to toggle the wireless interface when I notice the
network has become unresponsive.

However, my office is also our guest bedroom and we have holiday visitors, so
1) I haven't tried connecting with the machine in question since I
move my AP closer to said machine, and;
2) I won't really be able to access it to check the logs or the config
in detail until after Christmas.

At any rate, some amount of instability seems at this point to be
somewhat unavoidable in my setup (unless I win the lottery or get
snowbound, or some other magic event happens which provides me w/ the
amount of free time that would be necessary for me to poke around the
internals enough to really understand what's happening at a lower
level).

Dave



From scallegari  Mon Dec 18 08:00:25 2006
From: scallegari (Sergio Callegari)
Date: Mon, 18 Dec 2006 17:00:25 +0100
Subject: wpa_supplicant fails and reports weird AP address in	association
In-Reply-To: <20061212174024.GA4704@kadzban.is-a-geek.net>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
	<457EB0C5.1000908@arces.unibo.it>
	<200612130018.55939.kelmo@kanotixguide.org>
	<20061212174024.GA4704@kadzban.is-a-geek.net>
Message-ID: <4586BB19.3000807@arces.unibo.it>

> On Tue, Dec 12, 2006 at 12:15:44PM +0100, Sergio Callegari wrote:
>
> > I am trying to set up a wireless network including an Hamlet access
> > point and a Linux laptop with an intel 3945 wireless interface.
>
> I'm not familiar with "Hamlet access point". What is it? Is there a more
> specific model number and software version etc. available?
I don't have it at hand, but I'll let everybody have the exact model asap.
>
> > 1) my AP MAC address should be AA:BB:CC:DD:EE:30 as reported on the AP
> > web interface (only last byte is properly quoted here).
> >
> > 2) iwlist eth1 scan reports AA:BB:CC:DD:EE:33... i.e. the last byte is
> > different in 3 bits.
>
> It sounds like the AP is using more than one address. The oen shown in
> the web UI is likely the one from the wired interface, not wireless, in
> this case..
>
> > 4) when wpa_supplicant reports association, it says it is associating
> > with AA:BB:CC:DD:EE:33...
> >
> > 5) however, the subsequent debug of the 4 way
> > handshake shows AA:BB:CC:DD:EE:30 as the AP address...
> >
> > May this has anything to do with the failed handshake?
>
> Yes, very possible.
>
> > wpa_supplicant is version 0.5.4
>
> Could you please run with the latest wpa_supplicant version (0.5.6) and
> if that is also failing, please post a detailed debug log from
> wpa_supplicant (-dd on command line).
I'll see if I can try that... (btw, does anybody know if there are debs 
of wpa_supplicant 0.5.6 for ubuntu 6.10)?
In the meantime, just some little news....

I have had the occasion to try wpa_supplicant on the very same host but 
another AP (a linksys this time).  With the latter, everything is 
perfectly fine, both with WPA-PSK and WPA2-PSK.  So it appears to be a 
problem specific to the Hamlet AP. I have tried to look for hamlet 
firmware update, but I am running the latest.

BTW the WPA configuration on the linksys and the hamlet AP follow very 
different routes:
on the linksys I chose /either/ no security /or/ wep /or/ wpa. In other 
terms, WEP and WPA appear as alternatives. On the Hamlet box I have a 
two step setup.  First I chose whether to have basic cryptography or not 
(and this can be "open", "shared" or "both", with the possibility of 
setting a WEP key)... then on another setup stage I chose whether to 
have WPA-PSK or not, with the possibility of introducing a WPA-PSK key.  
So WEP and WPA appear as complementary.

So far I have tryed any possible option for the first basic 
cryptographic setup (I have actually tried all of them).  But is there a 
"proper" basic (wep?) cryptographic setup to be used with WPA?  This is 
very confusing and the Hamlet manual does not help.

Sergio




From elcorreu  Mon Dec 18 09:57:52 2006
From: elcorreu (Ignasi Blanco Sastre)
Date: Mon, 18 Dec 2006 18:57:52 +0100
Subject: Fwd: Multicast traffic
In-Reply-To: <60b30af40612170719g8faaacjc9b6561e2a68ec4b@mail.gmail.com>
References: <60b30af40612170719g8faaacjc9b6561e2a68ec4b@mail.gmail.com>
Message-ID: <60b30af40612180957l788cbb17s75bd65408f6b4c1c@mail.gmail.com>

Hi,

I asked a question about multicast traffic and probably I missed some
details;
So I have AP with a PrismII card running in hostAP mode (hostap 0.4.9 +
Conceptronic Airbridge 11C) and I haven't any STA's in Power Save Mode in
the network. Standard 802.11 say that when there are frames in AP must be
sended to STA.

But I sended multicast traffic and it is limited by DTIM period
(dtim_period=3). Multicast traffic are delayed until the third beacon frame
with bitmap control at 1.

How to send multicast traffic according to standard ? Is it a driver problem
or firmware problem?

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061218/a59b683f/attachment.htm 


From bryan  Mon Dec 18 11:18:38 2006
From: bryan (Bryan Kadzban)
Date: Mon, 18 Dec 2006 14:18:38 -0500
Subject: wpa_supplicant fails and reports weird AP address in	association
In-Reply-To: <4586BB19.3000807@arces.unibo.it>
References: <457E8F60.1000706@arces.unibo.it>	<1165928020.2747.7.camel@localhost.localdomain>	<457EB0C5.1000908@arces.unibo.it>	<200612130018.55939.kelmo@kanotixguide.org>	<20061212174024.GA4704@kadzban.is-a-geek.net>
	<4586BB19.3000807@arces.unibo.it>
Message-ID: <4586E98E.5060103@kadzban.is-a-geek.net>

Sergio Callegari wrote:
> on the linksys I chose /either/ no security /or/ wep /or/ wpa. In 
> other terms, WEP and WPA appear as alternatives.

They are.

> On the Hamlet box I have a two step setup.  First I chose whether to 
> have basic cryptography or not (and this can be "open", "shared" or 
> "both, with the possibility of setting a WEP key)...

Well... not exactly.

Open and shared refer to the 802.11 authentication, which happens just
before association.  The "normal" WPA or WPA2 authentication, OTOH,
happens after association.  Basically, never use shared authentication.

(Shared requires a WEP key.  It also informs everyone sniffing your
association frames of that WEP key; it's *extremely* insecure.  I don't
know how "both" would work, but AFAIK, WPA and WPA2 both require open.)

The open/shared choice should only be made if you configure the AP for
WEP.

> then on another setup stage I chose whether to have WPA-PSK or not, 
> with the possibility of introducing a WPA-PSK key. So WEP and WPA 
> appear as complementary.

They are not.  It may be possible with some cards to do both WEP and WPA
on the same SSID, but I don't know how the card would choose.  I don't
think there's any standard for it, in any case.

> is there a "proper" basic (wep?) cryptographic setup to be used with 
> WPA?  This is very confusing and the Hamlet manual does not help.

Authentication, as in the frames sent just before association, must be
set to open.  WPA and WPA2 handle key exchange, ensuring the client is
authorized, and setting up data frame encryption.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061218/12efa7bf/attachment.pgp 


From miknix  Mon Dec 18 11:24:48 2006
From: miknix (miknix)
Date: Mon, 18 Dec 2006 19:24:48 +0000
Subject: devicescape headers changed.
Message-ID: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>

Hi there.

Devicescape has unified net/d80211_common.h and net/d80211_shared.h into
d80211.h. Could someone update driver_devicescape to reflect these changes?
The rt2x00 development team is using this version for a while..

About the hostapd cvs repos. I cannot checkout sources using anonymous
access, is it working?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061218/7982774c/attachment.htm 


From dcbw  Mon Dec 18 11:40:20 2006
From: dcbw (Dan Williams)
Date: Mon, 18 Dec 2006 14:40:20 -0500
Subject: wpa_supplicant fails and reports weird AP address in	association
In-Reply-To: <4586E98E.5060103@kadzban.is-a-geek.net>
References: <457E8F60.1000706@arces.unibo.it>
	<1165928020.2747.7.camel@localhost.localdomain>
	<457EB0C5.1000908@arces.unibo.it>
	<200612130018.55939.kelmo@kanotixguide.org>
	<20061212174024.GA4704@kadzban.is-a-geek.net>
	<4586BB19.3000807@arces.unibo.it>
	<4586E98E.5060103@kadzban.is-a-geek.net>
Message-ID: <1166470820.30000.5.camel@localhost.localdomain>

On Mon, 2006-12-18 at 14:18 -0500, Bryan Kadzban wrote:
> Sergio Callegari wrote:
> > on the linksys I chose /either/ no security /or/ wep /or/ wpa. In 
> > other terms, WEP and WPA appear as alternatives.
> 
> They are.
> 
> > On the Hamlet box I have a two step setup.  First I chose whether to 
> > have basic cryptography or not (and this can be "open", "shared" or 
> > "both, with the possibility of setting a WEP key)...
> 
> Well... not exactly.
> 
> Open and shared refer to the 802.11 authentication, which happens just
> before association.  The "normal" WPA or WPA2 authentication, OTOH,
> happens after association.  Basically, never use shared authentication.
> 
> (Shared requires a WEP key.  It also informs everyone sniffing your
> association frames of that WEP key; it's *extremely* insecure.  I don't
> know how "both" would work, but AFAIK, WPA and WPA2 both require open.)
> 
> The open/shared choice should only be made if you configure the AP for
> WEP.
> 
> > then on another setup stage I chose whether to have WPA-PSK or not, 
> > with the possibility of introducing a WPA-PSK key. So WEP and WPA 
> > appear as complementary.
> 
> They are not.  It may be possible with some cards to do both WEP and WPA
> on the same SSID, but I don't know how the card would choose.  I don't
> think there's any standard for it, in any case.

Actually, what happens here is that the pairwise key is TKIP or CCMP for
all WPA-capable stations, but the broadcast key is WEP.  WEP-only
clients don't know (or have to) about the pairwise/multicast key
distinction.

So WEP-only clients can just keep doing what they always do and encrypt
_all_ outgoing traffic with the WEP key, regardless of the destination.
WPA-capable clients just encrypt multicast/broadcast packets with the
WEP key, but encrypt unicast packets using the TKIP/CCMP pairwise key
which only the AP can decrypt.  (I don't know how it works when stations
want to talk directly to each other though.)

So you _can_ have WEP and WPA coexist on the same network, but you loose
any security for multicast or broadcast frames because they are always
encrypted with lowest-common-denomiator (WEP) and therefore are
insecure.

Dan

> > is there a "proper" basic (wep?) cryptographic setup to be used with 
> > WPA?  This is very confusing and the Hamlet manual does not help.
> 
> Authentication, as in the frames sent just before association, must be
> set to open.  WPA and WPA2 handle key exchange, ensuring the client is
> authorized, and setting up data frame encryption.
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From dcbw  Mon Dec 18 11:41:04 2006
From: dcbw (Dan Williams)
Date: Mon, 18 Dec 2006 14:41:04 -0500
Subject: devicescape headers changed.
In-Reply-To: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
Message-ID: <1166470864.30000.7.camel@localhost.localdomain>

On Mon, 2006-12-18 at 19:24 +0000, miknix wrote:
> Hi there.
> 
> Devicescape has unified net/d80211_common.h and net/d80211_shared.h
> into d80211.h. Could someone update driver_devicescape to reflect
> these changes? The rt2x00 development team is using this version for a
> while.. 

And the rt2x00 team is not using driver_wext for what exact reason?

Dan

> About the hostapd cvs repos. I cannot checkout sources using anonymous
> access, is it working?
> 
> Thank you.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From miknix  Mon Dec 18 12:13:32 2006
From: miknix (miknix)
Date: Mon, 18 Dec 2006 20:13:32 +0000
Subject: devicescape headers changed.
In-Reply-To: <1166470864.30000.7.camel@localhost.localdomain>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
Message-ID: <766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>

When compiling hostapd-0.6-2006-12-15 with dscape included in latest rt2x00.

I get this:
gcc -MMD -O2 -Wall -g -DHOSTAPD_DUMP_STATE -I. -I../utils -I.
-I/usr/src/linux/include -I/usr/src/rt2x00/ieee80211 -D_LINUX_TYPES_H
-DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DCONFIG_RSN_PREAUTH
-DCONFIG_DRIVER_HOSTAP -DCONFIG_DRIVER_DEVICESCAPE -DINTERNAL_AES
-DINTERNAL_SHA1 -DINTERNAL_SHA256 -DINTERNAL_MD5 -DCONFIG_IPV6   -c -o
driver_devicescape.o driver_devicescape.c
driver_devicescape.c:41:31: warning: net/d80211_common.h: No such file or
directory
driver_devicescape.c:42:31: warning: net/d80211_shared.h: No such file or
directory
driver_devicescape.c: In function `i802_set_rate_sets':
driver_devicescape.c:234: error: `MODE_IEEE80211A' undeclared (first use in
this function)
driver_devicescape.c:234: error: (Each undeclared identifier is reported
only once
driver_devicescape.c:234: error: for each function it appears in.)
driver_devicescape.c:237: error: `MODE_IEEE80211B' undeclared (first use in
this function)
driver_devicescape.c:240: error: `MODE_IEEE80211G' undeclared (first use in
this function)
driver_devicescape.c: In function `i802_set_freq':
driver_devicescape.c:364: error: `MODE_IEEE80211A' undeclared (first use in
this function)
driver_devicescape.c:367: error: `MODE_IEEE80211B' undeclared (first use in
this function)
driver_devicescape.c:370: error: `MODE_IEEE80211G' undeclared (first use in
this function)
driver_devicescape.c: In function `i802_set_channel_flag':
driver_devicescape.c:738: error: `MODE_IEEE80211A' undeclared (first use in
this function)
driver_devicescape.c:741: error: `MODE_IEEE80211B' undeclared (first use in
this function)
driver_devicescape.c:744: error: `MODE_IEEE80211G' undeclared (first use in
this function)
driver_devicescape.c: In function `i802_get_hw_feature_data':
driver_devicescape.c:1131: error: `MODE_IEEE80211A' undeclared (first use in
this function)
driver_devicescape.c:1134: error: `MODE_IEEE80211B' undeclared (first use in
this function)
driver_devicescape.c:1137: error: `MODE_IEEE80211G' undeclared (first use in
this function)
driver_devicescape.c: At top level:
driver_devicescape.c:1193: warning: "struct ieee80211_frame_info" declared
inside parameter list
driver_devicescape.c:1193: warning: its scope is only this definition or
declaration, which is probably not what you want
driver_devicescape.c:1308: warning: "struct ieee80211_frame_info" declared
inside parameter list
driver_devicescape.c: In function `dump_frame_info':
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1312: error: dereferencing pointer to incomplete type
driver_devicescape.c:1316: error: dereferencing pointer to incomplete type
driver_devicescape.c:1317: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1318: error: dereferencing pointer to incomplete type
driver_devicescape.c:1320: error: dereferencing pointer to incomplete type
driver_devicescape.c:1321: error: dereferencing pointer to incomplete type
driver_devicescape.c:1322: error: dereferencing pointer to incomplete type
driver_devicescape.c:1323: error: dereferencing pointer to incomplete type
driver_devicescape.c:1324: error: dereferencing pointer to incomplete type
driver_devicescape.c:1325: error: dereferencing pointer to incomplete type
driver_devicescape.c:1326: error: dereferencing pointer to incomplete type
driver_devicescape.c:1327: error: dereferencing pointer to incomplete type
driver_devicescape.c:1328: error: dereferencing pointer to incomplete type
driver_devicescape.c:1329: error: dereferencing pointer to incomplete type
driver_devicescape.c:1330: error: dereferencing pointer to incomplete type
driver_devicescape.c: At top level:
driver_devicescape.c:1351: warning: "struct ieee80211_frame_info" declared
inside parameter list
driver_devicescape.c: In function `handle_frame':
driver_devicescape.c:1360: error: dereferencing pointer to incomplete type
driver_devicescape.c:1364: error: `ieee80211_msg_set_aid_for_sta' undeclared
(first use in this function)
driver_devicescape.c:1370: error: `ieee80211_msg_key_threshold_notification'
undeclared (first use in this function)
driver_devicescape.c:1381: error: `ieee80211_msg_sta_not_assoc' undeclared
(first use in this function)
driver_devicescape.c:1422: error: `ieee80211_msg_passive_scan' undeclared
(first use in this function)
driver_devicescape.c:1431: error: `ieee80211_msg_normal' undeclared (first
use in this function)
driver_devicescape.c:1435: error: `ieee80211_msg_tx_callback_ack' undeclared
(first use in this function)
driver_devicescape.c:1438: error: `ieee80211_msg_tx_callback_fail'
undeclared (first use in this function)
driver_devicescape.c:1441: error: `ieee80211_msg_wep_frame_unknown_key'
undeclared (first use in this function)
driver_devicescape.c:1444: error: `ieee80211_msg_michael_mic_failure'
undeclared (first use in this function)
driver_devicescape.c:1462: error: dereferencing pointer to incomplete type
driver_devicescape.c:1463: error: dereferencing pointer to incomplete type
driver_devicescape.c:1464: error: dereferencing pointer to incomplete type
driver_devicescape.c:1465: error: dereferencing pointer to incomplete type
driver_devicescape.c:1466: error: dereferencing pointer to incomplete type
driver_devicescape.c: In function `handle_read':
driver_devicescape.c:1514: error: invalid application of `sizeof' to
incomplete type `ieee80211_frame_info'
driver_devicescape.c:1521: error: dereferencing pointer to incomplete type
driver_devicescape.c:1521: error: `IEEE80211_FI_VERSION' undeclared (first
use in this function)
driver_devicescape.c:1523: warning: passing arg 1 of `dump_frame_info' from
incompatible pointer type
driver_devicescape.c:1528: error: invalid application of `sizeof' to
incomplete type `ieee80211_frame_info'
driver_devicescape.c:1529: error: invalid application of `sizeof' to
incomplete type `ieee80211_frame_info'
driver_devicescape.c:1530: warning: passing arg 4 of `handle_frame' from
incompatible pointer type
make: *** [driver_devicescape.o] Error 1

Since begining of december, I think, I could not compile hostapd anymore
with none of the rt2x00 snapshots.



On 12/18/06, Dan Williams <dcbw at redhat.com> wrote:
>
> On Mon, 2006-12-18 at 19:24 +0000, miknix wrote:
> > Hi there.
> >
> > Devicescape has unified net/d80211_common.h and net/d80211_shared.h
> > into d80211.h. Could someone update driver_devicescape to reflect
> > these changes? The rt2x00 development team is using this version for a
> > while..
>
> And the rt2x00 team is not using driver_wext for what exact reason?
>
> Dan
>
> > About the hostapd cvs repos. I cannot checkout sources using anonymous
> > access, is it working?
> >
> > Thank you.
> > _______________________________________________
> > 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/20061218/6859af5a/attachment.htm 


From jbarnett  Mon Dec 18 13:04:39 2006
From: jbarnett (jbarnett at coleinnovations.com)
Date: Mon, 18 Dec 2006 16:04:39 -0500 (EST)
Subject: Need help programming a prism card
Message-ID: <3263.128.132.174.49.1166475879.squirrel@www.coleinnovations.com>

Hi,
Iv'e been working on this problem for some time now, and I am in need
for some much needed help. Let me first describe what I am trying to
accomplish, I current have a Intersil PRISM 2 (802.11b) PCMCIA wireless

card; the card has three LEDs on the top part of the card. One of these


LEDs is the power LED, which lights green when the card is turned on.


The PRISM 2 wireless card came with the old linux-wlan-ng 2.0 drivers;
very out of date, and it also came with a tiny piece of software. This
piece of software has a couple of functions that are used to control
the wireless card; but the main function that I am interested in, is
the function that turns the card on, called "cardon". When I properly
configure the card using the linux-wlan-ng tools, and then run,
"./cardon wlan0". The power LED light turns green, and I then run
"tcpdump -x -X -s 2346 -vvv -i wlan0", which displays the expected
results to standard out.


My goal is to make this card work with the hostap-driver-0.4.9; which
is the newest drivers for the PRISM chipset. I am currently running
slackware 10.2 with the 2.4.31 kernel. The reason I want my wireless
card to work with the hostAP drivers is because I can use programs like


iwconfig, iwpriv, etc.


Now, when I insert the PRISM 2 wireless card into my PCMCIA slot, with
the hostAP drivers, the lights on the card flash; twice, then they go
blank. Now when I go and run "./cardon wlan0" the card should turn on,
but it doesn't because the "cardon" program is meant to communicate
with the linux-wlan-ng drivers; not the hostAP drivers.


I started to develope a new application that will turn the card on, and


will work with the hostAP driver. I beleive I am using the correct
value for the second aurgument to the ioctl call. I am not very good at


programming low level devices, but what I beleive is going on, is the
hex value gets sent to the wireless card which turns the card on; the
hex number is specific to the card. Once the ioctl is sent over the
socket; the card changes certain values in a structure, known as
comm_t. Im getting return values, from the comm_t struct, but not the
correct values.


The correct values that comm_t is suppose to return are..
NOTE: This is being ran using the linux-wlan-ng drivers


cmd: 24 = 0x11
param0:  0 = 0x00
param1:  0 = 0x00
param2:  0 = 0x00
response0:  0 = 0x00
response1:  0 = 0x00
response2: 24 = 0x11
status:     1 = 0x01


The incorrect values for comm_t are ..
NOTE: This is being ran using the hostAP drivers, these values value
sometimes..


cmd: 226 = 0xE2
param0: 101 = 0x65
param1: 230 = 0xE6
param2: 116 = 0x74
response0: 232 = 0xE8
response1: 105 = 0x69
response2: 238 = 0xEE
status:    114 = 0x72


Here is the code that I currently have been working on, this compiles
fine, but im just not getting the green LED light to turn on..


//----------------------------------------cardon.h-------------------------??--------------------


#define  ERR          1      /*error condition */
#define  MSIZE        4000        /* The message size */
#define  NAMELEN     16          /* length of device name */
#define  TURNCARDON    0x11        /* Turn card on command */


typedef char format_t [10];


typedef struct commt
{
   char header[32]                       __attribute__ ((packed));
   unsigned short cmd                __attribute__ ((packed));  /* The
command */
   format_t format1                       __attribute__ ((packed));
/*params for cmd*/
   unsigned short param0             __attribute__ ((packed));  /*
param0*/
   format_t format2                       __attribute__ ((packed));
   unsigned short param1             __attribute__ ((packed));  /*
param1*/
   format_t format3                       __attribute__ ((packed));
   unsigned short param2             __attribute__ ((packed));  /*
param2*/
   format_t format4                       __attribute__ ((packed));
/*response for cmd*/
   unsigned short response0          __attribute__ ((packed));  /*
response0 */
   format_t format5                       __attribute__ ((packed));
   unsigned short response1          __attribute__ ((packed));  /*
response1 */
   format_t format6                       __attribute__ ((packed));
   unsigned short response2          __attribute__ ((packed));  /*
response2 */
   format_t format7                       __attribute__ ((packed));
   unsigned short stat             __attribute__ ((packed));  /* The
status of the command */



} __attribute__ ((packed)) comm_t;


#define REQUESTLOWLEVEL  {0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00, 0x01, 0x00, \
                          0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00, 0x01, 0x00, \
                          0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00, 0x01, 0x00, \
                          0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00, 0x01, 0x00, \
                          0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00, 0x01, 0x00, \
                          0x00, 0x00, 0xc5, 0x41, \
                          0x00, 0x00, 0x00, 0x00, \
                          0x04, 0x00, 0x00, 0x00, \
                          0x00, 0x00, 0xc5, 0x51, \
                          0x00, 0x00}

//-----------------------------------------cardon.c------------------------??-------------------------


/* Standard wireless file, that comes with hostAP */
#include "wireless.h"


unsigned long return = 0;                    // The return value
char requestlowlevel[]= REQUESTLOWLEVEL;  // The command string
int   sd;          // The socket that the request is sent to


struct iwreq iwr;  //From wireless.h


unsigned char msg[MSIZE];               // The command
comm_t*    cmd = (comm_t*)ms;      // fill in the arguments into the
message.
                                   // Not sure if this is correct!!
bzero(ms, MSIZE);
memcpy(ms, requestlowlevel, sizeof(requestlowlevel));   //Not sure if
this is correct!!


// Fill in the message
cmd->cmd = TURNCARDON;


memset(&iwr, 0, sizeof(iwr));
strncpy(iwr.ifr_name, name, NAMELEN);
iwr.u.data.pointer = (caddr_t*)ms;                       //Not sure if
this is correct!!
iwr.u.data.length = MSIZE;


/* Create socket */
sd = socket(AF_INET, SOCK_STREAM, 0);


if(-1 == sd){
     perror("Could not open socket");
     return = ERR;



}


if(0 == ret){
     /* Do ioctl call */
     /* Note sure if the SIOCGIWPRIV is correct */
     if (ioctl(sd, SIOCGIWPRIV, &iwr)  == -1){
          perror("Bad ioctl request");
          return = ERR;
     }


}


return = (return|!cmd->stat);
return(return);


}


//-----------------------------END-----------------------------------------

Once again, as i said before, I am pretty new to programming low level
devices. Any help will be appreciated, I am looking for ideas,
examples, and type of help. I have been going at this problem for a
long while now.


Thanks,
Jimmie






From bryan  Mon Dec 18 18:43:16 2006
From: bryan (Bryan Kadzban)
Date: Mon, 18 Dec 2006 21:43:16 -0500
Subject: wpa_supplicant fails and reports weird AP address	in	association
In-Reply-To: <1166470820.30000.5.camel@localhost.localdomain>
References: <457E8F60.1000706@arces.unibo.it>	
	<1165928020.2747.7.camel@localhost.localdomain>	
	<457EB0C5.1000908@arces.unibo.it>	
	<200612130018.55939.kelmo@kanotixguide.org>	
	<20061212174024.GA4704@kadzban.is-a-geek.net>	
	<4586BB19.3000807@arces.unibo.it>
	<4586E98E.5060103@kadzban.is-a-geek.net>
	<1166470820.30000.5.camel@localhost.localdomain>
Message-ID: <458751C4.5060200@kadzban.is-a-geek.net>

Dan Williams wrote:
> Actually, what happens here is that the pairwise key is TKIP or CCMP
> for all WPA-capable stations, but the broadcast key is WEP.

Oh, right, duh.  I forgot about that one.

Thanks.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061218/229d8b0a/attachment.pgp 


From matt  Mon Dec 18 18:55:54 2006
From: matt (Matt Brown)
Date: Tue, 19 Dec 2006 15:55:54 +1300
Subject: [patch] bind to own_ip_addr for RADIUS communications
Message-ID: <458754BA.5060004@mattb.net.nz>

Hi,

The attached patch forces hostapd to bind to the own_ip_addr specified
in the configuration file for all RADIUS auth and acct traffic. This is
desirable as many RADIUS servers authenticate clients based on an (ip,
shared secret) tuple. If the hostapd machine has multiple interfaces
with redundant connections to the RADIUS server it is possible that
source IP address that the RADIUS server sees will not be consistent.

The patch also fixes what appeared to be a minor bug with v6 in
radius_client_init_acct. The v6 socket was never opened, but code later
in the function tried to use it regardless.

I had to rearrange where the own_ip_addr parameter is stored in the
config structures so that it was available to the radius_init routines.

I hope you find this useful.

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: hostapd-bind-own_ip_addr.diff
Type: text/x-patch
Size: 7892 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061219/cc29abbb/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061219/cc29abbb/attachment.pgp 


From jkmaline  Mon Dec 18 19:25:57 2006
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Dec 2006 19:25:57 -0800
Subject: seg fault when interface does not exist
In-Reply-To: <200612181613.33888.kelmo@kanotixguide.org>
References: <200612180715.42193.kelmo@kanotixguide.org>
	<20061218045348.GD9711@jm.kir.nu>
	<200612181613.33888.kelmo@kanotixguide.org>
Message-ID: <20061219032557.GB6633@jm.kir.nu>

On Mon, Dec 18, 2006 at 04:13:33PM +1000, Kel Modderman wrote:

> Debian 0.5.6-1 binary. No modification to your tarball apart from a patch that 
> points to specific doc's. The following config is used (madwifi headers are 
> activated via another patch):

OK, I was able to reproduce this with 0.5.6 using the included .config.
This was fixed couple of weeks ago and I merged the fix into 0.5.x
branch a week ago, so I believe the issue is resolved.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Dec 18 19:39:56 2006
From: jkmaline (Jouni Malinen)
Date: Mon, 18 Dec 2006 19:39:56 -0800
Subject: devicescape headers changed.
In-Reply-To: <766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
Message-ID: <20061219033956.GC6633@jm.kir.nu>

On Mon, Dec 18, 2006 at 08:13:32PM +0000, miknix wrote:

> When compiling hostapd-0.6-2006-12-15 with dscape included in latest rt2x00.

> driver_devicescape.c:41:31: warning: net/d80211_common.h: No such file or
> directory

Which kernel version is this using? The current wireless-dev.git tree
seems to still come with net/d80211_common.h and net/d80211_shared.h..

> >On Mon, 2006-12-18 at 19:24 +0000, miknix wrote:

> >> About the hostapd cvs repos. I cannot checkout sources using anonymous
> >> access, is it working?

CVS pserver is not available anymore. You can either download snapshot
releases from http://hostap.epitest.fi/releases/snapshots/ or a CVS
snapshot through viewcvs
http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/hostap/hostap.tar.gz?tarball=1

I'm planning on moving 0.6.x development into git soon(ish), so that may
also make it easier to get up-to-date versions of the development tree.

-- 
Jouni Malinen                                            PGP id EFC895FA



From yann.garcia  Tue Dec 19 00:00:34 2006
From: yann.garcia (Yann Garcia)
Date: Tue, 19 Dec 2006 09:00:34 +0100
Subject: wpa_supllicant on Windows XP : stange DHCP behavior when using WEP
Message-ID: <00d201c72343$c43272d0$0c01000a@smartcomnet.local>

Hello,

 

I use the version 0.5.6 of wpa_supplicant.

wpa_supplicant v0.5.6

Copyright (c) 2003-2006, Jouni Malinen <jkmaline at cc.hut.fi> and contributors

In a first time, I also thought that it was about a problem of. But in this
case, it won?t work with WZC?

 

Thanks again for your help,

 

Best regards,

 

Yann



  _____  

De : Jouni Malinen
Envoy? : vendredi 15 d?cembre 2006 19:49
? : Yann Garcia

Objet : RE: wpa_supllicant on Windows XP : stange DHCP behavior when using
WEP

Hi all,

 

> The Windows XP client uses wpa_supplicant to establish the connection.

Which version of wpa_supplicant are you using?

> * Without WEP, all works fine;
> * With WEP, the access point never receive the DHCP Discover request
> (tcpdump doesn't see any packet on the wlan0 interface) but (it's
strange!)
> I can see (ethereal on windows) the DHCP Discover packets sent on the
client
> interface. In the /var/log/messages, I can see that the association is
> established by hostapd.


Sounds like the driver did not understand how the WEP key was configured
or it dropped it for some reason.

 

 

  _____  

De : Yann Garcia [mailto:yann.garcia at smartcom.com] 
Envoy? : vendredi 15 d?cembre 2006 15:23
? : 'hostap at shmoo.com'
Objet : wpa_supllicant on Windows XP : stange DHCP behavior when using WEP

 

Hi all,

 

I?ve got a problem and I don?t really understand what happening. I want to
connect my Windows client (Netgear WG111v2) to my hotspot (WEP secured).

A Linux box with Hostapd/Chillispot/Radius works as an access point.

The Windows XP client uses wpa_supplicant to establish the connection.

 

Here is my problem:

*	Without WEP, all works fine;
*	With WEP, the access point never receive the DHCP Discover request
(tcpdump doesn?t see any packet on the wlan0 interface) but (it?s strange!)
I can see (ethereal on windows) the DHCP Discover packets sent on the client
interface. In the /var/log/messages, I can see that the association is
established by hostapd.

 

So I don?t really understand what happening.

 

The configuration seems to be ok because I can connect my client to the
hotspot (with WEP enable) using WZC.

 

Please anyone can help me?

 

Thanks a lot for your help,

 

Yann

 

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


From rememberme  Tue Dec 19 04:58:25 2006
From: rememberme (Henk Vergonet)
Date: Tue, 19 Dec 2006 13:58:25 +0100
Subject: TKIP: replay detected:
In-Reply-To: <20061218045549.GE9711@jm.kir.nu>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
	<1166370132.2757.17.camel@localhost.localdomain>
	<20061218045549.GE9711@jm.kir.nu>
Message-ID: <20061219125825.GA24833@god.dyndns.org>

On Sun, Dec 17, 2006 at 08:55:49PM -0800, Jouni Malinen wrote:
> On Sun, Dec 17, 2006 at 10:42:12AM -0500, Dan Williams wrote:
> > > On Tue, Dec 12, 2006 at 09:53:14AM +0100, Vincent Panel wrote:
> > > > I get a lot of these messages in my kernel log :
> > > > 
> > > > kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> > > > 0000000004a9 received TSC 0000000004a8
> 
> > I believe he said ipw3945...
> 
> In that case I would recommend asking this on the ipw3945 mailing list,
> not here.. It is driver specific and I my guess would be that ipw3945
> driver is not filtering out duplicate frames based on seq# before
> processing TKIP replays.
> 

I have a similar problem with an ipw2200.




From dcbw  Mon Dec 18 14:42:37 2006
From: dcbw (Dan Williams)
Date: Mon, 18 Dec 2006 17:42:37 -0500
Subject: No networks enabled - do not scan
Message-ID: <1166481757.11190.10.camel@localhost.localdomain>

This particular hunk [1] in wpa_supplicant presents a problem for
NetworkManager... First, NM must ask for scan results before it can tell
wpa_supplicant which network to use, of course, but wpa_supplicant
doesn't scan until it's told which network to use.  We lose.

This appears to work on the first scan request, because wpa_supplicant
does an initial scan automatically.  But thereafter, it does not scan
unless there's a configured network.  I understand why this is desirable
for standalone wpa_supplicant, but it certainly won't work with
NetworkManager.

Thoughts?

Dan

[1] wpa_supplicant.c:wpa_supplicant_scan, ~ line 1008

	if (wpa_s->disconnected)
		return;

	enabled = 0;
	ssid = wpa_s->conf->ssid;
	while (ssid) {
		if (!ssid->disabled) {
			enabled++;
			break;
		}
		ssid = ssid->next;
	}
	if (!enabled && !wpa_s->scan_req) {
		wpa_printf(MSG_DEBUG, "No enabled networks - do not scan");
		wpa_supplicant_set_state(wpa_s, WPA_INACTIVE);
		return;
	}
	scan_req = wpa_s->scan_req;
	wpa_s->scan_req = 0;





From miknix  Tue Dec 19 06:23:31 2006
From: miknix (miknix)
Date: Tue, 19 Dec 2006 14:23:31 +0000
Subject: devicescape headers changed.
In-Reply-To: <20061219033956.GC6633@jm.kir.nu>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
Message-ID: <766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>

I'm using 2.6.17-gentoo-r4.

On 12/19/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Mon, Dec 18, 2006 at 08:13:32PM +0000, miknix wrote:
>
> > When compiling hostapd-0.6-2006-12-15 with dscape included in latest
> rt2x00.
>
> > driver_devicescape.c:41:31: warning: net/d80211_common.h: No such file
> or
> > directory
>
> Which kernel version is this using? The current wireless-dev.git tree
> seems to still come with net/d80211_common.h and net/d80211_shared.h..
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061219/41679e07/attachment.htm 


From dcbw  Tue Dec 19 06:31:37 2006
From: dcbw (Dan Williams)
Date: Tue, 19 Dec 2006 09:31:37 -0500
Subject: devicescape headers changed.
In-Reply-To: <766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
	<766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
Message-ID: <1166538698.2753.8.camel@localhost.localdomain>

On Tue, 2006-12-19 at 14:23 +0000, miknix wrote:
> I'm using 2.6.17-gentoo-r4.

If the rt2x00 team has updated their driver to use the latest
wireless-dev (which they should be doing!), which is really new, it
likely won't work on your kernel.  You should probably update to a
2.6.19 or later kernel.  Optionally, you go back to a version of the
driver that _does_ work on your kernel.  You appear to be trying to
compile the rt2x00 driver using sources that are way too old.

Dan

> On 12/19/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>         On Mon, Dec 18, 2006 at 08:13:32PM +0000, miknix wrote:
>         
>         > When compiling hostapd-0.6-2006-12-15 with dscape included
>         in latest rt2x00.
>         
>         > driver_devicescape.c:41:31: warning: net/d80211_common.h: No
>         such file or 
>         > directory
>         
>         Which kernel version is this using? The current
>         wireless-dev.git tree
>         seems to still come with net/d80211_common.h and
>         net/d80211_shared.h..
>         
>         --
>         Jouni Malinen                                            PGP
>         id EFC895FA 
>         _______________________________________________
>         HostAP mailing list
>         HostAP at shmoo.com
>         http://lists.shmoo.com/mailman/listinfo/hostap
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From yohonet  Tue Dec 19 06:35:18 2006
From: yohonet (Vincent Panel)
Date: Tue, 19 Dec 2006 14:35:18 +0000
Subject: Fwd: TKIP: replay detected:
In-Reply-To: <15116fd10612190634i2dffe78atfb01a342bfc5e5e4@mail.gmail.com>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
	<1166370132.2757.17.camel@localhost.localdomain>
	<20061218045549.GE9711@jm.kir.nu>
	<20061219125825.GA24833@god.dyndns.org>
	<15116fd10612190634i2dffe78atfb01a342bfc5e5e4@mail.gmail.com>
Message-ID: <15116fd10612190635r27e951b6g43ef5a317828a426@mail.gmail.com>

---------- Forwarded message ----------
From: Vincent Panel <yohonet at gmail.com>
Date: Dec 19, 2006 2:34 PM
Subject: Re: TKIP: replay detected:
To: Henk Vergonet <rememberme at god.dyndns.org>


On 12/19/06, Henk Vergonet <rememberme at god.dyndns.org> wrote:
> On Sun, Dec 17, 2006 at 08:55:49PM -0800, Jouni Malinen wrote:
> > On Sun, Dec 17, 2006 at 10:42:12AM -0500, Dan Williams wrote:
> > > > On Tue, Dec 12, 2006 at 09:53:14AM +0100, Vincent Panel wrote:
> > > > > I get a lot of these messages in my kernel log :
> > > > >
> > > > > kernel: TKIP: replay detected: STA=00:0b:0e:02:95:09 previous TSC
> > > > > 0000000004a9 received TSC 0000000004a8
> >
> > > I believe he said ipw3945...
> >
> > In that case I would recommend asking this on the ipw3945 mailing list,
> > not here.. It is driver specific and I my guess would be that ipw3945
> > driver is not filtering out duplicate frames based on seq# before
> > processing TKIP replays.
> >
>
> I have a similar problem with an ipw2200.
>
I still have the same problem from time to time and my connection is
incredibly slow when it occurs... Could it be linked to the fact that
several access points belonging to the same ESSID surround me (of
course, they have different AP adresses) ?

(Grr... forgot reply to all again... sorry)



From miknix  Tue Dec 19 06:52:15 2006
From: miknix (miknix)
Date: Tue, 19 Dec 2006 14:52:15 +0000
Subject: devicescape headers changed.
In-Reply-To: <1166538698.2753.8.camel@localhost.localdomain>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
	<766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
	<1166538698.2753.8.camel@localhost.localdomain>
Message-ID: <766169df0612190652k2fed23d1j38415ba1c73c08f4@mail.gmail.com>

The latest rt2x00 driver does work in this kernel :\
But, I'm trying to make a home AP using hostapd. Since end of november I
could not build hostapd against none of rt2x00 snapshots.

The older-than-dezember rt2x00 driver is useless with hostapd since it has
some issues that prevents comunication after some packets.
That is, I can associate my client to hostapd with wpa. Client receives it's
IP by dhcp. Client can connect to remote hosts and request some data, but
after a while the AP stops responding, not even a beacon!
I think latest versions of rt2x00 have been fixed, but none of them builds
with hostapd :(

Still want me to test with a fresh 2.6.19 vanilla?

On 12/19/06, Dan Williams <dcbw at redhat.com> wrote:
>
> On Tue, 2006-12-19 at 14:23 +0000, miknix wrote:
> > I'm using 2.6.17-gentoo-r4.
>
> If the rt2x00 team has updated their driver to use the latest
> wireless-dev (which they should be doing!), which is really new, it
> likely won't work on your kernel.  You should probably update to a
> 2.6.19 or later kernel.  Optionally, you go back to a version of the
> driver that _does_ work on your kernel.  You appear to be trying to
> compile the rt2x00 driver using sources that are way too old.
>
> Dan
>
> > On 12/19/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> >         On Mon, Dec 18, 2006 at 08:13:32PM +0000, miknix wrote:
> >
> >         > When compiling hostapd-0.6-2006-12-15 with dscape included
> >         in latest rt2x00.
> >
> >         > driver_devicescape.c:41:31: warning: net/d80211_common.h: No
> >         such file or
> >         > directory
> >
> >         Which kernel version is this using? The current
> >         wireless-dev.git tree
> >         seems to still come with net/d80211_common.h and
> >         net/d80211_shared.h..
> >
> >         --
> >         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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061219/8b8f51ba/attachment.htm 


From alex  Tue Dec 19 07:11:40 2006
From: alex (Alex Pounds)
Date: Tue, 19 Dec 2006 15:11:40 -0000 (GMT)
Subject: HostAP and WPA2 with Intersil Prism card
In-Reply-To: <161717d50612180717r6d80dbeen67a6cf4806ebcf31@mail.gmail.com>
References: <53464.193.203.83.22.1165926032.squirrel@webmail.alexpounds.com> 
	<161717d50612120740xc6c1fb2s4d292a744853397d@mail.gmail.com> 
	<39508.193.203.83.22.1166008188.squirrel@webmail.alexpounds.com> 
	<161717d50612130459x60ece9dfh266384a57aadda8a@mail.gmail.com> 
	<20061215001302.GA17496@localhost.localdomain> 
	<161717d50612150754q51ab75d7kbd9e7fd601c6f598@mail.gmail.com> 
	<20061216133352.GA25998@localhost.localdomain> 
	<45855775.7010807@pcuf.fi> 
	<20061218003834.GA4636@localhost.localdomain> 
	<4586A30B.9080008@mobilerobots.com>
	<161717d50612180717r6d80dbeen67a6cf4806ebcf31@mail.gmail.com>
Message-ID: <37924.193.203.83.22.1166541100.squirrel@webmail.alexpounds.com>

On Mon, December 18, 2006 3:17 pm, Dave Neuer wrote:
> On 12/18/06, Aaron Baillargeon <abaillargeon at mobilerobots.com> wrote:
>> Alex Pounds wrote:
>> > I've downgraded to 1.7.4, but I have exactly the same problem as before.
>> > Debugging output with -dd from wpa_supplicant is pretty much identical
>> > (sometimes it receives 3 BSSIDs instead of 1 from the previous session).
>>
>> Just from staring at these for a couple days, the debug output seems
>> like it might be a config error on either the authentication server or
>> the client. From the log it seems you're using wpa2-psk/ccmp?, have you
>> tried wpa-psk/tkip or other configs and gotten them to work?
>
> FWIW, I'm using TKIP only, and I have the same problem. I did find
> that when I connect w/ a static-style startup script, I can't connect
> long enough to use the connection at all.

I had a play last night with different methods, but got the same result for
all of them. I also fiddled with the config options, but I believe the
wpa_supplicant defaults are quite permissive and the options are more for
restricting the program to certain methods.

My router (A Linksys - I think it's called a "WRT54TG", though I'm not sure)
offers two options that look good - WPA Personal and WPA2 Personal. IT also
offers an Enterprise option for these, but I don't have a RADIUS server so
that seems irrelevant. For WPA Personal I can choose between AES and TKIP;
WPA2 offers "AES" and "AES+TKIP", which I understand actually means "Use AES
if you can, fall back to TKIP if you can't."

Anyway, I tried all four options, but I still got my associated/unassociated
flip-flopping described previously. As I say, my desktop PC can connect
fine, so I'm really not sure where the problem lies - either with the hostap
driver or the wifi card itself, I suppose (my desktop is not prism-based).

So, what now? Is there some more debugging output I can provide to try and
nail down the problem more? Is there an alternative (ndiswrapper?) I can use
that may work and get me using WPA2 with this access point?

Thank you,

-- 
Alex Pounds (Creature)                  .~.         http://www.alexpounds.com/
                                        /V\        http://www.ethicsgirls.com/
                                       // \\
"Variables won't; Constants aren't"   /(   )\
                                       ^`~'^




From vschmidt  Tue Dec 19 07:31:48 2006
From: vschmidt (Val Schmidt)
Date: Tue, 19 Dec 2006 10:31:48 -0500
Subject: wpa_supplicant in ad-hoc mode
Message-ID: <D501FD3C-A082-4921-8E94-1CC60AEF6226@ccom.unh.edu>

Hello,

I am interested in encrypting a long haul point-to-point-link that  
runs in ad-hoc mode. I've looked through the documentation for wpa- 
supplicant and it is not clear to me that wpa supplicant supports  
point-to-point links in ad-hoc mode. Is this true?

If so, if anyone has any suggestions on security in such a set-up I'd  
love to hear your thoughts.

Thanks,

Val

------------------------------------------------------
Val Schmidt
CCOM/JHC
University of New Hampshire
Chase Ocean Engineering Lab
24 Colovos Road
Durham, NH 03824
e: vschmidt [AT] ccom.unh.edu
m: 614.286.3726


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


From paris_ste_82  Tue Dec 19 08:14:54 2006
From: paris_ste_82 (Stefano Paris)
Date: Tue, 19 Dec 2006 17:14:54 +0100 (CET)
Subject: wpa_supplicant in ad hoc mode
Message-ID: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>

Hi,

I tried to connect 3 pc in ad hoc mode with the followed configuration file:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2
network={
    ssid="ibss-test"
    mode=1
    proto=WPA
    key_mgmt=WPA-NONE
    pairwise=NONE
    group=CCMP
    psk="ibss-test-key"
}

I used madwifi driver .

When I started wpa_supplicant just 2 pc could communicate, the other one remained out, even if the cell and the key were the same of the other pcs.
The problem seems to be the same that Ly Hong posted at Jul 14 2006 (wpa-supplicant for ad hoc network with more than 2 nodes).

Has someone able to solve the problem?

I thank anyone for any suggestion.


 __________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061219/84c220d8/attachment.htm 


From dcbw  Tue Dec 19 10:32:29 2006
From: dcbw (Dan Williams)
Date: Tue, 19 Dec 2006 13:32:29 -0500
Subject: No networks enabled - do not scan
In-Reply-To: <1166481757.11190.10.camel@localhost.localdomain>
References: <1166481757.11190.10.camel@localhost.localdomain>
Message-ID: <1166553150.21065.1.camel@localhost.localdomain>

On Mon, 2006-12-18 at 17:42 -0500, Dan Williams wrote:
> This particular hunk [1] in wpa_supplicant presents a problem for
> NetworkManager... First, NM must ask for scan results before it can tell
> wpa_supplicant which network to use, of course, but wpa_supplicant
> doesn't scan until it's told which network to use.  We lose.
> 
> This appears to work on the first scan request, because wpa_supplicant
> does an initial scan automatically.  But thereafter, it does not scan
> unless there's a configured network.  I understand why this is desirable
> for standalone wpa_supplicant, but it certainly won't work with
> NetworkManager.

So my assertion here may be somewhat wrong.  I see that

	if (!enabled && !wpa_s->scan_req) {

should only suppress the scan if scan_req is 0.  Both the regular
control interface and the dbus control interface set scan_req to 2 when
they request a scan.

I also have now found out that wpa_supplicant is attempting to scan on
the wired interface too, which is quite odd, and is the real source of
this error message.  More investigation necessary to determine whether
the error is in wpa_supplicant or in my usage of it.

Dan

> Thoughts?
> 
> Dan
> 
> [1] wpa_supplicant.c:wpa_supplicant_scan, ~ line 1008
> 
> 	if (wpa_s->disconnected)
> 		return;
> 
> 	enabled = 0;
> 	ssid = wpa_s->conf->ssid;
> 	while (ssid) {
> 		if (!ssid->disabled) {
> 			enabled++;
> 			break;
> 		}
> 		ssid = ssid->next;
> 	}
> 	if (!enabled && !wpa_s->scan_req) {
> 		wpa_printf(MSG_DEBUG, "No enabled networks - do not scan");
> 		wpa_supplicant_set_state(wpa_s, WPA_INACTIVE);
> 		return;
> 	}
> 	scan_req = wpa_s->scan_req;
> 	wpa_s->scan_req = 0;
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From dcbw  Tue Dec 19 10:35:39 2006
From: dcbw (Dan Williams)
Date: Tue, 19 Dec 2006 13:35:39 -0500
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
References: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
Message-ID: <1166553339.21065.4.camel@localhost.localdomain>

On Tue, 2006-12-19 at 17:14 +0100, Stefano Paris wrote:
> Hi,
> 
> I tried to connect 3 pc in ad hoc mode with the followed configuration
> file:
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> ap_scan=2
> network={
>     ssid="ibss-test"
>     mode=1
>     proto=WPA
>     key_mgmt=WPA-NONE
>     pairwise=NONE
>     group=CCMP
>     psk="ibss-test-key"
> }
> 
> I used madwifi driver .
> 
> When I started wpa_supplicant just 2 pc could communicate, the other
> one remained out, even if the cell and the key were the same of the
> other pcs.
> The problem seems to be the same that Ly Hong posted at Jul 14 2006
> (wpa-supplicant for ad hoc network with more than 2 nodes).
> 
> Has someone able to solve the problem?
> 
> I thank anyone for any suggestion.

This could be highly driver dependent.  Without the 'frequency' setting
in your network config (added to 0.5.4 and later I think), the card may
not know which frequency to tune to.  You must have _all_ members of the
adhoc network on the _same_ frequency.

So, on each computer after configuring it with wpa_supplicant, run an
'iwconfig' and look for the frequency/channel #.  If they are all the
same, then we can rule out this issue.

I know that with ipw2200, you need to tell the card which channel to
join explicitly.

Dan




From re2823  Tue Dec 19 19:17:37 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Wed, 20 Dec 2006 03:17:37 +0000
Subject: ndiswrapper/wpa fails but rt2x00/wpa works with identical card/config
Message-ID: <N1-T3_MQmZhWh@Safe-mail.net>

Hi.

I have an rt2561-based pci wireless card that I'm trying to use with
wpa_supplicant. When I use the rt2x00 drivers, wpa_supplicant connects
successfully, but because the drivers are still alpha, the speed is very
bad. When I use ndiswrapper, wpa_supplicant fails to connect at all.
Since I am using the same /etc/wpa_supplicant.conf and the same command
line ("wpa_supplicant -w -d -Dwext -iwlan0 -c/etc/wpa.conf") both times,
I assume that the problem is something to do with ndiswrapper (I could
be wrong).

More details/versions follow:
Card: Edimax EW-7128g (pci rt2561 chipset)
OS: Debian Etch
Kernel: linux 2.6.18
Access point: Asus wl-500g running openwrt white russion rc6

I've tried to attach the debug logs, but then mailman refuses to accept
this mail as it's too big. Instead I've put the 2 wpa_supplicant logs
here:

http://www.carbon.eclipse.co.uk/wpa/rt2x00Success
http://www.carbon.eclipse.co.uk/wpa/ndiswrapperFail

Could someone who understands the output from wpa_supplicant please
confirm whether the ndiswrapper/wpa failure appears to be an
ndiswrapper problem (or does it seem like a wpa_supplicant problem)?

Thank you. Jaime.



From j.witteveen  Wed Dec 20 04:18:49 2006
From: j.witteveen (Jouke Witteveen)
Date: Wed, 20 Dec 2006 13:18:49 +0100
Subject: [PATCH] wpa_supplicant FreeBSD compatibility
Message-ID: <3993a4980612200418u16006e3fred1b0e62c69dc140@mail.gmail.com>

Hello all,

I believe to have made a FreeBSD compatible version of
wpa_supplicant's wired driver. Included are two patches. One for
v0.4.8 (probably works for v0.4.9 as well) and one for v0.5.6.
Please take a quick look and include them in the official tree.
Known bugs:
- when no traffic is received over the multicast address SIOCDELMULTI
throws in a ENOENT ("No such file or directory"). I believe this is
normal; mtest yields it too.
- #ifndef __linux__ is used to check wether we are compiling for BSD.
This is not too elegant (it works though).

regards,
Jouke Witteveen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: driver_wired.c-0.4.8.patch
Type: text/x-patch
Size: 1518 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061220/d4fa1fb1/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: driver_wired.c-0.5.6.patch
Type: text/x-patch
Size: 1340 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061220/d4fa1fb1/attachment-0001.bin 


From re2823  Wed Dec 20 04:33:11 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Wed, 20 Dec 2006 12:33:11 +0000
Subject: ndiswrapper/wpa fails but rt2x00/wpa works with identical
	card/config
Message-ID: <N1-5XSdSV67D3@Safe-mail.net>

-------- Original Message --------
From: kemas henry <k_henry at ramayana.co.id>
To: re2823 at Safe-mail.net
Subject: Re: ndiswrapper/wpa fails but rt2x00/wpa works with identicalcard/config
Date: Wed, 20 Dec 2006 14:42:02 +0700

> would please try this command
> 	wpa_supplicant -w -d -D ndiswrapper -iwlan0 -c/etc/wpa.conf

OK. I have tried ndiswrapper again, but this time I have used
-Dndiswrapper instead of -Dwext thus:

wpa_supplicant -w -d -Dndiswrapper -iwlan0 -c/etc/wpa.conf

Again, wpa_supplicant fails. I have put the debug log here:

http://www.carbon.eclipse.co.uk/wpa/ndiswrapperFail2

Interestingly, I notice that on line 17, it says:
Driver does not support WPA.

so I am not sure if this helps to find out where the problem lies (but
there is no harm in trying).

Jaime



From paris_ste_82  Wed Dec 20 08:19:05 2006
From: paris_ste_82 (Stefano Paris)
Date: Wed, 20 Dec 2006 17:19:05 +0100 (CET)
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <1166553339.21065.4.camel@localhost.localdomain>
Message-ID: <904265.96035.qm@web28115.mail.ukl.yahoo.com>

Hi,

I tried to add the field frequency like you advise me, but when I started wpa_supplicant with the command wpa_supplicant -B -D madwifi -i ath0 -c /etc/wpa_supplicant.conf, I got this error:
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
(the version of wpa_supplicant is 0.5.6)

Anyway, without the field frequency in the configuration file, I started iwconfig and the frequency was the same for every computer, such as key and cell.

Any other idea?

Thank a lot

Dan Williams <dcbw at redhat.com> ha scritto: On Tue, 2006-12-19 at 17:14 +0100, Stefano Paris wrote:
> Hi,
> 
> I tried to connect 3 pc in ad hoc mode with the followed configuration
> file:
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> ap_scan=2
> network={
>     ssid="ibss-test"
>     mode=1
>     proto=WPA
>     key_mgmt=WPA-NONE
>     pairwise=NONE
>     group=CCMP
>     psk="ibss-test-key"
> }
> 
> I used madwifi driver .
> 
> When I started wpa_supplicant just 2 pc could communicate, the other
> one remained out, even if the cell and the key were the same of the
> other pcs.
> The problem seems to be the same that Ly Hong posted at Jul 14 2006
> (wpa-supplicant for ad hoc network with more than 2 nodes).
> 
> Has someone able to solve the problem?
> 
> I thank anyone for any suggestion.

This could be highly driver dependent.  Without the 'frequency' setting
in your network config (added to 0.5.4 and later I think), the card may
not know which frequency to tune to.  You must have _all_ members of the
adhoc network on the _same_ frequency.

So, on each computer after configuring it with wpa_supplicant, run an
'iwconfig' and look for the frequency/channel #.  If they are all the
same, then we can rule out this issue.

I know that with ipw2200, you need to tell the card which channel to
join explicitly.

Dan



 __________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061220/0dde9f7f/attachment.htm 


From Jens.Rutschmann  Wed Dec 20 14:08:35 2006
From: Jens.Rutschmann (Jens Rutschmann)
Date: Wed, 20 Dec 2006 23:08:35 +0100
Subject: WPA/WPA2 with Prism54 card
Message-ID: <4589B463.2040902@online.de>

Hello,
in my Notebook I have a miniPCI card with Intersil Prism54 chipset.
Currently I am forced to use WEP encryption on my wireless network
because wpa_supplicant doesn't support the card right now.

Is there any chance that wpa_supplicants' prism54 driver will be
completed in the near future ?

I read in the mailing list that several components need to support WPA
to get it running:
The hardware: specifications of my chipset say that it supports  "AES
hardware acceleration"
The driver: I use the in-kernel driver (kernel 2.6.18)
And finally wpa_supplicant itself: I guess that concerns
wpa_supplicants' prism54 driver.

Can I even get this running if wpa_supplicants' driver would support it ?
Or would it be better to buy a new card with Atheros or Intel chipset?

Regards,
Jens Rutschmann




From dcbw  Wed Dec 20 16:14:12 2006
From: dcbw (Dan Williams)
Date: Wed, 20 Dec 2006 19:14:12 -0500
Subject: WPA/WPA2 with Prism54 card
In-Reply-To: <4589B463.2040902@online.de>
References: <4589B463.2040902@online.de>
Message-ID: <1166660052.10335.5.camel@localhost.localdomain>

On Wed, 2006-12-20 at 23:08 +0100, Jens Rutschmann wrote:
> Hello,
> in my Notebook I have a miniPCI card with Intersil Prism54 chipset.
> Currently I am forced to use WEP encryption on my wireless network
> because wpa_supplicant doesn't support the card right now.
> 
> Is there any chance that wpa_supplicants' prism54 driver will be
> completed in the near future ?

'wext' is the future (and cfg80211 after that), so card-specific
interfaces shouldn't be used if at all possible.

I ported the WPA support of the prism54 driver to the 'wext'
wpa_supplicant driver a while ago.  It should be able to exist alongside
the prism54-specific ioctls for WPA.  I was not able to extensively test
it, however, because my card died halfway through.

I believe that patch is already upstream.  Could you test it out?  I
think it's in 2.6.19 and later kernels.

There is also another patch floating around (in desperate need of
testers) that completes the 'wext' support of the prism54 driver.  If
the 'wext' bits of prism54 don't work with wpa_supplicant, we need to
fix that.

http://marc.theaimsgroup.com/?l=linux-netdev&m=116453812608332&w=2

Dan

> 
> I read in the mailing list that several components need to support WPA
> to get it running:
> The hardware: specifications of my chipset say that it supports  "AES
> hardware acceleration"
> The driver: I use the in-kernel driver (kernel 2.6.18)
> And finally wpa_supplicant itself: I guess that concerns
> wpa_supplicants' prism54 driver.
> 
> Can I even get this running if wpa_supplicants' driver would support it ?
> Or would it be better to buy a new card with Atheros or Intel chipset?
> 
> Regards,
> Jens Rutschmann
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From leonerd  Wed Dec 20 16:59:32 2006
From: leonerd (Paul LeoNerd Evans)
Date: Thu, 21 Dec 2006 00:59:32 +0000
Subject: wpa_supplicant claims AP doesn't do WPA
Message-ID: <20061221005932.GD27285@cel.leo>

I have a Linksys WAP54G running version 3.04 of their firmware. It's set
to WPA2-Personal, using AES with a preshared key. It is set to
802.11b-only, since I have slight issues from time to time with
G-enabled cards.

My laptop is using a Linksys WPC11 wireless network card. This is an
802.11b card. It's running wpa_supplicant in debian's package, claiming

ii  wpasupplicant         0.5.5-4               Client support for WPA
and WPA2 (IEEE 802.11i)

According to "iwlist scan" it therefore looks like:

wpc11     Scan completed :
          Cell 01 - Address: 00:06:25:xx:xx:xx
                    ESSID:"leoair"
                    Mode:Master
                    Frequency:2.417 GHz (Channel 2)
                    Signal level:56/153  Noise level:13/153
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s

I can't seem to get wpa_supplicant to connect to it though. My config
file for this AP looks like:

network={
        ssid="leoair"
        key_mgmt=WPA-PSK
        psk="xxxxxxxx"

        priority=10
}

Yet, when I run wpa_supplicant in foreground with "-d -d", it says:

...
Received 578 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 10
0: 00:06:25:49:c4:05 ssid='leoair' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
...

No WPA IE? Maybe some item of config is missing here? At the AP's end,
or the wpa_supp's end?

If it's any help, find attached the complete output from:

wpa_supplicant -iwpc11 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
  -d -d

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Initializing interface 'wpc11' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge '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'
ctrl_interface='/var/run/wpa_supplicant'
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=6):
     6c 65 6f 61 69 72                                 leoair          
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=24): [REMOVED]
priority=10 (0xa)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line: 14 - start of a new network block
ssid - hexdump_ascii(len=16):
     42 54 56 4f 59 41 47 45 52 32 30 39 31 2d 41 39   BTVOYAGER2091-A9
scan_ssid=1 (0x1)
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
priority=5 (0x5)
Line: 24 - start of a new network block
ssid - hexdump_ascii(len=5):
     62 61 67 65 6c                                    bagel           
key_mgmt: 0x4
priority=5 (0x5)
Priority group 10
   id=0 ssid='leoair'
Priority group 5
   id=1 ssid='BTVOYAGER2091-A9'
   id=2 ssid='bagel'
Initializing interface (2) 'wpc11'
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)=20 WE(source)=14 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:06:25:2a:b2:54
wpa_driver_wext_set_wpa
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
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
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
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
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wpc11
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wpc11' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=16):
     42 54 56 4f 59 41 47 45 52 32 30 39 31 2d 41 39   BTVOYAGER2091-A9
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 578 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 10
0: 00:06:25:49:c4:05 ssid='leoair' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:06:25:ba:5d:29 ssid='UUTT' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:16:01:0d:16:e1 ssid='0016010D16E0' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:18:4d:04:3f:84 ssid='B&GAirNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:09:5b:f6:40:46 ssid='Netgear' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Selecting BSS from priority group 5
0: 00:06:25:49:c4:05 ssid='leoair' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:06:25:ba:5d:29 ssid='UUTT' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:16:01:0d:16:e1 ssid='0016010D16E0' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:18:4d:04:3f:84 ssid='B&GAirNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:09:5b:f6:40:46 ssid='Netgear' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b19 len=8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061221/1a41a5fd/attachment.pgp 


From dcbw  Wed Dec 20 19:01:27 2006
From: dcbw (Dan Williams)
Date: Wed, 20 Dec 2006 22:01:27 -0500
Subject: wpa_supplicant claims AP doesn't do WPA
In-Reply-To: <20061221005932.GD27285@cel.leo>
References: <20061221005932.GD27285@cel.leo>
Message-ID: <1166670087.23168.5.camel@localhost.localdomain>

On Thu, 2006-12-21 at 00:59 +0000, Paul LeoNerd Evans wrote:
> I have a Linksys WAP54G running version 3.04 of their firmware. It's set
> to WPA2-Personal, using AES with a preshared key. It is set to
> 802.11b-only, since I have slight issues from time to time with
> G-enabled cards.
> 
> My laptop is using a Linksys WPC11 wireless network card. This is an
> 802.11b card. It's running wpa_supplicant in debian's package, claiming
> 
> ii  wpasupplicant         0.5.5-4               Client support for WPA
> and WPA2 (IEEE 802.11i)
> 
> According to "iwlist scan" it therefore looks like:
> 
> wpc11     Scan completed :
>           Cell 01 - Address: 00:06:25:xx:xx:xx
>                     ESSID:"leoair"
>                     Mode:Master
>                     Frequency:2.417 GHz (Channel 2)
>                     Signal level:56/153  Noise level:13/153
>                     Encryption key:on
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
> 
> I can't seem to get wpa_supplicant to connect to it though. My config
> file for this AP looks like:
> 
> network={
>         ssid="leoair"
>         key_mgmt=WPA-PSK
>         psk="xxxxxxxx"
> 
>         priority=10
> }
> 
> Yet, when I run wpa_supplicant in foreground with "-d -d", it says:
> 
> ...
> Received 578 bytes of scan results (5 BSSes)
> Scan results: 5
> Selecting BSS from priority group 10
> 0: 00:06:25:49:c4:05 ssid='leoair' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> ...
> 
> No WPA IE? Maybe some item of config is missing here? At the AP's end,
> or the wpa_supp's end?

If your driver doesn't support returning the WPA IE in the scan results,
it's certainly not going to work with WPA and wpa_supplicant.  Smells
like a driver problem.

What driver are you using?  Does that driver really support WPA?  What
hardware version is your card?  Is it prism or prism2 based?  What
firmware version are you using?  Linksys has a long history of calling
something the same product name but switching out chipsets; you may not
have the card you think you do.

Do an lsmod and lets see what driver the kernel is binding to your card.
If you're using 'orinoco' drivers, they don't do WPA.  You might try
blacklisting the orinoco ones and using the 'hostap' driver instead.

Dan


> If it's any help, find attached the complete output from:
> 
> wpa_supplicant -iwpc11 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf
>   -d -d
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From re2823  Thu Dec 21 07:48:51 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Thu, 21 Dec 2006 15:48:51 +0000
Subject: ndiswrapper/wpa fails but rt2x00/wpa works with identical
	card/config
Message-ID: <N1-NC1SaOr0Vg@Safe-mail.net>

-------- Original Message --------
From: kemas henry <k_henry at ramayana.co.id>
To: re2823 at Safe-mail.net
Subject: Re: ndiswrapper/wpa fails but rt2x00/wpa works with identicalcard/config
Date: Thu, 21 Dec 2006 13:45:08 +0700

> I use wifi card rt2500 chipset with driver from ralink
> http://www.ralinktech.com/ralink/Home/Support/Linux.html
> but I can't use it to authenticate eap-tls with wpa_supplicant.
> so I use ndiswrapper-1.31 then it can authenticate eap-tls with
> wpa_supplicant.
> 
> just curious, you did install wpa_supplicant with config_ndiswrapper=y,
> right?
> maybe some conf file to be shared
> 
> forgive me, if it don't help much to you

No apologies necessary - all help is greatly appreciated!

Yes, wpa_supplicant is being built with the ndiswrapper driver
(CONFIG_DRIVER_NDISWRAPPER=y) although I do not use it because there
is a note in the debian package which says:

"Ndiswrapper NO LONGER SUPPORTS the 'ndiswrapper' driver backend as of
version 1.16. Therefore, 'wext' must be used unless you use an
antiquated ndiswrapper release."

You can find this text in here:
http://ftp.debian.org/debian/pool/main/w/wpasupplicant/wpasupplicant_0.5.5-2.diff.gz

So I normally use:
wpa_supplicant -w -d -Dwext -iwlan0 -c/etc/wpa.conf

I just need to get a few more debug logs ready and I will post some
more bug reports...

Jaime



From gregwillden  Thu Dec 21 09:31:37 2006
From: gregwillden (Greg Willden)
Date: Thu, 21 Dec 2006 11:31:37 -0600
Subject: ipw3945, Cisco LEAP
Message-ID: <903323ff0612210931ud23a09bg18aed97f7f91aa1d@mail.gmail.com>

Hi All,
I'm new to this list and wpa_supplicant.
I am trying to get my laptop's wireless working with my company's Cisco LEAP
APs.

I have ipw3945 with module version 1.0.5m
wpa_supplicant is v0.4.8
$ uname -a
Linux eiger 2.6.15-27-386 #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 i686
GNU/Linux

So far the following configuration seems to get the closest to working.
Although the auth_alg=LEAP doesn't seem to make any difference.

network={
ssid="ADSWireless"
scan_ssid=1
#key_mgmt=WPA-EAP
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=LEAP
priority=2
proto=WPA
identity="username"
password="password"
}

Here is a dump from wpa_supplicant.
Can you offer any suggestions?
Thanks
Greg


$ sudo wpa_supplicant -ieth1 -Dwext -c/etc/wpa_supplicant.conf -dd

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'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=11):
     41 44 53 57 69 72 65 6c 65 73 73                  ADSWireless
scan_ssid=1 (0x1)
key_mgmt: 0x8
auth_alg: 0x4
eap methods - hexdump(len=2): 11 00
priority=2 (0x2)
proto: 0x1
identity - hexdump_ascii(len=8):
     67 77 69 6c 6c 64 65 6e                           gwillden
password - hexdump_ascii(len=8): [REMOVED]
Priority group 2
   id=0 ssid='ADSWireless'
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)=19 WE(source)=16 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
Own MAC address: 00:13:02:b3:3f:d9
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 (specific SSID)
Scan SSID - hexdump_ascii(len=11):
     41 44 53 57 69 72 65 6c 65 73 73                  ADSWireless
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: SCANNING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=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
Scan timeout - try to get results
Received 768 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 2
0: 00:0d:8d:f0:0b:51 ssid='Weathervane' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
1: 00:40:96:a0:c0:80 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:0f:f7:66:4b:f0 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:14:bf:78:4b:b0 ssid='<hidden>' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
   selected non-WPA AP 00:40:96:a0:c0:80 ssid='ADSWireless'
Trying to associate with 00:40:96:a0:c0:80 (SSID='ADSWireless' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
Overriding auth_alg selection: 0x4
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_drop_unencrypted
State: DISCONNECTED -> ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
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 2
State: ASSOCIATING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=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 3
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 767 bytes of scan results (4 BSSes)
Scan results: 4
Selecting BSS from priority group 2
0: 00:0d:8d:f0:0b:51 ssid='Weathervane' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
1: 00:40:96:a0:c0:80 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:0f:f7:66:4b:f0 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:14:bf:78:4b:b0 ssid='<hidden>' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
   selected non-WPA AP 00:40:96:a0:c0:80 ssid='ADSWireless'
Trying to associate with 00:40:96:a0:c0:80 (SSID='ADSWireless' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
Overriding auth_alg selection: 0x4
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_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=20
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_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



-- 
Linux.  Because rebooting is for adding hardware.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061221/0b4a65c3/attachment.htm 


From Jens.Rutschmann  Thu Dec 21 11:02:34 2006
From: Jens.Rutschmann (Jens Rutschmann)
Date: Thu, 21 Dec 2006 20:02:34 +0100
Subject: WPA/WPA2 with Prism54 card
In-Reply-To: <1166660052.10335.5.camel@localhost.localdomain>
References: <4589B463.2040902@online.de>
	<1166660052.10335.5.camel@localhost.localdomain>
Message-ID: <458ADA4A.2070603@online.de>

Thanks for that fast answer !

I'll test the kernel 2.6.19.1 together with wpa_supplicants' wext driver
tomorrow or during the weekend and post the results then.
If the in-kernel driver doesn't work, I will try out that patch you
mentioned.

Regards,
Jens

> I believe that patch is already upstream.  Could you test it out?  I
> think it's in 2.6.19 and later kernels.
>
> There is also another patch floating around (in desperate need of
> testers) that completes the 'wext' support of the prism54 driver.  If
> the 'wext' bits of prism54 don't work with wpa_supplicant, we need to
> fix that.
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=116453812608332&w=2
>
> Dan
>   



From Jens.Rutschmann  Fri Dec 22 03:22:49 2006
From: Jens.Rutschmann (Jens Rutschmann)
Date: Fri, 22 Dec 2006 12:22:49 +0100
Subject: WPA/WPA2 with Prism54 card
In-Reply-To: <1166660052.10335.5.camel@localhost.localdomain>
References: <4589B463.2040902@online.de>
	<1166660052.10335.5.camel@localhost.localdomain>
Message-ID: <458BC009.4020306@online.de>

OK,
the first round wasn't that successful ...

I tested the kernel 2.6.19.1 today and when launching wpa_supplicant I
got the following:

root:~> wpa_supplicant -i eth1 -D wext -c
/etc/wpa_supplicant/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - CTRL-EVENT-TERMINATING - signal 2 received
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - root:~>


The program  was hanging after line 2 until I pressed CTRL-C which was
resulting in the rest of the output.

Then I tried that patch. I couldn't apply it though, it seems that it
doesn't match the driver in the latest kernel.

This it the patch output:

root:/usr/src/linux-2.6.19.1> cat
../patches/prism54-wpa-wl2.6-git-BOTH.diff | patch -p1
patching file drivers/net/wireless/prism54/isl_38xx.c
Hunk #1 succeeded at 25 (offset 1 line).
patching file drivers/net/wireless/prism54/isl_ioctl.c
Hunk #1 succeeded at 4 (offset 1 line).
Hunk #2 succeeded at 28 (offset 1 line).
Hunk #3 succeeded at 42 (offset 1 line).
Hunk #4 succeeded at 159 (offset 1 line).
Hunk #5 succeeded at 193 (offset 1 line).
Hunk #6 FAILED at 221.
Hunk #7 succeeded at 408 (offset 1 line).
Hunk #8 succeeded at 431 (offset 1 line).
Hunk #9 succeeded at 561 (offset 1 line).
Hunk #10 succeeded at 597 (offset 1 line).
Hunk #11 succeeded at 611 (offset 1 line).
Hunk #12 succeeded at 871 (offset 1 line).
Hunk #13 succeeded at 1039 (offset 1 line).
Hunk #14 succeeded at 1095 (offset 1 line).
Hunk #15 FAILED at 1132.
Hunk #16 FAILED at 1252.
Hunk #17 succeeded at 1286 (offset 1 line).
Hunk #18 succeeded at 1370 (offset 1 line).
Hunk #19 succeeded at 1385 (offset 1 line).
Hunk #20 succeeded at 1462 (offset 1 line).
Hunk #21 succeeded at 2044 (offset 1 line).
Hunk #22 succeeded at 2115 (offset 1 line).
Hunk #23 succeeded at 2146 (offset 1 line).
Hunk #24 succeeded at 2162 (offset 1 line).
Hunk #25 succeeded at 2225 (offset 1 line).
Hunk #26 succeeded at 2242 (offset 1 line).
Hunk #27 succeeded at 2276 (offset 1 line).
Hunk #28 FAILED at 2383.
Hunk #29 FAILED at 2424.
Hunk #30 succeeded at 2458 (offset 1 line).
Hunk #31 succeeded at 2595 (offset 1 line).
Hunk #32 succeeded at 2686 (offset 1 line).
Hunk #33 succeeded at 2716 (offset 1 line).
Hunk #34 succeeded at 2903 (offset 1 line).
5 out of 34 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/isl_ioctl.c.rej
patching file drivers/net/wireless/prism54/isl_ioctl.h
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file
drivers/net/wireless/prism54/isl_ioctl.h.rej
patching file drivers/net/wireless/prism54/isl_oid.h
Hunk #1 succeeded at 4 (offset 2 lines).
Hunk #2 succeeded at 29 (offset 2 lines).
Hunk #3 succeeded at 100 (offset 2 lines).
Hunk #4 FAILED at 131.
Hunk #5 FAILED at 172.
Hunk #6 succeeded at 198 with fuzz 1 (offset 2 lines).
Hunk #7 succeeded at 512 (offset 2 lines).
Hunk #8 succeeded at 545 (offset 2 lines).
2 out of 8 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/isl_oid.h.rej
patching file drivers/net/wireless/prism54/islpci_dev.c
Hunk #1 succeeded at 26 (offset 1 line).
Hunk #2 succeeded at 87 (offset 1 line).
patching file drivers/net/wireless/prism54/islpci_dev.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_dev.h.rej
patching file drivers/net/wireless/prism54/islpci_eth.c
Hunk #1 succeeded at 25 (offset 1 line).
Hunk #2 FAILED at 482.
Hunk #3 FAILED at 499.
2 out of 3 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_eth.c.rej
patching file drivers/net/wireless/prism54/islpci_hotplug.c
Hunk #1 succeeded at 24 (offset 1 line).
Hunk #2 succeeded at 44 (offset 1 line).
Hunk #3 FAILED at 150.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 235.
Hunk #6 FAILED at 268.
4 out of 6 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_hotplug.c.rej
patching file drivers/net/wireless/prism54/islpci_mgt.c
Hunk #1 succeeded at 26 (offset 1 line).
patching file drivers/net/wireless/prism54/oid_mgt.c
patching file drivers/net/wireless/prism54/oid_mgt.h
patching file drivers/net/wireless/prism54/prismcompat.h
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file
drivers/net/wireless/prism54/prismcompat.h.rej


This is my wpa_supplicant.conf:

update_config=0
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
fast_reauth=1


network={
    ssid="rutschnet"
    psk="<secret_hey_here>"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=TKIP
    group=TKIP
}


Did you modify the in-kernel driver in a complete way so that it
supports wext without that additional patch ? Or do I need it anyway ?

Thanks,
Jens



Dan Williams schrieb:
> On Wed, 2006-12-20 at 23:08 +0100, Jens Rutschmann wrote:
>   
>> Hello,
>> in my Notebook I have a miniPCI card with Intersil Prism54 chipset.
>> Currently I am forced to use WEP encryption on my wireless network
>> because wpa_supplicant doesn't support the card right now.
>>
>> Is there any chance that wpa_supplicants' prism54 driver will be
>> completed in the near future ?
>>     
>
> 'wext' is the future (and cfg80211 after that), so card-specific
> interfaces shouldn't be used if at all possible.
>
> I ported the WPA support of the prism54 driver to the 'wext'
> wpa_supplicant driver a while ago.  It should be able to exist alongside
> the prism54-specific ioctls for WPA.  I was not able to extensively test
> it, however, because my card died halfway through.
>
> I believe that patch is already upstream.  Could you test it out?  I
> think it's in 2.6.19 and later kernels.
>
> There is also another patch floating around (in desperate need of
> testers) that completes the 'wext' support of the prism54 driver.  If
> the 'wext' bits of prism54 don't work with wpa_supplicant, we need to
> fix that.
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=116453812608332&w=2
>
> Dan
>
>   
>> I read in the mailing list that several components need to support WPA
>> to get it running:
>> The hardware: specifications of my chipset say that it supports  "AES
>> hardware acceleration"
>> The driver: I use the in-kernel driver (kernel 2.6.18)
>> And finally wpa_supplicant itself: I guess that concerns
>> wpa_supplicants' prism54 driver.
>>
>> Can I even get this running if wpa_supplicants' driver would support it ?
>> Or would it be better to buy a new card with Atheros or Intel chipset?
>>
>> Regards,
>> Jens Rutschmann
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>     
>
>   



From jbarnett  Fri Dec 22 08:48:45 2006
From: jbarnett (jbarnett at coleinnovations.com)
Date: Fri, 22 Dec 2006 11:48:45 -0500 (EST)
Subject: HostAP request code number?
Message-ID: <2556.128.132.176.181.1166806125.squirrel@www.coleinnovations.com>

Hi,
Sorry guys buy I am having a hard time finding what the hostAP request
code is, for an ioctl call.

~Jimmie



From tl2a.ch  Fri Dec 22 09:31:00 2006
From: tl2a.ch (Ta-Chien Lin)
Date: Fri, 22 Dec 2006 09:31:00 -0800
Subject: hostapd handling .1x and reassoc
Message-ID: <e3c3c3bd0612220931p216060ceic16562830d505ec4@mail.gmail.com>

When hostapd is running in 802.1x mode and an associated client (AP's
perspective) sends ASSOC or RE-ASSOC, both are treated as RE-ASSOC by
hostapd. With syslog logging level set to 0, the event sequence is as the
following:

daemon.info hostapd: wlan0: STA 00:12:f0:5b:95:2a IEEE 802.11: associated
daemon.debug hostapd: wlan0: STA 00:12:f0:5b:95:2a WPA: event 1 notification
daemon.debug hostapd: wlan0: STA 00:12:f0:5b:95:2a WPA: event 4 notification

At this point, if the AP does not receive EAPOL-Start from the client (event
5 notification), for any reason, the connection remains "authorized" but
there is no longer any KEY.

In a real assoc event, hostapd will take the data path to immediately begin
.1X authentication, so the connection can move along, whether STA sends
EAPOL-Start or not.

It would be good if on a "re-assoc" event, hostapd does the same thing,
without waiting for STA's EAPOL-Start to show up.

This can be accomplished by adding "sta->eapol_sm->reAuthenticate = TRUE;"
in the function ieee802_1x_new_station, in the else clause of "if
(sta->pmksa)", just before stepping through the eapol state machine.

-Ta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061222/9c9e2e2d/attachment.htm 


From dcbw  Sat Dec 23 12:45:29 2006
From: dcbw (Dan Williams)
Date: Sat, 23 Dec 2006 15:45:29 -0500
Subject: ipw3945, Cisco LEAP
In-Reply-To: <903323ff0612210931ud23a09bg18aed97f7f91aa1d@mail.gmail.com>
References: <903323ff0612210931ud23a09bg18aed97f7f91aa1d@mail.gmail.com>
Message-ID: <1166906729.2867.4.camel@localhost.localdomain>

On Thu, 2006-12-21 at 11:31 -0600, Greg Willden wrote:
> Hi All,
> I'm new to this list and wpa_supplicant.
> I am trying to get my laptop's wireless working with my company's
> Cisco LEAP APs.
> 
> I have ipw3945 with module version 1.0.5m
> wpa_supplicant is v0.4.8 
> $ uname -a
> Linux eiger 2.6.15-27-386 #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 i686
> GNU/Linux
> 
> So far the following configuration seems to get the closest to
> working.  Although the auth_alg=LEAP doesn't seem to make any
> difference. 
> 
> network={
> ssid="ADSWireless"
> scan_ssid=1
> #key_mgmt=WPA-EAP
> key_mgmt=IEEE8021X
> auth_alg=LEAP
> eap=LEAP
> priority=2
> proto=WPA
> identity="username"
> password="password" 
> }
> 
> Here is a dump from wpa_supplicant.

The driver itself is not actually associating with the access point, so
you never even get to the LEAP part.  You could try a few things:

1) just try to associate manually with 'iwconfig'.  Obviously you need
wpa_supplicant to do the LEAP stuff, but since you have to associate
first before you can start the LEAP exchanges, the driver should be
sending the associate event.  But it's not; and therefore wpa_supplicant
isn't able to start the LEAP exchange.  So anyway, run 'iwevent' in one
window, and do your iwconfig stuff in another, and see if you get an
SIWAP event that's not 0s.

2) Enable debug information in the ipw3945 driver, and get a dump of
what the _driver_ thinks its doing.  This is clearly a misconfiguration
problem between the driver and wpa_supplicant, but your config seems to
be the standard LEAP config, I -think-.

3) what happens if you take 'proto=WPA' out completely?

Dan

> Can you offer any suggestions?
> Thanks
> Greg
> 
> 
> $ sudo wpa_supplicant -ieth1 -Dwext -c/etc/wpa_supplicant.conf -dd
> 
> 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'
> Line: 1 - start of a new network block
> ssid - hexdump_ascii(len=11): 
>      41 44 53 57 69 72 65 6c 65 73 73                  ADSWireless
> scan_ssid=1 (0x1)
> key_mgmt: 0x8
> auth_alg: 0x4
> eap methods - hexdump(len=2): 11 00
> priority=2 (0x2)
> proto: 0x1
> identity - hexdump_ascii(len=8): 
>      67 77 69 6c 6c 64 65 6e                           gwillden
> password - hexdump_ascii(len=8): [REMOVED]
> Priority group 2
>    id=0 ssid='ADSWireless'
> 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)=19 WE(source)=16 enc_capa=0xf
>   capabilities: key_mgmt 0xf enc 0xf
> Own MAC address: 00:13:02:b3:3f:d9
> 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 (specific SSID)
> Scan SSID - hexdump_ascii(len=11):
>      41 44 53 57 69 72 65 6c 65 73 73                  ADSWireless 
> 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: SCANNING -> DISCONNECTED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=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
> Scan timeout - try to get results
> Received 768 bytes of scan results (4 BSSes) 
> Scan results: 4
> Selecting BSS from priority group 2
> 0: 00:0d:8d:f0:0b:51 ssid='Weathervane' wpa_ie_len=26 rsn_ie_len=0
> caps=0x11
>    skip - SSID mismatch
> 1: 00:40:96:a0:c0:80 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11 
>    skip - no WPA/RSN IE
> 2: 00:0f:f7:66:4b:f0 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11
>    skip - no WPA/RSN IE
> 3: 00:14:bf:78:4b:b0 ssid='<hidden>' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11 
>    skip - no WPA/RSN IE
>    selected non-WPA AP 00:40:96:a0:c0:80 ssid='ADSWireless'
> Trying to associate with 00:40:96:a0:c0:80 (SSID='ADSWireless' freq=0
> MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE 
> Automatic auth_alg selection: 0x4
> Overriding auth_alg selection: 0x4
> 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_drop_unencrypted 
> State: DISCONNECTED -> ASSOCIATING
> wpa_driver_wext_associate
> Setting authentication timeout: 10 sec 0 usec
> 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 2
> State: ASSOCIATING -> DISCONNECTED
> EAPOL: External notification - portEnabled=0 
> EAPOL: External notification - portValid=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 3
> 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 767 bytes of scan results (4 BSSes) 
> Scan results: 4
> Selecting BSS from priority group 2
> 0: 00:0d:8d:f0:0b:51 ssid='Weathervane' wpa_ie_len=26 rsn_ie_len=0
> caps=0x11
>    skip - SSID mismatch
> 1: 00:40:96:a0:c0:80 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11 
>    skip - no WPA/RSN IE
> 2: 00:0f:f7:66:4b:f0 ssid='ADSWireless' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11
>    skip - no WPA/RSN IE
> 3: 00:14:bf:78:4b:b0 ssid='<hidden>' wpa_ie_len=0 rsn_ie_len=0
> caps=0x11 
>    skip - no WPA/RSN IE
>    selected non-WPA AP 00:40:96:a0:c0:80 ssid='ADSWireless'
> Trying to associate with 00:40:96:a0:c0:80 (SSID='ADSWireless' freq=0
> MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE 
> Automatic auth_alg selection: 0x4
> Overriding auth_alg selection: 0x4
> 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_drop_unencrypted 
> State: SCANNING -> ASSOCIATING
> wpa_driver_wext_associate
> Setting authentication timeout: 10 sec 0 usec
> EAPOL: External notification - portControl=Auto
> Wireless event: cmd=0x8b06 len=8
> Wireless event: cmd=0x8b1a len=20 
> CTRL-EVENT-TERMINATING - signal 2 received
> Removing interface eth1
> State: ASSOCIATING -> DISCONNECTED
> No keys have been configured - skip key clearing
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0 
> wpa_driver_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 
> 
> 
> 
> -- 
> Linux.  Because rebooting is for adding hardware. 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From jkmaline  Sat Dec 23 19:13:17 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 23 Dec 2006 19:13:17 -0800
Subject: No networks enabled - do not scan
In-Reply-To: <1166553150.21065.1.camel@localhost.localdomain>
References: <1166481757.11190.10.camel@localhost.localdomain>
	<1166553150.21065.1.camel@localhost.localdomain>
Message-ID: <20061224031317.GA7017@jm.kir.nu>

On Tue, Dec 19, 2006 at 01:32:29PM -0500, Dan Williams wrote:
> On Mon, 2006-12-18 at 17:42 -0500, Dan Williams wrote:
> > This particular hunk [1] in wpa_supplicant presents a problem for
> > NetworkManager... First, NM must ask for scan results before it can tell
> > wpa_supplicant which network to use, of course, but wpa_supplicant
> > doesn't scan until it's told which network to use.  We lose.

This should be fine.. wpa_supplicant scans if requested to with SCAN
ctrl_iface command.

> > This appears to work on the first scan request, because wpa_supplicant
> > does an initial scan automatically.  But thereafter, it does not scan
> > unless there's a configured network.  I understand why this is desirable
> > for standalone wpa_supplicant, but it certainly won't work with
> > NetworkManager.

Not scanning unless requested to is indeed a desired feature.

> So my assertion here may be somewhat wrong.  I see that
> 
> 	if (!enabled && !wpa_s->scan_req) {
> 
> should only suppress the scan if scan_req is 0.  Both the regular
> control interface and the dbus control interface set scan_req to 2 when
> they request a scan.

Yes and that is there to allow explicit scan requests even if automatic
scans are disabled. I have not tested this with dbus, but this works
fine with an interface that is added with wpa_cli through the global
ctrl_iface.

> I also have now found out that wpa_supplicant is attempting to scan on
> the wired interface too, which is quite odd, and is the real source of
> this error message.  More investigation necessary to determine whether
> the error is in wpa_supplicant or in my usage of it.

Were you trying to add a wired interface? wpa_supplicant does not do
much internally with the knowledge of interface being wired.. As such,
requests to scan do indeed go through to the driver interface. Since
driver_wired is expected to be used with ap_scan=0, this is not much of
an issue since wpa_supplicant does not automatically requests scans in
this mode. If something external is trying to scan through ctrl_iface,
those will go through to the driver wrapper, but that will just fail in
the wired case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From re2823  Sat Dec 23 20:26:18 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Sun, 24 Dec 2006 04:26:18 +0000
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
Message-ID: <N1-pt7KUPWAuS@Safe-mail.net>

Hi.

I cannot get my dwl-650p working on Debian Etch ("modprobe hostap_cs"
does not create an extra interface), and I think that this might be due
to a possible error in the manfid for my card. "pccardctl ident"
returns:

Socket 0:
  product info: "D-Link", "DWL-650 Wireless PC Card RevP", "ISL37101P-10", "A3"
  manfid: 0x000b, 0x7110
  function: 6 (network)

To find out if my card is supported in linux, I read the source code in
the linux-2.6.19.1 kernel that I download from www.kernel.org. The ids
in linux-2.6.19.1/drivers/net/wireless/hostap/hostap_plx.c start:

        { 0x000b, 0x7110 } /* D-Link DWL-650 Rev. P1 */,
        { 0x000b, 0x7300 } /* Philips 802.11b WLAN PCMCIA */,
        { 0x0101, 0x0777 } /* 3Com AirConnect PCI 777A */,
        { 0x0126, 0x8000 } /* Proxim RangeLAN */,
        { 0x0138, 0x0002 } /* Compaq WL100 */,

while the ids in linux-2.6.19.1/drivers/net/wireless/hostap/hostap_cs.c
start:

        PCMCIA_DEVICE_MANF_CARD(0x000b, 0x7100),
        PCMCIA_DEVICE_MANF_CARD(0x000b, 0x7300),
        PCMCIA_DEVICE_MANF_CARD(0x0101, 0x0777),
        PCMCIA_DEVICE_MANF_CARD(0x0126, 0x8000),
        PCMCIA_DEVICE_MANF_CARD(0x0138, 0x0002),

Then I notice that these two lists are identical except for the first
entry, which is my card! I also think that the dwl-650p is supported
because of previous posts to this mailing list, such as:

http://thread.gmane.org/gmane.linux.drivers.hostap/7384/focus=7442

Could this problem be the reason why "modprobe hostap_cs" does not
create an extra interface?

Jaime



From jar  Sun Dec 24 02:06:38 2006
From: jar (Jar)
Date: Sun, 24 Dec 2006 12:06:38 +0200
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
In-Reply-To: <N1-pt7KUPWAuS@Safe-mail.net>
References: <N1-pt7KUPWAuS@Safe-mail.net>
Message-ID: <458E512E.100@pcuf.fi>

re2823 at Safe-mail.net wrote:

Have you started your pcmcia socket driver? Can you paster you dmesg 
right after boot.

You should not need to modprobe anything. Pcmciautils package should be 
installed. Udev should load the module and bring the interface up 
automatically.

-- 
Best Regards, Jar



From re2823  Sun Dec 24 03:36:41 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Sun, 24 Dec 2006 11:36:41 +0000
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
Message-ID: <N1-0RzhbaJ_0i@Safe-mail.net>

> Have you started your pcmcia socket driver? Can you paster you dmesg 
> right after boot.

I _think_ the pcmcia socket driver is started, as I can see Yenta
entries in the dmesg output (please excuse me, I don't understand
much about pcmcia/cardbus, other than knowing that this is a 16-bit
pcmcia (isa?) card. The machine/os is just a standard Debian Etch
install on a Thinkpad T21. Here's the dmesg:

# dmesg
Linux version 2.6.18-3-686 (Debian 2.6.18-7) (waldi at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 16:41:14 UTC 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
 BIOS-e820: 000000001fff0000 - 000000001fffec00 (ACPI data)
 BIOS-e820: 000000001fffec00 - 0000000020000000 (ACPI NVS)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
On node 0 totalpages: 131056
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 126960 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 PTLTD                                 ) @ 0x000f7120
ACPI: RSDT (v001 PTLTD    RSDT   0x06041160  LTP 0x00000000) @ 0x1fff4c5d
ACPI: FADT (v001 IBM    TP-T21   0x06041160  0x00000000) @ 0x1fffeb65
ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06041160  LTP 0x00000001) @ 0x1fffebd9
ACPI: DSDT (v001 IBM    TP-T21   0x06041160 MSFT 0x0100000c) @ 0x00000000
ACPI: PM-Timer IO Port: 0x1008
Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000)
Detected 697.041 MHz processor.
Built 1 zonelists.  Total pages: 131056
Kernel command line: root=/dev/hda5 ro vga=0x33c console=ttyS0,115200 console=tty0
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (0140a000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512056k/524224k available (1543k kernel code, 11564k reserved, 574k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1395.06 BogoMIPS (lpj=2790125)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0800)
CPU0: Intel Pentium III (Coppermine) stepping 06
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4388k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd94f, last bus=7
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 1000-103f claimed by PIIX4 ACPI
PCI quirk: region 1040-104f claimed by PIIX4 SMB
PIIX4 devres C PIO at 15e8-15ef
PIIX4 devres I PIO at 03f0-03f7
PIIX4 devres J PIO at 002e-002f
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: Power Resource [PSER] (on)
ACPI: Power Resource [PSIO] (on)
ACPI: Embedded Controller [EC] (gpe 9) interrupt mode.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 15 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:02: ioport range 0x1000-0x103f could not be reserved
pnp: 00:02: ioport range 0x1040-0x104f has been reserved
pnp: 00:02: ioport range 0xfe00-0xfe0f has been reserved
pnp: 00:09: ioport range 0x15e0-0x15ef has been reserved
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: f0000000-f7ffffff
  PREFETCH window: 38000000-380fffff
PCI: Bus 2, cardbus bridge: 0000:00:02.0
  IO window: 00001400-000014ff
  IO window: 00001800-000018ff
  PREFETCH window: 30000000-31ffffff
  MEM window: 32000000-33ffffff
PCI: Bus 6, cardbus bridge: 0000:00:02.1
  IO window: 00002400-000024ff
  IO window: 00002800-000028ff
  PREFETCH window: 34000000-35ffffff
  MEM window: 36000000-37ffffff
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Simple Boot Flag at 0x35 set to 0x1
audit: initializing netlink socket (disabled)
audit(1166951974.720:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Limiting direct PCI/PCI transfers.
vesafb: framebuffer at 0xf0000000, mapped to 0xe0880000, using 5742k, total 8192k
vesafb: mode is 1400x1050x16, linelength=2800, pages=1
vesafb: protected mode interface info at c000:882d
vesafb: pmi: set display start = c00c888d, set palette = c00c88d6
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 175x65
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
ACPI: (supports S0<6>Time: tsc clocksource has been installed.
 S1 S3 S4 S5)
Freeing unused kernel memory: 196k freed
input: AT Translated Set 2 keyboard as /class/input/input0
ACPI: Processor [CPU] (supports 8 throttling states)
ACPI: Thermal Zone [THM0] (30 C)
PCI: Enabling device 0000:00:03.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:03.0: 3Com PCI 3c556B Laptop Hurricane at e0826000.
PCI: Setting latency timer of device 0000:00:03.0 to 64
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1c00-0x1c07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1c08-0x1c0f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
hda: IBM-DJSA-232, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: MATSHITADVD-ROM SR-8175, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 11, io base 0x00001c20
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hda: max request size: 128KiB
hda: 62506080 sectors (32003 MB) w/1874KiB Cache, CHS=65535/15/63, UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Attempting manual resume
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Yenta: CardBus bridge found at 0000:00:02.0 [1014:0130]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0x00001000, devctl 0x66
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000010
Yenta: CardBus bridge found at 0000:00:02.1 [1014:0130]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0x00001000, devctl 0x66
Linux agpgart interface v0.101 (c) Dave Jones
input: PC Speaker as /class/input/input1
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000006
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xf8000000
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!
piix4_smbus: probe of 0000:00:07.3 failed with error -1
ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
pccard: PCMCIA card inserted into slot 0
gameport: CS46xx Gameport is pci0000:00:05.0/gameport0, speed 1807kHz
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Unable to reserve mem region #1:8000000 at f0000000 for device 0000:01:00.0
cannot request PCI regions
savagefb: probe of 0000:01:00.0 failed with error -16
input: ImPS/2 Logitech Wheel Mouse as /class/input/input2
irda_init()
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
ts: Compaq touchscreen protocol output
pnp: Device 00:0e activated.
nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 1.
nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Found dongle: Sharp RY5HD01
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
Adding 982760k swap on /dev/hda7.  Priority:-1 extents:1 across:982760k
EXT3 FS on hda5, internal journal
loop: loaded (max 8 devices)
ndiswrapper version 1.32rc2 loaded (preempt=no,smp=yes)
usbcore: registered new driver ndiswrapper
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel at redhat.com
ACPI: Battery Slot [BAT0] (battery absent)
ACPI: AC Adapter [AC] (on-line)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Sleep Button (CM) [SLPB]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0:  setting full-duplex.
eth0: no IPv6 routers present

> 
> You should not need to modprobe anything. Pcmciautils package should be 
> installed. Udev should load the module and bring the interface up 
> automatically.

Cool - in that case, something is definitely broken :)

I'm using the standard 686 debian kernel (linux-image-2.6.18-3-686 version
2.6.18-7) and I do have pcmciautils installed (version 014-3). I also note
that pcmcia-cs (version 3.2.8-9) is installed as standard, but the
description for the package says that it's deprecated (I don't know if this
could be causing problems).

"pccardctl ident" returns:
Socket 0:
  product info: "D-Link", "DWL-650 Wireless PC Card RevP", "ISL37101P-10", "A3"
  manfid: 0x000b, 0x7110
  function: 6 (network)
Socket 1:
  no product info available

Removing/plugging the card adds the following lines to /var/sys/syslog:

Dec 24 11:26:56 t21jt kernel: pccard: card ejected from slot 0
Dec 24 11:27:06 t21jt kernel: pccard: PCMCIA card inserted into slot 0
Dec 24 11:27:06 t21jt kernel: pcmcia: registering new device pcmcia0.0


After reading http://article.gmane.org/gmane.linux.drivers.hostap/7384
I also added the following to /etc/pcmcia/hostap_cs.conf:

card "Dlink Weird Card"
  manfid 0x000b, 0x7110
  bind "hostap_cs"

(This might be a mistake). Finally, currently loaded modules are:

lsmod | sort
3c59x                  40360  0
ac                      5188  0
agpgart                29896  1 intel_agp
battery                 9636  0
button                  6672  0
cdrom                  32544  1 ide_cd
crc_ccitt               2240  1 irda
dm_mirror              19152  0
dm_mod                 50232  2 dm_snapshot,dm_mirror
dm_snapshot            15520  0
evdev                   9088  1
ext3                  119208  1
fan                     4804  0
firmware_class          9600  1 pcmcia
gameport               14632  2 snd_cs46xx
generic                 5028  0 [permanent]
i2c_algo_bit            8424  1 savagefb
i2c_core               19680  3 savagefb,i2c_algo_bit,i2c_piix4
i2c_piix4               8140  0
ide_cd                 36064  0
ide_core              110504  4 ide_cd,ide_disk,piix,generic
ide_disk               14848  3
intel_agp              21148  1
ipv6                  226016  10
irda                  162588  1 nsc_ircc
jbd                    52456  1 ext3
loop                   15048  0
mbcache                 8356  1 ext3
mii                     5344  1 3c59x
Module                  Size  Used by
ndiswrapper           158996  0
nsc_ircc               20912  0
parport                33256  1 parport_pc
parport_pc             32164  0
pci_hotplug            28704  1 shpchp
pcmcia                 34108  0
pcmcia_core            36852  3 pcmcia,yenta_socket,rsrc_nonstatic
pcspkr                  3072  0
piix                    9444  0 [permanent]
processor              28840  1 thermal
psmouse                35016  0
rsrc_nonstatic         11840  1 yenta_socket
savagefb               26276  0
serio_raw               6660  0
shpchp                 33024  0
snd                    47012  6 snd_cs46xx,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer
snd_ac97_bus            2400  1 snd_ac97_codec
snd_ac97_codec         83104  1 snd_cs46xx
snd_cs46xx             76360  0
snd_page_alloc          9640  2 snd_cs46xx,snd_pcm
snd_pcm                68644  2 snd_cs46xx,snd_ac97_codec
snd_rawmidi            22560  1 snd_cs46xx
snd_seq_device          7820  1 snd_rawmidi
snd_timer              20996  1 snd_pcm
soundcore               9248  1 snd
thermal                13608  0
tsdev                   7520  0
uhci_hcd               21032  0
usbcore               112676  3 ndiswrapper,uhci_hcd
yenta_socket           24460  4

and "ifconfig -a" returns:
eth0      Link encap:Ethernet  HWaddr 00:00:86:4B:62:EA
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::200:86ff:fe4b:62ea/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9527 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9610 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7213540 (6.8 MiB)  TX bytes:1384311 (1.3 MiB)
          Interrupt:11 Base address:0x6000

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

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


If there's anything else I can do to help
(including a fresh install), please let me know.

Thank you (and Happy Xmas!)



From jar  Sun Dec 24 04:07:24 2006
From: jar (Jar)
Date: Sun, 24 Dec 2006 14:07:24 +0200
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
In-Reply-To: <N1-0RzhbaJ_0i@Safe-mail.net>
References: <N1-0RzhbaJ_0i@Safe-mail.net>
Message-ID: <458E6D7C.1030003@pcuf.fi>

re2823 at Safe-mail.net wrote:
> I _think_ the pcmcia socket driver is started, as I can see Yenta
> entries in the dmesg output 

Yes it seems so.

> "pccardctl ident" returns:
> Socket 0:
>   product info: "D-Link", "DWL-650 Wireless PC Card RevP", "ISL37101P-10", "A3"
>   manfid: 0x000b, 0x7110
>   function: 6 (network)
> Socket 1:
>   no product info available

Could it be that you card lacks the firmware image in its flash memory 
and it should be loaded when the card is initialized? See:

"config HOSTAP_FIRMWARE
         bool "Support downloading firmware images with Host AP driver"
         depends on HOSTAP
         ---help---
         Configure Host AP driver to include support for firmware image
         download. This option by itself only enables downloading to the
         volatile memory, i.e. the card RAM. This option is required to
         support cards that don't have firmware in flash, such as D-Link
         DWL-520 rev E and D-Link DWL-650 rev P.

         Firmware image downloading needs a user space tool, prism2_srec.
         It is available from http://hostap.epitest.fi/.
"

I don't know if the firmware can be loaded via kernel firmware 
downloading system by just copy the correct firmware images to 
/lib/firmware or equivalent directory. Or is the prism2_srec tool really 
needed.

You can try with pm010102.hex and rf010704.hex firmware files from 
http://linux.junsun.net/intersil-prism/firmware/1.7.4/

See also:

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

and

http://lists.infradead.org/pipermail/linux-pcmcia/2005-July/002253.html


> After reading http://article.gmane.org/gmane.linux.drivers.hostap/7384
> I also added the following to /etc/pcmcia/hostap_cs.conf:
> 
> card "Dlink Weird Card"
>   manfid 0x000b, 0x7110
>   bind "hostap_cs"

The old system (pcmcia-cs) reads the hostap_cs.conf file, but not the 
new system (pcmciautils). The same info is build inside the hostap_cs 
module itself. I think the old and new system can't coexist simultaneously.


-- 
Best Regards, Jar



From re2823  Sun Dec 24 04:54:44 2006
From: re2823 (re2823 at Safe-mail.net)
Date: Sun, 24 Dec 2006 12:54:44 +0000
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
Message-ID: <N1-s47lYgjf62@Safe-mail.net>

-------- Original Message --------
From: Jar <jar at pcuf.fi>
> Could it be that you card lacks the firmware image in its flash memory 
> and it should be loaded when the card is initialized? See:
> 
> "config HOSTAP_FIRMWARE
>          bool "Support downloading firmware images with Host AP driver"
>          depends on HOSTAP
>          ---help---
>          Configure Host AP driver to include support for firmware image
>          download. This option by itself only enables downloading to the
>          volatile memory, i.e. the card RAM. This option is required to
>          support cards that don't have firmware in flash, such as D-Link
>          DWL-520 rev E and D-Link DWL-650 rev P.
> 
>          Firmware image downloading needs a user space tool, prism2_srec.
>          It is available from http://hostap.epitest.fi/.
> "
> 
> I don't know if the firmware can be loaded via kernel firmware 
> downloading system by just copy the correct firmware images to 
> /lib/firmware or equivalent directory. Or is the prism2_srec tool really 
> needed.
> 
> You can try with pm010102.hex and rf010704.hex firmware files from 
> http://linux.junsun.net/intersil-prism/firmware/1.7.4/

Only one problem - all the documentation talks about invoking the firmware
loader with a particular interface name:

In hostap-utils/README:
Usage:
  prism2_srec [-vvrgfdpisD] [-P <PDA file>] [-O <PDA binary>] <interface> \
              <srec file name> [srec file name]

Also, in hostap-utils/hostap-fw-load:
IFNAME=$1
DIR=/proc/net/hostap/$IFNAME

The latter makes me think that there should be something in my
/proc/net/hostap but this is empty :(

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

This also talks about a wlan0, which I don't have...

> and
> 
> http://lists.infradead.org/pipermail/linux-pcmcia/2005-July/002253.html

Yes, this person has exactly the same problem as me (no wlan0)

> > After reading http://article.gmane.org/gmane.linux.drivers.hostap/7384
> > I also added the following to /etc/pcmcia/hostap_cs.conf:
> > 
> > card "Dlink Weird Card"
> >   manfid 0x000b, 0x7110
> >   bind "hostap_cs"
> 
> The old system (pcmcia-cs) reads the hostap_cs.conf file, but not the 
> new system (pcmciautils). The same info is build inside the hostap_cs 
> module itself. I think the old and new system can't coexist simultaneously.

I'll try a fresh debian (etch) and see what's installed by default.

Jaime



From jkmaline  Sun Dec 24 07:53:05 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 07:53:05 -0800
Subject: ipw3945, Cisco LEAP
In-Reply-To: <903323ff0612210931ud23a09bg18aed97f7f91aa1d@mail.gmail.com>
References: <903323ff0612210931ud23a09bg18aed97f7f91aa1d@mail.gmail.com>
Message-ID: <20061224155305.GA6618@jm.kir.nu>

On Thu, Dec 21, 2006 at 11:31:37AM -0600, Greg Willden wrote:

> I am trying to get my laptop's wireless working with my company's Cisco LEAP
> APs.
> 
> I have ipw3945 with module version 1.0.5m

> So far the following configuration seems to get the closest to working.
> Although the auth_alg=LEAP doesn't seem to make any difference.

Do you know whether the APs have been configured to require "Network
EAP" for IEEE 802.11 authentication or not? If yes, it is possible that
ipw3945 driver does not support this and that would prevent association
with the AP. At least based on a quick look at ipw3945.c from v1.1.3,
only Open System and Shared Key authentication algorithms are listed and
that would seem to indicate that auth_alg=LEAP in wpa_supplicant would
not be supported.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 07:57:23 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 07:57:23 -0800
Subject: WPA/WPA2 with Prism54 card
In-Reply-To: <458BC009.4020306@online.de>
References: <4589B463.2040902@online.de>
	<1166660052.10335.5.camel@localhost.localdomain>
	<458BC009.4020306@online.de>
Message-ID: <20061224155723.GB6618@jm.kir.nu>

On Fri, Dec 22, 2006 at 12:22:49PM +0100, Jens Rutschmann wrote:

> I tested the kernel 2.6.19.1 today and when launching wpa_supplicant I
> got the following:
> 
> root:~> wpa_supplicant -i eth1 -D wext -c
> /etc/wpa_supplicant/wpa_supplicant.conf
> ioctl[SIOCSIWAUTH]: Operation not supported
> WEXT auth param 4 value 0x0 - CTRL-EVENT-TERMINATING - signal 2 received

> The program  was hanging after line 2 until I pressed CTRL-C which was
> resulting in the rest of the output.

Could you please re-run this with full debugging output from
wpa_supplicant (-dd on command line)? Prism54 driver did not use to
support WPA in client mode, but there has been some comments on that
working with some changes. I have not tested this myself nor have I
heard many clear success reports, so I don't know what exactly the
current status of the WPA support in the driver is.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:11:11 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:11:11 -0800
Subject: ndiswrapper/wpa fails but rt2x00/wpa works with identical
	card/config
In-Reply-To: <N1-T3_MQmZhWh@Safe-mail.net>
References: <N1-T3_MQmZhWh@Safe-mail.net>
Message-ID: <20061224161046.GC6618@jm.kir.nu>

On Wed, Dec 20, 2006 at 03:17:37AM +0000, re2823 at Safe-mail.net wrote:

> I have an rt2561-based pci wireless card that I'm trying to use with
> wpa_supplicant. When I use the rt2x00 drivers, wpa_supplicant connects
> successfully, but because the drivers are still alpha, the speed is very
> bad. When I use ndiswrapper, wpa_supplicant fails to connect at all.
> Since I am using the same /etc/wpa_supplicant.conf and the same command
> line ("wpa_supplicant -w -d -Dwext -iwlan0 -c/etc/wpa.conf") both times,
> I assume that the problem is something to do with ndiswrapper (I could
> be wrong).

> http://www.carbon.eclipse.co.uk/wpa/rt2x00Success
> http://www.carbon.eclipse.co.uk/wpa/ndiswrapperFail

Both of these look a bit odd.. It looks like there are major problems
getting anything through to the AP in time. Could you please run a test
with timestamps enabled in the debug log (-t added to the wpa_supplicant
command line)? If you have possibility of running a wireless sniffer to
capture the frames between the AP and the client, that could also
provide useful data on the problem.

WPA 4-way handshake has relatively small timeouts on the messages and it
looks like the AP is either not receiving the response from the client
at all or the response is coming too late.

How fast is the system on which you are running wpa_supplicant? Is the
debug output written to a file (> file)? Have you tested with debugging
disabled?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:15:04 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:15:04 -0800
Subject: wpa_supplicant in ad-hoc mode
In-Reply-To: <D501FD3C-A082-4921-8E94-1CC60AEF6226@ccom.unh.edu>
References: <D501FD3C-A082-4921-8E94-1CC60AEF6226@ccom.unh.edu>
Message-ID: <20061224161504.GD6618@jm.kir.nu>

On Tue, Dec 19, 2006 at 10:31:48AM -0500, Val Schmidt wrote:

> I am interested in encrypting a long haul point-to-point-link that  
> runs in ad-hoc mode. I've looked through the documentation for wpa- 
> supplicant and it is not clear to me that wpa supplicant supports  
> point-to-point links in ad-hoc mode. Is this true?

There is support for configuring a key for WPA-None case which a very
minimal adhoc mode version of using TKIP/CCMP encryption. However, this
is not very well supported mode (i.e., drivers do not support it) and
even the protocol design side is completely bogus as far as replay
protection is concerned. In other words, I cannot really recommend using
this.

At the moment, the easiest solution would likely be to change one of the
end-points to be in AP mode and the other one in client mode..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:18:06 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:18:06 -0800
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
References: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
Message-ID: <20061224161806.GE6618@jm.kir.nu>

On Tue, Dec 19, 2006 at 05:14:54PM +0100, Stefano Paris wrote:

> ap_scan=2
> network={
>     ssid="ibss-test"
>     mode=1
>     proto=WPA
>     key_mgmt=WPA-NONE
>     pairwise=NONE
>     group=CCMP
>     psk="ibss-test-key"
> }

> I used madwifi driver .
>
> When I started wpa_supplicant just 2 pc could communicate, the other one remained out, even if the cell and the key were the same of the other pcs.
> The problem seems to be the same that Ly Hong posted at Jul 14 2006 (wpa-supplicant for ad hoc network with more than 2 nodes).


This would a question to madwifi mailing list.. wpa_supplicant does not
really do more than just configure a key to the driver in WPA-None mode
and that's it.. The driver will need to take care of everything else in
this case. WPA-None mode has enough issues to make it difficult to find
someone who would be interested in actually using time to mkae it work,
though.. Adding support for IEEE 802.11i (WPA2) IBSS could be more
worthwhile target for efforts.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:22:09 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:22:09 -0800
Subject: devicescape headers changed.
In-Reply-To: <766169df0612190652k2fed23d1j38415ba1c73c08f4@mail.gmail.com>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
	<766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
	<1166538698.2753.8.camel@localhost.localdomain>
	<766169df0612190652k2fed23d1j38415ba1c73c08f4@mail.gmail.com>
Message-ID: <20061224162209.GF6618@jm.kir.nu>

On Tue, Dec 19, 2006 at 02:52:15PM +0000, miknix wrote:

> The latest rt2x00 driver does work in this kernel :\

I still don't know what "this kernel" is referring to.. Where did you
get the kernel source code from and which version is it?

> I think latest versions of rt2x00 have been fixed, but none of them builds
> with hostapd :(

The latest wireless-dev.git kernel (the main location for net/d80211
development) worked fine as far as building of hostapd is concerned, so
I can only assume you are using some other kernel which may have some
additional patches applied to it.

> Still want me to test with a fresh 2.6.19 vanilla?

If the rt2x00 driver requires net/d80211 and driver_devicescape.c, there
is not much point in trying with 2.6.19 since it does not include
net/d80211. Though, I would recommend using wireless-dev.git for this
test.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:23:27 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:23:27 -0800
Subject: Fwd: TKIP: replay detected:
In-Reply-To: <15116fd10612190635r27e951b6g43ef5a317828a426@mail.gmail.com>
References: <15116fd10612120053o30c5213ds370b950f2702f09@mail.gmail.com>
	<20061217043519.GG6119@jm.kir.nu>
	<1166370132.2757.17.camel@localhost.localdomain>
	<20061218045549.GE9711@jm.kir.nu>
	<20061219125825.GA24833@god.dyndns.org>
	<15116fd10612190634i2dffe78atfb01a342bfc5e5e4@mail.gmail.com>
	<15116fd10612190635r27e951b6g43ef5a317828a426@mail.gmail.com>
Message-ID: <20061224162327.GG6618@jm.kir.nu>

On Tue, Dec 19, 2006 at 02:35:18PM +0000, Vincent Panel wrote:

> I still have the same problem from time to time and my connection is
> incredibly slow when it occurs... Could it be linked to the fact that
> several access points belonging to the same ESSID surround me (of
> course, they have different AP adresses) ?

Unlikely, but really, this needs to be posted on the driver mailing
list, not here..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 08:33:05 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 08:33:05 -0800
Subject: Need help programming a prism card
In-Reply-To: <3263.128.132.174.49.1166475879.squirrel@www.coleinnovations.com>
References: <3263.128.132.174.49.1166475879.squirrel@www.coleinnovations.com>
Message-ID: <20061224163305.GH6618@jm.kir.nu>

On Mon, Dec 18, 2006 at 04:04:39PM -0500, jbarnett at coleinnovations.com wrote:

> Iv'e been working on this problem for some time now, and I am in need
> for some much needed help. Let me first describe what I am trying to
> accomplish, I current have a Intersil PRISM 2 (802.11b) PCMCIA wireless
> card; the card has three LEDs on the top part of the card. One of these
> LEDs is the power LED, which lights green when the card is turned on.

Do you have any more detail model number/vendor information for this
card?

> The PRISM 2 wireless card came with the old linux-wlan-ng 2.0 drivers;
> very out of date, and it also came with a tiny piece of software. This
> piece of software has a couple of functions that are used to control
> the wireless card; but the main function that I am interested in, is
> the function that turns the card on, called "cardon". When I properly
> configure the card using the linux-wlan-ng tools, and then run,
> "./cardon wlan0". The power LED light turns green, and I then run
> "tcpdump -x -X -s 2346 -vvv -i wlan0", which displays the expected
> results to standard out.

Hmm.. Is that linux-wlan-ng driver just a standard driver or do you know
whether it has been modified for this specific card? Are there some
specific hardware changes (like radio on/off switch etc.) here?

> My goal is to make this card work with the hostap-driver-0.4.9; which
> is the newest drivers for the PRISM chipset.

If the card is a standard Prism2/2.5/3 card, it should work as-is..

> Now, when I insert the PRISM 2 wireless card into my PCMCIA slot, with
> the hostAP drivers, the lights on the card flash; twice, then they go
> blank. Now when I go and run "./cardon wlan0" the card should turn on,
> but it doesn't because the "cardon" program is meant to communicate
> with the linux-wlan-ng drivers; not the hostAP drivers.

cardon command sounds like something that is just not going to work with
Host AP driver. Anyway, could could you please send 'dmesg' output
showing the kernel debug messages after the card is inserted?

> will work with the hostAP driver. I beleive I am using the correct
> value for the second aurgument to the ioctl call. I am not very good at

To which ioctl call?

> cmd: 24 = 0x11
> param0:  0 = 0x00
> param1:  0 = 0x00
> param2:  0 = 0x00
> response0:  0 = 0x00
> response1:  0 = 0x00
> response2: 24 = 0x11
> status:     1 = 0x01
> 
> 
> The incorrect values for comm_t are ..

This is some linux-wlan-ng specific structure and there is not much
point in trying to use that with Host AP driver.. Do you know what
exactly this cardon command is trying to do as far as the Prism2 card is
concerned?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Dec 24 11:23:51 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 11:23:51 -0800
Subject: hostapd handling .1x and reassoc
In-Reply-To: <e3c3c3bd0612220931p216060ceic16562830d505ec4@mail.gmail.com>
References: <e3c3c3bd0612220931p216060ceic16562830d505ec4@mail.gmail.com>
Message-ID: <20061224192351.GI6618@jm.kir.nu>

On Fri, Dec 22, 2006 at 09:31:00AM -0800, Ta-Chien Lin wrote:

> When hostapd is running in 802.1x mode and an associated client (AP's
> perspective) sends ASSOC or RE-ASSOC, both are treated as RE-ASSOC by
> hostapd.

> At this point, if the AP does not receive EAPOL-Start from the client (event
> 5 notification), for any reason, the connection remains "authorized" but
> there is no longer any KEY.
> 
> In a real assoc event, hostapd will take the data path to immediately begin
> .1X authentication, so the connection can move along, whether STA sends
> EAPOL-Start or not.
> 
> It would be good if on a "re-assoc" event, hostapd does the same thing,
> without waiting for STA's EAPOL-Start to show up.

Agreed.

> This can be accomplished by adding "sta->eapol_sm->reAuthenticate = TRUE;"
> in the function ieee802_1x_new_station, in the else clause of "if
> (sta->pmksa)", just before stepping through the eapol state machine.

Thanks for reporting this. I added this type of change into ieee802_1x.c
in 0.5.x and 0.6.x branches. Though, I'm only setting reAuthenticate =
TRUE on re-association, not when creating the EAPOL state machines for
the first time. Anyway, the end result is same.

-- 
Jouni Malinen                                            PGP id EFC895FA



From joerg  Sun Dec 24 15:31:22 2006
From: joerg (=?iso-8859-1?Q?J=F6rg?= Sommer)
Date: Mon, 25 Dec 2006 00:31:22 +0100
Subject: WPA-EAP-TTLS with AirPort Extreme
Message-ID: <20061224233122.GA29555@alea.gnuu.de>

Hi,

I configured my wpa_supplicant according the instructions at
<http://www.uni-jena.de/Linux_Fedora_Core___Scientific_Linux_4_x_mit_WPA_EAP_TTLS_PAP.html>,
but I can't connect to the network. The log is here
<http://www.minet.uni-jena.de/~joergs/wlan12.wpa>. Can someone tell we what
goes wrong? Why wpa_supplicant can not connect?

% uname -a
Linux ibook 2.6.18 #2 Tue Sep 26 14:33:04 CEST 2006 ppc GNU/Linux
% wpa_supplicant -v
wpa_supplicant v0.5.5
Copyright (c) 2003-2006, Jouni Malinen <jkmaline at cc.hut.fi> and contributors
zsh: exit 255   wpa_supplicant -v

It's a Debian unstable.

BTW: Why wpa_supplicant treats -v as an error?

Kind regards, J?rg.

PS: Please, Cc me. I'm not subscribed on the list.
-- 
Der Pessimist ist jemand, der vorzeitig die Wahrheit erz?hlt.
    	      	  	      		    	(Cyrano de Bergerac)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061225/4fc402c6/attachment.pgp 


From jkmaline  Sun Dec 24 15:59:05 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 24 Dec 2006 15:59:05 -0800
Subject: WPA-EAP-TTLS with AirPort Extreme
In-Reply-To: <20061224233122.GA29555@alea.gnuu.de>
References: <20061224233122.GA29555@alea.gnuu.de>
Message-ID: <20061224235904.GA9070@jm.kir.nu>

On Mon, Dec 25, 2006 at 12:31:22AM +0100, J?rg Sommer wrote:

> I configured my wpa_supplicant according the instructions at
> <http://www.uni-jena.de/Linux_Fedora_Core___Scientific_Linux_4_x_mit_WPA_EAP_TTLS_PAP.html>,
> but I can't connect to the network. The log is here
> <http://www.minet.uni-jena.de/~joergs/wlan12.wpa>. Can someone tell we what
> goes wrong? Why wpa_supplicant can not connect?

It looks like the association works fine and the AP is starting IEEE
802.1X authentication. However, there is no sign of a valid response to
the supplicant EAP response with the anonymous identity. It looks like
the AP could be disconnecting at this point.

Do you know whether there are some specific requirements for the
anonymous identity in this network? The instructions you pointed at did
not have any clear comment on the use anonymous_identity. Have you tried
commenting out anonymous_identity option (i.e., use the real identity in
first phase)?
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From venturini  Mon Dec 25 03:37:51 2006
From: venturini (Alberto Venturini)
Date: Mon, 25 Dec 2006 12:37:51 +0100
Subject: D-Link DRC-650 and wpa_supplicant fails
Message-ID: <20061225123751.c511081d.venturini@fastmail.fm>

Hello,
I've bought a D-Link DRC-650 wifi pc-card (AKA D-Link "Neteasy"), and
I want to use it in a WPA-PSK environment. I'm trying to get it
working with wpa_supplicant, but I haven't had much success so far.

My first doubt is the driver: this card has a PrismII chipset, so I
think the hostap driver is fine. But when I plug the card in, the udev
subsystem loads both hostap_cs and orinoco_cs modules. I'm a bit
confused: why are two drivers loaded? I'm using a 2.6.19.1 kernel; the
distribution is Archlinux.

Anyway, the card is identified, and when I do "iwconfig", both
wlan0 and wifi0 interfaces are listed. Now, I want to run
wpa_supplicant, and I run these commands:

[root at vega ~]# iwconfig wlan0 mode managed
[root at vega ~]# ifconfig wlan0 up
[root at vega ~]# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
-Dhostap
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported

and it hangs here. I'm stuck at this point: how can I get
wpa_supplicant to work with this card? I also tried to blacklist the
orinoco* modules, so only the hostap_cs module is loaded, but I get the
same error message from wpa_supplicant.

Thank you for any suggestions.

Alberto



From dtheoharis  Mon Dec 25 04:41:23 2006
From: dtheoharis (Dimitris Theoharis)
Date: Mon, 25 Dec 2006 07:41:23 -0500
Subject: hostap and 2.4 kernel
Message-ID: <3948f2f20612250441y5bbcfdf1mb2aaf97303d632e9@mail.gmail.com>

Hi

Is it possible to compile it against a 2.4 kernel? It complained about
wireless stuff missing from the kernel...



From joerg  Mon Dec 25 06:42:54 2006
From: joerg (=?iso-8859-1?Q?J=F6rg?= Sommer)
Date: Mon, 25 Dec 2006 15:42:54 +0100
Subject: WPA-EAP-TTLS with AirPort Extreme
In-Reply-To: <20061224235904.GA9070@jm.kir.nu>
References: <20061224233122.GA29555@alea.gnuu.de>
	<20061224235904.GA9070@jm.kir.nu>
Message-ID: <20061225144254.GC29555@alea.gnuu.de>

Jouni Malinen schrieb am Sun 24. Dec, 15:59 (-0800):
> On Mon, Dec 25, 2006 at 12:31:22AM +0100, J?rg Sommer wrote:
> 
> > I configured my wpa_supplicant according the instructions at
> > <http://www.uni-jena.de/Linux_Fedora_Core___Scientific_Linux_4_x_mit_WPA_EAP_TTLS_PAP.html>,
> > but I can't connect to the network. The log is here
> > <http://www.minet.uni-jena.de/~joergs/wlan12.wpa>. Can someone tell we what
> > goes wrong? Why wpa_supplicant can not connect?
> 
> It looks like the association works fine and the AP is starting IEEE
> 802.1X authentication. However, there is no sign of a valid response to
> the supplicant EAP response with the anonymous identity. It looks like
> the AP could be disconnecting at this point.

What might be the reason? The signal is stable and the people around me
did not raise their head.

> Do you know whether there are some specific requirements for the
> anonymous identity in this network?

I don't know. As far as I know is the anonymous identity for decrypting
the certificate and my password is for authentication.

What makes me wonder, all other people don't have problems with this
config. I'm in so far special, that I've an iBook G4 (PowerPC) with an
Airport Extreme card.

With OS X I have to use this anonymous identity, too.

> The instructions you pointed at did not have any clear comment on the
> use anonymous_identity. Have you tried commenting out
> anonymous_identity option (i.e., use the real identity in first phase)?

No, I can try it.

Bye, J?rg.
-- 
Diskutiere nie mit einem Idioten:
Sie ziehen Dich auf ihr Niveau herab und schlagen Dich dann mit
Erfahrung.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061225/1014db37/attachment.pgp 


From miknix  Mon Dec 25 09:22:52 2006
From: miknix (miknix)
Date: Mon, 25 Dec 2006 17:22:52 +0000
Subject: devicescape headers changed.
In-Reply-To: <20061224162209.GF6618@jm.kir.nu>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
	<766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
	<1166538698.2753.8.camel@localhost.localdomain>
	<766169df0612190652k2fed23d1j38415ba1c73c08f4@mail.gmail.com>
	<20061224162209.GF6618@jm.kir.nu>
Message-ID: <766169df0612250922u103186bdj245e0645496a6de3@mail.gmail.com>

Sorry.. I'm quite confused about this.
I thought wireless-dev tree was in sync with rt2x00 dscape..

I'm not using the wireless-dev.git tree. I'm using the dscape stack included
in the rt2x00 tarball.
My kernel is gentoo patched: 2.6.17-gentoo-r4

So.. latest hostapd builds against latest wireless-dev.git tree.
And I want to build hostapd with support to dscape driver to use my rt2x00
driver as master.
And the rt2x00 includes a different version of dscape.

Hostapd and rt2x00 must be built with same versions of dscape, right?
So what are my alternatives?


On 12/24/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Tue, Dec 19, 2006 at 02:52:15PM +0000, miknix wrote:
>
> > The latest rt2x00 driver does work in this kernel :\
>
> I still don't know what "this kernel" is referring to.. Where did you
> get the kernel source code from and which version is it?
>
> > I think latest versions of rt2x00 have been fixed, but none of them
> builds
> > with hostapd :(
>
> The latest wireless-dev.git kernel (the main location for net/d80211
> development) worked fine as far as building of hostapd is concerned, so
> I can only assume you are using some other kernel which may have some
> additional patches applied to it.
>
> > Still want me to test with a fresh 2.6.19 vanilla?
>
> If the rt2x00 driver requires net/d80211 and driver_devicescape.c, there
> is not much point in trying with 2.6.19 since it does not include
> net/d80211. Though, I would recommend using wireless-dev.git for this
> test.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061225/67d6f1c5/attachment.htm 


From dcbw  Mon Dec 25 15:15:59 2006
From: dcbw (Dan Williams)
Date: Mon, 25 Dec 2006 18:15:59 -0500
Subject: D-Link DRC-650 and wpa_supplicant fails
In-Reply-To: <20061225123751.c511081d.venturini@fastmail.fm>
References: <20061225123751.c511081d.venturini@fastmail.fm>
Message-ID: <1167088559.3173.4.camel@localhost.localdomain>

On Mon, 2006-12-25 at 12:37 +0100, Alberto Venturini wrote:
> Hello,
> I've bought a D-Link DRC-650 wifi pc-card (AKA D-Link "Neteasy"), and
> I want to use it in a WPA-PSK environment. I'm trying to get it
> working with wpa_supplicant, but I haven't had much success so far.
> 
> My first doubt is the driver: this card has a PrismII chipset, so I
> think the hostap driver is fine. But when I plug the card in, the udev
> subsystem loads both hostap_cs and orinoco_cs modules. I'm a bit
> confused: why are two drivers loaded? I'm using a 2.6.19.1 kernel; the

Because both drivers can actually drive your hardware.  Drivers are
supposed to be _able_ to bind to any hardware they support, which is
100% correct and fine.  Where this starts to break down is that, of
course, only one driver should bind to the card.  So you get to add
orinoco_cs, hermes, and orinoco to your /etc/modprobe.d/blacklist file
(or wherever Arch keeps the modprobe blacklist file).

dan

> distribution is Archlinux.
> 
> Anyway, the card is identified, and when I do "iwconfig", both
> wlan0 and wifi0 interfaces are listed. Now, I want to run
> wpa_supplicant, and I run these commands:
> 
> [root at vega ~]# iwconfig wlan0 mode managed
> [root at vega ~]# ifconfig wlan0 up
> [root at vega ~]# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
> -Dhostap
> ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
> 
> and it hangs here. I'm stuck at this point: how can I get
> wpa_supplicant to work with this card? I also tried to blacklist the
> orinoco* modules, so only the hostap_cs module is loaded, but I get the
> same error message from wpa_supplicant.
> 
> Thank you for any suggestions.
> 
> Alberto
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From dcbw  Mon Dec 25 15:18:43 2006
From: dcbw (Dan Williams)
Date: Mon, 25 Dec 2006 18:18:43 -0500
Subject: devicescape headers changed.
In-Reply-To: <766169df0612250922u103186bdj245e0645496a6de3@mail.gmail.com>
References: <766169df0612181124x476fa475ya82914a401c38044@mail.gmail.com>
	<1166470864.30000.7.camel@localhost.localdomain>
	<766169df0612181213j3e14f817kb8add44b44681be8@mail.gmail.com>
	<20061219033956.GC6633@jm.kir.nu>
	<766169df0612190623v11665355n416d1908f637d581@mail.gmail.com>
	<1166538698.2753.8.camel@localhost.localdomain>
	<766169df0612190652k2fed23d1j38415ba1c73c08f4@mail.gmail.com>
	<20061224162209.GF6618@jm.kir.nu>
	<766169df0612250922u103186bdj245e0645496a6de3@mail.gmail.com>
Message-ID: <1167088723.3173.8.camel@localhost.localdomain>

On Mon, 2006-12-25 at 17:22 +0000, miknix wrote:
> Sorry.. I'm quite confused about this.
> I thought wireless-dev tree was in sync with rt2x00 dscape..
> 
> I'm not using the wireless-dev.git tree. I'm using the dscape stack
> included in the rt2x00 tarball.

Warning :)  If the rt2x00 maintainers haven't kept their dscape stack up
with recent kernel developments, then you'll have problems.  This is
_always_ the problem with out-of-kernel drivers.  Please contact the
authors of the rt2x00 driver and ask them.  I _do_ know that they are
quite actively porting the rt2x00 drivers to the devicescape stack in
wireless-dev.git.  Ask them, people on this list aren't likely to know
much about that specific driver and whatever stack the driver
maintainers appear to be including wtih their tarball.

dan

> My kernel is gentoo patched: 2.6.17-gentoo-r4
> 
> So.. latest hostapd builds against latest wireless-dev.git tree.
> And I want to build hostapd with support to dscape driver to use my
> rt2x00 driver as master.
> And the rt2x00 includes a different version of dscape. 
> 
> Hostapd and rt2x00 must be built with same versions of dscape, right?
> So what are my alternatives?
> 
> 
> On 12/24/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>         On Tue, Dec 19, 2006 at 02:52:15PM +0000, miknix wrote: 
>         
>         > The latest rt2x00 driver does work in this kernel :\
>         
>         I still don't know what "this kernel" is referring to.. Where
>         did you
>         get the kernel source code from and which version is it?
>         
>         > I think latest versions of rt2x00 have been fixed, but none
>         of them builds
>         > with hostapd :(
>         
>         The latest wireless-dev.git kernel (the main location for
>         net/d80211
>         development) worked fine as far as building of hostapd is
>         concerned, so 
>         I can only assume you are using some other kernel which may
>         have some
>         additional patches applied to it.
>         
>         > Still want me to test with a fresh 2.6.19 vanilla?
>         
>         If the rt2x00 driver requires net/d80211 and
>         driver_devicescape.c, there 
>         is not much point in trying with 2.6.19 since it does not
>         include
>         net/d80211. Though, I would recommend using wireless-dev.git
>         for this
>         test.
>         
>         --
>         Jouni Malinen                                            PGP
>         id EFC895FA 
>         _______________________________________________
>         HostAP mailing list
>         HostAP at shmoo.com
>         http://lists.shmoo.com/mailman/listinfo/hostap
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From bhuvan.kumarmital  Mon Dec 25 20:03:07 2006
From: bhuvan.kumarmital (bhuvan.kumarmital at wipro.com)
Date: Tue, 26 Dec 2006 09:33:07 +0530
Subject: wpa_supplicant testing
Message-ID: <24ED22E506B5A042BF5B05B6B017D86CB05EE0@PNE-HJN-MBX01.wipro.com>



I am doing a project which deals with porting the wpa_supplicant code to
nucleus RTOS. Our job is to develop test scenarios to test the
authentication procedure and the ported supplicant code. Can anyone
provide me some inputs on how to proceed with this testing? I am new to
WLAN world however I'm aware of the WLAN terminology and technology by
now.

Please guide me on the following:
1. Developing Test Cases
2. How exactly do I make permutations and combinations for making more
.config files (wpa_supplicant configuration file)?
3. There are some sample configurations available. I am not able to
understand what the various parameters
(key_mgmt,wep_key0,wep_key1,wep_tx_keyidx etc..) mean. Is there any
documentation which can help me?
4. Does wpa_supplicant support ad-hoc mode operations and if yes what is
the limit to the maximum no. of devices which can be present in an
ad-hoc scenario?





Regards,
 
Bhuvan Mital



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From venturini  Tue Dec 26 01:23:38 2006
From: venturini (Alberto Venturini)
Date: Tue, 26 Dec 2006 10:23:38 +0100
Subject: D-Link DRC-650 and wpa_supplicant fails
In-Reply-To: <1167088559.3173.4.camel@localhost.localdomain>
References: <20061225123751.c511081d.venturini@fastmail.fm>
	<1167088559.3173.4.camel@localhost.localdomain>
Message-ID: <20061226102338.f7c74460.venturini@fastmail.fm>

On Mon, 25 Dec 2006 18:15:59 -0500
Dan Williams <dcbw at redhat.com> wrote:

> On Mon, 2006-12-25 at 12:37 +0100, Alberto Venturini wrote:
> > I've bought a D-Link DRC-650 wifi pc-card (AKA D-Link "Neteasy"), and
> > [...]
> > 
> > My first doubt is the driver: this card has a PrismII chipset, so I
> > think the hostap driver is fine. But when I plug the card in, the udev
> > subsystem loads both hostap_cs and orinoco_cs modules. I'm a bit
> > confused: why are two drivers loaded? I'm using a 2.6.19.1 kernel; the
> 
> Because both drivers can actually drive your hardware.  Drivers are
> supposed to be _able_ to bind to any hardware they support, which is
> 100% correct and fine.  Where this starts to break down is that, of
> course, only one driver should bind to the card.  So you get to add
> orinoco_cs, hermes, and orinoco to your /etc/modprobe.d/blacklist file
> (or wherever Arch keeps the modprobe blacklist file).
> 

Ok, thank you :)

> > Anyway, the card is identified, and when I do "iwconfig", both
> > wlan0 and wifi0 interfaces are listed. Now, I want to run
> > wpa_supplicant, and I run these commands:
> > 
> > [root at vega ~]# iwconfig wlan0 mode managed
> > [root at vega ~]# ifconfig wlan0 up
> > [root at vega ~]# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
> > -Dhostap
> > ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
> > 

I solved it upgrading the firmware, as explained here:
http://linux.junsun.net/intersil-prism/ . The preinstalled firmware
was an old 0.8.3 version; I upgraded it to 1.7.1, and now everything is
working fine.

Goodbye,
Alberto



From ambedkar_r  Wed Dec 27 06:18:23 2006
From: ambedkar_r (Ambedkar R)
Date: Wed, 27 Dec 2006 06:18:23 -0800 (PST)
Subject: wpa_supplicant testing
In-Reply-To: <24ED22E506B5A042BF5B05B6B017D86CB05EE0@PNE-HJN-MBX01.wipro.com>
Message-ID: <20061227141823.9917.qmail@web35814.mail.mud.yahoo.com>

Hi Bhuvan,
   
  1.To Develop test case:You should read the specifications such as design spec,functional spec or implementation spec which released to setup the test scenario.You ask your developer for those specs,without spec reading specs you can't understand its functionality and other stuff.
   
  2.To make conf files:There are many types which you can use it for your Station(Client) configuration,(1)Plain-text(2)Static WEP (3)WPA/WPA2 PSK (4)IEEE802.1X with Dynamic WEP keys (5) WPA/WPA2 Enterprise.
       Item number (4) and (5) which will use External/Internal authetication server.Internal authentication server means,server will be integarted on the AP.
      External server means,we have to use the FreeRADIUS or whichever available in the market.
   
  3.Sample conf:
   key_mgmt is for plain-text "NONE",WPA-PSK "WPA-PSK" and WPA Enterprise "WPA-EAP"
   "wep_key0" and "wep_key1",you can configure different keys for stations access,For example in CISCO AP,DEVICESCAPE AP and Broadcom AP you can configure 4 different wep keys.
    "wep_keyidx=0",if you configure in station the first key(wep_key0) will be used to associate with AP.
   
  4.Example conf,
   
  ap_scan=2
  network={
  ssid="WEP_TEST"
  key_mgmt=NONE
  wep_key0=1234567890
  wep_key1=1222222222
  wep_tx_keyidx=0
  auth_alg=OPEN
  }
   
   
  WPA-PSK
   
  ap_scan=2
  network={
  ssid="chennai"
  proto=WPA
  key_mgmt=WPA-PSK
  pairwise=CCMP
  group=CCMP
  psk="12345678"
  scan_ssid=1
  }
   
  -Ambedkar.R
  

bhuvan.kumarmital at wipro.com wrote:
  

I am doing a project which deals with porting the wpa_supplicant code to
nucleus RTOS. Our job is to develop test scenarios to test the
authentication procedure and the ported supplicant code. Can anyone
provide me some inputs on how to proceed with this testing? I am new to
WLAN world however I'm aware of the WLAN terminology and technology by
now.

Please guide me on the following:
1. Developing Test Cases
2. How exactly do I make permutations and combinations for making more
.config files (wpa_supplicant configuration file)?
3. There are some sample configurations available. I am not able to
understand what the various parameters
(key_mgmt,wep_key0,wep_key1,wep_tx_keyidx etc..) mean. Is there any
documentation which can help me?
4. Does wpa_supplicant support ad-hoc mode operations and if yes what is
the limit to the maximum no. of devices which can be present in an
ad-hoc scenario?





Regards,

Bhuvan Mital



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com
_______________________________________________
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 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061227/6c0a8434/attachment.htm 


From joerg  Wed Dec 27 05:35:54 2006
From: joerg (=?iso-8859-1?Q?J=F6rg?= Sommer)
Date: Wed, 27 Dec 2006 14:35:54 +0100
Subject: WPA-EAP-TTLS with AirPort Extreme
In-Reply-To: <20061224235904.GA9070@jm.kir.nu>
References: <20061224233122.GA29555@alea.gnuu.de>
	<20061224235904.GA9070@jm.kir.nu>
Message-ID: <20061227133554.GH29555@alea.gnuu.de>

Jouni Malinen schrieb am Sun 24. Dec, 15:59 (-0800):
> On Mon, Dec 25, 2006 at 12:31:22AM +0100, J?rg Sommer wrote:
> 
> > I configured my wpa_supplicant according the instructions at
> > <http://www.uni-jena.de/Linux_Fedora_Core___Scientific_Linux_4_x_mit_WPA_EAP_TTLS_PAP.html>,
> > but I can't connect to the network. The log is here
> > <http://www.minet.uni-jena.de/~joergs/wlan12.wpa>. Can someone tell we what
> > goes wrong? Why wpa_supplicant can not connect?
>
> Have you tried commenting out anonymous_identity option (i.e., use the
> real identity in first phase)?

Here is the output from the connection without the anonymous_identity.
http://www.minet.uni-jena.de/~joergs/wlan.13.wpa

Does it look like the kernel driver has a bug? Should I ask the bcm43xx
team for help?

Bye, J?rg.
-- 
[dpkg] We are the apt. Resistance is futile. You will be packaged.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061227/7fc22de3/attachment.pgp 


From benoit.papillault  Wed Dec 27 12:20:24 2006
From: benoit.papillault (Benoit PAPILLAULT)
Date: Wed, 27 Dec 2006 21:20:24 +0100
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <20061224161806.GE6618@jm.kir.nu>
References: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
	<20061224161806.GE6618@jm.kir.nu>
Message-ID: <4592D588.9070803@free.fr>

Jouni Malinen wrote:
> 
> This would a question to madwifi mailing list.. wpa_supplicant does not
> really do more than just configure a key to the driver in WPA-None mode
> and that's it.. The driver will need to take care of everything else in
> this case. WPA-None mode has enough issues to make it difficult to find
> someone who would be interested in actually using time to mkae it work,
> though.. Adding support for IEEE 802.11i (WPA2) IBSS could be more
> worthwhile target for efforts.
> 

Hi there,

I'm interested in using 802.11i in IBSS mode as well. I tried WPA-None 
on Linux and got nowhere and probably most people here. I've seen that 
WPA-None has been removed in the latest Windows SP2 patch (the patch 
needed to get WPA2 working). As such, i agree with Jouni that there's 
not much point in working on WPA-None. Beside it's not standard.

Jouni : since you are the most experienced on this subject, what effort 
would be involved in implementing 802.11i in IBSS mode? I'll be happy to 
contribute, except i'm not a security expert.

Best regards,
Benoit





From jkmaline  Wed Dec 27 13:26:45 2006
From: jkmaline (Jouni Malinen)
Date: Wed, 27 Dec 2006 13:26:45 -0800
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <4592D588.9070803@free.fr>
References: <20061219161455.88719.qmail@web28113.mail.ukl.yahoo.com>
	<20061224161806.GE6618@jm.kir.nu> <4592D588.9070803@free.fr>
Message-ID: <20061227212645.GE6683@jm.kir.nu>

On Wed, Dec 27, 2006 at 09:20:24PM +0100, Benoit PAPILLAULT wrote:

> Jouni : since you are the most experienced on this subject, what effort 
> would be involved in implementing 802.11i in IBSS mode? I'll be happy to 
> contribute, except i'm not a security expert.

One part of this has been done already, i.e., it is now possible to link
in authenticator code from hostapd into wpa_supplicant and then run both
authenticator and supplicant functionality in the same process. The
example code for doing this is in tests/test_wpa.c (make test_wpa).

The next step is to merge test_wpa.c code into the main supplicant in a
way that allows multiple authenticator and supplicant entities to be
created dynamically (IEEE 802.11i/IBSS requires both functions to be
implemented in each STA and there will be separate entities of each for
all the connections between STAs in the IBSS).

Final step would be to add support for some drivers to allow IEEE
802.11i/IBSS to be used. This would involve both configuration (e.g.,
suitable RSN IE into Beacon/ProbeRsp frames) and notifications (driver
event telling wpa_supplicant that a connection would be desired with a
given peer STA MAC address in the IBSS).

-- 
Jouni Malinen                                            PGP id EFC895FA



From bhuvan.kumarmital  Wed Dec 27 18:56:13 2006
From: bhuvan.kumarmital (bhuvan.kumarmital at wipro.com)
Date: Thu, 28 Dec 2006 08:26:13 +0530
Subject: wpa_supplicant testing
Message-ID: <24ED22E506B5A042BF5B05B6B017D86CB05EF3@PNE-HJN-MBX01.wipro.com>


Thanks Ambedkar,
	As for some clarification of point 2 below, where can I read more about the 5 configurations that you have listed below? Like you mentioned in point 3 below about some parameters (like key_mgmt), can I get a document where I get to read about these parameters (along with their description)? I have already gone through the sample configurations. I want to try some more combinations of configurations. I want a manual which explains each parameter and the situation in which I should be defined so that I can make my own sample configurations.


Regards,
?
Bhuvan Mital
Wipro Technologies
Pune
________________________________________
From: Ambedkar R [mailto:ambedkar_r at yahoo.com] 
Sent: Wednesday, December 27, 2006 7:48 PM
To: Bhuvan Kumarmital (WT01 - Semiconductors & Consumer Electronics); hostap at shmoo.com
Subject: Re: wpa_supplicant testing

Hi Bhuvan,
?
1.To Develop test case: You should read the specifications such as design spec, functional spec or implementation spec which released to setup the test scenario. You ask your developer for those specs, without spec reading specs you can't understand its functionality and other stuff.
?
2.To make conf files: There are many types which you can use it for your Station(Client) configuration,(1)Plain-text(2)Static WEP (3)WPA/WPA2 PSK (4)IEEE802.1X with Dynamic WEP keys (5) WPA/WPA2 Enterprise.
???? Item number (4) and (5) which will use External/Internal authetication server.Internal authentication server means,server will be integarted on the AP.
??? External server means,we have to?use the FreeRADIUS or whichever available in the market.
?
3.Sample conf:
?key_mgmt is for plain-text "NONE",WPA-PSK "WPA-PSK" and WPA Enterprise "WPA-EAP"
?"wep_key0" and "wep_key1",you can configure different keys for?stations access,For example in CISCO AP,DEVICESCAPE AP and Broadcom AP?you can configure 4 different wep keys.
? "wep_keyidx=0",if you configure in station the first key(wep_key0) will be used to associate with AP.
?
4.Example conf,
?
ap_scan=2
network={
ssid="WEP_TEST"
key_mgmt=NONE
wep_key0=1234567890
wep_key1=1222222222
wep_tx_keyidx=0
auth_alg=OPEN
}
?
?
WPA-PSK
?
ap_scan=2
network={
ssid="chennai"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk="12345678"
scan_ssid=1
}
?
-Ambedkar.R


bhuvan.kumarmital at wipro.com wrote:


I am doing a project which deals with porting the wpa_supplicant code to
nucleus RTOS. Our job is to develop test scenarios to test the
authentication procedure and the ported supplicant code. Can anyone
provide me some inputs on how to proceed with this testing? I am new to
WLAN world however I'm aware of the WLAN terminology and technology by
now.

Please guide me on the following:
1. Developing Test Cases
2. How exactly do I make permutations and combinations for making more
.config files (wpa_supplicant configuration file)?
3. There are some sample configurations available. I am not able to
understand what the various parameters
(key_mgmt,wep_key0,wep_key1,wep_tx_keyidx etc..) mean. Is there any
documentation which can help me?
4. Does wpa_supplicant support ad-hoc mode operations and if yes what is
the limit to the maximum no. of devices which can be present in an
ad-hoc scenario?





Regards,

Bhuvan Mital



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com
_______________________________________________
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 


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com



From surjitsingh1971  Thu Dec 28 04:55:42 2006
From: surjitsingh1971 (Surjit Singh)
Date: Thu, 28 Dec 2006 04:55:42 -0800 (PST)
Subject: need sample data for PTK and MIC calculations for WPA-PSK
Message-ID: <296654.15442.qm@web58913.mail.re1.yahoo.com>

Hi,

I'm trying to port wpa_supplicant to our system using
WPA-PSK. The Access Point (DI-524) doesnt respond to
the supplicant's Eapol Key. What could be the reason?
I have the following situation

A ----EAPOL key---> S
S ----EAPOL key---> A

No repsonse from A.

I'd like to test the code used on my system. I was
wondering if somebody would be good enough to direct
me to sample data that uses predefined values of
ANONCE and SNONCE and the addresses and the expected
values of the MIC and the PTK.

Thanks,
Surjit

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



From Jens.Rutschmann  Thu Dec 28 08:37:38 2006
From: Jens.Rutschmann (Jens Rutschmann)
Date: Thu, 28 Dec 2006 17:37:38 +0100
Subject: WPA/WPA2 with Prism54 card
In-Reply-To: <20061224155723.GB6618@jm.kir.nu>
References: <4589B463.2040902@online.de>	<1166660052.10335.5.camel@localhost.localdomain>	<458BC009.4020306@online.de>
	<20061224155723.GB6618@jm.kir.nu>
Message-ID: <4593F2D2.1020300@online.de>

I tested both WPA and "WPA2(AES)" (as called by my router) with -dd.

The attached archive contains two text files containing the output of 
wpa_supplicant:
output.tkip (for WPA)
output.ccmp (for WPA2)


It seems as if wpa_supplicant didn't even accept my AP as valid when set 
up with WPA2.

This is the configuration I used (pairwise and group were set to "CCMP" 
when trying WPA2):
network={
   ssid="rutschnet"
   psk="<secret_key_here>"
   proto=WPA
   key_mgmt=WPA-PSK
   pairwise=TKIP
   group=TKIP
}

As I didn't mention it before: I am using Gentoo Linux and I have 
compiled wpa_supplicant with full features excluding support for the 
madwifi drivers. I hope this doesn't matter in any way.

Jouni: sorry for the double post, I'm new to this mailing list stuff and 
I still have some issues with my mail client ...



Jouni Malinen wrote:
> On Fri, Dec 22, 2006 at 12:22:49PM +0100, Jens Rutschmann wrote:
>
>   Could you please re-run this with full debugging output from
> wpa_supplicant (-dd on command line)? Prism54 driver did not use to
> support WPA in client mode, but there has been some comments on that
> working with some changes. I have not tested this myself nor have I
> heard many clear success reports, so I don't know what exactly the
> current status of the WPA support in the driver is.
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: output.tar.gz
Type: application/gzip
Size: 2705 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061228/eccdff69/attachment.bin 


From leonerd  Thu Dec 28 09:01:31 2006
From: leonerd (Paul LeoNerd Evans)
Date: Thu, 28 Dec 2006 17:01:31 +0000
Subject: wpa_supplicant claims AP doesn't do WPA
In-Reply-To: <20061221005932.GD27285@cel.leo>
References: <20061221005932.GD27285@cel.leo>
Message-ID: <20061228170130.GH27285@cel.leo>

[repost for the list]

On Wed, Dec 20, 2006 at 10:01:27PM -0500, Dan Williams wrote:
> If your driver doesn't support returning the WPA IE in the scan results,
> it's certainly not going to work with WPA and wpa_supplicant.  Smells
> like a driver problem.
> 
> What driver are you using?  Does that driver really support WPA?  What
> hardware version is your card?    

Oh? I thought that was the point of wpa_supplicant? To do things in
software that the hardware can't do..? So it wouldn't matter what the
hardware driver natively supports. Or, do I have the wrong end of the
stick here?

> Is it prism or prism2 based?  What
> firmware version are you using?  Linksys has a long history of calling
> something the same product name but switching out chipsets; you may not
> have the card you think you do.    

OK, how might I find out these details? I presume some poking in proc?
I note it doesn't appear in lspci, though I understand that's normal for
PCMCIA cards.

> Do an lsmod and lets see what driver the kernel is binding to your card.    

The following I guess:

orinoco_cs             15556  1 
orinoco                34388  1 orinoco_cs
hermes                  7200  2 orinoco_cs,orinoco
pcmcia                 33788  1 orinoco_cs

> If you're using 'orinoco' drivers, they don't do WPA.  You might try
> blacklisting the orinoco ones and using the 'hostap' driver instead.    

OK.. I'll build myself another kernel with hostap in there as well, and
try that out. Thanks for the suggestion

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061228/da8cdf63/attachment.pgp 


From dcbw  Thu Dec 28 14:00:29 2006
From: dcbw (Dan Williams)
Date: Thu, 28 Dec 2006 17:00:29 -0500
Subject: wpa_supplicant claims AP doesn't do WPA
In-Reply-To: <20061228170130.GH27285@cel.leo>
References: <20061221005932.GD27285@cel.leo> <20061228170130.GH27285@cel.leo>
Message-ID: <1167343229.2853.7.camel@localhost.localdomain>

On Thu, 2006-12-28 at 17:01 +0000, Paul LeoNerd Evans wrote:
> [repost for the list]
> 
> On Wed, Dec 20, 2006 at 10:01:27PM -0500, Dan Williams wrote:
> > If your driver doesn't support returning the WPA IE in the scan results,
> > it's certainly not going to work with WPA and wpa_supplicant.  Smells
> > like a driver problem.
> > 
> > What driver are you using?  Does that driver really support WPA?  What
> > hardware version is your card?    
> 
> Oh? I thought that was the point of wpa_supplicant? To do things in
> software that the hardware can't do..? So it wouldn't matter what the
> hardware driver natively supports. Or, do I have the wrong end of the
> stick here?

No, you've got it a bit confused.  WPA requires a combination of
hardware support, firmware support, and software support.  If you don't
have the right combination of all of those, you can't do WPA.  Some
cards will _never_ do WPA at all, because the manufacturer just hasn't
updated the firmware, but the hardware can support it.  Others will
never do WPA because the _hardware_ itself cannot support WPA.

Sometimes the hardware just can't do WPA even if the software can.
Other times, the hardware can if you have the right software and
firmware.

> > Is it prism or prism2 based?  What
> > firmware version are you using?  Linksys has a long history of calling
> > something the same product name but switching out chipsets; you may not
> > have the card you think you do.    
> 
> OK, how might I find out these details? I presume some poking in proc?
> I note it doesn't appear in lspci, though I understand that's normal for
> PCMCIA cards.

No, you'll need to use:

pccardctl info

or 'lshal' to get the PCCard/PCMCIA vendor and product ID out of the
card.  PCMCIA is not PCI-based.

> > Do an lsmod and lets see what driver the kernel is binding to your card.    
> 
> The following I guess:
> 
> orinoco_cs             15556  1 
> orinoco                34388  1 orinoco_cs
> hermes                  7200  2 orinoco_cs,orinoco
> pcmcia                 33788  1 orinoco_cs
> 
> > If you're using 'orinoco' drivers, they don't do WPA.  You might try
> > blacklisting the orinoco ones and using the 'hostap' driver instead.    
> 
> OK.. I'll build myself another kernel with hostap in there as well, and
> try that out. Thanks for the suggestion

Before you do this, lets make sure your card is supported by the hostap
driver.  Which requires getting the PCMCIA vendor and product IDs out of
the card.

Dan




From leonerd  Thu Dec 28 14:50:07 2006
From: leonerd (Paul LeoNerd Evans)
Date: Thu, 28 Dec 2006 22:50:07 +0000
Subject: wpa_supplicant claims AP doesn't do WPA
In-Reply-To: <1167343229.2853.7.camel@localhost.localdomain>
References: <20061221005932.GD27285@cel.leo> <20061228170130.GH27285@cel.leo>
	<1167343229.2853.7.camel@localhost.localdomain>
Message-ID: <20061228225007.GI27285@cel.leo>

On Thu, Dec 28, 2006 at 05:00:29PM -0500, Dan Williams wrote:
> No, you've got it a bit confused.  WPA requires a combination of
> hardware support, firmware support, and software support.  If you don't
> have the right combination of all of those, you can't do WPA.
<snip>

Ahh right; that all makes sense.

> No, you'll need to use:
> 
> pccardctl info

# pccardctl info
PRODID_1="The Linksys Group, Inc."
PRODID_2="Instant Wireless Network PC Card"
PRODID_3="ISL37300P"
PRODID_4="RevA"
MANFID=0274,1613
FUNCID=6
...

# lshal
...
udi = '/org/freedesktop/Hal/devices/pcmcia__1__1'
  info.udi = '/org/freedesktop/Hal/devices/pcmcia__1__1'  (string)
  linux.subsystem = 'pcmcia'  (string)
  linux.hotplug_type = 1  (0x1)  (int)
  info.product = 'Instant Wireless Network PC Card'  (string)
  info.vendor = 'The Linksys Group, Inc.'  (string)
  pcmcia.func_id = 6  (0x6)  (int)
  pcmcia.card_id = 5651  (0x1613)  (int)
  pcmcia.manf_id = 628  (0x274)  (int)
  pcmcia.prod_id4 = 'RevA'  (string)
  pcmcia.prod_id3 = 'ISL37300P'  (string)
  pcmcia.prod_id2 = 'Instant Wireless Network PC Card'  (string)
  pcmcia.prod_id1 = 'The Linksys Group, Inc.'  (string)
  pcmcia.socket_number = 0  (0x0)  (int)
  info.linux.driver = 'orinoco_cs'  (string)
  info.parent = '/org/freedesktop/Hal/devices/pci_1180_476_0'  (string)
  info.bus = 'pcmcia'  (string)
  linux.sysfs_path_device = '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0'  (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0'  (string)
...

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061228/af89d421/attachment.pgp 


From paris_ste_82  Fri Dec 29 03:21:20 2006
From: paris_ste_82 (Stefano Paris)
Date: Fri, 29 Dec 2006 12:21:20 +0100 (CET)
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <20061227212645.GE6683@jm.kir.nu>
Message-ID: <20061229112120.1471.qmail@web28106.mail.ukl.yahoo.com>

Hi,

I'm also interested in developing IEEE 802.11i in IBSS mode, but I didn't find the test_wpa.c file in tests directory. Maybe the file is eapol_test.c, isn't it?

Thanks a lot.

Stefano Paris

Jouni Malinen <jkmaline at cc.hut.fi> ha scritto: On Wed, Dec 27, 2006 at 09:20:24PM +0100, Benoit PAPILLAULT wrote:

> Jouni : since you are the most experienced on this subject, what effort 
> would be involved in implementing 802.11i in IBSS mode? I'll be happy to 
> contribute, except i'm not a security expert.

One part of this has been done already, i.e., it is now possible to link
in authenticator code from hostapd into wpa_supplicant and then run both
authenticator and supplicant functionality in the same process. The
example code for doing this is in tests/test_wpa.c (make test_wpa).

The next step is to merge test_wpa.c code into the main supplicant in a
way that allows multiple authenticator and supplicant entities to be
created dynamically (IEEE 802.11i/IBSS requires both functions to be
implemented in each STA and there will be separate entities of each for
all the connections between STAs in the IBSS).

Final step would be to add support for some drivers to allow IEEE
802.11i/IBSS to be used. This would involve both configuration (e.g.,
suitable RSN IE into Beacon/ProbeRsp frames) and notifications (driver
event telling wpa_supplicant that a connection would be desired with a
given peer STA MAC address in the IBSS).

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


 __________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061229/1d2b10f2/attachment.htm 


From jkmaline  Fri Dec 29 08:07:40 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 29 Dec 2006 08:07:40 -0800
Subject: wpa_supplicant in ad hoc mode
In-Reply-To: <20061229112120.1471.qmail@web28106.mail.ukl.yahoo.com>
References: <20061227212645.GE6683@jm.kir.nu>
	<20061229112120.1471.qmail@web28106.mail.ukl.yahoo.com>
Message-ID: <20061229160740.GA6639@jm.kir.nu>

On Fri, Dec 29, 2006 at 12:21:20PM +0100, Stefano Paris wrote:

> I'm also interested in developing IEEE 802.11i in IBSS mode, but I didn't find the test_wpa.c file in tests directory. Maybe the file is eapol_test.c, isn't it?

No, this has nothing to do with eapol_test.c. Which version of
wpa_supplicant did you look at? This code is only available in the
latest 0.6.x snapshots.

-- 
Jouni Malinen                                            PGP id EFC895FA



From michaelr  Fri Dec 29 10:24:04 2006
From: michaelr (Michael Reilly)
Date: Fri, 29 Dec 2006 11:24:04 -0700
Subject: EAP-FAST under Windows XP
References: 3e2dce660603211745r36df40b7peb14cfe8d33d2005@mail.gmail.com?subject=
Message-ID: <45955D44.2050104@cisco.com>

Hi,

I work for Cisco Systems on IOS and use wpa_supplicant on my Linux system to
connect to Cisco APs in the office using EAP-FAST.  I discovered a bug in Cisco
APs which causes wpa_supplicant to fail and filed a bug report in June 2006.  (I
do not work in the group which creates the firmware for the APs - I am just a
user of the APs.)

"A change made to after 12.3(2)JA broke EAP-FAST functionality for a number of
supplicants which worked with prior versions of the AP-1100 when using the local
radius server.

That change assumes that if cipher suite TLS_DHE_RSA_WITH_AES_128_CBC_SHA1 is
offered in a received client hello message then the client wants to do initial
provisioning."

Since OpenSSL sends TLS_DHE_RSA_WITH_AES_128_CBC_SHA1 in its client hello
message the AP always assumes the client wants to do initial provisioning.

Anyway since I filed the bug report the Quality Assurance group is asking me for
a wpa_supplicant they can use to verify the fix.  For some reason I do not
understand they use Windows boxes as the clients.  So do you know of a
pre-compiled wpa_supplicant (and openssl if it is a separate binary on windows)
with EAP-FAST support which I could download for them?

Thank you,

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



From bryan  Fri Dec 29 10:41:43 2006
From: bryan (Bryan Kadzban)
Date: Fri, 29 Dec 2006 13:41:43 -0500
Subject: EAP-FAST under Windows XP
In-Reply-To: <45955D44.2050104@cisco.com>
References: 3e2dce660603211745r36df40b7peb14cfe8d33d2005@mail.gmail.com?subject=
	<45955D44.2050104@cisco.com>
Message-ID: <45956167.9020906@kadzban.is-a-geek.net>

Michael Reilly wrote:
> So do you know of a pre-compiled wpa_supplicant (and openssl if it is
> a separate binary on windows) with EAP-FAST support which I could
> download for them?

Not sure about EAP-FAST support, but the main wpa_supplicant page [0]
has a link to the most recent Windows binaries [1], along with a couple
older versions.

I am fairly sure these statically link OpenSSL; at least, I don't need a
separate installation of that on the machines I use the supplicant on.

[0] http://hostap.epitest.fi/wpa_supplicant/
[1] http://hostap.epitest.fi/releases/wpa_supplicant-windows-bin-0.5.6.zip

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


From jkmaline  Fri Dec 29 10:53:29 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 29 Dec 2006 10:53:29 -0800
Subject: EAP-FAST under Windows XP
In-Reply-To: <45955D44.2050104@cisco.com>
References: <45955D44.2050104@cisco.com>
Message-ID: <20061229185329.GB6639@jm.kir.nu>

On Fri, Dec 29, 2006 at 11:24:04AM -0700, Michael Reilly wrote:

> Anyway since I filed the bug report the Quality Assurance group is asking me for
> a wpa_supplicant they can use to verify the fix.  For some reason I do not
> understand they use Windows boxes as the clients.  So do you know of a
> pre-compiled wpa_supplicant (and openssl if it is a separate binary on windows)
> with EAP-FAST support which I could download for them?

I don't currently build Windows binaries with a modified OpenSSL, so
there is no EAP-FAST support. However, I should upgrade the OpenSSL
library to the latest version anyway, so I could patch it at the same
time for EAP-FAST support and try to make the next release (0.5.7) with
EAP-FAST enabled. I hope to get this released within next couple of
days. If there are no extra problems with the OpenSSL library build
(it was a bit complex process involving cygwin due to my
crosscompilation setup with MinGW..), you should be able to get a
suitable binary at that point.

-- 
Jouni Malinen                                            PGP id EFC895FA



From rhys_rhaven  Fri Dec 29 13:11:49 2006
From: rhys_rhaven (Rhys)
Date: Fri, 29 Dec 2006 13:11:49 -0800 (PST)
Subject: Shared IRQ Problem
Message-ID: <914301.46046.qm@web53404.mail.yahoo.com>

I have a Senao NL-2511CD, Prism2.5 chipset, 16bit pcmcia card. I get a hard lockup whenever the HostAP driver tries to load. 

pcmcia: request for exclusive IRQ could not be fulfilled.
pcmcia: the driver needs updating to supported shared IRQ lines.

^ this is what i get just before it crashes. It tries to assign it to IRQ 11. i would try to display the exact message from dmesg, but it always locks up immeadatly after this, with nothing more than the hardware address and IRQ where it is assigning it. 

Ive tried 2.6.19.1 as well, and it does the same thing, as well as 2.6.18.1. All do the same thing. Just for kicks i modprobed the orinoco_cs and hermes drivers, both cause a lockup. 

Is there any way to fix this on my machine where -everything- is IRQ 11?



Linux ares 2.6.18.6 #1 SMP PREEMPT Wed Dec 20 16:47:04 CET 2006 i686 pentium3 i386 GNU/Linux

root[/]# cat /proc/interrupts 
         
  CPU0       
  0:    2250910          XT-PIC  timer
  1:       5319             XT-PIC  i8042
  2:          0                XT-PIC  cascade
  9:          0                XT-PIC  acpi
 11:      68975           XT-PIC  yenta, yenta, uhci_hcd:usb1, ESS Maestro
 12:      34610           XT-PIC  i8042
 14:      14233           XT-PIC  ide0
NMI:          0 
LOC:          0 
ERR:          1
MIS:          0

Maestro is my sound card.. :\

root[/]# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:04.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 09)
00:09.1 Serial controller: Agere Systems LT WinModem
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)

The card doesnt show up in lspci, but pccardctl does.

root[/]# pccardctl status
Socket 0:
  3.3V 16-bit PC Card
  Subdevice 0 (function 0) [unbound]
Socket 1:
  no card

Socket 0:
  product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", ""
  manfid: 0x0156, 0x0002
  function: 6 (network)
Socket 1:
  no product info available



 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061229/d30c3c72/attachment.htm 


From proski  Fri Dec 29 14:24:46 2006
From: proski (Pavel Roskin)
Date: Fri, 29 Dec 2006 17:24:46 -0500
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
In-Reply-To: <N1-pt7KUPWAuS@Safe-mail.net>
References: <N1-pt7KUPWAuS@Safe-mail.net>
Message-ID: <1167431086.394.9.camel@dv>

Hello!

On Sun, 2006-12-24 at 04:26 +0000, re2823 at Safe-mail.net wrote:

> I cannot get my dwl-650p working on Debian Etch ("modprobe hostap_cs"
> does not create an extra interface), and I think that this might be due
> to a possible error in the manfid for my card. "pccardctl ident"
> returns:
> 
> Socket 0:
>   product info: "D-Link", "DWL-650 Wireless PC Card RevP", "ISL37101P-10", "A3"
>   manfid: 0x000b, 0x7110
>   function: 6 (network)
> 
> To find out if my card is supported in linux, I read the source code in
> the linux-2.6.19.1 kernel that I download from www.kernel.org. The ids
> in linux-2.6.19.1/drivers/net/wireless/hostap/hostap_plx.c start:
> 
>         { 0x000b, 0x7110 } /* D-Link DWL-650 Rev. P1 */,
[skip]
> while the ids in linux-2.6.19.1/drivers/net/wireless/hostap/hostap_cs.c
> start:
> 
>         PCMCIA_DEVICE_MANF_CARD(0x000b, 0x7100),
[skip]
> Then I notice that these two lists are identical except for the first
> entry, which is my card!

0x000b:0x7100 is "SonicWALL Long Range Wireless Card", whereas
0x000b:0x7110 is D-Link DWL-650 Rev P.  Both should be supported.

I think 0x000b:0x7110 should be added to hostap_cs.c.  It is present in
hostap_cs.conf distributed with hostap-0.4.9, but it was lost during
conversion to the embedded PCMCIA IDs.  The ID is also present in
wlan-ng.conf distributed with linux-wlan-ng, which further confirms that
the card uses a compatible Prism chipset.

And while at that, I don't think D-Link DWL-650 Rev P would actually
work in the PLX adapter (the card is 3.3V, the adapter is 5V), but it's
a separate question.

-- 
Regards,
Pavel Roskin





From swenggsri  Fri Dec 29 16:45:25 2006
From: swenggsri (Sriram Chadalavada)
Date: Fri, 29 Dec 2006 18:45:25 -0600
Subject: Hostap station mode active scan question
Message-ID: <e78b60ce0612291645k2fa9d98bod7c9d9e676954ee2@mail.gmail.com>

Hi  everyone,
   We are trying to measure the Effective Isotropic Radiated Power(EIRP) of
few prism3 based compact flash wireless cards running on an embedded target
with hostap 0.3.8. For this purpose we need to have the cards transmitting
without being associated to an access point. Probe requests sent as part of
an active scan should be sufficient.

If I use the 'iwlist wlan0 scan' command, does the card firmware perform an
active scan with probe requests or does it simply perform a passive scan of
the values already obtained from AP beacons?

>From the hostap README, I came to know of the 'iwpriv wlan0 host_scan <x>'
command which performs an active scan. Does this work even in the default
firmware roaming mode?

Also, is there a way I can restrict the active scan to be performed only in
one channel at a time? Please let me know.

Thank you,
Sriram C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061229/8af24d39/attachment.htm 


From jkmaline  Fri Dec 29 18:01:03 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 29 Dec 2006 18:01:03 -0800
Subject: EAP-FAST under Windows XP
In-Reply-To: <20061229185329.GB6639@jm.kir.nu>
References: <45955D44.2050104@cisco.com> <20061229185329.GB6639@jm.kir.nu>
Message-ID: <20061230020102.GA6654@jm.kir.nu>

On Fri, Dec 29, 2006 at 10:53:29AM -0800, Jouni Malinen wrote:

> I don't currently build Windows binaries with a modified OpenSSL, so
> there is no EAP-FAST support. However, I should upgrade the OpenSSL
> library to the latest version anyway, so I could patch it at the same
> time for EAP-FAST support and try to make the next release (0.5.7) with
> EAP-FAST enabled. I hope to get this released within next couple of
> days. If there are no extra problems with the OpenSSL library build
> (it was a bit complex process involving cygwin due to my
> crosscompilation setup with MinGW..), you should be able to get a
> suitable binary at that point.

Looks liks it is possible to build OpenSSL with a MinGW cross compiler
after some minor changes into the Configure script.. That makes it quite
a bit easier for me to build new OpenSSL versions, so today's snapshot
builds for Windows binaries from both 0.5 and 0.6 branches for
wpa_supplicant are now available with new OpenSSL version and EAP-FAST
support.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Dec 29 18:07:21 2006
From: jkmaline (Jouni Malinen)
Date: Fri, 29 Dec 2006 18:07:21 -0800
Subject: Hostap station mode active scan question
In-Reply-To: <e78b60ce0612291645k2fa9d98bod7c9d9e676954ee2@mail.gmail.com>
References: <e78b60ce0612291645k2fa9d98bod7c9d9e676954ee2@mail.gmail.com>
Message-ID: <20061230020721.GB6654@jm.kir.nu>

On Fri, Dec 29, 2006 at 06:45:25PM -0600, Sriram Chadalavada wrote:

>   We are trying to measure the Effective Isotropic Radiated Power(EIRP) of
> few prism3 based compact flash wireless cards running on an embedded target
> with hostap 0.3.8. For this purpose we need to have the cards transmitting
> without being associated to an access point. Probe requests sent as part of
> an active scan should be sufficient.

Setting the card in Host AP mode would make it send out periodic beacon
frames on one channel which could be even easier for this..

> If I use the 'iwlist wlan0 scan' command, does the card firmware perform an
> active scan with probe requests or does it simply perform a passive scan of
> the values already obtained from AP beacons?

This may depend on the firmware and regulatory configuration.. Should be
easy to figure out with a wireless sniffer, though.

> >From the hostap README, I came to know of the 'iwpriv wlan0 host_scan <x>'
> command which performs an active scan. Does this work even in the default
> firmware roaming mode?

Maybe, if you have new enough firmware.

> Also, is there a way I can restrict the active scan to be performed only in
> one channel at a time? Please let me know.

iwpriv wlan0 scan_channels <bitmask>

-- 
Jouni Malinen                                            PGP id EFC895FA



From jar  Sat Dec 30 02:02:57 2006
From: jar (Jar)
Date: Sat, 30 Dec 2006 12:02:57 +0200 (EET)
Subject: Shared IRQ Problem
In-Reply-To: <914301.46046.qm@web53404.mail.yahoo.com>
References: <914301.46046.qm@web53404.mail.yahoo.com>
Message-ID: <1130.62.148.193.191.1167472977.squirrel@netlandzone.dyndns.org>


> pcmcia: request for exclusive IRQ could not be fulfilled.
> pcmcia: the driver needs updating to supported shared IRQ lines.

So...hostap_cs doesn't support shared IRQs or what?


-- 
Best Regards, Jar



From jar  Sat Dec 30 02:40:46 2006
From: jar (Jar)
Date: Sat, 30 Dec 2006 12:40:46 +0200 (EET)
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
In-Reply-To: <1167431086.394.9.camel@dv>
References: <N1-pt7KUPWAuS@Safe-mail.net> <1167431086.394.9.camel@dv>
Message-ID: <1430.62.148.193.191.1167475246.squirrel@netlandzone.dyndns.org>


> I think 0x000b:0x7110 should be added to hostap_cs.c.  It is present in
> hostap_cs.conf distributed with hostap-0.4.9, but it was lost during
> conversion to the embedded PCMCIA IDs.  The ID is also present in
> wlan-ng.conf distributed with linux-wlan-ng, which further confirms that
> the card uses a compatible Prism chipset.

Is this is the reason why the wlan0 interface doesn't exixst? Hostap_cs doesn't know
that it actually supports 0x000b:0x7110.

-- 
Best Regards, Jar



From proski  Sat Dec 30 06:07:16 2006
From: proski (Pavel Roskin)
Date: Sat, 30 Dec 2006 09:07:16 -0500
Subject: Manfid typographical error in hostap_cs.c for Dlink dwl-650p?
In-Reply-To: <1430.62.148.193.191.1167475246.squirrel@netlandzone.dyndns.org>
References: <N1-pt7KUPWAuS@Safe-mail.net> <1167431086.394.9.camel@dv>
	<1430.62.148.193.191.1167475246.squirrel@netlandzone.dyndns.org>
Message-ID: <20061230090716.a4d0wswwgs4os4wo@webmail.spamcop.net>

Quoting Jar <jar at pcuf.fi>:

>
> > I think 0x000b:0x7110 should be added to hostap_cs.c.  It is present in
> > hostap_cs.conf distributed with hostap-0.4.9, but it was lost during
> > conversion to the embedded PCMCIA IDs.  The ID is also present in
> > wlan-ng.conf distributed with linux-wlan-ng, which further confirms that
> > the card uses a compatible Prism chipset.
>
> Is this is the reason why the wlan0 interface doesn't exixst? Hostap_cs
> doesn't know
> that it actually supports 0x000b:0x7110.

Yes, the reason is because the ID is not in the hostap_cs driver.

--
Regards,
Pavel Roskin



From jkmaline  Sat Dec 30 19:29:33 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 30 Dec 2006 19:29:33 -0800
Subject: [PATCH] wpa_supplicant FreeBSD compatibility
In-Reply-To: <3993a4980612200418u16006e3fred1b0e62c69dc140@mail.gmail.com>
References: <3993a4980612200418u16006e3fred1b0e62c69dc140@mail.gmail.com>
Message-ID: <20061231032933.GA6774@jm.kir.nu>

On Wed, Dec 20, 2006 at 01:18:49PM +0100, Jouke Witteveen wrote:

> I believe to have made a FreeBSD compatible version of
> wpa_supplicant's wired driver. Included are two patches. One for
> v0.4.8 (probably works for v0.4.9 as well) and one for v0.5.6.
> Please take a quick look and include them in the official tree.

Thanks! I applied this with couple of changes into 0.6 and 0.5 branches.

> Known bugs:
> - when no traffic is received over the multicast address SIOCDELMULTI
> throws in a ENOENT ("No such file or directory"). I believe this is
> normal; mtest yields it too.

OK, that's fine.

> - #ifndef __linux__ is used to check wether we are compiling for BSD.
> This is not too elegant (it works though).

Yes.. I changed this to be #ifdef __linux__ for Linux specific parts and
#ifdef __FreeBSD__ for FreeBSD specific..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sat Dec 30 19:54:53 2006
From: jkmaline (Jouni Malinen)
Date: Sat, 30 Dec 2006 19:54:53 -0800
Subject: [patch] bind to own_ip_addr for RADIUS communications
In-Reply-To: <458754BA.5060004@mattb.net.nz>
References: <458754BA.5060004@mattb.net.nz>
Message-ID: <20061231035453.GB6774@jm.kir.nu>

On Tue, Dec 19, 2006 at 03:55:54PM +1300, Matt Brown wrote:

> The attached patch forces hostapd to bind to the own_ip_addr specified
> in the configuration file for all RADIUS auth and acct traffic. This is
> desirable as many RADIUS servers authenticate clients based on an (ip,
> shared secret) tuple. If the hostapd machine has multiple interfaces
> with redundant connections to the RADIUS server it is possible that
> source IP address that the RADIUS server sees will not be consistent.

Hmm.. own_ip_addr has potentially been used with incorrect values (e.g.,
127.0.0.1 if the AS is remote) and this change would break this kind of
(admittedly incorrect) configuration..

Do you happen to know how different RADIUS servers select which shared
secret to use? Based on the source IP address or would NAS-IP-Address
override this?

I like the possibility of binding the sockets into a specific address,
but I'm not sure I would like to do this unconditionally..

> The patch also fixes what appeared to be a minor bug with v6 in
> radius_client_init_acct. The v6 socket was never opened, but code later
> in the function tried to use it regardless.

Thanks! It looks like I just forgot to copy the socket opening and error
checking code from the authentication case. My testing for the IPv6
version has been very limited and likely only for authentication, since
hostapd-as-radius-server does not support accounting.

> I had to rearrange where the own_ip_addr parameter is stored in the
> config structures so that it was available to the radius_init routines.

That's ok. It would also be worth considering to move the code that is
adding NAS-IP-Address attribute into the RADIUS client code with this
kind of change in where the IP address is stored (and same for
NAS-Identifier for that matter).. That would remove some duplicated code
since this is done in three different files at the moment.
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From cemcginley  Sun Dec 31 11:46:39 2006
From: cemcginley (Chris McGinley)
Date: Sun, 31 Dec 2006 11:46:39 -0800 (PST)
Subject: Problem with dhcpcd v3.0.8 in conjunction with WPA with
	wpa_supplication & hostap
Message-ID: <20061231194639.55325.qmail@web33009.mail.mud.yahoo.com>

I recently discovered a problem where my DHCP assignment times out using dhcpcd v3.0.8. It works correctly with dhcpcd v2.0.5-r1. The assignment works fine with WEP encryption, but not WPA or WPA2. I've been working with the dhcpcd developer, but it seems that the problem may be related to the hostap driver somehow as it cannot be reproduced elsewhere. Can anyone shed light on this? Any ideas how to troubleshoot the true source of the problem?

Thanks.

Chris



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20061231/8f4ae1d5/attachment.htm 


From cbzimmermann  Sun Dec 31 14:25:53 2006
From: cbzimmermann (Chris Zimmermann)
Date: Sun, 31 Dec 2006 14:25:53 -0800
Subject: [patch] bind to own_ip_addr for RADIUS communications
In-Reply-To: <20061231035453.GB6774@jm.kir.nu>
References: <458754BA.5060004@mattb.net.nz> <20061231035453.GB6774@jm.kir.nu>
Message-ID: <251D6C59-C8A5-45FA-8699-05601D1ED8A4@mac.com>

While it's true that most times a machine acting as a wireless access  
point would either use static addressing or get a DHCP address from a  
DHCP server based on it's MAC, own_ip_address is a potential problem  
for RADIUS server communication.  Some RADIUS servers, such as  
Elektron, allow any machine with a valid shared secret to communicate  
with it.  I ran into a problem where the machine running hostapd was  
using DHCP, got a different address, and hostapd did not know about  
the change to own_ip_address; causing RADIUS to no longer work.  It  
may be worthwhile to configure hostapd's RADIUS server communications  
via a specific interface and address types (a combination of one or  
more of the following; IPv4 routable, IPv4 link local, IPv6 routable,  
IPv6 link local, etc) and use routing socket notifications (or the  
equivalent on the OS) to enable hostapd to be aware of changes to the  
interface's address(es) and not require a SIGHUP when the situation  
occurs.

On Dec 30, 2006, at 7:54 PM, Jouni Malinen wrote:

> On Tue, Dec 19, 2006 at 03:55:54PM +1300, Matt Brown wrote:
>
>> The attached patch forces hostapd to bind to the own_ip_addr  
>> specified
>> in the configuration file for all RADIUS auth and acct traffic.  
>> This is
>> desirable as many RADIUS servers authenticate clients based on an  
>> (ip,
>> shared secret) tuple. If the hostapd machine has multiple interfaces
>> with redundant connections to the RADIUS server it is possible that
>> source IP address that the RADIUS server sees will not be consistent.
>
> Hmm.. own_ip_addr has potentially been used with incorrect values  
> (e.g.,
> 127.0.0.1 if the AS is remote) and this change would break this  
> kind of
> (admittedly incorrect) configuration..
>
> Do you happen to know how different RADIUS servers select which shared
> secret to use? Based on the source IP address or would NAS-IP-Address
> override this?
>
> I like the possibility of binding the sockets into a specific address,
> but I'm not sure I would like to do this unconditionally..
>
>> The patch also fixes what appeared to be a minor bug with v6 in
>> radius_client_init_acct. The v6 socket was never opened, but code  
>> later
>> in the function tried to use it regardless.
>
> Thanks! It looks like I just forgot to copy the socket opening and  
> error
> checking code from the authentication case. My testing for the IPv6
> version has been very limited and likely only for authentication,  
> since
> hostapd-as-radius-server does not support accounting.
>
>> I had to rearrange where the own_ip_addr parameter is stored in the
>> config structures so that it was available to the radius_init  
>> routines.
>
> That's ok. It would also be worth considering to move the code that is
> adding NAS-IP-Address attribute into the RADIUS client code with this
> kind of change in where the IP address is stored (and same for
> NAS-Identifier for that matter).. That would remove some duplicated  
> code
> since this is done in three different files at the moment.
>
> -- 
> Jouni Malinen                                            PGP id  
> EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap

Thanks,
Chris

-- 
Chris Zimmermann
cbzimmermann at mac.com



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


From jkmaline  Sun Dec 31 16:51:12 2006
From: jkmaline (Jouni Malinen)
Date: Sun, 31 Dec 2006 16:51:12 -0800
Subject: hostapd/wpa_supplicant - new stable release v0.5.7
Message-ID: <20070101005111.GC6730@jm.kir.nu>

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

This release moves 0.5.x branch from development to stable status. In
other words, from now on, 0.5.x versions are the latest available
stable releases. 0.4.x branch continues to be supported, but it is
moving more towards only including critical fixes. 0.3.x branch is
about to reach its end of life. I'm planning on releasing one more
0.3.x version with whatever changes have accumulated in the branch and
after that, no more changes are made to the 0.3.x branch unless
critical bugs are found. In other words, I would recommend starting to
move to either 0.5.x or 0.4.x versions if you are still using 0.3.x.

0.5.x development is in its own branch (hostap_0_5_branch) and CVS
trunk continues to be the place for the main development branch with
eventual 0.6.x releases. The development branch may also move to
Git-based repository in the future.


0.5.x branch brings in number of new features when comparing to the
previous stable branch (0.4.x). hostapd got support for multiple BSSes
per radio interface (only with some driver interfaces) and dynamic
VLAN configuration. Number of EAP methods were also added and/or
completed for the EAP server in hostapd.

wpa_supplicant 0.5.x has number of clean ups in the source code and
design to improve portability to new OSes and C libraries/compilers.
The included project files for Microsoft Visual Studio 2005 can be
used to build Windows versions natively. Number of improvements were
added to the Windows integration, too. Many EAP peer methods were
improved, just like the server side in hostapd.

An experimental TLSv1 client implementation was added to provide
better support for target systems that do not include TLS
functionality needed for EAP-TLS/PEAP/TTLS/FAST. One of the main goals
for this library is to keep the code size very small to fit into
embedded systems (adding just 30 kB or so of extra code whereas some
external libraries can be close to 1 MB in size).


Below are the change logs from 0.5.6. More detailed lists of changes
in older 0.5.x versions are included in the ChangeLog files in the
source code release files.

hostapd:
* updated EAP-SAKE to RFC 4763 and the IANA-allocated EAP type 48
* updated EAP-PSK to use the IANA-allocated EAP type 47
* fixed EAP-PSK bit ordering of the Flags field
* fixed configuration reloading (SIGHUP) to re-initialize WPA PSKs
  by reading wpa_psk_file [Bug 181]
* fixed EAP-TTLS AVP parser processing for too short AVP lengths
* fixed IPv6 connection to RADIUS accounting server

wpa_supplicant:
* updated EAP-SAKE to RFC 4763 and the IANA-allocated EAP type 48
* updated EAP-PSK to use the IANA-allocated EAP type 47
* fixed EAP-PAX key derivation
* fixed EAP-PSK bit ordering of the Flags field
* fixed EAP-PEAP/TTLS/FAST to use the correct EAP identifier in
  tunnelled identity request (previously, the identifier from the outer
  method was used, not the tunnelled identifier which could be
  different)
* fixed EAP-TTLS AVP parser processing for too short AVP lengths
* added support for EAP-FAST authentication with inner methods that
  generate MSK (e.g., EAP-MSCHAPv2 that was previously only supported
  for PAC provisioning)
* fixed dbus ctrl_iface to validate message interface before
  dispatching to avoid a possible segfault [Bug 190]
* fixed PeerKey key derivation to use the correct PRF label
* updated Windows binary build to link against OpenSSL 0.9.8d and
  added support for EAP-FAST


-- 
Jouni Malinen                                            PGP id EFC895FA



