... > > >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
