INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  3458adec   
   REPLY: <20240625211849.42078917d9eae9b4c89c4ef3@eircom.net> c20fefc0   
   PID: SoupGate-Win32 v1.05   
   Ahem A Rivet's Shot  wrote:   
   > On Tue, 25 Jun 2024 19:53:11 -0000 (UTC)   
   >  wrote:   
   >   
   >> 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   
   >   
   >         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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 128/260 129/305   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360   
   SEEN-BY: 226/17 30 100 227/114 229/110 111 112 113 200 206 300 317   
   SEEN-BY: 229/400 426 428 470 550 616 664 700 240/1120 266/512 267/800   
   SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426