home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.os.windows-10      Steaming pile of horseshit Windows 10      197,671 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 195,824 of 197,671   
   Marian to Paul   
   Re: OT? Can my neiighbor, whose wifi I'm   
   27 Nov 25 16:01:38   
   
   XPost: alt.comp.os.windows-11   
   From: marian@dumbshits.com   
      
   On Wed, 26 Nov 2025 13:43:36 -0500, Paul wrote:   
      
   >> The box has been there for weeks but I don't restart the laptop very   
   >> often. Later I'll restart again with the box in place and see if it   
   >> connects to my neighbor.   
   >>>   
   >>>   
   >   
   > Your activities are partially hidden via https:// .   
   >   
   > That is why your banking password is safe.   
   >   
   > To hide the addresses, you could use a VPN. Then all   
   > the packets would have the VPN address as their destination,   
   > before the packets are decapsulated.   
      
   I looked it up for the OP, where this command supposedly tells Windows not   
   to automatically connect to any given SSID, (even if it's open or   
   previously saved). That alone should solve his connection problems.   
    netsh wlan add filter permission=block ssid="OPEN_SSID" network   
   ype=infrastructure   
      
   If that command doesn't work, given the OP is "connecting" to a neighbor's   
   Wi-Fi "by accident", then it logically most likely is set to open. On   
   Windows 10, you can forget that access point connection credentials with   
    Settings > Network & Internet > Wi-Fi > Manage known networks.   
      
   The OP can select that open AP SSID and in "Properties" he can toggle the   
   "Connect automatically when in range" setting from on, to off.   
   Unfortunately, he will always see the neighbor's broadcast access points.   
      
   What I'd like to write, if I knew what the commands were, is a script on   
   Windows that ignores all the known neighborly Wi-Fi access point SSIDs.   
      
   To prioritize his own access points, the OP can set it to "Connect   
   automatically" when in range, although that setting has adverse privacy   
   ramifications on a laptop (but not on a desktop) if the OP's SSID is not   
   being broadcast (so as to not be uploaded to Google/Mozilla for their   
   public databases (with or without _nomap) by every rude uncaring   
   Apple/Android owner who drives by his house.   
      
   In summary, my suggestion for the OP is to   
    a. Forget the network in Settings, and then   
    b. Add the block filter so Windows won't reconnect   
       (even if the OP clicks it accidentally).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca