netdev - Re: [PATCH net-next RFC v2 0/3] light weight tunnel infrastructure and 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] [day] [month] [year] [list]

Message-ID: <55842FC9.8080400@cumulusnetworks.com>
Date:	Fri, 19 Jun 2015 08:05:45 -0700
From:	roopa <roopa@...ulusnetworks.com>
To:	Robert Shearman <rshearma@...cade.com>
CC:	ebiederm@...ssion.com, tgraf@...g.ch, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next RFC v2 0/3] light weight tunnel infrastructure
 and driver

On 6/19/15, 7:38 AM, Robert Shearman wrote:
>> This series implements infrastructure for light weight tunnels to 
>> support
>> mpls label edge routers (ie mpls ip tunnels). As previously discussed
>> having netdevices will not scale. Hence this series introduces new 
>> RTA_ENCAP*
>> attributes to attach encap information with routes (following suggestion
>> from Eric Biederman).
>
> Looks promising, thanks for posting this series Roopa!
>
>>
>> The first patch introduces an infrastructure to support light weight 
>> tunnels
>> that dont have netdevices. The infrastructure allows tunnel drivers
>> to register handlers to parse and build tunnel encap data which can 
>> be attached
>> to each route nexthop.
>>
>> The second patch adds support in ipv4 fib to carry such light weight 
>> tunnel
>> encap data.
>
> I presume this isn't ready to be merged until IPv6 is done, right?
yes, I will be adding ipv6 support soon. I will post the next non-RFC 
series with the ipv6 changes

thanks,
Roopa

--
To unsubscribe from this list: send the line "unsubscribe netdev" in