Design Questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

Regards,
-Dan

--
Daniel F. de Araujo
IBM Linux Technology Center


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux