INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  d5bc19ee   
   REPLY:  5e09346a   
   PID: SoupGate-Win32 v1.05   
   Chris Green  wrote:   
   >>   
   > Three possible things to check:-   
   >   
   > 1 - Are the two Pis on the same subnet?  I.e. while you have told us   
   > the whole address for the Pi2 (192.168.1.10) you have only given the   
   > last digit for the Pi5 and the router.  What are the full IPV4   
   > addreses for the Pi5 and the router.  Certainly some widely used   
   > routers default to 192.168.0.254 and I'm wondering if that is your   
   > problem.  Maybe you even have *two* subnets on the router.   
      
   The router (A DI-524) has only one subnet (192.168.1.nnn) for which it   
   is the DHCP server. Both Pi5 and Pi4 use DHCP, with the DHCP range   
   from 192.168.1.10 to 192.168.1.20 .   
      
   >   
   > 2 - Are you using the 'guest' WiFi of the router, this may prevent   
   > connecting between different systems using the WiFi.  This may even be   
   > possible to configure with non-guest networks.  You'll have to look   
   > into the router configuration to check.   
   >   
   There's nothing called guest mode in the config pages, but there are   
   "filters", described as "allow or deny LAN users from accessing the   
   Internet". Nothing is listed as enabled, so I don't think that's the   
   problem.   
      
   There are three firewall rules active, allow ping to WAN port, allow   
   LAN to LAN for all protocols and deny WAN to LAN for all protocols.   
      
   > 3 - Is the Pi2 connected to the same network/router as the Pi5? Are   
   > you sure it's using DHCP to get its address?  If so then you should be   
   > able to check on the router that it's connected to as it is the router   
   > that is handing out IP addresses (usually).   
   >   
   >   
   Yes, there is only one router/AP.   
      
   > The first thing I would be doing is to look at the routers's Web GUI   
   > to check what it thinks is going on and what is connected to where.   
   >   
   >   
   The DHCP range is limited to 192.168.1.nnn, with no distinction between   
   wired and wireless connections. There's clearly bridging from wirless to   
   wired devices such as the printer, which works and can be pinged.   
      
   Maybe there's a firewall between wireless clients. I've certainly not needed   
   such connections much. I'll poke around on the Web to see if there are any   
   references to Guest Mode online. The internal help pages are close to useless,   
   and the configuration menus are worse.   
      
   Thanks for writing, and your patient good counsel!   
      
   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 129/305 153/757   
   SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426