This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

The Server seems to be sending FIN Acks for sessions that aren't in the trace, goes on for awhile and then the sessions all resume.

Thanks in advance.

Uploaded here: https://www.cloudshark.org/captures/86369a51b115

asked 12 Jul, 10:31

wiskydelta's gravatar image

wiskydelta
6112
accept rate: 0%

Can you make the capture at Cloudshark publicly accessible?

(12 Jul, 10:51) sindy

Should be accessible now

(12 Jul, 12:00) wiskydelta

What do you mean by "the sessions all resume"? Strictly speaking, a TCP session cannot "resume" once finished. An application may resume conversation, using a new TCP session.

Other than that, the first FIN seems to always come from the client side, the server only responds to it.

Not knowing the application case, it is hard to say anything more. I could imagine many clients behind the same NAT device, all of which keep TCP sessions alive for a while after the last application request has been responded, and then close them gracefully (using FIN) on timeout (which is quite a rational approach given the overhead of setting up and especially tearing down a TCP session). You would have to capture for much longer to see several TCP sessions to be established and closed to make some more useful conclusions.

I would consider it some kind of attack to the client, where somebody else would send FINs in its name, expecting that the server would respond with its own FIN, but two things contradict that view:

  • new sessions from the same client side IP are successfully established,
  • there would have to be some specific bug in the TCP stack of the server that it would respond a client's FIN with its own one if the session would not exist.

But there is also a possibility that it is some security device which forges a FIN in the name of the client and handles the consequences smoothly. Can you capture also at client side in parallel to the server side to prove or deny this?

(12 Jul, 12:27) sindy

When I say resume, all communications stops and I see a ton of FIN Acks, when they stop then the sessions start establishing correctly again and working. Working on getting a client capture now.

(12 Jul, 13:24) wiskydelta
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×75
×52
×21
×6

question asked: 12 Jul, 10:31

question was seen: 847 times

last updated: 12 Jul, 13:24

p​o​w​e​r​e​d by O​S​Q​A