Re: Piconet Routing

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.
> > 
> >   
> TCP connections are also point to point, but since it's built on top
> of IP, it goes (transparently) over many routers. Before I tested it,
> I thought the link manager would take care of this. How does the
> communiction of many BT devices work in practice? Who manages this
> routing, since one device can only be point-to-point-connected to 2
> devices (an this doesn't work really smooth)? There must be one
> controlling instance. One cannot let the different applications handle
> this, can one?

this is true, but the problem is, that a slave does not know to which
other slaves a master is connected. There is no routing stuff like in IP
and you can't retrieve these information from the HCI layer.

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