From: zsd@jdvb.ca   
      
   On 2026-01-05 at 18:21 AST, attend  wrote:   
   > On 27/12/2025 17:34, Jim Diamond wrote:   
   >> I was looking at my network and discovered an IP which I didn't know about;   
   >> after a few seconds of investigation I discovered that one of my Pis (which   
   >> is on wifi only, and only has one wifi card) has two IPs.   
      
   >> Two of my other Pis are running the same version of Raspberry Pi OS (i.e.,   
   >> "Debian GNU/Linux 12 (bookworm)").  They don't do this.   
      
   >> Looking around the net, there are claims that this is because Pis might try   
   >> to netboot, and that later on in the boot process they also get their usual   
   >> IP the "usual" way.  (In my case I am using networkmanager.)   
      
   >> I can't imagine what I did to make one of my Pis want to (try to) netboot.   
      
   >> 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?   
      
   >> Thanks.   
   >> Jim   
      
   > I had smililar problem when I upgraded to Bullseye. My solution was   
   > deleted connman package.   
      
   > Refer to   
   > https://raspberrypi.stackexchange.com/questions/133318/how-to-   
   isable-the-dynamic-ip-address-after-assigning-a-static-ip-in-bullseye   
      
   Thanks for the pointer, but that wasn't it.   
      
   The system in question (as well as my other systems) doesn't (respectively,   
   don't) have connman installed.   
      
   (I have a feeling I might not have named a piece of software "connman",   
   even though I can imagine where they got that name.)   
      
                                   Jim   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)