From: Richmond Dyes <rdyes@monroehosp.org>
To: "Taylor, Grant" <gtaylor@riverviewtech.net>
Cc: "Netfilter (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: Problem with re-directing from 2 sources to one server
Date: Mon, 11 Dec 2006 15:06:21 -0500 [thread overview]
Message-ID: <457DBA3D.8080206@monroehosp.org> (raw)
In-Reply-To: <457D7C57.3090301@riverviewtech.net>
Thanks by putting the output device in, it worked.
Taylor, Grant wrote:
> Richhmond Dyes wrote:
>> I have a server that I have to reach from 2 different networks, the
>> Internet and another private network called downtown and I also have to
>> reach from the server both networks. If I have one of the set of rules
>> running, it works fine, but if I put both set of rules on, it doesn't
>> work. below are my set of rules. Can anyone tell me a how this can be
>> done?
>>
>> Here is the setup.
>> mynetwork 172.31.0.0/21
>> eth0 172.31.4.254 my network interface
>> eth1 192.168.14.1 interface to downtown which on that network's side
>> routes to 10.0.0.0/9
>> eth2 publicIP to the internet
>> publicnetwork.100 is the virtual address on eth2 called eth2:100
>> 172.31.5.100 is the private ip address of the server I want reached
>> 192.168.14.10 is the virtual ip address on eth1 called eth1:10
>
> What you are wanting to do is a simple enough request and should be
> possible to do.
>
>> $IPT -t nat -A PREROUTING -d publicnetwork.100 -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
>> publicnetwork.100
>>
>> $IPT -t nat -A PREROUTING -d 192.168.14.10 -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
>> 192.168.14.10
>
> I believe your two POSTROUTING rules are the problem here. Both rules
> SNAT *ANY* traffic from your internal server. I would alter the rules
> so that they only applied on traffic as it left your two different
> network interfaces.
>
> I.e.
>
> $IPT -t nat -A POSTROUTING -o eth2 -s 172.31.5.100 -j SNAT --to-source
> publicnetwork.100
>
> and
>
> $IPT -t nat -A POSTROUTING -o eth1 -s 172.31.5.100 -j SNAT --to-source
> 192.168.14.10
>
>
>> Then I forward all my 10.0.0.0/9 ip requests to downtown
>>
>> $IPT -A FORWARD -m state --state NEW -i eth0 -s 172.31.0.0/21 -o eth1
>> -d 10.0.0.0/8 -j ACCEPT
>>
>> Then I forward ip requests from downtown for the server to it.
>> $IPT -A FORWARD -i eth1 -s 10.0.0.0/8 -d 172.31.5.100 -m state --state
>> NEW -j ACCEPT
>>
>> Then I forward ip request from the internet to the server.
>> $IPT -A FORWARD -i eth2 -s 0/0 -o eth0 -d 172.31.5.100 -m state --state
>> NEW -m multiport -p tcp --dport 22,80,1352 -j ACCEPT
>>
>> Again when I have both set of rules on, it does not work. any ideas?
>
>
>
> Grant. . . .
prev parent reply other threads:[~2006-12-11 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 2:46 Problem with re-directing from 2 sources to one server Richhmond Dyes
2006-12-10 14:49 ` former03 | Baltasar Cevc
2006-12-11 15:29 ` Richmond Dyes
[not found] ` <457D7C57.3090301@riverviewtech.net>
2006-12-11 20:06 ` Richmond Dyes [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=457DBA3D.8080206@monroehosp.org \
--to=rdyes@monroehosp.org \
--cc=Richmond.Dyes@monroehosp.org \
--cc=gtaylor@riverviewtech.net \
--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