Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Personette <dperson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] notes on going for a stable release
Date: Tue, 14 Jan 2014 07:36:34 -0500	[thread overview]
Message-ID: <CAMybZqxSbHHmuKN_GLx15KtmDa8ysF=_dAixoR9BeSS-0_n2YA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6PZk_5FZbgq0U_K9CL=xE9ZP+-U09HwkwNaDREjj4fOw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3647 bytes --]

On Tue, Jan 14, 2014 at 1:07 AM, Dave Taht <dave.taht@gmail.com> wrote:

> ** Instruction traps
>
> The instruction trap problem has resurfaced on boot. It is unknown
> what triggers it. It doesn't happen very much after boot in my limited
> testing.
>
> The last time it bit me was on doing tests on a busy ipv6-enabled
> network where it thoroughly blew up the tests. (even when not doing
> ipv6 itself) It also made cerowrt unreliable.
>
> oot@davedesk:~# cd /sys/kernel/debug/mips/
> root@davedesk:/sys/kernel/debug/mips# cat unaligned_instructions
> 7884
>
> What values do you see, both on boot and after some uptime?
>
> For more details on how to actually fix the bug:
> http://www.bufferbloat.net/issues/419
>

I updated to the 3.10.26-1 build, so not much uptime. Also, I don't have my
IPv6 hurricane tunnel active ATM.

root@outpost:~# uname -a
Linux outpost 3.10.26 #1 Sun Jan 12 14:50:55 PST 2014 mips GNU/Linux
root@outpost:~# cat /sys/kernel/debug/mips/unaligned_instructions
0
root@outpost:~# uptime
 06:49:16 up 20:28,  load average: 0.00, 0.03, 0.04
root@outpost:~# dmesg | grep "checksum failed"
root@outpost:~#


> ** BCP38 compliance
> Cerowrt does not currently stop unknown rfc1918 addresses from going out
> ge00.
> ** Squash incoming diffserv bits
> many providers pee on the diffserv bits. It would be good to detect it
> and reset to BE incoming packets. (note: IPv6 is far less peed on.).
> There was a nice idea discussed last year on using conntrack to match
> incoming with outgoing diffserv bits.
>

I'd added this into my /etc/firewall.user. I'd be happy to work on adding
it into the official script if you would like. I'm a sysadmin, what
development skills I have are in scripting.


> ** SSL support for the configuration interfaces
> All the plumbing exists for this in cero, it just has to be made to
> work. the key generation routine needs to be fixed in uci-defaults and
> lighttpd config updated. It's embarrassing to not have SSL running.
>

If it's scripting and web server config, I'll work on this too.


> * Bufferbloat.net problems
> the bufferbloat.net servers are undermaintained and obsolete. I long
> ago swapped out my sysadmin and ruby skills for other things.
>
> ** huchra replacement (one disk currently crashed, the other going)
> In addition to running this mailing list this used to be 1/5th of the
> openwrt build cluster.
>
> lists needs to move to a virtual server ASAP.
>
> openwrt could really use a good build cluster. been running most of
> theirs now for a couple years, out of machines pulled from the junk
> bin.
>
> ** Web Site updates
>    the redmine implementation on bufferbloat.net has been overrrun by
> spam and I stopped
>    accepting new contributors that didn't contact me also via email
>    long ago.
>
>    given how hard it would be to update the present website, perhaps
> moving to cerowrt.org
>    on a virtual server will be simpler.
>

This I can work on now, if you like, I can spin up a Digital Ocean VM that
should be able to run a mailing list with no problems. Getting Postfix
setup should be a snap, I'm not sure what else is needed for the mailing
list, but we can discuss it off the mailing list. Did you want a new name
or keep huchra for the VM? Once it's up, getting a list of needed software
from huchra, certs, and the data can be synced over, do some testing, then
the DNS A and MX records can be updated.

Hmm, just saw that Digital Ocean still doesn't have IPv6 yet. Will that be
a problem? Any other suggestions for hosting it? I've used them for several
little projects, they have a good interface and rates, IMHO. Thanks.

-- 
David P.

[-- Attachment #2: Type: text/html, Size: 5052 bytes --]

  parent reply	other threads:[~2014-01-14 12:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  6:07 Dave Taht
2014-01-14  8:37 ` Christopher Robin
2014-01-14  9:44   ` Toke Høiland-Jørgensen
2014-01-14 12:51     ` David Personette
2014-01-14 13:20       ` Rich Brown
2014-01-14 15:30         ` Dave Taht
2014-01-16  3:20         ` Theodore Ts'o
2014-01-15 15:18   ` Dave Taht
2014-01-14 12:10 ` Juergen Botz
2014-01-14 15:10   ` Dave Taht
2014-01-14 12:36 ` David Personette [this message]
2014-01-15  4:11   ` Dave Taht
     [not found]     ` <CAMybZqzs9ES9G23ke-PjU759wxbQNMytYa4EHmv0H8HqpPwwPQ@mail.gmail.com>
2014-01-15 14:47       ` Dave Taht
2014-01-15  0:30 ` David Lang
2014-01-15 17:31 ` Jim Reisert AD1C
2014-01-20 15:00 ` Maciej Soltysiak
2014-01-20 15:15   ` [Cerowrt-devel] notes on going for a stable release/replacement router Rich Brown

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='CAMybZqxSbHHmuKN_GLx15KtmDa8ysF=_dAixoR9BeSS-0_n2YA@mail.gmail.com' \
    --to=dperson@gmail.com \
    --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