• 9 Posts
  • 266 Comments
Joined 3 months ago
cake
Cake day: January 28th, 2025

help-circle
rss



  • Another point: 8gbps is mostly pointless. I would stay at 1gbps inside home and don’t bother to rewire and replace all my home equipment. That’s a long con game over the years slowly when each device has to be replaced anyway.

    Maybe plan for 2.5gbps inside for the time being of you can do that a zero cost like reusing wiring.

    I wouldn’t count on WiFi in any case, at best it’s a jimnick at that speed.


  • Get a nice hardware capable of running opnSense and use that immediately after your new ISP device. Just ignore their WiFi router, it will be crap whatever it is, unless you cat reflash with OpenWRT.

    Be prepared that the new ISP will .most probably have CG-NAT.

    Note: opnSense is based on *BSD so make sure the hardware you buy has supported 10gb network cards, at least two.








  • ShimitartoLinux@lemmy.mlssh reverse tunnel
    link
    fedilink
    English
    4
    edit-2
    11 days ago

    Wire guard + some nft tables or ip tables rules is a much better solution.

    Ssh on itself can do the port forward part but for the routing you still need the above mentioned rules. In addition, ssh will not autoreconnect if anything happens and you need to add autossh or some other solution to keep it rolling.




  • I usually pick the cheapest of a brand I trust. Kingston atm for my ssds.

    Don’t care, even the crappiest is way faster than what I need plus less energy hungry than mechanicals.

    I focus on size, buy the biggest I can afford according to the raid level I need. Currently have 4 x 4Tb Kingston ssds in RAID5.

    Edit: don’t buy ssds on aliexpress, don’t go that cheap… Go cheap like buy consumer level stuff not server grade stuff, but still from reputable sellers and brands.

    Yeah, would be great to buy server grade stuff, but I don’t have a server grade budget.




  • ShimitartoSelfhosted@lemmy.worldHelp with domain
    link
    fedilink
    English
    012 days ago

    Create the subdomains and have them all point to your PUBLIC IP (10.172… But keep in mind 10… Are -not- public ip)

    You will need to setup redirect from your router/gateway to your internal ip.

    Unless you are on cg-nat (that would explain a 10… class ip) in that case, you will definitely need a real public static ip

    To “match” the various ports all to 443, you will need a reverse proxy, since those ports are not standard. This could be mitigated with srv DNS records, but I really strongly suggest not to go public without https and reverse proxy.