20
submitted 10 months ago by MarkKray@lemmy.world to c/selfhosted@lemmy.world

Yesterday I setup remote access to my QNAP NAS and wrote a guide for it, that I can reference later. Might be helpful for someone. This was my first time doing something like this. So any notes on my approach are also welcome.

all 11 comments
sorted by: hot top controversial new old
[-] ShortN0te@lemmy.ml 2 points 10 months ago

Would not recommend setting the static IP on the device. A much better solution is to set up a static lease in your DHCP Server.

[-] Appoxo@lemmy.dbzer0.com 1 points 10 months ago

Hopefully your DHCP server never goes down.

[-] itmike@fikaverse.club 2 points 10 months ago

@Appoxo @ShortN0te On your own network you should be able to have a long enought lease that it shouldn't be a problem if your dhcp server is unavailable sometimes.

[-] ShortN0te@lemmy.ml -1 points 10 months ago

Hopefully your DHCP server never goes down.

DHCP is a curial part of every network. When it goes down then you need to respond. Leases usually are given out for several days. Even then, to fix yoy DHCP you can just use a static address temporarily.

Similar stupid statements are: Hopefully your Switch never goes down. Hopefully your Router never goes down. Hopefully your Server never goes down. Hopefully your House never burns down.

[-] MarkKray@lemmy.world 1 points 10 months ago

Thank you for the feedback. I wasn't aware of DHCP static leases. I quickly looked into it. Is the benefit that all IP addresses are assigned by the single DHCP server as opposed to having configurations scattered across individual devices? Or are there other benefits as well?

[-] ShortN0te@lemmy.ml 2 points 10 months ago

It boils all down to "centralized management".

With that the DHCP server has control over anything. Reduces (or basically eliminates) the risk of IP collisions. Also it gives you a place where you get a overview over your network. You change the DNS Server? You do it onetime in the DHCP settings. Etc. Etc.

[-] u_tamtam@programming.dev 1 points 10 months ago

Would be nice to be able to run WG on the NAS directly and not need a server, wouldn't it? I believe there are a few go/rust userspace WG servers out there but I don't know if anyone's using them for anything like that.

[-] Decronym@lemmy.decronym.xyz 1 points 10 months ago* (last edited 10 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
IP Internet Protocol
NAS Network-Attached Storage
VPN Virtual Private Network

[Thread #368 for this sub, first seen 21st Dec 2023, 16:15] [FAQ] [Full list] [Contact] [Source code]

this post was submitted on 21 Dec 2023
20 points (88.5% liked)

Selfhosted

39677 readers
246 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS