From bc27773de60e44866940179756ca88d5a4bd7ce4 Mon Sep 17 00:00:00 2001 From: XhmikosR Date: Tue, 4 Mar 2025 08:23:56 +0200 Subject: [PATCH] Remove extra newlines Signed-off-by: XhmikosR --- docs/docker/configuration.md | 1 - docs/docker/upgrading/v5-v6.md | 2 -- docs/group_management/example.md | 3 --- docs/guides/dns/cloudflared.md | 1 - docs/guides/dns/unbound.md | 2 -- docs/routers/OPNsense.md | 2 -- docs/routers/fritzbox.md | 2 -- 7 files changed, 13 deletions(-) diff --git a/docs/docker/configuration.md b/docs/docker/configuration.md index 90c4553..d8b4de8 100644 --- a/docs/docker/configuration.md +++ b/docs/docker/configuration.md @@ -38,7 +38,6 @@ Array type configs should be delimited with `;` !!! note All FTL settings that are set via environment variables effectively become read-only, meaning that you will not be able to change them via the web interface or CLI. This is to ensure a "single source of truth" on the config. If you later unset or remove an environment variable, then FTL will revert to the default value for that setting - An example of how some of these variables may look in your compose file ```yaml diff --git a/docs/docker/upgrading/v5-v6.md b/docs/docker/upgrading/v5-v6.md index b2ae5e2..b1e0934 100644 --- a/docs/docker/upgrading/v5-v6.md +++ b/docs/docker/upgrading/v5-v6.md @@ -65,10 +65,8 @@ By default, Pi-hole v6 no longer reads configuration files from `/etc/dnsmasq.d/ 1. Mount the local folder containing the config files into `/etc/dnsmasq.d` into the container 2. Set the environment variable `FTLCONF_misc_etc_dnsmasq_d: 'true'` - If you only want to add a single/few `dnsmasq` config lines you can use the variable `FTLCONF_misc_dnsmasq_lines`. Each line should be separated with `;` - ### Removed Variables The following variables can be removed without replacement, as they are no longer used: diff --git a/docs/group_management/example.md b/docs/group_management/example.md index e77f7ee..183b3cb 100644 --- a/docs/group_management/example.md +++ b/docs/group_management/example.md @@ -69,7 +69,6 @@ Client | Group membership | Domain | Blocked 192.168.0.102 | Group 2 + Default | doubleclick.net | Yes 192.168.0.103 | Group 3 + Default | doubleclick.net | Yes - All three clients got automatically assigned to the default (`Default`) group when they were added. The default group includes all subscribed lists and list domains (if not already changed by the user). When we remove the default group for client `192.168.0.101`, we effectively remove all associations to any subscribed lists and domains. This leaves this client completely unblocked. ## Example 2: Blocklist management @@ -92,7 +91,6 @@ Client | Group membership | Domain | Blocked 192.168.0.102 | Group 2 + Default | doubleclick.net | Yes 192.168.0.103 | Group 3 + Default | doubleclick.net | Yes - `192.168.0.101` gets `doubleclick.net` blocked as it uses a subscribed list including this domain. All other clients stay unchanged. ## Example 3: Denylisting @@ -121,7 +119,6 @@ Client | Group membership | Domain | Blocked 192.168.0.102 | Group 2 + Default | denylisted.com | **Yes** 192.168.0.103 | Group 3 + Default | denylisted.com | **Yes** - Note that Pi-hole is *not* blocking this domain for client `192.168.0.101` as we removed the default assignment through group 0 above. All remaining clients are linked through the Default group to this domain and see it as being blocked. ### Step 2 diff --git a/docs/guides/dns/cloudflared.md b/docs/guides/dns/cloudflared.md index 05e1f07..fcc0848 100644 --- a/docs/guides/dns/cloudflared.md +++ b/docs/guides/dns/cloudflared.md @@ -84,7 +84,6 @@ Edit configuration file by copying the following in to `/etc/default/cloudflared CLOUDFLARED_OPTS=--port 5053 --upstream https://cloudflare-dns.com/dns-query ``` - !!! info See the other available [Cloudflare endpoints](https://developers.cloudflare.com/1.1.1.1/infrastructure/network-operators/#available-endpoints). diff --git a/docs/guides/dns/unbound.md b/docs/guides/dns/unbound.md index f5829b3..7f222ee 100644 --- a/docs/guides/dns/unbound.md +++ b/docs/guides/dns/unbound.md @@ -193,7 +193,6 @@ To disable the service, run the statement below: sudo systemctl disable --now unbound-resolvconf.service ``` - #### Step 2 - Disable the file resolvconf_resolvers.conf Disable the file resolvconf_resolvers.conf from being generated when resolvconf is invoked elsewhere. @@ -263,7 +262,6 @@ Lastly, restart unbound: sudo service unbound restart ``` - ### Uninstall `unbound` To remove `unbound` from your system run diff --git a/docs/routers/OPNsense.md b/docs/routers/OPNsense.md index c9d4309..e0998b6 100644 --- a/docs/routers/OPNsense.md +++ b/docs/routers/OPNsense.md @@ -41,7 +41,6 @@ Leave the second line blank unless you have another Pi-hole host running. #### IPv6 - Go to **Interfaces** and click on the interface that you want to modify. Under **Manual configuration** check "Allow manual adjustment of DHCPv6 and Router Advertisements" @@ -55,7 +54,6 @@ Leave the second line blank unless you have another Pi-hole host running. Beware: Link local IPv6 are not reachable from other VLANs. - All client devices on your network should now automatically be configured with a single IPv4 and single IPv6 address for DNS resolution. If you don't see your client devices update quickly enough, you *can* toggle Wi-Fi off/on or disconnect the Ethernet cable for a couple of seconds and then reconnect it. ### Method 2: Using your Pi-hole as DNS server for your OPNsense diff --git a/docs/routers/fritzbox.md b/docs/routers/fritzbox.md index 4b54aec..5a60af1 100644 --- a/docs/routers/fritzbox.md +++ b/docs/routers/fritzbox.md @@ -35,7 +35,6 @@ Home Network/Network/Network Settings/IP Addresses/IPv4 Configuration/Home Netwo Now you should see individual clients in Pi-hole's web dashboard. - ## Pi-hole as upstream DNS server for your Fritz!Box With this configuration, Pi-hole is also used by the Fritz!Box itself as an upstream DNS server. DNS queries take the following path @@ -153,7 +152,6 @@ Source port: any Destination port: 53 ``` - This entry can then be added under ```plain