From: "Javier Cardona" <javier@cozybit.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: igor_trindade@yahoo.com.br, "Jouni Malinen" <j@w1.fi>,
"Andrey Yurovsky" <andrey@cozybit.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 user space
Date: Mon, 8 Dec 2008 10:17:00 -0800 [thread overview]
Message-ID: <445f43ac0812081017q2ac6ae1h84a86099518773cc@mail.gmail.com> (raw)
In-Reply-To: <1228658260.22164.41.camel@johannes.berg>
Johannes,
On Sun, Dec 7, 2008 at 5:57 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> For example, consider this scenario with three mesh points:
>
> MP1 ---- MP2 ---- MP3
>
> where MP1 and MP3 cannot directly communicate because they are too far
> apart, physically. It isn't possible to test such a scenario with hwsim
> because hwsim has no concept of distance.
>
> One easy solution to this would be to introduce "air groups", each just
> a number.
>
> [...]
>
> Does that make sense? Do you think it's flexible enough? Should we maybe
> use a u64 so we have more flexibility? It should be fairly easy to do
> this, I think.
>
>
> Of course, this isn't as general as it could be.
To be useful for our mesh tests this "virtual air" would have to allow
us to create 3 groups, each one a superset of the previous. The
smallest group would be the set of nodes that can a node communicate
with ("A can talk to B"). The next larger group would be nodes on
which a node that can interfere ("A can screw up C's reception").
Finally, the largest would be nodes that can detect each other ("A can
detect when D is transmitting").
Cheers,
Javier
--
Javier Cardona
cozybit Inc.
next prev parent reply other threads:[~2008-12-08 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <456087.50493.qm@web59308.mail.re1.yahoo.com>
2008-12-07 13:57 ` mac80211 user space Johannes Berg
2008-12-08 18:17 ` Javier Cardona [this message]
2008-12-08 19:52 ` Johannes Berg
2008-12-08 20:25 ` Javier Cardona
2008-12-08 20:32 ` Johannes Berg
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=445f43ac0812081017q2ac6ae1h84a86099518773cc@mail.gmail.com \
--to=javier@cozybit.com \
--cc=andrey@cozybit.com \
--cc=igor_trindade@yahoo.com.br \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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