On 6/25/14, 6:16 AM, Vasiliy Tolstov wrote:
2014-06-24 19:23 GMT+04:00 Lori Jakab <loja...@cisco.com>:
Others who know better can correct me, but I think there is more work
involved than that. For now, the data structures and code supporting
tunnels is IPv4 specific, and you would need to change more than one file,
and not just the datapath (user space needs support as well, e.g.
lib/odp-util.c).
I'm try to create vxlan tunnel with local_ip and remote_ip has ipv6
address, and ovs-vsctl does not provide any errors...
I just tried the following, after compiling OVS from the Git master branch:
$ sudo ovs-vsctl add-port br0 vxl0 -- set Interface vxl0 type=vxlan
options:remote_ip=2001::1
ovs-vsctl: Error detected while setting up 'vxl1'. See ovs-vswitchd log
for details.
As you can see, I get an error. More details in the logs:
Jun 26 16:22:30 ovs2 ovs-vswitchd: ovs|00030|socket_util|ERR|"2001::1"
is not a valid IP address
Jun 26 16:22:30 ovs2 ovs-vswitchd: ovs|00031|netdev_vport|WARN|vxl1: bad
vxlan 'remote_ip'
Jun 26 16:22:30 ovs2 ovs-vswitchd: ovs|00032|netdev_vport|ERR|vxl1:
vxlan type requires valid 'remote_ip' argument
Jun 26 16:22:30 ovs2 ovs-vswitchd: ovs|00033|netdev|WARN|vxl1: could not
set configuration (Invalid argument)
Older versions of ovs-vsctl may not report the error, but you will see
it on the ovs-vswitchd log file.
Implementing IPv6 support for tunnels is not trivial. You need to add
support in both user space and kernel datapath, and the netlink protocol
between the two. This involves changes in many files.
-Lori
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
