From: Dave Taht <dave.taht@gmail.com>
To: mandy ahuja <mandyahuja013@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] how to prove bufferbloat with ns2.35 simulator
Date: Sun, 22 Feb 2015 01:22:03 -0800 [thread overview]
Message-ID: <CAA93jw6N4vzz=Vgm=zimhAVMbuZFCJz-kWq6LYYPZ2aGsnWP0w@mail.gmail.com> (raw)
In-Reply-To: <CALbqCD50XxSqTobe+7FSi6dApUyCSy=_CB7OqfUecF3ivCggyg@mail.gmail.com>
you cant. use ns2.36
http://mailman.isi.edu/pipermail/ns-users/2014-December/073965.html
On Sun, Feb 22, 2015 at 1:14 AM, mandy ahuja <mandyahuja013@gmail.com> wrote:
> Hi everybody
> please tell me how can i show bufferbloat problem using traditional AQM(RED
> etc.) in ns2.35.
> can anyone provide me the tcl script??
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
prev parent reply other threads:[~2015-02-22 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 9:14 mandy ahuja
2015-02-22 9:22 ` Dave Taht [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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6N4vzz=Vgm=zimhAVMbuZFCJz-kWq6LYYPZ2aGsnWP0w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mandyahuja013@gmail.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