summaryrefslogtreecommitdiff
path: root/static/freebsd/man5/bluetooth.device.conf.5 3.html
diff options
context:
space:
mode:
Diffstat (limited to 'static/freebsd/man5/bluetooth.device.conf.5 3.html')
-rw-r--r--static/freebsd/man5/bluetooth.device.conf.5 3.html133
1 files changed, 133 insertions, 0 deletions
diff --git a/static/freebsd/man5/bluetooth.device.conf.5 3.html b/static/freebsd/man5/bluetooth.device.conf.5 3.html
new file mode 100644
index 00000000..d0e3544c
--- /dev/null
+++ b/static/freebsd/man5/bluetooth.device.conf.5 3.html
@@ -0,0 +1,133 @@
+<table class="head">
+ <tr>
+ <td class="head-ltitle">BLUETOOTH.DEVICE.CONF(5)</td>
+ <td class="head-vol">File Formats Manual</td>
+ <td class="head-rtitle">BLUETOOTH.DEVICE.CONF(5)</td>
+ </tr>
+</table>
+<div class="manual-text">
+<section class="Sh">
+<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
+<p class="Pp"><code class="Nm">bluetooth.device.conf</code> &#x2014;
+ <span class="Nd">Bluetooth device configuration file</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
+<p class="Pp">Bluetooth device configuration framework provides ability to
+ adjust certain Bluetooth device parameters on per-device basis.</p>
+<p class="Pp">Bluetooth device configuration files are plain text files that
+ should conform to basic <a class="Xr">sh(1)</a> syntax. Even though
+ Bluetooth device are not exactly shell scripts, they are parsed and passed
+ through shell <code class="Ic">eval</code> command. This makes it possible
+ to use various shell tricks in the Bluetooth device configuration files.</p>
+<p class="Pp">The <span class="Pa">/etc/rc.d/bluetooth</span> script is used to
+ start and stop Bluetooth devices. This script is not executed by default
+ when system boots. It is called by <a class="Xr">devd(8)</a> in response to
+ Bluetooth device arrival and departure events. It is possible to execute
+ this script by hand if required. The script accepts Bluetooth device driver
+ name as an extra parameter.</p>
+<p class="Pp">The system wide Bluetooth device configuration file is called
+ <span class="Pa">/etc/defaults/bluetooth.device.conf</span>. Configuration
+ parameters set in the system wide Bluetooth device configuration file apply
+ to every Bluetooth device connected to the system.</p>
+<p class="Pp">Configuration parameters overrides for the specific Bluetooth
+ device should be placed in the
+ <span class="Pa">/etc/bluetooth/</span><var class="Ar">DEVICE_DRIVER_NAME</var><span class="Pa">.conf</span>
+ file. Where <var class="Ar">DEVICE_DRIVER_NAME</var> is the device driver
+ name of the Bluetooth device.</p>
+<p class="Pp">The following list provides a name and short description for each
+ variable that can be set in a Bluetooth device configuration file.</p>
+<dl class="Bl-tag">
+ <dt id="authentication_enable"><var class="Va">authentication_enable</var></dt>
+ <dd>(<var class="Vt">bool</var>) The
+ <var class="Va">authentication_enable</var> parameter controls if the
+ device requires to authenticate the remote device at connection setup. If
+ set to &#x201C;<code class="Li">YES</code>&#x201D;, the device will try to
+ authenticate the other device at connection setup. Bluetooth
+ authentication requests are handled by <a class="Xr">hcsecd(8)</a>
+ daemon.</dd>
+ <dt id="class"><var class="Va">class</var></dt>
+ <dd>(<var class="Vt">str</var>) The <var class="Va">class</var> parameter is
+ used to indicate the capabilities of the device to other devices. For more
+ details see &#x201C;Assigned Numbers - Bluetooth Baseband&#x201D;
+ document.</dd>
+ <dt id="connectable"><var class="Va">connectable</var></dt>
+ <dd>(<var class="Vt">bool</var>) The <var class="Va">connectable</var>
+ parameter controls whether or not the device should periodically scan for
+ page attempts from other devices. If set to
+ &#x201C;<code class="Li">YES</code>&#x201D;, the device will periodically
+ scan for page attempts from other devices.</dd>
+ <dt id="discoverable"><var class="Va">discoverable</var></dt>
+ <dd>(<var class="Vt">bool</var>) The <var class="Va">discoverable</var>
+ parameter controls whether or not the device should periodically scan for
+ inquiry requests from other devices. If set to
+ &#x201C;<code class="Li">YES</code>&#x201D;, the device will periodically
+ scan for inquiry requests from other devices.</dd>
+ <dt id="encryption_mode"><var class="Va">encryption_mode</var></dt>
+ <dd>(<var class="Vt">str</var>) The <var class="Va">encryption_mode</var>
+ parameter controls if the device requires encryption to the remote device
+ at connection setup. At connection setup, only the devices with the
+ <var class="Va">authentication_enable</var> parameter enabled and
+ <var class="Va">encryption_mode</var> parameter enabled will try to
+ encrypt the connection to the other device. Possible values are
+ &#x201C;<code class="Li">NONE</code>&#x201D; encryption disabled,
+ &#x201C;<code class="Li">P2P</code>&#x201D; encryption for only
+ point-to-point packets, or &#x201C;<code class="Li">ALL</code>&#x201D;
+ encryption for both point-to-point and broadcast packets.</dd>
+ <dt id="hci_debug_level"><var class="Va">hci_debug_level</var></dt>
+ <dd>(<var class="Vt">int</var>) HCI node debug level. Higher values mean more
+ verbose output.</dd>
+ <dt id="l2cap_debug_level"><var class="Va">l2cap_debug_level</var></dt>
+ <dd>(<var class="Vt">int</var>) L2CAP node debug level. Higher values mean
+ more verbose output.</dd>
+ <dt id="local_name"><var class="Va">local_name</var></dt>
+ <dd>(<var class="Vt">str</var>) The <var class="Va">local_name</var> parameter
+ provides the ability to modify the user friendly name for the device.</dd>
+ <dt id="role_switch"><var class="Va">role_switch</var></dt>
+ <dd>(<var class="Vt">bool</var>) The <var class="Va">role_switch</var>
+ parameter controls whether the local device should perform role switch. By
+ default, if role switch is supported, the local device will try to perform
+ role switch and become Master on incoming connection. Some devices do not
+ support role switch and thus incoming connections from such devices will
+ fail. If <var class="Va">role switch</var> is disabled then accepting
+ device will remain Slave.</dd>
+</dl>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
+<dl class="Bl-tag Bl-compact">
+ <dt><span class="Pa">/etc/defaults/bluetooth.device.conf</span></dt>
+ <dd style="width: auto;">&#x00A0;</dd>
+ <dt><span class="Pa">/etc/rc.d/bluetooth</span></dt>
+ <dd style="width: auto;">&#x00A0;</dd>
+</dl>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1>
+<p class="Pp">The <span class="Pa">/etc/bluetooth/ubt0.conf</span> file should
+ be used to specify configuration parameters overrides for the first USB
+ Bluetooth device (device driver name is <code class="Li">ubt0</code>).</p>
+<p class="Pp">The <span class="Pa">/etc/bluetooth/ubt1.conf</span> file should
+ be used to specify configuration parameters overrides for the second USB
+ Bluetooth device.</p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
+ ALSO</a></h1>
+<p class="Pp"><a class="Xr">ng_hci(4)</a>, <a class="Xr">ng_l2cap(4)</a>,
+ <a class="Xr">ng_ubt(4)</a>, <a class="Xr">devd(8)</a>,
+ <a class="Xr">hccontrol(8)</a>, <a class="Xr">hcsecd(8)</a>,
+ <a class="Xr">l2control(8)</a></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
+<p class="Pp"><span class="An">Maksim Yevmenkin</span>
+ &lt;<a class="Mt" href="mailto:m_evmenkin@yahoo.com">m_evmenkin@yahoo.com</a>&gt;</p>
+</section>
+</div>
+<table class="foot">
+ <tr>
+ <td class="foot-date">September 29, 2021</td>
+ <td class="foot-os">FreeBSD 15.0</td>
+ </tr>
+</table>