So now we have two virtual machines called Lennix, the attack machine or a client, and B box Linux
server, which will be the victim or server.
So naturally, we should get them to communicate with each other.
So that means that we need to put them on the same network, otherwise they're just separate dummy machines,
right?
Couldn't resist.
So.
Putting these machines in our local network directly, was that going to do expose our own network and
our host to adversaries?
This is a vital and very important security risk.
And it's going to cause some major headaches, so for this reason.
We can use the Internet working system of VMware workstation player, so this will do is it will help
us to eliminate risk, but we don't necessarily have to expose our own network and all the headaches
that that may cause sound good.
It does to me.
Now, let me briefly tell you about the VMware workstation player networking.
Now, because there are a few options that could make it confusing, I want to point out the three most
popular configurations, which are Bridgid Nat'l and host only network.
So the first one is a Bridgid network, the Bridgid architecture will let your virtual machine connect
directly to your network or what I mean is your land and then the VM will get an automatic IP address
from your home router.
Now, this option obviously does not eliminate the risk of exposure.
But it opens the pvm to the land, so I don't recommend this configuration in a production or a business
environment, especially when you're busy with many vulnerable machines.
So the second one is not in this architecture can actually solve our problem because it creates a virtual
network and then it assigns an IP address to your VM.
So if you make this like we're going to do on our demo, your VM can only communicate with your host
and the machines in this network.
The third option, in case you're curious, host only network provides more isolation with the host
only network, you can completely isolate your VM from land as well as when.
This architecture is very useful when you need sandboxing.
For example, when you analyze malware, you really only want to use the host only network and you can
also observe if the malware tries to communicate to a remote control server.
So in our lab, what we're going to do is use the net network and I'll just quickly show you how it's
done.
Start your workstation player.
And your virtual machines are going to be listed on this left pane.
I'm going to first start calling, so choose Kelly Lennox by clicking on it, and a new view will be
opened in the right pane.
So from that view, by clicking in here, the settings window will open.
Now, you can change many configuration settings from this window.
We're only going to change the network adapter settings.
So when you click on Network Adapter, right, pain, you're going to see the network option that we
mentioned a little while ago, right?
And I'm going to check Nat and click, OK?
And then I will quickly do the same thing for our vulnerable virtual machine box.
OK, so now both machines are in the network and let's check to see if they're connected.
So let's start up Kelly Linux by double clicking.
And click on Shortcode again to open the workstation main window and we'll start at beatboxes as well.
And I'm going to log in to Kalli.
Now, let's open up the terminal and check the I.P. address by typing the IP config command.
And we get that the IP address is one nine two one six eight two two seven eight one two eight.
So I'm going to do the same thing for Beatbox as well.
I config.
And there's the IP address of Beatbox, 192000 one six eight two two seven dot one three zero.
OK, so now it's Taiping, one nine two, about one six eight 227000 one two eight.
And B box can reach Kaui.
So it's a return to Cali and Ping, the IP address of Xbox.
And perfect buybacks will also allow the connection.
So that means our attacking machine and vulnerable machine will be able to communicate with each other.
In fact, they're doing it right now.
Oh, and one more thing to say is, after recording this video, I needed to change something with my
system.
So the IP address of the machines are also changed for me, so for Linux, I will be using one nine
two two one six eight to zero for about one to eight.
And for beatboxer, I will be using one nine to about one six eight two zero four eight one three zero.
OK, so congratulations, your virtual machines are now ready to run and communicate, they are operational,
so now we include all machines into the same network.
Now they can communicate.
So there's one last task to do when you work in a lab, you can pretty much mess everything up pretty
easily.
You can change the configuration of server, upload malicious files, delete or change data and more
so after a while.
You are going to have so much in here that you could very easily lose your way.
So at that point, don't despair, just return to the first clean installation of the virtual machine.
So unfortunately, VMware workstation player does not support snapshots, if you have VMware workstation
pro, you can certainly use that feature.
So what you need to do then is copy the clean installation of the virtual machines, that's all.
If you're going to need clean ones later, you can always import them again.
And VMware player is always options.
And of course, you could always choose to run the whole lab on virtual box.
That way you'll have these kinds of features for free.
Always good to have options.