[d80211] connecting to B-mode AP

[d80211] connecting to B-mode AP

[mabbas]

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.

RE: [d80211] connecting to B-mode AP

[Simon Barber]

Why is it necessary to set phymode to B? - a G client can connect
perfectly well to a B AP.

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

Re: [d80211] connecting to B-mode AP

[mabbas]

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
>   

RE: [d80211] connecting to B-mode AP

[Simon Barber]

But it's not the AP connection type that determines what rates are
available - it's the available rate set - this is independent of whether
the card is B or G. A G AP may only advertise B rates, even though it's
a G AP. I still don't see any need to change the phytype.

Simon


-----Original Message-----
From: mabbas [mailto:mabbas@linux.intel.com] 
Sent: Friday, September 15, 2006 10:19 AM
To: Simon Barber
Cc: netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP

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
>   

Re: [d80211] connecting to B-mode AP

[mabbas]

I see your point here, although some one will file some bugs against the 
driver about showing G while associating with B-mode AP. By the way how 
can you figure if the AP is B/G other than the rates?

Simon Barber wrote:
> But it's not the AP connection type that determines what rates are
> available - it's the available rate set - this is independent of whether
> the card is B or G. A G AP may only advertise B rates, even though it's
> a G AP. I still don't see any need to change the phytype.
>
> Simon
>
>
> -----Original Message-----
> From: mabbas [mailto:mabbas@linux.intel.com] 
> Sent: Friday, September 15, 2006 10:19 AM
> To: Simon Barber
> Cc: netdev@vger.kernel.org
> Subject: Re: [d80211] connecting to B-mode AP
>
> 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
>>   
>>     
> -
> 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
>   

Re: [d80211] connecting to B-mode AP

[Michael Wu]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

On Friday 15 September 2006 19:50, mabbas wrote:
> I see your point here, although some one will file some bugs against the
> driver about showing G while associating with B-mode AP. By the way how
> can you figure if the AP is B/G other than the rates?
>
IIRC, only 802.11g APs will send the extended rate information element, though 
I don't know if forcing 802.11b on the AP will cause it to stop sending that. 
(but it might still be okay if it doesn't - it's still a 802.11g AP, with the 
faster speeds turned off..)

-Michael Wu

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [d80211] connecting to B-mode AP

[Michael Buesch]

On Saturday 16 September 2006 01:50, mabbas wrote:
> I see your point here, although some one will file some bugs against the 
> driver about showing G while associating with B-mode AP. By the way how 
> can you figure if the AP is B/G other than the rates?

I don't think this will happen.
This never happened with bcm43xx, for example. The PHY description
of the card is something _completely_ different than the AP's PHY.
People know that G is backwards compatible to B. And people who don't
even know that, don't care anyway. ;)

-- 
Greetings Michael.

RE: [d80211] connecting to B-mode AP

[Simon Barber]

The extended rates element is only needed if there are more than 8 rates
to report - which is normal for G operation, but not necessary. It only
exists because a particularly popular old 11b MAC codebase crashed when
the normal rate element had more than 8 elements, and this hurt
interoperability with early G AP implementations - so the spec was
changed.

Simon

-----Original Message-----
From: Michael Wu [mailto:flamingice@sourmilk.net] 
Sent: Saturday, September 16, 2006 10:05 AM
To: mabbas
Cc: Simon Barber; netdev@vger.kernel.org
Subject: Re: [d80211] connecting to B-mode AP

On Friday 15 September 2006 19:50, mabbas wrote:
> I see your point here, although some one will file some bugs against 
> the driver about showing G while associating with B-mode AP. By the 
> way how can you figure if the AP is B/G other than the rates?
>
IIRC, only 802.11g APs will send the extended rate information element,
though I don't know if forcing 802.11b on the AP will cause it to stop
sending that. 
(but it might still be okay if it doesn't - it's still a 802.11g AP,
with the faster speeds turned off..)

-Michael Wu