[Bluez-users] Can't connect RFCOMM socket: Host is down

Bram Jansen
2008-07-08T17:19:42Z

[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]

Hi,

I've been browsing the web for a while now and I can't find a solution to my
problem.

I'm trying to connect my Debian Etch box to the DUN service to any phone I
have. For some reason rfcomm isn't happy and is not able to make a
connection.

I've tried the following

1. passkey-agent -default 0000
2. hcitool cc <bdaddr>
3. hcitool auth <bdaddr>

a. pairing succeeded and my box are in the phones's paired devices list

4. rfcomm bind <bdaddr> 1 (channel is correctly found with sdptool)
works fine but gives a strange bdaddr for the phone it binds to.

a. rfcomm0: 01:00:00:00:00:00 channel 1 clean

for some reason only one time the correct Bluetooth address of one of my
phones was there but I'm not able to reproduce it.

Can anyone please point me in the right direction about why after the above
steps I only see the following line when I type

rfcomm show rfcomm0

I get the result

rfcomm0: 01:00:00:00:00:00 channel 1 clean

and not

rfcomm0: <bdaddr> channel 1 clean

thanks in advance,

Bram

[-- Attachment #1.2: Type: text/html, Size: 8708 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]