Also, I saw the PEAP-WinXP Failure question posted by Mr. Mike Saywell, and tried the NASTLS log method (thx btw) myself. Turns out I have the same "without TLV" issue. So there's no way to get around it if I want to use PEAP-MSCHAPv2 in WinXP, except recoding?
TIA
From: "Alan DeKok" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: PEAP - Unknown RADIUS packet Date: Tue, 13 Jan 2004 13:28:48 -0500
matt morris" <[EMAIL PROTECTED]> wrote:
> Unfortunately, I ran into the ip problem again. If I'm using PEAP, the
> supplicant could not get an ip address (the ip is 169.254.1.34, subnet mask
> 255.255.0.0).
If you're using Framed-Netmask, you're using the wrong attribute. See the FAQ.
> Also, although TLS works, the ip address the supplicant got isn't the framed
> ip address I defined in the users file, instead it's just an ip assigned by
> the DHCP server (AP).
I don't know why you're configuring the RADIUS server to send an IP address for the client to the AP, and then configure the client to request an address via DHCP.
And they're different addresses because the DHCP server doesn't know about the RADIUS request.
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html