netdev - Re: [PATCH net-next 00/23] netfilter: flowtable enhancements

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]

Message-ID: <20210311124705.0af44b8d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Thu, 11 Mar 2021 12:47:05 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Pablo Neira Ayuso <pablo@...filter.org>
Cc:     netfilter-devel@...r.kernel.org, davem@...emloft.net,
        netdev@...r.kernel.org, Felix Fietkau <nbd@....name>
Subject: Re: [PATCH net-next 00/23] netfilter: flowtable enhancements

On Thu, 11 Mar 2021 01:35:41 +0100 Pablo Neira Ayuso wrote:
> The following patchset augments the Netfilter flowtable fastpath to
> support for network topologies that combine IP forwarding, bridge,
> classic VLAN devices, bridge VLAN filtering, DSA and PPPoE. This
> includes support for the flowtable software and hardware datapaths.
> 
> The following pictures provides an example scenario:
> 
>                         fast path!
>                 .------------------------.
>                /                          \
>                |           IP forwarding  |
>                |          /             \ \/
>                |       br0               wan ..... eth0
>                .       / \                         host C
>                -> veth1  veth2  
>                    .           switch/router
>                    .
>                    .
>                  eth0
> 		host A
> 
> The bridge master device 'br0' has an IP address and a DHCP server is
> also assumed to be running to provide connectivity to host A which
> reaches the Internet through 'br0' as default gateway. Then, packet
> enters the IP forwarding path and Netfilter is used to NAT the packets
> before they leave through the wan device.
> 
> The general idea is to accelerate forwarding by building a fast path
> that takes packets from the ingress path of the bridge port and place
> them in the egress path of the wan device (and vice versa). Hence,
> skipping the classic bridge and IP stack paths.

And how did you solve the invalidation problem?