netdev - Re: NVGRE for Linux

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>] [day] [month] [year] [list]

Message-ID: <CAEnQRZDvqkSgvS5Ur9L-Q17kNDAVuNn3JsWm5u_raThBD5xubQ@mail.gmail.com>
Date:	Tue, 11 Jun 2013 16:23:25 +0300
From:	Daniel Baluta <daniel.baluta@...il.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	netdev@...r.kernel.org
Subject: Re: NVGRE for Linux

On Mon, Jun 10, 2013 at 7:46 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> On Mon, 10 Jun 2013 08:21:49 -0700
> Daniel Baluta <daniel.baluta@...il.com> wrote:
>
>> Hi,
>>
>> Is there anyone working on implementing NVGRE [1] in Linux kernel?
>>
>> A significant part of the code can be borrowed from VXLAN [2] (netlink
>> ops, fdb ops),
>> while another important part (packet reception/transmission) is based
>> on GRE tunneling code [3].
>>
>> Is this approach correct? Any suggestions are welcomed.
>>
>> thanks,
>> Daniel.
>>
>> [1] http://datatracker.ietf.org/doc/draft-sridharan-virtualization-nvgre/
>> [2] drivers/net/vxlan.c
>> [3] net/ipv4/ip_gre.c
>
> Packet transmission is not a problem the existing GRE provides more the necessary decode/encode.
> The problem problem is that you would need a management entity. Most of the interesting bits
> for connecting with real world clouds like Azure remain unspecified in RFC.

That's right. The RFC defers a lot of important details for the next
version (e.g 4.4 Address/Policy Management ).
For the moment, I will try to experiment with statically defined fdbs.

Thanks!
--
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