2024-06-03

2024-06-03 07:04:29 -07:00
commit a6071a4073
273 changed files with 16707 additions and 0 deletions
--- a/_-Review/pi-hole.md
+++ b/_-Review/pi-hole.md
@ -0,0 +1,169 @@
+---
+type: "topic"
+created: "2024-01-06T01:25:36.138Z"
+updated: "2024-04-11T04:33:41.638Z"
+---
+
+# Linux Pi Hole
+
+[Ubuntu](ubuntu.md)
+
+- [ ] Static IP
+- [ ] SSL Certificates
+- [ ] Nginx
+- [ ] ufw
+
+```bash
+# https://canyoublockit.com/
+curl -sSL https://install.pi-hole.net | bash
+192.168.0.73
+pihole -a -p 4hink
+apt install unbound
+# https://docs.pi-hole.net/guides/dns/unbound/
+nano /etc/unbound/unbound.conf.d/pi-hole.conf
+```
+
+```conf
+server:
+    # If no logfile is specified, syslog is used
+    # logfile: "/var/log/unbound/unbound.log"
+    verbosity: 0
+
+    interface: 127.0.0.1
+    port: 5335
+    do-ip4: yes
+    do-udp: yes
+    do-tcp: yes
+
+    # May be set to yes if you have IPv6 connectivity
+    do-ip6: no
+
+    # You want to leave this to no unless you have *native* IPv6. With 6to4 and
+    # Terredo tunnels your web browser should favor IPv4 for the same reasons
+    prefer-ip6: no
+
+    # Use this only when you downloaded the list of primary root servers!
+    # If you use the default dns-root-data package, unbound will find it automatically
+    #root-hints: "/var/lib/unbound/root.hints"
+
+    # Trust glue only if it is within the server's authority
+    harden-glue: yes
+
+    # Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
+    harden-dnssec-stripped: yes
+
+    # Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
+    # see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
+    use-caps-for-id: no
+
+    # Reduce EDNS reassembly buffer size.
+    # IP fragmentation is unreliable on the Internet today, and can cause
+    # transmission failures when large DNS messages are sent via UDP. Even
+    # when fragmentation does work, it may not be secure; it is theoretically
+    # possible to spoof parts of a fragmented DNS message, without easy
+    # detection at the receiving end. Recently, there was an excellent study
+    # >>> Defragmenting DNS - Determining the optimal maximum UDP response size for DNS <<<
+    # by Axel Koolhaas, and Tjeerd Slokker (https://indico.dns-oarc.net/event/36/contributions/776/)
+    # in collaboration with NLnet Labs explored DNS using real world data from the
+    # the RIPE Atlas probes and the researchers suggested different values for
+    # IPv4 and IPv6 and in different scenarios. They advise that servers should
+    # be configured to limit DNS messages sent over UDP to a size that will not
+    # trigger fragmentation on typical network links. DNS servers can switch
+    # from UDP to TCP when a DNS response is too big to fit in this limited
+    # buffer size. This value has also been suggested in DNS Flag Day 2020.
+    edns-buffer-size: 1232
+
+    # Perform prefetching of close to expired message cache entries
+    # This only applies to domains that have been frequently queried
+    prefetch: yes
+
+    # One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine, it should be unnecessary to seek performance enhancement by increasing num-threads above 1.
+    num-threads: 1
+
+    # Ensure kernel buffer is large enough to not lose messages in traffic spikes
+    so-rcvbuf: 1m
+
+    # Ensure privacy of local IP ranges
+    private-address: 192.168.0.0/16
+    private-address: 169.254.0.0/16
+    private-address: 172.16.0.0/12
+    private-address: 10.0.0.0/8
+    private-address: fd00::/8
+    private-address: fe80::/10
+```
+
+```bash
+service unbound restart
+# Disable Forwarding DNS in PiHole
+# Set Custom DNS in PiHole - 127.0.0.1#5335
+
+# And you're done! Bonus points for sending all DNS traffic through a VPN Gateway to encrypt all outbound requests - https://youtu.be/xFficDCEv3c
+
+pihole -up
+```
+
+```bash
+nano /etc/lighttpd/lighttpd.conf
+```
+
+```conf
+...
+server.port = 8005
+...
+```
+
+```bash
+service lighttpd restart
+```
+
+```bash
+# https://www.kali.org/docs/installation/network-pxe/
+# https://discourse.pi-hole.net/t/setting-up-a-pxe-boot-server-with-docker-compose-and-boot-kali-linux-or-other-oss/50218
+cd /etc/dnsmasq.d/
+touch /etc/dnsmasq.d/99-pxeboot.conf && nano /etc/dnsmasq.d/99-pxeboot.conf
+```
+
+```conf kali
+dhcp-boot=pxelinux.0
+enable-tftp
+tftp-root=/tftpboot/
+pxe-prompt="Press F8 for menu.", 60
+pxe-service=x86PC,"Boot from local disk",0
+pxe-service=x86PC,"Boot Kali Linux",kali/pxelinux
+```
+
+```conf Ignore
+dhcp-option=66,"192.168.0.2"
+dhcp-boot=pxelinux.0,,192.168.0.2
+```
+
+```bash
+mkdir /tftpboot
+mkdir /tftpboot/kali
+cd /tftpboot/kali
+wget http://http.kali.org/kali/dists/kali-rolling/main/installer-amd64/current/images/netboot/netboot.tar.gz
+tar -zxpf netboot.tar.gz
+rm netboot.tar.gz
+```
+
+```bash
+pihole restartdns
+pihole status
+```
+
+```bash
+pihole-FTL dhcp-discover
+apt-get install nmap
+nmap -n -sU -p67 --script broadcast-dhcp-discover
+```
+
+```bash
+# https://fuzzthepiguy.tech/adtest/
+nano /etc/dnsmasq.d/04-pihole-static-dhcp.conf
+service unbound-resolvconf status
+```
+
+```bash
+# https://serverfault.com/questions/1069459/configuration-on-nginx-for-nextcloud-and-pi-hole
+links https://phares3757.ddns.net/dhcp.leases
+```