How to fix "no route to host" problem

[Matt Graham]

> On Fri, Oct 5, 2018 at 4:35 PM Joe Lowder <joe at actionline.com> wrote:
>> For many months, I have been using rsync to copy files
>> from one of my computers to two others, and it has worked
>> flawlessly. But today, it quit working
>> ssh: connect to host 192.168.0.4 port 22: No route to host
On 2018-10-06 16:02, Michael Butash wrote:
> If no route to host in a local subnet, the remote device isn't arping
> in the local device cache, which is the most basic networking
> possible.  Using "ip neighbor" or old "arp -an" works to see this, but
> usually means your remote host isn't getting on the network enough ro
> even layer 2 arp.  
> 
> Can you ping it?

If this is a normal home network, it is entirely possible that the 
target machine is using DHCP.  The DHCP servers on many home routers are 
not always set up to give the same IPs to the same MAC addrs.  So:  Go 
to the target machine and find out what its IP and MAC 
are--"/sbin/ifconfig" from the command line will show that info.  Then 
set up your router such that it will always give out 192.168.0.4 to that 
MAC.

Many home routers also act as tiny caching DNS servers by default.  
Some of these are smart enough so that you can associate names with IPs 
in the local LAN, so that you can "rsync /path/to/stuff/ 
machine1:/backups/stuff/" instead of 192.168.0.4:/backups/stuff/ .

-- 
Crow202 Blog: http://crow202.org/wordpress
There is no Darkness in Eternity
But only Light too dim for us to see.