From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: bluez-devel@lists.sf.net
Subject: [Bluez-devel] Pairing fails with RFCOMM
Date: Fri, 06 Feb 2004 18:03:31 +0100 [thread overview]
Message-ID: <1076087010.964.75.camel@localhost> (raw)
Hi all!
I think I found a small problem with rfcomm concerning pairing.
The problem is that if you try to connect to a "new" device which
requires pairing using rfcomm you will be queried for y pin on both
sides. But it seems that a connect timeout in rfcomm is way too short
for being able to input the pin.
It happened to me while trying to connect to a Siemens S55 mobile.
I did a "rfcomm bind" and then opened minicom on the port. After that
the mobile requests the pin. But before you can even start to input the
pin minicom exits with an error.
If I start another connection first, like with multisync, the whole
connection process waits until the pin has been entered on both sides.
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-02-06 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:03 Nils Faerber [this message]
2004-02-06 19:57 ` [Bluez-devel] Pairing fails with RFCOMM Marcel Holtmann
[not found] ` <1076337219.2892.57.camel@localhost>
2004-02-09 15:01 ` Marcel Holtmann
[not found] ` <1076339124.1169.67.camel@localhost>
2004-02-09 15:08 ` Marcel Holtmann
[not found] ` <1076340484.1167.79.camel@localhost>
2004-02-09 15:56 ` Marcel Holtmann
[not found] ` <1076342698.1167.90.camel@localhost>
2004-02-09 16:14 ` 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=1076087010.964.75.camel@localhost \
--to=nils.faerber@kernelconcepts.de \
--cc=bluez-devel@lists.sf.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.