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_sppd.1,v 1.3 2003/09/07 18:15:55 max Exp $
26.\" $FreeBSD: head/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.1 153209 2005-12-07 19:41:58Z emax $
27.\"
28.Dd April 26, 2003
29.Dt RFCOMM_SPPD 1
30.Os
31.Sh NAME
32.Nm rfcomm_sppd
33.Nd RFCOMM Serial Port Profile daemon
34.Sh SYNOPSIS
35.Nm
36.Op Fl bh
37.Fl a Ar address
38.Fl c Ar channel
39.Op Fl t Ar tty
40.Sh DESCRIPTION
41The
42.Nm
43utility is a Serial Port Profile daemon.
44It opens RFCOMM connection to the specified
45.Ar address
46server and
47.Ar channel .
48Once connection is established, the
49.Nm
50utility provides access to the server's remote serial port via stdin/stdout
51or via
52.Xr pty 4
53interface if
54.Fl t
55option was specified.
56.Pp
57The
58.Nm
59utility opens both master and slave pseudo terminals.
60This is done to ensure that RFCOMM connection stays open until
61.Nm
62is terminated.
63The data received from the master pseudo terminal are sent over
64the RFCOMM connection.
65The data received from the RFCOMM connection are written
66into master pseudo terminal.
67The application in its turn opens the slave pseudo
68terminal and operates on it just like it would operate over the standard serial
69port.
70.Pp
71The options are as follows:
72.Bl -tag -width indent
73.It Fl a Ar address
74This required option specifies the address of the remote RFCOMM server.
75The address can be specified as BD_ADDR or name.
76If name was specified then the
77.Nm
78utility will attempt to resolve the name via
79.Xr bt_gethostbyname 3 .
80.It Fl b
81Detach from the controlling terminal, i.e., run in background.
82.It Fl c Ar channel
83This option specifies RFCOMM channel to connect to.
84RFCOMM channel could either be a number between 1 and 30 or a service name.
85Supported service names are:
86.Cm DUN
87(for DialUp Networking service),
88.Cm FAX
89(for Fax service),
90.Cm LAN
91(for LAN Access Using PPP service) and
92.Cm SP
93(for Serial Port service).
94If channel was not specified then
95.Nm
96utility will try to obtain RFCOMM channel for Serial Port service via Service
97Discovery Protocol from the server.
98.It Fl h
99Display usage message and exit.
100.It Fl t Ar tty
101Slave pseudo tty name.
102If not set stdin/stdout will be used.
103This option is required if
104.Fl b
105option was specified.
106.El
107.Sh FILES
108.Bl -tag -width ".Pa /dev/tty[p-sP-S][0-9a-v]" -compact
109.It Pa /dev/pty[p-sP-S][0-9a-v]
110master pseudo terminals
111.It Pa /dev/tty[p-sP-S][0-9a-v]
112slave pseudo terminals
--- 11 unchanged lines hidden (view full) ---
124.Li 1 .
125Once the connection has been established,
126.Pa /dev/ttyp1
127can be used to talk to the remote serial port on the server.
128.Sh SEE ALSO
129.Xr bluetooth 3 ,
130.Xr ng_btsocket 4 ,
131.Xr pty 4 ,
132.Xr rfcomm_pppd 8
133.Sh AUTHORS
134.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
135.Sh BUGS
136Please report if found.
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_sppd.1,v 1.3 2003/09/07 18:15:55 max Exp $
26.\" $FreeBSD: head/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.1 153209 2005-12-07 19:41:58Z emax $
27.\"
28.Dd April 26, 2003
29.Dt RFCOMM_SPPD 1
30.Os
31.Sh NAME
32.Nm rfcomm_sppd
33.Nd RFCOMM Serial Port Profile daemon
34.Sh SYNOPSIS
35.Nm
36.Op Fl bh
37.Fl a Ar address
38.Fl c Ar channel
39.Op Fl t Ar tty
40.Sh DESCRIPTION
41The
42.Nm
43utility is a Serial Port Profile daemon.
44It opens RFCOMM connection to the specified
45.Ar address
46server and
47.Ar channel .
48Once connection is established, the
49.Nm
50utility provides access to the server's remote serial port via stdin/stdout
51or via
52.Xr pty 4
53interface if
54.Fl t
55option was specified.
56.Pp
57The
58.Nm
59utility opens both master and slave pseudo terminals.
60This is done to ensure that RFCOMM connection stays open until
61.Nm
62is terminated.
63The data received from the master pseudo terminal are sent over
64the RFCOMM connection.
65The data received from the RFCOMM connection are written
66into master pseudo terminal.
67The application in its turn opens the slave pseudo
68terminal and operates on it just like it would operate over the standard serial
69port.
70.Pp
71The options are as follows:
72.Bl -tag -width indent
73.It Fl a Ar address
74This required option specifies the address of the remote RFCOMM server.
75The address can be specified as BD_ADDR or name.
76If name was specified then the
77.Nm
78utility will attempt to resolve the name via
79.Xr bt_gethostbyname 3 .
80.It Fl b
81Detach from the controlling terminal, i.e., run in background.
82.It Fl c Ar channel
83This option specifies RFCOMM channel to connect to.
84RFCOMM channel could either be a number between 1 and 30 or a service name.
85Supported service names are:
86.Cm DUN
87(for DialUp Networking service),
88.Cm FAX
89(for Fax service),
90.Cm LAN
91(for LAN Access Using PPP service) and
92.Cm SP
93(for Serial Port service).
94If channel was not specified then
95.Nm
96utility will try to obtain RFCOMM channel for Serial Port service via Service
97Discovery Protocol from the server.
98.It Fl h
99Display usage message and exit.
100.It Fl t Ar tty
101Slave pseudo tty name.
102If not set stdin/stdout will be used.
103This option is required if
104.Fl b
105option was specified.
106.El
107.Sh FILES
108.Bl -tag -width ".Pa /dev/tty[p-sP-S][0-9a-v]" -compact
109.It Pa /dev/pty[p-sP-S][0-9a-v]
110master pseudo terminals
111.It Pa /dev/tty[p-sP-S][0-9a-v]
112slave pseudo terminals
--- 11 unchanged lines hidden (view full) ---
124.Li 1 .
125Once the connection has been established,
126.Pa /dev/ttyp1
127can be used to talk to the remote serial port on the server.
128.Sh SEE ALSO
129.Xr bluetooth 3 ,
130.Xr ng_btsocket 4 ,
131.Xr pty 4 ,
132.Xr rfcomm_pppd 8
133.Sh AUTHORS
134.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
135.Sh BUGS
136Please report if found.