On Wed, Sep 24, 2014 at 11:18 PM, Pawel Wieczorkiewicz
On Wed, 24 Sep 2014 23:04:12 +0200 Grozdan
wrote: Thanks but I have two question.
1) Where do I place DHCLIENT_SET_DEFAULT_ROUTE? in the /etc/sysconfig/network/ifcfg-* files?
Yes, correct.
Done :)
2) Is there really no way to tell wicked in which order to start the NICs? I read somewhere (don't recall where) that this is possible, but it didn't give an example. I think (no sure) it was on the github README file
Wicked tries to start all interfaces it is told to in parallel (it's a feature ;-)) in order to get them up and running asap. Unless there are some dependency requirements to be fulfilled, but this is not the case here. So if some particular order is needed, it must be enforced manually (unless there is some ifcfg- option I am not aware of, but AFAIK there is not).
OK, understood :) A further small question is that I noticed after starting wicked that when I check the status with systemctl status wicked, it reports that the interfaces have timed out but a bit further it appears it starts them anyway. See output below Sep 24 18:13:06 neutrino wicked[13699]: device enp4s0 failed: operation timed out Sep 24 18:13:06 neutrino wicked[13699]: device enp3s0 failed: operation timed out Sep 24 18:13:06 neutrino wicked[13699]: lo up Sep 24 18:13:06 neutrino wicked[13699]: enp4s0 setup-in-progress Sep 24 18:13:06 neutrino wicked[13699]: enp3s0 setup-in-progress Sep 24 18:13:06 neutrino systemd[1]: Started wicked managed network interfaces. Should I be concerned about the timeout? I just ignore it at the moment as all appears to work
Thanks
HTH.
-- Best Regards, Pawel Wieczorkiewicz
, Linux System Developer SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstr. 5 / D-90409 Nürnberg / Phone: +49-911-740 53 - 613
-- Yours truly -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org