/explore
|
You are here 
|
operand.ca | ||
| | | | |
ketanvijayvargiya.com
|
|
| | | | | Vanilla installation # Setting up Pi-hole was really easy: https://docs.pi-hole.net/main/basic-install/ Docker, using macvlan #The following allows you to setup Pi-hole with a new dedicated IP address alongside other services that are already running on port 80 on your machine. version: '3.5' services: pihole: container_name: pihole image: pihole/pihole:latest cap_add: - NET_ADMIN networks: pihole_network: ipv4_address: 192.168.1.199 # New IP address that we'll assign to Pi-hole. ports: - 443/tcp - 53/tcp - 53/udp - 67/udp - 80/tcp environment: ServerIP: 192.168.1.199 TZ: 'America/Los_Angeles' WEBPASSWORD: "" volumes: - '/home/pi/docker-stuff/etc-pihole:/etc/pihole' - '/home/pi/docker-stuff/etc-dnsmasq.d:/etc/dnsmasq.d' restart: unless-stopped networks: piho... | |
| | | | |
vlad.website
|
|
| | | | | Yggdrasil allows you to easily set up a private virtual network based on IPv6. Your machines will then receive an IPv6 address such as 201:2af6:fcc4:30e7:b22d:15d6:a55d:10bb. However, that's not very fun to have to type, and it would be nicer to be able to refer to your machines by their hostnames, e.g. by doing ping apples and ping pears. I tried to do this in an intelligent way and failed, which led me to resort to setting up a local dnsmasq server to solve the problem. Still, I thought I'd write about my reasoning, since it could lead to a better solution in the future. | |
| | | | |
vincent.bernat.ch
|
|
| | | | | Implementation of redundant site-to-site VPNs on Linux with WireGuard (instead of IPsec) and BGP. | |
| | | | |
shibumi.dev
|
|
| | | How to setup wireguard with systemd-networkd | ||
