wired ethernet disabled between reboots, was: when startup delays become bugs

Dan Williams dcbw at redhat.com
Tue May 21 19:09:17 UTC 2013

On Sun, 2013-05-19 at 09:59 -0400, Nico Kadel-Garcia wrote:
> On Fri, May 17, 2013 at 1:10 AM, Chris Murphy <lists at colorremedies.com> wrote:
> >
> > On May 16, 2013, at 10:49 PM, Dan Williams <dcbw at redhat.com> wrote:
> >
> >> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> >>> On May 16, 2013, at 3:36 PM, Chris Murphy <lists at colorremedies.com> wrote:
> >>>
> >>>> Rebooted. I still have the problem. Wired connection is Off on each reboot. This happens even if I regress to the 3.9.0 kernel that's used on the Live media, which works on every boot. Flummoxed.
> >>>
> >>> I found part of the problem:
> >>> [root at F19 network-scripts]# cat ifcfg-ens5
> >>> ….
> >>> ONBOOT=no
> >>>
> >>>
> >>> But why is it set to no? Once set to yes, system reboots with p5p1 enabled.
> >>
> >> Either it was set to "no" during installation, or something set it to
> >> "no" after the install.  NetworkManager won't ever change that value by
> >> itself.  Something else (like the GUI, or directly editing that file
> >> with VIM/emacs/etc) had to change it.
> >
> > It was set to no during installation, user unaware of this.
> >
> > The Gnome shell > Settings > Network > Wired > gear button > Identity > Connect automatically checkbox is what affects the ONBOOT= value. A similarly named checkbox is checked in anaconda on Fedora 18, but is unchecked if the cable is unplugged in anaconda on Fedora 19. So the resulting installation gets an ONBOOT=no and stays that way until the user finds, five layers deep, this weird Connect automatically checkbox.
> >
> > But this bug has brought me to a plethora of buggy behavior in the Gnome Settings Network panel, so maybe the misery was worth it.
> *THIS*. *This* kind of thing is why NetworkManager remains unusable
> for production network configuratoin. The very powerful and flexible
> shell scripting written into the /etc/sysconfig/network-scripts
> infrastructure is neither pro0perly displayed by nor manageable by the
> NetworkManager gui's. It is not even a good GUI becuase it violates
> over half of the open source GUI guidelines published by Eric Raymond
> in his essay on GU's, "The Luxury of Ignorance".

I'd be very interested to know how, exactly, the network-scripts are
"neither properly displayed nor manageable".  What options in the
scripts do you not find in the GUI?  And if so, please state *which*
GUI, whether that's GNOME control center, nm-connection-editor, or KDE's
network panel.  Also note the NetworkManager daemon and API usually
provides the full range of functionality, customization, knobs,
twiddles, properties, etc, and it's up to the GUIs to figure out what to
display.  There's also nmcli, which we're furiously working on to expose
everything admins may need without a GUI.


> One of my biggest steps to stabilize any server or production
> environments is the script that puts this in place
>            # For /etc/sysocnfig/network, and any
> /etc/sysoncig/network-scripts/ifcfg-[nic].cfg
>            NM_CONTROLLED=no
> At this point, even if NetworkManager manages to finally be upgraded
> to supported the most basic of options such as being turned off or on
> for speicific nodes, trunking, KVM bridging, or pair bonding, there is
> another five years of getting it written into the installers and
> deployment tools for Anaconda and tools like VMware-tools or
> libvirt-manager before it's generally useful.

More information about the devel mailing list