From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] mosh ecn bits washed out
Date: Fri, 19 Mar 2021 07:08:10 -0700 [thread overview]
Message-ID: <CAA93jw60VpNtGd_0MzoaZBRO0azNptF-tdGyd7BZuUkSLr17nQ@mail.gmail.com> (raw)
In-Reply-To: <bc033e58bb1457d93a1dc66b197671faf6855b6f.camel@heistp.net>
On Fri, Mar 19, 2021 at 1:25 AM Pete Heist <pete@heistp.net> wrote:
>
> Meaning, the negotiation succeeds and ECT(0) is set going up, but
> zeroed on packets by the time they come down?
There has never been any "negotiation" for setting the ect(0) bit in mosh.
It's been set since 2012 on all udp packets.
I reasoned at the time, that since mosh is the tool of desparate sysadmins
everywhere coping with excessive latency and jitter on everything (the local
echo of keystrokes is a godsend), that turning further enabling CE would
help, or, if stuff with that bit set was dropped, be the focus of
outrage by sysadmins
everywhere and ecn support quickly reverted.
Nothing went wrong. :)
mosh has an extremely robust response to marks, reducing the rate to 2 frames
per second from as much as 60 fps on receipt of a single CE. Not going
any further is analogous to the "subpacket window" problem ecn
enabled tcps have, and attempting to
sustain that low frame rate essential for mosh's operation.
Ironically, since I last bothered to look, mosh gained ipv6 support, but the
parsing of cmsg and the setsockopt for ecn capability were not updated for that.
Also ironically, mosh packets were originally marked AF42 but it stopped working
on one of MITs networks, so the dscp setting was removed, but ecn kept.
https://github.com/mobile-shell/mosh/blob/master/src/network/network.cc#L166
It would be trivial to sce enable mosh.
>
> 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.
> >
>
>
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-03-19 14:08 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
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 ` Dave Taht [this message]
2021-03-19 14:59 ` [Ecn-sane] mosh ecn bits washed out 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=CAA93jw60VpNtGd_0MzoaZBRO0azNptF-tdGyd7BZuUkSLr17nQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=pete@heistp.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