Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)

Marcel Holtmann
2005-08-22T17:50:46Z

Hi Claudio,

> After this long discussion I think control multiple apdaters
> will not be easy. If we register multiple paths will not be easy
> map device register/unregister to D-Bus paths. When the user
> remove the default dongle the D-Bus path should be unregistered and
> the default adapter should be changed.

never was and never will be ;)

> Considering that bluez daemons are using the BDADDR_ANY. The D-Bus
> services should use the same approach. I agree that the default
> adapter must go through the kernel.
>
> Is there a way/interface to change the default adapter in the kernel?

No. It has a simple route heuristic and normally uses the first adapter
that is marked as up and is not a raw device. Unless the destination is
not itself.

This means that the default adapter depends on the destination which is
not easy to configure.

Regards

Marcel