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.

  • ShortN0te@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    TLDR, the developers of pfSense are not the nicest people sometimes. If this bothers you, consider checking out OPNsense.

    So first the author is arguing around on the router section that you should not buy a cheap router but then goes for pfsense instead of opnsense, i understand that when you are used to pfsense that you may not want to switch but recommending it for new ppl is just stupid. They have shown their hostality against their OS community in the past see https://news.ycombinator.com/item?id=13615896

  • mneasi@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    This guide seems pretty dated in terms of technologies and approaches used so I wouldn’t follow it 100%.

    • ShortN0te@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      And it is heavily opinionated, without pointing out other solutions like for example the use of openvpn without mentioning wireguard even once.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    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).

    • Slotos@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      Gl.iNet is a great value router, but if you want to do anything really interesting, it won’t do.

      I have Slate AX chugging along, and have been eyeing teklager boxes to do actual routing, with slate as an access point.