[Bluez-devel] "Can't connect RFCOMM socket"

[Bluez-devel] "Can't connect RFCOMM socket"

[Daniel Hertrich]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 2293 bytes --]

Dear bluez developers,

with the bluez drivers I tried to make a connection from my Sharp Zaurus
SL-C3000 PDA using various BT hardware (USB and compact flash devices) to my
Nokia phone. First I thought the problem was hardware-related, hence I
bought some other hardware and tried. But since I always get the same error
message I now suspect it is the software.
Could you please give some advice where to look for the source of the
problem?

What I have:
* Linux kernel 2.4.20 on ARM machine (Sharp Zaurus)
* Bluez drivers bluez-*.ipk from http://bluez.sf.net/download/zaurus 

What I do:
* Create rfcomm device: mknod -m 666 /dev/rfcomm0 c 216 0
* Plug in BT hardware via CF or USB
* hciconfig hci0 up
--> hciconfig then shows the bdaddr of the hardware
* hcitool -i hci0 scan
--> bdaddr of surrounding BT devices are shown, so hardware seems to work
fine
* rfcomm bind /dev/rfcomm0 00:02:EE:0D:71:96 1
--> The phone asks "connect to ?" I confirm and enter the pin which is
stored in /etc/bluetooth/pin. After a few seconds:
--> Can't connecto to RFCOMM socket: Resource temporarily unavailable


Some of the hci* tools complained about a missing libsdp library.
I investigated a little in the source tree of the libraries and found a
libsdp.c file (or similar) in the libbluetooth tree, so I assumed it is safe
to use libbluetooth instead of libsdp. So I did a
ln -s /usr/lib/libbluetooth.so /usr/lib/libsdp.so.2
and then the tools stopped complaining.
Can this be the reason?
But what to do instead against the libsdp problem?

Thanks for any hint!
daniel

-- 
Dipl.-Ing. Daniel Hertrich
Reichertshofen, Germany
http://www.hermocom.com
http://www.daniel-hertrich.de

Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "Can't connect RFCOMM socket"

[Bastien Nocera]

On Fri, 2006-03-24 at 11:55 +0100, Daniel Hertrich wrote:
> Dear bluez developers,
<snip>
> * rfcomm bind /dev/rfcomm0 00:02:EE:0D:71:96 1

Did you check that the device you're connecting to has RFCOMM on channel
1?

> --> The phone asks "connect to ?" I confirm and enter the pin which is
> stored in /etc/bluetooth/pin. After a few seconds:
> --> Can't connecto to RFCOMM socket: Resource temporarily unavailable

Double-check the pin setup in /etc/bluetooth/hcid.conf, the pin_helper
is the important thing.

> Some of the hci* tools complained about a missing libsdp library.

The tools will complain, but libsdp is included in libbluetooth nowadays
and isn't required anymore.

-- 
Bastien Nocera <hadess@hadess.net> 
It's beautiful, it's like a monkey.            -- Jean-Claude Van Damme



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "Can't connect RFCOMM socket"

[Daniel Hertrich]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1504 bytes --]

Hello Bastien,

thaks for your reply!

> On Fri, 2006-03-24 at 11:55 +0100, Daniel Hertrich wrote:
> > Dear bluez developers,
> <snip>
> > * rfcomm bind /dev/rfcomm0 00:02:EE:0D:71:96 1
> 
> Did you check that the device you're connecting to has RFCOMM on channel
> 1?

How can I check that?

> Double-check the pin setup in /etc/bluetooth/hcid.conf, the pin_helper
> is the important thing.

It is /usr/bin/bluepin, and if I call it manually, I get back
PIN:1234
Is it this what is expected from the pin_helper?

> > Some of the hci* tools complained about a missing libsdp library.
> 
> The tools will complain, but libsdp is included in libbluetooth nowadays
> and isn't required anymore.

So my linking of the libraries was okay it seems...

Thanks for any further help
daniel


-- 
Dipl.-Ing. Daniel Hertrich
Reichertshofen, Germany
http://www.hermocom.com
http://www.daniel-hertrich.de

"Feel free" mit GMX FreeMail!
Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "Can't connect RFCOMM socket"

[Daniel Hertrich]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1484 bytes --]

Hello Bastien,

addition:

> On Fri, 2006-03-24 at 11:55 +0100, Daniel Hertrich wrote:
> > Dear bluez developers,
> <snip>
> > * rfcomm bind /dev/rfcomm0 00:02:EE:0D:71:96 1
> 
> Did you check that the device you're connecting to has RFCOMM on channel
> 1?


Now I checked (with sdptool search --bdaddr ... DUN): It is indeed channel
1.

So what possible causes remain?

What is a bit unclear to me is which steps are actually really needed to
connect.
Different Internet pages mention different steps.

e.g. is an "rfcomm bind" needed before the rfcomm connect?
Which modules must be loaded? Could it be that here some modules are
missing?
Where can I find a summary of what conditions have to be met in order to be
able to connect?


Thanks
daniel


-- 
Dipl.-Ing. Daniel Hertrich
Reichertshofen, Germany
http://www.hermocom.com
http://www.daniel-hertrich.de

Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel