[ath9k-devel] Dlink 655 Wireless Mbs

[Luis R. Rodriguez <lrodriguez@atheros.com>]

On Mon, Dec 15, 2008 at 03:09:09PM -0800, Brian wrote:
> 
> 
> Luis,
> >>>> Does this mean if I do a git-pull now I should get this?
> >>>> Or is there some delay?
> >>>>
> >>> You should get it, since the commit is in wireles-testing.
> >>>
> >> I got Already up-to-date so you must have updated a few days ago before
> >> my last go.
> >>
> >> The wireless link seems to be a lot more stable and I have not had a
> >> lockup since.
> >>
> >> However, I still have the problem where my router shows.
> >>
> >> IP Address      Mode    Rate (Mbps)     Signal (%)
> >> 0.0.0.0         802.11g         130     62
> >> Now I thought this might just have been a router issue so I upgraded my
> >> firmware(glutton for punishment:). The update went well I am now at
> >> firmware Version: 1.21
> >> Hardware Version: A3
> >> Product Page: DIR-655
> >> (no-securespot version)
> >>
> >> Again this seems to have improved things a lot.
> >> But I am still left with the problem above.
> >> Given that the wireless says it is set up for 11n
> >>
> >> Wireless Enabled
> >> 802.11 Mode : Mixed 802.11n and 802.11g
> >> Channel Width : 40MHz
> >> Channel : 8
> >> Secondary Channel : 4
> >> WISH : Active
> >> Wi-Fi Protected Setup : Enabled/Configured
> >>
> >> I do not understand why it says 11g
> >
> > It means it will support stations that use either 11n or 11g.
> > If you have a station that supports 11n it will use 11n rates and
> > aggregation. If you use an 11g STA it will stick to 11g for
> > communication only with that STA.
> >
> Sorry did not make myself clear.
> 
> This says the router will accept either
> >> 802.11 Mode : Mixed 802.11n and 802.11g
> 
> This says my 11N pccard is connecting at 11G with a speed of 130?
> >> 0.0.0.0         802.11g         130     62

This is obviously wrong as you cannot possibly usc MCS rates on 802.11g.
The mode of operation must be wrong here as detected by the AP. Contact
your AP support tech guys and bug them if this bothers you a lot, but
this is also minor.

> Prior to rc7 it used to say 11N with a speed of 300.

You mean a rate of 300Mbit/s, anyway you won't always use the 300
Mbit/s, the rate control algorithm will only use it when the conditions
are right for it. If you can determine the actual rate being used for TX
has changed and your environment is consistent and it *used* to use 300
Mbit/s successfully before then perhaps it is a bug and you can use
git bisect to determine the culprit commit.

  Luis