Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement
Date: Sun, 30 Mar 2014 18:03:35 -0400	[thread overview]
Message-ID: <18138.1396217015@sandelman.ca> (raw)
In-Reply-To: <CAA93jw7wgA4Z4OUq3NCn0Ww10JBa2EHja2yumryp+aCTgBUO5w@mail.gmail.com>


Dave Taht <dave.taht@gmail.com> wrote:
    >> Dave Taht <dave.taht@gmail.com> wrote: >> that is just fine.  I don't
    >> expect 24-ports of GbE.  >> (I was expecting that cisco switch to do
    >> that... sadly no lost packets >> on a $100 unmanaged FE switch...)
    >> 
    >> > I started looking at the edgerouter LTE and related boxes again.  >
    >> Does anyone else have one?
    >> 
    >> I have ordered the 5-port POE one.

    > Does that support gigabit POE?

Unclear...  web site says:
            10/100/1000 Ethernet ports that support 24V or 48V PoE output
            with software-selectable voltage control* 

    >> My understanding is that it runs Vyatta. I would suspect that given
    >> that the

    > It is running an older version of vyatta, yes.

okay.

    >> edgerouter is MIPS, and has "special hardware", that VyOS might not
    >> have the

    > Not sure what the offloads buy you, except added latency. They are
    > easily disabled for testing various qdiscs... (can't remember the
    > command offhand)

    >> right support for that hardware.  I'm going to talk to Ubiquity if I
    >> can on Monday.  It might not make sense to run *Wrt on this device,
    >> not sure.

    > There is a pretty modern looking up-to-date build of openwrt for the
    > edgerouter, using 3.10, and so on. I am told however, that there are
    > some problems with the toolchain, which show up when you try to use
    > iptables. Haven't tried it myself (my edgerouter is 60km away), and
    > don't know how to flash openwrt onto it in the first place.

okay.

    > the current edgerouter firmware (v.1.4.1) is based on 3.4.23, and has
    > all the bugs in the 3.4 series.

    > I backported fq_codel and the latest flow hashing stuff to that
    > version; patch 0013 is a little problematic as yet:

why did you backport, rather than move the kernel forward?
Are there custom pieces in 3.4 which need to be forward ported?

    > http://snapon.lab.bufferbloat.net/~cero2/edgerouter-fq_codel-patches/

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

  reply	other threads:[~2014-03-30 22:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.02.1403251259390.747@uplift.swm.pp.se>
2014-03-25 15:16 ` Dave Taht
2014-03-26 22:11   ` David Lang
2014-03-27 12:50     ` Aaron Wood
2014-03-27 14:39       ` David Lang
2014-03-28  8:36         ` Mikael Abrahamsson
2014-03-28  9:33           ` Sebastian Moeller
2014-03-28 13:30           ` Aaron Wood
2014-03-28 18:40           ` Michael Richardson
2014-03-28 19:39             ` Dave Taht
2014-03-28 21:01               ` Aaron Wood
2014-03-29 21:08               ` Michael Richardson
2014-03-29 21:25                 ` Dave Taht
2014-03-30 22:03                   ` Michael Richardson [this message]
2014-03-30 22:10                     ` Dave Taht
2014-03-28 19:14           ` Michael Richardson
2014-03-29 19:27 Martin Bailey
2014-03-29 19:52 ` Dave Taht
2014-03-29 19:56 ` Dave Taht
2014-03-29 20:19   ` Martin Bailey

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=18138.1396217015@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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