mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Dave Young <dyoung@redhat.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxwifi@intel.com
Subject: Re: Intel Wireless 8265/8275 (rev 78) issue
Date: Thu, 30 Aug 2018 08:55:24 +0300	[thread overview]
Message-ID: <fa12a23813cf096e217eac27835ed416ca0d1632.camel@coelho.fi> (raw)
In-Reply-To: <20180830050632.GB2307@dhcp-128-65.nay.redhat.com>

On Thu, 2018-08-30 at 13:06 +0800, Dave Young wrote:
> On 08/30/18 at 07:15am, Luca Coelho wrote:
> > On Wed, 2018-08-29 at 14:54 +0800, Dave Young wrote:
> > > [   74.123114] wlp61s0: authenticate with 00:1f:c6:82:0a:57
> > > [   74.126099] wlp61s0: send auth to 00:1f:c6:82:0a:57 (try 1/3)
> > > [   74.139740] wlp61s0: authenticated
> > > [   74.140142] iwlwifi 0000:3d:00.0 wlp61s0: disabling HE/HT/VHT due to WEP/TKIP use
> > > [   74.140146] iwlwifi 0000:3d:00.0 wlp61s0: disabling HT as WMM/QoS is not supported by the AP
> > > [   74.140149] iwlwifi 0000:3d:00.0 wlp61s0: disabling VHT as WMM/QoS is not supported by the AP
> > 
> > Your AP seems to be configured to use WEP or TKIP, which is not allowed
> > by IEEE802.11n, so we disable all the higher rates, as you can see
> > here.  It should still work, but you will only get very basic rates
> > (i.e. slow).
> 
> Luka, thanks for the suggestion,  moved AP to use WPA2-personal + AES.
> seems I got only two features disabled this time:
> [   20.949347] iwlwifi 0000:3d:00.0 wlp61s0: disabling HT as WMM/QoS is not supported by the AP
> [   20.949351] iwlwifi 0000:3d:00.0 wlp61s0: disabling VHT as WMM/QoS is not supported by the AP
> [   20.949622] wlp61s0: associate with 00:1f:c6:82:0a:57 (try 1/3)

There are many interoperability problems with old 11n APs that either
support a draft version of the specs or simply have bugs in their
implementations of the 11n specs.  When we detect these problems, we
disable 11n rates, so connectivity will be slower, but it will at least
remain connected.  This seems to be the case with your AP. :(


> > > [ 2521.068469] wlp61s0: deauthenticating from 00:1f:c6:82:0a:57 by local choice (Reason: 3=DEAUTH_LEAVING)
> > 
> > Other than that I can't really see what is going on, except that
> > something is deciding to disconnect here...
> > 
> > So, first thing I'd suggest would be to try to reconfigure your AP to
> > use something else than WEP or TKIP, just to see if it improves in any
> > way.
> 
> Will observe if it works or not. BTW, my old laptop Thinkpad T440s works
> well with the same AP.

I hope it improves.  If not, we should debug it further.  It's a good
thing not to use WEP and TKIP anyway, because they're not very secure
anyway.


> > And BTW, is this a regression in recent kernels or has this always
> > happened to you with this laptop/AP combination?
> 
> From my observation it just always happen, but hmm not 100% sure..

Okay, so we don't have enough information on this.  It doesn't matter. 
What is the NIC on your old T440s?

--
Cheers,
Luca.


  reply	other threads:[~2018-08-30  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  6:54 Dave Young
2018-08-29 15:20 ` Kalle Valo
2018-08-30  5:02   ` Dave Young
2018-08-30  4:15 ` Luca Coelho
2018-08-30  5:06   ` Dave Young
2018-08-30  5:55     ` Luca Coelho [this message]
2018-08-30  6:34       ` Dave Young

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=fa12a23813cf096e217eac27835ed416ca0d1632.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=dyoung@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.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

all inboxes | Powered by JetHome®