From: Rahul Jadhav <rahul@iatp.org>
To: Ben Russo <ben@umialumni.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: problems with nat
Date: Wed, 13 Nov 2002 14:01:15 -0600 [thread overview]
Message-ID: <3DD2AF8B.7030904@iatp.org> (raw)
In-Reply-To: 1037215251.7329.2.camel@ben.mis.tnsi.com
Ben Russo wrote:
>Since you are working on this anyway....
>
>For a slightly more secure setup, you might want to consider:
>
>
> R E I
> T+--------+ X+--------+N
> internet |---|R| router |---|T|firewall|T|---| intranet
> I+--------+ I+--------+I
> P P | P
> |
> DMZ IP
> \
> | HTTP, MAIL, SSH
>
>This will protect your servers from other intranet users
>on the same subnet. (Also if you have 802.11 on your intranet...)
>
>Maybe after doing this your problem will disappear simply by
>rethinking the ruleset.
>
>-Ben.
>
>
>On Wed, 2002-11-13 at 13:13, Rahul Jadhav wrote:
>
>
>>please check the attachment...
>>
>>Thanks
>>Rahul
>>
>>
You are right but I am trying to avoid doing that right now as i have
invested a lot of time already into this system. Moreover, I am pretty
sure there are people who have got iptables working with a setup like mine.
next prev parent reply other threads:[~2002-11-13 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 18:13 problems with nat Rahul Jadhav
2002-11-13 19:20 ` Ben Russo
2002-11-13 20:01 ` Rahul Jadhav [this message]
2002-11-16 18:58 ` Joel Newkirk
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 15:15 Problems with NAT Jose Luis Hime
2003-05-29 15:55 ` Ray Leach
2003-05-29 17:15 ` Jose Luis Hime
2003-05-30 6:04 ` Ray Leach
2003-05-29 22:09 George Vieira
2003-05-29 23:02 ` Jose Luis Hime
2003-05-30 1:59 ` Matt Hellman
2003-05-30 2:01 ` Matt Hellman
2003-05-30 2:30 George Vieira
2003-05-30 6:57 George Vieira
2003-09-27 16:44 Adam Mercer
2003-09-28 3:30 ` Mark E. Donaldson
2003-09-28 7:36 ` Adam Mercer
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=3DD2AF8B.7030904@iatp.org \
--to=rahul@iatp.org \
--cc=ben@umialumni.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