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] TWO NIC WITH TWO BRIDGE NOT WORKS XEN 3.0.3 -- WHAT AM I WRO

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] TWO NIC WITH TWO BRIDGE NOT WORKS XEN 3.0.3 -- WHAT AM I WRONG ?
From: Jorge Constán <jorqejcv@xxxxxxxxx>
Date: Wed, 11 Feb 2009 13:09:04 +0000
Delivery-date: Wed, 11 Feb 2009 05:09:52 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=AHBvkykBExC+SZNLvNEk+7VnTQ0JegFadDMuic0Q6NI=; b=Yuxe9eL4px9HURnWWrsM6IQuKTIrQsblziynbq33g2Se1B8md/BLRLhkfeiqBmep4Z cAnzNnM9cI3UyVEHDq5kGvuFV59cHJqReA3179asUedQdF9xbfguRXF6Y2tpBJQqUTl7 431EZZCRe0opmy96jsGmeVpUF2aMaeVbSTDNk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VLYHVdTR+2afCrvUgRs2MiZR0+IBTfi2Vj6GEQ+xdG5wSZZnACpzBmyuK8bQeon6u3 zEGrQRJxN3s7TFy9fWhfnXwBRc3cTXJWXyKBIjZD1fdydfzIwTR0lf7pXCPbY6Bo4Egh X8JYw0bkcRBuce/GMjeVTLHNRIo+V85lI5jqg=
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello everyone.

I just installed Xen 3.0.3 in a debian etch box.

Linux server1.example.com 2.6.18-6-xen-686 #1

This server1 has two real nic (eth0 with real MAC 00:13:72:57:7B:AE and eth1 with real MAC00:13:72:57:7B:AF).


I made a network-bridge custom like this:
-----------------------------------------------------------------------
#!/bin/bash

dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0lan
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1wan
"$dir/network-bridge" "$@" vifnum=2 netdev=dummy0 bridge=xenbr2dmz
# EOF
-----------------------------------------------------------------------

I want only the 192.168.0.0 net for dom0 and 10.0.0.0 for two domUs for now (later I m´ll make new domu in 192.168.0.0).


My problem is that que te domU only has ping if I set the real MAC in the dum´s cfg script.



domu1 works if add the real MAC in cfg file like this:
--------------------------------------------------------------------
#  Networking
#
vif   = [ 'ip=10.0.0.55,mac=00:13:72:57:7B:AF,bridge=xenbr1wan' ]
--------------------------------------------------------------------


domu2 works if add the real MAC in cfg file like this:
--------------------------------------------------------------------
#  Networking
#
vif   = [ 'ip=10.0.0.15,mac=00:13:72:57:7B:AF,bridge=xenbr1wan' ]
--------------------------------------------------------------------


domU 1 and domU 2 not works if I add a no real MAC o MAC is not present in cfg domU´s file.

For example. If I make cfg with MAC random, empty o FE:FF:FF:FF:FF:FF, appear the error:

Configuring network interfaces...SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.




Moreover, when I add the real MAC in domUs they work (can ping to any IP), but if I have a ssh session with domU1 and open a new ssh session with
domU2, the network connection with domu1 crash.
So, I can not make two simultaneous ssh connections to domus using the same real MAC


What is wrong?


Thanks a lot for help.



The dom0 ifconfig is like this:
-----------------------------------------------------------------------

eth0      Link encap:Ethernet  HWaddr 00:13:72:57:7B:AE
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::213:72ff:fe65:b6ae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20077 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5247 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1635292 (1.5 MiB)  TX bytes:2590945 (2.4 MiB)


eth1      Link encap:Ethernet  HWaddr 00:13:72:57:7B:AF
          inet addr:10.0.0.10  Bcast:192.168.0.255  Mask:255.0.0.0
          inet6 addr: fe80::213:72ff:fe65:b6af/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1410 (1.3 KiB)  TX bytes:468 (468.0 b)


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:190 (190.0 b)  TX bytes:190 (190.0 b)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:26704 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5465 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2153821 (2.0 MiB)  TX bytes:2625975 (2.5 MiB)
          Base address:0xecc0 Memory:fe6e0000-fe700000

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1438388 errors:0 dropped:0 overruns:0 frame:0
          TX packets:995820 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:587494811 (560.2 MiB)  TX bytes:802828104 (765.6 MiB)
          Base address:0xdcc0 Memory:fe4e0000-fe500000

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:5247 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20077 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2590945 (2.4 MiB)  TX bytes:1635292 (1.5 MiB)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:534 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:43692 (42.6 KiB)

vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:326 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:714 (714.0 b)  TX bytes:26376 (25.7 KiB)

vif4.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:746803 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1437865 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:772754929 (736.9 MiB)  TX bytes:580090885 (553.2 MiB)

xenbr0lan Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:14601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:890242 (869.3 KiB)  TX bytes:0 (0.0 b)

xenbr1wan Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:534 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:36216 (35.3 KiB)  TX bytes:0 (0.0 b)

xenbr2dmz Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
-----------------------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] TWO NIC WITH TWO BRIDGE NOT WORKS XEN 3.0.3 -- WHAT AM I WRONG ?, Jorge Constán <=