<div dir="ltr"><div><div><div>Hi all,<br><br></div>My fault! It is all part of the algorithm. In fact, I was comparing EAP-TTLS/EAP-MSCHAPv2 and PEAP/EAP-MSCHAPv2 when I saw that PEAP has more packets transmitted. Thus, I thought it is a bug, because in all articles it is explained that both authentication protocols are quite similar. Anyway.<br>
<br></div>Cheers,<br></div>Nicko<br><div><div><br><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 3 September 2013 11:20, Nickolay Belchugov <span dir="ltr"><<a href="mailto:belchugov@gmail.com" target="_blank">belchugov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi all,<br><br></div>I am comparing several EAP authentication protocols and I found out when authenticating with EAP-PEAP/EAP-MSCHAPv2 some extra frames were transmitted during the second phase of authentication(When supplicant is authenticated). In fact extra 4 frames were transmitted which is equivalent to an EAP-MSCHAPv2 process. Thus, I suppose the second phase is repeated. But, in the end, there is successful authentication, of course.<br>
<br></div>Here's my network configuration:<br><br></div>Supplicant[wpa_supplicant 1.0/2.0]<---emulated 802.11a network-->Authenticator[hostapd]<---linux bridge-->Authentication Server[freeradius 2.1.12]<br clear="all">
<div><div><div><div><div><div><div><div><div><div><div><div><br></div><div>So have you ever noticed this issue?<br></div><div><br></div><div>Cheers,<br>Nicko<br>
</div></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Поздрави/Regards/Cordialement,<br><div>Nickolay Belchugov</div>
</div>