Changes

I strongly suggest you to use pi-imager and set ssh to use only your ssh key, set your keyboard, a password etc. You could do for the wifi, but suggest keeping the good old reliable cable.

I strongly suggest you to use pi-imager and set ssh to use only your ssh key, set your keyboard, a password etc. You could do for the wifi, but suggest keeping the good old reliable cable.

=== Configure a static IP ===

=== Configure a static IP ===

Initial logging in might be harder as you will need to find the IP of this new toy.  You could refer to dhcp logs or arp from your SME. Then I strongly suggest you to get the MAC address of the interfaces and use the server-manager to set a static IP for this host. You will need a static IP later to get this working. Also having an easy hostname to remember will help : pihole.mydomain.com

Initial logging in might be harder as you will need to find the IP of this new toy.  You could refer to dhcp logs or arp from your SME. Then I strongly suggest you to get the MAC address of the interfaces and use the server-manager to set a static IP for this host. You will need a static IP later to get this working. Also having an easy hostname to remember will help : pihole.mydomain.com

# Enable watchdog to send mails, whenever triggered:

# Enable watchdog to send mails, whenever triggered:

sudo apt-get -y install watchdog

sudo apt-get -y install watchdog

 

sudo sed -i -r 's/^#?max-load-5.*/max-load-5 = 18/' /etc/watchdog.conf

max-load-5 = 18

sudo sed -i -r 's/^#?max-load-15.*/max-load-15 = 12/' /etc/watchdog.conf

max-load-15 = 12

sudo sed -i -r 's/^#?watchdog-device.*/watchdog-device = \/dev\/watchdog/' /etc/watchdog.conf

watchdog-device = /dev/watchdog

sudo sed -i -r 's/^#?watchdog-timeout.*/watchdog-timeout = 15/' /etc/watchdog.conf

watchdog-timeout = 15

#use schedtools to optimize CPU for some process

#use schedtools to optimize CPU for some process

=== Tweak pihole using web interface ===

=== Tweak pihole using web interface ===

If you have windows machines that need updating , go to http://pi.hole and login.

If you have windows machines that need updating , go to http://pi.hole and login.

** you Primary domain.

** you Primary domain.

you might also read and apply some part of https://jpgpi250.github.io/piholemanual/doc/Block%20Ads%20Network-wide%20with%20A%20Raspberry%20Pi-hole.pdf

you might also read and apply some part of https://jpgpi250.github.io/piholemanual/doc/Block%20Ads%20Network-wide%20with%20A%20Raspberry%20Pi-hole.pdf

=== Setup your static IP machines to use ===

=== Setup your static IP machines to use ===

As explained, static ip machines that have their own network information set in their own configuration (not those that rely on dhcpd to address them and IP set on SME) have no idea of what idhcp is, and hence needs you to set the dns server with the ip of your pihole.

As explained, static ip machines that have their own network information set in their own configuration (not those that rely on dhcpd to address them and IP set on SME) have no idea of what dhcp is, and hence needs you to set the dns server with the ip of your pihole.

=== Setup SME firewall /router firewall to filter/redirect DNS request ===

=== Setup SME firewall /router firewall to filter/redirect DNS request ===

{{Note box|TODO}}

{{Note box|TODO - See Below - but note still under developement}}

== Why using SME Server as upstream server, and pihole only given by the dhcpd service to LAN ==

=== Why using SME Server as upstream server, and pihole only given by the dhcpd service to LAN ===

In other words, why not doing the opposite and set SME to rely on pihole?

In other words, why not doing the opposite and set SME to rely on pihole?

# you do not want to rely on an external DNS service pooling requests sending them to pihole, redirecting them to your local services. There are chances that DNSBL will fail with a result too many requests.

# you do not want to rely on an external DNS service pooling requests sending them to pihole, redirecting them to your local services. There are chances that DNSBL will fail with a result too many requests.

# you might want to be able to have some machines relying on SME result without pihole filtering.

# you might want to be able to have some machines relying on SME result without pihole filtering.

== References ==

== References ==