From: Martin Renold <martinxyz@gmx.ch>
To: Harald Welte <laforge@gnumonks.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [patch] tcp connection tracking 2.4.19
Date: Thu, 17 Oct 2002 22:29:35 +0200 [thread overview]
Message-ID: <20021017202935.GA5067@old.homeip.net> (raw)
In-Reply-To: <20021016224643.GC2408@naboo.club.berlin.ccc.de>
On Thu, Oct 17, 2002 at 12:46:43AM +0200, Harald Welte wrote:
> On Wed, Oct 16, 2002 at 09:48:37AM +0200, Martin Renold wrote:
> The question is whether this is really to be called a 'bug'. Netfilter
> connection tracking never claimed to do full state tracking, neither did
> it claim to do sequence number tracking. It does all it can without
> tracking sequence/ack numbers and window sizes.
>
> You can also send FIN flagged packets with a wrong sequence number to
> terminate a connection (conntrack entry, that is).
Well, I think the point is that if somebody sends a bad FIN (or RST)
packet, he has to know both used port numbers, and even then I perhaps
wouldn't care, I would still be able to establish a new connection.
I do not want a full state tracking, I just don't like being shut out of
my system for several days. And I called it a bug because one half of the
code to handle this situation was already there.
bye,
Martin
next prev parent reply other threads:[~2002-10-17 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 7:48 [patch] tcp connection tracking 2.4.19 Martin Renold
2002-10-16 22:46 ` Harald Welte
2002-10-17 20:29 ` Martin Renold [this message]
2002-10-17 8:26 ` Svenning Sorensen
2002-10-17 8:53 ` Martin Renold
-- strict thread matches above, loose matches on Subject: below --
2002-10-08 20:50 Martin Renold
2002-10-08 21:06 ` Roberto Nibali
2002-10-09 12:30 ` Gianni Tedesco
2002-10-09 17:25 ` Roberto Nibali
2002-10-10 10:38 ` Gianni Tedesco
2002-10-10 18:06 ` Roberto Nibali
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=20021017202935.GA5067@old.homeip.net \
--to=martinxyz@gmx.ch \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@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.