Hans Krueger wrote:
Erik Jakobsen wrote:
Dave Howorth wrote:
Erik Jakobsen wrote:
Is it all ok now ?.
Yes, I understand now, thanks :)
I will do the tests you suggested Dave but with the 2 HDD's. The one with the suse10.0eval, and the other with the suse10.0in a box
Sounds good. Dave
Hi Dave, hi Hans.
Now I have done the tests.
From the server to the ok suse box:
#PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data. 64 bytes from 192.168.1.9: icmp_seq=0 ttl=64 time=0.203 ms 64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=0.168 ms
--- 192.168.1.9 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.168/0.185/0.203/0.022 ms, pipe 2
#traceroute traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 38 byte packets 1 lajka3 (192.168.1.9) 0.290 ms 0.180 ms 0.121 ms
From the ok susebox to the server:
# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.171 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.256 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.169 ms
--- 192.168.1.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.169/0.198/0.256/0.043 ms
# traceroute 192.168.1.1 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets 1 192.168.1.1 0.160 ms 0.106 ms 0.141 ms
From the ok suse to the ok suse:
# ping 192.168.1.9 PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data. 64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=0.051 ms 64 bytes from 192.168.1.9: icmp_seq=2 ttl=64 time=0.042 ms 64 bytes from 192.168.1.9: icmp_seq=3 ttl=64 time=0.043 ms
--- 192.168.1.9 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.042/0.045/0.051/0.006 ms
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 40 byte packets 1 lajka3.urbakken.dk (192.168.1.9) 0.000 ms 0.000 ms 0.000 ms
From the server to the not ok suse:
traceroute ping 192.168.1.9 PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data.
--- 192.168.1.9 ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 10998ms
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 38 byte packets 1 * * * 2 * * * 3 * * *
From the not ok suse to the server:
# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.214 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.223 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.239 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.198 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.188 ms
--- 192.168.1.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.188/0.212/0.239/0.022 ms
# traceroute 192.168.1.1 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets 1 mail.urbakken.dk (192.168.1.1) 0.156 ms 0.103 ms 0.101 ms
From the not ok suse to the not ok suse:
# ping 192.168.1.9 PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data. 64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 192.168.1.9: icmp_seq=2 ttl=64 time=0.061 ms 64 bytes from 192.168.1.9: icmp_seq=3 ttl=64 time=0.057 ms
--- 192.168.1.9 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.057/0.063/0.071/0.005 ms
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 40 byte packets 1 lajka3.urbakken.dk (192.168.1.9) 0.000 ms 0.000 ms 0.000 ms
I hope that tells something.
/Erik
I got to think about this one just a thought have you tried knoppix on it ?
Hi Hans. No I haven't, and I'm not aware on how to test with Knoppix. Could you please explain it for me ?. Thanks in advance -- Venlig hilsen - Best regards - Erik Jakobsen SuSE Linux 10.0 Eval.. Licensed HAM-RADIO with the callsign OZ4KK http://www.urbakken.dk Registered Linux user #114875 with http://counter.li.org