On Wed, Jun 08, 2016 at 03:21:58PM -0300, Thadeu Lima de Souza Cascardo wrote:
> This series adds support for the creation of tunnels using the rtnetlink
> interface. This will open the possibility for new features and flags on those
> vports without the need to change vport compatibility code.
>
> Support for STT and LISP have not been added because these are not upstream
> yet,
> so we don't know how the interface will be like upstream. And there are no
> features in the current drivers right now we could make use of.
>
> We are able to set the MTU to UINT16_MAX since it is not restricted by the
> driver during newlink.
>
> Thadeu Lima de Souza Cascardo (5):
> netdev: get device type from vport prefix if not found
> dpif-netlink: break out code to add compat and non-compat vports
> dpif-netlink: add VXLAN creation support
> dpif-netlink: add GRE creation support
> dpif-netlink: add GENEVE creation support
>
> lib/dpif-netlink.c | 526
> ++++++++++++++++++++++++++++++++++++++++++++++++-----
> lib/netdev.c | 18 ++
> 2 files changed, 494 insertions(+), 50 deletions(-)
The patchset looks good to me, so I gave a try with vxlan interfaces
on Fedora 4.5.5-201.fc23.x86_64.
This is the recipe:
# ovs-vsctl add-port ovsbr0 vxlan0 \
-- set interface vxlan0 type=vxlan options:remote_ip=192.168.1.2
options:key=10
# ovs-vsctl add-port ovsbr0 vxlan1 \
-- set interface vxlan1 type=vxlan options:remote_ip=192.168.1.2
options:key=11
and I noticed on ovs-vswitchd.log this message repeated few times:
2016-06-15T17:00:05.993Z|00134|netdev_linux|INFO|tun0 device has
unknown hardware address family 65534
If I remove vxlan0 and vxlan1, the vxlan_sys_4789 remains.
And if I delete both vxlan ports and then add one back I get an error:
[root@plex ~]# ovs-vsctl del-port vxlan0
[root@plex ~]# ovs-vsctl del-port vxlan0
ovs-vsctl: no port named vxlan0
[root@plex ~]# ovs-vsctl add-port ovsbr0 vxlan0 -- set interface
vxlan0 type=vxlan options:remote_ip=192.168.1.2 options:key=10
ovs-vsctl: Error detected while setting up 'vxlan0'. See ovs-vswitchd
log for details.
2016-06-15T17:20:12.546Z|00164|dpif|WARN|system@ovs-system: failed to
add vxlan0 as port: File exists
Trying to add a completely new vxlan device doesn't help:
# ovs-vsctl add-port ovsbr0 vxlan66 -- set interface vxlan66
# type=vxlan options:remote_ip=192.168.1.66 options:key=66
ovs-vsctl: Error detected while setting up 'vxlan66'. See
ovs-vswitchd log for details.
2016-06-15T17:23:51.863Z|00199|dpif|WARN|system@ovs-system: failed to
add vxlan0 as port: File exists
Deleting the bridge or restarting openvswitch service didn't help.
--
fbl
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
