MSGID:  a071e396   
   REPLY: <10j335s$2gptg$10@dont-email.me> 26a4ee5c   
   PID: PyGate 1.5.2   
   TID: PyGate/Linux 1.5.2   
   CHRS: ASCII 1   
   TZUTC: 1100   
   REPLYADDR zsd@jdvb.ca   
   REPLYTO 3:633/10 UUCP   
   On 2025-12-31 at 07:58 AST, The Natural Philosopher    
   wrote:   
   > On 30/12/2025 21:07, Jim Diamond wrote:   
   >> All good thoughts, thanks.  But...   
   >> - There is no dhcp client running (at least by the time I am able to ssh in   
   >>    to the machine after it boots).   
   >> - All /etc/network/interfaces does is source any files in interfaces.d,   
   >>    and there are no files there.   
   >> - "sudo locate systemd.network" only shows the man page.   
   >> - the "mystery" IPv4 address doesn't show up anywhere in the   
   >>    /etc/NetworkManager directory or sub-directories.   
   >>    
   >> I guess the mystery continues.   
   >   
   > That was where I got to with my one.   
   >   
   > At some stage that mobo died and I took the opportunity to switch mobos    
   > and install an updated linux version, using a GUI and network manager to    
   > set up the fixed IP, and the problem vanished.   
      
   > If you can do a fresh install its probably the shortest route.   
      
   That will be a consideration, should push come to shove.  So far, this   
   mystery IP hasn't caused any problems, but it is anomalous, which is   
   bothersome.   
      
   > Now even if its headless there is a CLI to network manager and you might    
   > investigate that.   
      
   > It's called in a fit of stunning originality, 'nmcli'   
      
   > Try   
   > #nmcli device show   
      
   Yes, I know about nmcli and even use it occasionally.  Thanks.   
      
   > Also ifconfig -a should show up any active interfaces on odd addresses.   
      
   > BUT IIRC I never could identify that interface that way - it seemed to    
   > be some sort of low level zombie.   
      
   > It existed in the router DHCP table, showing it had been issues by the    
   > router in response to a request from the machine, but it only ever    
   > responded to pings, IIRC.   
      
   > No listening process beyond that was ever bound to it.   
      
   > I assumed it was some bug either induced by me hand editing files that    
   > network manager was supposed to edit, or as a changeover from earlier    
   > methods of setting up IP, not fully ignored by the new NM control system   
      
   > All I know is that rigorous adherence to the GUI CLI on a fresh install    
   > eliminated it. Whether it was one or the other factor that was crucial,    
   > I cannot say.   
   > As with most transient bugs, life is to frikkin short...   
      
   I agree 100% with that.   
      
   > I am sorry I cannot help beyond noting that yes, I have seen it happen,    
   > and no, I cant reproduce it any more, and at a given point it vanished,    
   > never to reappear...   
      
   Well, I haven't seen my mystery addr recently.  Maybe a neutrino hit   
   the wrong spot during boot.   
      
                                   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 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