• 4 Posts
  • 86 Comments
Joined 2 years ago
cake
Cake day: July 20th, 2023

help-circle
  • Precisely bitwarden movement proves my point. Bitwarden tried to degrade the features/compatibility of the solution and they couldn’t because of the vaultwarden implementation.

    Can they always add new features after a pay wall? Sure! But once foss Sw is here it is simple impossible to remove functionality, at most, to get some coins for services not fully selfhosted.

    If tailscale tries to do something similar is goint to be a shoot into their own leg, because all the sw already disclosed makes it impossible. Could they make the relay a paid one? Sure but then they will face the competence of a vps with the Headscale implementation.

    This and only this is because in your home lab only foss Sw should be allowed, even if you need to pay some money from time to time















  • Hi, depends of your knowledge level I can suggest you 2 alternatives.

    If you are tech savvy I recommend you to setup your own router and then install something like opnsense, then you can use wifi extenders to make sure you reach all the corners. For the hw there are a lot of router boxes in Amazon for 200€ with powerful cpus and 16 gb ram that should be future proof for the following 15 years. Opnsense (for the Sw) also has a very long record of supporting x86 architecture for ages.

    In case you are more limited kn tech skills try to get a top of art router from a reputable manufacturer and make sure you can install openwrt on it. Openwrt is more limited speaking about features but it is a more router oriented Sw which can be easily understood. It also has a good record of supporting legacy hw.

    As somebody else suggested, the obsolescence of the electronics is more related with the Sw and regulars updates than the hw itself. A good made hw can last >25 years without any probelm. Assuming that the performance is still good for your needs.



  • The problem with such advance Sw is the overwhelming list of options and the lacks of sane defaults

    It is not the same to find 10 different (and complex) solutions when you are evaluating what you can do for solving a problem. It adds more noise to the solution than anything else. And of course the minimum resources needed ;)

    For the downloading I suggest you to have the download folder and the main storage both exported under the same nfs folder. Quite handy.


    1. It depends of what you want as future proof (expansion capabilities). Usually home user nases come with low power cpu, a high power cpu usually is a enterprise grade nas, really costly for a home user. So having it separated makes the cpu upgrade easy but now you have 2 boxes. But if your terramaster comes with a decent cpu I don’t see any problem.

    2. True nas scale is really a behemoth able of almost everything. I would start with something more reduced like omv or unraid. You really don’t need the advance enterprise features of that and it will add only complexity to the setup.

    3. If you use NFS for exporting folders from your nas, the “computing box” will see this as a local folder, so no need to have 2 copies of the same file.

    Hope it helps


  • Huh???

    Honestly I don’t see your problem, a nuance? Sure! An unsolvable problem? For sure not.

    If you want to have your system reachable from the Wan then you will need a domain name. If you have a domain name then it is needed to be resolved by a dns server.

    If there is a dns resolver then you would able to update it dynamically every time your ip changes.

    True that the time alive of the dns records must be low enough to ensure that an ip change does not let your system down for an unacceptable amount of time.