summaryrefslogtreecommitdiff
path: root/man/nmcli.xml
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* man: fix 'domain' to 'domains' for nmcli general loggingJiří Klimeš2016-07-151-1/+1
|
* man: fix 'nmcli connection edit' description in nmcli.xmlJiří Klimeš2016-07-151-2/+2
|
* man: fix 'nmcli connection clone' description in nmcli.xmlJiří Klimeš2016-07-151-4/+4
|
* man: correct '--field' option in nmcli man pageJiří Klimeš2016-07-151-1/+1
|
* man: correct '--wait' option in nmcli man pageJiří Klimeš2016-07-151-7/+5
|
* man: fix bridge-port properties description in nmcli.xmlJiří Klimeš2016-07-151-3/+3
|
* man: add missing commands to 'nmcli connection' synopsis in nmcli.xmlJiří Klimeš2016-07-151-0/+3
|
* nmcli: fix 'nmcli device modify' descriptionJiří Klimeš2016-07-151-1/+2
| | | | Fixes: 8b4494598d04b6754a69463a4dc7274fdff8763f
* cli/device: add modify commandlr/device-modifyLubomir Rintel2016-06-291-4/+48
| | | | It modifies the applied connection using the Reapply API.
* man: update the nmcli manual for new connection add syntaxLubomir Rintel2016-06-211-1171/+432
| | | | | | | | | | It allows us to clean up the nmcli "c add" section considerably. We list the old-fashioned aliases in a separate section that applies to both "nmcli c add" and "nmcli c modify". The section is now nicely cross-linked with nm-settings in HTML rendering.
* man: turn the manual page cross-references into linksLubomir Rintel2016-06-211-10/+10
| | | | | | | | This improves the HTML rendering. But it also causes a lot of non-resolvable linkends warning when rendering a separate manual pages into roff/mman. The messages are harmless, but still a bit ugly.
* cli: remove version check against NMFrancesco Giudici2016-04-281-22/+0
| | | | | | | | | | | | When performing NM package upgrade the new version of nmcli will be immediately available while NM daemon will not, as it would not restart in order to avoid to disrupt connectivity. This could create issues with tools leveraging on nmcli output (till reboot). As apart from this case it is very unlikely that a user can have this nmcli / NM daemon version mismatch situation, the check could cause more harm than benefit in real user case scenarios. https://bugzilla.redhat.com/show_bug.cgi?id=1291785
* man: clarify the license of the manualslr/manLubomir Rintel2016-04-081-19/+11
| | | | It's included from GFDL 1.1+ document; it should be GFDL too.
* man: move nmcli-examples to section 7Lubomir Rintel2016-04-051-3/+3
| | | | It really is not a configuration file and doesn't belong to section 5.
* man: include version from a XML entityLubomir Rintel2016-04-051-2/+5
| | | | | | | | This way it's consistently used across all manual page without a need for XSL templating. Also, the entities file could in future possibly be used to template the build-time configurables such as filesystem paths or bug tracker URL.
* man: convert nmcli(1) manual to docbook refentryLubomir Rintel2016-04-051-0/+3113
View Lorry Controller Status