You are reading the documentation for v1.3.0. The current release is v1.4.0. Go to the latest version of this page →

Exactly what is recorded

Every entry the diagnostic writes carries a session field: the key the engine
grouped the exchange under. It is one of

key_kind session holds On an IPoE BNG that is
subscriber-arc User-Name|NAS-Port-Id the subscriber's MAC address and the physical port they are on
user-nas-port User-Name|NAS-Port-Id the same, for an arc we could not see start to finish
acct-session-id Acct-Session-Id the NAS's own session handle, which your accounting records key on
unmatched (empty) an exchange we could not attribute to anyone

Measured over the committed capture corpus, 88% of entries carry a session
key
— every exchange, finding and unverifiable entry does. Only the
per-segment receipt does not.

An entry also carries: the RADIUS code, the segment filename, a capture
timestamp, and — on a finding — the register requirement id, its tier, the RFC
citation, and the engine's observed/expected prose. That prose quotes packet
identifiers where a rule is about one (an Identifier, a frame number, an
attribute that was present or absent).