Blog
Troubleshooting write-ups, decisions with real numbers, and the occasional "here is what the vendor did not tell you". Each one names its editor, and every command and figure in it is traced to the documentation or the standard that defines it.
A write-up of one problem: the symptom as the ticket described it, the commands that locate it, and the fix. Every command and every figure traced to the vendor documentation or the standard that defines it, never to another summary.
Each note opens with the symptom in the words of the ticket, then a 30-second proof, then a numbered checklist. Copy the commands; the numbers to remember are in a box at the end.
Reader tickets, our own on-call weeks and the quotes MSPs send us. Send yours through the contact page; if we reproduce it, you get the credit.
Latest notes
8 notes, newest firstWhy a 1500 byte packet dies inside an IPsec tunnel, the two commands that prove it in under a minute, and the MSS clamp that fixes it for good.
A machine can report Secure Boot as on while enforcing nothing at all. Here is the state that causes it, the two commands that reveal it, and what changes when you fix it.
The attacker already has the password and is betting the user will eventually tap approve. Number matching removes the bet, and one alert rule catches the attempt.
The two attributes that tell you what is really stale, why one of them lies, and the order to work in so that a mistake costs two seconds instead of a restore.
The technical gap between them is narrow and specific. What changed is the price of that gap, and whether it is still worth paying depends almost entirely on the size of the estate.
The SAN quote is four times the NAS quote and the case for it is performance nobody has measured. Here is what to measure first, and what the answer usually turns out to be.
The model matters more than the price, because the model decides what happens in year three. Here are the four structures, the five questions worth asking, and when switching actually pays.
The same name answers twice, and which answer a laptop gets depends on which resolver the tunnel handed it. Here is how to prove it in two commands and fix it so it stays fixed.