Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
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 14:01:48 -0400	[thread overview]
Message-ID: <42483.1411840908@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 27 Sep 2014 10:23:13 -0700." <CAA93jw5UWGgdqe0Nz+i2oKq0aS+-TQTXSpnjW841GQfD_CTeQA@mail.gmail.com>

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

On Sat, 27 Sep 2014 10:23:13 -0700, Dave Taht said:
> I have thus far been delighted in the stability of 3.10.50-1, how's it
> working for all of you?

I installed it when it came out, and not a blip of trouble until I
mistakenly rebooted it yesterday when I thought it had forgotten how
to rout to other subnets (I couldn't reach my Raspberry Pi which has
a wired connection from my laptop on wireless).  Turned out the *real*
culprit was our corporate VPN handing me a route for 172.16/12 and no
specific route for the other local subnets.  Comcast native IPv6 working
fine.

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2014-09-27 18:01 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 [this message]
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=42483.1411840908@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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