Path: ...!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Newsgroups: comp.sys.raspberry-pi Subject: Re: Pi4 to Pi5 migration Date: Tue, 25 Jun 2024 19:53:11 -0000 (UTC) Organization: A noiseless patient Spider Lines: 27 Message-ID: References: <20240625192405.f104a800a1e06c299866c7a4@eircom.net> Injection-Date: Tue, 25 Jun 2024 21:53:12 +0200 (CEST) Injection-Info: dont-email.me; posting-host="45da3dd0f798c6adfce2b1da78bb3409"; logging-data="1793041"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Qzfb3fHshd/ikJL0t4osImTLEyPkmAds=" User-Agent: tin/2.6.2-20221225 ("Pittyvaich") (FreeBSD/14.0-RELEASE-p6 (arm64)) Cancel-Lock: sha1:GStXKDA0yZemtC5KKSO4vbDNqh4= Bytes: 2166 Ahem A Rivet's Shot wrote: > On Mon, 24 Jun 2024 22:28:01 -0000 (UTC) > 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 LAN IP addresses access to the Internet" which isn't my problem. Both firewalls and DMZ are disabled. There's also a "block WAN Ping" option, but that's to "Discard PING from WAN side" and disabled. The Pi4 and Pi5 hosts can ping the printer, but the two Pi's can't ping each other, nor will they answer ping from a Mac. Both Pi's can self-ping on their assigned LAN address. Thanks for writing! bob prohaska