From: tnp@invalid.invalid   
      
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)