Path: ...!3.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Chris Green Newsgroups: comp.sys.raspberry-pi Subject: Re: Getting along without a keyboard Date: Mon, 16 Sep 2024 07:16:30 +0100 Lines: 30 Message-ID: References: <4amfrk-ar77.ln1@q957.zbmc.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net t65QaOLYjzipSFlYpDPewAcDQNA57gVssFaPIRMxz31h417YA= X-Orig-Path: not-for-mail Cancel-Lock: sha1:ysVileLVP5iDnOBJ7prO03HrxH8= sha256:wAuDELvoe/Mqs1+L2YGx/0NCKGF7y55MFqyaACvFeR4= User-Agent: tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-41-generic (x86_64)) Bytes: 2078 bp@www.zefox.net wrote: > Chris Green wrote: > >> [snip] > > > 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. > Router software does sometimes have bugs. I have a TP-link router that has a symptom a bit like yours, I can't remember the exact details (it's relegated to being an access point now) but I do remember that it was something about the firewall treating WiFi connections differently from wired ones. Can you temporarily connect the Pi2 using a wired connection and see if it then works as expected? -- Chris Green ยท