From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Luca Muscariello <muscariello@ieee.org>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
Rich Brown <richb.hanover@gmail.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] Meanwhile, over on NANOG...
Date: Tue, 12 Nov 2019 15:35:25 +0100 [thread overview]
Message-ID: <87pnhxp3gy.fsf@toke.dk> (raw)
In-Reply-To: <CAH8sseTU+p7tv3iLzs8Ddmnzwv0GT__1ehmDqKDkME0pf9hAtQ@mail.gmail.com>
Luca Muscariello <muscariello@ieee.org> writes:
> On Tue, Nov 12, 2019 at 2:02 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Mikael Abrahamsson <swmike@swm.pp.se> writes:
>>
>> > On Tue, 12 Nov 2019, Toke Høiland-Jørgensen wrote:
>> >
>> >> I'm not on the nanog list, but feel free to cross-post; would be good
>> to
>> >> actually get to the bottom of this issue! Marek and I already had an
>> >> off-list back-and-forth after that original thread, and we couldn't
>> find
>> >> anything wrong on the Cloudflare side. And the RSTs have a higher TTL
>> >> than the actual traffic, indicating an in-path problem...
>> >
>> > tcptraceroute supports setting/clearing ECN bits (-E), would be very
>> > interesting to see difference between those tcptraceroutes?
>>
>> No difference. But the RST is not being sent as a response to the SYN;
>> it is sent in response to the first data packet...
>>
>> ... and now that I'm re-testing, things were working for a little while,
>> but now the bug is back. I got an intermittent successful connection
>> with the same TTL that I was previously getting the RST from. And now
>> I'm back to getting RSTed.
>>
>> So I guess there's some kind of multipath issue here; ECMP path,
>> multiple routing upstreams, or a broken load balancer? Any other ideas?
>>
>
>
> It makes me think of some usage of anycast TCP on the cloudflare side.
> What service is this Toke?
Yeah, I did also think about anycast when I said "multiple routing
upstreams". For testing I've just been doing 'curl 1.1.1.1'. But
Cloudflare-hosted sites in general seem to have this problem; for
instance, 'curl -4 bufferbloat.net' also fails (but IPv6 is fine).
-Toke
next prev parent reply other threads:[~2019-11-12 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 12:07 Rich Brown
2019-11-12 12:20 ` Toke Høiland-Jørgensen
2019-11-12 12:25 ` Mikael Abrahamsson
2019-11-12 13:02 ` Toke Høiland-Jørgensen
2019-11-12 13:54 ` Luca Muscariello
2019-11-12 14:35 ` Toke Høiland-Jørgensen [this message]
2019-11-12 22:01 ` Toke Høiland-Jørgensen
2019-11-13 0:04 ` Rodney W. Grimes
2019-11-13 8:05 ` Luca Muscariello
2019-11-13 10:45 ` Toke Høiland-Jørgensen
2019-11-13 15:36 ` Rodney W. Grimes
2019-11-13 10:43 ` Toke Høiland-Jørgensen
2019-11-13 15:25 ` Rodney W. Grimes
2019-11-13 15:35 ` Toke Høiland-Jørgensen
2019-11-13 15:36 ` Luca Muscariello
2019-11-13 15:42 ` Rodney W. Grimes
2019-11-13 15:52 ` Toke Høiland-Jørgensen
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=87pnhxp3gy.fsf@toke.dk \
--to=toke@toke.dk \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=muscariello@ieee.org \
--cc=richb.hanover@gmail.com \
--cc=swmike@swm.pp.se \
/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