<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
Thanks Andrew!<BR>
<BR>
Thankfully I have no small amount of h/w to do this with and can build VM's and bare-metal systems as will. Have plenty of routers so will reference your notes as I build....<BR>
<BR>
Brought my dual-Xeon server to work today to work on...if I get a chance that is! Keeping very busy today....<BR>
<BR>
RinL<BR>
<BR>
<BR>
On Thu, 2012-04-12 at 10:17 -0400, Andrew Wade wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
Rich,<BR>
<BR>
One of the key elements for studying for and passing the RHCE is having a good<BR>
test enviornment. I reccomend the following:<BR>
<BR>
You can do this with any virtualization technology (KVM, Xen, etc.), but I used<BR>
VMWare Workstation<BR>
<BR>
1) Set up VMWare Workstation and install three guests (centos 6.x)<BR>
<BR>
2) Set up snapshot of the fresh install<BR>
<BR>
3) Set the VMs to be bridged off your current adapter (so they can get the same<BR>
IP segement and interact with each other)<BR>
<BR>
4) Setup a Centos Server 6.x running in run level 5 to access your other guest<BR>
VMs (mimic your rhce test enviornment)<BR>
<BR>
5) SSH into the Guest VMs as if it was a real scenario (no XWindows)<BR>
<BR>
Go through the exercises/labs and feel free to screw up since you can simply<BR>
restore from the last snapshot. When it comes to the<BR>
tcp wrappers and iptables stuff, you'll want to get creative and setup another<BR>
routable subnet at home to attach some of your VMs to. <BR>
The easiest way for most people to do this is get a second wifi router and plug<BR>
it into your primary wifi router. Set it up<BR>
to be a NAT device that re-broadcasts a new subnet. Then in VMWare attach your<BR>
USB wifi to your guest VM and setup network on its<BR>
wlan0. That way one guest VM will be in another subnet, but still be able to<BR>
route its way to communicate with the other VMs on<BR>
the origianl subnet.<BR>
<BR>
<BR>
At this point you can sucessfully test tcp wrappers ie /etc/hosts.deny sshd :<BR>
192.168.1. : deny (I think they syntax is right, I'd have to double check).<BR>
<BR>
<BR>
This kind of setup will allow you to do most of the stuff needed (except for replicating a NIS enviornment, but that's for another post!),
</BLOCKQUOTE>
</BODY>
</HTML>