Pihole lost its static IP adress - not reachable anymore

[flex-0]

Hey guys, I have no clue whats going in here. I'm using pihole as dhcp, DNS and of course for adblocking. Its a pi3b with debian latest (i think bullseye).

Everything was working well till now, when suddenly all of my devices lost internet connection. At first I thought it would probably be my provider due to maintanence or an error but my fritzbox showed internet access was just fine.

So i tried the pihole web admin panel but getting an error. I tried to SSH but not cli statet not reachable. Pinged the IP, 100% package loss. So I restarted the pi (old windows trick ) but nothing changed either. Lastly I pluged in a screen and keyboard and restarted it again. Its booting, I can login and try:

ip a s

And it seems my pihole has no ipv4

I have no idea what to do, or even where to start. Could you provide some help?

Thanks in advance
flex0

[MichaIng]

How did you setup the static IP in the first place? Did you use dhcpcd as shipped with the RPi OS images or ifupdown resp. /etc/network/interfaces as used on Debian images by default?

Assuming the first one, please check the logs of dhcpcd:

journalctl -u dhcpcd

[deHakkelaar]

@MichaIng beat me to it but here is mine anyway:

You could temprarely assign/add an IP manually until get it fixed permanently/reboot persistent.
And can even install a default route if want the host to be able to connect to the Internet.
That way you can SSH in again.
Example below:

Running Pi-hole on Linux Router (RPi)

Try to use the current toolstack (iproute2) and dont use the depreciated ifconfig & route commands. To list all IPv4 addresses: ip -4 address Or shorter: ip -4 a Or less verbose: ip -br -4 a Or for a particular <INTERFACE_NAME> (the s argument for show): ip -br -4 a s <INTERFACE_NAME> List IPv4 routes: ip -4 r To isolate showing only the default route(s) (the s argument for show): ip -4 r s default To add an IP to an interface (a argument for add): sudo ip a a <IP_ADDRESS>/<MASK> d…

When can SSH in again, post results for below ones here pls?

journalctl --full -u dhcpcd | tail -50

grep -v '^#\|^$' /etc/dhcpcd.conf

[flex-0]

Hey there,

log was empty.

I could bring the adminpanel back online ( but only for a short time) with ‘ip addr add 192.168.X.X/24 dev eth0’

Also /etc/network/interfaces eth0 was on

auto eth0
iface eth0 inet dhcp
iface eth0 inet6 auto

which I changed to (according to my network)

auto eth0
iface eth0 inet static
address <IP in CIDR format, eg 10.0.0.53/24>
gateway

but after a restart everything is gone and i cant bring it back online. But I created a log. Is there anyway to upload it manualy?

[deHakkelaar]

@flex-0

Also /etc/network/interfaces eth0 was on

auto eth0
iface eth0 inet dhcp
iface eth0 inet6 auto

Whats your OS?

lsb_release -d

Network settings for Pi-OS/Raspbian should not be configured in /etc/network/interfaces but instead in the dhcpcd.conf file:

pi@ph5b:~ $ tail /etc/dhcpcd.conf
[..]
interface eth0
  static ip_address=10.0.0.4/24
  static routers=10.0.0.1
  static domain_name=home.dehakkelaar.nl
  static domain_name_servers=10.0.0.1

[deHakkelaar]

@flex-0

But I created a log. Is there anyway to upload it manualy?

Copy/paste only the relevant bits to here.
And enclose/highlight the log output with the </> button before replying.

[flex-0]

lsb_release -d is an unknown comand. Its debian I think bullseye or one prior.

[deHakkelaar]

cat /etc/os-release

cat /etc/debian_version

cat /etc/issue

?

Below if dont use dhcpcd but ifupdown instead.
Not sure if it shows more details but could try:

journalctl --full -u networking.service

[flex-0]

Hard to say whats important for me, so if you miss anything just say so:

*** [ DIAGNOSING ]: Network interfaces and addresses
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
       inet 127.0.0.1/8 scope host lo
          valid_lft forever preferred_lft forever
       inet6 ::1/128 scope host 
          valid_lft forever preferred_lft forever
   2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
       link/ether b8:27:eb:a2:5f:22 brd ff:ff:ff:ff:ff:ff
       inet 192.168.178.5/24 scope global eth0
          valid_lft forever preferred_lft forever
       inet6 2a02:8070:d186:d420:ba27:ebff:fea2:5f22/64 scope global dynamic mngtmpaddr 
          valid_lft 6974sec preferred_lft 3374sec
       inet6 fe80::ba27:ebff:fea2:5f22/64 scope link 
          valid_lft forever preferred_lft forever
   3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
       link/ether b8:27:eb:f7:0a:77 brd ff:ff:ff:ff:ff:ff

*** [ DIAGNOSING ]: Network routing table
   192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.5 

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    192.168.178.5/24

[✓] IPv6 address(es) bound to the eth0 interface:
    2a02:8070:d186:d420:ba27:ebff:fea2:5f22/64
    fe80::ba27:ebff:fea2:5f22/64

[i] Default IPv6 gateway: fe80::464e:6dff:fe9d:293a
   * Pinging fe80::464e:6dff:fe9d:293a...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
    udp:0.0.0.0:67 is in use by pihole-FTL
    udp:0.0.0.0:68 is in use by dhclient
[✓] udp:[::]:53 is in use by pihole-FTL
[✓] tcp:0.0.0.0:80 is in use by lighttpd
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
    tcp:0.0.0.0:22 is in use by sshd
[✓] tcp:127.0.0.1:4711 is in use by pihole-FTL
[✓] tcp:[::]:80 is in use by lighttpd
[✓] tcp:[::]:53 is in use by pihole-FTL
    tcp:[::]:22 is in use by sshd
[✓] tcp:[::1]:4711 is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] fbprogram-usa-votecontestsiteorgnet.000webhostapp.com is 0.0.0.0 on lo (127.0.0.1)
[✓] fbprogram-usa-votecontestsiteorgnet.000webhostapp.com is 0.0.0.0 on eth0 (192.168.178.5)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] a4589.casalemedia.com is :: on lo (::1)
[✓] a4589.casalemedia.com is :: on eth0 (2a02:8070:d186:d420:ba27:ebff:fea2:5f22)
[✓] a4589.casalemedia.com is :: on eth0 (fe80::ba27:ebff:fea2:5f22)
[✓] doubleclick.com is 2a00:1450:4016:80b::200e via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   * Received 303 bytes from eth0:192.168.178.5
     Offered IP address: 192.168.178.207
     Server IP address: 192.168.178.5
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.178.5
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.178.255
      dns-server: 192.168.178.5
      domain-name: "flexh0.me"
      router: 192.168.178.1
      --- end of options ---
    
   DHCP packets received on interface wlan0: 0
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 1

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Pi-hole-FTL full status
   ● pihole-FTL.service - LSB: pihole-FTL daemon
     Loaded: loaded (/etc/init.d/pihole-FTL; generated)
     Active: active (exited) since Mon 2022-08-15 17:58:46 CEST; 24min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 1094 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
        CPU: 103ms

Aug 15 17:58:44 rpi3-20220120 systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 15 17:58:44 rpi3-20220120 pihole-FTL[1094]: Not running
Aug 15 17:58:45 rpi3-20220120 su[1114]: (to pihole) root on none
Aug 15 17:58:45 rpi3-20220120 su[1114]: pam_unix(su:session): session opened for user pihole(uid=998) by (uid=0)
Aug 15 17:58:46 rpi3-20220120 systemd[1]: Started LSB: pihole-FTL daemon.

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.178.5/16
    PIHOLE_DNS_1=5.1.66.255
    PIHOLE_DNS_2=91.239.100.100
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    CACHE_SIZE=10000
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSMASQ_LISTENING=local
    BLOCKING_ENABLED=true
    DHCP_ACTIVE=true
    DHCP_START=192.168.178.151
    DHCP_END=192.168.178.251
    DHCP_ROUTER=192.168.178.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=flexh0.me
    DHCP_IPv6=false
    DHCP_rapid_commit=true

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Mon, 15 Aug 2022 16:23:02 GMT
Cache-Control: max-age=0
Date: Mon, 15 Aug 2022 16:23:02 GMT
Server: lighttpd/1.4.59

*** [ DIAGNOSING ]: Pi-hole log
-rw-r----- 1 pihole pihole 8.1M Aug 15 18:23 /var/log/pihole/pihole.log
   -----head of pihole.log------
   Aug 15 00:00:04 dnsmasq[55217]: query[A] discord.com from 192.168.178.21
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is 162.159.135.232
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is 162.159.138.232
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is 162.159.137.232
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is 162.159.136.232
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is 162.159.128.233
   Aug 15 00:00:04 dnsmasq[55217]: query[AAAA] discord.com from 192.168.178.21
   Aug 15 00:00:04 dnsmasq[55217]: cached discord.com is NODATA-IPv6
   Aug 15 00:00:04 dnsmasq[55217]: query[A] epdg.epc.mnc002.mcc262.pub.3gppnetwork.org from 192.168.178.44
   Aug 15 00:00:04 dnsmasq[55217]: forwarded epdg.epc.mnc002.mcc262.pub.3gppnetwork.org to 5.1.66.255
   Aug 15 00:00:04 dnsmasq[55217]: reply epdg.epc.mnc002.mcc262.pub.3gppnetwork.org is <CNAME>
   Aug 15 00:00:04 dnsmasq[55217]: reply epdg.epc.drz1.vodafone-ip.de is 139.7.117.169
   Aug 15 00:00:04 dnsmasq[55217]: reply epdg.epc.drz1.vodafone-ip.de is 139.7.117.168
   Aug 15 00:00:07 dnsmasq[55217]: query[A] epdg.epc.mnc002.mcc262.pub.3gppnetwork.org from 192.168.178.44
   Aug 15 00:00:07 dnsmasq[55217]: cached epdg.epc.mnc002.mcc262.pub.3gppnetwork.org is <CNAME>
   Aug 15 00:00:07 dnsmasq[55217]: cached epdg.epc.drz1.vodafone-ip.de is 139.7.117.168
   Aug 15 00:00:07 dnsmasq[55217]: cached epdg.epc.drz1.vodafone-ip.de is 139.7.117.169
   Aug 15 00:00:10 dnsmasq[55217]: query[PTR] 23.178.168.192.in-addr.arpa from 127.0.0.1
   Aug 15 00:00:10 dnsmasq[55217]: DHCP 192.168.178.23 is Surflex.flexh0.me
   Aug 15 00:00:10 dnsmasq[55217]: query[PTR] 188.178.168.192.in-addr.arpa from 127.0.0.1

   -----tail of pihole.log------
   Aug 15 18:23:09 dnsmasq[1118]: query[A] nrdp.prod.ftl.netflix.com from 192.168.178.161
   Aug 15 18:23:09 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:09 dnsmasq[1118]: query[A] nrdp.prod.ftl.netflix.com from 192.168.178.161
   Aug 15 18:23:09 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:09 dnsmasq[1118]: query[A] nrdp.prod.ftl.netflix.com from 192.168.178.161
   Aug 15 18:23:09 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:09 dnsmasq[1118]: query[A] nrdp.prod.ftl.netflix.com from 192.168.178.161
   Aug 15 18:23:09 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:10 dnsmasq[1118]: query[A] connectivity-check.ubuntu.com.flexh0.me from 192.168.178.22
   Aug 15 18:23:10 dnsmasq[1118]: config connectivity-check.ubuntu.com.flexh0.me is 192.168.178.17
   Aug 15 18:23:10 dnsmasq[1118]: query[AAAA] checkonline.home-assistant.io from 192.168.178.12
   Aug 15 18:23:10 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:10 dnsmasq[1118]: query[A] checkonline.home-assistant.io from 192.168.178.12
   Aug 15 18:23:10 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:10 dnsmasq[1118]: query[A] checkonline.home-assistant.io from 192.168.178.12
   Aug 15 18:23:10 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:10 dnsmasq[1118]: query[AAAA] checkonline.home-assistant.io from 192.168.178.12
   Aug 15 18:23:10 dnsmasq[1118]: config error is REFUSED (EDE: network error)
   Aug 15 18:23:11 dnsmasq[1118]: query[A] test.steampowered.com from 192.168.178.21
   Aug 15 18:23:11 dnsmasq[1118]: config error is REFUSED (EDE: network error)


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

[deHakkelaar]

I moved this thread to the community section as this is not a Pi-hole issue.

[flex-0]

Ok so OS is debian 11 bullseye.

There is no dhcpcd.conf

journalctl --full -u networking.service brought something up:

ifup missing required variable: adress
ifup missing required configuration variables for interface eth0/inet
ifup: failed to bring up eth0
networking.service: Main process exited, code = exited, status=1/Failure
networking.service: Failed with result exit code
Failed to start Raise network

[deHakkelaar]

I believe the indents indentations are important eg:

auto eth0
iface eth0 inet static
  address XX.XX.XX.XX/XXX
  gateway XX.XX.XX.XX

Could also give below a try without CIDR if know how to calculate mask and broadcast address:

auto eth0
iface eth0 inet static
  address XX.XX.XX.XX
  netmask XX.XX.XX.XX
  broadcast XX.XX.XX.XX
  gateway XX.XX.XX.XX

EDIT: Ow maybe below is enough if keep an eye on the journals instead of rebooting:

sudo service networking.service restart

EDIT2: Maybe the service command isnt installed.
If so:

sudo systemctl restart networking.service

And check journals.

[flex-0]

Hey there sorry for taking so long, but I have to do this all via my cellphone bc its the only device with internet conection.

So I tried the diffrent inputs on adress, mac and so on, but none of them work. Setting it back to dhcp and adding ip with

‘ip addr add 192.168.X.X/24 dev eth0’

makes it available via ssh and browser. The journal states the following:

root@rpi3-20220120:~# journalctl --full -u networking.service
-- Journal begins at Tue 2021-07-13 19:29:27 CEST, ends at Mon 2022-08-15 18:56>
Jul 13 19:29:31 rpi3-20220120 systemd[1]: Starting Raise network interfaces...
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Internet Systems Consortium DHCP C>
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Internet Systems Consortium DHCP Clien>
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Copyright 2004-2018 Internet Systems C>
Jul 13 19:29:32 rpi3-20220120 ifup[400]: All rights reserved.
Jul 13 19:29:32 rpi3-20220120 ifup[400]: For info, please visit https://www.isc>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Copyright 2004-2018 Internet Syste>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: All rights reserved.
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: For info, please visit https://www>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: 
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Listening on LPF/eth0/b8:27:eb:60:>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Sending on   LPF/eth0/b8:27:eb:60:>
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Listening on LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Sending on   LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Sending on   Socket/fallback
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Created duid "\000\001\000\001(\200\21>
Jul 13 19:29:32 rpi3-20220120 ifup[400]: DHCPDISCOVER on eth0 to 255.255.255.25>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Sending on   Socket/fallback
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Created duid "\000\001\000\001(\20>
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: DHCPDISCOVER on eth0 to 255.255.25>
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPDISCOVER on eth0 to 255.255.25>
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPOFFER of 192.168.178.5 from 19>
lines 1-23...skipping...
-- Journal begins at Tue 2021-07-13 19:29:27 CEST, ends at Mon 2022-08-15 18:56:02 CEST. --
Jul 13 19:29:31 rpi3-20220120 systemd[1]: Starting Raise network interfaces...
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Internet Systems Consortium DHCP Client 4.4.1
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Internet Systems Consortium DHCP Client 4.4.1
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Copyright 2004-2018 Internet Systems Consortium.
Jul 13 19:29:32 rpi3-20220120 ifup[400]: All rights reserved.
Jul 13 19:29:32 rpi3-20220120 ifup[400]: For info, please visit https://www.isc.org/software/dhcp/
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Copyright 2004-2018 Internet Systems Consortium.
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: All rights reserved.
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: For info, please visit https://www.isc.org/software/dhcp/
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: 
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Listening on LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Sending on   LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Listening on LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Sending on   LPF/eth0/b8:27:eb:60:86:94
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Sending on   Socket/fallback
Jul 13 19:29:32 rpi3-20220120 ifup[400]: Created duid "\000\001\000\001(\200\211\374\270'\353`\206\224".
Jul 13 19:29:32 rpi3-20220120 ifup[400]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Sending on   Socket/fallback
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: Created duid "\000\001\000\001(\200\211\374\270'\353`\206\224".
Jul 13 19:29:32 rpi3-20220120 dhclient[400]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPOFFER of 192.168.178.5 from 192.168.178.1
Jul 13 19:29:36 rpi3-20220120 ifup[400]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jul 13 19:29:36 rpi3-20220120 ifup[400]: DHCPOFFER of 192.168.178.5 from 192.168.178.1
Jul 13 19:29:36 rpi3-20220120 ifup[400]: DHCPREQUEST for 192.168.178.5 on eth0 to 255.255.255.255 port 67
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPREQUEST for 192.168.178.5 on eth0 to 255.255.255.255 port 67
Jul 13 19:29:36 rpi3-20220120 dhclient[400]: DHCPACK of 192.168.178.5 from 192.168.178.1
Jul 13 19:29:36 rpi3-20220120 ifup[400]: DHCPACK of 192.168.178.5 from 192.168.178.1
-- Boot b0596454140d497cae0f4f7d237fcd92 --
Mär 20 20:55:31 rpi3-20220120 systemd[1]: Starting Raise network interfaces...
-- Boot 631515a27d9e47b2aeea95aad8bd4eaa --
Jul 25 20:07:09 rpi3-20220120 dhclient[400]: bound to 192.168.178.5 -- renewal in -32222325 seconds.
Jul 25 20:07:09 rpi3-20220120 ifup[400]: bound to 192.168.178.5 -- renewal in -32222325 seconds.
Jul 25 20:07:09 rpi3-20220120 systemd[1]: Finished Raise network interfaces.
Jul 25 20:07:10 rpi3-20220120 dhclient[400]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Jul 25 20:07:10 rpi3-20220120 dhclient[400]: DHCPOFFER of 192.168.178.5 from 192.168.178.1
Jul 25 20:07:10 rpi3-20220120 dhclient[400]: DHCPREQUEST for 192.168.178.5 on eth0 to 255.255.255.255 port 67
Jul 25 20:07:10 rpi3-20220120 dhclient[400]: DHCPACK of 192.168.178.5 from 192.168.178.1
Jul 25 20:07:10 rpi3-20220120 dhclient[400]: bound to 192.168.178.5 -- renewal in 326838 seconds.
-- Boot b0596454140d497cae0f4f7d237fcd92 --
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: Internet Systems Consortium DHCP Client 4.4.1
Aug 15 18:29:46 rpi3-20220120 ifup[383]: Internet Systems Consortium DHCP Client 4.4.1
Aug 15 18:29:46 rpi3-20220120 ifup[383]: Copyright 2004-2018 Internet Systems Consortium.
Aug 15 18:29:46 rpi3-20220120 ifup[383]: All rights reserved.
Aug 15 18:29:46 rpi3-20220120 ifup[383]: For info, please visit https://www.isc.org/software/dhcp/
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: Copyright 2004-2018 Internet Systems Consortium.
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: All rights reserved.
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: For info, please visit https://www.isc.org/software/dhcp/
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: 
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: Listening on LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: Sending on   LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:29:46 rpi3-20220120 ifup[383]: Listening on LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:29:46 rpi3-20220120 ifup[383]: Sending on   LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:29:46 rpi3-20220120 ifup[383]: Sending on   Socket/fallback
Aug 15 18:29:46 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: Sending on   Socket/fallback
Aug 15 18:29:46 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Aug 15 18:29:52 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Aug 15 18:29:52 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Aug 15 18:30:01 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Aug 15 18:30:01 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Aug 15 18:30:16 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Aug 15 18:30:16 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Aug 15 18:30:33 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Aug 15 18:30:33 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Aug 15 18:30:40 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Aug 15 18:30:40 rpi3-20220120 ifup[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Aug 15 18:30:47 rpi3-20220120 dhclient[383]: No DHCPOFFERS received.
Aug 15 18:30:47 rpi3-20220120 dhclient[383]: No working leases in persistent database - sleeping.
Aug 15 18:30:47 rpi3-20220120 ifup[383]: No DHCPOFFERS received.
Aug 15 18:30:47 rpi3-20220120 ifup[383]: No working leases in persistent database - sleeping.
Aug 15 18:30:47 rpi3-20220120 systemd[1]: Finished Raise network interfaces.
Aug 15 18:36:35 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Aug 15 18:36:40 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Aug 15 18:36:51 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Aug 15 18:37:09 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Aug 15 18:37:20 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug 15 18:37:32 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Aug 15 18:37:36 rpi3-20220120 dhclient[383]: No DHCPOFFERS received.
Aug 15 18:37:36 rpi3-20220120 dhclient[383]: No working leases in persistent database - sleeping.
Aug 15 18:40:46 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Aug 15 18:40:49 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Aug 15 18:40:57 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Aug 15 18:41:10 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Aug 15 18:41:26 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Aug 15 18:41:34 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Aug 15 18:41:43 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Aug 15 18:41:47 rpi3-20220120 dhclient[383]: No DHCPOFFERS received.
Aug 15 18:41:47 rpi3-20220120 dhclient[383]: No working leases in persistent database - sleeping.
Aug 15 18:49:04 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Aug 15 18:49:07 rpi3-20220120 dhclient[383]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Aug 15 18:49:09 rpi3-20220120 systemd[1]: Stopping Raise network interfaces...
Aug 15 18:49:09 rpi3-20220120 ifdown[698]: ifdown: missing required variable: address
Aug 15 18:49:09 rpi3-20220120 ifdown[706]: RTNETLINK answers: No such process
Aug 15 18:49:09 rpi3-20220120 ifdown[698]: ifdown: missing required variable: address
Aug 15 18:49:09 rpi3-20220120 dhclient[383]: receive_packet failed on eth0: Network is down
Aug 15 18:49:09 rpi3-20220120 systemd[1]: networking.service: Succeeded.
Aug 15 18:49:09 rpi3-20220120 systemd[1]: Stopped Raise network interfaces.
Aug 15 18:49:09 rpi3-20220120 systemd[1]: Starting Raise network interfaces...
Aug 15 18:49:10 rpi3-20220120 ifup[728]: ifup: missing required variable: address
Aug 15 18:49:10 rpi3-20220120 ifup[728]: ifup: missing required configuration variables for interface eth0/inet
Aug 15 18:49:10 rpi3-20220120 ifup[728]: ifup: failed to bring up eth0
Aug 15 18:49:10 rpi3-20220120 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 18:49:10 rpi3-20220120 systemd[1]: networking.service: Failed with result 'exit-code'.
Aug 15 18:49:10 rpi3-20220120 systemd[1]: Failed to start Raise network interfaces.
Aug 15 18:51:32 rpi3-20220120 systemd[1]: Starting Raise network interfaces...
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: Internet Systems Consortium DHCP Client 4.4.1
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: Copyright 2004-2018 Internet Systems Consortium.
Aug 15 18:51:33 rpi3-20220120 ifup[777]: Internet Systems Consortium DHCP Client 4.4.1
Aug 15 18:51:33 rpi3-20220120 ifup[777]: Copyright 2004-2018 Internet Systems Consortium.
Aug 15 18:51:33 rpi3-20220120 ifup[777]: All rights reserved.
Aug 15 18:51:33 rpi3-20220120 ifup[777]: For info, please visit https://www.isc.org/software/dhcp/
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: All rights reserved.
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: For info, please visit https://www.isc.org/software/dhcp/
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: 
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: Listening on LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: Sending on   LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:51:33 rpi3-20220120 ifup[777]: Listening on LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:51:33 rpi3-20220120 ifup[777]: Sending on   LPF/eth0/b8:27:eb:a2:5f:22
Aug 15 18:51:33 rpi3-20220120 ifup[777]: Sending on   Socket/fallback
Aug 15 18:51:33 rpi3-20220120 ifup[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: Sending on   Socket/fallback
Aug 15 18:51:33 rpi3-20220120 dhclient[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Aug 15 18:51:41 rpi3-20220120 dhclient[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Aug 15 18:51:41 rpi3-20220120 ifup[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Aug 15 18:51:58 rpi3-20220120 dhclient[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug 15 18:51:58 rpi3-20220120 ifup[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug 15 18:52:10 rpi3-20220120 dhclient[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
Aug 15 18:52:10 rpi3-20220120 ifup[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
Aug 15 18:52:30 rpi3-20220120 dhclient[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Aug 15 18:52:30 rpi3-20220120 ifup[777]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Aug 15 18:52:34 rpi3-20220120 dhclient[777]: No DHCPOFFERS received.
Aug 15 18:52:34 rpi3-20220120 dhclient[777]: No working leases in persistent database - sleeping.
Aug 15 18:52:34 rpi3-20220120 ifup[777]: No DHCPOFFERS received.
Aug 15 18:52:34 rpi3-20220120 ifup[777]: No working leases in persistent database - sleeping.
Aug 15 18:52:34 rpi3-20220120 systemd[1]: Finished Raise network interfaces.

[deHakkelaar]

@flex-0

‘ip addr add 192.168.X.X/24 dev eth0’

It would help if you post the exact IP that your trying to configure via the interfaces file.
They are private addresses so there is very little harm in posting them here (we all share the same addresses).
Also the 192.168.178.5 IP acquired via DHCP is shown in the journals anyway.

Also it would help if you describe your changes first and below it, post only the relevant journal entries.
Its a bit difficult now to distinct what causes what journal entries.

@flex-0

Jul 25 20:07:10 rpi3-20220120 dhclient[400]: bound to 192.168.178.5 -- renewal in 326838 seconds.

By the looks of it, at some stage, acquiring an IP via DHCP seems successful and you would not have to add an IP with the ip command.

I still feel something is wrong with that /etc/network/interfaces file.
I would move it to some place else for reference, and recreate the file eg:

sudo mv /etc/network/interfaces ~

sudo nano /etc/network/interfaces

Or use vi if thats your editor of choice.

Permissions should be 644 if I'm correct.
Can check with below on the original file before moving:

stat /etc/network/interfaces

EDIT: Also after you've restored network connectivity with the ip command, could you post results for below one pls?

pihole-FTL dhcp-discover

Redact the bits that you dont want to expose here!

[flex-0]

Hey sorry for the struggle with me and thanks a lot for your help.

I activates the dhcp in the router, so I can use my normal computer instead of the cellphone.

So here is the outcome of pihole-FTL dhcp-discover

Scanning all your interfaces for DHCP servers
Timeout: 10 seconds

WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
* Received 303 bytes from eth0:192.168.178.5
  Offered IP address: 192.168.178.207
  Server IP address: 192.168.178.5
  Relay-agent IP address: N/A
  BOOTP server: (empty)
  BOOTP file: (empty)
  DHCP options:
   Message type: DHCPOFFER (2)
   server-identifier: 192.168.178.5
   lease-time: 86400 ( 1d )
   renewal-time: 43200 ( 12h )
   rebinding-time: 75600 ( 21h )
   netmask: 255.255.255.0
   broadcast: 192.168.178.255
   dns-server: 192.168.178.5
   domain-name: "flexh0.me"
   router: 192.168.178.1
   --- end of options ---
 
* Received 548 bytes from eth0:192.168.178.1
  Offered IP address: 192.168.178.4
  Server IP address: 192.168.178.1
  Relay-agent IP address: N/A
  BOOTP server: (empty)
  BOOTP file: (empty)
  DHCP options:
   Message type: DHCPOFFER (2)
   server-identifier: 192.168.178.1
   lease-time: 864000 ( 10d )
   renewal-time: 432000 ( 5d )
   rebinding-time: 756000 ( 8d 18h )
   netmask: 255.255.255.0
   router: 192.168.178.1
   dns-server: 192.168.178.1
   domain-name: "fritz.box"
   broadcast: 192.168.178.255
   ntp-server: 192.168.178.1
   Port Control Protocol (PCP) server: 192.168.178.1
 
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 0
DHCP packets received on interface eth0: 2

After that I changed eth0 acordingly to:

auto eth0
iface eth0 inet static
address 192.168.178.5/16
gateway 192.168.178.1
iface eth0 inet6 auto

This time after sudo systemctl restart networking.service its still reachable

root@rpi3-20220120:/etc/network/interfaces.d# sudo systemctl restart networking.service
root@rpi3-20220120:/etc/network/interfaces.d# pihole-FTL dhcp-discover
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds

WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
* Received 548 bytes from eth0:192.168.178.1
  Offered IP address: 192.168.178.4
  Server IP address: 192.168.178.1
  Relay-agent IP address: N/A
  BOOTP server: (empty)
  BOOTP file: (empty)
  DHCP options:
   Message type: DHCPOFFER (2)
   server-identifier: 192.168.178.1
   lease-time: 864000 ( 10d )
   renewal-time: 432000 ( 5d )
   rebinding-time: 756000 ( 8d 18h )
   netmask: 255.255.255.0
   router: 192.168.178.1
   dns-server: 192.168.178.1
   domain-name: "fritz.box"
   broadcast: 192.168.178.255
   ntp-server: 192.168.178.1
   Port Control Protocol (PCP) server: 192.168.178.1
 
* Received 303 bytes from eth0:192.168.178.5
  Offered IP address: 192.168.178.207
  Server IP address: 192.168.178.5
  Relay-agent IP address: N/A
  BOOTP server: (empty)
  BOOTP file: (empty)
  DHCP options:
   Message type: DHCPOFFER (2)
   server-identifier: 192.168.178.5
   lease-time: 86400 ( 1d )
   renewal-time: 43200 ( 12h )
   rebinding-time: 75600 ( 21h )
   netmask: 255.255.0.0
   broadcast: 192.168.255.255
   dns-server: 192.168.178.5
   domain-name: "flexh0.me"
   router: 192.168.178.1
   --- end of options ---
 
DHCP packets received on interface eth0: 2
DHCP packets received on interface wlan0: 0
DHCP packets received on interface lo: 0

[deHakkelaar]

Is it all working after a reboot?
If so, I wouldn't touch a thing except disabling one of the two DHCP services that are running now.