From: "Zbigniew Diaczyszyn \(gmx\)" <z.dia@gmx.de>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm: permission denied
Date: Thu, 12 Feb 2004 00:29:32 +0100 [thread overview]
Message-ID: <000c01c3f0f6$e9a19e10$154db850@ULLA> (raw)
In-Reply-To: 1076321608.6869.78.camel@pegasus
Hallo Marcel,
----- Original Message -----=20
> > linux:~ # rfcomm connect 0 00:10:60:29:AC:2C
> > Can't connect RFCOMM socket: Permission denied
>=20
> this can't work. If you bind the device you don't need an additional
> connect. You only have to open /dev/rfcomm0 with pppd or any other TTY
> related program.
--------------------------------------------------------
Well, having done this (suse 8.2, ppp1 is directed to /dev/rfcomm0) the =
kinternet protocol tells that there is <no route to host>:
SuSE Meta pppd (smpppd-ifcfg), Version 1.00 on linux.
trying to connect to smpppd
connect to smpppd
We are disconnected.
We are connecting.
pppd: Plugin passwordfd.so loaded.
pppd: Failed to open /dev/rfcomm0: No route to host
We are disconnected.
pppd died: Serial port open failed (exit code 7)
the proprietary mask tells: crw-rw---- root dialout =
/dev/rfcomm0
next prev parent reply other threads:[~2004-02-11 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 21:48 [Bluez-users] rfcomm: permission denied Zbigniew Diaczyszyn (gmx)
2004-02-09 10:13 ` Marcel Holtmann
2004-02-11 23:29 ` Zbigniew Diaczyszyn (gmx) [this message]
2004-02-11 23:27 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 22:03 Zbigniew Diaczyszyn (gmx)
2004-02-13 22:16 ` Marcel Holtmann
2004-02-14 21:45 Zbigniew Diaczyszyn (gmx)
2004-02-15 14:34 ` Marcel Holtmann
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='000c01c3f0f6$e9a19e10$154db850@ULLA' \
--to=z.dia@gmx.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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