Re: [PATCH net-next 1/2] bpf: Allow IP_TRANSPARENT and IPV6_TRANSPARENT in bpf_{set,get}sockopt()

On Fri, Jul 31, 2026 at 10:51 AM Shivaji Kant [off-list ref] wrote:

Currently, bpf_setsockopt() and bpf_getsockopt() for SOL_IP and SOL_IPV6
only allow a small subset of socket options (such as IP_TOS,
IPV6_TCLASS, and IPV6_AUTOFLOWLABEL). Calling bpf_setsockopt() with
IP_TRANSPARENT or IPV6_TRANSPARENT fails with -EINVAL.

Transparent proxying (TPROXY) and related networking components often
rely on IP_TRANSPARENT and IPV6_TRANSPARENT to enable binding sockets
to non-local IP addresses.

Allow IP_TRANSPARENT for SOL_IP in sol_ip_sockopt() and
IPV6_TRANSPARENT for SOL_IPV6 in sol_ipv6_sockopt().

Tested-by: Anubhav Singh <redacted>
Signed-off-by: Shivaji Kant <redacted>

Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>

Change itself looks good, but please rebase on bpf-next.git and
respin with the correct branch tag to trigger CI (and maybe Sashiko?).

  Subject: [PATCH bpf-next v2 1/2] bpf: ...