Beware The Dangling ifcfg-* Files of Doom

Different network configuration tools, such as the old "netconfig"
tool, had bad habits of leaving various backed up or reference
templates for ifcfg-eth* files scattered throughout /etc/sysconfig.
They were nasty and confusing and tended to get reloaded, accidentally
based on phase of the moon and whether the chimps trying to code
NetworkManager had actually succeeded in writing Hamlet instead, and
gone off to get a banana.

The "system-config-network" tool is not horrible, but leaves out a lot
of available options that need manual editing for more thorough
configuration. If you have to manually edit network settings for
stable servers, rip NetworkManager *out* with the a prybar, if
necessary, and keep any running NetworkManager daemons from touching
your system.

Historically, the /etc/sysconfig/network script is 'sourced' by the
various /etc/sysconfig/network-scripts/{if*} binary scripts, so it
should normally load from there if available. But coding standards can
change. Associating a gateway with a particular network port actually
has its uses if you have two ports on the same VLAN, and one port
*not* to carry outgoing traffic.


On Fri, Feb 14, 2014 at 7:02 PM, Tom H <[log in to unmask]> wrote:
> On Fri, Feb 14, 2014 at 6:25 PM, ToddAndMargo <[log in to unmask]> wrote:
>> On 02/14/2014 03:20 PM, Tom H wrote:
>>>
>>> Setting NETWORK in either "/etc/sysconfig/network" or
>>> "/etc/sysconfig/network-scripts/ifcfg-* works for me.
>>>
>>> "/etc/sysconfig/network" is sourced in
>>> "/etc/sysconfig/network-scripts/ifup-eth".
>>
>> do an "ifdown ethx"; switch your gateway over
>> to "network"; do an "ifup ethx".  Then
>> look at "netstat -rn"
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1038344
>
> Works for me.