VMware virtual Machines Build pentest network environment

VMware Virtual Machines Build a network environment for penetration testing 1. The question was raised

Running Kali Linux or owasp WTE through a virtual machine requires target drone to learn and research for penetration testing. The simpler approach is that target drone also operates as a virtual machine, creating a dedicated network connection between the infiltration machine and the virtual machine.

Using the LAN segment (LAN Segament) provided by VMware is a simple and fast solution. 2. Step -up instructions for setting up LAN section, virtual machine settings for target drone and osmosis machines in VMware

Virtual machine Internal 2.1 LAN section (LAN Segament) settings for target drone and infiltration machine system network settings

In VMware Workstation, open the Virtual Machine Settings tab for the target virtual machine, and click LAN Segment, as shown in the following figure:
![ After clicking on the "LAN section" button here (https://img-blog.csdn.net/20150701151917545)
,

+ If no LAN segment has been set, create a new LAN segment
+ If it has already been set, select the LAN segment where the target resides

2.2 Infiltration Machine/target drone virtual machine settings

After you have completed the above LAN section Setup, the virtual machine's network connection mode is set to "LAN segment" and the specific section of the above settings is selected.
the * * settings for virtual machines and target drone are the same * *.

2.3 The system setup of the osmosis machine/target drone

 to enter the virtual machine system, you need to specify the IP address manually, to ensure that the infiltration machine and target drone in the same network segment.
 The * * settings for virtual machines and target drone are the same * *.
 Windows settings are relatively simple. + for Linux without graphical interface, the manual setting method is as follows: 1. Turn off the network card in order to * * Clear previous networking settings * * <pre><code>$ ifconfig eth0 down</code></pre> 2. Set a new IP address and other information, and start the network card <pre><code>$ ifconfig eth0 192.168.xx.123 netmask 255.255.255.0 up</code>< /pre> > Note that the last up here is the meaning of the boot Nic 3. To set up gateway gateways, you need to use the route command <pre><code>$ route add default GW 192.168.xx.1 + for Linux with graphical interface, there are sometimes networ
     K Manager Shows "Device not managed", especially under Debian or Kali. 1. The problem is because the following conditions are met: (1) The/etc/network/interface file includes the target device (network card); (2)/etc/networkmanager/networkmanager.co
     No automatic management is set in NF.
                2. Workaround: (1) in/etc/networkmanager/networkmanager.conf, set Managed=true (2) To restart Network manager: <pre><code> $service Network-manager restart</code></pre>