Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Daniel Ashton <Daniel@ashtonfam.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] FiOS Quantum Gateway?
Date: Sat, 15 Nov 2014 17:41:07 -0800	[thread overview]
Message-ID: <CAA93jw7Y_WTi_7MQDcpCgsvQCr_CUrGaH298cF0_Ev=bWasEGw@mail.gmail.com> (raw)
In-Reply-To: <5457C22C.5010604@ashtonfam.org>

From looking at their source tarball supplied off that link, they are
shipping linux 3.4.69, which is the stable linux kernel release prior
to fq_codel (and there were many tweaks all over the system through
3.10 that were often important). .69 is pretty recent.

There is a paucity of patches, no indication of what firmware drivers
or even what cpu is in the box, etc. (they DO supply a .config file
for arm). I would certainly like it if someone were to purchase and
tear down this product... it would of course, be awesome, if the
supplied kernel just worked as is but I am as usual pessimistic.

They are promising github support, so perhaps they will start doing
development more openly.

Judging from their marketing, IPv6 support is still irrelevant to verizon.

It has never really been clear to me where exactly the bandwidth rates
and limits were set in a verizon FIOS system, I have generally seen
very good performance on the uplink, and buffering on the downlink
seemingly set for 300mbit (when run at 25mbit). So at least on one
FIOS box I have used, only downlink shaping was needed.


On Mon, Nov 3, 2014 at 9:58 AM, Daniel Ashton <Daniel@ashtonfam.org> wrote:
>
>
> Anybody know what this thing is that Verizon is offering as their new
> Quantum router?
>     http://campaign.verizon.com/fiosquantumgateway/
>
> If it really has more horsepower and coverage, it would be nice to have
> CeroWRT running on it.
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

  parent reply	other threads:[~2014-11-16  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.129825.1413898449.1815.cerowrt-devel@lists.bufferbloat.net>
2014-11-03 17:58 ` Daniel Ashton
2014-11-14  7:33   ` Outback Dingo
2014-11-14  7:51     ` Outback Dingo
2014-11-16  1:41   ` Dave Taht [this message]
2014-11-16  1:59     ` Dave Taht
2015-01-04  2:22     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7Y_WTi_7MQDcpCgsvQCr_CUrGaH298cF0_Ev=bWasEGw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Daniel@ashtonfam.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox