MSCHAPv2 Authentication

Sukhdeep Johar sukhdeep
Fri Mar 9 04:21:55 PST 2007

On 3/8/07, Bryan Kadzban <bryan at> wrote:
> >         scan_ssid=1
> >         key_mgmt=WPA-EAP
> >         proto=WPA2 WPA
> >         pairwise=CCMP TKIP
> >         group=CCMP TKIP
> The second issue is that you've specified scan_ssid=1, but you have more
> than one option for proto, pairwise, and group -- I don't know whether
> this works or not.

Yes, this works. In fact the defaults have multiple value for these. For eg.
if you leave proto commented, it will equal proto=WPA WPA2

I would start by removing the scan_ssid line, but if
> that doesn't work, I'd try adding it back in and fixing proto, pairwise,
> and group.  (From your description, it sounds like you will need to use
> WPA, TKIP, and TKIP, respectively.  But it's better to leave those
> parameters unspecified and let the supplicant figure out which values to

Leaving them unspecified will  make the supplicant use the defaults, which
proto = WPA RSN
grou = CCMP TKIP WEP104 WEP40
pairwise = CCMP TKIP

This configuration indicates the set of values that can be used.
The supplicant chooses a set based on the probe-response from the AP and the
valid values ( based on the configuration )

In short, the set of multiple values looks OK.

use based on the beacon information, rather than having the supplicant
> send a specific probe request.)

probe request doesn't contain this information.
It is exchanged in the probe-response and the Assoc-request.


But for the last minute,... Nothing would get done.
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Hostap mailing list