From: Pete Heist <pete@heistp.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
bloat@lists.bufferbloat.net, "Matt Taggart" <matt@lackof.org>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Ubiquiti Launches a Speed Test Network
Date: Sat, 07 Sep 2019 13:09:55 -0000 [thread overview]
Message-ID: <9DEC00AC-CE2B-400A-AF78-FCAD6F14E47C@heistp.net> (raw)
In-Reply-To: <182F72BE-7448-4F59-AD4D-64267D0721ED@gmx.de>
> On Sep 7, 2019, at 2:02 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Pete,
>
> If the PayPal ad of an irtt packet would contain the requested DSCP as ascci string (maybe starting with a string like "DSCP: 46: 101110 (EF)" in the first few bytes of the payload would make confirming bleaching/remapping from packetdumps relatively convenient, say just by looking at a packet in Wireshark and comparing the IP headers DSCP value with the string in the payload. Sure that is not automated, but would be great in at least allowing to test for bleaching in the packets received from a irtt server....
>
> But, as much as I would like that feature, I believe the total audience will be quite small....
>
> Best Regards
> Sebastian
You probably noticed, but it’s possible to fill the whole payload with the dscp byte, although the server has to allow that to put it in replies (requests can always contain it), for example:
irtt server --allow-fills=“*"
irtt client --dscp=0x10 -l 256 --fill=pattern:10 --sfill=pattern:10 localhost
If you still want the payload to be mostly random, I could potentially add a new fill mode which fills first with some arbitrary bytes (or a string) then the rest is random. I think in the case of flent, the irtt runner fills with random, but this only applies when there’s actually a payload (i.e. for the voip tests).
next prev parent reply other threads:[~2019-09-07 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 19:51 [Cerowrt-devel] " Matt Taggart
2019-09-06 8:15 ` Mikael Abrahamsson
2019-09-06 8:27 ` [Cerowrt-devel] [Bloat] " Toke Høiland-Jørgensen
2019-09-06 9:56 ` Sebastian Moeller
2019-09-06 12:18 ` Mikael Abrahamsson
2019-09-06 17:59 ` Toke Høiland-Jørgensen
2019-09-06 18:33 ` Sebastian Moeller
2019-09-06 22:50 ` Toke Høiland-Jørgensen
2019-09-06 22:56 ` Sebastian Moeller
2019-09-06 23:12 ` Toke Høiland-Jørgensen
2019-09-07 11:33 ` Pete Heist
2019-09-07 12:02 ` Sebastian Moeller
2019-09-07 13:09 ` Pete Heist [this message]
2019-09-07 13:47 ` Valdis Klētnieks
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=9DEC00AC-CE2B-400A-AF78-FCAD6F14E47C@heistp.net \
--to=pete@heistp.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=matt@lackof.org \
--cc=moeller0@gmx.de \
--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