9
edits
Changes
→Investigation 2: What files does the system-config-network GUI tool change?.
# Record the answer to Investigation 2 in your logbook.
=== Investigation 23: What files does the <code>system-config-network</code> GUI tool change?. ===
{{Admon/note | Note! | Complete this investigation on your fedora1 VM.}}
# Start fedora1 VM and login
#Before we configure fedora1 we should create a timestamp file that can be used to see which files have changed as a result of using the GUI tool.#* <code>date > /tmp/timestamp</code># Run the network configuration tool and enter the following static configuration in the same way that you configured fedora2.#* IP Address: 192.168.235.11#* Subnetmask: 255.255.255.0#* Default Gateway: 192.168.235.1#* DNS Server: 192.168.235.1# Save and quit and restart NetworkManager# Verify the configuration by pinging fedora host (192.168.235.1) and fedora2 (192.168.235.12)# To verify that fedora1 has the correct default gateway configured, enter the command <code>route -n</code># Use the <code>find</code> command to locate the configuration files modified by the GUI network configuration program#* Previously, you created a file called <code>/tmp/timestamp</code>. Any files that were modified by the GUI network configuration program should have a timestamp later (or newer) than the "timestamp" file you created. All the Linux TCP/IP configuration files are stored under the "/etc" directory or its sub-directories. The following command when run as root will give you a list of all the files under the <code>/etc</code> directory with a file modification date newer than the date of the "timestamp" file:#**<code>find /etc -newer /tmp/timestamp</code>