I finally figured out the problem moments ago. The Dlink access point has a 4X mode option enabled by default, and because of that it causes some fragmentation problems - the AP never interpreted the Access-Challenge and Access-Accept packets correctly. Now that I disabled that mode, the supplicant can finally get the framed ip and gain access to the internet. Thank you.
From: "Alan DeKok" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: IP setting for supplicant Date: Thu, 08 Jan 2004 10:56:56 -0500
"matt morris" <[EMAIL PROTECTED]> wrote: > So should I enable DHCP for the AP?
That's a local configuration issue. It's up to you.
> Also, another thing, when I set the supplicant's ip settings to auto, the AP
> cannot be reached (no reply from ping, can't access the AP). I can only
> access and ping the AP when I set a static ip for the supplicant.
I'll bet money that you're trying to ping the AP *before* the user was authenticated. The whole point of the RADIUS conversation is to have the server tell the AP you're allowed in, and what IP to give you.
If the AP doesn't know who you are, why should it allow you to use the network?
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
