From: "Bram Jansen" <bramsbox@gmail.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket: Host is down
Date: Wed, 9 Jul 2008 11:28:21 +0200 [thread overview]
Message-ID: <A11CE28965CC41E7BAE76CD934C7F6F0@radon> (raw)
In-Reply-To: <E1F40683-65D7-49AC-A515-44D9035ED97A@gmail.com>
Hi Johan,
This did the trick.
Thanks a lot.
Regards,
Bram
-----Original Message-----
From: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Johan
Hedberg
Sent: 08 July 2008 19:38
To: BlueZ users
Subject: Re: [Bluez-users] Can't connect RFCOMM socket: Host is down
Hi Bram,
On Jul 8, 2008, at 20:19, Bram Jansen wrote:
> 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
That's because (as the man-page states) the parameters to rfcomm bind
are:
rfcomm bind <dev> <bdaddr> <channel>
Where <dev> is the number of the device node you want to use (e.g. 0
for rfcomm0).
If you give the command as you do the rfcomm tool will interpret your
bdaddr as the device node number (atoi(00:...") will yield 0) and 1 as
the remote address (which is why you see "01:00:...") and use the
channel 1 which is the default when no channel has been specified.
Johan
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-07-09 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 17:19 [Bluez-users] Can't connect RFCOMM socket: Host is down Bram Jansen
2008-07-08 17:37 ` Johan Hedberg
2008-07-09 9:28 ` Bram Jansen [this message]
2008-07-10 17:24 ` jayjwa
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=A11CE28965CC41E7BAE76CD934C7F6F0@radon \
--to=bramsbox@gmail.com \
--cc=bluez-users@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox