> ## Documentation Index
> Fetch the complete documentation index at: https://docs.advinservers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Networking and DDoS Manager

> How to view and manage the IP addresses on your virtual server, change its primary IP, and set DDoS filtering rules in the Ascienth console.

## Overview

Every virtual server has a "Networking" tab that lists the IP addresses assigned to it. From there you can see each address's netmask and gateway, choose which IPv4 address is the primary one, and add or remove [floating IPs](/guides/floating-ips).

Servers in our Nuremberg, DE location also have a "DDoS Protection" tab. It opens the DDoS Manager, where you can add filtering rules for each protected address. See [DDoS Protection](/information/ddosprotection) for what the protection covers.

Open the Ascienth console at [https://console.advinservers.com](https://console.advinservers.com), click your server, and then click the tab you need.

<Note>
  Team members can open the "Networking" tab with the `View servers` permission. Changing addresses needs `Change networking`. Buying an address needs `Make purchases`, and cancelling one needs `Make purchases` as well. The team owner can do all of these.
</Note>

## The Networking Tab

The table lists every address on the server, IPv4 and IPv6, with these columns:

| Column | What it shows |
| - | - |
| `Address` | The IP address. A floating IP that is set to cancel at the end of its billing period is marked `(Cancellation Pending)`. |
| `Netmask` | The netmask of the address. |
| `Gateway / Nexthop` | The gateway to use for the address. Routed addresses are labelled `Nexthop`. |
| `Status` | `Attached` once the address is live on the server. While something is changing it shows `Provisioning`, `Needs funds`, `Attaching`, `Detaching` or `Deleting`. |
| `Type` | `Primary IP`, `Secondary IP` or `Floating IP`. |

Use the search box to filter the list. The actions for an address are in the menu at the end of its row. Only the actions that apply to that address, and that your role allows, are shown.

To set a reverse DNS (PTR) record for an address, see [Reverse DNS](/guides/ptr-rdns).

## Changing the Primary IP

If your server has more than one IPv4 address, you can choose which one is primary. The primary address is the one the server is set up around.

<Steps>
  <Step title="Open the address menu">
    On the "Networking" tab, click the menu at the end of the IPv4 address you want to use, and choose `Set as Primary`.
  </Step>

  <Step title="Confirm">
    The "Set Primary Address" dialog asks you to confirm. Click `Confirm`.
  </Step>
</Steps>

We update the server's network settings straight away. If the server is running, we also try to apply the new address inside it so it keeps answering without a reboot. If that is not possible, for example because the server is powered off, the change takes effect the next time it boots.

<Warning>
  Only IPv4 addresses can be primary, and a floating IP can never be the primary address. To move a server off its current primary address, set another of its own IPv4 addresses as primary first.
</Warning>

Need a different address altogether? See our [IP Change](/guides/ipchange) policy.

## Adding an Address

You can add a floating IP to the server from this tab, either one you already rent or a new one.

<Steps>
  <Step title="Open the Add Address dialog">
    Click `Add Address` above the table.
  </Step>

  <Step title="Choose the address">
    Pick a floating IP from the `Address` menu. Only addresses that are not attached elsewhere and can reach this server are listed.

    To buy a new one instead, choose `Create a new floating IP`. Pick IPv4 or IPv6 under `Address type`. The `Price` field shows what the address costs. It is paid from your [account credit](/guides/account-credit).
  </Step>

  <Step title="Confirm">
    Click `Attach address` for an address you already have, or `Buy and attach` for a new one. The `Status` column shows `Attaching` until the address is on the server, then `Attached`. A new address is attached as soon as its payment goes through.
  </Step>
</Steps>

## Detaching or Cancelling a Floating IP

* `Detach` takes a floating IP off this server. The address stays yours and stays billed, so you can attach it to another server from the "Floating IPs" page. Anything still using it on this server stops responding.
* `Cancel address` ends the floating IP's subscription. See [Floating IPs](/guides/floating-ips#cancelling-an-address) for the choices.

To detach several floating IPs at once, tick their rows and click `Detach` in the bar that appears.

<Note>
  Only floating IPs can be detached. A primary address cannot be detached or cancelled immediately. Set another IPv4 address as primary first.
</Note>

## DDoS Manager

The DDoS Manager lets you add filtering rules to your protected addresses. It is only available for servers in our Nuremberg, DE location, and only for their protected IPv4 addresses. Read [DDoS Protection](/information/ddosprotection) for how the filtering works and which presets are offered.

Open your server and click the "DDoS Protection" tab. Pick the address to work on from the `IP Address` menu at the top. The table below it lists the rules on that address, with their `Protocol`, `Preset`, `Min Port`, `Max Port` and when they were `Created`.

<Note>
  Viewing the DDoS Manager needs the `View networking` permission. Creating rules and changing an address's settings need `Change networking`. Deleting rules needs `Delete networking resources`.
</Note>

### Creating a Rule

<Steps>
  <Step title="Open the dialog">
    Click `Create Rule`.
  </Step>

  <Step title="Pick the protocol and preset">
    Choose the `Protocol`: TCP, UDP, ICMP or GRE. Then choose a `Preset`. The list only shows presets for the protocol you picked.
  </Step>

  <Step title="Enter the ports">
    For TCP and UDP, enter the port in `Min Port`. To cover a range, also enter `Max Port (optional)`. If you leave it blank, the rule covers only the one port. Ports must be between 1 and 65535.
  </Step>

  <Step title="Create the rule">
    Click `Create`. The rule appears in the table.
  </Step>
</Steps>

To remove a rule, click the menu at the end of its row and choose `Delete`. You will be asked to type the rule's ID to confirm.

### Address Settings

The "IP Configuration" card below the rules holds two settings for the selected address:

| Setting | What it does |
| - | - |
| `Default Action` | What happens to traffic that does not match any rule: `Filter` or `Drop`. |
| `Mitigation Duration (seconds)` | How long automatic mitigation stays on after an attack is detected, from 10 to 600 seconds. |

Change them and click `Save Changes`.

<Warning>
  `Drop` discards all traffic to the address that does not match one of your rules. Make sure you have rules for every service you run before you choose it.
</Warning>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Why is there no DDoS Protection tab on my server?">
    The tab only appears for servers in Nuremberg, DE. Our other locations do not offer DDoS filtering. See [DDoS Protection](/information/ddosprotection).
  </Accordion>

  <Accordion title="Why can I not set my floating IP as the primary address?">
    A floating IP can be detached and moved at any time, so it cannot be the address the server is built around. Use one of the server's own IPv4 addresses as primary.
  </Accordion>

  <Accordion title="Why is the Set as Primary option missing?">
    It only appears for IPv4 addresses that belong to the server itself, when the server has more than one IPv4 address, and only if your role has the `Change networking` permission.
  </Accordion>

  <Accordion title="Does detaching a floating IP stop its billing?">
    No. A detached floating IP is still yours and is still billed. Cancel it from the row menu or the "Floating IPs" page to stop paying for it.
  </Accordion>
</AccordionGroup>

## Using the API

The server's addresses are part of the server details returned by the API. To change the primary address, use an API key with the `Change networking` permission (`network.update`):

```bash theme={null}
curl -X POST https://console.advinservers.com/api/v1/client/servers/<SERVER_ID>/addresses/<ADDRESS_ID>/primary \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Accept: application/json"
```

The DDoS Manager is under `/api/v1/client/servers/<SERVER_ID>/ddos-protection`. Reading it needs `network.read`, creating rules and changing settings need `network.update`, and deleting rules needs `network.delete`.

See the [API introduction](/api-reference/introduction) for how to create a key and for the full list of endpoints.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.