public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Zbigniew Diaczyszyn (gmx)" <z.dia@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm: permission denied
Date: Mon, 09 Feb 2004 11:13:28 +0100	[thread overview]
Message-ID: <1076321608.6869.78.camel@pegasus> (raw)
In-Reply-To: <000101c3ee91$fa205f40$f84ab850@ULLA>

Hi Zbigniew,

> linux:~ # rfcomm bind 0 00:10:60:A6:97:8C
> linux:~ # rfcomm show
> rfcomm0: 00:10:60:A6:97:8C channel 1 clean
> linux:~ # hcitool scan
> Scanning ...
>         00:10:60:29:AC:2C       BluetoothModem
> linux:~ # rfcomm connect 0 00:10:60:29:AC:2C
> Can't connect RFCOMM socket: Permission denied

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.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-02-09 10:13 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 [this message]
2004-02-11 23:29   ` Zbigniew Diaczyszyn (gmx)
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=1076321608.6869.78.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=z.dia@gmx.de \
    /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