[Users] bluetooth in CT

[openvz at bigfatdave.com]

Hi Klaus,

The manual explains how to grant a CT access to a device.  (Look at the
section on VPN, for example.)  I don't know whether or not that would
be sufficient for bluetooth, but if it is, it's a simple one-line fix.
Sockets, on the other hand, are normally autocreated by the programs
listening on them, and so should not need any setup at all (other than
getting the required programs to work, of course).

Klaus Maria Pfeiffer wrote:
->From: Klaus Maria Pfeiffer <kmp+openvz.users at kmp.or.at>
->To: users at openvz.org
->Date: Wed, 21 Jul 2010 07:10:34 +0200 
->Message-ID: <a3cih7-fpg.ln1 at news.kmp.or.at> 
>
>hi!
>
>I've tried to get bluetooth into my CT (debian unstable, HN on debian 
>stable 
>with some parts from testing or unstable, kernel is Linux lotte 2.6.26-2-
>openvz-amd64 #1 SMP Tue Mar 9 17:24:55 UTC 2010 x86_64 GNU/Linux).
>
>first of all, with the help of <http://wiki.openvz.org/USB_Printing_in_VE> 
>I 
>see my bluetooth usb stick in the CT:
>
>;===
>ve111:~# lsusb
>Bus 002 Device 036: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
>Dongle (HCI mode)
>;===
>
>but starting bluetooth with /etc/init.d/bluetooth start is not successful 
>as 
>I can see in /var/log/daemon.log:
>
>;===
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Bluetooth deamon 4.66
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Starting SDP server
>Jul 18 18:09:51 ve111 bluetoothd[6971]: opening L2CAP socket: Address 
>family 
>not supported by protocol
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Server initialization failed
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Starting experimental netlink 
>support
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Failed to allocate generic netlink 
>cache
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Failed to init netlink plugin
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Failed to open control socket: 
>Address family not supported by protocol (97)
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Can't init bnep module
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Failed to init network plugin
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Unable to start SCO server socket
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Failed to init audio plugin
>Jul 18 18:09:51 ve111 bluetoothd[6971]: Can't open HCI socket: Address 
>family not supported by protocol (97)
>Jul 18 18:09:51 ve111 bluetoothd[6971]: adapter_ops_setup failed
>;===
>
>but no problem in the HN:
>
>;===
>lotte:~# /etc/init.d/bluetooth start
>Starting bluetooth: hcid.
>lotte:~# hcitool dev
>Devices:
>        hci0    00:09:DD:60:07:D3
>lotte:~# hcitool scan
>Scanning ...
>        00:1B:AF:CB:20:71       kmpNokiaN70
>        6C:0E:0D:42:96:44       kmpSEC902
>;===
>
>any ideas how to get bluetooth working in the CT? I think I need some 
>sockets for bluetooth to work, but no idea to get the socket into the CT. 
>or 
>do I searching the wrong end? :-)
>
>thanks für your support in advance!
>
>gre3tings & many thanks, Klaus
>
>_______________________________________________
>Users mailing list
>Users at openvz.org
>https://openvz.org/mailman/listinfo/users