> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan-mtu.md).

# Configure the MTU for a Private LAN

Check and configure the MTU that the IONOS CLOUD DHCP server assigns to VMs on a private LAN, or keep an MTU of 1500 bytes.

The <code class="expression">space.vars.ionos\_cloud</code> Dynamic Host Configuration Protocol (DHCP) server supports the interface maximum transmission unit (MTU) option, DHCP option 26, on private [<mark style="color:blue;">LANs</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#local-area-network-lan). If a virtual machine's (VM's) DHCP client requests this option, the VM is automatically configured with the largest MTU that the private LAN supports, up to 4074 bytes. Larger packets increase throughput and reduce CPU overhead for traffic between VMs in the same private LAN. Because the MTU is set through DHCP, it's consistent across all VMs in the LAN without manual configuration.

The option applies to [<mark style="color:blue;">Dedicated Core Servers</mark>](https://docs.ionos.com/cloud/compute-services/compute-engine/dedicated-core.md), [<mark style="color:blue;">vCPU Servers</mark>](https://docs.ionos.com/cloud/compute-services/compute-engine/vcpu-server.md), and [<mark style="color:blue;">Cubes</mark>](https://docs.ionos.com/cloud/compute-services/cubes/overview.md) with a [<mark style="color:blue;">NIC</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#nic) on a private LAN with DHCP enabled. Use this guide to check which MTU your VM uses and, if required, keep an MTU of 1500 bytes.

{% hint style="info" %}
**Prerequisites:**

* A VM with a NIC on a private LAN with DHCP enabled. For more information, see [<mark style="color:blue;">Configure a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan.md).
* Administrator (root) access to the VM's operating system.
  {% endhint %}

{% hint style="info" %}
**Note:**

* NICs with a public IP address keep their existing MTU.
* If the VM's DHCP client doesn't request the option, the VM keeps its existing MTU, typically 1500 bytes.
* Windows doesn't request DHCP option 26, so Windows VMs keep their existing MTU.
  {% endhint %}

{% hint style="warning" %}
**Important:** If traffic from the private LAN also passes through a component or path with a smaller MTU, Path MTU Discovery must work end to end. If it doesn't, keep an MTU of 1500 bytes on the interface.
{% endhint %}

## Procedure

{% stepper %}
{% step %}

### Check the current MTU

Replace `[device_name]` with the name of the network interface, for example, `eth1`, and check the `mtu` value in the output:

```bash
ip link show [device_name]
```

If the value is larger than 1500 and you haven't set it manually, the VM uses the MTU assigned by the <code class="expression">space.vars.ionos\_cloud</code> DHCP server. To keep the larger MTU, no further action is required.
{% endstep %}

{% step %}

### Keep an MTU of 1500 bytes

Use one of the following methods:

{% tabs %}
{% tab title="Static MTU" %}
Set a static MTU of 1500 on the interface in the operating system's network configuration. Some DHCP clients still apply the MTU from the DHCP server over a static MTU.

For ISC dhclient, add the following line to the DHCP client configuration to keep an MTU of 1500 bytes:

```
supersede interface-mtu 1500;
```

{% endtab %}

{% tab title="Don't request MTU option" %}
Configure the DHCP client not to request the MTU option:

* **ISC dhclient:** Remove `interface-mtu` from the `request` line in `/etc/dhcp/dhclient.conf`.
* **systemd-networkd:** Set `UseMTU=no` in the `[DHCPv4]` section:

  ```ini
  [DHCPv4]
  UseMTU=no
  ```
* **Netplan:** Set `dhcp4-overrides: { use-mtu: false }`. If cloud-init manages your Netplan configuration, verify that the setting persists after a restart.
  {% endtab %}
  {% endtabs %}
  {% endstep %}

{% step %}

### Apply the change

Renew the VM's DHCP lease or restart its network. The MTU configuration takes effect when the DHCP lease is renewed or the network is restarted.
{% endstep %}

{% step %}

### Verify the MTU

Run the command again and check that the `mtu` value is 1500:

```bash
ip link show [device_name]
```

Restart the VM, then run the command again and check that the `mtu` value is still 1500. If the value has changed, your network configuration was overwritten during startup. Use the **Static MTU** method or make the change in a configuration file that persists across restarts.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Result:** The interface on the private LAN uses an MTU of 1500 bytes. To use the larger MTU again, remove the static MTU or configure the DHCP client to request the MTU option, and then renew the DHCP lease.
{% endhint %}

## Related topics

* [<mark style="color:blue;">Larger MTU for Private LANs through DHCP</mark>](https://docs.ionos.com/cloud/release-notes/november-2026.md)
* [<mark style="color:blue;">Why did the MTU on my private LAN interface change?</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/networks-faq.md#why-did-the-mtu-on-my-private-lan-interface-change)
* [<mark style="color:blue;">How can I configure VirtIO settings in Linux?</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/networks-faq.md#how-can-i-configure-virtio-settings-in-linux)
* [<mark style="color:blue;">Configure a Private LAN</mark>](https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/network-services/vdc-networking/lan/how-tos/configure-private-lan-mtu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
