No…but you were the one trying to twist this exact thing out of context to meet your foolish argument. Same as right now 🤣

Thanks for mentioning that. Block

TLDW: “Everyone ignore my personal and political positions on everything, I’m giving you free code…”

We don’t need another Reiser incident, shitbag.

Go fuck yourself, David.

This guy fucks…or plays games with controllers

Sounds awful and tedious

Apparently he does. It also says things that aren’t lies sometimes.

Gonna say what I said so many times, and even a few times in this comment section.

ALL.software.has.bugs.

The language doesn’t matter. AI doesn’t matter. Testing doesn’t matter. Every single piece of software will be vulnerable to something eventually.

Staying on top of it is the best you can do.

ALL software has bugs. Doesn’t matter what the language is.

GOD DAMN, that’s an amazing idea.

Canonical didn’t make these tools…

Opentofu is Terraform 🤣 I generally don’t throw that out there to prevent confusing people, but I prefer it, honestly.

Packer builds images you can upload to cloud platforms.

Terraform/Opentofu executes API calls to orchestrate spinning things up and down.

Cloudinit is the native built-in bootstrap framework of instances themselves that all the major cloud providers support. It’s what executes as “userdata” as some call it. Check your cloud provider docs for how to hook it in.

Which batch of you turds was in here all up in my stuff last week when I said Rust projects have security vulnerabilities all the time just as any other and you all were arguing like “nuh-uh cuz Rust”?

Step up.

Use Terraform + Cloudinit scripts if you’re using a cloud platform, and make sure you version everything or use Packer to make versioned images.

I feel this is a trap…

Tailscale is for point-to-ooint connections between locations, so yes a VPN. That doesn’t mean two machines on a local network should be using it to talk to each other. Let me explain a bit:

Say you have two machines on two different networks 100 miles apart. You put those two on Tailscale, that virtual interface sends traffic through their servers and figures out the routing, and then they can talk to each other…cool.

Now move those two machines to the same network and what happens? Tailscale sends their traffic out of that same virtual interface and THEN brings it back into the network. Sure they can still talk to each other sort of, but you’re just skipping using your local network. Doesn’t make any sense.

This is because of “default routes”. Whenever you plug a machine into network with a router, that router sends along information on where this machine needs to send it’s traffic to get routed properly. Usually whatever your home router is. This is the default route.

Once you bring up the Tailscale interface without proper routing for your local networks taken into account, it sets your default route for Tailscale endpoints, meaning all of your traffic first goes out through Tailscale, and you get what you’re seeing here.

Regardless of what you read around and on Reddit, Tailscale is not as simple as it seems, especially if you don’t know networking basics. It’s meant to be used with exit node endpoints that route to a larger number of machines to prevent issues like this, NOT as a client in every single machine you want to talk to each other. I see A LOT of foolish comments around here where people say they install it on all of their local machines, and they don’t know what they are doing.

To my point: read this issue to see someone with similar problems, but make sure to read through the dupe issue linked for a longer discussion over the past number of years.

Extra thread here explaining some things.

This blog goes deeper into a possible solution for your setup.

The simplest solution for Linux is usually just making sure to NOT run Tailscaled as root, just as your local user. This should prevent the global override of your machines default routes in most cases, but not all.

The proper and more permanent solution is running Tailscale on your router and letting that single device act as an exit node and handle advertising the proper routes to clients through the DERP server translation.

Also, see the netcheck docs as it can help quickly debug if things are working properly or not.

Well a 6-7X improvement is something, but you still see the Tailnet running there.

Honestly, if you don’t know networking and routing, don’t mess with Tailscale. It breaks shit like this for all these people who don’t know what they’re doing who are doing things like installing it on all their local machines because they have no idea how it’s used or it’s purpose, and it’s clearly your problem right here because both you, and your tailnet are confused.

I know for a fact your containers are ALSO running Tailscale or something equally not good, because you’ve definitely got a polluted routing table from local route loops, and you’re confused as to what that is, how to prevent it, and why it’s broken.

1. Shut it down EVERYWHERE ON YOUR LOCAL NETWORK.
2. Make sure your default routes only point to LOCAL ADDRESSES
3. Recheck your transfer speeds which should be 100MBytes/s+

Why is your iperf run referencing a local 100.X address then?

That doesn’t look right. What are the two IP’s of the machines on your network?

Edit: you must be using containers or something. Don’t use bridge networking if you’re unsure of the performance issues there.

This is incredibly confusing and formatted oddly, so let me get some clarification:

1. What protocol are you using to mount the NAS to the Ubuntu machine?
2. What did you use to transfer this slow file over the network? The disk transfer rate would be much faster than the network in any case, so 160MB/s may just be the network max.
3. Have you tried other files and methods to transfer, like SSH, Rsync…etc? Try those and post the speeds.

☝️