|
Re: Piconet Routing: msg#00061linux.bluez.devel
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 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Piconet Routing: 00061, Stefan Mischke |
|---|---|
| Next by Date: | Sharing link keys with windows?: 00061, Fred Schaettgen |
| Previous by Thread: | Piconet Routingi: 00061, Stefan Mischke |
| Next by Thread: | Re: Piconet Routing: 00061, Marcel Holtmann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |