Deutsch   English   Français   Italiano  
<o3birk-8sg7.ln1@q957.zbmc.eu>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Chris Green <cl@isbd.net>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Getting along without a keyboard
Date: Sun, 15 Sep 2024 07:23:20 +0100
Lines: 58
Message-ID: <o3birk-8sg7.ln1@q957.zbmc.eu>
References: <vc2njn$149o8$1@dont-email.me> <4amfrk-ar77.ln1@q957.zbmc.eu> <vc4p23$1l77r$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net DsCYdpMGoi+WyH5HwTDEWATA03YuVJONY1rnjYmDh07VpoDqg=
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:As7wi2OwYzz8Pu1GJSfPdU6/X44= sha256:mkVz+xGAD/93AAgKNLrgW+x0RfiVHE1RSM55oUEZBks=
User-Agent: tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-41-generic (x86_64))
Bytes: 3459

bp@www.zefox.net wrote:
> Chris Green <cl@isbd.net> 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
·