Displaying 1 result from an estimated 1 matches for "29382ms".
Did you mean:
29382
2008 Aug 22
3
Problem with Broadcom Corporation NetXtreme II BCM5708 bnx2
...127
Reply from 10.1.1.1: bytes=32 time=-29815ms TTL=127
Reply from 10.1.1.1: bytes=32 time<1ms TTL=127
Reply from 10.1.1.1: bytes=32 time<1ms TTL=127
Reply from 10.1.1.1: bytes=32 time=-298341ms TTL=127
Reply from 10.1.1.1: bytes=32 time<1ms TTL=127
Reply from 10.1.1.1: bytes=32 time=29382ms TTL=127
Reply from 10.1.1.1: bytes=32 time<1ms TTL=127
It important to indicate that the "real" time is good ( approximately
between 1 and 2 seconds ). The problem is some applications used this value
to monitor some servers and send alarms when time value is high. How you can
see...