-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passwords/settings are not shared between wireless interfaces #6
Comments
Hi, Yes it would be nice, the thing though is that it's connman's job, not the interface's. |
Services are stored per device in ConnMan so ConnMan will think of these as different networks. If the network is provisioned (see doc/config-format.txt in ConnMan sources), ConnMan will match the network across devices - but again store them per device. |
If the passphrase is provisioned in the .config file, it is used for any wifi network (from any device) that matches. If not, and the service is connected, the Agent is asked for the missing passphrase. |
what component is provisionning the passphrase in the config file? |
The provisioned .config file can be added by installing a package, writing/moving the .config file to it's location or by any other means necessary. It's up to the OS itself or the device's admin to provide any adequate means for placing the provisioning file into a the correct location in the filesystem so that ConnMan picks it up. |
Hi,
connman_curses
doesn't reuse AP settings on different wireless interfaces (it may be applicable to other technologies).Testcase
connman_curses
wifi technology
connman_curses
asks the AP password/informationconnman_curses
ask the AP password/informationExpected behavior
I think
connman_curses
should remember settings per essid (or maybe per AP Mac address) so it doesn't ask information already given. Doing so could also open the possibility (or not depending in the technical details) to fall back to another interface when the used interface isn't available (which may be when the interface driver crashes, when it gets unplugged or when the interface chip fries)The text was updated successfully, but these errors were encountered: