Merge pull request #7694 from ovh/sa-bgp-guides-3

Y0Coss · web-flow · commit 0af9220d5d26 · 2025-03-31T08:38:57.000+02:00
BYOIP Range Fix
diff --git a/pages/network/bgp_service/bgp_service_config/guide.de-de.md b/pages/network/bgp_service/bgp_service_config/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-asia.md b/pages/network/bgp_service/bgp_service_config/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-au.md b/pages/network/bgp_service/bgp_service_config/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-ca.md b/pages/network/bgp_service/bgp_service_config/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-gb.md b/pages/network/bgp_service/bgp_service_config/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-ie.md b/pages/network/bgp_service/bgp_service_config/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-sg.md b/pages/network/bgp_service/bgp_service_config/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.en-us.md b/pages/network/bgp_service/bgp_service_config/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.es-es.md b/pages/network/bgp_service/bgp_service_config/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.es-us.md b/pages/network/bgp_service/bgp_service_config/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: BGP Service configuration
 excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objective
@@ -58,7 +58,7 @@ You need to provide us with the following parameters so that we can configure th
 | Location	| RBX | The location on which to deliver the service | |
 | vRack ID | 937 | vRack ID on which the BGP sessions will run | |
 | BYOIP | Y | IP prefix coming from the customer	| |
-| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
+| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/24 to /30) <br>&bull; IPv6 (/56) |
 | Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
 | Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.fr-ca.md b/pages/network/bgp_service/bgp_service_config/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Configuration du service BGP
 excerpt: En utilisant le service BGP, vous bénéficiez d'un contrôle total sur vos politiques de routage et la résilience du réseau. Suivez ce guide pour configurer et optimiser vos sessions BGP
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objectif
@@ -58,7 +58,7 @@ Vous devez nous fournir les paramètres suivants afin que nous puissions configu
 | Localisation	| RBX | Emplacement de livraison du service | |
 | ID vRack | 937 | ID du vRack sur lequel les sessions BGP vont s'exécuter | |
 | BYOIP | Y | Préfixe IP fourni par le client | |
-| Préfixe IP | 198.51.100.0/24 | Le préfixe IP public à utiliser <br> Des sous-ensembles appartenant à ce préfixe peuvent être annoncés : <br>&bull; Pour l'IPv4, n'importe quel sous-ensemble jusqu'à /32 <br>&bull; Pour l'IPv6, n'importe quel sous-ensemble jusqu'à /64 | Taille de préfixe autorisée : <br>&bull; IP OVHcloud (/24 à /30) <br>&bull; préfixe importé BYOIP (/19 à /24) <br>&bull; IPv6 (/56) |
+| Préfixe IP | 198.51.100.0/24 | Le préfixe IP public à utiliser <br> Des sous-ensembles appartenant à ce préfixe peuvent être annoncés : <br>&bull; Pour l'IPv4, n'importe quel sous-ensemble jusqu'à /32 <br>&bull; Pour l'IPv6, n'importe quel sous-ensemble jusqu'à /64 | Taille de préfixe autorisée : <br>&bull; IP OVHcloud (/24 à /30) <br>&bull; préfixe importé BYOIP (/24 à /30) <br>&bull; IPv6 (/56) |
 | Préfixe privé | 10.0.0.0 | Préfixe réservé aux IP des pairs BGP <br> Les 4 dernières adresses seront utilisées par OVHcloud pour les pairs BGP côté OVHcloud | IPv4 : Netmask /28 <br> IPv6 : Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | L'IP du client doit être spécifiée par ce dernier (pour le monitoring côté OVHcloud) | |
 | Peering IP 2 | 10.0.0.2 | L'IP du client doit être spécifiée par ce dernier (pour le monitoring côté OVHcloud) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.fr-fr.md b/pages/network/bgp_service/bgp_service_config/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Configuration du service BGP
 excerpt: En utilisant le service BGP, vous bénéficiez d'un contrôle total sur vos politiques de routage et la résilience du réseau. Suivez ce guide pour configurer et optimiser vos sessions BGP
-updated: 2025-03-27
+updated: 2025-03-31
 ---
 
 ## Objectif
@@ -58,7 +58,7 @@ Vous devez nous fournir les paramètres suivants afin que nous puissions configu
 | Localisation	| RBX | Emplacement de livraison du service | |
 | ID vRack | 937 | ID du vRack sur lequel les sessions BGP vont s'exécuter | |
 | BYOIP | Y | Préfixe IP fourni par le client | |
-| Préfixe IP | 198.51.100.0/24 | Le préfixe IP public à utiliser <br> Des sous-ensembles appartenant à ce préfixe peuvent être annoncés : <br>&bull; Pour l'IPv4, n'importe quel sous-ensemble jusqu'à /32 <br>&bull; Pour l'IPv6, n'importe quel sous-ensemble jusqu'à /64 | Taille de préfixe autorisée : <br>&bull; IP OVHcloud (/24 à /30) <br>&bull; préfixe importé BYOIP (/19 à /24) <br>&bull; IPv6 (/56) |
+| Préfixe IP | 198.51.100.0/24 | Le préfixe IP public à utiliser <br> Des sous-ensembles appartenant à ce préfixe peuvent être annoncés : <br>&bull; Pour l'IPv4, n'importe quel sous-ensemble jusqu'à /32 <br>&bull; Pour l'IPv6, n'importe quel sous-ensemble jusqu'à /64 | Taille de préfixe autorisée : <br>&bull; IP OVHcloud (/24 à /30) <br>&bull; préfixe importé BYOIP (/24 à /30) <br>&bull; IPv6 (/56) |
 | Préfixe privé | 10.0.0.0 | Préfixe réservé aux IP des pairs BGP <br> Les 4 dernières adresses seront utilisées par OVHcloud pour les pairs BGP côté OVHcloud | IPv4 : Netmask /28 <br> IPv6 : Netmask /124 |
 | Peering IP 1 | 10.0.0.1 | L'IP du client doit être spécifiée par ce dernier (pour le monitoring côté OVHcloud) | |
 | Peering IP 2 | 10.0.0.2 | L'IP du client doit être spécifiée par ce dernier (pour le monitoring côté OVHcloud) | |
diff --git a/pages/network/bgp_service/bgp_service_config/guide.it-it.md b/pages/network/bgp_service/bgp_service_config/guide.it-it.md
diff --git a/pages/network/bgp_service/bgp_service_config/guide.pl-pl.md b/pages/network/bgp_service/bgp_service_config/guide.pl-pl.md
diff --git a/pages/network/bgp_service/bgp_service_config/guide.pt-pt.md b/pages/network/bgp_service/bgp_service_config/guide.pt-pt.md
