From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: NETMAP of destination *after* routing
Date: Thu, 07 Aug 2008 10:16:58 -0500 [thread overview]
Message-ID: <489B11EA.6020700@riverviewtech.net> (raw)
In-Reply-To: <g7f2ch$tbm$1@ger.gmane.org>
On 08/07/08 09:55, Charles Duffy wrote:
> Perhaps I could also also add a rule setting an appropriate mark in
> OUTPUT. Not being able to communicate with the hosts from the local
> system is a showstopper, however, and I'd prefer to avoid munging the
> routing tables if possible to keep the patch to libvirt implementing
> this functionality minimal. (Robust infrastructure is already in place
> for modifying iptables rules for libvirt-managed networks; routing, not
> so much).
If you did get the rules in the PREROUTING and OUTPUT to work and they
were the same, I'd suggest you put them in a common sub-chain and jump
to it from both the PREROUTING and OUTPUT chains. This will make
maintenance much easier down the road.
Have you considered doing this on layer 2, doing so would allow your
systems to have the same IP address. You would in effect be altering
the destination MAC address of the ethernet frames. In fact, except for
ARPing, you could easily have an unlimited number of hosts with the same
address on the same physical network. You will just need to translate
IPs to the proper MAC at the time you want to communicate with them.
This will work from a traditional routing point of view. However this
does not take in to account that the target systems may see an IP
conflict on the network. To resolve this, you may want to put each
system on its own micro network and bridge micro networks together as
you see fit.
Grant. . . .
next prev parent reply other threads:[~2008-08-07 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 22:57 NETMAP of destination *after* routing Charles Duffy
2008-08-06 23:13 ` Jan Engelhardt
2008-08-07 19:22 ` Charles Duffy
2008-08-07 11:43 ` Sven-Haegar Koch
2008-08-07 14:55 ` Charles Duffy
2008-08-07 15:16 ` Grant Taylor [this message]
2008-08-07 16:03 ` Jan Engelhardt
2008-08-07 19:35 ` Grant Taylor
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=489B11EA.6020700@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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