Você já leu este ? Aqui está uma pasta da seção relevante (eu acho):
Here's an example:
To connect a PANU node (00:37:5C:67:D3:01) with a GN (00:37:5C:67:D3:02), BlueZ must be operational on both sides. The GN must be able to run as Bluetooth master (see above).
Enter # modprobe bnep
on both nodes. Then enter # pand --listen --role GN
on the GN side.
After that, you you can connect from the PANU side: # pand --connect 00:37:5C:67:D3:02
In case of problems, the system log files under /var/log/ (i.e. 'messages' and 'warn') may give you further information about the cause of failure.
Note that it is a good idea to start 'pand' as server on the GN (or NAP, respectively) rather than the PANU, since then you have a consistent access scheme from any possible PANU. When you do so, 'pand' permanently listens for connection attempts from other nodes, thus becomes resident. In case you have only one PANU, however, you may also swap roles and start 'pand' as server (i.e. using the '--listen' parameter) on the PANU side, and connect from the GN (or NAP) side.
EDIT : Acabou de encontrar Blueman , um gerenciador gráfico bluetooth para redes discadas, áudio bluetooth, emparelhamento e assim por diante.