From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-s66.mailgun.info (mail-s66.mailgun.info [184.173.153.194]) (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 B95D63B2A4 for ; Thu, 28 Mar 2019 07:00:58 -0400 (EDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=flamingpc.com; q=dns/txt; s=pic; t=1553770858; h=Content-Type: To: Subject: Message-ID: Date: From: MIME-Version: Sender; bh=L7Gx2HfTyjiknS4K/nvMiTF0xy51EbCpdpYXZxWfIGU=; b=hGrtyeDq/7liyTKJTsQWUGJEJglqKFr3Y2JlapzkX602hnuaKOipWxrTj+JHokSPSb/lpX1p Kge9EJOqJZvgqd0j3ReRjKFEKZJrCMNm1ccpgXvvVhg9+VHDlOjFItATyOo/aVE6IMTEwKkx /bldj9wksZdtavzkuqx8y8FOTuk= X-Mailgun-Sending-Ip: 184.173.153.194 X-Mailgun-Sid: WyJiMjA5OSIsICJibG9hdEBsaXN0cy5idWZmZXJibG9hdC5uZXQiLCAiNjY0ODllNyJd Sender: bufferbloat@flamingpc.com Received: from mail-vs1-f51.google.com (mail-vs1-f51.google.com [209.85.217.51]) by mxa.mailgun.org with ESMTP id 5c9ca96a.7fba93829070-smtp-out-n03; Thu, 28 Mar 2019 11:00:58 -0000 (UTC) Received: by mail-vs1-f51.google.com with SMTP id g187so11836799vsc.8 for ; Thu, 28 Mar 2019 04:00:58 -0700 (PDT) X-Gm-Message-State: APjAAAU8WenpFyfHecLNxemk5FNgLqq00Jfa1WEu0USj6EysrfdTUah6 r2mFcGVcBweWVHfpy4jYRG/pJaEyQFQVogjCnyg= X-Google-Smtp-Source: APXvYqwouZaef5ukHbkhXldoY0Tubc46Xdfy+UjtSu4E5jRDhyIr4nrz8UoIdyugHgh41dWEpcsfwl1GzNBpC/oBJM4= X-Received: by 2002:a67:e30a:: with SMTP id j10mr2836349vsf.103.1553770857264; Thu, 28 Mar 2019 04:00:57 -0700 (PDT) MIME-Version: 1.0 From: cloneman Date: Thu, 28 Mar 2019 07:00:45 -0400 X-Gmail-Original-Message-ID: Message-ID: To: bloat Content-Type: multipart/alternative; boundary="000000000000027b8e0585257880" Subject: [Bloat] unfixable bloat on Cable modem CODA-4680 (puma 7) 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: Thu, 28 Mar 2019 11:00:58 -0000 --000000000000027b8e0585257880 Content-Type: text/plain; charset="UTF-8" I'm getting a weird problem with this new modem , it's Docsis 3.1 latency/jitter measured via ping is about ~300ms during download pressure of 3 http transfers. The latency doesn't appear on synthetic bufferbloat benchmarks, though. (dslreports ; 20ms ("A") question: trying to figure out why I'm seeing this particular behavior, and determine if it'd a real issue or just an anomalie with ICMP traffic I've not seen ping do this with other modems. Perhaps I need to try some other traffic generation/ capture tools? --000000000000027b8e0585257880 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm getting a weird problem with this new modem , it&= #39;s Docsis 3.1

latency/jitte= r measured via ping is about ~300ms during download pressure of 3 http tran= sfers. The latency doesn't appear on synthetic bufferbloat benchmarks, = though. (dslreports ; 20ms ("A")

question: trying to figure out why I'm seeing this p= articular behavior, and determine if it'd a real issue or just an anoma= lie with ICMP traffic

I&= #39;ve not seen ping do this with other modems.=C2=A0

Perhaps I need to try some other traffic gene= ration/ capture=C2=A0 tools?=C2=A0


--000000000000027b8e0585257880--