|
Home > Archive > Radius Server > March 2004 > PEAP phase 2 hangs up
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
PEAP phase 2 hangs up
|
|
| Mike Chang 2004-02-10, 1:35 pm |
| Many thanks to Ashwin. I can finally get the RADIUS server
work with Odyssey clinet.
However, the Wireless Configuration hangs up after receiving
MS-CHAPV2/Success packet from RADIUS server. In other
words, the Wireless Configuration transmits nothing.
I think the packet format is correct since it follows the spec and
works well with Odyssey client.
Did I miss anything?
| |
| Mike Chang 2004-02-11, 1:35 pm |
| I've found the reason: the windows 802.1x supplicant (wireless
configuration)
requires the same MS-CHAPV2-ID in request/challenge and request/success or
request/failure. Is there any document specifies such behavior? The EAP-MS-
CHAPV2 internet draft doesn't specify such behavior.
Is there any constraint on the identifier field of Result-TLV?
"Mike Chang" <ycchang@zyxel.com.tw> 在郵件
news:uePhbQE8DHA.3804@tk2msftngp13.phx.gbl 中撰寫...
> Many thanks to Ashwin. I can finally get the RADIUS server
> work with Odyssey clinet.
>
> However, the Wireless Configuration hangs up after receiving
> MS-CHAPV2/Success packet from RADIUS server. In other
> words, the Wireless Configuration transmits nothing.
>
> I think the packet format is correct since it follows the spec and
> works well with Odyssey client.
>
> Did I miss anything?
>
>
| |
| Hakan Berk [MSFT] 2004-03-31, 12:41 pm |
| I think this is per EAP RFC. The success/failure packet for an EAP should
have the same id for the last packet trasnmitted.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Chang" <ycchang@zyxel.com.tw> wrote in message
news:us389CR8DHA.1428@TK2MSFTNGP12.phx.gbl...
> I've found the reason: the windows 802.1x supplicant (wireless
> configuration)
> requires the same MS-CHAPV2-ID in request/challenge and request/success or
> request/failure. Is there any document specifies such behavior? The
EAP-MS-
> CHAPV2 internet draft doesn't specify such behavior.
>
> Is there any constraint on the identifier field of Result-TLV?
>
> "Mike Chang" <ycchang@zyxel.com.tw> 在郵件
> news:uePhbQE8DHA.3804@tk2msftngp13.phx.gbl 中撰寫...
>
>
|
|
|
|
|