From: Grant Taylor <gtaylor@riverviewtech.net>
To: Netfilter User Mailing List <netfilter@lists.netfilter.org>
Subject: Re: RST packets
Date: Wed, 27 Jul 2005 00:28:03 -0500 [thread overview]
Message-ID: <42E71B63.90606@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0507181604210.26471@yvahk01.tjqt.qr>
>
>
>a simple question, though I could not clearly read it from the TCP RFC...
>do RST packets always have ACK set?
>
If memory serves me right the appearance of the ACK flag in a packet
with the RST flag is based on the packet that the packet with the RST
flag is setting. In other words if the packet that is being reset has
the ACK flag set then the ACK flag will not be set in the packet with
the RST flag. Conversely if the packet that is being reset does not
have the ACK flag set then the ACK flag will be set in the packet with
the RST flag. Translation I think it is an XOR issue.
Note: This was based on many hours of reading and following RFCs and
other things. This was the simplest summarization that I could find at
the time. I think I have a different reply to this mail list talking
about using the recent match extension to test for stray RST packets, I
could look back and see what I can find in my notes if you would like me to.
Grant. . . .
next prev parent reply other threads:[~2005-07-27 5:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 14:04 RST packets Jan Engelhardt
2005-07-18 14:12 ` Rob Sterenborg
2005-07-18 16:39 ` R. DuFresne
2005-07-18 18:27 ` Jozsef Kadlecsik
2005-07-27 5:28 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 6:43 Jan Engelhardt
2005-07-21 7:42 ` Rob Sterenborg
2005-07-21 10:56 ` Jörg Harmuth
2004-08-11 21:00 Peter Marshall
2004-08-12 16:58 ` Peter Marshall
2004-08-13 15:17 ` Chris Brenton
2004-08-16 12:17 ` Peter Marshall
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=42E71B63.90606@riverviewtech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.