public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* specifying client-side link mode properties before connect()
@ 2004-03-31 14:42 Stephen Crane
  2004-03-31 14:52 ` [Bluez-devel] " Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Crane @ 2004-03-31 14:42 UTC (permalink / raw)
  To: bluez-devel; +Cc: marcel

Hi,
[I think I may have asked something along these lines before, but I
can't remember what the outcome was...]

I have a server application which can specify the link mode requirements
of incoming connections using setsockopt(sock, SOL_L2CAP, L2CAP_LM, opt,
sizeof(opt)). This works fine, if a client can't meet the requirements,
no connection is made and the server's accept() sees nothing.

However I'd now like to be able to specify these requirements to the
connect() call on the client-side. That is, I'd like to call setsockopt
specifying the client's requirements (master, auth, encrypt) before
calling connect(). While I can /do/ this, the LM parameters seem to have
no effect. For example, I can set the L2CAP_LM_MASTER flag on both
sides, yet a connection is still established.

I suppose my question really is: are there any plans to implement this? 
Or is the usual answer (to send a patch) the correct one :-)?

Thanks,
Steve
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bluez-devel] Re: specifying client-side link mode properties before connect()
  2004-03-31 14:42 specifying client-side link mode properties before connect() Stephen Crane
@ 2004-03-31 14:52 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-03-31 14:52 UTC (permalink / raw)
  To: Stephen Crane; +Cc: BlueZ Mailing List

Hi Stephen,

> I have a server application which can specify the link mode requirements
> of incoming connections using setsockopt(sock, SOL_L2CAP, L2CAP_LM, opt,
> sizeof(opt)). This works fine, if a client can't meet the requirements,
> no connection is made and the server's accept() sees nothing.
> 
> However I'd now like to be able to specify these requirements to the
> connect() call on the client-side. That is, I'd like to call setsockopt
> specifying the client's requirements (master, auth, encrypt) before
> calling connect(). While I can /do/ this, the LM parameters seem to have
> no effect. For example, I can set the L2CAP_LM_MASTER flag on both
> sides, yet a connection is still established.

you can set the link mode, but the connection establishment procedure
dont't care about it.

> I suppose my question really is: are there any plans to implement this? 
> Or is the usual answer (to send a patch) the correct one :-)?

>>From my side I have no plan to implement it, but if you will do the work
and the patch don't break any other behaviour, I am going to apply it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-31 14:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-31 14:42 specifying client-side link mode properties before connect() Stephen Crane
2004-03-31 14:52 ` [Bluez-devel] " Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox