From: Sebastian Moeller <moeller0@gmx.de>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Testing Offer - Comcast L4S Trials
Date: Thu, 29 Jun 2023 16:32:25 +0200 [thread overview]
Message-ID: <E524CDBC-533A-4670-AAC4-C9CC2AEE5478@gmx.de> (raw)
In-Reply-To: <AC6B8C73-E5EE-487B-93E5-E3622757155A@cable.comcast.com>
While I have no test that I can volunteer, let alone a test that supports L4S.
I want to take the opportunity to share my tcpdump invocations that can show ECN in action on the IP-level:
# ECN: IPv4
tcpdump -i pppoe-wan -v -n 'ip and (ip[1] & 0x3) != 0' # NOT Not-ECT
tcpdump -i pppoe-wan -v -n 'ip and (ip[1] & 0x3) == 0' # Not-ECT
tcpdump -i pppoe-wan -v -n 'ip and (ip[1] & 0x3) == 1' # ECT(1)
tcpdump -i pppoe-wan -v -n 'ip and (ip[1] & 0x3) == 2' # ECT(0)
tcpdump -i pppoe-wan -v -n 'ip and (ip[1] & 0x3) == 3' # CE
# ECN: IPv6
tcpdump -i pppoe-wan -v -n 'ip6 and (ip6[0:2] & 0x30) >> 4 != 0' # NOT Not-ECT
tcpdump -i pppoe-wan -v -n 'ip6 and (ip6[0:2] & 0x30) >> 4 == 0' # Not-ECT
tcpdump -i pppoe-wan -v -n 'ip6 and (ip6[0:2] & 0x30) >> 4 == 1' # ECT(1)
tcpdump -i pppoe-wan -v -n 'ip6 and (ip6[0:2] & 0x30) >> 4 == 2' # ECT(0)
tcpdump -i pppoe-wan -v -n 'ip6 and (ip6[0:2] & 0x30) >> 4 == 3' # CE
# ECN IPv4/6
tcpdump -i pppoe-wan -v -n '(ip6 and (ip6[0:2] & 0x30) >> 4 != 0)' or '(ip and (ip[1] & 0x3) != 0)' # NOT Not-ECT
tcpdump -i pppoe-wan -v -n '(ip6 and (ip6[0:2] & 0x30) >> 4 == 1)' or '(ip and (ip[1] & 0x3) == 1)' # ECT(1)
tcpdump -i pppoe-wan -v -n '(ip6 and (ip6[0:2] & 0x30) >> 4 == 2)' or '(ip and (ip[1] & 0x3) == 2)' # ECT(0)
tcpdump -i pppoe-wan -v -n '(ip6 and (ip6[0:2] & 0x30) >> 4 == 3)' or '(ip and (ip[1] & 0x3) == 3)' # CE
Just replace "-i pppoe-wan" with your own network interface of interest, this seems to work on both recent inux and older macos (12.6.7).
Before L4S roll-out the test for ECT(1) can be helpful to confirm that there is no background ECT(1) usage that might (or might not) cause issues with L4S.
> On Jun 29, 2023, at 16:12, Livingood, Jason via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> As noted recently, we (Comcast) will soon begin L4S testing with customers. We’re working on our test plans now. So my offer here is to let me know if:
> 1 – You have test probes you’d like us to deploy. We are working on a plan to send out (1) University of Chicago NetMicroscope probes and (2) RIPE Atlas probes.
> 2 – You have web-based tests you’d like people to run, or have one-click install client for Mac or Windows. (Most testers will not be technical enough to run CLI-based tests, the the exception of the Apple network responsiveness test.)
>
> Thx! If this is of interest, please ping me 1:1 off-list.
> Jason
>
> Current list
> (1.a) Ookla web-based
> (1.b) Ookla client
> (1.c) M-Labs NDT
> (1.d) Fastly web-based
> (1.e) Netflix web-based
> (1.f) Waveform web-based
> (1.g) DSL Reports web-based
> (1.h) Apple Network Responsiveness test
[SM] Not mine to offer, but I think speed.cloudflare.com also might be interesting as it seems to follow the modern "let's not ignore latency under load" paradigm as well as the translate the results into terms suitable for casual users, while also reporting the hard numbers for those interested.
What seems not available right now is a public test that can selectively exercise both L4S queues independently.
Regards
Sebastian
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2023-06-29 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 14:12 Livingood, Jason
2023-06-29 14:32 ` 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=E524CDBC-533A-4670-AAC4-C9CC2AEE5478@gmx.de \
--to=moeller0@gmx.de \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@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