From: Martijn Klingens <mklingens@ism.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Unexpected RSTs?
Date: Wed, 16 Oct 2002 15:36:52 +0200 [thread overview]
Message-ID: <200210161536.52930.mklingens@ism.nl> (raw)
In-Reply-To: <200210111629.26991.mklingens@ism.nl>
On Friday 11 October 2002 16:29, Martijn Klingens wrote:
> On Friday 11 October 2002 15:03, Antony Stone wrote:
> > 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!
Just did some small tests, and unfortunately this idea seems to be incorrect.
Each 'unexpected rst' has exactly *ONE* RST coming in, so it's not a duplicate
entry being dropped, it's a unique entry.
Also, the IP addresses causing unexpected RSTs are sending accepted RSTs later
on in the firewall log with a slightly higher port number, so it looks like
the senders are legitimate and not malicious users.
Do you have any other ideas why the RSTs are not accepted by the conntrack
code as 'related' ?
--
Martijn
prev parent reply other threads:[~2002-10-16 13:36 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
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 ` Martijn Klingens [this message]
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=200210161536.52930.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