From: Manuel Munz <freifunk@somakoma.de>
To: linux-wireless@vger.kernel.org
Subject: Re: No beacons in ad-hoc mode with b43
Date: Sun, 18 Sep 2011 23:35:49 +0200 [thread overview]
Message-ID: <4E766435.3010707@somakoma.de> (raw)
In-Reply-To: <4E751496.30903@somakoma.de>
[-- Attachment #1.1: Type: text/plain, Size: 613 bytes --]
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.
regards, Manuel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 820-b43-fix-beacons.patch --]
[-- Type: text/x-patch; name="820-b43-fix-beacons.patch", Size: 469 bytes --]
--- a/drivers/net/wireless/b43/main.c
+++ b/drivers/net/wireless/b43/main.c
@@ -1616,7 +1616,8 @@ static void handle_irq_beacon(struct b43
u32 cmd, beacon0_valid, beacon1_valid;
if (!b43_is_mode(wl, NL80211_IFTYPE_AP) &&
- !b43_is_mode(wl, NL80211_IFTYPE_MESH_POINT))
+ !b43_is_mode(wl, NL80211_IFTYPE_MESH_POINT) &&
+ !b43_is_mode(wl, NL80211_IFTYPE_ADHOC))
return;
/* This is the bottom half of the asynchronous beacon update. */
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-18 21:35 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 [this message]
2011-09-18 23:05 ` Larry Finger
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=4E766435.3010707@somakoma.de \
--to=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 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).