public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zbigniew Diaczyszyn \(gmx\)" <z.dia@gmx.de>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] rfcomm: permission denied
Date: Sat, 7 Feb 2004 22:48:12 +0100	[thread overview]
Message-ID: <000101c3ee91$fa205f40$f84ab850@ULLA> (raw)

I'm working with Suse 8.2 and a Typhoon Bluetooth modem. I had it =
working - once. Now rfcomm is just saying: permission denied. The =
following lines are a protocol of bluetooth session. I have no idea at =
all in which  config-files I should look for a solution. /bin/bluepin =
ist just a < cat /etc/bluetooth/bluepin >. I'm working as root and =
/dev/rfcomm0 ist belonging to root.

Zbigniew Diaczyszyn        z.dia@gmx.de

-------------------------------------------------------------------------=
---------
linux:~ # hcid
linux:~ # hciconfig -a
hci0:   Type: USB
        BD Address: 00:10:60:A6:97:8C ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:129 acl:0 sco:0 events:18 errors:0
        TX bytes:569 acl:0 sco:0 commands:18 errors:0
        Features: 0xff 0xff 0x0f 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'Typhoon (0)'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: =
0x20d
        Manufacturer: Cambridge Silicon Radio (10)

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

linux:~ # sdptool browse
Inquiring ...
Failed to connect to SDP server on 00:10:60:29:AC:2C




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




-------------------------------------------------------
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-07 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 21:48 Zbigniew Diaczyszyn (gmx) [this message]
2004-02-09 10:13 ` [Bluez-users] rfcomm: permission denied Marcel Holtmann
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='000101c3ee91$fa205f40$f84ab850@ULLA' \
    --to=z.dia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox