Managing Networks With nmcli - Revision history

Digimer: /* Configuring a Bond */

2023-12-21T03:20:18Z

Configuring a Bond

← Older revision		Revision as of 03:20, 21 December 2023
Line 244:		Line 244:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection modify 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ipv4.method disabled		nmcli connection modify 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ipv4.method disabled
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			<no output>
			</syntaxhighlight>
			<syntaxhighlight lang="bash">
			nmcli connection modify 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ipv6.method disabled
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">

Digimer: /* Configuring a Bond */

2023-12-21T02:57:01Z

Configuring a Bond

← Older revision		Revision as of 02:57, 21 December 2023
Line 198:		Line 198:
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	Connection 'sn1_bond1' (~~8d463d4d~~-~~1e09~~-~~4892~~-~~a192~~-~~1bad4459320c~~) successfully added.		Connection 'sn1_bond1' (64da1139-990b-48da-848a-decad8cafa3b) successfully added.
	</syntaxhighlight>		</syntaxhighlight>

Line 207:		Line 207:
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	NAME UUID TYPE DEVICE		NAME UUID TYPE DEVICE
	enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ethernet sn1_link1		sn1_bond1 64da1139-990b-48da-848a-decad8cafa3b bond sn1_bond1
	enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 ethernet sn1_link2		enp1s0 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ethernet ifn1_link1
	enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b ethernet bcn1_link1		enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ethernet ifn1_link2
	enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd ethernet bcn1_link2		lo 97cc6108-7782-48da-a40d-922f69b47229 loopback lo
	~~sn1_bond1 8d463d4d-1e09-4892-a192-1bad4459320c bond sn1_bond1~~		enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ethernet sn1_link1
	~~enp1s0 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ethernet ifn1_link1~~		enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 ethernet sn1_link2
	~~enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ethernet ifn1_link2~~		enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b ethernet bcn1_link1
	~~lo e5f527b2-03d7-492d-982e-45ae4779c2e5 loopback lo~~		enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd ethernet bcn1_link2
	</syntaxhighlight>		</syntaxhighlight>

Line 249:		Line 249:
	</syntaxhighlight>		</syntaxhighlight>

	Now add the interface to the bond.		Now add the <span class="code">sn1_link1</span> interface to the bond (using it's UUID);

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection ~~add type ethernet con~~-~~name sn1_bond1_port1 ifname sn1_link1~~ master sn1_bond1		nmcli connection modify 0c601a39-65c0-3c6b-a064-a7df8d2d4329 master sn1_bond1
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	~~Connection 'sn1_bond1_port1' (f11e76d0-72a6-46e6-928f-5d654128d753) successfully added.~~		<no output>
	</syntaxhighlight>		</syntaxhighlight>

	~~We can confirm this worked with nmcli~~;		And bring the <span class="code">sn1_link1</span> connection down and back up;

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection ~~show~~		nmcli connection down 0c601a39-65c0-3c6b-a064-a7df8d2d4329
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Connection 'enp10s0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/12)
			</syntaxhighlight>
			<syntaxhighlight lang="bash">
			nmcli connection up 0c601a39-65c0-3c6b-a064-a7df8d2d4329
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	~~NAME UUID TYPE DEVICE~~		Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)
	~~sn1_bond1 dc6bc3c4~~-~~a3b6-458f-875b-630500bc050f bond sn1_bond1~~
	~~enp1s0 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ethernet ifn1_link1~~
	~~enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ethernet ifn1_link2~~
	~~lo e5f527b2-03d7-492d-982e-45ae4779c2e5 loopback lo~~
	~~sn1_bond1_port1 f11e76d0-72a6-46e6-928f-5d654128d753 ethernet sn1_link1~~
	~~enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ethernet --~~
	~~enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 ethernet --~~
	~~enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b ethernet --~~
	~~enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd ethernet --~~
	</syntaxhighlight>		</syntaxhighlight>

	~~Now lets~~ add the ~~second interface.~~		And now add, down and up the <span class="code">sn1_link2</span> link;

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection modify 77a64113-ea2a-3644-8ad4-2c30d8196f09 ~~ipv4.method disabled~~		nmcli connection modify 77a64113-ea2a-3644-8ad4-2c30d8196f09 master sn1_bond1
	~~</syntaxhighlight>~~
	~~<syntaxhighlight lang="text">~~
	~~<no output>~~
	</syntaxhighlight>		</syntaxhighlight>

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection ~~add type ethernet con~~-~~name sn1_bond1_port2 ifname sn1_link2 master sn1_bond1~~		nmcli connection down 77a64113-ea2a-3644-8ad4-2c30d8196f09
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	Connection '~~sn1_bond1_port2~~' (~~1f851704~~-~~8ba5-49fa-870a-f781781776ea~~) ~~successfully added.~~		Connection 'enp11s0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/21)
	</syntaxhighlight>		</syntaxhighlight>

	~~Again, lets confirm;~~

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	nmcli connection ~~show~~		nmcli connection up 77a64113-ea2a-3644-8ad4-2c30d8196f09
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	~~NAME UUID TYPE DEVICE~~		Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/24)
	~~enp1s0 80d3aaf2~~-~~0ed8-3e32-977c-e3c63c39581f ethernet ifn1_link1~~
	~~enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ethernet ifn1_link2~~
	~~lo e5f527b2-03d7-492d-982e-45ae4779c2e5 loopback lo~~
	~~enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ethernet --~~
	~~enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 ethernet --~~
	~~enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b ethernet --~~
	~~enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd ethernet --~~
	~~sn1_bond1 dc6bc3c4-a3b6-458f-875b-630500bc050f bond --~~
	~~sn1_bond1_port1 f11e76d0-72a6-46e6-928f-5d654128d753 ethernet --~~
	~~sn1_bond1_port2 1f851704-8ba5-49fa-870a-f781781776ea ethernet --~~
	</syntaxhighlight>		</syntaxhighlight>

Digimer: /* Configuring a Bond */

2023-12-20T04:06:38Z

Configuring a Bond

@@ Line 239: / Line 239: @@
 {{note|1=Red Hat as a company, and Linux as a community, are working to remove problematic language such as "master" and "slave". This is an ongoing process, and until it's finished, some of this legacy language is still used, as we'll see now.}}
 <syntaxhighlight lang="bash">
@@ Line 266: / Line 277: @@
 Now lets add the second interface.
 <syntaxhighlight lang="bash">

Digimer: /* Setting No IP on an Interface */

2023-12-20T03:57:54Z

Setting No IP on an Interface

← Older revision		Revision as of 03:57, 20 December 2023
Line 514:		Line 514:
	== Setting No IP on an Interface ==		== Setting No IP on an Interface ==

	To have an interface come up, but to set or request an IP address, you can set it to "<span class="code">...ipv4.~~mathod~~ disabled</span>".		To have an interface come up, but to set or request an IP address, you can set it to "<span class="code">...ipv4.method disabled</span>".

Digimer: /* Assigning IP Addresses */

2023-12-16T23:46:44Z

Assigning IP Addresses

← Older revision		Revision as of 23:46, 16 December 2023
Line 509:		Line 509:

	== Assigning an IP Address to a Bridge ==		== Assigning an IP Address to a Bridge ==



			== Setting No IP on an Interface ==

			To have an interface come up, but to set or request an IP address, you can set it to "<span class="code">...ipv4.mathod disabled</span>".

Digimer: /* Assigning an IP Address to an Interface */

2023-12-16T02:36:58Z

Assigning an IP Address to an Interface

← Older revision		Revision as of 02:36, 16 December 2023
Line 391:		Line 391:

	== Assigning an IP Address to an Interface ==		== Assigning an IP Address to an Interface ==

			In this example, we're assign a static IP address to the two interfaces;
			* <span class="code">192.168.4.1/255.255.0.0</span> to the network interface <span class="code">ifn1_link1</span>
			* <span class="code">10.201.4.1/255.255.0.0</span> to the network interface <span class="code">bcn1_link1</span>

			We will also create the default gateway <span class="code">192.168.255.254</span> and the two DNS servers <span class="code">8.8.8.8</span> and <span class="code">8.8.4.4</span>.

			Before we start, note the UUIDs for the two interfaces we'll be working with;

			<syntaxhighlight lang="bash">
			nmcli --fields NAME,UUID,DEVICE,ACTIVE,STATE connection
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			NAME UUID DEVICE ACTIVE STATE
			enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 sn1_link1 yes activating
			enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 sn1_link2 yes activating
			enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b bcn1_link1 yes activating
			enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd bcn1_link2 yes activating
			enp1s0 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ifn1_link1 yes activated
			enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ifn1_link2 yes activated
			lo 1964aad3-d943-4c44-b892-6e84f06de3bc lo yes activated
			</syntaxhighlight>

			So in this example, <span class="code">ifn1_link1</span> has the UUID <span class="code">80d3aaf2-0ed8-3e32-977c-e3c63c39581f</span> and <span class="code">bcn1_link1</span> has the UUID <span class="code">61cbf1bc-aab7-3b78-8d81-48a92409882b</span>.

			{{note\|1=If an interface is not active, the <span class="code">DEVICE</span> name will not be shown. If this is the case,

			First, we'll do <span class="code">ifn1_link1</span>, which currently has a [[DHCP]] assigned IP address.

			<syntaxhighlight lang="bash">
			nmcli connection show 80d3aaf2-0ed8-3e32-977c-e3c63c39581f \| grep IP4
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			IP4.ADDRESS[1]: 192.168.6.142/16
			IP4.GATEWAY: 192.168.255.254
			IP4.ROUTE[1]: dst = 192.168.0.0/16, nh = 0.0.0.0, mt = 102
			IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.255.254, mt = 102
			IP4.DNS[1]: 192.168.255.254
			IP4.DOMAIN[1]: ifn1_bridge1
			</syntaxhighlight>

			This doesn't show how the IP was set (a limitation on the grep). We can check if it's DHCP by seeing how <span class="code">ipv4.method</span> is set. if it's DHCP, it will be <span class="code">auto</span>.

			<syntaxhighlight lang="bash">
			nmcli --fields ipv4.method connection show 80d3aaf2-0ed8-3e32-977c-e3c63c39581f
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			ipv4.method: auto
			</syntaxhighlight>

			{{note\|1=The <span class="code">ipv4.addresses</span> must specify the subnet mask using [[CIDR]] notation.}}

			So let's switch to static configuration. This is the interface used for routing to the Internet, so we'll define the default gateway IP address, and the DNS IPs.

			<syntaxhighlight lang="bash">
			nmcli connection modify 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ipv4.method manual ipv4.addresses 192.168.4.1/16 ipv4.gateway 192.168.255.254 ipv4.dns 8.8.8.8,8.8.4.4 ipv4.dns-search alteeve.com
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			<no output>
			</syntaxhighlight>

			If you use <span class="code">nmcli connection show 80d3aaf2-0ed8-3e32-977c-e3c63c39581f</span>, you'll see the new configuration. However, the new configuration is not yet active. To have the new config take effect, <span class="code">down</span> and <span class="code">up</span> the interface.

			<syntaxhighlight lang="bash">
			nmcli connection down 80d3aaf2-0ed8-3e32-977c-e3c63c39581f
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Connection 'enp1s0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/292)
			</syntaxhighlight>

			And bring it back up.

			<syntaxhighlight lang="bash">
			nmcli connection up 80d3aaf2-0ed8-3e32-977c-e3c63c39581f
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/293)
			</syntaxhighlight>

			We can verify that the new IP is now in use with <span class="code">ip addr list ifn1_link1</span>.

			<syntaxhighlight lang="bash">
			ip addr list ifn1_link1
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			2: ifn1_link1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
			link/ether 52:54:00:d3:19:cc brd ff:ff:ff:ff:ff:ff
			altname enp1s0
			inet 192.168.4.1/16 brd 192.168.255.255 scope global noprefixroute ifn1_link1
			valid_lft forever preferred_lft forever
			inet6 fe80::5054:ff:fed3:19cc/64 scope link noprefixroute
			valid_lft forever preferred_lft forever
			</syntaxhighlight>

			Voila!

			<span class="code"></span>
			<syntaxhighlight lang="bash">
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			</syntaxhighlight>


	<span class="code"></span>		<span class="code"></span>

Digimer: /* Creating a Bridge Interface */

2023-12-15T22:36:36Z

Creating a Bridge Interface

← Older revision		Revision as of 22:36, 15 December 2023
Line 385:		Line 385:

	Done!		Done!

			= Assigning IP Addresses =

			In this example, we're going to assign IP addresses to various devices.

			== Assigning an IP Address to an Interface ==

			<span class="code"></span>
			<syntaxhighlight lang="bash">
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			</syntaxhighlight>

			== Assigning an IP Address to a Bond ==

			<span class="code"></span>
			<syntaxhighlight lang="bash">
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			</syntaxhighlight>

			== Assigning an IP Address to a Bridge ==

Digimer: /* Creating a Bridge Interface */

2023-12-15T22:33:19Z

Creating a Bridge Interface

← Older revision		Revision as of 22:33, 15 December 2023
Line 331:		Line 331:
	= Creating a Bridge Interface =		= Creating a Bridge Interface =

	A bridge is, basically, a dumb layer-2 ethernet switch. It is used to connect the network interfaces in virtual machines to the outside world, via a physical network interface.		A bridge is, basically, a dumb layer-2 ethernet switch. It is used to connect the network interfaces in virtual machines to the outside world, via a physical network interface. The bridge itself is called the "controller", and devices connected to it (typically the <span class="code">vnetX</span> devices connecting a VM's interface to the bridge) are called "ports".

			We built on the last tutorial to creat the bonded interface <span class="code">bcn1_bond1</span>. We'll now create the bridge <span class="code">bcn1_bridge1</span>, and use the bond as the (redundant) connection to the outside world.

			<syntaxhighlight lang="bash">
			nmcli connection add type bridge con-name bcn1_bridge1 ifname bcn1_bridge1
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			Connection 'bcn1_bridge1' (07829ca1-e028-40eb-b3b0-346f46a2bd49) successfully added.
			</syntaxhighlight>

			Indeed, we can now see this new bridge.

			<syntaxhighlight lang="bash">
			nmcli connection show
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			NAME UUID TYPE DEVICE
			bcn1_bridge1 07829ca1-e028-40eb-b3b0-346f46a2bd49 bridge bcn1_bridge1
			enp8s0 61cbf1bc-aab7-3b78-8d81-48a92409882b ethernet bcn1_link1
			enp9s0 7f45a5a2-2ba0-37e0-a38d-2a9da80653fd ethernet bcn1_link2
			sn1_bond1 dc6bc3c4-a3b6-458f-875b-630500bc050f bond sn1_bond1
			enp1s0 80d3aaf2-0ed8-3e32-977c-e3c63c39581f ethernet ifn1_link1
			enp7s0 8248651b-06ce-32e1-a9b4-67a9aa578ab6 ethernet ifn1_link2
			lo e5f527b2-03d7-492d-982e-45ae4779c2e5 loopback lo
			sn1_bond1_port1 f11e76d0-72a6-46e6-928f-5d654128d753 ethernet sn1_link1
			sn1_bond1_port2 1f851704-8ba5-49fa-870a-f781781776ea ethernet sn1_link2
			bcn1_bond1 9c13f3ee-0f64-4185-895b-5682797a73a3 bond --
			bcn1_bond1_port1 be724752-9dca-466f-a26c-84ce77af41d6 ethernet --
			bcn1_bond1_port2 912cfa55-7cd6-41f3-9004-7c0f137af84c ethernet --
			enp10s0 0c601a39-65c0-3c6b-a064-a7df8d2d4329 ethernet --
			enp11s0 77a64113-ea2a-3644-8ad4-2c30d8196f09 ethernet --
			</syntaxhighlight>

			Now connect the

			<syntaxhighlight lang="bash">
			nmcli connection modify bcn1_bond1 master bcn1_bridge1
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			<no output from this command>
			</syntaxhighlight>

			To verify that the bond is now connected to the bridge, you can check the <span class="code">connection.master</span> and <span class="code">connection.slave-type</span> fields;

			<syntaxhighlight lang="bash">
			nmcli --fields connection.master,connection.slave-type connection show bcn1_bond1
			</syntaxhighlight>
			<syntaxhighlight lang="text">
			connection.master: bcn1_bridge1
			connection.slave-type: bridge
			</syntaxhighlight>

			Done!

Digimer: /* Configuring a Bond */

2023-12-15T21:25:52Z

Configuring a Bond

Show changes

Digimer at 17:33, 15 December 2023

2023-12-15T17:33:31Z

← Older revision		Revision as of 17:33, 15 December 2023
Line 170:		Line 170:
	Voila! The device has been renamed!		Voila! The device has been renamed!

	~~<syntaxhighlight lang~~=~~"bash">~~		= Configuring a Bond =
	~~</syntaxhighlight>~~
	~~<syntaxhighlight lang~~=~~"text">~~
	~~</syntaxhighlight>~~

			A bond is a pairing of two or more interfaces to provide increased bandwidth, increased reliability, or both.

			In the [[Anvil!]] platform, <span class="code">active-passive</span>, aka <span class="code">mode=1</span>, is the mode we will use. It is the only bond type that does NOT increase bandwidth, but it is the one that fails over the fastest.

			== Configuring an Active-Passive Bond ==

	<span class="code"></span>		<span class="code"></span>