WARNING - OLD ARCHIVES

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/
Xen

xen-users

[Top] [All Lists]

[Xen-users] XEN problems with custom networking

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XEN problems with custom networking
From: Michael Steinhoff <mstde@xxxxxx>
Date: 2007年4月06日 11:59:00 +0200
Delivery-date: 2007年4月09日 02:43:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: http://freemail.web.de/
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hallo,
I cannot get my xen networking going ...
My Debian/Etch-Xen (2.6.18-3-xen-686)-machine has two nics. I wolud like to 
create a scenario with a public site (eth0), a private LAN (eth1) and a DMZ. 
This should not be too exotic as I found something like this in several 
postings.
In Dom0 I put the bridges in my /etc/network/interfaces (I've no knowlegde of 
perl, so fiddling with a custom xen-network-script is no option for me and from 
what I googled, this should be a valid way to configure the bridges.): 
auto eth0
iface eth0 inet static
 address 192.168.1.100
 network 192.168.1.0
 netmask 255.255.255.0
 gateway 192.168.1.1
 
#LAN 
auto eth1
iface eth1 inet static
 address 192.168.2.100
 network 192.168.2.0
 netmask 255.255.255.0
 
auto dummy0
iface dummy0 inet static
 address 192.168.3.100
 netmask 255.255.255.0
 gateway 192.168.3.1 
 
# Internal Bridged Network.
auto xenintbr
iface xenintbr inet static
pre-up brctl addbr xenintbr
post-down brctl delbr xenintbr
address 192.168.2.1
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
bridge_fd 0
bridge_hello 0
bridge_stp off
auto xendmzbr
iface xendmzbr inet static
pre-up brctl addbr xendmzbr
post-down brctl delbr xendmzbr
address 192.168.3.1
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
bridge_fd 0
bridge_hello 0
bridge_stp off
 
 
A ifconfig shows, that both brigdes are up; I can ping all given addresses (in 
Dom0).
In the DomU-config file I specify the brigde
vif = ['bridge=xenintbr']
I tried to apply the IP-Address from the config-File or within the running DomU 
- neither way worked.
What is wrong, what am I missing?
Any help is appreciated.
Thanks!
Michael
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] XEN problems with custom networking, Michael Steinhoff <=
Previous by Date: [Xen-users] Problem with 802.1Q tagging in Xen domain 0. (May be HW vlan acceleration related?) , Igor Chubin
Next by Date: [Xen-users] Re: vncviewer configuration problem , Anthony Liguori
Previous by Thread: [Xen-users] Problem with 802.1Q tagging in Xen domain 0. (May be HW vlan acceleration related?) , Igor Chubin
Next by Thread: [Xen-users] Custom networking problems , Michael Steinhoff
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /