XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10   
   From: this@ddress.is.invalid   
      
   nospam  wrote:   
   > In article , Frank Slootweg   
   >  wrote:   
   >   
   > > > > > > >> You have a device that allows settings for one access point to   
   > > > > > > >> influence   
   > > > > > > >> the settings for any or all other access points?  It's faulty.   
   > > > > > > >   
   > > > > > > > while it 'can' do that, it's not needed. setting a different   
   > > > > > > > configuration for every ssid is not only nuts, but it's asking   
   for   
   > > > > > > > problems.   
   > > > > > >   
   > > > > > > However, that is exactly what Android does. And Windows. And Linux.   
   > > > > > > Each   
   > > > > > > SSID gets its own independent configuration.   
   > > > > >   
   > > > > > strange how leaving it at its default (dhcp) works on any ssid   
   without   
   > > > > > any need for independent configs.   
   > > > >   
   > > > >   Ever heard of keys/passwords?   
   > > >   
   > > > sure. what about it? that has nothing to do with leaving it on dhcp.   
   > >   
   > >   Sigh!   
   > >   
   > >   Maybe the fact that they *do* need "independent configs"?   
   >   
   > which is issued by the dhcp server.   
      
     *Except* for the key/password for the SSID in question.   
      
   > as i said, leave the device set to dhcp and all is good.   
      
     Of course, but you *still* need, *multiple* "independent configs".   
      
   > ssid passwords are separate and not relevant.   
      
     SSID password/keys are part of the "config" on the device and because   
   most if not all SSID/password combinations will be unique, you *will*   
   have *multiple* "independent configs", whether nospam likes/admits it or   
   not.   
      
     QED.   
      
     HTH.HAND. EOD. NK.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)