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

[Xen-users] Xen IPv6 antispoof


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Peter Braun <xenware@xxxxxxxxx>
  • Date: Tue, 16 Feb 2010 01:21:02 +0100
  • Delivery-date: Mon, 15 Feb 2010 16:22:02 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I+YRwqYKYaME5bVJKHmJSsHNSAB93WZQhxIIvkcwpes2A6TxS/tkASt2DmciFktEUw hmQjZUXi9liH0SATEBzsbAR2TcWwTwm6IlZXBIT+D7OqcQ9WEH6LnLX2D8J1iI4amUa6 sqC6i4xqoHyZFnw1g4cG+DnXUQ9fNoTKuNr64=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

we are just testing IPv6 support - xen bridged mode.

IPv4 is specified all the time in domU.cfg. Now we added IPv6.

vif = [ 'vifname=Debian,ip=2001:110:0::1:2/64 99.99.99.99' ]

User inside domU can change his IPv4 address but he will be not able
to communicate with outside world.

But same thing doesn't work for specified IPv6 address.
Changing IPv6 address inside domU to 2001:110:1::1:3/64 simply works.

Question is how to prevent?


Br


Peter

_______________________________________________
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®.