netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Evgeniy Polyakov <s0mbre@tservice.net.ru>,
	David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Is 64k bind patch making bad assumption?
Date: Mon, 2 Feb 2009 10:35:15 -0800	[thread overview]
Message-ID: <20090202103515.60788d0f@extreme> (raw)

The patch to allow more that 64k connections is assuming that
all IP addresses on a machine have the same connectivity and policy.
I can think of several cases where this is not true:
  1. Server machine with public IP's for connections and private IP's
     for backend database connection
  2. Applications where certain IP's are required for security
     protocols
  3. Machines doing policy based routing

Doesn't this patch change/break this?

             reply	other threads:[~2009-02-02 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 18:35 Stephen Hemminger [this message]
2009-02-02 18:46 ` Is 64k bind patch making bad assumption? Evgeniy Polyakov

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=20090202103515.60788d0f@extreme \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=s0mbre@tservice.net.ru \
    /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).