Not going past "Sending Access-Challenge"

[Adam Tauno Williams]

It works!  I set "nastype = other" in the clients.conf file as per an 
example I
saw from someone using the same WAP, and it started working after restarting
Radius.  I don't recall making any other changes, but something had led me to
believe that "other" was the default nastype if not specified.

>>> I'm trying to setup RADIUS/WPA authentication using PEAP as
>>> described in -
>>> http://www.ibiblio.org/pub/Linux/docs/HOWTO/8021X-HOWTO - but I
>>> never seem to get past the "Sending Access-Challenge" after I enter
>>> my username and password on the client.  User is simply an entry in
>>> the users file with a clear text password.  I've gone over the
>>> config several times, but nothing jumps out at me as an error
>>> message.
> Alan DeKok wrote:
>>  The problem most likely is that the AP isn't seeing the response, or
>> it isn't liking the response.  Check the IP addresses that the packet
>> use, via "tcpdump".
> Okay, I've etherealled the connection and I see an "Access-Request" 
> from the WAP
> to the RADIUS server, then an "Access-Challenge" from the RADIUS serve to the
> WAP,  and nothing else.  What should the WAP's response to an
> "Access-Challenge" response be?
> The WAP is 192.168.1.42 and the RADIUS server is 192.168.1.47