From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Erick Sanz' <esanz@minorplanetusa.com>, netfilter@lists.netfilter.org
Subject: RE: RESEND: ip_conntrack_ftp and port forwarding
Date: Wed, 9 Jun 2004 20:01:09 -0700 [thread overview]
Message-ID: <200406100301.i5A31CN5027848@server5.bandwidthco.com> (raw)
In-Reply-To: <FLECICIIDHIEIENHHOOLAEFCCBAA.esanz@minorplanetusa.com>
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Erick Sanz
Sent: Tuesday, June 08, 2004 11:08 AM
To: netfilter@lists.netfilter.org
Subject: RESEND: ip_conntrack_ftp and port forwarding
All,
I sent the bellow message yesterday, but got no answers.
I am sure it did not get there; if it did, sorry for the repost.
The question is, can I have an internal FTP server? the firewall
would have to FORWARD the connections to port 21, and then ip_conntrack_ftp
would have to allow the rest of the communication in... Does this work?
For more information, please read bellow message...
is there anybody using it?
Best regards,
Erick
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Erick Sanz
> Sent: Monday, June 07, 2004 12:30 PM
> To: netfilter@lists.netfilter.org
> Subject: ip_conntrack_ftp and port forwarding
>
>
>
> All,
>
> I have a firewall at home protecting a web server (personal stuff);
I
> would like to add ftp capabilities in order to upload files from work,
> so I can work home.
>
> ASCII diagram:
>
>
> DSL -- Firewall -- Web server / FTP server
>
>
> My current rules to allow http are (no other rules included):
>
>
> iptables -t nat -A PREROUTING -p tcp -d 172.16.1.34 --dport 80 -j DNAT \
> --to 192.168.0.20
> iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
>
> iptables -A FORWARD -i eth0 -p tcp -d 192.168.0.20 --dport 80 -m state \
> --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -i
eth1
> -p tcp -s 192.168.0.20 --source-port 80 -j \
> ACCEPT
>
> I know I need to use ip_conntrack_ftp; however I am not sure if it
> allows port forwarding...
>
> Really basic question, but I was wondering what everybody is
doing...
>
> Best regards,
> Erick
>
>
> This email message has been scanned for viruses.
>
>
>
>
> This email message has been scanned for viruses.
>
You seem to have most of this correct, but don't make it more difficult than
it really is. You basically only need to do three things:
1. DNAT the packets to your FTP server
2. Accept the DNATted packets in the FORWARD chain
3. Let connection tracking handle the rest
By the way: what's with the port 80?
########################################################
This message has been scanned for viruses and dangerous
content by MailScanner, and is believed to be clean.
postmaster@bandwidthco.com
MailScanner at bandwidthco.com is for your absolute protection.
########################################################
next prev parent reply other threads:[~2004-06-10 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 11:17 smtp azeem ahmad
2004-05-14 11:37 ` smtp Gavin Hamill
2004-06-07 17:29 ` ip_conntrack_ftp and port forwarding Erick Sanz
2004-06-08 18:08 ` RESEND: " Erick Sanz
2004-06-10 3:01 ` Mark E. Donaldson [this message]
2004-05-14 12:46 ` smtp Antony Stone
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=200406100301.i5A31CN5027848@server5.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=esanz@minorplanetusa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox