From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 18E063B2A4 for ; Wed, 25 Mar 2020 05:04:40 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1585127074; bh=wGIxOckhzos91ZiB5tqf7kv+gIQZkTHsXpplIo4Oc/4=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=QbnXf2zDaMrJ3nT0cp301gFSwdtc8oxgwXavC6/+YclySVpF63zUHrHs1gd2M6qhe +KDrW+u8ju6+qmVyGgPuzbzUlLz+SCxYQHV9oFRvGK46pjvNORY0q2DEwLlEgICJMU gB/BFO1W+se5GxIU/YvX2AyaCNXbsA0mL00omvM8= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.11.12.22] ([134.76.241.253]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MLzBj-1izE830NBx-00Hz5l; Wed, 25 Mar 2020 10:04:34 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Sebastian Moeller In-Reply-To: <875zesret5.fsf@toke.dk> Date: Wed, 25 Mar 2020 10:04:32 +0100 Cc: Aaron Wood , bloat Content-Transfer-Encoding: quoted-printable Message-Id: References: <875zesret5.fsf@toke.dk> To: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= X-Mailer: Apple Mail (2.3445.104.11) X-Provags-ID: V03:K1:0QltgmN6+6v7BjDMalq+2h6kgZ4/abnyhJhJAulehB3DV6yaUd0 OEgYmwnQDnLaTLpc3DbxDfFe6CcBZbDuEYwyGv5AkcCFT0uvHRNOd9wcrnudHXoDqTtOBSs xfXE8MmF45flNhgsGx9Etj0sr+EEMlGtVE7GTQ2vfsqZU41x+YuVdng6O4m6y5bzjQa2yrS k3IofNc7aMbfbz6LeH2yA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:Pul/Hid9NAM=:xmTOAcjowHuiv4eRYCP1Fq aWkEqtZzfVIh2sDIVsPDGnJGYwa3jCosLVpSNDoBQbVtJDIjrO8x8mVDs6Qv7DQZMrPFT3a+e odgcIu9kbuZQT2bQhq1vKjxmkoQQjGC3tCjlLBKCIzazIDu3nDtGaFXR8xS7rdFTfCkgt4+pD AyiHDshXnfgJaR0sZ3VYXYITjEeqrStBigZ8FF7JQ0+VTz4oLBcdcckfo6oIAID4HYR1pARv7 CaGIli9xznzspSqdJW2uVCJImjvvba46slXBD7PuBCpDkVtnpdj7hKYgV9FHhWHabZkmXPMth zWhSa+ToMVn9LW5VtthibcnfzRvo9pRDJIaDIoNdy3sbuBuQ+eDMUtIrLh8fxjiePQ8BjPjAa TmvA5Lk18d2dm5ouYMGOj0jbT5kYfB3VirOZMRCW5SBa0/nBgkdqyXgTtY1Zo48FMyKzzzNIA Tft2jDNYW2EID5wOG805QrwQBLp/R25rZ1UeJhfTX5g3dC9ku4jg9e5S2OYSZ+0uAbI5j5wxE 4NeCvmzEt4T0/umExkvqGITFqvAmUeTnG9s431+PDxt04Vf6VY3IFdtTtjCR6ZZ64IQ0xxolP yCSSZHuhD1Ch6gDQVbwoffSOPbN4mfBvqkYfWcKHiF5I+ux/I+w56Rw5kRXjBf3i8HRi+7lx5 ZgFFKWusaGm/AyPt18VCiJTN6lDKooat/mw8di1J++GrsOEpg4cvdrZy/qxG5FsAXcwtv7uGO xQfvqBnW14cot4wc6KOiqlPaz0YgJlH1lBzZZUTzHe3iuip743uqPjxSEyHF4phuyp4GGQZm6 UcLg9phFpAqpdg9Qq16cSl2PsBtIjpr1FpZ6uOm+dyNnzZlJsCs4AbmYZmIvQef4aKnrnCZjh ioLOwVCqamHKBPjHZ3aHTichg+Gs6SYI0ONGPZbYKdiTFamAFIAVW8/vEtw0VztNlcvqhv68M QE0/8YdCasa0SCqcFtYW4+H9Xjqfe87LrODX0U+1Yr88fk5RYbgZ1pAZleWJ3lBIL2ZNy2kVv p3ON4z/Me+kU1fNXJ4d9PSOOOdyWqA0V7djklVUpdxZLg1/1QzOxByjdaq7NKhdT6ioNxIMN/ eNZpaFKL4X+Q5U9LHr6NZw7d3oqZTwU69758THW2xv7cPnG+dSY7enRrvfZz++DGJxo58fi6M yUojcMYw9FDgnsqxUMT9Y6ytbD6Wngvch3xXvtPan05UYV1Q6DK69QM0y4vSjYWIqjCLEjTqe /eHJxDnxwZ0XQwP23 Subject: Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2020 09:04:41 -0000 Hi Toke, > On Mar 25, 2020, at 09:58, Toke H=C3=B8iland-J=C3=B8rgensen = wrote: >=20 > Aaron Wood writes: >=20 >> I recently upgraded service from 150up, 10dn Mbps to xfinity's = gigabit >> (with 35Mbps up) tier, and picked up a DOCSIS 3.1 modem to go with = it. >>=20 >> Flent test results are here: >> = https://burntchrome.blogspot.com/2020/03/bufferbloat-with-comcast-gigabit-= with.html >>=20 >> tl/dr; 1000ms of upstream bufferbloat >>=20 >> But it's DOCSIS 3.1, so why isn't PIE working? Theory: It's in = DOCSIS 3.0 >> upstream mode based on the status LEDs. Hopefully it will go away if = I can >> convince it to run in DOCSIS 3.1 mode. >=20 > I think that while PIE is "mandatory to implement" in DOCSIS 3.1, the > ISP still has to turn it on? So maybe yelling at them will work? (ha!) >=20 >> At the moment, however, my WRT1900AC isn't up to the task of dealing = with >> these sorts of downstream rates. >>=20 >> So I'm looking at the apu2, which from this post: >> = https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-s= qm-wireguard-and-openvpn/44724 >>=20 >> Will certainly get most of the way there. >=20 > My Turris Omnia is doing fine on my 1Gbps connection (although that > hardly suffers from bloat, so I'm not doing any shaping; did try it > though, and it has no problem with running CAKE at 1Gbps). Well, doing local network flent RRUL stress tests indicated that = my omnia (at that time with TOS4/Openwrt18) only allowed up to 500/500 = Mbps shaping with bi directionally saturating traffic with full = MTU-sized packets. So I undirectional CAKE at 1Gbps can work, but under = full load, I did not manage that, what did I wrong? Best Regards Sebastian >=20 > -Toke > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat