Actions
Bug #5850
closed
tcp timestamping behavior changed mid-connection
Start date:
2015-04-17
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
If the peer sends a segment lacking timestamps on a connection which negotiated timestamps, illumos stops sending timestamp options to the peer. This is in violation of RFC 7323. More background in the thread https://www.listbox.com/member/archive/182193/2015/04/sort/time_rev/page/1/entry/2:3/20150414115040:F678B734-E2BD-11E4-A441-A07D3EA1AED1/
Related issues
Updated by Electric Monk about 8 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
git commit 1f183ba0b0be3e10202501aa3740753df6512804
commit 1f183ba0b0be3e10202501aa3740753df6512804
Author: Lauri Tirkkonen <lotheac@iki.fi>
Date: 2015-07-30T15:33:51.000Z
5850 tcp timestamping behavior changed mid-connection
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: Sebastien Roy <sebastien.roy@delphix.com>
Approved by: Richard Lowe <richlowe@richlowe.net>
Updated by Dan McDonald about 8 years ago
- Related to Bug #6264: seeming problems with 5850 tcp timestamping behavior changed mid-connection added
Updated by Marcel Telka almost 6 years ago
- Related to Bug #7814: Accept TCP keepalives with missing timestamps added
Actions