Re: traceroute giles.striker.ottawa.on.ca
> Is anyone more that me have this problem?
> It's just not workable... :)
> I'd started with gmp2/ssh/wget/tetex-bin, but it's just to slow, it takes about
> five minutes to type './configure --host=arm-linux'... :)
Right now, I'm getting ~130ms ping time to 126.96.36.199, and about a 50%
If I ping different machines listed in your traceroute, everything
is fine until mae-west3.fddi.mci.net (188.8.131.52). After that, it gets
I don't seem to be having problems connecting to most places on the
net, so I'd have to assume that the problem is the Wave systems.
For perspective, a friend has Rogers Wave, and is 3 kilometers (line
of sight) from me. I'm seeing ~10% packet loss, and 1000ms round trip
time to him. A traceroute to him shows it's identical to yours up to
the last 3 hops.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org