system/NetworkManager
system/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager synced 2024-07-21 18:24:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

man: add examples how to configure bluetooth devices to man nmcli-examples.

Browse source
This commit is contained in:
Thomas Haller 2019-08-30 11:02:00 +02:00
parent d6df0339ff
commit a5bc4cb785
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
man/nmcli-examples.xml
View file

@ -587,6 +587,28 @@ Connection 'ethernet-4' (de89cdeb-a3e1-4d53-8fa0-c22546c775f4) successfully
</para>
</example>
<example><title>Bluetooth connection profiles</title>
<para>NetworkManger supports both connecting to NAP and DUN devices as a client. It also
supports sharing the network via a NAP server.
</para>
<para>For NAP client connections, NetworkManager automatically creates a suitable in-memory profile
for paired devices if none is available. You may use that generated profile directly, but you may also modify
and persist it, which will prevent to automatically re-create it. You may also create a profile from scratch.
For example, the following uses DHCP and IPv6 autoconf for address configuration:
</para>
<screen><prompt>$ </prompt><userinput>nmcli connection add type bluetooth con-name "Profile for My Bluetooth Device (NAP)" autoconnect no bluetooth.type panu bluetooth.bdaddr "$BDADDR"</userinput></screen>
<para>For DUN connections, the user needs to configure modem settings and hence no profile
gets created automatically. The modem settings depend on your device and you either need
a "gsm" or a "csma" section. For example,
</para>
<screen><prompt>$ </prompt><userinput>nmcli connection add type bluetooth con-name "Profile for My Bluetooth Device (DUN)" autoconnect no bluetooth.type dun bluetooth.bdaddr "$BDADDR" gsm.apn apn.com</userinput></screen>
<para>Finally, you can create a bluetooth hotspot. BlueZ implements those as a bridge device,
so such profiles also have a bridge section. Also, you probably want to set IP methods as "shared",
so that clients get automatic IP addressing. Note that the "shared" IPv4 method requires dnsmasq to be available.
</para>
<screen><prompt>$ </prompt><userinput>nmcli connection add type bluetooth con-name "My Bluetooth Hotspot" autoconnect no ifname btnap0 bluetooth.type nap ipv4.method shared ipv6.method shared</userinput></screen>
</example>
</refsect1>
<refsect1>