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] Networking doesn't work

On Fri, Mar 16, 2007 at 07:31:40AM +1100, Russell Robinson wrote:
> Hi,
> 
> Sorry, spoke too soon
> 
> Friday, March 16, 2007, 7:10:22 AM, you wrote:
> RR> I *knew* it was something simple:
> RR>   ifconfig veth3 IPAddr up
> 
> This made IPAddr respond to ping, but it's not the guest/domU.
> 
> The Wiki docs don't seem to be correct....missing lots of information
> and my dom0 doesn't have a peth0 interface created by the bridge, as
> described (is that the problem)?
> 

Yeah, I was just prep'ing a reply to tell you not to get too excited.
A working bridge configuration for you should look like:

  $ brctl show
  bridge name     bridge id               STP enabled     interfaces
  xenbr0          8000.feffffffffff       no              vif0.0
                                                          peth0
                                                          vif3.0

At the moment it appears that the xen network-bridge script was
very unsuccessful in putting your eth0 interface onto the bridge. 
Can you check the xen logfiles as well of the syslog to see if there is
any indication of why this failed.

My initial gut feeling was that it was because you were using aliases
(ie you have an interface called eth0:0). I recommend that you take down
that eth0:0 interface and try again. 

However, I must note that I did a quick experiment here involving 
aliases and the xen scripts still worked (though eth0:0 was 
changed to eth0:2). Utlimately you will be better off using 
"ip addr add" to add additional ip addresses to your interfaces 
rather than using old-style aliases - but this probably won't solve 
all your problems here unfortunatly. 

Let us know how you get on searching the logs, and trying again without
eth0:0. 

Also, if you are running iptables this is going to get in the way of any
tests you conduct - so watch out for this.


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