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.
Edit 2: This is looking pretty good right now.
Just kinda flipped through his guide. It’s a bit dated on knowledge and techniques, even for beginners.
You don’t need a computer for a router. Get a router that ships with OpenWRT and start there. GL.iNet makes good and affordable stuff. Use that for your ad blocking, VPN, and so on to get started.
I’d just skip OpenVPN altogether and get started with Wireguard or Headscale/Tailscale.
If you want to run other heavier services, start out with a low-power minipc until you’re settled on what your needs or limitations are. You can get a very capable AMD minipc for $250-300, or an n100 low-power for a bit cheaper. Check out Minisforum units for this. Reliable, good price, and solid warranty.
If you deal in heavy storage, maybe consider adding a NAS to the mix, but maybe that’s a further steps. OpenWRT is a good starting point just to get your basic network services and remote access up, then just move on from there.
A good and fun starting point for some people is setting up Home Assistant on a minipc or Raspberry Pi (honestly, the costs of Pi boards now is insane. Might be good just to get the minipc).
Just glancing through that guide:
OPNsense instead of Pfsense, because pfsense is going to rugpull, it’s just a matter of time. I wouldn’t trust the twats that run it farther than I could throw them because they’re pretty silly people. Rossman suggests exactly this in the intro to the router section, he would change if he hadn’t been using it for a decade already. Unfortunately, a lot of this guide is focussed on how to do it via pfsense and if you’re brand new, you’re going to have to figure out how to do it in OPNsense yourself.
Wireguard/Tailscale instead of openvpn. Faster and way easier to set up. Don’t even try to set up a full LAN routed VPN, just use Tailscale for the services you want. And use it for everything and everyone instead of punching holes in the firewall.
He’s definitely right about mailcow; if you’re reading that guide for information, you are not a person that should be self-hosting email.
This guide seems pretty dated in terms of technologies and approaches used so I wouldn’t follow it 100%.
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.
I would not look at his guide. If you’ve watched any of Louis’ videos, you already know this guy is a ranting machine. He can go on and on for hours about things. I watched about 15 minutes of his rambling and realized he had gotten basically nowhere. It’s also one of the more complex ways of doing things. Use ZimaOS to get started with the easy button.
Stick with whatever router you have, for starters. You can upgrade later. You don’t necessarily need that at all.
For the actual server I highly recommend this guy. N100 is very common due to being very inexpensive and efficient. You’ll have to add RAM and an SSDs but you probably want to choose exactly how large that is anyway. It has 4xNVMe and 2xSATA, if you decide you want to expand later.
