From: Gustav Petersson <gustav.petersson@karlskrona.net>
To: markee@bandwidthco.com
Cc: netfilter@lists.netfilter.org
Subject: Re: how do i forward ftp from my firewall to an internal server?
Date: Mon, 01 Mar 2004 01:08:25 +0100 [thread overview]
Message-ID: <40427EF9.6090701@karlskrona.net> (raw)
In-Reply-To: <200402292315.i1TNFffG003448@server5.bandwidthco.com>
Ok, I rewrote the rules to exactly match yours except for the log level.
In the log I can only see one packet but that is ok because as I
understand it only the first packet for a connectio goes through the
PREROUTING chain. I also added a LOG for the POSTROUTING chain like this
just before my SNAT target:
iptables -t nat -A POSTROUTING -p tcp -s $LOCALNET/24 --source-port 20:21 \
-j LOG --log-prefix "SNAT FTP: "
And that doesn't show up in the log, in fact even if I remove the
--source-port argument I get nothing in the log... (is the LOG target
valid in the POSTROUTING chain?)
I am running proftpd in standalone mode with ident and reverse dns
lookups turned off, full access for everyone including anonymous. And
from proftpd (or any of the other ftp daemons I have tried) I can see a
connection being made in the log and immediately it closes again (not by
the ftp daemon). My best guess based on this is that the SNAT screws up
somewhere. Even if no data connection can be made I should at least get
the welcome message and be able to log in but I get absolutely _nothing_...
Mark E. Donaldson wrote:
>OK - seems like you left out your DNAT rule for port 20 this time. You
>could simplify that some by using just one rule. Here is how I DNAT my FTP
>servers:
>
>$IPT -t nat -A PREROUTING -p tcp --destination-port 20:21 -i $FW_INET_IFACE
>-j LOG --log-level $LOG_LEVEL --log-prefix "DNAT IN SERVICE FTP: "
>
>$IPT -t nat -A PREROUTING -p tcp --destination-port 20:21 -i $FW_INET_IFACE
>-j DNAT --to-destination $SERVICE_FTP
>
>I assume you have enabled logging (as I have done with this rule) so you can
>check you logs to see what the packets are doing?
>
>OK - now what else. The fact that your outbound is working is significant,
>and makes me think we should at applications after all. Few more questions:
>
>Is this an "anonymous" FTP server setup, or is it account authorized? Could
>there be a permissions problem within your "ftpusers" file? Is your ftp
>daemon initialized by inetd, and if so could tcpwrappers be killing the
>connections? Have you made sure that your PAM configuration is not killing
>the connections?
>
>These are mostly food-for-thought questions. I should also point out (and
>I'm sure you know this already) but once you have this debugged, you will
>want to set your default policies on INPUT and FORWARD to DROP, and then
>create the needed permit rules from there.
>
>-----Original Message-----
>From: Gustav Petersson [mailto:gustav.petersson@karlskrona.net]
>Sent: Sunday, February 29, 2004 2:11 PM
>To: markee@bandwidthco.com
>Cc: netfilter@lists.netfilter.org
>Subject: Re: how do i forward ftp from my firewall to an internal server?
>
>I cleaned up my script a bit as you suggested but with the same result.
>I should mention that outbound ftp works just fine.
>
>Here is the revised script:
>#!/bin/sh
>
>
>
>EXTIF=eth0
>INTIF=eth1
>EXTIP=213.88.181.68
>INTIP=192.168.150.3
>LOCALNET=192.168.150.0
>FTPSVR=192.168.150.10
>HTTPSVR=192.168.150.10
>
># Enable IP forwarding
>echo 1 > /proc/sys/net/ipv4/ip_forward
>
># Load modules
>modprobe ip_conntrack_ftp
>modprobe ip_nat_ftp
>
># Set default policies and flush tables
>iptables -t nat -F
>iptables -P INPUT ACCEPT
>iptables -F INPUT
>iptables -P OUTPUT ACCEPT
>iptables -F OUTPUT
>iptables -P FORWARD ACCEPT
>iptables -F FORWARD
>
># Masquerade on $EXTIF
>iptables -t nat -A POSTROUTING -o $EXTIF -s $LOCALNET/24 -d !
>$LOCALNET/24 \ # here I have tried both with and without the -d
>! $LOCALNET/24
> -j SNAT --to $EXTIP
>
># Forward ftp traffic to internal server iptables -t nat -A PREROUTING -d
>$EXTIP -p TCP --dport 21 \
> -j DNAT --to $FTPSVR:21
>
># Forward http traffic to internal server iptables -t nat -A PREROUTING -d
>$EXTIP -p TCP --dport 80 \
> -j DNAT --to $HTTPSVR:80
>
>Mark E. Donaldson wrote:
>
>
>
>>Yes - I see what you are saying now. And indeed, if your FORWARD
>>policy is set to ACCEPT, your packets should be properly DNATTED with
>>the rules you list. And you are correct, the FTPD application in use
>>would not be a factor at all here. You also seem to have all the needed
>>modules you need loaded as well. So, how do we fix this?
>>
>>First a question on your SNAT rule: iptables -t nat -A POSTROUTING -o
>>eth0 -j SNAT --to 213.88.181.68
>>
>>Is 213.88.181.68 the external IP? If so, is it the same as the
>>variable $EXP_IP is set to, and if so why not use $EXP_IP instead? I
>>would also add a -s address or network to the rule to assure only the
>>packets you want SNATTED are SNATTED. I doubt if this is causing your
>>problem, but these things need to get cleaned up to help troubleshoot the
>>
>>
>problem.
>
>
>>Next - run an lsmod after your ruleset is loaded to confirm all the
>>needed modules have loaded.
>>
>>Also - I notice you are flushing your NAT table after you have set your
>>default policies: iptables -t nat -F. I would move this up and flush
>>before the policies are set.
>>
>>Try all this and we shall go from there.
>>
>>-----Original Message-----
>>From: Gustav Petersson [mailto:gustav.petersson@karlskrona.net]
>>Sent: Sunday, February 29, 2004 11:15 AM
>>To: markee@bandwidthco.com
>>Cc: netfilter@lists.netfilter.org
>>Subject: Re: how do i forward ftp from my firewall to an internal server?
>>
>>Thanks for your reply Mark.
>>I should have explained better. I know that ftp uses two ports with a
>>different setup for active and passive mode. That is not the problem.
>>Right now I am only DNATing the control port and my INPUT,OUTPUT and
>>FORWARD chains have a default policy of ACCEPT. The rules I posted are
>>the _only_ rules I have for my firewall. The problem is that when I
>>telnet to my $EXTIP port 21 I should get a welcome message and be able
>>to send some commands but from logging all traffic to and from my
>>internal ftp server I can see the following traffic:
>>Client->FTP: SYN
>>FTP->Client: SYN ACK
>>Client->FTP: ACK
>>FTP->Client: ACK PSH
>>FTP->Client: ACK PSH
>>FTP->Client: ACK PSH
>>FTP->Client: ACK PSH
>>Client->FTP: RST
>>
>>after this short exchange the connection is terminated. If i telnet to
>>$EXTIP port 80 and do a 'GET /' everything works fine. I have tried
>>proftpd, in.ftpd, wu-ftpd and they all give the same result so it's not
>>a problem with the ftp server software.
>>
>>Gustav Petersson
>>
>>Mark E. Donaldson wrote:
>>
>>
>>
>>
>>
>>>The FTP protocol works completely differently than http, particularly
>>>in the way connections are negotiated and accepted. You must also
>>>account for both active and passive modes. I'm assuming the rules you
>>>have here are for new connections to your FTP server? What are your
>>>FTP rules for the FORWARD chain?
>>>
>>>-----Original Message-----
>>>From: netfilter-admin@lists.netfilter.org
>>>[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Gustav
>>>Petersson
>>>Sent: Saturday, February 28, 2004 12:28 AM
>>>To: netfilter@lists.netfilter.org
>>>Subject: how do i forward ftp from my firewall to an internal server?
>>>
>>>Like the subject line says.. how do I do it?
>>>
>>>I have port http traffic forwarded to the same server but when i use
>>>the same rule with only the port(s) changed for ftp traffic my ftp
>>>server opens the connection but immediately closes it again. I have
>>>tried running both the standard in.ftpd and proftpd. Any help would be
>>>
>>>
>>>
>>>
>>greatly appreciated.
>>
>>
>>
>>
>>>Gustav Petersson
>>>
>>>I am running debian 3.0 with kernel 2.4.24 and I have the following
>>>modules
>>>loaded:
>>>
>>>ipt_LOG
>>>ipt_state
>>>iptable_filter
>>>ip_nat_ftp
>>>ip_conntrack_ftp
>>>iptable_nat
>>>ip_conntrack
>>>ip_tables
>>>
>>>Here is my firewall config:
>>>#!/bin/sh
>>>
>>>EXT_IP=1.2.3.4
>>>INT_IP=192.168.x.x
>>>
>>>modprobe iptable_nat
>>>modprobe ip_conntrack_ftp
>>>modprobe ip_nat_ftp
>>>
>>>echo "1" > /proc/sys/net/ipv4/ip_forward
>>>
>>>iptables -P INPUT ACCEPT
>>>iptables -F INPUT
>>>iptables -P OUTPUT ACCEPT
>>>iptables -F OUTPUT
>>>iptables -P FORWARD ACCEPT
>>>iptables -F FORWARD
>>>iptables -t nat -F
>>>
>>># NAT
>>>iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 213.88.181.68
>>>
>>>
>>>
>>>
>>># Forward port 80 to internal server
>>>iptables -A PREROUTING -t nat -p tcp -d $EXT_IP --dport 80 \
>>> -j DNAT --to $INT_IP:80
>>>
>>># Forward ports 20 and 21 to internal server iptables -A PREROUTING -t
>>>nat -p tcp -d $EXT_IP --dport 20 \
>>> -j DNAT --to $INT_IP:20
>>>
>>>
>>>
>>>iptables -A PREROUTING -t nat -p tcp -d $EXT_IP --dport 21 \
>>> -j DNAT --to $INT_IP:21
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
>
next prev parent reply other threads:[~2004-03-01 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 8:27 how do i forward ftp from my firewall to an internal server? Gustav Petersson
2004-02-29 16:36 ` Mark E. Donaldson
2004-02-29 19:15 ` Gustav Petersson
2004-02-29 20:58 ` Mark E. Donaldson
2004-02-29 22:10 ` Gustav Petersson
2004-02-29 23:15 ` Mark E. Donaldson
2004-03-01 0:08 ` Gustav Petersson [this message]
2004-03-01 0:47 ` Mark E. Donaldson
2004-02-29 20:16 ` Jeroen Vriesman
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=40427EF9.6090701@karlskrona.net \
--to=gustav.petersson@karlskrona.net \
--cc=markee@bandwidthco.com \
--cc=netfilter@lists.netfilter.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.