Linux

48328 readers

641 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Tailscale/synology/NFS remote access (lemm.ee)

submitted 4 months ago* (last edited 4 months ago) by pukeko@lemm.ee to c/linux@lemmy.ml

16 comments fedilink hide all child comments

UPDATE (13:40 ET / 2024-07-05): Got the connection working via SMB. Literally the only thing I changed was moving to a credentials file rather than specifying credentials inline, so ... I'll be trying to figure out what mystery affliction prevented the connection before. Leaving this up because there are a bunch of great suggestions for troubleshooting this issue in the comments. Thanks everyone.

ORIGINAL POST:

Currently pulling out my hair. I have a Synology NAS with the tailscale service (everything up to date). I have a NixOS client laptop, everything up to date.

I'm simply (?) trying to connect to a share via tailscale, and I have not managed to find anything that works. I've been using NFS, but I'm fine with SMB ... or carrier pigeons at this point.

Does anyone know of a step by step, detailed, current tutorial to accomplish accessing a Synology share via tailscale on a linux device? I would not have thought this would be challenging!

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

[–] just_another_person@lemmy.world 7 points 4 months ago* (last edited 4 months ago) (6 children)

My first guess is that using an actual hostname isn't going to work for you if that hostname is served by your local network DNS (meaning, not using magicdns on tailscale), which you would not be on when connected via tailscale unless you override your DNS server once connected.

Try by IP instead. Give errors if that doesn't work.

[–] pukeko@lemm.ee 2 points 4 months ago (5 children)

It's the same error regardless of whether I connect by tailscale IP (100.x.x.x) or the tailscale hostname, and it strongly suggests an issue on the Synology, but everything looks correct on the NAS (but I am by NO MEANS an expert):

mount.nfs: access denied by server while mounting $IP:/volume1/$mount

[–] just_another_person@lemmy.world 7 points 4 months ago (1 children)

Then you need to ssh into both devices and confirm they can both ping each other via the tailscale interface as a starter. That will at least shownif you have a routing problem.

[–] pukeko@lemm.ee 2 points 4 months ago

Apologies for the delay. July 4th festivities and rescuing a kitten from a storm drain intervened (upside: we now have a kitten).

I can ping the NAS from the client on the Tailscale IP (100.x.x.x) and the tailscale hostname. If I SSH to the NAS, I cannot ping the client machine, but everything on the NAS is available from the client other than the NFS share (and I think I remember reading that the Synology tailscale client does not support ping).

I realize we're sort of narrowing in on an NFS setting or possibly a firewall setting, and I appreciate your patience in going on this journey with me, but I have configured both according to, most relevantly, the tailscale documentation for connecting to a Synology NAS.

load more comments (3 replies)