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. > _______________________________________________ > email@example.com mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org > " > _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"