Hi,
Hello, found out about connman after having some problems with
connecting to a network with wicd, and it's awesome.
Since I liked it so much I started working on a Ruby library to
interface with the daemon and a bundled fancy CLI.
There is already (with newer version of connman) a nice CLI client named
connmanctl.
You might want to check it.
However, as far as I know, there is no ruby library to access connman so
that could interest
some people to get one.
Came over on the IRC channel yesterday but everyone was idling (or
quite possibly in another timezone) so I thought I'd ask through a
more asynchronous mean.
Most of us are usually present during the week-days, EU times.
In the CLI I'm making I wanted to list the wifi services with the
access point BSSID and the channel, but after digging through the API
documentation and looking at some GUIs that didn't have that feature I
came to realize there's no way to have access to that information.
Is there a way to get access to that? Maybe I just overlooked
something while digging through the documentation, but in the service
properties dict there's no such data, so I guess it's not there.
If there is no way is there a reason for its absence, and if there's
no reason, are patches welcome?
ConnMan hides whatever information which is never required for the
end-user and for the UI
itself. No-one needs the BSSID or the channel, seriously. This is up to
the wifi daemon and/or
the network management daemon (connman here) to handle such information
relevantly.
About BSSID, if you have 2+ AP sharing the same network (same SSID, same
security,
different channels) ConnMan will still show 1 network (and not 2+ BSSID
entries).
The user should not care what AP to select precisely: ConnMan and - in
this case -
Wpa_supplicant will ensure he gets connected to the best AP among those
(strongest signal, lowest noise, so it will pick up the proper AP/Channel).
The name of a wifi service is the wifi network's SSID. That's all what
needed to connect to it.
Depending on its security settings, connman will ask the credentials
through Agent API.
And for whatever low level stuff a user should never care about: connman
will handle it
(wifi roaming, storing the settings, etc etc...).
Also, be aware that ConnMan sorts the services for you: by technology
type, signal strength
(for wifi for instance) etc... so you should not have to care about that.
Br,
Tomasz
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
