<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/13/2014 01:50 PM, RDH wrote:<br>
<blockquote cite="mid:21204.13695.260217.976747@UrK8.us.oracle.com"
type="cite">
<pre wrap="">Stephen John Smoogen writes:
</pre>
<blockquote type="cite">
<pre wrap="">On 13 January 2014 08:45, Brian Wheeler <a class="moz-txt-link-rfc2396E" href="mailto:bdwheele@indiana.edu"><bdwheele@indiana.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Is it just me or is basically impossible to manage networks using nmcli?
I've not been able to find any documentation that helps.
Here's what I've got -- My site is pretty traditional: static IPs,
default gateways, and alias addresses. On RHEL6 I'd just use the
ifcfg-eth0 and ifcfg-eth0:0 style of managing it, but in RHEL 7 that
doesn't seem to work and I keep getting duplicate interfaces that are
configured but not active, the route disappears on reboot, and I can't add
and remove aliases as needed without bringing down the entire interface.
Does anyone know of a good resource for dealing with NetworkManager for
this style of configuration? The RHEL 7 Networking guide isn't terribly
helpful because it seems like >90% is wifi, teaming, vpn, bridging, and
how to use the gui -- none of which are applicable to my use case (but I do
recognize their importance)
Between nmcli and firewall-cmd it is almost like I've been sucked back in
time to the days when I was an AIX admin where you had to use the tools to
maintain active/configured settings and you couldn't just edit the config
files.
</pre>
</blockquote>
<pre wrap="">Do not worry. It hates everyone with the malevolence of a million demons
being made to tell the truth.
So what are you needing on this? 2 Ip addresses off of one physical
adapter? Could you send what you have tried or used in the past so I can
see what might be needed to be different?
</pre>
</blockquote>
<pre wrap="">
What I have done/to do in Fedora is basically kill NetworkMangler
and fall back on the old network service (I think I've remembered
the right command spelling):
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
systemctl enable network.service # probably already enabled
systemctl start network.service # probably already started
and edit all the old standby config files
/etc/sysconfig/network # default route
/etc/hostname # from /etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcfg-*
/etc/resolv.conf
(and maybe /etc/nsswitch.conf, depending on your site)
This is PURE STATIC config, **NO** DHCP on any network port. (DHCP
also likes to dynamically mangle config files)
You've done all this? I haven't played much with RHEL7 yet, I'm
still trying to figure out how to specify focus follows mouse in
that damnable GNOMEish abortion. I wonder if I can download a
MATE from Fedora???
-RDH
</pre>
</blockquote>
I've been trying to do it the "right" way so that when the old way
disappears I won't be completely lost. As it stands now, I'm
having a ton of trouble remembering the all of the specialty
commands to manage things which used to be handled by configuration
files and/or filesystem links (I'm looking at YOU, systemd,
firewalld, and NetworkManager!) <br>
<br>
</body>
</html>