[SlugLUG] Latency Issues On Campus ResNet

[Matt Thrailkill]

I get some jitter pinging ucsc.edu, but pinging an external host is much
more consistent for me:
PING 66.52.66.40 (66.52.66.40) 56(84) bytes of data.
64 bytes from 66.52.66.40: icmp_seq=1 ttl=52 time=11.6 ms
64 bytes from 66.52.66.40: icmp_seq=2 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=3 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=4 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=5 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=6 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=7 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=8 ttl=52 time=11.5 ms
64 bytes from 66.52.66.40: icmp_seq=9 ttl=52 time=11.4 ms
64 bytes from 66.52.66.40: icmp_seq=10 ttl=52 time=10.9 ms
64 bytes from 66.52.66.40: icmp_seq=11 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=12 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=13 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=14 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=15 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=16 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=17 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=18 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=19 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=20 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=21 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=22 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=23 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=24 ttl=52 time=11.5 ms
64 bytes from 66.52.66.40: icmp_seq=25 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=26 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=27 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=28 ttl=52 time=11.0 ms
64 bytes from 66.52.66.40: icmp_seq=29 ttl=52 time=11.8 ms
64 bytes from 66.52.66.40: icmp_seq=30 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=31 ttl=52 time=11.3 ms
64 bytes from 66.52.66.40: icmp_seq=32 ttl=52 time=12.1 ms
64 bytes from 66.52.66.40: icmp_seq=33 ttl=52 time=11.0 ms
64 bytes from 66.52.66.40: icmp_seq=34 ttl=52 time=11.2 ms
64 bytes from 66.52.66.40: icmp_seq=35 ttl=52 time=11.4 ms
64 bytes from 66.52.66.40: icmp_seq=36 ttl=52 time=11.1 ms
64 bytes from 66.52.66.40: icmp_seq=37 ttl=52 time=11.4 ms
64 bytes from 66.52.66.40: icmp_seq=38 ttl=52 time=11.5 ms
64 bytes from 66.52.66.40: icmp_seq=39 ttl=52 time=11.4 ms

--- 66.52.66.40 ping statistics ---
39 packets transmitted, 39 received, 0% packet loss, time 38161ms
rtt min/avg/max/mdev = 10.972/11.324/12.120/0.246 ms


169.233.20.227, college 9 apts

If you are really concerned about jitter though.. maybe you should check
out this tool called "mtr".  It makes traceroutes more fun.

On Fri, 2006-11-03 at 21:58 -0800, Rohan Sheth wrote:
> 169.233.11.197
> 
> crown merrill apartments.
> 
> --Rohan
> 
> On Fri, 2006-11-03 at 21:54 -0800, Mark Boolootian wrote:
> > > Why does resnet seem slow? (pokes booloo and those other guys who read
> > > the list...)
> > >
> > > --- ucsc.edu ping statistics ---
> > > 100 packets transmitted, 100 received, 0% packet loss, time 99081ms
> > > rtt min/avg/max/mdev = 2.240/24.378/129.587/27.871 ms
> > 
> > It's helpful to know the IP address of the source when answering such
> > questions.  If you're located at the Inn or UTC, you have my condolences:
> > 
> >   http://tinyurl.com/ydy5j9
> >   http://tinyurl.com/yj7dog
> > 
> > If you're on campus, the explanation requires a bit of poking around.
> 
> _______________________________________________
> Sluglug mailing list
> Sluglug at sluglug.ucsc.edu
> http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug