Subject: Re: [Bluez-devel] Error while setting RFCOMM security options
From: Marcel Holtmann <marcel@holtmann.org>
To: Julien Campana <juliencampana@yahoo.fr>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <1084285384.893.17.camel@fischer>
References: <1084285384.893.17.camel@fischer>
Content-Type: text/plain
Message-Id: <1084368321.25099.29.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Wed, 12 May 2004 15:25:22 +0200

Hi Julien,

> This programm outputs the following message: 
> WARNING can't set link Mode (reason: Protocol not available)
> 
> Why? The L2CAP protocol is available as well as the RFCOMM protocol on
> my machine (l2ping actually works and my program exchanges data over
> RFCOMM without any problem).
> 
> Am I wrong in the way of setting these security flags?

why do you think that you can set L2CAP options on a RFCOMM socket ;)

Regards

Marcel


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel