From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Erik Auerswald <auerswal@unix-ag.uni-kl.de>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Ecn-sane] quick question
Date: Sat, 26 Aug 2023 17:35:15 +0200 [thread overview]
Message-ID: <C69B4F41-105B-485E-9EBB-8416252D6328@gmx.de> (raw)
In-Reply-To: <D27D02DD-A6FB-4223-B12D-66F935978846@gmail.com>
Hi Jonathan, hi Erik,
that was helpful, thanks!
I now played around with tcpdump a bit an apparently:
tcpdump -i pppoe-wan -v -n 'tcp[tcpflags] & (tcp-ece|tcp-cwr) != 0' # TCP ECN flags, ECN in action
will allow me to quickly see whether I get ECE or CWR flags in my traffic, so I will use this for the next steam download to see whether there is any ECN activity. I guess ECN echos will be apparent as these are from my host, so I might simply reduce the logging to CWR.
> On Aug 26, 2023, at 14:51, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 26 Aug, 2023, at 3:42 pm, Erik Auerswald <auerswal@unix-ag.uni-kl.de> wrote:
>>
>> I find the attached screenshot quite unreadable.
>
> Yeah, I forgot to prevent Apple Mail from auto-shrinking it.
[SM] I run into this same issue from time to time ;), but even the reduced screen shot and the surrounding informatin was enough to find that "page" in the RFC.
Regards
Sebastian
> Here's the original:
>
> <Screenshot 2023-08-26 at 3.03.03 pm.png>
>
> I also rearranged the formula and made log-log plots over the range of likely RTTs and bandwidths:
> <Screenshot 2023-08-26 at 3.49.14 pm.png>
>
> - Jonathan Morton
prev parent reply other threads:[~2023-08-26 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 11:48 [Bloat] " Sebastian Moeller
2023-08-26 12:06 ` [Bloat] [Ecn-sane] " Jonathan Morton
2023-08-26 12:34 ` Sebastian Moeller
2023-08-26 12:42 ` Erik Auerswald
2023-08-26 12:51 ` Jonathan Morton
2023-08-26 15:35 ` Sebastian Moeller [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=C69B4F41-105B-485E-9EBB-8416252D6328@gmx.de \
--to=moeller0@gmx.de \
--cc=auerswal@unix-ag.uni-kl.de \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@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