All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henning Riis Rasmussen" <hrr@indbakke.dk>
To: netfilter@lists.netfilter.org
Subject: DNAT and IP aliasing - how?
Date: Mon, 10 Mar 2003 12:02:00 +0100	[thread overview]
Message-ID: <001701c2e6f4$79edee00$85200f0a@smaug> (raw)

Hi all

I'm setting up a firewall using kernel 2.4.20 with iptables 1.2.7a (and some
patches).

The firewall has 3 NICS:

  LAN0  (Local protected network)
  WAN1  (Sister organisation)
  INET2 (Internet)

IP adresses used on LAN and WAN are not routable and must therefore all be
translated by the firewall (i.e. WAN can not route the addresses belonging
to LAN).

Generally hosts on the LAN accessing the WAN should be SNAT'ed behind the
WAN1 interface (and this is no problem).

But at the same time some host on the LAN need to provide services to hosts
on the WAN. And there need to be more than one LAN host providing the same
service (i.e. "DNS") with no possibility of moving that service to another
port.

Hence, I need WAN1 to have more than one IP address (i.e. 10.0.0.1/24,
10.0.0.2/24 and 10.0.0.3/24).

I assume I should use DNAT to provide the address translation needed for the
hosts on the LAN that must be visible on the WAN. But what am I supposed to
do about getting arp responses for the extra IP addresses on the WAN1
interface? I recall using the kernel IP aliasing option in previous setups,
but this is no longer an option in kernel 2.4.20 (as far as I can tell).

What is the "correct" way to set this up?

Regards,
Henning




             reply	other threads:[~2003-03-10 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 11:02 Henning Riis Rasmussen [this message]
2003-03-11 14:10 ` DNAT and IP aliasing - how? Joel Newkirk
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 17:16 Elmshauser, Erik

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='001701c2e6f4$79edee00$85200f0a@smaug' \
    --to=hrr@indbakke.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.