search for: 2002ms

...bytes of data. 1480 bytes from 192.168.7.175: icmp_seq=1 ttl=250 time=36.9 ms 1480 bytes from 192.168.7.175: icmp_seq=2 ttl=250 time=52.1 ms 1480 bytes from 192.168.7.175: icmp_seq=3 ttl=250 time=44.5 ms --- 192.168.7.175 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 36.994/44.569/52.160/6.191 ms Normal as can be... Now untagged: $ ping -c 3 -M do -s 1472 10.8.1.1 PING 10.8.1.1 (10.8.1.1) 1472(1500) bytes of data. --- 10.8.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms Same result all the way...

....8) from 100.10.10.1 eth1: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=16.9 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=49 time=19.4 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=49 time=20.7 ms --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 16.378/16.796/17.289/0.390 ms and # ping -c 3 -I eth2 8.8.8.8 PING 8.8.8.8 (8.8.8.8) from 99.10.11.1 eth2: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=48 time=24.9 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=48 time=25.3 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl...

....4 PING 1.2.3.4 (1.2.3.4) 56(84) bytes of data. 64 bytes from 1.2.3.4: icmp_seq=1 ttl=54 time=304 ms 64 bytes from 1.2.3.4: icmp_seq=2 ttl=54 time=22.7 ms 64 bytes from 1.2.3.4: icmp_seq=3 ttl=54 time=22.7 ms ^C --- 1.2.3.4 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 22.702/116.691/304.574/132.853 ms Immediately replying remote host on second try. $ ping 1.2.3.4 PING 1.2.3.4 (1.2.3.4) 56(84) bytes of data. 64 bytes from 1.2.3.4: icmp_seq=1 ttl=54 time=23.0 ms 64 bytes from 1.2.3.4: icmp_seq=2 ttl=54 time=22.8 ms 64 bytes from 1.2.3.4: i...

.... 64 bytes from 144.76.82.148: icmp_seq=1 ttl=47 time=117 ms 64 bytes from 144.76.82.148: icmp_seq=2 ttl=47 time=114 ms 64 bytes from 144.76.82.148: icmp_seq=3 ttl=47 time=113 ms ^C --- 144.76.82.148 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 113.948/115.229/117.293/1.473 ms $ ping 162.209.107.11 PING 162.209.107.11 (162.209.107.11) 56(84) bytes of data. 64 bytes from 162.209.107.11: icmp_seq=1 ttl=53 time=27.7 ms 64 bytes from 162.209.107.11: icmp_seq=2 ttl=53 time=23.4 ms 64 bytes from 16...

...234 wlan0: 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.64 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.28 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.33 ms --- 192.168.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 2.289/2.757/3.645/0.630 ms ------------------------------------------------------------------------------ i8600:~# ping -I wlan0 google.com.au PING google.com.au (216.239.57.104) from 192.168.0.234 wlan0: 56(84) bytes of data. --- google.com.au ping statistics --- 6 packets...

Listmates, I have had a few boxes where the 'matchname' message is filling my syslog with one new message ever ~40 seconds or so. No performance problems, just the log annoyance. An example of the messages are: Jan 11 13:43:03 nemesis smbd[2246]: [2010/01/11 13:43:03, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:03 nemesis smbd[2246]: Matchname failed on Adrienne-PC.rbpllc.com

sshd also dies when certain other kinds of traffic is generated, such as `man pw' using the most pager[1], and many x11 apps such as emacs. However, it is stable when running simple x11 apps such as xeyes, and the link its self is stable -- a terminal will stay connected without issue for days, as long as not much happens in it. Also a sshfs connection dies immediately. ssh -Y karren gkrellm