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

RE: [Xen-users] different vlans in different domU's

  • To: "Angel L. Mateo" <amateo@xxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "John Cianfarani" <jcianfarani@xxxxxxxxxx>
  • Date: Sat, 8 Apr 2006 14:32:54 -0400
  • Delivery-date: Sat, 08 Apr 2006 11:33:39 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Date:Content-class:Message-ID:X-MimeOLE:X-MS-Has-Attach:X-MS-TNEF-Correlator:Thread-Topic:Thread-Index:From:To; b=l8SEelDpILge/MMXW+/9MaZuqMifrOx0AGf82KgEn9+aMtVmB0ZyS2makJiF8TZZpLDlbY+vqUc9fCfhwl+Zy1eH/HF3dBzKU77J921kFfdpVB0Oaz8oijY56bQf6xLWGvir/9uVGEmG8lq6UKe0dZOedlBn2LREfhrAKmyvN0o= ;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcZZVhn8W8AgNmFyRcCjmLo3S7gxBACrWcrw
  • Thread-topic: [Xen-users] different vlans in different domU's

For me I have to run the below command in my domU because of the checksum bug.

ethtool -K eth0 tx off 


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Angel L. Mateo
Sent: Thursday, April 06, 2006 4:41 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] different vlans in different domU's


I am trying to configure xen to work with the same configuration:

* I have dom0 with one ethernet interface connected to my network. This
interface (eth0) has an IP address in the vlan assigned to its port (the
"typical" configuration).

* I have a domU which ethernet interface is in the same network (and
vlan). I configure this domU as:

vif = [ '' ]
ip="<its ip>"
netmask="<its netmask>"
gateway="<its gateway>"
hostname="<its hostname>"

this domU is working perfectly. I can boot it and I can connect to its
services (for example, ssh).

* I have another domU I want it to be connected to a different vlan,
although I want to use the same ethernet physical interface.

So I want to know how do I have to configure this domU so its network

In a typical configuration (without xen) I have to do:

1. vconfig add eth0 <vlan_id>: To create a virtual interface connected
to this vlan. This virtual interface will tag all sent packets with the
corresponding vlan tag.
2. Configure the interface eth0.<vland_id> with its corresponding IP
address, netmask, etc.

If a do this, I can work with the new IP, so the network switch is
correctly configured.

My problem is that I am trying to configure it (with xen) as:

1. I create the eth0.100 (for vlan id 100) interface with the vconfig
2. I do an ifconfig eth0.100 up
3. I create a new brigde called xen-br100
4. I run: /etc/xen/scripts/network start netdev=eth0.100
bridge=xen-br100 antispoof=no
5. I configure the domU as:

        vif = [ 'bridge=xen-br100' ]
        hostname="a hostname"

(this IP, netmask and gateway is the corresponding to my vlan 100).

With this configuration, network seems to work (just seems), because I
can ping to its IP address. The problem is that I can't contact with it
by udp neither tcp, just by icmp. But I run tcpdump in dom0 on the
eth0.100 interface, I can use all network functions in the domU (tcp and
udp too).

I have also check that I haven't got any filter (iptables or other) that
could filter it.

I don't know what I'm doing wrong. I'm not sure of needing another
bridge to this configuration (to work without xen, I don't need any
bridge to tag an interface). I've just followed the instructions found
in the xen howto at http://wiki.xensource.com/xenwiki/XenNetworking.

I guess this isn't an unsual configuration (having different domUs
running in the different networks and vlans), so I guess it could be
there a solution to this configuration.

Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información       _o)
y las Comunicaciones Aplicadas (ATICA)      / \\
http://www.um.es/atica                    _(___V
Tfo: 968367590
Fax: 968398337

Xen-users mailing list

Xen-users mailing list



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