MSGID: <10k0t2t$4hee$3@dont-email.me> c4b7573d
REPLY:  20498eee
PID: PyGate 1.5.2
TID: PyGate/Linux 1.5.2
CHRS: CP1252 2
TZUTC: 0000
REPLYADDR tnp@invalid.invalid
REPLYTO 3:633/10 UUCP
On 11/01/2026 14:13, Adrian wrote:
> I started looking at doing something similar to this a couple of years 
> ago (using the Pi as a WiFi access point in a location beyond the range 
> of my router's WiFi).ÿ I didn't complete the task for various reasons, 
> but one thing that was clear, was that if I were to do it again, I would 
> do the initial configuration of the Pi locally (keyboard etc. plugged 
> in) rather than across the network (ssh session) as at each step of the 
> way, it seemed that the Pi was inaccessible for something like 20-30 
> minutes whilst it sorted out what to do with each configuration change 
> (of which there were several needed).

Many thanks for good advice. I have a 4B available to test all this on 
with a scream and keybored, and I have been through all this myself with 
headless servers and IP changes. :-)

-- 
Future generations will wonder in bemused amazement that the early 
twenty-first century?s developed world went into hysterical panic over a 
globally average temperature increase of a few tenths of a degree, and, 
on the basis of gross exaggerations of highly uncertain computer 
projections combined into implausible chains of inference, proceeded to 
contemplate a rollback of the industrial age.

Richard Lindzen


--- PyGate Linux v1.5.2
 * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 112 134 200 206 275 300 317 400 426
SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219
SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422
SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35
PATH: 633/10 280 229/426