public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Pat Erley <pat-lkml@erley.org>
Cc: matt emery <matt@x204.com>, linux-wireless@vger.kernel.org
Subject: Re: Fwd: Intel 7260
Date: Tue, 26 Nov 2013 12:24:03 -0600	[thread overview]
Message-ID: <1385490243.7838.16.camel@dcbw.foobar.com> (raw)
In-Reply-To: <5294E46C.40102@erley.org>

On Tue, 2013-11-26 at 12:11 -0600, Pat Erley wrote:
> On 11/26/2013 06:28 AM, matt emery wrote:
> > Hi,
> >
> > I hope you can help, I am having problems getting N with new Dual band
> > wireless ac 7260 pci express half mini card, manufacturer code
> > 7260.HMWWB
> >
> > lspci: 03:00.0 Network controller: Intel Corporation Device 08b1 (rev 73)
> >
> > Kernel: 3.12.0-031200-generic
> >
> > firmware: -rw-r--r-- 1 root root 682892 Nov 26 12:10 iwlwifi-7260-7.ucode
> > from here; http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-7260-ucode-22.0.7.0.tgz
> >
> > wlan0     IEEE 802.11abg  ESSID:"XXXX"
> >            Mode:Managed  Frequency:2.412 GHz  Access Point: 06:XX:22:XX:ED:XX
> >            Bit Rate=54 Mb/s   Tx-Power=16 dBm
> >            Retry  long limit:7   RTS thr:off   Fragment thr:off
> 
> >            Encryption key:off
> 
> While I'm not certain about your AP or the 7260 driver, I believe 
> 802.11n technically requires WPA2 encryption.  Try turning that on and 
> testing again.

This is true, but also Matt is using 'iwconfig', which does not support
anything N-related because it uses the older WEXT kernel API.  It simply
won't show 802.11n bitrates, nor will it show encryption details for
WPA.

Matt should be using 'iw' instead, with:

iw dev wlan0 info
iw dev wlan0 link

Dan

> >            Power Management:off
> >            Link Quality=70/70  Signal level=-36 dBm
> >            Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >            Tx excessive retries:1  Invalid misc:27   Missed beacon:0
> >
> >
> > Let me know if you need anything else.
> >
> > Thanks
> >
> > matt
> >
> > Matthew Emery
> > 07988 197 438
> > --
> > 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
> >
> 
> --
> 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



  reply	other threads:[~2013-11-26 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKnB8xgAVp+Ti597RN4_kgPLgXpW1JCr4SQaqfqCzy5A4=o3Ow@mail.gmail.com>
2013-11-26 12:28 ` Fwd: Intel 7260 matt emery
2013-11-26 18:11   ` Pat Erley
2013-11-26 18:24     ` Dan Williams [this message]
2013-11-26 18:35       ` matt emery
2013-11-26 20:46       ` Drasko DRASKOVIC
2013-11-26 21:14         ` matt emery
2013-11-26 21:24           ` Pat Erley
2013-11-26 21:28             ` matt emery
2013-11-26 21:50               ` matt emery
2013-11-28  7:49                 ` Emmanuel Grumbach
2013-11-28  8:39                   ` matt emery

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=1385490243.7838.16.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matt@x204.com \
    --cc=pat-lkml@erley.org \
    /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