All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Jon Smirl" <jonsmirl@gmail.com>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"Michael Wu" <flamingice@sourmilk.net>,
	linux-wireless@vger.kernel.org
Subject: Re: Multiple interfaces in mac80211
Date: Sat, 7 Jul 2007 11:46:47 +0200	[thread overview]
Message-ID: <200707071146.48148.IvDoorn@gmail.com> (raw)
In-Reply-To: <1ba2fa240707061533u7db0eda4i2d76576690b33dec@mail.gmail.com>

Hi,

> > > The channel field appears to be uninitialized for beacon frames. When
> > > I booted this time it is displaying channel 9 and I am on channel 10.
> > >
> > > Other frames show channel 10 as expected.
> >
> > Which is quite weird since the beacon frames use the same rx_status structure
> > as the regular frames. No distinction is made within rt2x00 between rx frames...
> >
> > Ivo
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> I'm not sure if this is relevant but:
> It is normal to hear beacons for adjacent channel on 2.4 spectrum as
> channel overlaps. One must read DS information element from the beacon
> to determine on which channel the beacon was really sent.

Well that wouldn't explain why the bug that Jon experiences occurs since that
would mean that beacons from from example coming from channel 9 are reported
to come from channel 10.

But if it should be read from the beacon itself, then it would be the work for mac80211
to do that. Since the drivers will have to do as little as possible with the frame contents.

Ivo


  reply	other threads:[~2007-07-07  9:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  0:23 Multiple interfaces in mac80211 Jon Smirl
2007-07-05  6:05 ` Michael Wu
2007-07-05 12:30   ` Tomas Winkler
2007-07-05 12:34     ` Johannes Berg
2007-07-05 13:57       ` John W. Linville
2007-07-06 10:44         ` Johannes Berg
2007-07-05 13:32     ` Jon Smirl
2007-07-06  4:54       ` Michael Wu
2007-07-06 12:33         ` Jon Smirl
2007-07-06 12:44           ` Johannes Berg
2007-07-06 12:55             ` Jon Smirl
2007-07-06 12:58               ` Johannes Berg
2007-07-06 13:00                 ` Jon Smirl
2007-07-06 13:14                   ` Johannes Berg
2007-07-06 13:22                     ` Jon Smirl
2007-07-06 13:36                       ` Johannes Berg
2007-07-06 18:00                   ` Ivo van Doorn
2007-07-06 18:37                     ` Jon Smirl
2007-07-06 21:16                       ` Ivo van Doorn
2007-07-06 22:33                         ` Tomas Winkler
2007-07-07  9:46                           ` Ivo van Doorn [this message]
2007-07-07 10:01                             ` Johannes Berg

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=200707071146.48148.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=flamingice@sourmilk.net \
    --cc=johannes@sipsolutions.net \
    --cc=jonsmirl@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.