Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martijn Klingens <mklingens@ism.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Unexpected RSTs?
Date: Fri, 11 Oct 2002 16:29:26 +0200	[thread overview]
Message-ID: <200210111629.26991.mklingens@ism.nl> (raw)
In-Reply-To: <200210111303.g9BD3mL19306@vulcan.rissington.net>

On Friday 11 October 2002 15:03, Antony Stone wrote:
> Depending on what else you're logging, 15% of your log entries could be a
> lot of packets, could be only a few....

It's thousands of them ;-)

(And the timeframe was only a day or so...)

> I'd expect the reason might be a system sending two RST packets (I believe
> this is quite common, but I haven't done any specific network sniffing to
> check it out).   The first one takes down the connection so it is no longer
> ESTABLISHED, the second one gets logged because it doesn't correspond to an
> established connection...

Hmm, besides the obvious questions *why* the second RST is sent and why 
conntrack doesn't have provisions for ignoring subsequent RSTs for a short 
amount of time the reasoning itself makes sense.

> Maybe you could try putting a LOG rule to catch *all* RSTs at the beginning
> of your rules (before even the ESTABLISHED, RELATED rule) and see if this
> shows they are coming along in pairs ?

Good idea. I'm not going to modify the firewall so close before the weekend, 
but will do so next monday. Thanks for the tip and I'll let you know about 
the results!
-- 
Martijn



  reply	other threads:[~2002-10-11 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11 12:34 Unexpected RSTs? Martijn Klingens
2002-10-11 13:03 ` Antony Stone
2002-10-11 14:29   ` Martijn Klingens [this message]
2002-10-11 16:07     ` Send mail Secure(SSL): No, Socket Error Sundaram Ramasamy
2002-10-11 17:20       ` Antony Stone
2002-10-16 13:36     ` Unexpected RSTs? Martijn Klingens

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=200210111629.26991.mklingens@ism.nl \
    --to=mklingens@ism.nl \
    --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