summaryrefslogtreecommitdiff
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* NEWS: update for a release candidateBeniamino Galvani2017-11-031-0/+51
|
* release: update NEWSThomas Haller2017-05-101-5/+20
|
* release: update NEWSLubomir Rintel2017-04-201-1/+1
|
* NEWS: update for a release candidateLubomir Rintel2017-03-281-1/+8
|
* NEWS: update for a development snapshotLubomir Rintel2017-03-231-3/+20
|
* NEWS: updateThomas Haller2017-02-141-0/+14
|
* release: update NEWSThomas Haller2017-01-251-5/+2
|
* NEWS: move the more important entries upwardsLubomir Rintel2017-01-231-12/+12
|
* release: update NEWSLubomir Rintel2017-01-171-1/+16
| | | | Co-authored-by: Thomas Haller <thaller@redhat.com>
* NEWS: belatedly add news entry for th/preserve-fake-perm-hwaddr-bgo772880Thomas Haller2016-12-161-0/+3
| | | | This was already part of 1.5.2-dev.
* NEWS: add entry about th/sysctl-ifname-race-bgo775613 branchThomas Haller2016-12-161-0/+3
|
* NEWS: update for a development snapshotLubomir Rintel2016-12-151-1/+22
|
* NEWS: update for a development snapshotLubomir Rintel2016-11-031-3/+20
|
* device: change default value for cloned-mac-address to "preserve" (bgo#770611)Thomas Haller2016-09-121-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Long ago before commit 1b49f94, NetworkManager did not touch the MAC address at all. Since 0.8.2 NetworkManager would modify the MAC address, and eventually it would reset the permanent MAC address of the device. This prevents a user from externally setting the MAC address via tools like macchanger and rely on NetworkManager not to reset it to the permanent MAC address. This is considered a security regression in bgo#708820. This only changed with commit 9a354cd and 1.4.0. Since then it is possible to configure "cloned-mac-address=preserve", which instead uses the "initial" MAC address when the device activates. That also changed that the "initial" MAC address is the address which was externally configured on the device as last. In other words, the "initial" MAC address is picked up from external changes, unless it was NetworkManager itself who configured the address when activating a connection. However, in absence of an explicit configuration the default for "cloned-mac-address" is still "permanent". Meaning, the user has to explicitly configure that NetworkManager should not touch the MAC address. It makes sense to change the upstream default to "preserve". Although this is a change in behavior since 0.8.2, it seems a better default. This change has the drastic effect that all the existing connections out there with "cloned-mac-address=$(nil)" change behavior after upgrade. I think most users won't notice, because their devices have the permanent address set by default anyway. I would think that there are few users who intentionally configured "cloned-mac-address=" to have NetworkManager restore the permanent address. https://bugzilla.gnome.org/show_bug.cgi?id=770611
* NEWS: update file with changes to PropertiesChanged signalThomas Haller2016-09-021-0/+10
|
* NEWS: updateThomas Haller2016-08-231-2/+2
| | | | (cherry picked from commit 0a04b55491d98a3450cf1750ec96d4c4c819fa5b)
* NEWS: fix spellingThomas Haller2016-08-231-1/+1
| | | | (cherry picked from commit 154c86efc6711f2a8285cc7e74011c972f3b6c92)
* release: update NEWS with recently merged featuresLubomir Rintel2016-08-171-0/+3
|
* release: update NEWSBeniamino Galvani2016-08-031-0/+51
|
* NEWS: fix mistake in NEWS file about wifi.mac-address-randomizationThomas Haller2016-05-191-4/+6
|
* release: update NEWSLubomir Rintel2016-03-291-2/+11
|
* NEWS: minor update referencing 1.0.10 releaseThomas Haller2016-03-161-1/+1
|
* release: update NEWSBeniamino Galvani2016-03-011-1/+12
|
* release: improve NEWSBeniamino Galvani2016-01-211-15/+17
|
* relese: fix NEWS formattingLubomir Rintel2016-01-191-87/+0
| | | | The double spacing was probably a mistake. Also, there was an extra line break.
* release: update NEWSLubomir Rintel2016-01-181-0/+271
|
* NEWS: mention missing feature for 1.0Thomas Haller2015-01-271-1/+2
|
View Lorry Controller Status