From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D601A3B29E for ; Wed, 13 Nov 2019 10:35:17 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1573659316; bh=2rM3GH80mepBRSsi+eejJR7kpZhm2bJsTasiGHA9BbI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Kh7PLg2S0ePz+uWy0hvBL88dJo2YbFli+wT2LxV13lXlUR6MCi1mtHYddp0tT6g6q mdTUE54RtFuHIiT85mk85+p5rY8Yw+/QIiFCI/3YF+XKI1jNSBEYRisNc2Lw2fqMT1 pfTDvzPsckgmDDfuL9D/AQBe0EwjS85nx21x/NxiRkhMOYskxaYYYT2Qjs63ieL3Ni sM5k9PJ1rj8N0Lmq8kNcp8o8r0DW12s8aL+9lWCBBfyObo1pGHG8O8HccHHvE6RPiM IYLnj8A9iVH6a+ZT/s+bU870zuM+shzfh11qF3O1aJsNSG54Rdmq8y7JXyLBRlrcNT 0FlkX1woHhN2A== To: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net> Cc: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>, Luca Muscariello , Rich Brown , ECN-Sane In-Reply-To: <201911131525.xADFPQ61044389@gndrsh.dnsmgr.net> References: <201911131525.xADFPQ61044389@gndrsh.dnsmgr.net> Date: Wed, 13 Nov 2019 16:35:15 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87tv77oklo.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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:35:18 -0000 "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! :) -Toke