ping using loopback address

[moman62]

I created a loopback address and assigned it an ip address, I cannot ping my tftp server from the router nor can i ping the loopback address from the pc.

Router4331#copy flash: tftp
Source filename []? pp-adv-isr4000-1612.1a-37-49.0.0.pack
Address or name of remote host []? 192.168.0.7
Destination filename [pp-adv-isr4000-1612.1a-37-49.0.0.pack]? pp-adv-isr4000-1612.1a-37-49.0.0.pack
.....
Error opening tftp://192.168.0.7/pp-adv-isr4000-1612.1a-37-49.0.0.pack (Timed out)
Router4331#
Router4331#
Router4331#ping 192.168.0.7
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.7, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

[liviu.gheorghe]

Hello @moman62 ,

in order to solve your issue, you need to ask yourself two questions:

1. does your router have knowledge about network 192.168.0.0/24 - I assumed the mask is /24 - where the tftp server is located?

2. does the tftp server knows how to reach the router?

Can you provide the output from the show ip route command from the router? Also can you provide the output from the following commands from the tftp server:

netstat -nr

ipconfig

[moman62]

my question is what makes this 4331 so special lol. I am able to use the tftp server on my 2921 routers without incidence. or does this router demand that the tftp server is setup differently to transfer to and from? Just using flash:?

[Richard Burts]

First I would like to observe that the OP begins by describing a loopback interface. But I do not see anything else in the post that refers to the loopback interface. Is there some relationship between the loopback and the issue with copying to tftp?

Next I would like to respond to this part of the OP "my question is what makes this 4331 so special". Based on what is contained in the OP we do not believe that there is anything inherent in the 4331 that is different and that the significant difference is how those routers are configured, especially in terms of routing to remote destinations.

Then I would like to address this "I cannot ping my tftp server from the router". There might be some aspects of the network (access list filtering etc) that would prevent ping to the server. But my first assumption is that this indicates a basic lack of connectivity. To investigate this I would suggest starting with performing show ip route and look to see if the subnet of the server is in the routing table. If not is there a default route which might point to the subnet of the server? Then I would try a traceroute to the address of the server. How far does the traceroute go? If it does not go all the way to the server then at the point that it stops is there something that prevents it going further?

[moman62]

I got it to work by adding the default route and using command ip tftp source-interface. my tftpd64 was not associated with udp port 69 in windows firewall.

[Richard Burts]

Thanks for the update. So it is working now?

[moman62]

well other than this 4331 router, I was/am able to use the tftp server without issues.

[Joseph W. Doherty]

If you are using a loopback, its IP needs to be routable.

Also, later routers now include services within a management VRF. So, you may need to assign a source IP for a particular service.  E.g.  ip tftp source-interface lo1

[Joshqun Ismayilov]

@moman62 

You can tracerout from PC to Lo address /  and check if you have a route or no. 
If others is working only 4331 is not work / try to test real interface instead of Lo.

You can share # show ip route 192.168.0.7

Thanks !