deagle

Would it be possible to add SnapRAID? I managed to compile 11.5 on a Slackware VM a couple of years ago and copy the binary but I didn't document it and now I'm a few version behind. Thanks!

Unfortunately, my programming skills are limited. A simple Snapraid binary I can schedule would do the job for me. Also, is it possible to add Fish shell? Thanks.

I got PA-VM working with Q35-2.6, anything newer hangs at boot. PCI passthrough works as well, I used an old Intel quad PT and the interfaces are detected as e1000e. Looking to buy an ixgbe card for DPDK support. Something to keep in mind, only the first virtio interface (mgmt) was detected so you may need to passthough. I tried rebooting a couple of times and it wouldn't recognize the other virtio NICs. There may be a troubleshooting step I missed but I was going to passthough anyway so I skipped that part.

I edited the config file as follows and it works! Thanks. cipher aes-128-gcm auth sha256 ncp-disable

PA-VM supports CentOS so I'm optimistic. Has anyone gotten it working?

PIA now supports AES GCM. Is it possible to make that the default cypher? It's less than half the CPU cost, or double the bandwidth if you're maxing out one core. Thanks.

Snapraid please please. I'd love to have options to protect unassigned devices.

Thank you @Freddie @Benni-chan! When I first migrated to unRAID, even though I had researched split levels and set them up accordingly, rsync sprayed folders all over the array and the files ended up scattered. Finally fixed!

If you're running your own upstream DNS proxy and you only use DNS1, you set DNS2 to the same address or an update will set it to 8.8.4.4.

If you set both to the same IP in the docker template, the container start process stops with "upstream DSN error"

How do I prevent a container update from resetting my custom upstream DNS setting (internal router IP running Unbound)? I entered the IP in the template and I tried it three ways, with the second DNS server blank, repeating first IP, and deleting the variable. None worked ,the container started with an upstream DSN error and disabled the resolver and UI.

I would be happy to test Nvidia driver integration. HEVC is coming and my CPU is going to to hurt.

It's unlikely that a 1700 is double the single core performance of a 3.2GHz Sandy Bridge so would it be safe to assume AES-NI is working?

I just upgraded to gigabit internet and it turns out the openvpn process inside this container maxes out ~250 Mbit/s with 100% of one CPU core. When PIA starts supporting AES-GCM this should improve but in the meantime I'm inclined to upgrade to a CPU that supports AES-NI. OpenSSL 1.1.0e inside the container should automatically leverage AES-NI, can someone with AES-NI run a speed test and report back?

Wow that was fast. Thanks!