From: mabbas <mabbas@linux.intel.com>
To: Simon Barber <simon@devicescape.com>
Cc: netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP
Date: Fri, 15 Sep 2006 10:19:25 -0700 [thread overview]
Message-ID: <450AE09D.2040901@linux.intel.com> (raw)
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29F01785286@dhost002-46.dex002.intermedia.net>
Simon Barber wrote:
> Why is it necessary to set phymode to B? - a G client can connect
> perfectly well to a B AP.
>
We need this information for rate scaling and we need to send the NIC
different command depends on the AP connection type.
Mohamed
> Simon
>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of mabbas
> Sent: Thursday, September 14, 2006 4:25 PM
> To: netdev@vger.kernel.org
> Subject: [d80211] connecting to B-mode AP
>
> When I connect to b-mode only AP and then run iwconf it shows it as a
> G-mode AP. I guess when we set frequency it look through all the modes
> and set the mode to the first channel it founds. since B and G share the
> same frequencies it will set phymode to G. How can we force it to set
> phymode to the AP we are associating with.
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-09-15 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 23:24 [d80211] connecting to B-mode AP mabbas
2006-09-15 0:20 ` Simon Barber
2006-09-15 17:19 ` mabbas [this message]
2006-09-15 18:46 ` Simon Barber
2006-09-15 23:50 ` mabbas
2006-09-16 0:04 ` Michael Wu
2006-09-17 4:52 ` Simon Barber
2006-09-16 15:34 ` Michael Buesch
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=450AE09D.2040901@linux.intel.com \
--to=mabbas@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.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 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).