On Thursday, December 11th, 2025 at 10:18 AM, Rich Shepard 
<[email protected]> wrote:

> On Thu, 11 Dec 2025, Ben Koenig wrote:
> 
> > In an earlier post you mentioned that caddis has an IP address of
> > 192.168.55.2. This was showing in your /etc/hosts file.
> > 
> > According to the output of ip above, caddis has 2 IP addresses:
> > 
> > Ethernet: 192.168.55.112
> > wifi: 192.168.55.111
> 
> 
> Ben,
> 
> I saw that but it makes no sense to me.
> 
> $ less /etc/hosts:
> 127.0.0.1 localhost.localdomain localhost
> 192.168.55.1 salmo.appl-ecosys.com salmo mail # older desktop
> 192.168.55.2 caddis.appl-ecosys.com caddis # Lenovo ThinkPad T430
> 192.168.55.3 baetis.appl-ecosys.com baetis # newer desktop
> 192.168.55.4 router1.appl-ecosys.com router1 # Edge Router-X
> 192.168.55.5 lemna.appl-ecosys.com lemna
> 192.168.55.10 packy.appl-ecosys.com packy # HP laptop
> 192.168.55.150 ata.appl-ecosys.com ata
> 192.168.55.192 lj5.appl-ecosys.com lj5
> 192.168.55.194 colorp.appl-ecosys.com colorp
> 192.168.55.200 wap.appl-ecosys.com wap
> # End of hosts.
> 
> > I think you have been connecting to the wrong device. As a test, try the
> > following ssh command from your desktop (salmo):
> > ssh 192.168.55.111
> > If that fails, try this one
> > ssh 192.168.55.112
> 
> 
> $ ssh 192.168.55.111
> ssh: connect to host 192.168.55.111 port 14982: No route to host
> $ ssh 192.168.55.112
> ssh: connect to host 192.168.55.112 port 14982: No route to host
> $ ^C
> 
> No response for the latter.
> 
> Rich

That's really weird. I wonder what got buggered up. This probably means you 
need to simplify the network config of the laptop and verify bare minimum 
functionality. 

Try disabling your wifi connection so that we are using ethernet only, and then 
reconnect the ethernet cable to make sure it gets a fresh link.

Then restart sshd with '/etc/rc.d/rc.sshd restart'.

Next, verify that sshd is listening on the correct port with 'lsof -i tcp:22'. 
Example output from my machine with default sshd.conf

bash-5.3# lsof -i tcp:22
COMMAND  PID USER FD   TYPE DEVICE SIZE/OFF NODE NAME
sshd    1671 root 6u  IPv4  11119      0t0  TCP *:ssh (LISTEN)
sshd    1671 root 7u  IPv6  11121      0t0  TCP *:ssh (LISTEN)


You should see something similar to the above. 

At this point, if everything looks happy, try to ssh into the laptop, FROM THE 
LAPTOP. This merely a test to verify that sshd is actually responding to 
connections. 

If everything so far works, then the next step is to figure out which IP 
address your laptop has been assigned on the network.

Note these steps are of an investigational nature. They are not intended to be 
a solution, merely an attempt to isolate the point of failure. 
-Ben


Reply via email to