FS#5661 - ISCAN not set for hci0 despite correct hcid.conf settings

Attached to Project: Arch Linux
Opened by Dawid Wróbel (cromo) - Tuesday, 24 October 2006, 15:25 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 24 May 2007, 10:03 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tom Killian (tomk)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I had a problem today with bluez discovery. Whatever I done, my bluez server kept to not be visible on other BT devices (precisely, my Nokia mobile). Despite having correct settings in hcid.conf (i.e. "iscan enable; pscan enable;"), according to hciconf ISCAN was not set for hci0, only PSCAN was. I found the solution here: https://launchpad.net/distros/ubuntu/+source/bluez-utils/+bug/59222 . Seems that the reason for this problem is the need to put "discovto 0; " line into hcid.conf. I also had to rm -r /var/lib/bluetooth, as described in one of the comments. After this, it works just fine.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 24 May 2007, 10:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  seems to be solved by upstream
Comment by Dawid Wróbel (cromo) - Tuesday, 24 October 2006, 15:27 GMT
Oh, forgot to mention that I am using bluez-{libs,utils} from testing - 3.711 and 3.7-2 respictively.
Comment by Tom Killian (tomk) - Tuesday, 24 October 2006, 19:56 GMT
As specified in man hcid.conf, the discovto option is used to define a period of time during which the device will remain discoverable. Setting "discovto 0" disables it, and the device remains discoverable indefinitely. This is not a good default setting.

My initial inclination is to set it to something like 120-180 seconds, and add a post-install message with additional info. I'll run a few test scenarios first though.
Comment by Dawid Wróbel (cromo) - Wednesday, 25 October 2006, 21:00 GMT
I do realize it's not related to you but rather to the upstream developers, but anyway I don't really get why would someone want to be discoverable just for some short time after running bluez. For me it would be more obvious to just be able to manually and easly turn the discoverability on and off when needed, thus staying as secure as possible. This is the same approach as in the most of the modern mobile phones: you can set the discoverability on and off, as well as BT itself. So I'd suggest to put this "discovto 0;" line into hcid.conf, then set hci0 to not be discoverable by default (i.e. "pscan enable;" only) and then provide some script to set the discoverablity easly via hciconfig hci0 for example. This involves gaining root priveleges, though...

Loading...