Lists wrote:
>The following is the setup I have:
>
> |-eth1 Mail (domU) (10.0.0.1)
> WAN <---> eth0-GW (Dom0) ---|-eth2 WWW (domU) (10.0.0.2)
>(62.235.222.227) (10.0.0.128) |-eth1 test (domU) (10.0.0.3)
>
>I only have one external IP for eth0 and I'd like my DomUs to be
>available on the WAN. From what I can tell by Tom's documentation,
>is that he managed to do this using Xen-routed, so what is the
>difference between the two and can I implement the above in a routed
>environment?
The difference is that Tom has multiple public IPs, you are using
RFC1918 private addresses which are NOT routable on the internet -
that's why you are using NAT. If you look at one of the other pages,
then you'll see that his current arrangement involves the WAN
connection being connected ONLY to a DomU so the Dom0 is not directly
connected to the internet.
What I've done is like this :
WAN a.b.c.d <--> Dom1 ---+--- Dom0
Dom2 ---+
... |
DomN ---+
Dom1 runs a 'traditional' two interface router.
The WAN port (in this case an ethernet port) is made available by
hiding it from Dom0 (using pciback.hide=(xx:yy.z) in the Dom0 boot
config) and making it available to the DomU by adding pci=['xx:yy.z']
to the DomU config.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
