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_pppd.8,v 1.7 2003/09/07 18:32:11 max Exp $
51 daemon is a simple wrapper daemon that allows to use standard
54 It can operate in two modes: client and server.
58 opens an RFCOMM connection to the specified server's
62 Once RFCOMM connection is established,
68 mode with the specified
72 in its turn operates over the RFCOMM connection just like it would operate
73 over the standard serial port thus allowing user to
75 and connect to the Internet.
79 opens an RFCOMM socket and listens for incoming connections from remote clients.
80 Once the new incoming connection is accepted,
86 mode with the specified
90 in its turn operates over the RFCOMM connection just like it would operate over
91 the standard serial port thus providing network connectivity to remote clients.
93 The options are as follows:
94 .Bl -tag -width indent
96 In the client mode, this required option specifies the address of the remote
98 In the server mode, this option can be used to specify the local
100 By default, server will listen on
103 The address can be specified as BD_ADDR or name.
104 If name was specified then the
106 utility will attempt to resolve the name via
107 .Xr bt_gethostbyname 3 .
109 In both client and server modes, this required option specifies RFCOMM channel
110 to connect to or listen on.
111 In the server mode, RFCOMM channel should be a number between 1 and 30.
112 In the client mode, RFCOMM channel could either be a number between 1 and 30
114 Supported service names are:
116 (for DialUp Networking service) and
118 (for LAN Access Using PPP service).
119 If service name was specified instead of numeric RFCOMM channel then
121 utility will try to obtain RFCOMM channel for the service via Service
124 Act as an RFCOMM client.
125 This is the default mode.
127 Do not detach from the controlling terminal, i.e., run in foreground.
129 Display usage message and exit.
131 In both client and server modes, this required option specifies which
135 In the server mode, register the Serial Port (SP) service in addition to the
136 LAN Access Using PPP (LAN) service.
137 It appears that some cell phones are using the so-called
138 .Dq "callback mechanism" .
139 In this scenario, the user is trying to connect his cell phone to the Internet,
140 and user's host computer is acting as the gateway server.
141 It seems that it is not possible to tell the phone to just connect and start
142 using the LAN service.
143 Instead, the user's host computer must
145 the phone by connecting to the phone's SP service.
146 What happens next is the phone kills the existing connection and opens another
147 connection back to the user's host computer.
148 The phone really wants to use LAN service, but for whatever reason it looks
149 for the SP service on the user's host computer.
150 This brain damaged behavior was reported for Nokia 6600 and Sony/Ericsson P900.
152 Act as an RFCOMM server.
154 This option maps directly onto
157 command line option and tells
161 to only attempt to open
162 .Pa /dev/tun Ns Ar N .
163 This option only works in the client mode.
165 .Sh PPP CONFIGURATION
166 .Ss Important Notes on PPP Configuration
167 Special attention is required when adding new RFCOMM configurations to the
168 existing PPP configuration.
169 Please keep in mind that PPP will
171 execute commands in the
174 .Pa /etc/ppp/ppp.conf
176 Please make sure that the
180 contains commands that apply to
183 If you need to use PPP for both dialing out and accepting incoming
184 RFCOMM connections, please make sure you have moved all commands related to
187 section into an appropriate outgoing label.
189 One of the typical examples is the LAN access.
190 In this example, RFCOMM connection
191 is used as a null-modem connection between client and server.
193 and server will start talking PPP right after RFCOMM connection was established.
194 .Bd -literal -offset indent
198 set ifaddr 10.0.0.1 10.0.0.2 255.255.255.0
201 # Do not use PPP authentication. Assume that
202 # Bluetooth connection was authenticated already
212 supports both LAN and DUN (Dial-Up Networking) access.
213 The client's configuration for the LAN access is very similar to server's and
214 might look like this.
215 .Bd -literal -offset indent
222 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
223 # Do not use PPP authentication. Assume that
224 # Bluetooth connection was authenticated already
231 The client's configuration for the DUN access is different.
232 In this scenario, the client gets connected to the virtual serial port on the
234 To open a PPP session, client must dial a number.
237 will not execute any configured chat scripts.
240 option can be used to override this behavior.
241 The example of such configuration is shown below.
242 .Bd -literal -offset indent
244 # This is IMPORTANT option
247 # You might want to change these
252 # You might want to adjust dial string as well
253 set dial "ABORT BUSY ABORT NO\\\\sCARRIER TIMEOUT 5 \\
254 \\"\\" AT OK-AT-OK ATE1Q0 OK \\\\dATDT\\\\T TIMEOUT 40 CONNECT"
260 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
264 Note that by adjusting the initialization string, one can make CSD (Circuit
265 Switched Data), HSCSD (High Speed Circuit Switched Data) or GPRS (General
266 Packet Radio Service) connection.
267 The availability of the particular connection
268 type depends on the phone model and service plan activated on the phone.
272 .Dl "rfcomm_pppd -s -a 00:01:02:03:04:05 -C 1 -l rfcomm-server"
274 This command will start
277 The RFCOMM server will listen on local address
278 .Li 00:01:02:03:04:05
281 Once the incoming connection has been accepted,
291 .Dl "rfcomm_pppd -c -a 00:01:02:03:04:05 -C 1 -l rfcomm-client"
293 This command will start
297 will try to connect to the RFCOMM server at
298 .Li 00:01:02:03:04:05
313 utility in server mode will try to register Bluetooth LAN Access Over PPP
314 service with local SPD daemon.
315 If local SDP daemon is not running the
317 utility will exit with error.
326 .An Maksim Yevmenkin Aq m_evmenkin@yahoo.com