From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: Not NATed packets
Date: Thu, 04 May 2006 22:35:54 +0200 [thread overview]
Message-ID: <445A65AA.3070308@plouf.fr.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0604241149300.6204@tank.eu.org>
Hello,
lukas@tank.eu.org a écrit :
[...]
>> Exactly. I can see only FIN packets which are not translated. After
>> looking into conntrack table, I think MASQ ignores FIN packets that are
>> missing in conntrack table (Is it INVALID or NEW state?).
[...]
> I test it also on kernel 2.4.32-6 and its bad too.
Are you sure ? I'm surprised. Where did you get this kernel from ?
I just tested on a custom kernel 2.4.32 built from kernel.org sources
(almost standard, just a few Netfilter patch-o-matic add-ons). And my
conclusion is that unexpected TCP FIN or RST packets are classified NEW
by the connection tracking, thus creating an entry in the conntrack/NAT
table /proc/net/ip_conntrack. However, unexpected ICMP packets such as
Echo Reply or Destination Unreachable are classified INVALID.
next prev parent reply other threads:[~2006-05-04 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 15:04 Not NATed packets lukas
2006-04-23 20:35 ` Petr Pisar
2006-04-24 9:55 ` lukas
2006-05-04 20:35 ` Pascal Hambourg [this message]
2006-04-29 18:44 ` Petr Pisar
2006-04-29 19:15 ` Petr Pisar
2006-05-04 22:22 ` Pascal Hambourg
2006-05-05 17:26 ` Petr Pisar
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=445A65AA.3070308@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.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 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.