From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Fwd: [Ns-developers] 802.11n A-MPDU Support in ns3?
Date: Sun, 21 Oct 2012 08:29:20 -0700 [thread overview]
Message-ID: <CAA93jw7xGgut98Ch9DNJ4AHdQoG9=hOV2fDg-ianQfHfDDizuQ@mail.gmail.com> (raw)
I would like one day for the wifi models to line up with the os'es themselves...
---------- Forwarded message ----------
From: Ahmad Showail <ahmad.showail@kaust.edu.sa>
Date: Sun, Oct 21, 2012 at 4:50 AM
Subject: [Ns-developers] 802.11n A-MPDU Support in ns3
To: ns-developers@isi.edu
Cc: kamran jamshaid <kamran.jamshaid@kaust.edu.sa>
Good day,
Apparently, only MSDU aggregation (A-MSDU) is available in ns3. Is there
any plans to support A-MPDU soon?
Regards,
Ahmad
--
------------------------------
This message and its contents, including attachments are intended solely
for the original recipient. If you are not the intended recipient or have
received this message in error, please notify me immediately and delete
this message from your computer system. Any unauthorized use or
distribution is prohibited. Please consider the environment before printing
this email.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2012-10-21 15:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw7xGgut98Ch9DNJ4AHdQoG9=hOV2fDg-ianQfHfDDizuQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
/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