Imported Upstream version 1.4.4 upstream/1.4.4

14 files changed, 234 insertions, 178 deletions

diff --git a/man/NetworkManager.8 b/man/NetworkManager.8
index 1a19daf4..e35bc1cb 100644
--- a/man/NetworkManager.8
+++ b/man/NetworkManager.8
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: NetworkManager
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Network management daemons
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.4\&.2" "Network management daemons"
+.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.4\&.4" "Network management daemons"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -37,7 +37,9 @@ NetworkManager \- network management daemon
 The NetworkManager daemon attempts to make networking configuration and operation as painless and automatic as possible by managing the primary network connection and other network interfaces, like Ethernet, WiFi, and Mobile Broadband devices\&. NetworkManager will connect any network device when a connection for that device becomes available, unless that behavior is disabled\&. Information about networking is exported via a D\-Bus interface to any interested application, providing a rich API with which to inspect and control network settings and operation\&.
 .SH "DISPATCHER SCRIPTS"
 .PP
-NetworkManager will execute scripts in the /etc/NetworkManager/dispatcher\&.d directory or subdirectories in alphabetical order in response to network events\&. Each script should be a regular executable file owned by root\&. Furthermore, it must not be writable by group or other, and not setuid\&.
+NetworkManager will execute scripts in the
+/etc/NetworkManager/dispatcher\&.d
+directory or subdirectories in alphabetical order in response to network events\&. Each script should be a regular executable file owned by root\&. Furthermore, it must not be writable by group or other, and not setuid\&.
 .PP
 Each script receives two arguments, the first being the interface name of the device an operation just happened on, and second the action\&. For device actions, the interface is the name of the kernel interface suitable for IP configuration\&. Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable\&. For the
 \fIhostname\fR
@@ -49,7 +51,9 @@ The actions are:
 .PP
 \fIpre\-up\fR
 .RS 4
-The interface is connected to the network but is not yet fully activated\&. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher\&.d/pre\-up\&.d directory, and NetworkManager will wait for script execution to complete before indicating to applications that the interface is fully activated\&.
+The interface is connected to the network but is not yet fully activated\&. Scripts acting on this event must be placed or symlinked into the
+/etc/NetworkManager/dispatcher\&.d/pre\-up\&.d
+directory, and NetworkManager will wait for script execution to complete before indicating to applications that the interface is fully activated\&.
 .RE
 .PP
 \fIup\fR
@@ -59,7 +63,9 @@ The interface has been activated\&.
 .PP
 \fIpre\-down\fR
 .RS 4
-The interface will be deactivated but has not yet been disconnected from the network\&. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher\&.d/pre\-down\&.d directory, and NetworkManager will wait for script execution to complete before disconnecting the interface from its network\&. Note that this event is not emitted for forced disconnections, like when carrier is lost or a wireless signal fades\&. It is only emitted when there is an opportunity to cleanly handle a network disconnection event\&.
+The interface will be deactivated but has not yet been disconnected from the network\&. Scripts acting on this event must be placed or symlinked into the
+/etc/NetworkManager/dispatcher\&.d/pre\-down\&.d
+directory, and NetworkManager will wait for script execution to complete before disconnecting the interface from its network\&. Note that this event is not emitted for forced disconnections, like when carrier is lost or a wireless signal fades\&. It is only emitted when there is an opportunity to cleanly handle a network disconnection event\&.
 .RE
 .PP
 \fIdown\fR
@@ -69,7 +75,9 @@ The interface has been deactivated\&.
 .PP
 \fIvpn\-pre\-up\fR
 .RS 4
-The VPN is connected to the network but is not yet fully activated\&. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher\&.d/pre\-up\&.d directory, and NetworkManager will wait for script execution to complete before indicating to applications that the VPN is fully activated\&.
+The VPN is connected to the network but is not yet fully activated\&. Scripts acting on this event must be placed or symlinked into the
+/etc/NetworkManager/dispatcher\&.d/pre\-up\&.d
+directory, and NetworkManager will wait for script execution to complete before indicating to applications that the VPN is fully activated\&.
 .RE
 .PP
 \fIvpn\-up\fR
@@ -79,7 +87,9 @@ A VPN connection has been activated\&.
 .PP
 \fIvpn\-pre\-down\fR
 .RS 4
-The VPN will be deactivated but has not yet been disconnected from the network\&. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher\&.d/pre\-down\&.d directory, and NetworkManager will wait for script execution to complete before disconnecting the VPN from its network\&. Note that this event is not emitted for forced disconnections, like when the VPN terminates unexpectedly or general connectivity is lost\&. It is only emitted when there is an opportunity to cleanly handle a VPN disconnection event\&.
+The VPN will be deactivated but has not yet been disconnected from the network\&. Scripts acting on this event must be placed or symlinked into the
+/etc/NetworkManager/dispatcher\&.d/pre\-down\&.d
+directory, and NetworkManager will wait for script execution to complete before disconnecting the VPN from its network\&. Note that this event is not emitted for forced disconnections, like when the VPN terminates unexpectedly or general connectivity is lost\&. It is only emitted when there is an opportunity to cleanly handle a VPN disconnection event\&.
 .RE
 .PP
 \fIvpn\-down\fR
@@ -197,7 +207,9 @@ The network connectivity state, which can take the values defined by the NMConne
 .PP
 In case of VPN, VPN_IP_IFACE is set, and IP4_*, IP6_* variables with VPN prefix are exported too, like VPN_IP4_ADDRESS_0, VPN_IP4_NUM_ADDRESSES\&.
 .PP
-Dispatcher scripts are run one at a time, but asynchronously from the main NetworkManager process, and will be killed if they run for too long\&. If your script might take arbitrarily long to complete, you should spawn a child process and have the parent return immediately\&. Scripts that are symbolic links pointing inside the /etc/NetworkManager/dispatcher\&.d/no\-wait\&.d/ directory are run immediately, without waiting for the termination of previous scripts, and in parallel\&. Also beware that once a script is queued, it will always be run, even if a later event renders it obsolete\&. (Eg, if an interface goes up, and then back down again quickly, it is possible that one or more "up" scripts will be run after the interface has gone down\&.)
+Dispatcher scripts are run one at a time, but asynchronously from the main NetworkManager process, and will be killed if they run for too long\&. If your script might take arbitrarily long to complete, you should spawn a child process and have the parent return immediately\&. Scripts that are symbolic links pointing inside the
+/etc/NetworkManager/dispatcher\&.d/no\-wait\&.d/
+directory are run immediately, without waiting for the termination of previous scripts, and in parallel\&. Also beware that once a script is queued, it will always be run, even if a later event renders it obsolete\&. (Eg, if an interface goes up, and then back down again quickly, it is possible that one or more "up" scripts will be run after the interface has gone down\&.)
 .SH "OPTIONS"
 .PP
 The following options are understood:
@@ -229,12 +241,16 @@ Specify location of a PID file\&. The PID file is used for storing PID of the ru
 .PP
 \fB\-\-state\-file\fR
 .RS 4
-Specify file for storing state of the NetworkManager persistently\&. If not specified, the default value of /var/lib/NetworkManager/NetworkManager\&.state is used\&.
+Specify file for storing state of the NetworkManager persistently\&. If not specified, the default value of
+/var/lib/NetworkManager/NetworkManager\&.state
+is used\&.
 .RE
 .PP
 \fB\-\-config\fR
 .RS 4
-Specify configuration file to set up various settings for NetworkManager\&. If not specified, the default value of /etc/NetworkManager/NetworkManager\&.conf is used with a fallback to the older \*(Aqnm\-system\-settings\&.conf\*(Aq if located in the same directory\&. See
+Specify configuration file to set up various settings for NetworkManager\&. If not specified, the default value of
+/etc/NetworkManager/NetworkManager\&.conf
+is used with a fallback to the older \*(Aqnm\-system\-settings\&.conf\*(Aq if located in the same directory\&. See
 \fBNetworkManager.conf\fR(5)
 for more information on configuration file\&.
 .RE
@@ -286,7 +302,8 @@ NetworkManager process handles the following signals:
 .PP
 \fISIGHUP\fR
 .RS 4
-The signal causes a reload of NetworkManager\*(Aqs configuration\&. Note that not all configuration parameters can be changed at runtime and therefore some changes may be applied only after the next restart of the daemon\&. A SIGHUP also involves further reloading actions, like doing a DNS update and restarting the DNS plugin\&. The latter can be useful for example when using the dnsmasq plugin and changing its configuration in /etc/NetworkManager/dnsmasq\&.d\&. However, it also means this will shortly interrupt name resolution\&. In the future, there may be further actions added\&. A SIGHUP means to update NetworkManager configuration and reload everything that is supported\&. Note that this does not reload connections from disk\&. For that there is a D\-Bus API and nmcli\*(Aqs reload action
+The signal causes a reload of NetworkManager\*(Aqs configuration\&. Note that not all configuration parameters can be changed at runtime and therefore some changes may be applied only after the next restart of the daemon\&. A SIGHUP also involves further reloading actions, like doing a DNS update and restarting the DNS plugin\&. The latter can be useful for example when using the dnsmasq plugin and changing its configuration in
+/etc/NetworkManager/dnsmasq\&.d\&. However, it also means this will shortly interrupt name resolution\&. In the future, there may be further actions added\&. A SIGHUP means to update NetworkManager configuration and reload everything that is supported\&. Note that this does not reload connections from disk\&. For that there is a D\-Bus API and nmcli\*(Aqs reload action
 .RE
 .PP
 \fISIGUSR1\fR
@@ -311,8 +328,13 @@ and
 to enable debug logging inside NetworkManager itself\&.
 .PP
 \fBNM_PPP_DEBUG\fR: When set to anything, causes NetworkManager to turn on PPP debugging in pppd, which logs all PPP and PPTP frames and client/server exchanges\&.
+.SH "BUGS"
+.PP
+Please report any bugs you find in NetworkManager at the
+\m[blue]\fBNetworkManager bug tracker\fR\m[]\&\s-2\u[1]\d\s+2\&.
 .SH "SEE ALSO"
 .PP
+\m[blue]\fBNetworkManager home page\fR\m[]\&\s-2\u[2]\d\s+2,
 \fBNetworkManager.conf\fR(5),
 \fBnmcli\fR(1),
 \fBnmcli-examples\fR(7),
@@ -321,3 +343,14 @@ to enable debug logging inside NetworkManager itself\&.
 \fBnm-applet\fR(1),
 \fBnm-connection-editor\fR(1),
 \fBudev\fR(7)
+.SH "NOTES"
+.IP " 1." 4
+NetworkManager bug tracker
+.RS 4
+\%https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
+.RE
+.IP " 2." 4
+NetworkManager home page
+.RS 4
+\%https://wiki.gnome.org/Projects/NetworkManager
+.RE
diff --git a/man/NetworkManager.conf.5 b/man/NetworkManager.conf.5
index fed80761..a020d177 100644
--- a/man/NetworkManager.conf.5
+++ b/man/NetworkManager.conf.5
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: NetworkManager.conf
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NETWORKMANAGER\&.CON" "5" "" "NetworkManager 1\&.4\&.2" "Configuration"
+.TH "NETWORKMANAGER\&.CON" "5" "" "NetworkManager 1\&.4\&.4" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -208,7 +208,9 @@ dnsmasq: NetworkManager will run dnsmasq as a local caching nameserver, using a
 resolv\&.conf
 to point to the local nameserver\&.
 .sp
-unbound: NetworkManager will talk to unbound and dnssec\-triggerd, providing a "split DNS" configuration with DNSSEC support\&. The /etc/resolv\&.conf will be managed by dnssec\-trigger daemon\&.
+unbound: NetworkManager will talk to unbound and dnssec\-triggerd, providing a "split DNS" configuration with DNSSEC support\&. The
+/etc/resolv\&.conf
+will be managed by dnssec\-trigger daemon\&.
 .sp
 none: NetworkManager will not modify resolv\&.conf\&. This implies
 rc\-manager\ \&unmanaged
@@ -259,12 +261,14 @@ This section contains keyfile\-plugin\-specific options, and is normally only us
 .PP
 \fIhostname\fR
 .RS 4
-This key is deprecated and has no effect since the hostname is now stored in /etc/hostname or other system configuration files according to build options\&.
+This key is deprecated and has no effect since the hostname is now stored in
+/etc/hostname
+or other system configuration files according to build options\&.
 .RE
 .PP
 \fIpath\fR
 .RS 4
-The location where keyfiles are read and stored\&. This defaults to "${prefix}/etc/NetworkManager/conf\&.d"\&.
+The location where keyfiles are read and stored\&. This defaults to "/etc/NetworkManager/conf\&.d"\&.
 .RE
 .PP
 \fIunmanaged\-devices\fR
@@ -875,7 +879,8 @@ enable=nm\-version\-min:1\&.3,nm\-version\-min:1\&.2\&.6,nm\-version\-min:1\&.0\
 .RS 4
 The
 keyfile
-plugin is the generic plugin that supports all the connection types and capabilities that NetworkManager has\&. It writes files out in an \&.ini\-style format in /etc/NetworkManager/system\-connections\&.
+plugin is the generic plugin that supports all the connection types and capabilities that NetworkManager has\&. It writes files out in an \&.ini\-style format in
+/etc/NetworkManager/system\-connections\&.
 .sp
 The stored connection file may contain passwords and private keys, so it will be made readable only to root, and the plugin will ignore files that are readable or writable by any user or group other than root\&.
 .sp
@@ -913,7 +918,8 @@ plugin instead\&.
 .PP
 \fIibft\fR, \fIno\-ibft\fR
 .RS 4
-This plugin allows to read iBFT configuration (iSCSI Boot Firmware Table)\&. The configuration is read using /sbin/iscsiadm\&. Users are expected to configure iBFT connections via the firmware interfaces\&. If ibft support is available, it is automatically enabled after
+This plugin allows to read iBFT configuration (iSCSI Boot Firmware Table)\&. The configuration is read using
+/sbin/iscsiadm\&. Users are expected to configure iBFT connections via the firmware interfaces\&. If ibft support is available, it is automatically enabled after
 ifcfg\-rh\&. This can be disabled by
 no\-ibft\&. You can also explicitly specify
 ibft
@@ -921,7 +927,9 @@ to load the plugin without
 ifcfg\-rh
 or to change the plugin order\&.
 .sp
-Note that ibft plugin uses /sbin/iscsiadm and thus requires CAP_SYS_ADMIN capability\&.
+Note that ibft plugin uses
+/sbin/iscsiadm
+and thus requires CAP_SYS_ADMIN capability\&.
 .RE
 .SH "APPENDIX"
 .SS "Device List Format"
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml
index acb75c2e..6295b821 100644
--- a/man/NetworkManager.conf.xml
+++ b/man/NetworkManager.conf.xml
@@ -286,7 +286,7 @@ no-auto-default=*
         nameserver.</para>
         <para><literal>unbound</literal>: NetworkManager will talk
         to unbound and dnssec-triggerd, providing a "split DNS"
-        configuration with DNSSEC support. The /etc/resolv.conf
+        configuration with DNSSEC support. The <filename>/etc/resolv.conf</filename>
         will be managed by dnssec-trigger daemon.</para>
         <para><literal>none</literal>: NetworkManager will not
         modify resolv.conf. This implies
@@ -358,8 +358,8 @@ no-auto-default=*
         <varlistentry>
           <term><varname>hostname</varname></term>
           <listitem><para>This key is deprecated and has no effect
-          since the hostname is now stored in /etc/hostname or other
-          system configuration files according to build options.
+          since the hostname is now stored in <filename>/etc/hostname</filename>
+          or other system configuration files according to build options.
           </para></listitem>
         </varlistentry>
         <varlistentry>
@@ -986,7 +986,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
             plugin that supports all the connection types and
             capabilities that NetworkManager has. It writes files out
             in an .ini-style format in
-            /etc/NetworkManager/system-connections.
+            <filename>/etc/NetworkManager/system-connections</filename>.
           </para>
           <para>
             The stored connection file may contain passwords and
@@ -1051,15 +1051,16 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
         <listitem>
           <para>
             This plugin allows to read iBFT configuration (iSCSI Boot Firmware Table).
-            The configuration is read using /sbin/iscsiadm. Users are expected to
-            configure iBFT connections via the firmware interfaces.
+            The configuration is read using <filename>/sbin/iscsiadm</filename>. Users are
+            expected to configure iBFT connections via the firmware interfaces.
             If ibft support is available, it is automatically enabled after
             <literal>ifcfg-rh</literal>. This can be disabled by <literal>no-ibft</literal>.
             You can also explicitly specify <literal>ibft</literal> to load the
             plugin without <literal>ifcfg-rh</literal> or to change the plugin order.
           </para>
           <para>
-            Note that ibft plugin uses /sbin/iscsiadm and thus requires CAP_SYS_ADMIN capability.
+            Note that ibft plugin uses <filename>/sbin/iscsiadm</filename> and thus requires
+            CAP_SYS_ADMIN capability.
           </para>
         </listitem>
       </varlistentry>
diff --git a/man/NetworkManager.xml b/man/NetworkManager.xml
index 2cb458a2..60dbe7d7 100644
--- a/man/NetworkManager.xml
+++ b/man/NetworkManager.xml
@@ -69,7 +69,8 @@
     <title>Dispatcher scripts</title>
     <para>
       NetworkManager will execute scripts in the
-      /etc/NetworkManager/dispatcher.d directory or subdirectories in
+      <filename>/etc/NetworkManager/dispatcher.d</filename>
+      directory or subdirectories in
       alphabetical order in response to network events.  Each script should
       be a regular executable file owned by root.  Furthermore, it must not be
       writable by group or other, and not setuid.
@@ -88,8 +89,8 @@
         <term><varname>pre-up</varname></term>
         <listitem><para>The interface is connected to the network but is not
         yet fully activated.  Scripts acting on this event must be placed or
-        symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory,
-        and NetworkManager will wait for script execution to complete before
+        symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-up.d</filename>
+        directory, and NetworkManager will wait for script execution to complete before
         indicating to applications that the interface is fully activated.
         </para></listitem>
       </varlistentry>
@@ -101,7 +102,7 @@
         <term><varname>pre-down</varname></term>
         <listitem><para>The interface will be deactivated but has not yet been
         disconnected from the network.  Scripts acting on this event must be
-        placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d
+        placed or symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-down.d</filename>
         directory, and NetworkManager will wait for script execution to complete
         before disconnecting the interface from its network.  Note that this
         event is not emitted for forced disconnections, like when carrier is
@@ -119,8 +120,8 @@
         <term><varname>vpn-pre-up</varname></term>
         <listitem><para>The VPN is connected to the network but is not yet
         fully activated.  Scripts acting on this event must be placed or
-        symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory,
-        and NetworkManager will wait for script execution to complete before
+        symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-up.d</filename>
+        directory, and NetworkManager will wait for script execution to complete before
         indicating to applications that the VPN is fully activated.
         </para></listitem>
       </varlistentry>
@@ -134,7 +135,7 @@
         <term><varname>vpn-pre-down</varname></term>
         <listitem><para>The VPN will be deactivated but has not yet been
         disconnected from the network.  Scripts acting on this event must be
-        placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d
+        placed or symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-down.d</filename>
         directory, and NetworkManager will wait for script execution to complete
         before disconnecting the VPN from its network.  Note that this
         event is not emitted for forced disconnections, like when the VPN
@@ -308,7 +309,8 @@
       NetworkManager process, and will be killed if they run for too long. If your script
       might take arbitrarily long to complete, you should spawn a child process and have the
       parent return immediately. Scripts that are symbolic links pointing inside the
-      /etc/NetworkManager/dispatcher.d/no-wait.d/ directory are run immediately, without
+      <filename>/etc/NetworkManager/dispatcher.d/no-wait.d/</filename>
+      directory are run immediately, without
       waiting for the termination of previous scripts, and in parallel. Also beware that
       once a script is queued, it will always be run, even if a later event renders it
       obsolete. (Eg, if an interface goes up, and then back down again quickly, it is
@@ -354,14 +356,16 @@
         <term><option>--state-file</option></term>
         <listitem><para>Specify file for storing state of the
         NetworkManager persistently.  If not specified, the default
-        value of /var/lib/NetworkManager/NetworkManager.state is used.
+        value of <filename>/var/lib/NetworkManager/NetworkManager.state</filename>
+        is used.
         </para></listitem>
       </varlistentry>
       <varlistentry>
         <term><option>--config</option></term>
         <listitem><para> Specify configuration file to set up various
         settings for NetworkManager.  If not specified, the default
-        value of /etc/NetworkManager/NetworkManager.conf is used with
+        value of <filename>/etc/NetworkManager/NetworkManager.conf</filename>
+        is used with
         a fallback to the older 'nm-system-settings.conf' if located
         in the same directory.  See
         <link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>
@@ -407,7 +411,7 @@
   </refsect1>
 
   <refsect1>
-    <title>UDEV PROPERTIES</title>
+    <title>Udev Properties</title>
 
     <para>
       <citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>
@@ -448,8 +452,8 @@
           A SIGHUP also involves further reloading actions, like doing
           a DNS update and restarting the DNS plugin. The latter can be
           useful for example when using the dnsmasq plugin and changing
-          its configuration in /etc/NetworkManager/dnsmasq.d. However,
-          it also means this will shortly interrupt name resolution.
+          its configuration in <filename>/etc/NetworkManager/dnsmasq.d</filename>.
+          However, it also means this will shortly interrupt name resolution.
           In the future, there may be further actions added.
           A SIGHUP means to update NetworkManager configuration and reload
           everything that is supported. Note that this does not reload
@@ -486,7 +490,7 @@
   </refsect1>
 
   <refsect1>
-    <title>DEBUGGING</title>
+    <title>Debugging</title>
     <para>
       The following environment variables are supported to help
       debugging.  When used in conjunction with the
@@ -504,8 +508,17 @@
   </refsect1>
 
   <refsect1>
+    <title>Bugs</title>
+    <para>
+      Please report any bugs you find in NetworkManager at the
+      <ulink url="https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager">NetworkManager bug tracker</ulink>.
+    </para>
+  </refsect1>
+
+  <refsect1>
     <title>See Also</title>
     <para>
+      <ulink url="https://wiki.gnome.org/Projects/NetworkManager">NetworkManager home page</ulink>,
       <link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>,
       <link linkend='nmcli'><citerefentry><refentrytitle>nmcli</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>,
       <link linkend='nmcli-examples'><citerefentry><refentrytitle>nmcli-examples</refentrytitle><manvolnum>7</manvolnum></citerefentry></link>,
diff --git a/man/nm-online.1 b/man/nm-online.1
index ff02e2df..7192ea3a 100644
--- a/man/nm-online.1
+++ b/man/nm-online.1
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nm-online
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.4\&.2" "General Commands Manual"
+.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.4\&.4" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
diff --git a/man/nm-settings-ifcfg-rh.5 b/man/nm-settings-ifcfg-rh.5
index 7576df50..e69d4c45 100644
--- a/man/nm-settings-ifcfg-rh.5
+++ b/man/nm-settings-ifcfg-rh.5
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nm-settings-ifcfg-rh
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.3
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-IFCFG\" "5" "" "NetworkManager 1\&.4\&.2" "Configuration"
+.TH "NM\-SETTINGS\-IFCFG\" "5" "" "NetworkManager 1\&.4\&.3" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -336,7 +336,7 @@ are NetworkManager specific extensions not understood by traditional initscripts
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&1.\ \&802-1x setting
+.B Table\ \&1.\ \&802\-1x setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -748,7 +748,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&3.\ \&bridge-port setting
+.B Table\ \&3.\ \&bridge\-port setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -1391,7 +1391,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&8.\ \&ip-tunnel setting
+.B Table\ \&8.\ \&ip\-tunnel setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -1851,7 +1851,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&12.\ \&team-port setting
+.B Table\ \&12.\ \&team\-port setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2046,7 +2046,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&17.\ \&802-3-ethernet setting
+.B Table\ \&17.\ \&802\-3\-ethernet setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2195,7 +2195,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&18.\ \&802-11-wireless-security setting
+.B Table\ \&18.\ \&802\-11\-wireless\-security setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2402,7 +2402,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&19.\ \&802-11-wireless setting
+.B Table\ \&19.\ \&802\-11\-wireless setting
 .TS
 allbox tab(:);
 lB lB lB lB.
diff --git a/man/nm-settings-ifcfg-rh.xml b/man/nm-settings-ifcfg-rh.xml
index cbba4d2a..2490019e 100644
--- a/man/nm-settings-ifcfg-rh.xml
+++ b/man/nm-settings-ifcfg-rh.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
-<refentry id="nm-settings-ifcfg-rh"><refentryinfo><title>nm-settings-ifcfg-rh</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings-ifcfg-rh</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.2</refmiscinfo></refmeta><refnamediv><refname>nm-settings-ifcfg-rh</refname><refpurpose>Description of <emphasis>ifcfg-rh</emphasis> settings plugin</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
+<refentry id="nm-settings-ifcfg-rh"><refentryinfo><title>nm-settings-ifcfg-rh</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings-ifcfg-rh</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.3</refmiscinfo></refmeta><refnamediv><refname>nm-settings-ifcfg-rh</refname><refpurpose>Description of <emphasis>ifcfg-rh</emphasis> settings plugin</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
           NetworkManager is based on the concept of connection profiles that contain
           network configuration (see <citerefentry><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
diff --git a/man/nm-settings-keyfile.5 b/man/nm-settings-keyfile.5
index ffebaa09..433ba14d 100644
--- a/man/nm-settings-keyfile.5
+++ b/man/nm-settings-keyfile.5
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nm-settings-keyfile
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.3
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS\-KEYFIL" "5" "" "NetworkManager 1\&.4\&.2" "Configuration"
+.TH "NM\-SETTINGS\-KEYFIL" "5" "" "NetworkManager 1\&.4\&.3" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -513,7 +513,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&7.\ \&802-3-ethernet setting (section)
+.B Table\ \&7.\ \&802\-3\-ethernet setting (section)
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -566,7 +566,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&8.\ \&802-11-wireless setting (section)
+.B Table\ \&8.\ \&802\-11\-wireless setting (section)
 .TS
 allbox tab(:);
 lB lB lB lB.
diff --git a/man/nm-settings-keyfile.xml b/man/nm-settings-keyfile.xml
index b28395c5..e281e882 100644
--- a/man/nm-settings-keyfile.xml
+++ b/man/nm-settings-keyfile.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
-<refentry id="nm-settings-keyfile"><refentryinfo><title>nm-settings-keyfile</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings-keyfile</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.2</refmiscinfo></refmeta><refnamediv><refname>nm-settings-keyfile</refname><refpurpose>Description of <emphasis>keyfile</emphasis> settings plugin</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
+<refentry id="nm-settings-keyfile"><refentryinfo><title>nm-settings-keyfile</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings-keyfile</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.3</refmiscinfo></refmeta><refnamediv><refname>nm-settings-keyfile</refname><refpurpose>Description of <emphasis>keyfile</emphasis> settings plugin</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
           NetworkManager is based on the concept of connection profiles that contain
           network configuration (see <citerefentry><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details). The profiles can be
           stored in various formats. NetworkManager uses plugins for reading and writing
diff --git a/man/nm-settings.5 b/man/nm-settings.5
index eb4818a9..dde324fc 100644
--- a/man/nm-settings.5
+++ b/man/nm-settings.5
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nm-settings
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Configuration
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.3
 .\"  Language: English
 .\"
-.TH "NM\-SETTINGS" "5" "" "NetworkManager 1\&.4\&.2" "Configuration"
+.TH "NM\-SETTINGS" "5" "" "NetworkManager 1\&.4\&.3" "Configuration"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -63,7 +63,7 @@ command that can display description of particular settings and properties of th
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&1.\ \&802-1x setting
+.B Table\ \&1.\ \&802\-1x setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -758,7 +758,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&6.\ \&bridge-port setting
+.B Table\ \&6.\ \&bridge\-port setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2037,7 +2037,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&15.\ \&ip-tunnel setting
+.B Table\ \&15.\ \&ip\-tunnel setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2259,7 +2259,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&17.\ \&802-11-olpc-mesh setting
+.B Table\ \&17.\ \&802\-11\-olpc\-mesh setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -2734,7 +2734,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&22.\ \&team-port setting
+.B Table\ \&22.\ \&team\-port setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3290,7 +3290,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&28.\ \&802-3-ethernet setting
+.B Table\ \&28.\ \&802\-3\-ethernet setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3471,7 +3471,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&29.\ \&802-11-wireless setting
+.B Table\ \&29.\ \&802\-11\-wireless setting
 .TS
 allbox tab(:);
 lB lB lB lB.
@@ -3682,7 +3682,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&30.\ \&802-11-wireless-security setting
+.B Table\ \&30.\ \&802\-11\-wireless\-security setting
 .TS
 allbox tab(:);
 lB lB lB lB.
diff --git a/man/nm-settings.xml b/man/nm-settings.xml
index 94925278..d107231d 100644
--- a/man/nm-settings.xml
+++ b/man/nm-settings.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
-<refentry id="nm-settings"><refentryinfo><title>nm-settings</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.2</refmiscinfo></refmeta><refnamediv><refname>nm-settings</refname><refpurpose>Description of settings and properties of NetworkManager connection profiles</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
+<refentry id="nm-settings"><refentryinfo><title>nm-settings</title><author>NetworkManager developers</author></refentryinfo><refmeta><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum><refmiscinfo class="source">NetworkManager</refmiscinfo><refmiscinfo class="manual">Configuration</refmiscinfo><refmiscinfo class="version">1.4.3</refmiscinfo></refmeta><refnamediv><refname>nm-settings</refname><refpurpose>Description of settings and properties of NetworkManager connection profiles</refpurpose></refnamediv><refsect1 id="description"><title>Description</title><para>
           NetworkManager is based on a concept of connection profiles, sometimes referred to as
           connections only. These connection profiles contain a network configuration. When
           NetworkManager activates a connection profile on a network device the configuration will
diff --git a/man/nmcli-examples.7 b/man/nmcli-examples.7
index 69a627bc..2bfc2190 100644
--- a/man/nmcli-examples.7
+++ b/man/nmcli-examples.7
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nmcli-examples
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: Examples
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.4\&.2" "Examples"
+.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.4\&.4" "Examples"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -43,7 +43,7 @@ The purpose of this manual page is to provide you with various examples and usag
 \fInmcli\fR\&.
 .SH "EXAMPLES"
 .PP
-\fBExample\ \&1.\ \&Listing available Wi-Fi APs\fR
+\fBExample\ \&1.\ \&Listing available Wi\-Fi APs\fR
 .sp
 .if n \{\
 .RS 4
@@ -73,7 +73,7 @@ option for displaying different columns\&.
 \fBnmcli \-f all dev wifi list\fR
 will show all of them\&.
 .PP
-\fBExample\ \&2.\ \&Showing general information and properties for a Wi-Fi interface\fR
+\fBExample\ \&2.\ \&Showing general information and properties for a Wi\-Fi interface\fR
 .sp
 .if n \{\
 .RS 4
@@ -331,7 +331,7 @@ nager/ActiveConnection/9
 .PP
 This example shows escaping colon characters in tabular mode\&. It may be useful for script processing, because \*(Aq:\*(Aq is used as a field separator\&.
 .PP
-\fBExample\ \&11.\ \&nmcli usage in a NetworkManager dispatcher script to make Ethernet and Wi-Fi mutually exclusive\fR
+\fBExample\ \&11.\ \&nmcli usage in a NetworkManager dispatcher script to make Ethernet and Wi\-Fi mutually exclusive\fR
 .sp
 .if n \{\
 .RS 4
diff --git a/man/nmcli.1 b/man/nmcli.1
index 5023c0e4..13fc769e 100644
--- a/man/nmcli.1
+++ b/man/nmcli.1
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nmcli
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NMCLI" "1" "" "NetworkManager 1\&.4\&.2" "General Commands Manual"
+.TH "NMCLI" "1" "" "NetworkManager 1\&.4\&.4" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -529,6 +529,7 @@ For 802\&.1X password, the line would be
 .RE
 .\}
 .sp
+
 \fBnmcli\fR
 also accepts
 wifi\-sec
@@ -1321,7 +1322,7 @@ l l l.
 T{
 type
 T}:T{
-connection.type
+connection\&.type
 T}:T{
 This option also accepts values of \fBbond\-slave\fR,
 \fBteam\-slave\fR and \fBbridge\-slave\fR\&. They create
@@ -1331,21 +1332,21 @@ T}
 T{
 con\-name
 T}:T{
-connection.id
+connection\&.id
 T}:T{
 When not provided a default name is generated: <type>[\-<ifname>][\-<num>])\&.
 T}
 T{
 autoconnect
 T}:T{
-connection.autoconnect
+connection\&.autoconnect
 T}:T{
 \ \&
 T}
 T{
 ifname
 T}:T{
-connection.interface-name
+connection\&.interface\-name
 T}:T{
 A value of * will be interpreted as
 no value, making the connection profile interface\-independent\&.
@@ -1355,7 +1356,7 @@ T}
 T{
 master
 T}:T{
-connection.master
+connection\&.master
 T}:T{
 Value specified here will be canonicalized\&.
 It can be prefixed with ifname/, uuid/
@@ -1364,7 +1365,7 @@ T}
 T{
 slave\-type
 T}:T{
-connection.slave-type
+connection\&.slave\-type
 T}:T{
 \ \&
 T}
@@ -1391,17 +1392,17 @@ l l.
 T{
 username
 T}:T{
-pppoe.username
+pppoe\&.username
 T}
 T{
 password
 T}:T{
-pppoe.password
+pppoe\&.password
 T}
 T{
 service
 T}:T{
-pppoe.service
+pppoe\&.service
 T}
 .TE
 .sp 1
@@ -1426,17 +1427,17 @@ l l.
 T{
 mtu
 T}:T{
-wired.mtu
+wired\&.mtu
 T}
 T{
 mac
 T}:T{
-wired.mac-address
+wired\&.mac\-address
 T}
 T{
 cloned\-mac
 T}:T{
-wired.cloned-mac-address
+wired\&.cloned\-mac\-address
 T}
 .TE
 .sp 1
@@ -1463,27 +1464,27 @@ l l.
 T{
 mtu
 T}:T{
-infiniband.mtu
+infiniband\&.mtu
 T}
 T{
 mac
 T}:T{
-infiniband.mac-address
+infiniband\&.mac\-address
 T}
 T{
 transport\-mode
 T}:T{
-infiniband.transport-mode
+infiniband\&.transport\-mode
 T}
 T{
 parent
 T}:T{
-infiniband.parent
+infiniband\&.parent
 T}
 T{
 p\-key
 T}:T{
-infiniband.p-key
+infiniband\&.p\-key
 T}
 .TE
 .sp 1
@@ -1492,7 +1493,7 @@ T}
 .nr an-no-space-flag 1
 .nr an-break-flag 1
 .br
-.B Table\ \&5.\ \&Wi-Fi options
+.B Table\ \&5.\ \&Wi\-Fi options
 .TS
 allbox tab(:);
 lB lB.
@@ -1510,27 +1511,27 @@ l l.
 T{
 ssid
 T}:T{
-wireless.ssid
+wireless\&.ssid
 T}
 T{
 mode
 T}:T{
-wireless.mode
+wireless\&.mode
 T}
 T{
 mtu
 T}:T{
-wireless.mtu
+wireless\&.mtu
 T}
 T{
 mac
 T}:T{
-wireless.mac-address
+wireless\&.mac\-address
 T}
 T{
 cloned\-mac
 T}:T{
-wireless.cloned-mac-address
+wireless\&.cloned\-mac\-address
 T}
 .TE
 .sp 1
@@ -1554,12 +1555,12 @@ l l.
 T{
 nsp
 T}:T{
-wimax.network-name
+wimax\&.network\-name
 T}
 T{
 mac
 T}:T{
-wimax.mac-address
+wimax\&.mac\-address
 T}
 .TE
 .sp 1
@@ -1584,17 +1585,17 @@ l l.
 T{
 apn
 T}:T{
-gsm.apn
+gsm\&.apn
 T}
 T{
 user
 T}:T{
-gsm.username
+gsm\&.username
 T}
 T{
 password
 T}:T{
-gsm.password
+gsm\&.password
 T}
 .TE
 .sp 1
@@ -1618,12 +1619,12 @@ l l.
 T{
 user
 T}:T{
-cdma.username
+cdma\&.username
 T}
 T{
 password
 T}:T{
-cdma.password
+cdma\&.password
 T}
 .TE
 .sp 1
@@ -1649,14 +1650,14 @@ l l lt.
 T{
 addr
 T}:T{
-bluetooth.bdaddr
+bluetooth\&.bdaddr
 T}:T{
 \ \&
 T}
 T{
 bt\-type
 T}:T{
-bluetooth.type
+bluetooth\&.type
 T}:T{
 Apart from the usual dun and
 panu options, the values of dun\-gsm
@@ -1689,27 +1690,27 @@ l l.
 T{
 dev
 T}:T{
-vlan.parent
+vlan\&.parent
 T}
 T{
 id
 T}:T{
-vlan.id
+vlan\&.id
 T}
 T{
 flags
 T}:T{
-vlan.flags
+vlan\&.flags
 T}
 T{
 ingress
 T}:T{
-vlan.ingress-priority-map
+vlan\&.ingress\-priority\-map
 T}
 T{
 egress
 T}:T{
-vlan.egress-priority-map
+vlan\&.egress\-priority\-map
 T}
 .TE
 .sp 1
@@ -1788,7 +1789,7 @@ l l.
 T{
 config
 T}:T{
-team.config
+team\&.config
 T}
 .TE
 .sp 1
@@ -1811,7 +1812,7 @@ l l.
 T{
 config
 T}:T{
-team-port.config
+team\-port\&.config
 T}
 .TE
 .sp 1
@@ -1844,57 +1845,57 @@ l l.
 T{
 stp
 T}:T{
-bridge.stp
+bridge\&.stp
 T}
 T{
 priority
 T}:T{
-bridge.priority
+bridge\&.priority
 T}
 T{
 forward\-delay
 T}:T{
-bridge.forward-delay
+bridge\&.forward\-delay
 T}
 T{
 hello\-time
 T}:T{
-bridge.hello-time
+bridge\&.hello\-time
 T}
 T{
 max\-age
 T}:T{
-bridge.max-age
+bridge\&.max\-age
 T}
 T{
 ageing\-time
 T}:T{
-bridge.ageing-time
+bridge\&.ageing\-time
 T}
 T{
 multicast\-snooping
 T}:T{
-bridge.multicast-snooping
+bridge\&.multicast\-snooping
 T}
 T{
 mac
 T}:T{
-bridge.mac-address
+bridge\&.mac\-address
 T}
 T{
 priority
 T}:T{
-bridge-port.priority
+bridge\-port\&.priority
 T}
 T{
 path\-cost
 T}:T{
-bridge-port.path-cost
+bridge\-port\&.path\-cost
 T}
 T{
 hairpin
 T}:T{
-bridge-port.hairpin-mode
+bridge\-port\&.hairpin\-mode
 T}
 .TE
 .sp 1
@@ -1918,12 +1919,12 @@ l l.
 T{
 vpn\-type
 T}:T{
-vpn.service-type
+vpn\&.service\-type
 T}
 T{
 user
 T}:T{
-vpn.user-name
+vpn\&.user\-name
 T}
 .TE
 .sp 1
@@ -1948,17 +1949,17 @@ l l.
 T{
 ssid
 T}:T{
-olpc-mesh.ssid
+olpc\-mesh\&.ssid
 T}
 T{
 channel
 T}:T{
-olpc-mesh.channel
+olpc\-mesh\&.channel
 T}
 T{
 dhcp\-anycast
 T}:T{
-olpc-mesh.dhcp-anycast-address
+olpc\-mesh\&.dhcp\-anycast\-address
 T}
 .TE
 .sp 1
@@ -1984,22 +1985,22 @@ l l.
 T{
 username
 T}:T{
-adsl.username
+adsl\&.username
 T}
 T{
 protocol
 T}:T{
-adsl.protocol
+adsl\&.protocol
 T}
 T{
 password
 T}:T{
-adsl.password
+adsl\&.password
 T}
 T{
 encapsulation
 T}:T{
-adsl.encapsulation
+adsl\&.encapsulation
 T}
 .TE
 .sp 1
@@ -2024,17 +2025,17 @@ l l.
 T{
 dev
 T}:T{
-macvlan.parent
+macvlan\&.parent
 T}
 T{
 mode
 T}:T{
-macvlan.mode
+macvlan\&.mode
 T}
 T{
 tap
 T}:T{
-macvlan.tap
+macvlan\&.tap
 T}
 .TE
 .sp 1
@@ -2063,37 +2064,37 @@ l l.
 T{
 id
 T}:T{
-vxlan.id
+vxlan\&.id
 T}
 T{
 remote
 T}:T{
-vxlan.remote
+vxlan\&.remote
 T}
 T{
 dev
 T}:T{
-vxlan.parent
+vxlan\&.parent
 T}
 T{
 local
 T}:T{
-vxlan.local
+vxlan\&.local
 T}
 T{
 source\-port\-min
 T}:T{
-vxlan.source-port-min
+vxlan\&.source\-port\-min
 T}
 T{
 source\-port\-max
 T}:T{
-vxlan.source-port-max
+vxlan\&.source\-port\-max
 T}
 T{
 destination\-port
 T}:T{
-vxlan.destination-port
+vxlan\&.destination\-port
 T}
 .TE
 .sp 1
@@ -2121,32 +2122,32 @@ l l.
 T{
 mode
 T}:T{
-tun.mode
+tun\&.mode
 T}
 T{
 owner
 T}:T{
-tun.owner
+tun\&.owner
 T}
 T{
 group
 T}:T{
-tun.group
+tun\&.group
 T}
 T{
 pi
 T}:T{
-tun.pi
+tun\&.pi
 T}
 T{
 vnet\-hdr
 T}:T{
-tun.vnet-hdr
+tun\&.vnet\-hdr
 T}
 T{
 multi\-queue
 T}:T{
-tun.multi-queue
+tun\&.multi\-queue
 T}
 .TE
 .sp 1
@@ -2172,22 +2173,22 @@ l l.
 T{
 mode
 T}:T{
-ip-tunnel.mode
+ip\-tunnel\&.mode
 T}
 T{
 local
 T}:T{
-ip-tunnel.local
+ip\-tunnel\&.local
 T}
 T{
 remote
 T}:T{
-ip-tunnel.remote
+ip\-tunnel\&.remote
 T}
 T{
 dev
 T}:T{
-ip-tunnel.parent
+ip\-tunnel\&.parent
 T}
 .TE
 .sp 1
@@ -2213,7 +2214,7 @@ l l l.
 T{
 ip4
 T}:T{
-ipv4.addresses
+ipv4\&.addresses
 T}:T{
 This option can be specified multiple times\&.
 It\*(Aqs equivalent of using +ipv4\&.addresses syntax\&.
@@ -2221,7 +2222,7 @@ T}
 T{
 gw4
 T}:T{
-ipv4.gateway
+ipv4\&.gateway
 T}:T{
 \ \&
 T}
@@ -2249,7 +2250,7 @@ l l l.
 T{
 ip6
 T}:T{
-ipv6.addresses
+ipv6\&.addresses
 T}:T{
 This option can be specified multiple times\&.
 It\*(Aqs equivalent of using +ipv6\&.addresses syntax\&.
@@ -2257,7 +2258,7 @@ T}
 T{
 gw6
 T}:T{
-ipv6.gateway
+ipv6\&.gateway
 T}:T{
 \ \&
 T}
diff --git a/man/nmtui.1 b/man/nmtui.1
index 7b6f2bf6..2e6e1a1b 100644
--- a/man/nmtui.1
+++ b/man/nmtui.1
@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: nmtui
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 09/30/2016
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 12/16/2016
 .\"    Manual: General Commands Manual
-.\"    Source: NetworkManager 1.4.2
+.\"    Source: NetworkManager 1.4.4
 .\"  Language: English
 .\"
-.TH "NMTUI" "1" "" "NetworkManager 1\&.4\&.2" "General Commands Manual"
+.TH "NMTUI" "1" "" "NetworkManager 1\&.4\&.4" "General Commands Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------