[opensuse] adding another bridged interface in xen
I have a system (SLES 10 SP1) that has two NICs, eth0 and eth1. eth1 is bridged: # brctl show bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth1 vif31.0 What would the commands be for enabling a bridge on eth0 as well? Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 2008-04-07 19:57, James Pifer wrote:
I have a system (SLES 10 SP1) that has two NICs, eth0 and eth1. eth1 is bridged:
# brctl show bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth1 vif31.0
What would the commands be for enabling a bridge on eth0 as well?
Well you add it to /etc/sysconfig/network/ifcfg-xenbr1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-04-07 at 20:35 +0200, Jan Engelhardt wrote:
On Monday 2008-04-07 19:57, James Pifer wrote:
I have a system (SLES 10 SP1) that has two NICs, eth0 and eth1. eth1 is bridged:
# brctl show bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth1 vif31.0
What would the commands be for enabling a bridge on eth0 as well?
Well you add it to /etc/sysconfig/network/ifcfg-xenbr1
I don't have /etc/sysconfig/network/ifcfg-xenbr1 or /etc/sysconfig/network/ifcfg-xenbr0. James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 08 April 2008 03:17:57 James Pifer wrote:
On Mon, 2008-04-07 at 20:35 +0200, Jan Engelhardt wrote:
On Monday 2008-04-07 19:57, James Pifer wrote:
I have a system (SLES 10 SP1) that has two NICs, eth0 and eth1. eth1 is bridged:
# brctl show bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth1 vif31.0
What would the commands be for enabling a bridge on eth0 as well?
Well you add it to /etc/sysconfig/network/ifcfg-xenbr1
I don't have /etc/sysconfig/network/ifcfg-xenbr1 or /etc/sysconfig/network/ifcfg-xenbr0.
Xen networking is controlled from /etc/xen/scripts - typically the network-bridge script is called to set up the bridge. I don't have my SLES Xen system to hand to check on, but on openSUSE 10.3 there is a network-multinet script that you might want to run instead of network-bridge. it's pretty well documented, but it is obviously a bit more complex than the standard script that runs... Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Xen networking is controlled from /etc/xen/scripts - typically the network-bridge script is called to set up the bridge. I don't have my SLES Xen system to hand to check on, but on openSUSE 10.3 there is a network-multinet script that you might want to run instead of network-bridge. it's pretty well documented, but it is obviously a bit more complex than the standard script that runs...
Jon
This wasn't hard once I found what to do. Created a new file called /etc/xen/scripts/my-network-script and made it executable. Edited the file and added these lines: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 Then edited /etc/xen/xend-config.sxp and added: (network-script my-network-script) right before: (network-script network-bridge) Then restart xend. Now I have both xenbr0 and xenbr1. I modified my server script, /etc/xen/vm/server1 and changed this line: vif=[ 'bridge=xenbr1', ] to vif=[ 'bridge=xenbr0', ] What I was not able to figure out was how to simply modify my domU to use the other bridge. Even if I changed it in the config file, Virt Manager stilled showed the other bridge, even after resarting xend and rebooting. Simplest fix was to delete and reset up the domU in Virt Manager and select the disk, etc. Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/4/8, James Pifer
Xen networking is controlled from /etc/xen/scripts - typically the network-bridge script is called to set up the bridge. I don't have my SLES Xen system to hand to check on, but on openSUSE 10.3 there is a network-multinet script that you might want to run instead of network-bridge. it's pretty well documented, but it is obviously a bit more complex than the standard script that runs...
Jon
This wasn't hard once I found what to do. Created a new file called /etc/xen/scripts/my-network-script and made it executable. Edited the file and added these lines: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1
Then edited /etc/xen/xend-config.sxp and added: (network-script my-network-script) right before: (network-script network-bridge)
Then restart xend. Now I have both xenbr0 and xenbr1.
I modified my server script, /etc/xen/vm/server1 and changed this line: vif=[ 'bridge=xenbr1', ] to vif=[ 'bridge=xenbr0', ]
What I was not able to figure out was how to simply modify my domU to use the other bridge. Even if I changed it in the config file, Virt Manager stilled showed the other bridge, even after resarting xend and rebooting. Simplest fix was to delete and reset up the domU in Virt Manager and select the disk, etc.
Thanks,
James
--
What about adding the second device to "BRIDGE_NETDEV_LIST" on "/etc/sysconfig/xend"? Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/4/8, James Pifer
--
What about adding the second device to "BRIDGE_NETDEV_LIST" on "/etc/sysconfig/xend"?
I have a /etc/sysconfig/xendomains but no /etc/sysconfig/xend
James.
Oops, I checked in OS 10.3... Probably it'll be implemented in SLES10SP2 Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/4/8, Ciro Iriarte
2008/4/8, James Pifer
: --
What about adding the second device to "BRIDGE_NETDEV_LIST" on "/etc/sysconfig/xend"?
I have a /etc/sysconfig/xendomains but no /etc/sysconfig/xend
James.
Oops, I checked in OS 10.3... Probably it'll be implemented in SLES10SP2
Ciro
Well, I'm about to install XEN on SLES10SP1 too at the office and seems i'm going to find this issue too. Wanted to check in which package it's included but rpm says it came from nowhere.... mainwks:~ # rpm -q --whatprovides /etc/sysconfig/xend file /etc/sysconfig/xend is not owned by any package Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Apr 8, 2008 at 9:34 AM, Ciro Iriarte
2008/4/8, Ciro Iriarte
: 2008/4/8, James Pifer
: --
What about adding the second device to "BRIDGE_NETDEV_LIST" on "/etc/sysconfig/xend"?
I have a /etc/sysconfig/xendomains but no /etc/sysconfig/xend
James.
Oops, I checked in OS 10.3... Probably it'll be implemented in SLES10SP2
Ciro
Well, I'm about to install XEN on SLES10SP1 too at the office and seems i'm going to find this issue too. Wanted to check in which package it's included but rpm says it came from nowhere....
mainwks:~ # rpm -q --whatprovides /etc/sysconfig/xend file /etc/sysconfig/xend is not owned by any package
Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
This might help you, it might not but this what I use for Virtual Box to get the Bridge up and my two cards eth0 eth2 to connect. Also make sure that in sysconfig --> SuSEfirewall2, that you have FW_FORWAD_ALWAYS_INOUT_DEV uncommented for your interface... #!/bin/bash # By Chuck Payne # This will set up bridge for virtual box PATH="$PATH:/home/$USER/bin:/usr/local/bin:/usr/local/sbin:/etc/vbox" case "$1" in start) brctl addbr br0 brctl addif br0 eth0 eth2 ifconfig br0 up dhcpcd br0 ifconfig eth 0 0.0.0.0 ;; status) brctl show ;; stop ) ifconfig br0 down brctl delif br0 eth2 brctl delif br0 eth0 brctl delbr br0 /etc/init.d/network restart ifconfig br0 down brctl delbr br0 ;; *) echo "Usage: $0 start | status | stop" ;; esac Hope that's helps. -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Chuck Payne
-
Ciro Iriarte
-
James Pifer
-
Jan Engelhardt
-
Jonathan Ervine