From: "Stephan Higuti" <higuti.sam@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help!
Date: Thu, 1 Jun 2006 09:34:24 -0300 [thread overview]
Message-ID: <3da957060606010534x7f0c15fcs676c0bc29d24c6a2@mail.gmail.com> (raw)
In-Reply-To: <02BB8A4AC86C564C89C7F14CF98CE0C4012783@knowledge.wizdom.nu>
thankz for help guys!
So , its right my rule?
Anyway... look this image:
http://img180.imageshack.us/my.php?image=firewallsemip2ok.jpg
My eth0 reply for 4 reals ip's...
And forward the packs to my servers......... so , PREROUTING its the
right way to do this?
Thank's a lot!
On 6/1/06, Sietse van Zanen <sietse@wizdom.nu> wrote:
> You are doing it exactly as it should be done.
>
> DNAT rules go to PREROUTING CHAIN (as you first want to set the new destination and the do routing)
> SNAT rules go to POSTROUTING (usually, as it wouldn't really matter where they go, unless you do source routing).
>
> Ofcourse you will need to ACCEPT the connections in your filter table too.
>
> -Sietse
>
> ________________________________
>
> From: netfilter-bounces@lists.netfilter.org on behalf of Stephan Higuti
> Sent: Thu 01-Jun-06 13:53
> To: netfilter@lists.netfilter.org
> Subject: Help!
>
>
>
> 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:34 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 ` Help! Stephan Higuti
2006-06-01 12:07 ` Help! Sietse van Zanen
2006-06-01 12:34 ` Stephan Higuti [this message]
-- 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=3da957060606010534x7f0c15fcs676c0bc29d24c6a2@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