summaryrefslogtreecommitdiff
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* devices/wifi: support Mesh modeLubomir Rintel2019-07-291-0/+1
| | | | | This puts together the bits from previous commits and actually allows for activating a mode=mesh connection.
* NEWS: updateThomas Haller2019-07-261-1/+23
|
* NEWS: add news entries with changes from 1.18.2Thomas Haller2019-07-261-0/+19
|
* settings: drop ibft settings pluginth/drop-ibft-settings-pluginThomas Haller2019-06-201-0/+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
* NEWS: updateThomas Haller2019-06-111-0/+3
|
* settings: drop deprecated NetworkManager.conf option ↵Thomas Haller2019-05-281-0/+4
| | | | | | | | | | | | | | | "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.
* NEWS: updateLubomir Rintel2019-05-031-0/+2
|
* build: default to internal DHCP clientLubomir Rintel2019-04-161-0/+4
| | | | | | | Meson builds already seem to default this and RHEL & Fedora switched already. Everyone else also should. https://github.com/NetworkManager/NetworkManager/pull/345
* all: goodbye libnm-glibLubomir Rintel2019-04-161-0/+3
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* release: update NEWSThomas Haller2019-04-131-3/+10
|
* release: update NEWSThomas Haller2019-04-131-0/+6
|
* Revert "all: goodbye libnm-glib"Lubomir Rintel2019-04-031-3/+0
| | | | | | We need this for a little little longer :( This reverts commit 1de8383ad9fdfc8f552117e5d109bdfa7005634b.
* all: goodbye libnm-glibLubomir Rintel2019-03-191-0/+3
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* release: bump version to 1.17.1-dev after 1.16.0 release1.17.1-devThomas Haller2019-03-151-0/+10
|\ | | | | | | | | | | | | | | | | | | After 1.16.0 is released, merge it back into master so that 1.16.0 is part of the history of master. That means, $ git log --first-parent master will also traverse 1.16.0 and 1.16-rc*. Also bump the micro version to 1.17.1-dev to indicate that this is after 1.16.0 is out.
| * all: codespell fixesLubomir Rintel2019-03-111-4/+4
| | | | | | | | | | Codespel run with the same arguments as described in commit 58510ed56679 ('docs: misc. typos pt2').
| * release: update NEWSThomas Haller2019-02-231-3/+10
| |
* | release: update NEWSThomas Haller2019-03-151-4/+1
| |
* | all: codespell fixesLubomir Rintel2019-03-111-4/+4
| | | | | | | | | | | | | | Codespel run with the same arguments as described in commit 58510ed56679 ('docs: misc. typos pt2'). (cherry picked from commit bf0c4e6ac2855088e3962693886bb6ab71856f7b)
* | release: update NEWSThomas Haller2019-02-231-0/+4
|/
* release: update NEWSThomas Haller2019-02-231-0/+20
|
* release: update NEWS with entires from 1.14.6Thomas Haller2019-02-231-5/+40
|
* release: update NEWSth/wireguard-pt3Thomas Haller2019-02-221-0/+3
|
* release: update NEWSThomas Haller2019-02-151-0/+3
|
* NEWS: Add an entry for Wi-Fi P2PBenjamin Berg2019-01-281-0/+1
|
* NEWS: Add an entry for NMKeepAlive and DBus client bindingBenjamin Berg2019-01-281-0/+1
|
* all: say Wi-Fi instead of "wifi" or "WiFi"Lubomir Rintel2018-11-291-14/+14
| | | | | | | | 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-2/+2
| | | | | | Also affects documentation and translated strings. Reported-by: Flavio Leitner <fbl@redhat.com>
* release: update NEWSThomas Haller2018-10-171-0/+27
|
* docs: misc. typos pt2luz.paz2018-09-171-6/+6
| | | | | | | | | | | | | | | | | | | | | Remainder of typos found using `codespell -q 3 --skip="./shared,./src/systemd,*.po" -I ../NetworkManager-word-whitelist.txt` whereby whitelist consists of: ``` ans busses cace cna conexant crasher iff liftime creat nd sav technik uint ``` https://github.com/NetworkManager/NetworkManager/pull/205
* release: update NEWSThomas Haller2018-09-141-6/+5
|
* release: update NEWSThomas Haller2018-09-071-0/+10
|
* release: update NEWSThomas Haller2018-08-131-0/+3
|
* core: implement connection.multi-connect to activate profiles multiple timesThomas Haller2018-08-081-0/+2
| | | | | | | | Make use of the new property, and implement it. See previous commits for the reasons why. https://bugzilla.redhat.com/show_bug.cgi?id=1555012
* libnm: fix missing symbols in libnm ABIThomas Haller2018-06-301-1/+11
| | | | | Also backport the ABI to 1.12.2 (and thus, don't bother initially adding the API as libnm_1_14_0).
* release: bump version to 1.13.1-dev after 1.12.0 release1.13.1-devThomas Haller2018-06-291-0/+7
|\ | | | | | | | | | | | | | | | | | | After 1.12.0 is released, merge it back into master so that 1.12.0 is part of the history of master. That means, $ git log --first-parent master will also traverse 1.12.0 and 1.12-rc*. Also bump the micro version to 1.13.1-dev to indicate that this is after 1.12.0 is out.
| * NEWS: add an entry for WPAN & 6LowPAN supportlr/6lowpanLubomir Rintel2018-06-261-0/+7
| |
| * dispatcher: add NM_DISPATCHER_ACTION environment variableThomas Haller2018-06-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the action was only passed as the first command line argument to the dispatcher scripts. Now, also set it via the "$NM_DISPATCHER_ACTION" environment variable. The main purpose is to have a particular, nm-dispatcher specific variable that is always set inside the dispatcher scripts. For example, imagine you have a script that can be either called by dispatcher or some other means (manually, or spawned via /etc/NetworkManager/dispatcher.d/11-dhclient). Then it might make sense to differenciate from inside the script whether you are called by nm-dispatcher. But previously, there was no specific environment variable that was always set inside the dispatcher event. For example, with the "hostname" action there are no other environment variables. Now (with version 1.12), you can check for `test -n "$NM_DISPATCHER_ACTION"`.
| * release: update NEWS for 1.10.10 releaseThomas Haller2018-06-181-1/+2
| | | | | | | | | | | | | | 1.10.10 was released still before 1.12.0. Update the NEWS to reflect that. (cherry picked from commit f8dfc436b13f7a2f15e1f1a81086ba4b38e90ee4)
* | release: update NEWSThomas Haller2018-06-291-5/+2
| |
* | release: fix NEWS entry for NM_DISPATCHER_ACTIONThomas Haller2018-06-291-1/+1
| | | | | | | | This was not backported to nm-1-10 branch.
* | dispatcher: add NM_DISPATCHER_ACTION environment variableThomas Haller2018-06-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the action was only passed as the first command line argument to the dispatcher scripts. Now, also set it via the "$NM_DISPATCHER_ACTION" environment variable. The main purpose is to have a particular, nm-dispatcher specific variable that is always set inside the dispatcher scripts. For example, imagine you have a script that can be either called by dispatcher or some other means (manually, or spawned via /etc/NetworkManager/dispatcher.d/11-dhclient). Then it might make sense to differenciate from inside the script whether you are called by nm-dispatcher. But previously, there was no specific environment variable that was always set inside the dispatcher event. For example, with the "hostname" action there are no other environment variables. Now (with version 1.12), you can check for `test -n "$NM_DISPATCHER_ACTION"`. (cherry picked from commit ce9619047c5daac9a006d16d07453d50e0520e71)
* | release: update NEWS for 1.10.10 releaseThomas Haller2018-06-181-1/+2
|/ | | | | 1.10.10 was released still before 1.12.0. Update the NEWS to reflect that.
* release: update NEWSThomas Haller2018-06-151-19/+25
|
* build: disable libnm-glib by defaultLubomir Rintel2018-06-151-0/+4
| | | | | | | It's deprecated and has been replaced by libnm for 6 major releases now. Its use in modern distributions has faded to the point it can probably be safely removed.
* NEWS: add note about new WoWLAN settingsAlfonso Sánchez-Beato2018-06-151-0/+2
|
* dns: change main.rc-manager=file behavior to always follow symlinkThomas Haller2018-06-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With "main.rc-manager=file", if /etc/resolv.conf is a symlink, NetworkManager would follow the symlink and update the file instead. However, note that realpath() only returns a target, if the file actually exists. That means, if /etc/resolv.conf is a dangling symlink, NetworkManager would replace the symlink with a file. This was the only case in which NetworkManager would every change a symlink resolv.conf to a file. I think this is undesired behavior. This is a change in long established behavior. Although note that there were several changes regarding rc-manager settings in the past. See for example commit [1] and [2]. Now, first still try using realpath() as before. Only if that fails, try to resolve /etc/resolv.conf as a symlink with readlink(). Following the dangling symlink is likely not a problem for the user, it probably is even desired. The part that most likely can cause problems is if the destination file is not writable. That happens for example, if the destination's parent directories are missing. In this case, NetworkManager will now fail to write resolv.conf and log a warning. This has the potential of breaking existing setups, but it really is a mis-configuration from the user's side. This fixes for example the problem, if the user configures /etc/resolv.conf as symlink to /tmp/my-resolv.conf. At boot, the file would not exist, and NetworkManager would previously always replace the link with a plain file. Instead, it should follow the symlink and create the file. [1] 718fd2243690b8c72dd1cb32f67114f304542082 [2] 15177a34be297654086005f2d796e6a4c6a1b918 https://github.com/NetworkManager/NetworkManager/pull/127
* release: update NEWS for a development snapshotLubomir Rintel2018-05-311-0/+53
|
* dhcp: dhclient: set type 0 for printable client IDsBeniamino Galvani2018-03-151-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | The documentation for the ipv4.dhcp-client-id property says: 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. However, currently we set the client-id without the leading zero byte in the dhclient configuration and thus dhclient sends the first string character as type and the remainder as client-id content. Looking through git history, the dhclient plugin has always behaved this way even if the intent was clearly that string client-id had to be zero padded (this is evident by looking at nm_dhcp_utils_client_id_string_to_bytes()). The internal plugin instead sends the correct client-id with zero type. Change the dhclient plugin to honor the documented behavior and add the leading zero byte when the client-id is a string. This commit introduces a change in behavior for users that have dhcp=dhclient and have a plain string (not hexadecimal) set in ipv4.dhcp-client-id, as NM will send a different client-id possibly changing the IP address returned by the server. https://bugzilla.gnome.org/show_bug.cgi?id=793957
* all: drop trailing spacesThomas Haller2018-02-071-1/+1
|
* release: update NEWSBeniamino Galvani2017-11-101-4/+3
|
View Lorry Controller Status