| |
Matthew Miller wrote:
> Larry Pieniazek <lar@voyager.net> wrote:
> > > 8 206.132.253.97 16.484 ms 9.011 ms 9.696 ms
> > > 9 206.132.151.22 148.602 ms 148.816 ms 161.058 ms
> Most likely one of the routers is overloaded -- if one checks the dns for the
> gateways at 8 & 9, one finds the phrases "155M" and "622M", which seems like
> a lot of bandwidth to me.
What tool do you use for that? whois comes up with a blank, and host (1) just
says "pos3-1-155M.cr1.JFK.globalcenter.net".
Anyway, my packets don't even see that network -- they get stuck somewhere
between:
6 <10 ms 10 ms <10 ms 194.ATM3-0.TR2.SLT3.ALTER.NET [146.188.224.22]
7 51 ms 50 ms 70 ms 113.ATM6-0.TR2.DCA1.ALTER.NET [146.188.137.213]
Cheers,
- jsproat
1. My copy anyway -- it's entirely possible that since I'm on Win32, I have a
sub-standard set of inet tools. :-,
--
Jeremy H. Sproat <jsproat@io.com> ~~~ http://www.io.com/~jsproat/
Jeremy: "Hi, my name is Jeremy Sproat, and I'm a...Slashdot Lemming."
All: "Hi, Jeremy."
|
|
Message has 1 Reply:
Message is in Reply To:
42 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
