From 34bb501be08aa2b313d88e67d6e0a7e0a3f9cfa6 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 5 May 2024 00:07:30 +0200 Subject: New upstream version 1.47.90 --- docs/api/Makefile.in | 1039 ------------------- docs/api/NetworkManager-overrides.txt | 0 docs/api/NetworkManager-sections.txt | 0 ...-org.freedesktop.NetworkManager.AccessPoint.xml | 157 --- ...org.freedesktop.NetworkManager.AgentManager.xml | 83 -- ...reedesktop.NetworkManager.Connection.Active.xml | 283 ------ ...-org.freedesktop.NetworkManager.DHCP4Config.xml | 34 - ...-org.freedesktop.NetworkManager.DHCP6Config.xml | 34 - ...-org.freedesktop.NetworkManager.Device.Adsl.xml | 37 - ...freedesktop.NetworkManager.Device.Bluetooth.xml | 60 -- ...-org.freedesktop.NetworkManager.Device.Bond.xml | 62 -- ...rg.freedesktop.NetworkManager.Device.Bridge.xml | 62 -- ...org.freedesktop.NetworkManager.Device.Dummy.xml | 34 - ...g.freedesktop.NetworkManager.Device.Generic.xml | 45 - ...s-org.freedesktop.NetworkManager.Device.Hsr.xml | 78 -- ....freedesktop.NetworkManager.Device.IPTunnel.xml | 171 ---- ...reedesktop.NetworkManager.Device.Infiniband.xml | 49 - ....freedesktop.NetworkManager.Device.Loopback.xml | 15 - ...rg.freedesktop.NetworkManager.Device.Macsec.xml | 172 ---- ...g.freedesktop.NetworkManager.Device.Macvlan.xml | 67 -- ...org.freedesktop.NetworkManager.Device.Modem.xml | 92 -- ....freedesktop.NetworkManager.Device.OlpcMesh.xml | 58 -- ...reedesktop.NetworkManager.Device.Statistics.xml | 59 -- ...-org.freedesktop.NetworkManager.Device.Team.xml | 73 -- ...s-org.freedesktop.NetworkManager.Device.Tun.xml | 103 -- ...-org.freedesktop.NetworkManager.Device.Veth.xml | 34 - ...-org.freedesktop.NetworkManager.Device.Vlan.xml | 71 -- ...org.freedesktop.NetworkManager.Device.Vxlan.xml | 217 ---- ...g.freedesktop.NetworkManager.Device.WifiP2P.xml | 148 --- ...freedesktop.NetworkManager.Device.WireGuard.xml | 57 -- ...org.freedesktop.NetworkManager.Device.Wired.xml | 84 -- ....freedesktop.NetworkManager.Device.Wireless.xml | 235 ----- .../dbus-org.freedesktop.NetworkManager.Device.xml | 636 ------------ ...s-org.freedesktop.NetworkManager.DnsManager.xml | 62 -- ...us-org.freedesktop.NetworkManager.IP4Config.xml | 189 ---- ...us-org.freedesktop.NetworkManager.IP6Config.xml | 142 --- .../dbus-org.freedesktop.NetworkManager.PPP.xml | 126 --- ...-org.freedesktop.NetworkManager.SecretAgent.xml | 179 ---- ...edesktop.NetworkManager.Settings.Connection.xml | 350 ------- ...bus-org.freedesktop.NetworkManager.Settings.xml | 419 -------- ...g.freedesktop.NetworkManager.VPN.Connection.xml | 82 -- ...s-org.freedesktop.NetworkManager.VPN.Plugin.xml | 380 ------- docs/api/dbus-org.freedesktop.NetworkManager.xml | 1056 -------------------- docs/api/html/NetworkManager.conf.html | 46 +- docs/api/html/NetworkManager.devhelp2 | 10 + docs/api/html/index.html | 2 +- docs/api/html/ix01.html | 198 ++-- docs/api/html/nm-dbus-types.html | 152 ++- docs/api/html/nm-settings-dbus.html | 72 +- docs/api/html/nm-settings-ifcfg-rh.html | 23 + docs/api/html/nm-settings-keyfile.html | 16 + docs/api/html/nm-settings-nmcli.html | 137 ++- docs/api/html/settings-802-11-wireless.html | 6 + docs/api/html/settings-802-1x.html | 6 + docs/api/html/settings-802-3-ethernet.html | 6 + docs/api/html/settings-connection.html | 14 +- docs/api/html/settings-ipv4.html | 6 + docs/api/html/settings-ipv6.html | 26 +- docs/api/network-manager-docs.xml | 4 +- docs/api/network-manager-overrides.txt | 0 docs/api/settings-spec.xml | 575 ----------- docs/api/settings-spec.xsl | 4 +- docs/api/version.xml | 1 - 63 files changed, 580 insertions(+), 8058 deletions(-) delete mode 100644 docs/api/Makefile.in delete mode 100644 docs/api/NetworkManager-overrides.txt delete mode 100644 docs/api/NetworkManager-sections.txt delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.AgentManager.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Connection.Active.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.DHCP4Config.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.DHCP6Config.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Adsl.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Macsec.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Modem.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Statistics.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Tun.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Veth.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Vlan.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Wired.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.Wireless.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Device.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.DnsManager.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.PPP.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.SecretAgent.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Settings.Connection.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.VPN.Connection.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml delete mode 100644 docs/api/dbus-org.freedesktop.NetworkManager.xml create mode 100644 docs/api/network-manager-overrides.txt delete mode 100644 docs/api/settings-spec.xml delete mode 100644 docs/api/version.xml (limited to 'docs/api') diff --git a/docs/api/Makefile.in b/docs/api/Makefile.in deleted file mode 100644 index 9bc408e3..00000000 --- a/docs/api/Makefile.in +++ /dev/null @@ -1,1039 +0,0 @@ -# Makefile.in generated by automake 1.16.5 from Makefile.am. -# @configure_input@ - -# Copyright (C) 1994-2021 Free Software Foundation, Inc. - -# This Makefile.in is free software; the Free Software Foundation -# gives unlimited permission to copy and/or distribute it, -# with or without modifications, as long as this notice is preserved. - -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY, to the extent permitted by law; without -# even the implied warranty of MERCHANTABILITY or FITNESS FOR A -# PARTICULAR PURPOSE. - -@SET_MAKE@ - -# -*- mode: makefile -*- -# -# gtk-doc.make - make rules for gtk-doc -# Copyright (C) 2003 James Henstridge -# 2004-2007 Damon Chaplin -# 2007-2017 Stefan Sauer -# -# This program is free software: you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation, either version 3 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program. If not, see . - -#################################### -# Everything below here is generic # -#################################### -VPATH = @srcdir@ -am__is_gnu_make = { \ - if test -z '$(MAKELEVEL)'; then \ - false; \ - elif test -n '$(MAKE_HOST)'; then \ - true; \ - elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \ - true; \ - else \ - false; \ - fi; \ -} -am__make_running_with_option = \ - case $${target_option-} in \ - ?) ;; \ - *) echo "am__make_running_with_option: internal error: invalid" \ - "target option '$${target_option-}' specified" >&2; \ - exit 1;; \ - esac; \ - has_opt=no; \ - sane_makeflags=$$MAKEFLAGS; \ - if $(am__is_gnu_make); then \ - sane_makeflags=$$MFLAGS; \ - else \ - case $$MAKEFLAGS in \ - *\\[\ \ ]*) \ - bs=\\; \ - sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ - | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ - esac; \ - fi; \ - skip_next=no; \ - strip_trailopt () \ - { \ - flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ - }; \ - for flg in $$sane_makeflags; do \ - test $$skip_next = yes && { skip_next=no; continue; }; \ - case $$flg in \ - *=*|--*) continue;; \ - -*I) strip_trailopt 'I'; skip_next=yes;; \ - -*I?*) strip_trailopt 'I';; \ - -*O) strip_trailopt 'O'; skip_next=yes;; \ - -*O?*) strip_trailopt 'O';; \ - -*l) strip_trailopt 'l'; skip_next=yes;; \ - -*l?*) strip_trailopt 'l';; \ - -[dEDm]) skip_next=yes;; \ - -[JT]) skip_next=yes;; \ - esac; \ - case $$flg in \ - *$$target_option*) has_opt=yes; break;; \ - esac; \ - done; \ - test $$has_opt = yes -am__make_dryrun = (target_option=n; $(am__make_running_with_option)) -am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) -pkgdatadir = $(datadir)/@PACKAGE@ -pkgincludedir = $(includedir)/@PACKAGE@ -pkglibdir = $(libdir)/@PACKAGE@ -pkglibexecdir = $(libexecdir)/@PACKAGE@ -am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd -install_sh_DATA = $(install_sh) -c -m 644 -install_sh_PROGRAM = $(install_sh) -c -install_sh_SCRIPT = $(install_sh) -c -INSTALL_HEADER = $(INSTALL_DATA) -transform = $(program_transform_name) -NORMAL_INSTALL = : -PRE_INSTALL = : -POST_INSTALL = : -NORMAL_UNINSTALL = : -PRE_UNINSTALL = : -POST_UNINSTALL = : -build_triplet = @build@ -host_triplet = @host@ -target_triplet = @target@ -@BUILD_DOCS_TRUE@am__append_1 = settings-spec.xml -@WITH_OPENVSWITCH_TRUE@am__append_2 = $(top_builddir)/man/nm-openvswitch.xml -@BUILD_NM_CLOUD_SETUP_TRUE@am__append_3 = $(top_builddir)/man/nm-cloud-setup.xml -@CONFIG_PLUGIN_IFCFG_RH_TRUE@am__append_4 = $(top_builddir)/man/nm-settings-ifcfg-rh.xml -subdir = docs/api -ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 -am__aclocal_m4_deps = $(top_srcdir)/m4/attributes.m4 \ - $(top_srcdir)/m4/ax_lib_readline.m4 \ - $(top_srcdir)/m4/ax_pthread.m4 \ - $(top_srcdir)/m4/build-to-host.m4 \ - $(top_srcdir)/m4/compiler_options.m4 \ - $(top_srcdir)/m4/gettext.m4 $(top_srcdir)/m4/git-sha-record.m4 \ - $(top_srcdir)/m4/gnome-code-coverage.m4 \ - $(top_srcdir)/m4/gtk-doc.m4 $(top_srcdir)/m4/host-cpu-c-abi.m4 \ - $(top_srcdir)/m4/iconv.m4 $(top_srcdir)/m4/intlmacosx.m4 \ - $(top_srcdir)/m4/introspection.m4 $(top_srcdir)/m4/lib-ld.m4 \ - $(top_srcdir)/m4/lib-link.m4 $(top_srcdir)/m4/lib-prefix.m4 \ - $(top_srcdir)/m4/libtool.m4 $(top_srcdir)/m4/ltoptions.m4 \ - $(top_srcdir)/m4/ltsugar.m4 $(top_srcdir)/m4/ltversion.m4 \ - $(top_srcdir)/m4/lt~obsolete.m4 $(top_srcdir)/m4/nls.m4 \ - $(top_srcdir)/m4/po.m4 $(top_srcdir)/m4/progtest.m4 \ - $(top_srcdir)/m4/vapigen.m4 $(top_srcdir)/configure.ac -am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ - $(ACLOCAL_M4) -DIST_COMMON = $(srcdir)/Makefile.am $(am__DIST_COMMON) -mkinstalldirs = $(install_sh) -d -CONFIG_HEADER = $(top_builddir)/config.h -CONFIG_CLEAN_FILES = version.xml -CONFIG_CLEAN_VPATH_FILES = -AM_V_P = $(am__v_P_@AM_V@) -am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) -am__v_P_0 = false -am__v_P_1 = : -AM_V_GEN = $(am__v_GEN_@AM_V@) -am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) -am__v_GEN_0 = @echo " GEN " $@; -am__v_GEN_1 = -AM_V_at = $(am__v_at_@AM_V@) -am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) -am__v_at_0 = @ -am__v_at_1 = -SOURCES = -DIST_SOURCES = -am__can_run_installinfo = \ - case $$AM_UPDATE_INFO_DIR in \ - n|no|NO) false;; \ - *) (install-info --version) >/dev/null 2>&1;; \ - esac -am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) -am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/version.xml.in \ - $(top_srcdir)/gtk-doc.make -DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) -ACLOCAL = @ACLOCAL@ -AMTAR = @AMTAR@ -AM_CFLAGS = @AM_CFLAGS@ -AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ -AR = @AR@ -AUTOCONF = @AUTOCONF@ -AUTOHEADER = @AUTOHEADER@ -AUTOMAKE = @AUTOMAKE@ -AWK = @AWK@ -BLUEZ5_CFLAGS = @BLUEZ5_CFLAGS@ -BLUEZ5_LIBS = @BLUEZ5_LIBS@ -CC = @CC@ -CCDEPMODE = @CCDEPMODE@ -CFLAGS = @CFLAGS@ -CODE_COVERAGE_CFLAGS = @CODE_COVERAGE_CFLAGS@ -CODE_COVERAGE_ENABLED = @CODE_COVERAGE_ENABLED@ -CODE_COVERAGE_LDFLAGS = @CODE_COVERAGE_LDFLAGS@ -CPP = @CPP@ -CPPFLAGS = @CPPFLAGS@ -CSCOPE = @CSCOPE@ -CTAGS = @CTAGS@ -CXX = @CXX@ -CXXCPP = @CXXCPP@ -CXXDEPMODE = @CXXDEPMODE@ -CXXFLAGS = @CXXFLAGS@ -CYGPATH_W = @CYGPATH_W@ -DBUS_SYS_DIR = @DBUS_SYS_DIR@ -DEFS = @DEFS@ -DEPDIR = @DEPDIR@ -DISTRO_NETWORK_SERVICE = @DISTRO_NETWORK_SERVICE@ -DLLTOOL = @DLLTOOL@ -DL_LIBS = @DL_LIBS@ -DNSMASQ_PATH = @DNSMASQ_PATH@ -DSYMUTIL = @DSYMUTIL@ -DUMPBIN = @DUMPBIN@ -ECHO_C = @ECHO_C@ -ECHO_N = @ECHO_N@ -ECHO_T = @ECHO_T@ -EGREP = @EGREP@ -ELOGIND_INHIBIT_CFLAGS = @ELOGIND_INHIBIT_CFLAGS@ -ELOGIND_INHIBIT_LIBS = @ELOGIND_INHIBIT_LIBS@ -ETAGS = @ETAGS@ -EXEEXT = @EXEEXT@ -FGREP = @FGREP@ -FILECMD = @FILECMD@ -GENHTML = @GENHTML@ -GETTEXT_MACRO_VERSION = @GETTEXT_MACRO_VERSION@ -GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ -GLIB_CFLAGS = @GLIB_CFLAGS@ -GLIB_LIBS = @GLIB_LIBS@ -GLIB_MAKEFILE = @GLIB_MAKEFILE@ -GLIB_MKENUMS = @GLIB_MKENUMS@ -GMSGFMT = @GMSGFMT@ -GMSGFMT_015 = @GMSGFMT_015@ -GNUTLS_CFLAGS = @GNUTLS_CFLAGS@ -GNUTLS_LIBS = @GNUTLS_LIBS@ -GREP = @GREP@ -GTKDOC_CHECK = @GTKDOC_CHECK@ -GTKDOC_CHECK_PATH = @GTKDOC_CHECK_PATH@ -GTKDOC_DEPS_CFLAGS = @GTKDOC_DEPS_CFLAGS@ -GTKDOC_DEPS_LIBS = @GTKDOC_DEPS_LIBS@ -GTKDOC_MKPDF = @GTKDOC_MKPDF@ -GTKDOC_REBASE = @GTKDOC_REBASE@ -HTML_DIR = @HTML_DIR@ -INSTALL = @INSTALL@ -INSTALL_DATA = @INSTALL_DATA@ -INSTALL_PROGRAM = @INSTALL_PROGRAM@ -INSTALL_SCRIPT = @INSTALL_SCRIPT@ -INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ -INTLLIBS = @INTLLIBS@ -INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@ -INTROSPECTION_CFLAGS = @INTROSPECTION_CFLAGS@ -INTROSPECTION_COMPILER = @INTROSPECTION_COMPILER@ -INTROSPECTION_GENERATE = @INTROSPECTION_GENERATE@ -INTROSPECTION_GIRDIR = @INTROSPECTION_GIRDIR@ -INTROSPECTION_LIBS = @INTROSPECTION_LIBS@ -INTROSPECTION_MAKEFILE = @INTROSPECTION_MAKEFILE@ -INTROSPECTION_SCANNER = @INTROSPECTION_SCANNER@ -INTROSPECTION_TYPELIBDIR = @INTROSPECTION_TYPELIBDIR@ -IPTABLES_PATH = @IPTABLES_PATH@ -JANSSON_CFLAGS = @JANSSON_CFLAGS@ -JANSSON_LIBS = @JANSSON_LIBS@ -KERNEL_FIRMWARE_DIR = @KERNEL_FIRMWARE_DIR@ -LCOV = @LCOV@ -LD = @LD@ -LDFLAGS = @LDFLAGS@ -LIBAUDIT_CFLAGS = @LIBAUDIT_CFLAGS@ -LIBAUDIT_LIBS = @LIBAUDIT_LIBS@ -LIBCURL_CFLAGS = @LIBCURL_CFLAGS@ -LIBCURL_LIBS = @LIBCURL_LIBS@ -LIBICONV = @LIBICONV@ -LIBINTL = @LIBINTL@ -LIBNDP_CFLAGS = @LIBNDP_CFLAGS@ -LIBNDP_LIBS = @LIBNDP_LIBS@ -LIBOBJS = @LIBOBJS@ -LIBPSL_CFLAGS = @LIBPSL_CFLAGS@ -LIBPSL_LIBS = @LIBPSL_LIBS@ -LIBS = @LIBS@ -LIBSYSTEMD_CFLAGS = @LIBSYSTEMD_CFLAGS@ -LIBSYSTEMD_LIBS = @LIBSYSTEMD_LIBS@ -LIBSYSTEMD_NM_CFLAGS = @LIBSYSTEMD_NM_CFLAGS@ -LIBTEAMDCTL_CFLAGS = @LIBTEAMDCTL_CFLAGS@ -LIBTEAMDCTL_LIBS = @LIBTEAMDCTL_LIBS@ -LIBTOOL = @LIBTOOL@ -LIBUDEV_CFLAGS = @LIBUDEV_CFLAGS@ -LIBUDEV_LIBS = @LIBUDEV_LIBS@ -LIPO = @LIPO@ -LN_S = @LN_S@ -LOG_DRIVER = @LOG_DRIVER@ -LTLIBICONV = @LTLIBICONV@ -LTLIBINTL = @LTLIBINTL@ -LTLIBOBJS = @LTLIBOBJS@ -LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@ -MAINT = @MAINT@ -MAKEINFO = @MAKEINFO@ -MANIFEST_TOOL = @MANIFEST_TOOL@ -MKDIR_P = @MKDIR_P@ -MM_GLIB_CFLAGS = @MM_GLIB_CFLAGS@ -MM_GLIB_LIBS = @MM_GLIB_LIBS@ -MOBILE_BROADBAND_PROVIDER_INFO_CFLAGS = @MOBILE_BROADBAND_PROVIDER_INFO_CFLAGS@ -MOBILE_BROADBAND_PROVIDER_INFO_LIBS = @MOBILE_BROADBAND_PROVIDER_INFO_LIBS@ -MOC = @MOC@ -MODPROBE_PATH = @MODPROBE_PATH@ -MSGFMT = @MSGFMT@ -MSGMERGE = @MSGMERGE@ -MSGMERGE_FOR_MSGFMT_OPTION = @MSGMERGE_FOR_MSGFMT_OPTION@ -NEWT_CFLAGS = @NEWT_CFLAGS@ -NEWT_LIBS = @NEWT_LIBS@ -NFT_PATH = @NFT_PATH@ -NM = @NM@ -NMEDIT = @NMEDIT@ -NM_CONFIG_DEFAULT_LOGGING_AUDIT_TEXT = @NM_CONFIG_DEFAULT_LOGGING_AUDIT_TEXT@ -NM_CONFIG_DEFAULT_LOGGING_BACKEND_TEXT = @NM_CONFIG_DEFAULT_LOGGING_BACKEND_TEXT@ -NM_CONFIG_DEFAULT_MAIN_AUTH_POLKIT_TEXT = @NM_CONFIG_DEFAULT_MAIN_AUTH_POLKIT_TEXT@ -NM_CONFIG_DEFAULT_MAIN_DHCP = @NM_CONFIG_DEFAULT_MAIN_DHCP@ -NM_CONFIG_DEFAULT_MAIN_MIGRATE_IFCFG_RH_TEXT = @NM_CONFIG_DEFAULT_MAIN_MIGRATE_IFCFG_RH_TEXT@ -NM_CONFIG_DEFAULT_MAIN_RC_MANAGER = @NM_CONFIG_DEFAULT_MAIN_RC_MANAGER@ -NM_CONFIG_DEFAULT_WIFI_BACKEND_TEXT = @NM_CONFIG_DEFAULT_WIFI_BACKEND_TEXT@ -NM_DIST_VERSION = @NM_DIST_VERSION@ -NM_LOG_COMPILER = @NM_LOG_COMPILER@ -NM_MAJOR_VERSION = @NM_MAJOR_VERSION@ -NM_MICRO_VERSION = @NM_MICRO_VERSION@ -NM_MINOR_VERSION = @NM_MINOR_VERSION@ -NM_MODIFY_SYSTEM_POLICY = @NM_MODIFY_SYSTEM_POLICY@ -NM_VERSION = @NM_VERSION@ -NSS_CFLAGS = @NSS_CFLAGS@ -NSS_LIBS = @NSS_LIBS@ -OBJDUMP = @OBJDUMP@ -OBJEXT = @OBJEXT@ -OTOOL = @OTOOL@ -OTOOL64 = @OTOOL64@ -PACKAGE = @PACKAGE@ -PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ -PACKAGE_NAME = @PACKAGE_NAME@ -PACKAGE_STRING = @PACKAGE_STRING@ -PACKAGE_TARNAME = @PACKAGE_TARNAME@ -PACKAGE_URL = @PACKAGE_URL@ -PACKAGE_VERSION = @PACKAGE_VERSION@ -PATH_SEPARATOR = @PATH_SEPARATOR@ -PERL = @PERL@ -PKG_CONFIG = @PKG_CONFIG@ -PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ -PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ -POSUB = @POSUB@ -PPPD_CFLAGS = @PPPD_CFLAGS@ -PPPD_PATH = @PPPD_PATH@ -PPPD_PLUGIN_DIR = @PPPD_PLUGIN_DIR@ -PTHREAD_CC = @PTHREAD_CC@ -PTHREAD_CFLAGS = @PTHREAD_CFLAGS@ -PTHREAD_CXX = @PTHREAD_CXX@ -PTHREAD_LIBS = @PTHREAD_LIBS@ -PYTHON = @PYTHON@ -PYTHON_EXEC_PREFIX = @PYTHON_EXEC_PREFIX@ -PYTHON_PLATFORM = @PYTHON_PLATFORM@ -PYTHON_PREFIX = @PYTHON_PREFIX@ -PYTHON_VERSION = @PYTHON_VERSION@ -QT_CFLAGS = @QT_CFLAGS@ -QT_LIBS = @QT_LIBS@ -RANLIB = @RANLIB@ -READELF = @READELF@ -READLINE_LIBS = @READLINE_LIBS@ -SANITIZER_ENV = @SANITIZER_ENV@ -SANITIZER_EXEC_CFLAGS = @SANITIZER_EXEC_CFLAGS@ -SANITIZER_EXEC_LDFLAGS = @SANITIZER_EXEC_LDFLAGS@ -SANITIZER_LIB_CFLAGS = @SANITIZER_LIB_CFLAGS@ -SANITIZER_LIB_LDFLAGS = @SANITIZER_LIB_LDFLAGS@ -SED = @SED@ -SELINUX_CFLAGS = @SELINUX_CFLAGS@ -SELINUX_LIBS = @SELINUX_LIBS@ -SET_MAKE = @SET_MAKE@ -SHELL = @SHELL@ -STRIP = @STRIP@ -SYSTEMD_INHIBIT_CFLAGS = @SYSTEMD_INHIBIT_CFLAGS@ -SYSTEMD_INHIBIT_LIBS = @SYSTEMD_INHIBIT_LIBS@ -SYSTEMD_JOURNAL_CFLAGS = @SYSTEMD_JOURNAL_CFLAGS@ -SYSTEMD_JOURNAL_LIBS = @SYSTEMD_JOURNAL_LIBS@ -SYSTEMD_LOGIN_CFLAGS = @SYSTEMD_LOGIN_CFLAGS@ -SYSTEMD_LOGIN_LIBS = @SYSTEMD_LOGIN_LIBS@ -SYSTEM_CA_PATH = @SYSTEM_CA_PATH@ -UDEV_DIR = @UDEV_DIR@ -USE_NLS = @USE_NLS@ -UUID_CFLAGS = @UUID_CFLAGS@ -UUID_LIBS = @UUID_LIBS@ -VAPIGEN = @VAPIGEN@ -VAPIGEN_MAKEFILE = @VAPIGEN_MAKEFILE@ -VAPIGEN_VAPIDIR = @VAPIGEN_VAPIDIR@ -VERSION = @VERSION@ -XGETTEXT = @XGETTEXT@ -XGETTEXT_015 = @XGETTEXT_015@ -XGETTEXT_EXTRA_OPTIONS = @XGETTEXT_EXTRA_OPTIONS@ -XSLTPROC = xsltproc --xinclude --nonet -abs_builddir = @abs_builddir@ -abs_srcdir = @abs_srcdir@ -abs_top_builddir = @abs_top_builddir@ -abs_top_srcdir = @abs_top_srcdir@ -ac_ct_AR = @ac_ct_AR@ -ac_ct_CC = @ac_ct_CC@ -ac_ct_CXX = @ac_ct_CXX@ -ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ -ac_ct_NM = @ac_ct_NM@ -ac_ct_RANLIB = @ac_ct_RANLIB@ -ac_ct_READELF = @ac_ct_READELF@ -am__include = @am__include@ -am__leading_dot = @am__leading_dot@ -am__quote = @am__quote@ -am__tar = @am__tar@ -am__untar = @am__untar@ -ax_pthread_config = @ax_pthread_config@ -bindir = @bindir@ -build = @build@ -build_alias = @build_alias@ -build_cpu = @build_cpu@ -build_os = @build_os@ -build_vendor = @build_vendor@ -builddir = @builddir@ -datadir = @datadir@ -datarootdir = @datarootdir@ -docdir = @docdir@ -dvidir = @dvidir@ -exec_prefix = @exec_prefix@ -host = @host@ -host_alias = @host_alias@ -host_cpu = @host_cpu@ -host_os = @host_os@ -host_vendor = @host_vendor@ -htmldir = @htmldir@ -includedir = @includedir@ -infodir = @infodir@ -install_sh = @install_sh@ -libdir = @libdir@ -libexecdir = @libexecdir@ -localedir = @localedir@ -localedir_c = @localedir_c@ -localedir_c_make = @localedir_c_make@ -localstatedir = @localstatedir@ -mandir = @mandir@ -mkdir_p = @mkdir_p@ -nmbinary = @nmbinary@ -nmconfdir = @nmconfdir@ -nmdatadir = @nmdatadir@ -nmlibdir = @nmlibdir@ -nmrundir = @nmrundir@ -nmstatedir = @nmstatedir@ -oldincludedir = @oldincludedir@ -pdfdir = @pdfdir@ -pkgpyexecdir = @pkgpyexecdir@ -pkgpythondir = @pkgpythondir@ -prefix = @prefix@ -program_transform_name = @program_transform_name@ -psdir = @psdir@ -pyexecdir = @pyexecdir@ -pythondir = @pythondir@ -runstatedir = @runstatedir@ -sbindir = @sbindir@ -sharedstatedir = @sharedstatedir@ -srcdir = @srcdir@ -sysconfdir = @sysconfdir@ -systemdsystemunitdir = @systemdsystemunitdir@ -target = @target@ -target_alias = @target_alias@ -target_cpu = @target_cpu@ -target_os = @target_os@ -target_vendor = @target_vendor@ -top_build_prefix = @top_build_prefix@ -top_builddir = @top_builddir@ -top_srcdir = @top_srcdir@ -with_dhclient = @with_dhclient@ -with_dhcpcanon = @with_dhcpcanon@ -with_dhcpcd = @with_dhcpcd@ -with_netconfig = @with_netconfig@ -with_resolvconf = @with_resolvconf@ -with_valgrind = @with_valgrind@ -AUTOMAKE_OPTIONS = 1.7 -XMLS = $(wildcard $(top_srcdir)/introspection/nm-*.xml) -GENERATED_FILES = $(am__append_1) - -# The name of the module. -DOC_MODULE = NetworkManager - -# The top-level SGML file. -DOC_MAIN_SGML_FILE = network-manager-docs.xml -DOC_SOURCE_DIR = $(srcdir) - -# Extra options to supply to gtkdoc-mkdb -MKDB_OPTIONS = --sgml-mode --output-format=xml - -# Extra options to supply to gtkdoc-mktmpl -MKTMPL_OPTIONS = - -# Extra options to supply to gtkdoc-mkhtml -MKHTML_OPTIONS = --path="$(abs_srcdir)" - -# Files to be included in $(DOC_MAIN_SGML_FILE) -content_files = $(GENERATED_FILES) \ - dbus-org.freedesktop.NetworkManager.AccessPoint.xml \ - dbus-org.freedesktop.NetworkManager.AgentManager.xml \ - dbus-org.freedesktop.NetworkManager.Connection.Active.xml \ - dbus-org.freedesktop.NetworkManager.DHCP4Config.xml \ - dbus-org.freedesktop.NetworkManager.DHCP6Config.xml \ - dbus-org.freedesktop.NetworkManager.Device.Adsl.xml \ - dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml \ - dbus-org.freedesktop.NetworkManager.Device.Bond.xml \ - dbus-org.freedesktop.NetworkManager.Device.Bridge.xml \ - dbus-org.freedesktop.NetworkManager.Device.Dummy.xml \ - dbus-org.freedesktop.NetworkManager.Device.Generic.xml \ - dbus-org.freedesktop.NetworkManager.Device.Hsr.xml \ - dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml \ - dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml \ - dbus-org.freedesktop.NetworkManager.Device.Loopback.xml \ - dbus-org.freedesktop.NetworkManager.Device.Macsec.xml \ - dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml \ - dbus-org.freedesktop.NetworkManager.Device.Modem.xml \ - dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xml \ - dbus-org.freedesktop.NetworkManager.Device.Statistics.xml \ - dbus-org.freedesktop.NetworkManager.Device.Team.xml \ - dbus-org.freedesktop.NetworkManager.Device.Tun.xml \ - dbus-org.freedesktop.NetworkManager.Device.Veth.xml \ - dbus-org.freedesktop.NetworkManager.Device.Vlan.xml \ - dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml \ - dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml \ - dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml \ - dbus-org.freedesktop.NetworkManager.Device.Wired.xml \ - dbus-org.freedesktop.NetworkManager.Device.Wireless.xml \ - dbus-org.freedesktop.NetworkManager.Device.xml \ - dbus-org.freedesktop.NetworkManager.DnsManager.xml \ - dbus-org.freedesktop.NetworkManager.IP4Config.xml \ - dbus-org.freedesktop.NetworkManager.IP6Config.xml \ - dbus-org.freedesktop.NetworkManager.PPP.xml \ - dbus-org.freedesktop.NetworkManager.SecretAgent.xml \ - dbus-org.freedesktop.NetworkManager.Settings.Connection.xml \ - dbus-org.freedesktop.NetworkManager.Settings.xml \ - dbus-org.freedesktop.NetworkManager.VPN.Connection.xml \ - dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml \ - dbus-org.freedesktop.NetworkManager.xml \ - $(top_builddir)/src/libnm-core-public/nm-dbus-types.xml \ - $(top_builddir)/src/libnm-core-public/nm-vpn-dbus-types.xml \ - $(top_builddir)/man/nmcli.xml $(top_builddir)/man/nmtui.xml \ - $(top_builddir)/man/nm-online.xml \ - $(top_builddir)/man/nm-initrd-generator.xml \ - $(top_builddir)/man/NetworkManager.xml \ - $(top_builddir)/man/NetworkManager-dispatcher.xml \ - $(top_builddir)/man/NetworkManager.conf.xml \ - $(top_builddir)/man/NetworkManager-wait-online.service.xml \ - $(top_builddir)/man/nmcli-examples.xml \ - $(top_builddir)/man/nm-settings-dbus.xml \ - $(top_builddir)/man/nm-settings-keyfile.xml \ - $(top_builddir)/man/nm-settings-nmcli.xml version.xml $(NULL) \ - $(am__append_2) $(am__append_3) $(am__append_4) -@GTK_DOC_USE_LIBTOOL_FALSE@GTKDOC_CC = $(CC) $(INCLUDES) $(GTKDOC_DEPS_CFLAGS) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -@GTK_DOC_USE_LIBTOOL_TRUE@GTKDOC_CC = $(LIBTOOL) --tag=CC --mode=compile $(CC) $(INCLUDES) $(GTKDOC_DEPS_CFLAGS) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -@GTK_DOC_USE_LIBTOOL_FALSE@GTKDOC_LD = $(CC) $(GTKDOC_DEPS_LIBS) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -@GTK_DOC_USE_LIBTOOL_TRUE@GTKDOC_LD = $(LIBTOOL) --tag=CC --mode=link $(CC) $(GTKDOC_DEPS_LIBS) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -@GTK_DOC_USE_LIBTOOL_FALSE@GTKDOC_RUN = -@GTK_DOC_USE_LIBTOOL_TRUE@GTKDOC_RUN = $(LIBTOOL) --mode=execute - -# We set GPATH here; this gives us semantics for GNU make -# which are more like other make's VPATH, when it comes to -# whether a source that is a target of one rule is then -# searched for in VPATH/GPATH. -# -GPATH = $(srcdir) -TARGET_DIR = $(HTML_DIR)/$(DOC_MODULE) -SETUP_FILES = \ - $(content_files) \ - $(expand_content_files) \ - $(DOC_MAIN_SGML_FILE) \ - $(DOC_MODULE)-sections.txt \ - $(DOC_MODULE)-overrides.txt - -EXTRA_DIST = $(HTML_IMAGES) $(SETUP_FILES) version.xml.in \ - settings-spec.xsl meson.build $(GENERATED_FILES) $(NULL) -DOC_STAMPS = setup-build.stamp scan-build.stamp sgml-build.stamp \ - html-build.stamp pdf-build.stamp \ - sgml.stamp html.stamp pdf.stamp - -SCANOBJ_FILES = \ - $(DOC_MODULE).actions \ - $(DOC_MODULE).args \ - $(DOC_MODULE).hierarchy \ - $(DOC_MODULE).interfaces \ - $(DOC_MODULE).prerequisites \ - $(DOC_MODULE).signals - -REPORT_FILES = \ - $(DOC_MODULE)-undocumented.txt \ - $(DOC_MODULE)-undeclared.txt \ - $(DOC_MODULE)-unused.txt - -CLEANFILES = $(SCANOBJ_FILES) $(REPORT_FILES) $(DOC_STAMPS) \ - gtkdoc-check.test html/* tmpl/* xml/* \ - NetworkManager-overrides.txt NetworkManager-sections.txt \ - NetworkManager.actions settings-spec.xml $(NULL) -@GTK_DOC_BUILD_HTML_FALSE@HTML_BUILD_STAMP = -@GTK_DOC_BUILD_HTML_TRUE@HTML_BUILD_STAMP = html-build.stamp -@GTK_DOC_BUILD_PDF_FALSE@PDF_BUILD_STAMP = -@GTK_DOC_BUILD_PDF_TRUE@PDF_BUILD_STAMP = pdf-build.stamp - -#### setup #### -GTK_DOC_V_SETUP = $(GTK_DOC_V_SETUP_@AM_V@) -GTK_DOC_V_SETUP_ = $(GTK_DOC_V_SETUP_@AM_DEFAULT_V@) -GTK_DOC_V_SETUP_0 = @echo " DOC Preparing build"; - -#### scan #### -GTK_DOC_V_SCAN = $(GTK_DOC_V_SCAN_@AM_V@) -GTK_DOC_V_SCAN_ = $(GTK_DOC_V_SCAN_@AM_DEFAULT_V@) -GTK_DOC_V_SCAN_0 = @echo " DOC Scanning header files"; -GTK_DOC_V_INTROSPECT = $(GTK_DOC_V_INTROSPECT_@AM_V@) -GTK_DOC_V_INTROSPECT_ = $(GTK_DOC_V_INTROSPECT_@AM_DEFAULT_V@) -GTK_DOC_V_INTROSPECT_0 = @echo " DOC Introspecting gobjects"; - -#### xml #### -GTK_DOC_V_XML = $(GTK_DOC_V_XML_@AM_V@) -GTK_DOC_V_XML_ = $(GTK_DOC_V_XML_@AM_DEFAULT_V@) -GTK_DOC_V_XML_0 = @echo " DOC Building XML"; - -#### html #### -GTK_DOC_V_HTML = $(GTK_DOC_V_HTML_@AM_V@) -GTK_DOC_V_HTML_ = $(GTK_DOC_V_HTML_@AM_DEFAULT_V@) -GTK_DOC_V_HTML_0 = @echo " DOC Building HTML"; -GTK_DOC_V_XREF = $(GTK_DOC_V_XREF_@AM_V@) -GTK_DOC_V_XREF_ = $(GTK_DOC_V_XREF_@AM_DEFAULT_V@) -GTK_DOC_V_XREF_0 = @echo " DOC Fixing cross-references"; - -#### pdf #### -GTK_DOC_V_PDF = $(GTK_DOC_V_PDF_@AM_V@) -GTK_DOC_V_PDF_ = $(GTK_DOC_V_PDF_@AM_DEFAULT_V@) -GTK_DOC_V_PDF_0 = @echo " DOC Building PDF"; -all: all-am - -.SUFFIXES: -$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(top_srcdir)/gtk-doc.make $(am__configure_deps) - @for dep in $?; do \ - case '$(am__configure_deps)' in \ - *$$dep*) \ - ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ - && { if test -f $@; then exit 0; else break; fi; }; \ - exit 1;; \ - esac; \ - done; \ - echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign docs/api/Makefile'; \ - $(am__cd) $(top_srcdir) && \ - $(AUTOMAKE) --foreign docs/api/Makefile -Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status - @case '$?' in \ - *config.status*) \ - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ - *) \ - echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles)'; \ - cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles);; \ - esac; -$(top_srcdir)/gtk-doc.make $(am__empty): - -$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh - -$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh -$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) - cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh -$(am__aclocal_m4_deps): -version.xml: $(top_builddir)/config.status $(srcdir)/version.xml.in - cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ - -mostlyclean-libtool: - -rm -f *.lo - -clean-libtool: - -rm -rf .libs _libs -tags TAGS: - -ctags CTAGS: - -cscope cscopelist: - -distdir: $(BUILT_SOURCES) - $(MAKE) $(AM_MAKEFLAGS) distdir-am - -distdir-am: $(DISTFILES) - @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ - topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ - list='$(DISTFILES)'; \ - dist_files=`for file in $$list; do echo $$file; done | \ - sed -e "s|^$$srcdirstrip/||;t" \ - -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ - case $$dist_files in \ - */*) $(MKDIR_P) `echo "$$dist_files" | \ - sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ - sort -u` ;; \ - esac; \ - for file in $$dist_files; do \ - if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ - if test -d $$d/$$file; then \ - dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ - if test -d "$(distdir)/$$file"; then \ - find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ - fi; \ - if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ - cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ - find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ - fi; \ - cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ - else \ - test -f "$(distdir)/$$file" \ - || cp -p $$d/$$file "$(distdir)/$$file" \ - || exit 1; \ - fi; \ - done - $(MAKE) $(AM_MAKEFLAGS) \ - top_distdir="$(top_distdir)" distdir="$(distdir)" \ - dist-hook -check-am: all-am -check: check-am -@ENABLE_GTK_DOC_FALSE@all-local: -all-am: Makefile all-local -installdirs: -install: install-am -install-exec: install-exec-am -install-data: install-data-am -uninstall: uninstall-am - -install-am: all-am - @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am - -installcheck: installcheck-am -install-strip: - if test -z '$(STRIP)'; then \ - $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ - install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ - install; \ - else \ - $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ - install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ - "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ - fi -mostlyclean-generic: - -clean-generic: - -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES) - -distclean-generic: - -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) - -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) - -maintainer-clean-generic: - @echo "This command is intended for maintainers to use" - @echo "it deletes files that may require special tools to rebuild." -clean: clean-am - -clean-am: clean-generic clean-libtool clean-local mostlyclean-am - -distclean: distclean-am - -rm -f Makefile -distclean-am: clean-am distclean-generic distclean-local - -dvi: dvi-am - -dvi-am: - -html: html-am - -html-am: - -info: info-am - -info-am: - -install-data-am: install-data-local - -install-dvi: install-dvi-am - -install-dvi-am: - -install-exec-am: - -install-html: install-html-am - -install-html-am: - -install-info: install-info-am - -install-info-am: - -install-man: - -install-pdf: install-pdf-am - -install-pdf-am: - -install-ps: install-ps-am - -install-ps-am: - -installcheck-am: - -maintainer-clean: maintainer-clean-am - -rm -f Makefile -maintainer-clean-am: distclean-am maintainer-clean-generic \ - maintainer-clean-local - -mostlyclean: mostlyclean-am - -mostlyclean-am: mostlyclean-generic mostlyclean-libtool - -pdf: pdf-am - -pdf-am: - -ps: ps-am - -ps-am: - -uninstall-am: uninstall-local - -.MAKE: install-am install-strip - -.PHONY: all all-am all-local check check-am clean clean-generic \ - clean-libtool clean-local cscopelist-am ctags-am dist-hook \ - distclean distclean-generic distclean-libtool distclean-local \ - distdir dvi dvi-am html html-am info info-am install \ - install-am install-data install-data-am install-data-local \ - install-dvi install-dvi-am install-exec install-exec-am \ - install-html install-html-am install-info install-info-am \ - install-man install-pdf install-pdf-am install-ps \ - install-ps-am install-strip installcheck installcheck-am \ - installdirs maintainer-clean maintainer-clean-generic \ - maintainer-clean-local mostlyclean mostlyclean-generic \ - mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ - uninstall-am uninstall-local - -.PRECIOUS: Makefile - - -gtkdoc-check.test: Makefile - $(AM_V_GEN)echo "#!/bin/sh -e" > $@; \ - echo "$(GTKDOC_CHECK_PATH) || exit 1" >> $@; \ - chmod +x $@ - -all-gtk-doc: $(HTML_BUILD_STAMP) $(PDF_BUILD_STAMP) -.PHONY: all-gtk-doc - -@ENABLE_GTK_DOC_TRUE@all-local: all-gtk-doc - -docs: $(HTML_BUILD_STAMP) $(PDF_BUILD_STAMP) - -$(REPORT_FILES): sgml-build.stamp - -setup-build.stamp: - -$(GTK_DOC_V_SETUP)if test "$(abs_srcdir)" != "$(abs_builddir)" ; then \ - files=`echo $(SETUP_FILES) $(DOC_MODULE).types`; \ - if test "x$$files" != "x" ; then \ - for file in $$files ; do \ - destdir=`dirname $(abs_builddir)/$$file`; \ - test -d "$$destdir" || mkdir -p "$$destdir"; \ - test -f $(abs_srcdir)/$$file && \ - cp -pf $(abs_srcdir)/$$file $(abs_builddir)/$$file || true; \ - done; \ - fi; \ - fi - $(AM_V_at)touch setup-build.stamp - -scan-build.stamp: setup-build.stamp $(HFILE_GLOB) $(CFILE_GLOB) - $(GTK_DOC_V_SCAN)_source_dir='' ; \ - for i in $(DOC_SOURCE_DIR) ; do \ - _source_dir="$${_source_dir} --source-dir=$$i" ; \ - done ; \ - gtkdoc-scan --module=$(DOC_MODULE) --ignore-headers="$(IGNORE_HFILES)" $${_source_dir} $(SCAN_OPTIONS) $(EXTRA_HFILES) - $(GTK_DOC_V_INTROSPECT)if grep -l '^..*$$' $(DOC_MODULE).types > /dev/null 2>&1 ; then \ - scanobj_options=""; \ - gtkdoc-scangobj 2>&1 --help | grep >/dev/null "\-\-verbose"; \ - if test "$$?" = "0"; then \ - if test "x$(V)" = "x1"; then \ - scanobj_options="--verbose"; \ - fi; \ - fi; \ - CC="$(GTKDOC_CC)" LD="$(GTKDOC_LD)" RUN="$(GTKDOC_RUN)" CFLAGS="$(GTKDOC_CFLAGS) $(CFLAGS)" LDFLAGS="$(GTKDOC_LIBS) $(LDFLAGS)" \ - gtkdoc-scangobj $(SCANGOBJ_OPTIONS) $$scanobj_options --module=$(DOC_MODULE); \ - else \ - for i in $(SCANOBJ_FILES) ; do \ - test -f $$i || touch $$i ; \ - done \ - fi - $(AM_V_at)touch scan-build.stamp - -$(DOC_MODULE)-decl.txt $(SCANOBJ_FILES) $(DOC_MODULE)-sections.txt $(DOC_MODULE)-overrides.txt: scan-build.stamp - @true - -sgml-build.stamp: setup-build.stamp $(DOC_MODULE)-decl.txt $(SCANOBJ_FILES) $(HFILE_GLOB) $(CFILE_GLOB) $(DOC_MODULE)-sections.txt $(DOC_MODULE)-overrides.txt $(expand_content_files) xml/gtkdocentities.ent - $(GTK_DOC_V_XML)_source_dir='' ; \ - for i in $(DOC_SOURCE_DIR) ; do \ - _source_dir="$${_source_dir} --source-dir=$$i" ; \ - done ; \ - gtkdoc-mkdb --module=$(DOC_MODULE) --output-format=xml --expand-content-files="$(expand_content_files)" --main-sgml-file=$(DOC_MAIN_SGML_FILE) $${_source_dir} $(MKDB_OPTIONS) - $(AM_V_at)touch sgml-build.stamp - -sgml.stamp: sgml-build.stamp - @true - -$(DOC_MAIN_SGML_FILE): sgml-build.stamp - @true - -xml/gtkdocentities.ent: Makefile - $(GTK_DOC_V_XML)$(MKDIR_P) $(@D) && ( \ - echo ""; \ - echo ""; \ - echo ""; \ - echo ""; \ - echo ""; \ - echo ""; \ - echo ""; \ - ) > $@ - -html-build.stamp: sgml.stamp $(DOC_MAIN_SGML_FILE) $(content_files) $(expand_content_files) - $(GTK_DOC_V_HTML)rm -rf html && mkdir html && \ - mkhtml_options=""; \ - gtkdoc-mkhtml 2>&1 --help | grep >/dev/null "\-\-verbose"; \ - if test "$$?" = "0"; then \ - if test "x$(V)" = "x1"; then \ - mkhtml_options="$$mkhtml_options --verbose"; \ - fi; \ - fi; \ - gtkdoc-mkhtml 2>&1 --help | grep >/dev/null "\-\-path"; \ - if test "$$?" = "0"; then \ - mkhtml_options="$$mkhtml_options --path=\"$(abs_srcdir)\""; \ - fi; \ - cd html && gtkdoc-mkhtml $$mkhtml_options $(MKHTML_OPTIONS) $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE) - -@test "x$(HTML_IMAGES)" = "x" || \ - for file in $(HTML_IMAGES) ; do \ - test -f $(abs_srcdir)/$$file && cp $(abs_srcdir)/$$file $(abs_builddir)/html; \ - test -f $(abs_builddir)/$$file && cp $(abs_builddir)/$$file $(abs_builddir)/html; \ - test -f $$file && cp $$file $(abs_builddir)/html; \ - done; - $(GTK_DOC_V_XREF)gtkdoc-fixxref --module=$(DOC_MODULE) --module-dir=html --html-dir=$(HTML_DIR) $(FIXXREF_OPTIONS) - $(AM_V_at)touch html-build.stamp - -pdf-build.stamp: sgml.stamp $(DOC_MAIN_SGML_FILE) $(content_files) $(expand_content_files) - $(GTK_DOC_V_PDF)rm -f $(DOC_MODULE).pdf && \ - mkpdf_options=""; \ - gtkdoc-mkpdf 2>&1 --help | grep >/dev/null "\-\-verbose"; \ - if test "$$?" = "0"; then \ - if test "x$(V)" = "x1"; then \ - mkpdf_options="$$mkpdf_options --verbose"; \ - fi; \ - fi; \ - if test "x$(HTML_IMAGES)" != "x"; then \ - for img in $(HTML_IMAGES); do \ - part=`dirname $$img`; \ - echo $$mkpdf_options | grep >/dev/null "\-\-imgdir=$$part "; \ - if test $$? != 0; then \ - mkpdf_options="$$mkpdf_options --imgdir=$$part"; \ - fi; \ - done; \ - fi; \ - gtkdoc-mkpdf --path="$(abs_srcdir)" $$mkpdf_options $(DOC_MODULE) $(DOC_MAIN_SGML_FILE) $(MKPDF_OPTIONS) - $(AM_V_at)touch pdf-build.stamp - -############## - -clean-local: - @rm -f *~ *.bak - @rm -rf .libs - @if echo $(SCAN_OPTIONS) | grep -q "\-\-rebuild-types" ; then \ - rm -f $(DOC_MODULE).types; \ - fi - @if echo $(SCAN_OPTIONS) | grep -q "\-\-rebuild-sections" ; then \ - rm -f $(DOC_MODULE)-sections.txt; \ - fi - -distclean-local: - @rm -rf xml html $(REPORT_FILES) $(DOC_MODULE).pdf \ - $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt - @if test "$(abs_srcdir)" != "$(abs_builddir)" ; then \ - rm -f $(SETUP_FILES) $(DOC_MODULE).types; \ - fi - -maintainer-clean-local: - @rm -rf xml html - -install-data-local: - @installfiles=`echo $(builddir)/html/*`; \ - if test "$$installfiles" = '$(builddir)/html/*'; \ - then echo 1>&2 'Nothing to install' ; \ - else \ - if test -n "$(DOC_MODULE_VERSION)"; then \ - installdir="$(DESTDIR)$(TARGET_DIR)-$(DOC_MODULE_VERSION)"; \ - else \ - installdir="$(DESTDIR)$(TARGET_DIR)"; \ - fi; \ - $(mkinstalldirs) $${installdir} ; \ - for i in $$installfiles; do \ - echo ' $(INSTALL_DATA) '$$i ; \ - $(INSTALL_DATA) $$i $${installdir}; \ - done; \ - if test -n "$(DOC_MODULE_VERSION)"; then \ - mv -f $${installdir}/$(DOC_MODULE).devhelp2 \ - $${installdir}/$(DOC_MODULE)-$(DOC_MODULE_VERSION).devhelp2; \ - fi; \ - $(GTKDOC_REBASE) --relative --dest-dir=$(DESTDIR) --html-dir=$${installdir}; \ - fi - -uninstall-local: - @if test -n "$(DOC_MODULE_VERSION)"; then \ - installdir="$(DESTDIR)$(TARGET_DIR)-$(DOC_MODULE_VERSION)"; \ - else \ - installdir="$(DESTDIR)$(TARGET_DIR)"; \ - fi; \ - rm -rf $${installdir} - -# -# Require gtk-doc when making dist -# -@HAVE_GTK_DOC_TRUE@dist-check-gtkdoc: docs -@HAVE_GTK_DOC_FALSE@dist-check-gtkdoc: -@HAVE_GTK_DOC_FALSE@ @echo "*** gtk-doc is needed to run 'make dist'. ***" -@HAVE_GTK_DOC_FALSE@ @echo "*** gtk-doc was not found when 'configure' ran. ***" -@HAVE_GTK_DOC_FALSE@ @echo "*** please install gtk-doc and rerun 'configure'. ***" -@HAVE_GTK_DOC_FALSE@ @false - -dist-hook: dist-check-gtkdoc all-gtk-doc dist-hook-local - @mkdir $(distdir)/html - @cp ./html/* $(distdir)/html - @-cp ./$(DOC_MODULE).pdf $(distdir)/ - @-cp ./$(DOC_MODULE).types $(distdir)/ - @-cp ./$(DOC_MODULE)-sections.txt $(distdir)/ - @cd $(distdir) && rm -f $(DISTCLEANFILES) - @$(GTKDOC_REBASE) --online --relative --html-dir=$(distdir)/html - -.PHONY : dist-hook-local docs - -# workaround setup-build.stamp from gtk-doc.make, which copies -# the file as read-only. That breaks later build steps, as the -# file can no longer be written. Instead, copy the file with `cp -f` -# only. -setup-build.stamp: - -$(GTK_DOC_V_SETUP)if test "$(abs_srcdir)" != "$(abs_builddir)" ; then \ - files=`echo $(SETUP_FILES) $(DOC_MODULE).types`; \ - if test "x$$files" != "x" ; then \ - for file in $$files ; do \ - destdir=`dirname $(abs_builddir)/$$file`; \ - test -d "$$destdir" || mkdir -p "$$destdir"; \ - test -f $(abs_srcdir)/$$file && \ - ( cp -pf $(abs_srcdir)/$$file $(abs_builddir)/$$file ; \ - chmod u+w $(abs_builddir)/$$file ) || true; \ - done; \ - fi; \ - fi - $(AM_V_at)touch setup-build.stamp - -settings-spec.xml: settings-spec.xsl $(top_builddir)/man/nm-settings-docs-dbus.xml - $(AM_V_GEN) (! test -f $@ || chmod u+w $@) && xsltproc --output $@ $^ - -# Tell versions [3.59,3.63) of GNU make to not export all variables. -# Otherwise a system limit (for SysV at least) may be exceeded. -.NOEXPORT: diff --git a/docs/api/NetworkManager-overrides.txt b/docs/api/NetworkManager-overrides.txt deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/api/NetworkManager-sections.txt b/docs/api/NetworkManager-sections.txt deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml b/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml deleted file mode 100644 index 1fb52f5a..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.AccessPoint.xml +++ /dev/null @@ -1,157 +0,0 @@ - - - - org.freedesktop.NetworkManager.AccessPoint - org.freedesktop.NetworkManager.AccessPoint - org.freedesktop.NetworkManager.AccessPoint Wi-Fi Access Point. - Properties - -Flags readable u -WpaFlags readable u -RsnFlags readable u -Ssid readable ay -Frequency readable u -HwAddress readable s -Mode readable u -MaxBitrate readable u -Bandwidth readable u -Strength readable y -LastSeen readable i - - - - Description - - - - - - Property Details - - The "Flags" property - org.freedesktop.NetworkManager.AccessPoint:Flags - -Flags readable u - - -Flags describing the capabilities of the access point. - -Returns: NM80211ApFlags - - - - The "WpaFlags" property - org.freedesktop.NetworkManager.AccessPoint:WpaFlags - -WpaFlags readable u - - -Flags describing the access point's capabilities according to WPA (Wifi -Protected Access). - -Returns: NM80211ApSecurityFlags - - - - The "RsnFlags" property - org.freedesktop.NetworkManager.AccessPoint:RsnFlags - -RsnFlags readable u - - -Flags describing the access point's capabilities according to the RSN -(Robust Secure Network) protocol. - -Returns: NM80211ApSecurityFlags - - - - The "Ssid" property - org.freedesktop.NetworkManager.AccessPoint:Ssid - -Ssid readable ay - - -The Service Set Identifier identifying the access point. - - - - The "Frequency" property - org.freedesktop.NetworkManager.AccessPoint:Frequency - -Frequency readable u - - -The radio channel frequency in use by the access point, in MHz. - - - - The "HwAddress" property - org.freedesktop.NetworkManager.AccessPoint:HwAddress - -HwAddress readable s - - -The hardware address (BSSID) of the access point. - - - - The "Mode" property - org.freedesktop.NetworkManager.AccessPoint:Mode - -Mode readable u - - -Describes the operating mode of the access point. - -Returns: NM80211Mode - - - - The "MaxBitrate" property - org.freedesktop.NetworkManager.AccessPoint:MaxBitrate - -MaxBitrate readable u - - -The maximum bitrate this access point is capable of, in kilobits/second -(Kb/s). - - - - The "Bandwidth" property - org.freedesktop.NetworkManager.AccessPoint:Bandwidth - -Bandwidth readable u - - -The bandwidth announced by the access point in MHz. - - - - The "Strength" property - org.freedesktop.NetworkManager.AccessPoint:Strength - -Strength readable y - - -The current signal quality of the access point, in percent. - - - - The "LastSeen" property - org.freedesktop.NetworkManager.AccessPoint:LastSeen - -LastSeen readable i - - -The timestamp (in CLOCK_BOOTTIME seconds) for the last time the access -point was found in scan results. A value of -1 means the access point has -never been found in scan results. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.AgentManager.xml b/docs/api/dbus-org.freedesktop.NetworkManager.AgentManager.xml deleted file mode 100644 index 7a9b048d..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.AgentManager.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - org.freedesktop.NetworkManager.AgentManager - org.freedesktop.NetworkManager.AgentManager - org.freedesktop.NetworkManager.AgentManager Secret Agent Manager. - Methods - -Register (IN s identifier); -RegisterWithCapabilities (IN s identifier, - IN u capabilities); -Unregister (); - - - - Description - - - - - - Method Details - - The Register() method - org.freedesktop.NetworkManager.AgentManager.Register() - -Register (IN s identifier); - - -Called by secret Agents to register their ability to provide and save -network secrets. - - - - IN s identifier: - -Identifies this agent; only one agent in each user session may use the same identifier. Identifier formatting follows the same rules as D-Bus bus names with the exception that the ':' character is not allowed. The valid set of characters is "[A-Z][a-z][0-9]_-." and the identifier is limited in length to 255 characters with a minimum of 3 characters. An example valid identifier is 'org.gnome.nm-applet' (without quotes). - - - - - - The RegisterWithCapabilities() method - org.freedesktop.NetworkManager.AgentManager.RegisterWithCapabilities() - -RegisterWithCapabilities (IN s identifier, - IN u capabilities); - - -Like Register() but indicates agent capabilities to NetworkManager. - - - - IN s identifier: - -See the Register() method's identifier argument. - - - - IN u capabilities: - -(NMSecretAgentCapabilities) Indicates various agent capabilities to NetworkManager. - - - - - - The Unregister() method - org.freedesktop.NetworkManager.AgentManager.Unregister() - -Unregister (); - - -Called by secret Agents to notify NetworkManager that they will no longer -handle requests for network secrets. Agents are automatically unregistered -when they disconnect from D-Bus. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Connection.Active.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Connection.Active.xml deleted file mode 100644 index 1ec5d9a8..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Connection.Active.xml +++ /dev/null @@ -1,283 +0,0 @@ - - - - org.freedesktop.NetworkManager.Connection.Active - org.freedesktop.NetworkManager.Connection.Active - org.freedesktop.NetworkManager.Connection.Active Active Connection. - Signals - -StateChanged (u state, - u reason); - - - - Properties - -Connection readable o -SpecificObject readable o -Id readable s -Uuid readable s -Type readable s -Devices readable ao -State readable u -StateFlags readable u -Default readable b -Ip4Config readable o -Dhcp4Config readable o -Default6 readable b -Ip6Config readable o -Dhcp6Config readable o -Vpn readable b -Controller readable o -Master readable o - - - - Description - -Objects that implement the Connection.Active interface represent an -attempt to connect to a network using the details provided by a Connection -object. The Connection.Active object tracks the life-cycle of the -connection attempt and if successful indicates whether the connected -network is the "default" or preferred network for access. NetworkManager -has the concept of connections, which can be thought of as settings, a -profile or a configuration that can be applied on a networking device. -Such settings-connections are exposed as D-Bus object and the -active-connection expresses this relationship between device and -settings-connection. At any time a settings-connection can only be -activated on one device and vice versa. However, during activation and -deactivation multiple active-connections can reference the same device or -settings-connection as they are waiting to be activated or to be -deactivated. - - - - Signal Details - - The "StateChanged" signal - org.freedesktop.NetworkManager.Connection.Active::StateChanged - -StateChanged (u state, - u reason); - - -Emitted when the state of the active connection has changed. - - - - u state: - -(NMActiveConnectionState) The new state of the active connection. - - - - u reason: - -(NMActiveConnectionStateReason) Reason code describing the change to the new state. - - - -Since 1.8 - - - - Property Details - - The "Connection" property - org.freedesktop.NetworkManager.Connection.Active:Connection - -Connection readable o - - -The path of the connection. - - - - The "SpecificObject" property - org.freedesktop.NetworkManager.Connection.Active:SpecificObject - -SpecificObject readable o - - -A specific object associated with the active connection. This property -reflects the specific object used during connection activation, and will -not change over the lifetime of the ActiveConnection once set. - - - - The "Id" property - org.freedesktop.NetworkManager.Connection.Active:Id - -Id readable s - - -The ID of the connection, provided as a convenience so that clients do not -have to retrieve all connection details. - - - - The "Uuid" property - org.freedesktop.NetworkManager.Connection.Active:Uuid - -Uuid readable s - - -The UUID of the connection, provided as a convenience so that clients do -not have to retrieve all connection details. - - - - The "Type" property - org.freedesktop.NetworkManager.Connection.Active:Type - -Type readable s - - -The type of the connection, provided as a convenience so that clients do -not have to retrieve all connection details. - - - - The "Devices" property - org.freedesktop.NetworkManager.Connection.Active:Devices - -Devices readable ao - - -Array of object paths representing devices which are part of this active -connection. - - - - The "State" property - org.freedesktop.NetworkManager.Connection.Active:State - -State readable u - - -The state of this active connection. - -Returns: NMActiveConnectionState - - - - The "StateFlags" property - org.freedesktop.NetworkManager.Connection.Active:StateFlags - -StateFlags readable u - - -The state flags of this active connection. - -Returns: NMActivationStateFlags - - - - The "Default" property - org.freedesktop.NetworkManager.Connection.Active:Default - -Default readable b - - -Whether this active connection is the default IPv4 connection, i.e. -whether it currently owns the default IPv4 route. - - - - The "Ip4Config" property - org.freedesktop.NetworkManager.Connection.Active:Ip4Config - -Ip4Config readable o - - -Object path of the Ip4Config object describing the configuration of the -connection. Only valid when the connection is in the -NM_ACTIVE_CONNECTION_STATE_ACTIVATED state. - - - - The "Dhcp4Config" property - org.freedesktop.NetworkManager.Connection.Active:Dhcp4Config - -Dhcp4Config readable o - - -Object path of the Dhcp4Config object describing the DHCP options returned -by the DHCP server (assuming the connection used DHCP). Only valid when -the connection is in the NM_ACTIVE_CONNECTION_STATE_ACTIVATED state. - - - - The "Default6" property - org.freedesktop.NetworkManager.Connection.Active:Default6 - -Default6 readable b - - -Whether this active connection is the default IPv6 connection, i.e. -whether it currently owns the default IPv6 route. - - - - The "Ip6Config" property - org.freedesktop.NetworkManager.Connection.Active:Ip6Config - -Ip6Config readable o - - -Object path of the Ip6Config object describing the configuration of the -connection. Only valid when the connection is in the -NM_ACTIVE_CONNECTION_STATE_ACTIVATED state. - - - - The "Dhcp6Config" property - org.freedesktop.NetworkManager.Connection.Active:Dhcp6Config - -Dhcp6Config readable o - - -Object path of the Dhcp6Config object describing the DHCP options returned -by the DHCP server (assuming the connection used DHCP). Only valid when -the connection is in the NM_ACTIVE_CONNECTION_STATE_ACTIVATED state. - - - - The "Vpn" property - org.freedesktop.NetworkManager.Connection.Active:Vpn - -Vpn readable b - - -Whether this active connection is also a VPN connection. - - - - The "Controller" property - org.freedesktop.NetworkManager.Connection.Active:Controller - -Controller readable o - - -The path to the controller device if the connection is a port. This -property replaces the deprecated 'Master' property. - - - - The "Master" property - org.freedesktop.NetworkManager.Connection.Active:Master - -Master readable o - - -The path to the controller device if the connection is a port. - -DEPRECATED. This property is deprecated in favor of the 'Controller' -property since 1.44. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.DHCP4Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.DHCP4Config.xml deleted file mode 100644 index 6b879a0a..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.DHCP4Config.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - org.freedesktop.NetworkManager.DHCP4Config - org.freedesktop.NetworkManager.DHCP4Config - org.freedesktop.NetworkManager.DHCP4Config IPv4 DHCP Client State. - Properties - -Options readable a{sv} - - - - Description - -Options and configuration returned by the IPv4 DHCP server. - - - - Property Details - - The "Options" property - org.freedesktop.NetworkManager.DHCP4Config:Options - -Options readable a{sv} - - -Configuration options returned by a DHCP server, if any. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.DHCP6Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.DHCP6Config.xml deleted file mode 100644 index 9a82ff45..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.DHCP6Config.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - org.freedesktop.NetworkManager.DHCP6Config - org.freedesktop.NetworkManager.DHCP6Config - org.freedesktop.NetworkManager.DHCP6Config IPv6 DHCP Client State. - Properties - -Options readable a{sv} - - - - Description - -Options and configuration returned by the IPv6 DHCP server. - - - - Property Details - - The "Options" property - org.freedesktop.NetworkManager.DHCP6Config:Options - -Options readable a{sv} - - -Configuration options returned by a DHCP server, if any. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Adsl.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Adsl.xml deleted file mode 100644 index 7846247c..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Adsl.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Adsl - org.freedesktop.NetworkManager.Device.Adsl - org.freedesktop.NetworkManager.Device.Adsl ADSL Device. - Properties - -Carrier readable b - - - - Description - - - - - - Property Details - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Adsl:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found. - -DEPRECATED: check for the "carrier" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml deleted file mode 100644 index 689ddce7..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bluetooth.xml +++ /dev/null @@ -1,60 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Bluetooth - org.freedesktop.NetworkManager.Device.Bluetooth - org.freedesktop.NetworkManager.Device.Bluetooth Bluetooth Device. - Properties - -HwAddress readable s -Name readable s -BtCapabilities readable u - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Bluetooth:HwAddress - -HwAddress readable s - - -Bluetooth hardware address of the device. - -DEPRECATED. Use the "HwAddress" property in "org.freedesktop.NetworkManager.Device" instead which exists since version NetworkManager 1.24.0. - - - - The "Name" property - org.freedesktop.NetworkManager.Device.Bluetooth:Name - -Name readable s - - -Bluetooth name of the device. - - - - The "BtCapabilities" property - org.freedesktop.NetworkManager.Device.Bluetooth:BtCapabilities - -BtCapabilities readable u - - -Bluetooth capabilities of the device (either DUN or NAP). - -Returns: NMBluetoothCapabilities - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml deleted file mode 100644 index 43ea30eb..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bond.xml +++ /dev/null @@ -1,62 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Bond - org.freedesktop.NetworkManager.Device.Bond - org.freedesktop.NetworkManager.Device.Bond Bonding Device. - Properties - -HwAddress readable s -Carrier readable b -Slaves readable ao - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Bond:HwAddress - -HwAddress readable s - - - - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Bond:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "lower-up" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - The "Slaves" property - org.freedesktop.NetworkManager.Device.Bond:Slaves - -Slaves readable ao - - -DEPRECATED. Use the "Ports" property in -"org.freedesktop.NetworkManager.Device" instead which exists since -version NetworkManager 1.34.0. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml deleted file mode 100644 index 9bcabc1e..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Bridge.xml +++ /dev/null @@ -1,62 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Bridge - org.freedesktop.NetworkManager.Device.Bridge - org.freedesktop.NetworkManager.Device.Bridge Bridging Device. - Properties - -HwAddress readable s -Carrier readable b -Slaves readable ao - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Bridge:HwAddress - -HwAddress readable s - - - - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Bridge:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "carrier" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - The "Slaves" property - org.freedesktop.NetworkManager.Device.Bridge:Slaves - -Slaves readable ao - - -DEPRECATED. Use the "Ports" property in -"org.freedesktop.NetworkManager.Device" instead which exists since -version NetworkManager 1.34.0. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml deleted file mode 100644 index ae4e4719..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Dummy.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Dummy - org.freedesktop.NetworkManager.Device.Dummy - org.freedesktop.NetworkManager.Device.Dummy Dummy Device. - Properties - -HwAddress readable s - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Dummy:HwAddress - -HwAddress readable s - - - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml deleted file mode 100644 index a14a7199..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Generic.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Generic - org.freedesktop.NetworkManager.Device.Generic - org.freedesktop.NetworkManager.Device.Generic Unrecognized Device. - Properties - -HwAddress readable s -TypeDescription readable s - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Generic:HwAddress - -HwAddress readable s - - - - - - - The "TypeDescription" property - org.freedesktop.NetworkManager.Device.Generic:TypeDescription - -TypeDescription readable s - - -A (non-localized) description of the interface type, if known. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml deleted file mode 100644 index 7b2e75af..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Hsr.xml +++ /dev/null @@ -1,78 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Hsr - org.freedesktop.NetworkManager.Device.Hsr - org.freedesktop.NetworkManager.Device.Hsr HSR Device. - Properties - -Port1 readable o -Port2 readable o -SupervisionAddress readable s -MulticastSpec readable y -Prp readable b - - - - Description - - - - - - Property Details - - The "Port1" property - org.freedesktop.NetworkManager.Device.Hsr:Port1 - -Port1 readable o - - - - - - - The "Port2" property - org.freedesktop.NetworkManager.Device.Hsr:Port2 - -Port2 readable o - - - - - - - The "SupervisionAddress" property - org.freedesktop.NetworkManager.Device.Hsr:SupervisionAddress - -SupervisionAddress readable s - - - - - - - The "MulticastSpec" property - org.freedesktop.NetworkManager.Device.Hsr:MulticastSpec - -MulticastSpec readable y - - - - - - - The "Prp" property - org.freedesktop.NetworkManager.Device.Hsr:Prp - -Prp readable b - - - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml deleted file mode 100644 index 064bb9be..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.IPTunnel.xml +++ /dev/null @@ -1,171 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.IPTunnel - org.freedesktop.NetworkManager.Device.IPTunnel - org.freedesktop.NetworkManager.Device.IPTunnel IP Tunneling Device. - Properties - -Mode readable u -Parent readable o -Local readable s -Remote readable s -Ttl readable y -Tos readable y -PathMtuDiscovery readable b -InputKey readable s -OutputKey readable s -EncapsulationLimit readable y -FlowLabel readable u -FwMark readable u -Flags readable u - - - - Description - - - - - - Property Details - - The "Mode" property - org.freedesktop.NetworkManager.Device.IPTunnel:Mode - -Mode readable u - - -The tunneling mode. - - - - The "Parent" property - org.freedesktop.NetworkManager.Device.IPTunnel:Parent - -Parent readable o - - -The object path of the parent device. - - - - The "Local" property - org.freedesktop.NetworkManager.Device.IPTunnel:Local - -Local readable s - - -The local endpoint of the tunnel. - - - - The "Remote" property - org.freedesktop.NetworkManager.Device.IPTunnel:Remote - -Remote readable s - - -The remote endpoint of the tunnel. - - - - The "Ttl" property - org.freedesktop.NetworkManager.Device.IPTunnel:Ttl - -Ttl readable y - - -The TTL assigned to tunneled packets. 0 is a special value meaning that -packets inherit the TTL value - - - - The "Tos" property - org.freedesktop.NetworkManager.Device.IPTunnel:Tos - -Tos readable y - - -The type of service (IPv4) or traffic class (IPv6) assigned to tunneled -packets. - - - - The "PathMtuDiscovery" property - org.freedesktop.NetworkManager.Device.IPTunnel:PathMtuDiscovery - -PathMtuDiscovery readable b - - -Whether path MTU discovery is enabled on this tunnel. - - - - The "InputKey" property - org.freedesktop.NetworkManager.Device.IPTunnel:InputKey - -InputKey readable s - - -The key used for incoming packets. - - - - The "OutputKey" property - org.freedesktop.NetworkManager.Device.IPTunnel:OutputKey - -OutputKey readable s - - -The key used for outgoing packets. - - - - The "EncapsulationLimit" property - org.freedesktop.NetworkManager.Device.IPTunnel:EncapsulationLimit - -EncapsulationLimit readable y - - -How many additional levels of encapsulation are permitted to be prepended -to packets. This property applies only to IPv6 tunnels. - - - - The "FlowLabel" property - org.freedesktop.NetworkManager.Device.IPTunnel:FlowLabel - -FlowLabel readable u - - -The flow label to assign to tunnel packets. This property applies only to -IPv6 tunnels. - - - - The "FwMark" property - org.freedesktop.NetworkManager.Device.IPTunnel:FwMark - -FwMark readable u - - -The fwmark value to assign to tunnel packets. This property applies only to -VTI tunnels. - - - - The "Flags" property - org.freedesktop.NetworkManager.Device.IPTunnel:Flags - -Flags readable u - - -Tunnel flags. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml deleted file mode 100644 index 65fc978d..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Infiniband.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Infiniband - org.freedesktop.NetworkManager.Device.Infiniband - org.freedesktop.NetworkManager.Device.Infiniband Infiniband Device. - Properties - -HwAddress readable s -Carrier readable b - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Infiniband:HwAddress - -HwAddress readable s - - - - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Infiniband:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "lower-up" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml deleted file mode 100644 index b56cb95a..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Loopback.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Loopback - org.freedesktop.NetworkManager.Device.Loopback - org.freedesktop.NetworkManager.Device.Loopback Loopback Device. - Description - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macsec.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macsec.xml deleted file mode 100644 index 17b772ba..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macsec.xml +++ /dev/null @@ -1,172 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Macsec - org.freedesktop.NetworkManager.Device.Macsec - org.freedesktop.NetworkManager.Device.Macsec MACSec Device. - Properties - -Parent readable o -Sci readable t -IcvLength readable y -CipherSuite readable t -Window readable u -EncodingSa readable y -Validation readable s -Encrypt readable b -Protect readable b -IncludeSci readable b -Es readable b -Scb readable b -ReplayProtect readable b - - - - Description - - - - - - Property Details - - The "Parent" property - org.freedesktop.NetworkManager.Device.Macsec:Parent - -Parent readable o - - -The object path of the parent device. - - - - The "Sci" property - org.freedesktop.NetworkManager.Device.Macsec:Sci - -Sci readable t - - -The Secure Channel Identifier in use. - - - - The "IcvLength" property - org.freedesktop.NetworkManager.Device.Macsec:IcvLength - -IcvLength readable y - - -The length of ICV (Integrity Check Value). - - - - The "CipherSuite" property - org.freedesktop.NetworkManager.Device.Macsec:CipherSuite - -CipherSuite readable t - - -The set of cryptographic algorithms in use -(e.g. 0x0080020001000001 for GCM-AES-128). - - - - The "Window" property - org.freedesktop.NetworkManager.Device.Macsec:Window - -Window readable u - - -The size of the replay window. - - - - The "EncodingSa" property - org.freedesktop.NetworkManager.Device.Macsec:EncodingSa - -EncodingSa readable y - - -The value of the Association Number (0..3) for the Security -Association in use. - - - - The "Validation" property - org.freedesktop.NetworkManager.Device.Macsec:Validation - -Validation readable s - - -The validation mode for incoming packets (strict, check, -disabled). - - - - The "Encrypt" property - org.freedesktop.NetworkManager.Device.Macsec:Encrypt - -Encrypt readable b - - -Whether encryption of transmitted frames is enabled. - - - - The "Protect" property - org.freedesktop.NetworkManager.Device.Macsec:Protect - -Protect readable b - - -Whether protection of transmitted frames is enabled. - - - - The "IncludeSci" property - org.freedesktop.NetworkManager.Device.Macsec:IncludeSci - -IncludeSci readable b - - -Whether the SCI is always included in SecTAG for transmitted -frames. - - - - The "Es" property - org.freedesktop.NetworkManager.Device.Macsec:Es - -Es readable b - - -Whether the ES (End station) bit is enabled in SecTAG for -transmitted frames. - - - - The "Scb" property - org.freedesktop.NetworkManager.Device.Macsec:Scb - -Scb readable b - - -Whether the SCB (Single Copy Broadcast) bit is enabled in -SecTAG for transmitted frames. - - - - The "ReplayProtect" property - org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect - -ReplayProtect readable b - - -Whether replay protection is enabled. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml deleted file mode 100644 index bec10ff1..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Macvlan.xml +++ /dev/null @@ -1,67 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Macvlan - org.freedesktop.NetworkManager.Device.Macvlan - org.freedesktop.NetworkManager.Device.Macvlan MAC VLAN Device. - Properties - -Parent readable o -Mode readable s -NoPromisc readable b -Tap readable b - - - - Description - - - - - - Property Details - - The "Parent" property - org.freedesktop.NetworkManager.Device.Macvlan:Parent - -Parent readable o - - -The object path of the parent device. - - - - The "Mode" property - org.freedesktop.NetworkManager.Device.Macvlan:Mode - -Mode readable s - - -The macvlan mode, one of "private", "vepa", "bridge", or "passthru". - - - - The "NoPromisc" property - org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc - -NoPromisc readable b - - -Whether the device is blocked from going into promiscuous mode. - - - - The "Tap" property - org.freedesktop.NetworkManager.Device.Macvlan:Tap - -Tap readable b - - -Whether the device is a macvtap. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Modem.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Modem.xml deleted file mode 100644 index 49c4e009..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Modem.xml +++ /dev/null @@ -1,92 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Modem - org.freedesktop.NetworkManager.Device.Modem - org.freedesktop.NetworkManager.Device.Modem Modem Device. - Properties - -ModemCapabilities readable u -CurrentCapabilities readable u -DeviceId readable s -OperatorCode readable s -Apn readable s - - - - Description - - - - - - Property Details - - The "ModemCapabilities" property - org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities - -ModemCapabilities readable u - - -The generic family of access technologies the modem supports. Not all -capabilities are available at the same time however; some modems require a -firmware reload or other reinitialization to switch between eg CDMA/EVDO -and GSM/UMTS. - -Returns: NMDeviceModemCapabilities - - - - The "CurrentCapabilities" property - org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities - -CurrentCapabilities readable u - - -The generic family of access technologies the modem currently supports -without a firmware reload or reinitialization. - -Returns: NMDeviceModemCapabilities - - - - The "DeviceId" property - org.freedesktop.NetworkManager.Device.Modem:DeviceId - -DeviceId readable s - - -An identifier used by the modem backend (ModemManager) that aims to -uniquely identify the a device. Can be used to match a connection to a -particular device. - -Since 1.20 - - - The "OperatorCode" property - org.freedesktop.NetworkManager.Device.Modem:OperatorCode - -OperatorCode readable s - - -The MCC and MNC (concatenated) of the network the modem is connected to. -Blank if disconnected or not a 3GPP modem. - -Since 1.20 - - - The "Apn" property - org.freedesktop.NetworkManager.Device.Modem:Apn - -Apn readable s - - -The access point name the modem is connected to. Blank if disconnected. - -Since 1.20 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xml deleted file mode 100644 index 8fc2d33f..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.OlpcMesh.xml +++ /dev/null @@ -1,58 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.OlpcMesh - org.freedesktop.NetworkManager.Device.OlpcMesh - org.freedesktop.NetworkManager.Device.OlpcMesh OLPC Wireless Mesh Device. - Properties - -HwAddress readable s -Companion readable o -ActiveChannel readable u - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress - -HwAddress readable s - - -The hardware address of the device. - -DEPRECATED. Use the "HwAddress" property in "org.freedesktop.NetworkManager.Device" instead which exists since version NetworkManager 1.24.0. - - - - The "Companion" property - org.freedesktop.NetworkManager.Device.OlpcMesh:Companion - -Companion readable o - - -The object path of the companion device. - - - - The "ActiveChannel" property - org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel - -ActiveChannel readable u - - -The currently active channel. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Statistics.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Statistics.xml deleted file mode 100644 index 97fa4586..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Statistics.xml +++ /dev/null @@ -1,59 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Statistics - org.freedesktop.NetworkManager.Device.Statistics - org.freedesktop.NetworkManager.Device.Statistics Device Statistic Counters. - Properties - -RefreshRateMs readwrite u -TxBytes readable t -RxBytes readable t - - - - Description - - - - - - Property Details - - The "RefreshRateMs" property - org.freedesktop.NetworkManager.Device.Statistics:RefreshRateMs - -RefreshRateMs readwrite u - - -Refresh rate of the rest of properties of this interface. The properties -are guaranteed to be refreshed each RefreshRateMs milliseconds in case -the underlying counter has changed too. -If zero, there is no guaranteed refresh rate of the properties. - - - - The "TxBytes" property - org.freedesktop.NetworkManager.Device.Statistics:TxBytes - -TxBytes readable t - - -Number of transmitted bytes - - - - The "RxBytes" property - org.freedesktop.NetworkManager.Device.Statistics:RxBytes - -RxBytes readable t - - -Number of received bytes - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml deleted file mode 100644 index f8d0bd08..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Team.xml +++ /dev/null @@ -1,73 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Team - org.freedesktop.NetworkManager.Device.Team - org.freedesktop.NetworkManager.Device.Team Teaming Device. - Properties - -HwAddress readable s -Carrier readable b -Slaves readable ao -Config readable s - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Team:HwAddress - -HwAddress readable s - - - - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Team:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "lower-up" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - The "Slaves" property - org.freedesktop.NetworkManager.Device.Team:Slaves - -Slaves readable ao - - -DEPRECATED. Use the "Ports" property in -"org.freedesktop.NetworkManager.Device" instead which exists since -version NetworkManager 1.34.0. - - - - The "Config" property - org.freedesktop.NetworkManager.Device.Team:Config - -Config readable s - - -The JSON configuration currently applied on the device. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Tun.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Tun.xml deleted file mode 100644 index 9e447e6d..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Tun.xml +++ /dev/null @@ -1,103 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Tun - org.freedesktop.NetworkManager.Device.Tun - org.freedesktop.NetworkManager.Device.Tun Userspace Tunneling Device. - Properties - -Owner readable x -Group readable x -Mode readable s -NoPi readable b -VnetHdr readable b -MultiQueue readable b -HwAddress readable s - - - - Description - - - - - - Property Details - - The "Owner" property - org.freedesktop.NetworkManager.Device.Tun:Owner - -Owner readable x - - -The uid of the tunnel owner, or -1 if it has no owner. - - - - The "Group" property - org.freedesktop.NetworkManager.Device.Tun:Group - -Group readable x - - -The gid of the tunnel group, or -1 if it has no owner. - - - - The "Mode" property - org.freedesktop.NetworkManager.Device.Tun:Mode - -Mode readable s - - -The tunnel mode, either "tun" or "tap". - - - - The "NoPi" property - org.freedesktop.NetworkManager.Device.Tun:NoPi - -NoPi readable b - - -The tunnel's "TUN_NO_PI" flag; true if no protocol info is prepended to -the tunnel packets. - - - - The "VnetHdr" property - org.freedesktop.NetworkManager.Device.Tun:VnetHdr - -VnetHdr readable b - - -The tunnel's "TUN_VNET_HDR" flag; true if the tunnel packets include a -virtio network header. - - - - The "MultiQueue" property - org.freedesktop.NetworkManager.Device.Tun:MultiQueue - -MultiQueue readable b - - -The tunnel's "TUN_TAP_MQ" flag; true if callers can connect to the tap -device multiple times, for multiple send/receive queues. - - - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Tun:HwAddress - -HwAddress readable s - - - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Veth.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Veth.xml deleted file mode 100644 index fba9ac92..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Veth.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Veth - org.freedesktop.NetworkManager.Device.Veth - org.freedesktop.NetworkManager.Device.Veth Virtual Ethernet Device. - Properties - -Peer readable o - - - - Description - - - - - - Property Details - - The "Peer" property - org.freedesktop.NetworkManager.Device.Veth:Peer - -Peer readable o - - -The object path of the device's peer. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vlan.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vlan.xml deleted file mode 100644 index 964640e1..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vlan.xml +++ /dev/null @@ -1,71 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Vlan - org.freedesktop.NetworkManager.Device.Vlan - org.freedesktop.NetworkManager.Device.Vlan Virtual LAN Device. - Properties - -HwAddress readable s -Carrier readable b -Parent readable o -VlanId readable u - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Vlan:HwAddress - -HwAddress readable s - - - - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Vlan:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "carrier" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - The "Parent" property - org.freedesktop.NetworkManager.Device.Vlan:Parent - -Parent readable o - - -Object path of the parent device of this VLAN device. - - - - The "VlanId" property - org.freedesktop.NetworkManager.Device.Vlan:VlanId - -VlanId readable u - - -The VLAN ID of this VLAN interface. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml deleted file mode 100644 index 9a00720c..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Vxlan.xml +++ /dev/null @@ -1,217 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Vxlan - org.freedesktop.NetworkManager.Device.Vxlan - org.freedesktop.NetworkManager.Device.Vxlan VXLAN Device. - Properties - -Parent readable o -HwAddress readable s -Id readable u -Group readable s -Local readable s -Tos readable y -Ttl readable y -Learning readable b -Ageing readable u -Limit readable u -DstPort readable q -SrcPortMin readable q -SrcPortMax readable q -Proxy readable b -Rsc readable b -L2miss readable b -L3miss readable b - - - - Description - - - - - - Property Details - - The "Parent" property - org.freedesktop.NetworkManager.Device.Vxlan:Parent - -Parent readable o - - -The object path of the parent device (if the VXLAN is not purely internal -to this host). - - - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Vxlan:HwAddress - -HwAddress readable s - - - - - - - The "Id" property - org.freedesktop.NetworkManager.Device.Vxlan:Id - -Id readable u - - -The VXLAN Network Identifier (VNI). - - - - The "Group" property - org.freedesktop.NetworkManager.Device.Vxlan:Group - -Group readable s - - -The IP (v4 or v6) multicast group used to communicate with other physical -hosts on this VXLAN. - - - - The "Local" property - org.freedesktop.NetworkManager.Device.Vxlan:Local - -Local readable s - - -The local IPv4 or IPv6 address to use when sending VXLAN packets to other -physical hosts. - - - - The "Tos" property - org.freedesktop.NetworkManager.Device.Vxlan:Tos - -Tos readable y - - -The value to use in the IP ToS field for VXLAN packets sent to other -physical hosts. - - - - The "Ttl" property - org.freedesktop.NetworkManager.Device.Vxlan:Ttl - -Ttl readable y - - -The value to use in the IP TTL field for VXLAN packets sent to other -physical hosts. - - - - The "Learning" property - org.freedesktop.NetworkManager.Device.Vxlan:Learning - -Learning readable b - - -True if the VXLAN dynamically learns remote IP addresses. - - - - The "Ageing" property - org.freedesktop.NetworkManager.Device.Vxlan:Ageing - -Ageing readable u - - -The interval in seconds at which the kernel purges stale cached addresses. - - - - The "Limit" property - org.freedesktop.NetworkManager.Device.Vxlan:Limit - -Limit readable u - - -The maximum number of entries that can be added to the VXLAN's forwarding -table. - - - - The "DstPort" property - org.freedesktop.NetworkManager.Device.Vxlan:DstPort - -DstPort readable q - - -Destination port for outgoing VXLAN packets. - - - - The "SrcPortMin" property - org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin - -SrcPortMin readable q - - -The lowest source port number to use for outgoing VXLAN packets. - - - - The "SrcPortMax" property - org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax - -SrcPortMax readable q - - -The highest source port number to use for outgoing VXLAN packets. - - - - The "Proxy" property - org.freedesktop.NetworkManager.Device.Vxlan:Proxy - -Proxy readable b - - -True if the VXLAN is implementing DOVE ARP proxying for remote clients. - - - - The "Rsc" property - org.freedesktop.NetworkManager.Device.Vxlan:Rsc - -Rsc readable b - - -True if the VXLAN is implementing DOVE route short-circuiting of known -remote IP addresses. - - - - The "L2miss" property - org.freedesktop.NetworkManager.Device.Vxlan:L2miss - -L2miss readable b - - -True if the VXLAN will emit netlink notifications of L2 switch misses. - - - - The "L3miss" property - org.freedesktop.NetworkManager.Device.Vxlan:L3miss - -L3miss readable b - - -True if the VXLAN will emit netlink notifications of L3 switch misses. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml deleted file mode 100644 index c0f30afd..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.WifiP2P.xml +++ /dev/null @@ -1,148 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.WifiP2P - org.freedesktop.NetworkManager.Device.WifiP2P - org.freedesktop.NetworkManager.Device.WifiP2P Wi-Fi P2P Device. - Methods - -StartFind (IN a{sv} options); -StopFind (); - - - - Signals - -PeerAdded (o peer); -PeerRemoved (o peer); - - - - Properties - -HwAddress readable s -Peers readable ao - - - - Description - - - - Since 1.16 - - - Method Details - - The StartFind() method - org.freedesktop.NetworkManager.Device.WifiP2P.StartFind() - -StartFind (IN a{sv} options); - - -Start a find operation for Wi-Fi P2P peers. - -The options argument accepts the following keys: - - - - i timeout: - Timeout value in the range of 1-600 seconds. - The default is 30 seconds. - - - - - - IN a{sv} options: - -Options of find. - - - -Since 1.16 - - - The StopFind() method - org.freedesktop.NetworkManager.Device.WifiP2P.StopFind() - -StopFind (); - - -Stop an ongoing find operation again. - -Since 1.16 - - - - Signal Details - - The "PeerAdded" signal - org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded - -PeerAdded (o peer); - - -Emitted when a new Wi-Fi P2P peer is found by the device. - - - - o peer: - -The object path of the newly found access point. - - - -Since 1.16 - - - The "PeerRemoved" signal - org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved - -PeerRemoved (o peer); - - -Emitted when a Wi-Fi P2P peer disappears from view of the device. - - - - o peer: - -The object path of the Wi-Fi P2P peer that has disappeared. - - - -Since 1.16 - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress - -HwAddress readable s - - -The active hardware address of the device. - -DEPRECATED. Use the "HwAddress" property in "org.freedesktop.NetworkManager.Device" instead which exists since version NetworkManager 1.24.0. - -Since 1.16 - - - The "Peers" property - org.freedesktop.NetworkManager.Device.WifiP2P:Peers - -Peers readable ao - - -List of object paths of peers visible to this Wi-Fi P2P device. - -Since 1.16 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml deleted file mode 100644 index 3a754296..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.WireGuard.xml +++ /dev/null @@ -1,57 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.WireGuard - org.freedesktop.NetworkManager.Device.WireGuard - org.freedesktop.NetworkManager.Device.WireGuard WireGuard Device. - Properties - -PublicKey readable ay -ListenPort readable q -FwMark readable u - - - - Description - - - - - - Property Details - - The "PublicKey" property - org.freedesktop.NetworkManager.Device.WireGuard:PublicKey - -PublicKey readable ay - - -32-byte public WireGuard key. - - - - The "ListenPort" property - org.freedesktop.NetworkManager.Device.WireGuard:ListenPort - -ListenPort readable q - - -Local UDP listening port. - - - - The "FwMark" property - org.freedesktop.NetworkManager.Device.WireGuard:FwMark - -FwMark readable u - - -Optional 32-bit mark used to set routing policy for outgoing encrypted packets. -See: ip-rule(8) - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wired.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wired.xml deleted file mode 100644 index 320300db..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wired.xml +++ /dev/null @@ -1,84 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Wired - org.freedesktop.NetworkManager.Device.Wired - org.freedesktop.NetworkManager.Device.Wired Wired Ethernet Device. - Properties - -HwAddress readable s -PermHwAddress readable s -Speed readable u -S390Subchannels readable as -Carrier readable b - - - - Description - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Wired:HwAddress - -HwAddress readable s - - -Active hardware address of the device. - -DEPRECATED. Use the "HwAddress" property in "org.freedesktop.NetworkManager.Device" instead which exists since version NetworkManager 1.24.0. - - - - The "PermHwAddress" property - org.freedesktop.NetworkManager.Device.Wired:PermHwAddress - -PermHwAddress readable s - - -Permanent hardware address of the device. - - - - The "Speed" property - org.freedesktop.NetworkManager.Device.Wired:Speed - -Speed readable u - - -Design speed of the device, in megabits/second (Mb/s). - - - - The "S390Subchannels" property - org.freedesktop.NetworkManager.Device.Wired:S390Subchannels - -S390Subchannels readable as - - -Array of S/390 subchannels for S/390 or z/Architecture devices. - - - - The "Carrier" property - org.freedesktop.NetworkManager.Device.Wired:Carrier - -Carrier readable b - - -Indicates whether the physical carrier is found (e.g. whether a cable is -plugged in or not). - -DEPRECATED: check for the "carrier" flag in the "InterfaceFlags" -property on the "org.freedesktop.NetworkManager.Device" interface. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wireless.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wireless.xml deleted file mode 100644 index 8a2e6740..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.Wireless.xml +++ /dev/null @@ -1,235 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device.Wireless - org.freedesktop.NetworkManager.Device.Wireless - org.freedesktop.NetworkManager.Device.Wireless Wi-Fi Device. - Methods - -GetAccessPoints (OUT ao access_points); -GetAllAccessPoints (OUT ao access_points); -RequestScan (IN a{sv} options); - - - - Signals - -AccessPointAdded (o access_point); -AccessPointRemoved (o access_point); - - - - Properties - -HwAddress readable s -PermHwAddress readable s -Mode readable u -Bitrate readable u -AccessPoints readable ao -ActiveAccessPoint readable o -WirelessCapabilities readable u -LastScan readable x - - - - Description - - - - - - Method Details - - The GetAccessPoints() method - org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints() - -GetAccessPoints (OUT ao access_points); - - -DEPRECATED. Get the list of access points visible to this device. Note -that this list does not include access points which hide their SSID. To -retrieve a list of all access points (including hidden ones) use the -GetAllAccessPoints() method. - - - - OUT ao access_points: - -List of access point object paths. - - - - - - The GetAllAccessPoints() method - org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints() - -GetAllAccessPoints (OUT ao access_points); - - -Get the list of all access points visible to this device, including hidden -ones for which the SSID is not yet known. - - - - OUT ao access_points: - -List of access point object paths. - - - - - - The RequestScan() method - org.freedesktop.NetworkManager.Device.Wireless.RequestScan() - -RequestScan (IN a{sv} options); - - -Request the device to scan. To know when the scan is finished, use the "PropertiesChanged" signal from "org.freedesktop.DBus.Properties" to listen to changes to the "LastScan" property. - - - - IN a{sv} options: - -Options of scan. Currently, 'ssids' option with value of "aay" type is supported. - - - - - - - Signal Details - - The "AccessPointAdded" signal - org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded - -AccessPointAdded (o access_point); - - -Emitted when a new access point is found by the device. - - - - o access_point: - -The object path of the newly found access point. - - - - - - The "AccessPointRemoved" signal - org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved - -AccessPointRemoved (o access_point); - - -Emitted when an access point disappears from view of the device. - - - - o access_point: - -The object path of the access point that has disappeared. - - - - - - - Property Details - - The "HwAddress" property - org.freedesktop.NetworkManager.Device.Wireless:HwAddress - -HwAddress readable s - - -The active hardware address of the device. - -DEPRECATED. Use the "HwAddress" property in "org.freedesktop.NetworkManager.Device" instead which exists since version NetworkManager 1.24.0. - - - - The "PermHwAddress" property - org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress - -PermHwAddress readable s - - -The permanent hardware address of the device. - - - - The "Mode" property - org.freedesktop.NetworkManager.Device.Wireless:Mode - -Mode readable u - - -The operating mode of the wireless device. - -Returns: NM80211Mode - - - - The "Bitrate" property - org.freedesktop.NetworkManager.Device.Wireless:Bitrate - -Bitrate readable u - - -The bit rate currently used by the wireless device, in kilobits/second -(Kb/s). - - - - The "AccessPoints" property - org.freedesktop.NetworkManager.Device.Wireless:AccessPoints - -AccessPoints readable ao - - -List of object paths of access point visible to this wireless device. - - - - The "ActiveAccessPoint" property - org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint - -ActiveAccessPoint readable o - - -Object path of the access point currently used by the wireless device. - - - - The "WirelessCapabilities" property - org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities - -WirelessCapabilities readable u - - -The capabilities of the wireless device. - -Returns: NMDeviceWifiCapabilities - - - - The "LastScan" property - org.freedesktop.NetworkManager.Device.Wireless:LastScan - -LastScan readable x - - -The timestamp (in CLOCK_BOOTTIME milliseconds) for the last finished network scan. -A value of -1 means the device never scanned for access points. - -Since 1.12 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml deleted file mode 100644 index 96ef9a15..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml +++ /dev/null @@ -1,636 +0,0 @@ - - - - org.freedesktop.NetworkManager.Device - org.freedesktop.NetworkManager.Device - org.freedesktop.NetworkManager.Device Device. - Methods - -Reapply (IN a{sa{sv}} connection, - IN t version_id, - IN u flags); -GetAppliedConnection (IN u flags, - OUT a{sa{sv}} connection, - OUT t version_id); -Disconnect (); -Delete (); - - - - Signals - -StateChanged (u new_state, - u old_state, - u reason); - - - - Properties - -Udi readable s -Path readable s -Interface readable s -IpInterface readable s -Driver readable s -DriverVersion readable s -FirmwareVersion readable s -Capabilities readable u -Ip4Address readable u -State readable u -StateReason readable (uu) -ActiveConnection readable o -Ip4Config readable o -Dhcp4Config readable o -Ip6Config readable o -Dhcp6Config readable o -Managed readwrite b -Autoconnect readwrite b -FirmwareMissing readable b -NmPluginMissing readable b -DeviceType readable u -AvailableConnections readable ao -PhysicalPortId readable s -Mtu readable u -Metered readable u -LldpNeighbors readable aa{sv} -Real readable b -Ip4Connectivity readable u -Ip6Connectivity readable u -InterfaceFlags readable u -HwAddress readable s -Ports readable ao - - - - Description - - - - - - Method Details - - The Reapply() method - org.freedesktop.NetworkManager.Device.Reapply() - -Reapply (IN a{sa{sv}} connection, - IN t version_id, - IN u flags); - - -Attempts to update the configuration of a device without deactivating it. -NetworkManager has the concept of connections, which are profiles that -contain the configuration for a networking device. Those connections are -exposed via D-Bus as individual objects that can be created, modified and -deleted. When activating such a settings-connection on a device, the -settings-connection is cloned to become an applied-connection and used to -configure the device (see GetAppliedConnection). Subsequent modification -of the settings-connection don't propagate automatically to the device's -applied-connection (with exception of the firewall-zone and the metered -property). For the changes to take effect, you can either re-activate the -settings-connection, or call Reapply. The Reapply call allows you to -directly update the applied-connection and reconfigure the device. Reapply -can also be useful if the currently applied-connection is equal to the -connection that is about to be reapplied. This allows to reconfigure the -device and revert external changes like removing or adding an IP address -(which NetworkManager doesn't revert automatically because it is assumed -that the user made these changes intentionally outside of NetworkManager). -Reapply can make the applied-connection different from the -settings-connection, just like updating the settings-connection can make -them different. - -Since 1.42, "preserve-external-ip" flag (0x1) is supported to not remove -externally added IP addresses and routes on the device during reapply. - - - - IN a{sa{sv}} connection: - -The optional connection settings that will be reapplied on the device. If empty, the currently active settings-connection will be used. The connection cannot arbitrarily differ from the current applied-connection otherwise the call will fail. Only certain changes are supported, like adding or removing IP addresses. - - - - IN t version_id: - -If non-zero, the current version id of the applied-connection must match. The current version id can be retrieved via GetAppliedConnection. This optional argument allows to catch concurrent modifications between the GetAppliedConnection call and Reapply. - - - - IN u flags: - -Flags which would modify the behavior of the Reapply call. Invalid flags are rejected. - - - - - - The GetAppliedConnection() method - org.freedesktop.NetworkManager.Device.GetAppliedConnection() - -GetAppliedConnection (IN u flags, - OUT a{sa{sv}} connection, - OUT t version_id); - - -Get the currently applied connection on the device. This is a snapshot of -the last activated connection on the device, that is the configuration -that is currently applied on the device. Usually this is the same as -GetSettings of the referenced settings connection. However, it can differ -if the settings connection was subsequently modified or the applied -connection was modified by Reapply. The applied connection is set when -activating a device or when calling Reapply. - - - - IN u flags: - -Flags which would modify the behavior of the GetAppliedConnection call. There are no flags defined currently and the users should use the value of 0. - - - - OUT a{sa{sv}} connection: - -The effective connection settings that the connection has currently applied. - - - - OUT t version_id: - -The version-id of the currently applied connection. This can be specified during Reapply to avoid races where you first fetch the applied connection, modify it and try to reapply it. If the applied connection is modified in the meantime, the version_id gets incremented and Reapply will fail. - - - - - - The Disconnect() method - org.freedesktop.NetworkManager.Device.Disconnect() - -Disconnect (); - - -Disconnects a device and prevents the device from automatically activating -further connections without user intervention. - - - - The Delete() method - org.freedesktop.NetworkManager.Device.Delete() - -Delete (); - - -Deletes a software device from NetworkManager and removes the interface -from the system. The method returns an error when called for a hardware -device. - - - - - Signal Details - - The "StateChanged" signal - org.freedesktop.NetworkManager.Device::StateChanged - -StateChanged (u new_state, - u old_state, - u reason); - - - - - - - u new_state: - -(NMDeviceState) The new state of the device. - - - - u old_state: - -(NMDeviceState) The previous state of the device. - - - - u reason: - -(NMDeviceStateReason) A reason for the state transition. - - - - - - - Property Details - - The "Udi" property - org.freedesktop.NetworkManager.Device:Udi - -Udi readable s - - -Operating-system specific transient device hardware identifier. This is an -opaque string representing the underlying hardware for the device, and -shouldn't be used to keep track of individual devices. For some device -types (Bluetooth, Modems) it is an identifier used by the hardware service -(ie bluez or ModemManager) to refer to that device, and client programs -use it get additional information from those services which NM does not -provide. The Udi is not guaranteed to be consistent across reboots or -hotplugs of the hardware. If you're looking for a way to uniquely track -each device in your application, use the object path. If you're looking -for a way to track a specific piece of hardware across reboot or hotplug, -use a MAC address or USB serial number. - -Note that non-UTF-8 characters are backslash escaped. Use g_strcompress() -to obtain the true (non-UTF-8) string. - - - - The "Path" property - org.freedesktop.NetworkManager.Device:Path - -Path readable s - - -The path of the device as exposed by the udev property ID_PATH. - -Note that non-UTF-8 characters are backslash escaped. Use g_strcompress() -to obtain the true (non-UTF-8) string. - - - - The "Interface" property - org.freedesktop.NetworkManager.Device:Interface - -Interface readable s - - -The name of the device's control (and often data) interface. -Note that non UTF-8 characters are backslash escaped, so the -resulting name may be longer then 15 characters. Use g_strcompress() -to revert the escaping. - - - - The "IpInterface" property - org.freedesktop.NetworkManager.Device:IpInterface - -IpInterface readable s - - -The name of the device's data interface when available. This property may -not refer to the actual data interface until the device has successfully -established a data connection, indicated by the device's State becoming -ACTIVATED. -Note that non UTF-8 characters are backslash escaped, so the -resulting name may be longer then 15 characters. Use g_strcompress() -to revert the escaping. - - - - The "Driver" property - org.freedesktop.NetworkManager.Device:Driver - -Driver readable s - - -The driver handling the device. -Non-UTF-8 sequences are backslash escaped. Use g_strcompress() -to revert. - - - - The "DriverVersion" property - org.freedesktop.NetworkManager.Device:DriverVersion - -DriverVersion readable s - - -The version of the driver handling the device. -Non-UTF-8 sequences are backslash escaped. Use g_strcompress() -to revert. - - - - The "FirmwareVersion" property - org.freedesktop.NetworkManager.Device:FirmwareVersion - -FirmwareVersion readable s - - -The firmware version for the device. -Non-UTF-8 sequences are backslash escaped. Use g_strcompress() -to revert. - - - - The "Capabilities" property - org.freedesktop.NetworkManager.Device:Capabilities - -Capabilities readable u - - -Flags describing the capabilities of the device. - -Returns: NMDeviceCapabilities - - - - The "Ip4Address" property - org.freedesktop.NetworkManager.Device:Ip4Address - -Ip4Address readable u - - -DEPRECATED; use the 'Addresses' property of the 'Ip4Config' object -instead. This property always returns 0.0.0.0 (numeric 0) as address. - - - - The "State" property - org.freedesktop.NetworkManager.Device:State - -State readable u - - -The current state of the device. - -Returns: NMDeviceState - - - - The "StateReason" property - org.freedesktop.NetworkManager.Device:StateReason - -StateReason readable (uu) - - -The current state and reason for changing to that state. - -Returns: A tuple of NMDeviceState and NMDeviceStateReason. - - - - The "ActiveConnection" property - org.freedesktop.NetworkManager.Device:ActiveConnection - -ActiveConnection readable o - - -Object path of an ActiveConnection object that "owns" this device during -activation. The ActiveConnection object tracks the life-cycle of a -connection to a specific network and implements the -org.freedesktop.NetworkManager.Connection.Active D-Bus interface. - - - - The "Ip4Config" property - org.freedesktop.NetworkManager.Device:Ip4Config - -Ip4Config readable o - - -Object path of the Ip4Config object describing the configuration of the -device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED -state. - - - - The "Dhcp4Config" property - org.freedesktop.NetworkManager.Device:Dhcp4Config - -Dhcp4Config readable o - - -Object path of the Dhcp4Config object describing the DHCP options returned -by the DHCP server. Only valid when the device is in the -NM_DEVICE_STATE_ACTIVATED state. - - - - The "Ip6Config" property - org.freedesktop.NetworkManager.Device:Ip6Config - -Ip6Config readable o - - -Object path of the Ip6Config object describing the configuration of the -device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED -state. - - - - The "Dhcp6Config" property - org.freedesktop.NetworkManager.Device:Dhcp6Config - -Dhcp6Config readable o - - -Object path of the Dhcp6Config object describing the DHCP options returned -by the DHCP server. Only valid when the device is in the -NM_DEVICE_STATE_ACTIVATED state. - - - - The "Managed" property - org.freedesktop.NetworkManager.Device:Managed - -Managed readwrite b - - -Whether or not this device is managed by NetworkManager. Setting this -property has a similar effect to configuring the device as unmanaged via -the keyfile.unmanaged-devices setting in NetworkManager.conf. Changes to -this value are not persistent and lost after NetworkManager restart. - - - - The "Autoconnect" property - org.freedesktop.NetworkManager.Device:Autoconnect - -Autoconnect readwrite b - - -If TRUE, indicates the device is allowed to autoconnect. If FALSE, manual -intervention is required before the device will automatically connect to a -known network, such as activating a connection using the device, or -setting this property to TRUE. This property cannot be set to TRUE for -default-unmanaged devices, since they never autoconnect. - - - - The "FirmwareMissing" property - org.freedesktop.NetworkManager.Device:FirmwareMissing - -FirmwareMissing readable b - - -If TRUE, indicates the device is likely missing firmware necessary for its -operation. - - - - The "NmPluginMissing" property - org.freedesktop.NetworkManager.Device:NmPluginMissing - -NmPluginMissing readable b - - -If TRUE, indicates the NetworkManager plugin for the device is likely -missing or misconfigured. - - - - The "DeviceType" property - org.freedesktop.NetworkManager.Device:DeviceType - -DeviceType readable u - - -The general type of the network device; ie Ethernet, Wi-Fi, etc. - -Returns: NMDeviceType - - - - The "AvailableConnections" property - org.freedesktop.NetworkManager.Device:AvailableConnections - -AvailableConnections readable ao - - -An array of object paths of every configured connection that is currently -'available' through this device. - - - - The "PhysicalPortId" property - org.freedesktop.NetworkManager.Device:PhysicalPortId - -PhysicalPortId readable s - - -If non-empty, an (opaque) indicator of the physical network port -associated with the device. This can be used to recognize when two -seemingly-separate hardware devices are actually just different virtual -interfaces to the same physical port. - - - - The "Mtu" property - org.freedesktop.NetworkManager.Device:Mtu - -Mtu readable u - - -The device MTU (maximum transmission unit). - - - - The "Metered" property - org.freedesktop.NetworkManager.Device:Metered - -Metered readable u - - -Whether the amount of traffic flowing through the device is subject to -limitations, for example set by service providers. - -Returns: NMMetered - - - - The "LldpNeighbors" property - org.freedesktop.NetworkManager.Device:LldpNeighbors - -LldpNeighbors readable aa{sv} - - -Array of LLDP neighbors; each element is a dictionary mapping LLDP TLV -names to variant boxed values. - - - - The "Real" property - org.freedesktop.NetworkManager.Device:Real - -Real readable b - - -True if the device exists, or False for placeholder devices that do not -yet exist but could be automatically created by NetworkManager if one of -their AvailableConnections was activated. - - - - The "Ip4Connectivity" property - org.freedesktop.NetworkManager.Device:Ip4Connectivity - -Ip4Connectivity readable u - - -The result of the last IPv4 connectivity check. - -Returns: NMConnectivityState - -Since 1.16 - - - The "Ip6Connectivity" property - org.freedesktop.NetworkManager.Device:Ip6Connectivity - -Ip6Connectivity readable u - - -The result of the last IPv6 connectivity check. - -Returns: NMConnectivityState - -Since 1.16 - - - The "InterfaceFlags" property - org.freedesktop.NetworkManager.Device:InterfaceFlags - -InterfaceFlags readable u - - -The flags of the network interface. See -NMDeviceInterfaceFlags for -the currently defined flags. - -Since 1.22 - - - The "HwAddress" property - org.freedesktop.NetworkManager.Device:HwAddress - -HwAddress readable s - - -The hardware address of the device. - -This replaces the other 'HwAddress' properties on the device-specific D-Bus interfaces. - -Since 1.24 - - - The "Ports" property - org.freedesktop.NetworkManager.Device:Ports - -Ports readable ao - - -The port devices of the controller device. - -Array of object paths representing devices which are currently set as -port of this device. This replaces the 'Slaves' properties on the -device-specific D-Bus interfaces. - -Since 1.34 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.DnsManager.xml b/docs/api/dbus-org.freedesktop.NetworkManager.DnsManager.xml deleted file mode 100644 index 0488bd65..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.DnsManager.xml +++ /dev/null @@ -1,62 +0,0 @@ - - - - org.freedesktop.NetworkManager.DnsManager - org.freedesktop.NetworkManager.DnsManager - org.freedesktop.NetworkManager.DnsManager DNS Configuration State. - Properties - -Mode readable s -RcManager readable s -Configuration readable aa{sv} - - - - Description - -The interface contains DNS-related information. - - - - Property Details - - The "Mode" property - org.freedesktop.NetworkManager.DnsManager:Mode - -Mode readable s - - -The current DNS processing mode. - - - - The "RcManager" property - org.freedesktop.NetworkManager.DnsManager:RcManager - -RcManager readable s - - -The current resolv.conf management mode. - - - - The "Configuration" property - org.freedesktop.NetworkManager.DnsManager:Configuration - -Configuration readable aa{sv} - - -The current DNS configuration represented as an array of -dictionaries. Each dictionary has the "nameservers", -"priority" keys and, optionally, "interface" and "vpn". -"nameservers" is the list of DNS servers, "priority" their -relative priority, "interface" the interface on which these -servers are contacted, "vpn" a boolean telling whether the -configuration was obtained from a VPN connection. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml deleted file mode 100644 index c14e5c41..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.IP4Config.xml +++ /dev/null @@ -1,189 +0,0 @@ - - - - org.freedesktop.NetworkManager.IP4Config - org.freedesktop.NetworkManager.IP4Config - org.freedesktop.NetworkManager.IP4Config IPv4 Configuration Set. - Properties - -Addresses readable aau -AddressData readable aa{sv} -Gateway readable s -Routes readable aau -RouteData readable aa{sv} -Nameservers readable au -NameserverData readable aa{sv} -Domains readable as -Searches readable as -DnsOptions readable as -DnsPriority readable i -WinsServers readable au -WinsServerData readable as - - - - Description - - - - - - Property Details - - The "Addresses" property - org.freedesktop.NetworkManager.IP4Config:Addresses - -Addresses readable aau - - -Array of arrays of IPv4 address/prefix/gateway. All 3 elements of each -array are in network byte order. Essentially: [(addr, prefix, gateway), -(addr, prefix, gateway), ...]. - -DEPRECATED: use AddressData and Gateway - - - - The "AddressData" property - org.freedesktop.NetworkManager.IP4Config:AddressData - -AddressData readable aa{sv} - - -Array of IP address data objects. All addresses will include "address" (an -IP address string), and "prefix" (a uint). Some addresses may include -additional attributes. - - - - The "Gateway" property - org.freedesktop.NetworkManager.IP4Config:Gateway - -Gateway readable s - - -The gateway in use. - - - - The "Routes" property - org.freedesktop.NetworkManager.IP4Config:Routes - -Routes readable aau - - -Arrays of IPv4 route/prefix/next-hop/metric. All 4 elements of each tuple -are in network byte order. 'route' and 'next hop' are IPv4 addresses, -while prefix and metric are simple unsigned integers. Essentially: -[(route, prefix, next-hop, metric), (route, prefix, next-hop, metric), -...]. - -DEPRECATED: use RouteData - - - - The "RouteData" property - org.freedesktop.NetworkManager.IP4Config:RouteData - -RouteData readable aa{sv} - - -Array of IP route data objects. All routes will include "dest" (an IP -address string) and "prefix" (a uint). Some routes may include "next-hop" -(an IP address string), "metric" (a uint), and additional attributes. - - - - The "Nameservers" property - org.freedesktop.NetworkManager.IP4Config:Nameservers - -Nameservers readable au - - -The nameservers in use. - -DEPRECATED: use NameserverData - - - - The "NameserverData" property - org.freedesktop.NetworkManager.IP4Config:NameserverData - -NameserverData readable aa{sv} - - -The nameservers in use. Currently, only the value "address" -is recognized (with an IP address string). - -Since 1.14 - - - The "Domains" property - org.freedesktop.NetworkManager.IP4Config:Domains - -Domains readable as - - -A list of domains this address belongs to. - - - - The "Searches" property - org.freedesktop.NetworkManager.IP4Config:Searches - -Searches readable as - - -A list of dns searches. - - - - The "DnsOptions" property - org.freedesktop.NetworkManager.IP4Config:DnsOptions - -DnsOptions readable as - - -A list of DNS options that modify the behavior of the DNS resolver. See -resolv.conf(5) manual page for the list of supported options. - - - - The "DnsPriority" property - org.freedesktop.NetworkManager.IP4Config:DnsPriority - -DnsPriority readable i - - -The relative priority of DNS servers. - - - - The "WinsServers" property - org.freedesktop.NetworkManager.IP4Config:WinsServers - -WinsServers readable au - - -The Windows Internet Name Service servers associated with the connection. -Each address is in network byte order. - -DEPRECATED: use WinsServerData - - - - The "WinsServerData" property - org.freedesktop.NetworkManager.IP4Config:WinsServerData - -WinsServerData readable as - - -The Windows Internet Name Service servers associated with the connection. - -Since 1.14 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml b/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml deleted file mode 100644 index 55da5265..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.IP6Config.xml +++ /dev/null @@ -1,142 +0,0 @@ - - - - org.freedesktop.NetworkManager.IP6Config - org.freedesktop.NetworkManager.IP6Config - org.freedesktop.NetworkManager.IP6Config IPv6 Configuration Set. - Properties - -Addresses readable a(ayuay) -AddressData readable aa{sv} -Gateway readable s -Routes readable a(ayuayu) -RouteData readable aa{sv} -Nameservers readable aay -Domains readable as -Searches readable as -DnsOptions readable as -DnsPriority readable i - - - - Description - - - - - - Property Details - - The "Addresses" property - org.freedesktop.NetworkManager.IP6Config:Addresses - -Addresses readable a(ayuay) - - -Array of tuples of IPv6 address/prefix/gateway. - -DEPRECATED: use AddressData and Gateway. - - - - The "AddressData" property - org.freedesktop.NetworkManager.IP6Config:AddressData - -AddressData readable aa{sv} - - -Array of IP address data objects. All addresses will include "address" (an -IP address string), and "prefix" (a uint). Some addresses may include -additional attributes. - - - - The "Gateway" property - org.freedesktop.NetworkManager.IP6Config:Gateway - -Gateway readable s - - -The gateway in use. - - - - The "Routes" property - org.freedesktop.NetworkManager.IP6Config:Routes - -Routes readable a(ayuayu) - - -Tuples of IPv6 route/prefix/next-hop/metric. - -DEPRECATED: use RouteData. - - - - The "RouteData" property - org.freedesktop.NetworkManager.IP6Config:RouteData - -RouteData readable aa{sv} - - -Array of IP route data objects. All routes will include "dest" (an IP -address string) and "prefix" (a uint). Some routes may include "next-hop" -(an IP address string), "metric" (a uint), and additional attributes. - - - - The "Nameservers" property - org.freedesktop.NetworkManager.IP6Config:Nameservers - -Nameservers readable aay - - -The nameservers in use. - - - - The "Domains" property - org.freedesktop.NetworkManager.IP6Config:Domains - -Domains readable as - - -A list of domains this address belongs to. - - - - The "Searches" property - org.freedesktop.NetworkManager.IP6Config:Searches - -Searches readable as - - -A list of dns searches. - - - - The "DnsOptions" property - org.freedesktop.NetworkManager.IP6Config:DnsOptions - -DnsOptions readable as - - -A list of DNS options that modify the behavior of the DNS resolver. See -resolv.conf(5) manual page for the list of supported options. - - - - The "DnsPriority" property - org.freedesktop.NetworkManager.IP6Config:DnsPriority - -DnsPriority readable i - - -The relative priority of DNS servers. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.PPP.xml b/docs/api/dbus-org.freedesktop.NetworkManager.PPP.xml deleted file mode 100644 index a2222ff5..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.PPP.xml +++ /dev/null @@ -1,126 +0,0 @@ - - - - org.freedesktop.NetworkManager.PPP - org.freedesktop.NetworkManager.PPP - org.freedesktop.NetworkManager.PPP Helper interface for a PPP plugin. - Methods - -NeedSecrets (OUT s username, - OUT s password); -SetIp4Config (IN a{sv} config); -SetIp6Config (IN a{sv} config); -SetState (IN u state); -SetIfindex (IN i ifindex); - - - - Description - - - - - - Method Details - - The NeedSecrets() method - org.freedesktop.NetworkManager.PPP.NeedSecrets() - -NeedSecrets (OUT s username, - OUT s password); - - - - - - - OUT s username: - - - - - - OUT s password: - - - - - - - - The SetIp4Config() method - org.freedesktop.NetworkManager.PPP.SetIp4Config() - -SetIp4Config (IN a{sv} config); - - - - - - - IN a{sv} config: - - - - - - - - The SetIp6Config() method - org.freedesktop.NetworkManager.PPP.SetIp6Config() - -SetIp6Config (IN a{sv} config); - - - - - - - IN a{sv} config: - - - - - - - - The SetState() method - org.freedesktop.NetworkManager.PPP.SetState() - -SetState (IN u state); - - - - - - - IN u state: - - - - - - - - The SetIfindex() method - org.freedesktop.NetworkManager.PPP.SetIfindex() - -SetIfindex (IN i ifindex); - - - - - - - IN i ifindex: - - - - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.SecretAgent.xml b/docs/api/dbus-org.freedesktop.NetworkManager.SecretAgent.xml deleted file mode 100644 index 69e76573..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.SecretAgent.xml +++ /dev/null @@ -1,179 +0,0 @@ - - - - org.freedesktop.NetworkManager.SecretAgent - org.freedesktop.NetworkManager.SecretAgent - org.freedesktop.NetworkManager.SecretAgent User Secret Agent. - Methods - -GetSecrets (IN a{sa{sv}} connection, - IN o connection_path, - IN s setting_name, - IN as hints, - IN u flags, - OUT a{sa{sv}} secrets); -CancelGetSecrets (IN o connection_path, - IN s setting_name); -SaveSecrets (IN a{sa{sv}} connection, - IN o connection_path); -DeleteSecrets (IN a{sa{sv}} connection, - IN o connection_path); - - - - Description - -Private D-Bus interface used by secret agents that store and provide -secrets to NetworkManager. If an agent provides secrets to NetworkManager -as part of connection creation, and the some of those secrets are "agent -owned" the agent should store those secrets itself and should not expect -its SaveSecrets() method to be called. SaveSecrets() will be called eg if -some program other than the agent itself (like a connection editor) -changes the secrets out of band. The agent should implement this D-Bus -interface on an object with the path -/org/freedesktop/NetworkManager/SecretAgent. - - - - Method Details - - The GetSecrets() method - org.freedesktop.NetworkManager.SecretAgent.GetSecrets() - -GetSecrets (IN a{sa{sv}} connection, - IN o connection_path, - IN s setting_name, - IN as hints, - IN u flags, - OUT a{sa{sv}} secrets); - - -Retrieve and return stored secrets, if any, or request new secrets from -the agent's user. If user interaction is allowed and the user enters new -secrets, the agent is expected to save the new secrets to persistent -storage (if the secret's flags include AGENT_OWNED) as NetworkManager will -not send these secrets back to the same agent via a SaveSecrets() call. If -the user canceled any interaction, the agent should return the -UserCanceled error (see below). - - - - IN a{sa{sv}} connection: - -Nested settings maps containing the connection for which secrets are being requested. This may contain system-owned secrets if the agent has successfully authenticated to modify system network settings and the GetSecrets request flags allow user interaction. - - - - IN o connection_path: - -Object path of the connection for which secrets are being requested. - - - - IN s setting_name: - -Setting name for which secrets are being requested. - - - - IN as hints: - -Array of strings of key names in the requested setting for which NetworkManager thinks a secrets may be required, and/or well-known identifiers and data that may be useful to the client in processing the secrets request. Note that it's not always possible to determine which secret is required, so in some cases no hints may be given. The Agent should return any secrets it has, or that it thinks are required, regardless of what hints NetworkManager sends in this request. Some hints have special prefixes that provide information to the agent; for example, VPN requests may send server-specific messages prefixed with "x-vpn-message:". - - - - IN u flags: - -(NMSecretAgentGetSecretsFlags) Flags which modify the behavior of the secrets request. If true, new secrets are assumed to be invalid or incorrect, and the agent should ask the user for new secrets. If false, existing secrets should be retrieved from storage and returned without interrupting the user. - - - - OUT a{sa{sv}} secrets: - -Nested settings maps containing secrets. Each setting MUST contain at least the 'name' field, containing the name of the setting, and one or more secrets. - - - - - - The CancelGetSecrets() method - org.freedesktop.NetworkManager.SecretAgent.CancelGetSecrets() - -CancelGetSecrets (IN o connection_path, - IN s setting_name); - - -Cancel a pending GetSecrets request for secrets of the given connection. -Any GetSecrets request with the same 'connection_path' and 'setting_name' -that are given in a CancelGetSecrets request should be canceled. - - - - IN o connection_path: - -Object path of the connection for which, if secrets for the given 'setting_name' are being requested, the request should be canceled. - - - - IN s setting_name: - -Setting name for which secrets for this connection were originally being requested. - - - - - - The SaveSecrets() method - org.freedesktop.NetworkManager.SecretAgent.SaveSecrets() - -SaveSecrets (IN a{sa{sv}} connection, - IN o connection_path); - - -Save given secrets to backing storage. - - - - IN a{sa{sv}} connection: - -Nested settings maps containing the entire connection (including secrets), for which the agent should save the secrets to backing storage. This method will not be called when the agent itself is the process creating or updating a connection; in that case the agent is assumed to have already saved those secrets since it had them already. - - - - IN o connection_path: - -Object path of the connection for which the agent should save secrets to backing storage. - - - - - - The DeleteSecrets() method - org.freedesktop.NetworkManager.SecretAgent.DeleteSecrets() - -DeleteSecrets (IN a{sa{sv}} connection, - IN o connection_path); - - -Delete secrets from backing storage. - - - - IN a{sa{sv}} connection: - -Nested settings maps containing the connection properties (sans secrets), for which the agent should delete the secrets from backing storage. - - - - IN o connection_path: - -Object path of the connection for which the agent should delete secrets from backing storage. - - - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.Connection.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Settings.Connection.xml deleted file mode 100644 index a302a3d0..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.Connection.xml +++ /dev/null @@ -1,350 +0,0 @@ - - - - org.freedesktop.NetworkManager.Settings.Connection - org.freedesktop.NetworkManager.Settings.Connection - org.freedesktop.NetworkManager.Settings.Connection Connection Settings Profile. - Methods - -Update (IN a{sa{sv}} properties); -UpdateUnsaved (IN a{sa{sv}} properties); -Delete (); -GetSettings (OUT a{sa{sv}} settings); -GetSecrets (IN s setting_name, - OUT a{sa{sv}} secrets); -ClearSecrets (); -Save (); -Update2 (IN a{sa{sv}} settings, - IN u flags, - IN a{sv} args, - OUT a{sv} result); - - - - Signals - -Updated (); -Removed (); - - - - Properties - -Unsaved readable b -Flags readable u -Filename readable s - - - - Description - -Represents a single network connection configuration. - - - - Method Details - - The Update() method - org.freedesktop.NetworkManager.Settings.Connection.Update() - -Update (IN a{sa{sv}} properties); - - -Update the connection with new settings and properties (replacing all -previous settings and properties) and save the connection to disk. Secrets -may be part of the update request, and will be either stored in persistent -storage or sent to a Secret Agent for storage, depending on the flags -associated with each secret. - - - - IN a{sa{sv}} properties: - -New connection settings, properties, and (optionally) secrets. - - - - - - The UpdateUnsaved() method - org.freedesktop.NetworkManager.Settings.Connection.UpdateUnsaved() - -UpdateUnsaved (IN a{sa{sv}} properties); - - -Update the connection with new settings and properties (replacing all -previous settings and properties) but do not immediately save the -connection to disk. Secrets may be part of the update request and may sent -to a Secret Agent for storage, depending on the flags associated with each -secret. Use the 'Save' method to save these changes to disk. Note that -unsaved changes will be lost if the connection is reloaded from disk -(either automatically on file change or due to an explicit -ReloadConnections call). - - - - IN a{sa{sv}} properties: - -New connection settings, properties, and (optionally) secrets. - - - - - - The Delete() method - org.freedesktop.NetworkManager.Settings.Connection.Delete() - -Delete (); - - -Delete the connection. - - - - The GetSettings() method - org.freedesktop.NetworkManager.Settings.Connection.GetSettings() - -GetSettings (OUT a{sa{sv}} settings); - - -Get the settings maps describing this network configuration. This will -never include any secrets required for connection to the network, as those -are often protected. Secrets must be requested separately using the -GetSecrets() call. - - - - OUT a{sa{sv}} settings: - -The nested settings maps describing this object. - - - - - - The GetSecrets() method - org.freedesktop.NetworkManager.Settings.Connection.GetSecrets() - -GetSecrets (IN s setting_name, - OUT a{sa{sv}} secrets); - - -Get the secrets belonging to this network configuration. Only secrets from -persistent storage or a Secret Agent running in the requestor's session -will be returned. The user will never be prompted for secrets as a result -of this request. - - - - IN s setting_name: - -Name of the setting to return secrets for. If empty, all secrets will be returned. - - - - OUT a{sa{sv}} secrets: - -Nested settings maps containing secrets. - - - - - - The ClearSecrets() method - org.freedesktop.NetworkManager.Settings.Connection.ClearSecrets() - -ClearSecrets (); - - -Clear the secrets belonging to this network connection profile. - - - - The Save() method - org.freedesktop.NetworkManager.Settings.Connection.Save() - -Save (); - - -Saves a "dirty" connection (that had previously been updated with -UpdateUnsaved) to persistent storage. - - - - The Update2() method - org.freedesktop.NetworkManager.Settings.Connection.Update2() - -Update2 (IN a{sa{sv}} settings, - IN u flags, - IN a{sv} args, - OUT a{sv} result); - - -Update the connection with new settings and properties (replacing all -previous settings and properties). - -Update2 is an alternative to -Update, -UpdateUnsaved -and Save -extensible with extra flags and args arguments. - -The flags argument accepts the combination of following values, -logically or-ed together: - - - - 0x1 (to-disk): - The connection is persisted to disk. - - - 0x2 (in-memory): - The change is only made in memory (without touching an eventual - profile on disk). If neither 0x1 nor 0x2 is set, the change is made in memory - only, if the connection is already in memory only. - - - 0x4 (in-memory-detached): - Like "in-memory", but behaves slightly different when migrating - the profile from disk to in-memory. - - - 0x8 (in-memory-only): - Like "in-memory", but behaves slightly different when migrating - the profile from disk to in-memory. - - - 0x10 (volatile): - - - 0x20 (block-autoconnect): - Blocks auto-connect on the updated profile - - - 0x40 (no-reapply): - Prevents "connection.zone" and "connection.metered" properties - to take effect on currently active devices. - - - -The args argument accepts the following keys: - - - - plugin: - The settings plugin the connection will be migrated to - such as "keyfile" or "ifcfg-rh". - Since 1.38 - version-id: - If specified, the update request is rejected if the - profile's version-id does not match. This can be used to catch concurrent - modifications. Zero means no version check.Since 1.44 - - - -Secrets may be part of the update request, and will be either stored in persistent -storage or sent to a Secret Agent for storage, depending on the flags -associated with each secret. - - - - IN a{sa{sv}} settings: - -New connection settings, properties, and (optionally) secrets. Provide an empty array to use the current settings. - - - - IN u flags: - -Optional flags. Unknown flags cause the call to fail. - - - - IN a{sv} args: - -Optional arguments dictionary, for extentibility. Specifying unknown keys causes the call to fail. - - - - OUT a{sv} result: - -Currently no results are returned. - - - -Since 1.12 - - - - Signal Details - - The "Updated" signal - org.freedesktop.NetworkManager.Settings.Connection::Updated - -Updated (); - - -Emitted when any settings or permissions change. When handling this -signal, clients should re-read the connection using the GetSettings method -to get the changes and to ensure the client still has permission to access -the connection. - - - - The "Removed" signal - org.freedesktop.NetworkManager.Settings.Connection::Removed - -Removed (); - - -Emitted when this connection is no longer available. This happens when the -connection is deleted or if it is no longer accessible by any of the -system's logged-in users. After receipt of this signal, the object no -longer exists. Also see the Settings.ConnectionRemoved signal. - - - - - Property Details - - The "Unsaved" property - org.freedesktop.NetworkManager.Settings.Connection:Unsaved - -Unsaved readable b - - -If set, indicates that the in-memory state of the connection does not -match the on-disk state. This flag will be set when UpdateUnsaved() is -called or when any connection details change, and cleared when the -connection is saved to disk via Save() or from internal operations. - - - - The "Flags" property - org.freedesktop.NetworkManager.Settings.Connection:Flags - -Flags readable u - - -Additional flags of the connection profile. - -Returns: NMSettingsConnectionFlags - -Since 1.12 - - - The "Filename" property - org.freedesktop.NetworkManager.Settings.Connection:Filename - -Filename readable s - - -File that stores the connection in case the connection is file-backed. - -Since 1.12 - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml deleted file mode 100644 index 918bbc53..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.Settings.xml +++ /dev/null @@ -1,419 +0,0 @@ - - - - org.freedesktop.NetworkManager.Settings - org.freedesktop.NetworkManager.Settings - org.freedesktop.NetworkManager.Settings Connection Settings Profile Manager. - Methods - -ListConnections (OUT ao connections); -GetConnectionByUuid (IN s uuid, - OUT o connection); -AddConnection (IN a{sa{sv}} connection, - OUT o path); -AddConnectionUnsaved (IN a{sa{sv}} connection, - OUT o path); -AddConnection2 (IN a{sa{sv}} settings, - IN u flags, - IN a{sv} args, - OUT o path, - OUT a{sv} result); -LoadConnections (IN as filenames, - OUT b status, - OUT as failures); -ReloadConnections (OUT b status); -SaveHostname (IN s hostname); - - - - Signals - -NewConnection (o connection); -ConnectionRemoved (o connection); - - - - Properties - -Connections readable ao -Hostname readable s -CanModify readable b -VersionId readable t - - - - Description - -The Settings interface allows clients to view and administrate the -connections stored and used by NetworkManager. - - - - Method Details - - The ListConnections() method - org.freedesktop.NetworkManager.Settings.ListConnections() - -ListConnections (OUT ao connections); - - -List the saved network connections known to NetworkManager. - - - - OUT ao connections: - -List of connections. - - - - - - The GetConnectionByUuid() method - org.freedesktop.NetworkManager.Settings.GetConnectionByUuid() - -GetConnectionByUuid (IN s uuid, - OUT o connection); - - -Retrieve the object path of a connection, given that connection's UUID. - - - - IN s uuid: - -The UUID to find the connection object path for. - - - - OUT o connection: - -The connection's object path. - - - - - - The AddConnection() method - org.freedesktop.NetworkManager.Settings.AddConnection() - -AddConnection (IN a{sa{sv}} connection, - OUT o path); - - -Add new connection and save it to disk. This operation does not start the -network connection unless (1) device is idle and able to connect to the -network described by the new connection, and (2) the connection is allowed -to be started automatically. - - - - IN a{sa{sv}} connection: - -Connection settings and properties. - - - - OUT o path: - -Object path of the new connection that was just added. - - - - - - The AddConnectionUnsaved() method - org.freedesktop.NetworkManager.Settings.AddConnectionUnsaved() - -AddConnectionUnsaved (IN a{sa{sv}} connection, - OUT o path); - - -Add new connection but do not save it to disk immediately. This operation -does not start the network connection unless (1) device is idle and able -to connect to the network described by the new connection, and (2) the -connection is allowed to be started automatically. Use the 'Save' method -on the connection to save these changes to disk. - - - - IN a{sa{sv}} connection: - -Connection settings and properties. - - - - OUT o path: - -Object path of the new connection that was just added. - - - - - - The AddConnection2() method - org.freedesktop.NetworkManager.Settings.AddConnection2() - -AddConnection2 (IN a{sa{sv}} settings, - IN u flags, - IN a{sv} args, - OUT o path, - OUT a{sv} result); - - -Add a new connection profile. - -AddConnection2 is an alternative to -AddConnection and -AddConnectionUnsaved. -The new variant can do everything that the older variants could, and more. -Its behavior is extensible via extra flags and args arguments. - -The flags argument accepts the combination of following values, -logically or-ed together: - - - - 0x1 (to-disk): - The connection is persisted to disk. - - - 0x2 (in-memory): - The change is only made in memory (without touching an eventual - profile on disk). If neither 0x1 nor 0x2 is set, the change is made in memory - only, if the connection is already in memory only. - - - 0x20 (block-autoconnect): - Blocks auto-connect on the new profile - - - -The args argument accepts the following keys: - - - - plugin: - The settings plugin the newly added connection will - use, such as "keyfile" or "ifcfg-rh". - Since 1.38 - - - -Either the flags 0x1 (to-disk) or 0x2 (in-memory) must be specified. -The effect is whether to behave like -AddConnection or -AddConnectionUnsaved. - - - - IN a{sa{sv}} settings: - -New connection settings, properties, and (optionally) secrets. - - - - IN u flags: - -Flags. Unknown flags cause the call to fail. - - - - IN a{sv} args: - -Optional arguments dictionary, for extentibility. Specifying unknown keys causes the call to fail. - - - - OUT o path: - -Object path of the new connection that was just added. - - - - OUT a{sv} result: - -Output argument, currently no additional results are returned. - - - -Since 1.20 - - - The LoadConnections() method - org.freedesktop.NetworkManager.Settings.LoadConnections() - -LoadConnections (IN as filenames, - OUT b status, - OUT as failures); - - -Loads or reloads the indicated connections from disk. You should call this -after making changes directly to an on-disk connection file to make sure -that NetworkManager sees the changes. -As with AddConnection(), this operation does not necessarily -start the network connection. - -Note that before 1.20, NetworkManager had a bug and this status value was wrong. -It is better to assume success if the method does not return with a D-Bus error. -On top of that, you can look at failures to know whether any of the requested files failed. - - - - IN as filenames: - -Array of paths to on-disk connection profiles in directories monitored by NetworkManager. - - - - OUT b status: - -Success or failure of the operation as a whole. True if NetworkManager at least tried to load the indicated connections, even if it did not succeed. False if an error occurred before trying to load the connections (eg, permission denied). - - - - OUT as failures: - -Paths of connection files that could not be loaded. - - - - - - The ReloadConnections() method - org.freedesktop.NetworkManager.Settings.ReloadConnections() - -ReloadConnections (OUT b status); - - -Tells NetworkManager to reload all connection files from disk, including -noticing any added or deleted connection files. - - - - OUT b status: - -This always returns TRUE. - - - - - - The SaveHostname() method - org.freedesktop.NetworkManager.Settings.SaveHostname() - -SaveHostname (IN s hostname); - - -Save the hostname to persistent configuration. - - - - IN s hostname: - -The hostname to save to persistent configuration. If blank, the persistent hostname is cleared. - - - - - - - Signal Details - - The "NewConnection" signal - org.freedesktop.NetworkManager.Settings::NewConnection - -NewConnection (o connection); - - -Emitted when a new connection has been added after NetworkManager has -started up and initialized. This signal is not emitted for connections -read while starting up, because NetworkManager's D-Bus service is only -available after all connections have been read, and to prevent spamming -listeners with too many signals at one time. To retrieve the initial -connection list, call the ListConnections() method once, and then listen -for individual Settings.NewConnection and Settings.Connection.Deleted -signals for further updates. - - - - o connection: - -Object path of the new connection. - - - - - - The "ConnectionRemoved" signal - org.freedesktop.NetworkManager.Settings::ConnectionRemoved - -ConnectionRemoved (o connection); - - -Emitted when a connection is no longer available. This happens when the -connection is deleted or if it is no longer accessible by any of the -system's logged-in users. After receipt of this signal, the connection no -longer exists and cannot be used. Also see the Settings.Connection.Removed -signal. - - - - o connection: - -Object path of the removed connection. - - - - - - - Property Details - - The "Connections" property - org.freedesktop.NetworkManager.Settings:Connections - -Connections readable ao - - -List of object paths of available network connection profiles. - - - - The "Hostname" property - org.freedesktop.NetworkManager.Settings:Hostname - -Hostname readable s - - -The machine hostname stored in persistent configuration. - - - - The "CanModify" property - org.freedesktop.NetworkManager.Settings:CanModify - -CanModify readable b - - -If true, adding and modifying connections is supported. - - - - The "VersionId" property - org.freedesktop.NetworkManager.Settings:VersionId - -VersionId readable t - - -The version of the settings. This is incremented whenever the profile -changes and can be used to detect concurrent modifications. - -Since: 1.44 - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Connection.xml b/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Connection.xml deleted file mode 100644 index 6a23fae4..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Connection.xml +++ /dev/null @@ -1,82 +0,0 @@ - - - - org.freedesktop.NetworkManager.VPN.Connection - org.freedesktop.NetworkManager.VPN.Connection - org.freedesktop.NetworkManager.VPN.Connection Active VPN Connection. - Signals - -VpnStateChanged (u state, - u reason); - - - - Properties - -VpnState readable u -Banner readable s - - - - Description - -Represents an active connection to a Virtual Private Network. - - - - Signal Details - - The "VpnStateChanged" signal - org.freedesktop.NetworkManager.VPN.Connection::VpnStateChanged - -VpnStateChanged (u state, - u reason); - - -Emitted when the state of the VPN connection has changed. - - - - u state: - -(NMVpnConnectionState) The new state of the VPN connection. - - - - u reason: - -(NMActiveConnectionStateReason) Reason code describing the change to the new state. - - - - - - - Property Details - - The "VpnState" property - org.freedesktop.NetworkManager.VPN.Connection:VpnState - -VpnState readable u - - -The VPN-specific state of the connection. - -Returns: NMVpnConnectionState - - - - The "Banner" property - org.freedesktop.NetworkManager.VPN.Connection:Banner - -Banner readable s - - -The banner string of the VPN connection. - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml b/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml deleted file mode 100644 index 0efccfe7..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.VPN.Plugin.xml +++ /dev/null @@ -1,380 +0,0 @@ - - - - org.freedesktop.NetworkManager.VPN.Plugin - org.freedesktop.NetworkManager.VPN.Plugin - org.freedesktop.NetworkManager.VPN.Plugin VPN Service. - Methods - -Connect (IN a{sa{sv}} connection); -ConnectInteractive (IN a{sa{sv}} connection, - IN a{sv} details); -NeedSecrets (IN a{sa{sv}} settings, - OUT s setting_name); -Disconnect (); -SetConfig (IN a{sv} config); -SetIp4Config (IN a{sv} config); -SetIp6Config (IN a{sv} config); -SetFailure (IN s reason); -NewSecrets (IN a{sa{sv}} connection); - - - - Signals - -StateChanged (u state); -SecretsRequired (s message, - as secrets); -Config (a{sv} config); -Ip4Config (a{sv} ip4config); -Ip6Config (a{sv} ip6config); -LoginBanner (s banner); -Failure (u reason); - - - - Properties - -State readable u - - - - Description - -This interface is provided by plugins providing VPN services to the -NetworkManager daemon. - - - - Method Details - - The Connect() method - org.freedesktop.NetworkManager.VPN.Plugin.Connect() - -Connect (IN a{sa{sv}} connection); - - -Tells the plugin to connect. Interactive secrets requests (eg, emitting -the SecretsRequired signal) are not allowed. - - - - IN a{sa{sv}} connection: - -Describes the connection to be established. - - - - - - The ConnectInteractive() method - org.freedesktop.NetworkManager.VPN.Plugin.ConnectInteractive() - -ConnectInteractive (IN a{sa{sv}} connection, - IN a{sv} details); - - -Tells the plugin to connect, allowing interactive secrets requests (eg the -plugin is allowed to emit the SecretsRequired signal if the VPN service -indicates that it needs additional secrets during the connect process). - - - - IN a{sa{sv}} connection: - -Describes the connection to be established. - - - - IN a{sv} details: - -Additional details about the Connect process. - - - - - - The NeedSecrets() method - org.freedesktop.NetworkManager.VPN.Plugin.NeedSecrets() - -NeedSecrets (IN a{sa{sv}} settings, - OUT s setting_name); - - -Asks the plugin whether the provided connection will require secrets to -connect successfully. - - - - IN a{sa{sv}} settings: - -Describes the connection that may need secrets. - - - - OUT s setting_name: - -The setting name within the provided connection that requires secrets, if any. - - - - - - The Disconnect() method - org.freedesktop.NetworkManager.VPN.Plugin.Disconnect() - -Disconnect (); - - -Disconnect the plugin. - - - - The SetConfig() method - org.freedesktop.NetworkManager.VPN.Plugin.SetConfig() - -SetConfig (IN a{sv} config); - - -Set generic connection details on the connection. - - - - IN a{sv} config: - -Generic configuration details for the connection. - - - - - - The SetIp4Config() method - org.freedesktop.NetworkManager.VPN.Plugin.SetIp4Config() - -SetIp4Config (IN a{sv} config); - - -Set IPv4 details on the connection. - - - - IN a{sv} config: - -Ip4Config details for the connection. You must call SetConfig() before calling this. - - - - - - The SetIp6Config() method - org.freedesktop.NetworkManager.VPN.Plugin.SetIp6Config() - -SetIp6Config (IN a{sv} config); - - -Set IPv6 details on the connection. - - - - IN a{sv} config: - -Ip6Config details for the connection. You must call SetConfig() before calling this. - - - - - - The SetFailure() method - org.freedesktop.NetworkManager.VPN.Plugin.SetFailure() - -SetFailure (IN s reason); - - -Indicate a failure to the plugin. - - - - IN s reason: - -The reason for the failure. - - - - - - The NewSecrets() method - org.freedesktop.NetworkManager.VPN.Plugin.NewSecrets() - -NewSecrets (IN a{sa{sv}} connection); - - -Called in response to a SecretsRequired signal to deliver updated secrets -or other information to the plugin. - - - - IN a{sa{sv}} connection: - -Describes the connection including the new secrets. - - - - - - - Signal Details - - The "StateChanged" signal - org.freedesktop.NetworkManager.VPN.Plugin::StateChanged - -StateChanged (u state); - - -Emitted when the plugin state changes. - - - - u state: - -(NMVpnServiceState) The new state of the plugin. - - - - - - The "SecretsRequired" signal - org.freedesktop.NetworkManager.VPN.Plugin::SecretsRequired - -SecretsRequired (s message, - as secrets); - - -Emitted during an ongoing ConnectInteractive() request when the plugin has -determined that new secrets are required. NetworkManager will then call -the NewSecrets() method with a connection hash including the new secrets. - - - - s message: - -Informational message, if any, about the request. For example, if a second PIN is required, could indicate to the user to wait for the token code to change until entering the next PIN. - - - - as secrets: - -Array of strings of VPN secret names which the plugin thinks secrets may be required for, or other VPN-specific data to be processed by the VPN's front-end. - - - - - - The "Config" signal - org.freedesktop.NetworkManager.VPN.Plugin::Config - -Config (a{sv} config); - - -The plugin obtained generic configuration information. - - - - a{sv} config: - -The configuration information. - - - - - - The "Ip4Config" signal - org.freedesktop.NetworkManager.VPN.Plugin::Ip4Config - -Ip4Config (a{sv} ip4config); - - -The plugin obtained an IPv4 configuration. - - - - a{sv} ip4config: - -The IPv4 configuration. - - - - - - The "Ip6Config" signal - org.freedesktop.NetworkManager.VPN.Plugin::Ip6Config - -Ip6Config (a{sv} ip6config); - - -The plugin obtained an IPv6 configuration. - - - - a{sv} ip6config: - -The IPv6 configuration. - - - - - - The "LoginBanner" signal - org.freedesktop.NetworkManager.VPN.Plugin::LoginBanner - -LoginBanner (s banner); - - -Emitted when the plugin receives a login banner from the VPN service. - - - - s banner: - -The login banner string. - - - - - - The "Failure" signal - org.freedesktop.NetworkManager.VPN.Plugin::Failure - -Failure (u reason); - - -Emitted when a failure in the VPN plugin occurs. - - - - u reason: - -(NMVpnPluginFailure) Reason code for the failure. - - - - - - - Property Details - - The "State" property - org.freedesktop.NetworkManager.VPN.Plugin:State - -State readable u - - -The state of the plugin. - -Returns: NMVpnServiceState - - - - - diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.xml b/docs/api/dbus-org.freedesktop.NetworkManager.xml deleted file mode 100644 index c4832249..00000000 --- a/docs/api/dbus-org.freedesktop.NetworkManager.xml +++ /dev/null @@ -1,1056 +0,0 @@ - - - - org.freedesktop.NetworkManager - org.freedesktop.NetworkManager - org.freedesktop.NetworkManager Connection Manager. - Methods - -Reload (IN u flags); -GetDevices (OUT ao devices); -GetAllDevices (OUT ao devices); -GetDeviceByIpIface (IN s iface, - OUT o device); -ActivateConnection (IN o connection, - IN o device, - IN o specific_object, - OUT o active_connection); -AddAndActivateConnection (IN a{sa{sv}} connection, - IN o device, - IN o specific_object, - OUT o path, - OUT o active_connection); -AddAndActivateConnection2 (IN a{sa{sv}} connection, - IN o device, - IN o specific_object, - IN a{sv} options, - OUT o path, - OUT o active_connection, - OUT a{sv} result); -DeactivateConnection (IN o active_connection); -Sleep (IN b sleep); -Enable (IN b enable); -GetPermissions (OUT a{ss} permissions); -SetLogging (IN s level, - IN s domains); -GetLogging (OUT s level, - OUT s domains); -CheckConnectivity (OUT u connectivity); -state (OUT u state); -CheckpointCreate (IN ao devices, - IN u rollback_timeout, - IN u flags, - OUT o checkpoint); -CheckpointDestroy (IN o checkpoint); -CheckpointRollback (IN o checkpoint, - OUT a{su} result); -CheckpointAdjustRollbackTimeout (IN o checkpoint, - IN u add_timeout); - - - - Signals - -CheckPermissions (); -StateChanged (u state); -DeviceAdded (o device_path); -DeviceRemoved (o device_path); - - - - Properties - -Devices readable ao -AllDevices readable ao -Checkpoints readable ao -NetworkingEnabled readable b -WirelessEnabled readwrite b -WirelessHardwareEnabled readable b -WwanEnabled readwrite b -WwanHardwareEnabled readable b -WimaxEnabled readwrite b -WimaxHardwareEnabled readable b -RadioFlags readable u -ActiveConnections readable ao -PrimaryConnection readable o -PrimaryConnectionType readable s -Metered readable u -ActivatingConnection readable o -Startup readable b -Version readable s -VersionInfo readable au -Capabilities readable au -State readable u -Connectivity readable u -ConnectivityCheckAvailable readable b -ConnectivityCheckEnabled readwrite b -ConnectivityCheckUri readable s -GlobalDnsConfiguration readwrite a{sv} - - - - Description - - - - - - Method Details - - The Reload() method - org.freedesktop.NetworkManager.Reload() - -Reload (IN u flags); - - -Reload NetworkManager's configuration and perform certain updates, like flushing a cache or -rewriting external state to disk. This is similar to sending SIGHUP to NetworkManager but it -allows for more fine-grained control over what to reload (see flags). It also allows -non-root access via PolicyKit and contrary to signals it is synchronous. - -No flags (0x00) means to reload everything that is supported which is identical to -sending a SIGHUP. -(0x01) means to reload the NetworkManager.conf configuration from disk. Note that this -does not include connections, which can be reloaded via Setting's ReloadConnections. -(0x02) means to update DNS configuration, which usually involves writing /etc/resolv.conf -anew. -(0x04) means to restart the DNS plugin. This is for example useful when using -dnsmasq plugin, which uses additional configuration in /etc/NetworkManager/dnsmasq.d. -If you edit those files, you can restart the DNS plugin. This action shortly interrupts -name resolution. -Note that flags may affect each other. For example, restarting the DNS plugin (0x04) -implicitly updates DNS too (0x02). Or when reloading the configuration (0x01), changes -to DNS setting also cause a DNS update (0x02). However, (0x01) does not involve restarting -the DNS plugin (0x04) or update resolv.conf (0x02), unless the DNS related configuration -changes in NetworkManager.conf. - - - - IN u flags: - -Optional flags to specify which parts shall be reloaded. - - - - - - The GetDevices() method - org.freedesktop.NetworkManager.GetDevices() - -GetDevices (OUT ao devices); - - -Get the list of realized network devices. - - - - OUT ao devices: - -List of object paths of network devices known to the system. This list does not include device placeholders (see GetAllDevices()). - - - - - - The GetAllDevices() method - org.freedesktop.NetworkManager.GetAllDevices() - -GetAllDevices (OUT ao devices); - - -Get the list of all network devices. - - - - OUT ao devices: - -List of object paths of network devices and device placeholders (eg, devices that do not yet exist but which can be automatically created by NetworkManager if one of their AvailableConnections was activated). - - - - - - The GetDeviceByIpIface() method - org.freedesktop.NetworkManager.GetDeviceByIpIface() - -GetDeviceByIpIface (IN s iface, - OUT o device); - - -Return the object path of the network device referenced by its IP -interface name. Note that some devices (usually modems) only have an IP -interface name when they are connected. - - - - IN s iface: - -Interface name of the device to find. - - - - OUT o device: - -Object path of the network device. - - - - - - The ActivateConnection() method - org.freedesktop.NetworkManager.ActivateConnection() - -ActivateConnection (IN o connection, - IN o device, - IN o specific_object, - OUT o active_connection); - - -Activate a connection using the supplied device. - - - - IN o connection: - -The connection to activate. If "/" is given, a valid device path must be given, and NetworkManager picks the best connection to activate for the given device. VPN connections must always pass a valid connection path. - - - - IN o device: - -The object path of device to be activated for physical connections. This parameter is ignored for VPN connections, because the specific_object (if provided) specifies the device to use. - - - - IN o specific_object: - -The path of a connection-type-specific object this activation should use. This parameter is currently ignored for wired and mobile broadband connections, and the value of "/" should be used (ie, no specific object). For Wi-Fi connections, pass the object path of a specific AP from the card's scan list, or "/" to pick an AP automatically. For VPN connections, pass the object path of an ActiveConnection object that should serve as the "base" connection (to which the VPN connections lifetime will be tied), or pass "/" and NM will automatically use the current default device. - - - - OUT o active_connection: - -The path of the active connection object representing this active connection. - - - - - - The AddAndActivateConnection() method - org.freedesktop.NetworkManager.AddAndActivateConnection() - -AddAndActivateConnection (IN a{sa{sv}} connection, - IN o device, - IN o specific_object, - OUT o path, - OUT o active_connection); - - -Adds a new connection using the given details (if any) as a template -(automatically filling in missing settings with the capabilities of the -given device and specific object), then activate the new connection. -Cannot be used for VPN connections at this time. - -See also AddAndActivateConnection2. - - - - IN a{sa{sv}} connection: - -Connection settings and properties; if incomplete missing settings will be automatically completed using the given device and specific object. - - - - IN o device: - -The object path of device to be activated using the given connection. - - - - IN o specific_object: - -The path of a connection-type-specific object this activation should use. This parameter is currently ignored for wired and mobile broadband connections, and the value of "/" should be used (ie, no specific object). For Wi-Fi connections, pass the object path of a specific AP from the card's scan list, which will be used to complete the details of the newly added connection. - - - - OUT o path: - -Object path of the new connection that was just added. - - - - OUT o active_connection: - -The path of the active connection object representing this active connection. - - - - - - The AddAndActivateConnection2() method - org.freedesktop.NetworkManager.AddAndActivateConnection2() - -AddAndActivateConnection2 (IN a{sa{sv}} connection, - IN o device, - IN o specific_object, - IN a{sv} options, - OUT o path, - OUT o active_connection, - OUT a{sv} result); - - -Adds a new connection using the given details (if any) as a template -(automatically filling in missing settings with the capabilities of the -given device and specific object), then activate the new connection. -Cannot be used for VPN connections at this time. - -This method extends AddAndActivateConnection to allow passing further -parameters. At this time the following options are supported: - - * persist: A string value of either "disk" (default), "memory" or "volatile". If "memory" is passed, the connection will not be saved to disk. If "volatile" is passed, the connection will not be saved to disk and will be destroyed when disconnected. - * bind-activation: Bind the activation lifetime. Set to "dbus-client" to automatically disconnect when the requesting process disappears from the bus. The default of "none" means the connection is kept activated normally. - - - - IN a{sa{sv}} connection: - -Connection settings and properties; if incomplete missing settings will be automatically completed using the given device and specific object. - - - - IN o device: - -The object path of device to be activated using the given connection. - - - - IN o specific_object: - -The path of a connection-type-specific object this activation should use. This parameter is currently ignored for wired and mobile broadband connections, and the value of "/" should be used (ie, no specific object). For Wi-Fi connections, pass the object path of a specific AP from the card's scan list, which will be used to complete the details of the newly added connection. - - - - IN a{sv} options: - -Further options for the method call. - - - - OUT o path: - -Object path of the new connection that was just added. - - - - OUT o active_connection: - -The path of the active connection object representing this active connection. - - - - OUT a{sv} result: - -A dictionary of additional output arguments for future extension. Currently, not additional output arguments are supported. - - - - - - The DeactivateConnection() method - org.freedesktop.NetworkManager.DeactivateConnection() - -DeactivateConnection (IN o active_connection); - - -Deactivate an active connection. - - - - IN o active_connection: - -The currently active connection to deactivate. - - - - - - The Sleep() method - org.freedesktop.NetworkManager.Sleep() - -Sleep (IN b sleep); - - -Control the NetworkManager daemon's sleep state. When asleep, all -interfaces that it manages are deactivated. When awake, devices are -available to be activated. This command should not be called directly by -users or clients; it is intended for system suspend/resume tracking. - - - - IN b sleep: - -Indicates whether the NetworkManager daemon should sleep or wake. - - - - - - The Enable() method - org.freedesktop.NetworkManager.Enable() - -Enable (IN b enable); - - -Control whether overall networking is enabled or disabled. When disabled, -all interfaces that NM manages are deactivated. When enabled, all managed -interfaces are re-enabled and available to be activated. This command -should be used by clients that provide to users the ability to -enable/disable all networking. - - - - IN b enable: - -If FALSE, indicates that all networking should be disabled. If TRUE, indicates that NetworkManager should begin managing network devices. - - - - - - The GetPermissions() method - org.freedesktop.NetworkManager.GetPermissions() - -GetPermissions (OUT a{ss} permissions); - - -Returns the permissions a caller has for various authenticated operations -that NetworkManager provides, like Enable/Disable networking, changing -Wi-Fi, WWAN, and WiMAX state, etc. - - - - OUT a{ss} permissions: - -Dictionary of available permissions and results. Each permission is represented by a name (ie "org.freedesktop.NetworkManager.Foobar") and each result is one of the following values: "yes" (the permission is available), "auth" (the permission is available after a successful authentication), or "no" (the permission is denied). Clients may use these values in the UI to indicate the ability to perform certain operations. - - - - - - The SetLogging() method - org.freedesktop.NetworkManager.SetLogging() - -SetLogging (IN s level, - IN s domains); - - -Set logging verbosity and which operations are logged. - - - - IN s level: - -One of [ERR, WARN, INFO, DEBUG, TRACE, OFF, KEEP]. This level is applied to the domains as specified in the domains argument. Except for the special level "KEEP", all unmentioned domains are disabled entirely. "KEEP" is special and allows not to change the current setting except for the specified domains. E.g. level=KEEP and domains=PLATFORM:DEBUG will only touch the platform domain. - - - - IN s domains: - -A combination of logging domains separated by commas (','), or "NONE" to disable logging. Each domain enables logging for operations related to that domain. Available domains are: [PLATFORM, RFKILL, ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, AGENTS, SETTINGS, SUSPEND, CORE, DEVICE, OLPC, WIMAX, INFINIBAND, FIREWALL, ADSL, BOND, VLAN, BRIDGE, DBUS_PROPS, TEAM, CONCHECK, DCB, DISPATCH, AUDIT]. In addition to these domains, the following special domains can be used: [NONE, ALL, DEFAULT, DHCP, IP]. You can also specify that some domains should log at a different level from the default by appending a colon (':') and a log level (eg, 'WIFI:DEBUG'). If an empty string is given, the log level is changed but the current set of log domains remains unchanged. - - - - - - The GetLogging() method - org.freedesktop.NetworkManager.GetLogging() - -GetLogging (OUT s level, - OUT s domains); - - -Get current logging verbosity level and operations domains. - - - - OUT s level: - -One of [ERR, WARN, INFO, DEBUG, TRACE]. - - - - OUT s domains: - -For available domains see SetLogging() call. - - - - - - The CheckConnectivity() method - org.freedesktop.NetworkManager.CheckConnectivity() - -CheckConnectivity (OUT u connectivity); - - -Re-check the network connectivity state. - - - - OUT u connectivity: - -(NMConnectivityState) The current connectivity state. - - - - - - The state() method - org.freedesktop.NetworkManager.state() - -state (OUT u state); - - -The overall networking state as determined by the NetworkManager daemon, -based on the state of network devices under its management. - - - - OUT u state: - -NMState - - - - - - The CheckpointCreate() method - org.freedesktop.NetworkManager.CheckpointCreate() - -CheckpointCreate (IN ao devices, - IN u rollback_timeout, - IN u flags, - OUT o checkpoint); - - -Create a checkpoint of the current networking configuration -for given interfaces. If rollback_timeout is not zero, a -rollback is automatically performed after the given timeout. - - - - IN ao devices: - -A list of device paths for which a checkpoint should be created. An empty list means all devices. - - - - IN u rollback_timeout: - -The time in seconds until NetworkManager will automatically rollback to the checkpoint. Set to zero for infinite. - - - - IN u flags: - -(NMCheckpointCreateFlags) Flags for the creation. - - - - OUT o checkpoint: - -On success, the path of the new checkpoint. - - - - - - The CheckpointDestroy() method - org.freedesktop.NetworkManager.CheckpointDestroy() - -CheckpointDestroy (IN o checkpoint); - - -Destroy a previously created checkpoint. - - - - IN o checkpoint: - -The checkpoint to be destroyed. Set to empty to cancel all pending checkpoints. - - - - - - The CheckpointRollback() method - org.freedesktop.NetworkManager.CheckpointRollback() - -CheckpointRollback (IN o checkpoint, - OUT a{su} result); - - -Rollback a checkpoint before the timeout is reached. - - - - IN o checkpoint: - -The checkpoint to be rolled back. - - - - OUT a{su} result: - -On return, a dictionary of devices and results. Devices are represented by their original D-Bus path; each result is a RollbackResult. - - - - - - The CheckpointAdjustRollbackTimeout() method - org.freedesktop.NetworkManager.CheckpointAdjustRollbackTimeout() - -CheckpointAdjustRollbackTimeout (IN o checkpoint, - IN u add_timeout); - - -Reset the timeout for rollback for the checkpoint. - -Note that the added seconds start counting from now, -not "Created" timestamp or the previous expiration -time. Note that the "Created" property of the checkpoint -will stay unchanged by this call. However, the "RollbackTimeout" -will be recalculated to give the approximate new expiration time. -The new "RollbackTimeout" property will be approximate up to -one second precision, which is the accuracy of the property. - - - - IN o checkpoint: - -The checkpoint to be rolled back. - - - - IN u add_timeout: - -Number of seconds from now in which the timeout will expire. Set to 0 to disable the timeout. - - - -Since 1.12 - - - - Signal Details - - The "CheckPermissions" signal - org.freedesktop.NetworkManager::CheckPermissions - -CheckPermissions (); - - -Emitted when system authorization details change, indicating that clients -may wish to recheck permissions with GetPermissions. - - - - The "StateChanged" signal - org.freedesktop.NetworkManager::StateChanged - -StateChanged (u state); - - -NetworkManager's state changed. - - - - u state: - -(NMState) The new state of NetworkManager. - - - - - - The "DeviceAdded" signal - org.freedesktop.NetworkManager::DeviceAdded - -DeviceAdded (o device_path); - - -A device was added to the system - - - - o device_path: - -The object path of the newly added device. - - - - - - The "DeviceRemoved" signal - org.freedesktop.NetworkManager::DeviceRemoved - -DeviceRemoved (o device_path); - - -A device was removed from the system, and is no longer available. - - - - o device_path: - -The object path of the device that was just removed. - - - - - - - Property Details - - The "Devices" property - org.freedesktop.NetworkManager:Devices - -Devices readable ao - - -The list of realized network devices. Realized devices are those which -have backing resources (eg from the kernel or a management daemon like -ModemManager, teamd, etc). - - - - The "AllDevices" property - org.freedesktop.NetworkManager:AllDevices - -AllDevices readable ao - - -The list of both realized and un-realized network devices. Un-realized -devices are software devices which do not yet have backing resources, but -for which backing resources can be created if the device is activated. - - - - The "Checkpoints" property - org.freedesktop.NetworkManager:Checkpoints - -Checkpoints readable ao - - -The list of active checkpoints. - - - - The "NetworkingEnabled" property - org.freedesktop.NetworkManager:NetworkingEnabled - -NetworkingEnabled readable b - - -Indicates if overall networking is currently enabled or not. See the -Enable() method. - - - - The "WirelessEnabled" property - org.freedesktop.NetworkManager:WirelessEnabled - -WirelessEnabled readwrite b - - -Indicates if wireless is currently enabled or not. - - - - The "WirelessHardwareEnabled" property - org.freedesktop.NetworkManager:WirelessHardwareEnabled - -WirelessHardwareEnabled readable b - - -Indicates if the wireless hardware is currently enabled, i.e. the state of -the RF kill switch. - - - - The "WwanEnabled" property - org.freedesktop.NetworkManager:WwanEnabled - -WwanEnabled readwrite b - - -Indicates if mobile broadband devices are currently enabled or not. - - - - The "WwanHardwareEnabled" property - org.freedesktop.NetworkManager:WwanHardwareEnabled - -WwanHardwareEnabled readable b - - -Indicates if the mobile broadband hardware is currently enabled, i.e. the -state of the RF kill switch. - - - - The "WimaxEnabled" property - org.freedesktop.NetworkManager:WimaxEnabled - -WimaxEnabled readwrite b - - -DEPRECATED. Doesn't have any meaning and is around only for -compatibility reasons. - - - - The "WimaxHardwareEnabled" property - org.freedesktop.NetworkManager:WimaxHardwareEnabled - -WimaxHardwareEnabled readable b - - -DEPRECATED. Doesn't have any meaning and is around only for -compatibility reasons. - - - - The "RadioFlags" property - org.freedesktop.NetworkManager:RadioFlags - -RadioFlags readable u - - -Flags related to radio devices. See NMRadioFlags for the list of flags -supported. - -Since 1.38 - - - The "ActiveConnections" property - org.freedesktop.NetworkManager:ActiveConnections - -ActiveConnections readable ao - - -List of active connection object paths. - - - - The "PrimaryConnection" property - org.freedesktop.NetworkManager:PrimaryConnection - -PrimaryConnection readable o - - -The object path of the "primary" active connection being used to access -the network. In particular, if there is no VPN active, or the VPN does not -have the default route, then this indicates the connection that has the -default route. If there is a VPN active with the default route, then this -indicates the connection that contains the route to the VPN endpoint. - - - - The "PrimaryConnectionType" property - org.freedesktop.NetworkManager:PrimaryConnectionType - -PrimaryConnectionType readable s - - -The connection type of the "primary" active connection being used to -access the network. This is the same as the Type property on the object -indicated by PrimaryConnection. - - - - The "Metered" property - org.freedesktop.NetworkManager:Metered - -Metered readable u - - -Indicates whether the connectivity is metered. This is equivalent to the -metered property of the device associated with the primary connection. - -Returns: NMMetered - - - - The "ActivatingConnection" property - org.freedesktop.NetworkManager:ActivatingConnection - -ActivatingConnection readable o - - -The object path of an active connection that is currently being activated -and which is expected to become the new PrimaryConnection when it finishes -activating. - - - - The "Startup" property - org.freedesktop.NetworkManager:Startup - -Startup readable b - - -Indicates whether NM is still starting up; this becomes FALSE when NM has -finished attempting to activate every connection that it might be able to -activate at startup. - - - - The "Version" property - org.freedesktop.NetworkManager:Version - -Version readable s - - -NetworkManager version. - - - - The "VersionInfo" property - org.freedesktop.NetworkManager:VersionInfo - -VersionInfo readable au - - -NetworkManager version and capabilities. - -The first element in the array is the NM_VERSION of the daemon. It is a binary representation -of the "Version" and can be compared numerically. The version is encoded as -"(major << 16 | minor << 8 | micro)". - -The following elements are a bitfield of static capabilities of the daemon. See -#NMVersionInfoCapability for the available capability numbers. - -Since: 1.42 - - - - The "Capabilities" property - org.freedesktop.NetworkManager:Capabilities - -Capabilities readable au - - -The current set of capabilities. See NMCapability for currently -defined capability numbers. The array is guaranteed to -be sorted in ascending order without duplicates. - - - - The "State" property - org.freedesktop.NetworkManager:State - -State readable u - - -The overall state of the NetworkManager daemon. - -This takes state of all active connections and the connectivity state into account -to produce a single indicator of the network accessibility status. - -The graphical shells may use this property to provide network connection status -indication and applications may use this to check if Internet connection is -accessible. Shell that is able to cope with captive portals should use the -"Connectivity" property to decide whether to present a captive portal authentication -dialog. - -Returns: NMState - - - - The "Connectivity" property - org.freedesktop.NetworkManager:Connectivity - -Connectivity readable u - - -The result of the last connectivity check. The connectivity check is triggered -automatically when a default connection becomes available, periodically and by -calling a CheckConnectivity() method. - -This property is in general useful for the graphical shell to determine whether -the Internet access is being hijacked by an authentication gateway (a "captive -portal"). In such case it would typically present a web browser window to give -the user a chance to authenticate and call CheckConnectivity() when the user -submits a form or dismisses the window. - -To determine the whether the user is able to access the Internet without dealing -with captive portals (e.g. to provide a network connection indicator or disable -controls that require Internet access), the "State" property is more suitable. - -Returns: NMConnectivityState - - - - The "ConnectivityCheckAvailable" property - org.freedesktop.NetworkManager:ConnectivityCheckAvailable - -ConnectivityCheckAvailable readable b - - -Indicates whether connectivity checking service has been -configured. This may return true even if the service is not -currently enabled. - -This is primarily intended for use in a privacy control panel, -as a way to determine whether to show an option to -enable/disable the feature. - - - - The "ConnectivityCheckEnabled" property - org.freedesktop.NetworkManager:ConnectivityCheckEnabled - -ConnectivityCheckEnabled readwrite b - - -Indicates whether connectivity checking is enabled. This -property can also be written to disable connectivity -checking (as a privacy control panel might want to do). - - - - The "ConnectivityCheckUri" property - org.freedesktop.NetworkManager:ConnectivityCheckUri - -ConnectivityCheckUri readable s - - -The URI that NetworkManager will hit to check if there is internet connectivity. - - - - The "GlobalDnsConfiguration" property - org.freedesktop.NetworkManager:GlobalDnsConfiguration - -GlobalDnsConfiguration readwrite a{sv} - - -Dictionary of global DNS settings where the key is one of "searches", -"options" and "domains". The values for the "searches" and "options" keys -are string arrays describing the list of search domains and resolver -options, respectively. The value of the "domains" key is a second-level -dictionary, where each key is a domain name, and each key's value is a -third-level dictionary with the keys "servers" and "options". "servers" is -a string array of DNS servers, "options" is a string array of -domain-specific options. - - - - - diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index aee3ac66..b98b28ac 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -769,6 +769,11 @@ domains=ALL and these default values only matter if the per-profile values explicitly indicates to use the default from NetworkManager.conf.

+

+ Note that while nmcli supports various aliases and convenience features for configuring + properties, the settings in this section do not. For example, enum values usually only + can be configured via their numeric magic number. +

Example:

@@ -779,7 +784,7 @@ ipv6.ip6-privacy=0

-

Supported Properties

+

Supported Properties

Not all properties can be overwritten, only the following properties are supported to have their default values configured @@ -813,6 +818,10 @@ ipv6.ip6-privacy=0 +

connection.down-on-poweroff

+

Whether the connection will be brought down before the system is powered off.

+ +

connection.mud-url

If unspecified, MUD URL defaults to "none".

@@ -826,7 +835,13 @@ ipv6.ip6-privacy=0

connection.mdns

-

If unspecified, the ultimate default values depends on the DNS plugin. With systemd-resolved the default currently is "no" (0) and for all other plugins also "no" (0).

+

+ Currently only the systemd-resolve DNS plugin supports this setting. + If the setting is unspecified both in the profile and in the global + default here, then the default is determined by systemd-resolved. + See MulticastDNS= in + resolved.conf(5). +

connection.mptcp-flags

@@ -905,6 +920,10 @@ ipv6.ip6-privacy=0

If left unspecified, the value 3 (fqdn-encoded,fqdn-serv-update) is used.

+

ipv4.dhcp-send-release

+

Whether the DHCP client will send RELEASE message when bringing the connection down.

+ +

ipv4.dhcp-timeout

If left unspecified, the default value for the interface type is used.

@@ -960,6 +979,10 @@ ipv6.ip6-privacy=0

If left unspecified, the value 1 (fqdn-serv-update) is used.

+

ipv6.dhcp-send-release

+

Whether the DHCP client will send RELEASE message when bringing the connection down.

+ +

ipv6.dhcp-timeout

If left unspecified, the default value for the interface type is used.

@@ -971,8 +994,23 @@ ipv6.ip6-privacy=0

ipv6.ip6-privacy

-

If ipv6.ip6-privacy is unset, use the content of - "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback. +

If ipv6.ip6-privacy is unset, fall back to the original + value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager + started. +

+ + +

ipv6.temp-valid-lifetime

+

If ipv6.temp-valid-lifetime is unset, fall back to the + original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before + NetworkManager started. +

+ + +

ipv6.temp-preferred-lifetime

+

If ipv6.temp-preferred-lifetime is unset, fall back to + the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from + before NetworkManager started.

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 6e0036ab..2102feb9 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -747,6 +747,15 @@ + + + + + + + + + @@ -803,6 +812,7 @@ + diff --git a/docs/api/html/index.html b/docs/api/html/index.html index f43e0514..6f397e91 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.46.0 + for NetworkManager 1.47.90 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index 6dc24c5d..7443e3f6 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -780,9 +780,11 @@

dhcp-send-hostname, ipv4, ipv6
-
dhcp-timeout, ipv4, ipv6 +
dhcp-send-release, ipv4, ipv6
-
dhcp-vendor-class-identifier, ipv4 +
dhcp-timeout, ipv4, ipv6 +
+
dhcp-vendor-class-identifier, ipv4
org.freedesktop.NetworkManager.DHCP4Config, org.freedesktop.NetworkManager.DHCP4Config
@@ -792,22 +794,24 @@
org.freedesktop.NetworkManager.DHCP6Config:Options, The "Options" property
-
dns, ipv4, ipv6 +
dns, ipv4, ipv6
-
dns-data, ipv4, ipv6 +
dns-data, ipv4, ipv6
-
dns-options, ipv4, ipv6 +
dns-options, ipv4, ipv6
dns-over-tls, connection
-
dns-priority, ipv4, ipv6 +
dns-priority, ipv4, ipv6
-
dns-search, ipv4, ipv6 +
dns-search, ipv4, ipv6
domain-match, 802-1x
domain-suffix-match, 802-1x
+
down-on-poweroff, connection +
driver, match
duplex, 802-3-ethernet @@ -859,9 +863,9 @@

G

-
gateway, ipv4, ipv6 +
gateway, ipv4, ipv6
-
gateway-ping-timeout, connection +
gateway-ping-timeout, connection
generate-mac-address-mask, 802-3-ethernet, 802-11-wireless
@@ -895,13 +899,13 @@

I

-
id, connection, vlan, vxlan +
id, connection, vlan, vxlan
identity, 802-1x
-
ignore-auto-dns, ipv4, ipv6 +
ignore-auto-dns, ipv4, ipv6
-
ignore-auto-routes, ipv4, ipv6 +
ignore-auto-routes, ipv4, ipv6
ingress-priority-map, vlan
@@ -911,13 +915,13 @@
input-key, ip-tunnel
-
interface-name, connection, bond, bridge, match, team, vlan +
interface-name, connection, bond, bridge, match, team, vlan
ip4-auto-default-route, wireguard
ip6-auto-default-route, wireguard
-
ip6-privacy, ipv6 +
ip6-privacy, ipv6
@@ -957,15 +961,15 @@
limit, vxlan
-
link-local, ipv4 +
link-local, ipv4
link-watchers, team, team-port
listen-port, wireguard
-
lldp, connection +
lldp, connection
-
llmnr, connection +
llmnr, connection
local, ip-tunnel, vxlan
@@ -978,7 +982,9 @@
mac-address-blacklist, 802-3-ethernet, 802-11-wireless
-
mac-address-randomization, 802-11-wireless +
mac-address-denylist, 802-3-ethernet, 802-11-wireless +
+
mac-address-randomization, 802-11-wireless
org.freedesktop.NetworkManager, org.freedesktop.NetworkManager
@@ -1080,11 +1086,11 @@
org.freedesktop.NetworkManager:WwanHardwareEnabled, The "WwanHardwareEnabled" property
-
master, connection +
master, connection
max-age, bridge
-
may-fail, ipv4, ipv6 +
may-fail, ipv4, ipv6
mcast-rejoin-count, team
@@ -1092,11 +1098,11 @@
mcast-snooping-enable, ovs-bridge
-
mdns, connection +
mdns, connection
-
metered, connection +
metered, connection
-
method, ipv4, ipv6, proxy +
method, ipv4, ipv6, proxy
mka-cak, macsec
@@ -1108,15 +1114,15 @@
mppe-stateful, ppp
-
mptcp-flags, connection +
mptcp-flags, connection
mru, ppp
mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless, loopback
-
mud-url, connection +
mud-url, connection
-
multi-connect, connection +
multi-connect, connection
multi-queue, tun
@@ -1163,7 +1169,7 @@
network-name, wimax
-
never-default, ipv4, ipv6 +
never-default, ipv4, ipv6
NM80211ApFlags, enum NM80211ApFlags
@@ -1270,7 +1276,9 @@
only-from-default, hostname
-
optional, 802-1x +
openssl-ciphers, 802-1x +
+
optional, 802-1x
options, bond
@@ -1285,7 +1293,7 @@
p-key, infiniband
-
pac-file, 802-1x +
pac-file, 802-1x
pac-script, proxy
@@ -1301,13 +1309,13 @@
parity, serial
-
password, 802-1x, adsl, cdma, gsm, pppoe +
password, 802-1x, adsl, cdma, gsm, pppoe
-
password-flags, 802-1x, adsl, cdma, gsm, pppoe +
password-flags, 802-1x, adsl, cdma, gsm, pppoe
-
password-raw, 802-1x +
password-raw, 802-1x
-
password-raw-flags, 802-1x +
password-raw-flags, 802-1x
path, match
@@ -1321,67 +1329,67 @@
peers, wireguard
-
permissions, connection +
permissions, connection
persistent, vpn
-
phase1-auth-flags, 802-1x +
phase1-auth-flags, 802-1x
-
phase1-fast-provisioning, 802-1x +
phase1-fast-provisioning, 802-1x
-
phase1-peaplabel, 802-1x +
phase1-peaplabel, 802-1x
-
phase1-peapver, 802-1x +
phase1-peapver, 802-1x
-
phase2-altsubject-matches, 802-1x +
phase2-altsubject-matches, 802-1x
-
phase2-auth, 802-1x +
phase2-auth, 802-1x
-
phase2-autheap, 802-1x +
phase2-autheap, 802-1x
-
phase2-ca-cert, 802-1x +
phase2-ca-cert, 802-1x
-
phase2-ca-cert-password, 802-1x +
phase2-ca-cert-password, 802-1x
-
phase2-ca-cert-password-flags, 802-1x +
phase2-ca-cert-password-flags, 802-1x
-
phase2-ca-path, 802-1x +
phase2-ca-path, 802-1x
-
phase2-client-cert, 802-1x +
phase2-client-cert, 802-1x
-
phase2-client-cert-password, 802-1x +
phase2-client-cert-password, 802-1x
-
phase2-client-cert-password-flags, 802-1x +
phase2-client-cert-password-flags, 802-1x
-
phase2-domain-match, 802-1x +
phase2-domain-match, 802-1x
-
phase2-domain-suffix-match, 802-1x +
phase2-domain-suffix-match, 802-1x
-
phase2-private-key, 802-1x +
phase2-private-key, 802-1x
-
phase2-private-key-password, 802-1x +
phase2-private-key-password, 802-1x
-
phase2-private-key-password-flags, 802-1x +
phase2-private-key-password-flags, 802-1x
-
phase2-subject-match, 802-1x +
phase2-subject-match, 802-1x
pi, tun
-
pin, 802-1x, gsm +
pin, 802-1x, gsm
-
pin-flags, 802-1x, gsm +
pin-flags, 802-1x, gsm
pmf, 802-11-wireless-security
port, macsec, 802-3-ethernet
-
port-type, connection +
port-type, connection
port1, hsr
port2, hsr
-
powersave, 802-11-wireless +
powersave, 802-11-wireless
org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP
@@ -1415,13 +1423,13 @@
priority-traffic-class, dcb
-
private-key, 802-1x, wireguard +
private-key, 802-1x, wireguard
private-key-flags, wireguard
-
private-key-password, 802-1x +
private-key-password, 802-1x
-
private-key-password-flags, 802-1x +
private-key-password-flags, 802-1x
promiscuous, macvlan
@@ -1451,11 +1459,11 @@

R

-
ra-timeout, ipv6 +
ra-timeout, ipv6
-
rate, 802-11-wireless +
rate, 802-11-wireless
-
read-only, connection +
read-only, connection
refuse-chap, ppp
@@ -1469,23 +1477,23 @@
remote, ip-tunnel, vxlan
-
replace-local-rule, ipv4, ipv6 +
replace-local-rule, ipv4, ipv6
require-mppe, ppp
require-mppe-128, ppp
-
required-timeout, ipv4, ipv6 +
required-timeout, ipv4, ipv6
-
route-data, ipv4, ipv6 +
route-data, ipv4, ipv6
-
route-metric, ipv4, ipv6 +
route-metric, ipv4, ipv6
-
route-table, ipv4, ipv6 +
route-table, ipv4, ipv6
-
routes, ipv4, ipv6 +
routes, ipv4, ipv6
-
routing-rules, ipv4, ipv6 +
routing-rules, ipv4, ipv6
rsc, vxlan
@@ -1516,19 +1524,19 @@

S

-
s390-nettype, 802-3-ethernet +
s390-nettype, 802-3-ethernet
-
s390-options, 802-3-ethernet +
s390-options, 802-3-ethernet
-
s390-subchannels, 802-3-ethernet +
s390-subchannels, 802-3-ethernet
-
secondaries, connection +
secondaries, connection
secrets, vpn
-
security, 802-11-wireless +
security, 802-11-wireless
-
seen-bssids, 802-11-wireless +
seen-bssids, 802-11-wireless
send-delay, serial
@@ -1544,17 +1552,17 @@
sim-operator-id, gsm
-
slave-type, connection +
slave-type, connection
source-port-max, vxlan
source-port-min, vxlan
-
speed, 802-3-ethernet +
speed, 802-3-ethernet
ssid, 802-11-olpc-mesh, 802-11-wireless
-
stable-id, connection +
stable-id, connection
sticky, team-port
@@ -1564,9 +1572,9 @@
stp-enable, ovs-bridge
-
subject-match, 802-1x +
subject-match, 802-1x
-
system-ca-certs, 802-1x +
system-ca-certs, 802-1x
@@ -1579,13 +1587,17 @@
tap, macvlan
+
temp-preferred-lifetime, ipv6 +
+
temp-valid-lifetime, ipv6 +
tfilters, tc
timeout, vpn
-
timestamp, connection +
timestamp, connection
-
token, ipv6 +
token, ipv6
tos, ip-tunnel, vxlan
@@ -1597,11 +1609,11 @@
ttl, ip-tunnel, vxlan
-
tx-power, 802-11-wireless +
tx-power, 802-11-wireless
tx-queue-length, link
-
type, connection, bluetooth, ovs-interface +
type, connection, bluetooth, ovs-interface
@@ -1612,7 +1624,7 @@
username, adsl, cdma, gsm, pppoe
-
uuid, connection +
uuid, connection
@@ -1690,15 +1702,15 @@

W

-
wait-activation-delay, connection +
wait-activation-delay, connection
-
wait-device-timeout, connection +
wait-device-timeout, connection
-
wake-on-lan, 802-3-ethernet +
wake-on-lan, 802-3-ethernet
-
wake-on-lan-password, 802-3-ethernet +
wake-on-lan-password, 802-3-ethernet
-
wake-on-wlan, 802-11-wireless +
wake-on-wlan, 802-11-wireless
wep-key-flags, 802-11-wireless-security
@@ -1744,7 +1756,7 @@

Z

-
zone, connection +
zone, connection
diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 96afcda9..eba72972 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -3144,6 +3144,141 @@   + + +

NM_DEVICE_STATE_REASON_UNMANAGED_BY_DEFAULT

+

+ + +

= 69

+

+ + +

The device is unmanaged because the device type is unmanaged by default. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_EXTERNAL_DOWN

+

+ + +

= 70

+

+ + +

The device is unmanaged because it is an external device and is unconfigured (down or without addresses). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_LINK_NOT_INIT

+

+ + +

= 71

+

+ + +

The device is unmanaged because the link is not initialized by udev. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_QUITTING

+

+ + +

= 72

+

+ + +

The device is unmanaged because NetworkManager is quitting. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_SLEEPING

+

+ + +

= 73

+

+ + +

The device is unmanaged because networking is disabled or the system is suspended. Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_CONF

+

+ + +

= 74

+

+ + +

The device is unmanaged by user decision in NetworkManager.conf ('unmanaged' in a [device*] section). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_EXPLICIT

+

+ + +

= 75

+

+ + +

The device is unmanaged by explicit user decision (e.g. 'nmcli device set $DEV managed no'). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_SETTINGS

+

+ + +

= 76

+

+ + +

The device is unmanaged by user decision via settings plugin ('unmanaged-devices' for keyfile or 'NM_CONTROLLED=no' for ifcfg-rh). Since: 1.48

+

+ +  + + + +

NM_DEVICE_STATE_REASON_UNMANAGED_USER_UDEV

+

+ + +

= 77

+

+ + +

The device is unmanaged via udev rule. Since: 1.48

+

+ +  + @@ -3151,7 +3286,7 @@

enum NMMetered

-

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

+

The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.

For the connection profile only NM_METERED_UNKNOWN, NM_METERED_NO and NM_METERED_YES are allowed.

The device's metered state at runtime is determined by the profile which is currently active. If the profile explicitly specifies NM_METERED_NO or NM_METERED_YES, then the device's metered state is as such. If the connection profile leaves it undecided at NM_METERED_UNKNOWN (the default), then NetworkManager tries to guess the metered state, for example based on the device type or on DHCP options (like Android devices exposing a "ANDROID_METERED" DHCP vendor option). This then leads to either NM_METERED_GUESS_NO or NM_METERED_GUESS_YES.

Most applications probably should treat the runtime state NM_METERED_GUESS_YES like NM_METERED_YES, and all other states as not metered.

@@ -4144,6 +4279,21 @@   + + +

NM_CHECKPOINT_CREATE_FLAG_TRACK_INTERNAL_GLOBAL_DNS

+

+ + +

= 0x20

+

+ + +

during rollback, by default changes to global DNS via D-BUS interface are preserved. With this flag, the rollback reverts the global DNS changes made via D-Bus interface. Global DNS defined in [global-dns] section of NetworkManager.conf is not impacted by this flag. Since: 1.48.

+

+ +  +
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index 52539c2e..96992290 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -160,7 +160,9 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a autoconnect-slaves NMSettingConnectionAutoconnectSlaves (int32)   -Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. +Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. + +Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias. @@ -182,6 +184,13 @@ This feature requires a plugin which supports DNSOverTls. Otherwise, the setting +down-on-poweroff +int32 +-1 +Whether the connection will be brought down before the system is powered off. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as 0 (no). + + + gateway-ping-timeout uint32 0 @@ -239,9 +248,9 @@ Deprecated 1.46. Use "controller" instead, this is just an alias. -1 Whether mDNS is enabled for the connection. -The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). +The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin. -This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. +This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf. @@ -556,6 +565,13 @@ Certificate data is specified using a "scheme"; two are currently supported: blo +openssl-ciphers +string +  +Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols. + + + optional boolean FALSE @@ -1822,6 +1838,13 @@ This property is currently not implemented for DHCPv6. +dhcp-send-release +NMTernary (int32) +  +Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE. + + + dhcp-timeout int32 0 @@ -2179,6 +2202,13 @@ This property is currently not implemented for DHCPv6. +dhcp-send-release +NMTernary (int32) +  +Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE. + + + dhcp-timeout int32 0 @@ -2281,9 +2311,7 @@ Note that the gateway usually conflicts with routing that NetworkManager configu   Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). -Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". - -If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". +If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started. Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. @@ -2396,6 +2424,24 @@ Array of IPv6 route structures. Each IPv6 route structure is composed of an IPv +temp-preferred-lifetime +int32 +0 +The preferred lifetime of autogenerated temporary addresses, in seconds. + +If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started. + + + +temp-valid-lifetime +int32 +0 +The valid lifetime of autogenerated temporary addresses, in seconds. + +If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started. + + + token string   @@ -4230,6 +4276,13 @@ If the value contains more than one additional MAC addresses, one of them is cho +mac-address-denylist +array of string +  +If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55). + + + mtu uint32 0 @@ -4495,6 +4548,13 @@ Note that marking the network as hidden may be a privacy issue for you (in infra +mac-address-denylist +array of string +  +A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55"). + + + mac-address-randomization uint32 0 diff --git a/docs/api/html/nm-settings-ifcfg-rh.html b/docs/api/html/nm-settings-ifcfg-rh.html index 890e4643..cdeeabf6 100644 --- a/docs/api/html/nm-settings-ifcfg-rh.html +++ b/docs/api/html/nm-settings-ifcfg-rh.html @@ -354,6 +354,13 @@ Example: BSSID=00:1E:BD:64:83:21 It denies usage of the connection for any device whose address is listed. +mac-address-denylist +HWADDR_BLACKLIST(+) + +  +It denies usage of the connection for any device whose address is listed. + + seen-bssids (none)   @@ -913,6 +920,13 @@ Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12   whether the 802.1X authentication is optional + +openssl-ciphers +IEEE_8021X_OPENSSL_CIPHERS(+) + +  +Cipher string for tls setup of wpa_supplicant. + @@ -982,6 +996,15 @@ Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12   It denies usage of the connection for any device whose address is listed. +Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55" + + +mac-address-denylist +HWADDR_BLACKLIST(+) + +  +It denies usage of the connection for any device whose address is listed. + Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55" diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 6779fa4c..d998d502 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -241,6 +241,14 @@ Example: ssid=Quick Net Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 + +mac-address-denylist +  +list of MACs (separated with semicolons) +MAC address denylist. + +Example: mac-address-denylist= 00:22:68:12:79:A6;00:22:68:12:79:78 + @@ -280,6 +288,14 @@ Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79 Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 + +mac-address-denylist +  +list of MACs (separated with semicolons) +MAC address denylist. + +Example: mac-address-denylist= 00:22:68:12:79:A6;00:22:68:12:79:78 + diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 9d266d92..d91c80e3 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -141,6 +141,7 @@

connection.autoconnect-slaves

Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.

+

Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias.

Format: choice (NMSettingConnectionAutoconnectSlaves)

@@ -170,6 +171,16 @@ +

connection.down-on-poweroff

+ +

Whether the connection will be brought down before the system is powered off. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as "no" (0).

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

connection.gateway-ping-timeout

If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.

@@ -238,8 +249,8 @@

connection.mdns

Whether mDNS is enabled for the connection.

-

The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").

-

This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.

+

The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin.

+

This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf.

Format: choice (NMSettingConnectionMdns)

@@ -376,7 +387,7 @@

The connection.uuid is the real identifier of a profile. It cannot change and it must be unique. It is therefore often best to refer to a profile by UUID, for example with `nmcli connection up uuid $UUID`.

The UUID cannot be changed, except in offline mode. In that case, the special values "new", "generate" and "" are allowed to generate a new random UUID.

- Format: string

+ Format: a valid RFC4122 universally unique identifier (UUID).

@@ -479,9 +490,9 @@

802-1x.ca-cert

-

Contains the CA certificate if used by the EAP method specified in the "eap" property.

-

Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

-

Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

+

Contains the path to the CA certificate if used by the EAP method specified in the 802-1x.eap property.

+

This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Note that enabling 802-1x.system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

Format: filesystem path

@@ -516,8 +527,7 @@

802-1x.client-cert

-

Contains the client certificate if used by the EAP method specified in the "eap" property.

-

Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.

+

Contains the path to the client certificate if used by the EAP method specified in the 802-1x.eap property.

Format: filesystem path

@@ -575,6 +585,14 @@ +

802-1x.openssl-ciphers

+ +

Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols.

+

+ Format: string

+ + +

802-1x.optional

Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.

@@ -699,9 +717,9 @@

802-1x.phase2-ca-cert

-

Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.

-

Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

-

Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

+

Contains the path to the "phase 2" CA certificate if used by the EAP method specified in the 802-1x.phase2-auth or 802-1x.phase2-autheap properties.

+

This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Note that enabling 802-1x.system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.

Format: filesystem path

@@ -736,8 +754,7 @@

802-1x.phase2-client-cert

-

Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.

-

Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.

+

Contains the path to the "phase 2" client certificate if used by the EAP method specified in the 802-1x.phase2-auth or 802-1x.phase2-autheap properties.

Format: filesystem path

@@ -779,8 +796,7 @@

802-1x.phase2-private-key

-

Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".

-

Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.

+

The path to the "phase 2" inner private key when the 802-1x.phase2-auth or 802-1x.phase2-autheap property is set to "tls".

Format: filesystem path

@@ -788,7 +804,7 @@

802-1x.phase2-private-key-password

-

The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.

+

The password used to decrypt the "phase 2" private key specified in the 802-1x.phase2-private-key property. This is normally used by secret agents, not directly by users.

Format: string

@@ -835,9 +851,7 @@

802-1x.private-key

-

Contains the private key when the "eap" property is set to "tls".

-

Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.

-

WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.

+

The path to the private key when the 802-1.eap property is set to "tls".

Format: filesystem path

@@ -845,7 +859,7 @@

802-1x.private-key-password

-

The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.

+

The password used to decrypt the private key specified in the 802-1x.private-key property. This is normally used by secret agents, not directly by users.

Format: string

@@ -2772,7 +2786,7 @@ Alias: ip4

A list of IPv4 addresses and their prefix length. Multiple addresses can be separated by comma. For example "192.168.1.5/24, 10.1.0.5/24". The addresses are listed in decreasing priority, meaning the first address will be the primary address.

- Format: list of ipv4.addresses objects

+ Format: a comma separated list of addresses

@@ -2886,6 +2900,16 @@ +

ipv4.dhcp-send-release

+ +

Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

ipv4.dhcp-timeout

A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).

@@ -2925,7 +2949,7 @@

When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.

The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.

- Format: list of strings

+ Format: a comma separated list of DNS options

@@ -3150,7 +3174,7 @@ For details see also `man ip-route`.

- Format: list of ipv4.routes objects

+ Format: a comma separated list of routes

@@ -3166,7 +3190,7 @@ fixed priority. Example: priority 5 from 192.167.4.0/24 table 45

- Format: list of ipv4.routing-rules objects

+ Format: a comma separated list of routing rules

@@ -3196,7 +3220,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

If not specified, when creating a new profile the default is "default".

Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.

- Format: choice (NMSettingIP6ConfigAddrGenMode)

+ Format: one of "eui64" (0), "stable-privacy" (1), "default" (3) or "default-or-eui64" (2)

Valid values: eui64 (0), stable-privacy (1), default-or-eui64 (2), default (3)

@@ -3208,7 +3232,7 @@ Example: priority 5 from 192.167.4.0/24 table 45 Alias: ip6

A list of IPv6 addresses and their prefix length. Multiple addresses can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64". The addresses are listed in decreasing priority, meaning the first address will be the primary address. This can make a difference with IPv6 source address selection (RFC 6724, section 5).

- Format: list of ipv6.addresses objects

+ Format: a comma separated list of addresses

@@ -3284,6 +3308,16 @@ Example: priority 5 from 192.167.4.0/24 table 45 +

ipv6.dhcp-send-release

+ +

Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is "default" (-1). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.

+

+ Format: ternary

+

+ Valid values: true/yes/on, false/no/off, default/unknown

+ + +

ipv6.dhcp-timeout

A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).

@@ -3315,7 +3349,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.

The valid "ipv4.dns-options" and "ipv6.dns-options" get merged together.

- Format: list of strings

+ Format: a comma separated list of DNS options

@@ -3381,8 +3415,7 @@ Example: priority 5 from 192.167.4.0/24 table 45

ipv6.ip6-privacy

Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).

-

Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".

-

If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".

+

If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started.

Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.

Format: choice (NMSettingIP6ConfigPrivacy)

@@ -3554,7 +3587,7 @@ Example: priority 5 from 192.167.4.0/24 table 45 For details see also `man ip-route`.

- Format: list of ipv6.routes objects

+ Format: a comma separated list of routes

@@ -3570,7 +3603,29 @@ fixed priority. Example: priority 5 from 1:2:3::5/128 table 45

- Format: list of ipv6.routing-rules objects

+ Format: a comma separated list of routing rules

+ + + +

ipv6.temp-preferred-lifetime

+ +

The preferred lifetime of autogenerated temporary addresses, in seconds.

+

If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started.

+

+ Format: integer

+

+ Valid values: 0 - 2147483647

+ + + +

ipv6.temp-valid-lifetime

+ +

The valid lifetime of autogenerated temporary addresses, in seconds.

+

If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started.

+

+ Format: integer

+

+ Valid values: 0 - 2147483647

@@ -5042,7 +5097,7 @@ Linux traffic control subsystem

- Format: list of tc.qdiscs objects

+ Format: GPtrArray(NMTCQdisc)

@@ -5144,7 +5199,7 @@ Linux traffic control subsystem

- Format: list of tc.tfilters objects

+ Format: GPtrArray(NMTCTfilter)

@@ -6057,6 +6112,14 @@ Linux traffic control subsystem +

802-3-ethernet.mac-address-denylist

+ +

If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).

+

+ Format: list of MAC addresses

+ + +

802-3-ethernet.mtu

@@ -6349,6 +6412,14 @@ Linux traffic control subsystem +

802-11-wireless.mac-address-denylist

+ +

A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").

+

+ Format: list of MAC addresses

+ + +

802-11-wireless.mac-address-randomization

One of "default" (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization), "never" (1) (never randomize the MAC address), or "always" (2) (always randomize the MAC address).

diff --git a/docs/api/html/settings-802-11-wireless.html b/docs/api/html/settings-802-11-wireless.html index 0d402d10..c740d610 100644 --- a/docs/api/html/settings-802-11-wireless.html +++ b/docs/api/html/settings-802-11-wireless.html @@ -136,6 +136,12 @@ Note that marking the network as hidden may be a privacy issue for you (in infra A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply. Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55"). +
mac-address-denylist
+
array of string
+

+A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").
+
+
 
mac-address-randomization

 
uint32

 
0

diff --git a/docs/api/html/settings-802-1x.html b/docs/api/html/settings-802-1x.html
index f72bffab..e889c1be 100644
--- a/docs/api/html/settings-802-1x.html
+++ b/docs/api/html/settings-802-1x.html
@@ -146,6 +146,12 @@ Certificate data is specified using a "scheme"; two are currently supported: blo
 Identity string for EAP authentication methods.  Often the user's user or login name.
 
 
+
openssl-ciphers

+
string

+

+Define openssl_ciphers for wpa_supplicant. Openssl sometimes moves ciphers among SECLEVELs, thus compiled-in default value in wpa_supplicant (as modified by some linux distributions) sometimes prevents to connect to old servers that do not support new protocols.
+
+
 
optional

 
boolean

 
FALSE

diff --git a/docs/api/html/settings-802-3-ethernet.html b/docs/api/html/settings-802-3-ethernet.html
index a182b834..9323cf39 100644
--- a/docs/api/html/settings-802-3-ethernet.html
+++ b/docs/api/html/settings-802-3-ethernet.html
@@ -110,6 +110,12 @@ If the value contains more than one additional MAC addresses, one of them is cho
 If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
 
 
+
mac-address-denylist

+
array of string

+

+If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+
+
 
mtu

 
uint32

 
0

diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index afd9d6cc..06693539 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -97,7 +97,9 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a
 
autoconnect-slaves

 
NMSettingConnectionAutoconnectSlaves (int32)

 

-Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
+Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
+
+Deprecated 1.46. Use "autoconnect-ports" instead, this is just an alias.
 
 
 
controller

@@ -116,6 +118,12 @@ The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "oppor
 This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
 
 
+
down-on-poweroff

+
int32

+
-1

+Whether the connection will be brought down before the system is powered off.  The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as 0 (no).
+
+
 
gateway-ping-timeout

 
uint32

 
0

@@ -167,9 +175,9 @@ Deprecated 1.46. Use "controller" instead, this is just an alias.
 
-1

 Whether mDNS is enabled for the connection.
 
-The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
+The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin.
 
-This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
+This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. Currently the only supported DNS plugin is systemd-resolved. For systemd-resolved, the default is configurable via MulticastDNS= setting in resolved.conf.
 
 
 
metered

diff --git a/docs/api/html/settings-ipv4.html b/docs/api/html/settings-ipv4.html
index 587db9c2..2ce34426 100644
--- a/docs/api/html/settings-ipv4.html
+++ b/docs/api/html/settings-ipv4.html
@@ -159,6 +159,12 @@ This property is currently not implemented for DHCPv6.
 If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
 
 
+
dhcp-send-release

+
NMTernary (int32)

+

+Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.
+
+
 
dhcp-timeout

 
int32

 
0

diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html
index 54b78c27..ae18ca4c 100644
--- a/docs/api/html/settings-ipv6.html
+++ b/docs/api/html/settings-ipv6.html
@@ -173,6 +173,12 @@ This property is currently not implemented for DHCPv6.
 If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
 
 
+
dhcp-send-release

+
NMTernary (int32)

+

+Whether the DHCP client will send RELEASE message when bringing the connection down. The default value is -1 (default). When the default value is specified, then the global value from NetworkManager configuration is looked up, if not set, it is considered as FALSE.
+
+
 
dhcp-timeout

 
int32

 
0

@@ -266,9 +272,7 @@ Note that the gateway usually conflicts with routing that NetworkManager configu
 

 Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).
 
-Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".
-
-If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".
+If set to "-1" (unknown) for a connection, the value is taken from the global "ipv6.ip6-privacy" setting. If the global setting is unspecified or also set to "-1", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/use_tempaddr" from before NetworkManager started.
 
 Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.
 
@@ -368,6 +372,22 @@ Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv
 Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).
 
 
+
temp-preferred-lifetime

+
int32

+
0

+The preferred lifetime of autogenerated temporary addresses, in seconds.
+
+If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-preferred-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_prefered_lft" from before NetworkManager started.
+
+
+
temp-valid-lifetime

+
int32

+
0

+The valid lifetime of autogenerated temporary addresses, in seconds.
+
+If set to "0" (unknown) for a connection, the value is taken from the global "ipv6.temp-valid-lifetime" setting. If the global setting is unspecified or also set to "0", the value is set from the original value of "/proc/sys/net/ipv6/conf/<iface>/temp_valid_lft" from before NetworkManager started.
+
+
 
token

 
string

 

diff --git a/docs/api/network-manager-docs.xml b/docs/api/network-manager-docs.xml
index faee8799..a7cf2461 100644
--- a/docs/api/network-manager-docs.xml
+++ b/docs/api/network-manager-docs.xml
@@ -1,6 +1,6 @@
 
-
 ]>
 
diff --git a/docs/api/network-manager-overrides.txt b/docs/api/network-manager-overrides.txt
new file mode 100644
index 00000000..e69de29b
diff --git a/docs/api/settings-spec.xml b/docs/api/settings-spec.xml
deleted file mode 100644
index 3a1105e0..00000000
--- a/docs/api/settings-spec.xml
+++ /dev/null
@@ -1,575 +0,0 @@
-
-
-Configuration SettingsconnectionGeneral Connection Profile Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionauth-retriesauth-retriesint32-1The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.
-
-Currently, this only applies to 802-1x authentication.autoconnectautoconnectbooleanTRUEWhether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
-
-Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.
-
-Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.
-
-If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.
-
-Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.autoconnect-portsautoconnect-portsint32-1Whether or not ports of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for controller connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave port connections untouched, 1: activate all the port connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-ports is read to determine the real value. If it is default as well, this fallbacks to 0.autoconnect-priorityautoconnect-priorityint320The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.autoconnect-retriesautoconnect-retriesint32-1The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.autoconnect-slavesautoconnect-slavesNMSettingConnectionAutoconnectSlaves (int32)Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.controllercontrollerstringInterface name of the controller device or UUID of the controller connection.dns-over-tlsdns-over-tlsint32-1Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
-
-The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.
-
-This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.gateway-ping-timeoutgateway-ping-timeoutuint320If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.ididstringA human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".interface-nameinterface-namestringThe name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).
-
-For software devices this specifies the name of the created device.
-
-For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.lldplldpint32-1Whether LLDP is enabled for the connection.llmnrllmnrint32-1Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.
-
-The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").
-
-This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.mastermasterstringInterface name of the master device or UUID of the master connection.
-
-Deprecated 1.46. Use "controller" instead, this is just an alias.mdnsmdnsint32-1Whether mDNS is enabled for the connection.
-
-The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
-
-This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.meteredmeteredNMMetered (int32)Whether the connection is metered.
-
-When updating this property on a currently activated connection, the change takes effect immediately.mptcp-flagsmptcp-flagsuint320Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.
-
-If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.
-
-The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.
-
-Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.
-
-Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.
-
-When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.
-
-If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.
-
-NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.
-
-Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).mud-urlmud-urlstringIf configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".
-
-The special value "none" is allowed to indicate that no MUD URL is used.
-
-If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".multi-connectmulti-connectint320Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.permissionspermissionsarray of stringAn array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".
-
-At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.port-typeport-typestringSetting name of the device type of this port's controller connection (eg, "bond"), or NULL if this connection is not a port.read-onlyread-onlybooleanFALSEThis property is deprecated and has no meaning.secondariessecondariesarray of stringList of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.slave-typeslave-typestringSetting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
-
-Deprecated 1.46. Use "port-type" instead, this is just an alias.stable-idstable-idstringThis represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
-
-The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used to derive the DHCP client identifier with ipv4.dhcp-client-id=stable, the DHCPv6 DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid] and the DHCP IAID with ipv4.iaid=stable and ipv6.iaid=stable.
-
-Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
-
-The '$' character is treated special to perform dynamic substitutions at activation time. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${NETWORK_SSID}", "${BOOT}", "${RANDOM}".  These effectively create unique IDs per-connection, per-device, per-SSID, per-boot, or every time.  The "${CONNECTION}" uses the profile's connection.uuid, the "${DEVICE}" uses the interface name of the device and "${MAC}" the permanent MAC address of the device. "${NETWORK_SSID}" uses the SSID for Wi-Fi networks and falls back to "${CONNECTION}" on other networks. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$".  For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
-
-If the value is unset, a global connection default is consulted. If the value is still unset, the default is "default${CONNECTION}" go generate an ID unique per connection profile.timestamptimestampuint640The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
-
-NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).typetypestringBase type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).uuiduuidstringA universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.
-
-The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").wait-activation-delaywait-activation-delayint32-1Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
-
-The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.wait-device-timeoutwait-device-timeoutint32-1Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.
-
-The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.zonezonestringThe trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.
-
-When updating this property on a currently activated connection, the change takes effect immediately.
6lowpan6LoWPAN Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionparentparentstringIf given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.
802-1xIEEE 802.1x Authentication Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionaltsubject-matchesaltsubject-matchesarray of stringList of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.anonymous-identityanonymous-identitystringAnonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.auth-timeoutauth-timeoutint320A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.ca-certca-certbyte arrayContains the CA certificate if used by the EAP method specified in the "eap" property.
-
-Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
-
-Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.ca-cert-passwordca-cert-passwordstringThe password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.ca-cert-password-flagsca-cert-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "ca-cert-password" property.ca-pathca-pathstringUTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.
-
-If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.client-certclient-certbyte arrayContains the client certificate if used by the EAP method specified in the "eap" property.
-
-Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.client-cert-passwordclient-cert-passwordstringThe password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.client-cert-password-flagsclient-cert-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "client-cert-password" property.domain-matchdomain-matchstringConstraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.domain-suffix-matchdomain-suffix-matchstringConstraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.eapeaparray of stringThe allowed EAP method to be used when authenticating to the network with 802.1x.  Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast".  Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.identityidentitystringIdentity string for EAP authentication methods.  Often the user's user or login name.optionaloptionalbooleanFALSEWhether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.pac-filepac-filestringUTF-8 encoded file path containing PAC for EAP-FAST.passwordpasswordstringUTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.password-rawpassword-rawbyte arrayPassword used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.password-raw-flagspassword-raw-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password-raw" property.phase1-auth-flagsphase1-auth-flagsuint320Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. TLS time checks can be also disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x and tls_disable_time_checks settings. See the wpa_supplicant documentation for more details.phase1-fast-provisioningphase1-fast-provisioningstringEnables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning).  See the wpa_supplicant documentation for more details.phase1-peaplabelphase1-peaplabelstringForces use of the new PEAP label during key derivation.  Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1.  Set to "1" to force use of the new PEAP label.  See the wpa_supplicant documentation for more details.phase1-peapverphase1-peapverstringForces which PEAP version is used when PEAP is set as the EAP method in the "eap" property.  When unset, the version reported by the server will be used.  Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version.  To do so, this property may be set to "0" or "1" to force that specific PEAP version.phase2-altsubject-matchesphase2-altsubject-matchesarray of stringList of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.phase2-authphase2-authstringSpecifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method.  For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.phase2-autheapphase2-autheapstringSpecifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.phase2-ca-certphase2-ca-certbyte arrayContains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
-
-Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
-
-Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.phase2-ca-cert-passwordphase2-ca-cert-passwordstringThe password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.phase2-ca-cert-password-flagsphase2-ca-cert-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "phase2-ca-cert-password" property.phase2-ca-pathphase2-ca-pathstringUTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.
-
-If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.phase2-client-certphase2-client-certbyte arrayContains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
-
-Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.phase2-client-cert-passwordphase2-client-cert-passwordstringThe password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.phase2-client-cert-password-flagsphase2-client-cert-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "phase2-client-cert-password" property.phase2-domain-matchphase2-domain-matchstringConstraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.phase2-domain-suffix-matchphase2-domain-suffix-matchstringConstraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.phase2-private-keyphase2-private-keybyte arrayContains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".
-
-Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.phase2-private-key-passwordphase2-private-key-passwordstringThe password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.phase2-private-key-password-flagsphase2-private-key-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "phase2-private-key-password" property.phase2-subject-matchphase2-subject-matchstringSubstring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.pinpinstringPIN used for EAP authentication methods.pin-flagspin-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "pin" property.private-keyprivate-keybyte arrayContains the private key when the "eap" property is set to "tls".
-
-Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
-
-WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users.  Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.private-key-passwordprivate-key-passwordstringThe password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.private-key-password-flagsprivate-key-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key-password" property.subject-matchsubject-matchstringSubstring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.system-ca-certssystem-ca-certsbooleanFALSEWhen TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch.  The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).
adslADSL Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionencapsulationencapsulationstringEncapsulation of ADSL connection.  Can be "vcmux" or "llc".passwordpasswordstringPassword used to authenticate with the ADSL service.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.protocolprotocolstringADSL connection protocol.  Can be "pppoa", "pppoe" or "ipoatm".usernameusernamestringUsername used to authenticate with the ADSL service.vcivciuint320VCI of ADSL connectionvpivpiuint320VPI of ADSL connection
bluetoothBluetooth Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionbdaddrbdaddrbyte arrayThe Bluetooth address of the device.typetypestringEither "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.
bondBonding Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptioninterface-nameinterface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bond's interface name.optionsoptionsdict of string to string{'mode': 'balance-rr'}Dictionary of key/value pairs of bonding options.  Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
bridgeBridging Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionageing-timeageing-timeuint32300The Ethernet MAC address aging time, in seconds.forward-delayforward-delayuint3215The Spanning Tree Protocol (STP) forwarding delay, in seconds.group-addressgroup-addressbyte arrayIf specified, The MAC address of the multicast group this bridge uses for STP.
-
-The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.group-forward-maskgroup-forward-maskuint320A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.hello-timehello-timeuint322The Spanning Tree Protocol (STP) hello time, in seconds.interface-nameinterface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bridge's interface name.mac-addressmac-addressbyte arrayIf specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.
-
-If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge.max-agemax-ageuint3220The Spanning Tree Protocol (STP) maximum message age, in seconds.multicast-hash-maxmulticast-hash-maxuint324096Set maximum size of multicast hash table (value must be a power of 2).multicast-last-member-countmulticast-last-member-countuint322Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.multicast-last-member-intervalmulticast-last-member-intervaluint64100Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.multicast-membership-intervalmulticast-membership-intervaluint6426000Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.multicast-queriermulticast-querierbooleanFALSEEnable or disable sending of multicast queries by the bridge. If not specified the option is disabled.multicast-querier-intervalmulticast-querier-intervaluint6425500If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.multicast-query-intervalmulticast-query-intervaluint6412500Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.multicast-query-response-intervalmulticast-query-response-intervaluint641000Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.multicast-query-use-ifaddrmulticast-query-use-ifaddrbooleanFALSEIf enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.multicast-routermulticast-routerstringSets bridge's multicast router. Multicast-snooping must be enabled for this option to work.
-
-Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).multicast-snoopingmulticast-snoopingbooleanTRUEControls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.multicast-startup-query-countmulticast-startup-query-countuint322Set the number of IGMP queries to send during startup phase.multicast-startup-query-intervalmulticast-startup-query-intervaluint643125Sets the time (in deciseconds) between queries sent out at startup to determine membership information.prioritypriorityuint3232768Sets the Spanning Tree Protocol (STP) priority for this bridge.  Lower values are "better"; the lowest priority bridge will be elected the root bridge.stpstpbooleanTRUEControls whether Spanning Tree Protocol (STP) is enabled for this bridge.vlan-default-pvidvlan-default-pviduint321The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.vlan-filteringvlan-filteringbooleanFALSEControl whether VLAN filtering is enabled on the bridge.vlan-protocolvlan-protocolstringIf specified, the protocol used for VLAN filtering.
-
-Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.vlan-stats-enabledvlan-stats-enabledbooleanFALSEControls whether per-VLAN stats accounting is enabled.vlansvlansarray of vardictArray of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property.
-
-In nmcli the VLAN list can be specified with the following syntax:
-
-$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
-
-where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
bridge-portBridge Port Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionhairpin-modehairpin-modebooleanFALSEEnables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.path-costpath-costuint32100The Spanning Tree Protocol (STP) port cost for destinations via this port.prioritypriorityuint3232The Spanning Tree Protocol (STP) priority of this bridge port.vlansvlansarray of vardictArray of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.
-
-In nmcli the VLAN list can be specified with the following syntax:
-
-$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
-
-where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
cdmaCDMA-based Mobile Broadband Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.numbernumberstringThe number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
dcbData Center Bridging Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionapp-fcoe-flagsapp-fcoe-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-fcoe-modeapp-fcoe-modestringThe FCoE controller mode; either "fabric" or "vn2vn".
-
-Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".app-fcoe-priorityapp-fcoe-priorityint32-1The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the 0x1 (enable) flag.app-fip-flagsapp-fip-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-fip-priorityapp-fip-priorityint32-1The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the 0x1 (enable) flag.app-iscsi-flagsapp-iscsi-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).app-iscsi-priorityapp-iscsi-priorityint32-1The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the 0x1 (enable) flag.priority-bandwidthpriority-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.priority-flow-controlpriority-flow-controlarray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.priority-flow-control-flagspriority-flow-control-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).priority-group-bandwidthpriority-group-bandwidtharray of uint32An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.priority-group-flagspriority-group-flagsNMSettingDcbFlags (uint32)Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of 0x1 (enable), 0x2 (advertise), and 0x4 (willing).priority-group-idpriority-group-idarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.priority-strict-bandwidthpriority-strict-bandwidtharray of uint32An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.priority-traffic-classpriority-traffic-classarray of uint32An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
dummyDummy Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Description
ethtoolEthtool Ethernet Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Description
genericGeneric Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondevice-handlerdevice-handlerstringName of the device handler that will be invoked to add and delete the device for this connection. The name can only contain ASCII alphanumeric characters and '-', '_', '.'. It cannot start with '.'.
-
-See the NetworkManager-dispatcher(8) man page for more details about how to write the device handler.
-
-By setting this property the generic connection becomes "virtual", meaning that it can be activated without an existing device; the device will be created at the time the connection is started by invoking the device-handler.
gsmGSM-based Mobile Broadband Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionapnapnstringThe GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
-
-If the APN is unset (the default) then it may be detected based on "auto-config" setting. The property can be explicitly set to the empty string to prevent that and use no APN.auto-configauto-configbooleanFALSEWhen TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.device-iddevice-idstringThe device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.home-onlyhome-onlybooleanFALSEWhen TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.initial-eps-bearer-apninitial-eps-bearer-apnstringFor LTE modems, this sets the APN for the initial EPS bearer that is set up when attaching to the network.  Setting this parameter implies initial-eps-bearer-configure to be TRUE.initial-eps-bearer-configureinitial-eps-bearer-configurebooleanFALSEFor LTE modems, this setting determines whether the initial EPS bearer shall be configured when bringing up the connection.  It is inferred TRUE if initial-eps-bearer-apn is set.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.network-idnetwork-idstringThe Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.numbernumberstringLegacy setting that used to help establishing PPP data sessions for GSM-based modems.passwordpasswordstringThe password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.pinpinstringIf the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.pin-flagspin-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "pin" property.sim-idsim-idstringThe SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.sim-operator-idsim-operator-idstringA MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.usernameusernamestringThe username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.
infinibandInfiniband Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmac-addressmac-addressbyte arrayIf specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.p-keyp-keyint32-1The InfiniBand p-key to use for this device. A value of -1 means to use the default p-key (aka "the p-key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit 0x8000 is set if it is a "full membership" p-key. The values 0 and 0x8000 are not allowed.
-
-With the p-key set, the interface name is always "$parent.$p_key". Setting "connection.interface-name" to another name is not supported.
-
-Note that kernel will internally always set the full membership bit, although the interface name does not reflect that. Usually the user would want to configure a full membership p-key with 0x8000 flag set.parentparentstringThe interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".transport-modetransport-modestringThe IP-over-InfiniBand transport mode. Either "datagram" or "connected".
ipv4IPv4 Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionaddress-dataaddress-dataarray of vardictArray of IPv4 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesaddressesarray of array of uint32Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.
-Array of IPv4 address structures.  Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.auto-route-ext-gwauto-route-ext-gwNMTernary (int32)VPN connections will default to add the route automatically unless this setting is set to FALSE.
-
-For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutdad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
-
-A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-client-iddhcp-client-idstringA string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.
-
-The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.
-
-The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.
-
-The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.
-
-The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
-
-The special value "none" prevents any client identifier from being sent. Note that this is normally not recommended.
-
-If unset, a globally configured default from NetworkManager.conf is used. If still unset, the default depends on the DHCP plugin. The internal dhcp client will default to "mac" and the dhclient plugin will try to use one from its config file if present, or won't sent any client-id otherwise.dhcp-dscpdhcp-dscpstringSpecifies the value for the DSCP field (traffic class) of the IP header. When empty, the global default value is used; if no global default is specified, it is assumed to be "CS0". Allowed values are: "CS0", "CS4" and "CS6".
-
-The property is currently valid only for IPv4, and it is supported only by the "internal" DHCP plugin.dhcp-fqdndhcp-fqdnstringIf the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.dhcp-hostnamedhcp-hostnamestringIf the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.dhcp-hostname-flagsdhcp-hostname-flagsuint320Flags for the DHCP hostname and FQDN.
-
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
-
-When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname".
-
-For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
-
-For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.
-
-The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.dhcp-reject-serversdhcp-reject-serversarray of stringArray of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
-
-For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").
-
-This property is currently not implemented for DHCPv6.dhcp-send-hostnamedhcp-send-hostnamebooleanTRUEIf TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.dhcp-timeoutdhcp-timeoutint320A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).
-
-Set to 2147483647 (MAXINT32) for infinity.dhcp-vendor-class-identifierdhcp-vendor-class-identifierstringThe Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.dnsdnsarray of uint32Array of IP addresses of DNS servers (as network-byte-order integers)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options to be added to resolv.conf.
-
-NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
-
-The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
-
-In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
-
-The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
-
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-prioritydns-priorityint320DNS servers priority.
-
-The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
-
-Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
-
-Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
-
-Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
-
-When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
-
-When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.
-
-When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins.  If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.dns-searchdns-searcharray of stringList of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
-
-When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.
-
-When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).gatewaygatewaystringThe gateway associated with this configuration. This is only meaningful if "addresses" is also set.
-
-Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.
-
-Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".ignore-auto-dnsignore-auto-dnsbooleanFALSEWhen "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesignore-auto-routesbooleanFALSEWhen "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.link-locallink-localint320Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.
-
-When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".may-failmay-failbooleanTRUEIf TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.methodmethodstringIP configuration method.
-
-NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
-
-In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
-
-For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
-
-For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.never-defaultnever-defaultbooleanFALSEIf TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.replace-local-rulereplace-local-ruleNMTernary (int32)Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.required-timeoutrequired-timeoutint32-1The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
-
-This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
-
-Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.
-
-A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).route-dataroute-dataarray of vardictArray of IPv4 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'next-hop' entry, containing the next hop IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.route-metricroute-metricint64-1The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.route-tableroute-tableuint320Enable policy routing (source routing) and set the routing table used when adding routes.
-
-This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
-
-If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.
-
-Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.routesroutesarray of array of uint32Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.
-Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)routing-rulesrouting-rulesarray of 'a{sv}'Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).
ipv6IPv6 Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionaddr-gen-modeaddr-gen-modeint323Configure the method for creating the IPv6 interface identifier of addresses for RFC4862 IPv6 Stateless Address Autoconfiguration and IPv6 Link Local.
-
-The permitted values are: 0 (eui64), 1 (stable-privacy). 2 (default-or-eui64) or 3 (default).
-
-If the property is set to "eui64", the addresses will be generated using the interface token derived from the hardware address. This makes the host part of the address constant, making it possible to track the host's presence when it changes networks. The address changes when the interface hardware is replaced. If a duplicate address is detected, there is no fallback to generate another address. When configured, the "ipv6.token" is used instead of the MAC address to generate addresses for stateless autoconfiguration.
-
-If the property is set to "stable-privacy", the interface identifier is generated as specified by RFC7217. This works by hashing a host specific key (see NetworkManager(8) manual), the interface name, the connection's "connection.stable-id" property and the address prefix.  This improves privacy by making it harder to use the address to track the host's presence as every prefix and network has a different identifier. Also, the address is stable when the network interface hardware is replaced.
-
-The special values "default" and "default-or-eui64" will fallback to the global connection default as documented in the NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively.
-
-For libnm, the property defaults to "default" since 1.40.  Previously it used to default to "stable-privacy".  On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions.
-
-Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.address-dataaddress-dataarray of vardictArray of IPv6 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.addressesaddressesarray of legacy IPv6 address struct (a(ayuay))Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.
-Array of IPv6 address structures.  Each IPv6 address structure is composed of an IPv6 address, a prefix length (0 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.auto-route-ext-gwauto-route-ext-gwNMTernary (int32)VPN connections will default to add the route automatically unless this setting is set to FALSE.
-
-For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.dad-timeoutdad-timeoutint32-1Maximum timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail. The property is currently implemented only for IPv4.
-
-A zero value means that no duplicate address detection is performed, -1 means the default value (either the value configured globally in NetworkManger.conf or 200ms).  A value greater than zero is a timeout in milliseconds.  Note that the time intervals are subject to randomization as per RFC 5227 and so the actual duration can be between half and the full time specified in this property.dhcp-dscpdhcp-dscpstringSpecifies the value for the DSCP field (traffic class) of the IP header. When empty, the global default value is used; if no global default is specified, it is assumed to be "CS0". Allowed values are: "CS0", "CS4" and "CS6".
-
-The property is currently valid only for IPv4, and it is supported only by the "internal" DHCP plugin.dhcp-duiddhcp-duidstringA string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option.
-
-The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id.
-
-The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk.
-
-The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt").
-
-When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.dhcp-hostnamedhcp-hostnamestringIf the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.dhcp-hostname-flagsdhcp-hostname-flagsuint320Flags for the DHCP hostname and FQDN.
-
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) and 0x4 (fqdn-no-update).  When no FQDN flag is set and 0x8 (fqdn-clear-flags) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and 0x8 (fqdn-clear-flags) is not set, the standard FQDN flags are set in the request: 0x1 (fqdn-serv-update), 0x2 (fqdn-encoded) for IPv4 and 0x1 (fqdn-serv-update) for IPv6.
-
-When this property is set to the default value 0x0 (none), a global default is looked up in NetworkManager configuration. If that value is unset or also 0x0 (none), then the standard FQDN flags described above are sent in the DHCP requests.dhcp-iaiddhcp-iaidstringA string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The string can be a 32-bit number (either decimal, hexadecimal or as colon separated hexadecimal numbers). Alternatively it can be set to the special values "mac", "perm-mac", "ifname" or "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname".
-
-For DHCPv4, the IAID is only used with "ipv4.dhcp-client-id" values "duid" and "ipv6-duid" to generate the client-id.
-
-For DHCPv6, note that at the moment this property is only supported by the "internal" DHCPv6 plugin. The "dhclient" DHCPv6 plugin always derives the IAID from the MAC address.
-
-The actually used DHCPv6 IAID for a currently activated interface is exposed in the lease information of the device.dhcp-pd-hintdhcp-pd-hintstringA IPv6 address followed by a slash and a prefix length. If set, the value is sent to the DHCPv6 server as hint indicating the prefix delegation (IA_PD) we want to receive. To only hint a prefix length without prefix, set the address part to the zero address (for example "::/60").dhcp-reject-serversdhcp-reject-serversarray of stringArray of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
-
-For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").
-
-This property is currently not implemented for DHCPv6.dhcp-send-hostnamedhcp-send-hostnamebooleanTRUEIf TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.dhcp-timeoutdhcp-timeoutint320A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).
-
-Set to 2147483647 (MAXINT32) for infinity.dnsdnsarray of byte arrayArray of IP addresses of DNS servers (in network byte order)dns-datadns-dataarray of stringsArray of DNS name servers. This replaces the deprecated "dns" property. Each name server can also contain a DoT server name.dns-optionsdns-optionsarray of stringArray of DNS options to be added to resolv.conf.
-
-NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
-
-The following options are directly added to resolv.conf: "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-aaaa", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". See the resolv.conf(5) man page for a detailed description of these options.
-
-In addition, NetworkManager supports the special options "_no-add-edns0" and "_no-add-trust-ad". They are not added to resolv.conf, and can be used to prevent the automatic addition of options "edns0" and "trust-ad" when using caching DNS plugins (see below).
-
-The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
-
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added, unless "_no-add-edns0" and "_no-add-trust-ad" are present.dns-prioritydns-priorityint320DNS servers priority.
-
-The relative priority for DNS servers specified by this setting.  A lower numerical value is better (higher priority).
-
-Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
-
-Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
-
-Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile.
-
-When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
-
-When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.
-
-When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins.  If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.dns-searchdns-searcharray of stringList of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
-
-When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.
-
-When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).gatewaygatewaystringThe gateway associated with this configuration. This is only meaningful if "addresses" is also set.
-
-Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.
-
-Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".ignore-auto-dnsignore-auto-dnsbooleanFALSEWhen "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesignore-auto-routesbooleanFALSEWhen "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.ip6-privacyip6-privacyNMSettingIP6ConfigPrivacy (int32)Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses).
-
-Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy".
-
-If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr".
-
-Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.may-failmay-failbooleanTRUEIf TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.methodmethodstringIP configuration method.
-
-NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
-
-In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
-
-For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
-
-For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.mtumtuuint320Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.never-defaultnever-defaultbooleanFALSEIf TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.ra-timeoutra-timeoutint320A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device.
-
-Set to 2147483647 (MAXINT32) for infinity.replace-local-rulereplace-local-ruleNMTernary (int32)Connections will default to keep the autogenerated priority 0 local rule unless this setting is set to TRUE.required-timeoutrequired-timeoutint32-1The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
-
-This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
-
-Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.
-
-A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).route-dataroute-dataarray of vardictArray of IPv6 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'next-hop' entry, containing the next hop IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.route-metricroute-metricint64-1The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.route-tableroute-tableuint320Enable policy routing (source routing) and set the routing table used when adding routes.
-
-This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
-
-If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.
-
-Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.routesroutesarray of legacy IPv6 route struct (a(ayuayu))Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.
-Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv6 address, a prefix length (0 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.routing-rulesrouting-rulesarray of 'a{sv}'Array of dictionaries for routing rules. Each routing rule supports the following options: action (y), dport-end (q), dport-start (q), family (i), from (s), from-len (y), fwmark (u), fwmask (u), iifname (s), invert (b), ipproto (s), oifname (s), priority (u), sport-end (q), sport-start (q), supress-prefixlength (i), table (u), to (s), tos (y), to-len (y), range-end (u), range-start (u).tokentokenstringConfigure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.
-
-When set, the token is used as IPv6 interface identifier instead of the hardware address. This only applies to addresses from stateless autoconfiguration, not to IPv6 link local addresses.
ip-tunnelIP Tunneling Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionencapsulation-limitencapsulation-limituint320How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels. To disable this option, add 0x1 (ip6-ign-encap-limit) to ip-tunnel flags.flagsflagsuint320Tunnel flags. Currently, the following values are supported: 0x1 (ip6-ign-encap-limit), 0x2 (ip6-use-orig-tclass), 0x4 (ip6-use-orig-flowlabel), 0x8 (ip6-mip6-dev), 0x10 (ip6-rcv-dscp-copy), 0x20 (ip6-use-orig-fwmark). They are valid only for IPv6 tunnels.flow-labelflow-labeluint320The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.fwmarkfwmarkuint320The fwmark value to assign to tunnel packets. This property can be set to a non zero value only on VTI and VTI6 tunnels.input-keyinput-keystringThe key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.locallocalstringThe local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.modemodeuint320The tunneling mode. Valid values: 1 (ipip), 2 (gre), 3 (sit), 4 (isatap), 5 (vti), 6 (ip6ip6), 7 (ipip6), 8 (ip6gre), 9 (vti6), 10 (gretap) and 11 (ip6gretap)mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.output-keyoutput-keystringThe key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.parentparentstringIf given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.path-mtu-discoverypath-mtu-discoverybooleanTRUEWhether to enable Path MTU Discovery on this tunnel.remoteremotestringThe remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.tostosuint320The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.ttlttluint320The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.
macsecMACSec Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionencryptencryptbooleanTRUEWhether the transmitted traffic must be encrypted.mka-cakmka-cakstringThe pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement. Must be a string of 32 hexadecimal characters.mka-cak-flagsmka-cak-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "mka-cak" property.mka-cknmka-cknstringThe pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement. Must be a string of hexadecimal characters with a even length between 2 and 64.modemodeint320Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.offloadoffloadint32-1Specifies the MACsec offload mode.
-
-0 (off) disables MACsec offload.
-
-1 (phy) and 2 (mac) request offload respectively to the PHY or to the MAC; if the selected mode is not available, the connection will fail.
-
--1 (default) uses the global default value specified in NetworkManager configuration; if no global default is defined, the built-in default is 0 (off).parentparentstringIf given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.portportint321The port component of the SCI (Secure Channel Identifier), between 1 and 65534.send-scisend-scibooleanTRUESpecifies whether the SCI (Secure Channel Identifier) is included in every packet.validationvalidationint322Specifies the validation mode for incoming frames.
macvlanMAC VLAN Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmodemodeuint320The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.parentparentstringIf given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.promiscuouspromiscuousbooleanTRUEWhether the interface should be put in promiscuous mode.taptapbooleanFALSEWhether the interface should be a MACVTAP.
matchMatch settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondriverdriverarray of stringA list of driver names to match. Each element is a shell wildcard pattern.
-
-See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.interface-nameinterface-namearray of stringA list of interface names to match. Each element is a shell wildcard pattern.
-
-An element can be prefixed with a pipe symbol (|) or an ampersand (&). The former means that the element is optional and the latter means that it is mandatory. If there are any optional elements, than the match evaluates to true if at least one of the optional element matches (logical OR). If there are any mandatory elements, then they all must match (logical AND). By default, an element is optional. This means that an element "foo" behaves the same as "|foo". An element can also be inverted with exclamation mark (!) between the pipe symbol (or the ampersand) and before the pattern. Note that "!foo" is a shortcut for the mandatory match "&!foo". Finally, a backslash can be used at the beginning of the element (after the optional special characters) to escape the start of the pattern. For example, "&\\!a" is an mandatory match for literally "!a".kernel-command-linekernel-command-linearray of stringA list of kernel command line arguments to match. This may be used to check whether a specific kernel command line option is set (or unset, if prefixed with the exclamation mark). The argument must either be a single word, or an assignment (i.e. two words, joined by "="). In the former case the kernel command line is searched for the word appearing as is, or as left hand side of an assignment. In the latter case, the exact assignment is looked for with right and left hand side matching. Wildcard patterns are not supported.
-
-See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the match.pathpatharray of stringA list of paths to match against the ID_PATH udev property of devices. ID_PATH represents the topological persistent path of a device. It typically contains a subsystem string (pci, usb, platform, etc.) and a subsystem-specific identifier.
-
-For PCI devices the path has the form "pci-$domain:$bus:$device.$function", where each variable is an hexadecimal value; for example "pci-0000:0a:00.0".
-
-The path of a device can be obtained with "udevadm info /sys/class/net/$dev | grep ID_PATH=" or by looking at the "path" property exported by NetworkManager ("nmcli -f general.path device show $dev").
-
-Each element of the list is a shell wildcard pattern.
-
-See NMSettingMatch:interface-name for how special characters '|', '&', '!' and '\\' are used for optional and mandatory matches and inverting the pattern.
802-11-olpc-meshOLPC Wireless Mesh Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionchannelchanneluint320Channel on which the mesh network to join is located.dhcp-anycast-addressdhcp-anycast-addressbyte arrayAnycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request.
-
-This is currently only implemented by dhclient DHCP plugin.ssidssidbyte arraySSID of the mesh network to join.
ovs-bridgeOvsBridge Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondatapath-typedatapath-typestringThe data path type. One of "system", "netdev" or empty.fail-modefail-modestringThe bridge failure mode. One of "secure", "standalone" or empty.mcast-snooping-enablemcast-snooping-enablebooleanFALSEEnable or disable multicast snooping.rstp-enablerstp-enablebooleanFALSEEnable or disable RSTP.stp-enablestp-enablebooleanFALSEEnable or disable STP.
ovs-dpdkOvsDpdk Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptiondevargsdevargsstringOpen vSwitch DPDK device arguments.n-rxqn-rxquint320Open vSwitch DPDK number of rx queues. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures one queue.n-rxq-descn-rxq-descuint320The rx queue size (number of rx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.n-txq-descn-txq-descuint320The tx queue size (number of tx descriptors) for DPDK ports. Must be zero or a power of 2 between 1 and 4096, and supported by the hardware. Defaults to zero which means to leave the parameter in OVS unspecified and effectively configures 2048 descriptors.
ovs-interfaceOpen vSwitch Interface Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionofport-requestofport-requestuint320Open vSwitch openflow port number. Defaults to zero which means that port number will not be specified and it will be chosen randomly by ovs. OpenFlow ports are the network interfaces for passing packets between OpenFlow processing and the rest of the network. OpenFlow switches connect logically to each other via their OpenFlow ports.typetypestringThe interface type. Either "internal", "system", "patch", "dpdk", or empty.
ovs-patchOvsPatch Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionpeerpeerstringSpecifies the name of the interface for the other side of the patch. The patch on the other side must also set this interface as peer.
ovs-portOvsPort Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionbond-downdelaybond-downdelayuint320The time port must be inactive in order to be considered down.bond-modebond-modestringBonding mode. One of "active-backup", "balance-slb", or "balance-tcp".bond-updelaybond-updelayuint320The time port must be active before it starts forwarding traffic.lacplacpstringLACP mode. One of "active", "off", or "passive".tagtaguint320The VLAN tag in the range 0-4095.trunkstrunksarray of vardictA list of VLAN ranges that this port trunks.
-
-The property is valid only for ports with mode "trunk", "native-tagged", or "native-untagged port". If it is empty, the port trunks all VLANs.vlan-modevlan-modestringThe VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk", "dot1q-tunnel" or unset.
pppPoint-to-Point Protocol Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionbaudbauduint320If non-zero, instruct pppd to set the serial port to the specified baudrate.  This value should normally be left as 0 to automatically choose the speed.crtsctscrtsctsbooleanFALSEIf TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals.  This value should normally be set to FALSE.lcp-echo-failurelcp-echo-failureuint320If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer.  The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.lcp-echo-intervallcp-echo-intervaluint320If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value).  Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.mppe-statefulmppe-statefulbooleanFALSEIf TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.mrumruuint320If non-zero, instruct pppd to request that the peer send packets no larger than the specified size.  If non-zero, the MRU should be between 128 and 16384.mtumtuuint320If non-zero, instruct pppd to send packets no larger than the specified size.no-vj-compno-vj-compbooleanFALSEIf TRUE, Van Jacobsen TCP header compression will not be requested.noauthnoauthbooleanTRUEIf TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client.  If FALSE, require authentication from the remote side.  In almost all cases, this should be TRUE.nobsdcompnobsdcompbooleanFALSEIf TRUE, BSD compression will not be requested.nodeflatenodeflatebooleanFALSEIf TRUE, "deflate" compression will not be requested.refuse-chaprefuse-chapbooleanFALSEIf TRUE, the CHAP authentication method will not be used.refuse-eaprefuse-eapbooleanFALSEIf TRUE, the EAP authentication method will not be used.refuse-mschaprefuse-mschapbooleanFALSEIf TRUE, the MSCHAP authentication method will not be used.refuse-mschapv2refuse-mschapv2booleanFALSEIf TRUE, the MSCHAPv2 authentication method will not be used.refuse-paprefuse-papbooleanFALSEIf TRUE, the PAP authentication method will not be used.require-mpperequire-mppebooleanFALSEIf TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session.  If either 64-bit or 128-bit MPPE is not available the session will fail.  Note that MPPE is not used on mobile broadband connections.require-mppe-128require-mppe-128booleanFALSEIf TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE.  If 128-bit MPPE is not available the session will fail.
pppoePPP-over-Ethernet Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionparentparentstringIf given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.passwordpasswordstringPassword used to authenticate with the PPPoE service.password-flagspassword-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "password" property.serviceservicestringIf specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.usernameusernamestringUsername used to authenticate with the PPPoE service.
proxyWWW Proxy Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionbrowser-onlybrowser-onlybooleanFALSEWhether the proxy configuration is for browser only.methodmethodint320Method for proxy configuration, Default is 0 (none)pac-scriptpac-scriptstringPAC script for the connection. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function.pac-urlpac-urlstringPAC URL for obtaining PAC file.
serialSerial Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionbaudbauduint3257600Speed to use for communication over the serial port.  Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.bitsbitsuint328Byte-width of the serial communication. The 8 in "8n1" for example.parityparitybyteThe connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.send-delaysend-delayuint640Time to delay between each byte sent to the modem, in microseconds.stopbitsstopbitsuint321Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.
sriovSR-IOV settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionautoprobe-driversautoprobe-driversNMTernary (int32)Whether to autoprobe virtual functions by a compatible driver.
-
-If set to 1 (true), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF.
-
-If set to 0 (false), VFs will not be claimed and no network interfaces will be created for them.
-
-When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 1 (true).eswitch-encap-modeeswitch-encap-modeint32-1Select the eswitch encapsulation support.
-
-Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF.
-
-If set to -1 (preserve) (default) the eswitch encap-mode won't be modified by NetworkManager.eswitch-inline-modeeswitch-inline-modeint32-1Select the eswitch inline-mode of the device. Some HWs need the VF driver to put part of the packet headers on the TX descriptor so the e-switch can do proper matching and steering.
-
-Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF.
-
-If set to -1 (preserve) (default) the eswitch inline-mode won't be modified by NetworkManager.eswitch-modeeswitch-modeint32-1Select the eswitch mode of the device. Currently it's only supported for PCI PF devices, and only if the eswitch device is managed from the same PCI address than the PF.
-
-If set to -1 (preserve) (default) the eswitch mode won't be modified by NetworkManager.total-vfstotal-vfsuint320The total number of virtual functions to create.
-
-Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface (also when it is zero) during activation and resets it upon deactivation. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.vfsvfsarray of vardictArray of virtual function descriptors.
-
-Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF.
-
-When represented as string a VF is in the form:
-
-"INDEX [ATTR=VALUE[ ATTR=VALUE]...]".
-
-for example:
-
-"2 mac=00:11:22:33:44:55 spoof-check=true".
-
-Multiple VFs can be specified using a comma as separator. Currently, the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans.
-
-The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form
-
-"ID[.PRIORITY[.PROTO]]".
-
-PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.
tcLinux Traffic Control Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionqdiscsqdiscsarray of vardictArray of TC queueing disciplines.
-
-When the "tc" setting is present, qdiscs from this property are applied upon activation. If the property is empty, all qdiscs are removed and the device will only have the default qdisc assigned by kernel according to the "net.core.default_qdisc" sysctl.
-
-If the "tc" setting is not present, NetworkManager doesn't touch the qdiscs present on the interface.tfilterstfiltersarray of vardictArray of TC traffic filters.
-
-When the "tc" setting is present, filters from this property are applied upon activation. If the property is empty, NetworkManager removes all the filters.
-
-If the "tc" setting is not present, NetworkManager doesn't touch the filters present on the interface.
teamTeaming Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionconfigconfigstringThe JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.interface-nameinterface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the team's interface name.link-watcherslink-watchersarray of vardictLink watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.mcast-rejoin-countmcast-rejoin-countint32-1Corresponds to the teamd mcast_rejoin.count.mcast-rejoin-intervalmcast-rejoin-intervalint32-1Corresponds to the teamd mcast_rejoin.interval.notify-peers-countnotify-peers-countint32-1Corresponds to the teamd notify_peers.count.notify-peers-intervalnotify-peers-intervalint32-1Corresponds to the teamd notify_peers.interval.runnerrunnerstringCorresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".runner-activerunner-activebooleanTRUECorresponds to the teamd runner.active.runner-agg-select-policyrunner-agg-select-policystringCorresponds to the teamd runner.agg_select_policy.runner-fast-raterunner-fast-ratebooleanFALSECorresponds to the teamd runner.fast_rate.runner-hwaddr-policyrunner-hwaddr-policystringCorresponds to the teamd runner.hwaddr_policy.runner-min-portsrunner-min-portsint32-1Corresponds to the teamd runner.min_ports.runner-sys-priorunner-sys-prioint32-1Corresponds to the teamd runner.sys_prio.runner-tx-balancerrunner-tx-balancerstringCorresponds to the teamd runner.tx_balancer.name.runner-tx-balancer-intervalrunner-tx-balancer-intervalint32-1Corresponds to the teamd runner.tx_balancer.interval.runner-tx-hashrunner-tx-hasharray of stringCorresponds to the teamd runner.tx_hash.
team-portTeam Port Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionconfigconfigstringThe JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.lacp-keylacp-keyint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_key.lacp-priolacp-prioint32-1Corresponds to the teamd ports.PORTIFNAME.lacp_prio.link-watcherslink-watchersarray of vardictLink watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.prioprioint320Corresponds to the teamd ports.PORTIFNAME.prio.queue-idqueue-idint32-1Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.stickystickybooleanFALSECorresponds to the teamd ports.PORTIFNAME.sticky.
tunTunnel Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptiongroupgroupstringThe group ID which will own the device. If set to NULL everyone will be able to use the device.modemodeuint321The operating mode of the virtual device. Allowed values are 1 (tun) to create a layer 3 device and 2 (tap) to create an Ethernet-like layer 2 one.multi-queuemulti-queuebooleanFALSEIf the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.ownerownerstringThe user ID which will own the device. If set to NULL everyone will be able to use the device.pipibooleanFALSEIf TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.vnet-hdrvnet-hdrbooleanFALSEIf TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.
userGeneral User Profile Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondatadatadict of string to string{}A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.
vlanVLAN Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionegress-priority-mapegress-priority-maparray of stringFor outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".flagsflagsNMVlanFlags (uint32)One or more flags which control the behavior and features of the VLAN interface.  Flags include 0x1 (reorder-headers) (reordering of output packet headers), 0x2 (gvrp) (use of the GVRP protocol), and 0x4 (loose-binding) (loose binding of the interface to its master device's operating state). 0x8 (mvrp) (use of the MVRP protocol).
-
-The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.ididuint320The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.ingress-priority-mapingress-priority-maparray of stringFor incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".interface-nameinterface-namestringDeprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the vlan's interface name.parentparentstringIf given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.protocolprotocolstringSpecifies the VLAN protocol to use for encapsulation.
-
-Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
vpnVPN Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondatadatadict of string to string{}Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.persistentpersistentbooleanFALSEIf the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.secretssecretsdict of string to string{}Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.service-typeservice-typestringD-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.timeouttimeoutuint320Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.user-nameuser-namestringIf the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.
vrfVRF settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiontabletableuint320The routing table for this VRF.
vxlanVXLAN Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionageingageinguint32300Specifies the lifetime in seconds of FDB entries learnt by the kernel.destination-portdestination-portuint328472Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.ididuint320Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.l2-missl2-missbooleanFALSESpecifies whether netlink LL ADDR miss notifications are generated.l3-missl3-missbooleanFALSESpecifies whether netlink IP ADDR miss notifications are generated.learninglearningbooleanTRUESpecifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.limitlimituint320Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.locallocalstringIf given, specifies the source IP address to use in outgoing packets.parentparentstringIf given, specifies the parent interface name or parent connection UUID.proxyproxybooleanFALSESpecifies whether ARP proxy is turned on.remoteremotestringSpecifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.rscrscbooleanFALSESpecifies whether route short circuit is turned on.source-port-maxsource-port-maxuint320Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.source-port-minsource-port-minuint320Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.tostosuint320Specifies the TOS value to use in outgoing packets.ttlttluint320Specifies the time-to-live value to use in outgoing packets.
wifi-p2pWi-Fi P2P Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionpeerpeerstringThe P2P device that should be connected to. Currently, this is the only way to create or join a group.wfd-ieswfd-iesbyte arrayThe Wi-Fi Display (WFD) Information Elements (IEs) to set.
-
-Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.wps-methodwps-methoduint320Flags indicating which mode of WPS is to be used.
-
-There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.
wimaxWiMax Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmac-addressmac-addressbyte arrayIf specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).network-namenetwork-namestringNetwork Service Provider (NSP) name of the WiMAX network this connection should use.
802-3-ethernetWired Ethernet Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionaccept-all-mac-addressesaccept-all-mac-addressesNMTernary (int32)When TRUE, setup the interface to accept packets for all MAC addresses. This is enabling the kernel interface flag IFF_PROMISC. When FALSE, the interface will only accept the packets with the interface destination mac address or broadcast.assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".auto-negotiateauto-negotiatebooleanFALSEWhen TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.cloned-mac-addresscloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".duplexduplexstringWhen a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.generate-mac-address-maskgenerate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
-
-If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
-
-If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
-
-If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
-
-If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.mac-addressmac-addressbyte arrayIf specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistmac-address-blacklistarray of stringIf specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.portportstringSpecific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.s390-nettypes390-nettypestrings390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.s390-optionss390-optionsdict of string to string{}Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
-
-Currently, NetworkManager itself does nothing with this information. However, s390utils ships a udev rule which parses this information and applies it to the interface.s390-subchannelss390-subchannelsarray of stringIdentifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.speedspeeduint320When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.wake-on-lanwake-on-lanuint321The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of 0x2 (phy), 0x4 (unicast), 0x8 (multicast), 0x10 (broadcast), 0x20 (arp), 0x40 (magic) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).wake-on-lan-passwordwake-on-lan-passwordstringIf specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.
wireguardWireGuard Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionfwmarkfwmarkuint320The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise, it is a 32-bit fwmark for outgoing packets.
-
-Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.ip4-auto-default-routeip4-auto-default-routeNMTernary (int32)Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route from wireguard.peer-routes will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, an unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto and what WireGuard calls "Improved Rule-based Routing".
-
-Note that for this automatism to work, you usually don't want to set ipv4.gateway, because that will result in a conflicting default route.
-
-Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips. Since this automatism only makes sense if you also have a peer with an /0 allowed-ips, it is usually not necessary to enable this explicitly. However, you can disable it if you want to configure your own routing and rules.ip6-auto-default-routeip6-auto-default-routeNMTernary (int32)Like ip4-auto-default-route, but for the IPv6 default route.listen-portlisten-portuint320The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.
-
-If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.peer-routespeer-routesbooleanTRUEWhether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. Usually you want this automatism enabled. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.
-
-Note that if the peer's AllowedIPs is "0.0.0.0/0" or "::/0" and the profile's ipv4.never-default or ipv6.never-default setting is enabled, the peer route for this peer won't be added automatically.peerspeersarray of 'a{sv}'Array of dictionaries for the WireGuard peers.private-keyprivate-keystringThe 256 bit private-key in base64 encoding.private-key-flagsprivate-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "private-key" property.
802-11-wirelessWi-Fi Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionap-isolationap-isolationNMTernary (int32)Configures AP isolation, which prevents communication between wireless devices connected to this AP. This property can be set to a value different from -1 (default) only when the interface is configured in AP mode.
-
-If set to 1 (true), devices are not able to communicate with each other. This increases security because it protects devices against attacks from other clients in the network. At the same time, it prevents devices to access resources on the same wireless networks as file shares, printers, etc.
-
-If set to 0 (false), devices can talk to each other.
-
-When set to -1 (default), the global default is used; in case the global default is unspecified it is assumed to be 0 (false).assigned-mac-addressassigned-mac-addressstringThe new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".bandbandstring802.11 frequency band of the network.  One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11.  This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible.  This setting depends on specific driver capability and may not work with all drivers.bssidbssidbyte arrayIf specified, directs the device to only associate with the given access point.  This capability is highly driver dependent and not supported by all devices.  Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.
-
-Locking a client profile to a certain BSSID will prevent roaming and also disable background scanning. That can be useful, if there is only one access point for the SSID.channelchanneluint320Wireless channel to use for the Wi-Fi connection.  The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel.  Because channel numbers overlap between bands, this property also requires the "band" property to be set.cloned-mac-addresscloned-mac-addressbyte arrayThis D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".generate-mac-address-maskgenerate-mac-address-maskstringWith "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address.
-
-If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address.
-
-If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm.
-
-If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address.
-
-If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.hiddenhiddenbooleanFALSEIf TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode.
-
-In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution.
-
-In AP mode, the created network does not broadcast its SSID.
-
-Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.mac-addressmac-addressbyte arrayIf specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).mac-address-blacklistmac-address-blacklistarray of stringA list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").mac-address-randomizationmac-address-randomizationuint320One of 0 (default) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  1 (never) (never randomize the MAC address), or 2 (always) (always randomize the MAC address).modemodestringWi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.mtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.powersavepowersaveuint320One of 2 (disable) (disable Wi-Fi power saving), 3 (enable) (enable Wi-Fi power saving), 1 (ignore) (don't touch currently configure setting) or 0 (default) (use the globally configured value). All other values are reserved.raterateuint320This property is not implemented and has no effect.securitysecurityThis property is deprecated and has no effect. For backwards compatibility, it can be set to "802-11-wireless-security" if the profile has a wireless security setting.seen-bssidsseen-bssidsarray of stringA list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.
-
-This is not a regular property that the user would configure. Instead, NetworkManager automatically sets the seen BSSIDs and tracks them internally in "/var/lib/NetworkManager/seen-bssids" file.ssidssidbyte arraySSID of the Wi-Fi network. Must be specified.tx-powertx-poweruint320This property is not implemented and has no effect.wake-on-wlanwake-on-wlanuint321The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of 0x2 (any), 0x4 (disconnect), 0x8 (magic), 0x10 (gtk-rekey-failure), 0x20 (eap-identity-request), 0x40 (4way-handshake), 0x80 (rfkill-release), 0x100 (tcp) or the special values 0x1 (default) (to use global settings) and 0x8000 (ignore) (to disable management of Wake-on-LAN in NetworkManager).
802-11-wireless-securityWi-Fi Security Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionauth-algauth-algstringWhen WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.filsfilsint320Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable FILS), 2 (optional) (enable FILS if the supplicant and the access point support it) or 3 (required) (enable FILS and fail if not supported).  When set to 0 (default) and no global default is set, FILS will be optionally enabled.groupgrouparray of stringA list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".key-mgmtkey-mgmtstringKey management used for the connection. One of "none" (WEP or no password protection), "ieee8021x" (Dynamic WEP), "owe" (Opportunistic Wireless Encryption), "wpa-psk" (WPA2 + WPA3 personal), "sae" (WPA3 personal only), "wpa-eap" (WPA2 + WPA3 enterprise) or "wpa-eap-suite-b-192" (WPA3 enterprise only).
-
-This property must be set for any Wi-Fi connection that uses security.leap-passwordleap-passwordstringThe login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").leap-password-flagsleap-password-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "leap-password" property.leap-usernameleap-usernamestringThe login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").pairwisepairwisearray of stringA list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".pmfpmfint320Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of 0 (default) (use global default value), 1 (disable) (disable PMF), 2 (optional) (enable PMF if the supplicant and the access point support it) or 3 (required) (enable PMF and fail if not supported).  When set to 0 (default) and no global default is set, PMF will be optionally enabled.protoprotoarray of stringList of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.pskpskstringPre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.psk-flagspsk-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "psk" property.wep-key-flagswep-key-flagsNMSettingSecretFlags (uint32)Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties.wep-key-typewep-key-typeNMWepKeyType (uint32)Controls the interpretation of WEP keys.  Allowed values are 1 (key), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or 2 (passphrase), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.wep-key0wep-key0stringIndex 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key1wep-key1stringIndex 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key2wep-key2stringIndex 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-key3wep-key3stringIndex 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.wep-tx-keyidxwep-tx-keyidxuint320When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.wps-methodwps-methoduint320Flags indicating which mode of WPS is to be used if any.
-
-There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities.
-
-WPS can be disabled by setting this property to a value of 1.
wpanIEEE 802.15.4 (WPAN) MAC Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionchannelchannelint32-1IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".mac-addressmac-addressstringIf specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.pagepageint32-1IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".pan-idpan-iduint3265535IEEE 802.15.4 Personal Area Network (PAN) identifier.short-addressshort-addressuint3265535Short IEEE 802.15.4 address to be used within a restricted environment.
bond-portBond Port Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionprioprioint320The port priority for bond active port re-selection during failover. A higher number means a higher priority in selection. The primary port has the highest priority. This option is only compatible with active-backup, balance-tlb and balance-alb modes.queue-idqueue-iduint320The queue ID of this bond port. The maximum value of queue ID is the number of TX queues currently active in device.
hostnameHostname settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionfrom-dhcpfrom-dhcpNMTernary (int32)Whether the system hostname can be determined from DHCP on this connection.
-
-When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).from-dns-lookupfrom-dns-lookupNMTernary (int32)Whether the system hostname can be determined from reverse DNS lookup of addresses on this device.
-
-When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 1 (true).only-from-defaultonly-from-defaultNMTernary (int32)If set to 1 (true), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6).
-
-If set to 0 (false), the hostname can be set from this device even if it doesn't have the default route.
-
-When set to -1 (default), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be 0 (false).prioritypriorityint320The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority.
-
-If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100.
-
-Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.
hsrHSR/PRP Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmulticast-specmulticast-specuint320The last byte of supervision address.port1port1stringThe port1 interface name of the HSR. This property is mandatory.port2port2stringThe port2 interface name of the HSR. This property is mandatory.prpprpbooleanFALSEThe protocol used by the interface, whether it is PRP or HSR.
linkLink settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiongro-max-sizegro-max-sizeint64-1The maximum size of a packet built by the Generic Receive Offload stack for this device. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-segmentsgso-max-segmentsint64-1The maximum segments of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.gso-max-sizegso-max-sizeint64-1The maximum size of a Generic Segment Offload packet the device should accept. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.tx-queue-lengthtx-queue-lengthint64-1The size of the transmit queue for the device, in number of packets. The value must be between 0 and 4294967295. When set to -1, the existing value is preserved.
loopbackLoopback Link Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptionmtumtuuint320If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.
ovs-external-idsOVS External IDs Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondatadatadict of string to string{}A dictionary of key/value pairs with external-ids for OVS.
ovs-other-configOVS Other Config Settings
-            Properties
-        Key NameValue TypeDefault ValueValue Descriptiondatadatadict of string to string{}A dictionary of key/value pairs with other_config settings for OVS. See also "other_config" in the "ovs-vswitchd.conf.db" manual for the keys that OVS supports.
vethVeth Settings
-            Properties
-        Key NameValue TypeDefault ValueValue DescriptionpeerpeerstringThis property specifies the peer interface name of the veth. This property is mandatory.

diff --git a/docs/api/settings-spec.xsl b/docs/api/settings-spec.xsl
index 7a452237..39d4e357 100644
--- a/docs/api/settings-spec.xsl
+++ b/docs/api/settings-spec.xsl
@@ -4,8 +4,8 @@
 
   
 
   
diff --git a/docs/api/version.xml b/docs/api/version.xml
deleted file mode 100644
index 0a3db35b..00000000
--- a/docs/api/version.xml
+++ /dev/null
@@ -1 +0,0 @@
-1.46.0
-- 
cgit 1.3.0-6-gf8a5