From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] how's everybody's uptime?
Date: Sat, 27 Sep 2014 10:47:50 -0700 [thread overview]
Message-ID: <CALQXh-Pmu=o9dPqMR7Y+Vtf4AV97sTrCdn+TEA4R048QWxUDRQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5UWGgdqe0Nz+i2oKq0aS+-TQTXSpnjW841GQfD_CTeQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
I'm up to 12 days at this point, but it was longer (a month?) before I did
some re-arranging of things and needed to unplug the unit.
I have an AppleTV that's wired, and all the computers are on wifi, so we
end up stressing the mdns a fair bit. It seems solid, although all the
devices get confused about having other devices using their name, and
increment theirs (the Apple TV is up to 1344).
Everything seems to be going well, though. But it's all still just ipv4 (I
need to deal with comcast and getting their router into bridge mode, it's
not just a modem at 192.168.100.1, it's a full blown router).
-Aaron
On Sat, Sep 27, 2014 at 10:23 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I have thus far been delighted in the stability of 3.10.50-1, how's it
> working for all of you?
>
> In particular I am curious about how well native and hurricane
> electric ipv6 support is working,
> dns and mdns service, and those of you that are routing, how well, all
> that is holding up?
>
> --
> Dave Täht
>
> https://www.bufferbloat.net/projects/make-wifi-fast
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2337 bytes --]
next prev parent reply other threads:[~2014-09-27 17:47 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 [this message]
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
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='CALQXh-Pmu=o9dPqMR7Y+Vtf4AV97sTrCdn+TEA4R048QWxUDRQ@mail.gmail.com' \
--to=woody77@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