From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH net-next 0/4] ERSPAN version 2 (type III) support Date: Wed, 13 Dec 2017 17:54:46 -0800 Message-ID: <20171213175446.18c98648@xeon-e3> References: <1513211938-8749-1-git-send-email-u9012063@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: William Tu Return-path: Received: from mail-pf0-f176.google.com ([209.85.192.176]:45821 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751042AbdLNByu (ORCPT ); Wed, 13 Dec 2017 20:54:50 -0500 Received: by mail-pf0-f176.google.com with SMTP id u19so2529099pfa.12 for ; Wed, 13 Dec 2017 17:54:50 -0800 (PST) In-Reply-To: <1513211938-8749-1-git-send-email-u9012063@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 13 Dec 2017 16:38:54 -0800 William Tu wrote: > ERSPAN has two versions, v1 (type II) and v2 (type III). This patch > series add support for erspan v2 based on existing erspan v1 > implementation. The first patch refactors the existing erspan v1's > header structure, making it extensible to put additional v2's header. > The second and third patch introduces erspan v2's implementation to > ipv4 and ipv6 erspan, for both native mode and collect metadata mode. > Finally, test cases are added under the samples/bpf. > > Note: > ERSPAN version 2 has many features and this patch does not implement > all. One major use case of version 2 over version 1 is its timestamp > and direction. So the traffic collector is able to distinguish the > mirrorred traffic better. Other features such as SGT (security group > tag), FT (frame type) for carrying non-ethernet packet, and optional > subheader are not implemented yet. > > Example commandline for ERSPAN version 2: > ip link add dev ip6erspan11 type ip6erspan seq key 102 \ > local fc00:100::2 remote fc00:100::1 \ > erspan_ver 2 erspan_dir 1 erspan_hwid 17 > > The corresponding iproute2 patch: > https://marc.info/?l=linux-netdev&m=151321141525106&w=2 If this is accepted to net-next you will need to resubmit the iproute2 patch.