From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pand seem to ignore any pin configurations
Date: Sat, 07 May 2005 22:35:44 +0200 [thread overview]
Message-ID: <1115498144.9031.19.camel@pegasus> (raw)
In-Reply-To: <200505072203.45598.rdorsch@web.de>
Hi Rainer,
> I have setup a PAN network with a NAP (bluez-utils 2.15/kernel 2.6.7) and a
> PANU (bluez-utils/kernel-2.6.8). Each has an usb bt dongle and runs Debian
> sarge. Surprisingly, they seem to ignore any pin configuration. If there is
> good documentation on this somewhere, I would be happy with a pointer.
>
>
> My assumption is that the PANU provides a PIN and NAP needs to confirm it.
>
> My first problem is that I do not understand, where to provide a PIN on the
> PANU.
start pand with --encrypt on the NAP side. While looking at it, I
realized that the --auth option is missing. However --encrypt should
imply --auth by definition of the Bluetooth specification.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-05-07 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 20:03 [Bluez-users] pand seem to ignore any pin configurations Rainer Dorsch
2005-05-07 20:35 ` Marcel Holtmann [this message]
2005-05-07 21:39 ` Rainer Dorsch
2005-05-07 22:02 ` Marcel Holtmann
2005-05-08 13:08 ` Rainer Dorsch
2005-05-08 13:36 ` Marcel Holtmann
2005-05-08 15:27 ` Rainer Dorsch
2005-05-08 15:46 ` Marcel Holtmann
2005-05-08 16:24 ` Rainer Dorsch
2005-05-08 16:31 ` 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=1115498144.9031.19.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.