INTL 3:770/1 3:770/3   
   REPLYADDR cl@isbd.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  5e09346a   
   REPLY:  49ae0eda   
   PID: SoupGate-Win32 v1.05   
   bp@www.zefox.net wrote:   
   > Chris Green  wrote:   
   > > You need a virtual keyboard, a web search for 'pi virtual keyboard'   
   > > comes up with loads of hits.   
   > >   
   > > There are several in the standard Raspbian repositories:-   
   > >   
   > >     apt search "on-screen keyboard"   
   > >   
   > Thank you, the choice of search terms  makes a big difference!   
   >   
   > That has led to another puzzle: The Pi2 is on a wifi dongle that   
   > reports a connection using 192.168.1.10 and successfully downloads   
   > RasPiOS updates. However, turning on ssh using the Raspberry>   
   > Preferences> Raspberry Pi Configuration menu and rebooting doesn't   
   > allow ssh login. Indeed, my DHCP server doesn't seem to notice   
   > that the Pi2 is connected and ping from my Pi5 to the Pi2 reports   
   > "host is unreachable".   
   >   
   > It wouldn't be a huge mystery if the WiFi couldn't connect, but the   
   > combination of the Pi2 claiming 192.168.1.10 and yet not being   
   > visible strikes me as inexplicable unless the software updates are   
   > being downloaded vi some non-IP protocol, which seems implausible.   
   >   
   > The only clue so far is that traceroute 192.168.1.10 on the Pi5 reports:   
   > traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets   
   >  1  192.168.1.11 (192.168.1.11)  3077.790 ms !H  3077.735 ms !H  3077.730 ms   
   !H   
   > To clarify, the Pi5 is .11, the router is .254 and I don't know what the   
   > traceroute output means but it looks like a complaint about time.   
   >   
   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.   
      
   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.   
      
   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).   
      
      
   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.   
      
      
      
   --   
   Chris Green   
   ·   
      
   --- 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