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 Display usage message and exit.
131 In both client and server mode, this required option specifies which
135 In server mode, register the
137 (Serial Port) service in addition to the
139 (LAN Access Using PPP) service.
141 It appears that some cell phones are using the so-called
142 .Dq "callback mechanism" .
143 In this scenario, the user is trying to connect his cell phone to the Internet,
144 while the user's host computer is acting as the gateway server.
145 It seems that it is not possible to tell the phone to just connect and start
149 Instead, the user's host computer must
151 the phone by connecting to the phone's
154 What happens next is the phone kills the existing connection and opens another
155 connection back to the user's host computer.
156 The phone really wants to use the
158 service, but for whatever reason it looks for the
160 service on the user's host computer.
161 This brain-damaged behavior was reported for the Nokia 6600 and the
164 Act as an RFCOMM server.
166 This option maps directly to the
169 command-line option and tells
173 to only attempt to open
174 .Pa /dev/tun Ns Ar N .
175 This option only works in client mode.
177 .Sh PPP CONFIGURATION
178 .Ss Important Notes on PPP Configuration
179 Special attention is required when adding new RFCOMM configurations to the
180 existing PPP configuration.
181 Please keep in mind that PPP will
183 execute commands in the
186 .Pa /etc/ppp/ppp.conf
188 Please make sure that the
192 contains commands that apply to
195 If you need to use PPP for both dialing out and accepting incoming
196 RFCOMM connections, please make sure you have moved all commands related to
199 section into an appropriate outgoing label.
201 One of the typical examples is the LAN access.
202 In this example, an RFCOMM connection
203 is used as a null-modem connection between a client and a server.
204 Both client and server will start talking PPP right after the RFCOMM
205 connection has been established.
206 .Bd -literal -offset indent
210 set ifaddr 10.0.0.1 10.0.0.2 255.255.255.0
214 # Do not use PPP authentication. Assume that
215 # Bluetooth connection was authenticated already
224 utility supports both
226 (LAN Access Using PPP) and
228 (Dial-Up Networking) access.
229 The client's configuration for
231 access is very similar to the server's and might look like this:
232 .Bd -literal -offset indent
239 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
240 # Do not use PPP authentication. Assume that
241 # Bluetooth connection was authenticated already
248 The client's configuration for
251 In this scenario, the client gets connected to the virtual serial port on the
253 To open a PPP session, the client must dial a number.
256 will not execute any configured chat scripts.
259 option can be used to override this behavior.
260 An example configuration is shown below:
261 .Bd -literal -offset indent
263 # This is IMPORTANT option
266 # You might want to change these
271 # You might want to adjust dial string as well
272 set dial "ABORT BUSY ABORT NO\\\\sCARRIER TIMEOUT 5 \\
273 \\"\\" AT OK-AT-OK ATE1Q0 OK \\\\dATDT\\\\T TIMEOUT 40 CONNECT"
279 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
283 Note that by adjusting the initialization string, one can make a CSD (Circuit
284 Switched Data), HSCSD (High Speed Circuit Switched Data) or GPRS (General
285 Packet Radio Service) connection.
286 The availability of the particular connection
287 type depends on the phone model and service plan activated on the phone.
291 .Dl "rfcomm_pppd -s -a 00:01:02:03:04:05 -C 1 -l rfcomm-server"
293 This command will start
296 The RFCOMM server will listen on local address
297 .Li 00:01:02:03:04:05
300 Once the incoming connection has been accepted,
310 .Dl "rfcomm_pppd -c -a 00:01:02:03:04:05 -C 1 -l rfcomm-client"
312 This command will start
316 will try to connect to the RFCOMM server at
317 .Li 00:01:02:03:04:05
332 utility in server mode will try to register the Bluetooth LAN Access Over PPP
333 service with the local SPD daemon.
334 If the local SDP daemon is not running,
336 will exit with an error.
345 .An Maksim Yevmenkin Aq m_evmenkin@yahoo.com