public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gavin Glynn" <gglynn@hcvwireless.com>
To: <bluez-users@lists.sourceforge.net>, <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] PAND + DUND
Date: Fri, 9 Sep 2005 09:21:14 +1000	[thread overview]
Message-ID: <E1EDVht-00011o-Nf@mail.sourceforge.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

Hi All

 

I am trying to build an access point that supports both PAN and LAP
profiles. I was able to follow the instructions to create a PAND access
point using the Ethernet bridge technique
(http://bluez.sourceforge.net/contrib/HOWTO-PAN). I have searched all around
the web for instructions for incorporating DUND into this configuration, and
the best I have found is an out of date article from Ling-Jyh Chen
(http://www.cs.ucla.edu/~cclljj/interest/notes/bluez/pand_dund.html). Are
there any instructions for configuring the recent versions of Bluez to
support multiple Bluetooth devices using PAN and / or LAP? Any assistance
would be appreciated.

 

Regards

 

 

Gavin Glynn :-)

PS: I have been really impressed with the depth in the current
implementation of BlueZ and have managed to construct some interesting
software. As a developer, I find the lack of the formal documentation
describing the uses of the BlueZ utilities and the API available in the
BlueZ libraries a real issue. If the BlueZ implementation is to become
universally accepted by the development community, the BlueZ community will
need to work on this issue.

 

 


[-- Attachment #2: Type: text/html, Size: 4104 bytes --]

             reply	other threads:[~2005-09-08 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 23:21 Gavin Glynn [this message]
2005-09-08 23:34 ` [Bluez-devel] PAND + DUND Marcel Holtmann
2005-09-09 11:50   ` David Woodhouse
2005-09-09 12:21     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1EDVht-00011o-Nf@mail.sourceforge.net \
    --to=gglynn@hcvwireless.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox