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] Problems with domU networking

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Problems with domU networking
From: Jeff Blaine <jblaine@xxxxxxxxx>
Date: Tue, 26 Apr 2005 11:20:25 -0400
Delivery-date: Tue, 26 Apr 2005 15:20:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
FWIW, I am experiencing a very similar situation (if not
identical).

I am running 2.0.5 binary dist on a completely fresh box.

None of my vifs are "UP" by default.  Running 'ifconfig
vifNUM.NUM up' doesn't solve anything for me.

No firewalling is on.  Netmask and default route are proper.

I have the following:

eth0 in dom0        192.168.168.6
vif1.0              192.168.168.20    (aka eth0 in VM1)
vif2.0              192.168.168.21    (aka eth0 in VM2)
vif3.0              192.168.168.22    (aka eth0 in VM3)

Everything has a default route of 192.168.168.1 and a route
to 192.168.168.0 through gateway 0.0.0.0 on eth0.

I cannot:

  1.  ping dom0 from any VM
  2.  ping any VM from dom0

I can:

  1.  ping 192.168.168.1 from dom0

>> For some reason they took the 'ifconfig vif<number> up' out
>> of the bridging scripts.
>>
>> Notice how there is no 'UP' in the output:
>
>I'm confused. The vif-bridge script works fine for me as-is, and should
>be configuring the interface 'up':  "ifconfig ${vif} $OP"
>
>Are you using an old version of the script?
>
>Ian


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users