Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Steven Barth <cyrus@openwrt.org>
To: David Lang <david@lang.hm>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] anyone have real info on the google router?
Date: Wed, 19 Aug 2015 20:49:28 +0200	[thread overview]
Message-ID: <E971707D-606F-414E-A06D-5555069054F2@openwrt.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1508191054030.10162@nftneq.ynat.uz>




>It's all Linux under the covers, so there's probably far less
>reinventing than 
>you think.

The kernel is the least of your issues. Try finding a halfway decent network management daemon aimed at routers that handles v6 potentially all sorts of tunnels, properly integrates firewall routing qos etc.


      parent reply	other threads:[~2015-08-19 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 19:31 David Lang
2015-08-19  1:57 ` Jim Gettys
2015-08-19  4:16   ` David Lang
2015-08-19  6:02     ` Mikael Abrahamsson
2015-08-19  9:47   ` Steven Barth
2015-08-19 17:55     ` David Lang
2015-08-19 18:10       ` Mikael Abrahamsson
2015-08-19 18:49       ` Steven Barth [this message]

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=E971707D-606F-414E-A06D-5555069054F2@openwrt.org \
    --to=cyrus@openwrt.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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