From: Jouni Malinen (jkmaline_at_cc.hut.fi)
Date: 2002-04-07 17:15:15 UTC
On Sun, Apr 07, 2002 at 08:47:17PM +0800, penny wrote:
> The system set up list below:
> AP :
> HostAP driver : Prism2-2002-02-13
You might like to try a newer version of the driver since there have been some fixes that may affect also your setup.
> When I installed the HostAP driver , it worked fine and the client could associate to the AP successfully . Since I want the AP to get bridge ability , I installd the bridge utility and something strange apeared.
> Situation 1:
> If the client try to connect to the AP before I set the bridge "up" by ifconfig , it can associate to the AP successfully . Finally I set the bridge up and the client can connect to other host in the network by the bridged up AP.
> Situation 2:
> If I set the bridge up before the client connect , the client can't associate to the AP till I set the bridge down .
This is odd.. There should be no difference on whether wlan0 device is UP or not as far as the association is concerned. Does kernel log show any authentication and association messages in the situation 2?
> Both the two situation , the kernel will log the information again and again as soon as I set the bridge up:
> kernel: wlan0: TXEXC - fid=0x0491 - status=0x0001 ([RetryErr]) tx_control=000e
> kernel: retry_count=0 tx_rate=0 fc=0x0808 (Data::0)
> kernel: addr1=00:80:c8:6d:cf:76 addr2=00:50:8b:d0:7a:8f addr3=00:01:43:e2:14:29
> kernel: Could not find STA for this TX error
> kernel: AP: packet to non-associated STA 00:80:c8:6d:cf:76
Hmm.. If that fc value is correct, this looks like a data frame without FromDS or ToDS.. This should normally be sent and the AP does not get any ACK from 00:80:c8:6d:cf:76 if it does not even exist in your net. This may be caused by allowing "pseudo adhoc style AP to AP" frames. I think I changed this quite a bit when adding WDS support, so I would recommend using a newer version of the driver.
-- Jouni Malinen PGP id EFC895FA