| 10 | [https://download.gnome.org/sources/network-manager-applet/1.0/network-manager-applet-1.0.4.news] |
| 11 | |
| 12 | {{{ |
| 13 | ======================================================= |
| 14 | network-manager-applet-1.0.4 |
| 15 | Overview of changes since network-manager-applet-1.0.2 |
| 16 | ======================================================= |
| 17 | |
| 18 | This is a new stable release of network-manager-applet. Notable changes |
| 19 | include: |
| 20 | |
| 21 | • Setting MTU for a bond device is now supported. |
| 22 | • Connecting to a wireless network from the NetworkManager applet no |
| 23 | longer results in an attempt to create system-wide connections. This |
| 24 | fixes the ability to connect to a wireless network for non-privileged |
| 25 | user. |
| 26 | • The master interface name is used instead of master connection UUID |
| 27 | for slave connections created with nm-connection-editor. This fixes |
| 28 | compatibility of the ifcfg configuration files with the legacy network |
| 29 | service. |
| 30 | • It is now possible to specify an interface name instead of a MAC |
| 31 | address when editing a connection using nm-connection-editor. |
| 32 | • The WWAN connections now have IPv6 enabled by default. |
| 33 | • libnm-gtk includes functions for password storage selection, which |
| 34 | eases implementation of password GUI for VPN plugins and other users. |
| 35 | }}} |
| 36 | |
| 37 | URL (NETWORK MANAGER): |
| 38 | [https://download.gnome.org/sources/NetworkManager/1.0/NetworkManager-1.0.4.tar.xz] |
| 39 | |
| 40 | [http://download.gnome.org/sources/NetworkManager/1.0/NetworkManager-1.0.4.tar.xz.md5] |
| 41 | |
| 42 | 7eabef7bd3bbdd6dc0473dd32aeac924 |
| 43 | |
| 44 | RELEASE ANNOUNCEMENT: |
| 45 | [https://mail.gnome.org/archives/networkmanager-list/2015-July/msg00022.html] |
| 46 | |
| 47 | or |
| 48 | |
| 49 | [https://download.gnome.org/sources/NetworkManager/1.0/NetworkManager-1.0.4.news] |
18 | | * The MTU setting from an IPv6 neighbor discovery Router Advertisements is |
19 | | now ignored if applying it would result in invalid configuration. |
20 | | |
21 | | * Some configuration options can now be changed without restarting the |
22 | | daemon. Notably, this applies to 'dns', 'connectivity' and |
23 | | 'ignore-carrier' settings. |
24 | | |
25 | | * The connection activation was made more robust. If an active connection |
26 | | is reactivated, the device it's active on takes precedence. If an attempt |
27 | | is made to activate a connection on a different device than it is active on, |
28 | | the activation proceeds removing the connection from the active device. |
29 | | |
30 | | * The device specifiers in configuration files now support negation via |
31 | | 'except:' match. |
32 | | |
33 | | * Devices that only have IPv6 link-local address are no longer assumed to |
34 | | be connected. |
35 | | |
36 | | * nmcli now provides hints and tab-completion for enumeration properties. |
37 | | |
38 | | * If the IPv6 interface tokens are set they are honored when creating an |
39 | | interface identifier for IPv6 addressing. |
40 | | |
41 | | * NetworkManager now maintains correct routing configuration when multiple |
42 | | interfaces are connected to the same network. |
43 | | |
44 | | * The management of devices can now be controlled with udev rules. The veth |
45 | | devices as well as the virtual Ethernet devices of various |
46 | | virtualization tools (VMWare, VirtualBox, Parallels Workstation) are |
47 | | now ignored by default. |
48 | | |
49 | | * The IPv6 privacy extensions are now enabled by default and handling of |
50 | | the ip6-privacy sysctl has been improved. |
51 | | |
52 | | * Activating a Bond, Bridge or Team device can now optionally activate the |
53 | | slave connections as well. The behavior is controlled with |
54 | | 'connection.autoconnect-slaves' property. |
55 | | |
56 | | * The platform support code has been refactored, resulting in better |
57 | | scalability in large configurations. |
58 | | |
59 | | * Changes to network interfaces configuration done outside NetworkManager |
60 | | are now picked up and exposed to the user via NetworkManager API and tools. |
61 | | |
62 | | * A connection can now optionally leave externally configured default route |
63 | | in place instead of overriding it. The behavior is controlled with |
64 | | 'ipv4.never-default' and 'ipv6.never-default' properties. |
65 | | |
66 | | * Multiple crasher and memory leak bugs in the daemon were fixed. |
67 | | |
68 | | * Multiple bugs that could cause the client tools to hang or crash were fixed. |
69 | | |
70 | | * nmcli allows multiple devices for 'nmcli device disconnect/delete'. |
71 | | |
72 | | * Firewall zone is added to firewalld for device-based VPN connections too. |
73 | | |
| 60 | • The MTU setting from an IPv6 neighbor discovery Router Advertisements |
| 61 | is now ignored if applying it would result in invalid configuration. |
| 62 | • Some configuration options can now be changed without restarting the |
| 63 | daemon. Notably, this applies to 'dns', 'connectivity' and |
| 64 | 'ignore-carrier' settings. |
| 65 | • The connection activation was made more robust. If an active |
| 66 | connection is reactivated, the device it's active on takes precedence. |
| 67 | If an attempt is made to activate a connection on a different device |
| 68 | than it is active on, the activation proceeds removing the connection |
| 69 | from the active device. |
| 70 | • The device specifiers in configuration files now support negation via |
| 71 | 'except:' match. |
| 72 | • Devices that only have IPv6 link-local address are no longer assumed |
| 73 | to be connected. |
| 74 | • nmcli now provides hints and tab-completion for enumeration |
| 75 | properties. |
| 76 | • If the IPv6 interface tokens are set they are honored when creating an |
| 77 | interface identifier for IPv6 addressing. |
| 78 | • NetworkManager now maintains correct routing configuration when |
| 79 | multiple interfaces are connected to the same network. |
| 80 | • The management of devices can now be controlled with udev rules. The |
| 81 | veth devices as well as the virtual Ethernet devices of various |
| 82 | virtualization tools (VMWare, VirtualBox, Parallels Workstation) are |
| 83 | now ignored by default. |
| 84 | • The IPv6 privacy extensions are now enabled by default and handling of |
| 85 | the ip6-privacy sysctl has been improved. |
| 86 | • Activating a Bond, Bridge or Team device can now optionally activate |
| 87 | the slave connections as well. The behavior is controlled with |
| 88 | 'connection.autoconnect-slaves' property. |
| 89 | • The platform support code has been refactored, resulting in better |
| 90 | scalability in large configurations. |
| 91 | • Changes to network interfaces configuration done outside |
| 92 | NetworkManager are now picked up and exposed to the user via |
| 93 | NetworkManager API and tools. |
| 94 | • A connection can now optionally leave externally configured default |
| 95 | route in place instead of overriding it. The behavior is controlled |
| 96 | with 'ipv4.never-default' and 'ipv6.never-default' properties. |
| 97 | • Multiple crasher and memory leak bugs in the daemon were fixed. |
| 98 | • Multiple bugs that could cause the client tools to hang or crash were |
| 99 | fixed. |
| 100 | • nmcli allows multiple devices for 'nmcli device disconnect/delete'. |
| 101 | • Firewall zone is added to firewalld for device-based VPN connections |
| 102 | too. |