Re: What a strange route (The DoD inside)!

On Mon, 03 Apr 2006 09:52:06 CDT, Bob Radvanovsky said:
> May this was an isolated incident?

>  3  atm008.edge1.chi.megapath.net (216.36.100.1)  30.781 ms  18.686 ms  30.491 ms

>  6  ae-1-55.bbr1.Chicago1.Level3.net (4.68.101.129)  20.222 ms ae-1-53.bbr1.Chicago1.Level3.net (4.68.101.65)  23.849 ms  20.018 ms

> 13  194.244.2.114 (194.244.2.114)  145.201 ms  147.555 ms  143.591 ms
> 14  * * *
> 15  * * *

More likely, the fact that your packets went via megapath.net and level3.net
means they never transited the fastres.net/fastwebnet.it links that are the
problem.  The paths are totally divergent before your hop 13 and their hop 17
(although your hop 12 and their hop 16 are both in 194.20/16, so likely on
the same provider - probably 2 different routers at different sites but
owned by the same provider).

Similar to somebody who says "I saw something weird on I-95 North heading from
Richmond VA (south of Washington) to Washington DC" - you've replied with the
euqivalent of "There's nothing weird on I-270 coming into Washington from
Frederick MD (northwest of Washington".

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFEMVuFcC3lWbTT17ARAiqoAJ0bCdnSg5GWivIMIB5Zz7xp+7Yx0QCgjWJC
o7s/zdzmv2465hn+BRPnV4w=
=CykR
-----END PGP SIGNATURE-----