Wireguard + Pi-hole DNS broken on GL.iNet router

This page summarizes the projects mentioned and recommended in the original post on /r/WireGuard

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • docker-wireguard

    version: "2.1" networks: backend: driver: bridge ipam: config: - subnet: "172.19.0.0/24" services: wireguard: image: lscr.io/linuxserver/wireguard:1.0.20210914 container_name: wireguard cap_add: - NET_ADMIN - SYS_MODULE environment: - PUID=1000 - PGID=1000 - TZ=America/New_York - SERVERURL=redacted.duckdns.org #optional - SERVERPORT=51820 #optional - PEERS=redacted #optional - PEERDNS=auto #optional - INTERNAL_SUBNET=10.13.13.0 #optional - ALLOWEDIPS=192.168.4.0/24, 10.13.13.1 # this allows for split tunneling volumes: - /home/redacted/docker_data/wireguard/config:/config - /lib/modules:/lib/modules ports: - 51820:51820/udp sysctls: - net.ipv4.conf.all.src_valid_mark=1 # https://github.com/linuxserver/docker-wireguard/issues/106 dns: # https://github.com/linuxserver/docker-wireguard/issues/106 - 172.19.0.10 networks: backend: ipv4_address: 172.19.0.11 restart: unless-stopped pihole: container_name: pihole image: pihole/pihole:2022.02.1 # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" # - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/New_York' WEBPASSWORD: redacted # Volumes store your data between container upgrades volumes: - /home/redacted/docker_data/pihole/pihole:/etc/pihole # - /home/redacted/docker_data/pihole/resolv.conf:/etc/resolv.conf - /home/redacted/docker_data/pihole/dnsmasq.d:/etc/dnsmasq.d # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities # cap_add: # - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/linuxserver/docker-wireguard/issues/106 dns: - 127.0.0.1 networks: backend: # https://github.com/linuxserver/docker-wireguard/issues/106 ipv4_address: 172.19.0.10 restart: unless-stopped

  • docker-pi-hole

    Pi-hole in a docker container

    version: "2.1" networks: backend: driver: bridge ipam: config: - subnet: "172.19.0.0/24" services: wireguard: image: lscr.io/linuxserver/wireguard:1.0.20210914 container_name: wireguard cap_add: - NET_ADMIN - SYS_MODULE environment: - PUID=1000 - PGID=1000 - TZ=America/New_York - SERVERURL=redacted.duckdns.org #optional - SERVERPORT=51820 #optional - PEERS=redacted #optional - PEERDNS=auto #optional - INTERNAL_SUBNET=10.13.13.0 #optional - ALLOWEDIPS=192.168.4.0/24, 10.13.13.1 # this allows for split tunneling volumes: - /home/redacted/docker_data/wireguard/config:/config - /lib/modules:/lib/modules ports: - 51820:51820/udp sysctls: - net.ipv4.conf.all.src_valid_mark=1 # https://github.com/linuxserver/docker-wireguard/issues/106 dns: # https://github.com/linuxserver/docker-wireguard/issues/106 - 172.19.0.10 networks: backend: ipv4_address: 172.19.0.11 restart: unless-stopped pihole: container_name: pihole image: pihole/pihole:2022.02.1 # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" # - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/New_York' WEBPASSWORD: redacted # Volumes store your data between container upgrades volumes: - /home/redacted/docker_data/pihole/pihole:/etc/pihole # - /home/redacted/docker_data/pihole/resolv.conf:/etc/resolv.conf - /home/redacted/docker_data/pihole/dnsmasq.d:/etc/dnsmasq.d # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities # cap_add: # - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/linuxserver/docker-wireguard/issues/106 dns: - 127.0.0.1 networks: backend: # https://github.com/linuxserver/docker-wireguard/issues/106 ipv4_address: 172.19.0.10 restart: unless-stopped

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts