Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Managed to break 802.11n (on a 3800)
Date: Sun, 19 Jan 2014 21:01:29 +0100	[thread overview]
Message-ID: <8F136BCE-4EA4-434C-B88C-9C282925406C@gmx.de> (raw)
In-Reply-To: <87wqhv3ie7.fsf@toke.dk>

Hi Toke,


On Jan 19, 2014, at 20:01 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Dave Taht <dave.taht@gmail.com> writes:
> 
>> hah. Calling it that is the opposite of my intent with default blow-up
>> of 802.11e - which has been to convince everyone it's busted and to
>> fix it.
>> 
>> rrul_be ?
> 
> Added an rrul_be test to netperf-wrapper git. Will do a new release
> version once I've fixed one or two other things. :)

	Great! just pull the repository.

I noticed the new "hostnames are mandatory police" kick in:

bash-3.2$ ./netperf-wrapper --list-tests
Available tests:
  cisco_5tcpup               :  RTT Fair Realtime Response Under Load
  cisco_5tcpup_2udpflood     :  Cisco 5TCP up + 2 6Mbit UDP
Error occurred: No hostname specified.

Maybe you could allow listing the tests without a hostname?

	Anyway., just ran the rrul_be test from my macbook to cerowrt and I still see the massive bias for upload of around 10:1, same as with rrul and rrul_coclassification, and tcp_bidirectional. When I ran tcp_bidirectional on the universities wireless network (the only test that actually runs there), I get larger downloads than uploads. Wireless is weird...


Best
	Sebastian

> 
> -Toke


  reply	other threads:[~2014-01-19 20:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 15:03 Aaron Wood
2014-01-16 15:29 ` Sebastian Moeller
2014-01-16 15:46   ` Aaron Wood
2014-01-16 17:20     ` Sebastian Moeller
2014-01-16 19:08       ` Aaron Wood
2014-01-16 20:10         ` Sebastian Moeller
2014-01-16 21:33           ` Aaron Wood
2014-01-16 22:50           ` Dave Taht
2014-01-16 23:15             ` Sebastian Moeller
2014-01-16 23:40               ` Dave Taht
2014-01-17 20:15                 ` Toke Høiland-Jørgensen
2014-01-17 20:17                   ` Dave Taht
2014-01-19 19:01                     ` Toke Høiland-Jørgensen
2014-01-19 20:01                       ` Sebastian Moeller [this message]
2014-01-19 20:58                         ` Toke Høiland-Jørgensen
2014-01-19 21:12                           ` Sebastian Moeller
2014-01-16 22:35         ` Dave Taht
2014-01-16 22:30   ` Dave Taht
2014-01-16 22:56     ` Sebastian Moeller
2014-01-16 23:12       ` Dave Taht
2014-01-16 23:25         ` Sebastian Moeller
2014-01-16 15:38 ` Robert Bradley
2014-01-16 15:46   ` Aaron Wood
2014-01-16 22:08 ` Dave Taht

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8F136BCE-4EA4-434C-B88C-9C282925406C@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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