From: Zhixu Liu <zhixu.liu@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Linux ephemeral port range defaults to "broken".
Date: Thu, 7 Aug 2025 14:44:39 +0800 [thread overview]
Message-ID: <CALMA0xYOAs-hSELvNa1tTrYC+rSX+E_OzjhJ8xP_yhSU1h1haw@mail.gmail.com> (raw)
In-Reply-To: <107102s$em0$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
>
>
> It's simple enough to change the ephemeral range so it doesn't overlap
> with registered port numbers, and it looks like I'm going to need to
> do that to avoid possible collisions in a project I'm working on. The
> question is why do I have to do that? The standards are pretty clear.
> Why does Linux default to being broken like that?
>
You can put your port in `ip_local_reserved_ports` to avoid being used by
automatic port assignments.
--
Z. Liu
[-- Attachment #2: Type: text/html, Size: 840 bytes --]
next prev parent reply other threads:[~2025-08-07 6:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 1:38 [gentoo-user] Linux ephemeral port range defaults to "broken" Grant Edwards
2025-08-07 3:49 ` Alexandru N. Barloiu
2025-08-07 6:44 ` Zhixu Liu [this message]
2025-08-07 13:04 ` Javier Martinez
2025-08-07 13:12 ` Javier Martinez
2025-08-07 14:01 ` [gentoo-user] " Grant Edwards
2025-08-07 14:25 ` Javier Martinez
2025-08-07 14:37 ` Javier Martinez
2025-08-10 1:54 ` [gentoo-user] " Grant Taylor
2025-08-10 21:13 ` [gentoo-user] " Grant Edwards
2025-08-10 21:25 ` Javier Martinez
2025-08-10 21:35 ` Grant Edwards
2025-08-10 21:28 ` Grant Edwards
2025-08-10 21:30 ` Javier Martinez
2025-08-10 21:39 ` Grant Edwards
2025-08-10 21:43 ` Javier Martinez
2025-08-10 22:55 ` Grant Edwards
2025-08-10 23:12 ` Javier Martinez
2025-08-10 21:59 ` Javier Martinez
2025-08-10 23:00 ` Grant Edwards
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=CALMA0xYOAs-hSELvNa1tTrYC+rSX+E_OzjhJ8xP_yhSU1h1haw@mail.gmail.com \
--to=zhixu.liu@gmail.com \
--cc=gentoo-user@lists.gentoo.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