as far as i know the antispoof /egress filtering is done using ebtables.
I''ve checked and yes it supports ipv6.
Without knowing it, I would suspect that the xen network scripts are
missing some work on the ipv6 support. It might just be a wrong
syntax, but i doubt.
You should take this discussion to xen-devel and submit a bug report
somehow, somewhere. We''re in 2010 and ipv6 support is not
"optional"
any more.
florian
2010/2/16 Peter Braun <xenware@gmail.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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
--
''Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen''
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users