NM-CONNECTION-EDITOR(1) General Commands Manual NM-CONNECTION-EDITOR(1)NAME
nm-connection-editor - network connection editor for NetworkManager
nm-connection-editor [ OPTIONS ]
nm-connection-editor is a GTK-based application to add, remove, and modify network connections stored by NetworkManager. NetworkManager
must be running for any network connections to be added, removed, or modified.
OPTIONS -t, --type=<type>
Type of connection to create or show. Values are NetworkManager setting names, eg "802-3-ethernet", "802-11-wireless", "bridge",
"bond", "wimax", "infiniband", "vlan", etc. Does nothing if --create or --show is not given.
Expand or collapse the network list to highlight the network connection type given by --type.
Create a new connection of the type given by --type and allow the user to modify connection details.
Show the network connection edit window for the connection of the given UUID.
SEE ALSO nmcli(1), NetworkManager(8), nm-applet(1).
15 February 2013 NM-CONNECTION-EDITOR(1)
Check Out this Related Man Page
NETWORKMANAGER(8) Network management daemons NETWORKMANAGER(8)NAME
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
NetworkManager will execute scripts in the /etc/NetworkManager/dispatcher.d directory 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.
Each script receives two arguments, the first being the interface name of the device an operation just happened on, and second the action.
The actions are:
The interface has been activated.
The interface has been deactivated.
A VPN connection has been activated.
A VPN connection has been deactivated.
The system hostname has been updated. Use gethostname(2) to retrieve it. The interface name (first argument) is empty and no
environment variable is set for this action.
The DHCPv4 lease has changed (renewed, rebound, etc).
The DHCPv6 lease has changed (renewed, rebound, etc).
The environment contains more information about the interface and the connection. The following variables are available for the use in the
The UUID of the connection profile.
The name (ID) of the connection profile.
The interface name of the device.
The IP interface name of the device.
The IPv4 address in the format "address/prefix gateway", where N is a number from 0 to (# IPv4 address - 1).
The variable contains the number of IPv4 addresses the script may expect.
The IPv4 route in the format "address/prefix next-hop metric", where N is a number from 0 to (# IPv4 routes - 1).
The variable contains the number of IPv4 routes the script may expect.
The variable contains a space-separated list of the DNS servers.
The variable contains a space-separated list of the search domains.
If the connection used DHCP for address configuration, the received DHCP configuration is passed in the environment using standard DHCP
option names, prefixed with "DHCP4_", like "DHCP4_HOST_NAME=foobar".
IP6_<name> and DHCP6_<name>
The same variables as for IPv4 are available for IPv6, but the prefixes are IP6_ and DHCP6_ instead.
In case of VPN, VPN_IP_IFACE is set, and IP4_*, IP6_* variables with VPN prefix are exported too, like VPN_IP4_ADDRESS_0,
The following options are understood:
--version | -V
Print the NetworkManager software version and exit.
--help | -h
Print NetworkManager's available options and exit.
--no-daemon | -n
Do not daemonize.
--debug | -d
Do not daemonize, and direct log output to the controlling terminal in addition to syslog.
--pid-file | -p
Specify location of a PID file. The PID file is used for storing PID of the running proccess and prevents running multiple instances.
Specify file for storing state of the NetworkManager persistently. If not specified, the default value of
/var/lib/NetworkManager/NetworkManager.state is used.
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 'nm-system-settings.conf' if located in the same
directory. See NetworkManager.conf(5) for more information on configuration file.
List plugins used to manage system-wide connection settings. This list has preference over plugins specified in the configuration file.
Currently supported plugins are: keyfile, ifcfg-rh, ifcfg-suse, ifupdown.
Sets how much information NetworkManager sends to the log destination (usually syslog's "daemon" facility). By default, only
informational, warning, and error messages are logged. See the section on logging in NetworkManager.conf(5) for more information.
A comma-separated list specifying which operations are logged to the log destination (usually syslog). By default, most domains are
logging-enabled. See the section on logging in NetworkManager.conf(5) for more information.
The following environment variables are supported to help debugging. When used in conjunction with the --no-daemon option (thus echoing PPP
and DHCP helper output to stdout) these can quickly help pinpoint the source of connection issues. Also see the --log-level and
--log-domains to enable debug logging inside NetworkManager itself.
NM_PPP_DEBUG: When set to anything, causes NetworkManager to turn on PPP debugging in pppd, which logs all PPP and PPTP frames and
SEE ALSO NetworkManager.conf(5), nmcli(1), nmcli-examples(5), nm-online(1), nm-settings(5), nm-applet(1), nm-connection-editor(1)NetworkManager 0.9.10NETWORKMANAGER(8)