# Enabling IPv6 on Your Service

## Enabling IPv6 on Your Service

UP-NETWORK allows all VPS and dedicated servers to receive a full **/64 IPv6 subnet**.\
This guide explains how to enable IPv6, how to fix cases where the subnet was not assigned at deployment, and how to configure IPv6 on your operating system.

***

### Enabling IPv6 During Order

During the checkout process, you can enable the option:

✔ IPv6 /64 Subnet

If enabled, the service will automatically receive an IPv6 subnet during deployment.

***

### If IPv6 Was Not Enabled During Order

{% stepper %}
{% step %}

### After delivery

Wait for your VPS or dedicated server to be delivered.
{% endstep %}

{% step %}

### Edit service

Go to your service in the customer area and click **Edit**.
{% endstep %}

{% step %}

### Enable IPv6 /64 Subnet

Enable **IPv6 /64 Subnet** and save.
{% endstep %}
{% endstepper %}

***

{% hint style="warning" %}
Important: First Deployment Behaviour

Sometimes, during the **first deployment**, the IPv6 block may not attach automatically. If your IPv6 /64 does not appear, try the steps below or wait a few seconds — the subnet often appears shortly after enabling it.

We recommend ALWAYS activating IPv6 after the service has been deployed, even if you selected it during checkout.
{% endhint %}

#### Fix — Toggle IPv6

{% stepper %}
{% step %}
Disable IPv6 and save.
{% endstep %}

{% step %}
Re-enable IPv6 and save again.
{% endstep %}
{% endstepper %}

#### Fix — Wait

The subnet usually appears a few seconds after enabling it.

***

### Accessing Your IPv6 Subnet

Once IPv6 is enabled, your /64 subnet appears in:

* VPS: <https://vps.upn.li>
* Dedicated servers: Customer Area → Server Details

UP-NETWORK automatically assigns the first IPv6 of the /64.

Example:

* Subnet: `2a0e:xxxx:yyyy:zz00::/64`
* Auto-assigned IP: `2a0e:xxxx:yyyy:zz00::1`

If the IP wasn’t assigned, follow the OS configuration below.

***

## Configuring IPv6 on Your Operating System

### Linux — Debian / Ubuntu

#### Netplan Configuration

File: `/etc/netplan/01-netcfg.yaml`

```yaml
network:
  version: 2
  renderer: networkd
  ethernets:
    ens18:
      addresses:
        - 2a0e:xxxx:yyyy:zz00::1/64
      gateway6: GTW_IP
      nameservers:
        addresses:
          - 2a0e:xxxx:yyyy:zz00::1
          - 2606:4700:4700::1111
```

Apply:

```bash
sudo netplan apply
```

***

#### ifupdown Configuration

File: `/etc/network/interfaces`

```
auto ens18
iface ens18 inet6 static
    address 2a0e:xxxx:yyyy:zz00::1
    netmask 64
    gateway GTW_IP
```

Restart:

```bash
systemctl restart networking
```

***

### Linux — RHEL / AlmaLinux / Rocky

File: `/etc/sysconfig/network-scripts/ifcfg-eth0`

```
IPV6INIT=yes
IPV6ADDR=2a0e:xxxx:yyyy:zz00::1/64
IPV6_DEFAULTGW=GTW_IP
DNS1=2606:4700:4700::1111
```

Apply:

```bash
nmcli connection reload
nmcli connection up eth0
```

***

### Windows Server

Open PowerShell:

```powershell
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress "2a0e:xxxx:yyyy:zz00::1" -PrefixLength 64 -DefaultGateway "GTW_IP"
```

Add DNS:

```powershell
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses "2a0e:xxxx:yyyy:zz00::1","2606:4700:4700::1111"
```

Verify:

```powershell
ipconfig
```

***

## Testing IPv6

Ping IPv6:

```bash
ping6 ipv6.google.com
```

Check outbound IPv6:

```bash
curl -6 ifconfig.co
```

If IPv6 does not work, check:

* Correct assigned IP
* Gateway (`fe80::1`)
* Netmask `/64`
* Firewall rules

***

<figure><img src="/files/uEV3GntLBVJePXWrxtKW" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ajcwB5Go2l66vlxZ6CFK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/oCnlTdOh7asYX4Ji9U5e" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/rbu4kXtOCo8MJzyqwqIR" alt=""><figcaption></figcaption></figure>

***

Summary

* IPv6 can be enabled during order or after service delivery.
* If the /64 subnet does not appear → disable IPv6, save, re-enable.
* The first IPv6 of the prefix is assigned automatically.
* Manual configuration is available for Linux and Windows.
* IPv6 testing tools are included at the end.


---

# 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.up-network.ch/documentation/guides/enabling-ipv6-on-your-service.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.