An e-mail I just sent--and copied to our entire systems team and… - A Suburbs Boy Living a Country Life
[My Flickr Photos]
|Date:||November 23rd, 2004 03:05 pm (UTC)|| |
Re: This morning at our house
Thanks, RS...That's a very cogent summary. Of course, it doesn't explain the quantum jump from 1500 to 1700...By the way, though MCI claims to have made no changes, we are now seeing ~0% loss with >= 1500 byte packets.
Thanks for the explanation of the doubling of the loss rate in addition to increased latency.
We are, of course pinging through several routers--but because it's a managed MCI VPN we don't even see them, e.g.:
Tracing route to 10.0.2.100 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router.bfs.hpti.com [10.0.10.1]
2 1 ms 1 ms 1 ms router-mci.bfs.hpti.com [10.0.10.254]
3 46 ms 46 ms 50 ms 18.104.22.168
4 84 ms 101 ms 101 ms 10.0.2.100
1st hop, our local router (completely superfluous, but our network guy here keeps it "so we can set up a back-up dial-up path to the network if MCI goes down for a long time."--my thinking is that we could keep that in cold storage, not make it the default gateway, and crack it out for that purpose if such a disaster occurs...but that's just me); 2nd hop our router; 3rd hop === 10.0.2.99's "public face"; 4th hop == node on the other side of the router.
Note that the 2nd hop is in Picatinny, the 3rd hop is in Arlington. MCI has hidden the path between from us. (This is by design--we're not supposed to care, so long as the packets get there, and our network traffic is supposed to be secure and partitioned from everyone else's).
Okay, back to work for me.