Skip to content

Dot11 Reason Codes are off-by-one from 802.11 spec #810

@cdzombak

Description

@cdzombak

gopacket version: 1.1.18

Comparing gopacket/layers's Dot11 deauth reason codes with several sources from a quick Google search (1, 2, 3, 4), it appears the definitions in gopacket are offset by one.

gopacket's definitions start with Dot11ReasonReserved = 1, while as far as I can tell 0 is in fact reserved. The offset continues down the list: gopacket lists Dot11ReasonUnspecified = 2, while according to all sources I can find 1 in fact means Unspecified, and so on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions