From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
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, 08 Dec 2008 21:32:19 +0100 [thread overview]
Message-ID: <1228768339.22164.133.camel@johannes.berg> (raw)
In-Reply-To: <445f43ac0812081225o516ad4a9ye86557b720e1b81@mail.gmail.com> (sfid-20081208_212546_395656_BCBF9145)
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Mon, 2008-12-08 at 12:25 -0800, Javier Cardona wrote:
> > That's something we can't actually simulate since you're trying to see
> > whether they do NAV updates correctly, right?
>
> I was trying to simulate hidden nodes, which are unavoidable given the
> distributed nature of the mesh.
> Also trying to simulate "starvation at the edges", which varies
> greatly with the collision avoidance threshold.
> But, hey, I was just day dreaming. Even the simpler air groups that
> you proposed would be very useful.
:)
Makes a lot of sense, and you can maybe even implement that when a
userspace program is doing the packet propagation, but for topology
testing I think we should start with the simpler groups thing. And as I
said, the userspace propagation will actually need to turn off in-kernel
propagation which fits setting airgroups to 0.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-12-08 20:32 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
2008-12-08 19:52 ` Johannes Berg
2008-12-08 20:25 ` Javier Cardona
2008-12-08 20:32 ` Johannes Berg [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=1228768339.22164.133.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=igor_trindade@yahoo.com.br \
--cc=j@w1.fi \
--cc=javier@cozybit.com \
--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