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

Re: [Xen-users] Xen 4.1.0, multiple network interfaces, network-bridge f

Hi,

>From your original post I can gather you wish to create 2 bridges, one
each for the interfaces eth0 and eth1?

This can be achieved by running the following:
brctl addbr xenbr0
brctl addif xenbr0 eth0
brctl addbr xenbr1
brctl addif xenbr1 eth1

Slackware doesn't have a nice way of doing this with it's internal
networking system but adding the above to rc.local accomplishes the
job good enough.

To make use of a multiple bridge setup effectively you need to specify
the bridge in the vif statement of the xen config file (something like
bridge=xenbr0)

Note, only network-bridge and associated are depreciated.
You still require the vif-bridge script to be enabled in
/etc/xen/xend-config.xcp

When domains are created Xen will create the vif adapters to the
following naming convention:
vif<domid>.<adapternumber>

So for a domid of 5 and a system with 2 adapters the following vif
devices will be created in dom0:
vif5.0
vif5.1

During device hotplug the vif-script then brings this interface up and
adds it to the bridge.

Do you have any further questions or need any further clarification on
any of the points above?
I am considering writing an article on Xen Wiki about how network
configuration is carried out in Xen as it seems to be an area alot of
people have problems with.

Joseph.

On 6 May 2011 02:38, Jan Vejvalka <jan.vejvalka@xxxxxxxxxxxxxxx> wrote:
>>> (...) Does it mean that
>>> the /etc/xen/scripts/network-bridge script is obsolete ?
>>>
>>
>> Yes it is deprecated. It will be much better and more robust to use
>> the network scripts in your distribution.
>
> I see, thanks.
>
>> Offhand I can't seem to find the slackware documentation on creating
>> network bridges.
>
> I think that I can get around in Slackware with brctl; what I miss is a
> (distribution-independent ?) information on WHAT to do, not on HOW to
> do it.
>
> Quoting (almost)
> http://wiki.xensource.com/xenwiki/HostConfiguration/Networking,
> I need to know what is the appropriate network configuration that
> administrators are required to set up using the tools provided by their
> host distribution.
>
> For me, so far most useful was the brief info that describes what
> network-bridge does:
> # start:
> # Creates the bridge as tdev
> # Copies the IP and MAC addresses from pdev to bridge
> # Renames netdev to be pdev
> # Renames tdev to bridge
> # Enslaves pdev to bridge
>
> and the diagrams in http://libvirt.org/archnetwork.html#architecture
> that "illustrate some of the network configurations enabled by the libvirt
> networking APIs".
>
> http://wiki.xensource.com/xenwiki/XenNetworking , on the other hand,
> seems obsolete: I can't see any vethX/vif0.X interfaces in my Dom0.
>
> Thank you for your help,
>
> Jan
>
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Kind regards,
Joseph.
Founder | Director
Orion Virtualisation Solutions | www.orionvm.com.au | Phone: 1300 56
99 52 | Mobile: 0428 754 846

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