• 2 Posts
  • 24 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle


  • I’m not sure why you’d NOT want a battery powered one, because as you say, the batteries last years, and a USB powered one would waste much more electricity over time, but I digress.

    If you have any mini SoC boards or ESP32 devices laying around, you can get dirt cheap 2-pin external temp sensors. Works on anything with a GPIO pin out that supports simple I/O.

    Anything you find that is Zigbee by nature will be battery powered, however, you might be able to find a device with a different purpose that happens to have temp sensors that export data you could monitor.





  • I hate to keep being in these threads saying the same thing, but new people need to know:

    THERE IS NO APPRECIABLE PERFORMANCE DIFFERENCE BETWEEN ANY LINUX DISTRO FOR GAMING

    Doesn’t matter if it calls itself a “gaming” distro, or it wins by 10% in some benchmarks here and there. Any distro can be tuned like any other distro in every single way. No distro has any proprietary bits that make it better than another, and even if they did, you’d see devblogs or GitHub scripts you can one-shot to tune whatever you’re running to perform similarly.

    Save yourself from falling for the hype, and save yourself the time of sitting through videos like this.





  • Well, firstly, it’s not what Tailscale is meant for. I’m getting downvoted by the people using the wrong tool for the wrong job.

    You don’t install a VPN on all your local machines just to talk to each other. That’s insane. You especially don’t install one that, while misconfigured, is sending all of its traffic OUTSIDE of your local network, then back in. This is what Tailscale on a number of local machines will do by default.

    The way Tailscale works is by installing a Wireguard client on a machine. It then checks in with their DERP servers to figure out it’s network situation (behind NAT, peers in the network, routing tables…etc). So when you have more than one client on the Tailscale network, it automagically assumes some things, the first being that these two machines dont have a more direct route to talk to each other.

    So then it will attempt to bridge a path between the DERP server each client is checked into, and pass traffic that way. Which means you then have two machines on the same local network sending traffic OUTSIDE of that network, then back in to complete a VPN network.

    This is stupid.

    You setup multiple different networks and use exit nodes to bridge two networks together with Tailscale. That’s the entire point. This means setting up routes to let the orchestration layer know that a set of certain machines exist in the same network, and shouldn’t use Tailscale to communicate with each other. Then it will only be using routes for REMOTE networks, where other clients exist, to pass traffic over the Tailscale network.

    May I ask what you were planning on doing with Tailscale? I can point you in the right direction.