{"id":3423,"date":"2024-07-15T10:00:07","date_gmt":"2024-07-15T10:00:07","guid":{"rendered":"https:\/\/draculaservers.com\/tutorials\/?p=3423"},"modified":"2024-08-03T09:47:14","modified_gmt":"2024-08-03T09:47:14","slug":"multiple-networkmanager-connection-profiles-linux","status":"publish","type":"post","link":"https:\/\/draculaservers.com\/tutorials\/multiple-networkmanager-connection-profiles-linux\/","title":{"rendered":"Create Multiple NetworkManager Connection Profiles for the Same Network Interface on Linux"},"content":{"rendered":"
\n

If you have a single network interface on your Linux system that you want to use with different IP configurations for various purposes, NetworkManager makes this process simple. This article will guide you on how to configure multiple NetworkManager connection profiles for the same network interface on Linux and how to switch between them when needed.<\/p>\n\n<\/div>\n

\n

Finding the Current IP Addressing Information of the Network Interface on Linux<\/h2>\n<\/div>\n
\n

Before creating multiple NetworkManager connection profiles, it\u2019s useful to know the current IP addressing information of the network interface. This information helps in setting static IP addresses, DHCP configurations, and DNS server settings for different profiles.<\/p>\n<\/div>\n

\n

To find the name of the network interface, run:<\/p>\n<\/div>\n

\n
$ sudo<\/span> nmcli device\r\n<\/code><\/pre>\n<\/div>\n
\n
For instance, if the network interface name is\u00a0ens160<\/code>\u00a0and the active profile is\u00a0Wired connection 1<\/code>, take note of these details.<\/p>\n<\/div>\n
\n
To find the current IP configuration of\u00a0ens160<\/code>, use:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli -f GENERAL.DEVICE,GENERAL.CONNECTION,IP4.ADDRESS,IP4.GATEWAY,IP4.DNS device show ens160\r\n<\/code><\/pre>\n<\/div>\n
\n
You\u2019ll see information like IP address, subnet mask, gateway, and DNS server addresses.<\/p>\n<\/div>\n
\n
Creating Multiple NetworkManager Connection Profiles Using Nmcli<\/h2>\n<\/div>\n
\n
You can create a new NetworkManager connection profile by cloning an existing one and modifying the necessary parameters.<\/p>\n<\/div>\n
\n
To clone an existing profile (Wired connection 1<\/code>) and create a new profile (FixedLAN1<\/code>), run:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection clone \"Wired connection 1\"<\/span> \"FixedLAN1\"<\/span>\r\n<\/code><\/pre>\n<\/div>\n
\n
To set a static IP for\u00a0FixedLAN1<\/code>, modify the profile:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection modify \"FixedLAN1\"<\/span> ipv4.method manual ipv4.addresses 192.168.1.10\/24 ipv4.gateway 192.168.1.2 ipv4.dns 192.168.1.2 connection.autoconnect no\r\n<\/code><\/pre>\n<\/div>\n
\n
To create another profile (FixedLAN2<\/code>) with a different static IP:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection add con-name \"FixedLAN2\"<\/span> ifname ens160 type<\/span> ethernet autoconnect no ipv4.method manual ipv4.addresses 192.168.1.20\/24 ipv4.gateway 192.168.1.2 ipv4.dns 192.168.1.2\r\n<\/code><\/pre>\n<\/div>\n
\n
For a DHCP profile (DynamicLAN<\/code>):<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection add con-name \"DynamicLAN\"<\/span> ifname ens160 type<\/span> ethernet autoconnect no ipv4.method auto\r\n<\/code><\/pre>\n<\/div>\n
\n
Switching Between NetworkManager Connection Profiles Using Nmcli<\/h2>\n<\/div>\n
\n
To switch between profiles, use the\u00a0nmcli connection up<\/code>\u00a0command.<\/p>\n<\/div>\n
\n
To activate\u00a0FixedLAN2<\/code>:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection up \"FixedLAN2\"<\/span>\r\n<\/code><\/pre>\n<\/div>\n
\n
To verify, check the connection status and IP configuration:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection\r\n$ ip a\r\n<\/code><\/pre>\n<\/div>\n
\n
You can similarly activate\u00a0FixedLAN1<\/code>\u00a0and\u00a0DynamicLAN<\/code>:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection up \"FixedLAN1\"<\/span>\r\n$ sudo<\/span> nmcli connection up \"DynamicLAN\"<\/span>\r\n<\/code><\/pre>\n<\/div>\n
\n
Automatically Activating a NetworkManager Connection Profile Using Nmcli<\/h2>\n<\/div>\n
\n
To set a profile to auto-connect at boot, modify its autoconnect property.<\/p>\n<\/div>\n
\n
For\u00a0FixedLAN1<\/code>:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection modify \"FixedLAN1\"<\/span> autoconnect yes<\/span>\r\n$ sudo<\/span> nmcli connection modify \"FixedLAN2\"<\/span> autoconnect no\r\n$ sudo<\/span> nmcli connection modify \"DynamicLAN\"<\/span> autoconnect no\r\n<\/code><\/pre>\n<\/div>\n
\n
To enable autoconnect for\u00a0DynamicLAN<\/code>:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection modify \"DynamicLAN\"<\/span> autoconnect yes<\/span>\r\n$ sudo<\/span> nmcli connection modify \"FixedLAN1\"<\/span> autoconnect no\r\n$ sudo<\/span> nmcli connection modify \"FixedLAN2\"<\/span> autoconnect no\r\n<\/code><\/pre>\n<\/div>\n
\n
After rebooting, the specified profile should be active:<\/p>\n<\/div>\n
\n
$ sudo<\/span> nmcli connection\r\n$ ip a\r\n<\/code><\/pre>\n<\/div>\n
\n
Managing Multiple Profiles Efficiently<\/h2>\n<\/div>\n
\n
When managing multiple profiles, it\u2019s important to keep track of the profiles and their configurations. Use meaningful names for each profile and document their purposes and configurations.<\/p>\n<\/div>\n
\n