From: Phil Oester <kernel@linuxace.com>
To: Nebojsa Miljanovic <neb@alcatel-lucent.com>
Cc: linux-kernel@vger.kernel.org, "Kittlitz,
Edward \(Ned\)" <nkittlitz@alcatel-lucent.com>,
asweeney@alcatel-lucent.com, "Polhemus,
William \(Bart\)" <bpolhemus@alcatel-lucent.com>
Subject: Re: SO_REUSEADDR not allowing server and client to use same port
Date: Thu, 28 Feb 2008 10:30:54 -0800 [thread overview]
Message-ID: <20080228183054.GA903@linuxace.com> (raw)
In-Reply-To: <47C6FA2A.5030302@alcatel-lucent.com>
On Thu, Feb 28, 2008 at 12:15:06PM -0600, Nebojsa Miljanovic wrote:
> Hello all,
> I have seen similar complaints about this issue before in the list archive, but
> I have not seen any resolution. So, I am posting the question again in hope of
> getting some replies.
>
> Currently, Linux does not allow reuse of same local port for both TCP server and
> TCP client. I understand that there may be a need to prevent two servers from
> binding to the same local port, but having 1 server and 1 outgoing client use it
> should be allowed. Other Unix like operating systems do allow it. Further more,
> Linux SCTP socket API allows for this to happen. And, I can't imagine why this
> restriction would exists for TCP and not for SCTP.
You'd likely get better response by posting this on the netdev list.
Phil
next prev parent reply other threads:[~2008-02-28 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 18:15 SO_REUSEADDR not allowing server and client to use same port Nebojsa Miljanovic
2008-02-28 18:30 ` Phil Oester [this message]
2008-02-28 20:19 ` Alan Cox
2008-02-28 20:41 ` Willy Tarreau
2008-03-13 19:18 ` Nebojsa Miljanovic
2008-03-15 13:34 ` Alan Cox
2008-03-17 16:43 ` Nebojsa Miljanovic
2008-03-17 17:30 ` Alan Cox
2008-03-17 18:17 ` Nebojsa Miljanovic
2008-03-18 5:48 ` Willy Tarreau
2008-02-28 20:36 ` Willy Tarreau
2008-02-28 20:44 ` Nebojsa Miljanovic
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=20080228183054.GA903@linuxace.com \
--to=kernel@linuxace.com \
--cc=asweeney@alcatel-lucent.com \
--cc=bpolhemus@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neb@alcatel-lucent.com \
--cc=nkittlitz@alcatel-lucent.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