Hi, Am Dienstag 02 November 2010 schrieb Ivo Van Doorn: > > After studying the code some more, I'm confused by the > > comment for this code in rt2x00mac_add_interface(): > > > > * The BSSID address must only be configured in AP mode, > > * however we should not send an empty BSSID address for > > * STA interfaces at this time, since this can cause > > * invalid behavior in the device. Configuring the BSSID register in AP mode was added because rt2800 devices need it in AP mode for hw crypto. As I stated earlier it seems that older devices (<rt2800?) need the exact opposite. In order to fix that issue we could work around this problem by moving the BSSID register setting (in AP mode) into rt2800 and revert rt2x00lib back to not setting it at all (only upon association). > > On the contrary I think the BSSID needs to be configured for STA mode > > since it acts as a receive filter for broadcase/multicast frames. > > The 802.11 standard says in 7.2.2 Data frames: > > > > A STA uses the contents of the Address 1 field to perform address > > matching for receive decisions. In cases where the Address 1 field > > contains a group address, the BSSID also is validated to ensure that > > the broadcast or multicast originated from a STA in the BSS of which > > the receiving STA is a member. > > > > The ralinktech.com drivers seem to set the BSSID for STA mode and IBSS mode. > > True, but the comment in rt2x00 says: > 'empty BSSID address' and 'at this time' > > The legacy drivers from Ralink configure the BSSID, same as rt2x00 driver do, > when we start the association procedure. This complies with the 802.11 standard > for filtering the data frames. Yep, Ivo is correct. Helmut -- 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
