I’ve been searching around and can’t seem to find a good answer for how to share an NFS share with all devices on my Tailscale network. I know I can list out all of the IPs individually, but I’d like to have any new devices added to Tailscale to have access without having to update the share.

3 points

It’s really easy with headscale so I assume it must be really easy with tailscale too. How I did it was I created tiny tailscale vm to advertise the route to the ips I wanted access to on my internal lan. Then I shared the nfs share with the ip of that subnet router. now everything on my headscale network looks like it’s coming from the subnet router and it works no problem (Just remember you have it setup this way in case you ever expand your userbase, as this is inherently insecure if there is anything connected to your tailscale that you don’t want to have full access to your nfs shares)

permalink
report
reply
8 points

You can write shares to CIDR blocks e.g. 100.0.0.0/8

permalink
report
reply
4 points

If you enable Tailscale DNS, you can even mount the share using the host subdomain instead of using the ip address.

permalink
report
parent
reply
2 points

This is what I attempted by using *.mytailnet.ts.net, but that did not work. How would I enter this in my export file?

permalink
report
parent
reply
2 points

These IPs will be only resolved on nfsd restart. So you still need static IPs for nodes.

permalink
report
parent
reply
2 points

You need to get a subdomain. It should be two words separated by a hyphen. Then you use that as the address.

If your address is glossy-mouse, the address will be glossy-mouse.mytailnet.ts.net.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 4.8K

    Monthly active users

  • 3.5K

    Posts

  • 79K

    Comments