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

Re: [Xen-users] Xen networking newbie


  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Henrik Andersson <henrik.j.andersson@xxxxxxxxx>
  • Date: Fri, 4 Feb 2011 17:58:18 +0200
  • Cc: Emir Sosa <emir@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 04 Feb 2011 08:08:04 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eFTuRMWHa9Lbom5XYdYmSZnhvbazxU6TCaqMvkgQwk2GmMfxZSVlpI/W3P6X1UpytB sagasEzwRyCgOxypCTWUU159g7pAqk70Gl2f30/H1AAbQJrc2gGx+WEdpgaCDmZ59/P8 fGLneVuZ2mgzs/PLV4SaG4E+izxdAGgM707KM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok, seem's like I was talking crap. Didn't know xen has such a feature.

-Henrik Andersson

On 4 February 2011 17:54, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
On Fri, Feb 4, 2011 at 9:49 PM, Emir Sosa <emir@xxxxxxxxxxxxxx> wrote:
> but the thing is the windows server can ping the 192.168.1.1 but devices on
> 192.168.1.0 cant ping the 192.168.122.0(cuase they dont know of this
> network)

192.168.122 is a private network to the xen dom0, created by libvirt
(the virbr0 bridge)

>
> is there a way that the the guest OS belong to the same network? so they can
> be communicate easily?

Don't use virbr0 then.
There should be another bridge you can use, called xenbr0 (or eth0,
depends on the xen version).

--
Fajar

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

_______________________________________________
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®.