From: Stefan Mischke <survivor@uni-paderborn.de>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Piconet Routing
Date: Mon, 18 Oct 2004 19:07:54 +0200 [thread overview]
Message-ID: <4173F86A.3050801@uni-paderborn.de> (raw)
Hello!
Since Bluetooth uses Time Division Duplex, a slave is not allowed to
talk to another slave in the same Piconet. The logical consequence must
be that the data is routed over the master. I've used l2test to check if
l2cap does this kind of routing automatically. It doesn't but rather
creates a new, direct acl link to the remote slave device (scatternet).
I don't know how it is with rfcomm, but I suppose it's the same. My
question: Is there any automatic Piconet Routing inside BlueZ or does
one have to implement it by oneself?
Regards
Stefan
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-10-18 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 17:07 Stefan Mischke [this message]
2004-10-18 17:33 ` [Bluez-devel] Piconet Routing Marcel Holtmann
[not found] ` <4174026A.1080209@uni-paderborn.de>
2004-10-18 23:42 ` Marcel Holtmann
2004-10-19 9:11 ` GUILLON Gabriel
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 9:51 M RISON
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=4173F86A.3050801@uni-paderborn.de \
--to=survivor@uni-paderborn.de \
--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