Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AN
Posts
8
Comments
394
Joined
2 yr. ago

  • Sometimes the appeal of socketed RAM is to just buy the bottom model and upgrade.

    Yeah, I'm all for swappable RAM and disk in my laptops, problem is that those that care about it generally also spend more on their computer.

  • Cockpit
    I do know about and use Cockpit with said virtual machine manager but I mostly use it as a shutdown/boot/restart app in my phone and a convenient service monitor and log viewer when troubleshooting.

    Wireguard/OpenVPN
    I really should try out Wireguard sometime but currently OpenVPN is fast enough for my bandwidth and I was already proficient with setting it up before Wireguard.
    The WebUI definitely looks useful.

  • For linux this is as easy as script

    <filename>

    , ex:
    [user@fedoragaming ~]$ script 20240313InstallingJellyfin.log
    Script started, output log file is '20240313InstallingJellyfin.log'.
    [user@fedoragaming ~]$ exit
    exit
    Script done.

    edit: and for Windows I recommend using putty, it can also save sessions to logs.

  • My Debian Hypervisor do have a DE (GNOME) to be able to easily access virtual machines with virt-manager if I mess up their networking, my Debian VMs run CLI only though.

    Regarding your last section I agree strongly - I only expose my vpn with no other incoming ports open. You also don't need to invest in a domain if you do it this way.
    I don't mind helping my friends install their openvpn client and certificate and it's nice to not have my services bombarded with failed connection attempts.

  • I definitely agree on starting to tinker right away and to setup snapshot/backup for your stuff and then break it. It also makes one learn how to roll back and restore which is as important as setting up the snapshot/backup in the first place.

  • Basic knowledge that makes selfhosting easier

    1. Some networking basics (Firewall, VPN, NAT, DHCP, ARP, VLAN) makes every selfhosters life easier.
      1b. Your ISP router probably sucks, but you might be able to experiment with some static DHCP at least. I'm a fan of the BSD based routers opnsense/pfsense but depending on what router you have you might also be able to run OpenWrt on your existing router.
    2. Some management system and filesharing basics (NFS, SMB, SSH, SCP and SFTP).
    3. Learning how to set up a backup for your stuff. The hypervisor you choose may or may not have a built in solution.
    4. Checking out a few different hypervisors (Proxmox, Incus, KVM/QEMU, etc) and find out which one you wanna dive deeper into.
      4b. Learn how to make a snapshot for easy rollback in said hypervisor ASAP. Being able to undo the last changes that broke a machine is a godsend.
      4c. VM, LXC, Docker and Podman basics (what are they, how do they differ, which one fits my usecase?)

      I know Flackbox has a good CCNA (networking) study guide on youtube, but that is way too in depth for a self hosting beginner.
      Here's some introduction to different parts of the network:
      Free CCNA 200-301 Course 06-05: IPv4 Addresses
      Free CCNA 200-301 Course 23-01: DHCP Introduction
      Free CCNA 200-301 Course 12-04: ARP Address Resolution Protocol
      Free CCNA 200-301 Course 21-01: VLANs Introduction
      Free CCNA 200-301 Course 21-04: Why we have VLANs
  • Yeah getting stuck behind CGNAT IPv4 and no IPv6 would break setting up your own vpn server. That would cause me too look for another internet provider.
    I only got 100mbps at home so I'm still running openvpn as I don't gain anything worthwhile from wireguard.

  • Any router that supports latest openwrt will be able to do a mesh network, if you have the option to run cable I would recommend ethernet backhaul instead.

    Sometimes there are caveats when setting up the mesh, f.e. the firmware issue and fix here:
    https://www.tekovic.com/blog/openwrt-80211s-mesh-networking/

    Hardware list:
    https://openwrt.org/toh/start?toh.filter.supportedcurrentrel=22.03%7C23.05

    edit:
    OpenWrt Mesh guide:
    https://openwrt.org/docs/guide-user/network/wifi/mesh/80211s
    https://openwrt.org/docs/guide-user/network/wifi/mesh/mesh11sd

    edit 2 adding the openwrt warning here:
    It is unfortunate that some manufacturers have used the word “Mesh” for marketing purposes to describe their non-standard, closed source, proprietary “roaming” functionality and this causes great confusion to many people when they enter the world of international standards and open source firmware for their network infrastructure.

    The accepted standard for mesh networks is ieee802.11s.
    The accepted standard for fast roaming of user devices is ieee802.11r.

    These are two completely unrelated standards.

  • The Fedora and Debian thread solution should definitely work with Pipewire, as both those distros comes with pipewire default and no changes are discussed.

    Keep an eye on the issue here:
    https://github.com/thesofproject/linux/issues/4055#issuecomment-1332331409

    Just to make sure we're on the same page, I take it that the following isn't working for you:

    1. Download necessary-verbs.sh from https://github.com/joshuagrisham/galaxy-book2-pro-linux/blob/main/sound/necessary-verbs.sh
    2. move it to /usr/local/sbin/necessary-verbs.sh
    3. make it executable with
      chmod +x necessary-verbs.sh
    4. Create a systemd service in /etc/systemd/system that runs the script at startup:
      [Unit]
      Description=Run internal speaker fix script at startup
      After=getty.target

      [Service]
      User=root
      Group=root
      Type=oneshot
      ExecStart=/usr/local/sbin/necessary-verbs.sh
      RemainAfterExit=yes

      [Install]
      WantedBy=default.target