7.9 ms to my wifi in FIOS in NJ.
It's not the ping time... It's the throughput that is often lacking in real world use. No matter the pipe size.
Bill
Sent from my android device.
-----Original Message-----
From: Corey Lindsly <corey@lod.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Sent: Thu, 09 Feb 2017 14:55
Subject: Re: [TUHS] Code bloat (was: How Unix brings people together,
> In spite of that, I'm typing away to you all, I'm 3ms away from 8.8.8.8
> (Google's dns server). Go wireless. It's pretty remarkable to be here
> and have decent net connectivity.
>
> I do not yearn for the days of SLIP.
> --
> ---
> Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
3ms? Really? I'm impressed, and I'd like to see your traceroute. We peer
directly with Google and I get 4-5ms. Do share.
[root@daytona ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=5.43 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=5.39 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=5.43 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=5.02 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=59 time=5.30 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=59 time=5.35 ms
Pittock7206A#trace 8.8.8.8
Type escape sequence to abort.
Tracing the route to 8.8.8.8
1 198.32.195.34 4 msec 4 msec 4 msec
2 108.170.245.113 [AS 15169] 4 msec
108.170.245.97 [AS 15169] 8 msec 4 msec
3 209.85.246.217 [AS 15169] 4 msec
209.85.246.219 [AS 15169] 4 msec
209.85.245.67 [AS 15169] 8 msec
4 8.8.8.8 [AS 15169] 4 msec 4 msec 4 msec
Pittock7206A#
--corey