treblada

I experienced SSH connection issues when I tried to connect to my HP iLO 4 system. It worked a few days ago, and then suddenly stopped working. I could still connect from a Raspberry Pi. Given the full log files, Claude found the solution:

Diagnosis

Both logs show the SSH negotiation picking the exact same algorithms (diffie-hellman-group14-sha1 for KEX, ssh-rsa for host key, aes256-ctr/hmac-sha2-256 for cipher/MAC) — the iLO 4's ancient SSH stack (mpSSH_0.2.1) only understands that handful of legacy algorithms, and both your Mac and the Pi correctly negotiate down to them.

The difference shows up after negotiation, at the Diffie-Hellman exchange itself:

• Pi (works): sends KEXDH_INIT (type 30) → receives KEXDH_REPLY (type 31) → continues normally.
• Mac (fails): sends KEXDH_INIT (type 30) → instead of a reply, the iLO immediately sends SSH_MSG_DISCONNECT (type 1), reason 11, "Client Disconnect".

treblada

I had following warnings every 30 seconds in my /var/log/syslog on a RaspberryPi.

2026-07-30T20:10:13.123478+02:00 pi conmon: conmon f20c2d009a532fdadc23 <nwarn>: Failed to add inotify watch for /sys/fs/cgroup/user.slice/user-1001.slice/user@1001.service/user.slice/libpod-f20c2d009a532fdadc23.scope/container/init.scope/memory.events
2026-07-30T20:10:13.131901+02:00 pi conmon: conmon f20c2d009a532fdadc23 <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1001.slice/user@1001.service/user.slice/libpod-f20c2d009a532fdadc23.scope/container/init.scope/memory.events

Here is Claude's analysis and it was right.

Diagnosis — root cause found

treblada

Dockerised ioBroker (v11) + Yahka + HomeKit (iOS 26)

Created: 2025-12-29

#docker #iobroker #yahka #homekit #avahi #zeroconf #bonjour

Abstract

It is generally possible control devices in ioBroker via Yahka on your iOS device, but with some limitation, i.e. home controls cannot be shared with others without an HomeHub device like an AppleTV (4.Gen) or HomePod.

General Architecture (as I understand it)

treblada

Create DNS-over-TLS bridge with Pi-hole, unbound and stubby on Ubuntu Server

Few months ago, I've made a similar work but I wanted something a little more easier to manage. Please have a look at here for my previous work.

This time, I'm gonna do pretty much the same thing but using Pi-hole as base then modify it to include unbound and stubby.

This way, I can use the power of Pi-hole with some additional security layers:

• Recursive DNS check (unbound)
• DNS-over-TLS (stubby)