Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 354 — #380

16.4.6 Troubleshooting

If you have difﬁculties establishing a connection, proceed as follows:

1. Check the output of hcitool dev. Is the local device listed? If not,

hcid may not have been started or the device may not be recognized

as a Bluetooth device (either because the driver is not able to do this

or because the device is defective). Restart the daemon with the com-

mand rcbluetooth restart and check /var/log/messages to

see if any errors occurred.

2. Does the computer “see” other devices when you execute

hcitool inq? Try the command twice — the connection may have

been faulty, as the frequency band for Bluetooth is also used by other

devices.

3. Make sure the PIN in /etc/bluetooth/pin is the same as the PIN

of the remote device.

4. Try to establish the connection from the other device. Check if this

device sees the computer.

5. The ﬁrst example (network connection) does not work. This may

be due to various reasons. Possibly one of the two hosts does

not understand the ssh protocol. Try if ping 192.168.1.3 or

ping 192.168.1.4 works. If it does, check if sshd is active. Another

problem could be that you already have other addresses that conﬂict

with the address 192.168.1.X used in the example. If this is the

case, try other addresses, such as 10.123.1.2 and 10.123.1.3.

6. In the second example, the laptop does not appear as the target de-

vice. Does the mobile device recognize the Obex-Push service on the

laptop? In ‘My devices’, select the respective device and view the list

of ‘Services’. If Obex-Push is not displayed (even after the list is up-

dated), the problem is caused by opd on the laptop. Is opd active?

Do you have write access to the speciﬁed directory?

7. Does the second example work in reverse order? If obexftp is in-

stalled, this should work with obexftp -b <device_address>

-B 10 -p <image> on some devices (Siemens and Sony Ericsson

have been tested, other devices may or may not support this action).

354

16.4. Bluetooth — Wireless Connections