From owner-freebsd-bluetooth@FreeBSD.ORG Wed Oct 31 08:49:12 2007 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFE1516A420 for ; Wed, 31 Oct 2007 08:49:12 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9398F13C4D5 for ; Wed, 31 Oct 2007 08:49:12 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.37] (a89-182-132-20.net-htp.de [89.182.132.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 8CDD9A44529 for ; Wed, 31 Oct 2007 09:16:02 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-bluetooth@freebsd.org Date: Wed, 31 Oct 2007 09:21:54 +0100 User-Agent: KMail/1.9.7 References: <200710301550.42036.wundram@beenic.net> <1193811512.853463.800.nullmailer@galant.ukfsn.org> In-Reply-To: <1193811512.853463.800.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710310921.54780.wundram@beenic.net> Subject: Re: Bluetooth PAN support for FreeBSD X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 08:49:12 -0000 Am Mittwoch, 31. Oktober 2007 07:18:32 schrieben Sie: > Do you have a source archive? Currently, I just have the sources locally, but I'm going to set up a mercurial archive for it some time this evening, when I (hopefully) get/have my new dedicated server. I'll mail the list when I'm done with that. Just on a short sidenote for now: the BNEP protocol implementation is mostly complete (except for some packet filtering things, which are totally unclear in the specification), but from the PAN profile I have only implemented PANU (i.e., phone) to NAP (btpand) support for the time being. All other setups, such as PANU to PANU, PANU to group adhoc or NAP to PANU (with the computer being the client) should easily be implementable on top of that, but aren't at the moment. -- Heiko Wundram Product & Application Development