Page MenuHomeFreeBSD

Disallow broken ECN TCP stacks from using ECN
ClosedPublic

Authored by rscheff on Jan 28 2019, 1:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 25, 10:07 PM
Unknown Object (File)
Jan 23 2024, 9:48 PM
Unknown Object (File)
Jan 3 2024, 5:16 AM
Unknown Object (File)
Dec 22 2023, 10:06 PM
Unknown Object (File)
Dec 11 2023, 4:57 AM
Unknown Object (File)
Dec 3 2023, 6:09 PM
Unknown Object (File)
Oct 11 2023, 8:48 AM
Unknown Object (File)
Aug 19 2023, 7:24 PM
Subscribers

Details

Summary

RFC3168 specifies on page 15, how to correctly negotiate for a TCP session with ECN support.

There are a (diminishing) number of middleboxes reflecting reserved TCP header bits. Simultaneously an increasing interest in deploying ECN, may lead to
the incorrect behavior for TCP sessions.

On a SYN, both CWR and ECE have to be set, while on the SYN,ACK only the ECE must be set, and CWR must be clear.

Test Plan

Simulating a non-compliant ECN client, injecting ECE-marked ACKs should not result in a reduction of cwnd (and no packets with the CWR bit set).

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 22210
Build 21419: arc lint + arc unit

Event Timeline

Here are two test scripts to validate both the proper behavior of ECN as a client, against a conformant RFC3168 client, as well as a non-conformant client which reflects back all header flags as received:

This revision is now accepted and ready to land.Jan 28 2019, 12:04 PM
tuexen requested changes to this revision.Jan 28 2019, 12:23 PM

Please apply the same fix to tcp_stacks/rack.c.

This revision now requires changes to proceed.Jan 28 2019, 12:23 PM
  • adding RACK stack to ECN handshake check
  • trailing whitespace
This revision was not accepted when it landed; it landed in state Needs Review.Jan 28 2019, 12:45 PM
This revision was automatically updated to reflect the committed changes.