> > How about having a domU that does the iptables stuff and all the
> > "application" domUs live in rfc1918 space?
>> 2a though, at best, and it was considered.
>> > The "virtual router" domU could be identical on both sites if it
> > had some smart way of figuring out where it was running. For
> > example, ping the
> > upstream router IP address for both providers and see which has
> > the lower TTL.
>> Yeah, or have its IP passed to it at boot time - that's a solvable
> problem, but it's debatable what having that domU brings you, as
> against having iptables run on the dom0.
Your iptables-running domU is replicated between sites, same as the
application domUs. That way any iptables config only needs to be
done in one place. Running iptables on the dom0s means that you
have to configure it in two places.
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
