MSGID: <10jhdgl$3a1kp$1@nntp.eternal-september.org> 98cdbcad   
   REPLY:  a4a66ca6   
   PID: PyGate 1.5.2   
   TID: PyGate/Linux 1.5.2   
   CHRS: ASCII 1   
   TZUTC: 0000   
   REPLYADDR attend@homesrv.net   
   REPLYTO 3:633/10 UUCP   
   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-di   
   able-the-dynamic-ip-address-after-assigning-a-static-ip-in-bullseye   
      
   --- 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 275 300 317 400 426   
   SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219   
   SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422   
   SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35   
   PATH: 633/10 280 229/426