Skip to content
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

Open
javier-lopez opened this issue Feb 1, 2015 · 6 comments
Open

Comments

@javier-lopez
Copy link
Contributor

Hi,

connman_curses doesn't reuse AP settings on different wireless interfaces (it may be applicable to other technologies).

Testcase

  1. Make available two or more wireless interfaces to the system
  2. Disconnect from all wireless networks
  3. Launch connman_curses
  4. Select the wifi technology
  5. Select an AP with the better range detection wireless interface
    • connman_curses asks the AP password/information
    • Fill the missing information and connect
  6. Disconnect, and unplug the used wireless interface
  7. Select the previous AP with the better range detection wireless interface
    • connman_curses ask the AP password/information

Expected 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)

@alan-mushi
Copy link
Contributor

Hi,

Yes it would be nice, the thing though is that it's connman's job, not the interface's.
You should open a bug or write to the connman mailing list about it.

@pfl
Copy link

pfl commented Feb 2, 2015

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.

@jobol
Copy link
Contributor

jobol commented Feb 2, 2015

@pfl It seems to me that your remarks here are related to #5. What about password storing? Is there a required but missing argument to connect with registered password? Or to register it?

@pfl
Copy link

pfl commented Feb 2, 2015

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.

@jobol
Copy link
Contributor

jobol commented Feb 2, 2015

what component is provisionning the passphrase in the config file?

@pfl
Copy link

pfl commented Feb 2, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants