4
The /dev/rfcomm* serial devices entries are automatically created for using
5
RFCOMM with legacy applications -- see rfcomm(8). Users must be in group
6
'dialout' to have privileges to use these devices.
8
You can edit /etc/bluetooth/rfcomm.conf to have some rfcomm devices bound
9
automatically at boot time.
11
If you wish to install PCMCIA card services support for your Bluetooth
12
devices you should install the bluez-pcmcia-support package.
14
Some USB dongles require firmware to make them work: bluez-firmware from the
15
"non-free" section provides the required firmware.
18
Mailing lists and documentation
19
-------------------------------
20
The old sourceforge lists have been discontinued, the new lists can be found at:
22
http://www.bluez.org/development/lists/
24
plus a wiki at: http://wiki.bluez.org/
26
PIN (or passkey) management
27
---------------------------
28
Interaction with the local user can be required while BT connection is
29
being established (pairing process) and the PIN is not yet known or
32
To retrieve the passkey (or PIN) from the user a service program (agent)
33
running in user's interactive session needs to be prepared and listen
34
for requests of the bluez daemon when pairing begins.
36
Examples of such programs are kblueplugd (kdebluetooth package) and
37
bluetooth-applet (bluez-gnome or gnome-bluetooth packages). A minimal
38
command-line agent is also provided by bluez-simple-agent.
40
For example, you can execute bluez-simple-agent as follows.
42
$ bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX (Address of target device)
43
RequestPinCode (/org/bluez/27392/hci0/dev_XX_XX_XX_XX_XX_XX)
49
There's support for bluetooth headset both via ALSA and GStreamer, respectively
50
via bluez-alsa and bluez-gstreamer packages.
54
You might setup your headset by discovering it with gnome-bluetooth, once setup
55
add the following configuration to ~/.asoundrc:
62
then audio can be played with supported player, e.g. mplayer:
64
mplayer -ao alsa:device=bluetooth
66
See also: http://wiki.bluez.org/wiki/HOWTO/AudioDevices
70
The bluez-compat package includes old legacy daemons such as dund, pand and hidd
71
for enabling dial-up, ethernet networking and input devices over bluetooth.
73
Bluetooth Networking Quickstart with legacy daemons
74
+++++++++++++++++++++++++++++++++++++++++++++++++++
75
1. Start dund and pand at boot time
79
This is what most devices call "LAN Access" or "Serial Access". It
80
uses normal PPP over a serial connection. Most PDAs will be able to
81
connect using this method.
83
Use the 'dund' tool to accept incoming connections. Configure pppd
84
as per the instructions in the ppp package. Then run:
86
dund --listen --sdp --nodetach
88
Try and connect your device and you'll see something like:
90
dund[9801]: DUN daemon ver 1.1pre4
91
dund[9811]: New connection from 00:02:31:24:17:6A
93
The --sdp option causes the DUN access to be advertised to other
94
devices via the SDP protocol. Most devices need this in order to be
97
Run dund --help to see the various other options available to you.
99
If you want to make an outgoing connection using PPP, for instance to
100
a mobile phone, use the 'rfcomm' program from bluez-utils to bind a
101
/dev/rfcommX serial port to the phone, and then then use pppd as you
102
would with a normal modem.
106
The 'pand' tool allows you to use ethernet style networking over
107
Bluetooth. It creates a network interface on your machine that can be
108
configured in the same way normal network devices are.
110
For full details see the PAN HOWTO at
111
<http://bluez.sourceforge.net/contrib/HOWTO-PAN>
113
Keyboard and mouse support
114
++++++++++++++++++++++++++++++++++++
115
hidd daemon is included in a bluez-compat package.
116
We use bluez-simple-agent and bluez-test-input in bluez now.
118
1. Discover you mouse or keyboard bluetooth address (bdaddr) by running
121
2. Start bluez-simple-agent
123
$ sudo bluez-simple-agent hci0 <bdaddr>
124
RequestPinCode (/org/bluez/22302/hci0/dev_00_XX_XX_XX_XX_XX)
125
Enter PIN Code: 0000 <-- Please input PIN code
127
New device (/org/bluez/22302/hci0/dev_00_XX_XX_XX_XX_XX)
129
Bluetooth mouse set simple PIN code as "0000".
130
PIN code are different depending on mouse.
131
Please check the PIN code of your mouse.
133
3. With bluez-test-device, set *trusted* to the device.
135
$ sudo bluez-test-device trusted <bdaddr> yet
137
When you did not execute this, you use bluez-test-input after suspend
138
and resume (and reboot) have to connect a device again.
140
4. With bluez-test-input, connected to the device.
142
$ sudo bluez-test-input connect <bdaddr>
144
NOTE: If you want to use hidd daemon, please install bluez-compat package.
146
You must then connect to your keyboard or mouse using
147
"sudo hidd --connect <bdaddr>".
148
On first connection, pairing is likely and you should
149
press "connect" button on mice/keyboard, if any. Mice normally have a
150
preset PIN which should be in the manufacturer's documentation, try 0000.
151
For keyboards, type the PIN on the Bluetooth keyboard and hit enter, and
152
then supply it to the passkey agent
153
(using a cable-attached keyboard. e.g. bluez-simple-agent).
154
In future your keyboard or mouse should reconnect to your computer
157
-------------------------------
159
From Bluez 4.96, you also need to add to /etc/bluetooth/audio.conf: