From: Kalle Valo <kalle.valo@iki.fi>
To: Javier Cardona <javier@cozybit.com>
Cc: linux-wireless@vger.kernel.org,
Andrey Yurovsky <andrey@cozybit.com>,
johannes@sipsolutions.net, linville@tuxdriver.com,
devel@lists.open80211s.org
Subject: Re: [PATCH 3/8] mac80211: Simulate transmission losses on plinks to aid in testing mesh metrics.
Date: Sat, 08 Aug 2009 11:09:09 +0300 [thread overview]
Message-ID: <87d476n2vu.fsf@litku.valot.fi> (raw)
In-Reply-To: <1249702711-32737-4-git-send-email-javier@cozybit.com> (Javier Cardona's message of "Fri\, 7 Aug 2009 20\:38\:26 -0700")
Javier Cardona <javier@cozybit.com> writes:
> This enables us to specify a simulated loss probability per mesh peer link.
> Useful to simulate and test different mesh topologies and test different mesh
> metrics.
>
> The simulated loss rate setting can be configured as a plink action. The
> intended use is:
>
> iw dev mesh station set <MAC> plink_action loss 25
I really would not like to see debug functionality in nl80211 just to
simplify the maintenance. Debugging belongs to debugfs or somewhere
else.
Disclaimer: I know nothing about mesh and I may have misunderstood
something.
--
Kalle Valo
next prev parent reply other threads:[~2009-08-08 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 3:38 Mesh fixes and improvements Javier Cardona
2009-08-08 3:38 ` [PATCH 1/8] mac80211: Improve dequeing from mpath frame queue Javier Cardona
2009-08-08 3:38 ` [PATCH 2/8] mac80211: Use correct sign for mesh active path refresh Javier Cardona
2009-08-08 3:38 ` [PATCH 3/8] mac80211: Simulate transmission losses on plinks to aid in testing mesh metrics Javier Cardona
2009-08-08 3:38 ` [PATCH 4/8] mac80211: Use 3-address format for mesh broadcast frames Javier Cardona
2009-08-08 3:38 ` [PATCH 5/8] mac80211: Update the station failed frames average when minstrel is used Javier Cardona
2009-08-08 3:38 ` [PATCH 6/8] mac80211: Early detection of broken mesh paths when using minstrel Javier Cardona
2009-08-08 3:38 ` [PATCH 7/8] mac80211: Assign a default mesh beaconing interval Javier Cardona
2009-08-08 3:38 ` [PATCH 8/8] mac80211: Moved mpath and mpp growth to mesh workqueue Javier Cardona
2009-08-08 8:09 ` Kalle Valo [this message]
2009-08-08 8:46 ` [PATCH 3/8] mac80211: Simulate transmission losses on plinks to aid in testing mesh metrics Johannes Berg
2009-08-08 9:09 ` Mesh fixes and improvements Johannes Berg
2009-08-09 4:55 ` Javier Cardona
2009-08-10 17:52 ` John W. Linville
2009-08-10 19:15 ` Mesh fixes and improvements [v2] Javier Cardona
2009-08-10 19:15 ` [PATCH 1/7] mac80211: Improve dequeing from mpath frame queue Javier Cardona
2009-08-10 19:15 ` [PATCH 2/7] mac80211: Use correct sign for mesh active path refresh Javier Cardona
2009-08-10 19:15 ` [PATCH 3/7] mac80211: Use 3-address format for mesh broadcast frames Javier Cardona
2009-08-10 19:15 ` [PATCH 4/7] mac80211: Update the station failed frames average when minstrel is used Javier Cardona
2009-08-10 19:15 ` [PATCH 5/7] mac80211: Early detection of broken mesh paths when using minstrel Javier Cardona
2009-08-10 19:15 ` [PATCH 6/7] mac80211: Assign a default mesh beaconing interval Javier Cardona
2009-08-10 19:15 ` [PATCH 7/7] mac80211: Move mpath and mpp growth to mesh workqueue Javier Cardona
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=87d476n2vu.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=andrey@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).