aboutsummaryrefslogtreecommitdiffstats
path: root/packaging/svr4
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2000-07-30 08:20:52 +0000
committerGuy Harris <guy@alum.mit.edu>2000-07-30 08:20:52 +0000
commit0aa7bec73d7e06a9c55021937aea94be08ae2b84 (patch)
treeb1411f757ce6c06a6a6dfc3bea7aae3d63a60360 /packaging/svr4
parentf9008563433d440f14c7ca61e1deb6ff49b2355f (diff)
In TCP segments with RST and data, display the data as text, labeling it
as a cause for the RST, as per RFC 1122: 4.2.2.12 RST Segment: RFC-793 Section 3.4 A TCP SHOULD allow a received RST segment to include data. DISCUSSION It has been suggested that a RST segment could contain ASCII text that encoded and explained the cause of the RST. No standard has yet been established for such data. Thanks and a tip of the Hatlo hat to Kevin Steves of HP for mentioning this on the tcpdump-workers list (he contributed a tcpdump patch to do the same). svn path=/trunk/; revision=2178
Diffstat (limited to 'packaging/svr4')
0 files changed, 0 insertions, 0 deletions