MSGID: <10ipc0u$3n6cr$1@dont-email.me> 521d962b
REPLY: <10ipai0$39s0k$1@dont-email.me> 19b61e98
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 27/12/2025 19:03, John R Walliker wrote:
> On 27/12/2025 18:17, The Natural Philosopher wrote:
>> On 27/12/2025 17:34, Jim Diamond wrote:
>>> Has anyone here seen this, and, if so, know what grievous sins I have
>>> committed to make this happen?ÿ And how to make it stop?
>>
>> For years my main *86 server would register itself with DHCP first, 
>> then manually set its IP address to something else.
>>
>> In the end I plugged in a screen and used the GUI and net manager to 
>> sort it all out, and it stayed sorted out.
>>
>> The problem is that there have been so many ways to set up IP over the 
>> last few years that any online guidance has at best a 25% chance of 
>> doing it the way the distro thinks it ought to be done,
> 
> Did the Pi itself think that it had two addresses on the WiFi interface
> or was it your router / dhcp server that had two records?
> 
[It isnt a pi: it is an *x86 mobo running linux mint, with ethernet 
connectivity]

I am nor sure. I think I could at least ping the DHCP assigned interface.

The router only has DHCP records - statics are not recorded

But its all gone these days...

My point being this is not Pi or wifi specific, it is an issue with 
network configuration



-- 
?There are two ways to be fooled. One is to believe what isn?t true; the 
other is to refuse to believe what is true.?

?Soren Kierkegaard


--- 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