netdev - Re: [PATCH iproute-next] tc: m_tunnel

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]

Date:   Sun, 13 Jan 2019 12:10:43 +0200
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     David Ahern <dsahern@...il.com>,
        Linux Netdev List <netdev@...r.kernel.org>,
        Adi Nissim <adin@...lanox.com>
Subject: Re: [PATCH iproute-next] tc: m_tunnel_key: Allow key-less tunnels

On Thu, Jan 10, 2019 at 3:05 PM Adi Nissim <adin@...lanox.com> wrote:
> Change the id parameter of the tunnel_key set action from mandatory to
> optional.
> Some tunneling protocols (e.g. GRE) specify the id as an optional field.

Hi,

The kernel code for the tunnel key actions allows keyless tunnels as
of 5.0 (commit
80ef0f22ceda "net/sched: act_tunnel_key: Allow key-less tunnels") - so this one
here is actually for iproute and not iproute-next, Stephen, could you look?

Or.