From: David Laight <David.Laight@ACULAB.COM>
To: 'Marcelo Ricardo Leitner' <marcelo.leitner@gmail.com>,
Michael Tuexen <tuexen@fh-muenster.de>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Xin Long <lucien.xin@gmail.com>,
network dev <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [PATCH net-next] sctp: add support for SCTP_REUSE_PORT sockopt
Date: Tue, 22 May 2018 15:36:58 +0000 [thread overview]
Message-ID: <bfc973f868914c339caed34334f3e170@AcuMS.aculab.com> (raw)
In-Reply-To: <20180521155127.GB5489@localhost.localdomain>
...
> > >> the reason this was added is to have a specified way to allow a system to
> > >> behave like a client and server making use of the INIT collision.
> > >>
> > >> For 1-to-many style sockets you can do this by creating a socket, binding it,
> > >> calling listen on it and trying to connect to the peer.
> > >>
> > >> For 1-to-1 style sockets you need two sockets for it. One listener and one
> > >> you use to connect (and close it in case of failure, open a new one...).
> > >>
> > >> It was not clear if one can achieve this with SO_REUSEPORT and/or SO_REUSEADDR
> > >> on all platforms. We left that unspecified.
> > >>
> > >> I hope this makes the intention clearer.
That really doesn't help for 1-1 sockets.
You need a way of accepting connections that come from a specific remote host.
Otherwise the application has to verify that the remove address on the incoming
connection is the one it is expecting.
It is also a problem if two different applications (instances) want to
generate 'INIT collisions' for the same local addresses but different remote
ones.
The only way 'INIT collisions' are going to work is with a different
option that stops the receipt of an ABORT chunk erroring a connect.
David
next prev parent reply other threads:[~2018-05-22 16:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 7:44 [PATCH net-next] sctp: add support for SCTP_REUSE_PORT sockopt Xin Long
2018-05-19 20:26 ` Marcelo Ricardo Leitner
2018-05-20 19:44 ` Tom Herbert
2018-05-21 0:50 ` Neil Horman
2018-05-21 1:54 ` Marcelo Ricardo Leitner
2018-05-21 3:59 ` Tom Herbert
2018-05-21 7:46 ` Xin Long
2018-05-21 11:39 ` Neil Horman
2018-05-21 12:16 ` Michael Tuexen
2018-05-21 13:48 ` Neil Horman
2018-05-21 14:09 ` Michael Tuexen
2018-05-21 15:51 ` Marcelo Ricardo Leitner
2018-05-22 15:36 ` David Laight [this message]
2018-05-22 7:07 ` Xin Long
2018-05-22 11:51 ` Neil Horman
2018-05-23 7:04 ` Xin Long
2018-05-23 9:48 ` Neil Horman
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=bfc973f868914c339caed34334f3e170@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tuexen@fh-muenster.de \
/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).