HostAP Digest, Vol 31, Issue 32

[Duncan Grove]

I'll be there.

We forfeited last week :-( . Greg, Geoff and myself were there but 
Kriegy got the wrong time and Chop, what happened to you? I gather we'll 
need to stump up $ for the forfeit but I'm not sure how much it is. 
Geoff? I guess we'll just share it around...?

Cheers,
Duncan

hostap-request at shmoo.com wrote:

>Send HostAP mailing list submissions to
>	hostap at shmoo.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.shmoo.com/mailman/listinfo/hostap
>or, via email, send a message with subject or body 'help' to
>	hostap-request at shmoo.com
>
>You can reach the person managing the list at
>	hostap-owner at shmoo.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of HostAP digest..."
>
>
>Today's Topics:
>
>   1. Re: Handoff with wpa_supplicant and madwifi driver
>      (Leonardo Maccari)
>   2. Re: wpa_supplicant & winpcap & windows 2000 (Bryan Kadzban)
>   3. RE: wpa_supplicant PSK question (Bob Carlson)
>   4. wpasupplicant/madwifi and bridging (Elias Oltmanns)
>   5. RE: wpa_supplicant PSK question (Bob Carlson)
>   6. Re: wpa_supplicant PSK question (Bryan Kadzban)
>   7. RE: wpa_supplicant PSK question - update (Bob Carlson)
>   8. Re: wpa_supplicant & winpcap & windows 2000 (engage)
>   9. Re: wpa_supplicant PSK question (Jouni Malinen)
>  10. Re: wpa_supplicant PSK question - update (Jouni Malinen)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 22 Nov 2005 12:47:41 +0100
>From: Leonardo Maccari
>	<maccari-thisaintpartofmyaddress- at lenst.det.unifi.it>
>Subject: Re: Handoff with wpa_supplicant and madwifi driver
>To: hostap at shmoo.com
>Message-ID: <20051122114741.GB19458 at lenst.det.unifi.it>
>Content-Type: text/plain; charset=us-ascii
>
>On Sat, Nov 19, 2005 at 01:14:45PM -0800, Stephan Schlumbohm wrote:
>  
>
>>Hi all,
>>
>>I'm having serious trouble with the handoff from one access point to
>>    
>>
>another using wpa_supplicant (stable 0.3.8 and development 0.4.6) with
>the madwifi driver (madwifi-ng latest svn snapshot from madwifi.org).
>  
>
>>Both access points have the same ESSID and operate on the same channel
>>    
>>
>and have the same security settings. In fact, those access points are
>mesh access points - both are connected to a FreeRADIUS server.
>  
>
>>Authentication (Open, WPA-PSK, WPA-802.1X-TLS/PEAP/TTLS) works fine in
>>    
>>
>this setup to each access point.
>  
>
>>But, when I try to roam from one access point to another,
>>    
>>
>wpa_supplicant does not initiate a reassociation request to the new
>access point. Instead, it disassociates the old access point, then it
>performs the scanning and then finally goes through a full new
>authentication with the new access point.
>
>My experience says that scan time is not the real bottlenck, delay is
>introduced by loss of conectivity _before_ triggering a new scan, then
>from
>RADIUS authentication (multi-hop packets, worse in a mesh environment),
>and finally some delays that I couldn't really explain after
>authentication and before first EAPOL packet. Jouni said a few time ago
>that a bug was cleaned that caused hostapd waste some time after
>authentication.
>Anyway if you use WPA/WPA2 you must renegotiate the PMK key (whatever
>authentication method you use) and renegotiate the PTK/GTK.
>
>  
>
>>This causes the handoff to take about 1.5 to 3 seconds. This is not
>>    
>>
>acceptable and is not intended by the developers. A single channel
>handoff should take about 10 to 300 ms (depending on authentication).
>  
>
>
>there is an old thread about handoff times that you might read in the
>archives. 
>
>a couple questions: how do you trigger handoff procedure from one AP to
>another? and what does mesh access points means? how do they
>authenticate
>each other ?
>
>ciao,
>leonardo.
>
>  
>