Re: Wireless API

2013-10-15 Thread Eric Turgeon
Hi Adrian

That is OK,  I have download the source code of Wifimgr, it use ifconfig. I
was using ifconfig wlan0 scan, it was to slow to display info, but in the
Wifimgr code they use
 ifconfig -v wlan* list scan and ifconfig wlan* list scan. I also found
wifimgr calculate S:N to find the percentage of the connection, it is (S -
N) * 4.
I have also read further ifconfig manual, I suppose ifconfig will be a kind
of API for my work.

Thanks

Eric


On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd adr...@freebsd.org wrote:

 Not sure. I've not really focused on the userland side of the API at all
 I'm sorry.

 Thanks,


 -adrian



 On 13 October 2013 17:09, Eric Turgeon ericturgeon@gmail.com wrote:

 Were is the documentation for that API.


 On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd adr...@freebsd.org wrote:

 What do you mean like connection percentage ?

 Do you mean like signal strength? If so, then yes.

 You can then make some basic heuristic guesses mapping signal level /
 RSSI to a connection percentage based on some assumptions. For example, you
 could look at the minimum RSSI required to guarantee some decent stability
 at each receive/transmit rate (from 1mbit-54mbit, then MCS1-MCS23) and
 then use that to map out connection percentage (where stable at MCS0 /
 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.)

 HTH,



 -adrian



 On 13 October 2013 16:08, Eric Tugeon ericturgeon@gmail.com wrote:

 Hi,
 I work on a Python GTK network manager for FreeBSD/GhostBSD, it will
 look similar to 
 https://projects.gnome.org/**NetworkManager/https://projects.gnome.org/NetworkManager/.
 I want to know if we have wireless API like connection percentage?
  __**_
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**wirelesshttp://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscribe@**
 freebsd.org freebsd-wireless-unsubscr...@freebsd.org





 --
 *Eric Turgeon
 **GhostBSD project*
 Office location:
 1-11 connaught
 Moncton NB Canada
 www.ghostbsd.org http://www.ghostbsd.org/





-- 
*Eric Turgeon
**GhostBSD project*
Office location:
1-11 connaught
Moncton NB Canada
www.ghostbsd.org http://www.ghostbsd.org/
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: Wireless API

2013-10-15 Thread Adrian Chadd
I'd rather that the ioctl API be used, rather than the output of 'ifconfig'.

It's likely about time the ioctl API was turned into a library for userland
to use. That way it could be imported into python/etc via C bindings.

Thanks,



-adrian



On 15 October 2013 04:16, Eric Turgeon ericturgeon@gmail.com wrote:

 Hi Adrian

 That is OK,  I have download the source code of Wifimgr, it use ifconfig.
 I was using ifconfig wlan0 scan, it was to slow to display info, but in
 the Wifimgr code they use
  ifconfig -v wlan* list scan and ifconfig wlan* list scan. I also
 found wifimgr calculate S:N to find the percentage of the connection, it is
 (S - N) * 4.
 I have also read further ifconfig manual, I suppose ifconfig will be a
 kind of API for my work.

 Thanks

 Eric


 On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd adr...@freebsd.org wrote:

 Not sure. I've not really focused on the userland side of the API at all
 I'm sorry.

 Thanks,


 -adrian



 On 13 October 2013 17:09, Eric Turgeon ericturgeon@gmail.com wrote:

 Were is the documentation for that API.


 On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd adr...@freebsd.orgwrote:

 What do you mean like connection percentage ?

 Do you mean like signal strength? If so, then yes.

 You can then make some basic heuristic guesses mapping signal level /
 RSSI to a connection percentage based on some assumptions. For example, you
 could look at the minimum RSSI required to guarantee some decent stability
 at each receive/transmit rate (from 1mbit-54mbit, then MCS1-MCS23) and
 then use that to map out connection percentage (where stable at MCS0 /
 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.)

 HTH,



 -adrian



 On 13 October 2013 16:08, Eric Tugeon ericturgeon@gmail.comwrote:

 Hi,
 I work on a Python GTK network manager for FreeBSD/GhostBSD, it will
 look similar to 
 https://projects.gnome.org/**NetworkManager/https://projects.gnome.org/NetworkManager/.
 I want to know if we have wireless API like connection percentage?
  __**_
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**wirelesshttp://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscribe@**
 freebsd.org freebsd-wireless-unsubscr...@freebsd.org





 --
 *Eric Turgeon
 **GhostBSD project*
 Office location:
 1-11 connaught
 Moncton NB Canada
 www.ghostbsd.org http://www.ghostbsd.org/





 --
 *Eric Turgeon
 **GhostBSD project*
 Office location:
 1-11 connaught
 Moncton NB Canada
 www.ghostbsd.org http://www.ghostbsd.org/

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: Wireless API

2013-10-15 Thread Kris Moore
On 10/15/2013 11:15, Adrian Chadd wrote:
 Well, up until now the interactions have all been via the ioctl API or the
 ifconfig command. Both are cumbersome.

 There's a decent amount of library code in ifconfig for wifi and regulatory
 related stuff. It could be broken out into a public library..

 -adrian


Yea, our PC-BSD network utils are using a mixture of C ioctl and
ifconfig parsing, +1 for a public library API at some point ;)

-- 
Kris Moore
PC-BSD Software
iXsystems

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: Wireless API

2013-10-15 Thread Adrian Chadd
The wireless API used to be the same as what's in Linux. So, in theory, we
could just use anything that used Linux wireless extensions. Save, of
course, the API drift.

So, you could just write a full wireless manager that used the ioctl API
for the basic manipulation of the VAP (eg link status, current association
state, etc) and the wpa_supplicant socket API for talking to the supplicant
for the scan list, telling it which SSID to try associating to, etc.


-adrian



On 15 October 2013 09:39, Sam Fourman Jr. sfour...@gmail.com wrote:

 On Oct 15, 2013 12:26 PM, Kris Moore k...@pcbsd.org wrote:
 
  On 10/15/2013 11:15, Adrian Chadd wrote:
   Well, up until now the interactions have all been via the ioctl API or
 the
   ifconfig command. Both are cumbersome.
  
   There's a decent amount of library code in ifconfig for wifi and
 regulatory
   related stuff. It could be broken out into a public library..
  
   -adrian
  
 
  Yea, our PC-BSD network utils are using a mixture of C ioctl and
  ifconfig parsing, +1 for a public library API at some point ;)

 This really is somthing that should be brought to the FreeBSD foundations
 attetion.
 As an example the network manager in Gnome hasn't been ported for years,
 and I belive the largest part of the reason is lack of an API.

 The importance of this really can't be underestimated.
 Is there a formal way, to propose a project to the FreeBSD foundation?

 Sam Fourman Jr.
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
 

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: Wireless API

2013-10-14 Thread Adrian Chadd
Not sure. I've not really focused on the userland side of the API at all
I'm sorry.

Thanks,


-adrian



On 13 October 2013 17:09, Eric Turgeon ericturgeon@gmail.com wrote:

 Were is the documentation for that API.


 On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd adr...@freebsd.org wrote:

 What do you mean like connection percentage ?

 Do you mean like signal strength? If so, then yes.

 You can then make some basic heuristic guesses mapping signal level /
 RSSI to a connection percentage based on some assumptions. For example, you
 could look at the minimum RSSI required to guarantee some decent stability
 at each receive/transmit rate (from 1mbit-54mbit, then MCS1-MCS23) and
 then use that to map out connection percentage (where stable at MCS0 /
 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.)

 HTH,



 -adrian



 On 13 October 2013 16:08, Eric Tugeon ericturgeon@gmail.com wrote:

 Hi,
 I work on a Python GTK network manager for FreeBSD/GhostBSD, it will
 look similar to 
 https://projects.gnome.org/**NetworkManager/https://projects.gnome.org/NetworkManager/.
 I want to know if we have wireless API like connection percentage?
  __**_
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**wirelesshttp://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscribe@**
 freebsd.org freebsd-wireless-unsubscr...@freebsd.org





 --
 *Eric Turgeon
 **GhostBSD project*
 Office location:
 1-11 connaught
 Moncton NB Canada
 www.ghostbsd.org http://www.ghostbsd.org/

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org