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

[Xen-users] Re: broken networking - bridge

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: broken networking - bridge
From: Damir Špoljarič <admin@xxxxxxxxxx>
Date: Sun, 19 Feb 2006 23:49:21 +0100
Delivery-date: Mon, 20 Feb 2006 11:01:43 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43F8F58D.1020505@xxxxxxxxxx>
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: <43F8F58D.1020505@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
Oh, I´m sorry... Brctrl show is this:
Brctl show looks normal:
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                                vif0.0
                                                                vif1.0


Damir

Damir Špoljarič napsal(a):

Hi all,
I have a problem with network in bridge mode. Everything went well, but for unkown reason network stopped to work on virtual machines. One virtual machine has IP for example 82.208.36.96. I can´t get on it from the network (I mean Internet :-) ) and I also can´t from virtual machines get to Internet. I can get on virt. mach. only from domain0. Something with bridge has probably broken :-/. Brctl show looks normal:
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              peth0
                                                                  vif0.0
                                                                  vif4.0

Ifconfig output looks normal as well. There are interfaces eth0, peth0, xenbr0, vif0, vif1.0. I haven't edited scripts vif-bridge and network-bridge at all. They are default, as well as xend config.

These are individual domU configs (about network):
nics=1
dhcp ="off"
ip="82.208.36.96"
netmask="255.255.255.0"
gateway="82.208.36.1"

All rules in iptables are set to ACCEPT (OUTPUT, INPUT and FORWARD).
In addition to this, I have something in FORWARD:
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif1.0

There are no errors in logs. Only in xen-hotplug.log is this:
xenstore-read: couldn't read path backend/vif/1/0/ip
xenstore-read: couldn't read path backend/vbd/1/770/physical-device
xenstore-read: couldn't read path backend/vif/1/0/bridge
xenstore-read: couldn't read path backend/vbd/1/769/physical-device
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists


Does anyone know where the is problem?

Thanks !
Damir












--
------------------------------------------------
Damir  Špoljarič
šéfredaktor PC Svět.net
www.pcsvet.net


admin@xxxxxxxxxx
icq: 258080801
------------------------------------------------

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

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