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
docker_notes:vm-container [2025-01-02 Thu wk01 18:02] – [Setup VM] baumkpdocker_notes:vm-container [2025-12-23 Tue wk52 10:48] (current) – [KVM versus Proxmox] baumkp
Line 10: Line 10:
 I may try Proxmox in the future, there is currently no compelling reason for me to do so at this time. I may try Proxmox in the future, there is currently no compelling reason for me to do so at this time.
  
-As my old router became too unreliable to use circa November 2024, I have ordered a replacement.  ++My old router tl;dr|My previous router basic failed to operated reliably circa October 2024 had an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but still functions well as a sub gb/s router.  I also run a VM with Docker containers for a backup Bind9 DNS and backup Kea DHCP on this machine.  As my current (WAN) internet speed is about 265Mb/s down and 23Mb/s up this router is still suitable for purpose. I suspect it will not be limiting until the available WAN speeds are above 1000Mbps. <fs small>(I am currently 2023/2024 eyeing an Intel i5-1335U or N305 as a possible replacement, this is much fast overall and should easily handle multi Gb/s internet traffic, as well as more complex resource intensive Docker instances.)</fs>  Sadly the N3700 AS2400 BMS seem to be unreliable now. I can only login to the BMS after a long shutdown and the machine often fails to reboot reliably.  Due to the age of the hardware it is not worth the cost to repair.  I will need to get a replacement.+++As my old router became too unreliable to use circa November 2024, I have replaced.  ++My old router tl;dr|My previous router basic failed to operated reliably circa October 2024 had an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but did function well as a sub gb/s router.  I also run a VM with Docker containers for a backup Bind9 DNS and backup Kea DHCP on this machine.  As my current (WAN) internet speed is about 920Mb/s down and 90Mb/s up this router is still suitable for purpose. I suspect it will not be limiting until the available WAN speeds are above 1000Mbps. I replaced the router early 2025 with an Intel N305, this is much faster overall and can easily handle multi Gb/s internet traffic, as well as more complex resource intensive Docker instances.)++ 
 + 
 +My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 10Gb/s PCIe card.  My router as of 2025-01 is a i3-305 based machine, with modern 2x 2.5GB/s NICs and 2 x 10GB/s NICs, all RJ45 type with 10GB/S NICs able to operate reliably and low power at all main speeds down to 10MB/s.  I also still operate an older Intel Atom C2750 as a back-up server. This gets started by the main server once a week to run a Restic back-up with a Python script I wrote. 
 + 
 +My main switch is a XikeStor SKS8300-12E2T2X.  This has 12x 2.5Gb/s RJ45 NICs, 2x 10Gb/s RJ45 NICs and 2x 10GB/s SFP NICS.  This allows me to connect my main switch and servers via 10GB/s networking. With the bulk of the other NICS rated up to 2.5Gb/s.  My main Atom C3750 server also has 4x 1Gb/s NICs.  I have 2 wireless access points Netgear WAX206 with upstream ethernet connections to the main switch operating at 2.5Gb/s and each with 4x 1Gb/s downstream ethernet connections available.  The Netgear WAX206 wireless access points are Wifi 6 rated which is sufficient for my current needs. I run OpenWRT firmware on these wireless access points as Netgear stopped supporting this hardware after only 3-4 years.  Suitable Wifi7 routers are still too expensive as of the writing (2025-12) to merit replacing the current access points.  At the moment these Wifi 6 access points connected via 2.5Gbe ethernet provide adequate performance, such that the cost to upgrade to Wifi 7 is not merited. One of the Wifi Access I use (in my study) requires additional Ethernet connections for printer and IPMI connectivity.  If I upgraded to a Wifi 7 access point at a minimum I would require a 10Gbe upstream connection with a 2.5Gbe and 2 x 1GBE downstream connection, preferable 10GBe upstream, 1x 10GBE and 2x2.5Gbe downstream, e.g TP-Link Archer BE800 or BE550Pro.
  
-My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 2.5Gb/s PCIe card.  ++tl;dr|I have not been able to find a good replacement for this machine at this time.  It was designed as a server, again an i5-1335U is in many ways superior, CPU cores and threads, CPU and memory speed and bandwidth, however memory is not ECC and memory is limited to 64GB, neither of which is probably a problem for me, as I am currently only using 32GB. Power consumption is similar. The biggest problem is that I have not been able to date find an i5-1335U motherboard with 4+ SATA ports and PCIE expansion slot, most are laptop boards, router boards or industrial embedded type boards that do not have the functionality that I am after.++  I also still operate an older Intel Atom C2750 as a back-up server. This gets started by the main server once a week to run a Restic back-up with a Python script I wrote. 
  
  
Line 33: Line 36:
       * ''/etc/network/interfaces''        * ''/etc/network/interfaces'' 
 ++++source /etc/network/interfaces.d/*| ++++source /etc/network/interfaces.d/*|
-<code bash># The loopback network interface+<code bash interfaces># The loopback network interface
 auto lo auto lo
 iface lo inet loopback iface lo inet loopback
Line 41: Line 44:
 #iface enp1s0 inet dhcp #iface enp1s0 inet dhcp
  
-auto br0 +auto enp1s0 
-iface br0 inet static +iface enp1s0 inet static
-  bridge_ports enp1s0+
   address 192.168.1.2/24   address 192.168.1.2/24
   gateway 192.168.1.1         #Do not use on a router   gateway 192.168.1.1         #Do not use on a router
-  dns-nameservers 192.168.1.14 192.168.1.2  #Your LAN DNS server(s) +  dns-nameservers 192.168.1.14 192.168.1.2  #Your LAN DNS server(s)</code>
-  bridge_stp off  # disable Spanning Tree Protocol </code> +
 ++++ ++++
 +
 +Note that Docker does not need to operate on a machine with bridge network, which affords some benefits with operating a KVM.
 ====Reference==== ====Reference====
   *[[https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm|How to use bridged networking with libvirt and KVM]]   *[[https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm|How to use bridged networking with libvirt and KVM]]