From: Christian Hennrich <tettokalle@hotmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] problems with connect()
Date: Thu, 08 Jan 2004 17:16:47 +0100 [thread overview]
Message-ID: <3FFD826F.5080808@hotmail.com> (raw)
Hi,
I'm working on a programm which uses sdp to connect only to PANU,
creating l2cap and bnep connections. First i start the master, that
inquires and then connects to the discovered devices (using sdp), that
are started as slaves. 2 slaves are connected(with one L2cap and one
Bnep for each slave). this works very fine. then i want to connect the
third and so on... but there is the problem: the third one can't connect
with sdp on or off. the connect(socket) command fails with the error:
Connect failed. Function not implemented(38).
on the slave machine is only one program started. i tried around with
different dongles, but they are not the problem. what is wrong? has
anybody some idea? i don't use fork. the sockets that are created(have
all different numbers(increasing)). is there any limitation of creating
sockets or something like this.
i think the problem is the master, because on the clients there are only
2 sockets created. i only have one dongle per pc.
regards Christian
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-01-08 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 16:16 Christian Hennrich [this message]
2004-01-08 17:35 ` [Bluez-devel] problems with connect() Marcel Holtmann
2004-01-09 14:04 ` Christian Hennrich
2004-01-09 14:10 ` 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=3FFD826F.5080808@hotmail.com \
--to=tettokalle@hotmail.com \
--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 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.