[Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave

Michael Schmidt
2004-09-05T13:47:37Z

Hi folks,

I'm experiencing the following behavior with BlueZ and L2CAP:

After establishing an L2CAP connection between two nodes, only the
master of this connection is still able to:

- perform periodic device inquiries (i.e. search other devices
in 'Periodic_Inquiry_Mode')
- perform inquiry scans (i.e. be visible for other searching devices)

However, I would like to be able to do this as slave as well (at least,
to perform inquiry scans as slave).

Now I'm wondering whether:

- this is a restriction of BlueZ or
- this is a restriction of my BT chipsets or
- this is a restriction of Bluetooth or
- I'm doing (configuring) something wrong...

My environment:

SuSE Linux 9.0: kernel 2.4.21, bluez-libs 2.4, bluez-utils-2.3

I have tested and verified this behavior with the BrainBoxes BL-500 and
BL-554 adapters.
I'd be very grateful if someone of you could shed some light on this topic.

Thanks in advance,

Michael

--
===========================================
Michael Schmidt
-------------------------------------------
Institute for Data Communications Systems
University of Siegen, Germany
-------------------------------------------
http: www.nue.et-inf.uni-siegen.de
===========================================