[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] No traffic between tap* and vif*


  • To: "Bert Sluijer" <a.j.sluijer@xxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
  • Date: Mon, 31 Mar 2008 10:15:06 -0400
  • Delivery-date: Mon, 31 Mar 2008 07:15:40 -0700
  • Importance: normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Priority: normal
  • Thread-index: AciTA/r5DaMclNbjQOyXWVDcR0ujEQANFKtg
  • Thread-topic: [Xen-users] No traffic between tap* and vif*

Bert Sluijer wrote:
> 
> Newbie-question:
> 
> After a big hassle trying to configure ubuntu-xen-server on 
> 7.10, I installed xen-3.2-testing.hg with linux-2.6.18-xen.hg 
> on ubuntu-7.10 . All things went fine and I got a stable 
> virtualization platform, without kernel-errors. I started the 
> w2k03-servers but they had no network. All 3 had a 169.x.x.x 
> ipaddress and could communicate between themselves but not 
> with the internet. Ifconfig on the host showed I had now 3 
> tap*-interfaces and als 3 vif*-interfaces. I learned from 
> tcpdump that there seems to be no communication between tap* and vif*.
> 
> I think I overlooked something on the interface configuration 
> of the host. 
> 
> brctl show:
> 
> bridge name     bridge id               STP enabled     interfaces
> eth0            8000.001e0b701252       no              peth0
>                                                         vif1.0
> xenbr0          8000.12f74675b5eb       no              tap0
>                                                         vif3.0
>                                                         tap2
>                                                         vif4.0
>                                                         vif8.0
>                                                         tap3
> 
> vif1.0 is a linux-guest which has connection to the internet. 
> Looking for clues!
> 
> Thanks,
> 
> Bert.

Bert,

It looks like you have a mixture of the older and newer bridge
networking scripts.

The newer versions the bridge scripts now create the primary
bridges named after their hardware interfaces instead of
'xenbrX'.

This allows for a simpler implementation on dom0. The newer
scripts are suppose to intercept interface calls for 'xenbrX'
and redirect them to the appropriate interface bridges 'ethX'.

So you would see all your virtual interfaces and tap devices
on bridge 'eth0' instead of 'xenbr0'. I would make sure that
the Ubuntu Xen packages aren't overwriting your Xen 3.2
setup.

If you wanted a 'routed' setup though, then this is correct,
but you need to set an IP for the bridge 'xenbr0', setup
appropriate routes and enable forwarding.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.