Scott

Untrue. I work for a global enterprise company that transacts hundreds of millions of dollars via LE certs.

SELinux

The reason is “asymmetric routing”. The return ping packets are traveling a different route on the way out than on the way back.

https://immich.app/

https://gitlab.com/Nulide/findmydevice/-/wikis/FMD Server

The execute bit on directories allows for traversal of the directory (i.e. allows you to cd in), while the read bit allows for listing the directory contents (e.g. ls).

Have some commas, my man: ,

Jesus.

Try, https://www.amazon.com/Logitech-Vertical-Wireless-Mouse-Rechargeable/dp/B07FNJB8TT

It would mean you’re entrusting the entire security of your network to Dockge’s authentication system.

… and for that reason, I’m out.

Does for me.

I use Rallly.

Ahhh… very good. I avoided all this by running Pihole on its own IP on the LAN using a bridged interface from the host.

This post from Stack Exchange might help you, switching 80 for 53, of course.

You don’t need UDP on port 80 forwarded through. HTTP is TCP only.

Nextcloud does all of this.

Yes but it’s hard work.

I did it from the other side of the planet. I accidentally ran an rm -rf ... command on a running system. Luckily I had an identical system running that I could use to copy over the files, devices, etc.

Learning about inodes and /proc/xxx/fd works, I was able to recover enough files to then copy over the rest from the other system.

Doing it over SSH from the other side of the world was a tough 14 hours.

E2EE chat.

AudioBookshelf ticks all those requirements.

Third Room by matrix.org does all of this.

I’m wrong? You’re saying that IP addressing is one of the most complicated things about computers/networking?