From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Creating more than one instance of BlueZ
Date: Thu, 19 May 2005 15:06:40 +0200 [thread overview]
Message-ID: <1116508000.24921.19.camel@pegasus> (raw)
In-Reply-To: <20050519120627.77301.qmail@web8303.mail.in.yahoo.com>
Hi Mayank,
> I am still looking for a reply...
it seems that I missed your post. Sorry for that, but this can happen
some time.
> This is very necessary since this is the deterrent
> that I am facing during development process.
>
> Cause I now do not have access to a test PC.
BlueZ connections are always established with a source (local) and with
a destination (peer) address. So you can create connection between two
local device, but you must make sure that the source address is the
address of the other dongle. The only think where this not really works
is BNEP, because the kernel will route the TCP/IP traffic over the
loopback interface.
The instances question is non-sense, because there is always only one
instance of BlueZ running (like one TCP/IP, USB, SCSI, Firewire etc.),
but this instance is capable of handling more than one local device.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-19 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 12:06 [Bluez-devel] Creating more than one instance of BlueZ Mayank Batra
2005-05-19 12:56 ` Brad Midgley
2005-05-19 13:06 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 7:57 Mayank Batra
2005-05-20 8:17 ` Marcel Holtmann
2005-05-20 14:10 ` Brad Midgley
2005-05-15 12:33 Mayank Batra
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=1116508000.24921.19.camel@pegasus \
--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 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.