diff --git a/pages/dedibox-network/troubleshooting.mdx b/pages/dedibox-network/troubleshooting.mdx deleted file mode 100644 index bb126d8005..0000000000 --- a/pages/dedibox-network/troubleshooting.mdx +++ /dev/null @@ -1,154 +0,0 @@ ---- -meta: - title: Dedibox Network - Troubleshooting - description: This page explains techniques for how to troubleshoot network related issues on your Scaleway Dedibox dedicated server. -content: - h1: Dedibox Network - Troubleshooting - paragraph: This page explains techniques how to troubleshoot network-related issues on your Scaleway Dedibox dedicated server. -tags: mtr-test dedibox network iperf mtr -dates: - validation: 2025-03-03 - posted: 2021-08-20 -categories: - - dedibox-network ---- - -## Running network tests - -To diagnose a network issue, you can perform different tests. - -## MTR test - -An MTR test combines the functions of traceroute and ping on all points between two machines. - -When running an MTR test, it is important to do it in both directions: - -- From the server to the IP of your connection -- From your connection to the server - -### On Linux -You have to check that the `mtr` packet is installed. - -``` -sudo apt-get install mtr -``` -or -``` -sudo yum install mtr -``` - -### On Windows - - - You have to install [WinMTR](https://sourceforge.net/projects/winmtr/) on your server. - - -1. Download the application from its [project page](https://sourceforge.net/projects/winmtr/). -2. Extract the archive and run the executable. -3. Enter the target (IP) of your test in the Host text box, then click **Start**. Wait one or two minutes before you stop the test. You can then make a screenshot or export the result with the functions of the software. - - Example of MTR between a Scaleway Dedibox server and `free.fr`: - - ``` - root@163-172-30-2:~# mtr --report free.fr - Start: Sun May 1 16:23:57 2016 - HOST: 163-172-30-2 Loss% Snt Last Avg Best Wrst StDev - 1.|-- 163-172-30-1.rev.poneytel 0.0% 10 0.5 0.5 0.4 0.5 0.0 - 2.|-- 195.154.1.248 0.0% 10 1.6 1.0 0.9 1.6 0.0 - 3.|-- 195.154.1.254 0.0% 10 1.2 1.4 1.2 2.6 0.3 - 4.|-- th2-crs16-1-be1503-t.intf 0.0% 10 1.3 1.3 1.1 1.4 0.0 - 5.|-- p11-crs16-1-be1001.intf.r 0.0% 10 4.5 3.0 1.4 4.5 0.7 - 6.|-- p11-9k-1-be1000.intf.rout 0.0% 10 1.5 2.1 1.4 3.5 0.6 - 7.|-- bzn-9k-2-sys-be2001.intf. 0.0% 10 1.7 1.8 1.6 2.8 0.0 - 8.|-- www.free.fr 0.0% 10 1.2 1.2 1.2 1.2 0.0 - ``` - - The results show: - - **Loss%** - : The percentage of lost packets - - **Snt** - : The number of packets sent during the test (here 10) - - **Last** - : The latency of the last packet sent between two points - - **Avg** - : Average latency for all packets sent between two points - - **Best** - : Latency of the best result - - **Wrst** - : Latency of the worst result - -## iPerf test - -With an iPerf test, you can check the available bandwidth of your server. - -The iPerf server ping.online.net has several ports available (5200-5209). If the server is busy on the default port, you can specify another port using the `-p` flag, for example: `-p 5203 (5204, 5205, etc.)`. - -### On Linux - -If iPerf is not yet installed on your server, you can install it with the following command: - -``` -sudo apt-get install iperf3 -``` -or -``` -yum apt-get install iperf3 -``` - -Then launch the test: - -``` -root@163-172-30-2:~# iperf3 -c ping.online.net -R ------------------------------------------------------------- -Client connecting to ping.online.net, TCP port 5001 -TCP window size: 85.0 KByte (default) ------------------------------------------------------------- -[ 3] local 163.172.30.2 port 36490 connected with 62.210.18.40 port 5001 -[ ID] Interval Transfer Bandwidth -[ 3] 0.0-10.0 sec 1.10 GBytes 943 Mbits/sec -If your server is located at Amsterdam execute: root@163-172-30-2:~# iperf3 -c ping-ams1.online.net -R -``` - -### On Windows - -1. Download the tool [from its website](https://iperf.fr/iperf-download.php#windows). -2. Choose the latest version and download the file. -3. Extract the file. -4. Open a terminal and run the following command: - ``` - \iperf3.exe -c ping.online.net -p 5203 - ``` - -The results show: - -**Interval** -: Sampling interval in seconds - -**Transfer** -: Amount of data transferred during the test - -**Bandwidth** -: Available bandwidth of your server - -## If your server's network port is off - -Sometimes when you change the mode of your dedicated server from normal to rescue mode during the reboot of a server, you may see the following error message in your console: - - - **Your server's network port is off.** - If you just asked for a server reboot, or to boot in rescue or test mode, this message will only be displayed for a few seconds. Otherwise, our network equipment may be on protective mode due to non-authorized traffic. In this case, ask the support team to unlock your server. - - -If this message appears in cycles or for long periods, it means your server is distributing one of the following: unauthorized DHCP traffic, a MAC address unassigned to the server, ARP requests, or too many sending or receiving requests per second. - -If you continue to see this message, empty your browser cache, as the old page may be kept in it. Alternatively, you can reload the page several times until the message disappears. - - - When setting up the WAN interface on a PfSense firewall you should disable autoconfiguration, as it might cause an IPv6 packet flood, shutting down your server's network port. If your network ports do not become available after a few minutes, you need to contact the support. - \ No newline at end of file diff --git a/pages/dedibox-network/troubleshooting/index.mdx b/pages/dedibox-network/troubleshooting/index.mdx new file mode 100644 index 0000000000..49fe91abc9 --- /dev/null +++ b/pages/dedibox-network/troubleshooting/index.mdx @@ -0,0 +1,44 @@ +--- +meta: + title: Dedibox Network - Troubleshooting + description: Find troubleshooting resources for resolving issues with Dedibox Network. +content: + paragraph: Find troubleshooting resources for resolving issues with Dedibox Network. +dates: + posted: 2025-03-11 +categories: + - dedibox +--- + + + +## Featured Pages + + + + + + + +## Dedibox Network troubleshooting pages + +- [Troubleshooting Dedibox network issues](/dedibox-network/troubleshoot/network-troubleshooting/) diff --git a/pages/dedibox-network/troubleshooting/network-troubleshooting.mdx b/pages/dedibox-network/troubleshooting/network-troubleshooting.mdx new file mode 100644 index 0000000000..b758b382f8 --- /dev/null +++ b/pages/dedibox-network/troubleshooting/network-troubleshooting.mdx @@ -0,0 +1,150 @@ +--- +meta: + title: Troubleshooting Dedibox network issues + description: This page explains how to troubleshoot network-related issues on your Scaleway Dedibox dedicated server. +content: + h1: Troubleshooting Dedibox network issues + paragraph: This page provides techniques for diagnosing and resolving network-related issues on your Scaleway Dedibox dedicated server. +tags: mtr-test dedibox network iperf mtr +dates: + validation: 2025-03-11 + posted: 2021-08-20 +categories: + - dedibox-network +--- + +## Problem +To diagnose network issues, you need to perform a series of tests. + +### Symptoms +- Slow network speeds +- High packet loss +- Unstable connections + +## Possible Causes +- Network congestion +- Hardware issues +- Misconfigured network settings + +## Solution +Use MTR and iPerf tests to analyze network performance. + +### MTR Test + +An MTR test combines the functionality of `traceroute` and `ping` to examine all points between two machines. + +When performing an MTR test, it is important to run it in both directions: + +- From your server to your connection's IP +- From your connection to the server + +#### On Linux +Ensure the `mtr` package is installed: + +``` +sudo apt-get install mtr +``` +or +``` +sudo yum install mtr +``` + +#### On Windows + + + You need to install [WinMTR](https://sourceforge.net/projects/winmtr/) on your server. + + +1. Download the application from its [project page](https://sourceforge.net/projects/winmtr/). +2. Extract the archive and run the executable. +3. Enter the target IP in the **Host** text box, then click **Start**. Wait one or two minutes before stopping the test. You can take a screenshot or export the results using the software's built-in functions. + +#### Example of an MTR test between a Scaleway Dedibox server and `free.fr` + +``` +root@163-172-30-2:~# mtr --report free.fr +Start: Sun May 1 16:23:57 2016 +HOST: 163-172-30-2 Loss% Snt Last Avg Best Wrst StDev +1.|-- 163-172-30-1.rev.poneytel 0.0% 10 0.5 0.5 0.4 0.5 0.0 +2.|-- 195.154.1.248 0.0% 10 1.6 1.0 0.9 1.6 0.0 +3.|-- 195.154.1.254 0.0% 10 1.2 1.4 1.2 2.6 0.3 +... +``` + +**Key metrics:** + +- **Loss%**: Percentage of lost packets +- **Snt**: Number of packets sent (here, 10) +- **Last**: Latency of the last packet sent +- **Avg**: Average latency for all packets sent +- **Best**: Lowest recorded latency +- **Wrst**: Highest recorded latency + +### iPerf test + +An iPerf test helps measure the available bandwidth of your server. + +The iPerf server `ping.online.net` offers several ports (5200-5209). If the default port is busy, specify another port using the `-p` flag, e.g., `-p 5203`. + +#### On Linux + +If iPerf is not installed, install it using: + +``` +sudo apt-get install iperf3 +``` +or +``` +yum install iperf3 +``` + +Run the test: + +``` +root@163-172-30-2:~# iperf3 -c ping.online.net -R +------------------------------------------------------------ +Client connecting to ping.online.net, TCP port 5001 +TCP window size: 85.0 KByte (default) +------------------------------------------------------------ +[ 3] local 163.172.30.2 port 36490 connected with 62.210.18.40 port 5001 +[ ID] Interval Transfer Bandwidth +[ 3] 0.0-10.0 sec 1.10 GBytes 943 Mbits/sec +``` + + + If your server is located in Amsterdam, use: `iperf3 -c ping-ams1.online.net -R` + + +#### On Windows + +1. Download iPerf [from its website](https://iperf.fr/iperf-download.php#windows). +2. Choose the latest version and download the file. +3. Extract the file. +4. Open a terminal and run: + ``` + iperf3.exe -c ping.online.net -p 5203 + ``` + +**Key metrics:** + +- **Interval**: Sampling interval in seconds +- **Transfer**: Amount of data transferred +- **Bandwidth**: Available bandwidth + +### If your server’s network port is off + +If you change your dedicated server's mode (e.g., from normal to rescue mode) during a reboot, you may see the following error in your console: + + + **Your server's network port is off.** + If you recently requested a reboot or changed to rescue/test mode, this message should disappear within a few seconds. If it persists, your network may have been blocked due to unauthorized traffic. Contact support to unlock your server. + + +If this message appears repeatedly or for long periods, your server may be sending unauthorized DHCP traffic, an unassigned MAC address, excessive ARP requests, or too many requests per second. + +If the message persists, try clearing your browser cache or reloading the page multiple times. + + + When configuring the WAN interface on a **PfSense firewall**, disable autoconfiguration. It may cause an IPv6 packet flood, shutting down your server’s network port. If the network ports do not become available within a few minutes, contact [support](https://console.online.net/en/assistance/ticket). + +