Date: Sat, 28 Apr 2007 20:10:21 -0700 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Iain Hibbert" <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth PAN Message-ID: <bb4a86c70704282010m44bc8714n9303a8d7514ed9ae@mail.gmail.com> In-Reply-To: <1177747653.710071.9561.nullmailer@galant.ukfsn.org> References: <462C5A20.3030300@shadow-security.net> <bb4a86c70704231153i7fe71bc9g82c8b8cb99b9868f@mail.gmail.com> <1177747653.710071.9561.nullmailer@galant.ukfsn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/28/07, Iain Hibbert <plunky@rya-online.net> wrote: > On Mon, 23 Apr 2007, Maksim Yevmenkin wrote: > > > p.s. bluetooth pan is not supported under freebsd > > FWIW there is no reason it should not work, if somebody would write a > userland PAN program that works as a bridge between an L2CAP socket and a > tap(4) device (or tun(4), I'm not sure of the difference). The BNEP bnep should use tap(4), imo, as bnep is ethernet encapsulation protocol. > protocol looks very simple (just encapsulate ethernet frames in L2CAP > packets) - alas I currently have no hardware that supports PAN profiles > otherwise I would write a daemon, maybe I will look into that over the > summer.. standard windows bluetooth stack supports pan. hopefully i will have enough free time in the next months or so, to bring sco, pan etc. support to freebsd tree. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70704282010m44bc8714n9303a8d7514ed9ae>