All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Christian Seberino <seberino@spawar.navy.mil>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: TCP packets with RST flag set but **not** ACK flag OK??
Date: Mon, 11 Apr 2005 15:49:21 -0400	[thread overview]
Message-ID: <1113248961.2151.12.camel@grendel> (raw)
In-Reply-To: <1113247121.3544.118.camel@seberino.spawar.navy.mil>

On Mon, 2005-04-11 at 15:18, Christian Seberino wrote:
>
> I think RFC 793 requires TCP stacks to send RSTs if they
> get packets not meant for them in some cases.  Anyone know which
> cases?

Pretty much all. The exceptions I can think of off the top of my head:
In response to a RST
In response to a FIN to an open port (MS returns a RST/ACK)

> For example, I think closed ports must send RSTs if they
> get stuff.

Agreed.

> Even if YES, it seems a firewall could drop any RSTs that
> don't have ACK set without damage right?

The only condition I can think of off the top of my head that will
return a RST instead of a RST/ACK is in response to an unsolicited ACK
sent to either an open or closed port. So they do happen in the wild.

HTH,
Chris







  reply	other threads:[~2005-04-11 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 19:18 TCP packets with RST flag set but **not** ACK flag OK?? Christian Seberino
2005-04-11 19:49 ` Chris Brenton [this message]
2005-04-11 21:57 ` Taylor, Grant
2005-04-12  0:36   ` Chris Brenton
2005-04-12  2:32     ` Grant Taylor
2005-04-12  4:06       ` Chris Brenton
2005-04-12  4:01         ` Taylor Grant
2005-04-12  7:24         ` Taylor Grant
2005-04-12 14:41           ` Chris Brenton
2005-04-12  4:22     ` Taylor Grant

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=1113248961.2151.12.camel@grendel \
    --to=cbrenton@chrisbrenton.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=seberino@spawar.navy.mil \
    /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.