From: Rainer Lay <rainer.lay@gmx.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] no route to host
Date: Thu, 06 Oct 2005 17:58:31 +0200 [thread overview]
Message-ID: <434549A7.1070401@gmx.de> (raw)
In-Reply-To: <1128545657.5447.71.camel@localhost.localdomain>
Marcel Holtmann wrote:
> Hi Rainer,
>
>>>> when trying to access rfcomm devices, I get:
>>>> minicom: cannot open /dev/rfcomm0: No route to host
>>>>
>>>> rfcomm tells me:
>>>> rfcomm0: 00:20:E0:3A:BC:28 channel 3 clean
>>>>
>>>> I am using bluez-utils version 2.19
>>>> I cannot find any log files, ...
>>>> I can connect to my handy via bluetooth with e.g. wammu
>>> run "hcidump -X -V" to see where the problem might be. What is
>> while running minicom, I get no output.
>>
>>> "hciconfig -a" telling you?
>> hci0: Type: USB
>> BD Address: 00:20:E0:3A:BC:28 ACL MTU: 192:8 SCO MTU: 64:8
>
> the address in the rfcomm call is the remote address and not the local
> one. There is no loopback support in Bluetooth.
>
thanx! This was obviously my mistake.
I was to silly to remember my MAC address :-)
Maybe you could at the device comment from rfcomm.conf to the output
too, so silly people like me can detect their errors themselves.
thanx,
Rainer
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-10-06 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 18:15 [Bluez-users] no route to host Rainer Lay
2005-10-05 18:56 ` Marcel Holtmann
2005-10-05 19:49 ` Rainer Lay
2005-10-05 20:54 ` Marcel Holtmann
2005-10-06 15:58 ` Rainer Lay [this message]
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=434549A7.1070401@gmx.de \
--to=rainer.lay@gmx.de \
--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 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.