summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* core: implement setting MDNS setting for systemdThomas Haller2018-01-091-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | The connection.mdns setting is a per-connection setting, so one might expect that one activated device can only have one MDNS setting at a time. However, with certain VPN plugins (those that don't have their own IP interface, like libreswan), the VPN configuration is merged into the configuration of the device. So, in this case, there might be multiple settings for one device that must be merged. We already have a mechanism for that. It's NMIP4Config. Let NMIP4Config track this piece of information. Although, stricitly speaking this is not tied to IPv4, the alternative would be to introduce a new object to track such data, which would be a tremendous effort and more complicated then this. Luckily, NMDnsManager and NMDnsPlugin are already equipped to handle multiple NMIPConfig instances per device (IPv4 vs. IPv6, and Device vs. VPN). Also make "connection.mdns" configurable via global defaults in NetworkManager.conf.
* wifi: configure wifi-backend per deviceThomas Haller2017-12-271-0/+9
| | | | | | | | This allows to configure the wifi-backend per device, like [device-wifi-backend-eth0] match-device=interface-name:wlan0 wifi-backend=iwd
* settings: drop unmaintained ifnet settings plugin of GentooThomas Haller2017-12-211-11/+2
| | | | | | | | | | | | Even Gentoo disables this plugin since before 0.9.8 release of NetworkManager. Time to say goodbye. If somebody happens to show up to maintain it, we may resurrect it later. If "$distro_plugins=ifnet" was set, configure.ac would use that to autodetect --with-hostname-persist=gentoo. Replace that autodetect part by checking for /etc/gentoo-release file.
* man: document all setting plugins in NetworkManager.conf manualThomas Haller2017-12-212-14/+24
| | | | although they are deprecated and unused, document them.
* man/openvswitch: fix type in examplesLubomir Rintel2017-12-191-10/+10
| | | | | | "conn.type" doesn't allow type aliases. Use "type" instead. https://bugzilla.redhat.com/show_bug.cgi?id=1519173
* build: add initial support for meson build systemIñigo Martínez2017-12-131-0/+98
| | | | | | | | | | meson is a build system focused on speed an ease of use, which helps speeding up the software development. This patch adds meson support along autotools. [thaller@redhat.com: rebased patch and adjusted for iwd support] https://mail.gnome.org/archives/networkmanager-list/2017-December/msg00022.html
* device: make carrier-wait-timeout configurable per deviceThomas Haller2017-11-281-0/+18
| | | | | | | | As this depends on the particular host configuration, it's hard to find a default that suits everybody. At least make it configurable per-device. https://bugzilla.redhat.com/show_bug.cgi?id=1483343 https://bugzilla.redhat.com/show_bug.cgi?id=1515027
* logging: configure dnsmasq's logging in shared mode via nm-loggingThomas Haller2017-11-061-1/+1
| | | | (cherry picked from commit cc993aa02040564c16d78c864f3c3a22d20443eb)
* man: document PROXY logging domainThomas Haller2017-11-061-1/+3
| | | | (cherry picked from commit 43da186ec36dc9da6ab038783c3350f9206a638c)
* all: move setting 802-1x.auth-retries to connection.auth-retriesThomas Haller2017-11-021-5/+5
| | | | | | | | | | | The number of authentication retires is useful also for passwords aside 802-1x settings. For example, src/devices/wifi/nm-device-wifi.c also has a retry counter and uses a hard-coded value of 3. Move the setting, so that it can be used in general. Although it is still not implemented for other settings. This is an API and ABI break.
* libnm,cli,ifcfg-rh: add NMSetting8021x:auth-retries propertyThomas Haller2017-10-311-0/+5
|
* man: add OpenVSwitch overviewlr/ovsLubomir Rintel2017-10-301-0/+204
|
* all: rework configuring route table support by adding "route-table" settingThomas Haller2017-10-091-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | | We added "ipv4.route-table-sync" and "ipv6.route-table-sync" to not change behavior for users that configured policy routing outside of NetworkManager, for example, via a dispatcher script. Users had to explicitly opt-in for NetworkManager to fully manage all routing tables. These settings were awkward. Replace them with new settings "ipv4.route-table" and "ipv6.route-table". Note that this commit breaks API/ABI on the unstable development branch by removing recently added API. As before, a connection will have no route-table set by default. This has the meaning that policy-routing is not enabled and only the main table will be fully synced. Once the user sets a table, we recognize that and NetworkManager manages all routing tables. The new route-table setting has other important uses: analog to "ipv4.route-metric", it is the default that applies to all routes. Currently it only works for static routes, not DHCP, SLAAC, default-route, etc. That will be implemented later. For static routes, each route still can explicitly set a table, and overwrite the per-connection setting in "ipv4.route-table" and "ipv6.route-table".
* core: cleanup autoconnect retry handlingThomas Haller2017-10-041-2/+3
| | | | | | | | - clearify in the manual page that setting retry to 1 means to try once, without retry. - log the initially set retry value in nm_settings_connection_get_autoconnect_retries(). - use nm_settings_connection_get_autoconnect_retries() in nm_settings_connection_can_autoconnect().
* man: clearify plain text secrets in keyfileThomas Haller2017-09-282-6/+13
|
* device: add configuration option to mark devices as unmanagedThomas Haller2017-09-281-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already have various ways to mark a device as unmanaged. 1) via udev-rule ENV{NM_UNMANAGED}. This can be overwritten via D-Bus at runtime. 2) via settings plugin. That is NM_CONTROLLED=no for ifcfg-rh and keyfile.unmanaged-devices in NetworkManager.conf. 3) at runtime, via D-Bus. This is persisted in the run state file and persists restarts (but not reboot). This adds another way via NetworkManager.conf file. Note that the existing keyfile.unmanaged-devices (above 2) is also a configuration optin in NetworkManager.conf. However it has various downsides: - it cannot be overwritten at runtime (see commit c210134bd58ea40ee3458aff27ab41958e1f48b4). - you can only explicitly mark a device as unmanaged. That means, you cannot use it to manage a device which is unmanaged due to a udev rule. - the name "keyfile.*" sounds like it's only relevant for the keyfile settings plugin. Nowadays the keyfile plugin is always loaded, so the option applies to NetworkManager in general. https://github.com/NetworkManager/NetworkManager/pull/29
* man: fix example for device section in NetworkManager.conf's manualThomas Haller2017-09-281-1/+1
| | | | | | | | | | | | | | We currently don't support marking a device a managed/unmanaged via the [device] section. Eventually, I think we should, because the existing "keyfile.unmanaged-devices" looks keyfile specific (which it isn't). But more importantly, "keyfile.unmanaged-devices" sets the unmanaged flag NM_UNMANAGED_USER_SETTINGS, which cannot be overruled via D-Bus (see commit c210134bd58ea40ee3458aff27ab41958e1f48b4). A device.managed flag would make sense for a more sensible way to express configuration in NetworkManager.conf, which still can be overwritten via D-Bus. Anyway, it's not yet implemented. Fix the example.
* libnm,cli: add IP setting "route-table-sync"Thomas Haller2017-09-261-0/+8
|
* man: nmcli: add missing aliasesBeniamino Galvani2017-09-131-2/+21
|
* man: nmcli: improve description of type, ip4, ip6 aliasesBeniamino Galvani2017-09-131-9/+5
| | | | | | Clarify that the description refers to the alias, not to the property. https://bugzilla.redhat.com/show_bug.cgi?id=1482772
* device: enable support for ipv6.dhcp-timeoutThomas Haller2017-09-111-0/+5
| | | | | | | | | | | | | | | - cleanup data type and use guint32 consistently. We might want to introduce a new "infinity" value. But since libnm's NM_SETTING_IP_CONFIG_DHCP_TIMEOUT asserts against the range 0 - G_MAXINT32, we cannot express it as -1 anyway. So, infinity will have the numerical value G_MAXINT32, hence guint32 is just fine. - make use of existing ipv6.dhcp-timeout setting and add global default configuration in NetworkManager.conf - instead of having subclasses call nm_device_set_dhcp_timeout(), add a virtual function get_dhcp_timeout().
* man: fix evaluation of unsupported ifcfg-rh settingsBeniamino Galvani2017-09-051-1/+1
| | | | | | The 'contains' function has no notion of separators, so 'vlan' can match 'macvlan' in the unspported list. Add separator to avoid matching substrings.
* man: add unsupported ifcfg-rh settingsBeniamino Galvani2017-09-051-1/+1
| | | | | Add macsec and dummy setting to the unsupported list. While at it, also sort entries.
* man: remove unused xsl variableBeniamino Galvani2017-09-051-1/+0
|
* man: nmcli: grammar fixBeniamino Galvani2017-08-301-3/+3
| | | | s/It's equivalent of/It's equivalent to/
* device: handle carrier changes for master device differentlyNikolay Martynov2017-06-221-1/+8
| | | | | | | | | | | | | | | | | | | | | | For master devices, instead of ignoring loss of carrier entirely, handle it. First of all, master devices are now by default ignore-carrier=yes. That means, without explict user configuration in NetworkManager.conf, the previous behavior in carrier_changed() does not change. If the user decides to configure the master device like [device-with-carrier] match-device=type:bond,type:bridge,type:team ignore-carrier=no then, master device will disconnect on carrier loss like regular devices. https://github.com/NetworkManager/NetworkManager/pull/18 Co-authored-by: Thomas Haller <thaller@redhat.com>
* device: don't set MTU of device unless explicitly configuredThomas Haller2017-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Since commit 2b51d3967 "device: merge branch 'th/device-mtu-bgo777251'", we always set the MTU for certain device types during activation. Even if the MTU is neither specified via the connection nor other means, like DHCP. Revert that change. On activation, if nothing explicitly configures the MTU, leave it unchanged. This is like what we do with ethernet's cloned-mac-address, which has a default value "preserve". So, as last resort the default value for MTU is now 0 (don't change), instead of depending on the device type. Note that you also can override the default value in global configuration via NetworkManager.conf. This behavior makes sense, because whenever NM actively resets the MTU, it remembers the previous value and restores it when deactivating the connection. That wasn't implemented before 2b51d3967, and the MTU would depend on which connection was previously active. That is no longer an issue as the MTU gets reset when deactivating. https://bugzilla.redhat.com/show_bug.cgi?id=1460760
* clients: add support for Bluetooth NAP typeLubomir Rintel2017-05-311-4/+4
|
* core: add configuration flag to choose slaves activation orderBeniamino Galvani2017-05-241-0/+13
| | | | | | | | | Commits 39d0559d9a7a ("platform: sort links by name instead of ifindex") and 529a0a1a7f19 ("manager: sort slaves to be autoconnected by device name") changed the order of activation of slaves. Introduce a system-wide configuration property to preserve the old behavior. https://bugzilla.redhat.com/show_bug.cgi?id=1452585
* supplicant: configure PMF for each connectionBeniamino Galvani2017-04-281-0/+5
| | | | | | | Now that we have a PMF connection property, get rid of the previous code to globally enable/disable PMF and use the 'ieee80211w' configuration option for each configured network when the supplicant supports it.
* core: allow setting SR-IOV num_vfsBeniamino Galvani2017-04-181-0/+10
|
* nmcli: add -g[et-values] option as a '-m tab -t -f <arg>' shortcutFrancesco Giudici2017-03-282-4/+43
| | | | Quick and easy way to get clean and parsable field values.
* man: add description for the 'hostname' config option in the main sectionfg/keep_externally_set_hostname-rh1422610Francesco Giudici2017-03-241-0/+28
|
* man: fix default location for keyfile.path in documentationThomas Haller2017-03-241-1/+1
| | | | | Fixes: 530af7009ecca099372fd50a9b2b130c875a6524 Fixes: 90683fcb3a4a60d2902ebb7e4a47419d76acb1d8
* device: add spec "driver:" to match devicesThomas Haller2017-03-171-0/+7
| | | | | | | | Changing the MAC address of devices is known to fail with certain drivers. Add a device-spec to allow disabling it for for such devices. Related: https://bugzilla.gnome.org/show_bug.cgi?id=777523
* man: include the description for settingsLubomir Rintel2017-03-171-15/+18
|
* cli: support dummy connectionsBeniamino Galvani2017-02-221-0/+1
|
* build: use `sed` instead of AC_SUBST() to generate man/common.entThomas Haller2017-02-151-1/+1
| | | | | | | | | | | | Otherwise, substitions are not properly expanded. For example - "AC_SUBST(nmrundir, '${runstatedir}'/$PACKAGE, [NetworkManager runtime state directory])" gives ${runstatedir}/NetworkManager/resolv.conf - "AC_SUBST(nmrundir, "${runstatedir}/$PACKAGE", [NetworkManager runtime state directory])" gives ${prefix}/var/run/NetworkManager/resolv.conf
* dns: change behavior for "rc-manager=symlink" to preserve "/etc/resolv.conf" ↵Thomas Haller2017-02-142-9/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | as file The purpose of "rc-manager=symlink" is so that the administrator can point the "/etc/resolv.conf" as a symlink to a certain file, and thus indicating that a certain component is responsible to manage resolv.conf, while others should stay away from it. For example, systemd-resolved never touches "/etc/resolv.conf", but expects the admin to setup the symlink appropriately. It also recognizes whether the symlink points to it's own resolv.conf in /run or to another component. Previously, "rc-manager=symlink" would always replace a regular file with a symlink to "/var/run/NetworkManager/resolv.conf". Only if "/etc/resolv.conf" is already a symlink somewhere else, NM would not touch it. This with the exception that if "/etc/resolv.conf" points to "/var/run/NetworkManager/resolv.conf", it would replace the symlink with the same link to raise inotify events. Change behavior so if "/etc/resolv.conf" is already a regular file, keep it as file. This means, if you have multiple components that don't care, everybody can write the "/etc/resolv.conf" (as file) and there is no clear expressed responsibility. It was wrong that NetworkManager would convert the file to a symlink, this should be reserved to the admin. Instead, NetworkManager should accept that the intent is unspecified and preserve the regular file. It's up to the admin to replace the symlink to somewhere else (to keep NM off), or to point it to "/var/run/NetworkManager/resolv.conf", to show the explicit intent. The wrong behavior causes dangling symlinks when somebody disables NetworkManager for good. https://bugzilla.redhat.com/show_bug.cgi?id=1367551
* device: make the MTU globally configurable via connection-defaultsThomas Haller2017-01-171-0/+16
| | | | | | | | | | | | | | | | This allows a user to restore the previous behavior where NetworkManager would not reconfigure the MTU during device activation, if no MTU is available (commit "22e8af6 device: set a per-device default MTU on activation"). Well, not exactly. The previous behavior was to use per-connection configuration, then DHCP provided value, or finally leave the MTU unspecified. Now, we prefer a per-connection configuration, followed by a global connection default. If "ethernet.mtu=0", the MTU is left unspecified. In absense of a global connection default, the value from DHCP is used or finally a per-device-type default. That is effectively 1500 for most types, except for infiniband where the MTU is still left unspecified.
* man: minor fix to nmcli.xmlFrancesco Giudici2017-01-091-1/+1
|
* device: support dynamic "connection.stable-id" in form of text-substitutionThomas Haller2017-01-091-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Usecase: when connecting to a public Wi-Fi with MAC address randomization ("wifi.cloned-mac-address=random") you get on every re-connect a new IP address due to the changing MAC address. "wifi.cloned-mac-address=stable" is the solution for that. But that means, every time when reconnecting to this network, the same ID will be reused. We want an ID that is stable for a while, but at a later point a new ID should e generated when revisiting the Wi-Fi network. Extend the stable-id to become dynamic and support templates/substitutions. Currently supported is "${CONNECTION}", "${BOOT}" and "${RANDOM}". Any unrecognized pattern is treated verbaim/untranslated. "$$" is treated special to allow escaping the '$' character. This allows the user to still embed verbatim '$' characters with the guarantee that future versions of NetworkManager will still generate the same ID. Of course, a user could just avoid '$' in the stable-id unless using it for dynamic substitutions. Later we might want to add more recognized substitutions. For example, it could be useful to generate new IDs based on the current time. The ${} syntax is extendable to support arguments like "${PERIODIC:weekly}". Also allow "connection.stable-id" to be set as global default value. Previously that made no sense because the stable-id was static and is anyway strongly tied to the identity of the connection profile. Now, with dynamic stable-ids it gets much more useful to specify a global default. Note that pre-existing stable-ids don't change and still generate the same addresses -- unless they contain one of the new ${} patterns.
* man: replace libnm-util reference with libnm-core in nm-settings pageJiří Klimeš2016-12-151-3/+3
|
* man: add unsupported settings to the list in nm-settings-ifcfg-rh pageJiří Klimeš2016-12-151-1/+1
|
* config/trivial: unify name of compile time config defaultsThomas Haller2016-11-252-8/+8
|
* man: clarify dns=default setting in NetworkManager.conf manualThomas Haller2016-11-141-7/+11
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=774399
* man: use <filename> to mark file namesLubomir Rintel2016-11-112-19/+24
| | | | | This gives the templates a chance to do something extra clever with the formatting. The templates, of course, choose not to :(
* man: link to some online resourcesLubomir Rintel2016-11-111-0/+9
|
* man: get rid of the extra capitalization in docbook sourceLubomir Rintel2016-11-111-2/+2
| | | | The temaplates capitalize the names if they wish.
* man: use /run instead of /var/runLubomir Rintel2016-11-031-5/+5
| | | | /var/run is just a compatibility symlink, according to file-hierarchy(7).
View Lorry Controller Status