On 12/20/06, Dominique Rousseau <d.rousseau@xxxxxxx> wrote:
Le Wed, Dec 20, 2006 at 12:18:37PM +0900, Toshinao Ishii
[Ishii.Toshinao@xxxxxxxxxxxxxxxxxxxxxxxxxxx] a écrit:
[...]
> where ${dev} is the first argument. I checked these steps and I found
> that the last command `ip addr flush ${dev}` drops the properties of
> inet and brd.
>
> According to xenwiki/XenNetworking page, peth0 should have network
> address since it comes the interface directly connected to the
> external.
> The drop of inet and brd properties may be the reason of the problem
> that Dom0 cannot communicate with the external machines.
Here, on a setup using the network-bridge topology, we have, after
starting Xen :
- eth0 in Dom0 : which has the ip address
- peth0 : the physical ethernet
- vif0.0 : the other extremity of eth0
- xenbr0 : the bridge where peth0 and vif0.0 (and the further vifX) are
included
So, from this point of view, what you get seems quite normal.
--
Dominique Rousseau
Neuronnexion, Prestataire Internet & Intranet
57, route de Paris 80000 Amiens
tel: 03 22 71 61 90 - fax: 03 22 71 61 99 - http://www.neuronnexion.fr
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
I was having the same difficulty with Etch: networking was broken on
Dom0 when using network-bridge, worked fine with network-dummy.
However, I was just able to install a DomU using debootstrap with
network-dummy selected, then had to switch to network-bridge and
restart xend to get networking happening for both. ifconfig on Dom0
shows fe:ff:blah MAC addresses for the bridge, vif, and peth
interfaces, which seems odd to me. It also seems odd that networking
for Dom0 only works when a DomU is brought up. But I'm new to this,
so a lot of it seems odd.
--
Matt
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home