On Monday 08 December 2008, Lars Ericsson wrote: > > On Monday 08 December 2008, Lars Ericsson wrote: > > > > > > > > On Mon, 2008-12-08 at 11:50 +0100, Lars Ericsson wrote: > > > > > Hi Johannes, > > > > > > > > > > I would like to monitor number of packages properly > > > > transmitted and ACK'ed > > > > > by the AP. > > > > > Is the a single point where this can be done ? > > > > > > > > Not really, some drivers don't even give you that information, > > > > unfortunately. > > > > > > > > johannes > > > > > > > > > > OK, thanks. > > > I just discovered that Ralink rt61 does filter all ACK frames. > > > /Lars > > > > Did you look during monitor mode? > > When monitor mode is not enabled, the RX filter can be quite strict. > > > > Ivo > > > > Hi Ivo, > > No, I did not used monitor mode. I do not know how-to do it. iwconfig wlan0 mode monitor > I have a problem when the STA picks up AP BEACONS (last_rx updated), > but the AP, due to other AP/STA communication, have problems picking up the > STA traffic. > > One idea was to monitor that I receive ACK frames, i.e. someone receives me. > But the driver filter all ACK frames. Right, because mac80211 doesn't send the control filter to the driver by default, it does when using monitor mode. (Not sure if it also does this when having a secondary virtual interface running in monitor mode, but for full-monitor mode it does). After that all Ralink hardware send the ACK packets to the driver which sends them to mac80211. > Is there any other event generated from the driver to the mac layer that > can be used indicate bad communication? > > For instance large number of retries or low transmition speed. The retry count is send to mac80211 after the frame was send to the hardware (or if the hardware has given up on the transmission). The used retry rate is not reported. You could also check the 'iwconfig' statistic 'Link Quality' that is calculated by the driver and is based on the signal strength of the beacon from the AP, the TX success count and the RX success count. > PS: > You remember the problem we discussed with the PID that did not work, > until I not forced HW antenna diversity? Yes. It contained the recommendation was that you should force a feature on a device when you don't know if the hardware is capable of that. (Especially when the hardware explictely indicates that it shouldn't be used). ;) > I have been monitoring that site for a while and the 2.6.26 driver works > well. > The WLAN is very interesting. It is a http://www.merunetworks.com WLAN where > the STA associates with a virtual AP. The physical AP (radio) varies from > time to > time depending on the STA location. The STA never noticed when the AP > is changed since all AP's uses the same channel and the BSSID is always the > same. And how does this relate to the antenna setting? Ivo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
