summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* man: add examples how to configure bluetooth devices to `man nmcli-examples`.Thomas Haller2019-09-221-0/+22
|
* cli: add kill switch indication to "nmcli" outputLubomir Rintel2019-09-201-0/+7
| | | | | | | | There is some guess work done on the client side. Perhaps the o.fd.NM.Device could be extended to indicate which kill switch is the device disabled by. This could be good enough for now though. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/271/commits
* man/cli: better explain modifying properties regarding +/- modifiersThomas Haller2019-08-161-10/+12
|
* man: update nm-openswitch exampleFrancesco Giudici2019-07-091-2/+2
| | | | | | | | | | | | | | Seems that a quite common openswitch basic configuration consist of a one bridge, one port and one interface, all with the same interface name. When performing such configuration in NetworkManager you need to specify the slave-type for the ovs-interface, otherwise the master interface specified there may match the bridge interface, resulting in an error. So, let's specify the slave-type for the ovs-interface, so that the example will work also when the same interface name is specified for both the ovs-bridge and the ovs-port. https://bugzilla.redhat.com/show_bug.cgi?id=1638038
* settings: drop ibft settings pluginth/drop-ibft-settings-pluginThomas Haller2019-06-201-11/+2
| | | | | | | | | | | | | | | The functionality of the ibft settings plugin is now handled by nm-initrd-generator. There is no need for it anymore, drop it. Note that ibft called iscsiadm, which requires CAP_SYS_ADMIN to work ([1]). We really want to drop this capability, so the current solution of a settings plugin (as it is implemented) is wrong. The solution instead is nm-initrd-generator. Also, on Fedora the ibft was disabled and probably on most other distributions as well. This was only used on RHEL. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1371201#c7
* man: update reference for reporting bugs in `man nmcli`Thomas Haller2019-06-111-2/+2
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/188
* settings: drop deprecated NetworkManager.conf option ↵Thomas Haller2019-05-281-23/+1
| | | | | | | | | | | | | | | "main.monitor-connection-files" It's deprecated and off by default for a long time. It is bad to automatically reload connection profiles. For example, ifcfg files may consist of multiple files, there is no guarantee that we pick up the connection when it's fully written. Just don't do this anymore. Users should use D-Bus API or `nmcli connection reload` or `nmcli connection load $FILENAME` to reload profiles from disk.
* doc: replace "Split DNS" with "Conditional Forwarding"Jonas DOREL2019-05-171-4/+4
| | | | | | | | | Split DNS usually refers to "Split Horizon DNS" whereas "Conditional Forwarding" is specifically for what the documentation describes. [thaller@redhat.com: rewrote commit message] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/143
* wireguard: add "mtu" setting for WireGuard profilesThomas Haller2019-03-051-0/+3
| | | | | | This adds new API for 1.16.0 and is an ABI break since 1.16-rc1. (cherry picked from commit d5e93ae613fd355351bdf37530cae3d3dfb4e5ba)
* man: add a warning to NetworkManager.conf manual for rp_filter and ↵Thomas Haller2019-02-081-0/+8
| | | | connectivity checking
* man: explain purpose of connectivity checking in `man NetworkManager.conf`Thomas Haller2019-02-051-0/+9
|
* man: fix a typoLubomir Rintel2019-02-051-1/+1
|
* man: better explain "connectivity.response" in "NetworkManager.conf" manualThomas Haller2019-01-311-5/+8
|
* connectivity: fix handling of no-response for captive portal detectionThomas Haller2019-01-311-1/+3
| | | | | | | | | | | | | Since we only compare that the HTTP response starts with the expected response, we need to handle the empty expected response specially (because, every response has "" as prefix). So now if connectivity.response is set to "" (empty) we accept: - HTTP status code 204. We ignore and accept any extra data that we might receive. - HTTP status code 200 and an empty (or no) body.
* all: fix misspellingsRafael Fontenelle2019-01-241-1/+1
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/64
* merge: branch 'master' of https://github.com/balrog-kun/NetworkManagerLubomir Rintel2019-01-041-7/+6
|\ | | | | | | https://github.com/NetworkManager/NetworkManager/pull/137
| * cli: reuse connections in nmcli dev wifi conAndrew Zaborowski2018-12-041-7/+6
| | | | | | | | | | | | | | Try to locate an existing connection before creating a new one when handling "nmcli device wifi connect". This allows WPA-Enterprise networks to be activated this way, consistent with the comment that this command is equivalent to clicking on an SSID in a GUI client.
* | build: meson: Add trailing commasIñigo Martínez2018-12-201-6/+6
| | | | | | | | | | | | | | Add missing trailing commas that avoids getting noise when another file/parameter is added and eases reviewing changes[0]. [0] https://gitlab.gnome.org/GNOME/dconf/merge_requests/11#note_291585
* | man: add SR-IOV nmcli exampleBeniamino Galvani2018-12-121-0/+17
| | | | | | | | | | | | | | Add an example on how to configure SR-IOV to the nmcli examples man page. https://bugzilla.redhat.com/show_bug.cgi?id=1651979
* | core: fix match spec behavior for a list of all "except:"Thomas Haller2018-12-111-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the spec specifies only negative matches (and none of them matches), then the result shall be positive. Meaning: [connection*] match-device=except:dhcp-plugin:dhclient [connection*] match-device=except:interface-name:eth0 [.config] enabled=except:nm-version:1.14 should be the same as: [connection*] match-device=*,except:dhcp-plugin:dhclient [connection*] match-device=*,except:interface-name:eth0 [.config] enabled=*,except:nm-version:1.14 and match by default. Previously, such specs would never yield a positive match, which seems wrong. Note that "except:" already has a special meaning. It is not merely "not:". That is because we don't support "and:" nor grouping, but all matches are combined by an implicit "or:". With such a meaning, having a "not:" would be unclear to define. Instead it is defined that any "except:" match always wins and makes the entire condition to explicitly not match. As such, it makes sense to treat a match that only consists of "except:" matches special. This is a change in behavior, but the alternative meaning makes little sense.
* | connectivity: honor "main.systemd-resolved" setting to not resolve names firstThomas Haller2018-12-111-1/+3
| | | | | | | | | | | | | | | | | | | | | | If the user disabled systemd-resolved, two things seem apparent: - the user does not want us to use systemd-resolved - NetworkManager is not pushing the DNS configuration to systemd-resoved. It seems to me, we should not consult systemd-resolved in that case.
* | core: add checks on connection default propertiesBeniamino Galvani2018-12-011-0/+4
| | | | | | | | | | | | | | | | | | | | Add a new CON_DEFAULT() macro that places a property name into a special section used at runtime to check whether it is a supported connection default. Unfortunately, this mechanism doesn't work for plugins so we have to enumerate the connection defaults from plugins in the daemon using another CON_DEFAULT_NOP() macro.
* | man: add missing connection defaultsBeniamino Galvani2018-12-011-0/+12
| |
* | all: say Wi-Fi instead of "wifi" or "WiFi"Lubomir Rintel2018-11-293-4/+4
|/ | | | | | | | Correct the spelling across the *entire* tree, including translations, comments, etc. It's easier that way. Even the places where it's not exposed to the user, such as tests, so that we learn how is it spelled correctly.
* doc,all: fix spelling of Open vSwitch (instead of OpenVSwitch)Thomas Haller2018-11-281-9/+9
| | | | | | Also affects documentation and translated strings. Reported-by: Flavio Leitner <fbl@redhat.com>
* man: advise against configuring "monitor-connection-files" in ↵Thomas Haller2018-11-231-0/+9
| | | | NetworkManager.conf
* man: fix typo in nmcli manualThomas Haller2018-11-141-1/+1
| | | | Fixes: 17f9801e07df0c544e0416c65cedc28727476e55
* man: add an early reference to nmcli-examples in nmcli man pageFrancesco Giudici2018-11-141-1/+3
|
* man: add OTP-based VPN activation exampleFrancesco Giudici2018-11-141-0/+13
|
* man: document global connection default for "ipv4.dns-priority"Thomas Haller2018-11-131-0/+10
| | | | | | ... and "ipv6.dns-priority". Fixes: 77ded12da46457848e86561b0e9460f03302e6e8
* man: clarify blocking autoconnect during `nmcli connection down`Thomas Haller2018-11-131-3/+4
| | | | | | | | | | | | | | Manually disconnecting a profile of course blocks autoconnect of the same profile. Otherwise, the profile would likely re-activate right away, which is clearly against the users intention. If the users just want to re-activate the profile, they should issue `nmcli connection up` instead, with does a full down and up cycle. This is more interesting for profiles that have 'connection.multi-connect' set to 'multiple'. Would you expect that manually deactivating such a profile blocks autoconnect of the profile on all devices? Maybe yes, maybe not. Currently that is indeed the case and autoconnect gets blocked regardless of multi-connect.
* nm-online: sort options in man page and program helpBeniamino Galvani2018-11-051-19/+30
|
* cli: sort options in man page and program helpBeniamino Galvani2018-11-051-104/+104
| | | | Options are displayed in a random order, sort them.
* device: add "dhcp-plugin" match spec for deviceThomas Haller2018-11-011-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The need for this is the following: "ipv4.dhcp-client-id" can be specified via global connection defaults. In absence of any configuration in NetworkManager, the default depends on the DHCP client plugin. In case of "dhclient", the default further depends on /etc/dhcp. For "internal" plugin, we may very well want to change the default client-id to "mac" by universally installing a configuration snippet [connection-use-mac-client-id] ipv4.dhcp-client-id=mac However, if we the user happens to enable "dhclient" plugin, this also forces the client-id and overrules configuration from /etc/dhcp. The real problem is, that dhclient can be configured via means outside of NetworkManager, so our defaults shall not overwrite defaults from /etc/dhcp. With the new device spec, we can avoid this issue: [connection-dhcp-client-id] match-device=except:dhcp-plugin:dhclient ipv4.dhcp-client-id=mac This will be part of the solution for rh#1640494. Note that merely dropping a configuration snippet is not yet enough. More fixes for DHCP will follow. Also, bug rh#1640494 may have alternative solutions as well. The nice part of this new feature is that it is generally useful for configuring connection defaults and not specifically for the client-id issue. Note that this match spec is per-device, although the plugin is selected globally. That makes some sense, because in the future we may or may not configure the DHCP plugin per-device or per address family. https://bugzilla.redhat.com/show_bug.cgi?id=1640494
* man: clarify udev property "NM_UNMANAGED" in `man NetworkManager`Thomas Haller2018-10-261-10/+7
|
* man: fix "no-auto-default" state dir in NetworkManager.conf manualThomas Haller2018-10-253-1/+3
| | | | | | | | | | | | | Quote from `man NetworkManager.conf`: When the default wired connection is deleted or saved to a new persistent connection by a plugin, the device is added to a list in the file /run/NetworkManager/no-auto-default.state to prevent creating the default connection for that device again. "/run" is obviously wrong. Fix it. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/33
* man: document `nmcli device connect` behaviourThomas Haller2018-10-171-0/+5
| | | | | | | | | | | | | | Already since 1.0.0 release and commit "3784678177 cli: create a connection if none exist in 'nmcli dev connect' (rh #1113941)", device-connect can also create a profile. That is useful, in particular as opposed to $ nmcli connection up ifname "$DEVICE" which wouldn't create a profile (ever). Document it.
* build: meson: fix generation of api docsBeniamino Galvani2018-09-281-2/+0
| | | | | | | | | | We need to copy all introspection files to the same directory when building the documentation. Note that we only require Meson 0.44, but for the documentation at least 0.46 is needed because of a new functionality of gnome.gdbus_codegen(). In this way we can still build on Travis CI (without documentation).
* build: meson: add missing man fileBeniamino Galvani2018-09-281-1/+2
| | | | Fixes: 9f9609555d1c8606b2a177151b2e255b34c5594a
* dns: allow loading nm-dns-systemd-resolve alongside other DNS pluginsLubomir Rintel2018-09-241-0/+14
| | | | | | | | | | | | | | Even when the system resolver is configured to something else that systemd-resolved, it still is a good idea to keep systemd-resolved up to date. If not anything else, it does a good job at doing per-interface resolving for connectivity checks. If for whatever reasons don't want NetworkManager to push the DNS data it discovers to systemd-resolved, the functionality can be disabled with: [main] systemd-resolved=false
* dns: minor rewording of main.dns in `man NetworkManager.conf`Thomas Haller2018-09-211-2/+2
|
* dns: write original DNS servers to /var/run/NetworkManager/no-stub-resolv.confThomas Haller2018-09-211-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a DNS plugin is enabled (like "main.dns=dnsmasq" or "main.dns=systemd-resolved"), the name servers announced to the rc-manager are coerced to be 127.0.0.1 or 127.0.0.53. Depending on the "main.rc-manager" setting, also "/etc/resolv.conf" contains only this coerced name server to the local caching service. The same is true for "/var/run/NetworkManager/resolv.conf" file, which contains what we would write to "/etc/resolv.conf" (depending on the "main.rc-manager" configuration). Write a new file "/var/run/NetworkManager/no-stub-resolv.conf", which contains the original name servers, uncoerced. Like "/var/run/NetworkManager/resolv.conf", this file is always written. The effect is, when one enables "main.dns=systemd-resolved", then there is still a file "no-stub-resolv.conf" with the same content as with "main.dns=default". The no-stub-resolv.conf may be a possible solution, when a user wants NetworkManager to update systemd-resolved, but still have a regular /etc/resolv.conf [1]. For that, the user could configure [main] dns=systemd-resolved rc-manager=unmanaged and symlink "/etc/resolv.conf" to "/var/run/NetworkManager/no-stub-resolv.conf". This is not necessarily the only solution for the problem and does not preclude options for updating systemd-resolved in combination with other DNS plugins. [1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/20
* build: meson: gtk-doc needs common.entBeniamino Galvani2018-09-191-0/+2
|
* build: meson: man files depend on common.entBeniamino Galvani2018-09-191-1/+2
|
* man/NetworkManager: document --configure-and-quit optionlr/initrdLubomir Rintel2018-09-181-0/+7
|
* initrd: add configuration generatorLubomir Rintel2018-09-181-0/+140
| | | | | | nm-initrd-generator scans the command line for options relevant to network configuration and creates configuration files for an early instance of NetworkManager run from the initial ramdisk during early boot.
* core: add support for connection.llmnrBeniamino Galvani2018-09-061-0/+3
|
* man/openvswitch: advise to use "master" instead of "conn.master"Lubomir Rintel2018-08-061-9/+9
| | | | | | | It does some extra magic -- normalizes the value and initializes slave-type. https://bugzilla.redhat.com/show_bug.cgi?id=1519176
* device: configure SR-IOVBeniamino Galvani2018-07-111-0/+4
|
* man/trivial: fix heading comment in nm-openvswitch.xmlFrancesco Giudici2018-07-061-1/+1
|
View Lorry Controller Status