Path: ...!feeds.phibee-telecom.net!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Newsgroups: comp.sys.raspberry-pi Subject: Re: Getting along without a keyboard Date: Tue, 17 Sep 2024 16:56:26 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <4amfrk-ar77.ln1@q957.zbmc.eu> Injection-Date: Tue, 17 Sep 2024 18:56:26 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a9cdf617bc844ef5bec31a3aa1d67308"; logging-data="3803630"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX194K4KBXTqxMDiNkw0DwcfeOz6cv9izvBo=" User-Agent: tin/2.6.2-20221225 ("Pittyvaich") (FreeBSD/14.0-RELEASE-p10 (arm64)) Cancel-Lock: sha1:T+eqUOb3p8eorBNKE0K4blnLeH0= Bytes: 2180 mm0fmf wrote: > > That's AP Isolation at work. It stops Wifi devices communicating with > each. The idea is if you have lots of guest devices connecting, AP > Isolation stops them talking direct to each other and is meant to limit > a rogue guest device ability to do bad things to other guests. The problem is solved, and I'm feeling quite stupid about the solution. It turns out that setting a reserved DHCP address for the wireless client MAC address un-isolates hosts on WiFi. Ssh and ping work now. Interestingly, setting a static address at the client end, by itself, does not lift the isolation. An old iMac with a static IP connected to the LAN via a WiFi- Ethernet bridge still can't be pinged but connects outbound just fine. On reflection it makes perfect sense..... I've played with the idea of getting an open-wrt-compatible router in the past, but dropped the idea after finding nothing suitable at the local thrift store. Perhaps I should look again. Thanks to everyone for all your help! bob prohaska