All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Manuel Munz <freifunk@somakoma.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: No beacons in ad-hoc mode with b43
Date: Sun, 18 Sep 2011 18:05:24 -0500	[thread overview]
Message-ID: <4E767934.3000502@lwfinger.net> (raw)
In-Reply-To: <4E766435.3010707@somakoma.de>

On 09/18/2011 04:35 PM, Manuel Munz wrote:
> On 17.09.2011 23:43, Manuel Munz wrote:
>> Hi,
>>
>> i want to use b43 on older broadcom wireless routers with openwrt, but
>> there seems to be a problem: The router doesn't send beacons in adhoc
>> mode (verified with wireshark), which means users can't see the network
>> in a network scan. So is there a problem in the adhoc implementation
>> with b43? Could someone please have a look at this? It is preventing us
>> from using b43 in our mesh for too long now.
>>
>
> Hi,
>
> after trying various things i came up with the following patch which
> seems to address the issue for me.

I confirmed your fix with an ad-hoc connection from one b43 device to another.

Your patch needs to be reformatted to satisfy kernel requirements. I will take 
care of that for you, but you need to read Documentation/SubmittingPatches.

Good work to find the fix.

Larry


      reply	other threads:[~2011-09-18 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17 21:43 No beacons in ad-hoc mode with b43 Manuel Munz
2011-09-17 22:13 ` Rafał Miłecki
2011-09-17 22:23   ` Michael Büsch
2011-09-18  0:16   ` Manuel Munz
2011-09-18 21:35 ` Manuel Munz
2011-09-18 23:05   ` 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=4E767934.3000502@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=freifunk@somakoma.de \
    --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 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.