Windows ping and Linux ping command?

OK, there must be some fundumental difference
in the ping command that linux uses as opposed to
the ping command that Windows uses.

Can anyone here elaborate?

On Fri, 07 Nov 2003 18:58:19 GMT, tom <(E-Mail Removed)> wrote:
> OK, there must be some fundumental difference
> in the ping command that linux uses as opposed to
> the ping command that Windows uses.
>
> Can anyone here elaborate?

The windows ping is a toy version, a subset of the unix/linux version.

"tom" <(E-Mail Removed)> wrote:

> OK, there must be some fundumental difference in the ping command that
> linux uses as opposed to the ping command that Windows uses.

Though I have no Windows box at my hand to compare, I agree. But what is
it that makes you think so?

The windows ping has a limited set of command line options compared to the
linux ping. I'm basing this off the ping command in win2k, don't remember
how limited it was in win9x.

--
Jeff Umbach

"tom" <(E-Mail Removed)> wrote in message
news:fXRqb.13994$(E-Mail Removed) y.com...
> OK, there must be some fundumental difference
> in the ping command that linux uses as opposed to
> the ping command that Windows uses.
>
> Can anyone here elaborate?
>
>

"tom" <(E-Mail Removed)> wrote in message
news:fXRqb.13994$(E-Mail Removed) y.com...
> OK, there must be some fundumental difference
> in the ping command that linux uses as opposed to
> the ping command that Windows uses.
>
> Can anyone here elaborate?
>
>

Options for

Linux

ping -s [-d] [-l] [-L] [-n] [-r] [-R] [-v] [ -i interface_address ] [-I
interval] [-t ttl] host [packetsize] [count]

-d Set the SO_DEBUG socket option.
-l Loose source route. Use this option in the IP header to send the
packet to the given host and back again. Usually specified with the -R
option.
-L Turn off loopback of multicast packets. Normally, if there are
members in the host group on the out- going interface, a copy of the
multicast packets will be delivered to the local machine.
-n Show network addresses as numbers. ping normally displays addresses
as host names.
-r Bypass the normal routing tables and send directly to a host on an
attached network. If the host is not on a directly-attached network, an
error is returned. This option can be used to ping a local host through an
interface that has been dropped by the router daemon.
-R Record route. Sets the IP record route option, which will store the
route of the packet inside the IP header. The contents of the record route
will only be printed if the -v option is given, and only be set on return
packets if the target host preserves the record route option across echos,
or the -l option is given.
-v Verbose output. List any ICMP packets, other than ECHO_RESPONSE,
that are received.
-i interface_address Specify the outgoing interface address to use for
multicast packets. The default interface address for multicast packets is
determined from the (unicast) routing tables.
-I interval Specify the interval between successive transmissions. The
default is one second.
-t ttl Specify the IP time to live for unicast and multicast packets.
The default time to live for unicast packets is set with ndd (using the
icmp_def_ttl variable). The default time to live for multicast is one hop.
host The network host.
packetsize Specified size of packetsize. Default is 64.
count Amount of times to send the ping request.


Windows

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] target_name

Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS Type Of Service.
-r count Record route for count hops.
-s count Timestamp for count hops.
-j host-list Loose source route along host-list.
-k host-list Strict source route along host-list.
-w timeout Timeout in milliseconds to wait for each reply.

In article <FEXqb.103826$9E1.499728@attbi_s52> (E-Mail Removed)
(Michael O) writes:

>"tom" <(E-Mail Removed)> wrote in message
>news:fXRqb.13994$(E-Mail Removed) gy.com...
>
>> OK, there must be some fundumental difference
>> in the ping command that linux uses as opposed to
>> the ping command that Windows uses.
>>
>> Can anyone here elaborate?
>
>Options for
>
>Linux
>
>ping -s [-d] [-l] [-L] [-n] [-r] [-R] [-v] [ -i interface_address ] [-I
>interval] [-t ttl] host [packetsize] [count]

<snip>

>Windows
>
>Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
> [-r count] [-s count] [[-j host-list] | [-k host-list]]
> [-w timeout] target_name

Another highly visible difference between Windows and Linux pings
is that the number of pings (-n parameter for Windows) defaults
to 4 pings under the Windows version. Unix/Linux ping defaults
to sending packets continuously until interrupted.

--
/~\ (E-Mail Removed)lid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!