Cant ssh into pi after reboot with pihole installed

Ok, i had a problem like that before, so to my setup

Raspberry pi 2, newest updates and upgrades
Its running a Network bridge from lan to wlan
I have 3 interfaces, eth0, br0, wlan0
the bridge is still working fine
pihole is configured to use br0 for connections, working until reboot
Now no SSH access is possible anymore

Had someone the same problems? Internet must be working else the network bridge wouldnt work and i dont want to restore to my old backup all the time and then install everything again when i need to reboot the system....

Pihole is configured with static ip, checked that already
Was not configured to use an IPv6 thingy
Was configured to use the br0 interface since eth0 would kill the interface access for the pi (resolved that on github)

any help maybe why this is happening? and how to resolve that? found no answer anywhere till yet

I have the exact same issue. I cannot access my pi anymore since installing pihole and doing a reboot. SSH tells me that the devices fingerprint changed and this could be something nasty.
What is this? I don't like this. :frowning:

I found the problem: Pihole will not solve local domains like myserver.fritz.box. I think it tried to login on some internet address. How can I tell pihole that fritz.box is the local network?

There are several posts about Fritz!boxes. I recall seeing some post about upgrading the firmware fixed a lot of issues. Nonetheless, take a look here.

@VexMex ,
have you checked sshd is running on console ?

$ netstat -nltp
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 295/inetd

In my case, the super server daemon "inetd" is listening on port 22 and boots up an sshd daemon when a client tries to connect and then forwards the client to the sshd daemon.

Another way of checking if sshd is active is to do:

$ ssh localhost

With later distributions, the sshd daemon wont start default at boot.
Need to do for example below to have the sshd daemon activated at boot:

$ touch /boot/ssh
$ reboot

1 Like

so on netstat -nltp there are some things, also 2 times sshd

tcp 0 0.0.0.0:22 0.0.0:* Listen 812/sshd
and also this
tcp6 0 :::22 :::* Listen 812/sshd (i assume its ipv6 right?)

ssh localhost works but ping or overall internet access from withing the pi doesnt work,
ping to 8.8.8.8 doesnt work
ping to my computer doesnt work
ping to my fritzbox router doesnt work

but network bridge is still working flawless

@VexMex ,
yes those two entries mean sshd is listening on tcp4 and tcp6 port 22.
Could you run below, paste the output on pastebin.com, and post the pastebin link here please ?

ip link show; echo "---"; ip addr show; echo "---"; ip route show; echo "---"; brctl show;

Ps. run this one as user 'root' to make sure everything is included.

@VexMex ,
If you dont have ssh, you could redirect the output to a file on the '/boot' partition on the SD card as this is a FAT partition that can be read by most any PC.
So you just need to plug the SD card into another PC (remove power from pi first!!!) and look for the file 'network.txt':

(ip link show; echo "---"; ip addr show; echo "---"; ip route show; echo "---"; brctl show;) > /boot/network.txt

http://pastebin.com/JzWQVnaB used as root

Darn this gave me some headaches bc they changed things again :wink:
Better put the IP on the bridge interface like below.

In "/etc/network/interfaces":

allow-hotplug eth0
iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
    wpa-ssid <YOUR_SSID_NAME>
    wpa-psk <PASSWORD>

auto br0
iface br0 inet manual
    bridge_ports eth0 wlan0

In "/etc/dhcpcd.conf":

interface eth0
nodhcp
nodhcp6

interface wlan0
nodhcp
nodhcp6

interface br0
static ip_address=192.168.178.40/24
static routers=192.168.178.1
static domain_name_servers=127.0.0.1

Let me know if works ?
Ps. forget hot-plug without real STP.

ok i have absolutely no clue what was wrong ebsides the static domain_name_servers and here and there few other things, but damn you are good, it now works like a charm, even after a reboot :smiley: thanks very much for the help!!!

Your welcome and next time you can help someone else setting up bridging etc :wink:

Thanks,
It's resolved my issue with raspberrypi release 4.19.118.
ssh was not enabled on install.