public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Lutz Pressler <Lutz.Pressler@SerNet.DE>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"
Date: Tue, 18 May 2004 12:32:20 +0200	[thread overview]
Message-ID: <1084876340.5833.96.camel@pegasus> (raw)
In-Reply-To: <E1BQ1hB-0007WA-00@intern.SerNet.DE>

Hi Lutz,

> > please install bluez-libs-2.7 and bluez-utils-2.7, because it looks like
> > that this phone already contains some Bluetooth 1.2 features and I need
> > to know the full 8 bytes of the remote features.
> later (work to do here :)) - probably not today.

not really needed anymore, because it looks like a bug in one of the
link managers or maybe the hardware itself.

> > like that you are in security mode 3. From your hcid.conf I saw that you
> > haven't activated auth and encrypt so this is not you, but I can't think
> tried with and without "auth enable; encrypt enable;" and with
> "lm accept;" and "lm accept,master;". No difference.

Keep auth and encrypt always off unless you really wanna activate
security mode 3.

> > It disconnects with "Pairing With Unit Key Not Supported" error (0x29)
> > and I haven't seen this error before. I am no link manager expert, but I
> > really think that one implementation is acting very bad here. And I
> > guess it is your Acer dongle with the Zeevo/Telencomm chip, because it
> > has caused troubles in the past. Do you own another dongle (preferable
> > CSR based) to check this?
> At the moment I don't think so. We also have a physically bigger Acer
> dongle (that may be "100m" variant?), but that's on the road at the
> moment. Should I order some specific model?

The best is you buy yourself a CSR based dongle with a least HCI 16.4
firmware. If you still get problems with a CSR based dongle you have to
return your phone. For specific dongle information check our hardware
lists at http://www.bluez.org/hardware.html

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-05-18 10:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18  8:01 [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons" Lutz Pressler
2004-05-18  8:28 ` Marcel Holtmann
2004-05-18  8:51   ` Lutz Pressler
2004-05-18  9:22     ` Marcel Holtmann
2004-05-18  9:39       ` Peter Stephenson
2004-05-18  9:53         ` Marcel Holtmann
2004-05-18 10:07           ` Lutz Pressler
2004-05-18 10:15             ` Marcel Holtmann
2004-05-19  8:29               ` Lutz Pressler
2004-05-19  9:02                 ` Marcel Holtmann
2004-05-18 10:19       ` Lutz Pressler
2004-05-18 10:32         ` Marcel Holtmann [this message]
2004-05-18 13:49     ` [Bluez-devel] Nokia 6230 info Andreas Gaufer
2004-05-18 14:05       ` 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=1084876340.5833.96.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Lutz.Pressler@SerNet.DE \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox