From: Cong Wang <amwang@redhat.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: linux-kernel@vger.kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Neil Horman <nhorman@tuxdriver.com>,
linux-sctp@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [RFC Patch] net: reserve ports for applications using fixed port numbers
Date: Thu, 04 Feb 2010 11:23:38 +0800 [thread overview]
Message-ID: <4B6A3DBA.1000706@redhat.com> (raw)
In-Reply-To: <201002031312.48531.opurdila@ixiacom.com>
Octavian Purdila wrote:
> On Wednesday 03 February 2010 06:30:07 you wrote:
>
>> This patch introduces /proc/sys/net/ipv4/ip_local_reserved_ports,
>> it can be used like ip_local_port_range, but this is used to
>> reserve ports for third-party applications which use fixed
>> port numbers within ip_local_port_range.
>>
>> This only affects the applications which call socket functions
>> like bind(2) with port number 0, to prevent the kernel getting the ports
>> within the specified range for them. For applications which use fixed
>> port number, it will have no effects.
>
> It also affects the case where applications do connect, without previously
> doing bind, right?
Yeah, I forgot to mention this, sorry.
>
>> Any comments are welcome.
>
> I think it might be useful to allow setting individual ports as reserved, not
> only ranges, for example by using a bitmap.
>
This is a good idea, but I am not sure if this will be overkill? :-/
Also, using bitmap is not friendly to sysctl interface, I am afraid.
Thanks!
next prev parent reply other threads:[~2010-02-04 3:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 4:30 [RFC Patch] net: reserve ports for applications using fixed port numbers Amerigo Wang
2010-02-03 4:39 ` Eric Dumazet
2010-02-03 5:15 ` Cong Wang
2010-02-03 11:12 ` Octavian Purdila
2010-02-04 3:23 ` Cong Wang [this message]
2010-02-04 12:44 ` Octavian Purdila
2010-02-04 17:41 ` David Miller
2010-02-04 18:15 ` Octavian Purdila
2010-02-04 18:21 ` David Miller
2010-02-04 21:45 ` Tetsuo Handa
2010-02-04 21:56 ` David Miller
2010-02-05 0:41 ` Tetsuo Handa
2010-02-05 1:05 ` Octavian Purdila
2010-02-05 6:01 ` Cong Wang
2010-02-05 12:28 ` Octavian Purdila
2010-02-05 4:45 ` Cong Wang
2010-02-05 12:05 ` Octavian Purdila
2010-02-08 3:21 ` Cong Wang
2010-02-08 16:51 ` Octavian Purdila
2010-02-05 7:11 ` Bart Van Assche
2010-02-05 7:25 ` Cong Wang
2010-02-05 9:08 ` [RFC Patch] net: reserve ports for applications using fixed portnumbers Tetsuo Handa
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=4B6A3DBA.1000706@redhat.com \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=opurdila@ixiacom.com \
/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).