netdev - Re: [PATCH v3] add GENEVE netdev tunnel driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 May 2015 15:59:59 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	netdev@...r.kernel.org, jesse@...ira.com, azhou@...ira.com,
	stephen@...workplumber.org, alexander.h.duyck@...hat.com
Subject: Re: [PATCH v3] add GENEVE netdev tunnel driver

From: "John W. Linville" <linville@...driver.com>
Date: Wed, 13 May 2015 12:57:25 -0400

> This 5-patch kernel series adds a netdev implementation of a GENEVE
> tunnel driver, and the single iproute2 patch enables creation and
> such for those netdevs.  This makes use of the existing GENEVE
> infrastructure already used by the OVS code.  The net/ipv4/geneve.c
> file is renamed as net/ipv4/geneve_core.c as part of these changes.
 ...
> The overall structure of the GENEVE netdev driver is strongly
> influenced by the VXLAN netdev driver.  This is not surprising, as the
> two drivers are intended to serve similar purposes.  As development of
> the GENEVE driver continues, it is likely that those similarities will
> grow stronger.  This will include both simple configuration options
> (e.g. TOS and TTL settings) and new control plane support.
> 
> The current implementation is very simple, restricting itself to point
> to point links over IPv4.  This is due only to the simplicity of the
> implementation, and no such limit is inherent to GENEVE in any way.
> Support for IPv6 links and more sophisticated control plane options
> are predictable enhancements.
> 
> Using the included iproute2 patch, a GENEVE tunnel is created thusly:
> 
>         ip link add dev gnv0 type geneve remote 192.168.22.1 vni 1234
>         ip link set gnv0 up
>         ip addr add 10.1.1.1/24 dev gnv0
> 
> After a corresponding tunnel interface is created at the link partner,
> traffic should proceed as expected.
> 
> Please let me know if anyone has problems...thanks!

Looks good, series applied, thanks John!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html