1 .\" Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com>
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
25 .\" $Id: rfcomm_sppd.1,v 1.3 2003/09/07 18:15:55 max Exp $
33 .Nd RFCOMM Serial Port Profile daemon
42 utility is a Serial Port Profile daemon.
43 It can operate in two modes: client and server.
47 opens RFCOMM connection to the specified
51 Once connection is established, the
53 utility provides access to the server's remote serial port via stdin/stdout
64 will operate in server mode and act as RFCOMM server,
67 address and advertising a virtual serial port
73 options was specified,
74 the server side of the virtual serial port is attached to a pseudo-terminal.
75 Otherwise the virtual serial port is attached to the stdin/stdout.
77 should be run as root in order to communicate with
83 utility opens both master and slave pseudo terminals.
84 This is done to ensure that RFCOMM connection stays open until
87 The data received from the master pseudo terminal are sent over
88 the RFCOMM connection.
89 The data received from the RFCOMM connection are written
90 into master pseudo terminal.
91 The application in its turn opens the slave pseudo
92 terminal and operates on it just like it would operate over the standard serial
95 The options are as follows:
96 .Bl -tag -width indent
99 this required option specifies the address of the remote RFCOMM server.
100 If this option is specified in server mode,
102 will only accept connections from the
106 The address can be specified as BD_ADDR or name.
107 If name was specified then
109 utility will attempt to resolve the name via
110 .Xr bt_gethostbyname 3 .
112 Detach from the controlling terminal, i.e., run in background.
114 In both client and server mode,
115 this option specifies the RFCOMM channel to connect to or listen on.
117 the channel should be a number between 1 and 30.
122 RFCOMM channel number.
123 The actual RFCOMM channel will be obtained via
125 call and will be used to register Serial Port service with
128 the channel could either be a number between 1 and 30 or a service name.
129 Supported service names are:
131 (for DialUp Networking service),
135 (for LAN Access Using PPP service) and
137 (for Serial Port service).
138 If channel was not specified then
140 utility will try to obtain RFCOMM channel for Serial Port service via Service
141 Discovery Protocol from the server.
143 Display usage message and exit.
148 Use slave pseudo tty.
149 If not set stdin/stdout will be used.
150 This option is required if
152 option was specified.
155 .Bl -tag -width ".Pa /dev/pts/[num]" -compact
156 .It Pa /dev/pts/[num]
157 slave pseudo terminals
162 .Dl "rfcomm_sppd -a 00:01:02:03:04:05 -c 1 -t"
166 utility and open RFCOMM connection to the server at
167 .Li 00:01:02:03:04:05
170 Once the connection has been established, a
172 can be used to talk to the remote serial port on the server.
174 prints the name of the
184 .An Maksim Yevmenkin Aq Mt m_evmenkin@yahoo.com
186 Please report if found.