The
rfcomm_sppd utility is a Serial Port Profile daemon, providing serial access over an RFCOMM connection to a remote device.
rfcomm_sppd can work in client or server mode.
In client mode,
rfcomm_sppd initiates an RFCOMM connection to the
service at the remote
address.
In server mode,
rfcomm_sppd registers the
service with the local SDP server and listens on the specified RFCOMM
channel for an incoming connection.
The options are as follows:
-a address
Client mode. Specify the address of the remote RFCOMM device. The address can be specified as BD_ADDR or name. If given as a name, then the
rfcomm_sppd utility will attempt to resolve the name via
bt_gethostbyname(3).
-c channel
Server mode. Specify the RFCOMM channel number to listen on.
rfcomm_sppd will register the service with the local
sdpd(8) daemon. Note that registering services with
sdpd(8) is a privileged operation.
-d device
Use the local device with the specified address. The device can be specified by BD_ADDR or device name. See
btconfig(8) for a list of available devices. If no
device is specified, the connection will be set up on a system determined device.
-m mode
Set connection link mode. Supported modes are:
auth
require devices be paired.
encrypt
auth, plus enable encryption.
secure
encryption, plus change of link key.
-p psm
Specify the “Protocol/Service Multiplexer” value to be used for the RFCOMM protocol. In client mode where Service Discovery is being used, this value will be ignored.
-s service
This is the service class that will be searched for on the remote device. If no
service is given, the default “Serial Port” service class will be used. Known service classes are:
In client mode, the service class may be given as a channel number, for instances where the remote device does not provide Service Discovery.
-t tty
Slave pseudo tty name. If this option is given,
rfcomm_sppd will detach from the controlling process after the Bluetooth connection is made, and operate over the named
pty(4) pair. Otherwise, stdin/stdout will be used.