RE: IEEE 802.11 standard compliant 4 address WDS frame


From: Martin Whitlock (martin.whitlock_at_possio.com)
Date: 2002-07-02 15:07:53 UTC



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

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

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.

Any ideas?

/Martin

> -----Original Message-----
> From: Jouni Malinen [mailto:jkmaline_at_cc.hut.fi]
> Sent: den 29 juni 2002 11:39
> To: hostap_at_lists.ssh.com
> Subject: IEEE 802.11 standard compliant 4 address WDS frame
>
>
> I just added support for IEEE 802.11 standard compliant four address WDS
> frame in _other_ than Host AP (Master) mode. Host AP mode is still
> limited to using non-compliant frame format (4th address after the
> payload) when sending WDS frames, but it can now receive standard
> compliant frames.
>
> It looks like some station firmware versions are able to
> send valid WDS frames in pseudo ad-hoc mode, but some versions
> zero addr3 (=DA). I have thus added support for new operations mode for
> WDS. I used IW_MODE_REPEATER since it was free and even though not
> necessarily exactly correct but at least close. This mode can be
> selected with module parameters iw_mode=4 or using 'iwconfig wlan0 mode
> Repeater'. wlan# interface cannot be used for data transmit in Repeater
> mode (you need to make WDS links and use wlan#wds# interfaces). This
> mode does not send beacons and it can be used only with WDS links.
>
> I haven't tested new version with any wlan device that would use
> 802.11 WDS frames (since I do not happen to have one ;-). However, the
> frames looked to be correct when I sniffed frames sent between two hosts
> using Host AP driver. If anyone happens to test this with other devices,
> please let me know about the results.
>
> I see at least two configuration, in which this mode might be useful:
>
> 1) using two WLAN cards in AP and using one in Master mode for
> associating to stations and the other in Repeater mode for WDS
> link to another AP
> 2) bridging to Ethernets, but no need for supporting WLAN stations
> (i.e., no need to use Master mode and beacons)
>
>
> Following commands should be enough to brind up a 802.11 compliant WDS
> link to 00:11:22:33:44:55:
>
> iwconfig wlan0 mode Repeater
> iwpriv wlan0 wds_add 00:11:22:33:44:55
> ifconfig wlan0wds0 up
> # add IP addr if you want to use it also on IP layer
>
>
> --
> Jouni Malinen PGP id EFC895FA
>
>



This archive was generated by hypermail 2.1.4.