Re: Pi4 to Pi5 migration

Ahem A Rivet's Shot <steveo@eircom.net> wrote:

On Tue, 25 Jun 2024 19:53:11 -0000 (UTC)
<bp@www.zefox.net> wrote:
 

Ahem A Rivet's Shot <steveo@eircom.net> wrote:

On Mon, 24 Jun 2024 22:28:01 -0000 (UTC)
<bp@www.zefox.net> wrote:
 

At this point both machines are on the same 192.168.1.y network, but
they don't seem able to communicate at all, simply reporting
"no route to host" from either end. Ping fails, losing all packets.
It looks like sshd is running, based on ps output.

 
        Is the WAP configured to block traffic between clients ? That
seems to be the default with many consumer WAPs.

 
I think the answer is "no". There is an "advanced" tab in the router
config mentioning IP filters, but explains "Use IP Filters to deny

 
        It's usually called something to do with isolation "wireless" or
"client" most often. I'd be surprised if there wasn't the option.

It's an old router, a D-Link di-524.

The "wireless" page on the router configuration is exclusively about
configuring client connections (radio on, ssid, security). The LAN
page sets the router's LAN IP, subnet mask and local domain, along
with "dns relay", which is enabled.

There is a long list of "virtual servers", but I think that's to do
with services to the WAN. All are disabled.

I again tried to connect from the Mac to the Pi4 and Pi5, this time
using sftp. That timed out, but it didn't report "no path to host"
like ping did. Using ssh failed with a host key error, suggesting
the connections to the Pi4 and Pi5 worked but ssh on the Mac is too
old. It _is_ old, being Mac OS X 10.7.5, but that's nothing to do
with why the two Pi's cannot ssh each other. An attempt to connect
via sftp reported
 ssh: connect to host 192.168.1.10 port 22: No route to host
 Connection closed
after a short delay.

Thanks for writing!

bob prohaska