After recent update, not able to ssh into dietpi 8.9.2

Troubleshooting
1

I changed the /boot/dietpi.txt to enable auto updates a few weeks back.

CONFIG_CHECK_APT_UPDATES=2

Now I cannot ssh into the dietpi. logged into serial terminal, port 22 is still open on 0.0.0.0:22
Installed ssh through dietpi-software(it uninstalled dropbear)
Still can’t login.(permission denied)
Added ip to DMZ, still no go.
Reinstalled dropbear through dietpi-software, port 22 is open, can’t connect.
Tried port 24, no go.
Can ssh to localhost from rpi serial connection fine.

Also there is a bug installing telnetd, does not open port 23.
apt install telnetd
Dietpi 8.9.2 latest update.

2

Try this apt update; apt install tcpdump; iptables-save -c; tcpdump -i any -vn tcp port 22
Try to connect a couple of times before you run the commands, so we see hits on the firewall, and after tcpdump is running, so we can see if and how the packets get to the server.

3

question: are you able to connect but not able to login (incorrect user/password)? Or don’t you even have the login prompt?

4

Not able to connect, no login prompt.
No firewall installed on router or dietpi.
Dietpi ip is in DMZ on router.

5

Did you tried what Trendy suggested?
apt update; apt install tcpdump; iptables-save -c; tcpdump -i any -vn tcp port 22

1 Like
6

for testing, are you able to move your client (computer, laptop) into same DMZ? Just to have client and server within same network segment.

1 Like
7

For posterity.

I had a similar problem while trying to update. The first time occurred at 8.9.2, but still appears to hold with 9.1.1 .

Symptoms:

  1. No SSH connection is available after dietpi-update and reboot
  2. Cannot ping the updated device
  3. Updated device cannot ping any other device
  4. Updated device cannot get a WLAN connection - cannot even apt install tcpdump as suggested

What I found is that there is something wrong with the images/updates for my device specifically - Odroid Xu4.

Solution to workaround broken updates:
Referencing this I ‘held’ the packages listed below. I was then able to apt-update, apt upgrade, and dietpi-update without connections breaking.

apt-mark hold

linux-u-boot-odroidxu4-current
linux-image-current-odroidxu4
linux-dtb-current-odroidxu4
8

Since my XU4 runs fine with those packages at their latest version: If you find time, could you try again and check why network is not set up? As a start, details about the network interfaces and routes would help:

ip l
ip a
ip r

linux-u-boot-odroidxu4-current btw can be upgraded without issues. Upgrading this package does not imply an actual U-Boot update, as it does not flash the binary. Also, since the device does boot, just network is not configured, I am sure it is the kernel, not the bootloader.