From: Jakub Sitnicki <jakub@cloudflare.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, netdev@vger.kernel.org,
kernel-team@cloudflare.com
Subject: [PATCH] ip.7: Document IP_LOCAL_PORT_RANGE socket option
Date: Wed, 1 Feb 2023 13:36:34 +0100 [thread overview]
Message-ID: <20230201123634.284689-1-jakub@cloudflare.com> (raw)
Linux commit 91d0b78c5177 ("inet: Add IP_LOCAL_PORT_RANGE socket option")
introduced a new socket option available for AF_INET and AF_INET6 sockets.
Option will be available starting from Linux 6.3. Document it.
Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
---
Submitting this man page update as the author of the feature.
We did a technical review of the man page text together with the code [1].
[1]: https://lore.kernel.org/all/20221221-sockopt-port-range-v6-0-be255cc0e51f@cloudflare.com/
---
man7/ip.7 | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/man7/ip.7 b/man7/ip.7
index f69af1b32..f166c3b57 100644
--- a/man7/ip.7
+++ b/man7/ip.7
@@ -439,6 +439,27 @@ and
.B IP_TOS
are ignored.
.TP
+.BR IP_LOCAL_PORT_RANGE " (since Linux 6.3)"
+Set or get the per-socket default local port range. This option can be used to
+clamp down the global local port range, defined by the
+.I ip_local_port_range
+.I /proc
+interface described below, for a given socket.
+.IP
+The option takes an
+.I uint32_t
+value with the high 16 bits set to the upper range bound, and the low 16 bits
+set to the lower range bound. Range bounds are inclusive. The 16-bit values
+should be in host byte order.
+.IP
+The lower bound has to be less than the upper bound when both bounds are not
+zero. Otherwise, setting the option fails with EINVAL.
+.IP
+If either bound is outside of the global local port range, or is zero, then that
+bound has no effect.
+.IP
+To reset the setting, pass zero as both the upper and the lower bound.
+.TP
.BR IP_MSFILTER " (since Linux 2.4.22 / 2.5.68)"
This option provides access to the advanced full-state filtering API.
Argument is an
--
2.39.1
next reply other threads:[~2023-02-01 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:36 Jakub Sitnicki [this message]
2023-02-03 18:58 ` [PATCH] ip.7: Document IP_LOCAL_PORT_RANGE socket option Stephen Hemminger
2023-02-03 19:09 ` Simon Horman
2023-02-05 13:16 ` Alejandro Colomar
2023-02-06 10:42 ` Jakub Sitnicki
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=20230201123634.284689-1-jakub@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=alx.manpages@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
/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 NNTP newsgroup(s).