On 2020-06-17 07:19, Kenneth Porter
wrote:
--On
Wednesday, June 17, 2020 8:07 AM +0800 Ed Greshko
<ed.greshko@greshko.com> wrote:
[egreshko@acer ~]$ ssh 192.168.1.142
ssh: connect to host 192.168.1.142 port 22: No route to host
That error usually means an address issue, not a firewall issue.
Are the two machines in the same subnet? Check "ip addr show" for
the interfaces involved.
As I mentioned, if the firewall is down, it works just fine.
But, just for completeness.
[egreshko@acer ~]$ ip add show wlp6s0
3: wlp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
state UP group default qlen 1000
link/ether 00:1b:77:d6:ac:c7 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.116/24 brd 192.168.2.255 scope global dynamic
noprefixroute wlp6s0
valid_lft 69662sec preferred_lft 69662sec
inet6 fe80::247c:82ac:e0d7:64af/64 scope link noprefixroute
valid_lft forever preferred_lft forever
[egreshko@acer ~]$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
0.0.0.0 211.75.128.254 0.0.0.0 UG 0
0 0 enp8s0
0.0.0.0 192.168.2.5 0.0.0.0 UG 0
0 0 wlp6s0
192.168.1.0 192.168.2.127 255.255.255.0 UG 0
0 0 wlp6s0
192.168.2.0 0.0.0.0 255.255.255.0 U 0
0 0 wlp6s0
192.168.122.0 192.168.2.127 255.255.255.0 UG 0
0 0 wlp6s0
211.75.128.0 0.0.0.0 255.255.255.0 U 0
0 0 enp8s0