Skip to content
Damien Dye

Damien Dye

Infrastructure & homelab notes — Proxmox, Ceph, NetBox, Ansible, Certificates.

Recent Posts

Open WebUI to FastFlowLM to the XDNA2 NPU on IPv6 loopback: 21 W answering, 232,000 tokens in one prompt, three years from AMD's keynote to Linux

Running An LLM On The Ryzen AI NPU, In A Container

The NPU in a Ryzen AI laptop is 50 TOPS that sits idle on most Linux installs. This walks through building AMD’s amdxdna driver and keeping only the kernel module on the host, building FastFlowLM with AMD’s XRT runtime into a rootless podman container matched to that driver, binding everything to IPv6 loopback and starting it at boot with Quadlet. Then what it does: nine models benchmarked, a 232,000-token context test, Whisper speech-to-text at ten times real time, Open WebUI and the 7,000 hidden tokens it was adding to every message, and the speed and energy of the NPU measured against llama.cpp on the Radeon 860M iGPU. Last, the timeline: three years from AMD announcing Ryzen AI to a language model on its NPU under Linux, delivered by a project AMD did not start, while the effort went to Copilot+ on the Fisher-Price OS (Windows) instead of the data centre and the Linux tooling AI professionals actually use.

13th November 2026 · 24 min · 5853 words · Damien Dye
Crimson, Ceph's own Seastar rewrite of the OSD with SeaStore, against croit FlashStore, a Rust rewrite with its own store

FlashStore Against Crimson: Two Rewrites Of The Same OSD

Crimson is Ceph’s own rewrite of the OSD, in C++ on the Seastar framework, with a new native store called SeaStore; FlashStore is croit’s rewrite, in Rust, with a store of its own. Both are in preview and both are aimed at NVMe and fast networks. This compares them as Ceph 21.2.0 Umbrella ships Crimson, from Ceph’s source and documentation and croit’s ceph-rust snapshot: where each comes from and under what licence, why Rust meets the Five Eyes memory-safety guidance and C++ does not, why Crimson needs its own pools and an experimental flag while FlashStore drops into existing pools, why Umbrella has no way to turn an existing pool into a Crimson pool so the data has to be copied, what each tells the monitor at boot, Seastar reactors against pinned polling cores, the fact that a default Crimson OSD still runs BlueStore, SeaStore’s onode, OMAP and LBA trees against FlashStore’s one tree per shard, the order each commits a write in, SeaStore’s segment cleaner, and what hardware and pools each will take.

11th November 2026 · 20 min · 4679 words · Damien Dye
Umbrella BlueStore, RocksDB on BlueFS on any drive, against croit FlashStore, a copy-on-write B+tree and WAL per core on NVMe with power-loss protection

FlashStore Against Umbrella BlueStore: What croit Changed Under The OSD

croit’s ceph-rust is a clean-room Rust rewrite of the Ceph OSD with its own object store, FlashStore, in public preview since 9th November 2026. This puts it side by side with BlueStore exactly as Ceph 21.2.0 Umbrella ships it, read from both projects’ source and documentation: what is in the repository and under which licences, where each store keeps its metadata, how a 4 KiB write and a write under 4 KiB reach the drive in each, Umbrella’s thread pools against FlashStore’s one thread per core, why FlashStore makes power-loss protection a hard requirement, what it will not run on, why it tells your monitors it is BlueStore, which BlueStore options it honours and which it ignores, and why the only way between the two is backfill.

11th November 2026 · 20 min · 4665 words · Damien Dye
A Proxmox VE node running Proxmox's own Ceph monitor and manager beside croit FlashStore OSDs on eight Optane drives

FlashStore OSD on Proxmox VE: What It Took on One Node

croit’s FlashStore OSD is a Rust replacement for ceph-osd and BlueStore, in public preview since 9th November 2026. This deploys it hyperconverged on a single Proxmox VE 9.2 node: Ceph Umbrella 21.2.0 from the PVE wizard for the monitor and manager, FlashStore OSDs on Intel Optane P4800X drives. It covers why Umbrella is the only Proxmox release that matches, formatting the drives to 4 KiB and the controller reset that aborts a format, what croit-flashstore-osd –check reports, why the shipped unit cannot read Proxmox’s ceph.conf and the drop-in that fixes it, the NVMe passthrough Proxmox’s kernel refuses and the direct backend that works, preparing OSDs by PCI address, what the PVE OSD panel makes of them, a pool, RBD storage and a Fisher-Price OS (Windows) VM installed onto it, CrystalDiskMark from inside that VM read against the drives’ own counters, Ceph’s memory with all eight OSDs active, three VMs at once on a 1 GiB memory target, and a setup script that does all of it, tested by rebuilding an OSD from nothing.

11th November 2026 · 35 min · 7721 words · Damien Dye
Three customer sites feeding one Caddy, which hands each its own token, in front of one Proxmox Datacenter Manager

One PXE Estate for Every Customer: Unattended Installs with Proxmox Datacenter Manager

Proxmox Datacenter Manager 1.1 can serve answer files to the Proxmox automated installer, which makes it a natural install server for an MSP looking after many customer sites. The use case is a customer who wanted every site built with its own naming, root password and SSH keys, by plugging a server into the right VLAN and booting it, with no serial numbers to collect and no answer file per machine; this post covers that booting and installing half, and leaves joining the cluster aside. It cannot match an answer on the site, and it cannot give a node a first-boot script, and both are shown from PDM’s own source. This builds one PXE estate for every site anyway: one boot image carrying a non-secret catch token, DNS TXT discovery so the image holds no URL, and a Caddy proxy that swaps the catch token for the site’s own bearer token by source subnet. It covers how PDM picks an answer, prepare-iso for iPXE, the DNS records, dnsmasq and the iPXE loop, a hardened Caddy that serves the whole PDM UI on 443 with 8443 closed by nftables, logging which token was used by name only, the post-installation webhook, adding Proxmox Backup Server, and the trade-offs that remain.

7th November 2026 · 35 min · 8070 words · Damien Dye
Who is Reform actually for: settled taxpayers lose their status, donors living abroad fund the party

Who Is Reform Actually For? The Money, The Men And The Record

An opinion piece on Reform UK, built from its own documents and the public record. Its plan to rescind indefinite leave to remain from people who live, work and pay tax here. A welfare plan that spares the State Pension and cuts working-age support. A party company leader-owned until 2025, and a constitution that leaves members a suggestion box. The in-work Universal Credit claimants and the carers the plan would remove. 75 to 80% of donations from donors living abroad, a domicile test Parliament passed in 2009 and never switched on, and what the Council of Europe and the government’s own review say about that kind of money. The donors’ interests: Tether, QinetiQ, crypto, and a US guilty plea and pardon. The £5m gift, Farage’s earnings and his record as an MEP, Tice’s property and tax, Jenrick’s reversal and Westferry, the Putin and Trump links, who paid for the trips to Trump’s inauguration, Mar-a-Lago, Abu Dhabi and Israel, RFOI Ltd, the Ghandehari trust and the near-bankrupt firms that gave £485,000, the crypto firms paying Farage and the pensioners losing money to crypto fraud, the coverage Reform gets on the BBC and its own seat on GB News, the racism and discipline record, and 7 of 12 smears that turned out to be real. Then the question in the title.

28th October 2026 · 78 min · 21871 words · Damien Dye
Breathing space on a State Pension: what the 2026 Budget gives a pensioner couple heating with gas

Breathing Space On A State Pension: The 2026 Budget For A Pensioner Couple On Gas

What the 2026 Budget does for a couple living only on the full new State Pension, £25,095 a year between them, heating a home with gas at 13,375 kWh a year and running a petrol car for 4,000 miles. A ledger from the Treasury’s own document: the £100 Household Energy Payment, 0% VAT on electricity, the fuel duty cut, the gas standing charge moving into the unit rate, which costs a high gas user money, and the Gas Shipper Obligation moving to general taxation, which for once helps. Then the things that do not show on a bill: an income £119 a week too high for Pension Credit and the help with glasses that comes with it, a mandatory eyesight check for older drivers under consultation, fiscal drag that takes their room under the Personal Allowance rather than cash, a Pension Tax Allowance patching it that runs out a year before the freeze does and taxes a £790 workplace annuity that indexing would have left alone, the Triple Lock adjustment from April 2030 worth £15 billion a year to the Treasury by the late 2030s, and the insulation and heat pump money that would have helped them most, cut or taxed.

28th October 2026 · 17 min · 4069 words · Damien Dye
Breathing space for whom: what the 2026 Budget gives a house with an EV, solar and a battery, against what it gives large business

Breathing Space For Whom? The 2026 Budget From A House With An EV, Solar And A Battery

What the 2026 Budget actually does for a 40% taxpayer who works from home, runs an EV doing 20,000 miles a year on the other half’s commute, runs solar and a battery, and has cut gas to hot water and a little heating. A measure-by-measure ledger from the Treasury’s own document: the £100 Household Energy Payment, 0% VAT on electricity, the gas standing charge moving into the unit rate while the larger electricity standing charge stays, the Gas Shipper Obligation moved off the gas bill and onto general taxation, and who it pays, why hydrogen made from electricity loses to a 280% heat pump, the eVED mileage charge on a 20,000-mile commute, and the fiscal drag of thresholds frozen from 2021 to 2031, worked out against where the law would have put them, for a 40% taxpayer and for the low paid it hits first. Then who gets the money instead, from the Budget’s own costings: 10,000 energy-intensive manufacturers, energy-from-waste operators, high-growth founders against ordinary owners selling up, small high-street firms paid for by small online sellers, data centres at the front of the grid queue, and the defence build-up funded partly by cutting the Warm Homes Plan, with the MoD’s own figures on how much goes to BAE Systems and how much is spent without competition. What it does not do for insulation and rooftop solar, where VAT goes back up to 5%, and what has happened to the heat pump grant. And what the new online marketplace VAT rule means for selling your own things on eBay.

28th October 2026 · 38 min · 8937 words · Damien Dye
Guest writes on the left, VDO in the middle, and only about a quarter of the bytes reaching the drive on the right

VDO Under Proxmox Local LVM: Fewer Bytes Reach the Drive

VDO is the kernel’s deduplication and compression layer. Under a thick LVM volume group it gives Proxmox VE local disks that write one copy of every block the VMs share, so far fewer bytes ever reach the drive. This builds it thick on thick on a Proxmox VE 9 host, with VDO sized to the space it really has so nothing above it can overcommit, the lvm.conf scan_lvs setting and its filter, and VDO’s threads matched to the CPU count. It measures what deduplication saved on a template and six full clones, two ISOs, zeros and random data, how many bytes the drive actually received against what the guest wrote, and what VDO costs against the same Intel Optane with no VDO at all. It then builds the pool with VDO’s index and journals on NVMe and the data on a second device, proves the layout with vdolistmetadata, measures how the I/O splits, then puts VDO on top of bcache with one NVMe partitioned between the bcache cache and VDO’s metadata, and measures how many bytes reach the cache with and without VDO. It reasons through what all of this means on HDD hardware RAID6, and covers discard on delete.

27th October 2026 · 28 min · 6177 words · Damien Dye
Two Proxmox defaults: Hyper-V enlightenments switched on by the VM's OS Type, and CPU microcode switched on by how the host was installed

Two Proxmox VE 9 Defaults You Might Not Have: Hyper-V Enlightenments and CPU Microcode

Proxmox VE 9 turns on Hyper-V enlightenments for Fisher-Price OS (Windows) guests and installs CPU microcode on new hosts, but only if the VM was given a Microsoft Windows OS type and the host came from the 9.x installer. This covers what the enlightenments do, the exact rules qemu-server uses to pick them (measured on a live 9.2 host), why machine version pinning keeps older VMs off the July 2026 hv-evmcs fix, the pve-qemu-kvm build that fix needs and what each QEMU release since 10.0 fixed for those guests, why they belong on q35 and never i440fx (which the wizard still hands most of them), the two flags you can set by hand, how to prove what a VM is running, where microcode comes from (board firmware, Debian and Proxmox’s own repository), why an upgraded host has none (with an Intel node four Intel releases behind as the example), the initramfs rebuild that installing it triggers and the older kernels that rebuild misses, the Zen 5 RDSEED failure that follows, enabling it, a rolling reboot across a Ceph cluster, and rolling back a bad update.

27th October 2026 · 25 min · 6016 words · Damien Dye
AutoNavAlerts: Google's map and routing on Android Auto, with camera alerts only for cameras facing your way

AutoNavAlerts, Part One: A Sat Nav Of My Own For Android Auto

AutoNavAlerts is an Android Auto navigation app I am building on Google’s Navigation SDK: Google’s map, traffic, search and turn-by-turn, with a camera alert system on top that loads my own PocketGPSWorld subscription and only alerts for cameras facing my direction of travel. Part one covers what it does today, what Google allows a third-party app to do on the car screen and what it holds back (incident reporting, the speed limit, touch on its own controls), why every user brings their own Maps key and their own camera data, and how the code was written with Claude: a design document first, 87 commits in under two days, the hard rules that came out of the test bench, the bugs the agents wrote and how each one was caught, and the first real drive in the car.

23rd October 2026 · 16 min · 3395 words · Damien Dye
A stock WordPress exposes 133 REST routes, 80 XML-RPC methods and 1,514 PHP files; this static site runs nothing on request

A Static Site Has Nothing To Break Into

This blog is built with Hugo and served as 6,343 plain files, with no code of mine running on any request. Against it, a stock WordPress 7.1.3 measured in a podman lab: 133 REST routes, 62 of them accepting writes, 80 XML-RPC methods, 1,514 PHP files, every one of its 3,785 files writable by the web server’s own user, and a database account holding every privilege. This post counts both attack surfaces, explains what Hugo’s own security model does at build time, owns up to where the risk moves once nothing runs at serve time, including two gaps in how this site was built, one of them now fixed, and sets out how to build a static site offline, once, and upload nothing but the finished files.

23rd October 2026 · 17 min · 4046 words · Damien Dye
757 PHP interpreter CVEs since 1997, at least 288 memory corruption, 172 rated full remote compromise without a login

PHP: Twenty-Nine Years Of Leaving The Door Open

PHP2Shell, disclosed on 21st October 2026, is unauthenticated remote code execution in the PHP interpreter itself, every version back to 5.4, exploited before the patch existed. It is the latest entry in a long record: 757 CVEs against the interpreter since 1997, at least 288 of them memory corruption and 172 rated as full remote compromise without a login. This post counts that record from NVD and the CISA KEV catalogue, explains why a C engine and a language that took a decade to remove register_globals make the same mistake twice, looks at what WordPress does to the numbers, how web shells stay put and how to stop them, the two times php.net itself was broken into, the share of the web still running versions nobody patches, and why the usual deployment, one process holding the templates, the logic, the SQL and the database password, turns every one of those bugs into everything. And why, having given up on PHP myself, I think you should look at leaving it for a memory-safe language such as Go.

23rd October 2026 · 29 min · 8074 words · Damien Dye
Seven mail settings along the path between two servers, with DNSSEC and IPv6 underneath

Why Every Mail Setting Has To Be Right

Every layer of email security is designed to fall back to working rather than fail safely. Strip the STARTTLS line out of a greeting and an opportunistic sender carries on in the clear, which RFC 3207 both describes as an attack and, on a public server, forbids you to defend against. This post captures that man-in-the-middle in a lab, then walks the seven settings that protect a message in transit, showing for each one what it protects, what it does not, and how it fails open when it is wrong. From there to DANE: why a TLSA record is worthless without DNSSEC under it, why 3 1 1 and key reuse matter, and how a stale record is the one failure that closes rather than opens. Then a read-only census of UK banks, the big mail providers and the certificate authorities, counting how many actually do any of it.

22nd October 2026 · 20 min · 4350 words · Damien Dye
An SMTP session as six stages, each with the rule that rejects there

Postfix, DANE And Every Setting Done Properly

Out of the box Postfix sends in the clear when the far end offers no TLS and takes mail from anybody claiming to be anybody. This is the other build: Postfix 3.10.13 with Dovecot for logins, Rspamd for SPF, DKIM and DMARC, and postfix-tlspol for DANE and MTA-STS. No plaintext in or out, port 25 never relays, a login owns its addresses in the envelope and the From header, sender domains that do not exist are refused, and a tampered or spoofed message never gets past DATA. Every reply was captured in a lab over IPv4 and IPv6, along with the six settings that silently do nothing until something else is set too, the certbot default that breaks DANE on renewal, and what all of it costs you in forwarded mail.

22nd October 2026 · 22 min · 4858 words · Damien Dye
A split between the settings Microsoft 365 controls for you and the few you are left to configure, with the rules it cannot meet marked

Microsoft 365: The Fisher-Price IT Edition

Most organisations do not run their own mail server. They pay Microsoft, and Exchange Online does the work. So this post holds Microsoft 365 to exactly the house rules the Postfix and Stalwart builds met, using nothing but Microsoft’s own documentation and read-only DNS against real tenants. Some of the rules it meets well: outbound DANE and MTA-STS are on by default, and inbound DANE with DNSSEC finally went GA. Several it cannot meet at all. There is no documented way to require inbound TLS from every sender, no way to reject an SPF hard fail at the door, nothing that rejects on a failed DKIM signature alone, and no control that drops mail from a sender domain that does not exist. DNSSEC is explicitly not planned for the mail host every tenant actually uses. The IPv6 rollout that was meant to take six months has left the NCSC’s own mailbox unreachable over IPv6 two years on. And the documentation contradicts itself on wildcards, on SPF, and on DNSSEC. This is the platform most of the country’s mail runs on, and this is what it will and will not let you do.

22nd October 2026 · 12 min · 2800 words · Damien Dye
Stalwart as one binary containing the whole mail stack, against the four-package Postfix build

Stalwart: DANE And The Rest, Built In

Stalwart is a whole mail server in one binary: SMTP and IMAP and JMAP, SPF, DKIM, DMARC, ARC, DANE, MTA-STS, TLS reporting, a spam filter and the mail store, with no milter to wire up and no policy daemon to run beside it. This post holds it to the same house rules as the Postfix build and captures every reply in the lab. The rules all go on, but the story is in the detail: the settings live in a database rather than a file, the defaults as shipped accept plaintext and a tampered invoice, each rule lands in a different one of four configuration mechanisms, DKIM-fail rejection needs a Sieve script because the built-in check reports a tampered body as neutral, the unknown-sender check runs only after the whole message is in and fails open on a DNS error, and the MTA-STS sender bounces on the first attempt where the standard says it should defer. Built in is genuinely less to wire together. It is not the same as safe by default.

22nd October 2026 · 12 min · 2654 words · Damien Dye