wireguard-vyatta-ubnt VS docker-pihole-unbound

Joining serverless environments like AWS Lambda to a mesh network has traditionally been difficult because you can't directly access the network interfaces on the hosts that run your functions. The NetBird netstack mode addresses this by providing a simulated TUN device and a SOCKS5 proxy that targets that device. This allows your Lambda function to access other services in your NetBird network via the proxy.

NetBird simplifies Kubernetes access with its zero-configuration approach, leveraging WireGuard's simplicity and strength. It seamlessly integrates with various tools, offering transparency and high reliability as an open source solution.

WireGaurd

As for remote access, you will need another computer to install tailscale or wireguard vpn to access your local devices https://www.youtube.com/watch?v=AkKz7Vza1rw and the official docs for up to date advice https://www.wireguard.com/ this doesn't require much to run, you can use any old family computer or some old quad core 2nd-4th gen intel desktop for 30 bucks off facebook marketplace. You can also use that same computer to run klipper if you install proxmox and have two separate linux virtual machines.

Um modo mais avançado de se proteger é utilizando protocolos de VPN mais modernos, como o WireGuard. Muitos provedores de VPN oferecem suporte a este protocolo, que além de muito simples de usar e além do mais é open source.

here u find out how wireguard works https://www.wireguard.com/

WireGuard is a VPN protocol developed several years ago which is exremely fast, lightweight, and uses state-of-the art cryptography. Its performance blows legacy VPN's out of the water.

Try vanilla. It solved all my problems bar none.

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.