[174991] in North American Network Operators' Group
Re: Belkin Router issues this morning?
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue Oct 7 19:09:15 2014
X-Original-To: nanog@nanog.org
To: John Neiberger <jneiberger@gmail.com>
In-Reply-To: Your message of "Tue, 07 Oct 2014 16:27:16 -0600."
<CAOQYbjoYSnk561XXGvs1xxh0TmJuMGVfbc_HBAEv-MPj-rCODQ@mail.gmail.com>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 07 Oct 2014 19:08:57 -0400
Cc: Steve Atkins <steve@blighty.com>, "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--==_Exmh_1412723337_2562P
Content-Type: text/plain; charset=us-ascii
On Tue, 07 Oct 2014 16:27:16 -0600, John Neiberger said:
> Sounds like it might have been a DNS issue of some sort. The end result was
> that the customer routers couldn't reach their heartbeat server, which made
> them think they weren't on the net.
Seems like a dubious idea to equate "can't reach heartbeat server"
with "not on the net at all". At the very least, I'd add a second
clause "I have no reachable default route, and I must scream".
--==_Exmh_1412723337_2562P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001
iQIVAwUBVDRyiQdmEQWDXROgAQJvPhAAsVPzrFzjmao/nDB6nZguXP3Y4YZgvzjc
YIE7fkQw17h17ywqM7ESw/oOhUbWw9Ssez3g9kuwVj75y46qAlkCkMg9t1aw1AD+
rEM9VvSL9EhHQukZfOlp8w4ETql1jQ50qXt6geO525h5bjeJAuWNlmrH8/ejC+f5
2VUYB15PxLyo5pD80PKnwh5v0mo9pQhfuwf92e5Ss0jZANwQAhzYtOPgwGoLOF8r
dveD0G70C3A3NG2ab53KjzoOK9hcgZ7fsQybmaKTyhClJNhuedH3XXJZ9J4gA9iD
Hi3H3cMdkZeiS9sR50D+Egb+f/NKrsu7ghvPV4iL384+5vrE9j03IGaV0RNnQnLB
zSufAb8SRRH2NS7NDB6PLWIK6dpvAClSoEqV0EH0LwUMknGaQuo7WR0hSANer/BE
MnnmC3PLLP+pHMVU+65Qx+D+2GlFXqAiQdotid/sjEsf2J8SUEcvahWNkoRewQYa
8QLjD9qbZwD3ql1jes0HiKzqrSPAEDb0PWGB3NIpEBc2na9N8vn0Xkwo8NAFJOkB
0gigCEoUp15/hEtfHeNt7rnN75gNIvK6hF5iwCQsVhOG92PaZGZJ+9fHB+mx48ks
MoBmYHe43oeMaUfOrfxEWJaIVqtEjuRNtPfmK11wChtyAx3FFj0Qk0m7GbigO5Q8
63JG/sZhNHk=
=4ssE
-----END PGP SIGNATURE-----
--==_Exmh_1412723337_2562P--
