From: Bit Gossip (bit.gossip@chello.nl)
Date: Mon Jun 11 2007 - 06:09:36 ART
Group,
for testing multicast the following ping is useful because allow to
specify the outgoing interface; but it is very tedious and time
consuming because one has to type in every option every time.
Rack1R6#ping
Protocol [ip]:
Target IP address: 239.239.239.239
Repeat count [1]: 10
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]: FastEthernet0/0
Time to live [255]:
Source address: 192.10.1.6
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 239.239.239.239, timeout is 2
seconds:
Packet sent with a source address of 192.10.1.6
On the other side the following one liner is not equivalent because in
this case
ping ip 239.239.239.239 source FastEthernet0/0 repeat 10
packet are source with the IP address of f0/0 but sent out ALL
interfaces
Question: is there a way to create a one liner that does all the
extended ping does, in particular source address AND egress interface?
Maybe TCL?
Thanks,
Bit.
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:48 ART