Setup: passt 2026_10_02.cba3570, Podman 6.1.4, kernel 7.3.4 (openSUSE MicroOS), rootless; a WireGuard client (gluetun, kernel WireGuard) in a container on a Podman bridge network, so its UDP leaves through pasta. Host: net.core.rmem_default = 212992, rmem_max = 4194304. Observed: downloads through the tunnel reach 4-8 MB/s on a line that serves ~30 MB/s without it. During a 15 s download the host counts 300-15000 UdpRcvbufErrors (nstat). Counting the tunnel's datagrams at the host NIC, pasta's tap in the rootless netns, the container's eth0 and the WireGuard interface shows no loss after pasta once the buffer is large enough. With net.core.rmem_default = 4194304 (nothing else changed, container restarted so pasta opens new sockets): 0 UdpRcvbufErrors, 24-27 MB/s. The same tunnel under rootful Docker on another host reaches line rate with the kernel defaults, as no socket is involved there. Source: udp.c / udp_flow.c / sock_l4() set no SO_RCVBUF on UDP sockets; SO_RCVBUF/SO_SNDBUF are set only on the tap fd (tap.c), after sock_probe_features(). Unlike TCP there is no autotuning for UDP, so the socket keeps rmem_default. Question: could pasta set SO_RCVBUF on its UDP sockets (e.g. up to rmem_max when sock_probe_features() allows large buffers, as for the tap fd), or offer an option for it? Raising rmem_default host-wide works but affects every socket on the host.