From mstuff  Wed Sep  1 11:50:48 2004
From: mstuff (Morgan Read)
Date: Wed, 01 Sep 2004 14:50:48 -0400
Subject: firmware upgrade config
Message-ID: <41361A08.4060805@pl.net>

Hi,
Please, how do I enable firmware upgrade in hostap 0.2.4, instructions 
I've found say :
Enable PRISM2_DOWNLOAD_SUPPORT and PRISM2_NON_VOLATILE_DOWNLOAD in 
driver/modules/hostap_config.h. You simply just uncomment those two 
define's.

But, it's not so simple as PRISM2_NON_VOLATILE_DOWNLOAD seems to be 
embeded in some structure I don't understand.  Copied with my attempts:
******************************************
/* Include code for downloading firmware images into volatile RAM. */
define PRISM2_DOWNLOAD_SUPPORT

/* Allow kernel configuration to enable download support. */
#if !defined(PRISM2_DOWNLOAD_SUPPORT) && defined(CONFIG_HOSTAP_FIRMWARE)
#define PRISM2_DOWNLOAD_SUPPORT
#endif

#ifdef PRISM2_DOWNLOAD_SUPPORT
/* Allow writing firmware images into flash, i.e., to non-volatile storage.
  * Before you enable this option, you should make absolutely sure that 
you are
  * using prism2_srec utility that comes with THIS version of the driver!
  * In addition, please note that it is possible to kill your card with
  * non-volatile download if you are using incorrect image. This feature 
has not
  * been fully tested, so please be careful with it. */
/* #define PRISM2_NON_VOLATILE_DOWNLOAD */
#endif /* PRISM2_DOWNLOAD_SUPPORT */
define PRISM2_NON_VOLATILE_DOWNLOAD
******************************************
So, I get errors:
******************************************
[root at morgansmachine hostap-driver-0.2.4]# make
make -C /lib/modules/2.6.6-1.435.2.3/build 
SUBDIRS=/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules 
\
 
MODVERDIR=/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules 
modules
make[1]: Entering directory `/lib/modules/2.6.6-1.435.2.3/build'
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.o
In file included from 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:4,
                  from 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.c:38:
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_config.h:48: 
error: syntax error before "PRISM2_DOWNLOAD_SUPPORT"
In file included from 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:8,
                  from 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.c:38:
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt.h:4: 
error: syntax error before "struct"
make[2]: *** 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.o] 
Error 1
make[1]: *** 
[_module_/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules] 
Error 2
make[1]: Leaving directory `/lib/modules/2.6.6-1.435.2.3/build'
make: *** [2.6] Error 2
[root at morgansmachine hostap-driver-0.2.4]#
******************************************
Regards,
Morgan.
-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From mstuff  Wed Sep  1 12:12:40 2004
From: mstuff (Morgan Read)
Date: Wed, 01 Sep 2004 15:12:40 -0400
Subject: make warnings?
Message-ID: <41361F28.5070008@pl.net>

Hi List,
I'm getting a whole load of warnings on make with hostap as below, I 
don't think I used to get these, but may be i did & didn't notice them 
fly by because I didn't have my terminal window set so wide...  It seems 
to make install OK and then the drivers seem to load OK...  What do they 
mean and are they something to be worried with?
Any help very much appreciated.
Best regards,
Morgan.
******************************************
[root at morgansmachine hostap-driver-0.2.4]# make
make -C /lib/modules/2.6.6-1.435.2.3/build 
SUBDIRS=/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules 
\
 
MODVERDIR=/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules 
modules
make[1]: Entering directory `/lib/modules/2.6.6-1.435.2.3/build'
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_wep.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_tkip.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_ccmp.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.o
   CC [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.o
   Building modules, stage 2.
   MODPOST
*** Warning: "hostap_remove_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd_sta" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_remove_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_free_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_init_ap_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_init_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_add_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_init_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_80211_header_parse" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_master_start_xmit" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_setup_dev" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_info_init" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_multicast_list_queue" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "prism2_update_comms_qual" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_check_sta_fw_version" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_info_process" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_handle_sta_tx_exc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_80211_rx" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_80211_get_hdrlen" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_dump_rx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_dump_tx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_get_stats" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_auth_algs" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_roaming" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_antsel" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_encryption" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_string" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_get_porttype" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_set_word" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
has no CRC!
*** Warning: "hostap_remove_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd_sta" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_remove_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_free_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_init_ap_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_init_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_add_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_init_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_80211_header_parse" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_master_start_xmit" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_setup_dev" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_info_init" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_multicast_list_queue" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "prism2_update_comms_qual" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_check_sta_fw_version" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_info_process" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_handle_sta_tx_exc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_80211_rx" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_80211_get_hdrlen" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_dump_rx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_dump_tx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_get_stats" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_auth_algs" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_roaming" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_antsel" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_encryption" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_string" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_get_porttype" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_set_word" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko] 
has no CRC!
*** Warning: "hostap_remove_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd_sta" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_hostapd" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_remove_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_free_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_init_ap_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_init_proc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_add_interface" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_init_data" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_80211_header_parse" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_master_start_xmit" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_setup_dev" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_info_init" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_multicast_list_queue" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "prism2_update_comms_qual" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_check_sta_fw_version" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_info_process" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_handle_sta_tx_exc" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_80211_rx" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_80211_get_hdrlen" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_dump_rx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_dump_tx_header" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_get_stats" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_auth_algs" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_roaming" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_antsel" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_encryption" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_string" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_get_porttype" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_set_word" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko] 
has no CRC!
*** Warning: "hostap_unregister_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_wep.ko] 
has no CRC!
*** Warning: "hostap_register_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_wep.ko] 
has no CRC!
*** Warning: "hostap_unregister_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_tkip.ko] 
has no CRC!
*** Warning: "hostap_register_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_tkip.ko] 
has no CRC!
*** Warning: "hostap_unregister_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_ccmp.ko] 
has no CRC!
*** Warning: "hostap_register_crypto_ops" 
[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_ccmp.ko] 
has no CRC!
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_ccmp.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_ccmp.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_tkip.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_tkip.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_wep.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_crypt_wep.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_cs.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.ko
   CC 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.mod.o
   LD [M] 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko
make[1]: Leaving directory `/lib/modules/2.6.6-1.435.2.3/build'
make install_all_info
make[1]: Entering directory `/home/.Trash-root/hostap-driver-0.2.4'
*** Become superuser and 'make install' to install the modules. ***
make[1]: Leaving directory `/home/.Trash-root/hostap-driver-0.2.4'
[root at morgansmachine hostap-driver-0.2.4]#
******************************************
-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From mody  Wed Sep  1 00:29:58 2004
From: mody (mody at quick.cz)
Date: Wed, 1 Sep 2004 09:29:58 +0200
Subject: firmware upgrade config
In-Reply-To: <41361A08.4060805@pl.net>
References: <41361A08.4060805@pl.net>
Message-ID: <20040901072958.GA9427@sid>

Hi!

On Wed, Sep 01, 2004 at 14:50:48 -0400, Morgan Read wrote:
> #ifdef PRISM2_DOWNLOAD_SUPPORT
> /* Allow writing firmware images into flash, i.e., to non-volatile storage.
>  * Before you enable this option, you should make absolutely sure that 
> you are
>  * using prism2_srec utility that comes with THIS version of the driver!
>  * In addition, please note that it is possible to kill your card with
>  * non-volatile download if you are using incorrect image. This feature 
> has not
>  * been fully tested, so please be careful with it. */
> /* #define PRISM2_NON_VOLATILE_DOWNLOAD */
> #endif /* PRISM2_DOWNLOAD_SUPPORT */
> define PRISM2_NON_VOLATILE_DOWNLOAD

Looks like there is '#' missing in front of define. Should look like this:

#define PRISM2_NON_VOLATILE_DOWNLOAD

This is C, Morgan, '#' are not comments. :-)

HTH
Mody

-- 
Debian unstable 2.6.8-1-686 i686 GNU/Linux
-------------- 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/20040901/ae690947/attachment.pgp 


From eng10810  Wed Sep  1 00:32:25 2004
From: eng10810 (Henky Jatmiko Gunawan)
Date: Wed, 1 Sep 2004 15:32:25 +0800
Subject: Active scan control
Message-ID: <32A8E14B4023CC44B69BA8A630FF2CB21F4799@MBOX22.stu.nus.edu.sg>

I was looking through the source code for the active scan functionality in HostAP and I found this function in hostap_ioctl.c: prism2_ioctl_siwap. Can anyone tell me if this is the correct portion that I should be looking at?
 
In that function, I found scan_req.channel_list and I presume that modifying this value would allow me to instruct the card which channels to scan and which channels to skip. However, I am wondering if there is any way I can modify the scanning behaviour of the card e.g. order of the channels scanned and also the wait period for each channel.
 
Thanks in advance,
 
Henky
 


From kahing  Wed Sep  1 00:47:37 2004
From: kahing (Ka-Hing Cheung)
Date: Wed, 1 Sep 2004 00:47:37 -0700
Subject: DWL-520 trouble
In-Reply-To: <200409010944.57025.vda@port.imtp.ilyichevsk.odessa.ua>
References: <d9823ac104070700034fef376d@mail.gmail.com>
	<d9823ac1040718165011777af5@mail.gmail.com>
	<d9823ac104083120145e0b230f@mail.gmail.com>
	<200409010944.57025.vda@port.imtp.ilyichevsk.odessa.ua>
Message-ID: <d9823ac10409010047697a4683@mail.gmail.com>

On Wed, 1 Sep 2004 09:44:56 +0300, Denis Vlasenko
<vda at port.imtp.ilyichevsk.odessa.ua> wrote:
> Give up on automated scripts for now.
> Try to bring card up "by hand":
> 
> modprobe hostap_pci (or whatever)

Actually I've done that before using scripts, and modprob'ing would
crash the system. As you could see in the thread, there's nothing
interesting in syslog.

-khc



From vda  Wed Sep  1 01:14:20 2004
From: vda (Denis Vlasenko)
Date: Wed, 1 Sep 2004 11:14:20 +0300
Subject: DWL-520 trouble
In-Reply-To: <d9823ac10409010047697a4683@mail.gmail.com>
References: <d9823ac104070700034fef376d@mail.gmail.com>
	<200409010944.57025.vda@port.imtp.ilyichevsk.odessa.ua>
	<d9823ac10409010047697a4683@mail.gmail.com>
Message-ID: <200409011114.20769.vda@port.imtp.ilyichevsk.odessa.ua>

On Wednesday 01 September 2004 10:47, Ka-Hing Cheung wrote:
> On Wed, 1 Sep 2004 09:44:56 +0300, Denis Vlasenko
>
> <vda at port.imtp.ilyichevsk.odessa.ua> wrote:
> > Give up on automated scripts for now.
> > Try to bring card up "by hand":
> >
> > modprobe hostap_pci (or whatever)
>
> Actually I've done that before using scripts, and modprob'ing would
> crash the system. As you could see in the thread, there's nothing
> interesting in syslog.

Add printk("..."), yield() pairs to the driver initialization code.
Direct kernel log output to the tty.
Do:

# sleep 5; modprobe hostap_pci

switch to console with log and watch the fireworks.
--
vda




From wouter  Wed Sep  1 01:16:59 2004
From: wouter (Wouter de Jong)
Date: Wed, 1 Sep 2004 10:16:59 +0200
Subject: Atheros 5212 and WPA issues
Message-ID: <20040901081648.GB87052@widexs.nl>

Hello,

I'm trying to get my Atheros 5212 (mini-PCI) working under Gentoo Linux (kernel 2.6.7) with 
WPA. Either AES or TKIP (what is the 'best' and/or most secure option?).

All drivers are compiled (got CVS-version), and successfully load:

wlan: 0.8.4.2 (EXPERIMENTAL)
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.11.6
ath_pci: 0.9.4.0 (EXPERIMENTAL)

I can successfully use it with WEP-encryption, but I just can't get 
WPA to work. I've attached wpa_supplicant output. (Note that there are
more WLAN's configured here... the correct one is 'WIDEXS') 
(AP is currently in WPA-PSK mode with TKIP).

Anyone who has this baby working ?
Also, my AccessPoint is a Buffalo WLA-G54 (www.buffalotech.com)

Thanks in advance for any help.

Kind regards,

-- 
WideXS                          http://www.widexs.nl
Wouter de Jong                  System-Administrator
Tel +31 (0)23 5698070           Fax +31 (0)23 5698099
Bijlmermeerstraat 62,           2131 HG  HOOFDDORP, NL
-------------- next part --------------
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=0
Priority group 5
   id=0 ssid='WIDEXS'
wpa_driver_madwifi_set_wpa: enabled=1
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=ff:ff:ff:ff:ff:ff
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Network configuration found for the current AP
Cancelling authentication timeout
Wireless event: cmd=0x8b19 len=12
Received 538 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:07:40:da:d5:33 ssid='WDX-CUST' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:07:40:a0:80:fe ssid='WIDEXS' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:07:40:a0:80:fe (SSID='WIDEXS' freq=2432 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
Wireless event: cmd=0x8b1a len=18
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:07:40:a0:80:fe
Association event - clear replay counter
Associated to a new BSS: BSSID=00:07:40:a0:80:fe
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
Network configuration found for the current AP
Cancelling authentication timeout
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RX EAPOL from 00:07:40:a0:80:fe
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
Invalid group cipher (1).
WPA: Failed to generate WPA IE (for msg 2 of 4).
RX EAPOL from 00:07:40:a0:80:fe
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
Invalid group cipher (1).
WPA: Failed to generate WPA IE (for msg 2 of 4).
RX EAPOL from 00:07:40:a0:80:fe
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
Invalid group cipher (1).
WPA: Failed to generate WPA IE (for msg 2 of 4).
RX EAPOL from 00:07:40:a0:80:fe
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
Invalid group cipher (1).
WPA: Failed to generate WPA IE (for msg 2 of 4).
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Disconnect event - remove keys
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=00:07:40:a0:80:fe
Network configuration found for the current AP
Cancelling authentication timeout
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b19 len=12
Received 538 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 5
0: 00:07:40:da:d5:33 ssid='WDX-CUST' wpa_ie_len=24 rsn_ie_len=0
   skip - SSID mismatch
1: 00:07:40:a0:80:fe ssid='WIDEXS' wpa_ie_len=24 rsn_ie_len=0
   selected
Already associated with the selected AP.
Signal 2 received - terminating
wpa_driver_madwifi_deauthenticate
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_set_wpa: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0


From jkmaline  Wed Sep  1 07:05:28 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 1 Sep 2004 07:05:28 -0700
Subject: Atheros 5212 and WPA issues
In-Reply-To: <20040901081648.GB87052@widexs.nl>
References: <20040901081648.GB87052@widexs.nl>
Message-ID: <20040901140528.GB7162@jm.kir.nu>

On Wed, Sep 01, 2004 at 10:16:59AM +0200, Wouter de Jong wrote:

> I can successfully use it with WEP-encryption, but I just can't get 
> WPA to work. I've attached wpa_supplicant output. (Note that there are
> more WLAN's configured here... the correct one is 'WIDEXS') 
> (AP is currently in WPA-PSK mode with TKIP).

Do you know how the group cipher is configured? Is there any special
configuration for it or is it supposed to be TKIP for everything?

> Also, my AccessPoint is a Buffalo WLA-G54 (www.buffalotech.com)

What firmwate version are you using?

> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'

Could you please send the configuration file you are using?

> WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02

> IEEE 802.1X RX: version=1 type=3 length=95
>   EAPOL-Key type=254
> WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
> Invalid group cipher (1).
> WPA: Failed to generate WPA IE (for msg 2 of 4).

Hmm.. That group cipher 1 would be WPA_CIPHER_NONE which is not
allowed.. Odd that wpa_supplicant allowed the negotiation to go this
far. Own WPA IE above uses TKIP as the group cipher.. I will need to go
through the code to understand how this could happen.

Which version of wpa_supplicant are you using?

-- 
Jouni Malinen                                            PGP id EFC895FA



From syn-ack  Wed Sep  1 07:47:26 2004
From: syn-ack (syn-ack at 757.org)
Date: Wed, 1 Sep 2004 10:47:26 -0400 (EDT)
Subject: ioctl_sock error with FC2
Message-ID: <32083.204.37.10.8.1094050046.squirrel@users.757.org>

Having problems with FedoraCore2 and the 'set_iface_flags'...

below is a snipet of the error...

any help is appriciated.

-John

make HOSTAPD_PATH=/usr/include USEGTK=1 USECONSOL
E=1 all
make[1]: Entering directory `/tools/void11-0.2.0/lib'
gcc -O3 -fomit-frame-pointer -DVOID11_VERSION=\"0.2.0\" -I/usr/include -I.
  -c
-o void11.o void11.c
void11.c: In function `void11_set_iface_flags':
void11.c:91: error: structure has no member named `ioctl_sock'
void11.c:97: error: structure has no member named `ioctl_sock'
void11.c:107: error: structure has no member named `ioctl_sock'
void11.c:116: error: structure has no member named `ioctl_sock'
void11.c: In function `void11_ioctl':
void11.c:135: error: structure has no member named `ioctl_sock'
void11.c: In function `void11_ioctl_prism2param':
void11.c:154: error: structure has no member named `ioctl_sock




From gargid  Wed Sep  1 08:25:18 2004
From: gargid (Gargi D)
Date: Wed, 1 Sep 2004 20:55:18 +0530
Subject: PCMCIA Card which works with HostAP
Message-ID: <001601c49037$e39377b0$1006a8c0@rahul>

Hi,

The following card is working with HostAP.

The output of 

> cardctl ident

product info: "WLAN" , "PRISM PCMCIA CARD", "37300P", "Revision B6"
manfid: 0x50c2, 0x7300
function: 6 (network).

You might want to add it in hostap_cs.conf.

Regards,

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

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


From wouter  Wed Sep  1 09:06:36 2004
From: wouter (Wouter de Jong)
Date: Wed, 1 Sep 2004 18:06:36 +0200
Subject: Atheros 5212 and WPA issues
In-Reply-To: <20040901140528.GB7162@jm.kir.nu>
References: <20040901081648.GB87052@widexs.nl>
	<20040901140528.GB7162@jm.kir.nu>
Message-ID: <20040901160636.GA470@widexs.nl>

On Wed, Sep 01, 2004 at 07:05:28AM -0700, Jouni Malinen wrote:
> On Wed, Sep 01, 2004 at 10:16:59AM +0200, Wouter de Jong wrote:

Hi Jouni,

> > I can successfully use it with WEP-encryption, but I just can't get 
> > WPA to work. I've attached wpa_supplicant output. (Note that there are
> > more WLAN's configured here... the correct one is 'WIDEXS') 
> > (AP is currently in WPA-PSK mode with TKIP).
> 
> Do you know how the group cipher is configured? Is there any special
> configuration for it or is it supposed to be TKIP for everything?

Mm, see below. Don't know exactly what you mean :)

> > Also, my AccessPoint is a Buffalo WLA-G54 (www.buffalotech.com)
> 
> What firmwate version are you using?

WLA-G54 Ver.2.05, the latest available as of January 19th 2004

> > Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> 
> Could you please send the configuration file you are using?

Sure, I should have sent it in the first place :)
Here it is, but note that I've tried almost every combination that I've
found in the docs and howto's, etc:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=0
network={
	scan_ssid=1
	proto=WPA
	key_mgmt=WPA-PSK
	ssid="WIDEXS"
#	pairwise=TKIP
	psk="widexslan001"
	priority=5
}

Maybe this is a config that shouldn't work, but it just doesn't 
make a difference with whatever I configure in key_mgmt, pairwise, etc.

> > WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> 
> > IEEE 802.1X RX: version=1 type=3 length=95
> >   EAPOL-Key type=254
> > WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
> > Invalid group cipher (1).
> > WPA: Failed to generate WPA IE (for msg 2 of 4).
> 
> Hmm.. That group cipher 1 would be WPA_CIPHER_NONE which is not
> allowed.. Odd that wpa_supplicant allowed the negotiation to go this
> far. Own WPA IE above uses TKIP as the group cipher.. I will need to go
> through the code to understand how this could happen.

Mm, I see. The config-page for the Wireless LAN Security looks like this: 
http://www.maddog2k.net/stuff/tmp/buffalo-wla-g54-sc01.png

> Which version of wpa_supplicant are you using?

Version 0.2.4

Thanks for your time :)

-- 
WideXS                          http://www.widexs.nl
Wouter de Jong                  System-Administrator
Tel +31 (0)23 5698070           Fax +31 (0)23 5698099
Bijlmermeerstraat 62,           2131 HG  HOOFDDORP, NL



From kahing  Wed Sep  1 09:37:46 2004
From: kahing (Ka-Hing Cheung)
Date: Wed, 1 Sep 2004 09:37:46 -0700
Subject: DWL-520 trouble
In-Reply-To: <200409011114.20769.vda@port.imtp.ilyichevsk.odessa.ua>
References: <d9823ac104070700034fef376d@mail.gmail.com>
	<200409010944.57025.vda@port.imtp.ilyichevsk.odessa.ua>
	<d9823ac10409010047697a4683@mail.gmail.com>
	<200409011114.20769.vda@port.imtp.ilyichevsk.odessa.ua>
Message-ID: <d9823ac104090109374fdf6f2f@mail.gmail.com>

On Wed, 1 Sep 2004 11:14:20 +0300, Denis Vlasenko
<vda at port.imtp.ilyichevsk.odessa.ua> wrote:
> Add printk("..."), yield() pairs to the driver initialization code.
> Direct kernel log output to the tty.
> Do:
> 
> # sleep 5; modprobe hostap_pci

Actually Jouni gave me a patch to insert some printk's, and I posted
the result in a previous email in the same thread.

This problem seems to be specific to the card (or maybe even the
revision), I've heard of a couple others having the same problem.

-khc



From HostAP-Research  Wed Sep  1 09:45:44 2004
From: HostAP-Research (AP-Research)
Date: Wed, 1 Sep 2004 11:45:44 -0500 (CDT)
Subject: firmware upgrade config
In-Reply-To: <41361A08.4060805@pl.net>
References: <41361A08.4060805@pl.net>
Message-ID: <32884.208.54.95.1.1094057144.squirrel@208.54.95.1>


<quote who="Morgan Read">
> Enable PRISM2_DOWNLOAD_SUPPORT and PRISM2_NON_VOLATILE_DOWNLOAD in
> driver/modules/hostap_config.h. You simply just uncomment those two
> define's.

> ******************************************
> /* Include code for downloading firmware images into volatile RAM. */
> define PRISM2_DOWNLOAD_SUPPORT

Remarks in source code differ than config files.  "/*" and "*/" surround
comments in C like languages.  The "#" at the beginning of the line isn't
a remark statement... replace it.  The line should read:

#define PRISM2_DOWNLOAD_SUPPORT



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



From ramalhais  Wed Sep  1 12:14:13 2004
From: ramalhais (Pedro Ramalhais)
Date: Wed, 01 Sep 2004 20:14:13 +0100
Subject: Atheros 5212 and WPA issues
In-Reply-To: <20040901160636.GA470@widexs.nl>
References: <20040901081648.GB87052@widexs.nl>
	<20040901140528.GB7162@jm.kir.nu>  <20040901160636.GA470@widexs.nl>
Message-ID: <1094066053.24204.3126.camel@gandalf.uninova.pt>

Hi!

On Wed, 2004-09-01 at 17:06, Wouter de Jong wrote:
> On Wed, Sep 01, 2004 at 07:05:28AM -0700, Jouni Malinen wrote:
> > On Wed, Sep 01, 2004 at 10:16:59AM +0200, Wouter de Jong wrote:
> 
> Hi Jouni,
> 
> > > I can successfully use it with WEP-encryption, but I just can't get 
> > > WPA to work. I've attached wpa_supplicant output. (Note that there are
> > > more WLAN's configured here... the correct one is 'WIDEXS') 
> > > (AP is currently in WPA-PSK mode with TKIP).
> > 
> > Do you know how the group cipher is configured? Is there any special
> > configuration for it or is it supposed to be TKIP for everything?
> 
> Mm, see below. Don't know exactly what you mean :)
> 
> > > Also, my AccessPoint is a Buffalo WLA-G54 (www.buffalotech.com)
> > 
> > What firmwate version are you using?
> 
> WLA-G54 Ver.2.05, the latest available as of January 19th 2004
> 
> > > Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> > 
> > Could you please send the configuration file you are using?
> 
> Sure, I should have sent it in the first place :)
> Here it is, but note that I've tried almost every combination that I've
> found in the docs and howto's, etc:
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=0
> network={
> 	scan_ssid=1
> 	proto=WPA
> 	key_mgmt=WPA-PSK
> 	ssid="WIDEXS"
> #	pairwise=TKIP

Maybe you should set pairwise=TKIP CCMP so it accepts both cyphers.

> 	psk="widexslan001"

psk=64 HEXADECIMAL DIGITS, not a passphrase (i think)

> 	priority=5
> }
> 
> Maybe this is a config that shouldn't work, but it just doesn't 
> make a difference with whatever I configure in key_mgmt, pairwise, etc.
> 
> > > WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> > 
> > > IEEE 802.1X RX: version=1 type=3 length=95
> > >   EAPOL-Key type=254
> > > WPA: RX message 1 of 4-Way Handshake from 00:07:40:a0:80:fe (ver=1)
> > > Invalid group cipher (1).
> > > WPA: Failed to generate WPA IE (for msg 2 of 4).
> > 
> > Hmm.. That group cipher 1 would be WPA_CIPHER_NONE which is not
> > allowed.. Odd that wpa_supplicant allowed the negotiation to go this
> > far. Own WPA IE above uses TKIP as the group cipher.. I will need to go
> > through the code to understand how this could happen.
> 
> Mm, I see. The config-page for the Wireless LAN Security looks like this: 
> http://www.maddog2k.net/stuff/tmp/buffalo-wla-g54-sc01.png
> 
> > Which version of wpa_supplicant are you using?
> 
> Version 0.2.4
> 
> Thanks for your time :)
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From pesto  Wed Sep  1 12:57:20 2004
From: pesto (pesto at diet.drpepper.org)
Date: Wed, 1 Sep 2004 14:57:20 -0500 (CDT)
Subject: Had it working for a while...
Message-ID: <E1C2bEO-0003K8-TD@diet.drpepper.org>

I'm using 0.2.4 on fedora core 2 2.6.8-1.521. 
I had hostap working fine, until I installed the wlan-ng driver. I've since removed that driver and tried reinstalling hostap... it installs fine, but doesn't create an interface. When I insert my card, insmod doesn't show the hostap or hostap_cs modules loaded...even after doing an insmod, nothing changes. Restarting pcmcia service, nothing changes.

Any help would be appreciated.




From mstuff  Thu Sep  2 07:46:39 2004
From: mstuff (Morgan Read)
Date: Thu, 02 Sep 2004 10:46:39 -0400
Subject: No primary upgrade?
Message-ID: <4137324F.6060006@pl.net>

Hi list (agian:)
Any ideas why primary firmware might not be upgrading as indicated below?
Regards,
Morgan.
***************************
[root at morgansmachine root]# prism2_srec -r wlan0 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/firmware-1.7.4/mycardPri+SecRAM/ak010104.hex 
/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/firmware-1.7.4/mycardPri+SecRAM/rf010704.hex
srec summary for ak010104.hex
Included file name: AK010104.HEX
Component: 0x0015 1.1.4 (primary firmware)

srec summary for rf010704.hex
Included file name: RF010704.HEX
Component: 0x001f 1.7.4 (station firmware)


Verifying update compatibility and combining data:
PRI: old iface 1:4-4 new iface 4:4-5
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
OK.

Downloading to volatile memory (RAM).
OK.
Components after download:
   NICID: 0x801b v1.0.0
   PRIID: 0x0015 v1.1.0
   STAID: 0x001f v1.7.4
[root at morgansmachine root]# hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x801b v1.0.0 (PRISM III PCMCIA (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.7.4 (station firmware)
You have new mail in /var/spool/mail/root
[root at morgansmachine root]#
***************************
-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From mstuff  Thu Sep  2 08:05:37 2004
From: mstuff (Morgan Read)
Date: Thu, 02 Sep 2004 11:05:37 -0400
Subject: make warnings?
In-Reply-To: <1094009421.5356.2.camel@rootix>
References: <41361F28.5070008@pl.net> <1094009421.5356.2.camel@rootix>
Message-ID: <413736C1.8030409@pl.net>

Thanks for bearing with me, thanks also to Mody who emailed same off list.
Regards,
Morgan.

Pedro Ramalhais wrote:
> On Wed, 2004-09-01 at 20:12, Morgan Read wrote:
> 
>>Hi List,
>>I'm getting a whole load of warnings on make with hostap as below, I 
>>don't think I used to get these, but may be i did & didn't notice them 
>>fly by because I didn't have my terminal window set so wide...  It seems 
>>to make install OK and then the drivers seem to load OK...  What do they 
>>mean and are they something to be worried with?
>>Any help very much appreciated.
>>Best regards,
>>Morgan.
>>******************************************
>>[root at morgansmachine hostap-driver-0.2.4]# make
>>make -C /lib/modules/2.6.6-1.435.2.3/build 
> 
> 
> ...
> 
> 
>>/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_pci.o
>>   Building modules, stage 2.
>>   MODPOST
>>*** Warning: "hostap_remove_interface" 
>>[/home/morgan/Desktop/AlliedTelesyn_WiFi_Card/hostap-driver-0.2.4/driver/modules/hostap_plx.ko] 
>>has no CRC!
> 
> 
> This is a bug in the kernel, i think it has been fixed, just don't know
> in which version. I've used 2.6.7 and 2.6.8.1 and don't see those
> messages. Try upgrading your kernel.
> Anyway, the messages are harmless.

-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From jkmaline  Wed Sep  1 18:42:48 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 1 Sep 2004 18:42:48 -0700
Subject: Atheros 5212 and WPA issues
In-Reply-To: <1094066053.24204.3126.camel@gandalf.uninova.pt>
References: <20040901081648.GB87052@widexs.nl>
	<20040901140528.GB7162@jm.kir.nu> <20040901160636.GA470@widexs.nl>
	<1094066053.24204.3126.camel@gandalf.uninova.pt>
Message-ID: <20040902014248.GA7393@jm.kir.nu>

On Wed, Sep 01, 2004 at 08:14:13PM +0100, Pedro Ramalhais wrote:

> > #	pairwise=TKIP
> 
> Maybe you should set pairwise=TKIP CCMP so it accepts both cyphers.

That is the default if pairwise is not..

> > 	psk="widexslan001"
> 
> psk=64 HEXADECIMAL DIGITS, not a passphrase (i think)

No, it allows both forms.. Either psk="passphrase" or psk=0123... for
the hex version.

The configuration file itself looked fine, something else is going wrong
in somewhat odd way.

-- 
Jouni Malinen                                            PGP id EFC895FA



From brian  Wed Sep  1 18:46:17 2004
From: brian (Brian J. Murrell)
Date: Wed, 01 Sep 2004 21:46:17 -0400
Subject: unicast traffic stops after a while with wpa_supplicant
Message-ID: <1094089577.29672.66.camel@pc>

[ Try this again, with log fetchable at a URL rather than attached as it
seems bigger than the list allows and my previous post seems to be stuck
in moderator approval status ]

I am using hostap/wpa_supplicant from the current stable branch with
moderate success other than the slow throughput that I posted about in
an earlier message.

I am running into one issue though, where after a while unicast traffic
stop but multicast/broadcast traffic continues.  I have to restart
wpa_supplicant and all is good again.

Find at http://brian.interlinx.bc.ca/wpa_supplicant.txt a transcript of
such a session.

Any ideas?

b.

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


From snai8255  Wed Sep  1 21:33:57 2004
From: snai8255 (snai8255 at mail.usyd.edu.au)
Date: Thu,  2 Sep 2004 14:33:57 +1000
Subject: key_idx?
Message-ID: <1094099637.4136a2b5b0b5f@www-mail.usyd.edu.au>

hi guys;

i was wondering what is the "key_idx" field in "prism2_wep_data" structure in hostap_crypt_wep.c
used for?

also does anyone know where is the "prism_wep_init" function called from within the driver?

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From jkmaline  Wed Sep  1 22:08:15 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 1 Sep 2004 22:08:15 -0700
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040831085838.GC28682@informatik.uni-rostock.de>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
Message-ID: <20040902050815.GC7393@jm.kir.nu>

On Tue, Aug 31, 2004 at 10:58:38AM +0200, Gunter Burchardt wrote:

> First patch to bring wired authentication with hostapd alive. This
> patch enables hostapd to send and recieve eapol frames via ethernet.
> Furthermore sta detection is implemented via dhcp for station which
> didn't send eapol-start (like winxp supplicant).

Thanks! I haven't yet merged this in, but couple of quick
comments/questions first..

Is there any particular reason for parsing DHCP packets? One option
would be to open packet socket on the same interface with Linux Socket
filter to capture the packets and then take the layer 2 address from
them. Then again, this may not end up being much simpler. Eventually, I
would assume this could be replaced with something like iptables
firewall queueing packets from unknown MAC addresses for user space
processing and all devices would be noticed whenever they send the first
packet, no matter whether it is DHCP or something else, i.e., static IP
and non-IPv4 hosts would also be processed.

> In ieee802_11.c auth_get_sta() is implemented. I think this function
> should move to hostapd.c . There are no 802.11 thinks in this function.
> At the moment i declared this function to extern.

I would agree on moving the function, although I would probably move it
to sta_info.c, not hostapd.c. In addition, the function should be
renamed to something like ap_sta_add().

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Wed Sep  1 23:11:20 2004
From: gbur (Gunter Burchardt)
Date: Thu, 2 Sep 2004 08:11:20 +0200
Subject: Had it working for a while...
In-Reply-To: <E1C2bEO-0003K8-TD@diet.drpepper.org>
References: <E1C2bEO-0003K8-TD@diet.drpepper.org>
Message-ID: <20040902061120.GD28682@informatik.uni-rostock.de>

> I'm using 0.2.4 on fedora core 2 2.6.8-1.521. 
> I had hostap working fine, until I installed the wlan-ng driver. I've since removed that driver and tried reinstalling hostap... it installs fine, but doesn't create an interface. When I insert my card, insmod doesn't show the hostap or hostap_cs modules loaded...even after doing an insmod, nothing changes. Restarting pcmcia service, nothing changes.

Could it be that there is a wlan-ng module loaded? I had same with
orinoko stuff. Perhaps ng driver is compiled into kernel.

regards
gunter 



From gbur  Wed Sep  1 23:55:05 2004
From: gbur (Gunter Burchardt)
Date: Thu, 2 Sep 2004 08:55:05 +0200
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040902050815.GC7393@jm.kir.nu>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
	<20040902050815.GC7393@jm.kir.nu>
Message-ID: <20040902065505.GE28682@informatik.uni-rostock.de>

> > First patch to bring wired authentication with hostapd alive. This
> > patch enables hostapd to send and recieve eapol frames via ethernet.
> > Furthermore sta detection is implemented via dhcp for station which
> > didn't send eapol-start (like winxp supplicant).
> 
> Thanks! I haven't yet merged this in, but couple of quick
> comments/questions first..


> Is there any particular reason for parsing DHCP packets? One option
> would be to open packet socket on the same interface with Linux Socket
> filter to capture the packets and then take the layer 2 address from
> them. Then again, this may not end up being much simpler. Eventually, I
> would assume this could be replaced with something like iptables
> firewall queueing packets from unknown MAC addresses for user space
> processing and all devices would be noticed whenever they send the first
> packet, no matter whether it is DHCP or something else, i.e., static IP
> and non-IPv4 hosts would also be processed.

Sounds good. I will check it. But iptables has no real api. In
documentation iptables_restore is recommended as api. I've written a
function that starts iptables_restore, puts the iptables rules to its
stdin and parses stdout to check if it was successfull. I'm realy
unhappy about this. But at the moment i see no other way. 

I would like to use iptables for port authorization. Adding some rules
for authorized stations that patckets from this station where acceptet.
But iptables is layer 3 in ISO/OSI. Only ip address is known. Ok you
can match to incomming mac address. But there is no way to controll
packets sent to the station without knowlege of the ip address of this
station. 

Another way is that only one station can connect to a port (device).
Together with vlan-devices and a vlan enabled switch it would be a
secure way.

Is accounting using iptables ok? I will not count all packets in user
space (to slow) and i will not hack into device drivers.

> > In ieee802_11.c auth_get_sta() is implemented. I think this function
> > should move to hostapd.c . There are no 802.11 thinks in this function.
> > At the moment i declared this function to extern.
> 
> I would agree on moving the function, although I would probably move it
> to sta_info.c, not hostapd.c. In addition, the function should be
> renamed to something like ap_sta_add().

Should i do it or you?

regards
gunter



From wireless  Thu Sep  2 01:27:42 2004
From: wireless (Andy)
Date: Thu, 2 Sep 2004 09:27:42 +0100
Subject: PATCH: wired eapol receive/send
References: <20040831085838.GC28682@informatik.uni-rostock.de><20040902050815.GC7393@jm.kir.nu>
	<20040902065505.GE28682@informatik.uni-rostock.de>
Message-ID: <026801c490c6$b7445690$e200000a@int.madge.com>

> > Is there any particular reason for parsing DHCP packets?
> But iptables is layer 3 in ISO/OSI.

Why not use either the mac address filtering module for IP tables (man
iptables, search for mac-source), or better still, use ebtables
(http://ebtables.sourceforge.net) which provides layer 2 filtering
functionality (but needs kernel patches for kernel 2.4, but is in kernel
2.6)?  Maybe a .1x module for ebtables is the way to go?

Andy
wireless at windsorcarclub.co.uk
ENDOFMSG
----- Original Message ----- 
From: "Gunter Burchardt" <gbur at informatik.uni-rostock.de>
To: "Jouni Malinen" <jkmaline at cc.hut.fi>
Cc: <hostap at shmoo.com>
Sent: Thursday, September 02, 2004 7:55 AM
Subject: Re: PATCH: wired eapol receive/send


> > > First patch to bring wired authentication with hostapd alive. This
> > > patch enables hostapd to send and recieve eapol frames via ethernet.
> > > Furthermore sta detection is implemented via dhcp for station which
> > > didn't send eapol-start (like winxp supplicant).
> >
> > Thanks! I haven't yet merged this in, but couple of quick
> > comments/questions first..
>
>
> > Is there any particular reason for parsing DHCP packets? One option
> > would be to open packet socket on the same interface with Linux Socket
> > filter to capture the packets and then take the layer 2 address from
> > them. Then again, this may not end up being much simpler. Eventually, I
> > would assume this could be replaced with something like iptables
> > firewall queueing packets from unknown MAC addresses for user space
> > processing and all devices would be noticed whenever they send the first
> > packet, no matter whether it is DHCP or something else, i.e., static IP
> > and non-IPv4 hosts would also be processed.
>
> Sounds good. I will check it. But iptables has no real api. In
> documentation iptables_restore is recommended as api. I've written a
> function that starts iptables_restore, puts the iptables rules to its
> stdin and parses stdout to check if it was successfull. I'm realy
> unhappy about this. But at the moment i see no other way.
>
> I would like to use iptables for port authorization. Adding some rules
> for authorized stations that patckets from this station where acceptet.
> But iptables is layer 3 in ISO/OSI. Only ip address is known. Ok you
> can match to incomming mac address. But there is no way to controll
> packets sent to the station without knowlege of the ip address of this
> station.
>
> Another way is that only one station can connect to a port (device).
> Together with vlan-devices and a vlan enabled switch it would be a
> secure way.
>
> Is accounting using iptables ok? I will not count all packets in user
> space (to slow) and i will not hack into device drivers.
>
> > > In ieee802_11.c auth_get_sta() is implemented. I think this function
> > > should move to hostapd.c . There are no 802.11 thinks in this
function.
> > > At the moment i declared this function to extern.
> >
> > I would agree on moving the function, although I would probably move it
> > to sta_info.c, not hostapd.c. In addition, the function should be
> > renamed to something like ap_sta_add().
>
> Should i do it or you?
>
> regards
> gunter
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From masustec  Thu Sep  2 03:23:56 2004
From: masustec (=?iso-8859-1?q?Mr=20Asustec?=)
Date: Thu, 2 Sep 2004 11:23:56 +0100 (BST)
Subject: Broadcast/multicast ack?
Message-ID: <20040902102356.82525.qmail@web25206.mail.ukl.yahoo.com>


I observed prism2_tx_ev called after
broadcast/multicast frames in adhoc network. As I know
the broadcast frames should not be acknowledged
according to standard. Is it possible to switch the
driver to acknowledge unicast frames only?

Regards,
Asustec


	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com



From masustec  Thu Sep  2 03:25:32 2004
From: masustec (=?iso-8859-1?q?Mr=20Asustec?=)
Date: Thu, 2 Sep 2004 11:25:32 +0100 (BST)
Subject: Broadcast/multicast ack?
Message-ID: <20040902102532.73105.qmail@web25207.mail.ukl.yahoo.com>


I observed prism2_tx_ev called after
broadcast/multicast frames in adhoc network. As I know
the broadcast frames should not be acknowledged
according to standard. Is it possible to switch the
driver to acknowledge unicast frames only?

Regards,
Asustec


	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com



From gbur  Thu Sep  2 03:30:27 2004
From: gbur (Gunter Burchardt)
Date: Thu, 2 Sep 2004 12:30:27 +0200
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040902050815.GC7393@jm.kir.nu>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
	<20040902050815.GC7393@jm.kir.nu>
Message-ID: <20040902103027.GF28682@informatik.uni-rostock.de>

> Is there any particular reason for parsing DHCP packets? One option
> would be to open packet socket on the same interface with Linux Socket
> filter to capture the packets and then take the layer 2 address from
> them. Then again, this may not end up being much simpler. Eventually, I
> would assume this could be replaced with something like iptables
> firewall queueing packets from unknown MAC addresses for user space
> processing and all devices would be noticed whenever they send the first
> packet, no matter whether it is DHCP or something else, i.e., static IP
> and non-IPv4 hosts would also be processed.

Iptables is the wrong place doing it. If you define a user process
doing packet filtering with target QUEUE you can match only IPV4 or
IPV6 packets. There is no way to match both classes or layer 2
packets! So you will NOT see dhcp packets in userspace process!

regards
gunter



From wouter  Thu Sep  2 04:23:16 2004
From: wouter (Wouter de Jong)
Date: Thu, 2 Sep 2004 13:23:16 +0200
Subject: Atheros 5212 and WPA issues
In-Reply-To: <20040902014248.GA7393@jm.kir.nu>
References: <20040901081648.GB87052@widexs.nl>
	<20040901140528.GB7162@jm.kir.nu> <20040901160636.GA470@widexs.nl>
	<1094066053.24204.3126.camel@gandalf.uninova.pt>
	<20040902014248.GA7393@jm.kir.nu>
Message-ID: <20040902112316.GD25559@widexs.nl>

On Wed, Sep 01, 2004 at 06:42:48PM -0700, Jouni Malinen wrote:

Hi Jouni,

> The configuration file itself looked fine, something else is going wrong
> in somewhat odd way.

Do you have any debugging hints I can use to provide you with as much
info as possible?


Greetings,

-- 
WideXS                          http://www.widexs.nl
Wouter de Jong                  System-Administrator
Tel +31 (0)23 5698070           Fax +31 (0)23 5698099
Bijlmermeerstraat 62,           2131 HG  HOOFDDORP, NL



From steffen  Thu Sep  2 07:13:33 2004
From: steffen (Steffen Pfendtner)
Date: Thu, 2 Sep 2004 16:13:33 +0200 (CEST)
Subject: Collision detection and injection with wlan0ap
In-Reply-To: <20040902112316.GD25559@widexs.nl>
References: <20040901081648.GB87052@widexs.nl>
	<20040901140528.GB7162@jm.kir.nu> <20040901160636.GA470@widexs.nl>
	<1094066053.24204.3126.camel@gandalf.uninova.pt>
	<20040902014248.GA7393@jm.kir.nu> <20040902112316.GD25559@widexs.nl>
Message-ID: <Pine.NEB.4.60.0409021608450.16673@alpha.wh-stuttgart.de>

Hi,

Just a simple stupid question ;)
When I use the host ap wlan0ap interface to inject a packet into the 
"domain" of an other access point will it just send immediatly or does 
it wait until the channel it clear to send?

I guess it's just sending, any way to wait until the channel is clear?

Greetings,
Steffen

--
<steffen at wh-netz.de>
GPG Key fingerprint = DF91 11BB 498F 573B 8002  6E0B 3AE3 FF88 EADD B3BC



From zhangho  Thu Sep  2 10:08:05 2004
From: zhangho (Hongwei Zhang)
Date: Thu, 02 Sep 2004 13:08:05 -0400
Subject: iwconfig does not always work ...
Message-ID: <41375375.5050706@cis.ohio-state.edu>

Hi,

I am using hostap version 0.1.3 with linux kernel 2.4.19. I found that 
sometimes iwconfig is unable to setup frequency, channel correctly 
(i.e., iwconfig is uanble to change the essid, the frequency, etc.).

I wonder what may be the cause for this? Any information or pointers to 
information on this issue would be greatly appreciated.

Thanks,

Hongwei





From drew  Thu Sep  2 12:24:13 2004
From: drew (Drew)
Date: Thu, 02 Sep 2004 12:24:13 -0700
Subject: s1010704.hex firmware? 
Message-ID: <4137735D.9080901@wirelessanarchy.com>

I have a Senao 2011cd ext2 card, with a NICID of 8003, with firmware of 
primary 0.3.0 and station of 1.7.1, and I can't find anything newer.

The 8003's require hex files starting with p1 and s1, so I assume I need 
something named s1010704.hex (or newer). I've already tried looking 
through all the files here: http://linux.junsun.net/intersil-prism/ but 
it seems that 8003's must be rare, as there aren't many p1 or s1 
firmwares there. Anyone have any leads on where I could find them?

Thanks,
Drew





From kshogan  Thu Sep  2 14:18:20 2004
From: kshogan (Kelly Hogan)
Date: Thu, 02 Sep 2004 15:18:20 -0600
Subject: 0.2.4 deatuhentication reason_code=3
Message-ID: <1094159900.4973.132.camel@m2.linora.com>

Jouni,

We recently upgraded to 0.2.4 on soekris with a dual radio
configuration.  On our master radio, we are getting deauthentication
reason_code=3 from nodes with signals of -93/-70 which seems odd.

They then never re-authenticate unless we reboot the client side, then
they last for only a few minutes.  

Ideas?  Should we downgrade to 0.1.3?

Thanks
KH




From quintusl  Thu Sep  2 17:04:02 2004
From: quintusl (Tim Leung)
Date: Fri, 3 Sep 2004 08:04:02 +0800 (HKT)
Subject: hostap driver commercial support?
Message-ID: <1817.64.156.212.29.1094169842.squirrel@64.156.212.29>

Hello,

I am new to this list.
Could I know if, apart from Wi-Fi card vendors, there
is any commercial support for the hostap driver available?

Regards,
Tim Leung



From snai8255  Thu Sep  2 18:51:01 2004
From: snai8255 (snai8255 at mail.usyd.edu.au)
Date: Fri,  3 Sep 2004 11:51:01 +1000
Subject: wep challenge?
Message-ID: <1094176261.4137ce05299a5@www-mail.usyd.edu.au>

hii guys;

i was wondering if hostap-0.2.4 supports managed mode?if it does ,could someone please enlighten me
as to where the driver accepts the wep challenge from ap (auth_transaction=2) and replies with the
encrypted wep challenge (auth_transaction=3).

any comments will be highly appreciated :)

regards
saji

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From kchebrol  Thu Sep  2 19:14:17 2004
From: kchebrol (kameswari Chebrolu)
Date: Thu, 2 Sep 2004 19:14:17 -0700 (PDT)
Subject: CnfRcvCrcError: Passing errored packets to driver in ad-hoc mode
Message-ID: <20040903021417.50936.qmail@web41902.mail.yahoo.com>

Hello,
I am trying to get errored packets up to the driver to
collect some statistics while in ad-hoc mode. I set
the CnfRCvCRCerror RID to 1 but I still have no luck.
Are there other dependencies (I did ensure packets
were not being dropped in  hostap_rx_skb() because the
mode is not monitor)? I don't think errored packets
are even being placed in the queue.
Can some one please help...
thanks,
K.


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 



From jkmaline  Thu Sep  2 19:26:22 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 2 Sep 2004 19:26:22 -0700
Subject: wep challenge?
In-Reply-To: <1094176261.4137ce05299a5@www-mail.usyd.edu.au>
References: <1094176261.4137ce05299a5@www-mail.usyd.edu.au>
Message-ID: <20040903022622.GA7370@jm.kir.nu>

On Fri, Sep 03, 2004 at 11:51:01AM +1000, snai8255 at mail.usyd.edu.au wrote:

> i was wondering if hostap-0.2.4 supports managed mode?

Yes.

> if it does ,could someone please enlighten me as to where the driver accepts the wep challenge from ap (auth_transaction=2) and replies with the
> encrypted wep challenge (auth_transaction=3).

The driver does not.. This is implemented in the Prism2 station
firmware.

-- 
Jouni Malinen                                            PGP id EFC895FA



From rocci  Thu Sep  2 21:08:55 2004
From: rocci (Rocci)
Date: Fri, 03 Sep 2004 14:08:55 +1000
Subject: Configuring PEAP w/ ndiswrapper
In-Reply-To: <1093824169.6691.16.camel@localhost>
References: <1093824169.6691.16.camel@localhost>
Message-ID: <4137EE57.40003@rocknetworks.net.au>

Richard Laager wrote:

>My university uses 802.11x authentication with PEAP and MSCHAP (v2, I
>assume). The ESSID on the access points is the same across the
>university, and the access points broadcast the ESSID. IP addresses are
>handed out via DHCP. I'm using ndiswrapper with the bcmwl5a driver.
>
>I can connect to unsecured access points with no trouble. I've tried a
>number of configurations of Xsupplicant and wpa_supplicant with no luck.
>wpa_supplicant at least mentions ndiswrapper in the documentation, so I
>think it's my best shot at this point.
>
>The authentication credentials are simply my username and password.
>There are no client certificates used. I do not currently have the
>server certificate. I may be able to get the server certificate if it's
>required, but I'd prefer not to have to hassle the network
>administrators: Non-Windows configurations are allowed, but unsupported.
>
>My current wpa_supplicant configuration (for wpa_supplicant 0.2.4) is as
>follows:
>
>ctrl_interface=/var/run/wpa_supplicant
>ctrl_interface_group=wheel
>network={
>        ssid="UMC"
>        scan_ssid=0
>        key_mgmt=IEEE8021X
>        eap=PEAP
>        identity="laag0007 at umcrookston.edu"
>        password="my_password_goes_here"
>        ca_cert="/etc/cert/ca.pem"
>        eapol_flags=3
>        phase1="peaplabel=0"
>        phase2="auth=MSCHAPV2"
>}
>
>If I run the following command:
>wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -d
>
>I get the following debug output. The authentication appears to timeout
>and loop over and over until I hit Ctrl-C. I've let it loop once here
>before stopping it.
>
>Configuration file '/etc/wpa_supplicant.conf' ->
>'/etc/wpa_supplicant.conf'
>Reading configuration file '/etc/wpa_supplicant.conf'
>ctrl_interface='/var/run/wpa_supplicant'
>ctrl_interface_group=10 (from group name 'wheel')
>Priority group 0
>   id=0 ssid='UMC'
>EAPOL: SUPP_PAE entering state DISCONNECTED
>EAPOL: KEY_RX entering state NO_KEY_RECEIVE
>EAPOL: SUPP_BE entering state INITIALIZE
>EAP: EAP entering state DISABLED
>EAPOL: External notification - portEnabled=0
>EAPOL: External notification - portValid=0
>Setting scan request: 0 sec 100000 usec
>Starting AP scan (broadcast SSID)
>Scan timeout - try to get results
>Received 148 bytes of scan results (1 BSSes)
>Scan results: 1
>Selecting BSS from priority group 0
>0: 00:0b:5f:7c:1e:c5 ssid='UMC' wpa_ie_len=0 rsn_ie_len=0
>   skip - no WPA/RSN IE
>   selected non-WPA AP 00:0b:5f:7c:1e:c5 ssid='UMC'
>Trying to associate with 00:0b:5f:7c:1e:c5 (SSID='UMC' freq=2452 MHz)
>Cancelling scan request
>Setting authentication timeout: 5 sec 0 usec
>EAPOL: External notification - portControl=Auto
>Authentication with 00:00:00:00:00:00 timed out.
>Setting scan request: 0 sec 0 usec
>Starting AP scan (broadcast SSID)
>Scan timeout - try to get results
>Received 148 bytes of scan results (1 BSSes)
>Scan results: 1
>Selecting BSS from priority group 0
>0: 00:0b:5f:7c:1e:c5 ssid='UMC' wpa_ie_len=0 rsn_ie_len=0
>   skip - no WPA/RSN IE
>   selected non-WPA AP 00:0b:5f:7c:1e:c5 ssid='UMC'
>Trying to associate with 00:0b:5f:7c:1e:c5 (SSID='UMC' freq=2452 MHz)
>Cancelling scan request
>Setting authentication timeout: 5 sec 0 usec
>EAPOL: External notification - portControl=Auto
>Signal 2 received - terminating
>EAPOL: External notification - portEnabled=0
>EAPOL: External notification - portValid=0
>
>Is there a step-by-step guide to getting 802.11x authentication working
>in such a configuration? If not, can anyone point to my mistakes?
>
>I'm a very experience Linux administrator, but I'm a total newbie when
>it comes to configuring wireless authentication. If I've omitted any
>important information, please let me know.
>
>Thanks,
>Richard Laager
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>  
>
Hi,
I realise that this is a late response to your question but I've had the 
same problem and only recently managed to resolve it.
I am using wpa_supplicant with mad_wifi (Atheros chip driver) which 
works perfectly fine.
I too can access my university's wireless access points but the problem 
I have is obtaining the ca certificate.
My uni also uses TKIP+PEAP+MSCHAPv2 and login with user/password network 
access.
My uni IT services division does not support Linux :( ,only MacOS & 
Windose, so here's what I did:
I used a windows XP PC to access the network and obtain the ca 
certificate. Then I copied the windows ca certificate onto my linux 
partition.
Then converted that certificate using openssl and put it in the right 
place as per the wpa_supplicant.conf file. On windows the certificaate 
is a .cer file and I converted it to a .pem file as follows:

openssl x509 -inform der -in university_certificate.cer -out 
university_certificate.pem

Then edited the line in the config file for wpa_supplicant as: 
ca_cert="/etc/cert/university_certificate.pem"
And I managed to authenticate via wpa successfully and then restarted my 
network interface to pick up an IP from DHCP and yeeehaaaaaa I am now on 
the network at Uni.

Hope this helps :)

- Rocci



From dteed  Fri Sep  3 03:06:07 2004
From: dteed (Donald Teed)
Date: Fri, 3 Sep 2004 07:06:07 -0300 (ADT)
Subject: Configuring PEAP w/ ndiswrapper
In-Reply-To: <4137EE57.40003@rocknetworks.net.au>
References: <1093824169.6691.16.camel@localhost>
	<4137EE57.40003@rocknetworks.net.au>
Message-ID: <Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>


One difference is that Richard is using a different wireless
device - the broadcom based one.

Some Mac users on our campus found it was possible to get
wpa_supplicant working with TTLS rather than PEAP - and thus I discovered
we do not only work with PEAP.  I've tried TTLS as well,
with a certificate (PEAP doesn't require a certificate,
but TTLS does - as I've been told) and still the broadcom
will not work with a broadcasting SSID and ndiswrapper .10 .

Broadcom is said to work, but I've yet to hear of my
specific device (truemobile 1350) being reported a success
with wpa_supplicant.  Based on how we have seen a world
of difference in ndiswrapper stability between the
truemobile 1300 and 1350, I'm ready to assume that we can't 
just say "broadcom works" because the same brand and series
chipset was a sucess for someone else.  I don't think
anyone has had a sucess in wpa_supplicant with any
broadcom mini-PCI component (please correct me if I'm wrong).

The way I obtained the CA Certificate is to visit the
web server on the AD server.  I think the default is
http://yourservername/certsrv
It allows you to download a number of certificate related files.

--Donald Teed


On Fri, 3 Sep 2004, Rocci wrote:

> Richard Laager wrote:
>
>> My university uses 802.11x authentication with PEAP and MSCHAP (v2, I
>> assume). The ESSID on the access points is the same across the
>> university, and the access points broadcast the ESSID. IP addresses are
>> handed out via DHCP. I'm using ndiswrapper with the bcmwl5a driver.
>> 
>> I can connect to unsecured access points with no trouble. I've tried a
>> number of configurations of Xsupplicant and wpa_supplicant with no luck.
>> wpa_supplicant at least mentions ndiswrapper in the documentation, so I
>> think it's my best shot at this point.
>> 
>> The authentication credentials are simply my username and password.
>> There are no client certificates used. I do not currently have the
>> server certificate. I may be able to get the server certificate if it's
>> required, but I'd prefer not to have to hassle the network
>> administrators: Non-Windows configurations are allowed, but unsupported.
>> 
>> My current wpa_supplicant configuration (for wpa_supplicant 0.2.4) is as
>> follows:
>> 
>> ctrl_interface=/var/run/wpa_supplicant
>> ctrl_interface_group=wheel
>> network={
>> ssid="UMC"
>> scan_ssid=0
>> key_mgmt=IEEE8021X
>> eap=PEAP
>> identity="laag0007 at umcrookston.edu"
>> password="my_password_goes_here"
>> ca_cert="/etc/cert/ca.pem"
>> eapol_flags=3
>> phase1="peaplabel=0"
>> phase2="auth=MSCHAPV2"
>> }
>> 
>> If I run the following command:
>> wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -d
>> 
>> I get the following debug output. The authentication appears to timeout
>> and loop over and over until I hit Ctrl-C. I've let it loop once here
>> before stopping it.
>> 
>> Configuration file '/etc/wpa_supplicant.conf' ->
>> '/etc/wpa_supplicant.conf'
>> Reading configuration file '/etc/wpa_supplicant.conf'
>> ctrl_interface='/var/run/wpa_supplicant'
>> ctrl_interface_group=10 (from group name 'wheel')
>> Priority group 0
>>   id=0 ssid='UMC'
>> EAPOL: SUPP_PAE entering state DISCONNECTED
>> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
>> EAPOL: SUPP_BE entering state INITIALIZE
>> EAP: EAP entering state DISABLED
>> EAPOL: External notification - portEnabled=0
>> EAPOL: External notification - portValid=0
>> Setting scan request: 0 sec 100000 usec
>> Starting AP scan (broadcast SSID)
>> Scan timeout - try to get results
>> Received 148 bytes of scan results (1 BSSes)
>> Scan results: 1
>> Selecting BSS from priority group 0
>> 0: 00:0b:5f:7c:1e:c5 ssid='UMC' wpa_ie_len=0 rsn_ie_len=0
>> skip - no WPA/RSN IE
>> selected non-WPA AP 00:0b:5f:7c:1e:c5 ssid='UMC'
>> Trying to associate with 00:0b:5f:7c:1e:c5 (SSID='UMC' freq=2452 MHz)
>> Cancelling scan request
>> Setting authentication timeout: 5 sec 0 usec
>> EAPOL: External notification - portControl=Auto
>> Authentication with 00:00:00:00:00:00 timed out.
>> Setting scan request: 0 sec 0 usec
>> Starting AP scan (broadcast SSID)
>> Scan timeout - try to get results
>> Received 148 bytes of scan results (1 BSSes)
>> Scan results: 1
>> Selecting BSS from priority group 0
>> 0: 00:0b:5f:7c:1e:c5 ssid='UMC' wpa_ie_len=0 rsn_ie_len=0
>> skip - no WPA/RSN IE
>> selected non-WPA AP 00:0b:5f:7c:1e:c5 ssid='UMC'
>> Trying to associate with 00:0b:5f:7c:1e:c5 (SSID='UMC' freq=2452 MHz)
>> Cancelling scan request
>> Setting authentication timeout: 5 sec 0 usec
>> EAPOL: External notification - portControl=Auto
>> Signal 2 received - terminating
>> EAPOL: External notification - portEnabled=0
>> EAPOL: External notification - portValid=0
>> 
>> Is there a step-by-step guide to getting 802.11x authentication working
>> in such a configuration? If not, can anyone point to my mistakes?
>> 
>> I'm a very experience Linux administrator, but I'm a total newbie when
>> it comes to configuring wireless authentication. If I've omitted any
>> important information, please let me know.
>> 
>> Thanks,
>> Richard Laager
>> 
>> 
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>> 
>> 
> Hi,
> I realise that this is a late response to your question but I've had the same 
> problem and only recently managed to resolve it.
> I am using wpa_supplicant with mad_wifi (Atheros chip driver) which works 
> perfectly fine.
> I too can access my university's wireless access points but the problem I 
> have is obtaining the ca certificate.
> My uni also uses TKIP+PEAP+MSCHAPv2 and login with user/password network 
> access.
> My uni IT services division does not support Linux :( ,only MacOS & Windose, 
> so here's what I did:
> I used a windows XP PC to access the network and obtain the ca certificate. 
> Then I copied the windows ca certificate onto my linux partition.
> Then converted that certificate using openssl and put it in the right place 
> as per the wpa_supplicant.conf file. On windows the certificaate is a .cer 
> file and I converted it to a .pem file as follows:
>
> openssl x509 -inform der -in university_certificate.cer -out 
> university_certificate.pem
>
> Then edited the line in the config file for wpa_supplicant as: 
> ca_cert="/etc/cert/university_certificate.pem"
> And I managed to authenticate via wpa successfully and then restarted my 
> network interface to pick up an IP from DHCP and yeeehaaaaaa I am now on the 
> network at Uni.
>
> Hope this helps :)
>
> - Rocci
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
>



From ged  Fri Sep  3 05:45:34 2004
From: ged (Ged Haywood)
Date: Fri, 3 Sep 2004 13:45:34 +0100 (BST)
Subject: s1010704.hex firmware?
In-Reply-To: <20040903051451.1599B2C1C3@mail.iocaine.com>
References: <20040903051451.1599B2C1C3@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409031338240.21139@mail3.jubileegroup.co.uk>

Hi there,

On Thu, 2 Sep 2004 Drew wrote:

> I have a Senao 2011cd ext2 card, with a NICID of 8003, with firmware of
> primary 0.3.0 and station of 1.7.1, and I can't find anything newer.
>
> The 8003's require hex files starting with p1 and s1, so I assume I need
> something named s1010704.hex (or newer). I've already tried looking
> through all the files here: http://linux.junsun.net/intersil-prism/

According to

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

you should be able to use s1010409.hex shouldn't you?

For example

http://wwwcip.informatik.uni-erlangen.de/~simigern/wlan/?C=N;O=A

73,
Ged.



From jkmaline  Fri Sep  3 08:13:34 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 3 Sep 2004 08:13:34 -0700
Subject: Configuring PEAP w/ ndiswrapper
In-Reply-To: <Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>
References: <1093824169.6691.16.camel@localhost>
	<4137EE57.40003@rocknetworks.net.au>
	<Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>
Message-ID: <20040903151333.GA7366@jm.kir.nu>

On Fri, Sep 03, 2004 at 07:06:07AM -0300, Donald Teed wrote:

> Some Mac users on our campus found it was possible to get
> wpa_supplicant working with TTLS rather than PEAP - and thus I discovered
> we do not only work with PEAP.  I've tried TTLS as well,
> with a certificate (PEAP doesn't require a certificate,
> but TTLS does - as I've been told) and still the broadcom
> will not work with a broadcasting SSID and ndiswrapper .10 .

Both EAP-PEAP and EAP-TTLS require CA certificate to be configured to
avoid man-in-the-middle attacks. There's not much difference in that
sense with these methods. Yes, you can test either one without the
certificate and the authentication should succeed, but it is just not
secure to do so. Anyway, I don't think the problems with Broadcom card
and ndiswrapper have much to do with the EAP method since most reports I
have seen so far indicate that either the IEEE 802.11 association is not
succeeding or EAPOL packets are not being received at all.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Sep  3 08:16:17 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 3 Sep 2004 08:16:17 -0700
Subject: s1010704.hex firmware?
In-Reply-To: <4137735D.9080901@wirelessanarchy.com>
References: <4137735D.9080901@wirelessanarchy.com>
Message-ID: <20040903151617.GB7366@jm.kir.nu>

On Thu, Sep 02, 2004 at 12:24:13PM -0700, Drew wrote:

> I have a Senao 2011cd ext2 card, with a NICID of 8003, with firmware of 
> primary 0.3.0 and station of 1.7.1, and I can't find anything newer.

What makes you believe that a newer firmware version has been released
for that old hfa3841-based card?

-- 
Jouni Malinen                                            PGP id EFC895FA



From ian.monroe  Fri Sep  3 09:58:04 2004
From: ian.monroe (Ian Monroe)
Date: Fri, 3 Sep 2004 11:58:04 -0500
Subject: 520 revision E fails to bring up wlan0
Message-ID: <f680fec50409030958507216c3@mail.gmail.com>

I have the DWL-520 revision E wireless card. Its the card that
requires a firmware download at every boot I understand. I have gotten
it to work in Windows. I was trying to follow the directions at:
http://home.columbus.rr.com/andrewbarr/dwl520e1.html
...but modprobe does not bring up wlan0 so I don't even get the chance
to install the firmware using hostap_fw_load.

I use Gentoo and I installed the 0.2.4 drivers and utils.

# dmesg -c
<snip>
# modprobe hostap_pci
# dmesg
hostap_crypt: registered algorithm 'NULL'
hostap_pci: 0.1.3 - 2004-02-08 (Jouni Malinen <jkmaline at cc.hut.fi>)
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17
hostap_pci: Registered netdevice wlan0
wlan0: COR sreset timeout
wlan0: hfa384x_cmd - timeout - reg=0xc832
hostap_pci: first command failed - is the card compatible?
hostap_pci: hardware initialization failed
# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.
# hostap_fw_load wlan0
Host AP driver data for device wlan0 not found in procfs.
# ip link set dev wlan0 up
SIOCGIFFLAGS: No such device
# lsmod
Module                  Size  Used by
hostap_pci             57176  0
hostap                102216  1 hostap_pci
<snip>

Any ideas?



From capacity77  Fri Sep  3 09:17:24 2004
From: capacity77 (capacity77 at tin.it)
Date: Fri, 3 Sep 2004 18:17:24 +0200
Subject: HostAP help
Message-ID: <411971330000F802@ims6a.cp.tin.it>

Hi !
I'm working at a project concerning wireless applications and I have to
use HostAP to create a LAN. But I have to find an answer to some question,
for example, once I've installed HostAP on 2 laptops, they will see each
other just like
in a LAN network but how can each one recognize the other? What kind of
identification is used?
And more, where I can find information like these and detailed informations
about the know-how on what HostAP does or doesn't do without trying to read
the code?
Thanx a lot!
capacity





From ian.monroe  Fri Sep  3 11:31:23 2004
From: ian.monroe (Ian Monroe)
Date: Fri, 3 Sep 2004 13:31:23 -0500
Subject: 520 revision E fails to bring up wlan0
In-Reply-To: <f680fec50409030958507216c3@mail.gmail.com>
References: <f680fec50409030958507216c3@mail.gmail.com>
Message-ID: <f680fec504090311317f30d2@mail.gmail.com>

Turns out I was still using the older hostap, its working now with the
new drivers. Just figuring out how to setup the startup files now.

Sorry for the unnecessary traffic,
Ian

On Fri, 3 Sep 2004 11:58:04 -0500, Ian Monroe <ian.monroe at gmail.com> wrote:
> I have the DWL-520 revision E wireless card. Its the card that
...



From giri  Fri Sep  3 12:57:06 2004
From: giri (Giridhar Pemmasani)
Date: Fri, 03 Sep 2004 15:57:06 -0400
Subject: Configuring PEAP w/ ndiswrapper
In-Reply-To: <Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>
References: <1093824169.6691.16.camel@localhost>
	<4137EE57.40003@rocknetworks.net.au>
	<Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>
Message-ID: <20040903200114.7944177A5B@mail.lmc.cs.sunysb.edu>

On Fri, 3 Sep 2004 07:06:07 -0300 (ADT), Donald Teed <dteed at artistic.ca> said:

  Donald> with wpa_supplicant.  Based on how we have seen a world of
  Donald> difference in ndiswrapper stability between the truemobile
  Donald> 1300 and 1350, I'm ready to assume that we can't just say
  Donald> "broadcom works" because the same brand and series chipset

Again, ndiswrapper doesn't talk to the hardware. It is only a wrapper
for Windows functions. And yet again, there is no point bringing up
ndiswrapper issues on this list! Since you seem to follow this list,
let me clarify: If you followed ndiswrapper-general list, someone
mentioned that 1350 works but not when booted on battery. But
ndiswrapper can't address that problem.

  Donald> was a sucess for someone else.  I don't think anyone has had
  Donald> a sucess in wpa_supplicant with any broadcom mini-PCI
  Donald> component (please correct me if I'm wrong).

See http://ndiswrapper.sourceforge.net/wiki/index.php/List for a
number of Boradcom cards working with WPA.

  Jouni> have seen so far indicate that either the IEEE 802.11
  Jouni> association is not succeeding or EAPOL packets are not being
  Jouni> received at all.

I have encountered this problem myself with specific cards and
routers. After a bit of trial and error, I found that if the transmit
rates of card and router don't match, either the card won't see EAPOL
packets (I didn't use any sniffer, so I may be wrong about the reason)
or the handshake won't complete (it won't see response for 2nd step in
4-way handshake). So far, I have been able to get around this problem
by forcing 802.11b speeds in NDIS settings (different cards have
different ways of doing it, so unfortunately you have to figure out
how to do that by looking at the INF file). 

-- 
Giri



From ben.hart  Fri Sep  3 13:29:57 2004
From: ben.hart (Ben Hart)
Date: Fri, 3 Sep 2004 13:29:57 -0700
Subject: modprobe hostap_pci crash - dwl-520 e1
In-Reply-To: <e4aa44ef04090313141e7dd20b@mail.gmail.com>
References: <e4aa44ef04082615146930599f@mail.gmail.com>
	<e4aa44ef0408291550358878c2@mail.gmail.com>
	<d9823ac1040829234117a7429e@mail.gmail.com>
	<e4aa44ef04090313141e7dd20b@mail.gmail.com>
Message-ID: <e4aa44ef04090313295e5d25b@mail.gmail.com>

Thanks for your help...

I have tried all of your suggestions - but no luck.  This crashing
issue doesn't seem to be cold or warm boot related. I have also made
sure the modules are unloaded properly - but no luck there either.

Alas, the evil dwl-520 and its fry's mail-in rebate may win this battle.

-ben


On Sun, 29 Aug 2004 23:41:03 -0700, Ka-Hing Cheung <kahing at gmail.com> wrote:
> On Sun, 29 Aug 2004 22:50:21 +0000, Ben Hart <ben.hart at gmail.com> wrote:
> > Hi,
> >
> > I have a DWL-520 E1 card and have tried following Andrew Barr's "Using
> > the DWL-520 rev. E1 with HostAP"
> > <http://home.columbus.rr.com/andrewbarr/dwl520e1.html> instructions to
> > get the card up and running.
> >
> >
> > ::wham:: The system completely freezes up.  I can't ssh in, switch to
> > a different tty or anything.  complete crash.  After a reboot all is
> > fine but try again and the same will happen.
>
> I have the same card, and had the same problem. Basically if you
> didn't do a clean module unload, and you reboot, the system will crash
> the next time you load the module. Solution is do a cold reboot
> (shutdown and then start up again).
>
> I also found out that sometimes (I am not sure if it's always yet), if
> you unload modules and load them again, that will bring down the
> system as well. Also last time (the onlyt time) I tried to use kismet
> with it, and that also results in a crash.
>
> If you have another card, or another revision of the same card, I
> highly recommend you use that instead to save yourself some time.
>
> -khc
>



From dteed  Fri Sep  3 17:56:17 2004
From: dteed (Donald Teed)
Date: Fri, 3 Sep 2004 21:56:17 -0300 (ADT)
Subject: Configuring PEAP w/ ndiswrapper
In-Reply-To: <20040903200114.7944177A5B@mail.lmc.cs.sunysb.edu>
References: <1093824169.6691.16.camel@localhost>
	<4137EE57.40003@rocknetworks.net.au>
	<Pine.LNX.4.60.0409030653360.3189@artistic.localdomain.domain>
	<20040903200114.7944177A5B@mail.lmc.cs.sunysb.edu>
Message-ID: <Pine.LNX.4.60.0409032145030.11408@artistic.localdomain.domain>

On Fri, 3 Sep 2004, Giridhar Pemmasani wrote:

> On Fri, 3 Sep 2004 07:06:07 -0300 (ADT), Donald Teed <dteed at artistic.ca> said:
>
>  Donald> with wpa_supplicant.  Based on how we have seen a world of
>  Donald> difference in ndiswrapper stability between the truemobile
>  Donald> 1300 and 1350, I'm ready to assume that we can't just say
>  Donald> "broadcom works" because the same brand and series chipset
>
> Again, ndiswrapper doesn't talk to the hardware. It is only a wrapper
> for Windows functions. And yet again, there is no point bringing up
> ndiswrapper issues on this list! Since you seem to follow this list,
> let me clarify: If you followed ndiswrapper-general list, someone
> mentioned that 1350 works but not when booted on battery. But
> ndiswrapper can't address that problem.

If you read my comment carefully, in context, you'll see that
I mention this merely as an example of a case where calling it
"broadcom" or even the vendor and device ID, isn't enough
to identify the hardware.  This list and ndiswrapper list
are peppered with too many reports (e.g. "broadcom works for me")
that treat these like they are all alike, while I have proof
that the rev number can be very significant.  That degree of
detail is missing in these reports of what works, including
those on the web site you listed (sometimes there, sometimes not).

I did respond to another thread on ndiswrapper about this
but I guess your email is still not working.





From zen_hacker  Fri Sep  3 18:01:25 2004
From: zen_hacker (Brian Sturgill)
Date: Sat, 04 Sep 2004 01:01:25 +0000
Subject: HostAP help
Message-ID: <BAY13-F19lvtOW2ywUr0006acf0@hotmail.com>

Read the README files in the tarballs


>From: capacity77 at tin.it
>To: hostap at shmoo.com
>Subject: HostAP help
>Date: Fri, 3 Sep 2004 18:17:24 +0200
>
>Hi !
>I'm working at a project concerning wireless applications and I have to
>use HostAP to create a LAN. But I have to find an answer to some question,
>for example, once I've installed HostAP on 2 laptops, they will see each
>other just like
>in a LAN network but how can each one recognize the other? What kind of
>identification is used?
>And more, where I can find information like these and detailed informations
>about the know-how on what HostAP does or doesn't do without trying to read
>the code?
>Thanx a lot!
>capacity
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From kahing  Fri Sep  3 19:44:38 2004
From: kahing (Ka-Hing Cheung)
Date: Fri, 3 Sep 2004 19:44:38 -0700
Subject: modprobe hostap_pci crash
In-Reply-To: <e4aa44ef04090313141e7dd20b@mail.gmail.com>
References: <e4aa44ef04082615146930599f@mail.gmail.com>
	<e4aa44ef0408291550358878c2@mail.gmail.com>
	<d9823ac1040829234117a7429e@mail.gmail.com>
	<e4aa44ef04090313141e7dd20b@mail.gmail.com>
Message-ID: <d9823ac104090319446e57426@mail.gmail.com>

On Fri, 3 Sep 2004 13:14:40 -0700, Ben Hart <ben.hart at gmail.com> wrote:
> Thanks for your help...
> 
> I have tried all of your suggestions - but no luck.  This crashing
> issue doesn't seem to be cold or warm boot related. I have also made
> sure the modules are unloaded properly - but no luck there either.

Okay, at this point I am out of ideas, other than plug into another
PCI slot and see if that works.

> Alas, the evil fry's mail-in rebate may win this battle.

I am still waiting for my rebate from bestbuy.

-khc



From jim  Fri Sep  3 21:46:08 2004
From: jim (Jim Thompson)
Date: Fri, 3 Sep 2004 18:46:08 -1000
Subject: multiple aps one card
In-Reply-To: <20040831141607.15568.qmail@orodruin.tierramedia.org>
References: <20040831141607.15568.qmail@orodruin.tierramedia.org>
Message-ID: <567A8CB4-FE2D-11D8-9164-000A95AB7778@netgate.com>


On Aug 31, 2004, at 4:16 AM, fran wrote:

>
> is it posible to act like several APs at the same time in one card 
> (not like fakeap)?
> I wonder if it would be posible to simulate multiple APs at the same 
> time with one interface.

Couple different ways to do this, but its not really hostap-specific. 
Please contact me off-list.

Jim




From ndhegde  Sun Sep  5 13:29:33 2004
From: ndhegde (nikhil hegde)
Date: Sun, 5 Sep 2004 13:29:33 -0700 (PDT)
Subject: hostap0.2.4 on fedora core2 instalaion problems
Message-ID: <20040905202933.56471.qmail@web20825.mail.yahoo.com>

Hi all,
I am a beginner and am trying to install hostap driver
for fedora core on my PC.I went through the mailing
list and tried thsese things:
I started with 
* cp /boot/config-2.6.5-1.358
/usr/src/linux-2.6.5-1.358/.config
* I ran make in the directory where i have untarred
hostap driver(/home/nikhil/hostap-driver-0.2.4) and I
am getting this error:(Actually the list is huge but i
am cutting it short)

/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:818:
error: storage size of `rx_tasklet' isn't known
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:819:
error: storage size of `rx_list' isn't known
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:821:
error: storage size of `sta_tx_exc_tasklet' isn't
known
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:822:
error: storage size of `sta_tx_exc_list' isn't known
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_ap.h:65:
error: storage size of `tx_buf' isn't known
include/linux/proc_fs.h:210: warning:
`create_proc_read_entry' declared `static' but never
defined
make[2]: ***
[/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap.o]
Error 1
make[1]: ***
[/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules]
Error 

*If I did only "make menuconfig" instead of copying
the .config file from /boot then the steps "make and
make install" worked but modprobe hostap_plx gave me
an error something like:(I changed KERNELPATH and
modified EXTRAVERSION in tihs case)
    hostap.ko: Invalid module format
    hostap_plx.ko:invalid module format

The wireless card that I am using is prism2 chipset,
US robotics card. Could anyone please help me in this
regard?

thanks
Nikhil 




		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush



From jar  Sun Sep  5 13:38:55 2004
From: jar (jar)
Date: Sun, 05 Sep 2004 23:38:55 +0300
Subject: hostap0.2.4 on fedora core2 instalaion problems
In-Reply-To: <20040905202933.56471.qmail@web20825.mail.yahoo.com>
References: <20040905202933.56471.qmail@web20825.mail.yahoo.com>
Message-ID: <413B795F.6010702@pcuf.fi>

nikhil hegde wrote:

> Hi all,
> I am a beginner and am trying to install hostap driver
> for fedora core on my PC.I went through the mailing
> list and tried thsese things:
> I started with 
> * cp /boot/config-2.6.5-1.358
> /usr/src/linux-2.6.5-1.358/.config
> * I ran make in the directory where i have untarred
> hostap driver(/home/nikhil/hostap-driver-0.2.4) and I
> am getting this error:(Actually the list is huge but i
> am cutting it short)
> 
> /home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:818:
> error: storage size of `rx_tasklet' isn't known
> /home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:819:
> error: storage size of `rx_list' isn't known
> /home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:821:
> error: storage size of `sta_tx_exc_tasklet' isn't
> known
> /home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:822:
> error: storage size of `sta_tx_exc_list' isn't known
> /home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_ap.h:65:
> error: storage size of `tx_buf' isn't known
> include/linux/proc_fs.h:210: warning:
> `create_proc_read_entry' declared `static' but never
> defined
> make[2]: ***
> [/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap.o]
> Error 1
> make[1]: ***
> [/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules]
> Error 
> 
> *If I did only "make menuconfig" instead of copying
> the .config file from /boot then the steps "make and
> make install" worked but modprobe hostap_plx gave me
> an error something like:(I changed KERNELPATH and
> modified EXTRAVERSION in tihs case)
>     hostap.ko: Invalid module format
>     hostap_plx.ko:invalid module format
> 
> The wireless card that I am using is prism2 chipset,
> US robotics card. Could anyone please help me in this
> regard?

If your kernel is 2.6.5-1.358, just do:

1. untar the hostap-driver-0.2.4.tar.gz package
2. cd to the hostap-driver-0.2.4/ directory
3. run make: make KERNEL_PATH=/lib/modules/2.6.5-1.358/build

That's it

RB. Jar



From jhiller  Sun Sep  5 14:43:12 2004
From: jhiller (James B. Hiller)
Date: Sun, 5 Sep 2004 17:43:12 -0400 (EDT)
Subject: OT: linux-2.6.9-rc1 kernel bug reference (fwd)
Message-ID: <200409052143.i85LhCps003133@bassett.home.org>

Hi.

About a week ago, I put the email below and with subject as shown on the
list.  I just updated the bug referenced below to reflect that it is
invalid - has nothing whatever to do with the linux kernel Prism II PCI
driver.  Rather, seems to be an issue involving elements of netfilter.
I'll be redirecting information on it to an appropriate netfilter mailing
list.

Sorry for the noise, then and now.  Wanted to report my fault here so as
have a shot at closing the matter for anyone on this list who might have
taken an interest.

jbh

> 
> Those who use Prism II PCI cards (and possibly non-PCI cards) with the
> native linux kernel drivers (such as for other machines in their hostap-based
> LAN) might wish to review the following bug report URL before moving such
> machines to linux-2.6.9-rc1 or its successors, until a resolution is made:
> 
> http://bugme.osdl.org/show_bug.cgi?id=3306
> 
> jbh
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 




From snai8255  Sun Sep  5 21:31:43 2004
From: snai8255 (snai8255 at mail.usyd.edu.au)
Date: Mon,  6 Sep 2004 14:31:43 +1000
Subject: scanning in hostap
Message-ID: <1094445103.413be82f0fcb8@www-mail.usyd.edu.au>

hi guys;

i am using hostap-0.2.4,and want to scan for available networks.however everytime i get no scan
result.this is what i do:
-------------------------
[$root]iwlist wlan0 scan
wlan0    No scan results
-------------------------
i am sure there are many networks available however the scan returns with no result.does anyone know
of any tweaking i have to do,to get this working.

regards
saji




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From ndhegde  Sun Sep  5 22:07:47 2004
From: ndhegde (nikhil hegde)
Date: Sun, 5 Sep 2004 22:07:47 -0700 (PDT)
Subject: hostap0.2.4 on fedora core2 instalaion problems
In-Reply-To: <413B795F.6010702@pcuf.fi>
Message-ID: <20040906050747.40932.qmail@web20827.mail.yahoo.com>

Hi Jar,
Thanx a million for the help. I was finally able to
install hostap and it is up and running:-) 

regards
Nikhil



  
--- jar <jar at pcuf.fi> wrote:

> nikhil hegde wrote:
> 
> > Hi all,
> > I am a beginner and am trying to install hostap
> driver
> > for fedora core on my PC.I went through the
> mailing
> > list and tried thsese things:
> > I started with 
> > * cp /boot/config-2.6.5-1.358
> > /usr/src/linux-2.6.5-1.358/.config
> > * I ran make in the directory where i have
> untarred
> > hostap driver(/home/nikhil/hostap-driver-0.2.4)
> and I
> > am getting this error:(Actually the list is huge
> but i
> > am cutting it short)
> > 
> >
>
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:818:
> > error: storage size of `rx_tasklet' isn't known
> >
>
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:819:
> > error: storage size of `rx_list' isn't known
> >
>
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:821:
> > error: storage size of `sta_tx_exc_tasklet' isn't
> > known
> >
>
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_wlan.h:822:
> > error: storage size of `sta_tx_exc_list' isn't
> known
> >
>
/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap_ap.h:65:
> > error: storage size of `tx_buf' isn't known
> > include/linux/proc_fs.h:210: warning:
> > `create_proc_read_entry' declared `static' but
> never
> > defined
> > make[2]: ***
> >
>
[/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules/hostap.o]
> > Error 1
> > make[1]: ***
> >
>
[/home/wireless/meghadoot/hostap-driver-0.2.4/driver/modules]
> > Error 
> > 
> > *If I did only "make menuconfig" instead of
> copying
> > the .config file from /boot then the steps "make
> and
> > make install" worked but modprobe hostap_plx gave
> me
> > an error something like:(I changed KERNELPATH and
> > modified EXTRAVERSION in tihs case)
> >     hostap.ko: Invalid module format
> >     hostap_plx.ko:invalid module format
> > 
> > The wireless card that I am using is prism2
> chipset,
> > US robotics card. Could anyone please help me in
> this
> > regard?
> 
> If your kernel is 2.6.5-1.358, just do:
> 
> 1. untar the hostap-driver-0.2.4.tar.gz package
> 2. cd to the hostap-driver-0.2.4/ directory
> 3. run make: make
> KERNEL_PATH=/lib/modules/2.6.5-1.358/build
> 
> That's it
> 
> RB. Jar
> 



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 



From capacity77  Mon Sep  6 08:19:20 2004
From: capacity77 (capacity77 at tin.it)
Date: Mon, 6 Sep 2004 17:19:20 +0200
Subject: user identification
Message-ID: <411971330001184E@ims6a.cp.tin.it>

Hi there!
I'm trying to find out how HostAP treats the user identification. I'd like
to solve the problem on how I can provide and guarantee a certain QoS to
a user who moves in a network made up by laptops running HostAP. A sort
of hand off plus the QoS stuffs. And I need to know how HostAP recognize
a user.
Can you help me?
capacity





From gbur  Mon Sep  6 09:56:35 2004
From: gbur (Gunter Burchardt)
Date: Mon, 6 Sep 2004 18:56:35 +0200
Subject: user identification
In-Reply-To: <411971330001184E@ims6a.cp.tin.it>
References: <411971330001184E@ims6a.cp.tin.it>
Message-ID: <20040906165635.GG28682@informatik.uni-rostock.de>

> Hi there!
> I'm trying to find out how HostAP treats the user identification. I'd like
> to solve the problem on how I can provide and guarantee a certain QoS to
> a user who moves in a network made up by laptops running HostAP. A sort
> of hand off plus the QoS stuffs. And I need to know how HostAP recognize
> a user.

What did you mean with user identification? There is 802.1x to
recognize/authenticate a user. After it there is only the MAC address
with its keys (if WEP/WPA) to identify packets from/to the user. 

regards
gunter



From kshogan  Mon Sep  6 10:05:10 2004
From: kshogan (Kelly Hogan)
Date: Mon, 06 Sep 2004 11:05:10 -0600
Subject: Flashing prism2 PCMCIA cards with PCI Cards in same system
Message-ID: <1094490310.4973.270.camel@m2.linora.com>

All,

We have a Soekris 4511 with a PCI seneo radio (2511) and a PCMCIA radio
(2511) as well.  We have compiled the hostap with DOWNLOAD_SUPPORT
defined, and we can flash the PCI radio fine, but when we try and flash
the PCMCIA radio with:

#prism2_srec -v netcs0 pkradver.hex sfradver.hex

we get:

Could not read wlan PDA. This requires PRISM2_DOWNLOAD_SUPPORT
definition in driver/module/hostap_config.h.

Is there something different that must be done to flash both pci radios
and pcmcia radios in the same system?

Thanks
KH





From manojv  Mon Sep  6 12:46:56 2004
From: manojv (Manoj Verma, Noida)
Date: Tue, 7 Sep 2004 01:16:56 +0530 
Subject: PMK derivation in Host AP
Message-ID: <1B3885BC15C7024C845AAC78314766C50A9B973B@exch-01.noida.hcltech.com>

Hi,

I was trying to find out the exact place in the Host-AP code for the
derivation of PMK (256 bit) from the master secret key.

I found that:

In function eap_ttls_process (), the master secret is passed as a parameter
to eap_tls_derive_key(), which internally user eap_prf() function, to get
the another key. 

My confusion is, the key above obtained is of length EAP_TLS_KEY_LEN i.e.
64, then where exactly the 256 bit PMK is derived in the code.

Thanks.



From jkmaline  Mon Sep  6 12:55:49 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 6 Sep 2004 12:55:49 -0700
Subject: PMK derivation in Host AP (wpa_supplicant)
In-Reply-To: <1B3885BC15C7024C845AAC78314766C50A9B973B@exch-01.noida.hcltech.com>
References: <1B3885BC15C7024C845AAC78314766C50A9B973B@exch-01.noida.hcltech.com>
Message-ID: <20040906195549.GC7368@jm.kir.nu>

On Tue, Sep 07, 2004 at 01:16:56AM +0530, Manoj Verma, Noida wrote:

> I was trying to find out the exact place in the Host-AP code for the
> derivation of PMK (256 bit) from the master secret key.

Calling this "Host-AP code" is somewhat confusing, since apparently you
are talking about wpa_supplicant..

> In function eap_ttls_process (), the master secret is passed as a parameter
> to eap_tls_derive_key(), which internally user eap_prf() function, to get
> the another key. 
> 
> My confusion is, the key above obtained is of length EAP_TLS_KEY_LEN i.e.
> 64, then where exactly the 256 bit PMK is derived in the code.

Each EAP method that generates suitable keying data is expected to store
this data in eapKeyData (struct eap_sm). Most methods, like TLS, TTLS,
PEAP, SIM, generate more than 256 bits of keying material (e.g., MSK,
EMSK, etc.). MSK is expected to start from the beginning of eapKeyData
and first 256 bits of this is used as PMK for WPA/IEEE 802.11i.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mody  Mon Sep  6 13:05:40 2004
From: mody (mody at quick.cz)
Date: Mon, 6 Sep 2004 22:05:40 +0200
Subject: hostap contra DWL-2000AP+
Message-ID: <20040906200540.GA15158@sid>

Hello!

I've a big problem with my z-com xi-330 Prism3 base PCMCIA card and HW AP
DWL-2000AP+. I'm not able to associate. The AP is setup up 64bit WEP key and
DHCP server. Other guys from my office with xi-325 (Prism2.5) and Centrino
can associate withou any problems.

I have three days to play with the AP. What should I do now to hunt the
problem? I have kismet but I dunno how to read the binary dump. I dunno much
about 802.11b/g standard.

I need a help from an expert. Please help!

Thanx!
Mody

System: Debian unstable, kernel 2.6.8, hostap from cvs (IMO 0.2.5 version).

/var/log/syslog:
...
Sep  6 09:08:04 localhost cardmgr[2598]: executing: 'modprobe hostap'
Sep  6 09:08:04 localhost kernel: hostap_crypt: registered algorithm 'NULL'
Sep  6 09:08:04 localhost cardmgr[2598]: executing: 'modprobe hostap_cs'
Sep  6 09:08:04 localhost kernel: hostap_cs: CVS (Jouni Malinen <jkmaline at cc.hut.fi>)
Sep  6 09:08:04 localhost kernel: hostap_cs: setting Vcc=33 (constant)
Sep  6 09:08:04 localhost kernel: hostap_cs: CS_EVENT_CARD_INSERTION
Sep  6 09:08:04 localhost kernel: hostap_cs: setting Vcc=50 (from config)
Sep  6 09:08:04 localhost kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01)
Sep  6 09:08:04 localhost kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
Sep  6 09:08:04 localhost kernel: io->flags = 0x0047, io.base=0x0000, len=128
Sep  6 09:08:04 localhost kernel: hostap_cs: Registered netdevice wifi0
Sep  6 09:08:04 localhost kernel: hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0400-0x047f
Sep  6 09:08:05 localhost kernel: prism2_hw_init: initialized in 194 ms
Sep  6 09:08:05 localhost kernel: wifi0: NIC: id=0x800c v1.0.0
Sep  6 09:08:05 localhost kernel: wifi0: PRI: id=0x15 v1.1.1
Sep  6 09:08:05 localhost kernel: wifi0: STA: id=0x1f v1.7.4
Sep  6 09:08:05 localhost kernel: wifi0: registered netdevice wlan0
Sep  6 09:08:05 localhost cardmgr[2598]: executing: './network start wlan0'
Sep  6 09:08:05 localhost kernel: prism2_download: dl_cmd=4 start_addr=0x003f0000 num_areas=3
Sep  6 09:08:05 localhost kernel: wifi0: test Genesis mode with HCR 0x1f
Sep  6 09:08:05 localhost kernel: prism2_pccard_cor_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 c1 a1 c1
Sep  6 09:08:05 localhost kernel: wifi0: test Genesis mode with HCR 0x0f
Sep  6 09:08:05 localhost kernel: prism2_pccard_cor_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: Readback test succeeded, HCR 0x0f
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_hw_init: initialized in 0 ms
Sep  6 09:08:05 localhost kernel: wifi0: NIC: id=0x8000 v0.0.1
Sep  6 09:08:05 localhost kernel: wifi0: PRI: id=0x15 v1.1.4
Sep  6 09:08:05 localhost kernel: Could not get RID for component STA
Sep  6 09:08:05 localhost kernel: wifi0: Failed to read STA f/w version - only Primary f/w present
Sep  6 09:08:05 localhost kernel: prism2_download: dl_cmd=6 start_addr=0x003f0000 num_areas=3
Sep  6 09:08:05 localhost kernel: wifi0: test Genesis mode with HCR 0x1f
Sep  6 09:08:05 localhost kernel: prism2_pccard_cor_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 c1 a1 c1
Sep  6 09:08:05 localhost kernel: wifi0: test Genesis mode with HCR 0x0f
Sep  6 09:08:05 localhost kernel: prism2_pccard_cor_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: Readback test succeeded, HCR 0x0f
Sep  6 09:08:05 localhost kernel: prism2_pccard_genesis_sreset: original COR 41
Sep  6 09:08:05 localhost kernel: prism2_hw_init: initialized in 0 ms
Sep  6 09:08:05 localhost kernel: wifi0: NIC: id=0x800c v1.0.0
Sep  6 09:08:05 localhost kernel: wifi0: PRI: id=0x15 v1.1.4
Sep  6 09:08:05 localhost kernel: Could not get RID for component STA
Sep  6 09:08:05 localhost kernel: wifi0: Failed to read STA f/w version - only Primary f/w present
Sep  6 09:08:05 localhost kernel: prism2_download: dl_cmd=5 start_addr=0x003f0c01 num_areas=3
Sep  6 09:08:05 localhost kernel: prism2_hw_init: initialized in 27 ms
Sep  6 09:08:05 localhost kernel: wifi0: NIC: id=0x800c v1.0.0
Sep  6 09:08:05 localhost kernel: wifi0: PRI: id=0x15 v1.1.4
Sep  6 09:08:05 localhost kernel: wifi0: STA: id=0x1f v1.8.0
Sep  6 09:08:05 localhost kernel: prism2: wlan0: operating mode changed 3 -> 2
Sep  6 09:08:05 localhost kernel: hostap_crypt: registered algorithm 'WEP'
Sep  6 09:08:05 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.1
Sep  6 09:08:05 localhost dhclient: Copyright 2004 Internet Systems Consortium.
Sep  6 09:08:05 localhost dhclient: All rights reserved.
Sep  6 09:08:05 localhost dhclient: For info, please visit http://www.isc.org/products/DHCP
Sep  6 09:08:05 localhost dhclient: 
Sep  6 09:08:05 localhost dhclient: wifi0: unknown hardware address type 801
Sep  6 09:08:05 localhost dhclient: sit0: unknown hardware address type 776
Sep  6 09:08:06 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:06 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:06 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=33:33:00:00:00:16 A4=00:00:00:00:00:00
Sep  6 09:08:06 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:06 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:06 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=33:33:ff:8c:26:9a A4=00:00:00:00:00:00
Sep  6 09:08:07 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:07 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:07 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
Sep  6 09:08:07 localhost dhclient: wifi0: unknown hardware address type 801
Sep  6 09:08:07 localhost dhclient: sit0: unknown hardware address type 776
Sep  6 09:08:07 localhost kernel: NET: Registered protocol family 17
Sep  6 09:08:07 localhost dhclient: Listening on LPF/wlan0/00:60:b3:8c:26:9a
Sep  6 09:08:07 localhost dhclient: Sending on   LPF/wlan0/00:60:b3:8c:26:9a
Sep  6 09:08:07 localhost dhclient: Sending on   Socket/fallback
Sep  6 09:08:11 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Sep  6 09:08:11 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:11 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:11 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:08:11 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:11 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:11 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
Sep  6 09:08:15 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep  6 09:08:15 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:15 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:15 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:08:15 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:15 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:15 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
Sep  6 09:08:16 localhost kernel: wlan0: no IPv6 routers present
Sep  6 09:08:20 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Sep  6 09:08:20 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:20 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:20 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:08:29 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Sep  6 09:08:29 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:29 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:29 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:08:39 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Sep  6 09:08:39 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:39 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:39 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:08:53 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Sep  6 09:08:53 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:08:53 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:08:53 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:09:09 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Sep  6 09:09:09 localhost kernel: wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
Sep  6 09:09:09 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
Sep  6 09:09:09 localhost kernel:    A1=00:00:00:00:00:00 A2=00:60:b3:8c:26:9a A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Sep  6 09:09:12 localhost dhclient: No DHCPOFFERS received.
Sep  6 09:09:12 localhost dhclient: No working leases in persistent database - sleeping.
Sep  6 09:09:12 localhost cardmgr[2598]: + Downloading primary firmware /etc/hostap_fw/AK010104.HEX to interface wlan0
Sep  6 09:09:12 localhost cardmgr[2598]: + srec summary for AK010104.HEX
Sep  6 09:09:12 localhost cardmgr[2598]: + Included file name: AK010104.HEX
Sep  6 09:09:12 localhost cardmgr[2598]: + Component: 0x0015 1.1.4 (primary firmware)
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Verifying update compatibility and combining data:
Sep  6 09:09:12 localhost cardmgr[2598]: + Plugging PDR 0400 (NIC configuration): ram16=1 pci=0 (03 00)
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Downloading to volatile memory (RAM).
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
Sep  6 09:09:12 localhost last message repeated 2 times
Sep  6 09:09:12 localhost cardmgr[2598]: + srec summary for AK010104.HEX
Sep  6 09:09:12 localhost cardmgr[2598]: + Included file name: AK010104.HEX
Sep  6 09:09:12 localhost cardmgr[2598]: + Component: 0x0015 1.1.4 (primary firmware)
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + STAID not available (maybe running PRI-only)
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Verifying update compatibility and combining data:
Sep  6 09:09:12 localhost cardmgr[2598]: + Plug record length mismatch (PDR=0x0001): 6 != 16
Sep  6 09:09:12 localhost cardmgr[2598]: + ==> extend from default
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Downloading to volatile memory (RAM).
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + Downloading secondary (station) firmware /etc/hostap_fw/RF010800.hex to interface wlan0
Sep  6 09:09:12 localhost cardmgr[2598]: + ioctl[PRISM2_IOCTL_HOSTAPD]: No data available
Sep  6 09:09:12 localhost last message repeated 2 times
Sep  6 09:09:12 localhost cardmgr[2598]: + srec summary for RF010800.hex
Sep  6 09:09:12 localhost cardmgr[2598]: + Included file name: RF010800.hex
Sep  6 09:09:12 localhost cardmgr[2598]: + Component: 0x001f 1.8.0 (station firmware)
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + STAID not available (maybe running PRI-only)
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Verifying update compatibility and combining data:
Sep  6 09:09:12 localhost cardmgr[2598]: + Could not find data position for plugging PDR 0x0413 at 0x0000118e (len=2)
Sep  6 09:09:12 localhost cardmgr[2598]: + PDR 0x0413 is not in wlan card PDA and there is no default data. Ignoring plug record.
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + Downloading to volatile memory (RAM).
Sep  6 09:09:12 localhost cardmgr[2598]: + OK.
Sep  6 09:09:12 localhost cardmgr[2598]: + Components after download:
Sep  6 09:09:12 localhost cardmgr[2598]: +   NICID: 0x800c v1.0.0
Sep  6 09:09:12 localhost cardmgr[2598]: +   PRIID: 0x0015 v1.1.4
Sep  6 09:09:12 localhost cardmgr[2598]: +   STAID: 0x001f v1.8.0
Sep  6 09:09:12 localhost cardmgr[2598]: + Internet Systems Consortium DHCP Client V3.0.1
Sep  6 09:09:12 localhost cardmgr[2598]: + Copyright 2004 Internet Systems Consortium.
Sep  6 09:09:12 localhost cardmgr[2598]: + All rights reserved.
Sep  6 09:09:12 localhost cardmgr[2598]: + For info, please visit http://www.isc.org/products/DHCP
Sep  6 09:09:12 localhost cardmgr[2598]: + 
Sep  6 09:09:12 localhost cardmgr[2598]: + wifi0: unknown hardware address type 801
Sep  6 09:09:12 localhost cardmgr[2598]: + sit0: unknown hardware address type 776
Sep  6 09:09:12 localhost cardmgr[2598]: + wifi0: unknown hardware address type 801
Sep  6 09:09:12 localhost cardmgr[2598]: + sit0: unknown hardware address type 776
Sep  6 09:09:12 localhost cardmgr[2598]: + Listening on LPF/wlan0/00:60:b3:8c:26:9a
Sep  6 09:09:12 localhost cardmgr[2598]: + Sending on   LPF/wlan0/00:60:b3:8c:26:9a
Sep  6 09:09:12 localhost cardmgr[2598]: + Sending on   Socket/fallback
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Sep  6 09:09:12 localhost cardmgr[2598]: + DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Sep  6 09:09:12 localhost cardmgr[2598]: + No DHCPOFFERS received.
Sep  6 09:09:12 localhost cardmgr[2598]: + No working leases in persistent database - sleeping.

-- 
Debian unstable 2.6.8-1-686 i686 GNU/Linux
-------------- 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/20040906/f38e1556/attachment.pgp 


From mstuff  Mon Sep  6 18:41:36 2004
From: mstuff (Morgan Read)
Date: Tue, 07 Sep 2004 13:41:36 +1200
Subject: 802.1x auth with wpa_supp?
Message-ID: <413D11D0.8050203@pl.net>

Hi,
I'm a bit green with all this, any help would be very much appreciated.

I'm trying to set up wpa_supplicant to authenticate with 802.1X.  The
details are as below.  If there's any more info I can provide that would
please let me know.

I first tried connecting with the wpa_supplicant and got the output
(first) below before wpa_supplicant exited.  Because of the:
 >
 >Failed to enable WPA in the driver.
 >
I updated the station firmware to 1.7.4 in ram and got the second output
(second) below.  Also, in the second instance the AP seemed to
"disappear" and the MAC changed to all 4s while wpa_supplicant was
running (it didn't exit itself) and when I exited wpa_supplicant (with
ctrl-C) the AP came back with a real MAC.

But, this is all a bit strange because I shouldn't be doing anything
with wpa if I'm using 802.1x??  So, I think something must be
fundamentaly amiss?

Attached is my wpa_supplicant.conf

Details:
The authentication server is a "fully patched up" MS IAS win2003 Server.

"private_key" "/etc/cert/client.key" generated with "openssl genrsa -out
client.key 1024" with no password (and is as defined as "user_key" in
xsupplicant.conf - is this the same thing?).

"ca_cert" "/etc/cert/verisign_2028.pem" was obtained by recommendation
(and is as defined by "root_cert" in xsupplicant.conf - is this the same
thing?)

Thanks very much for any help.
Regards,
Morgan.

###########################

[root at morgansmachine root]# wpa_supplicant -iwlan0
-c/etc/wpa_supplicant.conf -d Configuration file
'/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=0
Priority group 0
     id=0 ssid='uoa'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=1
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to enable WPA in the driver.
wpa_driver_hostap_set_wpa: enabled=0
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to disable WPA in the driver.
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
[root at morgansmachine root]#

###########################

[root at morgansmachine root]# wpa_supplicant -iwlan0
-c/etc/wpa_supplicant.conf -d
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=0
Priority group 0
     id=0 ssid='uoa'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=44:44:44:44:44:44
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
Network configuration found for the current AP
EAPOL: External notification - portControl=Auto
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
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
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=44:44:44:44:44:44
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
Network configuration found for the current AP
EAPOL: External notification - portControl=Auto
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAP: EAP entering state FAILURE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state FAIL
EAPOL: SUPP_PAE entering state HELD
EAPOL: SUPP_BE entering state IDLE
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Authentication with 44:44:44:44:44:44 timed out.
Setting scan request: 0 sec 0 usec
Already associated with a configured network - generating associated event
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
Signal 2 received - terminating
wpa_driver_hostap_deauthenticate
wpa_driver_hostap_reset: type=2
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
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
[root at morgansmachine root]#

###########################

-- 
Morgan Read
<mailto:mstuffATplDOTnet>



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_supplicant.conf
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20040907/1d0de8de/attachment.txt 


From jkmaline  Mon Sep  6 19:53:00 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 6 Sep 2004 19:53:00 -0700
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <413D11D0.8050203@pl.net>
References: <413D11D0.8050203@pl.net>
Message-ID: <20040907025300.GB7392@jm.kir.nu>

On Tue, Sep 07, 2004 at 01:41:36PM +1200, Morgan Read wrote:

> >Failed to enable WPA in the driver.
> >
> I updated the station firmware to 1.7.4 in ram and got the second output
> (second) below.  Also, in the second instance the AP seemed to
> "disappear" and the MAC changed to all 4s while wpa_supplicant was
> running (it didn't exit itself) and when I exited wpa_supplicant (with
> ctrl-C) the AP came back with a real MAC.
> 
> But, this is all a bit strange because I shouldn't be doing anything
> with wpa if I'm using 802.1x??  So, I think something must be
> fundamentaly amiss?

The current version of the Host AP driver interface in wpa_supplicant
always enables WPA support and consequently, requires new station
firmware. You might be able to use IEEE 802.1X with driver_wext.c (add
CONFIG_DRIVER_WEXT=y to .config, use ap_scan=0 in wpa_supplicant.conf,
and -Dwext on command line).

> Already associated with a configured network - generating associated event
> Association event - clear replay counter
> Associated to a new BSS: BSSID=44:44:44:44:44:44

> ap_scan=0

I would recommend starting with ap_scan=1 when using Host AP driver.
Your debug log showed that wpa_supplicant was not receiving any EAPOL
packets from the AP and then timing out. ap_scan=1 has received much
more testing..

> 	eap=PEAP MSCHAPV2

If you are using EAP-PEAP with EAP-MSCHAPv2 as the inner (tunneled,
phase 2) authentication, you only need to have PEAP on this line. Phase
2 method is configured below with:

> 	phase2="auth=MSCHAPV2"

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep  6 21:01:21 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 6 Sep 2004 21:01:21 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040823134009.GH9839@informatik.uni-rostock.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
Message-ID: <20040907040121.GC7392@jm.kir.nu>

On Mon, Aug 23, 2004 at 03:40:09PM +0200, Gunter Burchardt wrote:

> Client to client communication doesnt work with WPA.

It took some time for me to get a suitable test setup at home so that I
can try to reproduce this. Now that I have the test setup, I was
actually unable to reproduce this.. Broadcast packets and ping between
two associated STAs worked fine in my tests with WPA-PSK using TKIP.

> hostapd: 10.0.0.1/8
> sta1: 10.0.0.2/8
> sta2: 10.0.0.3/8
> 
> sta1: ping 10.0.0.3 -> no answer !!!

Does sta1->hostapd ping work? What about hostapd->sta2?

> Arp is broadcast. Something is wrong with broadcast, bridge packets and
> wpa! Unicast works!

Please give more details of your test setup, including configuration
files and driver/firmware versions of each device.

-- 
Jouni Malinen                                            PGP id EFC895FA



From manojv  Mon Sep  6 23:46:09 2004
From: manojv (Manoj Verma, Noida)
Date: Tue, 7 Sep 2004 12:16:09 +0530 
Subject: PMK derivation in Host AP (wpa_supplicant)
Message-ID: <1B3885BC15C7024C845AAC78314766C50A9B987B@exch-01.noida.hcltech.com>



> -----Original Message-----
> From: hostap-bounces+manojv=noida.hcltech.com at shmoo.com [mailto:hostap-
> bounces+manojv=noida.hcltech.com at shmoo.com] On Behalf Of Jouni Malinen
> Sent: Tuesday, September 07, 2004 1:26 AM
> To: hostap at shmoo.com
> Subject: Re: PMK derivation in Host AP (wpa_supplicant)
> 
> On Tue, Sep 07, 2004 at 01:16:56AM +0530, Manoj Verma, Noida wrote:
> 
> > I was trying to find out the exact place in the Host-AP code for the
> > derivation of PMK (256 bit) from the master secret key.
> 
> Calling this "Host-AP code" is somewhat confusing, since apparently you
> are talking about wpa_supplicant..

 [Manoj]  Agree.

> 
> > In function eap_ttls_process (), the master secret is passed as a
> parameter
> > to eap_tls_derive_key(), which internally user eap_prf() function, to
> get
> > the another key.
> >
> > My confusion is, the key above obtained is of length EAP_TLS_KEY_LEN
i.e.
> > 64, then where exactly the 256 bit PMK is derived in the code.
> 
> Each EAP method that generates suitable keying data is expected to store
> this data in eapKeyData (struct eap_sm). Most methods, like TLS, TTLS,
> PEAP, SIM, generate more than 256 bits of keying material (e.g., MSK,
> EMSK, etc.). MSK is expected to start from the beginning of eapKeyData
> and first 256 bits of this is used as PMK for WPA/IEEE 802.11i.
> 

[Manoj] If we see the file "eap_tls.c" the statement:
	sm->eapKeyData = eap_tls_derive_key(..)    

So just to confirm once again, if I take first 256 bits of sm->eapKeyData,
that is my PMK.

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



From gbur  Tue Sep  7 02:44:52 2004
From: gbur (Gunter Burchardt)
Date: Tue, 7 Sep 2004 11:44:52 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907040121.GC7392@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
Message-ID: <20040907094452.GH28682@informatik.uni-rostock.de>

> > Client to client communication doesnt work with WPA.
> 
> It took some time for me to get a suitable test setup at home so that I
> can try to reproduce this. Now that I have the test setup, I was
> actually unable to reproduce this.. Broadcast packets and ping between
> two associated STAs worked fine in my tests with WPA-PSK using TKIP.

I'm using WPA-EAP with TKIP. 

> > hostapd: 10.0.0.1/8
> > sta1: 10.0.0.2/8
> > sta2: 10.0.0.3/8
> > 
> > sta1: ping 10.0.0.3 -> no answer !!!
> 
> Does sta1->hostapd ping work? What about hostapd->sta2?

sta1 can ping hostapd. sta2 can ping hostapd. hostapd can ping sta1 and
sta2. But sta1 didn't get an answer of its arp request to get mac address 
of sta2. Therefor sta1 can't ping sta2. In other direction the same
behaviour. There is no firewall or something else active. 

> > Arp is broadcast. Something is wrong with broadcast, bridge packets and
> > wpa! Unicast works!
> 
> Please give more details of your test setup, including configuration
> files and driver/firmware versions of each device.

How are mac-broadcast packets handled in hostap-driver? What key is
used to encrypt broadcast packets? The

Latest hostap cvs version. Latest firmware version (1.1.1/1.7.4).
wpa_supplicant works on broadcom chips. Other clints with windows own
supplicant.

Here the config of hostapd:

interface=wlan0

logger_syslog=-1
logger_syslog_level=3
logger_stdout=-1
logger_stdout_level=3

debug=1
dump_file=/tmp/hostapd.dump
daemonize=1
ssid=foobar

macaddr_acl=0
auth_algs=1
ieee8021x=1
minimal_eap=0
eap_message=hello

wep_key_len_broadcast=13
wep_key_len_unicast=13
wep_rekey_period=300


eapol_key_index_workaround=0
own_ip_addr=172.16.0.1

nas_identifier=3000

auth_server_addr=192.168.42.10
auth_server_port=1812
auth_server_shared_secret=secretsecretsecr

acct_server_addr=192.168.42.10
acct_server_port=1813
acct_server_shared_secret=secretsecretsecr

radius_retry_primary_interval=600
radius_acct_interim_interval=600

eap_reauth_period=60

wpa=1
wpa_passphrase=secret passphrase
wpa_key_mgmt=WPA-EAP
wpa_pairwise=TKIP CCMP
 

regards
gunter



From mstuff  Tue Sep  7 03:25:30 2004
From: mstuff (Morgan Read)
Date: Tue, 07 Sep 2004 22:25:30 +1200
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <20040907025300.GB7392@jm.kir.nu>
References: <413D11D0.8050203@pl.net> <20040907025300.GB7392@jm.kir.nu>
Message-ID: <413D8C9A.9030707@pl.net>

Hi Jouni,
Well that was much more exciting!  At least to my eyes...

I ran as you suggested per the hostap driver (not wext).

It seemed to be cycling through a process, and pausing if and when it
got some sort of response?  During one of these pauses I ran iwconfig &
ifconfig on another terminal, and then stopped the wpa_supplican
(ctl-c).  Copied below are first the output form iwconfig & ifconfig
followed by the debug output from wpa_supplicant (# wpa_supplicant
-iwlan0 -c/etc/wpa_supplicant.conf -d).  I guess that's a bit more
repetitive than necessary, but I thought better safe than sorry.

At some point I'll need to run dhclient?

Thanks very much!

Regards,
Morgan.

###########################
[root at morgansmachine root]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

wifi0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Access Point: 00:0D:ED:99:37:C0  Bit Rate:11Mb/s
           Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:14/70  Signal level:-78 dBm  Noise level:-92 dBm
           Rx invalid nwid:0  Rx invalid crypt:507  Rx invalid frag:0
           Tx excessive retries:26  Invalid misc:3760   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Access Point: 00:0D:ED:99:37:C0  Bit Rate:11Mb/s
           Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:14/70  Signal level:-78 dBm  Noise level:-92 dBm
           Rx invalid nwid:0  Rx invalid crypt:507  Rx invalid frag:0
           Tx excessive retries:26  Invalid misc:3760   Missed beacon:0

[root at morgansmachine root]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:90:F5:13:D2:5F
           inet6 addr: fe80::290:f5ff:fe13:d25f/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:8732 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1652 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1051438 (1.0 Mb)  TX bytes:127148 (124.1 Kb)
           Interrupt:10 Base address:0x3200

eth0:1    Link encap:Ethernet  HWaddr 00:90:F5:13:D2:5F
           inet addr:130.216.166.9  Bcast:130.216.167.255
Mask:255.255.254.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:2100 errors:0 dropped:5491 overruns:0 frame:0
           TX packets:2588 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:126000 (123.0 Kb)  TX bytes:116511 (113.7 Kb)
           Interrupt:10 Base address:0x3200

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:2167 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2167 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:2024844 (1.9 Mb)  TX bytes:2024844 (1.9 Mb)

wifi0     Link encap:UNSPEC  HWaddr
00-30-84-1F-AE-F7-00-00-00-00-00-00-00-00-00 -00
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:7591 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2589 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:618292 (603.8 Kb)  TX bytes:116537 (113.8 Kb)
           Interrupt:3 Base address:0x100

wlan0     Link encap:Ethernet  HWaddr 00:30:84:1F:AE:F7
           inet6 addr: fe80::230:84ff:fe1f:aef7/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:2100 errors:0 dropped:5491 overruns:0 frame:0
           TX packets:2588 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:126000 (123.0 Kb)  TX bytes:116511 (113.7 Kb)
           Interrupt:3 Base address:0x100

[root at morgansmachine root]#
###########################
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Disconnect event - remove keys
wpa_driver_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
Starting AP scan (broadcast SSID)
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=12
Received 158 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:ed:99:37:c0 ssid='uoa' wpa_ie_len=0 rsn_ie_len=0
    skip - no WPA/RSN IE
    selected non-WPA AP 00:0d:ed:99:37:c0 ssid='uoa'
Trying to associate with 00:0d:ed:99:37:c0 (SSID='uoa' freq=2437 MHz)
Cancelling scan request
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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b04 len=12
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Disconnect event - remove keys
wpa_driver_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
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=3):
      75 6f 61                                          uoa
Wireless event: cmd=0x8b19 len=12
Received 158 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:ed:99:37:c0 ssid='uoa' wpa_ie_len=0 rsn_ie_len=0
    skip - no WPA/RSN IE
    selected non-WPA AP 00:0d:ed:99:37:c0 ssid='uoa'
Trying to associate with 00:0d:ed:99:37:c0 (SSID='uoa' freq=2437 MHz)
Cancelling scan request
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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec

<SNIP>

Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b1a len=15
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Signal 2 received - terminating
wpa_driver_hostap_deauthenticate
wpa_driver_hostap_reset: type=2
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
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
[root at morgansmachine root]#
###########################


Jouni Malinen wrote:
> On Tue, Sep 07, 2004 at 01:41:36PM +1200, Morgan Read wrote:
> 
> 
>>>Failed to enable WPA in the driver.
>>>
>>
>>I updated the station firmware to 1.7.4 in ram and got the second output
>>(second) below.  Also, in the second instance the AP seemed to
>>"disappear" and the MAC changed to all 4s while wpa_supplicant was
>>running (it didn't exit itself) and when I exited wpa_supplicant (with
>>ctrl-C) the AP came back with a real MAC.
>>
>>But, this is all a bit strange because I shouldn't be doing anything
>>with wpa if I'm using 802.1x??  So, I think something must be
>>fundamentaly amiss?
> 
> 
> The current version of the Host AP driver interface in wpa_supplicant
> always enables WPA support and consequently, requires new station
> firmware. You might be able to use IEEE 802.1X with driver_wext.c (add
> CONFIG_DRIVER_WEXT=y to .config, use ap_scan=0 in wpa_supplicant.conf,
> and -Dwext on command line).
> 
> 
>>Already associated with a configured network - generating associated event
>>Association event - clear replay counter
>>Associated to a new BSS: BSSID=44:44:44:44:44:44
> 
> 
>>ap_scan=0
> 
> 
> I would recommend starting with ap_scan=1 when using Host AP driver.
> Your debug log showed that wpa_supplicant was not receiving any EAPOL
> packets from the AP and then timing out. ap_scan=1 has received much
> more testing..
> 
> 
>>	eap=PEAP MSCHAPV2
> 
> 
> If you are using EAP-PEAP with EAP-MSCHAPv2 as the inner (tunneled,
> phase 2) authentication, you only need to have PEAP on this line. Phase
> 2 method is configured below with:
> 
> 
>>	phase2="auth=MSCHAPV2"
> 
> 

-- 
Morgan Read
<mailto:mstuffATplDOTnet>





From dohan71  Tue Sep  7 06:31:10 2004
From: dohan71 (D.H.Kwon)
Date: Tue, 7 Sep 2004 22:31:10 +0900
Subject: Help me use Ethereal's Capture Filters
Message-ID: <10cf401c494de$effe5690$29011fac@korea.com>

I want to filter out uninteresting frames at capture time. I know
Ethereal use the pcap filter language. But, can pcap filter IEEE 802.11
frames? If yes, which syntax is used?






 <http://www.korea.com>
<http://blog.korea.com/nangmanadmin/5291> 	 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040907/1cfc4417/attachment.htm 


From wk-hostap  Tue Sep  7 08:09:02 2004
From: wk-hostap (Wilfried Klaebe)
Date: Tue, 7 Sep 2004 17:09:02 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907040121.GC7392@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
Message-ID: <20040907150902.GA5222@kaos.in-kiel.de>

Am Mon, Sep 06, 2004 at 09:01:21PM -0700 schrieb Jouni Malinen:
> > Arp is broadcast. Something is wrong with broadcast, bridge packets and
> > wpa! Unicast works!
> 
> Please give more details of your test setup, including configuration
> files and driver/firmware versions of each device.

I have a similar problem...

setup:

One Prism2.5 PCI card, ram-downloaded PRI 1.1.4, STA 1.8.3 and hostap-cvs
in Master mode, with RSN (config files attached), in the machine called
"the AP".

One Atheros 5001X+ (a/b/g) with latest madwifi driver and wpa_supplicant
in my laptop.

When I give the AP's eth0 it's IP, and wlan0 some private IP (10.40.0.1
in this case), there's no problem. My laptop can ping the AP from 10.40.0.2,
can ssh to it, can connect through it (via NAT) anywhere it wants, anything.

But when I set up bridging - br0 with slaves eth0 and wlan0, eth0 and wlan0
both up, br0 with the IP that eth0 had before, just as described several
times before, my laptop  I cannot ping it anymore.

tcpdump -i wlan0 shows ARP requests coming in on wlan0, but they don't
appear on br0. If I ping the same IP from another box over the ethernet,
ARP requests come in on eth0, and show up some milliseconds later on
br0, are then answered, and everything works.

Also, there is never anything going out on wlan0. I see router
advertisements and other broadcast packets on br0, both from the ethernet
and from the box itself, which both don't ever go out on wlan0.

I have no clue where to look for the problem. It seems to me that RSN is
not alone the problem, since the packets come in on wlan0. If some
keying/authentication/authorization was the issue, they should not, if
I am correct; and if wlan0 is not bridged, everything works.

Here the promised config files:

hostapd.conf:
interface=wlan0
ssid=SSID
macaddr_acl=0
auth_algs=1
ieee8021x=1
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1
auth_server_*=@values
wpa=2
wpa_key_mgmt=WPA-EAP
wpa_pairwise=CCMP
wpa_group_rekey=600
wpa_gmk_rekey=86400

wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
network={
        ssid="SSID"
        scan_ssid=0
        proto=RSN
        key_mgmt=WPA-EAP
        pairwise=CCMP
        group=CCMP
        eap=TTLS
        ca_cert="/etc/802.11i/SSID/root.pem"
        identity="identity"
        password="password"
        phase2="auth=PAP"
        anonymous_identity="anonymous"
}

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From capacity77  Tue Sep  7 09:00:48 2004
From: capacity77 (capacity77 at tin.it)
Date: Tue, 7 Sep 2004 18:00:48 +0200
Subject: user identification
In-Reply-To: <20040906165635.GG28682@informatik.uni-rostock.de>
Message-ID: <4119713300012F85@ims6a.cp.tin.it>

I mean, in a newtork of laptops mounting HostAP, when a host moves from
an area to another, how can this host be recognized? I explain my problem,
I have to guarantee a cartain Quality of Service on this kind of netwoks
so I need to identify uniquely every host that goes on roaming. 
Using the standard 802.1x, when you move from an AP to another, the connecion
falls on the further AP and it gets active on the nearer one, using a new
IP. The user would lose its identity to get a new one.
So my question was, does HostAP use the 802.1x standard to do the authentication
or does it implement a different kind?


>-- Messaggio originale --
>Date: Mon, 6 Sep 2004 18:56:35 +0200
>From: Gunter Burchardt <gbur at informatik.uni-rostock.de>
>To: capacity77 at tin.it
>Cc: hostap at shmoo.com
>Subject: Re: user identification
>
>
>> Hi there!
>> I'm trying to find out how HostAP treats the user identification. I'd
like
>> to solve the problem on how I can provide and guarantee a certain QoS
to
>> a user who moves in a network made up by laptops running HostAP. A sort
>> of hand off plus the QoS stuffs. And I need to know how HostAP recognize
>> a user.
>
>What did you mean with user identification? There is 802.1x to
>recognize/authenticate a user. After it there is only the MAC address
>with its keys (if WEP/WPA) to identify packets from/to the user. 
>
>regards
>gunter





From gbur  Tue Sep  7 10:06:03 2004
From: gbur (Gunter Burchardt)
Date: Tue, 7 Sep 2004 19:06:03 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907040121.GC7392@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
Message-ID: <20040907170603.GI28682@informatik.uni-rostock.de>

Well, I guess the problem could be with encryption of broadcast packets
(mac broadcast, not ip). I didn't have 802.11i specification here, but
i guess that broadcast packets should be encryted with the group key.
Could it be that such packets are encrypted with the wrong key from
hostap?

regards
gunter 



From gbur  Tue Sep  7 10:14:05 2004
From: gbur (Gunter Burchardt)
Date: Tue, 7 Sep 2004 19:14:05 +0200
Subject: user identification
In-Reply-To: <4119713300012F85@ims6a.cp.tin.it>
References: <20040906165635.GG28682@informatik.uni-rostock.de>
	<4119713300012F85@ims6a.cp.tin.it>
Message-ID: <20040907171405.GK28682@informatik.uni-rostock.de>

> I mean, in a newtork of laptops mounting HostAP, when a host moves from
> an area to another, how can this host be recognized? I explain my problem,
> I have to guarantee a cartain Quality of Service on this kind of netwoks
> so I need to identify uniquely every host that goes on roaming. 
> Using the standard 802.1x, when you move from an AP to another, the connecion
> falls on the further AP and it gets active on the nearer one, using a new

Why should the same user get a new ip? If you use 802.1x there is an
RADIUS server. And with help of some specific radius attribute you can
give one user whenever it connects the same IP! Ok hostapd doesn't
support it, but it is possible to implement such things. If the user
has the same IP its only a part of routing that his connections keep
opened!

> The user would lose its identity to get a new one.
> So my question was, does HostAP use the 802.1x standard to do the authentication
> or does it implement a different kind?

At the moment its only for authentication and to get keys from the
radius server. But its possible to implement other things.

regards
gunter



From snai8255  Tue Sep  7 22:18:23 2004
From: snai8255 (snai8255 at mail.usyd.edu.au)
Date: Wed,  8 Sep 2004 15:18:23 +1000
Subject: wep decrypt?
Message-ID: <1094620703.413e961f8be64@www-mail.usyd.edu.au>

hi guys;

does anyone know where in the source code is the wep decrypt function being called from?i put a
printk
in prism2_wep_encrypt and prism2_wep_decrypt.the funny thing is i can see "prism2_wep_encrypt" when
i do dmesg but no sign of prism2_wep_decrypt anywhere:(

regards saji

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From jkmaline  Tue Sep  7 23:00:22 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 7 Sep 2004 23:00:22 -0700
Subject: wep decrypt?
In-Reply-To: <1094620703.413e961f8be64@www-mail.usyd.edu.au>
References: <1094620703.413e961f8be64@www-mail.usyd.edu.au>
Message-ID: <20040908060022.GE7362@jm.kir.nu>

On Wed, Sep 08, 2004 at 03:18:23PM +1000, snai8255 at mail.usyd.edu.au wrote:

> does anyone know where in the source code is the wep decrypt function being called from?i put a
> printk
> in prism2_wep_encrypt and prism2_wep_decrypt.the funny thing is i can see "prism2_wep_encrypt" when
> i do dmesg but no sign of prism2_wep_decrypt anywhere:(

You may have to force the driver to use host-side decryption with
'iwpriv wlan0 host_decrypt 1' for this. By default, encryption and
decryption are done in the wlan card if the station firmware is known to
work correctly (many of them have bugs for some cases). You can also
verify the current configuration with 'iwpriv wlan0 gethost_encrypt'.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Sep  7 23:04:52 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 7 Sep 2004 23:04:52 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907170603.GI28682@informatik.uni-rostock.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907170603.GI28682@informatik.uni-rostock.de>
Message-ID: <20040908060452.GF7362@jm.kir.nu>

On Tue, Sep 07, 2004 at 07:06:03PM +0200, Gunter Burchardt wrote:

> Well, I guess the problem could be with encryption of broadcast packets
> (mac broadcast, not ip). I didn't have 802.11i specification here, but
> i guess that broadcast packets should be encryted with the group key.
> Could it be that such packets are encrypted with the wrong key from
> hostap?

Broadcast packets are indeed encrypted with a different key. However,
since you were able to ping the stations from the AP, I would assume
broadcast was working. Anyway, you can verify this by making sure that
the AP does not have station IP address in its ARP cache and then ping
the station from the AP.

However, I would be somewhat surprised if broadcast packets were
encrypted with incorrect key since they are working fine in my tests
even for the case of ping from one associated STA to another after
having cleared ARP cache.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Sep  7 23:09:57 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 7 Sep 2004 23:09:57 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907094452.GH28682@informatik.uni-rostock.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907094452.GH28682@informatik.uni-rostock.de>
Message-ID: <20040908060957.GG7362@jm.kir.nu>

On Tue, Sep 07, 2004 at 11:44:52AM +0200, Gunter Burchardt wrote:

> I'm using WPA-EAP with TKIP. 

> wep_key_len_broadcast=13
> wep_key_len_unicast=13
> wep_rekey_period=300

> wpa_pairwise=TKIP CCMP

You should not mix TKIP with dynamic WEP keys. This configuration is
likely to break your broadcast keys every 300 seconds.. You can verify
with 'hostap_crypt_conf -l wlan0' and 'cat /proc/net/hostap/wlan0/crypt'
that the broadcast keys (the once with non-zero keyidx; in
hostap_crypt_conf listing they are actually keys 2 and 3, in procfs file
1 and 2) look valid.

Some client implementations may have problems with mixed mode
configuration that allows both TKIP and CCMP for pairwise keys. If you
still see problems after removing those wep_* lines, I would also
consider disabling CCMP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Sep  7 23:15:36 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 7 Sep 2004 23:15:36 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040907150902.GA5222@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
Message-ID: <20040908061536.GH7362@jm.kir.nu>

On Tue, Sep 07, 2004 at 05:09:02PM +0200, Wilfried Klaebe wrote:

> When I give the AP's eth0 it's IP, and wlan0 some private IP (10.40.0.1
> in this case), there's no problem. My laptop can ping the AP from 10.40.0.2,
> can ssh to it, can connect through it (via NAT) anywhere it wants, anything.
> 
> But when I set up bridging - br0 with slaves eth0 and wlan0, eth0 and wlan0
> both up, br0 with the IP that eth0 had before, just as described several
> times before, my laptop  I cannot ping it anymore.

Have you tested this without RSN just using plaintext?

Can you please send 'brctl show', 'brctl showstp br0', and 'ifconfig'
output from the case where ping does not work?

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Tue Sep  7 23:46:09 2004
From: gbur (Gunter Burchardt)
Date: Wed, 8 Sep 2004 08:46:09 +0200
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040902050815.GC7393@jm.kir.nu>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
	<20040902050815.GC7393@jm.kir.nu>
Message-ID: <20040908064609.GM28682@informatik.uni-rostock.de>

> Is there any particular reason for parsing DHCP packets? One option
> would be to open packet socket on the same interface with Linux Socket
> filter to capture the packets and then take the layer 2 address from
> them. Then again, this may not end up being much simpler. Eventually, I
> would assume this could be replaced with something like iptables
> firewall queueing packets from unknown MAC addresses for user space
> processing and all devices would be noticed whenever they send the first
> packet, no matter whether it is DHCP or something else, i.e., static IP
> and non-IPv4 hosts would also be processed.

New plan! I will write a kernel module to filter pacets from assoziated
stations. Since 2.4 it is possible to register netfilter hooks. With
help of this, a callback function can decide which packet will be droped
or passed. This module will have a misc device. Over ipctrls you can
configure it (like you did it in hostap driver). I will borrow some
code of hostap driver ;)

regards
gunter



From mody  Wed Sep  8 00:09:40 2004
From: mody (mody at quick.cz)
Date: Wed, 8 Sep 2004 09:09:40 +0200
Subject: hostap contra DWL-2000AP+
In-Reply-To: <20040906200540.GA15158@sid>
References: <20040906200540.GA15158@sid>
Message-ID: <20040908070940.GA25274@sid>

Halloooo! I really need help with this AP. Please!

Mody

-- 
Debian unstable 2.6.8-1-686 i686 GNU/Linux
-------------- 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/20040908/f85eea14/attachment.pgp 


From sime  Wed Sep  8 02:58:34 2004
From: sime (Simon Males)
Date: Wed, 08 Sep 2004 19:58:34 +1000
Subject: ca_cert .pem extention
Message-ID: <413ED7CA.3060103@anticd.org>


Do the CA's have to have the .pem extention per the wpa_supplicant.conf 
examples.

I as I think I require thawte root CA, i have downloaded 
thawte-roots.zip which contain .cer files.

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



From rocci  Wed Sep  8 03:57:26 2004
From: rocci (Rocci)
Date: Wed, 08 Sep 2004 20:57:26 +1000
Subject: ca_cert .pem extention
In-Reply-To: <413ED7CA.3060103@anticd.org>
References: <413ED7CA.3060103@anticd.org>
Message-ID: <413EE596.9050806@rocknetworks.net.au>

Simon Males wrote:

>
> Do the CA's have to have the .pem extention per the 
> wpa_supplicant.conf examples.
>
> I as I think I require thawte root CA, i have downloaded 
> thawte-roots.zip which contain .cer files.
>
I wasn't sure myself so I just converted the .cer certificates using 
openssl.
I guess you could just try .cer files and see. Otherwise, convert them.

e.g. openssl x509 -inform der -in acertificate.pem -out acertificate.pem


HTH.



From rocci  Wed Sep  8 04:27:19 2004
From: rocci (Rocci)
Date: Wed, 08 Sep 2004 21:27:19 +1000
Subject: ca_cert .pem extention
In-Reply-To: <413EE596.9050806@rocknetworks.net.au>
References: <413ED7CA.3060103@anticd.org>
	<413EE596.9050806@rocknetworks.net.au>
Message-ID: <413EEC97.7020509@rocknetworks.net.au>

Rocci wrote:

> Simon Males wrote:
>
>>
>> Do the CA's have to have the .pem extention per the 
>> wpa_supplicant.conf examples.
>>
>> I as I think I require thawte root CA, i have downloaded 
>> thawte-roots.zip which contain .cer files.
>>
> I wasn't sure myself so I just converted the .cer certificates using 
> openssl.
> I guess you could just try .cer files and see. Otherwise, convert them.
>
> e.g. openssl x509 -inform der -in acertificate.pem -out acertificate.pem
>
>
> HTH.
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
sorry that openssl command was meant to be:
openssl x509 -inform der -in acertificate.cer -out acertificate.pem





From jkmaline  Wed Sep  8 06:31:35 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 8 Sep 2004 06:31:35 -0700
Subject: ca_cert .pem extention
In-Reply-To: <413ED7CA.3060103@anticd.org>
References: <413ED7CA.3060103@anticd.org>
Message-ID: <20040908133135.GA7166@jm.kir.nu>

On Wed, Sep 08, 2004 at 07:58:34PM +1000, Simon Males wrote:

> Do the CA's have to have the .pem extention per the wpa_supplicant.conf 
> examples.

File name or the extension does not really have anything to do with the
contents of the file.. It's just a convention to use .pem for files that
have PEM/BASE64 format.

Anyway, wpa_supplicant should accept both PEM and DER formats for the
files. DER/ASN1 is tried first and if parsing fails, the file is
assumed to be using PEM.

> I as I think I require thawte root CA, i have downloaded 
> thawte-roots.zip which contain .cer files.

And what do these files actually contain (e.g., what does 'file *.cer'
tell)? Another quick test would be to just configure them for
wpa_supplicant and see what happens..

-- 
Jouni Malinen                                            PGP id EFC895FA



From sime  Wed Sep  8 06:53:49 2004
From: sime (Simon Males)
Date: Wed, 08 Sep 2004 23:53:49 +1000
Subject: ca_cert .pem extention
In-Reply-To: <20040908133135.GA7166@jm.kir.nu>
References: <413ED7CA.3060103@anticd.org> <20040908133135.GA7166@jm.kir.nu>
Message-ID: <413F0EED.8040005@anticd.org>


 > And what do these files actually contain (e.g., what does 'file *.cer'
 > tell)?

$ file *.cer
Thawte Code Signing CA.cer: data
Thawte SGC CA.cer:          ASCII text, with CRLF line terminators
Thawte SSL Domain CA.cer:   ASCII text, with CRLF line terminators
$ file Thawte\ Server\ Roots/*.cer
Thawte Server Roots/ThawtePremiumServerCA.cer: data
Thawte Server Roots/ThawteServerCA.cer:        data
$ file Thawte\ Test\ Roots/*.cer
Thawte Test Roots/Thawte Test Root.cer: data

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



From wk-hostap  Wed Sep  8 07:04:58 2004
From: wk-hostap (Wilfried Klaebe)
Date: Wed, 8 Sep 2004 16:04:58 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040908061536.GH7362@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
Message-ID: <20040908140458.GA8673@kaos.in-kiel.de>

Am Tue, Sep 07, 2004 at 11:15:36PM -0700 schrieb Jouni Malinen:
> On Tue, Sep 07, 2004 at 05:09:02PM +0200, Wilfried Klaebe wrote:
> 
> > When I give the AP's eth0 it's IP, and wlan0 some private IP (10.40.0.1
> > in this case), there's no problem. My laptop can ping the AP from 10.40.0.2,
> > can ssh to it, can connect through it (via NAT) anywhere it wants, anything.
> > 
> > But when I set up bridging - br0 with slaves eth0 and wlan0, eth0 and wlan0
> > both up, br0 with the IP that eth0 had before, just as described several
> > times before, my laptop  I cannot ping it anymore.
> 
> Have you tested this without RSN just using plaintext?

For this I used another machine with a comparable setup, since I am at
the moment not at the first machine. It too has a Prism2.5 PCI Card
with the mentioned firmware.

I just tested with ieee8021x=0 and wpa=0 instead of ieee8021x=1 and wpa=2:
Same thing. ARP requests incoming on wlan0, but not showing up on br0.

I also tried it the other way round: If I try to ping the laptop on the
WLAN, I can see the ARP requests going out on br0 and then eth0, but not
wlan0.

It seems not to be a problem of encryption, then, but somewhere else.

> Can you please send 'brctl show', 'brctl showstp br0', and 'ifconfig'
> output from the case where ping does not work?

This is without encryption.

brctl show:
bridge name     bridge id               STP enabled     interfaces
br0             8000.0010dcca8d5d       no              eth0
                                                        wlan0
brctl showstp br0:
br0
 STP is disabled for this interface

ifconfig (removed uninteresting devices (sit*, ippp*, lo)):
br0       Link encap:Ethernet  HWaddr 00:10:DC:CA:8D:5D
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:875217 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1086722 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:94092273 (89.7 MiB)  TX bytes:547047397 (521.7 MiB)
            
eth0      Link encap:Ethernet  HWaddr 00:10:DC:CA:8D:5D
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:457605 errors:0 dropped:0 overruns:0 frame:0
          TX packets:496211 errors:0 dropped:0 overruns:1 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:65529152 (62.4 MiB)  TX bytes:366076552 (349.1 MiB)
          Interrupt:11 Base address:0x9000

wifi0     Link encap:UNSPEC  HWaddr 00-40-05-AF-4B-C9-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10531 (10.2 KiB)  TX bytes:11958 (11.6 KiB)
          Interrupt:12 Memory:d09e2000-d09e3000 

wlan0     Link encap:Ethernet  HWaddr 00:40:05:AF:4B:C9  
          inet6 addr: fe80::240:5ff:feaf:4bc9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:115 errors:0 dropped:0 overruns:0 frame:0
          TX packets:118 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4830 (4.7 KiB)  TX bytes:7212 (7.0 KiB)
          Interrupt:12 Memory:d09e2000-d09e3000 

wlan0ap   Link encap:UNSPEC  HWaddr 00-40-05-AF-4B-C9-30-30-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:2290  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:2778 (2.7 KiB)
          Interrupt:12 Memory:d09e2000-d09e3000 

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From jmi_1996  Wed Sep  8 09:15:00 2004
From: jmi_1996 (J I)
Date: Wed, 8 Sep 2004 09:15:00 -0700 (PDT)
Subject: PMK with LEAP in the WPA supplicant
Message-ID: <20040908161500.65336.qmail@web21421.mail.yahoo.com>


Hi,

I wanted to use LEAP with  WPA supplicant. As per my understanding, wpa_supplicant_process_1_of_4 function calls eapol_sm_get_key with the key size as 256, while the key size obtained with LEAP is only 128 bit.

 

With this, I am not sure if LEAP can be used with WPA where TKIP is configured as a unicast/group cipher suite. 

 

Thanks

JMI


		
---------------------------------
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040908/e18ef8bc/attachment.htm 


From simon  Wed Sep  8 09:24:38 2004
From: simon (Simon Barber)
Date: Wed, 8 Sep 2004 09:24:38 -0700
Subject: PATCH: wired eapol receive/send
Message-ID: <AC8C1F46CD753F4AAC8F890E35A9EB4698B05B@webmail.instant802.com>

Ebtables is a good way to do this - it already has everything you need
in the kernel. Set it up to pass frames to userspace by default, and as
you see new MAC addresses add a new rule to not pass that frame up.

Simon


-----Original Message-----
From: hostap-bounces+simon=instant802.com at shmoo.com
[mailto:hostap-bounces+simon=instant802.com at shmoo.com] On Behalf Of
Gunter Burchardt
Sent: Tuesday, September 07, 2004 11:46 PM
To: Jouni Malinen
Cc: hostap at shmoo.com
Subject: Re: PATCH: wired eapol receive/send


> Is there any particular reason for parsing DHCP packets? One option 
> would be to open packet socket on the same interface with Linux Socket

> filter to capture the packets and then take the layer 2 address from 
> them. Then again, this may not end up being much simpler. Eventually, 
> I would assume this could be replaced with something like iptables 
> firewall queueing packets from unknown MAC addresses for user space 
> processing and all devices would be noticed whenever they send the 
> first packet, no matter whether it is DHCP or something else, i.e., 
> static IP and non-IPv4 hosts would also be processed.

New plan! I will write a kernel module to filter pacets from assoziated
stations. Since 2.4 it is possible to register netfilter hooks. With
help of this, a callback function can decide which packet will be droped
or passed. This module will have a misc device. Over ipctrls you can
configure it (like you did it in hostap driver). I will borrow some code
of hostap driver ;)

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



From gbur  Wed Sep  8 10:24:45 2004
From: gbur (Gunter Burchardt)
Date: Wed, 8 Sep 2004 19:24:45 +0200
Subject: PATCH: wired eapol receive/send
In-Reply-To: <AC8C1F46CD753F4AAC8F890E35A9EB4698B05B@webmail.instant802.com>
References: <AC8C1F46CD753F4AAC8F890E35A9EB4698B05B@webmail.instant802.com>
Message-ID: <20040908172445.GN28682@informatik.uni-rostock.de>

> Ebtables is a good way to do this - it already has everything you need
> in the kernel. Set it up to pass frames to userspace by default, and as
> you see new MAC addresses add a new rule to not pass that frame up.

Sounds like a good idea. Now you have to write QUEUE target for
ebtables and a api for ebtables. There is no api for iptables too.
Adding/Deleting rules by exec could be very slow.

Why no generic ieee802.1x module?

regards
gunter



From tanuja_iv  Wed Sep  8 12:00:59 2004
From: tanuja_iv (tanuja ingale)
Date: Thu, 09 Sep 2004 00:30:59 +0530
Subject: Sniffer mode in hostAP
Message-ID: <BAY12-F28MVhEUsebms0002e9df@hotmail.com>

Hi,

Can anyone tell me how to go about using ethereal/kismet sniffing utilities 
with hostAP to sniff raw 802.11 packets. My interest is in finding out the 
data flow paths from the hostAP station in Managed mode to the Access Point 
in a public place. I'm using a DLink DWL 650 Rev P1 laptop card.

By putting the hostAP in monitor mode # 3, the AP with which my host was 
initially associated with now shows a 00:00:00:00:00:00. I lose the net 
connectivity after that.

Can anyone also tell me how to put the card in promiscuous mode?

Any help will be highly appreciated.
Thanks Ingale

_________________________________________________________________
Movies, music, celeb news. Stay in the loop. http://www.msn.co.in/cinema/ 
With MSN Entertainment!




From tanuja_iv  Wed Sep  8 12:19:38 2004
From: tanuja_iv (tanuja ingale)
Date: Thu, 09 Sep 2004 00:49:38 +0530
Subject: raw 802.11 packet sniffing with hostAP
Message-ID: <BAY12-F4pbKzUKurw7O0002e461@hotmail.com>

Hi,

Can anyone help me in knowing how to put my Dlink DWL 650 card in 
ARPHDR_IEEE80211 promiscuous mode so that i can monitor traffic and obtain 
raw packets?

When I put the card in monitor mode # 3, the AP with which it was previously 
associated, shows 00:00:00:00:00:00 sa the AP address. Can anyone tell me 
where I may be going wrong?

Any help will be highly appreciated.
Thanks!
Tanuja Ingale

_________________________________________________________________
All the news that matters. All the gossip from home. 
http://www.msn.co.in/NRI/ Specially for NRIs!




From jphstap  Wed Sep  8 12:55:56 2004
From: jphstap (Joe Parks)
Date: Wed, 8 Sep 2004 15:55:56 -0400
Subject: raw 802.11 packet sniffing with hostAP
In-Reply-To: <BAY12-F4pbKzUKurw7O0002e461@hotmail.com>
References: <BAY12-F4pbKzUKurw7O0002e461@hotmail.com>
Message-ID: <20040908155556.3fe33ed9@scrodconumulus>

On Thu, 09 Sep 2004 00:49:38 +0530
"tanuja ingale" <tanuja_iv at hotmail.com> wrote:

> Hi,
> 
> Can anyone help me in knowing how to put my Dlink DWL 650 card in 
> ARPHDR_IEEE80211 promiscuous mode so that i can monitor traffic and obtain 
> raw packets?
> 
> When I put the card in monitor mode # 3, the AP with which it was previously 
> associated, shows 00:00:00:00:00:00 sa the AP address. Can anyone tell me 
> where I may be going wrong?

I think you are trying to get the hardware to do something it simply can't do.  Unlike a normal ethernet card it can't sniff all traffic AND participate actively at the same time.   Only one or the other.

This question has been asked on the list before and some of the responses were of the "maybe you can try..." type so check the archives to see if someone more optimistic had something to say on the subject.



From amiandrew  Wed Sep  8 12:50:04 2004
From: amiandrew (Ondrej Zima)
Date: Wed, 08 Sep 2004 21:50:04 +0200
Subject: 0.2.4 deatuhentication reason_code=3
In-Reply-To: <1094159900.4973.132.camel@m2.linora.com>
References: <1094159900.4973.132.camel@m2.linora.com>
Message-ID: <413F626C.5050007@volny.cz>

Kelly Hogan wrote:
> Jouni,
> 
> We recently upgraded to 0.2.4 on soekris with a dual radio
> configuration.  On our master radio, we are getting deauthentication
> reason_code=3 from nodes with signals of -93/-70 which seems odd.
> 
> They then never re-authenticate unless we reboot the client side, then
> they last for only a few minutes.  
> 
> Ideas?  Should we downgrade to 0.1.3?

Hi,
I discover some stupid behaviour. It is not validated, but I have the same sitation. The only solution I make is the reset the card if client not response (in cron I have the script with checking the associated clients and if they not reply to ping, iwpriw reset 0 repair it) It wors, but not great, coz there was delay to run the cron script (was start every fitfth minute).
Now, I try to play with ALC and discover this: after the card is reset, the ALC is set to 1 (ALC is enabled) TX power fluctuate (MIF register 62) and driver will ignore my txpower changes. If I set the ALC to 0 (disabled) and set my txpower settings, it works very good. But only to next card reset, which can appear frequently (it depends on client quality).
For this, I create simple script which check the MIF 62 and test it for my txpower settings. If it vary, it seems the card was reseted and ALC is enabled. In this situation I disable ALC and reset the txpower.
If you use the patch from jbohac, it internaly disables the ALC if card was reseted.

BTW: deathentication for reason_code=3 is deauthentication for client inactivity



-- 
Ondrej Zima <amiandrew at volny.cz>
Member of Czech ATO - Amiga Translators Organization



From tanuja_iv  Wed Sep  8 17:20:13 2004
From: tanuja_iv (tanuja ingale)
Date: Thu, 09 Sep 2004 05:50:13 +0530
Subject: Ethereal and hostAP
Message-ID: <BAY12-F28Sw2vbcsgrP00032ae6@hotmail.com>

Hi,

I used Ethereal with the Dlink DWL 650 card in monitor mode 2. This brings 
down my wlan0 interface. As in, it shows

wlan0     IEEE 802.11b  ESSID:"cuairnet"
          Mode:Monitor  Frequency:2.422GHz  Access Point: 00:00:00:00:00:00
          Bit Rate:1Mb/s   Sensitivity=1/0
          Retry min limit:8   RTS thr=2312 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:53/0  Signal level:-38 dBm  Noise level:-92 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:9  Invalid misc:3177   Missed beacon:0
When I disable the monitor mode, the iwconfig shows the valid AP address.
Can anyone tell me where I may have gone wrong?
Thanks
Tanuja






>Ethereal does not need any special configuration for operation with Host AP 
>driver. You just need to >get recent enough versions of libpcap and 
>Ethereal so that they have support for 802.11 frames (I >use CVS versions) 
>and then you should be able to capture frames with 802.11 headers from 
>wlan0 >when using monitor mode 2 (or 3 in CVS version to get some extra 
>Prism2 info). You will also need to >set wlan0 interface UP for the 
>capture.
>
>--
>Jouni Malinen                                            PGP id EFC895FA

_________________________________________________________________
1 Paisa No Reserve Auctions.  
http://ads2.baazee.com/cgi-bin/banners/redirect.pl?id=2553 T-Shirts, Shirts, 
Kurtas, Apparels.




From kleinveld  Wed Sep  8 17:59:13 2004
From: kleinveld (Arnaud)
Date: Thu, 09 Sep 2004 08:59:13 +0800
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040908172445.GN28682@informatik.uni-rostock.de>
References: <AC8C1F46CD753F4AAC8F890E35A9EB4698B05B@webmail.instant802.com>
	<20040908172445.GN28682@informatik.uni-rostock.de>
Message-ID: <413FAAE1.3090902@pacific.net.sg>

Hi Gunter,

I have written a quick and dirty solution to insert and remove rules using 
iptables. Instead of doing an exec you can use integrate iptables.c in your 
program. Iptables.c is a small program that passes the commands as given on 
commandline to the iptables core programs. I don't think what I made is a nice 
solution but it works and without doing a exec. There must be better ways to do 
this. If you're interrested I will send you the code.

Regards,
Arnaud


Gunter Burchardt wrote:
>>Ebtables is a good way to do this - it already has everything you need
>>in the kernel. Set it up to pass frames to userspace by default, and as
>>you see new MAC addresses add a new rule to not pass that frame up.
> 
> 
> Sounds like a good idea. Now you have to write QUEUE target for
> ebtables and a api for ebtables. There is no api for iptables too.
> Adding/Deleting rules by exec could be very slow.
> 
> Why no generic ieee802.1x module?
> 
> regards
> gunter
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



From zen_hacker  Wed Sep  8 17:38:02 2004
From: zen_hacker (Brian Sturgill)
Date: Thu, 09 Sep 2004 00:38:02 +0000
Subject: Ethereal and hostAP
Message-ID: <BAY13-F306zsKXoBQve0000ef86@hotmail.com>

In monitor mode you are not associated to an AP so no mac address shows in 
iwconfig. You are not participating in a network. It is just listening for 
wireless packets.

Brian


>From: "tanuja ingale" <tanuja_iv at hotmail.com>
>To: hostap at shmoo.com
>Subject: Ethereal and hostAP
>Date: Thu, 09 Sep 2004 05:50:13 +0530
>
>Hi,
>
>I used Ethereal with the Dlink DWL 650 card in monitor mode 2. This brings 
>down my wlan0 interface. As in, it shows
>
>wlan0     IEEE 802.11b  ESSID:"cuairnet"
>          Mode:Monitor  Frequency:2.422GHz  Access Point: 00:00:00:00:00:00
>          Bit Rate:1Mb/s   Sensitivity=1/0
>          Retry min limit:8   RTS thr=2312 B   Fragment thr:off
>          Encryption key:off
>          Power Management:off
>          Link Quality:53/0  Signal level:-38 dBm  Noise level:-92 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:9  Invalid misc:3177   Missed beacon:0
>When I disable the monitor mode, the iwconfig shows the valid AP address.
>Can anyone tell me where I may have gone wrong?
>Thanks
>Tanuja
>
>
>
>
>
>
>>Ethereal does not need any special configuration for operation with Host 
>>AP driver. You just need to >get recent enough versions of libpcap and 
>>Ethereal so that they have support for 802.11 frames (I >use CVS versions) 
>>and then you should be able to capture frames with 802.11 headers from 
>>wlan0 >when using monitor mode 2 (or 3 in CVS version to get some extra 
>>Prism2 info). You will also need to >set wlan0 interface UP for the 
>>capture.
>>
>>--
>>Jouni Malinen                                            PGP id EFC895FA
>
>_________________________________________________________________
>1 Paisa No Reserve Auctions.  
>http://ads2.baazee.com/cgi-bin/banners/redirect.pl?id=2553 T-Shirts, 
>Shirts, Kurtas, Apparels.
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From jkmaline  Wed Sep  8 18:49:13 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 8 Sep 2004 18:49:13 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040908140458.GA8673@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
Message-ID: <20040909014913.GA7368@jm.kir.nu>

On Wed, Sep 08, 2004 at 04:04:58PM +0200, Wilfried Klaebe wrote:

> I just tested with ieee8021x=0 and wpa=0 instead of ieee8021x=1 and wpa=2:
> Same thing. ARP requests incoming on wlan0, but not showing up on br0.
> 
> I also tried it the other way round: If I try to ping the laptop on the
> WLAN, I can see the ARP requests going out on br0 and then eth0, but not
> wlan0.
> 
> It seems not to be a problem of encryption, then, but somewhere else.

OK, that's good to know; limits the area quite a bit.

> wlan0     Link encap:Ethernet  HWaddr 00:40:05:AF:4B:C9  
>           inet6 addr: fe80::240:5ff:feaf:4bc9/64 Scope:Link

Any particular reason for configuring that IPv6 address on wlan0? I
don't know whether it can cause something like this, but you did not
have similar address on eth0 and one should not configure IP addresses
for the devices that are in a bridge..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep  8 18:58:29 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 8 Sep 2004 18:58:29 -0700
Subject: PMK with LEAP in the WPA supplicant
In-Reply-To: <20040908161500.65336.qmail@web21421.mail.yahoo.com>
References: <20040908161500.65336.qmail@web21421.mail.yahoo.com>
Message-ID: <20040909015829.GB7368@jm.kir.nu>

On Wed, Sep 08, 2004 at 09:15:00AM -0700, J I wrote:

> I wanted to use LEAP with  WPA supplicant. As per my understanding, wpa_supplicant_process_1_of_4 function calls eapol_sm_get_key with the key size as 256, while the key size obtained with LEAP is only 128 bit.

Yes, this is the normal case and the exact reason for wpa_supplicant
README to say that LEAP is not supported with WPA..

> With this, I am not sure if LEAP can be used with WPA where TKIP is configured as a unicast/group cipher suite. 

There may be some proprietary Cisco magic for generating a 256-bit
session key from LEAP or maybe more likely for converting the 128-bit
key to a 256-bit one. If someone can either provide the details or point
to a publicly available spec, I should be able to implement this in
wpa_supplicant..

-- 
Jouni Malinen                                            PGP id EFC895FA



From mcgrof  Wed Sep  8 22:56:57 2004
From: mcgrof (Luis R. Rodriguez)
Date: Thu, 9 Sep 2004 01:56:57 -0400
Subject: WPA PSK - AUTH, ASSOC, 4-Way Handshake
Message-ID: <20040909055657.GM31207@ruslug.rutgers.edu>


Can someone tell me at what point the AUTH and ASSOC wireless
events are caught when a STA is associating to an AP using wpa_supplicant?
Is the AUTH sent, and in reponse the 4-way handshake occur? And then you
get an ASSOC at the 4th step of the handshake? Or does both of these
occur (AUTH, and ASSOC) occur prior to the 4-way handshake?

While at it, can someone please send me wpa_supplicant -d logs and iwevent logs
of a successfull connection using PSK and TKIP?

Thanks,

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E



From vda  Wed Sep  8 23:11:26 2004
From: vda (Denis Vlasenko)
Date: Thu, 9 Sep 2004 09:11:26 +0300
Subject: Ethereal and hostAP
In-Reply-To: <BAY12-F28Sw2vbcsgrP00032ae6@hotmail.com>
References: <BAY12-F28Sw2vbcsgrP00032ae6@hotmail.com>
Message-ID: <200409090911.26361.vda@port.imtp.ilyichevsk.odessa.ua>

On Thursday 09 September 2004 03:20, tanuja ingale wrote:
> Hi,
>
> I used Ethereal with the Dlink DWL 650 card in monitor mode 2. This brings
> down my wlan0 interface. As in, it shows
>
> wlan0     IEEE 802.11b  ESSID:"cuairnet"
>           Mode:Monitor  Frequency:2.422GHz  Access Point: 00:00:00:00:00:00
>           Bit Rate:1Mb/s   Sensitivity=1/0
>           Retry min limit:8   RTS thr=2312 B   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:53/0  Signal level:-38 dBm  Noise level:-92 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:9  Invalid misc:3177   Missed beacon:0
> When I disable the monitor mode, the iwconfig shows the valid AP address.
> Can anyone tell me where I may have gone wrong?
> Thanks
> Tanuja

In monitor mode, you aren't associated with anybody.
You are simply receiving every packet. No filtering
on BSSID, unknown crypto key, etc, is done.
--
vda




From jkmaline  Wed Sep  8 23:45:11 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 8 Sep 2004 23:45:11 -0700
Subject: WPA PSK - AUTH, ASSOC, 4-Way Handshake
In-Reply-To: <20040909055657.GM31207@ruslug.rutgers.edu>
References: <20040909055657.GM31207@ruslug.rutgers.edu>
Message-ID: <20040909064511.GE7368@jm.kir.nu>

On Thu, Sep 09, 2004 at 01:56:57AM -0400, Luis R. Rodriguez wrote:

> Can someone tell me at what point the AUTH and ASSOC wireless
> events are caught when a STA is associating to an AP using wpa_supplicant?
> Is the AUTH sent, and in reponse the 4-way handshake occur? And then you
> get an ASSOC at the 4th step of the handshake? Or does both of these
> occur (AUTH, and ASSOC) occur prior to the 4-way handshake?

If by AUTH you mean IEEE 802.11 authentication, the last option wuld be
correct. In other words:

0) Scan results, wpa_supplicants configures driver
1) IEEE 802.11 authentication (wpa_supplicant doesn't really care about
   this)
2) IEEE 802.11 association (New Access Point)
3) AP starts 4-Way Handshake by sending an EAPOL-Key frame
4) wpa_supplicant replies with EAPOL-Key frame and then another pair of
   EAPOL-Key frames
5) wpa_supplicant configures the pairwise key to the driver
6) Group Key handshake (encrypted) if WPA is used (WPA2 combines this
   with four way handshake)
7) wpa_supplicant configures the group key to the driver
8) data connection is fully operational

> While at it, can someone please send me wpa_supplicant -d logs and iwevent logs
> of a successfull connection using PSK and TKIP?

I'm lazy, so you can have WPA-PSK with CCMP which happens to be my
current configuration ;-).

Waiting for Wireless Events...
06:32:27.735722    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:28.013444    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:29.306483    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:30.125096    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:30.528911    wifi0    Scan request completed
06:32:30.533789    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:30.545894    wlan0    Channel:1
06:32:30.547007    wifi0    New Access Point/Cell address:00:00:00:00:00:00
06:32:30.559103    wlan0    ESSID:"jkm private"
06:32:30.588124    wifi0    New Access Point/Cell address:00:09:5B:95:E0:4E


wpa_supplicant debug log is attached.

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=10 (from group name 'wheel')
Priority group 10
   id=0 ssid='jkm private'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:06:25:11:57:6c
wpa_driver_wext_set_wpa
SIOCGIWRANGE: WE(compiled)=18 WE(source)=18 enc_capa=0xf
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=11):
     6a 6b 6d 20 70 72 69 76 61 74 65                  jkm private     
Wireless event: cmd=0x8b19 len=12
Received 236 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 10
0: 00:09:5b:95:e0:4e ssid='jkm private' wpa_ie_len=26 rsn_ie_len=0
   selected
Trying to associate with 00:09:5b:95:e0:4e (SSID='jkm private' freq=2412 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
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
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
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
Wireless event: cmd=0x8b1a len=23
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:95:e0:4e
Association event - clear replay counter
Associated to a new BSS: BSSID=00:09:5b:95:e0:4e
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
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:09:5b:95:e0:4e
Setting authentication timeout: 10 sec 0 usec
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:95:e0:4e (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): f8 9f 32 06 06 5a 66 9d 2e bc 9f 64 15 7b 93 6b ba 04 f8 94 de f4 7c 35 ce 24 c3 95 23 9c 13 de
WPA: PMK - hexdump(len=32): <removed>
WPA: PTK - hexdump(len=64): <removed>
WPA: EAPOL-Key MIC - hexdump(len=16): 75 68 2f 81 01 3a ec 3c 06 aa 91 db 4e 24 cf eb
WPA: Sending EAPOL-Key 2/4
RX EAPOL from 00:09:5b:95:e0:4e
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=121
  EAPOL-Key type=254
WPA: RX message 3 of 4-Way Handshake from 00:09:5b:95:e0:4e (ver=2)
WPA: Sending EAPOL-Key 4/4
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=3 key_idx=0 set_tx=1 seq_len=6 key_len=16
RX EAPOL from 00:09:5b:95:e0:4e
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
WPA: RX message 1 of Group Key Handshake from 00:09:5b:95:e0:4e (ver=2)
WPA: Group Key - hexdump(len=16): db 33 c4 d2 a4 62 8d bb 3e b0 09 b5 f8 3f 67 d3
WPA: Installing GTK to the driver (keyidx=1 tx=0).
WPA: RSC - hexdump(len=6): 01 00 00 00 00 00
wpa_driver_wext_set_key: alg=3 key_idx=1 set_tx=0 seq_len=6 key_len=16
WPA: Sending EAPOL-Key 2/2
WPA: Key negotiation completed with 00:09:5b:95:e0:4e [PTK=CCMP GTK=CCMP]
Cancelling authentication timeout
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:09:5b:95:e0:4e
EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
WPA: RX message 1 of Group Key Handshake from 00:09:5b:95:e0:4e (ver=2)
WPA: Group Key - hexdump(len=16): 12 bf ee 79 58 70 a9 eb 18 88 58 5f a0 54 3c 6e
WPA: Installing GTK to the driver (keyidx=2 tx=0).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=3 key_idx=2 set_tx=0 seq_len=6 key_len=16
WPA: Sending EAPOL-Key 2/2
WPA: Key negotiation completed with 00:09:5b:95:e0:4e [PTK=CCMP GTK=CCMP]
Cancelling authentication timeout
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
Signal 2 received - terminating
wpa_driver_wext_deauthenticate
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
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures


From mcgrof  Thu Sep  9 00:29:08 2004
From: mcgrof (Luis R. Rodriguez)
Date: Thu, 9 Sep 2004 03:29:08 -0400
Subject: WPA PSK - AUTH, ASSOC, 4-Way Handshake
In-Reply-To: <20040909064511.GE7368@jm.kir.nu>
References: <20040909055657.GM31207@ruslug.rutgers.edu>
	<20040909064511.GE7368@jm.kir.nu>
Message-ID: <20040909072908.GN31207@ruslug.rutgers.edu>

On Wed, Sep 08, 2004 at 11:45:11PM -0700, Jouni Malinen wrote:
> On Thu, Sep 09, 2004 at 01:56:57AM -0400, Luis R. Rodriguez wrote:
> 
> > Can someone tell me at what point the AUTH and ASSOC wireless
> > events are caught when a STA is associating to an AP using wpa_supplicant?
> > Is the AUTH sent, and in reponse the 4-way handshake occur? And then you
> > get an ASSOC at the 4th step of the handshake? Or does both of these
> > occur (AUTH, and ASSOC) occur prior to the 4-way handshake?
> 
> If by AUTH you mean IEEE 802.11 authentication, the last option wuld be
> correct. In other words:
> 

This is where I am with prism54 wpa_supplicant:

> 0) Scan results, wpa_supplicants configures driver

Check

> 1) IEEE 802.11 authentication (wpa_supplicant doesn't really care about
>    this)
> 2) IEEE 802.11 association (New Access Point)

I'm not seeing any of these sent caught by iwevent. I actually also do
not see these on your iwevent log too, but I checked and noticed hostap
src does not send a custom wireless event in the AUTH/ASSOC 802.11
event.

Here is what I usually see in my iwevent log when associating to a
non-WPA AP:

11:06:42.099028    eth0     Custom driver event:Authenticate request to 00:09:5B:9A:D8:62  : ACCEPTED  (00)
11:06:42.116797    eth0     Custom driver event:Associate request to 00:09:5B:9A:D8:62  : ACCEPTED  (00)
11:06:44.001712    eth0     New Access Point/Cell address:00:09:5B:9A:D8:62


Here is what I'm seeing once I turn wpa_supplicant on:

11:06:56.806540    eth0     Custom driver event:Received a beacon from an unkown AP to 00:09:5B:D4:C0:E0  (00)
11:06:59.897279    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:00.058512    eth0     ESSID:"asdf"
11:07:00.166238    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:00.269905    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:08.071873    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:08.071970    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:08.072022    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:08.072072    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:08.174560    eth0     ESSID:"asdf"
11:07:09.103046    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:09.205553    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:09.307959    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:16.194520    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:16.194617    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:16.194669    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)
11:07:16.194719    eth0     Custom driver event:Received a probe from client to 00:09:5B:D4:C0:E0  (00)

This is where I'm at. 

<-- snip -->

Also, bellow I comment on what I'm seeing.

> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group=10 (from group name 'wheel')
> Priority group 10
>    id=0 ssid='jkm private'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Own MAC address: 00:06:25:11:57:6c
> wpa_driver_wext_set_wpa
> SIOCGIWRANGE: WE(compiled)=18 WE(source)=18 enc_capa=0xf
> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_countermeasures
> wpa_driver_wext_set_drop_unencrypted
> Setting scan request: 0 sec 100000 usec
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> 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
> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=11):
>      6a 6b 6d 20 70 72 69 76 61 74 65                  jkm private     
> Wireless event: cmd=0x8b19 len=12
> Received 236 bytes of scan results (1 BSSes)
> Scan results: 1
> Selecting BSS from priority group 10
> 0: 00:09:5b:95:e0:4e ssid='jkm private' wpa_ie_len=26 rsn_ie_len=0
>    selected
> Trying to associate with 00:09:5b:95:e0:4e (SSID='jkm private' freq=2412 MHz)
> Cancelling scan request
> Automatic auth_alg selection: 0x1
> WPA: using IEEE 802.11i/D3.0
> WPA: using GTK CCMP
> WPA: using PTK CCMP
> WPA: using KEY_MGMT WPA-PSK
> WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02

I get this line and then:

WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8c02 len=74
Custom wireless event: 'Received a beacon from an unkown AP to 00:09:5B:D4:C0:E0  (00)'
Wireless event: cmd=0x8c02 len=67
Custom wireless event: 'Received a probe from client to 00:09:5B:D4:C0:E0  (00)'
Wireless event: cmd=0x8b1a len=16
Wireless event: cmd=0x8c02 len=67
Custom wireless event: 'Received a probe from client to 00:09:5B:D4:C0:E0  (00)'
Wireless event: cmd=0x8c02 len=67
Custom wireless event: 'Received a probe from client to 00:09:5B:D4:C0:E0  (00)'
Wireless event: cmd=0x8c02 len=67
Custom wireless event: 'Received a probe from client to 00:09:5B:D4:C0:E0  (00)'
Authentication with 00:00:00:00:00:00 timed out.

It seems evident to me AUTH/ASSOC in MLME extended mode are not being
sent out. I am not sure why and am trying to figure it out.
Suggestions/comments are welcomed.

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E



From karel  Thu Sep  9 00:35:32 2004
From: karel (Karel Rericha)
Date: Thu, 09 Sep 2004 09:35:32 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040909014913.GA7368@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>	<20040907040121.GC7392@jm.kir.nu>	<20040907150902.GA5222@kaos.in-kiel.de>	<20040908061536.GH7362@jm.kir.nu>	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
Message-ID: <414007C4.2010909@maxent.cz>

Jouni Malinen napsal(a):

>>wlan0     Link encap:Ethernet  HWaddr 00:40:05:AF:4B:C9  
>>          inet6 addr: fe80::240:5ff:feaf:4bc9/64 Scope:Link
>>    
>>
>
>Any particular reason for configuring that IPv6 address on wlan0? I
>don't know whether it can cause something like this, but you did not
>have similar address on eth0 and one should not configure IP addresses
>for the devices that are in a bridge..
>
>  
>
I would guess that this is some kind of default behaviour, I have same 
bridge config and my
wlan0 and br0 have IPv6 identical too. I did nothing to set any of them 
AFAIK. I have Mandrake
10.0, 2.6.3-14 kernel, hostap 0.2.4. Bridge is running fine, but I don?t 
use 802.1x (anyway it looks
like this is not the problem).

Karel Rericha




From sime  Thu Sep  9 01:30:46 2004
From: sime (Simon Males)
Date: Thu, 09 Sep 2004 18:30:46 +1000
Subject: WPA-PSK accepted for key management, but no PSK configured.
Message-ID: <414014B6.5040407@anticd.org>

$ wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
Line 192: WPA-PSK accepted for key management, but no PSK configured.
Line 192: failed to parse network block.

.config:
CONFIG_WIRELESS_EXTENSION=y
CONFIG_MSCHAPV2=y
CONFIG_DRIVER_HOSTAP=y
CONFIG_EAP_PEAP=y

I don't think I need a PSK because I have a password.

network={
	ssid="ACHERNAR-BG"
	proto=WPA
	eap=PEAP
#	ca_cert=
	pairwise=TKIP
	identity="ssm98 at uow.edu.au"
	password="****"
#	phase1="peapver=0"
#	phase2="auth=MSCHAPV2"
}				# Line 192

Related posting:
http://mail.iocaine.com/pipermail/hostap/2004-August/007583.html

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



From rocci  Thu Sep  9 02:45:29 2004
From: rocci (Rocci)
Date: Thu, 09 Sep 2004 19:45:29 +1000
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <414014B6.5040407@anticd.org>
References: <414014B6.5040407@anticd.org>
Message-ID: <41402639.5050509@rocknetworks.net.au>

Simon Males wrote:

> $ wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
> Line 192: WPA-PSK accepted for key management, but no PSK configured.
> Line 192: failed to parse network block.
>
> .config:
> CONFIG_WIRELESS_EXTENSION=y
> CONFIG_MSCHAPV2=y
> CONFIG_DRIVER_HOSTAP=y
> CONFIG_EAP_PEAP=y
>
> I don't think I need a PSK because I have a password.
>
> network={
>     ssid="ACHERNAR-BG"
>     proto=WPA
>     eap=PEAP
> #    ca_cert=
>     pairwise=TKIP
>     identity="ssm98 at uow.edu.au"
>     password="****"
> #    phase1="peapver=0"
> #    phase2="auth=MSCHAPV2"
> }                # Line 192
>
> Related posting:
> http://mail.iocaine.com/pipermail/hostap/2004-August/007583.html
>
UOW network does not use PSK, it uses TKIP + PEAP + MSCHAPv2

You need to enable these options in your compilation & your config file.

- Rocci.



From wk-hostap  Thu Sep  9 03:33:35 2004
From: wk-hostap (Wilfried Klaebe)
Date: Thu, 9 Sep 2004 12:33:35 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040909014913.GA7368@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
Message-ID: <20040909103335.GA13259@kaos.in-kiel.de>

Am Wed, Sep 08, 2004 at 06:49:13PM -0700 schrieb Jouni Malinen:
> On Wed, Sep 08, 2004 at 04:04:58PM +0200, Wilfried Klaebe wrote:
> 
> > I just tested with ieee8021x=0 and wpa=0 instead of ieee8021x=1 and wpa=2:
> > Same thing. ARP requests incoming on wlan0, but not showing up on br0.
> > 
> > I also tried it the other way round: If I try to ping the laptop on the
> > WLAN, I can see the ARP requests going out on br0 and then eth0, but not
> > wlan0.
> > 
> > It seems not to be a problem of encryption, then, but somewhere else.
> 
> OK, that's good to know; limits the area quite a bit.
> 
> > wlan0     Link encap:Ethernet  HWaddr 00:40:05:AF:4B:C9  
> >           inet6 addr: fe80::240:5ff:feaf:4bc9/64 Scope:Link
> 
> Any particular reason for configuring that IPv6 address on wlan0? I
> don't know whether it can cause something like this, but you did not
> have similar address on eth0 and one should not configure IP addresses
> for the devices that are in a bridge..

Erm... They were there on the other devices, but I deleted the lines
there...

It's a link-local address, they're automatically configured for every
interface at "ifconfig up".

At the moment I'm trying to understand what happens after netif_rx() in
the upper layers in linux... I hope to find the problem (or at least
the solution) there. The packets do arrive in the upper layers correctly,
else tcpdump would not be able to see them, but then something seems to
hinder them from arriving at the bridge.

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From gbur  Thu Sep  9 03:55:07 2004
From: gbur (Gunter Burchardt)
Date: Thu, 9 Sep 2004 12:55:07 +0200
Subject: hostapd with wpa dont work on big endian systems
Message-ID: <20040909105507.GO28682@informatik.uni-rostock.de>

Hello,

I tested hostap with wpa on a big endian system (IXP425). I think there
is a problem in MIC calculation. Here a log of hostapd. I will try to
find the problem.

wlan0: STA 00:0e:a6:c8:5a:88 IEEE 802.1X: decapsulated EAP packet
(code=3 id=15 len=4) from RADIUS server: EAP Success
IEEE 802.1X: 00:0e:a6:c8:5a:88 BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending EAP Packet to 00:0e:a6:c8:5a:88 (identifier 15)
IEEE 802.1X: 00:0e:a6:c8:5a:88 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0e:a6:c8:5a:88 BE_AUTH entering state IDLE
IEEE 802.1X: 00:0e:a6:c8:5a:88 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:0e:a6:c8:5a:88 REAUTH_TIMER entering state INITIALIZE
Received 40 bytes management frame
RX frame - hexdump(len=40): 0a 02 02 01 00 0e a6 c8 5a 88 00 02 6f 05
dc 3c 00 02 6f 05 dc 3c 80 d7 aa aa 03 00 00 00 88 8e 01 00 00 04 03
DATA (TX callback) ACK
IEEE 802.1X: 00:0e:a6:c8:5a:88 TX status - version=1 type=0 length=4 -
ack=1
WPA: 00:0e:a6:c8:5a:88 WPA_PTK entering state INITPMK
WPA: 00:0e:a6:c8:5a:88 WPA_PTK entering state PTKSTART
wlan0: STA 00:0e:a6:c8:5a:88 WPA: sending 1/4 msg of 4-Way Handshake
Received 131 bytes management frame
RX frame - hexdump(len=131): 0a 02 02 01 00 0e a6 c8 5a 88 00 02 6f 05
dc 3c 00 02 6f 05 dc 3c 90 d7 aa aa 03 00 00 00 88 8e 01 03 00 5f f
DATA (TX callback) ACK
IEEE 802.1X: 00:0e:a6:c8:5a:88 TX status - version=1 type=3 length=95 -
ack=1
Received 155 bytes management frame
RX frame - hexdump(len=155): 08 01 02 01 00 02 6f 05 dc 3c 00 0e a6 c8
5a 88 00 02 6f 05 dc 3c 10 25 aa aa 03 00 00 00 88 8e 01 03 00 77 f
DATA
IEEE 802.1X: 123 bytes from 00:0e:a6:c8:5a:88
   IEEE 802.1X: version=1 type=3 length=119
wlan0: STA 00:0e:a6:c8:5a:88 WPA: received EAPOL-Key frame (2/4
Pairwise)
WPA: 00:0e:a6:c8:5a:88 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 58 31 c6 e7 aa 8f 5c 89 aa 14 b7 10 63 9e ae cc
a0 9b 1f 4f 3e 81 3c 73 9f 7e bb 66 b3 eb 84 de
PTK - hexdump(len=64): 2a 6c 29 b6 42 ac 95 db 02 f8 5c 75 26 ce 86 2c
94 6a 2d 37 cf 8d 47 30 9b 80 d4 dd 45 5a fd 14 8b 4d ff cc 4a 6d 6
wlan0: STA 00:0e:a6:c8:5a:88 WPA: invalid MIC in msg 2/4 of 4-Way
Handshake

regards
gunter



From mstuff  Thu Sep  9 03:55:16 2004
From: mstuff (Morgan Read)
Date: Thu, 09 Sep 2004 22:55:16 +1200
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <20040907025300.GB7392@jm.kir.nu>
References: <413D11D0.8050203@pl.net> <20040907025300.GB7392@jm.kir.nu>
Message-ID: <41403694.80307@pl.net>

Below are the outputs from wpa_supp with the wext drivers instead of 
hostap.  It doesn't look much different from the hostap debug?  Any 
guidance form here would be very much appreciated?
Regards,
Morgan.


***************************
[root at morgansmachine root]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

wifi0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:0D:ED:99:37:C0
           Bit Rate:11Mb/s   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:ABCD-EF01-2345-6789-ABCD-EF01-23   Security 
mode:open
           Power Management:off
           Link Quality:11/70  Signal level:-81 dBm  Noise level:-93 dBm
           Rx invalid nwid:0  Rx invalid crypt:82  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:3347   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:0D:ED:99:37:C0
           Bit Rate:11Mb/s   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:ABCD-EF01-2345-6789-ABCD-EF01-23   Security 
mode:open
           Power Management:off
           Link Quality:11/70  Signal level:-81 dBm  Noise level:-93 dBm
           Rx invalid nwid:0  Rx invalid crypt:82  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:3347   Missed beacon:0

[root at morgansmachine root]#
***************************
[root at morgansmachine root]# wpa_supplicant -iwlan0 -Dwext 
-c/etc/wpa_supplicant.conf -d
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=0
Priority group 0
    id=0 ssid='uoa'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa: enabled=1 - not yet implemented
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures: enabled=0 - not yet implemented
wpa_driver_wext_set_drop_unencrypted: enabled=1 - not yet implemented
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
Network configuration found for the current AP
EAPOL: External notification - portControl=Auto
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Disconnect event - remove keys
wpa_driver_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
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Already associated with a configured network - generating associated event
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
Network configuration found for the current AP
EAPOL: External notification - portControl=Auto
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec

<SNIP>

Setting authentication timeout: 10 sec 0 usec
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Signal 2 received - terminating
wpa_driver_wext_deauthenticate - not yet implemented
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa: enabled=0 - not yet implemented
wpa_driver_wext_set_drop_unencrypted: enabled=0 - not yet implemented
wpa_driver_wext_set_countermeasures: enabled=0 - not yet implemented
[root at morgansmachine root]#
***************************
[root at morgansmachine root]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

wifi0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:0D:ED:99:37:C0
           Bit Rate:5.5Mb/s   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:11/70  Signal level:-82 dBm  Noise level:-94 dBm
           Rx invalid nwid:0  Rx invalid crypt:523  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:6104   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"uoa"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:0D:ED:99:37:C0
           Bit Rate:5.5Mb/s   Sensitivity=1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:11/70  Signal level:-82 dBm  Noise level:-94 dBm
           Rx invalid nwid:0  Rx invalid crypt:523  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:6104   Missed beacon:0

[root at morgansmachine root]#
***************************


Jouni Malinen wrote:
> On Tue, Sep 07, 2004 at 01:41:36PM +1200, Morgan Read wrote:
> 
> 
>>>Failed to enable WPA in the driver.
>>>
>>
>>I updated the station firmware to 1.7.4 in ram and got the second output
>>(second) below.  Also, in the second instance the AP seemed to
>>"disappear" and the MAC changed to all 4s while wpa_supplicant was
>>running (it didn't exit itself) and when I exited wpa_supplicant (with
>>ctrl-C) the AP came back with a real MAC.
>>
>>But, this is all a bit strange because I shouldn't be doing anything
>>with wpa if I'm using 802.1x??  So, I think something must be
>>fundamentaly amiss?
> 
> 
> The current version of the Host AP driver interface in wpa_supplicant
> always enables WPA support and consequently, requires new station
> firmware. You might be able to use IEEE 802.1X with driver_wext.c (add
> CONFIG_DRIVER_WEXT=y to .config, use ap_scan=0 in wpa_supplicant.conf,
> and -Dwext on command line).
> 
> 
>>Already associated with a configured network - generating associated event
>>Association event - clear replay counter
>>Associated to a new BSS: BSSID=44:44:44:44:44:44
> 
> 
>>ap_scan=0
> 
> 
> I would recommend starting with ap_scan=1 when using Host AP driver.
> Your debug log showed that wpa_supplicant was not receiving any EAPOL
> packets from the AP and then timing out. ap_scan=1 has received much
> more testing..
> 
> 
>>	eap=PEAP MSCHAPV2
> 
> 
> If you are using EAP-PEAP with EAP-MSCHAPv2 as the inner (tunneled,
> phase 2) authentication, you only need to have PEAP on this line. Phase
> 2 method is configured below with:
> 
> 
>>	phase2="auth=MSCHAPV2"
> 
> 

-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From tchouto  Thu Sep  9 04:12:21 2004
From: tchouto (Jean-Jacques Tchouto)
Date: Thu, 9 Sep 2004 13:12:21 +0200
Subject: hostap0.2.4 on fedora core2 WEP problem
Message-ID: <200409091312.21411.tchouto@fokus.fraunhofer.de>

Hi,
I successfull install the hostap driver on my PC
running fedora core 2 with the 2.6.8-1.521 kernel.
I have the following problem, wenn trying to set
the WEB key (e.g. iwconfig wlan0 key 12345):

Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.

Does some one also have such a problem ?
Does some one running the hostap as an AP successfully 
with fedora core 2?

I need some advices.

Best Regards,

Jean-Jacques.
-- 
>------------------------------------------------------------------------------->
> Dipl-Ing. Jean-Jacques Tchouto 		Tel.: +49-30-34637268		>
> Advanced Network Technologies and Systems	Fax : +49-30-34838268		>
> Kaiserin-Augusta-Allee 31			10589				>
> CATS, FHG-FOKUS, BERLIN GERMANY	e-mail: tchouto at fokus.fraunhofer.de	>
> http://www.fokus.fraunhofer.de/usr/tchouto	Mobile: +49 179 5722065		>
>------------------------------------------------------------------------------->



From jkmaline  Thu Sep  9 06:52:15 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 9 Sep 2004 06:52:15 -0700
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <414014B6.5040407@anticd.org>
References: <414014B6.5040407@anticd.org>
Message-ID: <20040909135215.GA7164@jm.kir.nu>

On Thu, Sep 09, 2004 at 06:30:46PM +1000, Simon Males wrote:

> $ wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
> Line 192: WPA-PSK accepted for key management, but no PSK configured.

> I don't think I need a PSK because I have a password.

Well, you would not need, if you were to disable PSK.. key_mgmt default
to include both WPA-PSK and WPA-EAP, so you need to explicitly set it to
key_mgmt=WPA-EAP for this case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Sep  9 06:54:11 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 9 Sep 2004 06:54:11 -0700
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <41402639.5050509@rocknetworks.net.au>
References: <414014B6.5040407@anticd.org>
	<41402639.5050509@rocknetworks.net.au>
Message-ID: <20040909135411.GB7164@jm.kir.nu>

On Thu, Sep 09, 2004 at 07:45:29PM +1000, Rocci wrote:
> Simon Males wrote:
> >CONFIG_MSCHAPV2=y
> >CONFIG_EAP_PEAP=y

> >    proto=WPA
> >    eap=PEAP
> >    pairwise=TKIP

> UOW network does not use PSK, it uses TKIP + PEAP + MSCHAPv2
> 
> You need to enable these options in your compilation & your config file.

??

Based on the about .config and wpa_supplicant.conf, they were enabled..

-- 
Jouni Malinen                                            PGP id EFC895FA



From sime  Thu Sep  9 07:45:17 2004
From: sime (Simon Males)
Date: Fri, 10 Sep 2004 00:45:17 +1000
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <20040909135215.GA7164@jm.kir.nu>
References: <414014B6.5040407@anticd.org> <20040909135215.GA7164@jm.kir.nu>
Message-ID: <41406C7D.9000707@anticd.org>


Jouni Malinen wrote:
> Well, you would not need, if you were to disable PSK.. key_mgmt default
> to include both WPA-PSK and WPA-EAP, so you need to explicitly set it to
> key_mgmt=WPA-EAP for this case.

Thanks Jouni. Rocci has actually assisted me off list.

I am running a hostap card so I need hostapd to manage the keys in 
station mode (not quite sure what that means).

so my wpa_supplicant contains
        ssid="ACHERNAR-BG"
        scan_ssid=1
        key_mgmt=WPA-EAP
        eap=PEAP
        pairwise=TKIP
        group=TKIP
        ca_cert="/etc/cert/cert.pem"
        phase1="peaplabel=0"
        phase2="auth=MSCHAPV2"
        priority=10

hostapd currently contains
	wpa=0
	wpa_key_mgmt=WPA-EAP
	wpa_pairwise=TKIP
	ssid=ACHERNAR-BG

The rest is default. Running wpa_supplicant I get the following.

EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=1
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to enable WPA in the driver.
wpa_driver_hostap_set_wpa: enabled=0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported



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




From jwright  Thu Sep  9 10:00:41 2004
From: jwright (Joshua Wright)
Date: Thu, 09 Sep 2004 13:00:41 -0400
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <41406C7D.9000707@anticd.org>
References: <414014B6.5040407@anticd.org> <20040909135215.GA7164@jm.kir.nu>
	<41406C7D.9000707@anticd.org>
Message-ID: <41408C39.80607@hasborg.com>

Simon Males wrote:
 > wpa_driver_hostap_set_wpa: enabled=1
 > ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
 > ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
 > Failed to enable WPA in the driver.
 > wpa_driver_hostap_set_wpa: enabled=0
 > ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
 > ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported

Jouni pointed out to me that this error is due to incompatible firmware. 
  You need to update the firmware of your card to use wpa_supplicant 
(station firmware 1.7.0 or later).

You can get updated firmware for your Prism2 wireless card from 
http://www.netgate.com/support/prism_firmware/.

-Josh
-- 
-Joshua Wright
jwright at hasborg.com
http://home.jwu.edu/jwright/

pgpkey: http://home.jwu.edu/jwright/pgpkey.htm
fingerprint: FDA5 12FC F391 3740 E0AE BDB6 8FE2 FC0A D44B 4A73

Today I stumbled across the world's largest hotspot.  The SSID is "linksys".



From rocci  Thu Sep  9 15:20:00 2004
From: rocci (Rocci)
Date: Fri, 10 Sep 2004 08:20:00 +1000
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <20040909135411.GB7164@jm.kir.nu>
References: <414014B6.5040407@anticd.org>	<41402639.5050509@rocknetworks.net.au>
	<20040909135411.GB7164@jm.kir.nu>
Message-ID: <4140D710.5080905@rocknetworks.net.au>

Jouni Malinen wrote:

>On Thu, Sep 09, 2004 at 07:45:29PM +1000, Rocci wrote:
>  
>
>>Simon Males wrote:
>>    
>>
>>>CONFIG_MSCHAPV2=y
>>>CONFIG_EAP_PEAP=y
>>>      
>>>
>
>  
>
>>>   proto=WPA
>>>   eap=PEAP
>>>   pairwise=TKIP
>>>      
>>>
>
>  
>
>>UOW network does not use PSK, it uses TKIP + PEAP + MSCHAPv2
>>
>>You need to enable these options in your compilation & your config file.
>>    
>>
>
>??
>
>Based on the about .config and wpa_supplicant.conf, they were enabled..
>
>  
>
Yes, sorry I missed that.




From jkmaline  Thu Sep  9 19:35:52 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 9 Sep 2004 19:35:52 -0700
Subject: WPA-PSK accepted for key management, but no PSK configured.
In-Reply-To: <41406C7D.9000707@anticd.org>
References: <414014B6.5040407@anticd.org> <20040909135215.GA7164@jm.kir.nu>
	<41406C7D.9000707@anticd.org>
Message-ID: <20040910023552.GA7362@jm.kir.nu>

On Fri, Sep 10, 2004 at 12:45:17AM +1000, Simon Males wrote:

> I am running a hostap card so I need hostapd to manage the keys in 
> station mode (not quite sure what that means).

???

Where did you get this information from? hostapd implements WPA
authenticator, i.e., the component that is used in an access point.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ndhegde  Thu Sep  9 22:29:49 2004
From: ndhegde (nikhil hegde)
Date: Thu, 9 Sep 2004 22:29:49 -0700 (PDT)
Subject: tx power related problem.
Message-ID: <20040910052949.50822.qmail@web20828.mail.yahoo.com>

Hi All,
I am trying to reduce the transmission power of my
802.11 PCI card. It is US robotics prism2 based
chipset. This I want to do to set up a multi hop
connection i.e try to isolate a machine from a third
machine which can be reached through an intermediate
machine.I am using hostAP  0.2.4 driver.
I tried:
 iwconfig wlan0 txpower <somevalue>
    Error for wireless request "Set Tx Power" (8B26)



		
_______________________________
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.
http://shopping.yahoo.com/backtoschool



From ndhegde  Thu Sep  9 22:29:52 2004
From: ndhegde (nikhil hegde)
Date: Thu, 9 Sep 2004 22:29:52 -0700 (PDT)
Subject: tx power related problem.
Message-ID: <20040910052952.57455.qmail@web20822.mail.yahoo.com>

Hi All,
I am trying to reduce the transmission power of my
802.11 PCI card. It is US robotics prism2 based
chipset. This I want to do to set up a multi hop
connection i.e try to isolate a machine from a third
machine which can be reached through an intermediate
machine.I am using hostAP  0.2.4 driver.
I tried:
 iwconfig wlan0 txpower <somevalue>
    Error for wireless request "Set Tx Power" (8B26)



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



From ndhegde  Thu Sep  9 22:31:16 2004
From: ndhegde (nikhil hegde)
Date: Thu, 9 Sep 2004 22:31:16 -0700 (PDT)
Subject: tx power related problem.
Message-ID: <20040910053116.45686.qmail@web20826.mail.yahoo.com>

Hi All,
I am trying to reduce the transmission power of my
802.11 PCI card. It is US robotics prism2 based
chipset. This I want to do to set up a multi hop
connection i.e try to isolate a machine from a third
machine which can be reached through an intermediate
machine.I am using hostAP  0.2.4 driver.
I tried:
 iwconfig wlan0 txpower <somevalue>
    Error for wireless request "Set Tx Power" (8B26)
    Set failed on device wlan0 operation not
supported.
I also tried
    iwpriv wlan0 alc 5 0 



		
_______________________________
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.
http://shopping.yahoo.com/backtoschool



From gbur  Thu Sep  9 22:47:55 2004
From: gbur (Gunter Burchardt)
Date: Fri, 10 Sep 2004 07:47:55 +0200
Subject: tx power related problem.
In-Reply-To: <20040910052949.50822.qmail@web20828.mail.yahoo.com>
References: <20040910052949.50822.qmail@web20828.mail.yahoo.com>
Message-ID: <20040910054755.GP28682@informatik.uni-rostock.de>

> Hi All,
> I am trying to reduce the transmission power of my
> 802.11 PCI card. It is US robotics prism2 based
> chipset. This I want to do to set up a multi hop
> connection i.e try to isolate a machine from a third
> machine which can be reached through an intermediate
> machine.I am using hostAP  0.2.4 driver.
> I tried:
>  iwconfig wlan0 txpower <somevalue>
>     Error for wireless request "Set Tx Power" (8B26)

Setting txpower ist experimental in hostap driver. Look at
hostapd/driver/modules/hostap_ioctl.c!

/* Note! This TX power controlling is experimental and should not be used in
 * production use. It just sets raw power register and does not use any kind of
 * feedback information from the measured TX power (CR58). This is now
 * commented out to make sure that it is not used by accident. TX power
 * configuration will be enabled again after proper algorithm using feedback
 * has been implemented. */

To enable it you have to define:

#define RAW_TXPOWER_SETTING

regards
gunter



From ndhegde  Thu Sep  9 22:51:10 2004
From: ndhegde (nikhil hegde)
Date: Thu, 9 Sep 2004 22:51:10 -0700 (PDT)
Subject: tx power related problem.
Message-ID: <20040910055110.53737.qmail@web20828.mail.yahoo.com>

Hi All,
I am trying to reduce the transmission power of my
802.11 PCI card. It is US robotics prism2 based
chipset. This I want to do to set up a multi hop
connection i.e try to isolate a machine from a third
machine which can be reached through an intermediate
machine.I am using hostAP  0.2.4 driver.
I tried:
 iwconfig wlan0 txpower <somevalue>
    Error for wireless request "Set Tx Power" (8B26)
    Set failed on device wlan0 operation not
supported.
I also tried to disable auto control of power through
    iwpriv wlan0 alc 5 0 
    iwpriv wlan0 prism2_param 5 0
  but not sure which actually is needed for reducing
the power.
Then I tried setting the power to -22.5dbm by
    iwpriv wlan0 writemif 62 120

Is this right?I am not able o observe visible
changes.Also could anyone please tell me the minimum
power value.

thanks
Nikhil


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



From jkmaline  Thu Sep  9 22:57:42 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 9 Sep 2004 22:57:42 -0700
Subject: WPA PSK - AUTH, ASSOC, 4-Way Handshake
In-Reply-To: <20040909072908.GN31207@ruslug.rutgers.edu>
References: <20040909055657.GM31207@ruslug.rutgers.edu>
	<20040909064511.GE7368@jm.kir.nu>
	<20040909072908.GN31207@ruslug.rutgers.edu>
Message-ID: <20040910055742.GD7362@jm.kir.nu>

On Thu, Sep 09, 2004 at 03:29:08AM -0400, Luis R. Rodriguez wrote:
> On Wed, Sep 08, 2004 at 11:45:11PM -0700, Jouni Malinen wrote:

> > 1) IEEE 802.11 authentication (wpa_supplicant doesn't really care about
> >    this)
> > 2) IEEE 802.11 association (New Access Point)
> 
> I'm not seeing any of these sent caught by iwevent. I actually also do
> not see these on your iwevent log too, but I checked and noticed hostap
> src does not send a custom wireless event in the AUTH/ASSOC 802.11
> event.

That New Access Point event is there and like I said, wpa_supplicant
does not care about IEEE 802.11 auth, so no much point in adding a new
wireless event for that.

> It seems evident to me AUTH/ASSOC in MLME extended mode are not being
> sent out. I am not sure why and am trying to figure it out.
> Suggestions/comments are welcomed.

Hmm.. I believe that I was able to get the card to authenticate in MLME
extended mode. This was in January. I think I sent the WPA scanning
patch to prism54-devel at that point and then sent the other, more
experimental parts for MLME handling to you in June. Some kind of
combinations of these changes was able to authenticate with a WPA AP,
but I did not get the card to associate with the AP with WPA IE. It
looked like the firmware implementation and documentation did not
exactly match on this.. Anyway, I haven't spent much time on this after
that initial effort.

-- 
Jouni Malinen                                            PGP id EFC895FA



From naik  Sat Sep 11 20:37:23 2004
From: naik (Vinayak Naik)
Date: Sat, 11 Sep 2004 23:37:23 -0400 (EDT)
Subject: tx power related problem.
In-Reply-To: <20040910055110.53737.qmail@web20828.mail.yahoo.com>
Message-ID: <Pine.GSO.4.40.0409112336310.8548-100000@lambda.cis.ohio-state.edu>


Please have a look at the webpage
http://www.cse.ohio-state.edu/~naik/programming/transmission_power_802.11.html

- Vinayak


On Thu, 9 Sep 2004, nikhil hegde wrote:

> Hi All,
> I am trying to reduce the transmission power of my
> 802.11 PCI card. It is US robotics prism2 based
> chipset. This I want to do to set up a multi hop
> connection i.e try to isolate a machine from a third
> machine which can be reached through an intermediate
> machine.I am using hostAP  0.2.4 driver.
> I tried:
>  iwconfig wlan0 txpower <somevalue>
>     Error for wireless request "Set Tx Power" (8B26)
>     Set failed on device wlan0 operation not
> supported.
> I also tried to disable auto control of power through
>     iwpriv wlan0 alc 5 0
>     iwpriv wlan0 prism2_param 5 0
>   but not sure which actually is needed for reducing
> the power.
> Then I tried setting the power to -22.5dbm by
>     iwpriv wlan0 writemif 62 120
>
> Is this right?I am not able o observe visible
> changes.Also could anyone please tell me the minimum
> power value.
>
> thanks
> Nikhil
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>




From jerith  Sun Sep 12 10:19:58 2004
From: jerith (Matt McHenry)
Date: Sun, 12 Sep 2004 13:19:58 -0400
Subject: wap_supplicant only gets to "Sending EAPOL-Key 2/4"
Message-ID: <1095009597.4736.18.camel@localhost>

	I'm trying to configure my linux box as a client in my new wireless
network w/ WPA.  The network is known to work with a WinXP box using the
exact same wireless card.  Any help would be much appreciated!

	The AP is a NetGear WGR614 802.11g wireless router. 
(http://www.ee.surrey.ac.uk/Personal/G.Wilford/WiFi.html indicates that
this should work w/ wpa_supplicant.)

	The card I'm using is a Linksys WMP54G.  lspci says:

02:09.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev
03)
        Subsystem: Linksys: Unknown device 0013
        Flags: bus master, fast devsel, latency 64, IRQ 10
        Memory at feafc000 (32-bit, non-prefetchable) [size=8K]

	I'm using ndiswrapper 0.10 to load the driver provided on the
installation CD (bcmw15.[inf|sys]).  dmesg reports:

ndiswrapper: no version for "struct_module" found: kernel tainted.
ndiswrapper version 0.10 loaded (preempt=no,smp=yes)
ndiswrapper: using irq 10
wlan0: ndiswrapper ethernet device 00:0c:41:61:ea:0a using driver
bcmwl5.sys
ndiswrapper device wlan0 supports WPA with AES/CCMP and TKIP ciphers
ndiswrapper: driver bcmwl5.sys (Linksys,07/17/2003, 3.30.15.0) added

	I am able to get the card to work if I set up the AP to use no
authentication whatsoever.  So I believe that the driver is working
correctly.  However, as the subject says, I can only get to step 2 of 4
with wpa_supplicant.  iwconfig reports:

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.462GHz  Access Point:
00:00:00:00:00:00  
          Bit Rate:54Mb/s   Tx-Power:14 dBm   
          RTS thr:2347 B   Fragment thr:2346 B   
          Encryption key:off
          Power Management:off
          Link Quality:100/100  Signal level:-54 dBm  Noise level:-256
dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:17  Invalid misc:3387   Missed beacon:0

my wpa_supplicant.conf file is based off of the version linked at
http://hostap.epitest.fi/wpa_supplicant/.  My network block looks like
this:

# Only WPA-PSK is used. Any valid cipher combination is accepted.
network={
	ssid="MattToby"
	proto=WPA
	key_mgmt=WPA-PSK
	pairwise=CCMP TKIP
	group=CCMP TKIP WEP104 WEP40
	psk="TobyMatt"
	priority=2
}

Here is the output from wpa_supplicant:

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


Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
Line: 242 - start of a new network block
SSID - hexdump_ascii(len=8):
     4d 61 74 74 54 6f 62 79                           MattToby        
proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK (ASCII passphrase) - hexdump_ascii(len=8):
     54 6f 62 79 4d 61 74 74                           TobyMatt        
priority=2
PSK (from passphrase) - hexdump(len=32): c3 f9 06 19 be 7f a2 39 83 3a
0f aa 28 
9c ce d9 c6 99 24 89 47 2a 51 37 4b 6e 49 20 cd d6 55 38
Priority group 2
   id=0 ssid='MattToby'
Setting scan request: 0 sec 100000 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 308 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:09:5b:dc:c4:0e ssid='MattToby' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:09:5b:dc:c4:0e (SSID='MattToby' freq=2462
MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 
50 f2 02 01 00 00 50 f2 02
Setting authentication timeout: 5 sec 0 usec
Wireless event: cmd=0x8c02 len=159
Custom wireless event:
'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
c32048c129860dd050010180100dd160050f20101000050f2
RespIEs=010482848b9632088c1298
24b048606c)'
Association info event
req_ies - hexdump(len=44): 00 08 4d 61 74 74 54 6f 62 79 01 08 82 84 8b
96 24 b0
 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50 f2 01 01 00 00
50 f2
assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 69 f3
01 00 00 
00 00 00 00 00 00 00 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:dc:c4:0e
Association event - clear replay counter
Associated to a new BSS: BSSID=00:09:5b:dc:c4:0e
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:09:5b:dc:c4:0e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 06 4
9 53 d4 e9 f5 ff fc f4 b8 63 ad c5 21 4a cb 80 6a d2 e4 52 0a 10 d8 43
64 97 17 
53 08 56 20 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00
00 00 0
0 00 06 49 53 d4 e9 f5 ff fc f4 b8 63 ad c5 21 4a cb 80 6a d2 e4 52 0a
10 d8 43 
64 97 17 53 08 56 20 e6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:dc:c4:0e (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 7b ff 6a 1e e0 e1 87 cb 45 64 c8
10 db 07
 dd 9a 24 63 cb de ed c8 11 e0 fe 6f 28 be f1 2a 3f 60
WPA: PMK - hexdump(len=32): c3 f9 06 19 be 7f a2 39 83 3a 0f aa 28 9c ce
d9 c6 9
9 24 89 47 2a 51 37 4b 6e 49 20 cd d6 55 38
WPA: PTK - hexdump(len=64): 0f 14 2d 5d 65 b2 70 9f c8 13 31 a0 a3 96 71
da 14 d
3 a5 44 c9 1c 4c df 2a 04 10 19 5c 15 6f f1 b3 2c 77 9f 03 cb f6 7e f6
a9 dc d8 
84 7c ab 59 21 2b b0 42 32 c5 d8 69 0a a3 4d f6 2e 60 22 9e
WPA: EAPOL-Key MIC - hexdump(len=16): f2 2c d3 75 4c ed 34 f3 f0 60 fb
33 77 72 
c9 d7
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b dc c4 0e 00 0c 41 61
ea 0a 88
 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 06 7b ff 6a 1e e0 e1
87 cb 4
5 64 c8 10 db 07 dd 9a 24 63 cb de ed c8 11 e0 fe 6f 28 be f1 2a 3f 60
00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 f2 2c d3 75 4c ed 34 f3 f0 60 fb 33 77 72 c9 d7 00 18 dd 16 00 50
f2 01 0
1 00 00 50 f2 69 f3 01 00 00 00 00 00 00 00 00 00 00
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b1a len=13
Authentication with 00:09:5b:dc:c4:0e timed out.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 308 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:09:5b:dc:c4:0e ssid='MattToby' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:09:5b:dc:c4:0e (SSID='MattToby' freq=2462
MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 
50 f2 02 01 00 00 50 f2 02
Setting authentication timeout: 5 sec 0 usec
Wireless event: cmd=0x8c02 len=159
Custom wireless event:
'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
c32048c129860dd050010180100dd160050f20101000050f2
RespIEs=010482848b9632088c1298
24b048606c)'
Association info event
req_ies - hexdump(len=44): 00 08 4d 61 74 74 54 6f 62 79 01 08 82 84 8b
96 24 b0
 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50 f2 01 01 00 00
50 f2
assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 49 f3
01 00 0c 
3d 06 08 ff ff ff ff 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:dc:c4:0e
Association event - clear replay counter
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:09:5b:dc:c4:0e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 07 c
2 b6 ba 99 1b 29 d2 48 bf 75 90 9c c7 17 23 13 29 0b 03 9e d8 4a 36 af
62 b2 88 
1c ea 5b be f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00
00 00 0
0 00 07 c2 b6 ba 99 1b 29 d2 48 bf 75 90 9c c7 17 23 13 29 0b 03 9e d8
4a 36 af 
62 b2 88 1c ea 5b be f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:dc:c4:0e (ver=1)
WPA: Renewed SNonce - hexdump(len=32): ac 85 4d 7c b7 ca 64 48 41 ed 11
04 44 09
 47 f4 f1 eb 1f 7a 29 95 9a 74 5f cd a9 c4 34 c4 9d 9b
WPA: PMK - hexdump(len=32): c3 f9 06 19 be 7f a2 39 83 3a 0f aa 28 9c ce
d9 c6 9
9 24 89 47 2a 51 37 4b 6e 49 20 cd d6 55 38
WPA: PTK - hexdump(len=64): c8 e2 f9 62 5d a0 08 f1 5f 69 e7 12 48 05 81
20 bd 1
3 f3 d1 b7 ca b7 02 ce 5e e0 d8 a5 6e e7 80 8c e1 2e 3d ef 2e c6 aa 07
3f 53 0d 
4c 41 09 fc 77 96 3a 93 d4 46 d2 49 3d c6 1f 3f f8 55 eb 6d
WPA: EAPOL-Key MIC - hexdump(len=16): 60 59 bd 58 9c be 9f 66 28 61 cf
dc fa 31 
32 01
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b dc c4 0e 00 0c 41 61
ea 0a 88
 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 07 ac 85 4d 7c b7 ca
64 48 4
1 ed 11 04 44 09 47 f4 f1 eb 1f 7a 29 95 9a 74 5f cd a9 c4 34 c4 9d 9b
00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 60 59 bd 58 9c be 9f 66 28 61 cf dc fa 31 32 01 00 18 dd 16 00 50
f2 01 0
1 00 00 50 f2 49 f3 01 00 0c 3d 06 08 ff ff ff ff 00
Wireless event: cmd=0x8c02 len=159
Custom wireless event:
'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
c32048c129860dd050010180100dd160050f20101000050f2
RespIEs=010482848b9632088c1298
24b048606c)'
Association info event
req_ies - hexdump(len=44): 00 08 4d 61 74 74 54 6f 62 79 01 08 82 84 8b
96 24 b0
 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50 f2 01 01 00 00
50 f2
assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 49 f3
01 00 ff 
ff ff ff 00 00 00 00 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:dc:c4:0e
Association event - clear replay counter
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:09:5b:dc:c4:0e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 08 c
4 83 f1 e0 37 cc e6 99 d0 df 33 76 5e 66 84 af 2a 56 24 2c 3c 3a 62 d0
59 03 3c 
b0 3e 51 d4 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00
00 00 0
0 00 08 c4 83 f1 e0 37 cc e6 99 d0 df 33 76 5e 66 84 af 2a 56 24 2c 3c
3a 62 d0 
59 03 3c b0 3e 51 d4 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:dc:c4:0e (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 00 a1 fb 70 3c b1 30 a2 0a ce 48
3d 52 38
 02 fc ba 9c c4 ea 2c 26 2c 31 a4 3f 7d 16 2c 92 32 c8
WPA: PMK - hexdump(len=32): c3 f9 06 19 be 7f a2 39 83 3a 0f aa 28 9c ce
d9 c6 9
9 24 89 47 2a 51 37 4b 6e 49 20 cd d6 55 38
WPA: PTK - hexdump(len=64): 02 49 89 d4 f6 eb b0 3a a6 7a ec 3c 57 a6 64
fa 9f 2
9 78 c4 ec 56 f8 85 fd a0 e5 80 06 55 d4 92 1d 82 aa e7 20 3d 55 5a 61
1c a7 fd 
70 ca 69 0b f1 30 6a e9 9f 98 ce c8 00 70 a4 27 1a 16 08 ad
WPA: EAPOL-Key MIC - hexdump(len=16): 15 38 00 92 f9 16 5b 40 b4 9c 21
f8 e1 f5 
1d 93
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b dc c4 0e 00 0c 41 61
ea 0a 88
 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 08 00 a1 fb 70 3c b1
30 a2 0
a ce 48 3d 52 38 02 fc ba 9c c4 ea 2c 26 2c 31 a4 3f 7d 16 2c 92 32 c8
00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 15 38 00 92 f9 16 5b 40 b4 9c 21 f8 e1 f5 1d 93 00 18 dd 16 00 50
f2 01 0
1 00 00 50 f2 49 f3 01 00 ff ff ff ff 00 00 00 00 00
Wireless event: cmd=0x8c02 len=159
Custom wireless event:
'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
c32048c129860dd050010180100dd160050f20101000050f2
RespIEs=010482848b9632088c1298
24b048606c)'
Association info event
req_ies - hexdump(len=44): 00 08 4d 61 74 74 54 6f 62 79 01 08 82 84 8b
96 24 b0
 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50 f2 01 01 00 00
50 f2
assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 49 f3
01 00 ff 
ff ff ff 00 00 00 00 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:dc:c4:0e
Association event - clear replay counter
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:09:5b:dc:c4:0e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 09 6
b 5b 15 7e 1b ca dd af 2d a3 1a 2b 04 03 e5 fd a1 29 84 78 f1 a5 73 be
41 82 7a 
c3 ab 88 ea 4f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00
00 00 0
0 00 09 6b 5b 15 7e 1b ca dd af 2d a3 1a 2b 04 03 e5 fd a1 29 84 78 f1
a5 73 be 
41 82 7a c3 ab 88 ea 4f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from 00:09:5b:dc:c4:0e (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 4d 45 77 86 e5 22 4e 06 b3 3f 5a
8c a1 91
 5b 78 e3 b4 14 77 e5 c0 a6 fb 2f 8b fe 04 21 cb 0f 1c
WPA: PMK - hexdump(len=32): c3 f9 06 19 be 7f a2 39 83 3a 0f aa 28 9c ce
d9 c6 9
9 24 89 47 2a 51 37 4b 6e 49 20 cd d6 55 38
WPA: PTK - hexdump(len=64): 65 b1 f3 7f fd 2d 27 03 cf 1e b0 3d f6 00 4a
e1 37 a
4 10 e5 21 00 fd be 55 ac b1 47 cb 86 80 d6 9f 49 e5 20 e2 45 cb 3b 2f
88 fc 7e 
07 e2 de 8f 24 e6 28 7d d6 a4 33 dc b3 a5 fb cf 7b 13 80 6d
WPA: EAPOL-Key MIC - hexdump(len=16): d7 b2 3d 57 e0 8b 2c 51 7b a2 dc
76 42 df 
12 c0
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 09 5b dc c4 0e 00 0c 41 61
ea 0a 88
 8e 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 09 4d 45 77 86 e5 22
4e 06 b
3 3f 5a 8c a1 91 5b 78 e3 b4 14 77 e5 c0 a6 fb 2f 8b fe 04 21 cb 0f 1c
00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 d7 b2 3d 57 e0 8b 2c 51 7b a2 dc 76 42 df 12 c0 00 18 dd 16 00 50
f2 01 0
1 00 00 50 f2 49 f3 01 00 ff ff ff ff 00 00 00 00 00
Wireless event: cmd=0x8c02 len=159
Custom wireless event:
'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
c32048c129860dd050010180100dd160050f20101000050f2
RespIEs=010482848b9632088c1298
24b048606c)'
Association info event
req_ies - hexdump(len=44): 00 08 4d 61 74 74 54 6f 62 79 01 08 82 84 8b
96 24 b0
 48 6c 32 04 8c 12 98 60 dd 05 00 10 18 01 00 dd 16 00 50 f2 01 01 00 00
50 f2
assoc_wpa_ie - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 49 f3
01 00 ff 
ff ff ff 00 00 00 00 00
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:09:5b:dc:c4:0e
Association event - clear replay counter
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:09:5b:dc:c4:0e
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00
00 0a 5
f 74 40 f8 09 f8 bd 79 e0 1b 08 16 07 6c d9 8a ce 90 de 45 a1 c7 5e 34
e1 7e c6 
8d 8a 85 a6 b3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 0
0 00








From jkmaline  Sun Sep 12 11:40:06 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 12 Sep 2004 11:40:06 -0700
Subject: wap_supplicant only gets to "Sending EAPOL-Key 2/4"
In-Reply-To: <1095009597.4736.18.camel@localhost>
References: <1095009597.4736.18.camel@localhost>
Message-ID: <20040912184005.GA7362@jm.kir.nu>

On Sun, Sep 12, 2004 at 01:19:58PM -0400, Matt McHenry wrote:

> 	I'm using ndiswrapper 0.10 to load the driver provided on the
> installation CD (bcmw15.[inf|sys]).

> WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
> 01 00 00 
> 50 f2 02 01 00 00 50 f2 02

> Wireless event: cmd=0x8c02 len=159
> Custom wireless event:
> 'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
> c32048c129860dd050010180100dd160050f20101000050f2
> RespIEs=010482848b9632088c1298
> 24b048606c)'

That ReqIEs string looks truncated. The last information element,
dd160050f20101000050f2, has only 9 bytes of data (0050..f2) even though
its length field indicates that there should be 22 bytes. In other
words, it looks like the driver (NDIS or ndiswrapper) has truncated the
data. Based on this, I would direct this to ndiswrapper mailing lists.
However, thanks for reporting this here, since this also showed a bug in
wpa_supplicant: it should reject that kind of ReqIEs report and complain
loadly about it.

This truncated WPA IE ended up in wpa_supplicant using corrupted WPA IE
in the msg 2/4. WPA APs are supposed to drop that kind of packets and
are likely to deauthenticate the STA.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Sun Sep 12 11:57:10 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 12 Sep 2004 11:57:10 -0700
Subject: wap_supplicant only gets to "Sending EAPOL-Key 2/4"
In-Reply-To: <20040912184005.GA7362@jm.kir.nu>
References: <1095009597.4736.18.camel@localhost>
	<20040912184005.GA7362@jm.kir.nu>
Message-ID: <20040912185710.GB7362@jm.kir.nu>

On Sun, Sep 12, 2004 at 11:40:06AM -0700, Jouni Malinen wrote:
> On Sun, Sep 12, 2004 at 01:19:58PM -0400, Matt McHenry wrote:
> > WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
> > 01 00 00 
> > 50 f2 02 01 00 00 50 f2 02
> 
> > Wireless event: cmd=0x8c02 len=159
> > Custom wireless event:
> > 'ASSOCINFO(ReqIEs=00084d617474546f6279010882848b9624b0486
> > c32048c129860dd050010180100dd160050f20101000050f2
> > RespIEs=010482848b9632088c1298
> > 24b048606c)'

> That ReqIEs string looks truncated. The last information element,
> dd160050f20101000050f2, has only 9 bytes of data (0050..f2) even though
> its length field indicates that there should be 22 bytes. In other
> words, it looks like the driver (NDIS or ndiswrapper) has truncated the
> data. Based on this, I would direct this to ndiswrapper mailing lists.
> However, thanks for reporting this here, since this also showed a bug in
> wpa_supplicant: it should reject that kind of ReqIEs report and complain
> loadly about it.

I fixed this now in wpa_supplicant. I would appreciate it if you test
the fix with your current setup that can generate this truncated IEs. In
theory, this fix could even be enough to workaround the problem since
wpa_supplicant tries to generate WPA IE itself when the driver does not
report one. If the IEs match, the AP should allow authentication to
continue.

You can either get the fix for wpa_supplicant by downloading the latest
CVS snapshot of the development version from http://hostap.epitest.fi/
or by applying the attached patch to the version you are using.

-- 
Jouni Malinen                                            PGP id EFC895FA
-------------- next part --------------
Index: wpa_supplicant.c
===================================================================
RCS file: /home/jm/cvsroot/hostap/wpa_supplicant/wpa_supplicant.c,v
retrieving revision 1.147
diff -u -p -r1.147 wpa_supplicant.c
--- wpa_supplicant.c	8 Sep 2004 03:37:28 -0000	1.147
+++ wpa_supplicant.c	12 Sep 2004 18:50:38 -0000
@@ -666,14 +666,19 @@ void wpa_supplicant_event(struct wpa_sup
 		p = data->assoc_info.req_ies;
 		l = data->assoc_info.req_ies_len;
 
-		/* Go through the IEs and make a copy of the WPA IE, if
+		/* Go through the IEs and make a copy of the WPA/RSN IE, if
 		 * present. */
-		while (l > (2 + 6)) {
+		while (l >= 2) {
 			len = p[1] + 2;
-			if (((p[0] == GENERIC_INFO_ELEM) && (p[1] > 6) &&
+			if (len > l) {
+				wpa_hexdump(MSG_DEBUG, "Truncated IE in "
+					    "assoc_info", p, l);
+				break;
+			}
+			if ((p[0] == GENERIC_INFO_ELEM && p[1] >= 6 &&
 			     (memcmp(&p[2], "\x00\x50\xF2\x01\x01\x00", 6) ==
 			      0)) ||
-			    p[0] == RSN_INFO_ELEM) {
+			    (p[0] == RSN_INFO_ELEM && p[1] >= 2)) {
 				wpa_s->assoc_wpa_ie = malloc(len);
 				if (wpa_s->assoc_wpa_ie == NULL)
 					break;


From jkmaline  Sun Sep 12 20:09:12 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 12 Sep 2004 20:09:12 -0700
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040831085838.GC28682@informatik.uni-rostock.de>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
Message-ID: <20040913030912.GA9322@jm.kir.nu>

On Tue, Aug 31, 2004 at 10:58:38AM +0200, Gunter Burchardt wrote:

> First patch to bring wired authentication with hostapd alive. This
> patch enables hostapd to send and recieve eapol frames via ethernet.
> Furthermore sta detection is implemented via dhcp for station which
> didn't send eapol-start (like winxp supplicant).

I applied this to hostapd now even though question about how to detect
new devices is still somewhat open. This is a good starting point and
allows people to start experimenting with the code. I verified that this
works in my test setup and added an example configuration, wired.conf,
that is quite minimal example of how to setup wired authenticator.

> In ieee802_11.c auth_get_sta() is implemented. I think this function
> should move to hostapd.c . There are no 802.11 thinks in this function.
> At the moment i declared this function to extern.

I moved this to sta_info.c as ap_sta_add().

-- 
Jouni Malinen                                            PGP id EFC895FA



From ramakrishna.b  Sun Sep 12 21:41:33 2004
From: ramakrishna.b (ramakrishna.b)
Date: Mon, 13 Sep 2004 10:11:33 +0530
Subject: information needed about Quality of Service
Message-ID: <414524FD.4080905@redpinesignals.com>

    i am working on Quality of Service i.e.802.11 e
    at the time of  testing ,we need station and access point which supports QoS
    we got access point from website of   cisco ,but not able to find a 
    station card which supports QoS
    if any one has the information of any station card,please let me know
    
    thanking you
    
    regards
    ramakrshna





From masustec  Mon Sep 13 02:46:36 2004
From: masustec (=?iso-8859-1?q?Mr=20Asustec?=)
Date: Mon, 13 Sep 2004 10:46:36 +0100 (BST)
Subject: tx_rate in adhoc
Message-ID: <20040913094636.27936.qmail@web25209.mail.ukl.yahoo.com>

In adhoc mode, the tx_rate value in transmitted frame
descriptor txdesc often has the value of 0 (prism2_tx,
prism2_tx_ev). Sometimes it gets the proper
transmission rate value but not always. What may be
the reason?

Regards,
Asustec



	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com



From nettie  Mon Sep 13 07:05:21 2004
From: nettie (nettie)
Date: Mon, 13 Sep 2004 16:05:21 +0200
Subject: Flash primary firmware
Message-ID: <4145A921.4010800@apple2.com>

Hi guys, I'm having problems flashing (volatile) the primary firmware of 
my Prism2.5 minipci adapter.

this is the hostap_diag output:

Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.0.7
STAID: id=0x001f v1.3.6 (station firmware)

srec summary for ak010104.hex
Included file name: AK010104.HEX
Component: 0x0015 1.1.4 (primary firmware)

srec summary for rf010803.hex
Component: 0x001f 1.8.3 (station firmware)


Verifying update compatibility and combining data:
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
PRI: old iface 1:4-4 new iface 4:4-5
Could not find data position for plugging PDR 0x0413 at 0x0000118a (len=2)
PDR 0x0413 is not in wlan card PDA and there is no default data. 
Ignoring plug .
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
OK.

Downloading to volatile memory (RAM).
OK.
Components after download:
   NICID: 0x8013 v1.0.0
   PRIID: 0x0015 v1.0.7
   STAID: 0x001f v1.8.3

as you can see only the secondary firmware has been lodead.

I would like to flash because I have some issues with orinoco gold 
adapters (they associate but there's no traffic), so I'm trying to 
figure out if an update could solve this problem.

I also would like to know if a primary/secondary firmware changelog 
exist and where should I find it considering I really would like to 
understand what are the enhancements and fixes before flashing the adapter.

Thanx in advance for your time guys, any feedback and suggestion will be 
appreciated.






From matt  Mon Sep 13 07:16:29 2004
From: matt (Matt Brown)
Date: Tue, 14 Sep 2004 02:16:29 +1200
Subject: Flash primary firmware
In-Reply-To: <4145A921.4010800@apple2.com>
References: <4145A921.4010800@apple2.com>
Message-ID: <1095084989.3874.36.camel@localhost>

On Tue, 2004-09-14 at 02:05, nettie wrote:

> srec summary for ak010104.hex
> Included file name: AK010104.HEX
> Component: 0x0015 1.1.4 (primary firmware)
<snip>
> Downloading to volatile memory (RAM).
> OK.
> Components after download:
>    NICID: 0x8013 v1.0.0
>    PRIID: 0x0015 v1.0.7
>    STAID: 0x001f v1.8.3

As indicated by the output the primary firmware you are loading is a RAM
based firmware, rather than a firmware to be written to the flash memory
on the card. 

You can also tell this by the filename (af indicates RAM based), for a
flash based firmware you want something starting with p (eg
pk010101.hex). 

Jun Sun's mini HOWTO at http://linux.junsun.net/intersil-prism/ seems to
be the definitive reference for this sort of thing. 

HTH.

Regards

-- 
Matt Brown
Email:	matt at mattb.net.nz
GSM: 	+64 21 611 544




From nettie  Mon Sep 13 07:24:49 2004
From: nettie (nettie)
Date: Mon, 13 Sep 2004 16:24:49 +0200
Subject: Flash primary firmware
Message-ID: <4145ADB1.90207@apple2.com>

Hi Matt,

thanx a lot for your feedback, I'm using the -r option to download the 
primary firmware on ram rather then on flash. When I try downlaoding it 
to flash I have IOCTL problems! When I download to flash I use a PK file 
as you suggested me. Of course I have enabled FLASH DOWNLOAD in 
hostap_confgi.h and recompiled.

Any idea? -- Thanx

 > srec summary for ak010104.hex
 > Included file name: AK010104.HEX
 > Component: 0x0015 1.1.4 (primary firmware)
<snip>
 > Downloading to volatile memory (RAM).
 > OK.
 > Components after download:
 >    NICID: 0x8013 v1.0.0
 >    PRIID: 0x0015 v1.0.7
 >    STAID: 0x001f v1.8.3

As indicated by the output the primary firmware you are loading is a RAM
based firmware, rather than a firmware to be written to the flash memory
on the card.

You can also tell this by the filename (af indicates RAM based), for a
flash based firmware you want something starting with p (eg
pk010101.hex).

Jun Sun's mini HOWTO at http://linux.junsun.net/intersil-prism/ seems to
be the definitive reference for this sort of thing.

HTH.

Regards

--
Matt Brown
Email:  matt at mattb.net.nz
GSM:    +64 21 611 544





From gbur  Mon Sep 13 11:26:09 2004
From: gbur (Gunter Burchardt)
Date: Mon, 13 Sep 2004 20:26:09 +0200
Subject: PATCH: wired eapol receive/send
In-Reply-To: <20040913030912.GA9322@jm.kir.nu>
References: <20040831085838.GC28682@informatik.uni-rostock.de>
	<20040913030912.GA9322@jm.kir.nu>
Message-ID: <20040913182609.GR28682@informatik.uni-rostock.de>

> I applied this to hostapd now even though question about how to detect
> new devices is still somewhat open. This is a good starting point and
> allows people to start experimenting with the code. I verified that this
> works in my test setup and added an example configuration, wired.conf,
> that is quite minimal example of how to setup wired authenticator.

Great :) . Detecting stations isn't a problem anymore! I found a good
and clean solution for all wired related problems (detecting,
authorize, accounting). The solution is a kernel module im writing at
the moment. It has nearly the same ioctls like hostap driver to handle
stations. Internal it has a hook to netfilter to drop unauthorized
packets (pass new stations to user daemon) and accept packets from/to
authozied station. I hope first version will be ready end of the week.

regards
gunter



From jkmaline  Mon Sep 13 18:38:33 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 13 Sep 2004 18:38:33 -0700
Subject: Flash primary firmware
In-Reply-To: <4145ADB1.90207@apple2.com>
References: <4145ADB1.90207@apple2.com>
Message-ID: <20040914013833.GA7355@jm.kir.nu>

On Mon, Sep 13, 2004 at 04:24:49PM +0200, nettie wrote:

> thanx a lot for your feedback, I'm using the -r option to download the 
> primary firmware on ram rather then on flash. When I try downlaoding it 
> to flash I have IOCTL problems! When I download to flash I use a PK file 
> as you suggested me. Of course I have enabled FLASH DOWNLOAD in 
> hostap_confgi.h and recompiled.

-r can be used to RAM download station firmware, but primary firmware
requires Genesis mode. You will need to load this in two steps: first
primary with -g and then secondary (station) with -r.

-- 
Jouni Malinen                                            PGP id EFC895FA



From grant  Mon Sep 13 20:43:56 2004
From: grant (Grant Limberg)
Date: Mon, 13 Sep 2004 23:43:56 -0400
Subject: IEEE 802.11: did not acknowledge authentication response
Message-ID: <414668FC.1040107@xactcommerce.com>

I'm trying to set up an open AP on my linux box using the hostap-0.1.3 
SuSE RPM package on SuSE 9.1 Pro with a D-Link DWL-520 (i dont remember 
the revision of the card, but it worked in my old linux box as an AP 
before I upgraded).

Whenever a Windows XP machine tries to connect to it, this is whats in 
the log:

wlan0: STA 00:02:2d:32:c0:f2 IEEE 802.11: did not acknowledge 
authentication response
Data frame from not associated STA 00:02:2d:32:c0:f2
wlan0: STA 00:02:2d:32:c0:f2 IEEE 802.11: did not acknowledge 
authentication response
Data frame from not associated STA 00:02:2d:32:c0:f2
Data frame from not associated STA 00:02:2d:32:c0:f2
wlan0: STA 00:02:2d:32:c0:f2 IEEE 802.11: did not acknowledge 
authentication response
Data frame from not associated STA 00:02:2d:32:c0:f2
wlan0: STA 00:02:2d:32:c0:f2 IEEE 802.11: did not acknowledge 
authentication response
wlan0: STA 00:02:2d:32:c0:f2 IEEE 802.11: did not acknowledge 
authentication response
Data frame from not associated STA 00:02:2d:32:c0:f2
Data frame from not associated STA 00:02:2d:32:c0:f2

Here's some of the latest output from dmesg:

wlan0: dropped received packet from non-associated STA 00:02:2d:32:c0:f2 
(type=0x02, subtype=0x00)
handle_ap_item - data frame
wlan0: STA 00:02:2d:32:c0:f2 TX rate lowered to 20
wlan0: 00:02:2d:32:c0:f2 auth_cb - frame was not ACKed
wlan0: 00:02:2d:32:c0:f2 auth_cb - frame was not ACKed
wlan0: STA 00:02:2d:32:c0:f2 TX rate lowered to 55
wlan0: 00:02:2d:32:c0:f2 assoc_cb - frame was not ACKed


and here's the output of hostap_diag wlan0:

Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.8.0 (station firmware)

If anyone can help get this working, it would be much appriciated.

Thanks in advance,

Grant



From nettie  Tue Sep 14 00:40:16 2004
From: nettie (nettie)
Date: Tue, 14 Sep 2004 09:40:16 +0200
Subject: Flash primary firmware
In-Reply-To: <20040914013833.GA7355@jm.kir.nu>
References: <4145ADB1.90207@apple2.com> <20040914013833.GA7355@jm.kir.nu>
Message-ID: <4146A060.7070805@apple2.com>

Thanx a lot Jouni, worked pefectly.

Jouni Malinen wrote:

> On Mon, Sep 13, 2004 at 04:24:49PM +0200, nettie wrote:
> 
> 
>>thanx a lot for your feedback, I'm using the -r option to download the 
>>primary firmware on ram rather then on flash. When I try downlaoding it 
>>to flash I have IOCTL problems! When I download to flash I use a PK file 
>>as you suggested me. Of course I have enabled FLASH DOWNLOAD in 
>>hostap_confgi.h and recompiled.
> 
> 
> -r can be used to RAM download station firmware, but primary firmware
> requires Genesis mode. You will need to load this in two steps: first
> primary with -g and then secondary (station) with -r.
> 




From lilnana  Tue Sep 14 01:48:57 2004
From: lilnana (Nana Kofi Asumadu)
Date: Tue, 14 Sep 2004 18:48:57 +1000
Subject: Madwifi, wpa_supplicant and WE-17
Message-ID: <1095151738.17934.16.camel@workstation.home.org>

Hi Jouni

I am trying to get Madwifi driver to work with WE-17 merged into
Andrew's mm kernel-2.6 patches.  The driver works fine with WEP but not
with WPA.
This is what I get when I run wpa_supplicant in debug mode

/usr/sbin/wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -dd
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
Line: 172 - start of a new network block
SSID - hexdump_ascii(len=16):
     4c 69 6c 6e 61 6e 61 5f 57 69 72 65 6c 65 73 73   Wireless
BSSID - hexdump(len=6): 00 09 5b ea 06 b8
proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK - hexdump(len=32): 7e 7b 85 77 26 36 fa 85 2c 48 4d 5d 04 66 a0 ef
0a 2d f8 43 8a 9b 7e 4d a1 ec ae d3 04 7a 6b 98
priority=2
Priority group 2
   id=0 ssid='Wireless'
Own MAC address: 00:09:5b:da:fc:87
wpa_driver_madwifi_set_wpa: enabled=1
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=12
Wireless event: cmd=0x8b19 len=12
Received 413 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 2
0: 00:09:5b:eb:07:f9 ssid='Wireless' wpa_ie_len=24 rsn_ie_len=0
   selected
Trying to associate with 00:09:5b:eb:07:f9 (SSID='Wireless' freq=2437
MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
ioctl[IEEE80211_IOCTL_SETOPTIE]: Argument list too long
Setting authentication timeout: 5 sec 0 usec

What puzzles me is the line:
ioctl[IEEE80211_IOCTL_SETOPTIE]: Argument list too long
which keeps repeating

This is my wpa_supplicant.conf file

network={
        ssid="Wireless"
	bssid=00:09:5b:eb:07:f9
	proto=WPA
	key_mgmt=WPA-PSK
	pairwise=CCMP TKIP
	group=CCMP TKIP WEP104 WEP40
        #psk="k920&^ld10nak29-%&92ks9k23@"
        psk=7e7b85772636fa852c484d5d0466a0ef0a2df8438a9b7e
}

Any help would be valuable. Thanks

Nana K. Asumadu
Email: lilnana at netspeed.com.au
Website: http://www.netspeed.com.au/lilnana/index.html

                               DISCLAIMER


________________________________________________________________________
This email and any attachment(s) are intended for the addressed
recipient(s) only.   If you have received this email by accident, I urge
you to notify the sender and delete this email and any attachment(s)
immediately.    Any unauthorised use, disclosure or reproduction of any
information in this email without the prior consent of the sender is
strictly prohibited and will be prosecuted to the fullest extent of the
law.    No representation is made that this email or any attachment(s)
are free of viruses. Virus scanning is recommended and it's the
responsibility of the recipient(s).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040914/915125dc/attachment.htm 


From jkmaline  Tue Sep 14 06:27:05 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Sep 2004 06:27:05 -0700
Subject: Madwifi, wpa_supplicant and WE-17
In-Reply-To: <1095151738.17934.16.camel@workstation.home.org>
References: <1095151738.17934.16.camel@workstation.home.org>
Message-ID: <20040914132705.GB7158@jm.kir.nu>

On Tue, Sep 14, 2004 at 06:48:57PM +1000, Nana Kofi Asumadu wrote:

> I am trying to get Madwifi driver to work with WE-17 merged into
> Andrew's mm kernel-2.6 patches.  The driver works fine with WEP but not
> with WPA.
> This is what I get when I run wpa_supplicant in debug mode

> ioctl[IEEE80211_IOCTL_SETOPTIE]: Argument list too long

Did you rebuild all components (kernel, madwifi modules, wpa_supplicant)
after having merged WE-17? Did wpa_supplicant build use correct header
files from madwifi (i.e., the ones from the version you are now using)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From Adam.Lewis  Tue Sep 14 07:15:42 2004
From: Adam.Lewis (Lewis Adam-CAL022)
Date: Tue, 14 Sep 2004 09:15:42 -0500
Subject: iwpriv and string argument
Message-ID: <FD52892BD296D71183B400065BFCB6900F0CD5CE@il02exm12>

Hello,

This is more of a wireless extensions question, but I could not find a mailing list dedicated to the topic.  If there is one, please point me in that direction.  

Is there a way to create a private extension (e.g. to be invoked by iwpriv) that I can pass a string argument?  Looking in wirless.h, I see types for byte, float, int, char, etc., but no char*.

Anyway to pass a string to iwpriv?


TIA,
Adam



From nettie  Tue Sep 14 08:03:37 2004
From: nettie (nettie)
Date: Tue, 14 Sep 2004 17:03:37 +0200
Subject: Most stable firmware? -- high load? 
Message-ID: <41470849.1060002@apple2.com>

Hi again guys,

thanx to your and Jouni feedbacks I was able to download new firmwares 
on my Prism2.5 adapter, I'm testing the various versions and I just 
figured out that the latest firmware I was able to find v1.8.3 doesnt 
performs as good as others like the 1.4.9 which comes by default on my 
adapter. I'm not using professional software or hardware to evaluate 
them,  but as far as I can see the signal quality/stability using the 
latest firmware seems worse.

I'm trying to figure out which is the best primary/secondary firmware 
duo for your guys.

Reading the mailing list archive I noticed some people has very stable 
links running primary firmware 1.1.1 and secodanry firmware 1.7.4.

I'm also interested in real life experience using hostap with a large 
number of STA's, did you guys experienced any problems?

Thanx again.

nettie




From togg  Tue Sep 14 08:04:30 2004
From: togg (Togg)
Date: Tue, 14 Sep 2004 17:04:30 +0200
Subject: WPA big-endian problematic
Message-ID: <E1C7Er9-0001rO-00@mrelayng.kundenserver.de>

Hi Jouni,

you may have overlooked an email by Gunter Burchardt, reporting an error
with wpa on big-endian machine.
I too have this problem and it looks like problems in key calculation (e.g.
mic). I don't have an ap right here but I can post logs again if you need. 
EAP-TLS works fine, but I need WPA in my environment.


Please let us know if youre looking into the problem.

Regards,
Togg




From stexas  Tue Sep 14 11:27:15 2004
From: stexas (Greg Hochstrasser)
Date: Tue, 14 Sep 2004 13:27:15 -0500
Subject: disassociate frames
Message-ID: <5724165.1095186435799.JavaMail.stexas@mac.com>

All:

I am using the latest version of HostAP.  I am currently
using it to evaluate a WIDS, (sic).

Can anyone tell me how to set hostap to ignore 
"disassociate frames" being generated by the WIDS to kick
me off the network?  This is being done in a greyhat method;
but is legit and above the table.  

Trying to learn how to overcome the WIDS and the frames it
is generating to protect the trusted section of the WLAN.

thanks
gmh



From proski  Tue Sep 14 15:28:52 2004
From: proski (Pavel Roskin)
Date: Tue, 14 Sep 2004 18:28:52 -0400 (EDT)
Subject: iwpriv and string argument
In-Reply-To: <FD52892BD296D71183B400065BFCB6900F0CD5CE@il02exm12>
References: <FD52892BD296D71183B400065BFCB6900F0CD5CE@il02exm12>
Message-ID: <Pine.LNX.4.61.0409141823370.15158@marabou.research.att.com>

On Tue, 14 Sep 2004, Lewis Adam-CAL022 wrote:

> This is more of a wireless extensions question, but I could not find a 
> mailing list dedicated to the topic.  If there is one, please point me 
> in that direction.

netdev at oss.sgi.com

> Is there a way to create a private extension (e.g. to be invoked by 
> iwpriv) that I can pass a string argument?  Looking in wirless.h, I see 
> types for byte, float, int, char, etc., but no char*.
>
> Anyway to pass a string to iwpriv?

I believe IW_PRIV_TYPE_CHAR is what you need.  Just set the argument 
number to the maximal length of the string.

-- 
Regards,
Pavel Roskin



From lilnana  Tue Sep 14 16:13:17 2004
From: lilnana (Nana Kofi Asumadu)
Date: Wed, 15 Sep 2004 09:13:17 +1000
Subject: Madwifi, wpa_supplicant and WE-17
In-Reply-To: <20040914132705.GB7158@jm.kir.nu>
References: <1095151738.17934.16.camel@workstation.home.org>
	<20040914132705.GB7158@jm.kir.nu>
Message-ID: <1095203598.11909.6.camel@workstation.home.org>

> Did you rebuild all components (kernel, madwifi modules, wpa_supplicant)
> after having merged WE-17? Did wpa_supplicant build use correct header
> files from madwifi (i.e., the ones from the version you are now using)?
> 

Yes, I rebuild all the components including the kernel, madwifi modules
and wpa_supplicant after updating WE-17.  I rebuilt 
wpa_supplicant using the current cvs of madwifi drivers.  WPA works fine
with WE-16.  it's just WE-17 that I am getting that message:

ioctl[IEEE80211_IOCTL_SETOPTIE]: Argument list too long


Nana K. Asumadu
Email: lilnana at netspeed.com.au
Website: http://www.netspeed.com.au/lilnana/index.html
Mobile : + 61 405 590 466

                               DISCLAIMER


________________________________________________________________________
This email and any attachment(s) are intended for the addressed
recipient(s) only.   If you have received this email by accident, I urge
you to notify the sender and delete this email and any attachment(s)
immediately.    Any unauthorised use, disclosure or reproduction of any
information in this email without the prior consent of the sender is
strictly prohibited and will be prosecuted to the fullest extent of the
law.    No representation is made that this email or any attachment(s)
are free of viruses. Virus scanning is recommended and it's the
responsibility of the recipient(s).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040915/9cceaeaa/attachment.htm 


From ramalhais  Tue Sep 14 17:38:18 2004
From: ramalhais (Pedro Ramalhais)
Date: Wed, 15 Sep 2004 01:38:18 +0100
Subject: Madwifi, wpa_supplicant and WE-17
In-Reply-To: <1095203598.11909.6.camel@workstation.home.org>
References: <1095151738.17934.16.camel@workstation.home.org>
	<20040914132705.GB7158@jm.kir.nu>
	<1095203598.11909.6.camel@workstation.home.org>
Message-ID: <1095208698.26282.7.camel@rootix>

On Wed, 2004-09-15 at 00:13, Nana Kofi Asumadu wrote:
> > Did you rebuild all components (kernel, madwifi modules, wpa_supplicant)
> > after having merged WE-17? Did wpa_supplicant build use correct header
> > files from madwifi (i.e., the ones from the version you are now using)?
> > 
> Yes, I rebuild all the components including the kernel, madwifi
> modules and wpa_supplicant after updating WE-17.  I rebuilt 
> wpa_supplicant using the current cvs of madwifi drivers.  WPA works
> fine with WE-16.  it's just WE-17 that I am getting that message:
> 
> ioctl[IEEE80211_IOCTL_SETOPTIE]: Argument list too long
> 
> 
> Nana K. Asumadu

/* Check what user space is giving us */
                if(IW_IS_SET(cmd)) {
                        /* Check NULL pointer */
                        if((iwr->u.data.pointer == NULL) &&
                           (iwr->u.data.length != 0))
                                return -EFAULT;

                        /* Does it fits within bounds ? */
                        if(iwr->u.data.length > (descr->set_args &
                                                 IW_PRIV_SIZE_MASK))
                                return -E2BIG;
                }

This might be it, if the -E2BIG did not come from the driver, it came
from this code in linux/net/core/wireless.c, which means that the length
you're setting in the wireless request is bigger than the size set  for
that IOCTL in the driver's struct iw_priv_args.
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From jkmaline  Tue Sep 14 20:43:09 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Sep 2004 20:43:09 -0700
Subject: WPA big-endian problematic
In-Reply-To: <E1C7Er9-0001rO-00@mrelayng.kundenserver.de>
References: <E1C7Er9-0001rO-00@mrelayng.kundenserver.de>
Message-ID: <20040915034309.GC7360@jm.kir.nu>

On Tue, Sep 14, 2004 at 05:04:30PM +0200, Togg wrote:

> you may have overlooked an email by Gunter Burchardt, reporting an error
> with wpa on big-endian machine.
> I too have this problem and it looks like problems in key calculation (e.g.
> mic). I don't have an ap right here but I can post logs again if you need. 
> EAP-TLS works fine, but I need WPA in my environment.

Thanks for the reports. I did notice the earlier mail, but haven't so
far had chance of trying to reproduce this problem myself. I do remember
testing WPA successfully on a big-endian system, but I do not remember
whether it was hostapd, wpa_supplicant, or both.

What kind of big-endian system are you using? Gunter reported an issue
on IXP425. This may be something else than endianness though, since ARM
has couple of other differences, too (e.g., in requirements for aligned
read/write and char type).. I did my tests on a PowerPC (8260-based
board) and I'm going to test both hostapd and wpa_supplicant again on
that board.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Sep 14 20:49:52 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 14 Sep 2004 20:49:52 -0700
Subject: disassociate frames
In-Reply-To: <5724165.1095186435799.JavaMail.stexas@mac.com>
References: <5724165.1095186435799.JavaMail.stexas@mac.com>
Message-ID: <20040915034952.GD7360@jm.kir.nu>

On Tue, Sep 14, 2004 at 01:27:15PM -0500, Greg Hochstrasser wrote:

> Can anyone tell me how to set hostap to ignore 
> "disassociate frames" being generated by the WIDS to kick
> me off the network?

Are you using Host AP driver as the access point or as the client? In
case of Host AP as the AP, you will just need to modify handle_deauth()
and handle_disassoc() functions to ignore packets. In case of client
mode, you are likely out of luck with Prism2/2.5/3 cards and their
current firmware.. In other words, it is the firmware that takes care of
the client side operations (auth/assoc/deauth/disassoc). You could use
another card with these functions implemented in the driver, e.g.,
Atheros-based cards for this.

> Trying to learn how to overcome the WIDS and the frames it
> is generating to protect the trusted section of the WLAN.

That sounds like useless "protection" to me if WIDS is sending those
frames over air to client or AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From stexas  Tue Sep 14 21:12:57 2004
From: stexas (Greg M. Hochstrasser)
Date: Tue, 14 Sep 2004 23:12:57 -0500
Subject: disassociate frames
In-Reply-To: <20040915034952.GD7360@jm.kir.nu>
References: <5724165.1095186435799.JavaMail.stexas@mac.com>
	<20040915034952.GD7360@jm.kir.nu>
Message-ID: <863650E6-06CD-11D9-B6DF-000A95CA3FBC@mac.com>

Jouni:

Thanks for the quick response.  Your answer in reference to firmware 
controlling
a client in HostAP makes sense.   I have been using prism2/2.5 cards 
for a while now.
Maybe it's time I switched over to the Atheros (madwifi) cards.  I did 
a quick
proof of concept with a Proxim a/b/g card and madwifi to work with 
Kismet; but didn't think about
making it the stable card for HostAP, because I have not seen  any 
Atheros cards with external
antenna connectors (R-MMCX).

Appreciate the response and help here.

gmh

On Sep 14, 2004, at 10:49 PM, Jouni Malinen wrote:

On Tue, Sep 14, 2004 at 01:27:15PM -0500, Greg Hochstrasser wrote:

> Can anyone tell me how to set hostap to ignore
> "disassociate frames" being generated by the WIDS to kick
> me off the network?

Are you using Host AP driver as the access point or as the client? In
case of Host AP as the AP, you will just need to modify handle_deauth()
and handle_disassoc() functions to ignore packets. In case of client
mode, you are likely out of luck with Prism2/2.5/3 cards and their
current firmware.. In other words, it is the firmware that takes care of
the client side operations (auth/assoc/deauth/disassoc). You could use
another card with these functions implemented in the driver, e.g.,
Atheros-based cards for this.

> Trying to learn how to overcome the WIDS and the frames it
> is generating to protect the trusted section of the WLAN.

That sounds like useless "protection" to me if WIDS is sending those
frames over air to client or AP.

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




From wk-hostap  Wed Sep 15 01:47:49 2004
From: wk-hostap (Wilfried Klaebe)
Date: Wed, 15 Sep 2004 10:47:49 +0200
Subject: IEEE 802.11: did not acknowledge authentication response
In-Reply-To: <414668FC.1040107@xactcommerce.com>
References: <414668FC.1040107@xactcommerce.com>
Message-ID: <20040915084749.GA10551@kaos.in-kiel.de>

Am Mon, Sep 13, 2004 at 11:43:56PM -0400 schrieb Grant Limberg:
> I'm trying to set up an open AP on my linux box using the hostap-0.1.3 
> SuSE RPM package on SuSE 9.1 Pro with a D-Link DWL-520 (i dont remember 
> the revision of the card, but it worked in my old linux box as an AP 
> before I upgraded).

> If anyone can help get this working, it would be much appriciated.

I don't think anyone wants to poke around in this version of hostap.
Try something newer first, 0.2.4 for example.

(Isn't this mentioned in some FAQ?)

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From masustec  Wed Sep 15 03:17:17 2004
From: masustec (Mr Asustec)
Date: Wed, 15 Sep 2004 11:17:17 +0100 (BST)
Subject: Disappearing MAC filename in /proc/net/hostap/wlan0
Message-ID: <20040915101717.58287.qmail@web25205.mail.ukl.yahoo.com>


I have observed very strange situation. I have two
stations configured to ad-hoc mode. Sometimes I can
observe other station MAC filename in
/proc/net/hostap/wlan0. Is consists some important
information about actual transmission rate.
Unfortunatelly it disappears from time to time. The
configuration is unchanged and stations sometimes
exchange some data (ping, ftp).
Can anybody provide some explanation of what happens
in HostAP driver?

Regards,
Asustec


	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com



From sime  Wed Sep 15 03:30:24 2004
From: sime (Simon Males)
Date: Wed, 15 Sep 2004 20:30:24 +1000
Subject: skipping signal quality query
Message-ID: <414819C0.5010402@anticd.org>

wlan0: hostap_get_wireless_stats() called while atomic - skipping signal 
quality query

I have a huge amount of these error messages, also my gnome wireless 
applet is usually static at N/A or at least one percentage that will 
never change. Which is a result of /proc/net/wireless remaining static.

There are also times when wavemon will not return anything as well.

I am using the 0.2.4 drivers.

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



From lriis  Wed Sep 15 05:13:32 2004
From: lriis (Lasse Riis)
Date: Wed, 15 Sep 2004 14:13:32 +0200
Subject: PCI NIC with external antenna
Message-ID: <200409151413.32573.lriis@tnb.aau.dk>

Hi

Now my wireless NIC in my thinkpad is finally running, so now I need an AP at 
home. But for people like me, standard APs are not good enough. :) As I 
already have a server (PII 350 MHz) I think adding a wireless PCI NIC with an 
external antenna would be a better idea. However I can't seem to find any 
complete list of cards that actually work in host AP mode.
I've been looking at the "D-Link AirPro DWL-AB520" but I can't seem to confirm 
whether it actually works in host AP mode. So my question basically is: Will 
the D-link card work, and/or could you recommend other cards that have these 
properties.

Also, I'd like to hear from people who have some sort of VPN running on their 
Linux boxen running in host AP mode. Links, tutorials the works

Lasse Riis



From Karl.Rothenhoefer  Wed Sep 15 05:41:28 2004
From: Karl.Rothenhoefer (=?us-ascii?Q?Karl_Rothenhofer?=)
Date: Wed, 15 Sep 2004 14:41:28 +0200
Subject: AW: PCI NIC with external antenna
In-Reply-To: <200409151413.32573.lriis@tnb.aau.dk>
Message-ID: <000001c49b21$5281c980$85c8a8c0@Gericomk>

I had the same question some weeks ago. I decided to buy the Allnet ALL0191
and made good experience with it.  Regards

> -----Ursprungliche Nachricht-----
> Von: hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com
> [mailto:hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com]Im
> Auftrag von Lasse Riis
> Gesendet: Mittwoch, 15. September 2004 14:14
> An: hostap at shmoo.com
> Betreff: PCI NIC with external antenna
>
>
> Hi
>
> Now my wireless NIC in my thinkpad is finally running, so now
> I need an AP at
> home. But for people like me, standard APs are not good
> enough. :) As I
> already have a server (PII 350 MHz) I think adding a wireless
> PCI NIC with an
> external antenna would be a better idea. However I can't seem
> to find any
> complete list of cards that actually work in host AP mode.
> I've been looking at the "D-Link AirPro DWL-AB520" but I
> can't seem to confirm
> whether it actually works in host AP mode. So my question
> basically is: Will
> the D-link card work, and/or could you recommend other cards
> that have these
> properties.
>
> Also, I'd like to hear from people who have some sort of VPN
> running on their
> Linux boxen running in host AP mode. Links, tutorials the works
>
> Lasse Riis
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





From gargid  Wed Sep 15 05:35:41 2004
From: gargid (Gargi D)
Date: Wed, 15 Sep 2004 18:05:41 +0530
Subject: Programming internal Base band processor (HFA3863) registers
Message-ID: <00d401c49b20$8349b100$1006a8c0@rahul>

Hi,

I have a PRISM based 802.11b WLAN card with HFA3863 Base band processor (BBP).  I have the datasheet for HFA3861?  Can I refer the same for HFA3863 for understanding the BBP registers?  I am unable to find the one for HFA3863 on the web.

I am interested in programming the internal register of BBP.  In particular, is it possible to program internal registers of the BBP for short preamble option using writemif?  

I am unable to change using 

"iwpriv wlan0 writemif 2*CR"

Are only certain registers programmable?  How to do I know the programming capability extended by my hardware.

Any insight would be appreciated,

Regards,

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

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


From lriis  Wed Sep 15 05:43:21 2004
From: lriis (Lasse Riis)
Date: Wed, 15 Sep 2004 14:43:21 +0200
Subject: AW: PCI NIC with external antenna
In-Reply-To: <000001c49b21$5281c980$85c8a8c0@Gericomk>
References: <000001c49b21$5281c980$85c8a8c0@Gericomk>
Message-ID: <200409151443.21006.lriis@tnb.aau.dk>

That particular card, doesn't seem to be avialable in Denmark (Where I live). 
Also I'm preferably looking for a 54 Mbps card. As I might upgrade my laptop 
someday.

But thank you for your input. I'm looking through the internet shops for the 
card now. it could run in host-ap mode right?

> I had the same question some weeks ago. I decided to buy the Allnet ALL0191
> and made good experience with it.  Regards
>
> > -----Ursprungliche Nachricht-----
> > Von: hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com
> > [mailto:hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com]Im
> > Auftrag von Lasse Riis
> > Gesendet: Mittwoch, 15. September 2004 14:14
> > An: hostap at shmoo.com
> > Betreff: PCI NIC with external antenna
> >
> >
> > Hi
> >
> > Now my wireless NIC in my thinkpad is finally running, so now
> > I need an AP at
> > home. But for people like me, standard APs are not good
> > enough. :) As I
> > already have a server (PII 350 MHz) I think adding a wireless
> > PCI NIC with an
> > external antenna would be a better idea. However I can't seem
> > to find any
> > complete list of cards that actually work in host AP mode.
> > I've been looking at the "D-Link AirPro DWL-AB520" but I
> > can't seem to confirm
> > whether it actually works in host AP mode. So my question
> > basically is: Will
> > the D-link card work, and/or could you recommend other cards
> > that have these
> > properties.
> >
> > Also, I'd like to hear from people who have some sort of VPN
> > running on their
> > Linux boxen running in host AP mode. Links, tutorials the works
> >
> > Lasse Riis
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap



From Karl.Rothenhoefer  Wed Sep 15 06:24:11 2004
From: Karl.Rothenhoefer (=?iso-8859-1?Q?Karl_Rothenh=F6fer?=)
Date: Wed, 15 Sep 2004 15:24:11 +0200
Subject: AW: AW: PCI NIC with external antenna
In-Reply-To: <200409151443.21006.lriis@tnb.aau.dk>
Message-ID: <000701c49b27$4a508fc0$85c8a8c0@Gericomk>

Yes the ALL0191 card is working with hostap_pci driver and has been tested
in Master mode in my configuration. To my knowledge no 54 Mbps cards have
ever made with Prism chipsets 2, 2.5 or 3 and those are the only chipsets
supported by hostap-drivers. So you may have to give up looking for a 54
Mbps card supported by hostap.


> -----Urspr?ngliche Nachricht-----
> Von: hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com
> [mailto:hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com]Im
> Auftrag von Lasse Riis
> Gesendet: Mittwoch, 15. September 2004 14:43
> An: Karl.Rothenhoefer at t-online.de; hostap at shmoo.com
> Betreff: Re: AW: PCI NIC with external antenna
>
>
> That particular card, doesn't seem to be avialable in Denmark
> (Where I live).
> Also I'm preferably looking for a 54 Mbps card. As I might
> upgrade my laptop
> someday.
>
> But thank you for your input. I'm looking through the
> internet shops for the
> card now. it could run in host-ap mode right?
>
> > I had the same question some weeks ago. I decided to buy
> the Allnet ALL0191
> > and made good experience with it.  Regards
> >
> > > -----Ursprungliche Nachricht-----
> > > Von: hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com
> > > [mailto:hostap-bounces+karl.rothenhoefer=t-online.de at shmoo.com]Im
> > > Auftrag von Lasse Riis
> > > Gesendet: Mittwoch, 15. September 2004 14:14
> > > An: hostap at shmoo.com
> > > Betreff: PCI NIC with external antenna
> > >
> > >
> > > Hi
> > >
> > > Now my wireless NIC in my thinkpad is finally running, so now
> > > I need an AP at
> > > home. But for people like me, standard APs are not good
> > > enough. :) As I
> > > already have a server (PII 350 MHz) I think adding a wireless
> > > PCI NIC with an
> > > external antenna would be a better idea. However I can't seem
> > > to find any
> > > complete list of cards that actually work in host AP mode.
> > > I've been looking at the "D-Link AirPro DWL-AB520" but I
> > > can't seem to confirm
> > > whether it actually works in host AP mode. So my question
> > > basically is: Will
> > > the D-link card work, and/or could you recommend other cards
> > > that have these
> > > properties.
> > >
> > > Also, I'd like to hear from people who have some sort of VPN
> > > running on their
> > > Linux boxen running in host AP mode. Links, tutorials the works
> > >
> > > Lasse Riis
> > > _______________________________________________
> > > 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 jerith  Wed Sep 15 06:17:40 2004
From: jerith (Matt McHenry)
Date: Wed, 15 Sep 2004 09:17:40 -0400 (EDT)
Subject: wap_supplicant only gets to "Sending EAPOL-Key 2/4
In-Reply-To: <20040914074147.D92B418EEA@mail.iocaine.com>
References: <20040914074147.D92B418EEA@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409150912450.6955@shell1.speakeasy.net>


Jouni,

	Using wpa_supplicant from CVS as of sunday, the problem is fixed.
I am now able to connect to my WPA AP with no problems.  Thanks very much
for the quick response and the patch!

> However, thanks for reporting this here, since this also showed a bug in
> wpa_supplicant: it should reject that kind of ReqIEs report and complain
> loadly about it.

> This truncated WPA IE ended up in wpa_supplicant using corrupted WPA IE
> in the msg 2/4. WPA APs are supposed to drop that kind of packets and
> are likely to deauthenticate the STA.

> I fixed this now in wpa_supplicant. I would appreciate it if you test
> the fix with your current setup that can generate this truncated IEs. In
> theory, this fix could even be enough to workaround the problem since
> wpa_supplicant tries to generate WPA IE itself when the driver does not
> report one. If the IEs match, the AP should allow authentication to
> continue.
>
> You can either get the fix for wpa_supplicant by downloading the latest
> CVS snapshot of the development version from http://hostap.epitest.fi/
> or by applying the attached patch to the version you are using.



From praedor  Wed Sep 15 06:40:25 2004
From: praedor (Praedor Atrebates)
Date: Wed, 15 Sep 2004 08:40:25 -0500
Subject: Mandrake Cooker, kernel-2.6.8, and hostap...slow
Message-ID: <200409150840.26619.praedor@yahoo.com>

As the subject indicates, I am running a current cooker (development) version 
of Mandrake on my laptop and have tried the 3rd Party builtin hostap_cs 
driver in kernel-2.6.8.1-2mdk (2.6.8 kernel variant).  I am finding that the 
rate on my card is locked at 2MB/s when using hostap.

I have an Orinoco Gold (Lucent) 802.11b wifi card for my laptop when at home.  
My desktop system, same distro,  to which I connect has a 802.11g card in it.  
When using the default orinoco_cs module, the default transfer rate is 
5.5MB/s.  Last night, I decided to give a shot to the hostap_cs driver 
provided now with the kernel as a 3rd Party addition.  It works fine except 
that the max/default rate is 2MB/s.  I used iwconfig to try to bump up the 
rate to 5, 6, or 11MB/s but nothing changed it from 2MB/s.  Unfortunately, I 
haven't been able to determine exactly what version of hostap is included in 
the current 2.6.8 kernels but I would presume it to be rather recent(?).

Is there a trick to getting the rate boosted upward?

praedor
-- 
"Our ship is in the hands of pilots who are steering directly under full sail 
for a rock.  The whole crew may see this course to violate our liberties in 
full view if they look the right way."
--Samuel Adams, 1771



From martin.polak  Wed Sep 15 07:23:00 2004
From: martin.polak (Martin Polak)
Date: Wed, 15 Sep 2004 16:23:00 +0200
Subject: AW: AW: PCI NIC with external antenna
In-Reply-To: <000701c49b27$4a508fc0$85c8a8c0@Gericomk>
References: <000701c49b27$4a508fc0$85c8a8c0@Gericomk>
Message-ID: <41485044.6040600@liwest.at>

Karl Rothenh?fer wrote:
> Yes the ALL0191 card is working with hostap_pci driver and has been tested
> in Master mode in my configuration. To my knowledge no 54 Mbps cards have
> ever made with Prism chipsets 2, 2.5 or 3 and those are the only chipsets
> supported by hostap-drivers. So you may have to give up looking for a 54
> Mbps card supported by hostap.
> 
> 
> 

Netgear MA-311 PCI also does it very well for me (Prism 2.5 11 Mbps)





From praedor  Wed Sep 15 07:35:08 2004
From: praedor (Praedor Atrebates)
Date: Wed, 15 Sep 2004 09:35:08 -0500
Subject: Mandrake Cooker, kernel-2.6.8, and hostap...slow
In-Reply-To: <200409150840.26619.praedor@yahoo.com>
References: <200409150840.26619.praedor@yahoo.com>
Message-ID: <200409150935.08558.praedor@yahoo.com>

On Wednesday 15 September 2004 08:40, Praedor Atrebates wrote:
> As the subject indicates, I am running a current cooker (development)
> version of Mandrake on my laptop and have tried the 3rd Party builtin
> hostap_cs driver in kernel-2.6.8.1-2mdk (2.6.8 kernel variant).  I am
> finding that the rate on my card is locked at 2MB/s when using hostap.
>
> I have an Orinoco Gold (Lucent) 802.11b wifi card for my laptop when at
> home. My desktop system, same distro,  to which I connect has a 802.11g
> card in it. When using the default orinoco_cs module, the default transfer
> rate is 5.5MB/s.  Last night, I decided to give a shot to the hostap_cs
> driver provided now with the kernel as a 3rd Party addition.  It works fine
> except that the max/default rate is 2MB/s.  I used iwconfig to try to bump
[...]

OK, a google search has led me to find a number of references to this question 
and I see that it may not actually be a factual indication of the rate.

My first indication of a mere 2Mb/s rate was that displayed from Gkrellm, then 
from iwconfig.  I do not use AP mode (yet), just ad-hoc.  I would THINK that 
since I am connecting to an 802.11g device, that the transfer rate would max 
out on the 802.11b card more often than not (and this 2Mb/s report is not 
coincident with a high CPU load).  

In any case, I'll play around to try to determine the "real" transfer rate.

praedor

-- 
"Our ship is in the hands of pilots who are steering directly under full sail 
for a rock.  The whole crew may see this course to violate our liberties in 
full view if they look the right way."
--Samuel Adams, 1771



From ged  Wed Sep 15 09:47:53 2004
From: ged (Ged Haywood)
Date: Wed, 15 Sep 2004 17:47:53 +0100 (BST)
Subject: PCI NIC with external antenna
In-Reply-To: <20040915131011.CB6522BFCC@mail.iocaine.com>
References: <20040915131011.CB6522BFCC@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409151724010.2333@mail3.jubileegroup.co.uk>

Hi there,

On Wed, 15 Sep 2004 Lasse Riis wrote:

> have a server (PII 350 MHz) I think adding a wireless PCI NIC with
> an external antenna would be a better idea. However I can't seem to
> find any complete list of cards that actually work in host AP mode.

I don't think there is one. :(

> I've been looking at the "D-Link AirPro DWL-AB520" but I can't seem
> to confirm whether it actually works in host AP mode.

I don't know, sorry.

> [another] card, doesn't seem to be available in Denmark

I can ship anything you like to Denmark. :)  Unfortunately I cannot
tell you whether it would be legal to use it there... :(

> Also I'm preferably looking for a 54 Mbps card.

As far as I know there is no 54Mbps card which will work with HostAP.

> could you recommend other cards ...

Netgear MA311 (NOT the MA311+ which is TI, not Prism-based).  They
have served me extremely well.  However they are only 11Mbps.  I use
external antennas on two such cards to link to access points mounted
on a tower at the industrial estate where lives one of my businesses.
This gave broadband access to the business when it was not available
from the cable suppliers.  I do not use the MA311 PCI cards as access
points, but they will work that way and I believe that you will have
no difficulty running a VPN over them running in that mode.

> I'd like to hear from people who have some sort of VPN running on
> their Linux boxen running in host AP mode.

I use OpenVPN, continuously, over two radio links and between three
countries.  The product is Open Source, free, and it works.  You will
find that the documentation at the OpenVPN website is quite adequate:

http://openvpn.sourceforge.net/

There are no special considerations for running OpenVPN over a radio
network, as long as the network is reliable.  Excessive duplicated
packets can be troublesome on a radio network but if that is happening
you need to find the reason(s) and fix it(them).

73,
Ged.



From prystelka  Wed Sep 15 10:26:24 2004
From: prystelka (prystelka at interia.pl)
Date: Wed, 15 Sep 2004 17:26:24 -0000
Subject: Promiscuous mode using HostAP driver
Message-ID: <20040915172613.13BDADAC94@poczta.interia.pl>

Hello,

I have a question concerned operation of Prism cards in promiscuous mode.
I use Linksys WPC-11 Prism 3 card.
How to configure it to promiscuous mode?
Should I set something in HostAP driver?
How to check that promiscuous mode is enabled?

Thanks for any help.

Mark




From db  Wed Sep 15 13:01:01 2004
From: db (ARCEO Daniel Beuchler)
Date: Wed, 15 Sep 2004 22:01:01 +0200
Subject: Problems with ALLNET PCI Card
Message-ID: <EMENLEDGIABGALAJCCADAEPFCAAA.db@arceo.de>

Hi there,

im currently trying to setup 
a debian (sarge) box as wlan access point with
hostap driver - im using a allnet PCI card
(Prism 2.5 chipset) - all worked out fine
(out of the box - couldnt believe it ;-)

but *sending* data to/over the access point
is (really) slow/or fails at all ... "download"
means sending data to nodes booked in the
access point - no problem - at accurate speeds ...
I mentioned that after using the WLAN for several
days when i tried to send emails with attachments

testing with orinoco driver in ad-hoc mode 
im facing the same - (even worse) 

i tried fiddling MTU, iwconfig rts, iwconfig frag
but this might be a general problem with my allnet pci 
card ... hardware broken ? cant believe it - FAQ 
mentions that untested hardware might bring 
unexpected results - 

any suggestions?
(debugging possibilities?)

thanks in advance
Daniel



From db  Wed Sep 15 13:20:42 2004
From: db (ARCEO Daniel Beuchler)
Date: Wed, 15 Sep 2004 22:20:42 +0200
Subject: AW: Problems with ALLNET PCI Card
In-Reply-To: <EMENLEDGIABGALAJCCADAEPFCAAA.db@arceo.de>
Message-ID: <EMENLEDGIABGALAJCCADOEPFCAAA.db@arceo.de>

Might be a firmware problem ?

Host AP driver diagnostics information for 'wlan0'
NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.0.5
STAID: id=0x001f v1.3.4 (station firmware)



-----Urspr?ngliche Nachricht-----
Von: hostap-bounces+db=arceo.de at shmoo.com
[mailto:hostap-bounces+db=arceo.de at shmoo.com]Im Auftrag von ARCEO Daniel
Beuchler
Gesendet: Mittwoch, 15. September 2004 22:01
An: hostap at shmoo.com
Cc: gg at arceo.de
Betreff: Problems with ALLNET PCI Card


Hi there,

im currently trying to setup
a debian (sarge) box as wlan access point with
hostap driver - im using a allnet PCI card
(Prism 2.5 chipset) - all worked out fine
(out of the box - couldnt believe it ;-)

but *sending* data to/over the access point
is (really) slow/or fails at all ... "download"
means sending data to nodes booked in the
access point - no problem - at accurate speeds ...
I mentioned that after using the WLAN for several
days when i tried to send emails with attachments

testing with orinoco driver in ad-hoc mode
im facing the same - (even worse)

i tried fiddling MTU, iwconfig rts, iwconfig frag
but this might be a general problem with my allnet pci
card ... hardware broken ? cant believe it - FAQ
mentions that untested hardware might bring
unexpected results -

any suggestions?
(debugging possibilities?)

thanks in advance
Daniel
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap




From stexas  Wed Sep 15 16:25:36 2004
From: stexas (Greg M. Hochstrasser)
Date: Wed, 15 Sep 2004 18:25:36 -0500
Subject: PCI NIC with external antenna
In-Reply-To: <200409151413.32573.lriis@tnb.aau.dk>
References: <200409151413.32573.lriis@tnb.aau.dk>
Message-ID: <8C40A63C-076E-11D9-A344-000A95CA3FBC@mac.com>

take a look here:

http://www.seattlewireless.net/

gmh

On Sep 15, 2004, at 7:13 AM, Lasse Riis wrote:

Hi

Now my wireless NIC in my thinkpad is finally running, so now I need an 
AP at
home. But for people like me, standard APs are not good enough. :) As I
already have a server (PII 350 MHz) I think adding a wireless PCI NIC 
with an
external antenna would be a better idea. However I can't seem to find 
any
complete list of cards that actually work in host AP mode.
I've been looking at the "D-Link AirPro DWL-AB520" but I can't seem to 
confirm
whether it actually works in host AP mode. So my question basically is: 
Will
the D-link card work, and/or could you recommend other cards that have 
these
properties.

Also, I'd like to hear from people who have some sort of VPN running on 
their
Linux boxen running in host AP mode. Links, tutorials the works

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




From HostAP-Research  Wed Sep 15 19:16:19 2004
From: HostAP-Research (AP-Research)
Date: Wed, 15 Sep 2004 21:16:19 -0500 (CDT)
Subject: PCI NIC with external antenna
In-Reply-To: <200409151413.32573.lriis@tnb.aau.dk>
References: <200409151413.32573.lriis@tnb.aau.dk>
Message-ID: <33009.67.174.81.186.1095300979.squirrel@67.174.81.186>


<quote who="Lasse Riis">
> I think adding a wireless PCI NIC with an external antenna would be a
> better idea.

What's magic about a PCI NIC?  Why not a PCI/PCMCIA Bridge and a PCMCIA
NIC? Several come with the option for external antennae... and if the
objective is higher gain at "home", as opposed to a 25Km link, then why
not get a 100/200/300mW card (see www.demarctech.com) and use a diversity
antennae?  I think bridges are cheaper than most antennae of respectable
gain.  One exception is the Pringles or dog food can wave guide ;)

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



From jhiller  Wed Sep 15 20:08:46 2004
From: jhiller (James B Hiller)
Date: Wed, 15 Sep 2004 23:08:46 -0400 (EDT)
Subject: AW: Problems with ALLNET PCI Card
In-Reply-To: <EMENLEDGIABGALAJCCADOEPFCAAA.db@arceo.de>
References: <EMENLEDGIABGALAJCCADOEPFCAAA.db@arceo.de>
Message-ID: <Pine.GSO.4.60.0409152305060.20309@ankara>


Hi!

On Wed, 15 Sep 2004, ARCEO Daniel Beuchler wrote:

> Might be a firmware problem ?
>
> Host AP driver diagnostics information for 'wlan0'
> NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
> PRIID: id=0x0015 v1.0.5
> STAID: id=0x001f v1.3.4 (station firmware)

Yes, might be.  In mid-2003 and earlier, various refs on the list
discussed firmware either 1.3.4 or 1.3.6 and earlier showing issues
with much packet-dropping.

When I took my off-the-shelf 1.3.4 card and flashed to 1.4.9, I had
a vast performance/throughput improvement (like, to rates that
would be expected).  Use 1.7.4 now.  There has been some more recent
discussion about 1.8.0 (for example) also exhibiting some bugginess,
though I don't recall what.

Suggest trying to flash to 1.7.4 and see how you like that.

jbh




From jkmaline  Wed Sep 15 20:46:14 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 20:46:14 -0700
Subject: hostapd with wpa dont work on big endian systems
In-Reply-To: <20040909105507.GO28682@informatik.uni-rostock.de>
References: <20040909105507.GO28682@informatik.uni-rostock.de>
Message-ID: <20040916034613.GC7360@jm.kir.nu>

On Thu, Sep 09, 2004 at 12:55:07PM +0200, Gunter Burchardt wrote:

> I tested hostap with wpa on a big endian system (IXP425). I think there
> is a problem in MIC calculation. Here a log of hostapd. I will try to
> find the problem.

I cannot reproduce this on my big endian test setup (MPC8260-based,
i.e., PowerPC 603e), so I do not think this is an endianness issue. I
was able to use x86 wpa_supplicant with both WPA-PSK and WPA-EAP when
hostapd was running on this big-endian board. ARM has other differences
that may have been missed somewhere.

Could you please try whether WPA-PSK works? Another verification would
be to compare hostapd debug log to supplicant log. It would be good to
verify that the session key from IEEE 802.1X/EAP matches and whether
PMK/PTK in WPA handshake get same values.

SHA-1 code has integrated test cases. I would be interested in seeing
those being run on the IXP425 board that had this issue with WPA-EAP.
You can compile this with

gcc -o sha1-test -DTEST_MAIN sha1.c

(well, gcc replaced with suitable cross-compiler, if needed)


PS.

Your debug log excerpt had truncated lines, so I was unable to verify
whether the reported PTK would have matched with the EAPOL-Key MIC.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:04:10 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:04:10 -0700
Subject: AW: Problems with ALLNET PCI Card
In-Reply-To: <EMENLEDGIABGALAJCCADOEPFCAAA.db@arceo.de>
References: <EMENLEDGIABGALAJCCADAEPFCAAA.db@arceo.de>
	<EMENLEDGIABGALAJCCADOEPFCAAA.db@arceo.de>
Message-ID: <20040916040410.GD7360@jm.kir.nu>

On Wed, Sep 15, 2004 at 10:20:42PM +0200, ARCEO Daniel Beuchler wrote:

> Might be a firmware problem ?
> 
> Host AP driver diagnostics information for 'wlan0'
> NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
> PRIID: id=0x0015 v1.0.5
> STAID: id=0x001f v1.3.4 (station firmware)

PRI f/w v1.0.5 and STA f/w v1.3.4 have known issues that cause data
corruption on PCI bus (in practice, a lot of packets get dropped; some
of these should show up in 'dmesg' output). These bugs were corrected in
PRI v1.0.7 and STA v1.3.5 if I remember correctly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:06:03 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:06:03 -0700
Subject: Programming internal Base band processor (HFA3863) registers
In-Reply-To: <00d401c49b20$8349b100$1006a8c0@rahul>
References: <00d401c49b20$8349b100$1006a8c0@rahul>
Message-ID: <20040916040603.GE7360@jm.kir.nu>

On Wed, Sep 15, 2004 at 06:05:41PM +0530, Gargi D wrote:

> I have a PRISM based 802.11b WLAN card with HFA3863 Base band processor (BBP).  I have the datasheet for HFA3861?  Can I refer the same for HFA3863 for understanding the BBP registers?  I am unable to find the one for HFA3863 on the web.

I would not recommend doing that. These chips have some differences..

> Are only certain registers programmable?  How to do I know the programming capability extended by my hardware.

Many of the registers are controlled by MAC/firmware. Even if you were
able to change them, they are likely returned to their previous values
shortly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:12:58 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:12:58 -0700
Subject: tx_rate in adhoc
In-Reply-To: <20040913094636.27936.qmail@web25209.mail.ukl.yahoo.com>
References: <20040913094636.27936.qmail@web25209.mail.ukl.yahoo.com>
Message-ID: <20040916041258.GF7360@jm.kir.nu>

On Mon, Sep 13, 2004 at 10:46:36AM +0100, Mr Asustec wrote:

> In adhoc mode, the tx_rate value in transmitted frame
> descriptor txdesc often has the value of 0 (prism2_tx,
> prism2_tx_ev). Sometimes it gets the proper
> transmission rate value but not always. What may be
> the reason?

Host AP driver relies on station firmware to take care of TX rate
control for adhoc mode. The rate control algorithm in the driver is only
used if there is a station entry (e.g., procfs file with MAC address in
/proc/net/hostap/wlan0) for the destination address and these are
normally used only in Master mode and with WDS links.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:19:24 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:19:24 -0700
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <413D8C9A.9030707@pl.net>
References: <413D11D0.8050203@pl.net> <20040907025300.GB7392@jm.kir.nu>
	<413D8C9A.9030707@pl.net>
Message-ID: <20040916041924.GG7360@jm.kir.nu>

On Tue, Sep 07, 2004 at 10:25:30PM +1200, Morgan Read wrote:

> Well that was much more exciting!  At least to my eyes...
> 
> I ran as you suggested per the hostap driver (not wext).

Yes, indeed, this time the EAPOL negotiation was at least started.
However, the AP/authentication server did not seem to like the identity
response from the client.

> EAP: Received EAP-Request method=1 id=2
> EAP: EAP entering state IDENTITY
> EAP: EAP-Request Identity data - hexdump_ascii(len=0):
> EAP: using real identity - hexdump_ascii(len=10):
>      45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005

Are you sure that is the current username? If "EC" is the domain part,
that should most likely be EC\mrea005, not EC/mrea005.. 

> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> Setting scan request: 0 sec 100000 usec
> EAPOL: External notification - portEnabled=0
> EAPOL: SUPP_PAE entering state DISCONNECTED

It looks like the AP disassociated the stations. This could have
happened, e.g., because the authentication server rejected access to
EC/mrea005 identity.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:23:09 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:23:09 -0700
Subject: Broadcast/multicast ack?
In-Reply-To: <20040902102356.82525.qmail@web25206.mail.ukl.yahoo.com>
References: <20040902102356.82525.qmail@web25206.mail.ukl.yahoo.com>
Message-ID: <20040916042309.GH7360@jm.kir.nu>

On Thu, Sep 02, 2004 at 11:23:56AM +0100, Mr Asustec wrote:

> I observed prism2_tx_ev called after
> broadcast/multicast frames in adhoc network. As I know
> the broadcast frames should not be acknowledged
> according to standard. Is it possible to switch the
> driver to acknowledge unicast frames only?

Multicast frames are indeed not acknowledged. TX event is generated for
successful frame transmission, not for receiving of ACK.. In case of
unicast, this is indeed ACK, but for multicast, transmission of the
frame is enough to trigger this event.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:25:34 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:25:34 -0700
Subject: key_idx?
In-Reply-To: <1094099637.4136a2b5b0b5f@www-mail.usyd.edu.au>
References: <1094099637.4136a2b5b0b5f@www-mail.usyd.edu.au>
Message-ID: <20040916042534.GI7360@jm.kir.nu>

On Thu, Sep 02, 2004 at 02:33:57PM +1000, snai8255 at mail.usyd.edu.au wrote:

> i was wondering what is the "key_idx" field in "prism2_wep_data" structure in hostap_crypt_wep.c
> used for?

IEEE 802.11 supports four separate defaults keys and this key_idx is
indicating which one of these is being used.

> also does anyone know where is the "prism_wep_init" function called from within the driver?

Search for ops->init in hostap_ioctl.c..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 15 21:27:56 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 15 Sep 2004 21:27:56 -0700
Subject: linux crypto api
In-Reply-To: <1094015355.4135597b1b92a@www-mail.usyd.edu.au>
References: <1094015355.4135597b1b92a@www-mail.usyd.edu.au>
Message-ID: <20040916042756.GJ7360@jm.kir.nu>

On Wed, Sep 01, 2004 at 03:09:15PM +1000, snai8255 at mail.usyd.edu.au wrote:

> i want hostap to use the linux crypto api,any idea on how i can achieve this?i can see in the code
> checking if HOSTAP_USE_CRYPTO_API is defined.do i simple add #define HOSTAP_USE_CRYPTO_API at the
> top of hostap_crypt_wep.c and recompile the driver or is there a better way of doing this?

You can define this in driver/modules/hostap_config.h.

-- 
Jouni Malinen                                            PGP id EFC895FA



From zen_hacker  Wed Sep 15 13:12:59 2004
From: zen_hacker (Brian Sturgill)
Date: Wed, 15 Sep 2004 20:12:59 +0000
Subject: Mandrake Cooker, kernel-2.6.8, and hostap...slow
Message-ID: <BAY13-F40Yrbj1E67qa00007238@hotmail.com>

I have the same problem with Orinoco clients on Hostap. You can force it to 
11Meg by iwconfig wlan0 rate 11M. This will not allow the AP to go to lower 
speeds when a client needs it. This also is not a true fix because even 
though the Orinoco client and cat /proc/net/hostap/wlan0/(macaddress) show 
11Mbps, the transfer rate is still much slower than a Prism card client 
connected to the Hostap machine. My prism based Wet11's connect fine to my 
hostap box, my Orinoco AP500  and AP1000. A hostap client in managed mode 
connects fine to to the Orinoco AP's fine also. The prism cards in hostap 
mode just don't seem to like the orinoco clients. I also tried a Dell 
Truemobile 1300 USB (Broadcom chipset?) connecting to my Hostap box. It is 
even slower than the Orinoco even with a signal level of -43dB. I am just 
sticking with prism based clients until I get more time to dig into it or 
someone else figures it out.

Brian


>From: Praedor Atrebates <praedor at yahoo.com>
>To: hostap at shmoo.com
>Subject: Mandrake Cooker, kernel-2.6.8, and hostap...slow
>Date: Wed, 15 Sep 2004 08:40:25 -0500
>
>As the subject indicates, I am running a current cooker (development) 
>version
>of Mandrake on my laptop and have tried the 3rd Party builtin hostap_cs
>driver in kernel-2.6.8.1-2mdk (2.6.8 kernel variant).  I am finding that 
>the
>rate on my card is locked at 2MB/s when using hostap.
>
>I have an Orinoco Gold (Lucent) 802.11b wifi card for my laptop when at 
>home.
>My desktop system, same distro,  to which I connect has a 802.11g card in 
>it.
>When using the default orinoco_cs module, the default transfer rate is
>5.5MB/s.  Last night, I decided to give a shot to the hostap_cs driver
>provided now with the kernel as a 3rd Party addition.  It works fine except
>that the max/default rate is 2MB/s.  I used iwconfig to try to bump up the
>rate to 5, 6, or 11MB/s but nothing changed it from 2MB/s.  Unfortunately, 
>I
>haven't been able to determine exactly what version of hostap is included 
>in
>the current 2.6.8 kernels but I would presume it to be rather recent(?).
>
>Is there a trick to getting the rate boosted upward?
>
>praedor
>--
>"Our ship is in the hands of pilots who are steering directly under full 
>sail
>for a rock.  The whole crew may see this course to violate our liberties in
>full view if they look the right way."
>--Samuel Adams, 1771
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From db  Thu Sep 16 01:34:48 2004
From: db (ARCEO Daniel Beuchler)
Date: Thu, 16 Sep 2004 10:34:48 +0200
Subject: AW: PCI NIC with external antenna
In-Reply-To: <8C40A63C-076E-11D9-A344-000A95CA3FBC@mac.com>
Message-ID: <EMENLEDGIABGALAJCCADKEPMCAAA.db@arceo.de>

After flashing the firmware my Allnet PCI Card 0191 works
fine - its "pure pci" (no cardbus/pcmcia on pci) - and
it works out of the box with Debian/Sarge ... you can connect
an external antenna (at least you can remove the one that comes
with it ;-)

Daniel

-----Ursprungliche Nachricht-----
Von: hostap-bounces+db=arceo.de at shmoo.com
[mailto:hostap-bounces+db=arceo.de at shmoo.com]Im Auftrag von Greg M.
Hochstrasser
Gesendet: Donnerstag, 16. September 2004 01:26
An: Lasse Riis
Cc: hostap at shmoo.com
Betreff: Re: PCI NIC with external antenna


take a look here:

http://www.seattlewireless.net/

gmh

On Sep 15, 2004, at 7:13 AM, Lasse Riis wrote:

Hi

Now my wireless NIC in my thinkpad is finally running, so now I need an 
AP at
home. But for people like me, standard APs are not good enough. :) As I
already have a server (PII 350 MHz) I think adding a wireless PCI NIC 
with an
external antenna would be a better idea. However I can't seem to find 
any
complete list of cards that actually work in host AP mode.
I've been looking at the "D-Link AirPro DWL-AB520" but I can't seem to 
confirm
whether it actually works in host AP mode. So my question basically is: 
Will
the D-link card work, and/or could you recommend other cards that have 
these
properties.

Also, I'd like to hear from people who have some sort of VPN running on 
their
Linux boxen running in host AP mode. Links, tutorials the works

Lasse Riis
_______________________________________________
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 ceyong  Thu Sep 16 05:36:12 2004
From: ceyong (Yong Chu Eu Ñî×ÓÓÓ)
Date: Thu, 16 Sep 2004 05:36:12 -0700 (PDT)
Subject: Low AP Signal
Message-ID: <20040916123612.68021.qmail@web41005.mail.yahoo.com>

HI,i setup 2 AP(i had flash the firmware from 0.8.3 to 1.5.6) with HOSTAP
0.1.3 with patch 0.1.0. When everything fine, i test the signal with
windows xp as client to see the signal strenght,one of my AP show a low
signal strenght(1 of 4 block) while another one is ok. Actually
configuration & software i installed for both pc almost the same,whty this
happend? Any kind expert can help? Thanks First

=====
???????????????????????? Happy & Healthy Always ! ^_^ !
???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
???????????? Buddhist Page: http://planet.time.net.my/SunwayCity/ceyong/artikel.htm


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



From kyle  Thu Sep 16 07:04:13 2004
From: kyle (Kyle McMartin)
Date: Thu, 16 Sep 2004 10:04:13 -0400
Subject: Interesting issues with CCMP
Message-ID: <20040916140413.GD2973@roadwarrior.mcmartin.ca>

Hello,

When using the latest version of hostap (either 0.2.4, or CVS HEAD) with
CCMP on my WPA2 network with wpa_supplicant, I see a massive
amount of kernel error messages generated...

printk: 267 messages suppressed.
CCMP: decrypt failed: STA=00:06:25:4a:9d:e4
wifi0: decryption failed (SA=00:06:25:4a:9d:e4) res=-5
wifi0: decryption failed (SA=00:06:25:4a:9d:e4) res=-5
(ad infinitum)

The network works, but it seems to be slower than it should.

This is using,

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.7.4 (station firmware)

[I'd to upgrade the cards firmware]

0000:01:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)

My wpa_supplicant.conf stanza for this looks like,

eapol_version=1
network={
        ssid="8021xTest"
        key_mgmt=WPA-EAP
        eap=TLS
        identity="kyle"
        ca_cert="/home/kyle/tmp/kyle.pem"
        client_cert="/home/kyle/tmp/kyle.pem"
        private_key="/home/kyle/tmp/kyle.pem"
        private_key_passwd="<password>"
        # eapol_flags=3
        priority=5
}

Which came in my IBM Thinkpad X30.

Any insight into this would be appreciated.

Also, I'd just like to thank Jouni, and all contributors, for the
excellent driver.

Cheers,
	Kyle.



From ged  Thu Sep 16 08:18:36 2004
From: ged (Ged Haywood)
Date: Thu, 16 Sep 2004 16:18:36 +0100 (BST)
Subject: PCI NIC with external antenna
In-Reply-To: <20040916034932.DD37F2BFF2@mail.iocaine.com>
References: <20040916034932.DD37F2BFF2@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409161602370.29236@mail3.jubileegroup.co.uk>

Hello again,

On Wed, 15 Sep 2004 KC Ferguson wrote:

> if the objective is higher gain at "home", as opposed to a 25Km
> link, then why not get a 100/200/300mW card (see www.demarctech.com)
> and use a diversity antennae?

The higher power cards are not legal in Denmark.  Effective Isotropic
Radiated Power (EIRP) is limited to 100mW in Europe.

There are still unanswered questions about the health implications of
microwave radiation.  I'd much prefer to send the 30mW from my Netgear
cards along a cable to an aerial on the roof, than to bathe my body in
the 300mW from a high-power card on my desk.

http://www.rfi-wireless.com/rfilibrary/articles/art024-rfican.htm
http://www.radioregs.co.uk/p03.htm

73,
Ged.



From philippe.teuwen  Thu Sep 16 08:40:04 2004
From: philippe.teuwen (Philippe Teuwen)
Date: Thu, 16 Sep 2004 17:40:04 +0200 (CEST)
Subject: Patch submission: multi-PSK support for hostapd
Message-ID: <27120.57.67.161.6.1095349204.squirrel@ssl.teuwen.org>

Hello,

My name is Philippe Teuwen and I'm working for Philips N.V.,
assisted by my colleague Ventzislav Nikov.
Our job consisted last weeks in the implementation of a new feature
in hostapd for a standardisation validation based on actual prototyping.

We decided, after agreement by our legal department, to release our
patch because it can have an added value for everybody.
Actually a first patch was already delivered directly to Jouni Malinen
and this one is a new version after integration of his previous clever
remarks.

Please find the description and comments in this mail and the attached
diff (sorry it's against v0.2.4 as we started with 0.2.3 and not the
last cvs snapshot which should contain right now already some premices
of multi-PSK as Jouni started on his side after our first discussion).

Remark: I tried first to post this message at the beginning of the week
but not gzipped but it was blocked because of the size so sorry for
any inconvenience if you get twice this mail in the next hours/days.

Functional changes:
===================
This patch implement two main features:

First it allows multiple PSKs to be used simultaneously.
Some can be flagged as guest PSKs, PSKs intended to be share with guest
devices.
Second it allows this multiple PSKs configuration to be dynamically updated.
This is achieved via a file and SIGUSR2.
According to Jouni, this is not the best option so in the future this
will be migrated to a UNIX socket communication between a small CLI
and the hostapd daemon.

cf patch of README file for user interaction details.

Why this patch?:
================
WPA-PSK is very limited for a home network.
It doesn't provide any mecanism to allow an easy and secure guest access.
Sharing your PSK with your guests is not what you want and having to renew
the PSK after a guest leaves is very annoying.
Moreover, due to the way WPA-PSK is defined, a guest knowing the PSK used
in the home network can crack all the PTKs in use in the network as the
rest of the informations are directly accessible to someone knowing the PSK.
Therefore we wrote this patch to allow easy and secure guest access
scenarios. The basic scenario is to define two common PSKs, one for the home
devices and one for the guest devices. You are then free to renew
the guest PSK whenever you want without perturbing the home devices.
But the implementation is generic enough to allow much more complex scenarii.
For example the PSK can be seen as a private password and you distribute
different passwords to each of your clients.
Now that as the wpa_psk field can be more complex, we found easier
and more coherent to support passphrases the way wpa_supplicant does.
Therefore only wpa_psk keyword remains, wpa_passphrase was removed.

Why going for plain EAP was not an option for us?
The context we are considering is the "Home Networking" and in the future
Home Networking will be more and more CE centric than PC centric.
Therefore we cannot afford an authentication server integrated in a
non-PC authenticator. Today APs proposing WPA-Enterprise rely on an
external authentication server, cf the Linksys solution for example.
Moreover CE STA devices can't neither afford certificates nor complex
cryptographic operations (public key) nor complex user interfaces,
imagine your wireless mp3 player...
There are other ligher promising options in the EAP methods such as
EAP-PSK and it could give the same functionality as our multiple-PSK
and indeed we first investigated this way but it is not yet
standardized (still draft) and according to the author there is still
some merging effort to do with similar EAP drafts so we cannot rely on
the fact CE devices will all support the EAP-PSK method while any
WPA/WPA2 device already supports PSK.


Involved developers:
====================

Philippe Teuwen   <philippe.teuwen at philips.com>
Ventzislav Nikov <ventzislav.nikov at philips.com>

License:
========

Our patch is released under the following license.
The license below is a clarified version of the standard open source BSD
license.Contributions released under this license can be incorporated into
GPL-licensed open source projects:

This software and associated documentation files (the "Software") are
copyright ? 2003 Koninklijke Philips Electronics N.V. All Rights Reserved.

A copyright license is hereby granted for redistribution and use of
the Software in source and binary forms, with or without modification,
provided that the following conditions are met:
?  Redistributions of source code must retain the above copyright notice,
thiscopyright license and the following disclaimer.
?  Redistributions in binary form must reproduce the above copyright
notice, thiscopyright license and the following disclaimer in the
documentation and/orothermaterials provided with the distribution.
?  Neither the name of Koninklijke Philips Electronics N.V. nor the names
of itssubsidiaries may be used to endorse or promote products derived from
theSoftwarewithout specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-multiPSK-0.2.4.diff.gz
Type: application/x-tar
Size: 8109 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20040916/269df441/attachment.tar 


From mrobinson28  Thu Sep 16 12:48:48 2004
From: mrobinson28 (michael robinson)
Date: Thu, 16 Sep 2004 15:48:48 -0400
Subject: Ndiswrapper + WPA ....failed to initiate AP scan? 
Message-ID: <BAY18-F181vhXt98JiI0000daf6@hotmail.com>

Every time I attempt to connect with wpa_supplicant I always eventually get:

     Authentication with 00:06:da:38:f5 timed out

and then a little latter...

     Failed to initiate AP scan

Then I guess the process times out and nothing else happens. I have tried 
every combination of configurations that I have read in the archives but to 
no avail.

My current setup is Fedora Core 2 with a Linksys WMP54G card attempting to 
connect to a WRT54G router. I have ndiswrapper version .10 installed (and 
working fine without encryption). I have attempted using two different 
broadcom drivers for the nic both bcmwl5a and bcmwl5. Both of these drivers 
work for me without encryption.

wpa_supplicant.conf currently contains:

crtl_interface=/var/run/wpa_supplicant #for wpa_cli support

ap_scan=1

network={
  ssid="mynetwork"
  scan_ssid=1
  psk="mypassword"
  key_mgmt=WPA-PSK
  pairwise=TKIP CCMP
  proto=WPA
}

Any help is very appreciated





From mrobinson28  Thu Sep 16 14:07:01 2004
From: mrobinson28 (michael robinson)
Date: Thu, 16 Sep 2004 17:07:01 -0400
Subject: wap_supplicant only gets to "Sending EAPOL-Key 2/4"
Message-ID: <BAY18-F36UWgP1A83xi00014f22@hotmail.com>

I may have posted to quickly (ndiswrapper + WPA... failed to initiate AP 
scan?) because this is the exact same thing that is occuring to me.

I looked around the ndiswrapper boards and didn't find any help. Did I just 
miss it?

Michael





From cijoml  Thu Sep 16 15:36:43 2004
From: cijoml (Bc. Michal Semler)
Date: Fri, 17 Sep 2004 00:36:43 +0200
Subject: LEAP and not broadcasted ESSID - problem??
Message-ID: <200409170036.43248.cijoml@volny.cz>

Hi,

I need to connect to CISCO LEAP AP - Cisco 1100. Admin gave me my 
login/password and AP is configured to use dynamical WEP. Username/password 
are handled via RADIUS. AP hides it's ESSID.

I wasn't successfull. Can you tell me wheres problem?

My card is hostap_cs - hostap0.2.4
wpa_supplicant 0.2.4

hostap_cs: 0.2.4 - 2004-07-17 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=50 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 5.0, irq 10, io 0x0100-0x013f
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.0
wifi0: registered netdevice wlan0
---
wpa_supplicant:
.config:
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_WEXT=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_LEAP=y

conf:
# LEAP with dynamic WEP keys
network={
    ssid="CVUT-13136-EAP"
    key_mgmt=IEEE8021X
    eap=LEAP
    scan_ssid=1
    identity="username"
    password="pass"
}

Then I call wpa_supplicant and gets this error:

Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=14):
     43 56 55 54 2d 31 33 31 33 36 2d 45 41 50         CVUT-13136-EAP
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to initiate AP scan.

That's probably that problem....how can I fix it? For test purposes I run 
wpa_supplicant as root

Thanks a lot!

Michal



From HostAP-Research  Thu Sep 16 16:32:03 2004
From: HostAP-Research (AP-Research)
Date: Thu, 16 Sep 2004 18:32:03 -0500 (CDT)
Subject: PCI NIC with external antenna
Message-ID: <32880.67.174.81.186.1095377523.squirrel@67.174.81.186>


<quote who="Ged Haywood">
> Hello again,
>
> On Wed, 15 Sep 2004 KC Ferguson wrote:
>
>> if the objective is higher gain at "home", as opposed to a 25Km
>> link, then why not get a 100/200/300mW card (see www.demarctech.com)
>> and use a diversity antenna?
>
> The higher power cards are not legal in Denmark.  Effective Isotropic
> Radiated Power (EIRP) is limited to 100mW in Europe.

Then choose a 100mW card if that satisfies your link budget and local
laws...  My response to the original question posed by Lasse Riis was to
point out a cost alternative to a PCI ONLY card with an external antenna. 
There are several PCMCIA cards which have detachable diversity antennas
and they run perfectly fine in a PCI/PCMCIA bridge.


** Off Topic **

> There are still unanswered questions about the health implications of
> microwave radiation.  I'd much prefer to send the 30mW from my Netgear
> cards along a cable to an aerial on the roof, than to bathe my body in
> the 300mW from a high-power card on my desk.

EIRP is the sum of the power sent to the antenna plus antenna gain.  So a
30mW card with a 5dBi antenna gives an EIRP of approximately 95mW.  The
only difference is where the RF originates.  Signal Strength/Power at a
given location is still relative to the EIRP and the distance from the RF
source.  For any given location you are still "bathing" in an RF cell.


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



From abonilla  Thu Sep 16 13:08:54 2004
From: abonilla (Alejandro Bonilla)
Date: Thu, 16 Sep 2004 14:08:54 -0600
Subject: wpa_supplicant and IPW2100 Driver.
Message-ID: <4149F2D6.7010000@linuxwireless.org>

Hi,

    I'm new to the list. I hope this is also related to wpa_supplicant.
I want to get wpa_supplicant to work with LEAP authentication Open/WEP/LEAP.

1. Is there a driver requirement for this? I mean should the Driver 
Support WPA even if not using it?
2. Have anyone here heard of someone using an Intel 2100 that worked 
with LEAP and wpa_supp?

This is my config.

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
pairwise=NONE
ssid=1200
key_mgmt=IEEE8021X
eap=LEAP
identity="administrator at domain.com"
password="mypassword"
}


Any info will be greatly appreciated.

Output:

First iwconfig eth1 essid 1200 enc 1234567890 open
Once associated :

debian: /root/hostap/wpa_supplicant# ./wpa_supplicant -dd -i eth1 -c 
/root/wpa_supplicant.conf
Configuration file '/root/wpa_supplicant.conf' -> 
'/root/wpa_supplicant.conf'
Reading configuration file '/root/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
Line: 5 - start of a new network block
pairwise: 0x1
ssid - hexdump_ascii(len=2):
     12 00                                             __
key_mgmt: 0x8
eap methods - hexdump(len=2): 11 00
identity - hexdump_ascii(len=23):
     61 64 6d 69 6e 69 73 74 72 61 74 6f 72 40 69 6e   administrator at do
     74 65 6c 2e 63 6f 6d                              main.com
password - hexdump_ascii(len=5):
     69 6e 74 65 6c                                    mypassword
Priority group 0
   id=0 ssid='_'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:04:23:50:cf:eb
wpa_driver_wext_set_wpa
ioctl[SIOCSIWAUTH]: Operation not supported
Failed to enable WPA in the driver.
wpa_driver_wext_set_wpa
ioctl[SIOCSIWAUTH]: Operation not supported
Failed to disable WPA in the driver.
wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported

Thanks,

- Alex



From ramalhais  Thu Sep 16 19:27:26 2004
From: ramalhais (Pedro Ramalhais)
Date: Fri, 17 Sep 2004 03:27:26 +0100
Subject: wpa_supplicant and IPW2100 Driver.
In-Reply-To: <4149F2D6.7010000@linuxwireless.org>
References: <4149F2D6.7010000@linuxwireless.org>
Message-ID: <1095388031.2448.8.camel@rootix>

On Thu, 2004-09-16 at 21:08, Alejandro Bonilla wrote:
> Hi,
> 
>     I'm new to the list. I hope this is also related to wpa_supplicant.
> I want to get wpa_supplicant to work with LEAP authentication Open/WEP/LEAP.
> 
> 1. Is there a driver requirement for this? I mean should the Driver 
> Support WPA even if not using it?

wpa_supplicant always tries to enable WPA in the driver even if it's not
going to be used, so, apply Lubomir Gelo's ipw2100 wpa patch and the
wpa_supplicant CVS ipw2100 patch i have attached to this email(this
patch already include a .config, so just apply the patch and type make
in the wpa_supplicant directory).

> 2. Have anyone here heard of someone using an Intel 2100 that worked 
> with LEAP and wpa_supp?
> 
> This is my config.
> 
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> network={
> pairwise=NONE

you can remove pairwise=NONE

> ssid=1200
> key_mgmt=IEEE8021X
> eap=LEAP
> identity="administrator at domain.com"
> password="mypassword"
> }
> 
> 
> Any info will be greatly appreciated.
> 
> Output:
> 
> First iwconfig eth1 essid 1200 enc 1234567890 open
> Once associated :
> 
> debian: /root/hostap/wpa_supplicant# ./wpa_supplicant -dd -i eth1 -c 
> /root/wpa_supplicant.conf
> Configuration file '/root/wpa_supplicant.conf' -> 
> '/root/wpa_supplicant.conf'
> Reading configuration file '/root/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group=0
> eapol_version=1
> ap_scan=1
> Line: 5 - start of a new network block
> pairwise: 0x1
> ssid - hexdump_ascii(len=2):
>      12 00                                             __
> key_mgmt: 0x8
> eap methods - hexdump(len=2): 11 00
> identity - hexdump_ascii(len=23):
>      61 64 6d 69 6e 69 73 74 72 61 74 6f 72 40 69 6e   administrator at do
>      74 65 6c 2e 63 6f 6d                              main.com
> password - hexdump_ascii(len=5):
>      69 6e 74 65 6c                                    mypassword
> Priority group 0
>    id=0 ssid='_'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Own MAC address: 00:04:23:50:cf:eb
> wpa_driver_wext_set_wpa
> ioctl[SIOCSIWAUTH]: Operation not supported
> Failed to enable WPA in the driver.
> wpa_driver_wext_set_wpa
> ioctl[SIOCSIWAUTH]: Operation not supported
> Failed to disable WPA in the driver.
> wpa_driver_wext_set_drop_unencrypted
> ioctl[SIOCSIWAUTH]: Operation not supported
> wpa_driver_wext_set_countermeasures
> ioctl[SIOCSIWAUTH]: Operation not supported

wpa_driver_wext driver uses wireless extensions 18 to setup WPA related
stuff, so you need to tell wpa_supplicant to use driver_ipw2100:

./wpa_supplicant -dd -i eth1 -c /etc/wpa_supplicant-LEAP.conf -Dipw2100

Hope this helps, good luck!

> 
> Thanks,
> 
> - Alex


-- 
Pedro Ramalhais <ramalhais at serrado.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hostap-CVS-ipw2100-lubomir.diff
Type: text/x-patch
Size: 12892 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20040917/2ade92ac/attachment.bin 


From jkmaline  Thu Sep 16 19:36:25 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 16 Sep 2004 19:36:25 -0700
Subject: Interesting issues with CCMP
In-Reply-To: <20040916140413.GD2973@roadwarrior.mcmartin.ca>
References: <20040916140413.GD2973@roadwarrior.mcmartin.ca>
Message-ID: <20040917023625.GB7354@jm.kir.nu>

On Thu, Sep 16, 2004 at 10:04:13AM -0400, Kyle McMartin wrote:

> When using the latest version of hostap (either 0.2.4, or CVS HEAD) with
> CCMP on my WPA2 network with wpa_supplicant, I see a massive
> amount of kernel error messages generated...

> CCMP: decrypt failed: STA=00:06:25:4a:9d:e4

What kind of device do you use as the AP?

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Sep 16 19:39:56 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 16 Sep 2004 19:39:56 -0700
Subject: Ndiswrapper + WPA ....failed to initiate AP scan?
In-Reply-To: <BAY18-F181vhXt98JiI0000daf6@hotmail.com>
References: <BAY18-F181vhXt98JiI0000daf6@hotmail.com>
Message-ID: <20040917023956.GC7354@jm.kir.nu>

On Thu, Sep 16, 2004 at 03:48:48PM -0400, michael robinson wrote:

> Every time I attempt to connect with wpa_supplicant I always eventually get:
>     Authentication with 00:06:da:38:f5 timed out
> and then a little latter...
>     Failed to initiate AP scan

> My current setup is Fedora Core 2 with a Linksys WMP54G card attempting to 
> connect to a WRT54G router. I have ndiswrapper version .10 installed (and 
> working fine without encryption). I have attempted using two different 
> broadcom drivers for the nic both bcmwl5a and bcmwl5. Both of these drivers 
> work for me without encryption.

Please post a full wpa_supplicant debug log (with -dd on command line).
In addition, you might want to upgrade ndiswrapper and/or wpa_supplicant
to the latest development version. If I understood correctly,
ndiswrapper .10 has a bug in WPA IE processing that may cause problems
that could match with your description here. Development version of
wpa_supplicant has a workaround for this and I would assume development
version of ndiswrapper has this issue fixed (I haven't verified this).

-- 
Jouni Malinen                                            PGP id EFC895FA



From ged  Fri Sep 17 00:07:51 2004
From: ged (Ged Haywood)
Date: Fri, 17 Sep 2004 08:07:51 +0100 (BST)
Subject: PCI NIC with external antenna
In-Reply-To: <20040917020947.8F67D2C0EB@mail.iocaine.com>
References: <20040917020947.8F67D2C0EB@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409170804330.10914@mail3.jubileegroup.co.uk>

Hi there,

On Thu, 16 Sep 2004 KC Ferguson wrote:

> ** Off Topic **
>
> > There are still unanswered questions about the health implications
> >
> EIRP is the sum of the power sent to the antenna plus antenna gain.  So a
> 30mW card with a 5dBi antenna gives an EIRP of approximately 95mW.  The
> only difference is where the RF originates.  Signal Strength/Power at a
> given location is still relative to the EIRP and the distance from the RF
> source.  For any given location you are still "bathing" in an RF cell.

You're forgetting that the aerials are directional - even the omnis.

73,
Ged.



From mstuff  Fri Sep 17 01:43:09 2004
From: mstuff (Morgan Read)
Date: Fri, 17 Sep 2004 20:43:09 +1200
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <20040916041924.GG7360@jm.kir.nu>
References: <413D11D0.8050203@pl.net>
	<20040907025300.GB7392@jm.kir.nu>	<413D8C9A.9030707@pl.net>
	<20040916041924.GG7360@jm.kir.nu>
Message-ID: <414AA39D.1060300@pl.net>

Hi Jouni
Progress!

With that little correction I now seem to be getting though the first
phase of the process?!:-)  (See debug below).

But, I'm getting stuck with my private key?  I've included what
seemed to be one cycle of the debug below, plus a couple of extra
error examples which are a little different (first).

Here's the command I used to generate the private key; the instructions 
I followed are from a v basic howto for xsupplicant at my uni:
<http://www.ece.auckland.ac.nz/%7Etcol036/wireless/wireless.html> -

"openssl genrsa -out client.key 1024"

All help very much appreciated!
Regards,
Morgan.

****************************************
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:140CB07C:SSL
routines:SSL_use_PrivateKey_file:bad ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.

###################################

EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:0B07C065:x509 certificate
routines:X509_STORE_add_cert:cert already in hash table
SSL - SSL error: error:140CB07C:SSL routines:SSL_use_PrivateKey_file:bad
ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.

####################################

Setting scan request: 0 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=3):
      75 6f 61                                          uoa
Wireless event: cmd=0x8b19 len=12
Received 158 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:ed:99:37:c0 ssid='uoa' wpa_ie_len=0 rsn_ie_len=0
    skip - no WPA/RSN IE
    selected non-WPA AP 00:0d:ed:99:37:c0 ssid='uoa'
Trying to associate with 00:0d:ed:99:37:c0 (SSID='uoa' freq=2437 MHz)
Cancelling scan request
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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 5c 6d 72 65 61 30 30 35                     EC\mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=25 id=3
EAP: EAP entering state GET_METHOD
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:0B07C065:x509 certificate
routines:X509_STORE_add_cert:cert already in hash table
SSL - SSL error: error:140CB07C:SSL routines:SSL_use_PrivateKey_file:bad
ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.
EAP: Failed to initialize EAP method 25
EAP: EAP entering state METHOD
EAP::METHOD - method not selected
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: txSuppRsp - EAP response data not available
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
Authentication with 00:0d:ed:99:37:c0 timed out.
Setting scan request: 0 sec 0 usec
****************************************

Jouni Malinen wrote:
> On Tue, Sep 07, 2004 at 10:25:30PM +1200, Morgan Read wrote:
> 
> 
>>Well that was much more exciting!  At least to my eyes...
>>
>>I ran as you suggested per the hostap driver (not wext).
> 
> 
> Yes, indeed, this time the EAPOL negotiation was at least started.
> However, the AP/authentication server did not seem to like the identity
> response from the client.
> 
> 
>>EAP: Received EAP-Request method=1 id=2
>>EAP: EAP entering state IDENTITY
>>EAP: EAP-Request Identity data - hexdump_ascii(len=0):
>>EAP: using real identity - hexdump_ascii(len=10):
>>     45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
> 
> 
> Are you sure that is the current username? If "EC" is the domain part,
> that should most likely be EC\mrea005, not EC/mrea005.. 
> 
> 
>>Wireless event: cmd=0x8b15 len=20
>>Wireless event: new AP: 00:00:00:00:00:00
>>Setting scan request: 0 sec 100000 usec
>>EAPOL: External notification - portEnabled=0
>>EAPOL: SUPP_PAE entering state DISCONNECTED
> 
> 
> It looks like the AP disassociated the stations. This could have
> happened, e.g., because the authentication server rejected access to
> EC/mrea005 identity.
> 

-- 
Morgan Read
<mailto:mstuffATplDOTnet>






From mstuff  Fri Sep 17 01:43:57 2004
From: mstuff (Morgan Read)
Date: Fri, 17 Sep 2004 20:43:57 +1200
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <20040916041924.GG7360@jm.kir.nu>
References: <413D11D0.8050203@pl.net>
	<20040907025300.GB7392@jm.kir.nu>	<413D8C9A.9030707@pl.net>
	<20040916041924.GG7360@jm.kir.nu>
Message-ID: <414AA3CD.6040801@pl.net>

Hi Jouni
Progress!

With that little correction I now seem to be getting though the first
phase of the process?!:-)  (See debug below).

But, I'm getting stuck with my private key?  I've included what
seemed to be one cycle of the debug below, plus a couple of extra
error examples which are a little different (first).

Here's the command I used to generate the private key; the instructions 
I followed are from a v basic howto for xsupplicant at my uni:
<http://www.ece.auckland.ac.nz/%7Etcol036/wireless/wireless.html> -

"openssl genrsa -out client.key 1024"

All help very much appreciated!
Regards,
Morgan.

****************************************
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:140CB07C:SSL
routines:SSL_use_PrivateKey_file:bad ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.

###################################

EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:0B07C065:x509 certificate
routines:X509_STORE_add_cert:cert already in hash table
SSL - SSL error: error:140CB07C:SSL routines:SSL_use_PrivateKey_file:bad
ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.

####################################

Setting scan request: 0 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=3):
      75 6f 61                                          uoa
Wireless event: cmd=0x8b19 len=12
Received 158 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:ed:99:37:c0 ssid='uoa' wpa_ie_len=0 rsn_ie_len=0
    skip - no WPA/RSN IE
    selected non-WPA AP 00:0d:ed:99:37:c0 ssid='uoa'
Trying to associate with 00:0d:ed:99:37:c0 (SSID='uoa' freq=2437 MHz)
Cancelling scan request
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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 5c 6d 72 65 61 30 30 35                     EC\mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=25 id=3
EAP: EAP entering state GET_METHOD
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:0B07C065:x509 certificate
routines:X509_STORE_add_cert:cert already in hash table
SSL - SSL error: error:140CB07C:SSL routines:SSL_use_PrivateKey_file:bad
ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.
EAP: Failed to initialize EAP method 25
EAP: EAP entering state METHOD
EAP::METHOD - method not selected
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: txSuppRsp - EAP response data not available
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
Authentication with 00:0d:ed:99:37:c0 timed out.
Setting scan request: 0 sec 0 usec
****************************************

Jouni Malinen wrote:
> On Tue, Sep 07, 2004 at 10:25:30PM +1200, Morgan Read wrote:
> 
> 
>>Well that was much more exciting!  At least to my eyes...
>>
>>I ran as you suggested per the hostap driver (not wext).
> 
> 
> Yes, indeed, this time the EAPOL negotiation was at least started.
> However, the AP/authentication server did not seem to like the identity
> response from the client.
> 
> 
>>EAP: Received EAP-Request method=1 id=2
>>EAP: EAP entering state IDENTITY
>>EAP: EAP-Request Identity data - hexdump_ascii(len=0):
>>EAP: using real identity - hexdump_ascii(len=10):
>>     45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
> 
> 
> Are you sure that is the current username? If "EC" is the domain part,
> that should most likely be EC\mrea005, not EC/mrea005.. 
> 
> 
>>Wireless event: cmd=0x8b15 len=20
>>Wireless event: new AP: 00:00:00:00:00:00
>>Setting scan request: 0 sec 100000 usec
>>EAPOL: External notification - portEnabled=0
>>EAPOL: SUPP_PAE entering state DISCONNECTED
> 
> 
> It looks like the AP disassociated the stations. This could have
> happened, e.g., because the authentication server rejected access to
> EC/mrea005 identity.
> 

-- 
Morgan Read
<mailto:mstuffATplDOTnet>






From kyle  Fri Sep 17 07:15:16 2004
From: kyle (Kyle McMartin)
Date: Fri, 17 Sep 2004 10:15:16 -0400
Subject: Interesting issues with CCMP
In-Reply-To: <20040917023625.GB7354@jm.kir.nu>
References: <20040916140413.GD2973@roadwarrior.mcmartin.ca>
	<20040917023625.GB7354@jm.kir.nu>
Message-ID: <20040917141516.GG4254@roadwarrior.mcmartin.ca>

On Thu, Sep 16, 2004 at 07:36:25PM -0700, Jouni Malinen wrote:
> What kind of device do you use as the AP?
>
It is a Linksys WAP54g.

Regards,
	Kyle.



From mstuff  Fri Sep 17 22:44:13 2004
From: mstuff (Morgan Read)
Date: Sat, 18 Sep 2004 17:44:13 +1200
Subject: No primary upgrade?
In-Reply-To: <4137324F.6060006@pl.net>
References: <4137324F.6060006@pl.net>
Message-ID: <414BCB2D.3070104@pl.net>

Resolved by:
<http://sisyphus.iocaine.com/pipermail/hostap/2004-September/007990.html>.

Morgan Read wrote:
> Hi list (agian:)
> Any ideas why primary firmware might not be upgrading as indicated below?
> Regards,
> Morgan.
> ***************************
> [root at morgansmachine root]# prism2_srec -r wlan0 
> /home/morgan/Desktop/AlliedTelesyn_WiFi_Card/firmware-1.7.4/mycardPri+SecRAM/ak010104.hex 
> /home/morgan/Desktop/AlliedTelesyn_WiFi_Card/firmware-1.7.4/mycardPri+SecRAM/rf010704.hex 
> 
> srec summary for ak010104.hex
> Included file name: AK010104.HEX
> Component: 0x0015 1.1.4 (primary firmware)
> 
> srec summary for rf010704.hex
> Included file name: RF010704.HEX
> Component: 0x001f 1.7.4 (station firmware)
> 
> 
> Verifying update compatibility and combining data:
> PRI: old iface 1:4-4 new iface 4:4-5
> Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
> OK.
> 
> Downloading to volatile memory (RAM).
> OK.
> Components after download:
>   NICID: 0x801b v1.0.0
>   PRIID: 0x0015 v1.1.0
>   STAID: 0x001f v1.7.4
> [root at morgansmachine root]# hostap_diag wlan0
> Host AP driver diagnostics information for 'wlan0'
> 
> NICID: id=0x801b v1.0.0 (PRISM III PCMCIA (SST parallel flash))
> PRIID: id=0x0015 v1.1.0
> STAID: id=0x001f v1.7.4 (station firmware)
> You have new mail in /var/spool/mail/root
> [root at morgansmachine root]#
> ***************************

-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From jankovic  Sun Sep 19 05:12:21 2004
From: jankovic (Stefan Jankovic)
Date: Sun, 19 Sep 2004 14:12:21 +0200
Subject: Packet bursting/compression on wireless links...
Message-ID: <200409191222.i8JCMGml096675@dateon.sk>

Hello list,

I've been testing the performance of my Prism 2.5 cards using Netperf.
I've got throughput of 5-6 Mbps with large (cca 1500) UDP packets, but only
under 1 Mbps with small ones (100).

My explanation was that it's due to approximately constant network overhead
independent of packet size.

1. Is it correct ?
2. Does hostap support or does anybody know some software, that would pack
the stream of small packets to a big one and unpack it on other side. Some
additional compression would also be nice :-)
I think, this procedure is in 108Mbits Turbo-mode known as packet bursting.

Thanks.

Stefan Jankovic.





From jkmaline  Sun Sep 19 09:26:04 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 19 Sep 2004 09:26:04 -0700
Subject: hostapd with wpa dont work on big endian systems
In-Reply-To: <20040916034613.GC7360@jm.kir.nu>
References: <20040909105507.GO28682@informatik.uni-rostock.de>
	<20040916034613.GC7360@jm.kir.nu>
Message-ID: <20040919162604.GB7354@jm.kir.nu>

On Wed, Sep 15, 2004 at 08:46:14PM -0700, Jouni Malinen wrote:
> On Thu, Sep 09, 2004 at 12:55:07PM +0200, Gunter Burchardt wrote:
> 
> > I tested hostap with wpa on a big endian system (IXP425). I think there
> > is a problem in MIC calculation. Here a log of hostapd. I will try to
> > find the problem.
> 
> I cannot reproduce this on my big endian test setup (MPC8260-based,
> i.e., PowerPC 603e), so I do not think this is an endianness issue. I
> was able to use x86 wpa_supplicant with both WPA-PSK and WPA-EAP when
> hostapd was running on this big-endian board. ARM has other differences
> that may have been missed somewhere.

I could not reproduce this on big-endian IXP425 either.. Both WPA-PSK
and WPA-EAP worked fine and so did TKIP and CCMP. I would need to get
quite a bit more details to try to figure this out (board specifics,
/proc/cpuinfo, kernel version, kernel config, Prism2/2.5/3 details,
hostapd configuration and full debug log).

-- 
Jouni Malinen                                            PGP id EFC895FA



From togg  Sun Sep 19 11:48:16 2004
From: togg (Togg)
Date: Sun, 19 Sep 2004 20:48:16 +0200
Subject: AW: hostapd with wpa dont work on big endian systems
In-Reply-To: <20040919162604.GB7354@jm.kir.nu>
Message-ID: <E1C96jT-0007sc-00@mrelayng.kundenserver.de>

Thanks! I will investigate further in this problem and get all required
informations.

Regards,
Togg

-----Urspr?ngliche Nachricht-----
Von: hostap-bounces+togg=togg.de at shmoo.com
[mailto:hostap-bounces+togg=togg.de at shmoo.com] Im Auftrag von Jouni Malinen
Gesendet: Sonntag, 19. September 2004 18:26
An: hostap at shmoo.com
Betreff: Re: hostapd with wpa dont work on big endian systems

On Wed, Sep 15, 2004 at 08:46:14PM -0700, Jouni Malinen wrote:
> On Thu, Sep 09, 2004 at 12:55:07PM +0200, Gunter Burchardt wrote:
> 
> > I tested hostap with wpa on a big endian system (IXP425). I think there
> > is a problem in MIC calculation. Here a log of hostapd. I will try to
> > find the problem.
> 
> I cannot reproduce this on my big endian test setup (MPC8260-based,
> i.e., PowerPC 603e), so I do not think this is an endianness issue. I
> was able to use x86 wpa_supplicant with both WPA-PSK and WPA-EAP when
> hostapd was running on this big-endian board. ARM has other differences
> that may have been missed somewhere.

I could not reproduce this on big-endian IXP425 either.. Both WPA-PSK
and WPA-EAP worked fine and so did TKIP and CCMP. I would need to get
quite a bit more details to try to figure this out (board specifics,
/proc/cpuinfo, kernel version, kernel config, Prism2/2.5/3 details,
hostapd configuration and full debug log).

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




From gdamjan  Sun Sep 19 21:07:58 2004
From: gdamjan (Damjan)
Date: Mon, 20 Sep 2004 06:07:58 +0200
Subject: Prism 2.5 card problems / card locks or something
Message-ID: <20040920040758.GA1373@legolas.on.net.mk>

I have a problem with my Prism-2.5 based PCMCIA card.
Card details:
Prism-2.5 chip 200mw
Product No. : SL-2511CD PLUS EXT2 (E200)
PRI firmware 1.1.1
STA firmware 1.8.0 
(it was PRI 1.1.0 and STA 1.4.9 but I upgraded it)

I've downloaded and installed the latest hostap driver (0.2.4).

The problem is that several minutes after I enable the card (after
ifconfig up) the card seems to power off, or something like that. The
LED on it goes off (when it works for some 3-10 minutes the LED is on
constantly).

I'm attaching two parts of dmesg output, one is when I insert the card
and everythin is fine, the other is when the card dies (this is
truncated because there are a lot of errors before I eject the card).

I've tried both kernels 2.6.8.1 and 2.4.26, same thing happens.
The same thing happened with the other firmware too.

Do I need to use 1.7.4 firmware? (since i'm seeing most people use that)

A similar problem happens with the orinoco_cs driver too, after some
time working, the card seems to use all of the CPU. The computer is
unusable (literally) until I eject the card.

Has anyone had similar experience??

I've not ruled out that it might be some laptop related problem, but I
have a PCMCIA modem that works great for long times (I've never had any
problems with it).



-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!
-------------- next part --------------
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.2.4 - 2004-07-17 (Jouni Malinen <jkmaline at cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 5, io 0x0180-0x01bf
prism2_hw_init: initialized in 200 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.0
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
hostap_crypt: registered algorithm 'WEP'
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
   A1=00:00:00:00:00:00 A2=00:02:6f:03:9f:f1 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:02:6f:33:b0:34
-------------- next part --------------
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: could not find matching txfid (0xffff, new read 0xffff) for alloc event
TXFIDs: 0134[ffff] 0149[ffff] 015e[ffff] 0173[ffff] 0188[ffff] 019d[ffff] 01b2[ffff] 01c7[ffff]
wifi0: hfa384x_setup_bap - timeout before
wifi0: prism2_tx_80211 - to BAP0 failed
hostap_cs: CS_EVENT_CARD_REMOVAL
wifi0: card already removed or not configured during shutdown
wifi0: Interrupt, but dev not OK
wifi0: scheduled card reset
hostap_cs: wifi0: resetting card
wifi0: card already removed or not configured during shutdown
wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
hostap_cs: first command failed - assuming card does not have primary firmware
wifi0: init command completed too quickly - retrying
wifi0: __hfa384x_cmd_no_wait(6) - timeout - reg=0xffff
hostap_cs: first command failed - assuming card does not have primary firmware
prism2_hw_init: initialized in 0 ms
wifi0: prism2_enable_aux_port - timeout - reg=0xffff
wifi0: prism2_enable_aux_port - timeout - reg=0xffff
wifi0: valid PDA not found
SWSUPPORT0 write/read failed: FFFF != 8A32
hostap_cs: Initialization failed
prism2_tx_timeout: wake up queue
wifi0: prism2_tx_80211: hw not ready - skipping
wifi0: card already removed or not configured during shutdown
hostap_cs: Driver unloaded


From Actinium  Sun Sep 19 21:30:21 2004
From: Actinium (Actinium at iocaine.com)
Date: Mon, 20 Sep 2004 12:30:21 +0800
Subject: Problem with WPA-PSK
Message-ID: <414E5CDD.309@actinium.org>

I wonder who can help me with this problem. I was setting up a WPA-PSK 
connection. my config for
wpa_supplicant are as follow:
network={
        ssid="test"
        scan_ssid=1
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=CCMP
        psk=1234567890123456789012345678901234567890123456789012345678901234
        priority=2
}

my config for hostapd are as follow:
ssid=test
auth_algs=3
wpa=1
wpa_psk=1234567890123456789012345678901234567890123456789012345678901234
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_group_rekey=600
wpa_gmk_rekey=86400

debug message from wpa_supplicant as follow:
# ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
ap_scan=1
Line: 186 - start of a new network block
SSID - hexdump_ascii(len=4):
     74 65 73 74                                       test
proto: 0x1
key_mgmt: 0x2
pairwise: 0x10
group: 0x10
PSK - hexdump(len=32): 12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 12 
34 56 78
90 12 34 56 78 90 12 34 56 78 90 12 34
priority=2
Priority group 2
   id=0 ssid='test'
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
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
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=4):
     74 65 73 74                                       test
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
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
Wireless event: cmd=0x8b19 len=12
Received 234 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 2
0: 00:60:b3:8b:ea:0b ssid='test' wpa_ie_len=28 rsn_ie_len=0
   selected
Trying to associate with 00:60:b3:8b:ea:0b (SSID='test' freq=2412 MHz)
Cancelling scan request
WPA: using IEEE 802.11i/D3.0
WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 
01 00 00
50 f2 04 01 00 00 50 f2 02
wpa_driver_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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
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
Wireless event: cmd=0x8b1a len=16
RX EAPOL from 00:60:b3:8b:ea:0b
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 
00 01 a8 5e dd 78 9e 8a fb 49 7e cc 55 9b 1f 37 53 e5 c8 79 bf 47 8f 03 
ab d8 9a 02 ba
79 19 16 21 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
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
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:60:b3:8b:ea:0b
Association event - clear replay counter
Associated to a new BSS: BSSID=00:60:b3:8b:ea:0b
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
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:60:b3:8b:ea:0b
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 
00 02 a8 5e dd 78 9e 8a fb 49 7e cc 55 9b 1f 37 53 e5 c8 79 bf 47 8f 03 
ab d8 9a 02 ba
79 19 16 21 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 
00 00 00 00 02 a8 5e dd 78 9e 8a fb 49 7e cc 55 9b 1f 37 53 e5 c8 79 bf 
47 8f 03 ab d8
9a 02 ba 79 19 16 21 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00
WPA: RX message 1 of 4-Way Handshake from 00:60:b3:8b:ea:0b (ver=2)
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 
f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
WPA: Renewed SNonce - hexdump(len=32): 77 6c 61 6e 30 20 20 20 20 20 4c 
69 6e 6b 20 65 6e 63 61 70 3a 45 74 68 65 72 6e 65 74 20 20 48
WPA: PMK - hexdump(len=32): 12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 
12 34 56 78 90 12 34 56 78 90 12 34 56 78 90 12 34
WPA: PTK - hexdump(len=64): 49 36 2b 87 b7 6f 6f ed c8 e8 da 73 18 4a 7b 
87 d3 bc ea f0 e9 1f 64 4e 05 27 58 55 38 32 e3 d7 47 f4 4c b6 ed 63 56 
d6 e2 3e 16 b6
a4 e3 f1 b3 e0 3f de 53 4e f7 ff 9d 06 a4 c1 ac 29 98 d1 cf
WPA: EAPOL-Key MIC - hexdump(len=16): bb fa c6 08 81 1b 81 6f b9 65 99 
bd 29 2c
f5 e3
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key 2/4 - hexdump(len=137): 00 60 b3 8b ea 0b 00 0c 84 01 
23 60 88 8e 01 03 00 77 fe 01 0a 00 10 00 00 00 00 00 00 00 02 77 6c 61 
6e 30 20 20 20 20 20 4c 69 6e 6b 20 65 6e 63 61 70 3a 45 74 68 65 72 6e 
65 74 20 20 48 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 bb fa c6 08 81 1b 81 6f b9 65 99 bd 29 2c f5 e3 00 18 dd 
16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
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
RX EAPOL from 00:60:b3:8b:ea:0b
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 
00 03 a8 5e dd 78 9e 8a fb 49 7e cc 55 9b 1f 37 53 e5 c8 79 bf 47 8f 03 
ab d8 9a 02 ba
79 19 16 21 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00
EAPOL frame received in disassociated state - dropped
Starting AP scan (broadcast SSID)
RX EAPOL from 00:60:b3:8b:ea:0b
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 
00 04 a8 5e dd 78 9e 8a fb 49 7e cc 55 9b 1f 37 53 e5 c8 79 bf 47 8f 03 
ab d8 9a 02 ba
79 19 16 21 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00
EAPOL frame received in disassociated state - dropped


    Thank you for the helps...
Regards,
Lim Yew Chai




From gbur  Mon Sep 20 01:53:17 2004
From: gbur (Gunter Burchardt)
Date: Mon, 20 Sep 2004 10:53:17 +0200
Subject: wired authentication (kernel module)
Message-ID: <20040920085317.GC9381@informatik.uni-rostock.de>

Hello,

Kernel module for 1x authentication works now. hostapd is patched and
works together with kernel module. I have to do some more tests now!

Jouni, it is possible/desired to include this kernel module into hostap
project?

regards
gunter



From Actinium  Mon Sep 20 03:10:08 2004
From: Actinium (Actinium at iocaine.com)
Date: Mon, 20 Sep 2004 18:10:08 +0800
Subject: Problem with WPA-PSK 
In-Reply-To: <20040920043203.3AC3E50C@mail.iocaine.com>
References: <20040920043203.3AC3E50C@mail.iocaine.com>
Message-ID: <414EAC80.4070208@actinium.org>

More information on the hostapd with regarding to authentication problem;

Configuration file: hostapd.conf
Opening raw packet socket for ifindex 25
Using interface wlan0ap with hwaddr 00:60:b3:8b:ea:0b and ssid 'test'
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): ef b8 32 a7 54 19 3d ae 61 1c ae e8 9e 3f d8 df 
d3 d7 a9
94 b9 2f 7a 99 36 2b 98 22 40 8b 23 0d
GTK - hexdump(len=32): 80 51 eb ce ef 60 ce c3 05 a2 3b bf 2d 8b fc 86 
e1 7f f1
d4 c0 cb 42 86 e5 b9 ea 60 7c db d4 f3
WPA: group state machine entering state SETKEYSDONE
Flushing old station entries
Deauthenticate all stations
mgmt::auth
authentication: STA=00:0c:84:01:23:60 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:0c:84:01:23:60 auth_alg=0 
auth_transaction=2 resp=0MGMT (TX callback) ACK
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:0c:84:01:23:60 capab_info=0x11 
listen_interval=10
  new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITIALIZE
WPA: 00:0c:84:01:23:60 WPA_PTK_GROUP entering state IDLE
WPA: 00:0c:84:01:23:60 WPA_PTK entering state AUTHENTICATION
WPA: 00:0c:84:01:23:60 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITPSK
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
WPA: 00:0c:84:01:23:60 WPA_PTK entering state DISCONNECT
WPA: 00:0c:84:01:23:60 WPA_PTK entering state DISCONNECTED
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITIALIZE
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not set station flags for kernel driver.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not set station flags for kernel driver.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not remove station from kernel driver.
DATA (TX callback) ACK
mgmt::auth
authentication: STA=00:0c:84:01:23:60 auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:0c:84:01:23:60 auth_alg=0 
auth_transaction=2 resp=0MGMT (TX callback) ACK
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:0c:84:01:23:60 capab_info=0x11 
listen_interval=10
  new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITIALIZE
WPA: 00:0c:84:01:23:60 WPA_PTK_GROUP entering state IDLE
WPA: 00:0c:84:01:23:60 WPA_PTK entering state AUTHENTICATION
WPA: 00:0c:84:01:23:60 WPA_PTK entering state AUTHENTICATION2
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITPSK
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:0c:84:01:23:60 TX status - version=1 type=3 length=95 - 
ack=1
WPA: 00:0c:84:01:23:60 WPA_PTK entering state PTKSTART
WPA: 00:0c:84:01:23:60 WPA_PTK entering state DISCONNECT
WPA: 00:0c:84:01:23:60 WPA_PTK entering state DISCONNECTED
WPA: 00:0c:84:01:23:60 WPA_PTK entering state INITIALIZE
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not set station flags for kernel driver.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not set station flags for kernel driver.
ioctl[PRISM2_IOCTL_HOSTAPD]: No such file or directory
Could not remove station from kernel driver.

Regards,
Lim Yew Chai




From mrcool  Mon Sep 20 04:39:57 2004
From: mrcool (Jerry)
Date: Mon, 20 Sep 2004 06:39:57 -0500
Subject: hostapd cannot connect to kernel driver.
Message-ID: <003b01c49f06$8e6f5e60$b900a8c0@Home>

CVS from 9/17/04, and kernel 2.4.21-144 (suse 9.0 stock), a pcmcia (hostap_cs) and a plx device (hostap_plx, and a atheros device as well).  wlan0 - Atheros, seems to work fine, wlan1 - pcmcia (200Mw Senaeo) AP w/1 client (<- my feed, use acl), seems to work fine, wlan2 - plx adapter w/normal power Zcomax clone (manfid 0xd601, 0x0005 not 200Mw <- my broadcast), works fine...

The problem is when i start hostapd on the wlan1 interface, I get "could not connect to kernel driver"  "hostapd : no private ioctl"  (<- or something quite similar to that, no ioctl, anyway).

At this point, i went ahead and got the last release (0.2.4) drivers/utils, and hostapd.  This seems to work ok.  

The firmware on the card in the plx adapter is rather old (1.3.9), but since i dont need WDS and otherwise it seems to work quite well, i havent bothered to update it.  Let me know if you wish any more info or want me to try something else.  I dont know if it is a problem, but i thought the developers should hear of this error (if it is one).

Good luck 

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040920/3244e82f/attachment.htm 


From gdamjan  Mon Sep 20 05:54:18 2004
From: gdamjan (Damjan)
Date: Mon, 20 Sep 2004 14:54:18 +0200
Subject: custom script after access accept
Message-ID: <20040920125418.GA2447@legolas.on.net.mk>

Is it possible to setup hostapd to execute a custom script after it
receives the Radius access reply, but before it authorizes the client?

I'd like to do several things in the script, enter MAC -> IP mapping in
the DHCP server config, according to the Framed-IP radius value.
set a fixed mac -> ip entry in ARP table (so user can't change ip
address).

Also I'm thinking about two types of users, fully authorized can do
anything, "Guest" users can only access two or three sites .


-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From gbur  Mon Sep 20 10:21:17 2004
From: gbur (Gunter Burchardt)
Date: Mon, 20 Sep 2004 19:21:17 +0200
Subject: custom script after access accept
In-Reply-To: <20040920125418.GA2447@legolas.on.net.mk>
References: <20040920125418.GA2447@legolas.on.net.mk>
Message-ID: <20040920172117.GF9381@informatik.uni-rostock.de>

> Is it possible to setup hostapd to execute a custom script after it
> receives the Radius access reply, but before it authorizes the client?

At the moment it is not possible to call a script at this point. But i
use a patch doing exatly this what you want. But befor i can submit it
i have to cleanup code. Access to all radius values in access-accept
packets will be possible! Script will be called on auth, reauth and
deauth. I will submit it to mailing list in about one week.

regards
gunter



From gdamjan  Mon Sep 20 13:13:28 2004
From: gdamjan (Damjan)
Date: Mon, 20 Sep 2004 22:13:28 +0200
Subject: Can I use 801.1x but also allow plain connections
Message-ID: <20040920201328.GA10392@legolas.on.net.mk>

If I use hostapd with all the 802.1x security (Radius, EAP,dynamic keys),
what happens to stations that don't even try to authenticate? 

For example users that haven't set up, or even don't have supplicant
software. Is it possible to allow them access too. Ofcourse in that case
I'd like to limit them (with iptables) only to an info page, allowing
them to download and setup the supplicant software.

Is this possible with hostapd?

-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From snai8255  Mon Sep 20 19:30:05 2004
From: snai8255 (snai8255 at mail.usyd.edu.au)
Date: Tue, 21 Sep 2004 12:30:05 +1000
Subject: deassociating STA
Message-ID: <1095733805.414f922d411d2@www-mail.usyd.edu.au>

hi guys;

i was wondering how do i force a STA to deassociate and deauthenticate with its current AP.i believe
it authenticates and associates on command "iwconfig wlan0 essid blah" (correct me if i am wrong).

regards
saji


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From gbur  Mon Sep 20 20:59:16 2004
From: gbur (Gunter Burchardt)
Date: Tue, 21 Sep 2004 05:59:16 +0200
Subject: Can I use 801.1x but also allow plain connections
In-Reply-To: <20040920201328.GA10392@legolas.on.net.mk>
References: <20040920201328.GA10392@legolas.on.net.mk>
Message-ID: <20040921035916.GG9381@informatik.uni-rostock.de>

> If I use hostapd with all the 802.1x security (Radius, EAP,dynamic keys),
> what happens to stations that don't even try to authenticate? 
> 
> For example users that haven't set up, or even don't have supplicant
> software. Is it possible to allow them access too. Ofcourse in that case
> I'd like to limit them (with iptables) only to an info page, allowing
> them to download and setup the supplicant software.
> 
> Is this possible with hostapd?

No. hostap has no net device for unauthorized stations.

regards
gunter



From jkmaline  Mon Sep 20 21:54:22 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 20 Sep 2004 21:54:22 -0700
Subject: Relicensing hostapd under dual GPL/BSD license
Message-ID: <20040921045422.GG7354@jm.kir.nu>

There has been some discussion on using hostapd with *BSD. One of the
question is on the used license. I'm looking into relicensing hostapd
under dual GPL/BSD license, i.e., adding BSD to the current license in
the same way as core code in wpa_supplicant is released. I'm willing to
do this for the code I have written and I have been going through my CVS
logs to get a list of contributions that are non-trivial (i.e., more
than couple of lines). I have already sent private email to most if not
all authors of these changes. I'll do another pass through the logs in
order to verify that I did not miss any contributions.

If you have contributed code to hostapd and I have not yet asked you
about relicensing, please help me speed up the process by sending an
email to jkmaline at cc.hut.fi and let me know if you are willing to
relicense the changes under dual GPL/BSD license, i.e., add BSD in
addition to GPL that was used as the sole license before. If you do not
want your changes licensed under BSD, please also let me know.

My current plan is to go through the code file by file and mark clear
cases dual licensed. Once all files are cleared, I'll change README etc.
to use the new license.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep 20 21:57:42 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 20 Sep 2004 21:57:42 -0700
Subject: wired authentication (kernel module)
In-Reply-To: <20040920085317.GC9381@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
Message-ID: <20040921045742.GH7354@jm.kir.nu>

On Mon, Sep 20, 2004 at 10:53:17AM +0200, Gunter Burchardt wrote:

> Kernel module for 1x authentication works now. hostapd is patched and
> works together with kernel module. I have to do some more tests now!

That's nice to hear.

> Jouni, it is possible/desired to include this kernel module into hostap
> project?

Yes, that sounds like a useful addition. I can add it to my CVS
repository and/or make it available in http://hostap.epitest.fi
release directory as a separate release.

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Mon Sep 20 23:34:42 2004
From: gbur (Gunter Burchardt)
Date: Tue, 21 Sep 2004 08:34:42 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040921045742.GH7354@jm.kir.nu>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
Message-ID: <20040921063442.GI9381@informatik.uni-rostock.de>

> > Jouni, it is possible/desired to include this kernel module into hostap
> > project?
> 
> Yes, that sounds like a useful addition. I can add it to my CVS
> repository and/or make it available in http://hostap.epitest.fi
> release directory as a separate release.

Ok - here is the directory. Makefile is very easy at the moment. My
make book will come in a couple of days. There is also a little test
programm. The patch for hostap i will send in next mail. 

regards
gunter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ieee802_1x.tar.gz
Type: application/x-tar-gz
Size: 16655 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20040921/18caaf2b/attachment.bin 


From gbur  Mon Sep 20 23:47:38 2004
From: gbur (Gunter Burchardt)
Date: Tue, 21 Sep 2004 08:47:38 +0200
Subject: [PATCH]: hostapd wired authenticator
Message-ID: <20040921064738.GA19728@informatik.uni-rostock.de>

Hello,

Here the patch to enable hostapd to work with kernel module i submitted
for some time.

Jouni, i had to include ioctrl specific stuff from a header file of the
kernel module (ieee802_1x_common.h). A aditional include path would be
fine if you found a location for the kernel module.

regards
gunter
-------------- next part --------------
diff -Nur hostap.old/hostapd/driver_wired.c hostap/hostapd/driver_wired.c
--- hostap.old/hostapd/driver_wired.c	2004-09-13 04:59:06.000000000 +0200
+++ hostap/hostapd/driver_wired.c	2004-09-21 08:39:33.000000000 +0200
@@ -21,10 +21,12 @@
 
 #ifdef USE_KERNEL_HEADERS
 #include <asm/types.h>
+#include <linux/if.h>
 #include <linux/if_packet.h>
 #include <linux/if_ether.h>   /* The L2 protocols */
 #include <linux/if_arp.h>
 #else /* USE_KERNEL_HEADERS */
+#include <net/if.h>
 #include <net/if_arp.h>
 #include <netpacket/packet.h>
 #endif /* USE_KERNEL_HEADERS */
@@ -35,6 +37,8 @@
 #include "eloop.h"
 #include "sta_info.h"
 
+#include "../ieee802_1x/modules/ieee802_1x_common.h"
+
 
 static int wired_send_eapol(void *priv, u8 *addr,
 			    u8 *data, size_t data_len, int encrypt)
@@ -73,6 +77,141 @@
 }
 
 
+static int drv_dev_ioctl(struct wired_driver_data *drv, 
+			 struct ieee802_1x_dev_param *param)
+{
+	struct ifreq req;
+
+	param->ifindex = drv->ifindex;
+	strcpy(req.ifr_name,IEEE802_1X_DEV_NAME);
+	req.ifr_data = (caddr_t)param;
+
+	if( ioctl(drv->sock, IEEE802_1X_DEV, &req ) < 0) {
+		printf("ioctl(IEEE802_1X_DEV)\n");
+		return -1;
+	}
+
+	return 0;
+}
+
+
+static int drv_sta_ioctl(struct wired_driver_data *drv,
+			 struct ieee802_1x_sta_param *param)
+{
+	struct ifreq req;
+
+	param->ifindex = drv->ifindex;
+	strcpy(req.ifr_name,IEEE802_1X_DEV_NAME);
+	req.ifr_data = (caddr_t)param;
+
+	if( ioctl(drv->sock, IEEE802_1X_STA, &req ) < 0) {
+		printf("ioctl(IEEE802_1X_STA)\n");
+		return -1;
+	}
+	return 0;
+}
+
+
+static int wired_flush(void *priv) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_dev_param param;
+
+	param.command = IEEE802_1X_DEV_FLUSH;
+
+	return drv_dev_ioctl(drv, &param);
+}
+
+
+static int wired_init_1x(void *priv) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_dev_param param;
+
+	param.command = IEEE802_1X_DEV_ADD;
+
+	return drv_dev_ioctl(drv, &param);
+}
+
+static int wired_deinit_1x(struct wired_driver_data *drv) {
+	struct ieee802_1x_dev_param param;
+
+	param.command = IEEE802_1X_DEV_DEL;
+
+	return drv_dev_ioctl(drv, &param); 
+}
+
+
+static int wired_add_sta(void *priv, u8 *addr, u16 aid, u16 capability,
+			 u8 tx_supp_rates) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_sta_param param;
+
+	param.command = IEEE802_1X_STA_ADD;
+	memcpy(param.sta_addr, addr, ETH_ALEN);
+	
+	return drv_sta_ioctl(drv, &param);
+}
+ 
+
+static void wired_remove_sta(void *priv, u8 *addr) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_sta_param param;
+
+	param.command = IEEE802_1X_STA_REMOVE;
+	memcpy(param.sta_addr, addr, ETH_ALEN);
+
+	drv_sta_ioctl(drv, &param);
+}
+
+
+static int wired_read_sta_data(void *priv, struct hostap_sta_driver_data *data,
+			       u8 *addr) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_sta_param param;
+
+	param.command = IEEE802_1X_STA_GET_INFO;
+	memcpy(param.sta_addr, addr, ETH_ALEN);
+
+	if (drv_sta_ioctl(drv, &param))
+		return -1;
+
+	data->rx_packets = param.u.get_info.rx_packets;
+	data->tx_packets = param.u.get_info.tx_packets;
+	data->rx_bytes = param.u.get_info.rx_bytes;
+	data->tx_bytes = param.u.get_info.tx_bytes;
+
+	return 0;
+}
+
+
+static int wired_get_inact_sec(void *priv, u8 *addr) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_sta_param param;
+
+	param.command = IEEE802_1X_STA_GET_INFO;
+	memcpy(param.sta_addr, addr, ETH_ALEN);
+
+	if (drv_sta_ioctl(drv, &param))
+		return -1;
+
+	return param.u.get_info.inactive_sec;
+}
+
+
+static void wired_set_sta_authorized(void *priv, u8 *addr, int authorized) {
+	struct wired_driver_data *drv = priv;
+	struct ieee802_1x_sta_param param;
+
+	if (authorized)
+		param.command = IEEE802_1X_STA_AUTHORIZE;
+	else
+		param.command = IEEE802_1X_STA_DEAUTHORIZE;
+
+	memcpy(param.sta_addr, addr, ETH_ALEN);
+
+	drv_sta_ioctl(drv, &param);
+}
+
+
 int wired_driver_init(struct hostapd_data *hapd)
 {
 	struct wired_driver_data *drv;
@@ -90,18 +229,18 @@
 		return -1;
 
 	/* register callback functions */
-	hapd->driver.set_sta_authorized = NULL;
+	hapd->driver.set_sta_authorized = wired_set_sta_authorized;
 	hapd->driver.send_eapol = wired_send_eapol;
 	hapd->driver.send_mgmt_frame = NULL;
-	hapd->driver.read_sta_data = NULL;
-	hapd->driver.remove_sta = NULL;
-	hapd->driver.add_sta = NULL;
-	hapd->driver.get_inact_sec = NULL;
+	hapd->driver.read_sta_data = wired_read_sta_data;
+	hapd->driver.remove_sta = wired_remove_sta;
+	hapd->driver.add_sta = wired_add_sta;
+	hapd->driver.get_inact_sec = wired_get_inact_sec;
 	hapd->driver.set_assoc_ap = NULL;
-	hapd->driver.init_1x = NULL;
+	hapd->driver.init_1x = wired_init_1x;
 	hapd->driver.set_privacy_invoked = NULL;
 	hapd->driver.set_encryption = NULL;
-	hapd->driver.flush = NULL;
+	hapd->driver.flush = wired_flush;
 
 	return 0;
 }
@@ -124,6 +263,8 @@
 	hapd->driver.set_encryption = NULL;
 	hapd->driver.flush = NULL;
 
+	wired_deinit_1x(drv);
+	
 	if (drv->sock >= 0)
 		close(drv->sock);
 	
diff -Nur hostap.old/hostapd/driver_wired.h hostap/hostapd/driver_wired.h
--- hostap.old/hostapd/driver_wired.h	2004-09-13 04:59:06.000000000 +0200
+++ hostap/hostapd/driver_wired.h	2004-09-17 14:21:52.000000000 +0200
@@ -4,8 +4,11 @@
 int wired_driver_init(struct hostapd_data *hapd);
 void wired_driver_deinit(struct hostapd_data *hapd);
 
+#define IEEE802_1X_DEV_NAME "ieee802_1x"
+
 struct wired_driver_data {
 	struct hostapd_data *hapd;
+	int ifindex; /* index of device stas can associate */
 
 	int sock; /* raw packet socket for driver access */
 	int dhcp_sock; /* socket for dhcp packets */
diff -Nur hostap.old/hostapd/hostapd.c hostap/hostapd/hostapd.c
--- hostap.old/hostapd/hostapd.c	2004-09-13 04:59:06.000000000 +0200
+++ hostap/hostapd/hostapd.c	2004-09-20 09:14:51.000000000 +0200
@@ -366,6 +366,16 @@
 
 static void hostapd_cleanup_driver_wired(struct hostapd_data *hapd)
 {
+	accounting_deinit(hapd);
+	ieee802_1x_deinit(hapd);
+	radius_client_deinit(hapd);
+
+	wired_driver_deinit(hapd);
+
+	hostapd_config_free(hapd->conf);
+	hapd->conf = NULL;
+	
+	free(hapd->config_fname);
 }
 
 
diff -Nur hostap.old/hostapd/receive_wired.c hostap/hostapd/receive_wired.c
--- hostap.old/hostapd/receive_wired.c	2004-09-13 05:28:30.000000000 +0200
+++ hostap/hostapd/receive_wired.c	2004-09-20 09:31:40.000000000 +0200
@@ -72,6 +72,12 @@
 		      MACSTR " - adding a new STA\n", MAC2STR(addr));
 	sta = ap_sta_add(hapd, addr);
 	if (sta) {
+		if (hapd->driver.add_sta &&
+		    hapd->driver.add_sta(hapd->driver.data, sta->addr,
+					 sta->aid, sta->capability,
+					 sta->tx_supp_rates)) {
+			printf("Could not add station to kernel driver.\n");
+		}
 		hostapd_new_assoc_sta(hapd, sta);
 	} else {
 		HOSTAPD_DEBUG(HOSTAPD_DEBUG_MINIMAL, "Failed to add STA entry "
@@ -195,6 +201,7 @@
 		return -1;
 	}
 
+	drv->ifindex = ifr.ifr_ifindex;
 	
 	memset(&addr, 0, sizeof(addr));
 	addr.sll_family = AF_PACKET;


From gdamjan  Tue Sep 21 00:01:34 2004
From: gdamjan (Damjan)
Date: Tue, 21 Sep 2004 09:01:34 +0200
Subject: Can I use 801.1x but also allow plain connections
In-Reply-To: <20040921035916.GG9381@informatik.uni-rostock.de>
References: <20040920201328.GA10392@legolas.on.net.mk>
	<20040921035916.GG9381@informatik.uni-rostock.de>
Message-ID: <20040921070134.GA13831@legolas.on.net.mk>

> > If I use hostapd with all the 802.1x security (Radius, EAP,dynamic keys),
> > what happens to stations that don't even try to authenticate? 
> > 
> > For example users that haven't set up, or even don't have supplicant
> > software. Is it possible to allow them access too. Ofcourse in that case
> > I'd like to limit them (with iptables) only to an info page, allowing
> > them to download and setup the supplicant software.
> > 
> > Is this possible with hostapd?
> 
> No. hostap has no net device for unauthorized stations.

Is this impossible to add, planed feature or it was never considered?


-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From terjesenl  Tue Sep 21 10:18:39 2004
From: terjesenl (Linda Terjesen)
Date: Tue, 21 Sep 2004 10:18:39 -0700 (PDT)
Subject: Intel(R)PRO/Wireless LAN 2100 3A Mini PCI Adapter
Message-ID: <20040921171839.17378.qmail@web52310.mail.yahoo.com>

hello.
i've seen a couple of messages related to the Intel(R)PRO/Wireless LAN 2100 3A Mini PCI Adapter.
however, i have not read any solution and wonder if anyone has one?

i also have a Dell laptop which has a Intel(R) PRO/Wireless LAN 2100 3A Mini PCI Adapter card in
it. I have secured my wireless network using wep encryption. When using my Dell laptop i am rarely
able to connect to the wireless network and the internet. when able to connect momentarily, i also
repeatedly loose connection.

if anyone has a solution please let me know. thanks!

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



From abonilla  Tue Sep 21 04:39:40 2004
From: abonilla (Alejandro Bonilla)
Date: Tue, 21 Sep 2004 05:39:40 -0600
Subject: Intel(R)PRO/Wireless LAN 2100 3A Mini PCI Adapter
In-Reply-To: <20040921171839.17378.qmail@web52310.mail.yahoo.com>
References: <20040921171839.17378.qmail@web52310.mail.yahoo.com>
Message-ID: <415012FC.8010901@linuxwireless.org>

Linda,

    Please join the ML at ipw2100.sf.net for this question.
Regarding your problem, make sure you have version 0.54 as it is the 
latest in the moment.

- Alex


Linda Terjesen wrote:

>hello.
>i've seen a couple of messages related to the Intel(R)PRO/Wireless LAN 2100 3A Mini PCI Adapter.
>however, i have not read any solution and wonder if anyone has one?
>
>i also have a Dell laptop which has a Intel(R) PRO/Wireless LAN 2100 3A Mini PCI Adapter card in
>it. I have secured my wireless network using wep encryption. When using my Dell laptop i am rarely
>able to connect to the wireless network and the internet. when able to connect momentarily, i also
>repeatedly loose connection.
>
>if anyone has a solution please let me know. thanks!
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around 
>http://mail.yahoo.com 
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>



From dermot  Tue Sep 21 10:49:56 2004
From: dermot (Dermot McGahon)
Date: Tue, 21 Sep 2004 18:49:56 +0100
Subject: Rebadged Senoa pcmcia cards with prism 3 chipset
In-Reply-To: <200409191222.i8JCMGml096675@dateon.sk>
References: <200409191222.i8JCMGml096675@dateon.sk>
Message-ID: <opseouhilf3ertue@mail.dspsrv.com>

Hi all,

We bought the wrong cards :(

We would have liked to have bought some 200mW Senoa PCMCIA cards.

The cards that we have are NL-2511CD PLUS EXT2 MERCURY. What I've found out
is that the NL means that they are rebadged. The EXT2 means that they have  
two
external antenna connectors.

The MERCURY means that they are based on the PRISM 3 chipset, which StarOS  
does
not have any support for. I saw a brief mention on a Seattle Wireless  
website
that support for these may be underway. Is this so?

Can anyone also confirm that these are 100mW cards and are basically not as
good as the PRISM 2.5 based cards? The vendor we were using Solwise.co.uk  
are
reporting poor availability for the 2.5 cards and that the wholesale  
prices from
Intelsil have doubled since the PRISM 3 based cards have become available.


Dermot.
--



From andreaf  Tue Sep 21 10:56:29 2004
From: andreaf (Andrea G. Forte)
Date: Tue, 21 Sep 2004 13:56:29 -0400 (EDT)
Subject: RX frames question.
Message-ID: <Pine.GSO.4.58.0409211354100.15549@flame.cs.columbia.edu>

Hi all,

Hope you can help me! I am trying to understand how hostAP filters the RX
packets when in STA mode. I know that is has to filter the dst.addr1
address with FromDS bit set to 1, but I could not find how it filters
them.

Thanks a lot for your help.
Andrea




From jkmaline  Tue Sep 21 20:22:35 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Sep 2004 20:22:35 -0700
Subject: [PATCH]: hostapd wired authenticator
In-Reply-To: <20040921064738.GA19728@informatik.uni-rostock.de>
References: <20040921064738.GA19728@informatik.uni-rostock.de>
Message-ID: <20040922032235.GC7355@jm.kir.nu>

On Tue, Sep 21, 2004 at 08:47:38AM +0200, Gunter Burchardt wrote:

> Here the patch to enable hostapd to work with kernel module i submitted
> for some time.

Thanks. Please note that the driver interface code in hostapd got a
rather large change with the merge of madwifi driver interface.
Consequently, this patch does not apply to the current CVS version.
Could you please take a look at the new version and rediff the changes
against it? One of the changes moved receive_wired.c into beginning of
driver_wired.c and got rid of driver_wired.h. In addition, registering
function pointers for handler functions changed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Tue Sep 21 20:42:57 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 21 Sep 2004 20:42:57 -0700
Subject: wired authentication (kernel module)
In-Reply-To: <20040921063442.GI9381@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040921063442.GI9381@informatik.uni-rostock.de>
Message-ID: <20040922034257.GD7355@jm.kir.nu>

On Tue, Sep 21, 2004 at 08:34:42AM +0200, Gunter Burchardt wrote:

> Ok - here is the directory. Makefile is very easy at the moment. My
> make book will come in a couple of days. There is also a little test
> programm. The patch for hostap i will send in next mail. 

Thanks. I did not yet go through all the files and did not commit this
to CVS yet. I have some quick comments/questions about this.

Should the code be renamed to something else, e.g., pae? If I understood
correctly, it implements one part of IEEE 802.1X, namely the port access
entity.

Any plans on making Linux 2.6.x version of this? Linux 2.4.x is getting
somewhat old for new development..

Kernel Makefile should be used instead of own Makefile when building
kernel modules (make -C (linux dir) SUBDIRS=.... modules).

Is the new netdevice really needed? Is that just for the ioctl handler?
New ioctls are not exactly in favor of Linux networking maintainers, so
something else (e.g., netlink) could be better option to make this more
acceptable.

I don't know whether I would like to see something like wlan0ap being
added for wired network (todo.lst). Filtering should work fine with one
interface and EAPOL packets could be allowed through always. They are
not supposed to be bridged or consumed by anything else than the
Authenticator code.

Can more than one Ethernet device be used at the same time? In most
cases, wired IEEE 802.1X is used in switch setups with large number of
ports (Ethernet interfaces in this case)..

Multicast should not be accepted in input direction from unauthorized
stations unless ethertype == EAPOL.

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Tue Sep 21 23:47:08 2004
From: gbur (Gunter Burchardt)
Date: Wed, 22 Sep 2004 08:47:08 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040922034257.GD7355@jm.kir.nu>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040921063442.GI9381@informatik.uni-rostock.de>
	<20040922034257.GD7355@jm.kir.nu>
Message-ID: <20040922064708.GC19728@informatik.uni-rostock.de>

> > Ok - here is the directory. Makefile is very easy at the moment. My
> > make book will come in a couple of days. There is also a little test
> > programm. The patch for hostap i will send in next mail.
>
> Should the code be renamed to something else, e.g., pae? If I understood
> correctly, it implements one part of IEEE 802.1X, namely the port access
> entity.

Ok!

> Any plans on making Linux 2.6.x version of this? Linux 2.4.x is getting
> somewhat old for new development..
>
> Kernel Makefile should be used instead of own Makefile when building
> kernel modules (make -C (linux dir) SUBDIRS=.... modules).

I will try it on linux 2.6 and include it into kernel makefile.

> Is the new netdevice really needed? Is that just for the ioctl handler?
> New ioctls are not exactly in favor of Linux networking maintainers, so
> something else (e.g., netlink) could be better option to make this more
> acceptable.
>
> I don't know whether I would like to see something like wlan0ap being
> added for wired network (todo.lst). Filtering should work fine with one
> interface and EAPOL packets could be allowed through always. They are
> not supposed to be bridged or consumed by anything else than the
> Authenticator code.

Well, I have no experience with netlink sockets. There is nearly no
dokumentation for netlink communication. Netlink sounds great for
kernel userspace communication but at the moment its impossible for me
to implement without dokumentation. The netdivice is only needed for
the ioctl (I thought would need it for some packet interaction). Im
searching for another device type (eg. misc).

> Can more than one Ethernet device be used at the same time? In most
> cases, wired IEEE 802.1X is used in switch setups with large number of
> ports (Ethernet interfaces in this case)..

Yes. Half of it is implemented quite now :). I plan to add vlan
support to seperate ports: A switch with vlan support can tag each
physical port with a vlan id and the filter only accepts it if the id
matches. But there are more basic things to do at the moment.

> Multicast should not be accepted in input direction from unauthorized
> stations unless ethertype == EAPOL.

Ok!



From dirk.gouders  Wed Sep 22 07:44:34 2004
From: dirk.gouders (Dirk Gouders)
Date: Wed, 22 Sep 2004 16:44:34 +0200
Subject: test
Message-ID: <200409221444.i8MEiY9O041231@musashi.et.bocholt.fh-gelsenkirchen.de>

test



From saads17  Wed Sep 22 08:56:15 2004
From: saads17 (Saad Shakshir)
Date: Wed, 22 Sep 2004 11:56:15 -0400
Subject: linksys wpc11 as an access point
Message-ID: <BAY1-F22nDzMm7C1kIj000b2012@hotmail.com>

Hi,

I'm trying to get my redhat linux 7.3 (kernel version 2.4.27) to work as an 
802.11b access point.  I have a linksys wpc11 (ver. 3) wireless card.  I 
recently recompiled the kernel and made sure the necessary wireless modules 
are installed.  I also installed the kernel pcmcia tree.  When I insert the 
card, it detects it and the hostap driver is loaded.  lsmod | grep hostap 
gives:

hostap_cs     48768     2
hostap          105608   0 [hostap_cs]

Right now the Power LED is on constantly and the Link LED blinks constantly 
at about 2 times per second.  Here are the contents of my 
/etc/sysconfig/network-scripts/ifcfg-wlan0:

DEVICE=wlan0
BOOTPROTO=static
ADDRESS=192.168.10.1
NETMASK=255.255.255.0
BROADCAST=192.168.10.255
ONBOOT=yes
MODE=Master
ESSID=linuxAP
CHANNEL=11
RATE=AUTO

Here is the output of iwconfig wlan0:

wlan0     IEEE 802.11b  ESSID:"linuxAP"  Nickname:"rashmi"
         Mode:Master  Frequency:2.462GHz  Access Point: 00:06:25:2A:6D:B0
         Bit Rate:11Mb/s   Sensitivity=1/0
         Retry min limit:8   RTS thr:off   Fragment thr:off
         Encryption key:off
         Power Management:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:82  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:12749   Missed beacon:0

And here is the output of ifconfig wlan0:

wlan0     Link encap:Ethernet  HWaddr 00:06:25:2A:6D:B0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
         Interrupt:5 Base address:0x100


One thing I noticed is that the IP address isn't being set, even though i 
have it setup in the ifcfg-wlan0 file.  I also have an 
/etc/pcmcia/wireless.opts file (but I don't know if this gets called).  Here 
are the relevant contents:

case "$ADDRESS" in

# Configuration for linksys wpc11 card to be an access point
ap,0,*,00:06:25:*)
INFO="Linux Laptop with Linksys WPC11"
ESSID="linuxAP"
MODE="Master"
RATE="Auto"
IPADDR="192.168.10.1"
NETMASK="255.255.255.0"
BROADCAST="192.168.10.255"
;;

I cannot connect to the access point from my other linux laptop using a 
lucent orinoco card.  I know that the configuration on the client laptop is 
fine because I have tried to connect to access points elsewhere and it works 
fine.  I set the ESSID on the client laptop to be "linuxAP" but it doesn't 
detect the access point.  Also the constantly flashing LED makes me more 
certain that the problem is with the access point and not with the client.

Any help would be appreciated.

Regards,
Saad





From ged  Wed Sep 22 11:50:47 2004
From: ged (Ged Haywood)
Date: Wed, 22 Sep 2004 19:50:47 +0100 (BST)
Subject: Rebadged Senoa pcmcia cards with prism 3 chipset
In-Reply-To: <20040922144512.A801B3D5B@mail.iocaine.com>
References: <20040922144512.A801B3D5B@mail.iocaine.com>
Message-ID: <Pine.LNX.4.58.0409221928040.19412@mail3.jubileegroup.co.uk>

Hi there,

On Wed, 22 Sep 2004 Dermot McGahon wrote:

> We bought the wrong cards :(

:(

> The MERCURY means that they are based on the PRISM 3 chipset, which
> StarOS does not have any support for. I saw a brief mention on a
> Seattle Wireless website that support for these may be underway. Is
> this so?

I don't know understand, StarOS appears to be based on Linux, and
Prism 3 is supported by HostAP

http://hostap.epitest.fi/

so I should have thought it possible to use Prism3 with StarOS, but I
know nothing about StarOS.  If not then there's Linux, if you have or
can find the skills to put the system together.  The skills are easy
to find I think, but time-consuming to learn.  I don't know what StarOS
might offer you that a Linux distribution wouldn't, out of the box.

> Can anyone also confirm that these are 100mW cards and are basically
> not as good as the PRISM 2.5 based cards?

I can't comment on that, I don't know the cards you have and I don't
know how you'd compare them to decide which was better than which.

> The vendor we were using Solwise.co.uk are reporting poor
> availability for the 2.5 cards and that the wholesale prices from
> Intelsil have doubled since the PRISM 3 based cards have become
> available.

After my experiences with that company, I would treat what Solwise
tell me with great caution.  However it is true that the availability
of Prism cards has been patchy.  We have a few of the Prism-based
MA311 PCI cards in stock which we could supply.  We keep them as a
hedge against times of bad supply, because we use them ourselves and
are very happy with them.  We are based in England.  Having said that,
I don't think you need new cards, probably just the right software.

73,
Ged.



From gdamjan  Wed Sep 22 15:13:37 2004
From: gdamjan (Damjan)
Date: Thu, 23 Sep 2004 00:13:37 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040921045742.GH7354@jm.kir.nu>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
Message-ID: <20040922221337.GA12132@legolas.on.net.mk>

> > Kernel module for 1x authentication works now. hostapd is patched and
> > works together with kernel module. I have to do some more tests now!
> 
> That's nice to hear.

Sorry if I'm missing something very obvious, but what does a kernel
module for 802.1x do that a user-space daemon and other functionality
already in the kernel can't do?

Isn't it possible to make a user-space daemon that
1. puts a rule in Linux's ebtables to DROP all non-EAPOL frames
2. Waits for EAPOL frames and does what needs to be done with them




-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From jkmaline  Wed Sep 22 19:25:15 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Sep 2004 19:25:15 -0700
Subject: wired authentication (kernel module)
In-Reply-To: <20040922221337.GA12132@legolas.on.net.mk>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
Message-ID: <20040923022515.GA7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 12:13:37AM +0200, Damjan wrote:

> Sorry if I'm missing something very obvious, but what does a kernel
> module for 802.1x do that a user-space daemon and other functionality
> already in the kernel can't do?

Nothing?

> Isn't it possible to make a user-space daemon that
> 1. puts a rule in Linux's ebtables to DROP all non-EAPOL frames
> 2. Waits for EAPOL frames and does what needs to be done with them

That is something that I would really like to see being done. I have a
bit limited experience in using ebtables, but if it can be configured to
send packets to user space processing, it should have more or less
everything that is needed. Actually, even this would not be needed. It
should be enough to have a "watcher" module that reports dropped
packets (mainly, the src L2 address from them). ebtables has log target,
so either that or something similar could be used.

All packets should be sent to user space by default and rules to allow
packets to pass would be added based on successfully completed
authentication. Statistics from the rules could be used to implement
timing out peers.

More detailed design (e.g., ebtables commands, plans on user space
queue handler) and/or patch to hostapd would be welcome..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 22 20:57:59 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Sep 2004 20:57:59 -0700
Subject: Preparations for 0.2.5 release
Message-ID: <20040923035759.GB7360@jm.kir.nu>

I'm hoping to make a new release from the stable 0.2.x branch shortly.
This is a bug fix -only version with number of fixes backported from the
development branch. I just made 0.2.5-pre1 version available for
testing. Please let me know if you notice any issues with this or think
that there are some issues with the code that should be fixed before
0.2.5 release.

The pre-release versions are available from following URLs:

http://hostap.epitest.fi/releases/testing/hostap-driver-0.2.5-pre1.tar.gz
http://hostap.epitest.fi/releases/testing/hostapd-0.2.5-pre1.tar.gz
http://hostap.epitest.fi/releases/testing/wpa_supplicant-0.2.5-pre1.tar.gz

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Wed Sep 22 21:04:39 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 06:04:39 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040922221337.GA12132@legolas.on.net.mk>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
Message-ID: <20040923040439.GA9858@informatik.uni-rostock.de>

> Sorry if I'm missing something very obvious, but what does a kernel
> module for 802.1x do that a user-space daemon and other functionality
> already in the kernel can't do?
> 
> Isn't it possible to make a user-space daemon that
> 1. puts a rule in Linux's ebtables to DROP all non-EAPOL frames
> 2. Waits for EAPOL frames and does what needs to be done with them

ebtables cant do it! if you look through you ebtables kernel code you
will see that all forwarding/prerouting/postroutung hooks only works
with briges. Input and output hook is only for local processes. If
you're using an routed environment without briges ebtables didn't see
any forwarded packets.

To accept eapol frames for local process is not the problem. But to
allow mac based forwards without briges didn't work with ebtables!

regards
gunter  



From kleinveld  Wed Sep 22 21:07:49 2004
From: kleinveld (Arnaud)
Date: Thu, 23 Sep 2004 12:07:49 +0800
Subject: wired authentication (kernel module)
In-Reply-To: <20040923040439.GA9858@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>	<20040921045742.GH7354@jm.kir.nu>	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
Message-ID: <41524C15.3050900@pacific.net.sg>

Hi Gunter,

Isn't iptables the answer?

Regards,
Arnaud

Gunter Burchardt wrote:
>>Sorry if I'm missing something very obvious, but what does a kernel
>>module for 802.1x do that a user-space daemon and other functionality
>>already in the kernel can't do?
>>
>>Isn't it possible to make a user-space daemon that
>>1. puts a rule in Linux's ebtables to DROP all non-EAPOL frames
>>2. Waits for EAPOL frames and does what needs to be done with them
> 
> 
> ebtables cant do it! if you look through you ebtables kernel code you
> will see that all forwarding/prerouting/postroutung hooks only works
> with briges. Input and output hook is only for local processes. If
> you're using an routed environment without briges ebtables didn't see
> any forwarded packets.
> 
> To accept eapol frames for local process is not the problem. But to
> allow mac based forwards without briges didn't work with ebtables!
> 
> regards
> gunter  
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 



From jkmaline  Wed Sep 22 21:08:20 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Sep 2004 21:08:20 -0700
Subject: wired authentication (kernel module)
In-Reply-To: <20040923040439.GA9858@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
Message-ID: <20040923040820.GC7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 06:04:39AM +0200, Gunter Burchardt wrote:

> ebtables cant do it! if you look through you ebtables kernel code you
> will see that all forwarding/prerouting/postroutung hooks only works
> with briges. Input and output hook is only for local processes. If
> you're using an routed environment without briges ebtables didn't see
> any forwarded packets.

Wouldn't matching iptables rules with src MAC address matching in
FORWARD chain do the trick for the IP routing case?

-- 
Jouni Malinen                                            PGP id EFC895FA



From kleinveld  Wed Sep 22 21:17:35 2004
From: kleinveld (Arnaud Kleinveld)
Date: Thu, 23 Sep 2004 12:17:35 +0800
Subject: wired authentication (kernel module)
In-Reply-To: <20040923040820.GC7360@jm.kir.nu>
References: <20040920085317.GC9381@informatik.uni-rostock.de>	<20040921045742.GH7354@jm.kir.nu>	<20040922221337.GA12132@legolas.on.net.mk>	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923040820.GC7360@jm.kir.nu>
Message-ID: <41524E5F.6090203@pacific.net.sg>

I have tested that in combination with Hostap and it works. I don't think my 
solution is exectly the one Gunter is searching for but I got iptables routing 
unauthenticated clients to a login page. So iptables can do the trick as you 
describe. With wired or wireless client, that doesn't matter.

Arnaud

Jouni Malinen wrote:
> On Thu, Sep 23, 2004 at 06:04:39AM +0200, Gunter Burchardt wrote:
> 
> 
>>ebtables cant do it! if you look through you ebtables kernel code you
>>will see that all forwarding/prerouting/postroutung hooks only works
>>with briges. Input and output hook is only for local processes. If
>>you're using an routed environment without briges ebtables didn't see
>>any forwarded packets.
> 
> 
> Wouldn't matching iptables rules with src MAC address matching in
> FORWARD chain do the trick for the IP routing case?
> 



From gbur  Wed Sep 22 21:48:58 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 06:48:58 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <41524E5F.6090203@pacific.net.sg>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923040820.GC7360@jm.kir.nu> <41524E5F.6090203@pacific.net.sg>
Message-ID: <20040923044858.GB9858@informatik.uni-rostock.de>

> I have tested that in combination with Hostap and it works. I don't think 
> my solution is exectly the one Gunter is searching for but I got iptables 
> routing unauthenticated clients to a login page. So iptables can do the 
> trick as you describe. With wired or wireless client, that doesn't matter.

And what about output? Iptables cant match output mac! Also its
impossible to accout (count bytes and packets) output without knowing
ip address. A port in PAE is normaly assigned to a mac and not to a ip.
hostapd dont care about ip addresses!

regards
gunter 



From kleinveld  Wed Sep 22 22:33:10 2004
From: kleinveld (Arnaud Kleinveld)
Date: Thu, 23 Sep 2004 13:33:10 +0800
Subject: wired authentication (kernel module)
In-Reply-To: <20040923044858.GB9858@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923040820.GC7360@jm.kir.nu> <41524E5F.6090203@pacific.net.sg>
	<20040923044858.GB9858@informatik.uni-rostock.de>
Message-ID: <41526016.80304@pacific.net.sg>

I don't understand where you need to match output.

Now I understand that you also need to implement the counting part beside the 
authentication. It is possible to count mac sources with iptables. You don't 
need the ip address. Something like this works:
iptables -A APINET -m mac --mac-source aa:bb:cc:dd:ee:ff -j ACCEPT
There is only now difference between sent and reveived packets, if that's what 
you meen with output.

Regards,
Arnaud

Gunter Burchardt wrote:
>>I have tested that in combination with Hostap and it works. I don't think 
>>my solution is exectly the one Gunter is searching for but I got iptables 
>>routing unauthenticated clients to a login page. So iptables can do the 
>>trick as you describe. With wired or wireless client, that doesn't matter.
> 
> 
> And what about output? Iptables cant match output mac! Also its
> impossible to accout (count bytes and packets) output without knowing
> ip address. A port in PAE is normaly assigned to a mac and not to a ip.
> hostapd dont care about ip addresses!
> 
> regards
> gunter 
> 



From gbur  Wed Sep 22 22:39:23 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 07:39:23 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040923040439.GA9858@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
Message-ID: <20040923053923.GC9858@informatik.uni-rostock.de>

To round up the discussion i will make a FAQ entry in PAE directory.
There i will write down all me thoughts. I have searched about one week
reading kernel, ip/ebtables, libpcap, ... dokumentation/source to find
a allready existing solution. But all solutions i found didn't work in
right way or have some huge disadvantages.

I'm really not happy about writing this kernel module, but at the
moment there is no other solution. If someone can prove that the kernel
is able to do what i want with existing project/extensions i will drop
this kernel module!

regards
gunter 



From gbur  Wed Sep 22 22:49:17 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 07:49:17 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <41526016.80304@pacific.net.sg>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923040820.GC7360@jm.kir.nu> <41524E5F.6090203@pacific.net.sg>
	<20040923044858.GB9858@informatik.uni-rostock.de>
	<41526016.80304@pacific.net.sg>
Message-ID: <20040923054917.GD9858@informatik.uni-rostock.de>

> I don't understand where you need to match output.
> 
> Now I understand that you also need to implement the counting part beside 
> the authentication. It is possible to count mac sources with iptables. You 
> don't need the ip address. Something like this works:
> iptables -A APINET -m mac --mac-source aa:bb:cc:dd:ee:ff -j ACCEPT
> There is only now difference between sent and reveived packets, if that's 
> what you meen with output.

If you receive packets from a station mac-source is set and you can
accept/account this packets. But with iptables it is impossible to
filter packets to a station, there is no mac-destination option! It
will never give such a option! iptables is layer 3. The mac will be set
in level 2. Thats behind iptables handling. Its impossible to add rules
for packets send to a station if you only hav mac addresses.

Well, its possible to allow all packets sent to stations and drop only
incomming station packets. But what about accounting? For packets from
a station it will work, but no chance to account packets send to the
station with iptables. A mapping from mac address to iptables would
work. But behind one mac address can be more than one ip address. Such
a handling would be very complex (and need extensions too).

regards
gunter



From jkmaline  Wed Sep 22 23:00:34 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 22 Sep 2004 23:00:34 -0700
Subject: wired authentication (kernel module)
In-Reply-To: <20040923053923.GC9858@informatik.uni-rostock.de>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923053923.GC9858@informatik.uni-rostock.de>
Message-ID: <20040923060034.GE7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 07:39:23AM +0200, Gunter Burchardt wrote:

> To round up the discussion i will make a FAQ entry in PAE directory.
> There i will write down all me thoughts. I have searched about one week
> reading kernel, ip/ebtables, libpcap, ... dokumentation/source to find
> a allready existing solution. But all solutions i found didn't work in
> right way or have some huge disadvantages.

Have you looked into this from the view point of what would need to be
changed/added to existing solutions to make them work in the way needed
for PAE/accounting? Could that be less work than adding a new module?
Would it be enough to get ebtables/iptables match for dest MAC addr just
before passing the packet to driver?

-- 
Jouni Malinen                                            PGP id EFC895FA



From gbur  Thu Sep 23 00:07:14 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 09:07:14 +0200
Subject: wired authentication (kernel module)
In-Reply-To: <20040923060034.GE7360@jm.kir.nu>
References: <20040920085317.GC9381@informatik.uni-rostock.de>
	<20040921045742.GH7354@jm.kir.nu>
	<20040922221337.GA12132@legolas.on.net.mk>
	<20040923040439.GA9858@informatik.uni-rostock.de>
	<20040923053923.GC9858@informatik.uni-rostock.de>
	<20040923060034.GE7360@jm.kir.nu>
Message-ID: <20040923070714.GE9858@informatik.uni-rostock.de>

> Have you looked into this from the view point of what would need to be
> changed/added to existing solutions to make them work in the way needed
> for PAE/accounting? Could that be less work than adding a new module?
> Would it be enough to get ebtables/iptables match for dest MAC addr just
> before passing the packet to driver?

Of cause its possible to add tables that uses layer2 hooks in ebtables.
But i saw that only in bridge environment everyfields are filled used
in ebtables. ebtables is really focused on briged environments and
therefor it works good. On my first look it seams not to be easy to add
such tables to ebtables.

I will try to add such a table. But im not very confident that it is
less work (due i allready did the work for the kernel module). I had
problems to access some fields in output packets in my kernel module.
ebtables would have the same problems using the same hook.   

One other thought:
If you only filter mac-addresses with ebtables is really "slow". It handles
rules in a list and a packet will go through all rules in worst cast to
find a matching rule. You know that there are faster methods.

regards
gunter



From hiphin  Thu Sep 23 01:13:46 2004
From: hiphin (hiphin)
Date: Thu, 23 Sep 2004 10:13:46 +0200
Subject: help width 0.2.4 -> 0.2.6
References: <004801c48373$549ba260$0100a8c0@racunar0d>
Message-ID: <023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>

ok, U helped me width 0.2.4 (suse 9.0), help me... teach me now how to fix on 2.6 kernel (suse 9.1), I don't know where to find orinoco, orinoco_pci, hermes modules to coment them out, ...
1. modules.conf iz empty zero leight file
2. modprobe.conf doesn't have orinoco, hermes, wlan, wireless words inside
3. searched entire forder /etc for word orinoco, and nothing ?!?

help,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20040923/d877ba9c/attachment.htm 


From gouders  Thu Sep 23 01:15:34 2004
From: gouders (Dirk Gouders)
Date: Thu, 23 Sep 2004 10:15:34 +0200
Subject: WEP and WPA?
Message-ID: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>

Hello,

is it possible to build an AP with hostap that provides both, WEP and
WPA encryption?

I tried to run hostapd with WEP and WPA both enabled but when I try to
connect with a client that wants WEP encryption, the debugging output
says that there is a client trying to connect that does not speak
WPA...

Dirk



From dermot  Thu Sep 23 02:25:18 2004
From: dermot (Dermot McGahon)
Date: Thu, 23 Sep 2004 10:25:18 +0100
Subject: Rebadged Senoa pcmcia cards with prism 3 chipset
In-Reply-To: <Pine.LNX.4.58.0409221928040.19412@mail3.jubileegroup.co.uk>
References: <20040922144512.A801B3D5B@mail.iocaine.com>
	<Pine.LNX.4.58.0409221928040.19412@mail3.jubileegroup.co.uk>
Message-ID: <opserwggyu3ertue@mail.dspsrv.com>

On Wed, 22 Sep 2004 19:50:47 +0100 (BST), Ged Haywood  
<ged at jubileegroup.co.uk> wrote:

> I don't know understand, StarOS appears to be based on Linux, and
> Prism 3 is supported by HostAP
>
> http://hostap.epitest.fi/
>
> so I should have thought it possible to use Prism3 with StarOS, but I
> know nothing about StarOS.

Hmmm, from the website, http://www.star-os.com/credits.php

-------------------
Software that has been developed in-house, and is not covered by GPL:
Package / Application
[snip]
Wireless drivers for: Intersil Prism 2.0, 2.5, 3.0, Indigo and Duette  
cards, Agere hermes & Ruby cards, Teletronics WL2400 2MB cards, ADMtek  
8211 802.11b cards, Atheros 802.11a/b/g cards.	


Our Wireless drivers are not GPL, however here are some GPL alternatives:

Open Source Project 					License 	Download
Prism 2/2.5 Access Point support (HostAP)  	GPL		hostap.epitest.fi
--------------------



> If not then there's Linux, if you have or
> can find the skills to put the system together.  The skills are easy
> to find I think, but time-consuming to learn.  I don't know what StarOS
> might offer you that a Linux distribution wouldn't, out of the box.

Good question. What StarOS offers above your own linux distro is basically
an invoice :)

That might be a little unfair, they are basically a distribution packager
and offer support. Just like RedHat; Suse; Mandrake, except specialised
for wireless networking. By writing their own drivers though they seem
to be falling behind the curve. It's hard to keep up with good open
source projects.



>> Can anyone also confirm that these are 100mW cards and are basically
>> not as good as the PRISM 2.5 based cards?
>
> I can't comment on that, I don't know the cards you have and I don't
> know how you'd compare them to decide which was better than which.

Fair point. Was really just probing for user experiences with different
versions of the PRISM chipset.


[-]
> are very happy with them.  We are based in England.  Having said that,
> I don't think you need new cards, probably just the right software.

Yes. Thanks Ged. We are going to investigate using a free linux distro
instead: www.me2000.net



Dermot.
--



From ged  Thu Sep 23 04:55:11 2004
From: ged (Ged Haywood)
Date: Thu, 23 Sep 2004 12:55:11 +0100 (BST)
Subject: Rebadged Senoa pcmcia cards with prism 3 chipset
In-Reply-To: <opserwggyu3ertue@mail.dspsrv.com>
References: <20040922144512.A801B3D5B@mail.iocaine.com>
	<Pine.LNX.4.58.0409221928040.19412@mail3.jubileegroup.co.uk>
	<opserwggyu3ertue@mail.dspsrv.com>
Message-ID: <Pine.LNX.4.58.0409231219140.5910@mail3.jubileegroup.co.uk>

Hi Dermot,

On Thu, 23 Sep 2004, Dermot McGahon wrote:

> What StarOS offers above your own linux distro is basically
> an invoice :)
>
> That might be a little unfair ... support

You just wrote the message that I thought better of, and didn't send.
Made the hair stand up on the back of my neck.  :)

> By writing their own drivers though they seem to be falling behind
> the curve. It's hard to keep up with good open source projects.

That's right.  Obvious when you think about it.

> Was really just probing for user experiences with different
> versions of the PRISM chipset.

Glad to share my own, which are basically that I've forgotten all
about them.  The cards we use just sit there and do the work.  One of
them has a 16dB yagi on a rooftop in Derbyshire.  It has a lightning
arrestor in the aerial cable and has been working through all the
lightning storms you could wish for, with no trouble.  I don't expect
it would take a direct hit of course, but it's been all I could have
hoped for short of that.  The only trouble we get is when snow builds
up on the Yagi.  Here's a plot of signal strength (as reported by the
MA311 card) for a snowy day last year:

http://www.jubileegroup.co.uk/JOS/radio/signal_strength.gif

I considered going up there to knock the snow off, but thought better
of it when I looked at the way the mast was bending... :)  When the
signal drops below about -95dB we lose the link of course.  If it was
life-or-death I'd install some means of deicing.

One thing I have noticed is that when we hit the link with a lot of
data, the data rate reported by the card seems to drop.  I sometimes
wonder if it's just measuring actual throughput rather than the link
capability, in which case that would make sense since most of the time
we're using up the full 512kbps bandwidth of our Internet connection.
But sometimes the same thing seems to happen even if we just send data
between the machines at the ends of the link - we run VPN over the
link and there's a firewall at each end, so we don't have to worry
about wireless encryption.  It's not an issue for us, so I haven't
investigated further but if anyone else reading and has any insights
to offer I'd be pleased to hear.

> We are going to investigate using a free linux distro instead:
> www.me2000.net

I'm sure any of the distros has the basics needed do what you want.
Ping the list if you need any more general info., mail me privately if
you want to know more about what we have done here - happy to send you
our kernel configurations etc..

73,
Ged.



From ceyong  Thu Sep 23 05:55:05 2004
From: ceyong (Yong Chu Eu Ñî×ÓÓÓ)
Date: Thu, 23 Sep 2004 05:55:05 -0700 (PDT)
Subject: Problem COnnecting AP from Mobile Node
Message-ID: <20040923125505.23746.qmail@web41009.mail.yahoo.com>


I am having problem in ping or connect AP from Mobile Node(essid & channel
is the same,maybe routing did 
not set properly but i fail to configure with route add default gw
192.168.3.4,its alway said 
network is unreachable ),My Mobile Node is using acx100 as driver while
AP(redhat 9.0) is using
HOSTAP 0.1.3.Any one can help? I heard How-To said we not need to set
address on eth0 & wlan0 if
we have bridge(with address)but will MN connect straight with bridge that
i set? 

My mobile node setting:
[root at localhost scripts]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

mip6mnha  no wireless extensions.

wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
          Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
          Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
          Retry min limit:7   RTS thr:off
          Encryption key:off
          Power Management:off
          Link Quality:69/100  Signal level:57/100  Noise level:0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root at localhost scripts]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
          inet addr:172.16.76.56  Bcast:172.16.76.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
          Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038

lo        Link encap:Local Loopback
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)

mip6mnha1 Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
          UP RUNNING NOARP  MTU:1460  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
          Interrupt:11 Base address:0x4000



My Redhat AP Setting

[root at localhost root]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11b  ESSID:"mipv6b"  Nickname:"localhost.localdomain"
          Mode:Master  Frequency:2.412GHz  Access Point: 00:01:03:88:62:96
          Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
          Retry limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:46   Missed beacon:0

br0       no wireless extensions.

[root at localhost root]# ifconfig
br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
          inet addr:192.168.3.3  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
          inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)

eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
          inet addr:192.168.3.2  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
          inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
          Interrupt:9 Base address:0xd000

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:232 errors:0 dropped:0 overruns:0 frame:0
          TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
          inet addr:192.168.3.4  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
          Interrupt:9 Base address:0xd400


Wireless testBed is almost like below:
 

                                         |
                                     192.168.1.1
                                 3ffe:80f0:ff03:1::1
                                        fxp0
                            FreeBSD 4.10 Router(Vls Server 0.5.6)
                            vr0                   rl0
                       192.168.2.1            192.168.3.1
                     3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
                             |                     |
                             |                     |
                             |                     |
                           eth0                  eth0
                   3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
                       192.168.2.2            192.168.3.2
                   Linux PC Access Point      Linux PC Access Point
                      (HOSTAP 0.13)          (HOSTAP 0.13)
                             |                     |
                             |                     |
                            br0                   br0
                        192.168.2.3            192.168.3.3
                   3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3  
                             |                     |                      
    
                             |                     |
                          wlan0                 wlan0
                        192.168.2.4            192.168.3.4
                       essid:mipv6a           essid:mipv6b


                          ----
                         | MN |
                          ----   
                Roaming notebook (VLC player 0.7.2)
              Linux Kernel 2.4.22 with MIPL 1.0
            (Dlink Wireless  Card with acx100 driver)
           192.168.4.1(Home address 3ffe:80d0:ff03:4::1)



=====
???????????????????????? Happy & Healthy Always ! ^_^ !
???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
???????????? Buddhist Page: http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at hotmail.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail



From jdavid  Thu Sep 23 06:09:33 2004
From: jdavid (Jeff David)
Date: Thu, 23 Sep 2004 09:09:33 -0400
Subject: Problem COnnecting AP from Mobile Node
Message-ID: <C6D44AA99ECEB540A5498F15F92DA07DDD38FD@amperion01>

Your client's IP Address is wrong.  The client should be on the same subnet as the Access Point.  Any routing must occur on the Access Point node, not on the client.  So if you want to connect the MN to 192.168.3.4, it must have a 192.168.3.x ip address.

Jeff


> -----Original Message-----
> From: Yong Chu Eu (??????) [mailto:ceyong at yahoo.com] 
> Sent: Thursday, September 23, 2004 8:55 AM
> To: hostap at shmoo.com; bridge at osdl.org
> Cc: jasonb at edseek.com; jt at hpl.hp.com; linux-help at houseofcraig.net
> Subject: Problem COnnecting AP from Mobile Node
> 
> 
> 
> I am having problem in ping or connect AP from Mobile 
> Node(essid & channel is the same,maybe routing did 
> not set properly but i fail to configure with route add 
> default gw 192.168.3.4,its alway said 
> network is unreachable ),My Mobile Node is using acx100 as 
> driver while AP(redhat 9.0) is using HOSTAP 0.1.3.Any one can 
> help? I heard How-To said we not need to set address on eth0 
> & wlan0 if we have bridge(with address)but will MN connect 
> straight with bridge that i set? 
> 
> My mobile node setting:
> [root at localhost scripts]# iwconfig
> lo        no wireless extensions.
> 
> sit0      no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> ip6tnl0   no wireless extensions.
> 
> mip6mnha  no wireless extensions.
> 
> wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
>           Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
>           Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
>           Retry min limit:7   RTS thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:69/100  Signal level:57/100  Noise level:0/100
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> root at localhost scripts]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
>           inet addr:172.16.76.56  Bcast:172.16.76.255  
> Mask:255.255.255.0
>           inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
>           Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038
> 
> lo        Link encap:Local Loopback
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)
> 
> mip6mnha1 Link encap:UNSPEC  HWaddr 
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
>           UP RUNNING NOARP  MTU:1460  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 
> wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
>           inet addr:192.168.4.1  Bcast:192.168.4.255  
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
>           Interrupt:11 Base address:0x4000
> 
> 
> 
> My Redhat AP Setting
> 
> [root at localhost root]# iwconfig
> lo        no wireless extensions.
> 
> sit0      no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> wlan0     IEEE 802.11b  ESSID:"mipv6b"  
> Nickname:"localhost.localdomain"
>           Mode:Master  Frequency:2.412GHz  Access Point: 
> 00:01:03:88:62:96
>           Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
>           Retry limit:8   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:0
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:46   Missed beacon:0
> 
> br0       no wireless extensions.
> 
> [root at localhost root]# ifconfig
> br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
>           inet addr:192.168.3.3  Bcast:192.168.3.255  
> Mask:255.255.255.0
>           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
>           inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)
> 
> eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
>           inet addr:192.168.3.2  Bcast:192.168.3.255  
> Mask:255.255.255.0
>           inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
>           inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
>           Interrupt:9 Base address:0xd000
> 
> 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:232 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)
> 
> wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
>           inet addr:192.168.3.4  Bcast:192.168.3.255  
> Mask:255.255.255.0
>           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
>           Interrupt:9 Base address:0xd400
> 
> 
> Wireless testBed is almost like below:
>  
> 
>                                          |
>                                      192.168.1.1
>                                  3ffe:80f0:ff03:1::1
>                                         fxp0
>                             FreeBSD 4.10 Router(Vls Server 0.5.6)
>                             vr0                   rl0
>                        192.168.2.1            192.168.3.1
>                      3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
>                              |                     |
>                              |                     |
>                              |                     |
>                            eth0                  eth0
>                    3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
>                        192.168.2.2            192.168.3.2
>                    Linux PC Access Point      Linux PC Access Point
>                       (HOSTAP 0.13)          (HOSTAP 0.13)
>                              |                     |
>                              |                     |
>                             br0                   br0
>                         192.168.2.3            192.168.3.3
>                    3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3  
>                              |                     |          
>             
>     
>                              |                     |
>                           wlan0                 wlan0
>                         192.168.2.4            192.168.3.4
>                        essid:mipv6a           essid:mipv6b
> 
> 
>                           ----
>                          | MN |
>                           ----   
>                 Roaming notebook (VLC player 0.7.2)
>               Linux Kernel 2.4.22 with MIPL 1.0
>             (Dlink Wireless  Card with acx100 driver)
>            192.168.4.1(Home address 3ffe:80d0:ff03:4::1)
> 
> 
> 
> =====
> ???????????????????????? Happy & Healthy Always ! ^_^ ! 
> ???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
> ???????????? Buddhist Page: 
> http://planet.time.net.my/SunwayCity/ceyong/ar> tikel.htm
> 
> ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN 
> Messenger:ceyong at hotmail.com
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail is new and improved - Check it out! 
http://promotions.yahoo.com/new_mail
_______________________________________________
HostAP mailing list
HostAP at shmoo.com
http://lists.shmoo.com/mailman/listinfo/hostap



From gbur  Thu Sep 23 06:45:28 2004
From: gbur (Gunter Burchardt)
Date: Thu, 23 Sep 2004 15:45:28 +0200
Subject: Big Endian problem for ixp435 found.
Message-ID: <20040923134528.GA13539@informatik.uni-rostock.de>

Hello Jouni

One of my college found the problem with bigendian by spending hours of
patching hostapd and reading hexdumps. The problem is in sha1.c in
function SHA1Init() u32 initialisation is used which causes endianess
problem if you read with u8 or u16 pointers.

Perhaps you use kernel cryto engine with 2.6 which hasn't this issue.

regards
gunter



From shine21  Thu Sep 23 07:02:24 2004
From: shine21 (Donghyuk Woo)
Date: Thu, 23 Sep 2004 23:02:24 +0900
Subject: Fragmentation.
Message-ID: <000b01c4a175$f3976f50$4d00a8c0@Lifebook>

Hello, all !

AFAIK, the maximum PSDU size of IEEE 802.11 WLAN is 2346 bytes, while that
of Ethernet is 1500 bytes.
and the IP layer of linux kernel fragmentizes its incoming data from upper
layer into 1500 bytes long packet.

However, I'd like to send frames that is longer than 1500 bytes through IEEE
802.11 WLAN.
Is this possible? If yes, what should I do?

Actually, I tried SOCK_PACKET, but I failed to send such frames. 
(When i call sendto, it returns negative value. I haven't figured out the
reason yet.)

Thanx in advance.





From slimmerz  Thu Sep 23 07:31:59 2004
From: slimmerz (slimmerz)
Date: Thu, 23 Sep 2004 22:31:59 +0800
Subject: basic_rates and oper_rates problem
Message-ID: <4152DE5F.8090607@spymac.com>

Hi list,

1. i am bit confuse about the parameter basic_rates and oper_rates 
settings with iwpriv, what is their different?

regards,
slimmerz




From kahing  Thu Sep 23 09:14:51 2004
From: kahing (Ka-Hing Cheung)
Date: Thu, 23 Sep 2004 09:14:51 -0700
Subject: help width 0.2.4 -> 0.2.6
In-Reply-To: <023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>
References: <004801c48373$549ba260$0100a8c0@racunar0d>
	<023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>
Message-ID: <d9823ac104092309143ba9999f@mail.gmail.com>

ok, U helped me width 0.2.4 (suse 9.0), help me... teach me now how to
fix on 2.6 kernel (suse 9.1), I don't know where to find orinoco,
orinoco_pci, hermes modules to coment them out, ...
1. modules.conf iz empty zero leight file 
2. modprobe.conf doesn't have orinoco, hermes, wlan, wireless words inside 
3. searched entire forder /etc for word orinoco, and nothing ?!? 

Does SuSe 9.1 uses hotplug? If so, just add the modules names to:

/etc/hotplug/blacklist

-khc



From hiphin  Thu Sep 23 12:37:06 2004
From: hiphin (hiphin)
Date: Thu, 23 Sep 2004 21:37:06 +0200
Subject: help width 0.2.4 -> 0.2.6
References: <004801c48373$549ba260$0100a8c0@racunar0d>
	<023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>
	<d9823ac104092309143ba9999f@mail.gmail.com>
Message-ID: <000401c4a1a4$b578fc50$0d02a8c0@racunar01>


----- Original Message ----- 
From: "Ka-Hing Cheung" <kahing at gmail.com>
To: "hiphin" <hiphin at cat-net.co.yu>
Cc: <hostap at shmoo.com>
Sent: Thursday, September 23, 2004 18:14
Subject: Re: help width 0.2.4 -> 0.2.6


> ok, U helped me width 0.2.4 (suse 9.0), help me... teach me now how to
> fix on 2.6 kernel (suse 9.1), I don't know where to find orinoco,
> orinoco_pci, hermes modules to coment them out, ...
> 1. modules.conf iz empty zero leight file
> 2. modprobe.conf doesn't have orinoco, hermes, wlan, wireless words inside
> 3. searched entire forder /etc for word orinoco, and nothing ?!?
>
> Does SuSe 9.1 uses hotplug? If so, just add the modules names to:
>
> /etc/hotplug/blacklist
>
> -khc
> 





From hiphin  Thu Sep 23 13:01:06 2004
From: hiphin (hiphin)
Date: Thu, 23 Sep 2004 22:01:06 +0200
Subject: help width 0.2.4 -> 0.2.6
References: <004801c48373$549ba260$0100a8c0@racunar0d>
	<023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>
	<d9823ac104092309143ba9999f@mail.gmail.com>
Message-ID: <000901c4a1a8$0f9c84b0$0d02a8c0@racunar01>

uppsss...

Suse 9.1, yes it have, and I tryed, but it doesn't completly solve problem, 
... it does't bring wlan configured (yes I have ifcfg-wlan... file), any 
other idea or I should put some script to auto configure wlan

thanks Ka-Hing 





From bpon  Thu Sep 23 13:27:13 2004
From: bpon (Barry Pon)
Date: Thu, 23 Sep 2004 13:27:13 -0700
Subject: Xperex Corp Looking for Embedded SW  Engr with WPA Experience
Message-ID: <OFC05D584C.0DDC7D69-ON88256F18.007011FE-88256F18.00703495@xperex.com>

Sorry if this is not the write place to be posting a help wanted sign, but 
thought that there would be one of you that may be interested in helping 
us out on a contract basis.

Xperex is looking for an experienced embedded SW engineer that can help 
port a WPA supplicant to our propietary embedded platform running ThreadX.
If you have experience working with driver development on wireless pcmcia 
cards like Cisco Aironet 350 cards that would help...

Thanks

Barry Pon
Director, Technology Services
Xperex Corp
384 Oyster Point Blvd, Unit 9
South San Francisco, CA  94080
650.266.2001 
bpon at xperex.com
PLEASE NOTE NEW ADDRESS ABOVE

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


From tanuja_iv  Thu Sep 23 13:33:36 2004
From: tanuja_iv (tanuja ingale)
Date: Fri, 24 Sep 2004 02:03:36 +0530
Subject: Support for DLink DWL rev M, in hostAP? 
Message-ID: <BAY12-F161ndcx3Vp2000006628@hotmail.com>

Hi,

I have a D-Link DWL 650 Rev.M1 which I am not able to get working with 
hostAP. Can anybody let me know if this version is supported by hostAP? And 
if not, then which is the latest version of Prism2 based Dlink card being 
supported by this driver?

Thanks,
Tanuja

_________________________________________________________________
All the news that matters. All the gossip from home. 
http://www.msn.co.in/NRI/ Specially for NRIs!




From brian  Thu Sep 23 14:47:26 2004
From: brian (Brian J. Murrell)
Date: Thu, 23 Sep 2004 17:47:26 -0400
Subject: Preparations for 0.2.5 release
In-Reply-To: <20040923035759.GB7360@jm.kir.nu>
References: <20040923035759.GB7360@jm.kir.nu>
Message-ID: <1095976046.14063.47.camel@pc>

On Wed, 2004-09-22 at 20:57 -0700, Jouni Malinen wrote:
> I'm hoping to make a new release from the stable 0.2.x branch shortly.
> This is a bug fix -only version with number of fixes backported from the
> development branch. I just made 0.2.5-pre1 version available for
> testing. Please let me know if you notice any issues with this or think
> that there are some issues with the code that should be fixed before
> 0.2.5 release.
> 
> The pre-release versions are available from following URLs:
> 
> http://hostap.epitest.fi/releases/testing/hostap-driver-0.2.5-pre1.tar.gz
> http://hostap.epitest.fi/releases/testing/hostapd-0.2.5-pre1.tar.gz
> http://hostap.epitest.fi/releases/testing/wpa_supplicant-0.2.5-pre1.tar.gz

For reference was this taken off of the hostap_0_2_branch branch?
Should we consider that the head of that branch will be 0.2.5 when it's
ready?

b.

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


From zen_hacker  Thu Sep 23 15:32:32 2004
From: zen_hacker (Brian Sturgill)
Date: Thu, 23 Sep 2004 22:32:32 +0000
Subject: Problem COnnecting AP from Mobile Node
Message-ID: <BAY13-F3vh18cbKTrRV00007ea4@hotmail.com>

Your problem is probably your bridge. When you bridge two interfaces, 
standard practice is as follows:
Your ethernet and wireless interface are bridged as br0 and the ip info is 
then set on the bridge interface.
In your case it would be something like: (if your 192 address is a class c 
subnet)

/sbin/brctl addbr br0
/sbin/brctl addif br0 eth0
/sbin/brctl addif br0 wlan0
/sbin/ifconfig eth0 0.0.0.0
/sbin/ifconfig wlan0 0.0.0.0
/sbin/ifconfig br0 192.168.2.3 broadcast 192.168.2.255 netmask 255.255.255.0 
up
/sbin/route add default gw 192.168.2.1

Another problem I see is you have your roaming client's ip on a different 
subnet than the access point (linux box). Your client doesn't know anything 
about the other subnets. Are you using NAT to get to the internet or is this 
just a private network? One easy thing to do is change the ip of the client 
to 192.168.2.5 and see if you can see the rest of your network. (Try to ping 
192.168.2.2 and then try 192.168.2.1)

Brian


>From: "Yong Chu Eu (??????)" <ceyong at yahoo.com>
>To: hostap at shmoo.com, bridge at osdl.org
>CC: jasonb at edseek.com, jt at hpl.hp.com, linux-help at houseofcraig.net
>Subject: Problem COnnecting AP from Mobile Node
>Date: Thu, 23 Sep 2004 05:55:05 -0700 (PDT)
>
>
>I am having problem in ping or connect AP from Mobile Node(essid & channel
>is the same,maybe routing did
>not set properly but i fail to configure with route add default gw
>192.168.3.4,its alway said
>network is unreachable ),My Mobile Node is using acx100 as driver while
>AP(redhat 9.0) is using
>HOSTAP 0.1.3.Any one can help? I heard How-To said we not need to set
>address on eth0 & wlan0 if
>we have bridge(with address)but will MN connect straight with bridge that
>i set?
>
>My mobile node setting:
>[root at localhost scripts]# iwconfig
>lo        no wireless extensions.
>
>sit0      no wireless extensions.
>
>eth0      no wireless extensions.
>
>ip6tnl0   no wireless extensions.
>
>mip6mnha  no wireless extensions.
>
>wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
>           Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
>           Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
>           Retry min limit:7   RTS thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:69/100  Signal level:57/100  Noise level:0/100
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
>root at localhost scripts]# ifconfig
>eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
>           inet addr:172.16.76.56  Bcast:172.16.76.255  Mask:255.255.255.0
>           inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
>           Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038
>
>lo        Link encap:Local Loopback
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)
>
>mip6mnha1 Link encap:UNSPEC  HWaddr
>00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>           inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
>           UP RUNNING NOARP  MTU:1460  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
>wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
>           inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
>           Interrupt:11 Base address:0x4000
>
>
>
>My Redhat AP Setting
>
>[root at localhost root]# iwconfig
>lo        no wireless extensions.
>
>sit0      no wireless extensions.
>
>eth0      no wireless extensions.
>
>wlan0     IEEE 802.11b  ESSID:"mipv6b"  Nickname:"localhost.localdomain"
>           Mode:Master  Frequency:2.412GHz  Access Point: 00:01:03:88:62:96
>           Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
>           Retry limit:8   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:0
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:46   Missed beacon:0
>
>br0       no wireless extensions.
>
>[root at localhost root]# ifconfig
>br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
>           inet addr:192.168.3.3  Bcast:192.168.3.255  Mask:255.255.255.0
>           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
>           inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)
>
>eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
>           inet addr:192.168.3.2  Bcast:192.168.3.255  Mask:255.255.255.0
>           inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
>           inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
>           Interrupt:9 Base address:0xd000
>
>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:232 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)
>
>wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
>           inet addr:192.168.3.4  Bcast:192.168.3.255  Mask:255.255.255.0
>           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
>           Interrupt:9 Base address:0xd400
>
>
>Wireless testBed is almost like below:
>
>
>                                          |
>                                      192.168.1.1
>                                  3ffe:80f0:ff03:1::1
>                                         fxp0
>                             FreeBSD 4.10 Router(Vls Server 0.5.6)
>                             vr0                   rl0
>                        192.168.2.1            192.168.3.1
>                      3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
>                              |                     |
>                              |                     |
>                              |                     |
>                            eth0                  eth0
>                    3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
>                        192.168.2.2            192.168.3.2
>                    Linux PC Access Point      Linux PC Access Point
>                       (HOSTAP 0.13)          (HOSTAP 0.13)
>                              |                     |
>                              |                     |
>                             br0                   br0
>                         192.168.2.3            192.168.3.3
>                    3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3
>                              |                     |
>
>                              |                     |
>                           wlan0                 wlan0
>                         192.168.2.4            192.168.3.4
>                        essid:mipv6a           essid:mipv6b
>
>
>                           ----
>                          | MN |
>                           ----
>                 Roaming notebook (VLC player 0.7.2)
>               Linux Kernel 2.4.22 with MIPL 1.0
>             (Dlink Wireless  Card with acx100 driver)
>            192.168.4.1(Home address 3ffe:80d0:ff03:4::1)
>
>
>
>=====
>???????????????????????? Happy & Healthy Always ! ^_^ !
>???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
>???????????? Buddhist Page: 
>http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
>ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at 
>hotmail.com
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail is new and improved - Check it out!
>http://promotions.yahoo.com/new_mail
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From ramalhais  Thu Sep 23 15:37:11 2004
From: ramalhais (Pedro Ramalhais)
Date: Thu, 23 Sep 2004 23:37:11 +0100
Subject: Preparations for 0.2.5 release
In-Reply-To: <20040923035759.GB7360@jm.kir.nu>
References: <20040923035759.GB7360@jm.kir.nu>
Message-ID: <1095978985.20143.8.camel@rootix>

On Thu, 2004-09-23 at 04:57, Jouni Malinen wrote:
> I'm hoping to make a new release from the stable 0.2.x branch shortly.
> This is a bug fix -only version with number of fixes backported from the
> development branch. I just made 0.2.5-pre1 version available for
> testing. Please let me know if you notice any issues with this or think
> that there are some issues with the code that should be fixed before
> 0.2.5 release.
> 
> The pre-release versions are available from following URLs:
> 
> http://hostap.epitest.fi/releases/testing/hostap-driver-0.2.5-pre1.tar.gz
> http://hostap.epitest.fi/releases/testing/hostapd-0.2.5-pre1.tar.gz
> http://hostap.epitest.fi/releases/testing/wpa_supplicant-0.2.5-pre1.tar.gz

Would you include the ipw2100 driver interface for wpa_supplicant? If
you would, could you wait a bit until the next ipw2100 driver is out?
Thanks!
-- 
Pedro Ramalhais <ramalhais at serrado.net>




From jkmaline  Thu Sep 23 18:53:12 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 23 Sep 2004 18:53:12 -0700
Subject: Preparations for 0.2.5 release
In-Reply-To: <1095976046.14063.47.camel@pc>
References: <20040923035759.GB7360@jm.kir.nu> <1095976046.14063.47.camel@pc>
Message-ID: <20040924015312.GB7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 05:47:26PM -0400, Brian J. Murrell wrote:

> For reference was this taken off of the hostap_0_2_branch branch?
> Should we consider that the head of that branch will be 0.2.5 when it's
> ready?

Yes, 0.2.5-pre1 is indeed from hostap_0_2_branch and it is actually
identical to the current head of that branch. All 0.2.x releases are
going to be released from the head of hostap_0_2_branch.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Sep 23 18:56:49 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 23 Sep 2004 18:56:49 -0700
Subject: Preparations for 0.2.5 release
In-Reply-To: <1095978985.20143.8.camel@rootix>
References: <20040923035759.GB7360@jm.kir.nu> <1095978985.20143.8.camel@rootix>
Message-ID: <20040924015649.GC7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 11:37:11PM +0100, Pedro Ramalhais wrote:

> Would you include the ipw2100 driver interface for wpa_supplicant? If
> you would, could you wait a bit until the next ipw2100 driver is out?

I would be happy to include ipw2100 driver interface. However, I would
like to see it first added to the development branch and once that has
received some testing, I can merge it to the 0.2.x branch and for the
next 0.2.x release. I consider 0.2.5 release to be bug fix release and
don't think it should wait for this. 0.2.6 release can be made once the
ipw2100 interface is ready.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Sep 23 19:04:35 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 23 Sep 2004 19:04:35 -0700
Subject: Big Endian problem for ixp435 found.
In-Reply-To: <20040923134528.GA13539@informatik.uni-rostock.de>
References: <20040923134528.GA13539@informatik.uni-rostock.de>
Message-ID: <20040924020435.GD7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 03:45:28PM +0200, Gunter Burchardt wrote:

> One of my college found the problem with bigendian by spending hours of
> patching hostapd and reading hexdumps. The problem is in sha1.c in
> function SHA1Init() u32 initialisation is used which causes endianess
> problem if you read with u8 or u16 pointers.
> 
> Perhaps you use kernel cryto engine with 2.6 which hasn't this issue.

That's confusing.. Could you please give me a bit more detailed
explanation? Did you try running the SHA-1 tests that I mentioned? If
SHA1Init() does not work at all on the board, those should fail..
However, interestingly, I cannot reproduce this on the ixp425 board I
used in testing. Kernel crypto code is not used at all in hostapd..

As far as I know, sha1.c works on both little and big endian systems.
SHA1Init() is only using 32-bit variables. Which functions do you mean
with u8/u16 pointers? There are no u16 processing in sha1.c and u8 is
used only in arguments to memcpy()..

In addition, I would expect context to always be alligned properly,
since it is only used as a local variable in functions within sha1.c.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Thu Sep 23 19:06:42 2004
From: jkmaline (Jouni Malinen)
Date: Thu, 23 Sep 2004 19:06:42 -0700
Subject: WEP and WPA?
In-Reply-To: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
References: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
Message-ID: <20040924020642.GE7360@jm.kir.nu>

On Thu, Sep 23, 2004 at 10:15:34AM +0200, Dirk Gouders wrote:

> is it possible to build an AP with hostap that provides both, WEP and
> WPA encryption?
> 
> I tried to run hostapd with WEP and WPA both enabled but when I try to
> connect with a client that wants WEP encryption, the debugging output
> says that there is a client trying to connect that does not speak
> WPA...

The current version of hostapd does not support this kind of mixed
configuration. In theory, this is possible configuration for WPA, but it
would require some changes for hostapd to handle the STAs that do not
use WPA (either provide keys with IEEE 802.1X or use staticly configured
WEP keys).

-- 
Jouni Malinen                                            PGP id EFC895FA



From ceyong  Thu Sep 23 22:23:43 2004
From: ceyong (Yong Chu Eu Ñî×ÓÓÓ)
Date: Thu, 23 Sep 2004 22:23:43 -0700 (PDT)
Subject: Problem COnnecting AP from Mobile Node
In-Reply-To: <C6D44AA99ECEB540A5498F15F92DA07DDD38FD@amperion01>
Message-ID: <20040924052343.24990.qmail@web41012.mail.yahoo.com>

Thanks for kindly advice,Another question:

since i have 2 AP,how do i set the routing(static) between 2 AP if the
mobile node roaming between this 2 AP? 

Any idea?


--- Jeff David <jdavid at amperion.com> wrote:

> Your client's IP Address is wrong.  The client should be on the same
> subnet as the Access Point.  Any routing must occur on the Access Point
> node, not on the client.  So if you want to connect the MN to
> 192.168.3.4, it must have a 192.168.3.x ip address.
> 
> Jeff
> 
> 
> > -----Original Message-----
> > From: Yong Chu Eu (??????) [mailto:ceyong at yahoo.com] 
> > Sent: Thursday, September 23, 2004 8:55 AM
> > To: hostap at shmoo.com; bridge at osdl.org
> > Cc: jasonb at edseek.com; jt at hpl.hp.com; linux-help at houseofcraig.net
> > Subject: Problem COnnecting AP from Mobile Node
> > 
> > 
> > 
> > I am having problem in ping or connect AP from Mobile 
> > Node(essid & channel is the same,maybe routing did 
> > not set properly but i fail to configure with route add 
> > default gw 192.168.3.4,its alway said 
> > network is unreachable ),My Mobile Node is using acx100 as 
> > driver while AP(redhat 9.0) is using HOSTAP 0.1.3.Any one can 
> > help? I heard How-To said we not need to set address on eth0 
> > & wlan0 if we have bridge(with address)but will MN connect 
> > straight with bridge that i set? 
> > 
> > My mobile node setting:
> > [root at localhost scripts]# iwconfig
> > lo        no wireless extensions.
> > 
> > sit0      no wireless extensions.
> > 
> > eth0      no wireless extensions.
> > 
> > ip6tnl0   no wireless extensions.
> > 
> > mip6mnha  no wireless extensions.
> > 
> > wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
> >           Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
> >           Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
> >           Retry min limit:7   RTS thr:off
> >           Encryption key:off
> >           Power Management:off
> >           Link Quality:69/100  Signal level:57/100  Noise level:0/100
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> > 
> > root at localhost scripts]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
> >           inet addr:172.16.76.56  Bcast:172.16.76.255  
> > Mask:255.255.255.0
> >           inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
> >           Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038
> > 
> > lo        Link encap:Local Loopback
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)
> > 
> > mip6mnha1 Link encap:UNSPEC  HWaddr 
> > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >           inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
> >           UP RUNNING NOARP  MTU:1460  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> > 
> > wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
> >           inet addr:192.168.4.1  Bcast:192.168.4.255  
> > Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
> >           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
> >           Interrupt:11 Base address:0x4000
> > 
> > 
> > 
> > My Redhat AP Setting
> > 
> > [root at localhost root]# iwconfig
> > lo        no wireless extensions.
> > 
> > sit0      no wireless extensions.
> > 
> > eth0      no wireless extensions.
> > 
> > wlan0     IEEE 802.11b  ESSID:"mipv6b"  
> > Nickname:"localhost.localdomain"
> >           Mode:Master  Frequency:2.412GHz  Access Point: 
> > 00:01:03:88:62:96
> >           Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
> >           Retry limit:8   RTS thr:off   Fragment thr:off
> >           Encryption key:off
> >           Power Management:off
> >           Link Quality:0  Signal level:0  Noise level:0
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:46   Missed beacon:0
> > 
> > br0       no wireless extensions.
> > 
> > [root at localhost root]# ifconfig
> > br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> >           inet addr:192.168.3.3  Bcast:192.168.3.255  
> > Mask:255.255.255.0
> >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> >           inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)
> > 
> > eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
> >           inet addr:192.168.3.2  Bcast:192.168.3.255  
> > Mask:255.255.255.0
> >           inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
> >           inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
> >           Interrupt:9 Base address:0xd000
> > 
> > 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:232 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)
> > 
> > wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> >           inet addr:192.168.3.4  Bcast:192.168.3.255  
> > Mask:255.255.255.0
> >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
> >           Interrupt:9 Base address:0xd400
> > 
> > 
> > Wireless testBed is almost like below:
> >  
> > 
> >                                          |
> >                                      192.168.1.1
> >                                  3ffe:80f0:ff03:1::1
> >                                         fxp0
> >                             FreeBSD 4.10 Router(Vls Server 0.5.6)
> >                             vr0                   rl0
> >                        192.168.2.1            192.168.3.1
> >                      3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
> >                              |                     |
> >                              |                     |
> >                              |                     |
> >                            eth0                  eth0
> >                    3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
> >                        192.168.2.2            192.168.3.2
> >                    Linux PC Access Point      Linux PC Access Point
> >                       (HOSTAP 0.13)          (HOSTAP 0.13)
> >                              |                     |
> >                              |                     |
> >                             br0                   br0
> >                         192.168.2.3            192.168.3.3
> >                    3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3  
> >                              |                     |          
> >             
> >     
> >                              |                     |
> >                           wlan0                 wlan0
> >                         192.168.2.4            192.168.3.4
> >                        essid:mipv6a           essid:mipv6b
> > 
> > 
> >                           ----
> >                          | MN |
> >                           ----   
> >                 Roaming notebook (VLC player 0.7.2)
> >               Linux Kernel 2.4.22 with MIPL 1.0
> >             (Dlink Wireless  Card with acx100 driver)
> >            192.168.4.1(Home address 3ffe:80d0:ff03:4::1)
> > 
> > 
> > 
> > =====
> > ???????????????????????? Happy & Healthy Always ! ^_^ ! 
> > ???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
> > ???????????? Buddhist Page: 
> > http://planet.time.net.my/SunwayCity/ceyong/ar> tikel.htm
> > 
> > ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN 
> > Messenger:ceyong at hotmail.com
> > 
> > 
> > 		
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail is new and improved - Check it out! 
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
> 


=====
???????????????????????? Happy & Healthy Always ! ^_^ !
???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
???????????? Buddhist Page: http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at hotmail.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail



From ceyong  Thu Sep 23 22:55:17 2004
From: ceyong (Yong Chu Eu Ñî×ÓÓÓ)
Date: Thu, 23 Sep 2004 22:55:17 -0700 (PDT)
Subject: Problem COnnecting AP from Mobile Node
In-Reply-To: <20040924052532.F3890E91C@mail.iocaine.com>
Message-ID: <20040924055517.70269.qmail@web41015.mail.yahoo.com>

When i configure MN(192.168.3.4)same subnet address with
AP(br0:192.168.3.3),its work. Thanks
I will unset all IP address on eth0 & wlan0 on AP.

my testbed just a small private wireless LAN,not NAT. Another thing is if
i want the MN roaming between this 2 AP(different Subnet),how can i
statically(manually) configure the routing between this 2 AP? it seem not
easy.

Later i will test on IPv6 routing & mobility testing

> Date: Thu, 23 Sep 2004 22:32:32 +0000
> From: "Brian Sturgill" <zen_hacker at hotmail.com>
> Subject: RE: Problem COnnecting AP from Mobile Node
> To: hostap at shmoo.com
> Message-ID: <BAY13-F3vh18cbKTrRV00007ea4 at hotmail.com>
> Content-Type: text/plain; format=flowed
> 
> Your problem is probably your bridge. When you bridge two interfaces, 
> standard practice is as follows:
> Your ethernet and wireless interface are bridged as br0 and the ip info
> is 
> then set on the bridge interface.
> In your case it would be something like: (if your 192 address is a class
> c 
> subnet)
> 
> /sbin/brctl addbr br0
> /sbin/brctl addif br0 eth0
> /sbin/brctl addif br0 wlan0
> /sbin/ifconfig eth0 0.0.0.0
> /sbin/ifconfig wlan0 0.0.0.0
> /sbin/ifconfig br0 192.168.2.3 broadcast 192.168.2.255 netmask
> 255.255.255.0 
> up
> /sbin/route add default gw 192.168.2.1
> 
> Another problem I see is you have your roaming client's ip on a
> different 
> subnet than the access point (linux box). Your client doesn't know
> anything 
> about the other subnets. Are you using NAT to get to the internet or is
> this 
> just a private network? One easy thing to do is change the ip of the
> client 
> to 192.168.2.5 and see if you can see the rest of your network. (Try to
> ping 
> 192.168.2.2 and then try 192.168.2.1)
> 
> Brian
> 
> 
> >From: "Yong Chu Eu (??????)" <ceyong at yahoo.com>
> >To: hostap at shmoo.com, bridge at osdl.org
> >CC: jasonb at edseek.com, jt at hpl.hp.com, linux-help at houseofcraig.net
> >Subject: Problem COnnecting AP from Mobile Node
> >Date: Thu, 23 Sep 2004 05:55:05 -0700 (PDT)
> >
> >
> >I am having problem in ping or connect AP from Mobile Node(essid &
> channel
> >is the same,maybe routing did
> >not set properly but i fail to configure with route add default gw
> >192.168.3.4,its alway said
> >network is unreachable ),My Mobile Node is using acx100 as driver while
> >AP(redhat 9.0) is using
> >HOSTAP 0.1.3.Any one can help? I heard How-To said we not need to set
> >address on eth0 & wlan0 if
> >we have bridge(with address)but will MN connect straight with bridge
> that
> >i set?
> >
> >My mobile node setting:
> >[root at localhost scripts]# iwconfig
> >lo        no wireless extensions.
> >
> >sit0      no wireless extensions.
> >
> >eth0      no wireless extensions.
> >
> >ip6tnl0   no wireless extensions.
> >
> >mip6mnha  no wireless extensions.
> >
> >wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
> >           Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
> >           Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
> >           Retry min limit:7   RTS thr:off
> >           Encryption key:off
> >           Power Management:off
> >           Link Quality:69/100  Signal level:57/100  Noise level:0/100
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> >
> >root at localhost scripts]# ifconfig
> >eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
> >           inet addr:172.16.76.56  Bcast:172.16.76.255 
> Mask:255.255.255.0
> >           inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
> >           Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038
> >
> >lo        Link encap:Local Loopback
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)
> >
> >mip6mnha1 Link encap:UNSPEC  HWaddr
> >00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >           inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
> >           UP RUNNING NOARP  MTU:1460  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> >
> >wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
> >           inet addr:192.168.4.1  Bcast:192.168.4.255 
> Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
> >           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
> >           Interrupt:11 Base address:0x4000
> >
> >
> >
> >My Redhat AP Setting
> >
> >[root at localhost root]# iwconfig
> >lo        no wireless extensions.
> >
> >sit0      no wireless extensions.
> >
> >eth0      no wireless extensions.
> >
> >wlan0     IEEE 802.11b  ESSID:"mipv6b" 
> Nickname:"localhost.localdomain"
> >           Mode:Master  Frequency:2.412GHz  Access Point:
> 00:01:03:88:62:96
> >           Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
> >           Retry limit:8   RTS thr:off   Fragment thr:off
> >           Encryption key:off
> >           Power Management:off
> >           Link Quality:0  Signal level:0  Noise level:0
> >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:46   Missed beacon:0
> >
> >br0       no wireless extensions.
> >
> >[root at localhost root]# ifconfig
> >br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> >           inet addr:192.168.3.3  Bcast:192.168.3.255 
> Mask:255.255.255.0
> >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> >           inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)
> >
> >eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
> >           inet addr:192.168.3.2  Bcast:192.168.3.255 
> Mask:255.255.255.0
> >           inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
> >           inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
> >           Interrupt:9 Base address:0xd000
> >
> >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:232 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)
> >
> >wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> >           inet addr:192.168.3.4  Bcast:192.168.3.255 
> Mask:255.255.255.0
> >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
> >           Interrupt:9 Base address:0xd400
> >
> >
> >Wireless testBed is almost like below:
> >
> >
> >                                          |
> >                                      192.168.1.1
> >                                  3ffe:80f0:ff03:1::1
> >                                         fxp0
> >                             FreeBSD 4.10 Router(Vls Server 0.5.6)
> >                             vr0                   rl0
> >                        192.168.2.1            192.168.3.1
> >                      3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
> >                              |                     |
> >                              |                     |
> >                              |                     |
> >                            eth0                  eth0
> >                    3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
> >                        192.168.2.2            192.168.3.2
> >                    Linux PC Access Point      Linux PC Access Point
> >                       (HOSTAP 0.13)          (HOSTAP 0.13)
> >                              |                     |
> >                              |                     |
> >                             br0                   br0
> >                         192.168.2.3            192.168.3.3
> >                    3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3
> >                              |                     |
> >
> >                              |                     |
> >                           wlan0                 wlan0
> >                         192.168.2.4            192.168.3.4
> >                        essid:mipv6a           essid:mipv6b
> >
> >
> >                           ----
> >                          | MN |
> >                           ----
> >                 Roaming notebook (VLC player 0.7.2)
> >               Linux Kernel 2.4.22 with MIPL 1.0
> >             (Dlink Wireless  Card with acx100 driver)
> >            192.168.4.1(Home address 3ffe:80d0:ff03:4::1)
> >
> >
> >


=====
???????????????????????? Happy & Healthy Always ! ^_^ !
???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
???????????? Buddhist Page: http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at hotmail.com


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



From brian  Thu Sep 23 23:06:38 2004
From: brian (Brian J. Murrell)
Date: Fri, 24 Sep 2004 02:06:38 -0400
Subject: trying to use wpa_supplicant with bonding driver
Message-ID: <1096005999.14063.61.camel@pc>

My laptop has both an 802.11b wireless and 100Mb/s wired interfaces.
After doing some reading it looks like what I want is a bonding
interface with them.  I want both interfaces to act as one, whichever
one is attached to the network, so that if I unplug the 100Mb/s
everything automatically switches to wlan.  I have that set up and half
working.

When my 100M/b interface is plugged in, everything through bond0 works
just fine, however the wlan0 slave interface configured to use
wpa_supplicant is not configuring correctly with wpa_supplicant.  This
interface works fine with wpa_supplicant when used in a non-bonding
configuration so he basics seem to be met.

Here is the wpa_supplicant log from trying to set up with the AP while
being a bonded slave interface can be found at
http://brian.interlinx.bc.ca/wpa_supplicant.log

I am using the latest on the 0.2.x cvs branch.

What is going wrong?

b.



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


From gbur  Fri Sep 24 00:31:21 2004
From: gbur (Gunter Burchardt)
Date: Fri, 24 Sep 2004 09:31:21 +0200
Subject: Big Endian problem for ixp435 found.
In-Reply-To: <20040924020435.GD7360@jm.kir.nu>
References: <20040923134528.GA13539@informatik.uni-rostock.de>
	<20040924020435.GD7360@jm.kir.nu>
Message-ID: <20040924073121.GB13539@informatik.uni-rostock.de>

> That's confusing.. Could you please give me a bit more detailed
> explanation? Did you try running the SHA-1 tests that I mentioned? If
> SHA1Init() does not work at all on the board, those should fail..
> However, interestingly, I cannot reproduce this on the ixp425 board I
> used in testing. Kernel crypto code is not used at all in hostapd..
> 
> As far as I know, sha1.c works on both little and big endian systems.
> SHA1Init() is only using 32-bit variables. Which functions do you mean
> with u8/u16 pointers? There are no u16 processing in sha1.c and u8 is
> used only in arguments to memcpy()..

sha1.c compiled with -DTEST_MAIN fails!

with -DVERBOSE it returns on my ixp425:

PRF-SHA1 test cases:
before (0,0) 67452301 efcdab89 98badcfe 10325476 c3d2e1f0
after  (512,0) 4df4a024 82182f0f 2891a3b7 9baf80db 6534f2c7
...

on x86:

PRF-SHA1 test cases:
before (0,0) 67452301 efcdab89 98badcfe 10325476 c3d2e1f0
after  (512,0) 64c662a cc6ed1b0 6cfa9ab0 42f137f cea570eb

regards
gunter



From gbur  Fri Sep 24 03:57:12 2004
From: gbur (Gunter Burchardt)
Date: Fri, 24 Sep 2004 12:57:12 +0200
Subject: Big Endian problem for ixp435 found.
In-Reply-To: <20040924020435.GD7360@jm.kir.nu>
References: <20040923134528.GA13539@informatik.uni-rostock.de>
	<20040924020435.GD7360@jm.kir.nu>
Message-ID: <20040924105712.GD13539@informatik.uni-rostock.de>

> In addition, I would expect context to always be alligned properly,
> since it is only used as a local variable in functions within sha1.c.

Yes it is a alingment problem in SHA1Transform().

        static unsigned char workspace[64];
        block = (CHAR64LONG16 *) workspace;

workspace[64] is NOT aligned at a 4 byte address. if you cast this to
block (u32 l[16]) it gets problem with alignment!

        static u32 workspace[16];
        block = (CHAR64LONG16 *) workspace;

Workspace is alligned at a 4 byte address. This works for me!

regards
gunter



From zen_hacker  Fri Sep 24 05:17:19 2004
From: zen_hacker (Brian Sturgill)
Date: Fri, 24 Sep 2004 12:17:19 +0000
Subject: Problem COnnecting AP from Mobile Node
Message-ID: <BAY13-F18KtdhQYZkxO0000b88e@hotmail.com>

Why don't you put everything on one subnet so you don't even have to worry 
about routing? Otherwise, you are going to have to set up a dhcp server on 
both subnets so the ip can change without having to set it manually when the 
client roams between AP's.


Brian



>From: "Yong Chu Eu (??????)" <ceyong at yahoo.com>
>To: Jeff David <jdavid at amperion.com>, hostap at shmoo.com,bridge at osdl.org
>CC: jasonb at edseek.com, jt at hpl.hp.com, linux-help at houseofcraig.net
>Subject: RE: Problem COnnecting AP from Mobile Node
>Date: Thu, 23 Sep 2004 22:23:43 -0700 (PDT)
>
>Thanks for kindly advice,Another question:
>
>since i have 2 AP,how do i set the routing(static) between 2 AP if the
>mobile node roaming between this 2 AP?
>
>Any idea?
>
>
>--- Jeff David <jdavid at amperion.com> wrote:
>
> > Your client's IP Address is wrong.  The client should be on the same
> > subnet as the Access Point.  Any routing must occur on the Access Point
> > node, not on the client.  So if you want to connect the MN to
> > 192.168.3.4, it must have a 192.168.3.x ip address.
> >
> > Jeff
> >
> >
> > > -----Original Message-----
> > > From: Yong Chu Eu (??????) [mailto:ceyong at yahoo.com]
> > > Sent: Thursday, September 23, 2004 8:55 AM
> > > To: hostap at shmoo.com; bridge at osdl.org
> > > Cc: jasonb at edseek.com; jt at hpl.hp.com; linux-help at houseofcraig.net
> > > Subject: Problem COnnecting AP from Mobile Node
> > >
> > >
> > >
> > > I am having problem in ping or connect AP from Mobile
> > > Node(essid & channel is the same,maybe routing did
> > > not set properly but i fail to configure with route add
> > > default gw 192.168.3.4,its alway said
> > > network is unreachable ),My Mobile Node is using acx100 as
> > > driver while AP(redhat 9.0) is using HOSTAP 0.1.3.Any one can
> > > help? I heard How-To said we not need to set address on eth0
> > > & wlan0 if we have bridge(with address)but will MN connect
> > > straight with bridge that i set?
> > >
> > > My mobile node setting:
> > > [root at localhost scripts]# iwconfig
> > > lo        no wireless extensions.
> > >
> > > sit0      no wireless extensions.
> > >
> > > eth0      no wireless extensions.
> > >
> > > ip6tnl0   no wireless extensions.
> > >
> > > mip6mnha  no wireless extensions.
> > >
> > > wlan0     IEEE 802.11b+  ESSID:"mipv6b"  Nickname:"acx100 v0.2.0pre8"
> > >           Mode:Managed  Channel:1  Access Point: 00:01:03:88:62:96
> > >           Bit Rate=11Mb/s   Tx-Power:18 dBm   Sensitivity=176/255
> > >           Retry min limit:7   RTS thr:off
> > >           Encryption key:off
> > >           Power Management:off
> > >           Link Quality:69/100  Signal level:57/100  Noise level:0/100
> > >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> > >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> > >
> > > root at localhost scripts]# ifconfig
> > > eth0      Link encap:Ethernet  HWaddr 00:D0:59:80:0C:2E
> > >           inet addr:172.16.76.56  Bcast:172.16.76.255
> > > Mask:255.255.255.0
> > >           inet6 addr: fe80::2d0:59ff:fe80:c2e/64 Scope:Link
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:3832 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:100
> > >           RX bytes:252364 (246.4 Kb)  TX bytes:3140 (3.0 Kb)
> > >           Interrupt:11 Base address:0x1400 Memory:f4020000-f4020038
> > >
> > > lo        Link encap:Local Loopback
> > >           inet6 addr: ::1/128 Scope:Host
> > >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> > >           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:5256 (5.1 Kb)  TX bytes:5256 (5.1 Kb)
> > >
> > > mip6mnha1 Link encap:UNSPEC  HWaddr
> > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> > >           inet6 addr: 3ffe:80d0:ff03:4::1/64 Scope:Global
> > >           UP RUNNING NOARP  MTU:1460  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:0 errors:8 dropped:8 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> > >
> > > wlan0     Link encap:Ethernet  HWaddr 00:0F:3D:46:A6:25
> > >           inet addr:192.168.4.1  Bcast:192.168.4.255
> > > Mask:255.255.255.0
> > >           UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
> > >           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:6 errors:1 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:100
> > >           RX bytes:1968 (1.9 Kb)  TX bytes:2052 (2.0 Kb)
> > >           Interrupt:11 Base address:0x4000
> > >
> > >
> > >
> > > My Redhat AP Setting
> > >
> > > [root at localhost root]# iwconfig
> > > lo        no wireless extensions.
> > >
> > > sit0      no wireless extensions.
> > >
> > > eth0      no wireless extensions.
> > >
> > > wlan0     IEEE 802.11b  ESSID:"mipv6b"
> > > Nickname:"localhost.localdomain"
> > >           Mode:Master  Frequency:2.412GHz  Access Point:
> > > 00:01:03:88:62:96
> > >           Bit Rate=11Mb/s   Tx-Power:150 dBm   Sensitivity=1/3
> > >           Retry limit:8   RTS thr:off   Fragment thr:off
> > >           Encryption key:off
> > >           Power Management:off
> > >           Link Quality:0  Signal level:0  Noise level:0
> > >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> > >           Tx excessive retries:0  Invalid misc:46   Missed beacon:0
> > >
> > > br0       no wireless extensions.
> > >
> > > [root at localhost root]# ifconfig
> > > br0       Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> > >           inet addr:192.168.3.3  Bcast:192.168.3.255
> > > Mask:255.255.255.0
> > >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> > >           inet6 addr: 3ffe:80d0:ff03:3::3/0 Scope:Global
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:0 (0.0 b)  TX bytes:1050 (1.0 Kb)
> > >
> > > eth0      Link encap:Ethernet  HWaddr 00:50:BA:5F:61:56
> > >           inet addr:192.168.3.2  Bcast:192.168.3.255
> > > Mask:255.255.255.0
> > >           inet6 addr: 3ffe:80d0:ff03:3::2/64 Scope:Global
> > >           inet6 addr: fe80::250:baff:fe5f:6156/64 Scope:Link
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:100
> > >           RX bytes:0 (0.0 b)  TX bytes:1458 (1.4 Kb)
> > >           Interrupt:9 Base address:0xd000
> > >
> > > 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:232 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:12792 (12.4 Kb)  TX bytes:12792 (12.4 Kb)
> > >
> > > wlan0     Link encap:Ethernet  HWaddr 00:01:03:88:62:96
> > >           inet addr:192.168.3.4  Bcast:192.168.3.255
> > > Mask:255.255.255.0
> > >           inet6 addr: fe80::201:3ff:fe88:6296/64 Scope:Link
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:100
> > >           RX bytes:0 (0.0 b)  TX bytes:1212 (1.1 Kb)
> > >           Interrupt:9 Base address:0xd400
> > >
> > >
> > > Wireless testBed is almost like below:
> > >
> > >
> > >                                          |
> > >                                      192.168.1.1
> > >                                  3ffe:80f0:ff03:1::1
> > >                                         fxp0
> > >                             FreeBSD 4.10 Router(Vls Server 0.5.6)
> > >                             vr0                   rl0
> > >                        192.168.2.1            192.168.3.1
> > >                      3ffe:80f0:ff03:2::1      3ffe:80f0:ff03:3::1
> > >                              |                     |
> > >                              |                     |
> > >                              |                     |
> > >                            eth0                  eth0
> > >                    3ffe:80f0:ff03:2::2      3ffe:80f0:ff03:3::2
> > >                        192.168.2.2            192.168.3.2
> > >                    Linux PC Access Point      Linux PC Access Point
> > >                       (HOSTAP 0.13)          (HOSTAP 0.13)
> > >                              |                     |
> > >                              |                     |
> > >                             br0                   br0
> > >                         192.168.2.3            192.168.3.3
> > >                    3ffe:80f0:ff03:2::3      3ffe:80f0:ff03:3::3
> > >                              |                     |
> > >
> > >
> > >                              |                     |
> > >                           wlan0                 wlan0
> > >                         192.168.2.4            192.168.3.4
> > >                        essid:mipv6a           essid:mipv6b
> > >
> > >
> > >                           ----
> > >                          | MN |
> > >                           ----
> > >                 Roaming notebook (VLC player 0.7.2)
> > >               Linux Kernel 2.4.22 with MIPL 1.0
> > >             (Dlink Wireless  Card with acx100 driver)
> > >            192.168.4.1(Home address 3ffe:80d0:ff03:4::1)
> > >
> > >
> > >
> > > =====
> > > ???????????????????????? Happy & Healthy Always ! ^_^ !
> > > ???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
> > > ???????????? Buddhist Page:
> > > http://planet.time.net.my/SunwayCity/ceyong/ar> tikel.htm
> > >
> > > ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN
> > > Messenger:ceyong at hotmail.com
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail is new and improved - Check it out!
> > http://promotions.yahoo.com/new_mail
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
>
>
>=====
>???????????????????????? Happy & Healthy Always ! ^_^ !
>???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
>???????????? Buddhist Page: 
>http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
>ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at 
>hotmail.com
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail is new and improved - Check it out!
>http://promotions.yahoo.com/new_mail
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap





From amr  Fri Sep 24 11:45:03 2004
From: amr (amrnasr)
Date: Fri, 24 Sep 2004 20:45:03 +0200
Subject: Software Reset of the wireless card
Message-ID: <41546B2F.4030705@broadbandcentral.us>

Hi all,
Is there anyone who can tell me if there is a way for software resetting 
the radio card instead of rebooting of the linux system.
Regards,
Amr



From bruno.randolf  Fri Sep 24 08:02:10 2004
From: bruno.randolf (Bruno Randolf)
Date: Fri, 24 Sep 2004 17:02:10 +0200
Subject: Software Reset of the wireless card
In-Reply-To: <41546B2F.4030705@broadbandcentral.us>
References: <41546B2F.4030705@broadbandcentral.us>
Message-ID: <200409241702.14371.bruno.randolf@4g-systems.biz>

On Friday 24 September 2004 20:45, amrnasr wrote:
> Hi all,
> Is there anyone who can tell me if there is a way for software resetting
> the radio card instead of rebooting of the linux system.

iwpriv wlan0 reset 1

bruno
-------------- 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/20040924/726fbd1d/attachment.pgp 


From zhangho  Fri Sep 24 08:51:49 2004
From: zhangho (Hongwei Zhang)
Date: Fri, 24 Sep 2004 11:51:49 -0400
Subject: Software Reset of the wireless card
In-Reply-To: <41546B2F.4030705@broadbandcentral.us>
References: <41546B2F.4030705@broadbandcentral.us>
Message-ID: <41544295.1040301@cis.ohio-state.edu>

try "/etc/init.d/pcmcia restart".

Best,

Hongwei



amrnasr wrote:

> Hi all,
> Is there anyone who can tell me if there is a way for software 
> resetting the radio card instead of rebooting of the linux system.
> Regards,
> Amr
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>




From jt  Fri Sep 24 09:17:25 2004
From: jt (Jean Tourrilhes)
Date: Fri, 24 Sep 2004 09:17:25 -0700
Subject: Problem COnnecting AP from Mobile Node
In-Reply-To: <20040924052343.24990.qmail@web41012.mail.yahoo.com>
References: <C6D44AA99ECEB540A5498F15F92DA07DDD38FD@amperion01>
	<20040924052343.24990.qmail@web41012.mail.yahoo.com>
Message-ID: <20040924161725.GA29731@bougret.hpl.hp.com>

On Thu, Sep 23, 2004 at 10:23:43PM -0700, Yong Chu Eu (??????) wrote:
> Thanks for kindly advice,Another question:
> 
> since i have 2 AP,how do i set the routing(static) between 2 AP if the
> mobile node roaming between this 2 AP? 
> 
> Any idea?

	Real APs use bridging, at L2, and therefore you just need to
place them in the same subnet and connect them on the same network
with no router between them.

	Jean



From kahing  Fri Sep 24 10:40:21 2004
From: kahing (Ka-Hing Cheung)
Date: Fri, 24 Sep 2004 10:40:21 -0700
Subject: help width 0.2.4 -> 0.2.6
In-Reply-To: <000901c4a1a8$0f9c84b0$0d02a8c0@racunar01>
References: <004801c48373$549ba260$0100a8c0@racunar0d>
	<023c01c4a145$3fd1dcb0$0d02a8c0@racunar01>
	<d9823ac104092309143ba9999f@mail.gmail.com>
	<000901c4a1a8$0f9c84b0$0d02a8c0@racunar01>
Message-ID: <d9823ac10409241040519e1679@mail.gmail.com>

On Thu, 23 Sep 2004 22:01:06 +0200, hiphin <hiphin at cat-net.co.yu> wrote:
> uppsss...
> 
> Suse 9.1, yes it have, and I tryed, but it doesn't completly solve problem,
> ... it does't bring wlan configured (yes I have ifcfg-wlan... file), any
> other idea or I should put some script to auto configure wlan
> 
> thanks Ka-Hing
> 
> 

I don't know what ifcfg-wlan is, but you generally need to load
hostap, then the firmware for your card. After that iwconfig should
work, and you should be able to associate yourself to an accesspoint.

-khc



From gdamjan  Fri Sep 24 15:10:39 2004
From: gdamjan (Damjan)
Date: Sat, 25 Sep 2004 00:10:39 +0200
Subject: WEP and WPA?
In-Reply-To: <20040924020642.GE7360@jm.kir.nu>
References: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
	<20040924020642.GE7360@jm.kir.nu>
Message-ID: <20040924221039.GB2037@legolas.on.net.mk>

> The current version of hostapd does not support this kind of mixed
> configuration. In theory, this is possible configuration for WPA, but it
> would require some changes for hostapd to handle the STAs that do not
> use WPA (either provide keys with IEEE 802.1X or use staticly configured
> WEP keys).

Jouni, 
when WPA is used with hostapd What happens to the wifi frames that are
not WPA. hostapd will send EAPOL requests, but the client doesn't answer
them... what happens then? 
If the frames get dropped, what part of the code drops them?

-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From jaws  Fri Sep 24 16:28:30 2004
From: jaws (James Woo)
Date: Fri, 24 Sep 2004 16:28:30 -0700
Subject: Interesting issues with CCMP
Message-ID: <4154AD9E.7050004@dis.ricoh.com>

On Thu, Sep 16, 2004 at 07:36:25PM -0700, Jouni Malinen wrote:
>/ What kind of device do you use as the AP?
/>/
/It is a Linksys WAP54g.

Regards,
	Kyle.

Kyle & Jouni,

It's a Linksys WAP54g bug. It's not clearing the PwrMgt bit (bit 12) when constructing
the AAD. You're losing your multicast packets when PwrMgt bit is set. To become bug-compatible,
change line 818 in hostap_crypt_ccmp.c from
	aad[3] = pos[1] & 0xc7; to 	aad[3] = pos[1] & 0xe7;
and then your problem should go away.

James Woo

P.S. Linksys WAP54g has similar CCMP problem with fragmentation too.
It's clearing the fragment number when constructing the AAD. To verify the problem, you'll
see no data traffic when fragmentation is enabled (for example, fragmentation = 256).





From kyle  Fri Sep 24 17:08:34 2004
From: kyle (Kyle McMartin)
Date: Fri, 24 Sep 2004 20:08:34 -0400
Subject: Interesting issues with CCMP
In-Reply-To: <4154AD9E.7050004@dis.ricoh.com>
References: <4154AD9E.7050004@dis.ricoh.com>
Message-ID: <20040925000834.GC2257@roadwarrior.mcmartin.ca>

Hi James,

On Fri, Sep 24, 2004 at 04:28:30PM -0700, James Woo wrote:
> It's a Linksys WAP54g bug. It's not clearing the PwrMgt bit (bit 12) when 
> constructing
> the AAD. You're losing your multicast packets when PwrMgt bit is set. To 
> become bug-compatible,
> change line 818 in hostap_crypt_ccmp.c from
> 	aad[3] = pos[1] & 0xc7; to 	aad[3] = pos[1] & 0xe7;
> and then your problem should go away.
> 

Thanks!

> James Woo
> 
> P.S. Linksys WAP54g has similar CCMP problem with fragmentation too.
> It's clearing the fragment number when constructing the AAD. To verify the 
> problem, you'll
> see no data traffic when fragmentation is enabled (for example, 
> fragmentation = 256).
> 

Ick. I guess I'll have to hope for a firmware upgrade from linksys.

Thanks again,
	Kyle McMartin.



From jkmaline  Fri Sep 24 18:39:13 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 24 Sep 2004 18:39:13 -0700
Subject: Interesting issues with CCMP
In-Reply-To: <4154AD9E.7050004@dis.ricoh.com>
References: <4154AD9E.7050004@dis.ricoh.com>
Message-ID: <20040925013913.GA7354@jm.kir.nu>

On Fri, Sep 24, 2004 at 04:28:30PM -0700, James Woo wrote:

> It's a Linksys WAP54g bug. It's not clearing the PwrMgt bit (bit 12) when 
> constructing
> the AAD. You're losing your multicast packets when PwrMgt bit is set. To 
> become bug-compatible,
> change line 818 in hostap_crypt_ccmp.c from
> 	aad[3] = pos[1] & 0xc7; to 	aad[3] = pos[1] & 0xe7;
> and then your problem should go away.

That's interesting to know. I know there are interoperability issues
with some of the AAD masking, but this particular case was news to me.

> P.S. Linksys WAP54g has similar CCMP problem with fragmentation too.
> It's clearing the fragment number when constructing the AAD. To verify the 
> problem, you'll
> see no data traffic when fragmentation is enabled (for example, 
> fragmentation = 256).

That's a feature, though. WPA and WPA2 have different masks for seq_frag
(great!) and Broadcom used to implement CCMP for WPA correctly whereas
many other implementations (including Host AP driver) use the new
version for CCMP even when used with WPA (v1).

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Fri Sep 24 19:16:06 2004
From: jkmaline (Jouni Malinen)
Date: Fri, 24 Sep 2004 19:16:06 -0700
Subject: Big Endian problem for ixp435 found.
In-Reply-To: <20040924103034.GC13539@informatik.uni-rostock.de>
References: <20040923134528.GA13539@informatik.uni-rostock.de>
	<20040924020435.GD7360@jm.kir.nu>
	<20040924103034.GC13539@informatik.uni-rostock.de>
Message-ID: <20040925021606.GB7354@jm.kir.nu>

On Fri, Sep 24, 2004 at 12:30:34PM +0200, Gunter Burchardt wrote:

> Yes it is a alingment problem in SHA1Transform(). 
> 
>         static unsigned char workspace[64];
>         block = (CHAR64LONG16 *) workspace;
> 
> workspace[64] is NOT aligned at a 4 byte address. if you cast this to
> block (u32 l[16]) it gets problem with alignment!
> 
>         static u32 workspace[16];
>         block = (CHAR64LONG16 *) workspace;
> 
> Workspace is alligned at a 4 byte address. This works for me!

Thanks! The toolchain I used had 32-bit aligned workspace which explains
why this did not happen in my tests. I managed to reproduce this now by
adding one-byte static variable before workspace. The fix is now in CVS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From mstuff  Sat Sep 25 02:29:05 2004
From: mstuff (Morgan Read)
Date: Sat, 25 Sep 2004 21:29:05 +1200
Subject: 802.1x auth with wpa_supp?
In-Reply-To: <20040916041924.GG7360@jm.kir.nu>
References: <413D11D0.8050203@pl.net>
	<20040907025300.GB7392@jm.kir.nu>	<413D8C9A.9030707@pl.net>
	<20040916041924.GG7360@jm.kir.nu>
Message-ID: <41553A61.8030108@pl.net>

Hi
I've had some feed back from my uni on this.  Apparently the server cert 
was changed a few weeks back and it can no longer be verified (nice 
work).  Now people are turning the verification option off in windows & 
linux/xsupplicant - How do I turn verification off in wpa_supplicant?

Another suggestion was that I need to regenerate my key?  The one I'm 
using was generated for xsupplicant - can anybody give me a basic "one 
two" on using ssh-keygen or openssl to correctly generate a private key 
for wpa_supplicant?  I've had this in the back of my mind for a while 
but not found any info on it.

Copy of recent debug output attached FYI (interesting bit's 35-45 lines 
from end).

Regards,
Morgan.

###################################
[root at morgansmachine root]# wpa_supplicant -iwlan0
-c/etc/wpa_supplicant.conf -d Configuration file
'/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
Priority group 0
    id=0 ssid='uoa'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Disconnect event - remove keys
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=3):
      75 6f 61                                          uoa
Wireless event: cmd=0x8b19 len=12
Received 158 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:ed:99:37:c0 ssid='uoa' wpa_ie_len=0 rsn_ie_len=0
    skip - no WPA/RSN IE
    selected non-WPA AP 00:0d:ed:99:37:c0 ssid='uoa'
Trying to associate with 00:0d:ed:99:37:c0 (SSID='uoa' freq=2437 MHz)
Cancelling scan request
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
wpa_driver_hostap_set_drop_unencrypted: enabled=1
wpa_driver_hostap_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b04 len=12
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL frame received in disassociated state - dropped
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
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
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:99:37:c0
Association event - clear replay counter
Associated to a new BSS: BSSID=00:0d:ed:99:37:c0
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
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
RX EAPOL from 00:0d:ed:99:37:c0
Setting authentication timeout: 10 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=1 id=2
EAP: EAP entering state IDENTITY
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=10):
      45 43 5c 6d 72 65 61 30 30 35                     EC\mrea005
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RX EAPOL from 00:0d:ed:99:37:c0
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request method=25 id=3
EAP: EAP entering state GET_METHOD
EAP-PEAP: Phase2 type: MSCHAPV2
SSL: Trusted root certificate(s) loaded
SSL: Private key failed verification: error:140CB07C:SSL
routines:SSL_use_PrivateKey_file:bad ssl filetype
SSL - SSL error: error:140A30B1:SSL routines:SSL_check_private_key:no
certificate assigned
EAP-PEAP: Failed to initialize SSL.
EAP: Failed to initialize EAP method 25
EAP: EAP entering state METHOD
EAP::METHOD - method not selected
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
EAPOL: txSuppRsp - EAP response data not available
EAPOL: SUPP_BE entering state RECEIVE
WPA: EAPOL frame too short, len 46, expecting at least 99
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Signal 2 received - terminating
wpa_driver_hostap_deauthenticate
wpa_driver_hostap_reset: type=2
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
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_hostap_set_wpa: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
[root at morgansmachine root]#
###########################

Jouni Malinen wrote:
> On Tue, Sep 07, 2004 at 10:25:30PM +1200, Morgan Read wrote:
> 
> 
>>Well that was much more exciting!  At least to my eyes...
>>
>>I ran as you suggested per the hostap driver (not wext).
> 
> 
> Yes, indeed, this time the EAPOL negotiation was at least started.
> However, the AP/authentication server did not seem to like the identity
> response from the client.
> 
> 
>>EAP: Received EAP-Request method=1 id=2
>>EAP: EAP entering state IDENTITY
>>EAP: EAP-Request Identity data - hexdump_ascii(len=0):
>>EAP: using real identity - hexdump_ascii(len=10):
>>     45 43 2f 6d 72 65 61 30 30 35                     EC/mrea005
> 
> 
> Are you sure that is the current username? If "EC" is the domain part,
> that should most likely be EC\mrea005, not EC/mrea005.. 
> 
> 
>>Wireless event: cmd=0x8b15 len=20
>>Wireless event: new AP: 00:00:00:00:00:00
>>Setting scan request: 0 sec 100000 usec
>>EAPOL: External notification - portEnabled=0
>>EAPOL: SUPP_PAE entering state DISCONNECTED
> 
> 
> It looks like the AP disassociated the stations. This could have
> happened, e.g., because the authentication server rejected access to
> EC/mrea005 identity.
> 

-- 
Morgan Read
<mailto:mstuffATplDOTnet>



From sime  Sat Sep 25 03:38:31 2004
From: sime (Simon Males)
Date: Sat, 25 Sep 2004 20:38:31 +1000
Subject: Software Reset of the wireless card
In-Reply-To: <41546B2F.4030705@broadbandcentral.us>
References: <41546B2F.4030705@broadbandcentral.us>
Message-ID: <41554AA7.7070804@anticd.org>


amrnasr wrote:
> Hi all,
> Is there anyone who can tell me if there is a way for software resetting 
> the radio card instead of rebooting of the linux system.
> Regards,
> Amr

or you can try
# cardctl reset

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



From jkmaline  Sat Sep 25 23:16:52 2004
From: jkmaline (Jouni Malinen)
Date: Sat, 25 Sep 2004 23:16:52 -0700
Subject: Fix PRISM2_IO_DEBUG - bad pointer
In-Reply-To: <20040908175843.GA7693@glines.org>
References: <20040908175843.GA7693@glines.org>
Message-ID: <20040926061652.GA22235@jm.kir.nu>

On Wed, Sep 08, 2004 at 10:58:43AM -0700, Mark Glines wrote:

> I just noticed PRISM2_IO_DEBUG doesn't work.  This patch gets it
> working again.  I checked the development CVS snapshot, looks like
> its still broken there.

Thanks! Applied into both branches. In addition, I fixed the function
below this one since both were using the old way of getting the pointer
to local data.

-- 
Jouni Malinen                                            PGP id EFC895FA



From wk-hostap  Sun Sep 26 06:52:54 2004
From: wk-hostap (Wilfried Klaebe)
Date: Sun, 26 Sep 2004 15:52:54 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040909103335.GA13259@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
	<20040909103335.GA13259@kaos.in-kiel.de>
Message-ID: <20040926135253.GA12920@kaos.in-kiel.de>

Am Thu, Sep 09, 2004 at 12:33:35PM +0200 schrieb Wilfried Klaebe:
[...]
> > > ARP requests incoming on wlan0, but not showing up on br0.
> > > 
> > > I also tried it the other way round: If I try to ping the laptop on the
> > > WLAN, I can see the ARP requests going out on br0 and then eth0, but not
> > > wlan0.
[...]
> At the moment I'm trying to understand what happens after netif_rx() in
> the upper layers in linux... I hope to find the problem (or at least
> the solution) there. The packets do arrive in the upper layers correctly,
> else tcpdump would not be able to see them, but then something seems to
> hinder them from arriving at the bridge.

I think I found it. The packets are dropped, because wlan0 is in state
BR_STATE_DISABLED. This is because netif_carrier_ok() returns false for
wlan0. This is because at HW initialisation netif_carrier_down() is
called (only occurrence in hostap_hw.c), and nowhere later
netif_carrier_up() is called. There are two occurrences in
hostap_info.c, but none of them showed up in my logs when I put some
printks beside them.

So far, I have no idea where changes should be made, only that they are
necessary...

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From xinwenfu  Sun Sep 26 14:25:15 2004
From: xinwenfu (Xinwen Fu)
Date: Sun, 26 Sep 2004 16:25:15 -0500 (CDT)
Subject: how to turn off CSMA of wireless cards?
Message-ID: <Pine.GSO.4.58.0409261621260.7893@unix.cs.tamu.edu>

Hi,
	Is there a way turn off CSMA of wireless cards? That is, I wish
that a wireless card could send out packets at will. Just want to check
how much the interference (destruction) will be in reality.

	Thanks!

Xinwen Fu



From jkmaline  Sun Sep 26 23:07:26 2004
From: jkmaline (Jouni Malinen)
Date: Sun, 26 Sep 2004 23:07:26 -0700
Subject: Relicensing hostapd under dual GPL/BSD license
In-Reply-To: <20040921045422.GG7354@jm.kir.nu>
References: <20040921045422.GG7354@jm.kir.nu>
Message-ID: <20040927060726.GB7370@jm.kir.nu>

On Mon, Sep 20, 2004 at 09:54:22PM -0700, Jouni Malinen wrote:

> There has been some discussion on using hostapd with *BSD. One of the
> question is on the used license. I'm looking into relicensing hostapd
> under dual GPL/BSD license, i.e., adding BSD to the current license in
> the same way as core code in wpa_supplicant is released.

Thank you to people who have contributed patches to hostapd. I received
permission to relicense changes under dual GPL/BSD license and
consequently, I believe that all parts of hostapd are now covered by
this dual license. This means that 0.3.0 release is likely to be the
first dual licensed version of hostapd.

For future contirutions to hostapd (and wpa_supplicant for that matter),
I would prefer to receive them under a license that allows integration
into dual licensed code base. The easiest way for this is to use
identical dual GPL/BSD license. Other options are considered on case by
case basis, but I'm likely to require a license that is compatible with
both GPL and BSD for contributions to core code in hostapd and
wpa_supplicant.

One exception area for dual GPL/BSD license is the driver interface
code (driver_*.c). Prefered license for them is also dual GPL/BSD, but
I'm more willing to use other licenses to make it easier to integrate
interface code from external sources into my CVS tree. This may add some
complexity for binary distributions which may have to exclude some of
the driver interfaces unless a compatible license (e.g., GPL in case
of current wpa_supplicant CVS tree) is suitable for the distribution.
Each driver interface code can be easily excluded from the build, so
this should not be a major problem.

-- 
Jouni Malinen                                            PGP id EFC895FA



From Actinium  Mon Sep 27 00:41:11 2004
From: Actinium (Actinium at iocaine.com)
Date: Mon, 27 Sep 2004 15:41:11 +0800
Subject: Problem with WPA-PSK - WPA Group keyerror ? 
In-Reply-To: <20040925093124.398DF917@mail.iocaine.com>
References: <20040925093124.398DF917@mail.iocaine.com>
Message-ID: <4157C417.2050706@actinium.org>

I try to use hostapd with configuration as follow:
ssid=test
wpa=1
wpa_passphrase=secretpassphrase
wpa_key_mgmt=WPA-PSK 
wpa_pairwise=TKIP
wpa_group_rekey=600
wpa_gmk_rekey=86400

the dump file for hostapd as follow:-
Configuration file: hostapd.conf
Opening raw packet socket for ifindex 62
Using interface wlan0ap with hwaddr 00:60:b3:8b:ea:0b and ssid 'test'
WPA: group state machine entering state GTK_INIT
GMK - hexdump(len=32): 08 3d c7 1c bc e6 2b eb f5 3e ed 20 2d ee 40 81 
43 9e a3 10 80 7b db 89 0a 23 19 20 22 82 10 ab
GTK - hexdump(len=32): df a6 67 e6 3d d3 47 36 96 54 a3 9e 92 9b 33 ec 
7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
WPA: group state machine entering state SETKEYSDONE
Flushing old station entries
Deauthenticate all stations
mgmt::auth
authentication: STA=00:60:b3:8c:49:9c auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:60:b3:8c:49:9c auth_alg=0 
auth_transaction=2 resp=0
MGMT (TX callback) ACK
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:60:b3:8c:49:9c capab_info=0x11 
listen_interval=10
  new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITIALIZE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state IDLE
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITPSK
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=95 - 
ack=1
DATA
IEEE 802.1X: 123 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=119
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 38 18 ea 72 5e 61 4f 2d a3 4d 81 da 4b db 0f 7b 
7b 98 69 da 1e 7e e5 59 15 62 fc 1f 47 08 96 0e
PTK - hexdump(len=64): 97 7d 1d 2c d6 a0 15 60 ac b4 17 e0 ba f4 4e 20 
bd 0d 51 bb 16 22 a8 20 d7 40 d8 6c 55 a7 05 84 08 ec 2f 3d bb 7f 97 59 
78 c8 60 28 a9 00 22 3f 93 af 77 32 7a f1 8d 27 e1 50 5b 88 82 c4 9b 2e
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITNEGOTIATING
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=119 - 
ack=1
DATA
IEEE 802.1X: 99 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=95
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITDONE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state KEYERROR
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state DISCONNECT
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state IDLE
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state DISCONNECTED
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITIALIZE
Failed to set encryption.
Could not set station flags for kernel driver.
Could not set station flags for kernel driver.
Could not remove station from kernel driver.
DATA (TX callback) ACK
mgmt::auth
authentication: STA=00:60:b3:8c:49:9c auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:60:b3:8c:49:9c auth_alg=0 
auth_transaction=2 resp=0
MGMT (TX callback) ACK
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:60:b3:8c:49:9c capab_info=0x11 
listen_interval=10
  new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITIALIZE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state IDLE
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITPSK
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=95 - 
ack=1
DATA
IEEE 802.1X: 123 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=119
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 38 18 ea 72 5e 61 4f 2d a3 4d 81 da 4b db 0f 7b 
7b 98 69 da 1e 7e e5 59 15 62 fc 1f 47 08 96 0e
PTK - hexdump(len=64): 10 03 a2 2f c0 e4 60 e1 4e 10 d2 2b 25 82 0c 05 
27 2a 52 0f 6b e5 04 5c 6b c2 d8 a4 2a 29 0f c1 1b d3 72 71 d6 8d a5 a9 
b5 c2 a3 03 6f d7 e2 3e 49 91 4b 8b 34 26 53 70 2b 67 85 c2 a6 c6 1b eb
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITNEGOTIATING
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=119 - 
ack=1
DATA
IEEE 802.1X: 99 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=95
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITDONE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state KEYERROR
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state DISCONNECT
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state IDLE
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state DISCONNECTED
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITIALIZE
Failed to set encryption.
Could not set station flags for kernel driver.
Could not set station flags for kernel driver.
Could not remove station from kernel driver.
DATA (TX callback) ACK
mgmt::auth
authentication: STA=00:60:b3:8c:49:9c auth_alg=0 auth_transaction=1 
status_code=0 wep=0
  New STA
authentication reply: STA=00:60:b3:8c:49:9c auth_alg=0 
auth_transaction=2 resp=0
MGMT (TX callback) ACK
mgmt::auth cb
mgmt::assoc_req
association request: STA=00:60:b3:8c:49:9c capab_info=0x11 
listen_interval=10
  new AID 1
MGMT (TX callback) ACK
mgmt::assoc_resp cb
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITIALIZE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state IDLE
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state AUTHENTICATION2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state INITPSK
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKSTART
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=95 - 
ack=1
DATA
IEEE 802.1X: 123 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=119
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): 38 18 ea 72 5e 61 4f 2d a3 4d 81 da 4b db 0f 7b 
7b 98 69 da 1e 7e e5 59 15 62 fc 1f 47 08 96 0e
PTK - hexdump(len=64): e8 43 76 3a d2 97 94 13 f9 7e 87 fa c7 cb 42 ac 
0e 33 a2 7d 5d ba 1c f0 1d ad 5d 8a 7b 99 7e e6 91 b9 35 ee 6b f0 dc 25 
f8 e7 8d 9f ec ea 6a 42 a8 37 db 73 d3 7b bf b3 b0 48 87 84 d1 70 96 f1
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITNEGOTIATING
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=119 - 
ack=1
DATA
IEEE 802.1X: 99 bytes from 00:60:b3:8c:49:9c
   IEEE 802.1X: version=1 type=3 length=95
WPA: 00:60:b3:8c:49:9c WPA_PTK entering state PTKINITDONE
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
WPA: 00:60:b3:8c:49:9c WPA_PTK_GROUP entering state REKEYNEGOTIATING
Plaintext EAPOL-Key Key Data - hexdump(len=32): df a6 67 e6 3d d3 47 36 
96 54 a3 9e 92 9b 33 ec 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb
DATA (TX callback) ACK
IEEE 802.1X: 00:60:b3:8c:49:9c TX status - version=1 type=3 length=127 - 
ack=1
Signal 2 received - terminating
Removing station 00:60:b3:8c:49:9c
Flushing old station entries
Deauthenticate all stations

any idea what happend ? Thank you very very much...

Regards,
Lim Yew Chai




From cwevans  Mon Sep 27 07:00:18 2004
From: cwevans (Chris Evans)
Date: Mon, 27 Sep 2004 07:00:18 -0700
Subject: Problem with WPA-PSK - WPA Group keyerror ? 
In-Reply-To: <4157C417.2050706@actinium.org>
References: <20040925093124.398DF917@mail.iocaine.com>
	<4157C417.2050706@actinium.org>
Message-ID: <90930EB8-108D-11D9-B504-000A95B1BFFA@acm.org>

What version of firmware is your card using?

And what OS/card is trying to connect?

On Sep 27, 2004, at 12:41 AM, Actinium at iocaine.com:Lim Yew Chai wrote:

> I try to use hostapd with configuration as follow:
> ssid=test
> wpa=1
> wpa_passphrase=secretpassphrase
> wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP
> wpa_group_rekey=600
> wpa_gmk_rekey=86400
>
> the dump file for hostapd as follow:-
> Configuration file: hostapd.conf
> Opening raw packet socket for ifindex 62
> Using interface wlan0ap with hwaddr 00:60:b3:8b:ea:0b and ssid 'test'
> WPA: group state machine entering state GTK_INIT
> GMK - hexdump(len=32): 08 3d c7 1c bc e6 2b eb f5 3e ed 20 2d ee 40 81 
> 43 9e a3 10 80 7b db 89 0a 23 19 20 22 82 10 ab
> GTK - hexdump(len=32): df a6 67 e6 3d d3 47 36 96 54 a3 9e 92 9b 33 ec 
> 7d b2 79 4d 0a c1 03 1d eb 56 f9 87 cb 83 3e bb

.....

> Signal 2 received - terminating
> Removing station 00:60:b3:8c:49:9c
> Flushing old station entries
> Deauthenticate all stations
>
> any idea what happend ? Thank you very very much...
>
> Regards,
> Lim Yew Chai
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
--
       -+--++---+++----++++-----+++++-----++++----+++---++--+-
      ___
  _.-|   |          |\__/,|   (`\      | Chris Evans
{   |   |          |o o  |__ _) )     |
  "-.|___|        _.( T   )  `  /      | cwevans at acm.org
   .--'-`-.     _((_ `^--' /_<  \      |
.+|______|__.-||__)`-'(((/  (((/      |  "Any technology distinguishable
                                       |  from magic, is not advanced
   Nika plays with a computer mouse    |  enough" -- Gregory Benford
       BY: Mike Rosulek                |
          http://showcase.netins.net/web/mikewrld/ascii/




From kevin.he  Mon Sep 27 11:35:50 2004
From: kevin.he (Kevin He)
Date: Mon, 27 Sep 2004 14:35:50 -0400
Subject: Support for Wlan SD card ?
Message-ID: <50ad22fb04092711351d46b41e@mail.gmail.com>

I'm wondering if there is support for Wlan SDIO card from hostap driver ?
If not yet I'm wondering how much work it is to add SDIO bus support to
the driver from developer's point of view ?

I've found one of such cards from Sandisk which is used by PocketPC
http://www.elx.com.au/item/SDWSDB000

Thanks
Kevin



From HostAP-Research  Mon Sep 27 12:44:31 2004
From: HostAP-Research (AP-Research)
Date: Mon, 27 Sep 2004 14:44:31 -0500 (CDT)
Subject: Support for Wlan SD card ?
In-Reply-To: <50ad22fb04092711351d46b41e@mail.gmail.com>
References: <50ad22fb04092711351d46b41e@mail.gmail.com>
Message-ID: <32990.67.174.81.186.1096314271.squirrel@67.174.81.186>


<quote who="Kevin He">
> I'm wondering if there is support for Wlan SDIO card from hostap driver ?

There aren't any whitepapers on the SanDisk website which cover the
SDWSDB-xxx-xxx.  I can't determine what chipset it uses, but I'm almost
certain it's NOT Prism.  In that case it wouldn't be supported by Host AP.


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



From Actinium  Mon Sep 27 18:15:43 2004
From: Actinium (Actinium at iocaine.com)
Date: Tue, 28 Sep 2004 09:15:43 +0800
Subject: Problem with WPA-PSK - WPA Group keyerror ? ( Lim Yew Chai )
In-Reply-To: <20040927194930.E1848629@mail.iocaine.com>
References: <20040927194930.E1848629@mail.iocaine.com>
Message-ID: <4158BB3F.2030605@actinium.org>

   

What version of firmware is your card using?

--my card is using 1.8.2 station firmware

And what OS/card is trying to connect?

--i'm trying to associate using OS ( Win 2000 ) , WPA Assistant .

:)





From jkmaline  Mon Sep 27 19:49:47 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 19:49:47 -0700
Subject: Problem with WPA-PSK - WPA Group keyerror ? ( Lim Yew Chai )
In-Reply-To: <4158BB3F.2030605@actinium.org>
References: <20040927194930.E1848629@mail.iocaine.com>
	<4158BB3F.2030605@actinium.org>
Message-ID: <20040928024947.GB7370@jm.kir.nu>

On Tue, Sep 28, 2004 at 09:15:43AM +0800, "Actinium at iocaine.com" wrote:

> And what OS/card is trying to connect?
> 
> --i'm trying to associate using OS ( Win 2000 ) , WPA Assistant .

Have you been able to use that client successfully with other APs? What
wlan card and what driver version are you using? I have never used WPA
Assistant and I have not heard of any interop tests with it before. Can
you use any other client to verify whether the AP works correctly?

The log file you sent showed a successful 4-way handshake, but the first
encrypted packet (in group key handshake) did not receive a reply from
the client. Please check 'dmesg' output from the host running hostapd
for possible decryption errors.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep 27 20:02:11 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 20:02:11 -0700
Subject: how to turn off CSMA of wireless cards?
In-Reply-To: <Pine.GSO.4.58.0409261621260.7893@unix.cs.tamu.edu>
References: <Pine.GSO.4.58.0409261621260.7893@unix.cs.tamu.edu>
Message-ID: <20040928030211.GC7370@jm.kir.nu>

On Sun, Sep 26, 2004 at 04:25:15PM -0500, Xinwen Fu wrote:

> 	Is there a way turn off CSMA of wireless cards? That is, I wish
> that a wireless card could send out packets at will. Just want to check
> how much the interference (destruction) will be in reality.

I haven't tested this myself, but some of the BBP configuration
registers may allow you to disable CCA. If you happen to have or can
find a data sheet for the BBP (e.g., HFA3861B or HFA3863), search for
CCA mode and go through the configuration registers. Another questions
is, whether the station firmware allows you to do this without restoring
the register back to its original value..

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep 27 20:04:29 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 20:04:29 -0700
Subject: basic_rates and oper_rates problem
In-Reply-To: <4152DE5F.8090607@spymac.com>
References: <4152DE5F.8090607@spymac.com>
Message-ID: <20040928030429.GD7370@jm.kir.nu>

On Thu, Sep 23, 2004 at 10:31:59PM +0800, slimmerz wrote:

> 1. i am bit confuse about the parameter basic_rates and oper_rates 
> settings with iwpriv, what is their different?

oper_rates: all rates that are allowed for transmit to any station

basic_rates: all rates that are allowed for broadcast/multicast packets;
in addition, STAs are required to support all these rates in order to be
abe to associate with the AP

basic_rates is a subset of oper_rates, i.e., all basic_rates must also
be in oper_rates.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep 27 20:05:28 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 20:05:28 -0700
Subject: Fragmentation.
In-Reply-To: <000b01c4a175$f3976f50$4d00a8c0@Lifebook>
References: <000b01c4a175$f3976f50$4d00a8c0@Lifebook>
Message-ID: <20040928030528.GE7370@jm.kir.nu>

On Thu, Sep 23, 2004 at 11:02:24PM +0900, Donghyuk Woo wrote:

> However, I'd like to send frames that is longer than 1500 bytes through IEEE
> 802.11 WLAN.
> Is this possible? If yes, what should I do?

You will need to set the interface MTU to larger value to be able to
send larger packets. This can be done, e.g., with 'ifconfig wlan0 mtu
<value>'.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Mon Sep 27 20:09:53 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 20:09:53 -0700
Subject: WEP and WPA?
In-Reply-To: <20040924221039.GB2037@legolas.on.net.mk>
References: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
	<20040924020642.GE7360@jm.kir.nu>
	<20040924221039.GB2037@legolas.on.net.mk>
Message-ID: <20040928030953.GF7370@jm.kir.nu>

On Sat, Sep 25, 2004 at 12:10:39AM +0200, Damjan wrote:

> when WPA is used with hostapd What happens to the wifi frames that are
> not WPA. hostapd will send EAPOL requests, but the client doesn't answer
> them... what happens then? 
> If the frames get dropped, what part of the code drops them?

I'm not sure what you mean with "wifi frames that are not WPA". If the
client does not reply to EAPOL-Key packets (i.e., WPA 4-Way Handshake),
it will be deauthenticated after a short timeout. No data frames are
allowed from STAs that have not completed configured authentication.
There are number of places in the driver code that do this filtering.
These are mainly in hostap_80211_rx.c. Search, e.g., for
"drop_unencrypted" and"authorized".

-- 
Jouni Malinen                                            PGP id EFC895FA



From gdamjan  Mon Sep 27 21:16:17 2004
From: gdamjan (Damjan)
Date: Tue, 28 Sep 2004 06:16:17 +0200
Subject: WEP and WPA?
In-Reply-To: <20040928034857.GI7370@jm.kir.nu>
References: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
	<20040924020642.GE7360@jm.kir.nu>
	<20040924221039.GB2037@legolas.on.net.mk>
	<20040928030953.GF7370@jm.kir.nu>
	<20040928033540.GA26740@legolas.on.net.mk>
	<20040928034857.GI7370@jm.kir.nu>
Message-ID: <20040928041617.GA27868@legolas.on.net.mk>

> > So the dropping is in software. I'm thinking of a feature, not to drop
> > these frames, but to mark them as non-authorized (*) so that I could
> > process them with iptables for ex.
> > 
> > (*) is it possible to have a separate interface for authenticated
> > clients, and separate for non-auth., say wlanx0 and wlan0?
> > That way I could still REDIRECT non-auth users with iptables and show
> > them some info without allowing them more access.
> 
> Yes, that should be possible. You may have some problems in convincing
> clients to associate with plaintext and and WPA with one AP
> configuration, since these modes have a conflict on the Privacy bit in
> the beacon frames. If the non-WPA clients are using WEP, this kind of
> combination should work fine.

Aha, "Privacy bit in the beacon frames", thats why someone suggested
that an AP should support two SSID's in order for this to work.

Does/can hostap support two SSID's with different settings?


ps.
by mistake the previous messages didn't go to the mail list.

-- 
damjan | ??????
This is my jabber ID --> damjan at bagra.net.mk <-- not my mail address!!!



From jkmaline  Mon Sep 27 21:32:55 2004
From: jkmaline (Jouni Malinen)
Date: Mon, 27 Sep 2004 21:32:55 -0700
Subject: WEP and WPA?
In-Reply-To: <20040928041617.GA27868@legolas.on.net.mk>
References: <200409230815.i8N8FYH2042875@musashi.et.bocholt.fh-gelsenkirchen.de>
	<20040924020642.GE7360@jm.kir.nu>
	<20040924221039.GB2037@legolas.on.net.mk>
	<20040928030953.GF7370@jm.kir.nu>
	<20040928033540.GA26740@legolas.on.net.mk>
	<20040928034857.GI7370@jm.kir.nu>
	<20040928041617.GA27868@legolas.on.net.mk>
Message-ID: <20040928043255.GJ7370@jm.kir.nu>

On Tue, Sep 28, 2004 at 06:16:17AM +0200, Damjan wrote:

> Aha, "Privacy bit in the beacon frames", thats why someone suggested
> that an AP should support two SSID's in order for this to work.
> 
> Does/can hostap support two SSID's with different settings?

The current station firmware code makes this pretty difficult because it
takes care of Probe Request processing and does not internally support
multiple SSIDs. In theory, one could try rotating SSIDs, but that is not
very nice solution for this. Anyway, multiple SSIDs do not necessarily
help with the Privacy bit because most implementations would share the
same beacon frame with all the SSIDs.

-- 
Jouni Malinen                                            PGP id EFC895FA



From info  Tue Sep 28 00:29:00 2004
From: info (info at dettorre.com)
Date: Tue, 28 Sep 2004 09:29:00 +0200
Subject: Hostap, Freeradius and TLS
Message-ID: <200409280729.i8S7T0SH031846@vz1060.evanzo-server.de>


Hello,

I\'m trying to set up Freeradius 1.0.1 with HostAP 0.2.4 and TLS. Setup up of Freeradius Server and HostAp went well. My Problem is when I start hostapd I get the following error:

pc9:~ # hostapd -dd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
Opening raw packet socket for ifindex 22
Using interface wlan0ap with hwaddr 00:09:5b:91:a2:68 and ssid \'testing\'
wlan0: RADIUS Authentication server 127.0.0.1:1812
Default WEP key - hexdump(len=5): 6d 69 44 d6 20
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
Failed to set encryption.
Could not set WEP encryption.
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Could not disable PrivacyInvoked for interface wlan0
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Could not remove generic information element from interface wlan0
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported

my hostapd.conf looks like this:

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

# Require IEEE 802.1X authorization
ieee8021x=1

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

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

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

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

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

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

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

when I try to set wep encryption for wlan0ap I get:

pc9:~ # iwconfig wlan0ap key 12345
Error for wireless request \"Set Encode\" (8B2A) :
    SET failed on device wlan0ap ; No such device.

The Firmware of my Netgear MA311 Card is:

pc9:~/hostap-utils-0.2.4 # ./hostap_diag wlan0
Host AP driver diagnostics information for \'wlan0\'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.5.6 (station firmware)


I would appreciate if someone of the list could give me a hint to solve this.

Thank You very much.

Regards
D\'Ettorre Sandro



From cijoml  Tue Sep 28 01:51:18 2004
From: cijoml (Bc. Michal Semler)
Date: Tue, 28 Sep 2004 10:51:18 +0200
Subject: how to get firmware FROM card?
Message-ID: <200409281051.18640.cijoml@volny.cz>

Hi,

I got card xi-330:

kernel:ident:nic h/w:id=0x800c 1.0.0
kernel:ident:pri f/w:id=0x15 1.1.4
kernel:ident:sta f/w:id=0x1f 1.8.3 

It's ids looks like my xi-325:

wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.0

So I would like to get firmware FROM 330 and flash it into 325 - How to get 
it?

All around the world are only howtos how to reflash card, but non how to get 
firmware from it.

Thanks guys

M.



From wk-hostap  Tue Sep 28 02:59:06 2004
From: wk-hostap (Wilfried Klaebe)
Date: Tue, 28 Sep 2004 11:59:06 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040926135253.GA12920@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
	<20040909103335.GA13259@kaos.in-kiel.de>
	<20040926135253.GA12920@kaos.in-kiel.de>
Message-ID: <20040928095906.GA16999@kaos.in-kiel.de>

Am Sun, Sep 26, 2004 at 03:52:54PM +0200 schrieb Wilfried Klaebe:
[...]
> > > > ARP requests incoming on wlan0, but not showing up on br0.
[...]
> I think I found it. The packets are dropped, because wlan0 is in state
> BR_STATE_DISABLED. This is because netif_carrier_ok() returns false for
> wlan0. This is because at HW initialisation netif_carrier_down() is
> called (only occurrence in hostap_hw.c), and nowhere later
> netif_carrier_up() is called. There are two occurrences in
> hostap_info.c, but none of them showed up in my logs when I put some
> printks beside them.
> 
> So far, I have no idea where changes should be made, only that they are
> necessary...

Maybe I should add that the check for netif_carrier_ok() in the linux
bridging code was added in 2.6.8-rc3 and so this problem won't show up
in previous versions. I don't know if it has gone into 2.4.

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From jkmaline  Tue Sep 28 06:31:02 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Sep 2004 06:31:02 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040928095906.GA16999@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
	<20040909103335.GA13259@kaos.in-kiel.de>
	<20040926135253.GA12920@kaos.in-kiel.de>
	<20040928095906.GA16999@kaos.in-kiel.de>
Message-ID: <20040928133102.GA7370@jm.kir.nu>

On Tue, Sep 28, 2004 at 11:59:06AM +0200, Wilfried Klaebe wrote:
> Am Sun, Sep 26, 2004 at 03:52:54PM +0200 schrieb Wilfried Klaebe:
> > I think I found it. The packets are dropped, because wlan0 is in state
> > BR_STATE_DISABLED. This is because netif_carrier_ok() returns false for
> > wlan0. This is because at HW initialisation netif_carrier_down() is
> > called (only occurrence in hostap_hw.c), and nowhere later
> > netif_carrier_up() is called. There are two occurrences in
> > hostap_info.c, but none of them showed up in my logs when I put some
> > printks beside them.

> Maybe I should add that the check for netif_carrier_ok() in the linux
> bridging code was added in 2.6.8-rc3 and so this problem won't show up
> in previous versions. I don't know if it has gone into 2.4.

Interesting.. I think I tested this with 2.6.8.1 which is newer than
2.6.8-rc3.. In addition, I remember verifying that the
netif_carrier_on() is being called; although this might have been only
for client modes. Then again, that LinkStatus even should be arriving
also in Master mode.

I will need to take a bit closer look at this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From nondito  Tue Sep 28 10:56:57 2004
From: nondito (nondito)
Date: Tue, 28 Sep 2004 10:56:57 -0700 (PDT)
Subject: Fragmentation.
Message-ID: <20040928175657.47618.qmail@web40625.mail.yahoo.com>

If the fragmentation is set to 512 (iwconfig wlan0
frag 512) and mtu to be set to 1500 (ifconfig wlan0
mtu 1500), what will be the layer 2 frame size between
an accesspoint (master) and client (managed)?

How is fragmentation related to mtu on wireless
layer-2?

Thanks in advance.
> 
> --- Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> 
> > On Thu, Sep 23, 2004 at 11:02:24PM +0900, Donghyuk
> > Woo wrote:
> > 
> > > However, I'd like to send frames that is longer
> > than 1500 bytes through IEEE
> > > 802.11 WLAN.
> > > Is this possible? If yes, what should I do?
> > 
> > You will need to set the interface MTU to larger
> > value to be able to
> > send larger packets. This can be done, e.g., with
> > 'ifconfig wlan0 mtu
> > <value>'.
> > 
> > -- 
> > Jouni Malinen                                     
>  
> >     PGP id EFC895FA
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> > 
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We
> finish.
> http://promotions.yahoo.com/new_mail 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail



From jkmaline  Tue Sep 28 20:41:22 2004
From: jkmaline (Jouni Malinen)
Date: Tue, 28 Sep 2004 20:41:22 -0700
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040926135253.GA12920@kaos.in-kiel.de>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu>
	<20040909103335.GA13259@kaos.in-kiel.de>
	<20040926135253.GA12920@kaos.in-kiel.de>
Message-ID: <20040929034122.GC7376@jm.kir.nu>

On Sun, Sep 26, 2004 at 03:52:54PM +0200, Wilfried Klaebe wrote:

> I think I found it. The packets are dropped, because wlan0 is in state
> BR_STATE_DISABLED. This is because netif_carrier_ok() returns false for
> wlan0. This is because at HW initialisation netif_carrier_down() is
> called (only occurrence in hostap_hw.c), and nowhere later
> netif_carrier_up() is called. There are two occurrences in
> hostap_info.c, but none of them showed up in my logs when I put some
> printks beside them.

> So far, I have no idea where changes should be made, only that they are
> necessary...

netif_carrier was only supposed to be used in client mode, but this was
indeed broken at least with some firmware versions. I think I tested
this with some firmware version when the change was added to CVS and it
seemed to be working in Master mode.. Anyway, I was able to reproduce
the problem case easily with the current firmware release and the devel
snapshot of the driver.

I committed couple of changes to disable netif_carrier_off() calls in
non-client modes. In addition, SIOCSIWMODE handler is now calling
netif_carrier_on() when moving to non-client mode.

I have not tested all combinations yet and would appreciate it if you
could test the current development snapshot and report whether it works
in your setup. I did not yet merge the changes to stable branch, but I
will do this before 0.2.5 release if these seem to fix the problem.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ceyong  Wed Sep 29 00:18:47 2004
From: ceyong (Yong Chu Eu Ñî×ÓÓÓ)
Date: Wed, 29 Sep 2004 00:18:47 -0700 (PDT)
Subject: Fwd: [vlc] Re: [streaming] Re: video image distorted
Message-ID: <20040929071847.58034.qmail@web41013.mail.yahoo.com>

anyone can help on this since the video streaming is from vls server
throught HOSTAP based AP before reach Mobile Node? i test on wired peer to
peer,everything fine but test on wireless, a lot packet drop.


Note: forwarded message attached.


=====
???????????????????????? Happy & Healthy Always ! ^_^ !
???????? Homepage:http://planet.time.net.my/sunwaycity/ceyong
???????????? Buddhist Page: http://planet.time.net.my/SunwayCity/ceyong/artikel.htm
ICQ:16994867/ Yahoo Messenger ID:ceyong /MSN Messenger:ceyong at hotmail.com


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
-------------- next part --------------
An embedded message was scrubbed...
From: "Yong Chu Eu (??????)" <ceyong at yahoo.com>
Subject: [vlc] Re: [streaming] Re: video image distorted
Date: Tue, 28 Sep 2004 22:58:38 -0700 (PDT)
Size: 4267
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20040929/ee71026a/attachment.eml 


From s_fakhoury  Wed Sep 29 07:26:02 2004
From: s_fakhoury (Sami FAKHOURY)
Date: Wed, 29 Sep 2004 16:26:02 +0200
Subject: Using Aux ports to send Control frames...
Message-ID: <BAY16-F30S8YV2btIXw00009a88@hotmail.com>

Hi,

Actually Im kind of a beginner in hostap...I red an interesting article 
where they stated that it's possible to send control frames with hostap 
using Aux ports I admit it wasn't so clear for me...

Can anyone help me understanding this method? can u plz send a code or 
indicate how to disable AUX ports in hostap and how to read or write from 
it...

Documents that describes the functionalities of AUX ports or the method 
reffered to would help me in my research...

Thx a lot for ur help guys
Sam

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963




From kickdown  Wed Sep 29 07:50:29 2004
From: kickdown (Stefan Winter)
Date: Wed, 29 Sep 2004 16:50:29 +0200
Subject: wlan0sta and wlan0ap
Message-ID: <200409291650.29410.kickdown@web.de>

Hello,

about a year ago there were some postings about being in Master mode and 
simultaneously with a logical device wlanXsta in Managed mode. At some 
posting in June last year Jouni mentioned that there was some experimental 
code with old firmware that allowed this simultaneous operation. I am 
speaking of posting:
http://lists.shmoo.com/pipermail/hostap/2003-June/003084.html

I wonder how the status of that experiment is? Did it ever leave its 
experimental state? And what specifically does "old" firmware mean? I have a 
card in possession that is an original "Lucent Orinoco" (really one of the 
first 11b ever) with a firmware of an alternate versioning scheme (something 
like 6.72 firmware or so). Would that be old enough? And is hostapd still 
capable of that sort of thing?

Greetings,

Stefan Winter




From s_fakhoury  Wed Sep 29 07:48:22 2004
From: s_fakhoury (Sami FAKHOURY)
Date: Wed, 29 Sep 2004 16:48:22 +0200
Subject: Using Aux ports to send Control frames...
Message-ID: <BAY16-F42hYSoOZzHZl0000e5c5@hotmail.com>

http://ramp.ucsd.edu/~bellardo/pubs/usenix-sec03-80211dos-html/node10.html

This is the article I told u about...

Can anyone help plz...
Sam

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail




From jwright  Wed Sep 29 08:26:59 2004
From: jwright (Joshua Wright)
Date: Wed, 29 Sep 2004 11:26:59 -0400
Subject: Using Aux ports to send Control frames...
In-Reply-To: <BAY16-F30S8YV2btIXw00009a88@hotmail.com>
References: <BAY16-F30S8YV2btIXw00009a88@hotmail.com>
Message-ID: <415AD443.9030809@hasborg.com>

> Can anyone help me understanding this method? can u plz send a code or 
> indicate how to disable AUX ports in hostap and how to read or write 
> from it...
> 
> Documents that describes the functionalities of AUX ports or the method 
> reffered to would help me in my research...

The premise is that you have to stop the transmit queue after writing 
the packet to the device, searching through the AUX device for a magic 
value that indicates that start of the packet, and modifying the memory 
offset with your custom frame.

In practice, it's quite difficult since you are competing with a race 
condition to get the card into the right state for you to be able to 
mess with it in a way that it was never intended to do.  In my tests, 
I'm only able to get a few frames (like 1 or 2) transmitted before my 
card ceases to respond altogether, forcing a manual reset.

As I understand it, Cisco and Atheros cards do not have the same 
firmware restrictions as the Prism2 series cards, and can inject 
arbitrary frames of any time or content without being mangled.  This 
could allow an attacker to send spoofed frames with in-order sequence 
numbers to avoid being detected by WLAN IDS systems, and a slew of other 
devious tactics.

Did anyone make it to Toorcon this year?  There was a presentation 
titled "Advanced Packet Injection in 802.11a/b/g Networks" that may shed 
some more light on other packet injection opportunities that are 
otherwise firmware unencumbered.

-Josh

-- 
-Joshua Wright
jwright at hasborg.com
http://home.jwu.edu/jwright/

pgpkey: http://home.jwu.edu/jwright/pgpkey.htm
fingerprint: FDA5 12FC F391 3740 E0AE BDB6 8FE2 FC0A D44B 4A73

Today I stumbled across the world's largest hotspot.  The SSID is "linksys".



From jkmaline  Wed Sep 29 19:13:25 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Sep 2004 19:13:25 -0700
Subject: wlan0sta and wlan0ap
In-Reply-To: <200409291650.29410.kickdown@web.de>
References: <200409291650.29410.kickdown@web.de>
Message-ID: <20040930021325.GB7376@jm.kir.nu>

On Wed, Sep 29, 2004 at 04:50:29PM +0200, Stefan Winter wrote:

> about a year ago there were some postings about being in Master mode and 
> simultaneously with a logical device wlanXsta in Managed mode.

> I wonder how the status of that experiment is? Did it ever leave its 
> experimental state? And what specifically does "old" firmware mean?

It is still experimental and mostly untested in the current version of
the driver & hostapd. "Old" would have been station firmware 0.8.0 or
something like that. However, if I remember correctly, this started
working again with some of the latest firmware versions.

> I have a 
> card in possession that is an original "Lucent Orinoco" (really one of the 
> first 11b ever) with a firmware of an alternate versioning scheme (something 
> like 6.72 firmware or so). Would that be old enough? And is hostapd still 
> capable of that sort of thing?

Old enough yes, but Lucent Orinoco is not a Prism2-based card, so not
much hope in getting it to work in this kind of configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 29 19:26:05 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Sep 2004 19:26:05 -0700
Subject: Using Aux ports to send Control frames...
In-Reply-To: <BAY16-F30S8YV2btIXw00009a88@hotmail.com>
References: <BAY16-F30S8YV2btIXw00009a88@hotmail.com>
Message-ID: <20040930022605.GC7376@jm.kir.nu>

On Wed, Sep 29, 2004 at 04:26:02PM +0200, Sami FAKHOURY wrote:

> Actually Im kind of a beginner in hostap...I red an interesting article 
> where they stated that it's possible to send control frames with hostap 
> using Aux ports I admit it wasn't so clear for me...

Taking into account that nowadays there are many other chipsets that
provide much less restricted access to sending and receiving raw IEEE
802.11 frames, I don't see much point in trying to do tricks like using
Aux port memory access with Prism2.. It is trivial to implement raw
packet sending with many of the cards with no (or minimal) firmware and
everything done in the driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jkmaline  Wed Sep 29 19:31:28 2004
From: jkmaline (Jouni Malinen)
Date: Wed, 29 Sep 2004 19:31:28 -0700
Subject: Fragmentation.
In-Reply-To: <20040928175657.47618.qmail@web40625.mail.yahoo.com>
References: <20040928175657.47618.qmail@web40625.mail.yahoo.com>
Message-ID: <20040930023128.GD7376@jm.kir.nu>

On Tue, Sep 28, 2004 at 10:56:57AM -0700, nondito wrote:
> If the fragmentation is set to 512 (iwconfig wlan0
> frag 512) and mtu to be set to 1500 (ifconfig wlan0
> mtu 1500), what will be the layer 2 frame size between
> an accesspoint (master) and client (managed)?

512 in case of plaintext mode; possibly larger if encryption is used
(and less for packets that happen to be shorter than 512 bytes and for
the final fragments of the frames).

> How is fragmentation related to mtu on wireless
> layer-2?

Well, not really related much at all.. In practice, MTU is limit for the
MSDU size and each MSDU may be fragmented into number of MPDUs based on
the fragmentation threshold. Howeverm, this fragmentation does not
change the maximum "packet size" in the same way that, e.g., IP
fragmentation does.

-- 
Jouni Malinen                                            PGP id EFC895FA



From shine21  Thu Sep 30 05:45:08 2004
From: shine21 (Donghyuk Woo)
Date: Thu, 30 Sep 2004 21:45:08 +0900
Subject: Fragmentation.
Message-ID: <000101c4a6eb$514f8db0$4d00a8c0@Lifebook>

I'd like to let my HostAP machine be connected to the ethernet, thus all its
associated nodes can enjoy the internet. And also, I'd like to use some
specific packets whose length is bigger than 1500 bytes and which is used
only in the WLAN BSS. Then what should I do? I guess bridging mode might not
be the solution for this purpose.

-----Original Message-----
From: hostap-bounces+shine21=korea.com at shmoo.com
[mailto:hostap-bounces+shine21=korea.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: Thursday, September 30, 2004 11:31 AM
To: hostap at shmoo.com
Subject: Re: Fragmentation.


On Tue, Sep 28, 2004 at 10:56:57AM -0700, nondito wrote:
> If the fragmentation is set to 512 (iwconfig wlan0
> frag 512) and mtu to be set to 1500 (ifconfig wlan0
> mtu 1500), what will be the layer 2 frame size between
> an accesspoint (master) and client (managed)?

512 in case of plaintext mode; possibly larger if encryption is used (and
less for packets that happen to be shorter than 512 bytes and for the final
fragments of the frames).

> How is fragmentation related to mtu on wireless
> layer-2?

Well, not really related much at all.. In practice, MTU is limit for the
MSDU size and each MSDU may be fragmented into number of MPDUs based on the
fragmentation threshold. Howeverm, this fragmentation does not change the
maximum "packet size" in the same way that, e.g., IP fragmentation does.

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





From wk-hostap  Thu Sep 30 06:35:58 2004
From: wk-hostap (Wilfried Klaebe)
Date: Thu, 30 Sep 2004 15:35:58 +0200
Subject: WPA && bridge_packets dont work
In-Reply-To: <20040929034122.GC7376@jm.kir.nu>
References: <20040823134009.GH9839@informatik.uni-rostock.de>
	<20040907040121.GC7392@jm.kir.nu>
	<20040907150902.GA5222@kaos.in-kiel.de>
	<20040908061536.GH7362@jm.kir.nu>
	<20040908140458.GA8673@kaos.in-kiel.de>
	<20040909014913.GA7368@jm.kir.nu> <20040929034122.GC7376@jm.kir.nu>
Message-ID: <20040930133558.GA10060@kaos.in-kiel.de>

Am Tue, Sep 28, 2004 at 08:41:22PM -0700 schrieb Jouni Malinen:
> I committed couple of changes to disable netif_carrier_off() calls in
> non-client modes. In addition, SIOCSIWMODE handler is now calling
> netif_carrier_on() when moving to non-client mode.
> 
> I have not tested all combinations yet and would appreciate it if you
> could test the current development snapshot and report whether it works
> in your setup. I did not yet merge the changes to stable branch, but I
> will do this before 0.2.5 release if these seem to fix the problem.

Seems to work perfectly. Thanks!

Regards, Wilfried
-- 
Irgendwas ist ja immer...



From andreas  Thu Sep 30 15:57:38 2004
From: andreas (Andreas Schuldei)
Date: Fri, 1 Oct 2004 00:57:38 +0200
Subject: wpa_supplicant against a wrt54g with new broadcom drivers
Message-ID: <20040930225737.GF20793@lukas.schuldei.com>

i updated the firware in my wrt54g in my working setup with the
latest sveasoft pre-release alchemy pre-5.3 and it broke. 

the firmware contains new broadcom binary only drivers. 

here comes some debugging information: 

 all relevant parts from my wpa_supplicant.conf: 
 timotheus:~# egrep -v '(^#.*|^[[:space:]]*$)' /etc/wpa_supplicant.conf 
 ctrl_interface=/var/run/wpa_supplicant 
 ctrl_interface_group=0 
 eapol_version=1 
 ap_scan=1 
 network={ 
 ssid="Access_Point" 
 proto=WPA 
 key_mgmt=WPA-PSK 
 pairwise=CCMP TKIP 
 group=CCMP TKIP WEP104 WEP40 
 psk="xR6if61M" 
 priority=5 
 } 
 
 
 the debug output from wpa_supplicant (Olssen is a neighbour`s network which gets picked up): 
 
 timotheus:~# wpa_supplicant -i ath0 -D madwifi -d 
 Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' 
 Reading configuration file '/etc/wpa_supplicant.conf' 
 ctrl_interface='/var/run/wpa_supplicant' 
 ctrl_interface_group=0 
 eapol_version=1 
 ap_scan=1 
 Priority group 5 
 id=0 ssid='Access_Point' 
 EAPOL: SUPP_PAE entering state DISCONNECTED 
 EAPOL: KEY_RX entering state NO_KEY_RECEIVE 
 EAPOL: SUPP_BE entering state INITIALIZE 
 EAP: EAP entering state DISABLED 
 EAPOL: External notification - portEnabled=0 
 EAPOL: External notification - portValid=0 
 wpa_driver_madwifi_set_wpa: enabled=1 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_del_key: keyidx=1 
 wpa_driver_madwifi_del_key: keyidx=2 
 wpa_driver_madwifi_del_key: keyidx=3 
 wpa_driver_madwifi_set_countermeasures: enabled=0 
 wpa_driver_madwifi_set_drop_unencrypted: enabled=1 
 Setting scan request: 0 sec 100000 usec 
 Wireless event: cmd=0x8b1a len=12 
 Starting AP scan (broadcast SSID) 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b19 len=12 
 Received 475 bytes of scan results (2 BSSes) 
 Scan results: 2 
 Selecting BSS from priority group 5 
 0: 00:0f:66:45:e2:ad ssid='Access_Point' wpa_ie_len=24 rsn_ie_len=0 
 selected 
 Trying to associate with 00:0f:66:45:e2:ad (SSID='Access_Point' freq=2462 MHz) 
 Cancelling scan request 
 WPA: using IEEE 802.11i/D3.0 
 WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_del_key: keyidx=1 
 wpa_driver_madwifi_del_key: keyidx=2 
 wpa_driver_madwifi_del_key: keyidx=3 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_set_drop_unencrypted: enabled=1 
 wpa_driver_madwifi_associate 
 Setting authentication timeout: 5 sec 0 usec 
 EAPOL: External notification - EAP success=0 
 EAPOL: External notification - EAP fail=0 
 EAPOL: External notification - portControl=Auto 
 Wireless event: cmd=0x8b1a len=24 
 Wireless event: cmd=0x8b1a len=24 
 Wireless event: cmd=0x8b15 len=20 
 Wireless event: new AP: 00:0f:66:45:e2:ad 
 Association event - clear replay counter 
 Associated to a new BSS: BSSID=00:0f:66:45:e2:ad 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_del_key: keyidx=1 
 wpa_driver_madwifi_del_key: keyidx=2 
 wpa_driver_madwifi_del_key: keyidx=3 
 wpa_driver_madwifi_del_key: keyidx=0 
 EAPOL: External notification - portValid=0 
 EAPOL: External notification - EAP success=0 
 EAPOL: External notification - portEnabled=1 
 EAPOL: SUPP_PAE entering state CONNECTING 
 EAPOL: txStart 
 WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0) 
 EAPOL: SUPP_BE entering state IDLE 
 EAP: EAP entering state INITIALIZE 
 EAP: EAP entering state IDLE 
 Setting authentication timeout: 10 sec 0 usec 
 RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added 
 RX EAPOL from 00:0f:66:45:e2:ad 
 Setting authentication timeout: 10 sec 0 usec 
 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines 
 IEEE 802.1X RX: version=1 type=3 length=95 
 EAPOL-Key type=254 
 WPA: RX message 1 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2) 
 WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02 
 WPA: Renewed SNonce - hexdump(len=32): 7b 68 45 58 49 2a 09 bf 5b 91 6f d6 86 df cb 3c 85 97 95 e4 bb e7 1e 14 f5 17 24 0b 93 cb 72 40 
 WPA: PMK - hexdump(len=32): 27 2a 7a ac 7c 67 cf 56 3b 86 26 cd f5 ad ae fa 13 08 24 6a cf 6b 1b 2e 6c 80 b9 dd dd 58 a1 56 
 WPA: PTK - hexdump(len=64): 01 92 48 4e e1 04 01 c1 08 c5 a0 27 7c f2 26 00 a1 15 6a 8d 4a 00 a1 e3 10 70 ec 0f 41 36 1d 3cdd 87 5a 72 0f 7f e2 42 c4 e1 9f 9e 2b 8f c8 af 17 08 a6 77 93 9f 44 58 cf a2 5b 15 11 76 a4 7c 
 WPA: EAPOL-Key MIC - hexdump(len=16): fe 95 06 4f 0b eb a9 b6 77 c1 d0 e1 2f 54 f5 24 
 WPA: Sending EAPOL-Key 2/4 
 RX EAPOL from 00:0f:66:45:e2:ad 
 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines 
 IEEE 802.1X RX: version=1 type=3 length=119 
 EAPOL-Key type=254 
 WPA: RX message 3 of 4-Way Handshake from 00:0f:66:45:e2:ad (ver=2) 
 WPA: Sending EAPOL-Key 4/4 
 WPA: Installing PTK to the driver. 
 WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 
 wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16 
 RX EAPOL from 00:0f:66:45:e2:ad 
 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines 
 IEEE 802.1X RX: version=1 type=3 length=119 
 EAPOL-Key type=254 
 WPA: RX message 1 of Group Key Handshake from 00:0f:66:45:e2:ad (ver=2) 
 WPA: Group Key - hexdump(len=16): c6 92 9c a0 0f 25 51 b1 da b3 bd 18 6f b7 09 82 
 WPA: Installing GTK to the driver (keyidx=1 tx=0). 
 WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 
 wpa_driver_madwifi_set_key: alg=CCMP key_idx=1 set_tx=0 seq_len=6 key_len=16 
 WPA: Sending EAPOL-Key 2/2 
 WPA: Key negotiation completed with 00:0f:66:45:e2:ad 
 Cancelling authentication timeout 
 EAPOL: External notification - portValid=1 
 EAPOL: External notification - EAP success=1 
 EAPOL: SUPP_PAE entering state AUTHENTICATING 
 EAPOL: SUPP_BE entering state SUCCESS 
 EAP: EAP entering state SUCCESS 
 EAPOL: SUPP_PAE entering state AUTHENTICATED 
 EAPOL: SUPP_BE entering state IDLE 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b15 len=20 
 Wireless event: new AP: 00:00:00:00:00:00 
 Setting scan request: 0 sec 100000 usec 
 EAPOL: External notification - portEnabled=0 
 EAPOL: SUPP_PAE entering state DISCONNECTED 
 EAPOL: SUPP_BE entering state INITIALIZE 
 EAP: EAP entering state DISABLED 
 EAPOL: External notification - portValid=0 
 EAPOL: External notification - EAP success=0 
 Disconnect event - remove keys 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_del_key: keyidx=1 
 wpa_driver_madwifi_del_key: keyidx=2 
 wpa_driver_madwifi_del_key: keyidx=3 
 wpa_driver_madwifi_del_key: keyidx=0 
 RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added 
 Starting AP scan (broadcast SSID) 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b19 len=12 
 Received 201 bytes of scan results (1 BSSes) 
 Scan results: 1 
 Selecting BSS from priority group 5 
 0: 00:09:5b:c4:a4:92 ssid='Olsson' wpa_ie_len=0 rsn_ie_len=0 
 skip - no WPA/RSN IE 
 No suitable AP found. 
 Setting scan request: 5 sec 0 usec 
 Starting AP scan (broadcast SSID) 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b19 len=12 
 Received 201 bytes of scan results (1 BSSes) 
 Scan results: 1 
 Selecting BSS from priority group 5 
 0: 00:09:5b:c4:a4:92 ssid='Olsson' wpa_ie_len=0 rsn_ie_len=0 
 skip - no WPA/RSN IE 
 No suitable AP found. 
 Setting scan request: 5 sec 0 usec 
 Starting AP scan (broadcast SSID) 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b1a len=12 
 Wireless event: cmd=0x8b19 len=12 
 Received 201 bytes of scan results (1 BSSes) 
 Scan results: 1 
 Selecting BSS from priority group 5 
 0: 00:09:5b:c4:a4:92 ssid='Olsson' wpa_ie_len=0 rsn_ie_len=0 
 skip - no WPA/RSN IE 
 No suitable AP found. 
 Setting scan request: 5 sec 0 usec 
 Signal 2 received - terminating 
 wpa_driver_madwifi_del_key: keyidx=0 
 wpa_driver_madwifi_del_key: keyidx=1 
 wpa_driver_madwifi_del_key: keyidx=2 
 wpa_driver_madwifi_del_key: keyidx=3 
 EAPOL: External notification - portEnabled=0 
 EAPOL: External notification - portValid=0 
 wpa_driver_madwifi_set_wpa: enabled=0 
 wpa_driver_madwifi_set_drop_unencrypted: enabled=0 
 wpa_driver_madwifi_set_countermeasures: enabled=0 
 
 as you can see the connection is set up all right (and during that time the iwconfig output shows a successfull connection, too). But it breaks up for reasons i dont understand and cant really guess. 
 
how can i work around this?




From madwifi  Wed Sep 29 23:04:54 2004
From: madwifi (Reto Bucher)
Date: Thu, 30 Sep 2004 08:04:54 +0200
Subject: HostAP IAPP code
Message-ID: <415BA206.6020303@opacus.ch>

Hi,

if i'm right, IAPP of hostAP does only cover the very basic
functionality of 802.11f.

Are there any ongoing activities to add some functionality to hostAP
(e.g IAPP caching, ...)? Or are there any plans?

Or, as a very basic question: is IAPP slowly dying?

rgds
Reto




