His marriage is fine. It's his own trauma that he's running from. That's why he spends his days fixing everything else and his nights playing dress-up and dolls.

Sometimes, less is more.

I would recommend trimming all your custom configuration from your router/firewall, one change at a time, until you can no longer reproduce the issue.

Or go the other way around: set up a barebones configuration, confirm the issue is resolved, and begin adding one customization at a time until it breaks.

How do your bufferbloat tests look?

https://www.waveform.com/tools/bufferbloat

It sounds like you have a lot of stateful inspection configured. YouTube's heavy usage of QUIC (i.e. UDP transport) may not play well with your config.

And, incidentally, what does your hardware look like?

Frankly, even the most barebones router should be able to handle YouTube. I am running pfSense in an ESXi VM, with passthru Intel gigabit NICs, 2 GB reserved RAM, and 2 vCPU (shared, but with higher priority than other VMs) on a Dell desktop with a second-gen i7 that was shipped from the factory in 2012.

Yes, I am routing on decade-old hardware. And I have never seen anything like what you are describing.

YouTube should "just work."

I am going to assume that if you're running OpenWRT, then you are probably using a typical consumer router? Please correct me if I am wrong.

Have you by any chance tried backing up your OpenWRT config and going back to stock firmware?

I know, I know, OpenWRT is great. I have a consumer router that I flashed with it to use strictly as a wireless AP.

But consumer devices flashed with vanilla OpenWRT tend to have very, very little resources left over to handle fun configurations.

And I have a feeling some of the fun configuration might be contributing to your issues.

At the risk of devolving into ad hominem...

I feel that Nintendo hasn't made a good Mario game since.. 3D world on the 3DS/wiiU and before that.. Mario Galexy and then.. since Paper Mario on the original Wii. those games were in my opinion the best of what Mario has to offer as it was originally intended. Fun, colorful cartoony, and exciteing.

...how old were you when those games were released?

We'll just ignore the fact that the other guy in that clip was one of the wormy dudes undercover

Cloud-init is fairly well documented:

https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html#nameservers-mapping

But if you do not need it (and if you're configuring DNS by hand, it doesn't sound like you do), you can disable it entirely:

https://cloudinit.readthedocs.io/en/latest/howto/disable_cloud_init.html

resolv.conf itself should be managed by systemd-resolved on any modern Ubuntu Server release. And that service will use the DNS settings provided by netplan.

With cloud-init disabled, you should have the freedom to create/edit configuration files in /etc/netplan and apply changes with netplan apply.

Citric acid as fabric softener.

Edit: Do NOT use with bleach!

They're the same picture

I paid $1 for Reddit Sync Pro and used it for hours a day for 13 years. In that time the developer provided dozens of updates, multiple major overhauls, and continual usage of functionality that requires the developer to pay ongoing API fees to provide.

Sync for Lemmy pricing is exactly as much as it should be.

100%

They almost undoubtedly would. That wasn't the problematic statement.

Let's go over some fundamentals here.

fsck is a utility for checking and repairing filesystem errors. Some filesystems do not support doing so when they are mounted.

Why? At a high level, because:

The utility needs the filesystem to be in a consistent state on disk. If the filesystem is mounted and in-use, that will not be so: The utility might come across data affected by an in-flight operation. In its state at that exact moment, the utility might think there is corruption and might attempt to repair it.

But in doing so, it might actually cause corruption once the in-flight operation is complete. That is because the mounted filesystem also expects the disks to be in a consistent state.

Some filesystems are designed to support online fsck. But for OP's purposes, I assume that the ones they are using are not so (hence the reason for the post).

"I know!" said the other commenter. "RAID uses mirroring! So why not just take the mirror offline and do it there?"

Well, for the exact same reasons as above, and then some additional ones.

Offlining a mirror like that while the filesystem is in use is still going to result in the data on the drive being in an inconsistent state. And then, as a bonus, if you tried to online it again, that puts the mirrors in an inconsistent state from each other too.

Even if you wanted to offline a mirror to check for errors, and even if you were doing a read-only check (thus not actually repairing any errors, thus not actually changing anything on that particular drive), and even if you didn't have to worry about the data on disk being inconsistent... The filesystem is in use. So data on the still-online drive has undoubtedly changed, meaning you can't just online the other one again (since they are now inconsistent from each other).

The employer basically gets an interest-free loan for that extra week; whereas the employee might need to pay interest to a third party to make up for any shortfall on their end (e.g. credit cards, payday loans). Majority of people live paycheck-to-paycheck and can't cover an unexpected $1000 expense.

It's a Heisenberg tradeoff. At a certain point you can either make them more impact resistant or more scratch resistant.