How to Configure a LAN Segment in VMware for Network Partitioning

Quick Insight

VMware Workstation lets you build a custom LAN Segment to lock down your test lab. First, open your virtual machine settings panel. Next, add a fresh network group name for your isolated nodes. Then, assign that new tag to each virtual card. As a result, all data stays on a safe Layer 2 switch with zero host links. Plus, this setup stops all outside traffic from reaching your private test machines.

Network setup in VMware Workstation often starts with NAT or Bridged. However, these modes fall short when you want an isolated test lab. That is because these network types connect your virtual machines to the physical network. They also connect them to the internet. At this point, a special structure called LAN Segment comes into play.

This structure creates a fully closed environment for your virtual machines. In addition, the segment allows data to flow only between the VMs you define. Thus, you block unwanted traffic from the outside world. In addition, this isolation does not affect the physical network card of your host machine.

In 2026, Broadcom expanded network simulation in Workstation Pro 25H2. Now you can set bandwidth, latency, and packet loss per VM. You apply these settings at the adapter level. These new features bring the isolated lab environment closer to real conditions.

In this guide, you will learn to build a LAN Segment from scratch. You will also learn how to solve the missing DHCP issue. You will see how to reach the internet with pfSense. Also, you will learn how to monitor traffic with Wireshark. Finally, we will look at the WAN emulation features in 25H2.

LAN Segment Connection Setup with VMware Workstation and Virtual Network Segmentation

Experience
Over the years, I have built dozens of different lab scenarios. In the early days, I set up a new VMnet each time. However, my habit changed once I found the segment feature. Now I create dozens of isolated networks with one click.

What Is a LAN Segment? The Basis of Virtual Network Segmentation in VMware Workstation

Technical Definition and How It Works

Technically, this structure offers a private broadcast domain inside Workstation. When you give it a name, a unique segment ID forms in the background. Then, VMs tied to this ID join the same Layer 2 switch.

Thus, all unicast, multicast, and broadcast traffic stays inside the segment. In addition, your host operating system does not add a virtual adapter to this network. That means your main machine does not become part of the segment. This detail increases the isolation level.

Meanwhile, VMware does not attach an automatic DHCP service to this segment. For this reason, your virtual machines get an address from the APIPA block by default. This state lasts until you assign a static IP. Therefore, you must do IP planning from the start.

  • Isolated broadcast domain: Traffic flows only between segment members.
  • Does not create a host adapter: The main machine does not join the isolated network.
  • No DHCP service: You manage IP addressing.
  • Local VM limit: Remote or shared VMs cannot join this segment.

Three Critical Differences That Set the Segment Apart from Other VMware Network Types

In Bridged mode, your virtual machine looks like a separate device on the physical network. It gets an IP directly from the router. It can communicate with every device on the local network. In contrast, there is no outside visibility inside a LAN Segment. As a result, traffic does not reach your physical network adapter.

In NAT mode, VMs share the host’s IP address to reach the internet. This structure hosts an automatic DHCP server on VMnet8. By contrast, an isolated segment has no NAT translation. It also has no automatic address assignment. In summary, you configure everything manually.

FeatureBridged (VMnet0)NAT (VMnet8)Host-Only (VMnet1)LAN Segment
Physical network accessYesIndirect (NAT)NoNo
Internet accessYesYesNoNo
DHCP serverFrom physical networkVMware providesVMware providesNo
Host adapterYesYesYesNo
Isolation levelLowMediumHighHighest

A Host-Only network runs on VMnet1. It sets up a closed loop between the host and VMs. However, a host adapter exists here. In an isolated segment, even a host adapter is not created. Therefore, this is the right choice if you want full isolation.

Warning
Do not confuse an isolated segment with Bridged or NAT. These two modes open your VM to the physical network. They also open it to the internet. In your isolation test, confirm that segment members see only each other.

When Should You Choose a LAN Segment?

This structure is ideal for multi-tier app tests. For example, you can put web, app, and database VMs in the same segment. This way, you build a client-server environment isolated from the outside world.

It is also vital for cybersecurity labs. During malware analysis, you stop samples from leaking out. You join FlareVM, REMnux, and INetSim in the same segment. This way, you get a safe dynamic analysis environment.

Finally, it is ideal for network performance measurement and WAN emulation. With the per-VM latency and packet loss settings in 25H2, you simulate realistic conditions. All these scenarios make this structure stand out when isolation is critical.

  1. Active Directory lab network: Isolate domain controller, client, and server VMs.
  2. Malware analysis environment: Stop malicious software from leaking out.
  3. Multi-tier app test: Run web, app, and DB tiers in the same segment.
  4. Network performance measurement: Test latency and packet loss under controlled conditions.
  5. Penetration testing lab: Bring attacker and target VMs together on a safe network.

Creating a LAN Segment in VMware Workstation: Step-by-Step Setup

To create a segment, first open the VM settings. Then, you define a new segment from the network adapter section. The process is relatively simple, so you can finish it in a few minutes.

The steps below follow the Workstation 17 Pro interface. However, the menu layout remains largely the same in 25H2 & 26H1 and later versions. You see only small cosmetic differences.

Before you move to network settings, complete the steps to create a new virtual machine (VM). Make the hardware choice from the start.

Add and Name a New LAN Segment

First, open Workstation Pro and select the target virtual machine. Next, follow the path VM > Settings. In the window that opens, switch to the Hardware tab.

Now click Network Adapter in the left list. You see the connection types on the right side. Check the segment option in this list.

When you click this button below, the segment management window opens. From there, you press Add to create a new segment.

Configuring the Virtual Network Interface

Step 1

First, open the Client1 virtual machine. Then click the Network Adapter option. In the Virtual Machine Settings window, check the segment option.

Configure the Virtual Machine Network Settings

Step 2

After you check the option, click the LAN Segments… button. This way, you open the segment management window. A global settings screen appears before you.

Segments

Step 3

In the global settings window, press Add. This action creates a new segment group. Then you rename the group.

Global Network Segmentation

Step 4

The moment you click Add, the Segment1 group forms. Then click Rename to change the group name. Set the name of the new local network to Local.

After that, click OK to close the window. This way, the segment name becomes permanent.

Name the Segment Network

Step 5

This time, you see the Local group in the drop-down menu. Thus, the new segment is ready to select. Other options also stay visible in the list.

Add the VM to a Local Network

Step 6

Select Local and click OK. This action ties the adapter to the segment. VMware saves the settings immediately.

Local Network

Step 7

In the image below, the Client1 virtual machine is a Local member. You do not need to create a new segment for the second VM. You only need to select Local in the adapter settings.

Configure the Virtual Machine Network Card

Tip
If you plan to use the same segment for more than one VM, set the name with a standard template. For example, use names like PROD-WEB and PROD-DB. This way, you know which VM sits on which network at a glance.

Connect a Virtual Machine Network Adapter to a LAN Segment

To connect the second virtual machine to the same segment, open the settings again. You do not need to create a new segment for this action. You only need to select the correct segment.

The steps below confirm the segment connection with APIPA assignment and ping tests. Apply each step in order.

Step 1

First, start the Client1 and Client2 virtual machines. Check the IP address that Client1 gets from APIPA in the image. This address usually falls in the 169.254.x.x range.

APIPA

Step 2

Next, check the IP address that the Client2 virtual machine gets. Each VM gets a different APIPA address. This fact proves that no DHCP server exists.

APIPA IP Address

Step 3

Virtual machines in the same group communicate with each other. Now ping Client2 from the Client1 virtual machine. If the ping fails, turn off Windows Firewall.

Ping with Command Prompt

Step 4

In the same way, ping Client1 from the Client2 virtual machine. This way, you confirm two-way connectivity. Good replies show that the segment works.

Ping with Command Prompt

Step 5

In this structure, virtual machines can never reach the physical network. From Client1, ping your 192.168.1.0/24 physical network. Confirm the result to verify isolation.

Ping

Step 6

Finally, ping your physical network from the Client2 virtual machine. As a result, you get no reply. This way, you see that isolation is complete.

Ping Client2 VM

To confirm the connection, run the ipconfig or ip addr command inside the VM. If the VM tries to get an IP on its own, you see an address in the 169.254.x.x range. This shows that no DHCP server exists and APIPA has stepped in.

  • Windows: Check the Autoconfiguration IPv4 Address line in the ipconfig /all output.
  • Linux: Check the interface state with the ip addr show command.
  • Link state: Check the adapter’s Connected and Connect at power on options.

Put the Same VM on Two Different Segments with Multiple Adapters

In some scenarios, a VM must be connected to two separate networks. For example, a router VM is connected to both the WAN and LAN sides. For this, you add a second network adapter to the VM.

In the VM settings, click Add and select Network Adapter. Set a different segment for the new adapter. This way, the VM becomes dual-homed.

  1. Configure the first adapter as WAN-SEGMENT.
  2. Define the second adapter as LAN-SEGMENT.
  3. Assign a different IP subnet to each adapter.
  4. Check the routing table to confirm packet flow between the two networks.

This architecture forms the base for router VMs like pfSense or vyOS. In later sections, you will see how to use this structure for internet access.

Delete, Rename, and Care Points for Segments

You use the same segment management window to delete or rename a segment. A delete action disconnects all virtual adapters tied to that segment. Therefore, note which VMs will be affected before the action.

Renaming does not break current connections. However, the segment ID in the VMX file does not change. The system updates only the display name. For this reason, use the ID instead of the name in your automation scripts. This method is safer.

After a delete, you must set up the disconnected adapters manually again. VMware does not move you to another network on its own. Therefore, in critical lab environments, I suggest you take a snapshot before you delete a segment.

Caution
When you delete a segment, your VMs do not fall back to NAT or Bridged on their own. The adapters stay unlinked. Until you set up the network connection again, the VMs do not see each other.

LAN Segment: DHCP Issue, APIPA, and Static IP Fix

IP address assignment is the most confusing part of this structure. VMware runs an automatic DHCP server on NAT and Host-Only networks. However, no such service exists on an isolated segment. Therefore, you must manage the IP addresses.

If you make no configuration at all, VMs get an address from the APIPA block. This range is the 169.254.0.0/16 block. Windows and Linux fall into this block when they cannot find DHCP.

Why Is There No DHCP Server? APIPA (169.254.0.0/16) Behavior

APIPA is a backup mechanism that steps in when no DHCP server exists. The operating system selects a random address and checks for a clash. If no clash exists, it begins to use this address.

However, this method is not reliable. Each VM can get a different 169.254.x.x address. In addition, the system cannot assign default gateway information. Thus, even if VMs see each other, they cannot reach the internet.

Working with APIPA addresses leads to chaos, especially in labs with many VMs. Ping tests give mixed results. Therefore, for a lasting fix, you must use static IP addressing or bring your own DHCP server online.

Fact
Broadcom documentation states clearly that Workstation Pro does not provide a DHCP server for a segment. Because of this, you must do IP addressing manually or set up a separate DHCP server.

Assign a Static IP Address: Step by Step for Windows and Linux

Assigning a static IP is the fastest fix for small labs. You give each VM a fixed address. This way, addresses never change and your tests stay consistent.

For Windows: Open the network connections window. Right-click the adapter and select Properties. Select Internet Protocol Version 4 (TCP/IPv4).

  • IP address: 192.168.10.10
  • Subnet mask: 255.255.255.0
  • Default gateway: Leave it blank (an isolated network has no gateway).

For Linux: Use the nmcli or nmtui tool. For example, you assign the address with the nmcli con mod command. Then you refresh the connection with nmcli con up.

The visual steps below illustrate the manual IP assignment process with screenshots. You give Client1 and Client2 machines different addresses from the same subnet.

Step 1

To assign a manual IP to the Client1 virtual machine, open Network and Sharing Center. Then click the Ethernet adapter. Here, assign the 192.168.10.10/24 address to Client1.

Manual IP Address Configuration

Step 2

Now give the Client2 virtual machine an address from the same subnet. That is, let the Client2 IP address be 192.168.10.20. Make sure no clash exists between these addresses.

Manual IP Address Configuration

Step 3

After you assign the manual IP, test the network connection. Ping Client2 from Client1. At this point, good replies show that your setup is correct.

Ping a PC on the Same Network

Finally, you can build more advanced topologies with private networks. This way, you grow your skills and test yourself. Each new scenario offers a new chance to learn.

  1. Give each VM a different IP (e.g., .10, .20, .30).
  2. Keep the subnet mask the same on all VMs.
  3. Leave the gateway field blank; an isolated segment has no router.
  4. If you need a DNS server, set up a separate VM with the DNS role.

Set Up a DHCP Server on a LAN Segment

Static IP management becomes difficult as the VM count grows. In this case, running a DHCP server inside the segment makes more sense. You can set up a Windows Server or Linux-based VM with the DHCP role.

For Windows Server: Add the DHCP Server role from Server Manager. After setup, create a new scope. For example, for the 192.168.50.0/24 network, define the range 192.168.50.100–192.168.50.200.

For Linux: You can use the isc-dhcp-server or dnsmasq package. Add the subnet definition to the /etc/dhcp/dhcpd.conf file and then start the service.

  1. Give the DHCP server VM a static IP (e.g., 192.168.50.2).
  2. Define the scope range and subnet mask.
  3. Set the DHCP server itself as the default gateway (leave it blank if not needed).
  4. Set the other VMs to get an IP on their own.

This structure is especially useful in Active Directory labs. Client VMs get an IP on their own and can join the domain. In addition, name resolution works without issues thanks to DNS integration.

Recommendation
If you have more than 10 VMs, set up a DHCP server without fail. Static IP management becomes unmanageable after a point. With DHCP, you also prevent IP address conflicts automatically.

Spot IP Clashes and ARP Issues

If an IP clash happens on an isolated segment, two VMs try to use the same address. In this case, network traffic is disrupted. You see connection drops. In this state, check the ARP table to find the issue.

  • List the ARP cache with the arp -a command.
  • Check whether two different IPs point to the same MAC address.
  • If you get a Destination host unreachable error in a ping test, check the subnet mask.
  • Use Wireshark to monitor ARP requests and find the clashing address.

A MAC address clash also leads to similar issues. Cloned VMs can sometimes start with the same MAC address. In this case, you must generate a new MAC address from the VM settings.

LAN Segment vs Host-Only vs NAT vs Bridged: Which One and When?

All four network types serve different needs. A wrong choice means either needless isolation or unwanted outside access. The comparison below will help you make the correct decision.

CriteriaBridgedNATHost-OnlyLAN Segment
ScopePhysical networkHost + outside networkHost + VMsOnly VMs
IsolationLowMediumHighHighest
InternetDirectThrough NATNoNo
DHCPFrom physical networkVMware providesVMware providesNo
Host adapterYesYesYesNo
Use caseProduction-like testDaily useHost-VM testFull isolation

Scope, Isolation, and Internet Access Matrix

Bridged mode connects your VM directly to the physical network. This way, other computers on the network see your VM. However, this state does not fit scenarios that need isolation.

NAT mode lets VMs reach the internet while it blocks connections from the outside. It is convenient for daily development work. However, it is not enough if you want full isolation.

A Host-Only network sets up a closed loop between the host and VMs. It has no internet access. However, the host machine joins this network because a host adapter exists.

LAN Segment, on the other hand, does not create a host adapter at all. It sets up a network only between VMs. For this reason, it offers the highest isolation level.

Note
On a Host-Only network, the host adapter forms over VMnet1. You can increase isolation by turning off this adapter. However, you still cannot get isolation as complete as a segment.

Difference Between LAN Segment and Custom VMnet (VMnet2/VMnet3)

You define custom VMnet networks through the Virtual Network Editor. Each one has its own subnet and DHCP settings. It also offers an option to create a host adapter.

A segment is a lighter structure. It does not need a separate VMnet definition in the Virtual Network Editor. You store the segment ID in the VMX file. This way, you build dozens of different isolated networks.

  • VMnet2/VMnet3: Offer a permanent subnet, DHCP, and host adapter options.
  • LAN Segment: Ideal for temporary or permanent isolated networks; it does not create a host adapter.
  • Flexibility: You can create or delete segments faster.
  • Use: If you need many different isolated labs, a segment is more convenient.

Difference Between LAN Segment and VLAN: Layer 2 Isolation and Tagging

A VLAN performs logical network segmentation on a physical switch. It adds a VLAN tag to Ethernet frames. This way, it creates more than one broadcast domain on the same physical infrastructure.

LAN Segment, in turn, offers fully software-based isolation inside VMware. It does not use a VLAN tag. Each segment acts like a separate virtual switch. Thus, it does not need physical switch configuration.

For a real VLAN experience, you can set up VLAN tagging in the Virtual Network Editor. However, a segment is much simpler and more effective for an isolated lab.

Give a LAN Segment Internet Access: pfSense/vyOS Router VM Model

The biggest limitation of an isolated segment is the lack of internet access. However, in some lab scenarios, VMs must get updates or reach outside sources. In this case, a router VM steps in.

You set up a router operating system like pfSense or vyOS as a VM. This VM has two network adapters: one WAN (NAT or Bridged), the other LAN (isolated segment). This way, VMs on the segment reach the internet through the router.

Dual-Homed Router VM Architecture (WAN + LAN Segment)

A dual-homed VM has two adapters tied to two different networks. One adapter faces the outside world (WAN), the other faces the isolated segment (LAN). The router VM routes packets between these two networks.

In this architecture, setting the WAN side as NAT is the most convenient method. That is because NAT shares the host internet connection. The LAN side, in turn, is the isolated segment.

  • WAN adapter: NAT (VMnet8) or Bridged (VMnet0).
  • LAN adapter: Isolated segment.
  • Router: pfSense, vyOS, OPNsense, or a Linux-based router.

Thanks to this structure, VMs on the segment reach the internet. You still block unwanted traffic from the outside world. The router VM filters traffic with firewall rules.

pfSense Setup and Interface Assignment

Download the pfSense ISO and create a new VM. Add two network adapters to the VM. Set the first adapter as NAT and the second as the isolated segment.

During setup, pfSense asks you to assign the WAN and LAN interfaces. em0 is often WAN, and em1 is LAN. However, you should still check MAC addresses and make the correct assignment.

  1. Start the pfSense setup and complete the disk install.
  2. On the interface assignment screen, select the NAT adapter for WAN.
  3. Select the segment adapter for LAN.
  4. Set the LAN IP address as 192.168.50.1/24.
  5. Turn on the DHCP server on the LAN interface.

After setup, you can reach the web interface from the LAN side. Access from the WAN side is off by default. This is the correct default for security.

Important
Set the pfSense LAN IP address as the default gateway for VMs on the segment. Otherwise, VMs cannot reach the internet. If you use DHCP, the system provides this setting automatically.

Internet Sharing with NAT and Static Route Setup

pfSense runs in NAT mode by default. It translates traffic on the LAN side into the WAN IP. This way, all VMs on the segment reach the internet through a single IP.

If NAT is off or you need a special route, you must define a static route. For example, you use the Firewall > Routes menu to reach another subnet.

A static route definition looks like this: target network, subnet mask, and gateway. For example, to reach the 10.0.0.0/24 network, you point to the router’s own LAN IP as the gateway.

  1. Edit the LAN scope from the Services > DHCP Server menu.
  2. Enter the pfSense LAN IP (192.168.50.1) as the gateway.
  3. Set pfSense or an external DNS server as the DNS server.
  4. Check the NAT rule under Firewall > NAT > Outbound.

Routing Between Segments (Inter-Segment Routing)

If you have more than one isolated segment, you may want to route between them. For example, you might want controlled access between a DMZ segment and an inner network segment.

For this, add a separate adapter to the router VM for each segment. In pfSense, assign an IP to each interface. Then control traffic between segments with firewall rules.

  1. Add a third adapter to the router VM and define it as DMZ-SEGMENT.
  2. In pfSense, assign the 192.168.60.1/24 IP to this interface.
  3. Set the default gateway of VMs on both segments to the matching pfSense interface IP.
  4. With firewall rules, allow only the traffic you permit to pass.

This structure offers a realistic topology for multi-tier app tests. The web tier runs in the DMZ, while app and database tiers run on the inner network. Traffic between them passes through the router.

Packet Analysis and Traffic Monitoring: Wireshark and Promiscuous Mode

An isolated segment offers a very safe environment for packet analysis. Because no outside noise exists, you study only your own traffic. In addition, you can do deep analysis with tools like Wireshark.

However, you need promiscuous mode to capture all traffic. This mode lets the network adapter accept frames that do not belong to it. That means you must allow it at the virtual switch level.

Effect of Promiscuous Mode on a Segment

Promiscuous mode lets a VM see all traffic on the segment. Normally, the adapter handles only frames sent to its own MAC address. In this mode, you capture all broadcast and unicast traffic.

In VMware Workstation, promiscuous mode is off by default. You must turn it on through the Virtual Network Editor. However, because a segment has no separate VMnet definition, this setting does not appear directly in the segment options.

Instead, put your analysis VM on the same segment as the other VMs. Then start Wireshark in promiscuous mode. The virtual switch will mirror traffic inside the segment to the analysis VM.

Test Result
In my own tests, I captured traffic between three VMs on the same segment with Wireshark without issue. When I turned on promiscuous mode, I saw broadcast ARP requests and unicast TCP sessions in full.

Capture Segment Traffic with Wireshark (BPF Filters)

Run Wireshark inside the VM and select the segment adapter. After you start the capture, you can narrow traffic with BPF filters. This way, you filter out unnecessary packets and speed up analysis.

For example, use the tcp port 80 filter to see only HTTP traffic. The icmp filter is enough for ICMP packets. Apply the arp filter for ARP analysis.

  1. Open Wireshark and select the segment adapter.
  2. Type not arp in the capture filter to drop ARP noise.
  3. Use the ip.addr == 192.168.50.10 filter to monitor one VM’s traffic.
  4. Stop the capture and get a summary with Statistics > Protocol Hierarchy.

Study ARP Table, Broadcast, and Multicast Behavior

ARP behavior on an isolated segment is relatively clear. Each VM finds other VMs on the same segment with ARP requests. Broadcast ARP requests reach all segment members.

  • View the ARP cache with arp -a.
  • Use the ether broadcast filter to monitor broadcast traffic.
  • Apply the ip multicast filter for multicast traffic.
  • For an ARP poisoning test, compare ARP replies between two VMs.

These observations offer valuable data for network security training. For example, you can test ARP spoofing attacks without risk on an isolated segment.

25H2 and Later: Bandwidth, Latency, and Packet Loss Simulation

VMware Workstation 25H2 brought key new features to network simulation. Now you set bandwidth, latency, and packet loss per VM. You define these settings on the virtual adapter, not at the segment level.

This change lets each VM simulate different network conditions. For example, one VM can run at low bandwidth while another stays at normal speed. This flexibility is very valuable for realistic test scenarios.

Per-VM Bandwidth Limit and Two-Way Traffic

For a bandwidth limit, follow Network Adapter > Advanced in the VM settings. Here you will see the Bandwidth section. You can set separate speeds for inbound and outbound traffic.

For example, you can enter 1544 Kbit/s to simulate a T1 line. Or you can write a custom value to set the speed you want.

  1. Shut down the VM and open its settings.
  2. Select Network Adapter and click the Advanced button.
  3. Select a speed profile from the Bandwidth drop-down or enter a Custom value.
  4. Set separate speeds for inbound and outbound traffic.
  5. Save the settings and start the VM.

This setting is ideal for WAN emulation and for testing app behavior under slow network conditions.

WAN Emulation with Latency and Jitter Settings

A latency setting increases the time packets take to reach the target artificially. In 25H2, you can enter this value in milliseconds. The supported range is generally 0 to 2000 ms.

For example, when you set 200 ms latency, the real delay lands in the 200–210 ms range. This gap comes from the hypervisor’s own processing time.

  1. Find the Latency field in the Advanced settings.
  2. Enter separate latency values for inbound and outbound traffic.
  3. Watch how your app reacts to this delay.
  4. For jitter measurement, study time gaps between packets in Wireshark.

This feature makes local tests of apps that run on remote servers much easier. Thus, you can simulate real WAN conditions in a lab environment.

Packet Loss Simulation and Realistic Test Scenarios

Packet loss is one of the most common causes of network issues. With 25H2, you can set a loss rate per VM. The default value is 0%.

For example, when you set 5% packet loss, one in every twenty packets is dropped. In this state, TCP retries the send to keep the connection alive. You can test how your app behaves under these conditions.

  1. Enter the rate you want in the Packet Loss (%) field.
  2. Set separate values for inbound and outbound traffic.
  3. Test delay-sensitive apps like VoIP or video streams.
  4. Check the results with Wireshark.
Fact
Virtualization Review highlights the most useful feature of 25H2 as its ability to simulate bad network conditions. Other hypervisors rarely offer this feature in such detail.

LAN Segment Automation: Setup with vmrun, PowerShell, and the VMX File

If you manage many VMs and segments, manual setup wastes time. VMware offers automation with command-line tools. vmrun and VMX file edits form the base of this work.

In addition, the dictTool utility that comes with 25H2 lets you edit VMX files from the command line. This tool makes scripting easier.

Each segment carries a unique ID in the background. You store this ID in the ethernet0.pvnID parameter in the VMX file. The short form pvn means private virtual network.

For example, you can see this line in the VMX file: ethernet0.pvnID = "52 4f 4d 45 4f 2d 33 32 2f 31 32 2f 32 30 32 36". This value is the unique ID of the segment.

All VMs tied to the same segment carry the same pvnID value. Even if you rename the segment, this ID does not change. Therefore, using the ID instead of the name in automation scripts is more reliable.

  • ethernet0.pvnID: Sets the segment ID.
  • ethernet0.connectionType = "pvn": Defines the link type.
  • ethernet0.virtualDev = "e1000e": Sets the virtual network card model.
  • ethernet0.addressType = "generated": Shows the MAC address assignment method.

Start a VM on a Specific Segment with vmrun

The vmrun tool lets you start VMs from the command line. However, segment assignment is not a direct vmrun parameter. Therefore, you define the segment connection in the VMX file.

Then you start the VM with the vmrun start command. The VM opens with the segment settings from the VMX file.

  1. Open the VMX file with a text editor.
  2. Update the ethernet0.pvnID line with the target segment ID.
  3. Save the file.
  4. Run the vmrun start "C:\\VMs\\TestVM\\TestVM.vmx" command.
vmrun -T ws start "C:\\VMs\\WebServer\\WebServer.vmx" nogui

This method helps you especially when you build automated test environments in CI/CD pipelines.

Bulk Segment Assignment with PowerShell Scripts

With PowerShell, you can edit the VMX file of more than one VM in bulk. This way, you connect dozens of VMs to the same segment in one pass.

The script below updates the ethernet0.pvnID line in every VMX file in the given folder:

$segmentId = "52 4f 4d 45 4f 2d 33 32 2f 31 32 2f 32 30 32 36"
Get-ChildItem -Path "C:\\VMs" -Filter *.vmx -Recurse | ForEach-Object {
    $content = Get-Content $_.FullName
    $content = $content -replace 'ethernet0\\.pvnID = ".*"', "ethernet0.pvnID = `"$segmentId`""
    $content | Set-Content $_.FullName
}

Before you run this script, make sure the VMs are powered off. The system overwrites changes made to open VMs when the VM shuts down.

Tip
Back up the VMX files before bulk work. A wrong pvnID value can leave your VMs unlinked. Keep backups ready so you can roll back.

Build an Isolated Malware and Cybersecurity Lab with LAN Segment

Malware analysis needs an environment completely isolated from the outside world. This structure is the best fit for this need. You stop malicious samples from leaking out over the network.

In this section, you will see how to join tools like FlareVM, REMnux, and INetSim on the same segment. We will also look at traffic routing with the Burp Suite proxy and static ARP.

Join FlareVM, REMnux, and INetSim on the Same Segment

FlareVM is a Windows-based reverse-engineering and analysis platform. REMnux, in turn, is a Linux-based distribution. On the other hand, INetSim offers simulated internet services.

By putting these three VMs on the same isolated segment, you set up a full analysis environment. FlareVM runs the sample, REMnux monitors network traffic, and INetSim makes simulated replies.

  1. Connect all three VMs to the same MALWARE-LAB segment.
  2. Give each VM a static IP from the 10.10.10.0/24 network.
  3. Start the Wireshark and INetSim services on REMnux.
  4. Point the FlareVM DNS server to the REMnux/INetSim IP.
  5. Confirm the segment is closed to the outside with the ping 8.8.8.8 test.

This structure stops malware from reaching the real internet while it records all behavior.

Traffic Routing with Burp Suite Proxy and Static ARP

When you analyze web-based malware, you must pass traffic through a proxy. Burp Suite lets you capture and analyze HTTP/HTTPS traffic.

However, some malware ignores proxy settings. In this case, you can force traffic to the proxy VM with a static ARP entry. You add a simulated gateway MAC address to the target VM’s ARP table.

  1. Find the proxy VM MAC address.
  2. Run the arp -s 10.10.10.1 <proxy-mac> command on the target VM.
  3. Start Burp Suite in transparent proxy mode on the proxy VM.
  4. Set the target VM default gateway as the proxy IP.
  5. Confirm traffic flows through Burp Suite.

This technique is effective especially in the analysis of malware that tries to avoid a proxy.

Verify Segment Isolation and Stop Outside Leaks

You must make sure the analysis environment is isolated from the outside. Otherwise, malware can leak out and create a serious risk.

  • Test internet access with the ping 8.8.8.8 command; no reply should come back.
  • Check whether a path to the outside exists with tracert 8.8.8.8.
  • Confirm your host machine does not appear on the segment.
  • Use Wireshark to verify that not even one packet leaves the segment.
  • If a router VM exists, disconnect the connection on its WAN interface.
Critical
Never use a NAT or Bridged network in a malware analysis lab. One wrong setup can cause malware to leak into your real network. Because of this, always stay on an isolated segment.

LAN Segment Troubleshooting Decision Tree: Ping Fails, VMs Do Not See Each Other

When you encounter connectivity issues on an isolated segment, you must proceed in a clear order. You find the source of the issue by checking layer by layer. The decision tree below covers the most common issues.

Layer 1-2-3 Systematic Checklist

First, check the physical layer. Is the VM network adapter connected? Is the segment selected? Next, move to the data link layer. Do MAC addresses clash? Finally, check the IP setup at the network layer.

  1. Layer 1 (Physical): Is the adapter’s Connected option checked?
  2. Layer 2 (Data link): Do all VMs carry the same segment ID?
  3. Layer 2: Is there a MAC address clash? Check with arp -a.
  4. Layer 3 (Network): Are the IP addresses on the same subnet?
  5. Layer 3: Is the subnet mask correct on all VMs?

Apply this list in order. Focus on the fix at the layer where you find the issue. Do not move to higher layers until you solve the lower layer.

MAC Address Clash, ARP Reply, and Missing Default Gateway

Cloned VMs can start with the same MAC address. In this case, network traffic is disrupted. In this state, you must generate a new MAC address from the VM settings.

An ARP reply clash shows similar signs. If two VMs reply to the same IP, the connection becomes unstable. For this reason, monitor ARP traffic with Wireshark and find the clashing address.

A missing default gateway is normal on an isolated segment. However, if you use a router VM, you must set a gateway. With no gateway, VMs communicate only with devices on the same subnet.

  • MAC clash: Generate a new MAC from the VM settings.
  • ARP clash: Clear the static ARP entries.
  • Missing gateway: If a router VM exists, enter the gateway IP.
  • Routing table: Check with route print or ip route.

Firewall and No NIC on the Host

By design, an isolated segment does not create a NIC on the host operating system. This is intentional; it is not an issue. The host not appearing on the segment increases isolation.

However, the firewall inside the VM can block the connection. Windows Defender or Linux iptables rules can drop ICMP packets. Before the test, turn off the firewall temporarily or allow ICMP.

Also, if the VM network profile is Public, the system blocks ping replies. Change the profile to Private or Domain. This small change saves you hours of troubleshooting work.

Note
No host adapter is proof of isolation. If you see a new NIC on the host, you may have set up a VMnet or Host-Only network by mistake.

VMware LAN Segment: Resources, Documentation, and Further Reading

If you want to study the official basis for the setups in this guide, check the sources below. Current Broadcom documentation explains all new features in the 25H2 release in detail.

FAQ About LAN Segment

What is a LAN Segment in VMware Workstation and what does it do?

A LAN Segment is a closed virtual network inside Workstation. You give this network a name. VMware creates a unique ID in the background.
VMs tied to the same name behave as one Layer 2 switch. Traffic flows only between these members. Your host machine does not add an adapter to this network.
Thus, you set up a test environment completely isolated from the physical network. For example, you put FlareVM and REMnux on the same segment for malware analysis. You do not want internet access.
This structure gives you safe isolation. To be clear, no DHCP service exists. You manage the IP addresses. A host adapter is not created here. This detail increases isolation. This network type helps you in multi-tier app tests.

What is the difference between LAN Segment and Host-Only?

A Host-Only network runs on VMnet1. It sets up a closed loop between the host and VMs. A host adapter exists here.
A segment, in turn, does not create a host adapter. That means your main machine does not join the isolated network. This difference increases the isolation level.
For example, if you want to copy files from the host to a VM, Host-Only works. If you want full isolation, you choose a segment. By contrast, VMware provides DHCP on a Host-Only network.
A segment has no automatic address assignment. That is because this structure focuses only on traffic between VMs. As a result, you build a more closed lab with no host adapter.
On a Host-Only network, the host and VMs share the same broadcast domain. Thus, the isolation level stays lower. On a segment, the main machine stays outside the network.

How do you assign an IP address on a VMware LAN Segment?

VMware does not run DHCP on a segment. VMs get an APIPA address on first start. This range is the 169.254.0.0/16 block. For a lasting fix, you assign a static IP. On Windows, you open the TCP/IPv4 settings. You choose different addresses from the same subnet.
For instance, assign 192.168.10.10 to Client1 and 192.168.10.20 to Client2. Set the subnet mask to 255.255.255.0 while leaving the gateway field blank. On Linux, configure the address using the nmcli command, then refresh the connection.
You confirm the connection with a ping test. If you need DNS, you use a separate VM. Also, you can set up your own DHCP VM.

How do you set up a DHCP server on a LAN Segment?

VMware does not give you DHCP on a segment. You set up your own DHCP VM. You give this VM a static IP. On Windows Server, you add the DHCP Server role. You create a new scope. You define the range 192.168.50.100–192.168.50.200.
On Linux, you use the isc-dhcp-server package. Write a subnet definition in the dhcpd.conf file and start the service. Next, connect client VMs to the segment, keeping the first lease time short while waiting for automated IP assignment.
This way, you get fast results in tests. If the DHCP VM is off, clients fall back to APIPA. This structure reduces the workload in small labs.

VMs on a LAN Segment do not see each other; what should I do?

First, you check that both VMs use the same segment name. Make sure Connected and Connect at power on are checked in the adapter settings. Then you give each VM an IP from the same subnet.
Windows Firewall can block ping. You open a temporary rule for the test. On Linux, you look at the ip addr output. If you see APIPA, it means no DHCP exists. You assign a static address. You ping Client2 from Client1.
If no reply comes, you check the segment name again. Also, you confirm the VMs are not on different virtual switches. If needed, you remove the adapter and add it again.
Then you run the ping test again. These steps show the source of the issue quickly.

How do you limit bandwidth on a LAN Segment?

Workstation Pro 25H2 offers new network emulation settings. You go to the Network Adapter section in the VM settings. In the Advanced options, you see the bandwidth field.
You enter the value in Mbps. There are separate fields for latency and packet loss. You apply these settings at the adapter level. For example, you choose 10 Mbps and 100 ms latency. You set packet loss to 2%. This way, you simulate a slow WAN condition.
You take a snapshot before the test. You monitor the results with Wireshark. When you remove the setting, you return to the old performance. You change values in small steps. This feature makes performance tests much easier.

How do you create more than one LAN Segment in VMware Workstation?

You do not need to open a separate segment for each VM. On the first VM, you open the Network Adapter settings. Check the segment option and click the Segments button. Next, create a new group with Add and give it a clear name using Rename.
For example, you choose names like PROD-WEB and PROD-DB. On the second VM, you select the same name from the list. This way, the two VMs connect on the same isolated network.
First, add new segments for different tests. Assign a separate subnet to each segment, following a standard naming template. This method lets you manage dozens of lab networks with one click. If confusion arises, you note the segment ID.

What happens when you delete a LAN Segment?

When you delete a segment, the adapters stay unlinked. VMware does not move VMs to NAT or Bridged. That means you relink each VM manually.
Before this action, you note which VMs will be affected. In critical labs, I suggest you take a snapshot. A delete action removes the segment ID.
Renaming does not break current connections. Only the display name changes. You use the ID instead of the name in automation scripts.
Otherwise, your scripts can fail. After a delete, IP settings stay inside the VM. But ping fails because the network connection is cut. When you connect the adapter to the right segment, traffic flows again. Thus, do not rush the deletion.

Is the segment feature safe?

This structure blocks outside traffic. VMs communicate only with segment members. Because no host adapter is created, the main machine does not join the network. In a malware lab, this isolation is essential. However, absolute security does not exist. A VM linked to the wrong segment can leak out.
For this reason, you check each VM adapter one by one. Snapshots and a separate host reduce the risk. At the same time, you turn off shared folders.
You also turn off clipboard sharing. If you need internet access, you connect the pfSense VM intentionally. Inside a segment, a hostile VM can still affect the others. Thus, isolation is strong, but operational discipline is required.

What is the difference between LAN Segment and VLAN?

A VLAN splits a logical network on a physical switch. A segment, in turn, creates a virtual broadcast domain inside Workstation. VLAN carries traffic with trunks and tags.
Segment traffic stays local between VMs. VLAN needs a router or Layer 3 switch. A segment does not even have a host adapter.
For example, you use a VLAN in a real server lab. You choose a segment for an isolated test on one machine. VLAN is part of the wired network.
A segment lives fully inside software. In terms of a security boundary, a segment is more isolated. Yet you extend VLAN across the whole physical network. Only local VMs see a segment. Do not think these two concepts are the same.

Can you use LAN Segment in VMware Workstation Player?

The Workstation Player interface does not offer a segment creation screen. This feature is available in the Pro version. In Player, you usually see Bridged, NAT, and Host-Only options.
You cannot use an existing segment with Player. That is because the segment definition is tied to Pro virtual network management. If you need an isolated lab, you move to Pro. As an option, you use a Host-Only network. Host-Only does not give full isolation. The host adapter exists on that network.
Still, it is enough for quick tests. In Player, you stay limited to Custom VMnet options. In addition, 25H2 WAN emulation also runs on the Pro side. Thus, if you plan a serious lab, you choose Pro. The Player version is suitable for basic use.

How do you set up IPv6 on a LAN Segment?

On a segment, you again do manual setup for IPv6. VMware does not offer automatic DHCPv6. Each VM gets a link-local address on its own.
This address falls in the fe80::/10 block. For a lasting test, you assign a global address. You write 2001:db8:10::10/64. You give different addresses to VMs on the same segment. If no router VM exists, the gateway stays blank. You test connectivity with ping6.
On Windows, you enter IPv6 from the network adapter properties. On Linux, you add the address with the nmcli command. If you want DHCPv6, you set up the service on a separate VM. You keep the subnet prefix the same on all VMs. This structure gives a clean base for IPv6 labs.

Conclusion: Five Golden Rules to Set Up a LAN Segment Correctly

Do not rush when you set up a LAN Segment network. Document and test each step. The five rules below form the base of a solid lab environment.

  1. Lock the segment ID: Renaming does not change the ID; use the ID in automation.
  2. Plan IPs ahead: Prevent clashes with static IP or a DHCP server.
  3. Verify isolation: Prove no outside leak with ping and Wireshark tests.
  4. Keep the router apart: If you need internet, place the pfSense/vyOS VM outside the segment.
  5. Take a snapshot: Make a rollback point before a segment deletion or rebuild.

When you follow these rules, you get a safe isolated network on VMware Workstation. In addition, this network becomes manageable. Now you can use this structure with confidence in every scenario, from malware analysis to multi-tier app tests.

They'll Thank You for Discovering This Guide!

Ready to do your loved ones a huge favor with just one click? Knowledge grows as it is shared.

Be the first to share your comment