netdev - Re: [PATCH iproute2 net-next] gre6: add collect metadata support

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: <CALDO+SZrYbVVdgkF8xw3gOCxqCqop_sBdQsBQDfVn2j0GfyafQ@mail.gmail.com>
Date:   Mon, 4 Dec 2017 12:40:39 -0800
From:   William Tu <u9012063@...il.com>
To:     Gregory Rose <gvrose8192@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH iproute2 net-next] gre6: add collect metadata support

On Mon, Dec 4, 2017 at 9:26 AM, Gregory Rose <gvrose8192@...il.com> wrote:
> On 12/1/2017 3:03 PM, William Tu wrote:
>>
>> The patch adds 'external' option to support collect metadata
>> gre6 tunnel. Example of L3 and L2 gre device:
>> bash:~# ip link add dev ip6gre123 type ip6gre external
>> bash:~# ip link add dev ip6gretap123 type ip6gretap external
>
>
> Hi William,
>
> one question.  Is there ever actually going to be a situation in which an
> ipv6 gre tunnel will go from
> external to not external?  I'm wondering if the "no external" option is
> really needed since default is
> no and I'm not sure under what circumstances a tunnel would go from external
> to not external.
>
> Thanks,
>
> - Greg

good point. I don't think we should support setting a tunnel from
external to no external at run-time.
Let me remove the "noexternal" description in man page.
Thanks

William