netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: David Miller <davem@davemloft.net>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Linux Kernel Developers <linux-kernel@vger.kernel.org>,
	Neil Horman <nhorman@tuxdriver.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [net-next PATCH v5 0/3] net: reserve ports for applications using fixed port numbers
Date: Sun, 21 Feb 2010 09:58:54 +0800	[thread overview]
Message-ID: <4B80935E.5040901@redhat.com> (raw)
In-Reply-To: <201002201557.04427.opurdila@ixiacom.com>

Octavian Purdila wrote:
> On Saturday 20 February 2010 10:11:40 you wrote:
> 
>> 2) I hope you could add some documentation to show the relations
>>     between ip_local_port_range and ip_local_reserved_ports.
>>
> 
> How does this sound:
> 
> ip_local_reserved_ports - list of comma separated ranges
>         Specify the ports which are reserved for known third-party
>         applications. These ports will not be used by automatic port
>         assignments (e.g. when calling connect() or bind() with port
>         number 0). Explicit port allocation behavior is unchanged.
> 
>         The format used for both input and output is a comma separated
>         list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
>         10). Writing to the file will clear all previously reserved
>         ports and update the current list with the one given in the
>         input.
> 
>         Note that ip_local_port_range and ip_local_port_range settings
>         are independent and both are considered by the kernel when
>         determining which ports are available for automatic port
>         assignments.
> 
>         You can reserve ports which are not in the current
>         ip_local_port_range, e.g.:
> 
>         $ cat /proc/sys/net/ipv4/ip_local_port_range
>         32000   61000
>         $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
>         8080,9148
> 
>         although this is redundant. However such a setting is useful
>         if later the port range is changed to a value that will
>         include the reserved ports.

This looks fine for me.

Thanks.


  reply	other threads:[~2010-02-21  1:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:30 [net-next PATCH v5 0/3] net: reserve ports for applications using fixed port numbers Octavian Purdila
2010-02-18 22:30 ` [net-next PATCH v5 1/3] sysctl: refactor integer handling proc code Octavian Purdila
2010-02-18 22:30 ` [net-next PATCH v5 3/3] net: reserve ports for applications using fixed port numbers Octavian Purdila
2010-02-20  8:20   ` Cong Wang
2010-02-20 13:27     ` Octavian Purdila
2010-02-21  2:00       ` Cong Wang
2010-02-21  6:38   ` Cong Wang
2010-02-20  8:11 ` [net-next PATCH v5 0/3] " Cong Wang
2010-02-20 13:57   ` Octavian Purdila
2010-02-21  1:58     ` Cong Wang [this message]
2010-02-21  6:10     ` Bill Fink

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=4B80935E.5040901@redhat.com \
    --to=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@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).