Diff for /wikisrc/guide/bluetooth.mdwn between versions 1.2 and 1.3

version 1.2, 2013/03/21 11:11:20 version 1.3, 2015/06/19 19:18:30
Line 23  service that is required is identified b Line 23  service that is required is identified b
 value.  value.
   
 Service Discovery in the Bluetooth environment is provided for by the  Service Discovery in the Bluetooth environment is provided for by the
 [sdp(3)](http://netbsd.gw.com/cgi-bin/man-cgi?sdp+3+NetBSD-5.0.1+i386) library  [[!template id=man name="sdp" section="3"]] library
 functions and the  functions and the
 [sdpd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?sdpd+8+NetBSD-5.0.1+i386) daemon,  [[!template id=man name="sdpd" section="8"]] daemon,
 which keeps a database of locally registered services and makes the information  which keeps a database of locally registered services and makes the information
 available to remote devices performing queries. The  available to remote devices performing queries. The
 [sdpquery(1)](http://netbsd.gw.com/cgi-bin/man-cgi?sdpquery+1+NetBSD-5.0.1+i386)  [[!template id=man name="sdpquery" section="1"]]
 tool can be used to query local and remote service databases.  tool can be used to query local and remote service databases.
   
 Security on Bluetooth links can be enabled by encryption and authentication  Security on Bluetooth links can be enabled by encryption and authentication
 options to  options to
 [btconfig(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btconfig+8+NetBSD-5.0.1+i386)  [[!template id=man name="btconfig" section="8"]]
 which apply to all baseband links that a controller makes, or encryption and  which apply to all baseband links that a controller makes, or encryption and
 authentication can be enabled for individual RFCOMM and L2CAP links as required.  authentication can be enabled for individual RFCOMM and L2CAP links as required.
 When authentication is requested, a PIN is presented by each side (generally  When authentication is requested, a PIN is presented by each side (generally
Line 41  entered by the operator, some limited in Line 41  entered by the operator, some limited in
 controller uses this PIN to generate a Link Key and reports this to the Host  controller uses this PIN to generate a Link Key and reports this to the Host
 which may be asked to produce it to authenticate subsequent connections. On  which may be asked to produce it to authenticate subsequent connections. On
 NetBSD, the  NetBSD, the
 [bthcid(8)](http://netbsd.gw.com/cgi-bin/man-cgi?bthcid+8+NetBSD-5.0.1+i386)  [[!template id=man name="bthcid" section="8"]]
 daemon is responsible for storing link keys and responding to Link Key Requests,  daemon is responsible for storing link keys and responding to Link Key Requests,
 and also provides an interface to allow unprivileged users to specify a PIN with  and also provides an interface to allow unprivileged users to specify a PIN with
 a PIN client, such as  a PIN client, such as
 [btpin(1)](http://netbsd.gw.com/cgi-bin/man-cgi?btpin+1+NetBSD-5.0.1+i386).  [[!template id=man name="btpin" section="1"]].
   
 ## Supported Hardware  ## Supported Hardware
   
Line 55  host, the NetBSD Bluetooth stack is comp Line 55  host, the NetBSD Bluetooth stack is comp
 requiring an interface driver, with the following drivers available in NetBSD  requiring an interface driver, with the following drivers available in NetBSD
 5.0:  5.0:
   
  * [bcsp(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bcsp+4+NetBSD-5.0.1+i386)   * [[!template id=man name="bcsp" section="4"]]
    provides a     provides a
    [tty(4)](http://netbsd.gw.com/cgi-bin/man-cgi?tty+4+NetBSD-5.0.1+i386) line     [[!template id=man name="tty" section="4"]] line
    discipline to send and receive BlueCore Serial Protocol packets over a serial     discipline to send and receive BlueCore Serial Protocol packets over a serial
    line as described in the *BlueCore Serial Protocol (BCSP)* specification.     line as described in the *BlueCore Serial Protocol (BCSP)* specification.
  * [bt3c(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bt3c+4+NetBSD-5.0.1+i386)   * [[!template id=man name="bt3c" section="4"]]
    provides an interface to the 3Com Bluetooth PC Card, model 3CRWB6096-A.     provides an interface to the 3Com Bluetooth PC Card, model 3CRWB6096-A.
  * [btbc(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btbc+4+NetBSD-5.0.1+i386)   * [[!template id=man name="btbc" section="4"]]
    provides support for the AnyCom BlueCard (LSE041, LSE039, LSE139) PCMCIA     provides support for the AnyCom BlueCard (LSE041, LSE039, LSE139) PCMCIA
    devices.     devices.
  * [btuart(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btuart+4+NetBSD-5.0.1+i386)   * [[!template id=man name="btuart" section="4"]]
    provides a     provides a
    [tty(4)](http://netbsd.gw.com/cgi-bin/man-cgi?tty+4+NetBSD-5.0.1+i386) line     [[!template id=man name="tty" section="4"]] line
    discipline to send and receive Bluetooth packets over a serial line as     discipline to send and receive Bluetooth packets over a serial line as
    described in the *Bluetooth Host Controller Interface [Transport Layer]     described in the *Bluetooth Host Controller Interface [Transport Layer]
    specification, Vol 4 part A*.     specification, Vol 4 part A*.
  * [sbt(4)](http://netbsd.gw.com/cgi-bin/man-cgi?sbt+4+NetBSD-5.0.1+i386)   * [[!template id=man name="sbt" section="4"]]
    provides support for Secure Digital IO Bluetooth adapters.     provides support for Secure Digital IO Bluetooth adapters.
  * [ubt(4)](http://netbsd.gw.com/cgi-bin/man-cgi?ubt+4+NetBSD-5.0.1+i386)   * [[!template id=man name="ubt" section="4"]]
    interfaces to all USB Bluetooth controllers conforming to the *HCI USB     interfaces to all USB Bluetooth controllers conforming to the *HCI USB
    Transport Layer* specification.     Transport Layer* specification.
   
 If support for the NetBSD Bluetooth stack is enabled in the kernel,  If support for the NetBSD Bluetooth stack is enabled in the kernel,
 autoconfiguration messages will show up in the  autoconfiguration messages will show up in the
 [dmesg(8)](http://netbsd.gw.com/cgi-bin/man-cgi/man?dmesg+8+NetBSD-current)  [[!template id=man name="dmesg" section="8"]]
 output, for example:  output, for example:
   
     bt3c0 at pcmcia0 function 0: <3COM, 3CRWB60-A, Bluetooth PC Card>      bt3c0 at pcmcia0 function 0: <3COM, 3CRWB60-A, Bluetooth PC Card>
Line 135  configuration file for any platform that Line 135  configuration file for any platform that
 Some older USB Bluetooth dongles based on the Broadcom BCM2033 chip require  Some older USB Bluetooth dongles based on the Broadcom BCM2033 chip require
 firmware to be loaded before they can function, and these devices will be  firmware to be loaded before they can function, and these devices will be
 attached to  attached to
 [ugen(4)](http://netbsd.gw.com/cgi-bin/man-cgi?ugen+4+NetBSD-5.0.1+i386). Use  [[!template id=man name="ugen" section="4"]]. Use
 the `sysutils/bcmfw` package from the NetBSD Package Collection, to load  the `sysutils/bcmfw` package from the NetBSD Package Collection, to load
 firmware and enable these.  firmware and enable these.
   
Line 151  and either reboot, or execute the follow Line 151  and either reboot, or execute the follow
     # /etc/rc.d/bluetooth start      # /etc/rc.d/bluetooth start
   
 *Note*: Configuration of Bluetooth controllers is done with the  *Note*: Configuration of Bluetooth controllers is done with the
 [btconfig(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btconfig+8+NetBSD-5.0.1+i386)  [[!template id=man name="btconfig" section="8"]]
 program, and the above argument enables only basic functionality, see the manual  program, and the above argument enables only basic functionality, see the manual
 page for other useful options.  page for other useful options.
   
 **Important**:  **Important**:
 [bthcid(8)](http://netbsd.gw.com/cgi-bin/man-cgi?bthcid+8+NetBSD-5.0.1+i386)  [[!template id=man name="bthcid" section="8"]]
 *must* be running in order to make authenticated connections with remote  *must* be running in order to make authenticated connections with remote
 devices, and authentication may be requested by either device.  devices, and authentication may be requested by either device.
   
Line 164  devices, and authentication may be reque Line 164  devices, and authentication may be reque
   
 Support for *Human Interface Devices (HIDs)*, which operate using the USB HID  Support for *Human Interface Devices (HIDs)*, which operate using the USB HID
 protocol over a pair of L2CAP channels is provided by the  protocol over a pair of L2CAP channels is provided by the
 [bthidev(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bthidev+4+NetBSD-5.0.1+i386)  [[!template id=man name="bthidev" section="4"]]
 driver. Currently, keyboards and mice are catered for, and attach to  driver. Currently, keyboards and mice are catered for, and attach to
 [wscons(4)](http://netbsd.gw.com/cgi-bin/man-cgi?wscons+4+NetBSD-5.0.1+i386) as  [[!template id=man name="wscons" section="4"]] as
 normal.  normal.
   
 ### Mice  ### Mice
   
 Bluetooth Mice can be attached to the system with the  Bluetooth Mice can be attached to the system with the
 [btms(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btms+4+NetBSD-5.0.1+i386) driver,  [[!template id=man name="btms" section="4"]] driver,
 using  using
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386).  [[!template id=man name="btdevctl" section="8"]].
   
 First, you must discover the BDADDR of the device. This may be printed on the  First, you must discover the BDADDR of the device. This may be printed on the
 box, but the easiest way is to place the device into discoverable mode and  box, but the easiest way is to place the device into discoverable mode and
Line 198  file, so that you can refer to the mouse Line 198  file, so that you can refer to the mouse
 Now, you can query the mouse, which will likely request authentication before it  Now, you can query the mouse, which will likely request authentication before it
 accepts connections. The fixed PIN should be listed in the documentation, though  accepts connections. The fixed PIN should be listed in the documentation, though
 `0000` is often used. Set the PIN first using the  `0000` is often used. Set the PIN first using the
 [btpin(1)](http://netbsd.gw.com/cgi-bin/man-cgi?btpin+1+NetBSD-5.0.1+i386)  [[!template id=man name="btpin" section="1"]]
 program:  program:
   
     # btpin -d ubt0 -a mouse -p 0000      # btpin -d ubt0 -a mouse -p 0000
Line 242  which should generate some messages on t Line 242  which should generate some messages on t
 and the mouse should work.  and the mouse should work.
   
 The device capabilities are cached by  The device capabilities are cached by
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386),  [[!template id=man name="btdevctl" section="8"]],
 and to reattach the mouse at system startup, place an entry in  and to reattach the mouse at system startup, place an entry in
 `/etc/bluetooth/btdevctl.conf`. The  `/etc/bluetooth/btdevctl.conf`. The
 [bthidev(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bthidev+4+NetBSD-5.0.1+i386)  [[!template id=man name="bthidev" section="4"]]
 driver will attempt to connect once, though mice will usually be sleeping and  driver will attempt to connect once, though mice will usually be sleeping and
 may require a tap on the shoulder to awaken, in which case they should initiate  may require a tap on the shoulder to awaken, in which case they should initiate
 the connection to the host computer.  the connection to the host computer.
Line 253  the connection to the host computer. Line 253  the connection to the host computer.
 ### Keyboards  ### Keyboards
   
 Bluetooth Keyboards can be attached to the system with the  Bluetooth Keyboards can be attached to the system with the
 [btkbd(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btkbd+4+NetBSD-5.0.1+i386)  [[!template id=man name="btkbd" section="4"]]
 driver, using  driver, using
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386).  [[!template id=man name="btdevctl" section="8"]].
   
 First, you must discover the BDADDR of the device. This may be printed on the  First, you must discover the BDADDR of the device. This may be printed on the
 box, but the easiest way is to place the device into discoverable mode and  box, but the easiest way is to place the device into discoverable mode and
Line 279  file, so that you can refer to the keybo Line 279  file, so that you can refer to the keybo
 Now, you can query the keyboard, which will likely request authentication before  Now, you can query the keyboard, which will likely request authentication before
 it accepts connections. The PIN will need to be entered on the keyboard, and we  it accepts connections. The PIN will need to be entered on the keyboard, and we
 can generate a random PIN, using the  can generate a random PIN, using the
 [btpin(1)](http://netbsd.gw.com/cgi-bin/man-cgi?btpin+1+NetBSD-5.0.1+i386)  [[!template id=man name="btpin" section="1"]]
 program.  program.
   
     # btpin -d ubt0 -a keyboard -r -l 8      # btpin -d ubt0 -a keyboard -r -l 8
Line 337  which should generate some messages on t Line 337  which should generate some messages on t
 and the keyboard should work.  and the keyboard should work.
   
 The device capabilities are cached by  The device capabilities are cached by
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386),  [[!template id=man name="btdevctl" section="8"]],
 and to reattach the keyboard at system startup, place an entry in  and to reattach the keyboard at system startup, place an entry in
 `/etc/bluetooth/btdevctl.conf`. The  `/etc/bluetooth/btdevctl.conf`. The
 [bthidev(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bthidev+4+NetBSD-5.0.1+i386)  [[!template id=man name="bthidev" section="4"]]
 driver will attempt to connect once when attached, but if the keyboard is not  driver will attempt to connect once when attached, but if the keyboard is not
 available at that time, you may find that pressing a key will cause it to wake  available at that time, you may find that pressing a key will cause it to wake
 up and initiate a connection to the last paired host.  up and initiate a connection to the last paired host.
Line 348  up and initiate a connection to the last Line 348  up and initiate a connection to the last
 ## Personal Area Networking  ## Personal Area Networking
   
 Personal Area Networking services over Bluetooth are provided by the  Personal Area Networking services over Bluetooth are provided by the
 [btpand(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btpand+8+NetBSD-5.0.1+i386)  [[!template id=man name="btpand" section="8"]]
 daemon which can assume all roles from the PAN profile and connects remote  daemon which can assume all roles from the PAN profile and connects remote
 devices to the system through a  devices to the system through a
 [tap(4)](http://netbsd.gw.com/cgi-bin/man-cgi?tap+4+NetBSD-5.0.1+i386) virtual  [[!template id=man name="tap" section="4"]] virtual
 Ethernet interface.  Ethernet interface.
   
 ### Personal Area Networking User  ### Personal Area Networking User
Line 398  reveals that the NAP service is availabl Line 398  reveals that the NAP service is availabl
 Most likely, the phone will request authentication before it allows connections  Most likely, the phone will request authentication before it allows connections
 to the NAP service, so before you make the first connection you may need to  to the NAP service, so before you make the first connection you may need to
 provide a PIN, which can be randomly generated. Then start  provide a PIN, which can be randomly generated. Then start
 [btpand(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btpand+8+NetBSD-5.0.1+i386):  [[!template id=man name="btpand" section="8"]]:
   
     # btpin -d ubt0 -a phone -r -l 6      # btpin -d ubt0 -a phone -r -l 6
     PIN: 862048      PIN: 862048
Line 412  provide a PIN, which can be randomly gen Line 412  provide a PIN, which can be randomly gen
     Using interface tap0 with addr 00:10:60:e1:50:3d      Using interface tap0 with addr 00:10:60:e1:50:3d
   
 Finally, you will need to configure the  Finally, you will need to configure the
 [tap(4)](http://netbsd.gw.com/cgi-bin/man-cgi?tap+4+NetBSD-5.0.1+i386)  [[!template id=man name="tap" section="4"]]
 interface, but the phone should have a DHCP server so  interface, but the phone should have a DHCP server so
 [dhcpcd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?dhcpcd+8+NetBSD-5.0.1+i386)  [[!template id=man name="dhcpcd" section="8"]]
 will do that for you.  will do that for you.
   
     # dhcpcd tap0      # dhcpcd tap0
Line 428  Serial connections over Bluetooth are pr Line 428  Serial connections over Bluetooth are pr
 provides up to 30 channels multiplexed over a single L2CAP channel. This  provides up to 30 channels multiplexed over a single L2CAP channel. This
 streamed data protocol can be accessed using the BTPROTO\_RFCOMM socket  streamed data protocol can be accessed using the BTPROTO\_RFCOMM socket
 interface, or via the  interface, or via the
 [rfcomm\_sppd(1)](http://netbsd.gw.com/cgi-bin/man-cgi?rfcomm_sppd+1+NetBSD-5.0.1+i386)  [[!template id=man name="rfcomm\_sppd" section="1"]]
 program.  program.
   
 For instance, you can make a serial connection to the *Dial Up Networking (DUN)*  For instance, you can make a serial connection to the *Dial Up Networking (DUN)*
Line 503  disconnect and return to the shell, for  Line 503  disconnect and return to the shell, for 
     ^C      ^C
     rfcomm_sppd[24635]: Completed on stdio      rfcomm_sppd[24635]: Completed on stdio
   
 To have [pppd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?pppd+8+NetBSD-5.0.1+i386)  To have [[!template id=man name="pppd" section="8"]]
 connect to the DUN service of your phone automatically when making outbound  connect to the DUN service of your phone automatically when making outbound
 connections, add the following line to the `/etc/ppp/options` file in place of  connections, add the following line to the `/etc/ppp/options` file in place of
 the normal tty declaration:  the normal tty declaration:
Line 514  the normal tty declaration: Line 514  the normal tty declaration:
   
 Isochronous (SCO) Audio connections may be created on a baseband radio link  Isochronous (SCO) Audio connections may be created on a baseband radio link
 using either the BTPROTO\_SCO socket interface, or the  using either the BTPROTO\_SCO socket interface, or the
 [btsco(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btsco+4+NetBSD-5.0.1+i386) audio  [[!template id=man name="btsco" section="4"]] audio
 device driver. While the specification says that up to three such links can be  device driver. While the specification says that up to three such links can be
 made between devices, the current Bluetooth stack can only handle one with any  made between devices, the current Bluetooth stack can only handle one with any
 dignity.  dignity.
   
 **Important**: When using SCO Audio with USB Bluetooth controllers, you will  **Important**: When using SCO Audio with USB Bluetooth controllers, you will
 need to enable isochronous data, and calculate the MTU that the device will use,  need to enable isochronous data, and calculate the MTU that the device will use,
 see [ubt(4)](http://netbsd.gw.com/cgi-bin/man-cgi?ubt+4+NetBSD-5.0.1+i386) and  see [[!template id=man name="ubt" section="4"]] and
 [btconfig(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btconfig+8+NetBSD-5.0.1+i386).  [[!template id=man name="btconfig" section="8"]].
   
 *Note*: SCO Audio does not work properly with the  *Note*: SCO Audio does not work properly with the
 [bt3c(4)](http://netbsd.gw.com/cgi-bin/man-cgi?bt3c+4+NetBSD-5.0.1+i386) driver,  [[!template id=man name="bt3c" section="4"]] driver,
 use a USB controller for best results.  use a USB controller for best results.
   
 *Note*: SCO Audio will not work with  *Note*: SCO Audio will not work with
 [ehci(4)](http://netbsd.gw.com/cgi-bin/man-cgi?ehci+4+NetBSD-5.0.1+i386) USB  [[!template id=man name="ehci" section="4"]] USB
 controllers, since support for Isochronous data over EHCI is missing in NetBSD.  controllers, since support for Isochronous data over EHCI is missing in NetBSD.
   
 ### SCO Audio Headsets  ### SCO Audio Headsets
   
 Audio connections to Bluetooth Headsets are possible using the  Audio connections to Bluetooth Headsets are possible using the
 [btsco(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btsco+4+NetBSD-5.0.1+i386) audio  [[!template id=man name="btsco" section="4"]] audio
 driver, and the  driver, and the
 [bthset(1)](http://netbsd.gw.com/cgi-bin/man-cgi?bthset+1+NetBSD-5.0.1+i386)  [[!template id=man name="bthset" section="1"]]
 program. First, you need to discover the BDADDR of the headset, and will  program. First, you need to discover the BDADDR of the headset, and will
 probably wish to make an alias in your `/etc/bluetooth/hosts` file for ease of  probably wish to make an alias in your `/etc/bluetooth/hosts` file for ease of
 use. Place the headset into discoverable mode and perform an inquiry with the  use. Place the headset into discoverable mode and perform an inquiry with the
Line 557  appropriate controller: Line 557  appropriate controller:
   
 You will need to pair with the headset the first time you connect, the fixed PIN  You will need to pair with the headset the first time you connect, the fixed PIN
 should be listed in the manual (often, `0000` is used).  should be listed in the manual (often, `0000` is used).
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386)  [[!template id=man name="btdevctl" section="8"]]
 will query the device and attach the  will query the device and attach the
 [btsco(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btsco+4+NetBSD-5.0.1+i386) audio  [[!template id=man name="btsco" section="4"]] audio
 driver.  driver.
   
     # btpin -d ubt0 -a headset -p 0000      # btpin -d ubt0 -a headset -p 0000
Line 578  which should generate some messages on t Line 578  which should generate some messages on t
   
 In order to use the audio device, you will need to open a control connection  In order to use the audio device, you will need to open a control connection
 with  with
 [bthset(1)](http://netbsd.gw.com/cgi-bin/man-cgi?bthset+1+NetBSD-5.0.1+i386)  [[!template id=man name="bthset" section="1"]]
 which conveys volume information to the mixer device.  which conveys volume information to the mixer device.
   
     # bthset -m /dev/mixer1 -v      # bthset -m /dev/mixer1 -v
Line 591  which conveys volume information to the  Line 591  which conveys volume information to the 
   
 and you should now be able to transfer 8khz samples to and from `/dev/audio1`  and you should now be able to transfer 8khz samples to and from `/dev/audio1`
 using any program that supports audio, such as  using any program that supports audio, such as
 [audioplay(1)](http://netbsd.gw.com/cgi-bin/man-cgi?audioplay+1+NetBSD-5.0.1+i386)  [[!template id=man name="audioplay" section="1"]]
 or  or
 [audiorecord(1)](http://netbsd.gw.com/cgi-bin/man-cgi?audiorecord+1+NetBSD-5.0.1+i386).  [[!template id=man name="audiorecord" section="1"]].
 Adjusting the mixer values should work when playing though you may find that  Adjusting the mixer values should work when playing though you may find that
 when opening a connection, the headset will reset the volume to the last known  when opening a connection, the headset will reset the volume to the last known
 settings.  settings.
Line 607  settings. Line 607  settings.
             < IN THE HEADSET >              < IN THE HEADSET >
   
 The device capabilities are cached by  The device capabilities are cached by
 [btdevctl(8)](http://netbsd.gw.com/cgi-bin/man-cgi?btdevctl+8+NetBSD-5.0.1+i386),  [[!template id=man name="btdevctl" section="8"]],
 and to reattach the  and to reattach the
 [btsco(4)](http://netbsd.gw.com/cgi-bin/man-cgi?btsco+4+NetBSD-5.0.1+i386)  [[!template id=man name="btsco" section="4"]]
 driver at system startup, add an entry to `/etc/bluetooth/btdevctl.conf`.  driver at system startup, add an entry to `/etc/bluetooth/btdevctl.conf`.
   
 ### SCO Audio Handsfree  ### SCO Audio Handsfree
Line 662  Handsfree profile: Line 662  Handsfree profile:
 and you will be able to use the bthfp program to access the Handsfree profile.  and you will be able to use the bthfp program to access the Handsfree profile.
 The first time you connect, you may need to use a PIN to pair with the phone,  The first time you connect, you may need to use a PIN to pair with the phone,
 which can be generated randomly by  which can be generated randomly by
 [btpin(1)](http://netbsd.gw.com/cgi-bin/man-cgi?btpin+1+NetBSD-5.0.1+i386):  [[!template id=man name="btpin" section="1"]]:
   
     # btpin -d ubt0 -a phone -r -l 6      # btpin -d ubt0 -a phone -r -l 6
     PIN: 349163      PIN: 349163

Removed from v.1.2  
changed lines
  Added in v.1.3


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb