> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/networking/network-configuration/manual-configuration/manual-configuration-of-networking-on-debian-based-os.md).

# Manual configuration of networking on Debian based OS

In this guide we'll show you how you can easily configure your assigned IPs on your VPS running `ifupdown`.

### 1. Getting your networking details

Start by logging into our VPS Control Panel and clicking on the `Manage` button for the server that you would like to open the VNC Console for.

<figure><img src="https://2514707875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcU9MNuN6meCyYuRlFMOh%2Fuploads%2FYlfVT9dnyK5sdd1n32ui%2FCleanShot%202025-11-01%20at%2008.14.04%402x.png?alt=media&amp;token=6af32d9f-b207-4255-afc6-48dc052e8144" alt=""><figcaption></figcaption></figure>

Now, Go to the `Network` \[1] tab, and scroll down to fetch the following details:

* IPv4 Address \[2]
* IPv4 Gateway \[3]
* IPv4 Netmask \[4]
* IPv6 Address \[5]
* IPv6 Gateway \[6]

We also assign a /64 routed IPv6 address by default which you can freely use. We will cover adding 1 address from it but you can always assign more addresses by clicking on the `Assign Address` \[8] button then configuring it on your VM. Go ahead and grab your default routed IPv6 address from the panel \[7] as per the screenshot below.

<figure><img src="https://2514707875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcU9MNuN6meCyYuRlFMOh%2Fuploads%2FU56mLJf9DnAGlEAYgEoX%2FCleanShot%202026-03-13%20at%2012.49.18%402x.png?alt=media&amp;token=93b3bf87-01b0-4d10-8cd5-b1ff4c1ba356" alt=""><figcaption></figcaption></figure>

Now we have everything we need to configure networking on our VPS. Make sure you fetch your own address from your own panel and double check for any mistakes or included spaces.

### 2. Configuring the Network

Start by logging into your VPS and then run the following command:

```
nano /etc/network/interfaces
```

Now, Depending on the IPs from step 1., edit this file to look like this:

```
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address <IPv4 Address>
    netmask <IPv4 Netmask>
    dns-nameservers 1.1.1.1 9.9.9.9 2620:fe::fe 2620:fe::9
    gateway <IPv4 Gateway>

iface eth0 inet6 static
    address <IPv6 Address>
    gateway <IPv6 Gateway>

iface eth0 inet6 static
    address <IPv6 Routed Address>/64
```

Once done, Press `Ctrl` + `X` then `Y` and then press `Enter` to exit out of the file editor.

### 3. Checking for syntax errors

Run the following command to check for any syntax errors:

```
ifquery eth0
```

Your  output should look something like this:

<figure><img src="https://2514707875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcU9MNuN6meCyYuRlFMOh%2Fuploads%2FiaDPfydum2E3q0qHlMYy%2FCleanShot%202026-04-03%20at%2015.26.10%402x.png?alt=media&amp;token=05d5dd26-411b-4474-b8ce-3b301f2d869a" alt=""><figcaption></figcaption></figure>

### 4. Applying Changes

Next, to apply your new changes, reboot the server with the following command:

```
# reboot
```

And Done! Network should be working on your VPS now.


---

# 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://legacy.docs.synteq.com/networking/network-configuration/manual-configuration/manual-configuration-of-networking-on-debian-based-os.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.
