From: Larry Finger <Larry.Finger@lwfinger.net>
To: Patrick McMunn <doctorwhoguy@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problem with b43 driver
Date: Fri, 02 Mar 2012 13:03:37 -0600 [thread overview]
Message-ID: <4F511989.8040508@lwfinger.net> (raw)
In-Reply-To: <CAKS+cu2g45-KvQdvT=5B8p7dCt76dwXgNjMSUARM5+v8Mz9joQ@mail.gmail.com>
On 03/02/2012 11:59 AM, Patrick McMunn wrote:
> A while back, a fix was issued for the b43 driver where the driver was
> not issuing beacons in ad-hoc mode (
> http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.33/ChangeLog-2.6.33.20
> ). I have a card which uses the driver, and it did allow me to use
> ad-hoc mode for sharing an internet connection. However, I think there
> is still some problem with the driver. When I start up my laptop (with
> an Intel wireless card) and try to connect to the connection which I
> created on my desktop which uses the b43 driver, there are occasions
> when it detects the network immediately, and there are occasions when
> it never does detect it even if I go to my desktop and stop then
> restart the network. I may wait 15 or 20 minutes before giving up on
> it. At the same time, my laptop may detect 3 or 4 wireless networks
> from neighbors' homes, but it will not detect mine. So I suspect that
> the b43 driver is somehow issuing beacons inconsistently. I'll be
> happy to supply any additional information I can upon request. Another
> thing that may or may not be related is that even when I do connect,
> the machines can only ping each other if I connect using channel 10.
> No other channel seems to work even if they successfully connect.
Does your laptop have a reasonable operating system that will let you run
wireshark in promiscuous mode? If so, please capture the traffic when you are
having this problem and check to see if the beacons are present.
That problem of needing to use channel 10 seems a bit strange.
Larry
prev parent reply other threads:[~2012-03-02 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 17:59 Problem with b43 driver Patrick McMunn
2012-03-02 19:03 ` Larry Finger [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=4F511989.8040508@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=doctorwhoguy@gmail.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).