public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lutz Pressler <Lutz.Pressler@SerNet.DE>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Peter Stephenson <pws@csr.com>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Nokia 6230: "pairing and conn. rejected for security reasons"
Date: Wed, 19 May 2004 10:29:06 +0200 (CEST)	[thread overview]
Message-ID: <E1BQMRm-0001ot-00@intern.SerNet.DE> (raw)
In-Reply-To: <1084875342.5833.89.camel@pegasus>

Hi,
On Tue, 18 May 2004, Marcel Holtmann wrote:
> looks like something is really screwed up here. Please check this with
> another USB dongle to make sure that your phone is not broken.
>
I borrowed a CSR based Allnet 1575.

hciconfig -a
hci0:   Type: USB
        BD Address: 00:0C:55:FF:DE:7F ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:99 acl:0 sco:0 events:13 errors:0
        TX bytes:296 acl:0 sco:0 commands:12 errors:0
        Features: 0xff 0xff 0x0f 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'tux'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)

Pairing and RFCOM usage of the Nokia 6230 (PPP via GPRS) does work with
that one.

hcitool info 00:E0:03:39:C9:AB   now looks different:

Requesting information ...
        BD Address:  00:E0:03:39:C9:AB
        Device Name: Nokia 6230 LP
        LMP Version: 1.1 (0x1) LMP Subversion: 0x380
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xbf 0xee 0x0f 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot offset>
                <timing accuracy> <role switch> <sniff mode> <RSSI>
                <channel quality> <SCO link> <HV3 packets> <u-law log>
                <A-law log> <CVSD> <paging scheme> <power control>
                <transparent SCO>

Any further tests/dums to (re)do with that phone?

Thanks!
  Lutz

-- 
  _              |  Lutz Pressler          |  Tel: ++49-551-3700002
 |_     |\ |     |  Service Network GmbH   |  FAX: ++49-551-3700009
 ._|ER  | \|ET   |  Bahnhofsallee 1b       |   mailto:lp@SerNet.DE
Service Network  |  D-37081 Goettingen     |  http://www.SerNet.DE/

  reply	other threads:[~2004-05-19  8:29 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 [this message]
2004-05-19  9:02                 ` Marcel Holtmann
2004-05-18 10:19       ` Lutz Pressler
2004-05-18 10:32         ` Marcel Holtmann
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=E1BQMRm-0001ot-00@intern.SerNet.DE \
    --to=lutz.pressler@sernet.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=pws@csr.com \
    /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