os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

In Bluetooth section:

Browse source 
- s/chapter/section where needed
- s/man page/manual page
- Some punctuation and tags fixes
- Avoid the use of "here" for URLs, it's better to display the full URL
This commit is contained in:
Marc Fonvieille 2004-07-23 07:02:03 +00:00
parent 373d8d0f3f
commit 728f0a1acd
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=21626
1 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

30
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1121,7 +1121,7 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
&man.ng.ubt.4; drivers. The 3Com Bluetooth PC Card 3CRWB60-A is
supported by the &man.ng.bt3c.4; driver. Serial and UART based
Bluetooth devices are supported via &man.sio.4;, &man.ng.h4.4;
and &man.hcseriald.8;. This chapter describes the use of the USB
and &man.hcseriald.8;. This section describes the use of the USB
Bluetooth dongle. Bluetooth support is available in &os; 5.0 and newer
systems.</para>
</sect2>
@ -1130,18 +1130,18 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<title>Plugging in the Device</title>
<para>By default Bluetooth device drivers are available as kernel modules.
Before attaching a device, you will need to load the driver into the
kernel.</para>
kernel:</para>
<screen>&prompt.root; <userinput>kldload ng_ubt</userinput></screen>
<para>If the Bluetooth device is present in the system during system
startup, load the module from
<filename>/boot/loader.conf</filename>.</para>
<filename>/boot/loader.conf</filename>:</para>
<programlisting>ng_ubt_load="YES"</programlisting>
<para>Plug in your USB dongle. The output similar to the following will
appear on the console (or in syslog).</para>
appear on the console (or in syslog):</para>
<screen>ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
@ -1190,7 +1190,7 @@ Number of SCO packets: 8</screen>
the L2CAP node (upstream). All HCI operations must be performed
on the HCI node and not on the device driver node. Default name
for the HCI node is <quote>devicehci</quote>.
For more details refer to the &man.ng.hci.4; man page.</para>
For more details refer to the &man.ng.hci.4; manual page.</para>
<para>One of the most common tasks is discovery of Bluetooth devices in
RF proximity. This operation is called <emphasis>inquiry</emphasis>.
@ -1219,7 +1219,7 @@ Inquiry complete. Status: No error [00]</screen>
The <filename>/etc/bluetooth/hosts</filename> file contains information
regarding the known Bluetooth hosts. The following example shows how
to obtain human readable name that was assigned to the remote
device.</para>
device:</para>
<screen>&prompt.user; <userinput>hccontrol -n ubt0hci remote_name_request 00:80:37:29:19:a4</userinput>
BD_ADDR: 00:80:37:29:19:a4
@ -1233,7 +1233,7 @@ Name: Pav's T39</screen>
Bluetooth units involved), or a point-to-multipoint connection. In the
point-to-multipoint connection the connection is shared among several
Bluetooth devices. The following example shows how to obtain the list
of active baseband connections for the local device.</para>
of active baseband connections for the local device:</para>
<screen>&prompt.user; <userinput>hccontrol -n ubt0hci read_connection_list</userinput>
Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State
@ -1278,11 +1278,11 @@ Reason: Connection terminated by local host [0x16]</screen>
connected to the Bluetooth HCI node (downstream) and Bluetooth sockets
nodes (upstream). Default name for the L2CAP node is
<quote>devicel2cap</quote>. For more details refer to the
&man.ng.l2cap.4; man page.</para>
&man.ng.l2cap.4; manual page.</para>
<para>A useful command is &man.l2ping.8;, which can be used to ping
other devices. Some Bluetooth implementations might not return all of
the data sent to them, so <emphasis>0 bytes</emphasis> in the following
the data sent to them, so <literal>0 bytes</literal> in the following
example is normal.</para>
<screen>&prompt.root; <userinput>l2ping -a 00:80:37:29:19:a4</userinput>
@ -1294,7 +1294,7 @@ Reason: Connection terminated by local host [0x16]</screen>
<para>The &man.l2control.8; utility is used to perform various operations
on L2CAP nodes. This example shows how to obtain the list of logical
connections (channels) and the list of baseband connections for the
local device.</para>
local device:</para>
<screen>&prompt.user; <userinput>l2control -a 00:02:72:00:d4:1a read_channel_list</userinput>
L2CAP channels:
@ -1467,7 +1467,7 @@ Bluetooth Profile Descriptor List:
<screen>&prompt.user; <userinput>sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH</userinput></screen>
<para>Offering services on &os; to Bluetooth clients is done with the
&man.sdpd.8; server.</para>
&man.sdpd.8; server:</para>
<screen>&prompt.root; <userinput>sdpd</userinput></screen>
<para>The local server application that wants to provide Bluetooth
@ -1477,7 +1477,7 @@ Bluetooth Profile Descriptor List:
SDP daemon.</para>
<para>The list of services registered with the local SDP server can be
obtained by issuing SDP browse query via local control channel.</para>
obtained by issuing SDP browse query via local control channel:</para>
<screen>&prompt.root; <userinput>sdpcontrol -l browse</userinput></screen>
@ -1607,7 +1607,7 @@ Success, response: OK, Success (0x20)</screen>
<screen>&prompt.root; <userinput>rfcomm_sppd -a 00:07:E0:00:0B:CA -t /dev/ttyp6</userinput>
rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<para>Once connected, the pseudo tty can be used as serial port.</para>
<para>Once connected, the pseudo tty can be used as serial port:</para>
<screen>&prompt.root; <userinput>cu -l ttyp6</userinput></screen>
@ -1625,7 +1625,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
performed when a new connection is being established, so it is not
possible to ask the remote device if it does support role switching.
There is a HCI option to disable role switching on the local
side.</para>
side:</para>
<screen>&prompt.root; <userinput>hccontrol -n ubt0hci write_node_role_switch 0</userinput></screen>
@ -1635,7 +1635,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<title>Something is going wrong, can I see what exactly is happening?</title>
<para>Yes, you can. Use the <application>hcidump-1.5</application>
third-party package that can be downloaded from
<ulink url="http://www.geocities.com/m_evmenkin/">here</ulink>.
<ulink url="http://www.geocities.com/m_evmenkin/"></ulink>.
The <application>hcidump</application> utility is similar to
&man.tcpdump.1;. It can be used to display the content of the Bluetooth
packets on the terminal and to dump the Bluetooth packets to a