From: "Thomas Bätzler" <t.baetzler@bringe.com>
To: netfilter@vger.kernel.org
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: Weird nat/conntrack Problem with PASV FTP upload
Date: Wed, 11 Jun 2008 10:50:45 +0200 [thread overview]
Message-ID: <484F91E5.8040807@bringe.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806101024010.31994@blackhole.kfki.hu>
Hi,
Jozsef Kadlecsik schrieb:
> In the first dump there is no dropped packet and the second one contains a
> single packet. Neither of the dumps help. I need a full record of a TCP
> session in which packets were marked as INVALID. If you can attach the log
> record, that'd be even better.
Sorry, my fault.
Here's what I've done now:
- "tcpdump -s0" on the external interface
- I log invalid packets using this iptables rule:
iptables -t mangle -A PREROUTING -m state --state INVALID -j LOG
- locate "invalid" dropped in kernel.log
- tcpdump -r -w on port identified above to create a session dump.
I've uploaded such a session dump and the corresponding log line to
http://baetzler.de/sandbox/dump.tar.bz2
I'm running a Debian flavour 2.6.25 kernel (nf_conntrack version 0.5.0
(16384 buckets, 65536 max)).
If there's a better/different method to do this or to get additional
debugging info, please let me know. I'm currently running a kernel
compiled with debugging info for netfilter enabled, but this does not
seem to produce any additional output in kernel.log.
TIA,
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
next prev parent reply other threads:[~2008-06-11 8: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 [this message]
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
-- 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=484F91E5.8040807@bringe.com \
--to=t.baetzler@bringe.com \
--cc=kadlec@blackhole.kfki.hu \
--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 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.