Due to time and energy i tend to an out of the box, non OSS solution.
Why not both? OPNsense and pfSense both sell official hardware.
Both are pretty easy to configure but have pretty much no limit on how deep you can go.
Unifi works great as well but you hit a ceiling fairly quickly if it needs to do anything advanced.
Anything interesting going on in the kernel log while connection doesn't work?
If so, you could maybe write a bug report at the amdgpu repo.
One thing I could imagine that is happening is that Linux chooses a higher chroma subsampling than on Windows. Had that issue before with a monitor that had a wrong EDID. Unfortunately it's a real pain to set the chroma subsampling on Linux with AMD.
That's strange, 6.6.14 is the same version that's on Fedora currently. My friend with a 7900 XTX is still on 6.5.0 so I can't get him to test that version right now.
Fix is merged already though: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c2f0338bbd132a4b12b988004d796798609d297 Should hopefully not be long before it is backported.
Having a bleeding edge kernel can and will come back to bite you. There's a reason why many distros hold back with kernel updates for so long, there's issues that only can be found with user feedback.
From experience, "stable" in the kernel world doesn't mean much unfortunately. I encountered dozens of issues over various versions and different hardware already and it's the main reason I don't run rolling release distros on my main rig.
There's also been enough times where the latest Nvidia driver borked my test system at work so I'm fine with just not running the latest kernel instead.
Over DisplayPort? That's interesting, I knew AMD can't do HDMI 2.0 but there shouldn't be a problem with DP.
Might wanna try a proper new certified DP 2.1 cable, just to be safe.
I "only" drive a AW3423DW but no issues at 3440x1440 with 165Hz.
Since people normally only report on negative experiences: I was lucky enough to get a reference AMD 6900 XT during the GPU shortages.
Switched from Ubuntu to Fedora for it because Ubuntu didn't have firmware for it yet.
Ever since then it has been a rock solid GPU. Never even had such a stable GPU under Windows.
Have been running Fedora with Wayland for more than 2 years now and can count the crashes on a single hand, most were my fault.
I'm sure once that issue is sorted out that GPU is going to ride along for years with minimal maintenance required.
(You might want to downgrade your kernel until then though)
I would not depend on DNS records being private. On the off chance that one of the nameservers messes up, I would prefer if no subdomains are leaked.
But you're correct, most of the time those leaks happen somewhere else.
You can avoid these scans by only using wildcards on your DNS entries and SSL certificates.
Both of these are commonly used by bots to find new domains.
Will have to try that, also a good way to one-up my neighbor with those CDs hanging outside. :)
Already have a few of those, always a good party gag for the ones that know.
Yes, I've got quite a few types, good idea.
Yes, I run two instances of Radarr and Sonarr. One caps out at 1080p, the other one only allows 2160p.
Jellyfin just has two separate libraries for them.
I'm mostly doing this to prevent unecessary transcoding away from home where streaming 4k HDR is unlikely. At some point I will merge them but bandwidth for 4k streaming is not there yet and proper HDR tone mapping is still rare.