From: Nicholas Rodrigues Lordello <n@lordello.net>
To: passt-user@passt.top
Subject: CAP_NET_BIND_SERVICE does not allow binding to low ports
Date: Wed, 14 Oct 2026 14:32:43 +0000 [thread overview]
Message-ID: <A59F14D4-FC86-406E-8C06-EDB14F46E215@lordello.net> (raw)
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>
reply other threads:[~2026-10-14 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A59F14D4-FC86-406E-8C06-EDB14F46E215@lordello.net \
--to=n@lordello.net \
--cc=passt-user@passt.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).