From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: Ivo Van Doorn <ivdoorn@gmail.com>, 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: Wed, 3 Nov 2010 16:21:48 +0100 [thread overview]
Message-ID: <201011031621.48923.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <20101103145950.GA5798@sig21.net>
Am Mittwoch 03 November 2010 schrieb Johannes Stezenbach:
> On Wed, Nov 03, 2010 at 03:51:52PM +0100, Ivo Van Doorn wrote:
> > On Wed, Nov 3, 2010 at 3:14 PM, Johannes Stezenbach <js@sig21.net> wrote:
> > > On Tue, Nov 02, 2010 at 01:50:07PM +0100, Johannes Stezenbach wrote:
> > >>
> > >> While reading through the code I noticed the following in rt2800_config_intf():
> > >>
> > >> rt2x00_set_field32(®, MAC_BSSID_DW1_BSS_ID_MASK, 3);
> > >>
> > >> However, in Ralink source from http://www.ralinktech.com/support.php?s=2
> > >> in DPO_RT3370_LinuxSTA_V2.4.0.1_20100831/include/chip/rtmp_mac.h it says:
> > >> USHORT BssIdMask:2; // 0: one BSSID, 10: 4 BSSID, 01: 2 BSSID , 11: 8BSSID
> > >>
> > >> This is different from rt73usb where 3 means "one BSSID".
> > >
> > > Any comments on this?
> >
> > Well RT3370 isn't rt73 ;)
> > Instead (altough I don't know this exact chipset), I suspect it to be
> > of the rt2800 family.
>
> OK, seems hat I wrote was confusing.
>
> rt73usb sets the field to 3 (meaning "one BSSID").
>
> But rt2800usb also sets it to 3, but it should be 0 (in rt2800_config_intf).
I would be fine with setting this to 0 but only in STA and IBSS mode. At
least in AP mode we want to keep the max value to be able to use multiple
AP mode interfaces.
Helmut
next prev parent reply other threads:[~2010-11-03 15:22 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
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 [this message]
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=201011031621.48923.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).