Red Hat Bugzilla – Bug 84106
"/etc/init.d/network start" starts cipe interfaces regardless of ONBOOT setting
Last modified: 2014-03-16 22:34:22 EDT
Description of problem:
When booting, my cipcb0 is always started regardless of the ONBOOT setting.
Obviously I only want the CIPE link to be up when needed ;-).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot system with CIPE interface configured
run "ifconfig" to see cipcb0 interface up and running though ONBOOT="no"
cipcb0 is down after boot when ONBOOT="no"
Apparently, /etc/sysconfig/network-scripts/network-functions has the function
is_available() which checks for availability of an interface, loads the modules
in correct order, etc. This function also loads CIPE modules which apparently
bring up the interface.
Created attachment 90024 [details]
Patch to /etc/network-scripts/network-functions for CIPE to work properly with ONBOOT="no"
This patch doesn't run "modprobe cipcb" when checking a cipe interface. This
probably should be extended to other virtual interface types that don't
correspond to real hardware (where module loading order has an impact).
I don't see this on my laptop. What does your
/etc/sysconfig/network-scripts/ifcfg-cipcb0 look like?
Created attachment 90040 [details]
I upgraded yesterday evening and now it all works again (with the original
script). Maybe it was a not so ideal combination of package versions before.