[176536] in North American Network Operators' Group
Re: Comcast IPv6 issues..?
daemon@ATHENA.MIT.EDU (Stephen Frost)
Wed Dec 3 15:40:41 2014
X-Original-To: nanog@nanog.org
Date: Wed, 3 Dec 2014 15:40:34 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Steve Meuse <smeuse@mara.org>
In-Reply-To: <CA+3sbiP4gxEyrFGJjtt398Tbyruu=oe3p9e0M8svm6rEXATh3A@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--1VtFtf1bAEcuptAG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Steve Meuse (smeuse@mara.org) wrote:
> It's likely a reverse DNS error. If you look at the latency, it's within
> range of the previous hops.
Still curious that the systems (IPv6 addresses) are changing too.. It's
not like it's the same route but just different rDNS results. It's also
quite a bit of latency between he.net and Comcast. Also seeing ~20%
packet loss to systems in Comcast and ~15% packet loss end-to-end.
Certainly seems like there's something unhappy there, but I'll just keep
an eye on it.
Thanks!
Stephen
--1VtFtf1bAEcuptAG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJUf3VCAAoJEO1sijiDR2RVA/IP/R8UisFQ3CJFQLEbN1J/Q2a1
yfaiH8PHC1uiFRf15b3L3Ls1kR1E/7wkxxy8w84cNkueeJpRDW/ysRXSN3T9rHfj
2tgwBoUedeyRGoLCq80e9wvotTYUHWUlpLmni7cGdDb7qPDXQ4Le3+wN5pCNj7Rj
k1syW3DHCWtoKMmLnleE3PC12OOqTZz7YnVASH6ZgiT+LMUF5PABBAYcXAH2NLBO
NuJto+cRniezpii9USHe4STI1dO2iACP1B35FqKtlAozR4mTmEnThNx+JRAnEbRv
HxSOH4zrbWgjAIiHHvn09hIUhdVKKiSi1eunTUbmlH+iL1Em9sRjW1CLgcJapaxl
4ElXik08mv6s+tWD/+PXp+at3+6YcrHRRwzOnxMuWEmoN55gfzyYNBmxUsBrtHKx
h/4RsuAEo9VCfSSiZ8ZDHjMA9DiBhqLD5wDA3ZGWkUr3Rvy2KuWWsEFWM3ccYG7v
U3225WB7yBlLJYHobSlZGA4EyZVj5V0FdiDS5webU2oXCGXRl9vdHVY+xxYq5ibu
H2Gd5qpTDhFtDl6XXUF5brK8wmbDXAAIduVwNlUfAmajJ80mgMBC6Ew5/dgCoaSB
vhgD6BHLiQNBnsOebW6cAddv9yZhOfCDF/jFirtpFd5kiFyIRoFa0W3f0if+D2c7
3JEAGxJHRSRcRSJgZoVS
=XNta
-----END PGP SIGNATURE-----
--1VtFtf1bAEcuptAG--
