openvpn-install VS Pi-hole

https://github.com/angristan/openvpn-install or if you want to be free from your distro's OpenSSL version: https://github.com/ix-ai/openvpn (recommended, just rebuild the container if it becomes outdated)

Buy your own cloud server and run https://github.com/angristan/openvpn-install to make it TCP over 443

Hey! I set up an OpenVPN Server on an Ubuntu Server VM inside ESXi 6.7 using this script: https://github.com/angristan/openvpn-install I need to access the local services running on the, e.g. 192.168.xxx.xxx, which works just fine. But I dont want all my network traffic being routed through the VPN Server. So if i reach out to 192.168.xxx.xxx I get the Service running on this IP in the local network where the server is in, but if I try to reach e.g. google.com the request does not get routed through the VPN. How can I achieve this? OpenVPN-Host: Ubuntu Server 22.04.3 LTS | OpenVPN 2.5.5 Connecting Client: EndeavourOS | OpenVPN 2.6.6

EDIT: I should add that the setup was done with angristan's OpenVPN installer. There's nothing particularly interesting about the conf files.

Very good, does it support https://github.com/angristan/openvpn-install ?

Pretty trivial actually. I set up my server on a VPS with https://github.com/angristan/openvpn-install, it generates the configs that I deployed to my devices, and when connected they can see each other. For resolving the domain name you'd need to set up the DNS during the wizard.

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.