D-Bus Documentation

[Dan Williams]

On Tue, 2008-07-22 at 11:41 +0530, Kiran Kulkarni wrote:
> Actually I was using WPA supplicant to code a program which will connect
> to the wireless network as soon as a device is powered. I know that same
> thing is done by the Network Manager. But I was still coding some light
> weight application. I followed the steps
> 1) Get a signal from HAL for the network interface and add or get
> Interface from the WPA Supplicant using "addInterface" or
> "getInterface", which returns me a proxy for the interface
> 
> 2) Then using this proxy I scanned the network using "scan" and then
> after its success I did "scanResults" which gives the paths for the
> bssid's which can be used to read the "properties" adn displayed them
> 
> 3) after that I did "setAPScan" with value 1 and added a new network
> using the "addNetwork" which can be then used for further process.
> 
> 4) After obtaining the object path for the new network, I created proxy
> for that and then  I called "set" for that network and set the
> properties "key-mgmt" and "proto", But I am unable to set the properties
> like "bssid" and the "ssid".

You probably want to send those as byte arrays, not strings, because
they can contain embedded NULLs.  What language are you using, C,
Python, ...?

Dan

> 
> 5) Then I did "selectNetwork" with path as returned by the "addNetwork"
> 
> But My problem is that I am unable to set "ssid" and "bssid" for the new
> network and because of that I unable to connect to the existing AP.
> Plz help me out here....
> 
> Waiting for the reply
> 
> On Mon, 2008-07-21 at 10:20 -0400, Dan Williams wrote:
> > On Mon, 2008-07-21 at 11:23 +0530, Kiran Kulkarni wrote:
> > > I was going through the site and I found that, Documentation for the
> > > ctrl_iface is available. But I was looking for D-Bus interface, So It
> > > will be great if somebody send me the documentation of the D-Bus.
> > 
> > There isn't any at the moment, but it closely follows the ctrl_iface
> > documentation.  Part of the problem is that since it's pretty much
> > hand-coded libdbus, it doesn't support introspection, and thus the
> > documentation is all manual labor.  I've had some ideas to rework the
> > interface to be more dbus-like, but until that point there really should
> > be documentation for the existing interface.  I can try to start writing
> > some up.
> > 
> > In the mean time, feel free to ask questions and I'll do my best to
> > answer them.  There's also wpa_supplicant/examples/wpas-test.py which
> > gives a quick overview of using the dbus interface via python.
> > 
> > Dan
> > 
>