Jarsky

what network are your wired devices on, and what network are your wireless? I'm assuming that theyre different networks (e.g 192.168.1.x and 192.168.2.x), and theyre unaware of whats on the other network. But yeah as @LIGISTX pointed out, you're running 2 routers; while you can have multiple networks you need routes between them which you probably cant do with this setup. Double NAT shouldnt block traffic between the networks but it will cause performance issues. It will also give you issues forwarding external to things on the Google Nest network. The easiest solution is if you're on fiber, just remove the Telus modem all together and use the Google Nest. But if youre on xDSL or Cable that needs the modem, then bridge the Telus router to the Google Nest Pro preferably. Then your Google Nest will do all the routing and will run DHCP handing out IP's for your entire network, rather than both routers trying to do this.

try open terminal on your Windows machine and run: net use * /delete net use * \\192.168.68.235\library <password> /user:<user> /persistent:yes where <user> and <password> are the credentials from your SMB share.

You are trying the mount point and not the device path? In terminal if you type df -h it should should show you the USB device and where its mounted. You could also run mount -l and search that list for it. If it is the mount path what if you try and browse the directory? e.g cd /media/myusbdrive ls -la

So if we look at this docker we can see what theyre doing. First they download the "jupiter" build of SteamOS and they unzip it to a folder called "steamos_image" #!/bin/sh set -e # these are hardcoded and can be found in ~/.netrc AUTH="jupiter-image-2021:e54fe7f0-756e-46e1-90d2-7843cda0ac01" FILE=$(curl -sS --user $AUTH "https://steamdeck-atomupd.steamos.cloud/updates?product=steamos&release=holo&variant=steamdeck&arch=amd64&version=snapshot&buildid=20220526.1&checkpoint=False&estimated_size=0" | jq -r ".minor.candidates[0].update_path" | sed 's/\.raucb/\.img.zip/') echo "Downloading image $FILE" curl --user $AUTH "https://steamdeck-images.steamos.cloud/$FILE" -o ./steamos.zip unzip ./steamos.zip -d ./steamos_image rm ./steamos.zip Then they build that into a "base image" called "holo-base" which they might use for multiple Docker containers. This is just SteamOS in this case, but building this "base image" is where you might add user permissions, tools, and packages that are common amongst all your Docker containers that use this base. #!/bin/bash set -e LOOP=$(losetup --find --partscan --show ./steamos_image/disk.img) mkdir -p ./steamos mount ${LOOP}p3 ./steamos unmountimg() { umount ./steamos losetup -d $LOOP } trap unmountimg ERR docker build -t ghcr.io/steamdeckhomebrew/holo-base:latest . unmountimg Then they build the actual holo-docker image. They start from scratch which means its empty...theres no base image, then they add the /steamos folder, which is a copy of the above "holo-base" They then remove a whole bunch of packages from the image using pacman (package manager). They then update everything and then they add some packages back to it. FROM scratch as builder ADD ./steamos / ADD ./steamos/usr/share/factory / # not removing libcroco holo-desync holo-keyring holo-pacman holo-pipewire holo-sudo holo-wireplumber elfutils RUN pacman -R --noconfirm accounts-qml-module accountsservice adobe-source-code-pro-fonts adwaita-icon-theme alsa-card-profiles alsa-lib alsa-plugins alsa-topology-conf alsa-ucm-conf alsa-utils amd-ucode anthy aom appstream appstream-glib appstream-qt arch-install-scripts archlinux-appstream-data ark aspell aspell-en assimp atkmm at-spi2-core attica avahi baloo baloo-widgets bash-bats bash-completion bluedevil bluez bluez-libs bluez-plugins bluez-qt bluez-utils bolt boost-libs breeze breeze-grub breeze-gtk breeze-icons btop btrfs-progs bubblewrap cairo cairomm cantarell-fonts caps casync-git cdparanoia cfitsio cifs-utils clang-libs convertlit cpio cpupower dav1d dbus-glib dbus-python dconf desktop-file-utils desync-git discount discover djvulibre dmidecode dmraid dnssec-anchors dolphin dos2unix dosfstools double-conversion dracut drkonqi ebook-tools editorconfig-core-c efibootmgr efivar ell enchant evtest exfat-utils exiv2 f3 fatresize fd ffmpeg fish flac flashrom flatpak fontconfig frameworkintegration freeglut freerdp freetype2 fribidi fuse2 fuse3 fuse-common fwupd gamemode gamescope gcab gdb gdb-common gdk-pixbuf2 geoclue geocode-glib giflib git ghostscript glew glfw-x11 glibmm glib-networking glslang glu gobject-introspection-runtime gpm gptfdisk gpu-trace graphene graphite grub gsettings-desktop-schemas gsm gst-plugins-base gst-plugins-base-libs drm_info gstreamer gtk3 gtkmm3 gtk-update-icon-cache gwenview harfbuzz hicolor-icon-theme hidapi htop hunspell ibus ibus-anthy ibus-hangul ibus-pinyin ibus-table ibus-table-cangjie-lite iniparser iotop iso-codes iw iwd jasper jbig2dec jq json-glib jupiter-dock-updater-bin jupiter-fan-control jupiter-hw-support jupiter-legacy-support kaccounts-integration kactivities kactivities-stats kactivitymanagerd karchive kate kauth kbookmarks kcmutils kcodecs kcolorpicker kcompletion kconfig kconfigwidgets kcontacts kcoreaddons kcrash kdbusaddons kdeclarative kde-cli-tools kdeconnect kdecoration kded kde-gtk-config kdelibs4support kdeplasma-addons kdesu kdialog kdnssd kdsoap kdsoap-ws-discovery-client kdump-steamos kemoticons kfilemetadata kgamma5 kglobalaccel kguiaddons kholidays khotkeys ki18n kiconthemes kidletime kimageannotator kinfocenter kio kio-extras kio-fuse kirigami2 kitemmodels kitemviews kitty-terminfo kjobwidgets kjs kmenuedit knewstuff knotifications knotifyconfig konsole kpackage kparts kpeople kpeoplevcard kpipewire kpmcore kpty kquickcharts krunner kscreen kscreenlocker kservice ksshaskpass ksystemstats ktexteditor ktextwidgets kunitconversion kuserfeedback kwallet kwallet-pam kwayland kwayland-integration kwidgetsaddons kwin kwindowsystem kwrited kxmlgui lame layer-shell-qt lcms2 ldb ldns lib32-alsa-lib lib32-alsa-plugins lib32-brotli lib32-bzip2 lib32-curl lib32-dbus lib32-e2fsprogs lib32-expat lib32-flac lib32-fontconfig lib32-freetype2 lib32-gamemode lib32-gcc-libs lib32-glib2 lib32-glibc lib32-harfbuzz lib32-icu lib32-keyutils lib32-krb5 lib32-libasyncns lib32-libcap lib32-libdrm lib32-libelf lib32-libffi lib32-libgcrypt lib32-libglvnd lib32-libgpg-error lib32-libice lib32-libidn2 lib32-libldap lib32-libnm lib32-libogg lib32-libpciaccess lib32-libpng lib32-libpsl lib32-libpulse lib32-libsm lib32-libsndfile lib32-libssh2 lib32-libtasn1 lib32-libtirpc lib32-libunistring lib32-libunwind lib32-libva lib32-libva-mesa-driver lib32-libvdpau lib32-libvorbis lib32-libx11 lib32-libxau lib32-libxcb lib32-libxcrypt lib32-libxdamage lib32-libxdmcp lib32-libxext lib32-libxfixes lib32-libxi lib32-libxinerama lib32-libxml2 lib32-libxshmfence lib32-libxss lib32-libxtst lib32-libxxf86vm lib32-llvm-libs lib32-lm_sensors lib32-mangohud lib32-mesa lib32-mesa-vdpau lib32-ncurses lib32-nspr lib32-nss lib32-openal lib32-openssl lib32-opus lib32-p11-kit lib32-pam lib32-pcre2 lib32-pipewire lib32-sqlite lib32-systemd lib32-util-linux lib32-vulkan-icd-loader lib32-vulkan-radeon lib32-wayland lib32-xz lib32-zlib lib32-zstd libaccounts-glib libaccounts-qt libaio libass libasyncns libatasmart libavc1394 libblockdev libbluray libbs2b libbsd libbytesize libcanberra libclc libcloudproviders libcolord libcups libdaemon libdatrie libdbusmenu-qt5 libdmtx libedit libepoxy libevdev libfakekey libfdk-aac libfontenc libfreeaptx libftdi libglvnd libgssglue libgudev libgusb libhangul libibus libical libice libiec61883 libimobiledevice libinih libinput libjcat libjpeg-turbo libkdcraw libkexiv2 libkscreen libksysguard libldac libmbim libmd libmfx libmm-glib libmodplug libmtp libndp libnewt libnm libnotify libogg libomxil-bellagio libspectre libdrm ds-inhibit libpciaccess libpgm libpipeline libplist libpng libproxy libpulse libqaccessibilityclient libqalculate libqmi libqrtr-glib libraw libraw1394 librsvg libsamplerate libsigc++ libsm libsndfile libsodium libsoup libsoup3 libsoxr libssh libstemmer libteam libthai libtheora libtiff libtommath libtraceevent libtracefs libunwind liburcu libusb libusbmuxd libutempter libva libva-intel-driver libva-mesa-driver libvdpau libvisual libvorbis libvpx libwacom libwebp libx11 libxau libxaw libxcb libxcomposite libxcursor libxcvt libxdamage libxdmcp libxext libxfixes libxfont2 libxft libxi libxinerama libxkbcommon libxkbcommon-x11 libxkbfile libxmlb libxmu libxpm libxrandr libxrender libxres libxshmfence libxslt libxss libxt libxtst libxv libxxf86vm libyaml libzip lilv linux-firmware-neptune linux-neptune llvm-libs lmdb lm_sensors lsb-release l-smash lsof lua luit lv2 lvm2 lzo maliit-framework maliit-keyboard man-db mangohud md4c mdadm media-player-info mesa mesa-utils mesa-vdpau milou minizip mobile-broadband-provider-info modemmanager modemmanager-qt mtdev nano ndctl nethogs networkmanager networkmanager-qt noise-suppression-for-voice noto-fonts noto-fonts-cjk nspr nss nss-mdns ntfs-3g numactl nvme-cli ocl-icd okular oniguruma openal opencl-mesa opencore-amr openjpeg2 openssh openvpn opus orc ostree oxygen p7zip pango pangomm parted partitionmanager paru pavucontrol pcsclite perf perl-error perl-mailtools perl-timedate phonon-qt5 phonon-qt5-gstreamer pipewire pipewire-alsa pipewire-audio pipewire-jack pipewire-pulse pixman pkcs11-helper plasma-browser-integration plasma-desktop plasma-disks plasma-firewall plasma-framework plasma-integration plasma-meta plasma-nm plasma-pa plasma-systemmonitor plasma-thunderbolt plasma-vault plasma-wayland-protocols plasma-wayland-session plasma-workspace plasma-workspace-wallpapers plymouth polkit polkit-kde-agent polkit-qt5 poppler poppler-qt5 powerdevil powertop ppp presage prison pulseaudio-qt purpose python-aiohttp python-aiosignal python-async-timeout python-attrs python-chardet python-charset-normalizer python-click python-crcmod python-evdev python-frozenlist python-gobject python-hid python-idna python-multidict python-progressbar python-psutil python-pyaml python-pyenchant python-pyinotify python-semantic-version python-systemd python-sysv_ipc python-typing_extensions python-utils python-yaml python-yarl pyzy qca-qt5 qqc2-desktop-style qrencode qt5-base qt5-declarative qt5-feedback qt5-graphicaleffects qt5-location qt5-multimedia qt5-quickcontrols qt5-quickcontrols2 qt5-sensors qt5-speech qt5-svg qt5-tools qt5-translations qt5-wayland qt5-webchannel qt5-webengine qt5-webview qt5-x11extras rauc rav1e re2 ripgrep rsync rtkit rxvt-unicode-terminfo sbc sddm-kcm sddm-wayland sdl2 seatd serd shared-mime-info signond signon-kwallet-extension signon-plugin-oauth2 signon-ui slang smartmontools smbclient snappy socat solid sonnet sord sound-theme-freedesktop source-highlight spectacle speex speexdsp squashfs-tools sratom srt sshfs steamdeck-kde-presets steam-im-modules steam-jupiter-stable steamos-atomupd-client-git steamos-customizations-jupiter steamos-devkit-service steamos-efi strace svt-av1 syndication syntax-highlighting sysfsutils systemd-swap systemsettings taglib talloc tcl tdb tevent thin-provisioning-tools threadweaver tk trace-cmd tracker3 tree tslib ttf-dejavu ttf-hack ttf-twemoji-default udisks2 unrar unzip upower usbmuxd usbutils v4l-utils vid.stab vim vim-runtime vkmark-git vmaf volume_key vpower vulkan-icd-loader vulkan-radeon vulkan-tools wayland wayland-utils webrtc-audio-processing wget wireless-regdb wireless_tools wireplumber wpa_supplicant x264 x265 xbindkeys xbitmaps xcb-proto xcb-util xcb-util-cursor xcb-util-errors xcb-util-image xcb-util-keysyms xcb-util-renderutil xcb-util-wm xdg-dbus-proxy xdg-desktop-portal xdg-desktop-portal-kde xdg-user-dirs xdg-utils xdotool xf86-input-libinput xf86-video-amdgpu xfsprogs xkeyboard-config xorg-fonts-encodings xorgproto xorg-server xorg-server-common xorg-setxkbmap xorg-xauth xorg-xdpyinfo xorg-xhost xorg-xkbcomp xorg-xmessage xorg-xprop xorg-xrandr xorg-xrdb xorg-xset xorg-xsetroot xorg-xwayland-jupiter xorg-xwininfo xterm xvidcore xxhash zenity-light zeromq zimg zip zsh zxing-cpp renderdoc-minimal lib32-renderdoc-minimal lib32-xcb-util-keysyms \ && sed -r -i 's/\[(jupiter|core|extra|community|multilib|holo)\]/\[\1-rel\]/g' /etc/pacman.conf \ && pacman-key --init \ && pacman-key --populate archlinux \ && pacman-key --populate holo \ && pacman -Sy \ # && comm -1 -2 <(pacman -Qeq | sort) <(pacman -Qoq /usr/include/ | sort) | pacman -S --noconfirm - \ && comm -1 -2 <(pacman -Qdq | sort) <(pacman -Qoq /usr/include/ | sort) | pacman -S --noconfirm --asdeps - \ && pacman -S --noconfirm gcc make autoconf automake bison fakeroot flex m4 tpm2-tss \ && yes | pacman -Scc FROM scratch COPY --from=builder / / After this script you will have your "holo-docker" image which in this specific case is just a version of SteamOS Jupiter with a few configuration changes. I presume this docker container is to provide an environment to run and test their homebrews in before installing it to the Steam Deck...

So its a 9240-8i which is a SAS2008 controller, and basically just a different form factor of the 9201-8i (the SAS ports are in the middle instead of the end). When you updated it, did you flash it with the latest P20 firmware? You should be flashing it into IT mode if you want to JBOD anyway. Otherwise in IR mode, each disk is treated as a 1 disk RAID disk. You want to just pass it straight through for JBOD. Here is the P20 IT Firmware If you do want to crossflash it, you need to clear the IR firmware with megarec first, then you can flash the IT firmware. Heres a guide: https://flemmingss.com/how-to-flash-it-mode-firmware-to-hp-lsi-sas-9212-4i-controller-card/ But really not sure why your drive would only show 1TB as these cards have LBA support. I have 16TB drives on a 9211. Is this during the boot it shows them as 931GB (1TB)? In your LSI WebBIOS or in your MegaRAID manager what does it look like? can you share screenshots? If you arent using MSM yet, heres the download for it: https://download.lenovo.com/servers/mig/2017/09/26/17650/lsi-lnvgy_utl_msm_17.05.01.02_windows_x86-64.zip

https://www.ebay.com/itm/162834659601 or https://www.ebay.com/itm/162958581156 and 2x breakout cables: https://www.amazon.com/s?k=SFF8087+to+4x+SFF8482 You can get cheaper 9201/9211's but theyre probably remanufacturerd. ArtOfServer sells only legitimate LSI manufactured cards

Lower transmit powers = less energy = cooler so it extends the life of your AP. You would also want to turn them down if you have more AP's. If theyre up to high and to close to eachother then they wont roam properly and you'll get *stuck* on an AP which at longer distance would give you lower transmission rates than roaming to your closest AP. Higher transmit power also causes more interference with neighbours wifi. Fine in most houses, but horrible in an apartment complex. It looks like thats stand alone though from that app (im guessing thats not the UniFi Controller?), so if you dont have to much around you then you can crank it up. It might not increase performance though. Keep in mind your devices are still limited to the power of their radio

Could give this a try? https://github.com/DerDanilo/proxmox-stuff Update Proxmox. Run a backup Shutdown and install Proxmox to a new drive using ZFS Update to the same level as your existing Proxmox Restore config to the new Proxmox install When all OK, then wipe the old drive and add it as a ZFS mirror

Your site configs look fine for the most part but I notice in the vscode-server you're accepting gzip proxy_set_header Accept-Encoding gzip; But in your nginx.conf, even though you've enabled gzip you havent set any parameters for it. I would make these changes to your nginx.conf This section: http { ## # Basic Settings ## sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; client_max_body_size 100M; proxy_read_timeout 600s; # server_tokens off; and this section: gzip on; gzip_vary on; gzip_proxied any; gzip_comp_level 5; gzip_min_length 256; # gzip_buffers 16 8k; # gzip_http_version 1.1; # Compress all output labeled with one of the following MIME-types. # `text/html` is always compressed by gzip module. # Default: text/html gzip_types application/atom+xml application/geo+json application/javascript application/x-javascript application/json application/ld+json application/manifest+json application/rdf+xml application/rss+xml application/vnd.ms-fontobject application/wasm application/x-web-app-manifest+json application/xhtml+xml application/xml font/eot font/otf font/ttf image/bmp image/svg+xml image/vnd.microsoft.icon image/x-icon text/cache-manifest text/calendar text/css text/javascript text/markdown text/plain text/xml text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy; Then reload your nginx (systemctl reload nginx) and see if it makes a difference. Otherwise if still the same issue, try commenting out the gzip line in your vscode-server conf. As for SSL, I would generally put the SSL into each site config that requires it personally. That way you can use different certs for different subdomains or domains easily. I see you already have the SSL config in your emby conf but have commented it out to use a general SSL conf. That could be annoying when/if you want to use different subdomains without a wildcard cert.

Cant download those configs getting a Forbidden (403) error. What is this "tiny file" its downloading? Does it happen on all your sites, or just the code-server site? If its all sites, if you disable the code-server site, does it return to normal?

The reason people say ECC is crucial for ZFS, is because of it utilizing memory as a write cache (ARC). ZFS uses whats called 'write-back". So all data is written to the cache before its written to the pool and journald. Compared to most software implementations which will just write directly to the array, called "write-through". Hardware raid controllers already have ECC memory buffers for write-back. Technically Ryzen does "support ECC" but its difficult to find proper information on boards that support it. It also only supports UDIMM's not RDIMM's, so you need to be cautious there when youre buying ECC as well. I'm not sure why youre talking about eMMC? eMMC is just for as its name describes, embedded devices. It's a budget storage device for things like tablets, netbooks, IoT devices, headunits etc.... Just use an SSD or NVMe for your server. Or depending what OS, could use Flash Drive/SD Card as well (though these are far less reliable so best deployed in a mirror) for boot. ECC is generally unnecessary for home servers. While I do have servers with ECC, my primary storage ive never used ECC in the ~20 years ive been using storage servers at home, never had any noticable issues related to in-flight corruption. In saying that, if you are using it for video rendering, ECC can be a good idea since your memory is pumping through far more data, odds do increase for an error. Though for a single user workload the odds are still incredibly low.

Since Proxmox is Debian, I would assume that this would work

Use Wireguard. Pretty sure theres a jail for it in TrueNAS so you could run it on there. Its very fast and because its self hosted you wont be dealing with MitM network issues. If you have a dynamic IP then youd want to set up a dynamic dns as well. Plenty of free choices out there

Only by default, you can configure Docker containers (and Kubernetes etc...) with resource reservations and limits the same as a VM, just not in the 'bare bones' config, so most general users dont do this for home since their containers are pretty light Or with Docker Compose it could be something like: services: service: image: lscr.io/linuxserver/plex:latest deploy: resources: limits: cpus: 4 memory: 4096M reservations: cpus: 2 memory: 1024M Or with Docker: docker run --cpus=4 --cpus-reservation=2 --memory=4096M --memory-reservation=1024M lscr.io/linuxserver/plex:latest

Do a fresh install of Ubuntu 22.04.1 LTS Remove the Ubuntu Docker and install Docker CE sudo apt-get remove -y docker docker-engine docker.io containerd runc sudo apt-get install -y ca-certificates curl gnupg lsb-release sudo apt-get update && sudo apt-get upgrade sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --batch --yes --dearmor -o /etc/apt/trusted.gpg.d/docker.gpg sudo echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/trusted.gpg.d/docker.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-compose Give your user docker permissions sudo usermod -a -G docker <username> Log off and log back on Optionally install Portainer to manage the containers through an easy WebUI docker volume create portainer_data docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_dat a:/data portainer/portainer-ce:latest Then login via https://<hostname>:9443 For a Plex container Use /dev/shm (shared memory) for a transcoding path. It is essentially a ram disk on your host. And then assign your GPU to the docker container. First install your GPU drivers and dependencies. If its Nvidia then something like below sudo apt-get install -y nvidia-headless-no-dkms-525 libnvidia-encode-525 nvidia-utils-525 nvidia-docker2 Then test the driver is working using: nvidia-smi Then create your Plex container. Heres a docker-compose.yml example for Nvidia: version: '3.3' services: plex: container_name: plex image: lscr.io/linuxserver/plex:latest network_mode: host environment: - PUID=1000 - PGID=1000 - UMASK_SET=022 - NVIDIA_VISIBLE_DEVICES=all volumes: - '/opt/plex/config:/config' - '/dev/shm:/transcode' - '/mnt/media:/media' restart: unless-stopped Then use docker-compose to bring it up docker-compose up -d For UniFi Controller First create a network that you want UniFi to be on. Its a good idea to create a seperate network for general docker containers (like to do with Plex etc...) and containers to do with network etc... Note: We did not create a bridge network for Plex because its recommended to leave it on the Host network. The easiest way to create networks is in Portainer. Something like this (specifying the name of the network, the driver, the subnet and the gateway): Then create a docker-compose file like below: version: "2.1" services: unifi-controller: image: lscr.io/linuxserver/unifi-controller container_name: unifi-controller hostname: <hostname of your server> environment: - PUID=1000 - PGID=1000 - MEM_LIMIT=4096 #optional - MEM_STARTUP=2048 #optional volumes: - /opt/unifi-controller/config:/config ports: - 3478:3478/udp - 10001:10001/udp - 8080:8080 - 8443:8443 - 1900:1900/udp #optional - 8843:8843 #optional - 8880:8880 #optional - 6789:6789 #optional - 5514:5514/udp #optional restart: always networks: default: external: name: myNetwork Once you've saved your docker-compose.yml file, same thing to start it up: docker-compose up -d Once your containers are up then you can manage them through Portainer easily. You can use something like WatchTower to upgrade them and any other containers, automatically. It will watch dockerhub and if the package is updated, it will re-create your container automatically. P.S I typically put the docker-compose file in its respective /opt directory and run them from there for example Plex it would be /opt/plex/docker-compose.yml

You could also use SFTP over ssh. With an FTP client like Filezilla, you simply select the SFTP protocol, or in the hostname put sftp://yourserverip and your SSH port (e.g 22) and your username/password and it will connect FTP over SSH

I was just helping someone set up VLAN last with pfSense and a TPLink last week that has a similar looking configuration UI and we had major headaches as well. It didnt want to "just work" with what looks like it should be a valid config to someone whos done a lot on Cisco & Ubiquiti. Good to see you got it working

Just to help clarify, there are 2 different types of Ports. Depending on vendor theyre referred to differently but they are: Tagged (aka Trunk port) Untagged (aka Access port) With Tagged ports, they carry multiple VLAN ID's, and are primarily used for connecting network devices. So you would use tagged/trunk ports between your router & switches, and your switches & AP's Untagged ports, or access ports, typically are a single VLAN configuration. They're for connecting your end devices like PC's, Consoles, TV's, etc.... Pretty much everyone uses VLAN1 as its default or "native" VLAN. That is, any packet that is sent not tagged with an ID, will go over VLAN1. VLAN1 is generally reserved for the network itself for various communication between routers and switches etc....(It can be changed to any VLAN, but by default is just normally 1) With Tagged ports, they essentially pass the tag all the way to the end device. To connect a device like a PC etc...the device must understand VLAN's. By default a Windows computer wont be configured with a VLAN for its network interface, hence the computer will just have no network. Untagged ports end at the port where it is turned back into "native" traffic for the device connected to it. So if you have VLAN20 with 192.168.20.0/24 assigned to that port and plug in a PC, if your DHCP is setup it should instantly get a 192.168.20.0 IP address. As for the AP's, as leadeater said, they support VLAN's. You can leave them on the default ALL, or if you have a UniFi Controller you can define specific VLAN's allowed to the AP Then setup different SSID's for every network you'll be connecting wifi devices to, and assign the VLAN ("Network") to that SSID

I just use this bash script, and schedule it in CRON https://gist.github.com/Tras2/cba88201b17d765ec065ccbedfb16d9a

Sounds like more of a config issue? The difference is literally just using sysvinit instead of systemd (or previously upstart in Ubuntu). Systemd isnt any more resource intensive, its just the replacement system for initializing and monitoring processes in GNU. You can do a "minimal" install by using Ubuntu Server, and just add what you need to the base. I run base images on my VM's and then use docker with ubuntu minimal or alpine based images for apps to keep them lightweight and run them in containers. Most popular apps already have existing docker images that you can just download.

You're ok with the inefficiency? Between the H8QG6-F and Quad Opteron 6134 you're looking at about a 12500 PassMark while being 115W chips each. Heres the Quad 6174's (12C/12T chips) which is ~12600 PassMark. Compare that to even just a lowly Ryzen 3 3300X which is a single 65w 4C/8T CPU with the same performance...

Yes some RAID's work like that. MegaRAID (LSI based hardware) can do this. That is why you can select size for your Virtual Disk when you're creating it. We do this for one of our customers, we have a RAID0 for hosting VM's for some basic caching servers, and then the rest of the drive space is in RAID6 and turned into a VMware Datastore and mounted to those VM's. Years ago I used to do a "hybrid raid" which is the opposite concept. Where i RAID0'd 2 x 1TB together into a 2TB virtual disk, and then created a mirror in the OS with another 2TB drive, to have a 2TB mirror using 2 x 1TB and 1 x 2TB disks.

TrueNAS was the name of their "enterprise" solution, while FreeNAS was their community one. They renamed FreeNAS to TrueNAS Core (BSD Kernel) and introduced FreeNAS Scale (Linux kernel) But no don't use TrueNAS for such a low spec'd system, thats not what its made for. And you only have a single disk as well which doesnt utilize ZFS features. OMV is a great lightweight simple NAS OS which is based on Debian: https://www.openmediavault.org It supports Linux Software RAID (MDADM) in its Web UI if you want to do any sort of RAID.

It's kubernetes and Bluefin. Docker is just compatible with K3s pods. So it's a bit more complex than Docker under the hood I still prefer just using Docker for home lab with Portainer. I would second Unraid as well for its simplistic docker integration and its flexible storage with mixed drives and expansion

OK turns out it has to be a 2016 refresh with the GM206 (Maxwell 2.0) silicon to support H265 https://www.anandtech.com/show/9547/nvidia-launches-geforce-gtx-950-gm206-the-lesser-for-159 Not the 2014-2015 GM107 based card.