netdev - Re: [PATCH net-next v5 0/3] New openvswitch MPLS actions for layer 2 tunnelling

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: <20191224.222504.1002685539423182176.davem@davemloft.net>
Date:   Tue, 24 Dec 2019 22:25:04 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     martinvarghesenokia@...il.com
Cc:     netdev@...r.kernel.org, pshelar@....org, scott.drennan@...ia.com,
        jbenc@...hat.com, martin.varghese@...ia.com
Subject: Re: [PATCH net-next v5 0/3] New openvswitch MPLS actions for layer
 2 tunnelling

From: Martin Varghese <martinvarghesenokia@...il.com>
Date: Sat, 21 Dec 2019 08:49:36 +0530

> The existing PUSH MPLS action inserts MPLS header between ethernet header
> and the IP header. Though this behaviour is fine for L3 VPN where an IP
> packet is encapsulated inside a MPLS tunnel, it does not suffice the L2
> VPN (l2 tunnelling) requirements. In L2 VPN the MPLS header should
> encapsulate the ethernet packet.
> 
> The new mpls action ADD_MPLS inserts MPLS header at the start of the
> packet or at the start of the l3 header depending on the value of l3 tunnel
> flag in the ADD_MPLS arguments.
> 
> POP_MPLS action is extended to support ethertype 0x6558
 ...

Series applied, thanks.