defining interface that is origination of pings, trace, tftp, etc

[abuswell]

Need someone to tell me if there is another way other than defining a loopback port to have an interface and its assigned ip to be the source ip of origin when performing operations from this router against other routers, switches, (ping, traceroute, tftp, etc)

[pkhatri · Accepted solution]

Hi,

Ping

====

ping source

OR

Use the extended ping command i.e type in ping and hit enter. Enter in 'y' for extended commands and you will be asked for a source address

E.g router#ping

Protocol [ip]:

Target IP address: 1.1.1.1

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 16.1.1.2

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 5, 100-byte ICMP Echos to 1.1.1.1, timeout is

Packet sent with a source address of 16.1.1.2

.....

Success rate is 0 percent (0/5)

router#

Traceroute

==========

Do an extended traceroute

router#trace

Protocol [ip]:

Target IP address: 1.1.1.1

Source address: 16.1.1.2

...

TFTP

====

Enter in the command 'ip tftp source-interface ' in config mode.

FTP

====

Enter in the command 'ip ftp source-interface ' in config mode.

NTP

====

Enter in the command 'ntp source ' in config mode.

Hope that helps - pls rate the post if it does.

Regards,

Paresh.

[abuswell]

thanks for the hugely informative post! the last 3 suggestions for tftp, ftp, & ntp were exactly what I was looking for.