| 1 |
nightmorph 09/07/16 23:02:02 |
| 2 |
|
| 3 |
Modified: bluetooth-guide.xml |
| 4 |
Log: |
| 5 |
updated bluetooth guide, emergency fixes, bug 266690. we now no longer have a chapter on setting up a PAN, since nobody knows how the hell to do this. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.16 xml/htdocs/doc/en/bluetooth-guide.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.16&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.16&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?r1=1.15&r2=1.16 |
| 13 |
|
| 14 |
Index: bluetooth-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v |
| 17 |
retrieving revision 1.15 |
| 18 |
retrieving revision 1.16 |
| 19 |
diff -u -r1.15 -r1.16 |
| 20 |
--- bluetooth-guide.xml 22 Oct 2007 05:28:14 -0000 1.15 |
| 21 |
+++ bluetooth-guide.xml 16 Jul 2009 23:02:01 -0000 1.16 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.15 2007/10/22 05:28:14 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.16 2009/07/16 23:02:01 nightmorph Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/bluetooth-guide.xml"> |
| 29 |
<title>Gentoo Linux Bluetooth Guide</title> |
| 30 |
@@ -20,6 +20,9 @@ |
| 31 |
<author title="Editor"> |
| 32 |
<mail link="rane@g.o">Łukasz Damentko</mail> |
| 33 |
</author> |
| 34 |
+<author title="Editor"> |
| 35 |
+ <mail link="nightmorph"/> |
| 36 |
+</author> |
| 37 |
|
| 38 |
<abstract> |
| 39 |
This guide will explain how to successfully install a host Bluetooth device, |
| 40 |
@@ -31,8 +34,8 @@ |
| 41 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 42 |
<license/> |
| 43 |
|
| 44 |
-<version>1.10</version> |
| 45 |
-<date>2007-10-21</date> |
| 46 |
+<version>1.11</version> |
| 47 |
+<date>2009-07-16</date> |
| 48 |
|
| 49 |
<chapter id="introduction"> |
| 50 |
<title>Introduction</title> |
| 51 |
@@ -55,17 +58,15 @@ |
| 52 |
<body> |
| 53 |
|
| 54 |
<p> |
| 55 |
-The first part of this guide is to identify qualified and non-qualified devices |
| 56 |
-that support the Bluetooth technology. This way, users can purchase Bluetooth |
| 57 |
-devices that are known to work. After that, the guide explains how to configure |
| 58 |
-the system kernel, identify the Bluetooth devices installed on the system and |
| 59 |
-detected by the kernel and install the necessary basic Bluetooth tools. |
| 60 |
+The first part of this guide explains how to configure the system kernel, |
| 61 |
+identify the Bluetooth devices installed on the system and detected by the |
| 62 |
+kernel and install the necessary basic Bluetooth tools. |
| 63 |
</p> |
| 64 |
|
| 65 |
<p> |
| 66 |
The second part covers how to detect remote devices and how to establish a |
| 67 |
connection from or to them by either setting up radio frequency communication |
| 68 |
-(RFCOMM) or by setting up a personal area network (PAN). |
| 69 |
+(RFCOMM)<!-- or by setting up a personal area network (PAN)-->. |
| 70 |
</p> |
| 71 |
|
| 72 |
<p> |
| 73 |
@@ -77,27 +78,6 @@ |
| 74 |
</section> |
| 75 |
</chapter> |
| 76 |
|
| 77 |
-<chapter id="devices"> |
| 78 |
-<title>Supported Devices</title> |
| 79 |
-<section> |
| 80 |
-<title>Qualified and non-qualified devices that support Bluetooth</title> |
| 81 |
-<body> |
| 82 |
- |
| 83 |
-<impo> |
| 84 |
-These products might work even though some are not qualified Bluetooth |
| 85 |
-products. Gentoo does not support them in any way, they might just work. |
| 86 |
-</impo> |
| 87 |
- |
| 88 |
-<p> |
| 89 |
-A list of the currently supported devices can be found at: <uri |
| 90 |
-link="http://www.holtmann.org/linux/bluetooth/features.html">Bluetooth device |
| 91 |
-features and revision information by Marcel Holtmann</uri>. |
| 92 |
-</p> |
| 93 |
- |
| 94 |
-</body> |
| 95 |
-</section> |
| 96 |
-</chapter> |
| 97 |
- |
| 98 |
<chapter id="kernel"> |
| 99 |
<title>Configuring the system</title> |
| 100 |
<section> |
| 101 |
@@ -108,7 +88,7 @@ |
| 102 |
As the latest Linux stable kernel is 2.6, the configuration will be done for |
| 103 |
these series of the kernel. Most Bluetooth devices are connected to a USB port, |
| 104 |
so USB will be enabled too. Please refer to the <uri |
| 105 |
-link="/doc/en/usb-guide.xml"> Gentoo Linux USB Guide</uri>. |
| 106 |
+link="/doc/en/usb-guide.xml">Gentoo Linux USB Guide</uri>. |
| 107 |
</p> |
| 108 |
|
| 109 |
<pre caption="Configuration for 2.6 kernels"> |
| 110 |
@@ -312,14 +292,6 @@ |
| 111 |
</impo> |
| 112 |
|
| 113 |
<note> |
| 114 |
-If you are using <c><=bluez-libs-2.x</c> and <c><=bluez-utils-2.x</c> you |
| 115 |
-can choose from different pin helpers, depending on what you want to use. |
| 116 |
-Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c> |
| 117 |
-(net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or |
| 118 |
-<c>/etc/bluetooth/pin-helper</c> among others. |
| 119 |
-</note> |
| 120 |
- |
| 121 |
-<note> |
| 122 |
Beginning with <c>>=bluez-libs-3.x</c> and <c>>=bluez-utils-3.x</c>, pin helpers |
| 123 |
have been replaced by passkey agents. There are a few different graphical |
| 124 |
passkey agents available to help manage your PIN, such as <c>bluez-gnome</c> and |
| 125 |
@@ -523,92 +495,7 @@ |
| 126 |
|
| 127 |
</body> |
| 128 |
</section> |
| 129 |
-<section> |
| 130 |
-<title>Setting up a Personal Area Network (PAN)</title> |
| 131 |
-<body> |
| 132 |
- |
| 133 |
-<note> |
| 134 |
-Please note that setting up a Personal Area Network is optional. This section |
| 135 |
-describes how to set up and connect to a Network Access Point, though setting |
| 136 |
-up a Group Ad-Hoc Network follows a similar way. |
| 137 |
-</note> |
| 138 |
- |
| 139 |
-<p> |
| 140 |
-First of all, we need the <c>bnep</c> module loaded. And probably we want it |
| 141 |
-loaded each time the computer starts. |
| 142 |
-</p> |
| 143 |
- |
| 144 |
-<pre caption="Loading the bnep module"> |
| 145 |
-# <i>modprobe bnep</i> |
| 146 |
-# <i>echo "bnep" >> /etc/modules.autoload.d/kernel-2.6</i> |
| 147 |
-</pre> |
| 148 |
- |
| 149 |
-<p> |
| 150 |
-We have to start the <c>pand</c> daemon in the host that will provide the NAP. |
| 151 |
-We'll have to specify that we want to provide a NAP service and that this host |
| 152 |
-will be the master, thus the other hosts that connect to it, the slaves. |
| 153 |
-Another possible service is GN (Group ad-hoc Network). |
| 154 |
-</p> |
| 155 |
- |
| 156 |
-<pre caption="Running the pand daemon"> |
| 157 |
-# <i>pand --listen --role NAP --master --autozap</i> |
| 158 |
-</pre> |
| 159 |
- |
| 160 |
-<p> |
| 161 |
-After doing that, we have a host listening, so the rest of hosts just have to |
| 162 |
-connect to that one. |
| 163 |
-</p> |
| 164 |
- |
| 165 |
-<pre caption="Connecting to the Network Access Point"> |
| 166 |
-# <i>pand --connect 00:0A:0B:0C:0D:0E --service NAP --autozap</i> |
| 167 |
-</pre> |
| 168 |
- |
| 169 |
-<p> |
| 170 |
-If everything went fine, we can now configure the IP addresses of our hosts. |
| 171 |
-</p> |
| 172 |
- |
| 173 |
-<pre caption="bnep IP address configuration"> |
| 174 |
-host0 #<i> ifconfig bnep0 192.168.2.1</i> |
| 175 |
-host1 #<i> ifconfig bnep0 192.168.2.2</i> |
| 176 |
- |
| 177 |
-host0 #<i> ifconfig bnep0</i> |
| 178 |
-bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E |
| 179 |
- inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 |
| 180 |
- inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link |
| 181 |
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
| 182 |
- RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
| 183 |
- TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 |
| 184 |
- collisions:0 txqueuelen:1000 |
| 185 |
- RX bytes:208 (208.0 b) TX bytes:188 (188.0 b) |
| 186 |
- |
| 187 |
-host1 #<i> ifconfig bnep0</i> |
| 188 |
-bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05 |
| 189 |
- inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 |
| 190 |
- inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link |
| 191 |
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
| 192 |
- RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
| 193 |
- TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 |
| 194 |
- collisions:0 txqueuelen:1000 |
| 195 |
- RX bytes:208 (208.0 b) TX bytes:188 (188.0 b) |
| 196 |
-</pre> |
| 197 |
- |
| 198 |
-<p> |
| 199 |
-Finally, we can do a simple test to see that the network is working fine. |
| 200 |
-</p> |
| 201 |
- |
| 202 |
-<pre caption="IP ping between bnep interfaces"> |
| 203 |
-host1 #<i> ping 192.168.2.1</i> |
| 204 |
-PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. |
| 205 |
-64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms |
| 206 |
-64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms |
| 207 |
- |
| 208 |
---- 192.168.2.1 ping statistics --- |
| 209 |
-2 packets transmitted, 2 received, 0% packet loss, time 1000ms |
| 210 |
-rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms |
| 211 |
-</pre> |
| 212 |
- |
| 213 |
-</body> |
| 214 |
-</section> |
| 215 |
+<!-- Deleting pan chapter, bug 266690, until we know how the hell to do this --> |
| 216 |
</chapter> |
| 217 |
|
| 218 |
<chapter id="apps"> |
Archives