Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sdpd(8) [netbsd man page]

SDPD(8) 						    BSD System Manager's Manual 						   SDPD(8)

sdpd -- Bluetooth Service Discovery Protocol daemon SYNOPSIS
sdpd [-dh] [-c path] [-G group] [-g group] [-u user] DESCRIPTION
The sdpd daemon keeps a database of Bluetooth Service Records registered on the host and responds to Service Discovery inquiries from remote Bluetooth devices. In order to discover services, remote Bluetooth devices send Service Search and Service Attribute or Service Search Attribute requests over Bluetooth L2CAP connections on the SDP PSM (0x0001). The sdpd daemon will try to find matching Service Records in its Service Database and will return the requested record extracts for the remote device to interpret. The remote device will then make a separate connection in order to access the service. Bluetooth applications, running on the host, are able to insert, remove and update Service Records with the sdpd daemon via the control socket. It is possible to query entire contents of the Service Database locally with sdpquery(1) using the -l option. The command line options are as follows: -c path Specify path to the control socket. The default path is /var/run/sdp. -d Do not detach from the controlling terminal. -G group Grant permission to members of the group to modify the sdpd Service Database. -g group Specifies the group the sdpd should run as after it initializes. The value specified may be either a group name or a numeric group ID. This only works if sdpd was started as root. The default group name is ``_sdpd''. -h Display usage message and exit. -u user Specifies the user the sdpd should run as after it initializes. The value specified may be either a user name or a numeric user ID. This only works if sdpd was started as root. The default user name is ``_sdpd''. FILES
/var/run/sdp SEE ALSO
sdpquery(1), sdp(3) The "Service Discovery Protocol" section of the Bluetooth Core specifications, available at "" HISTORY
The original sdpd daemon first appeared in FreeBSD 5.3 and was imported into NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc. This version was rewritten by Iain Hibbert for NetBSD 6.0 in order to allow Bluetooth applications to fully specify service records. AUTHORS
Maksim Yevmenkin <> Iain Hibbert CAVEATS
The sdpd daemon will listen for incoming L2CAP connections on a wildcard BD_ADDR. In case of multiple Bluetooth controllers connected to the same host it is possible to limit visibility of Service Records according to the controller the connection is made through. Requests to insert, remove or update service records can only be made via the control socket. The sdpd daemon will check the peer's creden- tials and will only accept the request when the peer is the superuser, of if the peer is a member of the group specified with the -G option. The sdpd daemon does not check for duplicated Service Records and only performs minimal validation of the record data sent in the Insert/Update Record requests. It is assumed that application must obtain all required resources such as RFCOMM channels etc., before regis- tering the service. BUGS
sdpd only ever generates 16-bit sequence headers, so if a response was to grow over UINT16_MAX, the sequence header will be wrong. There is no way for clients to discover the maximum packet size that sdpd will accept on the local socket. Currently this is SDP_LOCAL_MTU as defined in <bluetooth/sdp.h>. BSD
May 7, 2009 BSD

Check Out this Related Man Page

RFCOMM_SPPD(1)						    BSD General Commands Manual 					    RFCOMM_SPPD(1)

rfcomm_sppd -- RFCOMM Serial Port Profile daemon SYNOPSIS
rfcomm_sppd [-d device] [-m mode] [-p psm] [-s service] [-t tty] {-a address | [-c channel]} DESCRIPTION
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 con- nection, or the first unused channel if none was given. 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 In 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 Name of service class to connect to or register. If no service is given, the default "Serial Port" service class will be used. Known service classes are: DUN Dialup Networking LAN LAN access using PPP SP Serial Port In client mode, the service class may be given as a channel number, for instances where the remote device does not provide Ser- vice Discovery. -t tty Slave pseudo tty name. If this option is given, rfcomm_sppd will detach from the controlling process after the Bluetooth connec- tion is made, and operate over the named pty(4) pair. Otherwise, stdin/stdout will be used. FILES
/dev/pty[p-sP-S][0-9a-v] master pseudo terminals /dev/tty[p-sP-S][0-9a-v] slave pseudo terminals EXIT STATUS
The rfcomm_sppd utility exits 0 on success, and >0 if an error occurs. EXAMPLES
rfcomm_sppd -a 00:01:02:03:04:05 -s 1 -t /dev/ttyp1 Will open an RFCOMM connection to the server at 00:01:02:03:04:05 on channel 1. Once the connection has been established, rfcomm_sppd will detach and /dev/ttyp1 can be used to communicate with the remote serial port on the server, e.g. with the use of cu -l /dev/ttyp1 In order to use rfcomm_sppd to automatically create a secured link for pppd(8), use pty "rfcomm_sppd -a 00:01:02:03:04:05 -s DUN -m secure" in your pppd(8) configuration file. SEE ALSO
bluetooth(3), bluetooth(4), pty(4), btconfig(8), pppd(8), sdpd(8) HISTORY
The rfcomm_sppd program first appeared in FreeBSD and was ported to NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc. AUTHORS
Maksim Yevmenkin <>, Iain Hibbert BUGS
Please report if found. BSD
November 2, 2010 BSD
Man Page