[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Xen-3.0. Manually network switch
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@xxxxxxxxx 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@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |