[K12OSN] Re: tuxpaint and others running slow

[Eric Harrison]

On Tue, 25 Oct 2005, Justin Paulsen wrote:

> [root at Ayumi ~]# ping -c 100 192.168.0.254
> PING 192.168.0.254 (192.168.0.254) 56(84) bytes of data.
> 64 bytes from 192.168.0.254: icmp_seq=0 ttl=64 time=0.039 ms

192.168.0.254 is the default IP address of the server. Odds are
pretty good that you pinged the server's interface from the server
itself. If that is the case, it won't tell us much about the state
of your network.

To quote Dan's orginal suggestion:

> And let's look at the network:
> use ping to examine the health of the network connecting the server to
> the workstations, e.g. run "ping -c100 -A client1" on the server,
> and post the statistics it prints at the end.  It'll look like this:
>
> 100 packets transmitted, 100 received, 0% packet loss, time 19899ms
> rtt min/avg/max/mdev = 0.493/0.512/0.553/0.015 ms, pipe 2, ipg/ewma
> 201.002/0.513 ms


Note that Dan says you need to ping one of the terminals from the server, 
which is different than pinging the server from one of the terminals.

And also be sure to follow Dan's recommendation to post the LAST lines
of the ping output, not the first.


This should work for you...

* login to a thin client

* open a terminal shell (right click on the background and select
   "Open Terminal")

* at the terminal shell, type this command: (EXACTLY LIKE IT IS BELOW)

 	   ping -c200 -A $LTSP_CLIENT

   (NOTE: this command only works from a terminal booted from a K12LTSP server,
          if you get an "Usage: ping [-LRUbdfnqrvVaA]..." message let us know)

* start up TuxType and practice your typing for a couple of minutes,
   then exit TuxType.

* post the last couple of lines of output that ping displayed in
   the terminal shell.


-Eric