Hello,
since the effort for getting bonding interfaces to work is a bit to high for
our scenario, I''m developping some other solution for a better network
safety:
The dom0 has two physical network interfaces eth0, eth1. What I''d like
to
create is a simple script that creates a second bridge with eth1 rather than
eth0. Replacing peth0 with eth1 does not work.
I''m a bit confused with the Xen network interface naming: vifn.0
corresponds
to the network interfaces of the XenU instances and vifn.1 corresponds to
the second network interfaces of the XenU instances, right?
vif0.0 seems to be some virtual interface that connects the bridge to Xen0,
but what''s the peth0 interface and how do I create a peth1 interface?
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif15.0
vif0.0
peth0
vif1.0
vif2.0
xenbr1 8000.000bcd681c68 no eth1
If I remove the vif0.0 interfaces from xenbr0 I can''t ping eth1
anymore.
How should this work?
TIA -- Peter
--
Peter.Weiss@consol.de ConSol* Software GmbH
Phone +49 89 45841-100 Consulting & Solutions
Mobile +49 177 6040121 Franziskanerstr. 38
http://www.consol.de D-81669 München
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter.Weiss@ConSol.de wrote:> since the effort for getting bonding interfaces to work is a bit to high for > our scenario, I''m developping some other solution for a better network > safety:I''m using a similar setup to virtualize my firewall. In my setup eth1 is connected to the internet and xenbr1 and eth0 is connected to the local net and xenbr0. The reason why it''s this way around is that i''m lazy and don''t want to manually refer to the bridge in all configs ;)> The dom0 has two physical network interfaces eth0, eth1. What I''d like to > create is a simple script that creates a second bridge with eth1 rather than > eth0. Replacing peth0 with eth1 does not work.I never really figured out the network-bridge script, it was a horror to try and decipher it. I created the following script to do the work for me: - --8<-- #!/bin/sh # Invoke network-bridge script multiple times XENSCRIPTDIR=/etc/xen/scripts # Run twice for i in 0 1; do ${XENSCRIPTDIR}/network-bridge vifnum=$i netdev=eth$i bridge=xenbr$i $@ done - --8<-- put that in your Xen script directory and adjust your xend-config.sxp to use that as the network-bridge script. It will create xenbr0 and xenbr1 for you with the original script. - - S -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDuDP5qbb3MLg9dhwRAmU4AJ4xVwAOKME8Ci4h6jaPQVifgQwn9gCeNWQm 8KCkdKpeA9G8dBV7zqOlHFA=E5dl -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users