Skip to content

Commit 65d31c8

Browse files
bene2k1ldecarvalho-docnerda-codes
authored
feat(ddx): add network troubleshooting index (#4593)
* feat(ddx): add network troubleshooting * Apply suggestions from code review Co-authored-by: ldecarvalho-doc <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review Co-authored-by: Néda <[email protected]> --------- Co-authored-by: ldecarvalho-doc <[email protected]> Co-authored-by: Néda <[email protected]>
1 parent a5f2367 commit 65d31c8

File tree

3 files changed

+194
-154
lines changed

3 files changed

+194
-154
lines changed

‎pages/dedibox-network/troubleshooting.mdx‎

Lines changed: 0 additions & 154 deletions
This file was deleted.

‎pages/dedibox-network/troubleshooting/index.mdx‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
meta:
3+
title: Dedibox Network - Troubleshooting
4+
description: Find troubleshooting resources for resolving issues with Dedibox Network.
5+
content:
6+
paragraph: Find troubleshooting resources for resolving issues with Dedibox Network.
7+
dates:
8+
posted: 2025-03-11
9+
categories:
10+
- dedibox
11+
---
12+
13+
<ProductHeader
14+
productName="Dedibox Network troubleshooting"
15+
productLogo="Dedibox Network"
16+
description="Learn how to fix common issues related to the network connectivity of your Dedibox server."
17+
/>
18+
19+
## Featured Pages
20+
21+
<Grid>
22+
<DefaultCard
23+
title="Dedibox FAQ"
24+
description="General info on Dedibox servers."
25+
url="/faq/dedibox/"
26+
label="See more"
27+
/>
28+
<DefaultCard
29+
title="Troubleshooting Dedibox network issues"
30+
description="Learn how to diagnose and interpret connectivity issues with the network of your Dedibox server."
31+
url="/dedibox-network/troubleshoot/network-troubleshooting/"
32+
label="See more"
33+
/>
34+
<DefaultCard
35+
title="Dedibox anti-DDoS solutions"
36+
description="Scaleway provides comprehensive anti-DDoS protection for all its dedicated servers at no extra cost."
37+
url="/dedibox-network/reference-content/anti-ddos/"
38+
label="See more"
39+
/>
40+
</Grid>
41+
42+
## Dedibox Network troubleshooting pages
43+
44+
- [Troubleshooting Dedibox network issues](/dedibox-network/troubleshoot/network-troubleshooting/)

‎pages/dedibox-network/troubleshooting/network-troubleshooting.mdx‎

Lines changed: 150 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,150 @@
1+
---
2+
meta:
3+
title: Troubleshooting Dedibox network issues
4+
description: This page explains how to troubleshoot network-related issues on your Scaleway Dedibox dedicated server.
5+
content:
6+
h1: Troubleshooting Dedibox network issues
7+
paragraph: This page provides techniques for diagnosing and resolving network-related issues on your Scaleway Dedibox dedicated server.
8+
tags: mtr-test dedibox network iperf mtr
9+
dates:
10+
validation: 2025-03-11
11+
posted: 2021-08-20
12+
categories:
13+
- dedibox-network
14+
---
15+
16+
## Problem
17+
To diagnose network issues, you need to perform a series of tests.
18+
19+
### Symptoms
20+
- Slow network speeds
21+
- High packet loss
22+
- Unstable connections
23+
24+
## Possible Causes
25+
- Network congestion
26+
- Hardware issues
27+
- Misconfigured network settings
28+
29+
## Solution
30+
Use MTR and iPerf tests to analyze network performance.
31+
32+
### MTR Test
33+
34+
An MTR test combines the functionality of `traceroute` and `ping` to examine all points between two machines.
35+
36+
When performing an MTR test, it is important to run it in both directions:
37+
38+
- From your server to your connection's IP
39+
- From your connection to the server
40+
41+
#### On Linux
42+
Ensure the `mtr` package is installed:
43+
44+
```
45+
sudo apt-get install mtr
46+
```
47+
or
48+
```
49+
sudo yum install mtr
50+
```
51+
52+
#### On Windows
53+
54+
<Message type="note">
55+
You need to install [WinMTR](https://sourceforge.net/projects/winmtr/) on your server.
56+
</Message>
57+
58+
1. Download the application from its [project page](https://sourceforge.net/projects/winmtr/).
59+
2. Extract the archive and run the executable.
60+
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.
61+
62+
#### Example of an MTR test between a Scaleway Dedibox server and `free.fr`
63+
64+
```
65+
root@163-172-30-2:~# mtr --report free.fr
66+
Start: Sun May 1 16:23:57 2016
67+
HOST: 163-172-30-2 Loss% Snt Last Avg Best Wrst StDev
68+
1.|-- 163-172-30-1.rev.poneytel 0.0% 10 0.5 0.5 0.4 0.5 0.0
69+
2.|-- 195.154.1.248 0.0% 10 1.6 1.0 0.9 1.6 0.0
70+
3.|-- 195.154.1.254 0.0% 10 1.2 1.4 1.2 2.6 0.3
71+
...
72+
```
73+
74+
**Key metrics:**
75+
76+
- **Loss%**: Percentage of lost packets
77+
- **Snt**: Number of packets sent (here, 10)
78+
- **Last**: Latency of the last packet sent
79+
- **Avg**: Average latency for all packets sent
80+
- **Best**: Lowest recorded latency
81+
- **Wrst**: Highest recorded latency
82+
83+
### iPerf test
84+
85+
An iPerf test helps measure the available bandwidth of your server.
86+
87+
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`.
88+
89+
#### On Linux
90+
91+
If iPerf is not installed, install it using:
92+
93+
```
94+
sudo apt-get install iperf3
95+
```
96+
or
97+
```
98+
yum install iperf3
99+
```
100+
101+
Run the test:
102+
103+
```
104+
root@163-172-30-2:~# iperf3 -c ping.online.net -R
105+
------------------------------------------------------------
106+
Client connecting to ping.online.net, TCP port 5001
107+
TCP window size: 85.0 KByte (default)
108+
------------------------------------------------------------
109+
[ 3] local 163.172.30.2 port 36490 connected with 62.210.18.40 port 5001
110+
[ ID] Interval Transfer Bandwidth
111+
[ 3] 0.0-10.0 sec 1.10 GBytes 943 Mbits/sec
112+
```
113+
114+
<Message type="note">
115+
If your server is located in Amsterdam, use: `iperf3 -c ping-ams1.online.net -R`
116+
</Message>
117+
118+
#### On Windows
119+
120+
1. Download iPerf [from its website](https://iperf.fr/iperf-download.php#windows).
121+
2. Choose the latest version and download the file.
122+
3. Extract the file.
123+
4. Open a terminal and run:
124+
```
125+
iperf3.exe -c ping.online.net -p 5203
126+
```
127+
128+
**Key metrics:**
129+
130+
- **Interval**: Sampling interval in seconds
131+
- **Transfer**: Amount of data transferred
132+
- **Bandwidth**: Available bandwidth
133+
134+
### If your server’s network port is off
135+
136+
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:
137+
138+
<Message type="important">
139+
**Your server's network port is off.**
140+
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.
141+
</Message>
142+
143+
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.
144+
145+
If the message persists, try clearing your browser cache or reloading the page multiple times.
146+
147+
<Message type="important">
148+
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).
149+
</Message>
150+

0 commit comments

Comments
 (0)