p59342861
/
monkey
forked from p15670423/monkey
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update vmware.md

This commit is contained in:
MarketingYeti 2021-01-22 11:15:58 -05:00 committed by GitHub
parent c1118a54c0
commit 4737dc9b76
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/content/setup/vmware.md
View File

@ -9,22 +9,19 @@ tags: ["setup", "vmware"]
## Deployment ## Deployment
1. Deploy the Infection Monkey OVA by choosing Deploy OVF Template and follow the wizard instructions. *Note: make sure port 5000 and 5001 on the machine are accessible for inbound TCP traffic.* 1. Deploy the Infection Monkey OVA by choosing **Deploy OVF Template** and following the wizard instructions. *Note: make sure ports 5000 and 5001 on the machine are accessible for inbound TCP traffic.*
2. Turn on the Infection Monkey VM. 2. Turn on the Infection Monkey VM.
3. Log in to the machine with the following credentials: 3. Log in to the machine with the following credentials:
1. Username: **monkeyuser** 1. Username: **monkeyuser**
2. Password: **Noon.Earth.Always** 2. Password: **Noon.Earth.Always**
4. It's recommended to change the machine passwords by running the following commands: `sudo passwd monkeyuser`, `sudo passwd root`. 4. It's recommended you change the machine passwords by running the following commands: `sudo passwd monkeyuser`, `sudo passwd root`.
## OVA network modes ## OVA network modes
The OVA can be used in one of two modes: You can use the OVA in one of two modes:
1. In a network with DHCP configured. In this case, the Monkey Island will automatically query and receive an IP address from the network. 1. In a network with the DHCP configured— In this case, the Monkey Island will automatically query and receive an IP address from the network.
1. With a static IP address. 2. With a static IP address — For this case, you should login to the VM console with the username `root` and the password `G3aJ9szrvkxTmfAG`. After logging in, edit the interfaces file by writing the following command in the prompt:
In this case, you should login to the VM console with
username `root` and password `G3aJ9szrvkxTmfAG`. After logging in, edit the interfaces file. You can do that by writing the following command in the prompt:
```sh ```sh
sudo nano /etc/network/interfaces sudo nano /etc/network/interfaces
@ -47,7 +44,7 @@ username `root` and password `G3aJ9szrvkxTmfAG`. After logging in, edit the inte
gateway YYY.YYY.YYY.YYY gateway YYY.YYY.YYY.YYY
``` ```
Save the changes then run the command Save the changes then run the command:
```sh ```sh
sudo ifdown ens160 && ifup ens160 sudo ifdown ens160 && ifup ens160
@ -55,8 +52,6 @@ username `root` and password `G3aJ9szrvkxTmfAG`. After logging in, edit the inte
## Upgrading ## Upgrading
There's no "upgrade-in-place" option for Docker. To get the new version, download it, stop the current container, and run the installation commands again with the new file. There's no "upgrade-in-place" option for VMware. To get the new version, download the updated file. If you'd like to keep your existing configuration, you can export it to a file by using the Export button and then import it to the new server.
If you'd like to keep your existing configuration, you can export it to a file by using the Export button and then import it to the new server.
![Export configuration](../../images/setup/export-configuration.png "Export configuration") ![Export configuration](../../images/setup/export-configuration.png "Export configuration")