Changes

Jump to: navigation, search

Virtual-Lan

799 bytes added, 18:48, 30 September 2018
m
Updating to non-deprecated commands
== OS Installation ==
* Install 64-bit version of CentOS 6.4 7 with Virtualization Packages on the Host Computer (the physical unit)* Create Four Virtual Machines, each with 8GB 10GB of disk space, 1G Memory, 1CPU* Install CentOS6.4 CentOS 7 (excluding Virutualization Packages) on VM1 to VM3 with at least the following packages:
** NFS
** NIS
** DNS
** DHCP
** Postfix, sendmail
** OpenLDAP
** Wireshark** tcpdump* CentOS 6.4 7 configuration:
** Enable iptables
** Create a regular user account using your Seneca email ID
** Enable SELinux
** Name of the device used by each guest OS to connect to the virtual network
* Install Fedora 19 21 (without Virtualization packages) on VM4 with the following packages:
** NFS
** NIS
* Adding routes to each student's "opsnet" virtual network manually or by running the following bash script on the host OS:
#!/bin/bash
ip route add -net 192.168.1.0 netmask 255/24 via 172.25516.2551.1 ip route add 192.168.2.0 gw /24 via 172.16.2.1 ip route add 192.168.3.0/24 via 172.16.3.1 ip route add -net 192.168.24.0 netmask 255/24 via 172.16.4.1 ..255.255 ip route add 192.168.36.0 gw /24 via 172.16.236.1 or: #!/bin/bash count=1 x=1 # my network id while [ ${count} -le 32 ] do if [ ${count} != ${x} ] then ip route add -net 192.168.3${count}.0 netmask 255/24 via 172.25516.255${count}.0 gw 1 fi count=$(expr ${count} + 1) done * You also need to add routes on all you VMs to each student's "opsnet" and the logical network "172.16.30.0" that connects all the hosts. You can do it manually or by running the following script on each of your VMs: #!/bin/bash x=10 # my network id ip route add 192.168.1.0/24 via 192.168.${x}.1 ip route add -net 192.168.42.0 netmask 255/24 via 192.168.${x}.1 ip route add 192.255168.2553.0 gw 172/24 via 192.168.${x}.1 ip route add 192.16168.4.0/24 via 192.168.${x}.1
...
ip route add -net 192.168.36.0 netmask 255/24 via 192.255168.255${x}.0 gw 1 ip route add 172.16.36.0/16 via 192.168.${x}.1
or:
#!/bin/bash
count=1 x=110 # my network id while [ $x {count} -le 36 32 ]
do
if [ ${count} != ${x} ] then ip route add -net 192.168.${x}1.0 netmask 255/24 via 192.255.255.0 gw 172.16168.${x}.1 xfi count=$(expr $x {count} + 1)
done
ip route add 172.16..0/16 via 192.168.${x}.1
* To test your static routes, pair up with a few fellow students and try to ping their VMs in their "opsnet".
==Private Network Address Allocation==
* [[OPS535 Network Address| Network Address Allocation for 2014 Winter Semester]]
==CentOS Installation and update Issues==
# IP Addresses of your VMs
# IP Addresses of the other student's VMs
# IP address of the default gateway on your VMs, should be pointing to 192.168.x122.1# IP address of the default gateway on the other student's VMs, should be pointing to 192.168.y122.1
# The kernel routing table on your host. Should have a route to 192.168.y.0 network via 172.16.y.1
# The kernel routing table on the other student's host. Should have a route to 192.168.x.0 via 172.16.x.1
* If you can ping 172.16.x.1 but not 172.16.y.1, make sure that your host can ping the other student's host.
* If you can't ping 172.16.x.1, check your internet network setup.
* If you can ping 172.16.y.1, but not 192.168.y.1, ask/help the other stuent student to check his/her intenal network setupthe kernel routing table on its VM.
[[Category:OPS535]]
729
edits

Navigation menu