[opensuse-factory] NetworkManager-1.0 soon to be ready for testing
So some exciting news, for those of you that use NetworkManager. NetworkManager 1.0 is now in GNOME:Factory, and ready for everybody to test and break repeatedly, so we can get it ready to push to Tumbleweed. This will also bring 1.0 versions of the following packages: NetworkManager-gnome -openconnect -openswan -openvpn -pptp -vpn And I'm sure, shortly thereafter, updates from the KDE team, once it hits Tumbleweed. Some of the new Features/Bugs/Changes include: + A new 'libnm' GObject-based client library to replace libnm-util/libnm-glib: - IP address, IP route, hardware address, and other properties are now represented as strings. - Based on GIO's GDBus bindings instead of dbus-glib. - Uses modern GObject APIs including GAsyncResult and GVariant. - See https://wiki.gnome.org/Projects/NetworkManager/libnm. + Devices and VPN connections now have individual default routes. Priorities are handled through configurable route metrics. + nmcli now supports password requests and PolicyKit authorizations. + A faster, lighter-weight (though less capable) internal DHCP client has been added and may be selected with the "dhcp=internal" option. It supports fewer DHCP options and does not yet support DHCPv6. + A new 'configure-and-quit=yes' option has been added for environments with less dynamic network configuration. + When running on 3.17 and later kernels, NetworkManager handles IPv6LL address assignment to ensure that IPv6 connectivity is not enabled until intentionally configured by the user. + NetworkManager no longer causes the nl80211 kernel module to be loaded on systems with no Wi-Fi devices. + Bluetooth DUN support now works with Bluez 5.x. + VPN connections can now persist across link changes and suspend/resume if their VPN plugin supports this feature. + A new 'ibft' settings plugin has been added to support firmware-based iBFT/iSCSI configurations. This functionality has been moved to 'ibft' from the 'ifcfg-rh' plugin. + IPv6 router advertisement MTUs are now respected. + NetworkManager no longer requires polkit libraries at runtime when Polkit support is enabled, and Polkit can be disabled at build time too. + Automatically created connections are now deleted when their device goes away. + 'nmcli dev connect' now attemts to create a connection if none exists. + Manually configured static IPv6 configuration is kept even if SLAAC fails. + Manpages for the 'keyfile' and 'ifcfg-rh' plugins now describe their configuration syntax and available options. + WWAN connections now support IPv6 if the modem and provider support IPv6. + Software devices (bridge, bond, team, etc) can now be deleted from the D-Bus API or with nmcli. + The manpages, documentation, and API annotations have received many cleanups. + Externally created virtual interfaces are no longer managed by NetworkManager until they are set "up" or activated via nmcli. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2015-01-27 18:50, Shawn W Dunn wrote:
Some of the new Features/Bugs/Changes [of Networkmanager] include:
+ A faster, lighter-weight (though less capable) internal DHCP client has been added
I find it strange that everybody is suddenly writing their own DHCP clients. First networkd, now networkmanager. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-01-27 at 19:16 +0100, Jan Engelhardt wrote:
On Tuesday 2015-01-27 18:50, Shawn W Dunn wrote:
Some of the new Features/Bugs/Changes [of Networkmanager] include:
+ A faster, lighter-weight (though less capable) internal DHCP client has been added
I find it strange that everybody is suddenly writing their own DHCP clients. First networkd, now networkmanager.
Indeed.. but that doesn't mean we'll have to use it...
--
Dimstar / Dominique Leuenberger
El 27/01/15 a las 15:16, Jan Engelhardt escribió:
On Tuesday 2015-01-27 18:50, Shawn W Dunn wrote:
Some of the new Features/Bugs/Changes [of Networkmanager] include:
+ A faster, lighter-weight (though less capable) internal DHCP client has been added
I find it strange that everybody is suddenly writing their own DHCP clients. First networkd, now networkmanager.
code is shared between those two .. since libsystemd-network is not yet exported by systemd it carries a copy .. at some point networkmanager will.. just like ConMan ..become a consumer of networkd or the systemd network libraries. Unfortunately instead of working together with everybody else in the industry SUSE decided to implement wicked..well.. as it cannot match the manpower available (Intel, Samsung, redhat, CoreOS..etc..are all working on networkd) it will become just another thing nobody else uses. people never learn.. Cheers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Jan 27, Cristian Rodríguez wrote:
Unfortunately instead of working together with everybody else in the industry SUSE decided to implement wicked..well.. as it cannot match the manpower available (Intel, Samsung, redhat, CoreOS..etc..are all working on networkd) it will become just another thing nobody else uses. people never learn..
Come on, thats nonsense If we would go that route most people would be … offline. Its like forcing everyone to McDonalds: same old, same boring, same wrong. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 27 janvier 2015 à 15:49 -0300, Cristian Rodríguez a écrit :
Unfortunately instead of working together with everybody else in the industry SUSE decided to implement wicked..well.. as it cannot match the manpower available (Intel, Samsung, redhat, CoreOS..etc..are all working on networkd) it will become just another thing nobody else uses. people never learn..
Don't try to rewrite history, wicked was started and announced way before networkd first lines of code were written.. There were talks between NM and wicked people (again, before networkd was written) which didn't went anywhere, unfortunately.. -- Frederic Crozat Project Manager Enterprise Desktop SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2015-01-28 10:07, Frederic Crozat wrote:
There were talks between NM and wicked people (again, before networkd was written) which didn't went anywhere, unfortunately.. wicked was started and announced way before networkd first lines of code were written..
Good for wicked, but from the point of view of the openSUSE distribution, switching to wicked has been somewhat of a redundant exercise, especially because it was clear at openSUSE 13.2 release time that systemd would grow a network configuration thing. In other words, wicked, to me, is another short-lived mayfly like zmd. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 27 Jan 2015 18:50, Shawn W Dunn wrote:
So some exciting news, for those of you that use NetworkManager.
NetworkManager 1.0 is now in GNOME:Factory, and ready for everybody to test and break repeatedly, so we can get it ready to push to Tumbleweed.
This will also bring 1.0 versions of the following packages: NetworkManager-gnome -openconnect -openswan -openvpn -pptp -vpn
And I'm sure, shortly thereafter, updates from the KDE team, once it hits Tumbleweed.
What I could not find out about: is nmcli now a first class client, or is it still behind the GUI clients in functionality? IMHO, NetworkManager.spec should get a small change in the Summary line, an added "... for Desktops" Now: Summary: Network Link Manager and User Applications Should: Summary: Network Link Manager and User Applications for Desktops - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2015-01-27 at 19:20 +0100, Yamaban wrote:
Now: Summary: Network Link Manager and User Applications Should: Summary: Network Link Manager and User Applications for Desktops
Sounds inaccurate... especially as our default installer will chose to
install wicked on a traditional desktop system (arguably the right
thing).
YaST choses NM only as default on Notebooks
Cheers,
--
Dimstar / Dominique Leuenberger
On Tue, 27 Jan 2015 19:29, Dimstar / Dominique Leuenberger
On Tue, 2015-01-27 at 19:20 +0100, Yamaban wrote:
Now: Summary: Network Link Manager and User Applications Should: Summary: Network Link Manager and User Applications for Desktops
Sounds inaccurate... especially as our default installer will chose to install wicked on a traditional desktop system (arguably the right thing).
YaST choses NM only as default on Notebooks
Yeah, that may be, bust it still sounds better than: "... do not use for servers, unless you like frustration." or: "... for simple network access only, no routing/bridge" Would: "... for mobile needs" sound better? Still, NetworkManager is now (OSS13.2) much more useable than what was delivered with OSS 12.3, that one was hair-rising. Some of the patches will have to be reviewed, if they are still needed, and the combo with ModemManager will have to be tested heavilly in R.L. But over all, wicked makes more trouble atm, than NM does. (The wicked situation is {mostly} caused by 'new product', no reliable info/example for my use case, google does not give a useable answer) - Yamaban -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 27 Jan 2015 19:51:52 +0100 (CET)
Yamaban
On Tue, 27 Jan 2015 19:29, Dimstar / Dominique Leuenberger
wrote: On Tue, 2015-01-27 at 19:20 +0100, Yamaban wrote:
Now: Summary: Network Link Manager and User Applications Should: Summary: Network Link Manager and User Applications for Desktops
Sounds inaccurate... especially as our default installer will chose to install wicked on a traditional desktop system (arguably the right thing).
YaST choses NM only as default on Notebooks
Yeah, that may be, bust it still sounds better than: "... do not use for servers, unless you like frustration." or: "... for simple network access only, no routing/bridge"
NM supports bridge since 0.9.8. Not sure what you mean about "routing" here, but NM had custom routing entries for quite some time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrei Borzenkov
-
Cristian Rodríguez
-
Dimstar / Dominique Leuenberger
-
Frederic Crozat
-
Jan Engelhardt
-
Olaf Hering
-
Shawn W Dunn
-
Yamaban