Subject: Re: [Bluez-devel] Piconet Routing
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <survivor@uni-paderborn.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <4173F86A.3050801@uni-paderborn.de>
References: <4173F86A.3050801@uni-paderborn.de>
Content-Type: text/plain
Message-Id: <1098120822.11765.5.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Mon, 18 Oct 2004 19:33:42 +0200

Hi Stefan,

> 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?

you must do it by yourself, because even if the master manages to put
all devices into the same piconet the connections are point to point.

Regards

Marcel


-------------------------------------------------------
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