On Fri, 2015-02-06 at 10:47 +0800, Sheng-Jhih Jiang wrote: > hi, sorry for the late reply.
> >WPS should be added to NetworkManager (core daemon) first. It's not > >really necessary to add anything to nm-applet (client) at that point. > > Without the help of nm-applet to test the WPS flow, how can I confirm > the WPS functionality in NM is correct? you *can* implement support in nm-applet. But nm-applet merely uses the DBus interface of NetworkManager. So, the functionality must first be present in the DBus interface of NetworkManager core service. For testing and developing, it might be quicker to use DBus utilities such as d-feet, or write a test-client in python. -- e.g. http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/python/dbus > >these are linker errors. Apparently you try to link against an older > >version of libnm-util. Make sure, you link to the same version as the > >include headers. > > Thanks. I will check this. > > BTW, could you give me some instructions for problems belows > > In my plan, I will try to add the easiest scenario first: > i. press the pbc on AP > ii. NM trigger scan to know the AP is ready for WPS via PBC method NM/wpa_supplicant already scans repeatedly, but yes, you can trigger a new scan using the DBus method RequestScan() > iii. NM trigger the wpa_supplicant to start the PBC action > vi. the connection between STA(NM) and AP is constructed > > With the WPS patch in the first email, I believe that if the user > trigger a scan in > NM after the pbc of an AP is pressed, NM will know there is an AP ready for > WPS. > > But in iii), I don't know when the user select an AP to connect on the > nm-applet, where is the corresponding function call > in NM. I am trying to figure out the flow of triggering the > wpa_supplicant to connect to the selected AP from NM. I guess, you would have to add a DBus method like "NMDeviceWifi:WpsConnect()"? all the DBus invocation (server-side) are implemented named "impl_". Try: $ git grep '^impl_' > On Fri, Feb 6, 2015 at 5:56 AM, Thomas Haller <[email protected]> wrote: > > On Thu, 2015-02-05 at 22:36 +0800, Sheng-Jhih Jiang wrote: > > > > hi, > > > > > >> BTW, I think I must modify network-manager-applet for testing WPS, but > >> I also met some problems while building network-manager-applet. > > > > WPS should be added to NetworkManager (core daemon) first. It's not > > really necessary to add anything to nm-applet (client) at that point. > > > > > >> I already built and installed NetworkManage 1.1.0 obtained from git > >> master branch. > >> When I want to build network-manager-applet, some errors shows as below. > >> I found that these function prototypes in NetworkManager were > >> controlled by "NM_AVAILABLE_IN_0_9_10" > >> But the version of NM I installed was 1.1.0, it's even newer than > >> 0.9.10, I don't know why these errors occurred. > > > > "NM_AVAILABLE_IN_0_9_10" affects compilation (not linking). So, > > compilation works for you correctly. > > > > > >> " > >> make[4]: Entering directory > >> `/home/awkjiang/temp/network-manager-applet/src' > >> CCLD nm-applet > >> nm_applet-applet.o: In function `get_device_class': > >> /home/awkjiang/temp/network-manager-applet/src/applet.c:280: undefined > >> reference to `nm_device_team_get_type' > >> nm_applet-applet.o: In function `applet_find_active_connection_for_device': > >> /home/awkjiang/temp/network-manage > > > > these are linker errors. Apparently you try to link against an older > > version of libnm-util. Make sure, you link to the same version as the > > include headers. > > > > For example, try setting the search path for pkgconfig > > > > export PKG_CONFIG_PATH="$PREFIX/lib/pkgconfig" > > > > > > > > Thomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
