


How to change network interface policy on Ubuntu/Debian/RHEL/CentOS/Fedora/Rocky Linux
The predictable network interface name is:
- Stable after restart
- Fixed/consistent even when hardware is added or removed
- Fixed/consistent even after defective/damaged hardware was replaced
- Stateless, no explicit configuration file required
To ensure system security and ease of use of network interfaces, predictable network interface names are crucial. For this reason, mainstream Linux distributions often use "systemd" and "udev" to assign predictable names to the computer's network interfaces. This makes it easier for users to manage and identify individual network interfaces, while also contributing to system stability and performance optimization. In this way, users can configure and manage the network more conveniently, improving overall system operation efficiency and security.
Currently, there are some network interface naming strategies that can be used on Ubuntu, Debian, RHEL, CentOS, Fedora, Rocky Linux and other popular Debian/Ubuntu-based or RPM-based Linux distributions. In this article, we will discuss the network interface naming strategies available in Linux and show you how to switch to the one you want.
Content topic:
- Available network interface removal policies
- Currently used network interface deletion policy
- Change network interface deletion policy
- Check if the new network interface removal policy is being used
- Configure a custom name for the network interface
- in conclusion
Available network interface removal policies
Currently, the available network interface naming strategies are:
- Kernel - In this policy, the kernel does not rename predictable network devices, i.e. lo (loopback interface)
- Database - In this policy, the udev hardware database "hwdb" is used to assign network device names.
- Onboard—In this strategy, the index numbers provided by your computer's BIOS/firmware are used to name the onboard network devices, i.e. eno1, eno2.
- slot—In this strategy, the PCIE hot-plug slot index numbers provided by the computer BIOS/firmware are used to name the network devices, i.e. ens1, ens2.
- Path - In this policy, the network devices are named using the physical location of the hardware, i.e. enp1s0, enp1s2, enp1s0f0, enp1s0f1.
- mac—In this policy, the mac address of the network device is appended to the network interface name, which is enx000c294cd7e8.
Currently used network interface deletion policy
The default network interface naming policy configuration file on most popular Linux distributions is located in the "/usr/lib/systemd/network/99-default.link" path.
You can use the nano text editor to open the default network interface naming policy configuration file "/usr/lib/systemd/network/99—default.link", as shown below:
$sudo nano/usr/lib/systemd/network/www.example.com
The order of network interface naming policies to be used is listed in the "NamePolicy" section [1].
Here, "Hold" has the highest priority. systemd/udev will use the same name over and over again as long as that name has been assigned to the network interface.
It will then try to set the kernel name. If the kernel naming policy fails, database, onboard, slot, and path are used respectively.
You can also set alternative names for network interfaces in the same way using the "AlternativeNamesPolicy" option [2]. Naming policies that are not used for actual network interface naming are used as alternative naming policies, depending on the order set in "AlternativeNamesPolicy".
As you can see, by default, the slot network interface naming policy is used to name the actual network interface, and the path network interface naming policy is used to provide alternative names for network interfaces on Ubuntu 22.04 LTS. Other Linux distributions may use different naming strategies and alternative naming strategies by default.
$IP a
Change network interface deletion policy
To change the network interface naming policy, please use the nano text editor to open the "/usr/lib/systemd/network/99—default.link" configuration file, as shown below:
$sudo nano/usr/lib/systemd/network/www.example.com
Type the desired network interface naming policy in the "NamePolicy" section and the alternative network interface naming policy in the "AlternativeNamePolicy" section.
When finished, press X, then "Y" to save the "99—default.link" file.
For the changes to take effect, please restart your computer as follows:
$sudo reboot
Check if the new network interface removal policy is being used
After the computer boots, run the "ip" command to verify that the network interface name has changed accordingly. As you can see, the Mac network interface naming policy is used to set the real name of the network interface, and the PATH network interface naming policy is used to set the alternative name of the network interface.
$IP a
In this example, we use the path naming strategy for the real name and the mac naming strategy for the alternative name of the network interface.
Configure a custom name for the network interface
In addition to using the predefined network interface naming strategy, you can also set a custom name for your computer's network interface. To learn how to set a custom name for a network interface, read this article.
in conclusion
In this article, we discussed the network interface naming strategies available with modern Linux distributions. We also show you how to use different network interface naming strategies on Ubuntu/Debian, RHEL/Rocky Linux/CentOS/Fedora, and other modern Ubuntu/Debian-based or RPM-based Linux distributions.
The above is the detailed content of How to change network interface policy on Ubuntu/Debian/RHEL/CentOS/Fedora/Rocky Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.
