algo VS Pi-hole

Since we're already presuming you have a functional PFSense box with Wireguard installed and a VPS stood up, now you need to get Algo installed on the VPS. I'm not going to write this part out in detail, but basically you need to follow the procedures here to get Algo installed. However, *before* running ./algo you probably want to edit some of the config.cfg settings. I disabled IPSec (which saves a bunch of package installs and prevents a bunch of failures I saw on some of my VPSs), set my reduce_mtu setting to 80 just to prevent any MTU issues down the line, turned off DNS encryption, and renamed my users to the servers in question (for example: pfsense, vps_server, etc)

Check out the command line args for Auto1111, it talks about a gradio setup that can be accessed remotely. There's a time limit on gradio links though, I think. You could also set up a vpn that will allow you to access your PC remotely, then run A1111 with the --listen command and access it that way. I've done this with an Algo VPN on Azure and a Wireguard client for Windows for Android, but any VPN that lets you access your PC remotely would work.

One way you could try to get around is building your own VPN service, like this: https://github.com/trailofbits/algo/blob/master/README.md

Things I have tried so far: Clear network cache and reset adapters - IDK it fix aprevious problem I had https://github.com/trailofbits/algo/discussions/14504

(I can simply install Algo and get the Wireguard tunnel working, easy peasy... But from there, I can never get Plex port 32400 open... so I'm just trying from scratch now...)

Maybe try running algo vpn (following the road-warrior setup) in a VM instead? It has very light requirements. https://github.com/trailofbits/algo/blob/master/docs/deploy-to-ubuntu.md

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.

It's definitely not as simple as installing an app on your phone, but I run a Pi-hole on my home network, and it does block ads in many games.