XPost: alt.comp.os.windows-11, alt.comp.microsoft.windows   
   From: bowman@montana.com   
      
   On Mon, 15 Dec 2025 04:22:26 -0700, Marian wrote:   
      
   > In summary, the problem to resolve is NOT "interference" or "movement",   
   > but the fact that the netsh output depends on what's stored in cache   
   > which itself has a temporal relationship to the last association time.   
   >   
   > This thread is seeking a solution to *that* Windows "netsh" problem.   
      
   nmcli on Linux does have a 'rescan' command. Running rescan and list on   
   the same machine, same location, again and again, will frequently report   
   different APs with different signal strengths.   
      
   Another laptop, 10' away, shows a few more although that vaires between   
   rescans. A laptop 4' away shows many more than the desktop.   
      
   I presume that the difference between machines is a combination of   
   location and the wifi device, but that doesn't explain the difference   
   between successive rescans on the same machine.   
      
   If netsh is broken, so is nmcli.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)