Re: [Bluez-devel] L2CAP: One failing connection hurts others?

Marcel Holtmann
2004-09-14T21:12:06Z

Hi Stefan,

> > your firmware is HCI 16.4 which is good, but you are going to create a
> > scatternet on your client and that can be the problem. Looks like this
> > is an internal problem of the CSR firmware.
> You mean the dongles try to create a scatternet (with packet routing
> and so on) on their own? I always thought a scatternet has to be
> implemented outside the hard-/firmware.

no, you only create a scatternet. This means when one device must be
member of two different piconets.

> Is there a way to upgrade it? Are there better dongles the University
> could buy?

You can upgrade the D-Link DBT-120 Rev. B3 with the Apple firmware
update package to HCI 18.1.

> > Try to introduce some delays
> > between the connections and see if that helps.
> >
> I'm experimenting with delays and timeouts for three days now. It
> helps... a bit, but not really good. I just tried to switch
> master-slave, but it doesn't really help.

I think you should avoid the role-switching and keep the listening
applications as slaves. In this case the client creates the piconet and
can keep both servers in the same piconet.

> One year ago, I wrote another Location Awareness App on top of a
> modified JBlueZ and it just used ACL links to measure RSSI and LQ. It
> worked. I probably have to take care of the ACLs myself (does L2CAP
> use existing ACLs?). The only drawback: The App has to run as root :(.

The L2CAP creates the same ACL links, so this can't be the problem.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net