Codex

NMCLI-EXAMPLES

Section: Examples (5)

Updated:

Index?action=index Return to Main Contents


NAME

nmcli-examples - usage examples of nmcli

SYNOPSIS

:nmcli [OPTIONS...]

DESCRIPTION

nmcli

is a command-line client for NetworkManager. It allows controlling NetworkManager and reporting its status. For more information please refer to nmcli?(1) manual page.

The purpose of this manual page is to provide you with various examples and usage scenarios of nmcli.

Note: this page has "work-in-progress" status.

EXAMPLES

Example 1. Listing available Wi-Fi APs

:

''' $ nmcli device wifi list '''

@] :

This command shows how to list available Wi-Fi networks (APs). You can also use --fields option for displaying different columns. nmcli -f all dev wifi list will show all of them.

Example 2. Showing general information and properties for a Wi-Fi interface

:

''' $ nmcli -p -f general,wifi-properties device show wlan0 '''

@] :

This command shows information about a Wi-Fi device.

Example 3. Listing NetworkManager polkit permissions

:

''' $ nmcli general permissions '''

@] :

This command shows configured polkit permissions for various NetworkManager operations. These permissions or actions (using polkit language) are configured by a system administrator and are not meant to be changed by users. The usual place for the polkit configuration is /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy. pkaction command can display description for polkit actions.

:

''' pkaction --action-id org.freedesktop.NetworkManager.network-control --verbose '''

@] :

More information about polkit can be found at http://www.freedesktop.org/wiki/Software/polkit.

Example 4. Listing NetworkManager log level and domains

:

''' $ nmcli general logging '''

@] :

This command shows current NetworkManager logging status.

Example 5. Changing NetworkManager logging

:

''' $ nmcli g log level DEBUG domains CORE,ETHER,IP $ nmcli g log level INFO domains DEFAULT '''

@] :

The first command makes NetworkManager log in DEBUG level, and only for CORE, ETHER and IP domains. The second command restores the default logging state. Please refer to the (5) manual page for available logging levels and domains.

Example 6. Adding a bonding master and two slave connection profiles

:

''' $ nmcli con add type bond ifname mybond0 mode active-backup $ nmcli con add type bond-slave ifname eth1 master mybond0 $ nmcli con add type bond-slave ifname eth2 master mybond0 '''

@] :

This example demonstrates adding a bond master connection and two slaves. The first command adds a master bond connection, naming the bonding interface mybond0 and using active-backup mode. The next two commands add slaves connections, both enslaved to mybond0. The first slave will be bound to eth1 interface, the second to eth2.

Example 7. Adding a team master and two slave connection profiles

:

''' $ nmcli con add type team con-name Team1 ifname Team1 config team1-master-json.conf $ nmcli con add type team-slave con-name Team1-slave1 ifname em1 master Team1 $ nmcli con add type team-slave con-name Team1-slave2 ifname em2 master Team1 '''

@] :

This example demonstrates adding a team master connection profile and two slaves. It is very similar to the bonding example. The first command adds a master team profile, naming the team interface and the profile Team1. The team configuration for the master is read from team1-master-json.conf file. Later, you can change the configuration with modify command (nmcli con modify Team1 team.config team1-master-another-json.conf). The last two commands add slaves profiles, both enslaved to Team1. The first slave will be bound to em1 interface, the second to em2. The slaves don't specify config and thus teamd will use its default configuration. You will activate the whole setup by activating both slaves:

:

''' $ nmcli con up Team1-slave1 $ nmcli con up Team1-slave2 '''

@] :

By default, the created profiles are marked for auto-activation. But if another connection has been activated on the device, the new profile won't activate automatically and you need to activate it manually.

Example 8. Adding a bridge and two slave profiles

:

''' $ nmcli con add type bridge con-name TowerBridge ifname TowerBridge $ nmcli con add type bridge-slave con-name br-slave-1 ifname ens3 master TowerBridge $ nmcli con add type bridge-slave con-name br-slave-2 ifname ens4 master TowerBridge $ nmcli con modify TowerBridge bridge.stp no '''

@] :

This example demonstrates adding a bridge master connection and two slaves. The first command adds a master bridge connection, naming the bridge interface and the profile as TowerBridge. The next two commands add slaves profiles, both will be enslaved to TowerBridge. The first slave will be tied to ens3 interface, the second to ens4. The last command will disable 802.1D STP for the TowerBridge profile.

Example 9. Adding an ethernet connection profile with manual IP configuration

:

''' $ nmcli con add con-name my-con-em1 ifname em1 type ethernet ip4 192.168.100.100/24 gw4 192.168.100.1 ip4 1.2.3.4 ip6 abbe::cafe $ nmcli con mod my-con-em1 ipv4.dns "8.8.8.8 8.8.4.4" $ nmcli con mod my-con-em1 ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844" $ nmcli -p con show my-con-em1 '''

@] :

The first command adds an Ethernet connection profile named my-con-em1 that is bound to interface name em1. The profile is configured with static IP addresses. Three addresses are added, two IPv4 addresses and one IPv6. The first IP 192.168.100.100 has a prefix of 24 (netmask equivalent of 255.255.255.0). Gateway entry for the first IP address will become the default route if this profile is activated on em1 interface (and there is no connection with higher priority). The second two addresses don't specify a prefix, so a default prefix will be used, i.e. 32 for IPv4 and 128 for IPv6. The second and third commands modify DNS parameters of the new connection profile. The last con show command displays the profile so that all parameters can be reviewed.

Example 10. Escaping colon characters in tabular mode

:

''' $ nmcli -t -f general -e yes -m tab dev show eth0 '''

@] :

This example shows escaping colon characters in tabular mode. It may be useful for script processing, because ':' is used as a field separator.

Example 11. nmcli usage in a NetworkManager dispatcher script to make Ethernet and Wi-Fi mutually exclusive

This dispatcher script makes Wi-Fi mutually exclusive with wired networking. When a wired interface is connected, Wi-Fi will be set to airplane mode (rfkilled). When the wired interface is disconnected, Wi-Fi will be turned back on. Name this script e.g. 70-wifi-wired-exclusive.sh and put it into /etc/NetworkManager/dispatcher.d/ directory. See NetworkManager?(8) manual page for more information about NetworkManager dispatcher scripts.

Example sessions of interactive connection editor

Example 12. Adding an ethernet connection profile in interactive editor (a)

:

''' $ nmcli connection edit type ethernet '''

@] :

Example session in the nmcli interactive connection editor. The scenario creates an Ethernet connection (configuration) with static addressing (IPs and DNS).

SEE ALSO

nmcli?(1), NetworkManager?(8), (5), nm-settings?(5), nm-online?(1), nm-applet?(1), nm-connection-editor?(1)


Index

NAME

SYNOPSIS

DESCRIPTION

EXAMPLES

SEE ALSO