Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Jay Levitt <lists-netfilter@shopwatch.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: RST instead of FIN?
Date: Sun, 11 Apr 2004 06:00:40 -0400	[thread overview]
Message-ID: <1081677639.2013.11.camel@grendel> (raw)
In-Reply-To: <05c301c41f2a$4a6ef650$9701a8c0@office>

On Sat, 2004-04-10 at 14:33, Jay Levitt wrote:
>
> sourceforge: [SYN]
> me: [SYN, ACK]
> sourceforge: [ACK]
> [SMTP conversation ensues, switches to TLS, sends me an e-mail.  at
> the end..]
> me: [RST]

Weird. Are you sure this is not a RST/ACK? 

> sourceforge: [FIN, ACK]

Looks like the RST was ignored (although hard to say since you did not
include time stamps). Does the source MAC on the RST match your system?
When I've seen this in the past its been an IDS or IPS attempting to
reset the session due to a suspicious payload, but they get the sequence
numbers wrong. Thus the RST/ACK gets ignored and the session continues.

> me: [RST]
> me: [RST]

If this is an RST rather than a RST/ACK, it could be your system is
losing session info and handling the ACKs like they are new packets
(maybe some kind of broken IP wrapper application?). The second RST is
*really* odd as its an error packet without any stimulus. That's not
suppose to happen. 

I'm guessing this is not the kernel or Sendmail, but I'm honestly not
sure what it is.

Happy hunting,
Chris




  parent reply	other threads:[~2004-04-11 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 18:33 RST instead of FIN? Jay Levitt
2004-04-10 22:54 ` Antony Stone
2004-04-11  5:41   ` Jay Levitt
2004-04-11 10:00 ` Chris Brenton [this message]
2004-04-11 18:01   ` Jay Levitt
2004-04-12 19:33     ` Ranjeet Shetye

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=1081677639.2013.11.camel@grendel \
    --to=cbrenton@chrisbrenton.org \
    --cc=lists-netfilter@shopwatch.org \
    --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