From: Patrick McHardy <kaber@trash.net>
To: "Thomas Bätzler" <t.baetzler@bringe.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Weird nat/conntrack Problem with PASV FTP upload
Date: Fri, 06 Jun 2008 17:02:12 +0200 [thread overview]
Message-ID: <48495174.30909@trash.net> (raw)
In-Reply-To: <484941F6.9080701@bringe.com>
Thomas Bätzler wrote:
> Patrick McHardy wrote:
>> I guess you're seeing INVALID packets (from the view of conntrack)
>> and they're thus not NATed but delivered locally, causing a RST.
>> Does dropping -m state --state INVALID packets in PREROUTING make
>> any difference?
>
> I've tried that for a day, to no avail:
> ..
> My nat rules currently look like this:
>
> iptables -t nat -A PREROUTING -m state --state INVALID -j LOG
> iptables -t nat -A PREROUTING -m state --state INVALID -j DROP
These rules need to go in mangle, that nat table is only
traversed for the first packet of a connection.
next prev parent reply other threads:[~2008-06-06 15:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:02 Weird nat/conntrack Problem with PASV FTP upload Thomas Bätzler
2008-06-05 13:59 ` Patrick McHardy
2008-06-06 13:56 ` Thomas Bätzler
2008-06-06 15:02 ` Patrick McHardy [this message]
2008-06-09 9:06 ` Jan Engelhardt
2008-06-09 9:09 ` Patrick McHardy
2008-06-09 12:38 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2008-06-09 8:58 Thomas Bätzler
2008-06-09 9:14 ` Jozsef Kadlecsik
2008-06-09 10:36 Thomas Bätzler
2008-06-09 11:21 ` Jozsef Kadlecsik
2008-06-09 12:35 Thomas Bätzler
2008-06-09 12:53 ` Jozsef Kadlecsik
2008-06-10 8:28 ` Jozsef Kadlecsik
2008-06-11 8:50 ` Thomas Bätzler
2008-06-23 10:49 ` Jozsef Kadlecsik
2008-06-23 13:46 ` Thomas Bätzler
2008-06-25 9:47 ` Thomas Bätzler
2008-06-25 9:50 ` Jozsef Kadlecsik
2008-06-23 12:50 ` Thomas Bätzler
2008-06-23 13:15 ` Jozsef Kadlecsik
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=48495174.30909@trash.net \
--to=kaber@trash.net \
--cc=netfilter@vger.kernel.org \
--cc=t.baetzler@bringe.com \
/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.