XPost: alt.comp.os.windows-10   
   From: nospam@nospam.net   
      
   Zaghadka wrote:   
      
   > My mistake then. I didn't think mine had the ability to configure a   
   > static IP for the router. You can do it for the WAN port, but that's not   
   > the same thing. I thought mine was hardcoded to be 192.168.0.1.   
      
   I used to set my gateway to 10.20.30.40 because I thought, at the time,   
   that anyone could "guess" that it's 192.168.{0,1}.1 but over time, it   
   became a pain to constantly change all the defaults so I let it go.   
      
   I used to change the router MAC addresses for the same reason, but then I   
   realized you can't change the _one_ MAC that matters most for privacy.   
      
   For most of us (all of us?) the incoming WAN IP address is handed to us by   
   the ISP, where mine is a WISP so mine comes to me from a variety of access   
   points, all of which are miles away (so my WAN is set to get it by DHCP).   
     Typical range is about 10 miles   
      
   Given most of us are using MAC randomization now, that negates the   
   "assignment" of a static IP on the router to be handed to devices.   
     Random MAC on every connect   
      
   This is particularly pernicious when you have an iPad as Android handles   
   the MAC randomization better (IMHO) in that Android 10 made it the default   
   for MAC randomization per SSID (which routers can easily handle); but   
   Android 11 added the capability (which I use all the time) for MAC   
   randomization per connection (which routers have a hard time handling).   
      
   Hence, for a "static IP address" on my Android, I make that request on the   
   phone itself, using a set of IP addresses outside the router DHCP range.   
      
   I never fully understood how reserving IP addresses works, but if you   
   randomize your MAC address per connection, it's harder on the router.   
     Static/Reserved IP address   
      
   If you ask why you want a static IP address when you're randomizing the MAC   
   on every connections, it's because of Windows scripts I use with Android.   
     powershell hide-console trick   
      
   Some of those scripts use the Android unique serial number though, and   
   therefore those scripts which don't need a static IP address work anyway.   
     Connect over Wi-Fi sans USB   
      
   But many of the Windows networking scripts require the Android IP address.   
     Both sdcards mounted   
      
   These scripts are mostly needed when you're networking Android to Windows.   
     Android mnt as drive letter   
      
   Such that, for example, you download a file on Windows and it's on Android.   
     Windows Drive: === Android   
      
   By doing this magic, you can now just _slide_ APKs from Windows to Android   
   and they automatically install themselves, which makes setup really easy.   
     Drag APK from Windows   
      
   Of course, I'm sure if you're a good Windows coder, you don't need a static   
   IP address in your scripts so then you can concentrate on solving the fact   
   that Android randomizes every Wi-Fi connection to the PC using a unique   
   so-called Wi-Fi Debugging Pairing Code (which changes on every connect).   
     Android 12 Wireless Pairing   
      
   If someone could solve _that_ problem, they'd be a genius in my book.   
   --   
   Posted out of the goodness of my heart to disseminate useful information   
   which, in this case, is to faithfully add related technical experience.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)