multiple_ip_addresses_on_single_interface
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
multiple_ip_addresses_on_single_interface [2023/11/13 17:21] – [The Better Method] walkeradmin | multiple_ip_addresses_on_single_interface [2023/11/13 17:26] (current) – [The Better Method] walkeradmin | ||
---|---|---|---|
Line 180: | Line 180: | ||
</ | </ | ||
Play close attention to the **DEVICE** setting, you must set the name to match the interface file name (so for file <color # | Play close attention to the **DEVICE** setting, you must set the name to match the interface file name (so for file <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 | ||
+ | \\ | ||
+ | \\ | ||
+ | If we perform an ip route: | ||
+ | \\ | ||
+ | < | ||
+ | default via 192.168.1.1 dev eno1 proto static metric 101 | ||
+ | 10.32.13.0/ | ||
+ | 130.1.0.0/ | ||
+ | 192.168.1.0/ | ||
+ | 11.0.0.0/16 dev eno2 proto kernel scope link src 11.0.223.2 metric 102 | ||
+ | </ | ||
+ | We can see that the default route is still via **eno1**, and that the other alias IP Addresses are still going via **eno1**. | ||
\\ | \\ | ||
\\ | \\ | ||
+ | |||
+ | |||
multiple_ip_addresses_on_single_interface.1699896085.txt.gz · Last modified: 2023/11/13 17:21 by walkeradmin