All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: linux-bluetooth@vger.kernel.org
Subject: PAN with bluez-utils-3
Date: Tue, 31 Mar 2009 13:29:26 +0200	[thread overview]
Message-ID: <49D1FE96.1090200@binarywings.net> (raw)

Hi list!

I used to have a working private area network (pan) over bluetooth.
However, since the update to bluez-utils-3.36, it doesn't work anymore.

I especially want to get rid of the old daemons because, as I understand
it, they are deprecated. However, I just can't find satisfying
documentation on the new structure and config files.

I don't want to go into detail on what exactly doesn't work at the
moment because I really just guessed how I had to configure everything.

So my question is: Does anyone have a working set of configuration files
for newer bluez-utils? Preferably something related to the roles GN or  NAP.

Thanks in advance!
Florian Philipp

             reply	other threads:[~2009-03-31 11:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 11:29 Florian Philipp [this message]
2009-03-31 13:44 ` PAN with bluez-utils-3 Luiz Augusto von Dentz
2009-04-01  6:55   ` Florian Philipp
2009-04-02  6:02     ` Florian Philipp
2009-04-02 17:28       ` Luiz Augusto von Dentz
2009-04-15 14:44         ` Florian Philipp
2009-04-16  8:49           ` CreatDevice signal should be emitted at function create_stored_device_from_profiles() in src/adapter.c Xu, Martin
2009-04-16 13:31             ` [connman] " Luiz Augusto von Dentz
2009-04-17  0:43               ` Xu, Martin
2009-04-17  1:47                 ` Xu, Martin
2009-04-17 12:46                   ` Luiz Augusto von Dentz
2009-04-17 13:04                     ` Bastien Nocera
2009-04-17 13:08                       ` Johan Hedberg
2009-04-20  0:57                     ` Xu, Martin

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=49D1FE96.1090200@binarywings.net \
    --to=lists@binarywings.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.