Weird ping response

[raptorgeezus]

I'm trying to revive what I think is a dead router (running DD-WRT).

I pinged it to see if I could get some signs of life and got this response:

Pinging 192.168.1.1 with 32 bytes of data
Request timed out.
Reply from 213.130.48.253: Destination net unreachable.
Request timed out.
Request timed out.

Isn't that quite weird to get a ping response form that IP address which tracks back to the UK?

 

[adam_g]

Update servers for firmware maybe? lol

 

[SauRoNZA]

I'm trying to revive what I think is a dead router (running DD-WRT).

I pinged it to see if I could get some signs of life and got this response:

Pinging 192.168.1.1 with 32 bytes of data
Request timed out.
Reply from 213.130.48.253: Destination net unreachable.
Request timed out.
Request timed out.

Isn't that quite weird to get a ping response form that IP address which tracks back to the UK?

Normally those messages would show your own IP address not that of the destination.

So are you somehow trying to ping via your WAN maybe?

 

[RoganDawes]

Extremely odd. More information about your setup would be good. i.e. what client platform are you using? Windows, Linux, Mac, etc?

How are you connecting to the router? Ethernet? Are you connected to anything else at the same time? Is the router connected to anything else at the same time?

What router is it that you are trying to revive? What model, etc? Can you put a serial console on it?

 

[Treschen]

tracert back to the IP, what is your network ID ? is the device on your local network ?

 

[Stratt]

As the traffic routes from router to router, this specific IP will be in the path to reach the destination. This router does not seem to have a route, or can not access the destination IP/network in question. Therefore it is responding with "Destination net unreachable". Very poor setup on their end not to have dynamic routing that will choose an alternative path to the specific network in question.

As a matter of interest what is the IP you are trying to reach?