-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vpn access #31
base: main
Are you sure you want to change the base?
Vpn access #31
Conversation
As a longtime tailscale user this looks good to me. Disclaimer: I haven't personally followed this procedure as I preferred in my case to use a tailscale subnet route on my router to expose the 3d printer onto my tailnet. That being said, I think we should go ahead and merge this. |
|
||
**Alternative Option - Subnet Router** | ||
|
||
While out of scope for this specific documented procedure, it's worth calling out that one can configure a [subnet router](https://tailscale.com/kb/1019/subnets) to avoid having to install the tailscale client on your printer. It allows for more flexibility but comes at the cost of complexity; ie dedicated device acting as the subnet router and configuring it as a gateway on devices that you want access to. This notice is to draw awareness to the end user that alernative installations exist. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tailscale subnet router does not require configuration from the devices on that subnet at all. If you have a tailscale subnet router exposing 192.168.1.0/24
to tailscale, devices on the tailnet can access the subnet through tailscale, but devices on the subnet can't access the tailnet. It's essentially a split-vpn.
I thought this may be useful for friends who don't want to use qidilink but also want to have remote access to their printer.