[opensuse-factory] networkd and wicketd
Hi, I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network. How is it related to wicketd? Will they both be able to work on the same PC not interfering each other? Or networkd to be disabled in opensuse? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all. Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 February 2014, Cristian Rodríguez wrote:
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all.
Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict.
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 26/02/14 13:26, Ruediger Meier escribió:
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet.
manages in the sense that starts the relevant services, this is a completely different thing. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 26 février 2014 à 17:26 +0100, Ruediger Meier a écrit :
On Wednesday 26 February 2014, Cristian Rodríguez wrote:
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all.
Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict.
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet.
No, it's not. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 February 2014, Frederic Crozat wrote:
Le mercredi 26 février 2014 à 17:26 +0100, Ruediger Meier a écrit :
On Wednesday 26 February 2014, Cristian Rodríguez wrote:
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all.
Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict.
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet.
No, it's not.
Just an example https://bugzilla.novell.com/show_bug.cgi?id=846361 cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 26/02/14 13:59, Ruediger Meier escribió:
No, it's not.
Still no cookie, there is no code in 13.1 systemd to manage network interfaces other than setting up "lo" once at early boot time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 26.02.2014 17:59, schrieb Ruediger Meier:
On Wednesday 26 February 2014, Frederic Crozat wrote:
Le mercredi 26 février 2014 à 17:26 +0100, Ruediger Meier a écrit :
On Wednesday 26 February 2014, Cristian Rodríguez wrote:
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all.
Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict.
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet.
No, it's not.
It were required to change sysconfig to use per interfce services to power up ifup because things working since ages got changed upstream [udev]. And this causes "corner-case issues" like the bellow one.
Just an example https://bugzilla.novell.com/show_bug.cgi?id=846361
Because your bug has priority 5 (none). But I've applied a fix just now: http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope... Gruesse / Regards, Marius Tomaschewski <mt@suse.de>, <mt@suse.com> -- SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg), GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 February 2014, Marius Tomaschewski wrote:
Am 26.02.2014 17:59, schrieb Ruediger Meier:
On Wednesday 26 February 2014, Frederic Crozat wrote:
Le mercredi 26 février 2014 à 17:26 +0100, Ruediger Meier a écrit :
On Wednesday 26 February 2014, Cristian Rodríguez wrote:
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd?
Currently, it is not related at all.
Will they both be able to work on the same
PC not interfering each other?
networkd manages nothing by default and as long wicked is not configured to manage the same interfaces there will be no conflict.
But systemd "manages" network devices already now since openSUSE 13.1, even if you are using traditional ifup setup. Because of this we got already several bugs, not all fixed yet.
No, it's not.
It were required to change sysconfig to use per interfce services to power up ifup because things working since ages got changed upstream [udev].
That's what I ment. Upstream does not care about existing scenarios. Guess that introducing networkd will not make the situatuion better for wicketd or any other network setup.
Just an example https://bugzilla.novell.com/show_bug.cgi?id=846361
Because your bug has priority 5 (none).
Hm, somebody changed priority. I had opened this bug as critical because IMO shutting down network is actually a critical thing.
But I've applied a fix just now:
http://download.opensuse.org/repositories/home:/mtomaschewski:/branch es:/openSUSE:/13.1:/Update/standard/
Thanks a lot. I'll try soon. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 26/02/14 15:13, Ruediger Meier escribió:
That's what I ment. Upstream does not care about existing scenarios.
Yes, they do.
Guess that introducing networkd will not make the situatuion better for wicketd or any other network setup.
Peaceful coexistence is expected with: - ConnMan: developers work in systemd-networkd as well. - NetworkManager -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 26/02/14 12:39, Matwey V. Kornilov escribió:
Hi,
I've read that systemd 210 is supplied with networkd for network configuration. There are .link unit files where one can configure his network.
How is it related to wicketd? Will they both be able to work on the same PC not interfering each other?
Now if you want to use networkd , a few hints. - Only DHCPv4, static v4/v6 addresses, are supported at the moment. - networkd does not (and will not) touch, create or do anything with /etc/resolv.conf, you must manually symlink /run/systemd/network/resolv.conf to /etc/resolv,conf. The long term goal is to make resolv.conf a sysadmin-only territory as a fallback configuration file, that no application modifies at all. AFAIK the relevant library,system or $whatever calls to implement this (a per-interface dns configuration) do not exist yet. - There is no command line client or api to configure it YET, so you need to manually edit the configuration files. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Frederic Crozat -
Marius Tomaschewski -
Matwey V. Kornilov -
Ruediger Meier