Authentication: works with FRR master since #23331
Restarting the engine without the peers noticing (--pin)
1024 sessions, and the registration burst a released bfdd loses The engine holds 1024 sessions. A released bfdd offloads only about 58 of them per connect; #22645 on master fixes it, and the measured numbers are from master.
Separate the instructions from the measurements The instruction pages had this testbed in them. A sample attach showed an interface the page had not told anyone to use, the scheduling note appealed to the testbed as though a reader knew what that was, and the troubleshooting page talked about a full mesh, which is this project word for its own fabric and not something anyone else has. The measurement pages keep their numbers, which is the point of them, but now say what travels to another machine. Per-frame costs do; packets per second belong to one NIC and one CPU. Session counts are given out of 64 because that is the fabric they were taken on, and what matters is whether any session was lost rather than the denominator. Also says what native and generic attach mean, since the sample output prints one of them and nothing explained it.
Rewrite the wiki as pages a reader can use The first pass moved the old README sections across as they were, which gave a Deployment page that was six caveats in a bullet list and nothing telling anyone how to deploy anything. Written properly this time, for someone arriving without the project in their head: install it, wire it to FRR in an order that works, then check the fast path is really carrying the traffic rather than trusting show bfd peer, which looks identical either way. Two new pages carry most of the value. Troubleshooting is symptom first and covers what actually goes wrong: a peer configured on one side only, the 64 session ceiling, sessions stranded by an engine restart, the three separate reasons an authenticated session never comes up, a snapshot file left behind by a previous engine, and the observer quietly stealing the XDP attach. Monitoring explains the snapshot and all eighteen counters, since a number nobody can interpret is not monitoring. Limitations is prose with the reasoning and the upstream links rather than a list of bullets.