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] Xen Bridge Problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen Bridge Problem
From: Sebastian Biedermann <biedermann@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 02 Feb 2011 10:49:01 +0100
Delivery-date: Wed, 02 Feb 2011 01:49:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D47CB29.3090603@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4D47CB29.3090603@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
Dear list,

I have a problem connecting to my domU instance from the network.
My domU instance is running on a node and the bridge is set up

node0:~# virsh list
 Id Name                 State
----------------------------------
  0 Domain-0             running
  1 i-4BBF088C           idle

node0:~# brctl show
bridge name     bridge id               STP enabled         interfaces
eth0            8000.20cf30c34407       no                      peth0
vif1.0

The dom0 has the IP address 192.168.0.2 and the domU gets 192.168.0.4.

node0:~# ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 20:cf:30:c3:44:07
inet Adresse:192.168.0.2 Bcast:192.168.0.255 Maske:255.255.255.0 inet6-Adresse: fe80::22cf:30ff:fec3:4407/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:9642 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8484 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:2701535 (2.5 MiB)  TX bytes:3415253 (3.2 MiB)

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:6032 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6032 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:1010387 (986.7 KiB)  TX bytes:1010387 (986.7 KiB)

peth0     Link encap:Ethernet  Hardware Adresse 20:cf:30:c3:44:07
inet Adresse:192.168.0.4 Bcast:192.168.0.255 Maske:255.255.255.0 inet6-Adresse: fe80::22cf:30ff:fec3:4407/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:9642 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8596 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:2839977 (2.7 MiB)  TX bytes:3433899 (3.2 MiB)
          Interrupt:17 Basisadresse:0xc000

vif1.0    Link encap:Ethernet  Hardware Adresse fe:ff:ff:ff:ff:ff
inet6-Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:32
          RX bytes:0 (0.0 B)  TX bytes:88958 (86.8 KiB)


When I ping or try to connect to the instance on 192.168.0.4 from a cloud manager which is a seperate pc and which has ip 192.168.0.1, I´m always arriving at the 192.168.0.2 dom0,
which means the bridge is not working correctly, i think.
Same happens when I try to connect from dom0 to domU.

Anyone has an idea what to do or which files to check?

Greetings


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

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