title: Debian: cannot create rfcomm0
body: <p>On Debian Jessie 8.2:
  I'm trying to create the following device: /dev/rfcomm0 in order to connect my arduino via bluetooth module HC-05, but no success.
  Here are the steps I'm following:</p>
  
  <p>1) I guess my HC-05 called FOO is recognised and properly configured, because </p>
  
  <pre><code>hcitool scan
  </code></pre>
  
  <p>reports</p>
  
  <pre><code>98:D3:31:xx:xx:xx   FOO
  </code></pre>
  
  <p>xx are just a mask I use here for privacy.</p>
  
  <p>2) I added the file /etc/bluetooth/rfcomm.conf</p>
  
  <pre><code>rfcomm0 {
  # Automatically bind the device at startup
  bind yes;
  # Bluetooth address of the device
  device 98:D3:31:xx:xx:xx;
  # RFCOMM channel for the connection
  channel 1;
  # Description of the connection
  comment "FOO";
  }
  </code></pre>
  
  <p>3) I restarted bluetooth service</p>
  
  <pre><code>sudo /etc/init.d/bluetooth restart
  </code></pre>
  
  <p>response is:</p>
  
  <pre><code>[ ok ] Restarting bluetooth (via systemctl): bluetooth.service.
  </code></pre>
  
  <p>Nevertheless device rfcomm0 is not created. 
  I'm following the instructions here: </p>
  
  <p><a href="https://myraspberryandme.wordpress.com/2013/11/20/bluetooth-serial-communication-with-hc-05/" rel="nofollow" title="instruction for bluetooth">Bluetooth serial communication with HC-05</a></p>
  
  <p>I did this operation months ago on another Linux system (it was ubuntu) and I can remember
  evertything went well: the port was created. Probably I'm missing some important step!<br>
  Thanks a lot, 
  Valerio</p>
  
  <p>UPDATE:</p>
  
  <p>this command</p>
  
  <pre><code>sdptool records 98:D3:31:xx:xx:xx
  </code></pre>
  
  <p>reports</p>
  
  <pre><code>Service Name: Dev B
  Service RecHandle: 0x10000
  Service Class ID List:
  "Serial Port" (0x1101)
  Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
  Channel: 1
  Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
  </code></pre>
  
  <p>I think this confirms that the channel in rfcomm.conf is 1</p>