From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Manuel Munz <freifunk@somakoma.de>, linux-wireless@vger.kernel.org
Subject: Re: No beacons in ad-hoc mode with b43
Date: Sun, 18 Sep 2011 00:23:20 +0200 [thread overview]
Message-ID: <20110918002320.03f6a9fc@milhouse> (raw)
In-Reply-To: <CACna6rxN+9ZJVnt-WGpxvyUrnBO9gnVOcTeZD9=eJZOUjJcgww@mail.gmail.com>
On Sun, 18 Sep 2011 00:13:32 +0200
Rafał Miłecki <zajec5@gmail.com> wrote:
> 2011/9/17 Manuel Munz <freifunk@somakoma.de>:
> > 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.
adhoc is not tested a lot with b43 and nobody is really interested in it.
I _think_ it used to work, however.
You should probably compare AP vs adhoc codepaths. AP mode an adhoc are very
similar with only tiny differences in the driver.
> > Router:
> > Siemens SE505 (very similar to wrt54g), Broadcom 4712 WLAN (core revision 7)
>
> Please give us at least
> lspci -nn | grep 14e4
This is an embedded device.
--
Greetings, Michael.
next prev parent reply other threads:[~2011-09-17 22:23 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 [this message]
2011-09-18 0:16 ` Manuel Munz
2011-09-18 21:35 ` Manuel Munz
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=20110918002320.03f6a9fc@milhouse \
--to=m@bues.ch \
--cc=freifunk@somakoma.de \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@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 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).