Re: PEAP/MSCHAPv2 problem

2011-04-07 Thread Jürgen Stader
Looking at the output, things become clearer. The conversation ends when the server tries to send the first Access-Challenge packet to the client. It seems like that packet never gets there - and so the client retransmits the same Request over and over again. The server then repeatedly tries to

Re: PEAP/MSCHAPv2 problem

2011-04-05 Thread Jürgen Stader
Am 05.04.2011 07:31, schrieb Stefan Winter: Hi, The solution to the problem is simple. The answer is in front of you. Alan DeKok. Looks like i'm blind...please give me a hint ;-) Dude... supplicants are typically configured to trust only the exact one certificate that is in the

Re: PEAP/MSCHAPv2 problem

2011-04-04 Thread Jürgen Stader
Hi, thanks for your reply. Am 04.04.2011 16:27, schrieb Stefan Winter: Hi, PEAP can work with or without client certs. Both run through the tls instance; that is no error. The problem is much rather here: Sending Access-Challenge of id 219 to ... port 32769 Waking up in 2.0 seconds.

Re: PEAP/MSCHAPv2 problem

2011-04-04 Thread Jürgen Stader
Am 04.04.2011 18:02, schrieb Alan DeKok: Jürgen Stader wrote: When you cloned your RADIUS server, did you give the clone a different certificate afterwards? Since you didn't answer that question directly, it looks like a yes. You' re right, but you can read this out of the lines. The two