From j  Sun Dec  2 10:01:04 2007
From: j (Jouni Malinen)
Date: Sun, 2 Dec 2007 10:01:04 -0800
Subject: Metalink patches for Intel WPS code
In-Reply-To: <5002BD9FB045734DB9F20119530FB01701783C5B@ilmail2.metalink.dsl>
References: <5002BD9FB045734DB9F20119530FB017017424C5@ilmail2.metalink.dsl>
	<5002BD9FB045734DB9F20119530FB01701783C5B@ilmail2.metalink.dsl>
Message-ID: <20071202180103.GY5698@jm.kir.nu>

On Mon, Nov 26, 2007 at 07:47:30PM +0200, Assaf Harel wrote:

> Metalink released another patch today:
> http://w1.fi/contrib/metalink/Intel_WSC_Metalink_WSC.patch 
> This patch updates Intel's original WPS daemon (known as Wsccmd) that
> runs on top of hostapd / wpa_supplicant.
> 
> Now it is possible to pass wifi WPS certification

Nice to see this type of changes released. I know that number of
companies have worked on modifications to the Intel reference
implementation, but the changes have not usually been released which
leads into duplicate work.

Do you have any plans or do you know of anyone else having plans to
maintain the WSC reference implementation in the future? The Intel web
site for this does not seem to indicate that this code would be
maintained or modified to become production quality code. I'm somewhat
worried about depending on an implementation that does not have someone
maintaining it. Especially so, when there are still number of areas that
would benefit of major cleanup.


As far as the EAP method is concerned, there are number of issues with
the original hostapd/wpa_supplicant 0.4.x -based implementation. In
order to go forward on this area, I implemented an EAP method that
provides just the EAP transport part for WPS using the 0.6.x code base
and proper use of expanded EAP header. This, I believe, is also moving
the interface between EAP transport and WPS Registration Protocol into
cleaner location, i.e., doing all EAP specific stuff (including
fragmentation and reassembly and EAP header processing) into the EAP
method while leaving the WPS Registration Protocol to handle WSC M1..M8,
Done, ACK, and NACK.

The current version does not include interface for an external process
for processing the WPS messages. There is only a dummy implementation
that can be used for testing the EAP transport. However, communication
with an external process could be implemented using pending EAP
processing functionality in hostapd/wpa_supplicant to avoid the blocking
calls to external process which is used in the reference WSC code (and
which will not be acceptable for hostapd/wpa_supplicant integration).


The more I look at the reference WSC code, the more I would like to see
this done with simpler design or at least in smaller steps. I think it
would be useful to see a minimal implementation that supports just the
case of AP with an internal Registrar and client with an Enrollee and
only EAP transport (i.e., no UPnP complexity) as the first step. Once
this is available in a clean, maintainable implementation, more
functionality could be added.

I do not like the extra complexity caused by wsccmd being responsible
for starting hostapd/wpa_supplicant with hardcoded command line and
configuration file options. I would much rather see something that
allows both programs to be started (and configured) independently and
then whatever information needs to be transfered between the processes
would go through the ctrl_iface.


Is someone interested in working with a larger design change for the
Intel wsccd code? I have to say that I'm not exactly looking forward to
touching that code myself and would likely find it easier to work with a
new in-process implementation of WPS Registration Protocol as a library
that is designed to fit hostapd/wpa_supplicant model better if I had to
do the work..

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sun Dec  2 10:42:22 2007
From: j (Jouni Malinen)
Date: Sun, 2 Dec 2007 10:42:22 -0800
Subject: wps_enrollee cleaned up code
In-Reply-To: <200711121347.57122.ted@atheros.com>
References: <200711121347.57122.ted@atheros.com>
Message-ID: <20071202184221.GZ5698@jm.kir.nu>

On Mon, Nov 12, 2007 at 01:47:56PM -0800, Ted Merrill wrote:

> Logically, the new wps_enrollee sits above and commands wpa_supplicant, which
> continues to run... see below.
> It also however makes direct l2_packet calls.
> It could be argued that wps_enrollee should make use of the EAP code used 
> elsewhere, but i think this would only serve to confuse.
> Although WPS >uses< the EAP mechanism, WPS is not actually an authentication 
> protocol at all... using EAP is basically just a hack.

I think I will be arguing that this could will need to use the same
EAPOL and EAP implementation as all other EAP methods. I do not see much
point in duplicating this functionality just for WPS. A design that
separates WPS Registration Protocol from EAP and shares the already
existing EAPOL/EAP implementation looks much cleaner. I've added EAP-WSC
implementation (just the EAP specific functionality) into my Git tree
for both the EAP server and peer.

Since the Registration Protocol can be used over multiple transport
mechanisms, it would benefit of clean interface that passed M1..M8, ACK,
NACK, Done to WPS processing from wherever they came from (EAP, UPnP,
etc.). In other words, the main WPS code should not need to worry about
EAP details like fragmentation and reassembly or EAP header contents.
Nor should it have to even know anything about l2_packet. Please also
note that EAPOL frames can be received through the driver interface to
better support some platforms. Direct calls to l2_packet would mean this
option is not available (i.e., reduced OS/network stack support).

> -- wps_crypto -- key generation, authentication generation and checking.
> The state data consists only of key data.  Relies on the same underlying
> crypto routines as wpa_supplicant does (including can use the compact
> internal routines).  Some of this will be useful for wps server.

Some of this should really be integrated into src/crypto and only the
WPS specific parts should remain in wps_crypto. For example, the current
version seems to implement HMAC-SHA256 which is already available in
src/crypto/sha256.c.

> -- wpse_sm - enrollee state machine. The state data for the state machine
> consists of: configuration parameters; copies of packets sent and received;
> key state.  wpse_sm does NOT send or receive any packets, nor does it
> generate timeouts,  instead the next higher level queries wpse_sm and does
> the jobs for it.  This will simplify using this code in e.g. new embedded
> applications.

Does this really need to keep all possible packets (struct
wps_sm_packet_buffers) in memory all the time? That structure is close
to 30 kB.. Where does the 1520 byte maximum come from? WPS spec does not
seem to define a maximum length and at least EAP transport could handle
up to 64 kB packets..

Like I mentioned above, I don't think Ethernet/EAPOL/EAP processing
belongs here. While I really do not like the idea of UPnP, it sounds
better to keep the interface designed in a way that would handle, if
needed, both EAP and UPnP transports, assuming this can be done without
much extra complexity.

> -- wpse_supplicant -- enrollee interface to the supplicant, it commands the
> supplicant (via wpa_ctrl mechanism, using socket files on linux) to associate
> with the desired ssid in open mode... note that wpa_supplicant runs the whole
> time. This portion could be easily replaced to e.g. perform supplicant
> actions directly.

If the enrollee code will run as a separate process, ctrl_iface is a
proper place was interfacing with wpa_supplicant. However, if this is in
the same process, something else should be used.

> Currently, wps_enrollee is a separate program, and no modifications to
> wpa_supplicant were necessary (except for the Makefile and defconfig, to make
> wps_enrollee)... this is certainly the safe road for early development.
> I've gotten the feedback from you that for various reasons it would be
> better if it were part of wpa_supplicant.  My thinking is that it can be 
> linked as part
> of the wpa_supplicant program yet still logically sit above (the rest of)
> wpa_supplicant... i hope you agree with that. My intention is to extend
> the wpa_ctrl mechanism to include control from within the same process or just 
> bypass wpa_ctrl entirely.

I would agree that it would be fine to have the WPS Registration
Protocol implemented as a separate component above wpa_supplicant.
However, I do not think I would go as far with the full WPS
implementation that would only use wpa_supplicant to associate with the
AP and then take care of all EAPOL/EAP processing.

The way I've been thinking of the WPS process to go would be something
like this:
- wpa_supplicant is running; maybe with empty configuration, but still,
  running and able to provide scan results
- OS specific network management, say NetworkManager (NM), monitors
  network configuration and scan results and finds that no configured
  networks are available, but there is a WPS-enabled AP that could
  potentially be used
- NM requests wpa_supplicant to start WPS with an AP
- wpa_supplicant configures the driver for WPS and requests association
  with the BSS
- wpa_supplicant takes care of EAPOL and EAP processing; EAP-WSC payload
  may be handled either in-process (integrated Enrollee/Registrar) or by
  sending it to an external process (Enrollee/Registrar) (the mechanism
  for this could be separate from ctrl_iface)
- wpa_supplicant notifies NM about progress and if needed, requests
  information from the user (say, PIN)
- wpa_supplicant notifies NM of completion of WPS and availability of
  network parameters
- wpa_supplicant could internally update its configuration and/or wait
  for NM to do that

> The wpa_ctrl mechanism is in my opinion rather weak, and could use some
> extensive rework (in contrast to most of your code which is quite good).
> It uses a text based communication protocol which isn't very easy to extend.

Could you please elaborate? I don't see why text based protocol would
make it harder to extend. ctrl_iface was certainly not designed for
in-process communication, but if there are areas that would benefit from
changes to support external processes better, I would be interested in
hearing more details.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sun Dec  2 18:14:42 2007
From: j (Jouni Malinen)
Date: Sun, 2 Dec 2007 18:14:42 -0800
Subject: hostapd/wpa_supplicant - new stable release v0.5.9
Message-ID: <20071203021442.GA5698@jm.kir.nu>

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

This release is a bug fix version from the stable (0.5.x) branch and
it replaces 0.5.8 as the recommended stable version.

hostapd:
* updated EAP Generalized Pre-Shared Key (EAP-GPSK) to use the latest
  draft (draft-ietf-emu-eap-gpsk-07.txt)
* fixed debugging code not to use potentially unaligned read to fetch
  IPv4 addresses

wpa_supplicant:
* fixed an integer overflow issue in the ASN.1 parser used by the
  (experimental) internal TLS implementation to avoid a potential
  buffer read overflow
* fixed a race condition with -W option (wait for a control interface
  monitor before starting) that could have caused the first messages to
  be lost
* updated EAP Generalized Pre-Shared Key (EAP-GPSK) to use the latest
  draft (draft-ietf-emu-eap-gpsk-07.txt)
* added ctrl_iface RECONNECT (wpa_cli reconnect) command
  (like reassociate, but only takes effect if already associated)
* fixed a possible race condition between wpa_cli reassociate and
  wpa_cli disconnect
* return a non-zero exit code from non-interactive wpa_cli if the
  command is not recognized or fails
* fixed 0.5.8 regressions in BSS selection that prevented wildcard SSID
  from being used with non-WPA networks and disabled workaround for
  ignoring bogus WPA/RSN IE in non-WPA configuration
* fixed OpenSSL TLS wrapper to clear trusted CA list to allow
  network blocks to use different trusted CA configurations
* fixed a potential EAP state machine loop when mloving from PSK to EAP
  configuration without restarting wpa_supplicant


git-shortlog for 0.5.8 -> 0.5.9:

Daniel Drake (3):
      Add wpa_cli reconnect command
      Fix wpa_cli disconnect/reassociate race
      Meaningful non-interactive wpa_cli exit code

Johannes Berg (1):
      Update conf file eap_message help

Jouni Malinen (35):
      Fixed key_mgmt mapping to handle non-WPA IEEE 802.1X correctly.
      Clarified function documentation.
      Updated get_keyblock_size() to handle OpenSSL API change in 0.9.9.
      Fixed printf format for size_t to silence a compiler warning.
      Fixed X.509v3 certificate validation checks to use unsigned comparison when
      Fixed parsing of pathLenConstraint from BasicConstraints.
      Added support for validating pathLenConstraint.
      Added a workaround for handling validity dates between 1950 and 1970 to
      Changed PrintableString comparisons to be case insensitive and to filter
      Require that X509v3 CA certificates include BasicConstraints extension.
      Fixed l2_packet_deinit() to unregister read socket from eloop.
      Fixed an integer overflow issue in the ASN.1 parser used by the
      Fixed debugging code to print out IPv4 addresses without using potentially
      Added clarifying note to avoid confusion on what exactly is set with
      Fixed non-WPA AP selection code to ignore possible bogus WPA/RSN IE if the
      Update string length field only after the string has been parsed correctly.
      Fixed a typo in function documentation.
      Remove previously configured trusted CA certificates before adding new
      Fixed "Authentication with BSSID timed out." message to use the pending
      Fixed deinit code to cancel ieee802_1x_rekey timer to avoid potential
      Fixed remove_pmkid() handler not to clear list head (copy-paste error). The
      Fixed printf format for size_t to avoid compiler warnings.
      Revert "Fixed printf format for size_t to avoid compiler warnings."
      Fixed printf format for size_t to avoid compiler warnings.
      Added error codes for most command handlers and the case where multiple
      Replace dbus_watch_get_fd() calls with dbus_watch_get_unix_fd() when
      Clear forced EAP success when reconfiguring to avoid potential EAP state
      Updated EAP-GPSK to the latest draft version (-04). This changed
      Changed EAP-GPSK CSuite field to use 4 octets for vendor id and 2 octets
      Added vector version of AES-CMAC.
      Updated EAP-GPSK key derivation to use the new GKDF construction defined
      Updated the key derivation comments to match with the implementation and
      Cleaned up EAP-GPSK message processing by dividing it into number of
      Updated EAP-GPSK to match with the latest draft (-07):
      Preparations for 0.5.9.

Kel Modderman (3):
      action event name typo in wpa_cli(8)
      Allow selection of zero length non-WPA ssid by wpa_supplicant_select_bss
      Fixed a race condition with -W option (wait for a control interface monitor

Michael Taylor (1):
      Fix for noisy log output when no IP address is assigned.

Ted Merrill (2):
      send errno EBADF handling
      driver_madwifi.c null ptr dereference fix

-- 
Jouni Malinen                                            PGP id EFC895FA



From advan  Mon Dec  3 01:24:54 2007
From: advan (advan)
Date: Mon, 3 Dec 2007 17:24:54 +0800
Subject: how to forward IP
Message-ID: <200712031724512189659@rexian.com>


hi, all 
  In my embedded platform(station) , I create a bridge(br0) by brctl and build a station mode(ath0) with madwifi for atheros card and an ethernet interface(eth0), then add ath0 and eth0 to br0, it's able to connet a AP(cisco). I could ping the embeded platform from AP(cisco),but not ping the PC after the embedded platform (station), I thought my embedded platform didn't forward IP packets to PC . otherwsie on PC I also couldn't ping the AP (cisco) ,only ping station .
   How to ping PC after the embedded platform .please advise and give me clue ,thank you in advance 

kernel: 2.4.25 
uclibc+busybox 

PC --->station                          AP(cisco)


Best regards 


                          advan



advan
2007-12-03
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/be0a304f/attachment.htm 


From johannes  Mon Dec  3 02:41:10 2007
From: johannes (Johannes Berg)
Date: Mon, 03 Dec 2007 11:41:10 +0100
Subject: [PATCH] hostapd: make driver_devicescape set multi-BSS
	interfaces up
In-Reply-To: <20071201044941.GV5698@jm.kir.nu>
References: <1196196134.6058.101.camel@johannes.berg>
	<20071201044941.GV5698@jm.kir.nu>
Message-ID: <1196678470.6060.27.camel@johannes.berg>


> Is this really needed? Please note that at least my version of
> driver_devicescape.c is still using management interface and as such,
> the secondary BSS interfaces do not really need to be IFF_UP for
> association and EAPOL messages. Furthermore, hostapd_set_iface_flags()
> is setting the management interface MTU and doing this for each BSS
> interface sounds unnecessary.

Yes, I realise that we still use the mgmt iface. However, setting the
interface UP is needed to get the device to ACK frames on the other MAC
address because the drivers only configure the MAC address
correspondingly when the interface is set UP. Also, I think I changed
beaconing to be unsupported on interfaces that are down.

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


From s.raghu  Mon Dec  3 03:05:32 2007
From: s.raghu (RAGHAVENDRA SADARAMACHANDRA)
Date: Mon, 03 Dec 2007 11:05:32 +0000 (GMT)
Subject: EAP-TTLS problem on marvell 8686 wpa supplicant..
Message-ID: <0JSH009Z3058Q8@ms13.samsung.com>

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


From s.raghu  Mon Dec  3 03:11:56 2007
From: s.raghu (RAGHAVENDRA SADARAMACHANDRA)
Date: Mon, 03 Dec 2007 11:11:56 +0000 (GMT)
Subject: EAP-TTLS problem...
Message-ID: <0JSH006IT0FWVW@ms13.samsung.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/4219fef2/attachment.htm 


From raghavendra.akkasali  Mon Dec  3 03:51:54 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 3 Dec 2007 17:21:54 +0530
Subject: No subject
Message-ID: <58a444250712030351o6ed87d4ag259376e185947dd5@mail.gmail.com>

Hi All,

 I am configuring wpa supplicant to use EAP-TTLS on wpa supplicant ported to
marvell 8686. But have few raod block. Plz help me to solve the issue.
luckily i am not getting any error in RADIUS server side...

*1. Getting SSL connect error.*

SSL: SSL_connect:before/connect initialization

SSL: (where=0x1001 ret=0x1)

SSL: SSL_connect:SSLv3 write client hello A

SSL: (where=0x1002 ret=0xffffffff)

SSL: SSL_connect:error in SSLv3 read server hello A

SSL: SSL_connect - want more data

SSL: 102 bytes pending from ssl_out

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

EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL



*2. EAP entering failure state*

EAP: EAP entering state FAILURE

CTRL-EVENT-EAP-FAILURE EAP authentication failed

EAPOL: SUPP_PAE entering state AUTHENTICATING

EAPOL: SUPP_BE entering state FAIL



*my wpa_supplicant.conf as below*

update_config=1

eapol_version=1

ap_scan=1

fast_reauth=1



network={

        ssid="3Com"

        scan_ssid=1

        auth_alg=OPEN

        proto=WPA

        key_mgmt=WPA-EAP IEEE8021X

        pairwise=TKIP CCMP

        group=CCMP TKIP WEP104 WEP40

        eap=TTLS

        identity="jbibe"

        anonymous_identity="jbibe"

        password="whatever"

        priority=2

        phase2="auth=MD5"

}


-Raghu




-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/33cbe634/attachment.htm 


From raghavendra.akkasali  Mon Dec  3 03:52:37 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 3 Dec 2007 17:22:37 +0530
Subject: wpa supplicant EAP-TTLS problem on marvell 8686...
Message-ID: <58a444250712030352l2bd5197ax8f7dff0ac2831b12@mail.gmail.com>

Hi All,

 I am configuring wpa supplicant to use EAP-TTLS on wpa supplicant ported to
marvell 8686. But have few raod block. Plz help me to solve the issue.
luckily i am not getting any error in RADIUS server side...

*1. Getting SSL connect error.*

SSL: SSL_connect:before/connect initialization

SSL: (where=0x1001 ret=0x1)

SSL: SSL_connect:SSLv3 write client hello A

SSL: (where=0x1002 ret=0xffffffff)

SSL: SSL_connect:error in SSLv3 read server hello A

SSL: SSL_connect - want more data

SSL: 102 bytes pending from ssl_out

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

EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL



*2. EAP entering failure state*

EAP: EAP entering state FAILURE

CTRL-EVENT-EAP-FAILURE EAP authentication failed

EAPOL: SUPP_PAE entering state AUTHENTICATING

EAPOL: SUPP_BE entering state FAIL



*my wpa_supplicant.conf as below*

update_config=1

eapol_version=1

ap_scan=1

fast_reauth=1



network={

        ssid="3Com"

        scan_ssid=1

        auth_alg=OPEN

        proto=WPA

        key_mgmt=WPA-EAP IEEE8021X

        pairwise=TKIP CCMP

        group=CCMP TKIP WEP104 WEP40

        eap=TTLS

        identity="jbibe"

        anonymous_identity="jbibe"

        password="whatever"

        priority=2

        phase2="auth=MD5"

}


-Raghu




-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/1ef5e18f/attachment.htm 


From satyanarayanam  Mon Dec  3 04:20:27 2007
From: satyanarayanam (satyanarayanam)
Date: Mon, 3 Dec 2007 17:50:27 +0530
Subject: FW: wired 802.1x supplicent open source where i can get it?
Message-ID: <001701c835a6$e426cb10$2b29320a@telxsi.com>


Hi,

I am satyanarayana,we are working to implement 802.1x wired supplicent ,
But Tried a lot by checking somany sites But i didn't get that open source.
If any body knows the site are any details Please send to me.

Thank you in Advance..

Thank you,
Satyanarayna reddy mendaddula,
Tata Elxsi Ltd,White field ,Hoody-1,
Emp no--6185, Mb no - 9341311577
Email:- satyanarayanam at tataelxsi.co.in

  Help ever, Hurt never
..


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

Contact your Administrator for further information.



From ve2cii  Mon Dec  3 05:40:53 2007
From: ve2cii (Frank)
Date: Mon, 3 Dec 2007 08:40:53 -0500 (EST)
Subject: handshake error
Message-ID: <44555.66.201.209.31.1196689253.squirrel@mail1.canasoft.net>

   Hello,

NOTE: There are no files attached. This is my second attempt as my first
attempt did not pass through with the attachments. If someone can help
I can send the attachments.

  I was wondering if someone can give me a hand with this. I am trying
to connect my linux box to a Dlink DI-524 AP. I am not sure if I am doing
something wrong, or if I have run into a bug. I am attaching a picture of
the DI-524 config along with debug information. I tried this

wpa_supplicant -c /etc/wpa_supplicant.conf -i ath0 -D madwifi -d
which gives the file wpa_madwifi.txt

I also tried using the default driver

wpa_supplicant -c /etc/wpa_supplicant.conf -i ath0 -d
which gives the file wpa.txt

The file config.txt is the .config file which I used when I compiled
wpa_supplicant

The file lsmod.txt are the loaded modules

The file wpa_supplicant.conf I have also attached

I am using madwifi-0.9.3.2 and wpa_supplicant-0.5.8

The wireless card in the linux is a Dlink which uses Atheros.

If you need any further details just let me know and I will provide them.
I have also done quite a bit of reading of the mailing list, but may have
missed something.

-
sysadm  cronomagic.com , wapda.com
e-mail  ve2cii at canasoft.net

POWERED BY LINUX






-
sysadm  cronomagic.com , wapda.com
e-mail  ve2cii at canasoft.net

POWERED BY LINUX



From jsullivan  Mon Dec  3 05:50:16 2007
From: jsullivan (John A. Sullivan III)
Date: Mon, 03 Dec 2007 08:50:16 -0500
Subject: FW: wired 802.1x supplicent open source where i can get it?
In-Reply-To: <001701c835a6$e426cb10$2b29320a@telxsi.com>
References: <001701c835a6$e426cb10$2b29320a@telxsi.com>
Message-ID: <1196689816.6492.4.camel@localhost>


On Mon, 2007-12-03 at 17:50 +0530, satyanarayanam wrote:
> Hi,
> 
> I am satyanarayana,we are working to implement 802.1x wired supplicent ,
> But Tried a lot by checking somany sites But i didn't get that open source.
> If any body knows the site are any details Please send to me.
> 
> Thank you in Advance..
<snip>
Have you look at http://open1x.sourceforge.net/ 
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan at opensourcedevel.com

If you would like to participate in the development of an open source
enterprise class network security management system, please visit
http://iscs.sourceforge.net




From paresh.sawant  Mon Dec  3 06:20:44 2007
From: paresh.sawant (Paresh Sawant)
Date: Mon, 3 Dec 2007 19:50:44 +0530
Subject: wpa_supplicant fails to preauthenticate
Message-ID: <683e2de40712030620t598c78c9ld634c45635b11f2c@mail.gmail.com>

Hi,
           I'm trying to make wpa_supplicant ( on windows XP with
CONFIG_USE_NDISUIO ) preauthenticate with ap2 while it is already associated
with ap1. Following are the network blocks I've specified in .conf -

network={
    ssid="ap1"
    key_mgmt=WPA-PSK
    proto=WPA2
    pairwise=CCMP
    group=CCMP
    psk=<some_passphrase>
}

network={
    ssid="ap2"
    key_mgmt=WPA-EAP
    priority=0
    identity="user"
    proto=WPA2
    pairwise=CCMP
    group=CCMP
    eap=TLS
    ca_cert=<path_to_ca.der>
    client_cert=<path_to_client.der>
    private_key=<path_to_clientkey.der>
}

          when I send command "preauthenticate <bssid_of_ap2> from wpa_cli,
it fails to pre-authenticate. I could see EAP identitity request coming to
wpa_supplicant, but there is no response to that.  wpa_supplicant shows
following debug messages -

RX ctrl_iface - hexdump_ascii(len=25):
     50 52 45 41 55 54 48 20 30 30 3a 31 36 3a 62 36   PREAUTH
<bssid_of_ap2>
     3a 63 36 3a 62 63 3a 36 32
CTRL_IFACE PREAUTH <bssid_of_ap2>
RSN: starting pre-authentication with <bssid_of_ap2>
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=1
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
CTRL: Overlapped write started for 00B96578
CTRL: Overlapped write completed: dst=00B96578 err=0 bytes=3
CTRL: Overlapped read started for 00B96578
RX pre-auth from <bssid_of_ap2>
RX pre-auth - hexdump(len=46): 02 00 00 05 01 0b 00 05 01 00 00 00 00 00 00
00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
63
51 72 20
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=11 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL_IFACE monitor send 00B96578
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=0): [NULL]
EAP: buildIdentity: identity configuration was not available
CTRL-REQ-IDENTITY-1:Identity needed for SSID <ap1>
CTRL_IFACE monitor send 00B96578
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: startWhen --> 0
RX pre-auth from <bssid_of_ap2>
RX pre-auth - hexdump(len=46): 02 00 00 05 01 0b 00 05 01 00 00 00 00 00 00
00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
63
51 72 20
EAPOL: Received EAP-Packet frame
RSN: pre-authentication with <bssid_of_ap2> timed out





Cheers
- Paresh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/0666cd08/attachment.htm 


From j  Mon Dec  3 06:45:38 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 06:45:38 -0800
Subject: FW: wired 802.1x supplicent open source where i can get it?
In-Reply-To: <001701c835a6$e426cb10$2b29320a@telxsi.com>
References: <001701c835a6$e426cb10$2b29320a@telxsi.com>
Message-ID: <20071203144537.GC5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 05:50:27PM +0530, satyanarayanam wrote:

> I am satyanarayana,we are working to implement 802.1x wired supplicent ,
> But Tried a lot by checking somany sites But i didn't get that open source.
> If any body knows the site are any details Please send to me.

All wpa_supplicant source code, including wired 802.1X supplicant
functionality, is included in the source code package that is available
from http://w1.fi/wpa_supplicant/

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Mon Dec  3 06:47:40 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 3 Dec 2007 23:47:40 +0900
Subject: Any Idea about MAC 00:00:00:00:00:00
In-Reply-To: <58a444250712030645i35edd888v592a4a5f374f8a9d@mail.gmail.com>
References: <58a444250712030645i35edd888v592a4a5f374f8a9d@mail.gmail.com>
Message-ID: <58a444250712030647if4b00eeg520d3bc97e7b5e2b@mail.gmail.com>

Hi All,

   My WLAN marvell card 8686, is getting some event from a AP with MAC
00:00:00:00:00:00. Does any body know for what this MAC stands for...I mean
MAC with all FF stands for MAC broadcast right? Similarly...Just want to
make out from where I am getting this MAC.


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/7da883d0/attachment.htm 


From raghavendra.akkasali  Mon Dec  3 06:49:05 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 3 Dec 2007 23:49:05 +0900
Subject: Any wireless packet capturing tool available for free?..like ethereal
	for ethernet packet...
In-Reply-To: <58a444250712030646h3c51a47fo5f0035488dc7ad8e@mail.gmail.com>
References: <58a444250712030646h3c51a47fo5f0035488dc7ad8e@mail.gmail.com>
Message-ID: <58a444250712030649i10703c1cu10a7c7684fadc814@mail.gmail.com>

Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071203/b46c1632/attachment.htm 


From j  Mon Dec  3 06:49:08 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 06:49:08 -0800
Subject: EAP-TTLS problem on marvell 8686 wpa supplicant..
In-Reply-To: <0JSH009Z3058Q8@ms13.samsung.com>
References: <0JSH009Z3058Q8@ms13.samsung.com>
Message-ID: <20071203144908.GD5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 11:05:32AM +0000, RAGHAVENDRA SADARAMACHANDRA wrote:
> <HTML><HEAD>

Please send ASCII (non-HTML) emails when using this mailing list.

> <p>&nbsp;I am configuring wpa supplicant to use EAP-TTLS. But have few raod 
> block. Plz help me to solve the issue. luckily i am not getting any error in 
> RADIUS server side...</p>

You would need to include more of the debug log from wpa_supplicant to
make it useful in figuring out what happened. However..

> <p># WPA2-EAP/CCMP using EAP-TLS</p>
> <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;eap=TTLS</p>
> <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;phase2=&quot;auth=MD5&quot;</p>

That phase2 parameter is not correct. It should be autheap=MD5, not
auth=MD5 when using TTLS.

-- 
Jouni Malinen                                            PGP id EFC895FA



From jsullivan  Mon Dec  3 06:51:32 2007
From: jsullivan (John A. Sullivan III)
Date: Mon, 03 Dec 2007 09:51:32 -0500
Subject: Any wireless packet capturing tool available for free?..like
	ethereal for ethernet packet...
In-Reply-To: <58a444250712030649i10703c1cu10a7c7684fadc814@mail.gmail.com>
References: <58a444250712030646h3c51a47fo5f0035488dc7ad8e@mail.gmail.com>
	<58a444250712030649i10703c1cu10a7c7684fadc814@mail.gmail.com>
Message-ID: <1196693492.6492.8.camel@localhost>


On Mon, 2007-12-03 at 23:49 +0900, Raghavendra. S wrote:
> 
> Regards & Thanks
> Raghavendra. S 
<snip>
I believe if you put your wireless card into monitor mode as one would
with kismet or airsnort, ethereal (wireshark) will see the packets -
John
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan at opensourcedevel.com

If you would like to participate in the development of an open source
enterprise class network security management system, please visit
http://iscs.sourceforge.net




From j  Mon Dec  3 06:56:06 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 06:56:06 -0800
Subject: wpa_supplicant fails to preauthenticate
In-Reply-To: <683e2de40712030620t598c78c9ld634c45635b11f2c@mail.gmail.com>
References: <683e2de40712030620t598c78c9ld634c45635b11f2c@mail.gmail.com>
Message-ID: <20071203145606.GE5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 07:50:44PM +0530, Paresh Sawant wrote:

>            I'm trying to make wpa_supplicant ( on windows XP with
> CONFIG_USE_NDISUIO ) preauthenticate with ap2 while it is already associated
> with ap1. Following are the network blocks I've specified in .conf -
> 
> network={
>     ssid="ap1"
>     key_mgmt=WPA-PSK

> network={
>     ssid="ap2"
>     key_mgmt=WPA-EAP

I wouldn't be surprised if pre-authentication would not work when
associated with a WPA-PSK AP. This is somewhat odd configuration of RSN
pre-authentication. I don't remember whether this is even allowed in the
IEEE 802.11 standard. Anyway, it looks like the problem here could be in
use of different SSIDs. I've only ever heard of pre-authentication used
within the same ESS, i.e., between APs that use the the same SSID.

Is this kind of network really deployed somewhere or is this just a test
case?

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Mon Dec  3 07:29:21 2007
From: dcbw (Dan Williams)
Date: Mon, 03 Dec 2007 10:29:21 -0500
Subject: Any Idea about MAC 00:00:00:00:00:00
In-Reply-To: <58a444250712030647if4b00eeg520d3bc97e7b5e2b@mail.gmail.com>
References: <58a444250712030645i35edd888v592a4a5f374f8a9d@mail.gmail.com>
	<58a444250712030647if4b00eeg520d3bc97e7b5e2b@mail.gmail.com>
Message-ID: <1196695761.2819.44.camel@localhost.localdomain>

On Mon, 2007-12-03 at 23:47 +0900, Raghavendra. S wrote:
> 
> 
> Hi All,
>  
>    My WLAN marvell card 8686, is getting some event from a AP with MAC
> 00:00:00:00:00:00. Does any body know for what this MAC stands for...I
> mean MAC with all FF stands for MAC broadcast right? Similarly...Just
> want to make out from where I am getting this MAC. 

This is the standard signal from the driver that it has either been
disconnected, or has failed to associate with the requested AP.  It is
normal.

Dan






From paresh.sawant  Mon Dec  3 10:43:23 2007
From: paresh.sawant (Paresh Sawant)
Date: Tue, 4 Dec 2007 00:13:23 +0530
Subject: wpa_supplicant fails to preauthenticate
In-Reply-To: <20071203145606.GE5698@jm.kir.nu>
References: <683e2de40712030620t598c78c9ld634c45635b11f2c@mail.gmail.com>
	<20071203145606.GE5698@jm.kir.nu>
Message-ID: <683e2de40712031043i84bb84btddfbcc77548eee09@mail.gmail.com>

If we assume that pre-auth is not allowed if the bssid belongs to different
ssid than one it is already associated with, then would that be right idea
to make wpa_supplicant report an error instead of initiating the pre-auth by
sending out eapol start packet ?

Is it possible to have 2 different access points within same ESS having
separate security policies e.g. ap1 with WPA2-PSK and ap2 with WPA2-EAP ? I
don't see IEEE 802.11i enforcing such a rule. please correct me.

Cheers
- Paresh

On Dec 3, 2007 8:26 PM, Jouni Malinen <j at w1.fi> wrote:

> On Mon, Dec 03, 2007 at 07:50:44PM +0530, Paresh Sawant wrote:
>
> >            I'm trying to make wpa_supplicant ( on windows XP with
> > CONFIG_USE_NDISUIO ) preauthenticate with ap2 while it is already
> associated
> > with ap1. Following are the network blocks I've specified in .conf -
> >
> > network={
> >     ssid="ap1"
> >     key_mgmt=WPA-PSK
>
> > network={
> >     ssid="ap2"
> >     key_mgmt=WPA-EAP
>
> I wouldn't be surprised if pre-authentication would not work when
> associated with a WPA-PSK AP. This is somewhat odd configuration of RSN
> pre-authentication. I don't remember whether this is even allowed in the
> IEEE 802.11 standard. Anyway, it looks like the problem here could be in
> use of different SSIDs. I've only ever heard of pre-authentication used
> within the same ESS, i.e., between APs that use the the same SSID.
>
> Is this kind of network really deployed somewhere or is this just a test
> case?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071204/baa27fbd/attachment.htm 


From ted  Mon Dec  3 13:24:18 2007
From: ted (Ted Merrill)
Date: Mon, 3 Dec 2007 13:24:18 -0800
Subject: Non-remote control of wpa_supplicant
Message-ID: <200712031324.18919.ted@atheros.com>

Jouni,

Sorry, i lost your reply until now.
I've switched over to non-digest which will help a lot.

Regarding the style i used for callbacks:
Passing the pointer  to the object to the callback provides, in my opinion, 
important type safety... and information from the object including cookies 
are readily available via access functions (inline is possible) but incur no 
overhead if not needed.

The code will be part of the next code i send you.

netx/prev are indeed part of the internal implementation and there would be no 
access functions for them.
cookie could be passed as part of the create function, which would be 
reasonable since a cookie is desireable in most cases.

-Ted

>> The wpa_ctrl feature allows control of wpa_supplicant from another
>> process/program.  For control within the same process/program, calls can be
>> made "directly" to the needed subroutines.
>> But one thing that is missing is that there is general way to monitor state
>> changes from within the same process except perhaps by periodic polling.
>> I've added the following to my local copy (in wpa_supplicant_i.h):
>
>This looks like a good addition.
>
>> /**
>>  * struct wpa_supplicant_cb - State change callback
>>  *
>>  * Callback function is called AFTER the state is marked as changed.
>>  * Information from the callback struct should be obtained via
>>  * the access functions (below).
>>  */
>> struct wpa_supplicant_cb {
>>         struct wpa_supplicant_cb *next;
>>         struct wpa_supplicant_cb *prev;
>>         void (*cb_func)(struct wpa_supplicant_cb *cb);
>>         struct wpa_supplicant *wpa_s;
>>         void *cookie;   /* passed to cb */
>> };
>
>I normally use callback functions that take a void* context argument
>which, I would assume, this cookie value is for. Is there any particular
>reason for passing struct wpa_supplicant_cb to the callback? The
>next/prev pointers look internal to the list implementation and it might
>be clearner to just pass in wpa_s and cookie as the cb_func arguments
>(cookie could be registered with _cb_create, so no need for a separate
>_cb_cookie_set functions).



From mreinstein  Mon Dec  3 14:05:41 2007
From: mreinstein (Mike Reinstein)
Date: Mon, 03 Dec 2007 17:05:41 -0500
Subject: wpa supplicant on windows mobile?
Message-ID: <47547DB5.6090800@skyhookwireless.com>

Hi folks,

 I'm trying to build an app on a  windows mobile that connects to an ap 
using wpa-psk, sends some data, and disconnects. I tried wpa_supplicant 
on windows, and it works very well but it's kind of big in terms of 
footprint, and I really don't need most of the advanced features that 
the suite provides (wpa2, all of the eap support, etc).

* is there a way to strip down the code to get a minimal wpa supplicant 
footprint?
* are there any resources for people that want to get wpa_supplicant 
working on windows mobile 5?

I'm brand new to this list, so pardon the ignorance if I'm asking a dumb 
or rehashed question. Thank you very much!

kind regards,

-Mike





From ted  Mon Dec  3 20:48:13 2007
From: ted (Ted Merrill)
Date: Mon, 3 Dec 2007 20:48:13 -0800
Subject: WPS patch from Ted Merrill, 20071203
Message-ID: <200712032048.14159.ted@atheros.com>

Hi Jouni

I've sent hostap-wps-20071203.patch by separate email to you since it would 
otherwise not survive the hostap mail list filter due to size.

This patch includes all of my pending changes for WPS.
It is not well tested but i wanted to get this to you so we can discuss.
[CONFIG_]EAP_WSC is yours, and [CONFIG_]EAP_WPS is mine.

For hostapd, 
I removed the use of WLAN_STA_WPS... flags entirely along with use of "sta" 
that you found objectionable in the hostap code (this was from the Intel 
modifications to hostapd).  I'm not 100% this is the right thing to do but i 
was unable to determine what useful function these flags actually provided.

I added WPS_SCAN and WPS commands to ctrl_iface.c for wpa_supplicant.
WPS_SCAN differs from the old SCAN command in two respects: it sets 
appropriate information elements in probe requests (if possible) and it does 
not return old stale scan results but instead asyncronously sends new scan 
results.
The WPS command does the core WPS algorithm (passing M1 .. M8 messages).

There is a  new value for "proto" : "WPS" which bypasses some checks that 
would not allow wpa_supplicant to try to associate in open mode with e.g. a 
WPA2 AP.
The "WPS" command disables any existing "network" definitions and essentially 
defines and activates one like:
network={
    ssid="some_ssid"
    key_mgmt=NONE
    auth_alg=OPEN
    proto=WPS
}
The WPS-capable AP will accept an open connection (for WPS purposes only) even 
though it does not advertise this in information elements other than the WPS 
information element; proto=WPS attempts to make wpa_supplicant happy with 
this (see kernel driver issue below).

There are two programs for wps:
wps_enrollee is intended for automated or at least non-interactive 
operation... it will do scanning if you don't give it an ssid, but will is 
not as flexible or friendly as wps_wizard.
wps_wizard is an interactive program that could serve as the inspiration for a 
gui wizard...
These programs use wpa_ctrl to use the WPS_SCAN and WPS commands.

There are some issues that you have noted that i have not addressed yet, 
including:
-- Uses l2_packet
-- Doesn't use hmac_sha256_vector yet
-- I haven't looked into using openssl yet, works only with internal crypto
By separate email i'm giving feedback to your latest email.

Finally, there are some serious Linux kernel driver issues to deal with:

WPS_SCAN only works if the kernel driver reports WPS information elements to 
user space.  Unfortunately, the latest driver from madwifi doesn't do that.
I used a patch from https://www.saice-wpsnfc.bz which patches a somewhat out 
of date version of the madwifi driver, which in turn does not work with the 
latest linux (it worked for me with Linux 2.6.15 which i happened to have 
lying around).
Unfortunately, the madwifi driver has been written only to report certain 
known i.e.s to user space (the above mentioned patch adds WPS to the list)... 
it really should be redesigned to report ALL information elements.
In browsing the madwifi pages i did not get any idea that any sort of fix for 
this problem is in the works...  and of course this is not the only kernel 
driver to worry about...

There is also a problem with associating with the AP for which i've found only 
a poor workaround.
Typically, a WPS capable or ready AP will advertise e.g. WPA2 capability in 
the probe responses but will actually associate in open mode (as required) 
with a firewall of sorts so that open mode associations can be used only for 
WPS purposes.
For some reason, the ioctls that driver_wext uses do not reliably result in 
getting an open connection ... sometimes it works and usually it doesn't.
My work around with my Intel Pro 2200BG is (while the WPS job in 
wpa_supplicant is waiting to get associated) to issue the following command:
    iwconfig eth1 key open
This typically results in immediate association.
Unfortunately, the same command fails when using madwifi driver with my 
Atheros wifi card (ath0 of course)... i can do "iwconfig ath0 key off" but 
that is not the same thing.
(I have access to the drivers that Atheros uses internally but have not yet 
released, and i can see if the problem occurs with them).

I'm able to use my ath0 (with LInux 2.6.15 with patched madwifi driver) to 
demonstrate that scanning works using wps_wizard, and i'm able to use eth1 to 
demonstrate that the core WPS algorithm works using wps_enrollee:
wps_enrollee ssid=some_ssid ifname=eth1



-Ted Merrill




From ted  Mon Dec  3 20:56:19 2007
From: ted (Ted Merrill)
Date: Mon, 3 Dec 2007 20:56:19 -0800
Subject: wps_enrollee cleaned up code
In-Reply-To: <20071202184221.GZ5698@jm.kir.nu>
References: <200711121347.57122.ted@atheros.com>
	<20071202184221.GZ5698@jm.kir.nu>
Message-ID: <200712032056.19283.ted@atheros.com>

Hi Jouni,
Thanks for the very good feedback.

A little background.  It would be best for Atheros (and everyone else of 
course) if WPS was part of the hostap tree, to eliminate the pain of having 
to keep a home-grown solution compatible with upgrades to hostap.
That said, i am rapidly approach the limit to which Atheros is willing to pay 
me to work on this, so it is possible i may not be able to see this 
integration through to completion.
However, i can see that you have been motivated to write some code for WPS so 
perhaps i have had some influence.
If i motivate you to write the entire thing yourself and using none of my 
code, that is fine, i'll feel like i've accomplished something.
However you are obviously a very busy person so i have some fear that this 
won't happen in a timely fashion.
This may put me in a somewhat difficult situation of trying to maintain  a 
repository that is both based on your repository but that also replaces your 
unfinished WPS code with my finished, but incompatible code.
(I'll send another email re. my current effort... im having kernel driver 
issues).
I'm happy in the near term to help debug your WPS code, if you do indeed have 
time to work on this.
Feel free to cannibalize anything i've done...

I would hope at least that we fix the impediments in the way of any WPS 
solution first.... such as the fix for IEEE80211_IOCTL_FILTERFRAME 
handling...

more below

-Ted Merrill
Atheros Communications

On Sunday 02 December 2007 10:42:22 Jouni Malinen wrote:
> On Mon, Nov 12, 2007 at 01:47:56PM -0800, Ted Merrill wrote:
> > Logically, the new wps_enrollee sits above and commands wpa_supplicant,
> > which continues to run... see below.
> > It also however makes direct l2_packet calls.
> > It could be argued that wps_enrollee should make use of the EAP code used
> > elsewhere, but i think this would only serve to confuse.
> > Although WPS >uses< the EAP mechanism, WPS is not actually an
> > authentication protocol at all... using EAP is basically just a hack.
>
> I think I will be arguing that this could will need to use the same
> EAPOL and EAP implementation as all other EAP methods. I do not see much
> point in duplicating this functionality just for WPS. A design that
> separates WPS Registration Protocol from EAP and shares the already
> existing EAPOL/EAP implementation looks much cleaner. I've added EAP-WSC
> implementation (just the EAP specific functionality) into my Git tree
> for both the EAP server and peer.

Do you have to call it WSC? that name  is obsolete and just confuses people.

Also, what you call "peer" the WPS spec calls "enrollee" and "client"... or 
perhaps i'm missing something... although i see it is a general naming 
convention you use....

I realize that your code is just a first pass, but i hope you address the 
following:
-- I don't see our mac address in the data structures... it will be required 
to be known somehow.  Knowing the ap's address may be required also.
-- It obtains EAP identity from configuration from wpa_ssid but this is 
inappropriate since essentially WPS has hijacked this... and anyway, 
eap_server/eap_wsc.c should ALWAYS use WFA-SimpleConfig-Registrar-1-0 and is 
always the registrar or the proxy thereof, and similarly for the client side 
code which will NOT be a registrar.
-- You could use a file for shared data definitions
-- You have plain numbers in the code that should be #ifdefed
-- Where did you get the size 2000 from?

Some sort of packet buffer management scheme (perhaps not quite as fancy as 
skbuf :~) would help i suppose.

>
> Since the Registration Protocol can be used over multiple transport
> mechanisms, it would benefit of clean interface that passed M1..M8, ACK,
> NACK, Done to WPS processing from wherever they came from (EAP, UPnP,
> etc.). In other words, the main WPS code should not need to worry about
> EAP details like fragmentation and reassembly or EAP header contents.
> Nor should it have to even know anything about l2_packet. Please also
> note that EAPOL frames can be received through the driver interface to
> better support some platforms. Direct calls to l2_packet would mean this
> option is not available (i.e., reduced OS/network stack support).

For client interaction, uPnP is not an option.
It is not mentioned in the WPS spec and there are various wifi specific 
requirements.
The "M" messages incorporate mac adddresses....
fragmentation is a non-issue, and is anyway WPS specific.

That said, i'm fine with how you are doing it so long as you don't lose the 
mac addresses.

>
> > -- wps_crypto -- key generation, authentication generation and checking.
> > The state data consists only of key data.  Relies on the same underlying
> > crypto routines as wpa_supplicant does (including can use the compact
> > internal routines).  Some of this will be useful for wps server.
>
> Some of this should really be integrated into src/crypto and only the
> WPS specific parts should remain in wps_crypto. For example, the current
> version seems to implement HMAC-SHA256 which is already available in
> src/crypto/sha256.c.

Yes, i see that hmac_sha256_vector has been added? since i originally wrote 
this code and that it appears to be the same algorithm.
(My implementation has the advantage of handling any number of elements 
instead of being limited to a specific number, but that is not is not a big 
practical problem).
I've added that to my list.

However, i think the rest of wps_crypto.c is pretty much WPS specific...


>
> > -- wpse_sm - enrollee state machine. The state data for the state machine
> > consists of: configuration parameters; copies of packets sent and
> > received; key state.  wpse_sm does NOT send or receive any packets, nor
> > does it generate timeouts,  instead the next higher level queries wpse_sm
> > and does the jobs for it.  This will simplify using this code in e.g. new
> > embedded applications.
>
> Does this really need to keep all possible packets (struct
> wps_sm_packet_buffers) in memory all the time? That structure is close
> to 30 kB.. Where does the 1520 byte maximum come from? WPS spec does not
> seem to define a maximum length and at least EAP transport could handle
> up to 64 kB packets..

Regarding 1520 byte max:
In practice, no WPS implementation is going to come close to ethernet packet 
size (1500+ bytes) and there is no reason to think this will change anytime 
soon... there is a lot of reason to keep everything fitting in one packet.
Although the WPS standard specifies a method for fragmentation, wsccmd (the 
original defining implementation) doesn't bother to implement it.
However, there is something to be said for generality...

It is not necessary to keep all the packets, and some applications might be 
bothered by a 30 kB allocation.
It IS necessary to keep a copy of the last packet sent.


>
> Like I mentioned above, I don't think Ethernet/EAPOL/EAP processing
> belongs here. While I really do not like the idea of UPnP, it sounds
> better to keep the interface designed in a way that would handle, if
> needed, both EAP and UPnP transports, assuming this can be done without
> much extra complexity.

In some sense it is just a formatting issue.
Using an ethernet dix format is one way of encapsulating all of the needed 
information into one data structure (instead of e.g. having to pass 
additional subroutine arguments).
Please note that WPS >does< need to know our mac address being used... you 
cannot hide this information.
For security reasons, it is probably a good idea to check the address of the 
AP as well.

It is not a big change however to the code that i wrote to skip the lower 
levels, to the extent consistent with knowing our mac address.

>
> > -- wpse_supplicant -- enrollee interface to the supplicant, it commands
> > the supplicant (via wpa_ctrl mechanism, using socket files on linux) to
> > associate with the desired ssid in open mode... note that wpa_supplicant
> > runs the whole time. This portion could be easily replaced to e.g.
> > perform supplicant actions directly.
>
> If the enrollee code will run as a separate process, ctrl_iface is a
> proper place was interfacing with wpa_supplicant. However, if this is in
> the same process, something else should be used.

Some sort of ctrl_iface connection is needed assuming that the user will want 
to direct the use of WPS.

>
> > Currently, wps_enrollee is a separate program, and no modifications to
> > wpa_supplicant were necessary (except for the Makefile and defconfig, to
> > make wps_enrollee)... this is certainly the safe road for early
> > development. I've gotten the feedback from you that for various reasons
> > it would be better if it were part of wpa_supplicant.  My thinking is
> > that it can be linked as part
> > of the wpa_supplicant program yet still logically sit above (the rest of)
> > wpa_supplicant... i hope you agree with that. My intention is to extend
> > the wpa_ctrl mechanism to include control from within the same process or
> > just bypass wpa_ctrl entirely.
>
> I would agree that it would be fine to have the WPS Registration
> Protocol implemented as a separate component above wpa_supplicant.
> However, I do not think I would go as far with the full WPS
> implementation that would only use wpa_supplicant to associate with the
> AP and then take care of all EAPOL/EAP processing.

No problem.

>
> The way I've been thinking of the WPS process to go would be something
> like this:
> - wpa_supplicant is running; maybe with empty configuration, but still,
>   running and able to provide scan results
> - OS specific network management, say NetworkManager (NM), monitors
>   network configuration and scan results and finds that no configured
>   networks are available, but there is a WPS-enabled AP that could
>   potentially be used

That is possible, or user may want to add a new network even though they have 
other networks.
More importantly, there may be MANY APs that are WPS capable, but they are not 
WPS-ready until the user pushes the button or enters PIN which is further 
down in the process.

> - NM requests wpa_supplicant to start WPS with an AP

Wait!
We have to get the user to push the button on the AP, and possibly tell us 
what PIN to use, or possibly have us provide a PIN and tell the AP what PIN 
to use.
Only then will the AP be WPS-ready.
The standard says you are supposed to do a scan indicating that you want to do 
WPS in probe requests, and check in probe responses for readiness... and (for 
push button method, which will be most commonly used) there must be exactly 
one that is ready.

> - wpa_supplicant configures the driver for WPS and requests association
>   with the BSS
> - wpa_supplicant takes care of EAPOL and EAP processing; EAP-WSC payload
>   may be handled either in-process (integrated Enrollee/Registrar) or by
>   sending it to an external process (Enrollee/Registrar) (the mechanism
>   for this could be separate from ctrl_iface)
> - wpa_supplicant notifies NM about progress and if needed, requests
>   information from the user (say, PIN)

That had to be done way before...

> - wpa_supplicant notifies NM of completion of WPS and availability of
>   network parameters
> - wpa_supplicant could internally update its configuration and/or wait
>   for NM to do that
>
> > The wpa_ctrl mechanism is in my opinion rather weak, and could use some
> > extensive rework (in contrast to most of your code which is quite good).
> > It uses a text based communication protocol which isn't very easy to
> > extend.
>
> Could you please elaborate? I don't see why text based protocol would
> make it harder to extend. ctrl_iface was certainly not designed for
> in-process communication, but if there are areas that would benefit from
> changes to support external processes better, I would be interested in
> hearing more details.

Nothing to do with being text-based.
Everything to do with being (with some exception) positional parameter based.
Much better would be to use a tag=value approach.

It would also be really helpful to have unified text parsing instead of having 
to do it adhoc everywhere.
It would also be very helpful if wpa_ctrl.c provided friendly data structures 
and access routines for all remote procedure calls, e.g. for each current 
command.

wpa_ctrl_request allows specifying a callback routine, which is good except 
that there is no provision to pass a cookie to the callback routine!
I had to use static data to work around this, which is not good!

Minor things:
The specification for an alternative to /var/run/wpa_supplicant is painful;
using an environmental variable might be a reasonable approach.









From ted  Mon Dec  3 21:18:07 2007
From: ted (Ted Merrill)
Date: Mon, 3 Dec 2007 21:18:07 -0800
Subject: Another WPS effort
Message-ID: <200712032118.07869.ted@atheros.com>


Just recently i found the following. Saice Corporation is an obscure Japanese 
company, and the relation of this web site to Saice Corporation is even more 
obscure; none the less there is a lot of effort re. WPS evident on this site.

https://www.saice-wpsnfc.bz/data/NFC631KT_Software_for_Wi-Fi_Protected_Setup_Resource_Packages_Description.pdf
https://www.saice-wpsnfc.bz/




From j  Mon Dec  3 22:10:49 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 22:10:49 -0800
Subject: wps_enrollee cleaned up code
In-Reply-To: <200712032056.19283.ted@atheros.com>
References: <200711121347.57122.ted@atheros.com>
	<20071202184221.GZ5698@jm.kir.nu>
	<200712032056.19283.ted@atheros.com>
Message-ID: <20071204061049.GG5698@jm.kir.nu>

Some comments here.. I didn't have time go through everything today, so
I skipped some parts of the message for now.


On Mon, Dec 03, 2007 at 08:56:19PM -0800, Ted Merrill wrote:

> I would hope at least that we fix the impediments in the way of any WPS 
> solution first.... such as the fix for IEEE80211_IOCTL_FILTERFRAME 
> handling...

Sure, getting the driver interfaces sorted out was next on my list since
that is needed regardless of how the rest of WPS is implemented.

> On Sunday 02 December 2007 10:42:22 Jouni Malinen wrote:
> > existing EAPOL/EAP implementation looks much cleaner. I've added EAP-WSC
> > implementation (just the EAP specific functionality) into my Git tree
> > for both the EAP server and peer.
> 
> Do you have to call it WSC? that name  is obsolete and just confuses people.

As far as I know, the full mechanism is called Wi-Fi Protected Setup
(WPS), but the EAP method itself is still EAP-WSC, not EAP-WPS. As such,
it is not obsolete in naming the EAP method. Sure, it may confuse
people, but I would expect this part to end up being just an internal
name and the option that will be enabled will just be plain CONFIG_WPS
(which will end up enabling EAP-WSC into the build).

> Also, what you call "peer" the WPS spec calls "enrollee" and "client"... or 
> perhaps i'm missing something... although i see it is a general naming 
> convention you use....

I think there is some confusion here.. EAP peer is the "client" side of
EAP (the part that is run in IEEE 802.1X Supplicant) while EAP server
is the "server" part (run in IEEE 802.1X Authenticator). WPS spec
defines different roles like Enrollee and Registrar which may be run in
either the Supplicant or Authenticator (i.e, Supplicant can function as
a Registrar when adding an external Registrar as part of initial AP
setup and this case the EAP peer actually is not operating as an
Enrollee).

> -- I don't see our mac address in the data structures... it will be required 
> to be known somehow.  Knowing the ap's address may be required also.

Sure and I was planning on passing this information to EAP layer from
the EAPOL statemachine or making it easy for the WPS Registration
Protocol part to access association information. This was just not
needed for the EAP method itself, so I left it waiting for more proper
design of the EAP method <-> WPS Registration Protocol <-> rest of the
client interfaces.

> -- It obtains EAP identity from configuration from wpa_ssid but this is 
> inappropriate since essentially WPS has hijacked this... and anyway, 
> eap_server/eap_wsc.c should ALWAYS use WFA-SimpleConfig-Registrar-1-0 and is 
> always the registrar or the proxy thereof, and similarly for the client side 
> code which will NOT be a registrar.

This doesn't sound correct. EAP server for EAP-WSC can act both as the
Registrar (add a new Enrollee case) and Enrollee (and a new external
Registrar case). The identity from EAP-Response/Identity is used to
select which one is being used here. Similarly, the client side (EAP
peer) will need to be able to do both Enrollee and Registrar roles.

I think a good first step would be to just support the
Supplicant/Enrollee and Authenticator/Registrar case, but the EAP method
implementation itself should not be limited to this case.

> -- You could use a file for shared data definitions

Sure. This is still in the phase of figuring out what exactly is going
to be sharable between EAP server and peer.

> -- You have plain numbers in the code that should be #ifdefed

Many of the numbers will disappear when the dummy registrar protocol
test code (wps_* functions) is removed. The remaining couple of numbers
could be cleaned up at some point.

> -- Where did you get the size 2000 from?

I'm assuming you are referring to the size of the M7/M8. 2000 was just a
round number that is large enough for testing fragmentation. All the
wps_* functions are going to disappear from eap_wsc.c once a more
complete interface for EAP <-> registration protocol is ready.

> Some sort of packet buffer management scheme (perhaps not quite as fancy as 
> skbuf :~) would help i suppose.

I have that on my todo list and actually, I already implemented this
couple of weeks ago. However, this would have ended changing all EAP
method interfaces which is something that I did not want to do at that
time. I'm still unclear on whether this really should happen now in
0.6.x, but it may if I get to it again soon ;-). I do have a patch file
that does this for bit over half of the EAP methods in my Git tree.
However, this EAP method interface is one of the interfaces that I do
not like to be changing very frequently (along the driver_ops interface)
in a way that would be backwards incompatible.

> For client interaction, uPnP is not an option.

Depends on what one means with "client", I guess. The WPS Registration
Protocol is used to register external registrars and this can happen
over UPnP.

> Regarding 1520 byte max:
> In practice, no WPS implementation is going to come close to ethernet packet 
> size (1500+ bytes) and there is no reason to think this will change anytime 
> soon... there is a lot of reason to keep everything fitting in one packet.
> Although the WPS standard specifies a method for fragmentation, wsccmd (the 
> original defining implementation) doesn't bother to implement it.
> However, there is something to be said for generality...

WPS supports vendor-specific extensions and as such, there may be need
for passing more information. In such a case, the other end can be
assumed to support the spec and not be limited on what a reference
implementation supports. Anyway, EAP-WSC fragmentation is relatively
simple and hidden in the EAP method implementation (i.e., WPS
registration protocol does not need to know about this at all).

> > Like I mentioned above, I don't think Ethernet/EAPOL/EAP processing
> > belongs here.

> In some sense it is just a formatting issue.
> Using an ethernet dix format is one way of encapsulating all of the needed 
> information into one data structure (instead of e.g. having to pass 
> additional subroutine arguments).

That is just one part of it. The other part is duplicating EAPOL and EAP
state machine and that is something I don't want to see.

> Please note that WPS >does< need to know our mac address being used... you 
> cannot hide this information.

WPS Registration Protocol does need it, the EAP method part does not.

> For security reasons, it is probably a good idea to check the address of the 
> AP as well.

Sure and this can also be made available.

> > - OS specific network management, say NetworkManager (NM), monitors
> >   network configuration and scan results and finds that no configured
> >   networks are available, but there is a WPS-enabled AP that could
> >   potentially be used
> 
> That is possible, or user may want to add a new network even though they have 
> other networks.
> More importantly, there may be MANY APs that are WPS capable, but they are not 
> WPS-ready until the user pushes the button or enters PIN which is further 
> down in the process.

Sure, but the network management GUI on the device will likely need to
tell the user to do this.

> > - wpa_supplicant takes care of EAPOL and EAP processing; EAP-WSC payload
> >   may be handled either in-process (integrated Enrollee/Registrar) or by
> >   sending it to an external process (Enrollee/Registrar) (the mechanism
> >   for this could be separate from ctrl_iface)
> > - wpa_supplicant notifies NM about progress and if needed, requests
> >   information from the user (say, PIN)
> 
> That had to be done way before...

Depends on the case.. If there are multiple registrars, the
EAPOL/EAP-WSC processing is started and M2/M2D messages may be needed to
figure out what exactly is to be set and where. The cases of
Supplicant/client acting as a Registrar to configure an AP will be an
extra complexity here on top that. I did not go through all the
possibilities and what inputs are needed for them, but I'd guess that
should be done at some point ;-).

> > Could you please elaborate? I don't see why text based protocol would
> > make it harder to extend. ctrl_iface was certainly not designed for
> > in-process communication, but if there are areas that would benefit from
> > changes to support external processes better, I would be interested in
> > hearing more details.
> 
> Nothing to do with being text-based.
> Everything to do with being (with some exception) positional parameter based.
> Much better would be to use a tag=value approach.

That sounds reasonable if the commands start getting more parameters and
it can be done for new commands.

> It would also be really helpful to have unified text parsing instead of having 
> to do it adhoc everywhere.
> It would also be very helpful if wpa_ctrl.c provided friendly data structures 
> and access routines for all remote procedure calls, e.g. for each current 
> command.

That sounds reasonable, but this will likely need to be something that
is on top of wpa_ctrl and separate for hostapd and wpa_supplicant (both
of which are using the same mechanism for sending messages over
ctrl_iface).

> wpa_ctrl_request allows specifying a callback routine, which is good except 
> that there is no provision to pass a cookie to the callback routine!
> I had to use static data to work around this, which is not good!

That's a good point. I ended up using two connections to avoid the need
for msg_cb when working on a GUI, so this did not come up. Anyway, this
certainly needs to be fixed as long as the msg_cb case remains in
wpa_ctrl.

> The specification for an alternative to /var/run/wpa_supplicant is painful;
> using an environmental variable might be a reasonable approach.

I think that all Linux distros that I've heard of use the "default
directory", so this has not been much of an issue so far. Providing a
standard mechanism for wpa_ctrl clients to specify an alternative
directory could be useful. However, this is somewhat more complex due to
the same wpa_ctrl implementation being used both with wpa_supplicant and
hostapd.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Mon Dec  3 22:22:22 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 22:22:22 -0800
Subject: Another WPS effort
In-Reply-To: <200712032118.07869.ted@atheros.com>
References: <200712032118.07869.ted@atheros.com>
Message-ID: <20071204062222.GH5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 09:18:07PM -0800, Ted Merrill wrote:

> Just recently i found the following. Saice Corporation is an obscure Japanese 
> company, and the relation of this web site to Saice Corporation is even more 
> obscure; none the less there is a lot of effort re. WPS evident on this site.

Interesting.. I thought the NFC changes would have been on top of the
Intel reference implementation, but the patches from Sony are quite a
bit more than that..

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Mon Dec  3 22:30:44 2007
From: j (Jouni Malinen)
Date: Mon, 3 Dec 2007 22:30:44 -0800
Subject: wpa supplicant on windows mobile?
In-Reply-To: <47547DB5.6090800@skyhookwireless.com>
References: <47547DB5.6090800@skyhookwireless.com>
Message-ID: <20071204063044.GK5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 05:05:41PM -0500, Mike Reinstein wrote:

>  I'm trying to build an app on a  windows mobile that connects to an ap 
> using wpa-psk, sends some data, and disconnects. I tried wpa_supplicant 
> on windows, and it works very well but it's kind of big in terms of 
> footprint, and I really don't need most of the advanced features that 
> the suite provides (wpa2, all of the eap support, etc).
> 
> * is there a way to strip down the code to get a minimal wpa supplicant 
> footprint?

Yes, there are built time options for quite a bit of configuration on
what exactly is built, including removal of WPA2 and EAP support.
Currently, these are much simpler for Makefile based builds, but similar
configuration can be done for visual studio builds, too, with some more
effort in figuring out what exactly the Makefile is doing..

> * are there any resources for people that want to get wpa_supplicant 
> working on windows mobile 5?

wpa_supplicant does not include full support for WM5 in its current
version. Some commercial versions (e.g., DSA Supplicant from
Devicescape) have extended that to full support.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Mon Dec  3 23:42:52 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 4 Dec 2007 13:12:52 +0530
Subject: where to post the log that is as big as 172KB?
Message-ID: <58a444250712032342r69f7219au1f0f2cb352cd749@mail.gmail.com>

Hi,

 I have captured wpa supplicant log, which is of 172KB(detailed log with
-ddd). I cant directly post that to hostap. So I believe i should post that
somewhere and have to pass the link to the group..but dont know where to
post the log?

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071204/4ee30368/attachment.htm 


From AssafH  Tue Dec  4 05:29:41 2007
From: AssafH (Assaf Harel)
Date: Tue, 4 Dec 2007 15:29:41 +0200
Subject: Metalink patches for Intel WPS code
In-Reply-To: <20071202180103.GY5698@jm.kir.nu>
References: <5002BD9FB045734DB9F20119530FB017017424C5@ilmail2.metalink.dsl>
	<5002BD9FB045734DB9F20119530FB01701783C5B@ilmail2.metalink.dsl>
	<20071202180103.GY5698@jm.kir.nu>
Message-ID: <5002BD9FB045734DB9F20119530FB017017C2F16@ilmail2.metalink.dsl>


Jouni,

see embedded marked with >>>.

Regards,
Assaf 

-----Original Message-----
From: Jouni Malinen [mailto:j at w1.fi] 
Sent: Sunday, December 02, 2007 20:01
To: Assaf Harel
Cc: hostap at shmoo.com; Inna Reznik
Subject: Re: Metalink patches for Intel WPS code

On Mon, Nov 26, 2007 at 07:47:30PM +0200, Assaf Harel wrote:

> Metalink released another patch today:
> http://w1.fi/contrib/metalink/Intel_WSC_Metalink_WSC.patch
> This patch updates Intel's original WPS daemon (known as Wsccmd) that 
> runs on top of hostapd / wpa_supplicant.
> 
> Now it is possible to pass wifi WPS certification

Nice to see this type of changes released. I know that number of
companies have worked on modifications to the Intel reference
implementation, but the changes have not usually been released which
leads into duplicate work.

Do you have any plans or do you know of anyone else having plans to
maintain the WSC reference implementation in the future? The Intel web
site for this does not seem to indicate that this code would be
maintained or modified to become production quality code. I'm somewhat
worried about depending on an implementation that does not have someone
maintaining it. Especially so, when there are still number of areas that
would benefit of major cleanup.

>>> We're certainly plan to maintain this code for our own purposes (bug
fixes, specific client support, etc), and we plan to release these
modifications as patches when there will be enough to release. Intel are
working on this as well, at least so they told me on a separate e-mail,
but they are not doing this as a maintenance job, they simply offer next
versions, which clean bugs and support new features. I hope that their
next version will take our modifications into consideration, because we
think it made their package more mature (and certifiable...). 

As far as the EAP method is concerned, there are number of issues with
the original hostapd/wpa_supplicant 0.4.x -based implementation. In
order to go forward on this area, I implemented an EAP method that
provides just the EAP transport part for WPS using the 0.6.x code base
and proper use of expanded EAP header. This, I believe, is also moving
the interface between EAP transport and WPS Registration Protocol into
cleaner location, i.e., doing all EAP specific stuff (including
fragmentation and reassembly and EAP header processing) into the EAP
method while leaving the WPS Registration Protocol to handle WSC M1..M8,
Done, ACK, and NACK.

The current version does not include interface for an external process
for processing the WPS messages. There is only a dummy implementation
that can be used for testing the EAP transport. However, communication
with an external process could be implemented using pending EAP
processing functionality in hostapd/wpa_supplicant to avoid the blocking
calls to external process which is used in the reference WSC code (and
which will not be acceptable for hostapd/wpa_supplicant integration).

>>> I understand where you getting to, and we do plan to connect wsccmd
with 0.6.x version. This is a work in progress here, and it takes us
time, since we don't work with 0.6.x version on our commercial platform.
We'll use the latest git version, to enjoy your latest additions.

The more I look at the reference WSC code, the more I would like to see
this done with simpler design or at least in smaller steps. I think it
would be useful to see a minimal implementation that supports just the
case of AP with an internal Registrar and client with an Enrollee and
only EAP transport (i.e., no UPnP complexity) as the first step. Once
this is available in a clean, maintainable implementation, more
functionality could be added.

I do not like the extra complexity caused by wsccmd being responsible
for starting hostapd/wpa_supplicant with hardcoded command line and
configuration file options. I would much rather see something that
allows both programs to be started (and configured) independently and
then whatever information needs to be transfered between the processes
would go through the ctrl_iface.

Is someone interested in working with a larger design change for the
Intel wsccd code? I have to say that I'm not exactly looking forward to
touching that code myself and would likely find it easier to work with a
new in-process implementation of WPS Registration Protocol as a library
that is designed to fit hostapd/wpa_supplicant model better if I had to
do the work..

>>> Jouni, I agree with you completely. When we started this project we
faced the same questions, and chose to work with Intel for practical
purposes (shorter development time). If you want to start such a
development process, of adding WPS capabilities to
hostapd/wpa_supplicant, I would welcome this effort very much, and can
promise you that we will adopt to that version, once is published, and
offer help as much as required.

-- 
Jouni Malinen                                            PGP id EFC895FA

-- Disclaimer: --
This e-mail is intended solely for the person to whom it is addressed and may contain confidential or legally privileged information. Access to this e-mail by anyone else is unauthorized. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and destroy this e-mail and any attachments. 
E-mail may be susceptible to data corruption, interception, unauthorized amendment, viruses and delays or the consequences thereof. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited.



From maxk  Tue Dec  4 08:22:39 2007
From: maxk (Max Kovalenko)
Date: Tue, 4 Dec 2007 18:22:39 +0200
Subject: WPS implementation from Marvell
Message-ID: <A8D19528FBF27C4691BD90C81EB22ABE03E2999E@rdlnexch03.marvell.com>

On Sun, 2 Dec 2007 10:01:04 -0800, Jouni Malinen wrote:

 

>>The more I look at the reference WSC code, the more I would like to
see this

>>done with simpler design or at least in smaller steps. I think it
would be

>>useful to see a minimal implementation that supports just the case of
AP with

>>an internal Registrar and client with an Enrollee and only EAP
transport 

>>(i.e., no UPnP complexity) as the first step. Once this is available
in 

>>a clean, maintainable implementation, more functionality could be
added.

 

Hi,

 

We've been working for some time here at Marvell for 

a project that required the AP-side of WPS.

 

The main goal was the minimal footprint of the code.

 

As a result, we now have a small SDK written in C and based 

on hostapd-0.4.8. Like others, we looked a lot at the Intel WPS code, 

but made a complete rewrite in C. The design is simple and compact. 

 

Here are some highlights:

 

* ANSI-C, hostapd-like coding style

* wpsd - a stand alone process above Hostapd implementing 

  Internal Registar supporting PIN and PBC;

  wpsd daemon itself is 95Kb only, together with hostapd and 

  openssl-0.9.8f  - 970Kb (not compressed).

* 2 forms of API for applications: Cmd line shell based API,

  C API (a clone of Hostapd ctrl interface)  

* ledd daemon implementing the WPS LED patterns according 

  to the standard, easily customizable for the actual hardware

* extensive regression test suite emulating the client side 

  Enrollee(s) to ensure compliance with the standard

 

We now support only the case of an AP with internal Registrar for the

PIN and Push Button methods. Originally we planned to add support

for External Registrar (wireless and UpnP) as well. However, now that

the WPS dev goes open source we feel it's better to coordinate our 

efforts with others. I got a green light to publish the code, though 

I might need a few days to make it a submittable package. 

 

Is anyone interested? What's the codedrop submission procedure?

 

As part of the work we reduced the effective size of Openssl-0.9.8f

(hundreds of Kbs) and ported it to uclibc. If anyone is interested in 

this patch, we can publish it as well.

 

Best regards,

 

--

Max Kovalenko

WLAN Technical Leader,

Marvell Israel

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


From henrik  Tue Dec  4 09:36:46 2007
From: henrik (Henrik Brix Andersen)
Date: Tue, 4 Dec 2007 18:36:46 +0100
Subject: where to post the log that is as big as 172KB?
In-Reply-To: <58a444250712032342r69f7219au1f0f2cb352cd749@mail.gmail.com>
References: <58a444250712032342r69f7219au1f0f2cb352cd749@mail.gmail.com>
Message-ID: <20071204173646.GD56284@tirith.brixandersen.dk>

On Tue, Dec 04, 2007 at 01:12:52PM +0530, Raghavendra. S wrote:
>  I have captured wpa supplicant log, which is of 172KB(detailed log with
> -ddd). I cant directly post that to hostap. So I believe i should post that
> somewhere and have to pass the link to the group..but dont know where to
> post the log?

You could try http://pastebin.ca/ - I am not sure if they allow that
large pastes.

Brix
-- 
Henrik Brix Andersen <henrik at brixandersen.dk>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 209 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071204/cd9670c4/attachment.pgp 


From j  Tue Dec  4 19:08:45 2007
From: j (Jouni Malinen)
Date: Tue, 4 Dec 2007 19:08:45 -0800
Subject: where to post the log that is as big as 172KB?
In-Reply-To: <20071204173646.GD56284@tirith.brixandersen.dk>
References: <58a444250712032342r69f7219au1f0f2cb352cd749@mail.gmail.com>
	<20071204173646.GD56284@tirith.brixandersen.dk>
Message-ID: <20071205030845.GM5698@jm.kir.nu>

On Tue, Dec 04, 2007 at 06:36:46PM +0100, Henrik Brix Andersen wrote:

> You could try http://pastebin.ca/ - I am not sure if they allow that
> large pastes.

If that doesn't work, I can also post files on the w1.fi server and if
the log file is showing a bug in wpa_supplicant, it would also be
perfectly reasonable to open a new case in Bugzilla (also on
http://w1.fi/) and attach the file into the case.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Tue Dec  4 19:20:09 2007
From: j (Jouni Malinen)
Date: Tue, 4 Dec 2007 19:20:09 -0800
Subject: WPS implementation from Marvell
In-Reply-To: <A8D19528FBF27C4691BD90C81EB22ABE03E2999E@rdlnexch03.marvell.com>
References: <A8D19528FBF27C4691BD90C81EB22ABE03E2999E@rdlnexch03.marvell.com>
Message-ID: <20071205032009.GN5698@jm.kir.nu>

On Tue, Dec 04, 2007 at 06:22:39PM +0200, Max Kovalenko wrote:

> We've been working for some time here at Marvell for 
> a project that required the AP-side of WPS.

> The main goal was the minimal footprint of the code.

> As a result, we now have a small SDK written in C and based 
> on hostapd-0.4.8. Like others, we looked a lot at the Intel WPS code, 
> but made a complete rewrite in C. The design is simple and compact. 

This sounds very interesting! I was hoping to get something small and
suitable as a starting point with internal registrar support and your
description seems to match that quite well.

> We now support only the case of an AP with internal Registrar for the
> PIN and Push Button methods. Originally we planned to add support
> for External Registrar (wireless and UpnP) as well. However, now that
> the WPS dev goes open source we feel it's better to coordinate our 
> efforts with others. I got a green light to publish the code, though 
> I might need a few days to make it a submittable package. 

> Is anyone interested? What's the codedrop submission procedure?

Yes, very much so. You can publish the package on your web server or I
can alternatively host it at http://w1.fi/contrib/ with other WPS
related patches.


> As part of the work we reduced the effective size of Openssl-0.9.8f
> (hundreds of Kbs) and ported it to uclibc. If anyone is interested in 
> this patch, we can publish it as well.

Taken into account that this topic comes up every now and then, it might
be useful to get the patch available somewhere. OpenSSL is not exactly
the easiest piece of software to make smaller, but it is still quite
widely used even in many embedded systems, so options for reducing code
size are quite useful.

I will use more of my time on trying to make sure the integrated
crypto/TLS code option in 0.6.x branch gets more mature and can handle
all the needed functionality, including WPS, to provide an option of
getting the total binary size down quite a bit more, but anyway, I can
host a patch for OpenSSL and you could also ask whether OpenSSL
maintainers would be interested in it.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Tue Dec  4 19:36:46 2007
From: j (Jouni Malinen)
Date: Tue, 4 Dec 2007 19:36:46 -0800
Subject: wpa_supplicant fails to preauthenticate
In-Reply-To: <683e2de40712031043i84bb84btddfbcc77548eee09@mail.gmail.com>
References: <683e2de40712030620t598c78c9ld634c45635b11f2c@mail.gmail.com>
	<20071203145606.GE5698@jm.kir.nu>
	<683e2de40712031043i84bb84btddfbcc77548eee09@mail.gmail.com>
Message-ID: <20071205033646.GO5698@jm.kir.nu>

On Tue, Dec 04, 2007 at 12:13:23AM +0530, Paresh Sawant wrote:

> If we assume that pre-auth is not allowed if the bssid belongs to different
> ssid than one it is already associated with, then would that be right idea
> to make wpa_supplicant report an error instead of initiating the pre-auth by
> sending out eapol start packet ?

I couldn't find a very strong statement from the standard on disallowing
pre-authentication between different ESSes, but the comments in clause
8.4.6 seem to imply that pre-authentication is used only within the
current ESS, i.e., only with the same SSID. Taken into account that
pre-authentication requires layer 2 connectivity between the APs, this
sounds like a reasonable assumption.

wpa_supplicant is actually only adding pre-authentication candidates if
the SSID of the target AP matches the current SSID. The test case you
described uses an external trigger (wpa_cli preauthenticate) to force
wpa_supplicant to start pre-authentication. At this point, the SSID of
the destination BSS is not even known and as such, there is no way of
reporting an error here. The current wpa_supplicant behavior seems
reasonable to me.

> Is it possible to have 2 different access points within same ESS having
> separate security policies e.g. ap1 with WPA2-PSK and ap2 with WPA2-EAP ? I
> don't see IEEE 802.11i enforcing such a rule. please correct me.

There may not be an explicit statement for this in the standard, but
I've heard many comments  on the security policy to be assumed to be
configured consistently throughout the ESS. Though, it should also be
noted that it is possible even for a single AP to advertise support for
both PSK and EAP AKMPs since WPA/RSN IE can include multiple key
management protocols.

-- 
Jouni Malinen                                            PGP id EFC895FA



From archana.gopal  Tue Dec  4 20:23:52 2007
From: archana.gopal (Archana Rajagopal)
Date: Tue, 4 Dec 2007 23:23:52 -0500
Subject: Forwarding packets
Message-ID: <5dd628b40712042023o6bd68c35u7c8afd20f71a25b@mail.gmail.com>

Hi,
    I am using iperf to send traffic through HostAP .By default does HostAP
forward it or should I do something else other than "echo "1" /proc ... "
command.
Moreover , can you explain how it actually forwards packets not destined to
it?
The problem that I am facing is not exactly related to hostap I
guess.Theproblem is..
When I send iperf traffic through HostAP with ToS bits set , it is changing
the ToS bits somehow and not classifying any packets.This happens only when
the packet is to be forwarded to another system.Is HostAP responsible for
this or is it a kernel problem(I am using kernel version 2.6.16).

Please do clarify.

-- 
Regards
Archana Rajagopal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071204/74211677/attachment.htm 


From j  Tue Dec  4 20:40:43 2007
From: j (Jouni Malinen)
Date: Tue, 4 Dec 2007 20:40:43 -0800
Subject: Forwarding packets
In-Reply-To: <5dd628b40712042023o6bd68c35u7c8afd20f71a25b@mail.gmail.com>
References: <5dd628b40712042023o6bd68c35u7c8afd20f71a25b@mail.gmail.com>
Message-ID: <20071205044043.GP5698@jm.kir.nu>

On Tue, Dec 04, 2007 at 11:23:52PM -0500, Archana Rajagopal wrote:

> When I send iperf traffic through HostAP with ToS bits set , it is changing
> the ToS bits somehow and not classifying any packets.This happens only when
> the packet is to be forwarded to another system.Is HostAP responsible for
> this or is it a kernel problem(I am using kernel version 2.6.16).

If by "forward" you are referring to IP routing, this does not sound
like something that would be specific to Host AP driver in any way,
i.e., this is something that would be configured in the IP stack.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ambedkar_r  Tue Dec  4 20:58:42 2007
From: ambedkar_r (Ambedkar R)
Date: 5 Dec 2007 04:58:42 -0000
Subject: Forwarding packets
Message-ID: <20071205045842.1960.qmail@webmail100.rediffmail.com>

Hi Archana,

Could you please give more information that what you are looking exactly + Setup info?

Thanks
Ambedkar.R ?


On Wed, 05 Dec 2007 Archana Rajagopal wrote :
>Hi,
>     I am using iperf to send traffic through HostAP .By default does HostAP
>forward it or should I do something else other than "echo "1" /proc ... "
>command.
>Moreover , can you explain how it actually forwards packets not destined to
>it?
>The problem that I am facing is not exactly related to hostap I
>guess.Theproblem is..
>When I send iperf traffic through HostAP with ToS bits set , it is changing
>the ToS bits somehow and not classifying any packets.This happens only when
>the packet is to be forwarded to another system.Is HostAP responsible for
>this or is it a kernel problem(I am using kernel version 2.6.16).
>
>Please do clarify.
>
>--
>Regards
>Archana Rajagopal
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071205/df861888/attachment.htm 


From ambedkar_r  Tue Dec  4 21:16:26 2007
From: ambedkar_r (Ambedkar R)
Date: 5 Dec 2007 05:16:26 -0000
Subject: wpa_supplicant fails to preauthenticate
Message-ID: <20071205051626.19961.qmail@webmail73.rediffmail.com>

 Hi,

Since you have configured with different security and SSID policy for two different AP's,you can't perform Pre-Authentication.

To perform Pre-Authentication following things are required,they are
1.AP should have the support for WPA2-Enterprise/CCMP
2.Client should support for Pre-Authentication.

Configure AP1 and AP2 with same SSID and Security Policy(WPA2-Enterprise desired)


Thanks
Ambedkar.R?


On Tue, 04 Dec 2007 Paresh Sawant wrote :
>If we assume that pre-auth is not allowed if the bssid belongs to different
>ssid than one it is already associated with, then would that be right idea
>to make wpa_supplicant report an error instead of initiating the pre-auth by
>sending out eapol start packet ?
>
>Is it possible to have 2 different access points within same ESS having
>separate security policies e.g. ap1 with WPA2-PSK and ap2 with WPA2-EAP ? I
>don't see IEEE 802.11i enforcing such a rule. please correct me.
>
>Cheers
>- Paresh
>
>On Dec 3, 2007 8:26 PM, Jouni Malinen <j at w1.fi> wrote:
>
> > On Mon, Dec 03, 2007 at 07:50:44PM +0530, Paresh Sawant wrote:
> >
> > >            I'm trying to make wpa_supplicant ( on windows XP with
> > > CONFIG_USE_NDISUIO ) preauthenticate with ap2 while it is already
> > associated
> > > with ap1. Following are the network blocks I've specified in .conf -
> > >
> > > network={
> > >     ssid="ap1"
> > >     key_mgmt=WPA-PSK
> >
> > > network={
> > >     ssid="ap2"
> > >     key_mgmt=WPA-EAP
> >
> > I wouldn't be surprised if pre-authentication would not work when
> > associated with a WPA-PSK AP. This is somewhat odd configuration of RSN
> > pre-authentication. I don't remember whether this is even allowed in the
> > IEEE 802.11 standard. Anyway, it looks like the problem here could be in
> > use of different SSIDs. I've only ever heard of pre-authentication used
> > within the same ESS, i.e., between APs that use the the same SSID.
> >
> > Is this kind of network really deployed somewhere or is this just a test
> > case?
> >
> > --
> > Jouni Malinen                                            PGP id EFC895FA
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071205/82780c7b/attachment.htm 


From s.raghu  Wed Dec  5 02:15:46 2007
From: s.raghu (RAGHAVENDRA SADARAMACHANDRA)
Date: Wed, 05 Dec 2007 10:15:46 +0000 (GMT)
Subject: WPA-PSK/TTLS problem on Marvell 8686...[SOLVED]
Message-ID: <0JSK001ZMN6AMK@ms13.samsung.com>

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


From m.sukumar  Wed Dec  5 06:25:23 2007
From: m.sukumar (Sukku)
Date: Wed, 5 Dec 2007 19:55:23 +0530
Subject: ndiswrapper + wpa_supplicant
Message-ID: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>

Hi All,

>From last two weeks, I am working on this problem. I am working on FC8 with
kernel version 2.6.23.1-42.

I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
drivers for this device. so by using ndiswrappers I installed windows native
drives in linux box. finally adapter got detected.

after words  I try to use this  wpa_supplicant on this adapter.  Hear I am
facing problem

In debugging mode  I am getting so many IOCTL errors. I am not getting,
there errors are from ndiswrapper or wpa_supplicant.

plz help me in this regard.

my setup details:

*wireless adapter*: Linksys WUSB54G
*
ndiswrappers version:*

[root at sukumar wpa_supplicant]# ndiswrapper -l
rt2500usb : driver installed
        device (13B1:000D) present (alternate driver: rt2500usb)

[root at sukumar wpa_supplicant]# ndiswrapper -v
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename:       /lib/modules/2.6.23.1-42.fc8
/extra/ndiswrapper/ndiswrapper.ko
version:        1.48
vermagic:       2.6.23.1-42.fc8 SMP mod_unload 686 4KSTACKS



*wpa_supplicant logs:*

[root at sukumar wpa_supplicant]# wpa_supplicant -D wext -iwlan0 -c
/etc/wpa_supplicant/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf
'/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A'
bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' ->
'/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel' (DEPRECATED)
ap_scan=2
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=10):
                  XXXXXXX
scan_ssid=1 (0x1)
key_mgmt: 0x1
eap methods - hexdump(len=16): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 00
00
identity - hexdump_ascii(len=7):
     64 65 66 61 75 6c 74                              default
password - hexdump_ascii(len=7): [REMOVED]
Priority group 0
   id=0 ssid='XXXXXX'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:18:39:05:26:46
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
*ioctl[SIOCSIWAUTH]: Operation not supported*
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
*ioctl[SIOCSIWAUTH]: Operation not supported*
WEXT auth param 5 value 0x1 - Setting scan request: 0 sec 100000 usec
ctrl_interface_group=10 (from group name 'wheel')
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'XXXXXX'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 30 pairwise 24 key_mgmt 1 proto 2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00
00 0f ac 04 01 00 00 0f ac 01 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
*ioctl[SIOCSIWAUTH]: Operation not supported*
WEXT auth param 5 value 0x1 - State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=18
CTRL_IFACE monitor attached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63
74 72 6c 5f 32 38 30 34 2d 38 30 00
RX ctrl_iface - hexdump_ascii(len=10):
     49 4e 54 45 52 46 41 43 45 53                     INTERFACES
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS
*ioctl[SIOCGIFADDR]: Cannot assign requested address*
RX ctrl_iface - hexdump_ascii(len=13):
     4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53            LIST_NETWORKS
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING
CTRL-EVENT-TERMINATING - signal 2 received
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74
72 6c 5f 32 38 30 34 2d 38 30 00
Removing interface wlan0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - No keys have been configured - skip key
clearing
CTRL_IFACE wait for attached monitors to receive messages
cCancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6



Thanks and regards,
Sukumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071205/81788693/attachment.htm 


From gnwiii  Wed Dec  5 07:09:56 2007
From: gnwiii (George N. White III)
Date: Wed, 5 Dec 2007 11:09:56 -0400
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
Message-ID: <22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>

On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> Hi All,
>
> From last two weeks, I am working on this problem. I am working on FC8 with
> kernel version 2.6.23.1-42.
>
> I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
> drivers for this device. so by using ndiswrappers I installed windows native
> drives in linux box. finally adapter got detected.
>
> after words  I try to use this  wpa_supplicant on this adapter.  Hear I am
> facing problem
>
> In debugging mode  I am getting so many IOCTL errors. I am not getting,
> there errors are from ndiswrapper or wpa_supplicant.

I saw those errors, and failed to connect, also using FC8 with a ndiswrapper
but a different  USB dongle (TEW).    However, NetworkManager is more or
less working (too frequent disconnects from my AP, connects to random
open AP's).   Check that there isn't a 2nd copy of wpa_supplicant running.

Have you tried NetworkManager?

-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia



From dcbw  Wed Dec  5 07:17:14 2007
From: dcbw (Dan Williams)
Date: Wed, 05 Dec 2007 10:17:14 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
Message-ID: <1196867834.2519.7.camel@localhost.localdomain>

On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > Hi All,
> >
> > From last two weeks, I am working on this problem. I am working on FC8 with
> > kernel version 2.6.23.1-42.
> >
> > I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
> > drivers for this device. so by using ndiswrappers I installed windows native
> > drives in linux box. finally adapter got detected.
> >
> > after words  I try to use this  wpa_supplicant on this adapter.  Hear I am
> > facing problem
> >
> > In debugging mode  I am getting so many IOCTL errors. I am not getting,
> > there errors are from ndiswrapper or wpa_supplicant.
> 
> I saw those errors, and failed to connect, also using FC8 with a ndiswrapper
> but a different  USB dongle (TEW).    However, NetworkManager is more or
> less working (too frequent disconnects from my AP, connects to random
> open AP's).   Check that there isn't a 2nd copy of wpa_supplicant running.

NM itself will only ever connect to an AP that you've chosen from the
menu.

If you've never chosen that AP from the menu, it's important to remember
that the driver and/or firmware also control roaming, and that
often-times the driver/firmware will decide to associate to an access
point without being told to so (ipw* does this a lot).  Some drivers
have module options to disable that functionality, and the only real
arguments I've heard for this behavior are that people alone in the
woods then don't need to issue manual iwconfig commands when they start
their computer up.  I'm not sure what the security implications of the
card connecting to a random open AP are, but it can't be much good.

dan





From dcbw  Wed Dec  5 07:23:01 2007
From: dcbw (Dan Williams)
Date: Wed, 05 Dec 2007 10:23:01 -0500
Subject: WPA-PSK/TTLS problem on Marvell 8686...[SOLVED]
In-Reply-To: <0JSK001ZMN6AMK@ms13.samsung.com>
References: <0JSK001ZMN6AMK@ms13.samsung.com>
Message-ID: <1196868181.2519.13.camel@localhost.localdomain>

On Wed, 2007-12-05 at 10:15 +0000, RAGHAVENDRA SADARAMACHANDRA wrote:
> 
> Hi Scott, 
> 
>   Issue solved. Actually in our company primises AP operating in Wi-Fi
> zone should be registered with security. The access point that I was
> using was not registered with the security. Because of my wpa
> supplicant was getting Wireless event: new AP 00:00:00:00:00:00
> message and used to get disconnected immediately.
> 
>   So final conclusion is Wi-Fi security system was sending that event.
> OK now my WPA-EAP/WPA-PSK all are working. But still I have few
> doubts?
> 
> 1. All these security algorithms related to WPA. Whether they are
> implemented in supplicant code or driver or chip? 

They are implemented in hardware/firmware on the card, or in the driver
if the card is a softmac-type card.

>  I believe few of the encryption techniques must be provided by
> chip/driver..
> 
>   Can any one tell me which all encryption methods are supported by
> marvell 8686 card?

The 8686 is a fullmac type part, meaning that the WEP, TKIP, and CCMP
encryption algorithms are implemented in firmware (with hardware assist)
on the 8686 itself.  The driver does not handle _any_ encryption for the
8686.

> Also I have got OpenSSL: tls_connection_handshake - Failed to read
> possible Application Data error:00000000:lib(0):func(0):reason(0), 

If you see a message about "want more data" below that error, that is
probably something you can ignore.  SSL operates on _blocks_ of data,
and therefore requires a full block to decrypt.  However, because
networks don't guarantee to always send the entire block of data at the
same time, SSL needs to wait sometimes for the rest of the data to show
up.  You don't want to block on waiting for that data, because it might
be 10 minutes until it shows up.  So that specific OpenSSL call fails,
but returns the error code EAGAIN (or something like that), which tells
the caller (in this case wpa_supplicant) to retry when it wants to.  It
may be that wpa_supplicant is unconditionally reporting the error, but
still retries.  If that is correct, the error is harmless.  I just means
that wpa_supplicant is waiting for more data from the AP before it can
proceed.

Dan

> Is this going to harm anyway? See below log. Any body has idea about
> when this occurs?
> 
>  
> 
> # ./wpa_supplicant -ieth0 -Dmarvell -c./wpa_supplicant.ttls.conf -w
> 
> ioctl[SIOCSIWPMKSA]: Invalid argument
> 
> Trying to associate with 00:13:46:b6:77:c4 (SSID='dlink' freq=2437
> MHz)
> 
> Associated with 00:13:46:b6:77:c4
> 
> CTRL-EVENT-EAP-STARTED EAP authentication started
> 
> CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
> 
> X509_verify_cert: create new chain and
> insert /C=US/ST=Tennessee/L=Brentwood/O=Helava/OU=Engineering/CN=HAI/emailAddress=ohb at cmcast.net.
> 
> X509_verify_cert: try to find issuer of x in untrusted stack.
> 
> X509_verify_cert: loop (0th) find issuer in untrusted stack =====>
> 
> X509_verify_cert: current x
> = /C=US/ST=Tennessee/L=Brentwood/O=Helava/OU=Engineering/CN=HAI/emailAddress=ohb at cmcast.net
> 
> X509_verify_cert: depth = 9, chain num = 1
> 
> X509_verify_cert: issuer information to find...
> 
> X509_verify_cert:    * US
> 
> X509_verify_cert:    * Tennessee
> 
> X509_verify_cert:    * Brentwood
> 
> X509_verify_cert:    * Helava
> 
> X509_verify_cert:    * Engineering
> 
> X509_verify_cert:    * HAI
> 
> X509_verify_cert:    * ohb at cmcast.net
> 
> X509_verify_cert: x is root cert. break loop.
> 
> X509_verify_cert: current chain num = 1.
> 
> X509_verify_cert: last cert x in chain
> = /C=US/ST=Tennessee/L=Brentwood/O=Helava/OU=Engineering/CN=HAI/emailAddress=ohb at cmcast.net.
> 
> X509_verify_cert: last cert x in untrusted stack is self-signed cert.
> 
> X509_verify_cert: chain number is only one
> 
> OpenSSL: tls_connection_handshake - Failed to read possible
> Application Data error:00000000:lib(0):func(0):reason(0)
> 
> CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
> 
> WPA: Key negotiation completed with 00:13:46:b6:77:c4 [PTK=TKIP
> GTK=TKIP]
> 
> CTRL-EVENT-CONNECTED - Connection to 00:13:46:b6:77:c4 completed
> (auth) [id=0 id_str=]
> 
>  
> 
> -Raghu.
> 
>  
> 
>  
> 
>  
> 
> 
> 
> ------- Original Message -------
> Sender : ???<scott_liu at amit.com.tw>
> Date : Dec 01, 2007 15:04 (GMT+09:00)
> Title : Re: WPA-PSK problem on Marvell 8686...Help Plz
> 
>   
> 
> I've also encountered the same problem with you, I think you are using
> Marvell 8686 with SDIO interface on linux kernel 2.4 or 2.6 ?? If 2.6,
> then you could use -Dwext is suitable (wireless extension is grater
> than v18), or(this way is sutible for 2.4 and 2.6) one patch file
> might attach in the tar file with wpa-supplicant-0.5.7 marvell gave
> you, so that you can patch it and will see driver_marvell.c, after
> compiler successful, you could execute -Dmarvell to associate with
> your encryption AP. 
> 
> 
> Scott Liu 
> 
> Best regards.
> 
> 
>         -----Original Message-----
>         From: RAGHAVENDRA SADARAMACHANDRA <s.raghu at samsung.com>
>         To: hostap at shmoo.com
>         Date: Fri, 30 Nov 2007 11:48:34 +0000 (GMT)
>         Subject: WPA-PSK problem on Marvell 8686...Help Plz
>         
>         Hi All, 
>            I have to configure WPA-PSK on Marvell 8686. They have
>         given ported version of wpa supplicant 0.5.7 with the driver.
>         Compiled it and enabled....But no success. I am using Linksys
>         WAP54G Access Point. I tried for over 3 days...but cudn't find
>         out the problem. 
>         
>           
>         
>         I have following doubts 
>         
>           
>         
>         1. ioctl[SIOCSIWFREQ]: Operation not supported, does this
>         indicate marvell driver's problem?
>         
>         
>         
>         2. WPA: 4-Way Handshake failed - pre-shared key may be
>         incorrect, here i entered psk="data1234" which is same as that
>         entered in linksys  AP. But still getting this junk error?
>         
>          
>         
>         MY AP configuration is
>         
>          
>         
>         # iwlist eth0 scanning
>         
>         eth0      Scan completed :
>         
>                   Cell 01 - Address: 00:0F:CB:FE:2F:5F
>         
>                             ESSID:"3Com"
>         
>                             Mode:Managed
>         
>                             Frequency:2.412 GHz (Channel 1)
>         
>                              Quality:0/100  Signal level=-45 dBm
>         Noise level=-96 dBm
>         
>                             Encryption key:on
>         
>                             Bit Rates:54 Mb/s
>         
>                             IE: WPA Version 1
>         
>                                 Group Cipher : TKIP
>         
>                                 Pairwise Ciphers (1) : TKIP
>         
>                                 Authentication <?xml:namespace prefix
>         = st1 />Suites (1) : 802.1x
>         
>                   Cell 02 - Address: 00:90:4C:91:00:01 
>         
>                             ESSID:"linksys" [2]
>         
>                             Mode:Managed
>         
>                             Frequency:2.462 GHz (Channel 11)
>         
>                              Quality:0/100  Signal level=-29 dBm
>         Noise level=-96 dBm 
>         
>                             Encryption key:on
>         
>                             Bit Rates:48 Mb/s
>         
>                             IE: WPA Version 1
>         
>                                 Group Cipher : TKIP
>         
>                                 Pairwise Ciphers (1) : TKIP
>         
>                                 Authentication Suites (1) : PSK
>         
>            
>         MY wpa_supplicant.conf configuration is
>         
>          
>         
>         network={
>         
>                         ssid="linksys"
>         
>                        scan_ssid=1
>         
>                         proto=WPA
>         
>                         key_mgmt=WPA-PSK
>         
>                         pairwise=TKIP
>         
>                         group=TKIP
>         
>                         psk="data1234"
>         
>         }
>         
>         I enable wpa_supplicant using below command
>         
>          
>         
>         # ./wpa_supplicant -c./wpa_supplicant.conf -ieth0 
>         
>         ioctl[SIOCSIWPMKSA]: Invalid argument 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: Key negotiation completed with 00:90:4c:91:00:01
>         [PTK=TKIP GTK=TKIP] 
>         
>         CTRL-EVENT-CONNECTED - Connection to 00:90:4c:91:00:01
>         completed (auth) [id=0 id_str=] 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         ioctl[SIOCSIWESSID]: Network is down 
>         
>         ioctl[SIOCSIWAP]: Network is unreachable 
>         
>         Association request to the driver failed 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Associated with 00:00:00:00:00:00 
>         
>         Authentication with 00:00:00:00:00:00 timed out. 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: Key negotiation completed with 00:90:4c:91:00:01
>         [PTK=TKIP GTK=TKIP] 
>         
>         CTRL-EVENT-CONNECTED - Connection to 00:90:4c:91:00:01
>         completed (reauth) [id=0 id_str=] 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         ioctl[SIOCSIWAP]: Network is unreachable 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:00:00:00:00:00 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         WPA: No SSID info found (msg 1 of 4). 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: Key negotiation completed with 00:90:4c:91:00:01
>         [PTK=TKIP GTK=TKIP] 
>         
>         CTRL-EVENT-CONNECTED - Connection to 00:90:4c:91:00:01
>         completed (reauth) [id=0 id_str=] 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: Key negotiation completed with 00:90:4c:91:00:01
>         [PTK=TKIP GTK=TKIP] 
>         
>         CTRL-EVENT-CONNECTED - Connection to 00:90:4c:91:00:01
>         completed (reauth) [id=0 id_str=] 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: 4-Way Handshake failed - pre-shared key may be incorrect 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>         WPA: Key negotiation completed with 00:90:4c:91:00:01
>         [PTK=TKIP GTK=TKIP] 
>         
>         CTRL-EVENT-CONNECTED - Connection to 00:90:4c:91:00:01
>         completed (reauth) [id=0 id_str=] 
>         
>         CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys 
>         
>         Trying to associate with 00:90:4c:91:00:01 (SSID='linksys'
>         freq=2462 MHz) 
>         
>         ioctl[SIOCSIWFREQ]: Operation not supported 
>         
>         Association request to the driver failed 
>         
>         Associated with 00:90:4c:91:00:01 
>         
>           
>         
>           
>         
>         Thanx in Advance.
>         
>         
>         Raghu. 
> 
>  
> 
>  
> 
>  
> 
>  
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From archana.gopal  Wed Dec  5 11:54:40 2007
From: archana.gopal (Archana Rajagopal)
Date: Wed, 5 Dec 2007 14:54:40 -0500
Subject: Hostapd Configuration
Message-ID: <5dd628b40712051154q5954b1a3n34cf7ff1cd0013fb@mail.gmail.com>

Hi,
    I am using kernel version 2.6.16 which has inbuilt hostap driver.Is it
possible to install hostapd 0.4.9 with this kernel.I tried doing it and when
I tried the following command.
"hostapd -B hostapd.conf"
It gave hostap driver initialization failed.
but it created "wlanap" interface.What is this interface?
My prism card automatically loads into interface 'wifi0' which is created by
the system.
But if I activate the card in master,there is a problem in pinging the
Access Point though I could see it.
Moreover the network bridge(Global Sun Technology wireless network bridge)
was loaded on wifi0 when I booted the system but since I could not ping I
changed the network bridge to eth1 and opened a new wireless connection with
nickname wifi0 and device eth1.Now I could ping the Access Point and could
send traffic across it.Atleast the ping worked across the Access point.

Is this setup correct?Also please comment on the "wlanap" interface and
whether hostapd 0.4.9 is compatible with version 2.6.16 kernel's  hostap
driver.


-- 
Regards
Archana Rajagopal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071205/86b8755d/attachment.htm 


From raghavendra.akkasali  Wed Dec  5 17:15:12 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Thu, 6 Dec 2007 06:45:12 +0530
Subject: Need info about EAP-TTLS and EAP-PEAP
Message-ID: <58a444250712051715h64b81b9cr368e7425ada2ce09@mail.gmail.com>

Hi All,

   Can I support both EAP-TTLS and EAP-PEAP in same supplicant config?

  I mean, i have following wpa_supplicant.conf file which works for
EAP-TTLS.

update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1

network={
        ssid="test"
        scan_ssid=1
        auth_alg=OPEN
        proto=WPA RSN
        key_mgmt=WPA-EAP IEEE8021X
        pairwise=TKIP CCMP
        group=CCMP TKIP WEP104 WEP40
        eap=TTLS
        identity="jbibe"
        anonymous_identity="jbibe"
        password="whatever"
        phase2="autheap=MD5"
        priority=2
}
Can any one tell me what all things I have to add extra or modify. So that I
can use same wpa_supplicant.conf file to support EAP-PEAP also.

Thing I I want end user to configure less number of parameters. To elaborate
this in above config file for EAP-TTLS and end user have to change following
parameters to work in his network.
1. ssid
2. username
3. anonymous - Is this parameter must?
4. password

Other config parameters he need not modify to make EAP-TTLS working.
Similarly I need your help for supporting EAP-PEAP? where as end user modify
only above 3/4 parameters.

Also please let me know if I can support some more methods using same config
file.

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/251ec3bd/attachment.htm 


From raghavendra.akkasali  Wed Dec  5 18:37:28 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Thu, 6 Dec 2007 08:07:28 +0530
Subject: How to support preauthentication...
Message-ID: <58a444250712051837i3bfb2e07heea0aa5be9fdbe84@mail.gmail.com>

Hi All,

        I have following wpa supplicant config file for EAP-TTLS. Can any
one help me in providing preauthentication support.
-------------------------------------------------wpa.conf starts
here---------------------------------------------------
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1

network={
        ssid="test"
        scan_ssid=1
        auth_alg=OPEN
        proto=WPA RSN
        key_mgmt=WPA-EAP IEEE8021X
        pairwise=TKIP CCMP
        group=CCMP TKIP WEP104 WEP40
        eap=TTLS
        identity="jbibe"
        anonymous_identity="jbibe"
        password="whatever"
        phase2="autheap=MD5"
        priority=2
}

----------------------------------------------------------------------------
wpa.conf ends-----------------------------------

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/bd081a46/attachment.htm 


From j  Wed Dec  5 18:57:37 2007
From: j (Jouni Malinen)
Date: Wed, 5 Dec 2007 18:57:37 -0800
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
Message-ID: <20071206025737.GQ5698@jm.kir.nu>

On Wed, Dec 05, 2007 at 07:55:23PM +0530, Sukku wrote:

> ap_scan=2
> ssid - hexdump_ascii(len=10):
>                   XXXXXXX
> scan_ssid=1 (0x1)
> key_mgmt: 0x1
> eap methods - hexdump(len=16): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 00
> 00
> identity - hexdump_ascii(len=7):
>      64 65 66 61 75 6c 74                              default
> password - hexdump_ascii(len=7): [REMOVED]

This configuration is invalid. What kind of security settings are you
trying to use? scan_ssid=1 is not used in ap_scan=2 mode and ap_scan=2
requires that full security policy is configured explicitly (i.e.,
proto, pairwise, group parameters are set when using WPA/WPA2).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec  5 19:01:07 2007
From: j (Jouni Malinen)
Date: Wed, 5 Dec 2007 19:01:07 -0800
Subject: Hostapd Configuration
In-Reply-To: <5dd628b40712051154q5954b1a3n34cf7ff1cd0013fb@mail.gmail.com>
References: <5dd628b40712051154q5954b1a3n34cf7ff1cd0013fb@mail.gmail.com>
Message-ID: <20071206030107.GR5698@jm.kir.nu>

On Wed, Dec 05, 2007 at 02:54:40PM -0500, Archana Rajagopal wrote:

>     I am using kernel version 2.6.16 which has inbuilt hostap driver.Is it
> possible to install hostapd 0.4.9 with this kernel.I tried doing it and when

Should be, but I would recommend using the latest stable hostapd version
(0.5.9).

> I tried the following command.
> "hostapd -B hostapd.conf"
> It gave hostap driver initialization failed.

Please try this first by running the hostapd on foreground and with
debug enabled (replace "-B" with "-dd"). This should provide more
details on what failed.

> but it created "wlanap" interface.What is this interface?

Are you sure it was "wlanap" and not "wlan0ap"? It would likely be the
interface used for management frames.

> My prism card automatically loads into interface 'wifi0' which is created by
> the system.

It should come up with two interfaces, wifi0 and wlan0.

> Moreover the network bridge(Global Sun Technology wireless network bridge)
> was loaded on wifi0 when I booted the system but since I could not ping I
> changed the network bridge to eth1 and opened a new wireless connection with
> nickname wifi0 and device eth1.Now I could ping the Access Point and could
> send traffic across it.Atleast the ping worked across the Access point.

wifi0 is not used with IP/bridging configuration. wlan0 is used for more
or less all operations that relate to network configuration.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec  5 19:06:05 2007
From: j (Jouni Malinen)
Date: Wed, 5 Dec 2007 19:06:05 -0800
Subject: Need info about EAP-TTLS and EAP-PEAP
In-Reply-To: <58a444250712051715h64b81b9cr368e7425ada2ce09@mail.gmail.com>
References: <58a444250712051715h64b81b9cr368e7425ada2ce09@mail.gmail.com>
Message-ID: <20071206030605.GS5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 06:45:12AM +0530, Raghavendra. S wrote:

>    Can I support both EAP-TTLS and EAP-PEAP in same supplicant config?

Yes, but it is somewhat tricky on the phase2 configuration since the
used format is bit different.

>         eap=TTLS

If you want to enable both EAP-TTLS and EAP-PEAP, you would need to
changes this to "eap=TTLS PEAP".

>         phase2="autheap=MD5"

And this to something like phase2="autheap=MD5 auth=MD5" if you want to
use both TTLS and PEAP with a tunneled EAP-MD5. Alternatively, you could
probably leave this phase2 parameter out to allow all EAP methods in
phase 2.

> 3. anonymous - Is this parameter must?

anonymous_identity can be used to set the phase 1 identity. If it is not
configured the phase 2 identity is used for both phase 1 and 2 (i.e.,
the value from 'identity' field is used in both cases). If identity
protection is not needed (phase 1 identity is sent in clear; phase 2
identity is encrypted), anonymous_identity is not needed in the
configuration.

> Other config parameters he need not modify to make EAP-TTLS working.
> Similarly I need your help for supporting EAP-PEAP? where as end user modify
> only above 3/4 parameters.

In order to keep both EAP-TTLS and EAP-PEAP secure, you will have to add
ca_cert parameter to allow the supplicant to authenticate the server.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec  5 19:12:45 2007
From: j (Jouni Malinen)
Date: Wed, 5 Dec 2007 19:12:45 -0800
Subject: handshake error
In-Reply-To: <44555.66.201.209.31.1196689253.squirrel@mail1.canasoft.net>
References: <44555.66.201.209.31.1196689253.squirrel@mail1.canasoft.net>
Message-ID: <20071206031245.GU5698@jm.kir.nu>

On Mon, Dec 03, 2007 at 08:40:53AM -0500, Frank wrote:

> NOTE: There are no files attached. This is my second attempt as my first
> attempt did not pass through with the attachments. If someone can help
> I can send the attachments.

Well, let me put it the other way around.. No one can likely help
without seeing those attachments.. At minimum, please send debug output
from wpa_supplicant.

-- 
Jouni Malinen                                            PGP id EFC895FA



From archana.gopal  Wed Dec  5 22:14:08 2007
From: archana.gopal (Archana Rajagopal)
Date: Thu, 6 Dec 2007 01:14:08 -0500
Subject: kernel configuration for HostAP
Message-ID: <5dd628b40712052214p7385f00dn1b225dba4aef4e84@mail.gmail.com>

Hi,
    I am facing similar problem with two different versions of linux
kernel.(2.6.18 and 2.6.22).When I use Linksys WPC11 card , they dont create
any wireless interface.But the card is detected by orinoco_cs driver and it
is loaded on eth2 interface with no support for master mode.hostap_cs is
loaded but it does not activate the card.Moreover if i blacklist orinoco
driver , the card goes undetected or it gives kernel panic on boot.This does
not happen with kernel version 2.6.16.Is it related to config file?Any
suggestions?

-- 
Regards
Archana Rajagopal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/92c9dd6e/attachment.htm 


From raghavendra.akkasali  Wed Dec  5 23:24:04 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Thu, 6 Dec 2007 12:54:04 +0530
Subject: Small doubt about wpa supplicant.
Message-ID: <58a444250712052324o1ff3e5bdj5c866b78725f852@mail.gmail.com>

Hi All,

 I am newbie to wireless. So only this silly question comes from me...:)

 I am using wpa supplicant. Now on our device. we have some WLAN code which
does scanning..association ..etc all those basic wireless events and then it
call dhcp client to get IP.

   Now they asked me to integrate wpa supplicant to provide security. I saw
even wpa supplicant does scanning, association....authentication and then
connects. In short wpa supplicant is a binary with config file....which
establishes secure channel.

My question is if I integrate wpa supplicant I guess I dont need previous
code which does scanning..association...etc. I can directly invoke wpa
supplicant and then use dhcp client to get IP. Am I correct?

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/bbd151e0/attachment.htm 


From m.sukumar  Wed Dec  5 23:54:59 2007
From: m.sukumar (Sukku)
Date: Thu, 6 Dec 2007 13:24:59 +0530
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <1196867834.2519.7.camel@localhost.localdomain>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
Message-ID: <7ff5a6c20712052354w17910955wa40fed0e2a07e88a@mail.gmail.com>

Hi George and Dan,

First of all thank you very much for your replay.

I tried with NetworkManager also.. with NM also I didn't get successes.

In var/log/messages I am getting this logs:

Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'ssid' value
'test1'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'key_mgmt'
value 'WPA-EAP'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'identity'
value 'default'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'password'
value '<omitted>'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'eap' value
'LEAP'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'proto' value
'WPA RSN WPA RSN'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'pairwise'
value 'TKIP CCMP TKIP CCMP'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'group' value
'WEP40 WEP104 TKIP CCMP WEP40 WEP104 TKIP CCMP'
Dec  6 12:44:14 sukumar NetworkManager: <info>  Activation (wlan0) Stage 2
of 5 (Device Configure) complete.
Dec  6 12:44:14 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
state change: 0 -> 2
Dec  6 12:44:39 sukumar NetworkManager: <info>  Activation (wlan0/wireless):
association took too long, asking for new key.
Dec  6 12:44:39 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
state change: 2 -> 0
Dec  6 12:44:44 sukumar NetworkManager: <WARN>  get_secrets_cb(): Couldn't
get connection secrets: applet.c.2997 (get_secrets_dialog_response_cb):
canceled.
Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0) failed
for access point (Neolinksys)
Dec  6 12:44:44 sukumar NetworkManager: <info>  Marking connection 'Auto
Neolinksys' invalid.
Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0) failed.
Dec  6 12:44:44 sukumar NetworkManager: <info>  Deactivating device wlan0.
Dec  6 12:44:44 sukumar NetworkManager: <info>  SWITCH: no current
connection, found better connection 'Auto Ethernet (eth0)

Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'ssid' value
'test2'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'key_mgmt'
value 'WPA-PSK'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'psk' value
'<omitted>'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'proto' value
'WPA RSN'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'pairwise'
value 'TKIP CCMP'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'group' value
'WEP40 WEP104 TKIP CCMP'
Dec  6 12:45:52 sukumar NetworkManager: <info>  Activation (wlan0) Stage 2
of 5 (Device Configure) complete.
Dec  6 12:45:52 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
state change: 0 -> 2
Dec  6 12:45:52 sukumar avahi-daemon[1896]: Interface eth0.IPv4 no longer
relevant for mDNS.
Dec  6 12:45:52 sukumar avahi-daemon[1896]: Withdrawing address record for
fe80::20c:29ff:fe9d:5560 on eth0.
Dec  6 12:46:17 sukumar NetworkManager: <info>  Activation (wlan0/wireless):
association took too long, asking for new key.
Dec  6 12:46:17 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
state change: 2 -> 0




As per my understating the problem will be "what ever the IOCTL commands
generated by wpa_supplicant  are not understood by  ndiswrappered  drivers"

To resolve this problem where I need to change the code. Plz help me.

Thanks and regards,
Sukumar


On Dec 5, 2007 8:47 PM, Dan Williams <dcbw at redhat.com> wrote:

> On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> > On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > > Hi All,
> > >
> > > From last two weeks, I am working on this problem. I am working on FC8
> with
> > > kernel version 2.6.23.1-42.
> > >
> > > I am using Linksys wireless adapter (WUSB54G). I didn't found any
> linux
> > > drivers for this device. so by using ndiswrappers I installed windows
> native
> > > drives in linux box. finally adapter got detected.
> > >
> > > after words  I try to use this  wpa_supplicant on this adapter.  Hear
> I am
> > > facing problem
> > >
> > > In debugging mode  I am getting so many IOCTL errors. I am not
> getting,
> > > there errors are from ndiswrapper or wpa_supplicant.
> >
> > I saw those errors, and failed to connect, also using FC8 with a
> ndiswrapper
> > but a different  USB dongle (TEW).    However, NetworkManager is more or
> > less working (too frequent disconnects from my AP, connects to random
> > open AP's).   Check that there isn't a 2nd copy of wpa_supplicant
> running.
>
> NM itself will only ever connect to an AP that you've chosen from the
> menu.
>
> If you've never chosen that AP from the menu, it's important to remember
> that the driver and/or firmware also control roaming, and that
> often-times the driver/firmware will decide to associate to an access
> point without being told to so (ipw* does this a lot).  Some drivers
> have module options to disable that functionality, and the only real
> arguments I've heard for this behavior are that people alone in the
> woods then don't need to issue manual iwconfig commands when they start
> their computer up.  I'm not sure what the security implications of the
> card connecting to a random open AP are, but it can't be much good.
>
> dan
>
>
>


-- 

-------
????????.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/241b553b/attachment.htm 


From dcbw  Thu Dec  6 02:56:28 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 05:56:28 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <7ff5a6c20712052354w17910955wa40fed0e2a07e88a@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<7ff5a6c20712052354w17910955wa40fed0e2a07e88a@mail.gmail.com>
Message-ID: <1196938588.3980.15.camel@localhost.localdomain>

On Thu, 2007-12-06 at 13:24 +0530, Sukku wrote:
> Hi George and Dan,
> 
> First of all thank you very much for your replay.
> 
> I tried with NetworkManager also.. with NM also I didn't get
> successes. 
> 
> In var/log/messages I am getting this logs:
> 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'ssid'
> value 'test1' 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added
> 'key_mgmt' value 'WPA-EAP'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added
> 'identity' value 'default' 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added
> 'password' value '<omitted>'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'eap'
> value 'LEAP' 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'proto'
> value 'WPA RSN WPA RSN'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added
> 'pairwise' value 'TKIP CCMP TKIP CCMP' 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'group'
> value 'WEP40 WEP104 TKIP CCMP WEP40 WEP104 TKIP CCMP'

Pre-emptive FYI, I know the above ^^^ repeats are wrong but there are
bigger fish to fry right now with NM and wpa_supplicant handles it OK.

Dan

> Dec  6 12:44:14 sukumar NetworkManager: <info>  Activation (wlan0)
> Stage 2 of 5 (Device Configure) complete. 
> Dec  6 12:44:14 sukumar NetworkManager: <info>  (wlan0) Supplicant
> interface state change: 0 -> 2
> Dec  6 12:44:39 sukumar NetworkManager: <info>  Activation
> (wlan0/wireless): association took too long, asking for new key. 
> Dec  6 12:44:39 sukumar NetworkManager: <info>  (wlan0) Supplicant
> interface state change: 2 -> 0
> Dec  6 12:44:44 sukumar NetworkManager: <WARN>  get_secrets_cb():
> Couldn't get connection secrets: applet.c.2997
> (get_secrets_dialog_response_cb): canceled.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0)
> failed for access point (Neolinksys)
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Marking connection
> 'Auto Neolinksys' invalid. 
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0)
> failed.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Deactivating device
> wlan0.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  SWITCH: no current
> connection, found better connection 'Auto Ethernet (eth0) 
> 
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'ssid'
> value 'test2'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added
> 'key_mgmt' value 'WPA-PSK' 
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'psk'
> value '<omitted>'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'proto'
> value 'WPA RSN' 
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added
> 'pairwise' value 'TKIP CCMP'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'group'
> value 'WEP40 WEP104 TKIP CCMP' 
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Activation (wlan0)
> Stage 2 of 5 (Device Configure) complete.
> Dec  6 12:45:52 sukumar NetworkManager: <info>  (wlan0) Supplicant
> interface state change: 0 -> 2 
> Dec  6 12:45:52 sukumar avahi-daemon[1896]: Interface eth0.IPv4 no
> longer relevant for mDNS.
> Dec  6 12:45:52 sukumar avahi-daemon[1896]: Withdrawing address record
> for fe80::20c:29ff:fe9d:5560 on eth0.
> Dec  6 12:46:17 sukumar NetworkManager: <info>  Activation
> (wlan0/wireless): association took too long, asking for new key. 
> Dec  6 12:46:17 sukumar NetworkManager: <info>  (wlan0) Supplicant
> interface state change: 2 -> 0
> 
> 
> 
> 
> As per my understating the problem will be "what ever the IOCTL
> commands generated by wpa_supplicant  are not understood by
> ndiswrappered  drivers" 
> 
> To resolve this problem where I need to change the code. Plz help me.
> 
> Thanks and regards,
> Sukumar
> 
> 
> On Dec 5, 2007 8:47 PM, Dan Williams <dcbw at redhat.com> wrote:
>         On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote: 
>         > On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
>         > > Hi All,
>         > >
>         > > From last two weeks, I am working on this problem. I am
>         working on FC8 with 
>         > > kernel version 2.6.23.1-42.
>         > >
>         > > I am using Linksys wireless adapter (WUSB54G). I didn't
>         found any linux
>         > > drivers for this device. so by using ndiswrappers I
>         installed windows native 
>         > > drives in linux box. finally adapter got detected.
>         > >
>         > > after words  I try to use this  wpa_supplicant on this
>         adapter.  Hear I am
>         > > facing problem
>         > >
>         > > In debugging mode  I am getting so many IOCTL errors. I am
>         not getting, 
>         > > there errors are from ndiswrapper or wpa_supplicant.
>         >
>         > I saw those errors, and failed to connect, also using FC8
>         with a ndiswrapper
>         > but a different  USB dongle (TEW).    However,
>         NetworkManager is more or 
>         > less working (too frequent disconnects from my AP, connects
>         to random
>         > open AP's).   Check that there isn't a 2nd copy of
>         wpa_supplicant running.
>         
>         
>         NM itself will only ever connect to an AP that you've chosen
>         from the 
>         menu.
>         
>         If you've never chosen that AP from the menu, it's important
>         to remember
>         that the driver and/or firmware also control roaming, and that
>         often-times the driver/firmware will decide to associate to an
>         access 
>         point without being told to so (ipw* does this a lot).  Some
>         drivers
>         have module options to disable that functionality, and the
>         only real
>         arguments I've heard for this behavior are that people alone
>         in the
>         woods then don't need to issue manual iwconfig commands when
>         they start
>         their computer up.  I'm not sure what the security
>         implications of the
>         card connecting to a random open AP are, but it can't be much
>         good. 
>         
>         dan
>         
>         
> 
> 
> 
> -- 
> 
> -------
> ????????.




From dcbw  Thu Dec  6 02:58:01 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 05:58:01 -0500
Subject: Small doubt about wpa supplicant.
In-Reply-To: <58a444250712052324o1ff3e5bdj5c866b78725f852@mail.gmail.com>
References: <58a444250712052324o1ff3e5bdj5c866b78725f852@mail.gmail.com>
Message-ID: <1196938681.3980.17.camel@localhost.localdomain>

On Thu, 2007-12-06 at 12:54 +0530, Raghavendra. S wrote:
> Hi All,
>  
>  I am newbie to wireless. So only this silly question comes from
> me...:) 
>  
>  I am using wpa supplicant. Now on our device. we have some WLAN code
> which does scanning..association ..etc all those basic wireless events
> and then it call dhcp client to get IP.
>  
>    Now they asked me to integrate wpa supplicant to provide security.
> I saw even wpa supplicant does scanning, association....authentication
> and then connects. In short wpa supplicant is a binary with config
> file....which establishes secure channel.
>  
> My question is if I integrate wpa supplicant I guess I dont need
> previous code which does scanning..association...etc. I can directly
> invoke wpa supplicant and then use dhcp client to get IP. Am I
> correct?

That is correct.  Get rid of your own scanning and association code.
Create the right config file for wpa_supplicant, let it do it's job, and
then when it's connected you do the DHCP manually.

Dan






From gnwiii  Thu Dec  6 03:49:34 2007
From: gnwiii (George N. White III)
Date: Thu, 6 Dec 2007 07:49:34 -0400
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <1196867834.2519.7.camel@localhost.localdomain>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
Message-ID: <22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>

On Dec 5, 2007 11:17 AM, Dan Williams <dcbw at redhat.com> wrote:

> On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> > On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > > Hi All,
> > >
> > > From last two weeks, I am working on this problem. I am working on FC8 with
> > > kernel version 2.6.23.1-42.
> > >
> > > I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
> > > drivers for this device. so by using ndiswrappers I installed windows native
> > > drives in linux box. finally adapter got detected.
> > >
> > > after words  I try to use this  wpa_supplicant on this adapter.  Hear I am
> > > facing problem
> > >
> > > In debugging mode  I am getting so many IOCTL errors. I am not getting,
> > > there errors are from ndiswrapper or wpa_supplicant.
> >
> > I saw those errors, and failed to connect, also using FC8 with a ndiswrapper
> > but a different  USB dongle (TEW).    However, NetworkManager is more or
> > less working (too frequent disconnects from my AP, connects to random
> > open AP's).   Check that there isn't a 2nd copy of wpa_supplicant running.
>
> NM itself will only ever connect to an AP that you've chosen from the
> menu.
>
> If you've never chosen that AP from the menu, it's important to remember
> that the driver and/or firmware also control roaming, and that
> often-times the driver/firmware will decide to associate to an access
> point without being told to so (ipw* does this a lot).  Some drivers
> have module options to disable that functionality, and the only real
> arguments I've heard for this behavior are that people alone in the
> woods then don't need to issue manual iwconfig commands when they start
> their computer up.  I'm not sure what the security implications of the
> card connecting to a random open AP are, but it can't be much good.

All true.  There are several issues here:

1.  ndiswrapper doesn't have module options to disable association with
open access points.  Module writers should ensure that the default is to
disable this.

2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only
one "dlink" appears in the NetworkManager list.  Even if I give my AP a name,
an evil perp could use the same name and NM might well use that AP.
NM needs a way to present multiple AP's with the same name.

3.  it is easy, e.g., in NetworkManager, to accidentally select the wrong AP
(poor hand-eye coordination, jerky mouse on a busy system, screen updates
just as you click).

This says there is a need for a mechanism to remove an AP from NM's list,
and probably also a way to list AP's that should never be used.


-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia



From dcbw  Thu Dec  6 04:03:34 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 07:03:34 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
Message-ID: <1196942614.5042.12.camel@localhost.localdomain>

On Thu, 2007-12-06 at 07:49 -0400, George N. White III wrote:
> On Dec 5, 2007 11:17 AM, Dan Williams <dcbw at redhat.com> wrote:
> 
> > On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> > > On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > > > Hi All,
> > > >
> > > > From last two weeks, I am working on this problem. I am working on FC8 with
> > > > kernel version 2.6.23.1-42.
> > > >
> > > > I am using Linksys wireless adapter (WUSB54G). I didn't found any linux
> > > > drivers for this device. so by using ndiswrappers I installed windows native
> > > > drives in linux box. finally adapter got detected.
> > > >
> > > > after words  I try to use this  wpa_supplicant on this adapter.  Hear I am
> > > > facing problem
> > > >
> > > > In debugging mode  I am getting so many IOCTL errors. I am not getting,
> > > > there errors are from ndiswrapper or wpa_supplicant.
> > >
> > > I saw those errors, and failed to connect, also using FC8 with a ndiswrapper
> > > but a different  USB dongle (TEW).    However, NetworkManager is more or
> > > less working (too frequent disconnects from my AP, connects to random
> > > open AP's).   Check that there isn't a 2nd copy of wpa_supplicant running.
> >
> > NM itself will only ever connect to an AP that you've chosen from the
> > menu.
> >
> > If you've never chosen that AP from the menu, it's important to remember
> > that the driver and/or firmware also control roaming, and that
> > often-times the driver/firmware will decide to associate to an access
> > point without being told to so (ipw* does this a lot).  Some drivers
> > have module options to disable that functionality, and the only real
> > arguments I've heard for this behavior are that people alone in the
> > woods then don't need to issue manual iwconfig commands when they start
> > their computer up.  I'm not sure what the security implications of the
> > card connecting to a random open AP are, but it can't be much good.
> 
> All true.  There are several issues here:
> 
> 1.  ndiswrapper doesn't have module options to disable association with
> open access points.  Module writers should ensure that the default is to
> disable this.

Yep, I agree.  It may not be possible to change existing drivers to do
this (unless people start yelling about security), but new drivers
should certainly respect this.

> 2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only
> one "dlink" appears in the NetworkManager list.  Even if I give my AP a name,
> an evil perp could use the same name and NM might well use that AP.
> NM needs a way to present multiple AP's with the same name.

With 0.7, the applet will only combine SSIDs that have the same mode
(infra/adhoc), band (a/bg), and security settings (none/wep/wpa/wpa2).
If there are, say, two linksys access points, both with WEP and both on
channel 11, the applet will certainly combine those APs.  NM itself
always presents each AP split out via the D-Bus interface.  UI bits are
responsible for combining (or not) the results.

You simply cannot fix this situation at all unless you start displaying
BSSIDs in the menu.  We know what a BSSID is, but I have no clue what my
AP's BSSID is right now, and I just don't care.  Nor do 90% of users.
The nm-applet won't be showing each separate BSSID in the menu, but
you're certainly welcome to write your own tool that shows each BSSID
and allows you to select the exact one you want using the NM D-Bus
interface.

> 3.  it is easy, e.g., in NetworkManager, to accidentally select the wrong AP
> (poor hand-eye coordination, jerky mouse on a busy system, screen updates
> just as you click).

The menu in the gnome applet doesn't dynamically update the menu though,
so that shouldn't be a problem.

> This says there is a need for a mechanism to remove an AP from NM's list,
> and probably also a way to list AP's that should never be used.

There are two things we're going to do for removing APs:

1) Provide the ability to flip the autoconnect bit from the notification
bubbles

2) Provide the connection editor to allow you to remove connections
(already almost working)

Dan





From gnwiii  Thu Dec  6 04:16:20 2007
From: gnwiii (George N. White III)
Date: Thu, 6 Dec 2007 08:16:20 -0400
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <7ff5a6c20712052354w17910955wa40fed0e2a07e88a@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<7ff5a6c20712052354w17910955wa40fed0e2a07e88a@mail.gmail.com>
Message-ID: <22af238a0712060416r6937b9a2p45abbcec3471fc91@mail.gmail.com>

On Dec 6, 2007 3:54 AM, Sukku <m.sukumar at gmail.com> wrote:

> Hi George and Dan,
>
> First of all thank you very much for your replay.
>
> I tried with NetworkManager also.. with NM also I didn't get successes.
>
> In var/log/messages I am getting this logs:
>
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'ssid' value
> 'test1'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'key_mgmt'
> value 'WPA-EAP'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'identity'
> value 'default'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'password'
> value '<omitted>'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'eap' value
> 'LEAP'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'proto' value
> 'WPA RSN WPA RSN'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'pairwise'
> value 'TKIP CCMP TKIP CCMP'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Config: added 'group' value
> 'WEP40 WEP104 TKIP CCMP WEP40 WEP104 TKIP CCMP'
> Dec  6 12:44:14 sukumar NetworkManager: <info>  Activation (wlan0) Stage 2
> of 5 (Device Configure) complete.
> Dec  6 12:44:14 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
> state change: 0 -> 2
> Dec  6 12:44:39 sukumar NetworkManager: <info>  Activation (wlan0/wireless):
> association took too long, asking for new key.
> Dec  6 12:44:39 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
> state change: 2 -> 0
> Dec  6 12:44:44 sukumar NetworkManager: <WARN>  get_secrets_cb(): Couldn't
> get connection secrets: applet.c.2997 (get_secrets_dialog_response_cb):
> canceled.

I don't recall seeing this, but it looks bad.   When NM first connects
to a new AP that
needs a "secret", it should ask for one, which gets stored in your
Gnome keyring.  You
can verify the entries using gnome-keyring-manager.  Many people find
that NM will ask for the "secret" again after a disconnect.  I find
that entering
the secret here doesn't help -- I have to rmmod ndiswrapper, wait for
the scan to
succeed, and then NM will let me choose the AP and connect.

> Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0) failed
> for access point (Neolinksys)
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Marking connection 'Auto
> Neolinksys' invalid.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Activation (wlan0) failed.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  Deactivating device wlan0.
> Dec  6 12:44:44 sukumar NetworkManager: <info>  SWITCH: no current
> connection, found better connection 'Auto Ethernet (eth0)
>
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'ssid' value
> 'test2'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'key_mgmt'
> value 'WPA-PSK'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'psk' value
> '<omitted>'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'proto' value
> 'WPA RSN'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'pairwise'
> value 'TKIP CCMP'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Config: added 'group' value
> 'WEP40 WEP104 TKIP CCMP'
> Dec  6 12:45:52 sukumar NetworkManager: <info>  Activation (wlan0) Stage 2
> of 5 (Device Configure) complete.
> Dec  6 12:45:52 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
> state change: 0 -> 2
> Dec  6 12:45:52 sukumar avahi-daemon[1896]: Interface eth0.IPv4 no longer
> relevant for mDNS.
> Dec  6 12:45:52 sukumar avahi-daemon[1896]: Withdrawing address record for
> fe80::20c:29ff:fe9d:5560 on eth0.
> Dec  6 12:46:17 sukumar NetworkManager: <info>  Activation (wlan0/wireless):
> association took too long, asking for new key.
> Dec  6 12:46:17 sukumar NetworkManager: <info>  (wlan0) Supplicant interface
> state change: 2 -> 0
>
>
>
>
> As per my understating the problem will be "what ever the IOCTL commands
> generated by wpa_supplicant  are not understood by  ndiswrappered  drivers"

I don't see these on my system using NM, and I don't see them above.  NM
controls wpa_supplicant directly using dbus, and ignores the config file.
You can get more details in wpa_supplicant.log by writing a little wrapper
script to add debugging options, e.g., something along the lines:

# mv wpa_supplicant wpa_supplicant.bin
# cat <<EOF > wpa_supplicant
#! /bin/sh
# -dd -- lots of debugging messages
# -t -- timestamps
# -s -- use syslog
exec wpa_supplicant.bin -dd -t -s "$@"
EOF
# chmod +x wpa_supplicant

> To resolve this problem where I need to change the code. Plz help me.
>
> Thanks and regards,
> Sukumar
>
>
>
>
> On Dec 5, 2007 8:47 PM, Dan Williams < dcbw at redhat.com> wrote:
> >
> > On Wed, 2007-12-05 at 11:09 -0400, George N. White III wrote:
> > > On Dec 5, 2007 10:25 AM, Sukku <m.sukumar at gmail.com> wrote:
> > > > Hi All,
> > > >
> > > > From last two weeks, I am working on this problem. I am working on FC8
> with
> > > > kernel version 2.6.23.1-42.
> > > >
> > > > I am using Linksys wireless adapter (WUSB54G). I didn't found any
> linux
> > > > drivers for this device. so by using ndiswrappers I installed windows
> native
> > > > drives in linux box. finally adapter got detected.
> > > >
> > > > after words  I try to use this  wpa_supplicant on this adapter.  Hear
> I am
> > > > facing problem
> > > >
> > > > In debugging mode  I am getting so many IOCTL errors. I am not
> getting,
> > > > there errors are from ndiswrapper or wpa_supplicant.
> > >
> > > I saw those errors, and failed to connect, also using FC8 with a
> ndiswrapper
> > > but a different  USB dongle (TEW).    However, NetworkManager is more or
> > > less working (too frequent disconnects from my AP, connects to random
> > > open AP's).   Check that there isn't a 2nd copy of wpa_supplicant
> running.
> >
> > NM itself will only ever connect to an AP that you've chosen from the
> > menu.
> >
> > If you've never chosen that AP from the menu, it's important to remember
> > that the driver and/or firmware also control roaming, and that
> > often-times the driver/firmware will decide to associate to an access
> > point without being told to so (ipw* does this a lot).  Some drivers
> > have module options to disable that functionality, and the only real
> > arguments I've heard for this behavior are that people alone in the
> > woods then don't need to issue manual iwconfig commands when they start
> > their computer up.  I'm not sure what the security implications of the
> > card connecting to a random open AP are, but it can't be much good.
> >
> > dan
> >
> >
> >
>
>
>
> --
>
> -------
> ????????.



-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia


From gnwiii  Thu Dec  6 04:33:25 2007
From: gnwiii (George N. White III)
Date: Thu, 6 Dec 2007 08:33:25 -0400
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <1196942614.5042.12.camel@localhost.localdomain>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
	<1196942614.5042.12.camel@localhost.localdomain>
Message-ID: <22af238a0712060433p427ec4afgab7674111844d05e@mail.gmail.com>

On Dec 6, 2007 8:03 AM, Dan Williams <dcbw at redhat.com> wrote:

> [...]
> > 2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only
> > one "dlink" appears in the NetworkManager list.  Even if I give my AP a name,
> > an evil perp could use the same name and NM might well use that AP.
> > NM needs a way to present multiple AP's with the same name.
>
> With 0.7, the applet will only combine SSIDs that have the same mode
> (infra/adhoc), band (a/bg), and security settings (none/wep/wpa/wpa2).
> If there are, say, two linksys access points, both with WEP and both on
> channel 11, the applet will certainly combine those APs.  NM itself
> always presents each AP split out via the D-Bus interface.  UI bits are
> responsible for combining (or not) the results.
>
> You simply cannot fix this situation at all unless you start displaying
> BSSIDs in the menu.  We know what a BSSID is, but I have no clue what my
> AP's BSSID is right now, and I just don't care.  Nor do 90% of users.
> The nm-applet won't be showing each separate BSSID in the menu, but
> you're certainly welcome to write your own tool that shows each BSSID
> and allows you to select the exact one you want using the NM D-Bus
> interface.

I prefer a way to give NM some hints, e.g., show AP's configured in
/etc/wpa_supplicant/wpa_supplicant.conf or show only AP's with
(specified) security.

I think there are a couple intermediate UI options.

1.  show the number of AP's in one line in the menu: e.g., "dink (4)".

2. NM could invent names "dlink.a", "dlink.b", etc.

Both suggestions let the user know that there are multiple AP's.

-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia



From traxtopel  Thu Dec  6 04:51:57 2007
From: traxtopel (Grant Williamson)
Date: Thu, 06 Dec 2007 13:51:57 +0100
Subject: wpa_cli eapol_version
Message-ID: <4757F06D.5020906@gmail.com>

Hi,
I curious if it is possible to set eapol_version using the command 
client. I know I can add it to the wpa_supplicant.conf. But is there 
anyway to set this on the fly.

wpa_cli eapol_version 2



From ve2cii  Thu Dec  6 05:50:36 2007
From: ve2cii (Frank)
Date: Thu, 6 Dec 2007 08:50:36 -0500 (EST)
Subject: handshake error
Message-ID: <45114.66.201.209.31.1196949036.squirrel@mail1.canasoft.net>

   Hello,

   I have been communicating with:
"Christian Beier" <christian.beier at stud.tu-ilmenau.de>
and I have sent him all the attachments. He says that I need to use
wpa_passphrase to encrypt the password instead of putting it into the
config file in plain text. This I have just done and I tried it again and
still it does not work. I have attached the debug output.



-
sysadm  cronomagic.com , wapda.com
e-mail  ve2cii at canasoft.net

POWERED BY LINUX





-
sysadm  cronomagic.com , wapda.com
e-mail  ve2cii at canasoft.net

POWERED BY LINUX
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_output.txt
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071206/e3481fd4/attachment.txt 


From bryan  Thu Dec  6 06:20:26 2007
From: bryan (Bryan Kadzban)
Date: Thu, 06 Dec 2007 09:20:26 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
Message-ID: <4758052A.9070807@kadzban.is-a-geek.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

George N. White III wrote:
> 2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only one
> "dlink" appears in the NetworkManager list.  Even if I give my AP a
> name, an evil perp could use the same name and NM might well use that
> AP. NM needs a way to present multiple AP's with the same name.

If you're worried about so-called "rogue APs", then simply splitting out
each BSS from the ESS in the UI isn't going to help at all.  As Dan said
in response to this, most people don't know (or care) which BSSID
they're connecting to -- but even apart from that, it may be possible to
fake a BSSID.  (I don't know for sure.)

The only secure way to fix this is to either (a) ensure your PSK can't
be guessed, *and* that nobody writes AP firmware/software that will let
people connect even if their PSK is wrong (though I don't know if that's
possible), or (b) use a RADIUS server, ensure your RADIUS shared secret
can't be guessed, use some kind of certificate to authenticate the
server (e.g. PEAP, TTLS, or TLS), and configure the client to only trust
a root certificate that you control.

The last part is the critical one: a rogue AP can probably spoof just
about everything, but not knowledge of the root cert's private key.  And
the unguessable shared secret ensures that the rogue AP can't just use
your existing RADIUS server.  (Although if someone has the ability to
plug into your network already, it's a bit of a moot point -- but whatever.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHWAUpS5vET1Wea5wRA3G0AKC4D4fGQkxnWLI3V8o01wqb5ZacsgCeIY3u
PvTgX13oTU7pWoFx3WVbw8I=
=qeLM
-----END PGP SIGNATURE-----



From dcbw  Thu Dec  6 06:34:26 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 09:34:26 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <4758052A.9070807@kadzban.is-a-geek.net>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
	<4758052A.9070807@kadzban.is-a-geek.net>
Message-ID: <1196951666.9649.7.camel@localhost.localdomain>

On Thu, 2007-12-06 at 09:20 -0500, Bryan Kadzban wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> George N. White III wrote:
> > 2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only one
> > "dlink" appears in the NetworkManager list.  Even if I give my AP a
> > name, an evil perp could use the same name and NM might well use that
> > AP. NM needs a way to present multiple AP's with the same name.
> 
> If you're worried about so-called "rogue APs", then simply splitting out
> each BSS from the ESS in the UI isn't going to help at all.  As Dan said
> in response to this, most people don't know (or care) which BSSID
> they're connecting to -- but even apart from that, it may be possible to
> fake a BSSID.  (I don't know for sure.)

If the driver & firmware allow dumping raw frames through, then you can
certainly spoof any BSSID just like you can spoof MAC addresses today
with ethernet.  So it's quite possible to clone an access point.  The
only way to 99% ensure that you are using the AP you expect is to use
TLS or TTLS and check the certificate returned from the EAP exchange
against a verified CA certificate that you have locally, or use WPA2-PSK
(with only CCMP) with a really secure key and low key rotation times.
The BSSID means nothing in the paranoid world.

Dan

> The only secure way to fix this is to either (a) ensure your PSK can't
> be guessed, *and* that nobody writes AP firmware/software that will let
> people connect even if their PSK is wrong (though I don't know if that's
> possible), or (b) use a RADIUS server, ensure your RADIUS shared secret
> can't be guessed, use some kind of certificate to authenticate the
> server (e.g. PEAP, TTLS, or TLS), and configure the client to only trust
> a root certificate that you control.
> 
> The last part is the critical one: a rogue AP can probably spoof just
> about everything, but not knowledge of the root cert's private key.  And
> the unguessable shared secret ensures that the rogue AP can't just use
> your existing RADIUS server.  (Although if someone has the ability to
> plug into your network already, it's a bit of a moot point -- but whatever.)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFHWAUpS5vET1Wea5wRA3G0AKC4D4fGQkxnWLI3V8o01wqb5ZacsgCeIY3u
> PvTgX13oTU7pWoFx3WVbw8I=
> =qeLM
> -----END PGP SIGNATURE-----




From gnwiii  Thu Dec  6 06:50:27 2007
From: gnwiii (George N. White III)
Date: Thu, 6 Dec 2007 10:50:27 -0400
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <4758052A.9070807@kadzban.is-a-geek.net>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
	<4758052A.9070807@kadzban.is-a-geek.net>
Message-ID: <22af238a0712060650j9cad4beo19bcf09544fb2512@mail.gmail.com>

On Dec 6, 2007 10:20 AM, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:

> George N. White III wrote:
> > 2.  Iwlist wlan0 scan often shows multiple "dlink" AP's, but only one
> > "dlink" appears in the NetworkManager list.  Even if I give my AP a
> > name, an evil perp could use the same name and NM might well use that
> > AP. NM needs a way to present multiple AP's with the same name.
>
> If you're worried about so-called "rogue APs", then simply splitting out
> each BSS from the ESS in the UI isn't going to help at all.  As Dan said
> in response to this, most people don't know (or care) which BSSID
> they're connecting to -- but even apart from that, it may be possible to
> fake a BSSID.  (I don't know for sure.)
>
> The only secure way to fix this is to either (a) ensure your PSK can't
> be guessed, *and* that nobody writes AP firmware/software that will let
> people connect even if their PSK is wrong (though I don't know if that's
> possible), or (b) use a RADIUS server, ensure your RADIUS shared secret
> can't be guessed, use some kind of certificate to authenticate the
> server (e.g. PEAP, TTLS, or TLS), and configure the client to only trust
> a root certificate that you control.
>
> The last part is the critical one: a rogue AP can probably spoof just
> about everything, but not knowledge of the root cert's private key.  And
> the unguessable shared secret ensures that the rogue AP can't just use
> your existing RADIUS server.  (Although if someone has the ability to
> plug into your network already, it's a bit of a moot point -- but whatever.)

At present, some people are finding that NM unexpectedly connects to
an open AP, e.g., after the connection to a secure AP was dropped, so at
present, rogue AP justs needs to be open.   Give it an attractive name,
either that of an existing secure AP or "bypass_corporate_filrewall_here",
and put it close to your target.


-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia



From bryan  Thu Dec  6 08:50:33 2007
From: bryan (Bryan Kadzban)
Date: Thu, 06 Dec 2007 11:50:33 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <22af238a0712060650j9cad4beo19bcf09544fb2512@mail.gmail.com>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>	
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>	
	<1196867834.2519.7.camel@localhost.localdomain>	
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>	
	<4758052A.9070807@kadzban.is-a-geek.net>
	<22af238a0712060650j9cad4beo19bcf09544fb2512@mail.gmail.com>
Message-ID: <47582859.8050600@kadzban.is-a-geek.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

George N. White III wrote:
> At present, some people are finding that NM unexpectedly connects to 
> an open AP, e.g., after the connection to a secure AP was dropped,

Well, that sounds like a bug that should be fixed -- but I'm not sure
that a simple change to avoid combining BSSes would be sufficient to
prevent connection to rogue APs.  I think that preventing this is a good
idea, of course, but I'm not sure that showing the user the BSSID is
going to do that.

(Of course I don't know the nature of this sounds-like-a-bug behavior,
either, so I may be way off base there too.)

Anyway, carry on.  It sounds like Dan understands what's really needed
(from the crypto side anyway) to prevent this, so that's fine.  I'm just
being paranoid.  ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHWChYS5vET1Wea5wRA0fAAJ9yIbKWYbp/00EXR2kFErZ9xbaxJwCgrcVL
JZSU1HNC+KhjVe9O5IwB/ws=
=hSOb
-----END PGP SIGNATURE-----



From dcbw  Thu Dec  6 09:18:15 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 12:18:15 -0500
Subject: ndiswrapper + wpa_supplicant
In-Reply-To: <47582859.8050600@kadzban.is-a-geek.net>
References: <7ff5a6c20712050625h3f1bbd8dw29ccdf6b167045c6@mail.gmail.com>
	<22af238a0712050709h4843d7a6t39d406e292243d9e@mail.gmail.com>
	<1196867834.2519.7.camel@localhost.localdomain>
	<22af238a0712060349q4fbd2757s51fd30b2a93ed1dc@mail.gmail.com>
	<4758052A.9070807@kadzban.is-a-geek.net>
	<22af238a0712060650j9cad4beo19bcf09544fb2512@mail.gmail.com>
	<47582859.8050600@kadzban.is-a-geek.net>
Message-ID: <1196961495.1469.3.camel@localhost.localdomain>

On Thu, 2007-12-06 at 11:50 -0500, Bryan Kadzban wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> George N. White III wrote:
> > At present, some people are finding that NM unexpectedly connects to 
> > an open AP, e.g., after the connection to a secure AP was dropped,
> 
> Well, that sounds like a bug that should be fixed -- but I'm not sure
> that a simple change to avoid combining BSSes would be sufficient to
> prevent connection to rogue APs.  I think that preventing this is a good
> idea, of course, but I'm not sure that showing the user the BSSID is
> going to do that.

It will only connect to that AP if you've connected to that SSID before.
In 0.7, it won't connect to that AP if you've told it to lock to a
specific BSSID too.

If NM connects to that SSID, you have at some point explicitly told NM
to do so.

Dan

> (Of course I don't know the nature of this sounds-like-a-bug behavior,
> either, so I may be way off base there too.)
> 
> Anyway, carry on.  It sounds like Dan understands what's really needed
> (from the crypto side anyway) to prevent this, so that's fine.  I'm just
> being paranoid.  ;-)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFHWChYS5vET1Wea5wRA0fAAJ9yIbKWYbp/00EXR2kFErZ9xbaxJwCgrcVL
> JZSU1HNC+KhjVe9O5IwB/ws=
> =hSOb
> -----END PGP SIGNATURE-----




From armbigendian  Thu Dec  6 10:20:37 2007
From: armbigendian (IO te)
Date: Thu, 6 Dec 2007 19:20:37 +0100
Subject: pre-authentication problem
In-Reply-To: <20071130174832.GA14202@kadzban.is-a-geek.net>
References: <4b1890f00711300527w6f7c81ddo2bf08c3432ea34be@mail.gmail.com>
	<20071130174832.GA14202@kadzban.is-a-geek.net>
Message-ID: <4b1890f00712061020v4622383dnadcb55a7c0ed9da9@mail.gmail.com>

I have changed my hostapd configuration, now eth1 and ath0 are bridged together:

interface=ath0
driver=madwifi
bridge=br0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
eapol_key_index_workaround=0
ssid=prova
auth_algs=1
wpa=2
wpa_key_mgmt=WPA-EAP
wpa_pairwise=CCMP TKIP
ieee8021x=1
own_ip_addr=<ip_accesspoint>
nas_identifier=pippo
auth_server_addr=<ip_radius>
auth_server_port=1812
auth_server_shared_secret=jacvvv
acct_server_addr=<ip_radius>
acct_server_port=1813
acct_server_shared_secret=jacvvv
rsn_preauth=1
rsn_preauth_interfaces=eth0 br0
The wpa_supplicant configuration isn't changed. When wpa_supplicant
starts I have a lot of messages like:
"Custom wireless event: 'MLME-REPLAYFAILURE.indication(keyid=1
broadcast addr=ff:ff:ff:ff:ff:ff)'
".
So it's very difficult for me to understand what's happening, but
after some time I get the following log in the ap where my station
must pre-authenticate:
IEEE 802.1X: 00:15:6d:53:a1:99 BE_AUTH entering state SUCCESS
IEEE 802.1X: Sending EAP Packet to 00:15:6d:53:a1:99 (identifier 9)
IEEE 802.1X: 00:15:6d:53:a1:99 REAUTH_TIMER entering state INITIALIZE
IEEE 802.1X: 00:15:6d:53:a1:99 AUTH_PAE entering state AUTHENTICATED
ath0: STA 00:15:6d:53:a1:99 IEEE 802.1X: authenticated - EAP type: 13
(TLS) (pre-authentication)
ath0: STA 00:15:6d:53:a1:99 WPA: pre-authentication succeeded
RSN: added PMKSA cache entry for 00:15:6d:53:a1:99
RSN: added PMKID - hexdump(len=16): 1a 9b 20 37 fe e2 fa 6f a4 0b 5a
b4 f6 ab d0 40
ath0: STA 00:15:6d:53:a1:99 WPA: added PMKSA cache entry (pre-auth)
IEEE 802.1X: 00:15:6d:53:a1:99 BE_AUTH entering state IDLE
RSN: Removing pre-authentication STA entry for 00:15:6d:53:a1:99
ath0: WPA rekeying GTK
...

What's happening? Is there anything wrong in my configurations? I'm
using hostapd version 0.5.7 and wpa_supplicant 0.4.9.

Thank you so much for your help,

Massimiliano



From dcbw  Thu Dec  6 13:32:51 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:32:51 -0500
Subject: [0.5.9 PATCH] Make output logging to file usable on *NIX platforms
Message-ID: <1196976771.23463.2.camel@localhost.localdomain>

Add a .config option for enabling the output logging, and add a
command-line option for turning this on or off (output is logged to
stdout by default still).  Also set the buffering mode to line-buffered
on *NIX platforms so that output shows up in a reasonable timeframe.
Otherwise it gets buffered in 4096 byte chunks (or whatever the C
library uses for buffer sizes) and doesn't get written in a useful
amount of time.

Dan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 059-log-to-file.patch
Type: text/x-patch
Size: 2441 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/e819e0b8/attachment.bin 


From dcbw  Thu Dec  6 13:35:15 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:35:15 -0500
Subject: [0.5.9 PATCH] SIGUSR1 changes debug level
Message-ID: <1196976915.23463.6.camel@localhost.localdomain>

So you don't have to respawn wpa_supplicant with different debug
options, or fire up a control interface or something.  Many *NIX
programs have this functionality; bring it to wpa_supplicant too.

Dan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 059-sigusr1-debug-level.patch
Type: text/x-patch
Size: 1236 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/960e52e3/attachment.bin 


From dcbw  Thu Dec  6 13:38:30 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:38:30 -0500
Subject: [0.5.9 PATCH] Fix segfault when D-Bus interface is compiled in but
	not enabled at runtime
Message-ID: <1196977110.23463.10.camel@localhost.localdomain>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-0.5.7-dbus-iface-segfault-fix.patch
Type: text/x-patch
Size: 527 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/6df52fab/attachment.bin 


From dcbw  Thu Dec  6 13:43:10 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:43:10 -0500
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
Message-ID: <1196977390.23463.13.camel@localhost.localdomain>

Add a .config option for enabling the output logging, and add a
command-line option for turning this on or off (output is logged to
stdout by default still).  Also set the buffering mode to line-buffered
on *NIX platforms so that output shows up in a reasonable timeframe.
Otherwise it gets buffered in 4096 byte chunks (or whatever the C
library uses for buffer sizes) and doesn't get written in a useful
amount of time.

Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 060-log-to-file.patch
Type: text/x-patch
Size: 2909 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/8171a380/attachment.bin 


From dcbw  Thu Dec  6 13:45:17 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:45:17 -0500
Subject: [0.6.x PATCH] SIGUSR1 changes debug level
Message-ID: <1196977517.23463.16.camel@localhost.localdomain>

So you don't have to respawn wpa_supplicant with different debug
options, or fire up a control interface or something.  Many *NIX
programs have this functionality; bring it to wpa_supplicant too.

Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 060-sigusr1.patch
Type: text/x-patch
Size: 1221 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/16b8abf8/attachment.bin 


From dcbw  Thu Dec  6 13:48:27 2007
From: dcbw (Dan Williams)
Date: Thu, 06 Dec 2007 16:48:27 -0500
Subject: [0.6.x PATCH] Fix segfault when D-Bus interface is compiled in but
	not enabled at runtime
Message-ID: <1196977707.23463.18.camel@localhost.localdomain>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-0.5.7-dbus-iface-segfault-fix.patch
Type: text/x-patch
Size: 527 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071206/fe53bf47/attachment.bin 


From raghavendra.akkasali  Thu Dec  6 18:22:58 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 07:52:58 +0530
Subject: Small doubt about wpa supplicant.
In-Reply-To: <1196938681.3980.17.camel@localhost.localdomain>
References: <58a444250712052324o1ff3e5bdj5c866b78725f852@mail.gmail.com>
	<1196938681.3980.17.camel@localhost.localdomain>
Message-ID: <58a444250712061822v628dc0eax4fb67b4984f69428@mail.gmail.com>

Hi Dan,

 Thanx for your reply.

  Will you please tell me how to disassociate using supplicant. In my
case after enabling supplicant as daemon, i will get ip using dhcp client
and then start working. Once my work is done. I have to disassociate with
the AP rt? or just killing wpa_supplicant is enough?

Also as I am integrating wpa supplicant to some device. using iwlist to scan
is must or is there some other way by which I can get almost same output as
that of scan. If using iwlist is must then I have to port iwlist also. So I
am asking some thing that does provide same output like iwlist but with less
size.

-Raghu.


On 12/6/07, Dan Williams <dcbw at redhat.com> wrote:
>
> On Thu, 2007-12-06 at 12:54 +0530, Raghavendra. S wrote:
> > Hi All,
> >
> >  I am newbie to wireless. So only this silly question comes from
> > me...:)
> >
> >  I am using wpa supplicant. Now on our device. we have some WLAN code
> > which does scanning..association ..etc all those basic wireless events
> > and then it call dhcp client to get IP.
> >
> >    Now they asked me to integrate wpa supplicant to provide security.
> > I saw even wpa supplicant does scanning, association....authentication
> > and then connects. In short wpa supplicant is a binary with config
> > file....which establishes secure channel.
> >
> > My question is if I integrate wpa supplicant I guess I dont need
> > previous code which does scanning..association...etc. I can directly
> > invoke wpa supplicant and then use dhcp client to get IP. Am I
> > correct?
>
> That is correct.  Get rid of your own scanning and association code.
> Create the right config file for wpa_supplicant, let it do it's job, and
> then when it's connected you do the DHCP manually.
>
> Dan
>
>
>
>


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/0c9e2e34/attachment.htm 


From j  Thu Dec  6 18:28:04 2007
From: j (Jouni Malinen)
Date: Thu, 6 Dec 2007 18:28:04 -0800
Subject: handshake error
In-Reply-To: <45114.66.201.209.31.1196949036.squirrel@mail1.canasoft.net>
References: <45114.66.201.209.31.1196949036.squirrel@mail1.canasoft.net>
Message-ID: <20071207022804.GV5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 08:50:36AM -0500, Frank wrote:

> and I have sent him all the attachments. He says that I need to use
> wpa_passphrase to encrypt the password instead of putting it into the
> config file in plain text.

That is not correct. There is no difference between configuring the
ASCII passphrase directly to wpa_supplicant and using wpa_passphrase to
convert it to a PSK apart from the extra CPU time it takes to do this
when parsing the configuration file. wpa_passphrase is not needed and it
is there only to allow some optimization on CPU use for very low-end
devices. In addition, wpa_passphrase does not encrypt the passphrase in
any way, it just derives the pre-shared key from it (and SSID). The end
result is as "plain text" as the input.

> wpa_driver_madwifi_associate: SETMLME[ASSOC] failed

I would suggest testing with the standard Linux wireless extensions
interface code instead of the old madwifi specific version, i.e., change
-Dmadwifi to -Dwext on the command line.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec  6 18:31:37 2007
From: j (Jouni Malinen)
Date: Thu, 6 Dec 2007 18:31:37 -0800
Subject: pre-authentication problem
In-Reply-To: <4b1890f00712061020v4622383dnadcb55a7c0ed9da9@mail.gmail.com>
References: <4b1890f00711300527w6f7c81ddo2bf08c3432ea34be@mail.gmail.com>
	<20071130174832.GA14202@kadzban.is-a-geek.net>
	<4b1890f00712061020v4622383dnadcb55a7c0ed9da9@mail.gmail.com>
Message-ID: <20071207023137.GW5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 07:20:37PM +0100, IO te wrote:

> ath0: STA 00:15:6d:53:a1:99 IEEE 802.1X: authenticated - EAP type: 13
> (TLS) (pre-authentication)
> ath0: STA 00:15:6d:53:a1:99 WPA: pre-authentication succeeded
> RSN: added PMKSA cache entry for 00:15:6d:53:a1:99
> RSN: added PMKID - hexdump(len=16): 1a 9b 20 37 fe e2 fa 6f a4 0b 5a
> b4 f6 ab d0 40
> ath0: STA 00:15:6d:53:a1:99 WPA: added PMKSA cache entry (pre-auth)
> IEEE 802.1X: 00:15:6d:53:a1:99 BE_AUTH entering state IDLE
> RSN: Removing pre-authentication STA entry for 00:15:6d:53:a1:99
> ath0: WPA rekeying GTK
> ...
> 
> What's happening?

Looks like RSN pre-authentication is completed successfully.

> Is there anything wrong in my configurations?

Do you have reason to believe that there would be? At least
pre-authentication seems to be working.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec  6 18:35:02 2007
From: j (Jouni Malinen)
Date: Thu, 6 Dec 2007 18:35:02 -0800
Subject: wpa_cli eapol_version
In-Reply-To: <4757F06D.5020906@gmail.com>
References: <4757F06D.5020906@gmail.com>
Message-ID: <20071207023502.GX5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 01:51:57PM +0100, Grant Williamson wrote:

> I curious if it is possible to set eapol_version using the command 
> client. I know I can add it to the wpa_supplicant.conf. But is there 
> anyway to set this on the fly.

It doesn't look like that. Why would you want to do this? EAPOL version
is not really something that should be changed and the only reason to
have the option for this in the configuration file is to allow people to
make wpa_supplicant claim that it is using old EAPOL version (while it
is actually not) to work around some broken 802.1X authenticator
implementations.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Thu Dec  6 20:39:27 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 10:09:27 +0530
Subject: Few more question on wpa supplicant
Message-ID: <58a444250712062039q73d5af4fqdb2a295df148f7aa@mail.gmail.com>

Hi All,

Does wpa_supplicant support

 -  Adhoc connection?

 -  Adhoc security?

 - Adhoc network creation with the given channel?

 - AP connection without encryption and authentication?

 - AP connection with WEP?
-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/23a97d54/attachment.htm 


From raghavendra.akkasali  Thu Dec  6 22:01:06 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 11:31:06 +0530
Subject: wpa supplicant compilation error
Message-ID: <58a444250712062201t7601a383jb3d904d505c406a6@mail.gmail.com>

Hi,

 I have following .config file.
#---------------------------------------------------------.config
starts-------------------------------
CONFIG_DRIVER_MARVELL=y
CONFIG_DRIVER_WEXT=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_TLS=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_PEAP=y
CONFIG_CTRL_IFACE=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_OTP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_PKCS12=y
CONFIG_PCSC=y
CONFIG_WINDOWS=n
CONFIG_EAP_PAX=y
BINDIR=wpa_supplicant-linux-arm-0.5.7-MSI-2-bin
CONFIG_ARM=y
#---------------------------------------------------------.config
ends-------------------------------

*got following error while compiling with CONFIG_PCSC=y. Is it must to use
CONFIG_PCSC=y, if we enable CONFIG_EAP_SIM=y or CONFIG_EAP_AKA=y? I am not
getting this error if I dont use CONFIG_PCSC=y.
*
/opt/toolchains/arm-linux-4.1.1/bin/arm-linux-gcc -I/usr/xocean/include -MMD
-O2 -Wall -g -mabi=aapcs-linux -I. -I../utils -I../hostapd
-DCONFIG_BACKEND_FILE -DCONFIG_DRIVER_WEXT -s -static
-DCONFIG_DRIVER_MARVELL -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5
-DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_SIM -DEAP_LEAP -DEAP_PSK -DEAP_AKA
-DEAP_TLV -DEAP_PAX -DIEEE8021X_EAPOL -DPCSC_FUNCS -I/usr/include/PCSC
-DEAP_TLS_FUNCS -DEAP_TLS_OPENSSL -DPKCS12_FUNCS -DINTERNAL_SHA256
-DCONFIG_WIRELESS_EXTENSION -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX
-c -o pcsc_funcs.o pcsc_funcs.c
pcsc_funcs.c:20:22: warning: winscard.h: No such file or directory
pcsc_funcs.c:93: error: expected specifier-qualifier-list before
'SCARDCONTEXT'
pcsc_funcs.c: In function 'scard_pin_needed':
pcsc_funcs.c:303: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:310: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c: In function 'scard_init':
pcsc_funcs.c:456: warning: implicit declaration of function
'SCardEstablishContext'
pcsc_funcs.c:456: error: 'SCARD_SCOPE_SYSTEM' undeclared (first use in this
function)
pcsc_funcs.c:456: error: (Each undeclared identifier is reported only once
pcsc_funcs.c:456: error: for each function it appears in.)
pcsc_funcs.c:457: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c:458: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c:464: warning: implicit declaration of function
'SCardListReaders'
pcsc_funcs.c:464: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c:480: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c:501: warning: implicit declaration of function 'SCardConnect'
pcsc_funcs.c:501: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c:501: error: 'SCARD_SHARE_SHARED' undeclared (first use in this
function)
pcsc_funcs.c:502: error: 'SCARD_PROTOCOL_T0' undeclared (first use in this
function)
pcsc_funcs.c:502: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:502: error: 'struct scard_data' has no member named 'protocol'
pcsc_funcs.c:504: error: 'SCARD_E_NO_SMARTCARD' undeclared (first use in
this function)
pcsc_funcs.c:515: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:515: error: 'struct scard_data' has no member named 'protocol'
pcsc_funcs.c:516: error: 'struct scard_data' has no member named 'protocol'
pcsc_funcs.c:518: warning: implicit declaration of function
'SCardBeginTransaction'
pcsc_funcs.c:518: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:528: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:537: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:540: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:544: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:572: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:590: error: 'struct scard_data' has no member named
'pin1_required'
pcsc_funcs.c:594: warning: implicit declaration of function
'SCardEndTransaction'
pcsc_funcs.c:594: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:594: error: 'SCARD_LEAVE_CARD' undeclared (first use in this
function)
pcsc_funcs.c:604: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c: In function 'scard_set_pin':
pcsc_funcs.c:623: error: 'struct scard_data' has no member named
'pin1_required'
pcsc_funcs.c: In function 'scard_deinit':
pcsc_funcs.c:654: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:655: warning: implicit declaration of function
'SCardDisconnect'
pcsc_funcs.c:655: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:655: error: 'SCARD_UNPOWER_CARD' undeclared (first use in this
function)
pcsc_funcs.c:656: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c:662: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c:663: warning: implicit declaration of function
'SCardReleaseContext'
pcsc_funcs.c:663: error: 'struct scard_data' has no member named 'ctx'
pcsc_funcs.c: In function 'scard_transmit':
pcsc_funcs.c:684: warning: implicit declaration of function 'SCardTransmit'
pcsc_funcs.c:684: error: 'struct scard_data' has no member named 'card'
pcsc_funcs.c:685: error: 'struct scard_data' has no member named 'protocol'
pcsc_funcs.c:685: error: 'SCARD_PROTOCOL_T1' undeclared (first use in this
function)
pcsc_funcs.c:686: error: 'SCARD_PCI_T1' undeclared (first use in this
function)
pcsc_funcs.c:686: error: 'SCARD_PCI_T0' undeclared (first use in this
function)
pcsc_funcs.c:690: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function '_scard_select_file':
pcsc_funcs.c:736: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function 'scard_select_file':
pcsc_funcs.c:786: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c: In function 'scard_get_record_len':
pcsc_funcs.c:798: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:806: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function 'scard_read_record':
pcsc_funcs.c:834: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:845: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function 'scard_read_file':
pcsc_funcs.c:885: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:888: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function 'scard_verify_pin':
pcsc_funcs.c:926: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:933: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c: In function 'scard_get_imsi':
pcsc_funcs.c:976: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c: In function 'scard_gsm_auth':
pcsc_funcs.c:1053: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:1066: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
pcsc_funcs.c:1069: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:1071: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:1085: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c: In function 'scard_umts_auth':
pcsc_funcs.c:1153: error: 'struct scard_data' has no member named 'sim_type'
pcsc_funcs.c:1169: error: 'SCARD_S_SUCCESS' undeclared (first use in this
function)
make: *** [pcsc_funcs.o] Error 1


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/ce0419c9/attachment.htm 


From raghavendra.akkasali  Thu Dec  6 22:06:33 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 11:36:33 +0530
Subject: getting undefined reference error while compiling/linking
Message-ID: <58a444250712062206l70e79977oc6bbfa31473c2b16@mail.gmail.com>

Hi,

 I have my .config file as below
#-------------------------------------------------------.config
starts-----------------------------------------------
CONFIG_DRIVER_MARVELL=y
CONFIG_DRIVER_WEXT=y
CONFIG_WIRELESS_EXTENSION=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_TLS=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_PEAP=y
CONFIG_CTRL_IFACE=y
CONFIG_EAP_SIM=y
CONFIG_EAP_AKA=y
CONFIG_EAP_PSK=y
CONFIG_EAP_OTP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_PKCS12=y
CONFIG_WINDOWS=n
CONFIG_EAP_FAST=y
CONFIG_EAP_PAX=y
BINDIR=wpa_supplicant-linux-arm-0.5.7-MSI-2-bin
CONFIG_ARM=y
#-------------------------------------------------------.config
ends-------------------------------------------------
*I am getting undefine reference error if I use CONFIG_EAP_FAST=y. can any
body tell me how to solve this.*
*I am using wpa supplicant 0.5.7 and opensll 0.9.7. Below are error message.
*

/opt/toolchains/arm-linux-4.1.1/bin/arm-linux-gcc  -o wpa_supplicant
config.o common.o md5.o md4.o rc4.o sha1.o des.o os_unix.o eloop.oconfig_file.o
base64.o l2_packet_linux.o eap_tls.o eap_peap.o eap_ttls.o eap_md5.o
eap_mschapv2.o eap_gtc.o eap_otp.o eap_sim.o eap_leap.o eap_psk.o
eap_psk_common.o eap_aka.o eap_sim_common.o eap_tlv.o eap_fast.o eap_pax.o
eap_pax_common.o eapol_sm.o eap.o eap_methods.o eap_tls_common.o
tls_openssl.o ms_funcs.o crypto.o ctrl_iface.o ctrl_iface_unix.o wpa.o
preauth.o pmksa_cache.o aes_wrap.o wpa_supplicant.o events.o main.o
drivers.o driver_marvell.o driver_wext.o -L/usr/xocean/lib/ -lssl -lcrypto
-s -static
ctrl_iface_unix.o: In function `wpa_supplicant_ctrl_iface_init':
/mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/ctrl_iface_unix.c:297:
warning: Using 'getgrnam' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking
tls_openssl.o: In function `tls_connection_client_hello_ext':
/mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2137:
undefined reference to `SSL_set_hello_extension'
tls_openssl.o: In function `tls_connection_set_master_key':
/mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2031:
undefined reference to `SSL_set_session_secret_cb'
/mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2035:
undefined reference to `SSL_set_session_secret_cb'
collect2: ld returned 1 exit status
make: *** [wpa_supplicant] Error 1

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/111e65f7/attachment.htm 


From anjali_shirvoikar  Thu Dec  6 22:58:47 2007
From: anjali_shirvoikar (Anjali Shirvoikar)
Date: Fri, 7 Dec 2007 12:28:47 +0530
Subject: WPA supplicant not working for LEAP
Message-ID: <00c401c8389e$a52b5d90$d705f40a@persistent.co.in>

Hi,

The environment is

WIFI Card ? VIA Wyse USB Wireless
Driver ? vntwusb
AP ? DLink DWL2100
Radius server ? Free radius server

The AP is configured for TKIP with WPA-EAP. The radius server is set for
LEAP. The association with AP takes place successfully (seen in the AP log),
a packet trace at the radius server shows that the LEAP conversation takes
place(4 packets are exchanged) and ends in a success EAP packet being sent
to the wpa_supplicant. The wpa_supplicant then seems to be sending a 8 octet
challenge to the AP which is not forwarded by the AP to the RS (not seen in
the packet trace) Could anybody tell me how to fix this issue? Is LEAP to be
used only with Cisco AP?

The wpa_supplicant conf file has the following contents:
================
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
??????????? ssid="WyseWL1"
??????????? scan_ssid=1
??????????? proto=WPA
??????????? key_mgmt=WPA-EAP
??????????? identity="john"
??????????? password="hello"
??????????? eap=LEAP
}



The log file of the wpa_supplicant is as follows
==========================================================
Initializing interface 'wlan0' conf '/tmp/wpa.conf' driver 'vntwusb'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/tmp/wpa.conf' -> '/tmp/wpa.conf'
Reading configuration file '/tmp/wpa.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0' (DEPRECATED)
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=7):
???? 57 79 73 65 57 4c 31????????????????????????????? WyseWL1???????? 
scan_ssid=1 (0x1)
proto: 0x1
key_mgmt: 0x1
identity - hexdump_ascii(len=4):
???? 6a 6f 68 6e?????????????????????????????????????? john??????????? 
password - hexdump_ascii(len=5): [REMOVED]
eap methods - hexdump(len=16): 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00
00
Priority group 0
?? id=0 ssid='WyseWL1'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_viawget_init: 
Own MAC address: 00:20:b3:10:33:b2
wpa_driver_viawget_set_wpa: 1 
wpa_driver_viawget_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
addr= - hexdump(len=6): ff ff ff ff ff ff
key= - hexdump(len=0): [NULL]
wpa_driver_viawget_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
addr= - hexdump(len=6): ff ff ff ff ff ff
key= - hexdump(len=0): [NULL]
wpa_driver_viawget_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
addr= - hexdump(len=6): ff ff ff ff ff ff
key= - hexdump(len=0): [NULL]
wpa_driver_viawget_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
addr= - hexdump(len=6): ff ff ff ff ff ff
key= - hexdump(len=0): [NULL]
wpa_driver_viawget_set_countermeasures - not yet implemented
wpa_driver_viawget_set_drop_unencrypted: 1 
Setting scan request: 0 sec 100000 usec
ctrl_interface_group=0
mike:first time transfer SM-->wlan0
mike:total reserve config is 1
Transfer:device name=wlan0
Transfer:key_mgmt=1
Transfer:proto=1
Transfer:eap=17
Transfer:authen status=FALSE
mike:wpa announce ok
Added interface wlan0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
???? 57 79 73 65 57 4c 31????????????????????????????? WyseWL1???????? 
Trying to get current scan results first without requesting a new scan to
speed up initial association
wpa_driver_viawget_get_scan_results: 
VIAWGET: buf - hexdump(len=6): 00 13 46 e5 b4 9c
VIAWGET: AP WPA IEs - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 01
VIAWGET: AP RSN IEs - hexdump(len=0):
VIAWGET: buf - hexdump(len=6): 00 1c 0e 42 4d f0
VIAWGET: AP WPA IEs - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02 28 00
VIAWGET: AP RSN IEs - hexdump(len=0):
Received 2 AP of scan results 
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:13:46:e5:b4:9c ssid='WyseWL1' wpa_ie_len=24 rsn_ie_len=0 caps=0x0
?? selected based on WPA IE
?? selected WPA AP 00:13:46:e5:b4:9c ssid='WyseWL1'
Try to find non-WPA AP
Trying to associate with 00:13:46:e5:b4:9c (SSID='WyseWL1' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 1 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01
00 00 50 f2 02 01 00 00 50 f2 01
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01
No keys have been configured - skip key clearing
wpa_driver_viawget_set_drop_unencrypted: 1 
State: SCANNING -> ASSOCIATING
wpa_driver_viawget_associate:? pairwise_suite = 2, group_suite = 2,
key_mgmt_suite = 0 auth_alg = 1
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
wpa_driver_viawget_event_receive: 
RECEIVE EVENT - hexdump(len=80): 01 2d 00 1e 00 00 07 57 79 73 65 57 4c 31
01 08 82 84 8b 96 0c 18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00
50 f2 02 01 00 00 50 f2 01 00 00 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24
60 6c dd 0c 00 03 7f 02 01 01 00 00 02 a3 40 00
VIAWGET: ASSOC MESSAGE (left: 75)
VIAWGET: copying %d bytes into req_ies - hexdump(len=75): 00 07 57 79 73 65
57 4c 31 01 08 82 84 8b 96 0c 18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 01 00 00 73 75 70 70 6c 69 63 11 00 00 00
60 ca 14 08 50 13 13 42 10 00 00 00 38 00 00 00 04 00 00
Association info event
req_ies - hexdump(len=45): 00 07 57 79 73 65 57 4c 31 01 08 82 84 8b 96 0c
18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50
f2 01 00 00
resp_ies - hexdump(len=30): 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24 60 6c
dd 0c 00 03 7f 02 01 01 00 00 02 a3 40 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 01 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_viawget_get_bssid: 
Associated to a new BSS: BSSID=00:13:46:e5:b4:9c
No keys have been configured - skip key clearing
Associated with 00:13:46:e5:b4:9c
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=9): 01 00 00 05 01 00 00 05 01
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=0 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
???? 6a 6f 68 6e?????????????????????????????????????? john??????????? 
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=13): 01 00 00 09 02 00 00 09 01 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=9): 01 00 00 05 01 00 00 05 01
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=0 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state RETRANSMIT
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=13): 01 00 00 09 02 00 00 09 01 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=25): 01 00 00 15 01 01 00 15 11 01 00 08 70 29 48 b3
78 d6 8e f0 6a 6f 68 6e 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=1 method=17 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
EAP: Initialize selected EAP method: vendor 0 method 17 (LEAP)
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 17 (LEAP) selected
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Request
EAP-LEAP: Challenge from AP - hexdump(len=8): 70 29 48 b3 78 d6 8e f0
EAP-LEAP: Generating Challenge Response
EAP-LEAP: Response - hexdump(len=24): ca ca 14 8b 67 03 9d c5 5d 5c 6a de 2f
0c 61 db 4d 7e 1b 68 ef 94 7a dc
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=40): 01 00 00 24 02 01 00 24 11 01 00 18 ca ca 14 8b
67 03 9d c5 5d 5c 6a de 2f 0c 61 db 4d 7e 1b 68 ef 94 7a dc 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 03 02 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Success
EAP-LEAP: Challenge to AP/AS - hexdump(len=8): 6f 48 5d ec 41 a2 11 27
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=24): 01 00 00 14 01 02 00 14 11 01 00 08 6f 48 5d ec
41 a2 11 27 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
EAPOL: authWhile --> 0
EAPOL: SUPP_BE entering state TIMEOUT
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 03 02 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: deinitialize previously used EAP method (17, LEAP) at INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP-Success Id mismatch - reqId=2 lastId=-1
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 04 02 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Failure
EAP: EAP-Success Id mismatch - reqId=2 lastId=-1
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=9): 01 00 00 05 01 03 00 05 01
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=3 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
???? 6a 6f 68 6e?????????????????????????????????????? john??????????? 
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=13): 01 00 00 09 02 03 00 09 01 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=25): 01 00 00 15 01 04 00 15 11 01 00 08 e6 cc 3d 7c
6d 34 a6 45 6a 6f 68 6e 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=4 method=17 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
EAP: Initialize selected EAP method: vendor 0 method 17 (LEAP)
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 17 (LEAP) selected
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Request
EAP-LEAP: Challenge from AP - hexdump(len=8): e6 cc 3d 7c 6d 34 a6 45
EAP-LEAP: Generating Challenge Response
EAP-LEAP: Response - hexdump(len=24): ec 8f 2d da bf 44 11 02 bd 3a 21 46 62
05 c9 e4 94 78 8e cc 48 55 8c 05
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=40): 01 00 00 24 02 04 00 24 11 01 00 18 ec 8f 2d da
bf 44 11 02 bd 3a 21 46 62 05 c9 e4 94 78 8e cc 48 55 8c 05 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 03 05 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Success
EAP-LEAP: Challenge to AP/AS - hexdump(len=8): d9 bc df 60 6e d0 b1 20
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=24): 01 00 00 14 01 05 00 14 11 01 00 08 d9 bc df 60
6e d0 b1 20 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
Authentication with 00:13:46:e5:b4:9c timed out.
Added BSSID 00:13:46:e5:b4:9c into blacklist
wpa_driver_viawget_disassociate: 
addr= - hexdump(len=6): 00 13 46 e5 b4 9c
No keys have been configured - skip key clearing
State: ASSOCIATED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
wpa_driver_viawget_scan: 
wpa_driver_viawget_scan_timeout: 
wpa_driver_viawget_get_scan_results: 
VIAWGET: buf - hexdump(len=6): 00 13 46 e5 b4 9c
VIAWGET: AP WPA IEs - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 01
VIAWGET: AP RSN IEs - hexdump(len=0):
VIAWGET: buf - hexdump(len=6): 00 1c 0e 42 4d f0
VIAWGET: AP WPA IEs - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 02 28 00
VIAWGET: AP RSN IEs - hexdump(len=0):
Received 2 AP of scan results 
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:13:46:e5:b4:9c ssid='WyseWL1' wpa_ie_len=24 rsn_ie_len=0 caps=0x0
?? selected based on WPA IE
?? selected WPA AP 00:13:46:e5:b4:9c ssid='WyseWL1'
Try to find non-WPA AP
Trying to associate with 00:13:46:e5:b4:9c (SSID='WyseWL1' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 1 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01
00 00 50 f2 02 01 00 00 50 f2 01
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT 802.1X
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50
f2 02 01 00 00 50 f2 02 01 00 00 50 f2 01
No keys have been configured - skip key clearing
wpa_driver_viawget_set_drop_unencrypted: 1 
State: SCANNING -> ASSOCIATING
wpa_driver_viawget_associate:? pairwise_suite = 2, group_suite = 2,
key_mgmt_suite = 0 auth_alg = 1
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
wpa_driver_viawget_event_receive: 
RECEIVE EVENT - hexdump(len=80): 01 2d 00 1e 00 00 07 57 79 73 65 57 4c 31
01 08 82 84 8b 96 0c 18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00
50 f2 02 01 00 00 50 f2 01 00 00 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24
60 6c dd 0c 00 03 7f 02 01 01 00 00 02 a3 40 00
VIAWGET: ASSOC MESSAGE (left: 75)
VIAWGET: copying %d bytes into req_ies - hexdump(len=75): 00 07 57 79 73 65
57 4c 31 01 08 82 84 8b 96 0c 18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02
01 00 00 50 f2 02 01 00 00 50 f2 01 00 00 00 00 00 07 e0 3c ca 29 00 00 00
01 08 82 84 8b 96 0c 18 30 48 32 04 12 24 60 6c dd 0c 00
Association info event
req_ies - hexdump(len=45): 00 07 57 79 73 65 57 4c 31 01 08 82 84 8b 96 0c
18 30 48 dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50
f2 01 00 00
resp_ies - hexdump(len=30): 01 08 82 84 8b 96 0c 18 30 48 32 04 12 24 60 6c
dd 0c 00 03 7f 02 01 01 00 00 02 a3 40 00
WPA: set own WPA/RSN IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 01 00 00
State: ASSOCIATING -> ASSOCIATED
wpa_driver_viawget_get_bssid: 
Associated to a new BSS: BSSID=00:13:46:e5:b4:9c
No keys have been configured - skip key clearing
Associated with 00:13:46:e5:b4:9c
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
EAP: EAP entering state INITIALIZE
EAP: deinitialize previously used EAP method (17, LEAP) at INITIALIZE
EAP: EAP entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=9): 01 00 00 05 01 00 00 05 01
Setting authentication timeout: 70 sec 0 usec
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=0 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state IDENTITY
CTRL-EVENT-EAP-STARTED EAP authentication started
EAP: EAP-Request Identity data - hexdump_ascii(len=0):
EAP: using real identity - hexdump_ascii(len=4):
???? 6a 6f 68 6e?????????????????????????????????????? john??????????? 
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=13): 01 00 00 09 02 00 00 09 01 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=9): 01 00 00 05 01 00 00 05 01
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=0 method=1 vendor=0 vendorMethod=0
EAP: EAP entering state RETRANSMIT
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=13): 01 00 00 09 02 00 00 09 01 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=25): 01 00 00 15 01 01 00 15 11 01 00 08 99 68 69 af
3d 81 10 e4 6a 6f 68 6e 00
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Request id=1 method=17 vendor=0 vendorMethod=0
EAP: EAP entering state GET_METHOD
EAP: Initialize selected EAP method: vendor 0 method 17 (LEAP)
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 17 (LEAP) selected
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Request
EAP-LEAP: Challenge from AP - hexdump(len=8): 99 68 69 af 3d 81 10 e4
EAP-LEAP: Generating Challenge Response
EAP-LEAP: Response - hexdump(len=24): 4a 13 c9 ea 23 40 7d b1 c2 b2 b6 07 11
07 b6 fc dd 1d 90 d4 e6 bd ab bb
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=40): 01 00 00 24 02 01 00 24 11 01 00 18 4a 13 c9 ea
23 40 7d b1 c2 b2 b6 07 11 07 b6 fc dd 1d 90 d4 e6 bd ab bb 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 03 02 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP entering state METHOD
EAP-LEAP: Processing EAP-Success
EAP-LEAP: Challenge to AP/AS - hexdump(len=8): 82 6e 32 76 67 4a 82 c4
EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL - hexdump(len=24): 01 00 00 14 01 02 00 14 11 01 00 08 82 6e 32 76
67 4a 82 c4 6a 6f 68 6e
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
EAPOL: authWhile --> 0
EAPOL: SUPP_BE entering state TIMEOUT
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
RX EAPOL from 00:13:46:e5:b4:9c
RX EAPOL - hexdump(len=8): 01 00 00 04 03 02 00 04
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_PAE entering state RESTART
EAP: EAP entering state INITIALIZE
EAP: deinitialize previously used EAP method (17, LEAP) at INITIALIZE
EAP: EAP entering state IDLE
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Success
EAP: EAP-Success Id mismatch - reqId=2 lastId=-1
EAP: EAP entering state DISCARD
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: startWhen --> 0
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_viawget_deauthenticate - not yet implemented
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portValid=0
wpa_driver_viawget_set_wpa: 0 
wpa_driver_viawget_set_drop_unencrypted: 0 
wpa_driver_viawget_set_countermeasures - not yet implemented
No keys have been configured - skip key clearing
Removed BSSID 00:13:46:e5:b4:9c from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout

Regards,
Anjali




From s.raghu  Thu Dec  6 23:31:27 2007
From: s.raghu (RAGHAVENDRA SADARAMACHANDRA)
Date: Fri, 07 Dec 2007 07:31:27 +0000 (GMT)
Subject: getting RSN: not in suitable state for new pre-authentication
Message-ID: <0JSO00IGW4WF4W@ms13.samsung.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/2ef872bb/attachment.htm 


From dcbw  Fri Dec  7 01:53:45 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 04:53:45 -0500
Subject: Small doubt about wpa supplicant.
In-Reply-To: <58a444250712061822v628dc0eax4fb67b4984f69428@mail.gmail.com>
References: <58a444250712052324o1ff3e5bdj5c866b78725f852@mail.gmail.com>
	<1196938681.3980.17.camel@localhost.localdomain>
	<58a444250712061822v628dc0eax4fb67b4984f69428@mail.gmail.com>
Message-ID: <1197021225.2603.10.camel@localhost.localdomain>

On Fri, 2007-12-07 at 07:52 +0530, Raghavendra. S wrote:
> Hi Dan,
>  
>  Thanx for your reply.
>  
>   Will you please tell me how to disassociate using supplicant. In my
> case after enabling supplicant as daemon, i will get ip using dhcp
> client and then start working. Once my work is done. I have to
> disassociate with the AP rt? or just killing wpa_supplicant is enough?

Yes, but do it cleanly by sending it the TERM signal so that it will
remove keys and clear other stuff when it exits.

> Also as I am integrating wpa supplicant to some device. using iwlist
> to scan is must or is there some other way by which I can get almost
> same output as that of scan. If using iwlist is must then I have
> to port iwlist also. So I am asking some thing that does provide same
> output like iwlist but with less size.

There are a few options; if you're using C you can do your own scan
code, it's not really more than 200 lines of C.  Or, you can look at
using wpa_cli, or talk to wpa_supplicant directly over the control
socket just like wpa_cli does.  Both ways allow you to get scan results.

Dan
 
> -Raghu. 
> 
>  
> On 12/6/07, Dan Williams <dcbw at redhat.com> wrote: 
>         On Thu, 2007-12-06 at 12:54 +0530, Raghavendra. S wrote:
>         > Hi All,
>         >
>         >  I am newbie to wireless. So only this silly question comes
>         from 
>         > me...:)
>         >
>         >  I am using wpa supplicant. Now on our device. we have some
>         WLAN code
>         > which does scanning..association ..etc all those basic
>         wireless events
>         > and then it call dhcp client to get IP. 
>         >
>         >    Now they asked me to integrate wpa supplicant to provide
>         security.
>         > I saw even wpa supplicant does scanning,
>         association....authentication
>         > and then connects. In short wpa supplicant is a binary with
>         config 
>         > file....which establishes secure channel.
>         >
>         > My question is if I integrate wpa supplicant I guess I dont
>         need
>         > previous code which does scanning..association...etc. I can
>         directly
>         > invoke wpa supplicant and then use dhcp client to get IP. Am
>         I 
>         > correct?
>         
>         That is correct.  Get rid of your own scanning and association
>         code.
>         Create the right config file for wpa_supplicant, let it do
>         it's job, and
>         then when it's connected you do the DHCP manually. 
>         
>         Dan
>         
>         
>         
> 
> 
> 
> -- 
> Regards & Thanks
> Raghavendra. S 




From dcbw  Fri Dec  7 01:56:10 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 04:56:10 -0500
Subject: Few more question on wpa supplicant
In-Reply-To: <58a444250712062039q73d5af4fqdb2a295df148f7aa@mail.gmail.com>
References: <58a444250712062039q73d5af4fqdb2a295df148f7aa@mail.gmail.com>
Message-ID: <1197021370.2603.13.camel@localhost.localdomain>

On Fri, 2007-12-07 at 10:09 +0530, Raghavendra. S wrote:
> Hi All,
>  
> Does wpa_supplicant support 
>  -  Adhoc connection?

Yes, but only fully in 0.6.x.  0.5.x doesn't have the ability to tell
the card which frequency to communicate on, which is needed for some
drivers to successfully complete the adhoc setup.

>  -  Adhoc security?

Yes, for WPA-PSK and WEP.

>  - Adhoc network creation with the given channel?

With 0.6.x, yes.  With 0.5.x and lower, no.

>  - AP connection without encryption and authentication?

Do you mean having your client connect to an "open" access point?  If
so, then yes.

>  - AP connection with WEP?

Do you mean having the client connect to a WEP AP?  If so, then yes.

Dan





From dcbw  Fri Dec  7 01:58:22 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 04:58:22 -0500
Subject: wpa supplicant compilation error
In-Reply-To: <58a444250712062201t7601a383jb3d904d505c406a6@mail.gmail.com>
References: <58a444250712062201t7601a383jb3d904d505c406a6@mail.gmail.com>
Message-ID: <1197021502.2603.16.camel@localhost.localdomain>

On Fri, 2007-12-07 at 11:31 +0530, Raghavendra. S wrote:
> Hi,
>  
>  I have following .config file.
> #---------------------------------------------------------.config
> starts-------------------------------
> CONFIG_DRIVER_MARVELL=y
> CONFIG_DRIVER_WEXT=y
> CONFIG_WIRELESS_EXTENSION=y
> CONFIG_IEEE8021X_EAPOL=y
> CONFIG_EAP_MD5=y
> CONFIG_EAP_TLS=y
> CONFIG_EAP_TTLS=y
> CONFIG_EAP_LEAP=y
> CONFIG_EAP_PEAP=y
> CONFIG_CTRL_IFACE=y 
> CONFIG_EAP_SIM=y
> CONFIG_EAP_AKA=y
> CONFIG_EAP_PSK=y
> CONFIG_EAP_OTP=y
> CONFIG_EAP_GTC=y
> CONFIG_EAP_MSCHAPV2=y
> CONFIG_PKCS12=y
> CONFIG_PCSC=y
> CONFIG_WINDOWS=n
> CONFIG_EAP_PAX=y
> BINDIR=wpa_supplicant- linux-arm-0.5.7-MSI-2-bin
> CONFIG_ARM=y
> #---------------------------------------------------------.config
> ends-------------------------------
>  
> got following error while compiling with CONFIG_PCSC=y. Is it must to
> use CONFIG_PCSC=y, if we enable CONFIG_EAP_SIM=y or CONFIG_EAP_AKA=y?
> I am not getting this error if I dont use CONFIG_PCSC=y.
> 
> /opt/toolchains/arm-linux-4.1.1/bin/arm-linux-gcc
> -I/usr/xocean/include -MMD -O2 -Wall -g -mabi=aapcs-linux -I.
> -I../utils -I../hostapd -DCONFIG_BACKEND_FILE -DCONFIG_DRIVER_WEXT -s
> -static -DCONFIG_DRIVER_MARVELL -DEAP_TLS -DEAP_PEAP -DEAP_TTLS
> -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_SIM -DEAP_LEAP
> -DEAP_PSK -DEAP_AKA -DEAP_TLV -DEAP_PAX -DIEEE8021X_EAPOL -DPCSC_FUNCS
> -I/usr/include/PCSC -DEAP_TLS_FUNCS -DEAP_TLS_OPENSSL -DPKCS12_FUNCS
> -DINTERNAL_SHA256 -DCONFIG_WIRELESS_EXTENSION -DCONFIG_CTRL_IFACE
> -DCONFIG_CTRL_IFACE_UNIX   -c -o pcsc_funcs.o pcsc_funcs.c 
> pcsc_funcs.c:20:22: warning: winscard.h: No such file or directory

You don't have the necessary libraries to use PCSC then.  I think you
want this:

http://pcsclite.alioth.debian.org/

Or, just don't enable that option if you don't care about using
smartcards with wpa_supplicant.

Dan

> pcsc_funcs.c:93: error: expected specifier-qualifier-list before
> 'SCARDCONTEXT'
> pcsc_funcs.c: In function 'scard_pin_needed':
> pcsc_funcs.c:303: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:310: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c: In function 'scard_init': 
> pcsc_funcs.c:456: warning: implicit declaration of function
> 'SCardEstablishContext'
> pcsc_funcs.c:456: error: 'SCARD_SCOPE_SYSTEM' undeclared (first use in
> this function)
> pcsc_funcs.c:456: error: (Each undeclared identifier is reported only
> once 
> pcsc_funcs.c:456: error: for each function it appears in.)
> pcsc_funcs.c:457: error: 'struct scard_data' has no member named 'ctx'
> pcsc_funcs.c:458: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c:464: warning: implicit declaration of function
> 'SCardListReaders'
> pcsc_funcs.c:464: error: 'struct scard_data' has no member named 'ctx'
> pcsc_funcs.c:480: error: 'struct scard_data' has no member named
> 'ctx' 
> pcsc_funcs.c:501: warning: implicit declaration of function
> 'SCardConnect'
> pcsc_funcs.c:501: error: 'struct scard_data' has no member named 'ctx'
> pcsc_funcs.c:501: error: 'SCARD_SHARE_SHARED' undeclared (first use in
> this function) 
> pcsc_funcs.c:502: error: 'SCARD_PROTOCOL_T0' undeclared (first use in
> this function)
> pcsc_funcs.c:502: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c:502: error: 'struct scard_data' has no member named
> 'protocol' 
> pcsc_funcs.c:504: error: 'SCARD_E_NO_SMARTCARD' undeclared (first use
> in this function)
> pcsc_funcs.c:515: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c:515: error: 'struct scard_data' has no member named
> 'protocol' 
> pcsc_funcs.c:516: error: 'struct scard_data' has no member named
> 'protocol'
> pcsc_funcs.c:518: warning: implicit declaration of function
> 'SCardBeginTransaction'
> pcsc_funcs.c:518: error: 'struct scard_data' has no member named
> 'card' 
> pcsc_funcs.c:528: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:537: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:540: error: 'struct scard_data' has no member named
> 'sim_type' 
> pcsc_funcs.c:544: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:572: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:590: error: 'struct scard_data' has no member named
> 'pin1_required' 
> pcsc_funcs.c:594: warning: implicit declaration of function
> 'SCardEndTransaction'
> pcsc_funcs.c:594: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c:594: error: 'SCARD_LEAVE_CARD' undeclared (first use in
> this function) 
> pcsc_funcs.c:604: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c: In function 'scard_set_pin':
> pcsc_funcs.c:623: error: 'struct scard_data' has no member named
> 'pin1_required' 
> pcsc_funcs.c: In function 'scard_deinit':
> pcsc_funcs.c:654: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c:655: warning: implicit declaration of function
> 'SCardDisconnect' 
> pcsc_funcs.c:655: error: 'struct scard_data' has no member named
> 'card'
> pcsc_funcs.c:655: error: 'SCARD_UNPOWER_CARD' undeclared (first use in
> this function)
> pcsc_funcs.c:656: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c:662: error: 'struct scard_data' has no member named 'ctx'
> pcsc_funcs.c:663: warning: implicit declaration of function
> 'SCardReleaseContext'
> pcsc_funcs.c:663: error: 'struct scard_data' has no member named
> 'ctx' 
> pcsc_funcs.c: In function 'scard_transmit':
> pcsc_funcs.c:684: warning: implicit declaration of function
> 'SCardTransmit'
> pcsc_funcs.c:684: error: 'struct scard_data' has no member named
> 'card' 
> pcsc_funcs.c:685: error: 'struct scard_data' has no member named
> 'protocol'
> pcsc_funcs.c:685: error: 'SCARD_PROTOCOL_T1' undeclared (first use in
> this function)
> pcsc_funcs.c:686: error: 'SCARD_PCI_T1' undeclared (first use in this
> function) 
> pcsc_funcs.c:686: error: 'SCARD_PCI_T0' undeclared (first use in this
> function)
> pcsc_funcs.c:690: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function)
> pcsc_funcs.c: In function '_scard_select_file': 
> pcsc_funcs.c:736: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function)
> pcsc_funcs.c: In function 'scard_select_file':
> pcsc_funcs.c:786: error: 'struct scard_data' has no member named
> 'sim_type' 
> pcsc_funcs.c: In function 'scard_get_record_len':
> pcsc_funcs.c:798: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:806: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c: In function 'scard_read_record':
> pcsc_funcs.c:834: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:845: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c: In function 'scard_read_file':
> pcsc_funcs.c:885: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:888: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c: In function 'scard_verify_pin':
> pcsc_funcs.c:926: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:933: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function) 
> pcsc_funcs.c: In function 'scard_get_imsi':
> pcsc_funcs.c:976: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c: In function 'scard_gsm_auth':
> pcsc_funcs.c:1053: error: 'struct scard_data' has no member named
> 'sim_type' 
> pcsc_funcs.c:1066: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function)
> pcsc_funcs.c:1069: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c:1071: error: 'struct scard_data' has no member named
> 'sim_type' 
> pcsc_funcs.c:1085: error: 'struct scard_data' has no member named
> 'sim_type'
> pcsc_funcs.c: In function 'scard_umts_auth':
> pcsc_funcs.c:1153: error: 'struct scard_data' has no member named
> 'sim_type' 
> pcsc_funcs.c:1169: error: 'SCARD_S_SUCCESS' undeclared (first use in
> this function)
> make: *** [pcsc_funcs.o] Error 1
> 
> 
> -- 
> Regards & Thanks
> Raghavendra. S 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From dcbw  Fri Dec  7 01:59:36 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 04:59:36 -0500
Subject: getting undefined reference error while compiling/linking
In-Reply-To: <58a444250712062206l70e79977oc6bbfa31473c2b16@mail.gmail.com>
References: <58a444250712062206l70e79977oc6bbfa31473c2b16@mail.gmail.com>
Message-ID: <1197021576.2603.19.camel@localhost.localdomain>

On Fri, 2007-12-07 at 11:36 +0530, Raghavendra. S wrote:
> Hi,
>  
>  I have my .config file as below
> #-------------------------------------------------------.config
> starts-----------------------------------------------
> CONFIG_DRIVER_MARVELL=y
> CONFIG_DRIVER_WEXT=y
> CONFIG_WIRELESS_EXTENSION=y
> CONFIG_IEEE8021X_EAPOL=y
> CONFIG_EAP_MD5=y
> CONFIG_EAP_TLS=y
> CONFIG_EAP_TTLS=y
> CONFIG_EAP_LEAP=y
> CONFIG_EAP_PEAP=y
> CONFIG_CTRL_IFACE=y 
> CONFIG_EAP_SIM=y
> CONFIG_EAP_AKA=y
> CONFIG_EAP_PSK=y
> CONFIG_EAP_OTP=y
> CONFIG_EAP_GTC=y
> CONFIG_EAP_MSCHAPV2=y
> CONFIG_PKCS12=y
> CONFIG_WINDOWS=n
> CONFIG_EAP_FAST=y
> CONFIG_EAP_PAX=y
> BINDIR=wpa_supplicant- linux-arm-0.5.7-MSI-2-bin
> CONFIG_ARM=y
> #-------------------------------------------------------.config
> ends-------------------------------------------------
> 
> I am getting undefine reference error if I use CONFIG_EAP_FAST=y. can
> any body tell me how to solve this.
> I am using wpa supplicant 0.5.7 and opensll 0.9.7. Below are error
> message.
>  
> /opt/toolchains/arm-linux-4.1.1/bin/arm-linux-gcc  -o wpa_supplicant
> config.o common.o md5.o md4.o rc4.o sha1.o des.o os_unix.o eloop.o
> config_file.o base64.o l2_packet_linux.o eap_tls.o eap_peap.o
> eap_ttls.o eap_md5.o eap_mschapv2.o eap_gtc.o eap_otp.o eap_sim.o
> eap_leap.o eap_psk.o eap_psk_common.o eap_aka.o eap_sim_common.o
> eap_tlv.o eap_fast.o eap_pax.o eap_pax_common.o eapol_sm.o eap.o
> eap_methods.o eap_tls_common.o tls_openssl.o ms_funcs.o crypto.o
> ctrl_iface.o ctrl_iface_unix.o wpa.o preauth.o pmksa_cache.o
> aes_wrap.o wpa_supplicant.o events.o main.o drivers.o driver_marvell.o
> driver_wext.o -L/usr/xocean/lib/ -lssl -lcrypto -s -static 
> ctrl_iface_unix.o: In function `wpa_supplicant_ctrl_iface_init':
> /mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/ctrl_iface_unix.c:297: warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking 
> tls_openssl.o: In function `tls_connection_client_hello_ext':
> /mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2137: undefined reference to `SSL_set_hello_extension'
> tls_openssl.o: In function `tls_connection_set_master_key': 
> /mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2031: undefined reference to `SSL_set_session_secret_cb'
> /mnt/hgfs/security/marvell/wpa_supplicant-linux-src-0.5.7-MSI-2/tls_openssl.c:2035: undefined reference to `SSL_set_session_secret_cb' 
> collect2: ld returned 1 exit status
> make: *** [wpa_supplicant] Error 1

Looks like your version of openssl is not good enough, or not compiled
with the right options.  Either fix that, or don't compile
wpa_supplicant with EAP-FAST support.

Dan






From raghavendra.akkasali  Fri Dec  7 03:15:40 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 16:45:40 +0530
Subject: Small code which gives output similar to "iwlist eth0 scan"
Message-ID: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>

Hi,

   Does any one know small AP scan code which gives similar/same output as
that of *"iwlist eth0 scan"*. I dont want to use iwlist because of its size.

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/3e0ff5cf/attachment.htm 


From dcbw  Fri Dec  7 03:21:23 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 06:21:23 -0500
Subject: Small code which gives output similar to "iwlist eth0 scan"
In-Reply-To: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
References: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
Message-ID: <1197026483.4655.1.camel@localhost.localdomain>

On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S wrote:
> Hi,
>  
>    Does any one know small AP scan code which gives similar/same
> output as that of "iwlist eth0 scan". I dont want to use iwlist
> because of its size.

Look at the driver_wext.c code from wpa_supplicant at
wpa_driver_wext_scan() and wpa_driver_wext_get_scan_results().  You
don't need to screenscrape output if you can just use the values
directly.

Dan






From raghavendra.akkasali  Fri Dec  7 03:50:22 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 7 Dec 2007 17:20:22 +0530
Subject: Small code which gives output similar to "iwlist eth0 scan"
In-Reply-To: <1197026483.4655.1.camel@localhost.localdomain>
References: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
	<1197026483.4655.1.camel@localhost.localdomain>
Message-ID: <58a444250712070350o194dff0eg71a6f835fde9e10d@mail.gmail.com>

Hi Dan,

 Actually in my case I want to get scan result first then configure
wpa_supplicant.conf and then I will enable wpa_supplicant. Because user has
to first see the scanned result and after that he can configure to which AP
he want to associate with and security models he want to use. So I need some
independent small AP scan code similar to "iwlist eth0 scan".

-Raghu.


On 12/7/07, Dan Williams <dcbw at redhat.com> wrote:
>
> On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S wrote:
> > Hi,
> >
> >    Does any one know small AP scan code which gives similar/same
> > output as that of "iwlist eth0 scan". I dont want to use iwlist
> > because of its size.
>
> Look at the driver_wext.c code from wpa_supplicant at
> wpa_driver_wext_scan() and wpa_driver_wext_get_scan_results().  You
> don't need to screenscrape output if you can just use the values
> directly.
>
> Dan
>
>
>
>


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071207/f1802a83/attachment.htm 


From dcbw  Fri Dec  7 03:53:34 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 06:53:34 -0500
Subject: Small code which gives output similar to "iwlist eth0 scan"
In-Reply-To: <58a444250712070350o194dff0eg71a6f835fde9e10d@mail.gmail.com>
References: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
	<1197026483.4655.1.camel@localhost.localdomain>
	<58a444250712070350o194dff0eg71a6f835fde9e10d@mail.gmail.com>
Message-ID: <1197028414.4655.24.camel@localhost.localdomain>

On Fri, 2007-12-07 at 17:20 +0530, Raghavendra. S wrote:
> Hi Dan,
>  
>  Actually in my case I want to get scan result first then configure
> wpa_supplicant.conf and then I will enable wpa_supplicant. Because
> user has to first see the scanned result and after that he can
> configure to which AP he want to associate with and security models he
> want to use. So I need some independent small AP scan code similar to
> "iwlist eth0 scan".

Again, look at driver_wext.c.  Code to scan and get results is there.
You can print out whatever you want given the information it returns.
You can create a tool that incorporates that code, prints out what the
user wants from scan result information passed back by the driver, and
then spawn wpa_supplicant however you like.

Dan

> -Raghu.
> 
>  
> On 12/7/07, Dan Williams <dcbw at redhat.com> wrote: 
>         On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S wrote:
>         > Hi,
>         >
>         >    Does any one know small AP scan code which gives
>         similar/same 
>         > output as that of "iwlist eth0 scan". I dont want to use
>         iwlist
>         > because of its size.
>         
>         Look at the driver_wext.c code from wpa_supplicant at
>         wpa_driver_wext_scan() and
>         wpa_driver_wext_get_scan_results().  You 
>         don't need to screenscrape output if you can just use the
>         values
>         directly.
>         
>         Dan
>         
>         
>         
> 
> 
> 
> -- 
> Regards & Thanks
> Raghavendra. S 




From j  Fri Dec  7 06:55:50 2007
From: j (Jouni Malinen)
Date: Fri, 7 Dec 2007 06:55:50 -0800
Subject: getting RSN: not in suitable state for new pre-authentication
In-Reply-To: <0JSO00IGW4WF4W@ms13.samsung.com>
References: <0JSO00IGW4WF4W@ms13.samsung.com>
Message-ID: <20071207145550.GY5698@jm.kir.nu>

On Fri, Dec 07, 2007 at 07:31:27AM +0000, RAGHAVENDRA SADARAMACHANDRA wrote:
> <HTML><HEAD>..

Please use plaintext (not HTML) format in the messages..

> <p>&nbsp;I am trying to test WPA2-PSK, AES. Its getting connected and I am able 
> to ping. But I would like to know why I am getting</p>
> <p><b>RSN: not in suitable state for new pre-authentication</b>, message.</p>

RSN pre-authentication is only used with WPA2-EAP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Fri Dec  7 07:01:31 2007
From: j (Jouni Malinen)
Date: Fri, 7 Dec 2007 07:01:31 -0800
Subject: WPA supplicant not working for LEAP
In-Reply-To: <00c401c8389e$a52b5d90$d705f40a@persistent.co.in>
References: <00c401c8389e$a52b5d90$d705f40a@persistent.co.in>
Message-ID: <20071207150131.GZ5698@jm.kir.nu>

On Fri, Dec 07, 2007 at 12:28:47PM +0530, Anjali Shirvoikar wrote:

> AP ? DLink DWL2100
> Radius server ? Free radius server
> 
> The AP is configured for TKIP with WPA-EAP. The radius server is set for
> LEAP. The association with AP takes place successfully (seen in the AP log),
> a packet trace at the radius server shows that the LEAP conversation takes
> place(4 packets are exchanged) and ends in a success EAP packet being sent
> to the wpa_supplicant. The wpa_supplicant then seems to be sending a 8 octet
> challenge to the AP which is not forwarded by the AP to the RS (not seen in
> the packet trace) Could anybody tell me how to fix this issue? Is LEAP to be
> used only with Cisco AP?

LEAP is not compliant with EAP RFC and in addition, the mechanism used
for delivering keying material from the RADIUS server to the
AP/Authenticator is different from the one used for all other EAP
methods. I would expect most APs not to support this.

As far as fixing the issue is concerned, I would say the proper fix is
not to use LEAP. It's proprietary and not really very secure. If you
really need to use LEAP, it would probably be easiest to just get a
Cisco AP.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dave  Fri Dec  7 10:47:38 2007
From: dave (Dave Hansen)
Date: Fri, 07 Dec 2007 10:47:38 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
Message-ID: <1197053258.6207.46.camel@localhost>

I have a particularly nasty set of access points at work.  I think it's
all intentional, but it causes pains for wpasupplicant.  The APs
advertise an unencrypted "COMPANYVISITOR" network, but are also capable
of WPA when you associate with the "COMPANY" SSID.  Also, I do not think
they start to advertise WPA/RSN IE in their beacon frame until after you
explicitly set the SSID.  The only reason I know this is that
wpasupplicant wouldn't try to associate with them using my wpa-enabled
config entry even when I tried to force it.

ap_scan=2 works just fine for these.  But, I'd also like to use the
same .conf file at home and I'd prefer not to fiddle with it whenever I
move back and forth.  ap_scan=2 sadly won't search for multiple SSIDs:
it simply uses the first one.

I've hacked a little "scan_ssid=2" option into my version of
wpasupplicant, but I've now realized that I hacked it in pretty badly.

Would adding something like 'advertised_ssid="VISITOR"' option be useful
functionality to anyone else?  It would separate the SSID for which we
scan from the one with which we actually try to associate.  

Any ideas on how to solve this nicely?  Could we have ap_scan=2 timeout
after it fails to authenticate?  Or, have a select set of SSIDs that get
ap_scan=2 behavior while not extending it to all SSIDs?

-- Dave




From dcbw  Fri Dec  7 11:12:36 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 14:12:36 -0500
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197053258.6207.46.camel@localhost>
References: <1197053258.6207.46.camel@localhost>
Message-ID: <1197054756.4465.4.camel@localhost.localdomain>

On Fri, 2007-12-07 at 10:47 -0800, Dave Hansen wrote:
> I have a particularly nasty set of access points at work.  I think it's
> all intentional, but it causes pains for wpasupplicant.  The APs
> advertise an unencrypted "COMPANYVISITOR" network, but are also capable
> of WPA when you associate with the "COMPANY" SSID.  Also, I do not think
> they start to advertise WPA/RSN IE in their beacon frame until after you
> explicitly set the SSID.  The only reason I know this is that
> wpasupplicant wouldn't try to associate with them using my wpa-enabled
> config entry even when I tried to force it.
> 
> ap_scan=2 works just fine for these.  But, I'd also like to use the
> same .conf file at home and I'd prefer not to fiddle with it whenever I
> move back and forth.  ap_scan=2 sadly won't search for multiple SSIDs:
> it simply uses the first one.

This just won't work then.  ap_scan=2 is required for use with hidden
networks, and you can't switch between ap_scan=1 and ap_scan=2 on the
fly unless you're talking to the supplicant with wpa_cli or the D-Bus
control interface.  You probably want something like NetworkManager or
some other automatic tool that handles these things transparently.

> I've hacked a little "scan_ssid=2" option into my version of
> wpasupplicant, but I've now realized that I hacked it in pretty badly.
> 
> Would adding something like 'advertised_ssid="VISITOR"' option be useful
> functionality to anyone else?  It would separate the SSID for which we
> scan from the one with which we actually try to associate.  

Not really, since that's a completely different network in reality.
That also confuses the purpose of network blocks unnecessarily.

> Any ideas on how to solve this nicely?  Could we have ap_scan=2 timeout
> after it fails to authenticate?  Or, have a select set of SSIDs that get
> ap_scan=2 behavior while not extending it to all SSIDs?

Yeah, the problem is that the ap_scan stuff just isn't granular enough
when you're using the config file format, or when you're letting
wpa_supplicant alone handle the roaming.

What you _really_ want is ap_scan=1 + scan_ssid=1 in your network block.
Try that.  If your driver supports specific SSID scanning, it'll
probably work for you.  If your driver doesn't then you probably need to
get a better network card or find a good driver :)  Any driver based on
mac80211, or the ipw2200, or the hostap driver will work with
scan_ssid=1.  Most others, probably not.

Dan





From dave  Fri Dec  7 11:31:20 2007
From: dave (Dave Hansen)
Date: Fri, 07 Dec 2007 11:31:20 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197054756.4465.4.camel@localhost.localdomain>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
Message-ID: <1197055880.6207.55.camel@localhost>

On Fri, 2007-12-07 at 14:12 -0500, Dan Williams wrote:
> What you _really_ want is ap_scan=1 + scan_ssid=1 in your network block.
> Try that.  If your driver supports specific SSID scanning, it'll
> probably work for you.  If your driver doesn't then you probably need to
> get a better network card or find a good driver :)  Any driver based on
> mac80211, or the ipw2200, or the hostap driver will work with
> scan_ssid=1.  Most others, probably not. 

I actually have an ipw2200.  

The problem is that I don't think the scan_ssid=1 logic comes into play
until it finds an explicitly hidden ssid.  In my case, I think
wpasupplicant looks around and sees the ~10 "VISITOR" access points,
notes that it doesn't have any config entries for them, then promptly
ignores them. :(

It partly doesn't find matches because the aps somehow don't advertise
WPA when you're associated to the "VISITOR" ssid.  It hits this message,
btw:
        if (proto_match == 0)
                wpa_printf(MSG_DEBUG, "   skip - no WPA/RSN proto match");

I actually went in and hacked wpa_supplicant_ssid_bss_match()  to trick
wpasupplicant into trying to associate with the aps to get around this.

-- Dave




From dcbw  Fri Dec  7 15:57:15 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 18:57:15 -0500
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197055880.6207.55.camel@localhost>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
Message-ID: <1197071835.4563.0.camel@localhost.localdomain>

On Fri, 2007-12-07 at 11:31 -0800, Dave Hansen wrote:
> On Fri, 2007-12-07 at 14:12 -0500, Dan Williams wrote:
> > What you _really_ want is ap_scan=1 + scan_ssid=1 in your network block.
> > Try that.  If your driver supports specific SSID scanning, it'll
> > probably work for you.  If your driver doesn't then you probably need to
> > get a better network card or find a good driver :)  Any driver based on
> > mac80211, or the ipw2200, or the hostap driver will work with
> > scan_ssid=1.  Most others, probably not. 
> 
> I actually have an ipw2200.  
> 
> The problem is that I don't think the scan_ssid=1 logic comes into play
> until it finds an explicitly hidden ssid.  In my case, I think
> wpasupplicant looks around and sees the ~10 "VISITOR" access points,
> notes that it doesn't have any config entries for them, then promptly
> ignores them. :(

You've tried scan_ssid=1 + ap_scan=1 already I take it?

Dan

> It partly doesn't find matches because the aps somehow don't advertise
> WPA when you're associated to the "VISITOR" ssid.  It hits this message,
> btw:
>         if (proto_match == 0)
>                 wpa_printf(MSG_DEBUG, "   skip - no WPA/RSN proto match");
> 
> I actually went in and hacked wpa_supplicant_ssid_bss_match()  to trick
> wpasupplicant into trying to associate with the aps to get around this.
> 
> -- Dave
> 




From dave  Fri Dec  7 16:09:17 2007
From: dave (Dave Hansen)
Date: Fri, 07 Dec 2007 16:09:17 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197071835.4563.0.camel@localhost.localdomain>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
	<1197071835.4563.0.camel@localhost.localdomain>
Message-ID: <1197072557.6207.106.camel@localhost>

On Fri, 2007-12-07 at 18:57 -0500, Dan Williams wrote:
> > The problem is that I don't think the scan_ssid=1 logic comes into
> play
> > until it finds an explicitly hidden ssid.  In my case, I think
> > wpasupplicant looks around and sees the ~10 "VISITOR" access points,
> > notes that it doesn't have any config entries for them, then
> promptly
> > ignores them. :(
> 
> You've tried scan_ssid=1 + ap_scan=1 already I take it?

Yeah, wpasupplicant doesn't try to associate because it sees that the
scan_ssid=1 network is a WPA network, yet the APs don't advertise WPA.

-- Dave




From dcbw  Fri Dec  7 16:24:27 2007
From: dcbw (Dan Williams)
Date: Fri, 07 Dec 2007 19:24:27 -0500
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197072557.6207.106.camel@localhost>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
	<1197071835.4563.0.camel@localhost.localdomain>
	<1197072557.6207.106.camel@localhost>
Message-ID: <1197073467.4563.17.camel@localhost.localdomain>

On Fri, 2007-12-07 at 16:09 -0800, Dave Hansen wrote:
> On Fri, 2007-12-07 at 18:57 -0500, Dan Williams wrote:
> > > The problem is that I don't think the scan_ssid=1 logic comes into
> > play
> > > until it finds an explicitly hidden ssid.  In my case, I think
> > > wpasupplicant looks around and sees the ~10 "VISITOR" access points,
> > > notes that it doesn't have any config entries for them, then
> > promptly
> > > ignores them. :(
> > 
> > You've tried scan_ssid=1 + ap_scan=1 already I take it?
> 
> Yeah, wpasupplicant doesn't try to associate because it sees that the
> scan_ssid=1 network is a WPA network, yet the APs don't advertise WPA.

That's odd, because it should be sending out a probe request anyway,
getting the probe response with the IE back, and updating it's scan
table.  At least, that's the way it's reasonable to expect that it would
work.  I wouldn't expect it to ignore the scan_ssid=1 just because the
network block doesn't match, because then what's the point of the
scan_ssid=1 anyway...

I assume you're not specifying the BSSID in the network block?

dan





From j  Fri Dec  7 17:26:34 2007
From: j (Jouni Malinen)
Date: Fri, 7 Dec 2007 17:26:34 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197072557.6207.106.camel@localhost>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
	<1197071835.4563.0.camel@localhost.localdomain>
	<1197072557.6207.106.camel@localhost>
Message-ID: <20071208012634.GA5698@jm.kir.nu>

On Fri, Dec 07, 2007 at 04:09:17PM -0800, Dave Hansen wrote:

> Yeah, wpasupplicant doesn't try to associate because it sees that the
> scan_ssid=1 network is a WPA network, yet the APs don't advertise WPA.

They must advertise WPA at some point if you manage to connect with
ap_scan=2.. wpa_supplicant will try to scan for the specific SSID if
scan_ssid=1 is used in ap_scan=1 mode. If the driver supports this and
works correctly, it would include that WPA network in the scan results
and wpa_supplicant would then try to connect to it.

Is the hidden network visible in scan results when scan_ssid=1 is used?
wpa_supplicant will alternate the scans between broadcast SSID and the
SSID. I would be interested in seeing whether the scan results for the
specific SSID show the WPA/RSN IE correctly or not.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Fri Dec  7 21:04:07 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Sat, 8 Dec 2007 14:04:07 +0900
Subject: Few more question on wpa supplicant
In-Reply-To: <1197021370.2603.13.camel@localhost.localdomain>
References: <58a444250712062039q73d5af4fqdb2a295df148f7aa@mail.gmail.com>
	<1197021370.2603.13.camel@localhost.localdomain>
Message-ID: <58a444250712072104p525f0709m3680599a236cda5@mail.gmail.com>

Hi Dan,

 For my question about,
wpa supplicant's support for Adhoc network creation with the given channel
and Adhoc connection? , you have mentioned that wpa sipplicant
0.6.xversions has support for it.

As I am using wpa supplicant 0.5.7 ported for marvell 8686, it becomes
difficult for me to go for 0.6.x. I would like to know me changing wpa
supplicant 0.5.7 to support adhoc network creation and adhoc connection,
whether its going to take long time. whether its going to be a very big
change?

If you can tell me which all files/functions I have to refer in wpa
supplicant 0.6.0 or 0.6.1 for adhoc. then I think I will be able modify
0.5.7 to support adhoc connection. Will you please help me in this.

-Raghu.


On 12/7/07, Dan Williams <dcbw at redhat.com> wrote:
>
> On Fri, 2007-12-07 at 10:09 +0530, Raghavendra. S wrote:
> > Hi All,
> >
> > Does wpa_supplicant support
> >  -  Adhoc connection?
>
> Yes, but only fully in 0.6.x.  0.5.x doesn't have the ability to tell
> the card which frequency to communicate on, which is needed for some
> drivers to successfully complete the adhoc setup.
>
> >  -  Adhoc security?
>
> Yes, for WPA-PSK and WEP.
>
> >  - Adhoc network creation with the given channel?
>
> With 0.6.x, yes.  With 0.5.x and lower, no.
>
> >  - AP connection without encryption and authentication?
>
> Do you mean having your client connect to an "open" access point?  If
> so, then yes.
>
> >  - AP connection with WEP?
>
> Do you mean having the client connect to a WEP AP?  If so, then yes.
>
> Dan
>
>
>


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071208/88ebedeb/attachment.htm 


From raghavendra.akkasali  Fri Dec  7 21:09:33 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Sat, 8 Dec 2007 14:09:33 +0900
Subject: Small code which gives output similar to "iwlist eth0 scan"
In-Reply-To: <1197028414.4655.24.camel@localhost.localdomain>
References: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
	<1197026483.4655.1.camel@localhost.localdomain>
	<58a444250712070350o194dff0eg71a6f835fde9e10d@mail.gmail.com>
	<1197028414.4655.24.camel@localhost.localdomain>
Message-ID: <58a444250712072109h391c6136h411cbc714ef4a3f3@mail.gmail.com>

Hi,

 One more doubt about disassociation. In my code I will enable wpa
supplicant using
system("./wpa_supplicant -ieth0 -Dmarvell -c./wpa_supplicant.conf -B");
So it will be a daemon. Now to disassociate I need socket fd using which
wpa_supplicant is communicating, How to get that. If I store the opened
socket fd in some  temp file then can I use same sock fd to disassociate and
then kill wpa_supplicant using kill command or is there any better approach
for the same.

-Raghu.



On 12/7/07, Dan Williams <dcbw at redhat.com> wrote:
>
> On Fri, 2007-12-07 at 17:20 +0530, Raghavendra. S wrote:
> > Hi Dan,
> >
> >  Actually in my case I want to get scan result first then configure
> > wpa_supplicant.conf and then I will enable wpa_supplicant. Because
> > user has to first see the scanned result and after that he can
> > configure to which AP he want to associate with and security models he
> > want to use. So I need some independent small AP scan code similar to
> > "iwlist eth0 scan".
>
> Again, look at driver_wext.c.  Code to scan and get results is there.
> You can print out whatever you want given the information it returns.
> You can create a tool that incorporates that code, prints out what the
> user wants from scan result information passed back by the driver, and
> then spawn wpa_supplicant however you like.
>
> Dan
>
> > -Raghu.
> >
> >
> > On 12/7/07, Dan Williams <dcbw at redhat.com> wrote:
> >         On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S wrote:
> >         > Hi,
> >         >
> >         >    Does any one know small AP scan code which gives
> >         similar/same
> >         > output as that of "iwlist eth0 scan". I dont want to use
> >         iwlist
> >         > because of its size.
> >
> >         Look at the driver_wext.c code from wpa_supplicant at
> >         wpa_driver_wext_scan() and
> >         wpa_driver_wext_get_scan_results().  You
> >         don't need to screenscrape output if you can just use the
> >         values
> >         directly.
> >
> >         Dan
> >
> >
> >
> >
> >
> >
> > --
> > Regards & Thanks
> > Raghavendra. S
>
>


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071208/1feae5ee/attachment.htm 


From silentkeystroke  Sat Dec  8 09:36:34 2007
From: silentkeystroke (Peter Savage)
Date: Sat, 8 Dec 2007 17:36:34 +0000
Subject: Multiple clients on ath0 authentication failure
Message-ID: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>

Hi,
I've just setup a DLink card with an atheros chipset as an AP, using hostapd
and madwifi.  I'm using the stock pacakges available in ubuntu gutsy.
However, this appears to only allow one client to connect, what am I
missing?  When the second client connects, it just gets an authentication
failure message.

-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071208/9106bcf4/attachment.htm 


From j  Sat Dec  8 09:48:44 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 09:48:44 -0800
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>
	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>
Message-ID: <20071208174844.GB5698@jm.kir.nu>

On Wed, Oct 17, 2007 at 08:53:00AM +0200, Stjepan Gros wrote:

> This is a good question. I was planning to raise similar question also,
> but due to the lack of time wasn't able to do so. So, I'll do that now.

Sorry about this taking a while, but I finally had chance to take a
closer look at this thread..

> We use supplicant part as a library in IKEv2 protocol implementation.
> More specifically, version 0.4.7. Makefiles that produce dynamic
> libraries can be found in the contrib/ subdirectory of the ikev2
> (ikev2.sourceforge.net) source as well as README file that details how
> to build libraries.

To be more exact, you are using EAP peer functionality, not the IEEE
802.1X/EAPOL supplicant, from wpa_supplicant.

> The exact content of the Makefiles was trial and error process. But
> eventually, it worked. The main problem are some auxiliary functions,
> e.g. logging, that are mixed with other functions and so are not easily
> replaceable with ikev2's equivalents. This is necessary in order to
> better integrate the supplicant code into ikev2 implementation.

Even though there are still quite many areas that can be improved, this
should be much better in the current wpa_supplicant 0.6.x code base. The
logging functions that you may want to replace are in their own file
(src/utils/wpa_debug.c) and you can link in other files without having
to replace some of the common helper functions.

In addition, I just added a simple example program that shows how to
interact with the EAP peer and EAP server code. The Makefile for this
program shows how to build a library with EAP functionality and the
example program is linked against that library. I would expect this to
be quite close to the needs of your IKEv2 implementation.

The example code is available from my Git repository at http://w1.fi/ in
a new top level directory, eap_example. This makes it easier for me to
find areas in the interface between EAP and EAPOL (or other protocol
using EAP) and I would expect that some of the interfaces will change
during 0.6.x development to clear these, so please do not expect the
interfaces to be fixed at this point.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec  8 10:04:18 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 10:04:18 -0800
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
Message-ID: <20071208180418.GC5698@jm.kir.nu>

On Sat, Dec 08, 2007 at 05:36:34PM +0000, Peter Savage wrote:

> I've just setup a DLink card with an atheros chipset as an AP, using hostapd
> and madwifi.  I'm using the stock pacakges available in ubuntu gutsy.
> However, this appears to only allow one client to connect, what am I
> missing?  When the second client connects, it just gets an authentication
> failure message.

Please send debug log from hostapd (-dd on command line) showing both
the successful connection and the failed one.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec  8 10:57:13 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 10:57:13 -0800
Subject: how to compile the HOSTAPD into a liberary?
In-Reply-To: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>
Message-ID: <20071208185713.GD5698@jm.kir.nu>

On Wed, Oct 17, 2007 at 10:40:45AM +0800, Joren Joanna wrote:

> Now I am developing a software using with RADIUS protocol, then found
> that your work HOSTAPD is a great software, so I wanna use the
> radius_client part in hostapd for my software as the Radius Client.

Sorry for the later reply, but here's some information on this topic.

> These days, I have done many tests of this idea. So, my question is:
> 1. Is the idea correct?

Yes, that can be done. The current 0.6.x code base has cleaned up number
of internal interfaces to make it easier to use separate modules in
other programs.

> 2. If correct, Which files should be included in the liberary makefile?
> 3. How to use the liberary? Especially for the workflow.

I added a simple example program that shows how to build the RADIUS
client functionality into a library and how to interact with the library
to send and receive RADIUS messages. This is now available from my Git
tree at http://w1.fi/ (in the radius_example top-level directory).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec  8 19:33:08 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 19:33:08 -0800
Subject: [0.6.x PATCH] Fix segfault when D-Bus interface is compiled in
	but not enabled at runtime
In-Reply-To: <1196977707.23463.18.camel@localhost.localdomain>
References: <1196977707.23463.18.camel@localhost.localdomain>
Message-ID: <20071209033308.GH5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 04:48:27PM -0500, Dan Williams wrote:

> --- wpa_supplicant-0.5.7/wpa_supplicant.c.global-iface-segfault-fix	2007-10-09 17:34:25.000000000 -0400
> @@ -2352,7 +2352,8 @@ static void wpa_supplicant_deinit_iface(
> -	wpas_dbus_unregister_iface(wpa_s);
> +	if (wpa_s->global)
> +		wpas_dbus_unregister_iface(wpa_s);

This does not look necessary anymore as far as I can tell. I fixed this
segfault in ctrl_iface_dbus.c in February:
http://w1.fi/cgi-bin/viewcvs.cgi/hostap/wpa_supplicant/ctrl_iface_dbus.c?r1=1.17&r2=1.18

This fix was included in 0.5.8 and 0.6.0.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec  8 20:25:39 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 20:25:39 -0800
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
In-Reply-To: <1196977390.23463.13.camel@localhost.localdomain>
References: <1196977390.23463.13.camel@localhost.localdomain>
Message-ID: <20071209042539.GI5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 04:43:10PM -0500, Dan Williams wrote:
> Add a .config option for enabling the output logging, and add a
> command-line option for turning this on or off (output is logged to
> stdout by default still).  Also set the buffering mode to line-buffered
> on *NIX platforms so that output shows up in a reasonable timeframe.
> Otherwise it gets buffered in 4096 byte chunks (or whatever the C
> library uses for buffer sizes) and doesn't get written in a useful
> amount of time.

Thanks! Applied with some minor cleanup and added documentation to both
0.6.x and 0.5.x. Please note that I usually use git-cherry-pick to get
changes from 0.6.x to 0.5.x so separate patches for 0.5.x are not
necessary unless there is a large number of conflicts that are not
trivial to resolve.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec  8 20:34:32 2007
From: j (Jouni Malinen)
Date: Sat, 8 Dec 2007 20:34:32 -0800
Subject: [0.6.x PATCH] SIGUSR1 changes debug level
In-Reply-To: <1196977517.23463.16.camel@localhost.localdomain>
References: <1196977517.23463.16.camel@localhost.localdomain>
Message-ID: <20071209043432.GJ5698@jm.kir.nu>

On Thu, Dec 06, 2007 at 04:45:17PM -0500, Dan Williams wrote:

> So you don't have to respawn wpa_supplicant with different debug
> options, or fire up a control interface or something.  Many *NIX
> programs have this functionality; bring it to wpa_supplicant too.

The functionality itself sounds fine, but use of SIGUSR1 in
wpa_supplicant.c is not portable and that file needs to build for all
targets. Furthermore, hostapd is already using SIGUSR1 for something
else (state dump into a file) which would make this somewhat conflicting
use of signals between hostapd and wpa_supplicant.

> --- a/wpa_supplicant/wpa_supplicant.c

> @@ -1918,6 +1934,8 @@ int wpa_supplicant_run(struct wpa_global *global)
>  	eloop_register_signal_terminate(wpa_supplicant_terminate, NULL);
>  	eloop_register_signal_reconfig(wpa_supplicant_reconfig, NULL);
>  
> +	eloop_register_signal(SIGUSR1, wpa_supplicant_handle_sigusr1, NULL);

I added those eloop_register_signal_{terminate,reconfig}() functions to
hide the signal (etc.) details into platform specific code (eloop*.c).
Something similar would be needed for SIGUSR1. Though, I would rather
not change eloop interface for 0.5.x, so this may end up only in 0.6.x
branch.

Another option would be to use ctrl_iface to change the debug level.
That would have the extra benefit of being able to take in the exact
debug level instead of just switching to another level. This sounds more
useful to me since the caller would know what the end result is
regardless of the current state. With just SIGUSR1 available, the caller
would not really be able to tell whether the next signal will enable or
disable debugging (or just change the level of already enabled
debugging).

-- 
Jouni Malinen                                            PGP id EFC895FA



From kel  Sun Dec  9 04:26:29 2007
From: kel (Kel Modderman)
Date: Sun, 9 Dec 2007 22:26:29 +1000
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
In-Reply-To: <20071209042539.GI5698@jm.kir.nu>
References: <1196977390.23463.13.camel@localhost.localdomain>
	<20071209042539.GI5698@jm.kir.nu>
Message-ID: <200712092226.29462.kel@otaku42.de>

On Sunday 09 December 2007 14:25:39 Jouni Malinen wrote:
> On Thu, Dec 06, 2007 at 04:43:10PM -0500, Dan Williams wrote:
> > Add a .config option for enabling the output logging, and add a
> > command-line option for turning this on or off (output is logged to
> > stdout by default still).  Also set the buffering mode to line-buffered
> > on *NIX platforms so that output shows up in a reasonable timeframe.
> > Otherwise it gets buffered in 4096 byte chunks (or whatever the C
> > library uses for buffer sizes) and doesn't get written in a useful
> > amount of time.
>
> Thanks! Applied with some minor cleanup and added documentation to both
> 0.6.x and 0.5.x. Please note that I usually use git-cherry-pick to get
> changes from 0.6.x to 0.5.x so separate patches for 0.5.x are not
> necessary unless there is a large number of conflicts that are not
> trivial to resolve.

Is there an opportunity to control the target file location for this output?

Thanks, Kel.



From j  Sun Dec  9 07:58:17 2007
From: j (Jouni Malinen)
Date: Sun, 9 Dec 2007 07:58:17 -0800
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
In-Reply-To: <200712092226.29462.kel@otaku42.de>
References: <1196977390.23463.13.camel@localhost.localdomain>
	<20071209042539.GI5698@jm.kir.nu>
	<200712092226.29462.kel@otaku42.de>
Message-ID: <20071209155817.GK5698@jm.kir.nu>

On Sun, Dec 09, 2007 at 10:26:29PM +1000, Kel Modderman wrote:

> Is there an opportunity to control the target file location for this output?

Not in this version. The file name (or well, template with %d in it) is
hardcoded in wpa_debug_open_file(). I would assume it would be
relatively simple change to pass in similar template as an argument to
that function, though.

-- 
Jouni Malinen                                            PGP id EFC895FA



From aland  Sun Dec  9 09:01:24 2007
From: aland (Alan DeKok)
Date: Sun, 09 Dec 2007 18:01:24 +0100
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <20071208174844.GB5698@jm.kir.nu>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>
	<20071208174844.GB5698@jm.kir.nu>
Message-ID: <475C1F64.5000400@deployingradius.com>

Jouni Malinen wrote:
> In addition, I just added a simple example program that shows how to
> interact with the EAP peer and EAP server code. The Makefile for this
> program shows how to build a library with EAP functionality and the
> example program is linked against that library.

  With minor Makefile hacks to create "libeap.so" rather than
"libeap.a".  Yes, that does appear to work.

...
++[pap] returns noop
  rad_check_password:  Found Auth-Type eap2
auth: type "eap2"
+- entering group authenticate
  rlm_eap: Request found, released from the list
EAP-TLV: TLV Result - Success - requested Success
==> Success
++[eap2] returns ok
Sending Access-Accept of id 10 to 127.0.0.1 port 32852
...

 :)

> The example code is available from my Git repository at http://w1.fi/ in
> a new top level directory, eap_example. This makes it easier for me to
> find areas in the interface between EAP and EAPOL (or other protocol
> using EAP) and I would expect that some of the interfaces will change
> during 0.6.x development to clear these, so please do not expect the
> interfaces to be fixed at this point.

  Hmm...

  Alan DeKok.



From dcbw  Sun Dec  9 09:22:32 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 12:22:32 -0500
Subject: Small code which gives output similar to "iwlist eth0 scan"
In-Reply-To: <58a444250712072109h391c6136h411cbc714ef4a3f3@mail.gmail.com>
References: <58a444250712070315g2ced08c9ybd802aa0304a0c38@mail.gmail.com>
	<1197026483.4655.1.camel@localhost.localdomain>
	<58a444250712070350o194dff0eg71a6f835fde9e10d@mail.gmail.com>
	<1197028414.4655.24.camel@localhost.localdomain>
	<58a444250712072109h391c6136h411cbc714ef4a3f3@mail.gmail.com>
Message-ID: <1197220952.9149.17.camel@localhost.localdomain>

On Sat, 2007-12-08 at 14:09 +0900, Raghavendra. S wrote:
> Hi,
>  
>  One more doubt about disassociation. In my code I will enable wpa
> supplicant using 
> system("./wpa_supplicant -ieth0 -Dmarvell -c./wpa_supplicant.conf
> -B");
> So it will be a daemon. Now to disassociate I need socket fd using
> which wpa_supplicant is communicating, How to get that. If I store the
> opened socket fd in some  temp file then can I use same sock fd to
> disassociate and then kill wpa_supplicant using kill command or is
> there any better approach for the same.

Use the "ctrl_interface" parameter in the config file to tell
wpa_supplicant where to put it's global control socket.

dan


> -Raghu.
> 
> 
>  
> On 12/7/07, Dan Williams <dcbw at redhat.com> wrote: 
>         On Fri, 2007-12-07 at 17:20 +0530, Raghavendra. S wrote:
>         > Hi Dan,
>         >
>         >  Actually in my case I want to get scan result first then
>         configure 
>         > wpa_supplicant.conf and then I will enable wpa_supplicant.
>         Because
>         > user has to first see the scanned result and after that he
>         can
>         > configure to which AP he want to associate with and security
>         models he 
>         > want to use. So I need some independent small AP scan code
>         similar to
>         > "iwlist eth0 scan".
>         
>         Again, look at driver_wext.c.  Code to scan and get results is
>         there.
>         You can print out whatever you want given the information it
>         returns. 
>         You can create a tool that incorporates that code, prints out
>         what the
>         user wants from scan result information passed back by the
>         driver, and
>         then spawn wpa_supplicant however you like.
>         
>         Dan
>         
>         > -Raghu. 
>         >
>         >
>         > On 12/7/07, Dan Williams <dcbw at redhat.com> wrote:
>         >         On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S
>         wrote:
>         >         > Hi,
>         >         > 
>         >         >    Does any one know small AP scan code which
>         gives
>         >         similar/same
>         >         > output as that of "iwlist eth0 scan". I dont want
>         to use
>         >         iwlist
>         >         > because of its size. 
>         >
>         >         Look at the driver_wext.c code from wpa_supplicant
>         at
>         >         wpa_driver_wext_scan() and
>         >         wpa_driver_wext_get_scan_results().  You
>         >         don't need to screenscrape output if you can just
>         use the 
>         >         values
>         >         directly.
>         >
>         >         Dan
>         >
>         >
>         >
>         >
>         >
>         >
>         > --
>         > Regards & Thanks
>         > Raghavendra. S
>         
> 
> 
> 
> -- 
> Regards & Thanks
> Raghavendra. S 




From dcbw  Sun Dec  9 09:23:41 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 12:23:41 -0500
Subject: [0.6.x PATCH] Fix segfault when D-Bus interface is compiled in
	but not enabled at runtime
In-Reply-To: <20071209033308.GH5698@jm.kir.nu>
References: <1196977707.23463.18.camel@localhost.localdomain>
	<20071209033308.GH5698@jm.kir.nu>
Message-ID: <1197221021.9149.20.camel@localhost.localdomain>

On Sat, 2007-12-08 at 19:33 -0800, Jouni Malinen wrote:
> On Thu, Dec 06, 2007 at 04:48:27PM -0500, Dan Williams wrote:
> 
> > --- wpa_supplicant-0.5.7/wpa_supplicant.c.global-iface-segfault-fix	2007-10-09 17:34:25.000000000 -0400
> > @@ -2352,7 +2352,8 @@ static void wpa_supplicant_deinit_iface(
> > -	wpas_dbus_unregister_iface(wpa_s);
> > +	if (wpa_s->global)
> > +		wpas_dbus_unregister_iface(wpa_s);
> 
> This does not look necessary anymore as far as I can tell. I fixed this
> segfault in ctrl_iface_dbus.c in February:
> http://w1.fi/cgi-bin/viewcvs.cgi/hostap/wpa_supplicant/ctrl_iface_dbus.c?r1=1.17&r2=1.18
> 
> This fix was included in 0.5.8 and 0.6.0.


Ah, ok.  The patch applied to git just fine, but yours is better.
Thanks.

Dan





From dcbw  Sun Dec  9 09:24:46 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 12:24:46 -0500
Subject: Few more question on wpa supplicant
In-Reply-To: <58a444250712072104p525f0709m3680599a236cda5@mail.gmail.com>
References: <58a444250712062039q73d5af4fqdb2a295df148f7aa@mail.gmail.com>
	<1197021370.2603.13.camel@localhost.localdomain>
	<58a444250712072104p525f0709m3680599a236cda5@mail.gmail.com>
Message-ID: <1197221086.9149.23.camel@localhost.localdomain>

On Sat, 2007-12-08 at 14:04 +0900, Raghavendra. S wrote:
> Hi Dan,
>  
>  For my question about,
> wpa supplicant's support for Adhoc network creation with the given
> channel and Adhoc connection? , you have mentioned that wpa sipplicant
> 0.6.x versions has support for it.
>  
> As I am using wpa supplicant 0.5.7 ported for marvell 8686, it becomes
> difficult for me to go for 0.6.x. I would like to know me changing wpa
> supplicant 0.5.7 to support adhoc network creation and adhoc
> connection, whether its going to take long time. whether its going to
> be a very big change?

Probably not a huge change.  I have to backport that functionality
anyway, so I'll post the patch against 0.5.x when I'm done.  What you're
looking for (if you want to do it) is the frequency config parameter in
the network block of the config.

Dan

> If you can tell me which all files/functions I have to refer in wpa
> supplicant 0.6.0 or 0.6.1 for adhoc. then I think I will be able
> modify 0.5.7 to support adhoc connection. Will you please help me in
> this.
>  
> -Raghu.
> 
>  
> On 12/7/07, Dan Williams <dcbw at redhat.com> wrote: 
>         On Fri, 2007-12-07 at 10:09 +0530, Raghavendra. S wrote:
>         > Hi All,
>         >
>         > Does wpa_supplicant support 
>         >  -  Adhoc connection?
>         
>         Yes, but only fully in 0.6.x.  0.5.x doesn't have the ability
>         to tell
>         the card which frequency to communicate on, which is needed
>         for some
>         drivers to successfully complete the adhoc setup. 
>         
>         >  -  Adhoc security?
>         
>         Yes, for WPA-PSK and WEP.
>         
>         >  - Adhoc network creation with the given channel?
>         
>         With 0.6.x, yes.  With 0.5.x and lower, no.
>         
>         >  - AP connection without encryption and authentication? 
>         
>         Do you mean having your client connect to an "open" access
>         point?  If
>         so, then yes.
>         
>         >  - AP connection with WEP?
>         
>         Do you mean having the client connect to a WEP AP?  If so,
>         then yes.
>         
>         Dan
>         
>         
> 
> 
> 
> -- 
> Regards & Thanks
> Raghavendra. S 




From dcbw  Sun Dec  9 09:27:20 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 12:27:20 -0500
Subject: [0.6.x PATCH] SIGUSR1 changes debug level
In-Reply-To: <20071209043432.GJ5698@jm.kir.nu>
References: <1196977517.23463.16.camel@localhost.localdomain>
	<20071209043432.GJ5698@jm.kir.nu>
Message-ID: <1197221240.9149.26.camel@localhost.localdomain>

On Sat, 2007-12-08 at 20:34 -0800, Jouni Malinen wrote:
> On Thu, Dec 06, 2007 at 04:45:17PM -0500, Dan Williams wrote:
> 
> > So you don't have to respawn wpa_supplicant with different debug
> > options, or fire up a control interface or something.  Many *NIX
> > programs have this functionality; bring it to wpa_supplicant too.
> 
> The functionality itself sounds fine, but use of SIGUSR1 in
> wpa_supplicant.c is not portable and that file needs to build for all
> targets. Furthermore, hostapd is already using SIGUSR1 for something
> else (state dump into a file) which would make this somewhat conflicting
> use of signals between hostapd and wpa_supplicant.
> 
> > --- a/wpa_supplicant/wpa_supplicant.c
> 
> > @@ -1918,6 +1934,8 @@ int wpa_supplicant_run(struct wpa_global *global)
> >  	eloop_register_signal_terminate(wpa_supplicant_terminate, NULL);
> >  	eloop_register_signal_reconfig(wpa_supplicant_reconfig, NULL);
> >  
> > +	eloop_register_signal(SIGUSR1, wpa_supplicant_handle_sigusr1, NULL);
> 
> I added those eloop_register_signal_{terminate,reconfig}() functions to
> hide the signal (etc.) details into platform specific code (eloop*.c).
> Something similar would be needed for SIGUSR1. Though, I would rather
> not change eloop interface for 0.5.x, so this may end up only in 0.6.x
> branch.
> 
> Another option would be to use ctrl_iface to change the debug level.
> That would have the extra benefit of being able to take in the exact
> debug level instead of just switching to another level. This sounds more
> useful to me since the caller would know what the end result is
> regardless of the current state. With just SIGUSR1 available, the caller
> would not really be able to tell whether the next signal will enable or
> disable debugging (or just change the level of already enabled
> debugging).

Perhaps that's a better option.  The D-Bus control interface could just
have a method call and you can use dbus-send, and the socket control
interface I assume would have to grow the command and wpa_cli would have
to know about it too.  Feel free to drop this patch then.

Dan





From j  Sun Dec  9 09:42:07 2007
From: j (Jouni Malinen)
Date: Sun, 9 Dec 2007 09:42:07 -0800
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <475C1F64.5000400@deployingradius.com>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>
	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>
	<20071208174844.GB5698@jm.kir.nu>
	<475C1F64.5000400@deployingradius.com>
Message-ID: <20071209174207.GL5698@jm.kir.nu>

On Sun, Dec 09, 2007 at 06:01:24PM +0100, Alan DeKok wrote:

>   With minor Makefile hacks to create "libeap.so" rather than
> "libeap.a".  Yes, that does appear to work.

>   rad_check_password:  Found Auth-Type eap2
> auth: type "eap2"
> EAP-TLV: TLV Result - Success - requested Success
> ==> Success

>  :)

That looks quite interesting combination ;-). Nice to hear it worked.

> > The example code is available from my Git repository at http://w1.fi/ in
> > a new top level directory, eap_example. This makes it easier for me to
> > find areas in the interface between EAP and EAPOL (or other protocol
> > using EAP) and I would expect that some of the interfaces will change
> > during 0.6.x development to clear these, so please do not expect the
> > interfaces to be fixed at this point.
> 
>   Hmm...

While implementing the eap_example code, some areas started looking
worse than I had hoped for and I think I will end up cleaning the
interface a bit to make it less complex and to require less code in
whatever is using the EAP state machine. Though, this is more on the EAP
peer side, so that part may not touch the particular example you showed
above. I already did some cleanup on the server side some time ago when
updating hostapd EAPOL/EAP state machine interfaces.

In addition, I have a longstanding to-do item on implementing a generic
buffer data structure for dynamic memory buffers. If I end up finishing
this finally, that would change the EAP interfaces from passing in
pointer to u8* and length to using a pointer to struct wpabuf which
would have accessor functions for getting pointers/length for the
included data.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Sun Dec  9 09:56:49 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 12:56:49 -0500
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
In-Reply-To: <20071209155817.GK5698@jm.kir.nu>
References: <1196977390.23463.13.camel@localhost.localdomain>
	<20071209042539.GI5698@jm.kir.nu> <200712092226.29462.kel@otaku42.de>
	<20071209155817.GK5698@jm.kir.nu>
Message-ID: <1197223009.9149.55.camel@localhost.localdomain>

On Sun, 2007-12-09 at 07:58 -0800, Jouni Malinen wrote:
> On Sun, Dec 09, 2007 at 10:26:29PM +1000, Kel Modderman wrote:
> 
> > Is there an opportunity to control the target file location for this output?
> 
> Not in this version. The file name (or well, template with %d in it) is
> hardcoded in wpa_debug_open_file(). I would assume it would be
> relatively simple change to pass in similar template as an argument to
> that function, though.

Yes, I was looking into that at first, but hadn't gotten there quite
yet.  It would be awesome if somebody came up with a patch first :)  I
assume that it would be as simple as adding another to struct wpa_params
for the path to the logfile, as a char [PATH_MAX] or something like
that.  Not sure what needs to be done on the windows side, though if the
field is NULL then it could simply default to the current Windows
logfile location when wpa_debug_use_file is true.

Shouldn't be too hard.

Dan





From dcbw  Sun Dec  9 10:06:09 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 13:06:09 -0500
Subject: [PATCH] fix memory leak in D-Bus control interface
Message-ID: <1197223569.9149.63.camel@localhost.localdomain>

Applies to both 0.6.x and 0.5.x.  The D-Bus message wasn't getting
unreffed correctly when sending out some signals.

Dan



-------------- next part --------------
A non-text attachment was scrubbed...
Name: dbus-control-iface-signal-leak-fix.patch
Type: text/x-patch
Size: 605 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071209/b90a076e/attachment.bin 


From dcbw  Sun Dec  9 10:20:34 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 13:20:34 -0500
Subject: [PATCH] fix memory leak in D-Bus control interface
In-Reply-To: <1197223569.9149.63.camel@localhost.localdomain>
References: <1197223569.9149.63.camel@localhost.localdomain>
Message-ID: <1197224434.9149.66.camel@localhost.localdomain>

On Sun, 2007-12-09 at 13:06 -0500, Dan Williams wrote:
> Applies to both 0.6.x and 0.5.x.  The D-Bus message wasn't getting
> unreffed correctly when sending out some signals.

FYI, when you cherry-pick back to 0.5.x, you'll need to
s/_signal/signal/g.

Dan





From dcbw  Sun Dec  9 10:25:51 2007
From: dcbw (Dan Williams)
Date: Sun, 09 Dec 2007 13:25:51 -0500
Subject: [0.6.x PATCH] Make output logging to file usable on *NIX platforms
In-Reply-To: <20071209155817.GK5698@jm.kir.nu>
References: <1196977390.23463.13.camel@localhost.localdomain>
	<20071209042539.GI5698@jm.kir.nu> <200712092226.29462.kel@otaku42.de>
	<20071209155817.GK5698@jm.kir.nu>
Message-ID: <1197224751.9149.68.camel@localhost.localdomain>

On Sun, 2007-12-09 at 07:58 -0800, Jouni Malinen wrote:
> On Sun, Dec 09, 2007 at 10:26:29PM +1000, Kel Modderman wrote:
> 
> > Is there an opportunity to control the target file location for this output?
> 
> Not in this version. The file name (or well, template with %d in it) is
> hardcoded in wpa_debug_open_file(). I would assume it would be
> relatively simple change to pass in similar template as an argument to
> that function, though.

Proposed patch attached; compile-tested only.

Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: specific-debug-file.patch
Type: text/x-patch
Size: 4406 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071209/e01b1f04/attachment.bin 


From aland  Sun Dec  9 10:31:36 2007
From: aland (Alan DeKok)
Date: Sun, 09 Dec 2007 19:31:36 +0100
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <20071209174207.GL5698@jm.kir.nu>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>	<20071208174844.GB5698@jm.kir.nu>	<475C1F64.5000400@deployingradius.com>
	<20071209174207.GL5698@jm.kir.nu>
Message-ID: <475C3488.7030600@deployingradius.com>

Jouni Malinen wrote:
> That looks quite interesting combination ;-). Nice to hear it worked.

  "works".  It will take a little more code before it works for people
other than myself.

  But it's ~1k LoC, most of which is cut & pasted from other modules, or
from the eap_example code.  A small additional amount of code will make
it production-ready.

> While implementing the eap_example code, some areas started looking
> worse than I had hoped for and I think I will end up cleaning the
> interface a bit to make it less complex and to require less code in
> whatever is using the EAP state machine. Though, this is more on the EAP
> peer side, so that part may not touch the particular example you showed
> above. I already did some cleanup on the server side some time ago when
> updating hostapd EAPOL/EAP state machine interfaces.

  The interface right now looks pretty good.  Some comments:

 - exposing TTLS TLV data to the server would be useful
 - allowing the server to add TTLS TLV data would be useful
 - having method checks for PAP/CHAP/MS-CHAP in phase 2
   like is done for the EAP methods would be useful
 - ability to completely control phase2 method would be good
   i.e. run one EAP library for phase1, and another for phase2
   it's weird, but it can catch corner cases and assumptions

> In addition, I have a longstanding to-do item on implementing a generic
> buffer data structure for dynamic memory buffers. If I end up finishing
> this finally, that would change the EAP interfaces from passing in
> pointer to u8* and length to using a pointer to struct wpabuf which
> would have accessor functions for getting pointers/length for the
> included data.

  Sounds good.

  Alan DeKok.



From archana.gopal  Sun Dec  9 17:06:38 2007
From: archana.gopal (Archana Rajagopal)
Date: Sun, 9 Dec 2007 20:06:38 -0500
Subject: HostAP - ToS
Message-ID: <5dd628b40712091706w5a174a5eveca2db569c3fac56@mail.gmail.com>

Hi,
    I am having a problem with HostAP.When I send packets directly to it, it
identifies the ToS value properly(the ToS is extracted properly).But when I
send a packet to be forwarded to another client, the ToS value is altered
.But it does forward it to the correct client.I am not sure if this is
related to HostAP.Also not sure if the HostAP set up is proper.
Only wifi0 is created and no wlan0.But there is a file name wlan0 in
/proc/net/../hostap/.
Not sure if its correct to use HostAP on wifi0.
Any ideas?
-- 
Regards
Archana Rajagopal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071209/4bda3002/attachment.htm 


From j  Sun Dec  9 18:27:43 2007
From: j (Jouni Malinen)
Date: Sun, 9 Dec 2007 18:27:43 -0800
Subject: HostAP - ToS
In-Reply-To: <5dd628b40712091706w5a174a5eveca2db569c3fac56@mail.gmail.com>
References: <5dd628b40712091706w5a174a5eveca2db569c3fac56@mail.gmail.com>
Message-ID: <20071210022743.GM5698@jm.kir.nu>

On Sun, Dec 09, 2007 at 08:06:38PM -0500, Archana Rajagopal wrote:

>     I am having a problem with HostAP.When I send packets directly to it, it
> identifies the ToS value properly(the ToS is extracted properly).But when I
> send a packet to be forwarded to another client, the ToS value is altered
> .But it does forward it to the correct client.I am not sure if this is
> related to HostAP.

If you are referring to the ToS field in the IP header, then no, Host AP
does not have anything to do with it. That is higher layer networking
functionality; Host AP driver only handles the MAC layer processing and
it doesn't even care whether the frame itself is an IP packet or not.

> Only wifi0 is created and no wlan0.But there is a file name wlan0 in
> /proc/net/../hostap/.
> Not sure if its correct to use HostAP on wifi0.

That sounds odd.. The driver creates two interfaces which are, by
default, called wifi0 and wlan0. wifi0 is only used internally and all
higher layer (e.g., bridging or IP routing) network configuration should
be done using wlan0.

-- 
Jouni Malinen                                            PGP id EFC895FA



From bryan  Sun Dec  9 18:58:18 2007
From: bryan (Bryan Kadzban)
Date: Sun, 09 Dec 2007 21:58:18 -0500
Subject: HostAP - ToS
In-Reply-To: <20071210022743.GM5698@jm.kir.nu>
References: <5dd628b40712091706w5a174a5eveca2db569c3fac56@mail.gmail.com>
	<20071210022743.GM5698@jm.kir.nu>
Message-ID: <475CAB4A.6040906@kadzban.is-a-geek.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Jouni Malinen wrote:
> On Sun, Dec 09, 2007 at 08:06:38PM -0500, Archana Rajagopal wrote:
> 
>> Only wifi0 is created and no wlan0.But there is a file name wlan0
>> in /proc/net/../hostap/. Not sure if its correct to use HostAP on
>> wifi0.
> 
> That sounds odd.. The driver creates two interfaces which are, by 
> default, called wifi0 and wlan0. wifi0 is only used internally...

The distro probably renamed wlan0 because its udev rules are (or were)
old.  For a while, the udev persistent-net support renamed everything to
ethX, whether the initial interface's name was ethX or not.  I think
this has been fixed for a while, but it's possible that either the old
name stuck, or the version of udev in use still has rules that had this
issue.

Archana: If you do have an interface whose MAC matches the MAC of the
wifi0 interface, then try editing your distro's generated persistent-net
udev rule file (I'm not sure which file it is, but it'll have comments
in it about "write_net_rules") to name that interface wlan0 instead of
whatever it is now.  Or, wherever you read "wlan0", think whatever your
distro renamed your higher-level interface to; either way should work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHXKtIS5vET1Wea5wRA6UIAKDCPceMDU95bedlB5u6r3KSu2frAgCg3LeN
m8Uj59Zo1G/7a8WLLBh/bI4=
=yd/M
-----END PGP SIGNATURE-----



From kel  Mon Dec 10 03:26:49 2007
From: kel (Kel Modderman)
Date: Mon, 10 Dec 2007 21:26:49 +1000
Subject: [PATCH] Allow logging to specific file with -F option.
In-Reply-To: <1197223009.9149.55.camel@localhost.localdomain>
References: <1196977390.23463.13.camel@localhost.localdomain>
	<20071209155817.GK5698@jm.kir.nu>
	<1197223009.9149.55.camel@localhost.localdomain>
Message-ID: <200712102126.50116.kel@otaku42.de>

On Monday 10 December 2007 03:56:49 Dan Williams wrote:
> On Sun, 2007-12-09 at 07:58 -0800, Jouni Malinen wrote:
> > On Sun, Dec 09, 2007 at 10:26:29PM +1000, Kel Modderman wrote:
> > > Is there an opportunity to control the target file location for this
> > > output?
> >
> > Not in this version. The file name (or well, template with %d in it) is
> > hardcoded in wpa_debug_open_file(). I would assume it would be
> > relatively simple change to pass in similar template as an argument to
> > that function, though.
>
> Yes, I was looking into that at first, but hadn't gotten there quite
> yet.  It would be awesome if somebody came up with a patch first :)  I
> assume that it would be as simple as adding another to struct wpa_params
> for the path to the logfile, as a char [PATH_MAX] or something like
> that.  Not sure what needs to be done on the windows side, though if the
> field is NULL then it could simply default to the current Windows
> logfile location when wpa_debug_use_file is true.
>
> Shouldn't be too hard.

It looks like you beat me to having the first patch but I'll attach my take on
it anyway.

Attached patch builds upon the enhancement previously discussed
in this thread, by allowing specification of specific filename to write debug
output to. Below is the long description of the patch:

Logging to file was recently added, but the file path and name template
is hardcoded in wpa_debug_open_file(). This change adds an extra -F
command line option which allows specification of a specific output
filename to write debug output to.

wpa_debug_open_file() also prints an error message when the output file
failed to be opened for writing, and wpa_debug_close_file() does not
attempt to fclose the output file if it failed to be opened.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
diff --git a/src/utils/wpa_debug.c b/src/utils/wpa_debug.c
index b2f8c8b..7d3fff8 100644
--- a/src/utils/wpa_debug.c
+++ b/src/utils/wpa_debug.c
@@ -227,36 +227,42 @@ void wpa_hexdump_ascii_key(int level, const char *title, const u8 *buf,
 }
 
 
-int wpa_debug_open_file(void)
+int wpa_debug_open_file(const char *file)
 {
 #ifdef CONFIG_DEBUG_FILE
 	static int count = 0;
 	char fname[64];
 	if (!wpa_debug_use_file)
 		return 0;
+	if (file != NULL && out_file == NULL) {
+		out_file = fopen(file, "a");
+	} else {
 #ifdef _WIN32
-	os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
-		    count++);
+		os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
+			    count++);
 #else /* _WIN32 */
-	os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
-		    count++);
+		os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
+			    count++);
 #endif /* _WIN32 */
-	out_file = fopen(fname, "w");
+		out_file = fopen(fname, "w");
+	}
+	if (out_file == NULL) {
+		wpa_printf(MSG_ERROR, "wpa_debug_open_file: Failed to open output file, "
+			   "using standard output");
+		return -1;
+	}
 #ifndef _WIN32
-	if (out_file)
-		setvbuf(out_file, NULL, _IOLBF, 0);
+	setvbuf(out_file, NULL, _IOLBF, 0);
 #endif /* _WIN32 */
-	return out_file == NULL ? -1 : 0;
-#else /* CONFIG_DEBUG_FILE */
-	return 0;
 #endif /* CONFIG_DEBUG_FILE */
+	return 0;
 }
 
 
 void wpa_debug_close_file(void)
 {
 #ifdef CONFIG_DEBUG_FILE
-	if (!wpa_debug_use_file)
+	if (!wpa_debug_use_file || out_file == NULL)
 		return;
 	fclose(out_file);
 	out_file = NULL;
diff --git a/src/utils/wpa_debug.h b/src/utils/wpa_debug.h
index 311a9b5..1f4c0e1 100644
--- a/src/utils/wpa_debug.h
+++ b/src/utils/wpa_debug.h
@@ -33,7 +33,7 @@ enum { MSG_MSGDUMP, MSG_DEBUG, MSG_INFO, MSG_WARNING, MSG_ERROR };
 
 #else /* CONFIG_NO_STDOUT_DEBUG */
 
-int wpa_debug_open_file(void);
+int wpa_debug_open_file(const char *file);
 void wpa_debug_close_file(void);
 
 /**
diff --git a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
index 296e660..1c7234a 100644
--- a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
+++ b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
@@ -17,6 +17,7 @@
       <arg>-c<replaceable>config file</replaceable></arg>
       <arg>-D<replaceable>driver</replaceable></arg>
       <arg>-P<replaceable>PID_file</replaceable></arg>
+      <arg>-F<replaceable>output file</replaceable></arg>
     </cmdsynopsis>
   </refsynopsisdiv>
   <refsect1>
@@ -383,6 +384,13 @@
       </varlistentry>
 
       <varlistentry>
+	<term>-F output file</term>
+	<listitem>
+	  <para>Log output to specified file.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
 	<term>-g global ctrl_interface</term>
 	<listitem>
 	  <para>Path to global ctrl_interface socket.</para>
diff --git a/wpa_supplicant/main.c b/wpa_supplicant/main.c
index e5af13d..dc89a8d 100644
--- a/wpa_supplicant/main.c
+++ b/wpa_supplicant/main.c
@@ -40,7 +40,12 @@ static void usage(void)
 	printf("%s\n\n%s\n"
 	       "usage:\n"
 	       "  wpa_supplicant [-BddfhKLqqtuvwW] [-P<pid file>] "
-	       "[-g<global ctrl>] \\\n"
+	       "[-g<global ctrl>]"
+#ifdef CONFIG_DEBUG_FILE
+	       " [-F<output file>] \\\n"
+#else /* CONFIG_DEBUG_FILE */
+	       " \\\n"
+#endif /* CONFIG_DEBUG_FILE */
 	       "        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] "
 	       "[-p<driver_param>] \\\n"
 	       "        [-b<br_ifname> [-N -i<ifname> -c<conf> [-C<ctrl>] "
@@ -67,6 +72,7 @@ static void usage(void)
 	       "  -D = driver name\n"
 #ifdef CONFIG_DEBUG_FILE
 	       "  -f = Log output to default log location (normally /tmp)\n"
+	       "  -F = Log output to specified file\n"
 #endif /* CONFIG_DEBUG_FILE */
 	       "  -g = global ctrl_interface\n"
 	       "  -K = include keys (passwords, etc.) in debug output\n"
@@ -146,7 +152,7 @@ int main(int argc, char *argv[])
 	wpa_supplicant_fd_workaround();
 
 	for (;;) {
-		c = getopt(argc, argv, "b:Bc:C:D:dfg:hi:KLNp:P:qtuvwW");
+		c = getopt(argc, argv, "b:Bc:C:D:dF:fg:hi:KLNp:P:qtuvwW");
 		if (c < 0)
 			break;
 		switch (c) {
@@ -179,6 +185,10 @@ int main(int argc, char *argv[])
 		case 'f':
 			params.wpa_debug_use_file = 1;
 			break;
+		case 'F':
+			params.wpa_debug_use_file = 1;
+			params.wpa_debug_file = optarg;
+			break;
 #endif /* CONFIG_DEBUG_FILE */
 		case 'g':
 			params.ctrl_interface = optarg;
diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
index e81202c..85fea7a 100644
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -1828,7 +1828,7 @@ struct wpa_global * wpa_supplicant_init(struct wpa_params *params)
 		return NULL;
 
 	wpa_debug_use_file = params->wpa_debug_use_file;
-	wpa_debug_open_file();
+	wpa_debug_open_file(params->wpa_debug_file);
 
 	ret = eap_peer_register_methods();
 	if (ret) {
diff --git a/wpa_supplicant/wpa_supplicant_i.h b/wpa_supplicant/wpa_supplicant_i.h
index 00e3162..f741244 100644
--- a/wpa_supplicant/wpa_supplicant_i.h
+++ b/wpa_supplicant/wpa_supplicant_i.h
@@ -154,6 +154,11 @@ struct wpa_params {
 	 * wpa_debug_use_file - Write debug to a file (instead of stdout)
 	 */
 	int wpa_debug_use_file;
+
+	/**
+	 * wpa_debug_file - Write debug to specified file.
+	 */
+	char *wpa_debug_file;
 };
 
 /**
-- 
1.5.3.7



From kel  Mon Dec 10 03:30:53 2007
From: kel (Kel Modderman)
Date: Mon, 10 Dec 2007 21:30:53 +1000
Subject: [PATCH] "interfaces" mispelt in comment of
	wpa_supplicant/wpa_supplicant.c
Message-ID: <200712102130.53208.kel@otaku42.de>

Fix the spelling of "interfaces" (was "interdaces") in comment within
wpa_supplicant/wpa_supplicant.c.
---
diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
index 85fea7a..bcae686 100644
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -1762,7 +1762,7 @@ struct wpa_supplicant * wpa_supplicant_add_iface(struct wpa_global *global,
  *
  * This function can be used to dynamically remove network interfaces from
  * %wpa_supplicant, e.g., when a hotplug network adapter is ejected. In
- * addition, this function is used to remove all remaining interdaces when
+ * addition, this function is used to remove all remaining interfaces when
  * %wpa_supplicant is terminated.
  */
 int wpa_supplicant_remove_iface(struct wpa_global *global,
-- 
1.5.3.7



From paresh.sawant  Mon Dec 10 06:22:44 2007
From: paresh.sawant (Paresh Sawant)
Date: Mon, 10 Dec 2007 19:52:44 +0530
Subject: media disconnect event
Message-ID: <683e2de40712100622x2cb2a408p60f5373c0771cd6@mail.gmail.com>

Hi,
          I'm running wpa_supplicant on Wind-XP with CONFIG_USE_NDISUIO
defined. Ihave complied code in VS 2005. I see that
"MSNdis_StatusMediaDisconnect" type of event is NOT notified to
wpa_supplicant by WMI. I notice that "MSNdis_StatusMediaConnect" is notified
by WMI and the event handler is invoked appropriately. But it fails for
media_disconnect type. So in case of AP dissociates for some reason how can
the wpa_supplicant know the state of the station is
un-authenticated(state-1)?

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


From raghavendra.akkasali  Mon Dec 10 07:20:50 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 11 Dec 2007 00:20:50 +0900
Subject: does wpa supplicant support power save mode?
Message-ID: <58a444250712100720p498c1e69re958232f1e475ddd@mail.gmail.com>

-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071211/d9bc3b3a/attachment.htm 


From dave  Mon Dec 10 09:02:55 2007
From: dave (Dave Hansen)
Date: Mon, 10 Dec 2007 09:02:55 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197073467.4563.17.camel@localhost.localdomain>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
	<1197071835.4563.0.camel@localhost.localdomain>
	<1197072557.6207.106.camel@localhost>
	<1197073467.4563.17.camel@localhost.localdomain>
Message-ID: <1197306175.6207.119.camel@localhost>

On Fri, 2007-12-07 at 19:24 -0500, Dan Williams wrote:
> On Fri, 2007-12-07 at 16:09 -0800, Dave Hansen wrote:
> > On Fri, 2007-12-07 at 18:57 -0500, Dan Williams wrote:
> > > > The problem is that I don't think the scan_ssid=1 logic comes into
> > > play
> > > > until it finds an explicitly hidden ssid.  In my case, I think
> > > > wpasupplicant looks around and sees the ~10 "VISITOR" access points,
> > > > notes that it doesn't have any config entries for them, then
> > > promptly
> > > > ignores them. :(
> > > 
> > > You've tried scan_ssid=1 + ap_scan=1 already I take it?
> > 
> > Yeah, wpasupplicant doesn't try to associate because it sees that the
> > scan_ssid=1 network is a WPA network, yet the APs don't advertise WPA.
> 
> That's odd, because it should be sending out a probe request anyway,
> getting the probe response with the IE back, and updating it's scan
> table.  At least, that's the way it's reasonable to expect that it would
> work.  I wouldn't expect it to ignore the scan_ssid=1 just because the
> network block doesn't match, because then what's the point of the
> scan_ssid=1 anyway...
> 
> I assume you're not specifying the BSSID in the network block?

Nope, not specifying anything that I don't explicitly have to.  Just for
fun, I'll try specifying the BSSID and also ensuring that I'm not
blabbering on about a version that I hacked up.  I'll check with a clean
version the next time I go into the office.

-- Dave




From dcbw  Mon Dec 10 09:14:48 2007
From: dcbw (Dan Williams)
Date: Mon, 10 Dec 2007 12:14:48 -0500
Subject: does wpa supplicant support power save mode?
In-Reply-To: <58a444250712100720p498c1e69re958232f1e475ddd@mail.gmail.com>
References: <58a444250712100720p498c1e69re958232f1e475ddd@mail.gmail.com>
Message-ID: <1197306888.18585.5.camel@localhost.localdomain>

Depends on what you mean by this.  When you're running wpa_supplicant
and associated, the firmware/driver must take care of power save mode
since that's inherently a driver/firmware thing.

When the card is _not_ associated, I don't think wpa_supplicant does
anything for powersaving mode, because you as the developer probably
know more about what to do with the card, like shutting the radio off
when you don't need it, or setting the interface down when you're not
using it.

So your question doesn't really apply.  Because power save mode is
controlled through other  means and wpa_supplicant doesn't need to get
involved.

That said, wpa_supplicant could grow some options like "scan_interval"
and "ps_mode" or something that would control how often wpa_supplicant
would scan while disconnected, and it could, depending on ps_mode or
something set the interface down between scans when disconnected or set
specific powersave modes on the device, based on what driver is used.

Dan





From raghavendra.akkasali  Mon Dec 10 17:14:32 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 11 Dec 2007 06:44:32 +0530
Subject: Disassociation...
Message-ID: <58a444250712101714i6d831691q5e5e30d303ee11ee@mail.gmail.com>

Hi Jouni,



-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071211/af35cf2a/attachment.htm 


From raghavendra.akkasali  Mon Dec 10 17:21:01 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 11 Dec 2007 06:51:01 +0530
Subject: Disassociation support...
Message-ID: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>

Hi Jouni Malinen,

    In below mailing list link you have mentioned that wpa supplicant
snapshot version has provided command to disassociate.

    http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html

   I downloaded snapshot 0.6.0. But could not find command for
disassociation. Will you plz tell me where can I get wpa supplicant code
that supports disassociation command.

here is ./wpa_supplicant -h, output on screen.

[/mnt/hgfs/security/wpa_supplicant-0.6-2007-05-26/wpa_supplicant]#
./wpa_supplicant -h
wpa_supplicant v0.6.0
Copyright (c) 2003-2007, Jouni Malinen <j at w1.fi> and contributors

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

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

This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)

usage:
  wpa_supplicant [-BddhKLqqtuvwW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>]
[-p<driver_param>] \
        [-b<br_ifname> [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
  wext = Linux wireless extensions (generic)
  hostap = Host AP driver (Intersil Prism2/2.5/3)
  atmel = ATMEL AT76C5XXx (USB, PCMCIA)
  wired = wpa_supplicant wired Ethernet driver
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  -c = Configuration file
  -C = ctrl_interface parameter (only used if -c is not)
  -i = interface name
  -d = increase debugging verbosity (-dd even more)
  -D = driver name
  -g = global ctrl_interface
  -K = include keys (passwords, etc.) in debug output
  -t = include timestamp in debug messages
  -h = show this help text
  -L = show license (GPL and BSD)
  -p = driver parameters
  -P = PID file
  -q = decrease debugging verbosity (-qq even less)
  -v = show version
  -w = wait for interface to be added, if needed
  -W = wait for a control interface monitor before starting
  -N = start describing new interface
example:
  wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf


-- 
Regards & Thanks
Raghavendra. S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071211/592814b7/attachment.htm 


From j  Mon Dec 10 18:07:50 2007
From: j (Jouni Malinen)
Date: Mon, 10 Dec 2007 18:07:50 -0800
Subject: Disassociation support...
In-Reply-To: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
References: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
Message-ID: <20071211020750.GP5698@jm.kir.nu>

On Tue, Dec 11, 2007 at 06:51:01AM +0530, Raghavendra. S wrote:

>     In below mailing list link you have mentioned that wpa supplicant
> snapshot version has provided command to disassociate.
> 
>     http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html

That message has nothing to do with wpa_supplicant (it was about the
Host AP driver).

>    I downloaded snapshot 0.6.0. But could not find command for
> disassociation. Will you plz tell me where can I get wpa supplicant code
> that supports disassociation command.

What exactly do you mean with "disassociation command"? Would 'wpa_cli
disconnect' meet your needs?

-- 
Jouni Malinen                                            PGP id EFC895FA



From aland  Tue Dec 11 00:07:49 2007
From: aland (Alan DeKok)
Date: Tue, 11 Dec 2007 09:07:49 +0100
Subject: FreeRADIUS CVS head supports PEAPv1 and EAP-FAST
Message-ID: <475E4555.8020703@deployingradius.com>

  I have just committed a new module: rlm_eap2.  It uses the hostap
libraries to implement EAP.  This means that FreeRADIUS now has two
independent EAP modules, and can support a wider range of EAP types.

  There are some limitations:

  * The rlm_eap2 module is experimental, and requires some Makefile
changes on both hostap && rlm_eap2 to build.

  * The inner tunneled sessions for PEAP and TTLS are *not* run through
a virtual server, as with rlm_eap.  This can be fixed before 2.0.

  * The inner tunneled sessions CANNOT be proxied (see above for why)

  * the eap types in use CANNOT be controlled by the server.  This can
be fixed before 2.0.


  The goal is to enable a wider range of EAP types to be used in FreeRADIUS.

  I will try to put together some upstream patches for hostap which will
make it easier for EAP servers to selectively control which types they
choose to implement.

  Alan DeKok.



From aland  Tue Dec 11 05:43:15 2007
From: aland (Alan DeKok)
Date: Tue, 11 Dec 2007 14:43:15 +0100
Subject: Patch to build libeap.so
Message-ID: <475E93F3.4080006@deployingradius.com>

  It adds a CONFIG_SOLIB parameter.  If set, it will build libeap.so
rather than libeap.a.

  The commands to compile the PIC code && link it into a .so are also
defined in the Makefile.  They will need to be updated for any new platform.

  I have successfully used this to create a libeap.so, and run
FreeRADIUS with it using the previously mentioned EAP module.

  For FreeRADIUS testing, see:

  src/modules/rlm_eap2/
  raddb/experimental.conf   (also has notes on building, etc.)

  Alan DeKok.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libeap.diff
Type: text/x-patch
Size: 843 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071211/bca09857/attachment.bin 


From raghavendra.akkasali  Tue Dec 11 16:33:06 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Wed, 12 Dec 2007 06:03:06 +0530
Subject: Disassociation support...
In-Reply-To: <20071211020750.GP5698@jm.kir.nu>
References: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
	<20071211020750.GP5698@jm.kir.nu>
Message-ID: <58a444250712111633h5d28abc4l4f6621fc8702aa54@mail.gmail.com>

Hi,
    My requirement is something like this...let me explain with small
piece of code.

int main()
{
     printf("1- scan\n
                2 - enable esecurity\n
                3 - disable security\n
                4 - edit config\n");

    //after taking input from user - say 'choice'

  switch(choice)
{

case SCAN:
                 // here i want to scan using wpa supplicant. and get result.
                break;

case EDIT_CONFIG:
                // user will enter inputs after seeing scan result and
then i will configure wpa_supplicant.conf as per users requirement.
                break;

case ENABLE_SECURITY:
             // here i will enable supplicant. as below
            system("./wpa_supplicant -c ./wpa_supplicant.conf");
//assume I will enable successfully with required command line
parameter.
            //if successfully enabled i will work here...say getting
ip...ping etc..
             break;

case DISABLE_SECURITY:
            //here i should disable to do that...
            // I have to disassociate first.
            // then i will kill wpa supplicant.
    break;

}

return 0;
}

My code will look as above. I would like to understand following things here.

 1. for scanning - I will modify wpa supplicant code to take command
line argument say  '-s' which indicates enable wpa supplicant only to
scan. so I will enable wpa supplicant like this,
system("./wpa_supplicant   -s  -c ./dummy_wpa_supplicant.conf"). I
think using this I will get scan result. Let me know if there's any
better approach. My objective here is to get scan result and i should
fill this scan result in some structure.

2. For disable security. - First I will disassociate. problem here is
how i will get control on socket opened by wpa_supplicant, to
disassociate it? If I able to to that then...my problem is solved.
After this I will simply kill wpa supplicant.

I am not planning to use, wpa_cli.

-Raghu.

On 12/11/07, Jouni Malinen <j at w1.fi> wrote:
> On Tue, Dec 11, 2007 at 06:51:01AM +0530, Raghavendra. S wrote:
>
> >     In below mailing list link you have mentioned that wpa supplicant
> > snapshot version has provided command to disassociate.
> >
> >     http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html
>
> That message has nothing to do with wpa_supplicant (it was about the
> Host AP driver).
>
> >    I downloaded snapshot 0.6.0. But could not find command for
> > disassociation. Will you plz tell me where can I get wpa supplicant code
> > that supports disassociation command.
>
> What exactly do you mean with "disassociation command"? Would 'wpa_cli
> disconnect' meet your needs?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



-- 
Regards & Thanks
Raghavendra. S



From jagadish.nadimpalli  Wed Dec 12 03:18:48 2007
From: jagadish.nadimpalli (Jagadish)
Date: Wed, 12 Dec 2007 16:48:48 +0530
Subject: How to set-up RADIUS server in hostapd
Message-ID: <475FC398.1050600@oneconvergence.com>

Hi,

      I am using hostapd-0.5.9. I want to use hostapd as RADIUS server. 
For this I enabled CONFIG_EAP, CONFIG_EAP_TLS and CONFIG_RADIUS_SERVER 
in .config file. It compiled successfully. But if I run it using 
"hostapd hostapd.conf", it is giving segmentation fault.
In hostapd.conf file, I added interface=wlan0. The coredump is showing 
the following function as responsible for segmentation fault.
===================================================
driver_lookup (name=0x8076f62 "default") at hostapd.c:1561
1561                     return p->ops;
====================================================
Please help me solving this problem.

thanks,
Jagadish



From kohen.d  Wed Dec 12 05:51:27 2007
From: kohen.d (Dudy Kohen)
Date: Wed, 12 Dec 2007 15:51:27 +0200
Subject: Ndiswrapper and virtual interfaces - WPA_supplicant can't associate
In-Reply-To: <e3a7b8140712120548k1566d64bl575ae179bcf8e3a@mail.gmail.com>
References: <e3a7b8140712120548k1566d64bl575ae179bcf8e3a@mail.gmail.com>
Message-ID: <e3a7b8140712120551y560d57d7h38f7727b13bb6b6f@mail.gmail.com>

Hi,
I have a TrendNET 421PC and a Prism2 based card.
I use a Linksys WRT54GL 1.0 router with DD-WRT and a virtual interface
using WPA. (another with WEP, but it's for WDS)
Wpa_supplicant claims not to find the appropriate SSID although it
shows it in the debug output.
It works perfectly in Windows XP (no WPA_SUPPLICANT, same machine) and
no change (apart from interface name) is needed to use the prism based
card.
I use FC7 with reconfigured kernel (the 4K issue) with native versions
of all the tools.
Tried the ap_scan option, it didn't work any better.
The problem exists only with the second interface, not the first.

A while ago I had a different router configuration and couldn't
connect to a "hidden" SSID at all.
appreciate your help...
David



From dcbw  Wed Dec 12 06:44:16 2007
From: dcbw (Dan Williams)
Date: Wed, 12 Dec 2007 09:44:16 -0500
Subject: Disassociation support...
In-Reply-To: <58a444250712111633h5d28abc4l4f6621fc8702aa54@mail.gmail.com>
References: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
	<20071211020750.GP5698@jm.kir.nu>
	<58a444250712111633h5d28abc4l4f6621fc8702aa54@mail.gmail.com>
Message-ID: <1197470656.11193.6.camel@localhost.localdomain>

On Wed, 2007-12-12 at 06:03 +0530, Raghavendra. S wrote:
> Hi,
>     My requirement is something like this...let me explain with small
> piece of code.
> 
> int main()
> {
>      printf("1- scan\n
>                 2 - enable esecurity\n
>                 3 - disable security\n
>                 4 - edit config\n");
> 
>     //after taking input from user - say 'choice'
> 
>   switch(choice)
> {
> 
> case SCAN:
>                  // here i want to scan using wpa supplicant. and get result.
>                 break;
> 
> case EDIT_CONFIG:
>                 // user will enter inputs after seeing scan result and
> then i will configure wpa_supplicant.conf as per users requirement.
>                 break;
> 
> case ENABLE_SECURITY:
>              // here i will enable supplicant. as below
>             system("./wpa_supplicant -c ./wpa_supplicant.conf");
> //assume I will enable successfully with required command line
> parameter.
>             //if successfully enabled i will work here...say getting
> ip...ping etc..
>              break;
> 
> case DISABLE_SECURITY:
>             //here i should disable to do that...
>             // I have to disassociate first.
>             // then i will kill wpa supplicant.
>     break;
> 
> }
> 
> return 0;
> }
> 
> My code will look as above. I would like to understand following things here.
> 
>  1. for scanning - I will modify wpa supplicant code to take command
> line argument say  '-s' which indicates enable wpa supplicant only to
> scan. so I will enable wpa supplicant like this,
> system("./wpa_supplicant   -s  -c ./dummy_wpa_supplicant.conf"). I
> think using this I will get scan result. Let me know if there's any
> better approach. My objective here is to get scan result and i should
> fill this scan result in some structure.

Yes, there is.  Take the scanning code in driver_wext.c, and put it into
the same file in which your main.c is.  Do the scanning from _your_
program.  You don't need wpa_supplicant running to scan.

Or, talk to wpa_supplicant over the control socket.

> 2. For disable security. - First I will disassociate. problem here is
> how i will get control on socket opened by wpa_supplicant, to
> disassociate it? If I able to to that then...my problem is solved.
> After this I will simply kill wpa supplicant.

You specify the control interface in the config file you pass to the
supplicant.

Dan

> I am not planning to use, wpa_cli.
> 
> -Raghu.
> 
> On 12/11/07, Jouni Malinen <j at w1.fi> wrote:
> > On Tue, Dec 11, 2007 at 06:51:01AM +0530, Raghavendra. S wrote:
> >
> > >     In below mailing list link you have mentioned that wpa supplicant
> > > snapshot version has provided command to disassociate.
> > >
> > >     http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html
> >
> > That message has nothing to do with wpa_supplicant (it was about the
> > Host AP driver).
> >
> > >    I downloaded snapshot 0.6.0. But could not find command for
> > > disassociation. Will you plz tell me where can I get wpa supplicant code
> > > that supports disassociation command.
> >
> > What exactly do you mean with "disassociation command"? Would 'wpa_cli
> > disconnect' meet your needs?
> >
> > --
> > Jouni Malinen                                            PGP id EFC895FA
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
> 
> 
> 




From raghavendra.akkasali  Wed Dec 12 07:43:02 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Thu, 13 Dec 2007 00:43:02 +0900
Subject: Disassociation support...
In-Reply-To: <1197470656.11193.6.camel@localhost.localdomain>
References: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
	<20071211020750.GP5698@jm.kir.nu>
	<58a444250712111633h5d28abc4l4f6621fc8702aa54@mail.gmail.com>
	<1197470656.11193.6.camel@localhost.localdomain>
Message-ID: <58a444250712120743u5b9bd720g462efea34749a990@mail.gmail.com>

Hi Dan,

 My doubts are inline..

On 12/12/07, Dan Williams <dcbw at redhat.com> wrote:
> On Wed, 2007-12-12 at 06:03 +0530, Raghavendra. S wrote:
> > Hi,
> >     My requirement is something like this...let me explain with small
> > piece of code.
> >
> > int main()
> > {
> >      printf("1- scan\n
> >                 2 - enable esecurity\n
> >                 3 - disable security\n
> >                 4 - edit config\n");
> >
> >     //after taking input from user - say 'choice'
> >
> >   switch(choice)
> > {
> >
> > case SCAN:
> >                  // here i want to scan using wpa supplicant. and get result.
> >                 break;
> >
> > case EDIT_CONFIG:
> >                 // user will enter inputs after seeing scan result and
> > then i will configure wpa_supplicant.conf as per users requirement.
> >                 break;
> >
> > case ENABLE_SECURITY:
> >              // here i will enable supplicant. as below
> >             system("./wpa_supplicant -c ./wpa_supplicant.conf");
> > //assume I will enable successfully with required command line
> > parameter.
> >             //if successfully enabled i will work here...say getting
> > ip...ping etc..
> >              break;
> >
> > case DISABLE_SECURITY:
> >             //here i should disable to do that...
> >             // I have to disassociate first.
> >             // then i will kill wpa supplicant.
> >     break;
> >
> > }
> >
> > return 0;
> > }
> >
> > My code will look as above. I would like to understand following things here.
> >
> >  1. for scanning - I will modify wpa supplicant code to take command
> > line argument say  '-s' which indicates enable wpa supplicant only to
> > scan. so I will enable wpa supplicant like this,
> > system("./wpa_supplicant   -s  -c ./dummy_wpa_supplicant.conf"). I
> > think using this I will get scan result. Let me know if there's any
> > better approach. My objective here is to get scan result and i should
> > fill this scan result in some structure.
>
> Yes, there is.  Take the scanning code in driver_wext.c, and put it into
> the same file in which your main.c is.  Do the scanning from _your_
> program.  You don't need wpa_supplicant running to scan.
>
> Or, talk to wpa_supplicant over the control socket.


[Raghu]: Here I think first I should initialize driver using
             void * wpa_driver_wext_init(void *ctx, const char *ifname)

             Here whether "ctx" stands for some callbackname?  I mean,
whether I have to pass some callback above init function or just
passing NULL will be fine.

              after this i will call scan function
              int wpa_driver_wext_scan(void *priv, const u8 *ssid,
size_t ssid_len)
               where priv is value returned by init call rt?


>
> > 2. For disable security. - First I will disassociate. problem here is
> > how i will get control on socket opened by wpa_supplicant, to
> > disassociate it? If I able to to that then...my problem is solved.
> > After this I will simply kill wpa supplicant.
>
> You specify the control interface in the config file you pass to the
> supplicant.

[Raghu]: Here if I mention say crtl_interface=/var/run/wpa_supplicant
and if I enable wpa supplicant on "eth0", I can see some control
socket in  "/var/run/wpa_supplicant/eth0" right? I observed that
wpa_cli uses socket to talk with these control socket "eth0". Is there
any simpler way to issue "disassociate" command to control socket...I
mean some other IPC mechanism.


> Dan
>
> > I am not planning to use, wpa_cli.
> >
> > -Raghu.
> >
> > On 12/11/07, Jouni Malinen <j at w1.fi> wrote:
> > > On Tue, Dec 11, 2007 at 06:51:01AM +0530, Raghavendra. S wrote:
> > >
> > > >     In below mailing list link you have mentioned that wpa supplicant
> > > > snapshot version has provided command to disassociate.
> > > >
> > > >     http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html
> > >
> > > That message has nothing to do with wpa_supplicant (it was about the
> > > Host AP driver).
> > >
> > > >    I downloaded snapshot 0.6.0. But could not find command for
> > > > disassociation. Will you plz tell me where can I get wpa supplicant code
> > > > that supports disassociation command.
> > >
> > > What exactly do you mean with "disassociation command"? Would 'wpa_cli
> > > disconnect' meet your needs?
> > >
> > > --
> > > Jouni Malinen                                            PGP id EFC895FA
> > > _______________________________________________
> > > HostAP mailing list
> > > HostAP at shmoo.com
> > > http://lists.shmoo.com/mailman/listinfo/hostap
> > >
> >
> >
> >
>
>


-- 
Regards & Thanks
Raghavendra. S



From dcbw  Wed Dec 12 08:47:30 2007
From: dcbw (Dan Williams)
Date: Wed, 12 Dec 2007 11:47:30 -0500
Subject: Disassociation support...
In-Reply-To: <58a444250712120743u5b9bd720g462efea34749a990@mail.gmail.com>
References: <58a444250712101721s7727268clf98502b7511fe0ca@mail.gmail.com>
	<20071211020750.GP5698@jm.kir.nu>
	<58a444250712111633h5d28abc4l4f6621fc8702aa54@mail.gmail.com>
	<1197470656.11193.6.camel@localhost.localdomain>
	<58a444250712120743u5b9bd720g462efea34749a990@mail.gmail.com>
Message-ID: <1197478050.13414.12.camel@localhost.localdomain>

On Thu, 2007-12-13 at 00:43 +0900, Raghavendra. S wrote:
> Hi Dan,
> 
>  My doubts are inline..
> 
> On 12/12/07, Dan Williams <dcbw at redhat.com> wrote:
> > On Wed, 2007-12-12 at 06:03 +0530, Raghavendra. S wrote:
> > > Hi,
> > >     My requirement is something like this...let me explain with small
> > > piece of code.
> > >
> > > int main()
> > > {
> > >      printf("1- scan\n
> > >                 2 - enable esecurity\n
> > >                 3 - disable security\n
> > >                 4 - edit config\n");
> > >
> > >     //after taking input from user - say 'choice'
> > >
> > >   switch(choice)
> > > {
> > >
> > > case SCAN:
> > >                  // here i want to scan using wpa supplicant. and get result.
> > >                 break;
> > >
> > > case EDIT_CONFIG:
> > >                 // user will enter inputs after seeing scan result and
> > > then i will configure wpa_supplicant.conf as per users requirement.
> > >                 break;
> > >
> > > case ENABLE_SECURITY:
> > >              // here i will enable supplicant. as below
> > >             system("./wpa_supplicant -c ./wpa_supplicant.conf");
> > > //assume I will enable successfully with required command line
> > > parameter.
> > >             //if successfully enabled i will work here...say getting
> > > ip...ping etc..
> > >              break;
> > >
> > > case DISABLE_SECURITY:
> > >             //here i should disable to do that...
> > >             // I have to disassociate first.
> > >             // then i will kill wpa supplicant.
> > >     break;
> > >
> > > }
> > >
> > > return 0;
> > > }
> > >
> > > My code will look as above. I would like to understand following things here.
> > >
> > >  1. for scanning - I will modify wpa supplicant code to take command
> > > line argument say  '-s' which indicates enable wpa supplicant only to
> > > scan. so I will enable wpa supplicant like this,
> > > system("./wpa_supplicant   -s  -c ./dummy_wpa_supplicant.conf"). I
> > > think using this I will get scan result. Let me know if there's any
> > > better approach. My objective here is to get scan result and i should
> > > fill this scan result in some structure.
> >
> > Yes, there is.  Take the scanning code in driver_wext.c, and put it into
> > the same file in which your main.c is.  Do the scanning from _your_
> > program.  You don't need wpa_supplicant running to scan.
> >
> > Or, talk to wpa_supplicant over the control socket.
> 
> 
> [Raghu]: Here I think first I should initialize driver using
>              void * wpa_driver_wext_init(void *ctx, const char *ifname)
> 
>              Here whether "ctx" stands for some callbackname?  I mean,
> whether I have to pass some callback above init function or just
> passing NULL will be fine.
> 
>               after this i will call scan function
>               int wpa_driver_wext_scan(void *priv, const u8 *ssid,
> size_t ssid_len)
>                where priv is value returned by init call rt?

You don't need to initialize the driver or anything.  You just need to
be able to do ioctls, which requires root.  So either your program must
be root, or you must have some other tool do this.  Beyond that, the
only two ioctls you care about are SIOCSIWSCAN and SIOCGIWSCAN.  That's
it.  You don't need to init the driver or anything like that, beyond
ensuring that the interface is marked UP.

> >
> > > 2. For disable security. - First I will disassociate. problem here is
> > > how i will get control on socket opened by wpa_supplicant, to
> > > disassociate it? If I able to to that then...my problem is solved.
> > > After this I will simply kill wpa supplicant.
> >
> > You specify the control interface in the config file you pass to the
> > supplicant.
> 
> [Raghu]: Here if I mention say crtl_interface=/var/run/wpa_supplicant
> and if I enable wpa supplicant on "eth0", I can see some control
> socket in  "/var/run/wpa_supplicant/eth0" right? I observed that
> wpa_cli uses socket to talk with these control socket "eth0". Is there
> any simpler way to issue "disassociate" command to control socket...I
> mean some other IPC mechanism.

There are two ways to talk to wpa_supplicant:  the control socket, or
D-Bus.  I doubt you want to use D-Bus here.  So you can:

1) use the control socket like wpa_cli does

2) kill wpa_supplicant with -TERM, which will cause it to disassociate

Seriously, let wpa_supplicant do the work _for_ you, instead of trying
to program around it.  Your life will be easier :)

Dan

> 
> > Dan
> >
> > > I am not planning to use, wpa_cli.
> > >
> > > -Raghu.
> > >
> > > On 12/11/07, Jouni Malinen <j at w1.fi> wrote:
> > > > On Tue, Dec 11, 2007 at 06:51:01AM +0530, Raghavendra. S wrote:
> > > >
> > > > >     In below mailing list link you have mentioned that wpa supplicant
> > > > > snapshot version has provided command to disassociate.
> > > > >
> > > > >     http://lists.shmoo.com/pipermail/hostap/2003-November/004852.html
> > > >
> > > > That message has nothing to do with wpa_supplicant (it was about the
> > > > Host AP driver).
> > > >
> > > > >    I downloaded snapshot 0.6.0. But could not find command for
> > > > > disassociation. Will you plz tell me where can I get wpa supplicant code
> > > > > that supports disassociation command.
> > > >
> > > > What exactly do you mean with "disassociation command"? Would 'wpa_cli
> > > > disconnect' meet your needs?
> > > >
> > > > --
> > > > Jouni Malinen                                            PGP id EFC895FA
> > > > _______________________________________________
> > > > HostAP mailing list
> > > > HostAP at shmoo.com
> > > > http://lists.shmoo.com/mailman/listinfo/hostap
> > > >
> > >
> > >
> > >
> >
> >
> 
> 




From johannes  Wed Dec 12 08:30:24 2007
From: johannes (Johannes Berg)
Date: Wed, 12 Dec 2007 17:30:24 +0100
Subject: [PATCH] hostapd: use wext's privacy_invoked instead of prism ioctl
Message-ID: <1197477024.6558.100.camel@johannes.berg>

This patch changes driver_devicescape to use IW_AUTH_PRIVACY_INVOKED
rather than PRISM2_PARAM_PRIVACY_INVOKED.

Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
---
 hostapd/driver_devicescape.c |   14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

--- hostap.orig/hostapd/driver_devicescape.c	2007-12-12 17:27:56.000000000 +0100
+++ hostap/hostapd/driver_devicescape.c	2007-12-12 17:28:55.000000000 +0100
@@ -926,10 +926,18 @@ static int i802_set_ieee8021x(const char
 static int i802_set_privacy(const char *ifname, void *priv, int enabled)
 {
 	struct i802_driver_data *drv = priv;
+	struct iwreq iwr;
 
-	return hostap_ioctl_prism2param_iface(ifname, drv,
-					      PRISM2_PARAM_PRIVACY_INVOKED,
-					      enabled);
+	memset(&iwr, 0, sizeof(iwr));
+
+	os_strlcpy(iwr.ifr_name, ifname, IFNAMSIZ);
+	iwr.u.param.flags = IW_AUTH_PRIVACY_INVOKED;
+	iwr.u.param.value = enabled;
+
+	ioctl(drv->ioctl_sock, SIOCSIWAUTH, &iwr);
+
+	/* ignore errors, the kernel/driver might not care */
+	return 0;
 }
 
 





From johannes  Wed Dec 12 08:35:51 2007
From: johannes (Johannes Berg)
Date: Wed, 12 Dec 2007 17:35:51 +0100
Subject: [PATCH] hostapd: make driver_devicescape set multi-BSS interfaces up
Message-ID: <1197477351.6558.104.camel@johannes.berg>

It seems that I forgot this when converting the driver to nl80211, it should
of course set IFF_UP on all secondary BSS interfaces as well. I will handle
the MTU issue in a separate patch as this isn't really working right now
anyway. Also note that in another forthcoming patch I will change it to
receive EAPOL frames via the regular data interface. As I've noted before,
this is also necessary for proper MAC address setting in multi-BSS
scenarios.

Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
---
 hostapd/driver_devicescape.c |   18 +++++++++++++-----
 1 file changed, 13 insertions(+), 5 deletions(-)

--- hostap.orig/hostapd/driver_devicescape.c	2007-12-12 17:28:55.000000000 +0100
+++ hostap/hostapd/driver_devicescape.c	2007-12-12 17:29:00.000000000 +0100
@@ -77,7 +77,8 @@ static int i802_sta_set_flags(void *priv
 			      int total_flags, int flags_or, int flags_and);
 
 
-static int hostapd_set_iface_flags(struct i802_driver_data *drv, int dev_up)
+static int hostapd_set_iface_flags(struct i802_driver_data *drv,
+				   const char *ifname, int dev_up)
 {
 	struct ifreq ifr;
 
@@ -85,7 +86,7 @@ static int hostapd_set_iface_flags(struc
 		return -1;
 
 	memset(&ifr, 0, sizeof(ifr));
-	os_strlcpy(ifr.ifr_name, drv->iface, IFNAMSIZ);
+	os_strlcpy(ifr.ifr_name, ifname, IFNAMSIZ);
 
 	if (ioctl(drv->ioctl_sock, SIOCGIFFLAGS, &ifr) != 0) {
 		perror("ioctl[SIOCGIFFLAGS]");
@@ -854,8 +855,15 @@ static int nl80211_create_iface(struct i
 
 static int i802_bss_add(void *priv, const char *ifname, const u8 *bssid)
 {
-	if (nl80211_create_iface(priv, ifname, NL80211_IFTYPE_AP, bssid) < 0)
+	int ifidx;
+
+	ifidx = nl80211_create_iface(priv, ifname, NL80211_IFTYPE_AP, bssid);
+	if (ifidx < 0)
 		return -1;
+	if (hostapd_set_iface_flags(priv, ifname, 1)) {
+		nl80211_remove_iface(priv, ifidx);
+		return -1;
+	}
 	return 0;
 }
 
@@ -1563,7 +1571,7 @@ static int i802_init_sockets(struct i802
 		return -1;
 	}
 
-	if (hostapd_set_iface_flags(drv, 1))
+	if (hostapd_set_iface_flags(drv, drv->iface, 1))
 		return -1;
 
 	memset(&addr, 0, sizeof(addr));
@@ -1952,7 +1960,7 @@ static void i802_deinit(void *priv)
 	/* Disable management interface */
 	(void) hostap_ioctl_prism2param(drv, PRISM2_PARAM_MGMT_IF, 0);
 
-	(void) hostapd_set_iface_flags(drv, 0);
+	(void) hostapd_set_iface_flags(drv, drv->iface, 0);
 
 	if (drv->sock >= 0) {
 		eloop_unregister_read_sock(drv->sock);





From johannes  Wed Dec 12 08:38:03 2007
From: johannes (Johannes Berg)
Date: Wed, 12 Dec 2007 17:38:03 +0100
Subject: [PATCH] hostapd: allow bssid config on default interface
Message-ID: <1197477483.6558.108.camel@johannes.berg>

This patch makes hostapd accept bssid= on the default interface for
those drivers that are changed to support it and changes
driver_devicescape to support it. In order to support such a setting the
driver must provide an init_bssid() in addition to the init() routine.

Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
---
The reason I want this is that I'm lazy and because the default MAC
address of my interface is odd (lowest bit set) hostapd rejects the
configuration if I don't clear that bit by hand... specifying it in the
config file makes it much easier.

Other drivers could easily support it too but again I'm too lazy...

 hostapd/config.c             |    6 ++++--
 hostapd/driver.h             |    9 +++++++++
 hostapd/driver_devicescape.c |   28 ++++++++++++++++++++++++----
 hostapd/hostapd.c            |    8 +++++++-
 4 files changed, 44 insertions(+), 7 deletions(-)

--- hostap.orig/hostapd/driver.h	2007-12-12 17:27:56.000000000 +0100
+++ hostap/hostapd/driver.h	2007-12-12 17:29:03.000000000 +0100
@@ -23,6 +23,7 @@ struct wpa_driver_ops {
 	const char *name;		/* as appears in the config file */
 
 	void * (*init)(struct hostapd_data *hapd);
+	void * (*init_bssid)(struct hostapd_data *hapd, u8 *bssid);
 	void (*deinit)(void *priv);
 
 	int (*wireless_event_init)(void *priv);
@@ -168,6 +169,14 @@ hostapd_driver_init(struct hostapd_data 
 	return hapd->driver->init(hapd);
 }
 
+static inline void *
+hostapd_driver_init_bssid(struct hostapd_data *hapd, u8 *bssid)
+{
+	if (hapd->driver == NULL || hapd->driver->init_bssid == NULL)
+		return NULL;
+	return hapd->driver->init_bssid(hapd, bssid);
+}
+
 static inline void
 hostapd_driver_deinit(struct hostapd_data *hapd)
 {
--- hostap.orig/hostapd/config.c	2007-12-12 17:27:56.000000000 +0100
+++ hostap/hostapd/config.c	2007-12-12 17:29:03.000000000 +0100
@@ -1891,9 +1891,11 @@ struct hostapd_config * hostapd_config_r
 				errors++;
 			}
 		} else if (os_strcmp(buf, "bssid") == 0) {
-			if (bss == conf->bss) {
+			if (bss == conf->bss &&
+			    (!conf->driver || !conf->driver->init_bssid)) {
 				printf("Line %d: bssid item not allowed "
-				       "for the default interface\n", line);
+				       "for the default interface and this "
+				       "driver\n", line);
 				errors++;
 			} else if (hwaddr_aton(pos, bss->bssid)) {
 				printf("Line %d: invalid bssid item\n", line);
--- hostap.orig/hostapd/hostapd.c	2007-12-12 17:27:56.000000000 +0100
+++ hostap/hostapd/hostapd.c	2007-12-12 17:29:03.000000000 +0100
@@ -1468,12 +1468,18 @@ static int setup_interface1(struct hosta
 	struct hostapd_bss_config *conf = hapd->conf;
 	size_t i;
 	char country[4];
+	u8 *b = conf->bssid;
 
 	/*
 	 * Initialize the driver interface and make sure that all BSSes get
 	 * configured with a pointer to this driver interface.
 	 */
-	hapd->drv_priv = hostapd_driver_init(hapd);
+	if (b[0] | b[1] | b[2] | b[3] | b[4] | b[5]) {
+		hapd->drv_priv = hostapd_driver_init_bssid(hapd, b);
+	} else {
+		hapd->drv_priv = hostapd_driver_init(hapd);
+	}
+
 	if (hapd->drv_priv == NULL) {
 		printf("%s driver initialization failed.\n",
 			hapd->driver ? hapd->driver->name : "Unknown");
--- hostap.orig/hostapd/driver_devicescape.c	2007-12-12 17:29:00.000000000 +0100
+++ hostap/hostapd/driver_devicescape.c	2007-12-12 17:29:03.000000000 +0100
@@ -1499,7 +1499,7 @@ static void handle_read(int sock, void *
 }
 
 
-static int i802_init_sockets(struct i802_driver_data *drv)
+static int i802_init_sockets(struct i802_driver_data *drv, u8 *bssid)
 {
 	struct hostapd_data *hapd = drv->hapd;
 	struct hostapd_iface *iface = hapd->iface;
@@ -1515,6 +1515,20 @@ static int i802_init_sockets(struct i802
 		return -1;
 	}
 
+	if (hostapd_set_iface_flags(drv, drv->iface, 0))
+		return -1;
+
+	if (bssid) {
+		os_strlcpy(ifr.ifr_name, drv->iface, IFNAMSIZ);
+		memcpy(ifr.ifr_hwaddr.sa_data, bssid, ETH_ALEN);
+		ifr.ifr_hwaddr.sa_family = ARPHRD_ETHER;
+
+		if (ioctl(drv->ioctl_sock, SIOCSIFHWADDR, &ifr)) {
+			perror("ioctl(SIOCSIFHWADDR)");
+			return -1;
+		}
+	}
+
 	/*
 	 * initialise generic netlink and nl80211
 	 */
@@ -1928,8 +1942,7 @@ static int i802_sta_disassoc(void *priv,
 				       sizeof(mgmt.u.disassoc), 0);
 }
 
-
-static void * i802_init(struct hostapd_data *hapd)
+static void *i802_init_bssid(struct hostapd_data *hapd, u8 *bssid)
 {
 	struct i802_driver_data *drv;
 
@@ -1942,7 +1955,7 @@ static void * i802_init(struct hostapd_d
 	drv->hapd = hapd;
 	memcpy(drv->iface, hapd->conf->iface, sizeof(drv->iface));
 
-	if (i802_init_sockets(drv))
+	if (i802_init_sockets(drv, bssid))
 		goto failed;
 
 	return drv;
@@ -1953,6 +1966,12 @@ failed:
 }
 
 
+static void *i802_init(struct hostapd_data *hapd)
+{
+	return i802_init_bssid(hapd, NULL);
+}
+
+
 static void i802_deinit(void *priv)
 {
 	struct i802_driver_data *drv = priv;
@@ -1980,6 +1999,7 @@ static void i802_deinit(void *priv)
 const struct wpa_driver_ops wpa_driver_devicescape_ops = {
 	.name = "devicescape",
 	.init = i802_init,
+	.init_bssid = i802_init_bssid,
 	.deinit = i802_deinit,
 	.wireless_event_init = i802_wireless_event_init,
 	.wireless_event_deinit = i802_wireless_event_deinit,





From dcbw  Wed Dec 12 09:21:08 2007
From: dcbw (Dan Williams)
Date: Wed, 12 Dec 2007 12:21:08 -0500
Subject: [PATCH] fix memory leak in D-Bus control interface
Message-ID: <1197480068.13414.33.camel@localhost.localdomain>

Be sure to unref the D-Bus message for the signal after sending it.

When backporting to 0.5.x, s/_signal/signal/g and it should apply.

Dan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-dbus-ctrl-iface-signal-leaks.patch
Type: text/x-patch
Size: 1349 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071212/e13f1619/attachment.bin 


From silentkeystroke  Wed Dec 12 12:21:10 2007
From: silentkeystroke (Peter Savage)
Date: Wed, 12 Dec 2007 20:21:10 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <20071208180418.GC5698@jm.kir.nu>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
Message-ID: <7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>

On 08/12/2007, Jouni Malinen <j at w1.fi> wrote:
>
> On Sat, Dec 08, 2007 at 05:36:34PM +0000, Peter Savage wrote:
>
> > I've just setup a DLink card with an atheros chipset as an AP, using
> hostapd
> > and madwifi.  I'm using the stock pacakges available in ubuntu gutsy.
> > However, this appears to only allow one client to connect, what am I
> > missing?  When the second client connects, it just gets an
> authentication
> > failure message.
>
> Please send debug log from hostapd (-dd on command line) showing both
> the successful connection and the failed one.


I'll try to grab that data, I've found that actually multiple clients can
connect, but it's hit and miss as to whether they actually connect or not.
I'll try to get that log data later on today.


-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071212/293ea0ab/attachment.htm 


From silentkeystroke  Wed Dec 12 14:04:41 2007
From: silentkeystroke (Peter Savage)
Date: Wed, 12 Dec 2007 22:04:41 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
	<7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
Message-ID: <7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>

This is the hostapd.conf file


interface=ath0
driver=madwifi
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=instance89
hw_mode=b
channel=60
beacon_int=100
dtim_period=2
max_num_sta=255
rts_threshold=2347
fragm_threshold=2346
macaddr_acl=0
auth_algs=3
ignore_broadcast_ssid=0
wme_enabled=1
wme_ac_bk_cwmin=4
wme_ac_bk_cwmax=10
wme_ac_bk_aifs=7
wme_ac_bk_txop_limit=0
wme_ac_bk_acm=0
wme_ac_be_aifs=3
wme_ac_be_cwmin=4
wme_ac_be_cwmax=10
wme_ac_be_txop_limit=0
wme_ac_be_acm=0
wme_ac_vi_aifs=2
wme_ac_vi_cwmin=3
wme_ac_vi_cwmax=4
wme_ac_vi_txop_limit=94
wme_ac_vi_acm=0
wme_ac_vo_aifs=2
wme_ac_vo_cwmin=2
wme_ac_vo_cwmax=3
wme_ac_vo_txop_limit=47
wme_ac_vo_acm=0

eapol_key_index_workaround=0
eap_server=0

own_ip_addr=127.0.0.1

wpa=1
wpa_passphrase=<OBFUSCATED>
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP

=============================
And now the interfaces

auto ath0
iface ath0 inet static
pre-up wlanconfig ath0 destroy || true
pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
post-down wlanconfig ath0 destroy
address 10.3.0.1
netmask 255.255.0.0
broadcast 10.3.255.255
wireless-mode master
wireless-essid instance89
up hostapd -B /etc/hostapd/hostapd.conf


Please help !
-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071212/ca7393c7/attachment.htm 


From silentkeystroke  Wed Dec 12 13:53:17 2007
From: silentkeystroke (Peter Savage)
Date: Wed, 12 Dec 2007 21:53:17 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
Message-ID: <7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>

Using versions
hostapd 0.5.7

I think madwifi is built into my ubuntu gutsy restricted kernels.  I can't
seem to get the version.  This has previously worked ok with some linux
clients.  but at the moment I can't get my Nokia N800 to connect, or my
laptop.  A windows XP machine however connects fine as shown below.  I'm
really not sure what's happening here.  Occasionally clients will connect
but it usually takes a few tries.  At the moment however no linux based
clients seem able to connect.

Any help very much appreciated

Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
madwifi_set_iface_flags: dev_up=0
madwifi_set_privacy: enabled=0
BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
SIOCGIWRANGE: WE(compiled)=22 WE(source)=13 enc_capa=0xf
ath0: IEEE 802.11 Fetching hardware channel/rate support not supported.
Flushing old station entries
madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3
madwifi_sta_deauth: Failed to deauth STA (addr ff:ff:ff:ff:ff:ff reason 3)
Could not connect to kernel driver.
Deauthenticate all stations
Mode: IEEE 802.11b  Channel: 60  Frequency: 0 MHz
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=0
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=1
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=2
madwifi_del_key: addr=00:00:00:00:00:00 key_idx=3
Using interface ath0 with hwaddr 00:11:95:94:22:2c and ssid 'instance89'
SSID - hexdump_ascii(len=10):
     *****OBFUSCATED******
PSK (ASCII passphrase) - hexdump_ascii(len=12):
     *****OBFUSCATED******
PSK (from passphrase) - hexdump(len=32):      *****OBFUSCATED******
madwifi_set_ieee8021x: enabled=1
madwifi_configure_wpa: group key cipher=1
madwifi_configure_wpa: pairwise key ciphers=0xa
madwifi_configure_wpa: key management algorithms=0x2
madwifi_configure_wpa: rsn capabilities=0x0
madwifi_configure_wpa: enable WPA=0x1
madwifi_set_privacy: enabled=0
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
GMK - hexdump(len=32): [REMOVED]
GTK - hexdump(len=32): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
madwifi_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1
madwifi_set_privacy: enabled=1
madwifi_set_iface_flags: dev_up=1
ath0: Setup of interface done.
Wireless event: cmd=0x8b1a len=19
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:19:4f:9e:cd:26 IEEE 802.11: associated
  New STA
ath0: STA 00:19:4f:9e:cd:26 WPA: event 1 notification
madwifi_del_key: addr=00:19:4f:9e:cd:26 key_idx=0
ath0: STA 00:19:4f:9e:cd:26 WPA: start authentication
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:19:4f:9e:cd:26 key_idx=0
madwifi_set_sta_authorized: addr=00:19:4f:9e:cd:26 authorized=0
ath0: STA 00:19:4f:9e:cd:26 IEEE 802.1X: unauthorizing port
WPA: 00:19:4f:9e:cd:26 WPA_PTK_GROUP entering state IDLE
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state AUTHENTICATION
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state AUTHENTICATION2
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state INITPSK
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state PTKSTART
ath0: STA 00:19:4f:9e:cd:26 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0
encr=0)
TX EAPOL - hexdump(len=113): 00 19 4f 9e cd 26 00 11 95 94 22 2c 88 8e 02 03
00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 bf 6f 4b 1c 15 46 72 45 18 d4
5f 1a 08 87 a3 c1 3d 76 af ad aa ba ad 7e a8 d2 df 4d 71 6b d9 f6 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ath0: STA 00:19:4f:9e:cd:26 WPA: EAPOL-Key timeout
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state PTKSTART
ath0: STA 00:19:4f:9e:cd:26 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0
encr=0)
TX EAPOL - hexdump(len=113): 00 19 4f 9e cd 26 00 11 95 94 22 2c 88 8e 02 03
00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 02 bf 6f 4b 1c 15 46 72 45 18 d4
5f 1a 08 87 a3 c1 3d 76 af ad aa ba ad 7e a8 d2 df 4d 71 6b d9 f6 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ath0: STA 00:19:4f:9e:cd:26 WPA: EAPOL-Key timeout
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state PTKSTART
ath0: STA 00:19:4f:9e:cd:26 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0
encr=0)
TX EAPOL - hexdump(len=113): 00 19 4f 9e cd 26 00 11 95 94 22 2c 88 8e 02 03
00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 03 bf 6f 4b 1c 15 46 72 45 18 d4
5f 1a 08 87 a3 c1 3d 76 af ad aa ba ad 7e a8 d2 df 4d 71 6b d9 f6 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ath0: STA 00:19:4f:9e:cd:26 WPA: EAPOL-Key timeout
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state PTKSTART
ath0: STA 00:19:4f:9e:cd:26 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0
encr=0)
TX EAPOL - hexdump(len=113): 00 19 4f 9e cd 26 00 11 95 94 22 2c 88 8e 02 03
00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 04 bf 6f 4b 1c 15 46 72 45 18 d4
5f 1a 08 87 a3 c1 3d 76 af ad aa ba ad 7e a8 d2 df 4d 71 6b d9 f6 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state DISCONNECT
hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA
00:19:4f:9e:cd:26 reason 2
madwifi_sta_deauth: addr=00:19:4f:9e:cd:26 reason_code=2
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state DISCONNECTED
WPA: 00:19:4f:9e:cd:26 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:19:4f:9e:cd:26 key_idx=0
madwifi_del_key: Failed to delete key (addr 00:19:4f:9e:cd:26 key_idx 0)
madwifi_set_sta_authorized: addr=00:19:4f:9e:cd:26 authorized=0
madwifi_set_sta_authorized: Failed to unauthorize STA 00:19:4f:9e:cd:26
ath0: STA 00:19:4f:9e:cd:26 IEEE 802.1X: unauthorizing port
Could not set station 00:19:4f:9e:cd:26 flags for kernel driver (errno=29).
ath0: STA 00:19:4f:9e:cd:26 IEEE 802.11: deauthenticated due to local deauth
request
Wireless event: cmd=0x8c02 len=97
Custom wireless event: 'STA-TRAFFIC-STAT
mac=00:19:4f:9e:cd:26
rx_packets=0
rx_bytes=0
tx_packets=4
tx_bytes=428
'
Wireless event: cmd=0x8c04 len=20
ath0: STA 00:19:4f:9e:cd:26 IEEE 802.11: disassociated
Wireless event: cmd=0x8c03 len=20

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

However, it works fine on a windows machine

ath0: STA 00:19:7e:53:90:54 IEEE 802.11: associated
  New STA
ath0: STA 00:19:7e:53:90:54 WPA: event 1 notification
madwifi_del_key: addr=00:19:7e:53:90:54 key_idx=0
ath0: STA 00:19:7e:53:90:54 WPA: start authentication
WPA: 00:19:7e:53:90:54 WPA_PTK entering state INITIALIZE
madwifi_del_key: addr=00:19:7e:53:90:54 key_idx=0
madwifi_set_sta_authorized: addr=00:19:7e:53:90:54 authorized=0
ath0: STA 00:19:7e:53:90:54 IEEE 802.1X: unauthorizing port
WPA: 00:19:7e:53:90:54 WPA_PTK_GROUP entering state IDLE
WPA: 00:19:7e:53:90:54 WPA_PTK entering state AUTHENTICATION
WPA: 00:19:7e:53:90:54 WPA_PTK entering state AUTHENTICATION2
WPA: 00:19:7e:53:90:54 WPA_PTK entering state INITPSK
WPA: 00:19:7e:53:90:54 WPA_PTK entering state PTKSTART
ath0: STA 00:19:7e:53:90:54 WPA: sending 1/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0
encr=0)
TX EAPOL - hexdump(len=113): 00 19 7e 53 90 54 00 11 95 94 22 2c 88 8e 02 03
00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 c2 fd a7 82 ef a1 10 21 2b 09
56 8f a6 1d 74 03 a5 1e e1 5f 62 9e 30 ea ad 75 f9 70 83 9a 67 c7 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
IEEE 802.1X: 125 bytes from 00:19:7e:53:90:54
   IEEE 802.1X: version=1 type=3 length=121
ath0: STA 00:19:7e:53:90:54 WPA: received EAPOL-Key frame (2/4 Pairwise)
WPA: 00:19:7e:53:90:54 WPA_PTK entering state PTKCALCNEGOTIATING
PMK - hexdump(len=32): [REMOVED]
PTK - hexdump(len=64): [REMOVED]
WPA: 00:19:7e:53:90:54 WPA_PTK entering state PTKCALCNEGOTIATING2
WPA: 00:19:7e:53:90:54 WPA_PTK entering state PTKINITNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:19:7e:53:90:54 WPA: sending 3/4 msg of 4-Way Handshake
WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28
keyidx=0 encr=0)
TX EAPOL - hexdump(len=141): 00 19 7e 53 90 54 00 11 95 94 22 2c 88 8e 02 03
00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 c2 fd a7 82 ef a1 10 21 2b 09
56 8f a6 1d 74 03 a5 1e e1 5f 62 9e 30 ea ad 75 f9 70 83 9a 67 c7 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 79 5f 62 93 04 9e 2f 9d b4 53 d5 21 b8 fa dd f7 00 1c dd 1a 00
50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X: 99 bytes from 00:19:7e:53:90:54
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:19:7e:53:90:54 WPA: received EAPOL-Key frame (4/4 Pairwise)
WPA: 00:19:7e:53:90:54 WPA_PTK entering state PTKINITDONE
madwifi_set_key: alg=CCMP addr=00:19:7e:53:90:54 key_idx=0
madwifi_set_sta_authorized: addr=00:19:7e:53:90:54 authorized=1
ath0: STA 00:19:7e:53:90:54 IEEE 802.1X: authorizing port
madwifi_sta_clear_stats: addr=00:19:7e:53:90:54
ath0: STA 00:19:7e:53:90:54 WPA: pairwise key handshake completed (WPA)
WPA: 00:19:7e:53:90:54 WPA_PTK_GROUP entering state REKEYNEGOTIATING
madwifi_get_seqnum: addr=00:00:00:00:00:00 idx=1
ath0: STA 00:19:7e:53:90:54 WPA: sending 1/2 msg of Group Key Handshake
WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32
keyidx=1 encr=1)
Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED]
TX EAPOL - hexdump(len=153): 00 19 7e 53 90 54 00 11 95 94 22 2c 88 8e 02 03
00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 c2 fd a7 82 ef a1 10 21 2b 09
56 8f a6 1d 74 03 a5 1e e1 5f 62 9e 30 ea ad 75 f9 70 83 9a 67 bd 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 93 9d af 28 25 13 0e 33 61 94 21 df df 61 6a 9d 00 28 8f 02 ff
33 75 8c 26 a4 02 60 a3 66 0f 45 9d ac e2 f9 3d ca 09 c2 5d 29 93 8d e8 77
de d3 d7 fa 83 1a c2 c4 c5 fc 53 a4
IEEE 802.1X: 99 bytes from 00:19:7e:53:90:54
   IEEE 802.1X: version=1 type=3 length=95
ath0: STA 00:19:7e:53:90:54 WPA: received EAPOL-Key frame (2/2 Group)
WPA: 00:19:7e:53:90:54 WPA_PTK_GROUP entering state REKEYESTABLISHED
ath0: STA 00:19:7e:53:90:54 WPA: group key handshake completed (WPA)

-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071212/28c43264/attachment.htm 


From LTI  Wed Dec 12 16:11:30 2007
From: LTI (LTI. - Ticmanis, Linards)
Date: Thu, 13 Dec 2007 01:11:30 +0100
Subject: wpa_supplicant: "LEAP (note: requires special support from the
	driver)"
Message-ID: <37ED64EE21A398409D609EAF7B0525A0216520@hw-mail.hannover.huwag.net>

Hello to all of you,

is there someone in here who could help me with this note found on the wpa_supplicant website?

    "* LEAP (note: requires special support from the driver)"

What exactly does my driver have to do extra to support LEAP? Is it another ioctl or some such?

The driver I'm working on is basically an older version of the marvell-libertas code found in the most recent Linux kernel (currently, changing my project to that kernel is not yet possible for other resons). LEAP-based WPA works fine, but I can't find a way to get "LEAP with dynamic WEP keys" working.

I'd be extremely grateful for any help or hints.

Regards,
-- 
Linards Ticmanis



From jagadish.nadimpalli  Thu Dec 13 00:40:09 2007
From: jagadish.nadimpalli (Jagadish)
Date: Thu, 13 Dec 2007 14:10:09 +0530
Subject: hostapd is working as RADIUS server
Message-ID: <4760EFE9.7070708@oneconvergence.com>

Hi,

The hostapd daemon is working as RADIUS server for me. I did the 
following configuration for it.

1) In hostapd.conf file

    a) interface=eth0  --- Since I used wired driver.
    b) removed all AP related configurations.
    c) In "Integrated EAP server" section, added eap_server=1, 
    eap_user_file=/etc/hostapd.eap_user, ca_cert=/etc/root.pem,
    server_cert=/etc/server.pem, private_key=/etc/server.pem,
    private_key_passwd=serverpasswd.
    d) In "RADIUS authentication server configuration" section added
    radius_server_clients=/etc/hostapd.radius_clients,
    radius_server_auth_ports=1812.
    e) In "WPA/IEEE 80211i configuration" added wpa_key_mgmt=WPA-EAP,
    wpa_pairwise=TKIP CCMP.

2) In /etc/hostapd.eap_user file

    Add * TLS. I am using EAP_TLS. So enabled this and disabled all
    other methods.

3) In /etc/hostapd.radius_clients

    Add your subnet on which the AP reside. Shared key need to be
    specified. This is shared between AP and RADIUS server.

With this configuration I ran hostapd with hostapd.conf as argument. It 
is working.

thanks,
Jagadish



From johannes  Wed Dec 12 18:23:34 2007
From: johannes (Johannes Berg)
Date: Thu, 13 Dec 2007 03:23:34 +0100
Subject: [FYI] hostapd with mac80211 progress
Message-ID: <1197512614.6558.224.camel@johannes.berg>

Hi,

I thought I'd write another update because I'm much further than last
time, I've been able to remove the management interface.

With my "[RFC] mac80211: clean up frame receive handling" patch and a
few more patches like "[PATCH] mac80211: fix header ops" I've been able
to implement hostapd without the management interface.

That requires a whole bunch of patches which, as always, you can find on
http://johannes.sipsolutions.net/patches/. I will be sending them out as
I feel appropriate. There are, contrary to what some think, reasons I
haven't done so yet. For example, I just found a bug with multicast keys
in my hostapd key patches.

The only ioctls I now still need are:

020-prism2-ioctl-bridge-packets.patch
021-prism2-ioctl-8021x.patch
022-hostapd-ioctl-hw-features.patch

However, a few more things are missing:
 * set_rate_sets <*>
 * set_channel_flag <*>
 * set_regulatory_domain <*>
 * set_tx_queue_params
 * set_cts_protect
 * set_preamble
 * set_short_slot_time
 * sta_clear_stats

hostapd works without these, but obviously not actually correctly (it
advertises WMM without being able to set queue parameters etc). The
items marked with <*> depend on the regulatory stuff we're going to
implement in the kernel.

The big thing with removing the management interface was the receive
frame handling cleanup that also made EAPOL frames show up on the
respective data interface rather than requiring the management
interface. This means that we can now use a monitor interface for
getting the management frames (and TX status callbacks) instead of the
management interface. Michael Wu is working on optimising this by adding
a "cooked" monitor mode that doesn't show data frames that were handled
by other virtual interfaces, but right now that's only an optimisation.
It will matter again when 802.11w is implemented where "cooked" will
give us decrypted frames, but w/o 802.11w management frames are always
sent in clear (and never fragmented in either case) so the regular
monitor interfaces work fine.

Also, using the monitor interfaces here means that we'll again send
deauth/disassoc frames when receiving class three frames from
not-associated stations as soon as the cooked monitor is used instead of
the socket filter. That still needs to be fixed up to work with PS-poll
packets, but that's a SMOP.

Other things to do include:
 * key threshold notifications
 * Michael MIC failure notifications (disable TKIP for now)

Ron, have you started working on traffic flows for hostapd yet? If so, I
guess I should set up a git tree or simply push all my hostapd patches
to Jouni (and send fixes as I find the bugs) because otherwise we're
going to produce many conflicts, most of my changes are quite large.
OTOH, I guess the only thing you need to do in the nl80211 driver stuff
is add support for flows to the station management. Let me know how you
want to proceed.

All, any help with hostapd would be much appreciated. In case I forget
to publish my hostapd patches though, ping me rather than working from
older ones. Any patches older than this mail are too old.

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


From raghavendra.akkasali  Thu Dec 13 05:14:13 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Thu, 13 Dec 2007 22:14:13 +0900
Subject: what is the max time that a wpa supplicant daemon takes?
Message-ID: <58a444250712130514v7d62d2b3h6a08c013d0446bbe@mail.gmail.com>

Hi,

   I would like to know what is the max time that a wpa supplicant
takes to come up?

 Assume that I have proper configuration in wpa_supplicant.conf.
Actually I want to know what is the time taken to come up, if I
configure to support EAP security and time taken for WEP. Just
interested to know is that time can be in seconds in worst case?

-- 
Regards & Thanks
Raghavendra. S



From tomasw  Thu Dec 13 06:35:27 2007
From: tomasw (Tomas Winkler)
Date: Thu, 13 Dec 2007 16:35:27 +0200
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1197512614.6558.224.camel@johannes.berg>
References: <1197512614.6558.224.camel@johannes.berg>
Message-ID: <1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>

> Ron, have you started working on traffic flows for hostapd yet? If so, I
> guess I should set up a git tree or simply push all my hostapd patches
> to Jouni (and send fixes as I find the bugs) because otherwise we're
> going to produce many conflicts, most of my changes are quite large.
> OTOH, I guess the only thing you need to do in the nl80211 driver stuff
> is add support for flows to the station management. Let me know how you
> want to proceed.
>

I take this question instead of Ron.
We have mostly configuration patches - (enhanced hostap_ioctls.h)  and
some minor changes in hostapd flows that we would like to rebase over
your changes to nl80211/mac80211 and hostap respectively. We can start
with 11n Association flows patches.
It would be great if you can setup git repository. Unfortunately it's
rather complicated to export one from Intel.
Thanks
Tomas


> All, any help with hostapd would be much appreciated. In case I forget
> to publish my hostapd patches though, ping me rather than working from
> older ones. Any patches older than this mail are too old.
>
> johannes
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>



From dcbw  Thu Dec 13 06:51:18 2007
From: dcbw (Dan Williams)
Date: Thu, 13 Dec 2007 09:51:18 -0500
Subject: wpa_supplicant: "LEAP (note: requires special support from the
	driver)"
In-Reply-To: <37ED64EE21A398409D609EAF7B0525A0216520@hw-mail.hannover.huwag.net>
References: <37ED64EE21A398409D609EAF7B0525A0216520@hw-mail.hannover.huwag.net>
Message-ID: <1197557478.2528.13.camel@localhost.localdomain>

On Thu, 2007-12-13 at 01:11 +0100, LTI. - Ticmanis, Linards wrote:
> Hello to all of you,
> 
> is there someone in here who could help me with this note found on the wpa_supplicant website?
> 
>     "* LEAP (note: requires special support from the driver)"
> 
> What exactly does my driver have to do extra to support LEAP? Is it another ioctl or some such?

It needs to support the SIOCSIWAUTH call and the IW_AUTH_80211_AUTH_ALG
sub-command.  Into which you pass IW_AUTH_ALG_LEAP.  The driver _should_
support LEAP correctly, but I have never tested LEAP with libertas.

> The driver I'm working on is basically an older version of the marvell-libertas code found in the most recent Linux kernel (currently, changing my project to that kernel is not yet possible for other resons). LEAP-based WPA works fine, but I can't find a way to get "LEAP with dynamic WEP keys" working.

Could you say which exact kernel version you're using?

Can you provide some debug output (libertas_debug=0x43a7 is usually
pretty good) of an attempted association using LEAP?

What firmware version and interface (CF, SDIO, USB) are you using?

Dan




From dcbw  Thu Dec 13 06:53:45 2007
From: dcbw (Dan Williams)
Date: Thu, 13 Dec 2007 09:53:45 -0500
Subject: what is the max time that a wpa supplicant daemon takes?
In-Reply-To: <58a444250712130514v7d62d2b3h6a08c013d0446bbe@mail.gmail.com>
References: <58a444250712130514v7d62d2b3h6a08c013d0446bbe@mail.gmail.com>
Message-ID: <1197557625.2528.17.camel@localhost.localdomain>

On Thu, 2007-12-13 at 22:14 +0900, Raghavendra. S wrote:
> Hi,
> 
>    I would like to know what is the max time that a wpa supplicant
> takes to come up?
> 
>  Assume that I have proper configuration in wpa_supplicant.conf.
> Actually I want to know what is the time taken to come up, if I
> configure to support EAP security and time taken for WEP. Just
> interested to know is that time can be in seconds in worst case?

It depends a lot on how long it takes for the card to scan for the AP
you want to connect to and find it.  That's a completely variable time.
So is the association time.

Are you trying to run a timeout to kill the supplicant if it hasn't
connected within a certain time or something?  If that's the case, just
use the control socket and the supplicant will tell you it's state.

If thats not what you're trying to do, could you say a bit more about
what you're trying to achieve here?

Dan





From johannes  Thu Dec 13 09:36:03 2007
From: johannes (Johannes Berg)
Date: Thu, 13 Dec 2007 18:36:03 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	(sfid-20071213_143532_407063_3AB777D4)
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	(sfid-20071213_143532_407063_3AB777D4)
Message-ID: <1197567363.8313.31.camel@johannes.berg>


> We have mostly configuration patches - (enhanced hostap_ioctls.h)  and
> some minor changes in hostapd flows that we would like to rebase over
> your changes to nl80211/mac80211 and hostap respectively. We can start
> with 11n Association flows patches.

Sounds good.

> It would be great if you can setup git repository. Unfortunately it's
> rather complicated to export one from Intel.

Not sure if I really want to, maybe we can convince Jouni to take
patches early if they don't break anything else?

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


From johannes  Thu Dec 13 09:36:55 2007
From: johannes (Johannes Berg)
Date: Thu, 13 Dec 2007 18:36:55 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	(sfid-20071213_143532_407063_3AB777D4)
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	(sfid-20071213_143532_407063_3AB777D4)
Message-ID: <1197567415.8313.33.camel@johannes.berg>


> We have mostly configuration patches - (enhanced hostap_ioctls.h)  and
> some minor changes in hostapd flows that we would like to rebase over
> your changes to nl80211/mac80211 and hostap respectively. We can start
> with 11n Association flows patches.

Oh btw, will you be publishing driver updates to support AP mode in
iwlwifi? You must have them anyway if you're working on this and I'd
love have a second driver capable of AP mode in the kernel.

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


From chasedouglas  Thu Dec 13 10:06:29 2007
From: chasedouglas (Chase Douglas)
Date: Thu, 13 Dec 2007 13:06:29 -0500
Subject: AR5212 "Association requestion to the driver failed"
Message-ID: <476174A5.7080304@gmail.com>

Hello,

I've got two IBM/Lenovo laptops, a t41p and a t60. Both have the Atheros 
5212 wireless chips in them. Both have madwifi-ng-0.9.3.3 and 
wpa_supplicant-0.5.8. Both are configured to connect to my home WPA 
network using the same block:

network={
	priority=1
	ssid="myssid"
	psk="mypsk"
}

However, the t60 can connect to the network while the t41p cannot. Under 
wpa_cli, the t41p prints:

Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
Association requestion to the driver failed
Associated with <myroutermacaddr>
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

What could be going wrong here?

Thanks



From silentkeystroke  Thu Dec 13 12:18:50 2007
From: silentkeystroke (Peter Savage)
Date: Thu, 13 Dec 2007 20:18:50 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
	<7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
	<7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>
Message-ID: <7293d610712131218ifd7a40eu69b3ff17c6b06ee8@mail.gmail.com>

Also I've noticed that occasionally all my interfaces seem to go
unresponsive.  This only started happening when I inserted the NIC.  I
thought it was a network manager issue, but I have since removed that, so it
shouldn't be causing a problem anymore.

On 12/12/2007, Peter Savage <silentkeystroke at googlemail.com> wrote:
>
> This is the hostapd.conf file
>
>
> interface=ath0
> driver=madwifi
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> debug=0
> dump_file=/tmp/hostapd.dump
> ctrl_interface=/var/run/hostapd
> ctrl_interface_group=0
> ssid=instance89
> hw_mode=b
> channel=60
> beacon_int=100
> dtim_period=2
> max_num_sta=255
> rts_threshold=2347
> fragm_threshold=2346
> macaddr_acl=0
> auth_algs=3
> ignore_broadcast_ssid=0
> wme_enabled=1
> wme_ac_bk_cwmin=4
> wme_ac_bk_cwmax=10
> wme_ac_bk_aifs=7
> wme_ac_bk_txop_limit=0
> wme_ac_bk_acm=0
> wme_ac_be_aifs=3
> wme_ac_be_cwmin=4
> wme_ac_be_cwmax=10
> wme_ac_be_txop_limit=0
> wme_ac_be_acm=0
> wme_ac_vi_aifs=2
> wme_ac_vi_cwmin=3
> wme_ac_vi_cwmax=4
> wme_ac_vi_txop_limit=94
> wme_ac_vi_acm=0
> wme_ac_vo_aifs=2
> wme_ac_vo_cwmin=2
> wme_ac_vo_cwmax=3
> wme_ac_vo_txop_limit=47
> wme_ac_vo_acm=0
>
> eapol_key_index_workaround=0
> eap_server=0
>
> own_ip_addr=127.0.0.1
>
> wpa=1
> wpa_passphrase=<OBFUSCATED>
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP CCMP
>
> =============================
> And now the interfaces
>
> auto ath0
> iface ath0 inet static
> pre-up wlanconfig ath0 destroy || true
> pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
> post-down wlanconfig ath0 destroy
> address 10.3.0.1
> netmask 255.255.0.0
> broadcast 10.3.255.255
> wireless-mode master
> wireless-essid instance89
> up hostapd -B /etc/hostapd/hostapd.conf
>
>
> Please help !
> --
> Pete Savage - cbx33::silentk
> wiki.ubuntu.com/PeteSavage
>



-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071213/f6b201f6/attachment.htm 


From dcbw  Thu Dec 13 13:27:29 2007
From: dcbw (Dan Williams)
Date: Thu, 13 Dec 2007 16:27:29 -0500
Subject: AR5212 "Association requestion to the driver failed"
In-Reply-To: <476174A5.7080304@gmail.com>
References: <476174A5.7080304@gmail.com>
Message-ID: <1197581250.14270.19.camel@localhost.localdomain>

On Thu, 2007-12-13 at 13:06 -0500, Chase Douglas wrote:
> Hello,
> 
> I've got two IBM/Lenovo laptops, a t41p and a t60. Both have the Atheros 
> 5212 wireless chips in them. Both have madwifi-ng-0.9.3.3 and 
> wpa_supplicant-0.5.8. Both are configured to connect to my home WPA 
> network using the same block:
> 
> network={
> 	priority=1
> 	ssid="myssid"
> 	psk="mypsk"
> }
> 
> However, the t60 can connect to the network while the t41p cannot. Under 
> wpa_cli, the t41p prints:
> 
> Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
> Association requestion to the driver failed
> Associated with <myroutermacaddr>
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

wpa_supplicant says that when the wpa_drv_associate() function returns
an error code.  The most usual cause of that is that the driver does not
support some of the parameters wpa_supplicant is try to set.  That's OK,
it's normal that drivers don't support all of the ioctls.  And the
association routine should just ignore those parameters that fail unless
they really are fatal.

So you'll need to get more debugging output about _what_ call failed to
determine whether or not it's an important failure.  On Fedora we have a
patch that prints out specifically which calls the driver does not
support, which aids in debugging.

Are you using the 'madwifi' driver or the 'wext' driver?  If you're
using the madwifi driver, try the 'wext' driver instead.

Dan





From chasedouglas  Thu Dec 13 14:29:58 2007
From: chasedouglas (Chase Douglas)
Date: Thu, 13 Dec 2007 17:29:58 -0500
Subject: AR5212 "Association requestion to the driver failed"
In-Reply-To: <1197581250.14270.19.camel@localhost.localdomain>
References: <476174A5.7080304@gmail.com>
	<1197581250.14270.19.camel@localhost.localdomain>
Message-ID: <4761B266.9080205@gmail.com>

Dan Williams wrote:
> On Thu, 2007-12-13 at 13:06 -0500, Chase Douglas wrote:
>   
>> Hello,
>>
>> I've got two IBM/Lenovo laptops, a t41p and a t60. Both have the Atheros 
>> 5212 wireless chips in them. Both have madwifi-ng-0.9.3.3 and 
>> wpa_supplicant-0.5.8. Both are configured to connect to my home WPA 
>> network using the same block:
>>
>> network={
>> 	priority=1
>> 	ssid="myssid"
>> 	psk="mypsk"
>> }
>>
>> However, the t60 can connect to the network while the t41p cannot. Under 
>> wpa_cli, the t41p prints:
>>
>> Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
>> Association requestion to the driver failed
>> Associated with <myroutermacaddr>
>> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>>     
>
> wpa_supplicant says that when the wpa_drv_associate() function returns
> an error code.  The most usual cause of that is that the driver does not
> support some of the parameters wpa_supplicant is try to set.  That's OK,
> it's normal that drivers don't support all of the ioctls.  And the
> association routine should just ignore those parameters that fail unless
> they really are fatal.
>
> So you'll need to get more debugging output about _what_ call failed to
> determine whether or not it's an important failure.  On Fedora we have a
> patch that prints out specifically which calls the driver does not
> support, which aids in debugging.
>
> Are you using the 'madwifi' driver or the 'wext' driver?  If you're
> using the madwifi driver, try the 'wext' driver instead.
>
> Dan

I am using the madwifi driver. Which Atheros driver would use wext?

Thanks



From silentkeystroke  Thu Dec 13 15:03:35 2007
From: silentkeystroke (Peter Savage)
Date: Thu, 13 Dec 2007 23:03:35 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712131218ifd7a40eu69b3ff17c6b06ee8@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
	<7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
	<7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>
	<7293d610712131218ifd7a40eu69b3ff17c6b06ee8@mail.gmail.com>
Message-ID: <7293d610712131503s16597e4xfd8e53c488ed5ffc@mail.gmail.com>

ok.  i have managed to get this linux client to connect, however it seems
very hit and miss.  suffice to say authentication does work.  but it may not
hold the connection, or may not authenticate in the first place.  My speed
also seems limited to 5.5Mb.  Also, the windows xp client can still connect
without a problem.  very odd.  The connection dropped whilst i was writing
this email too.


-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071213/f82ae17a/attachment.htm 


From tomasw  Thu Dec 13 15:25:34 2007
From: tomasw (Tomas Winkler)
Date: Fri, 14 Dec 2007 01:25:34 +0200
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1197567415.8313.33.camel@johannes.berg>
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	<1197567415.8313.33.camel@johannes.berg>
Message-ID: <1ba2fa240712131525o6c0767e8je8a4feff21fbae69@mail.gmail.com>

On Dec 13, 2007 7:36 PM, Johannes Berg <johannes at sipsolutions.net> wrote:

>Not sure if I really want to, maybe we can convince Jouni to take
>patches early if they don't break anything else?

That's probably the best option as more people are looking there so
we've might receive more exposure and get fast response.

> Oh btw, will you be publishing driver updates to support AP mode in
> iwlwifi? You must have them anyway if you're working on this and I'd
> love have a second driver capable of AP mode in the kernel.

We have frozen the AP stack before you've removed management interface
so first we have to rebase it to the current code, but it's being done
it will all go through this mailing list

Thanks
Tomas

>



From dcbw  Thu Dec 13 15:53:16 2007
From: dcbw (Dan Williams)
Date: Thu, 13 Dec 2007 18:53:16 -0500
Subject: AR5212 "Association requestion to the driver failed"
In-Reply-To: <4761B266.9080205@gmail.com>
References: <476174A5.7080304@gmail.com>
	<1197581250.14270.19.camel@localhost.localdomain>
	<4761B266.9080205@gmail.com>
Message-ID: <1197589996.14897.6.camel@localhost.localdomain>

On Thu, 2007-12-13 at 17:29 -0500, Chase Douglas wrote:
> Dan Williams wrote:
> > On Thu, 2007-12-13 at 13:06 -0500, Chase Douglas wrote:
> >   
> >> Hello,
> >>
> >> I've got two IBM/Lenovo laptops, a t41p and a t60. Both have the Atheros 
> >> 5212 wireless chips in them. Both have madwifi-ng-0.9.3.3 and 
> >> wpa_supplicant-0.5.8. Both are configured to connect to my home WPA 
> >> network using the same block:
> >>
> >> network={
> >> 	priority=1
> >> 	ssid="myssid"
> >> 	psk="mypsk"
> >> }
> >>
> >> However, the t60 can connect to the network while the t41p cannot. Under 
> >> wpa_cli, the t41p prints:
> >>
> >> Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
> >> Association requestion to the driver failed
> >> Associated with <myroutermacaddr>
> >> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> >>     
> >
> > wpa_supplicant says that when the wpa_drv_associate() function returns
> > an error code.  The most usual cause of that is that the driver does not
> > support some of the parameters wpa_supplicant is try to set.  That's OK,
> > it's normal that drivers don't support all of the ioctls.  And the
> > association routine should just ignore those parameters that fail unless
> > they really are fatal.
> >
> > So you'll need to get more debugging output about _what_ call failed to
> > determine whether or not it's an important failure.  On Fedora we have a
> > patch that prints out specifically which calls the driver does not
> > support, which aids in debugging.
> >
> > Are you using the 'madwifi' driver or the 'wext' driver?  If you're
> > using the madwifi driver, try the 'wext' driver instead.
> >
> > Dan
> 
> I am using the madwifi driver. Which Atheros driver would use wext?

madwifi will.  Try running wpa_supplicant with "-D wext" instead of "-D
madwifi".

dan





From chasedouglas  Thu Dec 13 16:01:50 2007
From: chasedouglas (Chase Douglas)
Date: Thu, 13 Dec 2007 19:01:50 -0500
Subject: AR5212 "Association requestion to the driver failed"
In-Reply-To: <1197589996.14897.6.camel@localhost.localdomain>
References: <476174A5.7080304@gmail.com>	
	<1197581250.14270.19.camel@localhost.localdomain>	
	<4761B266.9080205@gmail.com>
	<1197589996.14897.6.camel@localhost.localdomain>
Message-ID: <4761C7EE.8080905@gmail.com>

Dan Williams wrote:
> On Thu, 2007-12-13 at 17:29 -0500, Chase Douglas wrote:
>   
>> Dan Williams wrote:
>>     
>>> On Thu, 2007-12-13 at 13:06 -0500, Chase Douglas wrote:
>>>   
>>>       
>>>> Hello,
>>>>
>>>> I've got two IBM/Lenovo laptops, a t41p and a t60. Both have the Atheros 
>>>> 5212 wireless chips in them. Both have madwifi-ng-0.9.3.3 and 
>>>> wpa_supplicant-0.5.8. Both are configured to connect to my home WPA 
>>>> network using the same block:
>>>>
>>>> network={
>>>> 	priority=1
>>>> 	ssid="myssid"
>>>> 	psk="mypsk"
>>>> }
>>>>
>>>> However, the t60 can connect to the network while the t41p cannot. Under 
>>>> wpa_cli, the t41p prints:
>>>>
>>>> Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
>>>> Association requestion to the driver failed
>>>> Associated with <myroutermacaddr>
>>>> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>>>>     
>>>>         
>>> wpa_supplicant says that when the wpa_drv_associate() function returns
>>> an error code.  The most usual cause of that is that the driver does not
>>> support some of the parameters wpa_supplicant is try to set.  That's OK,
>>> it's normal that drivers don't support all of the ioctls.  And the
>>> association routine should just ignore those parameters that fail unless
>>> they really are fatal.
>>>
>>> So you'll need to get more debugging output about _what_ call failed to
>>> determine whether or not it's an important failure.  On Fedora we have a
>>> patch that prints out specifically which calls the driver does not
>>> support, which aids in debugging.
>>>
>>> Are you using the 'madwifi' driver or the 'wext' driver?  If you're
>>> using the madwifi driver, try the 'wext' driver instead.
>>>
>>> Dan
>>>       
>> I am using the madwifi driver. Which Atheros driver would use wext?
>>     
>
> madwifi will.  Try running wpa_supplicant with "-D wext" instead of "-D
> madwifi".
>
> dan
>   

Now, I get:

Trying to associate with <myroutermacaddr> (SSID='myssid' freq=myfreq)
Authentication with <myroutermacaddr> timed out.

Any ideas?





From raghavendra.akkasali  Thu Dec 13 17:17:29 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 14 Dec 2007 06:47:29 +0530
Subject: Doubt about WPA and WPA2
Message-ID: <58a444250712131717i2193809ej7ed5a55727a65f1e@mail.gmail.com>

Hi,

   I read some where that only WPA2 has capability to use AES/CCMP
encryption. But I saw few Access Points which provide an option to
configure WPA1 to use either of TKIP or CCMP/AES, can any body tell me
why?


They option to configure AP, with PSK-Mixed/WPA-Mixed/WPA2-Mixed, here
in all three cases user can configure encryption types as one of AES,
TKIP and (AES+TKIP), please tell what it means?

-- 
Regards & Thanks
Raghavendra. S



From raghavendra.akkasali  Thu Dec 13 17:37:23 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 14 Dec 2007 07:07:23 +0530
Subject: PAP and CHAP support
Message-ID: <58a444250712131737y150d392fxc6d35f6ed92b9d5a@mail.gmail.com>

Hi,

 Whether wpa supplicant supports PAP and CHAP? how it should be configured.?

 eap=TTLS
 phase2="auth=PAP auth=CHAP autheap=MSCHAPV2 autheap=MD5"

is above configuration correct? or i have to use autheap for PAP and CHAP.

-- 
Regards & Thanks
Raghavendra. S



From chasedouglas  Thu Dec 13 18:22:37 2007
From: chasedouglas (Chase Douglas)
Date: Thu, 13 Dec 2007 21:22:37 -0500
Subject: AR5212 "Association requestion to the driver failed"
In-Reply-To: <1197589996.14897.6.camel@localhost.localdomain>
References: <476174A5.7080304@gmail.com>	
	<1197581250.14270.19.camel@localhost.localdomain>	
	<4761B266.9080205@gmail.com>
	<1197589996.14897.6.camel@localhost.localdomain>
Message-ID: <4761E8ED.2020301@gmail.com>

Sorry for the spam I suppose, but I realized that I had limited the 
allowed clients by setting per-client psks. After adding in my new 
laptop everything worked. Again, sorry for the trouble, but thanks for 
your help!

-- Chase



From j  Thu Dec 13 19:31:49 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 19:31:49 -0800
Subject: PAP and CHAP support
In-Reply-To: <58a444250712131737y150d392fxc6d35f6ed92b9d5a@mail.gmail.com>
References: <58a444250712131737y150d392fxc6d35f6ed92b9d5a@mail.gmail.com>
Message-ID: <20071214033149.GT5698@jm.kir.nu>

On Fri, Dec 14, 2007 at 07:07:23AM +0530, Raghavendra. S wrote:

>  Whether wpa supplicant supports PAP and CHAP? how it should be configured.?

Yes, PAP and CHAP can be used as tunneled authentication methods with
EAP-TTLS.

>  eap=TTLS
>  phase2="auth=PAP auth=CHAP autheap=MSCHAPV2 autheap=MD5"
> 
> is above configuration correct? or i have to use autheap for PAP and CHAP.

You can only select one EAP-TTLS phase 2 method out of five options:
PAP, CHAP, MSCHAP, MSCHAPV2, and EAP since EAP-TTLS does not have a
negotiation for the used mechanism. However, EAP option (autheap) can
have multiple enabled EAP methods.

In other words, the configuration above would not result in all four
options being enabled. Instead, it would actually end up enabling just
EAP-MSCHAPv2 for phase 2. You could set phase2 parameter to "auth=PAP"
to enable PAP, to "auth=CHAP" to enable CHAP, and "autheap=MSCHAPV2 MD5"
to enable EAP with both EAP-MSCHAPv2 and EAP-MD5 allowed.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 19:34:42 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 19:34:42 -0800
Subject: Doubt about WPA and WPA2
In-Reply-To: <58a444250712131717i2193809ej7ed5a55727a65f1e@mail.gmail.com>
References: <58a444250712131717i2193809ej7ed5a55727a65f1e@mail.gmail.com>
Message-ID: <20071214033442.GU5698@jm.kir.nu>

On Fri, Dec 14, 2007 at 06:47:29AM +0530, Raghavendra. S wrote:

>    I read some where that only WPA2 has capability to use AES/CCMP
> encryption. But I saw few Access Points which provide an option to
> configure WPA1 to use either of TKIP or CCMP/AES, can any body tell me
> why?

Wi-Fi Alliance did not certify WPA with CCMP (this is only included in
WPA2 certification tests). However, it is possible to use CCMP with WPA
and many implementations support this configuration.

> They option to configure AP, with PSK-Mixed/WPA-Mixed/WPA2-Mixed, here
> in all three cases user can configure encryption types as one of AES,
> TKIP and (AES+TKIP), please tell what it means?

I'm not sure what the "Mixed" is referring to here, but as far as
encryption options are concerned, AES would mean enabling only CCMP,
TKIP would mean only TKIP, and AES+TKIP would mean that clients can
select to use either CCMP or TKIP for unicast packets (TKIP would be
used for multicast/broadcast).
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 19:38:07 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 19:38:07 -0800
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1197567363.8313.31.camel@johannes.berg>
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	<1197567363.8313.31.camel@johannes.berg>
Message-ID: <20071214033807.GV5698@jm.kir.nu>

On Thu, Dec 13, 2007 at 06:36:03PM +0100, Johannes Berg wrote:

> Not sure if I really want to, maybe we can convince Jouni to take
> patches early if they don't break anything else?

I'm fine with patches that are either specific to driver_devicescape.c
or are clearly not breaking other driver wrappers (or core hostapd
functionality) as long as they are somehow in sync with a commonly used
Linux kernel tree. At some point, I would like to limit this to proper
kernel releases, but for the time being, any development tree should be
fine taken into account the current state of the AP support.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 19:41:43 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 19:41:43 -0800
Subject: Ndiswrapper and virtual interfaces - WPA_supplicant can't
	associate
In-Reply-To: <e3a7b8140712120551y560d57d7h38f7727b13bb6b6f@mail.gmail.com>
References: <e3a7b8140712120548k1566d64bl575ae179bcf8e3a@mail.gmail.com>
	<e3a7b8140712120551y560d57d7h38f7727b13bb6b6f@mail.gmail.com>
Message-ID: <20071214034143.GW5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 03:51:27PM +0200, Dudy Kohen wrote:

> I have a TrendNET 421PC and a Prism2 based card.
> I use a Linksys WRT54GL 1.0 router with DD-WRT and a virtual interface
> using WPA. (another with WEP, but it's for WDS)
> Wpa_supplicant claims not to find the appropriate SSID although it
> shows it in the debug output.

That would probably be caused by a mismatch in security parameters.

> Tried the ap_scan option, it didn't work any better.

What do you mean with this? Did you try setting ap_scan=2 (required for
NDIS drivers when using hidden SSIDs and multi-SSID configuration) and
configuring key_mgmt, proto, pairwise, group to match with the AP
configuration (only one option allowed for each parameter in ap_scan=2
mode)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:05:01 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:05:01 -0800
Subject: Patch to build libeap.so
In-Reply-To: <475E93F3.4080006@deployingradius.com>
References: <475E93F3.4080006@deployingradius.com>
Message-ID: <20071214040501.GX5698@jm.kir.nu>

On Tue, Dec 11, 2007 at 02:43:15PM +0100, Alan DeKok wrote:
>   It adds a CONFIG_SOLIB parameter.  If set, it will build libeap.so
> rather than libeap.a.

Thanks! Applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:07:41 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:07:41 -0800
Subject: [PATCH] "interfaces" mispelt in comment of
	wpa_supplicant/wpa_supplicant.c
In-Reply-To: <200712102130.53208.kel@otaku42.de>
References: <200712102130.53208.kel@otaku42.de>
Message-ID: <20071214040741.GY5698@jm.kir.nu>

On Mon, Dec 10, 2007 at 09:30:53PM +1000, Kel Modderman wrote:
> Fix the spelling of "interfaces" (was "interdaces") in comment within
> wpa_supplicant/wpa_supplicant.c.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:33:10 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:33:10 -0800
Subject: [PATCH] hostapd: use wext's privacy_invoked instead of prism ioctl
In-Reply-To: <1197477024.6558.100.camel@johannes.berg>
References: <1197477024.6558.100.camel@johannes.berg>
Message-ID: <20071214043310.GZ5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 05:30:24PM +0100, Johannes Berg wrote:
> This patch changes driver_devicescape to use IW_AUTH_PRIVACY_INVOKED
> rather than PRISM2_PARAM_PRIVACY_INVOKED.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:36:36 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:36:36 -0800
Subject: [PATCH] hostapd: make driver_devicescape set multi-BSS
	interfaces up
In-Reply-To: <1197477351.6558.104.camel@johannes.berg>
References: <1197477351.6558.104.camel@johannes.berg>
Message-ID: <20071214043636.GA5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 05:35:51PM +0100, Johannes Berg wrote:
> It seems that I forgot this when converting the driver to nl80211, it should
> of course set IFF_UP on all secondary BSS interfaces as well. I will handle
> the MTU issue in a separate patch as this isn't really working right now
> anyway. Also note that in another forthcoming patch I will change it to
> receive EAPOL frames via the regular data interface. As I've noted before,
> this is also necessary for proper MAC address setting in multi-BSS
> scenarios.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:46:26 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:46:26 -0800
Subject: [PATCH] hostapd: allow bssid config on default interface
In-Reply-To: <1197477483.6558.108.camel@johannes.berg>
References: <1197477483.6558.108.camel@johannes.berg>
Message-ID: <20071214044626.GB5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 05:38:03PM +0100, Johannes Berg wrote:
> This patch makes hostapd accept bssid= on the default interface for
> those drivers that are changed to support it and changes
> driver_devicescape to support it. In order to support such a setting the
> driver must provide an init_bssid() in addition to the init() routine.

Thanks! Applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 13 20:59:09 2007
From: j (Jouni Malinen)
Date: Thu, 13 Dec 2007 20:59:09 -0800
Subject: [PATCH] fix memory leak in D-Bus control interface
In-Reply-To: <1197480068.13414.33.camel@localhost.localdomain>
References: <1197480068.13414.33.camel@localhost.localdomain>
Message-ID: <20071214045909.GD5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 12:21:08PM -0500, Dan Williams wrote:
> Be sure to unref the D-Bus message for the signal after sending it.
> 
> When backporting to 0.5.x, s/_signal/signal/g and it should apply.

Thanks! Applied to 0.6 and I will merge it into 0.5 before the next
release.
 
-- 
Jouni Malinen                                            PGP id EFC895FA



From johannes  Fri Dec 14 03:17:32 2007
From: johannes (Johannes Berg)
Date: Fri, 14 Dec 2007 12:17:32 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1197512614.6558.224.camel@johannes.berg>
	(sfid-20071213_113823_799536_82B49721)
References: <1197512614.6558.224.camel@johannes.berg>
	(sfid-20071213_113823_799536_82B49721)
Message-ID: <1197631052.16079.26.camel@johannes.berg>

>  * set_tx_queue_params

Actually, I wonder if any of that should be implemented in the wireless
classifier. Well, what I'm thinking is that we should make mac80211
provide multiqueue netdevs with four queues and then write a new 802.11
classifier that is attached in the sch_fifo qdisc. Then, the queue
parameters could be configured with the 802.11 qdisc.

Tomas, you said you might look into the QoS stuff, any ideas?

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


From johannes  Fri Dec 14 04:16:23 2007
From: johannes (Johannes Berg)
Date: Fri, 14 Dec 2007 13:16:23 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <20071214033807.GV5698@jm.kir.nu>
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	<1197567363.8313.31.camel@johannes.berg>
	<20071214033807.GV5698@jm.kir.nu>
Message-ID: <1197634583.16079.40.camel@johannes.berg>


> I'm fine with patches that are either specific to driver_devicescape.c
> or are clearly not breaking other driver wrappers (or core hostapd
> functionality) as long as they are somehow in sync with a commonly used
> Linux kernel tree. At some point, I would like to limit this to proper
> kernel releases, but for the time being, any development tree should be
> fine taken into account the current state of the AP support.

Great. I think all the remaining patches I have are specific to
driver_nl80211.c (I think I sent you the rename patch, didn't I?) I'll
send them to you as appropriate, I think the beaconing/station and eapol
stuff is pretty well fleshed out right now.

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


From johannes  Fri Dec 14 04:16:54 2007
From: johannes (Johannes Berg)
Date: Fri, 14 Dec 2007 13:16:54 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1ba2fa240712131525o6c0767e8je8a4feff21fbae69@mail.gmail.com>
	(sfid-20071213_232539_914393_6ACC0719)
References: <1197512614.6558.224.camel@johannes.berg>
	<1ba2fa240712130635n44838ac4s5bb606e5dc27fdeb@mail.gmail.com>
	<1197567415.8313.33.camel@johannes.berg>
	<1ba2fa240712131525o6c0767e8je8a4feff21fbae69@mail.gmail.com>
	(sfid-20071213_232539_914393_6ACC0719)
Message-ID: <1197634614.16079.42.camel@johannes.berg>


> > Oh btw, will you be publishing driver updates to support AP mode in
> > iwlwifi? You must have them anyway if you're working on this and I'd
> > love have a second driver capable of AP mode in the kernel.
> 
> We have frozen the AP stack before you've removed management interface

How's that relevant to the driver?

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


From tomasw  Fri Dec 14 06:13:45 2007
From: tomasw (Tomas Winkler)
Date: Fri, 14 Dec 2007 16:13:45 +0200
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1197631052.16079.26.camel@johannes.berg>
References: <1197512614.6558.224.camel@johannes.berg>
	<1197631052.16079.26.camel@johannes.berg>
Message-ID: <1ba2fa240712140613p59e1d9fsf214310d8d9a66fd@mail.gmail.com>

On Dec 14, 2007 1:17 PM, Johannes Berg <johannes at sipsolutions.net> wrote:
> >  * set_tx_queue_params
>
> Actually, I wonder if any of that should be implemented in the wireless
> classifier. Well, what I'm thinking is that we should make mac80211
> provide multiqueue netdevs with four queues and then write a new 802.11
> classifier that is attached in the sch_fifo qdisc. Then, the queue
> parameters could be configured with the 802.11 qdisc.
>
> Tomas, you said you might look into the QoS stuff, any ideas?
>
This is a bit more complicated then that
 In HT aggregation we have more then 4 queues. In theory you have TID
X receiving address queues. Number of TIDs is 16 yet for the
aggregation on 8 are relevant.Let say your AP supports 32 connected
stations so you need 256 queues for to keep packets in order. Of
course in HW you keep smaller number..etc.
Ron will send RX AMSDU aggregation patches at the beginning of the
next week, then he will work on TX side. I suggest that in that
context we can open the discussion how to solve the QoS queues and
Qdisc cleanly.

Tomas

> johannes
>



From johannes  Fri Dec 14 06:38:57 2007
From: johannes (Johannes Berg)
Date: Fri, 14 Dec 2007 15:38:57 +0100
Subject: [FYI] hostapd with mac80211 progress
In-Reply-To: <1ba2fa240712140613p59e1d9fsf214310d8d9a66fd@mail.gmail.com>
	(sfid-20071214_141352_383010_B40A3AB3)
References: <1197512614.6558.224.camel@johannes.berg>
	<1197631052.16079.26.camel@johannes.berg>
	<1ba2fa240712140613p59e1d9fsf214310d8d9a66fd@mail.gmail.com>
	(sfid-20071214_141352_383010_B40A3AB3)
Message-ID: <1197643137.16079.55.camel@johannes.berg>


> This is a bit more complicated then that
>  In HT aggregation we have more then 4 queues. In theory you have TID
> X receiving address queues. Number of TIDs is 16 yet for the
> aggregation on 8 are relevant.Let say your AP supports 32 connected
> stations so you need 256 queues for to keep packets in order. Of
> course in HW you keep smaller number..etc.

Hmm. I'm not too familiar with the 802.11e stuff that is really getting
used now in 802.11n

> Ron will send RX AMSDU aggregation patches at the beginning of the
> next week, then he will work on TX side. I suggest that in that
> context we can open the discussion how to solve the QoS queues and
> Qdisc cleanly.

Sounds good.

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


From migdalis.mago  Fri Dec 14 09:45:48 2007
From: migdalis.mago (Migdalis Mago)
Date: Fri, 14 Dec 2007 09:45:48 -0800 (PST)
Subject: Migdalis Mago quiere ser tu amigo en Sonico
Message-ID: <20071214174548.F356C113536@mail.iocaine.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071214/3320e205/attachment.htm 


From dimitrysh  Fri Dec 14 11:28:42 2007
From: dimitrysh (Dmitry Shmidt)
Date: Fri, 14 Dec 2007 11:28:42 -0800
Subject: WPA Supplicant doesn't send authentication request
Message-ID: <bc27201d0712141128y636d01fdxdae22ec1b4df80cf@mail.gmail.com>

Hello,

I am porting WPA Supplicant ver 0.5.8 to work with unsupported WiFi driver.
Driver doesn't have WEXT support.
It allows me to connect to "open" network but not to WEP.
According to WiFi sniffer Authentication request is not sent by the driver
to AP.
What can be the most probable reason for this ?
Log is attached.

?hanks,
Dmitry
------------------------------------------------------------------------------------------------------------------
Configuration file '/wpa_supplicant.conf' -> '/wpa_supplicant.conf'
Reading configuration file '/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 437 - start of a new network block
ssid - hexdump_ascii(len=16):
     4c 69 6e 6b 73 79 73 5f 53 45 53 5f 34 34 38 33   Linksys_SES_4483
key_mgmt: 0x4
auth_alg: 0x2
wep_key0 - hexdump(len=5): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 0
   id=0 ssid='Linksys_SES_4483'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Initializing CE-STA-DK 1.0 interface...
driver events socket is 0x7...
driver events socket is 0x8...
wpa_driver_get_mac_addr called
Own MAC address: 00:18:41:01:66:6b
wpa_driver_set_wpa called
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 0
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 1
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 2
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 3
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_countermeasures called
wpa_driver_set_drop_unencrypted called: 1 - not implemented
Setting scan request: 0 sec 100000 usec
Added interface wlan0
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to
speed up initial association
wpa_driver_get_scan_results called
Received 1170 bytes of scan results (10 BSSes)
Scan results: 10
Selecting BSS from priority group 0
4: 00:18:39:39:66:c2 ssid='Linksys_SES_4483' wpa_ie_len=0 rsn_ie_len=0
caps=0x411
   selected non-WPA AP 00:18:39:39:66:c2 ssid='Linksys_SES_4483'
Trying to associate with 00:18:39:39:66:c2 (SSID='Linksys_SES_4483'
freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
wpa_driver_set_auth_alg called
proto: 0
auth_alg: 2
auth_alg (AUTH_ALG_SHARED_KEY)
Selected Auth:os802_11AuthModeShared
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 0
add_key (alg): 1
add_key (set_tx): 1
add_key (seq): - hexdump(len=0):
add_key (key): - hexdump(len=5): 37 dd 5a 07 41
setting this key to be the index: 0x80000000
Adding WEP key index: 0x0
wpa_driver_set_drop_unencrypted called: 1 - not implemented
State: SCANNING -> ASSOCIATING
wpa_driver_associate called
setting os802_11Infrastructure mode...
BSSID=00:18:39:39:66:c2
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:18:39:39:66:c2 into blacklist
wpa_driver_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 0
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 1
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 2
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
wpa_driver_set_key called
add_key (addr): ff:ff:ff:ff:ff:ff
add_key (key_idx): 3
add_key (alg): 0
add_key (set_tx): 0
add_key (seq): - hexdump(len=0): [NULL]
add_key (key): - hexdump(len=0): [NULL]
State: ASSOCIATING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
wpa_driver_scan called
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071214/2ada577e/attachment.htm 


From dcbw  Fri Dec 14 11:40:06 2007
From: dcbw (Dan Williams)
Date: Fri, 14 Dec 2007 14:40:06 -0500
Subject: WPA Supplicant doesn't send authentication request
In-Reply-To: <bc27201d0712141128y636d01fdxdae22ec1b4df80cf@mail.gmail.com>
References: <bc27201d0712141128y636d01fdxdae22ec1b4df80cf@mail.gmail.com>
Message-ID: <1197661206.18469.16.camel@localhost.localdomain>

On Fri, 2007-12-14 at 11:28 -0800, Dmitry Shmidt wrote:
> Hello,
> 
> I am porting WPA Supplicant ver 0.5.8 to work with unsupported WiFi
> driver.
> Driver doesn't have WEXT support.
> It allows me to connect to "open" network but not to WEP.
> According to WiFi sniffer Authentication request is not sent by the
> driver to AP. 
> What can be the most probable reason for this ?
> Log is attached.

Well, wpa_supplicant itself doesn't send the authentication request.
The driver does.  Your custom wpa_supplicant driver should tell the
card's driver to trigger association at the end of the 'associate'
wpa_supplicant driver handler.  In WEXT, that usually happens when the
SSID or BSSID is set via SIOCSIWESSID or SIOCSIWBSSID.  Without seeing
your driver or your wpa_supplicant driver sources, it's impossible to
say exactly in your case.  But however the unsupported WiFi driver wants
to be told to associate is what you should be doing at the end of the
associate handler like wpa_driver_wext_associate() does.

Dan

> ?hanks,
> Dmitry
> ------------------------------------------------------------------------------------------------------------------
> Configuration file '/wpa_supplicant.conf' -> '/wpa_supplicant.conf'
> Reading configuration file '/wpa_supplicant.conf' 
> ctrl_interface='/var/run/wpa_supplicant'
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> Line: 437 - start of a new network block
> ssid - hexdump_ascii(len=16):
>      4c 69 6e 6b 73 79 73 5f 53 45 53 5f 34 34 38 33
> Linksys_SES_4483 
> key_mgmt: 0x4
> auth_alg: 0x2
> wep_key0 - hexdump(len=5): [REMOVED]
> wep_tx_keyidx=0 (0x0)
> Priority group 0
>    id=0 ssid='Linksys_SES_4483'
> Initializing interface (2) 'wlan0'
> EAPOL: SUPP_PAE entering state DISCONNECTED 
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0 
> Initializing CE-STA-DK 1.0 interface...
> driver events socket is 0x7...
> driver events socket is 0x8...
> wpa_driver_get_mac_addr called
> Own MAC address: 00:18:41:01:66:6b
> wpa_driver_set_wpa called
> wpa_driver_set_key called 
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 0
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 1
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff 
> add_key (key_idx): 2
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 3
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_countermeasures called
> wpa_driver_set_drop_unencrypted called: 1 - not implemented 
> Setting scan request: 0 sec 100000 usec
> Added interface wlan0
> State: DISCONNECTED -> SCANNING
> Starting AP scan (broadcast SSID)
> Trying to get current scan results first without requesting a new scan
> to speed up initial association 
> wpa_driver_get_scan_results called
> Received 1170 bytes of scan results (10 BSSes)
> Scan results: 10
> Selecting BSS from priority group 0
> 4: 00:18:39:39:66:c2 ssid='Linksys_SES_4483' wpa_ie_len=0 rsn_ie_len=0
> caps=0x411 
>    selected non-WPA AP 00:18:39:39:66:c2 ssid='Linksys_SES_4483'
> Trying to associate with 00:18:39:39:66:c2 (SSID='Linksys_SES_4483'
> freq=2437 MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE 
> Automatic auth_alg selection: 0x1
> Overriding auth_alg selection: 0x2
> wpa_driver_set_auth_alg called
> proto: 0
> auth_alg: 2
> auth_alg (AUTH_ALG_SHARED_KEY)
> Selected Auth:os802_11AuthModeShared
> WPA: clearing AP WPA IE 
> WPA: clearing AP RSN IE
> WPA: clearing own WPA/RSN IE
> No keys have been configured - skip key clearing
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 0
> add_key (alg): 1 
> add_key (set_tx): 1
> add_key (seq): - hexdump(len=0):
> add_key (key): - hexdump(len=5): 37 dd 5a 07 41
> setting this key to be the index: 0x80000000
> Adding WEP key index: 0x0
> wpa_driver_set_drop_unencrypted called: 1 - not implemented 
> State: SCANNING -> ASSOCIATING
> wpa_driver_associate called
> setting os802_11Infrastructure mode...
> BSSID=00:18:39:39:66:c2
> Setting authentication timeout: 10 sec 0 usec
> EAPOL: External notification - portControl=ForceAuthorized 
> Authentication with 00:00:00:00:00:00 timed out.
> Added BSSID 00:18:39:39:66:c2 into blacklist
> wpa_driver_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 0
> add_key (alg): 0
> add_key (set_tx): 0 
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 1
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 2
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL] 
> add_key (key): - hexdump(len=0): [NULL]
> wpa_driver_set_key called
> add_key (addr): ff:ff:ff:ff:ff:ff
> add_key (key_idx): 3
> add_key (alg): 0
> add_key (set_tx): 0
> add_key (seq): - hexdump(len=0): [NULL]
> add_key (key): - hexdump(len=0): [NULL]
> State: ASSOCIATING -> DISCONNECTED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Setting scan request: 0 sec 0 usec
> State: DISCONNECTED -> SCANNING 
> Starting AP scan (broadcast SSID)
> wpa_driver_scan called
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




From j  Fri Dec 14 18:51:22 2007
From: j (Jouni Malinen)
Date: Fri, 14 Dec 2007 18:51:22 -0800
Subject: How to set-up RADIUS server in hostapd
In-Reply-To: <475FC398.1050600@oneconvergence.com>
References: <475FC398.1050600@oneconvergence.com>
Message-ID: <20071215025122.GJ5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 04:48:48PM +0530, Jagadish wrote:

>       I am using hostapd-0.5.9. I want to use hostapd as RADIUS server. 
> For this I enabled CONFIG_EAP, CONFIG_EAP_TLS and CONFIG_RADIUS_SERVER 
> in .config file. It compiled successfully. But if I run it using 
> "hostapd hostapd.conf", it is giving segmentation fault.
> In hostapd.conf file, I added interface=wlan0. The coredump is showing 
> the following function as responsible for segmentation fault.
> ===================================================
> driver_lookup (name=0x8076f62 "default") at hostapd.c:1561
> 1561                     return p->ops;

You will need to include support for at least a single driver wrapper to
make this work. In case of using hostapd only as a RADIUS server, you
can use the test driver interface (add CONFIG_DRIVER_TEST=y into
.config).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Fri Dec 14 18:53:12 2007
From: j (Jouni Malinen)
Date: Fri, 14 Dec 2007 18:53:12 -0800
Subject: media disconnect event
In-Reply-To: <683e2de40712100622x2cb2a408p60f5373c0771cd6@mail.gmail.com>
References: <683e2de40712100622x2cb2a408p60f5373c0771cd6@mail.gmail.com>
Message-ID: <20071215025312.GK5698@jm.kir.nu>

On Mon, Dec 10, 2007 at 07:52:44PM +0530, Paresh Sawant wrote:

>           I'm running wpa_supplicant on Wind-XP with CONFIG_USE_NDISUIO
> defined. Ihave complied code in VS 2005. I see that
> "MSNdis_StatusMediaDisconnect" type of event is NOT notified to
> wpa_supplicant by WMI. I notice that "MSNdis_StatusMediaConnect" is notified
> by WMI and the event handler is invoked appropriately. But it fails for
> media_disconnect type. So in case of AP dissociates for some reason how can
> the wpa_supplicant know the state of the station is
> un-authenticated(state-1)?

Which NDIS driver are you using? I've seen Media Disconnect notification
to work fine with many cards. Do you see any WMI notifications for
disconnect (i.e., what exact do you mena with event handler failing)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Fri Dec 14 19:58:31 2007
From: j (Jouni Malinen)
Date: Fri, 14 Dec 2007 19:58:31 -0800
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <7293d610712131503s16597e4xfd8e53c488ed5ffc@mail.gmail.com>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
	<7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
	<7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>
	<7293d610712131218ifd7a40eu69b3ff17c6b06ee8@mail.gmail.com>
	<7293d610712131503s16597e4xfd8e53c488ed5ffc@mail.gmail.com>
Message-ID: <20071215035831.GL5698@jm.kir.nu>

On Thu, Dec 13, 2007 at 11:03:35PM +0000, Peter Savage wrote:
> ok.  i have managed to get this linux client to connect, however it seems
> very hit and miss.  suffice to say authentication does work.  but it may not
> hold the connection, or may not authenticate in the first place.  My speed
> also seems limited to 5.5Mb.  Also, the windows xp client can still connect
> without a problem.  very odd.  The connection dropped whilst i was writing
> this email too.

What is this Linux client (WLAN card/driver/etc.)? The debug log from
hostapd seemed to indicate that there were no replies from the client.
It is difficult to say what exactly is causing this based on that
information. Probably the best way to debug this would be to use a
wireless sniffer to capture the packets between the AP and the client
from a failed connection attempt if you happen to have a suitable device
for doing this.

-- 
Jouni Malinen                                            PGP id EFC895FA



From paresh.sawant  Fri Dec 14 20:32:05 2007
From: paresh.sawant (Paresh Sawant)
Date: Sat, 15 Dec 2007 10:02:05 +0530
Subject: media disconnect event
In-Reply-To: <20071215025312.GK5698@jm.kir.nu>
References: <683e2de40712100622x2cb2a408p60f5373c0771cd6@mail.gmail.com>
	<20071215025312.GK5698@jm.kir.nu>
Message-ID: <683e2de40712142032x416bcc3dvb47bac5f34d81ae1@mail.gmail.com>

I'm using NDIS 5.1 on Win XP.  I observe that after a successful association
station receives a connect event, and then if AP dissociates for some reason
before PMKSA or PTKSA finishes successfully, then the driver/card restarts
the association implicitly and station gets connect event  again, but there
is no disconnect event in between.

On Dec 15, 2007 8:23 AM, Jouni Malinen <j at w1.fi> wrote:

> On Mon, Dec 10, 2007 at 07:52:44PM +0530, Paresh Sawant wrote:
>
> >           I'm running wpa_supplicant on Wind-XP with CONFIG_USE_NDISUIO
> > defined. Ihave complied code in VS 2005. I see that
> > "MSNdis_StatusMediaDisconnect" type of event is NOT notified to
> > wpa_supplicant by WMI. I notice that "MSNdis_StatusMediaConnect" is
> notified
> > by WMI and the event handler is invoked appropriately. But it fails for
> > media_disconnect type. So in case of AP dissociates for some reason how
> can
> > the wpa_supplicant know the state of the station is
> > un-authenticated(state-1)?
>
> Which NDIS driver are you using? I've seen Media Disconnect notification
> to work fine with many cards. Do you see any WMI notifications for
> disconnect (i.e., what exact do you mena with event handler failing)?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071215/121ea742/attachment.htm 


From kohen.d  Sat Dec 15 04:11:56 2007
From: kohen.d (Dudy Kohen)
Date: Sat, 15 Dec 2007 14:11:56 +0200
Subject: Ndiswrapper and virtual interfaces - WPA_supplicant can't
	associate
Message-ID: <e3a7b8140712150411x152fca11q34a962606c144ec1@mail.gmail.com>

Thank you,
I set those parameters now and realized what the problem is...
with the card that works I get this output in debug mode:
0: 00:1a:XX:XX:XX:XX ssid='dd-wrt_wpa' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
with the one that doesn't work I get this:
0: 00:1a:XX:XX:XX:XX ssid='dd-wrt_wpa' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE

Any idea as to why?
Thanks again,
David
> Date: Thu, 13 Dec 2007 19:41:43 -0800
> From: Jouni Malinen <j at w1.fi>
> Subject: Re: Ndiswrapper and virtual interfaces - WPA_supplicant can't
>         associate
> To: hostap at shmoo.com
> Message-ID: <20071214034143.GW5698 at jm.kir.nu>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, Dec 12, 2007 at 03:51:27PM +0200, Dudy Kohen wrote:
>
> > I have a TrendNET 421PC and a Prism2 based card.
> > I use a Linksys WRT54GL 1.0 router with DD-WRT and a virtual interface
> > using WPA. (another with WEP, but it's for WDS)
> > Wpa_supplicant claims not to find the appropriate SSID although it
> > shows it in the debug output.
>
> That would probably be caused by a mismatch in security parameters.
>
> > Tried the ap_scan option, it didn't work any better.
>
> What do you mean with this? Did you try setting ap_scan=2 (required for
> NDIS drivers when using hidden SSIDs and multi-SSID configuration) and
> configuring key_mgmt, proto, pairwise, group to match with the AP
> configuration (only one option allowed for each parameter in ap_scan=2
> mode)?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>
>



From j  Sat Dec 15 07:36:14 2007
From: j (Jouni Malinen)
Date: Sat, 15 Dec 2007 07:36:14 -0800
Subject: Ndiswrapper and virtual interfaces - WPA_supplicant can't
	associate
In-Reply-To: <e3a7b8140712150411x152fca11q34a962606c144ec1@mail.gmail.com>
References: <e3a7b8140712150411x152fca11q34a962606c144ec1@mail.gmail.com>
Message-ID: <20071215153614.GM5698@jm.kir.nu>

On Sat, Dec 15, 2007 at 02:11:56PM +0200, Dudy Kohen wrote:

> I set those parameters now and realized what the problem is...
> with the card that works I get this output in debug mode:
> 0: 00:1a:XX:XX:XX:XX ssid='dd-wrt_wpa' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
>    selected based on WPA IE
> with the one that doesn't work I get this:
> 0: 00:1a:XX:XX:XX:XX ssid='dd-wrt_wpa' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> 
> Any idea as to why?

Use of hidden SSIDs (including this type of multi-SSID configuration) is
not defined in the IEEE 802.11 standard and can cause various issues
since some clients do not expect the Beacon frame and Probe Response
frames to use different information. You can usually get this working by
using ap_scan=2 mode (i.e., ask the driver to connect to the network
instead of ask it for scan results).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sat Dec 15 07:37:30 2007
From: j (Jouni Malinen)
Date: Sat, 15 Dec 2007 07:37:30 -0800
Subject: media disconnect event
In-Reply-To: <683e2de40712142032x416bcc3dvb47bac5f34d81ae1@mail.gmail.com>
References: <683e2de40712100622x2cb2a408p60f5373c0771cd6@mail.gmail.com>
	<20071215025312.GK5698@jm.kir.nu>
	<683e2de40712142032x416bcc3dvb47bac5f34d81ae1@mail.gmail.com>
Message-ID: <20071215153730.GN5698@jm.kir.nu>

On Sat, Dec 15, 2007 at 10:02:05AM +0530, Paresh Sawant wrote:
> I'm using NDIS 5.1 on Win XP.  I observe that after a successful association
> station receives a connect event, and then if AP dissociates for some reason
> before PMKSA or PTKSA finishes successfully, then the driver/card restarts
> the association implicitly and station gets connect event  again, but there
> is no disconnect event in between.

That sounds normal NDIS behavior. If the same SSID is still available
and the driver can re-associate quickly, it will not indicate Media
Disconnect between the associations.

-- 
Jouni Malinen                                            PGP id EFC895FA



From silentkeystroke  Sat Dec 15 08:21:50 2007
From: silentkeystroke (Peter Savage)
Date: Sat, 15 Dec 2007 16:21:50 +0000
Subject: Multiple clients on ath0 authentication failure
In-Reply-To: <20071215035831.GL5698@jm.kir.nu>
References: <7293d610712080936t395c208ek9fd1150e584f4505@mail.gmail.com>
	<20071208180418.GC5698@jm.kir.nu>
	<7293d610712121221n21688a03p399e5219df4ea38b@mail.gmail.com>
	<7293d610712121353t5ab7a2d3re7d99dc39e7828bc@mail.gmail.com>
	<7293d610712121404yceb95dfr73127b748560a6f5@mail.gmail.com>
	<7293d610712131218ifd7a40eu69b3ff17c6b06ee8@mail.gmail.com>
	<7293d610712131503s16597e4xfd8e53c488ed5ffc@mail.gmail.com>
	<20071215035831.GL5698@jm.kir.nu>
Message-ID: <7293d610712150821q1d23f11bl902c96e4c9824543@mail.gmail.com>

On 15/12/2007, Jouni Malinen <j at w1.fi> wrote:
>
> On Thu, Dec 13, 2007 at 11:03:35PM +0000, Peter Savage wrote:
> > ok.  i have managed to get this linux client to connect, however it
> seems
> > very hit and miss.  suffice to say authentication does work.  but it may
> not
> > hold the connection, or may not authenticate in the first place.  My
> speed
> > also seems limited to 5.5Mb.  Also, the windows xp client can still
> connect
> > without a problem.  very odd.  The connection dropped whilst i was
> writing
> > this email too.
>
> What is this Linux client (WLAN card/driver/etc.)? The debug log from
> hostapd seemed to indicate that there were no replies from the client.
> It is difficult to say what exactly is causing this based on that
> information. Probably the best way to debug this would be to use a
> wireless sniffer to capture the packets between the AP and the client
> from a failed connection attempt if you happen to have a suitable device
> for doing this.


I agree it's very odd.  The clients, a noka n800 and a hp laptop with a
netgear wg311 work fine with my main access point.  Sometimes they connect,
but it is very rare.  I will try to debug.  No more suggestions??  Does my
config look sound.  I see a few other people have had this problem, but
there seems to be no resolution.


-- 
Pete Savage - cbx33::silentk
wiki.ubuntu.com/PeteSavage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071215/6f22761a/attachment.htm 


From kel  Sun Dec 16 17:49:40 2007
From: kel (Kel Modderman)
Date: Mon, 17 Dec 2007 11:49:40 +1000
Subject: [PATCH] Allow logging to specific file with -F option
Message-ID: <200712171149.40842.kel@otaku42.de>

Hi,

(Re-sending this one, as it was not commented on in last patch frenzy.)

Logging to file was recently added, but the file path and name template
is hardcoded in wpa_debug_open_file(). This change adds an extra -F
command line option which allows specification of a specific output
filename to write debug output to.

wpa_debug_open_file() also prints an error message when the output file
failed to be opened for writing, and wpa_debug_close_file() does not
attempt to fclose the output file if it failed to be opened.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
diff --git a/src/utils/wpa_debug.c b/src/utils/wpa_debug.c
index b2f8c8b..7d3fff8 100644
--- a/src/utils/wpa_debug.c
+++ b/src/utils/wpa_debug.c
@@ -227,36 +227,42 @@ void wpa_hexdump_ascii_key(int level, const char *title, 
const u8 *buf,
 }
 
 
-int wpa_debug_open_file(void)
+int wpa_debug_open_file(const char *file)
 {
 #ifdef CONFIG_DEBUG_FILE
 	static int count = 0;
 	char fname[64];
 	if (!wpa_debug_use_file)
 		return 0;
+	if (file != NULL && out_file == NULL) {
+		out_file = fopen(file, "a");
+	} else {
 #ifdef _WIN32
-	os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
-		    count++);
+		os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
+			    count++);
 #else /* _WIN32 */
-	os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
-		    count++);
+		os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
+			    count++);
 #endif /* _WIN32 */
-	out_file = fopen(fname, "w");
+		out_file = fopen(fname, "w");
+	}
+	if (out_file == NULL) {
+		wpa_printf(MSG_ERROR, "wpa_debug_open_file: Failed to open output file, "
+			   "using standard output");
+		return -1;
+	}
 #ifndef _WIN32
-	if (out_file)
-		setvbuf(out_file, NULL, _IOLBF, 0);
+	setvbuf(out_file, NULL, _IOLBF, 0);
 #endif /* _WIN32 */
-	return out_file == NULL ? -1 : 0;
-#else /* CONFIG_DEBUG_FILE */
-	return 0;
 #endif /* CONFIG_DEBUG_FILE */
+	return 0;
 }
 
 
 void wpa_debug_close_file(void)
 {
 #ifdef CONFIG_DEBUG_FILE
-	if (!wpa_debug_use_file)
+	if (!wpa_debug_use_file || out_file == NULL)
 		return;
 	fclose(out_file);
 	out_file = NULL;
diff --git a/src/utils/wpa_debug.h b/src/utils/wpa_debug.h
index 9890945..8372cce 100644
--- a/src/utils/wpa_debug.h
+++ b/src/utils/wpa_debug.h
@@ -37,7 +37,7 @@ enum { MSG_MSGDUMP, MSG_DEBUG, MSG_INFO, MSG_WARNING, 
MSG_ERROR };
 
 #else /* CONFIG_NO_STDOUT_DEBUG */
 
-int wpa_debug_open_file(void);
+int wpa_debug_open_file(const char *file);
 void wpa_debug_close_file(void);
 
 /**
diff --git a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml 
b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
index 296e660..1c7234a 100644
--- a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
+++ b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
@@ -17,6 +17,7 @@
       <arg>-c<replaceable>config file</replaceable></arg>
       <arg>-D<replaceable>driver</replaceable></arg>
       <arg>-P<replaceable>PID_file</replaceable></arg>
+      <arg>-F<replaceable>output file</replaceable></arg>
     </cmdsynopsis>
   </refsynopsisdiv>
   <refsect1>
@@ -383,6 +384,13 @@
       </varlistentry>
 
       <varlistentry>
+	<term>-F output file</term>
+	<listitem>
+	  <para>Log output to specified file.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
 	<term>-g global ctrl_interface</term>
 	<listitem>
 	  <para>Path to global ctrl_interface socket.</para>
diff --git a/wpa_supplicant/main.c b/wpa_supplicant/main.c
index e5af13d..dc89a8d 100644
--- a/wpa_supplicant/main.c
+++ b/wpa_supplicant/main.c
@@ -40,7 +40,12 @@ static void usage(void)
 	printf("%s\n\n%s\n"
 	       "usage:\n"
 	       "  wpa_supplicant [-BddfhKLqqtuvwW] [-P<pid file>] "
-	       "[-g<global ctrl>] \\\n"
+	       "[-g<global ctrl>]"
+#ifdef CONFIG_DEBUG_FILE
+	       " [-F<output file>] \\\n"
+#else /* CONFIG_DEBUG_FILE */
+	       " \\\n"
+#endif /* CONFIG_DEBUG_FILE */
 	       "        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] "
 	       "[-p<driver_param>] \\\n"
 	       "        [-b<br_ifname> [-N -i<ifname> -c<conf> [-C<ctrl>] "
@@ -67,6 +72,7 @@ static void usage(void)
 	       "  -D = driver name\n"
 #ifdef CONFIG_DEBUG_FILE
 	       "  -f = Log output to default log location (normally /tmp)\n"
+	       "  -F = Log output to specified file\n"
 #endif /* CONFIG_DEBUG_FILE */
 	       "  -g = global ctrl_interface\n"
 	       "  -K = include keys (passwords, etc.) in debug output\n"
@@ -146,7 +152,7 @@ int main(int argc, char *argv[])
 	wpa_supplicant_fd_workaround();
 
 	for (;;) {
-		c = getopt(argc, argv, "b:Bc:C:D:dfg:hi:KLNp:P:qtuvwW");
+		c = getopt(argc, argv, "b:Bc:C:D:dF:fg:hi:KLNp:P:qtuvwW");
 		if (c < 0)
 			break;
 		switch (c) {
@@ -179,6 +185,10 @@ int main(int argc, char *argv[])
 		case 'f':
 			params.wpa_debug_use_file = 1;
 			break;
+		case 'F':
+			params.wpa_debug_use_file = 1;
+			params.wpa_debug_file = optarg;
+			break;
 #endif /* CONFIG_DEBUG_FILE */
 		case 'g':
 			params.ctrl_interface = optarg;
diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
index 0c1a142..bcae686 100644
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -1828,7 +1828,7 @@ struct wpa_global * wpa_supplicant_init(struct 
wpa_params *params)
 		return NULL;
 
 	wpa_debug_use_file = params->wpa_debug_use_file;
-	wpa_debug_open_file();
+	wpa_debug_open_file(params->wpa_debug_file);
 
 	ret = eap_peer_register_methods();
 	if (ret) {
diff --git a/wpa_supplicant/wpa_supplicant_i.h 
b/wpa_supplicant/wpa_supplicant_i.h
index 00e3162..f741244 100644
--- a/wpa_supplicant/wpa_supplicant_i.h
+++ b/wpa_supplicant/wpa_supplicant_i.h
@@ -154,6 +154,11 @@ struct wpa_params {
 	 * wpa_debug_use_file - Write debug to a file (instead of stdout)
 	 */
 	int wpa_debug_use_file;
+
+	/**
+	 * wpa_debug_file - Write debug to specified file.
+	 */
+	char *wpa_debug_file;
 };
 
 /**
-- 
1.5.3.7




From raghavendra.akkasali  Sun Dec 16 18:08:05 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 17 Dec 2007 07:38:05 +0530
Subject: When will wpa supplicant 0.6.0 stable version get released?
Message-ID: <58a444250712161808l1fe218ceq6efd9f3a6b06812f@mail.gmail.com>

Hi,

  Can any body tell me when will 0.6.0 stable version will get
realeased. Also can I start using 0.6.0 in my device? Whether its
going to harm in some way. or its better to wait for stable version
release.

-- 
Regards & Thanks
Raghavendra. S



From j  Sun Dec 16 18:44:55 2007
From: j (Jouni Malinen)
Date: Sun, 16 Dec 2007 18:44:55 -0800
Subject: When will wpa supplicant 0.6.0 stable version get released?
In-Reply-To: <58a444250712161808l1fe218ceq6efd9f3a6b06812f@mail.gmail.com>
References: <58a444250712161808l1fe218ceq6efd9f3a6b06812f@mail.gmail.com>
Message-ID: <20071217024455.GT5698@jm.kir.nu>

On Mon, Dec 17, 2007 at 07:38:05AM +0530, Raghavendra. S wrote:

>   Can any body tell me when will 0.6.0 stable version will get
> realeased.

0.6.0 will never be released as a stable version, but some later 0.6.x
version will (or well, maybe it will end up being renumbered to 1.0.0 at
that point, but anyway). However, I do not have a good estimate on when
this would happen. In theory, I would like to get this released soon,
but in practice, there is still number of open cleanup tasks that I
would prefer to get into bit more complete state before declaring 0.6.x
stable (which would also mean locking down many of the APIs and prevent
the planned cleanups in this branch).

> Also can I start using 0.6.0 in my device? Whether its
> going to harm in some way. or its better to wait for stable version
> release.

That's something that you will need to decide for yourself depending on
the exact requirements of the project. I'm using 0.6.x versions in my
daily use without any problems and I think that some Linux distributions
are also using something from 0.6.x branch.

If you want to play things safe and be more conservative, the latest
stable branch may be the best choice. However, if you need some new
features that are only available from the development branch, you may
have to consider using the development branch (or be prepared to
backport some of the features to an older branch).

In general, I expect wpa_supplicant development branch to be suitable
for general use all the time since my policy is not to commit partial
changes there. The main reason for having a separate development branch
is in having no limits on what kind of cleanup can be done. For example,
I just changed one of the internal APIs (EAP method interface) that
resulted in huge number of small changes throughout the code. This is
something that I won't be doing in stable branches, but still, the
change itself is not expected to bring much instability from the view
point of just using wpa_supplicant binary.

The main "instability" comes from the view point of maintaining external
changes. This is going to be very much more work if done against a
development branch.

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Sun Dec 16 19:21:54 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 17 Dec 2007 08:51:54 +0530
Subject: When will wpa supplicant 0.6.0 stable version get released?
In-Reply-To: <20071217024455.GT5698@jm.kir.nu>
References: <58a444250712161808l1fe218ceq6efd9f3a6b06812f@mail.gmail.com>
	<20071217024455.GT5698@jm.kir.nu>
Message-ID: <58a444250712161921j19627e18v41c52a6ad884010b@mail.gmail.com>

On 12/17/07, Jouni Malinen <j at w1.fi> wrote:
> On Mon, Dec 17, 2007 at 07:38:05AM +0530, Raghavendra. S wrote:
>
> >   Can any body tell me when will 0.6.0 stable version will get
> > realeased.
>
> 0.6.0 will never be released as a stable version, but some later 0.6.x
> version will (or well, maybe it will end up being renumbered to 1.0.0 at
> that point, but anyway). However, I do not have a good estimate on when
> this would happen. In theory, I would like to get this released soon,
> but in practice, there is still number of open cleanup tasks that I
> would prefer to get into bit more complete state before declaring 0.6.x
> stable (which would also mean locking down many of the APIs and prevent
> the planned cleanups in this branch).
>
> > Also can I start using 0.6.0 in my device? Whether its
> > going to harm in some way. or its better to wait for stable version
> > release.
>
> That's something that you will need to decide for yourself depending on
> the exact requirements of the project. I'm using 0.6.x versions in my
> daily use without any problems and I think that some Linux distributions
> are also using something from 0.6.x branch.
>
> If you want to play things safe and be more conservative, the latest
> stable branch may be the best choice. However, if you need some new
> features that are only available from the development branch, you may
> have to consider using the development branch (or be prepared to
> backport some of the features to an older branch).
>
> In general, I expect wpa_supplicant development branch to be suitable
> for general use all the time since my policy is not to commit partial
> changes there. The main reason for having a separate development branch
> is in having no limits on what kind of cleanup can be done. For example,
> I just changed one of the internal APIs (EAP method interface) that
> resulted in huge number of small changes throughout the code. This is
> something that I won't be doing in stable branches, but still, the
> change itself is not expected to bring much instability from the view
> point of just using wpa_supplicant binary.


  I need to provide support for Adhoc network creation and Adhoc
connection. Some time back Dan Williams has replied me that these are
not supported in version 0.5.x. So I am planning to use 0.6.x..I am
not very particular about using 0.6.0. Can you suggest me which of
0.6.x version is safe to use.

 Also I am planning to modify wpa_cli, as thread and will use in my
product, Is there any Licensing issue involved? I am not modifying
wpa_supplicant binary.


>
> The main "instability" comes from the view point of maintaining external
> changes. This is going to be very much more work if done against a
> development branch.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>


-- 
Regards & Thanks
Raghavendra. S



From j  Sun Dec 16 19:45:36 2007
From: j (Jouni Malinen)
Date: Sun, 16 Dec 2007 19:45:36 -0800
Subject: When will wpa supplicant 0.6.0 stable version get released?
In-Reply-To: <58a444250712161921j19627e18v41c52a6ad884010b@mail.gmail.com>
References: <58a444250712161808l1fe218ceq6efd9f3a6b06812f@mail.gmail.com>
	<20071217024455.GT5698@jm.kir.nu>
	<58a444250712161921j19627e18v41c52a6ad884010b@mail.gmail.com>
Message-ID: <20071217034536.GU5698@jm.kir.nu>

On Mon, Dec 17, 2007 at 08:51:54AM +0530, Raghavendra. S wrote:

>   I need to provide support for Adhoc network creation and Adhoc
> connection. Some time back Dan Williams has replied me that these are
> not supported in version 0.5.x. So I am planning to use 0.6.x..I am
> not very particular about using 0.6.0. Can you suggest me which of
> 0.6.x version is safe to use.

As far as the development branch is concerned, there are no particularly
testing releases and I would use the latest snapshot of the Git tree..
However, if the adhoc network configuration is the only reason for using
0.6.x, I would consider using the stable 0.5.x branch and just
backporting whatever minimal changes are needed for adhoc, if any,
depending on your needs.

>  Also I am planning to modify wpa_cli, as thread and will use in my
> product, Is there any Licensing issue involved? I am not modifying
> wpa_supplicant binary.

wpa_cli is licensed with the same terms as wpa_supplicant, i.e., using
GPLv2 or BSD (the one without so called advertisement clause). Just like
with any other piece of software (well, maybe apart from public domain),
one should be aware of the licensing terms when considering distributing
modified versions. Anyway, I would not expect to see any problems in
being able to meet the requirements of the BSD-like license that you may
opt to use for distributing your modified version.

-- 
Jouni Malinen                                            PGP id EFC895FA



From dave  Mon Dec 17 10:06:19 2007
From: dave (Dave Hansen)
Date: Mon, 17 Dec 2007 10:06:19 -0800
Subject: wpasupplicant and multiple/hidden SSIDs
In-Reply-To: <1197073467.4563.17.camel@localhost.localdomain>
References: <1197053258.6207.46.camel@localhost>
	<1197054756.4465.4.camel@localhost.localdomain>
	<1197055880.6207.55.camel@localhost>
	<1197071835.4563.0.camel@localhost.localdomain>
	<1197072557.6207.106.camel@localhost>
	<1197073467.4563.17.camel@localhost.localdomain>
Message-ID: <1197914779.5385.18.camel@localhost>

On Fri, 2007-12-07 at 19:24 -0500, Dan Williams wrote:
> On Fri, 2007-12-07 at 16:09 -0800, Dave Hansen wrote:
> > On Fri, 2007-12-07 at 18:57 -0500, Dan Williams wrote:
> > > > The problem is that I don't think the scan_ssid=1 logic comes into
> > > play
> > > > until it finds an explicitly hidden ssid.  In my case, I think
> > > > wpasupplicant looks around and sees the ~10 "VISITOR" access points,
> > > > notes that it doesn't have any config entries for them, then
> > > promptly
> > > > ignores them. :(
> > > 
> > > You've tried scan_ssid=1 + ap_scan=1 already I take it?
> > 
> > Yeah, wpasupplicant doesn't try to associate because it sees that the
> > scan_ssid=1 network is a WPA network, yet the APs don't advertise WPA.
> 
> That's odd, because it should be sending out a probe request anyway,
> getting the probe response with the IE back, and updating it's scan
> table.  At least, that's the way it's reasonable to expect that it would
> work.  I wouldn't expect it to ignore the scan_ssid=1 just because the
> network block doesn't match, because then what's the point of the
> scan_ssid=1 anyway...
> 
> I assume you're not specifying the BSSID in the network block?

Sorry for the delay.  I've been too lazy to actually trouble myself to
drive into the office. :)

Here's exactly what I have:

ap_scan=1
network={ 
        scan_ssid=1
        ssid="FOO"
        key_mgmt=IEEE8021X
        eap=LEAP
        identity="user"
        password="pass"
        priority=7
}
plus a few other networks...

Here's some output from -d with wpasupplicant:

ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0' (DEPRECATED)
ap_scan=1
fast_reauth=1
Priority group 7
   id=0 ssid='IBM'
Priority group 6
   id=3 ssid='Jella'
Priority group 5
   id=1 ssid='Commodore'
   id=2 ssid='GROOMLAKE'
....
EAPOL: External notification - portValid=0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=3):
     49 42 4d                                          IBM             
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 1123 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 7
0: 00:12:44:b8:f8:40 ssid='IBMVISITOR' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
1: 00:12:44:b8:fc:80 ssid='IBMVISITOR' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
2: 00:12:44:b8:fc:c0 ssid='IBMVISITOR' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
3: 00:12:44:b9:00:30 ssid='IBMVISITOR' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
4: 00:12:44:b8:fc:b0 ssid='IBMVISITOR' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE

I'd be happy to send you the entire -d output if it helps.

One odd thing that I've noticed is that the card comes back after
wpasupplicant associated with IBMVISITOR.  I run wpasupplicant like
this:

	 iwconfig eth1 essid any; ./wpa_supplicant -c /root/wpa_supplicant.conf -i eth1 -Dwext   -d 

and it always comes back like this:

eth1      IEEE 802.11g  ESSID:"IBMVISITOR"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:12:44:B8:FC:B0   
          Bit Rate:54 Mb/s   Tx-Power=20 dBm   Sensitivity=8/0  
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=67/100  Signal level=-60 dBm  Noise level=-85 dBm
          Rx invalid nwid:0  Rx invalid crypt:1339  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:1950   Missed beacon:0


-- Dave




From ken  Mon Dec 17 10:45:07 2007
From: ken (Ken Roberts)
Date: Mon, 17 Dec 2007 10:45:07 -0800
Subject: hostapd memory leak when connecting to Linux wpa_supplicant
Message-ID: <4766C3B3.4030208@glaserelectronics.com>

hostapd v0.5.8
wpa_supplicant v0.5.8
madwifi v0.9.3.3
kernel 2.6.21.5 <http://2.6.21.5> (recompiled for minimal drivers)

I've got 2 geode machines using the madwifi drivers. They worked great 
for about a week. Unfortunately, hostapd started eating ram and causing 
"out of memory and no programs to kill" errors on the ap running hostapd.

When a windows client connected to hostapd ap, there were no problems 
and no memory leaks.

When connecting to a Linux machine running wpa_supplicant, free ram 
started dropping like a rock until "out of memory" condition caused a 
system freeze.


Following are the config files I used:

======= hostapd.conf ============
# root at host:/# hostapd /<path-to>/hostapd.conf

# wpa_conf_hostapd.test
#
# Basic hostapd control stuff
#
# country_code=US     # Default
logger_syslog=1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/mnt/rd/hostapd.dump
ctrl_interface=/mnt/rd/hostapd
ctrl_interface_group=0
auth_algs=3
ignore_broadcast_ssid=0
ap_max_inactivity=900
max_num_sta=5
eapol_version=1
#
# Interface information
#
driver=madwifi
ssid=kens_bridge
interface=ath0
bridge=br0
wpa=3    # 1=WPA 2=IEEE802.11i/RSN (WPA2) 3=both
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
wpa_psk={wpa key}
#wpa_phrase='{wpa passphrase}'


======= wpa_supplicant.conf =======
root at host:/# wpa_supplicant -b br0 -i ath0 -c 
/<path-to>/wpa_supplicant.conf

# wpa_conf_hostapd.test
#
# Basic hostapd control stuff
#
# country_code=US     # Default
logger_syslog=1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/mnt/rd/hostapd.dump
ctrl_interface=/mnt/rd/hostapd
ctrl_interface_group=0
auth_algs=3
ignore_broadcast_ssid=0
ap_max_inactivity=900
max_num_sta=5
eapol_version=1
#
# Interface information
#
driver=madwifi
ssid=kens_bridge
interface=ath0
bridge=br0
wpa=3    # 1=WPA 2=IEEE802.11i/RSN (WPA2) 3=both
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
wpa_psk={wpa key}
#wpa_phrase='{wpa passphrase}'



From Proger  Mon Dec 17 12:44:39 2007
From: Proger (Proger at web.de)
Date: Mon, 17 Dec 2007 21:44:39 +0100
Subject: 802.11i support in IBSS mode
Message-ID: <695989561@web.de>

Hi Nicolas,

I also currently working on a future implementation of 802.11i for IBSS mode. First implementation step I'm already finished is is to compile the test_wpa example.
For this I modified the make file in line 936 as follows:
# test_wpa: $(OBJS_wpa) $(OBJS_h)
#	$(LDO) $(LDFLAGS) -o test_wpa $(OBJS_wpa) $(LIBS)
test_wpa: $(OBJS) $(OBJS_h)
	$(LDO) $(LDFLAGS) -o test_wpa $(OBJS) $(LIBS)

Now I'm working on step 2 and step 3 as Jouni described earlier. So it will be nice if we could coordnate us and realise this task much quicker.
Further it will be nice if somebody have some addional hints for me which help us to realise this task.

Regards,
  Christian
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066




From raghavendra.akkasali  Mon Dec 17 17:52:32 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 07:22:32 +0530
Subject: WEP-shared is failing...
Message-ID: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>

Hi All,

 I tried to test wpa supplicant for auth_alg=SHARED, but failing to
connect with AP,
My supplicant.conf file configuration is all below.

----------------------start------------------------------------------------------------------

ctrl_interface=/var/run/wpa_supplicant

network={
        ssid="3Com"
        key_mgmt=NONE
        auth_alg=SHARED
        wep_key0="raghu123456"
        wep_tx_keyidx=0
}
----------------------end-------------------------------------------------------------------

I got following failure logs,

# ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file './files/wpa_supplicant.sharedWEP' ->
'/mnt/nfs/./files/wpa_supplicant.sharedWEP'
Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=4):
     33 43 6f 6d                                       3Com
key_mgmt: 0x4
auth_alg: 0x2
wep_key0 - hexdump(len=11): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 0
   id=0 ssid='3Com'
Initializing interface (2) 'eth0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: Invalid argument
SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:13:e0:9e:9b:2e
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface eth0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan
to speed up initial association
Received 416 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
   skip - no WPA/RSN IE
3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
   skip - no WPA/RSN IE
4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
ioctl[SIOCSIWFREQ]: Operation not supported
ioctl[SIOCSIWESSID]: Network is unreachable
ioctl[SIOCSIWAP]: Network is unreachable
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:0f:cb:fe:2f:5f into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
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
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 416 bytes of scan results (5 BSSes)
Scan results: 5
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
   skip - no WPA/RSN IE
3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
   skip - no WPA/RSN IE
4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
ioctl[SIOCSIWFREQ]: Operation not supported
ioctl[SIOCSIWESSID]: Network is unreachable
ioctl[SIOCSIWAP]: Network is unreachable
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0


Please tell me why it is failing?


-- 
Regards & Thanks
Raghavendra. S



From dcbw  Mon Dec 17 17:59:33 2007
From: dcbw (Dan Williams)
Date: Mon, 17 Dec 2007 20:59:33 -0500
Subject: WEP-shared is failing...
In-Reply-To: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
Message-ID: <1197943173.4733.0.camel@localhost.localdomain>

On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> Hi All,
> 
>  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> connect with AP,
> My supplicant.conf file configuration is all below.
> 
> ----------------------start------------------------------------------------------------------
> 
> ctrl_interface=/var/run/wpa_supplicant
> 
> network={
>         ssid="3Com"
>         key_mgmt=NONE
>         auth_alg=SHARED
>         wep_key0="raghu123456"

Are you trying to use a WEP passphrase here?  I don't think
wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
instead.

Dan


>         wep_tx_keyidx=0
> }
> ----------------------end-------------------------------------------------------------------
> 
> I got following failure logs,
> 
> # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> Configuration file './files/wpa_supplicant.sharedWEP' ->
> '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> ctrl_interface='/var/run/wpa_supplicant'
> Line: 4 - start of a new network block
> ssid - hexdump_ascii(len=4):
>      33 43 6f 6d                                       3Com
> key_mgmt: 0x4
> auth_alg: 0x2
> wep_key0 - hexdump(len=11): [REMOVED]
> wep_tx_keyidx=0 (0x0)
> Priority group 0
>    id=0 ssid='3Com'
> Initializing interface (2) 'eth0'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> ioctl[SIOCSIWPMKSA]: Invalid argument
> SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
>   capabilities: key_mgmt 0x0 enc 0x3
> WEXT: Operstate: linkmode=1, operstate=5
> Own MAC address: 00:13:e0:9e:9b:2e
> wpa_driver_wext_set_wpa
> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_countermeasures
> wpa_driver_wext_set_drop_unencrypted
> Setting scan request: 0 sec 100000 usec
> Added interface eth0
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b06 len=8
> State: DISCONNECTED -> SCANNING
> Starting AP scan (broadcast SSID)
> Trying to get current scan results first without requesting a new scan
> to speed up initial association
> Received 416 bytes of scan results (5 BSSes)
> Scan results: 5
> Selecting BSS from priority group 0
> Try to find WPA-enabled AP
> 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
>    skip - no WPA/RSN IE
> 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
>    skip - no WPA/RSN IE
> 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
>    skip - no WPA/RSN IE
> Try to find non-WPA AP
> 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - SSID mismatch
> 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE
> Automatic auth_alg selection: 0x1
> Overriding auth_alg selection: 0x2
> WPA: clearing AP WPA IE
> WPA: clearing AP RSN IE
> WPA: clearing own WPA/RSN IE
> No keys have been configured - skip key clearing
> wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> wpa_driver_wext_set_drop_unencrypted
> State: SCANNING -> ASSOCIATING
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> wpa_driver_wext_associate
> ioctl[SIOCSIWFREQ]: Operation not supported
> ioctl[SIOCSIWESSID]: Network is unreachable
> ioctl[SIOCSIWAP]: Network is unreachable
> Association request to the driver failed
> Setting authentication timeout: 5 sec 0 usec
> EAPOL: External notification - portControl=ForceAuthorized
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b06 len=8
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> State: ASSOCIATING -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> Added BSSID 00:00:00:00:00:00 into blacklist
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> State: DISCONNECTED -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Authentication with 00:00:00:00:00:00 timed out.
> BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> 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
> State: DISCONNECTED -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Setting scan request: 0 sec 0 usec
> State: DISCONNECTED -> SCANNING
> Starting AP scan (broadcast SSID)
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b19 len=8
> Received 416 bytes of scan results (5 BSSes)
> Scan results: 5
> Selecting BSS from priority group 0
> Try to find WPA-enabled AP
> 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - no WPA/RSN IE
> 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
>    skip - no WPA/RSN IE
> 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
>    skip - no WPA/RSN IE
> 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
>    skip - no WPA/RSN IE
> Try to find non-WPA AP
> 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    skip - SSID mismatch
> 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
>    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> Cancelling scan request
> WPA: clearing own WPA/RSN IE
> Automatic auth_alg selection: 0x1
> Overriding auth_alg selection: 0x2
> WPA: clearing AP WPA IE
> WPA: clearing AP RSN IE
> WPA: clearing own WPA/RSN IE
> No keys have been configured - skip key clearing
> wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> wpa_driver_wext_set_drop_unencrypted
> State: SCANNING -> ASSOCIATING
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> wpa_driver_wext_associate
> ioctl[SIOCSIWFREQ]: Operation not supported
> ioctl[SIOCSIWESSID]: Network is unreachable
> ioctl[SIOCSIWAP]: Network is unreachable
> Association request to the driver failed
> Setting authentication timeout: 5 sec 0 usec
> EAPOL: External notification - portControl=ForceAuthorized
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b06 len=8
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> State: ASSOCIATING -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:00:00:00:00:00
> BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> State: DISCONNECTED -> DISCONNECTED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> 
> 
> Please tell me why it is failing?
> 
> 




From raghavendra.akkasali  Mon Dec 17 18:10:35 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 07:40:35 +0530
Subject: WEP-shared is failing...
In-Reply-To: <1197943173.4733.0.camel@localhost.localdomain>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
Message-ID: <58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>

Hi,

  Tried with hex key...still failing...
----------------------------------------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1

network={
        ssid="3Com"
        key_mgmt=NONE
        wep_key0=76F6B7657D
        wep_tx_keyidx=0
        auth_alg=SHARED
}
----------------------------------------------------------------------------------------

if you see below log...i have following three lines...

ioctl[SIOCSIWFREQ]: Operation not supported
ioctl[SIOCSIWESSID]: Network is unreachable
ioctl[SIOCSIWAP]: Network is unreachable

is this a problem..or some thing else?





On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > Hi All,
> >
> >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > connect with AP,
> > My supplicant.conf file configuration is all below.
> >
> > ----------------------start------------------------------------------------------------------
> >
> > ctrl_interface=/var/run/wpa_supplicant
> >
> > network={
> >         ssid="3Com"
> >         key_mgmt=NONE
> >         auth_alg=SHARED
> >         wep_key0="raghu123456"
>
> Are you trying to use a WEP passphrase here?  I don't think
> wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> instead.
>
> Dan
>
>
> >         wep_tx_keyidx=0
> > }
> > ----------------------end-------------------------------------------------------------------
> >
> > I got following failure logs,
> >
> > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > ctrl_interface='/var/run/wpa_supplicant'
> > Line: 4 - start of a new network block
> > ssid - hexdump_ascii(len=4):
> >      33 43 6f 6d                                       3Com
> > key_mgmt: 0x4
> > auth_alg: 0x2
> > wep_key0 - hexdump(len=11): [REMOVED]
> > wep_tx_keyidx=0 (0x0)
> > Priority group 0
> >    id=0 ssid='3Com'
> > Initializing interface (2) 'eth0'
> > EAPOL: SUPP_PAE entering state DISCONNECTED
> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > EAPOL: SUPP_BE entering state INITIALIZE
> > EAP: EAP entering state DISABLED
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > ioctl[SIOCSIWPMKSA]: Invalid argument
> > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> >   capabilities: key_mgmt 0x0 enc 0x3
> > WEXT: Operstate: linkmode=1, operstate=5
> > Own MAC address: 00:13:e0:9e:9b:2e
> > wpa_driver_wext_set_wpa
> > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_countermeasures
> > wpa_driver_wext_set_drop_unencrypted
> > Setting scan request: 0 sec 100000 usec
> > Added interface eth0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (broadcast SSID)
> > Trying to get current scan results first without requesting a new scan
> > to speed up initial association
> > Received 416 bytes of scan results (5 BSSes)
> > Scan results: 5
> > Selecting BSS from priority group 0
> > Try to find WPA-enabled AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> >    skip - no WPA/RSN IE
> > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> >    skip - no WPA/RSN IE
> > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> >    skip - no WPA/RSN IE
> > Try to find non-WPA AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - SSID mismatch
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > Overriding auth_alg selection: 0x2
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > No keys have been configured - skip key clearing
> > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > wpa_driver_wext_set_drop_unencrypted
> > State: SCANNING -> ASSOCIATING
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > wpa_driver_wext_associate
> > ioctl[SIOCSIWFREQ]: Operation not supported
> > ioctl[SIOCSIWESSID]: Network is unreachable
> > ioctl[SIOCSIWAP]: Network is unreachable
> > Association request to the driver failed
> > Setting authentication timeout: 5 sec 0 usec
> > EAPOL: External notification - portControl=ForceAuthorized
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: ASSOCIATING -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > Added BSSID 00:00:00:00:00:00 into blacklist
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > Authentication with 00:00:00:00:00:00 timed out.
> > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > 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
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > Setting scan request: 0 sec 0 usec
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (broadcast SSID)
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b19 len=8
> > Received 416 bytes of scan results (5 BSSes)
> > Scan results: 5
> > Selecting BSS from priority group 0
> > Try to find WPA-enabled AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> >    skip - no WPA/RSN IE
> > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> >    skip - no WPA/RSN IE
> > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> >    skip - no WPA/RSN IE
> > Try to find non-WPA AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - SSID mismatch
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > Overriding auth_alg selection: 0x2
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > No keys have been configured - skip key clearing
> > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > wpa_driver_wext_set_drop_unencrypted
> > State: SCANNING -> ASSOCIATING
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > wpa_driver_wext_associate
> > ioctl[SIOCSIWFREQ]: Operation not supported
> > ioctl[SIOCSIWESSID]: Network is unreachable
> > ioctl[SIOCSIWAP]: Network is unreachable
> > Association request to the driver failed
> > Setting authentication timeout: 5 sec 0 usec
> > EAPOL: External notification - portControl=ForceAuthorized
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: ASSOCIATING -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> >
> >
> > Please tell me why it is failing?
> >
> >
>
>


-- 
Regards & Thanks
Raghavendra. S



From dcbw  Mon Dec 17 18:14:00 2007
From: dcbw (Dan Williams)
Date: Mon, 17 Dec 2007 21:14:00 -0500
Subject: WEP-shared is failing...
In-Reply-To: <58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
Message-ID: <1197944040.4733.4.camel@localhost.localdomain>

On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> Hi,
> 
>   Tried with hex key...still failing...
> ----------------------------------------------------------------------------------
> ctrl_interface=/var/run/wpa_supplicant
> ap_scan=1
> 
> network={
>         ssid="3Com"
>         key_mgmt=NONE
>         wep_key0=76F6B7657D
>         wep_tx_keyidx=0
>         auth_alg=SHARED
> }
> ----------------------------------------------------------------------------------------
> 
> if you see below log...i have following three lines...
> 
> ioctl[SIOCSIWFREQ]: Operation not supported
> ioctl[SIOCSIWESSID]: Network is unreachable
> ioctl[SIOCSIWAP]: Network is unreachable

The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
SIOCSIWAP when it can't find the SSID to associate with, or when the
security parameters of the network don't match what the driver has been
configured for.  Basically, the configuration you have and the scan
result that the driver has don't match up, or the network wasn't found
during the pre-association scan.  Can you provide the output of 'iwlist
ethX scan' for the 3Com network you want to connect to?

Dan

> is this a problem..or some thing else?
> 
> 
> 
> 
> 
> On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > Hi All,
> > >
> > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > connect with AP,
> > > My supplicant.conf file configuration is all below.
> > >
> > > ----------------------start------------------------------------------------------------------
> > >
> > > ctrl_interface=/var/run/wpa_supplicant
> > >
> > > network={
> > >         ssid="3Com"
> > >         key_mgmt=NONE
> > >         auth_alg=SHARED
> > >         wep_key0="raghu123456"
> >
> > Are you trying to use a WEP passphrase here?  I don't think
> > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > instead.
> >
> > Dan
> >
> >
> > >         wep_tx_keyidx=0
> > > }
> > > ----------------------end-------------------------------------------------------------------
> > >
> > > I got following failure logs,
> > >
> > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > ctrl_interface='/var/run/wpa_supplicant'
> > > Line: 4 - start of a new network block
> > > ssid - hexdump_ascii(len=4):
> > >      33 43 6f 6d                                       3Com
> > > key_mgmt: 0x4
> > > auth_alg: 0x2
> > > wep_key0 - hexdump(len=11): [REMOVED]
> > > wep_tx_keyidx=0 (0x0)
> > > Priority group 0
> > >    id=0 ssid='3Com'
> > > Initializing interface (2) 'eth0'
> > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > EAPOL: SUPP_BE entering state INITIALIZE
> > > EAP: EAP entering state DISABLED
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > >   capabilities: key_mgmt 0x0 enc 0x3
> > > WEXT: Operstate: linkmode=1, operstate=5
> > > Own MAC address: 00:13:e0:9e:9b:2e
> > > wpa_driver_wext_set_wpa
> > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_countermeasures
> > > wpa_driver_wext_set_drop_unencrypted
> > > Setting scan request: 0 sec 100000 usec
> > > Added interface eth0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > State: DISCONNECTED -> SCANNING
> > > Starting AP scan (broadcast SSID)
> > > Trying to get current scan results first without requesting a new scan
> > > to speed up initial association
> > > Received 416 bytes of scan results (5 BSSes)
> > > Scan results: 5
> > > Selecting BSS from priority group 0
> > > Try to find WPA-enabled AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > >    skip - no WPA/RSN IE
> > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > >    skip - no WPA/RSN IE
> > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > >    skip - no WPA/RSN IE
> > > Try to find non-WPA AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - SSID mismatch
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > Cancelling scan request
> > > WPA: clearing own WPA/RSN IE
> > > Automatic auth_alg selection: 0x1
> > > Overriding auth_alg selection: 0x2
> > > WPA: clearing AP WPA IE
> > > WPA: clearing AP RSN IE
> > > WPA: clearing own WPA/RSN IE
> > > No keys have been configured - skip key clearing
> > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > wpa_driver_wext_set_drop_unencrypted
> > > State: SCANNING -> ASSOCIATING
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > wpa_driver_wext_associate
> > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > ioctl[SIOCSIWAP]: Network is unreachable
> > > Association request to the driver failed
> > > Setting authentication timeout: 5 sec 0 usec
> > > EAPOL: External notification - portControl=ForceAuthorized
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: ASSOCIATING -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > Authentication with 00:00:00:00:00:00 timed out.
> > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > 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
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > Setting scan request: 0 sec 0 usec
> > > State: DISCONNECTED -> SCANNING
> > > Starting AP scan (broadcast SSID)
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b19 len=8
> > > Received 416 bytes of scan results (5 BSSes)
> > > Scan results: 5
> > > Selecting BSS from priority group 0
> > > Try to find WPA-enabled AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > >    skip - no WPA/RSN IE
> > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > >    skip - no WPA/RSN IE
> > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > >    skip - no WPA/RSN IE
> > > Try to find non-WPA AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - SSID mismatch
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > Cancelling scan request
> > > WPA: clearing own WPA/RSN IE
> > > Automatic auth_alg selection: 0x1
> > > Overriding auth_alg selection: 0x2
> > > WPA: clearing AP WPA IE
> > > WPA: clearing AP RSN IE
> > > WPA: clearing own WPA/RSN IE
> > > No keys have been configured - skip key clearing
> > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > wpa_driver_wext_set_drop_unencrypted
> > > State: SCANNING -> ASSOCIATING
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > wpa_driver_wext_associate
> > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > ioctl[SIOCSIWAP]: Network is unreachable
> > > Association request to the driver failed
> > > Setting authentication timeout: 5 sec 0 usec
> > > EAPOL: External notification - portControl=ForceAuthorized
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: ASSOCIATING -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > >
> > >
> > > Please tell me why it is failing?
> > >
> > >
> >
> >
> 
> 




From raghavendra.akkasali  Mon Dec 17 18:18:14 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 07:48:14 +0530
Subject: WEP-shared is failing...
In-Reply-To: <1197944040.4733.4.camel@localhost.localdomain>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
	<1197944040.4733.4.camel@localhost.localdomain>
Message-ID: <58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>

Hi,

  Plz find "iwlist eth0 scan" - result

# /sbin/ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:13:E0:9E:9B:2E
          UP BROADCAST 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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:41

# iwlist eth0 scan
eth0      Scan completed :
          Cell 01 - Address: 00:0F:CB:FE:2F:5F
                    ESSID:"3Com"
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:0/100  Signal level=-42 dBm  Noise level=-96 dBm
                    Encryption key:on
                    Bit Rates:54 Mb/s


-Raghu

On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> > Hi,
> >
> >   Tried with hex key...still failing...
> > ----------------------------------------------------------------------------------
> > ctrl_interface=/var/run/wpa_supplicant
> > ap_scan=1
> >
> > network={
> >         ssid="3Com"
> >         key_mgmt=NONE
> >         wep_key0=76F6B7657D
> >         wep_tx_keyidx=0
> >         auth_alg=SHARED
> > }
> > ----------------------------------------------------------------------------------------
> >
> > if you see below log...i have following three lines...
> >
> > ioctl[SIOCSIWFREQ]: Operation not supported
> > ioctl[SIOCSIWESSID]: Network is unreachable
> > ioctl[SIOCSIWAP]: Network is unreachable
>
> The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
> SIOCSIWAP when it can't find the SSID to associate with, or when the
> security parameters of the network don't match what the driver has been
> configured for.  Basically, the configuration you have and the scan
> result that the driver has don't match up, or the network wasn't found
> during the pre-association scan.  Can you provide the output of 'iwlist
> ethX scan' for the 3Com network you want to connect to?
>
> Dan
>
> > is this a problem..or some thing else?
> >
> >
> >
> >
> >
> > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > Hi All,
> > > >
> > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > connect with AP,
> > > > My supplicant.conf file configuration is all below.
> > > >
> > > > ----------------------start------------------------------------------------------------------
> > > >
> > > > ctrl_interface=/var/run/wpa_supplicant
> > > >
> > > > network={
> > > >         ssid="3Com"
> > > >         key_mgmt=NONE
> > > >         auth_alg=SHARED
> > > >         wep_key0="raghu123456"
> > >
> > > Are you trying to use a WEP passphrase here?  I don't think
> > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > instead.
> > >
> > > Dan
> > >
> > >
> > > >         wep_tx_keyidx=0
> > > > }
> > > > ----------------------end-------------------------------------------------------------------
> > > >
> > > > I got following failure logs,
> > > >
> > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > Line: 4 - start of a new network block
> > > > ssid - hexdump_ascii(len=4):
> > > >      33 43 6f 6d                                       3Com
> > > > key_mgmt: 0x4
> > > > auth_alg: 0x2
> > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > wep_tx_keyidx=0 (0x0)
> > > > Priority group 0
> > > >    id=0 ssid='3Com'
> > > > Initializing interface (2) 'eth0'
> > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > EAP: EAP entering state DISABLED
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > wpa_driver_wext_set_wpa
> > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_countermeasures
> > > > wpa_driver_wext_set_drop_unencrypted
> > > > Setting scan request: 0 sec 100000 usec
> > > > Added interface eth0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > State: DISCONNECTED -> SCANNING
> > > > Starting AP scan (broadcast SSID)
> > > > Trying to get current scan results first without requesting a new scan
> > > > to speed up initial association
> > > > Received 416 bytes of scan results (5 BSSes)
> > > > Scan results: 5
> > > > Selecting BSS from priority group 0
> > > > Try to find WPA-enabled AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > >    skip - no WPA/RSN IE
> > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > >    skip - no WPA/RSN IE
> > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > >    skip - no WPA/RSN IE
> > > > Try to find non-WPA AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - SSID mismatch
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > Cancelling scan request
> > > > WPA: clearing own WPA/RSN IE
> > > > Automatic auth_alg selection: 0x1
> > > > Overriding auth_alg selection: 0x2
> > > > WPA: clearing AP WPA IE
> > > > WPA: clearing AP RSN IE
> > > > WPA: clearing own WPA/RSN IE
> > > > No keys have been configured - skip key clearing
> > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > wpa_driver_wext_set_drop_unencrypted
> > > > State: SCANNING -> ASSOCIATING
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > wpa_driver_wext_associate
> > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > Association request to the driver failed
> > > > Setting authentication timeout: 5 sec 0 usec
> > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: ASSOCIATING -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > 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
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > Setting scan request: 0 sec 0 usec
> > > > State: DISCONNECTED -> SCANNING
> > > > Starting AP scan (broadcast SSID)
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b19 len=8
> > > > Received 416 bytes of scan results (5 BSSes)
> > > > Scan results: 5
> > > > Selecting BSS from priority group 0
> > > > Try to find WPA-enabled AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > >    skip - no WPA/RSN IE
> > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > >    skip - no WPA/RSN IE
> > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > >    skip - no WPA/RSN IE
> > > > Try to find non-WPA AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - SSID mismatch
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > Cancelling scan request
> > > > WPA: clearing own WPA/RSN IE
> > > > Automatic auth_alg selection: 0x1
> > > > Overriding auth_alg selection: 0x2
> > > > WPA: clearing AP WPA IE
> > > > WPA: clearing AP RSN IE
> > > > WPA: clearing own WPA/RSN IE
> > > > No keys have been configured - skip key clearing
> > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > wpa_driver_wext_set_drop_unencrypted
> > > > State: SCANNING -> ASSOCIATING
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > wpa_driver_wext_associate
> > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > Association request to the driver failed
> > > > Setting authentication timeout: 5 sec 0 usec
> > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: ASSOCIATING -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > >
> > > >
> > > > Please tell me why it is failing?
> > > >
> > > >
> > >
> > >
> >
> >
>
>


-- 
Regards & Thanks
Raghavendra. S



From raghavendra.akkasali  Mon Dec 17 18:21:42 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 07:51:42 +0530
Subject: WEP-shared is failing...
In-Reply-To: <58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
	<1197944040.4733.4.camel@localhost.localdomain>
	<58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>
Message-ID: <58a444250712171821l5a4cf9e8k4a26402a1bf66fcd@mail.gmail.com>

Hi,

   One small correction, i am using wpa supplicant-0.5.9, with -Dwext
on marvell 8686. It is working for EAP methods, WEP-open...etc.
   Previously  I was using marvell ported wpa supplicant 0.5.7 with
-Dmarvell. Now I tried with 0.5.7 also...for that also it is failing.

-Raghu.

On 12/18/07, Raghavendra. S <raghavendra.akkasali at gmail.com> wrote:
> Hi,
>
>  Plz find "iwlist eth0 scan" - result
>
> # /sbin/ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:13:E0:9E:9B:2E
>          UP BROADCAST 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:1000
>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>          Interrupt:41
>
> # iwlist eth0 scan
> eth0      Scan completed :
>          Cell 01 - Address: 00:0F:CB:FE:2F:5F
>                    ESSID:"3Com"
>                    Mode:Managed
>                    Frequency:2.412 GHz (Channel 1)
>                    Quality:0/100  Signal level=-42 dBm  Noise level=-96 dBm
>                    Encryption key:on
>                    Bit Rates:54 Mb/s
>
>
> -Raghu
>
> On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> > > Hi,
> > >
> > >   Tried with hex key...still failing...
> > > ----------------------------------------------------------------------------------
> > > ctrl_interface=/var/run/wpa_supplicant
> > > ap_scan=1
> > >
> > > network={
> > >         ssid="3Com"
> > >         key_mgmt=NONE
> > >         wep_key0=76F6B7657D
> > >         wep_tx_keyidx=0
> > >         auth_alg=SHARED
> > > }
> > > ----------------------------------------------------------------------------------------
> > >
> > > if you see below log...i have following three lines...
> > >
> > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > ioctl[SIOCSIWAP]: Network is unreachable
> >
> > The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
> > SIOCSIWAP when it can't find the SSID to associate with, or when the
> > security parameters of the network don't match what the driver has been
> > configured for.  Basically, the configuration you have and the scan
> > result that the driver has don't match up, or the network wasn't found
> > during the pre-association scan.  Can you provide the output of 'iwlist
> > ethX scan' for the 3Com network you want to connect to?
> >
> > Dan
> >
> > > is this a problem..or some thing else?
> > >
> > >
> > >
> > >
> > >
> > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > > Hi All,
> > > > >
> > > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > > connect with AP,
> > > > > My supplicant.conf file configuration is all below.
> > > > >
> > > > > ----------------------start------------------------------------------------------------------
> > > > >
> > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > >
> > > > > network={
> > > > >         ssid="3Com"
> > > > >         key_mgmt=NONE
> > > > >         auth_alg=SHARED
> > > > >         wep_key0="raghu123456"
> > > >
> > > > Are you trying to use a WEP passphrase here?  I don't think
> > > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > > instead.
> > > >
> > > > Dan
> > > >
> > > >
> > > > >         wep_tx_keyidx=0
> > > > > }
> > > > > ----------------------end-------------------------------------------------------------------
> > > > >
> > > > > I got following failure logs,
> > > > >
> > > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > > Line: 4 - start of a new network block
> > > > > ssid - hexdump_ascii(len=4):
> > > > >      33 43 6f 6d                                       3Com
> > > > > key_mgmt: 0x4
> > > > > auth_alg: 0x2
> > > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > > wep_tx_keyidx=0 (0x0)
> > > > > Priority group 0
> > > > >    id=0 ssid='3Com'
> > > > > Initializing interface (2) 'eth0'
> > > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > > EAP: EAP entering state DISABLED
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > > wpa_driver_wext_set_wpa
> > > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > > wpa_driver_wext_set_countermeasures
> > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > Setting scan request: 0 sec 100000 usec
> > > > > Added interface eth0
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b06 len=8
> > > > > State: DISCONNECTED -> SCANNING
> > > > > Starting AP scan (broadcast SSID)
> > > > > Trying to get current scan results first without requesting a new scan
> > > > > to speed up initial association
> > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > Scan results: 5
> > > > > Selecting BSS from priority group 0
> > > > > Try to find WPA-enabled AP
> > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - no WPA/RSN IE
> > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - no WPA/RSN IE
> > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > >    skip - no WPA/RSN IE
> > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > >    skip - no WPA/RSN IE
> > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > >    skip - no WPA/RSN IE
> > > > > Try to find non-WPA AP
> > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - SSID mismatch
> > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > Cancelling scan request
> > > > > WPA: clearing own WPA/RSN IE
> > > > > Automatic auth_alg selection: 0x1
> > > > > Overriding auth_alg selection: 0x2
> > > > > WPA: clearing AP WPA IE
> > > > > WPA: clearing AP RSN IE
> > > > > WPA: clearing own WPA/RSN IE
> > > > > No keys have been configured - skip key clearing
> > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > State: SCANNING -> ASSOCIATING
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > wpa_driver_wext_associate
> > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > Association request to the driver failed
> > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b06 len=8
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b15 len=20
> > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b15 len=20
> > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > > 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
> > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > > Setting scan request: 0 sec 0 usec
> > > > > State: DISCONNECTED -> SCANNING
> > > > > Starting AP scan (broadcast SSID)
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b19 len=8
> > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > Scan results: 5
> > > > > Selecting BSS from priority group 0
> > > > > Try to find WPA-enabled AP
> > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - no WPA/RSN IE
> > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - no WPA/RSN IE
> > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > >    skip - no WPA/RSN IE
> > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > >    skip - no WPA/RSN IE
> > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > >    skip - no WPA/RSN IE
> > > > > Try to find non-WPA AP
> > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    skip - SSID mismatch
> > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > Cancelling scan request
> > > > > WPA: clearing own WPA/RSN IE
> > > > > Automatic auth_alg selection: 0x1
> > > > > Overriding auth_alg selection: 0x2
> > > > > WPA: clearing AP WPA IE
> > > > > WPA: clearing AP RSN IE
> > > > > WPA: clearing own WPA/RSN IE
> > > > > No keys have been configured - skip key clearing
> > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > State: SCANNING -> ASSOCIATING
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > wpa_driver_wext_associate
> > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > Association request to the driver failed
> > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b06 len=8
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b15 len=20
> > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > Wireless event: cmd=0x8b15 len=20
> > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > EAPOL: External notification - portEnabled=0
> > > > > EAPOL: External notification - portValid=0
> > > > >
> > > > >
> > > > > Please tell me why it is failing?
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> --
> Regards & Thanks
> Raghavendra. S
>


-- 
Regards & Thanks
Raghavendra. S



From kel  Mon Dec 17 18:27:17 2007
From: kel (Kel Modderman)
Date: Tue, 18 Dec 2007 12:27:17 +1000
Subject: WEP-shared is failing...
In-Reply-To: <1197943173.4733.0.camel@localhost.localdomain>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
Message-ID: <200712181227.17651.kel@otaku42.de>

On Tuesday 18 December 2007 11:59:33 Dan Williams wrote:
> On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > Hi All,
> >
> >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > connect with AP,
> > My supplicant.conf file configuration is all below.
> >
> > ----------------------start----------------------------------------------
> >--------------------
> >
> > ctrl_interface=/var/run/wpa_supplicant
> >
> > network={
> >         ssid="3Com"
> >         key_mgmt=NONE
> >         auth_alg=SHARED
> >         wep_key0="raghu123456"
>
> Are you trying to use a WEP passphrase here?  I don't think
> wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> instead.
>
> Dan

It was my understanding that WEP passphrase hashing is supported. At least, it 
appears to be working for me right now.

Thanks, Kel.

>
> >         wep_tx_keyidx=0
> > }
> > ----------------------end------------------------------------------------
> >-------------------
> >
> > I got following failure logs,
> >
> > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w
> > -ddd Initializing interface 'eth0' conf
> > './files/wpa_supplicant.sharedWEP' driver 'wext' ctrl_interface 'N/A'
> > bridge 'N/A'
> > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > ctrl_interface='/var/run/wpa_supplicant'
> > Line: 4 - start of a new network block
> > ssid - hexdump_ascii(len=4):
> >      33 43 6f 6d                                       3Com
> > key_mgmt: 0x4
> > auth_alg: 0x2
> > wep_key0 - hexdump(len=11): [REMOVED]
> > wep_tx_keyidx=0 (0x0)
> > Priority group 0
> >    id=0 ssid='3Com'
> > Initializing interface (2) 'eth0'
> > EAPOL: SUPP_PAE entering state DISCONNECTED
> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > EAPOL: SUPP_BE entering state INITIALIZE
> > EAP: EAP entering state DISABLED
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > ioctl[SIOCSIWPMKSA]: Invalid argument
> > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> >   capabilities: key_mgmt 0x0 enc 0x3
> > WEXT: Operstate: linkmode=1, operstate=5
> > Own MAC address: 00:13:e0:9e:9b:2e
> > wpa_driver_wext_set_wpa
> > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > wpa_driver_wext_set_countermeasures
> > wpa_driver_wext_set_drop_unencrypted
> > Setting scan request: 0 sec 100000 usec
> > Added interface eth0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (broadcast SSID)
> > Trying to get current scan results first without requesting a new scan
> > to speed up initial association
> > Received 416 bytes of scan results (5 BSSes)
> > Scan results: 5
> > Selecting BSS from priority group 0
> > Try to find WPA-enabled AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> >    skip - no WPA/RSN IE
> > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> >    skip - no WPA/RSN IE
> > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > caps=0x1 skip - no WPA/RSN IE
> > Try to find non-WPA AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - SSID mismatch
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > Overriding auth_alg selection: 0x2
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > No keys have been configured - skip key clearing
> > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > wpa_driver_wext_set_drop_unencrypted
> > State: SCANNING -> ASSOCIATING
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > wpa_driver_wext_associate
> > ioctl[SIOCSIWFREQ]: Operation not supported
> > ioctl[SIOCSIWESSID]: Network is unreachable
> > ioctl[SIOCSIWAP]: Network is unreachable
> > Association request to the driver failed
> > Setting authentication timeout: 5 sec 0 usec
> > EAPOL: External notification - portControl=ForceAuthorized
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: ASSOCIATING -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > Added BSSID 00:00:00:00:00:00 into blacklist
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > Authentication with 00:00:00:00:00:00 timed out.
> > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > 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
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > Setting scan request: 0 sec 0 usec
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (broadcast SSID)
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b19 len=8
> > Received 416 bytes of scan results (5 BSSes)
> > Scan results: 5
> > Selecting BSS from priority group 0
> > Try to find WPA-enabled AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - no WPA/RSN IE
> > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> >    skip - no WPA/RSN IE
> > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> >    skip - no WPA/RSN IE
> > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > caps=0x1 skip - no WPA/RSN IE
> > Try to find non-WPA AP
> > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    skip - SSID mismatch
> > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > Cancelling scan request
> > WPA: clearing own WPA/RSN IE
> > Automatic auth_alg selection: 0x1
> > Overriding auth_alg selection: 0x2
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > No keys have been configured - skip key clearing
> > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > wpa_driver_wext_set_drop_unencrypted
> > State: SCANNING -> ASSOCIATING
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > wpa_driver_wext_associate
> > ioctl[SIOCSIWFREQ]: Operation not supported
> > ioctl[SIOCSIWESSID]: Network is unreachable
> > ioctl[SIOCSIWAP]: Network is unreachable
> > Association request to the driver failed
> > Setting authentication timeout: 5 sec 0 usec
> > EAPOL: External notification - portControl=ForceAuthorized
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b06 len=8
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: ASSOCIATING -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > Wireless event: cmd=0x8b15 len=20
> > Wireless event: new AP: 00:00:00:00:00:00
> > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > State: DISCONNECTED -> DISCONNECTED
> > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > WEXT: Operstate: linkmode=-1, operstate=5
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> >
> >
> > Please tell me why it is failing?
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap





From dcbw  Mon Dec 17 18:34:32 2007
From: dcbw (Dan Williams)
Date: Mon, 17 Dec 2007 21:34:32 -0500
Subject: WEP-shared is failing...
In-Reply-To: <200712181227.17651.kel@otaku42.de>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<200712181227.17651.kel@otaku42.de>
Message-ID: <1197945272.6048.3.camel@localhost.localdomain>

On Tue, 2007-12-18 at 12:27 +1000, Kel Modderman wrote:
> On Tuesday 18 December 2007 11:59:33 Dan Williams wrote:
> > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > Hi All,
> > >
> > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > connect with AP,
> > > My supplicant.conf file configuration is all below.
> > >
> > > ----------------------start----------------------------------------------
> > >--------------------
> > >
> > > ctrl_interface=/var/run/wpa_supplicant
> > >
> > > network={
> > >         ssid="3Com"
> > >         key_mgmt=NONE
> > >         auth_alg=SHARED
> > >         wep_key0="raghu123456"
> >
> > Are you trying to use a WEP passphrase here?  I don't think
> > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > instead.
> >
> > Dan
> 
> It was my understanding that WEP passphrase hashing is supported. At least, it 
> appears to be working for me right now.

I think it'll do WEP _ASCII_ password.  But I'm pretty sure it won't do
WEP passphrases, which are what most APs these days use.

Dan

> Thanks, Kel.
> 
> >
> > >         wep_tx_keyidx=0
> > > }
> > > ----------------------end------------------------------------------------
> > >-------------------
> > >
> > > I got following failure logs,
> > >
> > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w
> > > -ddd Initializing interface 'eth0' conf
> > > './files/wpa_supplicant.sharedWEP' driver 'wext' ctrl_interface 'N/A'
> > > bridge 'N/A'
> > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > ctrl_interface='/var/run/wpa_supplicant'
> > > Line: 4 - start of a new network block
> > > ssid - hexdump_ascii(len=4):
> > >      33 43 6f 6d                                       3Com
> > > key_mgmt: 0x4
> > > auth_alg: 0x2
> > > wep_key0 - hexdump(len=11): [REMOVED]
> > > wep_tx_keyidx=0 (0x0)
> > > Priority group 0
> > >    id=0 ssid='3Com'
> > > Initializing interface (2) 'eth0'
> > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > EAPOL: SUPP_BE entering state INITIALIZE
> > > EAP: EAP entering state DISABLED
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > >   capabilities: key_mgmt 0x0 enc 0x3
> > > WEXT: Operstate: linkmode=1, operstate=5
> > > Own MAC address: 00:13:e0:9e:9b:2e
> > > wpa_driver_wext_set_wpa
> > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > wpa_driver_wext_set_countermeasures
> > > wpa_driver_wext_set_drop_unencrypted
> > > Setting scan request: 0 sec 100000 usec
> > > Added interface eth0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > State: DISCONNECTED -> SCANNING
> > > Starting AP scan (broadcast SSID)
> > > Trying to get current scan results first without requesting a new scan
> > > to speed up initial association
> > > Received 416 bytes of scan results (5 BSSes)
> > > Scan results: 5
> > > Selecting BSS from priority group 0
> > > Try to find WPA-enabled AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > >    skip - no WPA/RSN IE
> > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > >    skip - no WPA/RSN IE
> > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > > caps=0x1 skip - no WPA/RSN IE
> > > Try to find non-WPA AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - SSID mismatch
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > Cancelling scan request
> > > WPA: clearing own WPA/RSN IE
> > > Automatic auth_alg selection: 0x1
> > > Overriding auth_alg selection: 0x2
> > > WPA: clearing AP WPA IE
> > > WPA: clearing AP RSN IE
> > > WPA: clearing own WPA/RSN IE
> > > No keys have been configured - skip key clearing
> > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > wpa_driver_wext_set_drop_unencrypted
> > > State: SCANNING -> ASSOCIATING
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > wpa_driver_wext_associate
> > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > ioctl[SIOCSIWAP]: Network is unreachable
> > > Association request to the driver failed
> > > Setting authentication timeout: 5 sec 0 usec
> > > EAPOL: External notification - portControl=ForceAuthorized
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: ASSOCIATING -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > Authentication with 00:00:00:00:00:00 timed out.
> > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > 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
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > Setting scan request: 0 sec 0 usec
> > > State: DISCONNECTED -> SCANNING
> > > Starting AP scan (broadcast SSID)
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b19 len=8
> > > Received 416 bytes of scan results (5 BSSes)
> > > Scan results: 5
> > > Selecting BSS from priority group 0
> > > Try to find WPA-enabled AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - no WPA/RSN IE
> > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > >    skip - no WPA/RSN IE
> > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > >    skip - no WPA/RSN IE
> > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > > caps=0x1 skip - no WPA/RSN IE
> > > Try to find non-WPA AP
> > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    skip - SSID mismatch
> > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > Cancelling scan request
> > > WPA: clearing own WPA/RSN IE
> > > Automatic auth_alg selection: 0x1
> > > Overriding auth_alg selection: 0x2
> > > WPA: clearing AP WPA IE
> > > WPA: clearing AP RSN IE
> > > WPA: clearing own WPA/RSN IE
> > > No keys have been configured - skip key clearing
> > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > wpa_driver_wext_set_drop_unencrypted
> > > State: SCANNING -> ASSOCIATING
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > wpa_driver_wext_associate
> > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > ioctl[SIOCSIWAP]: Network is unreachable
> > > Association request to the driver failed
> > > Setting authentication timeout: 5 sec 0 usec
> > > EAPOL: External notification - portControl=ForceAuthorized
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b06 len=8
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: ASSOCIATING -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > Wireless event: cmd=0x8b15 len=20
> > > Wireless event: new AP: 00:00:00:00:00:00
> > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > State: DISCONNECTED -> DISCONNECTED
> > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > WEXT: Operstate: linkmode=-1, operstate=5
> > > EAPOL: External notification - portEnabled=0
> > > EAPOL: External notification - portValid=0
> > >
> > >
> > > Please tell me why it is failing?
> >
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> 
> 




From dcbw  Mon Dec 17 18:39:11 2007
From: dcbw (Dan Williams)
Date: Mon, 17 Dec 2007 21:39:11 -0500
Subject: WEP-shared is failing...
In-Reply-To: <58a444250712171821l5a4cf9e8k4a26402a1bf66fcd@mail.gmail.com>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
	<1197944040.4733.4.camel@localhost.localdomain>
	<58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>
	<58a444250712171821l5a4cf9e8k4a26402a1bf66fcd@mail.gmail.com>
Message-ID: <1197945551.6048.7.camel@localhost.localdomain>

On Tue, 2007-12-18 at 07:51 +0530, Raghavendra. S wrote:
> Hi,
> 
>    One small correction, i am using wpa supplicant-0.5.9, with -Dwext
> on marvell 8686. It is working for EAP methods, WEP-open...etc.
>    Previously  I was using marvell ported wpa supplicant 0.5.7 with
> -Dmarvell. Now I tried with 0.5.7 also...for that also it is failing.

You're going to need to get debug output from the driver to figure out
what is going wrong in the association bits.

Turn on DBG_INFO (see wlan_defs.h) and reply with the output you get in
the kernel logs.

Dan


> -Raghu.
> 
> On 12/18/07, Raghavendra. S <raghavendra.akkasali at gmail.com> wrote:
> > Hi,
> >
> >  Plz find "iwlist eth0 scan" - result
> >
> > # /sbin/ifconfig eth0
> > eth0      Link encap:Ethernet  HWaddr 00:13:E0:9E:9B:2E
> >          UP BROADCAST 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:1000
> >          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> >          Interrupt:41
> >
> > # iwlist eth0 scan
> > eth0      Scan completed :
> >          Cell 01 - Address: 00:0F:CB:FE:2F:5F
> >                    ESSID:"3Com"
> >                    Mode:Managed
> >                    Frequency:2.412 GHz (Channel 1)
> >                    Quality:0/100  Signal level=-42 dBm  Noise level=-96 dBm
> >                    Encryption key:on
> >                    Bit Rates:54 Mb/s
> >
> >
> > -Raghu
> >
> > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> > > > Hi,
> > > >
> > > >   Tried with hex key...still failing...
> > > > ----------------------------------------------------------------------------------
> > > > ctrl_interface=/var/run/wpa_supplicant
> > > > ap_scan=1
> > > >
> > > > network={
> > > >         ssid="3Com"
> > > >         key_mgmt=NONE
> > > >         wep_key0=76F6B7657D
> > > >         wep_tx_keyidx=0
> > > >         auth_alg=SHARED
> > > > }
> > > > ----------------------------------------------------------------------------------------
> > > >
> > > > if you see below log...i have following three lines...
> > > >
> > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > ioctl[SIOCSIWAP]: Network is unreachable
> > >
> > > The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
> > > SIOCSIWAP when it can't find the SSID to associate with, or when the
> > > security parameters of the network don't match what the driver has been
> > > configured for.  Basically, the configuration you have and the scan
> > > result that the driver has don't match up, or the network wasn't found
> > > during the pre-association scan.  Can you provide the output of 'iwlist
> > > ethX scan' for the 3Com network you want to connect to?
> > >
> > > Dan
> > >
> > > > is this a problem..or some thing else?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > > > Hi All,
> > > > > >
> > > > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > > > connect with AP,
> > > > > > My supplicant.conf file configuration is all below.
> > > > > >
> > > > > > ----------------------start------------------------------------------------------------------
> > > > > >
> > > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > > >
> > > > > > network={
> > > > > >         ssid="3Com"
> > > > > >         key_mgmt=NONE
> > > > > >         auth_alg=SHARED
> > > > > >         wep_key0="raghu123456"
> > > > >
> > > > > Are you trying to use a WEP passphrase here?  I don't think
> > > > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > > > instead.
> > > > >
> > > > > Dan
> > > > >
> > > > >
> > > > > >         wep_tx_keyidx=0
> > > > > > }
> > > > > > ----------------------end-------------------------------------------------------------------
> > > > > >
> > > > > > I got following failure logs,
> > > > > >
> > > > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > > > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > > > Line: 4 - start of a new network block
> > > > > > ssid - hexdump_ascii(len=4):
> > > > > >      33 43 6f 6d                                       3Com
> > > > > > key_mgmt: 0x4
> > > > > > auth_alg: 0x2
> > > > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > > > wep_tx_keyidx=0 (0x0)
> > > > > > Priority group 0
> > > > > >    id=0 ssid='3Com'
> > > > > > Initializing interface (2) 'eth0'
> > > > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > > > EAP: EAP entering state DISABLED
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > > > wpa_driver_wext_set_wpa
> > > > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > > > wpa_driver_wext_set_countermeasures
> > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > Setting scan request: 0 sec 100000 usec
> > > > > > Added interface eth0
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > State: DISCONNECTED -> SCANNING
> > > > > > Starting AP scan (broadcast SSID)
> > > > > > Trying to get current scan results first without requesting a new scan
> > > > > > to speed up initial association
> > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > Scan results: 5
> > > > > > Selecting BSS from priority group 0
> > > > > > Try to find WPA-enabled AP
> > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - no WPA/RSN IE
> > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - no WPA/RSN IE
> > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > >    skip - no WPA/RSN IE
> > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > >    skip - no WPA/RSN IE
> > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > >    skip - no WPA/RSN IE
> > > > > > Try to find non-WPA AP
> > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - SSID mismatch
> > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > Cancelling scan request
> > > > > > WPA: clearing own WPA/RSN IE
> > > > > > Automatic auth_alg selection: 0x1
> > > > > > Overriding auth_alg selection: 0x2
> > > > > > WPA: clearing AP WPA IE
> > > > > > WPA: clearing AP RSN IE
> > > > > > WPA: clearing own WPA/RSN IE
> > > > > > No keys have been configured - skip key clearing
> > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > State: SCANNING -> ASSOCIATING
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > wpa_driver_wext_associate
> > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > Association request to the driver failed
> > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > > > 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
> > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > > Setting scan request: 0 sec 0 usec
> > > > > > State: DISCONNECTED -> SCANNING
> > > > > > Starting AP scan (broadcast SSID)
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b19 len=8
> > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > Scan results: 5
> > > > > > Selecting BSS from priority group 0
> > > > > > Try to find WPA-enabled AP
> > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - no WPA/RSN IE
> > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - no WPA/RSN IE
> > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > >    skip - no WPA/RSN IE
> > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > >    skip - no WPA/RSN IE
> > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > >    skip - no WPA/RSN IE
> > > > > > Try to find non-WPA AP
> > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    skip - SSID mismatch
> > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > Cancelling scan request
> > > > > > WPA: clearing own WPA/RSN IE
> > > > > > Automatic auth_alg selection: 0x1
> > > > > > Overriding auth_alg selection: 0x2
> > > > > > WPA: clearing AP WPA IE
> > > > > > WPA: clearing AP RSN IE
> > > > > > WPA: clearing own WPA/RSN IE
> > > > > > No keys have been configured - skip key clearing
> > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > State: SCANNING -> ASSOCIATING
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > wpa_driver_wext_associate
> > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > Association request to the driver failed
> > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > EAPOL: External notification - portEnabled=0
> > > > > > EAPOL: External notification - portValid=0
> > > > > >
> > > > > >
> > > > > > Please tell me why it is failing?
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Regards & Thanks
> > Raghavendra. S
> >
> 
> 




From kel  Mon Dec 17 18:51:46 2007
From: kel (Kel Modderman)
Date: Tue, 18 Dec 2007 12:51:46 +1000
Subject: WEP-shared is failing...
In-Reply-To: <1197945272.6048.3.camel@localhost.localdomain>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<200712181227.17651.kel@otaku42.de>
	<1197945272.6048.3.camel@localhost.localdomain>
Message-ID: <200712181251.46641.kel@otaku42.de>

On Tuesday 18 December 2007 12:34:32 Dan Williams wrote:
> On Tue, 2007-12-18 at 12:27 +1000, Kel Modderman wrote:
> > On Tuesday 18 December 2007 11:59:33 Dan Williams wrote:
> > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > Hi All,
> > > >
> > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > connect with AP,
> > > > My supplicant.conf file configuration is all below.
> > > >
> > > > ----------------------start------------------------------------------
> > > >---- --------------------
> > > >
> > > > ctrl_interface=/var/run/wpa_supplicant
> > > >
> > > > network={
> > > >         ssid="3Com"
> > > >         key_mgmt=NONE
> > > >         auth_alg=SHARED
> > > >         wep_key0="raghu123456"
> > >
> > > Are you trying to use a WEP passphrase here?  I don't think
> > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > instead.
> > >
> > > Dan
> >
> > It was my understanding that WEP passphrase hashing is supported. At
> > least, it appears to be working for me right now.
>
> I think it'll do WEP _ASCII_ password.  But I'm pretty sure it won't do
> WEP passphrases, which are what most APs these days use.
>
> Dan

Aha, thanks for the clarification. Admittedly, I didn't really know the 
difference when it came to WEP keys.

Kel.

>
> > Thanks, Kel.
> >
> > > >         wep_tx_keyidx=0
> > > > }
> > > > ----------------------end--------------------------------------------
> > > >---- -------------------
> > > >
> > > > I got following failure logs,
> > > >
> > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP
> > > > -w -ddd Initializing interface 'eth0' conf
> > > > './files/wpa_supplicant.sharedWEP' driver 'wext' ctrl_interface 'N/A'
> > > > bridge 'N/A'
> > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > Reading configuration file
> > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > Line: 4 - start of a new network block
> > > > ssid - hexdump_ascii(len=4):
> > > >      33 43 6f 6d                                       3Com
> > > > key_mgmt: 0x4
> > > > auth_alg: 0x2
> > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > wep_tx_keyidx=0 (0x0)
> > > > Priority group 0
> > > >    id=0 ssid='3Com'
> > > > Initializing interface (2) 'eth0'
> > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > EAP: EAP entering state DISABLED
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > wpa_driver_wext_set_wpa
> > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > wpa_driver_wext_set_countermeasures
> > > > wpa_driver_wext_set_drop_unencrypted
> > > > Setting scan request: 0 sec 100000 usec
> > > > Added interface eth0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > State: DISCONNECTED -> SCANNING
> > > > Starting AP scan (broadcast SSID)
> > > > Trying to get current scan results first without requesting a new
> > > > scan to speed up initial association
> > > > Received 416 bytes of scan results (5 BSSes)
> > > > Scan results: 5
> > > > Selecting BSS from priority group 0
> > > > Try to find WPA-enabled AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x11 skip - no WPA/RSN IE
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x12 skip - no WPA/RSN IE
> > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > >    skip - no WPA/RSN IE
> > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x1 skip - no WPA/RSN IE
> > > > Try to find non-WPA AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x11 skip - SSID mismatch
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412
> > > > MHz) Cancelling scan request
> > > > WPA: clearing own WPA/RSN IE
> > > > Automatic auth_alg selection: 0x1
> > > > Overriding auth_alg selection: 0x2
> > > > WPA: clearing AP WPA IE
> > > > WPA: clearing AP RSN IE
> > > > WPA: clearing own WPA/RSN IE
> > > > No keys have been configured - skip key clearing
> > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0
> > > > key_len=11 wpa_driver_wext_set_drop_unencrypted
> > > > State: SCANNING -> ASSOCIATING
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > wpa_driver_wext_associate
> > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > Association request to the driver failed
> > > > Setting authentication timeout: 5 sec 0 usec
> > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: ASSOCIATING -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > 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
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > Setting scan request: 0 sec 0 usec
> > > > State: DISCONNECTED -> SCANNING
> > > > Starting AP scan (broadcast SSID)
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b19 len=8
> > > > Received 416 bytes of scan results (5 BSSes)
> > > > Scan results: 5
> > > > Selecting BSS from priority group 0
> > > > Try to find WPA-enabled AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x11 skip - no WPA/RSN IE
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    skip - no WPA/RSN IE
> > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x12 skip - no WPA/RSN IE
> > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > >    skip - no WPA/RSN IE
> > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x1 skip - no WPA/RSN IE
> > > > Try to find non-WPA AP
> > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0
> > > > caps=0x11 skip - SSID mismatch
> > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412
> > > > MHz) Cancelling scan request
> > > > WPA: clearing own WPA/RSN IE
> > > > Automatic auth_alg selection: 0x1
> > > > Overriding auth_alg selection: 0x2
> > > > WPA: clearing AP WPA IE
> > > > WPA: clearing AP RSN IE
> > > > WPA: clearing own WPA/RSN IE
> > > > No keys have been configured - skip key clearing
> > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0
> > > > key_len=11 wpa_driver_wext_set_drop_unencrypted
> > > > State: SCANNING -> ASSOCIATING
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > wpa_driver_wext_associate
> > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > Association request to the driver failed
> > > > Setting authentication timeout: 5 sec 0 usec
> > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b06 len=8
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: ASSOCIATING -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > Wireless event: cmd=0x8b15 len=20
> > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > State: DISCONNECTED -> DISCONNECTED
> > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > EAPOL: External notification - portEnabled=0
> > > > EAPOL: External notification - portValid=0
> > > >
> > > >
> > > > Please tell me why it is failing?
> > >
> > > _______________________________________________
> > > HostAP mailing list
> > > HostAP at shmoo.com
> > > http://lists.shmoo.com/mailman/listinfo/hostap





From raghavendra.akkasali  Mon Dec 17 19:04:03 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 08:34:03 +0530
Subject: WEP-shared is failing...
In-Reply-To: <1197945551.6048.7.camel@localhost.localdomain>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
	<1197944040.4733.4.camel@localhost.localdomain>
	<58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>
	<58a444250712171821l5a4cf9e8k4a26402a1bf66fcd@mail.gmail.com>
	<1197945551.6048.7.camel@localhost.localdomain>
Message-ID: <58a444250712171904y4d9893d1h571f84f2466330d9@mail.gmail.com>

Hi Dan,

  I wonder..it started working all of a sudden. Previously I was
getting some event...
"Wireless event new AP 00:00:00:00:00:00", bcoz of which it was
disconnecting. Couldn't find out why my AP was sending this. Just let
me know in case if you have answer for this.

 But it works only for hex keys as you mentioned earlier.

 Thanx.

-Raghu.

On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-12-18 at 07:51 +0530, Raghavendra. S wrote:
> > Hi,
> >
> >    One small correction, i am using wpa supplicant-0.5.9, with -Dwext
> > on marvell 8686. It is working for EAP methods, WEP-open...etc.
> >    Previously  I was using marvell ported wpa supplicant 0.5.7 with
> > -Dmarvell. Now I tried with 0.5.7 also...for that also it is failing.
>
> You're going to need to get debug output from the driver to figure out
> what is going wrong in the association bits.
>
> Turn on DBG_INFO (see wlan_defs.h) and reply with the output you get in
> the kernel logs.
>
> Dan
>
>
> > -Raghu.
> >
> > On 12/18/07, Raghavendra. S <raghavendra.akkasali at gmail.com> wrote:
> > > Hi,
> > >
> > >  Plz find "iwlist eth0 scan" - result
> > >
> > > # /sbin/ifconfig eth0
> > > eth0      Link encap:Ethernet  HWaddr 00:13:E0:9E:9B:2E
> > >          UP BROADCAST 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:1000
> > >          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> > >          Interrupt:41
> > >
> > > # iwlist eth0 scan
> > > eth0      Scan completed :
> > >          Cell 01 - Address: 00:0F:CB:FE:2F:5F
> > >                    ESSID:"3Com"
> > >                    Mode:Managed
> > >                    Frequency:2.412 GHz (Channel 1)
> > >                    Quality:0/100  Signal level=-42 dBm  Noise level=-96 dBm
> > >                    Encryption key:on
> > >                    Bit Rates:54 Mb/s
> > >
> > >
> > > -Raghu
> > >
> > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> > > > > Hi,
> > > > >
> > > > >   Tried with hex key...still failing...
> > > > > ----------------------------------------------------------------------------------
> > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > > ap_scan=1
> > > > >
> > > > > network={
> > > > >         ssid="3Com"
> > > > >         key_mgmt=NONE
> > > > >         wep_key0=76F6B7657D
> > > > >         wep_tx_keyidx=0
> > > > >         auth_alg=SHARED
> > > > > }
> > > > > ----------------------------------------------------------------------------------------
> > > > >
> > > > > if you see below log...i have following three lines...
> > > > >
> > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > >
> > > > The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
> > > > SIOCSIWAP when it can't find the SSID to associate with, or when the
> > > > security parameters of the network don't match what the driver has been
> > > > configured for.  Basically, the configuration you have and the scan
> > > > result that the driver has don't match up, or the network wasn't found
> > > > during the pre-association scan.  Can you provide the output of 'iwlist
> > > > ethX scan' for the 3Com network you want to connect to?
> > > >
> > > > Dan
> > > >
> > > > > is this a problem..or some thing else?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > > > > Hi All,
> > > > > > >
> > > > > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > > > > connect with AP,
> > > > > > > My supplicant.conf file configuration is all below.
> > > > > > >
> > > > > > > ----------------------start------------------------------------------------------------------
> > > > > > >
> > > > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > > > >
> > > > > > > network={
> > > > > > >         ssid="3Com"
> > > > > > >         key_mgmt=NONE
> > > > > > >         auth_alg=SHARED
> > > > > > >         wep_key0="raghu123456"
> > > > > >
> > > > > > Are you trying to use a WEP passphrase here?  I don't think
> > > > > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > > > > instead.
> > > > > >
> > > > > > Dan
> > > > > >
> > > > > >
> > > > > > >         wep_tx_keyidx=0
> > > > > > > }
> > > > > > > ----------------------end-------------------------------------------------------------------
> > > > > > >
> > > > > > > I got following failure logs,
> > > > > > >
> > > > > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > > > > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > > > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > > > > Line: 4 - start of a new network block
> > > > > > > ssid - hexdump_ascii(len=4):
> > > > > > >      33 43 6f 6d                                       3Com
> > > > > > > key_mgmt: 0x4
> > > > > > > auth_alg: 0x2
> > > > > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > > > > wep_tx_keyidx=0 (0x0)
> > > > > > > Priority group 0
> > > > > > >    id=0 ssid='3Com'
> > > > > > > Initializing interface (2) 'eth0'
> > > > > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > > > > EAP: EAP entering state DISABLED
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > > > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > > > > wpa_driver_wext_set_wpa
> > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > > > > wpa_driver_wext_set_countermeasures
> > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > Setting scan request: 0 sec 100000 usec
> > > > > > > Added interface eth0
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > State: DISCONNECTED -> SCANNING
> > > > > > > Starting AP scan (broadcast SSID)
> > > > > > > Trying to get current scan results first without requesting a new scan
> > > > > > > to speed up initial association
> > > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > > Scan results: 5
> > > > > > > Selecting BSS from priority group 0
> > > > > > > Try to find WPA-enabled AP
> > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > Try to find non-WPA AP
> > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - SSID mismatch
> > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > > Cancelling scan request
> > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > Automatic auth_alg selection: 0x1
> > > > > > > Overriding auth_alg selection: 0x2
> > > > > > > WPA: clearing AP WPA IE
> > > > > > > WPA: clearing AP RSN IE
> > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > No keys have been configured - skip key clearing
> > > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > State: SCANNING -> ASSOCIATING
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > wpa_driver_wext_associate
> > > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > > Association request to the driver failed
> > > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > > > > 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
> > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > Setting scan request: 0 sec 0 usec
> > > > > > > State: DISCONNECTED -> SCANNING
> > > > > > > Starting AP scan (broadcast SSID)
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b19 len=8
> > > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > > Scan results: 5
> > > > > > > Selecting BSS from priority group 0
> > > > > > > Try to find WPA-enabled AP
> > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > > >    skip - no WPA/RSN IE
> > > > > > > Try to find non-WPA AP
> > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    skip - SSID mismatch
> > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > > Cancelling scan request
> > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > Automatic auth_alg selection: 0x1
> > > > > > > Overriding auth_alg selection: 0x2
> > > > > > > WPA: clearing AP WPA IE
> > > > > > > WPA: clearing AP RSN IE
> > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > No keys have been configured - skip key clearing
> > > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > State: SCANNING -> ASSOCIATING
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > wpa_driver_wext_associate
> > > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > > Association request to the driver failed
> > > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > >
> > > > > > >
> > > > > > > Please tell me why it is failing?
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Regards & Thanks
> > > Raghavendra. S
> > >
> >
> >
>
>


-- 
Regards & Thanks
Raghavendra. S



From j  Mon Dec 17 19:03:03 2007
From: j (Jouni Malinen)
Date: Mon, 17 Dec 2007 19:03:03 -0800
Subject: hostapd memory leak when connecting to Linux wpa_supplicant
In-Reply-To: <4766C3B3.4030208@glaserelectronics.com>
References: <4766C3B3.4030208@glaserelectronics.com>
Message-ID: <20071218030303.GZ5698@jm.kir.nu>

On Mon, Dec 17, 2007 at 10:45:07AM -0800, Ken Roberts wrote:

> hostapd v0.5.8
> wpa_supplicant v0.5.8
> madwifi v0.9.3.3
> kernel 2.6.21.5 <http://2.6.21.5> (recompiled for minimal drivers)
> 
> I've got 2 geode machines using the madwifi drivers. They worked great 
> for about a week. Unfortunately, hostapd started eating ram and causing 
> "out of memory and no programs to kill" errors on the ap running hostapd.

How did you measure hostapd memory use? It sounds a bit odd if the
kernel would not kill hostpad in such a case if the memory was indeed
leaked in hostapd.

> When connecting to a Linux machine running wpa_supplicant, free ram 
> started dropping like a rock until "out of memory" condition caused a 
> system freeze.

Have you looked at debug log from either hostapd or wpa_supplicant in
this state? Do they show constant action (e.g., new
associations/authentications)?

-- 
Jouni Malinen                                            PGP id EFC895FA



From dcbw  Mon Dec 17 19:08:09 2007
From: dcbw (Dan Williams)
Date: Mon, 17 Dec 2007 22:08:09 -0500
Subject: WEP-shared is failing...
In-Reply-To: <58a444250712171904y4d9893d1h571f84f2466330d9@mail.gmail.com>
References: <58a444250712171752o49cf062bp3b48725a9809803b@mail.gmail.com>
	<1197943173.4733.0.camel@localhost.localdomain>
	<58a444250712171810x2d099886i8bc149ed599794d1@mail.gmail.com>
	<1197944040.4733.4.camel@localhost.localdomain>
	<58a444250712171818r6093ad77if6a8b71dec8bd990@mail.gmail.com>
	<58a444250712171821l5a4cf9e8k4a26402a1bf66fcd@mail.gmail.com>
	<1197945551.6048.7.camel@localhost.localdomain>
	<58a444250712171904y4d9893d1h571f84f2466330d9@mail.gmail.com>
Message-ID: <1197947289.6048.23.camel@localhost.localdomain>

On Tue, 2007-12-18 at 08:34 +0530, Raghavendra. S wrote:
> Hi Dan,
> 
>   I wonder..it started working all of a sudden. Previously I was
> getting some event...
> "Wireless event new AP 00:00:00:00:00:00", bcoz of which it was
> disconnecting. Couldn't find out why my AP was sending this. Just let
> me know in case if you have answer for this.

Sometimes APs get confused if you try to reconnect to them too
frequently back to back .  APs suck, especially consumer ones.
Frequently, power-cycling the AP or waiting a minute between connection
attempts (like when debugging this sort of stuff) helps.

Dan

>  But it works only for hex keys as you mentioned earlier.
> 
>  Thanx.
> 
> -Raghu.
> 
> On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > On Tue, 2007-12-18 at 07:51 +0530, Raghavendra. S wrote:
> > > Hi,
> > >
> > >    One small correction, i am using wpa supplicant-0.5.9, with -Dwext
> > > on marvell 8686. It is working for EAP methods, WEP-open...etc.
> > >    Previously  I was using marvell ported wpa supplicant 0.5.7 with
> > > -Dmarvell. Now I tried with 0.5.7 also...for that also it is failing.
> >
> > You're going to need to get debug output from the driver to figure out
> > what is going wrong in the association bits.
> >
> > Turn on DBG_INFO (see wlan_defs.h) and reply with the output you get in
> > the kernel logs.
> >
> > Dan
> >
> >
> > > -Raghu.
> > >
> > > On 12/18/07, Raghavendra. S <raghavendra.akkasali at gmail.com> wrote:
> > > > Hi,
> > > >
> > > >  Plz find "iwlist eth0 scan" - result
> > > >
> > > > # /sbin/ifconfig eth0
> > > > eth0      Link encap:Ethernet  HWaddr 00:13:E0:9E:9B:2E
> > > >          UP BROADCAST 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:1000
> > > >          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> > > >          Interrupt:41
> > > >
> > > > # iwlist eth0 scan
> > > > eth0      Scan completed :
> > > >          Cell 01 - Address: 00:0F:CB:FE:2F:5F
> > > >                    ESSID:"3Com"
> > > >                    Mode:Managed
> > > >                    Frequency:2.412 GHz (Channel 1)
> > > >                    Quality:0/100  Signal level=-42 dBm  Noise level=-96 dBm
> > > >                    Encryption key:on
> > > >                    Bit Rates:54 Mb/s
> > > >
> > > >
> > > > -Raghu
> > > >
> > > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > > On Tue, 2007-12-18 at 07:40 +0530, Raghavendra. S wrote:
> > > > > > Hi,
> > > > > >
> > > > > >   Tried with hex key...still failing...
> > > > > > ----------------------------------------------------------------------------------
> > > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > > > ap_scan=1
> > > > > >
> > > > > > network={
> > > > > >         ssid="3Com"
> > > > > >         key_mgmt=NONE
> > > > > >         wep_key0=76F6B7657D
> > > > > >         wep_tx_keyidx=0
> > > > > >         auth_alg=SHARED
> > > > > > }
> > > > > > ----------------------------------------------------------------------------------------
> > > > > >
> > > > > > if you see below log...i have following three lines...
> > > > > >
> > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > >
> > > > > The Marvell vendor driver returns ENETUNREACH from SIOCSIWESSID adn
> > > > > SIOCSIWAP when it can't find the SSID to associate with, or when the
> > > > > security parameters of the network don't match what the driver has been
> > > > > configured for.  Basically, the configuration you have and the scan
> > > > > result that the driver has don't match up, or the network wasn't found
> > > > > during the pre-association scan.  Can you provide the output of 'iwlist
> > > > > ethX scan' for the 3Com network you want to connect to?
> > > > >
> > > > > Dan
> > > > >
> > > > > > is this a problem..or some thing else?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 12/18/07, Dan Williams <dcbw at redhat.com> wrote:
> > > > > > > On Tue, 2007-12-18 at 07:22 +0530, Raghavendra. S wrote:
> > > > > > > > Hi All,
> > > > > > > >
> > > > > > > >  I tried to test wpa supplicant for auth_alg=SHARED, but failing to
> > > > > > > > connect with AP,
> > > > > > > > My supplicant.conf file configuration is all below.
> > > > > > > >
> > > > > > > > ----------------------start------------------------------------------------------------------
> > > > > > > >
> > > > > > > > ctrl_interface=/var/run/wpa_supplicant
> > > > > > > >
> > > > > > > > network={
> > > > > > > >         ssid="3Com"
> > > > > > > >         key_mgmt=NONE
> > > > > > > >         auth_alg=SHARED
> > > > > > > >         wep_key0="raghu123456"
> > > > > > >
> > > > > > > Are you trying to use a WEP passphrase here?  I don't think
> > > > > > > wpa_supplicant supports WEP passphrase hashing.  Try a hex key here
> > > > > > > instead.
> > > > > > >
> > > > > > > Dan
> > > > > > >
> > > > > > >
> > > > > > > >         wep_tx_keyidx=0
> > > > > > > > }
> > > > > > > > ----------------------end-------------------------------------------------------------------
> > > > > > > >
> > > > > > > > I got following failure logs,
> > > > > > > >
> > > > > > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > > > > Initializing interface 'eth0' conf './files/wpa_supplicant.sharedWEP'
> > > > > > > > driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> > > > > > > > Configuration file './files/wpa_supplicant.sharedWEP' ->
> > > > > > > > '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > > > Reading configuration file '/mnt/nfs/./files/wpa_supplicant.sharedWEP'
> > > > > > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > > > > > Line: 4 - start of a new network block
> > > > > > > > ssid - hexdump_ascii(len=4):
> > > > > > > >      33 43 6f 6d                                       3Com
> > > > > > > > key_mgmt: 0x4
> > > > > > > > auth_alg: 0x2
> > > > > > > > wep_key0 - hexdump(len=11): [REMOVED]
> > > > > > > > wep_tx_keyidx=0 (0x0)
> > > > > > > > Priority group 0
> > > > > > > >    id=0 ssid='3Com'
> > > > > > > > Initializing interface (2) 'eth0'
> > > > > > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > > > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > > > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > > > > > EAP: EAP entering state DISABLED
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > > ioctl[SIOCSIWPMKSA]: Invalid argument
> > > > > > > > SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
> > > > > > > >   capabilities: key_mgmt 0x0 enc 0x3
> > > > > > > > WEXT: Operstate: linkmode=1, operstate=5
> > > > > > > > Own MAC address: 00:13:e0:9e:9b:2e
> > > > > > > > wpa_driver_wext_set_wpa
> > > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> > > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> > > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> > > > > > > > wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> > > > > > > > wpa_driver_wext_set_countermeasures
> > > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > > Setting scan request: 0 sec 100000 usec
> > > > > > > > Added interface eth0
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > > State: DISCONNECTED -> SCANNING
> > > > > > > > Starting AP scan (broadcast SSID)
> > > > > > > > Trying to get current scan results first without requesting a new scan
> > > > > > > > to speed up initial association
> > > > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > > > Scan results: 5
> > > > > > > > Selecting BSS from priority group 0
> > > > > > > > Try to find WPA-enabled AP
> > > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > Try to find non-WPA AP
> > > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - SSID mismatch
> > > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > > > Cancelling scan request
> > > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > > Automatic auth_alg selection: 0x1
> > > > > > > > Overriding auth_alg selection: 0x2
> > > > > > > > WPA: clearing AP WPA IE
> > > > > > > > WPA: clearing AP RSN IE
> > > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > > No keys have been configured - skip key clearing
> > > > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > > State: SCANNING -> ASSOCIATING
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > wpa_driver_wext_associate
> > > > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > > > Association request to the driver failed
> > > > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > > Added BSSID 00:0f:cb:fe:2f:5f into blacklist
> > > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > > Added BSSID 00:00:00:00:00:00 into blacklist
> > > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > > Authentication with 00:00:00:00:00:00 timed out.
> > > > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 2
> > > > > > > > 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
> > > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > > Setting scan request: 0 sec 0 usec
> > > > > > > > State: DISCONNECTED -> SCANNING
> > > > > > > > Starting AP scan (broadcast SSID)
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b19 len=8
> > > > > > > > Received 416 bytes of scan results (5 BSSes)
> > > > > > > > Scan results: 5
> > > > > > > > Selecting BSS from priority group 0
> > > > > > > > Try to find WPA-enabled AP
> > > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 2: 02:1b:77:03:c6:24 ssid='Enaru_Ser' wpa_ie_len=0 rsn_ie_len=0 caps=0x12
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 3: 02:e0:98:04:50:3e ssid='kk' wpa_ie_len=0 rsn_ie_len=0 caps=0x2
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > 4: 00:1c:10:21:94:bb ssid='linksysWRT150N' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
> > > > > > > >    skip - no WPA/RSN IE
> > > > > > > > Try to find non-WPA AP
> > > > > > > > 0: 00:90:4c:91:00:01 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    skip - SSID mismatch
> > > > > > > > 1: 00:0f:cb:fe:2f:5f ssid='3Com' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
> > > > > > > >    selected non-WPA AP 00:0f:cb:fe:2f:5f ssid='3Com'
> > > > > > > > Trying to associate with 00:0f:cb:fe:2f:5f (SSID='3Com' freq=2412 MHz)
> > > > > > > > Cancelling scan request
> > > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > > Automatic auth_alg selection: 0x1
> > > > > > > > Overriding auth_alg selection: 0x2
> > > > > > > > WPA: clearing AP WPA IE
> > > > > > > > WPA: clearing AP RSN IE
> > > > > > > > WPA: clearing own WPA/RSN IE
> > > > > > > > No keys have been configured - skip key clearing
> > > > > > > > wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=11
> > > > > > > > wpa_driver_wext_set_drop_unencrypted
> > > > > > > > State: SCANNING -> ASSOCIATING
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > wpa_driver_wext_associate
> > > > > > > > ioctl[SIOCSIWFREQ]: Operation not supported
> > > > > > > > ioctl[SIOCSIWESSID]: Network is unreachable
> > > > > > > > ioctl[SIOCSIWAP]: Network is unreachable
> > > > > > > > Association request to the driver failed
> > > > > > > > Setting authentication timeout: 5 sec 0 usec
> > > > > > > > EAPOL: External notification - portControl=ForceAuthorized
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b06 len=8
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > > BSSID 00:0f:cb:fe:2f:5f blacklist count incremented to 2
> > > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > > State: ASSOCIATING -> DISCONNECTED
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > > RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> > > > > > > > Wireless event: cmd=0x8b15 len=20
> > > > > > > > Wireless event: new AP: 00:00:00:00:00:00
> > > > > > > > BSSID 00:00:00:00:00:00 blacklist count incremented to 3
> > > > > > > > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > > > > > > > State: DISCONNECTED -> DISCONNECTED
> > > > > > > > wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> > > > > > > > WEXT: Operstate: linkmode=-1, operstate=5
> > > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > > EAPOL: External notification - portValid=0
> > > > > > > >
> > > > > > > >
> > > > > > > > Please tell me why it is failing?
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards & Thanks
> > > > Raghavendra. S
> > > >
> > >
> > >
> >
> >
> 
> 




From webmail.hce  Mon Dec 17 21:32:37 2007
From: webmail.hce (hce)
Date: Tue, 18 Dec 2007 16:32:37 +1100
Subject: Get connected and associated status
Message-ID: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>

Hi,

I am running wpa_supplicant 0.5.8. My application (a wifi client)
talks to wpa_supplicant via sockets to scan host APs. Is it possible
to get wifi card AP connected and associated status from
wpa_supplicant? If so, what is the command?

Thank you.

Kind Regards,

Jim



From raghavendra.akkasali  Mon Dec 17 22:58:26 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 12:28:26 +0530
Subject: Ad-Hoc problem...
Message-ID: <58a444250712172258u52cc663nf4c2b60ea6cb8365@mail.gmail.com>

Hi,

 I tried testing for Ad-Hoc mode support with wpa supplicant-0.6.1.

wpa_supplicant.conf has following entries.
------------------------------start--------------------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
        ssid="kk"
        mode=1
        frequency=2462
        key_mgmt=NONE
}
------------------------------start--------------------------------------------------------------

My iwlist scan result...

# iwlist eth0 scan
eth0      Scan completed :
          Cell 03 - Address: 02:E0:98:05:56:A6
                    ESSID:"kk" [3]
                    Mode:Ad-Hoc
                    Frequency:2.462 GHz (Channel 11)
                    Quality:0/100  Signal level=-58 dBm  Noise level=-98 dBm
                    Encryption key:off
                    Bit Rates:54 Mb/s


After enabling wpa supplicant as below, it is getting connected.
------------------------------------------------------------------
# ./wpa_supplicant -ieth0 -c ./files/wpa_supplicant.adhoc -Dwext -B
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWPMKSA]: Invalid argument
# iwconfig
eth0      MRVL-SD8686  ESSID:"kk" [3]
          Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: 02:E0:98:05:62:CB
          Bit Rate:54 Mb/s   Tx-Power=13 dBm
          Retry limit:8   RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:160
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:379693
          Tx excessive retries:234  Invalid misc:59670   Missed beacon:0



Now I modified ssid="gsdgdg" in wpa_supplicant.conf. still it is
getting connected to some MAC, which is not displayed by "iwlist eth0
scan"
Even tried by modifying frequency=162 or some junk value. now iwconfig
had yield following result

# iwconfig
eth0      MRVL-SD8686  ESSID:"gsdgdg"
          Mode:Ad-Hoc  Frequency:2.437 GHz  Cell: 02:24:F4:14:0B:E7
          Bit Rate:11 Mb/s   Tx-Power=18 dBm
          Retry limit:8   RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:160
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:621730
          Tx excessive retries:494  Invalid misc:125970   Missed beacon:0


Can any body tell me why this is happenning? Is it a bug in 0.6.1? or
I am doing something wrong.

-- 
Regards & Thanks
Raghavendra. S



From ged  Tue Dec 18 00:57:56 2007
From: ged (G.W. Haywood)
Date: Tue, 18 Dec 2007 08:57:56 +0000 (GMT)
Subject: HostAP Digest, Vol 56, Issue 31
In-Reply-To: <mailman.3095.1197947046.32411.hostap@shmoo.com>
References: <mailman.3095.1197947046.32411.hostap@shmoo.com>
Message-ID: <Pine.LNX.4.58.0712180853330.20094@mail3.jubileegroup.co.uk>

Hi Guys,

On Mon, 17 Dec 2007 Kel Modderman and Dan Williams wrote:

> > > > > > > > I got following failure logs,
> > > > > > > >
> > > > > > > > # ./wpa_supplicant -ieth0 -Dwext -c ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > > > >
> > > > > > > > yadayadayada
> > > > > > > >
> > > > > > > > [TWO HUNDRED lines more crap snipped]

Fercryinoutloud guys, this is a MAILING LIST!

I've had eleven copies of this crap this morning!

PLEASE TRIM YOUR POSTS!

--

73,
Ged.



From raghavendra.akkasali  Tue Dec 18 02:16:39 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 15:46:39 +0530
Subject: Doubt about EAP-SIM
Message-ID: <58a444250712180216p24deaa7amdd625082fca8fda4@mail.gmail.com>

Hi,

  I have some config parameter by name "pin" in wpa_supplicant.conf. I
would like to know, whether this is IMSI number or something else?

-- 
Regards & Thanks
Raghavendra. S



From raghavendra.akkasali  Tue Dec 18 06:32:46 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Tue, 18 Dec 2007 23:32:46 +0900
Subject: example wpa_supplicant.conf needed for EAP-AKA
Message-ID: <58a444250712180632r1419addap78b05530848619b9@mail.gmail.com>

Hi,

 I have a requirement to test EAP-AKA, can any one tell me where can I
get an example config file for EAP-AKA?

-- 
Regards & Thanks
Raghavendra. S



From dcbw  Tue Dec 18 06:58:56 2007
From: dcbw (Dan Williams)
Date: Tue, 18 Dec 2007 09:58:56 -0500
Subject: Get connected and associated status
In-Reply-To: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>
References: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>
Message-ID: <1197989936.31456.6.camel@localhost.localdomain>

On Tue, 2007-12-18 at 16:32 +1100, hce wrote:
> Hi,
> 
> I am running wpa_supplicant 0.5.8. My application (a wifi client)
> talks to wpa_supplicant via sockets to scan host APs. Is it possible
> to get wifi card AP connected and associated status from
> wpa_supplicant? If so, what is the command?

wpa_supplicant will send events back through the control socket that you
must read and match.

Dan





From dcbw  Tue Dec 18 07:01:18 2007
From: dcbw (Dan Williams)
Date: Tue, 18 Dec 2007 10:01:18 -0500
Subject: Ad-Hoc problem...
In-Reply-To: <58a444250712172258u52cc663nf4c2b60ea6cb8365@mail.gmail.com>
References: <58a444250712172258u52cc663nf4c2b60ea6cb8365@mail.gmail.com>
Message-ID: <1197990078.31456.9.camel@localhost.localdomain>

On Tue, 2007-12-18 at 12:28 +0530, Raghavendra. S wrote:
> Hi,
> 
>  I tried testing for Ad-Hoc mode support with wpa supplicant-0.6.1.
> 
> wpa_supplicant.conf has following entries.
> ------------------------------start--------------------------------------------------------------
> ctrl_interface=/var/run/wpa_supplicant
> ap_scan=2
> 
> network={
>         ssid="kk"
>         mode=1
>         frequency=2462
>         key_mgmt=NONE
> }
> ------------------------------start--------------------------------------------------------------
> 
> My iwlist scan result...
> 
> # iwlist eth0 scan
> eth0      Scan completed :
>           Cell 03 - Address: 02:E0:98:05:56:A6
>                     ESSID:"kk" [3]
>                     Mode:Ad-Hoc
>                     Frequency:2.462 GHz (Channel 11)
>                     Quality:0/100  Signal level=-58 dBm  Noise level=-98 dBm
>                     Encryption key:off
>                     Bit Rates:54 Mb/s
> 
> 
> After enabling wpa supplicant as below, it is getting connected.
> ------------------------------------------------------------------
> # ./wpa_supplicant -ieth0 -c ./files/wpa_supplicant.adhoc -Dwext -B
> ioctl[SIOCSIWPMKSA]: Invalid argument
> ioctl[SIOCSIWPMKSA]: Invalid argument
> # iwconfig
> eth0      MRVL-SD8686  ESSID:"kk" [3]
>           Mode:Ad-Hoc  Frequency:2.462 GHz  Cell: 02:E0:98:05:62:CB
>           Bit Rate:54 Mb/s   Tx-Power=13 dBm
>           Retry limit:8   RTS thr=2347 B   Fragment thr=2346 B
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:160
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:379693
>           Tx excessive retries:234  Invalid misc:59670   Missed beacon:0
> 
> 
> 
> Now I modified ssid="gsdgdg" in wpa_supplicant.conf. still it is
> getting connected to some MAC, which is not displayed by "iwlist eth0
> scan"

The driver invents a BSSID.  The MAC you see (starting with 02:xxxxxx)
is created by the driver because that's sort of how Ad-Hoc mode works.

> Even tried by modifying frequency=162 or some junk value. now iwconfig
> had yield following result
> 
> # iwconfig
> eth0      MRVL-SD8686  ESSID:"gsdgdg"
>           Mode:Ad-Hoc  Frequency:2.437 GHz  Cell: 02:24:F4:14:0B:E7
>           Bit Rate:11 Mb/s   Tx-Power=18 dBm
>           Retry limit:8   RTS thr=2347 B   Fragment thr=2346 B
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:160
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:621730
>           Tx excessive retries:494  Invalid misc:125970   Missed beacon:0
> 
> 
> Can any body tell me why this is happenning? Is it a bug in 0.6.1? or
> I am doing something wrong.

What's the actual problem here?  Its not clear to me what problem you're
really having...  It looks like it's working as expected.

Dan





From migdalis.mago  Tue Dec 18 09:32:23 2007
From: migdalis.mago (Migdalis Mago)
Date: Tue, 18 Dec 2007 09:32:23 -0800 (PST)
Subject: Migdalis Mago quiere ser tu amigo en Sonico
Message-ID: <20071218173223.978AD129FEA@mail.iocaine.com>

An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071218/1445514b/attachment.htm 


From Proger  Tue Dec 18 09:43:33 2007
From: Proger (Christian Fackroth)
Date: Tue, 18 Dec 2007 18:43:33 +0100
Subject: wpa_supplicant-0.6.1 IBSS Mode
Message-ID: <697941076@web.de>

Hi,

my task is to implement real IBSS mode in wpa_supplicant. The first step to compile the test_wpa.c I have already finished. Now I will test the WPA-NONE mode of wpa_supplicant but it don't work. I use the madwifi driver and configure two stations as follows:

wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
sudo iwconfig ath0 essid test-adhoc channel 6
sudo ifconfig ath0 192.168.1.x up

After the cells are merged I can transfer data between the two stations. Now I start wpa_supplicant on the stations with the follow configure file:

network={
        ssid="test-adhoc"
        mode=1
        frequency=2437
        proto=WPA
        key_mgmt=WPA-NONE
        pairwise=NONE
        group=CCMP
        psk="schluessel"
}

The connection can't established because wpa_supplicant show the message "... skip - no WPA/RSN IE" when it scanning. So my question is what do I wrong? Also it will be nice if somebody have additional hints for me which make it easier for me to realise my task.


I found in driver_wext.c in line 970 a instruction which makes in my mind no sence.

"if (wpa_driver_wext_set_mode(drv, 0) < 0) {"

Why is the driver always configured in managed mode? But I'm sure this is not the reason why WPA-NONE not work. ;-)


Regards,
 Christian

______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt testen! http://produkte.web.de/club/?mc=021130




From ken  Tue Dec 18 10:26:48 2007
From: ken (Ken Roberts)
Date: Tue, 18 Dec 2007 10:26:48 -0800
Subject: hostapd memory leak when connecting to Linux wpa_supplicant
In-Reply-To: <20071218030303.GZ5698@jm.kir.nu>
References: <4766C3B3.4030208@glaserelectronics.com>
	<20071218030303.GZ5698@jm.kir.nu>
Message-ID: <476810E8.8080000@glaserelectronics.com>

Jouni Malinen wrote:
> On Mon, Dec 17, 2007 at 10:45:07AM -0800, Ken Roberts wrote:
>
>   
>> hostapd v0.5.8
>> wpa_supplicant v0.5.8
>> madwifi v0.9.3.3
>> kernel 2.6.21.5 <http://2.6.21.5> (recompiled for minimal drivers)
>>
>> I've got 2 geode machines using the madwifi drivers. They worked great 
>> for about a week. Unfortunately, hostapd started eating ram and causing 
>> "out of memory and no programs to kill" errors on the ap running hostapd.
>>     
>
> How did you measure hostapd memory use? It sounds a bit odd if the
> kernel would not kill hostpad in such a case if the memory was indeed
> leaked in hostapd.
>   
After the first halt, I did the following:

root at host# while /bin/true; do grep ^Mem /proc/meminfo ; echo "Sleep 2 
seconds"; sleep 2; done

and watched the Memfree entry drop like a stone

>> When connecting to a Linux machine running wpa_supplicant, free ram 
>> started dropping like a rock until "out of memory" condition caused a 
>> system freeze.
>>     
>
> Have you looked at debug log from either hostapd or wpa_supplicant in
> this state? Do they show constant action (e.g., new
> associations/authentications)?
>   
Lots of debugging where it was toggling between associating -> 
disconnecting.

Problem change: apparently, the problem was the script was not telling 
wpa_supplicant which driver to use ( -Dmadwifi) when it called 
wpa_supplicant - which may have caused the memory problem.

Now, unfortunately, it's not connecting at all - which is where I was 
about a month ago when dealing with the eapol_version issue (among other 
things).

So - back to the configuration setup again and see what's changed.




From dcbw  Tue Dec 18 10:41:41 2007
From: dcbw (Dan Williams)
Date: Tue, 18 Dec 2007 13:41:41 -0500
Subject: wpa_supplicant-0.6.1 IBSS Mode
In-Reply-To: <697941076@web.de>
References: <697941076@web.de>
Message-ID: <1198003301.6020.2.camel@localhost.localdomain>

On Tue, 2007-12-18 at 18:43 +0100, Christian Fackroth wrote:
> Hi,
> 
> my task is to implement real IBSS mode in wpa_supplicant. The first step to compile the test_wpa.c I have already finished. Now I will test the WPA-NONE mode of wpa_supplicant but it don't work. I use the madwifi driver and configure two stations as follows:
> 
> wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
> sudo iwconfig ath0 essid test-adhoc channel 6
> sudo ifconfig ath0 192.168.1.x up
> 
> After the cells are merged I can transfer data between the two stations. Now I start wpa_supplicant on the stations with the follow configure file:
> 
> network={
>         ssid="test-adhoc"
>         mode=1
>         frequency=2437
>         proto=WPA
>         key_mgmt=WPA-NONE
>         pairwise=NONE
>         group=CCMP
>         psk="schluessel"
> }
> 
> The connection can't established because wpa_supplicant show the message "... skip - no WPA/RSN IE" when it scanning. So my question is what do I wrong? Also it will be nice if somebody have additional hints for me which make it easier for me to realise my task.

You're probably not setting ap_scan=2:

# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
# to be set to 2 for IBSS. WPA-None requires following network block options:
# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
# both), and psk must also be set.

This is the comment in the 'mode' section of the example
wpa_supplicant.conf config file.

> I found in driver_wext.c in line 970 a instruction which makes in my mind no sence.
> 
> "if (wpa_driver_wext_set_mode(drv, 0) < 0) {"
> 
> Why is the driver always configured in managed mode? But I'm sure this is not the reason why WPA-NONE not work. ;-)

That part shouldn't really matter, because it's only set to managed when
the card is initialized.  The _real_ mode you request is set in the
'associate' hook below around line 1946.  That's the only mode set that
really matters.

Dan





From linux-ra  Tue Dec 18 13:15:17 2007
From: linux-ra (Robert Allerstorfer)
Date: Tue, 18 Dec 2007 22:15:17 +0100
Subject: Operation "wpa_driver_wext_set_countermeasures" not supported with
	b43 driver
Message-ID: <910568798.20071218221517@anet.at>

Hi,

I am trying to connect with my iBook G4 to my WPA2 access point under
Fedora 8. It works fine with the same laptop booted into MacOSX,
however it never worked so far with Fedora. The WLAN card is based on
the Broadcom 4306 chipset with the IEEE 802.11 MAC Core revision of 5
- thus the kernel (2.6.23.9-90.fc8) autoloads the b43 driver. The
required firmware has been provided.

When I start wpa_supplicant (v0.5.7) with
wpa_supplicant -iwlan0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf -dd > wpa_supplicant.log
the following will be written to STDERR:
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 -

Without redirecting STDOUT to a file, I see that the last output
before the "ioctl[SIOCSIWAUTH]: Operation not supported" line was:
wpa_driver_wext_set_countermeasures

Does this mean that the b43 driver does not support a command issued
by wpa_supplicant?

Thanks,
rob.





From webmail.hce  Tue Dec 18 16:16:21 2007
From: webmail.hce (hce)
Date: Wed, 19 Dec 2007 11:16:21 +1100
Subject: Name server IP address
Message-ID: <95455e980712181616o73f3453crc2c38c410b3c9d6e@mail.gmail.com>

Hi,

I am using dhcp client to get assigned IP address from the server
after calling wpa_supplicant. But, it seems that the dhcp client could
not get IP address without a nameserver in resolv.conf. I can manully
add a nameserver to the resolv.conf on my home AP. But, if I take my
device to the street, I don't have knowledge of the nameserver for
that street AP. So, the question are:

(a) How can I create the nameserver in resolv.conf dynamically before
calling the dhcp client?

(b) The wpa_supplicant does not need an IP address or nameserver to
scan the APs, can the wpa_supplicant get the nameserver or IP address
from the scanning AP process?

Thank you.

Kind Regards,

Jim



From bhasker  Tue Dec 18 17:56:49 2007
From: bhasker (Bhasker C V)
Date: Wed, 19 Dec 2007 07:26:49 +0530 (IST)
Subject: Name server IP address
In-Reply-To: <95455e980712181616o73f3453crc2c38c410b3c9d6e@mail.gmail.com>
References: <95455e980712181616o73f3453crc2c38c410b3c9d6e@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0712190722220.3054@s1.unixindia.com>



On Wed, 19 Dec 2007, hce wrote:

> Hi,
>
> I am using dhcp client to get assigned IP address from the server
> after calling wpa_supplicant. But, it seems that the dhcp client could
> not get IP address without a nameserver in resolv.conf. I can manully
> add a nameserver to the resolv.conf on my home AP. But, if I take my
> device to the street, I don't have knowledge of the nameserver for
> that street AP. So, the question are:
>
> (a) How can I create the nameserver in resolv.conf dynamically before
> calling the dhcp client?
  The nameserver information present in the AP must be needed by the
AP only and not used in the process of association.
  However, DHCP is configured to send the nameserver information. I think
the DHCP server may be misconfigured. Can you try connecting the machine
through a wired network ?  The result may be same. dhcpd.conf file must
have an entry
  option domain-name-servers   a.b.c.d;

>
> (b) The wpa_supplicant does not need an IP address or nameserver to
> scan the APs, can the wpa_supplicant get the nameserver or IP address
> from the scanning AP process?
wpa supplicant establishes connection at the Layer 2 of OSI layer and
so there is no need for wpa_supplicant to be aware of the higher layers
like layer 3 where the ip address comes into picture.
>

Try troubleshooting the DHCP server...

> Thank you.
>
> Kind Regards,
>
> Jim
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>



From j  Tue Dec 18 18:10:52 2007
From: j (Jouni Malinen)
Date: Tue, 18 Dec 2007 18:10:52 -0800
Subject: hostapd memory leak when connecting to Linux wpa_supplicant
In-Reply-To: <476810E8.8080000@glaserelectronics.com>
References: <4766C3B3.4030208@glaserelectronics.com>
	<20071218030303.GZ5698@jm.kir.nu>
	<476810E8.8080000@glaserelectronics.com>
Message-ID: <20071219021052.GD5698@jm.kir.nu>

On Tue, Dec 18, 2007 at 10:26:48AM -0800, Ken Roberts wrote:

> After the first halt, I did the following:
> 
> root at host# while /bin/true; do grep ^Mem /proc/meminfo ; echo "Sleep 2 
> seconds"; sleep 2; done
> 
> and watched the Memfree entry drop like a stone

That doesn't sound like something that would indicate anything
particular about hostapd. Unless there is a clear sign that the hostapd
process is using more memory, I would take a look at the madwifi driver
that is taking care of associations.

-- 
Jouni Malinen                                            PGP id EFC895FA



From webmail.hce  Tue Dec 18 19:08:02 2007
From: webmail.hce (hce)
Date: Wed, 19 Dec 2007 14:08:02 +1100
Subject: Name server IP address
In-Reply-To: <Pine.LNX.4.64.0712190722220.3054@s1.unixindia.com>
References: <95455e980712181616o73f3453crc2c38c410b3c9d6e@mail.gmail.com>
	<Pine.LNX.4.64.0712190722220.3054@s1.unixindia.com>
Message-ID: <95455e980712181908y5de9706fr22cecfe902236ff4@mail.gmail.com>

On Dec 19, 2007 12:56 PM, Bhasker C V <bhasker at unixindia.com> wrote:
>
>
> On Wed, 19 Dec 2007, hce wrote:
>
> > Hi,
> >
> > I am using dhcp client to get assigned IP address from the server
> > after calling wpa_supplicant. But, it seems that the dhcp client could
> > not get IP address without a nameserver in resolv.conf. I can manully
> > add a nameserver to the resolv.conf on my home AP. But, if I take my
> > device to the street, I don't have knowledge of the nameserver for
> > that street AP. So, the question are:
> >
> > (a) How can I create the nameserver in resolv.conf dynamically before
> > calling the dhcp client?
>   The nameserver information present in the AP must be needed by the
> AP only and not used in the process of association.
>   However, DHCP is configured to send the nameserver information. I think
> the DHCP server may be misconfigured. Can you try connecting the machine
> through a wired network ?  The result may be same. dhcpd.conf file must
> have an entry
>   option domain-name-servers   a.b.c.d;

I am using a NETGEAR AP model WGR614. I set following to the AP:

Tick Use Router as DHCP Server
Starting IP address 192.168.2.2
Ending IP address 192.168.2.51.

I guess it is configured well. But the dhcp process from my wifi
device will be failed if the nameserver on resolv.conf is empty. Am I
missing something for configuing the DHCP server correctly for this
AP?

You are right, that the DHCP server in a wired network have an entry
of "option domain-name-servers   a.b.c.d". I guess the DHCP process
updates the resolv.conf in a wired network. The question is why the
dhcp process failed to create a resolv.conf in a wifi network? How
does other poeple resolve this issue?

> >
> > (b) The wpa_supplicant does not need an IP address or nameserver to
> > scan the APs, can the wpa_supplicant get the nameserver or IP address
> > from the scanning AP process?
> wpa supplicant establishes connection at the Layer 2 of OSI layer and
> so there is no need for wpa_supplicant to be aware of the higher layers
> like layer 3 where the ip address comes into picture.
> >
>
> Try troubleshooting the DHCP server...

Don't know how to do it?

Thank you.

Kind Regards,

Jim



From raghavendra.akkasali  Wed Dec 19 01:42:02 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Wed, 19 Dec 2007 15:12:02 +0530
Subject: EAP-SIM failing...
Message-ID: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>

Hi All,

 I am trying to test EAP-SIM. using wpa supplicant 0.6.1.
I have following supplicant.conf file entry.
-----------------------start--------------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=0


# EAP-SIM with a GSM SIM or USIM
network={
#       ssid="3Com"
        key_mgmt=WPA-EAP
        eap=SIM
        pin="1234"
        pcsc=""
        eapol_flags=0
}
-----------------------end--------------------------------------------------------

I got following failure logs.

# ifconfig eth0 up
# ./wpa_supplicant -Dwext -ieth0 -c ./files/wpa_supplicant.eap-sim -w -ddd
Initializing interface 'eth0' conf './files/wpa_supplicant.eap-sim'
driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file './files/wpa_supplicant.eap-sim' ->
'/mnt/nfs/./files/wpa_supplicant.eap-sim'
Reading configuration file '/mnt/nfs/./files/wpa_supplicant.eap-sim'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=0
Line: 7 - start of a new network block
key_mgmt: 0x1
eap methods - hexdump(len=16): 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00 00
pin - hexdump_ascii(len=4): [REMOVED]
pcsc - hexdump_ascii(len=0):
eapol_flags=0 (0x0)
Priority group 0
   id=0 ssid=''
Initializing interface (2) 'eth0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Interface eth0 set UP - waiting a second for the driver to complete
initialization
ioctl[SIOCSIWPMKSA]: Invalid argument
SIOCGIWRANGE: WE(compiled)=22 WE(source)=15 enc_capa=0x0
  capabilities: key_mgmt 0x0 enc 0x3
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:13:e0:9e:9b:2e
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
ioctl[SIOCSIWPMKSA]: Invalid argument
Setting scan request: 0 sec 100000 usec
Added interface eth0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
Selected network is configured to use SIM (sim=1 aka=0) - initialize PCSC
Failed to initialize SIM (pcsc-lite)
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
BSSID not set when trying to send an EAPOL frame
Using the source address of the last received EAPOL frame
00:00:00:00:00:00 as the EAPOL destination
TX EAPOL: dst=00:00:00:00:00:00
TX EAPOL - hexdump(len=4): 01 01 00 00
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
Selected network is configured to use SIM (sim=1 aka=0) - initialize PCSC
Failed to initialize SIM (pcsc-lite)
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
BSSID not set when trying to send an EAPOL frame
Using the source address of the last received EAPOL frame
00:00:00:00:00:00 as the EAPOL destination
TX EAPOL: dst=00:00:00:00:00:00
TX EAPOL - hexdump(len=4): 01 01 00 00


I configured AP for WPA-EAP. I am not getting any logs at RADIUS
server side. I am using freeradius.

-- 
Regards & Thanks
Raghavendra. S



From kel  Wed Dec 19 02:53:57 2007
From: kel (Kel Modderman)
Date: Wed, 19 Dec 2007 20:53:57 +1000
Subject: HostAP Digest, Vol 56, Issue 31
In-Reply-To: <Pine.LNX.4.58.0712180853330.20094@mail3.jubileegroup.co.uk>
References: <mailman.3095.1197947046.32411.hostap@shmoo.com>
	<Pine.LNX.4.58.0712180853330.20094@mail3.jubileegroup.co.uk>
Message-ID: <200712192053.57800.kel@otaku42.de>

Hi,

On Tuesday 18 December 2007 18:57:56 G.W. Haywood wrote:
> Hi Guys,
>
> On Mon, 17 Dec 2007 Kel Modderman and Dan Williams wrote:
> > > > > > > > > I got following failure logs,
> > > > > > > > >
> > > > > > > > > # ./wpa_supplicant -ieth0 -Dwext -c
> > > > > > > > > ./files/wpa_supplicant.sharedWEP -w -ddd
> > > > > > > > >
> > > > > > > > > yadayadayada
> > > > > > > > >
> > > > > > > > > [TWO HUNDRED lines more crap snipped]
>
> Fercryinoutloud guys, this is a MAILING LIST!
>
> I've had eleven copies of this crap this morning!
>
> PLEASE TRIM YOUR POSTS!

This makes your last 3 posts to this list to tell people to shorten their 
emails for the sake of your quick perusal over the digest. Now I realise why 
you wrote the above like you did, you must be severely frustrated by this 
issue. I feel sympathy for you, because you wasted time due to our discussion 
on this list due to excess email content, and will endeavour to make every 
effort to trim each email I write so as to not waste your precious time.

Thanks for making it a nice experience to conduct discussion on this list!

Thanks! Kel.



From Proger  Wed Dec 19 04:57:39 2007
From: Proger (Christian Fackroth)
Date: Wed, 19 Dec 2007 13:57:39 +0100
Subject: wpa_supplicant-0.6.1 IBSS Mode
Message-ID: <699783167@web.de>

Cheers Dan!

> > Hi,
> > 
> > my task is to implement real IBSS mode in wpa_supplicant. The first step to compile the test_wpa.c I have already finished. Now I will test the WPA-NONE mode of wpa_supplicant but it don't work. I use the madwifi driver and configure two stations as follows:
> > 
> > wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
> > sudo iwconfig ath0 essid test-adhoc channel 6
> > sudo ifconfig ath0 192.168.1.x up
> > 
> > After the cells are merged I can transfer data between the two stations. Now I start wpa_supplicant on the stations with the follow configure file:
> > 
> > network={
> >         ssid="test-adhoc"
> >         mode=1
> >         frequency=2437
> >         proto=WPA
> >         key_mgmt=WPA-NONE
> >         pairwise=NONE
> >         group=CCMP
> >         psk="schluessel"
> > }
> > 
> > The connection can't established because wpa_supplicant show the message "... skip - no WPA/RSN IE" when it scanning. So my question is what do I wrong? Also it will be nice if somebody have additional hints for me which make it easier for me to realise my task.
> 
> You're probably not setting ap_scan=2:
> 
> # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
> # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
> # to be set to 2 for IBSS. WPA-None requires following network block options:
> # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
> # both), and psk must also be set.
> 
> This is the comment in the 'mode' section of the example
> wpa_supplicant.conf config file.
> 

It is correct I forgot to configure the scan mode. Anyway WPA-NONE don't work. :-/

> > I found in driver_wext.c in line 970 a instruction which makes in my mind no sence.
> > 
> > "if (wpa_driver_wext_set_mode(drv, 0) < 0) {"
> > 
> > Why is the driver always configured in managed mode? But I'm sure this is not the reason why WPA-NONE not work. ;-)
> 
> That part shouldn't really matter, because it's only set to managed when
> the card is initialized.  The _real_ mode you request is set in the
> 'associate' hook below around line 1946.  That's the only mode set that
> really matters.

I agree with you.


My complete config file look as follows:

# mode: IEEE 802.11 operation mode
# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
# 1 = IBSS (ad-hoc, peer-to-peer)
# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
# to be set to 2 for IBSS. WPA-None requires following network block options:
# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
# both), and psk must also be set.

ap_scan=2

network={
        ssid="test-adhoc"
        mode=1
        frequency=2437
        proto=WPA
        key_mgmt=WPA-NONE
        pairwise=NONE
        group=CCMP
        psk="schluessel"
}

If I start wpa_supplicant with the command line: 

> ./wpa_supplicant -i ath0 -D madwifi -c /scratch/wpa_none.conf -dd

I get follows debug information for the two stations only with different own MAC addresses:

Initializing interface 'ath0' conf '/scratch/wpa_none.conf' driver 'madwifi' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/scratch/wpa_none.conf' -> '/scratch/wpa_none.conf'
Reading configuration file '/scratch/wpa_none.conf'
ap_scan=2
Line: 12 - start of a new network block
mode=1 (0x1)
proto: 0x1
key_mgmt: 0x10
pairwise: 0x1
group: 0x10
PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid=''
Initializing interface (2) 'ath0'
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5

Own MAC address: 06:15:6d:10:23:17

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
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
Added interface ath0
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID ''
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 16 pairwise 1 key_mgmt 16 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK NONE
WPA: using KEY_MGMT WPA-NONE
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 00 01 00 00 50 f2 00
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_madwifi_associate
ioctl[IEEE80211_IOCTL_SETOPTIE]: Invalid argument
Association request to the driver failed
wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
Cancelling authentication timeout
State: ASSOCIATING -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (auth) [id=-1 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
WEXT: Operstate: linkmode=-1, operstate=6
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added

Could it be that there is a problem with the driver interface?

Regards,
 Christian

_______________________________________________________________________
Jetzt neu! Sch?tzen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220




From Proger  Wed Dec 19 06:16:01 2007
From: Proger (Christian Fackroth)
Date: Wed, 19 Dec 2007 15:16:01 +0100
Subject: wpa_supplicant-0.6.1 IBSS Mode
Message-ID: <699957138@web.de>

Hi,

I solved the problem. The problem is the driver interface of madwifi.
I changed it to the generic Linux wireless extension and it works fine. :-)

Regards,
 Christian

> Cheers Dan!
> 
> > > Hi,
> > > 
> > > my task is to implement real IBSS mode in wpa_supplicant. The first step to compile the test_wpa.c I have already finished. Now I will test the WPA-NONE mode of wpa_supplicant but it don't work. I use the madwifi driver and configure two stations as follows:
> > > 
> > > wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
> > > sudo iwconfig ath0 essid test-adhoc channel 6
> > > sudo ifconfig ath0 192.168.1.x up
> > > 
> > > After the cells are merged I can transfer data between the two stations. Now I start wpa_supplicant on the stations with the follow configure file:
> > > 
> > > network={
> > >         ssid="test-adhoc"
> > >         mode=1
> > >         frequency=2437
> > >         proto=WPA
> > >         key_mgmt=WPA-NONE
> > >         pairwise=NONE
> > >         group=CCMP
> > >         psk="schluessel"
> > > }
> > > 
> > > The connection can't established because wpa_supplicant show the message "... skip - no WPA/RSN IE" when it scanning. So my question is what do I wrong? Also it will be nice if somebody have additional hints for me which make it easier for me to realise my task.
> > 
> > You're probably not setting ap_scan=2:
> > 
> > # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
> > # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
> > # to be set to 2 for IBSS. WPA-None requires following network block options:
> > # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
> > # both), and psk must also be set.
> > 
> > This is the comment in the 'mode' section of the example
> > wpa_supplicant.conf config file.
> > 
> 
> It is correct I forgot to configure the scan mode. Anyway WPA-NONE don't work. :-/
> 
> > > I found in driver_wext.c in line 970 a instruction which makes in my mind no sence.
> > > 
> > > "if (wpa_driver_wext_set_mode(drv, 0) < 0) {"
> > > 
> > > Why is the driver always configured in managed mode? But I'm sure this is not the reason why WPA-NONE not work. ;-)
> > 
> > That part shouldn't really matter, because it's only set to managed when
> > the card is initialized.  The _real_ mode you request is set in the
> > 'associate' hook below around line 1946.  That's the only mode set that
> > really matters.
> 
> I agree with you.
> 
> 
> My complete config file look as follows:
> 
> # mode: IEEE 802.11 operation mode
> # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
> # 1 = IBSS (ad-hoc, peer-to-peer)
> # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
> # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
> # to be set to 2 for IBSS. WPA-None requires following network block options:
> # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
> # both), and psk must also be set.
> 
> ap_scan=2
> 
> network={
>         ssid="test-adhoc"
>         mode=1
>         frequency=2437
>         proto=WPA
>         key_mgmt=WPA-NONE
>         pairwise=NONE
>         group=CCMP
>         psk="schluessel"
> }
> 
> If I start wpa_supplicant with the command line: 
> 
> > ./wpa_supplicant -i ath0 -D madwifi -c /scratch/wpa_none.conf -dd
> 
> I get follows debug information for the two stations only with different own MAC addresses:
> 
> Initializing interface 'ath0' conf '/scratch/wpa_none.conf' driver 'madwifi' ctrl_interface 'N/A' bridge 'N/A'
> Configuration file '/scratch/wpa_none.conf' -> '/scratch/wpa_none.conf'
> Reading configuration file '/scratch/wpa_none.conf'
> ap_scan=2
> Line: 12 - start of a new network block
> mode=1 (0x1)
> proto: 0x1
> key_mgmt: 0x10
> pairwise: 0x1
> group: 0x10
> PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
> PSK (from passphrase) - hexdump(len=32): [REMOVED]
> Priority group 0
>    id=0 ssid=''
> Initializing interface (2) 'ath0'
> ioctl[SIOCSIWMODE]: Invalid argument
> Could not configure driver to use managed mode
> SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
>   capabilities: key_mgmt 0xf enc 0xf
> WEXT: Operstate: linkmode=1, operstate=5
> 
> Own MAC address: 06:15:6d:10:23:17
> 
> 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
> RSN: flushing PMKID list in the driver
> Setting scan request: 0 sec 100000 usec
> Added interface ath0
> RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> State: DISCONNECTED -> SCANNING
> Trying to associate with SSID ''
> Cancelling scan request
> WPA: clearing own WPA/RSN IE
> Automatic auth_alg selection: 0x1
> WPA: No WPA/RSN IE available from association info
> WPA: Set cipher suites based on configuration
> WPA: Selected cipher suites: group 16 pairwise 1 key_mgmt 16 proto 1
> WPA: clearing AP WPA IE
> WPA: clearing AP RSN IE
> WPA: using GTK CCMP
> WPA: using PTK NONE
> WPA: using KEY_MGMT WPA-NONE
> WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 00 01 00 00 50 f2 00
> No keys have been configured - skip key clearing
> wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
> wpa_driver_madwifi_set_drop_unencrypted: enabled=1
> State: SCANNING -> ASSOCIATING
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> wpa_driver_madwifi_associate
> ioctl[IEEE80211_IOCTL_SETOPTIE]: Invalid argument
> Association request to the driver failed
> wpa_driver_madwifi_set_key: alg=CCMP key_idx=0 set_tx=1 seq_len=6 key_len=16
> Cancelling authentication timeout
> State: ASSOCIATING -> COMPLETED
> CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (auth) [id=-1 id_str=]
> wpa_driver_wext_set_operstate: operstate 0->1 (UP)
> WEXT: Operstate: linkmode=-1, operstate=6
> RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
> WEXT: Operstate: linkmode=-1, operstate=6
> Wireless event: cmd=0x8b1a len=8
> RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> 
> Could it be that there is a problem with the driver interface?
> 
> Regards,
>  Christian
> 


_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066




From ken  Wed Dec 19 09:32:39 2007
From: ken (Ken Roberts)
Date: Wed, 19 Dec 2007 09:32:39 -0800
Subject: hostapd memory leak when connecting to Linux wpa_supplicant
In-Reply-To: <20071219021052.GD5698@jm.kir.nu>
References: <4766C3B3.4030208@glaserelectronics.com>	<20071218030303.GZ5698@jm.kir.nu>	<476810E8.8080000@glaserelectronics.com>
	<20071219021052.GD5698@jm.kir.nu>
Message-ID: <476955B7.4030805@glaserelectronics.com>

Jouni Malinen wrote:
> On Tue, Dec 18, 2007 at 10:26:48AM -0800, Ken Roberts wrote:
>
>   
>> After the first halt, I did the following:
>>
>> root at host# while /bin/true; do grep ^Mem /proc/meminfo ; echo "Sleep 2 
>> seconds"; sleep 2; done
>>
>> and watched the Memfree entry drop like a stone
>>     
>
> That doesn't sound like something that would indicate anything
> particular about hostapd. Unless there is a clear sign that the hostapd
> process is using more memory, I would take a look at the madwifi driver
> that is taking care of associations.
>
>   

Except the memory issue only popped up when I started hostapd. When I 
ran the same system as a station and wpa_supplicant, there were no 
memory issues - just connectivity issues between wpa_supplicant and  
hostapd.

Another issue that may be indicative of a non-hostapd issue is the flash 
drive I'm using may be getting flakey as well (crc errors on loading the 
kernel from a warm boot, for one).

At any rate, I updated the madwifi driver to the latest revision (r3065) 
and it appears to have fixed the memory and connectivity problem - still 
looking at some connectivity issues, but I'm still checking on that.





From Proger  Wed Dec 19 10:26:19 2007
From: Proger (Proger at web.de)
Date: Wed, 19 Dec 2007 19:26:19 +0100
Subject: 802.11i support in IBSS mode
Message-ID: <700422215@web.de>

Sorry,

my last post was rubbish! :-/
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsst?rkeren E-Mail-Postfach!		
Mehr Infos unter http://produkte.web.de/club/?mc=021131




From webmail.hce  Wed Dec 19 15:41:57 2007
From: webmail.hce (hce)
Date: Thu, 20 Dec 2007 10:41:57 +1100
Subject: Get connected and associated status
In-Reply-To: <1197989936.31456.6.camel@localhost.localdomain>
References: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>
	<1197989936.31456.6.camel@localhost.localdomain>
Message-ID: <95455e980712191541m16dd0c59qe2bf4a97d52e2e1b@mail.gmail.com>

On Dec 19, 2007 1:58 AM, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-12-18 at 16:32 +1100, hce wrote:
> > Hi,
> >
> > I am running wpa_supplicant 0.5.8. My application (a wifi client)
> > talks to wpa_supplicant via sockets to scan host APs. Is it possible
> > to get wifi card AP connected and associated status from
> > wpa_supplicant? If so, what is the command?
>
> wpa_supplicant will send events back through the control socket that you
> must read and match.

Thanks Dan. I've searched but could not find a proper document on how
to use control socket in applications to get events from the
wpa_supplicant. Would you please point me a document or an example?

Thank you.

Kind Regards,

Jim



From j  Wed Dec 19 18:25:46 2007
From: j (Jouni Malinen)
Date: Wed, 19 Dec 2007 18:25:46 -0800
Subject: Doubt about EAP-SIM
In-Reply-To: <58a444250712180216p24deaa7amdd625082fca8fda4@mail.gmail.com>
References: <58a444250712180216p24deaa7amdd625082fca8fda4@mail.gmail.com>
Message-ID: <20071220022546.GE5698@jm.kir.nu>

On Tue, Dec 18, 2007 at 03:46:39PM +0530, Raghavendra. S wrote:

>   I have some config parameter by name "pin" in wpa_supplicant.conf. I
> would like to know, whether this is IMSI number or something else?

"pin" parameter can be used to configure the PIN code for the SIM card
(if the card is marked to require PIN for authentication operations).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 19 18:26:35 2007
From: j (Jouni Malinen)
Date: Wed, 19 Dec 2007 18:26:35 -0800
Subject: example wpa_supplicant.conf needed for EAP-AKA
In-Reply-To: <58a444250712180632r1419addap78b05530848619b9@mail.gmail.com>
References: <58a444250712180632r1419addap78b05530848619b9@mail.gmail.com>
Message-ID: <20071220022635.GF5698@jm.kir.nu>

On Tue, Dec 18, 2007 at 11:32:46PM +0900, Raghavendra. S wrote:

>  I have a requirement to test EAP-AKA, can any one tell me where can I
> get an example config file for EAP-AKA?

network={
	ssid="foo"
        key_mgmt=WPA-EAP
	eap=AKA
	pin="1234"
	pcsc=""
}

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 19 18:28:10 2007
From: j (Jouni Malinen)
Date: Wed, 19 Dec 2007 18:28:10 -0800
Subject: EAP-SIM failing...
In-Reply-To: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>
References: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>
Message-ID: <20071220022810.GG5698@jm.kir.nu>

On Wed, Dec 19, 2007 at 03:12:02PM +0530, Raghavendra. S wrote:

>  I am trying to test EAP-SIM. using wpa supplicant 0.6.1.

> Selected network is configured to use SIM (sim=1 aka=0) - initialize PCSC
> Failed to initialize SIM (pcsc-lite)

It looks like initialization of the pcsc-lite connection for SIM
operation is failing. Which pcsc-lite version are you using? Have you
verified that pcscd sees the SIM card properly?

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 19 18:32:22 2007
From: j (Jouni Malinen)
Date: Wed, 19 Dec 2007 18:32:22 -0800
Subject: Get connected and associated status
In-Reply-To: <95455e980712191541m16dd0c59qe2bf4a97d52e2e1b@mail.gmail.com>
References: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>
	<1197989936.31456.6.camel@localhost.localdomain>
	<95455e980712191541m16dd0c59qe2bf4a97d52e2e1b@mail.gmail.com>
Message-ID: <20071220023222.GH5698@jm.kir.nu>

On Thu, Dec 20, 2007 at 10:41:57AM +1100, hce wrote:

> Thanks Dan. I've searched but could not find a proper document on how
> to use control socket in applications to get events from the
> wpa_supplicant. Would you please point me a document or an example?

How and where did you search for this information? I was hoping that the
documentation was easily available, but if not, it would be useful to
get more details so that this can be made easier to find.

The developers' documentation for wpa_supplicant has a page about the
use of control interface at
http://w1.fi/wpa_supplicant/devel/ctrl_iface_page.html

Both wpa_cli and wpa_gui source code is included with wpa_supplicant to
give an example on how the control interface is used.

-- 
Jouni Malinen                                            PGP id EFC895FA



From webmail.hce  Wed Dec 19 18:44:16 2007
From: webmail.hce (hce)
Date: Thu, 20 Dec 2007 13:44:16 +1100
Subject: Does ssid="any" work?
Message-ID: <95455e980712191844i7b872f48t5aaa3bfd8090356b@mail.gmail.com>

Hi,

I am running wpa_supplicant version 0.5.8. If I set ssid="MyAP", it
works. But, if I set ssid="any" in wpa_supplicant.conf, then calling
wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant.conf &", it
failed, stopped at "WEXT auth param 5 value 0x1 - Added interface
eth1Hack: state = 0x7". What I was missing?

Basically, I don't want to specify a hardcoded ssid, so I can bring
the wifi up in a street open AP. Is it possible, or it is not
supported?

Thank you.

Kind Regards,

Jim



From webmail.hce  Wed Dec 19 19:24:21 2007
From: webmail.hce (hce)
Date: Thu, 20 Dec 2007 14:24:21 +1100
Subject: Get connected and associated status
In-Reply-To: <20071220023222.GH5698@jm.kir.nu>
References: <95455e980712172132m61b9cdebgaa9caf2b590f0b88@mail.gmail.com>
	<1197989936.31456.6.camel@localhost.localdomain>
	<95455e980712191541m16dd0c59qe2bf4a97d52e2e1b@mail.gmail.com>
	<20071220023222.GH5698@jm.kir.nu>
Message-ID: <95455e980712191924l4747d34cre5526d06a3649911@mail.gmail.com>

On Dec 20, 2007 1:32 PM, Jouni Malinen <j at w1.fi> wrote:
> On Thu, Dec 20, 2007 at 10:41:57AM +1100, hce wrote:
>
> > Thanks Dan. I've searched but could not find a proper document on how
> > to use control socket in applications to get events from the
> > wpa_supplicant. Would you please point me a document or an example?
>
> How and where did you search for this information? I was hoping that the
> documentation was easily available, but if not, it would be useful to
> get more details so that this can be made easier to find.
>
> The developers' documentation for wpa_supplicant has a page about the
> use of control interface at
> http://w1.fi/wpa_supplicant/devel/ctrl_iface_page.html
>
> Both wpa_cli and wpa_gui source code is included with wpa_supplicant to
> give an example on how the control interface is used.

Thanks  Jouni and the link information. I was searching control socket
information from google....

Anyway, from Dan's  comments:
"wpa_supplicant will send events back through the control socket that
you must read and match"

Does the wpa_supplicant provide a control socket we can register our
callback to get events asynchronously? Or, should I use a select
mechanism to get events from control interface?

What are event names and event descriptions that my application can
use? It doesn't look like above link providing that information, I
might blindly miss them?

Thank you.

Kind Regards,

Jim



From j  Wed Dec 19 19:28:37 2007
From: j (Jouni Malinen)
Date: Wed, 19 Dec 2007 19:28:37 -0800
Subject: Does ssid="any" work?
In-Reply-To: <95455e980712191844i7b872f48t5aaa3bfd8090356b@mail.gmail.com>
References: <95455e980712191844i7b872f48t5aaa3bfd8090356b@mail.gmail.com>
Message-ID: <20071220032837.GI5698@jm.kir.nu>

On Thu, Dec 20, 2007 at 01:44:16PM +1100, hce wrote:

> I am running wpa_supplicant version 0.5.8. If I set ssid="MyAP", it
> works. But, if I set ssid="any" in wpa_supplicant.conf, then calling
> wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant.conf &", it
> failed, stopped at "WEXT auth param 5 value 0x1 - Added interface
> eth1Hack: state = 0x7". What I was missing?

I would assume wpa_supplicant was trying to follow what the
configuration file asked, i.e., trying to get the driver to use network
with a three-octet SSID 'any'. This is not the way to configure a
wildcard SSID which, I would assume, is what you were actually trying to
configure here.

> Basically, I don't want to specify a hardcoded ssid, so I can bring
> the wifi up in a street open AP. Is it possible, or it is not
> supported?

Did you look at the end of the example configuration file which gives an
example network block for wildcard match for SSID (plaintext APs)? Just
leave the ssid parameter out or set it to an empty string and you'll get
this behavior.

-- 
Jouni Malinen                                            PGP id EFC895FA



From webmail.hce  Wed Dec 19 19:49:53 2007
From: webmail.hce (hce)
Date: Thu, 20 Dec 2007 14:49:53 +1100
Subject: Does ssid="any" work?
In-Reply-To: <20071220032837.GI5698@jm.kir.nu>
References: <95455e980712191844i7b872f48t5aaa3bfd8090356b@mail.gmail.com>
	<20071220032837.GI5698@jm.kir.nu>
Message-ID: <95455e980712191949v3d34248fp2592e53c5840fe49@mail.gmail.com>

On Dec 20, 2007 2:28 PM, Jouni Malinen <j at w1.fi> wrote:
> On Thu, Dec 20, 2007 at 01:44:16PM +1100, hce wrote:
>
> > I am running wpa_supplicant version 0.5.8. If I set ssid="MyAP", it
> > works. But, if I set ssid="any" in wpa_supplicant.conf, then calling
> > wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant.conf &", it
> > failed, stopped at "WEXT auth param 5 value 0x1 - Added interface
> > eth1Hack: state = 0x7". What I was missing?
>
> I would assume wpa_supplicant was trying to follow what the
> configuration file asked, i.e., trying to get the driver to use network
> with a three-octet SSID 'any'. This is not the way to configure a
> wildcard SSID which, I would assume, is what you were actually trying to
> configure here.

> > Basically, I don't want to specify a hardcoded ssid, so I can bring
> > the wifi up in a street open AP. Is it possible, or it is not
> > supported?
>
> Did you look at the end of the example configuration file which gives an
> example network block for wildcard match for SSID (plaintext APs)? Just
> leave the ssid parameter out or set it to an empty string and you'll get
> this behavior.

I tried that, it did not work, stopped at "WEXT auth param 5 value 0x1
- Added interface eth1Hack: state = 0x7". Please see following my
wpa_supplicant.conf for an open AP, is there anything wrong there?

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

network={
    ssid=""
    key_mgmt=NONE
}

Thanks Jouni,

Kind Regards,

Jim



From johannes  Thu Dec 20 03:50:09 2007
From: johannes (Johannes Berg)
Date: Thu, 20 Dec 2007 12:50:09 +0100
Subject: per-BSS driver structures
Message-ID: <1198151409.16241.34.camel@johannes.berg>

Hi,

When implementing a few things with nl80211 I need per-BSS driver
objects for some things.

What way would you prefer to do this? I could add a hashtable to the
driver to look up these structures by interface name but that seems
useless. Or we could change the whole interface all over to pass a new
structure containing the interface name and a driver-private pointer
instead of just the interface name, but as I'm not all too familiar with
hostapd yet I'd need some help with that.

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


From CTuffli  Fri Dec 21 08:44:07 2007
From: CTuffli (Chuck Tuffli)
Date: Fri, 21 Dec 2007 08:44:07 -0800
Subject: driver behavior when beacon changes
Message-ID: <BC985D0776746A4C8332947B350E01A67BF052@USEXCH2003.US-SC.dspcorp.com>

What event is a device driver supposed to generate if it detects that an
AP has changed security types? I recently ran across a case in which an
AP's beacon changed from including the RSNA IE to including the WPA IE,
and without sending a de-auth or disassoc to the client. I'm running the
0.5.7 client with the WEXT driver and using ap_scan=1.

---chuck




From j  Sat Dec 22 09:25:32 2007
From: j (Jouni Malinen)
Date: Sat, 22 Dec 2007 09:25:32 -0800
Subject: driver behavior when beacon changes
In-Reply-To: <BC985D0776746A4C8332947B350E01A67BF052@USEXCH2003.US-SC.dspcorp.com>
References: <BC985D0776746A4C8332947B350E01A67BF052@USEXCH2003.US-SC.dspcorp.com>
Message-ID: <20071222172532.GL5698@jm.kir.nu>

On Fri, Dec 21, 2007 at 08:44:07AM -0800, Chuck Tuffli wrote:
> What event is a device driver supposed to generate if it detects that an
> AP has changed security types? I recently ran across a case in which an
> AP's beacon changed from including the RSNA IE to including the WPA IE,
> and without sending a de-auth or disassoc to the client. I'm running the
> 0.5.7 client with the WEXT driver and using ap_scan=1.

If the beacon change is compatible with the previously used policy
(e.g., adding WPA IE sounds like such a change), I would not expect to
see any event messages from the driver. If the change is not compatible
with the current policy (e.g., RSN association and RSN IE removed), I
would expect the client driver to disassociate and generate a suitable
disassociation event for WEXT. However, in that case I would have
assumed that the AP would have already diassociated the client anyway..

-- 
Jouni Malinen                                            PGP id EFC895FA



From ruzsinszky.attila  Sat Dec 22 10:33:48 2007
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Sat, 22 Dec 2007 19:33:48 +0100
Subject: Madwifi and hidden SSID
Message-ID: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>

Hi,

SuSE 10.3, wpa_supplicant-0.5.8-37
madwifi-kmp-default-0.9.3.3_2.6.22.9_0.4-0.1
madwifi-0.9.3.2-0.1

The only one successfull solution is:
ap_scan=1 and ssid_scan=1 (and of course I disabled hidden SSID!).
(I definied all connection parameters explicite in network block.)

AP is a Linksys WRT54GL with WhiteRussian.

If I change ap_scan and/or ssid_scan no ASSOCIATION.
I tried out wext and madwifi driver.
Is this the right behaviour?

I've got a Prism2.5 and Atheros PCMCIA card and they are
working under SuSE 10.1 with an older one madwifi and
wpa_supplicant version.

TIA,
Ruzsi



From raghavendra.akkasali  Sat Dec 22 19:00:24 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Sun, 23 Dec 2007 12:00:24 +0900
Subject: EAP-SIM failing...
In-Reply-To: <20071220022810.GG5698@jm.kir.nu>
References: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>
	<20071220022810.GG5698@jm.kir.nu>
Message-ID: <58a444250712221900t443f125bh8c9bd2b7844072b8@mail.gmail.com>

Hi Jouni,

 I am not using CONFIG_PCSC in my .config file. Because in my previous
mail to mailing list Dan Williams replied me as below.

 "just don't enable that option if you don't care about using
smartcards with wpa_supplicant."

Is this correct? or I have to enable CONFIG_PCSC option in .config?

-Raghu.


On 12/20/07, Jouni Malinen <j at w1.fi> wrote:
> On Wed, Dec 19, 2007 at 03:12:02PM +0530, Raghavendra. S wrote:
>
> >  I am trying to test EAP-SIM. using wpa supplicant 0.6.1.
>
> > Selected network is configured to use SIM (sim=1 aka=0) - initialize PCSC
> > Failed to initialize SIM (pcsc-lite)
>
> It looks like initialization of the pcsc-lite connection for SIM
> operation is failing. Which pcsc-lite version are you using? Have you
> verified that pcscd sees the SIM card properly?
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>


-- 
Regards & Thanks
Raghavendra. S



From bryan  Sat Dec 22 19:58:47 2007
From: bryan (Bryan Kadzban)
Date: Sat, 22 Dec 2007 22:58:47 -0500
Subject: EAP-SIM failing...
In-Reply-To: <58a444250712221900t443f125bh8c9bd2b7844072b8@mail.gmail.com>
References: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>	<20071220022810.GG5698@jm.kir.nu>
	<58a444250712221900t443f125bh8c9bd2b7844072b8@mail.gmail.com>
Message-ID: <476DDCF7.9020008@kadzban.is-a-geek.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Raghavendra. S wrote:
> I am not using CONFIG_PCSC in my .config file. Because in my previous
> mail to mailing list Dan Williams replied me as below.
> 
> "just don't enable that option if you don't care about using 
> smartcards with wpa_supplicant."
> 
> Is this correct? or I have to enable CONFIG_PCSC option in .config?

At the time, you weren't trying to do anything with smartcards, but you
were getting compile errors (IIRC) in that part of the code.  Since you
didn't need support for smartcards then, it was easier to just disable
that whole area.

Now, it sounds like you've changed your mind and do need to use them, or
something?

In any case, that statement you quoted is correct -- *if* you don't need
smartcard support, then you can disable PCSC.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHbdzzS5vET1Wea5wRA3vuAKCvYijIaZbXbCP5eCcnuy8kY99YegCg2MnS
4bosZXmZqhVFdMPKVYGoaNU=
=Wsj8
-----END PGP SIGNATURE-----



From j  Sat Dec 22 20:00:03 2007
From: j (Jouni Malinen)
Date: Sat, 22 Dec 2007 20:00:03 -0800
Subject: EAP-SIM failing...
In-Reply-To: <58a444250712221900t443f125bh8c9bd2b7844072b8@mail.gmail.com>
References: <58a444250712190142x6fcd001o2a46a08a39c0e936@mail.gmail.com>
	<20071220022810.GG5698@jm.kir.nu>
	<58a444250712221900t443f125bh8c9bd2b7844072b8@mail.gmail.com>
Message-ID: <20071223040003.GS5698@jm.kir.nu>

On Sun, Dec 23, 2007 at 12:00:24PM +0900, Raghavendra. S wrote:

>  I am not using CONFIG_PCSC in my .config file. Because in my previous
> mail to mailing list Dan Williams replied me as below.
> 
>  "just don't enable that option if you don't care about using
> smartcards with wpa_supplicant."
> 
> Is this correct? or I have to enable CONFIG_PCSC option in .config?

Well, if you want to test EAP-SIM authentication properly, you would
need to have a SIM card and use PC/SC to access it for authentication..
If you are just testing the EAP part of EAP-SIM, you can disable
CONFIG_PCSC. However, in that case you must not include pcsc="" in the
configuration file since that is used to request PC/SC connection (which
was the part that was failing in your debug log). Please also note that
this is only suitable for testing since no real level of security is
provided by EAP-SIM with hardcoded authentication data.

-- 
Jouni Malinen                                            PGP id EFC895FA



From reikred  Sun Dec 23 12:44:33 2007
From: reikred (Reik Red)
Date: Sun, 23 Dec 2007 12:44:33 -0800
Subject: Failed to initialize wpa_supplicant
Message-ID: <476EC8B1.5080400@gmail.com>

Hi everybody,

In a nutshell: I cannot get init to start wpa_supplicant successfully as a service,
but I can start it manually myself after the fact. I'm trying debug this so that I
will be able to bring up wlan0 on boot.

Here's what happens during boot (after which wlan0 is not able to get an ip address):

Starting wpa_supplicant: /etc/wpa_supplicant/wpa_supplicant.conf,
   -iwlan0, dbus_bus_get[ctrl_iface_dbus]: No such file or directory
Failed to initialize wpa_supplicant

And here's what happens when I run it manually after boot:

#The following is the same command that "service wpa_supplicant start" generates
% wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -B -u -f
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 -

Despite the error message, wlan0 is now up and will even get itself an ip address
if I issue a "dhclient wlan0" command.

I have already tried the bit about changing 12 88 to 09 88 in the /etc/init.d/wpa_supplicant script.
# chkconfig:   - 09 88

After looking for a bout a day on the web, I'm hoping someone here knows the answer.
The only thing missing here is to be able to boot and have wlan0 come right up.

Thanks
Reik

System details: Fedora 8 fc8_x86_64, kernel 2.6.23.9-85.fc8, yum update wpa_supplicant
is current as of today, driver used is ralink's ra61pci.



From raghavendra.akkasali  Sun Dec 23 18:04:42 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Mon, 24 Dec 2007 07:34:42 +0530
Subject: Ad-Hoc mode clarification needed...
Message-ID: <58a444250712231804i3b94e615y88c7534eb4b12882@mail.gmail.com>

Hi All,

Does wpa supplicant supports EAP security methods while operating in
Ad-Hoc mode(IBSS)?

I saw explanation where in they have mentioned only key_mgmt  NONE and WPA_NONE?

I would like to know whether it supports any or all of the following.
WEP,
WPA_EAP (WPA_Enterprise),
WPA_PSK (WPA_Personal)

-- 
Regards & Thanks
Raghavendra. S



From j  Sun Dec 23 18:08:44 2007
From: j (Jouni Malinen)
Date: Sun, 23 Dec 2007 18:08:44 -0800
Subject: [PATCH] hostapd: rename devicescape driver to nl80211
In-Reply-To: <1197477624.6558.112.camel@johannes.berg>
References: <1197477624.6558.112.camel@johannes.berg>
Message-ID: <20071224020844.GU5698@jm.kir.nu>

On Wed, Dec 12, 2007 at 05:40:24PM +0100, Johannes Berg wrote:

> This renames driver_devicescape.c to driver_nl80211.c with associated
> changes to the registration files etc. It also moves things from the header
> file that was originally shared with the kernel into the file directly,
> those things will be removed gradually as time permits.

Which version was this based on? The end result did not built and this
type of changes would be nice to handle in two different patches (i.e.,
first change driver_devicescape.c and then rename in a separate change).

Is driver_nl80211.c correct name for this? I would assume this would be
quite specific to net/mac80211 at least for the time being or would you
expect this to work with non-mac80211 drivers?

I applied the change of moving definitions from heaser files into
driver_devicescape.c, but with quite a bit of additional definitions
included to allow this to be compiled. I did not apply parts that
removed 'const' from couple of function definitions since they looked
more like reverting something than desired changes. I did not rename the
file.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sun Dec 23 18:10:40 2007
From: j (Jouni Malinen)
Date: Sun, 23 Dec 2007 18:10:40 -0800
Subject: Ad-Hoc mode clarification needed...
In-Reply-To: <58a444250712231804i3b94e615y88c7534eb4b12882@mail.gmail.com>
References: <58a444250712231804i3b94e615y88c7534eb4b12882@mail.gmail.com>
Message-ID: <20071224021040.GV5698@jm.kir.nu>

On Mon, Dec 24, 2007 at 07:34:42AM +0530, Raghavendra. S wrote:

> Does wpa supplicant supports EAP security methods while operating in
> Ad-Hoc mode(IBSS)?

No.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Sun Dec 23 19:25:27 2007
From: j (Jouni Malinen)
Date: Sun, 23 Dec 2007 19:25:27 -0800
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <475C3488.7030600@deployingradius.com>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>
	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>
	<20071208174844.GB5698@jm.kir.nu>
	<475C1F64.5000400@deployingradius.com>
	<20071209174207.GL5698@jm.kir.nu>
	<475C3488.7030600@deployingradius.com>
Message-ID: <20071224032527.GW5698@jm.kir.nu>

On Sun, Dec 09, 2007 at 07:31:36PM +0100, Alan DeKok wrote:

>   The interface right now looks pretty good.  Some comments:
> 
>  - exposing TTLS TLV data to the server would be useful
>  - allowing the server to add TTLS TLV data would be useful

I would assume you are referring to TTLS AVPs here. Would this be mainly
to allow PAP/CHAP/MS-CHAP/MS-CHAPv2 to be implemented elsewhere or is
there some additional AVPs that are commonly transmitted within TTLS?

>  - having method checks for PAP/CHAP/MS-CHAP in phase 2
>    like is done for the EAP methods would be useful

I added a separate flags for this into struct eap_user (ttls_auth
bitfield). This changed the default behavior from all non-EAP phase 2
methods allowed to not allow any of them unless explicitly allowed in
this bitfield.

>  - ability to completely control phase2 method would be good
>    i.e. run one EAP library for phase1, and another for phase2
>    it's weird, but it can catch corner cases and assumptions

This would likely require larger changes, but then again, designing a
nicer interface for this could also be useful from the view point of
simplifying the current design where EAP-PEAP/TTLS/FAST have their own
implementations.. This should probably also allow phase 2 to be proxied
to an external host or at least have hooks in place for such
functionality (i.e., having to wait for phase 2 reply).

-- 
Jouni Malinen                                            PGP id EFC895FA



From leenax  Sun Dec 23 23:05:22 2007
From: leenax (Leena Soman)
Date: Mon, 24 Dec 2007 12:35:22 +0530
Subject: Preauthentication configuration
Message-ID: <a4a1fe4a0712232305m52050fdew8f0846c9cc1c2139@mail.gmail.com>

I want to configure my network so that my supplicant is able to
preauthenticate with an AP. For this,  I have 2 APs - AP1 - hostapd on Linux
and a Linksys  WRT54G -  AP2 , both with preauthentication enabled.  I have
configured both with the same SSID, the security policy being WPA2-EAP(TLS).
My supplicant gets associated successfully with AP1 and then I also see it
sending out an EAPOL-Start on the wireless interface, with the destination
mac address of AP2. But I don't see anything being received at AP2. Do I
need to configure the hostpad interfaces as a birdge? Is there any other
configuration that is missing for this to work.

Thanks,
Leena.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/3ab3c04c/attachment.htm 


From aland  Mon Dec 24 00:46:44 2007
From: aland (Alan DeKok)
Date: Mon, 24 Dec 2007 09:46:44 +0100
Subject: EAP peer implementation from wpa_supplicant as a library
In-Reply-To: <20071224032527.GW5698@jm.kir.nu>
References: <2a6807850710161940n5c9b3831p98ed849c433ef213@mail.gmail.com>	<1192601236.3775.13.camel@fedora.centrala.partner-banka.hr>	<20071208174844.GB5698@jm.kir.nu>	<475C1F64.5000400@deployingradius.com>	<20071209174207.GL5698@jm.kir.nu>	<475C3488.7030600@deployingradius.com>
	<20071224032527.GW5698@jm.kir.nu>
Message-ID: <476F71F4.6020201@deployingradius.com>

Jouni Malinen wrote:
>>  - exposing TTLS TLV data to the server would be useful
>>  - allowing the server to add TTLS TLV data would be useful
> 
> I would assume you are referring to TTLS AVPs here. Would this be mainly
> to allow PAP/CHAP/MS-CHAP/MS-CHAPv2 to be implemented elsewhere or is
> there some additional AVPs that are commonly transmitted within TTLS?

  Yes.  There isn't any additional data inside of TTLS, but there are a
number of discussions about it.

>>  - having method checks for PAP/CHAP/MS-CHAP in phase 2
>>    like is done for the EAP methods would be useful
> 
> I added a separate flags for this into struct eap_user (ttls_auth
> bitfield). This changed the default behavior from all non-EAP phase 2
> methods allowed to not allow any of them unless explicitly allowed in
> this bitfield.

  OK, thanks.

>>  - ability to completely control phase2 method would be good
>>    i.e. run one EAP library for phase1, and another for phase2
>>    it's weird, but it can catch corner cases and assumptions
> 
> This would likely require larger changes, but then again, designing a
> nicer interface for this could also be useful from the view point of
> simplifying the current design where EAP-PEAP/TTLS/FAST have their own
> implementations.. This should probably also allow phase 2 to be proxied
> to an external host or at least have hooks in place for such
> functionality (i.e., having to wait for phase 2 reply).

  Yes, exactly.  I'll see if I can make some progress down that path.

  Alan DeKok.



From johannes  Mon Dec 24 02:32:16 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 11:32:16 +0100
Subject: [PATCH] hostapd: rename devicescape driver to nl80211
In-Reply-To: <20071224020844.GU5698@jm.kir.nu>
References: <1197477624.6558.112.camel@johannes.berg>
	<20071224020844.GU5698@jm.kir.nu>
Message-ID: <1198492336.4103.27.camel@johannes.berg>


> > This renames driver_devicescape.c to driver_nl80211.c with associated
> > changes to the registration files etc. It also moves things from the header
> > file that was originally shared with the kernel into the file directly,
> > those things will be removed gradually as time permits.
> 
> Which version was this based on?

Something a bit after my patches. I rebased it though.

>  The end result did not built and this
> type of changes would be nice to handle in two different patches (i.e.,
> first change driver_devicescape.c and then rename in a separate change).

I could do that. But it'd be a lot of work for little gain. If you
really want that let me know, otherwise I'll send you a few new patches
that make driver_nl80211 almost usable.

> Is driver_nl80211.c correct name for this? I would assume this would be
> quite specific to net/mac80211 at least for the time being or would you
> expect this to work with non-mac80211 drivers?

For the time being it is, indeed, specific to mac80211. I would hope,
however, that non-mac80211 drivers can pick up the cfg80211 API (it is,
after all, easily implemented, see net/mac80211/cfg.c) and we can use
this driver with anything that supports it.

> I applied the change of moving definitions from heaser files into
> driver_devicescape.c, but with quite a bit of additional definitions
> included to allow this to be compiled. I did not apply parts that
> removed 'const' from couple of function definitions since they looked
> more like reverting something than desired changes. I did not rename the
> file.

Ah, ok. Yeah, I had a mistake there with the additional definitions and
removed some ioctls later. I'll rebase my patches on your current tree
starting with the rename then. The const bssid was indeed a "revert"
because you added the const in your version of the bssid patch and I had
this rename patch based on my original version of that (w/o const).

Thanks,
johannes




From johannes  Mon Dec 24 02:57:03 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 11:57:03 +0100
Subject: [PATCH] hostapd: rename driver_devicescape to driver_nl80211
Message-ID: <1198493823.4103.31.camel@johannes.berg>

This patch renames driver_devicescape to driver_nl80211 in the hope that
we'll at some point be able to use it with non-mac80211 chipsets too.

Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
---
Jouni, this patch requires that you *first* do

  git mv hostapd/driver_devicescape.c hostapd/driver_nl80211.c

because I didn't want to send a huge patch again. If there's a problem
with that let me know.

--- hostap.orig/hostapd/Makefile	2007-12-24 11:46:23.000000000 +0100
+++ hostap/hostapd/Makefile	2007-12-24 11:46:56.000000000 +0100
@@ -116,9 +116,9 @@ CFLAGS += -DCONFIG_DRIVER_PRISM54
 OBJS += driver_prism54.o
 endif
 
-ifdef CONFIG_DRIVER_DEVICESCAPE
-CFLAGS += -DCONFIG_DRIVER_DEVICESCAPE
-OBJS += driver_devicescape.o
+ifdef CONFIG_DRIVER_NL80211
+CFLAGS += -DCONFIG_DRIVER_NL80211
+OBJS += driver_nl80211.o
 LIBS += -lnl
 endif
 
--- hostap.orig/hostapd/defconfig	2007-12-24 11:45:40.000000000 +0100
+++ hostap/hostapd/defconfig	2007-12-24 11:46:56.000000000 +0100
@@ -22,19 +22,8 @@ CONFIG_DRIVER_HOSTAP=y
 # Driver interface for Prism54 driver
 #CONFIG_DRIVER_PRISM54=y
 
-# Driver interface for drivers using Devicescape IEEE 802.11 stack
-#CONFIG_DRIVER_DEVICESCAPE=y
-# Currently, driver_devicescape.c build requires some additional parameters
-# to be able to include some of the kernel header files. Following lines can
-# be used to set these (WIRELESS_DEV must point to the root directory of the
-# wireless-dev.git tree).
-#WIRELESS_DEV=/usr/src/wireless-dev
-#CFLAGS += -I$(WIRELESS_DEV)/net/mac80211
-# driver_devicescape.c requires a rather new libnl, probably not
-# shipped with your distribution yet
-#LIBNL=/usr/src/libnl
-#CFLAGS += -I$(LIBNL)/include
-#LIBS += -L$(LIBNL)/lib
+# Driver interface for drivers using the nl80211 kernel interface
+#CONFIG_DRIVER_NL80211=y
 
 # Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
 #CONFIG_DRIVER_BSD=y
--- hostap.orig/hostapd/drivers.c	2007-12-24 11:45:40.000000000 +0100
+++ hostap/hostapd/drivers.c	2007-12-24 11:46:56.000000000 +0100
@@ -18,10 +18,9 @@
 #ifdef CONFIG_DRIVER_HOSTAP
 extern struct wpa_driver_ops wpa_driver_hostap_ops; /* driver_hostap.c */
 #endif /* CONFIG_DRIVER_HOSTAP */
-#ifdef CONFIG_DRIVER_DEVICESCAPE
-/* driver_devicescape.c */
-extern struct wpa_driver_ops wpa_driver_devicescape_ops;
-#endif /* CONFIG_DRIVER_DEVICESCAPE */
+#ifdef CONFIG_DRIVER_NL80211
+extern struct wpa_driver_ops wpa_driver_nl80211_ops; /* driver_nl80211.c */
+#endif /* CONFIG_DRIVER_NL80211 */
 #ifdef CONFIG_DRIVER_PRISM54
 extern struct wpa_driver_ops wpa_driver_prism54_ops; /* driver_prism54.c */
 #endif /* CONFIG_DRIVER_PRISM54 */
@@ -44,9 +43,9 @@ struct wpa_driver_ops *hostapd_drivers[]
 #ifdef CONFIG_DRIVER_HOSTAP
 	&wpa_driver_hostap_ops,
 #endif /* CONFIG_DRIVER_HOSTAP */
-#ifdef CONFIG_DRIVER_DEVICESCAPE
-	&wpa_driver_devicescape_ops,
-#endif /* CONFIG_DRIVER_DEVICESCAPE */
+#ifdef CONFIG_DRIVER_NL80211
+	&wpa_driver_nl80211_ops,
+#endif /* CONFIG_DRIVER_NL80211 */
 #ifdef CONFIG_DRIVER_PRISM54
 	&wpa_driver_prism54_ops,
 #endif /* CONFIG_DRIVER_PRISM54 */
--- hostap.orig/hostapd/hostapd.conf	2007-12-24 11:46:24.000000000 +0100
+++ hostap/hostapd/hostapd.conf	2007-12-24 11:46:56.000000000 +0100
@@ -160,7 +160,7 @@ fragm_threshold=2346
 # Station MAC address -based authentication
 # Please note that this kind of access control requires a driver that uses
 # hostapd to take care of management frame processing and as such, this can be
-# used with driver=hostap or driver=devicescape, but not with driver=madwifi.
+# used with driver=hostap or driver=nl80211, but not with driver=madwifi.
 # 0 = accept unless in deny list
 # 1 = deny unless in accept list
 # 2 = use external RADIUS server (accept/deny lists are searched first)
--- hostap.orig/hostapd/driver_nl80211.c	2007-12-24 11:46:23.000000000 +0100
+++ hostap/hostapd/driver_nl80211.c	2007-12-24 11:51:55.000000000 +0100
@@ -1,5 +1,6 @@
 /*
- * hostapd / Kernel driver communication with Devicescape IEEE 802.11 stack
+ * hostapd / Kernel driver communication via nl80211
+ *
  * Copyright (c) 2002-2007, Jouni Malinen <j at w1.fi>
  * Copyright (c) 2003-2004, Instant802 Networks, Inc.
  * Copyright (c) 2005-2006, Devicescape Software, Inc.
@@ -2169,8 +2170,8 @@
 }
 
 
-const struct wpa_driver_ops wpa_driver_devicescape_ops = {
-	.name = "devicescape",
+const struct wpa_driver_ops wpa_driver_nl80211_ops = {
+	.name = "nl80211",
 	.init = i802_init,
 	.init_bssid = i802_init_bssid,
 	.deinit = i802_deinit,





From johannes  Mon Dec 24 03:14:35 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:35 +0100
Subject: [PATCH 4/8] nl80211 driver: use nl80211 for beacons
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111654.137806000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 005-use-nl80211-for-beacons.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/edfd806f/attachment.txt 


From johannes  Mon Dec 24 03:14:32 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:32 +0100
Subject: [PATCH 1/8] nl80211 driver: receive EAPOL Frames on the data interface
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111652.530127000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 002-eapol-on-regular-iface.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/f688e243/attachment.txt 


From johannes  Mon Dec 24 03:14:39 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:39 +0100
Subject: [PATCH 8/8] hostapd: use nl80211 to set interface to master mode
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111655.915230000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 009-nl80211-for-master-mode.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/b76236cb/attachment.txt 


From johannes  Mon Dec 24 03:14:34 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:34 +0100
Subject: [PATCH 3/8] nl80211 driver: use nl80211 for keys
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111653.697525000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 004-use-nl80211-for-keys.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/382bbbd5/attachment.txt 


From johannes  Mon Dec 24 03:14:33 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:33 +0100
Subject: [PATCH 2/8] nl80211 driver: remove Michael MIC failure code
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111653.209216000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 003-remove-michael-mic.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/36ec60a2/attachment.txt 


From johannes  Mon Dec 24 03:14:36 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:36 +0100
Subject: [PATCH 5/8] nl80211 driver: use nl80211 for key information
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111654.577351000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 006-use-nl80211-for-get-key.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/8db25bf9/attachment.txt 


From johannes  Mon Dec 24 03:14:37 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:14:37 +0100
Subject: [PATCH 6/8] nl80211 driver: use nl80211 for station management
References: <20071224111431.992265000@sipsolutions.net>
Message-ID: <20071224111655.018804000@sipsolutions.net>

An embedded and charset-unspecified text was scrubbed...
Name: 007-use-nl80211-for-sta.patch
Url: http://lists.shmoo.com/pipermail/hostap/attachments/20071224/48232e6e/attachment.txt 


From johannes  Mon Dec 24 03:18:21 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:18:21 +0100
Subject: [PATCH 0/8] nl80211 driver updates
Message-ID: <1198495101.4103.33.camel@johannes.berg>

This patch series updates the nl80211 to use the newly added
infrastructure. Due to outstanding patches to the kernel it
will currently not compile ("cooked monitor" is missing). If
that bothers you, please apply only patches 1-6.

johannes




From johannes  Mon Dec 24 03:24:08 2007
From: johannes (Johannes Berg)
Date: Mon, 24 Dec 2007 12:24:08 +0100
Subject: [PATCH 7/8] nl80211 driver: use monitor rather than management
	interface
In-Reply-To: <20071224111655.466223000@sipsolutions.net>
References: <20071224111431.992265000@sipsolutions.net>
	<20071224111655.466223000@sipsolutions.net>
Message-ID: <1198495448.4103.36.camel@johannes.berg>


On Mon, 2007-12-24 at 12:18 +0100, Johannes Berg wrote:
> plain text document attachment (008-use-monitor-not-mgmt.patch)
> This patch makes the nl80211 driver use a monitor rather than a
> management interface for receiving management frames. Monitor
> interfaces use radiotap so a radiotap parser (thanks to Andy Green)
> is also included.
> 
> Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
> ---
>  hostapd/Makefile         |    2 
>  hostapd/driver_nl80211.c |  573 +++++++++++++++++++----------------------------
>  hostapd/ieee802_11.c     |    3 
>  hostapd/radiotap.c       |  290 +++++++++++++++++++++++
>  hostapd/radiotap.h       |  242 +++++++++++++++++++
>  hostapd/radiotap_iter.h  |   41 +++
>  6 files changed, 816 insertions(+), 335 deletions(-)

That was too large for the list, if you need to see it before moderation
check
http://johannes.sipsolutions.net/patches/hostap/all/2007-12-24-11%3a22/

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


From j  Mon Dec 24 16:44:55 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 16:44:55 -0800
Subject: [PATCH] hostapd: rename driver_devicescape to driver_nl80211
In-Reply-To: <1198493823.4103.31.camel@johannes.berg>
References: <1198493823.4103.31.camel@johannes.berg>
Message-ID: <20071225004455.GY5698@jm.kir.nu>

On Mon, Dec 24, 2007 at 11:57:03AM +0100, Johannes Berg wrote:
> This patch renames driver_devicescape to driver_nl80211 in the hope that
> we'll at some point be able to use it with non-mac80211 chipsets too.

Thanks! Applied for other parts, but I skipped this change:

> --- hostap.orig/hostapd/defconfig	2007-12-24 11:45:40.000000000 +0100
> +++ hostap/hostapd/defconfig	2007-12-24 11:46:56.000000000 +0100
> -# driver_devicescape.c requires a rather new libnl, probably not
> -# shipped with your distribution yet
> -#LIBNL=/usr/src/libnl
> -#CFLAGS += -I$(LIBNL)/include
> -#LIBS += -L$(LIBNL)/lib

Since this statement seems to remain true at this point. Or well, at
least I need to use separate libnl installation on up-to-date Gentoo
system.

-- 
Jouni Malinen                                            PGP id EFC895FA



From johannes  Mon Dec 24 16:48:44 2007
From: johannes (Johannes Berg)
Date: Tue, 25 Dec 2007 01:48:44 +0100
Subject: [PATCH] hostapd: rename driver_devicescape to driver_nl80211
In-Reply-To: <20071225004455.GY5698@jm.kir.nu>
References: <1198493823.4103.31.camel@johannes.berg>
	<20071225004455.GY5698@jm.kir.nu>
Message-ID: <1198543724.4103.48.camel@johannes.berg>


On Mon, 2007-12-24 at 16:44 -0800, Jouni Malinen wrote:
> On Mon, Dec 24, 2007 at 11:57:03AM +0100, Johannes Berg wrote:
> > This patch renames driver_devicescape to driver_nl80211 in the hope that
> > we'll at some point be able to use it with non-mac80211 chipsets too.
> 
> Thanks! Applied for other parts, but I skipped this change:

Thanks :)

> > --- hostap.orig/hostapd/defconfig	2007-12-24 11:45:40.000000000 +0100
> > +++ hostap/hostapd/defconfig	2007-12-24 11:46:56.000000000 +0100
> > -# driver_devicescape.c requires a rather new libnl, probably not
> > -# shipped with your distribution yet
> > -#LIBNL=/usr/src/libnl
> > -#CFLAGS += -I$(LIBNL)/include
> > -#LIBS += -L$(LIBNL)/lib
> 
> Since this statement seems to remain true at this point. Or well, at
> least I need to use separate libnl installation on up-to-date Gentoo
> system.

Seriously? Debian now ships libnl 1.0-pre8 which is sufficient. Poke the
Gentoo maintainer :)

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


From dcbw  Mon Dec 24 17:03:33 2007
From: dcbw (Dan Williams)
Date: Mon, 24 Dec 2007 20:03:33 -0500
Subject: [PATCH] Allow logging to specific file with -F option
In-Reply-To: <200712171149.40842.kel@otaku42.de>
References: <200712171149.40842.kel@otaku42.de>
Message-ID: <1198544613.23509.6.camel@localhost.localdomain>

On Mon, 2007-12-17 at 11:49 +1000, Kel Modderman wrote:
> Hi,
> 
> (Re-sending this one, as it was not commented on in last patch frenzy.)
> 
> Logging to file was recently added, but the file path and name template
> is hardcoded in wpa_debug_open_file(). This change adds an extra -F
> command line option which allows specification of a specific output
> filename to write debug output to.

Since there hadn't been any releases with the -f flag, any reason why
you added a new flag for the debug file rather than just using -f?  It
seems a bit overkill to have two options; you could make it so that if
you specify -f without the path it'll log to the default location but
you can override it if you like.  That's the approach I'd rather see
here...  I think optarg will just be NULL if you don't specify a file,
in which case it'll just fall through to the default location because
params->wpa_debug_file will be NULL.

Other than that, the patch looks OK to me.

Dan

> wpa_debug_open_file() also prints an error message when the output file
> failed to be opened for writing, and wpa_debug_close_file() does not
> attempt to fclose the output file if it failed to be opened.
> 
> Signed-off-by: Kel Modderman <kel at otaku42.de>
> ---
> diff --git a/src/utils/wpa_debug.c b/src/utils/wpa_debug.c
> index b2f8c8b..7d3fff8 100644
> --- a/src/utils/wpa_debug.c
> +++ b/src/utils/wpa_debug.c
> @@ -227,36 +227,42 @@ void wpa_hexdump_ascii_key(int level, const char *title, 
> const u8 *buf,
>  }
>  
> 
> -int wpa_debug_open_file(void)
> +int wpa_debug_open_file(const char *file)
>  {
>  #ifdef CONFIG_DEBUG_FILE
>  	static int count = 0;
>  	char fname[64];
>  	if (!wpa_debug_use_file)
>  		return 0;
> +	if (file != NULL && out_file == NULL) {
> +		out_file = fopen(file, "a");
> +	} else {
>  #ifdef _WIN32
> -	os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
> -		    count++);
> +		os_snprintf(fname, sizeof(fname), "\\Temp\\wpa_supplicant-log-%d.txt",
> +			    count++);
>  #else /* _WIN32 */
> -	os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
> -		    count++);
> +		os_snprintf(fname, sizeof(fname), "/tmp/wpa_supplicant-log-%d.txt",
> +			    count++);
>  #endif /* _WIN32 */
> -	out_file = fopen(fname, "w");
> +		out_file = fopen(fname, "w");
> +	}
> +	if (out_file == NULL) {
> +		wpa_printf(MSG_ERROR, "wpa_debug_open_file: Failed to open output file, "
> +			   "using standard output");
> +		return -1;
> +	}
>  #ifndef _WIN32
> -	if (out_file)
> -		setvbuf(out_file, NULL, _IOLBF, 0);
> +	setvbuf(out_file, NULL, _IOLBF, 0);
>  #endif /* _WIN32 */
> -	return out_file == NULL ? -1 : 0;
> -#else /* CONFIG_DEBUG_FILE */
> -	return 0;
>  #endif /* CONFIG_DEBUG_FILE */
> +	return 0;
>  }
>  
> 
>  void wpa_debug_close_file(void)
>  {
>  #ifdef CONFIG_DEBUG_FILE
> -	if (!wpa_debug_use_file)
> +	if (!wpa_debug_use_file || out_file == NULL)
>  		return;
>  	fclose(out_file);
>  	out_file = NULL;
> diff --git a/src/utils/wpa_debug.h b/src/utils/wpa_debug.h
> index 9890945..8372cce 100644
> --- a/src/utils/wpa_debug.h
> +++ b/src/utils/wpa_debug.h
> @@ -37,7 +37,7 @@ enum { MSG_MSGDUMP, MSG_DEBUG, MSG_INFO, MSG_WARNING, 
> MSG_ERROR };
>  
>  #else /* CONFIG_NO_STDOUT_DEBUG */
>  
> -int wpa_debug_open_file(void);
> +int wpa_debug_open_file(const char *file);
>  void wpa_debug_close_file(void);
>  
>  /**
> diff --git a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml 
> b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
> index 296e660..1c7234a 100644
> --- a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
> +++ b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
> @@ -17,6 +17,7 @@
>        <arg>-c<replaceable>config file</replaceable></arg>
>        <arg>-D<replaceable>driver</replaceable></arg>
>        <arg>-P<replaceable>PID_file</replaceable></arg>
> +      <arg>-F<replaceable>output file</replaceable></arg>
>      </cmdsynopsis>
>    </refsynopsisdiv>
>    <refsect1>
> @@ -383,6 +384,13 @@
>        </varlistentry>
>  
>        <varlistentry>
> +	<term>-F output file</term>
> +	<listitem>
> +	  <para>Log output to specified file.</para>
> +	</listitem>
> +      </varlistentry>
> +
> +      <varlistentry>
>  	<term>-g global ctrl_interface</term>
>  	<listitem>
>  	  <para>Path to global ctrl_interface socket.</para>
> diff --git a/wpa_supplicant/main.c b/wpa_supplicant/main.c
> index e5af13d..dc89a8d 100644
> --- a/wpa_supplicant/main.c
> +++ b/wpa_supplicant/main.c
> @@ -40,7 +40,12 @@ static void usage(void)
>  	printf("%s\n\n%s\n"
>  	       "usage:\n"
>  	       "  wpa_supplicant [-BddfhKLqqtuvwW] [-P<pid file>] "
> -	       "[-g<global ctrl>] \\\n"
> +	       "[-g<global ctrl>]"
> +#ifdef CONFIG_DEBUG_FILE
> +	       " [-F<output file>] \\\n"
> +#else /* CONFIG_DEBUG_FILE */
> +	       " \\\n"
> +#endif /* CONFIG_DEBUG_FILE */
>  	       "        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] "
>  	       "[-p<driver_param>] \\\n"
>  	       "        [-b<br_ifname> [-N -i<ifname> -c<conf> [-C<ctrl>] "
> @@ -67,6 +72,7 @@ static void usage(void)
>  	       "  -D = driver name\n"
>  #ifdef CONFIG_DEBUG_FILE
>  	       "  -f = Log output to default log location (normally /tmp)\n"
> +	       "  -F = Log output to specified file\n"
>  #endif /* CONFIG_DEBUG_FILE */
>  	       "  -g = global ctrl_interface\n"
>  	       "  -K = include keys (passwords, etc.) in debug output\n"
> @@ -146,7 +152,7 @@ int main(int argc, char *argv[])
>  	wpa_supplicant_fd_workaround();
>  
>  	for (;;) {
> -		c = getopt(argc, argv, "b:Bc:C:D:dfg:hi:KLNp:P:qtuvwW");
> +		c = getopt(argc, argv, "b:Bc:C:D:dF:fg:hi:KLNp:P:qtuvwW");
>  		if (c < 0)
>  			break;
>  		switch (c) {
> @@ -179,6 +185,10 @@ int main(int argc, char *argv[])
>  		case 'f':
>  			params.wpa_debug_use_file = 1;
>  			break;
> +		case 'F':
> +			params.wpa_debug_use_file = 1;
> +			params.wpa_debug_file = optarg;
> +			break;
>  #endif /* CONFIG_DEBUG_FILE */
>  		case 'g':
>  			params.ctrl_interface = optarg;
> diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
> index 0c1a142..bcae686 100644
> --- a/wpa_supplicant/wpa_supplicant.c
> +++ b/wpa_supplicant/wpa_supplicant.c
> @@ -1828,7 +1828,7 @@ struct wpa_global * wpa_supplicant_init(struct 
> wpa_params *params)
>  		return NULL;
>  
>  	wpa_debug_use_file = params->wpa_debug_use_file;
> -	wpa_debug_open_file();
> +	wpa_debug_open_file(params->wpa_debug_file);
>  
>  	ret = eap_peer_register_methods();
>  	if (ret) {
> diff --git a/wpa_supplicant/wpa_supplicant_i.h 
> b/wpa_supplicant/wpa_supplicant_i.h
> index 00e3162..f741244 100644
> --- a/wpa_supplicant/wpa_supplicant_i.h
> +++ b/wpa_supplicant/wpa_supplicant_i.h
> @@ -154,6 +154,11 @@ struct wpa_params {
>  	 * wpa_debug_use_file - Write debug to a file (instead of stdout)
>  	 */
>  	int wpa_debug_use_file;
> +
> +	/**
> +	 * wpa_debug_file - Write debug to specified file.
> +	 */
> +	char *wpa_debug_file;
>  };
>  
>  /**




From j  Mon Dec 24 17:04:22 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 17:04:22 -0800
Subject: [PATCH 1/8] nl80211 driver: receive EAPOL Frames on the data
	interface
In-Reply-To: <20071224111652.530127000@sipsolutions.net>
References: <20071224111431.992265000@sipsolutions.net>
	<20071224111652.530127000@sipsolutions.net>
Message-ID: <20071225010422.GZ5698@jm.kir.nu>

On Mon, Dec 24, 2007 at 12:14:32PM +0100, Johannes Berg wrote:
> With recent kernel changes, EAPOL frames are no longer visible on the
> (deprecated) management interface but are shown on the data interfaces
> instead.
> 
> This patch makes the nl80211 driver register an EAPOL socket and keep track
> of all data interfaces so that it can receive EAPOL frames for the
> supplicant.

Thanks! Applied with some minor cleanup and couple of bug fixes
(if_indices needs to be freed in i802_deinit() if it was (re)allocated,
add_ifidx() should not be used with invalid ifidx).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Mon Dec 24 18:10:16 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 18:10:16 -0800
Subject: [PATCH] hostapd: rename driver_devicescape to driver_nl80211
In-Reply-To: <1198543724.4103.48.camel@johannes.berg>
References: <1198493823.4103.31.camel@johannes.berg>
	<20071225004455.GY5698@jm.kir.nu>
	<1198543724.4103.48.camel@johannes.berg>
Message-ID: <20071225021016.GA5698@jm.kir.nu>

On Tue, Dec 25, 2007 at 01:48:44AM +0100, Johannes Berg wrote:

> Seriously? Debian now ships libnl 1.0-pre8 which is sufficient. Poke the
> Gentoo maintainer :)

Gentoo is still using 1.0-pre6.. Kernel update (wireless-2.6#everything)
triggered a semi-related issue since linux/ip_mp_alg.h does not seem to
exist anymore, but netlink/netlink.h from 1.0-pre8 libnl tries to
include it.. As a bonus, something triggered conflicts between
src/utils/common.h and linux/types.h which gets included when building
driver_nl80211.c. I think I resolved this, but I really do not like
including linux/* when this type of issues show up.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kel  Mon Dec 24 18:20:57 2007
From: kel (Kel Modderman)
Date: Tue, 25 Dec 2007 12:20:57 +1000
Subject: [PATCH] Allow logging to specific file with -F option
In-Reply-To: <1198544613.23509.6.camel@localhost.localdomain>
References: <200712171149.40842.kel@otaku42.de>
	<1198544613.23509.6.camel@localhost.localdomain>
Message-ID: <200712251220.57562.kel@otaku42.de>

On Tuesday 25 December 2007 11:03:33 Dan Williams wrote:
> On Mon, 2007-12-17 at 11:49 +1000, Kel Modderman wrote:
> > Hi,
> >
> > (Re-sending this one, as it was not commented on in last patch frenzy.)
> >
> > Logging to file was recently added, but the file path and name template
> > is hardcoded in wpa_debug_open_file(). This change adds an extra -F
> > command line option which allows specification of a specific output
> > filename to write debug output to.
>
> Since there hadn't been any releases with the -f flag, any reason why
> you added a new flag for the debug file rather than just using -f?  It
> seems a bit overkill to have two options; you could make it so that if
> you specify -f without the path it'll log to the default location but
> you can override it if you like.  That's the approach I'd rather see
> here...  I think optarg will just be NULL if you don't specify a file,
> in which case it'll just fall through to the default location because
> params->wpa_debug_file will be NULL.
>
> Other than that, the patch looks OK to me.
>
> Dan

afaik, getopt requires that a specified argument accepts an argument or does 
not accept an argument (denoted by semi-colon after option letter), but there 
is no middle ground.

Ok, after reading `man 3 getopt`, two semi colons can allow an optional 
argument, but that is a GNU specific extension, and as such, probably not as 
portable as adding a definitive option.

Personally, I don't see the point in having the hardcoded fallback in /temp 
(\\Temp), but maybe I missed something.

Hope you have a good christmas btw ;-)

Thanks, Kel.



From j  Mon Dec 24 18:31:49 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 18:31:49 -0800
Subject: [PATCH 0/8] nl80211 driver updates
In-Reply-To: <1198495101.4103.33.camel@johannes.berg>
References: <1198495101.4103.33.camel@johannes.berg>
Message-ID: <20071225023149.GB5698@jm.kir.nu>

On Mon, Dec 24, 2007 at 12:18:21PM +0100, Johannes Berg wrote:
> This patch series updates the nl80211 to use the newly added
> infrastructure. Due to outstanding patches to the kernel it
> will currently not compile ("cooked monitor" is missing). If
> that bothers you, please apply only patches 1-6.

Thanks! I applied patches 1-6 and 8 for now. I need to take a closer
look at 7 and anyway, I would also prefer to keep hostapd in state that
does compile.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Mon Dec 24 18:39:42 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 18:39:42 -0800
Subject: [PATCH] Allow logging to specific file with -F option
In-Reply-To: <200712251220.57562.kel@otaku42.de>
References: <200712171149.40842.kel@otaku42.de>
	<1198544613.23509.6.camel@localhost.localdomain>
	<200712251220.57562.kel@otaku42.de>
Message-ID: <20071225023942.GC5698@jm.kir.nu>

On Tue, Dec 25, 2007 at 12:20:57PM +1000, Kel Modderman wrote:

> > > (Re-sending this one, as it was not commented on in last patch frenzy.)

Sorry.. I'm still planning on getting this type of change in at some
point. I think I found some parts that I liked more in Dan's patch and
some other areas that I preferred from your change, so I was planning on
doing some kind of merge of the two.. I just don't remember the details
anymore ;-).

> > Since there hadn't been any releases with the -f flag, any reason why
> > you added a new flag for the debug file rather than just using -f?  It
> > seems a bit overkill to have two options; you could make it so that if
> > you specify -f without the path it'll log to the default location but
> > you can override it if you like.  That's the approach I'd rather see
> > here...  I think optarg will just be NULL if you don't specify a file,
> > in which case it'll just fall through to the default location because
> > params->wpa_debug_file will be NULL.

> afaik, getopt requires that a specified argument accepts an argument or does 
> not accept an argument (denoted by semi-colon after option letter), but there 
> is no middle ground.
> 
> Ok, after reading `man 3 getopt`, two semi colons can allow an optional 
> argument, but that is a GNU specific extension, and as such, probably not as 
> portable as adding a definitive option.

I don't like that.. Both from the portability view point and from the
view point of being able to understand how the command line parsing is
supposed to work for some odd combinations like -fd (is it "-f -d" or -f
to a file named 'd')..

> Personally, I don't see the point in having the hardcoded fallback in /temp 
> (\\Temp), but maybe I missed something.

Some main*.c implementations do not have code for setting the path
(e.g., Windows service) and only use true/false to select whether
logging to file is enabled. These would need to be handled by moving the
hardcoded value somewhere else, but that should be okay. Forcing the
unix main() version to require full path name on the command line sounds
reasonable.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Mon Dec 24 19:13:12 2007
From: j (Jouni Malinen)
Date: Mon, 24 Dec 2007 19:13:12 -0800
Subject: [PATCH 7/8] nl80211 driver: use monitor rather than management
	interface
In-Reply-To: <20071224111655.466223000@sipsolutions.net>
References: <20071224111431.992265000@sipsolutions.net>
	<20071224111655.466223000@sipsolutions.net>
Message-ID: <20071225031312.GD5698@jm.kir.nu>

On Mon, Dec 24, 2007 at 12:14:38PM +0100, Johannes Berg wrote:
> This patch makes the nl80211 driver use a monitor rather than a
> management interface for receiving management frames. Monitor
> interfaces use radiotap so a radiotap parser (thanks to Andy Green)
> is also included.

Couple of questions below..

> --- hostap.orig/hostapd/driver_nl80211.c	2007-12-24 12:10:05.000000000 +0100
> +++ hostap/hostapd/driver_nl80211.c	2007-12-24 12:14:15.000000000 +0100

> +static int i802_send_mgmt_frame(void *priv, const void *data, size_t len,
>  				int flags)
>  {

> +	/*
> +	 * ugh, guess what, the generic code sets one of the version
> +	 * bits to request tx callback
> +	 */
> +	hdr->frame_control &= ~host_to_le16(BIT(1));
> +	return sendmsg(drv->monitor_sock, &msg, flags);

How is the TX callback/status requested with the radiotap version? It
looks like there is a flag (IEEE80211_RADIOTAP_TX_FLAGS) for figuring
out status for frames that were reported, but it was not immediately
obvious to me when that information would be provided back to userspace
for injected frames. Is this enabled for all injected frames by default
or there something in the radiotap header that requests this?


> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ hostap/hostapd/radiotap.c	2007-12-24 12:10:59.000000000 +0100
> @@ -0,0 +1,290 @@
> +/*
> + * Radiotap parser
> + *
> + * Copyright 2007		Andy Green <andy at warmcat.com>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + *
> + * Alternatively, this software may be distributed under the terms of BSD
> + * license.

Hmm.. This is based on code from Linux kernel (net/wireless/radiotap.c).
Right? And that file does not seem to indicate anything special about
license, so I would assume it is GPLv2. Has Andy licensed this code
under dual-GPL/BSD license?

> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ hostap/hostapd/radiotap.h	2007-12-24 12:10:59.000000000 +0100
> @@ -0,0 +1,242 @@
> +/* $FreeBSD: src/sys/net80211/ieee80211_radiotap.h,v 1.5 2005/01/22 20:12:05 sam Exp $ */
> +/* $NetBSD: ieee80211_radiotap.h,v 1.11 2005/06/22 06:16:02 dyoung Exp $ */
> +
> +/*-
> + * Copyright (c) 2003, 2004 David Young.  All rights reserved.

..

Do we need to distribute this file with hostapd? Is there not a standard
user space header for defining radiotap headers? This file has slightly
different license terms from rest of the files and as such, adds extra
complexity on that area.

-- 
Jouni Malinen                                            PGP id EFC895FA



From johannes  Tue Dec 25 02:44:34 2007
From: johannes (Johannes Berg)
Date: Tue, 25 Dec 2007 11:44:34 +0100
Subject: [PATCH 7/8] nl80211 driver: use monitor rather than management
	interface
In-Reply-To: <20071225031312.GD5698@jm.kir.nu>
References: <20071224111431.992265000@sipsolutions.net>
	<20071224111655.466223000@sipsolutions.net>
	<20071225031312.GD5698@jm.kir.nu>
Message-ID: <1198579474.4103.58.camel@johannes.berg>


> > +	/*
> > +	 * ugh, guess what, the generic code sets one of the version
> > +	 * bits to request tx callback
> > +	 */
> > +	hdr->frame_control &= ~host_to_le16(BIT(1));
> > +	return sendmsg(drv->monitor_sock, &msg, flags);
> 
> How is the TX callback/status requested with the radiotap version? It
> looks like there is a flag (IEEE80211_RADIOTAP_TX_FLAGS) for figuring
> out status for frames that were reported, but it was not immediately
> obvious to me when that information would be provided back to userspace
> for injected frames. Is this enabled for all injected frames by default
> or there something in the radiotap header that requests this?

Currently, it's implicitly done for all frames, even those that came
over the 802.3 interfaces, i.e. whenever we get a status notification we
show it on the monitor interfaces with the appropriate status. That will
need to change though.

> > --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> > +++ hostap/hostapd/radiotap.c	2007-12-24 12:10:59.000000000 +0100
> > @@ -0,0 +1,290 @@
> > +/*
> > + * Radiotap parser
> > + *
> > + * Copyright 2007		Andy Green <andy at warmcat.com>
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + *
> > + * Alternatively, this software may be distributed under the terms of BSD
> > + * license.
> 
> Hmm.. This is based on code from Linux kernel (net/wireless/radiotap.c).
> Right? And that file does not seem to indicate anything special about
> license, so I would assume it is GPLv2. Has Andy licensed this code
> under dual-GPL/BSD license?

Yes, I asked him to license it under dual-BPL/BSD (which sort of makes
the GPL moot). CC'ed again, Andy please confirm.

> > --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> > +++ hostap/hostapd/radiotap.h	2007-12-24 12:10:59.000000000 +0100
> > @@ -0,0 +1,242 @@
> > +/* $FreeBSD: src/sys/net80211/ieee80211_radiotap.h,v 1.5 2005/01/22 20:12:05 sam Exp $ */
> > +/* $NetBSD: ieee80211_radiotap.h,v 1.11 2005/06/22 06:16:02 dyoung Exp $ */
> > +
> > +/*-
> > + * Copyright (c) 2003, 2004 David Young.  All rights reserved.
> 
> ..
> 
> Do we need to distribute this file with hostapd? Is there not a standard
> user space header for defining radiotap headers? This file has slightly
> different license terms from rest of the files and as such, adds extra
> complexity on that area.

Oh, I didn't realise it had slightly different terms. We actually do
need the file unless we want to rewrite it, but I'm sure we can ask
David Young to adjust the terms to something we can agree with, after
all, rewriting it would mostly be mechanical and now even be possible
with the info I put on radiotap.org. I'll look into the exact terms and
ask David Young.

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


From dcbw  Tue Dec 25 06:11:40 2007
From: dcbw (Dan Williams)
Date: Tue, 25 Dec 2007 09:11:40 -0500
Subject: [PATCH] hostapd: rename driver_devicescape to driver_nl80211
In-Reply-To: <20071225021016.GA5698@jm.kir.nu>
References: <1198493823.4103.31.camel@johannes.berg>
	<20071225004455.GY5698@jm.kir.nu>
	<1198543724.4103.48.camel@johannes.berg>
	<20071225021016.GA5698@jm.kir.nu>
Message-ID: <1198591900.29158.5.camel@localhost.localdomain>

On Mon, 2007-12-24 at 18:10 -0800, Jouni Malinen wrote:
> On Tue, Dec 25, 2007 at 01:48:44AM +0100, Johannes Berg wrote:
> 
> > Seriously? Debian now ships libnl 1.0-pre8 which is sufficient. Poke the
> > Gentoo maintainer :)
> 
> Gentoo is still using 1.0-pre6.. Kernel update (wireless-2.6#everything)

I think -pre6 will be broken with 2.6.24 because of changes in netlink
in the kernel side.  Gentoo really will need to update quite soon
anyway.

> triggered a semi-related issue since linux/ip_mp_alg.h does not seem to
> exist anymore, but netlink/netlink.h from 1.0-pre8 libnl tries to

Update to the latest git snapshot, that's fixed for a week or so.

Dan

> include it.. As a bonus, something triggered conflicts between
> src/utils/common.h and linux/types.h which gets included when building
> driver_nl80211.c. I think I resolved this, but I really do not like
> including linux/* when this type of issues show up.
> 




From kel  Wed Dec 26 06:01:42 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 00:01:42 +1000
Subject: [PATCH]: remove ref to ctrl_interface_group in wpa_cli manpage
Message-ID: <200712270001.42267.kel@otaku42.de>

Remove reference to the deprecated ctrl_interface_group global configuration
option in the docbook source of the wpa_cli manpage. Instead hint to the GROUP=
parameter of the ctrl_interface global option.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/doc/docbook/wpa_cli.sgml
+++ b/wpa_supplicant/doc/docbook/wpa_cli.sgml
@@ -44,7 +44,7 @@
     response.</para>
 
     <para>The control interface of wpa_supplicant can be configured to
-    allow non-root user access (ctrl_interface_group in the
+    allow non-root user access (ctrl_interface GROUP= parameter in the
     configuration file). This makes it possible to run wpa_cli with a
     normal user account.</para>
 
---



From kel  Wed Dec 26 06:07:24 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 00:07:24 +1000
Subject: [PATCH]: remove ref to ctrl_interface_group in wpa_supplicant.conf
	manpage
Message-ID: <200712270007.25127.kel@otaku42.de>

Remove reference to the deprecated ctrl_interface_group global configuration
option in the docbook source of the wpa_supplicant.conf manpage. Instead use
the new ctrl_interface=DIR GROUP= global option syntax.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml
+++ b/wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml
@@ -46,8 +46,7 @@
 
 <blockquote><programlisting>
 # allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 #
 # home network; allow all valid ciphers
 network={
@@ -80,8 +79,7 @@
         Aegis, Interlink RAD-Series)</para>
 
 <blockquote><programlisting>
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 network={
 	ssid="example"
 	scan_ssid=1
@@ -103,8 +101,7 @@
 
 
 <blockquote><programlisting>
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 network={
 	ssid="example"
 	scan_ssid=1
@@ -126,8 +123,7 @@
         authentication</para>
 
 <blockquote><programlisting>
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 network={
 	ssid="1x-test"
 	scan_ssid=1
@@ -152,8 +148,7 @@
         use.</para>
 
 <blockquote><programlisting>
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 network={
 	ssid="example"
 	scan_ssid=1
@@ -182,8 +177,7 @@
        'wired' interface (-Dwired on command line).</para>
 
 <blockquote><programlisting>
-ctrl_interface=/var/run/wpa_supplicant
-ctrl_interface_group=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
 ap_scan=0
 network={
 	key_mgmt=IEEE8021X
---



From kel  Wed Dec 26 03:42:18 2007
From: kel (Kel Modderman)
Date: Wed, 26 Dec 2007 21:42:18 +1000
Subject: [PATCH]: fix compile warnings in wpa_gui
Message-ID: <200712262142.18308.kel@otaku42.de>

The following warnings can be observed while compiling wpa_gui:

g++ -c -pipe -fpermissive -O2 -Wall -W -D_REENTRANT -DQT_SHARED -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DQT_NO_DEBUG -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/Qt3Support -I/usr/include/qt4 -I. -I.. -I../../src/utils -I../../src/common -I.moc -I.ui -o .obj/networkconfig.o .ui/networkconfig.cpp
In file included from .ui/networkconfig.cpp:9:
.ui/../networkconfig.ui.h: In member function 'virtual void NetworkConfig::addNetwork()':
.ui/../networkconfig.ui.h:137: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:140: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:143: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:144: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:147: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:148: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:151: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:152: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:155: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:156: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:164: warning: deprecated conversion from string constant to 'char*'
.ui/../networkconfig.ui.h:166: warning: deprecated conversion from string constant to 'char*'

The attached patch fixes them. I'm pretty sure none of the strings marked as
constants by this patch are expected to be modifiable by other functions.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/wpa_gui/networkconfig.ui.h
+++ b/wpa_supplicant/wpa_gui/networkconfig.ui.h
@@ -131,7 +131,7 @@
 
     setNetworkParam(id, "ssid", ssidEdit->text().ascii(), true);
     
-    char *key_mgmt = NULL, *proto = NULL, *pairwise = NULL;
+    const char *key_mgmt = NULL, *proto = NULL, *pairwise = NULL;
     switch (auth) {
     case AUTH_NONE:
 	key_mgmt = "NONE";
---



From kel  Wed Dec 26 05:59:04 2007
From: kel (Kel Modderman)
Date: Wed, 26 Dec 2007 23:59:04 +1000
Subject: [PATCH]: add wpa_gui.sgml docbook manpage source
Message-ID: <200712262359.04226.kel@otaku42.de>

Please add a basic manpage for wpa_gui to live alongside the others. We can
improve upon it over time ;-)

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/doc/docbook/Makefile
+++ b/wpa_supplicant/doc/docbook/Makefile
@@ -2,6 +2,7 @@
 
 FILES += wpa_background
 FILES += wpa_cli
+FILES += wpa_gui
 FILES += wpa_passphrase
 FILES += wpa_supplicant.conf
 FILES += wpa_supplicant
@@ -18,7 +19,7 @@
 
 
 clean:
-	rm -f wpa_background.8 wpa_cli.8 wpa_passphrase.8 wpa_supplicant.8
+	rm -f wpa_background.8 wpa_cli.8 wpa_gui.8 wpa_passphrase.8 wpa_supplicant.8
 	rm -f wpa_supplicant.conf.5
 	rm -f manpage.links manpage.refs
 	rm -f $(FILES:%=%.pdf)
--- /dev/null
+++ b/wpa_supplicant/doc/docbook/wpa_gui.sgml
@@ -0,0 +1,76 @@
+<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<refentry>
+  <refmeta>
+    <refentrytitle>wpa_gui</refentrytitle>
+    <manvolnum>8</manvolnum>
+  </refmeta>
+  <refnamediv>
+    <refname>wpa_gui</refname>
+
+    <refpurpose>WPA Graphical User Interface</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>wpa_gui</command>
+      <arg>-p <replaceable>path to ctrl sockets</replaceable></arg>
+      <arg>-i <replaceable>ifname</replaceable></arg>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsect1>
+    <title>Overview</title>
+
+    <para>wpa_cgui is a QT graphical frontend program for interacting
+    with wpa_supplicant. It is used to query current status, change
+    configuration and request interactive user input.</para>
+
+    <para>wpa_gui supports (almost) all of the interactive status and
+    configuration features of the command line client, wpa_cli. Refer
+    to the wpa_cli manpage for a comprehensive list of the
+    interactive mode features.</para>
+  </refsect1>
+  <refsect1>
+    <title>Command Arguments</title>
+    <variablelist>
+      <varlistentry>
+	<term>-p path</term>
+
+	<listitem><para>Change the path where control sockets should
+	be found.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>-i ifname</term>
+
+        <listitem><para>Specify the interface that is being
+	configured. By default, choose the first interface found with
+	a control socket in the socket path.</para></listitem>
+      </varlistentry>
+    </variablelist>
+  </refsect1>
+  <refsect1>
+    <title>See Also</title>
+    <para>
+      <citerefentry>
+	<refentrytitle>wpa_cli</refentrytitle>
+	<manvolnum>8</manvolnum>
+      </citerefentry>
+      <citerefentry>
+	<refentrytitle>wpa_supplicant</refentrytitle>
+	<manvolnum>8</manvolnum>
+      </citerefentry>
+    </para>
+  </refsect1>
+  <refsect1>
+    <title>Legal</title>
+    <para>wpa_supplicant is copyright (c) 2003-2007,
+    Jouni Malinen <email>j at w1.fi</email> and
+    contributors.
+    All Rights Reserved.</para>
+
+    <para>This program is dual-licensed under both the GPL version 2
+    and BSD license. Either license may be used at your option.</para>
+  </refsect1>
+</refentry>
---



From kel  Wed Dec 26 03:32:40 2007
From: kel (Kel Modderman)
Date: Wed, 26 Dec 2007 21:32:40 +1000
Subject: [PATCH]: Add a D-BUS service activation configuration
Message-ID: <200712262132.40461.kel@otaku42.de>

Please consider adding the following file, which is a D-BUS configuration
file that adds system activation support for wpa_supplicant. Here is the
upstream specification:

http://webcvs.freedesktop.org/dbus/dbus/doc/system-activation.txt?view=co

You have to install the service file into /usr/share/dbus-1/system-service
and the name of the file must correspond to the service bus name.

e.g: /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- /dev/null
+++ b/wpa_supplicant/dbus-wpa_supplicant.service
@@ -0,0 +1,4 @@
+[D-BUS Service]
+Name=fi.epitest.hostap.WPASupplicant
+Exec=/sbin/wpa_supplicant -u
+User=root
---



From kel  Wed Dec 26 06:08:42 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 00:08:42 +1000
Subject: [PATCH]: fix x86_64 compile warnings in pcsc_funcs.c
Message-ID: <200712270008.42844.kel@otaku42.de>

The following compilation warnings can be observed on x86_64 when 
CONFIG_PCSC=y is set:

cc -MMD -O2 -Wall -g -I. -I../src -I../src/crypto -I../src/utils -I../src/common -I../src/rsn_supp -I../src/drivers/driver_madwifi/ -DCONFIG_BACKEND_FILE -DCONFIG_DRIVER_HOSTAP -DCONFIG_DRIVER_WEXT -DCONFIG_DRIVER_MADWIFI -DCONFIG_DRIVER_ATMEL -DCONFIG_DRIVER_WIRED -DCONFIG_DRIVER_TEST -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_SIM -DEAP_LEAP -DEAP_PSK -DEAP_AKA -DEAP_TLV -DEAP_PAX -DIEEE8021X_EAPOL -DPCSC_FUNCS -I/usr/include/PCSC -DEAP_TLS_FUNCS -DEAP_TLS_OPENSSL -DPKCS12_FUNCS -DCONFIG_SMARTCARD -DINTERNAL_SHA256 -DCONFIG_WIRELESS_EXTENSION -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DCONFIG_CTRL_IFACE_DBUS -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include   -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=1 -DCONFIG_READLINE -DCONFIG_PEERKEY -DCONFIG_NO_T_PRF -DCONFIG_DEBUG_FILE   -c -o ../src/utils/pcsc_funcs.o ../src/utils/pcsc_funcs.c
../src/utils/pcsc_funcs.c: In function 'scard_read_record':
../src/utils/pcsc_funcs.c:851: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:851: warning: format '%d' expects type 'int', but 
argument 4 has type 'size_t'
../src/utils/pcsc_funcs.c: In function 'scard_read_file':
../src/utils/pcsc_funcs.c:894: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:894: warning: format '%d' expects type 'int', but 
argument 4 has type 'size_t'
../src/utils/pcsc_funcs.c: In function 'scard_get_imsi':
../src/utils/pcsc_funcs.c:972: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:986: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:992: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:992: warning: format '%d' expects type 'int', but 
argument 4 has type 'size_t'
../src/utils/pcsc_funcs.c: In function 'scard_gsm_auth':
../src/utils/pcsc_funcs.c:1075: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:1089: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c:1098: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'
../src/utils/pcsc_funcs.c: In function 'scard_umts_auth':
../src/utils/pcsc_funcs.c:1180: warning: format '%d' expects type 'int', but 
argument 3 has type 'size_t'

The attached patch makes them go away.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/src/utils/pcsc_funcs.c
+++ b/src/utils/pcsc_funcs.c
@@ -848,7 +848,8 @@
 	}
 	if (blen != len + 2) {
 		wpa_printf(MSG_DEBUG, "SCARD: record read returned unexpected "
-			   "length %d (expected %d)", blen, len + 2);
+			   "length %ld (expected %ld)",
+			   (long) blen, (long) len + 2);
 		os_free(buf);
 		return -3;
 	}
@@ -891,7 +892,8 @@
 	}
 	if (blen != len + 2) {
 		wpa_printf(MSG_DEBUG, "SCARD: file read returned unexpected "
-			   "length %d (expected %d)", blen, len + 2);
+			   "length %ld (expected %ld)",
+			   (long) blen, (long) len + 2);
 		os_free(buf);
 		return -3;
 	}
@@ -969,7 +971,7 @@
 		return -1;
 	if (blen < 4) {
 		wpa_printf(MSG_WARNING, "SCARD: too short (GSM) EF-IMSI "
-			   "header (len=%d)", blen);
+			   "header (len=%ld)", (long) blen);
 		return -2;
 	}
 
@@ -982,14 +984,14 @@
 		blen = file_size;
 	}
 	if (blen < 2 || blen > sizeof(buf)) {
-		wpa_printf(MSG_DEBUG, "SCARD: invalid IMSI file length=%d",
-			   blen);
+		wpa_printf(MSG_DEBUG, "SCARD: invalid IMSI file length=%ld",
+			   (long) blen);
 		return -3;
 	}
 
 	imsilen = (blen - 2) * 2 + 1;
-	wpa_printf(MSG_DEBUG, "SCARD: IMSI file length=%d imsilen=%d",
-		   blen, imsilen);
+	wpa_printf(MSG_DEBUG, "SCARD: IMSI file length=%ld imsilen=%ld",
+		   (long) blen, (long) imsilen);
 	if (blen < 2 || imsilen > *len) {
 		*len = imsilen;
 		return -4;
@@ -1071,8 +1073,8 @@
 	    (scard->sim_type == SCARD_USIM &&
 	     (len != 2 || resp[0] != 0x61 || resp[1] != 0x0e))) {
 		wpa_printf(MSG_WARNING, "SCARD: unexpected response for GSM "
-			   "auth request (len=%d resp=%02x %02x)",
-			   len, resp[0], resp[1]);
+			   "auth request (len=%ld resp=%02x %02x)",
+			   (long) len, resp[0], resp[1]);
 		return -3;
 	}
 	get_resp[4] = resp[1];
@@ -1085,8 +1087,8 @@
 	if (scard->sim_type == SCARD_GSM_SIM) {
 		if (len != 4 + 8 + 2) {
 			wpa_printf(MSG_WARNING, "SCARD: unexpected data "
-				   "length for GSM auth (len=%d, expected 14)",
-				   len);
+				   "length for GSM auth (len=%ld, expected 14)",
+				   (long) len);
 			return -5;
 		}
 		os_memcpy(sres, buf, 4);
@@ -1094,8 +1096,8 @@
 	} else {
 		if (len != 1 + 4 + 1 + 8 + 2) {
 			wpa_printf(MSG_WARNING, "SCARD: unexpected data "
-				   "length for USIM auth (len=%d, "
-				   "expected 16)", len);
+				   "length for USIM auth (len=%ld, "
+				   "expected 16)", (long) len);
 			return -5;
 		}
 		if (buf[0] != 4 || buf[5] != 8) {
@@ -1176,8 +1178,8 @@
 		return -1;
 	} else if (len != 2 || resp[0] != 0x61) {
 		wpa_printf(MSG_WARNING, "SCARD: unexpected response for UMTS "
-			   "auth request (len=%d resp=%02x %02x)",
-			   len, resp[0], resp[1]);
+			   "auth request (len=%ld resp=%02x %02x)",
+			   (long) len, resp[0], resp[1]);
 		return -1;
 	}
 	get_resp[4] = resp[1];
---



From kel  Wed Dec 26 06:09:54 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 00:09:54 +1000
Subject: [PATCH]: fix x86_64 compile warnings in eap_wsc.c
Message-ID: <200712270009.54309.kel@otaku42.de>

The following compilation warnings can be observed on x86_64 when
CONFIG_EAP_WSC=y is set:

cc -MMD -O2 -Wall -g -I. -I../src -I../src/crypto -I../src/utils -I../src/common -I../src/rsn_supp -I../src/drivers/driver_madwifi/ -DCONFIG_BACKEND_FILE -DCONFIG_DRIVER_HOSTAP -DCONFIG_DRIVER_WEXT -DCONFIG_DRIVER_MADWIFI -DCONFIG_DRIVER_ATMEL -DCONFIG_DRIVER_WIRED -DCONFIG_DRIVER_TEST -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_SIM -DEAP_LEAP -DEAP_PSK -DEAP_AKA -DEAP_TLV -DEAP_PAX -DEAP_WSC -DIEEE8021X_EAPOL -DPCSC_FUNCS -I/usr/include/PCSC -DEAP_TLS_FUNCS -DEAP_TLS_OPENSSL -DPKCS12_FUNCS -DCONFIG_SMARTCARD -DINTERNAL_SHA256 -DCONFIG_WIRELESS_EXTENSION -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX -DCONFIG_CTRL_IFACE_DBUS -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include   -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=1 -DCONFIG_READLINE -DCONFIG_PEERKEY -DCONFIG_IEEE80211W -DCONFIG_IEEE80211R -DCONFIG_NO_T_PRF -DCONFIG_DEBUG_FILE   -c -o ../src/eap_peer/eap_wsc.o ../src/eap_peer/eap_wsc.c
../src/eap_peer/eap_wsc.c: In function 'eap_wsc_build_msg':
../src/eap_peer/eap_wsc.c:261: warning: format '%u' expects type 'unsigned 
int', but argument 3 has type 'size_t'
../src/eap_peer/eap_wsc.c:275: warning: format '%u' expects type 'unsigned 
int', but argument 3 has type 'size_t'
../src/eap_peer/eap_wsc.c:275: warning: format '%u' expects type 'unsigned 
int', but argument 4 has type 'size_t'
../src/eap_peer/eap_wsc.c: In function 'eap_wsc_process':
../src/eap_peer/eap_wsc.c:389: warning: format '%u' expects type 'unsigned 
int', but argument 3 has type 'long int'
../src/eap_peer/eap_wsc.c:389: warning: format '%u' expects type 'unsigned 
int', but argument 4 has type 'size_t'
../src/eap_peer/eap_wsc.c:416: warning: format '%u' expects type 'unsigned 
int', but argument 3 has type 'size_t'
../src/eap_peer/eap_wsc.c:416: warning: format '%u' expects type 'unsigned 
int', but argument 4 has type 'size_t'

The attached patch makes them go away.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/src/eap_peer/eap_wsc.c
+++ b/src/eap_peer/eap_wsc.c
@@ -257,8 +257,9 @@
 	ret->decision = DECISION_FAIL;
 
 	if (data->out_used == data->out_len) {
-		wpa_printf(MSG_DEBUG, "EAP-WSC: Sending out %u bytes "
-			   "(message sent completely)", send_len);
+		wpa_printf(MSG_DEBUG, "EAP-WSC: Sending out %lu bytes "
+			   "(message sent completely)",
+			   (unsigned long) send_len);
 		os_free(data->out_buf);
 		data->out_buf = NULL;
 		data->out_len = data->out_used = 0;
@@ -270,9 +271,9 @@
 		} else
 			eap_wsc_state(data, MSG);
 	} else {
-		wpa_printf(MSG_DEBUG, "EAP-WSC: Sending out %u bytes "
-			   "(%u more to send)", send_len,
-			   data->out_len - data->out_used);
+		wpa_printf(MSG_DEBUG, "EAP-WSC: Sending out %lu bytes "
+			   "(%lu more to send)", (unsigned long) send_len,
+			   (unsigned long) data->out_len - data->out_used);
 		eap_wsc_state(data, WAIT_FRAG_ACK);
 	}
 
@@ -385,8 +386,8 @@
 		os_memcpy(data->in_buf + data->in_used, pos, end - pos);
 		data->in_used += end - pos;
 		wpa_printf(MSG_DEBUG, "EAP-WSC: Received %u bytes, waiting "
-			   "for %u bytes more", end - pos,
-			   data->in_len - data->in_used);
+			   "for %lu bytes more", (unsigned int) (end - pos),
+			   (unsigned long) data->in_len - data->in_used);
 	}
 
 	if (flags & WSC_FLAGS_MF) {
@@ -410,10 +411,10 @@
 			data->in_used = end - pos;
 			data->in_op_code = op_code;
 			os_memcpy(data->in_buf, pos, data->in_used);
-			wpa_printf(MSG_DEBUG, "EAP-WSC: Received %u bytes in "
-				   "first fragment, waiting for %u bytes more",
-				   data->in_used,
-				   data->in_len - data->in_used);
+			wpa_printf(MSG_DEBUG, "EAP-WSC: Received %lu bytes in "
+				   "first fragment, waiting for %lu bytes more",
+				   (unsigned long) data->in_used,
+				   (unsigned long) data->in_len - data->in_used);
 		}
 
 		return eap_wsc_build_frag_ack(id, EAP_CODE_RESPONSE);
---



From kel  Wed Dec 26 06:32:09 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 00:32:09 +1000
Subject: [PATCH]: add wpa_gui.sgml docbook manpage source
In-Reply-To: <200712262359.04226.kel@otaku42.de>
References: <200712262359.04226.kel@otaku42.de>
Message-ID: <200712270032.09779.kel@otaku42.de>

On Wednesday 26 December 2007 23:59:04 Kel Modderman wrote:
<snip>
> --- /dev/null
> +++ b/wpa_supplicant/doc/docbook/wpa_gui.sgml
> @@ -0,0 +1,76 @@
> +<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
> +
> +<refentry>
> +  <refmeta>
> +    <refentrytitle>wpa_gui</refentrytitle>
> +    <manvolnum>8</manvolnum>
> +  </refmeta>
> +  <refnamediv>
> +    <refname>wpa_gui</refname>
> +
> +    <refpurpose>WPA Graphical User Interface</refpurpose>
> +  </refnamediv>
> +
> +  <refsynopsisdiv>
> +    <cmdsynopsis>
> +      <command>wpa_gui</command>
> +      <arg>-p <replaceable>path to ctrl sockets</replaceable></arg>
> +      <arg>-i <replaceable>ifname</replaceable></arg>
> +    </cmdsynopsis>
> +  </refsynopsisdiv>
> +
> +  <refsect1>
> +    <title>Overview</title>
> +
> +    <para>wpa_cgui is a QT graphical frontend program for interacting

Crap, made a typo ^ :(

Kel.




From j  Wed Dec 26 10:13:10 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:13:10 -0800
Subject: [PATCH]: Add a D-BUS service activation configuration
In-Reply-To: <200712262132.40461.kel@otaku42.de>
References: <200712262132.40461.kel@otaku42.de>
Message-ID: <20071226181309.GA6450@jm.kir.nu>

On Wed, Dec 26, 2007 at 09:32:40PM +1000, Kel Modderman wrote:
> Please consider adding the following file, which is a D-BUS configuration
> file that adds system activation support for wpa_supplicant.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:17:46 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:17:46 -0800
Subject: [PATCH]: fix compile warnings in wpa_gui
In-Reply-To: <200712262142.18308.kel@otaku42.de>
References: <200712262142.18308.kel@otaku42.de>
Message-ID: <20071226181746.GB6450@jm.kir.nu>

On Wed, Dec 26, 2007 at 09:42:18PM +1000, Kel Modderman wrote:
> The following warnings can be observed while compiling wpa_gui:
> .ui/../networkconfig.ui.h:137: warning: deprecated conversion from string constant to 'char*'

> The attached patch fixes them. I'm pretty sure none of the strings marked as
> constants by this patch are expected to be modifiable by other functions.

I don't see these with g++ 4.1.2, but anyway, the change itself looks
fine. I applied it to both wpa_gui and wpa_gui-qt4.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:20:42 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:20:42 -0800
Subject: [PATCH]: add wpa_gui.sgml docbook manpage source
In-Reply-To: <200712262359.04226.kel@otaku42.de>
References: <200712262359.04226.kel@otaku42.de>
Message-ID: <20071226182042.GC6450@jm.kir.nu>

On Wed, Dec 26, 2007 at 11:59:04PM +1000, Kel Modderman wrote:
> Please add a basic manpage for wpa_gui to live alongside the others. We can
> improve upon it over time ;-)

Thanks! Applied (with a typo fixed).

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:22:11 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:22:11 -0800
Subject: [PATCH]: remove ref to ctrl_interface_group in wpa_cli manpage
In-Reply-To: <200712270001.42267.kel@otaku42.de>
References: <200712270001.42267.kel@otaku42.de>
Message-ID: <20071226182211.GD6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 12:01:42AM +1000, Kel Modderman wrote:
> Remove reference to the deprecated ctrl_interface_group global configuration
> option in the docbook source of the wpa_cli manpage. Instead hint to the GROUP=
> parameter of the ctrl_interface global option.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:23:46 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:23:46 -0800
Subject: [PATCH]: remove ref to ctrl_interface_group in
	wpa_supplicant.conf manpage
In-Reply-To: <200712270007.25127.kel@otaku42.de>
References: <200712270007.25127.kel@otaku42.de>
Message-ID: <20071226182346.GE6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 12:07:24AM +1000, Kel Modderman wrote:
> Remove reference to the deprecated ctrl_interface_group global configuration
> option in the docbook source of the wpa_supplicant.conf manpage. Instead use
> the new ctrl_interface=DIR GROUP= global option syntax.

Thanks! Applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:28:17 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:28:17 -0800
Subject: [PATCH]: fix x86_64 compile warnings in pcsc_funcs.c
In-Reply-To: <200712270008.42844.kel@otaku42.de>
References: <200712270008.42844.kel@otaku42.de>
Message-ID: <20071226182817.GF6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 12:08:42AM +1000, Kel Modderman wrote:
> The following compilation warnings can be observed on x86_64 when 
> CONFIG_PCSC=y is set:
> ../src/utils/pcsc_funcs.c:851: warning: format '%d' expects type 'int', but 
> argument 4 has type 'size_t'

> The attached patch makes them go away.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:30:01 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:30:01 -0800
Subject: [PATCH]: fix x86_64 compile warnings in eap_wsc.c
In-Reply-To: <200712270009.54309.kel@otaku42.de>
References: <200712270009.54309.kel@otaku42.de>
Message-ID: <20071226183001.GG6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 12:09:54AM +1000, Kel Modderman wrote:
> The following compilation warnings can be observed on x86_64 when
> CONFIG_EAP_WSC=y is set:
> ../src/eap_peer/eap_wsc.c:261: warning: format '%u' expects type 'unsigned 
> int', but argument 3 has type 'size_t'

> The attached patch makes them go away.

Thanks, applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 10:36:25 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 10:36:25 -0800
Subject: Preauthentication configuration
In-Reply-To: <a4a1fe4a0712232305m52050fdew8f0846c9cc1c2139@mail.gmail.com>
References: <a4a1fe4a0712232305m52050fdew8f0846c9cc1c2139@mail.gmail.com>
Message-ID: <20071226183625.GH6450@jm.kir.nu>

On Mon, Dec 24, 2007 at 12:35:22PM +0530, Leena Soman wrote:

> I want to configure my network so that my supplicant is able to
> preauthenticate with an AP. For this,  I have 2 APs - AP1 - hostapd on Linux
> and a Linksys  WRT54G -  AP2 , both with preauthentication enabled.  I have
> configured both with the same SSID, the security policy being WPA2-EAP(TLS).
> My supplicant gets associated successfully with AP1 and then I also see it
> sending out an EAPOL-Start on the wireless interface, with the destination
> mac address of AP2. But I don't see anything being received at AP2. Do I
> need to configure the hostpad interfaces as a birdge?

You will need to make sure that the AP sends RSN pre-authentication
packets properly. In most cases, this means that the WLAN interface and
wired interface will need to be bridged together.


-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Wed Dec 26 11:14:30 2007
From: j (Jouni Malinen)
Date: Wed, 26 Dec 2007 11:14:30 -0800
Subject: [PATCH] Allow logging to specific file with -F option
In-Reply-To: <200712251220.57562.kel@otaku42.de>
References: <200712171149.40842.kel@otaku42.de>
	<1198544613.23509.6.camel@localhost.localdomain>
	<200712251220.57562.kel@otaku42.de>
Message-ID: <20071226191430.GI6450@jm.kir.nu>

On Tue, Dec 25, 2007 at 12:20:57PM +1000, Kel Modderman wrote:
> On Tuesday 25 December 2007 11:03:33 Dan Williams wrote:
> > Since there hadn't been any releases with the -f flag, any reason why
> > you added a new flag for the debug file rather than just using -f?  It
> > seems a bit overkill to have two options; you could make it so that if
> > you specify -f without the path it'll log to the default location but
> > you can override it if you like.

> Personally, I don't see the point in having the hardcoded fallback in /temp 
> (\\Temp), but maybe I missed something.

I merged the patches (and this argument-to-f-flag idea) together and did
some additional cleanup. The end result is that there is no default
location and I also removed the '-%d' template for a counter since it
was not really used in wpa_supplicant. In other words, there is now just
one command line option (-f) and that provides the full path for the
debug log. The file is opened in append mode, so it will not be cleared
automatically which was the previous behavior.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kel  Wed Dec 26 15:01:34 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 09:01:34 +1000
Subject: [PATCH]: fix compile warnings in wpa_gui
In-Reply-To: <20071226181746.GB6450@jm.kir.nu>
References: <200712262142.18308.kel@otaku42.de>
	<20071226181746.GB6450@jm.kir.nu>
Message-ID: <200712270901.34192.kel@otaku42.de>

On Thursday 27 December 2007 04:17:46 Jouni Malinen wrote:
> On Wed, Dec 26, 2007 at 09:42:18PM +1000, Kel Modderman wrote:
> > The following warnings can be observed while compiling wpa_gui:
> > .ui/../networkconfig.ui.h:137: warning: deprecated conversion from string
> > constant to 'char*'
> >
> > The attached patch fixes them. I'm pretty sure none of the strings marked
> > as constants by this patch are expected to be modifiable by other
> > functions.
>
> I don't see these with g++ 4.1.2, but anyway, the change itself looks
> fine. I applied it to both wpa_gui and wpa_gui-qt4.

IIRC, g++ >= 4.2 makes the noise.

Thanks, Kel.



From kel  Wed Dec 26 21:09:51 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 15:09:51 +1000
Subject: [PATCH]: Add initial wpa_priv docbook manpage source
Message-ID: <200712271509.51470.kel@otaku42.de>

The attached patch adds an initial docbook manpage source for the new
privilege separation utility, wpa_priv.

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/doc/docbook/Makefile
+++ b/wpa_supplicant/doc/docbook/Makefile
@@ -4,6 +4,7 @@
 FILES += wpa_cli
 FILES += wpa_gui
 FILES += wpa_passphrase
+FILES += wpa_priv
 FILES += wpa_supplicant.conf
 FILES += wpa_supplicant
 
@@ -19,7 +20,7 @@
 
 
 clean:
-	rm -f wpa_background.8 wpa_cli.8 wpa_gui.8 wpa_passphrase.8 wpa_supplicant.8
+	rm -f wpa_background.8 wpa_cli.8 wpa_gui.8 wpa_passphrase.8 wpa_priv.8 wpa_supplicant.8
 	rm -f wpa_supplicant.conf.5
 	rm -f manpage.links manpage.refs
 	rm -f $(FILES:%=%.pdf)
--- /dev/null
+++ b/wpa_supplicant/doc/docbook/wpa_priv.sgml
@@ -0,0 +1,148 @@
+<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<refentry>
+  <refmeta>
+    <refentrytitle>wpa_priv</refentrytitle>
+    <manvolnum>8</manvolnum>
+  </refmeta>
+  <refnamediv>
+    <refname>wpa_priv</refname>
+
+    <refpurpose>wpa_supplicant privilege separation helper</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>wpa_priv</command>
+      <arg>-c <replaceable>ctrl path</replaceable></arg>
+      <arg>-Bdd</arg>
+      <arg>-P <replaceable>pid file</replaceable></arg>
+      <arg>driver:ifname <replaceable>[driver:ifname ...]</replaceable></arg>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsect1>
+    <title>Overview</title>
+
+    <para><command>wpa_priv</command> is a privilege separation helper that
+    minimizes the size of <command>wpa_supplicant</command> code that needs
+    to be run with root privileges.</para>
+
+    <para>If enabled, privileged operations are done in the wpa_priv process
+    while leaving rest of the code (e.g., EAP authentication and WPA
+    handshakes) to operate in an unprivileged process (wpa_supplicant) that
+    can be run as non-root user. Privilege separation restricts the effects
+    of potential software errors by containing the majority of the code in an
+    unprivileged process to avoid the possibility of a full system
+    compromise.</para>
+
+    <para><command>wpa_priv</command> needs to be run with network admin
+    privileges (usually, root user). It opens a UNIX domain socket for each
+    interface that is included on the command line; any other interface will
+    be off limits for <command>wpa_supplicant</command> in this kind of
+    configuration. After this, <command>wpa_supplicant</command> can be run as
+    a non-root user (e.g., all standard users on a laptop or as a special
+    non-privileged user account created just for this purpose to limit access
+    to user files even further).</para>
+  </refsect1>
+  <refsect1>
+    <title>Example configuration</title>
+
+    <para>The following steps are an example of how to configure
+    <command>wpa_priv</command> to allow users in the 'wpapriv' group
+    to communicate with <command>wpa_supplicant</command> with privilege
+    separation:</para>
+
+    <para>Create user group (e.g., wpapriv) and assign users that
+    should be able to use wpa_supplicant into that group.<para>
+
+    <para>Create /var/run/wpa_priv directory for UNIX domain sockets and
+    control user access by setting it accessible only for the wpapriv
+    group:<para>
+
+<blockquote><programlisting>
+mkdir /var/run/wpa_priv
+chown root:wpapriv /var/run/wpa_priv
+chmod 0750 /var/run/wpa_priv
+</programlisting></blockquote>
+
+    <para>Start <command>wpa_priv</command> as root (e.g., from system
+    startup scripts) with the enabled interfaces configured on the
+    command line:<para>
+
+<blockquote><programlisting>
+wpa_priv -B -c /var/run/wpa_priv -P /var/run/wpa_priv.pid wext:wlan0
+</programlisting></blockquote>
+
+    <para>Run <command>wpa_supplicant</command> as non-root with a user
+    that is in the wpapriv group:<para>
+
+<blockquote><programlisting>
+wpa_supplicant -i ath0 -c wpa_supplicant.conf
+</programlisting></blockquote>
+
+  </refsect1>
+  <refsect1>
+    <title>Command Arguments</title>
+    <variablelist>
+      <varlistentry>
+	<term>-c ctrl path</term>
+
+	<listitem><para>Specify the path to wpa_priv control directory
+	(Default: /var/run/wpa_priv/).</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>-B</term>
+	<listitem><para>Run as a daemon in the background.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>-P file</term>
+
+	<listitem><para>Set the location of the PID
+	file.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>driver:ifname [driver:ifname ...]</term>
+
+	<listitem><para>The &lt;driver&gt; string dictates which of the
+	supported <command>wpa_supplicant</command> driver backends is to be
+	used. To get a list of supported driver types see wpa_supplicant help
+	(e.g, wpa_supplicant -h). The driver backend supported by most good
+	drivers is 'wext'.</para>
+
+	<listitem><para>The &lt;ifname&gt; string specifies which network
+	interface is to be managed by <command>wpa_supplicant</command>
+	(e.g., wlan0 or ath0).</para>
+
+	<para><command>wpa_priv</command> does not use the network interface
+	before <command>wpa_supplicant</command> is started, so it is fine to
+	include network interfaces that are not available at the time wpa_priv
+	is started. wpa_priv can control multiple interfaces with one process,
+	but it is also possible to run multiple <command>wpa_priv</command>
+	processes at the same time, if desired.</para></listitem>
+      </varlistentry>
+    </variablelist>
+  </refsect1>
+  <refsect1>
+    <title>See Also</title>
+    <para>
+      <citerefentry>
+	<refentrytitle>wpa_supplicant</refentrytitle>
+	<manvolnum>8</manvolnum>
+      </citerefentry>
+    </para>
+  </refsect1>
+  <refsect1>
+    <title>Legal</title>
+    <para>wpa_supplicant is copyright (c) 2003-2007,
+    Jouni Malinen <email>j at w1.fi</email> and
+    contributors.
+    All Rights Reserved.</para>
+
+    <para>This program is dual-licensed under both the GPL version 2
+    and BSD license. Either license may be used at your option.</para>
+  </refsect1>
+</refentry>
---



From mahendra.p  Wed Dec 26 22:00:57 2007
From: mahendra.p (Mahendra Prajapat)
Date: Thu, 27 Dec 2007 11:30:57 +0530
Subject: Internal TLS/crypto in wpa supplicant
In-Reply-To: <20071010031321.GP14401@jm.kir.nu>
References: <001d01c80a59$da6aab50$36d06c6b@sisodomain.com>
	<20071010031321.GP14401@jm.kir.nu>
Message-ID: <000301c8484d$da2700d0$36d06c6b@sisodomain.com>


Dear Jouni,

Thanx for ur support.

I want to use Internal TLS/crypto in wpa supplicant to test EAP-TLS.
As I  am getting following errors:

TLSv1: Failed to parse private key
TLS: Failed to load private key
TLS: Failed to set TLS connection parameters
EAP-TLS: Failed to initialize SSL.

For testing purpose I require following certificates:
Ca-cert.pem
Ca-key.pem
Client-cert.pem
Client-key.pem
Client's private key password
Server-cert.pem
Server-key.pem
Server's private key password


Can you please send the certificates that you have used for testing Internal
TLS/crypto ?? 

Thanking you in advance..

Regards,
Mahen


-----Original Message-----
From: hostap-bounces+mahendra.p=samsung.com at shmoo.com
[mailto:hostap-bounces+mahendra.p=samsung.com at shmoo.com] On Behalf Of Jouni
Malinen
Sent: Wednesday, October 10, 2007 8:43 AM
To: hostap at shmoo.com
Subject: Re: Internal TLS/crypto in wpa supplicant

On Tue, Oct 09, 2007 at 03:20:39PM +0530, Mahendra Prajapat wrote:

> I m using internal crypto implementation for testing EAP_TLs and i m 
> getting errors.Corresponding significant logs messages are pasted below.

The internal TLS code has somewhat limited support for different formats for
certificates and especially private keys. I would guess that the problem
here was in the private key not being in support format. Which format did
you use for the private key? You will likely need to convert it at least to
use DER encoding and even that may not be enough depending on how the key
was generated.

One thing to note about the internal TLS implementation is that it is still
experimental and lacks some important functionality and testing.
Furthermore, I would highly recommend using the latest available code for it
(which, in this case, means the current git snapshot of the development
branch since there has been a critical bug fix in it since 0.6.0 release).

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





From dcbw  Thu Dec 27 00:45:14 2007
From: dcbw (Dan Williams)
Date: Thu, 27 Dec 2007 03:45:14 -0500
Subject: [PATCH] backport the 'frequency' option to 0.5.9
Message-ID: <1198745114.15031.20.camel@localhost.localdomain>

Thanks to stupid drivers, needed on 0.5.9 too.

Dan


diff --git a/wpa_supplicant/config.c b/wpa_supplicant/config.c
index 6a21bbc..10c454f 100644
--- a/wpa_supplicant/config.c
+++ b/wpa_supplicant/config.c
@@ -1158,7 +1158,8 @@ static const struct parse_data ssid_fields[] = {
 	{ INT_RANGE(ieee80211w, 0, 2) },
 #endif /* CONFIG_IEEE80211W */
 	{ INT_RANGE(peerkey, 0, 1) },
-	{ INT_RANGE(mixed_cell, 0, 1) }
+	{ INT_RANGE(mixed_cell, 0, 1) },
+	{ INT_RANGE(frequency, 0, 10000) }
 };
 
 #undef OFFSET
diff --git a/wpa_supplicant/config_ssid.h b/wpa_supplicant/config_ssid.h
index d4c3654..393f750 100644
--- a/wpa_supplicant/config_ssid.h
+++ b/wpa_supplicant/config_ssid.h
@@ -851,6 +851,18 @@ struct wpa_ssid {
 		IEEE80211W_REQUIRED = 2
 	} ieee80211w;
 #endif /* CONFIG_IEEE80211W */
+
+	/**
+	 * frequency - Channel frequency in megahertz (MHz) for IBSS
+	 *
+	 * This value is used to configure the initial channel for IBSS (adhoc)
+	 * networks, e.g., 2412 = IEEE 802.11b/g channel 1. It is ignored in
+	 * the infrastructure mode. In addition, this value is only used by the
+	 * station that creates the IBSS. If an IBSS network with the
+	 * configured SSID is already present, the frequency of the network
+	 * will be used instead of this configured value.
+	 */
+	int frequency;
 };
 
 int wpa_config_allowed_eap_method(struct wpa_ssid *ssid, int vendor,
diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c
index d5342fe..35ddbcd 100644
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -1468,6 +1468,8 @@ void wpa_supplicant_associate(struct wpa_supplicant *wpa_s,
 		params.ssid = ssid->ssid;
 		params.ssid_len = ssid->ssid_len;
 	}
+	if (ssid->mode == 1 && ssid->frequency > 0 && params.freq == 0)
+		params.freq = ssid->frequency; /* Initial channel for IBSS */
 	params.wpa_ie = wpa_ie;
 	params.wpa_ie_len = wpa_ie_len;
 	params.pairwise_suite = cipher_pairwise;
diff --git a/wpa_supplicant/wpa_supplicant.conf b/wpa_supplicant/wpa_supplicant.conf
index dce9d87..ec8b0ee 100644
--- a/wpa_supplicant/wpa_supplicant.conf
+++ b/wpa_supplicant/wpa_supplicant.conf
@@ -192,6 +192,13 @@ fast_reauth=1
 # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
 # both), and psk must also be set.
 #
+# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
+# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
+# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
+# In addition, this value is only used by the station that creates the IBSS. If
+# an IBSS network with the configured SSID is already present, the frequency of
+# the network will be used instead of this configured value.
+#
 # proto: list of accepted protocols
 # WPA = WPA/IEEE 802.11i/D3.0
 # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
@@ -657,6 +664,7 @@ network={
 network={
 	ssid="test adhoc"
 	mode=1
+	frequency=2412
 	proto=WPA
 	key_mgmt=WPA-NONE
 	pairwise=NONE




From dcbw  Thu Dec 27 00:48:13 2007
From: dcbw (Dan Williams)
Date: Thu, 27 Dec 2007 03:48:13 -0500
Subject: [PATCH] restrict D-Bus interface to root only
Message-ID: <1198745293.15031.22.camel@localhost.localdomain>

By default; distros can do what they want.  As a bonus, this removes a
SUSE/Fedora-ism (debian uses group permissions instead).


diff -up wpa_supplicant-0.5.7/dbus-wpa_supplicant.conf.permfix wpa_supplicant-0.5.7/dbus-wpa_supplicant.conf
--- wpa_supplicant-0.5.7/dbus-wpa_supplicant.conf.permfix	2007-10-20 07:42:01.000000000 -0400
+++ wpa_supplicant-0.5.7/dbus-wpa_supplicant.conf	2007-10-20 07:42:22.000000000 -0400
@@ -8,10 +8,6 @@
                 <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
                 <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
         </policy>
-        <policy at_console="true">
-                <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
-                <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
-        </policy>
         <policy context="default">
                 <deny own="fi.epitest.hostap.WPASupplicant"/>
                 <deny send_destination="fi.epitest.hostap.WPASupplicant"/>




From kel  Thu Dec 27 04:46:04 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 22:46:04 +1000
Subject: [PATCH]: Add id_str input support to wpa_gui (QT3)
Message-ID: <200712272246.04319.kel@otaku42.de>

This adds a "Network ID" field to the wpa_gui QT3 variant to support
configuration of the id_str network parameter.

It increases the default window height to 430 from 413 to fit in the new row.

It also changes the textLabel index to begin at 0 and not 1, this makes it
easier to identify what row the textLabel lives in (and also keeps this diff
from becoming needlessly large).

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/wpa_gui/networkconfig.ui
+++ b/wpa_supplicant/wpa_gui/networkconfig.ui
@@ -9,7 +9,7 @@
             <x>0</x>
             <y>0</y>
             <width>380</width>
-            <height>413</height>
+            <height>430</height>
         </rect>
     </property>
     <property name="caption">
@@ -43,7 +43,7 @@
                 </property>
                 <widget class="QLabel" row="0" column="0">
                     <property name="name">
-                        <cstring>textLabel1</cstring>
+                        <cstring>textLabel0</cstring>
                     </property>
                     <property name="text">
                         <string>SSID</string>
@@ -62,13 +62,32 @@
                 </widget>
                 <widget class="QLabel" row="1" column="0">
                     <property name="name">
+                        <cstring>textLabel1</cstring>
+                    </property>
+                    <property name="text">
+                        <string>Network ID</string>
+                    </property>
+                </widget>
+                <widget class="QLineEdit" row="1" column="1">
+                    <property name="name">
+                        <cstring>idstrEdit</cstring>
+                    </property>
+                    <property name="text">
+                        <string></string>
+                    </property>
+                    <property name="toolTip" stdset="0">
+                        <string>Network Identification String</string>
+                    </property>
+                </widget>
+                <widget class="QLabel" row="2" column="0">
+                    <property name="name">
                         <cstring>textLabel2</cstring>
                     </property>
                     <property name="text">
                         <string>Authentication</string>
                     </property>
                 </widget>
-                <widget class="QComboBox" row="1" column="1">
+                <widget class="QComboBox" row="2" column="1">
                     <item>
                         <property name="text">
                             <string>Plaintext or static WEP</string>
@@ -103,7 +122,7 @@
                         <cstring>authSelect</cstring>
                     </property>
                 </widget>
-                <widget class="QLabel" row="2" column="0">
+                <widget class="QLabel" row="3" column="0">
                     <property name="name">
                         <cstring>textLabel3</cstring>
                     </property>
@@ -111,7 +130,7 @@
                         <string>Encryption</string>
                     </property>
                 </widget>
-                <widget class="QComboBox" row="2" column="1">
+                <widget class="QComboBox" row="3" column="1">
                     <item>
                         <property name="text">
                             <string>None</string>
@@ -136,7 +155,7 @@
                         <cstring>encrSelect</cstring>
                     </property>
                 </widget>
-                <widget class="QLabel" row="3" column="0">
+                <widget class="QLabel" row="4" column="0">
                     <property name="name">
                         <cstring>textLabel4</cstring>
                     </property>
@@ -144,7 +163,7 @@
                         <string>PSK</string>
                     </property>
                 </widget>
-                <widget class="QLineEdit" row="3" column="1">
+                <widget class="QLineEdit" row="4" column="1">
                     <property name="name">
                         <cstring>pskEdit</cstring>
                     </property>
@@ -161,7 +180,7 @@
                         <string></string>
                     </property>
                 </widget>
-                <widget class="QLabel" row="4" column="0">
+                <widget class="QLabel" row="5" column="0">
                     <property name="name">
                         <cstring>textLabel5</cstring>
                     </property>
@@ -169,7 +188,7 @@
                         <string>EAP method</string>
                     </property>
                 </widget>
-                <widget class="QComboBox" row="4" column="1">
+                <widget class="QComboBox" row="5" column="1">
                     <property name="name">
                         <cstring>eapSelect</cstring>
                     </property>
@@ -177,7 +196,7 @@
                         <bool>false</bool>
                     </property>
                 </widget>
-                <widget class="QLabel" row="5" column="0">
+                <widget class="QLabel" row="6" column="0">
                     <property name="name">
                         <cstring>textLabel6</cstring>
                     </property>
@@ -185,7 +204,7 @@
                         <string>Identity</string>
                     </property>
                 </widget>
-                <widget class="QLineEdit" row="5" column="1">
+                <widget class="QLineEdit" row="6" column="1">
                     <property name="name">
                         <cstring>identityEdit</cstring>
                     </property>
@@ -196,7 +215,7 @@
                         <string>Username/Identity for EAP methods</string>
                     </property>
                 </widget>
-                <widget class="QLabel" row="6" column="0">
+                <widget class="QLabel" row="7" column="0">
                     <property name="name">
                         <cstring>textLabel7</cstring>
                     </property>
@@ -204,7 +223,7 @@
                         <string>Password</string>
                     </property>
                 </widget>
-                <widget class="QLineEdit" row="6" column="1">
+                <widget class="QLineEdit" row="7" column="1">
                     <property name="name">
                         <cstring>passwordEdit</cstring>
                     </property>
@@ -218,7 +237,7 @@
                         <string>Password for EAP methods</string>
                     </property>
                 </widget>
-                <widget class="QLabel" row="7" column="0">
+                <widget class="QLabel" row="8" column="0">
                     <property name="name">
                         <cstring>textLabel1_2</cstring>
                     </property>
@@ -226,7 +245,7 @@
                         <string>CA certificate</string>
                     </property>
                 </widget>
-                <widget class="QLineEdit" row="7" column="1">
+                <widget class="QLineEdit" row="8" column="1">
                     <property name="name">
                         <cstring>cacertEdit</cstring>
                     </property>
@@ -234,7 +253,7 @@
                         <bool>false</bool>
                     </property>
                 </widget>
-                <widget class="QButtonGroup" row="8" column="0" rowspan="1" colspan="2">
+                <widget class="QButtonGroup" row="9" column="0" rowspan="1" colspan="2">
                     <property name="name">
                         <cstring>buttonGroup1</cstring>
                     </property>
@@ -400,6 +419,7 @@
 </connections>
 <tabstops>
     <tabstop>ssidEdit</tabstop>
+    <tabstop>idstrEdit</tabstop>
     <tabstop>authSelect</tabstop>
     <tabstop>encrSelect</tabstop>
     <tabstop>pskEdit</tabstop>
--- a/wpa_supplicant/wpa_gui/networkconfig.ui.h
+++ b/wpa_supplicant/wpa_gui/networkconfig.ui.h
@@ -131,6 +131,9 @@
 
     setNetworkParam(id, "ssid", ssidEdit->text().ascii(), true);
     
+    if (idstrEdit->isEnabled())
+	setNetworkParam(id, "id_str", idstrEdit->text().ascii(), true);
+
     const char *key_mgmt = NULL, *proto = NULL, *pairwise = NULL;
     switch (auth) {
     case AUTH_NONE:
@@ -315,6 +318,17 @@
 	    *pos = '\0';
 	ssidEdit->setText(reply + 1);
     }
+
+    snprintf(cmd, sizeof(cmd), "GET_NETWORK %d id_str", network_id);
+    reply_len = sizeof(reply) - 1;
+    if (wpagui->ctrlRequest(cmd, reply, &reply_len) >= 0 && reply_len >= 2 &&
+	reply[0] == '"') {
+	reply[reply_len] = '\0';
+	pos = strchr(reply + 1, '"');
+	if (pos)
+	    *pos = '\0';
+	idstrEdit->setText(reply + 1);
+    }
     
     snprintf(cmd, sizeof(cmd), "GET_NETWORK %d proto", network_id);
     reply_len = sizeof(reply) - 1;
---



From kel  Thu Dec 27 04:50:03 2007
From: kel (Kel Modderman)
Date: Thu, 27 Dec 2007 22:50:03 +1000
Subject: [PATCH]: Add id_str input support to wpa_gui (QT4)
Message-ID: <200712272250.03615.kel@otaku42.de>

This adds a "Network ID" field to the wpa_gui QT4 variant to support
configuration of the id_str network parameter.

It also makes similar changes to the patch that adds id_str support to
the QT3 variant.

Please note I have not tested this patch, only the one for QT3 wpa_gui, but
it looks similar enough...

Signed-off-by: Kel Modderman <kel at otaku42.de>
---
--- a/wpa_supplicant/wpa_gui-qt4/networkconfig.cpp
+++ b/wpa_supplicant/wpa_gui-qt4/networkconfig.cpp
@@ -162,6 +162,10 @@
 
 	setNetworkParam(id, "ssid", ssidEdit->text().ascii(), true);
 
+	if (idstrEdit->isEnabled())
+		setNetworkParam(id, "id_str", idstrEdit->text().ascii(),
+				true);
+
 	const char *key_mgmt = NULL, *proto = NULL, *pairwise = NULL;
 	switch (auth) {
 	case AUTH_NONE:
@@ -355,6 +359,17 @@
 		ssidEdit->setText(reply + 1);
 	}
 
+	snprintf(cmd, sizeof(cmd), "GET_NETWORK %d id_str", network_id);
+	reply_len = sizeof(reply) - 1;
+	if (wpagui->ctrlRequest(cmd, reply, &reply_len) >= 0 &&
+	    reply_len >= 2 && reply[0] == '"') {
+		reply[reply_len] = '\0';
+		pos = strchr(reply + 1, '"');
+		if (pos)
+			*pos = '\0';
+		idstrEdit->setText(reply + 1);
+	}
+
 	snprintf(cmd, sizeof(cmd), "GET_NETWORK %d proto", network_id);
 	reply_len = sizeof(reply) - 1;
 	int wpa = 0;
--- a/wpa_supplicant/wpa_gui-qt4/networkconfig.ui
+++ b/wpa_supplicant/wpa_gui-qt4/networkconfig.ui
@@ -9,7 +9,7 @@
         <x>0</x>
         <y>0</y>
         <width>380</width>
-        <height>413</height>
+        <height>430</height>
       </rect>
     </property>
     <property name="windowTitle" >
@@ -33,7 +33,7 @@
           </property>
           <layout class="QGridLayout" >
             <item row="0" column="0" >
-              <widget class="QLabel" name="textLabel1" >
+              <widget class="QLabel" name="textLabel0" >
                 <property name="text" >
                   <string>SSID</string>
                 </property>
@@ -50,13 +50,30 @@
               </widget>
             </item>
             <item row="1" column="0" >
+              <widget class="QLabel" name="textLabel1" >
+                <property name="text" >
+                  <string>Network ID</string>
+                </property>
+              </widget>
+            </item>
+            <item row="1" column="1" >
+              <widget class="QLineEdit" name="idstrEdit" >
+                <property name="text" >
+                  <string/>
+                </property>
+                <property name="toolTip" stdset="0" >
+                  <string>Network Identification String</string>
+                </property>
+              </widget>
+            </item>
+            <item row="2" column="0" >
               <widget class="QLabel" name="textLabel2" >
                 <property name="text" >
                   <string>Authentication</string>
                 </property>
               </widget>
             </item>
-            <item row="1" column="1" >
+            <item row="2" column="1" >
               <widget class="QComboBox" name="authSelect" >
                 <item>
                   <property name="text" >
@@ -90,14 +107,14 @@
                 </item>
               </widget>
             </item>
-            <item row="2" column="0" >
+            <item row="3" column="0" >
               <widget class="QLabel" name="textLabel3" >
                 <property name="text" >
                   <string>Encryption</string>
                 </property>
               </widget>
             </item>
-            <item row="2" column="1" >
+            <item row="3" column="1" >
               <widget class="QComboBox" name="encrSelect" >
                 <item>
                   <property name="text" >
@@ -121,14 +138,14 @@
                 </item>
               </widget>
             </item>
-            <item row="3" column="0" >
+            <item row="4" column="0" >
               <widget class="QLabel" name="textLabel4" >
                 <property name="text" >
                   <string>PSK</string>
                 </property>
               </widget>
             </item>
-            <item row="3" column="1" >
+            <item row="4" column="1" >
               <widget class="QLineEdit" name="pskEdit" >
                 <property name="enabled" >
                   <bool>false</bool>
@@ -144,28 +161,28 @@
                 </property>
               </widget>
             </item>
-            <item row="4" column="0" >
+            <item row="5" column="0" >
               <widget class="QLabel" name="textLabel5" >
                 <property name="text" >
                   <string>EAP method</string>
                 </property>
               </widget>
             </item>
-            <item row="4" column="1" >
+            <item row="5" column="1" >
               <widget class="QComboBox" name="eapSelect" >
                 <property name="enabled" >
                   <bool>false</bool>
                 </property>
               </widget>
             </item>
-            <item row="5" column="0" >
+            <item row="6" column="0" >
               <widget class="QLabel" name="textLabel6" >
                 <property name="text" >
                   <string>Identity</string>
                 </property>
               </widget>
             </item>
-            <item row="5" column="1" >
+            <item row="6" column="1" >
               <widget class="QLineEdit" name="identityEdit" >
                 <property name="enabled" >
                   <bool>false</bool>
@@ -175,14 +192,14 @@
                 </property>
               </widget>
             </item>
-            <item row="6" column="0" >
+            <item row="7" column="0" >
               <widget class="QLabel" name="textLabel7" >
                 <property name="text" >
                   <string>Password</string>
                 </property>
               </widget>
             </item>
-            <item row="6" column="1" >
+            <item row="7" column="1" >
               <widget class="QLineEdit" name="passwordEdit" >
                 <property name="enabled" >
                   <bool>false</bool>
@@ -195,21 +212,21 @@
                 </property>
               </widget>
             </item>
-            <item row="7" column="0" >
+            <item row="8" column="0" >
               <widget class="QLabel" name="textLabel1_2" >
                 <property name="text" >
                   <string>CA certificate</string>
                 </property>
               </widget>
             </item>
-            <item row="7" column="1" >
+            <item row="8" column="1" >
               <widget class="QLineEdit" name="cacertEdit" >
                 <property name="enabled" >
                   <bool>false</bool>
                 </property>
               </widget>
             </item>
-            <item rowspan="1" row="8" column="0" colspan="2" >
+            <item rowspan="1" row="9" column="0" colspan="2" >
               <widget class="QGroupBox" name="buttonGroup1" >
                 <property name="enabled" >
                   <bool>true</bool>
@@ -331,6 +348,7 @@
   <pixmapfunction>qPixmapFromMimeSource</pixmapfunction>
   <tabstops>
     <tabstop>ssidEdit</tabstop>
+    <tabstop>idstrEdit</tabstop>
     <tabstop>authSelect</tabstop>
     <tabstop>encrSelect</tabstop>
     <tabstop>pskEdit</tabstop>
---



From j  Thu Dec 27 09:12:29 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 09:12:29 -0800
Subject: [PATCH]: Add initial wpa_priv docbook manpage source
In-Reply-To: <200712271509.51470.kel@otaku42.de>
References: <200712271509.51470.kel@otaku42.de>
Message-ID: <20071227171229.GJ6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 03:09:51PM +1000, Kel Modderman wrote:
> The attached patch adds an initial docbook manpage source for the new
> privilege separation utility, wpa_priv.

Thanks, applied. There was a number of mismatches in 'para' and
'listitem' tags ("<para>" used as the closing tag and some extra
"<listitem>" tags), but I think I managed to fix them properly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 27 09:17:57 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 09:17:57 -0800
Subject: [PATCH]: Add id_str input support to wpa_gui (QT3)
In-Reply-To: <200712272246.04319.kel@otaku42.de>
References: <200712272246.04319.kel@otaku42.de>
Message-ID: <20071227171757.GK6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 10:46:04PM +1000, Kel Modderman wrote:
> This adds a "Network ID" field to the wpa_gui QT3 variant to support
> configuration of the id_str network parameter.

Thanks! Applied.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 27 09:18:33 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 09:18:33 -0800
Subject: [PATCH]: Add id_str input support to wpa_gui (QT4)
In-Reply-To: <200712272250.03615.kel@otaku42.de>
References: <200712272250.03615.kel@otaku42.de>
Message-ID: <20071227171833.GL6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 10:50:03PM +1000, Kel Modderman wrote:
> This adds a "Network ID" field to the wpa_gui QT4 variant to support
> configuration of the id_str network parameter.

Thanks, applied.

> Please note I have not tested this patch, only the one for QT3 wpa_gui, but
> it looks similar enough...

Seemed to work fine in my quick test.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kel  Thu Dec 27 14:56:21 2007
From: kel (Kel Modderman)
Date: Fri, 28 Dec 2007 08:56:21 +1000
Subject: [PATCH]: Add initial wpa_priv docbook manpage source
In-Reply-To: <20071227171229.GJ6450@jm.kir.nu>
References: <200712271509.51470.kel@otaku42.de>
	<20071227171229.GJ6450@jm.kir.nu>
Message-ID: <200712280856.21782.kel@otaku42.de>

On Friday 28 December 2007 03:12:29 Jouni Malinen wrote:
> On Thu, Dec 27, 2007 at 03:09:51PM +1000, Kel Modderman wrote:
> > The attached patch adds an initial docbook manpage source for the new
> > privilege separation utility, wpa_priv.
>
> Thanks, applied. There was a number of mismatches in 'para' and
> 'listitem' tags ("<para>" used as the closing tag and some extra
> "<listitem>" tags), but I think I managed to fix them properly.

I'll double check it today, sorry about that.

Kel.



From j  Thu Dec 27 15:49:58 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 15:49:58 -0800
Subject: [PATCH] restrict D-Bus interface to root only
In-Reply-To: <1198745293.15031.22.camel@localhost.localdomain>
References: <1198745293.15031.22.camel@localhost.localdomain>
Message-ID: <20071227234958.GM6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 03:48:13AM -0500, Dan Williams wrote:
> By default; distros can do what they want.  As a bonus, this removes a
> SUSE/Fedora-ism (debian uses group permissions instead).

Thanks, applied to 0.6.x. Should this be merged into 0.5.x, too?

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Thu Dec 27 16:00:12 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 16:00:12 -0800
Subject: [PATCH] backport the 'frequency' option to 0.5.9
In-Reply-To: <1198745114.15031.20.camel@localhost.localdomain>
References: <1198745114.15031.20.camel@localhost.localdomain>
Message-ID: <20071228000012.GN6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 03:45:14AM -0500, Dan Williams wrote:
> Thanks to stupid drivers, needed on 0.5.9 too.

Thanks. I cherry-picked a064f6fc642771dbc6447413a999a777213b682a from
0.6.x into 0.5.x.

-- 
Jouni Malinen                                            PGP id EFC895FA



From kel  Thu Dec 27 17:48:22 2007
From: kel (Kel Modderman)
Date: Fri, 28 Dec 2007 11:48:22 +1000
Subject: [PATCH] restrict D-Bus interface to root only
In-Reply-To: <20071227234958.GM6450@jm.kir.nu>
References: <1198745293.15031.22.camel@localhost.localdomain>
	<20071227234958.GM6450@jm.kir.nu>
Message-ID: <200712281148.22425.kel@otaku42.de>

On Friday 28 December 2007 09:49:58 Jouni Malinen wrote:
> On Thu, Dec 27, 2007 at 03:48:13AM -0500, Dan Williams wrote:
> > By default; distros can do what they want.  As a bonus, this removes a
> > SUSE/Fedora-ism (debian uses group permissions instead).
>
> Thanks, applied to 0.6.x. Should this be merged into 0.5.x, too?

I don't see why not, all the distro's will have to patch their distroism's 
into this file forever anyway...

Thanks, Kel.



From kel  Thu Dec 27 19:22:46 2007
From: kel (Kel Modderman)
Date: Fri, 28 Dec 2007 13:22:46 +1000
Subject: wpa_gui-qt4 status
Message-ID: <200712281322.46896.kel@otaku42.de>

Hi Jouni,

A year or so ago, it was suggested to stick with the QT3 wpa_gui variant for a 
while, because the port to QT4 was incomplete (and still required QT3 compat 
stuff).

The last few commits seemed to change this, is wpa_gui-qt4 now pretty good to 
use?

On a related note, I see these warnings when starting the current wpa_gui-qt4:

$ wpa_gui
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
QObject::connect: Connecting from COMPAT signal (QAction::activated())
Selected interface 'eth1'
Trying to connect to '/var/run/wpa_supplicant/eth1'

Did a small amount of searching for the cause of this warning, but my QT 
knowledge is pretty poor, and I'm meant to be getting ready to go camping for 
a few days ;-)

Also, when I start wpa_gui, and the supplicant has already successfully
connected to a network predefined in the network configurion (id=1 in this
case), the network id presented in the 'Network:' combo box is set to '0', and
if I attempt to change this to '1' (which is currently active network) in an
attempt to modify that networks settings, connection is lost and the
supplicant seems to experience difficulties (trying to reassociate to
an already associated-to network?). Log attached.

Network 0 is the catch all associate-to-any-open network block.

Update: If I open wpa_cli, and attempt to `select_network 1` and already
connected to network id=1, the same thing happens.

This is git version f320a8b.

Initializing interface 'eth1' conf '/etc/wpa_supplicant/conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/conf' -> '/etc/wpa_supplicant/conf'
Reading configuration file '/etc/wpa_supplicant/conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=netdev'
update_config=1
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=0):
key_mgmt: 0x4
Line: 9 - start of a new network block
ssid - hexdump_ascii(len=6):
     6b 65 6c 6e 65 74                                 kelnet          
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
id_str - hexdump_ascii(len=6):
     6b 65 6c 6e 65 74                                 kelnet          
Priority group 0
   id=0 ssid=''
   id=1 ssid='kelnet'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Interface eth1 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:0e:35:18:2c:a3
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
ctrl_interface_group=108 (from group name 'netdev')
Added interface eth1
Daemonize..
CTRL_IFACE - eth1 - wait for monitor to attach
CTRL_IFACE monitor attached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 672 bytes of scan results (3 BSSes)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1b:2f:98:61:38 ssid='sundhar' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:0f:b5:23:20:f2 ssid='thuis1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - privacy mismatch
   selected non-WPA AP 00:13:10:41:7e:1f ssid='kelnet'
Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2422 MHz)
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=14
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:41:7e:1f
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:13:10:41:7e:1f
Associated with 00:13:10:41:7e:1f
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:13:10:41:7e:1f completed (auth) [id=1 id_str=kelnet]
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
Cancelling scan request
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
WEXT: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
CTRL_IFACE monitor attached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
RX ctrl_iface - hexdump_ascii(len=10):
     49 4e 54 45 52 46 41 43 45 53                     INTERFACES      
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
RX ctrl_iface - hexdump_ascii(len=13):
     4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53            LIST_NETWORKS   
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=16):
     53 45 4c 45 43 54 5f 4e 45 54 57 4f 52 4b 20 31   SELECT_NETWORK 1
CTRL_IFACE: SELECT_NETWORK id=1
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
Scan timeout - try to get results
Received 675 bytes of scan results (3 BSSes)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1b:2f:98:61:38 ssid='sundhar' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:0f:b5:23:20:f2 ssid='thuis1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - disabled
   selected non-WPA AP 00:13:10:41:7e:1f ssid='kelnet'
Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2422 MHz)
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
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_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
wpa_driver_wext_set_drop_unencrypted
State: COMPLETED -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b1a len=14
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
RX ctrl_iface - hexdump_ascii(len=13):
     4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53            LIST_NETWORKS   
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
Authentication with 00:13:10:41:7e:1f timed out.
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
Added BSSID 00:13:10:41:7e:1f into blacklist
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
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
RX ctrl_iface - hexdump_ascii(len=13):
     4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53            LIST_NETWORKS   
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
Scan timeout - try to get results
Received 453 bytes of scan results (2 BSSes)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1b:2f:98:61:38 ssid='sundhar' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:13:10:41:7e:1f ssid='kelnet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - disabled
   selected non-WPA AP 00:13:10:41:7e:1f ssid='kelnet'
Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2422 MHz)
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b1a len=14
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS          
RX ctrl_iface - hexdump_ascii(len=13):
     4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53            LIST_NETWORKS   
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
RX ctrl_iface - hexdump_ascii(len=4):
     50 49 4e 47                                       PING            
Authentication with 00:13:10:41:7e:1f timed out.
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
BSSID 00:13:10:41:7e:1f blacklist count incremented to 2
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
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
CTRL_IFACE monitor detached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 31 39 34 2d 30 00
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
CTRL-EVENT-TERMINATING - signal 15 received
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 32 31 32 37 30 2d 31 00
Removing interface eth1
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
CTRL_IFACE wait for attached monitors to receive messages
Removed BSSID 00:13:10:41:7e:1f from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

Thanks, Kel.



From j  Thu Dec 27 20:23:24 2007
From: j (Jouni Malinen)
Date: Thu, 27 Dec 2007 20:23:24 -0800
Subject: wpa_gui-qt4 status
In-Reply-To: <200712281322.46896.kel@otaku42.de>
References: <200712281322.46896.kel@otaku42.de>
Message-ID: <20071228042324.GO6450@jm.kir.nu>

On Fri, Dec 28, 2007 at 01:22:46PM +1000, Kel Modderman wrote:

> A year or so ago, it was suggested to stick with the QT3 wpa_gui variant for a 
> while, because the port to QT4 was incomplete (and still required QT3 compat 
> stuff).
> 
> The last few commits seemed to change this, is wpa_gui-qt4 now pretty good to 
> use?

Yes, I would say so. As far as functionality and fixes are concerned, it
is now actually even better than Qt3 version and I'm more likely to do
future development with the Qt4 version while Qt3 version is mainly
maintained only for backwards compatibility for systems that do not have
Qt4.

I'm now using Qt4 on my Linux system and consequently, the wpa_gui-qt4
version seems more natural one to work with. In addition, I just changed
the Windows binary builds to use the native Qt4 version (they had always
used Qt4 toolchain, but until today, they were using the old wpa_gui
directory with Qt3 support in Qt4).

> On a related note, I see these warnings when starting the current wpa_gui-qt4:
> 
> $ wpa_gui
> QObject::connect: Connecting from COMPAT signal (QAction::activated())

I don't see these on either Linux (Qt 4.3.2) or Windows (Qt 4.3.3)
builds. Which version of Qt are you using? This is clearly documented to
be Qt3 compatibility signal, but it is somewhat surprising that it is
still working.. Anyway, I'll fix that by changing the activated()
signals to triggered() which seems to be the new name for this QAction
signal.

> Also, when I start wpa_gui, and the supplicant has already successfully
> connected to a network predefined in the network configurion (id=1 in this
> case), the network id presented in the 'Network:' combo box is set to '0', and
> if I attempt to change this to '1' (which is currently active network) in an
> attempt to modify that networks settings, connection is lost and the
> supplicant seems to experience difficulties (trying to reassociate to
> an already associated-to network?). Log attached.
> 
> Network 0 is the catch all associate-to-any-open network block.
> 
> Update: If I open wpa_cli, and attempt to `select_network 1` and already
> connected to network id=1, the same thing happens.

wpa_gui and wpa_cli should behave pretty much same here as far as
network selection is concerned. The only difference would be in the way
wpa_gui automatically updates that combo box and that may sometimes be a
bit confusing..

Based on a quick look through the log, this looks like a potential
driver issue since wpa_supplicant seems to be trying to associate, but
driver does not react to this in any way or well, at least not in a way
that is visible to wpa_supplicant. Which driver are you using?

-- 
Jouni Malinen                                            PGP id EFC895FA



From raghavendra.akkasali  Thu Dec 27 22:42:58 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 28 Dec 2007 12:12:58 +0530
Subject: Is there a way to put wpa supplicant only in scan state?
Message-ID: <58a444250712272242v4870c595o69b03082709387d7@mail.gmail.com>

Hi All,

 Is there a way to put wpa supplicant only in scan state?

I mean can we have some configuration in wpa_supplicant.conf using
which I can put wpa supplicant in scan state. It should never try to
get associated with any of the APs available in that network.

Even it should not get connected to non-secured APs also. It should
just get enabled and should return the scanned info.

-- 
Regards & Thanks
Raghavendra. S



From raghavendra.akkasali  Thu Dec 27 22:56:11 2007
From: raghavendra.akkasali (Raghavendra. S)
Date: Fri, 28 Dec 2007 12:26:11 +0530
Subject: EAP-TLS, whether we should provide password or not?
Message-ID: <58a444250712272256w648c0806p3f66c07c1b52cd4a@mail.gmail.com>

Hi All,

I have following configuration for EAP-TLS.

---------------------------------start----------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
fast_reauth=1
eapol_version=1

network={
        ssid="3Com"
        proto=WPA
        scan_ssid=1
        key_mgmt=WPA-EAP IEEE8021X
        pairwise=CCMP TKIP
        group=CCMP TKIP
        eap=TLS
        identity="jbibe"
        ca_cert="/mnt/nfs/certs/root.pem"
        client_cert="/mnt/nfs/certs/cert-clt.pem"
        private_key="/mnt/nfs/certs/cert-clt.pem"
        private_key_passwd="whatever"
}
---------------------------------start----------------------------------------------------

Is above configuration is correct? or I should provide password also.

sorry i dont have setup to test EAP-TLS. some certificate problem.

-- 
Regards & Thanks
Raghavendra. S



From ruzsinszky.attila  Fri Dec 28 00:23:12 2007
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Fri, 28 Dec 2007 09:23:12 +0100
Subject: Madwifi and hidden SSID
In-Reply-To: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>
References: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>
Message-ID: <f637dd860712280023g3e6968cam2a078a49441b298@mail.gmail.com>

Hi,

No one  has got any clue associating to a hidden SSID AP with
madwifi driver?

TIA,
Ruzsi



From riyaz.list  Fri Dec 28 05:22:47 2007
From: riyaz.list (Mohammed Riyaz)
Date: Fri, 28 Dec 2007 18:52:47 +0530
Subject: hostap compilation issue on 2.6.23.11
Message-ID: <622912820712280522t3c012ac5sec33e8743743ce@mail.gmail.com>

Hi,

I am trying to compile hostap version hostapd-0.6-2007-05-26 on kernel
2.6.23.11. I am trying to get this to compile for mac80211. I have
enabled CONFIG_DRIVER_DEVICESCAPE in the config file.

Initially the build was failing as hostapd_ioctl.h was missing. So I
have added the kernel header path for mac80211 to the makefile. But,
now the problem is with enum value redeclarations.

The values are duplicated across hostap_common.h in the current
directory and the hostapd_ioctl.h in the kernel headers.

Does hostapd-0.6-2007-05-26  build for kernel 2.6.23.11 with mac80211 support??

Regards,
Riyaz



From CTuffli  Fri Dec 28 06:13:55 2007
From: CTuffli (Chuck Tuffli)
Date: Fri, 28 Dec 2007 06:13:55 -0800
Subject: EAP-TLS, whether we should provide password or not?
In-Reply-To: <58a444250712272256w648c0806p3f66c07c1b52cd4a@mail.gmail.com>
References: <58a444250712272256w648c0806p3f66c07c1b52cd4a@mail.gmail.com>
Message-ID: <BC985D0776746A4C8332947B350E01A67BF1C1@USEXCH2003.US-SC.dspcorp.com>

> -----Original Message-----
> From: hostap-bounces+ctuffli=dspg.com at shmoo.com 
> [mailto:hostap-bounces+ctuffli=dspg.com at shmoo.com] On Behalf 
> Of Raghavendra. S
> Sent: Thursday, December 27, 2007 10:56 PM
> To: hostap at shmoo.com
> Subject: EAP-TLS, whether we should provide password or not?
> 
> Hi All,
> 
> I have following configuration for EAP-TLS.
> 
> ---------------------------------start------------------------
----------------------------
> ctrl_interface=/var/run/wpa_supplicant
> ap_scan=1
> fast_reauth=1
> eapol_version=1
> 
> network={
>         ssid="3Com"
>         proto=WPA
>         scan_ssid=1
>         key_mgmt=WPA-EAP IEEE8021X
>         pairwise=CCMP TKIP
>         group=CCMP TKIP
>         eap=TLS
>         identity="jbibe"
>         ca_cert="/mnt/nfs/certs/root.pem"
>         client_cert="/mnt/nfs/certs/cert-clt.pem"
>         private_key="/mnt/nfs/certs/cert-clt.pem"
>         private_key_passwd="whatever"
> }

This looks pretty similar to something I used for testing. The below
seemed like the bare minimum I needed to get a Proxim + FreeRADIUS
working with TLS.

network={
	ssid="myssid"

	# 802.1X
	key_mgmt=WPA-EAP
	proto=RSN
	eap=TLS
	ca_cert="/certs/wifi_ca_cert.pem"
	client_cert="/certs/client_keycert.pem"
	private_key="/certs/client_keycert.pem"
	private_key_passwd="whatever"

	identity="root"
}

---chuck



From dcbw  Fri Dec 28 07:24:32 2007
From: dcbw (Dan Williams)
Date: Fri, 28 Dec 2007 10:24:32 -0500
Subject: [PATCH] restrict D-Bus interface to root only
In-Reply-To: <200712281148.22425.kel@otaku42.de>
References: <1198745293.15031.22.camel@localhost.localdomain>
	<20071227234958.GM6450@jm.kir.nu> <200712281148.22425.kel@otaku42.de>
Message-ID: <1198855472.23441.0.camel@localhost.localdomain>

On Fri, 2007-12-28 at 11:48 +1000, Kel Modderman wrote:
> On Friday 28 December 2007 09:49:58 Jouni Malinen wrote:
> > On Thu, Dec 27, 2007 at 03:48:13AM -0500, Dan Williams wrote:
> > > By default; distros can do what they want.  As a bonus, this removes a
> > > SUSE/Fedora-ism (debian uses group permissions instead).
> >
> > Thanks, applied to 0.6.x. Should this be merged into 0.5.x, too?
> 
> I don't see why not, all the distro's will have to patch their distroism's 
> into this file forever anyway...

Yeah, please apply to 0.5.x too.  Thanks!

Dan





From dcbw  Fri Dec 28 07:26:10 2007
From: dcbw (Dan Williams)
Date: Fri, 28 Dec 2007 10:26:10 -0500
Subject: Is there a way to put wpa supplicant only in scan state?
In-Reply-To: <58a444250712272242v4870c595o69b03082709387d7@mail.gmail.com>
References: <58a444250712272242v4870c595o69b03082709387d7@mail.gmail.com>
Message-ID: <1198855570.23441.2.camel@localhost.localdomain>

On Fri, 2007-12-28 at 12:12 +0530, Raghavendra. S wrote:
> Hi All,
> 
>  Is there a way to put wpa supplicant only in scan state?
> 
> I mean can we have some configuration in wpa_supplicant.conf using
> which I can put wpa supplicant in scan state. It should never try to
> get associated with any of the APs available in that network.
> 
> Even it should not get connected to non-secured APs also. It should
> just get enabled and should return the scanned info.

Don't give it any network blocks, and issue it scan commands explicitly
over the control socket periodically.

Dan





From j  Fri Dec 28 08:02:18 2007
From: j (Jouni Malinen)
Date: Fri, 28 Dec 2007 08:02:18 -0800
Subject: hostap compilation issue on 2.6.23.11
In-Reply-To: <622912820712280522t3c012ac5sec33e8743743ce@mail.gmail.com>
References: <622912820712280522t3c012ac5sec33e8743743ce@mail.gmail.com>
Message-ID: <20071228160218.GP6450@jm.kir.nu>

On Fri, Dec 28, 2007 at 06:52:47PM +0530, Mohammed Riyaz wrote:

> I am trying to compile hostap version hostapd-0.6-2007-05-26 on kernel
> 2.6.23.11. I am trying to get this to compile for mac80211. I have
> enabled CONFIG_DRIVER_DEVICESCAPE in the config file.
> 
> Initially the build was failing as hostapd_ioctl.h was missing. So I
> have added the kernel header path for mac80211 to the makefile. But,
> now the problem is with enum value redeclarations.

The access point code and kernel interface are still very much in flux
and there is no released version of either mac80211 or hostapd that
would really be expected to work properly. Your best chance of compiling
this would likely to be to take the latest development snapshot of both.

> Does hostapd-0.6-2007-05-26  build for kernel 2.6.23.11 with mac80211 support??

No idea and even if it did, it would unlikely work properly.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Fri Dec 28 08:11:25 2007
From: j (Jouni Malinen)
Date: Fri, 28 Dec 2007 08:11:25 -0800
Subject: Internal TLS/crypto in wpa supplicant
In-Reply-To: <000301c8484d$da2700d0$36d06c6b@sisodomain.com>
References: <001d01c80a59$da6aab50$36d06c6b@sisodomain.com>
	<20071010031321.GP14401@jm.kir.nu>
	<000301c8484d$da2700d0$36d06c6b@sisodomain.com>
Message-ID: <20071228161125.GQ6450@jm.kir.nu>

On Thu, Dec 27, 2007 at 11:30:57AM +0530, Mahendra Prajapat wrote:

> I want to use Internal TLS/crypto in wpa supplicant to test EAP-TLS.
> As I  am getting following errors:
> 
> TLSv1: Failed to parse private key

> For testing purpose I require following certificates:
> Client-key.pem
> Client's private key password

The internal TLS/crypto code does not support private keys in PEM format
(must be DER) and neither does it support private key encryption, so the
passphrase here is not going to work either.

-- 
Jouni Malinen                                            PGP id EFC895FA



From ruzsinszky.attila  Fri Dec 28 10:42:20 2007
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Fri, 28 Dec 2007 19:42:20 +0100
Subject: Madwifi and hidden SSID
In-Reply-To: <f637dd860712280023g3e6968cam2a078a49441b298@mail.gmail.com>
References: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>
	<f637dd860712280023g3e6968cam2a078a49441b298@mail.gmail.com>
Message-ID: <f637dd860712281042v34a97b0bu9309d2c45547f52b@mail.gmail.com>

Hi,

> No one  has got any clue associating to a hidden SSID AP with
> madwifi driver?

I did some tests and I found ap_scan=2 doesn't work at all for me.
I unhide my SSID and wpa_supplicant can't connect when ap_scan=2.
Is this correct?

-Dwext doesn't work at all. I must use -W madwifi.

TIA,
Ruzsi



From laurento.frittella  Fri Dec 28 12:55:56 2007
From: laurento.frittella (Laurento Frittella)
Date: Fri, 28 Dec 2007 21:55:56 +0100
Subject: Netgear MA311 firmware update, some strage "warnings"
Message-ID: <1198875356.5292.10.camel@localhost>

I'm trying to update my Prism 2.5 NETGEAR MA311, I read
http://linux.junsun.net/intersil-prism/ but I'd like to have your
opinion about these outputs (without and with -v option)


# prism2_srec wlan0 PK010101.HEX SF010802.HEX 
srec summary for PK010101.HEX
Component: 0x0015 1.1.1 (primary firmware)

srec summary for SF010802.HEX
Component: 0x001f 1.8.2 (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 1:4-4
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 record.
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
OK.



More verbose output...


# prism2_srec -v wlan0 PK010101.HEX SF010802.HEX 
S3 CRC-16 generation record: start=0x007E17FE len=2 prog=0
Start address 0x00000000
srec summary for PK010101.HEX
Component: 0x0015 1.1.1 (primary firmware)
Supported platforms:
  0x800c 1.0.0,  0x8013 1.0.0,  0x8017 1.0.0,  0x801b 1.0.0,  0x8022
1.0.0
Interface compatibility information:
  role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver (3)
  role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
Separate S3 data areas:
S3 area count: 3
  addr=0x007E0000..0x007E0B55 (len=2902)
  addr=0x007E0C00..0x007E151F (len=2336)
  addr=0x007E17FE..0x007E17FF (len=2)
Total data length: 5240
Start address 0x00000000

S3 CRC-16 generation record: start=0x007E1800 len=65536 prog=1
Start address 0x00000000
srec summary for SF010802.HEX
Component: 0x001f 1.8.2 (station firmware)
Supported platforms:
  0x800a 1.0.0,  0x800b 1.0.0,  0x800c 1.0.0,  0x800d 1.0.0,  0x8012
1.0.0
  0x8013 1.0.0,  0x8014 1.0.0,  0x8016 1.0.0,  0x8017 1.0.0,  0x8018
1.0.0
  0x801a 1.0.0,  0x801b 1.0.0,  0x801c 1.0.0,  0x8021 1.0.0,  0x8022
1.0.0
  0x8023 1.0.0
Interface compatibility information:
  role=Supplier variant=2 range=1-15 iface=Station Firmware-Driver (4)
  role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)
  role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
  role=Actor    variant=1 range=4-4 iface=Primary Firmware-Driver (3)
Separate S3 data areas:
S3 area count: 3
  addr=0x007E1800..0x007EEAEF (len=54000)
  addr=0x007F0800..0x007F17FF (len=4096)
  addr=0x007FE000..0x007FECD1 (len=3282)
Total data length: 61378
Start address 0x00000000

Overriding component id and supplied range data using PDA.
Wireless LAN card information:
Components:
  NICID: 0x8013 v1.0.0
  PRIID: 0x0015 v1.0.7
  STAID: 0x001f v1.3.6
Interface compatibility information:
  PRI role=Supplier variant=1 range=1-1 iface=Modem-Firmware (1)
  PRI role=Supplier variant=2 range=1-1 iface=Controller-Firmware (2)
  PRI role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver
(3)
  STA role=Supplier variant=1 range=1-9 iface=Station Firmware-Driver
(4)
  PRI role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
  STA role=Actor    variant=2 range=1-1 iface=Controller-Firmware (2)
  STA role=Actor    variant=1 range=1-1 iface=Modem-Firmware (1)

Verifying update compatibility and combining data:
Plugging PDR 0xffffffff at 0x007e1510 (len=14)
Plugging PDR 0x0003 at 0x007e14b8 (len=12)
PDR 0x0003 not found from wlan card PDA. Using default data.
  len=12: 39 39 53 41 30 31 30 30 30 30 30 30
Plugging PDR 0x0005 at 0x007e1310 (len=2)
PDR 0x0005 not found from wlan card PDA. Using default data.
  len=2: 00 01
Plugging PDR 0x0006 at 0x007e14f0 (len=10)
Plugging PDR 0x0007 at 0x007e1504 (len=10)
Plugging PDR 0x0008 at 0x007e14c4 (len=8)
Plugging PDR 0x0400 at 0x007e1314 (len=2)
Plugging PDR 0x0402 at 0x007e131e (len=4)
Plugging PDR 0x0403 at 0x007e1316 (len=16)
Plugging PDR 0x0404 at 0x007e1326 (len=10)
Plugging PDR 0x0408 at 0x007e1312 (len=2)
PDR 0x0408 not found from wlan card PDA. Using default data.
  len=2: 64 00
Plugging PDR 0x0001 at 0x007e14cc (len=16)
Plug record length mismatch (PDR=0x0001): 12 != 16
==> extend from default
PRI: old iface 1:4-4 new iface 1:4-4
Plugging PDR 0xffffffff at 0x007ee614 (len=14)
Plugging PDR 0x0202 at 0x007f1250 (len=100)
Plugging PDR 0x0203 at 0x007f12b4 (len=128)
Plugging PDR 0x0204 at 0x007f1434 (len=80)
Plugging PDR 0x0405 at 0x007f1484 (len=4)
PDR 0x0405 not found from wlan card PDA. Using default data.
  len=4: 00 00 00 30
Plugging PDR 0x0300 at 0x007f1488 (len=28)
Plugging PDR 0x0301 at 0x007f14a4 (len=34)
Plugging PDR 0x0101 at 0x007f16b0 (len=6)
Plugging PDR 0x0103 at 0x007ee5d6 (len=12)
Plugging PDR 0x0104 at 0x007ee70e (len=2)
Plugging PDR 0x0105 at 0x007f16bc (len=2)
Plugging PDR 0x0105 at 0x007ee744 (len=2)
Plugging PDR 0x0105 at 0x007f17bc (len=2)
Plugging PDR 0x0107 at 0x007ee5e4 (len=2)
Plugging PDR 0x0006 at 0x007ee5b0 (len=10)
Plugging PDR 0x0406 at 0x007f1750 (len=2)
PDR 0x0406 not found from wlan card PDA. Using default data.
  len=2: 64 00
Plugging PDR 0x0302 at 0x007f14cc (len=2)
PDR 0x0302 not found from wlan card PDA. Using default data.
  len=2: 12 00
Plugging PDR 0x0303 at 0x007f14ce (len=2)
PDR 0x0303 not found from wlan card PDA. Using default data.
  len=2: ff 1f
Plugging PDR 0x0412 at 0x007ee764 (len=6)
PDR 0x0412 not found from wlan card PDA. Using default data.
  len=6: ff ff 02 00 02 00
Plugging PDR 0x0413 at 0x0000118a (len=2)
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 record.
Generating CRC-16 (start=0x007e1800, len=65536) at 0x007e17fe
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)
After srec file merge
S3 area count: 5
  addr=0x007E0000..0x007E0B55 (len=2902)
  addr=0x007E0C00..0x007E151F (len=2336)
  addr=0x007E17FE..0x007EEAEF (len=54002)
  addr=0x007F0800..0x007F17FF (len=4096)
  addr=0x007FE000..0x007FECD1 (len=3282)
Total data length: 66618
OK.


Cheers,
Laurento




From proski  Fri Dec 28 13:10:14 2007
From: proski (Pavel Roskin)
Date: Fri, 28 Dec 2007 16:10:14 -0500
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198875356.5292.10.camel@localhost>
References: <1198875356.5292.10.camel@localhost>
Message-ID: <1198876214.4396.2.camel@dv>

On Fri, 2007-12-28 at 21:55 +0100, Laurento Frittella wrote:
> I'm trying to update my Prism 2.5 NETGEAR MA311, I read
> http://linux.junsun.net/intersil-prism/ but I'd like to have your
> opinion about these outputs (without and with -v option)

prism2_srec is very conservative.  If it says OK, then it's OK.  Of
course, I cannot guarantee anything, but I've been reading this list for
many years and I don't remember a single post about prism2_srec bricking
any card.

-- 
Regards,
Pavel Roskin



From laurento.frittella  Fri Dec 28 14:28:38 2007
From: laurento.frittella (Laurento Frittella)
Date: Fri, 28 Dec 2007 23:28:38 +0100
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198876214.4396.2.camel@dv>
References: <1198875356.5292.10.camel@localhost> <1198876214.4396.2.camel@dv>
Message-ID: <1198880918.5292.22.camel@localhost>


Il giorno ven, 28/12/2007 alle 16.10 -0500, Pavel Roskin ha scritto:
> prism2_srec is very conservative.  If it says OK, then it's OK.  Of
> course, I cannot guarantee anything, but I've been reading this list for
> many years and I don't remember a single post about prism2_srec bricking
> any card.

I have found another website http://www.friedhoff.org/ma311.html here
the author shows how he uses his MA311 with the latest firmware loaded
in RAM. I'm interested in his use of the -s option:
  -s   Skip PDA reading and use defaults from the firmware image

Can this option helps me too?


If it can be useful this is my PDA dump:

# prism2_srec wlan0 -D
; PDR 0x0001 data len=12 Platform name / Manufacturing part number
7 0001
5349 334c 3437 3030 004d 0000
; PDR 0x0002 data len=2 PDA Version Record
2 0002
0003
; PDR 0x0006 data len=10 RF Modem Supplier Range
6 0006
0000 0001 0001 0001 0001
; PDR 0x0007 data len=10 MAC Controller Supplier Range
6 0007
0000 0002 0002 0001 0001
; PDR 0x0008 data len=8 NIC ID (component ID)
5 0008
8013 0000 0001 0000
; PDR 0x0101 data len=6 MAC Address
4 0101
0900 675b 7a4e
; PDR 0x0103 data len=12 Regulatory Domain List
7 0103
0001 0030 0000 0000 0000 0000
; PDR 0x0104 data len=2 Allowed Channel Set/Active Channel List
2 0104
1fff
; PDR 0x0105 data len=2 Default Channel
2 0105
0003
; PDR 0x0107 data len=2 Temperature Type
2 0107
0001
; PDR 0x0202 data len=100 3861 Baseline Register Settings
33 0202
0200 0401 0638 0880 0a13 0c04 0e04 1000 12a2 14c8 1603 1800 1a00 1c00
1e5c 2082 221e 24c7 2617 286a 2a12 2c00 2e00 302d 3220 3482 3618 3879
3aca 3c24 3ec6 4000 4200 4400 467f 488b 4a0f 4c06 4e0a 500f 5220 5420
5610 5810 5a20 5cee 5e1e 6026 625b 0400
; PDR 0x0203 data len=128 3861 Shadow Register Settings
41 0203
2c00 2e0c 2c01 2e10 2c02 2e14 2c03 2e18 2c04 2e1c 2c05 2e20 2c06 2e24
2c07 2e28 2c08 2e2e 2c09 2e34 2c0a 2e38 2c0b 2e3c 2c0c 2e3f 2c0d 2e43
2c0e 2e46 2c0f 2e48 2c10 2e4b 2c11 2e50 2c12 2e55 2c13 2e5a 2c14 2e63
2c15 2e6d 2c16 2e76 2c17 2e7f 2c18 2e7f 2c19 2e7f 2c1a 2e7f 2c1b 2e7f
2c1c 2e7f 2c1d 2e7f 2c1e 2e7f 2c1f 2e7f
; PDR 0x0204 data len=80 3861 IF/RF Register Settings
29 0204
0003 5000 0006 7000 0016 0000 05c6 6000 0007 5000 002c 0000 0fe5 e000
0fea e000 0fef e000 1004 e000 1009 e000 100e e000 1023 e000 1028 e000
102d e000 1042 e000 1047 e000 104c e000 1061 e000 106d e000
; PDR 0x0300 data len=28 3861 Channel Calibration Set Point
f 0300
00d5 00dd 00e6 00ee 00f4 00f7 00f2 00f0 00ef 00f2 00f1 00f4 00f5 00db
; PDR 0x0301 data len=34 3861 Channel Calibration Integrator
12 0301
00c2 00c2 00c2 00c2 00c2 00c2 00c6 00c6 00c6 00c6 00ca 00ca 00ca 00bc
00e9 0000 0025
; PDR 0x0400 data len=2 3842 PRISM II NIC Configuration
2 0400
0007
; PDR 0x0402 data len=4 PRISM PCI Identifier
3 0402
4105 1385
; PDR 0x0403 data len=16 PRISM PCI Interface Configuration
9 0403
0000 0200 8000 0101 3873 1260 3873 1260
; PDR 0x0404 data len=10 PRISM PCI PM Configuration
6 0404
0001 0000 0000 7e02 0001
; PDR 0x0900 data len=60 3861 Manufacturing Test Channel Set Points
1f 0900
00d5 00dd 00e6 00ee 00f4 00f7 00f2 00f0 00ef 00f2 00f1 00f4 00f5 00db
00d5 00f5 00d5 00dd 00e6 00ee 00f4 00f7 00f2 00f0 00ef 00f2 00f1 00f4
00f5 00db
; PDR 0x0901 data len=66 Manufacturing Test Channel Integrators
22 0901
00c2 00c2 00c2 00c2 00c2 00c2 00c6 00c6 00c6 00c6 00ca 00ca 00ca 00bc
00c2 00ca 00c2 00c2 00c2 00c2 00c2 00c2 00c6 00c6 00c6 00c6 00ca 00ca
00ca 00bc 00e9 0000 0025
; PDR 0x0000 data len=2 PDA End Record
2 0000
6095


Cheers,
Laurento




From proski  Fri Dec 28 14:53:36 2007
From: proski (Pavel Roskin)
Date: Fri, 28 Dec 2007 17:53:36 -0500
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198880918.5292.22.camel@localhost>
References: <1198875356.5292.10.camel@localhost>
	<1198876214.4396.2.camel@dv>  <1198880918.5292.22.camel@localhost>
Message-ID: <1198882416.22736.5.camel@dv>


On Fri, 2007-12-28 at 23:28 +0100, Laurento Frittella wrote:
> Il giorno ven, 28/12/2007 alle 16.10 -0500, Pavel Roskin ha scritto:
> > prism2_srec is very conservative.  If it says OK, then it's OK.  Of
> > course, I cannot guarantee anything, but I've been reading this list for
> > many years and I don't remember a single post about prism2_srec bricking
> > any card.
> 
> I have found another website http://www.friedhoff.org/ma311.html here
> the author shows how he uses his MA311 with the latest firmware loaded
> in RAM. I'm interested in his use of the -s option:
>   -s   Skip PDA reading and use defaults from the firmware image

I don't see "-s" on that page.

> Can this option helps me too?

You didn't specify your goal, so I don't know the answer.  If your goal
is to lose all individual data from your card, including its MAC address
and the allowed channel list, then it may help.

-- 
Regards,
Pavel Roskin



From j  Fri Dec 28 15:18:49 2007
From: j (Jouni Malinen)
Date: Fri, 28 Dec 2007 15:18:49 -0800
Subject: Madwifi and hidden SSID
In-Reply-To: <f637dd860712281042v34a97b0bu9309d2c45547f52b@mail.gmail.com>
References: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>
	<f637dd860712280023g3e6968cam2a078a49441b298@mail.gmail.com>
	<f637dd860712281042v34a97b0bu9309d2c45547f52b@mail.gmail.com>
Message-ID: <20071228231849.GE12245@jm.kir.nu>

On Fri, Dec 28, 2007 at 07:42:20PM +0100, Ruzsinszky Attila wrote:

> I did some tests and I found ap_scan=2 doesn't work at all for me.
> I unhide my SSID and wpa_supplicant can't connect when ap_scan=2.
> Is this correct?
> 
> -Dwext doesn't work at all. I must use -W madwifi.

Which version of madwifi driver are you using? I'm using -Dwext with
madwifi 0.9.3 and both ap_scan=1 and ap_scan=2 have worked fine in my
tests. I don't use hidden SSIDs (they are quite pointless from security
view point), so I'm not sure about the current madwifi status for them.

-- 
Jouni Malinen                                            PGP id EFC895FA



From j  Fri Dec 28 15:26:06 2007
From: j (Jouni Malinen)
Date: Fri, 28 Dec 2007 15:26:06 -0800
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198880918.5292.22.camel@localhost>
References: <1198875356.5292.10.camel@localhost> <1198876214.4396.2.camel@dv>
	<1198880918.5292.22.camel@localhost>
Message-ID: <20071228232606.GF12245@jm.kir.nu>

On Fri, Dec 28, 2007 at 11:28:38PM +0100, Laurento Frittella wrote:

> I have found another website http://www.friedhoff.org/ma311.html here
> the author shows how he uses his MA311 with the latest firmware loaded
> in RAM. I'm interested in his use of the -s option:
>   -s   Skip PDA reading and use defaults from the firmware image
> 
> Can this option helps me too?

Help with what? I did not see any problem being reported in either of
your messages to the mailing list.. Anyway, I would not recommend using
'-s' unless you have a specific reason to do that.

If you want to first test a newer firmware version without upgrading the
device flash, you may be able to run the RAM downloadable version ('-r'
on prism2_srec command line).

-- 
Jouni Malinen                                            PGP id EFC895FA



From laurento.frittella  Fri Dec 28 15:50:38 2007
From: laurento.frittella (Laurento Frittella)
Date: Sat, 29 Dec 2007 00:50:38 +0100
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <20071228232606.GF12245@jm.kir.nu>
References: <1198875356.5292.10.camel@localhost>
	<1198876214.4396.2.camel@dv> <1198880918.5292.22.camel@localhost>
	<20071228232606.GF12245@jm.kir.nu>
Message-ID: <1198885838.5292.29.camel@localhost>

> If you want to first test a newer firmware version without upgrading the
> device flash, you may be able to run the RAM downloadable version ('-r'
> on prism2_srec command line).

Ok now I know -s it's "bad" in my case...

For "problem" I mean these messages:
"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 record.
Allowing S3 overlap due to CRC-16 signature at 0x007e17fe (was: ffff)"

And I'd like to test 1.8.2 before flash it but I haven't found any AK...
and RF... only PK and SF for this version and 1.8.4 seems to have
problems with "long distance" so I thought to try with 1.8.2 (as
suggested in the first website I've linked).

Cheers,
Laurento




From webmail.hce  Fri Dec 28 20:18:18 2007
From: webmail.hce (hce)
Date: Sat, 29 Dec 2007 15:18:18 +1100
Subject: buffer size for wpa_ctrl_recv
Message-ID: <95455e980712282018n2521ab38we86aca87b59224b9@mail.gmail.com>

Hi,

What buffer size need be defined for calling wpa_ctrl_recv(ctrl_conn,
buf, &len)? And what's happen if the replay_len is smaller than the
real size, will the function returns a trucked data, or an error?

Thank you.

Jim



From webmail.hce  Fri Dec 28 20:28:04 2007
From: webmail.hce (hce)
Date: Sat, 29 Dec 2007 15:28:04 +1100
Subject: wpa events, poll or callback
Message-ID: <95455e980712282028k459a9608n6a923e1e14b26b96@mail.gmail.com>

Hi,

Is there an asynchronise call back mechanism to get events from
control interface? Or, should I use a poll method to get events from
the control interface?

Thank you.

Jim



From jar  Sat Dec 29 01:21:57 2007
From: jar (Jar)
Date: Sat, 29 Dec 2007 11:21:57 +0200
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198875356.5292.10.camel@localhost>
References: <1198875356.5292.10.camel@localhost>
Message-ID: <477611B5.6040705@pcuf.fi>

Laurento Frittella wrote:
> I'm trying to update my Prism 2.5 NETGEAR MA311, I read
> http://linux.junsun.net/intersil-prism/ but I'd like to have your
> opinion about these outputs (without and with -v option)
> 
> 
> # prism2_srec wlan0 PK010101.HEX SF010802.HEX 
> srec summary for PK010101.HEX
> Component: 0x0015 1.1.1 (primary firmware)
> 
> srec summary for SF010802.HEX
> Component: 0x001f 1.8.2 (station firmware)

I would suggest the versions PRI=v1.1.1 STA=v1.7.4, because this 
combination seems to work best.

hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
prism2_hw_init: initialized in 198 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: Intersil Prism2.5 PCI: mem=0xdfbff000, irq=21
wifi0: registered netdevice wlan0

-- 
Best Regards, Jar



From ruzsinszky.attila  Sat Dec 29 03:20:48 2007
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Sat, 29 Dec 2007 12:20:48 +0100
Subject: Madwifi and hidden SSID
In-Reply-To: <20071228231849.GE12245@jm.kir.nu>
References: <f637dd860712221033p43bb2661i878cc402377f3ff6@mail.gmail.com>
	<f637dd860712280023g3e6968cam2a078a49441b298@mail.gmail.com>
	<f637dd860712281042v34a97b0bu9309d2c45547f52b@mail.gmail.com>
	<20071228231849.GE12245@jm.kir.nu>
Message-ID: <f637dd860712290320i2fa0d5d0m4f64ce75caeeeebe@mail.gmail.com>

> Which version of madwifi driver are you using? I'm using -Dwext with
As I mentioned here in my first letter
SuSE 10.3, wpa_supplicant-0.5.8-37
madwifi-kmp-default-0.9.3.3_2.6.22.9_0.4-0.1
madwifi-0.9.3.2-0.1

> tests. I don't use hidden SSIDs (they are quite pointless from security
> view point), so I'm not sure about the current madwifi status for them.
I know hidden SSID isn't the best security solution I want to send as few
as possible information as the hardvare and software can.
I use MAC filter and WPA/WPA2+EAP-TLS, too.

Now the solution is the unhidden SSID.
-Dwext can't connect at all. With or without hidden SSID, any ap_scan
or ssid_scan settings.

TIA,
Ruzsi



From laurento.frittella  Sat Dec 29 05:42:38 2007
From: laurento.frittella (Laurento Frittella)
Date: Sat, 29 Dec 2007 14:42:38 +0100
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <477611B5.6040705@pcuf.fi>
References: <1198875356.5292.10.camel@localhost>  <477611B5.6040705@pcuf.fi>
Message-ID: <1198935759.26665.6.camel@localhost>


Il giorno sab, 29/12/2007 alle 11.21 +0200, Jar ha scritto:
> I would suggest the versions PRI=v1.1.1 STA=v1.7.4, because this 
> combination seems to work best.

Ok I'll give it a try but I'm interested in WPA and it seems to be
supported since 1.8.2
I'm actually using OpenVPN to secure my wifi link but I think WPA should
introduces less overhead -> better performance

Cheers,
Laurento




From jar  Sat Dec 29 06:39:41 2007
From: jar (Jar)
Date: Sat, 29 Dec 2007 16:39:41 +0200
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <1198935759.26665.6.camel@localhost>
References: <1198875356.5292.10.camel@localhost> <477611B5.6040705@pcuf.fi>
	<1198935759.26665.6.camel@localhost>
Message-ID: <47765C2D.50908@pcuf.fi>

Laurento Frittella wrote:
> Ok I'll give it a try but I'm interested in WPA and it seems to be
> supported since 1.8.2

No, it is also supported in v1.7.4. According to the hostapd README, the 
firmware version needs to be 1.7.0 or newer to support WPA.

> I'm actually using OpenVPN to secure my wifi link but I think WPA should
> introduces less overhead -> better performance

Sure.

-- 
Best Regards, Jar



From laurento.frittella  Sat Dec 29 08:34:27 2007
From: laurento.frittella (Laurento Frittella)
Date: Sat, 29 Dec 2007 17:34:27 +0100
Subject: Netgear MA311 firmware update, some strage "warnings"
In-Reply-To: <47765C2D.50908@pcuf.fi>
References: <1198875356.5292.10.camel@localhost>  <477611B5.6040705@pcuf.fi>
	<1198935759.26665.6.camel@localhost>  <47765C2D.50908@pcuf.fi>
Message-ID: <1198946067.26665.12.camel@localhost>


Il giorno sab, 29/12/2007 alle 16.39 +0200, Jar ha scritto:
> Laurento Frittella wrote:
> > Ok I'll give it a try but I'm interested in WPA and it seems to be
> > supported since 1.8.2
> 
> No, it is also supported in v1.7.4. According to the hostapd README, the 
> firmware version needs to be 1.7.0 or newer to support WPA.

Interesting... I read about WPA and 1.8.2 on this website
http://linux.junsun.net/intersil-prism/ I think I'll write an email to
the author about this. That website seems to be very popular and this
info can helps other people searching for the best firmware to use ;)

Cheers,
Laurento




From laurento.frittella  Sun Dec 30 03:50:53 2007
From: laurento.frittella (Laurento Frittella)
Date: Sun, 30 Dec 2007 12:50:53 +0100
Subject: Which LiveCD has prism2_srec and a kernel with non-volatile flash
	enabled?
Message-ID: <1199015453.15781.2.camel@localhost>

I'm searching for a LiveCD to flash my prism2.5, any suggestion?

Cheers,
Laurento




From ruzsinszky.attila  Sun Dec 30 04:55:07 2007
From: ruzsinszky.attila (Ruzsinszky Attila)
Date: Sun, 30 Dec 2007 13:55:07 +0100
Subject: hostapd madwifi problem under SuSE 10.3
Message-ID: <f637dd860712300455j5ac482cfn5991959bd6d23ff2@mail.gmail.com>

Hi,

Is that means no madwifi driver compiled in my hostapd:

#hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
Line 14: invalid/unknown driver 'madwifi'
1 errors found in configuration file '/etc/hostapd.conf'

driver=madwifi in the config.

I checked any madwifi string in hostapd and I can't find.

hostapd-0.5.8-31

TIA,
Ruzsi



From leenax  Mon Dec 31 00:32:48 2007
From: leenax (Leena Soman)
Date: Mon, 31 Dec 2007 14:02:48 +0530
Subject: Preauthentication configuration
In-Reply-To: <20071226183625.GH6450@jm.kir.nu>
References: <a4a1fe4a0712232305m52050fdew8f0846c9cc1c2139@mail.gmail.com>
	<20071226183625.GH6450@jm.kir.nu>
Message-ID: <a4a1fe4a0712310032t27132221y7af15b9277325244@mail.gmail.com>

Thanks Jouni,
It did work after I bridged the 2 interfaces and specified the bridge
interface as the preauth interface in the hostapd configuration.
Thanks for your reply.
Leena.

On Dec 27, 2007 12:06 AM, Jouni Malinen <j at w1.fi> wrote:

> On Mon, Dec 24, 2007 at 12:35:22PM +0530, Leena Soman wrote:
>
> > I want to configure my network so that my supplicant is able to
> > preauthenticate with an AP. For this,  I have 2 APs - AP1 - hostapd on
> Linux
> > and a Linksys  WRT54G -  AP2 , both with preauthentication enabled.  I
> have
> > configured both with the same SSID, the security policy being
> WPA2-EAP(TLS).
> > My supplicant gets associated successfully with AP1 and then I also see
> it
> > sending out an EAPOL-Start on the wireless interface, with the
> destination
> > mac address of AP2. But I don't see anything being received at AP2. Do I
> > need to configure the hostpad interfaces as a birdge?
>
> You will need to make sure that the AP sends RSN pre-authentication
> packets properly. In most cases, this means that the WLAN interface and
> wired interface will need to be bridged together.
>
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20071231/aeca9b44/attachment.htm 


From linux-ra  Mon Dec 31 04:47:30 2007
From: linux-ra (Robert Allerstorfer)
Date: Mon, 31 Dec 2007 13:47:30 +0100
Subject: wpa_supplicant service fails to autostart on Fedora 8
Message-ID: <147350010.20071231134730@anet.at>

I am trying to activate the wlan0 device automatically at booting
Fedora 8. It should associate to my WPA2-personal protected Access
Point. Since NetworkManager 0.7 svn3109 does NOT work for this, I
don't start that service. Instead, I have set the wpa_supplicant
service to autostart. This will run
'wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
-Dwext -B -u -f -d'
which fails while booting:
[root at localhost ~]# cat /var/log/wpa_supplicant.log
Could not acquire the system bus.

However, the same command succeeds in an already booted system:
[root at localhost ~]# grep "State: " /var/log/wpa_supplicant.log
State: DISCONNECTED -> SCANNING
State: SCANNING -> ASSOCIATING
State: ASSOCIATING -> ASSOCIATED
State: ASSOCIATED -> 4WAY_HANDSHAKE
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
State: GROUP_HANDSHAKE -> COMPLETED

The autostart failure seems to be related to wpa_supplicant's -u
option (enable DBus control interface). Here is the order of all
services to be autostarted in the default runlevel:

[root at localhost ~]# ls -l /etc/rc.d/rc5.d | grep S
lrwxrwxrwx 1 root root 15 2007-12-29 23:28 S05kudzu -> ../init.d/kudzu
lrwxrwxrwx 1 root root 18 2007-12-29 23:24 S06cpuspeed -> ../init.d/cpuspeed
lrwxrwxrwx 1 root root 19 2007-12-29 11:55 S08ip6tables -> ../init.d/ip6tables
lrwxrwxrwx 1 root root 18 2007-12-29 11:54 S08iptables -> ../init.d/iptables
lrwxrwxrwx 1 root root 14 2007-12-29 23:39 S09isdn -> ../init.d/isdn
lrwxrwxrwx 1 root root 17 2007-12-29 23:28 S10network -> ../init.d/network
lrwxrwxrwx 1 root root 16 2007-12-29 23:20 S11auditd -> ../init.d/auditd
lrwxrwxrwx 1 root root 21 2007-12-29 23:30 S12restorecond -> ../init.d/restorecond
lrwxrwxrwx 1 root root 24 2007-12-31 03:48 S12wpa_supplicant -> ../init.d/wpa_supplicant
                                              ^^^^^^^^^^^^^^
lrwxrwxrwx 1 root root 20 2007-12-29 11:58 S13irqbalance -> ../init.d/irqbalance
lrwxrwxrwx 1 root root 17 2007-12-29 23:20 S13rpcbind -> ../init.d/rpcbind
lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S14nfslock -> ../init.d/nfslock
lrwxrwxrwx 1 root root 19 2007-12-29 23:37 S15mdmonitor -> ../init.d/mdmonitor
lrwxrwxrwx 1 root root 19 2007-12-29 23:39 S18rpcidmapd -> ../init.d/rpcidmapd
lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S19rpcgssd -> ../init.d/rpcgssd
lrwxrwxrwx 1 root root 15 2007-12-29 23:28 S25netfs -> ../init.d/netfs
lrwxrwxrwx 1 root root 15 2007-12-29 23:44 S25pcscd -> ../init.d/pcscd
lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S26rsyslog -> ../init.d/rsyslog
lrwxrwxrwx 1 root root 19 2007-12-29 23:28 S26udev-post -> ../init.d/udev-post
lrwxrwxrwx 1 root root 20 2007-12-29 12:35 S27messagebus -> ../init.d/messagebus
lrwxrwxrwx 1 root root 24 2007-12-29 12:35 S27setroubleshoot -> ../init.d/setroubleshoot
lrwxrwxrwx 1 root root 16 2007-12-29 23:24 S28autofs -> ../init.d/autofs
lrwxrwxrwx 1 root root 19 2007-12-29 12:35 S50bluetooth -> ../init.d/bluetooth
lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S50iprinit -> ../init.d/iprinit
lrwxrwxrwx 1 root root 19 2007-12-29 12:35 S50iprupdate -> ../init.d/iprupdate
lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S51iprdump -> ../init.d/iprdump
lrwxrwxrwx 1 root root 14 2007-12-29 23:39 S55sshd -> ../init.d/sshd
lrwxrwxrwx 1 root root 18 2007-12-29 12:35 S80sendmail -> ../init.d/sendmail
lrwxrwxrwx 1 root root 20 2007-12-29 23:28 S90ConsoleKit -> ../init.d/ConsoleKit
lrwxrwxrwx 1 root root 15 2007-12-29 23:24 S90crond -> ../init.d/crond
lrwxrwxrwx 1 root root 13 2007-12-29 23:24 S95atd -> ../init.d/atd
lrwxrwxrwx 1 root root 22 2007-12-29 17:15 S96avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 22 2007-12-29 12:28 S97yum-updatesd -> ../init.d/yum-updatesd
lrwxrwxrwx 1 root root 14 2007-12-29 23:37 S98cups -> ../init.d/cups
lrwxrwxrwx 1 root root 19 2007-12-29 23:43 S98haldaemon -> ../init.d/haldaemon
lrwxrwxrwx 1 root root 17 2007-12-29 11:58 S99anacron -> ../init.d/anacron
lrwxrwxrwx 1 root root 19 2007-12-29 23:36 S99firstboot -> ../init.d/firstboot
lrwxrwxrwx 1 root root 11 2007-12-29 23:28 S99local -> ../rc.local

Should this order be tweaked for wpa_supplicant to start successfully?

rob.





mfg,

Ing. Robert Allerstorfer
ANET - New Media Solutions
Allerstorfer & Beutel OEG
www.anet.at

--




From bryan  Mon Dec 31 05:35:48 2007
From: bryan (Bryan Kadzban)
Date: Mon, 31 Dec 2007 08:35:48 -0500
Subject: wpa_supplicant service fails to autostart on Fedora 8
In-Reply-To: <147350010.20071231134730@anet.at>
References: <147350010.20071231134730@anet.at>
Message-ID: <4778F034.2030304@kadzban.is-a-geek.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Robert Allerstorfer wrote:
> The autostart failure seems to be related to wpa_supplicant's -u
> option (enable DBus control interface).

Do you need that interface?  If not, remove that option; that's probably
the simplest solution.

> lrwxrwxrwx 1 root root 24 2007-12-31 03:48 S12wpa_supplicant -> ../init.d/wpa_supplicant
> <...>
> lrwxrwxrwx 1 root root 17 2007-12-29 23:20 S13rpcbind -> ../init.d/rpcbind
> lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S14nfslock -> ../init.d/nfslock
> <...>
> lrwxrwxrwx 1 root root 19 2007-12-29 23:39 S18rpcidmapd -> ../init.d/rpcidmapd
> lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S19rpcgssd -> ../init.d/rpcgssd
> lrwxrwxrwx 1 root root 15 2007-12-29 23:28 S25netfs -> ../init.d/netfs

OK, it needs to be before most of these (or at least netfs), because
netfs depends on the network if you have any remote filesystems in
/etc/fstab.

> lrwxrwxrwx 1 root root 15 2007-12-29 23:44 S25pcscd -> ../init.d/pcscd

However, it probably needs to be after this if you use any smartcard
stuff in your configuration, and:

> lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S26rsyslog -> ../init.d/rsyslog

it does need to be after this if you tell it to log its output to
syslog, and:

> lrwxrwxrwx 1 root root 20 2007-12-29 12:35 S27messagebus -> ../init.d/messagebus

it does need to be after this if it uses D-Bus.

> Should this order be tweaked for wpa_supplicant to start successfully?

Yes, or the wpa_supplicant configuration needs to be changed.  There is
no way with the Fedora bootscripts to have a remote filesystem on a
wpa_supplicant network if wpa_supplicant requires D-Bus, smart-card, or
syslog support (I'd consider that a bug in Fedora, but you can't easily
fix it).  If you don't need networked FSes, then you'll still need
pcscd, rsyslog, and messagebus, so put it somewhere around S30.

(Or S99, since haldaemon is starting at S98, and D-Bus is required for
HAL too.  But that's drastic...)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHePAzS5vET1Wea5wRAyevAJ4iVlRoUp6Kgro52LouudBWs6OLzgCgxIXu
Z/Jbg3YGLaCUIDbPVSOYX9s=
=OI0t
-----END PGP SIGNATURE-----



From dcbw  Mon Dec 31 08:10:37 2007
From: dcbw (Dan Williams)
Date: Mon, 31 Dec 2007 11:10:37 -0500
Subject: wpa_supplicant service fails to autostart on Fedora 8
In-Reply-To: <147350010.20071231134730@anet.at>
References: <147350010.20071231134730@anet.at>
Message-ID: <1199117437.4697.3.camel@localhost.localdomain>

On Mon, 2007-12-31 at 13:47 +0100, Robert Allerstorfer wrote:
> I am trying to activate the wlan0 device automatically at booting
> Fedora 8. It should associate to my WPA2-personal protected Access
> Point. Since NetworkManager 0.7 svn3109 does NOT work for this, I
> don't start that service. Instead, I have set the wpa_supplicant
> service to autostart. This will run
> 'wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
> -Dwext -B -u -f -d'
> which fails while booting:
> [root at localhost ~]# cat /var/log/wpa_supplicant.log
> Could not acquire the system bus.

You're probably interested in Fedora bug #244029.  That's the best place
to track your issue since it's a Fedora specific issue.

Dan


> However, the same command succeeds in an already booted system:
> [root at localhost ~]# grep "State: " /var/log/wpa_supplicant.log
> State: DISCONNECTED -> SCANNING
> State: SCANNING -> ASSOCIATING
> State: ASSOCIATING -> ASSOCIATED
> State: ASSOCIATED -> 4WAY_HANDSHAKE
> State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
> State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
> State: GROUP_HANDSHAKE -> COMPLETED
> 
> The autostart failure seems to be related to wpa_supplicant's -u
> option (enable DBus control interface). Here is the order of all
> services to be autostarted in the default runlevel:
> 
> [root at localhost ~]# ls -l /etc/rc.d/rc5.d | grep S
> lrwxrwxrwx 1 root root 15 2007-12-29 23:28 S05kudzu -> ../init.d/kudzu
> lrwxrwxrwx 1 root root 18 2007-12-29 23:24 S06cpuspeed -> ../init.d/cpuspeed
> lrwxrwxrwx 1 root root 19 2007-12-29 11:55 S08ip6tables -> ../init.d/ip6tables
> lrwxrwxrwx 1 root root 18 2007-12-29 11:54 S08iptables -> ../init.d/iptables
> lrwxrwxrwx 1 root root 14 2007-12-29 23:39 S09isdn -> ../init.d/isdn
> lrwxrwxrwx 1 root root 17 2007-12-29 23:28 S10network -> ../init.d/network
> lrwxrwxrwx 1 root root 16 2007-12-29 23:20 S11auditd -> ../init.d/auditd
> lrwxrwxrwx 1 root root 21 2007-12-29 23:30 S12restorecond -> ../init.d/restorecond
> lrwxrwxrwx 1 root root 24 2007-12-31 03:48 S12wpa_supplicant -> ../init.d/wpa_supplicant
>                                               ^^^^^^^^^^^^^^
> lrwxrwxrwx 1 root root 20 2007-12-29 11:58 S13irqbalance -> ../init.d/irqbalance
> lrwxrwxrwx 1 root root 17 2007-12-29 23:20 S13rpcbind -> ../init.d/rpcbind
> lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S14nfslock -> ../init.d/nfslock
> lrwxrwxrwx 1 root root 19 2007-12-29 23:37 S15mdmonitor -> ../init.d/mdmonitor
> lrwxrwxrwx 1 root root 19 2007-12-29 23:39 S18rpcidmapd -> ../init.d/rpcidmapd
> lrwxrwxrwx 1 root root 17 2007-12-29 23:39 S19rpcgssd -> ../init.d/rpcgssd
> lrwxrwxrwx 1 root root 15 2007-12-29 23:28 S25netfs -> ../init.d/netfs
> lrwxrwxrwx 1 root root 15 2007-12-29 23:44 S25pcscd -> ../init.d/pcscd
> lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S26rsyslog -> ../init.d/rsyslog
> lrwxrwxrwx 1 root root 19 2007-12-29 23:28 S26udev-post -> ../init.d/udev-post
> lrwxrwxrwx 1 root root 20 2007-12-29 12:35 S27messagebus -> ../init.d/messagebus
> lrwxrwxrwx 1 root root 24 2007-12-29 12:35 S27setroubleshoot -> ../init.d/setroubleshoot
> lrwxrwxrwx 1 root root 16 2007-12-29 23:24 S28autofs -> ../init.d/autofs
> lrwxrwxrwx 1 root root 19 2007-12-29 12:35 S50bluetooth -> ../init.d/bluetooth
> lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S50iprinit -> ../init.d/iprinit
> lrwxrwxrwx 1 root root 19 2007-12-29 12:35 S50iprupdate -> ../init.d/iprupdate
> lrwxrwxrwx 1 root root 17 2007-12-29 12:35 S51iprdump -> ../init.d/iprdump
> lrwxrwxrwx 1 root root 14 2007-12-29 23:39 S55sshd -> ../init.d/sshd
> lrwxrwxrwx 1 root root 18 2007-12-29 12:35 S80sendmail -> ../init.d/sendmail
> lrwxrwxrwx 1 root root 20 2007-12-29 23:28 S90ConsoleKit -> ../init.d/ConsoleKit
> lrwxrwxrwx 1 root root 15 2007-12-29 23:24 S90crond -> ../init.d/crond
> lrwxrwxrwx 1 root root 13 2007-12-29 23:24 S95atd -> ../init.d/atd
> lrwxrwxrwx 1 root root 22 2007-12-29 17:15 S96avahi-daemon -> ../init.d/avahi-daemon
> lrwxrwxrwx 1 root root 22 2007-12-29 12:28 S97yum-updatesd -> ../init.d/yum-updatesd
> lrwxrwxrwx 1 root root 14 2007-12-29 23:37 S98cups -> ../init.d/cups
> lrwxrwxrwx 1 root root 19 2007-12-29 23:43 S98haldaemon -> ../init.d/haldaemon
> lrwxrwxrwx 1 root root 17 2007-12-29 11:58 S99anacron -> ../init.d/anacron
> lrwxrwxrwx 1 root root 19 2007-12-29 23:36 S99firstboot -> ../init.d/firstboot
> lrwxrwxrwx 1 root root 11 2007-12-29 23:28 S99local -> ../rc.local
> 
> Should this order be tweaked for wpa_supplicant to start successfully?
> 
> rob.
> 
> 
> 
> 
> 
> mfg,
> 
> Ing. Robert Allerstorfer
> ANET - New Media Solutions
> Allerstorfer & Beutel OEG
> www.anet.at
> 
> --
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap




