as someone who does publicly expose services that have auth, why does CGNAT make exposing ports publicly bad?
Tailscale is pretty useful
11–20 of 419 posts
Re: Tailscale is pretty useful
#12I love tailscale, but the performance overhead on file transfer (my primary use case for it) is very real. Samba transfers take a 15 megabyte per second hit over tailscale even with a fairly fast CPU on both ends (Ryzen 3600 and Ryzen 7900X3D) on my local network
Re: Tailscale is pretty useful
#13I love tailscale, but the performance overhead on file transfer (my primary use case for it) is very real. Samba transfers take a 15 megabyte per second hit over tailscale even with a fairly fast CPU on both ends (Ryzen 3600 and Ryzen 7900X3D) on my local network
In my experience Samba is just a slow protocol due to its chattiness.
Re: Tailscale is pretty useful
#14> it’s no longer possible thanks to a cursed thing called CGNAT as someone who does publicly expose services that have auth, why does CGNAT make exposing ports publicly bad?
Re: Tailscale is pretty useful
#15> it’s no longer possible thanks to a cursed thing called CGNAT as someone who does publicly expose services that have auth, why does CGNAT make exposing ports publicly bad?
Re: Tailscale is pretty useful
#16I love tailscale, but the performance overhead on file transfer (my primary use case for it) is very real. Samba transfers take a 15 megabyte per second hit over tailscale even with a fairly fast CPU on both ends (Ryzen 3600 and Ryzen 7900X3D) on my local network
Re: Tailscale is pretty useful
#17> it’s no longer possible thanks to a cursed thing called CGNAT as someone who does publicly expose services that have auth, why does CGNAT make exposing ports publicly bad?
Re: Tailscale is pretty useful
#18I love tailscale, but the performance overhead on file transfer (my primary use case for it) is very real. Samba transfers take a 15 megabyte per second hit over tailscale even with a fairly fast CPU on both ends (Ryzen 3600 and Ryzen 7900X3D) on my local network
15 MiB/s is trivially handled by any CPU you're likely to run. Indeed 100 MiB/s seems reasonable. 15 MiB/s cap seems either the protocol being used is doing too many round trips (assuming the machines you're testing with are far apart) or the network that's being set up requires routing through Tailscale's infra for hole punching.
Re: Tailscale is pretty useful
#19Re: Tailscale is pretty useful
#20The features here seem to be fairly standard with most the WireGuard based VPNs these days. For example, I use Nord for my use-case which is very similar to the author's. This allows me to rsync my home directory between my laptop, tablet, phone's Termux env, and desktop (all running Linux) to maintain configuration parity and file locality regardless of where I turn these devices on, so long as they have internet. D…