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] how do I make sure that bridge is active on Xen

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] how do I make sure that bridge is active on Xen
From: Tapas Mishra <mightydreams@xxxxxxxxx>
Date: Sat, 10 Apr 2010 11:15:42 +0530
Delivery-date: Fri, 09 Apr 2010 22:47:00 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:content-type; bh=zIimp4+2tQDltHrD7XRqK17cQbnapXgd+yTt4YmO3Ek=; b=JRZ/jNZNJkJueCY2w4gr01s/ZPK34yD+V44tunpejuAMx6KgZxkt97GPvsiZyNbBdn QZjksduZQsYn13YTEHzSO3IL3k+I0hc1UxhrmgXUtQoxYbAtN+fMWtnwK4nz+IHJYI2M otcfgG5hN1v7Vqtz6zafXz/k54J+OQ3eF0BJM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=DBQ3vJpy2NwOGI8DUmavu00nla9TaSVUnmgDj1BDZlm9GYL7C7BnOGgj9n7jQk3aQm ScmH52TUmA0EgoQ17ZoHw0JUIumEk5IZnCipmRiEnuzlG6aoHncPbHL6Mh9FbEhP/Ndg Hlq8Uh9mDBfNgcRuf/yTHYopvWwqffDAWI2bU=
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
I am doubtful that the default bridge is active.
When I do following no where the bridge name comes how do I make sure
bridge is active.



openworld:/etc/xen# ifconfig

eth2      Link encap:Ethernet  HWaddr 00:26:b9:82:42:38
          inet addr:192.1.100.150  Bcast:172.21.255.255  Mask:255.255.0.0
          inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:136687 errors:0 dropped:0 overruns:0 frame:0
          TX packets:379 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:115126806 (109.7 MiB)  TX bytes:42095 (41.1 KiB)

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:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1281 (1.2 KiB)  TX bytes:1281 (1.2 KiB)

peth2     Link encap:Ethernet  HWaddr 00:26:b9:82:42:38
          inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:178069 errors:0 dropped:0 overruns:0 frame:0
          TX packets:421 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:123134712 (117.4 MiB)  TX bytes:48409 (47.2 KiB)
          Interrupt:32 Memory:da000000-da012100

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 PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:163192 errors:0 dropped:80 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:1076 (1.0 KiB)  TX bytes:120369832 (114.7 MiB)

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 PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:412 (412.0 B)  TX bytes:62179 (60.7 KiB)



In /etc/xen/xend-config.sxp following entries are there

# use
#
 (network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
  (network-script 'network-bridge netdev=eth2'')

# The bridge is named xenbr0, by default.  To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#### Tapas made changes
 (network-script 'network-bridge bridge=tapas')


The defaul ethernet device is eth2 on my system.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] how do I make sure that bridge is active on Xen, Tapas Mishra <=