# Virtual Network Adapter

### Adding a Network Adapter

**--device-add net --type** <**shared** | **bridged** | **host-only**> \[**--iface** <*name*>] \[**--mac** <**addr** | **auto**>]

\[**--ipadd** <*addr* \[/*mask*]> | **--ipdel** <*addr*\[/*mask*]> | **--dhcp** <**yes** | **no**> | **--dhcp6** <**yes** | **no**>]

\[**--gw** <*gw*>] \[**--gw6** <*gw*>] \[**--nameserver** <*addr*>] \[**--searchdomain** <*addr*>]

\[**--configure** <**yes** | **no**>] \[**--apply-iponly** <**yes** | **no**>]

\[**--adapter-type** <**virtio** | **e1000** | **e1000e** | **rtl**>]

### Modifying a Network Adapter

**--device-set** <*adapter\_name*> **--type** <**shared** | **bridged** | **host-only**> \[**--iface** <*name*>]

\[**--mac** <**addr** | **auto**>]

\[**--ipadd** <*addr* \[/*mask*]> | **--ipdel** <*addr*\[/*mask*]> | **--dhcp** <**yes** | **no**> | **--dhcp6** <**yes** | **no**>]

\[**--gw** <*gw*>] \[**--gw6** <*gw*>] \[**--nameserver** <*addr*>] \[**--searchdomain** <*addr*>]

\[**--configure** <**yes** | **no**>] \[**--apply-iponly** <**yes** | **no**>]

\[**--adapter-type** <**virtio** | **e1000** | **e1000e** | **rtl**>]

### Applying a Network Conditioner

Imitates adverse network conditions for testing purposes. Read more [here](/landing/parallels-desktop-developers-guide/software-development-specific-functions-of-parallels-desktop/simulating-adverse-network-connectivity-conditions.md).

**--network-conditioner** \[**--enable** | **disable**]

**--network-conditioner** \[**--inbound-bandwidth** *\<value\_in\_kbps>*] \[**--inbound-packet-loss** *\<value\_in\_%>*] \[**-- inbound-delay** *\<value\_in\_ms>*] \[**--outbound-bandwidth** *\<value\_in\_kbps>*] \[**--outbound-packet-loss** *\<value\_in\_%>*] \[**-- outbound-delay** *\<value\_in\_ms>*]

**--network-conditioner-profile** <**edge** | **3g** | **dsl** | **100-percent-loss** | **very-bad-net** | **wifi**>

To check the current status of the network conditioner, use the **prlctl list -i** command and look for the respective parameter in the **Network** section.

#### Parameters

*adapter\_name*: the name of the virtual network adapter to modify (**--device-set** command only). To obtain the list of the available adapters, use the prlctl list --info command.

**--type**: the type of the network adapter to create in the virtual machine.

**--iface**: the host network interface to be assigned to the bridged or host-only virtual network adapter.

**--mac**: the MAC address to be assigned to the virtual network adapter. If omitted, the MAC address will be automatically generated.

**--ipadd**: the IP address to be assigned to the network adapter in the virtual machine.

**--ipdel**: the IP address to be removed from the network adapter in the virtual machine.

**--dhcp**: specifies whether the virtual network adapter should get its IP settings through a DHCP server.

**--dhcp6**: specifies whether the virtual network adapter should get its IPv6 settings through a DHCP server.

**--gw**: the default gateway to be used by the virtual machine.

**--gw6**: the default IPv6 gateway to be used by the virtual machine.

**--nameserver**: the default DNS server to be used by the virtual machine.

**--searchdomain**: the default search domain to be used by the virtual machine.

**--configure**: if set to **yes**, the settings above are applied to the virtual network adapter instead of its original settings. Configuring any of the settings automatically sets this option to **yes**.

**--apply-iponly**: if set to **yes**, the hostname, nameserver, and search domain settings from the virtual machine configuration file are ignored.

**--adapter-type**: specifies the network adapter emulation type.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.parallels.com/landing/parallels-desktop-developers-guide/command-line-interface-utility/manage-virtual-machines-from-cli/virtual-machine-configuration-tasks/device-management/virtual-network-adapter.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.