From: "it clown" <suse@mailbox.co.za>
To: netfilter@lists.netfilter.org
Subject: nat and slow ftp
Date: Sun, 12 Jun 2005 13:47:58 +0200 [thread overview]
Message-ID: <web-789187132@mail01.infosat.net> (raw)
Hi All,
I would like to know if the following is the correct way to
setup my firewall rules to browse the net:
iptables -A OUTPUT -p tcp -o ppp0 --dport 53 -j ACCEPT
iptables -A OUTPUT -p udp -o ppp0 --dport 53 -j ACCEPT
iptables -A OUTPUT -p tcp -o ppp0 --dport 80 -j ACCEPT
iptables -A OUTPUT -p tcp -o ppp0 --dport 20 -j ACCEPT
iptables -A OUTPUT -p tcp -o ppp0 --dport 21 -j ACCEPT
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j
ACCEPT
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
I am using this with squid and it is working.
Is that a good way of doing things? I am nating the ports
right?
What i find is that when i browse ftp site they take ages
to display the contents. Why is this happening and i did
load ip_nat_ftp and iptables_nat.
But when i setup a forward rule for ftp it will connect
nice and quick.
Thanks
Regards
_____________________________________________________________________
For super low premiums, click here http://www.dialdirect.co.za/quote
reply other threads:[~2005-06-12 11:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=web-789187132@mail01.infosat.net \
--to=suse@mailbox.co.za \
--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