From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: Johannes Stezenbach <js@sig21.net>, Lee <lee-in-berlin@web.de>,
Gertjan van Wingerde <gwingerde@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36, rt73usb)
Date: Tue, 2 Nov 2010 16:05:36 +0100 [thread overview]
Message-ID: <201011021605.37137.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <AANLkTikYDHBSVuMEnUsR7WpPPo8rK0+OBm_Rd-H0znHT@mail.gmail.com>
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
next prev parent reply other threads:[~2010-11-02 15:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 23:47 [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36-, rt73usb) Lee
2010-10-23 19:58 ` [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36, rt73usb) Lee
2010-10-25 17:49 ` John W. Linville
2010-10-26 2:04 ` Lee
2010-10-26 5:40 ` Helmut Schaa
2010-10-26 10:19 ` Johannes Stezenbach
2010-10-26 11:03 ` Johannes Stezenbach
2010-10-26 15:40 ` Johannes Stezenbach
2010-10-28 8:16 ` Lee
2010-10-28 8:20 ` Ivo Van Doorn
2010-10-28 8:23 ` Helmut Schaa
2010-10-28 19:06 ` Lee
2010-10-28 19:54 ` Gertjan van Wingerde
2010-10-28 20:36 ` Ivo Van Doorn
2010-10-28 20:40 ` Gertjan van Wingerde
2010-10-28 22:17 ` Helmut Schaa
2010-10-29 21:39 ` Lee
2010-10-30 12:30 ` Helmut Schaa
2010-11-02 12:50 ` Johannes Stezenbach
2010-11-02 14:46 ` Johannes Stezenbach
2010-11-02 14:58 ` Ivo Van Doorn
2010-11-02 15:05 ` Helmut Schaa [this message]
2010-11-02 15:49 ` Johannes Stezenbach
2010-11-03 14:14 ` Johannes Stezenbach
2010-11-03 14:50 ` Ivo Van Doorn
2010-11-03 15:08 ` Johannes Stezenbach
2010-11-03 14:51 ` Ivo Van Doorn
2010-11-03 14:59 ` Johannes Stezenbach
2010-11-03 15:21 ` Helmut Schaa
2010-11-03 14:53 ` Helmut Schaa
2010-10-29 16:17 ` Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011021605.37137.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=js@sig21.net \
--cc=lee-in-berlin@web.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).