This is a discussion on "Ping" doesn't work properly within the Linux Networking forums, part of the Linux Forums category; I only want to send one packet to another host to check whether it is connected or not. I want ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I only want to send one packet to another host to check whether it is
connected or not. I want to have 2 seconds timeout. I use, ping -c 1 -w 2 192.168.0.2 If host is not connected, it fails correctly. BUT summary says. PING 192.168.0.2 from 192.168.0.1 : 56(84) bytes of data --------192.168.0.2 ping statastics -------- 2 packets transmitted, 0 received, 100% loss, time 999ms Why 2 packets are sent instead of 1 (specified) and why it only waits for 999 ms instead of 2 seconds. Even if I use: ping -c 5 -w 2 192.168.0.2, it has the same result. Here I wanted to send 5 packets but, again 2 packets were sent? What is wrong here? Please help me. Thanks a lot |
|
|||
|
-w deadline
Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network. I think you want to use: -t ttl Set the IP Time to Live. Neel wrote: > I only want to send one packet to another host to check whether it is > connected or not. I want to have 2 seconds timeout. > > I use, ping -c 1 -w 2 192.168.0.2 > > If host is not connected, it fails correctly. BUT summary says. > > PING 192.168.0.2 from 192.168.0.1 : 56(84) bytes of data > > --------192.168.0.2 ping statastics -------- > 2 packets transmitted, 0 received, 100% loss, time 999ms > > Why 2 packets are sent instead of 1 (specified) and why it only waits > for 999 ms instead of 2 seconds. > > Even if I use: ping -c 5 -w 2 192.168.0.2, it has the same result. Here > I wanted to send 5 packets but, again 2 packets were sent? > > What is wrong here? Please help me. > Thanks a lot -- Living on Earth may be expensive, but it includes an annual free trip around the sun. |
|
|||
|
Neel wrote:
> I only want to send one packet to another host to check whether it is > connected or not. I want to have 2 seconds timeout. > > I use, ping -c 1 -w 2 192.168.0.2 > > If host is not connected, it fails correctly. BUT summary says. > > PING 192.168.0.2 from 192.168.0.1 : 56(84) bytes of data > > --------192.168.0.2 ping statastics -------- > 2 packets transmitted, 0 received, 100% loss, time 999ms > > Why 2 packets are sent instead of 1 (specified) and why it only waits > for 999 ms instead of 2 seconds. > > Even if I use: ping -c 5 -w 2 192.168.0.2, it has the same result. Here > I wanted to send 5 packets but, again 2 packets were sent? > > What is wrong here? Please help me. > Thanks a lot > the -w flag..?? gives me "invalid option -w" .. on a linux system. |
|
|||
|
"Neel" <nilayhshah@gmail.com> wrote:
>I only want to send one packet to another host to check whether it is >connected or not. I want to have 2 seconds timeout. > >I use, ping -c 1 -w 2 192.168.0.2 > >If host is not connected, it fails correctly. BUT summary says. > >PING 192.168.0.2 from 192.168.0.1 : 56(84) bytes of data > >--------192.168.0.2 ping statastics -------- >2 packets transmitted, 0 received, 100% loss, time 999ms > >Why 2 packets are sent instead of 1 (specified) and why it only waits >for 999 ms instead of 2 seconds. > >Even if I use: ping -c 5 -w 2 192.168.0.2, it has the same result. Here >I wanted to send 5 packets but, again 2 packets were sent? > >What is wrong here? Please help me. >Thanks a lot There are several versions of ping, so results vary depending on which set of bugs you encounter! In your case, the -w option invalidates the -c option. If you have a -w option, the -c option is ignored. That will not likely cause you any real problems though. The other bug is an off-by-one in the reported number of packets sent. Again, probably not really a problem. Offhand I would guess that both of those bugs are easy to fix, hence if you can find out who did that version of ping it might be possible to get something changed. -- Floyd L. Davidson <http://www.apaflo.com/floyd_davidson> Ukpeagvik (Barrow, Alaska) floyd@apaflo.com |
![]() |
| Thread Tools | |
| Display Modes | |
|
|