Actions
Bug #7753
openvxlan: decoder drops packets with non-zero reserved fields
Affected Versions:
Effort:
Difficulty:
Label:
C, Needs Suricata-Verify test, Protocol
Description
The current VXLAN decoder implementation follows RFC draft-mahalingam-dutt-dcops-vxlan-00 too strictly and does not ignore the Reserved fields on receipt, as required by RFC 7348 §5 . This causes valid VXLAN packets with non-zero Reserved bits to be dropped, leading to loss of response-side traffic in some environments.
Files
Updated by Fupeng Zhao 28 days ago
- Status changed from New to Assigned
- Assignee changed from OISF Dev to Fupeng Zhao
Assigned to myself.
I plan to remove the strict validation of the Reserved fields entirely. Since we don’t decode the inner packet before parsing the VXLAN header, we can’t reliably determine the packet direction (transmit vs receive) and thus can’t selectively apply Reserved field checks.
Open to alternative suggestions if there's a preferred way to handle this.
Updated by Fupeng Zhao 27 days ago
- Status changed from Assigned to In Review
Updated by Philippe Antoine 10 days ago
- Target version changed from TBD to 9.0.0-beta1
Actions