Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: not sure ESTABLISHED TCP traffic will have ACK flag setalways...
Date: Fri, 8 Apr 2005 16:01:49 -0500	[thread overview]
Message-ID: <006901c53c7e$2ead1c90$f5001eac@riverview.office> (raw)
In-Reply-To: 20050408205224.GA15635@vetz.homelinux.org

> This problem is resolved by the TCP window? Am I right?

If the ""problem that you are referring to is how many unACKed packets can
be sent by either side before it retransmits the packet that has not been
ACKed, then Yes this number is controlled by the TCP Window size.  The TCP
Window size is asically the number of TCP packets that can be sent out and
still on the wire before the sender resends a packet assuming that it was
dropped.

> One side CAN send more packets.

Yes I believe that this is correct.  Any packets sent by the server MUST be
ACKed by the client, but the client could ACK the SYN number of a packet
sent later in the conversation thus ACKing all packets that were sent up to
the point just prior to the number that was ACKed.  What??? When a packet is
ACKed, the ACK number is the number of the next sequence number that the
receiving system is expecting to receive from the server.  Thus if I have
received packets 1234, 1235, 1236, and 1237 from you I would send a packet
back to you with an ACK of 1238 statin gthat I'm expecting your next
sequence number to be 1238 effectively ACKing all packets up to and
including 1237.



Grant. . . .



  reply	other threads:[~2005-04-08 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 15:57 not sure ESTABLISHED TCP traffic will have ACK flag set always Christian Seberino
2005-04-08 19:59 ` Taylor, Grant
2005-04-08 20:52 ` Michele Vetturi
2005-04-08 21:01   ` Taylor, Grant [this message]
2005-04-09  6:24     ` not sure ESTABLISHED TCP traffic will have ACK flag setalways seberino
2005-04-09 18:33       ` Grant Taylor
2005-04-10  3:23         ` seberino
2005-04-10  5:09           ` Grant Taylor
2005-04-10  3:54         ` seberino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006901c53c7e$2ead1c90$f5001eac@riverview.office' \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox