From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:52:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E2FB770 for ; Wed, 16 Oct 2013 04:52:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E1AB2FB5 for ; Wed, 16 Oct 2013 04:52:08 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id j15so301807qaq.13 for ; Tue, 15 Oct 2013 21:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=seNGPO8SnJ+3BvPxlu9yHFJ6apdvrMf69F1aKaC+UQs=; b=mR8vrcMNVKZQoR6j0oqdyElXgauRGRLefG2DyboCS3pcyIWp1LBRDRy9RnN/sf8Duo bo9lXrFuwRX9zNYifUQNgz2VfbmJcHqh618FB+ytHttRft9EisVHIOuRkyuyshYav9GR uJWoiy1BeMGx4hVu6kokQQFGb1UFT0f6EszlZUVUTnDNJSVynHICtrM2FWzXQijab4On 0qODAWMacKyBAEpT2r/DkILKEKMmYnol7lXilLOW1UfWeRPDO+DLJX8awrxB33Uaxm0d p5RF7KF+IUMHzrUptPfhP7HO+nbN8akjwm3LyHMQDRehOigQuEYNGXBFOMgU15OOYWcH KdLw== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr1120613qeb.74.1381899127007; Tue, 15 Oct 2013 21:52:07 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:52:06 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> <525D6CBA.4010101@pcbsd.org> Date: Tue, 15 Oct 2013 21:52:06 -0700 Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: "Sam Fourman Jr." Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Oct 2013 04:52:09 -0000 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. wrote: > On Oct 15, 2013 12:26 PM, "Kris Moore" 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-unsubscribe@freebsd.org > " >