| rfcomm_pppd.8 (132711) | rfcomm_pppd.8 (133178) |
|---|---|
| 1.\" Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com> 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 9 unchanged lines hidden (view full) --- 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 23.\" SUCH DAMAGE. 24.\" 25.\" $Id: rfcomm_pppd.8,v 1.7 2003/09/07 18:32:11 max Exp $ | 1.\" Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com> 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 9 unchanged lines hidden (view full) --- 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 23.\" SUCH DAMAGE. 24.\" 25.\" $Id: rfcomm_pppd.8,v 1.7 2003/09/07 18:32:11 max Exp $ |
| 26.\" $FreeBSD: head/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 132711 2004-07-27 22:40:42Z emax $ | 26.\" $FreeBSD: head/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 133178 2004-08-05 16:32:41Z emax $ |
| 27.\" 28.Dd February 4, 2003 29.Dt RFCOMM_PPPD 8 30.Os 31.Sh NAME 32.Nm rfcomm_pppd 33.Nd RFCOMM PPP daemon 34.Sh SYNOPSIS 35.Nm 36.Fl c 37.Op Fl dh | 27.\" 28.Dd February 4, 2003 29.Dt RFCOMM_PPPD 8 30.Os 31.Sh NAME 32.Nm rfcomm_pppd 33.Nd RFCOMM PPP daemon 34.Sh SYNOPSIS 35.Nm 36.Fl c 37.Op Fl dh |
| 38.Fl a Ar BD_ADDR | 38.Fl a Ar address |
| 39.Fl C Ar channel 40.Fl l Ar label 41.Fl u Ar N 42.Nm 43.Fl s 44.Op Fl dhS | 39.Fl C Ar channel 40.Fl l Ar label 41.Fl u Ar N 42.Nm 43.Fl s 44.Op Fl dhS |
| 45.Op Fl a Ar BD_ADDR | 45.Op Fl a Ar address |
| 46.Fl C Ar channel 47.Fl l Ar label 48.Sh DESCRIPTION 49The 50.Nm 51daemon is a simple wrapper daemon that allows to use standard 52.Xr ppp 8 53on RFCOMM connection. --- 33 unchanged lines hidden (view full) --- 87.Ar label . 88The 89.Xr ppp 8 90in its turn operates over the RFCOMM connection just like it would operate over 91the standard serial port thus providing network connectivity to remote clients. 92.Pp 93The options are as follows: 94.Bl -tag -width indent | 46.Fl C Ar channel 47.Fl l Ar label 48.Sh DESCRIPTION 49The 50.Nm 51daemon is a simple wrapper daemon that allows to use standard 52.Xr ppp 8 53on RFCOMM connection. --- 33 unchanged lines hidden (view full) --- 87.Ar label . 88The 89.Xr ppp 8 90in its turn operates over the RFCOMM connection just like it would operate over 91the standard serial port thus providing network connectivity to remote clients. 92.Pp 93The options are as follows: 94.Bl -tag -width indent |
| 95.It Fl a Ar BD_ADDR 96In the client mode, this required option specifies the remote BD_ADDR of the | 95.It Fl a Ar address 96In the client mode, this required option specifies the address of the remote |
| 97RFCOMM server. 98In the server mode, this option can be used to specify the local | 97RFCOMM server. 98In the server mode, this option can be used to specify the local |
| 99BD_ADDR to listen on. | 99address to listen on. |
| 100By default, server will listen on 101.Dv ANY 102address. | 100By default, server will listen on 101.Dv ANY 102address. |
| 103The address can be specified as BD_ADDR or name. 104If name was specified then the 105.Nm 106utility will attempt to resolve the name via 107.Xr bt_gethostbyname 3 . |
|
| 103.It Fl C Ar channel 104In both client and server modes, this required option specifies RFCOMM channel 105to connect to or listen on. 106In the server mode, RFCOMM channel should be a number between 1 and 30. 107In the client mode, RFCOMM channel could either be a number between 1 and 30 108or a service name. 109Supported service names are: 110.Cm DUN --- 196 unchanged lines hidden (view full) --- 307.Nm 308utility in server mode will try to register Bluetooth LAN Access Over PPP 309service with local SPD daemon. 310If local SDP daemon is not running the 311.Nm 312utility will exit with error. 313.Sh SEE ALSO 314.Xr rfcomm_sppd 1 , | 108.It Fl C Ar channel 109In both client and server modes, this required option specifies RFCOMM channel 110to connect to or listen on. 111In the server mode, RFCOMM channel should be a number between 1 and 30. 112In the client mode, RFCOMM channel could either be a number between 1 and 30 113or a service name. 114Supported service names are: 115.Cm DUN --- 196 unchanged lines hidden (view full) --- 312.Nm 313utility in server mode will try to register Bluetooth LAN Access Over PPP 314service with local SPD daemon. 315If local SDP daemon is not running the 316.Nm 317utility will exit with error. 318.Sh SEE ALSO 319.Xr rfcomm_sppd 1 , |
| 320.Xr bluetooth 3 , |
|
| 315.Xr ng_btsocket 4 , 316.Xr ppp 8 , 317.Xr sdpcontrol 8 , 318.Xr sdpd 8 319.Sh AUTHORS 320.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com | 321.Xr ng_btsocket 4 , 322.Xr ppp 8 , 323.Xr sdpcontrol 8 , 324.Xr sdpd 8 325.Sh AUTHORS 326.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com |