First, a hardware question. I’m looking for a computer to use as a… router? Louis calls it a router but it’s a computer that is upstream of my whole network and has two ethernet ports. And suggestions on this? Ideal amount or RAM? Ideal processor/speed? I have fiber internet, 10 gbps up and 10 gbps down, so I’m willing to spend a little more on higher bandwidth components. I’m assuming I won’t need a GPU.

Anyways, has anyone had a chance to look at his guide? It’s accompanied by two youtube videos that are about 7 hours each.

I don’t expect to do everything in his guide. I’d like to be able to VPN into my home network and SSH into some of my projects, use Immich, check out Plex or similar, and set up a NAS. Maybe other stuff after that but those are my main interests.

Any advice/links for a beginner are more than welcome.

Edit: thanks for all the info, lots of good stuff here. OpenWRT seems to be the most frequently recommended thing here so I’m looking into that now. Unfortunately my current router/AP (Asus AX6600) is not supported. I was hoping to not have to replace it, it was kinda pricey, I got it when I upgraded to fiber since it can do 6.6gbps. I’m currently looking into devices I can put upstream of my current hardware but I might have to bite the bullet and replace it.

  • net00@lemm.eeEnglish
    5·
    1 day ago

    There’s a million ways to do anything when self hosting, so I’ll just talk about what I have and if you interested just reply.

    I only host a few services for now: Invidious, CloudTube, Redlib, FreshRSS. All of them as docker containers, this helps in quickly updating them and isolating their configurations. I have a few TB of disk space on the server itself that I can access through SMB3 shares, so I don’t have a proper NAS yet. Probably will do so at some point when I need it.

    As for hardware, I’m using an HP mini-pc with

    • Ryzen 5 PRO 3400GE
    • 16GB DDR4
    • 256GB boot drive (NVME), 2TB storage drive (HDD)

    This mini-pc can literally be opened by removing 1 screw, so hardware changes/cleaning can’t get easier. I installed Debian on it

    As for remote access, I use twingate instead of self-hosted wireguard. Mostly because I’m using my ISPs router and they like to reset it whenever they want. I’m also not confortable opening ports on the router. Twingate covers my use case completely so I never went back to this. I can map a custom domain to the server’s IP and this meant I just switch on twingate when I’m out and can access it seamlessly.