[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] IP blocking


  • To: "mail4dla@xxxxxxxxxxxxxx" <mail4dla@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: shacky <shacky83@xxxxxxxxx>
  • Date: Wed, 8 Aug 2007 12:00:53 +0200
  • Delivery-date: Wed, 08 Aug 2007 02:58:31 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GeUNenyw6whz/cu7ypamN3++FYfeiWM3uA5SAXHIUo2j/q0dFNipThW8GCPXtfHqnke7h3Txq1RfJxIchK/4d34kGdUMq4S+bX2coKXnItcgoiz6gZqXTTNdH47eYQGo/aNOMaCLzhC1zGXDzEbkGaDgxwnA6oKdfq9/YFjctCA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> If the DomU is already started, "brctl delif xenbrX vifY.Z" is your friend.
> Before starting, you can simply set "bridge=" in the DomU config file.

Setting "bridge=" will I make no bridge with no interface?

> Yes, and that's the important point: Do you want to do NAT and share one IP
> or should each DomU have its own IP that is visible to the outside?
> In the latter case, the easiest solution is a dedicated subnet for the DomUs
> that is routed via an IP in the DomU. I.e., all traffic targeted to one of
> the DomUs is not sent directly there but to the Dom0.
> AFAIK, most providers of cheap servers with root access do not offer this.

I didn't think about this.
I absolutely need to do routing instead of NAT because all the domUs
needs to be visible to the outside with their own IP address and not
with the IP address of the dom0.
But now the question is: how I can make routing on the dom0 for the
domUs? With NAT 1:1 in Shorewall?

Thank you very much!

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.