From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C53D43B29E for ; Wed, 13 Nov 2019 10:36:43 -0500 (EST) Received: by mail-wr1-x42b.google.com with SMTP id w9so2909432wrr.0 for ; Wed, 13 Nov 2019 07:36:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J5+QcpYoDFOu5mqlqGoRm3PP7M4vcXzCX+ypfMqSjrc=; b=foxQHDRqj2t7uwAd6EN9ZN5WZRk9nOo4PK+W7wIaxd/EyWm8iWE9aA6CQSSfSu/zu9 FEGXIUdkU0CS0D0ZQbawye6t/gxSyTzL/C1qxBkgdG/6DwzYIV33MEoZB6ZcrJifMXeR n0t4wXx5VS6jKcGJdlURV1uRVxqzN9lnry0pg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J5+QcpYoDFOu5mqlqGoRm3PP7M4vcXzCX+ypfMqSjrc=; b=Yyxi5dn4Y1ddN3kAiJKGG6onlqa1J9Ho+wAYm5qX5k2Q/rUFIzbmT05m2OIm4yIY3E 8am+OD1cVjerPEQGoVSKUM9lmbkcQn0r7U0n21gG1OPkuQPmu+gYrL60znpNrFqA/U29 U7YkSR6oUbqfz45MC5hpFQU//0NHghdwqwgaGafKvuzsTTjhgLAAR2dE7DvnLIFWFUrb 7ka72VPCnU4cMw8a2lWMjT0F0JvqWMeuBIx5r9DbC09PtHkS0y5IeJjWLKqffHiocb50 h/d451yV8xB/S/Pk/8SrTlmxjVPwVWndcCYSb/dVOuTVoKuAhcbq0nZsAa8CuvFAXWS5 FxLg== X-Gm-Message-State: APjAAAVgyC9sSLDcPFgj9MTDPzISmgBtJlCrpAB9Fr5tLgR/27wLn6pu 6g7tqDWU/lcMl7W3f3e9Crc1gHVU1c3swE+DQWUWQg== X-Google-Smtp-Source: APXvYqzr/MTp24IqzgmjHwjBNUxXVkec9ZXaGdvhotkWIw3zhoOtdndh6XIPhupjbTtiEZ2ZQzwDSsjBRjUoVtK8i70= X-Received: by 2002:a5d:4e90:: with SMTP id e16mr3639732wru.224.1573659402905; Wed, 13 Nov 2019 07:36:42 -0800 (PST) MIME-Version: 1.0 References: <201911131525.xADFPQ61044389@gndrsh.dnsmgr.net> <87tv77oklo.fsf@toke.dk> In-Reply-To: <87tv77oklo.fsf@toke.dk> From: Luca Muscariello Date: Wed, 13 Nov 2019 16:36:31 +0100 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>, Rich Brown , ECN-Sane Content-Type: multipart/alternative; boundary="000000000000b55e3705973c2113" Subject: Re: [Ecn-sane] Meanwhile, over on NANOG... X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2019 15:36:43 -0000 --000000000000b55e3705973c2113 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 13, 2019 at 4:35 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: > "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net> writes: > > >> -t is the TOS value; so those two happen to correspond to ECT(1) and > >> ECT(0); and as you can see they go two different paths. Which would be > >> consistent with the SYN going one way and the data packets going > >> another. > > > > Perhaps Old enough that maybe they are treating that as TOS byte? > > > > Looks like you have nailed it though, someone has a broken hash. > > Yup, seems like it. Posted a writeup to the NANOG list in response to > the guy asking; it hasn't showed up in the archive, though, so I guess > it's still in the moderation queue. > > I think I'll write the whole thing up as a blog post as well, once it's > resolved. I'll see if I can get them to tell me which router make and > model is doing this. > > Thanks everyone who helped with ideas etc! :) > > great! You'll get a free subscription for a full year! > -Toke > --000000000000b55e3705973c2113 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Nov 13, 2019 at 4:35 = PM Toke H=C3=B8iland-J=C3=B8rgensen <tok= e@toke.dk> wrote:
"Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net> writes:

>> -t is the TOS value; so those two happen to correspond to ECT(1) a= nd
>> ECT(0); and as you can see they go two different paths. Which woul= d be
>> consistent with the SYN going one way and the data packets going >> another.
>
> Perhaps Old enough that maybe they are treating that as TOS byte?
>
> Looks like you have nailed it though, someone has a broken hash.

Yup, seems like it. Posted a writeup to the NANOG list in response to
the guy asking; it hasn't showed up in the archive, though, so I guess<= br> it's still in the moderation queue.

I think I'll write the whole thing up as a blog post as well, once it&#= 39;s
resolved. I'll see if I can get them to tell me which router make and model is doing this.

Thanks everyone who helped with ideas etc! :)


great! You'll get a free subscri= ption for a full year!


=C2=A0
-Toke
--000000000000b55e3705973c2113--