MSGID: <10j0bdl$1nm5b$3@dont-email.me> 1f2d8dce
REPLY:  4ffecc94
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 30/12/2025 00:40, Jim Diamond wrote:
> On 2025-12-28 at 23:51 AST, Lawrence D?Oliveiro  wrote:
>> On Sun, 28 Dec 2025 23:14:09 -0400, Jim Diamond wrote:
>>
>>> No, the Pi thought two IPs were associated with the one and only
>>> wifi card.
>>
>> Just a note that this itself is not an error; the Pi doesn?t *think*
>> the interface has two IPs, it *knows*, because it was configured that
>> way.
> 
> OK... If we want to be really careful with our English, I suppose we should
> say "The Pi associated two IPv4 addresses with the one and only WiFi card."
> 
Well that depends on what constitutes the 'Pi'' Its software did the 
association, not the Pi...

> Not running any AI on my Pi, I don't think it knows or thinks anything.  ;-)
> 
You never know, with Heffalumps

>> There are legitimate uses for this sort of thing, even though it
>> was not a deliberate setup in your case.
> 
> Quite true, I have used it once or twice in the past myself.  (Why I did it
> is now lost in the depths of time.)
> 
Handy way to talk to an unconfigured router on some random default address.

>                                  Jim

-- 
There is nothing a fleet of dispatchable nuclear power plants cannot do 
that cannot be done worse and more expensively and with higher carbon 
emissions and more adverse environmental impact by adding intermittent 
renewable energy.


--- 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 300 317 400 426 428
SEEN-BY: 229/470 616 664 700 705 266/512 291/111 292/854 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/10 280 414 418 420 422 509 2744
SEEN-BY: 712/848 770/1 902/26 2320/105 5020/400 5075/35
PATH: 633/10 280 229/426