From 0018d1f3cf71d680d7b6bceda55a5717244d8b26 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Tue, 16 Aug 2022 18:24:19 +0200 Subject: New upstream version 1.39.90 --- docs/api/html/nmcli-examples.html | 56 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 56 insertions(+) (limited to 'docs/api/html/nmcli-examples.html') diff --git a/docs/api/html/nmcli-examples.html b/docs/api/html/nmcli-examples.html index 2bc6cbc2..0a832ab7 100644 --- a/docs/api/html/nmcli-examples.html +++ b/docs/api/html/nmcli-examples.html @@ -633,6 +633,62 @@ Connection 'ethernet-4' (de89cdeb-a3e1-4d53-8fa0-c22546c775f4) successfully 
$ nmcli connection add type bluetooth con-name "My Bluetooth Hotspot" autoconnect no ifname btnap0 bluetooth.type nap ipv4.method shared ipv6.method shared
+
+

Example 18. Offline use

+
+
$ nmcli --offline con add type ethernet '
+  conn.id eth0 \
+  conn.interface-name eth0 \
+  >/sysroot/etc/NetworkManager/system-connections/eth0.nmconnection
+

+ Creates a connection file in keyfile format without using the NetworkManager service. + This allows for use of familiar nmcli syntax in situations + where the service is not running, such as during system installation of image + provisioning and ensures the resulting file is correctly formatted. +

+
$ nmcli --offline con modify type ethernet '
+  conn.id eth0-ipv6 \
+  ipv4.method disabled \
+  </sysroot/etc/NetworkManager/system-connections/eth0.nmconnection \
+  >/sysroot/etc/NetworkManager/system-connections/eth0-ipv6.nmconnection
+

+ Read and write a connection file without using the NetworkManager service, modifying + some properties along the way. +

+

+ This allows templating of the connection profiles using familiar + nmcli syntax in situations where the service is not running. +

+
+
+
+

Example 19. Device Checkpoint and Restore

+
+
$ nmcli dev checkpoint eth0 -- nmcli dev dis eth0
+Device 'eth0' successfully disconnected.
+Type "Yes" to commit the changes: No
+Checkpoint was removed.
+

+ In this example the device eth0 was disconnected with the eth0 checkpoint + taken. The user didn't confirm that the change is good, so the eth0 was + brought back to the state it was when the checkpoint was taken. +

+

+ If the command being run unintentionaly brings down the remote connection + (such as a + ssh(1) + session) to the very machine it's being run on, the user wouldn't be able to + confirm the success and the connectivity would end up being restored + after a timeout. +

+

+ If, on the other hand, the command results in a success, the user could just + confirm, causing the checkpoint to be abandoned without a rollback: +

+
$ nmcli dev checkpoint -- ip link del br0
+Type "Yes" to commit the changes: Yes
+
+

-- cgit 1.3.0-6-gf8a5