Romain

Install Tailscale tsidp in Proxmox

In this guide we’ll walk through setting up Tailscale’s experimental Identity Provider (tsidp) inside a lightweight Debian Proxmox container. We’ll create the container, install Go, build the binary, configure systemd with environment variables, and run tsidp as a dedicated user.

This is a very raw howto, copy paste ready, based on my attempts, target audience is homelaber. Comments welcome !

Read More

Proxmox: Losing network with Intel I-219v

Recently migrated my homelab ESXi to Proxmox VE, and while things mostly went smoothly, one node would randomly hang (mostly during large transfers or under sustained network load but sometimes when idling...).
I plugged in a monitor to check logs and... confirmed the cause with a quick dmesg:

e1000e: Detected Hardware Unit Hang 

Turns out this has been a known issue for years with Intel e1000e NICs (like I217-LM, I219-V, 82574L, etc.). These "aging" chips choke when offload features are enabled under modern workloads.

Read More

Explore Btrfs images on MacOS

While troubleshooting a malfunctioning radar system, I wanted to inspect its firmware for diagnostic tools (couldn't find any). The firmware was stored in a Btrfs image, which isn't straightforward to handle on macOS without spending some quality time with FUSE.

To "extract" its contents, I instead used a Docker container with the necessary tools, because it's quite easy to do on plain linux. Here's how.

Read More

High Battery Drain in Cursor AI: It was the Import Cost Extension

Out of curiosity I'm testing Cursor AI ( and I'm actually enjoying it more that I should ), but I quickly noticed my laptop's battery draining at an alarming rate - faster than playing Factorio. After investigation, the root cause was clear: the Import Cost VS Code extension was triggering excessive CPU usage through repeated recalculations (for no reason?!).

Edit: No reason might seem excessive. It's a TypeScript project and I was working on components that got imported everywhere so I might understand why the sizes needed to be updated, but it's not a BIG project, it still doesn't make sense to eat all the CPU.

Read More