Configuring RedHat WS 4 Virtual Operating SystemsPart 2: The RouterSetting up the RouterSome examples of manually modifying routesManually Controlling Your Network InterfacesPart 3: Traffic MonitoringInstallation of Traffic Generators and ServersExecuting the TrafficUDP vs. One TCP GeneratorUDP vs. Two TCP GeneratorsPart 4: printkThe objective of this part of the lab is to learn how to modify the Linux kernel to initially learn how to recompile the Linux Kernel source code. You will print some messages from the Linux Kernel and learn how to compile the kernel.Modifying the Kernel CodeCompiling the KernelPart 5: Changing the kernel schedulingECE 4110 Lab 9:Configuring a Linux Machine as a Router and Modifying the Operating SystemDate Issued: November 6, 2008Checkoff Due Date: November 24, 2008Report Due Date: November 26, 2008Please note this is a much longer lab than the others so please plan ahead and do not wait until the last minute to try to complete this lab. It can be done in pieces. You will not be able to complete this lab in one lab visit. Plan ahead and start early.This lab requires two computers. There are 3 lab setups (more, if needed) and no reservations are required. Place your hard drive in a computer labeled “ECE4110 Lab 9 SOURCE.” The computer on your right should be labeled “ECE4110 Lab 9 DESTINATION a” where a is a number between 201 and 203. IP routing is the process that a machine containing multiple network interfaces uses to decide where datagrams that it receives should to be delivered. We will construct a router that connects three networks. The following diagram shows the networks and their respective IP addresses. 1network57.35.7.0/2457.35.7.b (eth1)ROUTER MACHINE(your linux source machine) 57.35.c.1 57.35.d.1 (vmnet1) (vmnet2)destination57.35.7.a(eth1) network57.35.d.0/24network57.35.c.0/24virtual257.35.d.2virtual157.35.c.2Part 1: A Virtual NetworkFor lab 9 use the following numbering conventions:Variable Valuea The number designated by your destinationb The last number of your RedHat WS 4 IP addressc Your group number plus 100d Your group number plus 200The following steps will guide you in constructing the small network shown above. Rather than using three physical subnets, we will be using one physical subnet and two virtual subnets using the tool VMware. Before you start this lab, you need to configure a new Network Interface Card (NIC). The Dell PC is using a Broadcom NIC (eth0), which we will not use in this lab. Instead we will use an Intel EtherExpress Pro100B NIC (run by eepro100 driver). The TAs have placed this new NIC inside each source and destination machine. There is no need for you to configure the destination machine. However, you will have to configure the source machine, which is the machine you will place your HD inside of. After you power on the source machine, Linux should automatically detect the Intel NIC. During “Checking for the new hardware”, Kudzu (with a blue background) will ask what you would like to do about the new NIC. Choose “Configure” then select “Back” without filling in any network setup information. After the computer boots up, you will need to configure the new NIC. Login as the root. Click the RedHat icon, choose “System Settings” then choose “Network”. Right now, you should see eth0 is active. Click “Hardware”, if eth1 does not exist, then click “Add”. Choose “Ethernet” as hardware type. Click OK. Choose EtherExpress Pro 100B as the adapter and “eth1” as the adapter, then click OK.Click “Devices” then click “New”. Choose “Ethernet connection” as the “Device Type”. Click Forward. Select Ethernet Pro 100 (eth1), click Forward. Check “Statically set IP addresses”. Use 57.35.7.b (“b” is from the table above) as the IP address, and 255.255.255.0 as the subnet mask. Click Forward and click Apply. Finally, click Apply again. Now close the Network configuration window and save the settings.Now, open /etc/modprobe.conf, add the follow line (right below “alias eth1 eepro100”) options eepro100 options=0x50(You have to change the line “alias eth1 ee100” to “alias eth1 eepro100” if it is not already done.) This is done to configure the network card into 10Mbs mode. We want to 2limit the bandwidth to only 10 mbits/sec for this lab. This will be a bandwidth bottleneck in your experiments.Now, reboot your source machine.You have already installed VMware on your RedHat WS Host in a previous lab and should have installed two RedHat WS 4 virtual machines as well. If not see the appendixof Lab 4 to see how to do this.We are using VMware software and only two machines instead of no VMware and four machines. This is just so that we use as few real machines as possible in the lab leaving resources for other classes.We need to change the configuration of these two virtual machines for this lab:From your WS4 Host machine, Run the vmware-config.pl$ /usr/bin/vmware-config.plUse the following answers:Accept the default directories for the first two questions.Accept the default “yes” for the question about building a vmon module for your system.Again accept the default directory for the location of the C header files.“Would you like to skip networking setup and keep you old settings as they are?”. NoDo you want networking for your virtual machines? YesWould you prefer to modify your existing network configuration using the wizard or the editor? EditorDo you wish to make any changes to the current virtual networks settings? YesWhich Virtual network do you wish to configure? (0-99)1The network vmnet1 has been reserved for a host-only network. You may changeit, but it is highly recommended that you use it as a host-only network. Areyou sure you want to modify it? (yes/no) [no] YesWhat type of virtual network do you wish to set vmnet1?(bridged,hostonly,nat,none) [none] HostonlyConfiguring a host-only network for vmnet1.Do you want this program to probe for an unused private subnet? (yes/no/help) [yes] NoWhat will be the IP address of your host on the private network? 57.35.c.1 (c is from table on page 2)What will be the netmask of your private network? 255.255.255.0The following virtual networks have been defined:. vmnet0 is bridged to eth0. vmnet1 is a host-only network on private subnet 57.35.c.0.Do you wish to make additional changes to the current virtual networks settings