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

jayjwa
2008-07-10T17:24:01Z

On Tue, 8 Jul 2008, Bram Jansen wrote:

-> 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.

-> 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

Not sure if there are typo's or not here, but those aren't the correct command
syntaxes as-written.

I'm assuming you have a phone that has a modem inside and is advertising the
DUN service via bluetooth and you'd like to make the computer connect to the
phone and cause the modem to dial out, taking the connection for the computer?
This is the case with my LG cellphone. There are two ways, with the dund
binary handling rfcomm itself, or with you calling the rfcomm binary to get
the device, then giving that to pppd.

passkey-agent --default <PIN> <bt addr> &
auth-agent &
rfcomm bind 0 <bt addr> 1
(to bind chan. 1 at /dev/rfcomm0. )

Then use /dev/rfcomm0 for the pppd connection. If I remember correctly, you
don't have to do the 'hcitool cc/auth' part at all.