Constant Enumerations¶

The constant enumerations of pcapkit, generated by pcapkit.vendor.

Unrecognised Values¶

Nearly every registry below departs from enum in one deliberate way: looking up a value it does not define does not raise. Its _missing_ override returns a member-like object named for the unassigned or reserved band the value falls in. Only a value no band covers, or of the wrong type, raises ValueError.

That object is usually not installed: the registry does not grow, and a repeat lookup returns an equal but distinct object. The exceptions, of which Minting an Unrecognised Value gives the full split:

CGAType installs a permanent member, so __members__ and iteration grow.
Flags, CommandType and the Mobility Header and radiotap flag registries, such as BindingACKFlag, hand back to aenum’s flag base, which caches the composed object in the value lookup table only: a repeat lookup returns the same object, while __members__ and iteration are unchanged.
Transport, Type, ManagementSubtype, ExtensionHeader, TLSKeyLabel and the memberless AppType base raise ValueError for any unknown value.

This lets the enumerations decode live captures, where a code assigned after this release was generated is routine, so iterating a registry need not list every value it resolves. Since whether a repeat lookup returns the same object varies by registry, compare unassigned members by value, not identity.

The template in pcapkit.vendor.default emits the override’s common form; the valid range and band names come from each registry’s source data, so the individual overrides are not documented per class.

Constant Enumerations¶

Unrecognised Values¶

Protocol Numbers¶

Link Layer¶

Internet Layer¶

Transport Layer¶

Application Layer¶

Miscellaneous¶