From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"Kan Yan" <kanyan@broadcom.com>
Subject: Re: brcmsmac connection stalls (was Re: )
Date: Wed, 30 May 2012 23:23:09 +0200 [thread overview]
Message-ID: <4FC68FBD.6080908@broadcom.com> (raw)
In-Reply-To: <20120530210538.GG30697@thinkpad-t410>
On 05/30/2012 11:05 PM, Seth Forshee wrote:
> On Wed, May 30, 2012 at 10:49:05PM +0200, Arend van Spriel wrote:
>> If you can provide me as much detail as possible on the AP settings I
>> can dive into it over here.
>
> The AP is a Linksys E3000 running dd-wrt. Here's what iw says about it.
> Let me know if there's any more information you'd like to have or
> anything else I can do to help.
This will do nicely. Thanks.
Gr. AvS
> TSF: 80992461200 usec (0d, 22:29:52)
> freq: 2412
> beacon interval: 100
> capability: ESS Privacy ShortSlotTime (0x0411)
> signal: -35.00 dBm
> last seen: 10192 ms ago
> Information elements from Probe Response frame:
> SSID: Kailia
> Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
> DS Parameter set: channel 1
> ERP: <no flags>
> RSN: * Version: 1
> * Group cipher: CCMP
> * Pairwise ciphers: CCMP
> * Authentication suites: PSK
> * Capabilities: 16-PTKSA-RC (0x000c)
> Extended supported rates: 6.0 9.0 12.0 48.0
> HT capabilities:
> Capabilities: 0x187e
> HT20/HT40
> SM Power Save disabled
> RX Greenfield
> RX HT20 SGI
> RX HT40 SGI
> No RX STBC
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT RX MCS rate indexes supported: 0-15, 32
> HT TX MCS rate indexes are undefined
> HT operation:
> * primary channel: 1
> * secondary channel offset: above
> * STA channel width: any
> * RIFS: 1
> * HT protection: nonmember
> * non-GF present: 0
> * OBSS non-GF present: 1
> * dual beacon: 0
> * dual CTS protection: 0
> * STBC beacon: 0
> * L-SIG TXOP Prot: 0
> * PCO active: 0
> * PCO phase: 0
> WMM: * Parameter version 1
> * u-APSD
> * BE: CW 15-1023, AIFSN 3
> * BK: CW 15-1023, AIFSN 7
> * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
> * VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec
>
>
prev parent reply other threads:[~2012-05-30 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 20:25 Seth Forshee
2012-05-30 20:47 ` brcmsmac problems in wireless-testing Seth Forshee
2012-05-30 20:51 ` Arend van Spriel
2012-05-30 20:49 ` brcmsmac connection stalls (was Re: ) Arend van Spriel
2012-05-30 21:05 ` Seth Forshee
2012-05-30 21:23 ` Arend van Spriel [this message]
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=4FC68FBD.6080908@broadcom.com \
--to=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kanyan@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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).