All of lore.kernel.org
 help / color / mirror / Atom feed
From: dave sailer <d.sailer@comcast.net>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] hcid.conf multiple dongles
Date: Tue, 21 Nov 2006 22:13:08 -0500	[thread overview]
Message-ID: <4563C044.3030200@comcast.net> (raw)

I have a Microsoft bluetooth keyboard and mouse that has worked well for
some time. I bought new bluetooth dongle (Kensington) in hopes of
getting my palm to connect via bluetooth (the Microsoft dongle didn't
work for this). With this arrangement, how do I control which dongle the
keyboard & mouse connect to? (it seems more reliable with Microsoft to
Microsoft).

Also, the results of "hci tool scan" are confusing me a bit. For
example, I get...

myth1 ~ # hcitool scan
Scanning ...
        00:50:F2:7E:11:F1       Myth1 Kensington dongle4


firstly, this bdadr is the microsoft dongle. Does this normally return a
dongle address? At one point I'm sure it was returning the palm pilot
address. Secondly, this name "Myth1 Kensington dongle4" is old. I used
to have that in hcid.conf, but changed it and even rebooted the box. 
Just for history, at one point I had an hcid.conf file with only one
device section (no device id's). Now I have the following ... (wasn't
sure about the device syntax, but this seems to work. btw, it would be
nice if the hcid.conf man page was more clear about the syntax on how to
specify multiple devices)


options {
    # Automatically initialize new devices
    autoinit yes;

    # Security Manager mode
    #   none - Security manager disabled (palm fails completely with this)
    #   auto - Use local PIN for incoming connections
    #   user - Always ask user for a PIN
    #
    security user;

    # Pairing mode
    #   none  - Pairing disabled
    #   multi - Allow pairing with already paired devices
    #   once  - Pair once and deny successive attempts
    pairing multi;

    # PIN helper
    pin_helper /etc/bluetooth/pin-helper;
    #pin_helper /usr/bin/bluepin;

    # D-Bus PIN helper
    #dbus_pin_helper;
}

# Default settings for HCI devices
device 00:16:38:BE:F1:21 {
        name "Myth1 Kensington dongle1";
    class 0x020100;
    iscan enable; pscan enable;
    lm accept;
    lp rswitch,hold,sniff,park;
}

device 00:50:F2:7E:11:F1 {
        name "Myth1 Microsoft dongle2";
    class 0x020100;
    iscan enable; pscan enable;
    lm accept;
    lp rswitch,hold,sniff,park;
}


thanks


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2006-11-22  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  3:13 dave sailer [this message]
2006-11-22  6:59 ` [Bluez-users] hcid.conf multiple dongles Marcel Holtmann
2006-11-22 12:44   ` Dave sailer
2006-11-22 23:29     ` dave sailer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4563C044.3030200@comcast.net \
    --to=d.sailer@comcast.net \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.