public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Holger Frydrych <h.frydrych@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Logitech diNovo hub not recognized?
Date: Sat, 10 Jul 2004 11:25:15 +0200	[thread overview]
Message-ID: <1089451515.13519.49.camel@pegasus> (raw)
In-Reply-To: <40EFB4C7.3040509@gmx.de>

Hi Holger,

> > Don't use "hcitool cc ...", because this is only for development. What
> > does "hciconfig -a" show?
> This is the output:
> 
> hci0:   Type: USB
>          BD Address: 00:07:61:0D:C4:DF ACL MTU: 192:8  SCO MTU: 64:8
>          UP RUNNING PSCAN ISCAN AUTH ENCRYPT
>          RX bytes:19699 acl:854 sco:0 events:334 errors:0
>          TX bytes:3722 acl:122 sco:0 commands:64 errors:0
>          Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>          Link policy: RSWITCH HOLD SNIFF PARK
>          Link mode: SLAVE ACCEPT
>          Name: 'BlueZ (0)'
>          Class: 0x000100
>          Service Classes: Unspecified
>          Device Class: Computer, Uncategorized
>          HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP 
> Subver: 0x34e
>          Manufacturer: Cambridge Silicon Radio (10)
> 
> 
> Well, this reminded me of the fact that I had auth and encrypt options 
> in the hcid config file enabled because I considered that to be good 
> things. Well, but I disabled them, and guess what? My diNovo hardware 
> can now connect to the hub. So far, so good, I guess, though I still 
> thought that hid2hci was not necessary anymore?
> Well ok, it does work so far, but only without auth and encrypt. Is 
> there anything special I must do to get it working with both?

actually I thought that you enabled auth and encrypt ;)

Setting auth and encrypt in hcid.conf or with hciconfig sets your device
into security mode 3 and this is not what you want. The basic security
mode should be 2 which means service level security. I explained this
some times, so check the mailing list archive or the Bluetooth spec. for
more details.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-10  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 16:37 [Bluez-users] Logitech diNovo hub not recognized? Holger Frydrych
2004-07-09 18:15 ` Marcel Holtmann
     [not found]   ` <40EF0F10.8050302@gmx.de>
2004-07-09 22:51     ` Marcel Holtmann
2004-07-10  8:41       ` Holger Frydrych
2004-07-10  8:48         ` Marcel Holtmann
2004-07-10  9:20           ` Holger Frydrych
2004-07-10  9:25             ` Marcel Holtmann [this message]
2004-07-10 12:32               ` Holger Frydrych
2004-07-10 17:34                 ` Marcel Holtmann

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=1089451515.13519.49.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=h.frydrych@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox