i am using debian, i used to ssh to a machine inside my local network a few weeks ago, probably after the updates i cannot ssh into that machine again, ssh username@ shows:

ssh: connect to host port 22: No route to host

so i tried pinging the machine ping shows:

PING ( 56(84) bytes of data.
From icmp_seq=1 Destination Host Unreachable
From icmp_seq=2 Destination Host Unreachable
From icmp_seq=3 Destination Host Unreachable
--- ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5128ms
pipe 4

Another windows machine in the same network is able to ssh into the machine as well as getting the response on pinging.

i can ssh into demo@test.rebex.net which is a demo ssh server (ofc not local)

I think i may have messed up my ssh client for local networks.

Additional info

My machine's local IP:

Default gateway:

ip addr returns:

2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 14:f6:d8:f3:85:81 brd ff:ff:ff:ff:ff:ff
    inet brd scope global dynamic noprefixroute wlp0s20f3
       valid_lft 12379sec preferred_lft 12379sec
    inet6 fe80::2cfd:51da:c35:978b/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
  • 1
    The responding is outside of your system's IP range, so it has to be the next-hop router after .40.1. It seems that doesn't have a route to subnet Can you check the routing table on that device? What's the IP address of the other system that can successfully ping? Can you run traceroute on both and the other system, and edit the question to add the results? Mar 18 at 19:45
  • Are you using Docker? It tends to create networks that will clash with your own real networks.
    – A.B
    Mar 19 at 11:05

1 Answer 1


You're mixing networks.

RFC1918 defines the Address Allocation for Private Internets for creating a Private network

These addresses are designed to be used inside a local network, and are not intended for links between networks (although they can be).

One of these address ranges is -, or 172.16/12.

The IP address is inside this network, but is not inside it.

You're getting the error "Destination Host Unreachable" because the computer doesn't know of a route for contacting the other network.

I have no idea what update was done and what it has changed, but you should define your local network so it uses just one IP range that is common to all the computers and routers. Otherwise, you will need to setup the router or routers so that forwarding messages between the two networks is defined.

If you need more information, please add a drawing of the schema of your network to your post so we can better understand the problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.