From: Johannes Berg <johannes@sipsolutions.net>
To: ming li <mingli@cs.umass.edu>
Cc: Kalle Valo <kalle.valo@iki.fi>, linux-wireless@vger.kernel.org
Subject: Re: Adhoc-demo support in mac80211
Date: Tue, 24 Mar 2009 21:53:51 +0100 [thread overview]
Message-ID: <1237928031.4320.133.camel@johannes.local> (raw)
In-Reply-To: <c03d7e680903241348x27363902m764c25a9a439d419@mail.gmail.com> (sfid-20090324_214907_712583_E14D9763)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On Tue, 2009-03-24 at 16:48 -0400, ming li wrote:
> The adhoc-demo mode is also called pseudo-adhoc mode. It is simply the
> ad-hoc mode without control pkts. It does not probe for or associate
> to adjacent adhoc networks. The user has to set all the nodes to the
> same channel manually. The good thing of adhoc-demo is that it does
> not have the beaconing overhead or the IBSS merging/splitting problem.
Do you really need to disable beaconing, or would it be sufficient for
you to just fix the BSSID and the channel? You can do those two already
easily, something like
iwconfig wlan0 ap ...
iwconfig wlan0 channel ...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-24 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 16:59 Adhoc-demo support in mac80211 ming li
2009-03-24 17:55 ` Kalle Valo
2009-03-24 20:33 ` Johannes Berg
2009-03-24 20:48 ` ming li
2009-03-24 20:53 ` Johannes Berg [this message]
2009-03-24 20:58 ` ming li
2009-03-24 21:10 ` Alina Friedrichsen
2009-03-25 8:57 ` Johannes Berg
2009-03-24 21:08 ` Alina Friedrichsen
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=1237928031.4320.133.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=mingli@cs.umass.edu \
/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).