From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: quick questions ---
Date: Thu, 27 Nov 2003 13:12:01 +0000 [thread overview]
Message-ID: <200311271312.01582.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <FDB52A0429DFD31196FB0008C7D972D50EA57B26@OST_EXCH_USR5>
On Thursday 27 November 2003 1:02 pm, Knight, Steve wrote:
> Hi chaps
>
> Had a bit of a google, and of course consulted Ziegler, but I'm still not
> 100% on either of these, so ---
>
> 1) can iptables use eth0:0 as a valid interface distinct from eth0 ?
No. They're both the same physical device, and netfilter only knows it as
eth0.
> So I can use eth0 as LAN internal i/f and eth0:0 as DMZ internal i/f.
You can if you really want to but nobody here will respect you for it :)
I almost completely blows away the concept of a DMZ - because somebody on your
internal LAN can get unrestricted access to the DMZ machines simply by
changing their IP address.
> and ...
>
> 2) Back when I did my checkpoint certs we covered "static NAT" - simple
> one-to-one address translation, rather than "hide NAT" - aka iptables SNAT
> / MASQUERADE....
>
> ...the question I have is -
>
> is the example given in Ziegler starting on p280 and table 7.1 "Host
> Forwarding to Servers in a Privately Addressed DMZ" an example of "static
> NAT"?
Please can you rephrase the question so that we can answer it without needing
a copy of the book?
Antony.
--
All matter in the Universe can be placed into one of two categories:
1. Things which need to be fixed.
2. Things which need to be fixed once you've had a few minutes to play with
them.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2003-11-27 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 13:02 quick questions --- Knight, Steve
2003-11-27 13:12 ` Antony Stone [this message]
2003-11-27 13:13 ` Ray Leach
2003-11-27 13:26 ` Cedric Blancher
-- strict thread matches above, loose matches on Subject: below --
2003-11-27 14:13 Knight, Steve
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=200311271312.01582.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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