All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: "John H." <mistamaila@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: timeout problems with certain APs and b43
Date: Thu, 22 Nov 2007 23:41:02 -0600	[thread overview]
Message-ID: <474667EE.7060100@lwfinger.net> (raw)
In-Reply-To: <5b9417770711222031r28011e75v3a6eb4a7acdf2183@mail.gmail.com>

John H. wrote:
> wrt54gs with latest firmware.
> 
> it seems exclusive to linux:O
> 
> On Nov 21, 2007 4:18 PM, Larry Finger <larry.finger@lwfinger.net> wrote:
>> John H. wrote:
>>>  uname -a
>>> Linux laptop 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 21:41:26 EST 2007 i686
>>> i686 i386 GNU/Linux
>>> fedora 8
>>>
>>> on certain APs, the internet works for a long time then stops, and I
>>> get authentication time outs, why?  It usually works again if I reset
>>> the AP itself, which i should not have to do and don't have to if in
>>> XP....
>>>
>>>
>>> wlan0: switched to long barker preamble (BSSID=00:0f:66:53:3e:24)
>>> wlan0: switched to short barker preamble (BSSID=00:0f:66:53:3e:24)
>>>
>>>
>>>
>>> wlan0: Initial auth_alg=0
>>> wlan0: authenticate with AP 00:0f:66:53:3e:24
>>> wlan0: authenticate with AP 00:0f:66:53:3e:24
>>> wlan0: authenticate with AP 00:0f:66:53:3e:24
>>> wlan0: authentication with AP 00:0f:66:53:3e:24 timed out
>> Do you have the opportunity to capture the wireless traffic with a second computer using Kismet or
>> Wireshark when this condition occurs? Without that info, it would be hard to know what might be
>> wrong. Of course, I don't have the problem with either of my AP's.
>>
>> Could you identify the make/model and firmware revisions of any AP's that show this behavior?

Please do not top post!

The problem is not generic with Linksys AP's. I use a WRT54GL V1.1 and a WRT54G V5. Neither shows
the problem.

We need a dump of the wireless traffic when this condition occurs.

Larry

  reply	other threads:[~2007-11-23  5:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 19:35 timeout problems with certain APs and b43 John H.
2007-11-21 22:18 ` Larry Finger
2007-11-23  4:31   ` John H.
2007-11-23  5:41     ` Larry Finger [this message]
2007-11-23 10:05 ` Johannes Berg
2007-11-23 21:58   ` Rafael J. Wysocki
2007-11-23 21:57     ` Johannes Berg
2007-11-23 22:21       ` Rafael J. Wysocki
2007-11-24  1:56         ` John H.
2007-11-24  8:35         ` Johannes Berg
2007-11-24 11:17           ` Rafael J. Wysocki

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=474667EE.7060100@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=mistamaila@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.