Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] "Lupin undeclared"?
Date: Sat, 25 Jul 2015 14:48:56 +0200	[thread overview]
Message-ID: <CAA93jw5PzCyiWuOjw2gXm3EWbJr_i7aw_84RYmpm5MEipNCqhA@mail.gmail.com> (raw)
In-Reply-To: <559FE735.9000106@gmail.com>

"lupin undeclared" is a build I managed to deploy at the campground
campus to about 8 of the 30 or so routers, including a few critical
paths. So far it is working spectacularly well in deployment there -
no forced reboots, aps, routing, dnssec, source specific stuff,
minstrel-blues, minstrel-variance... even cake.

root@pool2:~# uptime

 05:40:49 up 14 days, 22 min,  load average: 0.15, 0.07, 0.05

But I chickened out on dragging ipv6 to the pool. (5 hops)

Anyway cake is working as well as it can on wifi, running on a
picostation, I do not see any memory growth, it drops and marks...

http://pastebin.com/wbcXuNFM

qdisc cake 8004: root refcnt 5 unlimited diffserv4 flows raw
 Sent 107577100738 bytes 79678911 pkt (dropped 152068, overlimits 0
requeues 757808)
 backlog 0b 0p requeues 757808

and I guess we have to improve the statistics generated by tc to use
"k" and "m" to keep the cake columns aligned.

I am keeping detailed statistics on this portion of the network while
I am away and trying to design more.

I certainly did not intend for others to try these builds all that much.

My goal in life for the lupin build was to have something that did not
crash. Ever. It is a pita to climb trees and reflash the firmware
where these core wifi routers are placed.

It is kind of my hope to get out a new build during battlemesh or
shortly thereafter, but I plan to stick with this one for battlemesh.
Would like to sink some time into the ac1200...

  parent reply	other threads:[~2015-07-25 12:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 11:13 [Cerowrt-devel] Correct syntax for cake commands and atm issues Fred Stratton
2015-07-10 12:57 ` Jonathan Morton
2015-07-10 13:11   ` Fred Stratton
2015-07-10 13:40     ` Jonathan Morton
2015-07-10 14:52   ` Fred Stratton
2015-07-10 15:16     ` [Cerowrt-devel] "Lupin undeclared"? Rich Brown
2015-07-10 15:39       ` Alan Jenkins
2015-07-10 23:16         ` Rich Brown
2015-07-25 12:48         ` Dave Taht [this message]
2015-07-10 15:19     ` [Cerowrt-devel] Correct syntax for cake commands and atm issues Alan Jenkins
2015-07-10 15:48       ` Fred Stratton
2015-07-10 18:25       ` Fred Stratton
2015-07-10 18:46         ` Sebastian Moeller
2015-07-10 19:14           ` Fred Stratton
2015-07-10 19:15             ` Dave Taht
2015-07-10 19:18             ` Jonathan Morton
2015-07-10 19:30               ` Sebastian Moeller
2015-07-10 19:27             ` Sebastian Moeller
2015-07-10 19:34           ` Fred Stratton
2015-07-10 19:40             ` Sebastian Moeller
2015-07-10 19:45               ` Fred Stratton
2015-07-10 19:49                 ` Alan Jenkins
2015-07-10 19:50                 ` Sebastian Moeller
2015-07-10 20:07                   ` Fred Stratton
2015-07-10 20:12                     ` Sebastian Moeller
2015-07-10 20:24                       ` Fred Stratton
2015-07-10 20:34                         ` Sebastian Moeller
2015-07-10 19:41             ` Alan Jenkins
2015-07-10 19:43               ` Sebastian Moeller
2015-07-10 19:17         ` Alan Jenkins

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=CAA93jw5PzCyiWuOjw2gXm3EWbJr_i7aw_84RYmpm5MEipNCqhA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=alan.christopher.jenkins@gmail.com \
    --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