From: Pete Heist <pete@heistp.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] mosh ecn bits washed out
Date: Fri, 19 Mar 2021 09:25:17 +0100 [thread overview]
Message-ID: <bc033e58bb1457d93a1dc66b197671faf6855b6f.camel@heistp.net> (raw)
In-Reply-To: <CAA93jw7w3vvTJf+HdK4rY_VVbzbrcfG+Xq9=k3nrGN2RkXX00A@mail.gmail.com>
Meaning, the negotiation succeeds and ECT(0) is set going up, but
zeroed on packets by the time they come down?
The negotiation can also be blocked with iptables --ecn-tcp-remove,
which just zeroes out ECE and CWR, preventing negotiation
(https://git.netfilter.org/iptables/tree/extensions/libipt_ECN.c), but
I doubt that's very commonly done.
On Thu, 2021-03-18 at 13:00 -0700, Dave Taht wrote:
> mosh, which has long had excellent support for ecn, appears to be
> getting the
> ecn bit washed out along my path from california to england.
>
> ecn survives up that way, but not down.
>
> Just a single data point thus far.
>
next prev parent reply other threads:[~2021-03-19 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 20:00 Dave Taht
2021-03-19 8:25 ` Pete Heist [this message]
2021-03-19 8:56 ` Sebastian Moeller
2021-03-19 9:18 ` [Ecn-sane] re-marking ECT(1) to ECT(0) (was: mosh ecn bits washed out) Pete Heist
2021-03-19 14:24 ` Sebastian Moeller
2021-03-19 14:08 ` [Ecn-sane] mosh ecn bits washed out Dave Taht
2021-03-19 14:59 ` Pete Heist
2021-03-19 15:26 ` Dave Taht
2021-03-20 5:24 ` Mikael Abrahamsson
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc033e58bb1457d93a1dc66b197671faf6855b6f.camel@heistp.net \
--to=pete@heistp.net \
--cc=dave.taht@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