rfcomm(1)

📦
version 5.87 · 6 versions
, in arch rolling, nixpkgs unstable, ubuntu stonking

💖 rfcomm(1) — RFCOMM configuration utility 💖

okay so bestie, welcome to rfcomm(1) from the Linux System Administration manual. This is literally the Bluetooth RFCOMM utility, and it’s lowkey iconic. We’re here to set up, maintain, and inspect — no cap. ✨

🌸 NAME 🌸

rfcomm — RFCOMM configuration utility

✨ SYNOPSIS ✨

rfcomm [OPTIONS] <COMMAND> <dev>

🦋 DESCRIPTION 🦋

rfcomm(1) is used to set up, maintain, and inspect the RFCOMM configuration of the Bluetooth subsystem in the Linux kernel. If no command is given, or if the option -a is used, rfcomm prints information about the configured RFCOMM devices. iykyk, that’s the whole flow. 💅

💅 OPTIONS 💅

  • -h — gives a list of possible commands. So helpful, fr fr.
  • -a — prints information about all configured RFCOMM devices. All of them, periodt.
  • -r — switch the TTY into raw mode. Heads up, bestie: it doesn’t work with bind. Important caveat!
  • -i <hciX> | <bdaddr> — the command is applied to device hciX, which must be the name or the address of an installed Bluetooth device. If not specified, the command will use the first available Bluetooth device.
  • -A — enable authentication. Secure the vibe. 🔐
  • -E — enable encryption. Extra safety energy.
  • -S — secure connection. Yes bestie.
  • -C — become the central of a piconet. Main character energy, honestly. 👑
  • -L <seconds> — set linger timeout.
⚠️ Caveat reminder because it matters: -r doesn’t work with bind. Don’t forget, bestie.

🎀 COMMANDS 🎀

  • show <dev> — display the information about the specified device. Simple, clean, slay.
  • connect <dev> [bdaddr] [channel] — connect the RFCOMM device to the remote Bluetooth device on the specified channel. If no channel is specified, it will use the channel number 1. This command can be terminated with the key sequence CTRL-C.
  • listen <dev> [channel] [cmd] — listen on a specified RFCOMM channel for incoming connections. If no channel is specified, it will use the channel number 1, but a channel must be specified before cmd. If cmd is given, it will be executed as soon as a client connects. When the child process terminates or the client disconnect, the command will terminate. Occurrences of {} in cmd will be replaced by the name of the device used by the connection. This command can be terminated with the key sequence CTRL-C.
  • watch <dev> [channel] [cmd] — watch is identical to listen except that when the child process terminates or the client disconnect, the command will restart listening with the same parameters. Obsessed with the resilience. 💪
  • bind <dev> [bdaddr] [channel] — this binds the RFCOMM device to a remote Bluetooth device. The command does not establish a connection to the remote device, it only creates the binding. The connection will be established right after an application tries to open the RFCOMM device. If no channel number is specified, it uses the channel number 1.
  • release <dev> — this command releases a defined RFCOMM binding. If all is specified for the RFCOMM device, then all bindings will be removed.

🌈 RESOURCES 🌈

The resource line is literally:

😭 REPORTING BUGS 😭

Bug reports go to:

  • <linux-bluetooth@vger.kernel.org>

👑 AUTHOR 👑

Marcel Holtmann <marcel@holtmann.org>

Free use of this software is granted under the terms of the GNU Lesser General Public Licenses (LGPL).

💖 okay that’s the whole page, bestie — this rfcomm(1) goodness comes from BlueZ, dated April 28, 2002, and it’s giving iconic manual energy. Slay. 💖

📦 where this page comes from