Now it looks correct. If you have a Gigabit capable switch/router, and 100Mbps seems wrong, you should check your negotiated link speed on your Ethernet interface with something like ethtool [your_interface] | grep Speed
100Mbps is obviously low if you have a Gigabit router. Either way, you should have your jellyfin setup working without issue now.
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.
Apparently he does. It also says things that aren’t lies sometimes.
GOD DAMN, that’s an amazing idea.
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.
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:
We do? I haven’t seen those. Link me.
Well that’s…a bit conspiracy heavy I suppose.
The other explanation is that they are from states harder hit from the shutdown, and this essentially gets everyone paid right now and sets up this vote from two weeks from now where they can just shut it down again if the GOP doesn’t pony up.
100% NOT how updates work, but 👍
I’ve been building custom immutable distros for more than a decade. They have their place. Desktop and development ain’t that place.
The main application and use-case is obvious: IoT, EDD, consumer devices…etc. Maybe even bare metal if you don’t have proper PXE or other remote image booting. They mean nothing for cloud, because, well, why? They certainly aren’t needed for any container-based work either, because containers.
There’s a reason why devs aren’t adopting them.
Also, on your point about people “accidentally” deleting crucial files, that’s a straw man’s argument. If you have users in any kind of setting where you need a stable and repeatable install, you’re working with mapped network mounts and these users don’t have sudo/root access. If you’re dumb enough to be giving them said access, or deleting these files yourself, well that’s on you.
I absolutely love that they included a wider shot in the article that most people probably scrolled past, but I caught this in it:
They have the votes on the Dem side plus GOP defectors to pass something no problem. It would political suicide for the GOP people siding with Dems right to bail on it in a month, especially after people just got hit hard by this shutdown and the bills for their upcoming ACA premiums. I think they’ve got the votes.
Berries will last 3x longer in the fridge than on the counter. Longer if you give them a citric acid or diluted vinegar bath after you bring them home.
Depending on how this all was built and configured while Tailscale was running, you may need to take some steps to “undo” some things, like re-mounting your network mounts with the proper IPs (auto discovery may have messed things up).
What are the errors you’re getting?