From: "Stephan Higuti" <higuti.sam@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help!
Date: Thu, 1 Jun 2006 09:05:59 -0300 [thread overview]
Message-ID: <3da957060606010505x2744ca27x85a51e9f1961ae36@mail.gmail.com> (raw)
In-Reply-To: <a919cbc70606010501r73a6f23ds5405eeb94a4b1942@mail.gmail.com>
thank'z Manish!
But i dont understant what you mean here:
> In ur scenario u will require only PREROUTING rule, but if want to
> access internet behind ur friewall, then need the POSTROUTING rule
> also. Choice is URs.
If i want that my servers access internet?
On 6/1/06, manish Jamwal <manish.jamwal@gmail.com> wrote:
> Hi
> When the server's r behind the firewall, u only need PREROUTING rule
> with target as DNAT.
> The POSTROUTING rule is required when ur traffic will be outwards,
> means u access the server's which are on ur WAN side.
> In ur scenario u will require only PREROUTING rule, but if want to
> access internet behind ur friewall, then need the POSTROUTING rule
> also. Choice is URs.
> This information is as per my knowledge. :)
> Manish
>
> On 6/1/06, Stephan Higuti <higuti.sam@gmail.com> wrote:
> > Hello guys....
> > I have a question about PREROUTING and POSTROUTING.
> > I'm making a new firewall script.....
> > In this script, i put some PREROUTING rules , ex:
> >
> > ####################### Apache ##########################
> > iptables -t nat -A PREROUTING -d 200.xxx.yyy.zzz -p tcp --dport 80 -j
> > DNAT --to-destination 192.168.23.7:80
> >
> > But i need to put some POSTROUTING rules to this?
> > My situation: My firewall will reply for 4 differents Ip's (reals) ,
> > one for apache , other for e-mail server, etc............
> > This PREROUTING rule get a pack that come from internet to a IP "x" ,
> > and i want that all that incoming to this ip , to be forward to my
> > internal ip.
> > So , i think that PREROUTING rules its right... but i dont if i need
> > to create a POSTROUTING for this.....
> > Waiting Help....
> >
> > p.s.:* Sorry for my bad, bad english =D
> >
> > Cheers
> >
> > --
> > ---------------------------------------------------------------------
> > Stephan Higuti
> > MSN: higutisam@hotmail.com
> > Email: higuti@fai.com.br
> > ---------------------------------------------------------------------
> >
> >
>
--
---------------------------------------------------------------------
Stephan Higuti
MSN: higutisam@hotmail.com
Email: higuti@fai.com.br
Técnico em Informática
Adm servidores Linux
FAI - Faculdades Adamantinenses Integradas
---------------------------------------------------------------------
next prev parent reply other threads:[~2006-06-01 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 11:53 Help! Stephan Higuti
[not found] ` <a919cbc70606010501r73a6f23ds5405eeb94a4b1942@mail.gmail.com>
2006-06-01 12:05 ` Stephan Higuti [this message]
2006-06-01 12:07 ` Help! Sietse van Zanen
2006-06-01 12:34 ` Help! Stephan Higuti
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 12:00 Help!!! Baake, Matthias
2005-06-23 11:50 Help!!! radu
2005-06-23 12:14 ` Help!!! /dev/rob0
2005-06-23 14:35 ` Help!!! Jason Opperisano
2004-03-30 1:15 Help! btjiang
2003-07-18 15:22 help!! Tuyo Board Unilago
2002-09-06 14:58 Help!!! Bharat (Hotmail Mithibaiguy)
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=3da957060606010505x2744ca27x85a51e9f1961ae36@mail.gmail.com \
--to=higuti.sam@gmail.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