ipv6-slaac-logger - accountability for SLAAC addresses with RFC 9686

One of the most common objections I hear to SLAAC, and frankly one of the most legitimate ones, is accountability. “If the host picks its own address, how do I know who had 3fff:db8:10::5c1e:9aff:fe3b:21aa last Tuesday at 21:00?” With DHCPv6 IA_NA you get a lease log - this is what everyone is used to with legacy IP - and why so many enterprises ask for DHCPv6 support. With SLAAC, and especially with temporary/privacy addresses rotating underneath you, you get… whatever you can scrape out of neighbor caches before they age out.

piccolo-perf - a perfSONAR-lite for routers and SBCs

I have a soft spot for perfSONAR . It’s the gold standard for research and education network performance measurement, and if you run a network that touches ESnet, Internet2, or any of the big R&E backbones, you’ve probably got a perfSONAR node (or ten) somewhere. The problem is that perfSONAR is heavy. It wants a full OS, a stack of services, and real resources. That’s fine for a dedicated measurement box and that has served perfSonar well for 20 years, but it’s a non-starter for a router, a Raspberry Pi at a remote site, or anything else you’d call “constrained.

An alternative to smokeping

I have been using smokeping for 25 years. It’s a great tool that provides a useful and unique data set. The thing about smokeping is that it does not really have a lot of alternatives. To that end, I embarked on an amateurish re-imagining of both smokeping and its contemporary successor, vaping in golang. Initial version supports ping and DNS and has a nearly identical structure to Vaping (why re-invent the wheel?