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 the use of
53 via an RFCOMM connection.
54 It can operate in two modes: client and server.
58 opens an RFCOMM connection to the specified server's
62 Once the RFCOMM connection is established,
68 mode with the specified
72 operates over the RFCOMM connection just like it would over a standard serial
73 port, thus allowing a 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 operates over the RFCOMM connection just like it would over a standard serial
91 port, thus providing network connectivity to remote clients.
93 The options are as follows:
94 .Bl -tag -width indent
96 In client mode, this required option specifies the address of the remote
98 In server mode, this option can be used to specify the local
100 By default, in server mode, the daemon will listen on
103 The address can be specified as BD_ADDR or name.
104 If a name was specified, the
106 utility will attempt to resolve the name via
107 .Xr bt_gethostbyname 3 .
109 In both client and server mode, this required option specifies the RFCOMM
110 channel to connect to or listen on.
111 In server mode, the channel should be a number between 1 and 30.
112 In client mode, the channel could either be a number between 1 and 30
114 Supported service names are:
116 (Dial-Up Networking) and
118 (LAN Access Using PPP).
119 If a service name is used instead of a numeric channel number, then
121 will try to obtain an RFCOMM channel number via SDP
122 (Service Discovery Protocol).
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 In server mode, register the
131 (Dial-Up Networking) service in addition to the
133 (LAN Access Using PPP) service.
134 AT-command exchange can be faked with
138 Display usage message and exit.
140 In both client and server mode, this required option specifies which
144 In server mode, register the
146 (Serial Port) service in addition to the
148 (LAN Access Using PPP) service.
150 It appears that some cell phones are using the so-called
151 .Dq "callback mechanism" .
152 In this scenario, the user is trying to connect his cell phone to the Internet,
153 while the user's host computer is acting as the gateway server.
154 It seems that it is not possible to tell the phone to just connect and start
158 Instead, the user's host computer must
160 the phone by connecting to the phone's
163 What happens next is the phone kills the existing connection and opens another
164 connection back to the user's host computer.
165 The phone really wants to use the
167 service, but for whatever reason it looks for the
169 service on the user's host computer.
170 This brain-damaged behavior was reported for the Nokia 6600 and the
173 Act as an RFCOMM server.
175 This option maps directly to the
178 command-line option and tells
182 to only attempt to open
183 .Pa /dev/tun Ns Ar N .
184 This option only works in client mode.
186 .Sh PPP CONFIGURATION
187 .Ss Important Notes on PPP Configuration
188 Special attention is required when adding new RFCOMM configurations to the
189 existing PPP configuration.
190 Please keep in mind that PPP will
192 execute commands in the
195 .Pa /etc/ppp/ppp.conf
197 Please make sure that the
201 contains commands that apply to
204 If you need to use PPP for both dialing out and accepting incoming
205 RFCOMM connections, please make sure you have moved all commands related to
208 section into an appropriate outgoing label.
210 One of the typical examples is the LAN access.
211 In this example, an RFCOMM connection
212 is used as a null-modem connection between a client and a server.
213 Both client and server will start talking PPP right after the RFCOMM
214 connection has been established.
215 .Bd -literal -offset indent
219 set ifaddr 10.0.0.1 10.0.0.2 255.255.255.0
223 # Do not use PPP authentication. Assume that
224 # Bluetooth connection was authenticated already
233 utility supports both
235 (LAN Access Using PPP) and
237 (Dial-Up Networking) access.
238 The client's configuration for
240 access is very similar to the server's and might look like this:
241 .Bd -literal -offset indent
248 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
249 # Do not use PPP authentication. Assume that
250 # Bluetooth connection was authenticated already
257 The client's configuration for
260 In this scenario, the client gets connected to the virtual serial port on the
262 To open a PPP session, the client must dial a number.
265 will not execute any configured chat scripts.
268 option can be used to override this behavior.
269 An example configuration is shown below:
270 .Bd -literal -offset indent
272 # This is IMPORTANT option
275 # You might want to change these
280 # You might want to adjust dial string as well
281 set dial "ABORT BUSY ABORT NO\\\\sCARRIER TIMEOUT 5 \\
282 \\"\\" AT OK-AT-OK ATE1Q0 OK \\\\dATDT\\\\T TIMEOUT 40 CONNECT"
288 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
292 Note that by adjusting the initialization string, one can make a CSD (Circuit
293 Switched Data), HSCSD (High Speed Circuit Switched Data) or GPRS (General
294 Packet Radio Service) connection.
295 The availability of the particular connection
296 type depends on the phone model and service plan activated on the phone.
300 .Dl "rfcomm_pppd -s -a 00:01:02:03:04:05 -C 1 -l rfcomm-server"
302 This command will start
305 The RFCOMM server will listen on local address
306 .Li 00:01:02:03:04:05
309 Once the incoming connection has been accepted,
319 .Dl "rfcomm_pppd -c -a 00:01:02:03:04:05 -C 1 -l rfcomm-client"
321 This command will start
325 will try to connect to the RFCOMM server at
326 .Li 00:01:02:03:04:05
346 .An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
350 utility in server mode will try to register the Bluetooth LAN Access Over PPP
351 service with the local SPD daemon.
352 If the local SDP daemon is not running,
354 will exit with an error.