Updated NetworkManager packages that fix three bugs and add an enhancement are now available for Red Hat Enterprise Linux 6.
NetworkManager is a system network service that manages network devices and connections, attempting to keep active network connectivity when available. It manages Ethernet, wireless, mobile broadband (WWAN), and PPPoE (Point-to-Point Protocol over Ethernet) devices, and provides VPN integration with a variety of different VPN services.
- Due to a bug reading and writing network configuration files, network connections using the LEAP authentication method could not be made available to all users. A patch has been provided to address this issue and the network configuration files now allow LEAP as expected.
- Previously, NetworkManager did not allow selecting the WPA protocol version for connection. Certain enterprise WLAN networks using Cisco equipment do not allow roaming between WPA and WPA2 Virtual Access Points (VAP) provided by the same physical access point, requiring the use of a specific WPA protocol version to prevent disconnections. This update adds a WPA protocol combo box to the NetworkManager user interface (UI), thus allowing a specific WPA protocol version to be used when necessary and preventing this bug.
- When a connection was locked to a specific WPA protocol version (either v1 or v2/RSN) via either the GConf system or settings in the /etc/sysconfig/network-scripts/ configuration files, the NetworkManager UI overwrote that preference when the connection was edited and saved. This bug has been fixed and such WPA preferences are now preserved in the described scenario.
- Support for Opportunistic Key Caching (OKC), also known as Proactive Key Caching (PKC), has been added to NetworkManager for all WPA-Enterprise configurations.
Users of NetworkManager are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.
An updated NetworkManager package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
NetworkManager is a system network service that manages network devices and connections, attempting to keep active network connectivity when available. It manages Ethernet, wireless, mobile broadband (
PPPoEdevices, and provides
VPNintegration with a variety of different VPN services.
- NetworkManager used a
DHCPtransaction timeout of 45 seconds without the possibility of configuring a different value. Consequently, in certain cases NetworkManager failed to obtain a network address. NetworkManager has been extended to read the timeout parameter from a DHCP configuration file and use that instead of the default value. As a result, NetworkManager will wait to obtain an address for the duration of the DHCP transaction period as specified in the DHCP client configuration file.
- If no Web browser was installed and the web site link was clicked in nm-applet's About dialog box, there was no response and NetworkManager did not display an error message. This has now been improved and the user is now presented with an error dialog box in the scenario described.
- NetworkManager did not update the timestamps for system connections. Consequently, the entry under the heading “Last Used” in the connection editor was always “never”, even if the connection had been used. An upstream patch has been applied and NetworkManager now updates connection timestamps for all connections.
- After system boot or when the user re-logged into the Gnome display manager, NetworkManager tried to initialize the user settings proxy even if it was not active. Consequently, this caused an unnecessary warning to be written to the
/var/log/messagesfile. An upstream patch has been applied to prevent NetworkManager from trying to initialize the user settings proxy if the user settings service does not exist. As a result, warning messages are no longer generated in the scenario described.
- NetworkManager inserted erroneous warning messages in the
/var/log/messageslog file when changing the hostname. An upstream patch has been applied to the nm-dispatcher script and NetworkManager no longer generates unnecessary warnings during a hostname change.
- When an existing DHCP lease was renewed, NetworkManager did not recognize it as a change in DHCP state and therefore failed to run the dispatcher scripts. Consequently, hostnames where purged from DHCP records. With this update the code has been improved and NetworkManager now handles same-state transitions correctly. As a result, hostnames are not purged from the DHCP server when a lease is renewed.
- There were errors in nm-applet's message catalog for some languages. Consequently, the Routes button name in the connection editor was not translated for those languages and appeared in English. The message catalog has been corrected and now the button text is translated correctly for all supported languages.
- NetworkManager did not support
WPA2 Enterprisewireless networks, which made it unusable in some wireless environments. NetworkManager has been enhanced to handle EAP-FAST authentication.
- NetworkManager did not handle RFC3442-standard classless static routes provided by a DHCP server without manual changes to the dhclient's configuration file. An enhancement has been made to ensure that RFC3442 classless static routes are requested from the DHCP server, and that they are properly processed by NetworkManager without any manual intervention.
- NetworkManager did not recognize
IP-over-InfiniBandinterfaces, which prevented installation in some situations. These interfaces are now recognized.
- BZ#712302, BZ#717475, BZ#804797
VLANand bonding interfaces were not supported by NetworkManager and required special configuration to ensure NetworkManager did not interfere with their operation. NetworkManager now recognizes and can configure VLAN and bonding interfaces but only if the
NM_BOND_VLAN_ENABLEDkey is set to
/etc/sysconfig/network. The default is that this option is set to
- If PolicyKit setup was used to disable creation of shared
Wi-Finetworks, and a user tried to create a network using nm-applet, the setup silently failed. With this update, nm-applet now issues a notification providing the reason for the failure.
- When no VPN plug-in for NetworkManager was installed and a user tried to configure a
VPNconnection, the connection editor displayed an insensitive Add button without giving any indication of the cause. This update adds a tooltip to the button informing the user that editing a VPN connection is disabled due to missing VPN plug-ins.
Users are advised to upgrade to these updated NetworkManager packages, which resolve these bugs and add these enhancements.