• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle
rss



  • I cannot recommend any consumer router brand, at least not with stock firmware, because any of them don’t have guaranteed update policy. Further, some of the stock firmware contains insecure protocols, like telnet (yes, still), outdated ciphers (SSL, TLS 1.0), and some feature you want is always missing. Further they often lack innovative features like WireGuard in updates, mostly bug fixes and security patches.

    That’s why I would urge you to consider using one of the router/ gateway distributions listed below.

    Depending on your requirements, I can recommend the following router OS:

    • OpenSense (router without WiFi)
    • OpenWRT (router with WiFi)

    If you have an old laptop or pc to spare, you could at least give those two a try.

    Someone already mentioned it, OpenSense runs only on x86 / PC Hardware (and MiPS). OpenWRT can be flashed onto a lot of consumer routers as well as be installed on traditional x86 / PC hardware.

    OpenWRT has a hardware table on their website for supported models. Some of them come cheap if you buy them used and are pretty decent.

    If you like more flexibility, I can recommend building your own router. Used thin clients, Iike for example Fujitsu Futro S920. Thin clients are basically low-powered PCs, which are often cheap on the used market and provide a variety of hardware interfaces. Most use Intel NICs, some have secondary NIC, can hold SATA disks, provide interfaces for WiFi (pice, miniPCIe, m.2) or extension cards, have high efficient power supplies and are in majority are passive cooled. Or get some SBC/ Low-Powered board with the interfaces you need. It doesn’t need to be new hardware.


  • Please don’t host a router on a Hypervisor VM. That does not benefit security. First of all a router is an integral part of the (home) network, therefore it should not be dependent on anything, like a hypervisor. You want to be able to replace or update your server/ hypervisor independently from each other, for example in 5 hrs your router might be still rocking all data, but you would want to upgrade your home server / hypervisor. Furthermore all those OpenWRT, PFsense, OpenSense kernel/ OS hardening is more effective on the hardware itself, especially all RAM/ Memory based security measures. Also if you truly want to be more secure, you use dedicated hardware for multiple reasons, performance is dedicated to only routing/ firewall processing (no other service/ VM can block or slow down packet processing), reducing the attack surface (less software, less attack surface), easier to update.


  • Many given good advice on hardware, and there are plenty other threads with a lot of good recommendations.

    Regarding OS, I would recommend to ease into it, and try some before committing. Just try a few services, how stable it is and if the configuration complexity meets your personal learning expectations. (Self hosting is only fun, as long as you can get everything up and running. If you need 36hrs of troubleshooting for every 2nd problem, that awe for elf hosting melts pretty fast.)

    I started myself with OMV 0.x, and since then it’s gotten pretty decent. But I switched to plain Debian and CLI tool. After learning enough using OMV as my starting point. I also tried FreeNAS in the beginning, but that wasn’t for me.

    And I recently discovered CasaOS, wich is pretty neat and has a lot of benefits, but I haven’t tested it yet.