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 <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWRT and "FTTN" 50/10 VDSL2 (aka "FIBE")
Date: Mon, 30 Jun 2014 09:24:09 -0400	[thread overview]
Message-ID: <29573.1404134649@sandelman.ca> (raw)
In-Reply-To: <CAA93jw6sad1Zai9Fcjs+=cF=3rtk8A0mgRojQ0ajB1UsT1=CbA@mail.gmail.com>


Dave Taht <dave.taht@gmail.com> wrote:
    > The edgerouter (which has fq_codel in their 1.5 firmware release),
    > doesn't.

Yes, I have one, and I've been thinking it might be a better choice for me.

    > (and I haven't got around to booting an openwrt version on it, their firmware
    > is 3.4 based)

good to know.

    > That said I am seeing stuff that indicates inbound htb is increasingly
    > inaccurate on both products starting at about 20 mbit. (I had long
    > assumed before now that it was a cpu limitation as I don't see this on
    > x86) The 36mbit number you got matches mine, try increasing the rate
    > limit to 64mbits and see what happens.

I'll try that today.

    > Also, please measure the bloat you get on the openrg without sqm.... I
    > would hope the downstream bloat is less horrible than cable modems.

Bell Canada and nortel ATM equipment is involved.

    >> connection, but agreed to swap my IPv4/25 for an IPv4/28.
    >> I moved all my IPv4 to traditional NAT'ed, IPv6 all around, and /32
    >> routed the IPv4 to the various machines that actually need it.

    > nifty. When I get a /29 from comcast I don't have that ability, I think.
    > did you do that via proxy arp, or did they give you an ipv4 gateway
    > and routed the /28 ?

v4 gateway and routed /28.

    >> My PPPoE interface doesn't come up on it's own.  What is the "@ge00"
    >> part about?  I'm doing it in /etc/rc.local, which has all sorts of
    >> problems, including failing to include the pppoe-* interface into the
    >> iptables, etc.

    > regrettably how pppoe works is a mystery to me. I'd nuke the @ge00 and
    > try creating the pppoe interface from the gui for a start.

I went through that... it's all there. Netifd just ignores it.

    >> At this point my guess is that netifd has some kind of limit on the number of
    >> interfaces it will bring up.  I have 27 interfaces in my the ifconfig,

    > Well there are other hard limits - for example ifb's number is created by
    > a line in /etc/modules.d/ (ifb numifbs=0)

okay, I'll try making that zero and see if that makes netifd happier.

    >> including the 8 "ifbX" ones, the tun,tap, and my VLANs ("se00.XX") and the
    >> like.  Maybe the number is around 16... I have been looking at netifd source,
    >> and I don't see any obvious struct interfaces[16] or something like that.

    > You definately aren't a typical user.

    >> Is there a way to enable debugging on netifd?  The -d option to it?
    >> The /etc/rc.common stuff is... a bit impenetrable to me...

    > Hit #openwrt-devel for questions - netifd is a rather complex state machine.

I'll try there.
There used to be images/nightlies of barrier breaker, but I can't find them
anymore.  I have two authenticate 54GLs that I want to upgrade...

--
]               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    [


  parent reply	other threads:[~2014-06-30 13:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 22:48 Michael Richardson
2014-06-27 19:37 ` Dave Taht
2014-06-27 20:15   ` Dave Taht
2014-06-30 15:35     ` Michael Richardson
2014-06-30 15:59       ` Dave Taht
2014-06-29  8:33   ` Baptiste Jonglez
2014-06-29 14:00     ` dpreed
2014-06-30 13:24   ` Michael Richardson [this message]
2014-06-30 13:55     ` Sebastian Moeller
2014-06-30 15:37       ` Michael Richardson
2014-06-30 19:17         ` Sebastian Moeller
2014-07-02 20:45           ` Michael Richardson
2014-07-03  9:39             ` Sebastian Moeller

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=29573.1404134649@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