1RFCOMM(1) RFCOMM(1)
2
3
4
6 rfcomm - RFCOMM configuration utility
7
9 rfcomm [ options ] < command > < dev >
10
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
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 -i <hciX> | <bdaddr>
25 The command is applied to device hciX, which must be the name or
26 the address of an installed Bluetooth device. If not specified,
27 the command will be use the first available Bluetooth device.
28
29 -A Enable authentification
30
31 -E Enable encryption
32
33 -S Secure connection
34
35 -M Become the master of a piconet
36
37 -L <seconds>
38 Set linger timeout
39
41 show <dev>
42 Display the information about the specified device.
43
44 connect <dev> [bdaddr] [channel]
45 Connect the RFCOMM device to the remote Bluetooth device on the
46 specified channel. If no channel is specified, it will use the
47 channel number 1. This command can be terminated with the key
48 sequence CTRL-C.
49
50 listen <dev> [channel] [cmd]
51 Listen on a specified RFCOMM channel for incoming connections.
52 If no channel is specified, it will use the channel number 1,
53 but a channel must be specified before cmd. If cmd is given, it
54 will be executed as soon as a client connects. When the child
55 process terminates or the client disconnect, the command will
56 terminate. Occurrences of {} in cmd will be replaced by the
57 name of the device used by the connection. This command can be
58 terminated with the key sequence CTRL-C.
59
60 watch <dev> [channel] [cmd]
61 Watch is identical to listen except that when the child process
62 terminates or the client disconnect, the command will restart
63 listening with the same parameters.
64
65 bind <dev> [bdaddr] [channel]
66 This binds the RFCOMM device to a remote Bluetooth device. The
67 command does not establish a connection to the remote device, it
68 only creates the binding. The connection will be established
69 right after an application tries to open the RFCOMM device. If
70 no channel number is specified, it uses the channel number 1.
71
72 release <dev>
73 This command releases a defined RFCOMM binding.
74
75 If all is specified for the RFCOMM device, then all bindings
76 will be removed.
77
79 Written by Marcel Holtmann <marcel@holtmann.org>.
80
81
82
83 APRIL 28, 2002 RFCOMM(1)