[wicked-devel] Multiple interfaces
Hi, I'm having an issue with wicked on openSUSE 13.1. I have two NICs, enp3s0 and enp4s0. The first one is connected to a switch which itself is connected to the cable modem. The second NIC is connected to my router which itself is also connected to the switch. When I start wicked with systemctl start wicked it , I suspect, starts the second NIC (enp4s0) first, then the first NIC (enp3s0) as last. This makes it that my internet connection goes through the second NIC somehow. I can check that easily by using some IP site which displays the address, and it reports the public address of the router so my internet really goes through the second NIC. I would like that wicked starts the enp3s0 first and then enp4s0 My current workaround is to stop everything, then start enp3s0 with wicked ifup enp3s0 and then the enp4s0 NIC. Then when I go to an IP site, it reports the correct address being used, which is that of my first enp3s0 NIC and not from the second/router one How to make it work without manually doing the above every time? Please CC me as I'm not subscribed -- Yours truly -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
On Wed, 24 Sep 2014 18:29:04 +0200 Grozdan <neutrino8@gmail.com> wrote:
Hi,
I'm having an issue with wicked on openSUSE 13.1. I have two NICs, enp3s0 and enp4s0. The first one is connected to a switch which itself is connected to the cable modem. The second NIC is connected to my router which itself is also connected to the switch. When I start wicked with systemctl start wicked it , I suspect, starts the second NIC (enp4s0) first, then the first NIC (enp3s0) as last. This makes it that my internet connection goes through the second NIC somehow. I can check that easily by using some IP site which displays the address, and it reports the public address of the router so my internet really goes through the second NIC. I would like that wicked starts the enp3s0 first and then enp4s0
My current workaround is to stop everything, then start enp3s0 with wicked ifup enp3s0 and then the enp4s0 NIC. Then when I go to an IP site, it reports the correct address being used, which is that of my first enp3s0 NIC and not from the second/router one
How to make it work without manually doing the above every time?
Please CC me as I'm not subscribed
Hi, First thing that comes to mind is: change the STARTMODE= param of enp4s0 to STARTMODE="manual" and after systemctl start wicked, run additional wicked ifup enp4s0. But I guess the problem here is with default route, isn't it? So add DHCLIENT_SET_DEFAULT_ROUTE="yes" to ifcfg-eno3s0 and DHCLIENT_SET_DEFAULT_ROUTE="no" to eno4s0. -- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, 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 -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
On Wed, Sep 24, 2014 at 10:54 PM, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de> wrote:
On Wed, 24 Sep 2014 18:29:04 +0200 Grozdan <neutrino8@gmail.com> wrote:
Hi,
I'm having an issue with wicked on openSUSE 13.1. I have two NICs, enp3s0 and enp4s0. The first one is connected to a switch which itself is connected to the cable modem. The second NIC is connected to my router which itself is also connected to the switch. When I start wicked with systemctl start wicked it , I suspect, starts the second NIC (enp4s0) first, then the first NIC (enp3s0) as last. This makes it that my internet connection goes through the second NIC somehow. I can check that easily by using some IP site which displays the address, and it reports the public address of the router so my internet really goes through the second NIC. I would like that wicked starts the enp3s0 first and then enp4s0
My current workaround is to stop everything, then start enp3s0 with wicked ifup enp3s0 and then the enp4s0 NIC. Then when I go to an IP site, it reports the correct address being used, which is that of my first enp3s0 NIC and not from the second/router one
How to make it work without manually doing the above every time?
Please CC me as I'm not subscribed
Hi,
First thing that comes to mind is: change the STARTMODE= param of enp4s0 to STARTMODE="manual" and after systemctl start wicked, run additional wicked ifup enp4s0.
But I guess the problem here is with default route, isn't it? So add DHCLIENT_SET_DEFAULT_ROUTE="yes" to ifcfg-eno3s0 and DHCLIENT_SET_DEFAULT_ROUTE="no" to eno4s0.
Thanks but I have two question. 1) Where do I place DHCLIENT_SET_DEFAULT_ROUTE? in the /etc/sysconfig/network/ifcfg-* files? 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 Thanks
-- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, 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
On Wed, 24 Sep 2014 23:04:12 +0200 Grozdan <neutrino8@gmail.com> 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.
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).
Thanks
HTH. -- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, 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 -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
On Wed, Sep 24, 2014 at 11:18 PM, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de> wrote:
On Wed, 24 Sep 2014 23:04:12 +0200 Grozdan <neutrino8@gmail.com> 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 <pwieczorkiewicz@suse.de>, 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
On Wed, 24 Sep 2014 23:25:18 +0200 Grozdan <neutrino8@gmail.com> wrote:
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
Really hard to tell without looking at complete log. Which version of wicked is it? Have you disabled NetworkManager? I suspect you have something like BOOTPROTO=dhcp in your ifcfg-* files, which is dhcp4+dhcp6, while your network does not provide dhcp6? -- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, 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 -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org
On Wed, Sep 24, 2014 at 11:36 PM, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de> wrote:
On Wed, 24 Sep 2014 23:25:18 +0200 Grozdan <neutrino8@gmail.com> wrote:
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
Really hard to tell without looking at complete log. Which version of wicked is it? Have you disabled NetworkManager?
yes, no NM here. Only wicked is running. Version is 0.6.10, latest packaged from network:/wicked repo for openSUSE 13.1
I suspect you have something like BOOTPROTO=dhcp in your ifcfg-* files, which is dhcp4+dhcp6, while your network does not provide dhcp6?
Correct, I have dhcp set and no IPv6 here yet.
-- Best Regards, Pawel Wieczorkiewicz <pwieczorkiewicz@suse.de>, 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
participants (2)
-
Grozdan -
Pawel Wieczorkiewicz