Alex Clemente <alexbm...@gmail.com> wrote: > This discution is not remove nmcli*, is default, but keep ifup and ifdown. > NetworkManger is easy.
This will be my last post, and I'll use an analogy to hopefully assist with understanding the history. For our analogy, let's replace ... - nmcli -> firewalld - if* scripts -> iptables-services scripts - ip -> iptables The "iptables" command is what both newer "firewalld" and legacy "iptables-services" scripts utilize. To maximize the "Greatest Common Denominator," there are objectives to teach "iptables" instead of, say, distro-specific "iptables services" commands and related setup. But if we teach "iptables-services" commands and related setup, they might conflict with other services, like "firewalld", while the "iptables" command does not. Hence why the focus is on "iptables" ... _especially_ for troublehshooting. ;) Same concept ... The "ip" command is what both newer NetworkManager (nmcli -- NetworkManager Command Line Interface) and legacy scripts, originally based on "net-tools" (and some updated to use "iproute2", while others may not) like "ifup/ifdown" use. To maximize the "Greatest Common Denominator," there are objectives to teach "ip" instead of, say, distro-specific "ifup/ifdown" and other "interface" or "network-scripts" commands and related setup. But if we teach "ifup/ifdown" and other "interface" or "network-scripts" commands and related setup, they might conflict with other services, like "firewalld" (let alone libvirtd and other services, that might tap other things), while the "ip" command. Hence why the focus is on "ip" ... _especially_ for troublehshooting. ;) Again, my last post on the matter. Just trying to point out these technical details and Upstream/distro-commonality. - bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith E-mail: b.j.smith at ieee.org or me at bjsmith.me _______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
