Differences

This shows you the differences between two versions of the page.

--- multiple_ip_addresses_on_single_interface [2023/11/13 17:05] – [The Better Method] walkeradmin
+++ multiple_ip_addresses_on_single_interface [2023/11/13 17:26] (current) – [The Better Method] walkeradmin
@@ Line 110: / Line 110: @@
 In the directory /etc/sysconfig/network-scripts we can see in this example we two interfaces:
 \\
-\\
+<file>
-    -rw-r--r--. 1 root root 255 Nov 13 17:01 ifcfg-eno1
+-rw-r--r--. 1 root root 255 Nov 13 17:01 ifcfg-eno1
-    -rw-r--r--. 1 root root 232 Nov 13 17:00 ifcfg-eno2
+-rw-r--r--. 1 root root 232 Nov 13 17:00 ifcfg-eno2
-\\
+</file>
-\\
 <color #ed1c24>ifcfg-eno1</color> is the interface that we want to apply multiple IP Addresses to. Firstly we will copy this interface file and edit each file accordingly. When creating the new interface configuration files we will add a number to the end of each file:
 \\
@@ Line 123: / Line 123: @@
 \\
 \\
+Now we have three configuration files for interface <color #ed1c24>eno1</color>.
+\\
+\\
+<color #ed1c24>-rw-r--r--. 1 root root 255 Nov 13 17:01 ifcfg-eno1</color>\\
+<color #00a2e8>-rw-r--r--. 1 root root 255 Nov 13 17:04 ifcfg-eno1:0</color> (Alias 1)\\
+<color #22b14c>-rw-r--r--. 1 root root 255 Nov 13 17:06 ifcfg-eno1:1</color> (Alias 2)\\
+\\
+Each one of these interface files will contain the specific IP Address details that are required, but they will all be associated with a single interface. The <color #ed1c24>ifcfg-eno1</color> file is the main interface configuration file and the other two files <color #00a2e8>ifcfg-eno1:0</color> and <color #22b14c>ifcfg-eno1:1</color> only contain the extra information, these are known as aliases.
+\\
+\\
+**<color #ed1c24>ifcfg-eno1</color>** - In this file we have all of the primary IP Address details:
+\\
+<file>
 TYPE=Ethernet
 PROXY_METHOD=none
@@ Line 146: / Line 151: @@
 IPV6_DISABLED=yes
 IPV6INIT=no
+</file>
+In the next two files, we just enter the additional information:
+\\
+\\
+**<color #00a2e8>ifcfg-eno1:0</color>**
+\\
+<file>
+NAME=eno1
+UUID=ca90417f-9df9-4f34-bae5-77aa6531cc00
+DEVICE=eno1:0
+ONBOOT=yes
+IPADDR=10.32.13.233
+PREFIX=24
+GATEWAY=10.32.13.1
+PREFIX1=24
+</file>
+\\
+**<color #22b14c>ifcfg-eno1:1</color>**
+<file>
+NAME=eno1
+UUID=ca90417f-9df9-4f34-bae5-77aa6531cc00
+DEVICE=eno1:1
+ONBOOT=yes
+IPADDR=137.1.0.100
+PREFIX=24
+GATEWAY=137.1.0.1
+PREFIX1=24
+</file>
+Play close attention to the **DEVICE** setting, you must set the name to match the interface file name (so for file <color #22b14c>ifcfg-eno1:1</color> the **DEVICE** name must be <color #22b14c>eno1:1</color>)
+\\
+\\
+After rebooting the unit, we can now see that there are three IP Addresses on interface ifcfg-eno1.
+\\
+\\
+Using ip -br -c a to show the IP Addresses:
+\\
+\\
+eno1   UP   <color #ed1c24>192.168.1.223</color>/24 1<color #00a2e8>0.32.13.223</color>/24 <color #22b14c>130.1.0.233</color>/24
+\\
+\\
+If we perform an ip route:
+\\
+<file>
+default via 192.168.1.1 dev eno1 proto static metric 101
+.32.13.0/24 dev eno1 proto kernel scope link src 10.32.13.223 metric 101
+.1.0.0/24 dev eno1 proto kernel scope link src 130.1.0.233 metric 101
+.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.223 metric 101
+.0.0.0/16 dev eno2 proto kernel scope link src 11.0.223.2 metric 102
+</file>
+We can see that the default route is still via **eno1**, and that the other alias IP Addresses are still going via **eno1**.
+\\
+\\