Daniel F de Araujo wrote:
Hello list,
I have a couple of questions regarding the design of the network
gui/text screen. Before I ask, it maybe helpful to explain my setup and
situation:
I have a network adapter with two ports. The first port (eth0, static
IP) is connected to the public network and the other port (eth1, dhcp)
is connected to my private network (same subnet as the NFS installation
and DHCP servers). After I grab a dynamic IP for eth1 and setup the
partitions, I end up in the network gui. Here, I enter the static IP
address of eth0. I cannot, however, edit the gateway or DNS settings
(which are different than eth1) for this port (eth0). So:
1) Is Anaconda designed to simply configure the adapter/port that
accesses the install data? I assume the responsibility would then fall
on the user to configure the other adapters during the firstboot process
or setup agent screen.
2) If #1 is true, then I am curious as to why Anaconda allows the user
to configure the IP, but the not the gateway/DNS information, for other
adapters since it relies on firstboot, etc.
Thanks in advance for the help/explanations.
Anaconda collects enough information to write out files in
/etc/sysconfig/network-scripts. We write out ifcfg-ethX files. The
gateway and DNS settings are not stored per-interface. The gateway is
written to /etc/sysconfig/network since you can only have one default
gateway. DNS settings are written to /etc/resolv.conf and are also
system-wide rather than per interface.
Anaconda will allow you to configure each network interface in the
system. You can set it up for manual or dynamic configuration and flag
it as ONBOOT or not.
--
David Cantrell
Red Hat / Westford, MA
