"matt morris" <[EMAIL PROTECTED]> wrote: > (2) Redhat 7.2 with Freeradius 0.9.3, with its own WAN ip; in the user file: > Framed-IP-Address =192.168.0.105, Framed-IP-Netmask = 255.255.255.0, > Framed-MTU = 1380
See the FAQ for reasons why you don't want to use Framed-IP-Netmask. > (Actually a question: Does the user's framed-MTU have to match that of the > AP's?) If not, you'll get fragmentation. > (3) WinXP Supplicant, set with static ip 192.168.0.105 and netmask > 255.255.255.0, Default gateway and DNS to router's internal ip. Huh? You're trying to use RADIUS to set an IP when the supplicant already has a static IP? You do realize that your configuration is inconsistent, don't you? > Both freeradius' and the AP's log shows the authenication was successful, > but the supplicant was not supplied with an ip (just 0.0.0.0). I've tried > getting rid of router from the setup (un-setting the Ap's default gateway > and DNS while setting the supplicant's to the internal ip of the AP), but > still no luck.... Try configuring the supplicant to use a dynamic IP, rather than a static one. That might make a difference. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
