linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milan Bouchet-Valat <nalimilan@club-internet.fr>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Re: BCM4313 keeps disconnecting with brcmsmac and multiple APs
Date: Tue, 31 Jan 2012 14:36:46 +0100 (CET)	[thread overview]
Message-ID: <32081421.179347.1328017006287.JavaMail.www@wsfrf1118> (raw)
In-Reply-To: <1327660003.21888.14.camel@milan>

Le vendredi 27 janvier 2012 à 12:37 +0100, Arend van Spriel a écrit :
On 01/27/2012 11:26 AM, Milan Bouchet-Valat wrote:
> > Le vendredi 27 janvier 2012 à 11:08 +0100, Arend van Spriel a écrit :
> >> Another thing to consider. I notice that you have a bluetooth device in
> >> there as well. Can you disable that (if possible) and try again.
> > I'll try that, but sadly not before Tuesday as I'm not in the right
> > place ATM.
> 
> Ok. To disable bluetooth you could use the rfkill utility:
> 
> $ rfkill block bluetooth
> Yes, I did that, but it doesn't fix the problem.

>> Does your AP have DFS enabled?
> > I'll ask my IT staff about that. Or is there a way to get this
> > information from the logs or iwconfig?
> > 
> 
> I actually did mean whether the AP has automatic channel selection. I am
> not sure whether it is advertised in the beacons.
> I think you found the origin of the problem. I ran iwlist scan after the bug happened, and my network's APs are visible on 3 different channels (1, 6 and 11). When everything was fine, it was only on channel 11. The most surprising thing is that the precise AP I'm associated with is now visible on two channels (1 and 11).

Another weird fact is that after reloading brcmsmac (I had to do it twice to be able to reconnect), I still see my APs on these different 3 channels, and still it works fine. But maybe the channel change is what triggers the bug.

As you see, this is a very crowded place, with other networks using the same channels. This is probably not an ideal setup, but it's great to stress-test the drivers. ;-)


Regards

      parent reply	other threads:[~2012-01-31 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 10:31 BCM4313 keeps disconnecting with brcmsmac and multiple APs Milan Bouchet-Valat
2012-01-27  8:46 ` Arend van Spriel
2012-01-27 10:19   ` Felix Fietkau
2012-01-27 10:08 ` Arend van Spriel
2012-01-27 10:26   ` Milan Bouchet-Valat
2012-01-27 11:37     ` Arend van Spriel
2012-01-31 13:57       ` Milan Bouchet-Valat
2012-01-31 14:44         ` Arend van Spriel
2012-01-31 14:57         ` Milan Bouchet-Valat
2012-02-02  9:35         ` Milan Bouchet-Valat
2012-01-31 13:36     ` Milan Bouchet-Valat [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=32081421.179347.1328017006287.JavaMail.www@wsfrf1118 \
    --to=nalimilan@club-internet.fr \
    --cc=arend@broadcom.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).