From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Michael Welzl <michawe@ifi.uio.no>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] osx not doing ecn for me
Date: Fri, 20 Mar 2020 21:23:49 -0700 [thread overview]
Message-ID: <CAA93jw5+iUZ_VDPagMbnFOv5Vh_7mtzjVx1YyKrr7VCvhTCnxQ@mail.gmail.com> (raw)
In-Reply-To: <9427F843-64FC-4998-B3E1-0299162C1C7D@heistp.net>
Going back to looking at this my devices... my mac rarely attempts ecn
over ipv4 or ipv6 nowadays. It seems to fall back to not even trying,
frequently. So for example on one rrul test on a local AP, it will
successfuly try for all the connection, but on a subsequent test won't
try at all or only try two or so. I sat down to look at it harder with
the rrul test against various servers, today....
There is a complex heuristic at work here that I do not understand.
It's really hard to do science when you can't force it to always
negotiate, but I guess it explains
some of the complex data I have from the field where the attempts do
not match the size of the deployment in any sane way.
This is osx high sierra 10.13.6.
On Fri, Jan 10, 2020 at 1:41 AM Pete Heist <pete@heistp.net> wrote:
>
>
> > On Jan 10, 2020, at 9:48 AM, Michael Welzl <michawe@ifi.uio.no> wrote:
> >
> >> On Jan 10, 2020, at 12:45 AM, Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> On Thu, Jan 9, 2020 at 3:30 PM Pete Heist <pete@heistp.net> wrote:
> >>>
> >>> Mine negotiates it, but I’m stuck on 10.13.
> >>>
> >>> This likely isn’t the problem, but I’ve fallen for the trap before that “netstat -sp tcp” needs to be run as root or all counters show 0...
> >>
> >> No, that was the trap I'd fallen for. I'd seen it not attempt a couple
> >> negotiations (from looking at the packet captures), then ran that, and
> >> panicked!
> >
> > … and I thought that your Mac had discovered that you hate ECN and turned it off just for you :)
>
> I’d started on some other good conspiracy theories when it didn’t work for me but Jon set me straight. :)
>
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-03-21 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 21:18 Dave Taht
2020-01-09 21:41 ` Holland, Jake
2020-01-09 23:30 ` Pete Heist
2020-01-09 23:45 ` Dave Taht
2020-01-10 8:48 ` Michael Welzl
2020-01-10 9:41 ` Pete Heist
2020-03-21 4:23 ` Dave Taht [this message]
2020-03-21 18:41 ` Holland, Jake
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=CAA93jw5+iUZ_VDPagMbnFOv5Vh_7mtzjVx1YyKrr7VCvhTCnxQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=michawe@ifi.uio.no \
--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