From: Joel Newkirk <netfilter@newkirk.us>
To: "Simpson, Doug" <dsimpson@friedmancorp.com>,
"'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: fw-builder
Date: Thu, 2 Jan 2003 21:01:53 -0500 [thread overview]
Message-ID: <200301022101.53365.netfilter@newkirk.us> (raw)
In-Reply-To: <20ED00AA0BC135449469D6EF0AE79C970FA3@ozlan.fcdomain.net>
On Thursday 02 January 2003 04:18 pm, Simpson, Doug wrote:
> Here is my rc.firewall that I generated using FW Builder.
> I want to add these lines -
> iptables -t nat -A POSTROUTING -p tcp --dport 110 -o eth0 -s
> $INTERNAL_IP -j SNAT --to $external_ip
> iptables -t nat -A POSTROUTING -p tcp --dport 23 -o eth0 -s
> $INTERNAL_IP -j SNAT --to $EXTERNAL_IP
> Where can I put these in the script and do I need to follow the same
> pattern as the script?
> Thank you
> Doug
> ##############################################
> #!/bin/sh
> #
> # This is automatically generated file. DO NOT MODIFY !
> #
> # Firewall Builder fwb_ipt v1.0.7-
> $IPTABLES -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> $IPTABLES -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> $IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
Right here would probably make sense. Actually you can put them
anywhere, since there are no other POSTROUTING rules in the script.
Just DON'T put them inside a loop or a conditional statement. There's
no explicit need to follow the pattern in the script, but be aware that
if you rebuild the ruleset with fw-builder you will need to manually
re-insert these afterwards, AFAIK.
j
prev parent reply other threads:[~2003-01-03 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 21:18 fw-builder Simpson, Doug
2003-01-03 2:01 ` Joel Newkirk [this message]
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=200301022101.53365.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=dsimpson@friedmancorp.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.