- 1 NetworkManager 1.8
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Upgrade/compatibility impact
- 1.8 How To Test
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 Contingency Plan
- 1.12 Documentation
- 1.13 Release Notes
Update to NetworkManager to version 1.8.
- Name: Lubomir Rintel
- Email: firstname.lastname@example.org
- Release notes owner:
NetworkManager 1.8 will include significant changes and improvements:
- MACsec support
- Proxy support including autoconfiguration
- Integration with systemd-resolved
- IPv6 connection sharing (prefix delegation to hotspots)
- Dropped hard dependency on dhclient, ppp
- VPN plugins no longer depend on GUI
Benefit to Fedora
A major feature release, brings new features often requested by users.
- Proposal owners: Update NetworkManager, connection editor and VPN plugin packages.
- Other developers: N/A (not needed for this Change)
- Release engineering: N/A (not needed for this Change)
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
We're not removing any functionality and keeping the ABI in place (though we add new libraries). The upgrades should be seamless.
How To Test
The usual test cases for NetworkManager will do. It would be great to test these areas:
- IPv6-enabled and legacy-free networks (no IPv4)
- Wireless access points with various security mechanisms (WPA, WEP, ...)
- Multiple links to the same network, wireless & wired
- Server setups, bonding, teaming, bridging, vlans (possibly stacked)
- Other tools that namange networking installed for testing interoperability: libvirt, Docker, VMWare, VirtualBox, systemd-networkd, ...
- A Mobile broadband connectivity dongle
- Bluetooth DUN & PAN enabled dongle or a phone
- VPN servers, concentrators
- Different desktop environemnts installed, to test integration: GNOME, KDE, Xfce, ...
The detailed tes plans:
The users may notice new features available: IPv6 connectivity with hotspots, smaller dependency chain in server environments.
These are packages directly affected by this change. They will be updated to new major versions:
It would be possible to revert the change by downgrading the affected packages (see "Dependencies" above). All packages would need to be downgraded. However, as the new version is compatible with the previous versions we don't anticipate the need to do this.
- Contingency mechanism: Revert the packages
- Contingency deadline: Beta freeze
- Blocks release? Yes
We'll write extensive release notes upstream.
We'll need to digest the upstream NEWS into the Fedora release notes.