From 5bb95fbc5c31ee5af6d25de03ef9a110ebaa44ca Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 10 Feb 2026 15:59:27 +0100 Subject: [PATCH 01/12] New section - Managing public IP bandwidth on vRack Added new sections to the IPv4 and IPv6 guides for configuring an Additional IP in a vRack for Dedicated Servers. --- .../guide.en-gb.md | 55 +++++++++++++++++++ .../guide.en-gb.md | 55 +++++++++++++++++++ 2 files changed, 110 insertions(+) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index 5177a79def6..ecd4bd55191 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -204,6 +204,61 @@ Don't forget to configure SLAAC on your host machine. /// +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 100 Mbps. As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services. + +While the complimentary 100 Mbps option remains the default standard, OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-Region**. Since Additional IP services are regional, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular Region. + +/// details | During the Additional IP ordering process + +### Choosing bandwidth during an Additional IP order + +You can define your bandwidth requirements at the time of purchasing a new IP block. + +To order a new Additional IPv6 block: +- Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). +- Go to the `Bare Metal Cloud`{.action} section (or `Public Cloud`{.action}). +- Click on `Network`{.action} then `IP`{.action} in the left-hand sidebar. +- Click on the `Order`{.action} button and select `Additional IP`{.action}. +- In the configuration drop-down menus, select your **Service** (the vRack) and the desired **Region**. + +Once the vRack and Region are selected, the bandwidth options become available: +1. Click the `Modify bandwidth`{.action} button. +2. A new window will open on the right-hand side of your screen, listing all the available bandwidth options. +3. Select the desired bandwidth option, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. + +![Ordering bandwidth selection](images/placeholder){.thumbnail} + +/// + +/// details | From the vRack management page + +### Choosing bandwidth via the vRack management page + +For IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Open `vRack private network`{.action}. +- Select the vRack you wish to configure. + +The management page is organized into two tabs: +* **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. +* **Public IP routing**: Manages the public routing and performance of your Additional IPs. + +To modify the bandwidth: +1. Navigate to the `Public IP routing`{.action} tab. +2. The interface displays individual management windows for each Region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +3. Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +4. Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. + +![vRack bandwidth management](images/placeholder){.thumbnail} + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + #### Host-side commands /// details | Static IP configuration diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index b9638acf25d..0c5bfa43bbe 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -65,6 +65,61 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 100 Mbps. As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services. + +While the complimentary 100 Mbps option remains the default standard, OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-Region**. Since Additional IP services are regional, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular Region. + +/// details | During the Additional IP ordering process + +### Choosing bandwidth during an Additional IP order + +You can define your bandwidth requirements at the time of purchasing a new IP block. + +To order a new Additional IPv6 block: +- Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). +- Go to the `Bare Metal Cloud`{.action} section (or `Public Cloud`{.action}). +- Click on `Network`{.action} then `IP`{.action} in the left-hand sidebar. +- Click on the `Order`{.action} button and select `Additional IP`{.action}. +- In the configuration drop-down menus, select your **Service** (the vRack) and the desired **Region**. + +Once the vRack and Region are selected, the bandwidth options become available: +1. Click the `Modify bandwidth`{.action} button. +2. A new window will open on the right-hand side of your screen, listing all the available bandwidth options. +3. Select the desired bandwidth option, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. + +![Ordering bandwidth selection](images/placeholder){.thumbnail} + +/// + +/// details | From the vRack management page + +### Choosing bandwidth via the vRack management page + +For IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Open `vRack private network`{.action}. +- Select the vRack you wish to configure. + +The management page is organized into two tabs: +* **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. +* **Public IP routing**: Manages the public routing and performance of your Additional IPs. + +To modify the bandwidth: +1. Navigate to the `Public IP routing`{.action} tab. +2. The interface displays individual management windows for each Region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +3. Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +4. Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. + +![vRack bandwidth management](images/placeholder){.thumbnail} + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For [vRack](/links/network/vrack) purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: From b0170057746242cd0a41a95c752a2d5e3980def4 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 16 Feb 2026 15:13:56 +0100 Subject: [PATCH 02/12] update following feedback --- .../guide.en-gb.md | 40 +++++++++---------- .../guide.en-gb.md | 40 +++++++++---------- 2 files changed, 38 insertions(+), 42 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index ecd4bd55191..04a2bf776d5 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -206,27 +206,24 @@ Don't forget to configure SLAAC on your host machine. ### Managing public IP bandwidth on vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 100 Mbps. As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services. +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5Gbps in Europe/Canada/US and 100Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). -While the complimentary 100 Mbps option remains the default standard, OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-Region**. Since Additional IP services are regional, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular Region. +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. /// details | During the Additional IP ordering process -### Choosing bandwidth during an Additional IP order +#### Choosing public bandwidth during an Additional IP order -You can define your bandwidth requirements at the time of purchasing a new IP block. +The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. To order a new Additional IPv6 block: - Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). -- Go to the `Bare Metal Cloud`{.action} section (or `Public Cloud`{.action}). -- Click on `Network`{.action} then `IP`{.action} in the left-hand sidebar. -- Click on the `Order`{.action} button and select `Additional IP`{.action}. -- In the configuration drop-down menus, select your **Service** (the vRack) and the desired **Region**. - -Once the vRack and Region are selected, the bandwidth options become available: -1. Click the `Modify bandwidth`{.action} button. -2. A new window will open on the right-hand side of your screen, listing all the available bandwidth options. -3. Select the desired bandwidth option, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. +- Go to the `Network`{.action} section in the left-hand sidebar, then select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to you vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. ![Ordering bandwidth selection](images/placeholder){.thumbnail} @@ -234,24 +231,25 @@ Once the vRack and Region are selected, the bandwidth options become available: /// details | From the vRack management page -### Choosing bandwidth via the vRack management page +#### Modifying vRack public bandwidth on management page -For IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. To access the management interface: - Open `Network`{.action} in the left-hand sidebar of your Control Panel. - Open `vRack private network`{.action}. -- Select the vRack you wish to configure. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: * **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. * **Public IP routing**: Manages the public routing and performance of your Additional IPs. -To modify the bandwidth: -1. Navigate to the `Public IP routing`{.action} tab. -2. The interface displays individual management windows for each Region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -3. Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -4. Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. +To modify the public bandwidth: +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. ![vRack bandwidth management](images/placeholder){.thumbnail} diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 0c5bfa43bbe..1f0415694b5 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -67,27 +67,24 @@ Select your vRack from the list to display the list of eligible services. Click ### Managing public IP bandwidth on vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 100 Mbps. As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services. +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5Gbps in Europe/Canada/US and 100Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). -While the complimentary 100 Mbps option remains the default standard, OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-Region**. Since Additional IP services are regional, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular Region. +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. /// details | During the Additional IP ordering process -### Choosing bandwidth during an Additional IP order +#### Choosing public bandwidth during an Additional IP order -You can define your bandwidth requirements at the time of purchasing a new IP block. +The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. To order a new Additional IPv6 block: - Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). -- Go to the `Bare Metal Cloud`{.action} section (or `Public Cloud`{.action}). -- Click on `Network`{.action} then `IP`{.action} in the left-hand sidebar. -- Click on the `Order`{.action} button and select `Additional IP`{.action}. -- In the configuration drop-down menus, select your **Service** (the vRack) and the desired **Region**. - -Once the vRack and Region are selected, the bandwidth options become available: -1. Click the `Modify bandwidth`{.action} button. -2. A new window will open on the right-hand side of your screen, listing all the available bandwidth options. -3. Select the desired bandwidth option, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. +- Go to the `Network`{.action} section in the left-hand sidebar, then select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to you vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. ![Ordering bandwidth selection](images/placeholder){.thumbnail} @@ -95,24 +92,25 @@ Once the vRack and Region are selected, the bandwidth options become available: /// details | From the vRack management page -### Choosing bandwidth via the vRack management page +#### Modifying vRack public bandwidth on management page -For IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. To access the management interface: - Open `Network`{.action} in the left-hand sidebar of your Control Panel. - Open `vRack private network`{.action}. -- Select the vRack you wish to configure. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: * **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. * **Public IP routing**: Manages the public routing and performance of your Additional IPs. -To modify the bandwidth: -1. Navigate to the `Public IP routing`{.action} tab. -2. The interface displays individual management windows for each Region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -3. Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -4. Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to apply the selected bandwidth to your vRack. +To modify the public bandwidth: +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. ![vRack bandwidth management](images/placeholder){.thumbnail} From 8ad79e7d5bb1ad7bbcbabceed9480316f340b78b Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 16 Feb 2026 15:19:58 +0100 Subject: [PATCH 03/12] update following feedback - 2 --- .../configure-an-ipv6-in-a-vrack/guide.en-gb.md | 4 ++-- .../configuring-an-ip-block-in-a-vrack/guide.en-gb.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index 04a2bf776d5..effa8a5de29 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -241,8 +241,8 @@ To access the management interface: - In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: -* **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. -* **Public IP routing**: Manages the public routing and performance of your Additional IPs. +* **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +* **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. To modify the public bandwidth: - Navigate to the `Public IP routing`{.action} tab. diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 1f0415694b5..92e262b9f2d 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -102,8 +102,8 @@ To access the management interface: - In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: -* **All attached services**: Lists the products (Servers, Cloud Projects, etc.) currently linked to the vRack. -* **Public IP routing**: Manages the public routing and performance of your Additional IPs. +* **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +* **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. To modify the public bandwidth: - Navigate to the `Public IP routing`{.action} tab. From bb5cc8fc8257d8dd50d1fcec31f9e848ffc1f83c Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 16 Feb 2026 15:28:45 +0100 Subject: [PATCH 04/12] Update guide.en-gb.md --- .../configuring-an-ip-block-in-a-vrack/guide.en-gb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 92e262b9f2d..b760b033494 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -77,7 +77,7 @@ As infrastructure requirements scale, users may require broader bandwidth to sup The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. -To order a new Additional IPv6 block: +To order a new Additional IP block: - Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). - Go to the `Network`{.action} section in the left-hand sidebar, then select `Public IP addresses`{.action}. - Click on the `Order IPs`{.action} button, near the top of the page. From 0b3377082341a4b5a9bbb3729f51bf7e2edc404d Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 17 Feb 2026 16:49:05 +0100 Subject: [PATCH 05/12] typo + placeholder removal --- .../configuring-an-ip-block-in-a-vrack/guide.en-gb.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index b760b033494..8e1c88a2f8a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -83,11 +83,9 @@ To order a new Additional IP block: - Click on the `Order IPs`{.action} button, near the top of the page. - Select the IP version, then the vRack you want to attach your Additional IP to. - Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to you vRack for that specific region. +- Choose the public bandwidth you want to apply to your vRack for that specific region. - Fill in the other options as necessary, then proceed with your order. -![Ordering bandwidth selection](images/placeholder){.thumbnail} - /// /// details | From the vRack management page @@ -112,8 +110,6 @@ To modify the public bandwidth: - Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. - Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. -![vRack bandwidth management](images/placeholder){.thumbnail} - The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. /// From 557e37070b67aa8eae78f3163b90e77863ebb367 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 17 Feb 2026 16:49:49 +0100 Subject: [PATCH 06/12] typo + placeholder removal --- .../configure-an-ipv6-in-a-vrack/guide.en-gb.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index effa8a5de29..4eb532cd042 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -222,11 +222,9 @@ To order a new Additional IPv6 block: - Click on the `Order IPs`{.action} button, near the top of the page. - Select the IP version, then the vRack you want to attach your Additional IP to. - Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to you vRack for that specific region. +- Choose the public bandwidth you want to apply to your vRack for that specific region. - Fill in the other options as necessary, then proceed with your order. -![Ordering bandwidth selection](images/placeholder){.thumbnail} - /// /// details | From the vRack management page @@ -251,8 +249,6 @@ To modify the public bandwidth: - Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. - Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. -![vRack bandwidth management](images/placeholder){.thumbnail} - The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. /// From fb3d2e30ce8c90884e5a84cc0938deaef0deb167 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 23 Feb 2026 10:54:39 +0100 Subject: [PATCH 07/12] Cleanup + price pro-rata disclaimer --- .../configure-an-ipv6-in-a-vrack/guide.en-gb.md | 7 ++++++- .../configuring-an-ip-block-in-a-vrack/guide.en-gb.md | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index 4eb532cd042..5821c3a0500 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -208,7 +208,7 @@ Don't forget to configure SLAAC on your host machine. By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5Gbps in Europe/Canada/US and 100Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. /// details | During the Additional IP ordering process @@ -249,6 +249,11 @@ To modify the public bandwidth: - Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. - Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +> [!primary] +> +> Please note that charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. /// diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 8e1c88a2f8a..e7142b5eae7 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -69,7 +69,7 @@ Select your vRack from the list to display the list of eligible services. Click By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5Gbps in Europe/Canada/US and 100Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options for users requiring higher throughput. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. /// details | During the Additional IP ordering process @@ -110,6 +110,11 @@ To modify the public bandwidth: - Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. - Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +> [!primary] +> +> Please note that charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. /// From 764e90b6144561e6fa49890e99799479537d6daf Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Wed, 4 Mar 2026 12:21:12 +0100 Subject: [PATCH 08/12] small formulation edits small changes for uniformization. --- .../configure-an-ipv6-in-a-vrack/guide.en-gb.md | 5 +++-- .../configuring-an-ip-block-in-a-vrack/guide.en-gb.md | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index 5821c3a0500..dd16ed85f73 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -218,7 +218,8 @@ The default selection of public bandwidth can be modified at the order time of a To order a new Additional IPv6 block: - Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). -- Go to the `Network`{.action} section in the left-hand sidebar, then select `Public IP addresses`{.action}. +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. - Click on the `Order IPs`{.action} button, near the top of the page. - Select the IP version, then the vRack you want to attach your Additional IP to. - Select the region you want your Additional IP to be in. @@ -235,7 +236,7 @@ For Additional IP blocks already attached to a vRack, bandwidth can be managed d To access the management interface: - Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Open `vRack private network`{.action}. +- Select `vRack private network`{.action}. - In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index e7142b5eae7..29aaaaee26b 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -79,7 +79,8 @@ The default selection of public bandwidth can be modified at the order time of a To order a new Additional IP block: - Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). -- Go to the `Network`{.action} section in the left-hand sidebar, then select `Public IP addresses`{.action}. +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. - Click on the `Order IPs`{.action} button, near the top of the page. - Select the IP version, then the vRack you want to attach your Additional IP to. - Select the region you want your Additional IP to be in. @@ -96,7 +97,7 @@ For Additional IP blocks already attached to a vRack, bandwidth can be managed d To access the management interface: - Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Open `vRack private network`{.action}. +- Select `vRack private network`{.action}. - In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: From 011bebfafcd9862367fec0e0d7cc9c8ce9699eec Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 6 Mar 2026 14:58:50 +0100 Subject: [PATCH 09/12] Translation + links FR translation done. Links to the manager replaced. --- .../guide.en-gb.md | 2 +- .../guide.fr-fr.md | 55 +++++++++++++++++++ .../guide.en-gb.md | 2 +- .../guide.fr-fr.md | 55 +++++++++++++++++++ 4 files changed, 112 insertions(+), 2 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index dd16ed85f73..d72d34db7e5 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -217,7 +217,7 @@ As infrastructure requirements scale, users may require broader bandwidth to sup The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. To order a new Additional IPv6 block: -- Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). +- Log in to the [OVHcloud Control Panel](/links/manager). - Open the `Network`{.action} section in the left-hand sidebar. - Select `Public IP addresses`{.action}. - Click on the `Order IPs`{.action} button, near the top of the page. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md index 61fb0b1bf72..c8831a13db2 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md @@ -202,6 +202,61 @@ N'oubliez pas de configurer SLAAC sur votre machine hôte. /// +### Gérer la bande passante des IP publiques sur le vRack + +Par défaut, les blocs d'Additional IP routés via un vRack bénéficient d'une bande passante publique standard de 5 Gbps en Europe et en Amérique du Nord, ou de 100 Mbps dans les régions APAC. Pour plus de détails sur les offres disponibles, consultez les options de routage public sur notre [page produit vRack](/links/network/vrack). + +Pour répondre à la montée en charge des infrastructures et aux besoins des services à fort trafic, OVHcloud propose maintenant à ses clients des options de bande passante payantes. Notez que ces options s'appliquent **par vRack et par région**. Comme les Additional IP sont liées à une région précise, toute modification de la bande passante impactera l'ensemble des adresses (IPv4 et IPv6) routées vers ce vRack dans la région concernée. + +/// details | Lors de la commande d'une Additional IP + +#### Choisir la bande passante publique lors de la commande + +Vous pouvez modifier la bande passante par défaut au moment de commander un nouveau bloc d'Additional IP, dès lors qu'un réseau vRack est sélectionné comme service backend. + +Pour commander un nouveau bloc d'Additional IPv6 : +- Connectez-vous à [l'espace client OVHcloud](/links/manager). +- Dans la barre latérale gauche, accédez à la section `Network`{.action}. +- Sélectionnez `Adresses IP Publiques`{.action}. +- Cliquez sur le bouton `Commander des IPs`{.action} en haut de la page. +- Choisissez la version de l'IP, puis le vRack auquel l'Additional IP sera rattachée. +- Sélectionnez la région de votre Additional IP. +- Choisissez la bande passante publique à appliquer à votre vRack pour cette région. +- Configurez les autres options selon vos besoins, puis finalisez la commande. + +/// + +/// details | Depuis la page de gestion du vRack + +#### Modifier la bande passante publique depuis la page de gestion + +Pour les blocs d'Additional IP déjà rattachés à un vRack, la bande passante se gère directement depuis la page de configuration du service. + +Pour accéder à l'interface de gestion : +- Dans la barre latérale gauche du Tableau de bord, ouvrez `Network`{.action}. +- Sélectionnez `Réseau Privé vRack`{.action}. +- Dans la colonne "Adresse IP publique et bande passante", cliquez sur le bouton `Gérer`{.action} correspondant au vRack souhaité. + +L'interface de gestion se divise en deux onglets : +* **Tous les services attachés** : Redirige actuellement vers la page de gestion classique du vRack. Prochainement, cet onglet listera de façon optimisée tous les produits (serveurs, projets Cloud, etc.) liés au vRack. +* **Connectivité IP publique** : Permet de gérer les options de routage public de votre vRack, y compris la bande passante. + +Pour modifier la bande passante : +- Allez dans l'onglet `Connectivité IP publique`{.action}. +- L'interface affiche des fenêtres de gestion par région (ex: `eu-west-par`) associées au vRack, avec la liste des IP rattachées. +- Dans l'encadré de la région concernée, cliquez sur `Modifier la bande passante`{.action}. +- Sélectionnez l'option souhaitée dans le panneau de droite, puis cliquez sur `Commander`{.action} pour valider. +- Une fois le paiement effectué, la nouvelle bande passante sera effective sur votre vRack dans la région choisie après quelques minutes. + +> [!primary] +> +> Notez que le premier mois souscrit est facturé au prorata des jours restants. Le tarif complet s'appliquera lors du cycle de facturation suivant. +> + +L'augmentation de bande passante s'appliquera à toutes les adresses IP de cette région pour le vRack sélectionné. + +/// + #### Commandes sur l'hôte /// details | Configuration IP statique diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 29aaaaee26b..47b7ec5d72f 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -78,7 +78,7 @@ As infrastructure requirements scale, users may require broader bandwidth to sup The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. To order a new Additional IP block: -- Log in to the [OVHcloud Control Panel](https://www.ovh.com/manager). +- Log in to the [OVHcloud Control Panel](/links/manager). - Open the `Network`{.action} section in the left-hand sidebar. - Select `Public IP addresses`{.action}. - Click on the `Order IPs`{.action} button, near the top of the page. diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md index dbc0df18aa1..353932ef3a9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md @@ -65,6 +65,61 @@ Sélectionnez votre vRack dans la liste pour afficher la liste des services éli ![vrack](images/addIPblock.png){.thumbnail} +### Gérer la bande passante des IP publiques sur le vRack + +Par défaut, les blocs d'Additional IP routés via un vRack bénéficient d'une bande passante publique standard de 5 Gbps en Europe et en Amérique du Nord, ou de 100 Mbps dans les régions APAC. Pour plus de détails sur les offres disponibles, consultez les options de routage public sur notre [page produit vRack](/links/network/vrack). + +Pour répondre à la montée en charge des infrastructures et aux besoins des services à fort trafic, OVHcloud propose maintenant à ses clients des options de bande passante payantes. Notez que ces options s'appliquent **par vRack et par région**. Comme les Additional IP sont liées à une région précise, toute modification de la bande passante impactera l'ensemble des adresses (IPv4 et IPv6) routées vers ce vRack dans la région concernée. + +/// details | Lors de la commande d'une Additional IP + +#### Choisir la bande passante publique lors de la commande + +Vous pouvez modifier la bande passante par défaut au moment de commander un nouveau bloc d'Additional IP, dès lors qu'un réseau vRack est sélectionné comme service backend. + +Pour commander un nouveau bloc d'Additional IPv6 : +- Connectez-vous à [l'espace client OVHcloud](/links/manager). +- Dans la barre latérale gauche, accédez à la section `Network`{.action}. +- Sélectionnez `Adresses IP Publiques`{.action}. +- Cliquez sur le bouton `Commander des IPs`{.action} en haut de la page. +- Choisissez la version de l'IP, puis le vRack auquel l'Additional IP sera rattachée. +- Sélectionnez la région de votre Additional IP. +- Choisissez la bande passante publique à appliquer à votre vRack pour cette région. +- Configurez les autres options selon vos besoins, puis finalisez la commande. + +/// + +/// details | Depuis la page de gestion du vRack + +#### Modifier la bande passante publique depuis la page de gestion + +Pour les blocs d'Additional IP déjà rattachés à un vRack, la bande passante se gère directement depuis la page de configuration du service. + +Pour accéder à l'interface de gestion : +- Dans la barre latérale gauche du Tableau de bord, ouvrez `Network`{.action}. +- Sélectionnez `Réseau Privé vRack`{.action}. +- Dans la colonne "Adresse IP publique et bande passante", cliquez sur le bouton `Gérer`{.action} correspondant au vRack souhaité. + +L'interface de gestion se divise en deux onglets : +* **Tous les services attachés** : Redirige actuellement vers la page de gestion classique du vRack. Prochainement, cet onglet listera de façon optimisée tous les produits (serveurs, projets Cloud, etc.) liés au vRack. +* **Connectivité IP publique** : Permet de gérer les options de routage public de votre vRack, y compris la bande passante. + +Pour modifier la bande passante : +- Allez dans l'onglet `Connectivité IP publique`{.action}. +- L'interface affiche des fenêtres de gestion par région (ex: `eu-west-par`) associées au vRack, avec la liste des IP rattachées. +- Dans l'encadré de la région concernée, cliquez sur `Modifier la bande passante`{.action}. +- Sélectionnez l'option souhaitée dans le panneau de droite, puis cliquez sur `Commander`{.action} pour valider. +- Une fois le paiement effectué, la nouvelle bande passante sera effective sur votre vRack dans la région choisie après quelques minutes. + +> [!primary] +> +> Notez que le premier mois souscrit est facturé au prorata des jours restants. Le tarif complet s'appliquera lors du cycle de facturation suivant. +> + +L'augmentation de bande passante s'appliquera à toutes les adresses IP de cette région pour le vRack sélectionné. + +/// + ### Configurer une adresse IP utilisable Dans le cas du vRack, la première, l'avant-dernière et la dernière adresse d'un bloc d'IP donné sont toujours réservées respectivement à l'adresse réseau, la passerelle réseau et au *broadcast* du réseau. Cela signifie que la première adresse utilisable est la deuxième adresse du bloc, comme indiqué ci-dessous : From 8653a6173d43b8a00dbd31893d2f0d1107f51a16 Mon Sep 17 00:00:00 2001 From: benchbzh Date: Mon, 9 Mar 2026 15:26:35 +0100 Subject: [PATCH 10/12] proofreading, translation & duplication --- .../guide.de-de.md | 74 +++- .../guide.en-asia.md | 74 +++- .../guide.en-au.md | 74 +++- .../guide.en-ca.md | 74 +++- .../guide.en-gb.md | 29 +- .../guide.en-ie.md | 74 +++- .../guide.en-sg.md | 74 +++- .../guide.en-us.md | 74 +++- .../guide.es-es.md | 74 +++- .../guide.es-us.md | 74 +++- .../guide.fr-ca.md | 78 ++++- .../guide.fr-fr.md | 33 +- .../guide.it-it.md | 74 +++- .../guide.pl-pl.md | 74 +++- .../guide.pt-pt.md | 74 +++- .../guide.de-de.md | 320 ++++++++++++++--- .../guide.en-asia.md | 235 ++++++++++++- .../guide.en-au.md | 232 ++++++++++++- .../guide.en-ca.md | 232 ++++++++++++- .../guide.en-gb.md | 63 ++-- .../guide.en-ie.md | 232 ++++++++++++- .../guide.en-sg.md | 230 ++++++++++++- .../guide.en-us.md | 230 ++++++++++++- .../guide.es-es.md | 316 ++++++++++++++--- .../guide.es-us.md | 316 ++++++++++++++--- .../guide.fr-ca.md | 251 +++++++++++++- .../guide.fr-fr.md | 198 ++++++++++- .../guide.it-it.md | 318 ++++++++++++++--- .../guide.pl-pl.md | 322 +++++++++++++++--- .../guide.pt-pt.md | 308 ++++++++++++++--- 30 files changed, 4271 insertions(+), 560 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md index 61d95139519..0833871bbcc 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack (EN) +title: Einen Additional IPv6-Block in einem vRack konfigurieren (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack -updated: 2025-06-04 +updated: 2026-03-09 --- + ## Einleitung -Neben Private IP Addressing ist es mit dem [vRack](/links/network/vrack) auch möglich, mithilfe eines öffentlichen IP-Adressblocks den öffentlichen IP-Traffic über den vRack Port Ihres Servers zu routen. +Neben der privaten IP-Adressierung ermöglicht das [vRack](/links/network/vrack) auch die Weiterleitung von öffentlichem IP-Verkehr über den vRack-Port Ihres Servers mithilfe eines öffentlichen IP-Adressblocks. -**In dieser Anleitung erfahren Sie, wie Sie einen öffentlichen IP-Adressblock so konfigurieren, dass Sie ihn mit dem vRack verwenden können.** +**In dieser Anleitung erfahren Sie, wie Sie einen Block öffentlicher IP-Adressen für die Verwendung mit dem vRack konfigurieren.** > [!primary] > -> vRack unterstützt Routing für IPv4 und IPv6 Additional IP Blöcke. Details zur Konfiguration von IPv6 finden Sie in dieser Anleitung: [Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack). +> Das vRack unterstützt sowohl IPv4- als auch IPv6-öffentliches Routing mit Additional IP-Adressblöcken. Die Anleitung zur Konfiguration von IPv6-Blöcken finden Sie hier: "[Konfiguration eines IPv6-Blocks in einem vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Dieser Artikel erklärt die Konfiguration von Additional IP über ein vRack Netzwerk. Weitere Informationen zur Konfiguration mit der primären IP (über die Schnittstelle des öffentlichen Netzwerks) finden Sie in den folgenden Anleitungen: +> Dieser Artikel befasst sich mit der Konfiguration von Additional IP über ein vRack-Netzwerk. Wenn Sie Anleitungen zur Konfiguration von Additional IP zusammen mit der primären IP (auf der öffentlichen Netzwerkschnittstelle) suchen, lesen Sie die folgenden Artikel: > > - IPv4: -> - [Konfiguration von IP-Aliasing](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing) -> - [IP-Adresse als Alias auf einem VPS konfigurieren](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing) +> - [Konfiguration von IP-Aliasing auf dedizierten Servern](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Konfiguration von IP-Aliasing auf einem VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [IPv6 auf einem Dedicated Server konfigurieren](/pages/bare_metal_cloud/dedicated_servers/network_ipv6) -> - [IPv6 auf einem VPS einrichten](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6) -> - [IPv6 auf einer Public Cloud Instanz konfigurieren](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6) +> - [Konfiguration von IPv6 auf dedizierten Servern](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Konfiguration von IPv6 auf einem VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Konfiguration von IPv6 auf einer Public Cloud Instanz](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Voraussetzungen -- Sie haben einen öffentlichen IP-Adressblock mit mindestens vier Adressen in Ihrem Account reserviert. -- Sie haben den gewünschten privaten IP-Adressbereich vorbereitet. -- Sie verfügen über einen mit vRack kompatiblen [Dedicated Server](/links/bare-metal/bare-metal). -- Sie haben einen [vRack](/links/network/vrack) Dienst aktiviert. -- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager). +- Sie verfügen über einen öffentlichen IP-Adressblock in Ihrem Account mit mindestens vier Adressen. +- Sie haben Ihren gewünschten privaten IP-Adressbereich festgelegt. +- Sie verfügen über einen [vRack-kompatiblen Server](/links/bare-metal/bare-metal). +- Sie haben den [vRack](/links/network/vrack)-Dienst in Ihrem Account aktiviert. +- Sie haben Zugang zum [OVHcloud Kundencenter](/links/manager). > [!warning] -> Diese Funktion kann nur eingeschränkt oder nicht verfügbar sein, falls ein Dedicated Server der [**Eco** Produktlinie](/links/bare-metal/eco-about) eingesetzt wird. +> Diese Funktion kann auf Dedicated Server der [**Eco** Produktlinie](/links/bare-metal/eco-about) nicht verfügbar oder eingeschränkt sein. > -> Weitere Informationen finden Sie auf der [Vergleichsseite](/links/bare-metal/eco-compare). +> Weitere Informationen finden Sie auf unserer [Vergleichsseite](/links/bare-metal/eco-compare). ## In der praktischen Anwendung > [!primary] > -> In der vorliegenden Anleitung verwenden wir als Beispiel den IP-Block 46.105.135.96/28 sowie `eth1` als sekundäres Netzwerk, das dem vRack zugewiesen ist. +> Als Beispiel verwenden wir einen IP-Block von 46.105.135.96/28 und eth1 für die sekundäre Netzwerkschnittstelle, die dem vRack gewidmet ist. > -> Ebenfalls nur als Beispiel: Die Netzwerkkonfigurationsdatei, auf die wir uns beziehen, befindet sich unter `/etc/network/interfaces`. Je nach verwendetem Betriebssystem kann sich die entsprechende Datei an anderer Stelle befinden. Auch der Inhalt der Datei kann unterschiedlich sein. Für Details können Sie die offizielle Dokumentation Ihrer Distribution zu Rate ziehen. +> Als Beispiel befindet sich die Netzwerkkonfigurationsdatei, auf die wir verweisen, unter `/etc/network/interfaces`. Die entsprechende Datei auf Ihrem Server kann sich je nach Betriebssystem an einem anderen Ort befinden. Der Dateiinhalt kann ebenfalls abweichen. Bei Schwierigkeiten konsultieren Sie bitte die offizielle Dokumentation Ihrer Distribution. -### IP-Block zum vRack hinzufügen +### Den IP-Block zum vRack hinzufügen > [!warning] > -> Wenn ein IP-Block zum vRack hinzugefügt wird, ist er nicht mehr an einen physischen Server gebunden. +> Sobald ein IP-Block zum vRack hinzugefügt wird, ist er nicht mehr mit einem physischen Server verbunden. > -> Mit dieser Konfiguration können IP-Adressen eines Blocks auf mehreren Servern konfiguriert werden, sofern sich alle Server im selben vRack befinden wie der IP-Block. Der IP-Block muss über mindestens 2 IP-Adressen oder mehr verfügen, damit dies möglich ist. +> Dieses Setup ermöglicht es Ihnen, IPs desselben Blocks auf mehreren Servern zu konfigurieren, vorausgesetzt, dass sich alle Server im selben vRack wie der IP-Block befinden. Der IP-Block muss mindestens 2 nutzbare IPs oder mehr haben, damit dies möglich ist. > -Gehen Sie in Ihrem [OVHcloud Kundencenter](/links/manager) in den Bereich `Bare Metal Cloud`{.action} und klicken Sie auf `Network`{.action}. Öffnen Sie anschließend das Menü `vRack`{.action}. +Gehen Sie in Ihrem [OVHcloud Kundencenter](/links/manager) zum Bereich `Bare Metal Cloud`{.action} und klicken Sie auf `Network`{.action}. Öffnen Sie anschließend das Menü `vRack`{.action}. -Wählen Sie in der Liste Ihr vRack aus, um die Liste der verfügbaren Dienstleistungen anzuzeigen. Klicken Sie auf den IP-Block, den Sie zum vRack hinzufügen möchten, und klicken Sie auf den Button `Hinzufügen`{.action}. +Wählen Sie Ihr vRack aus der Liste aus, um die Liste der berechtigten Dienste anzuzeigen. Klicken Sie auf den IP-Block, den Sie zum vRack hinzufügen möchten, und klicken Sie auf die Schaltfläche `Hinzufügen`{.action}. ![vrack](images/addIPblock.png){.thumbnail} -### Eine verwendbare IP-Adresse konfigurieren +### Öffentliche IP-Bandbreite im vRack verwalten + +Standardmäßig profitieren Additional IP-Blöcke, die über ein vRack geroutet werden, von einer Standard-Öffentlichbandbreite von 5 Gbps in Europa/Kanada/USA und 100 Mbps in APAC-Regionen. Eine detaillierte Übersicht der Verfügbarkeit finden Sie in den öffentlichen Routing-Optionen auf unserer [vRack-Produktseite](/links/network/vrack). + +Mit wachsenden Infrastrukturanforderungen benötigen Nutzer möglicherweise eine größere Bandbreite zur Unterstützung von hochfrequentierten öffentlich ausgerichteten Diensten, für die OVHcloud kostenpflichtige Bandbreitenoptionen bereitstellt. Es ist wichtig zu beachten, dass Bandbreitenoptionen **pro vRack und pro Region** angewendet werden. Da Additional IP-Adressen an eine Region gebunden sind, wirkt sich jede Bandbreitenänderung auf alle IP-Adressen (sowohl IPv4 als auch IPv6) aus, die zum spezifischen vRack in dieser bestimmten Region geroutet werden. + +/// details | Während des Additional IP-Bestellvorgangs + +#### Öffentliche Bandbreite bei einer Additional IP-Bestellung auswählen + +Die Standard-Öffentlichbandbreite kann geändert werden, wenn Sie einen neuen Additional IP-Block mit einem vRack-Netzwerk als Backend bestellen. + +So bestellen Sie einen neuen Additional IP-Block: + +- Melden Sie sich im [OVHcloud Kundencenter](/links/manager) an. +- Öffnen Sie den Bereich `Network`{.action} in der linken Seitenleiste. +- Wählen Sie `Öffentliche IP-Adressen`{.action}. +- Klicken Sie auf die Schaltfläche `IPs bestellen`{.action} nahe der Oberseite der Seite. +- Wählen Sie die IP-Version und dann das vRack aus, an das Sie Ihre Additional IP anhängen möchten. +- Wählen Sie die Region, in der Ihre Additional IP sein soll. +- Wählen Sie die öffentliche Bandbreite, die Sie für Ihr vRack in dieser spezifischen Region anwenden möchten. +- Füllen Sie die übrigen Optionen nach Bedarf aus und führen Sie dann Ihre Bestellung durch. + +/// + +/// details | Von der vRack-Verwaltungsseite + +#### Öffentliche vRack-Bandbreite auf der Verwaltungsseite ändern + +Für Additional IP-Blöcke, die bereits an ein vRack angehängt sind, kann die Bandbreite direkt über die Dienstkonfigurationsseite verwaltet werden. + +So greifen Sie auf die Verwaltungsoberfläche zu: -Beim vRack sind die erste, die vorletzte und die letzte Adresse eines gegebenen IP-Blocks immer jeweils für die Netzwerkadresse, das Netzwerk-Gateway sowie für den Netzwerk-*Broadcast* reserviert. Das heißt, die erste verwendbare Adresse ist die zweite Adresse des Blocks, wie im Folgenden zu sehen ist: +- Öffnen Sie `Network`{.action} in der linken Seitenleiste Ihres Kundencenters. +- Wählen Sie `Das private Netzwerk vRack`{.action}. +- Klicken Sie in der Spalte "Public IP & bandwidth" auf die Schaltfläche `Verwalten`{.action} für das entsprechende vRack. + +Die Verwaltungsseite ist in zwei Tabs unterteilt: +- **All attached services**: Derzeit leitet es zur klassischen vRack-Verwaltungsseite weiter. In Kürze werden dort alle Produkte (Server, Cloud-Projekte usw.), die derzeit mit dem vRack verknüpft sind, auf neue Weise aufgelistet. +- **Public IP Routing**: Verwaltet die öffentlichen IP-Routing-Optionen Ihres vRack, einschließlich der öffentlichen Bandbreite. + +So ändern Sie die öffentliche Bandbreite: + +- Navigieren Sie zum Tab `Public IP Routing`{.action}. +- Die Oberfläche zeigt individuelle Verwaltungsfenster für jede Region (z. B. `eu-west-par`) an, die mit dem vRack verknüpft ist, und listet alle IP-Adressen auf, die mit dieser spezifischen Region verbunden sind. +- Klicken Sie im Fenster für die betreffende Region auf die Schaltfläche `Bandbreite ändern`{.action}. +- Wählen Sie die gewünschte Bandbreitenoption im Panel, das auf der rechten Seite erscheint, und klicken Sie dann auf `Zur Bestellung`{.action}, um die Bestellung zu bestätigen. +- Nach der Zahlung sollte die ausgewählte Bandbreite nach einigen Minuten für Ihr vRack in der gewählten Region verfügbar sein. + +> [!primary] +> +> Die Gebühren für den ersten Monat werden anteilig auf der Grundlage der verbleibenden Tage berechnet, wobei der volle Tarif im nächsten Abrechnungszyklus gilt. +> + +Das ausgewählte Bandbreiten-Upgrade gilt für alle IP-Adressen in dieser Region für das gewählte vRack. + +/// + +### Eine nutzbare IP-Adresse konfigurieren + +Für vRack-Zwecke sind die erste, vorletzte und letzte Adresse in einem IP-Block immer für die Netzwerkadresse, das Netzwerk-Gateway und den Netzwerk-Broadcast reserviert. Das bedeutet, dass die erste nutzbare Adresse die zweite Adresse im Block ist, wie unten gezeigt: ```sh 46.105.135.96 # Reserviert: Netzwerkadresse -46.105.135.97 # Erste verwendbare IP +46.105.135.97 # Erste nutzbare IP 46.105.135.98 46.105.135.99 46.105.135.100 @@ -83,18 +155,20 @@ Beim vRack sind die erste, die vorletzte und die letzte Adresse eines gegebenen 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Letzte verwendbare IP -46.105.135.110 # Reserviert: Netzwerk-Gateway -46.105.135.111 # Reserviert: Netzwerk-Broadcast +46.105.135.109 # Letzte nutzbare IP +46.105.135.110 # Reserviert: Netzwerk-Gateway +46.105.135.111 # Reserviert: Netzwerk-Broadcast ``` -Um die erste verwendbare IP-Adresse zu konfigurieren, bearbeiten Sie die Netzwerkkonfigurationsdatei wie im Folgenden beschrieben. In unserem Beispiel verwenden wir **255.255.255.240** als Subnetzmaske. +Um die erste nutzbare IP-Adresse zu konfigurieren, müssen wir die Netzwerkkonfigurationsdatei bearbeiten, wie unten gezeigt. In diesem Beispiel müssen wir eine Subnetzmaske von *255.255.255.240* verwenden. > [!primary] > -> Die von uns in diesem Beispiel verwendete Subnetzmaske passt zu unserem IP-Block. Ihre Subnetzmaske kann je nach Größe Ihres Blocks variieren. Wenn Sie Ihren IP-Block kaufen, erhalten Sie eine E-Mail mit der zu verwendenden Subnetzmaske. +> Die in unserem Beispiel verwendete Subnetzmaske ist für unseren IP-Block geeignet. Ihre Subnetzmaske kann je nach Größe Ihres Blocks abweichen. Beim Kauf Ihres IP-Blocks erhalten Sie eine E-Mail, die Ihnen mitteilt, welche Subnetzmaske Sie verwenden müssen. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -104,39 +178,43 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` +### Eine neue IP-Routing-Tabelle erstellen -### Neue IP-Routing-Tabelle erstellen +Zunächst müssen wir iproute2 herunterladen und installieren, ein Paket, das es uns ermöglicht, das IP-Routing auf dem Server manuell zu konfigurieren. -Wir empfehlen Ihnen, zuerst “iproute2” herunterzuladen und zu installieren. Mit diesem Paket ist es möglich, das IP-Routing auf dem Server manuell zu konfigurieren. - -Stellen Sie eine SSH-Verbindung zu Ihrem Server her und verwenden Sie folgenden Befehl, um das Paket herunterzuladen und zu installieren. +Stellen Sie eine SSH-Verbindung zu Ihrem Server her und führen Sie den folgenden Befehl über die Befehlszeile aus. Damit wird iproute2 heruntergeladen und installiert. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -Erstellen Sie anschließend eine neue IP-Route für das vRack. Hierzu empfehlen wir, eine neue Traffic-Regel hinzuzufügen, indem Sie die Datei wie folgt bearbeiten: +Als nächstes müssen wir eine neue IP-Route für das vRack erstellen. Wir fügen eine neue Verkehrsregel hinzu, indem wir die Datei wie folgt ergänzen: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# reservierte Werte +# 255 local 254 main 253 default 0 unspec -# # # -# local -# # # +# +# lokal +# #1 inr.ruhep 1 vrack ``` -### Netzwerkkonfigurationsdatei bearbeiten +### Die Netzwerkkonfigurationsdatei anpassen -Um den Vorgang abzuschließen, muss nun noch die Netzwerkkonfigurationsdatei bearbeitet werden, damit die neue Traffic-Regel umgesetzt und der vRack Traffic über die Netzwerk-Gateway-Adresse **46.105.135.110** geleitet wird. +> [!primary] +> +> Als Beispiel befindet sich die Netzwerkkonfigurationsdatei, auf die wir verweisen, unter /etc/network/interfaces. Die entsprechende Datei auf Ihrem Server kann sich je nach Betriebssystem an einem anderen Ort befinden. +> + +Schließlich müssen wir die Netzwerkkonfigurationsdatei anpassen, um die neue Verkehrsregel zu berücksichtigen und den vRack-Verkehr über die Netzwerk-Gateway-Adresse **46.105.135.110** zu routen. ```sh /etc/network/interfaces @@ -152,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Starten Sie jetzt den Server neu, um die Änderungen anzuwenden. +Starten Sie nun Ihren Server neu, um die Änderungen zu übernehmen, oder aktivieren Sie alternativ einfach die neue Netzwerkschnittstelle: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Die Datei für die sekundäre Netzwerkschnittstelle erstellen + +Zunächst können wir die Konfiguration der primären Netzwerkschnittstelle kopieren und nach unseren Bedürfnissen anpassen: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Dann öffnen wir die neue Datei: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Und wir definieren die IP-Einstellungen: +```sh +# Automatisch beim Instanzstart durch cloud-init erstellt, nicht bearbeiten. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Eine neue IP-Routing-Tabelle erstellen + +Als nächstes müssen wir eine neue IP-Route für das vRack erstellen. Wir fügen eine neue Verkehrsregel hinzu, indem wir die Datei wie folgt ergänzen: + +```sh +/etc/iproute2/rt_tables + +# +# reservierte Werte +# +255 local +254 main +253 default +0 unspec +# +# lokal +# +#1 inr.ruhep +1 vrack +``` + +Als nächstes erstellen wir die Datei, die zum Anwenden der neuen Regeln benötigt wird: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +Und fügen den folgenden Inhalt ein (denken Sie daran, unsere Variablen durch Ihre eigenen Werte zu ersetzen): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Die Netzwerkkonfigurationsdatei anpassen + +Schließlich müssen wir die Netzwerkkonfigurationsdatei anpassen, um die neue Verkehrsregel zu berücksichtigen und den vRack-Verkehr über die Netzwerk-Gateway-Adresse **46.105.135.110** zu routen. + +Dazu bearbeiten wir die folgende Datei, um persistente und statische Routen hinzuzufügen: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Fügen Sie den folgenden Inhalt ein (denken Sie daran, unsere Variablen durch Ihre eigenen Werte zu ersetzen): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Starten Sie nun Ihren Server neu, um die Änderungen zu übernehmen, oder aktivieren Sie alternativ einfach die neue Netzwerkschnittstelle: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Schritt 1: Die sekundäre Netzwerkschnittstelle prüfen und konfigurieren + +Zunächst müssen wir auf die Informationen der neuen Netzwerkschnittstelle zugreifen: + +![die zweite Netzwerkschnittstelle prüfen](images/win-ip-vrack-1.png){.thumbnail} + +Anschließend müssen wir die Eigenschaften prüfen: + +![Eigenschaften der zweiten Netzwerkschnittstelle](images/win-ip-vrack-2.png){.thumbnail} + +![Eigenschaften der zweiten Netzwerkschnittstelle](images/win-ip-vrack-3.png){.thumbnail} + +#### Schritt 2: IP-Konfiguration + +Wir müssen die Option ```Use the following IP address``` auswählen: + +![IP-Konfiguration](images/win-ip-vrack-4.png){.thumbnail} + +Und wir können schließlich die IP-Informationen festlegen: + +![IP-Konfiguration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Schritt 3: Neustart der Netzwerkschnittstelle + +Zunächst deaktivieren wir die Schnittstelle: + +![Netzwerk deaktivieren](images/win-ip-vrack-6.png){.thumbnail} + +Dann aktivieren wir sie wieder: + +![Netzwerk aktivieren](images/win-ip-vrack-7.png){.thumbnail} + +### Fehlersuche + +Wenn Sie keine Verbindung von Ihrer VM oder Ihrem Server zum privaten Netzwerk herstellen können, senden Sie uns bitte ein Ticket über Ihr Kundencenter mit folgenden Angaben: + +- Quell-IP und Ziel-IP +- Ifconfig -a oder ipconfig /all von beiden Servern oder VMs (Setup der Netzwerkkonfigurationsschnittstelle) +- Ping in beide Richtungen +- Arp -a +- Routing-Tabelle + +Bitte fügen Sie die Ergebnisse der oben genannten Punkte in Ihr Ticket ein. ## Weiterführende Informationen -[Mehrere dedizierte Server im vRack konfigurieren](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Konfiguration des vRack auf Ihren dedizierten Servern](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Mehrere VLANs im vRack erstellen](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Mehrere VLANs in einem vRack erstellen](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) -[vRack zwischen Public Cloud und Dedicated Server einrichten](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) +[Das vRack zwischen der Public Cloud und einem dedizierten Server konfigurieren](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Für den Austausch mit unserer User Community gehen Sie auf . +Treten Sie unserer [User Community](/links/community) bei. diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-asia.md index bba48ccb506..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-asia.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -33,9 +47,9 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - A public block of IP addresses in your account, with a minimum of four addresses - Your chosen private IP address range -- A [vRack compatible server](https://www.ovh.com/asia/dedicated-servers/) +- A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account -- Access to the OVHcloud [Control Panel](/links/manager) +- Access to the [OVHcloud Control Panel](/links/manager) > [!warning] > This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -135,6 +209,11 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf ### Amend the network configuration file +> [!primary] +> +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> + Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. ```sh @@ -151,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-au.md index 9891445391f..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-au.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -33,9 +47,9 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - A public block of IP addresses in your account, with a minimum of four addresses - Your chosen private IP address range -- A [vRack compatible server](https://www.ovh.com.au/dedicated-servers/) +- A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account -- Access to the OVHcloud [Control Panel](/links/manager) +- Access to the [OVHcloud Control Panel](/links/manager) > [!warning] > This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -137,7 +211,7 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. @@ -156,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ca.md index adca6586642..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ca.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -33,9 +47,9 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - A public block of IP addresses in your account, with a minimum of four addresses - Your chosen private IP address range -- A [vRack compatible server](/links/network/vrack) +- A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account -- Access to the OVHcloud [Control Panel](/links/manager) +- Access to the [OVHcloud Control Panel](/links/manager) > [!warning] > This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -137,7 +211,7 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. @@ -156,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md index 47b7ec5d72f..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-gb.md @@ -1,14 +1,28 @@ --- title: 'Configuring an Additional IP block in a vRack' excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' -updated: 2025-06-04 +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. -**This guide will show you how to configure a block of public IP addresses for use with the [vRack](/links/network/vrack).** +**This guide will show you how to configure a block of public IP addresses for use with the vRack.** > [!primary] > @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -67,7 +81,7 @@ Select your vRack from the list to display the list of eligible services. Click ### Managing public IP bandwidth on vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5Gbps in Europe/Canada/US and 100Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. @@ -75,9 +89,10 @@ As infrastructure requirements scale, users may require broader bandwidth to sup #### Choosing public bandwidth during an Additional IP order -The default selection of public bandwidth can be modified at the order time of a new Additional IP block, when a vRack network is selected as a backend service. +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. To order a new Additional IP block: + - Log in to the [OVHcloud Control Panel](/links/manager). - Open the `Network`{.action} section in the left-hand sidebar. - Select `Public IP addresses`{.action}. @@ -96,15 +111,17 @@ To order a new Additional IP block: For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. To access the management interface: + - Open `Network`{.action} in the left-hand sidebar of your Control Panel. - Select `vRack private network`{.action}. - In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. The management page is organized into two tabs: -* **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -* **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. To modify the public bandwidth: + - Navigate to the `Public IP routing`{.action} tab. - The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. - Within the window for the relevant region, click the `Modify bandwidth`{.action} button. @@ -113,7 +130,7 @@ To modify the public bandwidth: > [!primary] > -> Please note that charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. > The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. @@ -122,7 +139,7 @@ The selected bandwidth upgrade will apply to all IP addresses in that region for ### Configure a usable IP address -For [vRack](/links/network/vrack) purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: +For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: ```sh 46.105.135.96 Reserved: Network address @@ -147,10 +164,10 @@ To configure the first usable IP address, we need to edit the network configurat > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > -###Debian/Ubuntu +### Debian/Ubuntu ```sh /etc/network/interfaces @@ -171,7 +188,7 @@ Establish an SSH connection to your server and run the following command from th # apt-get install iproute2 ``` -Next, we need to create a new IP route for the [vRack](/links/network/vrack). We'll be adding a new traffic rule by amending the file, as shown below: +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: ```sh /etc/iproute2/rt_tables @@ -194,10 +211,10 @@ Next, we need to create a new IP route for the [vRack](/links/network/vrack). We > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > -Finally, we need to amend the network configuration file to account for the new traffic rule and route the [vRack](/links/network/vrack) traffic through the network gateway address of **46.105.135.110**. +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. ```sh /etc/network/interfaces @@ -251,7 +268,7 @@ ARP=yes ### Create a new IP routing table -Next, we need to create a new IP route for the [vRack](/links/network/vrack). We'll be adding a new traffic rule by amending the file, as shown below: +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: ```sh /etc/iproute2/rt_tables @@ -284,7 +301,7 @@ to 46.105.135.96/28 table vrack ### Amend the network configuration file -Finally, we need to amend the network configuration file to account for the new traffic rule and route the [vRack](/links/network/vrack) traffic through the network gateway address of **46.105.135.110**. +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. We can achieve it by editing the following file in order to add persistent and static routes: @@ -321,7 +338,7 @@ Then we must check the properties: #### Step 2: IP Configuration -We must select the ```Use the following IP address``` option: +We must select the `Use the following IP address`{.action} option: ![ip configuration](images/win-ip-vrack-4.png){.thumbnail} @@ -343,11 +360,11 @@ Then we do the enabling process If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : -* IP source and IP destination -* Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) -* ping in both ways -* arp -a -* Routing table +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table Please, include the results from above into your ticket. diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ie.md index 5d98e379670..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-ie.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -33,7 +47,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - A public block of IP addresses in your account, with a minimum of four addresses - Your chosen private IP address range -- A [vRack compatible server](https://www.ovh.ie/dedicated_servers/) +- A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account - Access to the [OVHcloud Control Panel](/links/manager) @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -137,7 +211,7 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. @@ -156,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further @@ -166,4 +376,4 @@ Now reboot your server to apply the changes. [Configuring the vRack between the Public Cloud and a Dedicated Server](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-sg.md index 344770cd0e0..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-sg.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -33,7 +47,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - A public block of IP addresses in your account, with a minimum of four addresses - Your chosen private IP address range -- A [vRack compatible server](https://www.ovh.com/sg/dedicated-servers/) +- A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account - Access to the [OVHcloud Control Panel](/links/manager) @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -137,7 +211,7 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. @@ -156,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-us.md index 9affe5c589f..a25b8735c0a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.en-us.md @@ -1,12 +1,26 @@ --- -title: Configuring an IP block in a vRack -excerpt: This guide will show you how to configure a block of public IP addresses for use with the vRack. -updated: 2025-06-04 +title: 'Configuring an Additional IP block in a vRack' +excerpt: 'This guide will show you how to configure a block of public IP addresses for use with the vRack.' +updated: 2026-03-09 --- + + ## Objective -As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's [vRack](/links/network/vrack) port using a public IP address block. +As well as private IP addressing, the [vRack](/links/network/vrack) also allows you to route public IP traffic through your server's vRack port using a public IP address block. **This guide will show you how to configure a block of public IP addresses for use with the vRack.** @@ -35,7 +49,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows - Your chosen private IP address range - A [vRack compatible server](/links/bare-metal/bare-metal) - A [vRack](/links/network/vrack) service activated in your account -- Access to the OVHcloud [Control Panel](/links/manager) +- Access to the [OVHcloud Control Panel](/links/manager) > [!warning] > This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). @@ -46,7 +60,7 @@ As well as private IP addressing, the [vRack](/links/network/vrack) also allows > [!primary] > -> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the [vRack](/links/network/vrack). +> For example purposes we'll be using an IP block of 46.105.135.96/28 and eth1 for the secondary network interface, which is dedicated to the vRack. > > Also for example purposes, the network configuration file we refer to is located in `/etc/network/interfaces`. The equivalent file on your server may be located somewhere else, depending on your operating system. The file content may also be different. If you encounter any difficulties, please refer to the official documentation for your distribution. @@ -65,6 +79,64 @@ Select your vRack from the list to display the list of eligible services. Click ![vrack](images/addIPblock.png){.thumbnail} +### Managing public IP bandwidth on vRack + +By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). + +As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. It is important to note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. + +/// details | During the Additional IP ordering process + +#### Choosing public bandwidth during an Additional IP order + +The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. + +To order a new Additional IP block: + +- Log in to the [OVHcloud Control Panel](/links/manager). +- Open the `Network`{.action} section in the left-hand sidebar. +- Select `Public IP addresses`{.action}. +- Click on the `Order IPs`{.action} button, near the top of the page. +- Select the IP version, then the vRack you want to attach your Additional IP to. +- Select the region you want your Additional IP to be in. +- Choose the public bandwidth you want to apply to your vRack for that specific region. +- Fill in the other options as necessary, then proceed with your order. + +/// + +/// details | From the vRack management page + +#### Modifying vRack public bandwidth on management page + +For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. + +To access the management interface: + +- Open `Network`{.action} in the left-hand sidebar of your Control Panel. +- Select `vRack private network`{.action}. +- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. + +The management page is organized into two tabs: +- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. +- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. + +To modify the public bandwidth: + +- Navigate to the `Public IP routing`{.action} tab. +- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. +- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. +- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. +- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. + +> [!primary] +> +> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> + +The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. + +/// + ### Configure a usable IP address For vRack purposes, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. This means that the first useable address is the second address in the block, as shown below: @@ -88,13 +160,15 @@ For vRack purposes, the first, penultimate, and last addresses in any given IP b 46.105.135.111 Reserved: Network broadcast ``` -To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of **255.255.255.240**. +To configure the first usable IP address, we need to edit the network configuration file, as shown below. In this example, we need to use a subnet mask of *255.255.255.240*. > [!primary] > -The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. +> The subnet mask we've used in our example is appropriate for our IP block. Your subnet mask may differ depending on the size of your block. When you purchase your IP block, you'll receive an email that will tell you which subnet mask to use. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -137,7 +211,7 @@ Next, we need to create a new IP route for the vRack. We'll be adding a new traf > [!primary] > -For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. +> For example purposes, the network configuration file we refer to is located in /etc/network/interfaces. The equivalent file on your server may be located somewhere else, depending on your operating system. > Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. @@ -156,7 +230,143 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Now reboot your server to apply the changes. +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Create the file for the secondary network interface + +First we can copy and use the configuration being used for the primary network interface and adjust it as per our needs: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Then we access to the new file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +And we define the IP settings: +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Create a new IP routing table + +Next, we need to create a new IP route for the vRack. We'll be adding a new traffic rule by amending the file, as shown below: + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Next, create the file needed to apply the new rules: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +And paste the following content (please remember to replace our variables with your own values): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Amend the network configuration file + +Finally, we need to amend the network configuration file to account for the new traffic rule and route the vRack traffic through the network gateway address of **46.105.135.110**. + +We can achieve it by editing the following file in order to add persistent and static routes: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Paste the following content (please remember to replace our variables with your own values): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Now reboot your server to apply the changes or alternatively enable simply the new network interface: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Check and configure the secondary network interface + +First we must access to the new network interface information: + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Then we must check the properties: + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: IP Configuration + +We must select the `Use the following IP address`{.action} option: + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +And we can finally define the IP information: + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Rebooting the network interface + +First we do the disabling process + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Then we do the enabling process + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Troubleshooting + +If you are unable to establish a connection from your VM or server to the private network, please send us a ticket from your control panel with the following : + +- IP source and IP destination +- Ifconfig -a or ipconfig /all from both servers or VMs (setup network configuration interface) +- Ping in both ways +- Arp -a +- Routing table + +Please, include the results from above into your ticket. ## Go further diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-es.md index ec5ebf07005..858a5133c59 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-es.md @@ -1,77 +1,149 @@ --- -title: 'Configurar un bloque de IP en el vRack' -excerpt: 'Cómo configurar un bloque de direcciones IP públicas en el vRack' -updated: 2025-06-04 +title: 'Configurar un bloque de Additional IP en un vRack' +excerpt: 'Descubra cómo configurar un bloque de direcciones IP públicas en el vRack.' +updated: 2026-03-09 --- + + ## Objetivo -Además del direccionamiento IP privado, el [vRack](/links/network/vrack) permite dirigir el tráfico IP público a través del puerto vRack del servidor mediante un bloque de direcciones IP públicas. +Además del direccionamiento IP privado, el [vRack](/links/network/vrack) también le permite enrutar el tráfico IP público a través del puerto vRack de su servidor mediante un bloque de direcciones IP públicas. -**Esta guía explica cómo configurar en el vRack un bloque de direcciones IP públicas.** +**Esta guía le muestra cómo configurar un bloque de direcciones IP públicas para su uso con el vRack.** > [!primary] > -> El vRack admite el enrutamiento público IPv4 e IPv6 con bloques de direcciones Additional IP. Para más información sobre la configuración de bloques de IPv6, consulte esta guía: "[Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". +> El vRack admite tanto el enrutamiento público IPv4 como IPv6 con bloques de direcciones Additional IP. Puede encontrar las instrucciones sobre cómo configurar bloques IPv6 en esta guía: "[Configurar un bloque IPv6 en un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Este artículo explica cómo configurar direcciones Additional IP en una red vRack. Si necesita instrucciones para configurar direcciones Additional IP con una dirección IP principal (en la interfaz de red pública), consulte los siguientes artículos: +> Este artículo se centra en la configuración de Additional IP sobre una red vRack. Si busca orientación sobre la configuración de Additional IP junto con la IP primaria (en la interfaz de red pública), consulte los siguientes artículos: > > - IPv4: -> - [Configurar una dirección IP como alias en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configurar una dirección IP como alias en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar el aliasing de IP en servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar el aliasing de IP en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [Configurar IPv6 en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configurar la IPv6 en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurar IPv6 en servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar IPv6 en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). > - [Configurar IPv6 en una instancia de Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Requisitos -- Tener un bloque público de direcciones IP reservado en su cuenta, con un mínimo de cuatro direcciones. -- Haber elegido un rango de direcciones IP privadas. -- Tener un [servidor compatible con el vRack](/links/bare-metal/bare-metal). -- Haber activado un servicio [vRack](/links/network/vrack). -- Estar conectado al [área de cliente de OVHcloud](/links/manager). +- Un bloque público de direcciones IP en su cuenta, con un mínimo de cuatro direcciones +- Su rango de direcciones IP privadas elegido +- Un [servidor compatible con vRack](/links/bare-metal/bare-metal) +- Un servicio [vRack](/links/network/vrack) activado en su cuenta +- Acceso al [área de cliente de OVHcloud](/links/manager) > [!warning] -> Esta funcionalidad puede no estar disponible o estar limitada en los [servidores dedicados **Eco**](/links/bare-metal/eco-about). +> Es posible que esta funcionalidad no esté disponible o esté limitada en los [servidoresdedicados de la línea de productos **Eco**](/links/bare-metal/eco-about). > -> Para más información, consulte nuestra [comparativa](/links/bare-metal/eco-compare). +> Para más información, visite nuestra [página de comparación](/links/bare-metal/eco-compare). ## Procedimiento > [!primary] > -> En esta guía utilizaremos, a modo de ejemplo, el bloque de IP **46.105.135.96/28** y la interfaz de red secundaria **eth1** (dedicada al vRack). +> A modo de ejemplo, utilizaremos un bloque de IP de 46.105.135.96/28 y eth1 para la interfaz de red secundaria, que está dedicada al vRack. > -> También a modo de ejemplo, el archivo de configuración de red al que nos referimos se encuentra en `/etc/network/interfaces`. En función del sistema operativo, este archivo puede encontrarse en otra ubicación. El contenido del archivo también puede ser diferente. Si tiene alguna dificultad, consulte la documentación oficial de su distribución. +> También a modo de ejemplo, el archivo de configuración de red al que hacemos referencia se encuentra en `/etc/network/interfaces`. El archivo equivalente en su servidor puede estar ubicado en otro lugar, dependiendo de su sistema operativo. El contenido del archivo también puede ser diferente. Si tiene alguna dificultad, consulte la documentación oficial de su distribución. -### Añadir el bloque IP al vRack +### Añadir el bloque de IP al vRack > [!warning] > -> Cuando se añade un bloque IP al vRack, este ya no está asociado a un servidor físico. +> Una vez que se añade un bloque de IP al vRack, ya no está asociado a un servidor físico. > -> Esta configuración permite configurar IP de un mismo bloque en varios servidores, siempre que todos estos servidores estén en el mismo vRack que el bloque IP. El bloque IP debe tener al menos 2 direcciones IP utilizables o más para que esto sea posible. +> Esta configuración le permite configurar IPs del mismo bloque en varios servidores, siempre que todos estos servidores estén en el mismo vRack que el bloque de IP. El bloque de IP debe tener al menos 2 IPs utilizables o más para que esto sea posible. > -En el [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y haga clic en `Network`{.action}. A continuación, abra el menú `vRack`{.action}. +En su [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y haga clic en `Network`{.action}. A continuación, abra el menú `vRack`{.action}. -Seleccione el vRack en la lista para ver la lista de servicios compatibles. Haga clic en el bloque IP que quiera añadir al vRack y haga clic en el botón `Añadir`{.action}. +Seleccione su vRack de la lista para mostrar la lista de servicios elegibles. Haga clic en el bloque de IP que desea añadir al vRack y luego haga clic en el botón `Añadir`{.action}. ![vrack](images/addIPblock.png){.thumbnail} -### Configurar una dirección IP útil +### Gestionar el ancho de banda de IP pública en el vRack + +De forma predeterminada, los bloques de Additional IP enrutados a través de un vRack se benefician de un ancho de banda público estándar de 5 Gbps en Europa y América del Norte, o de 100 Mbps en las regiones APAC. Para más detalles sobre las opciones disponibles, consulte las opciones de enrutamiento público en nuestra [página del producto vRack](/links/network/vrack). + +Para responder a las crecientes necesidades de las infraestructuras y a los requisitos de los servicios de alto tráfico, OVHcloud ofrece ahora a sus clientes opciones de ancho de banda de pago. Tenga en cuenta que estas opciones se aplican **por vRack y por región**. Dado que las direcciones Additional IP están vinculadas a una región precisa, cualquier modificación del ancho de banda afectará al conjunto de las direcciones (IPv4 e IPv6) enrutadas a ese vRack en la región correspondiente. + +/// details | Durante el proceso de pedido de Additional IP + +#### Elegir el ancho de banda público durante el pedido + +Puede modificar el ancho de banda predeterminado al pedir un nuevo bloque de Additional IP, siempre que se seleccione una red vRack como servicio backend. + +Para pedir un nuevo bloque de Additional IP: + +- Inicie sesión en el [área de cliente de OVHcloud](/links/manager). +- En la barra lateral izquierda, acceda a la sección `Network`{.action}. +- Seleccione `Direcciones IP públicas`{.action}. +- Haga clic en el botón `Pedir IPs`{.action} en la parte superior de la página. +- Elija la versión de IP y, a continuación, el vRack al que se asociará la Additional IP. +- Seleccione la región de su Additional IP. +- Elija el ancho de banda público que desea aplicar a su vRack para esa región. +- Configure las demás opciones según sus necesidades y, a continuación, finalice el pedido. + +/// + +/// details | Desde la página de gestión del vRack + +#### Modificar el ancho de banda público desde la página de gestión + +Para los bloques de Additional IP ya asociados a un vRack, el ancho de banda se gestiona directamente desde la página de configuración del servicio. + +Para acceder a la interfaz de gestión: -En el caso del vRack, la primera, la penúltima y la última dirección de un bloque de IP siempre están reservadas para la dirección de red, la puerta de enlace y el *broadcast* respectivamente. Eso significa que la primera dirección útil es la segunda dirección del bloque, tal y como se muestra a continuación: +- En la barra lateral izquierda del Panel de control, abra `Network`{.action}. +- Seleccione `Red privada vRack`{.action}. +- En la columna "Dirección IP pública y ancho de banda", haga clic en el botón `Gestionar`{.action} correspondiente al vRack deseado. + +La interfaz de gestión se divide en dos pestañas: +- **All attached services**: Actualmente redirige a la página de gestión clásica del vRack. Próximamente, esta pestaña listará de forma optimizada todos los productos (servidores, proyectos Cloud, etc.) vinculados al vRack. +- **Conectividad IP pública**: Permite gestionar las opciones de enrutamiento público de su vRack, incluido el ancho de banda. + +Para modificar el ancho de banda: + +- Vaya a la pestaña `Conectividad IP pública`{.action}. +- La interfaz muestra ventanas de gestión por región (p. ej., `eu-west-par`) asociadas al vRack, con la lista de las IPs asociadas. +- En el recuadro de la región correspondiente, haga clic en `Modificar ancho de banda`{.action}. +- Seleccione la opción deseada en el panel de la derecha y, a continuación, haga clic en `Contratar`{.action} para validar. +- Una vez realizado el pago, el nuevo ancho de banda estará activo en su vRack en la región elegida después de unos minutos. + +> [!primary] +> +> El primer mes suscrito se factura de forma proporcional a los días restantes. La tarifa completa se aplicará en el siguiente ciclo de facturación. +> + +El aumento de ancho de banda se aplicará a todas las direcciones IP de esa región para el vRack seleccionado. + +/// + +### Configurar una dirección IP utilizable + +Para los propósitos del vRack, la primera, penúltima y última dirección de cualquier bloque de IP dado están siempre reservadas para la dirección de red, la puerta de enlace de red y la difusión de red respectivamente. Esto significa que la primera dirección utilizable es la segunda dirección del bloque, como se muestra a continuación: ```sh -46.105.135.96 # Reservada: dirección de red -46.105.135.97 # Primera IP útil +46.105.135.96 # Reservada: Dirección de red +46.105.135.97 # Primera IP utilizable 46.105.135.98 46.105.135.99 46.105.135.100 @@ -83,18 +155,20 @@ En el caso del vRack, la primera, la penúltima y la última dirección de un bl 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Última IP útil -46.105.135.110 # Reservada: puerta de enlace -46.105.135.111 # Reservada: broadcast +46.105.135.109 # Última IP utilizable +46.105.135.110 # Reservada: Puerta de enlace de red +46.105.135.111 # Reservada: Difusión de red ``` -Para configurar la primera dirección IP útil, edite el archivo de configuración de red como se indica a continuación. En este ejemplo, se utiliza la máscara de subred **255.255.255.240**. +Para configurar la primera dirección IP utilizable, necesitamos editar el archivo de configuración de red, como se muestra a continuación. En este ejemplo, necesitamos usar una máscara de subred de *255.255.255.240*. > [!primary] > -> La mascara de subred utilizada en el ejemplo es apropiada para nuestro bloque de IP. Su máscara de subred puede ser diferente en función del tamaño del bloque. Al contratar su bloque de IP, recibirá un mensaje de correo electrónico con la máscara de subred que debe utilizar. +> La máscara de subred que hemos utilizado en nuestro ejemplo es apropiada para nuestro bloque de IP. Su máscara de subred puede variar dependiendo del tamaño de su bloque. Cuando compre su bloque de IP, recibirá un correo electrónico que le indicará qué máscara de subred debe usar. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -104,39 +178,43 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` - ### Crear una nueva tabla de enrutamiento IP -En primer lugar, es recomendable descargar e instalar **iproute2**, un paquete que permite configurar manualmente el enrutamiento IP en el servidor. +En primer lugar, necesitamos descargar e instalar iproute2, que es un paquete que nos permitirá configurar manualmente el enrutamiento IP en el servidor. -Abra una conexión SSH a su servidor y ejecute el siguiente comando para descargar e instalar el paquete: +Establezca una conexión SSH con su servidor y ejecute el siguiente comando desde la línea de comandos. Esto descargará e instalará iproute2. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -A continuación, cree una nueva ruta IP para el vRack. Para ello, le recomendamos que añada una nueva regla de tráfico editando el archivo como se indica a continuación: +A continuación, necesitamos crear una nueva ruta IP para el vRack. Añadiremos una nueva regla de tráfico modificando el archivo, como se muestra a continuación: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# valores reservados +# 255 local 254 main 253 default 0 unspec -# # # +# # local -# # # +# #1 inr.ruhep 1 vrack ``` -### Editar el archivo de configuración de red +### Modificar el archivo de configuración de red -Por último, edite el archivo de configuración de red para que reconozca la nueva regla de tráfico y enrute el tráfico vRack hacia la dirección de la puerta de enlace **46.105.135.110**. +> [!primary] +> +> A modo de ejemplo, el archivo de configuración de red al que hacemos referencia se encuentra en /etc/network/interfaces. El archivo equivalente en su servidor puede estar ubicado en otro lugar, dependiendo de su sistema operativo. +> + +Finalmente, necesitamos modificar el archivo de configuración de red para tener en cuenta la nueva regla de tráfico y enrutar el tráfico del vRack a través de la dirección de puerta de enlace de red **46.105.135.110**. ```sh /etc/network/interfaces @@ -152,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Reinicie el servidor para que se apliquen los cambios realizados. +Ahora reinicie su servidor para aplicar los cambios o, alternativamente, habilite simplemente la nueva interfaz de red: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Crear el archivo para la interfaz de red secundaria + +En primer lugar, podemos copiar y usar la configuración que se utiliza para la interfaz de red primaria y ajustarla según nuestras necesidades: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Luego accedemos al nuevo archivo: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Y definimos la configuración de IP: +```sh +# Creado automáticamente por cloud-init al arrancar la instancia, no editar. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Crear una nueva tabla de enrutamiento IP + +A continuación, necesitamos crear una nueva ruta IP para el vRack. Añadiremos una nueva regla de tráfico modificando el archivo, como se muestra a continuación: + +```sh +/etc/iproute2/rt_tables + +# +# valores reservados +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +A continuación, cree el archivo necesario para aplicar las nuevas reglas: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +Y pegue el siguiente contenido (recuerde reemplazar nuestras variables con sus propios valores): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modificar el archivo de configuración de red + +Finalmente, necesitamos modificar el archivo de configuración de red para tener en cuenta la nueva regla de tráfico y enrutar el tráfico del vRack a través de la dirección de puerta de enlace de red **46.105.135.110**. + +Podemos lograrlo editando el siguiente archivo para añadir rutas persistentes y estáticas: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Pegue el siguiente contenido (recuerde reemplazar nuestras variables con sus propios valores): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Ahora reinicie su servidor para aplicar los cambios o, alternativamente, habilite simplemente la nueva interfaz de red: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Paso 1: Verificar y configurar la interfaz de red secundaria + +Primero debemos acceder a la información de la nueva interfaz de red: + +![verificar la segunda interfaz de red](images/win-ip-vrack-1.png){.thumbnail} + +Luego debemos verificar las propiedades: + +![propiedades de la segunda interfaz de red](images/win-ip-vrack-2.png){.thumbnail} + +![propiedades de la segunda interfaz de red](images/win-ip-vrack-3.png){.thumbnail} + +#### Paso 2: Configuración de IP + +Debemos seleccionar la opción ```Use the following IP address```: + +![configuración de ip](images/win-ip-vrack-4.png){.thumbnail} + +Y finalmente podemos definir la información de IP: + +![configuración de ip](images/win-ip-vrack-5b.png){.thumbnail} + +#### Paso 3: Reiniciar la interfaz de red + +Primero realizamos el proceso de desactivación: + +![desactivar red](images/win-ip-vrack-6.png){.thumbnail} + +Luego realizamos el proceso de activación: + +![activar red](images/win-ip-vrack-7.png){.thumbnail} + +### Resolución de problemas + +Si no puede establecer una conexión desde su VM o servidor a la red privada, envíenos un ticket desde su área de cliente con lo siguiente: + +- IP de origen e IP de destino +- Ifconfig -a o ipconfig /all de ambos servidores o VMs (configuración de la interfaz de configuración de red) +- Ping en ambas direcciones +- Arp -a +- Tabla de enrutamiento + +Por favor, incluya los resultados de lo anterior en su ticket. ## Más información -[Configurar varios servidores dedicados en el vRack](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Configurar el vRack en sus servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Crear varias VLAN en el vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Crear múltiples VLANs en un vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) -[Configurar el vRack entre la solución Public Cloud y un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) +[Configurar el vRack entre la Public Cloud y un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Interactúe con nuestra comunidad de usuarios en . +Interactúe con nuestra [comunidad de usuarios](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-us.md index e275c99043c..858a5133c59 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.es-us.md @@ -1,77 +1,149 @@ --- -title: 'Configurar un bloque de IP en el vRack' -excerpt: 'Cómo configurar un bloque de direcciones IP públicas en el vRack' -updated: 2025-06-04 +title: 'Configurar un bloque de Additional IP en un vRack' +excerpt: 'Descubra cómo configurar un bloque de direcciones IP públicas en el vRack.' +updated: 2026-03-09 --- + + ## Objetivo -Además del direccionamiento IP privado, el [vRack](https://www.ovh.com/world/es/soluciones/vrack/) permite dirigir el tráfico IP público a través del puerto vRack del servidor mediante un bloque de direcciones IP públicas. +Además del direccionamiento IP privado, el [vRack](/links/network/vrack) también le permite enrutar el tráfico IP público a través del puerto vRack de su servidor mediante un bloque de direcciones IP públicas. -**Esta guía explica cómo configurar en el vRack un bloque de direcciones IP públicas.** +**Esta guía le muestra cómo configurar un bloque de direcciones IP públicas para su uso con el vRack.** > [!primary] > -> El vRack admite el enrutamiento público IPv4 e IPv6 con bloques de direcciones Additional IP. Para más información sobre la configuración de bloques de IPv6, consulte esta guía: "[Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". +> El vRack admite tanto el enrutamiento público IPv4 como IPv6 con bloques de direcciones Additional IP. Puede encontrar las instrucciones sobre cómo configurar bloques IPv6 en esta guía: "[Configurar un bloque IPv6 en un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Este artículo explica cómo configurar direcciones Additional IP en una red vRack. Si necesita instrucciones para configurar direcciones Additional IP con una dirección IP principal (en la interfaz de red pública), consulte los siguientes artículos: +> Este artículo se centra en la configuración de Additional IP sobre una red vRack. Si busca orientación sobre la configuración de Additional IP junto con la IP primaria (en la interfaz de red pública), consulte los siguientes artículos: > > - IPv4: -> - [Configurar una dirección IP como alias en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configurar una dirección IP como alias en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar el aliasing de IP en servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar el aliasing de IP en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [Configurar IPv6 en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configurar la IPv6 en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurar IPv6 en servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar IPv6 en un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). > - [Configurar IPv6 en una instancia de Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Requisitos -- Tener un bloque público de direcciones IP reservado en su cuenta, con un mínimo de cuatro direcciones. -- Haber elegido un rango de direcciones IP privadas. -- Tener un [servidor compatible con el vRack](/links/bare-metal/bare-metal). -- Haber activado un servicio [vRack](https://www.ovh.com/world/es/soluciones/vrack/). -- Estar conectado al [área de cliente de OVHcloud](/links/manager). +- Un bloque público de direcciones IP en su cuenta, con un mínimo de cuatro direcciones +- Su rango de direcciones IP privadas elegido +- Un [servidor compatible con vRack](/links/bare-metal/bare-metal) +- Un servicio [vRack](/links/network/vrack) activado en su cuenta +- Acceso al [área de cliente de OVHcloud](/links/manager) > [!warning] -> Esta funcionalidad puede no estar disponible o estar limitada en los [servidores dedicados **Eco**](/links/bare-metal/eco-about). +> Es posible que esta funcionalidad no esté disponible o esté limitada en los [servidoresdedicados de la línea de productos **Eco**](/links/bare-metal/eco-about). > -> Para más información, consulte nuestra [comparativa](/links/bare-metal/eco-compare). +> Para más información, visite nuestra [página de comparación](/links/bare-metal/eco-compare). ## Procedimiento > [!primary] > -> En esta guía utilizaremos, a modo de ejemplo, el bloque de IP **46.105.135.96/28** y la interfaz de red secundaria **eth1** (dedicada al vRack). +> A modo de ejemplo, utilizaremos un bloque de IP de 46.105.135.96/28 y eth1 para la interfaz de red secundaria, que está dedicada al vRack. > -> También a modo de ejemplo, el archivo de configuración de red al que nos referimos se encuentra en `/etc/network/interfaces`. En función del sistema operativo, este archivo puede encontrarse en otra ubicación. El contenido del archivo también puede ser diferente. Si tiene alguna dificultad, consulte la documentación oficial de su distribución. +> También a modo de ejemplo, el archivo de configuración de red al que hacemos referencia se encuentra en `/etc/network/interfaces`. El archivo equivalente en su servidor puede estar ubicado en otro lugar, dependiendo de su sistema operativo. El contenido del archivo también puede ser diferente. Si tiene alguna dificultad, consulte la documentación oficial de su distribución. -### Añadir el bloque IP al vRack +### Añadir el bloque de IP al vRack > [!warning] > -> Cuando se añade un bloque IP al vRack, este ya no está asociado a un servidor físico. +> Una vez que se añade un bloque de IP al vRack, ya no está asociado a un servidor físico. > -> Esta configuración permite configurar IP de un mismo bloque en varios servidores, siempre que todos estos servidores estén en el mismo vRack que el bloque IP. El bloque IP debe tener al menos 2 direcciones IP utilizables o más para que esto sea posible. +> Esta configuración le permite configurar IPs del mismo bloque en varios servidores, siempre que todos estos servidores estén en el mismo vRack que el bloque de IP. El bloque de IP debe tener al menos 2 IPs utilizables o más para que esto sea posible. > -En el [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y haga clic en `Network`{.action}. A continuación, abra el menú `vRack`{.action}. +En su [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y haga clic en `Network`{.action}. A continuación, abra el menú `vRack`{.action}. -Seleccione el vRack en la lista para ver la lista de servicios compatibles. Haga clic en el bloque IP que quiera añadir al vRack y haga clic en el botón `Añadir`{.action}. +Seleccione su vRack de la lista para mostrar la lista de servicios elegibles. Haga clic en el bloque de IP que desea añadir al vRack y luego haga clic en el botón `Añadir`{.action}. ![vrack](images/addIPblock.png){.thumbnail} -### Configurar una dirección IP útil +### Gestionar el ancho de banda de IP pública en el vRack + +De forma predeterminada, los bloques de Additional IP enrutados a través de un vRack se benefician de un ancho de banda público estándar de 5 Gbps en Europa y América del Norte, o de 100 Mbps en las regiones APAC. Para más detalles sobre las opciones disponibles, consulte las opciones de enrutamiento público en nuestra [página del producto vRack](/links/network/vrack). + +Para responder a las crecientes necesidades de las infraestructuras y a los requisitos de los servicios de alto tráfico, OVHcloud ofrece ahora a sus clientes opciones de ancho de banda de pago. Tenga en cuenta que estas opciones se aplican **por vRack y por región**. Dado que las direcciones Additional IP están vinculadas a una región precisa, cualquier modificación del ancho de banda afectará al conjunto de las direcciones (IPv4 e IPv6) enrutadas a ese vRack en la región correspondiente. + +/// details | Durante el proceso de pedido de Additional IP + +#### Elegir el ancho de banda público durante el pedido + +Puede modificar el ancho de banda predeterminado al pedir un nuevo bloque de Additional IP, siempre que se seleccione una red vRack como servicio backend. + +Para pedir un nuevo bloque de Additional IP: + +- Inicie sesión en el [área de cliente de OVHcloud](/links/manager). +- En la barra lateral izquierda, acceda a la sección `Network`{.action}. +- Seleccione `Direcciones IP públicas`{.action}. +- Haga clic en el botón `Pedir IPs`{.action} en la parte superior de la página. +- Elija la versión de IP y, a continuación, el vRack al que se asociará la Additional IP. +- Seleccione la región de su Additional IP. +- Elija el ancho de banda público que desea aplicar a su vRack para esa región. +- Configure las demás opciones según sus necesidades y, a continuación, finalice el pedido. + +/// + +/// details | Desde la página de gestión del vRack + +#### Modificar el ancho de banda público desde la página de gestión + +Para los bloques de Additional IP ya asociados a un vRack, el ancho de banda se gestiona directamente desde la página de configuración del servicio. + +Para acceder a la interfaz de gestión: -En el caso del vRack, la primera, la penúltima y la última dirección de un bloque de IP siempre están reservadas para la dirección de red, la puerta de enlace y el *broadcast* respectivamente. Eso significa que la primera dirección útil es la segunda dirección del bloque, tal y como se muestra a continuación: +- En la barra lateral izquierda del Panel de control, abra `Network`{.action}. +- Seleccione `Red privada vRack`{.action}. +- En la columna "Dirección IP pública y ancho de banda", haga clic en el botón `Gestionar`{.action} correspondiente al vRack deseado. + +La interfaz de gestión se divide en dos pestañas: +- **All attached services**: Actualmente redirige a la página de gestión clásica del vRack. Próximamente, esta pestaña listará de forma optimizada todos los productos (servidores, proyectos Cloud, etc.) vinculados al vRack. +- **Conectividad IP pública**: Permite gestionar las opciones de enrutamiento público de su vRack, incluido el ancho de banda. + +Para modificar el ancho de banda: + +- Vaya a la pestaña `Conectividad IP pública`{.action}. +- La interfaz muestra ventanas de gestión por región (p. ej., `eu-west-par`) asociadas al vRack, con la lista de las IPs asociadas. +- En el recuadro de la región correspondiente, haga clic en `Modificar ancho de banda`{.action}. +- Seleccione la opción deseada en el panel de la derecha y, a continuación, haga clic en `Contratar`{.action} para validar. +- Una vez realizado el pago, el nuevo ancho de banda estará activo en su vRack en la región elegida después de unos minutos. + +> [!primary] +> +> El primer mes suscrito se factura de forma proporcional a los días restantes. La tarifa completa se aplicará en el siguiente ciclo de facturación. +> + +El aumento de ancho de banda se aplicará a todas las direcciones IP de esa región para el vRack seleccionado. + +/// + +### Configurar una dirección IP utilizable + +Para los propósitos del vRack, la primera, penúltima y última dirección de cualquier bloque de IP dado están siempre reservadas para la dirección de red, la puerta de enlace de red y la difusión de red respectivamente. Esto significa que la primera dirección utilizable es la segunda dirección del bloque, como se muestra a continuación: ```sh -46.105.135.96 # Reservada: dirección de red -46.105.135.97 # Primera IP útil +46.105.135.96 # Reservada: Dirección de red +46.105.135.97 # Primera IP utilizable 46.105.135.98 46.105.135.99 46.105.135.100 @@ -83,18 +155,20 @@ En el caso del vRack, la primera, la penúltima y la última dirección de un bl 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Última IP útil -46.105.135.110 # Reservada: puerta de enlace -46.105.135.111 # Reservada: broadcast +46.105.135.109 # Última IP utilizable +46.105.135.110 # Reservada: Puerta de enlace de red +46.105.135.111 # Reservada: Difusión de red ``` -Para configurar la primera dirección IP útil, edite el archivo de configuración de red como se indica a continuación. En este ejemplo, se utiliza la máscara de subred **255.255.255.240**. +Para configurar la primera dirección IP utilizable, necesitamos editar el archivo de configuración de red, como se muestra a continuación. En este ejemplo, necesitamos usar una máscara de subred de *255.255.255.240*. > [!primary] > -> La mascara de subred utilizada en el ejemplo es apropiada para nuestro bloque de IP. Su máscara de subred puede ser diferente en función del tamaño del bloque. Al contratar su bloque de IP, recibirá un mensaje de correo electrónico con la máscara de subred que debe utilizar. +> La máscara de subred que hemos utilizado en nuestro ejemplo es apropiada para nuestro bloque de IP. Su máscara de subred puede variar dependiendo del tamaño de su bloque. Cuando compre su bloque de IP, recibirá un correo electrónico que le indicará qué máscara de subred debe usar. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -104,39 +178,43 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` - ### Crear una nueva tabla de enrutamiento IP -En primer lugar, es recomendable descargar e instalar **iproute2**, un paquete que permite configurar manualmente el enrutamiento IP en el servidor. +En primer lugar, necesitamos descargar e instalar iproute2, que es un paquete que nos permitirá configurar manualmente el enrutamiento IP en el servidor. -Abra una conexión SSH a su servidor y ejecute el siguiente comando para descargar e instalar el paquete: +Establezca una conexión SSH con su servidor y ejecute el siguiente comando desde la línea de comandos. Esto descargará e instalará iproute2. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -A continuación, cree una nueva ruta IP para el vRack. Para ello, le recomendamos que añada una nueva regla de tráfico editando el archivo como se indica a continuación: +A continuación, necesitamos crear una nueva ruta IP para el vRack. Añadiremos una nueva regla de tráfico modificando el archivo, como se muestra a continuación: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# valores reservados +# 255 local 254 main 253 default 0 unspec -# # # +# # local -# # # +# #1 inr.ruhep 1 vrack ``` -### Editar el archivo de configuración de red +### Modificar el archivo de configuración de red -Por último, edite el archivo de configuración de red para que reconozca la nueva regla de tráfico y enrute el tráfico vRack hacia la dirección de la puerta de enlace **46.105.135.110**. +> [!primary] +> +> A modo de ejemplo, el archivo de configuración de red al que hacemos referencia se encuentra en /etc/network/interfaces. El archivo equivalente en su servidor puede estar ubicado en otro lugar, dependiendo de su sistema operativo. +> + +Finalmente, necesitamos modificar el archivo de configuración de red para tener en cuenta la nueva regla de tráfico y enrutar el tráfico del vRack a través de la dirección de puerta de enlace de red **46.105.135.110**. ```sh /etc/network/interfaces @@ -152,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Reinicie el servidor para que se apliquen los cambios realizados. +Ahora reinicie su servidor para aplicar los cambios o, alternativamente, habilite simplemente la nueva interfaz de red: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Crear el archivo para la interfaz de red secundaria + +En primer lugar, podemos copiar y usar la configuración que se utiliza para la interfaz de red primaria y ajustarla según nuestras necesidades: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Luego accedemos al nuevo archivo: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Y definimos la configuración de IP: +```sh +# Creado automáticamente por cloud-init al arrancar la instancia, no editar. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Crear una nueva tabla de enrutamiento IP + +A continuación, necesitamos crear una nueva ruta IP para el vRack. Añadiremos una nueva regla de tráfico modificando el archivo, como se muestra a continuación: + +```sh +/etc/iproute2/rt_tables + +# +# valores reservados +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +A continuación, cree el archivo necesario para aplicar las nuevas reglas: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +Y pegue el siguiente contenido (recuerde reemplazar nuestras variables con sus propios valores): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modificar el archivo de configuración de red + +Finalmente, necesitamos modificar el archivo de configuración de red para tener en cuenta la nueva regla de tráfico y enrutar el tráfico del vRack a través de la dirección de puerta de enlace de red **46.105.135.110**. + +Podemos lograrlo editando el siguiente archivo para añadir rutas persistentes y estáticas: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Pegue el siguiente contenido (recuerde reemplazar nuestras variables con sus propios valores): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Ahora reinicie su servidor para aplicar los cambios o, alternativamente, habilite simplemente la nueva interfaz de red: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Paso 1: Verificar y configurar la interfaz de red secundaria + +Primero debemos acceder a la información de la nueva interfaz de red: + +![verificar la segunda interfaz de red](images/win-ip-vrack-1.png){.thumbnail} + +Luego debemos verificar las propiedades: + +![propiedades de la segunda interfaz de red](images/win-ip-vrack-2.png){.thumbnail} + +![propiedades de la segunda interfaz de red](images/win-ip-vrack-3.png){.thumbnail} + +#### Paso 2: Configuración de IP + +Debemos seleccionar la opción ```Use the following IP address```: + +![configuración de ip](images/win-ip-vrack-4.png){.thumbnail} + +Y finalmente podemos definir la información de IP: + +![configuración de ip](images/win-ip-vrack-5b.png){.thumbnail} + +#### Paso 3: Reiniciar la interfaz de red + +Primero realizamos el proceso de desactivación: + +![desactivar red](images/win-ip-vrack-6.png){.thumbnail} + +Luego realizamos el proceso de activación: + +![activar red](images/win-ip-vrack-7.png){.thumbnail} + +### Resolución de problemas + +Si no puede establecer una conexión desde su VM o servidor a la red privada, envíenos un ticket desde su área de cliente con lo siguiente: + +- IP de origen e IP de destino +- Ifconfig -a o ipconfig /all de ambos servidores o VMs (configuración de la interfaz de configuración de red) +- Ping en ambas direcciones +- Arp -a +- Tabla de enrutamiento + +Por favor, incluya los resultados de lo anterior en su ticket. ## Más información -[Configurar varios servidores dedicados en el vRack](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Configurar el vRack en sus servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Crear varias VLAN en el vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Crear múltiples VLANs en un vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) -[Configurar el vRack entre la solución Public Cloud y un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) +[Configurar el vRack entre la Public Cloud y un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Interactúe con nuestra comunidad de usuarios en . +Interactúe con nuestra [comunidad de usuarios](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-ca.md index 498830a7495..feb5f06a889 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-ca.md @@ -1,18 +1,32 @@ --- -title: Configurer un bloc d'IP dans le vRack -excerpt: Découvrez comment configurer un bloc d'adresses IP publiques dans le vRack -updated: 2025-06-04 +title: "Configurer un bloc Additional IP dans le vRack" +excerpt: "Découvrez comment configurer un bloc d'adresses IP publiques dans le vRack" +updated: 2026-03-09 --- + + ## Objectif -En plus de l'adressage IP privé, le [vRack](https://www.ovh.com/ca/fr/solutions/vrack/) vous permet de diriger le trafic IP public via le port vRack de votre serveur à l'aide d'un bloc d'adresses IP publiques. +En plus de l'adressage IP privé, le [vRack](/links/network/vrack) vous permet de diriger le trafic IP public via le port vRack de votre serveur à l'aide d'un bloc d'adresses IP publiques. **Ce guide vous explique comment configurer un bloc d'adresses IP publiques à utiliser avec le vRack.** > [!primary] > -> Le vRack prend en charge le routage public IPv4 et IPv6 avec des blocs d’adresses Additional IP. Retrouvez les instructions sur la configuration de blocs IPv6 dans ce guide : « [Configurer un bloc Additional IPv6 dans un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack) ». +> Le vRack prend en charge le routage public IPv4 et IPv6 avec des blocs d'adresses Additional IP. Retrouvez les instructions sur la configuration de blocs IPv6 dans ce guide : « [Configurer un bloc Additional IPv6 dans un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack) ». > > [!primary] @@ -33,14 +47,14 @@ En plus de l'adressage IP privé, le [vRack](https://www.ovh.com/ca/fr/solutions - Avoir réservé un bloc public d'adresses IP dans votre compte, avec un minimum de quatre adresses. - Préparer votre plage d'adresses IP privées choisies. -- Posséder un [serveur compatible vRack](https://www.ovh.com/ca/fr/serveurs_dedies/). -- Activer un service [vRack](https://www.ovh.com/ca/fr/solutions/vrack/). +- Posséder un [serveur compatible vRack](/links/bare-metal/bare-metal). +- Activer un service [vRack](/links/network/vrack). - Être connecté à l'[espace client OVHcloud](/links/manager). > [!warning] > Cette fonctionnalité peut être indisponible ou limitée sur les [serveurs dédiés **Eco**](/links/bare-metal/eco-about). > -> Consultez notre [comparatif](/links/bare-metal/eco-compare) pour plus d’informations. +> Consultez notre [comparatif](/links/bare-metal/eco-compare) pour plus d'informations. ## En pratique @@ -48,7 +62,7 @@ En plus de l'adressage IP privé, le [vRack](https://www.ovh.com/ca/fr/solutions > > À titre d'exemple, nous utiliserons un bloc IP de 46.105.135.96/28 et `eth1` pour l'interface réseau secondaire, qui est dédiée au vRack. > -> À titre d’exemple également, le fichier de configuration réseau auquel nous faisons référence se trouve dans `/etc/network/interfaces`. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. Le contenu du fichier peut également être différent. En cas de difficultés, n'hésitez pas à vous référer à la documentation officielle de votre distribution. +> À titre d'exemple également, le fichier de configuration réseau auquel nous faisons référence se trouve dans `/etc/network/interfaces`. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. Le contenu du fichier peut également être différent. En cas de difficultés, n'hésitez pas à vous référer à la documentation officielle de votre distribution. ### Ajouter le bloc IP au vRack @@ -65,6 +79,64 @@ Sélectionnez votre vRack dans la liste pour afficher la liste des services éli ![vrack](images/addIPblock.png){.thumbnail} +### Gérer la bande passante des IP publiques sur le vRack + +Par défaut, les blocs d'Additional IP routés via un vRack bénéficient d'une bande passante publique standard de 5 Gbps en Europe et en Amérique du Nord, ou de 100 Mbps dans les régions APAC. Pour plus de détails sur les offres disponibles, consultez les options de routage public sur notre [page produit vRack](/links/network/vrack). + +Pour répondre à la montée en charge des infrastructures et aux besoins des services à fort trafic, OVHcloud propose maintenant à ses clients des options de bande passante payantes. Notez que ces options s'appliquent **par vRack et par région**. Comme les Additional IP sont liées à une région précise, toute modification de la bande passante impactera l'ensemble des adresses (IPv4 et IPv6) routées vers ce vRack dans la région concernée. + +/// details | Lors de la commande d'une Additional IP + +#### Choisir la bande passante publique lors de la commande + +Vous pouvez modifier la bande passante par défaut au moment de commander un nouveau bloc d'Additional IP, dès lors qu'un réseau vRack est sélectionné comme service backend. + +Pour commander un nouveau bloc d'Additional IP : + +- Connectez-vous à [l'espace client OVHcloud](/links/manager). +- Dans la barre latérale gauche, accédez à la section `Network`{.action}. +- Sélectionnez `Adresses IP Publiques`{.action}. +- Cliquez sur le bouton `Commander des IPs`{.action} en haut de la page. +- Choisissez la version de l'IP, puis le vRack auquel l'Additional IP sera rattachée. +- Sélectionnez la région de votre Additional IP. +- Choisissez la bande passante publique à appliquer à votre vRack pour cette région. +- Configurez les autres options selon vos besoins, puis finalisez la commande. + +/// + +/// details | Depuis la page de gestion du vRack + +#### Modifier la bande passante publique depuis la page de gestion + +Pour les blocs d'Additional IP déjà rattachés à un vRack, la bande passante se gère directement depuis la page de configuration du service. + +Pour accéder à l'interface de gestion : + +- Dans la barre latérale gauche du Tableau de bord, ouvrez `Network`{.action}. +- Sélectionnez `Réseau Privé vRack`{.action}. +- Dans la colonne « Adresse IP publique et bande passante », cliquez sur le bouton `Gérer`{.action} correspondant au vRack souhaité. + +L'interface de gestion se divise en deux onglets : +- **Tous les services attachés** : Redirige actuellement vers la page de gestion classique du vRack. Prochainement, cet onglet listera de façon optimisée tous les produits (serveurs, projets Cloud, etc.) liés au vRack. +- **Connectivité IP publique** : Permet de gérer les options de routage public de votre vRack, y compris la bande passante. + +Pour modifier la bande passante : + +- Allez dans l'onglet `Connectivité IP publique`{.action}. +- L'interface affiche des fenêtres de gestion par région (ex : `eu-west-par`) associées au vRack, avec la liste des IP rattachées. +- Dans l'encadré de la région concernée, cliquez sur `Modifier la bande passante`{.action}. +- Sélectionnez l'option souhaitée dans le panneau de droite, puis cliquez sur `Commander`{.action} pour valider. +- Une fois le paiement effectué, la nouvelle bande passante sera effective sur votre vRack dans la région choisie après quelques minutes. + +> [!primary] +> +> Le premier mois souscrit est facturé au prorata des jours restants. Le tarif complet s'appliquera lors du cycle de facturation suivant. +> + +L'augmentation de bande passante s'appliquera à toutes les adresses IP de cette région pour le vRack sélectionné. + +/// + ### Configurer une adresse IP utilisable Dans le cas du vRack, la première, l'avant-dernière et la dernière adresse d'un bloc d'IP donné sont toujours réservées respectivement à l'adresse réseau, la passerelle réseau et au *broadcast* du réseau. Cela signifie que la première adresse utilisable est la deuxième adresse du bloc, comme indiqué ci-dessous : @@ -84,7 +156,7 @@ Dans le cas du vRack, la première, l'avant-dernière et la dernière adresse d' 46.105.135.107 46.105.135.108 46.105.135.109 # Dernière IP utilisable -46.105.135.110 # Réservée : passerelle réseau Reserved: Network gateway +46.105.135.110 # Réservée : passerelle réseau 46.105.135.111 # Réservée : broadcast réseau ``` @@ -95,6 +167,8 @@ Pour configurer la première adresse IP utilisable, vous devez éditer le fichie > Le masque de sous-réseau utilisé dans cet exemple est approprié pour notre bloc IP. Votre masque de sous-réseau peut différer en fonction de la taille de votre bloc. Lorsque vous achetez votre bloc d'IP, vous recevez un e-mail vous indiquant le masque de sous-réseau à utiliser. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -107,7 +181,7 @@ broadcast 46.105.135.111 ### Créer une nouvelle table de routage IP -Avant tout, il convient de télécharger et installer « iproute2 », un paquet qui permettra de configurer manuellement le routage IP sur le serveur. +Avant tout, il convient de télécharger et installer « iproute2 », un paquet qui permettra de configurer manuellement le routage IP sur le serveur. Ouvrez ensuite une connexion SSH à votre serveur et utilisez la commande suivante pour télécharger et installer le paquet : @@ -120,22 +194,27 @@ Ensuite, vous devez créer une nouvelle route IP pour le vRack. Pour cela, il co ```sh /etc/iproute2/rt_tables -# # # +# # reserved values -# # # +# 255 local 254 main 253 default 0 unspec -# # # +# # local -# # # +# #1 inr.ruhep 1 vrack ``` ### Modifier le fichier de configuration réseau +> [!primary] +> +> À titre d'exemple, le fichier de configuration réseau auquel nous faisons référence se trouve dans /etc/network/interfaces. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. +> + Pour finir, il reste à modifier le fichier de configuration réseau pour prendre en compte la nouvelle règle de trafic et acheminer le trafic vRack via l'adresse de passerelle réseau **46.105.135.110**. ```sh @@ -152,7 +231,147 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Redémarrez le serveur pour appliquer les modifications effectuées. +Redémarrez le serveur pour appliquer les modifications effectuées. Vous pouvez également activer simplement la nouvelle interface réseau : + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Créer le fichier pour l'interface réseau secondaire + +Tout d'abord, copiez et utilisez la configuration de l'interface réseau principale, puis adaptez-la selon vos besoins : + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` + +Accédez ensuite au nouveau fichier : + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` + +Définissez les paramètres IP : + +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Créer une nouvelle table de routage IP + +Ensuite, créez une nouvelle route IP pour le vRack. Ajoutez une nouvelle règle de trafic en modifiant le fichier comme indiqué ci-dessous : + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Créez ensuite le fichier nécessaire pour appliquer les nouvelles règles : + +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +Collez le contenu suivant (pensez à remplacer les variables par vos propres valeurs) : + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modifier le fichier de configuration réseau + +Pour finir, modifiez le fichier de configuration réseau pour prendre en compte la nouvelle règle de trafic et acheminer le trafic vRack via l'adresse de passerelle réseau **46.105.135.110**. + +Modifiez le fichier suivant afin d'ajouter des routes persistantes et statiques : + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Collez le contenu suivant (pensez à remplacer les variables par vos propres valeurs) : + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Redémarrez le serveur pour appliquer les modifications effectuées. Vous pouvez également activer simplement la nouvelle interface réseau : + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Étape 1 : Vérifier et configurer l'interface réseau secondaire + +Tout d'abord, accédez aux informations de la nouvelle interface réseau : + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Vérifiez ensuite les propriétés : + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Étape 2 : Configuration IP + +Sélectionnez l'option `Utiliser l'adresse IP suivante` : + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +Définissez ensuite les informations IP : + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Étape 3 : Redémarrage de l'interface réseau + +Commencez par désactiver l'interface : + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Puis activez-la : + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Résolution des problèmes + +Si vous ne parvenez pas à établir une connexion depuis votre VM ou serveur vers le réseau privé, ouvrez un ticket depuis votre espace client en fournissant les informations suivantes : + +* IP source et IP de destination +* Résultat de la commande `ifconfig -a` ou `ipconfig /all` sur les deux serveurs ou VMs (configuration de l'interface réseau) +* Résultat du ping dans les deux sens +* Résultat de la commande `arp -a` +* Table de routage + +Joignez les résultats des commandes ci-dessus à votre ticket. ## Aller plus loin diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md index 353932ef3a9..f76d82bc8c9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.fr-fr.md @@ -1,9 +1,23 @@ --- title: "Configurer un bloc Additional IP dans le vRack" excerpt: "Découvrez comment configurer un bloc d'adresses IP publiques dans le vRack" -updated: 2025-06-04 +updated: 2026-03-09 --- + + ## Objectif En plus de l'adressage IP privé, le [vRack](/links/network/vrack) vous permet de diriger le trafic IP public via le port vRack de votre serveur à l'aide d'un bloc d'adresses IP publiques. @@ -12,7 +26,7 @@ En plus de l'adressage IP privé, le [vRack](/links/network/vrack) vous permet d > [!primary] > -> Le vRack prend en charge le routage public IPv4 et IPv6 avec des blocs d’adresses Additional IP. Retrouvez les instructions sur la configuration de blocs IPv6 dans ce guide : « [Configurer un bloc Additional IPv6 dans un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack) ». +> Le vRack prend en charge le routage public IPv4 et IPv6 avec des blocs d'adresses Additional IP. Retrouvez les instructions sur la configuration de blocs IPv6 dans ce guide : « [Configurer un bloc Additional IPv6 dans un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack) ». > > [!primary] @@ -40,7 +54,7 @@ En plus de l'adressage IP privé, le [vRack](/links/network/vrack) vous permet d > [!warning] > Cette fonctionnalité peut être indisponible ou limitée sur les [serveurs dédiés **Eco**](/links/bare-metal/eco-about). > -> Consultez notre [comparatif](/links/bare-metal/eco-compare) pour plus d’informations. +> Consultez notre [comparatif](/links/bare-metal/eco-compare) pour plus d'informations. ## En pratique @@ -48,7 +62,7 @@ En plus de l'adressage IP privé, le [vRack](/links/network/vrack) vous permet d > > À titre d'exemple, nous utiliserons un bloc IP de 46.105.135.96/28 et `eth1` pour l'interface réseau secondaire, qui est dédiée au vRack. > -> À titre d’exemple également, le fichier de configuration réseau auquel nous faisons référence se trouve dans `/etc/network/interfaces`. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. Le contenu du fichier peut également être différent. En cas de difficultés, n'hésitez pas à vous référer à la documentation officielle de votre distribution. +> À titre d'exemple également, le fichier de configuration réseau auquel nous faisons référence se trouve dans `/etc/network/interfaces`. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. Le contenu du fichier peut également être différent. En cas de difficultés, n'hésitez pas à vous référer à la documentation officielle de votre distribution. ### Ajouter le bloc IP au vRack @@ -77,7 +91,8 @@ Pour répondre à la montée en charge des infrastructures et aux besoins des se Vous pouvez modifier la bande passante par défaut au moment de commander un nouveau bloc d'Additional IP, dès lors qu'un réseau vRack est sélectionné comme service backend. -Pour commander un nouveau bloc d'Additional IPv6 : +Pour commander un nouveau bloc d'Additional IP : + - Connectez-vous à [l'espace client OVHcloud](/links/manager). - Dans la barre latérale gauche, accédez à la section `Network`{.action}. - Sélectionnez `Adresses IP Publiques`{.action}. @@ -96,24 +111,26 @@ Pour commander un nouveau bloc d'Additional IPv6 : Pour les blocs d'Additional IP déjà rattachés à un vRack, la bande passante se gère directement depuis la page de configuration du service. Pour accéder à l'interface de gestion : + - Dans la barre latérale gauche du Tableau de bord, ouvrez `Network`{.action}. - Sélectionnez `Réseau Privé vRack`{.action}. -- Dans la colonne "Adresse IP publique et bande passante", cliquez sur le bouton `Gérer`{.action} correspondant au vRack souhaité. +- Dans la colonne « Adresse IP publique et bande passante », cliquez sur le bouton `Gérer`{.action} correspondant au vRack souhaité. L'interface de gestion se divise en deux onglets : -* **Tous les services attachés** : Redirige actuellement vers la page de gestion classique du vRack. Prochainement, cet onglet listera de façon optimisée tous les produits (serveurs, projets Cloud, etc.) liés au vRack. -* **Connectivité IP publique** : Permet de gérer les options de routage public de votre vRack, y compris la bande passante. +- **Tous les services attachés** : Redirige actuellement vers la page de gestion classique du vRack. Prochainement, cet onglet listera de façon optimisée tous les produits (serveurs, projets Cloud, etc.) liés au vRack. +- **Connectivité IP publique** : Permet de gérer les options de routage public de votre vRack, y compris la bande passante. Pour modifier la bande passante : + - Allez dans l'onglet `Connectivité IP publique`{.action}. -- L'interface affiche des fenêtres de gestion par région (ex: `eu-west-par`) associées au vRack, avec la liste des IP rattachées. +- L'interface affiche des fenêtres de gestion par région (ex : `eu-west-par`) associées au vRack, avec la liste des IP rattachées. - Dans l'encadré de la région concernée, cliquez sur `Modifier la bande passante`{.action}. - Sélectionnez l'option souhaitée dans le panneau de droite, puis cliquez sur `Commander`{.action} pour valider. - Une fois le paiement effectué, la nouvelle bande passante sera effective sur votre vRack dans la région choisie après quelques minutes. > [!primary] > -> Notez que le premier mois souscrit est facturé au prorata des jours restants. Le tarif complet s'appliquera lors du cycle de facturation suivant. +> Le premier mois souscrit est facturé au prorata des jours restants. Le tarif complet s'appliquera lors du cycle de facturation suivant. > L'augmentation de bande passante s'appliquera à toutes les adresses IP de cette région pour le vRack sélectionné. @@ -139,7 +156,7 @@ Dans le cas du vRack, la première, l'avant-dernière et la dernière adresse d' 46.105.135.107 46.105.135.108 46.105.135.109 # Dernière IP utilisable -46.105.135.110 # Réservée : passerelle réseau Reserved: Network gateway +46.105.135.110 # Réservée : passerelle réseau 46.105.135.111 # Réservée : broadcast réseau ``` @@ -150,6 +167,8 @@ Pour configurer la première adresse IP utilisable, vous devez éditer le fichie > Le masque de sous-réseau utilisé dans cet exemple est approprié pour notre bloc IP. Votre masque de sous-réseau peut différer en fonction de la taille de votre bloc. Lorsque vous achetez votre bloc d'IP, vous recevez un e-mail vous indiquant le masque de sous-réseau à utiliser. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -162,7 +181,7 @@ broadcast 46.105.135.111 ### Créer une nouvelle table de routage IP -Avant tout, il convient de télécharger et installer « iproute2 », un paquet qui permettra de configurer manuellement le routage IP sur le serveur. +Avant tout, il convient de télécharger et installer « iproute2 », un paquet qui permettra de configurer manuellement le routage IP sur le serveur. Ouvrez ensuite une connexion SSH à votre serveur et utilisez la commande suivante pour télécharger et installer le paquet : @@ -175,22 +194,27 @@ Ensuite, vous devez créer une nouvelle route IP pour le vRack. Pour cela, il co ```sh /etc/iproute2/rt_tables -# # # +# # reserved values -# # # +# 255 local 254 main 253 default 0 unspec -# # # +# # local -# # # +# #1 inr.ruhep 1 vrack ``` ### Modifier le fichier de configuration réseau +> [!primary] +> +> À titre d'exemple, le fichier de configuration réseau auquel nous faisons référence se trouve dans /etc/network/interfaces. En fonction du système d'exploitation utilisé, le fichier équivalent peut être situé ailleurs. +> + Pour finir, il reste à modifier le fichier de configuration réseau pour prendre en compte la nouvelle règle de trafic et acheminer le trafic vRack via l'adresse de passerelle réseau **46.105.135.110**. ```sh @@ -207,7 +231,147 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Redémarrez le serveur pour appliquer les modifications effectuées. +Redémarrez le serveur pour appliquer les modifications effectuées. Vous pouvez également activer simplement la nouvelle interface réseau : + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Créer le fichier pour l'interface réseau secondaire + +Tout d'abord, copiez et utilisez la configuration de l'interface réseau principale, puis adaptez-la selon vos besoins : + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` + +Accédez ensuite au nouveau fichier : + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` + +Définissez les paramètres IP : + +```sh +# Created by cloud-init on instance boot automatically, do not edit. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Créer une nouvelle table de routage IP + +Ensuite, créez une nouvelle route IP pour le vRack. Ajoutez une nouvelle règle de trafic en modifiant le fichier comme indiqué ci-dessous : + +```sh +/etc/iproute2/rt_tables + +# +# reserved values +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Créez ensuite le fichier nécessaire pour appliquer les nouvelles règles : + +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +Collez le contenu suivant (pensez à remplacer les variables par vos propres valeurs) : + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modifier le fichier de configuration réseau + +Pour finir, modifiez le fichier de configuration réseau pour prendre en compte la nouvelle règle de trafic et acheminer le trafic vRack via l'adresse de passerelle réseau **46.105.135.110**. + +Modifiez le fichier suivant afin d'ajouter des routes persistantes et statiques : + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Collez le contenu suivant (pensez à remplacer les variables par vos propres valeurs) : + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Redémarrez le serveur pour appliquer les modifications effectuées. Vous pouvez également activer simplement la nouvelle interface réseau : + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Étape 1 : Vérifier et configurer l'interface réseau secondaire + +Tout d'abord, accédez aux informations de la nouvelle interface réseau : + +![check the second network interface](images/win-ip-vrack-1.png){.thumbnail} + +Vérifiez ensuite les propriétés : + +![properties of the second network interface](images/win-ip-vrack-2.png){.thumbnail} + +![properties of the second network interface](images/win-ip-vrack-3.png){.thumbnail} + +#### Étape 2 : Configuration IP + +Sélectionnez l'option `Utiliser l'adresse IP suivante` : + +![ip configuration](images/win-ip-vrack-4.png){.thumbnail} + +Définissez ensuite les informations IP : + +![ip configuration](images/win-ip-vrack-5b.png){.thumbnail} + +#### Étape 3 : Redémarrage de l'interface réseau + +Commencez par désactiver l'interface : + +![disabling network](images/win-ip-vrack-6.png){.thumbnail} + +Puis activez-la : + +![enabling network](images/win-ip-vrack-7.png){.thumbnail} + +### Résolution des problèmes + +Si vous ne parvenez pas à établir une connexion depuis votre VM ou serveur vers le réseau privé, ouvrez un ticket depuis votre espace client en fournissant les informations suivantes : + +- IP source et IP de destination +- Résultat de la commande `ifconfig -a` ou `ipconfig /all` sur les deux serveurs ou VMs (configuration de l'interface réseau) +- Résultat du ping dans les deux sens +- Résultat de la commande `arp -a` +- Table de routage + +Joignez les résultats des commandes ci-dessus à votre ticket. ## Aller plus loin diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.it-it.md index 57c8a2919fc..bbb6b250718 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.it-it.md @@ -1,76 +1,148 @@ --- -title: 'Configurare un blocco di indirizzi IP nella vRack' -excerpt: 'Scopri come configurare un blocco di indirizzi IP nella vRack' -updated: 2025-06-04 +title: 'Configurare un blocco Additional IP in un vRack' +excerpt: 'Scopri come configurare un blocco di indirizzi IP pubblici nel vRack.' +updated: 2026-03-09 --- + + ## Obiettivo -Oltre a consentire un indirizzamento IP privato, la [vRack](https://www.ovh.it/soluzioni/vrack/) permette di dirigere il traffico IP pubblico tramite la porta vRack del server attraverso un blocco di indirizzi IP pubblici. +Oltre all'indirizzamento IP privato, il [vRack](/links/network/vrack) consente anche di instradare il traffico IP pubblico attraverso la porta vRack del server utilizzando un blocco di indirizzi IP pubblici. -**Questa guida ti mostra come configurare un blocco di indirizzi IP pubblici da utilizzare con la vRack.** +**Questa guida mostra come configurare un blocco di indirizzi IP pubblici per l'utilizzo con il vRack.** > [!primary] > -> La vRack supporta il routing pubblico IPv4 e IPv6 con blocchi di indirizzi Additional IP. Per istruzioni sulla configurazione dei blocchi IPv6, consulta questa guida: "[Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". +> Il vRack supporta sia il routing pubblico IPv4 che IPv6 con blocchi di indirizzi Additional IP. Le istruzioni su come configurare i blocchi IPv6 sono disponibili in questa guida: "[Configurare un blocco IPv6 in un vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Questo articolo descrive la configurazione degli indirizzi Additional IP su una rete vRack. Per istruzioni sulla configurazione degli indirizzi Additional IP con un indirizzo IP primario (nell'interfaccia di rete pubblica), vedere gli articoli seguenti: +> Questo articolo è incentrato sulla configurazione di Additional IP su una rete vRack. Se si cercano indicazioni sulla configurazione di Additional IP insieme all'IP primario (sull'interfaccia di rete pubblica), consultare i seguenti articoli: > > - IPv4: -> - [Configurare un indirizzo IP come alias su un server dedicato](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configurare un indirizzo IP in alias su un server VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurare l'IP aliasing sui server dedicati](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurare l'IP aliasing su un VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [Configurare IPv6 sur un server dedicato](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configurare IPv6 su un server VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configurare IPv6 su un’istanza Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Configurare IPv6 sui server dedicati](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurare IPv6 su un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurare IPv6 su un'istanza Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Prerequisiti -- Disporre di un blocco pubblico di indirizzi IP nel proprio account, con almeno quattro indirizzi -- Aver selezionato un intervallo di indirizzi IP privati -- Disporre di un [server compatibile con la vRack](https://www.ovh.it/server_dedicati/) -- Aver attivato un servizio [vRack](https://www.ovh.it/soluzioni/vrack/) -- Essere connesso allo [Spazio Cliente OVHcloud](/links/manager) +- Un blocco pubblico di indirizzi IP nel proprio account, con un minimo di quattro indirizzi +- L'intervallo di indirizzi IP privati scelto +- Un [server compatibile con vRack](/links/bare-metal/bare-metal) +- Un servizio [vRack](/links/network/vrack) attivato nel proprio account +- Accesso allo [Spazio Cliente OVHcloud](/links/manager) > [!warning] -> Questa funzionalità può non essere disponibile o limitata sui [server dedicati **Eco**](/links/bare-metal/eco-about). +> Questa funzionalità potrebbe non essere disponibile o potrebbe essere limitata sui [server dedicati della linea di prodotti **Eco**](/links/bare-metal/eco-about). > -> Per maggiori informazioni, consulta la nostra [a confronto](/links/bare-metal/eco-compare). +> Per ulteriori informazioni, visitare la nostra [pagina di confronto](/links/bare-metal/eco-compare). ## Procedura > [!primary] > -> In questa guida utilizzeremo, a titolo di esempio, un blocco IP di 46.105.135.96/28 e l’interfaccia di rete secondaria `eth1` (dedicata alla vRack). +> A titolo di esempio utilizzeremo un blocco IP di 46.105.135.96/28 ed eth1 per l'interfaccia di rete secondaria, dedicata al vRack. > -> Sempre a titolo di esempio, il file di configurazione della rete a cui ci riferiamo si trova in `/etc/network/interfaces`. A seconda del sistema operativo utilizzato, il file equivalente potrebbe trovarsi altrove. Anche il contenuto del file potrebbe essere diverso. In caso di difficoltà, consultare la documentazione ufficiale della propria distribuzione. +> Sempre a titolo di esempio, il file di configurazione di rete a cui facciamo riferimento si trova in `/etc/network/interfaces`. Il file equivalente sul server potrebbe trovarsi altrove, a seconda del sistema operativo. Il contenuto del file potrebbe essere diverso. In caso di difficoltà, fare riferimento alla documentazione ufficiale della propria distribuzione. -### Aggiungi il blocco IP alla vRack +### Aggiungere il blocco IP al vRack > [!warning] > -> Quando un blocco IP viene aggiunto alla vRack, non è più collegato a un server fisico. +> Una volta aggiunto un blocco IP al vRack, non è più collegato a un server fisico. > -> Questa configurazione permette di configurare gli IP di uno stesso blocco su più server, a condizione che questi server siano tutti nella stessa vRack del blocco IP. Il blocco IP deve avere almeno 2 indirizzi IP utilizzabili o più per farlo. +> Questa configurazione consente di configurare gli IP dello stesso blocco su più server, a condizione che tutti questi server si trovino nello stesso vRack del blocco IP. Il blocco IP deve avere almeno 2 IP utilizzabili o più affinché ciò sia possibile. > -Nello [Spazio Cliente OVHcloud](/links/manager), accedi alla sezione `Bare Metal Cloud`{.action} e clicca su `Network`{.action}. In seguito, apri il menu `vRack`{.action} +Nello [Spazio Cliente OVHcloud](/links/manager), accedere alla sezione `Bare Metal Cloud`{.action} e cliccare su `Network`{.action}. Aprire quindi il menu `vRack`{.action}. -Seleziona la tua vRack nella lista per visualizzare la lista dei servizi ammissibili. Clicca sul blocco IP che vuoi aggiungere alla vRack e clicca su `Aggiungi`{.action}. +Selezionare il proprio vRack dall'elenco per visualizzare l'elenco dei servizi idonei. Cliccare sul blocco IP da aggiungere al vRack e poi sul pulsante `Aggiungi`{.action}. ![vrack](images/addIPblock.png){.thumbnail} -### Configura un indirizzo IP utilizzabile +### Gestire la larghezza di banda IP pubblica nel vRack + +Per impostazione predefinita, i blocchi Additional IP instradati tramite un vRack beneficiano di una larghezza di banda pubblica standard di 5 Gbps in Europa e Nord America, o di 100 Mbps nelle regioni APAC. Per ulteriori dettagli sulle opzioni disponibili, fare riferimento alle opzioni di routing pubblico sulla nostra [pagina del prodotto vRack](/links/network/vrack). + +Per rispondere alle crescenti esigenze delle infrastrutture e ai requisiti dei servizi ad alto traffico, OVHcloud propone ora ai propri clienti opzioni di larghezza di banda a pagamento. Si noti che queste opzioni si applicano **per vRack e per regione**. Poiché gli indirizzi Additional IP sono collegati a una regione precisa, qualsiasi modifica della larghezza di banda influirà sull'insieme degli indirizzi (IPv4 e IPv6) instradati verso quel vRack nella regione corrispondente. + +/// details | Durante il processo di ordine di Additional IP + +#### Scelta della larghezza di banda pubblica durante il processo di ordine + +È possibile modificare la larghezza di banda predefinita al momento di ordinare un nuovo blocco Additional IP, non appena viene selezionata una rete vRack come servizio backend. + +Per ordinare un nuovo blocco Additional IP: + +- Accedere allo [Spazio Cliente OVHcloud](/links/manager). +- Nella barra laterale sinistra, accedere alla sezione `Network`{.action}. +- Selezionare `Indirizzi IP pubblici`{.action}. +- Cliccare sul pulsante `Ordina IP`{.action} in cima alla pagina. +- Scegliere la versione IP, quindi il vRack a cui sarà associato l'Additional IP. +- Selezionare la regione del proprio Additional IP. +- Scegliere la larghezza di banda pubblica da applicare al proprio vRack per quella regione. +- Configurare le altre opzioni secondo le proprie esigenze e, successivamente, finalizzare l'ordine. + +/// + +/// details | Dalla pagina di gestione del vRack + +#### Modifica della larghezza di banda pubblica dalla pagina di gestione + +Per i blocchi Additional IP già collegati a un vRack, la larghezza di banda viene gestita direttamente dalla pagina di configurazione del servizio. + +Per accedere all'interfaccia di gestione: -Nel caso della vRack, il primo, il penultimo e l’ultimo indirizzo di un determinato blocco IP sono sempre riservati rispettivamente all’indirizzo di rete, al gateway di rete e al *broadcast* di rete. Questo significa che il primo indirizzo utilizzabile è il secondo indirizzo del blocco, come indicato di seguito: +- Nella barra laterale sinistra del Pannello di controllo, aprire `Network`{.action}. +- Selezionare `Rete privata vRack`{.action}. +- Nella colonna "Indirizzo IP pubblico e larghezza di banda", cliccare sul pulsante `Gestisci`{.action} corrispondente al vRack desiderato. + +L'interfaccia di gestione si divide in due schede: +- **All attached services**: Attualmente reindirizza alla pagina di gestione classica del vRack. Prossimamente, questa scheda elencherà in modo ottimizzato tutti i prodotti (server, progetti Cloud, ecc.) collegati al vRack. +- **Connettività IP pubblica**: Consente di gestire le opzioni di routing pubblico del proprio vRack, inclusa la larghezza di banda. + +Per modificare la larghezza di banda: + +- Andare alla scheda `Connettività IP pubblica`{.action}. +- L'interfaccia mostra finestre di gestione per regione (ad es. `eu-west-par`) associate al vRack, con la lista degli IP associati. +- Nel riquadro della regione corrispondente, cliccare su `Modifica larghezza di banda`{.action}. +- Selezionare l'opzione desiderata nel pannello di destra, quindi cliccare su `Ordina`{.action} per convalidare. +- Una volta effettuato il pagamento, la nuova larghezza di banda sarà attiva sul proprio vRack nella regione scelta dopo alcuni minuti. + +> [!primary] +> +> Il primo mese sottoscritto viene fatturato in modo proporzionale ai giorni rimanenti. La tariffa completa verrà applicata nel ciclo di fatturazione successivo. +> + +L'aumento di larghezza di banda si applicherà a tutti gli indirizzi IP di quella regione per il vRack selezionato. + +/// + +### Configurare un indirizzo IP utilizzabile + +Per i fini del vRack, il primo, il penultimo e l'ultimo indirizzo in qualsiasi blocco IP sono sempre riservati rispettivamente per l'indirizzo di rete, il gateway di rete e il broadcast di rete. Ciò significa che il primo indirizzo utilizzabile è il secondo indirizzo nel blocco, come mostrato di seguito: ```sh -46.105.135.96 # Riservato : indirizzo di rete +46.105.135.96 # Riservato: Indirizzo di rete 46.105.135.97 # Primo IP utilizzabile 46.105.135.98 46.105.135.99 @@ -83,18 +155,20 @@ Nel caso della vRack, il primo, il penultimo e l’ultimo indirizzo di un determ 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Ultimo IP utilizzabile -46.105.135.110 # Riservato : gateway di rete -46.105.135.111 # Riservato : broadcast di rete +46.105.135.109 # Ultimo IP utilizzabile +46.105.135.110 # Riservato: Gateway di rete +46.105.135.111 # Riservato: Broadcast di rete ``` -Per configurare il primo indirizzo IP utilizzabile, è necessario modificare il file di configurazione di rete come indicato qui di seguito: In questo esempio, utilizziamo la subnet mask **255.255.255.240**. +Per configurare il primo indirizzo IP utilizzabile, è necessario modificare il file di configurazione di rete, come mostrato di seguito. In questo esempio, è necessario utilizzare una subnet mask di *255.255.255.240*. > [!primary] > -> La subnet mask utilizzata in questo esempio è adatta al nostro blocco IP, ma può variare in base alla dimensione del blocco. Nel momento in cui acquisti un blocco IP, ricevi un’email con le indicazioni riguardo alla subnet mask da utilizzare. +> La subnet mask utilizzata nel nostro esempio è appropriata per il nostro blocco IP. La subnet mask potrebbe variare a seconda della dimensione del blocco. Quando si acquista il blocco IP, si riceverà un'e-mail che indicherà quale subnet mask utilizzare. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -104,37 +178,43 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` +### Creare una nuova tabella di routing IP -### Crea una nuova tabella di routing IP +Per prima cosa, è necessario scaricare e installare iproute2, un pacchetto che ci permetterà di configurare manualmente il routing IP sul server. -Come prima cosa è necessario scaricare e installare **iproute2**, un pacchetto per configurare manualmente il routing IP sul server. Pertanto, stabilisci una connessione SSH con il tuo server e inserisci il seguente comando: +Stabilire una connessione SSH al server ed eseguire il seguente comando dalla riga di comando. Questo scaricherà e installerà iproute2. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -Successivamente, è necessario creare una nuova rotta IP per la vRack. Per aggiungere una nuova regola di traffico, modifica il file come indicato di seguito: +Successivamente, è necessario creare una nuova route IP per il vRack. Aggiungeremo una nuova regola di traffico modificando il file, come mostrato di seguito: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# valori riservati +# 255 local 254 main 253 default 0 unspec -# # # -# local -# # # +# +# locale +# #1 inr.ruhep 1 vrack ``` -### Modifica il file di configurazione di rete +### Modificare il file di configurazione di rete -Infine, non ti resta che modificare il file di configurazione di rete per tenere conto della nuova regola di traffico e instradare il traffico vRack attraverso l’indirizzo di gateway di rete **46.105.135.110**. +> [!primary] +> +> A titolo di esempio, il file di configurazione di rete a cui facciamo riferimento si trova in /etc/network/interfaces. Il file equivalente sul server potrebbe trovarsi altrove, a seconda del sistema operativo. +> + +Infine, è necessario modificare il file di configurazione di rete per tenere conto della nuova regola di traffico e instradare il traffico del vRack attraverso l'indirizzo del gateway di rete **46.105.135.110**. ```sh /etc/network/interfaces @@ -150,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Riavvia il server per applicare tutte le modifiche. +Riavviare il server per applicare le modifiche oppure abilitare semplicemente la nuova interfaccia di rete: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Creare il file per l'interfaccia di rete secondaria + +Per prima cosa, è possibile copiare e utilizzare la configurazione utilizzata per l'interfaccia di rete primaria e adattarla alle proprie esigenze: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Poi accediamo al nuovo file: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +E definiamo le impostazioni IP: +```sh +# Creato automaticamente da cloud-init all'avvio dell'istanza, non modificare. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Creare una nuova tabella di routing IP + +Successivamente, è necessario creare una nuova route IP per il vRack. Aggiungeremo una nuova regola di traffico modificando il file, come mostrato di seguito: + +```sh +/etc/iproute2/rt_tables + +# +# valori riservati +# +255 local +254 main +253 default +0 unspec +# +# locale +# +#1 inr.ruhep +1 vrack +``` + +Successivamente, creare il file necessario per applicare le nuove regole: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +E incollare il seguente contenuto (ricordare di sostituire le variabili con i propri valori): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modificare il file di configurazione di rete + +Infine, è necessario modificare il file di configurazione di rete per tenere conto della nuova regola di traffico e instradare il traffico del vRack attraverso l'indirizzo del gateway di rete **46.105.135.110**. + +È possibile farlo modificando il seguente file per aggiungere route persistenti e statiche: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Incollare il seguente contenuto (ricordare di sostituire le variabili con i propri valori): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Riavviare il server per applicare le modifiche oppure abilitare semplicemente la nuova interfaccia di rete: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Step 1: Verifica e configurazione dell'interfaccia di rete secondaria + +Per prima cosa dobbiamo accedere alle informazioni della nuova interfaccia di rete: + +![verificare la seconda interfaccia di rete](images/win-ip-vrack-1.png){.thumbnail} + +Poi dobbiamo verificare le proprietà: + +![proprietà della seconda interfaccia di rete](images/win-ip-vrack-2.png){.thumbnail} + +![proprietà della seconda interfaccia di rete](images/win-ip-vrack-3.png){.thumbnail} + +#### Step 2: Configurazione IP + +Dobbiamo selezionare l'opzione ```Use the following IP address```: + +![configurazione ip](images/win-ip-vrack-4.png){.thumbnail} + +E infine possiamo definire le informazioni IP: + +![configurazione ip](images/win-ip-vrack-5b.png){.thumbnail} + +#### Step 3: Riavvio dell'interfaccia di rete + +Prima eseguiamo il processo di disabilitazione: + +![disabilitazione rete](images/win-ip-vrack-6.png){.thumbnail} + +Poi eseguiamo il processo di abilitazione: + +![abilitazione rete](images/win-ip-vrack-7.png){.thumbnail} + +### Risoluzione dei problemi + +Se non si riesce a stabilire una connessione dalla propria VM o server alla rete privata, inviare un ticket dal proprio pannello di controllo con le seguenti informazioni: + +- IP sorgente e IP destinazione +- Ifconfig -a o ipconfig /all da entrambi i server o VM (configurazione dell'interfaccia di rete) +- Ping in entrambe le direzioni +- Arp -a +- Tabella di routing + +Si prega di includere i risultati di cui sopra nel ticket. ## Per saperne di più -[Configurare due o più server dedicati nella vRack](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Configurare il vRack sui server dedicati](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Creare due o più VLAN nella vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Creare più VLAN in un vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) -[Configurare la vRack tra un’istanza Public Cloud e un server dedicato](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) +[Configurare il vRack tra il Public Cloud e un server dedicato](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Contatta la nostra Community di utenti all’indirizzo . +Contatta la nostra [Community di utenti](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pl-pl.md index 256b30a9a5c..df3c7b83318 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pl-pl.md @@ -1,77 +1,149 @@ --- -title: 'Konfiguracja bloku IP w sieci vRack' -excerpt: 'Dowiedz się, jak skonfigurować blok publicznych adresów IP w sieci vRack' -updated: 2025-06-04 +title: 'Konfiguracja bloku Additional IP w sieci vRack' +excerpt: 'Ten przewodnik pokazuje, jak skonfigurować blok publicznych adresów IP do użytku z siecią vRack.' +updated: 2026-03-09 --- + + ## Wprowadzenie -Oprócz prywatnego adresowania IP, [vRack](/links/network/vrack) umożliwia kierowanie publicznego ruchu IP przez port vRack Twojego serwera za pomocą bloku publicznych adresów IP. +Oprócz prywatnego adresowania IP, sieć [vRack](/links/network/vrack) umożliwia również kierowanie publicznego ruchu IP przez port vRack serwera przy użyciu bloku publicznych adresów IP. -**Niniejszy przewodnik wyjaśnia, jak skonfigurować blok publicznych adresów IP do zastosowania z rozwiązaniem vRack.** +**Ten przewodnik pokazuje, jak skonfigurować blok publicznych adresów IP do użytku z siecią vRack.** > [!primary] > -> vRack obsługuje adresy IPv4 i IPv6 public routing z dodatkowymi adresami IP. Możesz sfinalizować instrukcje dotyczące konfigurowania bloków IPv6 w tym przewodniku: "[Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". +> Sieć vRack obsługuje zarówno publiczny routing IPv4, jak i IPv6 z blokami adresów Additional IP. Instrukcje dotyczące konfiguracji bloków IPv6 można znaleźć w tym przewodniku: "[Konfiguracja bloku IPv6 w sieci vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Ten artykuł dotyczy konfiguracji dodatkowych adresów IP w sieci vRack. Jeśli poszukujesz wskazówek dotyczących konfiguracji Additional IP w połączeniu z primary IP (w publicznym interfejsie sieciowym), przeczytaj następujące artykuły: +> Ten artykuł skupia się na konfiguracji Additional IP w sieci vRack. Jeśli szukasz wskazówek dotyczących konfiguracji Additional IP razem z głównym IP (na publicznym interfejsie sieciowym), zapoznaj się z następującymi artykułami: > > - IPv4: -> - [Konfiguracja adresu IP jako aliasu na serwerze dedykowanym](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Konfiguracja adresu IP jako aliasu na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Konfiguracja aliasowania IP na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Konfiguracja aliasowania IP na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [Konfigurowanie adresu IPv6 na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Konfiguracja IPv6 na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). > - [Konfiguracja IPv6 na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Jak konfigurować IPv6 w instancji Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Konfiguracja IPv6 na instancji Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Wymagania początkowe -- Rezerwacja bloku publicznych adresów IP na Twoim koncie z minimalną liczbą czterech adresów -- Przygotowanie Twojego zakresu wybranych prywatnych adresów IP -- Posiadanie [serwera kompatybilnego z vRack](/links/bare-metal/bare-metal) -- Aktywacja usługi [vRack](/links/network/vrack) +- Publiczny blok adresów IP na koncie, z minimum czterema adresami +- Wybrany zakres prywatnych adresów IP +- [Serwer kompatybilny z vRack](/links/bare-metal/bare-metal) +- Usługa [vRack](/links/network/vrack) aktywowana na koncie - Dostęp do [Panelu klienta OVHcloud](/links/manager) > [!warning] -> Funkcja ta może być niedostępna lub ograniczona na [serwerach dedykowanych **Eco**](/links/bare-metal/eco-about). +> Ta funkcja może być niedostępna lub ograniczona na [serwerach dedykowanych z linii produktów **Eco**](/links/bare-metal/eco-about). > -> Aby uzyskać więcej informacji, zapoznaj się z naszym [porównaniem](/links/bare-metal/eco-compare). +> Więcej informacji znajdziesz na naszej [stronie porównawczej](/links/bare-metal/eco-compare). ## W praktyce > [!primary] > -> Jako przykład użyjemy bloku IP 46.105.135.96/28 oraz `eth1` dla dodatkowego interfejsu sieciowego dedykowanego sieci vRack. +> Dla celów przykładowych będziemy używać bloku IP 46.105.135.96/28 i eth1 dla dodatkowego interfejsu sieciowego, który jest dedykowany sieci vRack. > -> Dla przykładu, plik konfiguracyjny sieci, do którego się odnosimy, znajduje się w `/etc/network/interfaces`. W zależności od używanego systemu operacyjnego, równoważny plik może znajdować się w innym miejscu. Zawartość pliku może być również inna. Jeśli masz jakiekolwiek trudności, zapoznaj się z oficjalną dokumentacją swojej dystrybucji. +> Również dla celów przykładowych, plik konfiguracji sieci, do którego się odwołujemy, znajduje się w `/etc/network/interfaces`. Odpowiedni plik na Twoim serwerze może znajdować się w innym miejscu, w zależności od systemu operacyjnego. Zawartość pliku może być również inna. W przypadku trudności zapoznaj się z oficjalną dokumentacją swojej dystrybucji. -### Dodaj blok IP do vRack +### Dodanie bloku IP do sieci vRack > [!warning] > -> Gdy blok IP jest dodany do sieci vRack, nie jest już przypisany do fizycznego serwera. +> Po dodaniu bloku IP do sieci vRack nie jest on już przypisany do fizycznego serwera. > -> Konfiguracja ta pozwala na skonfigurowanie adresów IP tego samego bloku na kilku serwerach, pod warunkiem że wszystkie te serwery są w tej samej sieci vRack co blok IP. Aby to możliwe, blok IP musi mieć co najmniej 2 adresów IP nadających się do wykorzystania. +> Ta konfiguracja umożliwia skonfigurowanie adresów IP z tego samego bloku na wielu serwerach, pod warunkiem, że wszystkie te serwery znajdują się w tej samej sieci vRack co blok IP. Blok IP musi mieć co najmniej 2 lub więcej użytecznych adresów IP, aby było to możliwe. > -W [Panelu klienta OVHcloud](/links/manager) przejdź do sekcji `Bare Metal Cloud`{.action} i kliknij `Network`{.action}. Następnie otwórz menu `vRack`{.action}. +W [Panelu klienta OVHcloud](/links/manager) przejdź do sekcji `Bare Metal Cloud`{.action} i kliknij `Sieć`{.action}. Następnie otwórz menu `vRack`{.action}. -Wybierz z listy usługę vRack, aby wyświetlić listę usług, które chcesz zamówić. Kliknij blok IP, który chcesz dodać do sieci vRack i kliknij przycisk `Dodaj`{.action}. +Wybierz swój vRack z listy, aby wyświetlić listę kwalifikujących się usług. Kliknij blok IP, który chcesz dodać do sieci vRack, a następnie kliknij przycisk `Dodaj`{.action}. ![vrack](images/addIPblock.png){.thumbnail} -### Konfiguracja adresu IP +### Zarządzanie publiczną przepustowością IP w sieci vRack + +Domyślnie bloki Additional IP kierowane przez sieć vRack korzystają ze standardowej publicznej przepustowości 5 Gbps w Europie/Kanadzie/USA i 100 Mbps w regionach APAC. Szczegółowe informacje o dostępności można znaleźć w opcjach routingu publicznego na naszej [stronie produktu vRack](/links/network/vrack). + +Wraz ze wzrostem wymagań infrastrukturalnych użytkownicy mogą potrzebować większej przepustowości do obsługi publicznych usług o dużym natężeniu ruchu, dla których OVHcloud oferuje płatne opcje przepustowości. Należy pamiętać, że opcje przepustowości są stosowane **per vRack i per region**. Ponieważ adresy Additional IP są powiązane z regionem, każda modyfikacja przepustowości wpłynie na wszystkie adresy IP (zarówno IPv4, jak i IPv6) kierowane do konkretnego vRack w tym określonym regionie. + +/// details | Podczas procesu zamawiania Additional IP + +#### Wybór publicznej przepustowości podczas zamówienia Additional IP + +Domyślną publiczną przepustowość można zmienić podczas zamawiania nowego bloku Additional IP z siecią vRack jako backendem. + +Aby zamówić nowy blok Additional IP: + +- Zaloguj się do [Panelu klienta OVHcloud](/links/manager). +- Otwórz sekcję `Sieć`{.action} na lewym pasku bocznym. +- Wybierz `Publiczne adresy IP`{.action}. +- Kliknij przycisk `Zamów IP`{.action} w pobliżu górnej części strony. +- Wybierz wersję IP, a następnie vRack, do którego chcesz przypisać swój Additional IP. +- Wybierz region, w którym ma znajdować się Twój Additional IP. +- Wybierz publiczną przepustowość, którą chcesz zastosować do swojego vRack dla tego konkretnego regionu. +- Wypełnij pozostałe opcje według potrzeb, a następnie złóż zamówienie. + +/// + +/// details | Ze strony zarządzania vRack + +#### Modyfikacja publicznej przepustowości vRack na stronie zarządzania + +W przypadku bloków Additional IP już przypisanych do sieci vRack przepustowością można zarządzać bezpośrednio na stronie konfiguracji usługi. + +Aby uzyskać dostęp do interfejsu zarządzania: -W przypadku sieci vRack pierwszy, przedostatni i ostatni adres danego bloku IP są zawsze zarezerwowane odpowiednio dla: adresu sieci, bramy sieciowej i broadcastu sieci. Oznacza to, że pierwszy możliwy do użycia adres jest drugim adresem z bloku, jak pokazano poniżej: +- Otwórz `Sieć`{.action} na lewym pasku bocznym Panelu klienta. +- Wybierz `Prywatna sieć vRack`{.action}. +- W kolumnie "Public IP & bandwidth" kliknij przycisk `Zarządzaj`{.action} dla odpowiedniego vRack. + +Strona zarządzania jest podzielona na dwie zakładki: +- **All attached services**: Na razie przekierowuje do klasycznej strony zarządzania vRack. Wkrótce będzie wyświetlać wszystkie produkty (Serwery, Projekty Cloud itp.) aktualnie powiązane z vRack w nowy sposób. +- **Publiczny routing IP**: Zarządza opcjami publicznego routingu IP Twojego vRack, w tym publiczną przepustowością. + +Aby zmodyfikować publiczną przepustowość: + +- Przejdź do zakładki `Publiczny routing IP`{.action}. +- Interfejs wyświetla indywidualne okna zarządzania dla każdego regionu (np. `eu-west-par`) powiązanego z vRack, zawierające listę wszystkich adresów IP przypisanych do tego konkretnego regionu. +- W oknie dla odpowiedniego regionu kliknij przycisk `Zmień przepustowość`{.action}. +- Wybierz żądaną opcję przepustowości w panelu, który pojawi się po prawej stronie, a następnie kliknij `Przejdź do zamówienia`{.action}, aby zatwierdzić zamówienie. +- Po dokonaniu płatności wybrana przepustowość powinna być dostępna dla Twojego vRack w wybranym regionie po kilku minutach. + +> [!primary] +> +> Opłaty za pierwszy miesiąc są naliczane proporcjonalnie do liczby pozostałych dni, a pełna stawka obowiązuje od następnego cyklu rozliczeniowego. +> + +Wybrany upgrade przepustowości zostanie zastosowany do wszystkich adresów IP w tym regionie dla wybranego vRack. + +/// + +### Konfiguracja użytecznego adresu IP + +W sieci vRack pierwszy, przedostatni i ostatni adres w dowolnym bloku IP są zawsze zarezerwowane odpowiednio dla adresu sieci, bramki sieciowej i rozgłoszenia sieciowego. Oznacza to, że pierwszy użyteczny adres to drugi adres w bloku, jak pokazano poniżej: ```sh -46.105.135.96 # Zarezerwowany: adres sieci -46.105.135.97 # Pierwszy możliwy do użycia adres IP +46.105.135.96 # Zarezerwowany: Adres sieci +46.105.135.97 # Pierwszy użyteczny adres IP 46.105.135.98 46.105.135.99 46.105.135.100 @@ -83,20 +155,22 @@ W przypadku sieci vRack pierwszy, przedostatni i ostatni adres danego bloku IP s 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Ostatni możliwy do użycia adres IP -46.105.135.110 # Zarezerwowany: brama sieci -46.105.135.111 # Zarezerwowany: broadcast sieci +46.105.135.109 # Ostatni użyteczny adres IP +46.105.135.110 # Zarezerwowany: Bramka sieciowa +46.105.135.111 # Zarezerwowany: Rozgłoszenie sieciowe ``` -Aby skonfigurować pierwszy możliwy do użycia adres IP, edytuj plik konfiguracyjny sieci, jak wskazano poniżej. Użyj maski podsieci **255.255.255.240**. +Aby skonfigurować pierwszy użyteczny adres IP, należy edytować plik konfiguracji sieci, jak pokazano poniżej. W tym przykładzie musimy użyć maski podsieci *255.255.255.240*. > [!primary] > -> Maska podsieci użyta w tym przykładzie jest odpowiednia dla przykładowego bloku IP 46.105.135.96/28. Twoja maska podsieci może różnić się od przykładowej ze względu na wielkość Twojego bloku. Po zakupieniu bloku IP otrzymasz e-mail zawierający informacje o masce podsieci, której należy użyć. +> Maska podsieci użyta w naszym przykładzie jest odpowiednia dla naszego bloku IP. Twoja maska podsieci może się różnić w zależności od rozmiaru bloku. Po zakupie bloku IP otrzymasz e-mail z informacją, której maski podsieci należy użyć. > +### Debian/Ubuntu + ```sh -vi /etc/network/interfaces +/etc/network/interfaces auto eth1 iface eth1 inet static @@ -104,42 +178,46 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` +### Tworzenie nowej tabeli routingu IP -### Tworzenie nowej tablicy routingu IP +Najpierw musimy pobrać i zainstalować iproute2, czyli pakiet, który umożliwi nam ręczną konfigurację routingu IP na serwerze. -Pakiet “iproute2” umożliwi ręczną konfigurację routingu IP na serwerze. - -Połącz się przez SSH z Twoim serwerem i wprowadź następującą komendę, aby pobrać i zainstalować pakiet: +Nawiąż połączenie SSH z serwerem i uruchom następujące polecenie z wiersza poleceń. Spowoduje to pobranie i zainstalowanie iproute2. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -Następnie utwórz nową trasę IP dla vRack. W tym celu dodaj nową regułę ruchu, modyfikując plik, jak pokazano poniżej: +Następnie musimy utworzyć nową trasę IP dla sieci vRack. Dodamy nową regułę ruchu, modyfikując plik w następujący sposób: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# zarezerwowane wartości +# 255 local 254 main 253 default 0 unspec -# # # -# local -# # # +# +# lokalne +# #1 inr.ruhep 1 vrack ``` -### Zmodyfikuj plik konfiguracyjny sieci +### Modyfikacja pliku konfiguracji sieci -Na koniec zmodyfikuj plik konfiguracyjny sieci, aby została uwzględniona nowa reguła ruchu, i aby ruch vRack został przekierowany za pomocą adresu bramy sieciowej **46.105.135.110**. +> [!primary] +> +> Dla celów przykładowych plik konfiguracji sieci, do którego się odwołujemy, znajduje się w /etc/network/interfaces. Odpowiedni plik na Twoim serwerze może znajdować się w innym miejscu, w zależności od systemu operacyjnego. +> + +Na koniec musimy zmodyfikować plik konfiguracji sieci, aby uwzględnić nową regułę ruchu i skierować ruch vRack przez adres bramki sieciowej **46.105.135.110**. ```sh -vi /etc/network/interfaces +/etc/network/interfaces auto eth1 iface eth1 inet static @@ -152,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Zrestartuj serwer, aby zastosować wprowadzone zmiany. +Teraz uruchom ponownie serwer, aby zastosować zmiany, lub alternatywnie włącz po prostu nowy interfejs sieciowy: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Tworzenie pliku dla dodatkowego interfejsu sieciowego + +Najpierw możemy skopiować i użyć konfiguracji stosowanej dla głównego interfejsu sieciowego i dostosować ją do naszych potrzeb: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Następnie otwieramy nowy plik: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +I definiujemy ustawienia IP: +```sh +# Automatycznie utworzone przez cloud-init podczas uruchamiania instancji, nie edytować. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Tworzenie nowej tabeli routingu IP + +Następnie musimy utworzyć nową trasę IP dla sieci vRack. Dodamy nową regułę ruchu, modyfikując plik w następujący sposób: + +```sh +/etc/iproute2/rt_tables + +# +# zarezerwowane wartości +# +255 local +254 main +253 default +0 unspec +# +# lokalne +# +#1 inr.ruhep +1 vrack +``` + +Następnie utwórz plik potrzebny do zastosowania nowych reguł: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +I wklej następującą zawartość (pamiętaj, aby zastąpić nasze zmienne własnymi wartościami): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modyfikacja pliku konfiguracji sieci + +Na koniec musimy zmodyfikować plik konfiguracji sieci, aby uwzględnić nową regułę ruchu i skierować ruch vRack przez adres bramki sieciowej **46.105.135.110**. + +Możemy to osiągnąć, edytując następujący plik w celu dodania trwałych i statycznych tras: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Wklej następującą zawartość (pamiętaj, aby zastąpić nasze zmienne własnymi wartościami): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Teraz uruchom ponownie serwer, aby zastosować zmiany, lub alternatywnie włącz po prostu nowy interfejs sieciowy: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Krok 1: Sprawdzenie i konfiguracja dodatkowego interfejsu sieciowego + +Najpierw musimy uzyskać dostęp do informacji o nowym interfejsie sieciowym: + +![sprawdzenie drugiego interfejsu sieciowego](images/win-ip-vrack-1.png){.thumbnail} + +Następnie musimy sprawdzić właściwości: + +![właściwości drugiego interfejsu sieciowego](images/win-ip-vrack-2.png){.thumbnail} + +![właściwości drugiego interfejsu sieciowego](images/win-ip-vrack-3.png){.thumbnail} + +#### Krok 2: Konfiguracja IP + +Musimy wybrać opcję ```Use the following IP address```: + +![konfiguracja ip](images/win-ip-vrack-4.png){.thumbnail} + +I możemy w końcu zdefiniować informacje o adresie IP: + +![konfiguracja ip](images/win-ip-vrack-5b.png){.thumbnail} + +#### Krok 3: Ponowne uruchomienie interfejsu sieciowego + +Najpierw wykonujemy proces wyłączania: + +![wyłączanie sieci](images/win-ip-vrack-6.png){.thumbnail} + +Następnie wykonujemy proces włączania: + +![włączanie sieci](images/win-ip-vrack-7.png){.thumbnail} + +### Rozwiązywanie problemów + +Jeśli nie możesz nawiązać połączenia z maszyny wirtualnej lub serwera z siecią prywatną, wyślij nam ticket z Panelu klienta z następującymi informacjami: + +- Źródłowy adres IP i docelowy adres IP +- Ifconfig -a lub ipconfig /all z obu serwerów lub maszyn wirtualnych (konfiguracja interfejsu sieciowego) +- Ping w obu kierunkach +- Arp -a +- Tabela routingu + +Dołącz wyniki powyższych poleceń do swojego ticketu. ## Sprawdź również -[Konfiguracja kilku serwerów dedykowanych w sieci vRack](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Konfiguracja sieci vRack na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Tworzenie kilku sieci VLAN w prywatnej sieci vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Tworzenie wielu sieci VLAN w ramach vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) -[Konfiguracja sieci vRack między Public Cloud a serwerem dedykowanym](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) +[Konfiguracja sieci vRack między usługą Public Cloud a serwerem dedykowanym](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) -Przyłącz się do społeczności naszych użytkowników na stronie . +Dołącz do [grona naszych użytkowników](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pt-pt.md index f3458f97ec3..4c4f536926f 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.pt-pt.md @@ -1,76 +1,148 @@ --- -title: 'Configurar um bloco de endereços IP no vRack' -excerpt: 'Saiba como configurar um bloco de endereços IP públicos no vRack' -updated: 2025-06-04 +title: 'Configurar um bloco de Additional IP num vRack' +excerpt: 'Saiba como configurar um bloco de endereços IP públicos num vRack.' +updated: 2026-03-09 --- + + ## Objetivo -Além do direcionamento IP privado, o [vRack](/links/network/vrack) permite direcionar o tráfego IP público através da porta vRack do servidor através de um bloco de endereços IP públicos. +Para além do endereçamento IP privado, o [vRack](/links/network/vrack) permite também encaminhar o tráfego IP público através da porta vRack do servidor utilizando um bloco de endereços IP públicos. -**Este manual explica como configurar um bloco de endereços IP públicos no vRack.** +**Este guia mostra como configurar um bloco de endereços IP públicos para utilização com o vRack.** > [!primary] > -> O vRack suporta o roteamento público IPv4 e IPv6 com blocos de endereços Additional IP. Encontre as instruções sobre a configuração de blocos IPv6 neste guia: "[Configuring an IPv6 block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". +> O vRack suporta tanto o routing público IPv4 como IPv6 com blocos de endereços Additional IP. Pode encontrar as instruções sobre como configurar blocos IPv6 neste guia: "[Configurar um bloco IPv6 num vRack](/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack)". > > [!primary] > -> Este artigo detalha a configuração de endereços Additional IP numa rede vRack. Se você estiver procurando instruções sobre como configurar endereços Additional IP com um endereço IP principal (na interface de rede pública), consulte os seguintes artigos: +> Este artigo foca-se na configuração de Additional IP numa rede vRack. Se procura orientações sobre a configuração de Additional IP em conjunto com o IP principal (na interface de rede pública), consulte os seguintes artigos: > > - IPv4: -> - [Configurar um endereço IP como alias num servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configurar um endereço IP como alias num servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar o IP aliasing em servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar o IP aliasing num VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > > - IPv6: -> - [Configurar IPv6 em servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar o IPv6 em servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). > - [Configurar o IPv6 num VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). > - [Configurar o IPv6 numa instância Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > ## Requisitos -- Ter reservado um bloco público de endereços IP na sua conta, com um mínimo de quatro endereços. -- Ter acesso ao intervalo de endereços de IP privados escolhidos. -- Dispor de um [servidor compatível com o vRack](/links/bare-metal/bare-metal). -- Ter ativado um serviço [vRack](/links/network/vrack). -- Ter acesso à [Área de Cliente OVHcloud](/links/manager). +- Um bloco público de endereços IP na sua conta, com um mínimo de quatro endereços +- O intervalo de endereços IP privados escolhido +- Um [servidor compatível com vRack](/links/bare-metal/bare-metal) +- Um serviço [vRack](/links/network/vrack) ativado na sua conta +- Acesso à [área de cliente OVHcloud](/links/manager) > [!warning] -> Esta funcionalidade pode estar indisponível ou limitada nos [servidores dedicados **Eco**](/links/bare-metal/eco-about). +> Esta funcionalidade pode não estar disponível ou pode estar limitada nos [servidores dedicados da linha de produtos **Eco**](/links/bare-metal/eco-about). > -> Para mais informações, consulte o nosso [comparativo](/links/bare-metal/eco-compare). +> Visite a nossa [página de comparação](/links/bare-metal/eco-compare) para mais informações. ## Instruções > [!primary] > -> A título de exemplo, iremos utilizar um bloco de endereços IP 46.105.135.96/28 e a interface de rede secundária `eth1` (dedicada ao vRack). +> A título de exemplo, utilizaremos um bloco IP de 46.105.135.96/28 e eth1 para a interface de rede secundária, dedicada ao vRack. > -> Também a título de exemplo, o ficheiro de configuração de rede a que nos referimos está localizado em `/etc/network/interfaces`. Dependendo do sistema operativo utilizado, o ficheiro equivalente pode estar localizado noutro local. O conteúdo do ficheiro também pode ser diferente. Se tiver alguma dificuldade, por favor consulte a documentação oficial da sua distribuição. +> Também a título de exemplo, o ficheiro de configuração de rede ao qual nos referimos encontra-se em `/etc/network/interfaces`. O ficheiro equivalente no seu servidor pode estar noutro local, dependendo do sistema operativo. O conteúdo do ficheiro também pode ser diferente. Se tiver dificuldades, consulte a documentação oficial da sua distribuição. ### Adicionar o bloco IP ao vRack > [!warning] > -> Quando um bloco IP é adicionado ao vRack, este deixa de estar ligado a um servidor físico. +> Assim que um bloco IP é adicionado ao vRack, deixa de estar associado a um servidor físico. > -> Esta configuração permite configurar endereços IP de um mesmo bloco em vários servidores, desde que todos estejam no mesmo vRack que o bloco IP. O bloco IP deve ter pelo menos 2 endereços IP utilizáveis ou mais para que isso seja possível. +> Esta configuração permite-lhe configurar IPs do mesmo bloco em vários servidores, desde que todos esses servidores estejam no mesmo vRack que o bloco IP. O bloco IP deve ter pelo menos 2 IPs utilizáveis ou mais para que isso seja possível. > -Na sua [Área de Cliente OVHcloud](/links/manager), vá à secção `Bare Metal Cloud`{.action} e clique em `Network`{.action}. A seguir, abra o menu `vRack`{.action}. +Na sua [área de cliente OVHcloud](/links/manager), aceda à secção `Bare Metal Cloud`{.action} e clique em `Network`{.action}. Em seguida, abra o menu `vRack`{.action}. -Selecione o seu vRack na lista para apresentar a lista dos serviços elegíveis. Clique no bloco IP que deseja adicionar ao vRack e clique no botão `Adicionar`{.action}. +Selecione o seu vRack na lista para exibir a lista de serviços elegíveis. Clique no bloco IP que deseja adicionar ao vRack e clique no botão `Adicionar`{.action}. ![vrack](images/addIPblock.png){.thumbnail} +### Gerir a largura de banda IP pública no vRack + +Por predefinição, os blocos Additional IP encaminhados através de um vRack beneficiam de uma largura de banda pública padrão de 5 Gbps na Europa e na América do Norte, ou de 100 Mbps nas regiões APAC. Para mais detalhes sobre as opções disponíveis, consulte as opções de routing público na nossa [página do produto vRack](/links/network/vrack). + +Para responder às crescentes necessidades das infraestruturas e aos requisitos dos serviços de alto tráfego, a OVHcloud oferece agora aos seus clientes opções de largura de banda pagas. Tenha em atenção que estas opções se aplicam **por vRack e por região**. Uma vez que os endereços Additional IP estão associados a uma região precisa, qualquer modificação da largura de banda afetará o conjunto dos endereços (IPv4 e IPv6) encaminhados para esse vRack na região correspondente. + +/// details | Durante o processo de encomenda de Additional IP + +#### Escolha da largura de banda pública durante o processo de encomenda + +É possível modificar a largura de banda predefinida no momento de encomendar um novo bloco Additional IP, desde que seja selecionada uma rede vRack como serviço backend. + +Para encomendar um novo bloco Additional IP: + +- Inicie sessão na [área de cliente OVHcloud](/links/manager). +- Na barra lateral esquerda, aceda à secção `Network`{.action}. +- Selecione `Endereços IP públicos`{.action}. +- Clique no botão `Encomendar IPs`{.action} no topo da página. +- Escolha a versão IP e, em seguida, o vRack ao qual o Additional IP será associado. +- Selecione a região do seu Additional IP. +- Escolha a largura de banda pública a aplicar ao seu vRack para essa região. +- Configure as outras opções de acordo com as suas necessidades e, em seguida, finalize a encomenda. + +/// + +/// details | A partir da página de gestão do vRack + +#### Modificação da largura de banda pública a partir da página de gestão + +Para os blocos Additional IP já associados a um vRack, a largura de banda é gerida diretamente a partir da página de configuração do serviço. + +Para aceder à interface de gestão: + +- Na barra lateral esquerda do Painel de controlo, abra `Network`{.action}. +- Selecione `Rede privada vRack`{.action}. +- Na coluna "Endereço IP público e largura de banda", clique no botão `Gerir`{.action} correspondente ao vRack pretendido. + +A interface de gestão divide-se em dois separadores: +- **All attached services**: Atualmente redireciona para a página clássica de gestão do vRack. Em breve, este separador listará de forma otimizada todos os produtos (servidores, projetos Cloud, etc.) associados ao vRack. +- **Conectividade IP pública**: Permite gerir as opções de routing público do seu vRack, incluindo a largura de banda. + +Para modificar a largura de banda: + +- Vá ao separador `Conectividade IP pública`{.action}. +- A interface apresenta janelas de gestão por região (por exemplo, `eu-west-par`) associadas ao vRack, com a lista dos IPs associados. +- No bloco da região correspondente, clique em `Modificar largura de banda`{.action}. +- Selecione a opção pretendida no painel da direita e, em seguida, clique em `Encomendar`{.action} para validar. +- Após o pagamento, a nova largura de banda estará ativa no seu vRack na região escolhida após alguns minutos. + +> [!primary] +> +> O primeiro mês subscrito é faturado de forma proporcional aos dias restantes. A tarifa completa será aplicada no próximo ciclo de faturação. +> + +O aumento de largura de banda será aplicado a todos os endereços IP dessa região para o vRack selecionado. + +/// + ### Configurar um endereço IP utilizável -No caso do vRack, o primeiro, o penúltimo e o último endereço de um bloco de endereços IP estão sempre reservados, respetivamente, para o endereço da rede, ao gateway da rede e ao *broadcast* da rede. Isto significa que o primeiro endereço utilizável é o segundo endereço do bloco, como indicado a seguir: +Para fins do vRack, o primeiro, o penúltimo e o último endereço em qualquer bloco IP são sempre reservados para o endereço de rede, o gateway de rede e o broadcast de rede, respetivamente. Isto significa que o primeiro endereço utilizável é o segundo endereço no bloco, como se mostra abaixo: ```sh -46.105.135.96 # Reservado: endereço de rede +46.105.135.96 # Reservado: Endereço de rede 46.105.135.97 # Primeiro IP utilizável 46.105.135.98 46.105.135.99 @@ -83,18 +155,20 @@ No caso do vRack, o primeiro, o penúltimo e o último endereço de um bloco de 46.105.135.106 46.105.135.107 46.105.135.108 -46.105.135.109 # Último IP utilizável -46.105.135.110 # Reservado: gateway de rede -46.105.135.111 # Reservado: broadcast +46.105.135.109 # Último IP utilizável +46.105.135.110 # Reservado: Gateway de rede +46.105.135.111 # Reservado: Broadcast de rede ``` -Para configurar o primeiro endereço IP utilizável, é preciso editar o ficheiro de configuração de rede, como indicado abaixo. Neste exemplo, utilize uma máscara de sub-rede **255.255.255.240**. +Para configurar o primeiro endereço IP utilizável, é necessário editar o ficheiro de configuração de rede, como se mostra abaixo. Neste exemplo, precisamos de utilizar uma máscara de sub-rede de *255.255.255.240*. > [!primary] > -> A máscara de sub-rede utilizada neste exemplo adequa-se ao nosso bloco de endereços IP. A sua máscara de sub-rede pode diferir em função da dimensão do bloco. Quando comprar o seu bloco de endereços IP, receberá um e-mail com a máscara de sub-rede que deve utilizar. +> A máscara de sub-rede utilizada no nosso exemplo é adequada para o nosso bloco IP. A sua máscara de sub-rede pode variar consoante o tamanho do seu bloco. Quando adquirir o seu bloco IP, receberá um e-mail que lhe indicará qual a máscara de sub-rede a utilizar. > +### Debian/Ubuntu + ```sh /etc/network/interfaces @@ -104,39 +178,43 @@ address 46.105.135.97 netmask 255.255.255.240 broadcast 46.105.135.111 ``` +### Criar uma nova tabela de routing IP -### Criar uma nova tabela de roteamento IP - -Antes de mais, é preciso descarregar e instalar o “iproute2”, um pacote que permitirá configurar manualmente o roteamento IP no servidor. +Em primeiro lugar, precisamos de descarregar e instalar o iproute2, que é um pacote que nos permitirá configurar manualmente o routing IP no servidor. -A seguir, estabeleça uma ligação SSH ao seu servidor e utilize o comando seguinte para descarregar e instalar o pacote: +Estabeleça uma ligação SSH ao servidor e execute o seguinte comando a partir da linha de comandos. Isto irá descarregar e instalar o iproute2. ```sh -apt-get install iproute2 +# apt-get install iproute2 ``` -Agora tem de criar uma nova rota IP para o vRack. Para isso, basta adicionar uma nova regra de tráfego alterando o ficheiro, tal como indicado a seguir: +Em seguida, precisamos de criar uma nova rota IP para o vRack. Adicionaremos uma nova regra de tráfego modificando o ficheiro, como se mostra abaixo: ```sh /etc/iproute2/rt_tables -# # # -# reserved values -# # # +# +# valores reservados +# 255 local 254 main 253 default 0 unspec -# # # +# # local -# # # +# #1 inr.ruhep 1 vrack ``` ### Modificar o ficheiro de configuração de rede -Por fim, resta modificar o ficheiro de configuração de rede para ter em conta a nova regra de tráfego e encaminhar o tráfego vRack através do endereço do gateway de rede **46.105.135.110**. +> [!primary] +> +> A título de exemplo, o ficheiro de configuração de rede ao qual nos referimos encontra-se em /etc/network/interfaces. O ficheiro equivalente no seu servidor pode estar noutro local, dependendo do sistema operativo. +> + +Por último, precisamos de modificar o ficheiro de configuração de rede para ter em conta a nova regra de tráfego e encaminhar o tráfego do vRack através do endereço do gateway de rede **46.105.135.110**. ```sh /etc/network/interfaces @@ -152,14 +230,150 @@ post-up ip rule add from 46.105.135.96/28 table vrack post-up ip rule add to 46.105.135.96/28 table vrack ``` -Reinicie o servidor para aplicar as modificações realizadas. +Reinicie agora o servidor para aplicar as alterações ou, em alternativa, ative simplesmente a nova interface de rede: + +```sh +ip link set eth1 up +``` + +### CentOS 6/7 + +#### Criar o ficheiro para a interface de rede secundária + +Em primeiro lugar, podemos copiar e utilizar a configuração utilizada para a interface de rede primária e ajustá-la de acordo com as nossas necessidades: + +```sh +sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +Em seguida, acedemos ao novo ficheiro: + +```sh +sudo nano /etc/sysconfig/network-scripts/ifcfg-eth1 +``` +E definimos as configurações de IP: +```sh +# Criado automaticamente pelo cloud-init no arranque da instância, não editar. +# +DEVICE=eth1 +BOOTPROTO=static +ONBOOT=yes +USERCTL=no +IPV6INIT=no +PEERDNS=yes +TYPE=Ethernet +NETMASK=255.255.255.240 +IPADDR=46.105.135.97 +ARP=yes +``` + +### Criar uma nova tabela de routing IP + +Em seguida, precisamos de criar uma nova rota IP para o vRack. Adicionaremos uma nova regra de tráfego modificando o ficheiro, como se mostra abaixo: + +```sh +/etc/iproute2/rt_tables + +# +# valores reservados +# +255 local +254 main +253 default +0 unspec +# +# local +# +#1 inr.ruhep +1 vrack +``` + +Em seguida, crie o ficheiro necessário para aplicar as novas regras: +```sh +nano /etc/sysconfig/network-scripts/rule-eth1 +``` + +E cole o seguinte conteúdo (lembre-se de substituir as nossas variáveis pelos seus próprios valores): + +```sh +from 46.105.135.96/28 table vrack +to 46.105.135.96/28 table vrack +``` + +### Modificar o ficheiro de configuração de rede + +Por último, precisamos de modificar o ficheiro de configuração de rede para ter em conta a nova regra de tráfego e encaminhar o tráfego do vRack através do endereço do gateway de rede **46.105.135.110**. + +Podemos fazê-lo editando o seguinte ficheiro para adicionar rotas persistentes e estáticas: + +```sh +nano /etc/sysconfig/network-scripts/route-eth1 +``` + +Cole o seguinte conteúdo (lembre-se de substituir as nossas variáveis pelos seus próprios valores): + +```sh +46.105.135.96/28 dev eth1 table vrack +default via 46.105.135.110 dev eth1 table vrack +``` + +Reinicie agora o servidor para aplicar as alterações ou, em alternativa, ative simplesmente a nova interface de rede: + +```sh +ip link set eth1 up +``` + +### Windows Server 2012/2016 + +#### Passo 1: Verificar e configurar a interface de rede secundária + +Primeiro, devemos aceder às informações da nova interface de rede: + +![verificar a segunda interface de rede](images/win-ip-vrack-1.png){.thumbnail} + +Em seguida, devemos verificar as propriedades: + +![propriedades da segunda interface de rede](images/win-ip-vrack-2.png){.thumbnail} + +![propriedades da segunda interface de rede](images/win-ip-vrack-3.png){.thumbnail} + +#### Passo 2: Configuração de IP + +Devemos selecionar a opção ```Use the following IP address```: + +![configuração de ip](images/win-ip-vrack-4.png){.thumbnail} + +E podemos finalmente definir as informações de IP: + +![configuração de ip](images/win-ip-vrack-5b.png){.thumbnail} + +#### Passo 3: Reiniciar a interface de rede + +Primeiro, realizamos o processo de desativação: + +![desativar rede](images/win-ip-vrack-6.png){.thumbnail} + +Em seguida, realizamos o processo de ativação: + +![ativar rede](images/win-ip-vrack-7.png){.thumbnail} + +### Resolução de problemas + +Se não conseguir estabelecer uma ligação a partir da sua VM ou servidor para a rede privada, envie-nos um ticket a partir do seu painel de controlo com o seguinte: + +- IP de origem e IP de destino +- Ifconfig -a ou ipconfig /all de ambos os servidores ou VMs (configuração da interface de rede) +- Ping em ambas as direções +- Arp -a +- Tabela de routing + +Por favor, inclua os resultados acima no seu ticket. ## Quer saber mais? -[Configurar vários servidores dedicados no vRack](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) +[Configurar o vRack nos servidores dedicados](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server) -[Criar várias VLAN no vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) +[Criar múltiplas VLANs num vRack](/pages/bare_metal_cloud/dedicated_servers/creating-multiple-vlans-in-a-vrack) [Configurar o vRack entre o Public Cloud e um servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server) - -Fale com a nossa comunidade de utilizadores: . + +Fale com a nossa [comunidade de utilizadores](/links/community). From d861f23afb55b196bfaf93a7572e5d6f887c39aa Mon Sep 17 00:00:00 2001 From: benchbzh Date: Mon, 9 Mar 2026 16:26:10 +0100 Subject: [PATCH 11/12] minor updates on IPv6 guide --- .../configure-an-ipv6-in-a-vrack/guide.de-de.md | 6 +++--- .../configure-an-ipv6-in-a-vrack/guide.en-asia.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-au.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-ca.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-gb.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-ie.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-sg.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.en-us.md | 8 ++++---- .../configure-an-ipv6-in-a-vrack/guide.es-es.md | 6 +++--- .../configure-an-ipv6-in-a-vrack/guide.es-us.md | 6 +++--- .../configure-an-ipv6-in-a-vrack/guide.fr-ca.md | 4 ++-- .../configure-an-ipv6-in-a-vrack/guide.fr-fr.md | 4 ++-- .../configure-an-ipv6-in-a-vrack/guide.it-it.md | 6 +++--- .../configure-an-ipv6-in-a-vrack/guide.pl-pl.md | 6 +++--- .../configure-an-ipv6-in-a-vrack/guide.pt-pt.md | 6 +++--- 15 files changed, 50 insertions(+), 50 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md index 0833871bbcc..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md @@ -1,5 +1,5 @@ --- -title: Einen Additional IPv6-Block in einem vRack konfigurieren (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-au.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-au.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ca.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ca.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-gb.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ie.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-ie.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-sg.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-sg.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-us.md index e630f03a6a0..8ad25250a6a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-us.md @@ -1,6 +1,6 @@ --- -title: Configuring an Additional IPv6 block in a vRack -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack +title: Configuring an IPv6 block in a vRack +excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-es.md index 6bcca4c9afb..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-es.md @@ -1,5 +1,5 @@ --- -title: Configurar un bloque Additional IPv6 en un vRack (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md index 6bcca4c9afb..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md @@ -1,5 +1,5 @@ --- -title: Configurar un bloque Additional IPv6 en un vRack (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md index 46bad6a3c85..183722a3836 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md @@ -1,6 +1,6 @@ --- -title: Configurer un bloc Additional IPv6 dans un vRack -excerpt: "Ce guide vous montrera comment configurer un bloc d'adresses IPv6 publiques à utiliser dans un vRack" +title: Configurer un bloc IPv6 dans un vRack +excerpt: "Découvrez comment configurer un bloc d'adresses IPv6 publiques à utiliser dans un vRack" updated: 2026-03-09 --- diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md index 46bad6a3c85..183722a3836 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-fr.md @@ -1,6 +1,6 @@ --- -title: Configurer un bloc Additional IPv6 dans un vRack -excerpt: "Ce guide vous montrera comment configurer un bloc d'adresses IPv6 publiques à utiliser dans un vRack" +title: Configurer un bloc IPv6 dans un vRack +excerpt: "Découvrez comment configurer un bloc d'adresses IPv6 publiques à utiliser dans un vRack" updated: 2026-03-09 --- diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.it-it.md index cde816d293a..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.it-it.md @@ -1,5 +1,5 @@ --- -title: Configurare un blocco Additional IPv6 in un vRack (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md index 02ac3cab6a1..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md @@ -1,5 +1,5 @@ --- -title: Konfiguracja bloku Additional IPv6 w sieci vRack (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md index 97edad5e7de..6ef93a06ea9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md @@ -1,5 +1,5 @@ --- -title: Configurar um bloco Additional IPv6 numa vRack (EN) +title: Configuring an IPv6 block in a vRack (EN) excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack updated: 2026-03-09 --- @@ -303,7 +303,7 @@ First, let's allow our host to accept Router Advertisements (for autoconfigurati $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Important to note is that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. Then, simply bring up the interface: @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere in the Internet): +And traceroute from a remote host (somewhere on the internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 From eafcd8ba4845ce6d0a8edd02c4430eef479597eb Mon Sep 17 00:00:00 2001 From: benchbzh Date: Tue, 10 Mar 2026 10:59:50 +0100 Subject: [PATCH 12/12] translation for IPv6 guide and minor other updates --- .../guide.de-de.md | 415 +++++++++-------- .../guide.en-asia.md | 4 +- .../guide.en-au.md | 4 +- .../guide.en-ca.md | 4 +- .../guide.en-gb.md | 4 +- .../guide.en-ie.md | 4 +- .../guide.en-sg.md | 4 +- .../guide.en-us.md | 4 +- .../guide.es-es.md | 417 +++++++++-------- .../guide.es-us.md | 417 +++++++++-------- .../guide.fr-ca.md | 4 +- .../guide.fr-fr.md | 4 +- .../guide.it-it.md | 419 +++++++++-------- .../guide.pl-pl.md | 426 +++++++++--------- .../guide.pt-pt.md | 417 +++++++++-------- .../guide.de-de.md | 4 +- .../guide.en-asia.md | 4 +- .../guide.en-au.md | 4 +- .../guide.en-ca.md | 4 +- .../guide.en-gb.md | 4 +- .../guide.en-ie.md | 4 +- .../guide.en-sg.md | 4 +- .../guide.en-us.md | 4 +- .../guide.es-es.md | 6 +- .../guide.es-us.md | 6 +- .../guide.fr-ca.md | 4 +- .../guide.fr-fr.md | 4 +- .../guide.it-it.md | 4 +- .../guide.pl-pl.md | 4 +- .../guide.pt-pt.md | 4 +- .../meta.yaml | 1 - 31 files changed, 1303 insertions(+), 1309 deletions(-) diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md index 6ef93a06ea9..69a6548735b 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.de-de.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack (EN) -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack -updated: 2026-03-09 +title: Einen Additional-IPv6-Block in einem vRack konfigurieren +excerpt: "Erfahren Sie, wie Sie einen Block öffentlicher IPv6-Adressen für die Verwendung in einem OVHcloud vRack-Netzwerk konfigurieren" +updated: 2026-03-11 --- -## Objective +## Ziel -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +Das vRack-Netzwerk dient als globales privates Netzwerk, das verschiedene OVHcloud-Produkte verbindet und die Erstellung anspruchsvoller Netzwerklösungen ermöglicht. Über die Erleichterung privater Verbindungen hinaus unterstützt es auch das Routing öffentlicher IP-Adressen. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Diese Anleitung beschreibt die Konfiguration von Additional-IPv6-Adressblöcken innerhalb eines vRack-Netzwerks.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> Das vRack unterstützt sowohl IPv4- als auch IPv6-öffentliches Routing mit Additional-IP-Adressblöcken. Die Anleitung zur Konfiguration von IPv4-Blöcken finden Sie hier: [Einen IP-Block im vRack konfigurieren](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Dieser Artikel behandelt die Additional-IP-Konfiguration über ein vRack-Netzwerk. Wenn Sie Informationen zur Additional-IP-Konfiguration zusammen mit einer primären IP (auf dem öffentlichen Netzwerkinterface) suchen, lesen Sie die folgenden Anleitungen: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [IP-Aliasing auf Dedicated Servern konfigurieren](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [IP-Aliasing auf einem VPS konfigurieren](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [IPv6 auf Dedicated Servern konfigurieren](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [IPv6 auf einem VPS konfigurieren](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [IPv6 auf einer Public-Cloud-Instanz konfigurieren](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction +## Einleitung -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +IPv6 revolutioniert die Vernetzung innerhalb des OVHcloud vRack, indem es die Einschränkungen von IPv4 überwindet und Funktionen für das moderne Internet einführt. Die Einführung ist eine direkte Reaktion auf den Bedarf an umfangreicheren, sichereren und anspruchsvolleren Internet-Architekturen. Dies sind die wichtigsten Vorteile der IPv6-Integration mit dem vRack: -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +- **Flexibilität für anspruchsvolle Netzwerke**: IPv6 vergrößert den Adressraum erheblich und bietet die nötige Flexibilität zum Skalieren der Infrastruktur, zur Verwaltung von Failover-Szenarien und zur Unterstützung größerer Lösungen. Dadurch können Netzwerke ohne die Adressierungsbeschränkungen von IPv4 wachsen und sich anpassen. -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Hierarchisches Routing und Segmentierung**: IPv6 ermöglicht effizientes hierarchisches Routing und logische Infrastruktursegmentierung. Dies verbessert die Verwaltbarkeit und Sicherheit des Netzwerks - ideal für den Wiederverkauf von VMs mit dedizierten Subnetzen oder die Aufteilung der Infrastruktur in distinct Segmente. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Niedrige Latenz**: Native End-to-End-IPv6-Konnektivität kann als Enabler für latenzempfindliche Dienste wie Media-Streaming dienen, da viele neuere Provider-Netzwerke nativ mit IPv6 aufgebaut sind. In solchen Netzwerken bringt die Nutzung von IPv4-Diensten zusätzliche Latenz (und Kosten) mit sich. -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +Durch die Nutzung von IPv6 innerhalb des vRack können OVHcloud-Nutzer eine sicherere, effizientere und skalierbarere Netzwerkumgebung genießen, die den Anforderungen der modernen Internetnutzung gerecht wird. +## Voraussetzungen -## Requirements - -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Sie verfügen über einen aktiven [vRack](/links/network/vrack)-Dienst in Ihrem Account. +- Sie verfügen über einen [vRack-kompatiblen Server](/links/network/vrack), der mit Ihrem vRack-Netzwerk verbunden ist. +- Sie haben Zugang zum [OVHcloud Kundencenter](/links/manager). > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Diese Funktion kann auf Servern der [**Eco**-Produktlinie](/links/bare-metal/eco-about) eingeschränkt oder nicht verfügbar sein. > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Weitere Informationen finden Sie auf unserer [Vergleichsseite](/links/bare-metal/eco-compare). -## Instructions +## In der praktischen Anwendung -### Obtaining a new Additional IPv6 block +### Einen neuen Additional-IPv6-Block anfordern -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Beim Anfordern eines neuen Additional-IPv6-Blocks ist zu beachten, dass die Zuteilung regional erfolgt. Das bedeutet, dass der erhaltene IPv6-Block an eine bestimmte Region gebunden ist, die festlegt, wo der öffentliche Datenverkehr in Ihr vRack-Netzwerk eintritt (also wo sich das Gateway befindet). -/// details | Request a new Additional IPv6 block +/// details | Einen neuen Additional-IPv6-Block anfordern -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Sie können Ihren neuen zusätzlichen IPv6-Block [hier](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip) bestellen. -![configuration page](images/500.png){.thumbnail} +![Konfigurationsseite](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +Folgen Sie anschließend den schrittweisen Anweisungen. -Your new Additional IPv6 will then be available on your vRack configuration page. +Ihr neues Additional IPv6 ist dann auf der Konfigurationsseite Ihres vRack verfügbar. /// -### Configuring IPv6 in a vRack (basic mode) +### IPv6 in einem vRack konfigurieren (Basismodus) -In this section we will present basic IPv6 setup for your vRack connected hosts. +In diesem Abschnitt stellen wir die grundlegende IPv6-Einrichtung für Ihre mit dem vRack verbundenen Hosts vor. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![IPv6 in einem vRack konfigurieren](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +Das obige Beispiel zeigt zwei Hosts, deren vRack-seitige Interfaces mit öffentlichen IPv6-Adressen konfiguriert sind. Ein Host ist manuell konfiguriert, während dem anderen eine IP-Adresse automatisch über SLAAC zugewiesen wird. Alle IP-Adressen gehören zum ersten /64-Subnetz aus einem gegebenen öffentlichen /56-Additional-IPv6-Block. Beide nutzen das vRack-Interface für die öffentliche IPv6-Konnektivität. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +Das Standard-Gateway für das erste /64-Subnetz (das gebrückte) ist die erste Adresse aus dem /56-Block. In diesem Beispiel ist es `2001:41d0:abcd:ef00::1`. Dies wird über SLAAC verteilt, muss aber manuell konfiguriert werden (als Standard-Route), wenn SLAAC deaktiviert ist. Weitere Informationen finden Sie im Abschnitt **Statische IP-Konfiguration** weiter unten. -/// details | Via the OVHcloud Control Panel +/// details | Über das OVHcloud Kundencenter -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Öffnen Sie `Network`{.action} in der linken Seitenleiste. +- Öffnen Sie `Privates vRack-Netzwerk`{.action}. +- Wählen Sie das betreffende vRack aus. -![vRack management](images/700.png){.thumbnail} +![vRack-Verwaltung](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +Auf der linken Seite sind die verfügbaren Optionen (konfigurierbare Dienste) aufgelistet. -On the right you see what is already configured with your vRack. +Auf der rechten Seite sehen Sie, was bereits mit Ihrem vRack konfiguriert ist. -Select your new Additional IPv6 and add it to your vRack. +Wählen Sie Ihr neues Additional IPv6 aus und fügen Sie es Ihrem vRack hinzu. -![vRack selection](images/701.png){.thumbnail} +![vRack-Auswahl](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +Ihr neues Additional IPv6 ist nun Ihrem vRack hinzugefügt. -### Static IP configuration +### Statische IP-Konfiguration -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Sobald der Additional-IPv6-/56-Block einem vRack-Netzwerk zugewiesen ist, wird das erste /64-Subnetz damit gebrückt. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Das bedeutet, dass Sie diese IPs problemlos auf Ihren Hosts mit statischer IP-Konfiguration auf vRack-Interfaces verwenden können (einen Konfigurationsbeispiel auf der Host-Seite finden Sie im nächsten Abschnitt). -### Automatic IP configuration (SLAAC) +### Automatische IP-Konfiguration (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Um die IP-Adressierung in Ihrem Netzwerk zu vereinfachen, können Sie SLAAC verwenden. Es kann nur pro gebrücktem Subnetz aktiviert werden und kann für das erste /64 Ihres Blocks (dieses ist immer gebrückt) jederzeit mit diesem Regler aktiviert werden: -![enabling SLAAC](images/702.png){.thumbnail} +![SLAAC aktivieren](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Vergessen Sie nicht, SLAAC auf Ihrem Host-Rechner zu konfigurieren. /// -/// details | Via the APIv6 (alternative way) +/// details | Über die APIv6 (alternativer Weg) -### Attributing an Additional IPv6 to a vRack +### Einem vRack ein Additional IPv6 zuweisen -When you request an additional IPv6, it is automatically assigned to your vRack. +Wenn Sie ein zusätzliches IPv6 anfordern, wird es automatisch Ihrem vRack zugewiesen. -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Wenn Sie dieses neue Additional IPv6 aus Ihrem vRack entfernt haben, können Sie es mit dieser POST-Methode erneut zuweisen: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Wie im folgenden Beispiel: ![api post add block](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Verwenden Sie den folgenden Aufruf, um zu überprüfen, ob das IPv6 zugewiesen wurde: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Wie im folgenden Beispiel: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Jetzt sehen wir unseren Block mit einem vRack konfiguriert. Der nächste Schritt ist die Konfiguration des Hosts oder der VMs. -### Static IP configuration +### Statische IP-Konfiguration -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Sobald der Additional-IPv6-/56-Block einem vRack-Netzwerk zugewiesen ist, wird das erste /64-Subnetz damit gebrückt. Das bedeutet, dass Sie diese IPs problemlos auf Ihren Hosts verwenden können. -Let's check exactly which subnet is bridged: +Überprüfen wir, welches Subnetz gebrückt ist: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Wie im folgenden Beispiel: ![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Für weitere Details verwenden Sie diesen Aufruf: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Wie im folgenden Beispiel: ![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Beachten Sie, dass die automatische IP-Konfiguration (SLAAC) standardmäßig deaktiviert ist. -### Automatic IP configuration (SLAAC) +### Automatische IP-Konfiguration (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Um die IP-Adressierung in Ihrem Netzwerk zu vereinfachen, können Sie SLAAC verwenden. Es kann nur pro gebrücktem Subnetz aktiviert werden und kann mit dieser PUT-Methode aktiviert werden: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Wie im folgenden Beispiel: ![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Vergessen Sie nicht, SLAAC auf Ihrem Host-Rechner zu konfigurieren. /// -### Managing public IP bandwidth on vRack +### Öffentliche IP-Bandbreite im vRack verwalten -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Standardmäßig profitieren Additional-IP-Blöcke, die über ein vRack geroutet werden, von einer öffentlichen Standard-Bandbreite von 5 Gbps in Europa/Kanada/USA und 100 Mbps in APAC-Regionen. Eine detaillierte Übersicht der verfügbaren Optionen finden Sie in den öffentlichen Routing-Optionen auf unserer [vRack-Produktseite](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +Da die Anforderungen an die Infrastruktur wachsen, benötigen Nutzer möglicherweise mehr Bandbreite zur Unterstützung öffentlicher Dienste mit hohem Datenverkehr. OVHcloud bietet hierfür kostenpflichtige Bandbreitenoptionen an. Beachten Sie, dass Bandbreitenoptionen **pro vRack und pro Region** angewendet werden. Da Additional-IP-Adressen an eine Region gebunden sind, wirkt sich jede Bandbreitenänderung auf alle IP-Adressen (sowohl IPv4 als auch IPv6) aus, die in der betreffenden Region zu dem spezifischen vRack geroutet werden. -/// details | During the Additional IP ordering process +/// details | Beim Bestellen einer Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Öffentliche Bandbreite während der Bestellung wählen -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Die Standard-Bandbreite kann beim Bestellen eines neuen Additional-IP-Blocks mit einem vRack-Netzwerk als Backend geändert werden. -To order a new Additional IPv6 block: +Um einen neuen Additional-IPv6-Block zu bestellen: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Melden Sie sich im [OVHcloud Kundencenter](/links/manager) an. +- Öffnen Sie den Bereich `Network`{.action} in der linken Seitenleiste. +- Wählen Sie `Öffentliche IP-Adressen`{.action}. +- Klicken Sie auf die Schaltfläche `IPs bestellen`{.action} oben auf der Seite. +- Wählen Sie die IP-Version und dann das vRack, mit dem Ihr Additional IP verbunden werden soll. +- Wählen Sie die Region für Ihr Additional IP. +- Wählen Sie die öffentliche Bandbreite, die Sie für Ihr vRack in dieser Region anwenden möchten. +- Füllen Sie die anderen Optionen nach Bedarf aus und schließen Sie die Bestellung ab. /// -/// details | From the vRack management page +/// details | Über die vRack-Verwaltungsseite -#### Modifying vRack public bandwidth on management page +#### Öffentliche vRack-Bandbreite auf der Verwaltungsseite ändern -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +Für Additional-IP-Blöcke, die bereits mit einem vRack verbunden sind, kann die Bandbreite direkt über die Dienstkonfigurationsseite verwaltet werden. -To access the management interface: +Um auf die Verwaltungsoberfläche zuzugreifen: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- Öffnen Sie `Network`{.action} in der linken Seitenleiste Ihres Kundencenters. +- Wählen Sie `Privates vRack-Netzwerk`{.action}. +- Klicken Sie in der Spalte "Öffentliche IP und Bandbreite" auf die Schaltfläche `Verwalten`{.action} für das entsprechende vRack. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +Die Verwaltungsseite ist in zwei Registerkarten unterteilt: +- **Alle verbundenen Dienste**: Leitet derzeit auf die klassische vRack-Verwaltungsseite weiter. Demnächst werden hier alle mit dem vRack verbundenen Produkte (Server, Cloud-Projekte usw.) übersichtlich aufgelistet. +- **Öffentliches IP-Routing**: Verwaltet die öffentlichen IP-Routing-Optionen Ihres vRack, einschließlich der Bandbreite. -To modify the public bandwidth: +Um die öffentliche Bandbreite zu ändern: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Wechseln Sie zur Registerkarte `Öffentliches IP-Routing`{.action}. +- Die Oberfläche zeigt individuelle Verwaltungsfenster für jede mit dem vRack verbundene Region (z. B. `eu-west-par`) mit allen in dieser Region zugeordneten IP-Adressen. +- Klicken Sie im Fenster der betreffenden Region auf `Bandbreite ändern`{.action}. +- Wählen Sie die gewünschte Bandbreitenoption im rechten Bereich aus und klicken Sie auf `Zur Bestellung`{.action}, um die Bestellung zu bestätigen. +- Nach der Zahlung ist die ausgewählte Bandbreite nach einigen Minuten für Ihr vRack in der gewählten Region verfügbar. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> Die Gebühren für den ersten Monat werden anteilig für die verbleibenden Tage berechnet. Der volle Tarif gilt ab dem nächsten Abrechnungszyklus. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +Das ausgewählte Bandbreiten-Upgrade wird auf alle IP-Adressen in dieser Region für das gewählte vRack angewendet. /// -#### Host-side commands +#### Host-seitige Befehle -/// details | Static IP configuration +/// details | Statische IP-Konfiguration -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +In einer Basiskonfiguration möchten Sie möglicherweise eine IP-Adresse und das Routing manuell einrichten. Dies ist auch der empfohlene Weg, wenn Ihr Rechner als Router fungiert (siehe Abschnitt [Geroutetes Subnetz konfigurieren](#routedmode)) und der Modus ipv6.forwarding aktiviert ist. -First, let's add an IP address on the vRack interface (in our example "eth1"): +Fügen wir zunächst eine IP-Adresse auf dem vRack-Interface (in unserem Beispiel "eth1") hinzu: ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +Bitte beachten Sie, dass die erste IP-Adresse in einem Block, `2001:41d0:abcd:ef00::1/64`, die Gateway-IP-Adresse ist und nicht für die Host-Adressierung verwendet werden darf. -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Optional, wenn Sie das vRack-Interface als Hauptinterface für IPv6-Datenverkehr verwenden möchten, kann die Standard-Route folgendermaßen konfiguriert werden: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Aktivieren Sie abschließend das Interface (und überprüfen Sie die konfigurierte IP): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +292,19 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Automatische IP-Konfiguration (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Um die automatische Konfiguration zu nutzen, stellen Sie sicher, dass Sie Ihr Interface wie folgt konfiguriert haben: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +Erlauben wir zunächst unserem Host, Router-Ankündigungen (für die automatische Konfiguration) auf dem vRack-Interface (in unserem Beispiel "eth1") zu akzeptieren: ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Beachten Sie, dass diese Einstellung nicht funktioniert, wenn ipv6.forwarding in Ihrem System aktiviert ist. Lesen Sie in diesem Fall die [Automatische IP-Konfiguration für geroutetes Subnetz](#host-side) für weitere Details. -Then, simply bring up the interface: +Aktivieren Sie dann einfach das Interface: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +314,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Nach einem Moment (die Konfiguration muss sich propagieren) sollte eine spezifische IPv6-Adresse (mit den Flags *global* und *dynamic*) auf dem Interface sichtbar sein. /// -#### Setup verification +#### Einrichtungsüberprüfung -/// details | Local +/// details | Lokal -The most basic test is to ping a local IP address on a host: +Der grundlegendste Test besteht darin, eine lokale IP-Adresse auf einem Host anzupingen: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -336,7 +335,7 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// details | Remote -Next, let's verify the connectivity from remote: +Überprüfen wir nun die Konnektivität von einem Remote-Host: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +347,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Einen IPv6 in einem vRack für den gerouteten Modus konfigurieren -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +In diesem Abschnitt stellen wir eine erweiterte IPv6-Einrichtung vor, bei der Ihre mit dem vRack verbundenen Hosts als Router für gehostete virtuelle Maschinen fungieren. Solche VMs erhalten delegierte Subnetze aus dem IPv6-Hauptblock (im nachfolgenden Schema in orange dargestellt). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Einen IPv6 in einem vRack für den gerouteten Modus konfigurieren](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +Der Datenpfad verläuft wie folgt: Eingehender Datenverkehr zu einer bestimmten VM (mit angegebenem Subnetz) wird über das kundeneigene vRack geleitet, zunächst zu einem bestimmten Host (mit einer Next-Hop-Adresse), dann über einen lokalen Link (oder vSwitch - schwarzer Link fd00::/64 im Diagramm) zur jeweiligen VM. +Der von einer solchen VM zurückkommende Datenverkehr sollte die Standard-Route über den ersten Teil des lokalen Links (den schwarzen, fd00::1) verwenden, dann die (möglicherweise Standard-)Route von einem Host zu seinem Gateway. -For routed subnet definition any prefix size can be used between /57 and /64. +Für die Definition eines gerouteten Subnetzes kann jede Präfixgröße zwischen /57 und /64 verwendet werden. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +Das Standard-Gateway des Hosts ist die erste Adresse aus dem /56-Block, in diesem Beispiel: `2001:41d0:abcd:ef00::1`. Das von den VMs verwendete Standard-Gateway ist die Adresse ihres Hosts über den lokalen Link, also `fd00::1` in diesem Beispiel. -#### Define routed subnet +#### Geroutetes Subnetz definieren -/// details | OVHcloud Control Panel actions +/// details | OVHcloud Kundencenter -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Nach dem Hinzufügen einer Additional IP zu Ihrem vRack können Sie das geroutete Subnetz verwalten, indem Sie auf die Schaltfläche `Subnetz hinzufügen`{.action} klicken. -![vRack select](images/600.png){.thumbnail} +![vRack-Auswahl](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Um ein geroutetes Subnetz zu erstellen, müssen wir zunächst folgendes definieren: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **Subnetz in CIDR-Notation** (Größe zwischen /57 und /64) +- **Next-Hop-Adresse** (also die IPv6-Adresse des Hosts) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Bitte beachten Sie, dass sich ein gegebenes Subnetz nicht mit einem anderen definierten Subnetz überschneiden darf und die Next-Hop-Adresse zum ersten Teil (gebrücktes /64-Subnetz) Ihres Additional-IPv6-Präfixes gehören muss. -![continue](images/800.png){.thumbnail} +![weiter](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +Das erstellte geroutete Subnetz `2001:41d0:abcd::ef10::/60` ist über den Next Hop `2001:41d0:abcd::ef00::2` erreichbar. -![continue](images/801.png){.thumbnail} +![weiter](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | APIv6-Befehle -To create a routed subnet, we must first define: +Um ein geroutetes Subnetz zu erstellen, müssen wir zunächst folgendes definieren: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **Subnetz in CIDR-Notation** (Größe zwischen /57 und /64) +- **Next-Hop-Adresse** (also die IPv6-Adresse des Hosts) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Bitte beachten Sie, dass sich ein gegebenes Subnetz nicht mit einem anderen definierten Subnetz überschneiden darf und die Next-Hop-Adresse zum ersten Teil (gebrücktes /64-Subnetz) Ihres Additional-IPv6-Präfixes gehören muss. -The example below shows how to define such a subnet: +Das folgende Beispiel zeigt, wie ein solches Subnetz definiert wird: -![continue](images/20240418-02.png){.thumbnail} +![weiter](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +Hier haben wir das geroutete Subnetz `2001:41d0:abcd:ef10::/60` definiert, das an die VM delegiert wird, die auf `2001:41d0:abcd:ef00::2` gehostet ist. /// -#### Host-side configuration +#### Host-seitige Konfiguration -/// details | Static IP configuration for a host (recommended) +/// details | Statische IP-Konfiguration für einen Host (empfohlen) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +Beim Hosten von Virtual Machines empfehlen wir dringend, eine statische Konfiguration auf Ihrem Host zu verwenden. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Richten Sie eine IPv6-Adresse ein, aktivieren Sie das Interface und fügen Sie (optional) die Standard-Route über das vRack-Interface hinzu: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +416,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Automatische IP-Konfiguration (SLAAC) für einen Host -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +In manchen Fällen möchten Sie Ihre Interfaces möglicherweise mit SLAAC und IP-Forwarding zusammen konfigurieren. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Bitte beachten Sie, dass dies zusätzliche Risiken mit sich bringt (wie den Verlust des Zugangs nicht nur zum Host, sondern auch zu allen VMs) und nicht empfohlen wird. -Ensuring IPv6 forwarding is enabled: +Aktivierung des IPv6-Forwardings sicherstellen: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Konfiguration der Router-Ankündigungen, die auf dem vRack-Interface eth1 akzeptiert werden (in unserem Beispiel): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +436,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Konfiguration des gerouteten Subnetzes auf einem Host und innerhalb einer VM -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Um sicherzustellen, dass unser Host weiß, wie er mit Paketen umgehen soll, die an das neue geroutete Subnetz (das auf einer VM liegt) adressiert sind, müssen wir eine spezifische Route dafür hinzufügen. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +In unserem Beispiel ist dies der veth-Link mit der Adresse fd00::2/64 innerhalb einer VM, die wir für das Routing verwenden werden. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Bitte beachten Sie, dass dies sehr spezifisch für den installierten Hypervisor ist (es kann sich um vSwitch- oder veth-Interfaces handeln). Lesen Sie die spezifische Hypervisor-Netzwerkdokumentation für diese Einrichtung. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +451,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Konfiguration des gerouteten Subnetzes innerhalb einer VM -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Auch hier gilt: Der Link zwischen Host und VMs ist sehr spezifisch für den installierten Hypervisor (es kann sich um vSwitch- oder veth-Interfaces handeln). Lesen Sie die spezifische Hypervisor-Netzwerkdokumentation für diese Einrichtung. -Add our routed IP block inside a VM to ensure it can accept packets: +Fügen Sie unseren gerouteten IP-Block innerhalb einer VM hinzu, um sicherzustellen, dass sie Pakete akzeptieren kann: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Fügen Sie die Standard-Route auf einer VM hinzu, um sicherzustellen, dass der Datenverkehr die VM verlassen kann: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +470,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Einrichtungsüberprüfung -/// details | Local, on a host +/// details | Lokal, auf einem Host -Ping from the host into the container (using local link): +Ping vom Host in den Container (über den lokalen Link): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +483,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Ping vom Host in den Container (über das geroutete Subnetz): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +492,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Route zu unserem /60-Subnetz auf einem Host überprüfen: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +501,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Lokal, auf einer VM -First, check the routing table: +Überprüfen Sie zunächst die Routing-Tabelle: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +512,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Ping zum Link-Local-Interface des Hosts: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +521,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Ping zum globalen Interface des Hosts: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +530,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Pingen wir abschließend eine externe IPv6-Adresse von einer VM: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +539,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +Oder unter Verwendung eines Domainnamens: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +550,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | Von einem Remote-Host -Let's check connectivity to our VM from outside the OVHcloud network: +Überprüfen wir die Konnektivität zu unserer VM von außerhalb des OVHcloud-Netzwerks: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +561,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +Und ein Traceroute von einem Remote-Host (irgendwo im Internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +574,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +In diesem Beispiel: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- Hop 10 - IP-Adresse unseres Hosts +- Hop 11 - IP-Adresse unserer VM /// -## Multiple region locations vs. global vRack +## Mehrere Regionsstandorte vs. globales vRack -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +Die vRack-Technologie von OVHcloud ermöglicht es Unternehmen, Server an verschiedenen Standorten zu verbinden, als ob sie sich im selben Rechenzentrum befänden. +Andererseits sind Dienste wie Additional IPv6 regional, was bedeutet, dass ihre Funktionalität an einen bestimmten Standort gebunden ist. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +Nachfolgend wird zu Lernzwecken eine Architektur mit zwei verschiedenen Regionen und verschiedenen Additional-IPv6-Blöcken präsentiert, die jeweils aus einer Region angekündigt werden. Außerdem wird ein Host mit IP-Adressen aus beiden Netzwerken sowie ein Beispiel einer suboptimalen Route vorgestellt - ein Host in einer Region mit einer in einer anderen Region angekündigten IPv6-Adresse: ![image](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Bitte beachten Sie, dass bei solchen Setups (mit Additional IPv6 aus mehr als einer Region) SLAAC **im gesamten vRack deaktiviert sein muss** (da dies zu unvorhersehbaren Ergebnissen und zufälligem Konnektivitätsverlust führen kann). -### Benefits +### Vorteile -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Verbesserte Konnektivität:** Durch die Nutzung eines vRack-Netzwerks zusammen mit öffentlichen IP-Blöcken, die an mehreren Standorten geroutet werden, können Unternehmen eine nahtlose Kommunikation weltweit sicherstellen, unabhängig von den physischen Standorten der Backend-Server. +- **Migration in die Cloud:** Die vRack-Technologie kann ein wichtiger Enabler für erste Schritte in Richtung einer "Migration in die Cloud"-Organisationsstrategie sein und Legacy-Anwendungen entsperren, die noch lokale Netzwerkkommunikation erfordern. -### Risks and Considerations +### Risiken und Überlegungen -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Kein SLAAC-Support in Multi-Standort-Setups:** Wenn mehr als ein Standort am Routing von öffentlichem IP-Datenverkehr (sowohl IPv4 als auch IPv6) in dasselbe vRack beteiligt ist, sollte die Stateless Address Autoconfiguration (SLAAC) **nicht verwendet werden**. Als Beispiel für eine solche Situation betrachten wir bestehende Hosts, die IPv4-Adressen verwenden. Diese Hosts werden automatisch von SLAAC mit einem IPv6-Gateway neu konfiguriert, das in einer anderen Region eingerichtet ist. Zusammen mit der IPv6-Priorisierung gegenüber IPv4 durch einige Betriebssysteme kann diese Situation zu suboptimalem Routing oder sogar zum vollständigen Konnektivitätsverlust für diese Hosts führen. -## Known Limitations +## Bekannte Einschränkungen -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Das Verständnis der Einschränkungen bei der Verwendung von **Additional IPv6** in der **vRack**-Umgebung ist entscheidend für eine effektive Netzwerkplanung. Hier sind die wichtigsten zu berücksichtigenden Einschränkungen: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 ist nur mit vRack verfügbar**: Bitte beachten Sie, dass Additional-IPv6-Adressen nur mit vRack-verbundenen Backends konfiguriert werden können. +- **SLAAC-Einschränkungen in Multi-Standort-Setups**: Die Stateless Address Autoconfiguration (SLAAC) wird nicht unterstützt, wenn öffentlicher IP-Datenverkehr (sowohl IPv6 als auch IPv4) in mehreren Regionsstandorte in das vRack geroutet wird. +- **Bis zu 128 Hosts innerhalb des gebrückten Subnetzes**: Sie können bis zu 128 IP-Adressen direkt im vRack verwenden. +- **Bis zu 128 Next-Hop-Routen**: Sie können bis zu 128 Routen für geroutete Subnetze innerhalb eines vRack verwenden. +- **Öffentliche Bandbreitenbegrenzung**: Ausgehender Datenverkehr von OVHcloud ins Internet ist auf 5 Gbps pro Regionsstandort begrenzt. +- **IPv6-Block-Zuteilungslimits**: Ein einzelner Additional-IPv6-Block pro vRack in einem Regionsstandort. Maximal 3 Blöcke (/56) pro Regionsstandort. +- **Mobilität von Additional-IPv6-Blöcken**: Aufgrund des hierarchischen Designs des IPv6-Adressraums sind Additional-IPv6-Blöcke regionsspezifisch. Das bedeutet, dass Blöcke nicht zwischen Regionen übertragen werden können, obwohl sie einem beliebigen vRack-verbundenen Backend neu zugewiesen werden können. +- **Kein direkter VLAN-802.1Q-Support im vRack durch Additional IPv6**: Die Konfiguration kann nur mit dem nativen VLAN Ihres vRack-Netzwerks erfolgen. Für die Paketweiterleitung innerhalb eines bestimmten VLANs (eines vRack) wird ein dedizierter Host auf der Kundenseite benötigt. +- **Derzeit wird das Routing von Additional IPv6 in das vRack in APAC-Regionen (Asien-Pazifik) nicht unterstützt.** -## Go further +## Weiterführende Informationen -Join our [community of users](/links/community). +Treten Sie unserer [User Community](/links/community) bei. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md index 8ad25250a6a..cc607a70bb9 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack +title: Configuring an Additional IPv6 block in a vRack excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network -updated: 2026-03-09 +updated: 2026-03-11 --- -## Objective +## Objetivo -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +La red vRack es una red privada global que interconecta diferentes productos de OVHcloud y permite crear soluciones de red sofisticadas. Además de facilitar las conexiones privadas, también permite enrutar direcciones IP públicas. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Esta guía se centra en la configuración de bloques de direcciones Additional IPv6 dentro de una red vRack.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> El vRack admite el enrutamiento público IPv4 e IPv6 con bloques de direcciones Additional IP. Puede encontrar las instrucciones para configurar bloques IPv4 en esta guía: [Configurar un bloque IP en el vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Este artículo detalla la configuración de direcciones Additional IP en una red vRack. Si busca instrucciones para configurar direcciones Additional IP con una dirección IP principal (en la interfaz de red pública), consulte los siguientes artículos: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar una dirección IP en alias en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar una dirección IP en alias en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Configurar IPv6 en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar IPv6 en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurar IPv6 en una instancia Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction - -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +## Introducción -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +El IPv6 revoluciona las redes dentro del vRack de OVHcloud, ofreciendo una solución a las limitaciones del IPv4 y funcionalidades adaptadas a la Internet moderna. Su despliegue responde directamente a la necesidad de arquitecturas de Internet más amplias, seguras y sofisticadas. Estas son las principales ventajas de integrar IPv6 en el vRack: -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Flexibilidad para redes avanzadas**: el IPv6 aumenta considerablemente el espacio de direccionamiento, proporcionando la flexibilidad necesaria para escalar la infraestructura, gestionar escenarios de conmutación por error y soportar soluciones de mayor envergadura. Esto permite que las redes crezcan y se adapten sin las restricciones de direccionamiento del IPv4. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Enrutamiento jerárquico y segmentación**: IPv6 permite un enrutamiento jerárquico eficiente y una segmentación lógica de la infraestructura. Esto mejora la gestión y la seguridad de la red, ideal para revender máquinas virtuales con subredes dedicadas o para segmentar la infraestructura de red. -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +- **Baja latencia**: la conectividad IPv6 nativa de extremo a extremo puede facilitar la implementación de servicios sensibles a la latencia, como el streaming multimedia, ya que muchas redes de proveedores recientes se han construido con IPv6 nativo. En tales redes, el uso de servicios IPv4 genera latencia (y costes) adicionales. +Al aprovechar el IPv6 dentro del vRack, los usuarios de OVHcloud pueden disfrutar de un entorno de red más seguro, eficiente y escalable, listo para satisfacer las exigencias de los usos modernos de Internet. -## Requirements +## Requisitos -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Un servicio [vRack](/links/network/vrack) activo en su cuenta +- Un [servidor compatible con vRack](/links/network/vrack) conectado a su red vRack +- Acceso al [área de cliente de OVHcloud](/links/manager) > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Esta funcionalidad puede estar limitada o no disponible en los servidores de [la gama **Eco**](/links/bare-metal/eco-about). > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Consulte nuestra [página de comparación de servidores Eco](/links/bare-metal/eco-compare) para obtener más información. -## Instructions +## Procedimiento -### Obtaining a new Additional IPv6 block +### Obtención de un nuevo bloque Additional IPv6 -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Al solicitar un nuevo bloque Additional IPv6, es importante tener en cuenta que la asignación es regional. Esto significa que el bloque IPv6 que reciba estará vinculado a una región específica, que define el punto de entrada del tráfico público en su red vRack (es decir, la ubicación de la pasarela). -/// details | Request a new Additional IPv6 block +/// details | Solicitar un nuevo bloque Additional IPv6 -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Puede contratar su nuevo bloque IPv6 adicional [aquí](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). -![configuration page](images/500.png){.thumbnail} +![página de configuración](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +A continuación, siga las instrucciones paso a paso. -Your new Additional IPv6 will then be available on your vRack configuration page. +Su Additional IPv6 estará disponible en la página de configuración de su vRack. /// -### Configuring IPv6 in a vRack (basic mode) +### Configurar la IPv6 en un vRack (modo básico) -In this section we will present basic IPv6 setup for your vRack connected hosts. +En esta sección presentamos la configuración básica de IPv6 para sus hosts conectados al vRack. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![Configurar una IPv6 en un vRack](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +El ejemplo anterior muestra dos hosts con sus interfaces del lado del vRack configuradas con direcciones públicas IPv6. Un host tiene una configuración manual, mientras que otro tiene una dirección IP asignada automáticamente mediante SLAAC. Todas las direcciones IP pertenecen a la primera subred /64 de un bloque /56 de Additional IPv6 públicas dado. Ambos utilizan la interfaz vRack para la conectividad IPv6 pública. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +La pasarela predeterminada para la primera subred /64 (la que está puenteada) es la primera dirección del bloque /56. En este ejemplo, la pasarela es `2001:41d0:abcd:ef00::1`. Esta se distribuye mediante SLAAC, pero debe configurarse manualmente (como ruta predeterminada) si el SLAAC está desactivado (consulte la sección **Configuración IP estática** a continuación). -/// details | Via the OVHcloud Control Panel +/// details | A través del área de cliente de OVHcloud -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Haga clic en `Network`{.action} en el menú de la izquierda. +- Haga clic en `Red privada vRack`{.action}. +- Seleccione el vRack correspondiente. -![vRack management](images/700.png){.thumbnail} +![gestión del vRack](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +En la parte izquierda se muestran las opciones disponibles (servicios elegibles para configurar). -On the right you see what is already configured with your vRack. +En la parte derecha puede ver lo que ya está configurado en su vRack. -Select your new Additional IPv6 and add it to your vRack. +Seleccione su nueva Additional IPv6 y añádala a su vRack. -![vRack selection](images/701.png){.thumbnail} +![selección del vRack](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +Su nueva Additional IPv6 ya está añadida a su vRack. -### Static IP configuration +### Configuración IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Una vez que el bloque Additional IPv6 /56 se asigna a una red vRack, la primera subred /64 queda puenteada con él. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Esto significa que puede utilizar fácilmente estas IP en sus hosts con una configuración IP estática en las interfaces vRack (consulte la siguiente sección para ver un ejemplo de configuración en el lado del host). -### Automatic IP configuration (SLAAC) +### Configuración IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Para simplificar el direccionamiento IP dentro de su red, puede utilizar SLAAC. Puede activarse únicamente por subred puenteada, y también puede activarse para la primera subred /64 de su bloque (que siempre está puenteada) en cualquier momento mediante este botón deslizante: -![enabling SLAAC](images/702.png){.thumbnail} +![activar SLAAC](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +No olvide configurar SLAAC en su máquina host. /// -/// details | Via the APIv6 (alternative way) +/// details | A través de la APIv6 (método alternativo) -### Attributing an Additional IPv6 to a vRack +Cuando solicita una IPv6 adicional, esta se asigna automáticamente a su vRack. -When you request an additional IPv6, it is automatically assigned to your vRack. - -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Si ha eliminado esta nueva Additional IPv6 de su vRack, puede reasignarla utilizando el siguiente método POST: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Como en el ejemplo siguiente: ![api post add block](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Utilice la siguiente llamada para verificar que la IPv6 ha sido asignada: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Como en el ejemplo siguiente: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Ahora vemos nuestro bloque configurado con un vRack. El siguiente paso es configurar el host o los hosts virtuales. -### Static IP configuration +### Configuración IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Una vez que el bloque Additional IPv6 /56 se asigna a una red vRack, la primera subred /64 queda puenteada con él. Esto significa que puede utilizar fácilmente estas IP en sus hosts. -Let's check exactly which subnet is bridged: +Verifiquemos qué subredes están puenteadas: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Como en el ejemplo siguiente: ![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Para obtener más detalles, utilice la siguiente llamada: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como en el ejemplo siguiente: ![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Tenga en cuenta que la configuración IP automática (SLAAC) está desactivada por defecto. -### Automatic IP configuration (SLAAC) +### Configuración IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Para simplificar el direccionamiento IP dentro de su red, puede utilizar SLAAC. Puede activarse únicamente por subred puenteada y puede activarse con el siguiente método PUT: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como en el ejemplo siguiente: ![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +No olvide configurar SLAAC en su máquina host. /// -### Managing public IP bandwidth on vRack +### Gestionar el ancho de banda de las IP públicas en el vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Por defecto, los bloques de Additional IP enrutados a través de un vRack disponen de un ancho de banda público estándar de 5 Gbps en Europa y América del Norte, o de 100 Mbps en las regiones APAC. Para más información sobre las opciones disponibles, consulte las opciones de enrutamiento público en nuestra [página del producto vRack](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +Para responder al aumento de la carga de la infraestructura y a las necesidades de los servicios con tráfico elevado, OVHcloud ofrece opciones de ancho de banda de pago. Tenga en cuenta que estas opciones se aplican **por vRack y por región**. Dado que las Additional IP están vinculadas a una región específica, cualquier modificación del ancho de banda afectará a todas las direcciones (IPv4 e IPv6) enrutadas hacia ese vRack en la región correspondiente. -/// details | During the Additional IP ordering process +/// details | Al contratar una Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Elegir el ancho de banda público al contratar -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Puede modificar el ancho de banda predeterminado en el momento de contratar un nuevo bloque de Additional IP, siempre que se seleccione una red vRack como servicio backend. -To order a new Additional IPv6 block: +Para contratar un nuevo bloque de Additional IPv6: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Conéctese al [área de cliente de OVHcloud](/links/manager). +- En la barra lateral izquierda, acceda a la sección `Network`{.action}. +- Seleccione `Direcciones IP Públicas`{.action}. +- Haga clic en el botón `Contratar IPs`{.action} en la parte superior de la página. +- Elija la versión de la IP y, a continuación, el vRack al que se asociará la Additional IP. +- Seleccione la región de su Additional IP. +- Elija el ancho de banda público que desea aplicar a su vRack para esa región. +- Configure las demás opciones según sus necesidades y finalice el pedido. /// -/// details | From the vRack management page +/// details | Desde la página de gestión del vRack -#### Modifying vRack public bandwidth on management page +#### Modificar el ancho de banda público desde la página de gestión -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +Para los bloques de Additional IP ya asociados a un vRack, el ancho de banda se gestiona directamente desde la página de configuración del servicio. -To access the management interface: +Para acceder a la interfaz de gestión: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- En la barra lateral izquierda del área de cliente, abra `Network`{.action}. +- Seleccione `Red privada vRack`{.action}. +- En la columna "IP pública y ancho de banda", haga clic en el botón `Gestionar`{.action} correspondiente al vRack deseado. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +La interfaz de gestión se divide en dos pestañas: +- **Todos los servicios asociados**: Por el momento, redirige a la página de gestión clásica del vRack. Próximamente, esta pestaña listará de forma optimizada todos los productos (servidores, proyectos Cloud, etc.) vinculados al vRack. +- **Conectividad IP pública**: Permite gestionar las opciones de enrutamiento público de su vRack, incluido el ancho de banda. -To modify the public bandwidth: +Para modificar el ancho de banda: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Vaya a la pestaña `Conectividad IP pública`{.action}. +- La interfaz muestra ventanas de gestión por región (p. ej.: `eu-west-par`) asociadas al vRack, con la lista de IP asociadas. +- En el recuadro de la región correspondiente, haga clic en `Modificar el ancho de banda`{.action}. +- Seleccione la opción deseada en el panel de la derecha y haga clic en `Contratar`{.action} para validar. +- Una vez efectuado el pago, el nuevo ancho de banda estará activo en su vRack en la región elegida en pocos minutos. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> El primer mes suscrito se factura de forma proporcional a los días restantes. La tarifa completa se aplicará en el siguiente ciclo de facturación. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +El aumento del ancho de banda se aplicará a todas las direcciones IP de esa región para el vRack seleccionado. /// -#### Host-side commands +#### Comandos en el host -/// details | Static IP configuration +/// details | Configuración IP estática -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +En una configuración básica, puede querer configurar una dirección IP y el enrutamiento manualmente. Este también es el método recomendado cuando su máquina está configurada como enrutador (consulte la sección [configurar la subred enrutada](#routedmode)) y el modo ipv6.forwarding está activado. -First, let's add an IP address on the vRack interface (in our example "eth1"): +En primer lugar, añadamos una dirección IP en la interfaz vRack (en nuestro ejemplo, "eth1"): ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +(Tenga en cuenta que la primera dirección IP de un bloque, en este caso `2001:41d0:abcd:ef00::1/64`, es la dirección de la pasarela y no debe utilizarse para el direccionamiento de hosts). -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Si desea utilizar la interfaz vRack como interfaz principal para el tráfico IPv6, la ruta predeterminada puede configurarse de la siguiente manera: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Por último, active la interfaz (y compruebe la IP configurada en ella): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +291,20 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Configuración IP automática (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Para utilizar la configuración automática, asegúrese de haber configurado su interfaz de la siguiente manera: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +En primer lugar, permitamos a nuestro host aceptar los anuncios de enrutamiento (para la configuración automática) en la interfaz vRack (en nuestro ejemplo "eth1"): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Es importante tener en cuenta que esta configuración no funcionará si el modo ipv6.forwarding está activado en su sistema. En ese caso, consulte la [Configuración IP automática para una subred enrutada](#host-side) para obtener más detalles. + -Then, simply bring up the interface: +A continuación, active la interfaz: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +314,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Tras un breve período de tiempo (el tiempo de propagación de la configuración), debería aparecer en la interfaz una dirección IPv6 específica (con los flags *global* y *dynamic*). /// -#### Setup verification +#### Verificación de la instalación /// details | Local -The most basic test is to ping a local IP address on a host: +La prueba más sencilla es realizar un ping hacia una dirección IP local desde un host: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -334,9 +333,9 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -/// details | Remote +/// details | Remoto -Next, let's verify the connectivity from remote: +A continuación, verifiquemos la conectividad desde una dirección remota: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +347,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Configurar una IPv6 en un vRack para el modo de enrutamiento -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +En esta sección presentamos una configuración IPv6 más avanzada, donde los hosts conectados al vRack actúan como enrutadores para las máquinas virtuales alojadas. Estas VMs disponen de subredes delegadas procedentes del bloque IPv6 principal (representadas en color naranja en el esquema siguiente). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Configurar una IPv6 en un vRack para el modo de enrutamiento](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +El flujo de tráfico es el siguiente: el tráfico entrante hacia una VM determinada (con la subred especificada) se enruta a través del vRack del cliente, primero hacia un host específico (con una dirección de siguiente salto), y luego a través de un enlace local (o vSwitch - enlace negro fd00::/64 en el diagrama) hasta la máquina virtual concreta. +El tráfico que retorna de dicha VM debe utilizar la ruta predeterminada a través de la primera parte del enlace local (el negro, fd00::1), y luego la ruta (posiblemente predeterminada) del host hacia su pasarela. -For routed subnet definition any prefix size can be used between /57 and /64. +Para la definición de una subred enrutada, se puede utilizar cualquier tamaño de prefijo entre /57 y /64. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +La pasarela predeterminada del host es la primera dirección del bloque /56, que en este ejemplo es: `2001:41d0:abcd:ef00::1`. Las pasarelas predeterminadas utilizadas por las VMs son las direcciones configuradas del host (aquí fd00::1). -#### Define routed subnet +#### Definir una subred enrutada -/// details | OVHcloud Control Panel actions +/// details | Área de cliente de OVHcloud -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Después de añadir la Additional IP a su vRack, puede gestionar la subred enrutada haciendo clic en el botón `Añadir una subred`{.action}. -![vRack select](images/600.png){.thumbnail} +![selección vRack](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Para crear una subred enrutada, primero debemos definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subred en notación CIDR** (tamaño comprendido entre /57 y /64) +- **dirección de siguiente salto** (dirección IPv6 del host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Tenga en cuenta que una subred dada no puede solaparse con ninguna otra subred definida, y que la dirección del siguiente salto debe pertenecer a la primera parte (subred /64 puenteada) de su prefijo Additional IPv6. -![continue](images/800.png){.thumbnail} +![continuar](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +La subred enrutada `2001:41d0:abcd::ef10::/60` es accesible a través del siguiente salto `2001:41d0:abcd::ef00::2`. -![continue](images/801.png){.thumbnail} +![continuar](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | Comandos APIv6 -To create a routed subnet, we must first define: +Para crear una subred enrutada, primero debemos definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subred en notación CIDR** (tamaño comprendido entre /57 y /64) +- **dirección de siguiente salto** (por tanto, la dirección IPv6 del host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Tenga en cuenta que una subred dada no puede solaparse con ninguna otra subred definida, y que la dirección del siguiente salto debe pertenecer a la primera parte (subred /64 puenteada) de su prefijo Additional IPv6. -The example below shows how to define such a subnet: +El ejemplo siguiente muestra cómo definir una subred de este tipo: -![continue](images/20240418-02.png){.thumbnail} +![continuar](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +Aquí hemos definido la subred enrutada `2001:41d0:abcd:ef10::/60`, que será delegada a la VM alojada en la dirección `2001:41d0:abcd:ef00::2`. /// -#### Host-side configuration +#### Configuración del host -/// details | Static IP configuration for a host (recommended) +/// details | Configuración IP estática de un host (recomendado) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +Cuando aloje VMs, le recomendamos encarecidamente utilizar una configuración estática en su host. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Configure una dirección IPv6, active la interfaz y (opcionalmente) añada la ruta predeterminada en la interfaz vRack: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +416,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Configuración IP automática (SLAAC) para un host -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +En algunos casos, puede querer configurar sus interfaces con SLAAC y el reenvío de IP juntos. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Tenga en cuenta que esto conlleva riesgos adicionales (como la pérdida de acceso no solo al host sino también a todas las VMs) y no es recomendable. -Ensuring IPv6 forwarding is enabled: +Verificación de que el reenvío IPv6 está activado: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Configuración de los anuncios de enrutamiento para que sean aceptados (en la interfaz vRack eth1 en nuestro ejemplo): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +436,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Configuración de la subred enrutada en un host y dentro de una máquina virtual -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Para garantizar que nuestro host sepa cómo gestionar los paquetes dirigidos a la nueva subred enrutada (que estará en una VM), debemos añadir una ruta específica para ella. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +En nuestro ejemplo, se trata del enlace vEth con la dirección fd00::2/64, dentro de una VM que utilizaremos para el enrutamiento. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Tenga en cuenta que esto es específico del hipervisor instalado (puede tratarse de vSwitch o interfaces vEth). Consulte la guía de configuración de red específica del hipervisor para esta configuración. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +451,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Configuración de una subred enrutada dentro de una VM -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +De nuevo, tenga en cuenta que el enlace utilizado entre el host y las VMs es específico del hipervisor instalado (puede tratarse de vSwitch o interfaces vEth). Consulte las guías de configuración de red de su hipervisor para esta configuración. -Add our routed IP block inside a VM to ensure it can accept packets: +Añada el bloque de IP enrutadas dentro de una VM para garantizar que puede aceptar paquetes: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Añada la ruta predeterminada en una VM para garantizar que el tráfico pueda salir de ella: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +470,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Verificación de la configuración -/// details | Local, on a host +/// details | Local, en un host -Ping from the host into the container (using local link): +Realice un ping desde el host hacia el contenedor (utilizando el enlace local): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +483,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Realice un ping desde el host hacia el contenedor (utilizando la subred enrutada): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +492,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Compruebe la ruta hacia nuestra subred /60 en un host: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +501,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Local, en una VM -First, check the routing table: +En primer lugar, compruebe la tabla de enrutamiento: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +512,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Realice un ping hacia la interfaz de enlace local del host: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +521,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Realice un ping hacia la interfaz global del host: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +530,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Por último, realice un ping hacia una dirección IPv6 externa desde una VM: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +539,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +O bien, utilizando un nombre de dominio: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +550,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | Desde un host remoto -Let's check connectivity to our VM from outside the OVHcloud network: +Verifiquemos la conectividad con nuestra VM desde fuera de la red de OVHcloud: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +561,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +Y realice un traceroute desde un host remoto (en Internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +574,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +En este ejemplo: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- salto 10 - Dirección IP del host +- salto 11 - Dirección IP de la VM /// -## Multiple region locations vs. global vRack +## Ubicaciones multirregión vs. vRack global -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +La tecnología vRack de OVHcloud permite a las empresas conectar servidores en diferentes ubicaciones, como si estuvieran situados en el mismo centro de datos. +Por otro lado, los servicios como Additional IPv6 son regionales, lo que significa que su funcionamiento está vinculado a una ubicación concreta. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +A continuación se presenta una arquitectura con fines didácticos con dos regiones diferentes y bloques Additional IPv6 distintos anunciados desde cada una de ellas. Además, se muestra un host configurado con direcciones IP de ambas redes y un ejemplo de ruta subóptima: un host en una región con una dirección IPv6 anunciada en otra región: ![image](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Tenga en cuenta que en tales configuraciones (con Additional IPv6 procedentes de más de una región), el SLAAC **debe estar desactivado en todo el vRack** (ya que esto puede provocar resultados impredecibles y pérdidas aleatorias de conectividad). -### Benefits +### Ventajas -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Conectividad mejorada:** Al aprovechar una red vRack junto con bloques de IP públicas enrutados en múltiples ubicaciones, las empresas pueden garantizar una comunicación fluida en todo el mundo, independientemente de las ubicaciones físicas de los servidores backend. +- **Migración a la nube:** La tecnología vRack puede facilitar enormemente los primeros pasos hacia una estrategia organizacional de "migración a la nube", desbloqueando algunas aplicaciones heredadas que todavía requieren comunicación de red local. -### Risks and Considerations +### Riesgos y consideraciones -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Sin compatibilidad con SLAAC en configuraciones con múltiples ubicaciones:** Cuando hay más de una ubicación implicada en el enrutamiento del tráfico IP público (IPv4 e IPv6) en el mismo vRack, la configuración automática de direcciones sin estado (SLAAC) **no debe utilizarse**. Como ejemplo de tal situación, consideremos hosts existentes que utilizan direcciones IPv4. Estos hosts son reconfigurados automáticamente por SLAAC con una pasarela IPv6 configurada desde otra región. Junto con la priorización de IPv6 sobre IPv4 por parte de algunos sistemas operativos, esta situación puede provocar un enrutamiento subóptimo o incluso una pérdida total de conectividad para dichos hosts. -## Known Limitations +## Limitaciones conocidas -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Comprender las restricciones relacionadas con el uso de **Additional IPv6** en el entorno **vRack** es esencial para una planificación eficaz de la red. Estas son las principales limitaciones a tener en cuenta: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 solo está disponible con vRack**: Tenga en cuenta que las direcciones Additional IPv6 solo pueden configurarse con backends conectados al vRack. +- **Limitaciones del SLAAC en configuraciones con múltiples ubicaciones**: La configuración automática de direcciones sin estado (SLAAC) no es compatible cuando hay tráfico IP público (IPv6 e IPv4) enrutado en el vRack en múltiples regiones. +- **Hasta 128 hosts dentro de la subred puenteada**: Puede utilizar hasta 128 direcciones IP directamente en el vRack. +- **Hasta 128 rutas de siguiente salto**: Puede utilizar hasta 128 rutas para subredes enrutadas dentro de un vRack. +- **Límite de ancho de banda público**: El tráfico saliente de OVHcloud hacia Internet está limitado a 5 Gbps por región. +- **Límites de asignación de bloques IPv6**: Un único bloque Additional IPv6 por vRack en una región. Máximo de 3 bloques (/56) por ubicación de región. +- **Movilidad de los bloques Additional IPv6**: Debido al diseño jerárquico del espacio de direcciones IPv6, los bloques Additional IPv6 son específicos de cada región. Esto significa que los bloques no pueden transferirse entre regiones, aunque sí pueden reasignarse a cualquier backend conectado al vRack. +- **Sin compatibilidad directa con VLAN 802.1Q en el vRack con Additional IPv6**: La configuración solo puede realizarse con la VLAN nativa de su red vRack. Para la transmisión de paquetes dentro de una VLAN específica (en un vRack), será necesario un host dedicado en el lado del cliente. +- **Por el momento, el enrutamiento de Additional IPv6 en el vRack no es compatible con las regiones APAC.** -## Go further +## Más información -Join our [community of users](/links/community). +Interactúe con nuestra [comunidad de usuarios](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md index 6ef93a06ea9..10de938da97 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.es-us.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack (EN) -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack -updated: 2026-03-09 +title: Configurar un bloque Additional IPv6 en un vRack +excerpt: "Descubra cómo configurar un bloque de direcciones IPv6 públicas para su uso en un vRack" +updated: 2026-03-11 --- -## Objective +## Objetivo -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +La red vRack es una red privada global que interconecta diferentes productos de OVHcloud y permite crear soluciones de red sofisticadas. Además de facilitar las conexiones privadas, también permite enrutar direcciones IP públicas. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Esta guía se centra en la configuración de bloques de direcciones Additional IPv6 dentro de una red vRack.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> El vRack admite el enrutamiento público IPv4 e IPv6 con bloques de direcciones Additional IP. Puede encontrar las instrucciones para configurar bloques IPv4 en esta guía: [Configurar un bloque IP en el vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Este artículo detalla la configuración de direcciones Additional IP en una red vRack. Si busca instrucciones para configurar direcciones Additional IP con una dirección IP principal (en la interfaz de red pública), consulte los siguientes artículos: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar una dirección IP en alias en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar una dirección IP en alias en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Configurar IPv6 en un servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar IPv6 en un servidor VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurar IPv6 en una instancia Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction - -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +## Introducción -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +El IPv6 revoluciona las redes dentro del vRack de OVHcloud, ofreciendo una solución a las limitaciones del IPv4 y funcionalidades adaptadas a la Internet moderna. Su despliegue responde directamente a la necesidad de arquitecturas de Internet más amplias, seguras y sofisticadas. Estas son las principales ventajas de integrar IPv6 en el vRack: -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Flexibilidad para redes avanzadas**: el IPv6 aumenta considerablemente el espacio de direccionamiento, proporcionando la flexibilidad necesaria para escalar la infraestructura, gestionar escenarios de conmutación por error y soportar soluciones de mayor envergadura. Esto permite que las redes crezcan y se adapten sin las restricciones de direccionamiento del IPv4. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Enrutamiento jerárquico y segmentación**: IPv6 permite un enrutamiento jerárquico eficiente y una segmentación lógica de la infraestructura. Esto mejora la gestión y la seguridad de la red, ideal para revender máquinas virtuales con subredes dedicadas o para segmentar la infraestructura de red. -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +- **Baja latencia**: la conectividad IPv6 nativa de extremo a extremo puede facilitar la implementación de servicios sensibles a la latencia, como el streaming multimedia, ya que muchas redes de proveedores recientes se han construido con IPv6 nativo. En tales redes, el uso de servicios IPv4 genera latencia (y costes) adicionales. +Al aprovechar el IPv6 dentro del vRack, los usuarios de OVHcloud pueden disfrutar de un entorno de red más seguro, eficiente y escalable, listo para satisfacer las exigencias de los usos modernos de Internet. -## Requirements +## Requisitos -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Un servicio [vRack](/links/network/vrack) activo en su cuenta +- Un [servidor compatible con vRack](/links/network/vrack) conectado a su red vRack +- Acceso al [área de cliente de OVHcloud](/links/manager) > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Esta funcionalidad puede estar limitada o no disponible en los servidores de [la gama **Eco**](/links/bare-metal/eco-about). > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Consulte nuestra [página de comparación de servidores Eco](/links/bare-metal/eco-compare) para obtener más información. -## Instructions +## Procedimiento -### Obtaining a new Additional IPv6 block +### Obtención de un nuevo bloque Additional IPv6 -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Al solicitar un nuevo bloque Additional IPv6, es importante tener en cuenta que la asignación es regional. Esto significa que el bloque IPv6 que reciba estará vinculado a una región específica, que define el punto de entrada del tráfico público en su red vRack (es decir, la ubicación de la pasarela). -/// details | Request a new Additional IPv6 block +/// details | Solicitar un nuevo bloque Additional IPv6 -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Puede contratar su nuevo bloque IPv6 adicional [aquí](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). -![configuration page](images/500.png){.thumbnail} +![página de configuración](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +A continuación, siga las instrucciones paso a paso. -Your new Additional IPv6 will then be available on your vRack configuration page. +Su Additional IPv6 estará disponible en la página de configuración de su vRack. /// -### Configuring IPv6 in a vRack (basic mode) +### Configurar la IPv6 en un vRack (modo básico) -In this section we will present basic IPv6 setup for your vRack connected hosts. +En esta sección presentamos la configuración básica de IPv6 para sus hosts conectados al vRack. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![Configurar una IPv6 en un vRack](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +El ejemplo anterior muestra dos hosts con sus interfaces del lado del vRack configuradas con direcciones públicas IPv6. Un host tiene una configuración manual, mientras que otro tiene una dirección IP asignada automáticamente mediante SLAAC. Todas las direcciones IP pertenecen a la primera subred /64 de un bloque /56 de Additional IPv6 públicas dado. Ambos utilizan la interfaz vRack para la conectividad IPv6 pública. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +La pasarela predeterminada para la primera subred /64 (la que está puenteada) es la primera dirección del bloque /56. En este ejemplo, la pasarela es `2001:41d0:abcd:ef00::1`. Esta se distribuye mediante SLAAC, pero debe configurarse manualmente (como ruta predeterminada) si el SLAAC está desactivado (consulte la sección **Configuración IP estática** a continuación). -/// details | Via the OVHcloud Control Panel +/// details | A través del área de cliente de OVHcloud -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Haga clic en `Network`{.action} en el menú de la izquierda. +- Haga clic en `Red privada vRack`{.action}. +- Seleccione el vRack correspondiente. -![vRack management](images/700.png){.thumbnail} +![gestión del vRack](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +En la parte izquierda se muestran las opciones disponibles (servicios elegibles para configurar). -On the right you see what is already configured with your vRack. +En la parte derecha puede ver lo que ya está configurado en su vRack. -Select your new Additional IPv6 and add it to your vRack. +Seleccione su nueva Additional IPv6 y añádala a su vRack. -![vRack selection](images/701.png){.thumbnail} +![selección del vRack](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +Su nueva Additional IPv6 ya está añadida a su vRack. -### Static IP configuration +### Configuración IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Una vez que el bloque Additional IPv6 /56 se asigna a una red vRack, la primera subred /64 queda puenteada con él. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Esto significa que puede utilizar fácilmente estas IP en sus hosts con una configuración IP estática en las interfaces vRack (consulte la siguiente sección para ver un ejemplo de configuración en el lado del host). -### Automatic IP configuration (SLAAC) +### Configuración IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Para simplificar el direccionamiento IP dentro de su red, puede utilizar SLAAC. Puede activarse únicamente por subred puenteada, y también puede activarse para la primera subred /64 de su bloque (que siempre está puenteada) en cualquier momento mediante este botón deslizante: -![enabling SLAAC](images/702.png){.thumbnail} +![activar SLAAC](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +No olvide configurar SLAAC en su máquina host. /// -/// details | Via the APIv6 (alternative way) +/// details | A través de la APIv6 (método alternativo) -### Attributing an Additional IPv6 to a vRack +Cuando solicita una IPv6 adicional, esta se asigna automáticamente a su vRack. -When you request an additional IPv6, it is automatically assigned to your vRack. - -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Si ha eliminado esta nueva Additional IPv6 de su vRack, puede reasignarla utilizando el siguiente método POST: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Como en el ejemplo siguiente: ![api post add block](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Utilice la siguiente llamada para verificar que la IPv6 ha sido asignada: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Como en el ejemplo siguiente: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Ahora vemos nuestro bloque configurado con un vRack. El siguiente paso es configurar el host o los hosts virtuales. -### Static IP configuration +### Configuración IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Una vez que el bloque Additional IPv6 /56 se asigna a una red vRack, la primera subred /64 queda puenteada con él. Esto significa que puede utilizar fácilmente estas IP en sus hosts. -Let's check exactly which subnet is bridged: +Verifiquemos qué subredes están puenteadas: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Como en el ejemplo siguiente: ![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Para obtener más detalles, utilice la siguiente llamada: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como en el ejemplo siguiente: ![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Tenga en cuenta que la configuración IP automática (SLAAC) está desactivada por defecto. -### Automatic IP configuration (SLAAC) +### Configuración IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Para simplificar el direccionamiento IP dentro de su red, puede utilizar SLAAC. Puede activarse únicamente por subred puenteada y puede activarse con el siguiente método PUT: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como en el ejemplo siguiente: ![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +No olvide configurar SLAAC en su máquina host. /// -### Managing public IP bandwidth on vRack +### Gestionar el ancho de banda de las IP públicas en el vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Por defecto, los bloques de Additional IP enrutados a través de un vRack disponen de un ancho de banda público estándar de 5 Gbps en Europa y América del Norte, o de 100 Mbps en las regiones APAC. Para más información sobre las opciones disponibles, consulte las opciones de enrutamiento público en nuestra [página del producto vRack](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +Para responder al aumento de la carga de la infraestructura y a las necesidades de los servicios con tráfico elevado, OVHcloud ofrece opciones de ancho de banda de pago. Tenga en cuenta que estas opciones se aplican **por vRack y por región**. Dado que las Additional IP están vinculadas a una región específica, cualquier modificación del ancho de banda afectará a todas las direcciones (IPv4 e IPv6) enrutadas hacia ese vRack en la región correspondiente. -/// details | During the Additional IP ordering process +/// details | Al contratar una Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Elegir el ancho de banda público al contratar -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Puede modificar el ancho de banda predeterminado en el momento de contratar un nuevo bloque de Additional IP, siempre que se seleccione una red vRack como servicio backend. -To order a new Additional IPv6 block: +Para contratar un nuevo bloque de Additional IPv6: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Conéctese al [área de cliente de OVHcloud](/links/manager). +- En la barra lateral izquierda, acceda a la sección `Network`{.action}. +- Seleccione `Direcciones IP Públicas`{.action}. +- Haga clic en el botón `Contratar IPs`{.action} en la parte superior de la página. +- Elija la versión de la IP y, a continuación, el vRack al que se asociará la Additional IP. +- Seleccione la región de su Additional IP. +- Elija el ancho de banda público que desea aplicar a su vRack para esa región. +- Configure las demás opciones según sus necesidades y finalice el pedido. /// -/// details | From the vRack management page +/// details | Desde la página de gestión del vRack -#### Modifying vRack public bandwidth on management page +#### Modificar el ancho de banda público desde la página de gestión -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +Para los bloques de Additional IP ya asociados a un vRack, el ancho de banda se gestiona directamente desde la página de configuración del servicio. -To access the management interface: +Para acceder a la interfaz de gestión: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- En la barra lateral izquierda del área de cliente, abra `Network`{.action}. +- Seleccione `Red privada vRack`{.action}. +- En la columna "IP pública y ancho de banda", haga clic en el botón `Gestionar`{.action} correspondiente al vRack deseado. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +La interfaz de gestión se divide en dos pestañas: +- **Todos los servicios asociados**: Por el momento, redirige a la página de gestión clásica del vRack. Próximamente, esta pestaña listará de forma optimizada todos los productos (servidores, proyectos Cloud, etc.) vinculados al vRack. +- **Conectividad IP pública**: Permite gestionar las opciones de enrutamiento público de su vRack, incluido el ancho de banda. -To modify the public bandwidth: +Para modificar el ancho de banda: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Vaya a la pestaña `Conectividad IP pública`{.action}. +- La interfaz muestra ventanas de gestión por región (p. ej.: `eu-west-par`) asociadas al vRack, con la lista de IP asociadas. +- En el recuadro de la región correspondiente, haga clic en `Modificar el ancho de banda`{.action}. +- Seleccione la opción deseada en el panel de la derecha y haga clic en `Contratar`{.action} para validar. +- Una vez efectuado el pago, el nuevo ancho de banda estará activo en su vRack en la región elegida en pocos minutos. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> El primer mes suscrito se factura de forma proporcional a los días restantes. La tarifa completa se aplicará en el siguiente ciclo de facturación. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +El aumento del ancho de banda se aplicará a todas las direcciones IP de esa región para el vRack seleccionado. /// -#### Host-side commands +#### Comandos en el host -/// details | Static IP configuration +/// details | Configuración IP estática -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +En una configuración básica, puede querer configurar una dirección IP y el enrutamiento manualmente. Este también es el método recomendado cuando su máquina está configurada como enrutador (consulte la sección [configurar la subred enrutada](#routedmode)) y el modo ipv6.forwarding está activado. -First, let's add an IP address on the vRack interface (in our example "eth1"): +En primer lugar, añadamos una dirección IP en la interfaz vRack (en nuestro ejemplo, "eth1"): ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +(Tenga en cuenta que la primera dirección IP de un bloque, en este caso `2001:41d0:abcd:ef00::1/64`, es la dirección de la pasarela y no debe utilizarse para el direccionamiento de hosts). -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Si desea utilizar la interfaz vRack como interfaz principal para el tráfico IPv6, la ruta predeterminada puede configurarse de la siguiente manera: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Por último, active la interfaz (y compruebe la IP configurada en ella): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +291,20 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Configuración IP automática (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Para utilizar la configuración automática, asegúrese de haber configurado su interfaz de la siguiente manera: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +En primer lugar, permitamos a nuestro host aceptar los anuncios de enrutamiento (para la configuración automática) en la interfaz vRack (en nuestro ejemplo "eth1"): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Es importante tener en cuenta que esta configuración no funcionará si el modo ipv6.forwarding está activado en su sistema. En ese caso, consulte la [Configuración IP automática para una subred enrutada](#host-side) para obtener más detalles. + -Then, simply bring up the interface: +A continuación, active la interfaz: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +314,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Tras un breve período de tiempo (el tiempo de propagación de la configuración), debería aparecer en la interfaz una dirección IPv6 específica (con los flags *global* y *dynamic*). /// -#### Setup verification +#### Verificación de la instalación /// details | Local -The most basic test is to ping a local IP address on a host: +La prueba más sencilla es realizar un ping hacia una dirección IP local desde un host: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -334,9 +333,9 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -/// details | Remote +/// details | Remoto -Next, let's verify the connectivity from remote: +A continuación, verifiquemos la conectividad desde una dirección remota: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +347,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Configurar una IPv6 en un vRack para el modo de enrutamiento -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +En esta sección presentamos una configuración IPv6 más avanzada, donde los hosts conectados al vRack actúan como enrutadores para las máquinas virtuales alojadas. Estas VMs disponen de subredes delegadas procedentes del bloque IPv6 principal (representadas en color naranja en el esquema siguiente). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Configurar una IPv6 en un vRack para el modo de enrutamiento](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +El flujo de tráfico es el siguiente: el tráfico entrante hacia una VM determinada (con la subred especificada) se enruta a través del vRack del cliente, primero hacia un host específico (con una dirección de siguiente salto), y luego a través de un enlace local (o vSwitch - enlace negro fd00::/64 en el diagrama) hasta la máquina virtual concreta. +El tráfico que retorna de dicha VM debe utilizar la ruta predeterminada a través de la primera parte del enlace local (el negro, fd00::1), y luego la ruta (posiblemente predeterminada) del host hacia su pasarela. -For routed subnet definition any prefix size can be used between /57 and /64. +Para la definición de una subred enrutada, se puede utilizar cualquier tamaño de prefijo entre /57 y /64. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +La pasarela predeterminada del host es la primera dirección del bloque /56, que en este ejemplo es: `2001:41d0:abcd:ef00::1`. Las pasarelas predeterminadas utilizadas por las VMs son las direcciones configuradas del host (aquí fd00::1). -#### Define routed subnet +#### Definir una subred enrutada -/// details | OVHcloud Control Panel actions +/// details | Área de cliente de OVHcloud -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Después de añadir la Additional IP a su vRack, puede gestionar la subred enrutada haciendo clic en el botón `Añadir una subred`{.action}. -![vRack select](images/600.png){.thumbnail} +![selección vRack](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Para crear una subred enrutada, primero debemos definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subred en notación CIDR** (tamaño comprendido entre /57 y /64) +- **dirección de siguiente salto** (dirección IPv6 del host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Tenga en cuenta que una subred dada no puede solaparse con ninguna otra subred definida, y que la dirección del siguiente salto debe pertenecer a la primera parte (subred /64 puenteada) de su prefijo Additional IPv6. -![continue](images/800.png){.thumbnail} +![continuar](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +La subred enrutada `2001:41d0:abcd::ef10::/60` es accesible a través del siguiente salto `2001:41d0:abcd::ef00::2`. -![continue](images/801.png){.thumbnail} +![continuar](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | Comandos APIv6 -To create a routed subnet, we must first define: +Para crear una subred enrutada, primero debemos definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subred en notación CIDR** (tamaño comprendido entre /57 y /64) +- **dirección de siguiente salto** (por tanto, la dirección IPv6 del host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Tenga en cuenta que una subred dada no puede solaparse con ninguna otra subred definida, y que la dirección del siguiente salto debe pertenecer a la primera parte (subred /64 puenteada) de su prefijo Additional IPv6. -The example below shows how to define such a subnet: +El ejemplo siguiente muestra cómo definir una subred de este tipo: -![continue](images/20240418-02.png){.thumbnail} +![continuar](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +Aquí hemos definido la subred enrutada `2001:41d0:abcd:ef10::/60`, que será delegada a la VM alojada en la dirección `2001:41d0:abcd:ef00::2`. /// -#### Host-side configuration +#### Configuración del host -/// details | Static IP configuration for a host (recommended) +/// details | Configuración IP estática de un host (recomendado) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +Cuando aloje VMs, le recomendamos encarecidamente utilizar una configuración estática en su host. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Configure una dirección IPv6, active la interfaz y (opcionalmente) añada la ruta predeterminada en la interfaz vRack: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +416,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Configuración IP automática (SLAAC) para un host -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +En algunos casos, puede querer configurar sus interfaces con SLAAC y el reenvío de IP juntos. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Tenga en cuenta que esto conlleva riesgos adicionales (como la pérdida de acceso no solo al host sino también a todas las VMs) y no es recomendable. -Ensuring IPv6 forwarding is enabled: +Verificación de que el reenvío IPv6 está activado: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Configuración de los anuncios de enrutamiento para que sean aceptados (en la interfaz vRack eth1 en nuestro ejemplo): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +436,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Configuración de la subred enrutada en un host y dentro de una máquina virtual -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Para garantizar que nuestro host sepa cómo gestionar los paquetes dirigidos a la nueva subred enrutada (que estará en una VM), debemos añadir una ruta específica para ella. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +En nuestro ejemplo, se trata del enlace vEth con la dirección fd00::2/64, dentro de una VM que utilizaremos para el enrutamiento. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Tenga en cuenta que esto es específico del hipervisor instalado (puede tratarse de vSwitch o interfaces vEth). Consulte la guía de configuración de red específica del hipervisor para esta configuración. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +451,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Configuración de una subred enrutada dentro de una VM -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +De nuevo, tenga en cuenta que el enlace utilizado entre el host y las VMs es específico del hipervisor instalado (puede tratarse de vSwitch o interfaces vEth). Consulte las guías de configuración de red de su hipervisor para esta configuración. -Add our routed IP block inside a VM to ensure it can accept packets: +Añada el bloque de IP enrutadas dentro de una VM para garantizar que puede aceptar paquetes: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Añada la ruta predeterminada en una VM para garantizar que el tráfico pueda salir de ella: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +470,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Verificación de la configuración -/// details | Local, on a host +/// details | Local, en un host -Ping from the host into the container (using local link): +Realice un ping desde el host hacia el contenedor (utilizando el enlace local): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +483,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Realice un ping desde el host hacia el contenedor (utilizando la subred enrutada): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +492,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Compruebe la ruta hacia nuestra subred /60 en un host: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +501,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Local, en una VM -First, check the routing table: +En primer lugar, compruebe la tabla de enrutamiento: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +512,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Realice un ping hacia la interfaz de enlace local del host: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +521,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Realice un ping hacia la interfaz global del host: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +530,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Por último, realice un ping hacia una dirección IPv6 externa desde una VM: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +539,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +O bien, utilizando un nombre de dominio: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +550,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | Desde un host remoto -Let's check connectivity to our VM from outside the OVHcloud network: +Verifiquemos la conectividad con nuestra VM desde fuera de la red de OVHcloud: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +561,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +Y realice un traceroute desde un host remoto (en Internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +574,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +En este ejemplo: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- salto 10 - Dirección IP del host +- salto 11 - Dirección IP de la VM /// -## Multiple region locations vs. global vRack +## Ubicaciones multirregión vs. vRack global -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +La tecnología vRack de OVHcloud permite a las empresas conectar servidores en diferentes ubicaciones, como si estuvieran situados en el mismo centro de datos. +Por otro lado, los servicios como Additional IPv6 son regionales, lo que significa que su funcionamiento está vinculado a una ubicación concreta. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +A continuación se presenta una arquitectura con fines didácticos con dos regiones diferentes y bloques Additional IPv6 distintos anunciados desde cada una de ellas. Además, se muestra un host configurado con direcciones IP de ambas redes y un ejemplo de ruta subóptima: un host en una región con una dirección IPv6 anunciada en otra región: ![image](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Tenga en cuenta que en tales configuraciones (con Additional IPv6 procedentes de más de una región), el SLAAC **debe estar desactivado en todo el vRack** (ya que esto puede provocar resultados impredecibles y pérdidas aleatorias de conectividad). -### Benefits +### Ventajas -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Conectividad mejorada:** Al aprovechar una red vRack junto con bloques de IP públicas enrutados en múltiples ubicaciones, las empresas pueden garantizar una comunicación fluida en todo el mundo, independientemente de las ubicaciones físicas de los servidores backend. +- **Migración a la nube:** La tecnología vRack puede facilitar enormemente los primeros pasos hacia una estrategia organizacional de "migración a la nube", desbloqueando algunas aplicaciones heredadas que todavía requieren comunicación de red local. -### Risks and Considerations +### Riesgos y consideraciones -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Sin compatibilidad con SLAAC en configuraciones con múltiples ubicaciones:** Cuando hay más de una ubicación implicada en el enrutamiento del tráfico IP público (IPv4 e IPv6) en el mismo vRack, la configuración automática de direcciones sin estado (SLAAC) **no debe utilizarse**. Como ejemplo de tal situación, consideremos hosts existentes que utilizan direcciones IPv4. Estos hosts son reconfigurados automáticamente por SLAAC con una pasarela IPv6 configurada desde otra región. Junto con la priorización de IPv6 sobre IPv4 por parte de algunos sistemas operativos, esta situación puede provocar un enrutamiento subóptimo o incluso una pérdida total de conectividad para dichos hosts. -## Known Limitations +## Limitaciones conocidas -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Comprender las restricciones relacionadas con el uso de **Additional IPv6** en el entorno **vRack** es esencial para una planificación eficaz de la red. Estas son las principales limitaciones a tener en cuenta: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 solo está disponible con vRack**: Tenga en cuenta que las direcciones Additional IPv6 solo pueden configurarse con backends conectados al vRack. +- **Limitaciones del SLAAC en configuraciones con múltiples ubicaciones**: La configuración automática de direcciones sin estado (SLAAC) no es compatible cuando hay tráfico IP público (IPv6 e IPv4) enrutado en el vRack en múltiples regiones. +- **Hasta 128 hosts dentro de la subred puenteada**: Puede utilizar hasta 128 direcciones IP directamente en el vRack. +- **Hasta 128 rutas de siguiente salto**: Puede utilizar hasta 128 rutas para subredes enrutadas dentro de un vRack. +- **Límite de ancho de banda público**: El tráfico saliente de OVHcloud hacia Internet está limitado a 5 Gbps por región. +- **Límites de asignación de bloques IPv6**: Un único bloque Additional IPv6 por vRack en una región. Máximo de 3 bloques (/56) por ubicación de región. +- **Movilidad de los bloques Additional IPv6**: Debido al diseño jerárquico del espacio de direcciones IPv6, los bloques Additional IPv6 son específicos de cada región. Esto significa que los bloques no pueden transferirse entre regiones, aunque sí pueden reasignarse a cualquier backend conectado al vRack. +- **Sin compatibilidad directa con VLAN 802.1Q en el vRack con Additional IPv6**: La configuración solo puede realizarse con la VLAN nativa de su red vRack. Para la transmisión de paquetes dentro de una VLAN específica (en un vRack), será necesario un host dedicado en el lado del cliente. +- **Por el momento, el enrutamiento de Additional IPv6 en el vRack no es compatible con las regiones APAC.** -## Go further +## Más información -Join our [community of users](/links/community). +Interactúe con nuestra [comunidad de usuarios](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md index 183722a3836..0f8b5e20214 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.fr-ca.md @@ -1,7 +1,7 @@ --- -title: Configurer un bloc IPv6 dans un vRack +title: Configurer un bloc Additional IPv6 dans un vRack excerpt: "Découvrez comment configurer un bloc d'adresses IPv6 publiques à utiliser dans un vRack" -updated: 2026-03-09 +updated: 2026-03-11 --- -## Objective +## Obiettivo -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +La rete vRack è una rete privata globale che collega diversi prodotti OVHcloud e consente la creazione di soluzioni di rete sofisticate. Oltre a facilitare le connessioni private, supporta anche il routing degli indirizzi IP pubblici. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Questa guida si concentra sulla configurazione dei blocchi di indirizzi Additional IPv6 all'interno di una rete vRack.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> Il vRack supporta il routing pubblico IPv4 e IPv6 con blocchi di indirizzi Additional IP. Per le istruzioni sulla configurazione dei blocchi IPv4, consulta questa guida: [Configurare un blocco IP nel vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Questo articolo descrive la configurazione degli indirizzi Additional IP su una rete vRack. Se stai cercando istruzioni per configurare indirizzi Additional IP con un indirizzo IP principale (sull'interfaccia di rete pubblica), consulta i seguenti articoli: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurare un indirizzo IP in alias su un server dedicato](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurare un indirizzo IP in alias su un VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Configurare IPv6 su un server dedicato](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurare IPv6 su un VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurare IPv6 su un'istanza Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction - -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +## Introduzione -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +L'IPv6 rivoluziona le reti all'interno del vRack di OVHcloud, offrendo una soluzione ai limiti dell'IPv4 e funzionalità adatte a Internet moderna. Il suo deployment è una risposta diretta alla necessità di architetture Internet più estese, sicure e sofisticate. Ecco i principali vantaggi dell'integrazione di IPv6 nel vRack: -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Flessibilità per reti avanzate**: l'IPv6 aumenta considerevolmente lo spazio di indirizzamento, fornendo la flessibilità necessaria per scalare l'infrastruttura, gestire scenari di failover e supportare soluzioni più grandi. Ciò consente alle reti di crescere e adattarsi senza i vincoli di indirizzamento dell'IPv4. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Routing gerarchico e segmentazione**: IPv6 consente un routing gerarchico efficiente e una segmentazione logica dell'infrastruttura. Questo migliora la gestione e la sicurezza della rete, ideale per la rivendita di macchine virtuali con subnet dedicate o per la segmentazione dell'infrastruttura di rete. -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +- **Bassa latenza**: la connettività IPv6 nativa end-to-end può facilitare l'implementazione di servizi sensibili alla latenza, come lo streaming multimediale, poiché molte reti di provider recenti sono costruite con IPv6 nativo. In tali reti, l'utilizzo di servizi IPv4 crea latenza (e costi) aggiuntivi. +Sfruttando l'IPv6 all'interno del vRack, gli utenti di OVHcloud possono beneficiare di un ambiente di rete più sicuro, efficiente e scalabile, pronto a soddisfare le esigenze degli usi moderni di Internet. -## Requirements +## Prerequisiti -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Un servizio [vRack](/links/network/vrack) attivo sul tuo account +- Un [server compatibile con vRack](/links/network/vrack) connesso alla tua rete vRack +- Accesso allo [Spazio Cliente OVHcloud](/links/manager) > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Questa funzionalità potrebbe essere limitata o non disponibile sui server della [gamma **Eco**](/links/bare-metal/eco-about). > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Consulta la nostra [pagina di confronto dei server Eco](/links/bare-metal/eco-compare) per ulteriori informazioni. -## Instructions +## Procedura -### Obtaining a new Additional IPv6 block +### Ottenere un nuovo blocco Additional IPv6 -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Quando richiedi un nuovo blocco Additional IPv6, è importante notare che l'allocazione è regionale. Ciò significa che il blocco IPv6 che ricevi sarà legato a una regione specifica, definendo il punto di ingresso del traffico pubblico nella tua rete vRack (ovvero la posizione del gateway). -/// details | Request a new Additional IPv6 block +/// details | Richiedere un nuovo blocco Additional IPv6 -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Puoi ordinare il tuo nuovo blocco IPv6 aggiuntivo [qui](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). -![configuration page](images/500.png){.thumbnail} +![pagina di configurazione](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +Successivamente, segui le istruzioni passo dopo passo. -Your new Additional IPv6 will then be available on your vRack configuration page. +Il tuo Additional IPv6 sarà quindi disponibile nella pagina di configurazione del tuo vRack. /// -### Configuring IPv6 in a vRack (basic mode) +### Configurare l'IPv6 in un vRack (modalità semplice) -In this section we will present basic IPv6 setup for your vRack connected hosts. +In questa sezione presentiamo la configurazione IPv6 di base per i tuoi host connessi al vRack. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![Configurare un IPv6 in un vRack](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +L'esempio precedente mostra due host con le relative interfacce lato vRack configurate con indirizzi IPv6 pubblici. Un host ha una configurazione manuale, mentre l'altro ha un indirizzo IP assegnato automaticamente tramite SLAAC. Tutti gli indirizzi IP appartengono alla prima subnet /64 di un dato blocco /56 di Additional IPv6 pubbliche. Entrambi utilizzano l'interfaccia vRack per la connettività IPv6 pubblica. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +Il gateway predefinito per la prima subnet /64 (quella in bridge) è il primo indirizzo del blocco /56. In questo esempio, il gateway è `2001:41d0:abcd:ef00::1`. Questo viene distribuito tramite SLAAC, ma deve essere configurato manualmente (come route predefinita) se SLAAC è disabilitato (vedi la sezione **Configurazione IP statica** di seguito). -/// details | Via the OVHcloud Control Panel +/// details | Tramite lo Spazio Cliente OVHcloud -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Clicca su `Network`{.action} nel menu a sinistra. +- Clicca su `Rete privata vRack`{.action}. +- Seleziona il vRack interessato. -![vRack management](images/700.png){.thumbnail} +![gestione vRack](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +Sul lato sinistro sono elencate le opzioni disponibili (servizi idonei alla configurazione). -On the right you see what is already configured with your vRack. +Sul lato destro puoi vedere cosa è già configurato nel tuo vRack. -Select your new Additional IPv6 and add it to your vRack. +Seleziona il tuo nuovo Additional IPv6 e aggiungilo al tuo vRack. -![vRack selection](images/701.png){.thumbnail} +![selezione vRack](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +Il tuo nuovo Additional IPv6 è stato aggiunto al tuo vRack. -### Static IP configuration +### Configurazione IP statica -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Una volta che il blocco Additional IPv6 /56 è assegnato a una rete vRack, la prima subnet /64 viene messa in bridge con esso. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Ciò significa che puoi facilmente utilizzare tali IP sui tuoi host con una configurazione IP statica sulle interfacce vRack (vedi la sezione successiva per un esempio di configurazione lato host). -### Automatic IP configuration (SLAAC) +### Configurazione IP automatica (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Per semplificare l'indirizzamento IP all'interno della tua rete, puoi utilizzare SLAAC. Può essere abilitato solo per subnet in bridge e può essere attivato per la prima subnet /64 del tuo blocco (sempre in bridge) in qualsiasi momento tramite questo pulsante cursore: -![enabling SLAAC](images/702.png){.thumbnail} +![abilitazione SLAAC](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Non dimenticare di configurare SLAAC sulla tua macchina host. /// -/// details | Via the APIv6 (alternative way) +/// details | Tramite l'APIv6 (metodo alternativo) -### Attributing an Additional IPv6 to a vRack +Quando richiedi un IPv6 aggiuntivo, viene automaticamente assegnato al tuo vRack. -When you request an additional IPv6, it is automatically assigned to your vRack. - -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Se hai rimosso questo nuovo Additional IPv6 dal tuo vRack, puoi riassegnarlo utilizzando il seguente metodo POST: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Come nell'esempio seguente: ![api post add block](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Usa la seguente chiamata per verificare che l'IPv6 sia stato assegnato: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Come nell'esempio seguente: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Ora vediamo il nostro blocco configurato con un vRack. Il passo successivo è configurare l'host o gli host virtuali. -### Static IP configuration +### Configurazione IP statica -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Una volta che il blocco Additional IPv6 /56 è assegnato a una rete vRack, la prima subnet /64 viene messa in bridge con esso. Ciò significa che puoi facilmente utilizzare tali IP sui tuoi host. -Let's check exactly which subnet is bridged: +Verifichiamo quali subnet sono in bridge: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Come nell'esempio seguente: ![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Per ottenere maggiori dettagli, usa la seguente chiamata: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Come nell'esempio seguente: ![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Nota che la configurazione IP automatica (SLAAC) è disabilitata per impostazione predefinita. -### Automatic IP configuration (SLAAC) +### Configurazione IP automatica (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Per semplificare l'indirizzamento IP all'interno della tua rete, puoi utilizzare SLAAC. Può essere abilitato solo per subnet in bridge e può essere attivato con il seguente metodo PUT: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Come nell'esempio seguente: ![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Non dimenticare di configurare SLAAC sulla tua macchina host. /// -### Managing public IP bandwidth on vRack +### Gestire la larghezza di banda degli IP pubblici sul vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Per impostazione predefinita, i blocchi di Additional IP instradati tramite un vRack beneficiano di una larghezza di banda pubblica standard di 5 Gbps in Europa e America del Nord, o di 100 Mbps nelle regioni APAC. Per maggiori dettagli sulle opzioni disponibili, consulta le opzioni di routing pubblico sulla nostra [pagina del prodotto vRack](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +Per rispondere all'aumento del carico delle infrastrutture e alle esigenze dei servizi ad alto traffico, OVHcloud propone opzioni di larghezza di banda a pagamento. Nota che queste opzioni si applicano **per vRack e per regione**. Poiché gli Additional IP sono legati a una regione specifica, qualsiasi modifica della larghezza di banda avrà impatto su tutti gli indirizzi (IPv4 e IPv6) instradati verso quel vRack nella regione interessata. -/// details | During the Additional IP ordering process +/// details | Al momento dell'ordine di un Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Scegliere la larghezza di banda pubblica durante l'ordine -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Puoi modificare la larghezza di banda predefinita al momento di ordinare un nuovo blocco di Additional IP, a condizione che una rete vRack sia selezionata come servizio backend. -To order a new Additional IPv6 block: +Per ordinare un nuovo blocco di Additional IPv6: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Accedi allo [Spazio Cliente OVHcloud](/links/manager). +- Nella barra laterale sinistra, accedi alla sezione `Network`{.action}. +- Seleziona `Indirizzi IP Pubblici`{.action}. +- Clicca sul pulsante `Ordina degli IP`{.action} in cima alla pagina. +- Scegli la versione IP, quindi il vRack a cui associare l'Additional IP. +- Seleziona la regione del tuo Additional IP. +- Scegli la larghezza di banda pubblica da applicare al tuo vRack per quella regione. +- Configura le altre opzioni in base alle tue esigenze, quindi finalizza l'ordine. /// -/// details | From the vRack management page +/// details | Dalla pagina di gestione del vRack -#### Modifying vRack public bandwidth on management page +#### Modificare la larghezza di banda pubblica dalla pagina di gestione -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +Per i blocchi di Additional IP già associati a un vRack, la larghezza di banda viene gestita direttamente dalla pagina di configurazione del servizio. -To access the management interface: +Per accedere all'interfaccia di gestione: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- Nella barra laterale sinistra dello Spazio Cliente, apri `Network`{.action}. +- Seleziona `Rete privata vRack`{.action}. +- Nella colonna "IP pubblico e larghezza di banda", clicca sul pulsante `Gestisci`{.action} corrispondente al vRack desiderato. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +L'interfaccia di gestione è suddivisa in due schede: +- **Tutti i servizi associati**: Al momento reindirizza alla pagina di gestione classica del vRack. Prossimamente, questa scheda elencherà in modo ottimizzato tutti i prodotti (server, progetti Cloud, ecc.) collegati al vRack. +- **Connettività IP pubblica**: Consente di gestire le opzioni di routing pubblico del tuo vRack, inclusa la larghezza di banda. -To modify the public bandwidth: +Per modificare la larghezza di banda: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Vai alla scheda `Connettività IP pubblica`{.action}. +- L'interfaccia mostra finestre di gestione per regione (es.: `eu-west-par`) associate al vRack, con l'elenco degli IP associati. +- Nel riquadro della regione interessata, clicca su `Modifica la larghezza di banda`{.action}. +- Seleziona l'opzione desiderata nel pannello a destra, quindi clicca su `Ordina`{.action} per confermare. +- Una volta effettuato il pagamento, la nuova larghezza di banda sarà attiva sul tuo vRack nella regione scelta dopo alcuni minuti. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> Il primo mese sottoscritto viene fatturato in proporzione ai giorni rimanenti. La tariffa completa si applicherà nel ciclo di fatturazione successivo. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +L'aumento della larghezza di banda si applicherà a tutti gli indirizzi IP di quella regione per il vRack selezionato. /// -#### Host-side commands +#### Comandi sull'host -/// details | Static IP configuration +/// details | Configurazione IP statica -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +In una configurazione di base, potresti voler configurare un indirizzo IP e il routing manualmente. Questo è anche il metodo consigliato quando la tua macchina è configurata come router (vedi la sezione [configurare la subnet instradata](#routedmode)) e la modalità ipv6.forwarding è abilitata. -First, let's add an IP address on the vRack interface (in our example "eth1"): +Prima di tutto, aggiungiamo un indirizzo IP sull'interfaccia vRack (nel nostro esempio "eth1"): ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +(Nota che il primo indirizzo IP di un blocco, in questo caso `2001:41d0:abcd:ef00::1/64`, è l'indirizzo del gateway e non deve essere utilizzato per l'indirizzamento degli host). -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Se desideri utilizzare l'interfaccia vRack come interfaccia principale per il traffico IPv6, la route predefinita può essere configurata nel seguente modo: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Infine, avvia l'interfaccia (e verifica l'IP configurato su di essa): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +291,20 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Configurazione IP automatica (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Per utilizzare la configurazione automatica, assicurati di aver configurato la tua interfaccia come segue: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +Prima di tutto, permettiamo al nostro host di accettare gli annunci del router (per la configurazione automatica) sull'interfaccia vRack (nel nostro esempio "eth1"): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +È importante notare che questa configurazione non funzionerà se la modalità ipv6.forwarding è abilitata nel tuo sistema. In tal caso, fai riferimento alla [Configurazione IP automatica per una subnet instradata](#host-side) per maggiori dettagli. + -Then, simply bring up the interface: +Quindi, avvia l'interfaccia: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +314,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Dopo un breve periodo (il tempo di propagazione della configurazione), un indirizzo IPv6 specifico (con i flag *global* e *dynamic*) dovrebbe apparire sull'interfaccia. /// -#### Setup verification +#### Verifica dell'installazione -/// details | Local +/// details | Locale -The most basic test is to ping a local IP address on a host: +Il test più semplice è eseguire un ping verso un indirizzo IP locale da un host: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -334,9 +333,9 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -/// details | Remote +/// details | Remoto -Next, let's verify the connectivity from remote: +Successivamente, verifichiamo la connettività da un indirizzo remoto: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +347,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Configurare un IPv6 in un vRack per la modalità instradata -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +In questa sezione presentiamo una configurazione IPv6 più avanzata, in cui i tuoi host connessi al vRack agiscono come router per le macchine virtuali ospitate. Tali VM dispongono di subnet delegate dal blocco IPv6 principale (rappresentate in arancione nello schema seguente). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Configurare un IPv6 in un vRack per la modalità instradata](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +Il percorso del traffico è il seguente: il traffico in entrata verso una determinata VM (con la subnet specificata) viene instradato attraverso il vRack del cliente, prima verso un host specifico (con un indirizzo next-hop), poi tramite un collegamento locale (o vSwitch - collegamento nero fd00::/64 nel diagramma) verso la VM specifica. +Il traffico proveniente da tale VM deve utilizzare la route predefinita attraverso la prima parte del collegamento locale (quello nero, fd00::1), poi la route (eventualmente predefinita) dall'host al suo gateway. -For routed subnet definition any prefix size can be used between /57 and /64. +Per la definizione di una subnet instradata, si può utilizzare qualsiasi dimensione di prefisso tra /57 e /64. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +Il gateway predefinito dell'host è il primo indirizzo del blocco /56, che in questo esempio è: `2001:41d0:abcd:ef00::1`. I gateway predefiniti utilizzati dalle VM sono gli indirizzi configurati dell'host (qui fd00::1). -#### Define routed subnet +#### Definire una subnet instradata -/// details | OVHcloud Control Panel actions +/// details | Spazio Cliente OVHcloud -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Dopo aver aggiunto l'Additional IP al tuo vRack, puoi gestire la subnet instradata cliccando sul pulsante `Aggiungere una sottorete`{.action}. -![vRack select](images/600.png){.thumbnail} +![selezione vRack](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Per creare una subnet instradata, dobbiamo prima definire: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subnet in notazione CIDR** (dimensione compresa tra /57 e /64) +- **indirizzo next-hop** (indirizzo IPv6 dell'host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Nota che una determinata subnet non può sovrapporsi a un'altra subnet definita e che l'indirizzo next-hop deve appartenere alla prima parte (subnet /64 in bridge) del tuo prefisso Additional IPv6. -![continue](images/800.png){.thumbnail} +![continua](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +La subnet instradata `2001:41d0:abcd::ef10::/60` è raggiungibile tramite il next hop `2001:41d0:abcd::ef00::2`. -![continue](images/801.png){.thumbnail} +![continua](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | Comandi APIv6 -To create a routed subnet, we must first define: +Per creare una subnet instradata, dobbiamo prima definire: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **subnet in notazione CIDR** (dimensione compresa tra /57 e /64) +- **indirizzo next-hop** (quindi l'indirizzo IPv6 dell'host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Nota che una determinata subnet non può sovrapporsi a un'altra subnet definita e che l'indirizzo next-hop deve appartenere alla prima parte (subnet /64 in bridge) del tuo prefisso Additional IPv6. -The example below shows how to define such a subnet: +L'esempio seguente mostra come definire tale subnet: -![continue](images/20240418-02.png){.thumbnail} +![continua](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +Qui abbiamo definito la subnet instradata `2001:41d0:abcd:ef10::/60`, che verrà delegata alla VM ospitata all'indirizzo `2001:41d0:abcd:ef00::2`. /// -#### Host-side configuration +#### Configurazione dell'host -/// details | Static IP configuration for a host (recommended) +/// details | Configurazione IP statica di un host (consigliata) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +Quando ospiti VM, ti consigliamo vivamente di utilizzare una configurazione statica sul tuo host. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Configura un indirizzo IPv6, avvia l'interfaccia e (facoltativamente) aggiungi la route predefinita sull'interfaccia vRack: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +416,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Configurazione IP automatica (SLAAC) per un host -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +In alcuni casi, potresti voler configurare le tue interfacce con SLAAC e l'inoltro IP insieme. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Nota che questo comporta rischi aggiuntivi (come la perdita di accesso non solo all'host ma anche a tutte le VM) e non è consigliato. -Ensuring IPv6 forwarding is enabled: +Verifica che l'inoltro IPv6 sia abilitato: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Configurazione degli annunci del router per essere accettati (sull'interfaccia vRack eth1 nel nostro esempio): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +436,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Configurazione della subnet instradata su un host e all'interno di una macchina virtuale -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Per garantire che il nostro host sappia come gestire i pacchetti indirizzati alla nuova subnet instradata (che sarà su una VM), dobbiamo aggiungere una route specifica per essa. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +Nel nostro esempio, si tratta del collegamento vEth con l'indirizzo fd00::2/64, all'interno di una VM che utilizzeremo per l'instradamento. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Nota che questo è molto specifico per l'hypervisor installato (può trattarsi di vSwitch o interfacce vEth). Fai riferimento alla guida di configurazione di rete specifica dell'hypervisor per questa configurazione. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +451,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Configurazione di una subnet instradata all'interno di una VM -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Ancora una volta, nota che il collegamento utilizzato tra l'host e le VM è molto specifico per l'hypervisor installato (può trattarsi di vSwitch o interfacce vEth). Fai riferimento alle guide di configurazione di rete del tuo hypervisor per questa configurazione. -Add our routed IP block inside a VM to ensure it can accept packets: +Aggiungi il blocco IP instradato all'interno di una VM per garantire che possa accettare pacchetti: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Aggiungi la route predefinita su una VM per garantire che il traffico possa uscire da essa: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +470,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Verifica della configurazione -/// details | Local, on a host +/// details | Locale, su un host -Ping from the host into the container (using local link): +Esegui un ping dall'host al container (usando il collegamento locale): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +483,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Esegui un ping dall'host al container (usando la subnet instradata): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +492,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Verifica la route verso la nostra subnet /60 su un host: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +501,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Locale, su una VM -First, check the routing table: +Prima di tutto, verifica la tabella di routing: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +512,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Esegui un ping verso l'interfaccia di collegamento locale dell'host: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +521,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Esegui un ping verso l'interfaccia globale dell'host: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +530,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Infine, esegui un ping verso un indirizzo IPv6 esterno da una VM: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +539,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +Oppure, utilizzando un nome di dominio: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +550,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | Da un host remoto -Let's check connectivity to our VM from outside the OVHcloud network: +Verifichiamo la connettività alla nostra VM dall'esterno della rete OVHcloud: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +561,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +E un traceroute da un host remoto (su Internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +574,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +In questo esempio: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- hop 10 - Indirizzo IP dell'host +- hop 11 - Indirizzo IP della VM /// -## Multiple region locations vs. global vRack +## Ubicazioni multi-regione vs. vRack globale -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +La tecnologia vRack di OVHcloud consente alle aziende di connettere server in diverse ubicazioni come se fossero situati nello stesso datacenter. +D'altra parte, i servizi come Additional IPv6 sono regionali, il che significa che il loro funzionamento è legato a una particolare ubicazione. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +Di seguito viene presentata un'architettura a scopo didattico con due regioni diverse e blocchi Additional IPv6 diversi annunciati da ciascuna di esse. Inoltre, è presentato un host configurato con indirizzi IP di entrambe le reti e un esempio di route non ottimale: un host in una regione con un indirizzo IPv6 annunciato in un'altra regione: ![image](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Nota che in tali configurazioni (con Additional IPv6 provenienti da più di una regione), il SLAAC **deve essere disabilitato sull'intero vRack** (poiché ciò potrebbe portare a risultati imprevedibili e perdita di connettività casuale). -### Benefits +### Vantaggi -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Connettività migliorata:** Sfruttando una rete vRack insieme a blocchi IP pubblici instradati in più ubicazioni, le aziende possono garantire una comunicazione fluida in tutto il mondo, indipendentemente dalle ubicazioni fisiche dei server backend. +- **Migrazione al cloud:** La tecnologia vRack può essere un grande facilitatore dei primi passi verso una strategia organizzativa di "migrazione al cloud", sbloccando alcune applicazioni legacy che richiedono ancora la comunicazione di rete locale. -### Risks and Considerations +### Rischi e considerazioni -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Nessun supporto SLAAC nelle configurazioni con più ubicazioni:** Quando è coinvolta più di una ubicazione nell'instradamento del traffico IP pubblico (IPv4 e IPv6) nello stesso vRack, la configurazione automatica degli indirizzi senza stato (SLAAC) **non deve essere utilizzata**. Come esempio di tale situazione, consideriamo host esistenti che utilizzano indirizzi IPv4. Tali host vengono riconfigurati automaticamente da SLAAC con un gateway IPv6 configurato da un'altra regione. Insieme alla prioritizzazione di IPv6 rispetto a IPv4 da parte di alcuni sistemi operativi, questa situazione può portare a un routing non ottimale o addirittura alla perdita totale di connettività per tali host. -## Known Limitations +## Limitazioni note -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Comprendere i vincoli legati all'utilizzo di **Additional IPv6** nell'ambiente **vRack** è essenziale per una pianificazione efficace della rete. Ecco le principali limitazioni da considerare: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 è disponibile solo con vRack**: Nota che gli indirizzi Additional IPv6 possono essere configurati solo con backend connessi al vRack. +- **Limitazioni SLAAC nelle configurazioni con più ubicazioni**: La configurazione automatica degli indirizzi senza stato (SLAAC) non è supportata quando c'è traffico IP pubblico (IPv6 e IPv4) instradato nel vRack in più regioni. +- **Fino a 128 host all'interno della subnet in bridge**: Puoi utilizzare fino a 128 indirizzi IP direttamente sul vRack. +- **Fino a 128 route next-hop**: Puoi utilizzare fino a 128 route per subnet instradate all'interno di un vRack. +- **Limite della larghezza di banda pubblica**: Il traffico in uscita da OVHcloud verso Internet è limitato a 5 Gbps per regione. +- **Limiti di allocazione dei blocchi IPv6**: Un singolo blocco Additional IPv6 per vRack in una regione. Massimo 3 blocchi (/56) per ubicazione di regione. +- **Mobilità dei blocchi Additional IPv6**: A causa del design gerarchico dello spazio di indirizzamento IPv6, i blocchi Additional IPv6 sono specifici per ogni regione. Ciò significa che i blocchi non possono essere trasferiti tra regioni, anche se possono essere riassegnati a qualsiasi backend connesso al vRack. +- **Nessun supporto diretto VLAN 802.1Q nel vRack tramite Additional IPv6**: La configurazione può essere effettuata solo con la VLAN nativa della tua rete vRack. Per l'inoltro di pacchetti all'interno di una VLAN specifica (in un vRack), sarà necessario un host dedicato lato cliente. +- **Al momento, l'instradamento di Additional IPv6 nel vRack non è supportato nelle regioni APAC.** -## Go further +## Per saperne di più -Join our [community of users](/links/community). +Contatta la nostra [Community di utenti](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md index 6ef93a06ea9..54dbedcf9d2 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pl-pl.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack (EN) -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack -updated: 2026-03-09 +title: Konfiguracja bloku Additional IPv6 w sieci vRack +excerpt: Dowiedz się, jak skonfigurować blok publicznych adresów IPv6 do użytku w sieci vRack OVHcloud +updated: 2026-03-11 --- -## Objective +## Cel -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +Sieć vRack stanowi globalną sieć prywatną łączącą różne produkty OVHcloud, umożliwiając tworzenie zaawansowanych rozwiązań sieciowych. Poza ułatwianiem połączeń prywatnych obsługuje również routing publicznych adresów IP. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Niniejszy przewodnik skupia się na konfiguracji dodatkowego bloku IPv6 w sieci vRack.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> vRack obsługuje publiczny routing IPv4 i IPv6 z blokami adresów Additional IP. Instrukcje dotyczące konfiguracji bloków IPv4 znajdziesz w tym przewodniku: [Konfiguracja bloku IP w sieci vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Niniejszy artykuł dotyczy konfiguracji Additional IP w sieci vRack. Jeśli szukasz wskazówek dotyczących konfiguracji Additional IP wraz z głównym adresem IP (na publicznym interfejsie sieciowym), zapoznaj się z następującymi artykułami: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Konfiguracja aliasowania IP na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Konfiguracja aliasowania IP na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Konfiguracja IPv6 na serwerach dedykowanych](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Konfiguracja IPv6 na serwerze VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Konfiguracja IPv6 na instancji Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction +## Wprowadzenie -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +IPv6 rewolucjonizuje sieciowanie w ramach sieci vRack OVHcloud, rozwiązując ograniczenia IPv4 i wprowadzając funkcje dla nowoczesnego Internetu. Jego wdrożenie jest bezpośrednią odpowiedzią na potrzebę bardziej rozbudowanych, bezpiecznych i zaawansowanych architektur internetowych. Oto kluczowe korzyści z integracji IPv6 z vRack: -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +- **Elastyczność dla zaawansowanych sieci**: IPv6 znacząco zwiększa przestrzeń adresową, zapewniając elastyczność niezbędną do skalowania infrastruktury, zarządzania scenariuszami failover i obsługi większych rozwiązań. Dzięki temu sieci mogą rosnąć i dostosowywać się bez ograniczeń przestrzeni IPv4. -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Hierarchiczny routing i segmentacja**: IPv6 umożliwia wydajny hierarchiczny routing i logiczną segmentację infrastruktury. Poprawia to zarządzalność sieci i bezpieczeństwo, idealne do odsprzedaży maszyn wirtualnych z dedykowanymi podsieciami lub organizowania infrastruktury w odrębne segmenty. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Niska latencja**: Natywna, end-to-end łączność IPv6 może być czynnikiem sprzyjającym dla usług wrażliwych na opóźnienia, takich jak strumieniowanie multimediów, ponieważ wiele nowoczesnych sieci dostawców jest zbudowanych natywnie w IPv6. W takich sieciach korzystanie z usług IPv4 powoduje dodatkowe opóźnienia (i koszty). -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +Dzięki wykorzystaniu IPv6 w sieci vRack użytkownicy OVHcloud mogą cieszyć się bezpieczniejszym, wydajniejszym i bardziej skalowalnym środowiskiem sieciowym, gotowym na wymagania nowoczesnego użytkowania Internetu. -## Requirements +## Wymagania wstępne -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Usługa [vRack](/links/network/vrack) aktywowana na Twoim koncie +- Serwer [kompatybilny z vRack](/links/network/vrack) podłączony do sieci vRack +- Dostęp do [Panelu klienta OVHcloud](/links/manager) > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Ta funkcja może być niedostępna lub ograniczona na serwerach z [linii produktów **Eco**](/links/bare-metal/eco-about). > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Więcej informacji znajdziesz na naszej [stronie porównania](/links/bare-metal/eco-compare). -## Instructions +## W praktyce -### Obtaining a new Additional IPv6 block +### Uzyskanie nowego dodatkowego bloku IPv6 -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Podczas zamawiania nowego dodatkowego bloku IPv6 należy pamiętać, że przydział jest regionalny. Oznacza to, że otrzymany blok IPv6 będzie powiązany z konkretnym regionem, określającym miejsce, w którym ruch publiczny wchodzi do sieci vRack (a zatem gdzie znajduje się brama sieciowa). -/// details | Request a new Additional IPv6 block +/// details | Zamów nowy dodatkowy blok IPv6 -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Nowy dodatkowy blok IPv6 możesz zamówić [tutaj](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). -![configuration page](images/500.png){.thumbnail} +![strona konfiguracji](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +Następnie postępuj zgodnie z instrukcjami krok po kroku. -Your new Additional IPv6 will then be available on your vRack configuration page. +Nowy dodatkowy blok IPv6 będzie dostępny na stronie konfiguracji sieci vRack. /// -### Configuring IPv6 in a vRack (basic mode) +### Konfiguracja IPv6 w sieci vRack (tryb podstawowy) -In this section we will present basic IPv6 setup for your vRack connected hosts. +W tej sekcji przedstawiamy podstawową konfigurację IPv6 dla hostów podłączonych do sieci vRack. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![Konfiguracja IPv6 w sieci vRack](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +Powyższy przykład przedstawia dwa hosty z interfejsami po stronie vRack skonfigurowanymi z publicznymi adresami IPv6. Jeden host jest skonfigurowany ręcznie, a drugi ma adres IP przypisany automatycznie przy użyciu SLAAC. Wszystkie adresy IP należą do pierwszej podsieci /64 z podanego publicznego bloku Additional IPv6 /56. Oba wykorzystują interfejs vRack do publicznej łączności IPv6. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +Domyślna brama dla pierwszej podsieci /64 (mostkowanej) to pierwszy adres bloku /56. W tym przykładzie jest to `2001:41d0:abcd:ef00::1`. Jest ona dystrybuowana przez SLAAC, ale musi być skonfigurowana ręcznie (jako trasa domyślna), jeśli SLAAC jest wyłączone. Zobacz sekcję **Statyczna konfiguracja IP** poniżej. -/// details | Via the OVHcloud Control Panel +/// details | Przez Panel klienta OVHcloud -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Otwórz `Sieć`{.action} na lewym pasku bocznym. +- Otwórz `Prywatna sieć vRack`{.action}. +- Wybierz odpowiednią sieć vRack. -![vRack management](images/700.png){.thumbnail} +![zarządzanie vRack](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +Po lewej stronie wyświetlona jest lista możliwych opcji (usług kwalifikujących się do konfiguracji). -On the right you see what is already configured with your vRack. +Po prawej stronie widoczne jest to, co jest już skonfigurowane w sieci vRack. -Select your new Additional IPv6 and add it to your vRack. +Wybierz nowy dodatkowy blok IPv6 i dodaj go do sieci vRack. -![vRack selection](images/701.png){.thumbnail} +![wybór vRack](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +Nowy dodatkowy blok IPv6 jest teraz dodany do sieci vRack. -### Static IP configuration +### Statyczna konfiguracja IP -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Po przypisaniu bloku Additional IPv6 /56 do sieci vRack pierwsza podsieć /64 jest z nią mostkowana. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Oznacza to, że możesz łatwo używać takich adresów IP na swoich hostach ze statyczną konfiguracją IP na interfejsach vRack (patrz następna sekcja, przykładowa konfiguracja po stronie hosta). -### Automatic IP configuration (SLAAC) +### Automatyczna konfiguracja IP (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Aby uprościć adresowanie IP w sieci, możesz użyć SLAAC. Można ją włączyć tylko per-mostkowana-podsieć i można ją włączyć dla pierwszej podsieci /64 bloku (ta zawsze jest mostkowana) w dowolnym momencie, używając tego przycisku: -![enabling SLAAC](images/702.png){.thumbnail} +![włączanie SLAAC](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Nie zapomnij skonfigurować SLAAC na swoim hoście. /// -/// details | Via the APIv6 (alternative way) +/// details | Przez APIv6 (metoda alternatywna) -### Attributing an Additional IPv6 to a vRack +### Przypisanie dodatkowego bloku IPv6 do sieci vRack -When you request an additional IPv6, it is automatically assigned to your vRack. +Po zamówieniu dodatkowego bloku IPv6 jest on automatycznie przypisywany do sieci vRack. -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Jeśli usunąłeś ten nowy dodatkowy blok IPv6 z sieci vRack, możesz go ponownie przypisać przy użyciu tej metody POST: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Jak w poniższym przykładzie: -![api post add block](images/post-ipv6.png){.thumbnail} +![api post dodaj blok](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Użyj następującego wywołania, aby zweryfikować, czy blok IPv6 został przypisany: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Jak w poniższym przykładzie: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Widzimy teraz nasz blok skonfigurowany w sieci vRack. Następnym krokiem jest konfiguracja hosta lub maszyn wirtualnych. -### Static IP configuration +### Statyczna konfiguracja IP -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Po przypisaniu bloku Additional IPv6 /56 do sieci vRack pierwsza podsieć /64 jest z nią mostkowana. Oznacza to, że możesz łatwo używać takich adresów IP na swoich hostach. -Let's check exactly which subnet is bridged: +Sprawdźmy dokładnie, która podsieć jest mostkowana: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Jak w poniższym przykładzie: -![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} +![GET podsieci mostkowanej w sieci vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Aby uzyskać więcej szczegółów, użyj tego wywołania: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Jak w poniższym przykładzie: -![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} +![GET podsieci mostkowanej w sieci vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Należy pamiętać, że autokonfiguracja IP (SLAAC) jest domyślnie wyłączona. -### Automatic IP configuration (SLAAC) +### Automatyczna konfiguracja IP (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Aby uprościć adresowanie IP w sieci, możesz użyć SLAAC. Można ją włączyć tylko per-mostkowana-podsieć przy użyciu tej metody PUT: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Jak w poniższym przykładzie: -![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} +![Wywołanie API POST włącz SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Nie zapomnij skonfigurować SLAAC na swoim hoście. /// -### Managing public IP bandwidth on vRack +### Zarządzanie przepustowością publiczną IP w sieci vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Domyślnie bloki Additional IP routowane przez sieć vRack korzystają ze standardowej publicznej przepustowości 5 Gbps w Europie/Kanadzie/USA i 100 Mbps w regionach APAC. Szczegółowy przegląd dostępności znajdziesz w opcjach routingu publicznego na naszej [stronie produktu vRack](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +W miarę skalowania wymagań infrastrukturalnych użytkownicy mogą potrzebować większej przepustowości do obsługi usług o dużym natężeniu ruchu publicznego, dla których OVHcloud udostępnia płatne opcje przepustowości. Należy pamiętać, że opcje przepustowości są stosowane **per-vRack i per-region**. Ponieważ adresy Additional IP są powiązane z regionem, każda modyfikacja przepustowości będzie dotyczyć wszystkich adresów IP (zarówno IPv4, jak i IPv6) routowanych do konkretnej sieci vRack w danym regionie. -/// details | During the Additional IP ordering process +/// details | Podczas procesu zamawiania Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Wybór przepustowości publicznej podczas zamawiania Additional IP -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Domyślna przepustowość publiczna może zostać zmieniona podczas zamawiania nowego bloku Additional IP z siecią vRack jako backendem. -To order a new Additional IPv6 block: +Aby zamówić nowy dodatkowy blok IPv6: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Zaloguj się do [Panelu klienta OVHcloud](/links/manager). +- Otwórz sekcję `Sieć`{.action} na lewym pasku bocznym. +- Wybierz `Publiczne adresy IP`{.action}. +- Kliknij przycisk `Zamów adresy IP`{.action} w pobliżu górnej części strony. +- Wybierz wersję IP, a następnie sieć vRack, do której chcesz podłączyć Additional IP. +- Wybierz region, w którym ma znajdować się Additional IP. +- Wybierz przepustowość publiczną, którą chcesz zastosować do sieci vRack dla tego konkretnego regionu. +- Wypełnij pozostałe opcje w razie potrzeby, a następnie sfinalizuj zamówienie. /// -/// details | From the vRack management page +/// details | Ze strony zarządzania siecią vRack -#### Modifying vRack public bandwidth on management page +#### Modyfikacja przepustowości publicznej vRack na stronie zarządzania -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +W przypadku bloków Additional IP już podłączonych do sieci vRack przepustowością można zarządzać bezpośrednio przez stronę konfiguracji usługi. -To access the management interface: +Aby uzyskać dostęp do interfejsu zarządzania: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- Otwórz `Sieć`{.action} na lewym pasku bocznym Panelu klienta. +- Wybierz `Prywatna sieć vRack`{.action}. +- W kolumnie "Publiczne IP i przepustowość" kliknij przycisk `Zarządzaj`{.action} przy odpowiedniej sieci vRack. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +Strona zarządzania podzielona jest na dwie zakładki: +- **Wszystkie podłączone usługi**: Na razie przekierowuje do klasycznej strony zarządzania siecią vRack. Wkrótce wyświetli wszystkie produkty (serwery, projekty Cloud itp.) aktualnie powiązane z siecią vRack w nowy sposób. +- **Publiczny routing IP**: Zarządza opcjami routingu publicznego IP sieci vRack, w tym przepustowością publiczną. -To modify the public bandwidth: +Aby zmodyfikować przepustowość publiczną: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Przejdź do zakładki `Publiczny routing IP`{.action}. +- Interfejs wyświetla indywidualne okna zarządzania dla każdego regionu (np. `eu-west-par`) powiązanego z siecią vRack, zawierające listę wszystkich adresów IP podłączonych do tego konkretnego regionu. +- W oknie odpowiedniego regionu kliknij przycisk `Zmień przepustowość`{.action}. +- Wybierz żądaną opcję przepustowości w panelu wyświetlonym po prawej stronie, a następnie kliknij `Złóż zamówienie`{.action}, aby zatwierdzić zamówienie. +- Po opłaceniu wybrana przepustowość powinna być dostępna dla sieci vRack w wybranym regionie po kilku minutach. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> Opłaty za pierwszy miesiąc są naliczane proporcjonalnie do pozostałych dni, a pełna stawka obowiązuje od następnego cyklu rozliczeniowego. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +Wybrane ulepszenie przepustowości zostanie zastosowane do wszystkich adresów IP w danym regionie dla wybranej sieci vRack. /// -#### Host-side commands +#### Polecenia po stronie hosta -/// details | Static IP configuration +/// details | Statyczna konfiguracja IP -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +W podstawowej konfiguracji możesz chcieć skonfigurować adres IP i routing ręcznie. Jest to również zalecany sposób, gdy Twoja maszyna działa jako router (patrz sekcja [konfiguracja routowanej podsieci](#routedmode)) i ma włączony tryb ipv6.forwarding. -First, let's add an IP address on the vRack interface (in our example "eth1"): +Najpierw dodajmy adres IP na interfejsie vRack (w naszym przykładzie "eth1"): ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +Pamiętaj, że pierwszy adres IP w bloku, `2001:41d0:abcd:ef00::1/64`, jest adresem IP bramy sieciowej i nie może być używany do adresowania hostów. -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Opcjonalnie, jeśli chcesz używać interfejsu vRack jako głównego dla ruchu IPv6, domyślną trasę można skonfigurować w następujący sposób: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Na koniec uruchom interfejs (i zweryfikuj skonfigurowany na nim adres IP): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +293,19 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Automatyczna konfiguracja IP (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Aby użyć automatycznej konfiguracji, upewnij się, że interfejs jest skonfigurowany w następujący sposób: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +Najpierw zezwólmy hostowi na akceptowanie Router Advertisements (do autokonfiguracji) na interfejsie vRack (w naszym przykładzie "eth1"): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +Pamiętaj, że to ustawienie nie zadziała, jeśli w systemie jest włączone ipv6.forwarding. W takim przypadku zapoznaj się z sekcją [Automatyczna konfiguracja IP dla routowanej podsieci](#host-side), aby uzyskać więcej szczegółów. -Then, simply bring up the interface: +Następnie po prostu uruchom interfejs: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +315,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Po chwili (konfiguracja musi się rozpropagować) na interfejsie powinien być widoczny konkretny adres IPv6 (z flagami global i dynamic). /// -#### Setup verification +#### Weryfikacja konfiguracji -/// details | Local +/// details | Lokalna -The most basic test is to ping a local IP address on a host: +Najprostszym testem jest ping lokalnego adresu IP na hoście: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -334,9 +334,9 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -/// details | Remote +/// details | Zdalna -Next, let's verify the connectivity from remote: +Następnie zweryfikujmy łączność ze zdalnego hosta: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +348,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Konfiguracja IPv6 w sieci vRack dla trybu routowanego -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +W tej sekcji przedstawiamy bardziej zaawansowaną konfigurację IPv6, w której hosty podłączone do sieci vRack działają jako routery dla hostowanych maszyn wirtualnych. Takie maszyny wirtualne mają delegowane podsieci z głównego bloku IPv6 (przedstawione kolorem pomarańczowym na schemacie poniżej). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Konfiguracja IPv6 w sieci vRack dla trybu routowanego](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +Ścieżka ruchu jest następująca: ruch przychodzący do danej maszyny wirtualnej (z określoną podsiecią) jest routowany przez sieć vRack klienta, najpierw do określonego hosta (z adresem next-hop), a następnie przy użyciu łącza lokalnego (lub vSwitch - czarne łącze fd00::/64 na schemacie) do konkretnej maszyny wirtualnej. +Ruch powrotny z takiej maszyny wirtualnej powinien używać trasy domyślnej przez pierwszą część lokalnego łącza (czarnego, fd00::1), a następnie (ewentualnie domyślnej) trasy z hosta do jego bramy sieciowej. -For routed subnet definition any prefix size can be used between /57 and /64. +Dla definicji routowanej podsieci można użyć dowolnego rozmiaru prefiksu między /57 a /64. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +Domyślna brama dla hosta to pierwszy adres z bloku /56, który w tym przykładzie wynosi: `2001:41d0:abcd:ef00::1`. Domyślna brama używana przez maszyny wirtualne to adres ich hosta przez łącze lokalne, który w tym przykładzie wynosi `fd00::1`. -#### Define routed subnet +#### Definiowanie routowanej podsieci -/// details | OVHcloud Control Panel actions +/// details | Działania w Panelu klienta OVHcloud -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Po dodaniu Additional IP do sieci vRack możesz zarządzać routowaną podsiecią, klikając przycisk `Dodaj podsieć`{.action}. -![vRack select](images/600.png){.thumbnail} +![wybór vRack](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Aby utworzyć routowaną podsieć, musimy najpierw zdefiniować: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **podsieć w notacji CIDR** (rozmiar między /57 a /64) +- **adres next-hop** (czyli adres IPv6 hosta) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Pamiętaj, że dana podsieć nie może pokrywać się z żadną inną zdefiniowaną podsiecią, a adres next-hop musi należeć do pierwszej części (mostkowanej podsieci /64) prefiksu Additional IPv6. -![continue](images/800.png){.thumbnail} +![kontynuuj](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +Utworzono routowaną podsieć `2001:41d0:abcd::ef10::/60` osiągalną przez next-hop `2001:41d0:abcd::ef00::2`. -![continue](images/801.png){.thumbnail} +![kontynuuj](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | Polecenia APIv6 -To create a routed subnet, we must first define: +Aby utworzyć routowaną podsieć, musimy najpierw zdefiniować: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **podsieć w notacji CIDR** (rozmiar między /57 a /64) +- **adres next-hop** (czyli adres IPv6 hosta) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Pamiętaj, że dana podsieć nie może pokrywać się z żadną inną zdefiniowaną podsiecią, a adres next-hop musi należeć do pierwszej części (mostkowanej podsieci /64) prefiksu Additional IPv6. -The example below shows how to define such a subnet: +Poniższy przykład pokazuje, jak zdefiniować taką podsieć: -![continue](images/20240418-02.png){.thumbnail} +![kontynuuj](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +W tym przypadku zdefiniowaliśmy routowaną podsieć `2001:41d0:abcd:ef10::/60`, która zostanie delegowana do maszyny wirtualnej hostowanej na: `2001:41d0:abcd:ef00::2`. /// -#### Host-side configuration +#### Konfiguracja po stronie hosta -/// details | Static IP configuration for a host (recommended) +/// details | Statyczna konfiguracja IP hosta (zalecana) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +W przypadku hostowania maszyn wirtualnych zdecydowanie zalecamy stosowanie statycznej konfiguracji na hoście. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Skonfiguruj adres IPv6, uruchom interfejs i (opcjonalnie) dodaj trasę domyślną przez interfejs vRack: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +417,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Automatyczna konfiguracja IP (SLAAC) dla hosta -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +W niektórych przypadkach możesz chcieć skonfigurować interfejsy z SLAAC i przekazywaniem IP jednocześnie. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Pamiętaj, że wiąże się to z dodatkowymi ryzykami (takimi jak utrata dostępu nie tylko do hosta, ale także do wszystkich maszyn wirtualnych) i nie jest zalecane. -Ensuring IPv6 forwarding is enabled: +Upewnij się, że przekazywanie IPv6 jest włączone: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Skonfiguruj akceptowanie Router Advertisements (na interfejsie vRack eth1 w naszym przykładzie): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +437,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Konfiguracja routowanej podsieci na hoście i wewnątrz maszyny wirtualnej -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Aby host wiedział, co zrobić z pakietami adresowanymi do nowej routowanej podsieci (która będzie na maszynie wirtualnej), musimy dodać dla niej specyficzną trasę. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +W naszym przykładzie do routingu użyjemy łącza veth z adresem fd00::2/64 wewnątrz maszyny wirtualnej. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Pamiętaj, że jest to bardzo specyficzne dla zainstalowanego hypervisora (mogą to być interfejsy vSwitch lub veth). W tym celu zapoznaj się z przewodnikiem dotyczącym sieci konkretnego hypervisora. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +452,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Konfiguracja routowanej podsieci wewnątrz maszyny wirtualnej -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Pamiętaj, że łącze używane między hostem a maszynami wirtualnymi jest bardzo specyficzne dla zainstalowanego hypervisora (mogą to być interfejsy vSwitch lub veth). W tym celu zapoznaj się z przewodnikiem dotyczącym sieci konkretnego hypervisora. -Add our routed IP block inside a VM to ensure it can accept packets: +Dodaj nasz routowany blok IP wewnątrz maszyny wirtualnej, aby mogła ona akceptować pakiety: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Dodaj trasę domyślną na maszynie wirtualnej, aby ruch mógł z niej wychodzić: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +471,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Weryfikacja konfiguracji -/// details | Local, on a host +/// details | Lokalna, na hoście -Ping from the host into the container (using local link): +Ping z hosta do kontenera (przy użyciu łącza lokalnego): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +484,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Ping z hosta do kontenera (przy użyciu routowanej podsieci): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +493,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Sprawdź trasę do podsieci /60 na hoście: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +502,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Lokalna, na maszynie wirtualnej -First, check the routing table: +Najpierw sprawdź tabelę routingu: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +513,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Ping interfejsu link-local hosta: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +522,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Ping globalnego interfejsu hosta: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +531,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Na koniec przeprowadźmy ping zewnętrznego adresu IPv6 z maszyny wirtualnej: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +540,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +Lub, używając nazwy domeny: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +551,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | Ze zdalnego hosta -Let's check connectivity to our VM from outside the OVHcloud network: +Sprawdźmy łączność z maszyną wirtualną spoza sieci OVHcloud: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +562,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +I traceroute ze zdalnego hosta (gdzieś w Internecie): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +575,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +W tym przykładzie: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- hop 10 - adres IP naszego hosta +- hop 11 - adres IP naszej maszyny wirtualnej /// -## Multiple region locations vs. global vRack +## Wiele lokalizacji regionalnych a globalna sieć vRack -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +Technologia vRack OVHcloud umożliwia organizacjom łączenie serwerów w różnych lokalizacjach tak, jakby znajdowały się w tym samym centrum danych. +Z drugiej strony usługi takie jak Additional IPv6 są regionalne, co oznacza, że ich funkcjonalność jest powiązana z konkretną lokalizacją. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +Poniżej przedstawiono architekturę do celów edukacyjnych z dwoma różnymi regionami i różnymi blokami Additional IPv6 ogłaszanymi z każdego z nich. Przedstawiono również hosta z adresami IP z obu sieci oraz przykład nieoptymalne trasy - hosta w jednym regionie zaadresowanego adresem IPv6 ogłaszanym w innym regionie: -![image](images/20240418-08.png){.thumbnail} +![obraz](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Należy pamiętać, że w takich konfiguracjach (z Additional IPv6 z więcej niż jednego regionu) SLAAC **musi być wyłączone w całej sieci vRack** (ponieważ może to prowadzić do nieprzewidywalnych wyników i losowej utraty łączności). -### Benefits +### Korzyści -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Lepsza łączność:** Dzięki wykorzystaniu sieci vRack wraz z blokami publicznych adresów IP routowanymi w wielu lokalizacjach, firmy mogą zapewnić bezproblemową komunikację na całym świecie, niezależnie od fizycznej lokalizacji serwerów zaplecza. +- **Przejście do chmury:** Technologia vRack może być doskonałym czynnikiem umożliwiającym pierwsze kroki w kierunku strategii organizacyjnej "move-to-cloud", odblokowując niektóre starsze aplikacje, które nadal wymagają lokalnej komunikacji sieciowej. -### Risks and Considerations +### Ryzyka i uwagi -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Brak obsługi SLAAC w konfiguracjach wielolokalizacyjnych:** Gdy istnieje więcej niż jedna lokalizacja obsługująca routing publicznego ruchu IP (zarówno IPv4, jak i IPv6) do tej samej sieci vRack, Stateless Address Autoconfiguration (SLAAC) **nie powinno być używane**. Jako przykład takiej sytuacji rozważmy istniejące hosty używające adresów IPv4. Takie hosty są automatycznie rekonfigurowane przez SLAAC z bramą IPv6 skonfigurowaną z innego regionu. Wraz z priorytetyzacją IPv6 nad IPv4 przez niektóre systemy operacyjne sytuacja ta może prowadzić do nieoptymalne routingu, a nawet całkowitej utraty łączności dla takich hostów. -## Known Limitations +## Znane ograniczenia -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Zrozumienie ograniczeń korzystania z **Additional IPv6** w środowisku **vRack** jest kluczowe dla efektywnego planowania sieci. Oto kluczowe ograniczenia do uwzględnienia: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 działa tylko z vRack**: Należy pamiętać, że adresy Additional IPv6 można konfigurować tylko z backendami podłączonymi do sieci vRack. +- **Ograniczenia SLAAC w konfiguracjach wielolokalizacyjnych**: Stateless Address Autoconfiguration (SLAAC) nie jest obsługiwane, gdy publiczny ruch IP (zarówno IPv6, jak i IPv4) jest routowany do sieci vRack w wielu lokalizacjach regionalnych. +- **Do 128 hostów w mostkowanej podsieci**: Można używać do 128 adresów IP bezpośrednio w sieci vRack. +- **Do 128 tras next-hop**: Można używać do 128 tras dla routowanych podsieci wewnątrz sieci vRack. +- **Limit przepustowości publicznej**: Ruch wychodzący z OVHcloud do Internetu jest ograniczony do 5 Gbps per lokalizacja regionalna. +- **Limity przydziału bloków IPv6**: Jeden dodatkowy blok IPv6 per sieć vRack w lokalizacji regionalnej. Maksymalnie 3 bloki (/56) per lokalizacja regionalna. +- **Mobilność bloków Additional IPv6**: Ze względu na hierarchiczny projekt przestrzeni adresowej IPv6, bloki Additional IPv6 są specyficzne dla regionu. Oznacza to, że bloków nie można przenosić między regionami, choć mogą być ponownie przypisywane do dowolnego backendu podłączonego do sieci vRack. +- **Brak bezpośredniej obsługi VLAN 802.1Q w sieci vRack przez Additional IPv6**: Konfiguracja może być wykonana tylko z natywnym VLANem sieci vRack. Do przekazywania pakietów wewnątrz konkretnego VLANu (sieci vRack) potrzebny będzie dedykowany host po stronie klienta. +- **Obecnie routing Additional IPv6 do sieci vRack nie jest obsługiwany w regionach APAC (Azja-Pacyfik).** -## Go further +## Sprawdź również -Join our [community of users](/links/community). +Dołącz do [grona naszych użytkowników](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md index 6ef93a06ea9..a41cb749d96 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.pt-pt.md @@ -1,7 +1,7 @@ --- -title: Configuring an IPv6 block in a vRack (EN) -excerpt: This guide will show you how to configure a block of public IPv6 addresses for use with the vRack -updated: 2026-03-09 +title: Configurar um bloco Additional IPv6 num vRack +excerpt: "Saiba como configurar um bloco de endereços IPv6 públicos para utilização num vRack" +updated: 2026-03-11 --- -## Objective +## Objetivo -The vRack network serves as a global private network bridging various OVHcloud products, enabling the creation of sophisticated network solutions. Beyond facilitating private connections, it also supports routing public IP addresses. +A rede vRack é uma rede privada global que interliga diferentes produtos OVHcloud e permite a criação de soluções de rede sofisticadas. Para além de facilitar as ligações privadas, suporta também o roteamento de endereços IP públicos. -**This guide focuses on Additional IPv6 address block configuration within a vRack network.** +**Este guia centra-se na configuração de blocos de endereços Additional IPv6 numa rede vRack.** > [!primary] > -> vRack supports both IPv4 and IPv6 public routing with Additional IP address blocks. You can find the instructions on how to configure IPv4 blocks in this guide: [Configuring an IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). +> O vRack suporta o roteamento público IPv4 e IPv6 com blocos de endereços Additional IP. Pode encontrar as instruções sobre a configuração de blocos IPv4 neste guia: [Configurar um bloco IP no vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack). > > [!primary] > -> This article is focusing on Additional IP configuration over a vRack network. If you look for guidance on Additional IP configuration together with primary IP (on public network interface), read the following articles: +> Este artigo detalha a configuração de endereços Additional IP numa rede vRack. Se procura instruções sobre a configuração de endereços Additional IP com um endereço IP principal (na interface de rede pública), consulte os seguintes artigos: > > - IPv4: -> - [Configuring IP aliasing on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). -> - [Configuring IP aliasing on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> - [Configurar um endereço IP em alias num servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipaliasing). +> - [Configurar um endereço IP em alias num VPS](/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing). +> > - IPv6: -> - [Configuring IPv6 on dedicated servers](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). -> - [Configuring IPv6 on a VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). -> - [Configuring IPv6 on a Public Cloud instance](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). +> - [Configurar IPv6 num servidor dedicado](/pages/bare_metal_cloud/dedicated_servers/network_ipv6). +> - [Configurar IPv6 num VPS](/pages/bare_metal_cloud/virtual_private_servers/configure-ipv6). +> - [Configurar IPv6 numa instância Public Cloud](/pages/public_cloud/public_cloud_network_services/configuration-02-how-to-configure-ipv6). > -## Introduction - -IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack: +## Introdução -- **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4. +O IPv6 revoluciona as redes dentro do vRack da OVHcloud, oferecendo uma solução às limitações do IPv4 e funcionalidades adaptadas à Internet moderna. A sua implementação é uma resposta direta à necessidade de arquiteturas de Internet mais extensas, seguras e sofisticadas. Eis as principais vantagens da integração do IPv6 no vRack: -- **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments. +- **Flexibilidade para redes avançadas**: o IPv6 aumenta consideravelmente o espaço de endereçamento, proporcionando a flexibilidade necessária para escalar a infraestrutura, gerir cenários de failover e suportar soluções de maior dimensão. Isto permite que as redes cresçam e se adaptem sem as restrições de endereçamento do IPv4. -- **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs). +- **Roteamento hierárquico e segmentação**: o IPv6 permite um roteamento hierárquico eficiente e uma segmentação lógica da infraestrutura. Isto melhora a gestão e a segurança da rede, ideal para a revenda de máquinas virtuais com sub-redes dedicadas ou para a segmentação da infraestrutura de rede. -By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage. +- **Baixa latência**: a conectividade IPv6 nativa de ponta a ponta pode facilitar a implementação de serviços sensíveis à latência, como o streaming multimédia, uma vez que muitas redes de fornecedores recentes são construídas com IPv6 nativo. Nessas redes, a utilização de serviços IPv4 cria latência (e custos) adicionais. +Ao tirar partido do IPv6 dentro do vRack, os utilizadores da OVHcloud podem usufruir de um ambiente de rede mais seguro, eficiente e escalável, pronto para responder às exigências das utilizações modernas da Internet. -## Requirements +## Requisitos -- A [vRack](/links/network/vrack) service activated in your account -- A [vRack compatible server](/links/network/vrack) attached to your vRack network -- Access to the [OVHcloud Control Panel](/links/manager) +- Um serviço [vRack](/links/network/vrack) ativo na sua conta +- Um [servidor compatível com vRack](/links/network/vrack) ligado à sua rede vRack +- Acesso à [área de cliente OVHcloud](/links/manager) > [!warning] -> This feature might be unavailable or limited on servers of the [**Eco** product line](/links/bare-metal/eco-about). +> Esta funcionalidade pode estar limitada ou indisponível nos servidores da [gama **Eco**](/links/bare-metal/eco-about). > -> Please visit our [comparison page](/links/bare-metal/eco-compare) for more information. +> Consulte a nossa [página de comparação dos servidores Eco](/links/bare-metal/eco-compare) para obter mais informações. -## Instructions +## Instruções -### Obtaining a new Additional IPv6 block +### Obter um novo bloco Additional IPv6 -While requesting a new Additional IPv6 block, it's important to note that the allocation is regional. This means the IPv6 block you receive will be tied to a specific region, defining where public traffic enters your vRack network (thus, where the gateway is located). +Ao solicitar um novo bloco Additional IPv6, é importante notar que a alocação é regional. Isto significa que o bloco IPv6 que recebe estará associado a uma região específica, definindo o ponto de entrada do tráfego público na sua rede vRack (ou seja, a localização do gateway). -/// details | Request a new Additional IPv6 block +/// details | Solicitar um novo bloco Additional IPv6 -You can order your new additional IPv6 block [here](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). +Pode encomendar o seu novo bloco IPv6 adicional [aqui](https://www.ovh.com/manager/#/dedicated/ip/agoraOrder/ipv6?catalogName=ip). -![configuration page](images/500.png){.thumbnail} +![página de configuração](images/500.png){.thumbnail} -Next you need to follow the step-by-step instructions. +De seguida, siga as instruções passo a passo. -Your new Additional IPv6 will then be available on your vRack configuration page. +O seu Additional IPv6 estará então disponível na página de configuração do seu vRack. /// -### Configuring IPv6 in a vRack (basic mode) +### Configurar o IPv6 num vRack (modo simples) -In this section we will present basic IPv6 setup for your vRack connected hosts. +Nesta secção apresentamos a configuração básica de IPv6 para os seus hosts ligados ao vRack. -![Configuring IPv6 in a vRack](images/20240418-03.png){.thumbnail} +![Configurar um IPv6 num vRack](images/20240418-03.png){.thumbnail} -The example above shows two hosts with their vRack-side interfaces configured with IPv6 public addresses. One host is configured manually, while the other has an IP address assigned automatically using SLAAC. All IP addresses belong to the first /64 subnet from a given public /56 Additional IPv6 block. Both leverage the vRack interface for public IPv6 connectivity. +O exemplo acima mostra dois hosts com as suas interfaces do lado do vRack configuradas com endereços IPv6 públicos. Um host tem uma configuração manual, enquanto o outro tem um endereço IP atribuído automaticamente via SLAAC. Todos os endereços IP pertencem à primeira sub-rede /64 de um dado bloco /56 de Additional IPv6 públicas. Ambos utilizam a interface vRack para a conectividade IPv6 pública. -The default gateway for the first /64 subnet (bridged one) is the first address from the /56 block. In this example it is `2001:41d0:abcd:ef00::1`. This is distributed via SLAAC but must be manually configured (as a default route) if SLAAC is disabled. See the **Static IP configuration** section below. +O gateway predefinido para a primeira sub-rede /64 (a que está em bridge) é o primeiro endereço do bloco /56. Neste exemplo, o gateway é `2001:41d0:abcd:ef00::1`. Este é distribuído via SLAAC, mas deve ser configurado manualmente (como rota predefinida) se o SLAAC estiver desativado (consulte a secção **Configuração IP estática** abaixo). -/// details | Via the OVHcloud Control Panel +/// details | Através da área de cliente OVHcloud -- Open `Network`{.action} in the left-hand sidebar. -- Open `vRack private network`{.action}. -- Select the vRack concerned. +- Clique em `Network`{.action} no menu à esquerda. +- Clique em `Rede privada vRack`{.action}. +- Selecione o vRack em causa. -![vRack management](images/700.png){.thumbnail} +![gestão do vRack](images/700.png){.thumbnail} -On the left side, the possible options (eligible services to be configured) are listed. +Do lado esquerdo, estão listadas as opções disponíveis (serviços elegíveis para configurar). -On the right you see what is already configured with your vRack. +Do lado direito, pode ver o que já está configurado no seu vRack. -Select your new Additional IPv6 and add it to your vRack. +Selecione o seu novo Additional IPv6 e adicione-o ao seu vRack. -![vRack selection](images/701.png){.thumbnail} +![seleção do vRack](images/701.png){.thumbnail} -You now have your new Additional IPv6 added to your vRack. +O seu novo Additional IPv6 foi adicionado ao seu vRack. -### Static IP configuration +### Configuração IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. +Após o bloco Additional IPv6 /56 ser atribuído a uma rede vRack, a primeira sub-rede /64 fica em bridge com o mesmo. -This means you can easily use such IPs on your hosts with static IP configuration on vRack interfaces (see the next section for a host-side configuration example). +Isto significa que pode facilmente utilizar esses IPs nos seus hosts com uma configuração IP estática nas interfaces vRack (consulte a secção seguinte para um exemplo de configuração do lado do host). -### Automatic IP configuration (SLAAC) +### Configuração IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled for the first /64 of your block (this one is always bridged) at any time using this slider button: +Para simplificar o endereçamento IP dentro da sua rede, pode utilizar o SLAAC. Pode ser ativado apenas por sub-rede em bridge e pode ser ativado para a primeira sub-rede /64 do seu bloco (esta está sempre em bridge) a qualquer momento usando este botão de cursor: -![enabling SLAAC](images/702.png){.thumbnail} +![ativar SLAAC](images/702.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Não se esqueça de configurar o SLAAC na sua máquina host. /// -/// details | Via the APIv6 (alternative way) +/// details | Através da APIv6 (método alternativo) -### Attributing an Additional IPv6 to a vRack +Quando solicita um IPv6 adicional, este é automaticamente atribuído ao seu vRack. -When you request an additional IPv6, it is automatically assigned to your vRack. - -If you removed this new Additional IPv6 from your vRack, you can assign it again using this POST method: +Se removeu este novo Additional IPv6 do seu vRack, pode reatribuí-lo usando este método POST: > [!api] > > @api {v1} /vrack POST /vrack/{serviceName}/ipv6 > -As in the example below: +Como no exemplo abaixo: ![api post add block](images/post-ipv6.png){.thumbnail} -Use the following call to verify the IPv6 has been assigned: +Use a seguinte chamada para verificar que o IPv6 foi atribuído: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6} > -As in the example below: +Como no exemplo abaixo: ![GET ipv6 call](images/20240418-04.png){.thumbnail} -Now, we see our block configured with a vRack. The next step is to configure the host or VMs. +Agora vemos o nosso bloco configurado com um vRack. O passo seguinte é configurar o host ou os hosts virtuais. -### Static IP configuration +### Configuração IP estática -Once the Additional IPv6 /56 block is attributed to a vRack network, there is still the first /64 subnet that is bridged with it. This means you can easily use such IPs on your hosts. +Após o bloco Additional IPv6 /56 ser atribuído a uma rede vRack, a primeira sub-rede /64 fica em bridge com o mesmo. Isto significa que pode facilmente utilizar esses IPs nos seus hosts. -Let's check exactly which subnet is bridged: +Vamos verificar quais são as sub-redes em bridge: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange > -As in the example below: +Como no exemplo abaixo: ![GET subrange bridged into your vRack](images/20240418-05.png){.thumbnail} -To get more details, use this call: +Para obter mais detalhes, use a seguinte chamada: > [!api] > > @api {v1} /vrack GET /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como no exemplo abaixo: ![GET subrange bridged into your vRack](images/20240418-06.png){.thumbnail} -Notice that IP autoconfiguration (SLAAC) is turned off by default. +Note que a configuração IP automática (SLAAC) está desativada por predefinição. -### Automatic IP configuration (SLAAC) +### Configuração IP automática (SLAAC) -To simplify IP addressing inside your network, you may want to use SLAAC. It can be enabled per-bridged-subnet only and can be enabled with this PUT method: +Para simplificar o endereçamento IP dentro da sua rede, pode utilizar o SLAAC. Pode ser ativado apenas por sub-rede em bridge e pode ser ativado com este método PUT: > [!api] > > @api {v1} /vrack PUT /vrack/{serviceName}/ipv6/{ipv6}/bridgedSubrange/{bridgedSubrange} > -As in the example below: +Como no exemplo abaixo: ![API call POST enable SLAAC](images/20240418-07.png){.thumbnail} -Don't forget to configure SLAAC on your host machine. +Não se esqueça de configurar o SLAAC na sua máquina host. /// -### Managing public IP bandwidth on vRack +### Gerir a largura de banda dos IPs públicos no vRack -By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). +Por predefinição, os blocos de Additional IP encaminhados através de um vRack beneficiam de uma largura de banda pública padrão de 5 Gbps na Europa e América do Norte, ou de 100 Mbps nas regiões APAC. Para mais detalhes sobre as opções disponíveis, consulte as opções de roteamento público na nossa [página do produto vRack](/links/network/vrack). -As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region. +Para responder ao crescimento das infraestruturas e às necessidades dos serviços com tráfego elevado, a OVHcloud disponibiliza opções de largura de banda pagas. Note que estas opções se aplicam **por vRack e por região**. Uma vez que os Additional IP estão associados a uma região específica, qualquer alteração da largura de banda afetará todos os endereços (IPv4 e IPv6) encaminhados para esse vRack na região em causa. -/// details | During the Additional IP ordering process +/// details | Durante a encomenda de um Additional IP -#### Choosing public bandwidth during an Additional IP order +#### Escolher a largura de banda pública durante a encomenda -The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend. +Pode modificar a largura de banda predefinida ao encomendar um novo bloco de Additional IP, desde que uma rede vRack seja selecionada como serviço backend. -To order a new Additional IPv6 block: +Para encomendar um novo bloco de Additional IPv6: -- Log in to the [OVHcloud Control Panel](/links/manager). -- Open the `Network`{.action} section in the left-hand sidebar. -- Select `Public IP addresses`{.action}. -- Click on the `Order IPs`{.action} button, near the top of the page. -- Select the IP version, then the vRack you want to attach your Additional IP to. -- Select the region you want your Additional IP to be in. -- Choose the public bandwidth you want to apply to your vRack for that specific region. -- Fill in the other options as necessary, then proceed with your order. +- Ligue-se à [área de cliente OVHcloud](/links/manager). +- Na barra lateral esquerda, aceda à secção `Network`{.action}. +- Selecione `Endereços IP Públicos`{.action}. +- Clique no botão `Encomendar IPs`{.action} no topo da página. +- Escolha a versão do IP e, de seguida, o vRack ao qual o Additional IP será associado. +- Selecione a região do seu Additional IP. +- Escolha a largura de banda pública a aplicar ao seu vRack para essa região. +- Configure as outras opções conforme necessário e finalize a encomenda. /// -/// details | From the vRack management page +/// details | A partir da página de gestão do vRack -#### Modifying vRack public bandwidth on management page +#### Modificar a largura de banda pública a partir da página de gestão -For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page. +Para os blocos de Additional IP já associados a um vRack, a largura de banda é gerida diretamente a partir da página de configuração do serviço. -To access the management interface: +Para aceder à interface de gestão: -- Open `Network`{.action} in the left-hand sidebar of your Control Panel. -- Select `vRack private network`{.action}. -- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack. +- Na barra lateral esquerda da área de cliente, abra `Network`{.action}. +- Selecione `Rede privada vRack`{.action}. +- Na coluna "IP público e largura de banda", clique no botão `Gerir`{.action} correspondente ao vRack pretendido. -The management page is organized into two tabs: -- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way. -- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth. +A interface de gestão divide-se em dois separadores: +- **Todos os serviços associados**: De momento, redireciona para a página de gestão clássica do vRack. Em breve, este separador listará de forma otimizada todos os produtos (servidores, projetos Cloud, etc.) ligados ao vRack. +- **Conectividade IP pública**: Permite gerir as opções de roteamento público do seu vRack, incluindo a largura de banda. -To modify the public bandwidth: +Para modificar a largura de banda: -- Navigate to the `Public IP routing`{.action} tab. -- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region. -- Within the window for the relevant region, click the `Modify bandwidth`{.action} button. -- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order. -- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes. +- Aceda ao separador `Conectividade IP pública`{.action}. +- A interface apresenta janelas de gestão por região (ex.: `eu-west-par`) associadas ao vRack, com a lista de IPs associados. +- No quadro da região em causa, clique em `Modificar a largura de banda`{.action}. +- Selecione a opção pretendida no painel da direita e clique em `Encomendar`{.action} para validar. +- Após o pagamento, a nova largura de banda ficará ativa no seu vRack na região escolhida após alguns minutos. > [!primary] > -> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle. +> O primeiro mês subscrito é faturado pro rata dos dias restantes. A tarifa completa será aplicada no ciclo de faturação seguinte. > -The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack. +O aumento da largura de banda aplicar-se-á a todos os endereços IP dessa região para o vRack selecionado. /// -#### Host-side commands +#### Comandos no host -/// details | Static IP configuration +/// details | Configuração IP estática -In a basic configuration, you may want to setup an IP address and routing manually. This is also the suggested way when your machine acts as a router (see the [configuring routed subnet](#routedmode) section) and has ipv6.forwarding mode enabled. +Numa configuração básica, pode querer configurar um endereço IP e o roteamento manualmente. Este é também o método recomendado quando a sua máquina está configurada como router (consulte a secção [configurar a sub-rede encaminhada](#routedmode)) e o modo ipv6.forwarding está ativado. -First, let's add an IP address on the vRack interface (in our example "eth1"): +Em primeiro lugar, vamos adicionar um endereço IP na interface vRack (no nosso exemplo "eth1"): ```bash $ sudo ip address add 2001:41d0:abcd:ef00::2/64 dev eth1 ``` -Please note that the first IP address in a block, `2001:41d0:abcd:ef00::1/64` is the gateway IP address and must not be used for host addressing. +(Note que o primeiro endereço IP de um bloco, neste caso `2001:41d0:abcd:ef00::1/64`, é o endereço do gateway e não deve ser utilizado para o endereçamento dos hosts). -Optionally, if you want to use the vRack interface as the main one for IPv6 traffic, the default route can be configured the following way: +Se pretender utilizar a interface vRack como interface principal para o tráfego IPv6, a rota predefinida pode ser configurada da seguinte forma: ```bash $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1/64 dev eth1 ``` -Finally, bring up the interface (and verify the configured IP on it): +Por fim, inicie a interface (e verifique o IP configurado na mesma): ```bash $ sudo ip link set up dev eth1 @@ -293,19 +291,20 @@ $ ip -6 addr list dev eth1 /// -/// details | Automatic IP configuration (SLAAC) +/// details | Configuração IP automática (SLAAC) -To use automatic configuration, please ensure you have configured your interface as follows: +Para utilizar a configuração automática, certifique-se de que configurou a sua interface da seguinte forma: -First, let's allow our host to accept Router Advertisements (for autoconfiguration) on the vRack interface (in our example "eth1"): +Em primeiro lugar, vamos permitir que o nosso host aceite os anúncios de roteamento (para a configuração automática) na interface vRack (no nosso exemplo "eth1"): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=1 ``` -Note that this setting will not work if ipv6.forwarding is enabled in your system. In such case please refer to [Automatic IP configuration for routed subnet](#host-side) for more details. +É importante notar que esta configuração não funcionará se o modo ipv6.forwarding estiver ativado no seu sistema. Nesse caso, consulte a [Configuração IP automática para uma sub-rede encaminhada](#host-side) para mais detalhes. + -Then, simply bring up the interface: +De seguida, inicie a interface: ```bash $ sudo ip link set up dev eth1 @@ -315,15 +314,15 @@ $ ip -6 addr list dev eth1 valid_lft 2322122sec preferred_lft 334922sec ``` -After a moment (the configuration must propagate), specific IPv6 address (with the flags global and dynamic) should be visible on the interface. +Após um curto período de tempo (o tempo de propagação da configuração), um endereço IPv6 específico (com os flags *global* e *dynamic*) deverá aparecer na interface. /// -#### Setup verification +#### Verificação da instalação /// details | Local -The most basic test is to ping a local IP address on a host: +O teste mais simples consiste em efetuar um ping para um endereço IP local a partir de um host: ```bash debian@host:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -334,9 +333,9 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -/// details | Remote +/// details | Remoto -Next, let's verify the connectivity from remote: +De seguida, vamos verificar a conectividade a partir de um endereço remoto: ```bash ubuntu@remote-test:~$ ping 2001:41d0:900:2100:fe34:97ff:feb0:c166 @@ -348,66 +347,66 @@ PING 2001:41d0:900:2100:fe34:97ff:feb0:c166(2001:41d0:900:2100:fe34:97ff:feb0:c1 /// -### Configuring an IPv6 in a vRack for routed mode +### Configurar um IPv6 num vRack para o modo encaminhado -In this section we will present a more advanced IPv6 setup, where your vRack connected hosts are acting as a routers for hosted Virtual Machines. Such VMs have delegated subnets from the main IPv6 block (presented with an orange color in the schema below). +Nesta secção apresentamos uma configuração IPv6 mais avançada, em que os seus hosts ligados ao vRack atuam como routers para as máquinas virtuais alojadas. Essas VMs dispõem de sub-redes delegadas provenientes do bloco IPv6 principal (representadas a cor de laranja no esquema abaixo). -![Configuring an IPv6 in a vRack for routed-mode](images/routed-mode-20240513.png){.thumbnail} +![Configurar um IPv6 num vRack para o modo encaminhado](images/routed-mode-20240513.png){.thumbnail} -The traffic path is as follows: Inbound traffic to a given VM (with specified subnet) is routed through the customer's vRack, first to a specified host (with a next-hop address), then using a local link (or vSwitch - black link fd00::/64 on a diagram) to the particular VM. -Traffic coming back from such a VM should use the default route via the first part of the local link (black one, fd00::1), then (possibly default) route from a host to its gateway. +O percurso do tráfego é o seguinte: o tráfego de entrada para uma determinada VM (com a sub-rede especificada) é encaminhado através do vRack do cliente, primeiro para um host específico (com um endereço next-hop) e depois através de uma ligação local (ou vSwitch - ligação preta fd00::/64 no diagrama) até à máquina virtual específica. +O tráfego proveniente de uma VM dessas deve utilizar a rota predefinida através da primeira parte da ligação local (a preta, fd00::1) e depois a rota (eventualmente predefinida) de um host para o seu gateway. -For routed subnet definition any prefix size can be used between /57 and /64. +Para a definição de uma sub-rede encaminhada, pode ser utilizado qualquer tamanho de prefixo entre /57 e /64. -The default gateway for the host is the first address from the /56 block, which is in this example: `2001:41d0:abcd:ef00::1`. The default gateway used by the VMs is the address of their host via the local link, which is `fd00::1` in this example. +O gateway predefinido do host é o primeiro endereço do bloco /56, que neste exemplo é: `2001:41d0:abcd:ef00::1`. Os gateways predefinidos utilizados pelas VMs são os endereços configurados do host (aqui fd00::1). -#### Define routed subnet +#### Definir uma sub-rede encaminhada -/// details | OVHcloud Control Panel actions +/// details | Área de cliente OVHcloud -After adding Additional IP to your vRack you can manage routed subnet by clicking `Add subnet`{.action} button. +Após adicionar o Additional IP ao seu vRack, pode gerir a sub-rede encaminhada clicando no botão `Adicionar uma sub-rede`{.action}. -![vRack select](images/600.png){.thumbnail} +![seleção vRack](images/600.png){.thumbnail} -To create a routed subnet, we must first define: +Para criar uma sub-rede encaminhada, devemos primeiro definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **sub-rede em notação CIDR** (tamanho entre /57 e /64) +- **endereço next-hop** (endereço IPv6 do host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Note que uma determinada sub-rede não pode sobrepor-se a outra sub-rede definida e que o endereço next-hop deve pertencer à primeira parte (sub-rede /64 em bridge) do seu prefixo Additional IPv6. -![continue](images/800.png){.thumbnail} +![continuar](images/800.png){.thumbnail} -This created routed subnet `2001:41d0:abcd::ef10::/60` reachable via next hop `2001:41d0:abcd::ef00::2`. +A sub-rede encaminhada `2001:41d0:abcd::ef10::/60` é acessível através do next hop `2001:41d0:abcd::ef00::2`. -![continue](images/801.png){.thumbnail} +![continuar](images/801.png){.thumbnail} /// -/// details | APIv6 commands +/// details | Comandos APIv6 -To create a routed subnet, we must first define: +Para criar uma sub-rede encaminhada, devemos primeiro definir: -- **subnet in CIDR notation** (size between /57 and /64) -- **next-hop address** (so the host's IPv6 address) +- **sub-rede em notação CIDR** (tamanho entre /57 e /64) +- **endereço next-hop** (portanto, o endereço IPv6 do host) -Please note that a given subnet can not overlap with any other subnet defined and next-hop address must belong to the first part (bridged /64 subnet) of your Additional IPv6 prefix. +Note que uma determinada sub-rede não pode sobrepor-se a outra sub-rede definida e que o endereço next-hop deve pertencer à primeira parte (sub-rede /64 em bridge) do seu prefixo Additional IPv6. -The example below shows how to define such a subnet: +O exemplo abaixo mostra como definir uma sub-rede deste tipo: -![continue](images/20240418-02.png){.thumbnail} +![continuar](images/20240418-02.png){.thumbnail} -Here, we defined a routed subnet `2001:41d0:abcd:ef10::/60 `which will be delegated to the VM hosted on: `2001:41d0:abcd:ef00::2`. +Aqui definimos a sub-rede encaminhada `2001:41d0:abcd:ef10::/60`, que será delegada à VM alojada no endereço `2001:41d0:abcd:ef00::2`. /// -#### Host-side configuration +#### Configuração do host -/// details | Static IP configuration for a host (recommended) +/// details | Configuração IP estática de um host (recomendado) -When hosting Virtual Machines, we strongly recommend to use static configuration on your host. +Quando aloja VMs, recomendamos vivamente a utilização de uma configuração estática no seu host. -Set up an IPv6 address, bring up the interface and (optionally) add the default route over the vRack interface: +Configure um endereço IPv6, inicie a interface e (opcionalmente) adicione a rota predefinida na interface vRack: ```bash $ sudo ip addr add 2001:41d0:abcd:ef00::2/64 dev eth1 @@ -417,19 +416,19 @@ $ sudo ip -6 route add default via 2001:41d0:abcd:ef00::1 dev eth1 /// -/// details | Automatic IP configuration (SLAAC) for a host +/// details | Configuração IP automática (SLAAC) para um host -In some cases, you may want to configure your interfaces with SLAAC and IP forwarding together. +Em alguns casos, pode querer configurar as suas interfaces com SLAAC e o reencaminhamento de IP em conjunto. -Please note that this brings additional risks (such as losing access not only to the host but also to all VMs) and is not recommended. +Note que isto apresenta riscos adicionais (como a perda de acesso não só ao host mas também a todas as VMs) e não é recomendado. -Ensuring IPv6 forwarding is enabled: +Verificação da ativação do reencaminhamento IPv6: ```bash $ sudo sysctl -w net.ipv6.conf.all.forwarding=1 ``` -Configuring Router Advertisements to be accepted (on vRack eth1 interface in our example): +Configuração dos anúncios de roteamento para serem aceites (na interface vRack eth1 no nosso exemplo): ```bash $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 @@ -437,13 +436,13 @@ $ sudo sysctl -w net.ipv6.conf.eth1.accept_ra=2 /// -/// details | Routed subnet configuration on a host and inside a VM +/// details | Configuração da sub-rede encaminhada num host e dentro de uma máquina virtual -To ensure that our host knows what to do with packets addressed to the new routed subnet (that will be on a VM), we must add a specific route for it. +Para garantir que o nosso host sabe como gerir os pacotes endereçados à nova sub-rede encaminhada (que estará numa VM), devemos adicionar uma rota específica para ela. -In our example this is the veth link with the address fd00::2/64 inside a VM we will use for routing. +No nosso exemplo, trata-se da ligação vEth com o endereço fd00::2/64, dentro de uma VM que utilizaremos para o encaminhamento. -Please note that this is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Note que isto é muito específico para o hipervisor instalado (pode ser vSwitch ou interfaces vEth). Consulte o guia de configuração de rede específico do hipervisor para esta configuração. ```bash $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 @@ -452,17 +451,17 @@ $ sudo ip -6 route add 2001:41d0:abcd:ef10::/60 via fd00::2 /// -/// details | Routed subnet configuration inside a VM +/// details | Configuração de uma sub-rede encaminhada dentro de uma VM -Again, please note that the link used between host and VMs is very specific to the hypervisor installed (it can be vSwitch or veth interfaces). Please refer to the specific hypervisor networking guide for this setup. +Mais uma vez, note que a ligação utilizada entre o host e as VMs é muito específica para o hipervisor instalado (pode ser vSwitch ou interfaces vEth). Consulte os guias de configuração de rede do seu hipervisor para esta configuração. -Add our routed IP block inside a VM to ensure it can accept packets: +Adicione o bloco de IPs encaminhados dentro de uma VM para garantir que pode aceitar pacotes: ```bash debian@vm-1:~$ sudo ip address add 2001:41d0:abcd:ef10::1/60 dev lo ``` -Add the default route on a VM to ensure traffic can get back out of it: +Adicione a rota predefinida numa VM para garantir que o tráfego pode sair da mesma: ```bash debian@vm-1:~$ sudo ip -6 route add default via fd00::1 @@ -471,11 +470,11 @@ debian@vm-1:~$ sudo ip -6 route add default via fd00::1 /// -#### Setup verification +#### Verificação da configuração -/// details | Local, on a host +/// details | Local, num host -Ping from the host into the container (using local link): +Efetue um ping do host para o container (usando a ligação local): ```bash debian@host:~$ ping fd00::2 @@ -484,7 +483,7 @@ PING fd00::2(fd00::2) 56 data bytes 64 bytes from fd00::2: icmp_seq=2 ttl=64 time=0.071 ms ``` -Ping from the host into the container (using routed subnet): +Efetue um ping do host para o container (usando a sub-rede encaminhada): ```bash debian@host:~$ ping 2001:41d0:abcd:ef10::1 @@ -493,7 +492,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=64 time=0.073 ms ``` -Check the route to our /60 subnet on a host: +Verifique a rota para a nossa sub-rede /60 num host: ```bash debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 @@ -502,9 +501,9 @@ debian@host:~$ ip -6 route get 2001:41d0:abcd:ef10::1 /// -/// details | Local, on a VM +/// details | Local, numa VM -First, check the routing table: +Em primeiro lugar, verifique a tabela de roteamento: ```bash debian@vm-1:~$ ip -6 route show @@ -513,7 +512,7 @@ fd00::/64 dev veth1b proto kernel metric 256 pref medium default via fd00::1 dev veth1b src 2001:41d0:abcd:ef10::1 metric 1024 pref medium ``` -Ping host link local interface: +Efetue um ping para a interface de ligação local do host: ```bash debian@vm-1:~$ ping fd00::1 @@ -522,7 +521,7 @@ PING fd00::1(fd00::1) 56 data bytes 64 bytes from fd00::1: icmp_seq=2 ttl=64 time=0.070 ms ``` -Ping host global interface: +Efetue um ping para a interface global do host: ```bash debian@vm-1:~$ ping 2001:41d0:abcd:ef00::2 @@ -531,7 +530,7 @@ PING 2001:41d0:abcd:ef00::2(2001:41d0:abcd:ef00::2) 56 data bytes 64 bytes from 2001:41d0:abcd:ef00::2: icmp_seq=2 ttl=64 time=0.080 ms ``` -Finally, let's ping an external IPv6 from a VM: +Por fim, efetue um ping para um endereço IPv6 externo a partir de uma VM: ```bash debian@vm-1:~$ ping 2001:41d0:242:d300:: @@ -540,7 +539,7 @@ PING 2001:41d0:242:d300::(2001:41d0:242:d300::) 56 data bytes 64 bytes from 2001:41d0:242:d300::: icmp_seq=2 ttl=57 time=0.417 ms ``` -Or, using a domain name: +Ou, utilizando um nome de domínio: ```bash debian@vm-1:~$ ping -6 proof.ovh.net @@ -551,9 +550,9 @@ PING proof.ovh.net(2001:41d0:242:d300:: (2001:41d0:242:d300::)) 56 data bytes /// -/// details | From remote host +/// details | A partir de um host remoto -Let's check connectivity to our VM from outside the OVHcloud network: +Vamos verificar a conectividade com a nossa VM a partir do exterior da rede OVHcloud: ```bash ubuntu@remote-test:~$ ping 2001:41d0:abcd:ef10::1 @@ -562,7 +561,7 @@ PING 2001:41d0:abcd:ef10::1(2001:41d0:abcd:ef10::1) 56 data bytes 64 bytes from 2001:41d0:abcd:ef10::1: icmp_seq=2 ttl=55 time=2.98 ms ``` -And traceroute from a remote host (somewhere on the internet): +E um traceroute a partir de um host remoto (na Internet): ```bash ubuntu@remote-test:~$ mtr -rc1 2001:41d0:abcd:ef10::1 @@ -575,47 +574,47 @@ HOST: remote-test Loss% Snt Last Avg Best Wrst StDe 11.|-- 2001:41d0:abcd:ef10::1 0.0% 1 2.2 2.2 2.2 2.2 0.0 ``` -In this example: +Neste exemplo: -- hop 10 - our host's IP address -- hop 11 - our VM's IP address +- hop 10 - Endereço IP do host +- hop 11 - Endereço IP da VM /// -## Multiple region locations vs. global vRack +## Localizações multi-região vs. vRack global -OVHcloud's vRack technology enables organizations to connect servers across different locations as if they were located within the same data center. -On the other hand, services like Additional IPv6 are regional, which means their functionality is linked to a particular location. +A tecnologia vRack da OVHcloud permite às empresas ligar servidores em diferentes localizações como se estivessem situados no mesmo datacenter. +Por outro lado, os serviços como o Additional IPv6 são regionais, o que significa que o seu funcionamento está ligado a uma localização específica. -Below, an architecture is presented for learning purposes with two different regions and different Additional IPv6 blocks announced from each. Also, there is a host presented with IP addresses from both networks as well as a suboptimal route example - a host in one region addressed with IPv6 address announced in another region: +Abaixo é apresentada uma arquitetura para fins pedagógicos com duas regiões diferentes e blocos Additional IPv6 diferentes anunciados a partir de cada uma delas. Além disso, é apresentado um host configurado com endereços IP de ambas as redes e um exemplo de rota não otimizada: um host numa região com um endereço IPv6 anunciado noutra região: ![image](images/20240418-08.png){.thumbnail} -Please note that in such setups (with Additional IPv6 from more than single region) SLAAC **must be turned off in the whole vRack** (as this may lead to unpredictable results and losing connectivity randomly). +Note que em tais configurações (com Additional IPv6 provenientes de mais de uma região), o SLAAC **deve estar desativado em todo o vRack** (pois isso pode conduzir a resultados imprevisíveis e perda aleatória de conectividade). -### Benefits +### Vantagens -- **Enhanced Connectivity:** By leveraging a vRack network together with public IP blocks routed in multiple locations, businesses can ensure seamless communication around the globe, regardless of backend server's physical locations. -- **Move to cloud:** vRack technology can be a great enabler of early steps toward a "move-to-cloud" organizational strategy, unblocking some legacy applications that still require local network communication. +- **Conectividade melhorada:** Ao tirar partido de uma rede vRack com blocos de IP públicos encaminhados em múltiplas localizações, as empresas podem garantir uma comunicação fluida em todo o mundo, independentemente das localizações físicas dos servidores backend. +- **Migração para a cloud:** A tecnologia vRack pode ser um grande facilitador dos primeiros passos para uma estratégia organizacional de "migração para a cloud", desbloqueando algumas aplicações legadas que ainda requerem comunicação de rede local. -### Risks and Considerations +### Riscos e considerações -- **No SLAAC support in multi-location setups:** When there is more than one location acting in routing public IP traffic (both IPv4 and IPv6) into the same vRack, Stateless Address Autoconfiguration (SLAAC) **should not be used**. As an example of such situation, let's consider existing hosts using IPv4 addresses. Such hosts are becoming reconfigured automatically by SLAAC with IPv6 gateway set up from other region. Together with IPv6 prioritization over IPv4 by some Operating Systems this situation can lead to suboptimal routing or even total loss of connectivity for such hosts. +- **Sem suporte SLAAC em configurações com múltiplas localizações:** Quando há mais de uma localização envolvida no encaminhamento de tráfego IP público (IPv4 e IPv6) no mesmo vRack, a configuração automática de endereços sem estado (SLAAC) **não deve ser utilizada**. Como exemplo dessa situação, consideremos hosts existentes que utilizam endereços IPv4. Esses hosts são reconfigurados automaticamente pelo SLAAC com um gateway IPv6 configurado a partir de outra região. Associada à priorização do IPv6 sobre o IPv4 por parte de alguns sistemas operativos, esta situação pode conduzir a um encaminhamento não otimizado ou mesmo à perda total de conectividade para esses hosts. -## Known Limitations +## Limitações conhecidas -Understanding the constraints of using **Additional IPv6** within the **vRack** environment is crucial for effective network planning. Here are the key limitations to consider: +Compreender as restrições relacionadas com a utilização de **Additional IPv6** no ambiente **vRack** é essencial para um planeamento eficaz da rede. Seguem-se as principais limitações a ter em conta: -- **Additional IPv6 goes only with vRack**: Please note that Additional IPv6 addresses can only be configured with vRack-connected backends. -- **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations. -- **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack. -- **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack. -- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location. -- **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location. -- **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend. -- **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed. -- **At the moment, routing Additional IPv6 into vRack is not supported in APAC (Asia-Pacific) regions.** +- **Additional IPv6 disponível apenas com vRack**: Note que os endereços Additional IPv6 só podem ser configurados com backends ligados ao vRack. +- **Limitações do SLAAC em configurações com múltiplas localizações**: A configuração automática de endereços sem estado (SLAAC) não é suportada quando há tráfego IP público (IPv6 e IPv4) encaminhado no vRack em múltiplas regiões. +- **Até 128 hosts dentro da sub-rede em bridge**: Pode utilizar até 128 endereços IP diretamente no vRack. +- **Até 128 rotas next-hop**: Pode utilizar até 128 rotas para sub-redes encaminhadas dentro de um vRack. +- **Limite da largura de banda pública**: O tráfego de saída da OVHcloud para a Internet está limitado a 5 Gbps por região. +- **Limites de alocação de blocos IPv6**: Um único bloco Additional IPv6 por vRack numa região. Máximo de 3 blocos (/56) por localização de região. +- **Mobilidade dos blocos Additional IPv6**: Devido ao design hierárquico do espaço de endereçamento IPv6, os blocos Additional IPv6 são específicos de cada região. Isto significa que os blocos não podem ser transferidos entre regiões, embora possam ser reatribuídos a qualquer backend ligado ao vRack. +- **Sem suporte direto de VLAN 802.1Q no vRack com Additional IPv6**: A configuração só pode ser efetuada com a VLAN nativa da sua rede vRack. Para o encaminhamento de pacotes dentro de uma VLAN específica (num vRack), será necessário um host dedicado do lado do cliente. +- **De momento, o encaminhamento de Additional IPv6 no vRack não é suportado nas regiões APAC.** -## Go further +## Quer saber mais? -Join our [community of users](/links/community). +Fale com a nossa [comunidade de utilizadores](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.de-de.md index e653032b8c3..a30fc7acba4 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/guide.de-de.md @@ -1,7 +1,7 @@ --- title: 'Konfiguration eines Additional IP-Blocks in einem vRack' excerpt: 'In dieser Anleitung erfahren Sie, wie Sie einen Block öffentlicher IP-Adressen für die Verwendung mit dem vRack konfigurieren.' -updated: 2026-03-09 +updated: 2026-03-11 ---