Branch: refs/heads/sctp-rework
Home: https://github.com/kronosnet/kronosnet
Commit: 591759f9b0cbb279ae1d6a20d70c2c775ae054ab
https://github.com/kronosnet/kronosnet/commit/591759f9b0cbb279ae1d6a20d70c2…
Author: Christine Caulfield <ccaulfie(a)redhat.com>
Date: 2019-12-13 (Fri, 13 Dec 2019)
Changed paths:
M libknet/transport_sctp.c
M libknet/transports.c
Log Message:
-----------
sctp: Rework SCTP code to not use connect() [WIP]
connect() causes interesting failures on SCTP because the connections
are association-driven rather than connection driven. So if two
nodes run connect at the same time then the first one to succeed sets
up the association and the second one never completes, you're supposed
to use the received socket I beleive.
In thery we should just remove connect() and all will be well, but
it needs some mungeing in the knet code to get the FDs sorted out
properly.
This code is unfinished and not working. It works for the first
link setup but if a link goes down it doesn't yet reconnect.