WDS and TX rates, signal measurements

Sergio M. Ammirata ammirata at econointl.com
Sun Jun 8 22:36:45 EDT 2003


> > 2) WDS link autorate negotiation does not work with hostapd (it
stays
> > stuck at 2Mbit) but it does in kernel mode. When I look at the stats
of
> > the neighbor in /proc/.. I see that that the supported_rates are
blank
> > when you use hostapd and they are filled in correctly in kernel
mode.
> 
> Which method do you use to add WDS links? Kernel driver is not
> processing beacon frames when hostapd is used, so it cannot
> automatically get the supported rates list. However, when the station
> entry for WDS peer is added with iwpriv wds_add or based on incoming
WDS
> frame, supported rates are set to 1, 2, 5.5, and 11 Mbps. I did not
see
> them blank in any of my tests with hostapd running.
> 
> Anyway, I think I will change the driver to process beacon frames even
> when hostapd is running

I think this could be a consequence of the order in which I do things. I
create the wds links first using "iwpriv wlan0 wds_add xx:xx...." and
later on I start hostapd.

Sergio




More information about the HostAP mailing list