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 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen network question

To: Damjan Rems <d_rems@xxxxxxxxx>
Subject: Re: [Xen-users] Xen network question
From: Andreas Seuss <mam04exx@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Aug 2005 10:30:58 +0200
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 Aug 2005 08:30:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050810114625.51022.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
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: <20050810114625.51022.qmail@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.2 (X11/20050331)
Hi Damjan,

Damjan Rems wrote:

>I am no expert to Linux or Xen. Runing Xen on Suse
>9.3.
>
>Network scenario:
>Dom0 eth0 ip=192.168.1.118 mask=255.255.255.0,
>gw=192.168.1.1.
>I would like to setup domU eth0 ip=192.168.1.116. domU
>should also have access to Internet. I was able to
>follow instructions by Gregorz in previous posts but
>the best I could get was:
>
>1. I could ping domU from dom0, but not dom0 from
>domU. If I disable firewall I can ping from both
>sites. But this should not be OK.
>
>2. I can not get to Internet even from dom0. Look like
>gateway address (route) is lost.
>
>
>For dom0 I was using:
>brctl addbr xen-br0
>ip addr 192.168.1.118 brd 192.168.1.255 scope global
>dev xen-br0
>route del -net 192.168.1.0/24 eth0
>route add -net 192.168.1.0/24 xen-br0
>brctl addif xen-br0 eth0
>  
>
Before I start, it#s been a long time since I had a look at a SuSE
System, might be, that their directory structure is somewhat different.
Also I don't know as to how much influence yast has on your configuration.

Actually, there is a script from Xen itself that should do all the
networking stuuf itself. When I tried it just worked. ->
/etc/xen/scripts/* Xen should use these scripts automatically. I think
they are set as default in /etc/xen/xend-config.sxp

This is what it looks like:
# The script used to start/stop networking for xend.
(network-script    network)
# The default bridge that virtual interfaces should be connected to.
(vif-bridge        xen-br0)
# The default script used to control virtual interfaces.
(vif-script        vif-bridge)

As for your commands, can you please post

/etc/network/interfaces (both, dom0 and domU)

What does the output of "route" look like? Should look something like

Destination     Gateway         Genmask     Flags Metric Ref    Use Iface
10.0.0.0                  *               255.0.0.0       U          0 
     0        0 xen-br0
default               gw.d.tld        0.0.0.0         UG        0      
0        0 xen-br0

Looks like the routing is not configured in the correct way. Did you
configure a default gateway?

e.g. route add default gw ...?

Regards,

Andreas

>For domU I was using:
>ifconfig eth0 192.168.1.116
>
>What am I doing wrong?
>
>by
>
>TheR
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around 
>http://mail.yahoo.com 
>
>_______________________________________________
>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

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