MSGID:  85ba6edc
REPLY: <10ipai0$39s0k$1@dont-email.me> 19b61e98
PID: PyGate 1.5.2
TID: PyGate/Linux 1.5.2
CHRS: CP437 2
TZUTC: 1100
REPLYADDR zsd@jdvb.ca
REPLYTO 3:633/10 UUCP
On 2025-12-27 at 15:03 AST, 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?

Just in case that question was directed at me...

No, the Pi thought two IPs were associated with the one and only wifi card.
(In fact, I discovered which device it was by ssh-ing in after nmap told me
that it was listening on the sshd port.)

                        Jim

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