Changes

= Configuring a Network Using Virtual Machines =

==Overview==

* In addition, you will learn to associate network services with port numbers, and learn how to backup files by date/time.

==Required Materials (Bring to All Labs)==

==Prerequisites==

== Lab Preparation ==

{{Admon/important | Live disc installations and system-config-network | The '''fedora1''' VM was installed from Live CD. It is missing the GUI Network Configuration tool we will be using. Use the command <code>yum install system-config-network</code> to install it.}}

{{Admon/important | Backup your VMs before proceeding | Stop all of your VMs and backup your VM disk images. Do not start the VMs until told to start them.}}

== Configuring a Network Using Virtual Machines ==

=== Investigation 1: How do you create a new virtual network. ===

Before configuring our network we want to turn off dynamic network configuration for our Virtual Machines by turning off the "default" virtual network.

# In the Virtual Machine Manager dialog box, Select '''Edit'''-> '''Connection Details'''.

# In the '''Hosts''' Details dialog box, select the '''Virtual Networks''' tab

'''Answer the Investigation 1 observations / questions in your lab log book.'''

=== Investigation 2: How do you configure a static network using <code>system-config-network</code>. ===

# To configure a new interface on fedora2 go to '''Applications'''->'''Other'''->'''Network Connections'''.

# Make certain there are no '''"Wired"''' connections (even if you have to click on the connection name and click the '''Delete''' button.

# Click on the '''Add''' button, and select the '''IPv4 Settings''' tab.

# Change the method from "Automatic (DHCP)" to '''"Manual"'''.

#: Subnet Mask '''255.255.255.0'''

#: Default Gateway '''192.168.235.1''' (The IP address of <code>virbr1</code> on your fedora host.)

# Click '''Save''' to Finish, and exit the Network Connections dialog box.

# Your network connection may connect (view the Network Manager applet in the gnome panel at the top of the screen). If there is no connection after a few minutes, you should be able to right-click on the applet and click "eth1" to connect.

# You should be able to use the systemctl command to restart your network.

#'''Restart your network''' on fedora2 by issuing the commands:

# Verify your new interface by examining the output of <code>ifconfig</code>

# To verify that fedora2 has the correct default gateway configured, enter the command: <code>route -n</code>

'''Answer the Investigation 2 observations / questions in your lab log book.'''

=== Investigation 3: What files does the <code>system-config-network</code> GUI tool change?. ===

<li>View the <code>/root/netcfg.lst</code> file. What does it contain?</li>

<li>Create a new directory called: <code>/tmp/lab6</code></li>

<ul>

<li><code>find /etc -newer /tmp/timestamp -exec cp {} /tmp/lab6 \;</code></li>

</ul>

'''Answer the Investigation 3 observations / questions in your lab log book.'''

=== Investigation 4: How do I configure the network without a GUI tool? ===

{{Admon/note | Use fedora3 | Complete this investigation on your fedora3 VM.}}

# Start '''fedora3''' VM and login as root

# To configure your card with a static address use the following command:

# To configure a default gateway for that interface enter the command:

#* <code>route add default gw 192.168.235.1</code>

#* Change to the <code>/etc/sysconfig/network-scripts</code> directory on <code>fedora3</code>

#* List the contents of the directory and you should see 2 different types of files, network config scripts and network configuration files.

#* Edit the new file for you interface and give it the following settings:

# Verify your configuration as you did before.

# Finally the kickstart file used to install this VM did not set the hostname. Edit the file <code>/etc/sysconfig/network</code> and set the hostname to <code>fedora3</code>

'''Answer the Investigation 4 observations / questions in your lab log book.'''

=== Investigation 5: How do I setup local hostname resolution? ===

::1 localhost6.localdomain6 localhost6 fedora1

192.168.235.11 fedora1

192.168.235.12 fedora2

{{Admon/note | Use All Machines | Complete this investigation on all of your VM's and the Fedora host.}}

=== Investigation 8: How do I view and configure the IPTABLES firewall? -- Basic Function/Configuration ===

{{Admon/note | | [http://en.wikipedia.org/wiki/Iptables Iptables] is the built-in firewall for LINUX. While this program can be controlled by different GUI's, we are going to investigate the powerful command line interface for this program to choose what data is allowed into, out of and through our computer.

'''FORWARD''' – LINUX PC's are often used as routers or gateways for other PC's. This means that data may have to be passed through this LINUX box, but the data is not intended for the LINUX PC nor is it being sent by the LINUX PC. Even though the data will go into this PC and it will exit this PC, the INPUT and OUTPUT chains do not apply here. Because the PC is acting as a router it does not actually send or receive data, it FORWARDS data from one machine to another. When this process happens, the data is checked against the FORWARD chain to see if it is allowed through. If it is the router will forward the data to it's destination. If not, the packet is dropped.}}

It should be noted that all of the commands that we do here with iptables will not be persistent unless you have your configuration. That means if you re-boot, the default iptables configuration will be loaded.}}

<li value="9">'''Make a backup of the file <code>/etc/sysconfig/iptables</code>'''</li>

<li>Examine the file to see how rules are added.</li>

<li>Verify that the file <code>/etc/sysconfig/iptables</code> was updated with your new rules.</li>

<li>Restart your iptables service and test your configuration. </li>

'''Answer the Investigation 8 observations / questions in your lab log book.'''

== New Configuration ==