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

[Xen-devel] vlan between domU and dom0 on the same host via a bridge?


  • To: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Nicholas Lee <emptysands@xxxxxxxxx>
  • Date: Sat, 19 Nov 2005 00:13:36 +1300
  • Delivery-date: Fri, 18 Nov 2005 11:13:35 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Zyaz8PJWkOpSdbScAkmd1NwDWu9ghrsGBv8173BIfU7PuDSRE33rFuOebKfSkcGfI59pVqE6poZkVmeQbwdQ1mY/RBaDM1S2kXi3Kji5QpPQUF7+YI/8PxJDUU3rlzfiRrYnLE71xxD99YUEVJilVCflAhGtI5UU2MqEubxiRL0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

With Xen 2.0/Debian in standard bridged mode.

Seems easy enough to get vlans working between domUs on the same host.
 Don't have a vlan switch handy, so I haven't try it between two
different hosts.

I was able to get a vconfig add eth0 2; ifconfig eth0.2 172.16.0.2;
ping 172.16.0.1, working in a trival way without doing any
configuration in dom0.

However I'm not sure how to get a vlan interface on dom0 to talk via
the bridge to the vlans in the domUs.

Neither vconfig add eth0 2 or vconfig add xen-br0 2 seemed to work.
Also adding (addif) either interface to the bridge didn't help either.

Suggestions or hints?


My goal is to have two or more machines/dom0 operating in a basic
manner, and domUs on these machines segmented into different networks.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

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


 


Rackspace

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