<!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.2719.2200" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=006311415-15112002><FONT face=Arial color=#0000ff
size=2>Correction... It appears that it was a little too early to blaim the new
Intersil f/w. I have just proven myself wrong by getting the same kind of
trouble even with older versions of STA f/w. But the problem definately
disappears when other_ap_policy is set to 0. </FONT></SPAN></DIV>
<DIV><SPAN class=006311415-15112002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=006311415-15112002><FONT face=Arial color=#0000ff size=2>Is the
solution to the problem to kick the macaddress of an AP that tries to associate?
Or would this have any bad side effects?</FONT></SPAN></DIV>
<DIV><SPAN class=006311415-15112002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=006311415-15112002><FONT face=Arial color=#0000ff
size=2>/Martin</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> hostap-admin@shmoo.com
[mailto:hostap-admin@shmoo.com]<B>On Behalf Of </B>Martin
Whitlock<BR><B>Sent:</B> den 15 november 2002 12:29<BR><B>To:</B>
Hostap@Shmoo. Com<BR><B>Subject:</B> Possible bug in STA f/w
1.5.6<BR><BR></FONT></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>I beleive I've
found a bug in STA f/w 1.5.6 while trying to solve the
HostAP(Client)-to-HostAP(AP) problem. I don't think that this possible f/w bug
is the only reason for my troubles, but it could definately be one
reason.</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>I have a HostAP
(#1, f/w 1.3.6) in Master mode (with other_ap_policy=2)</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>I start another
device with HostAP (#2, f/w 1.5.6), default settting Master
mode.</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>#1 sees #2 and get
thats it is a AP</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>I change mode on
#2 into Managed mode</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>#1 _still_ thinks
that #2 is an AP</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>#2 tries to
associate, but #1 prints debug message (AP trying to
associate?)</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>iwconfig on #2
shows a good signal quality, but macaddress
44:44:44:44:44:44</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>When I kick #2's
macaddress it associates just fine.</FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>With f/w 1.3.6 in
#2 this problem does not occur, but I havn't tested any versions in between of
1.3.6 and 1.5.6. Also if I switch other_ap_policy to 0 in #1, the problem
disappears. </FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial size=2>QUESTION: Would it
be a bad idea to let HostAP driver do a kick_mac on that address each time it
thinks an AP is trying to associate? </FONT></SPAN></DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=626505610-15112002><FONT face=Arial
size=2>/Martin</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>