Ah, so I bet what they’re doing is looking like a single VPN from the Android OS level, setting a default route into that, and then doing routing in userspace.

I have not used such a configuration, but I believe that it’s fine to have multiple WireGuard VPNs concurrently up, at least from a Linux client standpoint. I have no idea whether your phone’s client permits that — it could well be that it can’t do it.

Your routing table would have the default route go to a host on one of them (and your Internet-bound traffic would go there), but you should be able to have it be either. Or neither — I’ve set up a WireGuard configuration with a Linux client where the default route wasn’t over the WireGuard VPN, and only traffic destined for the LAN at the other end of the WireGuard VPN traversed the WireGuard VPN.

From Linux’s standpoint, a WireGuard VPN is just like another NIC on the host. You say “all traffic destined for this address range heads out this NIC”. Just that the NIC happens to be virtual and to be software that tunnels the traffic.

EDIT:

It sounds like this is an Android OS-level limitation:

https://android.stackexchange.com/questions/261526/are-there-technical-limitation-to-multiple-vpns

In the Android VPN development documentation you can find a clear statement regarding the possibility to have multiple VPNs active at the same time:

There can be only one VPN connection running at the same time. The existing interface is deactivated when a new one is created.

That same page does mention that you can have apps running in different profiles using different VPNs at the same time. That might be an acceptable workaround for you.

https://en.wikipedia.org/wiki/.wtf

I have additional sound deadening material if I need to apply it but I’m not there yet.

That’s probably a pretty good idea in terms of cost. I checked earlier when I made the comment to see what the price difference these days was, and IIRC a non-isolated 18U is ~$800 and an isolated 18U is ~$1800. They aren’t putting anything like $1k of sound-absorbing material into the rack.

Heh. Someone else in this thread posted an image that has three disconnected Elitedesks just stacked on each other on the bookshelf housing their homelab, another powered-on one, and what I think might be two or three more Elitedesks that are partially-obscured.

Thanks!

I’m still not using one. The problem is that you’ve got two classes of devices that haven’t quite converged to what I want.

UPS

Traditionally, the purpose of UPSes isn’t to keep systems running (other than through very short outages). It’s to do one of the following:

• Provide a small amount of buffer until a backup power system, like a generator, has time to come online.

• Give the systems time to shut down cleanly. If the user is right there, they have time to save their work. This was particularly an issue before journaled filesystems became the norm, since an unclean shutdown in the era when Windows was using FAT, Linux was using ext2, and MacOS was using HFS had at least the possibility to corrupt your filesystem. They have the ability to report their charge level to an attached computer so that it knows when the battery level is critical and then software on it can start it shutting down. On Linux, the most-common software package to do this is Network UPS Tools, or NUT.

These things don’t need a lot of capacity. They rarely get drained, so they usually use lead-acid batteries, which are heavy and don’t have many full charge-discharge cycles in them (but are pretty happy staying fully charged all the time). You can still get these. The lead-acid batteries are replaceable, though, so an old UPS can keep going for a very long time.

Powerstation

These are designed to keep attached devices running for a longer period of time. Unfortunately, they have a couple of important limitations for powering computer systems.

• They do not normally have the ability to report their charge level. Irritatingly, they do nearly always have a voltmeter rigged up to some software to map voltage to charge remaining to drive a ‘charge remaining’ display on the device, and there are USB HID device classes for reporting charge levels to a host OS, but for some reason, powerstation manufacturers don’t seem to have an interest in making a powerstation that has the latter functionality. NUT does have a USB HID backend, which means that it can monitor and shut down a system if they’d expose it. I’d really prefer the ability to treat one of these as a laptop-style battery, as Linux (as well as other OSes) have the ability to hibernate on low battery. On Linux, these show up as /sys/class/power_supply/BAT*, and there’s lots of software to display charge information and act based on low levels…but AFAICT from looking around the kernel, there is no way to get the kernel to deal with a USB HID device reporting remaining charge like this as a BAT device.

• Computer power supplies can only smooth out so much of an interruption in their power. Computers rely on something on the order of a 10 millisecond transfer time after AC goes out until the UPS needs to be running full-tilt. searches ATX PSUs apparently are only required to operate for 16 milliseconds without power. Other hardware attached may or may not actually deal well with interruptions, but obviously the shorter the transfer time, the better. It looks like line-interactive UPSes tend to do something like 3-6 milliseconds. The problem is that a lot of powerstations have a transfer time in excess of this.

There are some LFP UPSes now, but these have their own disadvantages. They tend to be fairly pricey, and the batteries are often not replaceable, which means that unlike the old lead-acid UPSes, when the battery dies (which will take longer than with a lead-acid battery), the whole device is also going to the landfill.

And lastly, you have the problem that while lead-acid batteries are pretty mature and prices are pretty stable, LFP battery prices are coming down (and sodium-ion might start competing with them for fixed batteries). If batteries are cheaper in the future, waiting means a better deal.

I don’t currently run a UPS on my systems (though I have in the past). I kind of decided that if I’m going to run a UPS, I’m probably going to just bite the bullet and use the combination of a traditional lead-acid UPS and an LFP powerstation, with the UPS plugged into the powerstation. In that configuration, the powerstation provides provides the longer-running power, and the UPS deals with short transfer time and warning computer systems that power is about to go out. This isn’t perfect, because (a) your computing devices can’t see the remaining charge on the powerstation in an outage (b) at some point, one still has to toss the LFP powerstation, and (c) there’s a little extra hardware involved. However, it also has a number of benefits:

• Lead-acid UPSes pretty much always have replaceable batteries. One can keep the UPS around, though the batteries will have to be periodically replaced.

• The UPS will provide time for the system to shut down.

• UPSes are designed specifically for this, and have short transfer times. You don’t need to worry the way one might about a powerstation having marginal transfer time.

• You can get a lot of AC-related functionality in UPSes, like online capability (which will clean up the power, if you want), which isn’t generally available in powerstations.

• You can upgrade the “powerstation”, even (if you want) doing a build-your-own thing with separate cells and an inverter and charge controller (which is generally more cost-effective for larger systems) down the line. These discrete-component systems are also a lot easier to provide human monitoring of remaining charge, since you can pick the components (and worst case, all you need to do is connect a voltage sensor that can talk to a computer to it), though they don’t integrate as nicely off-the-shelf with something like NUT as do traditional UPSes.

I’m not saying that this UPS+separate-battery-system is the only route to take, but I spent some time banging my head on it, and wanted to share if anyone else is similarly thinking about the same thing – that there may be a good argument to have a traditional UPS and some kind of separate battery system.

I remember looking at Sysracks racks a while back when I was trying to find sound-absorbent enclosed racks (which they do make, though I didn’t get one; wasn’t willing to pay for it, as they come at a very large premium). They were one of the very few companies making them. I don’t think that those particular ones are the sound-absorbent models, but their name stuck in my head.

Old system 76 machine from a while back. Its what is running a majority of my services for self hosting. Only one screw keeps the case together, since I get into the insides quite often.

If you get bored and adventurous:

https://en.wikipedia.org/wiki/Computer_case_screws

Computer case screws are the hardware used to secure parts of a PC to the case. Although there are numerous manufacturers of computer cases, they have generally used three thread sizes.

The #6-32 UNC screws are often found on 3.5" hard disk drives and the case’s body to secure the covers. The M3 threaded holes are often found on 5.25" optical disc drives, 3.5" floppy drives, and 2.5" drives. Motherboards and other circuit boards often use a #6-32 UNC standoff. #4-40 UNC thumb screws are often found on the ends of DVI, VGA, serial and parallel connectors.

You might be able to get a box of thumbscrews in the appropriate diameter and go toolless. I’ve had a number of computer cases that ship with those (my current desktop case just uses magnets, doesn’t even have the thumbscrews). I have had a lot of less-than-ideal toolless things in the past, including poorly-designed toolless hard drive mounting stuff that wound up being a lot more work than the traditional tool-requiring stuff, but for the screws that keep the case closed, going toolless has always been a big win for me.

Re: the cabling up top there, there’s some Reddit subreddit devoted solely to people showing off their spiffy cable-routing.

searches

Might be:

https://old.reddit.com/r/CableManagement/top/?sort=top&t=all

Though that looks like in-PC-case cabling. I thought that it dealt more with network cables.

searches more

Ah. I think this:

https://old.reddit.com/r/cableporn/top/?sort=top&t=all

It looks like we do have a !cableporn@lemmy.world, but basically nobody is posting.

beverages

That desk is about a million times cleaner than mine.

¯_(ツ)_/¯

You want a double-backslash in Markdown.

¯\_(ツ)_/¯

yields

¯_(ツ)_/¯

Whereas:

¯\\_(ツ)_/¯

yields

¯\(ツ)/¯

Those HP Elitedesks are all over Amazon as refurbished machines. I was actually considering getting one earlier today for a server.

https://www.pcgamingwiki.com/wiki/List_of_games_that_support_PlayStation_light_bar

I probably wouldn’t use something specialized to home maintenance. Just any todo/task management system that lets you have a recurring task to tick off. There are tons of those out there.

Personally, I use repeated tasks in org-agenda in emacs for most of this, but I wouldn’t recommend picking up emacs simply to use org-agenda. But if you are an emacs user, then it might be a good option.

I haven’t used Taskwarrior myself, but I’ve seen a few people recommend it for Linux use, and if I weren’t using an emacs-oriented system, I’d probably look into it. It supports recurring tasks.

I’m waiting for release, myself, since I want to get the full experience all at once, so I’m not the best person to advise there.

I’d point out, for those not aware, that there’s a spiritual successor in the form of Kitten Space Agency.

Every time I get an Android update, my first reaction is “what workflows that had been working am I going to need to relearn?”

I’ve had some similar comments about Windows in the past. Like, a lot of the lock-in value that Microsoft enjoys isn’t anything special that they’ve done — it’s because people are expert in using their platform. If you make them change their workflow, you throw that out. And people profoundly dislike changing their workflow, once they’ve put the effort in to become accustomed to one.

Yes this works when I’m having issues.

Okay, gotcha. In that case, my guess is that the most-likely issue is with the DNS daemon that OpenWRT is using, which is most-likely dnsmasq.

You could confirm that your DNS configuration on the LAN hosts is actually using OpenWRT as the DNS server if you wanted — I could walk through that, if you’re not sure. But from a test-when-it’s-happening situation, I’d probably:

• Install dig on the Mint box, if it’s not already installed. That’s a DNS diagnostic program that doesn’t use your system resolving mechanism, talks directly to DNS, so it cuts out any other factors. It’ll be in the bind9-dnsutils package.

    $ sudo apt install bind9-dnsutils
  

• Install dig on the OpenWRT box.

    $ opkg update
    $ opkg install bind-dig
  

• Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems (your router’s LAN address probably being something like 192.168.1.1):

    $ dig @your-router-LAN-address www.google.com
  

• Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems using whatever outside DNS server you have the OpenWrt box set to use (assuming 1.1.1.1 here):

    $ dig @1.1.1.1 www.google.com
  

• Next time you have problems, repeat the above. If both the dig on your OpenWrt box and on your laptop using the OpenWrt DNS server now fail, then it’s probably pretty safe to say that it’s the DNS server on the OpenWrt box at fault. If just the one on your laptop fails, then it’s going to be a communication issue between your LAN box and the OpenWrt DNS server.

Assuming that the problem is the OpenWrt DNS server, and assuming that it’s dnsmasq, to troubleshoot further, I might try looking at its logs, or installing tcpdump on the OpenWrt box and running that, something like $ tcpdump -nvvv -i any udp port domain. That should let you see both the incoming DNS queries going to the OpenWrt DNS server as well as the queries that it is sending upstream (the -n will prevent tcpdump from itself sending DNS queries to look up IP addresses, which would generate more noise, the -vvv to show all possible information about the packets, and the -i any to show all packets on all interfaces). That’ll let you see whether it’s getting flooded with DNS queries and to see what queries it’s sending to the upstream DNS server out on the Internet.

That won’t alone solve your problem, but it’d be the next step I’d try to narrow down what’s going on.