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] Routed dom0 setup problem -- second time around

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Routed dom0 setup problem -- second time around
From: jim burns <jim_burn@xxxxxxxxxxxxx>
Date: Fri, 28 Dec 2007 21:49:45 -0500
Delivery-date: Fri, 28 Dec 2007 18:50:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4775A0AA.7050806@xxxxxxxxxxxxxxxxxxxx>
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: <47749EFF.2050408@xxxxxxxxxxxxxxxxxxxx> <477546F5.4080804@xxxxxxxxxxxxxxxxxxxx> <4775A0AA.7050806@xxxxxxxxxxxxxxxxxxxx> (sfid-20071228_203924_991808_E202213D)
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 20070904.708012)
On Friday 28 December 2007 08:19:38 pm Rich Wales wrote:
> Note that my non-default network interface (dmz0) is given as a parameter
> to vif-route, as well as to network-route.  This point wasn't mentioned
> anywhere in any of the documentation or discussions I could find online,

Hmm - if you read between the lines the comments in xend-config.sxp about 

# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here.  The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.

Apparently the same rules apply to the netdev= parm, and since the -route 
and -nat sections are just non-commented alternatives to the -bridge section, 
it should be assumed the same rules for specifying bridge= and netdev=  for 
both the network-route/nat and vif-route/nat scripts apply. Isn't guessing 
what they mean fun :-) !

Xen-users mailing list