This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Looking for easy guide for Fedora 8 xen networking

To: Jason Solan <jsolan@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Looking for easy guide for Fedora 8 xen networking
From: John Haxby <john.haxby@xxxxxxxxxx>
Date: Fri, 25 Apr 2008 15:57:47 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 25 Apr 2008 07:58:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1209128784.3216.12.camel@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1209128784.3216.12.camel@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080226)
Jason Solan wrote:
  From the other environments I've used, the networking "just works" for
the guest if there's only 1 nic card.  It stays on the same subnet as
the dom0 and everything works like the guest has its own network card.

  In using Fedora 8, the default networking appears to create a bridged
device and put it on a 192.168.122 subnet.  If the domU requests a DHCP
address, this nic provides it and the domU stays on the 192.168.122
subnet.  I can get out from the domU, but I can't seem to get in.
There are two bridges, IIRC, virtbr0 for a local network (which is what you're using) and eth0. Previously the you would have had something like virbr0 and xenbr0 where xenbr0 has dom0's eth0 and peth0 on it; in Fedora8 eth0 is the bridge instead. You probably want to use that instead of virbr0.

Now that the bridge has an IP address you can, again IIRC, do cool things with iptables for traffic flowing through the bridge without having to use ebtables.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>