Skip to content

Commit 64dc511

Browse files
Jessica41Jessica41
committed
minor update
1 parent 5b4bd62 commit 64dc511

File tree

2 files changed

+48
-51
lines changed

2 files changed

+48
-51
lines changed

‎pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.de-de.md‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -66,8 +66,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
6666
6767

6868
> [!tabs]
69-
> Debian 11
70-
>> **Debian 11**
69+
> **Debian 11**
70+
>> Debian 11
7171
>>
7272
>> **Schritt 1: Automatische Netzwerkkonfiguration deaktivieren**
7373
>>
@@ -150,8 +150,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
150150
>> sudo systemctl restart networking
151151
>> ```
152152
>>
153-
> *Debian 12, Ubuntu 20.04+
154-
>> **Debian 12, Ubuntu 20.04 und höher**
153+
> **Debian 12, Ubuntu 22.04+**
154+
>> Debian 12, Ubuntu 22.04 und höher
155155
>>
156156
>> Die Konfigurationsdatei für Ihre Additional IPs befindet sich in `/etc/netplan/`. In diesem Beispiel heißt sie `50-cloud-init.yaml`.
157157
>>
@@ -240,8 +240,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
240240
>>
241241
>> Wiederholen Sie diesen Vorgang für jede Additional IP-Adresse.
242242
>>
243-
> AlmaLinux (8 & 9), Rocky Linux (8 & 9)
244-
>> **AlmaLinux (8/9), Rocky Linux (8/9)**
243+
> **AlmaLinux / Rocky Linux**
244+
>> AlmaLinux (8/9/10), Rocky Linux (8/9/10)
245245
>>
246246
>> Die Hauptkonfigurationsdatei befindet sich im Ordner `/etc/sysconfig/network-scripts/`. In diesem Beispiel ist es `ifcfg-eth0`. Überprüfen Sie den Dateinamen in Ihrem Ordner, bevor Sie Änderungen vornehmen.
247247
>>
@@ -300,8 +300,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
300300
>> sudo systemctl restart NetworkManager
301301
>> ```
302302
>>
303-
> Fedora 42
304-
>> **Fedora 42**
303+
> **Fedora 42**
304+
>> Fedora 42
305305
>>
306306
>> Fedora verwendet Schlüsseldateien. NetworkManager hat zuvor Netzwerkprofile im Format ifcfg in diesem Verzeichnis gespeichert: `/etc/sysconfig/network-scripts/`. Da ifcfg nicht mehr unterstützt wird, erstellt NetworkManager keine neuen Profile mehr in diesem Format. Die Konfigurationsdatei befindet sich nun in `/etc/NetworkManager/system-connections/`.
307307
>>
@@ -367,8 +367,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
367367
>> sudo systemctl restart NetworkManager
368368
>> ```
369369
>>
370-
> cPanel
371-
>> **cPanel**
370+
> **cPanel**
371+
>> cPanel
372372
>>
373373
>> **Schritt 1: Auf den Bereich IP-Verwaltung des WHM zugreifen**
374374
>>
@@ -395,8 +395,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
395395
>>
396396
>> ![check configured IP](images/cpanel-alma-3.png){.thumbnail}
397397
>>
398-
> Plesk
399-
>> **Plesk**
398+
> **Plesk**
399+
>> Plesk
400400
>>
401401
>> **Schritt 1: Auf die IP-Verwaltung von Plesk zugreifen**
402402
>>
@@ -422,8 +422,8 @@ In den folgenden Beispielen verwenden wir den Texteditor `nano`. Auf einigen Bet
422422
>>
423423
>> ![aktuelle IP-Konfiguration](images/plesk-final-configuration.png){.thumbnail}
424424
>>
425-
> Windows Servers
426-
>> **Windows Servers**
425+
> **Windows Server**
426+
>> Windows Server
427427
>>
428428
>> **Schritt 1: Netzwerkkonfiguration überprüfen**
429429
>>

‎pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-gb.md‎

Lines changed: 34 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ In the examples below, we will use the `nano` text editor. With some operating s
6565
>
6666
6767
> [!tabs]
68-
> Debian 11
69-
>> **Debian 11**
68+
> **Debian 11**
69+
>> Debian 11
7070
>>
71-
>> Step 1: Disable automatic network configuration
71+
>> **Step 1: Disable automatic network configuration**
7272
>>
7373
>> Open the following file path with a text editor:
7474
>>
@@ -84,7 +84,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
8484
>>
8585
>> Creating this configuration file will prevent changes to your network configuration from being made automatically.
8686
>>
87-
>> Step 2: Create a backup
87+
>> **Step 2: Create a backup**
8888
>>
8989
>> By default, the configuration file is located in the path `etc\network\interfaces.d`.
9090
>>
@@ -100,7 +100,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
100100
>> sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
101101
>> ```
102102
>>
103-
>> Step 3: Edit the configuration file
103+
>> **Step 3: Edit the configuration file**
104104
>>
105105
>> The first step is to verify your network interface name with this command:
106106
>>
@@ -146,7 +146,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
146146
>>
147147
>> ///
148148
>>
149-
>> Step 4: Restart the interface
149+
>> **Step 4: Restart the interface**
150150
>>
151151
>> Apply the changes with the following command:
152152
>>
@@ -161,15 +161,15 @@ In the examples below, we will use the `nano` text editor. With some operating s
161161
>>
162162
>> The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
163163
>>
164-
>> Step 1: Create the network configuration file
164+
>> **Step 1: Create the network configuration file**
165165
>>
166166
>> In our example, our file is call `51-cloud-init.yaml`:
167167
>>
168168
>> ```bash
169169
>> sudo touch /etc/netplan/51-cloud-init.yaml
170170
>> ```
171171
>>
172-
>> Step 2: Edit the configuration file
172+
>> **Step 2: Edit the configuration file**
173173
>>
174174
>> You can verify your network interface name with this command:
175175
>>
@@ -228,7 +228,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
228228
>>
229229
>> Save and close the file.
230230
>>
231-
>> Step 3: Apply the new network configuration
231+
>> **Step 3: Apply the new network configuration**
232232
>>
233233
>> You can test your configuration using this command:
234234
>>
@@ -242,21 +242,20 @@ In the examples below, we will use the `nano` text editor. With some operating s
242242
>> sudo netplan apply
243243
>> ```
244244
>>
245-
> CentOS 7, AlmaLinux (8/9), Rocky Linux (8/9)
246-
>>
247-
>> **CentOS 7, AlmaLinux (8/9), Rocky Linux (8/9)**
245+
> **AlmaLinux / Rocky Linux (8/9)**
246+
>> AlmaLinux (8/9/10), Rocky Linux (8/9/10)
248247
>>
249248
>> The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
250249
>>
251250
>> For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
252251
>>
253-
>> Step 1: Determine the interface
252+
>> **Step 1: Determine the interface**
254253
>>
255254
>> ```bash
256255
>> ip a
257256
>> ```
258257
>>
259-
>> Step 2: Create the configuration file
258+
>> **Step 2: Create the configuration file**
260259
>>
261260
>> First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
262261
>>
@@ -287,7 +286,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
287286
>> ```
288287
>> ///
289288
>>
290-
>> Step 3: Restart the interface
289+
>> **Step 3: Restart the interface**
291290
>>
292291
>> ```bash
293292
>> sudo systemctl restart network
@@ -299,13 +298,12 @@ In the examples below, we will use the `nano` text editor. With some operating s
299298
>> sudo systemctl restart NetworkManager
300299
>> ```
301300
>>
302-
> Fedora 42
303-
>>
304-
>> **Fedora 42**
301+
> **Fedora 42**
302+
>> Fedora 42
305303
>>
306304
>> Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
307305
>>
308-
>> Step 1: Create a backup
306+
>> **Step 1: Create a backup**
309307
>>
310308
>> In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
311309
>>
@@ -320,7 +318,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
320318
>> sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
321319
>> ```
322320
>>
323-
>> Step 2: Edit the config file
321+
>> **Step 2: Edit the config file**
324322
>>
325323
>> > [!primary]
326324
>> > Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
@@ -359,25 +357,24 @@ In the examples below, we will use the `nano` text editor. With some operating s
359357
>> ```
360358
>> ///
361359
>>
362-
>> Step 3: Restart the interface
360+
>> **Step 3: Restart the interface**
363361
>>
364362
>> You now need to restart your interface:
365363
>>
366364
>> ```bash
367365
>> sudo systemctl restart NetworkManager
368366
>> ```
369367
>>
370-
> cPanel
371-
>>
372-
>> **cPanel**
368+
> **cPanel**
369+
>> cPanel
373370
>>
374-
>> Step 1: Access the WHM IP management section
371+
>> **Step 1: Access the WHM IP management section**
375372
>>
376373
>> In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
377374
>>
378375
>> ![Add new IP](images/cpanel-alma-1.png){.thumbnail}
379376
>>
380-
>> Step 2: Add the Additional IP information
377+
>> **Step 2: Add the Additional IP information**
381378
>>
382379
>> Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
383380
>>
@@ -390,24 +387,24 @@ In the examples below, we will use the `nano` text editor. With some operating s
390387
>> > Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
391388
>> >
392389
>>
393-
>> Step 3: Check the current IP configuration
390+
>> **Step 3: Check the current IP configuration**
394391
>>
395392
>> Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
396393
>>
397394
>> ![check configured IP](images/cpanel-alma-3.png){.thumbnail}
398395
>>
399-
> Plesk
400-
>> **Plesk**
396+
> **Plesk**
397+
>> Plesk
401398
>>
402-
>> Step 1: Access the Plesk IP management section
399+
>> **Step 1: Access the Plesk IP management section**
403400
>>
404401
>> In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
405402
>>
406403
>> ![acces to the ip addresses management](images/pleskip1.png){.thumbnail}
407404
>>
408405
>> Click on `IP Addresses`{.action} under **Tools & Resources**.
409406
>>
410-
>> Step 2: Add the additional IP information
407+
>> **Step 2: Add the additional IP information**
411408
>>
412409
>> In this section, click on the button `Add IP Address`{.action}.
413410
>>
@@ -417,16 +414,16 @@ In the examples below, we will use the `nano` text editor. With some operating s
417414
>>
418415
>> ![add ip information](images/Plesk-additional-ip.png){.thumbnail}
419416
>>
420-
>> Step 3: Check the current IP configuration
417+
>> **Step 3: Check the current IP configuration**
421418
>>
422419
>> Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
423420
>>
424421
>> ![current IP configuration](images/plesk-final-configuration.png){.thumbnail}
425422
>>
426-
> Windows Servers
427-
>> **Windows Servers**
423+
> **Windows Servers**
424+
>> Windows Servers
428425
>>
429-
>> Step 1: Verify the network configuration
426+
>> **Step 1: Verify the network configuration**
430427
>>
431428
>> Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
432429
>>
@@ -450,7 +447,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
450447
>> Default Gateway . . . . . . . . . : 192.0.2.1
451448
>> ```
452449
>>
453-
>> Step 2: Change the IPv4 Properties
450+
>> **Step 2: Change the IPv4 Properties**
454451
>>
455452
>> Now you need to change the IP properties to a static configuration.
456453
>>
@@ -485,7 +482,7 @@ In the examples below, we will use the `nano` text editor. With some operating s
485482
>>
486483
>> You will lose the connection to the server for a few seconds.
487484
>>
488-
>> Step 4: Check the new network configuration
485+
>> **Step 4: Check the new network configuration**
489486
>>
490487
>> Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
491488
>>

0 commit comments

Comments
 (0)