netdev - Re: [PATCH net-next 0/4] ERSPAN version 2 (type III) 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 13 Dec 2017 17:54:46 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     William Tu <u9012063@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/4] ERSPAN version 2 (type III) support

On Wed, 13 Dec 2017 16:38:54 -0800
William Tu <u9012063@...il.com> 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.