linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis New <dennisn@dennisn.mooo.com>
To: linux-wireless@vger.kernel.org
Subject: Re: wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute
Date: Sun, 26 Mar 2017 14:51:04 -0400	[thread overview]
Message-ID: <20170326145104.ca03fee3e90230e7fb5e02d3@dennisn.mooo.com> (raw)
In-Reply-To: <98e61d2c-97af-0a67-a4bb-abac16765006@broadcom.com>

On Sun, 26 Mar 2017 20:47:41 +0200, Arend Van Spriel wrote:
> 
> 
> On 26-3-2017 19:43, Dennis New wrote:
> > On Sun, 26 Mar 2017 11:00:12 -0500, Larry Finger wrote:
> >> ...  provide information regarding what specific card you have. The
> >> appropriate stanza from "lspci -nn" has that information.
> >>
> >> I do not normally run a b43 wireless NIC, but I did pull out an
> >> ancient laptop that uses the PCMCIA version of a BCM4318 with PCI
> >> ID of 14e4:4318. Running kernel 4.10.0, I do see periodic drops. My
> >> period is 120 sec and the drop is a reason 7, not reason 3 as you
> >> see. Another difference is that I see the drops with kernel 4.8.0
> >> as well. With the earlier kernel, the drop period is closer to 60
> >> sec, but it is not as regular.
> > 
> > Huh. I also have that BCM4318 card, but not PCMCIA.
> > 
> > 06:02.0 Network controller [0280]: Broadcom Corporation BCM4318
> > [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev
> > 02) Subsystem: AMBIT Microsystem Corp. Aspire 3022WLMi, 5024WLMi,
> > 5020 [1468:0311] Flags: bus master, fast devsel, latency 64, IRQ 9
> > Memory at c0304000 (32-bit, non-prefetchable) [size=8K] Kernel
> > driver in use: b43-pci-bridge
> > 
> > These past few days I seem to have had some "success" by simply
> > putting a 60 second sleep in my bootup scripts before bringing up
> > my wlan0 interface. (Ie. I haven't been getting any deauths after
> > doing this.)
> 
> Interesting. I assume you are using wpa_supplicant so can you make a
> supplicant log of that with and without the 60 second sleep.

The same thing happens even without wpa_supplicant. Simply doing "iw
wlan0 connect BlablaAP" .... it will still mysteriously deauthenticate
after a minute (usually).

  reply	other threads:[~2017-03-26 18:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25  1:32 wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute Dennis New
2017-03-26 16:00 ` Larry Finger
2017-03-26 17:43   ` Dennis New
2017-03-26 18:47     ` Arend Van Spriel
2017-03-26 18:51       ` Dennis New [this message]
2017-03-26 19:00         ` Arend Van Spriel
2017-03-29  7:34 ` Johannes Berg
2017-03-29  7:43   ` Arend Van Spriel
2017-03-29  7:46     ` Johannes Berg
2017-03-29  8:20       ` Arend Van Spriel
2017-03-29  8:50         ` Johannes Berg
2017-03-29 10:28   ` Dennis New
2017-03-29 11:49     ` Johannes Berg
2017-03-29 18:58       ` Arend Van Spriel
2017-03-30  8:06         ` Johannes Berg
2017-03-29 19:36       ` Dennis New
2017-03-29 20:15         ` Larry Finger
2017-03-29 20:21           ` Arend Van Spriel

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=20170326145104.ca03fee3e90230e7fb5e02d3@dennisn.mooo.com \
    --to=dennisn@dennisn.mooo.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).