From: Vitezslav Samel <vitezslav@samel.cz>
To: Patrick McHardy <kaber@trash.net>
Cc: Krzysztof Piotr Oledzki <ole@ans.pl>,
Greg Kroah-Hartman <gregkh@suse.de>,
netdev@vger.kernel.org
Subject: [BUG bisected] 2.6.30.4: NET: active FTP doesn't work
Date: Wed, 26 Aug 2009 10:33:59 +0200 [thread overview]
Message-ID: <20090826083358.GB6010@pc11.op.pod.cz> (raw)
Hi!
When testing 2.6.30.4+ kernel, I discovered active ftp does not work
anymore (2.6.30.3 is OK).
LAN internet
machine1 ------- router1 ------- machine2
Active ftp from machine1 to machine2 connects, transfers some files and
then hangs. Passive ftp works OK. The faulty box (router1)
is router/firewall and is doing NAT.
I bisected it down to commit 7500f93f415a2fc07e0031d99fa3964bf8981cfc
in linux-2.6.30.y tree ("netfilter: tcp conntrack: fix unacknowledged
data detection with NAT").
Could you, please, take look at it?
I'm open to do any tests.
Thanks,
Vita Samel
next reply other threads:[~2009-08-26 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 8:33 Vitezslav Samel [this message]
2009-08-26 12:51 ` [BUG bisected] 2.6.30.4: NET: active FTP doesn't work Patrick McHardy
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=20090826083358.GB6010@pc11.op.pod.cz \
--to=vitezslav@samel.cz \
--cc=gregkh@suse.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
/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;
as well as URLs for NNTP newsgroup(s).