public inbox for passt-user@passt.top
 help / color / mirror / Atom feed
* CAP_NET_BIND_SERVICE does not allow binding to low ports
@ 2026-10-14 14:32 Nicholas Rodrigues Lordello
  2026-11-15 23:24 ` Stefano Brivio
  0 siblings, 1 reply; 2+ messages in thread
From: Nicholas Rodrigues Lordello @ 2026-10-14 14:32 UTC (permalink / raw)
  To: passt-user

Hey all,

Just wanted to report what is either a documentation issur, or an
issue in `passt` proper. The `man` pages document the following for
binding to low numbered (i.e. service ports):

    or the CAP_NET_BIND_SERVICE Linux capability is granted, see
    services(5) and capabilities(7).

    [...]

    To grant this capability, you can issue, as root:

        for p in $(which passt passt.avx2); do
            setcap 'cap_net_bind_service=+ep' "${p}"
        done

However, this does not work:

    # setcap 'cap_net_bind_service=+ep' /usr/local/bin/passt
    # setcap 'cap_net_bind_service=+ep' /usr/local/bin/passt.avx2
    $ /usr/local/bin/passt -f -t 123
    Listen failed for HOST TCP port */123: Permission denied
    Couldn't listen on requsted ports
    [1]

The reason I'm asking is that `krun` uses `passt` for port forwarding
and is having issues with service ports [1]. The current work-around is
to set the `net.ipv4.ip_unprivileged_port_start` sysctl to a lower
number in the container where `passt` is run, but since `passt` is
started already with `CAP_NET_BIND_SERVICE` it would be nice for that
to work and not require the `sysctl` work-around.

Anyway, curious to know if this is documentation issue or actually
something that should be working but isn't (or a local setup issue).


Regards,
Nick

[1]: <https://github.com/containers/crun/issues/2251>



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: CAP_NET_BIND_SERVICE does not allow binding to low ports
  2026-10-14 14:32 CAP_NET_BIND_SERVICE does not allow binding to low ports Nicholas Rodrigues Lordello
@ 2026-11-15 23:24 ` Stefano Brivio
  0 siblings, 0 replies; 2+ messages in thread
From: Stefano Brivio @ 2026-11-15 23:24 UTC (permalink / raw)
  To: Nicholas Rodrigues Lordello; +Cc: passt-user

Hi Nick,

Sorry for the delay.  I finally found a moment to look into this:

On Wed, 14 Oct 2026 14:32:43 +0000
Nicholas Rodrigues Lordello <n@lordello.net> wrote:

> Hey all,
> 
> Just wanted to report what is either a documentation issur, or an
> issue in `passt` proper. The `man` pages document the following for
> binding to low numbered (i.e. service ports):
> 
>     or the CAP_NET_BIND_SERVICE Linux capability is granted, see
>     services(5) and capabilities(7).
> 
>     [...]
> 
>     To grant this capability, you can issue, as root:
> 
>         for p in $(which passt passt.avx2); do
>             setcap 'cap_net_bind_service=+ep' "${p}"
>         done
> 
> However, this does not work:
> 
>     # setcap 'cap_net_bind_service=+ep' /usr/local/bin/passt
>     # setcap 'cap_net_bind_service=+ep' /usr/local/bin/passt.avx2
>     $ /usr/local/bin/passt -f -t 123
>     Listen failed for HOST TCP port */123: Permission denied
>     Couldn't listen on requsted ports
>     [1]
> 
> The reason I'm asking is that `krun` uses `passt` for port forwarding
> and is having issues with service ports [1]. The current work-around is
> to set the `net.ipv4.ip_unprivileged_port_start` sysctl to a lower
> number in the container where `passt` is run, but since `passt` is
> started already with `CAP_NET_BIND_SERVICE` it would be nice for that
> to work and not require the `sysctl` work-around.
> 
> Anyway, curious to know if this is documentation issue or actually
> something that should be working but isn't (or a local setup issue).

...ideally we'd like it to work (not for automatic port forwards, and
also not for runtime ones, that is, configured via pesto(1)), but:

  https://archives.passt.top/passt-dev/Y0YshqEtFoCRlLH9@yekko/

on the other hand, there would be a way to fix it, by reordering things
a bit and postponing isolation steps.  This was my draft from 4 years
ago:

  https://archives.passt.top/passt-dev/20221013125017.195769cf@elisabeth/

now things changed quite a bit, but what would need to be done is
essentially to move the isolate_user() call *after* the initial
fwd_listen_init() call.  There might be a few implications, I don't
think it's as simple as moving that single call, but I think it should
be doable.

-- 
Stefano


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-11-15 23:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-14 14:32 CAP_NET_BIND_SERVICE does not allow binding to low ports Nicholas Rodrigues Lordello
2026-11-15 23:24 ` Stefano Brivio

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).