Re: IEEE 802.11 standard compliant 4 address WDS frame

From: Jouni Malinen (
Date: 2002-07-08 16:10:30 UTC

On Tue, Jul 02, 2002 at 05:07:53PM +0200, Martin Whitlock wrote:

> The Intel PRO 2011 AP has a mode that Intel call WLAP to set up a wireless
> bridge. Does anyone know if this is standard IEEE 802.11 wds? I tried to set
> up a hostap in repeater mode towards my Intel, but all I got was this
> repeated message (when trying to do a DHCP request):
> wlan0: TXEXC - fid=0x0252 - status=0x0001 ([RetryErr]) tx_control=000c
> retry_count=0 tx_rate=0 fc=0x4b08 (Data::0)
> addr1=00:02:b3:04:e1:7a addr2=00:60:b3:6f:8b:56 addr3=ff:ff:ff:ff:ff:ff

I'm not familiar with "WLAP", but at least the Intel AP did not ACK the WDS frame sent by the Host AP driver here.

> where addr1 belongs to my Intel and addr2 is the prism card in hostap
> repeater mode. The funny thing is that I have the option to set "WLAP Manual
> BSS ID" on the Intel config page, and if I set it to "00:00:00:00:00:00"
> (default option) I sometimes get this message:
> wlan0: TXEXC - fid=0x0320 - status=0x0001 ([RetryErr]) tx_control=000c
> retry_count=0 tx_rate=0 fc=0x4a08 (Data::0)
> addr1=00:00:00:00:00:00 addr2=00:60:b3:6f:8b:56 addr3=00:60:b3:6f:8b:56

This looks like a not-ACKed data from with only FromDS bit (i.e., only 3 addrs). You did not describe the Host AP driver configuration during this message, but if it was in Master mode, it looks like the Intel AP might have associated with it.

> which implies that there is some form of communication between my units,
> right? Any other "WLAP Manual BSS ID" makes it impossible for clients to
> associate to the Intel AP (like 00:60:b3:6f:8b:56, for instance) but doesn't
> make any other difference.

There is no BSSID in WDS frame, so I would guess that this is not a four address frame, but just an "extended" three address frame that uses a selected BSSID between a set of Intel APs for a wireless link.

Jouni Malinen                                            PGP id EFC895FA

This archive was generated by hypermail 2.1.4.