netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fernando@intellilink.co.jp
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] TCP: Use 32768-65535 outgoing port range by default
Date: Tue, 03 Apr 2012 02:28:37 -0400 (EDT)	[thread overview]
Message-ID: <20120403.022837.1830755903242379322.davem@davemloft.net> (raw)
In-Reply-To: <20120403141827.sakagdugg04os8w8@webmail.int.intellilink.co.jp>

From: fernando@intellilink.co.jp
Date: Tue,  3 Apr 2012 14:18:27 +0900

> The thing is that certain non-linux hosts already use a superset of
> the 61000-65095 range and 61000 looks like a magic number to most
> users.

Who cares what other systems usage, it's only an issue about local
port allocations and locally performed masquerading.

> Do you want me to document where 61000 comes from instead?

I think the current documentation on this is adequate.

  reply	other threads:[~2012-04-03  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  0:48 [PATCH 1/2] TCP: update ip_local_port_range documentation fernando
2012-04-03  0:50 ` [PATCH 2/2] TCP: Use 32768-65535 outgoing port range by default fernando
2012-04-03  4:50   ` David Miller
2012-04-03  5:18     ` fernando
2012-04-03  6:28       ` David Miller [this message]
2012-04-03  4:54 ` [PATCH 1/2] TCP: update ip_local_port_range documentation David Miller
2012-04-03  4:59   ` fernando
2012-04-03 11:08   ` fernando
2012-04-03 11:12     ` [PATCH] " fernando
2012-04-03 18:41       ` [PATCH v3] " fernando
2012-04-03 21:40         ` David Miller

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=20120403.022837.1830755903242379322.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fernando@intellilink.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).