summaryrefslogtreecommitdiff
path: root/man/nmcli.xml
Commit message (Collapse)AuthorAgeFilesLines
* man/nmcli: document variables affecting fancy outputLubomir Rintel2022-10-111-1/+40
| | | | | | Notably, PAGER, TERM and NO_COLORS. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1419
* nmcli/devices: add "checkpoint" commandlr/nmcli-checkpointLubomir Rintel2022-06-151-1/+29
| | | | | | | | | | | | | | | This is an interface to the Checkpoint/Restore functionality that's available for quite some time. It runs a command with a checkpoint taken and rolls back unless success is confirmed before the checkpoint times out: $ nmcli dev checkpoint eth0 -- nmcli dev dis eth0 Device 'eth0' successfully disconnected. Type "Yes" to commit the changes: No Checkpoint was removed. The details about how it's used are documented in nmcli(1) and nmcli-examples(7).
* nmcli: add --offline option for "add" and "modify"Lubomir Rintel2022-04-191-2/+30
| | | | | | | | | | | | | | | | | | | | | This adds a global "--offline" option and allows its use with "add" and "modify" commands. The "add" looks like this: $ nmcli --offline conn add type ethernet ens3 ipv4.dns 192.168.1.1 \ >output.nmconnection The "modify" is essentially implementing what's been suggested by Beniamino in bugzilla ticked (referred to below): $ nmcli --offline connection modify ens3 ipv4.dns 192.168.1.1 \ <input.nmconnection >output.nmconnection Other commands don't support the argument at the moment: $ nmcli --offline c up ens3 Error: 'up' command doesn't support --offline mode. https://bugzilla.redhat.com/show_bug.cgi?id=1361145
* cli: add "connection migrate" subcommandlr/conn-migrateLubomir Rintel2022-03-281-0/+35
| | | | This is used to move a connection to a different settings plugin.
* cli: add color codes for deprecated featuresLubomir Rintel2022-03-131-0/+14
| | | | | | | Follow-up commits are going color Wi-Fi networks and connections that rely on deprecated features differently, to provide a visual cue. Add color definitions for those.
* cli: document connection/device-external colorsLubomir Rintel2022-03-091-0/+14
| | | | | | | | These were added without documentation. Fixes: 16cff1149a76 ('core: fix taking over external connection after restart') https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1137
* man/cli: mention `nmcli device up|down` instead of `nmcli device ↵Thomas Haller2021-07-091-4/+4
| | | | connect|disconnect`
* man/cli: minor cleanups in "nmcli.xml"Thomas Haller2021-07-091-7/+7
|
* cli: add alias to nmcli device connect|disconnectVojtech Bubela2021-07-091-2/+27
| | | | | | | nmcli now accepts `nmcli device up|down` which works the same way as `nmcli device connect|disconnect` I also edited man pages of nmcli with new options.
* man: document the 'nmcli general reload' commandBeniamino Galvani2021-05-031-0/+61
|
* veth: add support to configure veth interfacesFernando Fernandez Mancera2020-11-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | NetworkManager is now able to configure veth interfaces throught the NMSettingVeth. Veth interfaces only have "peer" property. In order to support Veth interfaces in NetworkManager the design need to pass the following requirements: * Veth setting only has "peer" attribute. * Ethernet profiles must be applicable to Veth interfaces. * When creating a veth interface, the peer will be managed by NetworkManager but will not have a profile. * Veth connection can reapply only if the peer has not been modified. * In order to modify the veth peer, NetworkManager must deactivate the connection and create a new one with peer modified. In general, it should support the basis of veth interfaces but without breaking any existing feature or use case. The users that are using veth interfaces as ethernet should not notice anything changed unless they specified the veth peer setting. Creating a Veth interface in NetworkManager is useful even without the support for namespaces for some use cases, e.g "connecting one side of the veth to an OVS bridge and the other side to a Linux bridge" this is done when using OVN kubernetes [1][2]. In addition, it would provide persistent configuration and rollback support for Veth interfaces. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1885605 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1894139 Signed-off-by: Fernando Fernandez Mancera <ffmancera@riseup.net>
* man: update supported connection types in `man nmcli`Thomas Haller2020-11-171-5/+45
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/444
* man: sort supported connection types in `man nmcli`Thomas Haller2020-11-171-17/+17
|
* man: update nmcli.xml wordingCharlie Getzen2020-07-211-1/+1
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/582
* all: fix minor typosYuri Chornoivan2020-07-071-5/+5
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/565
* all: fix typo in man pagesSayed Shah2020-07-031-2/+2
| | | | | | | | There should be a comma after 'Otherwise' and 'Currently'. https://bugzilla.redhat.com/show_bug.cgi?id=1852452 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/560
* docs: drop "property aliases" section from `man nmcli`Thomas Haller2020-06-121-411/+14
| | | | | The aliases are now shown in `man nm-settings-nmcli`. Also the list there gets generated and isn't hardcoded.
* man: fix obsolete references to monitor-connection-files in manual pagesThomas Haller2020-04-101-6/+3
| | | | | | | monitor-connection-files was deprecated and disabled by default for a long time. In the meantime, it has no effect at all. Remove references from the manual pages.
* cli: support setting removalBeniamino Galvani2020-03-231-0/+17
|
* cli: add "nmcli d wifi show"lr/nmcli-d-wifi-showLubomir Rintel2019-10-181-0/+13
| | | | | | A quick overview of the currently connected Wi-Fi network, including credentials. Comes handy if someone wants to connect more devices to their Hotspot or the same network as they are connected to.
* cli: honor NO_COLOR environment variable to prevent automatic ASCII colorsThomas Haller2019-10-081-0/+3
| | | | See-also: https://no-color.org/
* 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 reference for reporting bugs in `man nmcli`Thomas Haller2019-06-111-2/+2
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/188
* 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.
* | all: say Wi-Fi instead of "wifi" or "WiFi"Lubomir Rintel2018-11-291-2/+2
|/ | | | | | | | 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.
* 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: 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.
* cli: sort options in man page and program helpBeniamino Galvani2018-11-051-104/+104
| | | | Options are displayed in a random order, sort them.
* 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.
* client: support 6lowpan settingLubomir Rintel2018-06-261-0/+9
|
* client: support wpan settingLubomir Rintel2018-06-261-0/+11
|
* cli/devices: rescan the Wi-Fi network if the AP list is not fresh enoughlr/cli-wifi-list-rescanLubomir Rintel2018-06-131-0/+10
|
* cli: allow setting the colors with terminal-colors.d(5)lr/nmcli-colorsLubomir Rintel2018-05-101-2/+270
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The present version of the specification is somewhat unclear at times, Unclear points were discussed with the maintainers [1] and probably some new version will address those. https://www.spinics.net/lists/util-linux-ng/msg15222.html Until then here's how the implementation copes with ambiguities (after the discussion with util-linux maintainers): 1.) It is unclear whether multiple .schem files should override each other or be merged. We use the overriding behavior -- take the highest priority one and ignore the rest. 2.) We assume "name.schem" is more specific than "@term.schem". 3.) We assume the "Color name" are to be used as aliases for the color sequences and translate them to ANSI escape sequences. 4.) The "Escape sequences" are of no use since the specification pretty much assumes an ANSI terminal and none of the sequences make any sense in ANSI color codes. We don't support them. accept that. 5.) We don't implement TERMINAL_COLORS_DEBUG because it's unspecified what should it do.
* 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
* man: nmcli: grammar fixBeniamino Galvani2017-08-301-3/+3
| | | | s/It's equivalent of/It's equivalent to/
* clients: add support for Bluetooth NAP typeLubomir Rintel2017-05-311-4/+4
|
* nmcli: add -g[et-values] option as a '-m tab -t -f <arg>' shortcutFrancesco Giudici2017-03-281-4/+24
| | | | Quick and easy way to get clean and parsable field values.
* cli: support dummy connectionsBeniamino Galvani2017-02-221-0/+1
|
* man: minor fix to nmcli.xmlFrancesco Giudici2017-01-091-1/+1
|
* man: clarify behavior of "ip4"/"ip6" alias to nmcliThomas Haller2016-11-021-7/+8
|
* cli: support qualifying proxy.pac-script with "file://" or "js://"Thomas Haller2016-10-041-0/+13
|
* cli: support explicitly selecting team-config as file or json dataThomas Haller2016-09-271-6/+10
| | | | | | | | | | | | | | nmcli has a heuristic when setting the team-config to accepting both a filename or the plain json text. Add support for two schemes "file://" and "json://" to explicitly determine whether to read from file or from json. Also, no longer silently ignore an all-whitespace word. That is an error (unless you have a file named " "). Also, no longer replace newlines with space. Don't mangle the input text at all.
* man: document completionLubomir Rintel2016-08-011-0/+17
|
* cli: add ability to indicate command completion expects a file nameLubomir Rintel2016-08-011-0/+7
|
* man: additional fixes for nmcli commands syntax in nmcli.xmlJiří Klimeš2016-07-191-9/+9
|
View Lorry Controller Status