Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Packetdrill_tarr_ext
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Stefan Gense
Packetdrill_tarr_ext
Commits
11e07d63
Commit
11e07d63
authored
9 years ago
by
Shivansh Rai
Browse files
Options
Downloads
Patches
Plain Diff
Test for behavior when sending a packet with RST bit set but no SYN bit set
parent
00035bb2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt
+22
-0
22 additions, 0 deletions
.../packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt
with
22 additions
and
0 deletions
gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt
0 → 100644
+
22
−
0
View file @
11e07d63
// Test behavior when a listener gets an incoming packet that has
// the RST bit set but not the SYN bit set.
0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
0.000 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
0.000 bind(3, ..., ...) = 0
0.000 listen(3, 1) = 0
0.100 < R 0:0(0) win 65535 <mss 1460,sackOK,nop,nop,nop,wscale 7>
// The TCP stack should not respond to incoming RSTs, or else
// we could get infinite RST ping-pong storms.
// Now make sure that when a valid SYN arrives shortly thereafter
// (with the same address 4-tuple) we can still successfully establish
// a connection.
0.200 < S 0:0(0) win 65535 <mss 1460,sackOK,nop,nop,nop,wscale 7>
0.200 > S. 0:0(0) ack 1 <...>
0.300 < . 1:1(0) ack 1 win 65535
0.300 accept(3, ..., ...) = 4
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment