From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Link Mode
Date: Mon, 05 Mar 2007 13:35:07 +0100 [thread overview]
Message-ID: <1173098107.6638.12.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1173045518.989564.4714.nullmailer@galant.ukfsn.org>
Hi Iain,
> I am trying to write a compatible equivalent to the Link Mode socket
> options API for NetBSD, and I wonder if somebody can clarify some things
> for me since I can't find any documentation about this.
>
> I assume that RFCOMM_LM and L2CAP_LM are essentially the same, the
> following bits are defined:
from a bitwise perspective they are even the same as HCI_LM. The
different prefix is only exists to make the programs more cleanly.
> _LM_MASTER
> means we prefer to be master of the baseband link
It actually comes down to the HCI_Create_Connection command. This one
has a flag to indicate if a role-switch is allowed or not.
> _LM_AUTH
> means we want the baseband link to be authenticated
It means that a HCI_Authentication_Requested must succeed.
> _LM_ENCRYPT
> means we want the baseband link to be encrypted
It means that a HCI_Set_Encryption must be used to enable the
encryption.
> _LM_TRUSTED
> this seems unused, is there an intention?
Actually I can't remember what this was supposed to do. I think it
should be indicate that the device must be marked as trusted before
allowing a connection. However there is no way at the moment to mark a
device as trusted.
> _LM_RELIABLE
> signal error on unreliable link (means disconnect?)
It is basically only used in L2CAP to detect wrong ACL packets. This was
needed for the Bluetooth qualification testing.
> _LM_SECURE
> is this somehow different than (_LM_AUTH | _LM_ENCRYPT)?
It is authentication + encryption and on a successful connect at that
protocol level, it will also issue a HCI_Change_Connection_Link_Key.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-03-05 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 21:58 [Bluez-devel] Link Mode Iain Hibbert
2007-03-05 12:35 ` Marcel Holtmann [this message]
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=1173098107.6638.12.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@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