Gentoo Linux Bluetooth Guide

-The first part of this guide is to identify qualified and non-qualified = devices -that support the Bluetooth technology. This way, users can purchase Blue= tooth -devices that are known to work. After that, the guide explains how to co= nfigure -the system kernel, identify the Bluetooth devices installed on the syste= m and -detected by the kernel and install the necessary basic Bluetooth tools. +The first part of this guide explains how to configure the system kernel= , +identify the Bluetooth devices installed on the system and detected by t= he +kernel and install the necessary basic Bluetooth tools.

The second part covers how to detect remote devices and how to establish= a connection from or to them by either setting up radio frequency communic= ation -(RFCOMM) or by setting up a personal area network (PAN). +(RFCOMM).

-Qualified and non-qualified devices that support Bluetooth</title= > -<body> - -<impo> -These products might work even though some are not qualified Bluetooth -products. Gentoo does not support them in any way, they might just work. -</impo> - -<p> -A list of the currently supported devices can be found at: <uri -link=3D"http://www.holtmann.org/linux/bluetooth/features.html">Bluetooth= device -features and revision information by Marcel Holtmann</uri>. -</p> - -</body> -</section> -</chapter> - <chapter id=3D"kernel"> <title>Configuring the system

@@ -108,7 +88,7 @@ As the latest Linux stable kernel is 2.6, the configuration will be done= for these series of the kernel. Most Bluetooth devices are connected to a US= B port, so USB will be enabled too. Please refer to the Gentoo Linux USB Guide. +link=3D"/doc/en/usb-guide.xml">Gentoo Linux USB Guide.

=20

@@ -312,14 +292,6 @@
 
=20
 
-If you are using <=3Dbluez-libs-2.x and <=3Dbluez-utils-=
2.x you
-can choose from different pin helpers, depending on what you want to use=
.
-Available pin helpers are: /usr/lib/kdebluetooth/kbluepin
-(net-wireless/kdebluetooth), /usr/bin/bluepin or
-/etc/bluetooth/pin-helper among others.
-
-
-
 Beginning with >=3Dbluez-libs-3.x and >=3Dbluez-utils-3.x,=
 pin helpers
 have been replaced by passkey agents. There are a few different graphica=
l
 passkey agents available to help manage your PIN, such as bluez-gnome=
 and
@@ -523,92 +495,7 @@
=20

-Setting up a Personal Area Network (PAN) - - - -Please note that setting up a Personal Area Network is optional. This se= ction -describes how to set up and connect to a Network Access Point, though se= tting -up a Group Ad-Hoc Network follows a similar way. - - -

-First of all, we need the bnep module loaded. And probably we wan= t it -loaded each time the computer starts. -

- -

-# modprobe bnep
-# echo "bnep" >> /etc/modules.autoload.d/kernel-2.6
-

- -

-We have to start the pand daemon in the host that will provide th= e NAP. -We'll have to specify that we want to provide a NAP service and that thi= s host -will be the master, thus the other hosts that connect to it, the slaves. -Another possible service is GN (Group ad-hoc Network). -

- -

-# pand --listen --role NAP --master --autozap
-

- -

-After doing that, we have a host listening, so the rest of hosts just ha= ve to -connect to that one. -

- -

-# pand --connect 00:0A:0B:0C:0D:0E --service NAP --autozap
-

- -

-If everything went fine, we can now configure the IP addresses of our ho= sts. -

- -

-host0 # ifconfig bnep0 192.168.2.1
-host1 # ifconfig bnep0 192.168.2.2
-
-host0 # ifconfig bnep0
-bnep0     Link encap:Ethernet  HWaddr 00:0A:0B:0C:0D:0E
-          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
-          inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link
-          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000
-          RX bytes:208 (208.0 b)  TX bytes:188 (188.0 b)
-
-host1 # ifconfig bnep0
-bnep0     Link encap:Ethernet  HWaddr 00:01:02:03:04:05
-          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
-          inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link
-          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000
-          RX bytes:208 (208.0 b)  TX bytes:188 (188.0 b)
-

- -

-Finally, we can do a simple test to see that the network is working fine= . -

- -

-host1 # ping 192.168.2.1
-PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
-64 bytes from 192.168.2.1: icmp_seq=3D1 ttl=3D64 time=3D34.0 ms
-64 bytes from 192.168.2.1: icmp_seq=3D2 ttl=3D64 time=3D37.3 ms
-
---- 192.168.2.1 ping statistics ---
-2 packets transmitted, 2 received, 0% packet loss, time 1000ms
-rtt min/avg/max/mdev =3D 34.045/35.690/37.336/1.656 ms
-

- - -

+ =20