• 25 Posts
  • 2.29K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle





  • Not sure what the Frame means with any of this. It’s going to be running the same stack as Deck, which is KDE. It’s also not going to be any sort of headset for your PC, at least at the outset.

    As for your other Dr questions, it’s all just personal preference. The Desktop is just window dressing on a compositor and window manager anymore. If you’re comfortable without all the system helpers and convenience of using either Gnome or KDE, you can just run a WM like Hyprland or Sway instead.








  • If you’re not comfortable using SSH, each Linux DE comes with its own RDP setup, so refer to the docs of whichever you’re running to set that up if you want things to be super simple.

    Past that, there’s tons of stuff, but I would generally avoid VNC these days because it’s pretty much a dead protocol that is insecure and inefficient.

    Some people prefer to use RDP compatible tools, some people just use Moonlight. You can use whatever is comfortable for you, really. I would avoid all the suggestions that are telling you to install the giant constructs like Mesh Central though. That’s overkill for just two machines here.




  • So then as a next step, I’d set Wireshark up on one of your regularly hosts, set it to filter for DHCP traffic, confirm you’re seeing regularly advertisements first, then reboot the device that’s responsible for DHCP and make sure it resumes sending those advertisements when it comes back.

    If it’s the same device handling DNS, make sure it’s also immediately returning responses after the reboot as well with dig or nslookup.




    1. Okay, so no issues there
    2. DHCP handles the address assignments in your network, not DNS. DNS resolves to named host queries. If no devices got IP addresses, that’s one problem. If you couldn’t resolve public hosts like www.news.com, that’s a DNS problem. If you couldn’t resolve INTERNAL named hosts you refer to around your network, then that’s also DNS, but a different problem.

    My hunch here is that you MIGHT be using a named host as your DNS resolves instead of an IP address in your network, OR, for some reason your DNS resolves doesn’t have a static address. Never use named hosts to point to network services, and all network services need a static IP, so go and check all of that.


  • Well…no, and this is what I’m saying.

    Every downstream issue you try to solve with redundancy has a doubled and duplicate cost to it’s upstream. Internet links, load balancers for web services, and in this specific situation, UPS’s.

    Throwing more servers at a homelab with no power is just wasting money without more UPS power in the mix. You have 4 servers, and want HA for everything on your network, expect to have two of everything, including UPS units.

    This is the n* sunken cost of redundancy at its core, and in your example, you’re assuming this person even had a generator or whatever, but even if they did, they’d need an even BIGGER generator to run all this stuff.

    That’s why my points deal with solving for what they have and making it work better than, instead, immediately jumping to adding more and more and more to the stack. It’s just not necessary when all they want is a graceful recovery to power loss.


  • Need more details here:

    1. What’s your bandwidth and delivery medium like?
    2. What are your edge/router specs?
    3. What hardware would you be hosting this on?
    4. What format are you expecting to stream (audio and video formats)?
    5. Related to #5, what hardware would you streaming from?

    OBS and Owncast should allow you to do this for the most part, but it’s heavily dependent on all of the above.