From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <white.phoenix@gmail.com>
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com
	[IPv6:2607:f8b0:4002:c01::22e])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client CN "smtp.gmail.com",
	Issuer "Google Internet Authority G2" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 477E121F181
	for <cerowrt-devel@lists.bufferbloat.net>;
	Wed, 19 Mar 2014 13:21:41 -0700 (PDT)
Received: by mail-yh0-f46.google.com with SMTP id b6so9187558yha.5
	for <cerowrt-devel@lists.bufferbloat.net>;
	Wed, 19 Mar 2014 13:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc:content-type;
	bh=qomJZZCJZM3yT0pewxOjmGQnVnsck437caXVxsYgGcQ=;
	b=VSmtfYDGC3qFxEoA38p+KjEvcQE8TNH0cnrYVBFLBlBIRKkUngD4YLbf1R5Tguz8CP
	W0Jbu43A9yhXRIhLbNxForD+LouFZVO4iBKJ9v56Jvg7/eWk0A3VrdBoqo4gI/88Bqwa
	Edl9iAMti4UB/wZ6MivC0qSlavzt9l53jW2MhAkObbD6+OYIRWBl9t12qTqE9SW5NiyY
	G/GTpof0/DlPGEnFqwSReffzA8debkmDZGGAnvewOLBX67z7OgU11mYlmu15h96Wqtwx
	ZzW6+SQZv3BAEWKxmsCQjH8qT7sHF4XAAu1v2MCzzAYwlQmlURcDXF4nkJNHNDXIKGFn
	BA+g==
X-Received: by 10.236.126.81 with SMTP id a57mr13645000yhi.95.1395260500296;
	Wed, 19 Mar 2014 13:21:40 -0700 (PDT)
MIME-Version: 1.0
Sender: white.phoenix@gmail.com
Received: by 10.170.114.200 with HTTP; Wed, 19 Mar 2014 13:21:10 -0700 (PDT)
In-Reply-To: <000901cf43ae$729399c0$57bacd40$@com>
References: <mailman.13652.1395208661.1815.cerowrt-devel@lists.bufferbloat.net>
	<00ef01cf4370$0c5bba90$25132fb0$@com>
	<CAA93jw55Mj28q8eNPtV22mygPFgPs==458pQTHzU+KjNEPR=xA@mail.gmail.com>
	<000901cf43ae$729399c0$57bacd40$@com>
From: Aristar <LeetMiniWheat@gmail.com>
Date: Wed, 19 Mar 2014 16:21:10 -0400
X-Google-Sender-Auth: LSnoaIfPoiCcR2rC3LBY7wnmDnE
Message-ID: <CAGHZhqE_ykhYZQOYQt45StzwZZT0B-vDgiwpPuuL0r0p+zhCbw@mail.gmail.com>
To: Frits Riep <riep@riepnet.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Verizon FIOS - How to use CeroWRT directly with
 interactive TV
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 20:21:41 -0000

On Wed, Mar 19, 2014 at 4:04 PM, Frits Riep <riep@riepnet.com> wrote:

> At our office we have a 30 mb/s down 30 mb/s up Verizon FIOS and we
> certainly get bufferbloat on the download of Speedtest using a Sonicwall
> TZ200 per the results below.
>
> Reply from 74.125.226.78: bytes=32 time=17ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=18ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=18ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=19ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=17ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=26ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=25ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=59ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=102ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=89ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=107ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=96ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=85ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=72ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=90ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=105ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=99ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=100ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=70ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=82ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=98ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=67ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=16ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=16ms TTL=251
> Reply from 74.125.226.78: bytes=32 time=15ms TTL=251
>
> On the Netalyzr results, while it only shows the speeds as greater than 20
> mb/s, there are buffering results, and these are much better using CeroWRT
> than using another router on this connection and as far as I can tell the
> buffering numbers are valid and repeatable, so I do believe that bufferbloat
> can be an issue even on 80 mb/s download connections.
>

I think a lot of Verizon's network in general has some major
bufferbloat especially on their GPON or BPON hubs. I occasionally get
1000+ pings from my very first hop after my router.