Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Thomas Bätzler" <t.baetzler@bringe.com>
To: netfilter@vger.kernel.org
Subject: Re: Weird nat/conntrack Problem with PASV FTP upload
Date: Mon, 23 Jun 2008 14:50:29 +0200	[thread overview]
Message-ID: <485F9C15.9080001@bringe.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806101024010.31994@blackhole.kfki.hu>

Hi,

to finish up this matter and perhaps help people who are
in the same situation as me, here's a summary.

- From the end users PoV, data connections from a ftp
client to a ftp server would sometime spontaeously break
down.

- tcpdump on the client side nat gateway showed that
the nat gateway would inject RST packets in the connection.

- Further examination involved logging packets with a
conntrack state of INVALID and proved that the packets
causing the RST reply were considered to be INVALID by
conntrack.

- Upgrading client and NAT gateway from a 2.6.18 Debian
Etch stock kernel to 2.6.25 Debian testing kernel didn't
help.

At this point more info was requested, but I couldn't
provide it in any useful form.

By chance I happend across a posting by Vladislav Kurz
last week, where he suggested to activate conntrack
logging of invalid packets by setting
/proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid
to the protocol number that one was interested in.

Now that finally gave me some useful output, namely,
"nf_ct_tcp: ACK is under the lower bound (possible overly delayed ACK)".

 From looking at my dumps I think this is probably an
error, but then I'm still digesting the small parts
of TCP/IP Illustrated that I've read so for, so I
might aswell be wrong. If somebody feels like looking
into it, let me know what you need and I'll try and
supply it.

Anyways, the quick and dirty fix to my problem was to put
"inet.ipv4.netfilter.ip_conntrack_tcp_be_liberal=1" in
/etc/systcl.conf.

Cheers,
Thomas
-- 
BRINGE Informationstechnik GmbH
Zur Seeplatte 12
D-76228 Karlsruhe
Germany

Fon: +49 721 94246-0
Fon: +49 171 5438457
Fax: +49 721 94246-66
Web: http://www.bringe.de/

Geschäftsführer: Dipl.-Ing. (FH) Martin Bringe
Ust.Id: DE812936645, HRB 108943 Mannheim

  parent reply	other threads:[~2008-06-23 12:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 12:35 Weird nat/conntrack Problem with PASV FTP upload 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 [this message]
2008-06-23 13:15     ` Jozsef Kadlecsik
  -- strict thread matches above, loose matches on Subject: below --
2008-06-09 10:36 Thomas Bätzler
2008-06-09 11:21 ` Jozsef Kadlecsik
2008-06-09  8:58 Thomas Bätzler
2008-06-09  9:14 ` Jozsef Kadlecsik
2008-06-05  9:02 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
2008-06-09  9:06       ` Jan Engelhardt
2008-06-09  9:09         ` Patrick McHardy
2008-06-09 12:38           ` Jan Engelhardt

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=485F9C15.9080001@bringe.com \
    --to=t.baetzler@bringe.com \
    --cc=netfilter@vger.kernel.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