netdev - Re: [PATCH next 3/3] ipvlan: Introduce l3s mode

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:   Fri, 9 Sep 2016 15:07:32 -0700
From:   Rick Jones <rick.jones2@....com>
To:     Mahesh Bandewar <mahesh@...dewar.net>,
        netdev <netdev@...r.kernel.org>
Cc:     Eric Dumazet <edumazet@...gle.com>,
        David Miller <davem@...emloft.net>,
        Mahesh Bandewar <maheshb@...gle.com>
Subject: Re: [PATCH next 3/3] ipvlan: Introduce l3s mode

On 09/09/2016 02:53 PM, Mahesh Bandewar wrote:

> @@ -48,6 +48,11 @@ master device for the L2 processing and routing from that instance will be
>  used before packets are queued on the outbound device. In this mode the slaves
>  will not receive nor can send multicast / broadcast traffic.
>
> +4.3 L3S mode:
> +	This is very similar to the L3 mode except that iptables conn-tracking
> +works in this mode and that is why L3-symsetric (L3s) from iptables perspective.
> +This will have slightly less performance but that shouldn't matter since you
> +are choosing this mode over plain-L3 mode to make conn-tracking work.

What is that first sentence trying to say?  It appears to be incomplete, 
and is that supposed to be "L3-symmetric?"

happy benchmarking,

rick jones