From: Johannes Stezenbach <js@sig21.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Lee <lee-in-berlin@web.de>,
Gertjan van Wingerde <gwingerde@gmail.com>,
linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36, rt73usb)
Date: Tue, 2 Nov 2010 15:46:25 +0100 [thread overview]
Message-ID: <20101102144625.GA32002@sig21.net> (raw)
In-Reply-To: <20101102125007.GA30000@sig21.net>
On Tue, Nov 02, 2010 at 01:50:07PM +0100, Johannes Stezenbach wrote:
>
> Sorry for slow response time. I can confirm that changing
> rt2x00lib_config_intf(rt2x00dev, intf, vif->type,
> intf->mac, intf->bssid);
> to
> rt2x00lib_config_intf(rt2x00dev, intf, vif->type,
> intf->mac, NULL);
> in rt2x00mac_add_interface() fixes rt73usb AP mode for me, too.
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.
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.
Johannes
next prev parent reply other threads:[~2010-11-02 14:46 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 [this message]
2010-11-02 14:58 ` Ivo Van Doorn
2010-11-02 15:05 ` Helmut Schaa
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=20101102144625.GA32002@sig21.net \
--to=js@sig21.net \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=ivdoorn@gmail.com \
--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).