Copyright (c) 2006 Itronix Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. The name of Itronix Inc. may not be used to endorse
or promote products derived from this software without specific
prior written permission.
THIS SOFTWARE IS PROVIDED BY ITRONIX INC. ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ITRONIX INC. BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com>
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
.Dd April 10, 2007 .Dt RFCOMM_SPPD 1 .Os .Sh NAME .Nm rfcomm_sppd .Nd RFCOMM Serial Port Profile daemon .Sh SYNOPSIS .Nm .Op Fl d Ar device .Op Fl m Ar mode .Op Fl s Ar service .Op Fl t Ar tty rq Fl a Ar address | Fl c Ar channel .Sh DESCRIPTION The .Nm utility is a Serial Port Profile daemon, providing serial access over an RFCOMM connection to a remote device. .Nm can work in client or server mode.
p In client mode, .Nm initiates an RFCOMM connection to the .Ar service at the remote .Ar address .
p In server mode, .Nm registers the .Ar service with the local SDP server and listens on the specified RFCOMM .Ar channel for an incoming connection.
p The options are as follows: l -tag -width ".Fl c Ar channel" t Fl a Ar 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 .Nm utility will attempt to resolve the name via .Xr bt_gethostbyname 3 . t Fl c Ar channel Server mode. Specify the RFCOMM channel number to listen on. .Nm will register the service with the local .Xr sdpd 8 daemon. Note that registering services with .Xr sdpd 8 is a privileged operation. t Fl d Ar device Use the local device with the specifed address. The device can be specified by BD_ADDR or device name. See .Xr btconfig 8 for a list of available devices. If no .Ar device is specified, the connection will be set up on a system determined device. t Fl m Ar mode Set connection link mode. Supported modes are:
p l -tag -compact -offset indent t auth require devices be paired. t encrypt auth, plus enable encryption. t secure encryption, plus change of link key. .El t Fl s Ar service This is the service class that will be searched for on the remote device. If no .Ar service is given, the default .Qq Serial Port service class will be used. Known service classes are:
p l -tag -compact -offset indent t DUN Dialup Networking t LAN LAN access using PPP t SP Serial Port .El
p 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 Fl t Ar tty Slave pseudo tty name. If this option is given, .Nm will detach from the controlling process after the bluetooth connection is made, and operate over the named .Xr pty 4 pair. Otherwise, stdin/stdout will be used. .El .Sh EXIT STATUS .Ex -std .Sh FILES l -tag -width ".Pa /dev/tty[p-sP-S][0-9a-v]" -compact t Pa /dev/pty[p-sP-S][0-9a-v] master pseudo terminals t Pa /dev/tty[p-sP-S][0-9a-v] slave pseudo terminals .El .Sh EXAMPLES .Dl rfcomm_sppd -a 00:01:02:03:04:05 -s 1 -t /dev/ttyp1
p Will open an RFCOMM connection to the server at .Li 00:01:02:03:04:05 on channel .Li 1 . Once the connection has been established, .Nm will detach and
a /dev/ttyp1 can be used to communicate with the remote serial port on the server, e.g. with the use of
p In order to use .Nm to automatically create a secured link for .Xr pppd 8 , use .Dl pty Qo rfcomm_sppd -a 00:01:02:03:04:05 -s DUN -m secure Qc
p in your .Xr pppd 8 configuration file. .Sh SEE ALSO .Xr bluetooth 3 , .Xr bluetooth 4 , .Xr pty 4 , .Xr btconfig 8 , .Xr pppd 8 , .Xr sdpd 8 .Sh HISTORY The .Nm program first appeared in .Fx and was ported to .Nx 4.0 by .An Iain Hibbert under the sponsorship of .An Itronix, Inc . .Sh AUTHORS .An Maksim Yevmenkin Aq m_evmenkin@yahoo.com , .An Iain Hibbert .Sh BUGS Please report if found.