| 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
| ||
|
Message-Id:
<171526322793.14863.3674169086267452877.git-patchwork-notify@kernel.org>
Date: Thu, 09 May 2024 14:00:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Samuel Thibault <samuel.thibault@...-lyon.org>
Cc: tparkin@...alix.com, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, jchapman@...alix.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCHv2] l2tp: Support several sockets with same IP/port quadruple
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Mon, 6 May 2024 23:53:35 +0200 you wrote:
> Some l2tp providers will use 1701 as origin port and open several
> tunnels for the same origin and target. On the Linux side, this
> may mean opening several sockets, but then trafic will go to only
> one of them, losing the trafic for the tunnel of the other socket
> (or leaving it up to userland, consuming a lot of cpu%).
>
> This can also happen when the l2tp provider uses a cluster, and
> load-balancing happens to migrate from one origin IP to another one,
> for which a socket was already established. Managing reassigning
> tunnels from one socket to another would be very hairy for userland.
>
> [...]
Here is the summary with links:
- [PATCHv2] l2tp: Support several sockets with same IP/port quadruple
https://git.kernel.org/netdev/net-next/c/628bc3e5a1be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists