1RFCOMM(1)                                                            RFCOMM(1)
2
3
4

NAME

6       rfcomm - RFCOMM configuration utility
7

SYNOPSIS

9       rfcomm [ options ] < command > < dev >
10

DESCRIPTION

12       rfcomm  is  used to set up, maintain, and inspect the RFCOMM configura‐
13       tion of the Bluetooth subsystem in the Linux kernel. If no  command  is
14       given, or if the option -a is used, rfcomm prints information about the
15       configured RFCOMM devices.
16

OPTIONS

18       -h     Gives a list of possible commands.
19
20       -a     Prints information about all configured RFCOMM devices.
21
22       -r     Switch TTY into raw mode (doesn't work with "bind").
23
24       -f <file>
25              Specify alternate config file.
26
27       -i <hciX> | <bdaddr>
28              The command is applied to device -A Enable  authentication.   -E
29              Enable  encryption.  -S Secure connection.  -M Become the master
30              of a piconet.  hciX , which must be the name or the  address  of
31              an  installed  Bluetooth  device.  If not specified, the command
32              will be use the first available Bluetooth device.
33
34       -A     Enable authentification
35
36       -E     Enable encryption
37
38       -S     Secure connection
39
40       -M     Become the master of a piconet
41
42       -L <seconds>
43              Set linger timeout
44

COMMANDS

46       show <dev>
47              Display the information about the specified device.
48
49       connect <dev> [bdaddr] [channel]
50              Connect the RFCOMM device to the remote Bluetooth device on  the
51              specified  channel.  If no channel is specified, it will use the
52              channel number 1. If also the Bluetooth address is left out,  it
53              tries to read the data from the config file. This command can be
54              terminated with the key sequence CTRL-C.
55
56       listen <dev> [channel] [cmd]
57              Listen on a specified RFCOMM channel for  incoming  connections.
58              If  no  channel  is specified, it will use the channel number 1,
59              but a channel must be specified before cmd. If cmd is given,  it
60              will  be  executed  as soon as a client connects. When the child
61              process terminates or the client disconnect,  the  command  will
62              terminate.  Occurences of {} in cmd will be replaced by the name
63              of the device used by the connection. This command can be termi‐
64              nated with the key sequence CTRL-C.
65
66       watch <dev> [channel] [cmd]
67              Watch  is identical to listen except that when the child process
68              terminates or the client disconnect, the  command  will  restart
69              listening with the same parameters.
70
71       bind <dev> [bdaddr] [channel]
72              This  binds  the RFCOMM device to a remote Bluetooth device. The
73              command did not establish a connection to the remote device,  it
74              only  creates  the  binding.  The connection will be established
75              right after an application tries to open the RFCOMM  device.  If
76              no channel number is specified, it uses the channel number 1. If
77              the Bluetooth address is also left out, it  tries  to  read  the
78              data from the config file.
79
80              If all is specified for the RFCOMM device, then all devices that
81              have bind yes set in the config will be bound.
82
83       release <dev>
84              This command releases a defined RFCOMM binding.
85
86              If all is specified for the RFCOMM  device,  then  all  bindings
87              will be removed.  This command didn't care about the settings in
88              the config file.
89

AUTHOR

91       Written by Marcel Holtmann <marcel@holtmann.org>.
92
93
94
95                                APRIL 28, 2002                       RFCOMM(1)