<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Hi,<BR><BR>I
encontered a very strange problem with following setting:<BR><BR> Hostap
driver 0.2.4, Linux2.4, and WindowsXP as a client. The problem comes when
I<BR> turn on i802.1x authentication by using freeradius. The
authentication method<BR> is PEAP and this problem seems have nothing to do
with authentication method directly.<BR><BR> In fact everything works
pretty well. The i802.1x authentication works fine,<BR>but several seconds after
the i802.1x authentication finishs, XP always sends<BR>out a "deauthentication"
frame with reason code 3:(Station has left the basic<BR>service area..)<BR>It
seems no long detect signal! This last part of the log
is:<BR>-------------------------------------------------------------------------------------<BR>...........<BR>RADIUS
packet matching with station 00:09:5b:69:64:e7<BR>MS-MPPE-Send-Key (len=32): 83
96 c8 4e b9 8e 99 d5 54 7b e4 21 83 57 3e 34 ed 43<BR>f4 15<BR>e7 c4 a1 2e 80 69
4c c5 0b 47 2f d3<BR>MS-MPPE-Recv-Key (len=32): c4 45 f3 fc ae 6a 41 c0 50 e5 98
0b 7e f2 ef eb 28 00<BR>65 07<BR>c6 48 31 83 b1 5a c0 ac 46 7a 14 6e<BR>IEEE
802.1X: 00:09:5b:69:64:e7 BE_AUTH entering state SUCCESS<BR>IEEE 802.1X: Sending
EAP Packet to 00:09:5b:69:64:e7 (identifier 9)<BR>IEEE 802.1X: 00:09:5b:69:64:e7
REAUTH_TIMER entering state INITIALIZE<BR>IEEE 802.1X: 00:09:5b:69:64:e7
AUTH_PAE entering state AUTHENTICATED<BR>wlan0: STA 00:09:5b:69:64:e7 IEEE
802.1X: authenticated<BR>IEEE 802.1X: 00:09:5b:69:64:e7 BE_AUTH entering state
IDLE<BR>Received 40 bytes management frame<BR>RX frame - hexdump(len=40): 0a 02
d5 00 00 09 5b 69 64 e7 00 09 5b 2f 96 b2 00<BR>09 5b 2f 96 b2 20 77 aa aa 03 00
00 00 88 8e 01 00 00 04 03 09 00 04<BR>DATA (TX callback) ACK<BR>IEEE 802.1X:
00:09:5b:69:64:e7 TX status - version=1 type=0 length=4 - ack=1<BR>IEEE 802.1X:
00:09:5b:69:64:e7 Port Timers TICK (timers: 29 0 3599 29)<BR>IEEE 802.1X:
00:09:5b:69:64:e7 Port Timers TICK (timers: 28 0 3598 28)<BR>IEEE 802.1X:
00:09:5b:69:64:e7 Port Timers TICK (timers: 27 0 3597 27)<BR>IEEE 802.1X:
00:09:5b:69:64:e7 Port Timers TICK (timers: 26 0 3596 26)<BR>IEEE 802.1X:
00:09:5b:69:64:e7 Port Timers TICK (timers: 25 0 3595 25)</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Received 26
bytes management frame<BR>RX frame - hexdump(len=26): c0 00 11 93 00 09 5b 2f 96
b2 00 09 5b 69 64 e7 cb<BR>3d 55 5d 5e 43 f0 ba 03 00<BR>MGMT<BR>MGMT:
BSSID=cb:3d:55:5d:5e:43 not our address<BR>IEEE 802.1X: 00:09:5b:69:64:e7 Port
Timers TICK (timers: 24 0 3594
24)<BR>---------------------------------------------------------------------------</FONT><FONT
face="Times New Roman" size=3><BR><BR>More interesting thing is that XP doesn't
send this "deauthentication" if I do<BR>following:<BR><BR>(1)Start the "hostapd"
and let XP connect.<BR>(2)For some reason, after the station is associated and
first "Sending EAP<BR>Request-Identity", AP always have to wait long without
response and try second<BR>time. Kill the<BR>"hostapd" when AP is
waiting.<BR>(3)restart "hostapd". The whole process will start again almost same
as first run of<BR>"hostapd" except it seems no waiting mentioned in (2). And
guess what? This XP<BR>"deauthentication" problem disappears!!!<BR><BR>I am so
confused. Don't know if it is an XP problem, or HostAp
problem.</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Hope to get
some help from somebody. Thanks.<BR>Detail log is
attached.<BR><BR>-yuannong</FONT><BR></DIV></FONT></BODY></HTML>