Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TCP: Zero window probing not correct #126

Closed
BartVolkaerts opened this issue Mar 14, 2014 · 1 comment
Closed

TCP: Zero window probing not correct #126

BartVolkaerts opened this issue Mar 14, 2014 · 1 comment
Labels

Comments

@BartVolkaerts
Copy link

Flow:
we <--------- SYN ------------- pico
we ---------- SYN, ACK -----> pico
we <--------- ACK ------------- pico (connection established)
we <----- PSH, ACK, data --- pico
we ------- ACK, window=0 --> pico (we advertise our window is zero)
Now, when pico wants to send more data it is going to probe our window first, but in an incorrect way. (It sends a segment with only PSH flag, a seq nr. and no data)

There are 2 correct ways of window probing.

  • 'normal' way
    • send a packet with PSH,ACK flags on
    • seq and ack numbers incrementing in normal way
    • data = one byte
  • keep-alive way (suggested and linux-like)
    • send a packet with PSH,ACK flags on
    • seq = -1
    • no data needed

pcap:
Faulty: https://dl.dropboxusercontent.com/u/49342572/faultywindowprobe (packet 9)
Correct: https://dl.dropboxusercontent.com/u/49342572/correctwindowprobe (keep-alive packets)

@BartVolkaerts
Copy link
Author

Testcase:
sudo ./run.sh --test zerowindowprobing testcases/hardware/tcp_talk_dut_bench.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant