From: Ross Biro <ross.biro@gmail.com>
To: Ilya Pashkovsky <ilya.pashkovsky@gmail.com>
Cc: netdev@oss.sgi.com,
"YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] port_reuse listen fix (allow simultaneous single listen + outgoing connects from same port)
Date: Thu, 9 Dec 2004 10:36:08 -0500 [thread overview]
Message-ID: <8783be6604120907367db1fda5@mail.gmail.com> (raw)
In-Reply-To: <fcb9aa29041209032521899698@mail.gmail.com>
On Thu, 9 Dec 2004 13:25:26 +0200, Ilya Pashkovsky
<ilya.pashkovsky@gmail.com> wrote:
> This is the latest patch with removed bool > 1 check and ipv6 support.
> http://puding.mine.nu/patches/
> http://puding.mine.nu/patches/patch-reuse-bool-ipv6
>
> to check, you can use netcat (sets SO_REUSEADDR by default).
> on one host (host A): nc -v -l -p 9999
> on another/same host (host B): nc -v -l -p 9000
> on host A: nc -v -p 9999 host.B.ip.addr 9000
> on host B: nc -v host.A.ip.addr 9999
What happens if on host B you do
nc -v -p 9000 host.A.ip.addr 9999?
Seems to me you will break the rule that a connection is uniquely
identified by (srcpip, destip, srcport, destport).
Ross
next prev parent reply other threads:[~2004-12-09 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 11:25 [PATCH] port_reuse listen fix (allow simultaneous single listen + outgoing connects from same port) Ilya Pashkovsky
2004-12-09 15:36 ` Ross Biro [this message]
[not found] ` <fcb9aa290412091010124f754@mail.gmail.com>
[not found] ` <8783be66041209103567bb3310@mail.gmail.com>
[not found] ` <fcb9aa290412091537b2215bd@mail.gmail.com>
2004-12-09 23:39 ` Ilya Pashkovsky
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=8783be6604120907367db1fda5@mail.gmail.com \
--to=ross.biro@gmail.com \
--cc=davem@redhat.com \
--cc=ilya.pashkovsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.org \
/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).