mirror of
https://github.com/pi-hole/docs.git
synced 2024-12-06 19:27:12 +01:00
Changed per Mcat12 requests.
Signed-off-by: Dan Schaper <dan.schaper@pi-hole.net>
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
###Hardware
|
||||
### Hardware
|
||||
Pi-hole is very lightweight, and does not require much processing power
|
||||
|
||||
- ~52MB of free space
|
||||
@@ -7,7 +7,7 @@ Pi-hole is very lightweight, and does not require much processing power
|
||||
Despite the name, you are not limited to running Pi-hole on a Raspberry Pi.
|
||||
Any hardware that runs one of the supported operating systems will do!
|
||||
|
||||
###Supported Operating Systems
|
||||
### Supported Operating Systems
|
||||
|
||||
The following operating systems are **officially** supported:
|
||||
|
||||
@@ -17,7 +17,7 @@ The following operating systems are **officially** supported:
|
||||
- Debian: 8 / 9
|
||||
- CentOS: 7 (not ARM)
|
||||
|
||||
###IP Addressing
|
||||
### IP Addressing
|
||||
|
||||
Pi-hole needs a static IP address to properly function (a DHCP reservation is just fine). Users may run into issues because **we currently install `dhcpcd5`, which may conflict with other running network managers** such as `dhclient`, `dhcpcd`, `networkmanager`, and `systemd-networkd`.
|
||||
|
||||
@@ -27,7 +27,7 @@ Please be aware of this fact because it [may cause confusion](https://github.com
|
||||
|
||||
Due to the complexity of different ways of setting an IP address across different systems, it's a slow process and [we need help](https://github.com/pi-hole/pi-hole/issues/629). If you're willing to contribute, please let us know.
|
||||
|
||||
###Ports
|
||||
### Ports
|
||||
|
||||
| Service | Port | Protocol | Notes |
|
||||
| --------------------|:-------|:------| --------------------|
|
||||
@@ -35,17 +35,17 @@ Due to the complexity of different ways of setting an IP address across differen
|
||||
| dnsmasq - DHCP | 67 | IPv4 UDP |The DHCP server is an optional feature that requires additional ports.|
|
||||
| dnsmasq - DHCPv6 | 547 | IPv6 UDP |The DHCP server is an optional feature that requires additional ports.|
|
||||
|lighttpd|80|TCP|If you have another Web server already running, such as Apache, Pi-hole's Web server will not work. You can either disable the other Web server or change the port on which `lighttpd` listens, which allows you keep both Web servers running.|
|
||||
|pihole-FTL | 4711| TCP |FTL is our API engine and by default uses port 4711, but will increment if it's already in use by something else.|
|
||||
|pihole-FTL | 4711:4720 | TCP |FTL is our API engine and by default uses port 4711, but will increment if it's already in use by something else.|
|
||||
|
||||
!!! info
|
||||
The use of lighttpd on port _80_ is optional if you decide not to install the Web dashboard during installation.
|
||||
The use of dnsmasq on ports _67_ or _547_ is optional and required if you use the DHCP functions of Pi-hole.
|
||||
The use of dnsmasq on ports _67_ or _547_ is optional, but required if you use the DHCP functions of Pi-hole.
|
||||
|
||||
###Firewalls
|
||||
### Firewalls
|
||||
|
||||
Below are some examples of firewall rules that will need to be set on your Pi-hole server in order to use the functions available. These are only shown as guides, the actual commands used will be found with your distributions documentation.
|
||||
|
||||
####IPTables
|
||||
#### IPTables
|
||||
|
||||
IPTables uses two sets of tables. One set is for IPv4 chains, and the second is for IPv6 chains. If only IPv4 blocking is used for the Pi-hole installation, only apply the rules for IP4Tables. Full Stack (IPv4 and IPv6) require both sets of rules to be applied. *Note: These examples insert the rules at the front of the chain. Please see your distributions documentation to see the exact proper command to use.*
|
||||
|
||||
@@ -64,7 +64,7 @@ IP6Tables (IPv6)
|
||||
```bash
|
||||
ip6tables -I INPUT -p udp -m udp --sport 546:547 --dport 546:547 -j ACCEPT
|
||||
```
|
||||
####FirewallD
|
||||
#### FirewallD
|
||||
|
||||
<TODO: Explain how to use FTLDNS with firewall-cmd>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user