Can't connect RFCOMM socket: Connection refused

Bluez-users neci 3 participants 9 messages Aug 2, 2006 Bluetooth drivers

Share & tools

neci

author

2006-08-02 15:24 UTC #0 lore raw

Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.

# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused

# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff

linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13

Quoted 2 lines

HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11

< ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 3 scid 0x0040

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4

Quoted 4 lines

HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024

Quoted 3 lines

HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c

Quoted 3 lines

HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7

< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7

Quoted 2 lines

HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18

L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59

Quoted 5 lines

HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6

< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22

Quoted 2 lines

HCI Event: Command Complete (0x0e) plen 10 ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040

Quoted 3 lines

HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040

< HCI Command: Disconnect (0x01|0x0006) plen 3

Quoted 2 lines

HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4

#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;

# D-Bus PIN helper
#dbus_pin_helper;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "PC";

# Local device class
# e.g.
# 0xsss100 = Computer
# 0xsss104 = Computer Desktop
# 0xsss108 = Computer Server
# 0xsss10c = Computer Laptop
# The 'sss' above defines the service-class (not quite, only the # first 11 bits, the next 11 define the device-class, than 2 format bits.) # See https://www.bluetooth.org/foundry/assignnumb/document/baseband
# for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
class 0xdb0100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;

# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}

#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #

rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Paulo Wollny

2006-08-02 15:37 UTC #1 lore raw

As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*

Quoted 99 lines · neci

Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
Quoted 3 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 6 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
Quoted 3 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8

Quoted 132 lines

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
Quoted 124 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
------------------------------------------------------------------------
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "PC";
# Local device class
# e.g.
# 0xsss100 = Computer
# 0xsss104 = Computer Desktop
# 0xsss108 = Computer Server
# 0xsss10c = Computer Laptop
# The 'sss' above defines the service-class (not quite, only the # first 11 bits, the next 11 define the device-class, than 2 format bits.) # See https://www.bluetooth.org/foundry/assignnumb/document/baseband
# for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
class 0xdb0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}
------------------------------------------------------------------------
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}
------------------------------------------------------------------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

neci

author

2006-08-02 15:45 UTC #2 lore raw

it is wrong command?
#cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1
bash: *mknod: command not found

i edit him

# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
# chmod 666 /dev/rfcomm*
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused

Paulo Wollny write:

Quoted 239 lines

As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*
Quoted 99 lines · neci
Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
Quoted 2 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335
Quoted 1 line
ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7
Quoted 2 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
Quoted 2 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
Quoted 134 lines
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Quoted 1 line
ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
Quoted 126 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
------------------------------------------------------------------------
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "PC";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format
bits.) # See
https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" class 0xdb0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}
------------------------------------------------------------------------
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}
------------------------------------------------------------------------
------------------------------------------------------------------------
- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
------------------------------------------------------------------------
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Quoted 10 lines

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Paulo Wollny

2006-08-02 16:39 UTC #3 lore raw

the initial # is the prompt from the command line.

Quoted 4 lines · neci

it is wrong command?
#cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1
bash: *mknod: command not found

Quoted 274 lines

i edit him
# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
# chmod 666 /dev/rfcomm*
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
Paulo Wollny write:
Quoted 262 lines
As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*
Quoted 108 lines · neci
Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
Quoted 3 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 6 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
Quoted 3 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
Quoted 137 lines
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
Quoted 127 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
------------------------------------------------------------------------
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "PC";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format
bits.) # See
https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" class 0xdb0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}
------------------------------------------------------------------------
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}
------------------------------------------------------------------------
------------------------------------------------------------------------
- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
------------------------------------------------------------------------
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

neci

author

2006-08-02 19:58 UTC #4 lore raw

yes i know, and?

Paulo Wollny write:

Quoted 268 lines

the initial # is the prompt from the command line.
Quoted 265 lines · neci
it is wrong command?
#cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1
bash: *mknod: command not found
i edit him
# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
# chmod 666 /dev/rfcomm*
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
Paulo Wollny write:
Quoted 253 lines
As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*
Quoted 99 lines · neci
Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
Quoted 2 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335
Quoted 1 line
ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7
Quoted 2 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
Quoted 2 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
Quoted 138 lines
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Quoted 1 line
ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
Quoted 130 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
----------------------------------------------------------------------
--
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "PC";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format
bits.) # See
https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" class 0xdb0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}
----------------------------------------------------------------------
--
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}
----------------------------------------------------------------------
--
----------------------------------------------------------------------
-- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV
DE V
----------------------------------------------------------------------
--
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
------------------------------------------------------------------------
- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V _______________________________________________ Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Paulo Wollny

2006-08-02 20:12 UTC #5 lore raw

sorry, was wrong... :-)
striping the * from the mknod shall work.
see if there are the /dev/rfcomm* files
after that, issue rfcomm bind 0 xx:xx:xx:xx:xx:xx 1 as root. this shall work.

Quoted 288 lines · neci

yes i know, and?
Paulo Wollny write:
Quoted 283 lines
the initial # is the prompt from the command line.
Quoted 279 lines · neci
it is wrong command?
#cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1
bash: *mknod: command not found
i edit him
# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
# chmod 666 /dev/rfcomm*
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
Paulo Wollny write:
Quoted 266 lines
As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*
Quoted 108 lines · neci
Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
Quoted 3 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 335
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 330 max_retrans 0 credits 7
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
Quoted 6 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
Quoted 3 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
Quoted 141 lines
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
Quoted 131 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
----------------------------------------------------------------------
--
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
# if you want a interactiv query of your pin use /usr/bin/bluepin # /bin/bluepincat is using the pin in the /etc/bluetooth/pin file # pin_helper /usr/bin/bluepin;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "PC";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format
bits.) # See
https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" class 0xdb0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
iscan enable;
pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3) auth disable;
encrypt disable;
}
----------------------------------------------------------------------
--
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:01:E3:58:23:EA;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "Mobil";
}
----------------------------------------------------------------------
--
----------------------------------------------------------------------
-- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV
DE V
----------------------------------------------------------------------
--
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
------------------------------------------------------------------------
- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V _______________________________________________ Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Quoted 12 lines

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

neci

author

2006-08-02 20:26 UTC #6 lore raw

doing something wrong? i can upload files with OBEX object push client.

linux:/dev # cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1 linux:/dev # chmod 666 /dev/rfcomm*
linux:/dev # ls | grep rfcomm
rfcomm0
rfcomm1
linux:/dev # hcitool scan
Scanning ...

        00:01:E3:58:23:EA       Neci

linux:/dev # rfcomm bind 0 00:01:E3:58:23:EA 1
Can't create device: Address already in use

Paulo Wollny write:

Quoted 8 lines

sorry, was wrong... :-)
striping the * from the mknod shall work.
see if there are the /dev/rfcomm* files
after that, issue rfcomm bind 0 xx:xx:xx:xx:xx:xx 1 as root. this shall work.
neci schrieb:
yes i know, and?

Quoted 64 lines

Paulo Wollny write:
=A0 =
Quoted 61 lines
the initial # is the prompt from the command line.
neci schrieb:
=A0 =A0 =
Quoted 56 lines
it is wrong command?
#cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1
bash: *mknod: command not found
i edit him
# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
# chmod 666 /dev/rfcomm*
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
Paulo Wollny write:
=A0 =A0 =A0 =
Quoted 42 lines
As root, issue the following command:
cd /dev && *mknod rfcomm0* c 216 0 && *mknod* rfcomm1 c 216 1 then, chmod 666 /dev/rfcomm*
neci schrieb:
=A0 =A0 =A0 =A0 =
Quoted 35 lines
Hello,
i can't create /dev/rfcomm. What is wrong? attach config files and out from hcidump.
# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Connection refused
# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
linux:/etc # hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13
=A0 =A0 =A0 =A0 =A0 =
Quoted 3 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Connect Complete (0x03) plen 11
=A0 =A0 =A0 =A0 =A0 =A0 =
< ACL data: handle 42 flags 0x02 dlen 12
=A0 =A0 L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
=A0 =A0 =A0 =A0 =A0 =
Quoted 5 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Max Slots Change (0x1b) plen 3 HCI Event: Command Complete (0x0e) plen 6 ACL data: handle 42 flags 0x02 dlen 16
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 statu=

s 0

Quoted 37 lines

Quoted 36 lines
Quoted 36 lines
Quoted 36 lines
Quoted 36 lines
=A0 =A0 =A0 Connection successful
< ACL data: handle 42 flags 0x02 dlen 16
=A0 =A0 L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4 =A0 =A0 =A0 MTU 1024
=A0 =A0 =A0 =A0 =A0 =
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 17
ACL data: handle 42 flags 0x01 dlen 1
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4 =A0 =A0 =A0 Success
=A0 =A0 =A0 MTU 335
=A0 =A0 =A0 =A0 =A0 =
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 16
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4 =A0 =A0 =A0 MTU 335
< ACL data: handle 42 flags 0x02 dlen 14
=A0 =A0 L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0 =A0 =A0 =A0 Success
< ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
=A0 =A0 =A0 =A0 =A0 =
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 =A0 =A0 =A0 =A0 =

Quoted 5 lines

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 42 flags 0x02 dlen 18
=A0 =A0 L2CAP(d): cid 0x0040 len 14 [psm 3]
=A0 =A0 =A0 RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_=

len 8

Quoted 11 lines

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
=A0 =A0 =A0 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 =A0 =A0 =A0 frame_size 330 max_retrans 0 credits 7
=A0 =A0 =A0 =A0 =A0 =
Quoted 3 lines
HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 18
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(d): cid 0x0040 len 14 [psm 3]
=A0 =A0 =A0 RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_=

len 8

Quoted 49 lines

Quoted 49 lines
Quoted 49 lines
Quoted 49 lines
Quoted 49 lines
=A0 =A0 =A0 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 =A0 =A0 =A0 frame_size 330 max_retrans 0 credits 4
< ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
=A0 =A0 =A0 =A0 =A0 =
Quoted 6 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 HCI Event: Role Change (0x12) plen 8
HCI Event: Max Slots Change (0x1b) plen 3
HCI Event: Link Key Request (0x17) plen 6
=A0 =A0 =A0 =A0 =A0 =A0 =
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
=A0 =A0 =A0 =A0 =A0 =
Quoted 3 lines
HCI Event: Command Complete (0x0e) plen 10
ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73 < ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd < ACL data: handle 42 flags 0x02 dlen 12
=A0 =A0 L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
=A0 =A0 =A0 =A0 =A0 =
Quoted 4 lines
HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 42 flags 0x02 dlen 8
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(d): cid 0x0040 len 4 [psm 3]
=A0 =A0 =A0 RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
=A0 =A0 =A0 =A0 =A0 =
Quoted 2 lines
ACL data: handle 42 flags 0x02 dlen 12
=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040 < HCI Command: Disconnect (0x01|0x0006) plen 3

Quoted 6 lines

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
=A0 =A0 =A0 =A0 =A0 =
Quoted 4 lines
HCI Event: Command Status (0x0f) plen 4
HCI Event: Disconn Complete (0x05) plen 4
--------------------------------------------------------------------=

Quoted 43 lines

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
--
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $ #
# HCId options
options {
=A0# Automatically initialize new devices
=A0autoinit yes;
=A0# Security Manager mode
=A0# =A0 none - Security manager disabled =A0# =A0 auto - Use local PIN for incoming connections =A0# =A0 user - Always ask user for a PIN =A0#
=A0security auto;
=A0# Pairing mode
=A0# =A0 none =A0- Pairing disabled
=A0# =A0 multi - Allow pairing with already paired devices =A0# =A0 once =A0- Pair once and deny successive attempts =A0pairing multi;
=A0# PIN helper
=A0# if you want a interactiv query of your pin use /usr/bin/bluepin =A0# /bin/bluepincat is using the pin in the /etc/bluetooth/pin file =A0# pin_helper /usr/bin/bluepin;
=A0pin_helper /bin/bluepincat;
=A0# D-Bus PIN helper
=A0#dbus_pin_helper;
}
# Default settings for HCI devices
device {
=A0# Local device name
=A0# =A0 %d - device id
=A0# =A0 %h - host name
=A0name "PC";

Quoted 8 lines

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
=A0# Local device class
=A0# e.g.
=A0# =A00xsss100 =3D Computer
=A0# =A00xsss104 =3D Computer Desktop
=A0# =A00xsss108 =3D Computer Server
=A0# =A00xsss10c =3D Computer Laptop
=A0# The 'sss' above defines the service-class (not quite, only the =A0# first 11 bits, the next 11 define the device-class, than 2 form=

Quoted 4 lines

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
bits.) # See
https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information.
=A0# 0x100bbb stands for "Object Transfer =A0(v-Inbox, v-Folder, ...=

Quoted 26 lines

Quoted 26 lines
Quoted 26 lines
Quoted 26 lines
Quoted 26 lines
Quoted 26 lines
=A0# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" =A0class 0xdb0100;
=A0# Default packet type
=A0#pkt_type DH1,DM1,HV1;
=A0# Inquiry and Page scan
=A0# valid parameters: enable | disable
=A0iscan enable;
=A0pscan enable;
=A0# Default link mode
=A0# =A0 none =A0 - no specific policy
=A0# =A0 accept - always accept incoming connections
=A0# =A0 master - become master on incoming connections, =A0# =A0 =A0 =A0 =A0 =A0 =A0deny role switch on outgoing connections =A0lm accept;
=A0# Default link policy
=A0# =A0 none =A0 =A0- no specific policy
=A0# =A0 rswitch - allow role switch
=A0# =A0 hold =A0 =A0- allow hold mode
=A0# =A0 sniff =A0 - allow sniff mode
=A0# =A0 park =A0 =A0- allow park mode
=A0lp rswitch,hold,sniff,park;

Quoted 6 lines

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
=A0# Authentication and Encryption (Security Mode 3) =A0auth disable;
=A0encrypt disable;
}
--------------------------------------------------------------------=

Quoted 15 lines

Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
--
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $ #
rfcomm0 {
=A0# Automatically bind the device at startup
=A0bind yes;
=A0# Bluetooth address of the device
=A0device 00:01:E3:58:23:EA;

Quoted 8 lines

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
=A0# RFCOMM channel for the connection
=A0channel=A01;
=A0# Description of the connection
=A0comment "Mobil";
}
--------------------------------------------------------------------=

Quoted 3 lines

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
--
--------------------------------------------------------------------=

Quoted 5 lines

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
-- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&C=

ID=3DDEV

Quoted 2 lines

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
DE V
--------------------------------------------------------------------=

Quoted 9 lines

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 7 lines
Quoted 7 lines
--
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
=A0 =A0 =A0 =A0 =A0 =A0 =
----------------------------------------------------------------------=

Quoted 5 lines

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
- Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=

=3DDEVDE

Quoted 10 lines

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
V _______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
=A0 =A0 =A0 =A0 =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share y=

our

Quoted 2 lines

opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=

DEVDEV

Quoted 7 lines

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
=A0 =

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Stefan Seyfried

2006-08-02 21:46 UTC #7 lore raw

Quoted 10 lines · neci

doing something wrong? i can upload files with OBEX object push client. =
linux:/dev # cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1 linux:/dev # chmod 666 /dev/rfcomm*
linux:/dev # ls | grep rfcomm
rfcomm0
rfcomm1
linux:/dev # hcitool scan
Scanning ...

Quoted 3 lines

        00:01:E3:58:23:EA       Neci
linux:/dev # rfcomm bind 0 00:01:E3:58:23:EA 1
Can't create device: Address already in use

output of just plain "rfcomm"?

Oh - and stripping a bit of the useless quotes surely would not hurt :-)

-- =

Stefan Seyfried | "Please, just tell people
QA / R&D Team Mobile Devices | to use KDE."
SUSE LINUX Products GmbH, N=FCrnberg | -- Linus Torvalds

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

neci

author

2006-08-02 21:50 UTC #8 lore raw

linux:/dev # rfcomm
rfcomm0: 00:01:E3:58:23:EA channel 1 closed

Stefan Seyfried write:

Quoted 14 lines · neci

Quoted 9 lines
doing something wrong? i can upload files with OBEX object push client.
linux:/dev # cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1 linux:/dev # chmod 666 /dev/rfcomm*
linux:/dev # ls | grep rfcomm
rfcomm0
rfcomm1
linux:/dev # hcitool scan
Scanning ...
Quoted 3 lines
        00:01:E3:58:23:EA       Neci
linux:/dev # rfcomm bind 0 00:01:E3:58:23:EA 1
Can't create device: Address already in use

Quoted 4 lines

output of just plain "rfcomm"?
Oh - and stripping a bit of the useless quotes surely would not hurt :-)