Selfhosted

60426 readers

229 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Security considerations for accessing NAS in external network (slrpnk.net)

submitted 2 years ago by Emotet@slrpnk.net to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

I'm strongly considering adding another backup location in the form of an old Raspberry Pi and a USB HDD.

I want the Pi to exclusively use the available network to connect to my Wireguard Server, so other devices (local to the Wireguard Server and remote connected to the server) can use it as a secondary backup location.

I'm kind of worried about a scenario, where my network is compromised and, through the VPN connection of the Pi in the external network, the external network is as well.

What are the best practices to secure such a setup?

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127@lemmy.zip 4 points 2 years ago (1 children)

Go the other way. Have the backup server connect in to the rest of the network.

[–] Strit@lemmy.linuxuserspace.show 1 points 2 years ago

I was considering doing something similar to OP, but I also think it's better to do it the other way around, having the backup server connect to the network when it's time to do a backup. Then you can just use the trusty ssh/rsync combo for backup.