XPost: sci.geo.satellite-nav, alt.comp.os.windows-10   
   From: walterjones@invalid.nospam   
      
   Andy Burns  wrote   
      
   >>  From that thread way back in January 2016 that Andy just referred to above.   
   >>   *Are we all handing to Google the SSID of our home routers?*   
   >   
   > Google do "age-out" BSSIDs that haven't been seen in some time, the   
   > original addresses I fed the API back then won't return a result now.   
      
   Thank you for that thread, as there was a lot then that is apropos now.   
   Yes. I know they age out, as I tested it myself by changing my SSID.   
      
   One thing I could not, for the life of me figure out then, and now, is how   
   _you_ managed to _change_ your home router's MAC (BSSID) address, Andy.   
      
   1. Jeff Liebermann said you could not "normally" change the AP BSSID.   
         
      
   2. Not without Linux, anyway... (we're talking the outward-facing MAC!)   
         
      
   3. But you seem to have changed the router's AP MAC (but did you really)?   
         
      "ifconfig wlan0 down   
       ifconfig wlan0 hw ether 08:BD:43:XX:XX:XX   
       ifconfig wlan0 up   
       on mine to change the MAC for the 2.4GHz Atheros radio   
       (as I'm SSH'ed over the 5.2GHz radio wlan1) and it seems   
       to have taken the new address"   
      
   I don't understand how you changed the hard-coded AP MAC (BSSID)   
   (which is what is seen by a wardriving car driving by your home).   
      
   Did you really change the outward-facing BSSID on your router?   
   How?   
   --   
   Because if you managed to change yours, I want to change mine.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)