From: Marcel Holtmann <marcel@holtmann.org>
To: David Feldman <wb0gaz@hotmail.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How is pairing completed in rfcomm?
Date: Mon, 21 Jun 2004 23:08:55 +0200 [thread overview]
Message-ID: <1087852135.4328.30.camel@pegasus> (raw)
In-Reply-To: <20040621135136.7C703C50.wb0gaz@hotmail.com>
Hi David,
> I'm working on getting my RH9 laptop to communicate with T68 (not i),
> and I made
> another step forward, but I can't complete the "pairing" process (
> which is where the
> phone picks up the identity of a PC and makes that PC "OK" for future
> data operation.)
>
> My steps:
>
> insert card, do cardctl insert.
> hciconfig hci0 up
> rfcomm /dev/rfcomm0 MAC-ADDRESS 1 (1 is for DUN on this phone)
it is "rfcomm bind 0 <bdaddr> [channel]".
> Now at this step I gave the phone the instruction to add to paired
> devices, with
> the option "phone accepts".
>
> Then, I did this:
>
> cat </dev/rfcomm0
>
> at which point the phone displays the PC's name, then asks for a PIN.
>
> I entered the PIN (a 4-digit code) that I had previously configured
>
> Now the phone says "pairing..." and waits forever.
>
> If I interrupt the cat </dev/rfcomm0 with Control-C,
>
> then the following is seen:
>
> 1. Any output (echo, cat, etc.) to /dev/rfcomm0 produces the error
> message:
> "bash: /dev/rfcomm0: Operation already in progress"
>
> 2. The rfcomm command produces the message:
> rfcomm0: MAC-ADDRESS channel 1 disconnecting
Until you upgraded to a newer kernel I can't guarantee that this will
work. Your RFCOMM code seems to be buggy for Bluetooth 1.0b phones.
> Marcel had advised me to update to the latest kernel - I am not in a
> position to
> do this immediately, and it I hope the pairing process would be able
> to proceed
> in any event, if I am using the correct procedure. I am using Kernel 2.
> 4.20-31.9,
> which was current as of 04/2004; as the phone is nearly 2 years old,
> I'm hoping
> I can validate it's operation at least through the pairing process.
The phone will work. I don't see any problem here because the Bluetooth
stack of the T68 and the T39m are identical and the T39m is working for
me.
> So my core question - how do I complete the pairing process, when
> initiated
> by the PC and accepted by the phone?
The phone uses security level 2 and this means the security routines
kick in when you request access to the RFCOMM channel. If you want them
earlier then the use of security mode 3 is needed. Use "hciconfig hci0
auth" to activate it on your device.
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
next prev parent reply other threads:[~2004-06-21 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 19:51 [Bluez-users] How is pairing completed in rfcomm? David Feldman
2004-06-21 21:08 ` Marcel Holtmann [this message]
2004-06-22 15:20 ` David Feldman
2004-06-22 15:30 ` Solved pairing problem - big success! David Feldman
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=1087852135.4328.30.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=wb0gaz@hotmail.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