Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyone knows the difference between the NAME and the DEVICE when i run 'nmcli connection'?
can i change the NAME to anything I want and it wont effect any best practice? and when I need to stop or restart interfaces do i call them with their NAME or DEVICE?
DEVICE is what is file in the /dev folder, such as eth1 in /dev/eth0.
NAME can be whatever you want. But default for the first automatically configured connection nmcli set NAME to the same value as DEVICE.
I have never really tried to rename an existing connection.
I usually create an new one (pointing to the same device), and delete the old one.
You can also try to nmcli con edit, or nmcli con mod, or even nmcli con clone.
DEVICE is what is file in the /dev folder, such as eth1 in /dev/eth0.
NAME can be whatever you want. But default for the first automatically configured connection nmcli set NAME to the same value as DEVICE.
I have never really tried to rename an existing connection.
I usually create an new one (pointing to the same device), and delete the old one.
You can also try to nmcli con edit, or nmcli con mod, or even nmcli con clone.
thank you for the information. Do you think it is possible to change the device name?
Yes, theoretically it is possible to change the device name.
But for which real purpose? You really rarely need that.
Maybe, if you tell us what problem you are trying to solve, we might be able to propose a more suitable solution.
That said, you should bear in mind that the device names under /dev/devicename are managed by the kernel.
So I would not advise in changing or modifying the way the kernel thought it should have named a device.
But playing with udev rules (I have done it once and long time ago for a USB drive), you can add alias device names for your network interface with names of your choice.
Yes, theoretically it is possible to change the device name.
But for which real purpose? You really rarely need that.
Maybe, if you tell us what problem you are trying to solve, we might be able to propose a more suitable solution.
That said, you should bear in mind that the device names under /dev/devicename are managed by the kernel.
So I would not advise in changing or modifying the way the kernel thought it should have named a device.
But playing with udev rules (I have done it once and long time ago for a USB drive), you can add alias device names for your network interface with names of your choice.
Ok understood. Alias is an option.
Oh its nothing; just an OC problem where in one of your 10 servers didn't get the same device name as the others and we wanted to find a way to fix that without having to reinstall linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.