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 User - listmembers <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Routed dom0 setup problem -- second time around
From: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Date: Fri, 28 Dec 2007 08:58:50 +0100
Cc: Rich Wales <richw@xxxxxxxxx>
Delivery-date: Thu, 27 Dec 2007 23:59:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47749EFF.2050408@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>
Organization: netz-haut e.K.
References: <47749EFF.2050408@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20071022)
Rich Wales schrieb:
> I'm still having problems getting a new Xen system to work properly in
> a "routed" configuration.
> I thought I had it figured out a few days ago, but when I couldn't get
> the Shorewall firewall application to work properly, it became evident
> that my Xen configuration was seriously messed up and that I really
> needed to start over with the networking from scratch.
> I'm running Xen 3.1 / Ubuntu 7.10 (kernel = 2.6.22-14-xen).  Here's my
> current xend-config.sxp file:
> (xen-api-server ((unix)))
> (xend-http-server yes)
> (xend-unix-server yes)
> (xend-relocation-server no)
> (xend-port 8000)
> (xend-address '')
> (xend-relocation-hosts-allow '')
> (network-script 'network-route netdev=dmz0')


without a deeper look into it, i assume network-script is called via some
kind of exec() and 'network-route netdev=dmz0' is trivially not found.

For easier use, I always use a wrapper script at this line.

(network-script 'my-network-route')

--- /etc/xen/scripts/my-network-route (chmod +x) ---
# start bridge on dmz0


$XENDIR/network-bridge "$@" netdev=dmz0 bridge=xenbr0 vifnum=0



> (vif-script vif-route)
> (dom0-min-mem 196)
> (dom0-cpus 0)
> (vncpasswd '')

Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054

Attachment: s_seitz.vcf
Description: Vcard

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-users mailing list