mirror of
https://github.com/pi-hole/docs.git
synced 2024-12-06 19:27:12 +01:00
Merge branch 'master' into tweak/moveloglocation
This commit is contained in:
yubiuser
GitHub
@@ -130,6 +130,8 @@ ID | Status | | Details
|
||||
12 | Allowed | ✅ | Retried query
|
||||
13 | Allowed | ✅ | Retried but ignored query (this may happen during ongoing DNSSEC validation)
|
||||
14 | Allowed | ✅ | Already forwarded, not forwarding again
|
||||
15 | Blocked | ❌ | Blocked (database is busy)<br> How these queries are handled can be [configured](../ftldns/configfile.md#reply_when_busy)
|
||||
16 | Blocked | ❌ | Blocked (special domain)<br>*E.g. Mozilla's canary domain and Apple's Private Relay domains* <br> Handling can be [configured](../ftldns/configfile.md)
|
||||
|
||||
### Supported reply types
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ By default, `FTL` determines the address of the interface a query arrived on and
|
||||
|
||||
Used to overwrite the IP address for blocked `AAAA` queries. See [`BLOCK_IPV4`](#block_ipv4) for details when this setting is used.
|
||||
|
||||
#### `REPLY_WHEN_BUSY=ALLOW|DROP|BLOCK|REFUSE` (PR [#1156](https://github.com/pi-hole/FTL/pull/1156)) {#reply_when_busy data-toc-label='Database busy reply'}
|
||||
#### `REPLY_WHEN_BUSY=DROP|ALLOW|BLOCK|REFUSE` (PR [#1156](https://github.com/pi-hole/FTL/pull/1156) & PR [#1341](https://github.com/pi-hole/FTL/pull/1341)) {#reply_when_busy data-toc-label='Database busy reply'}
|
||||
|
||||
When the gravity database is locked/busy, how should Pi-hole handle queries?
|
||||
|
||||
@@ -156,9 +156,9 @@ Controls whether and how FTL will reply with for address for which a local inter
|
||||
|
||||
Note about `HOSTNAMEFQDN`: If no local suffix has been defined, FTL appends the local domain `.no_fqdn_available`. In this case you should either add `domain=whatever.com` to a custom config file inside `/etc/dnsmasq.d/` (to set `whatever.com` as local domain) or use `domain=#` which will try to derive the local domain from `/etc/resolv.conf` (or whatever is set with `resolv-file`, when multiple `search` directives exist, the first one is used).
|
||||
|
||||
#### `DELAY_STARTUP=0` (PR [#716](https://github.com/pi-hole/FTL/pull/716)) {#delay_startup data-toc-label='Delay resolver startup'}
|
||||
#### `DELAY_STARTUP=0` (PR [#716](https://github.com/pi-hole/FTL/pull/716), PR [1349](https://github.com/pi-hole/FTL/pull/1349)) {#delay_startup data-toc-label='Delay resolver startup'}
|
||||
|
||||
In certain configurations, you may want FTL to wait a given amount of time before trying to start the DNS revolver. This is typically found when network interfaces appear only late during system startup and the interface startup priorities are configured incorrectly. This setting takes any integer value between 0 and 300 seconds.
|
||||
During startup, in some configurations, network interfaces appear only late during system startup and are not ready when FTL tries to bind to them. Therefore, you may want FTL to wait a given amount of time before trying to start the DNS revolver. This setting takes any integer value between 0 and 300 seconds. To prevent delayed startup while the system is already running and FTL is restarted, the delay only takes place within the first 60 seconds (hard-coded) after booting.
|
||||
|
||||
#### `NICE=-10` (PR [#798](https://github.com/pi-hole/FTL/pull/798)) {#nice data-toc-label='Set niceness'}
|
||||
|
||||
|
||||
@@ -247,4 +247,31 @@ Get the IP of the gateway of the default route and the corresponding interface
|
||||
|
||||
Note that if no non-default route could be found, `0.0.0.0` and an empty interface string is returned
|
||||
|
||||
---
|
||||
|
||||
#### `>interfaces` {data-toc-label='interfaces'}
|
||||
|
||||
Get extended information of the interfaces of th Pi-hole device
|
||||
|
||||
```text
|
||||
eth0 UP 1000 2.2GB 5.6GB 10.0.1.5 fd00:e57b:XXXX:210e:1a1,2a01:XXXX:c15b,fe80::2e5c:XXXX:4060
|
||||
wlan0 DOWN -1 0.0B 0.0B - -
|
||||
docker0 UP 10000 837.6MB 300.7MB 172.17.0.1,169.254.241.237 -
|
||||
lo UP -1 48.0MB 48.0MB 127.0.0.1 -
|
||||
wg0 UP -1 1.0GB 141.2MB 10.0.40.1 -
|
||||
sum UP 0 4.2GB 6.1GB - -
|
||||
```
|
||||
|
||||
Column definitions are:
|
||||
|
||||
1. Interface name
|
||||
2. UP/DOWN status
|
||||
3. Link speed in MBit/s (-1 means "Not available" (like link down) or "Not applicable" (like virtual interface))
|
||||
4. TX bytes
|
||||
5. RX bytes
|
||||
6. Associated IPv4 addresses
|
||||
7. Associated IPv6 addresses
|
||||
|
||||
The default interface (the one connected to the gateway) will always be the first. The sum will always be the last one - even if you have (for whatever reason) an interface called sum. Regarding the link speed: It won't work for most WiFi interfaces as the speed is not known at the kernel level. Instead, the drivers manage them dynamically depending on package loss, signal strength, etc. - in this case, you'll see link speed -1 as well
|
||||
|
||||
{!abbreviations.md!}
|
||||
|
||||
+1
-1
@@ -61,7 +61,7 @@ If requesting a lot of data from the long-term database you get this error
|
||||
```code
|
||||
An unknown error occurred while loading the data.
|
||||
|
||||
Check the server's log files (/var/log/lighttpd/error.log) for details.
|
||||
Check the server's log files (/var/log/lighttpd/error-pihole.log) for details.
|
||||
|
||||
You may need to increase PHP memory limit.
|
||||
|
||||
|
||||
@@ -24,10 +24,10 @@ The following operating systems are **officially** supported:
|
||||
|
||||
| Distribution | Release | Architecture |
|
||||
| ------------ | ---------------- | ------------------- |
|
||||
| Raspberry Pi OS <br>(formerly Raspbian) | Stretch / Buster / Bullseye | ARM |
|
||||
| Ubuntu | 16.x / 18.x / 20.x /21.x | ARM / x86_64 |
|
||||
| Debian | 9 / 10 /11 | ARM / x86_64 / i386 |
|
||||
| Fedora | 33 / 34 | ARM / x86_64 |
|
||||
| Raspberry Pi OS <br>(formerly Raspbian) | Buster / Bullseye | ARM |
|
||||
| Ubuntu | 18.x / 20.x / 22.x | ARM / x86_64 |
|
||||
| Debian | 10 /11 | ARM / x86_64 / i386 |
|
||||
| Fedora | 34 | ARM / x86_64 |
|
||||
| CentOS | 7 | x86_64 |
|
||||
| CentOS Stream | 8 | x86_64 |
|
||||
|
||||
|
||||
Generated
+954
-703
File diff suppressed because it is too large
Load Diff
+1
-1
@@ -22,7 +22,7 @@
|
||||
"test": "npm run markdownlint && npm run linkinator"
|
||||
},
|
||||
"devDependencies": {
|
||||
"linkinator": "^3.1.0",
|
||||
"linkinator": "^4.0.1",
|
||||
"markdownlint-cli2": "0.4.0"
|
||||
}
|
||||
}
|
||||
|
||||
+2
-2
@@ -1,5 +1,5 @@
|
||||
markdown-include==0.6.0
|
||||
mkdocs==1.3.0
|
||||
mkdocs-git-revision-date-localized-plugin==1.0.1
|
||||
mkdocs-material==8.3.8
|
||||
mkdocs-git-revision-date-localized-plugin==1.1.0
|
||||
mkdocs-material==8.3.9
|
||||
mkdocs-redirects==1.0.4
|
||||
|
||||
Reference in New Issue
Block a user