|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] xen-3.3 missing xenbr0 new tmpbridge
Am Sonntag, den 07.12.2008, 20:30 +0100 schrieb Torsten:
> Thanks,
>
> I should be read my article still another 2. time...
> xenbr0 was renamed to eth0, but why?
>
> On [3] "Xen 3.2+ Networking" written: "eth0 and eth1 are the bridge names..."
> Me too find it is confusing.
>
> [3] http://wiki.xensource.com/xenwiki/XenNetworking
>
> it contains network-samples, but no config-examples and
> predivide and disadvantages.
>
>
> on xend-config.sxp written:
> ---%<---
>
> # To bridge network traffic, like this:
> #
> # dom0: ----------------- bridge -> real eth0 -> the network
> # |
> # domU: fake eth0 -> vifN.0 -+
> #
> # use
> #
> # (network-script network-bridge)
> ....
> # The bridge is named xenbr0, by default. To rename the bridge, use
> #
> # (network-script 'network-bridge bridge=<name>')
>
> ---%<---
>
> It seen to be description and working to drift apart.
>
> Ok...
>
> - Test7 overwrite bridge-name
>
> # diff xend-config.sxp.org xend-config.sxp
> 152c152,153
> < (network-script network-bridge)
> ---
> > #(network-script network-bridge)
> > (network-script 'network-bridge bridge=xenbr0')
>
> ## network-bridge stop .. start || reboot
>
> # brctl show
> bridge name bridge id STP enabled interfaces
> eth0 8000.0015c5be8f93 no peth0
>
> -> not working
>
> How must it are configured that xenbr0 showing as before version 3.2 ?
i would recommend to write your own network-script
something like
# vim /etc/xen/script/network-mynet
---------snip----------------
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
------------snap-------
# chmod +x /etc/xen/script/network-mynet
edit xend-config.sxp
# /etc/init.d/xend restart
should do the job.
>
> regards torsten
hth,
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|