• 0 Posts
  • 28 Comments
Joined 7 months ago
cake
Cake day: June 21st, 2025

help-circle

  • vividspecter@aussie.zonetoSelfhosted@lemmy.worldOpenWRT router
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    10 days ago

    Also unrelated, but if you’re running a x86 system with gigabytes of RAM, why not run Opnsense at that point?

    I believe it’s gotten better but historically *BSD had poor SQM support (bufferbloat mitigation), which is particularly useful on slower, asymmetric connections and where low, consistent latency is paramount.

    It was also a bit of a laggard on Wireguard support, although that’s long since been fixed. So mainly you might prefer OpenWRT if you want the Linux kernel which tends to get features more quickly. Also because it’s so low on resource usage (including disk space), you can put it in a VM and very rapidly recover in the case of issues.

    You could of course also use a full Linux based router OS, but I don’t believe there are many with a web interface, which most users would prefer.






  • You could also secure what peers inside the tunnel can access, particularly if you plan to give other people access. I.e. only allow only port 443 on a given server using a reverse proxy. It’s not a major threat either way but it would reduce the amount of access if someone gets into your phone/laptop etc.



  • probably something with my ISP that I can’t really easily work around

    I’d try and find out if you’re behind a CG-NAT first, and whether you have IPv6 support. Some ISPs will turn off CG-NAT if you ask if that is the reason you haven’t been able to get things working. Wireguard will then work properly which is a bit kinder on battery life with mobile devices in particular compared to Tailscale and Netbird (although both are improving in that regard).









  • I’ve used both Headscale and a while ago, Netbird. Some of this will be in comparison to raw Wireguard, which I’m also using.

    I’m currently using Headscale, but it does have some annoyances. There were breaking changes fairly often for a while, although it looks to have mostly stabilised now. Tailscale itself is pretty invasive with its routing rules and DNS which can break things or cause unexpected behaviour, which doesn’t occur with raw Wireguard which is more predictable once you understand it. The Tailscale android client has been somewhat unreliable and clunky, although getting better, although third party Android clients for Wireguard, in turn, have also improved Wireguard usage dramatically. On the other hand, Headscale (or Netbird) are pretty much necessary if you are on a CG-NAT and need ipv4 access, and more usable if you want to build a mesh network.

    I can’t remember if I tested the service Netbird or the self-hosted version (I think both) but the main thing I remember is that it had poor support for ipv6, which I consider mandatory. Otherwise, the Android client seemed solid and it felt well-designed overall. And maybe the ipv6 support is better now.



  • Primary goal: Navidrome as server combined with a VPN (tailscale is probably the easiest to setup but not technically self-hosted). Clients can be any that support the subsonic protocol. I personally use dsub2000 (android) + supersonic (Linux) but there are others. I’d start by testing it on your LAN to see if it’s workable.

    Secondary goal: if you can get all 12 people to install Tailscale on all relevant devices then you can continue to use that. If not, you’ll need to host navidrome (or an alternative) publically preferably with a reverse proxy for better security. You could alternatively try Tailscale funnel or some cloudflare solution to host navidrome.