From: "Ron Lai" <ronlai@cs.stanford.edu>
To: "Patrick McHardy" <kaber@trash.net>
Cc: <netfilter@vger.kernel.org>,
"Netfilter Development Mailinglist"
<netfilter-devel@vger.kernel.org>
Subject: Re: Problems with nf_nat_ftp.ko and nf_conntrack_ftp.ko in 2.6.22.6
Date: Wed, 24 Oct 2007 05:24:34 -0700 [thread overview]
Message-ID: <002401c81638$d97f2ff0$050ba8c0@FireEye.com> (raw)
In-Reply-To: 471DF457.3010404@trash.net
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
The packet dump from the 2.6.22.6 box in the middle is attached. In the
trace 172.16.119.91 is the original IP address of the FTP client and
172.16.255.123 is the NATted address. The FTP server's address is
172.16.118.1.
The problem happens between packet 31 and packet 34. Packet 31 indicates
that the client expects ACK number 0x64b4dda9 for the PORT command it sends.
However, the ACK number it actually gets is 0x64b4dda8.
Ron
----- Original Message -----
From: "Patrick McHardy" <kaber@trash.net>
To: "Ron Lai" <ronlai@cs.stanford.edu>
Cc: <netfilter@vger.kernel.org>; "Netfilter Development Mailinglist"
<netfilter-devel@vger.kernel.org>
Sent: Tuesday, October 23, 2007 6:17 AM
Subject: Re: Problems with nf_nat_ftp.ko and nf_conntrack_ftp.ko in 2.6.22.6
> Please send bugreports to netfilter-devel.
>
> Ron Lai wrote:
>> Hi all,
>> My 2.6.22.6 Linux box is acting as a NAT device. I found that a NATted
>> FTP client is having problem using active mode to connect to a outside
>> FTP server. (Passive mode works fine.)
>>
>>> From the trace I could see that the PORT command from the FTP client is
>> correctly modified by the Linux box to use the converted NAT address.
>> However, the confirmation from the server never makes it to the client
>> and the client just keeps retransmitting the PORT command packet.
>
>
> Do you mean it never makes it to the FTP client or to the machine
> where the client is running?
>
>> The interesting part is that active mode can work if the length of the
>> actual IP address of the client is the same as the length of the
>> converted NAT address. It looks like if there is no TCP sequence number
>> modification by the Linux box, the FTP connection can work properly in
>> active mode. I am suspecting that there may a problem in the TCP sequence
>> number tracking in the kernel modules.
>>
>> The same settings work fine when I try with Linux 2.6.15 loading
>> ip_nat_ftp.ko and ip_conntrack_ftp.ko. Did I miss anything in configuring
>> the Linux 2.6.22.6 box?
>
>
> Works fine here. Please post the dump, ideally from a box in the
> middle.
> -
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: ftp_test.pcap --]
[-- Type: application/octet-stream, Size: 5737 bytes --]
next prev parent reply other threads:[~2007-10-24 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001f01c8142e$e6a67960$ea50f53c@FireEye.com>
2007-10-23 13:17 ` Problems with nf_nat_ftp.ko and nf_conntrack_ftp.ko in 2.6.22.6 Patrick McHardy
2007-10-24 12:24 ` Ron Lai [this message]
2007-10-29 12:51 ` 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='002401c81638$d97f2ff0$050ba8c0@FireEye.com' \
--to=ronlai@cs.stanford.edu \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).