Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] how's everybody's uptime?
Date: Tue, 30 Sep 2014 22:20:47 -0700	[thread overview]
Message-ID: <CAA93jw5POeUyWP9XvvfSEqS6L0dqvWxUm0Qr6PDdhWe+s+khZw@mail.gmail.com> (raw)
In-Reply-To: <87lhp4540a.fsf@toke.dk>

Could y'all check your instruction traps?

Also check for space on flash periodically. Hopefully we're not
writing flash anywhere, either.

I note that once upon a time we had a dhcpv6 bug that only struck
every 55 days, and if we get past that point,
we're finally in stable territory...

... except for all the little bugs like pim that have cropped up.


On Sun, Sep 28, 2014 at 5:22 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave.taht@gmail.com> writes:
>
>> I have thus far been delighted in the stability of 3.10.50-1, how's it
>> working for all of you?
>
> Very good. Two main gateways running tunnelled IPv6 and authoritative
> DNS; one with unencrypted wifi and no guest network, another with
> Freeradius and 802.11i authentication on the encrypted network. Both
> running without issue (other than what I've caused myself by tinkering)
> for ~50 days.
>
> Also, the second box distributes routes to a secondary router over
> babel, which is also very stable; including automatic failover when the
> wireless bridge between the buildings fails (which again mostly happens
> when I tinker with it...). Bridging the wifi interfaces to a secondary
> router with VLAN interconnect between the two routes also works well.
>
> All in all, very happy with the stability of this release and quite
> impressed with the feature set. Big thumbs up! :)
>
> -Toke



-- 
Dave Täht

https://www.bufferbloat.net/projects/make-wifi-fast

  reply	other threads:[~2014-10-01  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27 17:23 Dave Taht
2014-09-27 17:47 ` Aaron Wood
2014-09-27 17:51 ` Jim Gettys
2014-09-27 18:01 ` Valdis.Kletnieks
2014-09-28  0:51 ` Rich Brown
2014-09-28  1:01 ` William Katsak
2014-09-28  9:45 ` Sebastian Moeller
2015-02-06 11:04   ` Sebastian Moeller
2014-09-28 11:48 ` Neil Shepperd
2014-09-28 12:22 ` Toke Høiland-Jørgensen
2014-10-01  5:20   ` Dave Taht [this message]
2014-10-01  7:57     ` Keith Duthie
2014-11-08  5:33     ` Aaron Wood
2014-11-09 18:27       ` Luke Hamburg
2014-10-01 12:37 ` Richard Weait
2014-11-06 15:45   ` leetminiwheat
2014-11-08 12:08     ` 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=CAA93jw5POeUyWP9XvvfSEqS6L0dqvWxUm0Qr6PDdhWe+s+khZw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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