Popping their ears. I can “pop” my ears by opening my eustachian tubes on demand. I can even hold them open if I want to. Apparently a lot of people can’t do that.

Wonder if there’s any demand for guys with dad bod, large feet, and early signs of a receding hairline.

It’s not. It happened in 1988.

Bruh.

Ms Owens’ lawyers have responded to the Macrons’ lawsuit with a motion to dismiss, arguing that the case should not have been filed in Delaware, as she says it does not relate to her businesses, which are incorporated in the state. They claim forcing her to defend the case in Delaware would cause “substantial financial and operational hardship”.

It definitely relates to her businesses since her business is primarily manufacturing and spreading bullshit.

I’d like to learn to play the organ. I have an old Allen MOS-2 in my workshop that I started doing a MIDI conversion on and just haven’t had time to finish it.

Agreed. This whole lawsuit is one giant looming catastrophe. If ISP’s are found liable for copyright infringement, that will be the effective end of the open internet. From there, I can already see the argument taking shape that ISP’s, telco’s, and account holders are all effectively accomplices in all sorts of crimes facilitated using communications networks.

OK recording industry. Riddle me this. If you manage to cut off my internet access, how am I supposed to purchase your media?

In this situation it’s not necessarily that it’s the “right” or “wrong” device. The better question is, “does it meet your needs?” There are pros and cons to running each service in its own VM. One of the cons is the overhead consumed by the VM OS. Sometimes that’s a necessary sacrifice.

Some of the advantages of running a system like Proxmox are that it’s easily scalable and you’re not locked into specific hardware. If your current Beelink doesn’t prove to be enough, you can just add another one to the cluster or add a different host and Proxmox doesn’t care what it is.

TLDR: it’s adequate until it’s not. When it’s not, it’s an easy fix.

Yeah, with something that size you’re pretty much limited to containers.

Edit: Which is totally fine, OP. Self hosting is an opportunity to learn and your setup can be easily changed as your needs change over time.

I use one VM per service. WAN facing services, of which I only have a couple, are on a separate DMZ subnet and are firewalled off from the LAN.

It’s probably little overkill for a self hosted setup but I have enough server resources, experience, and paranoia to support it.

I have toddlers. I get told “no” all the time. Even when it doesn’t make any sense, which is most of the time.

Hope he likes expensive homeowners premiums. That’s what you get without a good local fire department.

@[email protected]

Why did you have to go and make this personal?

…Now where did the rest of those donuts go?

Not nearly as much as I once did. I quit dipping about 15 years ago and started drinking a lot less after getting diagnosed and medicated for ADHD.

I do enjoy a good cigar and a glass of Macallan occasionally but that’s too expensive to be a regular habit.

Lol that was not the Amazon guy. That was probably a cat that decided your planters were as good a port-a-potty as they were going to get in the moment.

I use Outlook for work and personal. I’ve gotten used to it and old habits die hard I guess.

The overall state of technology is actually pretty great. There’s just a few really shitty organizations that tend to dominate the headlines with their pump and dump schemes.

I want to make sure I understand your goal correctly. Here’s what I’m getting.

1. You have a wire guard connection that you want to use for outbound traffic from your local LAN.
2. You have a Debian box that serves at the client in this situation.

Here’s the part where I’m a little fuzzy

3. You want to connect to your local LAN using another wire guard connection and have WAN requests routed from clients connecting to your LAN (via wire guard) out the wire guard connection mentioned in #1.

Did I get any part of that wrong?

Edit: NVM. I saw your response to another comment that sounds like this is exactly what you want.

This should be achievable via routing. I actually do the same thing. The main difference is all the work is done on my router which handles both wire guard connections and routing.

At the minimim you’re going to need:

• A NAT rule on your local router to port forward incoming wire guard requests on the WAN to your Debian box. **Assuming the Debian box is also the wire guard server.
• An iptables DSTNAT rule on your Debian box to route local traffic to the LAN gateway.
• An iptables DSTNAT rule on your Debian box to route outbound WAN traffic that does NOT originate from your Debian box to the gateway at the other end of the outbound wire guard connection.