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
43 utility is a Serial Port Profile daemon.
44 It can operate in two modes: client and server.
48 opens RFCOMM connection to the specified
52 Once connection is established, the
54 utility provides access to the server's remote serial port via stdin/stdout
65 will operate in server mode and act as RFCOMM server,
68 address and advertising a virtual serial port
74 option must be specified;
75 the server side of the virtual serial port is attached to the pseudo-terminal
78 should be run as root in order to communicate with
84 utility opens both master and slave pseudo terminals.
85 This is done to ensure that RFCOMM connection stays open until
88 The data received from the master pseudo terminal are sent over
89 the RFCOMM connection.
90 The data received from the RFCOMM connection are written
91 into master pseudo terminal.
92 The application in its turn opens the slave pseudo
93 terminal and operates on it just like it would operate over the standard serial
96 The options are as follows:
97 .Bl -tag -width indent
100 this required option specifies the address of the remote RFCOMM server.
101 If this option is specified in server mode,
103 will only accept connections from the
107 The address can be specified as BD_ADDR or name.
108 If name was specified then
110 utility will attempt to resolve the name via
111 .Xr bt_gethostbyname 3 .
113 Detach from the controlling terminal, i.e., run in background.
115 In both client and server mode,
116 this required option specifies the RFCOMM channel to connect to or listen on.
118 the channel should be a number between 1 and 30.
121 will try to allocate RFCOMM channel number based on process ID.
123 the channel could either be a number between 1 and 30 or a service name.
124 Supported service names are:
126 (for DialUp Networking service),
130 (for LAN Access Using PPP service) and
132 (for Serial Port service).
133 If channel was not specified then
135 utility will try to obtain RFCOMM channel for Serial Port service via Service
136 Discovery Protocol from the server.
138 Display usage message and exit.
143 Slave pseudo tty name.
144 If not set stdin/stdout will be used.
145 This option is required if
149 option was specified.
152 .Bl -tag -width ".Pa /dev/tty[p-sP-S][0-9a-v]" -compact
153 .It Pa /dev/pty[p-sP-S][0-9a-v]
154 master pseudo terminals
155 .It Pa /dev/tty[p-sP-S][0-9a-v]
156 slave pseudo terminals
161 .Dl "rfcomm_sppd -a 00:01:02:03:04:05 -c 1 -t /dev/ttyp1"
165 utility and open RFCOMM connection to the server at
166 .Li 00:01:02:03:04:05
169 Once the connection has been established,
171 can be used to talk to the remote serial port on the server.
179 .An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
181 Please report if found.