Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
home_server:home_server_setup:network_setup [2021-12-25 Sat wk51 09:10] – [Full Network Setup] baumkphome_server:home_server_setup:network_setup [2023-10-29 Sun wk43 12:56] (current) – [Full Network Setup] baumkp
Line 1: Line 1:
-{{tag>network interface netplan nic setup loopback eth ethernet bridge bond networkd linux ubuntu setup command}}+{{tag>network interface netplan nic setup loopback eth ethernet bridge bond networkd linux debian setup command}}
 =====Network Setup===== =====Network Setup=====
  
 The home server I have has 4 Intel Gigabit NICs. The past couple of years I have only been using 1 NIC to a main 24 port gigabit switch. This is described in the Basic Network Setup below. The newer home server has 5 drive, 2 SSD system drive, 2 larger data storage drives and 1 drive used as a parity drive for off line raid for the data storage drives. For most the time a single NIC will provide sufficient bandwidth between the server and switch. However there exists server capacity to saturate bandwidth of a single gigabit NIC. To increase effective bandwidth there is an option to bond 2 or more NIC together to combine their bandwidth. This is call NIC Bonding. To allow virtual machine NIC access the NIC(s) must be setup in bridge mode. Furthermore bridging NICs can also allow the NICs to act as a switch, obviously where more than one NIC is available. The Full Network Setup section below, describes setting up the system with bonded and bridge NICs. All these described setups were found to operate well. The home server I have has 4 Intel Gigabit NICs. The past couple of years I have only been using 1 NIC to a main 24 port gigabit switch. This is described in the Basic Network Setup below. The newer home server has 5 drive, 2 SSD system drive, 2 larger data storage drives and 1 drive used as a parity drive for off line raid for the data storage drives. For most the time a single NIC will provide sufficient bandwidth between the server and switch. However there exists server capacity to saturate bandwidth of a single gigabit NIC. To increase effective bandwidth there is an option to bond 2 or more NIC together to combine their bandwidth. This is call NIC Bonding. To allow virtual machine NIC access the NIC(s) must be setup in bridge mode. Furthermore bridging NICs can also allow the NICs to act as a switch, obviously where more than one NIC is available. The Full Network Setup section below, describes setting up the system with bonded and bridge NICs. All these described setups were found to operate well.
 +I added a 2.5gbe NIC card to my servers and switch.
  
 Some references are noted below Network Setup Links. Some references are noted below Network Setup Links.
 =====Archived Network Setups===== =====Archived Network Setups=====
  
-++++Old Network Interfaces Setup|+++++Network Interfaces Setup|
 ====Basic Network Setup==== ====Basic Network Setup====
  
Line 148: Line 149:
 Wifi quoted speeds are particularly bogus / optimistic. The quoted speed is usually the best possible speed achievable. Wifi bandwidth is often shared with many simultaneous users, with each n user only often getting at best a 1/n share of bandwidth. There are also latency and interference issues with Wifi that can affect performance. Wired LAN ethernet connection tend to provide more reliable consistent performance. That being said Wifi is convenient and in most, but certainly not all, cases fast enough.++++ Wifi quoted speeds are particularly bogus / optimistic. The quoted speed is usually the best possible speed achievable. Wifi bandwidth is often shared with many simultaneous users, with each n user only often getting at best a 1/n share of bandwidth. There are also latency and interference issues with Wifi that can affect performance. Wired LAN ethernet connection tend to provide more reliable consistent performance. That being said Wifi is convenient and in most, but certainly not all, cases fast enough.++++
 =====Full Network Setup===== =====Full Network Setup=====
-As of 2021 instead of bonding my server I have installed a 2.5Gb/s ethernet card in my mainserver, backup server and main desktop computers. I have purchased a 5 ports 2.5Gb/s switch.  My 2 home home Wifi access points (APs) are connected to the 2.5Gb/s switch too.  I have had these older Wifi APs since 2014, Netgear EX6200/AC1200 and they still serve my home well. They each have 5 x 1Gb/s ethernet ports, for which 1 is used to connect to the upstream switch. As much of my home network equipment is connected by CAT 6 ethernet cable the dual  APs are not very stretched.  I have been luck to avoid the whole Wifi mesh to enable adequate Wifi coverage, which is clearly inferior to the cabled system I have. I researched purchasing upgraded Wifi6 APs, but those with a 2.5Gb/s ethernet port (or better) are still unreasonably expensive. The 5GB/s Ethernet cards and switches are not readily available. The 10Gb/s cards and switches are still much more expensive and consume significantly more power at 10Gb/s connection, meaning operating costs are probably also adversely affected.\\+As of 2021 instead of bonding my server I have installed a 2.5Gb/s ethernet card in my mainserver, and backup server. My current main desktop computer comes with 2.5Gb/s standard. I original purchased a 5 ports 2.5Gb/s switch, but upgraded to an 8 port version.  My 2 home home Wifi 6 access points (APs) are connected to the 2.5Gb/s switch too with 2.5Gb/s Ethernet ports and have 4 x 4 Gb/s ports downstream.  Last year (2022) I upgraded from older Wifi APs since 2014, Netgear EX6200/AC1200. They each have 5 x 1Gb/s ethernet ports, for which 1 is used to connect to the upstream switch. As much of my home network equipment is connected by CAT 6 ethernet cable the dual  APs are not very stretched.  I have been lucky to avoid the whole Wifi mesh to enable adequate Wifi coverage, which is clearly inferior to the cabled system I have. The 5GB/s Ethernet cards and switches are not readily available. The 10Gb/s cards and switches are still much more expensive and consume significantly more power at 10Gb/s connection, meaning operating costs are probably also adversely affected.\\
  
-I have not tested the performance of the 2.5Gb/s ethernet system, in all honesty I have not noticed much difference. This is perhaps not unexpected as my in eternet connection is ~ 30Mb/s down and 12Mb/s up.  My main server primary storage is 3.5" spinning disk with peak performance at best <2Gb/s and sustain and average performance much lower than this. These hard disks are limited to individual speed performance, no interleaving raid to speed thing up.  The operating systems and VMs are on SSDs / NVM with much higher achievable transfer rate and should improved overall system performance, but are not used for normal server storage purposes, hence the speed advantage here are not generally restricted by the network speed.+I have not tested the performance of the 2.5Gb/s ethernet system, in all honesty I have not noticed much difference. This is perhaps not unexpected as my in Ethernet connection is ~ 65Mb/s down and 17Mb/s up.  My main server primary storage is 3.5" spinning disk with peak performance at best <2Gb/s and sustain and average performance much lower than this. These hard disks are limited to individual speed performance, no interleaving raid to speed thing up.  The operating systems and VMs are on SSDs / NVM with much higher achievable transfer rate and should improved overall system performance, but are not used for normal server storage purposes, hence the speed advantage here are not generally restricted by the network speed.
  
 This is the setup for my new server with 4 built in Intel NICs, with Ubuntu 20.04 To reduce performance reduction due to limited Ethernet bandwidth using only one NIC I propose to use 2 NICs in bonded configuration and also use bridging to allow server virtual machine access to the NICs and also use the remaining 2 NICs effectively as a switch. This is the setup for my new server with 4 built in Intel NICs, with Ubuntu 20.04 To reduce performance reduction due to limited Ethernet bandwidth using only one NIC I propose to use 2 NICs in bonded configuration and also use bridging to allow server virtual machine access to the NICs and also use the remaining 2 NICs effectively as a switch.
  
-Ubuntu has for some time defaulted to netplan.io, where as Debian 11 still defaults to the interfaces configuration style.  Use ''sudo apt install netplan.io'' to install netplan on Debian.  <color #fff200>After configuring netplan, move the interfaces file to prevent overlapping configuration, e.g.</color> ''sudo mv /etc/network/interfaces /etc/network/interfaces.old''+Ubuntu has for some time defaulted to netplan.io, where as Debian 11 still defaults to the interfaces configuration style.  Use ''sudo apt install netplan.io'' to install netplan on Debian.  <fc #ff0000>After configuring netplan, move the interfaces file to prevent overlapping configuration, e.g.</fc> ''sudo mv /etc/network/interfaces /etc/network/interfaces.old''
  
 To check available interfaces and names: ''ip link'' To check available interfaces and names: ''ip link''
Line 160: Line 161:
 Netplan does **not** require the bridge utilities to be loaded however these utilities can be used upon the bridge: ''sudo apt install bridge-utils'' Netplan does **not** require the bridge utilities to be loaded however these utilities can be used upon the bridge: ''sudo apt install bridge-utils''
  
-Under netplan the bonded configuration does not need ifenslave utility loaded, as this utilities is dependent upon ifupdown. Do **not** install ''sudo apt install ifenslave''+Under netplan the bonded configuration does not need ifenslave utility loaded, as this utilities is dependent upon ifupdown. <fc #ff0000>Do **not** install</fc> ''sudo apt install ifenslave''
  
 The netplan website with basic information [[https://netplan.io|netplan.io]]. Also another resource is from cloud-init [[https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html#examples|Networking Config Version 2]]. The netplan website with basic information [[https://netplan.io|netplan.io]]. Also another resource is from cloud-init [[https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html#examples|Networking Config Version 2]].
Line 175: Line 176:
  
 Edit the network configuration file: ''/etc/netplan/interfaces.yaml'' as follows: Edit the network configuration file: ''/etc/netplan/interfaces.yaml'' as follows:
-<code>+++++interfaces.yaml| 
 +<code yaml>
 network: network:
   #setup network interfaces   #setup network interfaces
Line 227: Line 229:
   *''sudo netplan try'' To try a new neplan configuration with automatic roll back.   *''sudo netplan try'' To try a new neplan configuration with automatic roll back.
   *''journalctl -u systemd-networkd'' to check the networkd log   *''journalctl -u systemd-networkd'' to check the networkd log
 +++++
 +=====Full VM Network Setup=====
 +Moving back to Debian I am also moving away from netplan back to interfaces.
 +<code>
 +# This file describes the network interfaces available on your system
 +# and how to activate them. For more information, see interfaces(5).
  
-=====Full VM Network Setup 20.04=====+source /etc/network/interfaces.d/* 
 + 
 +# The loopback network interface 
 +auto lo 
 +  iface lo inet loopback 
 + 
 +# The primary network interface 
 +#allow-hotplug enp1s0 
 +#iface enp1s0 inet dhcp 
 + 
 +auto enp1s0 
 +  iface enp1s0 inet static 
 +    address 192.168.1.17/24 
 +    gateway 192.168.1.1 
 +    #dns-nameservers 192.168.1.1 only functional is resolvconf installed 
 + 
 +  iface enp1s0 inet6 static 
 +    address 2001:470:1f2c:10d::17/64 
 +    gateway 2001:470:1f2c:10d::3 
 +</code>
  
 The VM netplan yaml configuration file for static LAN IP address: ''/etc/netplan/network.yaml'' as follows: The VM netplan yaml configuration file for static LAN IP address: ''/etc/netplan/network.yaml'' as follows:
-<code>+<code yaml>
 network: network:
   version: 2   version: 2
Line 245: Line 272:
  
 Create a file br0.xml, ''vim ~/br0.xml'' and add following to it: Create a file br0.xml, ''vim ~/br0.xml'' and add following to it:
-<code>+<code xml>
 <network> <network>
   <name>br0</name>   <name>br0</name>