[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iLE-2O8ZJGv+TqrPt+kh-ku8JdkyA4qtR=RKitt7rgrAA@mail.gmail.com>
Date: Tue, 24 Jan 2023 18:14:09 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Kuniyuki Iwashima <kuniyu@...zon.com>,
Neal Cardwell <ncardwell@...gle.com>,
Leon Romanovsky <leon@...nel.org>, selinux@...r.kernel.org,
Paul Moore <paul@...l-moore.com>,
Stephen Smalley <stephen.smalley.work@...il.com>,
Eric Paris <eparis@...isplace.org>, kernel-team@...udflare.com,
Marek Majkowski <marek@...udflare.com>
Subject: Re: [PATCH net-next v6 1/2] inet: Add IP_LOCAL_PORT_RANGE socket option
On Tue, Jan 24, 2023 at 2:36 PM Jakub Sitnicki <jakub@...udflare.com> wrote:
>
> Users who want to share a single public IP address for outgoing connections
> between several hosts traditionally reach for SNAT. However, SNAT requires
> state keeping on the node(s) performing the NAT.
>
> A stateless alternative exists, where a single IP address used for egress
> can be shared between several hosts by partitioning the available ephemeral
> port range. In such a setup:
>
> [1] https://github.com/cloudflare/cloudflare-blog/blob/232b432c1d57/2022-02-connectx/connectx.py#L116
>
> Reviewed-by: Marek Majkowski <marek@...udflare.com>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@...zon.com>
> Signed-off-by: Jakub Sitnicki <jakub@...udflare.com>
>
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists